CAFM and workplace management
The estate and the work done on it: sites, assets, contracts, planned maintenance and every work order raised.
01 What it holds
The data inside it
The contractual scope of a facilities operation and the operational record of delivering it, including SLA response and rectification times.
Site, Asset, Contract, SLA, Work order, PPM schedule, Subcontractor, Variation
02 Getting the data out
Extraction, and the keys that decide whether it joins
Vendor APIs and database access. Multi-client operations often run one instance per client or per contract, which fragments group-level analysis.
Asset identity rarely matches the client's own register or the field service app, so failure history does not accumulate against the physical asset.
03 What goes wrong
The failures that look like success
Each of these produces a number that is plausible, reconciles to something, and is wrong. They are worth reading before the first extract, not after the first dispute.
Planned versus reactive classification
The ratio drives contract profitability, and the classification is set by whoever raised the work order.
Work completed but not billable
Missing sign-off, photo or variation approval leaves finished work sitting in unbilled balances.
SLA clocks with local rules
Pause conditions, working calendars and priority definitions vary per contract, so a group SLA number needs a mapping layer.
One instance per client
Comparing performance across contracts requires consolidation that the tooling deliberately does not provide.
04 Joins that matter
What this system is worth joining to
| Join to | What it lets you answer |
|---|---|
| Field service | what the technician actually did, and whether it is billable |
| Procurement and inventory | subcontract cost and parts consumed per work order |
| BMS / IoT | condition and consumption data ahead of a reactive callout |
05 Metrics it feeds
The numbers that come out of it
06 Questions
Frequently asked
What single join makes FM data useful?
Work order to a resolved asset. Without it there is no service history, no repair-or-replace analysis and no way to find the asset that is quietly consuming the contract margin.
How is contract profitability produced?
Labour, subcontract and parts joined to the work order, and work orders joined to the contract, with unbilled work included. Most operations can produce revenue per contract and not cost.
Connect this system without replacing it
SCIKIQ reads it in place, resolves the entities inside it and governs what the fields mean.