European Network of

Transmission System Operators

for Electricity

AVAILABILITY SCHEDULE
PROFILE SPECIFICATION

2022-09-21
SOC APPROVED
VERSION 2.1

ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e

 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

1 Copyright notice:
2 Copyright © ENTSO-E. All Rights Reserved.

3 This document and its whole translations may be copied and furnished to others, and derivative
4 works that comment on or otherwise explain it or assist in its implementation may be prepared,
5 copied, published and distributed, in whole or in part, without restriction of any kind, provided
6 that the above copyright notice and this paragraph a re included on all such copies and
7 derivative works. However, this document itself may not be modified in any way, except for
8 literal and whole translation into languages other than English and under all circumstances, the
9 copyright notice or references to ENTSO-E may not be removed.

10 This document and the information contained herein is provided on an "as is" basis.

11 ENTSO-E DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT

12 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
13 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
14 FITNESS FOR A PARTICULAR PURPOSE.

15 This document is maintained by the ENTSO-E CIM EG. Comments or remarks are to be
16 provided at [email protected]

17 NOTE CONCERNING WORDING USED IN THIS DOCUMENT

18 The force of the following words is modified by the requirement level of the document in which
19 they are used.

20 • SHALL: This word, or the terms “REQUIRED” or “MUST”, means that the definition is an
21 absolute requirement of the specification.
22 • SHALL NOT: This phrase, or the phrase “MUST NOT”, means that the definition is an
23 absolute prohibition of the specification.
24 • SHOULD: This word, or the adjective “RECOMMENDED”, means that there may exist valid
25 reasons in particular circumstances to ignore a particular item, but the full implications must
26 be understood and carefully weighed before choosing a different course.
27 • SHOULD NOT: This phrase, or the phrase “NOT RECOMMENDED”, means that there may
28 exist valid reasons in particular circumstances when the particular behaviour is acceptable
29 or even useful, but the full implications should be understood and the case carefully weighed
30 before implementing any behaviour described with this label.
31 • MAY: This word, or the adjective “OPTIONAL”, means that an item is truly optional.
32

– Page 2 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

33 Revision History
Version Release Date Paragraph Comments
0 1 2021-10-12 For CIM EG review
1 0 2022-02-16 SOC approved.
2 1 2022-09-21 SOC approved.

– Page 3 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

34 CONTENTS
35 Copyright notice: ..................................................................................................................... 2
36 Revision History ...................................................................................................................... 3
37 CONTENTS ............................................................................................................................ 4
38 1 Introduction ..................................................................................................................... 7
39 2 Application profile specification ....................................................................................... 7
40 2.1 Version information ............................................................................................ 7
41 2.2 Constraints naming convention .......................................................................... 7
42 2.3 Profile constraints .............................................................................................. 8
43 2.4 Metadata.......................................................................................................... 10
44 2.4.1 Constraints ..................................................................................... 10
45 2.4.2 Reference metadata ....................................................................... 10
46 3 Detailed Profile Specification ......................................................................................... 10
47 3.1 General ............................................................................................................ 10
48 3.2 (NC) AvailabilityAction ..................................................................................... 11
49 3.3 (NC) AvailabilityEquipment .............................................................................. 12
50 3.4 (NC) AvailabilityExceptionalLimit...................................................................... 12
51 3.5 (NC) AvailabilityGroup ..................................................................................... 13
52 3.6 (abstract,NC) AvailabilityPowerSystemFunction ............................................... 13
53 3.7 (abstract,NC) AvailabilityRemedialAction root class ......................................... 14
54 3.8 (NC) AvailabilityRemedialActionScheme .......................................................... 14
55 3.9 (NC) AvailabilitySchedule................................................................................. 15
56 3.10 (NC) AvailabilityContainer ................................................................................ 16
57 3.11 (abstract,NC) BaseIrregularTimeSeries ............................................................ 16
58 3.12 (abstract,NC) BaseTimeSeries ......................................................................... 17
59 3.13 (abstract) Equipment root class ........................................................................ 17
60 3.14 (abstract) EquipmentContainer root class ......................................................... 17
61 3.15 (NC) EventSchedule ........................................................................................ 17
62 3.16 (NC) EventTimePoint root class ....................................................................... 17
63 3.17 (abstract,NC) GridStateAlteration ..................................................................... 18
64 3.18 (abstract,NC) GridStateAlterationCollection root class ..................................... 18
65 3.19 (abstract) IdentifiedObject root class ................................................................ 18
66 3.20 (abstract) OperationalLimit ............................................................................... 19
67 3.21 (abstract,NC) RemedialActionScheme root class ............................................. 19
68 3.22 (NC) TimeSeriesInterpolationKind enumeration ................................................ 19
69 3.23 (NC) AvailabilityFunctionKind enumeration ...................................................... 19
70 3.24 (NC) AvailabilityScheduleCauseKind enumeration ........................................... 20
71 3.25 (NC) BaseTimeSeriesKind enumeration ........................................................... 20
72 3.26 UnitMultiplier enumeration ............................................................................... 20
73 3.27 UnitSymbol enumeration .................................................................................. 21
74 3.28 Seconds datatype ............................................................................................ 27
75 3.29 Boolean primitive ............................................................................................. 27
76 3.30 Date primitive................................................................................................... 27
77 3.31 DateTime primitive ........................................................................................... 27

– Page 4 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

78 3.32 Duration primitive ............................................................................................. 27

79 3.33 Integer primitive ............................................................................................... 27
80 3.34 Float primitive .................................................................................................. 27
81 3.35 String primitive ................................................................................................. 27
82 Annex A (informative): Sample data ...................................................................................... 28
83 A.1 General ............................................................................................................ 28
84 A.2 Sample instance data....................................................................................... 28
85

86 List of figures

87 Figure 1 – Class diagram AvailabilityScheduleProfile::AvailabilityScheduleProfile ................. 11

88 Figure 2 – Class diagram AvailabilityScheduleProfile::Core .................................................. 11
89

90 List of tables

91 Table 1 – Attributes of AvailabilityScheduleProfile::AvailabilityAction .................................... 11

92 Table 2 – Association ends of AvailabilityScheduleProfile::AvailabilityAction with other
93 classes ................................................................................................................................. 12
94 Table 3 – Attributes of AvailabilityScheduleProfile::AvailabilityEquipment ............................. 12
95 Table 4 – Association ends of AvailabilityScheduleProfile::AvailabilityEquipment with
96 other classes ........................................................................................................................ 12
97 Table 5 – Attributes of AvailabilityScheduleProfile::AvailabilityExceptionalLimit .................... 13
98 Table 6 – Association ends of AvailabilityScheduleProfile::AvailabilityExceptionalLimit
99 with other classes ................................................................................................................. 13
100 Table 7 – Attributes of AvailabilityScheduleProfile::AvailabilityGroup .................................... 13
101 Table 8 – Attributes of AvailabilityScheduleProfile::AvailabilityPowerSystemFunction ........... 14
102 Table 9 – Association ends of
103 AvailabilityScheduleProfile::AvailabilityPowerSystemFunction with other classes .................. 14
104 Table 10 – Attributes of AvailabilityScheduleProfile::AvailabilityRemedialActionScheme ....... 14
105 Table 11 – Association ends of
106 AvailabilityScheduleProfile::AvailabilityRemedialActionScheme with other classes ............... 14
107 Table 12 – Attributes of AvailabilityScheduleProfile::AvailabilitySche dule ............................. 15
108 Table 13 – Association ends of AvailabilityScheduleProfile::AvailabilitySchedule with
109 other classes ........................................................................................................................ 15
110 Table 14 – Attributes of AvailabilityScheduleProfile::AvailabilityContainer ............................. 16
111 Table 15 – Association ends of AvailabilityScheduleProfile::AvailabilityContainer with
112 other classes ........................................................................................................................ 16
113 Table 16 – Attributes of AvailabilityScheduleProfile::BaseIrregularTimeSeries ...................... 17
114 Table 17 – Attributes of AvailabilityScheduleProfile::BaseTimeSeries ................................... 17
115 Table 18 – Attributes of AvailabilityScheduleProfile::EventSchedule ..................................... 17
116 Table 19 – Attributes of AvailabilityScheduleProfile::EventTimePoint .................................... 18
117 Table 20 – Association ends of AvailabilityScheduleProfile::EventTimePoint with other
118 classes ................................................................................................................................. 18
119 Table 21 – Attributes of AvailabilityScheduleProfile::GridStateAlteration ............................... 18

