OGC PipelineML SWG Meeting – Geneva 2014

The following are notes from this week’s PipelineML SWG meeting held in Geneva on June 10, 2014:

Meeting Metadata

Date: 2014.06.10 17:00-17:50 PM (10:00-10:50 AM CDT)

Location: Geneva, Switzerland

Attendees:

• John Tisdale, Enterprise Products
• Gary Hoover, Enterprise Products
• Terry Strahan, Morris P. Hebert, Inc.
• Bart De Lathouwer, OGC
• Joseph Howell, Global Information Systems

Meeting Agenda

The following agenda was reviewed with no comments:

• 17:00-17:05 – Meeting Schedule Overview
• 17:05-17:20 – Election of SWG Chair and Co-chair positions
• 17:20-17:25 – Key PipelineML Events to Date
• 17:25-17:30 – Governing Values of PipelineML
• 17:30-17:40 – Standards Development Process
• 17:40-17:50 – Major Components of SolutionThe following guidelines were discussed related to potential conflicts of interests regarding leadership positions for the SWG. We want to avoid any situation in which there could be a perception of a conflict of interest. Given these parameters, the following guidelines were suggested:
• Chair and Co-chair Election

• Avoiding Potential Conflicts of Interest

• Position/s should not be delegated to:
  • Staff of vendor/solution provider who may be considered for outsourcing, prototyping, or building of any PipelineML components or technologies
  • Staff of standards organization
• Prefer pipeline operators or pipeline service providers (non-technical services providers)
• Following leadership guideline discussion, the opportunity was extended for nominations to be made for the Chair position of the SWG.

• Nominations for PipelineML SWG Chair Position

• Ron Lake, Galdos Systems, nominated John Tisdale
• Gary Hoover, Enterprise Products, seconded the motion
• No further nominations were made
• Call for discussions yielded none
• Call for objections to unanimous consent yielded none
• Motion passed

• Nominations for PipelineML SWG Co-chair Position/s

• Gary Hoover, Enterprise Products, nominated Terry Strahan
• Ron Lake, Galdos Systems, seconded the motion
• No further nominations were made
• Call for discussions yielded none
• Call for objections to unanimous consent yielded none
• Motion passed

Key Milestones for PipelineML

The following information was shared outlining some of the key milestones that have led to this point in the formation of PipelineML:

• PODS and Enterprise Products begin exploring standards opportunities with ISO 15926 (11/2012)
• Enterprise Products joined OGC (7/2013)
• Formation of OGC PODS MOU (9/2013)
• OGC PipelineML Ad-hoc Meeting – Washington, DC (3/2014)
• Tentative formation of PipelineML SWG (3/2014)
• Development of PipelineML SWG Charter (3/2014)
• Refinement of PipelineML SWG Charter (4/2014)
• Charter review and commenting period passed (5/2014)
• Discussions with American Society of Civil Engineers (ASCE) about formation of MOU (5/2014)The following governing values were defined for PipelineML:
• Governing Values for PipelineML

• Practical/Pragmatic
• Flexible
• Extensible
• Fit-for-purpose
• Broad industry support (International)
• Use Case driven
• Agile and iterative developmentThe following process was proposed for the development of the PipelineML standard.
• Proposed Process for Defining and Developing the PipelineML Standards

1. Identify Prospective Partners and Engage in Dialogue
   • Existing standards bodies (identify gap/overlaps – adopt and extend whenever possible)
   • Thought-leader pipeline operators and service providers
2. Requirements and Scope
   • Gather, document, model (UML), and vet use cases and requirements
   • Define phases and scopes
3. Define Solution Architecture
   • Major solution components
   • Discover existing solution components we can leverage
   • Define component champions and ownership
4. Develop PipelineML
   • Define conceptual model
   • Determine existing standards candidates (XML, GML, CSW-ebRIM, etc.) – integrate where viable
   • Translate conceptual model into encoding schemes
   • Rapid prototypes in agile iterations to quickly vet concepts
   • Engage OGC Interoperability Program
   • Test proposed standard
   • Collection additional feedback
   • Refine standard as needed
5. Publish Standard
6. Create Awareness of Standard among Industry Stakeholders
7. Broaden Scope, Mature Concepts and Repeat

The opportunity for feedback was extended. Ron Lake mentioned the need to define the conceptual model as early in the process as possible. Ron was thanked for his feedback and insights.

Key Components of Solution Architecture

The following diagram was shown and discussed that define the key components of the proposed solution:

The Pipeline Type Registry [working title] is an online registry that contains a thorough industry-vetted listing of various component types.

1. This registry would provide the functionality needed to add or edit classes of codes, codes, and attributes
2. This registry would provide the functionality needed to add or edit classes of codes, codes, and attributes