Project

General

Profile

CIM Issues #6757

BasicIntervalSchedule and RegularIntervalSchedule

Added by Chavdar Ivanov 7 months ago. Updated 7 months ago.

Status:
New
Priority:
High
Solution Version:
Breaking Change:
Breaking Change Description:
CIM Impacted Groups:
WG13, WG14, WG16, WG21
Requestor:
Standard(s):
Version:
Clause:
Sub-Clause:
Paragraph:
Table:
Origination Date:
Origination ID:
Originally Assigned To:

Description

BasicIntervalSchedule.startTime has datatype DateTime and description: The time for the first time point. The value can be a time of day, not a specific date.

RegularIntervalSchedule.endTime has datatype DateTime and description: The time for the last time point. The value can be a time of day, not a specific date.

452 has section 4.9 Definition of schedules - text provided below

XML that includes this does not pass SHACL validation due to datatype issue

<cim:BasicIntervalSchedule.startTime>00:00:00</cim:BasicIntervalSchedule.startTime>
<cim:RegularIntervalSchedule.endTime>23:59:59</cim:RegularIntervalSchedule.endTime>

4.9 Definition of schedules
The use of the RegularIntervalSchedule and RegularTimePoint attributes will differ for the different types of schedules derived from RegularIntervalSchedule. To specify a relative time for a schedule, the date portion of the dateTime format can be eliminated, which leaves the ISO 8601 time of day format “hh:mm:ss”. In this format, hh is the number of complete hours that have passed since midnight, mm is the number of complete minutes since the start of the hour, and ss is the number of complete seconds since the start of the minute.
The earliest allowed time used in a schedule (BasicIntervalSchedule.startTime) is “00:00:00”. The latest allowed time used in a schedule (RegularIntervalSchedule.endTime) is “24:00:00”. The point in time specified by the endTime is not included in the period of the schedule.
A schedule defining a day shall be defined with multiple RegularTimePoints associated with the same RegularIntervalSchedule. It shall not be defined with multiple schedules.
For schedules that are associated with Season and DayType, the associations to Season and DayType are not required. If a schedule does not have an associated Season, the schedule will be considered valid for all Seasons. Similarly, if a schedule does not have an association to a DayType, the schedule will be considered to apply to all days of the week.
When SeasonDayTypeSchedules are defined for a given entity, such as ConformLoadSchedules for a given ConformLoadGroup, only one schedule can be defined for a given combination of Season and DayType.

Files

SteadyStateHypothesisSchedule_Profile_Specification.docx SteadyStateHypothesisSchedule_Profile_Specification.docx 707 KB Chavdar Ivanov, 05/08/2024 10:44 AM

Related issues

Related to WG13 Issues - CIM Issues #6680: Support time series/schedule for SSHIn ProgressActions

Also available in: Atom PDF