– Page 5 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

120 Table 22 – Attributes of AvailabilityScheduleProfile::IdentifiedObject .................................... 18

121 Table 23 – Attributes of AvailabilityScheduleProfile::OperationalLimit ................................... 19
122 Table 24 – Literals of AvailabilityScheduleProfile::TimeSeriesInterpolationKind .................... 19
123 Table 25 – Literals of AvailabilityScheduleProfile::AvailabilityFunctionKind ........................... 19
124 Table 26 – Literals of AvailabilityScheduleProfile::AvailabilityScheduleCauseKind ................ 20
125 Table 27 – Literals of AvailabilityScheduleProfile::BaseTimeSeriesKind ................................ 20
126 Table 28 – Literals of AvailabilityScheduleProfile::UnitMultiplier ............................................ 21
127 Table 29 – Literals of AvailabilityScheduleProfile::UnitSymbol .............................................. 22
128 Table 30 – Attributes of AvailabilityScheduleProfile::Seconds ............................................... 27
129

– Page 6 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

130 1 Introduction
131 The availability schedule profile is a profile to exchange information on availability related to
132 different equipment. Availability schedules and functions are exchanged. A given
133 (un)availability schedule provides information on status, cause and can include multiple
134 equipment that is simultaneously scheduled for unavailability . The availability power system
135 function is an instruction on the relevant power system function availability in regard to a given
136 availability schedule. Only power system functions that are directly impacted are explicitly
137 included. For example, the unavailability of a switch might cause a line to be unavailable. Only
138 the switch is included in the schedule and not the line that becomes de -energized as a cause
139 of the availability schedule for switch.

140 2 Application profile specification

141 2.1 Version information
142 The content is generated from UML model file CIM100_CGMES31v01_501-
143 20v02_NC21v52_MM10v01.eap.

144 This edition is based on the IEC 61970 UML version ‘ IEC61970CIM17v40’, dated ‘2020-08-24’.

145 - Title: Availability schedule vocabulary

146 - Keyword: AS

147 - Description: This vocabulary is describing the availability schedule profile.

148 - Version IRI: http://entsoe.eu/ns/CIM/AvailabilitySchedule-EU/2.1

149 - Version info: 2.1.0

150 - Prior version:

151 - Conforms to: urn:iso:std:iec:61970-600-2:ed-1|urn:iso:std:iec:61970-301:ed-

152 7:amd1|file://iec61970cim17v40_iec61968cim13v13a_ iec62325cim03v17a.eap|urn:iso:
153 std:iec:61970-401:draft:ed-1|urn:iso:std:iec:61970-501:draft:ed-2|file://CGMES-
154 30v25_501-20v01.eap

155 - Identifier: urn:uuid:8d128e35-86c7-4d67-b2dd-93229bf1005a

156

157 2.2 Constraints naming convention

158 The naming of the rules shall not be used for machine processing. The rule names are just a
159 string. The naming convention of the constraints is as follows.

160 “{rule.Type}:{rule.Standard}:{rule.Profile}:{rule.Property}:{rule.Name}”

161 where

162 rule.Type: C – for constraint; R – for requirement

163 rule.Standard: the number of the standard e.g. 301 for 61970 -301, 456 for 61970-456, 13 for
164 61968-13. 61970-600 specific constraints refer to 600 although they are related to one or
165 combination of the 61970-450 series profiles. For NC profiles, NC is used.

166 rule.Profile: the abbreviation of the profile, e.g. TP for Topology profile. If set to “ALL” the
167 constraint is applicable to all IEC 61970-600 profiles.

– Page 7 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

168 rule.Property: for UML classes, the name of the class, for attributes and associations, the name
169 of the class and attribute or association end, e.g. EnergyConsumer, IdentifiedObject.name, etc.
170 If set to “NA” the property is not applicable to a specific UML element.

171 rule.Name: the name of the rule. It is unique for the same property.

172 Example: C:600:ALL:IdentifiedObject.name:stringLength

173 2.3 Profile constraints

174 This clause defines requirements and constraints that shall be fulfilled by applications that
175 conform to this document.

176 This document is the master for rules and constraints tagged " NC". For the sake of self-
177 containment, the list below also includes a copy of the relevant rules from IEC 61970 -452,
178 tagged "452".

179 • C:452:ALL:NA:datatypes

180 According to 61970-501, datatypes are not exchanged in the instance data. The
181 UnitMultiplier is 1 in cases none value is specified in the profile.

182 • R:452:ALL:NA:exchange

183 Optional and required attributes and associations must be imported and exported if they
184 are in the model file prior to import.

185 • R:452:ALL:NA:exchange1

186 If an optional attribute does not exist in the imported file, it does not have to be exported
187 in case exactly the same data set is exported, i.e. the tool is not obliged to automatically
188 provide this attribute. If the export is resulting from an action by the user performed after
189 the import, e.g. data processing or model update the export can contain optional
190 attributes.

191 • R:452:ALL:NA:exchange2

192 In most of the profiles the selection of optional and required attributes i s made so as to
193 ensure a minimum set of required attributes without which the exchange does not fulfil
194 its basic purpose. Business processes governing different exchanges can require
195 mandatory exchange of certain optional attributes or associations. Option al and required
196 attributes and associations shall therefore be supported by applications which claim
197 conformance with certain functionalities of the IEC 61970 -452. This provides flexibility
198 for the business processes to adapt to different business requirem ents and base the
199 exchanges on IEC 61970-452 compliant applications.

200 • R:452:ALL:NA:exchange3

201 An exporter may, at his or her discretion, produce a serialization containing additional
202 class data described by the CIM Schema but not required by this document pr ovided
203 these data adhere to the conventions established in Clause 5.

204 • R:452:ALL:NA:exchange4

205 From the standpoint of the model import used by a data recipient, the document
206 describes a subset of the CIM that importing software shall be able to interpret in o rder
207 to import exported models. Data providers are free to exceed the minimum requirements
208 described herein as long as their resulting data files are compliant with the CIM Schema
209 and the conventions established in Clause 5. The document, therefore, descri bes
210 additional classes and class data that, although not required, exporters will, in all

