Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
C
citygml-energy
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • energyade
  • citygml-energy
  • Issues
  • #171

Closed
Open
Opened Oct 11, 2019 by Joachim Benner@JoachimBennerMaintainer

Heating and Cooling system availability schedules

The UsageZone class enables to specify schedules for heating and cooling set-point temperatures. It is implicitly assumed that the corresponding building systems are operating at any time. In practice, building systems may be not available at specific times of the year (e.g. heating in summer times) or of the day. At the moment, this could only be realized by specifying very low set-point temperatures for heating (or very high temperatures for the cooling system).

In order to decouple system set-point temperatures and system availability, it is proposed to introduce 2 new poptional properties in UsageZone:

heatingAvailabilitySchedule: DailyPatternSchedule[0..1]

coolingAvailabilitySchedule: DailyPatternSchedule[0..1]

In both schedules, there are only the values 0 (not available) and 1 (available).

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: energyade/citygml-energy#171