Add Configuration Audit Trail for Map Manager and GIS/Spatial Configuration

Hi Team

Currently, the Map Manager application in IBM Maximo Manage lacks standard fields or an audit mechanism to identify when a configuration record was created or modified, and which user made the change.

The MAPMANAGER table does not currently contain information such as:

• Created By
• Creation Date
• Changed By
• Changed Date

As a result, it is difficult to determine who originally created or subsequently modified a Map Manager configuration.

This is particularly important in enterprise environments where Maximo is shared and maintained by multiple internal teams, implementation teams, and external vendors. Proper traceability is required for governance, troubleshooting, change management, and accountability.

Business Impact

Without this information, it is difficult to:

• Identify who created a GIS/Map Manager configuration.
• Determine who subsequently modified a configuration.
• Establish when a configuration change was made.
• Investigate unexpected configuration changes.
• Maintain an accurate audit trail across teams and vendors.
• Support change-management and compliance requirements.

Currently, the only potential way to identify the user is through system/application logs. However, these logs may only be retained for a limited period. Once the relevant logs are no longer available, it is no longer possible to reliably determine who created or modified the configuration.

Requested Enhancement

Please provide a supported audit/traceability mechanism for Map Manager and other relevant GIS/Spatial configuration records.

At minimum, the solution should capture:

• Created By
• Creation Date
• Changed By
• Changed Date

The information should be available through the Maximo application and/or an appropriate supported audit/history mechanism.

Historical Records

An important part of this requirement is the treatment of existing records.

If this functionality is introduced in a future MAS release, please clarify how existing Map Manager records would be handled.

Ideally, the solution should provide a supported mechanism to retain or establish the available creation/change information for existing records where such information can be determined. At minimum, IBM should clearly document whether the enhancement applies only to records created or modified after the functionality is introduced.

Scope

Although the immediate requirement is for Map Manager, the same capability would be valuable for other GIS/Spatial configuration records where configuration changes need to be traceable.

A consistent audit mechanism across Maximo configuration records would provide significant benefits for enterprise governance and change management.

Expected Benefit

This enhancement would provide customers with reliable configuration traceability and improve:

• Governance and accountability
• Change management
• Troubleshooting
• Security and auditability
• Vendor/team accountability
• Operational support

It would also reduce the dependency on short-term application logs to determine who performed a configuration change.