This technical specification is for European electricity markets.

This document specifies a standard for a communication platform which every Transmission System Operator (TSO) in Europe may use to reliably and securely exchange documents for the energy market. Consequently a European market participant (trader, distribution utilities, etc.) could benefit from a single, common, harmonized and secure platform for message exchange with the different TSOs; thus reducing the cost of building different IT platforms to interface with all the parties involved. This also represents an important step in facilitating parties entering into markets other than their national ones.

From now on the acronym “MADES” (MArket Data ExchangeS) will be used to designate these Technical Specifications.

MADES is a specification for a decentralized common communication platform based on international IT protocol standards:

From a business application (BA) perspective, MADES specifies software interfaces to exchange electronic documents with other BAs. Such interfaces mainly provide means to send and receive documents using a so-called “MADES network”. Every step of the delivery process is acknowledged, and the sender can request about the delivery status of a document. This is done through acknowledgement, which are messages returned back to the sender. This makes MADES networks usable for exchanging documents in business processes requiring reliable delivery.
MADES also specifies all services for the business application (BA); the complexities of recipient localisation, recipient connection status, message routing and security are hidden from the connecting BA. MADES services include directory, authentication, encryption, signing, message tracking, message logging and temporary message storage.

The purpose of MADES is to create a data exchange standard comprised of standard protocols and utilizing IT best practices to create a mechanism for exchanging data over any TCP/IP communication network, in order to facilitate business to business information exchanges as described in IEC 62325-351 and the IEC 62325-451 series.

A MADES network acts as a post-office organization. The transported object is a “message” in which the sender document is securely repackaged in an envelope (i.e. a header) containing all the necessary information for tracking, transportation and delivery.

PDF Catalog

