Smart Places and Infrastructure · Study deck

Smart Grid: Measurement and Architecture

This first route starts with field measurements, safety boundaries, grid value, and the layered architecture that carries trustworthy observations.

Ada is your guide for this deck.

applicationdomainssmart

Ada, the module guide, in a scene from this chapter.

After studying this chapter

Learning objectives

You will be able to:

Explain: The utility has no idea how much power you're using right now, whether your air conditioner just kicked on, or if a transformer down the street is about to fail.
Explain: A 15-minute interval produces 60 ÷ 15 = 4 readings per hour, or 96 per day, while a last-gasp outage message must move with different urgency.
Explain: A DER dispatch should show the requested active-power or reactive-power behavior, the inverter capability curve, customer consent, aggregator responsibility, and settlement record.
Explain: CVR reduces voltage to 116V while staying within ANSI C84.1 service limits.

Major section

Overview · Start With the Story

This first route starts with field measurements, safety boundaries, grid value, and the layered architecture that carries trustworthy observations.

A local line is near its safe limit.
A control-room team must decide whether to change voltage, shift demand, or send a field crew.
A dashboard hint may wait for review.
Each sees a different failure.

Major section

For Beginners: What Is a Smart Grid? · Grid Measurement and Control

The utility has no idea how much power you're using right now, whether your air conditioner just kicked on, or if a transformer down the street is about to fail.

Smart-grid devices only help when each reading or command has a clear operating consequence.

Grid automation boundary: smart-grid IoT connects field equipment, customer resources, and operational control systems across generation, transmission, distribution, and consumer domains.

Major section

Map Field Devices to Grid Systems

Practitioners also need data governance that respects operational separation.

A smart-grid architecture has to connect field devices to operational and market systems without blurring their roles.
Smart meters from vendors such as Itron, Landis+Gyr, Sensus, or Honeywell may feed an AMI head-end and MDMS.
The integration contract should name these boundaries explicitly.

Major section

Map Field Devices to Grid Systems (continued)

A FLISR step should show the feeder section, protective device state, crew safety constraint, and rollback action.

Substation IEDs, reclosers, relays, capacitor banks, voltage regulators, and RTUs may communicate with SCADA, DMS, ADMS, OMS, EMS, DERMS, or forecasting tools.
Customer and DER programs may use OpenADR, IEEE 2030.5, SunSpec Modbus, OCPP, or utility APIs.
The test should prove who sees the problem, who can override, and what evidence remains for after-action review.

Major section

Map Field Devices to Grid Systems (continued)

An AMI outage event should show whether it came from a last-gasp message, periodic read, manual call, or restoration ping.

A DER dispatch should show the requested active-power or reactive-power behavior, the inverter capability curve, customer consent, aggregator responsibility, and settlement record.
Fast operational events belong in SCADA, DMS, ADMS, historian, or event-stream platforms with tighter timing and access controls.
Forecast and market data can inform decisions, but it should not quietly bypass protection settings or operator clearance rules.

Major section

Grid Data Safety Boundaries

A lost weather sensor may degrade a dashboard; a bad grid command can damage equipment or create unsafe field conditions.

The design should define which systems are allowed to observe, recommend, command, block, and override.
The same event may have different meanings in protection, operations, billing, customer support, and regulatory evidence.
Command paths need the same discipline.

Major section

Grid Data Safety Boundaries (continued)

A phasor value without clock quality is not equivalent to a validated SCADA point.

Under the hood, a grid event should carry provenance.
A meter read that passed billing validation is not automatically suitable for fast operational control.
A forecast can guide dispatch, but it must not be confused with measured capacity.
Some should require operator confirmation.

Smart Meter Data Flow from Home to Utility Cloud

Major section

Grid Data Safety Boundaries (continued)

It should identify the device or system that produced it, the asset and feeder context, the time source, the quality state, the transformation path, and whether it is raw, estimated, validated, operator-confirmed, or settlement-grade.

A recloser operation, capacitor-bank change, inverter function update, EV charging limit, and customer demand-response signal have different risk profiles.
Some actions should remain local and protection-driven.
Some may be safe for automated optimisation if they have constraints, rate limits, and rollback.
Logs should capture request, authorization, target, previous state, command state, acknowledgement, timeout, failure, and rollback so the control story can be reconstructed.

Major section

Putting Numbers to It

CVR reduces voltage to 116V while staying within ANSI C84.1 service limits.

The voltage reduction ratio is 116 / 120 = 0.9667.
For resistive loads, which make up about 40% of this residential example, power consumption scales with voltage squared.
Energy savings on the resistive portion are 15 TWh x 0.40 x (1: 0.9345) = 0.393 TWh/year.

Major section

The Four-Layer Smart Grid Architecture · Wide Area Monitoring Systems (WAMS)

The band underneath pairs those layers with example IoT roles, and the timing spread is stark.

