Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ReadingType Cost to TimeSeries #200

Merged
merged 8 commits into from
Aug 27, 2020
Merged

Conversation

macintoshpie
Copy link
Contributor

No description provided.

@macintoshpie macintoshpie marked this pull request as draft July 15, 2020 21:47
#### Pros
- non-breaking change
#### Cons
- linking a cost to another reading (eg Total use) is non-trivial and must be done using Start and End Timestamps as well as the ResourceUseID's IDref.
Copy link
Contributor

@corymosiman12 corymosiman12 Jul 16, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

linking a cost about a specific resource to either 1) a single timeseries element (cost only driven by energy consumption) or 2) multiple timeseries elements (cost driven by both energy consumption and peak demand) is non-trivial. One must:

  1. Find all auc:ReadingType=Cost associated with a ResourceUse
  2. Ensure start and end timestamps align across different auc:TimeSeries elements (i.e. the cost and the reading are referring to the same period of time).

Comment on lines 161 to 163
<auc:IntervalTotal>123</auc:Total>
<auc:IntervalPeak>123</auc:Peak>
<auc:IntervalCost>1000</auc:Cost>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix:

            <auc:IntervalTotal>123</auc:IntervalTotal>
            <auc:IntervalPeak>123</auc:IntervalPeak>
            <auc:IntervalCost>1000</auc:IntervalCost>

Copy link
Contributor

@corymosiman12 corymosiman12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor changes. In general, I like option 4 or option 5 best.

@macintoshpie macintoshpie marked this pull request as ready for review July 16, 2020 15:42
@macintoshpie macintoshpie requested a review from nllong July 16, 2020 15:42
@macintoshpie macintoshpie changed the title feat(propsals): write proposal for timeseries cost feat(proposals): write proposal for timeseries cost Jul 16, 2020
@macintoshpie macintoshpie marked this pull request as draft July 27, 2020 19:23
@macintoshpie
Copy link
Contributor Author

Waiting to fully finish 211 <> BuildingSync mapping before making final decisions about the proposal.
ie Don't merge this for now.

@macintoshpie macintoshpie added DO NOT MERGE STD 211 Mapping Related to the effort of mapping ASHRAE 211 levels to BuildingSync labels Jul 29, 2020
@macintoshpie macintoshpie marked this pull request as ready for review August 26, 2020 20:21
Copy link
Contributor

@markborkum markborkum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good, thanks.

@macintoshpie macintoshpie merged commit c0fdc79 into develop Aug 27, 2020
@macintoshpie macintoshpie deleted the feat/time-series-cost branch August 27, 2020 18:20
@macintoshpie macintoshpie changed the title feat(proposals): write proposal for timeseries cost Add ReadingType Cost to TimeSeries Sep 2, 2020
@macintoshpie macintoshpie added Schema: General General update to BuildingSync Schema: Reports Update to reports Non-breaking Change and removed Schema: General General update to BuildingSync labels Sep 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Non-breaking Change Schema: Reports Update to reports STD 211 Mapping Related to the effort of mapping ASHRAE 211 levels to BuildingSync
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants