Different technology stacks are used for machine connectivity interfaces across the industry, ranging from self-developed REST APIs to data models like MTConnect. 3YOURMIND uses the OPCUA/umati standard to harmonize this data. Despite our efforts, the support for our desired Use Cases varies based on the technologies (and their implementations). Find out more below:
Use case coverage: Some technologies/interfaces support more of our Use Cases than others. Most vary due to their lack of standardization.
Standardized data: If the technology/interface provides a standardized data representation, the mapping to umati is more consistent and allows plug&play of machines.
Usage within AM: Is the technology/interface used within the AM industry and is provided by different machine types and vendors?
Extendable: In order to implement further use cases a technology/interface needs to provide some kind of extendability.
Real-time data: Some technologies/interfaces do not publish data changes automatically which may result in the loss of data between requests.
2-way-operational: Automation requires data to be pulled from a machine but also pushing control instructions or job files to it.
Safety: Most technologies/interfaces come with encryption and multi-layer authentication and authorization processes. Those marked with may or may not support those based on the implementation.
Complexity: A less complex technology may be easier to implement but lacks a lot of functionality needed within an industrial environment.
| OPC/UA + umati CS | OPC/UA (custom) | REST API (Octoprint) | REST API (custom) | MTConnect | MQTT |
---|---|---|---|---|---|---|
Use case coverage |
|
|
|
|
|
|
Standardized data |
| |||||
Usage within AM |
|
|
|
|
|
|
Extendable |
|
|
|
|
| |
Real-time data | ||||||
2-way-operational |
|
|
| |||
Safety |
|
| | |||
Complexity |
|