Connectivity Framework
7: Connectivity Standards
Fieldbuses implement parts of the connectivity transport and framework functions. None satisfies all of the connectivity core standards criteria( see section 3.4). However, they are well deployed with extensive experience. Most of these protocols support the following types of communication:
• Management: Request-Reply pattern, with explicit schemas, for example a RESTful architectural style, used for resource lifecycle communication for management and status of the device / thing
• Operational: Peer-to-peer publish-subscribe pattern, with implicit schemas, often timeseries, used for data streaming of key operational data used for sense-control-actuate control loop processing that maintains the system’ s operational integrity.
This suggests that the core connectivity standards should support both forms of data exchange patterns to support the range of functions in the overlying applications.
Most automation and control applications in operations and being deployed for the foreseeable future will rely upon a Fieldbus-based ecosystem protocol. Most“ Industrial Internet” applications will have to access data from these protocols to acquire data from and actuate decisions or insights into these protocols. Integration is important.
IIC: PUB: G5: V1.0: PB: 20170228- 54-