CMMS

The maintenance engine - work orders, requests, preventive maintenance, inspections, parts, vendors, compliance, and costs in one loop.

The CMMS is where daily operations happen. Everything in this section shares one loop: work comes in, gets done against the thing it's for - an asset, a location, a system, or an infrastructure feature - and leaves behind history, costs, and condition data the planning modules feed on.

What lives here

AreaWhat it covers
Work ordersThe unit of work - creation to completion, views, assignment
Work requestsIntake, triage, and live conversations with requesters
Requester portalThe simplified surface for non-staff reporters
PM schedules & templatesRecurring maintenance that generates its own work orders
Forms & inspectionsChecklists and inspections attached to work
Parts inventoryStock, reorder points, and consumption
VendorsContractors and suppliers, with performance history
ContractsService agreements and their expirations
ComplianceRegulatory inspections and certificates on a clock
Expenses & cost trackingWhere every dollar of O&M lands

The operating loop

  1. Intake - a requester reports a problem, or a PM schedule fires, or staff spot something.
  2. Triage - requests are approved and converted; priorities set.
  3. Execution - technicians work their queue; forms capture inspection data; parts get consumed.
  4. Closure - hours and costs recorded, photos attached; costs post to the asset automatically.
  5. Compounding - history, condition, and spend feed risk, FCI, and the replacement planner.

The discipline that makes it work is small: every piece of work is a work order, and every work order points at what it's for - asset(s), location(s), system(s), or infrastructure feature(s). Everything else follows from that.

Roles in the loop

See Roles & access for the full model.