Presentation is loading. Please wait.

Presentation is loading. Please wait.

Cigre WG D2.24 EMS Architectures of the 21 st Century Vasteras 2008 Alain P. STEVEN PJM Interconnection, LLC, USA CIGRE WG D2.24 Convenor Jay BRITTON AREVA.

Similar presentations


Presentation on theme: "Cigre WG D2.24 EMS Architectures of the 21 st Century Vasteras 2008 Alain P. STEVEN PJM Interconnection, LLC, USA CIGRE WG D2.24 Convenor Jay BRITTON AREVA."— Presentation transcript:

1 Cigre WG D2.24 EMS Architectures of the 21 st Century Vasteras 2008 Alain P. STEVEN PJM Interconnection, LLC, USA CIGRE WG D2.24 Convenor Jay BRITTON AREVA T&D, USA TC57, CIM expert Thierry LEFEBVRE RTE, France TC57 chairman

2 WG D2.24 Outline  Part 1: o Overview, goals o Relationships with IEC- TC57  (Thierry Lefebvre)  Part 2 : o CIM in CIGRE D2.24 o Focus on the « Information Architecture »  (Jay Britton)

3 WG D2.24 Several organizations sharing the same goal  Cigré o International Council on Large Electric Systems o Facilitates, develops and synthesizes technical knowledge in all the fields related to HV generation and transmission o Based in Paris, 80 member countries  VLPGO o Very Large Power Grid Operators o International initiative regrouping the world’s twelve largest grid operators o Focus is on addressing challenges unique to the operation of very large power grids (> 50,000 MW)  IEC o International Electrotechnical Commission o Prepares and publishes International Standards for all electrical, electronic and related technologies  IRC/ITC o IRC = North American ISO/RTO Council (CEO level) o ITC = Information Technology Committee, reports to IRC (CIO level)

4 WG D2.24 (Cont’d)  10/03: First meeting of the VLPGO o CEO level o Creation of WG #2 - EMS Architectures of the 21 st Century  01/06: IRC/ITC launches EAS project o EAS = Enterprise Architecture Standardization o Complementary to the work of WG #2  01/07: VLPGO WG #2 becomes Cigré WG D2.24 o Expands membership to the rest of the industry o Formalizes the work of WG #2 and provides a formal communication channel with IEC  06/07: EAS project merges with Cigré WG D2.24 o Provides a consistent description of the architecture, from the high level requirements down to the detailed message definitions

5 WG D2.24 Mission & Scope  Mission  Develop the vision for the architecture of the next generation of Energy Management and Market Management Systems,  Gain broad adoption by the industry  Facilitate its implementation as a de facto standard  Scope  Real-time Systems associated with the transmission and market operations  Extendable to generation and distribution

6 WG D2.24 Goals and Objectives  Goal: to develop the vision for a highly interoperable and reusable architecture, and to facilitate its implementation through a common coordinated procurement process  Objectives o Develop a common set of requirements o Develop a description of the architecture and its standard components o Facilitate its implementation and its funding through a coordinated procurement process along with a roadmap agreed upon between end users and manufacturers

7 WG D2.24 Membership  End Users o British Columbia TC o California ISO* o Cemig (Brazil) o Duke Energy o EPRI o ERCOT o Fingrid Oyj o Hydro-Quebec o Israel Electric Coorporation o ISO/RTO Council o KPX (Korea)* o Midwest ISO* o National Grid Company* o ONS (Brazil)* o PJM Interconnection* o Power Grid Corporation of India* o Red Electrica Espana* o RTE (France)* o SO-CDO for UES of Russia* o State Grid Corporation of China* o Statnett SF o Swedish Center of Excellence o Tepco (Japan)* o Terna (Italy)* o Transba SA (Argentina) o Transpower (NZ)  System Suppliers o ABB o Areva T&D o GE o Siemens  Application Suppliers o PowerWorld  Consultants o Grid Engineering o Kema  Academic o Texas A&M * VLPGO Member

8 WG D2.24 WG-2 Initial Findings  Common Issues o High development and maintenance/support costs o Lack of modularity and interoperability among multiple vendors o Limited innovation o Limited number of viable vendors o Inadequate security o Multiplicity of user interfaces  Perceived Root Causes o Limited standardization (Market requirements as well as vendor products) o Limited market(s) size o Real-time performance imperatives o High investment in legacy products o Limited software reuseability

9 WG D2.24 Design Principles  Component based, Services Oriented Architecture for integration and reusability within the Enterprise  Modularity based on businesses processes componentization  High Speed Bus for real-time message exchange  Common Information Model for data standards  Security layer  Built on industry standards  Common User Interface  Common Modeling tools integrating display and data maintenance  Transportable to future technologies  Scalable

