1. 1
© 1994 – 2011 Fieldbus Foundation

2. User Layer – Blocks and Device Descriptions
HMI
Values
are read from
the device. Descriptions
User Layer are obtained from the DD.
Alerts Mode
Inputs Algorithm Outputs
e.g. AI
Function Block
PV Units
Transducer
e.g. Level PV
Transducer Block
COMMUNICATION COMMUNICATION
STACK STACK
PHYSICAL LAYER PHYSICAL LAYER
PV
2
© 1994 – 2011 Fieldbus Foundation

3. Device Interoperability Test and Registration
Function
Block
Transducer
Block

Registered
Device Device
Communication
Stack
Interoperability Tester
Registered DD
Device Description
(DD)
3
© 1994 – 2011 Fieldbus Foundation

4. FOUNDATION for ROM Development
FB TB DD
H1 + HSE
Basic Control Advanced Control Remote Operations Management
Analog Input Analog Alarm Large Point Count Remote Devices
Analog Output Arithmetic 64 Channel Discrete Input/Output
Bias & Gain Deadtime 16 Channel Analog Input/Output
Control Selector Device Control Wired HART ® Connectivity
Discrete Input 8 Channel Discrete Input/Output Wireless Connectivity
Discrete Output Flexible Function Block Wireless HSE Backhaul
Manual Loader Input Selector Wireless Field Devices
PD Control Integrator WirelessHART®
PID Control Lead/Lag ISA100.11a
Ratio Control Setpoint Ramp Generator
Signal Characterizer
Splitter
Safety Instrumented
Timer
Functions
4
© 1994 – 2011 Fieldbus Foundation

5. FOUNDATION for ROM Development Phases
5
© 1994 – 2011 Fieldbus Foundation

6. FOUNDATION for ROM Development Teams
Host
HSE Remote I/O
HSE-RIO Team Fieldbus Foundation – ISA Cooperation
ISA100.15 Working Group
• Large Point Count Device
• Multi-channel I/O
Wireless HSE Backhaul
• Wired HART Block
FOUNDATION for ROM Device
Conventional
WirelessHART ISA100.11a
I/O
H1
Wired
HART
Wireless Sensor Integration Team
6
© 1994 – 2011 Fieldbus Foundation

7. FOUNDATION for ROM Development – HSE RIO
Configuration Operation
1. User configures Expected Tags in Association Block  Real-time process data published as configured
2. ROM Device instantiates appropriate Transducer Blocks  Control
e.g. RIO, HART, WirelessHART, ISA100.11a  HMI
3. ROM Device changes TB Tag to Expected Tag  Asset Management
4. TB are connected to FBs.  Device diagnostics are reported as configured
5. FB links and device diagnostics are configured  Control
 HMI
AB_001; Expd_Tag=TIC_334   Asset Management
 Maintenance
Association Block AB_002; Expd_Tag=TIC_335 
(AB) …
AB_003; Expd_Tag=TIC_336
AB_nnn; Expd_Tag=TIC_nnn

2048
 TBAI
TB Tag = “TIC_336” 

 TBAI  Data + Status
TB Tag = “TIC_336”   FBMAI  Device Diagnostics
 TBAI FB Tag = “Tank_1”
TB Tag = “TIC_334” 
7
© 1994 – 2011 Fieldbus Foundation

8. Device Diagnostics Function
Failure
Check
Out of Maintenance
Specification Required
Wired or Wireless HSE
FOUNDATION for ROM Device
 Utilizes advanced diagnostic capabilities of intelligent devices
 4 standard “status signals” categories are available
 Mapping of diagnostics in status signals configurable by user I/O
 Enables condition-based maintenance – automatic work orders H1 HART
 Optimizes maintenance functions
 Detailed information available on demand
Wireless
8
© 1994 – 2011 Fieldbus Foundation

9. Device Diagnostics Example
H1 + HSE
Device Memory Device Internal Calibration Has Plugged
Error Temperature High Drifted Impulse line
9
© 1994 – 2011 Fieldbus Foundation

