PODS Next Generation A Commitment to PODS as a Standard and a Transformed Data Model August 23 & 30, 2016 KATHY Welcome and introduction to Forum-Kathy Mayo. Introduce PODS leadership Welcome to all in the room and on the webinar Intro PODS Next Generation Co-Chairs Intro Dan F. and Jen. PODS Association commitment to good communication with Members This is our 5th webinar We try and offer 2 different dates and times for a topic/session Pass to BUDDY for SLIDES 2-4

Mission Develop and advance global pipeline data standards to support efficient data management and reporting for the oil and gas industry BUDDY This is our Mission

Vision Become the recognized global leader in pipeline data standards and best practices through collaboration with our member community and the development of pipeline data models designed with open specifications BUDDY PODS Association vision is to …… read it

Our Goals Products Advocacy Strategies Goal 1 PODS Core Goal 2 Interchange specs Goal 3 Stakeholder engagement Goal 4 Standards implementation guidance Goal 5 Governance Goal 6 Grow membership Products Advocacy Strategies BUDDY PRESENT Quick review Goals and how they relate to Next Gen – especially Goals 1 and 2 The Board adopted six goals as part of its strategic plan. PODS 6 goals are organized three categories: Our Products (PODS Data Model), -- Goals 1 and 2 relate directly to Next Gen Advocacy (communication and guidance), delivered through a variety of methods Strategies (around PODS organizational Needs) Goal three is about how we communicate with members (and other stakeholders). PODS has increased the level of engagement and how we engage with members. This webinar is a good example. Hand over to Next Gen Co-Chairs, Peter Veenstra of TRC

Next Gen Drivers Challenges in Current Model Next Gen Workgroup Drivers Lack of Performance Difficult to Implement Lack of Agility Multiple standards to choose from Core Documentation lacking Disparity between vendor solutions Strategic Plan Member Concerns Technology Changes PETER Next Gen, PODS Association is addressing what we’ve heard from you, Member Concerns. These have become the drivers Some of the drivers of the Next Generation scope (development) include: READ from Slide

PODS Board is Committed to Change Lessons learned from users of the Standard Exponential growth of data Expanded regulatory reporting requirements (PHMSA and FERC) International partners Changes in technology PETER Commitment to PODS As A Standard and A Transformed Data Model The PODS Board of Directors has chosen to transform the PODS Pipeline Data Standard, going forward. This directive came about after thorough consideration of lessons learned from PODS Association members using the Standard, the exponential growth of data, expanded regulatory reporting requirements (PHMSA and FERC), an increased call for support among international industry partners, and changes in relevant technologies.

PODS Next Generation "PODS Next Generation is defining a standard that is easy to understand, simplified, rigorously documented and makes use of current technology. It is important for pipeline data consistency and interoperability. How PODS is implemented makes a difference. This is what we are working toward in PODS Next Generation." --Peter Veenstra, Co-Chair of the PODS Next Generation Work Group and PODS Association Board member PETE V present…

Benefits of Next Gen Transformation Achieve greater agility to build and extend the data model Interoperate Share data Intuitive framework Well-defined rules Performance optimized BUDDY Benefits of Next Generation Data Standards Transformation Achieve greater agility to build and extend the data model, responding to new business requirements. Interoperate through standard data models and consistent application interface. Share data within and between organizations using well defined data exchange specifications. Intuitive framework includes clear and concise guidance and specifications. Well-defined rules to document content, structure, and editing of data. Performance optimized for management of bulk loading, reroute, inspection data and history. FROM OLD SLIDE _ APRIL FORUM: Agility to respond to new requirements Interoperate through consistent application framework Share data between organizations Rapidly build and extend the data model Prescribe data content, structure, and editing results Optimize performance

Next Generation Standards Design Principles Design for the Future Solid Core Coupled with Flexibility and Agility Support Time and History Support Location and Spatial Representation Support Interoperability Easy to Understand BUDDY

A Transformed PODS Model Clear guidance to ensure consistency across implementations Clear guidance for data maintenance in a PODS database Modernized schema, data loading and QA/QC tools Best practices PETER