– Page 8 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

211 likelihood, choose to include in their data files. The additional classes and data are
212 labelled as required (cardinality 1..1) or as optional (cardinality 0..1) to di stinguish them
213 from their required counterparts. Please note, however, that data importers could
214 potentially receive data containing instances of any and all classes described by the
215 CIM Schema.

216 • R:452:ALL:NA:cardinality

217 The cardinality defined in the CIM model shall be followed, unless a more restrictive
218 cardinality is explicitly defined in this document. For instance, the cardinality on the
219 association between VoltageLevel and BaseVoltage indicates that a VoltageLevel shall
220 be associated with one and only one BaseVoltage, but a BaseVoltage can be associated
221 with zero to many VoltageLevels.

222 • R:452:ALL:NA:associations

223 Associations between classes referenced in this document and classes not referenced
224 here are not required regardless of cardinality.

225 • R:452:ALL:IdentifiedObject.name:rule

226 The attribute “name” inherited by many classes from the abstract class IdentifiedObject
227 is not required to be unique. It must be a human readable identifier without additional
228 embedded information that would need to be parsed. The attribute is used for purposes
229 such as User Interface and data exchange debugging. The MRID defined in the data
230 exchange format is the only unique and persistent identifier used for this data exchange.
231 The attribute IdentifiedObject.name is, however, always required for CoreEquipment
232 profile and Short Circuit profile.

233 • R:452:ALL:IdentifiedObject.description:rule

234 The attribute “description” inherited by many classes from the abstract class
235 IdentifiedObject must contain human readable text without additional embedded
236 information that would need to be parsed.

237 • R:452:ALL:NA:uniqueIdentifier

238 All IdentifiedObject-s shall have a persistent and globally unique identifier (Master
239 Resource Identifier - mRID).

240 • R:452:ALL:NA:unitMultiplier

241 For exchange of attributes defined using CIM Data Types (ActivePower , Susceptance,
242 etc.) a unit multiplier of 1 is used if the UnitMultiplier specified in this document is “none”.

243 • C:452:ALL:IdentifiedObject.name:stringLength

244 The string IdentifiedObject.name has a maximum of 128 characters.

245 • C:452:ALL:IdentifiedObject.description:stringLength

246 The string IdentifiedObject.description is maximum 256 characters.

247 • C:452:ALL:NA:float

248 An attribute that is defined as float (e.g. has a type Float or a type which is a Datatype
249 with .value attribute of type Float) shall support ISO/IEC 60559:2020 for floating -point
250 arithmetic using single precision floating point. A single precision float s upports 7
251 significant digits where the significant digits are described as an integer, or a decimal

– Page 9 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

252 number with 6 decimal digits. Two float values are equal when the significant with 7
253 digits are identical, e.g. 1234567 is equal 1.234567E6 and so are 1.234 5678 and
254 1.234567E0.

255 2.4 Metadata

256 ENTSO-E agreed to extend the header and metadata definitions by IEC 61970 -552 Ed2. This
257 new header definitions rely on W3C recommendations which are used worldwide and are
258 positively recognised by the European Commission. The new definitions of the header mainly
259 use Provenance ontology (PROV-O), Time Ontology and Data Catalog Vocabulary (DCAT). The
260 global new header applicable for this profile is included in the metadata and document header
261 specification document.

262 The header vocabulary contains all attributes defined in IEC 61970 -552. This is done only for
263 the purpose of having one vocabulary for header and to ensure transition for data exchanges
264 that are using IEC 61970-552:2016 header. This profile does not use IEC 61970 -552:2016
265 header attributes and relies only on the extended attributes.

266 2.4.1 Constraints

267 The identification of the constraints related to the metadata follows the same convention for
268 naming of the constraints as for profile constraints.

269 • R:NC:ALL:wasAttributedTo:usage

270 The prov:wasAttributedTo should normally be the “X” EIC code of the actor (prov:Agent).

271

272 2.4.2 Reference metadata

273 The header defined for this profile requires availability of a set of reference metadata. For
274 instance, the attribute prov:wasGeneratedBy requires a reference to an activity which produced
275 the model or the related process. The activities are defined as ref erence metadata and their
276 identifiers are referenced from the header to enable the receiving entity to retrieve the “static”
277 (reference) information that is not modified frequently. This approach imposes a requirement
278 that both the sending entity and the receiving entity have access to a unique version of the
279 reference metadata. Therefore, each business process shall define which reference metadata
280 is used and where it is located.

281 3 Detailed Profile Specification

282 3.1 General
283 This package contains the availability schedule profile.

– Page 10 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

284
285 Figure 1 – Class diagram AvailabilityScheduleProfile::AvailabilityScheduleProfile

286 Figure 1: The diagram contains the main classes used in the availability schedule profile.

287
288 Figure 2 – Class diagram AvailabilityScheduleProfile::Core

289 Figure 2: The diagram shows classes from Base CIM used in the availability plan profile.
290 3.2 (NC) AvailabilityAction
291 Inheritance path = AvailabilityPowerSystemFunction : IdentifiedObject
292 Availability action is availability power system function of type grid state alteration (e.g. tap
293 position action).
294 Table 1 shows all attributes of AvailabilityAction.
295 Table 1 – Attributes of AvailabilityScheduleProfile::AvailabilityAction

name mult type description

kind 1..1 AvailabilityFunctionKind (NC) inherited from:
AvailabilityPowerSystemFunction

– Page 11 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

name mult type description

description 0..1 String inherited from: IdentifiedObject
mRID 1..1 String inherited from: IdentifiedObject
name 0..1 String inherited from: IdentifiedObject
296
297 Table 2 shows all association ends of AvailabilityAction with other classes.
298 Table 2 – Association ends of AvailabilityScheduleProfile::AvailabilityAction with other
299 classes

mult name mult type description

from to
0..* GridStateAlteration 1..1 GridStateAlteration (NC) Grid state alteration that is affected
by the availability given by this
availability action.
0..* AvailabilityGroup 0..1 AvailabilityGroup (NC) inherited from:
AvailabilityPowerSystemFunction
1..* AvailabilitySchedule 1..1 AvailabilitySchedule (NC) inherited from:
AvailabilityPowerSystemFunction
300
301 3.3 (NC) AvailabilityEquipment
302 Inheritance path = AvailabilityPowerSystemFunction : IdentifiedObject
303 Availability equipment is availability power system function of type equipment (e.g.
304 ACLineSegment).
305 Table 3 shows all attributes of AvailabilityEquipment.
306 Table 3 – Attributes of AvailabilityScheduleProfile::AvailabilityEquipment

name mult type description

kind 1..1 AvailabilityFunctionKind (NC) inherited from:
AvailabilityPowerSystemFunction
description 0..1 String inherited from: IdentifiedObject
mRID 1..1 String inherited from: IdentifiedObject
name 0..1 String inherited from: IdentifiedObject
307
308 Table 4 shows all association ends of AvailabilityEquipment with other classes.
309 Table 4 – Association ends of AvailabilityScheduleProfile::AvailabilityEquipment with
310 other classes

mult name mult type description

