liveBook · Manning

Total cost of ownership

As explained in Effective Platform Engineering

Total cost of ownership is the complete cost of acquiring, deploying, operating, maintaining, and retiring a product or system across its lifecycle.

Total cost of ownership (TCO) measures the complete cost of acquiring, deploying, operating, maintaining, and retiring a product or system across its lifecycle. For platform engineering, it prevents attractive implementations from being judged only by build cost or license price. section 3.5.1

Build a useful TCO view by including:

  • Cloud infrastructure provisioning and usage, including costs at the expected performance and scalability level. section 3.5.1
  • Third-party licensing plus administration, installation, upgrades, and the engineering time saved by using the tools. section 3.5.1
  • Buy-versus-build trade-offs, including replaceability and the future cost of vendor lock-in, retraining, redesign, or replatforming. section 3.5.1
  • Engineering effort, infrastructure, and licensing costs when evaluating the value of a platform capability. section 3.2.2

Platform capability investment

Before building a shared platform capability, compare its engineering, cloud, and licensing costs with expected savings from faster delivery, compliance, or fewer and shorter outages. Record assumptions, choose an investment timeline, and compare returned value with delivery cost through an ROI measure. section 3.2.2

Figure 3.5 Components of value modeling process. These are both subjective and objective measurements that a technical product owner should identify by working with stakeholders and engineers, which will be used to show platform value.
A screenshot of a computer screen

AI-generated content may be incorrect.

Use the value-model components to combine subjective and objective measurements from stakeholders and engineers. section 3.2.2

How Effective Platform Engineering covers it

How deep it goes
Breaks costs into infrastructure, licensing, maintenance, engineering, and lifecycle trade-offs, then connects them to savings and ROI.
Examples
Uses cloud provisioning, third-party tools, shared platform capabilities, delivery time, compliance, and outage reduction as evaluation inputs.
What it assumes
Assumes familiarity with platform capabilities, cloud infrastructure, licensing, engineering costs, and organizational investment decisions.
What you can do after
Evaluate platform capabilities by modeling total costs, expected savings, assumptions, timelines, and return on investment.
How it connects
Connects cloud infrastructure, licensing, buy-versus-build analysis, composable architecture, platform engineering, savings, and ROI.

Also explained in

Compare how 3 books explain total cost of ownership →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.