MIMOSA Asset Lifecycle Information Model Open Meeting Set

MIMOSA Asset Lifecycle Information Model Open Meeting Set

Manufacturing and production information is rapidly moving to the cloud. I wrote yesterday about what all the companies are trying to do to bring information into their ecosystems. Not all the efforts promote interoperability. Dell is open source, coming the closest to the ideal. Microsoft and Siemens are closest for individual companies.

What they are all lacking is bringing in asset lifecycle information.

Enter MIMOSA, developer and proponent of the most complete asset lifecycle information model. CCOM has been publicly proved in the Oil & Gas Pilot Demo Project and in several private company instances.

Another drawback to these systems occurs when a company implements more than one. Let’s suppose that a company installs both SAP and Microsoft. And then maybe GE Predix. How are these proprietary systems all going to get along together?

MIMOSA has a solution—web service Information Service Bus Model the heart of the Open Industrial Interoperability Ecosystem (OIIE). These open standards describe how to tie together all the parts into an interoperable industrial system.

These standards plus current efforts to define Industry Standard Datatsheet Definition and a joint working group to write a companion specification with OPC UA will be discussed at the open meeting.

There will be an MIMOSA meeting  on Sept. 28-29. All are invited to attend. BP Helios Center, 201 Helios Way, Houston, Texas 77079

More information coming.

For deeper information on MIMOSA click on the white paper small ad on the right.

MIMOSA Asset Lifecycle Information Model Open Meeting Set

MIMOSA Annual Meetings To Tout Interoperability Successes

MIMOSA has announced its MIMOSA Open Meeting and Annual MIMOSA Members Meeting to be held in Houston, Texas at the BP Upstream Learning Center on Nov 29 and 30, 2016. The Open Meeting will take place on Nov 29, while the Members Meeting will take place on Nov 30.  The address for both meetings is BP America Inc, 2 Helios Way, Houston, TX 77079.

The focus of the MIMOSA Open Meeting is to highlight recent developments and progress toward adoption of interoperability standards between MIMOSA and cooperating industry organizations enabling the Open Industrial Digital Ecosystems based on the Open Industrial Interoperability Ecosystem (OIIE). The OIIE provides a pragmatic option to proprietary ecosystems. It is developed in a fully cooperative manner with multiple industry standards organizations, so that it is fully open and supplier neutral, while allowing the use of Commercial Off The Shelf solutions from suppliers of all types and sizes.  The agenda for the MIMOSA Open Meeting is still being finalized, but the starting time will be 9:00 AM CT on Nov 29 and it will finish at 4:00 PM.  Owner/Operators, EPCs, Integrators, Equipment OEMs, Software Suppliers and Industrial Media participants are welcomed.

The MIMOSA Members Meeting on Nov 30 will focus on areas of greatest interest to our members, including Owner/Operators, EPCs, Equipment OEMs, Software Suppliers and invited guests. The MIMOSA Annual Business Meeting will be included in the day’s events. The MIMOSA Members Meeting will start at 9:00 AM on Nov 30 and conclude at 5:00 PM.

To reserve your spot at this important meeting, please email [email protected]. Further information will be made available on the MIMOSA website at www.mimosa.org.

MIMOSA Asset Lifecycle Information Model Open Meeting Set

MIMOSA Announces SAP Membership to Support Interoperability Standards

This announcement reveals important advances in the cause of suppliers, owner/operators, and standards organizations coming together to support and use interoperability standards. Much progress has been made since the OGI Pilot demonstration in 2009. I have written two white papers on the subject that you can download here.

MIMOSA, which provides information standards for physical asset management, announced Nov. 1, 2016 that SAP has joined the organization to incorporate MIMOSA’s industry standards on SAP Asset Intelligence Network. Alan Johnston, president of MIMOSA said, “I am very pleased to have SAP join MIMOSA and support the Open Industrial Interoperability Ecosystem. This way, we expect that many more of the owner/operators in asset-intensive industry groups will gain business value from SAP Asset Intelligence Network running on the new SAP HANA Cloud Platform when they leverage our open standards.”

