Metasys Connectivity Sales Resource Manual Section Product Bulletin Issue Date

629 IV 1000

Metasys BACnet System Integrator (BSI)

The Metasys BACnet System Integrator (BSI) provides an interface between a Metasys Network and a BACnet network. The BSI is a software product that operates on Personal Computers (PCs) running Microsoft Windows 98 or Windows NT Version 4.0. This software is a system-level integration providing communication at the N1 level with a BACnet system. This interface was designed for Ethernet integration of Metasys systems and BACnet (Figure 1). Another integration option involves the Metasys system using ARCNET while BACnet uses Ethernet (Figure 2). This product complies with BACnet Conformance Class 4. However, it also provides services that are required for the BACnet Conformance Class 5. This means that the BACnet system can monitor and control the Metasys system and that the Metasys system has the capability to monitor and control a BACnet system. In either case, the PC acting as the interface requires the Metasys Application Enabler (MAE) or the Person-Machine Interface (PMI) software Release 11.00. When the Metasys system is used to monitor and control a BACnet system, a Network Control Module (NCM) is required for the purpose of mapping points from the BACnet system into the Metasys system.

Features and Benefits

Conforms to BACnet Specifications 135-1995 Bidirectional Interoperability IP Network Enabled Supports BACnet Alarm and Event Services Single-seat Interface Manufacturer Independence Interoperability Between a BACnet System and More than 500 Johnson Controls Metasys Compatible Products Provides an open and standard protocol connection, which increases the opportunity to integrate systems from different manufacturers Provides interaction between Metasys and BACnet systems, increasing management efficiency and reducing operation costs Provides support for standard IP network communication. Continued support for BACnet Ethernet communication is provided. Provides Metasys Change-of-State (COS) messages to BACnet systems, increasing management efficiency and reducing operation costs Allows efficient management of information from one workstation Protects the investment in devices and training of the installed control solutions Greatly expands the options for connectivity solutions of the range of devices supported by a single user interface

2000 Johnson Controls, Inc. Code No. LIT-629019

1
www.johnsoncontrols.com

S ample Configurations for the BSI

PMI BSI and PMI or MAE Third-party BACnet Workstation (if present)

* * *

ISO-8802-3 Ethernet
*

ISO-8802-3 Ethernet

S
**

Metasys NCMs

BACnet NCM (BACnet Conformance Class 4)

BACnet Devices

* Ethernet board required. ** A standard NCM350 required when the Metasys system is commanding or monitoring BACnet points.

BACnet1

Figure 1: Metasys BACnet System Integrator with Ethernet Implementation

Section IVMetasys BACnet System Integrator (BSI)

PMI BSI and PMI or MAE

Third-party BACnet Workstation (if present)

** **

ARCNET

** **

ISO-8802-3

Ethernet

**

***

Metasys NCMs

BACnet NCM (BACnet Conformance Class 4)

BACnet Devices

* Ethernet board required. ** ARCNET board required. *** NCM300 or NCM350 used when the Metasys system is commanding or monitoring BACnet points.

BACnet2

Figure 2: Metasys BACnet System Integrator with ARCNET/Ethernet Implementation

I ntroduction
BACnet, Building Automation Control network, is a standard communications protocol designed by consensus of the American Society of Heating, Refrigerating, and Air Conditioning Engineers (ASHRAE) committee to allow devices from various vendors to exchange information. The Metasys BACnet System Integrator (BSI) allows communication between Metasys and other devices or building automation systems that comply with BACnet Standard 135-1995, and with Addendum A.

Section IVMetasys BACnet System Integrator (BSI)

P rovides Building Environment

Solutions
By supporting the BACnet protocol, the BSI provides solutions to a number of important needs for building automation systems:

S ystem Components
The general BSI configuration requires:

Intel Pentium PC hardware platform Metasys Person-Machine Interface (PMI) or Metasys Application Enabler (MAE) software Release 11.00 or later Metasys BACnet System Integrator (BSI) software Ethernet card for the PC for communicating with BACnet based on BACnet/IP or BACnet Ethernet