A Transformed PODS Model Re-engineered PODS data model Defined set of core tables primarily designed as the system of record for location of pipeline assets Clearly documented support the deployment of the model Interoperability and data sharing enabled Enhanced standards for governance and communication PETER The next version of the Pipeline Data Model will not be another incremental release, but will be entirely restructured with major improvements and new approaches, as follows: Re-engineered PODS data model Defined set of core tables primarily designed as the system of record for location of pipeline assets Clearly documented to support the deployment of the model Interoperability and data sharing enabled Enhanced standards for governance and communication

A Transformed PODS Model One Logical Model – Multiple Implementation Patterns Geodatabase Relational Database Data Exchange Esri APR-Compatible Linear Reference System Model Data Editing Documentation Domain Management Data Exchange Specification PETER – This solves the difference with PODS relational and esri being different…. Relational Database talking points: - LRS (with spatial types or without) No LRS (with spatial types or without) Esri APR-Compatible Linear Reference System Model: Built-in Linear referencing is compatible….can be realized not only in geo database but also in relational database implementation patterns. Data Exchange Specs: - I can send someone assets, conditions, centerline etc…. In a way they will be able to understand and use.

Strategic Alignment - Review Next Generation aligns with the following PODS Strategic Plan Goals Goal 1 - Core logical data model Goal 2 - Interchange specifications Goal 3 - Communication Goal 4 - Implementation guidance PETER As we said at the beginning of the presentation: Next Gen is supporting these Strategic Goals

Goal 1 Establish an industry-recognized core logical data model and vendor-neutral physical data model with implementation resources Pete—briefly discuss. How far has the group taken this, and what are the next steps (talk about Pipeline Week and the presentations; then completion of Phase 1).

Goal 1 - Outcomes Best Practices in Data Standards & Database Well-defined core Extendable through a modular approach Maximum implementation flexibility, agility and interoperability Implementation Resources Support a wide variety of GIS and relational database formats Enable improved interoperability PETE Best Practices in data standard and database, this includes A well-defined core One that is extendable through PODS modules, and maximum implementation flexibility, agility and interoperability PODS provides Implementation resources Supporting a wide variety of GIS and relational database formats (our templates), and Enable improved interoperability

Conceptual, Logical and Physical Models Abstract Conceptual models convey fundamental principles and basic properties of a system Logical models provide a detailed blueprint for creation of databases, independent of any given database technology Physical models provide a detailed design for a database, specific for a given database platform A physical model is used to create a template which can be used to add and manage data PETER Tangible

WORK in PROGRESS Logical Data Model PETER This shows “proof in the pudding” – work has been done…..work in progress.... Ability to send someone assets, conditions, centerline etc…. In a way they will be able to understand and use.

Steward open-interchange specifications for data sharing Goal 2 Steward open-interchange specifications for data sharing PETER

Open (vendor-neutral) data interchange specifications Goal 2 - Outcome Open (vendor-neutral) data interchange specifications Enable accurate transfer and sharing of pipeline and associated business data and metadata Platforms Software products Systems PETER Open (vendor-neutral) data interchange specifications that enable accurate transfer and sharing of pipeline and associated business data and metadata between different platforms, software products and systems.

Data Exchange Specification WORK in PROGRESS PETER This is an XML spec – we will talk about it in more detail at pipeline week

Next Gen - Near Term Schedule Conceptual Data Model 29 July 2016 – Subset of core for Pipeline Week (Pipelines, Centerlines, Valves) 2 Sept 2016 – Full core Logical Data Model 12 Aug 2016– Subset of core for Pipeline Week, draft 17-18 Aug 2016 – Working Group Team Meeting to Finalize subset of core Physical Data Model and Templates 24 Aug 2016 – Subset of core for Pipeline Week (multiple implementation patterns) 1 Sep 2016 – Data Exchange Specification (DES) for subset of core Data Editing Documentation 2 Sept 2016 - Draft Next Gen Demos/ Presentations Complete 15 Sept 2016 PETER Speak to each of these Feedback during pipeline week will help inform how schedule progresses after 21 Sept 2016 – 8:30-10am Plenary with Demos 22 Sept 2016 – 8:00am – Deep Dive into Next Gen

Next Gen – Looking Forward Completed Core Module Strategy Schedule will be rolled out after Pipeline Week – Website Newsletter LinkedIn PETER What’s next?

Learn More at Pipeline Week! Conceptual Model Logical Model Physical Data Model Data exchange specification Demonstration Documentation Sign up now! Attend in person OR webcast.

PODS Next Gen KATHY – Wrap up and make a plug for Sponsorships….