10. FOUNDATION for ROM – HSE RIO Timeline
2007
Specification Team Kickoff Meeting Jan
2008
Draft Preliminary Specifications Oct
2009
Validation Team Kickoff Meeting Feb
Laboratory Validation Testing - Conventional I/O Aug, Dec
2010
 Laboratory Validation Testing - Conventional I/O Mar
 Laboratory Validation Testing - Wired HART ` Jun, Sep
 Preliminary Specifications – Conventional I/O Dec
2011
 Final Specifications – Conventional I/O Apr
 Association Block
 64 Channel Discrete Input/Output
 16 Channel Analog Input/Output
10
© 1994 – 2011 Fieldbus Foundation

11. FOUNDATION for ROM – WirelessHART Integration
Association Block
(AB)
Data + Status
2048
FB Device Diagnostics
TBHART
TB Tag = “HART_5”
TBLL
TB Tag = “HART_LIVE_LIST_GW_1”
GW_1
Gateway Expected Network Network Address 9
Tag Address Status
GW_1 HART_5 5 Good Network Address 5
Network Address 10
GW_1 HART_7 7 Bad
Mesh
GW_1 HART_9 9 Good Status Network Address 11
Network Address 7
GW_1 HART_10 10 Good
GW_1 HART_11 11 Bad
WirelessHART Mesh
11
© 1994 – 2011 Fieldbus Foundation

12. FOUNDATION for ROM - WirelessHART® Integration
2010
Lab Validation Testing – WirelessHART Parameter Mapping Nov
2011
 Lab Validation Testing – WirelessHART Parameter Mapping Mar
 Lab Validation Testing – WirelessHART Live List Jun
 Preliminary Specification - HART and WirelessHART Aug
2012
 Final Specification – HART and WirelessHART Jan
12
© 1994 – 2011 Fieldbus Foundation

13. FOUNDATION for ROM – Wireless Backhaul Model
CCD - Set of devices
BHI - Provides isolation and security of communications flows
BSP - Provides connectivity between CCD’s
IF1 - Physical interface to the backhaul technology
IF2 - Protected data flowing across the backhaul - authentication, authorization, encryption
IF3 - Physical interface to CCD
IF4 - Transparent end-to-end communication between CCDs
IF5 - Management - Configuration of IF1-IF3 and BHI functions
13
© 1994 – 2011 Fieldbus Foundation

14. FOUNDATION for ROM – Wireless Backhaul Security
Overlay Secure
Endpoint Endpoint Overlay
Tunnel
Secure Tunnel
14
© 1994 – 2011 Fieldbus Foundation

15. FOUNDATION for ROM – Wireless Backhaul Security
Overlay Secure
Endpoint Endpoint Overlay
Tunnel
PV PV
IF2
#8%%0@!!(%0
15
© 1994 – 2011 Fieldbus Foundation

16. FOUNDATION for ROM - Wireless Backhaul
2009
Backhaul Uses Cases and Requirements Completed Jan
Backhaul Request for Information (RFI) Development Feb - Oct
Review of RFI Responses by ISA100.15 Dec
2010
RFI Gap Analysis Competed Feb
Backhaul Security Modeling using ISA99 Methods Apr
First Wireless HSE Backhaul to Conventional I/O Operational Aug
First Wireless HSE Backhaul to WirelessHART Operational Nov
2011
 Backhaul Architecture Model review by ISA100.15 – Interfaces, Security Mar
 Backhaul Architecture Model review by ISA100.15 – Flow Control May
 Backhaul Architecture Model approved by ISA100.15 (Unanimous) Oct
2012
 Wireless HSE Backhaul Profiles
16
© 1994 – 2011 Fieldbus Foundation

17. FOUNDATION for ROM - Wireless Backhaul Profiles
Applications Design Demonstration Release
Requirements Validation
Backhaul
Technologies
System
(DEMO WG) HSE Wireless Engineering
Profiles for HSE
Profiles for HSE
Remote Operations Backhaul Design Guideline
Operation on
Operation on
Management End-User Specification Wireless Backhaul
Wireless Backhaul
Applications
Backhaul
Architecture Model
17
17
© 1994 – 2011 Fieldbus Foundation

18. FOUNDATION for ROM – ISA100.11a Integration
Association Block
(AB)
Data + Status
2048
FB Device Diagnostics
TBISA
TB Tag = “ISA_5”
TBLL
TB Tag = “ISA_LIVE_LIST_GW_1”
GW_1
Gateway Expected Network Network Address 9
Tag Address Status
GW_1 ISA_5 5 Good Network Address 5
Network Address 10
GW_1 ISA_7 7 Good
Mesh
GW_1 ISA_9 9 Good Status Network Address 11
Network Address 7
GW_1 ISA_10 10 Bad
GW_1 ISA_11 11 Good
ISA100.11a Mesh
18
© 1994 – 2011 Fieldbus Foundation

19. FOUNDATION for ROM - ISA100.11a Integration
2010
Specification Team Kickoff Meeting Oct
Initial ISA100.11a Integration Architecture Dec
2011
 ISA100.11a Integration Architecture Completed Mar
 ISA100.11a Integration Design Jun
 ISA100.11 Draft Preliminary Specification – Revision 1 Aug
 ISA100.11 Draft Preliminary Specification – Revision 2 Sep
 First Wireless HSE Backhaul to ISA100.11a Operational Sep
 ISA100.11 Draft Preliminary Specification – Revision 3 Nov
2012
 Lab Validation Testing - ISA100.11a 1Q
 Preliminary Specification – ISA100.11a 3Q
 Final Specification – ISA100.11a 4Q
19
© 1994 – 2011 Fieldbus Foundation