Full Report
Explore the what, why and who of open standards and open automation, including the challenges, partnerships and benefits, including AI and edge computing integration.
Analysis Summary
# Best Practices: Adopting Open Standards in Software-Defined Automation (SDA)
## Overview
These practices focus on leveraging open standards and technology partnerships within Software-Defined Automation (SDA) strategies to enhance interoperability, flexibility, and future-proofing of industrial automation systems, particularly in contexts involving digital transformation, AI, and edge computing integration.
## Key Recommendations
### Immediate Actions
1. **Identify Key Open Standards:** Immediately inventory and document the critical open standards relevant to your current operational technology (OT) and IT environments, specifically naming **OPC UA**, **MQTT**, and **IEC 61499**.
2. **Review Partner Ecosystem:** Assess current automation vendors and solutions to determine the degree to which they rely on proprietary standards versus those based on open standards (e.g., checking if solutions are based on platforms like EcoStruxure Automation Expert).
### Short-term Improvements (1-3 months)
1. **Develop an Open Standards Adoption Roadmap:** Create a phased plan for migrating away from heavily proprietary components toward solutions that mandate support for identified open standards (OPC UA, MQTT, IEC 61499).
2. **Pilot Integration Projects:** Initiate small, defined projects to integrate two disparate systems using a standardized open protocol (e.g., using MQTT for data transport between a legacy PLC and a new cloud analytics service).
3. **Establish Technology Partnerships:** Actively seek out and formalize beneficial partnerships with organizations committed to open industrial automation (e.g., collaborating with organizations affiliated with UniversalAutomation.org where applicable).
### Long-term Strategy (3+ months)
1. **Integrate Open Standards into Procurement Policy:** Mandate that all new automation hardware and software acquisitions must demonstrate native support (not just via middleware layer) for critical open standards as a primary evaluation criterion.
2. **Develop Edge/AI Strategy based on Open Data:** Ensure the long-term strategy for integrating Artificial Intelligence and Edge Computing leverages open standards (like OPC UA for data access) to guarantee portability and reduce vendor lock-in at the network edge.
3. **Ensure IEC 61499 Adoption for Future Flexibility:** Begin planning for the implementation of IEC 61499 capabilities to enable function portability across different hardware platforms, significantly enhancing system flexibility.
## Implementation Guidance
### For Small Organizations
- **Focus on Data Exchange:** Prioritize implementing MQTT for lightweight, bidirectional data exchange, as it is often easier to adopt incrementally for basic sensor/device connectivity than full system overhauls.
- **Utilize Pre-built Open Solutions:** Favor commercially available, pre-integrated software solutions (like Schneider Electric’s EcoStruxure Automation Expert) that are explicitly built on open standards to reduce internal development burden.
### For Medium Organizations
- **Standardize on OPC UA for Machine-to-Machine (M2M):** Mandate OPC UA as the standard communication protocol for all new machine interfaces and HMI/SCADA data acquisition layers to ensure robust, secure, and standardized data modeling.
- **Cross-Train Personnel:** Invest in training engineering teams specifically on the architectural principles of IEC 61499 to future-proof application development and deployment skills.
### For Large Enterprises
- **Centralized Standards Governance:** Establish a dedicated Digital Transformation or OT Governance body responsible for enforcing adherence to open standards across all business units and global sites.
- **Legacy Modernization Strategy:** Develop a specific, budgeted plan for retiring proprietary communication layers and replacing them with compliant open standards, often starting with supervisory layers before moving to control layers.
- **Global Collaboration Frameworks:** Leverage open standards to facilitate global collaboration and standard data models, ensuring successful digital transformation and data analytics integration across various geographical operations.
## Configuration Examples
*No specific configuration commands or syntax examples were provided in the source material, as the content was a description of a webinar focusing on concepts and standards definitions.*
## Compliance Alignment
The focus on open standards aligns with broader industry goals promoted by standards organizations:
- **ISA** (International Society of Automation): Pertaining to standards like OPC UA, which ISA is heavily involved in promoting.
- **IEC 61499:** Directly relates to the standard for distributed control systems and function block application-portability.
## Common Pitfalls to Avoid
- **Assuming "Open" Means "Zero Cost":** Recognize that adopting open standards requires investment in training, system redesign, and potentially new middleware/software layers.
- **Vendor Lock-in Disguised as Interoperability:** Be cautious if a vendor claims "openness" but requires proprietary licenses or specific toolchains to fully utilize the open protocols—ensure true vendor neutrality.
- **Ignoring Data Format Standards:** Do not focus solely on the transport protocol (like MQTT); ensure the actual data payload structure also adheres to open industrial standards (e.g., using standardized OPC UA Information Models).
## Resources
- **Standards Focus Areas:** OPC UA, MQTT, IEC 61499.
- **Organizational Reference:** Consult documentation or experts associated with **UniversalAutomation.org** for guidance on open automation principles.
- **Product Example Reference:** Investigate solutions based on underlying open standards, such as **Schneider Electric’s EcoStruxure Automation Expert**.