10 WG D2.24 Common User Interface Operate the Grid - Monitor Operations - Forecast demand - Schedule supply - Control generation - Control transmission Operate the Market - Develop real-time markets - Develop day-ahead markets - Settle the market - Monitor the market Plan the Assets - Determine capacity adequacy - Approve generation citing - Plan transmission expansion - Plan generation capacity Orchestration Engine and Work Flow Optimization engines MIPS engine PRA Optimization Clearing engine IAP SE DPF Event correlation Rules engine LMP calc Lagrangian engine Substation SCADA Event processing Data acquisition FTR Engine Auction clearing Pattern recognition Intelligent agents ARR engine Visualization Operating system services Database services High-availability services Portal Platform monitoring services User interface components Historical logging components Standard data model [CIM] Rules engine components DW/ODS Security services Application monitoring services Logging services Time management services Diagnostics services High-speed integration services Enterprise integration services Data access services Exception management services Model maintenance services Common name service Data synchronization services Enterprise integration services Failover/ redundancy services Repository services Technical Services Business Services Core Business Processes

11 WG D2.24 Future State Road Map Common Business Services Legacy Applications Core Business Processes Common Technology Services 20XX

12 WG D2.24 Enterprise Integration Services Data Analysis & Presentation Interface SCADA Systems SCADA Interface EMS Advanced Applications Advanced Apps Interface SCUC/SCED Outage Scheduler SCUC Interface I n t e r n e t Local OASIS Data OASIS Interface Data Mart Market Monitor CIM Rules Engine Intelligent Logging Portal Services Common Name Service Standard Data Model Optimization Engines Integration Services Orchestration and Workflow Interface HIS Business Intelligence Interface Data Mining and Analysis Web Services Security Services Visualization Components Model Maintenance Services Network Applications Network Apps Interface Customer Relationship Management CRM Interface Ancillary Markets Interface Day Ahead Real Time FTR Markets Interface Market Settlements Interface Intelligent Alarms Processes IAP Interface “High Speed System Bus” Future State Conceptual SOA Model Shared Services

13 WG D2.24 Business Domain Architecture

14 WG D Application and Integration Architecture 2. Information Architecture 3. Security Architecture 4. Platform Architecture 5. Network Architecture 6. Business Continuity Architecture 7. User Interface Architecture Seven Layers for a reference architecture

15 WG D2.24 Harmonization Process VLPGO WG-2 New Members RTO/ISO EAS Project WG 24 Cigre SC D2 RTO/ISO (IRC) IT Council VLPGO

16 WG D2.24 Detailed Services and Messages Definitions (EAS/TF 5) Standard Business Services (TF 3b) Standard Technology Services (TF 4) CRD TF 1/2 Generic Business Processes (TF 3a) High Level Architecture Requirements and Applicable Standards (07/08) Defines Application Modularity and Granularity (07/08) High Level Services Definitions and Interfaces (12/08) Cigre WG D2.24 Task Forces & Deliverables

17 WG D2.24

18 Industry Coordination Standard Committees/Initiatives  WG D2.24 sets the vision and requirements, not the standards  Objectives o Align with current and emerging standards, and leverage work done o Produce a complete and consistent specification of the architecture  Coordination with o IEC TC-57 related working groups (mainly CIM) o North American ISO/RTO Council EAS Project

19 WG D2.24 IEC-CIGRE Relationships 1. Liaison type A between CIGRE D2 and IEC TC57 IEC Category A liaison for Organizations that make an effective contribution to the work of the Technical Committee for questions dealt with by this TC. Such organizations can exchange all relevant documentation and are invited to meetings. They may nominate experts to participate in a WG. 2. MoU to clarify organization & management  General management:  CIGRE: D2.convenor => A. Steven  IEC: TC57 chairman => T. Lefebvre  Operational management:  CIGRE: S. Neuman (CIGRE member, TC57 member)  IEC: P. Skare (CIGRE member, TC57-WG19 chairman)  Members:  Most of D2.24 members are TC57 members

20 WG D2.24 In brief  The ultimate goal of WG D2.24 is to deliver a complete specification for the next EMS/MMS architecture  This specification will become a key building block for future EMS/MMS procurements  WG D2.24 will work closely with the vendors to develop requirements and a time-based prioritized roadmap, which is technically and commercially viable  WG D2.24 intends to leverage existing IEC TC-57 Standards. Conversely, new IEC TC-57 standardization efforts may emerge from the WG D2.24 work products


Download ppt "Cigre WG D2.24 EMS Architectures of the 21 st Century Vasteras 2008 Alain P. STEVEN PJM Interconnection, LLC, USA CIGRE WG D2.24 Convenor Jay BRITTON AREVA."

Similar presentations


Ads by Google