PipelineML 2.0 Candidate Conceptual Model

We’re excited to share the progress we’ve made on the PipelineML 2.0 conceptual model!

This updated version focuses on improving the clarity and consistency of inheritance relationships within the model. You’ll notice in the  UML diagram below that some features have been shifted between classes to achieve this goal.

Please keep in mind:

  • This is a work in progress, and the design is not yet finalized.
  • Do not build integrations or write code based on this model yet.

We welcome your feedback on the changes reflected in the latest version of the model.

Enterprise Products: A Collaborative Journey with OGC

Enterprise Products: A Collaborative Journey with OGC

Houston, Texas – February 20, 2024

In this article published by the Open Geospatial Consortium (OGC), an overview of  is given of Enterprise Products Partners, L.P.’s adoption of the PipelineML data interchange standards.

This is an article about how Enterprise Products collaborated with OGC to develop a standard for the pipeline industry. It discusses the benefits of using open standards and open-source technology. The article also highlights the importance of collaboration and community engagement. Some of the key points are that Enterprise Products helped develop the PipelineML Standard, which is used to improve the management of pipeline networks. They also implemented an open-source data architecture that provides a central location for data and services.

By clicking the above link, you will be sent directly to the OGC’s website, where you can read this article.

 

 

PipelineML 2.0 Status Update

We have been working in the background for several years now preparing for a 2.0 release of PipelineML. The data interchange standard is being used in production environments now and lessons are being learned on a daily basis as to how best to improve its design. We continue collecting this information and using it through iterations of design improvement lifecycles.

Continue reading

Blue Sky Evolution Orbital PipelineML Tutorial

In this video, you will see a tutorial showing how Blue Sky Evolution’s Orbital product integrates with PipelineML. You will discover how to export a PipelineML file out of the Orbital system.

PipelineML GeoPackager Released as Free Open-source QGIS Plugin

PipelineML GeoPackager Released as Free Open-source QGIS Plugin

Wayland, MA – February 12, 2021

The OGC PipelineML Standards Working Group today announced the release of a free open-source plugin for QGIS. This plugin converts a PipelineML file into a GeoPackage (an open geospatial data format that is readily understood by QGIS and other GIS software). Once a PipelineML file has been ingested into QGIS as a GeoPackage, the geospatial data can be visualized, all the PipelineML attributes displayed, and that data can be edited within the free open-source QGIS application.

Since QGIS already supports the import and export of many other data formats such as Shapefiles, GeoJSON, GeoRSS, and others, the PipelineML GeoPackager facilitates the conversion of PipelineML files to and from many other common data formats. “The addition of this plugin adds a considerable amount of value to the PipelineML data interchange ecosystem,” commented Jan Stuckens, Co-chair of the PipelineML Standards Working Group. Adding further, “Our goal with PipelineML is to make a rich array of free open-source solutions to the pipeline industry and this value proposition can be clearly seen in the release of this important resource.”

It is important to note that this plugin was developed through the PipelineML open-source development community. In this case, Jeff Bourdier, a software developer with 9 years of experience in the pipeline industry, volunteered to develop this plugin. “I’m pleased to have had the opportunity to contribute to this new OGC standard, which I believe will significantly improve data interoperability in the pipeline industry,” remarked Jeff. “Jeff has been a valuable addition to our developer community. We see a huge opportunity for open-source development within the oil and gas space. As data demands continue to increase, we must stay ahead of the growth curve with increasingly smarter and more flexible technologies and business processes. We believe PipelineML is just the start of an emerging trend to develop open-source solutions to meet pipeline market demands,” commented John Tisdale, Co-chair of the PipelineML Standards Working Group.

PipelineML GeoPackager is released under the GNU General Public License v3.0 license, which can be found here. The source code for the PipelineML GeoPackager is managed here. A tutorial on how to install and use this plugin can be found here. QGIS can be downloaded here. Jeff Bourdier can be reached on Github here and LinkedIn here.

The Open Geospatial Consortium (OGC) is an international consortium of more than 500 businesses, government agencies, research organizations, and universities driven to make geospatial (location) information and services FAIR – Findable, Accessible, Interoperable, and Reusable. OGC’s member-driven consensus process creates royalty-free, publicly available, open geospatial standards. Existing at the cutting edge, OGC actively analyzes and anticipates emerging tech trends, and runs an agile, collaborative Research and Development (R&D) lab – the OGC Innovation Program – that builds and tests innovative prototype solutions to members’ use cases. To learn more about OGC, visit ogc.org.

PipelineML is an open-source data interchange standard that allows pipeline operators, service providers, and software companies to freely exchange pipeline asset information in a free, open, universal international standard. To learn how your organization can benefit from the capabilities of PipelineML, visit pipelineml.org.

European Press Contact: Jan Stuckens

Phone: +32 2 3092 112

Email: jan.stuckens@merkator.com

U.S. Press Contact: John Tisdale

Phone: 713-381-5565

Email: jtisdale@eprod.com

How to Install and Use the PipelineML GeoPackager

Overview

This tutorial will help you install and use the PipelineML GeoPackager.