Utilizing Existing Communication Media Infrastructure: With the BSI support for BACnet/IP communication, it is possible to connect the BSI to standard Ethernet IP networks. This makes the BSI easy to install. Besides the support for BACnet/IP, continued support for BACnet Ethernet is provided. Providing Process Interaction: The integration of different building controls systems work together adding convenience and low involvement in facility management. Bidirectional Interoperability: A BSI may be configured to provide support for exporting up to 5000 Metasys N1 objects to BACnet, or to provide support for importing up to 1500 BACnet objects into the Metasys system. Supports BACnet Alarm and Event Services: The BSI supports the BACnet Intrinsic Reporting mechanism that allows providing Metasys Change-of-State (COS) messages to BACnet. This helps to increase building management efficiency and reduces operational costs. Single-seat User Interface: Multiple building systems can be monitored and controlled in the same way from a single workstation. Manufacturer Independence: BACnet devices from different manufacturers can be effectively added or replaced resulting in convenient system upgrades and expansion. Non-compliant Product Communication: The integrating architecture of the Metasys Network provides connectivity and integration through the BSI allowing over 400 non-BACnet compliant devices and systems to work with compliant systems.

For integrating BACnet objects into the Metasys system, the BSI configuration requires in addition:

NCM with a minimum of 4 Mb second Ethernet card for the NCM when using an Ethernet-only implementation (Figure 1) or

ARCNET card for the PC and an ARCNET cards for the NCM, if using an ARCNET implementation (Figure 2)

O rdering Information
To order the Metasys BACnet System Integrator, specify the complete product code number: WS-BACSIS-0 To order Workstation PMI or MAE software, specify either of the part numbers: WS-SWOPMI-0C WS-SWOMAE-0C

Section IVMetasys BACnet System Integrator (BSI)

P rotocol Implementation
Conformance Statement
The ASHRAE Protocol Implementation Conformance Statement (PICS) as defined in Standard 135-1995 describes the conformance class, functional groups, application services, and standard object types supported within a product. It also details the data link layer and character sets implemented. The Metasys BSI PICS contains information necessary to connect to a third-party BACnet system. In many cases, however, it may not be the only means to achieve interoperability or data sharing between a Metasys Network and another system. The following BACnet Protocol Implementation Conformance Statement section summarizes the PICS for the Metasys BACnet System Integrator (BSI). This statement indicates the level of compliance with the standard. It also describes the function and scope of interaction for the product. Due to the amount of information involved, an abbreviated description of Standard Object Types supported has been included (Table 2). For a detailed PICS on the BSI, consult the Metasys BACnet System Integrator (BSI) System Architecture Technical Bulletin (LIT-6295095) in the Metasys Connectivity Technical Manual (FAN 629.5). While the Metasys BSI PICS is believed to be accurate at the time of printing, Johnson Controls does not guarantee the accuracy of the document, nor will it be held responsible for damages of any kind, direct or indirect, which may result from the use of the Metasys BSI PICS, even in situations in which a Johnson Controls employee has examined your system. The conformance implementation is subject to change without notice. Note: The Metasys BSI PICS is copyrighted.

Section IVMetasys BACnet System Integrator (BSI)

BACnet Protocol Implementation Conformance Statement

Vendor Name: Product Name: Product Model Number: Product Description: Johnson Controls, Inc. Metasys BACnet System Integrator WS-BACSIS-0 This software product provides bidirectional communication between the Johnson Controls Metasys Facility Management System and a BACnet system, residing on Ethernet media.

BACnet Conformance Class Supported: Class 4 BACnet Functional Groups Supported: None

Table 1: BACnet Standard Application Services Supported

Application Services
Acknowledge Alarm Confirmed Event Notification Unconfirmed Event Notification Add List Element Remove List Element Read Property Read Property Multiple Write Property Write Property Multiple Time Synchronization Who Has I Have Who Is I Am X X X X X X X X X X X X X X X X X X X X X X X

Initiate Requests

Execute Requests
X

Section IVMetasys BACnet System Integrator (BSI)

Table 2: Standard Object Types Supported *

Object Type**
Analog Input (AI) Analog Output (AOS) Analog Value (AD) Binary Input (BI) Binary Output (BO) Binary Value (BD) Device Multistate Device MSD Multistate Input (MSI) Multistate Output (MSO) Notification Class 1 = DESCRIPTION 2 = RELIABILITY 3 = PRESENT-VALUE 4 = TIME-DELAY 5 = HIGH-LIMIT 6 = LOW-LIMIT 7 = INACTIVE-TEXT

Metasys Export Object Mapping Optional Properties*** Writeable Properties

