PODS Lite version 1.1. Executive Summary

Transcription

1 PODS Lite version 1.1 Executive Summary Introduction Since 1998, the Pipeline Open Data Standard (PODS) Association has been focused on providing a comprehensive, open, vendor-neutral, highly scalable, and proven enterprise database architecture focused on increasing the safety and integrity of pipelines worldwide. The PODS Association announces the second release of PODS Lite, version 1.1. PODS Lite is an abbreviated version of the full PODS Pipeline Data Model 7.0, allowing pipeline industry professionals to explore how implementation of this recognized and established data model may improve their pipeline data management, integrity and risk management, operational and regulatory reporting activities. Pipeline operators and other interested parties not yet using the full PODS Pipeline Data Model, along with Association members not yet familiar with the PODS data standards, are encouraged to use PODS Lite to evaluate the PODS Pipeline Data Model capabilities and value. For existing Association members and users of the full PODS Pipeline Data Model, PODS Lite provides an opportunity to preview the Associations Next Generation Data Model. The PODS Association offers the PODS Lite Data Model version 1.1 free of charge to anyone wishing to evaluate and understand how the PODS Pipeline Data Model can support their needs.

2 Table of Contents Introduction What Is PODS Lite? PODS Next Generation What s Included in PODS Lite version 1.1? PODS Association Overview PODS Lite v. 1.1 (.zip Package Contents) PODS LITE V 1-1 USER DOCUMENTS.ZIP PODS LITE V 1-1 GEODATABASE FILES.ZIP PODS LITE V 1-1 DATA DICTIONARIES - ALL.ZIP PODS LITE V 1-1 SCRIPTS ALL FLAVORS.ZIP PAGE 2 of 10 PODS LITE VERSION 1.1

3 What Is PODS Lite? PODS Lite is a subset of the full PODS Pipeline Data Model including many of the essential tables of the full Data Model. The specific list of essential tables provided with PODS Lite is described in more detail below. The PODS Association is currently developing a new PODS Data Model Version 7.0. This new version will be a transformational not an incremental change from the current Data Model Version 6.0. This transformation of the PODS Data Model is being conducted under the PODS Association s Next Generation initiative. As such, PODS Lite also operates as a preview of the new PODS Pipeline Data Model Version 7.0, being developed as part of the PODS Next Generation initiative. PODS Lite version 1.1 is being made available in the Esri Geodatabase format, RDBMS format, and the OpenSpatial Format. It does NOT require Esri APR. PODS 7.0 and PODS Lite support Esri APR without any modification to either data model. The Esri geodatabase version, referred to as PODS Lite Geodatabase XML Workspace APR, will work with Esri s ArcGIS for Pipeline Referencing (APR) extension. This is possible because the Esri APR linear referencing extension will work with any data model that meets certain requirements; the PODS Pipeline Data Model Version 7.0 and PODS Lite meet these requirements. The PODS Association and Esri have worked collaboratively on the development of PODS Lite for APR. PODS Lite Overview Free for Use by All PODS Lite is available to both PODS Association members and non-members. Both are encouraged to use PODS Lite to understand how the PODS Pipeline Data Model works and what value it provides. Subset of the Full Data Model PODS Lite is a subset of the full PODS Pipeline Data Model. A set of essential tables is provided, allowing users to preview the PODS linear referencing, asset and operational tables. Preview of PODS Version 7.0 PODS Lite is a preview of PODS Pipeline Data Model Version 7.0, scheduled for release in Preview of Modernized PODS Standards PODS Lite reflects a major re-design and modernization of the PODS Pipeline Data Standard taking place as part of PODS Next Generation initiative. Available for Multiple Platforms PODS Lite is being made available in Esri geodatabase format for use in Esri s ArcGIS for Pipeline Referencing (APR) extension, as well as other GIS and RDBMS platforms. PODS Lite allows pipeline operators to take advantage of both Esri s APR and the PODS Pipeline Data Model. Pipeline operators will realize significant value when using APR s linear referencing and data management tools along with the PODS Lite Data Model. PODS 7.0 and PODS Lite DO NOT REQUIRE Esri s APR, although they support Esri APR without any modification to either data model. PODS Lite and PODS 7.0 are not specific to Esri or the Esri APR extension to the ArcGIS Platform. PODS Lite v 1.1 supports implementation in additional relational database management system (RDBMS) and geographic information system (GIS) environments. PODS Lite comes in many flavors. PODS Next Generation The PODS Association s Next Generation, or Next Gen, initiative is focused on a complete re-design and modernization of the PODS Pipeline Data Model. The re-design of the PODS Pipeline Data Model is driven by PODS Association Strategy objectives as defined in its Strategic Plan, as well as from nearly 20 years of PODS Pipeline Data Model implementation experience and lessons learned. PAGE 3 of 10 PODS LITE VERSION 1.1