PDF Pages	PDF Title
4	CONTENTS
9	FOREWORD
11	INTRODUCTION
12	1 Scope 2 Normative references
13	3 Terms and definitions
14	4 High level concepts 4.1 What is MADES intended for? Figures Figure 1 – MADES overall view
15	4.2 General overview Figure 2 – MADES scope Figure 3 – MADES key features
16	4.3 Message delivery and transparency 4.3.1 Message delivery 4.3.2 Transparency Figure 4 – MADES message delivery overview
17	4.4 Security and reliability Figure 5 – MADES security and reliability
18	4.5 Main components Figure 6 – MADES components
19	4.6 Distributed architecture Figure 7 – MADES network distributed architecture
20	4.7 Components’ exposed interfaces 4.8 Security features 4.8.1 Overview Figure 8 – MADES interfaces and services
21	4.8.2 Transport-layer security Figure 9 – MADES transport security overview Figure 10 – MADES secure communication initiation
22	4.8.3 Message-level security Figure 11 – Message signature Figure 12 – Message encryption and decryption
23	4.8.4 Non repudiation Figure 13 – Non repudiation
24	5 Components’ functions 5.1 Routing messages Figure 14 – Delivery route of a business-message
25	5.2 Component and message unique identification (ID) 5.3 Business-type of a business-message 5.4 Delivery-status of a business-message
26	Figure 15 – Reported events during the delivery of a business-message
27	5.5 Communication between components 5.5.1 Principle 5.5.2 Establishing a secured communication channel between two components Tables Table 1 – Message delivery status
28	5.5.3 Token authentication of the client component 5.5.4 Request authorisation 5.5.5 Request/Reply validation
29	5.6 Storing messages in components 5.7 Lifecycle of a message state within a component
30	Figure 16 – Lifecycle of the local state of a business-message within a component Table 2 – Business message status
31	5.8 Transferring a message between two components (Handshake) Figure 17 – Transfer handshake when uploading of a message
32	5.9 Accepting a message Figure 18 – Transfer handshake when downloading of a message
33	5.10 Event management 5.10.1 Acknowledgements Table 3 – Accepting a message – Validation checks
34	5.10.2 Notifying events Figure 19 – Acknowledgements along the route of the business-message
35	Table 4 – Characteristics of notified events
36	5.10.3 Lifecycle of an acknowledgement 5.10.4 Processing a transferred acknowledgement Table 5 – Event characteristics description Table 6 – Acknowledgement state description
37	5.11 Message expiration 5.11.1 Principle 5.11.2 Setting the expiration time of a message: 5.11.3 Looking for the expired messages: 5.12 Checking the connectivity between two endpoints (Tracing-messages)
38	5.13 Ordering the messages (Priority) 5.14 Endpoint 5.14.1 Endpoint functions
39	5.14.2 Compression
40	5.14.3 Signing Table 7 – Compression – metadata attributes
41	5.14.4 Encryption Table 8 – Signing – metadata attributes
42	Figure 20 – Encryption process Table 9 – Encryption – metadata attributes
43	5.15 Node 5.15.1 Node functions 5.15.2 Synchronizing directory with other nodes
44	5.15.3 Updating the synchronization nodes’ list Figure 21 – A node synchronizes with two other nodes
45	5.16 Certificates and directory management 5.16.1 Definitions and principles
46	5.16.2 Certificates: Format and unique ID 5.16.3 Used certificates and issuers (CAs)
47	Figure 22 – Certificates and certificate authorities (CAs) for a MADES network
48	5.16.4 Directory services 5.16.5 Caching directory data
49	5.16.6 Trusting the certificates of others components 5.16.7 Renewing the expired certificates
50	5.16.8 Revoking a certificate Table 10 – Consequences of a certificate revocation
51	6 Managing the version of the MADES specification 6.1 Issues and principles 6.1.1 General 6.1.2 Rolling out a new version (Mversion and N-compliance) 6.1.3 Service compatibility
52	6.1.4 Message compatibility 6.1.5 Interface with BAs Table 11 – Service compatibility – Possible changes
53	6.2 Using the correct version for services and messages 6.2.1 Node synchronization and authentication Figure 23 – Managing the specification version – node synchronization and authentication
54	6.2.2 Directory services and Network acceptance Figure 24 – Managing the specification version – Directory services
55	6.2.3 Messaging services 6.2.4 Which version to use to send a message? Figure 25 – Managing the specification version – Messaging services
56	Figure 26 – Managing the specification version – Which version to use to send a message? Table 12 – Which version to use to send a message? Table 13 – Managing the specification version – Rejection conditions
57	7 Interfaces and services 7.1 Overview 7.1.1 General 7.1.2 Error Codes 7.1.3 Types for Time Table 14 – Interfaces and services – Generic error Table 15 – Interfaces and services – String value for errorCode
58	7.2 Endpoint interface 7.2.1 Overview 7.2.2 Services Table 16 – SendMessage – Service request elements
59	Table 17 – SendMessage – Service response elements Table 18 – SendMessage – Additional error elements Table 19 – ReceiveMessage – Service request elements Table 20 – ReceiveMessage – Service response elements
60	Table 21 – ReceiveMessage – Additional error elements Table 22 – CheckMessageStatus – Service request elements Table 23 – CheckMessageStatus – Service response elements Table 24 – CheckMessageStatus – Additional error elements
61	Table 25 – ConnectivityTest – Service request elements Table 26 – ConnectivityTest – Service response elements Table 27 – ConnectivityTest – Additional error elements Table 28 – ConfirmReceiveMessage – Service request elements Table 29 – ConfirmReceiveMessage – Service response elements
62	7.2.3 File System Shared Folders (FSSF) Table 30 – ConfirmReceiveMessage – Additional error elements
63	Table 31 – FSSF – Description and filename format Table 32 – FSSF – Filename description
64	7.3 Node interface 7.3.1 Overview
65	7.3.2 Authentication service Figure 27 – Node interface – Overview Figure 28 – Node interface – Authentication service
66	7.3.3 Messaging Services Table 33 – Authentication – Service request elements Table 34 – Authentication – Service response elements
67	Figure 29 – Node interface – Messaging services – UploadMessages service Table 35 – UploadMessages – Service request elements Table 36 – UploadMessages – Service response elements
68	Figure 30 – Node interface – Messaging services – DownloadMessages service Table 37 – DownloadMessages – Service request elements Table 38 – DownloadMessages – Service response elements
69	7.3.4 Directory services Figure 31 – Node interface – Messaging services – ConfirmDownload service Table 39 – ConfirmDownload – Service request elements Table 40 – ConfirmDownload – Service response elements
70	Figure 32 – Node interface – Directory services – GetCertificate service Table 41 – SetComponentMversion – Service request elements Table 42 – SetComponentMversion – Service response elements
71	Table 43 – GetCertificate – Service request elements Table 44 – GetCertificate – Service response elements Table 45 – GetCertificate – Additional conditions
72	7.3.5 Node Synchronization interface Figure 33 – Node interface – Directory services – GetComponent service Table 46 – GetComponent – Service request elements Table 47 – GetComponent – Service response elements Table 48 – GetNodeMversion – Service request elements
73	7.4 Format of the node-list file Table 49 – GetNodeMversion – Service response elements Table 50 – GetAllDirectoryData – Service request elements Table 51 – GetAllDirectoryData – Service response elements Table 52 – Node attributes ordered list
74	7.5 Typed Elements used by the interfaces Table 53 – AuthenticationToken Table 54 – Certificate Table 55 – CertificateType – string enumeration Table 56 – ComponentCertificate
75	Table 57 – ComponentDescription Table 58 – ComponentInformation Table 59 – ComponentType – string enumeration Table 60 – Endpoint
76	Table 61 – InternalMessage
77	Table 62 – InternalMessageType – string enumeration Table 63 – MessageMetadata Table 64 – MessageProcessor Table 65 – Map
78	Table 66 – MapEntry Table 67 – ValueType (enumeration) Table 68 – MessageState (string enumeration) Table 69 – MessageStatus
79	Table 70 – MessageTraceItem Table 71 – MessageTraceState (string enumeration) Table 72 – NotConfirmedMessageResponse
80	Table 73 – NotUploadedMessageResponse Table 74 – ReceivedMessage Table 75 – RoutingInformation Table 76 – SentMessage
81	7.6 Description of the services 7.6.1 About WSDL and SOAP 7.6.2 Endpoint interface Figure 34 – WSDL 1.1 definitions
88	7.6.3 Node interface
102	7.6.4 XML signature example

Published By	Publication Date	Number of Pages
BSI	2014	104


PDF Format	Searchable	Printable	Preview Now

Status	Withdrawn
Title	Framework for energy market communications – Market data exchanges guidelines for the IEC 62325-351 profile
Publisher	BSI
Committee	PEL/57
Pages	104
Publication Date	2014-02-28
Withdrawn Date	2018-11-13
Replaced By	BS EN IEC 62325-503:2018, BS EN 62325-451-2:2014
ISBN	978 0 580 81901 8
Standard Number	PD IEC/TS 62325-503:2014
Identical National Standard Of	IEC TS 62325-503:2014
Descriptors	Computer networks, Commerce, Information exchange, Electric power systems, Electric power distribution, Markup, Programming languages, Messages, Internet, Electricity, Electronic data interchange, EDIFACT
ICS Codes	33.200 - Telecontrol. Telemetering

BSI PD IEC/TS 62325-503:2014

PDF Catalog