Pipeline Asset Management and Workforce Optimization Speakers: David Supp Andrew Karns Jesse Everling
Who We Are EQT Corporation (EQT) EQT Midstream Pipe: 11,670 miles Gathering: 10,900 miles Equitrans: 770 miles EQT Production 5.2 TCF of proved reserves 32 TCF resource potential Equitable Gas 276,500 LDC customers
Midstream EAM Project Charter Business Objectives Manage business growth in a controlled manner Improve operator efficiency- miles of pipe/operator Standardize work processes across all operational districts Reduce operating costs Safety Strategic Roadmap Consolidate disparate spatial data into a central geo-database Implement an EAM solution that derives master data from the GIS Integrate EAM to a user friendly mobile data collection system Utilize and incorporate currently implemented GPS technology Provide metrics around realized field productivity
Project Milestones Scope Definition Which assets would we manage in EAM? What is the authoritative system for asset creation, master data, etc? What is the set of standard work orders? What data is important to collect? GForms Pipeline Pilot January 2010 GForms standard forms against a temporary master data database Maximo Project Kickoff - February 2010 Build integration between ESRI and Maximo Clean geospatial & attribute data (11,670 miles of pipeline across 4 states) Data mapping of ESRI domains, features, and attributes to Maximo Assets Identify operator route polygons, department and district boundaries Build integration between Maximo and GForms Integrated System Go Live- September 2010
EQT s Pipeline EAM Solution Integrity Application EAM Application Data Manager Facility editor Above ground surveys Inline inspection data Alignment and construction sheets Survey Manager ILI analyses Excavation planning AVL System GPS Data Real-time location NMEA Feed Work Orders GPS Data Assets and Attributes Assets Sched. WO WO Result Linear Work Orders Pipe Inspections Valve Inspections Leak Survey Patrol Leak Investigations Corrosion Inspection Coupon Analysis CP Tests Drip Blows Dig packages Risk Manager Risk assessment HCA analysis DOT Class analysis Integrity & Risk GIS APDM Pipeline Asset DB Pipelines Point Assets Enterprise Asset Management DB Compression Work Orders Shutdown Planning Station Daily Checklist Relief Valve Test Engine maintenance SPCC inspections Gas Meters Meter Inspections Meter Calibrations Field Survey Data GPS Surveys Feature Attributes Mobile GIS Supply Chain Inventory Purchasing Warranty Projects / AFE Scheduling Employees / Quals Routes / Crews Time Capture Work Scheduling Mobile As-Built Maintenance Costing Resource Leveling
GForms Technology Overview GForms Client A user accessible platform to gather consistent data in a connected or disconnected environment Easy to use interface for field or office use Centralized Data Repository GForms are stored as entered by user as a complete report Open and accessible data standard for integration within enterprise Full audit trail for each GForm Workflow & Approval Process GForms can be routed for approval before entering the system Ability to automate notifications Dashboards Visualization of GForms progress throughout the organization
GForms Designer Designated users have the ability to build GForms templates Easy to use forms designer Templates are stored in a central repository and versioned Templates can mirror workflow paths
GForms Portal Central location to review all GForms Ability for users to Check In/Out reports Full Report History for Audit Tracking Ability to Query GForms based on report criteria Dashboards to give overview of report statuses and progress
GForms Future Enhancements Advanced integration with mobile maps ArcGIS Mobile 10 Google Earth & Maps Enterprise Tools to help organize and prioritize work Enable operators to plan their work by assigning a planned completion date Workflow Manager Simplify the routing of GForms between systems Form Factors New mobile environments (ipad, iphone, tablet PC)
GForms: End User Experience User Inbox
GForms: End User Experience Work Order
GForms: End User Experience GPS Integration Roadmap
GPS Insight Route Analysis
GPS Insight Route Analysis
The Pain Relying on GIS as a central repository for Maximo Significant effort required to cleanup legacy data New data quality standards can slow work of GIS Analysts What is your primary key that links the systems? Change Management and Company culture How do we name our lines, drips, valves, etc? Migrating from ad-hoc / unplanned to scheduled work Adoption of defined Routes versus divide and conquer approach Agreeing on what technology would aide productivity Choosing mobile form factors Connected vs. Disconnected scenarios Traditional work routes vs. Optimized/Weighted scheduling
The Pain continued Managing integration between GIS and EAM Process Line headers result Implications / Notes Accepted Lineheaders 139 meets all criteria (valid Person Group, linetype, linename, opertionalstatus) Rejected Lineheaders 826 510 Inactive, 223 Invalid LineType, 89 Invalid Route, 4 Duplicate Descriptions Missing Line headers 0 Requires research. Either deactivate Maximo asset or reassign to a new LineHeaderEventID. Changes to Line Type 3 Rare Event. Requires manual action. Changes to Line Name 18 12 were updated, 6 require investigation. Need to change PM descriptions. 39 changes from one Valid Route to another Valid Route in same Location (Completed) 8 changes require a Location Move (Manual change required) Changes to Routes 101 Changes to Operational Status 3 Note that Route Changes can result in a Location or Site Change for the Line. Changing Line routes and locations will not impact Route and Location of Children. Potential for active children to be associated with line. Requires manual action. Should children be deactivated or moved to another parent? How do we address pending transactions? Changes to Line Length 47 Captures changes > 10 feet.
The Payoff Sustainable geospatial data structure Greater audience can view data in GIS, including operators Operators are contributing and updating feature attributes Single source of spatial data stream is shared by Compliance, Operations Planning and Land groups Establishing baseline metrics to track operator efficiency Drive time, miles drive, route efficiency Wrench time, average completion time of work types Meeting schedule and compliance based work types Ability to optimize routes Increased operator work coverage Pipeline mileage, feature count, workload balance tracked by route Track driving patterns against available work
Pipeline Operations Dashboard
Questions and Answers David Supp- Director IT, EQT Midstream Andrew Karns- Sr. Systems Analyst, EQT Midstream Jesse Everling - Lead Application Developer, Global Information Systems