Click here to load reader

PODS Lite for ESRI Geodatabase configured with ArcGIS for ... for ESRI Geodatabase configured with ArcGIS for Pipeline Referencing (APR) ESRI Petroleum User Group Conference - April

  • View

  • Download

Embed Size (px)

Text of PODS Lite for ESRI Geodatabase configured with ArcGIS for ... for ESRI Geodatabase configured with...

  • PODS Lite for ESRI Geodatabase

    configured with ArcGIS for Pipeline Referencing (APR)

    ESRI Petroleum User Group Conference - April 13, 2017

  • Introduction and Outline

    • PODS Association

    • Strategic Plan and Next Generation

    • PODS Lite

    • PODS Lite with ArcGIS for Pipeline Referencing (APR)

  • The PODS Association

    • Organization

    • Members

    • Mission – develop and advance global standards and best practices

    • Industry Leadership

  • Strategic Plan

    • Transformation of Data Model

    • Design principals – simple, uniform, consistent, documented

    • Strategic partnership with ESRI

  • Next Generation Drivers Feedback and Lessons Learned

    Lack of Performance

    Difficult to Implement

    Lack of Agility

    Multiple standards to choose from

    Core Documentation


    Disparity between vendor


    Member Concerns, Lessons Learned

  • A change in data modeling

    • Transformative change

    • Remove redundancy, simplify and organize the existing model

    • Clean up duplicate tables and un-used attributes

    • Manage the model in a single place (single file)

    • New approach to data modeling (focus on the logical model not the physical model)

    • Support many different physical implementations especially ESRI ArcGIS for Pipeline Referencing

  • PODS Next Generation

    Modules (eg. New Construction)

    Modules (eg. Regulatory) Implementation Patterns (Spatial, Relational, Hybrid, Geodatabase)


    RDBMS Spatial Data Types: Oracle Spatial

    SQL Server Spatial


    ESRI Geodatabase Native Data Format

    Open Source

    PostGRES/PostGIS data format


    RDBMS Spatial Data Types: Oracle Spatial

    SQL Server Spatial

    Meta Tables

    Core Linear Referencing System (LRS)

    Routes Calibration


    Centerline Sequence


    Core Tables

    Core Table Reference Data (Look up and conditional domains)

    Modules (eg. ILI)

    Module Reference Data (Look up and conditional domains)

    Offline Storage

    Big Data Support

    History Definitions and Explainations

    Business Intelligence Presentation Layer, API

    D ata Exchan

    ge Specificatio n

    X M

    L, JSO N

    , C SV

    Documentation Conceptual Data Model Logical Data Model Data Dictionary Governance (Model Use, Editing Standards, Data Content Specifications)

    Reference Modes Continuous (2D/3D) Interrupted (2D/3D) Referent Point and Offset (MilePost) XYZ Odometer

    Software ShapeChange Enterprise Architect Module Validator

    Best Practices Schema/Module Specification, Definition, Creation and Validation Application Specification, Creation and Validation Managing History, Work Orders, Documents, Re-routes and Activities Feature/Condition Provenance Managing Metadata Module Management Data Exchange

    New to Next Generation of PODS Standards

  • Definitions


     Next Generation • Is the Process of defining the standard and the core

     PODS Lite is all flavours • ESRI Geodatabase, Oracle, MS SQL Server, POSTGRES

    (APR tables are common to all)

     PODS 7.0 • Will be the first release of what we are considering the


  • Conceptual, Logical and Physical Models

    • 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 platform- specific template which can be used to add and manage data



  • Implementation Patterns

    Conceptual Model (Visio)

    Shape Change

    Logical Model – GML

    Next Gen Working


    PODS 7.0 Core

    Modules Modules

    Modules Modules

    Next Gen Working


    ShapeChange Configuration



    Physical Schema

    Geometry Type

    Relationship Classes

    Physical Model XML Workspace

    Physical Model (SQL DDL)

    Physical Model XML DES

    Oracle PostGres

    MS-SQL Server

    ESRI Geodatabase

    Data Exchange Specification

  • PODS Lite

    • Freely available from the PODS WebSite (

    • Subset of the Full PODS 7.0 Core Data Model

    • Uber-Documents

    • Coordinate vs Linear Referencing (or Both)

    • In the Geodatabase, with or without ArcGIS for Pipeline Referencing

  • Documentation

    Document Description

    PODS Lite README List of Documents.pdf PODS Lite “README” List of Documents

    PODS Lite Executive Summary_Final_V1.pdf PODS Lite Executive Summary

    PODS Lite Technical Overview and Guide_Final_V1.pdf PODS Lite Technical Overview and Guide

    PODS Lite Conceptual Model Diagram_Final_V1.pdf PODS Lite Conceptual Model Diagram

    PODS Lite Logical Model and Data Dictionary_Final_V1.pdf PODS Lite Logical Model and Data Dictionary

    PODS Lite Geodatabase Data Dictionary_Final_V1.pdf PODS Lite Geodatabase Data Dictionary

    UsPODS Lite XML Workspace with CRS Not Defined_Final_V1.xml PODS Lite XML Workspace Document with Coordinate Reference System (CRS) Not Defined

    PODS Lite Geodatabase EA Physical UML_Final_V1.eap PODS Lite Geodatabase Enterprise Architect (EA) Physical UML

    PODS Lite Configuring a CRS in EA_Final_V1.pdf PODS Lite Configuring A Coordinate Reference System in Enterprise Architect (EA)

    PODS Lite Geodatabase Configuration for APR_Final_V1.pdf PODS Lite Geodatabase Configuration for use with ArcGIS for Pipeline Referencing (APR)

    PODS Lite Geodatabase Configuration Toolbox.tbx PODS Lite Geodatabase Configuration Toolbox

    Readme.txt Readme

  • Choose Geodatabase

    or RDBMS

    Choose Enterprise or File


    Oracle PostGres

    MS-SQL Server

    Personal or File Geodatabase

    Choose RDBMS

    Oracle PostGres

    MS-SQL Server

    Choose Geometry Type



    Choose Spatial Location





    Choose Editing Tools




    Versioned Geodatabase


    • Organization of the model

    • Shows the ‘concepts’

    • Details the relationships

    • Describes the model at a high level



    shared geometry in network

    Centerline CalibrationPoint

    measure (double) networkID (integer *) networkRouteID (fk) (GUID) pointTypeCL seriesOrder (integer) forwardMeasure (double) backwardMeasure (double)


    centerlineID (fk) (GUID) networkID (fk) (integer *) networkRouteID (fk) (GUID)


    EngineeringStationNetwork = 1 ContinuousMeasureNetwork = 2

    1 2 3

    ContinuousMeasureNetwork EngineeringStationNetwork

    parentNetworkID (fk) (integer) stationingDirectionCL


    ordered by

    Pipeline Product


    Valve PipeSegment

    dateManufactured (date) detailFeatureID (fk) detailTableName (string) gradeCL joinTypeCL longSeamCL manufacturerCL materialCL nominalDiameterCL nominalPressureRating (long) nominalWallThicknessCL millLocation (string) millTestPressure (long) originCL outsideDiameterCL segmentTypeCL specificationCL SMYSCL

    dateManufactured (date) functionalStatusCL functionCL Identifier (string) joinTypeCL length (double) manufacturerCL materialCL millTestPressure model (srting) operatorTypeCL operatorManufacturerCL outsideDiameterCL ratingCL remotelyOperatedLF responseTime (integer) safetyCriticalEquipmentLF specificationCL (string) typeCL

    History (H)

    fromDate (date) toDate (date) statusCL

    Abstract Classes


    Current Historic Unknown Verified as Unknown


    The Global abstract class is concerned with a model wide global identifier field.

    The Assets abstract class is concerned with describing physical installed assets used to transport product or are part of the physical pipeline operation. Assets can be contained within Sites. The Conditions abstract classes is used to describe the historic and current state or condition of the pipeline. Conditions are discovered as a result of Activities.

    Describe is used to describe elements in the pipeline. History is used to track when elements were current or active or when they were historic or idle . Audit is used to track what person created and last modified a element in the database.

    PipelineFeature is used to represent how a geometric feature/shape is located on or along the pipeline. All elements in the model that have a location in space (with the exception of area features – polygons) must implement (or possess the attributes from) the PipelineFeature abstract class. Each PipelineFeatur