EN 50631-1:2017

Household appliances network and grid connectivity - Part 1: General Requirements, Generic Data Modelling and Neutral Messages

This document defines data models for Interoperable Connected Household Appliances. The data model is derived from a logical decomposition of use cases into functional blocks that themselves are realized by abstract actions on the data model itself.

Netzwerk- und Stromnetz-Konnektivität von Haushaltsgeräten - Teil 1: Allgemeine Anforderungen, allgemeine Datenmodellierung und neutrale Meldungen

Appareils domestiques connectés au réseau et réseau intelligent - Partie 1: Exigences générales, modélisation de données génériques et messages neutres génériques

Omrežje gospodinjskih aparatov in povezljivost mreže - 1. del: Splošne zahteve, modeliranje rodovnih podatkov in nevtralna sporočila

Ta dokument določa podatkovne modele za interoperabilne povezane gospodinjske aparate. Podatkovni model izhaja iz logične razdelitve primerov uporabe v funkcionalne bloke, realizirane na podlagi abstraktnih ukrepov na samem podatkovnem modelu.

General Information

• Status: Published
• Publication Date: 07-Dec-2017
• Withdrawal Date: 17-Sep-2020
• ICS: 97.120 - Automatic controls for household use
• Technical Committee: CLC/TC 59X - Consumer information related to household electrical appliances
• Drafting Committee: CLC/TC 59X - Consumer information related to household electrical appliances
• Current Stage: 6060 - Document made available - Publishing
• Start Date: 08-Dec-2017
• Due Date: 08-Nov-2017
• Completion Date: 08-Dec-2017
• Mandate: M/490 - Standardisation mandate to the European Standardisation Organisations (ESOs) to support European Smart Grid deployment
• Mandate: M/495 - Standardisation mandate to CEN, CENELEC and ETSI under Directive 2009/125/EC relating to harmonised standards in the field of Ecodesign
• Ref Project: SIST EN 50631-1:2018 - Household appliances network and grid connectivity - Part 1: General Requirements, Generic Data Modelling and Neutral Messages

Relations

• Replaced By: EN 50631-1:2023 - Household appliances network and grid connectivity - Part 1: General requirements, generic data modelling and neutral messages
• Effective Date: 08-Sep-2020

Overview

EN 50631-1:2017 - Household appliances network and grid connectivity, Part 1 - defines general requirements, generic data modelling and neutral messages for interoperable connected household appliances. The standard specifies a logical data model derived from decomposing real-world use cases into functional blocks, realized by abstract actions on that data model. It establishes the foundation for device interoperability, communication semantics and the SPINE (Smart Premises INteroperability Environment) data/protocol constructs used to exchange neutral messages between appliances, controllers and energy systems.

Key topics and technical requirements

• Generic data modelling: A SPINE-based device/resource model and feature types to represent appliances, measurements, setpoints and schedules.
• Neutral messaging: Message formats and payload organization for device control, monitoring and notifications that are independent of transport layers.
• SPINE Protocol & Datagram: Structure, headers and payload conventions for consistent message exchange and communication modes (simple/enhanced).
• Use cases & user stories: Demand Response (DR), Demand Side Management (DSM), emergency blackout prevention, remote control/monitoring, flexible start and direct load control.
• Requirements & common functions: Registration/deregistration, fallback/autonomous operation, planning automated starts, immediate control, configuration modification, emergency control and notification.
• Mappings and resource definitions: Mapping of use cases to SPINE data model; comprehensive resource and class definitions (ActuatorSwitch, LoadControl, Measurement, TaskManagement, etc.).
• Functional commissioning: Discovery, destination lists, binding, subscription and device lifecycle management.
• Interoperability process: Top-down design approach, conceptual architecture and registration/commissioning processes to enable multi-vendor ecosystems.

Practical applications and who uses this standard

EN 50631-1:2017 is intended for:

• Appliance manufacturers designing smart, grid-aware household devices (washing machines, HVAC, water heaters).
• Smart home & energy platform developers implementing neutral message handling and SPINE data mappings.
• Energy providers and DSOs enabling Demand Response and DSM programs through interoperable device control.
• System integrators and installers performing functional commissioning and lifecycle management.
• Standards bodies and test labs validating interoperability and compliance.

Typical applications include automated load shifting (flexible start), coordinated direct load control, remote monitoring and firmware-independent messaging for grid services and emergency management.

Related standards

