ETSI TS 103 410-1 V1.1.1 (2017-01)

SmartM2M; Smart Appliances Extension to SAREF; Part 1: Energy Domain

DTS/SmartM2M-103410-1-SAREF4EN

General Information

• Status: Published
• Publication Date: 26-Jan-2017
• Technical Committee: SmartM2M - Smart M2M
• Current Stage: 12 - Completion
• Due Date: 01-Feb-2017
• Completion Date: 27-Jan-2017

Standards Content (Sample)

ETSI TS 103 410-1 V1.1.1 (2017-01)






TECHNICAL SPECIFICATION
SmartM2M;
Smart Appliances Extension to SAREF;
Part 1: Energy Domain

---------------------- Page: 1 ----------------------
2 ETSI TS 103 410-1 V1.1.1 (2017-01)



Reference
DTS/SmartM2M-103410-1-SAREF4EN
Keywords
data sharing, IoT, M2M, ontology, SAREF, smart
appliance

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2017.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 410-1 V1.1.1 (2017-01)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 SAREF4ENER ontology and semantics . 6
4.1 Introduction and overview . 6
4.2 SAREF4ENER . 7
4.2.1 General Overview . 7
4.2.2 Device . 10
4.2.3 Power Profile and Alternatives Group . 10
4.2.4 Power Sequence . 12
4.2.5 Slot . 14
4.2.6 Load control . 16
4.3 Observations about SAREF4ENER . 17
Annex A (informative): Approach . 19
Annex B (informative): Additional concepts. 21
Annex C (informative): Bibliography . 26
History . 27


ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 410-1 V1.1.1 (2017-01)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Smart Machine-to-Machine
communications (SmartM2M).
The present document is part 1 of a multi-part deliverable covering SmartM2M; Smart Appliances Extension to
SAREF, as identified below:
Part 1: "Energy Domain";
Part 2: "Environment Domain";
Part 3: "Building Domain".
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 410-1 V1.1.1 (2017-01)
1 Scope
The present document presents SAREF4ENER, the SAREF extension for EEBus and Energy@Home in the energy
domain.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] EEBus, SPINE.
NOTE: Available at https://www.eebus.org/en/specifications/.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] TNO, EEBus, Energy@Home: "SAREF4EE".
NOTE: Available at https://w3id.org/saref4ee and http://ontology.tno.nl/saref4ee_Documentation_v0.1.pdf.
[i.2] Energy@home Data Model, v2.1, October 2015.
NOTE: Available at http://www.energy-
home.it/Documents/Technical%20Specifications/E@h_data_model_v2.1.pdf.
[i.3] IEC TR 62746-2:2015: "Systems interface between customer energy management system and the
power management system - Part 2: Use cases and requirements".
NOTE: Available at https://webstore.iec.ch/publication/22279.
[i.4] ETSI TR 103 411: "SmartM2M Smart Appliances SAREF extension investigation".
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 410-1 V1.1.1 (2017-01)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
ontology: formal specification of a conceptualization, used to explicit capture the semantics of a certain reality
smart appliances: devices, which are used in the household, e.g. for performing domestic work, and which have the
ability to communicate with each other and which can be controlled via Internet
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
CEM Customer Energy Manager
E@H Energy@Home association
EEBus EEBus initiative
OM Ontology of units of Measure
OWL Web Ontology Language
SAREF Smart Appliances REFerence ontology
TNO Netherlands Organization for Applied Scientific Research
TR Technical Report
TS Technical Specification
UML Unified Modeling Language
XSD W3C XML Schema Definition
4 SAREF4ENER ontology and semantics
4.1 Introduction and overview
The present document is a technical specification of SAREF4ENER, an extension of SAREF that was created in
collaboration with Energy@Home (http://www.energy-home.it) and EEBus (http://www.eebus.org/en), the major Italy-
and Germany-based industry associations, to enable the interconnection of their (different) data models. The
Energy@Home association, abbreviated in the rest of the document as E@H. E@H aims at developing and promoting
technologies and services for energy efficiency in smart homes, based upon the interaction between user devices and the
energy infrastructure. The E@H data model is described in [i.2]. EEBus is an important initiative in the area of the
Internet of Things, which has its roots in the sector of smart and renewable energy. EEBus developed a standardized
and consensus-oriented smart grid and smart home networking concept. The EEBus data model is described in [1].
SAREF4ENER is meant to enable the (currently missing) interoperability among various proprietary solutions
developed by different consortia in the smart home domain. By using SAREF4ENER, smart appliances from
manufacturers that support the EEBus or E@H data models will easily communicate with each other using any energy
management system at home or in the cloud.
Towards this aim, SAREF4ENER should be used to annotate (or generate) a neutral (protocol-independent) set of
messages to be directly adopted by the various manufacturers, or mapped to their domain specific protocols of choice.
SAREF4ENER is an OWL-DL ontology that extends SAREF with 63 classes, 17 object properties and 40 data type
properties. SAREF4ENER focuses on demand response scenarios, in which customers can offer flexibility to the Smart
Grid to manage their smart home devices by means of a Customer Energy Manager (CEM). The CEM is a logical
function for optimizing energy consumption and/or production that can reside either in the home gateway or in the
cloud. Moreover, the Smart Grid can influence the quantity or patterns of use of the energy consumed by customers
when energy-supply systems are constrained, e.g. during peak hours. These scenarios involve the following use cases:
• Use case 1: configuration of devices that want to connect to each other in the home network, for example, to
register a new dishwasher to the list of devices managed by the CEM;
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 410-1 V1.1.1 (2017-01)
• Use case 2: smart energy management/ (re-)scheduling appliances in certain modes and preferred times using
power profiles to optimize energy efficiency and accommodate the customer's preferences;
• Use case 3: monitoring and control of the start and status of the appliances;
• Use case 4: reaction to special requests from the Smart Grid, for example, incentives to consume more or less
depending on current energy availability, or emergency situations that require temporary reduction of the
power consumption.
These use cases are associated with the user stories described in [i.3], which include, among others, the following
examples:
• User wants to do basic settings of his/her devices;
• User wants to know when the washing machine has finished working;
• User wants the washing done by 5:00 p.m. with least electrical power costs;
• User likes to limit his/her own energy consumption up to a defined limit;
• User allows the CEM to reduce the energy consumption of his/her freezer in a defined range for a specific
time, if the grid recognizes (severe) stability issues;
• Grid related emergency situations (blackout prevention).
The prefixes and namespaces used in SAREF4ENER and in the present document are listed in Table 1.
Table 1: Prefixes and namespaces used within the SAREF4ENER ontology
Prefix Namespace
s4ener https://w3id.org/saref4ener
saref https://w3id.org/saref#
dcterms http://purl.org/dc/terms/
owl http://www.w3.org/2002/07/owl#
rdf http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs http://www.w3.org/2000/01/rdf-schema#
om http://www.wurvoc.org/vocabularies/om-1.8/
xsd http://www.w3.org/2001/XMLSchema#

4.2 SAREF4ENER
4.2.1 General Overview
An overview of the SAREF4ENER ontology is provided in Figure 1, where rectangles containing an orange circle are
used to denote classes created in SAREF4ENER, while rectangles containing a faded orange circle denote classes
reused from other ontologies, such as SAREF. For all the entities described in this document, it is indicated whether
they are defined in the SAREF4ENER extension or elsewhere by the prefix included before their identifier, i.e. if the
element is defined in SAREF4ENER the prefix is s4ener:, while if the element is reused from another ontology it is
indicated by a prefix according to Table 1.
Arrows with white triangles on top represent the rdfs:subClassOf relation between two classes. The origin of the
arrow is the class to be declared as subclass of the class at the destination of the arrow.
Directed arrows are used represent properties between classes.
Rectangles that contain a list of values between square brackets denote an enumeration of individuals.
Note that Figure 1 aims at showing a global overview of the main classes of SAREF4ENER and their mutual relations.
More details on the different parts of Figure 1 are provided in clause 4.2.2 to clause 4.2.6.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 410-1 V1.1.1 (2017-01)

Figure 1: SAREF4ENER overview
Figure 2 shows the hierarchy of classes and properties defined in SAREF4ENER.
Orange circles represent classes of SAREF4ENER, while faded orange circles represent classes that are reused from
other ontologies. Object properties - which are properties between two classes - are denoted by blue rectangles, while
datatype properties - which are properties between a class and a data type, such as xsd:string or xsd:dateTime
- are denoted by green rectangles. Faded blue and green rectangles denote object properties and datatype properties that
are reused from other ontologies.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 410-1 V1.1.1 (2017-01)

Figure 2: SAREF4ENER class and property hierarchy
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 410-1 V1.1.1 (2017-01)
4.2.2 Device
A s4ener:Device is a subclass of a saref:Device, i.e. it inherits the properties of the more general saref:Device
and extends it with additional properties that are specific for SAREF4ENER. The s4ener:Device class is shown in
Figure 3.

Figure 3: Device
Table 2 summarizes the properties that characterize a s4ener:Device.
Table 2: Properties of a Device
Property Definition
s4ener:exposes min 0 s4ener:PowerProfile A relationship between a device and its power profile.
s4ener:receives min 0
A relationship between a device (e.g. an appliance or a smart
s4ener:LoadControlEventData meter) and a load control event.
s4ener:brandName max 1 xsd:string The name of the brand of a device. Useful where the name of
the brand and the vendor differs.
s4ener: deviceCode max 1 xsd:string Device code for the device as defined by the manufacturer.
s4ener: s4ee:deviceName max 1 xsd:string Name of the device as defined by the manufacturer.
s4ener: hardwareRevision max 1 xsd:string
Hardware revision of the device as defined by the
manufacturer.
s4ener:manufacturerDescription max 1 xsd:string A description for the device as defined by the manufacturer.
s4ener:manufacturerLabel max 1 xsd:string
A short label of the device as defined by the manufacturer.
s4ener:manufacturerNodeIdentification max 1
A node identification for the device as defined by the
xsd:string manufacturer. This could be used for the identification of a
device, even if it was removed from the network and re-joined
later with changed node address.
s4ener:powerSource min 0 xsd:string
The power source of a device. Possible values are
{"unknown", "mainsSinglePhase", "mains3Phase", "battery",
"dc"}.
s4ener:serialNumber max 1 xsd:string Serial number of a device as defined by the manufacturer.
Usually the same as printed on the case.
s4ener:softwareRevision max 1 xsd:string Software revision of a device as defined by the manufacturer.
s4ener:vendorCode max 1 xsd:string Code for the vendor of the device as defined by the
manufacturer.
s4ener:vendorName max 1 xsd:string Name of the vendor of the device as defined by the
manufacturer.

4.2.3 Power Profile and Alternatives Group
This clause presents the classes of interest for smart energy management. These classes are used to schedule devices in
certain modes and preferred times using power profiles to optimize energy efficiency and accommodate the customer's
preferences (i.e. use case 2). These classes are s4ener:PowerProfile, s4ener:Alternative,
s4ener:PowerSequence and s4ener:Slot, which are shown in Figure 4.
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 103 410-1 V1.1.1 (2017-01)
A s4ener:PowerProfile is a subclass of a saref:Profile, i.e. it inherits the properties of the more general
saref:Profile extending it with additional properties that are specific for SAREF4ENER. The
s4ener:PowerProfile is used by a s4ener:Device to expose the power sequences that are potentially relevant
for the CEM. A s4ener:Device can expose a s4ener:PowerProfile, which consists of one or more
alternative plans (s4ener:AlternativesGroup class). A s4ener:AlternativesGroup consists of one or
more power sequences (s4ener:PowerSequence class), and a s4ener:PowerSequence consists of one or
more slots (s4ener:Slot class). Inversely, a s4ener:Slot belongs to only and exactly one
s4ener:PowerSequence, which, in turn, belongs to only and exactly one s4ener:AlternativesGroup,
which, in turn, belongs to only and exactly one s4ener:PowerProfile. A s4ener:PowerProfile belongs to
only and exactly one s4ener:Device.

Figure 4: Power Profile and Alternatives Group
Table 3 summarizes the properties that characterize a s4ener:PowerProfile and an
s4ener:AternativesGroup.
ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 103 410-1 V1.1.1 (2017-01)
Table 3: Properties of a Power Profile and an AlternativesGroup
Property Definition
s4ener:alternativesGroupID exactly 1
The endpoint-wide unique identifier for the alternatives
xsd:unsignedInt group instances provided by a power profile.
s4ener:alternativesCount exactly 1 xsd:integer Number of "alternatives" groups provided by a power
profile.
s4ener:nodeRemoteControllable exactly 1 Whether the device is configured for remote control by the
xsd:boolean CEM. This refers to the selection chosen by the user on
the remote control feature of the device.
s4ener:supportsReselection exactly 1 xsd:boolean
Whether the device restricts the number of sequence
re-selections by the CEM. If set to TRUE, there is no
restriction, i.e. within a given alternative the CEM may first
choose one sequence, alter the selection by configuring
another sequence later on, then alter the selection again,
etc. If set to FALSE, the device permits the CEM to select
a sequence of an alternative only one time.
s4ener:supportsSingleSlotSchedulingOnly exactly 1
Whether the device permits the modification of more than
xsd:boolean one slot per configuration command. If set to TRUE the
device does NOT permit this modification.
s4ener:totalSequencesCountMax exactly 1 Total number of sequences supported by the device,
xsd:unsignedInt i.e. the sum of all power sequences across all alternatives.

4.2.4 Power Sequence
The s4ener:AlternativesGroup described in clause 4.2.3 consists of one or more power sequences
(s4ener:PowerSequence class) and, inversely, a s4ener:PowerSequence belongs to only and exactly one
s4ener:AlternativesGroup. Figure 5 shows the details of the s4ener:PowerSequence class.
ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 103 410-1 V1.1.1 (2017-01)

Figure 5: Power Sequence
Table 4 summarizes the properties that characterize a s4ener:PowerSequence.
Table 4: Properties of the PowerSequence
Property Definition
s4ener:sequenceId exactly 1 xsd:unsignedInt An endpoint-wide unique sequence identifier.
saref:hasDescription max 1 xsd:string Textual description for the power sequence.
s4ener:isStoppable max 1 xsd:boolean If the power sequence is stoppable by the CEM, this
element is TRUE. Otherwise it SHALL be omitted.
s4eef:isPausable max 1 xsd:boolean If the power sequence is pausable by the CEM, this
element is TRUE. Otherwise it SHALL be omitted.
s4ener:taskIdentifier min 0 xsd:unsignedInt
Used by a device that wants to uniquely identify
reoccurring types of power sequences. For example,
specific types of washing cycles with specific parameters
SHOULD have the same s4ener:taskIdentifier value every
time they are offered using power sequences.
s4ener:activeRepetitionNumber max 1 The current repetition of the sequence of slots. SHALL be
xsd:unsignedInt present if s4ener:repetitionsTotal is present and has a
value > 1. Otherwise, it SHALL be absent.
s4ener:activeSlotNumber max 1 xsd:unsignedInt If s4ener:PowerSequenceState is set to "running" or
"paused" this element SHALL contain the currently active
slot. Otherwise it SHALL be omitted.
s4ener:cheapest max 1 xsd:boolean If present and set to TRUE, the CEM shall try to apply a
configuration that minimizes the user's energy bill for this
power sequence. Absence of this element is equal to the
presence with value FALSE.
ETSI

---------------------- Page: 13 ----------------------
14 ETSI TS 103 410-1 V1.1.1 (2017-01)
Property Definition
s4ener:greenest max 1 xsd:boolean If present and set to TRUE, the CEM shall try to optimize
the configuration towards the maximum availability of
renewable energy. Absence of this element is equal to the
presence with value FALSE.
s4ener:maxCyclesPerDay max 1 xsd:unsignedInt The maximum amount of starts that the device allows per
day.
s4ener:repetitionsTotal max 1 xsd:unsignedInt If a power sequence repeats its sequence of slots, the
element is present and contains the total number of
repetitions. Absence of the element is equal to a presence
with a value of 0 (zero). SHALL be absent if the value is 1.
s4ener:sequenceRemoteControllable exactly 1 Whether the sequence is modifiable (if value is TRUE) or
xsd:boolean not (if value is FALSE). Modifiability is required to
configure power sequences and slots. It is also required to
change a power sequence state.
s4ener:valueSource min 0 {"measuredValue", The source (origin/foundation) of the measurement
"calculatedValue", "empiricalValue"} forecasted values for this power sequence. If absent, the
source is undefined.
s4ener:hasEnergy max 1
The additional energy the device will consume before
s4ener:ResumeEnergyEstimated resuming its normal operation (after a pause). This is only
an estimated value which will not be added to the value
stated in any slot value information.
saref:hasPrice max 1 s4ener:ResumeCostEstimated The additional costs for the resumption of a device to its
normal operation (after a pause).
saref:hasState min 1 s4ener:PowerSequenceState
The current state of the power sequence. It can assume
one of the following values:
'running', 'paused', 'scheduled', 'scheduled paused',
'pending', 'inactive', 'completed' or 'invalid'.
saref:hasTime max 1 s4ener:ActiveDurationMax
The active maximum duration the power sequence can
run without interruption.
saref:hasTime max 1 s4ener:ActiveDurationMin The active minimum duration the power sequence can run
without interruption.
saref:hasTime max 1 The active maximum duration the power sequence can
s4ener:ActiveDurationSumMax run in total (summation of all active times).
saref:hasTime max 1 s4ener:ActiveDurationSumMin The active minimum duration the power sequence runs in
total (summation of all active times).
saref:hasTime min 1 s4ener:StartTime The start time of the power sequence. SHALL be present.
saref:hasTime max 1 s4ener:EarliestStartTime SHALL state the earliest possible start time for the whole
power sequence.
saref:hasTime max 1 s4ener:EndTime The end time of the power sequence. If the value is
available, it SHALL be denoted here. Otherwise the
element SHALL be omitted.
saref:hasTime max 1 s4ener:LatestEndTime The latest possible end time for the whole power
sequence.
saref:hasTime max 1 s4ener:ElapsedSlotTime If the power sequence state is set to 'running' or 'paused'
AND the slot is determined, this element CAN contain the
time the slot has already been in 'running' state (this also
means the value remains constant during a 'paused'
state). Otherwise it SHALL be omitted.
saref:hasTime max 1 s4ener:RemainingSlotTime If the power sequence state is set to 'running' or 'paused'
AND the slot is determined, this element SHALL contain
the time the slot still needs to be in 'running' state (this
also means the value remains constant during a 'paused'
state). Otherwise it SHALL be omitted.
saref:hasTime max 1 s4ener:PauseDurationMax
The maximum duration the power sequence can pause
after the end of an activity.
saref:hasTime max 1 s4ener:PauseDurationMin The minimum duration the power sequence can pause
after the end of an activity.

4.2.5 Slot
The s4ener:PowerSequence described in clause 4.2.4 consists of one or more slots (s4ener:Slot class) and,
inversely, a s4ener:Slot belongs to only and exactly one s4ener:PowerSequence. Figure 6 shows the
details of the s4ener:Slot class.
ETSI

---------------------- Page: 14 ----------------------
15 ETSI TS 103 410-1 V1.1.1 (2017-01)

Figure 6: Slot
Table 5 summarizes the properties that characterize a s4ener:Slot.
ETSI

---------------------- Page: 15 ----------------------
16 ETSI TS 103 410-1 V1.1.1 (2017-01)
Table 5: Properties of a Slot
Property Definition
s4ener:slotNumber exactly 1
A power sequence Id-wide unique slot identifier.
saref:hasDescription max 1 Textual description for the slot.
s4ener:optionalSlot max 1 It is set to TRUE if the slot can be omitted, otherwise the
element SHALL be omitted or set to FALSE. See note 1.
s4ener:slotActivated max 1
If the slot is optional, i.e. s4ener:optionalSlot is set to
TRUE, this element reflects the current status of the slot
(TRUE = the slot will be executed, FALSE = the slot will
not be executed). If the slot is not opt
...