CIM Projects Plans in Distribution

Transcription

1 CIM Projects Plans in Distribution Using the GWAC Stack as a Model For SG Project Plan Development John J. Simmins. Ph.D. Senior Project Manager Smart Grid Electric Power Research Institute Common Information Model (CIM) Role in Smart Grid for Transmission and Distribution September 8-9, 2010 Washington, DC

2 Agenda Three Things: 1. Description of Project Management Address why projects fail. Define the Project Management Life Cycle. Contrast with Project Life Cycle. 2. GWAC Stack Introduce the GWAC Stack as a model for SG/CIM project plan development. Discuss a project management methodology based on GWAC Stack model. 3. Apply the Methodology to CIM Implementations Drill down to the Semantic layer of the GWAC stack CIM. Planning for CIM implementations. 2

3 Projects and Why they Fail 80% of Smart Grid projects will fail Why? Because 80% of ALL projects fail 3

4 What do you mean, fail? Triple Constraint Cost/Resource Schedule/Time Scope/Quality 4

5 From SmartGridNews.com This seems to be a simple matter of bad project management - from understanding the requirements and due diligence to building an accurate business case with reliable cost/benefit analyses, the expectation setting was diametrically opposed to the actual delivery. Project Management 5

6 The Project Management Life Cycle vs. The Project Life Cycle Simple Project 1 Initiate 2 Plan 3 Execute 4 Control 5 Close PMI: PMBOK Complex or Problematic Project 1 Initiate 2 Plan 3 Execute 4 Control Re-plan Re-plan 5 Close Re-plan 6

7 The Project Management Life Cycle vs. The Project Life Cycle 1 Design Initiate Plan Execute Control Close 2 Code 3 Test Output of phase one becomes input to phase two. 4 Train 5 Release 6 Maintain The project life cycle refers to the development phases that a project can go through. For example: Evaluate Design Build Test Launch Design Code Test Train Release 7

8 GWAC Stack - Interoperability Categories Organizational Informational Technical 8: Economic/Regulatory Policy 7: Business Objectives 6: Business Procedures 5: Business Context 4: Semantic Understanding 3: Syntactic Interoperability 2: Network Interoperability 1. Basic Connectivity Political and Economic Objectives as Embodied in Policy and Regulation Strategic and Tactical Objectives Shared between Businesses Alignment between Operational Business Processes and Procedures Awareness of the Business Knowledge Related to Specific Interaction Understanding of the Concepts Contained in the Message Data Structure Understanding of Data Structure in Messages Exchanged between Systems Mechanism to Exchange Messages between Multiple Systems across Varity of Networks Mechanisms to Establish Physical and Logical Connections between Systems 8

9 GWAC Stack - Interoperability Categories Examples Organizational Informational Technical 8: Economic/Regulatory Policy 7: Business Objectives 6: Business Procedures 5: Business Context 4: Semantic Understanding 3: Syntactic Interoperability 2: Network Interoperability 1. Basic Connectivity PUC/FERC DR Program/Prices to Devices Systems/Manuals/Training CIS/MDM/OMS CIM/61850 Smart Energy Profile 2.0 TCP-IP/Wi-Fi/ZigBee IEEE (PLC) 9

10 GWAC Stack Cross Cutting Issues 8: Economic/Regulatory Policy Shared Meaning of Content Resource Identification Time Synch & Sequencing Security & Privacy Logging & Auditing Transaction & State Management System Preservation Performance/Reliability/Scalability Discovery & Configuration System Evolution Organizational Informational Technical 7: Business Objectives 6: Business Procedures 5: Business Context 4: Semantic Understanding 3: Syntactic Interoperability 2: Network Interoperability 1. Basic Connectivity There may be more. 10

11 Applying the GWAC Stack to Project Plan Development Every project has a structure a way of organizing the project. The way the project is organized is independent from the work that needs to be done on the project. The work never changes. Let s take a look at a project where we have Evaluate Design Build Test Launch 11

12 Structuring the Project Plan Around the GWAC Stack How you structure the project depends on how you report the project Sub-phases contain the tasks needed to complete the work......and are repeated for each phase. You can just as easily have the Evaluate Design Build Test Launch as the phases with the GWAC Stack defining the sub-phases 12

13 How do You Apply the Cross - Cutting Issues? Each phase and each major task must take into account the cross cutting issues. Each phase needs to be evaluated and tasks added in the appropriate place to address the cross-cutting issue. Ideally, there would be a series of documents that cover each issue that describes the tasks in the project plan. The tasks in the project plan should be easily found in the documentation and the documentation should point to the project plan. Security Security Plan Plan 13

14 Applying the Methodology to the CIM 8: Economic/Regulatory Policy Organizational 7: Business Objectives Informational Technical 6: Business Procedures 5: Business Context 4: Semantic Understanding 3: Syntactic Interoperability 2: Network Interoperability 1. Basic Connectivity CIM: Evaluate Design Build Test Launch 14

15 Applying the Methodology to the CIM - Evaluate Evaluate Design Build Test Launch Inputs Consolidated interface catalog Integration architecture blueprint Service framework and architecture Integration patterns Steps Build the use cases IntelliGrid Create the sequence diagrams IntelliGrid Build the domain model IntelliGrid 15

16 Applying the Methodology to the CIM - Design Evaluate Design Build Test Launch Collect requisite API and data structure definition documents for all end-point systems including respective meta-definitions Develop canonical model consisting of common fields and unique fields for all end-point systems involved Map canonical model to CIM UML Model, identifying required CIM extensions Define Utility's AMS Implementation Profile 16

17 Applying the Methodology to the CIM - Build Evaluate Design Build Test Launch Build the API s Create XML Message Definitions (XSDs) 17

18 Applying the Methodology to the CIM - Test Evaluate Design Build Test Launch Unit test each interface Interoperability testing (EPRI) Integration testing (EPRI) Capacity testing (EPRI) Disaster recovery testing 18

19 Applying the Methodology to the CIM - Launch Evaluate Design Build Test Launch Utility's CIM Model Utility's AMS Implementation Profile Utility's-specific CIM Model CIM-Based Message Model Message Types (XSDs) Service Definitions (WSDLs) Governance CIM version control Managing CIM extensions Recommendations to IEC Submission of CIM Extensions Submission of new Message Types 19

20 Applying the Cross Cutting Issues to the CIM Evaluation Phase: Security and Privacy Do requests need to be authenticated and authorized? Is encryption needed? Is non-repudiation needed for transactions? Performance/Reliability/Scalability How long will it take the service to process the request? How much data will be exchanged? Transaction and State Management Does a request need to be routed or orchestrated? What is the impact of the service being unavailable? Etc. 20

21 EPRI CIM for Distribution Highlights Completed Smart Meter Information Interoperability Test (61968 Part 9) Product ID: To be Delivered P : Distribution Service Guide to Enterprise Service Buses Supplemental: Guide to Using MultiSpeak in an ESB Environment CIM-MultiSpeak map and translator Three Interops

22 In Conclusion: 1. Description of Project Management Failure to plan is planning to fail. Bad project management is the single biggest cause of failed projects. 2. GWAC Stack GWAC Stack is a model for defining project scope. GWAC Stack is clearly seen and addressed in the project plan. 3. Apply the Methodology to CIM Implementations CIM implementations can be planned based on the model proposed. It isn t magic. 22

23 Together Shaping the Future of Electricity 23