1. Interfacing Building Automation Systems (BAS) to Process Control Presented by: Gordon MacLachlan (Mac)

2. Presentation Highlights  The Need for BAS In Process Control Systems  The Need for Process Control in BAS Systems  Common BAS Network Protocols  Common Process Control Network Protocols  FieldServer Protocol Support  FieldServer Hardware Solutions  Case Study: Interfacing with Rockwell  General Integration Considerations

3. The Need for BAS in Process Control  Energy Management Process Control and BAS equipment interact to minimize energy requirementsProcess Control and BAS equipment interact to minimize energy requirements Example: Different cooling schedules for a building when plant is in or out of operationExample: Different cooling schedules for a building when plant is in or out of operation  Safety Process Control Events could trigger safety actions on the BAS side and vice versa.Process Control Events could trigger safety actions on the BAS side and vice versa. Example: Gas leak detection could close room vents in affected zone.Example: Gas leak detection could close room vents in affected zone.  Centralized Control Centralized operations lead to the desire for homogenous host HMI’s that monitor both BAS and Process control.Centralized operations lead to the desire for homogenous host HMI’s that monitor both BAS and Process control.

4. The Need for Process Control in BAS  Optimized Environmental Control Control Process affect the building environment. Monitoring the process allows for predictive zone management.Control Process affect the building environment. Monitoring the process allows for predictive zone management.  Shared technology BAS makes use of many of the same types of equipment that Process Control does.BAS makes use of many of the same types of equipment that Process Control does. Examples: Boilers, UPS systems, VFD’s etc.Examples: Boilers, UPS systems, VFD’s etc.

5. Common BAS Networks  Open Protocol Networks BACnetBACnet LonWorksLonWorks ModbusModbus  Common OEM Networks JCI Metasys N2JCI Metasys N2 Data AireData Aire CarrierCarrier LutronLutron  Fire Alarm Control Panel (FACP) Networks NotifierNotifier ESTEST SimplexSimplex SiemensSiemens Fike, and othersFike, and others

6. Common Process Control Networks  Open Protocol Networks Modbus/TCPModbus/TCP Modbus RTUModbus RTU OPCOPC ODVA EtherNet/IPODVA EtherNet/IP DeviceNetDeviceNet ProfibusProfibus HartHart  Common OEM Networks AB CSPAB CSP AB DF1AB DF1 AB ControlNetAB ControlNet GE SNPGE SNP GE SRTPGE SRTP

7. Deciding on a Protocol – Factors that count  Legacy PLC/SLC, or “Logix”? If ControlLogix, then use SlotServerIf ControlLogix, then use SlotServer  Is the serial DF1 port in use? If so, then rule out DF1 as an optionIf so, then rule out DF1 as an option  Does the specification state protocol to be used? If so, then decision is madeIf so, then decision is made  Cost of PLC equipment needed for the interface Price differences may be significant.Price differences may be significant.  Client or Server Application? For HMI Interface, use OPC.For HMI Interface, use OPC. CASE STUDY: Rockwell Interface

8.  Direct connection from Allen Bradley ControlLogix PLC to another network  Standard 1756 format plugging directly into the Allen Bradley ControlLogix rack  RS-485 port for devices/networks using RS-485 protocols  Ethernet port for Configuration Utilities & Ethernet devices/network  Standard LonWorks TP/FT-10 interface for LonWorks devices/network  Installing the SlotServer module is a very simple procedure LonWorks TP/FT-10 interface RS-485 port Ethernet port CASE STUDY: Rockwell Interface The ControlLogix Solution: SlotServer

9. SlotServer Features  Plug the SlotServer directly into the ControlLogix Communications rack  Scrolling text display with 3 status LED’s provides card status at a glance  A bank of six LED’s provides communications status at a glance, as well as additional diagnostic indications  Ethernet port for advanced troubleshooting purposes  Service Pin for LonWorks commissioning Diagnostic displays Service Pin CASE STUDY: Rockwell Interface

10. Hardware Specifications:  Backplane Load: 0.6A  Slot width: 1  Operating Temperature: -40 to 185 Deg. F  Humidity: 5-95% (non-condensing) CASE STUDY: Rockwell Interface

11. Software Features  Transfer up to 6000 points between ControlLogix and many third party interfaces.  Configure the SlotServer to communicate with many different protocols, including LonWorks, BACnet, Metasys and Modbus.  Flexible configuration architecture allows for creative connectivity options.  Use the Standard SlotServer profiles for connection without configuration CASE STUDY: Rockwell Interface

12. Software Features  Control communications in the ControlLogix software using standard generic message blocks  Example message block code provided in an ACD file with the SlotServer CASE STUDY: Rockwell Interface

13. Distinct Advantages - SlotServer  Allows connection of a Third Party Network to a ControlLogix system without the use of external gateways  Sits in the ControlLogix rack, thereby preserving cabinet “Real Estate”  Provides generic profiles (such as LonWorks Open Interface) or custom profiles (with configuration), allowing for a choice between ease and flexibility. CASE STUDY: Rockwell Interface