1,2,(4),5,6,(14),18,19,(20), 21,22,23 1,2,(4),(5),(6),(14),18,(19), (20),21,22,23 1,2,(4),5,6,(14),18,19,(20), 21,22,23 1,2,4,7,8,9,18,(20),21,22,23 1,2,(4),7,8,13,18,(20),21,22, 23 1,2,4,7,8,9,18,(20),21,22,23 16,17 1,2,4,12 1,2,4,12,18, (20),21,22,23,24,(25) 1,2,(4),12,13,18,(20),21,22, 23 1 8 = ACTIVE-TEXT 9 = ALARM-VALUE 10 = PRIORITY-ARRAY 11 = RELINQUISH-DEFAULT 12 = STATE-TEXT 13 = FEEDBACK-VALUE 14 = LIMIT-ENABLE 1,3,5,6 1,3 1,3,5,6 1,3 1,3 1,3 --1,3 1,3 1,3 1

BACnet Import Object Mapping Optional Writeable Properties Properties

1,4,5,6,14 1,4,5,6,14 1,4,5,6,10,11,14 1,4,7,8,9 1,4,7,8 1,4,7,8,9 1 --1,4,12 1,4,12,13 --1,3,4,5,6,15 1,3,4,5,6,11,1 5 1,3,4,5,6,11,1 5 1,3,4,7,8,9 1,3,4,7,8,11 1,3,4,7,8,9 1 --1,3,4,12 1,3,4,11,12 --22 = NOTIFY-TYPE 23 = EVENT-TIME-STAMPS 24 = ALARM-VALUES 25 = FAULT-VALUES

15 = UNITS 16 = LOCAL-TIME 17 = LOCAL-DATE 18 = NOTIFICATION CLASS 19 = DEADBAND 20 = EVENT-ENABLE 21 = ACKED-TRANSITIONS

* For more details, please refer to the Metasys BACnet System Integrator (BSI) System Architecture Technical Bulletin (LIT- 6295095 ) in the Metasys Connectivity Technical Manual (FAN 629.5). **This product does not support dynamic creation or deletion. ***The parentheses indicate that the properties are fixed to default values

Data Link Layer Option

ISO 8802-3, 10BASE2 ISO 8802-3, 10BASET ISO 8802-3, Fiber BACnet/IP

Character Sets Supported

ANSI X3.4 (US ASCII or simply ASCII)

Special Functionality
Segmented Requests Supported Segmented Responses Supported Router Yes Yes Yes No No No Window Size: 127 maximum Window Size: 127 maximum

Property Range Restrictions

Please refer to the Metasys BACnet System Integrator (BSI) System Architecture Technical Bulletin (LIT-6295095) in the Metasys Connectivity Technical Manual (FAN 629.5).

Section IVMetasys BACnet System Integrator (BSI)

S pecifications
Product Recommended PC Platform (Order Separately) Metasys BACnet System Integrator (BSI) 200 MHz or higher Intel Pentium Processor Requires a minimum of 64 Mb of RAM CD-ROM drive for installing BSI software Requires minimum of 1 GB hard disk Ethernet card (NU-NET301-0) Monitor (required only for system setup) Keyboard (required only for system setup) Mouse (required only for system setup) Microsoft Windows 98 or Windows NT Version 4.0. Metasys PMI (WS-SWOPMI-0) or MAE (WS-SWOMAE-0) Release 11.00 Metasys BACnet System Integrator (WS-BACSIS-0) A second Ethernet adapter card (NU-NET301-0) for the NCM (when using an all Ethernet implementation as per Figure 1) An ARCNET card for the PC and an ARCNET card for the NCM (when using an ARCNET implementation as per Figure 2) NCM350 with 4 Mb of RAM or more required if using an all Ethernet implementation NCM300 or 350 with 4 Mb of RAM or more if using an ARCNET implementation Additional Information NCM controller must be configured with Metasys Release 11.00 software as a General with NT (Network Terminal) NC type or General with OT (Operator Terminal) NC type.

Software (Order Separately) Additional Components (Order Separately)

The performance specifications are nominal and conform to acceptable industry standards. For application at conditions beyond these specifications, consult the local Johnson Controls office. Johnson Controls, Inc. shall not be liable for damages resulting from misapplication or misuse of its products.

Controls Group 507 E. Michigan Street P.O. Box 423 Milwaukee, WI 53201

FAN 629 Metasys Connectivity Sales Resource Manual Release 2.0 Printed in U.S.A. www.johnsoncontrols.com

Section IVMetasys BACnet System Integrator (BSI)