RF Code CenterScape Connector

RF Code CenterScape offers real-time asset management and environmental monitoring solution. CenterScape continuously tracks physical asset locations and environmental conditions allowing users to locate and manage equipment, identify and troubleshoot power and cooling inefficiencies and avoid downtime. The integration of the CenterScape into Data Center Operation simplifies the management of complex data and reduces data manipulation, providing a single source of information.

Prerequisites

DCO with Change license
RF Code CenterScape version 1 and above
User access to CenterScape web services for integration
Open port and communication between DCO and CenterScape (CenterScape port number depends on the customer installation)

Preparation

Field mapping

This CenterScape data will always be synchronized with DCO:

Asset Data

Custom Properties

Environmental Sensor Readings

Name

Serial Number

Location

Description

Model name

Manufacturer

Asset Tag

Scope

Deletable

Operationnal Status

Temperature reading

Daily peak temperature

Daily average temperature

Relative Humidity

Connector parameters

This information is to be provided by the customer.

rfcode_user	RF Code user name with webservices access
rfcode_password	RF Code user password
rfcode_host	Url or IP address of your RF Code instance. Typically: http://myserver.rfcode.com/
rfcode_port	RF Code port to query web services (e.g. port 6580)
Remove_deleted	Possible choices: Yes / No. See Deletion of devices.
Change_ticket_due_days	Number of days when a change ticket is due by. Example, 10. See Creation of Change Tickets

Deletion of devices

The user can choose whether the information coming from CenterScape and pushed to DCO should or should not be deleted in DCO when an asset is removed from the CenterScape system.

This does not delete the actual device in the DCO model, only the RF Code information attached to this device.

Creation of Change Tickets

When an asset change location and DCO discovers that Centerscape reports a different detected location than what it previously reported, a change ticket will be created in DCO. These change tickets will appear in DCO and then can be associated with either a new or existing work order.

No change tickets will be created on original asset location assignment
The change tickets will have predefined status as “RF Code generated” and priority “Medium”
Change_ticket_due_days variable decides the number of days from present day to be set for due date.
DCO Change module is required to use this functionality

Note: CenterScape considers Location type of Rack as a valid location. When devices are assigned to DataCenters or Rows, it is not considered as valid locations and hence the change ticket would not be as required. Also when moving a device from DataCenter/Rows to Racks, a change ticket will not be created as this is considered as initial allocation of location.

CI polling interval (job scheduling)

Recommended settings

Up to 60 racks	60 minutes
From 61 to 150 racks	120 minutes
From 151 to 300 racks	180 minutes
From 301 to 500 racks	2400 minutes
Above 500 racks	Please contact technical support

It is not recommended to configure a frequency lower than 60 minutes.

RF Code CenterScape data in DCO

Inventory shows up as unassociated devices. Automatic/manual association is needed.

Temperature and humidity sensors bring in values.

They can be dropped anywhere on the floor, in a rack, or on a device.

Article info

In this article