1. AGA MAOP Document Review / PODS Implementation
January 17, 2012

2. Company Overview
Atmos Energy serves 3.2 million customers in 12 States
Majority of transmission pipe located within state of Texas in 2 operating divisions
Atmos Energy Pipeline division contains 6,600 miles of transmission pipeline
Atmos Energy Distribution division contains 28,000 miles of distribution main
400 miles of >=20% SMYS 2

3. Service Territory

4. MAOP Documentation Get the plan together
Key documents to consider assembling
Hydro tests
Mill Specs
Inspectors logs
Records location and form (paper or electronic)
State specific requirements
Considerations for volume and location of records in planning
Considerations for staging efforts Class 3 and 4 and HCA’s in class 1 and 2

5. MAOP Documentation Get the documents
Central Archives
Approximately 60,000 boxes in Archives
One Archive company, four different warehouses
Box descriptions / Inventory system
Field Records
50+ field offices
Some contain MAOP related records
Other records
Rate Case filings
Federal Power Commission certificate of public convenience filings 5

6. MAOP Documentation Inventory and analyze
Inventory considerations
Are records accurately described in the archive system?
Should you update descriptions?
Do you retain all documents reviewed?
Scanning considerations
Scan records at beginning or end of the process?
Do you scan?
GIS/PODS
Integrate scanned documents to pipe via GIS 6

7. Major Integrity Program Elements
PIM
Data
Gathering
Threat
Identification
Risk Ranking
Assessment
Remediation
Feedback
Re-
MOC
Data from many sources
Data belongs to all of us
Departments Need To Share Data

8. PIM Need for Central Data
CFR 192 Subpart O requires data collection & integration
ASME B31.8S data integration / analysis
Integrate & Align Different Data Sources
Align data by pipe segment along centerline by station plus
Analyze Assessments: Collect, Store, Compare
Integrate Assessment Results with Physical, Operational and Maintenance Data
Efficiently Collect Integrity information
Collect Threat & Risk Data - Efficiently and As-Needed
Improved HCA monitoring and analysis 8

9. Data Sources Central Data Compliance Records CP Data
Inspections
Patrols
Surveys
Leaks
Incidents
Subject Matter Expert
Land Use
Soil
Customers
Response Time
Environment
Central
Data
SCADA
Gas Measurement
Gas Quality
Encroachments &
Damage Data
Compressors
Valves
Pipe Attributes
Data Alignment
Analysis
Remediation
P&M Measures
Risk Rank
Sheet Gen
Integrity Assessments
Geographic
Information
System
Direct Examinations
Repairs

10. Data Sources
AutoCAD Extended Data Extract for Pipe Centerline and Attributes
In-house Compliance Apps for Leak, Encroachment, Survey, Patrol Data
Cathodic Protection Database
Excel or Access Tables
Field Input for HCA, Topography, etc
Identified Site Data, Threats
Assessment Plan, Assessment Methods
Assessment Results
Excavations, Repairs
Flow & Pressure data
Gas Quality data

11. Data Integration Challenges
Most Data Sources are NOT Pipe Position Aware
Naming conventions not consistent
Moving spreadsheet information into databases
Formatting data for risk evaluation
Alignment of assessment surveys with GIS data
Graphical presentation of assessment results
Identification of potential threat interaction
Identification of preventive and mitigative measures
Comparing assessment results
Alignment of compliance data with GIS

12. What is PODS? PODS = Pipeline Open Data Standard
Open data standard for managing linear referenced transportation pipeline systems
Industry Organization of Pipeline Companies, Contractors & Vendors
Database Template, Not Software, In SQL or Oracle
PODS Can Be Alternative or Addition to Central Pipeline GIS for Data Storage and Integration
Standardized Reference Pipeline Range and Point “Events”

13. More About PODS
Widespread industry supported initiative (standard model)
Collective experience pipeline companies, vendors, contractors
Flexibility to select technologies from multiple vendors without need to rebuild/re-structure data
Pipeline Open Data Standard
Non-profit pipeline trade association
Industry driven, independent database modeling initiative
PODS is an Open Data Structure that
Encompasses requirements of pipeline industry (both gas and liquids)
Provides basis for industry data and data exchange standards
Atmos Energy is implementing PODS 4.02 with Oracle and Intrepid ™ 3.0 as the PODS Editor
Enables standards-based GIS implementation

