The current ELMS system uses an overly simplified and outdated set of job statuses that does not reflect the full range of actions and stages in Marine Corps maintenance workflowsBRD JOB STATUES. This limited framework creates several operational and reporting issues:Units lose visibility of their equipment once it is evacuated to higher echelon maintenance, preventing accurate readiness reporting.Lack of granular statuses disrupts communication between organizational levels and reduces transparency of maintenance progress.There is no real-time visibility for using units, which hinders operational planning.Readiness reporting is compromised, particularly when equipment is in intermediate maintenance activities but only shows as a generic “in maintenance” status.
Identified Material Weakness: The absence of sufficient job status categories and transitions creates a material weakness in reporting and accountability, leading to inaccurate readiness visibility, poor auditability, and delays in decision-making.
Job Status Framework Enhancements
1.1 Expanded Job Status List
FR1.1.1: The system shall support a configurable and extensible list of maintenance job statuses that accurately represent each phase of the maintenance lifecycle.
FR1.1.2: The new status list shall include, but not be limited to: (list here)
FR1.1.3: Each job status shall be associated with a standardized definition and criteria for transitioning to/from other statuses.
FR1.2.1: The system shall support controlled status transitions based on workflow logic or user roles.
FR1.2.2: Users shall be prompted with a reason code or comments field when skipping or overriding standard status flows.
FR2.1.1: The maintenance job form shall display an updated drop-down menu or status selection tool that reflects the full status list.
FR2.1.2: Status changes shall be logged with user ID, timestamp, and optional notes.
FR2.2.1: Each job status shall be color-coded in dashboards and reports to enhance visual identification (e.g., red for “Awaiting Parts,” green for “Repair Complete”).
FR3.1.1: Users shall be able to filter maintenance job reports based on any job status or combination of statuses.
FR3.1.2: Reports shall include job status progression history for auditing and analysis.3.2 Performance Metrics
FR3.2.1: The system shall generate performance metrics based on time spent in each job status.
FR3.2.2: Metrics shall include Mean Time to Repair (MTTR), parts wait time, and overall repair cycle time.
FR4.1.1: System administrators shall be able to add, remove, rename, or reorder job statuses via a configuration panel.
FR4.1.2: Changes to the status list shall be logged and version-controlled.4.2 Role-Based AccessFR4.
ELMS does not provide currently.