System architecture

Design the decision before automating the workflow.

A useful system connects the operating state to evidence, authority and action. These architectures define that connection.

01 · NPI

NPI Evidence Architecture

IP-DA-001

What must be true, and what evidence must exist, before the programme advances?

  • 01requirement and configuration truth
  • 02design maturity
  • 03process and tooling readiness
  • 04supplier and material readiness
  • 05quality and verification evidence
  • 06capacity and production readiness
  • 07approval, exception and change control
Outputs
  • Advance
  • Hold
  • Recover
  • Rebase
02 · FLOW

Constraint Intelligence

IP-DA-002

What currently limits throughput, and which action best protects the system?

  • 01demand and mix
  • 02demonstrated capacity
  • 03load-to-capacity condition
  • 04queue and buffer health
  • 05constraint migration
  • 06recovery sequence
  • 07portfolio priority
Outputs
  • Protect
  • Subordinate
  • Elevate
  • Resequence
03 · READINESS

Industrial Readiness Network

IP-DA-003

Which dependency makes the commitment unsafe?

  • 01supplier evidence
  • 02material and lead-time exposure
  • 03process capability
  • 04inspection and release capacity
  • 05quality and traceability
  • 06people, tooling and infrastructure
  • 07approval dependencies
Outputs
  • Ready
  • Conditionally Ready
  • Not Ready
04 · EXECUTION

ERP Decision Layer

IP-DA-004

Which system signal requires action, by whom and by when?

  • 01master-data condition
  • 02demand and supply signals
  • 03orders, routings and material state
  • 04capacity and constraint logic
  • 05exception thresholds
  • 06decision and action traceability
  • 07closure evidence
Outputs
  • Act
  • Escalate
  • Verify
  • Close
05 · GOVERNANCE

Decision Ledger

IP-DA-005

Can the decision be reconstructed and judged fairly after the outcome is known?

  • 01decision question
  • 02known facts
  • 03assumptions
  • 04alternatives
  • 05trade-off
  • 06authority
  • 07decision
  • 08invalidation condition
  • 09action owner
  • 10result
  • 11learning
Outputs
  • Trace
  • Review
  • Learn
  • Update
Boundary

Architecture is not authority.

These systems do not replace engineering approval, regulatory authority, contractual obligations or accountable professional judgement. They structure information and decisions so that authority can be exercised more clearly.

Test the logic in the Decision Lab