The legend adds the arrow that breaks the old picture.

Smart Grid Four-Layer Architecture with IoT Integration Points

Major section

Smart Meter Data Flow

In the second, the round display sits high on a larger rectangular cabinet against stone.

The third has a dark front cover with its display and label visible.
Those different cases change what can be checked on site.
Three things stand out in Figure: This installed household smart meter is the endpoint.
It names which quantity was measured.

A round digital electricity meter is mounted on a metal service box against a brick wall, showing its display, housing, and installation form.

Major section

Smart Meter Data Flow (continued)

The display carries a register code beside the energy figure, so a reading is never just a number.

The nameplate underneath fixes voltage, current range, temperature limits, a serial number and an identifier the utility uses to tell one meter from millions.
Together they explain why meter data can support billing and outage decisions.
Reading frequency: traditional meters are read manually each month; smart meters report automated interval data, often every 15 minutes, for real-time visibility.

A mounted smart electricity meter with a circular display and blue interface, enclosed in a rectangular box.

Major section

Smart Meter Data Flow (continued)

Outage detection: traditional outage reporting depends on customer calls; smart meters can send last-gasp messages that speed restoration and dispatch.

Billing accuracy: traditional bills often rely on estimates; smart meters provide actual interval usage that reduces disputes.
Remote disconnect: traditional service changes require truck rolls; smart meters can receive authorized remote commands, saving about USD 75 per service call.
The MDMS validates and stores readings before clean intervals support billing, analytics, and the customer app.

A dark gray rectangular smart electricity meter mounted on a wall. Its front has a display behind a clear cover, two round buttons, a right-side interface port, and a visible SP AusNet label above the screen.

Major section

Smart Meter Data Flow (continued)

Theft detection: traditional metering makes abnormal consumption hard to detect; smart-meter analytics can flag anomalies and recover billions in lost revenue.

A 15-minute interval produces 60 ÷ 15 = 4 readings per hour, or 96 per day, while a last-gasp outage message must move with different urgency.
Authorized commands can return to the meter, so identity and audit matter in both directions.
The photos matter because the same device name does not tell us what is accessible after installation.

This installed household smart meter is the endpoint that turns local energy measurements into the interval readings, outage messages, and authorized control data described in the flow below. Photo: RobbieIanMorrison, CC BY 4.0

Deck summary

Key takeaways

This first route starts with field measurements, safety boundaries, grid value, and the layered architecture that carries trustworthy observations.

The utility has no idea how much power you're using right now, whether your air conditioner just kicked on, or if a transformer down the street is about to fail.
Practitioners also need data governance that respects operational separation.
A FLISR step should show the feeder section, protective device state, crew safety constraint, and rollback action.
An AMI outage event should show whether it came from a last-gasp message, periodic read, manual call, or restoration ping.

Retrieval practice

Recall check 1 of 3

Ada says: answer from memory, then check your reasoning.

Q1A utility sends a demand-response request to flexible loads. What makes that path different from a meter read?

AA billing observation without authority to change flexible loads.

BAuthorized grid control with fallback and an auditable action record.

CAn unverified dashboard command sent to flexible loads without approval.

DA load-control action with no record because customers may opt out.

Show answer

Answer: B Controlled load changes need a validated owner and safe fallback.

Retrieval practice

Recall check 2 of 3

Ada says: answer from memory, then check your reasoning.

Q2What makes smart-grid IoT different from a simple consumer sensor deployment?

AGrid IoT links measurement, control, safety, timing, and cyber constraints

BSmart grids are mainly about adding more decorative dashboards

CPower systems can ignore latency and safety because sensors are low power

DCybersecurity matters less because grid devices are not connected to homes

Show answer

Answer: A Smart-grid deployments are critical infrastructure, so reliability, safety, latency, and security shape every design choice.

Retrieval practice

Recall check 3 of 3

Ada says: answer from memory, then check your reasoning.

Q3A utility needs to compare grid conditions at distant substations. What should it use?

AMonthly customer meter bills from nearby homes.

BUse time-synced PMU readings across a WAMS.

COne thermostat reading at a single substation.

DA retail checkout log for the same district.

Show answer

Answer: B PMUs measure grid conditions, and WAMS brings the readings together across sites.

Q4A neighborhood loses power. What new evidence can smart meters send before going offline?

AOnly the next manual meter reading

BA thermostat setting from each home

CA guessed bill for the month

DLast-gasp outage messages

Show answer

Answer: D A meter can send a last-gasp message so the utility can locate and respond to the outage.

Print reference

Answers

Answer key.

B · Controlled load changes need a validated owner and safe fallback.
A · Smart-grid deployments are critical infrastructure, so reliability, safety, latency, and security shape every design choice.
B · PMUs measure grid conditions, and WAMS brings the readings together across sites.
D · A meter can send a last-gasp message so the utility can locate and respond to the outage.