4 The Next Gen initiative will result in a new data model the PODS Pipeline Data Model Version 7.0 as well as a Data Exchange Specification and migration and implementation guidance and instructions. The Next Gen Data Exchange Specification will facilitate data translations between the PODS Pipeline Data Model Versions 7.0 and earlier as well as other data models and will also enable system integration via serviceoriented approaches. The re-designed Data Model will standardize and modernize data management and reporting across the pipeline industry. PODS Next Generation Design Principles Design for the Future The next PODS Pipeline Data Model will be transformational not an incremental update to the existing standard. A Solid Core Coupled with Agility and Flexibility The Data Model will allow for independent extension of the model in a flexible fashion yet in alignment with core modeling and design principles. Support Time and History The Data Model will support timebased events and track asset lifecycle history. Support Location and Spatial Representation The Data Model will provide flexibility to include or exclude spatial representation of assets and events. Support Interoperability The Data Model will support data exchanges between systems and work streams within an organization as well as data exchanges between organizations. Easy to Understand The Data Model will be easy to understand, implement, extend and use. The Next Gen initiative is scheduled for completion in The PODS Association will be providing incremental releases of the full PODS Pipeline Data Model with the release of Version 7.0. As a subset of Version 7.0, PODS Lite offers current and potential future Association members the opportunity to preview the re-designed data model. More information on the Next Gen initiative and outcomes can be found on the PODS web site at What s Included in PODS Lite version 1.1? As a subset of the PODS Pipeline Data Model Version 7.0, PODS Lite v 1.1 provides a data model allowing users to collect and manage data for: Pipeline Hierarchy Defining the pipelines in a system and how they are organized, as well as the ability to define sites and stations and where they are located in space. Linear Referencing Enabling referencing of assets, events and conditions along a pipeline via measures and/or stationing. Linear referencing tables provided in PODS Lite include centerline, centerline sequence, continuous measure network, engineering stationing network and calibration points. It is these tables that enable use of Esri ArcGIS for Pipeline Referencing (APR) extension and toolset. Use of linear referencing tables (and APR) is optional when using PODS Lite. Should users elect to not use the PODS Lite linear referencing tables, location can be collected and managed via XYZ coordinate positions. Assets Installed and in-service product transport or containment devices, when connected end-to-end form a pipeline in the ground. Assets may be located by a measured position along a pipeline or alternately by an XYZ coordinate position. A subset of assets provided in PODS Lite includes pipe segments, coatings, valves, pipe bends, girth welds and pigging launchers and receivers. Conditions Representing the state or condition of a pipeline and representing the results of activities including inspection or analysis (population class study, high consequence area analysis). A subset of condition and operational tables provided in PODS Lite v 1.1 includes inspection range, class, operating PAGE 4 of 10 PODS LITE VERSION 1.1

5 pressure (to manage maximum allowable operating pressure or MAOP and maximum operating pressure or MOP), test pressure, consequence segment, pipeline operating condition, pipe jurisdiction and crossings including online, pipeline, utility, hydrology and transportation. Operations - Operations are a classification of a part of the pipeline system based on need for organization or as the result of analysis of the pipeline and the surrounding geography. Operating areas, operating pressure, high consequence areas and Class Location are forms of classification or organization of the pipeline. Operations do not reflect the state of the pipeline but rather reflect how the pipeline is organized or classified either manually or by virtue of the geography surrounding the pipeline or the operating limitations of the pipeline. Locations - Locations are events that are used to denote the location of something on or along the pipeline. Locations are typically used as reference points to find other features on or along the pipeline. Crossings and monuments represent locations along a pipeline. Crossings are points where cultural or physical geographic features intersect the pipeline. Monuments are used to locate inspections or serve as calibration or reference points for inspections. Aerial markers or above ground markers for inline inspections are forms of locations. While conceptually these may be considered assets because they are installed, their primary purpose is to locate the pipeline. Metadata - Metadata tables are used to describe generic non-spatial elements and to capture or codify rules about the structure and content of the model. Metadata is comprised of the following three groups: o o o TableMetadata Describes the structure and content of tables, modules, and layers in the model. Modules can be added to the base model tables store information about things on or along the pipeline. TableMetadata also describes the rules about if geometric features are required for the table. Layers are used to sub-type tables into groups of data within a table and also to define rules for features such as gap/overlap and cross layer dependency (cannot have coating without pipe, cannot have gaps in active pipes, what is internal and external coating etc.). These sections also describe business rules and units of measure and how domains and code-look up tables are organized and used in the model. ModelMetadata Describes the model version and the reference modes (if any) used in the data model. ReferenceMode describes all the route networks or measure/ stationing systems within the model. DocumentationMetadata Allows the user to capture links to documents (and the spatial position/boundary of those documents) and describe activities that occur on or along the pipeline. Allows the user to capture notes or make comments about any record in the model. PODS Association Overview Since 1998, the PODS Pipeline Data Model has been increasing safety and integrity of pipelines worldwide by providing pipeline operators with an enterprise database architecture that is comprehensive, open, vendor-neutral, highly-scalable, and proven. PODS supports the growing and changing needs of the pipeline industry through ongoing development and maintenance of its Pipeline Data Model and standards. This work is led by the PODS Technical Committee on Governance, responsible for the strategic technical direction of PODS Association. The work, including debate, deliberation and resulting recommendations, is conducted through the assigned Project Teams and Work Groups. PAGE 5 of 10 PODS LITE VERSION 1.1