MIMOSA provides a broadly used portfolio of industry standards for physical asset management and leads the development of the Open Industrial Interoperability Ecosystem (OIIE), in cooperation with other industry standards associations. Ken Dunn from BP, who is chairman of the MIMOSA board, explained: “The OIIE incorporates a portfolio of international and industry standards which enable sustainable standards-based interoperability. It is designed to dramatically reduce the cost of integration across a heterogeneous information technology environment and to facilitate the Industrial Internet of Things (IIOT). The OIIE is even more important in economically challenging times, as it helps owner/operators reduce cost and complexity, while continuing to sustain critical programs around asset integrity management and operational risk management. SAP’s commitment to these industry standards is a major step forward in their widespread adoption.”

SAP Asset Intelligence Network will provide a global registry of industrial equipment designed to enable collaborative business models. Achim Krueger, VP of Global Solutions for the SAP Extended Supply Chain (which includes Asset Management and HSE), commented, “Being part of this interoperability standards organization will become a key support of SAP Asset Intelligence Network, benefitting our entire ecosystem of manufacturers, engineering suppliers and asset operators. The intent is to enable them to automatically exchange their asset management data and reduce manual steps in the process. This is a great example of how SAP continues to work with the industry to co-innovate new solutions that are important for our customers.”

Ken Evans, head of SAP Global O&G Business Unit, stated, “As our customers digitally transform their global operations, they need greater flexibility in their business and operations technology platforms. We view joining MIMOSA as an important step to support their ability to openly integrate SAP Asset Intelligence Network with their ecosystem of service providers. We are excited to continue our innovations with the O&G industry and to utilize standards to improve overall enterprise process efficiency and access to operational content.”

Plethora Of Protocols

Plethora Of Protocols

Purdue and Information FlowI’ve spent way too much time on the phone and on GoToMeeting over the past several days. So I let the last post on the hierarchy of the Purdue Model sit and ferment. Thanks for the comments.

Well, I made it sound so simple, didn’t I? I mean, just run a wire around the control system and move data in a non-hierarchical manner to The Cloud. Voila. The Industrial Internet of Things. Devices serving data on the Internet.

Turns out it’s not that simple, is it?

First off, “The Cloud” is actually a data repository (or lots of them) located on a server somewhere and probably within an application of some sort. These applications can be siloed like they mostly are now. Or maybe they share data in a federated manner—the trend of the future.

To accomplish that federation will require standardized ways of describing devices, data, and the metadata. I’ll have more to say about that later relative to some white papers I’m writing for MIMOSA and The OpenO&M Initiative.

Typically data is carried by protocols. OPC (and its latest iteration OPC UA) has been popular in control to HMI applications—and more. Other Internet of Things protocols include XMPP, MQTT, AMQP. Maybe some use JSON. You may have heard of SOAP and RESTful.

Will we live with a multiplicity of protocols? Can we? Will some dominant supplier force a standard?

Check out these recent blogs and articles:

GE Blog – Industrial Internet Protocol Wars

FastCompany, Why the Internet of Things Might Never Speak A Common Language

Inductive Automation Webinar — MQTT the only control protocol you need

OPC – Reshape the Automation Pyramid (is OPC UA all you need?)

Interoperability Among Protocols

What we need is something in the middle that wraps each of the messages in a standard way and delivers to the application or Enterprise Service Bus. Such a technology is described by the OpenO&M Information Service Bus Model that is the core component of the Open Industrial Interoperability Ecosystem (OIIE) that I introduced in the last post. The ISBM is actually not a bus, per se, but a set of APIs based on Web Services. It is also described in ISA 95 Part 6 as Message Service Model (MSM).

OIIE Architecture

The MSM is described in a few points by Dennis Brandl:

  • Defines a standard method for interfacing with different Enterprise Service Buses
  • Enables sending and receiving messages between applications using a common interface
  • Reduces the number of interfaces that must be supported in an integration project

Here is a graphic representation Brandl has developed:

ISA 95 MSM

These are simple Web Services designed to remove complexity from the transaction at this stage of communication.

Follow this blog

Get a weekly email of all new posts.