• This document is the Part 1 specification of the EN 50631 series (published as EN 50631-1:2017) and complements other parts that cover transport profiles, security and certification. Implementers should consult additional EN 50631 parts and national implementations for complete compliance and deployment guidance.

Keywords: EN 50631-1:2017, household appliances network, grid connectivity, SPINE data model, neutral messages, interoperability, demand response, DSM, smart appliances.

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Household appliances network and grid connectivity - Part 1: General Requirements, Generic Data Modelling and Neutral Messages97.030VSORãQRDomestic electrical appliances in generalICS:Ta slovenski standard je istoveten z:EN 50631-1:2017SIST EN 50631-1:2018en01-februar-2018SIST EN 50631-1:2018SLOVENSKI
STANDARD
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 50631-1
December 2017 ICS 97.120
English Version
Household appliances network and grid connectivity - Part 1: General Requirements, Generic Data Modelling and Neutral Messages
Appareils domestiques connectés au réseau et réseau intelligent - Partie 1: Exigences générales, modélisation de données génériques et messages neutres génériques
Netzwerk- und Stromnetz-Konnektivität von Haushaltsgeräten - Teil 1: Allgemeine Anforderungen, allgemeine Datenmodellierung und neutrale Meldungen This European Standard was approved by CENELEC on 2017-09-18. CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions. CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique Europäisches Komitee für Elektrotechnische Normung CEN-CENELEC Management Centre: Rue de la Science 23,
B-1040 Brussels © 2017 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 50631-1:2017 E SIST EN 50631-1:2018

2 Contents Page European foreword . 6 Introduction . 7 1 Scope . 8 2 Normative references . 8 3 Terms, definitions and abbreviations . 8 4 Process & Requirements to enable interoperability . 14 4.1 Introduction . 14 4.2 Conceptual Architecture Model . 15 4.3 Top Down Approach . 17 4.4 Process . 18 5 User Stories and Use Cases . 19 5.1 Introduction . 19 5.2 User Stories . 20 5.2.1 Demand Response (DR) . 20 5.2.2 Demand Side Management (DSM), see “EURELECTRIC Views on Demand-Side Participation” [5] . 21 5.2.3 Emergency Blackout Prevention (see [2]) . 22 5.2.4 Remote Control of a Smart Appliance (see [3]) . 22 5.2.5 Remote Monitoring of a Smart Appliance (see [3]) . 23 5.2.6 Manual Operation of a Smart Appliance (see [3]) . 23 5.3 Derived use cases. 23 5.3.1 Introduction . 23 5.3.2 Actors . 24 5.3.3 Main level of Smart Appliances use cases . 24 5.3.4 Flexible Start . 25 5.3.5 Direct Load Control . 34 5.3.6 Emergency Blackout Prevention . 38 5.3.7 Remote Programming . 41 5.3.8 Remote Monitoring . 44 5.3.9 Manual Operation. 48 5.3.10 Install Smart Appliance . 50 5.3.11 Remove Smart Appliance . 52 6 Requirements & Common Function Descriptions . 54 6.1 Introduction . 54 6.2 Requirements . 54 6.2.1 JWG-R100 – Provide fallback mechanism of Smart Device to regular device (autonomous operation) if no CCM is available . 54 6.2.2 JWG-R101 – Safety relevant requirements . 54 6.3 Common Function Descriptions . 54 6.3.1 JWG-F100/101 – Register / De-Register Smart Appliance with available options . 54 6.3.2 JWG-F102 – Provide alternatives on power profiles with available optimization targets, Notify about pending job(s) that were initiated by Smart Aplliance and/or the end-customer . 57 6.3.3 JWG-F103 – Plan automated start in advance . 58 6.3.4 JWG-F104 – Query and show information as well as status and/or status change of a Smart Appliance. 60 6.3.5 JWG-F105 – Immediately control device (no emergency case) . 62 6.3.6 JWG-F106 – Modify configuration of Smart Device during runtime to increase/decrease power consumption . 63 SIST EN 50631-1:2018

