Example architecture

Engineering change propagation

This is an example architecture, not a client engagement. The operation is composite and the names are generic.

Context

A composite Solar + BESS EPC project where engineering, procurement, project controls, construction and commissioning each hold part of the project's state in a different system.

Operational constraint

The change is approved once, but each function starts acting on the new reality at a different time. Nobody is wrong; the architecture has no defined propagation path.

Design change approvedDecides: Engineering lead
The change is approved once, but each function starts acting on the new reality at a different time. Nobody is wrong; the architecture has no defined propagation path.
EngineeringState it is left in:Revision issuedDecides:Engineering leadSystem of record:Document controlFinds out:Immediately
ProcurementState it is left in:Purchase order still on the old revisionDecides:Nobody definedSystem of record:ERPFinds out:When someone tells them
Project controlsState it is left in:Forecast still on the superseded scopeDecides:Project controlsSystem of record:Cost toolFinds out:At the next reporting cycle
ConstructionState it is left in:Building to a superseded drawingDecides:Site leadSystem of record:Field copyFinds out:When the drawing reaches site
CommissioningState it is left in:Test plan not updatedDecides:Commissioning leadSystem of record:Test planFinds out:At handover, often

A dashed marker means the handoff has no defined owner and depends on a person carrying the context.

The change is approved once, but each function starts acting on the new reality at a different time. Nobody is wrong; the architecture has no defined propagation path.

How to read it

  • Two handoffs have no owner at all. They work because an experienced person remembers them.
  • Four systems each hold a version of the project. None of them is wrong on its own terms.
  • The cost of the change is not what it costs to redraw. It is what gets built, bought and tested against the old revision in the meantime.
  • The fix is rarely a new system. It is a defined propagation path, an owner per state, and a record boundary that says which system is authoritative for what.
Example architecture: engineering change propagation in a Solar + BESS EPC project | BoRo Studio