Download the PODS Brochure

More documents

Recommendations

Info

PODS relational While pipelines are clearly linear objects, PODS Relational stores the linear nature of the pipeline centerline deconstructed into sequenced (X, Y, Z) coordinates. This allows PODS Relational to utilize the inherent functionality found in modern Relational Database Management Systems (RDBMS). While the PODS Relational model provides GIS neutrality, it is usually spatially enabled with a GIS system. This allows PODS Relational to easily integrate with other IT systems and databases. PODS Relational is the most widely deployed enterprise implementation of the PODS Data Model. PODS includes more than 670 tables that can be categorized into the four functional groups as listed below. • The Core Tables store the pipeline hierarchy and include Line, Route, Series and Station Point. The Core Tables also define the linear distances, or stationing, used to reference the location of Events on the pipelines. The Core Tables also store the instructions that control how individual components are re-assembled into a pipeline centerline. • The Location Tables store the centerline of the pipeline, as well as the GPS coordinates of specified features, including offline features. The Location Tables also serve as the translation point between the PODS Relational Database and a Geographic Information System (GIS). The PODS Relational Database has the capacity to store a variety of spatial content and to interface with a multitude of GIS platforms. • The Event Tables store the information about the pipelines such as pipeline specifications and features, operational measures, integrity and inspection results, geographic features, repair and maintenance history, analysis records, and regulatory compliance information. These data records are stored as either linear or point features. The Event Tables also provide a mechanism to link to external documents through the PODS database. • The Code Look-up Tables are used to limit entries in certain fields to predetermined sets of allowable values. The Pipeline Operator typically determines the values for the Code Look-up Tables early in the implementation process. Operators can use company-specific values, example values provided by PODS for some tables, or a combination of the two. 4
PODS esri spatial The PODS ESRI Spatial model is a derivative of the PODS Relational model, but designed for implementation as an object-relational ESRI geodatabase. PODS ESRI Spatial contains the tables, attributes and domains of the PODS Relational model, but is designed specifically for an ESRI SDE deployment. The PODS ESRI Spatial model was designed to leverage advantages inherent in ESRI Geodatabase technology, including: • The object-relational structure of the PODS ESRI Spatial Geodatabase precludes the need to manage synchronization between the relational database and a separate GIS system. • Data versioning • History tracking • Storage of offline spatial data (such as roads, water bodies or structures) • Geoprocessing tools • Linear referencing • Interoperability with other geographic data sets 5
Page 1 and 2: uild an intelligent pipeline center
Page 3 and 4: what PODS does for pipeline compani
Page 5: PODS implementation methods the POD
Page 9 and 10: what data does PODS manage? • Phy
Page 11 and 12: how are companies leveraging PODS?
Page 13 and 14: Components of the PODS pipeline dat
Page 15 and 16: collaborating to develop industry b
Page 17 and 18: structure of the PODS association T
Page 19 and 20: PODS documentation With each new re
Page 21 and 22: what are the benefits to being a PO
Page 23 and 24: www.pods.org For more information a

Download the PODS Brochure

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?