4 10.5.5 LoadControl . 253 10.5.6 Measurement . 258 10.5.7 Messaging . 267 10.5.8 NetworkManagement . 271 10.5.9 OperatingConstraints . 296 10.5.10 PowerSequences . 305 10.5.11 Sensing . 332 10.5.12 Setpoint . 336 10.5.13 SubscriptionManagement . 343 10.5.14 TaskManagement . 348 10.5.15 Threshold . 354 10.5.16 TimeInformation . 359 10.5.17 TimeTable . 365 10.5.18 Version . 372 Annex A (normative)
XSDs in alphabetic order . 375 A.1 SPINE_TS_ActuatorSwitch . 375 A.2 SPINE_TS_BindingManagement . 375 A.3 SPINE_TS_CommandCommonDefinitions . 377 A.4 SPINE_TS_CommandFrame . 380 A.5 SPINE_TS_CommonDataTypes . 381 A.6 SPINE_TS_Datagram . 392 A.7 SPINE_TS_DeviceClassification . 392 A.8 SPINE_TS_DirectControl . 393 A.9 SPINE_TS_LoadControl . 394 A.10 SPINE_TS_Measurement . 396 A.11 SPINE_TS_Messaging . 399 A.12 SPINE_TS_NetworkManagement . 400 A.13 SPINE_TS_NodeManagement . 405 A.14 SPINE_TS_OperatingConstraints . 413 A.15 SPINE_TS_PowerSequences . 416 A.16 SPINE_TS_Result. 423 A.17 SPINE_TS_Sensing. 423 A.18 SPINE_TS_Setpoint . 425 A.19 SPINE_TS_SmartEnergyManagementPs . 427 A.20 SPINE_TS_SpecificDeviceEntityDefinitions . 436 A.21 SPINE_TS_SubscriptionManagement . 437 A.22 SPINE_TS_TaskManagement . 438 A.23 SPINE_TS_Threshold . 440 A.24 SPINE_TS_TimeInformation . 442 A.25 SPINE_TS_TimeTable . 443 A.26 SPINE_TS_Version . 445 Annex B (informative)
Examples and supplementary overviews . 446 B.1 PowerSequence Example . 446 B.1.1 101 read nodeManagementDetailedDiscoveryData . 447 B.1.2 102 reply nodeManagementDetailedDiscoveryData . 448 B.1.3 301 call nodeManagementSubscriptionRequestCall . 449 B.1.4 302/306 reply resultData . 450 B.1.5 303 read smartEnergyManagementPsData . 450 B.1.6 304 reply smartEnergyManagementPsData . 450 B.1.7 305 call nodeManagementBindingRequestCall . 451 B.1.8 308 write partial smartEnergyManagementPsData startTime . 452 B.1.9 309 notify partial smartEnergyManagementPsData scheduled . 452 B.1.10 310 notify partial smartEnergyManagementPsData running . 453 B.1.11 311 notify partial smartEnergyManagementPsData completed . 454 B.2 Identifier list . 455 B.3 Examples of enhanced communication mode and DestinationList . 456 B.3.1 Introduction . 456 B.3.2 “Interfaces” and “internal routing” . 456 SIST EN 50631-1:2018

6 European foreword This document (EN 50631-1:2017) has been prepared by the WG 7 "Smart Household Appliances" of CLC/TC 59X "Performance of household and similar electrical appliances". The following dates are fixed: • latest date by which this document has to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2018-09-18 • latest date by which the national standards conflicting with this document have to be withdrawn (dow) 2020-09-18
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CENELEC shall not be held responsible for identifying any or all such patent rights. This document has been prepared under a mandate given to CENELEC by the European Commission and the European Free Trade Association. SIST EN 50631-1:2018

8 1 Scope This document defines data models for Interoperable Connected Household Appliances. The data model is derived from a logical decomposition of use cases into functional blocks that themselves are realized by abstract actions on the data model itself. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. EN 60335 (all parts), Household and similar electrical appliances – Safety RFC 2119, Key words for use in RFCs to Indicate Requirement Levels, March 1997 3 Terms, definitions and abbreviations For the purposes of this document, the following terms and definitions apply. 3.1
appliance electrical apparatus intended for household or similar use Examples: Refrigerators, dishwashers, clothes washers, clothes dryers, air conditioners, water heaters, circulation pumps etc.
3.2
binding concept for connecting functionally matching features 3.3
(standard or complex) class
set of SPINE functions used to describe a specific functionality. A class can be considered as a topic where functions are defined for. For example the SPINE class “Measurement” is a collection of SPINE functions that are used to describe measurement values 3.4
classifier specifies whether a message serves to read, reply, write, etc. 3.5
client role that specifies that a node uses data from a "server" or can request for change 3.6
command functional part of a Message 3.7
complex class SPINE class that is built up by parts of SPINE standard classes and combines them in a new, ordered way 3.8
Customer Connectivtiy Manager (CCM), see also 4.2 component or set of functions with the capability to: 1) Receive and process Grid Information, Appliance Information and User Instructions, and SIST EN 50631-1:2018