14. Generic vs Custom Mapping  SlotServer can ship default with generic open profile or can be shipped as the configurable version.  The generic profile eliminates the need for messing with config.csv, thus reducing commissioning time.  Creating a custom profile with config.csv allows for more flexibility to suit the specific application  FieldServer offers custom profiling services if needed. CASE STUDY: Rockwell Interface

15. Preparing for Configuration 1. Training – Attend a FieldServer training class or order the first SlotServer pre-configured as a template to learn from. 2. Input – Acquire information about BAS protocol points to be mapped. Information must include point address details for the particular protocol. 3. Draw – A picture paints the proverbial 1000 words. Sketch a network diagram, and then sketch a schematic of how the data blocks are to be mapped. 4. Configure – With the first 3 steps done correctly, this step becomes easy. CASE STUDY: Rockwell Interface

16. Data Arrays. Map Third party points into and out of these data arrays and let the Logix driver do the rest. Multiple blocks exist so that the data can be mapped through the limited IO Buffer on the backplane using multiplexing. CASE STUDY: Rockwell Interface

17. Example: Connecting the SlotServer to LonWorks Sample Mapping: The points below show a sample of Lon Points that are mapped into the Data Arrays that get multiplexed in and out of the Backplane buffers. Map_Descriptors Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Lon_Function, Function, Node_Name, SNVT_Type nvoVolt1_25,Out_25,74,NVUOIMX,WRBX,Lon_Srv_1,SNVT_volt nvoVolt2_25,Out_25,75,NVUOIMX,WRBX,Lon_Srv_1,SNVT_volt nviAmp1_01,In_1,00,NVUI,Server,Lon_Srv_1,SNVT_amp nviAmp2_01,In_1,01,NVUI,Server,Lon_Srv_1,SNVT_amp Data Arrays Assigned to I/O Buffers by Logix driver Standard LonWorks Driver Mapping CASE STUDY: Rockwell Interface

18. General Integration Considerations  Are you a BAS expert or a Process Control expert? Bridging between industries probably means that the user will be familiar with one side of the gateway application, but not the other. Some familiarization with the unknown side will be required.Bridging between industries probably means that the user will be familiar with one side of the gateway application, but not the other. Some familiarization with the unknown side will be required.

19. General Integration Considerations  Different Protocols behave differently LonWorks has binding, BACnet autodiscovers, EtherNet/IP talks tags, Profibus needs gsd’s, whereas ControlNet needs eds’s. Metasys has slaves, Modbus polls, GE EGD has subscribers, etc, etc..LonWorks has binding, BACnet autodiscovers, EtherNet/IP talks tags, Profibus needs gsd’s, whereas ControlNet needs eds’s. Metasys has slaves, Modbus polls, GE EGD has subscribers, etc, etc.. The bottom line is they all do the same thing in different ways. They all pass data.The bottom line is they all do the same thing in different ways. They all pass data. Configuring these protocols is typically easy due to tools provided. However, knowing what to configure is not.Configuring these protocols is typically easy due to tools provided. However, knowing what to configure is not.

20. General Integration Considerations  Scaleable support – Use what you need Using a FieldServer product requires purchase, configuration, commissioning and supportUsing a FieldServer product requires purchase, configuration, commissioning and support If familiar with the network protocols involved consider purchasing the product and doing configuration and commissioning yourselfIf familiar with the network protocols involved consider purchasing the product and doing configuration and commissioning yourself If unfamiliar with the network protocols, consider purchasing the configurationIf unfamiliar with the network protocols, consider purchasing the configuration If unfamiliar with network integration, consider purchasing the commissioning.If unfamiliar with network integration, consider purchasing the commissioning.

21. General Integration Considerations  Getting it right – Input is the key GIGO – Garbage in, garbage out - GUARANTEEDGIGO – Garbage in, garbage out - GUARANTEED To configure a FieldServer product, details of the data to be mapped is required. This is the configuration input.To configure a FieldServer product, details of the data to be mapped is required. This is the configuration input. The quality of the configuration input determines the quality of the configuration, which in turn determines the success of the commissioning process.The quality of the configuration input determines the quality of the configuration, which in turn determines the success of the commissioning process. The bottom line: Spend more time getting the input right.The bottom line: Spend more time getting the input right.

22. Resources  FieldServer Website (www.FieldServer.com) www.FieldServer.com  LonMark website (www.LonMark.org) www.LonMark.org  Modbus IDA website (www.modbus.org)  Echelon Website (www.echelon.com)  Rockwell Allen-Bradley Website (www.ab.com) www.ab.com  BACnet Website (www.bacnetinternational.com) www.bacnetinternational.com  Rockwell Automation Encompass Website (www.rockwellautomation.com/encompass/)

23. Contacts Marketing and Sales: Steve Ferree: sferree@fieldserver.com sferree@fieldserver.com Richard Theron: rtheron@fieldserver.com rtheron@fieldserver.com Technical: Mac: mac@sfintegration.com mac@sfintegration.com

24. THANK YOU! …..for taking the time to attend this presentation. Questions?