6 PODS lowers the risk, cost, and time required to implement a pipeline GIS. Maintaining a single pipeline data repository helps pipeline operators to improve the quality, quantity and timeliness of pipeline information managed. PODS is an open standard, so members can choose software applications based on features, cost and usability. Multiple vendors may develop software products that interact with the PODS database. Pipeline operators don t have to be tied to a single vendor s proprietary data model. PODS promotes better business processes and workflow. Members will experience reduced data transfer between software applications and multiple databases; clear, concise definitions; plus, the ability to clearly delineate data ownership. PODS Association membership leverages a broad knowledge-base. As a PODS Association member, organizations immediately become part of a global network of over 170 companies, associations and agencies to access a wealth of technical knowledge and experience from other PODS members. Members work collaboratively to develop and refine the PODS Pipeline Data Model. PODS Lite v. 1.1 (.zip Package Contents) PODS Lite is free and available to all. The following PODS Lite resources can be found and downloaded from These twenty-four documents that comprise the PODS Lite version 1.1 download have been compressed into four ZIP files as follows: 1. PODS Lite v 1-1 USER DOCUMENTS.zip contains seven pdf documents describing technical and configuration steps (documents 1-7 in table below) 2. PODS Lite v 1-1 GEODATABASE FILES.zip contains two.xml and two.xls documents, and a zip file which provides configuration tools (documents 8-12) 3. PODS Lite v 1-1 DATA DICTIONARIES ALL.zip contains seven pdf documents, one Data Dictionary for each flavor (documents 13-19) 4. PODS Lite v1-1 SCRIPTS ALL flavors.zip contains five zip files that, when expanded, include the.sql scripts for Oracle SDO, Oracle ST, PostgreSQL, SQLServer and for population of metadata tables (documents 20-24) These documents have been arranged in an order which we believe will best help you understand what is included in the PODS Lite Package (PODS Lite v 1-1.zip). We suggest that you read them in the order provided. (NOTE: you will see this list repeated in each of the documents, with the document you are currently reading highlighted in yellow): PAGE 6 of 10 PODS LITE VERSION 1.1

7 Filename Title and Description PODS LITE V 1-1 USER DOCUMENTS.ZIP 1 PODS Lite README List of Documents-FINAL-v1-1.pdf PODS Lite v 1.1 README List of Documents A comprehensive list of all of the documents contained within the PODS Lite v1-1.zip file, with brief descriptions, titles and filenames (note the unformatted version of this doc is Readme.txt). 2 PODS Lite Executive Summary-FINAL-V1-1.pdf (this document you are currently reading) 3 PODS Lite Technical Overview and Guide-FINAL-v1-1.pdf PODS Lite v 1.1 Executive Summary A big-picture overview of PODS Lite, Next Generation and the PODS Association read this document first. PODS Lite v 1.1 Technical Overview and Guide A comprehensive technical overview of PODS Lite and its relationship to the PODS Pipeline Data Model. The document is intended for individuals deploying, configuring and extending the PODS Lite data model and for individuals wishing to understand new procedures being used by the PODS Association to manage and maintain PODS Lite and the large PODS Pipeline Data Model. A technical user of the PODS Pipeline Data Model should be able to understand how the model is designed and how it can be implemented after reading this document. 4 PODS Conceptual Model-FINAL-V7-0.pdf PODS 7.0 Conceptual Model Diagram A poster-sized diagram showing and describing the conceptual design for the PODS 7.0 Data Model (previously called Next Gen ). The Diagram shows and describes the classes, attributes, relationships between the classes and the pre-defined code lists contained in the model. The Conceptual Model Diagram is a recommended starting point to help users of PODS Lite understand what is included and how the data model is structured. 5 PODS Lite RDBMS Configuration Guide-FINAL-v1-1.pdf PODS Lite v 1.1 RDBMS Configuration Guide An implementation guide outlining the various design decisions and implementation patterns that may be elected during the installation and configuration of the PODS Lite RDBMS model. 6 PODS Lite Geodatabase Configuration Guide-FINALv1-1.pdf PODS Lite Geodatabase Configuration Guide For APR Or Non-APR Implementation A full listing of the steps to download, install and configure a PODS Lite geodatabase - for use with Esri s APR OR without APR. Note: this is not intended to replace full documentation for APR as provided by Esri. 7 PODS Lite Change Log-FINAL-v1-1.pdf PODS Lite Change Log v 1.0 to v 1.1 A list of all of the changes from version 1.0 to version PAGE 7 of 10 PODS LITE VERSION 1.1

