The monthly review between operations and finance brings the two leads into the same room with two different dashboards that never quite mesh. The operations director presents the OPEX breakdown by cost center, with the monthly evolution of the four main categories: direct labor, materials, subcontracting and technical services. Finance presents actual versus budget, also by cost center, with year-to-date variance. Both readings are technically correct and both are insufficient to answer the question the CFO has just posed for the third month in a row: which specific assets are driving cost upward and which per-asset unit cost is drifting quarter over quarter. The answer arrives as an Excel extract three days later, is brought to next month's meeting and by then has become stale.
Cost per managed asset is the metric that unifies operations and finance because it lives in both domains simultaneously: operations captures the intervention, the direct labor hours, the materials and the external services linked to the asset; finance owns the amortization, the depreciation and the structural allocations. The sum of both components at the asset level produces the reading the monthly review needs, but it can only be produced when the two domains share an asset identifier, an allocation rule and a reconciliation cadence. In most private operators, those three elements exist only halfway, and that is why the metric that could technically exist ends up not existing.
The four components of cost per asset
A useful reading of cost per asset rests on four components which, summed, provide the total figure on which operations and finance can act in coordination. The first is direct maintenance cost: technical labor hours attributable to interventions on the asset, materials consumed, specific subcontractor services and imputable travel. This component naturally lives in the CMMS when field capture is done with a firm link to the specific asset. The second is indirect maintenance cost: planning, coordination, spare parts management and area administration hours allocated to the asset by rule — typically by intervention count and by criticality. The third is accounting amortization or depreciation, which lives in the financial ERP. The fourth, when the operation can calculate it, is the opportunity cost of unavailability: production lost during out-of-service hours, valued at the asset's unit margin or the service's sales price. The four components have different granularities and cadences, but they share the same key element: the asset identifier.
The three usual barriers to unification
The first barrier is the identifier. The CMMS uses an internal taxonomy, with codes derived from the installation project or the manufacturer catalog. The ERP uses an accounting code, aligned with the chart of accounts and the amortization rules. The two systems refer to the same physical asset by two different codes that have rarely been formally aligned. Without a maintained correspondence, reconciliation happens by name or description, and both methods are fragile and consume human time every month.
The second barrier is the granularity of allocation. The CMMS can allocate labor hours at the level of a specific intervention with a timestamp; the ERP consolidates labor cost at the monthly payroll level per cost center. Without a top-down rule from ERP to asset level, direct labor cost can only be estimated by proportion, not reproduced exactly.
The third barrier is cadence. The CMMS produces data in real time or daily; the ERP closes monthly. The operational conversation runs in weeks; the financial conversation runs in months. A useful reading of cost per asset requires synchronizing the two rhythms, not imposing one on the other.
Three practices that unify without opening an ERP project
The technically correct solution would be a full integration between CMMS and ERP, with shared master, asset-level allocation and continuous close. In practice, that is a costly project on an eighteen-to-thirty-six-month horizon that most mid-sized operators cannot afford. Three lighter practices produce most of the value without opening that project.
The first is to establish a canonical asset identifier that both systems reference explicitly. The identifier can live in the CMMS — if the master is the system of record on the operations side — with a bidirectional correspondence table to the ERP's accounting code. It is maintained by a named owner and audited once per quarter. The second is to define indirect cost allocation rules both sides accept: for example, planning and coordination assigned to the asset by a combined ratio of sixty percent by intervention count and forty percent by criticality. The rule is agreed once, applied uniformly and reviewed annually. The third is to set a fortnightly or monthly reconciliation cadence — depending on operation size — with a partial close that prevents the drift between the two domains from growing beyond the tolerance margin.
The reading that changes what can be decided
With the three elements in place, the monthly review changes. The CFO stops asking for an Excel extract and starts asking about specific assets with deteriorated unit cost, about cost bands by criticality and about comparisons between assets of the same type inside the portfolio. The conversation moves from defending budget lines to deciding on interventions. For this operator profile, Maptainer offers a WebGL-rendered interface that lets the CFO navigate from portfolio total to specific asset unit cost within the same session, with the breakdown of the four components visible without exporting to an intermediate spreadsheet. One hundred thousand assets are traversed in the interface at the same rhythm as a single cost center would be traversed; and that fluency is what allows the operational decision to be made inside the meeting, not in the following day's email.
The metric that reconciles two cultures
Cost per managed asset is a technically simple and culturally difficult metric. It requires operations to accept allocating with the discipline finance demands and finance to accept pushing allocation detail down to the level at which operations acts. The reconciliation between the two cultures is not done by a dashboard, it is done by the discipline that sustains the three elements above. But when the dashboard exists and faithfully reflects that discipline, the monthly meeting between operations and finance stops being a defensive review and becomes a joint conversation about which assets are worth intervening in next month. That is the meeting the organization needs, and it does not depend on the size of the budget but on the quality of the reading.