PipelineML GeoPackager is a QGIS plugin that reads a PipelineML file and translates its contents into a GeoPackage. This allows QGIS to natively consume and store PipelineML data for GIS analysis, and demonstrates the ability for PipelineML to be implemented in a fully open architecture. It is free, open-source software (FOSS), distributed under the GNU General Public License.

PipelineML GeoPackager is implemented as a processing plugin with an algorithm provider, so it can be run within the components of the QGIS processing framework (such as the graphical modeler or the batch processing interface) and thus integrated into more complex workflows. It requires QGIS version 3.0 (or higher).

Installation

The easiest way to install PipelineML GeoPackager is directly from the Plugin Manager dialog (within the QGIS application). For detailed instructions on how to do this, see QGIS Training Manual > Installing New Plugins. Alternatively, it can be downloaded in zipped format from the QGIS plugin repository and then installed using the Install from ZIP tab on the Plugin Manager dialog.

When the plugin is loaded, the provider PipelineML should appear in the Processing Toolbox, with an algorithm called PipelineML to GeoPackage. (The algorithm ID for Python scripting is pml:pml2gpkg.)

Usage

To execute the algorithm, double-click PipelineML to GeoPackage in the toolbox. The following dialog should appear.

The browse buttons can be used to help populate the parameters, which are explained in the table below.

LabelNameDescription
Source PipelineML fileINPUTFull path to the PipelineML file (e.g., C:\Data\PML-1.0-Official-Sample-Files-1\PML_Valid_Medium01.xml).
Destination GeoPackageOUTPUTFull path to the GeoPackage file destination (e.g., C:\Data\PML-1.0-Official-Sample-Files-1\PML_Valid_Medium01.gpkg), or empty to save to a temporary file.

Once the parameters are populated, click Run. The dialog should switch to the Log tab, which indicates progress as the algorithm executes.

When the algorithm is finished, the resulting layers in the GeoPackage are added to the current project in QGIS.

Development

PipelineML GeoPackager is written in Python using the GDAL (Geospatial Data Abstraction Library) API that ships with QGIS. Source code is hosted on GitHub, where you can report bugs, request enhancements, or otherwise become involved.

Blue Sky Evolution Integrates PipelineML into Orbital Product Line

Blue Sky Evolution Integrates PipelineML into Orbital Product Line

Houston, TX – December 7, 2020

Blue Sky Evolution today announced full integration of the Open Geospatial Consortium (OGC) PipelineML international pipeline data interchange standard into its Orbital product suite. The software extension provides functionality to leverage the PipelineML data standard to interchange pipeline survey data between Orbital, field surveyors and other data providers or consumers.

“We expect PipelineML to give our customers the ability to get survey and mapping data into the hands of project stakeholders quickly and easily. We are excited to be an early adopter of PipelineML because we believe it gives us a competitive advantage while providing our clients with a richer set of data management tools.”, Rene Ramirez, Blue Sky Evolution Owner & CEO.

PipelineML was developed over a 5-year period with the help of the (OGC), an organization that develops open geospatial data standards in use by businesses and government agencies around the world. PipelineML is a free, open data interchange standard that empowers pipeline stakeholders to move data between operators and service providers without the need for timely and costly and complex data transformation. This enables the oil and gas industry to streamline the movement of information to keep pace with the increasing demand for putting information into the hands of decision-makers quickly and efficiently.

“Blue Sky Evolution’s adoption of PipelineML provides pipeline operators as well as survey and mapping companies the ability to utilize the powerful capabilities of PipelineML to freely move data between different data providers, software applications, and devices. This will enable Blue Sky’s constituents to save time and money as they utilize modern data management standards like PipelineML to help them keep pace with evolving business requirements”, John Tisdale, Co-chair Open Geospatial Consortium PipelineML Standards Working Group.

To learn how your organization can benefit from the capabilities of PipelineML, visit pipelineml.org.

Download this press release as a PDF.

Name of Press Contact: Tazarra Berrien
Phone: (281) 980-9494
Email: tazarra@blueskyevo.com

Why We Are Not Actively Promoting PipelineML

We’re excited about PipelineML and the potential it holds, but we’re prioritizing responsible development over immediate publicity. Before we start promoting it heavily, we want to ensure its stability and effectiveness through real-world use cases. We’ll be integrating PipelineML into select production projects to gather valuable feedback that will guide potential improvements. This approach allows us to learn and iterate before making PipelineML widely available.

Continue reading

PipelineML Technical Specification Officially Published by OGC

After many thousands of hours of work by many people, the OGC published the official PipelineML Technical Specification that describes the abstract specification and XML/GML encoding standard. You will find the official publication at https://www.ogc.org/standard/pipelineml/. Feel free to let me know if you have any outstanding questions about the specification, or if you need any help in adopting the standard.

Continue reading

PipelineML Standard Approved by OGC

