“From the PLC side, the Auto industry began major efforts to drive standards in the 1990’s like GM’s MAP mfg automation protocol. However, after a decade they realized that even with their leadership and size, the Big Three and their top tier suppliers couldn’t get PLC vendors to agree on a standard. So in 2000, they decided it would literally take an “Act of Congress” to get vendors to agree. Two years later, a bipartisan Congress passed the Manufacturing Enterprise Integration Act of 2002 giving NIST over $150 million to develop and drive Interoperability protocols and standards. What happened next? President Bush never approved the budget for NIST to do it because he philosophically didn’t believe that the federal government should be creating standards. Thus, 25 years later we still have nothing — because this problem is like solving world hunger or world peace. It’s too big. “
Good recap, John.
Then there were PC standards
In those days, there was a PC standard. Actually, there were a few. There was an “XT” bus that standardized PCs on what became known as the PC platform. In the late 80s, IBM thought it would get fancy and recapture some proprietary technology it lost with the XT platform. Anyone remember Microchannel?But then PCI came along driven more by chip makers, I believe, to take the backplane to another level without being vendor specific.
I actually took classes and may still have a certificate around the house having passed tests on IBM’s proprietary, or sort-of proprietary, technologies. Remember also Token Ring? Yep, that was another. The third test had something to do with finance applications on the PC.
In those days you could build cards to plug into the bus. Only Apples were locked down.
There was an “embedded” PC world dominated by VMEbus and in the mid-late 90s PCI and then CompactPCI. PLCs were generally built on a modified VME but nothing was standard.
None of these things I’m talking about were driven by government. IBM allowed its first PC bus to become an industry standard that other companies could build to–and the PC industry took off.
In the 90s the big automakers grew frustrated with what was essentially a single PLC source and tried a bunch of things. Maybe the government. Maybe they were big enough to drive a CompactPCI standard. All PLC manufacturers would build on a single CompactPCI standard. Anyone’s cards would fit in the backplane–just like the PC industry. You could load anyone’s operating system and programming software on the platform.
By driving hardware and then software to commodity, then the automakers could drive the cost dramatically down.
Since the 80s and 90s saw tremendous innovation around the standards driven PC platform, it was logical (to users) that similar innovation advances would be seen in the industrial “PC” market.
Many things were tried. Many things failed.
Trouble is–the industrial market is much smaller than the PC market. A commodity industrial market would drive incumbents to seek other markets. Innovation would dry up. Suppliers drove to protect their turf.
And innovation exploded.
We saw many things added to the PLC platform driven by competition (although reducing interoperability):
- PC technologies–memory, processing
- Integrated motion control
- Reduced footprint
- Innovative development studios
But, alas, if you bought Rockwell, you were stuck with Rockwell. Same with Siemens, and everyone else.
Users did reap some price concessions. Better, they reaped technology advances because the suppliers could afford to invest in new technology.
New technology cycle
Theses curves always run their cycle.
Where are we now? Is there any reason to need a standard platform PLC? Or has that technology curve been passed?
Do we need a single protocol for moving data in this brave new IoT world? Or, will suppliers build gateways that foster inter-communication–or a bus such as the ws-ISBM? And render the argument moot?