from to
0..* Equipment 1..1 Equipment (NC) Equipment that is affected by the
availability given by this availability
equipment.
0..* AvailabilityGroup 0..1 AvailabilityGroup (NC) inherited from:
AvailabilityPowerSystemFunction
1..* AvailabilitySchedule 1..1 AvailabilitySchedule (NC) inherited from:
AvailabilityPowerSystemFunction
311
312 3.4 (NC) AvailabilityExceptionalLimit
313 Inheritance path = AvailabilityPowerSystemFunction : IdentifiedObject
314 Availability exceptional limit is availability power system function of type operational limit
315 restriction (e.g. current limit on ACLineSegment terminal). This is limits that occur due to special

– Page 12 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

316 operational condition that is outside the normal dynamic rat ing. The exceptional limit could also
317 be the cause of asset related issues, e.g. de-rating due to fault.
318 Table 5 shows all attributes of AvailabilityExceptionalLimit.
319 Table 5 – Attributes of AvailabilityScheduleProfile::AvailabilityExceptionalLimit

name mult type description

value 1..1 Float (NC) Value for the refered operational limit.
kind 1..1 AvailabilityFunctionKind (NC) inherited from:
AvailabilityPowerSystemFunction
description 0..1 String inherited from: IdentifiedObject
mRID 1..1 String inherited from: IdentifiedObject
name 0..1 String inherited from: IdentifiedObject
320
321 Table 6 shows all association ends of AvailabilityExceptionalLimit with other classes.
322 Table 6 – Association ends of AvailabilityScheduleProfile::AvailabilityExceptionalLimit
323 with other classes

mult name mult type description

from to
0..* OperationalLimit 1..1 OperationalLimit (NC) Operational limit that is constrained
by this availability exceptional limit.
0..* AvailabilityGroup 0..1 AvailabilityGroup (NC) inherited from:
AvailabilityPowerSystemFunction
1..* AvailabilitySchedule 1..1 AvailabilitySchedule (NC) inherited from:
AvailabilityPowerSystemFunction
324
325 3.5 (NC) AvailabilityGroup
326 Inheritance path = IdentifiedObject
327 Container to link relevant equipment that is affected by (un)availability schedule across
328 availability coordinator (e.g. TSO-TSO, TSO-DSO or DSO-DSO).
329 Table 7 shows all attributes of AvailabilityGroup.
330 Table 7 – Attributes of AvailabilityScheduleProfile::AvailabilityGroup

name mult type description

description 0..1 String inherited from: IdentifiedObject
mRID 1..1 String inherited from: IdentifiedObject
name 0..1 String inherited from: IdentifiedObject
331
332 3.6 (abstract,NC) AvailabilityPowerSystemFunction
333 Inheritance path = IdentifiedObject
334 Availability power system function describes the power system function that has a non -normal
335 availability in the associated availability schedule. The availability of the function is needed as
336 part of a power flow solution. This function is the cause and n ot the effect of the availability, if
337 the effect can be calculated through power flow. For instance if only the step -up transformer for
338 a generator is not available, the power flow will calculate that the generator is de -energized
339 (outage). If both are tagged as not available it will not be possible to investigate remedial action
340 for connecting the generator. It is expected that the power flow function is able to perform simple
341 topology changes affected by a function taken out of service, e.g. open switches on both end
342 of a ACLineSegment when the ACLineSegment is taken out of service. More complex changes,
343 like change regulation set point, must be described in the linked GridStateAlterationCollection .

– Page 13 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

344 Table 8 shows all attributes of AvailabilityPowerSystemFunction.

345 Table 8 – Attributes of AvailabilityScheduleProfile::AvailabilityPowerSystemFunction

name mult type description

kind 1..1 AvailabilityFunctionKind (NC) Kind of availability that affect the power
system function.
description 0..1 String inherited from: IdentifiedObject
mRID 1..1 String inherited from: IdentifiedObject
name 0..1 String inherited from: IdentifiedObject
346
347 Table 9 shows all association ends of AvailabilityPowerSystemFunction with other classes.
348 Table 9 – Association ends of
349 AvailabilityScheduleProfile::AvailabilityPowerSystemFun ction with other classes

mult name mult type description

from to
0..* AvailabilityGroup 0..1 AvailabilityGroup (NC) Availability group that link all
related power system function controlled
by all relevant system operators.
1..* AvailabilitySchedule 1..1 AvailabilitySchedule (NC) Availability schedule for this
availability power system function.
350
351 3.7 (abstract,NC) AvailabilityRemedialAction root class
352 Availability remedial action is a remedial action that cancel or reschedule an availability
353 schedule.
354 3.8 (NC) AvailabilityRemedialActionScheme
355 Inheritance path = AvailabilityPowerSystemFunction : IdentifiedObject
356 Availability remedial action scheme is availability power system function of type remedial action
357 scheme (e.g. System Integrity Protection Scheme (SIPS)) For instance SIPS that is taken our-
358 of-service due to communication issues.
359 Table 10 shows all attributes of AvailabilityRemedialActionScheme.
360 Table 10 – Attributes of AvailabilityScheduleProfile::AvailabilityRemedialActionScheme

name mult type description

kind 1..1 AvailabilityFunctionKind (NC) inherited from:
AvailabilityPowerSystemFunction
description 0..1 String inherited from: IdentifiedObject
mRID 1..1 String inherited from: IdentifiedObject
name 0..1 String inherited from: IdentifiedObject
361
362 Table 11 shows all association ends of AvailabilityRemedialActionScheme with other classes.
363 Table 11 – Association ends of
364 AvailabilityScheduleProfile::AvailabilityRemedialActionScheme with other classes

mult name mult type description

from to
0..* RemedialActionScheme 1..1 RemedialActionScheme (NC) Remedial action scheme that is
affected by the availability given by this
availability remedial action scheme.

– Page 14 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

mult name mult type description

from to
0..* AvailabilityGroup 0..1 AvailabilityGroup (NC) inherited from:
AvailabilityPowerSystemFunction
1..* AvailabilitySchedule 1..1 AvailabilitySchedule (NC) inherited from:
AvailabilityPowerSystemFunction
365
366 3.9 (NC) AvailabilitySchedule
367 Inheritance path = IdentifiedObject
368 A given (un)availability schedule with a given status and cause that include multiple equipment
369 that need to follow the same scheduling periods.
370 Table 12 shows all attributes of AvailabilitySchedule.
371 Table 12 – Attributes of AvailabilityScheduleProfile::AvailabilitySchedule

name mult type description

cancelledDateTime 0..1 DateTime (NC) The date and time the (un)availability
schedule were cancelled .
causeDescription 0..1 String (NC) A cause description for a cause kind. In
case of CauseKind equals other, description or a
reference of the cause of the (un)availability
schedule.
causeKind 1..1 AvailabilityScheduleCau (NC) Kind of cause for the availability schedule.
seKind
daytimeRestitutionDurati 0..1 Duration (NC) The time required to take the out -of-service
on equipment back into service during daytime. This
includes the start-up time for generating units.
eveningRestitutionDurati 0..1 Duration (NC) The time required to take the out -of-service
on equipment back into service after office hours.
This includes the start-up time for generating
units.
maxRestitutionDuration 0..1 Duration (NC) The maximum time required to take the out -
of-service equipment back into service. This
includes the start-up time for generating units.
priority 1..1 Integer (NC) Value 0 means ignore priority. 1 means the
highest priority, 2 is the second highest priority.
weekendRestitutionDura 0..1 Duration (NC) The time required to take the out -of-service
tion equipment back into service in the weekend or
during bank holidays. This includes the start -up
time for generating units.
description 0..1 String inherited from: IdentifiedObject
mRID 1..1 String inherited from: IdentifiedObject
name 0..1 String inherited from: IdentifiedObject
372
373 Table 13 shows all association ends of AvailabilitySchedule with other classes.
374 Table 13 – Association ends of AvailabilityScheduleProfile::AvailabilitySchedule with
375 other classes

