230 likes | 497 Views
EDEX Platform Energy Data Exchange Platform Erik Wolfs. Who am I. Erik Wolfs Working as IT project leader for ELIA – Belgium TSO Convenor CWE MC IT group Convenor ENTSO-e MADES Workgroup Erik.wolfs@elia.be. Agenda - EDEX. Purpose Components Future development Questions.
E N D
EDEX PlatformEnergy Data Exchange Platform Erik Wolfs
Who am I Erik Wolfs Working as IT project leader for ELIA – Belgium TSO Convenor CWE MC IT group Convenor ENTSO-e MADES Workgroup Erik.wolfs@elia.be
Agenda - EDEX • Purpose • Components • Future development • Questions
Purpose - EDEX: • Forecast calculations become more and more important for modern TSO’s • Actual used methods are no more adequate for guaranteeing the security on future Electrical Grids • More dynamic and flexible studies needed • More (continuous) intraday dynamic calculations needed between D-1 and Real-time • More correct and continuously updated data needed during the complete forecasting cycle • Access to the correct data becomes critical • More and more platforms appear (TSC CTSS, 20’s, CWE CS, Entso-e PowerSystem DB…….)
Purpose - EDEX: • Standardization • EDEX wants to provide interface specifications basic functionality and best practices to the Energy world to : • Create a standardized platform to transmit ENTSO-e messages and process them : • CIM Messages • Market Messages • Any binary Message
EDEX: • Components • ECP : Energy Communication Platform • MADES compliant External communication platform • EPP : Energy Process Platform • Central Process handler and integrator • Client Toolbox • Decentralised process handler and local integrator
Components - communication MADES MADES (Market Data Exchange Standard) What for? • Harmonization of a communication software for the European electricity (or energy) market, including the following services: - guarantee of delivery - electronic signature - uniform method for data encryption • Defines the platform used for external communication
Components - ECP • ECP, (Energy Communication Platform), • Reference package for MADES standard • ECP was developed by CWE TSO’s • Transfer of the ownership of ECP to Entso-e on-going • Licenses for all TSO’s available • Already used by 13 TSO’s
Components – EPP Message Processing • EPP, (Energy Process Platform), • Based on Open Source Components (JBoss) • EPP was developed by CWE TSO’s for the MC CS • Availability of licenses for all TSO’s on-going • Uses a canonical model • ESB, Process Orchestrator, Message Validators • ECP integrated for external communication • Standardized interfaces for functional modules and data containers
Next Step : Client Toolbox • Message Validation (CIM, Market….) • Standardised Interfaces • Distributed calculations – so less need for model transfers • Can run as standalone system • Intelligent data gathering provided as a Service • Data Security and confidentiality : • On the Communication via ECP • Owner of data decides who has access • Local Data Storage for models with subscription service
And now: • Schedule • Questions ?