A storm rolls through and 400 meters on one feeder go quiet at once. You are in the control room with six systems on the wall: SCADA, OMS, DMS, ADMS, AMI, and GIS. Before reading on, predict it: which one do you open first to see the outage as an outage and start managing the restoration?
You open the OMS, the Outage Management System. It takes the trouble calls coming in, the last-gasp pings from those 400 meters, and any SCADA trips, lays them over the network model, and predicts the single upstream device that most likely failed. That is the job no other system does: turn scattered signals into one outage you can dispatch a crew on and track until the lights come back.
The other five each own a different slice. SCADA monitors and remotely controls field devices, OMS manages outages, DMS analyzes and optimizes the network, AMI reads the meters, and GIS holds the map of record. SCADA is the live telemetry and control link to breakers, reclosers, and substation equipment. DMS (Distribution Management System) runs the analysis on top of that data: voltage and VAR optimization, load balancing, switching plans.
ADMS is not a seventh tool. It is SCADA + DMS + OMS converged into one platform so operators stop hopping between three siloed screens and instead work from a single shared model of the feeder. When a vendor says ADMS, that is the convergence they mean. It is not tied to any one manufacturer; treat it as the architecture, not a brand.
AMI (Advanced Metering Infrastructure) is the smart-meter network at the edge of the system. It collects usage, voltage, and outage data from every service point, but on a meter cadence (minutes to hours) and for a different purpose than SCADA’s sub-second device telemetry. Do not confuse the two: AMI watches consumption at the customer, SCADA watches and controls equipment on the feeder. Underneath all of it sits the GIS, the geographic system of record for every pole, conductor, transformer, and switch, and the connectivity those other systems read to know what feeds what.
Reading a single-line diagram is the first step to writing a defensible RFQ. DistroForge report editions apply that same fluency to real bid packages: supplier capacity, lead times, and spec language that survives an OEM’s substitution clause.