Establishing a Pipeline GIS - Developing a Data Collection
Strategy Kevin Miller
Summit Midstream Rockies GIS Technician
Summit Overview • Growth-oriented midstream company focused on developing and
acquiring strategically located midstream infrastructure in unconventional resource basins.
• Own and operate approximately 2,660 miles of natural gas and crude oil
gathering pipelines
• Headquartered in Dallas, TX • Operations
• Piceance Basin – Western CO • Niobrara Shale – Northern CO • Barnett Shale – Dallas-Fort Worth, TX • Bakken Shale – North Dakota • Marcellus Shale – West Virginia
• Two acquisitions totaling 1,700 miles of pipeline in the Piceance Basin
• Acquired two GIS databases with
overwhelming amount of centerline inaccuracies and very limited attribute data
• Outdated / inaccurate field maps • Lack of GIS support and
anticipated growth prompted Summit’s need for a GIS Tech.
A Need for GIS Support
Importance of an Accurate GIS Pipeline Database
• One Call Coverage to Prevent Line Strikes • Engineering and Modeling • Field Efficiency • Pipeline Mileage • Land Team / ROW • Regulatory • Business Development Decisions • Strategy / Planning • Cannot Share Inaccurate Data
Original Pipelines Corrected Pipelines
Original Pipelines Corrected Pipelines
Original Pipelines Corrected Pipelines
Original Pipelines Corrected Pipelines
Challenges • Existing Gathering System (50+ years old)
– Work with what is handed to you – Unknown data source
• Time Frame / Consumption • Dissecting the job books • Choosing a Data Model • Data collection limitations on re-survey of buried pipeline • Conflicting information from operators
Correcting and Populating the Databases • Phase 1 (What do we have and where is it?)
- Manually correct all centerline inaccuracies - Populate all pipelines with name and correct diameter - 2D to 3D using a DEM for more accurate pipeline lengths
• Phase 2 (Additional / Offline Pipeline Equipment) - Identify all valve yards and in-line block valves for ER concerns - Identify launcher / receiver locations for pigging operations - Intersect roads and streams layers with pipelines to establish crossings/bores
• Phase 3 (Attribute Data) - Alignment Sheets - Job Books - As-built Files - Operators
Correcting and Populating the Databases • Phase 4 (Re-survey / Data Collection)
– Trimble GeoXH6000 • Centimeter Accuracy • Floodlight Technology • GLONASS and GPS • Wireless Connectivity • 5 megapixel camera
– Field-verify centerlines (prioritize by confidence level) – Collect all missing valves, launchers, receivers, and meters – Data Dictionaries used on re-survey helped define Summit’s data collection
standard moving forward.
Why Use a Data Model?
• Trusted Source of Information • Improves Data Quality and Reliability • Regulatory Issues • Accurate Data Sharing
Data Model Creation – New Construction
Alignment Sheets + MTRs + As-built Documents + Operator’s Knowledge + Data Dictionaries + Wish List
= “SUMMIT 1.0 Data Model”
Sharing Our GIS - Paper Maps
Sharing Our GIS - Paper Maps
Web Map Demo / Video
Something Out of Nothing - Original Attributes • Diameter • Length • Name
Something Out of Nothing - Corrected Attributes • Diameter • Length Feet • Length Miles • Name • Wall Thickness • Grade • MAOP • HTP • Coating • County • AFE Code
New Construction
Segment Attributes • Diameter • 3D Length • Wall Thickness • Grade • Coating • Begin Measure • End Measure • Mill Test Pressure • Heat # • Joint # • Slope
