PODS Spatial Implementation Working Group

1
PODS Spatial Implementation Working Group

• PODS User Group
• September 21, 2006

PODS Users Group Presentation 2006
2
Agenda

• Working Group General Overview
• ESRI/PODS/APDM MOU
• ESRI Sub-Committee
• Oracle Spatial Sub-Committee
• Questions/Answers

PODS Users Group Presentation 2006
3
Working Group Charter

• Initial Working Group Kick-off Meeting
  03.14/15.06
• Established objectives, SoW, deliverables,
  membership, etc.
• Technical Committee approved Charter 04.18.06
• Board of Directors approved Charter 04.21.06
• Membership
• Chairman Mike King, BP America
• Co-Chairman Ron Brush, New Century Software
• PODS Technical Committee Liaison Costas
  Kotzabassis, Blue Sky Development
• ESRI Sub-Committee Chairman Scott Moravec, Eagle
  Information Mapping
• Oracle Spatial Sub-Committee Chairman Brad
  Grabowski, GE Energy

PODS Users Group Presentation 2006
4
Working Group Objectives

• Development of industry Standard PODS-Compatible
  database model(s) or extension(s) that will
  spatially enable the PODS database to facilitate
  proprietary applications and PODS GIS
  integration.
• PODS will retain all intellectual property rights
• Maintain vendor neutral open concept (PODS
  Relational Model) but also recognize the need to
  integrate with proprietary spatial technologies
• Formation of ESRI sub-committee focused on an
  ESRI Geodatabase solution compatible with ArcGIS
  9.x and beyond.
• Formation of an Oracle Spatial sub-committee
  focused on an Oracle Spatial solution that will
  support implementation with SmallWorld,
  Intergraph, and Autodesk.
• Established an industry-wide collaborative
  environment

PODS Users Group Presentation 2006
5
MOU ESRI/PODS/APDM

• Collaborative industry initiative between
  ESRI/PODS/APDM
• This agreement to work together is great news
  for the pipeline industry. It will allow
  operators to adopt an industry standard data
  model that PODS provides plus take advantage of
  the full benefit of the spatial geodatabase of
  APDM Bill Meehan, Director of Utility
  Solutions and acting Pipeline Industry Manager
  for ESRI.
• Viewed as a major step forward for the industry
  with the integration of a standard data model
  (PODS) and a standard approach to an ESRI
  Geodatabase implementation.

PODS Users Group Presentation 2006
6
MOU ESRI/PODS/APDM

• Key Features
• PODS ESRI Geodatabase Lite
• Consisting of common APDM core classes and a
  limited number of the PODS tables
• Access for free public distribution
• PODS ESRI Geodatabase (Heavy)
• Consisting of common APDM core classes and all
  PODS event and domain tables
• To protect the investment of our PODS members
  access will be limited to PODS members only
• Formation of a standing joint committee with
  co-chairs consisting of equal representation from
  PODS and APDM members
• Provide the framework for continuity between APDM
  and PODS of future enhancements to the APDM core
  classes.
• To assure the interest of the PODS Association is
  preserved, the PODS Board of Directors will
  appoint an ex-officio member to the APDM Steering
  Committee.
• Will have full voting rights on changes and
  modifications to the APDM core classes.
• A licensing agreement between PODS and ESRI will
  enable the PODS Association to own and maintain
  the PODS ESRI Geodatabase and Geodatabase Lite
  models that include the integration of the APDM
  core classes
• PODS and APDM will maintain their exclusive and
  respective branding.

PODS Users Group Presentation 2006
7
PODS Spatial Implementations Development
APDM
PODS
Board of Directors
Steering Committee
Technical Committee
Technical Committee
PODS Spatial Working Group (short-term)
PODS Oracle Spatial Sub-committee (short-term)
PODS ESRI Sub-committee (short-term)
Consists of PODS, APDM, and ESRI members
responsible for development of a PODS Geodatabase
Standard Implementation
Consists of PODS, Oracle Spatial, Autodesk,
Intergraph, and SmallWorld members responsible
for development of a PODS Oracle Spatial Standard
Implementation
PODS Users Group Presentation 2006
8
PODS Spatial Implementations Ongoing Maintenance
APDM
PODS
Board of Directors
Steering Committee
Technical Committee
Technical Committee
Joint PODS/APDM Standing Committee
PODS Oracle Spatial Standing Committee
PODS Geodatabase Standing Committee
Consists of PODS members from Joint PODS/APDM
committee and other PODS members responsible for
ongoing maintenance of PODS Geodatabase Standard
Implementation
Consists of equal representation from PODS and
APDM members and responsible for management of
change and enhancements to APDM Core
Consists of PODS members responsible for ongoing
maintenance of PODS Oracle Spatial Standard
Implementation
PODS Users Group Presentation 2006
9
ESRI Sub-Committee Membership

• Scott Moravec, Eagle Information Mapping (Chair)
• Keith Cote, MOORE Resource Systems
• Hai-Li Wang, Chevron
• David Frye, ESRI/EIM
• John Alsup, ESRI
• Doug Thorpe, Duke Energy Field Services
• John Minassian, Geofields
• Jennifer Flax, Petris
• Daniel Barry, American Innovations
• Rene Ramirez, Blue Sky Development
• Robert Maggio, Petris
• Benny Guo, Enghouse
• Membership is somewhat dynamic with additional
  APDM members being added along with other
  re-alignment to focus on technical delivery

PODS Users Group Presentation 2006
10
ESRI Sub-Committee Guidelines

• Seek participation of PODS members and
  non-members
• Seek participation of members with hands-on
  Geodatabase knowledge and PODS knowledge
• Seek participation of pipeline operators,
  vendors, software service providers, consultants
  and related parties
• Seek contributions from participants, utilizing
  existing mature data structures where practical
  and applicable. IP contributions will be assigned
  to the PODS Association.
• Inclusive design incorporating best practices
  from PODS, PPDM, APDM and recommended practices
  from ESRI
• Extensible design providing users the ability
  to extend (add to) as necessary
• Face-to-face initial kick-off meeting and closure
  meeting
• Bi-weekly one-hour conference calls or as
  otherwise determined

PODS Users Group Presentation 2006
11
ESRI Sub-Committee Scope of Work

• Phase I PODS ArcSDE Existing Implementations
• Focus on documenting the different methods for
  spatially enabling PODS based on existing PODS
  implementations (Complete end of 4Q06)
• Phase II PODS Geodatabase Specification
• Phase Two will build upon the concepts identified
  in Phase I to develop a stand-alone ESRI
  Geodatabase implementation. (Targeted
  Completion end of 1Q07)
• Review by ESRI
• Review IP contract
• Review of 9.2 history features vs. PODS history.
• Review of Topology vs. Geometric Network vs.
  Network Data Model.
• Review of PPDM Lite, APDM and other similar
  Geodatabase models
• Draft of PODS Geodatabase Logical Core Model
  (conceptual)
• Draft of PODS Geodatabase Physical Core Model
  (implement)
• Pilot test implementation by Working Group
  members
• Review results of Pilot test implementations
• Recommendations for PODS Geodatabase
  Implementation
• Develop documentation
• Submission of deliverables to PODS Technical
  Committee for approval
• Submission of deliverables to the PODS Board of
  Directors for approval and inclusion in PODS
  Technical Standards

PODS Users Group Presentation 2006
12
ESRI Sub-Committee Scope of Work

• Phase III PODS Geodatabase Implementation
  Processes
• Phase III is the development of processes that
  will define the extraction and/or replication of
  data between the PODS data model and the PODS
  Geodatabase. (Targeted Completion end of 3Q07)
• Determine processes and procedures for extracting
  and/or replicating data between the PODS model
  and the PODS Geodatabase
