1 / 29

ADDRESS European Project Integration of Active Demand

ADDRESS European Project Integration of Active Demand. Eric Lambert, Cyril Effantin, EDF R&D UCA CIMUg Prague May 2011. CIM usage, one year after. Active Distribution network with full integration of Demand and distributed energy RESourceS. Agenda. Introduction

fergus
Download Presentation

ADDRESS European Project Integration of Active Demand

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ADDRESS European ProjectIntegration of Active Demand Eric Lambert, Cyril Effantin, EDF R&D UCA CIMUg Prague May 2011 CIM usage, one year after Active Distribution network with full integration of Demand and distributed energy RESourceS

  2. Agenda Introduction Methodological working framework for Interoperable information exchanges Results Role Model Use Cases Modeling CIM-ADDRESS Information Model CIM-ADDRESS XML Messages Prototype testing interoperability through SOA + IEC61968-1-2 standards Conclusion and next steps

  3. ADDRESS : what is it ?

  4. ADDRESS : Some results Some results from the ADDRESS European project: • Deliver a technical and commercial framework for the development of Active Demand and for the market-based exploitation of its benefits • Active Demand: active participation of domestic and small commercial consumersin system markets and the provision of services to the different participants • Architecture based on the concept of Demand flexibility aggregation OUR MISSION : Promote Standards, Method and Tools to insure interoperability Keep It Simple ! 4

  5. Promoting and using standards in ADDRESS • TC8 PAS 62559 • UML notation • UML « Role Model » • Message Payload : Common Information modelPromote CIM profiles (61970-452/456, 61968-13) • Methodology & Tools ExpressingtheWHAT HOWExpressingthe WHAT ?

  6. Expressing the WHAT ? ADDRESS PROCESS ARCHITECTURE DIAGRAM

  7. Methodological working framework From Use Cases down to message modeling Leveraging interoperability in communication between ADDRESS components

  8. AD Product/service description: power delivery charac. “use cases” approach for the 31 AD services One Business Example before to start Standardized AD products

  9. AD PRODUCT ΔCdecrease (MW) ΔCdecrease (MW) PayBack Effect Aggregated Curves t PayBack Effect (MW) ΔCdecrease (MW) t C decrease PayBack Effect t t C increase C decrease C increase : ex: shift of consumption

  10. Methodology to leverage interoperability in ADDRESS message exchanges Centralized Producer Retailer TSO DSO Message Service Bus : Single Common Semantic for Message Payload IEC CIM … Market Aggregator Energy Box Interface for external data interchanges Internal Applications

  11. ADDRESS Actor Interface for external data interchanges Internal Applications 11

  12. Interoperability based on SOA integration Message Service Bus Message Payloads XSD ADDRESS Actor Encapsulation in services WSDL API Automated Generation Contract First Plugged Into ESB

  13. Modeling Methodological Framework : 5 Steps UML Use CaseDefinitions WP1,WP2,WP3, WP5 Use CaseDefinition (text) 1 2a 2b 3 Find Business Objectsin CIM model orextend CIM T4.4 UML needs for Message Payload Definition from WP1, WP2,WP3,WP5 IEC WG14 Verb + payload Define Message Payloads from CIM-ADDRESS 4 Generate XML XSD 5 CIM-ADDRESS UML Information Model WP4 T4.4 responsible for 3,4,5

  14. Results From Use Cases down to Message Modeling Models UML Role Model UML Use Cases definition based on IEC TC57 WG14 conventions CIM-ADDRESS UML information Model XML messages definition for the use cases information exchanges Demonstrating Interoperability Prototype leveraging SOA + IEC61968-1-2 standards

  15. ADDRESS Actors glossary

  16. 5 Reusable Core Use Cases

  17. Configure Load Areas

  18. Configure Load Areas

  19. Clear Active Demand Market

  20. Designing common XML structures : CIM Message Types

  21. Overview of the CIM-ADDRESS Information Model

  22. Building XML schemas (XSD) for ADDRESS Messages Types UML CIM-ADDRESS Information Model XSD for messages types CIMTool Project

  23. Prototype testing interoperability through SOA + IEC61968-1-2 standards Actor1 Axis OpenESB Actor2 AXIS XML IEC61968-1-2 IEC61968-1-2 IEC61968-1-2 Business Service Orchestration BPEL WebService Interface

  24. Conclusion Feedback from the regulated package [JOSEBA JIMENO (TECHNALIA)] Towards Field Tests… Final word

  25. CIM used for ADDRESS regulated players (TSO, DSO) • CIM models have been used as input and outputs for: • State Estimation • Validation of AD products • Load area definition • Generation forecasting • Etc.For the State Estimator the following information has been modeled: • Equipment at MV level: ACLineSegment, PowerTransformer, SynchronousMachine, ComformLoad etc. • Equipment at LV level: Combination of real equipment as in the MV level and equivalents (EquivalentBranch, EquivalentNetwork, etc.) • Topology for MV and LV using ConnectivityNode and TopologicalNode • Generation forecasts: An extension to CIM has been used as provided by ABB (QuantityAxis, QuantityData etc) • Measurements: Analog, AnalogValue, Quality etc. • Network state: SvVoltage, SvInjection, SvPowerFlow

  26. Use of CIM for the regulated ADDRESS actors • Advantages of using CIM • It is a very complete model providing support for many different applications (from SE to AD validation) • UML modeling and the use of CIMTool are very useful • Issues found • CIM allows multiple ways of modeling the same thing. This brings the need to agree between the different developers about common profiles • The model is quite complex and it takes some time to learn it • The need of XML parsing and RDF navigation can be resource consuming

  27. How to Implement the WHAT ? Simulation platform + Field Tests Adapter API API API Adapter Adapter • Stakes • Minimize Gaps • Minimize iterative loops • Field tests requirements Field Test =integration with some real application Centralized Producer TSO DSO Retailer Adapter Adapter Adapter API API API Message Bus : CIM-Address Messages API API Adapter Adapter Aggregator market … Energy Box

  28. Final Word ! • Use Case MANAGEMENT is essential : UC LIFE CYCLE • We have to distinguish between • What is/can be done at IEC level • What is/can be done during interoperability tests conducted by Users Associations • What is/can be done during a EUROPEAN PROJECT with Field test • ADDRESS is the first European FP7 project using CIM

  29. Thanks for your attention Questions ?

More Related