Formal Value & Decision-Support Architecture
This pillar's founding principle can be stated in four words: betting is not deciding. Every major asset decision must be supported by an explicit, quantified value comparison rather than experience-based intuition alone.
Two facilities with identical 90% availability can differ by more than $100M in projected value over ten years. Scalar performance metrics alone are structurally insufficient.
Plan Before Control Before Execution Before Verification
This ordering is what separates a governed value process from a reporting exercise dressed up as management. It is the direct operational expression of KIAME's third enforceability condition.
Forecast expected value before the decision is made. Define what success looks like in quantified terms before any action is authorized.
Define control points and tolerances that will confirm whether execution is tracking the forecast while the decision is still being carried out.
Carry out the decision within the controlled framework. Deviations from forecast trigger structured review — not post-hoc explanation.
Close the loop with a confirmed outcome checked against the prior forecast. An unplanned favorable result is an unexplained variance, not a success.
“A good result is only accepted as proof of a working system when it was forecast and pursued deliberately — not when it arrived unplanned. A lucky shot and a governed outcome can look identical in hindsight. They are not the same thing. Only the second one is repeatable.”
What Pillar 2 Enforces — and Why
Every major decision must be supported by an explicit, quantified value comparison rather than experience-based intuition alone. Intuition has a role in framing options; it does not have a role in replacing formal comparison.
A late measurement of value, produced after the fact through periodic reporting, is not evidence of enforcement. It is simply late accounting, arriving only in time to explain why a decision underperformed rather than in time to change it.
Under KIAME, an unplanned favorable result is not treated as success. It is treated as an unexplained variance that must be investigated, because a system that only recognizes success in hindsight cannot be enforced going forward.
Two facilities with identical 90% availability figures can differ by more than $100M in projected value over a ten-year horizon. Availability is not value. Enforcing availability targets without connecting them to financial outcomes is a governance gap, not a governance practice.
Industrial Digital Assets & iDSS at This Layer
Formal optimization applied to complex configuration problems has produced value estimates in the range of $500M to $1B in net present value. These are not theoretical figures; they are documented outcomes from applying the tools Pillar 2 mandates.
Probability distributions over outcomes — not point estimates
P50/P80 capital, operational, and TAR scenarios compared against forecast
Demonstrated value estimates: $500M–$1B NPV in complex configuration problems
Reliability and availability outcomes connected to enterprise financial metrics
Value stated before execution, confirmed against forecast afterward
Unplanned favorable results treated as unexplained variance, not success
Value difference between two facilities with identical 90% availability over a 10-year horizon — demonstrating that scalar metrics cannot guide decisions.
Value estimates from formal optimization applied to complex configuration problems — the scale Pillar 2 tools are built to protect or unlock.
Pillar 2 closes FM-02 and FM-04
Every major decision must pass through a formal, tool-based value comparison, eliminating value as rhetoric.
Because Pillar 2 must be defined before technology selection, KIAME prevents software acquisition from substituting for architectural clarity.
Engineering Context
This page connects Knar's work to established engineering, reliability, and asset-management disciplines where those connections are materially relevant.
- Life cycle cost and value — Value & Decision-Support Architecture formalizes how lifecycle cost and value trade-offs feed into real decisions, turning financial modeling into a structural input rather than a report that sits separate from operations.
- Monte Carlo simulation — Decision-support architecture depends on probabilistic modeling techniques like Monte Carlo simulation to translate uncertain operational inputs into defensible financial ranges rather than false-precision point estimates.
- Asset financial performance — This pillar exists to translate asset performance into the financial language executives act on, making value and decision-support architecture the structural mechanism behind every asset financial performance claim we make.