We have had considerable interaction with members of the OGC Architecture Board and Technical Committee over the past few months as our proposal has gone through a lengthy review process. Some minor tweaks were recommended by Carl Reed, who did a detailed assessment of the 300-page technical specification. After all the review and voting processes were complete, our proposal was approved by all stages and PipelineML is now an official OGC GML application schema standard for the interchange of geospatial data. It will take a bit longer for the specification to undergo editing by OGC staff before it is officially published on the OGC portal. Stay tuned for further updates.

Continue reading

PipelineML Standard Submitted

After many years of hard work on the part of countless individuals, today we submitted the abstract specification along with an encoding standard for PipelineML to the Open Geospatial Consortium (OGC) for consideration of approval. We intentionally kept the scope of this first version small and focused only on defining the characteristics of the coterminous components (linepipe, meters, valves, reducers, etc.), appurtenances (casings, coatings, sleeves, etc.), and connectors (girthwelds, tees, taps, etc.). By limiting the scope to only these pipeline assets, it leaves the future open to aligning with other existing standards, as well as expansion into other areas as we partner with other subject matter experts. We are looking forward to seeing how the OGC receives this proposal, and where we go from here.

Continue reading

PipelineML Conceptual Model Established

After years of collaborative work, we have finally gotten agreement from all parties on the following abstract class model. This shows the inheritance of all objects/features that will be supported in this initial version of PipelineML. We would love to get your thoughts and feedback as we continue to mature this oil and gas midstream asset data interchange standard.

Continue reading

PipelineML Scope Established

We have spent a consider amount of time determining the initial scope for PipelineML. We want the scope to be fairly narrow because we want just enough that we can complete it in a reasonable amount of time. We also want to leave plenty of room in the future to work in conjunction with other standards where there may be overlap in scope. We expect to expand the scope as time goes and we determine which priorities are commonly shared among stakeholders. For now, see the diagram below as it shows the scope we have determined for PipelineML 1.0.

Continue reading

OGC PipelineML SWG Meeting – 2017 Southampton, UK

We held our quarterly OGC technical committee meeting on September 13, 2017 at the Southampton, UK event. The meeting was well attended (both physically in UK as well as online). Discussion was robust and many individuals contributed to the discussions on how best to advance this standards development initiative. The meeting agenda included the following:

Continue reading

OGC PipelineML SWG Meeting – 2017 St. John’s, Newfoundland

A meeting on the PipelineML standards initiative took place in St. John’s, Newfoundland on June 28th, 2017. Discussions centered on recent progress, including the completion of core component definitions and reference codes, as well as ongoing challenges like component attribute inheritance and avoiding redundancy with other standards. The group also explored potential harmonization with LandInfra and planned an upcoming interoperability experiment to further develop the initiative.

Continue reading

OGC PipelineML SWG Meeting – 2017 Delft, The Netherlands

A PipelineML SWG meeting was held in Delft, Netherlands on March 23, 2017. The meeting focused on the status of the PipelineML standard and next steps for development. Discussions included revisions to the conceptual model and modular schemas, the potential for including offshore assets and merging with the LandInfra standard, and the definition of core component attributions. The meeting also addressed future considerations for the standard, such as cathodic protection, safety, and regulatory requirements. Finally, the meeting outlined various ways for attendees to participate in the development of the PipelineML standard.

Continue reading

OGC PipelineML SWG Meeting – 2016 Taichung, Taiwan

The OGC PipelineML SWG held a low-attendance quarterly meeting in Taichung, Taiwan, due to the inconvenient time zone. The meeting covered introductory topics, reviewed the conceptual model and ongoing discussions with LandInfra, and planned for a future meeting in Delft, Netherlands with the expectation of higher attendance and a more convenient time.

Continue reading

Status Update

We are making excellent progress on the list of attributes to be supported in the first version of PipelineML. As you may know, Jan Stuckens in Belgium was voted in as a co-chair of the Standards Working Group. We are holding weekly conference calls where we are going through our individual lists of component attributes and determining matches, overlaps and gaps. It is an arduous process. However, the results are quite encouraging. We are finding over 90% matches. The remaining 10% of attributes are being flagged for inclusion or exclusion based on our discussions.

Continue reading

OGC PipelineML SWG Meeting – Orlando 2016

Our OGC Technical Committee meeting held on September 21, 2016 in Orlando, FL USA went well. This was the 100th occurrence of the OGC TC meetings. We briefly reviewed decisions made in previous meetings. We discussed our concepts for modularizing our schema and presented a package dependency UML diagram that illustrated our concepts. There was solid agreement on the approach. Jan Stuckens and I presented the most recent version of our conceptual model as a UML class diagram.

Continue reading

OGC PipelineML SWG Meeting – Dublin 2016

This week, the PipelineML SWG meeting focused on several key topics:

Standardization progress: The group discussed ongoing revisions to the core schema based on prototyping, refined component definitions, and reference code lists. They also aimed to prepare for a major revision in September.
New co-chair: Jan Stuckens from Belgium was elected as the new co-chair to replace Terry Strahan.
Internationalization: The meeting addressed challenges of international unit of measure standardization and potential approaches like custom enumerations or leveraging existing resources. They also discussed best practices for handling international encoding and terminology.

Continue reading