ManageUPS CIO BACnet Supplement-090210

ManageUPS CIO UsrGuide 913-601_BACnet Supplement page
DOC VER. 090210, CIO Software Version 1.2.1 (2992)

1
ManageUPS CIO v1.2 BACnet/IP Services Option

ManageUPS CIO with BACnet server module allows a higher level monitoring
system (BACnet client) to monitor the status of the CIO monitoring server.
The BACnet service is licensed separately. It is sold/priced in device count
increments to match the underlying Base license.

A BACnet license can be added using the License Manager.

2

Configuring BACnet/IP Services

Open the BACnet server Configuration Dialog.
All of the specific BACnet parameters and options on the following screens is
to be provided by the BACnet Engineer.

Summary Tab
Network Settings Section
To enable the BACnet/IP services plugin, select Enable BACnet/IP Service
on the Summary tab of the BACnet/IP Service screen. The IP Port and the
Device ID can also be configured here.
To configure additional Network options, press on the More Options button.

3
BACnet/IP Server Options
Network More Options Dialog - Network Options Tab

NOTE
If the computer has more than one Ethernet interface it is critical to configure
ManageUPS CIO to bind with the proper interface for proper operation.
The IP Address list box contains all of the IP addresses associated with this
computer, select the one that the BACnet services should use. The IP port,
BACnet Device ID, APDU Timeout, APDU Retries and Maximum APDU can
all be configured on this screen.
4
BACnet/IP Device Options
Network More Options Dialog - Device Bindings Tab
This screen can be used to add device bindings to BACnet devices on other
networks. This can be used if a BBMD BACnet/IP Broadcast Management
Device" is not installed on the network.

To add a new device binding press the button. The device binding must
be entered in the form device:address:port:maxapdu.

5
Alarms Section
To enable Intrinsic Reporting, select Enable Intrinsic Reporting on the
Summary Tab of the BACnet/IP Service screen.
There are two classes of objects which support Intrinsic Reporting:
Multi-State Inputs (MSI) which represent individual devices monitored
by CIO.
Multi-State Values (MSV) which represent the alarm severity of groups
and smart groups within CIO.

The following screenshot, from a third party Bacnet Management Station,
provides an example of Bacnet data available from a Multistate Input value.
The objectName is derived from the device name in CIO. The string; MSI is
appended to the end of the objectName after a space.

6
There are two Notification Class objects
NC1 Covers notifications from the MSI objects.
NC2 Covers notifications from the MSV objects.

provides an example of Bacnet data available from a Notification Class.

7
Analog Values (AV) represent device counts in CIO groups and smart groups.
provides an example of Bacnet data available from an analog value. The
objectName is derived from the Group or Smart group name. The letters AV
are appended to the end of the objectName after a blank space.

8
All objects support COV.
To configure additional options for Intrinsic Reporting press the More
Options button to display the Intrinsic Reporting Options dialog. This dialog
can be used to map CIO alarm severity levels to BACnet Alarms and Faults.
By default, CIO Warning level Alarms will generate BACnet Alarms and CIO
Severe level Alarms generate BACnet Faults.

NOTE: The severity classification for each alarm is defined in the agent layer
representing each device to CIO on the network.

The To-Normal, To-Offnormal, and To-Fault text can also be configured in this
dialog. The %NAME% macro will be replaced with the BACnet Object name
of the device, which is derived from the CIO device name as described
previously.

9
Statistics Section
The statistics section of the Summary Tab contains various statistics for
diagnosing BACnet communications.
Included are;
BACnet bytes received
BACnet bytes transmitted
timeout counter
error counter.

10
Objects Tab

Devices Tab
This tab lists all the assigned BACnet Instance numbers for all devices
configured in the CIO All Devices list (list of UPS and sensor devices being
monitored by CIO).
These numbers are assigned automatically by the CIO service to ensure
uniqueness -- and cannot be changed manually. (See Instance Numbers,
page 11 for more information).
The Value (multi-state input) associated with each object is the current alarm
value (1=Normal 4=Severe).
The device list can be saved to a CSV file using the Save to CSV button.

11
Groups Tab
This tab lists each Smart Group with their assigned Instance numbers. These
numbers are assigned automatically by the CIO service to ensure uniqueness
-- and cannot be changed manually. The Value associated with each group is
the number of devices currently present in the Smart Group.
The group list can be saved to a CSV file using the Save to CSV button.

