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 portable building apps use case draft #132

Merged
merged 2 commits into from
Sep 14, 2021
Merged

Add portable building apps use case draft #132

merged 2 commits into from
Sep 14, 2021

Conversation

gtfierro
Copy link
Contributor

@gtfierro gtfierro commented May 6, 2021

Addresses the request in #121

Happy to take comments, suggestions, questions and critiques!

@mlagally
Copy link
Contributor

Use case call on 29.6.:
We started to review the PR and ran out of time. Will continue in the next use case call.
Michael Koster knows Gabe Fierro and will invite him to the next use case call.

@gtfierro
Copy link
Contributor Author

gtfierro commented Jul 1, 2021

@mlagally I should be able to attend the next call (I have it listed on my calendar as July 13th @ 8am Pacific?). Apologies for being away; I'm in the middle of moving to a new state to begin a new position

@mlagally
Copy link
Contributor

mlagally commented Jul 6, 2021

@gtfierro
The next Use Case call is scheduled on July 13 at 12pm UTC, which unfortunately is very early for you (5am).
We can try to reschedule to give people from the US a better chance to attend.

* virtual metering (calculating the energy or power consumption of a subsystem that is not directly metered)
* building performance measurement and energy audits
* predictive occupancy, energy consumption models
* high-performance "sequences of operations" for various subsystems, such as HVAC
Copy link
Contributor

Choose a reason for hiding this comment

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

Please clarify what is meant by that

* high-performance "sequences of operations" for various subsystems, such as HVAC

There is still significant cost in deploying these applications because of the effort required to customize and configure their operation for each individual building.
While ontologies exist for describing sensors and the data they produce and for describing the spatial topology of buildings, the applications above require modeling the context of data sources that are embedded **within** building subsystems.
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this related to SSN and features of interest?
Geospatial relationship?


There is still significant cost in deploying these applications because of the effort required to customize and configure their operation for each individual building.
While ontologies exist for describing sensors and the data they produce and for describing the spatial topology of buildings, the applications above require modeling the context of data sources that are embedded **within** building subsystems.
Therefore, there is a need to model the topology and composition of building subsystems, including HVAC systems, lighting systems, electrical systems, domestic water systems and hot and chilled water systems.
Copy link
Contributor

Choose a reason for hiding this comment

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

this triggers requirements for a module concept and graphs for modeling the topology and composition of things

@mlagally mlagally merged commit d2db772 into w3c:main Sep 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants