DCO-DCE external system data prerequisites?

[DCIM_Support]

DCE is configured in DCO as an external devices to get all our PDU and ATS sensor data

But after device assocations only a few PDU display mesured data. What are the prerequisites in DCE to display power data in DCO? Do the related ddf file of the PDU need to be reviewed?

(CID:120817322)

[DCIM_Support]

Hi Yannick

The presence of the device in DCE does not guarantee it will be properly shown in DCO.  This is dependant on the DDF which must be code to present data to DCO in the correct format.  I recall a EcoStruxure IT Help Center post about DDF and DCO but in any event, you should make sure time sync is OK

http://sxwhelpcenter.ecostruxureit.com/display/public/UADCO8x/The+Importance+of+System+Time+Synchron...

and give DCO 24 hours.

You did not mention make and model of rPDU.  IF they are late model APC with latest firmware and DDF it often works OOB (but sometimes needs a little DDF caress)

Cheers

Ed

(CID:120817331)

[DCIM_Support]

Hi Ed,

Thanks. I already know this post.

We are using different models of rPDU: IBM, Liebert Emerson

The sensors are displayed in DCO only for IBM DPI C13 pdu.

In DCO which data is got from DCE? Is it based on a specific sensor name?

I have noticed the IBM PDU have a sensor, named "PDU Output Total Power" that is diplayed in DCO as "Peak Power". With the current ddf file, the Emerson PDU do not have this kind of sensor, or less explicit "MPH2 1 - Power Source 1 - Power Total"...

Regards,

Yannick

(CID:121210959)

[DCIM_Support · Accepted solution]

Hi Yannick

See https://hlep.se-dmaas.com/display/DCIMDEVELOPER/DCE+Sensor+Mapping+to+DCO

From the ISXCSensorType, a subset of the sensors are mapped in DCO for temperature and power.

Power Sensors:

OUTPUT_POWER_WATTS

OUTPUT_POWER_TOTAL_WATTS

MODULE_OUTPUT_POWER or MODULE_BREAKER_POWER

The only way IO know to absolutely prove that DCE is or is not exposing the exact sensors via teh web service API is to query it.  You can do this by downloading free SoapUI (soapui.org) and then installing the relevant WSDLs form

http://sxwhelpcenter.ecostruxureit.com/display/public/UADCE725/StruxureWare+Data+Center+Expert+Web+S...

ISXCentralDeviceGroupService_v2_0

ISXCentralDeviceService_v2_0
ISXCentralSensorService_v2_0

If you find an issue, you can then go back to multivendorsupport@apc.com and describe exactly what you need.  I know that may be a lot but it's the only way for you to be sure.  

Otherwise, you can go back to multivendorsupport@apc.com and ask for the DDFs that will properly expose the data to DCO

Cheers 

(CID:121211073)

[DCIM_Support]

Hi Ed,

Thanks a lot. I investigated and in fact the ISXCSensorType of the Total Power sensor on the Liebert Emerson rPDU is UNKNOWN unlike the IBM rPDU where it is correctly OUTPUT_POWER_TOTAL_WATTS

I will then contact the support

Cheers

Yannick

(CID:121211206)

[DCIM_Support]

FYI to colleagues Daniel Kwong Eddie Mou Fergus Wong Edward Chan

This is the DCE=> DCO data linkage technical discussion. If we are interfacing with external BMS system via DCE first then to DCO, in-depth understanding and insight into items in this discussion are needed.

This DCE=>DCO data linkage is just 1 part of the full story-chain. We still have

• BMS=>DCE - for Bacnet, we may need Automation Server (AS-P) help. For dry contact, we may need Netbotz etc.
• Modbus Slave device requirement of DCO for proper modeling - We may need 3rd party connector to help convert Modbus TCP Client into multiple Modbus TCP Slave

(CID:132669191)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.