data model definition of possible data (data structures, values) for the exchange of information (especially for communications systems) 3.10
Demand Response (DR) “EURELECTRIC Views on Demand-Side Participation” [5] Demand Response (DR) implies a ‘bottom-up’ approach: the customer becomes active in managing his/her consumption – in order to achieve efficiency gains and by this means monetary/economic benefits. Demand Response (DR) can be defined as “the changes in electric usage by end-use customers from their normal consumption patterns in response to changes in the price of electricity over time. Further, DR can be also defined as the incentive payments designed to induce lower electricity use at times of high wholesale market prices or when system reliability is jeopardized. DR includes all intentional modifications to consumption patterns of electricity of end use customers that are intended to alter the timing, level of instantaneous demand, or the total electricity consumption”. DR aims to reduce electricity consumption in times of high energy cost or network constraints by allowing customers to respond to price or quantity signals 3.11
Demand Side Management (DSM), see “EURELECTRIC Views on Demand-Side Participation” [5] Demand Side Management (DSM) or Load Management has been used in the (mainly still vertically integrated as opposed to unbundled) power industry over the last thirty years with the aim “to reduce energy consumption and improve overall electricity usage efficiency through the implementation of policies and methods that control electricity demand. Demand Side Management (DSM) is usually a task for power companies / utilities to reduce or remove peak load, hence defer the installations of new capacities and distribution facilities. The commonly used methods by utilities for demand side management are: combination of high efficiency generation units, peak-load shaving, load shifting, and operating practices facilitating efficient usage of electricity, etc.” Demand Side Management (DSM) is therefore characterized by a ‘top-down’ approach: the utility decides to implement measures on the demand side to increase its efficiency 3.12
device (specific node) SPINE node that can include a set of entities. It has a “deviceType”. With regards to the hierarchy of SPINE nodes a device is a root node for all functionalities offered by a device 3.13
“device” (address information) SPINE address part for the (physical) device 3.14
Device Connectivity Manager (DCM), see also 4.2 component or set of functions with the capability to: 1) Receive and process information from a CCM, 2) Manage one appliance. Note 1 to entry: A DCM may be integrated with an Appliance or be physically separate. SIST EN 50631-1:2018

10 Note 2 to entry: A DCM enables an Appliance to become a Smart Appliance. It enables communication with a CCM. Thus, DCM and Appliance manage the behaviour of a Smart Appliance.
3.15
devicetype specific type of physical device (e.g. "WashingMachine", "HeatPump", "FridgeFreezer", etc.) 3.16
discovery process of finding appropriate partners for communication. Dependent on the context this can be either finding other devices or examination of a device’s potential functionalities 3.17
element item (or “attribute”) of a SPINE function. Holds one information (e.g. "timestamp", "value", etc.) or contains further sub-elements 3.18
entity (specific node) SPINE node that can include a set of (sub-)entities or features. It has an “entityType”. With regards to the hierarchy of SPINE nodes an entity is a sub-element of a device 3.19
“entity” (address information) SPINE address part for the (logical) entity 3.20
EntityType specific type of logical device (e.g. "Freezer" is one logical part of a physical device "FridgeFreezer") 3.21
feature (specific node) SPINE node that can include a set of functions (of a class). It has a “featureType”. With regards to the hierarchy of SPINE nodes a feature is a sub-element (i.e. “child”) of an entity 3.22
“feature” (address information) SPINE address part for one feature 3.23
FeatureType defines optional or mandatory rules and a general behaviour of the underlying Class (standard or complex) 3.24
function smallest structure to model “actual data” (“functional data”). I.e. functions usually consist of child elements that each hold an information (e.g. "timestamp", "value", etc.). Information between communication partners is exchanged via the exchange of a function (as part of a so-called “payload”) 3.25
header SPINE Header, including elements for addressing, unique identification of messages, timestamp, etc 3.26
grid information information received by a CCM directly from or relating to the electricity grid Note 1 to entry: Such information may include (but is not restricted to) the following categories: SIST EN 50631-1:2018

