Ransford's NotesCourses
Workspace

Architecture Decision Record

Document an architecture decision in the Nygard format with context, decision, status and consequences so the reasoning survives the meeting.

Phase G, Implementation GovernanceDerived from Nygard ADR

Architecture Decision Record: adopting the IEC CIM for the LTDS

A Nygard-format record reads as a spine: the context flows into the decision, the one emphasis anchor, which then branches into the consequences it accepts and the alternatives it set aside.

An ADR captures one decision and the reasoning behind it, so a future team can see not just what was chosen but why, and what was weighed and rejected at the time it was made.

Architecture Decision Record: adopting the IEC CIM for the LTDS A Nygard-format Architecture Decision Record drawn as a reasoning spine. A header band carries record number 0007, the title adopt the IEC CIM as the LTDS data model, and a green Accepted status. A Context panel sets out why the LTDS must publish network data others can consume. An arrow labelled motivates flows down into the Decision panel, the single red emphasis anchor: model the LTDS on the IEC Common Information Model. The decision branches into two columns: on the left, three Consequences accepted shown in green; on the right, two Alternatives set aside shown in amber. A legend names the two states and a red note records that one ADR holds one decision. Record 0007 Adopt the IEC CIM as the LTDS data model Accepted WhyContextThe LTDS must publish distribution network data that regulators andneighbouring networks can consume without bespoke rework each time. motivates PickDecisionModel the LTDS on the IEC Common Information Model (CIM), mappingevery published entity to its CIM class rather than a local schema. Consequences acceptedInteroperable from day oneConsumable by NESO and other DNOsReuses a global standardNot a one-off local schemaRamp-up costCIM is large, so the team needs time Alternatives set asideBespoke relational schemaQuicker to start, but not interoperableSpreadsheet publicationReadable, but not machine-consumable Accepted consequenceAlternative set aside One record, one decision.The next team reads why CIM was chosen and what was rejected, without reopening the debate.