Glossary · Systems engineering and MBSE
Open systems
Also known as: Open architecture
German: Offene Systeme
In automation, open systems are control and communication systems based on published, vendor-independent standards and interfaces, so that components from different manufacturers can be combined, exchanged and integrated.
- Integrated systems
- Data and interfaces
In one sentence
Open systems use published, vendor-independent standards and interfaces so components from different manufacturers can work together.
Example
A plant operator specifies OPC UA and IEC 61131-3 so that machines from different builders can be integrated into one line control.
How it applies
- Engineering: Openness reduces vendor lock-in and eases integration, but interoperability still requires agreed profiles, versions and testing.
- Security: Open interfaces must still be secured; openness is not the same as unrestricted access.
- Documentation: Documentation should state exactly which standards, profiles and versions are supported; the documentation team should avoid a vague "open interface" claim.
- Procurement: Specify open interfaces with named standards and versions in purchase specifications.
Open systems can make later migration easier, because components can be replaced without redesigning all interfaces. Openness should be verified in interoperability tests rather than assumed from a datasheet.
Open systems vs. open-source software
Open systems are about standardized interfaces; the products themselves can be proprietary. Open-source software is about the license of the code.