Load Shape Library: Sync eTRM draft measures to Cedars database
Set up a sync between Cedars and eTRM to pull the eTRM draft measure package data into Cedars to support the load shape library.
eTRM data will be available in staging on Jan 30 and in production on Feb 12.
As a user I want CEDARS to be synced with the most up to date list of draft measure packages, so I can use them to add load shapes.
Draft workflow including questions
- Select the module in CEDARS
- Select user type
Log in to comment and vote
Comments10
Jennifer Scheuerell
Jan 27
E3MeaElecEndUseShape will be generated as the concatenation of:
Building Type
Building Vintage
Building HVAC
Technology Group
Technology Type
Technology ID
e.g. “RFF*Ex*Any*WaterHtg_eq*HP_UEF*Stor_UEF-ElecHP-065gal-3.50UEF”
Questions
Do we want a prefix for PA generated load shapes and their resulting impact profiles, similar to how the DEER impact profiles start with “DEER:”?
SInce eTRM sets building HVAC = “Any” for all data can we remove it from the concatenation?
What character do we want to use for the concatenation delimiter? DEER uses both underscores and dashes in their values. (I used asterisk * in the example above)
rachel.murray@dnv.com
Jan 30
Here’s my two cents:
I would say “no”. CA went statewide with deemed measures so that the impacts are consistent across a given climate zone, no matter how many IOUs might serve that CZ.
FutEE must fix that.
An asterisk is okay to me. I’m pretty sure that none of those fields contain that character.
Jennifer Scheuerell
Feb 1
@rachel.murray@dnv.com I was wrong that building HVAC is always “Any” in the eTRM permutations, I had been looking at a (large) subset of the eTRM data. Today I saw permutations that have other HVAC options.
dan.pidgeon
Feb 5
@Jennifer Scheuerell My assumption is HVAC (SWHC), Whole Building (SWWB), and Service (SWSV) measure packages should have the building HVAC field populated to something other than ‘Any’. A lot of other measure packages (appliance - SWAP, food service - SWFS, process - SWPR, recreation - SWRE, Water Heating - SWWH) will likely use ‘Any’ as those savings are not as dependent on the type of HVAC system. There is likely an exception to the rule in this summary somewhere, but in general this is what I would expect to see when looking at the master permutation database from a BldgHVAC perspective.
dan.pidgeon
Feb 5
@Jennifer Scheuerell @rachel.murray@dnv.com Also, I think we need Building Location in the E3MeasElecEndUseShape concatenation. Most modeled measures will have load shapes that differ among climate zones in addition to different UECs per climate zone. Thoughts?
Jennifer Scheuerell
Jan 27
How do we want to re-sync to refresh the draft permutation data?
Automated nightly sync
On-demand button for users
When load shapes are uploaded
Other?
rachel.murray@dnv.com
Jan 30
This is a good question for FutEE and measure package developers.
Jennifer Scheuerell
Jan 27
Do we need to resolve data inconsistencies between eTRM and CET?
Sector e.g “Com” versus E3TargetSector e.g. “Commercial”
Building Location e.g. “CZ03” versus E3ClimateZone e.g. “3a”
No IOU_AC_Territory data in eTRM
rachel.murray@dnv.com
Jan 30
Since the avoided costs differ between 3A and 3B and the impact profiles do not, I don’t think the eTRM needs to be consistent with the ACCs.
Jennifer Scheuerell
Feb 4
Feb 4 update: These data were scheduled to available from eTRM on Jan 30. Access to the tables was provided by Chau on Jan 30 but testing revealed that the tables do not return data when queried. The eTRM team was notified of the issue and have confirmed the data tables do not return results when queried.