mult name mult type description

from to
0..* RemedialAction 0..1 AvailabilityRemedialActi (NC) Remedial action that is cancelling
on this availability schedule.
0..* GridStateAlterationColle 0..1 GridStateAlterationColle (NC) The grid state alteration collection
ction ction that has this availability schedule.

– Page 15 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

mult name mult type description

from to
0..* DependentOnSchedule 0..1 AvailabilitySchedule (NC) (un)availability schedule requested
by one operator my require another
operator to request there (un)availability
schedule. This association is linking the
schedules so that the dependency is
clear.
0..1 ActualSchedule 0..1 EventSchedule (NC) Actual schedule that relates to this
availability schedule.
0..1 PlannedSchedule 0..1 EventSchedule (NC) Planned schedule that relates to
this planned availability schedule.
0..* PrioritySchedule 0..1 AvailabilitySchedule (NC) Priority schedule. This is the
schedule that has the highest priority
and the only valid if not cancelled.
376
377 3.10 (NC) AvailabilityContainer
378 Inheritance path = AvailabilityPowerSystemFunction : IdentifiedObject
379 Availability container is availability power system function of type equipment container (e.g.
380 Line, Bay etc). This is used when multiple equipment in the relevant container are having the
381 same availability.
382 Table 14 shows all attributes of AvailabilityContainer.
383 Table 14 – Attributes of AvailabilityScheduleProfile::AvailabilityContai ner

name mult type description

kind 1..1 AvailabilityFunctionKind (NC) inherited from:
AvailabilityPowerSystemFunction
description 0..1 String inherited from: IdentifiedObject
mRID 1..1 String inherited from: IdentifiedObject
name 0..1 String inherited from: IdentifiedObject
384
385 Table 15 shows all association ends of AvailabilityContainer with other classes.
386 Table 15 – Association ends of AvailabilityScheduleProfile::AvailabilityContainer with
387 other classes

mult name mult type description

from to
0..* EquipmentContainer 1..1 EquipmentContainer (NC) Equipment container that is
affected by the availability given by this
availability container.
0..* AvailabilityGroup 0..1 AvailabilityGroup (NC) inherited from:
AvailabilityPowerSystemFunction
1..* AvailabilitySchedule 1..1 AvailabilitySchedule (NC) inherited from:
AvailabilityPowerSystemFunction
388
389 3.11 (abstract,NC) BaseIrregularTimeSeries
390 Inheritance path = BaseTimeSeries : IdentifiedObject
391 Time series that has irregular points in time.
392 Table 16 shows all attributes of BaseIrregularTimeSeries.

– Page 16 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

393 Table 16 – Attributes of AvailabilityScheduleProfile::BaseIrregularTimeSeries

name mult type description

interpolationKind 1..1 TimeSeriesInterpolation inherited from: BaseTimeSeries
Kind
kind 1..1 BaseTimeSeriesKind inherited from: BaseTimeSeries
description 0..1 String inherited from: IdentifiedObject
mRID 1..1 String inherited from: IdentifiedObject
name 0..1 String inherited from: IdentifiedObject
394
395 3.12 (abstract,NC) BaseTimeSeries
396 Inheritance path = IdentifiedObject
397 Time series of values at points in time.
398 Table 17 shows all attributes of BaseTimeSeries.
399 Table 17 – Attributes of AvailabilityScheduleProfile::BaseTimeSeries

name mult type description

interpolationKind 1..1 TimeSeriesInterpolation Kind of interpolation done between time point.
Kind
kind 1..1 BaseTimeSeriesKind Kind of base time series.
description 0..1 String inherited from: IdentifiedObject
mRID 1..1 String inherited from: IdentifiedObject
name 0..1 String inherited from: IdentifiedObject
400
401 3.13 (abstract) Equipment root class
402 The parts of a power system that are physical devices, electronic or mechanical.
403 3.14 (abstract) EquipmentContainer root class
404 A modelling construct to provide a root class for containing equipment.
405 3.15 (NC) EventSchedule
406 Inheritance path = BaseIrregularTimeSeries : BaseTimeSeries : IdentifiedObject
407 Time series represent irregular event described by event points in time.
408 Table 18 shows all attributes of EventSchedule.
409 Table 18 – Attributes of AvailabilityScheduleProfile::EventSchedule

name mult type description

interpolationKind 1..1 TimeSeriesInterpolation inherited from: BaseTimeSeries
Kind
kind 1..1 BaseTimeSeriesKind inherited from: BaseTimeSeries
description 0..1 String inherited from: IdentifiedObject
mRID 1..1 String inherited from: IdentifiedObject
name 0..1 String inherited from: IdentifiedObject
410
411 3.16 (NC) EventTimePoint root class
412 Event valid for a given point in time.
413 Table 19 shows all attributes of EventTimePoint.

– Page 17 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

414 Table 19 – Attributes of AvailabilityScheduleProfile::EventTimePoint

name mult type description

atTime 1..1 DateTime (NC) The time the data is valid for.
isActive 1..1 Boolean (NC) True, if the event is occurring (Active) at
this time point. Otherwise false.
415
416 Table 20 shows all association ends of EventTimePoint with other classes.
417 Table 20 – Association ends of AvailabilityScheduleProfile::EventTimePoint with other
418 classes

mult name mult type description

from to
1..* EventSchedule 1..1 EventSchedule (NC) Time series the time point values
belongs to.
419
420 3.17 (abstract,NC) GridStateAlteration
421 Inheritance path = IdentifiedObject
422 Grid state alteration is a change of values describing state (operating point) of one element in
423 the grid model compared to the base case.
424 Table 21 shows all attributes of GridStateAlteration.
425 Table 21 – Attributes of AvailabilityScheduleProfile::GridStateAlteration

name mult type description

description 0..1 String inherited from: IdentifiedObject
mRID 1..1 String inherited from: IdentifiedObject
name 0..1 String inherited from: IdentifiedObject
426
427 3.18 (abstract,NC) GridStateAlterationCollection root class
428 A collection of grid state alterations.
429 3.19 (abstract) IdentifiedObject root class
430 This is a root class to provide common identification for all classes needing identification and
431 naming attributes.
432 Table 22 shows all attributes of IdentifiedObject.
433 Table 22 – Attributes of AvailabilityScheduleProfile::IdentifiedObject

name mult type description

description 0..1 String The description is a free human readable text
describing or naming the object. It may be non
unique and may not correlate to a naming
hierarchy.
mRID 1..1 String Master resource identifier issued by a model
authority. The mRID is unique within an
exchange context. Global uniqueness is easily
achieved by using a UUID, as specified in RFC
4122, for the mRID. The use of UUID is strongly
recommended.
For CIMXML data files in RDF syntax conforming
to IEC 61970-552, the mRID is mapped to rdf:ID
or rdf:about attributes that identify CIM object
elements.

– Page 18 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

name mult type description

name 0..1 String The name is any free human readable and
possibly non unique text naming the object.
434
435 3.20 (abstract) OperationalLimit
436 Inheritance path = IdentifiedObject
437 A value and normal value associated with a specific kind of limit.
438 The sub class value and normalValue attributes vary inversely to the associated
439 OperationalLimitType.acceptableDuration (acceptableDuration for short).
440 If a particular piece of equipment has multiple operational limits of the same kind (apparent
441 power, current, etc.), the limit with the greatest acceptableDuration shall have the small est limit
442 value and the limit with the smallest acceptableDuration shall have the largest limit value. Note:
443 A large current can only be allowed to flow through a piece of equipment for a short duration
444 without causing damage, but a lesser current can be allowed to flow for a longer duration.
445 Table 23 shows all attributes of OperationalLimit.
446 Table 23 – Attributes of AvailabilityScheduleProfile::OperationalLimit

name mult type description

description 0..1 String inherited from: IdentifiedObject
mRID 1..1 String inherited from: IdentifiedObject
name 0..1 String inherited from: IdentifiedObject
447
448 3.21 (abstract,NC) RemedialActionScheme root class
449 Remedial Action Scheme (RAS), Special Protection Schemes (SPS), System Protection
450 Schemes (SPS) or System Integrity Protection Schemes (SIPS).
451 A Remedial Action Scheme consists of one or more stages that can trigger and execute a
452 protection action.
453 3.22 (NC) TimeSeriesInterpolationKind enumeration
454 Kinds of interpolation of values between two time point.
455 Table 24 shows all literals of TimeSeriesInterpolationKind.
456 Table 24 – Literals of AvailabilityScheduleProfile::TimeSeriesInterpolationKind

literal value description

previous The value between two time points is set to
previous value.
457
458 3.23 (NC) AvailabilityFunctionKind enumeration
459 Kind of availability that is affecting the function.
460 Table 25 shows all literals of AvailabilityFunctionKind.
461 Table 25 – Literals of AvailabilityScheduleProfile::Availabil ityFunctionKind

literal value description

inService Function is in service.
outOfService Function is out-of-service.
underTesting Function is under testing and need to expect
unscheduled availability.
462

– Page 19 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

463 3.24 (NC) AvailabilityScheduleCauseKind enumeration

464 The kinds of cause of the (un)availability schedule.
465 Table 26 shows all literals of AvailabilityScheduleCauseKind.
466 Table 26 – Literals of AvailabilityScheduleProfile::AvailabilityScheduleCauseKind

literal value description

commissioning The cause is due to a commissioning.
decommissioning The cause is due to a decommissioning.
functionalControl The cause is due to a functional control (in &
out).
environmentalCondition The cause is due to an environmental condition.
This can lead to exceptional margin and limits.
maintenance The cause is due to a maintenance.
refurbishment The cause is due to a refurbishment, either
upgrade or downgrade.
worksInProximity The cause is due to a works in proximity.
other The cause is of other kind.
467
468 3.25 (NC) BaseTimeSeriesKind enumeration
469 Kind of time series.
470 Table 27 shows all literals of BaseTimeSeriesKind.
471 Table 27 – Literals of AvailabilityScheduleProfile::BaseTimeSeriesKind

literal value description

schedule Time series is schedule data. The values
represent the result of a committed and plan
forecast data that has been through a quality
control and could incur penalty when not
followed.
actual Time series is actual data. The values represent
measured or calculated values that represent the
actual behaviour.
472
473 3.26 UnitMultiplier enumeration
474 The unit multipliers defined for the CIM. When applied to unit symbols, the unit symbol is
475 treated as a derived unit. Regardless of the conten ts of the unit symbol text, the unit symbol
476 shall be treated as if it were a single-character unit symbol. Unit symbols should not contain
477 multipliers, and it should be left to the multiplier to define the multiple for an entire data type.
478 For example, if a unit symbol is "m2Pers" and the multiplier is "k", then the value is k(m**2/s),
479 and the multiplier applies to the entire final value, not to any individual part of the value. This
480 can be conceptualized by substituting a derived unit symbol for the unit t ype. If one imagines
481 that the symbol "Þ" represents the derived unit "m2Pers", then applying the multiplier "k" can
482 be conceptualized simply as "kÞ".
483 For example, the SI unit for mass is "kg" and not "g". If the unit symbol is defined as "kg", then
484 the multiplier is applied to "kg" as a whole and does not replace the "k" in front of the "g". In
485 this case, the multiplier of "m" would be used with the unit symbol of "kg" to represent one gram.
486 As a text string, this violates the instructions in IEC 80000 -1. However, because the unit symbol
487 in CIM is treated as a derived unit instead of as an SI unit, it makes more sense to conceptualize
488 the "kg" as if it were replaced by one of the proposed replacements for the SI mass symbol. If
489 one imagines that the "kg" were replaced by a symbol "Þ", then it is easier to conceptualize the
490 multiplier "m" as creating the proper unit "mÞ", and not the forbidden unit "mkg".
491 Table 28 shows all literals of UnitMultiplier.

– Page 20 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

492 Table 28 – Literals of AvailabilityScheduleProfile::UnitMultiplier

literal value description

y -24 Yocto 10**-24.
z -21 Zepto 10**-21.
a -18 Atto 10**-18.
f -15 Femto 10**-15.
p -12 Pico 10**-12.
n -9 Nano 10**-9.
micro -6 Micro 10**-6.
m -3 Milli 10**-3.
c -2 Centi 10**-2.
d -1 Deci 10**-1.
none 0 No multiplier or equivalently multiply by 1.
da 1 Deca 10**1.
h 2 Hecto 10**2.
k 3 Kilo 10**3.
M 6 Mega 10**6.
G 9 Giga 10**9.
T 12 Tera 10**12.
P 15 Peta 10**15.
E 18 Exa 10**18.
Z 21 Zetta 10**21.
Y 24 Yotta 10**24.
493
494 3.27 UnitSymbol enumeration
495 The derived units defined for usage in the CIM. In some cases, the derived unit is equal to an
496 SI unit. Whenever possible, the standard derived symbol is used instead of the formula for the
497 derived unit. For example, the unit symbol Farad is defined as "F" instead of "CPerV". In cases
498 where a standard symbol does not exist for a derived unit, the formula for the unit is used as
499 the unit symbol. For example, density does not have a standard symbol and so it is represented
500 as "kgPerm3". With the exception of the "kg", which is an SI unit, the unit symbols do not contain
501 multipliers and therefore represent the base derived unit to whi ch a multiplier can be applied as
502 a whole.
503 Every unit symbol is treated as an unparseable text as if it were a single-letter symbol. The
504 meaning of each unit symbol is defined by the accompanying descriptive text and not by the
505 text contents of the unit symbol.
506 To allow the widest possible range of serializations without requiring special char acter handling,
507 several substitutions are made which deviate from the format described in IEC 80000 -1. The
508 division symbol "/" is replaced by the letters "Per". Exponents are written in plain text after the
509 unit as "m3" instead of being formatted as "m" with a superscript of 3 or introducing a symbol
510 as in "m^3". The degree symbol "°" is replaced with the letters "deg". Any clarification of the
511 meaning for a substitution is included in the description for the unit symbol.
512 Non-SI units are included in list of unit symbols to allow sources of data to be correctly labelled
513 with their non-SI units (for example, a GPS sensor that is reporting numbers that represent feet
514 instead of meters). This allows software to use the unit symbol information correctly convert
515 and scale the raw data of those sources into SI-based units.
516 The integer values are used for harmonization with IEC 61850.
517 Table 29 shows all literals of UnitSymbol.

– Page 21 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

518 Table 29 – Literals of AvailabilityScheduleProfile::UnitSymbol

literal value description

none 0 Dimension less quantity, e.g. count, per unit, etc.
m 2 Length in metres.
kg 3 Mass in kilograms. Note: multiplier “k” is
included in this unit symbol for compatibility with
IEC 61850-7-3.
s 4 Time in seconds.
A 5 Current in amperes.
K 6 Temperature in kelvins.
mol 7 Amount of substance in moles.
cd 8 Luminous intensity in candelas.
deg 9 Plane angle in degrees.
rad 10 Plane angle in radians (m/m).
sr 11 Solid angle in steradians (m2/m2).
Gy 21 Absorbed dose in grays (J/kg).
Bq 22 Radioactivity in becquerels (1/s).
degC 23 Relative temperature in degrees Celsius.
In the SI unit system the symbol is °C. Electric
charge is measured in coulomb that has the unit
symbol C. To distinguish degree Celsius from
coulomb the symbol used in the UML is degC.
The reason for not using °C is that the special
character ° is difficult to manage in software.
Sv 24 Dose equivalent in sieverts (J/kg).
F 25 Electric capacitance in farads (C/V).
C 26 Electric charge in coulombs (A·s).
S 27 Conductance in siemens.
H 28 Electric inductance in henrys (Wb/A).
V 29 Electric potential in volts (W/A).
ohm 30 Electric resistance in ohms (V/A).
J 31 Energy in joules (N·m = C·V = W·s).
N 32 Force in newtons (kg·m/s²).
Hz 33 Frequency in hertz (1/s).
lx 34 Illuminance in lux (lm/m²).
lm 35 Luminous flux in lumens (cd·sr).
Wb 36 Magnetic flux in webers (V·s).
T 37 Magnetic flux density in teslas (Wb/m2).
W 38 Real power in watts (J/s). Electrical power may
have real and reactive components. The real
portion of electrical power (I²R or VIcos(phi)), is
expressed in Watts. See also apparent power
and reactive power.
Pa 39 Pressure in pascals (N/m²). Note: the absolute or
relative measurement of pressure is implied with
this entry. See below for more explicit forms.
m2 41 Area in square metres (m²).

– Page 22 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

literal value description

m3 42 Volume in cubic metres (m³).
mPers 43 Velocity in metres per second (m/s).
mPers2 44 Acceleration in metres per second squared
(m/s²).
m3Pers 45 Volumetric flow rate in cubic metres per second
(m³/s).
mPerm3 46 Fuel efficiency in metres per cubic metres
(m/m³).
kgm 47 Moment of mass in kilogram metres (kg·m) (first
moment of mass). Note: multiplier “k” is included
in this unit symbol for compatibility with IEC
61850-7-3.
kgPerm3 48 Density in kilogram/cubic metres (kg/m³). Note:
multiplier “k” is included in this unit symbol for
compatibility with IEC 61850-7-3.
m2Pers 49 Viscosity in square metres / second (m²/s).
WPermK 50 Thermal conductivity in watt/metres kelvin.
JPerK 51 Heat capacity in joules/kelvin.
ppm 52 Concentration in parts per million.
rotPers 53 Rotations per second (1/s). See also Hz (1/s).
radPers 54 Angular velocity in radians per second (rad/s).
WPerm2 55 Heat flux density, irradiance, watts per square
metre.
JPerm2 56 Insulation energy density, joules per square
metre or watt second per square metre.
SPerm 57 Conductance per length (F/m).
KPers 58 Temperature change rate in kelvins per second.
PaPers 59 Pressure change rate in pascals per second.
JPerkgK 60 Specific heat capacity, specific entropy, joules
per kilogram Kelvin.
VA 61 Apparent power in volt amperes. See also real
power and reactive power.
VAr 63 Reactive power in volt amperes reactive. The
“reactive” or “imaginary” component of electrical
power (VIsin(phi)). (See also real power and
apparent power).
Note: Different meter designs use different
methods to arrive at their results. Some meters
may compute reactive power as an arithmetic
value, while others compute the value
vectorially. The data consumer should determine
the method in use and the suitability of the
measurement for the intended purpose.
cosPhi 65 Power factor, dimensionless.
Note 1: This definition of power factor only holds
for balanced systems. See the alternative
definition under code 153.
Note 2 : Beware of differing sign conventions in
use between the IEC and EEI. It is assumed that
the data consumer understands the type of
meter in use and the sign convention in use by
the utility.
Vs 66 Volt seconds (Ws/A).

– Page 23 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

literal value description

V2 67 Volt squared (W²/A²).
As 68 Ampere seconds (A·s).
A2 69 Amperes squared (A²).
A2s 70 Ampere squared time in square amperes (A²s).
VAh 71 Apparent energy in volt ampere hours.
Wh 72 Real energy in watt hours.
VArh 73 Reactive energy in volt ampere reactive hours.
VPerHz 74 Magnetic flux in volt per hertz.
HzPers 75 Rate of change of frequency in hertz per second.
character 76 Number of characters.
charPers 77 Data rate (baud) in characters per second.
kgm2 78 Moment of mass in kilogram square metres
(kg·m²) (Second moment of mass, commonly
called the moment of inertia). Note: multiplier “k”
is included in this unit symbol for compatibility
with IEC 61850-7-3.
dB 79 Sound pressure level in decibels. Note:
multiplier “d” is included in this unit symbol for
compatibility with IEC 61850-7-3.
WPers 81 Ramp rate in watts per second.
lPers 82 Volumetric flow rate in litres per second.
dBm 83 Power level (logarithmic ratio of signal strength ,
Bel-mW), normalized to 1mW. Note: multiplier
“d” is included in this unit symbol for
compatibility with IEC 61850-7-3.
h 84 Time in hours, hour = 60 min = 3600 s.
min 85 Time in minutes, minute = 60 s.
Q 100 Quantity power, Q.
Qh 101 Quantity energy, Qh.
ohmm 102 Resistivity, ohm metres, (rho).
APerm 103 A/m, magnetic field strength, amperes per metre.
V2h 104 Volt-squared hour, volt-squared-hours.
A2h 105 Ampere-squared hour, ampere-squared hour.
Ah 106 Ampere-hours, ampere-hours.
count 111 Amount of substance, Counter value.
ft3 119 Volume, cubic feet.
m3Perh 125 Volumetric flow rate, cubic metres per hour.
gal 128 Volume in gallons, US gallon (1 gal = 231 in3 =
128 fl ounce).
Btu 132 Energy, British Thermal Units.
l 134 Volume in litres, litre = dm3 = m3/1000.
lPerh 137 Volumetric flow rate, litres per hour.
lPerl 143 Concentration, The ratio of the volume of a
solute divided by the volume of the solution.
Note: Users may need use a prefix such a ‘µ’ to
express a quantity such as ‘µL/L’.

– Page 24 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

literal value description