• Develop DDL and/or other scripts as required
• Develop documentation and submit to Technical
  Committee for approval as Best Practices
• PODS Geodatabase Implementations will be based on
  next release of PODS and APDM models (Version
  5.0)
• PODS Geodatabase Lite (Targeted Completion end of
  2Q07)
• PODS Geodatabase (Targeted Completion end of
  3Q07)

PODS Users Group Presentation 2006
13
Oracle Spatial Sub-Committee Membership

• Brad Grabowski, GE Energy (Chair)
• Blake Philpot, GE Energy
• Jay Smith, GE Oil Gas
• Brimmer Sherman, Intergraph
• Doug Szabo, Intergraph
• David Glenn, Intergraph
• Jay Sharma, Oracle Spatial
• Siva Ravada, Oracle Spatial
• Stephen Brockwell, Autodesk
• Costas Kotzabassis, Blue Sky Development
• Pipeline Operator representative(s) Need
  Volunteers!!!

PODS Users Group Presentation 2006
14
Oracle Spatial Sub-Committee Guidelines

• Seek participation of PODS members and
  non-members
• Seek participation of members with hands-on
  Oracle Spatial and PODS knowledge
• Seek participation of pipeline operators,
  vendors, software service providers, consultants
  and related parties
• Seek contributions from participants, utilizing
  existing mature data structures where practical
  and applicable. IP contributions will be assigned
  to the PODS Association.
• Inclusive design incorporating best practices
  from PODS and recommended practices from Oracle
  Spatial implementations
• Extensible design providing users the ability
  to extend (add to) as necessary
• Face-to-face initial kick-off meeting and closure
  meeting
• Bi-weekly one-hour conference calls or as
  otherwise determined

PODS Users Group Presentation 2006
15
Oracle Spatial Sub-Committee Scope of Work

• Phase I Evaluation of existing linear Oracle
  Spatial solutions
• Phase I will involve the discovery and due
  diligence evaluation of existing linear Oracle
  Spatial solutions. (Targeted completion end of
  4Q06)
• Determine the basic requirements and
  functionality of the Oracle Spatial interaction
  with PODS
• Document methods of linear Oracle Spatial
  solutions based on examples from the
  transportation industry.
• Develop a comparison of the advantages and
  disadvantages of each identified method
• Identify the gaps between the existing PODS
  tables and Oracle Spatial.
• Identify the appropriate CASE tools for use with
  Oracle Spatial
• Define use cases for rendering with Oracle Spatial

PODS Users Group Presentation 2006
16
Oracle Spatial Sub-Committee Scope of Work

• Phase II Development of the design basis and
  geometry relationships and development of
  prototype
• Phase II will involve the development of the
  design basis and determination of the geometry
  relationships and how they will be graphically
  represented. (Targeted completion end of 3Q07)
• Create a process map
• Develop the Prototype based on the design basis
• Test for scalability and performance
• Identify a PODS member representative sample of a
  populated PODS database.
• Define minimum software and hardware
  specifications
• Provide a report out of the Phase II work at next
  years PODS User Group meeting following GITA.

PODS Users Group Presentation 2006
17
Oracle Spatial Sub-Committee Scope of Work

• Phase III Completion of Oracle Spatial
  integration, final, coding and documentation
• Phase III will involve the completion of the
  Oracle Spatial Integration with the final output
  of scripts, dump files, and a sample PODS
  database for use by the members. (Targeted
  completion end of 4Q07)
• Development of documentation and implementation
  white paper
• Development of data base dump with prototype
  implementation
• Identify and recommend future steps and
  enhancements for consideration.
• Anyone (especially operators) that are
  interested in actively participating in the
  sub-committee please notify Brad Grabowski by
  October 15, 2006.
• Bradley.grabowski_at_ge.com or phone [phone]

PODS Users Group Presentation 2006
18
Thank You

PODS Users Group Presentation 2006