A guide to APIs in process automation
The Industrial Internet of Things (IIoT) has introduced new approaches to retrieve field data. When integrating this data into another application or developing custom services, application programming interfaces (APIs) become essential.
요약
- Operational technology (OT) and information technology (IT) were once separate domains, rarely overlapping.
- Collaboration occurred only in specific cases, such as implementing plant asset management (PAM) solutions, where IT ensured firewall compatibility and provided servers.
- Today, OT networks increasingly resemble IT networks, using protocols like PROFINET and EtherNet/IP.
- Field devices now rely on Ethernet connections, and gateways integrate technologies such as WirelessHART, HART, or PROFIBUS into Ethernet-based systems using standards like EtherNet/IP or OPC UA.
- The rise of the Industrial Internet of Things (IIoT) and frameworks like Namur Open Architecture (NOA) enable data from the automation pyramid to support value-added services.
- To integrate this data into applications or develop custom solutions, application programming interfaces (APIs) are essential.
- APIs provide the connectivity that makes modern automation flexible, scalable, and ready for digital transformation.
What is an API?
API stands for application programming interface, but what does this term actually mean? An API is a computing interface that manages multiple user requests to create, delete, and deliver information. It can be customized to provide specific features, depending on the developer’s design.
To clarify how it works, consider this analogy: Imagine visiting a store for a new pair of shoes. The store offers many models, but a specific color and size are required. A salesperson checks the stock and returns with the exact pair requested.
In this analogy, the user is the customer seeking specific information, the salesperson acts as the messenger handling requests, and the stock represents the API that processes and delivers results.
A more practical example is a flight booking website. Users enter details such as departure and arrival dates, airports, and seating preferences.
When the request is submitted, the site communicates with multiple APIs from different companies. These APIs return options based on the criteria provided, and some platforms even allow booking and applying discounts directly.
APIs are deeply integrated into modern digital services. They operate behind the scenes, enabling seamless functionality that users benefit from without realizing it.
How does an API work in process automation?
APIs provide significant opportunities to enhance applications in industrial environments. One example is Netilion Connect from Endress+Hauser, which offers a secure and user-friendly REST/JSON API.
The Netilion Connect architecture typically includes an edge device, a cloud platform, and the API, although it can also function without the edge device. The service incorporates authentication and authorization mechanisms to ensure reliability and security. Data collected from the field via an edge device is made available in a protected environment, enabling flexible integration into various applications.
This data can be utilized in numerous ways. For instance, an application could retrieve cloud-based information through the API to display instrumentation status in customized service platforms, send notifications to team members regarding issues and resolutions, or design dashboards with device data for performance analysis. Such scenarios demonstrate the versatility of APIs in process automation. Find out here how the skid provider BWT used the Netilion Connect API to make documentation available in the service portal which customers access.
As IT and OT continue to converge, skills such as JavaScript and JSON coding are becoming increasingly important for automation professionals. Tools like Netilion Connect allow users to experiment with real APIs for process automation and even develop custom applications.
