1. General Information Type Functional enhancement Impacted applications OT and DI Interventions (Maximo) Subject Enable mass status changes for Interventions despite Workflow constraints 2. Context In the HxGn solution, after selecting multiple Interventions in a list, it is possible to perform bulk status transitions. This functionality is used to simplify data entry for small or secondary assets, which exist in large quantities but still require maintenance tracking. In Maximo, the use of Workflows prevents this standard behavior, forcing users to update Interventions one by one, which is time-consuming and not suitable for high-volume operational contexts. 3. Objective Provide a mass status change capability in Maximo for OT and DI Interventions while preserving: • existing business rules, • Workflow validations and controls, • user authorization rules. 4. Functional Requirement – OT Interventions The following status transitions must be possible in bulk: • From OT Released to OT Planned with assignment. • From OT Work Complete to OT Functional Validation. • From OT Functional Validation to OT Closed. 5. Functional Requirement – DI Interventions The following status transitions must be possible in bulk: • From DI Work Complete to DI Functional Validation. • From DI Functional Validation to DI Closed. 6. Target Functional Principle Based on discussions with functional and technical teams: • A dedicated action must be created: “Change Status (Bulk)”. • This action must be available from the Common Actions menu. • It must allow: – applying the status change to all listed Interventions, or – only to the selected Interventions. 1 • The list of available target statuses must correspond to the common statuses allowed for all selected Interventions, in line with Workflow rules. 7. Workflow Handling As bulk status changes are executed outside the Workflow engine: • All Workflow actions and validations must be re-implemented via scripting. • Existing business checks (labor, inspections, VR/VS rules, wait/refusal causes, etc.) must be preserved. • Identified rules (GPAT-2872, GPAT-2969, etc.) must be integrated into the bulk processing logic. 8. Target Status Selection Algorithm Two approaches were analyzed. 8.1 Selected Approach • Analyze the selected Interventions. • Determine the list of common allowed target statuses. • Present the filtered list to the user. • Apply the selected status in a single bulk operation. 9. Eligibility Variable To ensure business consistency: • A specific flag/variable must indicate whether an Intervention is eligible for bulk status change. • This variable must itself be modifiable in bulk. 10. Security and Authorizations The “Change Status (Bulk)” action must be available to the following security groups: • MAXADMIN, ADMIN_DSIM, ADMIN_NATIONAL • ADMIN_LOCAL, ADMIN_ESM, PLANNER • RESP_CONTRACT_EXTERNAL, RESP_CONTRACT_SNCF • RESP_MAINT_EXTERNAL, RESP_MAINT_SNCF The Personae configuration file must be updated accordingly. 11. Constraints and Open Points • Define a maximum number of selectable Interventions (e.g. 500) based on performance analysis. • Choose the execution feedback mode: – blocking dialog with immediate results, – or background execution with results sent by email. • Plan integration into release v1.4. 2 12. Conclusion This enhancement is critical to improve usability, productivity, and adoption of Maximo in high-volume maintenance contexts. The proposed solution reconciles bulk processing, Workflow compliance, and business safeguards.
