Stage 0. Foundations: phase summary

6 min read 5 sections 7 key points

The Foundations phase builds the ground floor for everything that follows: how electricity actually travels from a power station to your wall socket, what a distribution network operator like the fictional London Grid Distribution does each day, and why a company cannot change its systems piece by piece without losing control. By the end you can describe the generation, transmission, and distribution chain, name the five core systems London Grid runs, and explain in plain terms why architecture is the discipline that keeps a complex organisation working as one. These three primers give you the context to understand why TOGAF and enterprise architecture matter before Module 1 introduces them formally.

Electricity reaches you through three connected stages

Electricity is the flow of electrons through a conductor, pushed along by voltage, and it travels through generation, transmission, and distribution. Generation spins a magnet inside coils of wire, whatever the energy source, so once electrons are on the network there is no difference between wind, gas, or solar power. Transmission is the motorway, carrying power at 275,000 or 400,000 volts because higher voltage loses less energy as heat over long distances; distribution is the local road system, stepping voltage down through substations and transformers to 132,000, 33,000, 11,000, and finally 230 volts at the socket. In Great Britain, NESO operates the transmission network and 14 licensed DNOs manage the local networks.

The grid is a balanced system that can cascade

Generation and demand must match at every moment, or the system frequency drifts away from 50 hertz. When frequency falls too far, automatic protection systems shed load, deliberately cutting some customers to save the rest from a full blackout. On 9 August 2019 a lightning strike led to two generators, Little Barford and Hornsea One, disconnecting within moments; the grid lost more power than backup could replace, and over one million homes went dark. The investigation found the protection worked as designed but coordination between generators, transmission, and distribution had gaps, which is an information, communication, and organisational problem as much as an engineering one.

London Grid Distribution is a fictional but realistic DNO

London Grid Distribution is invented for this course, modelled on a mid-sized DNO covering Greater London with roughly 40,000 kilometres of underground cable, 200 major substations, 3.5 million customers, and around 4,000 staff. Its core job is keeping power flowing safely and reliably around the clock: monitoring the network, fixing faults, connecting new customers, maintaining and upgrading equipment, and planning ahead. It runs five key systems, summed up as SCADA the heart monitor, DMS the satnav, GIS the map, OMS the fault tracker, and ERP the business backbone, all built at different times and struggling to share data.

The energy transition forces the company to change

Distribution was built for one-way flow from large generators to consumers, and that model is breaking down. Three forces drive change: Clean Power 2030 brings more variable renewable generation that is harder to balance; rooftop solar pushes surplus power back into a network never designed for two-way flow; and the electrification of heat and transport sharply raises demand, where a single EM fast charger can draw as much as a whole house. The 2024 connections queue reached over 700 gigawatts against roughly 50 gigawatts of peak demand, more than fourteen times the system, forcing NESO to redesign a process built for a few large power stations. Meeting all this needs more than new cables; it means new processes, data systems, and skills across the whole organisation.

Architecture coordinates change before it goes wrong

When teams each buy the best tool for their own job without checking how the tools connect, the result is islands of information, duplicated spend, decisions made on incomplete data, change that is slow and risky, and regulatory failure. In the running scenario, London Grid spent over eight million pounds on five good systems that together could not answer a basic question about its ten worst circuits because nobody asked how they would work together first. Architecture gives a shared map of what exists, a picture of the target state, a sequenced plan to get there, and rules to keep change on track. Applied to a whole organisation it becomes enterprise architecture, looking at business, data and information, applications, and technology together, which Module 1 introduces properly using TOGAF.

Watch out for

  • Thinking different power stations produce different qualities of electricity; once electrons are on the network, wind, gas, and solar are indistinguishable
  • Treating London Grid Distribution as a real company; it is a fictional teaching device with realistic but invented details
  • Assuming the energy transition is solved by building more cables and substations alone; it also needs new processes, data systems, and skills
  • Believing architecture is about drawing diagrams and producing documentation; its purpose is to improve decisions about change, and documentation is only a by-product

Key takeaways

  • Electricity flows through three stages: generation, transmission at 275,000 or 400,000 volts, and distribution stepped down to 230 volts at the socket
  • The grid must keep generation and demand matched near 50 hertz; when frequency falls, automatic protection sheds load, as in the 9 August 2019 blackout that hit over one million homes
  • Great Britain has NESO operating transmission and 14 licensed DNOs; London Grid Distribution is a fictional DNO with about 40,000 km of cable, 200 substations, 3.5 million customers, and 4,000 staff
  • London Grid runs five core systems: SCADA (real-time readings), DMS (decision support), GIS (asset map), OMS (outage tracking), and ERP (finance and business)
  • Three forces drive change: Clean Power 2030, two-way power flow from rooftop solar, and electrification of heat and transport; the 2024 connections queue hit over 700 GW against 50 GW peak demand
  • Without coordination, companies get disconnected systems, duplicated spend, and slow risky change; London Grid spent over eight million pounds on five systems that could not share data
  • Enterprise architecture looks at business, data and information, applications, and technology together, which is what distinguishes it from narrower IT architecture

With the physical network, the company, and the case for architecture now clear, the scenario practice lets you apply these foundations to realistic London Grid situations and catch the common mistakes before the timed stage assessment.

Start the scenario practice