gPerg 144 Concentration, The ratio of the mass of a solute
divided by the mass of the solution. Note: Users
may need use a prefix such a ‘µ’ to express a
quantity such as ‘µg/g’.
molPerm3 145 Concentration, The amount of substance
concentration, (c), the amount of solvent in
moles divided by the volume of solution in m³.
molPermol 146 Concentration, Molar fraction, the ratio of the
molar amount of a solute divided by the molar
amount of the solution.
molPerkg 147 Concentration, Molality, the amount of solute in
moles and the amount of solvent in kilograms.
sPers 149 Time, Ratio of time. Note: Users may need to
supply a prefix such as ‘µ’ to show rates such as
‘µs/s’.
HzPerHz 150 Frequency, rate of frequency change. Note:
Users may need to supply a prefix such as ‘m’ to
show rates such as ‘mHz/Hz’.
VPerV 151 Voltage, ratio of voltages. Note: Users may
need to supply a prefix such as ‘m’ to show rates
such as ‘mV/V’.
APerA 152 Current, ratio of amperages. Note: Users may
need to supply a prefix such as ‘m’ to show rates
such as ‘mA/A’.
VPerVA 153 Power factor, PF, the ratio of the active power to
the apparent power. Note: The sign convention
used for power factor will differ between IEC
meters and EEI (ANSI) meters. It is assumed
that the data consumers understand the type of
meter being used and agree on the sign
convention in use at any given utility.
rev 154 Amount of rotation, revolutions.
kat 158 Catalytic activity, katal = mol / s.
JPerkg 165 Specific energy, Joules / kg.
m3Uncompensated 166 Volume, cubic metres, with the value
uncompensated for weather effects.
m3Compensated 167 Volume, cubic metres, with the value
compensated for weather effects.
WPerW 168 Signal Strength, ratio of power. Note: Users
may need to supply a prefix such as ‘m’ to show
rates such as ‘mW/W’.
therm 169 Energy, therms.
onePerm 173 Wavenumber, reciprocal metres, (1/m).
m3Perkg 174 Specific volume, cubic metres per kilogram, v.
Pas 175 Dynamic viscosity, pascal seconds.
Nm 176 Moment of force, newton metres.
NPerm 177 Surface tension, newton per metre.
radPers2 178 Angular acceleration, radians per second
squared.
JPerm3 181 Energy density, joules per cubic metre.
VPerm 182 Electric field strength, volts per metre.

– Page 25 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

literal value description

CPerm3 183 Electric charge density, coulombs per cubic
metre.
CPerm2 184 Surface charge density, coulombs per square
metre.
FPerm 185 Permittivity, farads per metre.
HPerm 186 Permeability, henrys per metre.
JPermol 187 Molar energy, joules per mole.
JPermolK 188 Molar entropy, molar heat capacity, joules per
mole kelvin.
CPerkg 189 Exposure (x rays), coulombs per kilogram.
GyPers 190 Absorbed dose rate, grays per second.
WPersr 191 Radiant intensity, watts per steradian.
WPerm2sr 192 Radiance, watts per square metre steradian.
katPerm3 193 Catalytic activity concentration, katals per cubic
metre.
d 195 Time in days, day = 24 h = 86400 s.
anglemin 196 Plane angle, minutes.
anglesec 197 Plane angle, seconds.
ha 198 Area, hectares.
tonne 199 Mass in tons, “tonne” or “metric ton” (1000 kg =
1 Mg).
bar 214 Pressure in bars, (1 bar = 100 kPa).
mmHg 215 Pressure, millimetres of mercury (1 mmHg is
approximately 133.3 Pa).
M 217 Length, nautical miles (1 M = 1852 m).
kn 219 Speed, knots (1 kn = 1852/3600) m/s.
Mx 276 Magnetic flux, maxwells (1 Mx = 10-8 Wb).
G 277 Magnetic flux density, gausses (1 G = 10-4 T).
Oe 278 Magnetic field in oersteds, (1 Oe = (103/4p)
A/m).
Vh 280 Volt-hour, Volt hours.
WPerA Active power per current flow, watts per Ampere.
onePerHz Reciprocal of frequency (1/Hz).
VPerVAr Power factor, PF, the ratio of the active power to
the apparent power. Note: The sign convention
used for power factor will differ between IEC
meters and EEI (ANSI) meters. It is assumed
that the data consumers understand the type of
meter being used and agree on the sign
convention in use at any given utility.
ohmPerm 86 Electric resistance per length in ohms per metre
((V/A)/m).
kgPerJ Weight per energy in kilograms per joule (kg/J).
Note: multiplier “k” is included in this unit symbol
for compatibility with IEC 61850-7-3.
JPers Energy rate in joules per second (J/s).
519

– Page 26 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

520 3.28 Seconds datatype

521 Time, in seconds.
522 Table 30 shows all attributes of Seconds.
523 Table 30 – Attributes of AvailabilityScheduleProfile::Seconds

name mult type description

value 0..1 Float Time, in seconds
unit 0..1 UnitSymbol (const=s)
multiplier 0..1 UnitMultiplier (const=none)
524
525 3.29 Boolean primitive
526 A type with the value space "true" and "false".
527 3.30 Date primitive
528 Date as "yyyy-mm-dd", which conforms with ISO 8601. UTC time zone is specified as "yyyy -
529 mm-ddZ". A local timezone relative UTC is specified as "yyyy -mm-dd(+/-)hh:mm".
530 3.31 DateTime primitive
531 Date and time as "yyyy-mm-ddThh:mm:ss.sss", which conforms with ISO 8601. UTC time zone
532 is specified as "yyyy-mm-ddThh:mm:ss.sssZ". A local timezone relative UTC is specified as
533 "yyyy-mm-ddThh:mm:ss.sss-hh:mm". The second component (shown here as "ss.sss") could
534 have any number of digits in its fractional part to allow any kind of precision beyond seconds.
535 3.32 Duration primitive
536 Duration as "PnYnMnDTnHnMnS" which conforms to ISO 8601, where nY expresses a number
537 of years, nM a number of months, nD a number of days. The letter T separates the date
538 expression from the time expression and, after it, nH identifies a number of hours, nM a number
539 of minutes and nS a number of seconds. The number of seconds could be expressed as a
540 decimal number, but all other numbers are integers.
541 3.33 Integer primitive
542 An integer number. The range is unspecified and not limited.
543 3.34 Float primitive
544 A floating point number. The range is unspecified and not limited.
545 3.35 String primitive
546 A string consisting of a sequence of characters. The character encoding is UTF -8. The string
547 length is unspecified and unlimited.
548

549

– Page 27 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e
 Availability Schedule Profile Specification European Network of
Transmission System Operators
for Electricity

550 Annex A (informative): Sample data

551 A.1 General
552 This Annex is designed to illustrate the profile by using fragments of sample data. It is not meant
553 to be a complete set of examples covering all possibilities of using the profile. Defining a
554 complete set of test data is considered a separate activity to be performed for the purpose of
555 setting up interoperability testing and conformity related to this profile.

556 A.2 Sample instance data

557 Intentionally left blank. Sample data will be updated at later stage.

558

559

– Page 28 of 28 –
ENTSO-E | Rue de Spa, 8 | 1000 Brussels | [email protected] | www.entsoe.eu | @entso_e