14. Key Implementation Issue
Transmission Pipeline PODS Events
HCA (2 Records)
Class Location (2 Records)
External Coating (2 Records)
Wall Thickness (3 Records)
Pipe Grade (4 Records)
Segmented Records (12)
Pipe Size
Date of Installation
Wall Thickness
Grade
External Coating
Joint Type
Seam Type
Pipe Joint Coating
Class
MAOP
HCA
Etc….

15. PODS Data “Layers” - Pipeline operator, pipeline system
- Pipeline centerline
- Control and stationing
Pipeline Routing
- Pipe segments, specifications
- Valves and other control facilities
- Fittings and appurtenances
- Cathodic protection
- Coatings, pressure tests, etc.
Pipeline & Specifications
- Class locations
- HCAs and HCA Ranges
Class Locations & HCAs
- Dynamic risk segments
- Risk assessment ranges
Pipeline Risk
IM Assessment/Remediation
Direct assessments
In-line inspections
- Assessment results
- Anomalies
- Verification/remediation
Compliance
- Patrol/inspection activities
Maintenance & Operations
- Maintenance activities
Pipeline Incidents
- Leaks, ruptures, failures and non-leaking damage
Encroachment
- DOT structures and identified sites
- Pipeline encroachments including crossings

16. Intrepid™ – Maintain and View PODS Data
“Desktop” Application
Atmos Energy’s PODS interface
App created & maintained by Coler & Colantonio (C&C)
PODS & Intrepid are “Enterprise” systems
Based on users role - Data loaded, reported or viewed 
Design of tables and interfaces includes a variety of different systems
Some employees - Authority To Enter or Revise Data  

17. PODS Implementation
June, PIM Effectiveness Study started by C&C March 2010 – PIM study report finalized May, 2010 – Approval for PODS implementation June, 2010 – First template for migration to PODS ready October, 2010 – First training for Atmos Energy December, 2010 – Phase 1 PODS in Production (Hosted) March, 2011 – PODS data used for Risk Assessment (American Innovations RIPL application) December, 2011 – Database/software installed Company Servers February, 2011 – PODS to be in production on Company servers

18. PODS Implementation Plan

19. PODS Data Centralized / aligned data Source data for:
Integrity assessment results
Excavations
Integrity repairs
Subject matter expert data
Assessment plan
Automated updates from other source databases:
Cathodic Protection
Leaks
Exposures
Surveys / Patrols
Gas flow / pressure / quality

20. PODS Benefits Visual presentation of aligned data
Centerline data on aerial imagery
Risk / Integrity Sheets
Improve risk analysis process
Use of available geographic data
Soil
Fault lines
Crossings
Anomaly analysis
Reporting
Compliance reports
Pre and post assessment reports
Ad hoc reporting

21. Data Currently in PODS Pipe & Features Operations – Compliance Related
Transmission Pipeline Centerline & Attributes
Class, HCA, Coating, Install Date
Pressure Tests, Material Attributes, Valves, Casings
Partial List: Taps, Crossings
Operations – Compliance Related
Leaks, Encroachment Records
Cathodic Test Points
Integrity Related
HCA History, Subject Matter Expert Data
Risk score results
Other
Aerial photographs

22. Data to be Loaded PODS MAOP Documentation Integrity Assessment Results
Integrity Dig Reports
Excavation Reports
Crossing / Exposures
Measurement Database
Gas Quality Database
Maintenance Pigging Reports
Liquid / Solid Analysis
Corrosion Coupons
ROW Data

23. Future Enhancements Web based PODS data viewer Application Interfaces
Link to Document Management Server
Updates from Work Management Database (CMPlus)
Updates from CP Compliance DB (CPDM)
Updates from Encroachment Database
HCA / Class Location analysis
Alignment and Risk / Integrity Sheet Generation
Field Data Collection
Electronic collection of excavation data
Link to PODS database
Hydraulic Modeling

24. Some Learning Points for Atmos Energy
“C&C” as Knowledgeable Consultant Saved Time
PODS table extensions maintained compatibility
Tables were added to fit “current state” data compilation formats (SME, CP TP)
Try to keep key data providers & users informed
Data scrubbing takes time
Some “New” Tables were Re-designed before Use
Add “Anomaly” table & Modify ILI tables to suit assessment need

25. Intrepid Screen

26. Pipe Facility Details Event List

27. Thank You