Good day! Thank you for the prompt reply.
Well noted on the above and appreciate your detailed explanations. Just to clarify the below if I understand the idea/concept correctly.
Indicates that measured data is available throughout the past month and usage (kWh) was calculated based on the measured data (average across the period).
with TWO asterisk **
Indicates that measured data is not available for the full time period, however, usage (kWh) was still calculated based on the measured data available (average across the period).
with ONE asterisk *
Indicates that usage (kWh) was calculated solely based on estimated load as there is possibly no measured data available during the period.
Your explanation for the scenario observed on the Energy Cost report generated from July to August seems logical, assuming ITA uses only either the measured data or estimated load across the period for the calculations.
My team and I managed to retrieve the latest backup for the IT Advisor (ITA) from our customer site today. And YES, we can share the backup files. I have uploaded the backup onto Box and will share the hyperlink to the files with you separately via email. We can discuss further on this once we have gotten a chance to have a closer look at the data as well.
... View more
Recently, we noticed there is a huge difference of the Usage (kWh) from Energy Cost report generated (July vs August) . It was confirmed by user that there were no load removed from existing racks during the period. Please find below the attached Energy Cost report snapshot for three (3) racks usage (kWh) for the month of July and August.
Month of July (01 - 31 July)
Month of August (01 - 31 August)
With reference to the above Energy Cost report, the usage (kWh) for the month of August is significantly lower as compared to the month of July (highlighted in red ). The only difference we observed from the report was the indication of asterisk sign * vs ** next to the rack identification (highlighted in orange ). Referring to the description in the Energy Cost report, it describes as below.
For the month of August, it seems that measured data was not available for the full time period for the racks (**). However, based on the description, we should expect a higher data values when no measured data is available as the Energy Cost report will be based on estimated load. We have cross-checked the estimated load of the racks (based on adjusted nameplates) is significantly higher than the measured peak data. Thus, would like to check whether anyone have any idea with regards to the findings above?
When we generated the Energy Cost report for the period of 01 July to 31 August (two months), the usage (kWh) was not compounded but instead showing a low value close to the readings observed for month of August only.
Month of July and August (01 July - 31 August)
To summarize, below are my inquiries:
1. In what situation would the system categorize "measured data not available for a full period" for the racks (e.g. no data from DCE for a prolonged period)?
2. Shouldn't the Energy Cost calculation for usage (kWh) expected to be higher when measured data is not available, where the estimated load is used instead?
3. What could be the reason for the usage (kWh) for the period of 01 July to 31 August not compounded or is lower when Energy Cost report generated for two months instead of individual month?
4. Is there a more detailed description or clarification on Energy Cost calculation than the information that is readily available on our DCIM support page (as per attached link below)?
Referred references: https://dcimsupport.ecostruxureit.com/hc/en-us/articles/360038075894-Energy-Cost-Report
Data Center Expert (DCE)
IT Advisor (ITA)
Appreciate any help and input with the above.
... View more