Ransford's NotesCourses
Workspace

London LTDS Information Architecture

Walk through London Grid Distribution's Long-Term Development Statement data architecture using CIM entities, showing how network planning data flows from GIS through to regulatory publication.

Phase C, Information Systems ArchitectureDerived from TOGAF

The LTDS information journey: from operator data to a published product

Six steps move the data from the operator's systems to the regulator: raw operator data, CIM model, validation, package, publication and regulator consumption, each owned by a different team.

The LTDS is an information product, not a document. The journey names the six steps the data must clear, the hand-off between each pair of teams, and the one step that can stop the flow before the regulator ever reads it.

The LTDS information journey: from operator data to a published product A vertical pipeline of six numbered steps with a left axis pointing down, labelled information journey, joined by labelled flow arrows. Step 1 Operator data from the DNO maps to step 2 CIM model on the IEC CIM profile (EQ, SC, SSH), which validates to step 3 Validation, SHACL shape rules that check the model and can reject it, shown in amber as a gate that can stop the flow. It packages to step 4 Package, CGMES files with a header and dependencies, publishes to step 5 Publication on the LTDS endpoint, and Ofgem consumes it at step 6 Regulator. A red note states that the reader only ever sees the last step, so every hidden step needs its own owner and check. Information journey 1Operator dataNetwork, asset and capacity data from operational systemsDNO 2CIM modelData mapped to the IEC CIM profile (EQ, SC, SSH and more)IEC CIM 3ValidationSHACL shape rules check the model and can reject itSHACL 4PackageCGMES files assembled with a header and dependenciesPackager 5PublicationThe package is published to the LTDS endpointPlatform 6RegulatorOfgem and other consumers download and use the productOfgem maps validates packages publishes consumes Transformation stepGate that can stop the flow The reader only ever sees the last step.Every step before publication is hidden, yet each one is a place the data can be wrong, so each needsits own owner and check.