8 PODS LITE V 1-1 GEODATABASE FILES.ZIP 8 PODS-Lite-Geodatabase-XML-Workspace-APR- FINAL-v1-1.xml 9 PODS-Lite-Geodatabase-XML-Workspace-with- Relationships-FINAL-v1-1.xml PODS Lite v 1.1 Geodatabase XML Workspace for APR Users may create an Esri geodatabase for use with APR using this PODSprovided XML workspace document. The XML workspace document can be imported using the tool provided in the geodatabase configuration toolbox below. PODS Lite XML Workspace Document with Relationships (Non-APR Implementation) Users may create an Esri geodatabase with full relationships (NOT for use with APR) using this PODS-provided XML workspace document. The XML workspace document can be imported using the tool provided in the geodatabase configuration toolbox below. 10 PODS-Lite-Insert-Metadata-APR-FINAL-v1-1.xls PODS Lite Insert Metadata for APR The data in this spreadsheet is content for the metadata tables in PODS Lite 1.1. The insertion process is described in the PODS Lite Geodatabase Configuration Guide for APR (document #6). 11 PODS-Lite-Insert-Metadata-With-Relationships- FINAL-v1-1.xls 12 PODS Lite Geodatabase Configuration Toolbox- FINAL-v1-1.zip PODS Lite Insert Metadata with Relationships (Non-APR Implementation) The data in this spreadsheet is content for the metadata tables in PODS Lite 1.1. The insertion process is described in the PODS Lite Geodatabase Configuration Guide (document #6). PODS Lite Geodatabase Configuration Toolbox A toolbox containing one Python script, presented as an ArcToolbox tool. The tool uses the either of the geodatabase XML documents (described above) to create a geodatabase automatically. The tool allows the user to set up the CRS of their choice. PODS LITE V 1-1 DATA DICTIONARIES - ALL.ZIP 13 PODS Lite Logical Model and Data Dictionary-FINALv1-1.pdf PODS Lite Logical Model and Data Dictionary The global PODS Lite Logical Data Model and Dictionary (applies to all physical implementations regardless of target database - APR, Geodatabase, Oracle, PostgreSQL, or SQL Server). This document is intended to be a guide on describing how data are stored in each class in the model and presents a first pass at data governance for how data are created, retrieved, updated and deleted to and from these tables. 14 PODS Lite Geodatabase APR Data Dictionary-FINALv1-1.pdf PODS Lite Geodatabase Data Dictionary A data dictionary of the physical PODS Lite Model implemented in an Esri Geodatabase for APR. It contains a complete listing of feature and object classes, fields, and domains of the physical model in a geodatabase. As such, it does not contain the full documentation of abstract classes and data types found in the PODS Lite Logical Model and Data Dictionary (document #13). Therefore, the two data dictionaries should be used together to fully understand and implement PODS Lite v PAGE 8 of 10 PODS LITE VERSION 1.1

9 15 PODS Lite Geodatabase with Relationships Data Dictionary-FINAL-v1-1.pdf 16 PODS Lite Oracle SDO RDBMS Data Dictionary-FINALv1-1.pdf 17 PODS Lite Oracle ST RDBMS Data Dictionary-FINALv1-1.pdf 18 PODS Lite PostgresSQL RDBMS Data Dictionary- FINAL-v1-1.pdf 19 PODS Lite MS SQLServer RDBMS Data Dictionary- FINAL-v1-1.pdf PODS Lite Geodatabase with Relationships Data Dictionary A data dictionary of the physical PODS Lite Model implemented in a Geodatabase with full relationships. It contains a complete listing of feature and object classes, fields, and domains of the physical model in a geodatabase. As such, it does not contain the full documentation of abstract classes and data types found in the PODS Lite Logical Model and Data Dictionary (document #13). Therefore, the two data dictionaries should be used together to fully understand and implement PODS Lite v 1.1. PODS Lite Oracle SDO Geometry Native ( Oracle Spatial ) RDBMS Spatial Data Type - Data Dictionary A data dictionary of the physical PODS Lite Model implemented in Oracle for SDO geometry (for the native Oracle Spatial RDBMS spatial data types). It contains a complete listing of feature and object classes, fields, and domains of the physical model. As such, it does not contain the full documentation of abstract classes and data types found in the PODS Lite Logical Model and Data Dictionary (document #13). Therefore, the two data dictionaries should be used together to fully understand and implement PODS Lite. PODS Lite Oracle ST - RDBMS Spatial Data Type - Data Dictionary A data dictionary of the physical PODS Lite Model implemented in Oracle for ST geometry (for the industry standard RDBMS spatial data types). It contains a complete listing of feature and object classes, fields, and domains of the physical model. As such, it does not contain the full documentation of abstract classes and data types found in the PODS Lite Logical Model and Data Dictionary (document #13). Therefore, the two data dictionaries should be used together to fully understand and implement PODS Lite. PODS Lite PostgresSQL RDBMS Data Dictionary A data dictionary of the physical PODS Lite Model implemented in PostgresSQL RDBMS. It contains a complete listing of feature and object classes, fields, and domains of the physical model in a geodatabase. As such, it does not contain the full documentation of abstract classes and data types found in the PODS Lite Logical Model and Data Dictionary (document #13). Therefore, the two data dictionaries should be used together to fully understand and implement PODS Lite. PODS Lite MS SQLServer RDBMS Data Dictionary A data dictionary of the physical PODS Lite Model implemented in MS SQL Server. It contains a complete listing of feature and object classes, fields, and domains of the physical model in a geodatabase. As such, it does not contain the full documentation of abstract classes and data types found in the PODS Lite Logical Model and Data Dictionary (document #13). Therefore, the two data dictionaries should be used together to fully understand and implement PODS Lite. PODS LITE V 1-1 SCRIPTS ALL FLAVORS.ZIP 20 PODS-Lite-insert-metadata-v1-1.zip PODS-Lite-v1.1_insert_metadata.sql PODS-Lite-v1-1_insert_metadata-Oracle.sql 21 PODS-Lite-Oracle-SDO-v1-1.zip PODS-Lite-Oracle-SDO-v1-1.sql PAGE 9 of 10 PODS LITE VERSION 1.1

10 PODS-Lite-Oracle-SDO-v1-1_inserts_codelistType_2.sql PODS-Lite-Oracle-SDO-v1-1_inserts_codelistType_3.sql PODS-Lite-Oracle-SDO-v1-1_spatial.sql PODS-Lite-v1-1_insert_metadata-Oracle.sql 22 PODS-Lite-Oracle-ST-v1-1.zip PODS-Lite-Oracle-ST-v1-1.sql PODS-Lite-Oracle-ST-v1-1_inserts_codelistType_2.sql PODS-Lite-Oracle-ST-v1-1_inserts_codelistType_3.sql PODS-Lite-Oracle-ST-v1-1_spatial.sql PODS-Lite-v1-1_insert_metadata-Oracle.sql 23 PODS-Lite-SQLServer-v1-1.zip PODS-Lite-SQLServer-v1-1.eap PODS-Lite-SQLServer-v1-1.sql PODS-Lite-SQLServer-codelist-type2-v1-1.sql PODS-Lite-SQLServer-codelist-type3-v1-1.sql PODS-Lite-SQLServer-spatial-v1-1.sql PODS-Lite-v1.1_insert_metadata.sql 24 PODS-Lite-PostgreSQL-v1-1.zip PODS-Lite-PostgresSQL-v1-1.eap PODS-Lite-PostgreSQL-v1-1.sql PODS-Lite-PostgreSQL-codelist-type2-v1-1.sql PODS-Lite-PostgreSQL-codelist-type3-v1-1.sql PODS-Lite-PostgreSQL-spatial-v1-1.sql PODS-Lite-v1.1_insert_metadata.sql PAGE 10 of 10 PODS LITE VERSION 1.1