1. ConnI (Connectivity Initiative) Status and Update
Ron O’Reilly, Peter van Vuuren
2002 Spring Sponsor Meeting
Center for Process Analytical Chemistry

2. Overview - What is ConnI
Topics
Overview - What is ConnI
Domain Model for Connectivity
Specific ConnI Goals
Current Status and Plans

3. What is ConnI
ConnI recognizes that a process analyzer is not a stand- alone entity but has only added value if through connectivity it is an integral component of several related system domains:
it must be integrated with other analyzers in its own Measurement domain
the DCS domain is it primary customer
an Analyzer Operations/Maintenance domain must ensure reliable operation and support effective user interfaces
the Enterprise domain to allow remote access and support

4. Historian (LT Archive) Data Server Workstation (User Inerface)
Hierarchical/Domain Model for Process Analyzer System - Overview
Historian (LT Archive)
Level 3 LAN
Enterprise Domain
Level 4 Enterprise LAN
Data Server L4
Workstation (User Inerface)
DCS Domain
c-LAN
AnLAN
O&M Domain
Safety
Control/ Optimization
Environmental L3 L2
Primary Data Path > Requires Maximum Integrity/Reliability
Level 2 LAN = Field LAN
Secondary Data Path > Requires High Integrity/Reliability
Measurement Domain 
SAM
eSAM
Level 1 Sensor Bus (CAN) L1
Measurement Data (Validated) Status/Change Info
Limited Control Functions
DCS Data +: Raw Data/Calibration/SQC Diagnostics/Alarms
Configuration Data All Control Functions L0

5. ConnI Goals
Define the Physical Layers for Level 1/2/3 * Level 1 : CAN bus * Level 2/3: Ethernet TCP/IP (Industrial)
Identify Compatible High-level Communication Protocols (peaceful co-existence on same workstations, servers etc.) * OPC * HTTP * Fieldbus etc.
Define Functional requirements for Data Server, Workstations and Long Term Historian
Define Requirements for Analyzer-DCS Data Link Interface * Draft Specification posted on New ConnI

6. Ethernet -TCP/IP Ethernet -TCP/IP CAN - bus (IS ??)  ConnI Goals
OPC Analyzer-DCS Datalink Specification
Ethernet -TCP/IP
Enterprise Domain
Level 4 Enterprise LAN L4
DCS Domain
c-LAN
AnLAN
O&M Domain
Safety L3
Ethernet -TCP/IP
Level 3 LAN
Control/ Optimization
Protocols: OPC HTTP Fieldbus
Environmental L2
Protocols: DeviceNet SDS CANOpen
CAN - bus (IS ??)
Level 2 LAN = Field LAN
Primary Data Path > Requires Maximum Integrity/Reliability
Secondary Data Path > Requires High Integrity/Reliability
Measurement Domain 
SAM
eSAM
Level 1 Sensor Bus (CAN) L1
Measurement Data (Validated) Status/Change Info
Limited Control Functions
DCS Data +: Raw Data/Calibration/SQC Diagnostics/Alarms
Configuration Data All Control Functions L0

7. OPC Datalink Specification - Analyzer Operations as Event Driven Functions
Specification allows for Bidirectional control: DCS Console Operator can Request Status Change e.g. * Start/Stop an Analyzer * Enable/Bypass a Stream * Change the Sequence of Streams to be Analyzed
Initialization
Data
Status Change
Fault Recovery

8. ConnI Status Report: A Summary
Overall Domain Model for Distributed Process Analyzer Functionality Proposed * Measurement Domain * DCS or Control System Domain * Analyzer Operations and Maintenance Domain (O&M) Domain * Enterprise Domain
Overall Connectivity Model for Domain Interaction Proposed * Ethernet TCP/IP as Connectivity Backbone Physical Layer/Protocol (Level 2) * TCP/IP-OPC Protocol proposed for Analyzer/DCS Datalink * Preliminary OPC Datalink Specification prepared for review by ConnI Steering Team/Participants (now available on CPAC ConnI Website) * CAN bus identified as Leading Candidate for Level Sensor Communications * Identified a Sensor/Actuator Manager (SAM) as a Necessary Device to Manage Sensor/Actuator Configurations related to Smart Modular Sampling Systems (NeSSI)
Plans: * ConnI Review/Acceptance of OPC Analyzer/DCS Datalink Specification (1Q2002) * Testing of Prototype OPC Datalink on a Honeywell System (2Q2002) - likely with ABB * Develop CAN based specification for NeSSI based Sensor/Actuator Communications (1-2Q2002) * Develop Functional Specification for SAM including Level 1 & 2 Communication Requirements * Develop Overall Domain/Connectivity Specification for Measurement/DCS/O&M Domains (3Q2002)