Evolution of NeSSI-bus for Process Analytics | Clear Path to Analytical Control | Seattle, WA 2005

1. NeSSI-bus History, Evolution and Selection for Process Analytical CPAC, Seattle, WA, USA November 10, 2005 “the best way to predict the future is to create it”

2. dcs V P A F USB equivalent…..? ANLAN - Ethernet/OPC NeSSI™-bus Sensor/Actuator Manager (SAM) Fluid Handling System

3. V P A F Fluid Handling System End User Objective 1:More diagnostics and control through use of sensors/actuators • A system may require as many as 20 I/O • P, T, F sampling system • valves & pumps • utility monitoring • heating/cooling • in addition to analytical • Currently we have no good way of handling these devices

4. End User Objective 2:Rated IS for hazardous areas* • Europe, USA, Canada, Japan and the Russian Federation use different Hazardous Area approval bodies • The use of a universally acceptable hazardous protection method allows entry into any geography without conditions or exceptions • The NeSSI-bus requires Intrinsic Safety (IS)* [Ex ia/b] meets the requirements of ALL jurisdictions approval bodies [e.g. FM, CSA, ATEX, GOST] • The NeSSI-bus shall also be available (without a barrier) for use in general purpose non-IS applications (N-IS)

5. End User Objective 3:Screw on connections and simple wiring* • Probably the compelling reason for an IS bus is the ability to operate miniature devices in a hazardous environment using screw on connections and “normal” wiring. • The M8 cable size is ideal for flexibility and small components POCA = Proof of Concept Apparatus

6. End User Objective 4: PC-like* host for the NeSSI-bus • Today we use a hodge-podge of analyzer I/O, PLC’s, DCS’s, data bases, proprietary systems to handle sensors and actuators needed for diagnostics and control • Enables a simple graphical user interface • Enables use of 3rd party software Industrial, miniature PC Sensor/Actuator Manager (SAM) * Transmitter sized

7. End User Objective 5: Make our systems more reliable. Reduce the use of unintelligent devices! • Discrete devices (switches) do not meet industries needs. • The NeSSI-bus transmits both analogue and discrete sensor data as well as allowing data read/write to each device along with status checks

8. End User Objective 6:Open, non proprietary, rugged bus A CLEAR DESIGN TARGET FOR COMPONENT MANUFACTURERS * WE NEED TO REDUCE DESIGN RISK*

9. End User Objective 7:Formation of a NeSSI-Bus Users Group (N-bug) • Deal with issues unique to the PA industry • Reduce risk to manufacturers • Similar to CanOpen Vehicle User Group • CPAC may be an opportune forum

10. History & Evolution of the NeSSI-bus • 2000 - NeSSI launched – mechanical fluid components initially • 2001 –7 elements of Generation II proposed • 2001 – X-team advocates Div/Zone 1 approval for NeSSI • 2002 – NeSSI Gen II spec draft released • 2003 – ODVA/Rockwell Meeting (DeviceNet) • 2003 – NIST Meeting (CiA/IEEE-1451.6 initiative launched) • 2003 - Swagelok demos first CAN valve actuation system • 2003 – POCA Sample System using CAN proof of concept (Dow, EMCC, Honeywell) • 2003 – Intertec releases first “smart” heater • 2004 – “This Dog Don’t Hunt” 4-20 mA eliminated as a viable sol’n • 2004 - Honeywell selects ProfiBus for DOE prototype • 2005 - Honeywell selects FF for DOE project with Softing • 2005 – (Nov Workshop) Alternative buses proposed at CPAC

11. Foundation Fieldbus Status • Work miniaturizing FF for NeSSI is languishing • Honeywell’s funding by the US Department of Energy (DOE) has been cut back and they are not driving this development nor providing prototypes • concern expressed about cost of FF nodes • A champion needed to push FF miniaturization for NeSSI

12. Fork in the Road • CAN based/alternatives • cheap • simple, robust • small • IS certification needed • Foundation Fieldbus • powerful • control on the wire • more expensive • out of box intrinsic safety