API for Ecostruxure ITA

[NF-London]

Hi, We have external DCE systems from the hosts managed BMS systems connected to our Ecostruxure ITA.  These capture things like the UPS and other upstream devices in the power chain.  We do not manage the hosts DCE system and merely benefit from the link into ITA.

Although I can see live readings on the upstream devices, and run reports on them, I would like to extract the information using an API.  Is this possible and is there any documentation on achieving this?

We are currently on ITA 9.4.4, potentially upgrading soon.

Nigel

[Jef]

Hi Nigel,

That may not be possible. Using ITA rest api calls we cannot fetch DCE device data/info.

Regarding the documentation:

ITA REST API page: https://<ITA server>/api/current/docs/index.html contains the list of the supported API calls as well as the descriptions.

Kind regards,

Jef

[NF-London]

Hi Jef.  I am not looking to poll the devices on the DCE system, only extract the figures from ITA which is receiving them.  If I can run a report on the device for measured peak power over time then I should be able to extract the power figures from the database somewhere?  Example report attached of power over time for a device that is imported from a DCE managed by the host team into ITA.

N

[gsterling · Accepted solution]

Hello Nigel. Yes, the items like capacity history are present in the API's. They are found under the KPI endpoints.

So if you check the https://<ita-server/api/current view and login, you'll find this section:

Under which you can query kpi historically using the top endpoint, or the latest values using the middle endpoint.

If you expand the "GET /kpis" endpoint you'll see a detailed description of the values you can query including peak measurement info.

To use the API's you'll need to have the UUID of the device, so you'll need the UUID of the pdu, rpp, rack pdu and so on to get its peak measurement data.

Regards

Greg Sterling

[NF-London]

Thanks Greg.  working through these now.  I think you need to add /v8.1/ in the string after api but getting information through now.