Operating Cost

Definition

In business architecture, operating cost refers to the recurring expenditure required to keep a business capability, value stream, or organizational function performing its role — people, systems, facilities, licensing, third-party services, and overhead allocated to sustained operation. It is distinguished from capital or change cost, which covers the investment needed to build, transform, or retire a capability. Architects use operating cost as a lens for capability-based costing: mapping general ledger and cost-center data onto the capability model so leaders can see what it actually costs to perform 'Order Management' or 'Claims Processing' regardless of which department, system, or geography delivers it. This matters because traditional financial reporting is organized by cost center and account code, not by capability. Two business units can both perform 'Customer Onboarding' at very different cost points, and no P&L view will surface that redundancy — only a capability-based operating cost view will. Operating cost analysis is therefore a foundational input to heat mapping exercises, where capabilities are color-coded by cost, performance, and strategic value to prioritize investment or rationalization decisions. It's important to bound the concept correctly: operating cost is not the same as process cost (which measures a specific end-to-end workflow) nor total cost of ownership (which spans the full lifecycle including acquisition and disposal). Operating cost is a steady-state, run-the-business figure, typically expressed annually, and it becomes most powerful when normalized per unit of output or per transaction so that capabilities can be benchmarked against peers, industry standards, or prior years.

Origin & Context

The concept has roots in traditional cost accounting and activity-based costing, but its application to capability models emerged as business architecture practitioners — formalized through frameworks like the Business Architecture Guild's BIZBOK — sought to connect strategy and structure to financial reality. TOGAF and enterprise architecture practice reinforced this by linking cost data to the architecture repository for portfolio and investment governance. The practice matured as organizations moved from IT cost transparency initiatives toward true business capability costing.

Why It Matters

CFOs and business architects care about operating cost because it exposes redundant capabilities, hidden cross-subsidies, and capabilities that are disproportionately expensive relative to their strategic value — all of which drive rationalization and cost-reduction programs. CIOs use capability-level operating cost to justify or challenge technology investment, since a high-cost, low-value capability is a strong candidate for automation, outsourcing, or platform consolidation. In M&A integration, comparing operating cost by capability across two entities is often the fastest way to identify duplication and target synergy realization. Regulators and boards increasingly expect this level of cost transparency in regulated industries where cost allocation must withstand scrutiny.

Common Misconceptions

Myth: Operating cost and IT cost are the same thing.

Reality: Operating cost spans people, process, facilities, and technology — IT cost is only one component. A capability like 'Regulatory Reporting' may have modest system cost but very high labor cost; focusing only on IT spend hides the real driver of expense.

Myth: Operating cost analysis requires a perfect, unified chart of accounts before it's worth doing.

Reality: Most organizations start with imperfect cost allocation and refine it over several cycles. Directional accuracy — knowing that Capability A costs meaningfully more than a comparable Capability B — is enough to drive an initial rationalization decision.

Myth: Lower operating cost for a capability is always the goal.

Reality: Some capabilities are strategic differentiators where higher spend relative to peers is intentional and correct. Operating cost must be interpreted alongside strategic value and performance, never in isolation.

Practical Example

A regional insurer's business architecture team was asked to identify cost-reduction opportunities ahead of a planning cycle. Working with finance, they mapped cost-center spend onto the enterprise capability map, allocating shared services and overhead using activity drivers. The resulting heat map showed that 'Policy Servicing' carried a disproportionately high operating cost compared to peer capabilities of similar strategic value, driven largely by manual reconciliation work split across three regional teams performing the same activity differently. The business architecture lead presented this to the operations and finance leadership as a capability consolidation case, rather than a departmental budget cut, which reframed the conversation around standardizing the capability rather than simply trimming headcount. Leadership approved a phased consolidation of the capability into a single operating model with shared processes and a common platform, materially reducing the ongoing cost base while preserving service levels.

Industry Applications

Financial Services

Capability-based operating cost analysis supports regulatory cost transparency and identifies redundant compliance or servicing functions across business lines and legal entities.

Healthcare

Health systems compare operating cost per capability (e.g., 'Patient Scheduling') across facilities to standardize shared services and reduce variation in administrative overhead.

Manufacturing

Operating cost is mapped against capabilities like 'Supply Chain Planning' to decide where to centralize shared services versus retain plant-level autonomy.

Related Terms

• Heat Map: a visualization technique that frequently uses operating cost as one of its scoring dimensions
• Business Capability: the unit of analysis to which operating cost is allocated