Future-Proofing Midstream Operations with PODS 7 for Esri Utility Network
- May 15
- 2 min read
How a spatial data model turned a midstream operator's GIS from a record-keeping tool into an operational asset.
For midstream operators, GIS has changed from a simple record-keeping tool into the core of safe, compliant pipeline management. To reach this level, many companies need to move away from old relational data models and adopt systems designed for today’s spatial needs.
One of our midstream clients recently made this transition, and the lessons they learned can help any operator thinking about switching to PODS7 and the ArcGIS Utility Network.
The Starting Point
Our client managed their PODS relational database using third-party middleware. They had three main goals: to use a spatial, feature-class-based data model, to perform trace calculations, and to manage the data model themselves in Esri ArcGIS Pro. To achieve this, they worked with Magnolia River and Esri, with each team handling different parts of the project.
Challenge 1: Cleaning Up the Data
The Utility Network needs accurate geometry, and moving from a relational system often reveals problems that legacy systems miss. We found centerline errors, orphaned records, missing or invalid shapes, and unexpected elevation values, and guided the client through fixing each issue. This gave them a solid spatial foundation for advanced network tracing.
Challenge 2: Keeping Pace with New Construction
Our client is building new pipelines, so it’s important for construction data to enter the GIS quickly. We connected their survey database to the new PODS UNET schema and updated the model as needed. This allowed their ETL process to send survey data into the right PODS7 format using Location Referencing tools. Now, new construction data is available for reporting almost immediately.
Challenge 3: Unifying Regulatory Reporting
With the old relational model, it was hard to share regulatory status between business units. The new PODS7 UNET data model includes the PODS Regulatory module, which records regulatory status, jurisdiction, and mileage in one spatial source. Now, federal and state reports, including PHMSA submissions, are generated directly from PODS7 UNET, keeping integrity management information and mileage in sync.
There’s also a practical benefit. With regulatory data available on web and mobile maps, field teams can quickly see the jurisdiction at an incident site and contact the right emergency response officials.
The Bigger Picture
Switching to PODS7 and Utility Network changed our client’s GIS from a record-keeping tool into a dynamic operational asset. Now, they manage it themselves in ArcGIS Pro, with the spatial accuracy that modern pipeline operations need.
If your team is considering a legacy PODS migration or wants to get more out of the ArcGIS Utility Network, we’d be happy to talk.
