by Gary Mintchell | Nov 8, 2017 | Interoperability, Operations Management, Software, Standards
Iconics has been a long-time supporter of OPC Foundation and an early adopter of OPC UA. President Russ Agrusa has seen the power and benefits of OPC as an information model for open interchange of data among industrial automation devices.
Thomas Burke, president of the OPC Foundation presented a keynote on the technology and benefits of OPC UA and the status of working with a variety of protocols such as Time Sensitive Networking, MQTT, AMQP, and others. I have written a white paper on TSN and OPC that you can download here.
The company provides advanced web-enabled OPC UA certified visualization, analytics, and mobile software solutions for any energy, manufacturing, industrial or building automation application. OPC is obviously a popular topic with Iconics developers as revealed by the packed session and probing questions.
“Connected Intelligence is our theme at this year’s customer summit and it all about connectivity to every “thing” in the Industrial Internet of Things (IIoT), which is critical for today’s manufacturing, industrial, and building automation systems. The OPC Unified Architecture (OPC UA) is the core standard for Industry 4.0 and IIoT. ICONICS works closely with the OPC Foundation and its technical committees to help create new standards that have applications in many industries.
“As a member of the OPC Board of Directors, I am proud to promote its many specifications and wide-reaching standards for manufacturing, industrial, and building automation,” says Russ Agrusa, President and CEO of ICONICS.
“I have presented at many ICONICS Worldwide Customer Summits over the years and I find meeting the wide variety of ICONICS customers, partners, and integrators from around the world to be rewarding. ICONICS early support and extensive commitment to OPC for over 20 years has helped propel OPC to where it is today,” says Thomas Burke, President of the OPC Foundation.
The ICONICS community of partners, system integrators and customers will learn from top industry experts how the OPC Foundation is driving the next wave of solutions for Industry 4.0 and the Industrial Internet of Things.
Takeaway: OPC UA has been recognized as an essential standard by Industie 4.0 in Germany and is a central technology for industrial data communication for software applications such as Iconics.
by Gary Mintchell | Sep 27, 2017 | Automation, Standards
This article appeared in TechCrunch. It’s pretty IT oriented, but the thoughts are relevant for the OT world, too.
The author, Ron Miller, reported that Amazon’s AWS move to join an industry standard on a technology known as containers signals the importance of standards.
Get Smart: Standards develop in a number of ways. Not all of them are ISA or ISO or IEC, although these definitely have a place. An industry leader once told me, “Gary, the best industry standards are de facto standards.” These are the ones that build a critical mass among users and developers and that solve real problems.
When AWS today became a full-fledged member of the container standards body, the Cloud Native Computing Foundation, it represented a significant milestone. By joining Google, IBM, Microsoft, Red Hat and just about every company that matters in the space, AWS has acknowledged that when it comes to container management, standards matter.
Does this sound familiar to the industrial automation market? AWS has been known to go the proprietary route, after all. When you’re that big and powerful, and control vast swaths of market share as AWS does, you can afford to go your own way from time to time. Containers is an area it hasn’t controlled, though. That belongs to Kubernetes, the open source container management tool originally developed inside Google.
What does it take for standards to win? Once it recognized Google’s dominance in container management, the next logical step was to join the CNCF and adhere to the same container standards the entire industry is using. Sometimes it’s better to switch than fight, and this was clearly one of those times.
The reason for standards. Standards provide a common basis for managing containers. Everyone can build their own tools on top of them. Google already has when it built Kubernetes, Red Hat has OpenShift, Microsoft makes Azure Container Service — and so forth and so on.
As for end users: Companies like standards because they know the technology is going to work a certain way, regardless of who built it. Each vendor provides a similar set of basic services, then differentiates itself based on what it builds on top.
Benefits for all: Technology tends to take off once a standard is agreed upon by the majority of the industry. Look at the World Wide Web. It has taken off because there is a standard way of building web sites. When companies agree to the building blocks, everything else seems to fall into place.
by Gary Mintchell | Aug 31, 2017 | Interoperability, News, Operations Management, Standards
Looks like standards and interoperability week at The Manufacturing Connection. I once was pretty active with MESA and lately I’ve gotten to know the IIC. Both good organizations promoting best practices in industry. MESA is not a standards organization, though, but one that promotes Level 3 (MES/MOM) software applications. IIC has taken a leadership roll bringing Internet of Things people and companies together.
The Industrial Internet Consortium (IIC) and the Manufacturing Enterprise Solutions Association (MESA) International announced they have signed a memorandum of understanding (MoU) to work together to advance their shared interests. Under the agreement, the IIC and MESA will work together to align efforts to maximize interoperability, portability, security and privacy for the industrial Internet. That all sounds pretty vague and something like motherhood, but I applaud all steps toward collaboration.
Joint activities between the IIC and the MESA will include:
- Identifying and sharing IIoT best practices
- Realizing interoperability by harmonizing architecture and other elements
- Collaborating on standardization
- Collaboration in the areas of industrial analytics and asset performance management (APM)
MESA’s President, Mike Yost, said, “This partnership makes good business sense, with the Industrial Internet Consortium advocating for the broad adoption of industrial Internet technologies and with MESA educating manufacturers and solution providers of all sizes on both how and why to adopt them. Collaborating with the IIC also helps ensure MESA members and IIC members have a common vocabulary and a common understanding of business value.”
“We look forward to working with the Manufacturing Enterprise Solutions Enterprise Association,” said Wael William Diab, IIC Chair of the Liaison Working Group. “Within the manufacturing vertical, industrial analytics and asset intelligence systems enable manufacturers to realize the value of their industrial IoT systems by analyzing and acting on data to increase asset reliability and availability and reduce maintenance. Collaborating on industrial analytics and asset performance management will help to further advance industrial IoT in manufacturing environments.”
MESA and the IIC have agreed to meet regularly to exchange information and have targeted a joint workshop on industrial analytics and asset performance management for Q4. The IIC Liaison Working Group is the gateway for formal relationships with standards and open-source organizations, consortia, alliances, certification and testing bodies and government entities/agencies.
The agreement with the MESA is one of a number of agreements made by the IIC’s Liaison Working Group.
Here is a little more information about the IIC.
The Industrial Internet Consortium maintains active relationships with standards development organizations, open-source organizations, other consortia and alliances, certification and testing bodies and government entities or agencies involved in the Industrial Internet.
The purpose of these relationships is to generate requirements for new standards from every part of the activities taking place within the Industrial Internet Consortium.
These relationships help eliminate duplication of effort and ensure that new standards and technologies necessary to build and enable the Industrial Internet are brought to market more rapidly.
By establishing a formal liaison with the Industrial Internet Consortium, organizations can engage directly with our Working Groups and gain faster access to developing requirements for standards and technologies required for the Industrial Internet across a spectrum of industries and applications.
The Industrial Internet Consortium itself is not a standards organization; however, it strongly advocates for open standard technologies in order to ease the deployment of connected technologies. Our Liaison Working Group is the gateway for the liaison relationships listed below and new ones forming now.
by Gary Mintchell | Aug 28, 2017 | Automation, Organizations, Process Control, Standards
The future of process automation was front and center of discussions last week at the Foxboro User Group—The Foxboro Company being the process automation arm of Schneider Electric.
During the week I was involved in quite animated discussions with SVP Chris Lyden and VP Peter Martin regarding the future of process automation. These executives are convinced that there is an inflexion point we are reaching where we are returning to the open architecture we started with years ago. The pendulum swung toward centralized, integrated systems. Technology has progressed to a point of realizing the old dream of distributed control, interoperable systems, systems of systems, and open systems based on standards.
Martin used his closing remarks to the group to talk about the Open Process Automation Forum, which is organized under The Open Group. You may recall I’ve written about this group following each of the last two ARC Industry Forums in Orlando.
The spark was provided by a group from ExxonMobil who saw a dire need to upgrade its systems. Leaders looked at the huge upfront cost of the control upgrade plus the likelihood of being locked into a single supplier and then facing huge lifecycle costs during the life of the equipment.
“When we released our first DCS 30 years ago, we tried to make it as open as possible,” said Martin. “We felt for future innovation, the system needed to be as open as possible. But the level of standards necessary just didn’t exist.”
When ExxonMobil said they wanted to build an open platform, “we jumped in” added Martin.
Foxboro’s Trevor Cusworth is co-chair of the OPAF. He asked attendees to consider the benefits of joining in the effort. “We need more end users,” he said, “since we have only about 11 right now.”
The key benefit noted was reducing lifecycle costs, while the key technology is a new type of I/O.
From the OPAF brochure:
Not only can you contribute to the creation and development of a new process automation system, you can also:
- Ensure your experience and requirements are included
- Advocate that your industry sector is represented
- Validate that existing standards important to you are used
- Sustain the benefits of the standard and subsequent certification programs
Takeaways: This is an ambitious undertaking. The last one of these I saw eventually fell apart due to a “vicious circle”—suppliers got into the discussion hoping for new sales or the ability to knock off the incumbent; end users failed to not only write the system into their specs even if they did they weren’t enforced; suppliers lost interest due to no sales.
One important thing: If this catches on, it will greatly shake up the process automation supplier market.
by Gary Mintchell | Aug 22, 2017 | Standards
Standards that enable interoperability drives innovation and industry growth.
For some reason, technology suppliers tend to avoid standards at almost all costs—and the costs can be substantial in terms of losing market share or momentum—in order to build a “complete” solution all their own.
One reason beyond the obvious is that standards creation can be a time-consuming and tedious process.
Where would we be without standardized shipping containers, standardized railway tracks and cars, standardized Ethernet and the ISO stack, and more?
I’ve been working with OPC Foundation and am finishing a white paper about the technology of combining two standards—OPC UA and Time Sensitive Networking. This is going to be huge some day.
I also work with a standards organization known as MIMOSA which has promulgated an information standard for asset lifecycle management.
These are key technologies that can move industry forward
I ran across this article by Ron Miller on TechCrunch about standards in another area—cloud services. This article discusses Amazon Web Services (AWS).
AWS just proved why standards drive technology platforms
Quoting from Miller:
When AWS today became a full-fledged member of the container standards body, the Cloud Native Computing Foundation, it represented a significant milestone. By joining Google, IBM, Microsoft, Red Hat and just about every company that matters in the space, AWS has acknowledged that when it comes to container management, standards matter.
AWS has been known to go the proprietary route, after all. When you’re that big and powerful, and control vast swaths of market share as AWS does, you can afford to go your own way from time to time. Containers is an area it hasn’t controlled, though. That belongs to Kubernetes, the open source container management tool originally developed inside Google.
AWS was smart enough to recognize that Kubernetes is becoming an industry standard in itself, and that when it comes to build versus buy versus going open source, AWS wisely recognized that battle has been fought and won.
What we have now is a clearer path to containerization, a technology that is all the rage inside large companies — for many good reasons. They allow you to break down the application into discrete manageable chunks, making updates a heck of a lot easier, and clearly dividing developer tasks and operations tasks in a DevOps model.
Standards provide a common basis for managing containers. Everyone can build their own tools on top of them. Google already has when it built Kubernetes, Red Hat has OpenShift, Microsoft makes Azure Container Service — and so forth and so on.
Companies like standards because they know the technology is going to work a certain way, regardless of who built it. Each vendor provides a similar set of basic services, then differentiates itself based on what it builds on top.
Technology tends to take off once a standard is agreed upon by the majority of the industry. Look at the World Wide Web. It has taken off because there is a standard way of building web sites. When companies agree to the building blocks, everything else seems to fall into place.
A lack of standards has traditionally held back technology. Having common building blocks just make sense. Sometimes a clear market leader doesn’t always agree. Today AWS showed why it matters, even to them.
by Gary Mintchell | May 31, 2017 | Standards
Joint working groups to develop companion specifications has been a great method to advance interoperability. Here is an announcement of one where you can still get involved if you have expertise in one or the other. Note: I am chief marketing officer of MIMOSA and I also have done some work with OPC Foundation.
MIMOSA (an operations and maintenance information open system alliance) and the OPC Foundation have announced a joint working group to develop a companion specification for MIMOSA’s CCOM standard and OPC UA.
MIMOSA is a not-for-profit trade association dedicated to developing and encouraging the adoption of open information standards for Operations and Maintenance in manufacturing, fleet, and facility environments. MIMOSA’s open standards enable collaborative asset lifecycle management in both commercial and military applications.
MIMOSA CCOM (Common Collaborative Object Model) serves as an information model for the exchange of asset information. Its core mission is to facilitate standards-based interoperability between systems: providing an XML model to allow systems to electronically exchange data.
OPC Foundation is a not-for-profit association dedicated to providing the interoperability standard for the secure and reliable exchange of data in the industrial automation space and in other industries. The OPC UA (Unified Architecture) is platform independent and ensures the seamless flow of information among devices from multiple vendors.
The OPC UA standard is a series of specifications developed by industry vendors, end-users and software developers. These specifications define the interface between Clients and Servers, as well as Servers and Servers, including secure access to real-time data, monitoring of alarms and events, access to historical data and other applications. The standard includes the ability to securely transport any information model between the systems. It is a key standard for Industry 4.0.
The joint MIMOSA and OPC Foundation CCOM OPC UA Working Group will develop an OPC UA Information Model for CCOM. The information model specified by CCOM will be defined in a UA companion specification using OPC UA constructs for the purpose of exposing CCOM information to OPC UA applications, with an initial focus on existing Use Cases relating to information exchange to and from the control system. This will combine existing strengths of each organization for some near-term wins, where OPC UA is used to bring information from the factory floor and where MIMOSA plays its traditional role in Asset Management.
The working group will deliver the following:
• OPC UA Information Model for CCOM (Standard OPC UA companion specification, Nodeset file and prototype implementation)
• A write up for the OPC Wiki describing the Companion specification
• Trade show demonstration and information material
Anyone who would like to contribute to this industry specification please contact Alan Johnston [email protected].
