[{"content":"I write about how utilities actually make digital grid systems work in practice — especially where GIS, ADMS, OMS, DERMS, planning, field operations, and enterprise systems meet.\nMy background is in utility GIS, ADMS integration, network modeling, and digital grid transformation. This site is where I share practical perspectives on architecture, data readiness, system ownership, and the operational realities behind utility modernization efforts.\nWhat I write about Topics on this site include:\nGIS as the network model at the center of utility operations ADMS, OMS, and DERMS integration Data readiness for operational systems Utility network modeling and system architecture Engineering, planning, and field workflows Asset, customer, and meter data relationships What works — and what fails — in real utility transformation programs Why this site exists A lot of utility technology content is either too abstract, too vendor-driven, or too disconnected from the operational realities utilities deal with every day.\nThis site is meant to be different.\nThe goal is to publish clear, practical writing for utility leaders, GIS and ADMS teams, architects, operators, and digital grid professionals who want a more honest view of what it takes to make these systems work together.\nConnect If you\u0026rsquo;d like to connect about GIS, ADMS, OMS, DERMS, utility architecture, or digital grid modernization, feel free to reach out.\nLinkedIn: Joseph Marsh on LinkedIn Email: joemarshgis@gmail.com Subscribe If you want new posts by email, subscribe below.\nIf you prefer RSS, you can subscribe here:\nRSS feed for ADMS Readiness Posts feed If you want new posts by email, subscribe below.\nA note on perspective The views on this site are based on real-world experience across utility GIS, operational integrations, and grid modernization work. The focus here is not on abstract theory — it is on the patterns, decisions, and data issues that shape how utility systems actually perform.\n","permalink":"https://www.admsreadiness.com/about/","summary":"\u003cp\u003eI write about how utilities actually make digital grid systems work in practice — especially where GIS, ADMS, OMS, DERMS, planning, field operations, and enterprise systems meet.\u003c/p\u003e\n\u003cp\u003eMy background is in utility GIS, ADMS integration, network modeling, and digital grid transformation. This site is where I share practical perspectives on architecture, data readiness, system ownership, and the operational realities behind utility modernization efforts.\u003c/p\u003e\n\u003ch2 id=\"what-i-write-about\"\u003eWhat I write about\u003c/h2\u003e\n\u003cp\u003eTopics on this site include:\u003c/p\u003e","title":"About"},{"content":"Utilities often talk about “integrated systems,” but in practice most integrations already revolve around one platform: GIS. Not as a mapping tool—but as the operational system of record that defines how the grid actually exists.\nThe reality behind the diagram The diagram in this post is closer to how utilities actually operate than most vendor slideware:\nflowchart TB GIS[\u0026#34;GIS\u0026lt;br/\u0026gt;(Authoritative Network Model)\u0026#34;]:::center OPS[\u0026#34;Operations\u0026lt;br/\u0026gt;OMS • ADMS/DMS • SCADA • Field\u0026#34;] --\u0026gt; GIS GIS --\u0026gt; PLAN[\u0026#34;Planning \u0026amp; Analysis\u0026lt;br/\u0026gt;Engineering Studies • Distribution Planning\u0026#34;] GIS --\u0026gt; ENT[\u0026#34;Enterprise \u0026amp; Customer\u0026lt;br/\u0026gt;EAM • CIS • AMI/MDMS • DERMS\u0026#34;] OPS -. \u0026#34;Operational feedback\u0026#34; .-\u0026gt; GIS PLAN -. \u0026#34;Planning updates\u0026#34; .-\u0026gt; GIS classDef center fill:#01696f,stroke:#0c4e54,color:#ffffff,stroke-width:2px; GIS is in the center as the system of record for the network model. OMS, ADMS, SCADA, DERMS, field, planning, asset, CIS, and AMI/MDMS all radiate out from that center. A few systems have dashed feedback loops back into GIS, where it makes sense to feed data and results into spatial and engineering analysis. The architecture only matters if it helps people operate the grid in real time. For leaders in OMS, ADMS, and operations, the point of putting GIS at the center is not “better diagrams” — it is better situational awareness, decision support, and operational coordination.\nIf you treat this as just another “IT architecture picture,” you miss the point. It’s really a statement about data ownership and operational responsibility.\nWhy GIS ends up in the middle Modern utilities run a complex ecosystem of systems:\nOMS ADMS / DMS SCADA DERMS Engineering analysis tools Distribution planning tools Asset management (EAM / APM) Mobile workforce / field mobility / work management CIS AMI / MDMS On paper, you can draw these as neat layers. In reality, they all depend on the same foundational data: the distribution network model. That model lives in GIS.\nAt a practical level, GIS is what ties the physical system to the digital one. It is where substations, feeders, devices, and connectivity become a model that downstream systems can actually use.\nGIS is the only place where all of these coexist in one model:\nConnectivity – how assets are actually connected. Topology – upstream/downstream relationships. Attribution – phase, voltage, conductor, device details. Spatial accuracy – where assets physically exist. Asset identity – stable IDs that other systems can reference. No other system maintains all of that together. As a result:\nOMS consumes GIS connectivity and device modeling. ADMS depends on accurate phasing and feeder models. SCADA references GIS asset IDs and locations. DERMS needs spatial and electrical context. Engineering and planning tools rely on GIS for as‑built conditions. Field systems synchronize work against GIS features. Whether intentional or not, GIS becomes the hub the rest of the ecosystem orbits around.\nReading the diagram like an operator, not an architect The diagram breaks that hub‑and‑spoke reality into three views that execs and program leaders can use:\nOperations – OMS, ADMS/DMS, SCADA, field/work management\nSolid arrows from GIS show where those systems take their model and context from. Cross‑links between OMS, ADMS, and SCADA reflect how those systems have to agree on the same network model to support switching, FLISR, outage prediction, and DER operations. Planning \u0026amp; analysis – engineering studies and distribution planning\nThey pull the as‑built model from GIS, run studies, and inform future changes. Their results can feed back into GIS when planners modify how the network should be built or operated. Enterprise \u0026amp; customer – EAM, CIS, AMI/MDMS, DERMS\nEAM tracks the lifecycle of the same assets GIS locates and connects. CIS and AMI/MDMS rely on accurate customer‑to‑meter and meter‑to‑network relationships. DERMS needs the GIS/ADMS model to understand where DERs really sit on the grid. Field systems are one of the clearest reminders that the model has to work outside the control room. If crews cannot trust the location, connectivity, or asset context coming from GIS, the rest of the integration stack starts breaking down quickly.\nThe dashed arrows back into GIS—from OMS and ADMS in your diagram—represent feedback loops where it actually makes sense to bring data and results back into the spatial model:\nOutage and event history, so you can analyze where the system is fragile or recurring problems cluster. Switching and study results, so you can do spatiotemporal analysis of how the network is operated versus how it was designed. That’s where executives and directors start seeing value beyond “integration for its own sake”: you get a model that supports continuous learning about the system, not just a one‑time ADMS go‑live.\nWhere utilities get into trouble The architecture itself is not the problem. Utilities run into trouble when GIS is treated as:\nA passive map. A downstream reporting tool. “Good enough” for operations. Common failure patterns include:\nSelf‑intersecting or disconnected lines. Missing or invalid phase designation. Invalid or missing operating voltage. Inconsistent feeder boundaries. Null or duplicate facility IDs. Those issues don’t stay in GIS—they show up as:\nADMS model failures and bad power flow results. OMS prediction inaccuracies. SCADA mismatches and suspect alarms. Field crews not trusting what they see on the screen. Longer restoration times and more operational risk. What actually works in practice Utilities that succeed with ADMS, DERMS, and grid modernization generally do three things:\n1. Treat GIS as a production system GIS changes are controlled, validated, and aligned to operations, not edited casually. There is a clear owner for “what is the network model?” and how it gets updated. 2. Perform real data readiness assessments Before ADMS, DERMS, or OMS upgrades they deliberately assess:\nNetwork connectivity and topology. Phase and voltage integrity. Modeling consistency (devices, conductors, equipment). Attribute completeness for the functions they care about. This is not a one‑time cleanup; it becomes a recurring discipline.\n3. Design architecture around data ownership, not software logos Instead of “everyone owns everything,” they define:\nGIS: authoritative for structure, connectivity, and core attributes. ADMS/OMS/SCADA: authoritative for real‑time states, switching, and control. DERMS and analytics: authoritative for specific optimization and forecasting use cases. Integration flows respect those boundaries. Systems consume and enhance the model—they don’t silently redefine it.\nThe executive takeaway You don’t need another architecture drawing. You need a stronger center.\nWhen GIS is treated as the authoritative network model—and the architecture is built around that reality—every downstream system performs better: ADMS, DERMS, OMS, SCADA, planning, and customer‑facing tools.\nIf your ADMS, OMS, or DERMS initiatives feel harder than they should, the issue is often not the application—it’s the data and ownership model at the center. The diagram isn’t just a technical picture; it’s a reminder to decide, explicitly:\nWhat does GIS own? What does each operational system own? Where do we want feedback loops back into GIS so we can actually learn from how we operate the grid? Those are questions executives and program leaders can act on—without having to debug the diagram itself.\nSubscribe If you prefer RSS, you can subscribe here:\nRSS feed for ADMS Readiness Posts feed If you want new posts by email, subscribe below.\n","permalink":"https://www.admsreadiness.com/posts/2026-01-gis-in-the-center-architecture/","summary":"\u003cp\u003eUtilities often talk about “integrated systems,” but in practice most integrations already revolve around one platform: GIS. Not as a mapping tool—but as the operational system of record that defines how the grid actually exists.\u003c/p\u003e\n\u003ch2 id=\"the-reality-behind-the-diagram\"\u003eThe reality behind the diagram\u003c/h2\u003e\n\u003cp\u003eThe diagram in this post is closer to how utilities actually operate than most vendor slideware:\u003c/p\u003e\n\u003cpre class=\"mermaid\"\u003e\nflowchart TB\n  GIS[\u0026#34;GIS\u0026lt;br/\u0026gt;(Authoritative Network Model)\u0026#34;]:::center\n\n  OPS[\u0026#34;Operations\u0026lt;br/\u0026gt;OMS • ADMS/DMS • SCADA • Field\u0026#34;] --\u0026gt; GIS\n  GIS --\u0026gt; PLAN[\u0026#34;Planning \u0026amp; Analysis\u0026lt;br/\u0026gt;Engineering Studies • Distribution Planning\u0026#34;]\n  GIS --\u0026gt; ENT[\u0026#34;Enterprise \u0026amp; Customer\u0026lt;br/\u0026gt;EAM • CIS • AMI/MDMS • DERMS\u0026#34;]\n\n  OPS -. \u0026#34;Operational feedback\u0026#34; .-\u0026gt; GIS\n  PLAN -. \u0026#34;Planning updates\u0026#34; .-\u0026gt; GIS\n\n  classDef center fill:#01696f,stroke:#0c4e54,color:#ffffff,stroke-width:2px;\n\u003c/pre\u003e\n\u003cul\u003e\n\u003cli\u003eGIS is in the center as the system of record for the network model.\u003c/li\u003e\n\u003cli\u003eOMS, ADMS, SCADA, DERMS, field, planning, asset, CIS, and AMI/MDMS all radiate out from that center.\u003c/li\u003e\n\u003cli\u003eA few systems have dashed feedback loops back into GIS, where it makes sense to feed data and results into spatial and engineering analysis.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg alt=\"Utility grid control room with operators and large wall displays\" loading=\"lazy\" src=\"https://pplx-res.cloudinary.com/image/upload/pplx_search_images/ec0e46fada53e0ecb01ce0756b6d7c70fd69f9fb.jpg\"\u003e\u003c/p\u003e","title":"GIS in the Center: The Architecture Utilities Actually Operate On"},{"content":"Articles A collection of writing on utility GIS, data readiness, and operational system integration.\n","permalink":"https://www.admsreadiness.com/posts/readme/","summary":"\u003ch1 id=\"articles\"\u003eArticles\u003c/h1\u003e\n\u003cp\u003eA collection of writing on utility GIS, data readiness,\nand operational system integration.\u003c/p\u003e","title":""}]