Key findings

API And Data Export appears in 42 of 45 maintained organization records, the highest documented count in the current sample. Facilities And Space-Linked Maintenance appears in 6. A higher count signals more public positioning, not greater importance or product quality.

Capability	Documented records	Share of maintained sample
API And Data Export	42	93%
Asset Registry And Hierarchy	39	87%
ERP MES SCADA And Historian Integration	39	87%
Document Control And Audit Trails	36	80%
Work Requests And Work Order Control	32	71%
Preventive Maintenance Scheduling	32	71%
Inspection And Route Execution	32	71%
Maintenance Cost And Budget Analysis	32	71%
Multi-Site Governance	32	71%
Mobile Technician Execution	31	69%
Labor And Crew Scheduling	31	69%
Job Plans And Standard Procedures	31	69%
MRO Parts And Inventory	31	69%
Meter And Usage-Based Maintenance	30	67%
Downtime And Availability Analysis	28	62%
Failure Codes And Maintenance History	27	60%
Condition Monitoring And Sensor Ingestion	26	58%
Asset Health And Performance Analytics	23	51%
Purchasing And Vendor Coordination	20	44%
Maintenance Knowledge And Assisted Triage	20	44%
Anomaly Detection And Failure Prediction	18	40%
Asset Criticality And Risk Ranking	16	36%
Offline Field Work	12	27%
Warranty And Contract Records	12	27%
Capital Planning And Asset Investment	10	22%
Safety Permits And Compliance Evidence	9	20%
Reliability-Centered Maintenance And Strategy	7	16%
Vibration And Machinery Diagnostics	7	16%
GIS And Linear Asset Management	6	13%
Facilities And Space-Linked Maintenance	6	13%

What the count can support

The dataset can show how frequently a capability appears in approved official positioning, which operating models document it, and where a buyer may find research candidates. It cannot show depth, accuracy, configured availability, implementation quality, adoption, satisfaction, commercial fit, or outcome.

Methodology

Define the market boundary, exclusions, operating models, and capability taxonomy before classifying organizations.
Require an approved official source for organization inclusion and each documented capability.
Keep authority sources, provider claims, independent observations, editorial synthesis, and unknowns in separate evidence states.
Use one primary operating model per organization while retaining adjacent scope in the narrative record.
Preserve source URLs, review dates, material changes, limitations, and correction history.

Limitations

The maintained population is substantial but not claimed to be a complete global market.
Official public documentation may omit available capabilities or lag product and service changes.
Documented positioning does not measure product depth, configured availability, independent performance, implementation effort, customer outcome, or commercial terms.
Authority mappings are editorial research aids and do not establish buyer-specific applicability or product conformity.
No organization may purchase inclusion, classification, finding, or correction outcome.

Reproducibility and updates

The report is reproduced from the provider registry, normalized facts and evidence, authority and domain records, and the publication taxonomy. A material change requires a dated source and editorial explanation. Historical values remain available through the change ledger rather than disappearing when the current record changes.

Research boundary

Maintenance Operations Ledger is not a maintenance contractor, engineering firm, regulator, standards body, certification body, inspection authority, insurer, or software provider. Its records support research and operational review; they do not establish legal compliance, engineering sufficiency, safe condition, standards conformity, failure diagnosis, required maintenance, prediction accuracy, reliability outcome, or fitness of any system for a particular asset estate.

Provider capability coverage

What current official company records document across the normalized maintenance capability model—and what those records do not establish.