Glossary · Engineering, integration and validation
.NET integration
Also known as: DotNet integration
German: .NET-Integration
In industrial automation, .NET integration is the use of Microsoft's .NET platform to extend or connect automation systems, for example through APIs that automate engineering tools, .NET-based HMI or SCADA add-ins, or applications that exchange data with controllers.
- Validation
- Vendor product
In one sentence
.NET integration uses Microsoft's .NET platform to automate engineering tools, extend HMIs or connect applications to controllers.
Example
A C# program uses the engineering tool's .NET API to generate the hardware configuration and standard function block calls from the I/O list.
How it applies
- Engineering: Several automation vendors provide .NET interfaces that let programs create or modify engineering projects, which supports code generation from lists and Continuous integration (CI) pipelines.
- Operation: .NET applications can exchange data with controllers or HMIs, for example through vendor libraries or OPC UA client libraries.
- Security: Custom applications that access controllers must follow the plant's security rules for accounts, network access and updates, like any other software on the OT network.
- Documentation: The documentation team documents which API version and .NET runtime a tool or add-in requires and describes custom extensions so service staff can maintain them.
Keep in mind: .NET versions, vendor APIs and their feature sets change between releases. Check the names, supported versions and capabilities against the vendor's current documentation.