Solving the Issue of Interoperability among Devices and Systems

591 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
591
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
25
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Solving the Issue of Interoperability among Devices and Systems

  1. 1. Solving the Issue of Interoperability among Devices and Systems ISA100 Wireless Solutions Summit 19 May 2008
  2. 2. Presenter <ul><li>David D. Brandt Principal Engineer Rockwell Automation Advanced Technology – Milwaukee [email_address] </li></ul>
  3. 3. About the ISA100 Standard Activity <ul><li>Multiple protocol support on a single, integrated wireless network (ISA100.11a): </li></ul><ul><ul><li>ISA100.11a native </li></ul></ul><ul><ul><li>HART ® </li></ul></ul><ul><ul><li>FOUNDATION ™ Fieldbus </li></ul></ul><ul><ul><li>PROFIBUS </li></ul></ul><ul><ul><li>Modbus ® </li></ul></ul><ul><ul><li>CIP ™ </li></ul></ul><ul><ul><li>Others </li></ul></ul><ul><li>Multiple radio support in a family of standards (ISA100): </li></ul><ul><ul><li>Process Automation (Process Focus) </li></ul></ul><ul><ul><li>Factory Automation (Discrete Focus) </li></ul></ul><ul><ul><li>Transmission and Distribution (Long Distance Focus) </li></ul></ul><ul><ul><li>RTLS/RFID (Industrial Tagging Focus) </li></ul></ul>
  4. 4. Challenge: How to provide Interoperability among Devices and Systems? HART ® , FOUNDATION ™ Fieldbus , PROFIBUS, Modbus ® , CIP ™ , ... ISA100.11a, WirelessHART TM , ZigBee ® , … HART ® , FOUNDATION ™Fieldbus , PROFIBUS, Modbus ® , CIP ™ , ... Asset Management Engineering Tools Historians Control Systems Other applications Mixed Automation Systems Embedded Wireless Device Wireless Adapter Wired Device Mixed Wired and Wireless Devices Gateway
  5. 5. A specific challenge: ISA100.11a / WirelessHART ™ Interoperability <ul><li>ISA100-WirelessHART Joint Analysis Team (JAT) addressed this issue </li></ul><ul><li>The ISA100.11a draft standard has followed the recommendations for release 1: </li></ul><ul><ul><li>Enable dual-mode gateways </li></ul></ul><ul><ul><li>Develop a “common high-side interface” in the gateway </li></ul></ul><ul><ul><ul><li>As a common model and interface for mixed systems and devices </li></ul></ul></ul><ul><ul><ul><li>Base the interface on the WirelessHART ™ optional XML interface </li></ul></ul></ul><ul><ul><ul><ul><li>Specify as an implementation neutral Service Access Point </li></ul></ul></ul></ul><ul><ul><ul><li>Provide enhanced tunneling for application layer protocols </li></ul></ul></ul><ul><ul><ul><li>Provide generic wireless network management that is separate from the application protocols </li></ul></ul></ul><ul><ul><ul><ul><li>Provide information to facilitate coordination of RF usage </li></ul></ul></ul></ul><ul><li>Convergence below the gateway will be considered for later releases </li></ul>
  6. 6. Multimode Gateway with Common High-side Interface ISA100.11a specific interfaces WirelessHART ™ specific interfaces ISA100.11a Stack (PHY through APP) WirelessHART ™ Stack (PHY through APP) Protocol translator and stack to communicate with plant network of choice Other Stack… Common High-side Interface “ Other” specific interfaces Other applications ISA100.11a WirelessHART ™ Coexistence Features and Functions “ Other” e.g., Bluetooth ® , ZigBee ® , etc. Asset Management Engineering Tools Historians Control Systems
  7. 7. Gateway Service Access Point (GSAP) <ul><li>Session </li></ul><ul><li>Lease </li></ul><ul><li>Messaging </li></ul><ul><ul><li>Publish/subscribe </li></ul></ul><ul><ul><li>Client/server </li></ul></ul><ul><ul><li>Source/sink </li></ul></ul><ul><ul><li>Bulk transfer </li></ul></ul><ul><li>Alert </li></ul><ul><li>Reports </li></ul><ul><ul><li>Device List </li></ul></ul><ul><ul><li>Topology, Schedule </li></ul></ul><ul><ul><li>Device Health, Neighbor Health, Network Health </li></ul></ul><ul><li>Time Synchronization </li></ul><ul><li>Gateway configuration </li></ul>This is the Common High-side Interface used by protocol translators.
  8. 8. GSAP: Session Service Protocol Translator Gateway Session Protocol translators act on behalf of plant applications to establish sessions with the gateway entity through the GSAP session service. Sessions allow resource allocation for a specific network. Resources are reclaimed when a session ends. GSAP Gateway Entity Translating proxy Embedded Wireless Device Wireless Adapter Wired Device Asset Management Engineering Tools Control Systems Embedded Wireless Device Wireless Adapter Wired Device
  9. 9. GSAP: Lease Service Gateway Entity GSAP Protocol Translator Protocol translators act on behalf of plant applications to establish leases within sessions to allocate specific communication resources. Leases allow dynamic resource allocation and release. Resources are allocated within the gateway entity, the network, or both. Specific types of leases are available for: publish/subscribe, client/server, bulk transfer and alerts Lease Translating proxy Control Systems Wireless Adapter Wired Device Embedded Wireless Device
  10. 10. GSAP: Messaging Services Buffer Publish Subscribe Client Server Bulk Transfer Client Subscribe Publish Server Client Bulk Transfer Server Buffer Buffer Buffer Buffer <ul><li>Change of state delivery </li></ul><ul><li>Local caching </li></ul><ul><li>Synchronization </li></ul>Buffer Buffer Buffer <ul><li>Optional caching </li></ul><ul><li>Large item transfer </li></ul><ul><li>Reliable, in-order delivery </li></ul>Alert Alert Translating proxy Protocol translators act on behalf of plant applications to utilize lease-based messages services to perform messaging that supports protocol translation. Protocol specific application content is carried in the messages. Message Services
  11. 11. GSAP: Report Services Protocol Translator Common reports available, independent of the underlying wireless technology. GSAP Gateway Entity Report Generation Common Reports Gateway Translating proxy
  12. 12. GSAP: Device List Report Service Protocol translators present each wireless device as if it were a wired device within the plant network. The device list report service allows the wireless devices to be discovered and mapped into the plant network, ultimately linking to the control strategy. Each device has a globally unique identifier. EDDL and other device description methods extensions can enable linkage without additional tools. GSAP Gateway Entity Protocol Translator Proxy 1 Proxy 2 Proxy 3 Proxy 4 Plant Network Control System
  13. 13. GSAP: Health Report Services Protocol Translator Health reports are available to alert control systems to underlying problems in a generic manner. Health reports are also available to asset management systems for maintenance purposes. Protocol translators are responsible for conversion to specific formats. GSAP Gateway Entity Report Generation Gateway Device Health Neighbor Health Network Health Translating proxy Asset Management Control Systems
  14. 14. GSAP: Topology Report Service, Schedule Report Service Topology and Schedule reports enable the ability to “drill down” when a Health report indicates a communication problem. When devices from different types of wireless networks share the same physical space, channel and transmission schedule can be evaluated for coexistence improvement opportunities. Network 1 Node 1 Network 1 Node 2 Network 2 Node 1 Network 1 Node 2 Time, Channel Time, Channel Errors Errors Protocol Translator GSAP Gateway Entity Report Generation Topology Schedule Health Translating proxy Engineering Tools
  15. 15. GSAP: Time Synchronization Service Protocol Translator Services are available to synchronize underlying wireless networks to an external source. This is useful when the same source is used in a control system. This is also useful to synchronize wireless device communication across wireless networks. Protocol translators can adapt a variety of sources. GSAP Gateway Entity Time Synchronization Gateway Translating proxy Clock Source
  16. 16. Example wireless device integration scheme Multiple Systems A single wireless device (single catalog number) can operate across multiple systems. A specific protocol translator is required in the gateway for each system. ISA100.11a provides an efficient application model that native devices can use for this purpose. Gateway GSAP Gateway Entity Translating proxy Translating proxy Translating proxy HART® Application FOUNDATION™ Fieldbus Application PROFIBUS Application Single Generic Device Multiple Protocol Translators Control Systems Control Systems Control Systems Embedded Wireless Device
  17. 17. Example wired device integration scheme Multiple Systems Wired devices can operate across multiple systems. A simple protocol translator is required in the gateway to tunnel each protocol. Adapters must also implement the tunnel protocol. ISA100.11a provides an efficient tunneling model that can be used for this purpose. Gateway GSAP Gateway Entity HART® Application FOUNDATION™ Fieldbus Application PROFIBUS Application Single Device Tunneling Protocol Translators Translating proxy Translating proxy Translating proxy Control Systems Control Systems Control Systems Wireless Adapter Wired Device Wireless Adapter Wired Device Wireless Adapter Wired Device
  18. 18. Conserving battery life: Minimizing transactions with caching Plant Network Gateway Caching reduces transactions (increasing battery life). Caching gives immediate response to application if used properly. Both ISA100.11a native messaging and tunneled messaging utilize cache techniques. Tunneled Information Native Information Buffer Buffer Information is routed through gateway cache Control Systems
  19. 19. Conserving battery life: Reducing header sizes Address Length Data Integrity Check Application Content Plant Network Wired Packet Address Length Data Integrity Check Wireless Packet Address Length Data Integrity Check Tunneled Device Wired Packet Plant Network Gateway MAP MAP CARRY CARRY CREATE CREATE CREATE CREATE Enhanced tunneling reduces the size of packets (increasing battery life) via a “configuration agreement” to map and create fields rather than carrying them. ISA100.11a native messaging provides numerous mechanisms to reduce header size. Wireless Adapter Wired Device Control Systems
  20. 20. Benefits to Users <ul><li>Protects investment in legacy devices and protocols </li></ul><ul><li>Reduces the lifecycle cost associated with gateways </li></ul><ul><ul><li>Acquisition cost (less gateways) </li></ul></ul><ul><ul><li>Training and Maintenance cost (common gateway model) </li></ul></ul><ul><li>Provides a future migration path </li></ul><ul><ul><li>For wired devices </li></ul></ul><ul><ul><li>For improved wireless technology </li></ul></ul><ul><ul><li>First step on path to more complete integration with WirelessHART ™, a nticipated to be upgradeable to “Release 2” approach without impacting higher level applications </li></ul></ul>
  21. 21. Benefits to Vendors <ul><li>Reduces development cost and time </li></ul><ul><ul><li>Design to a common gateway model </li></ul></ul><ul><ul><ul><li>Independent of plant network </li></ul></ul></ul><ul><ul><ul><li>Independent of low-power wireless network </li></ul></ul></ul><ul><ul><li>Single paradigm fits both ISA100 and WirelessHART ™ architectures </li></ul></ul><ul><li>Enables value-added integration enhancements </li></ul><ul><ul><li>E.g., time synchronization across networks </li></ul></ul><ul><ul><li>E.g., coexistance coordination tools </li></ul></ul>

×