Instance Numbers

Automatically assigned and managed to ensure uniqueness
CIO BACNET Server implementation is that of a Smart Sensor representing
the state of a large number of UPS objects and SmartGroup objects
associated with the list of UPS objects to be monitored.
( BACnet Standard Device Profile (Annex L): BACnet Smart Sensor (B-SS)

As a Smart Sensor, BACnet instance numbers for each UPS and SmartGroup
object are assigned automatically within CIO to ensure uniqueness per
BACNET standards. The BACNET instance numbers are derived from a
unique internal identifier assigned to the device when it is added to the All
devices list (inventory of UPS to be monitored).

NOTE: If a UPS is added to the inventory of monitored objects, it will retain its
unique identifier until it is deleted/removed from the inventory list. If a UPS is
later added back in to the inventory, CIO will see it as a new device and will
randomly assign a new unique identifier from the pool of available unique
identifiers.

12
Mechanism for automatic assignment and re-assignment of
BACNET Instance Numbers
When a UPS or other device is added to the All Devices list in a CIO system,
it is automatically registered within CIO internal database structure and
assigned an internally unique identifier. Identifiers are assigned randomly from
a pool of 16
5
possible identifiers (5 digit hex value)
1
.

The Name, Host IP and Port are properties of the UPS that are retained in
CIO associated with the unique identifier along with Pin-Map location and
Group membership. These properties can be changed or updated from time
to time manually but the unique identifier will be retained as long as the
representation of the device remains in the All Devices inventory list.
This identifier is also used to generate the unique BACNET instance number
associated with that device
The identifier is released back into the pool
when a device is removed from the All
Devices list.

1
It is possible but not likely that a previously assigned, but later released identifier may be re-assigned to a device.
All identifiers in the pool have an equal probability of being assigned to any new device added to the inventory. As
such, it is possible, but exceptionally rare that a previously released identifier might be assigned to the same device if
that device were added, removed and then added back into the All Devices inventory. For further guidance, see :
Recommended Practice for managing consistency of Instance Numbers when physical UPS or Adapters are
changed for maintenance
13
Recommended Practice for managing consistency of Instance Numbers
when physical UPS or Adapters are changed for maintenance

The recommended practice for maintaining the monitored inventory list is to
not remove an entry from the All Devices list unless the underlying physical
assets will be removed completely and not replaced in the physical
infrastructure.

The unique identifier for the asset will be retained in the CIO internal database
along with the named identity properties (Name, PinMap Location, Group
membership and network address) and the other properties that CIO attaches
to the asset via SmartGroup logic and event history logger.

If the UPS and/or ManageUPS network adapter are replaced, or exchanged,
and the UPS asset will remain in the same physical or electrical supply
location you should try to reuse the previous IP address and network name
from the previous adapter and enter these in the new adapter.
When CIO refreshes the monitored properties of the device, the
manufacturer, model , nominal ratings and serial number of the new UPS will
be retrieved by CIO and associated with the existing entry in the All devices
list.

If it is not possible to reuse the
previous IP address in a new
adapter, right click the device entry
in the All Devices list to access the
Settings dialog associated with the
device . Enter the new network
address and port that CIO should
associate with the asset.

If you need to change from SNMP to mopNET, or mopNET to SNMP protocol
for the communications between CIO and the UPS management card
2
, you
will need to remove the asset from the All Devices list, then re-add it using the
new communications protocol. This will reset the unique identifier associated
with the physical asset. The BACNET instance number will change and the
recent alarms history, Name and PinMap location will be cleared.

2
The only reason to change the communications protocol between CIO and the UPS Management adapter is a
change in UPS brand deployed as replacement for the previous brand. The preferred protocol for monitoring Chloride
UPS via CIO is Chlorides own TCP layer protocol mopNET. For 3
rd
party UPS, CIO uses the standard published
SNMP MIBs. SNMP is a UDP layer protocol, generally less reliable that TCP layer protocol.
14
PICS Tab
The PICS statement that matches the specific version of the BACnet server is
displayed on this tab.

ManageUPS CIO BACnet Supplement-090210

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

ManageUPS CIO BACnet Supplement-090210

Enviado por

Direitos autorais:

Formatos disponíveis

ManageUPS CIO UsrGuide 913-601_BACnet Supplement page

DOC VER. 090210, CIO Software Version 1.2.1 (2992)

Você também pode gostar