JWG (Joint Working Group) Joint working Group Use Cases & Requirements is a working group under the roof of IEC TC57 WG21. It is a cross functional working group and develops Smart Grid and Smart Home&Building related user stories and use cases. See IEC TR 62746-2:2015 Use cases & requirements [2] 3.28
manual operation operation of a Device under direct user control Note 1 to entry: Includes operation under the influence of remote controls provided with the appliance or device. Note 2 to entry: A Smart Device may default to Normal User Operation if the DCM is inactive, deactivated or removed. 3.29
manual over-ride return to Normal User Operation that terminates or prevents a period of Smart Operation, that is initiated by the User 3.30
message one SPINE transfer from a sender to a receiver 3.31
(XML) namespace XML namespaces provide a simple method for qualifying element and attribute names used in XML documents by associating them with namespaces identified by URI references (source: www.w3.org) 3.32
neutral message information exchange that is independent of any specific communication solution. Part 4 (EN 50631-4) describes the mapping of neutral messages to examples of typical communication protocols 3.33
node common term for a SPINE instance that has a SPINE address. Dependent on the situation a node can be either a device or an entity (of a specific device) or a feature (of a specific device-entity) 3.34
payload SPINE Payload, containing the functional SPINE data 3.35
power profile any combination of one or more Power sequences over a specified time SIST EN 50631-1:2018

12 3.36
power sequence one or more Power slots of one entity. The power slots are executed in sequence. A power sequence reflects typically the power behaviour of an entity’s process or program (e.g. washing program) 3.37
power slot single step of a Power sequence. Each power slot is modelled with at least one constant power value for its duration 3.38
role each Feature has a functional role, usually either “server” (data owner) or “client”. For some special features (NodeManagement, e.g.) the role “special” is defined 3.39
scope (Type) some feature types define scope types for identifying specific functionalities unambiguously (e.g. outsideAirTemperature) 3.40
server role that specifies that a node offers own data to be read or written by a node with role client. A server can notify its data to other nodes (with role client) 3.41
smart appliance appliance that: 1) incorporates or has been equipped with a DCM; and 2) is capable of Smart Operation. Notwithstanding the possibly broader concept related to the term “smart appliance”, a smart appliance under the framework of this standard needs to be understood as follows: 1) It is an appliance that is able to respond to an external stimulus initiated by a CCM and/or Remote Agent to provide activities amongst others like a. energy related demand response (supporting flexibility) or demand side management (adaptation of load) b. job status related functions like starting, stopping, pausing, c. content or level related functions like temperature, doorstatus, 2) The appliance will respond when user set conditions, and its status allow for a response, 3) The response is a change of the appliance’s behavior like electricity consumption, job status and/or level or content pattern or a notification of, 4) The specific technical smart capabilities do not need to be activated when the product is placed on the market; the activation can be done at a later point of time by the consumer or a service provider. Smart appliances in this context are able to communicate through a Customer Connectivity Manager (CCM) function processing external signals such as price information or Renewable Energy Sources availability (demand response) or direct control signals (demand side management), being able to take into account households’ preferences or the behavior of the other home appliances. SIST EN 50631-1:2018

smart operation operation of an Appliance where the CCM or DCM has been set to modify operation automatically in response to Trigger Criteria Note 1 to entry: Smart operation may be initiated by a CCM or a DCM. The trigger criteria for Smart Operation. 3.43
SpecificUsage Specific usage of a functionality defined by a FeatureType (for example for a FeatureType “Measurement” the specific usage could be “Temperature”) 3.44
SPINE Smart Premises Interoperable Neutral-message Exchange 3.45
SPINE Data Model SPINE Data Model describes the concepts and data model to ensure information exchange between devices like Smart Appliance and CCM, comprising 1) SPINE Protocol, defining a neutral message structure and neutral message exchange 2) SPINE Feature Types, describing the specific information to be exchanged 3.46
Standard Class all basic/standard functions are defined in standard classes. Functions of standard classes follow very simple patterns and do not have deeply nested data structures 3.47
subscription enables the receiving of messages of interest from another device without polling it 3.48
Use case textual description of a re-usable functionality consisting of one or more messages of one or more participating actors. May be visualized with a sequence diagram. E.g. "A CCM shifts the energy usage of a washing machine." 3.49
Use Case Functions Use Case Functions group basic functionalities that had been derived from use cases. These functions provide the entire information exchange required to implement the considered use cases and user stories 3.50
User story complete (but specific) business case described from the perspective of a user. Can be separated into several use cases. E.g. "The user wants to get the laundry done by 8:00pm." SIST EN 50631-1:2018

14 3.51
XML (Extensible Markup Language) Extensible Markup Language (XML) is a simple, very flexible text format derived from SGML (ISO 8879). See [16]. Extensible Mark-up Language (XML) defines a set of rules for encoding documents
...