Command Urgent Facilities Maintenance Without Replacing Your CMMS

The Facilities Maintenance Pack is a role-based AI capability bundle for facilities and O&M teams. It turns urgent maintenance issues into job-ready response plans across the systems you already run, covering triage, likely cause and confirm steps, technician assignment, parts and tools, procedure, and safety requirements.

It’s built for the public works departments, installation-support commands, civil engineering shops, and primes that keep federal HVAC, chillers, boilers, and utilities running. Teams get more done with the staff they have, and the overtime and SLA record follows into the recompete. Assets return to service sooner, and preventive maintenance is less likely to slip while an emergency is worked. Work order records arrive structured and every approval is attributed, so the audit record is stronger with less reconstruction.

The answer is spread across four systems. The CMMS knows the work order, the labor system knows who is available, inventory knows which parts exist, and the manuals know the correct procedure. Those systems don’t connect in time to change the outcome, so the supervisor connects them by hand, on the phone, while the SLA clock runs. That takes 20 to 30 minutes and often a second trip. Legion brings the four together and proposes a response in about a minute, and nothing dispatches until a supervisor approves.

No. Maximo stays your system of record, and no data migration is required. Legion reads work order history, manuals, inventory, qualifications, and schedules, then writes structured work orders and schedule changes back once a supervisor approves them.

A CMMS is built to schedule work and hold records, and it does that well. Predictive platforms catch what sensors and service intervals can see. Legion is built for the repair order that arrives as a sentence in a work order note: reasoning across the manual, the repair history, the roster, and the storeroom to propose a response and show what it affects. An internal build has to reproduce those integrations, the approval controls, and the upkeep.

Yes, within a limit. Legion reasons from manufacturer manuals and job plans as well as your repair history, so it can propose a likely cause on an asset with thin local history. Incomplete repair history narrows the local evidence rather than stopping the proposal, and where it does not support a confident call, Legion says so.

A supervisor approves dispatches, schedule changes, work order releases, and reorder-point changes. Legion drafts the package, attaches the safety requirements found in your job plans and SOPs, reserves available parts, and readies the dispatch message. Every action is attributed and logged.

Diagnostic and procedural recommendations cite the source and manual section behind them, so a technician verifies rather than trusts. Legion states whether confidence is high or low, and proposes confirm steps when the supporting evidence does not carry a confident call. LOTO, permit, and PPE requirements found in your job plans and SOPs come attached to the package.

The Pack does not use technician location. It proposes who should take a job from qualifications, availability, and current assignment, and it shows work orders running past their planned duration. What a supervisor sees is the state of the work.

In federal and defense sustainment deployments, the Pack has delivered 25% more technician capacity in the first weeks, 20% less unwanted overtime, and 5+ hours a week reclaimed per supervisor. It generates a structured work order from an inspection report in 1 minute, against 20 to 30 minutes.

Work order history, asset records, technician qualifications and availability, manuals and job plans, and parts inventory, plus the security approvals to reach them. Legion reads these from the systems you already run.

Yes. The same Apps and the same approval controls run in cloud, on-prem, and air-gapped environments. Legion operates across IL2 through IL6 for DoW networks, and the cloud platform carries FedRAMP High authorization.

Weeks, not months. The Pack arrives with its Apps, CMMS connections, and approval controls, so the work is connecting them to your CMMS and document repositories rather than building capability from scratch. The pacing items are usually security review, data access, and integration scope rather than the Pack itself.

IBM Maximo, SharePoint, Microsoft Teams, ServiceNow, Box, NetSuite, and Jira are connected today. Additional CMMS and inventory integrations get built where demand is confirmed.

Yes. You start with the prebuilt Apps, then add custom Apps to the same Pack with Mission Builder as new needs come up. They run on the same connections and approval controls, so you extend the Pack without starting over.