search

BuildingSync / TestSuite

Other
4 stars 1 forks source link

Provide example of how TS data and ResourceUses should be linked / mapped. #6

Open corymosiman12 opened 4 years ago

corymosiman12 commented 4 years ago

In ATT, upon import from ENERGYSTAR (using example Excel sheet):

  1. kBtu from spreadsheet -> kWh as expected
  2. kWh/day and kBtu/day as expected.

Upon download of BSync:

  1. TS Data available under 3 of the scenarios (although many more scenarios than 3), however, NG and Elec are confusing:
    1. The Resource Use appears to get exported correctly. We end up having three uses: 1) Fuel oil number 4, 2) Natural gas, 3) Electricity…all good
      1. Fuel oil number 4:
        1. Interval reading gets set to ‘day’, I think the logic being that the fuel is just delivered on a single day.
        2. ReadingType set to ‘Point’…maybe need to clarify a bit what the different ReadingTypes mean
        3. Maybe this guy ok
      2. Natural Gas
        1. ReadingType gets set to Peak – believe this should be ‘Total’ i.e. Total NG usage over the ReadingInterval
        2. TimeSeriesReadingQuantity set to Voltage…obviously incorrect
        3. IntervalFrequency is Other – need to understand how timedelta between dates corresponds to IntervalFrequency… (i.e. btw 28 – 31 days is considered monthly IntervalFrequency…or how?)
      3. Electricity:
        1. ReadingType that gets exported is for the ‘Peak’, which has no data (i.e. 0.0 for every month), which is correct based on data in ATT ii. Electricity Use doesn’t get mapped out into BSync…why? iii. TimeSeriesReadingQuantity set to Voltage… iv. IntervalFrequency = ‘Other’

General question:

  1. Mapping of a ResourceUse within a scenario to an individual TimeSeries element…how is this supposed to work? Because, currently, there can be contradictory scenarios.
    1. Example:
      1. ResourceUse (ID=1):
        1. EnergyResource: Electricity
        2. ResourceUnits: kWh
      2. TimeSeries:
        1. TimeSeriesReadingQuantity: Voltage
        2. ResourceUseID=1
      3. This is a false statement

A few things:

  1. Why not just use FuelTypes and why declare a new EnergyResource?
  2. Simply referring to just a FuelType within a ResourceUse is less limiting
  3. I think Quantity and Units should belong to the same element, either ResourceUse or TimeSeries…
  4. Why not do something like:
    1. VoltageQuantity:
      1. VoltageUnits: one of a, b, c
      2. Basically, the Quantity should limit the applicable units
  5. Would help resolve contradictory scenarios.