SG-ENTERPRISE 2.0 Project Charter Project Name: SG-ENTERPRISE 2.0 Prepared By Document Owner(s) Project/Organization Role Gerald R. Gray, PhD (EPRI) Chair Mark Ortiz (Xtensible) Co-Chair Project Charter Version Control Version 0.1 Date Author Change Description Gerald Gray Document created [Replace this text with the name of the Change Owner.] [Replace this text with a list of changes for this Owner on this Date and Version.] [Change 1] [Change 2] [Change n] Confidential Document1 Last printed on 3/18/2016 9:10:00 AM SG-ENTERPRISE 2.0 Project Charter TABLE OF CONTENTS 1 PROJECT CHARTER PURPOSE ........................................................................................... 3 2 PROJECT EXECUTIVE SUMMARY ....................................................................................... 3 3 PROJECT OVERVIEW ............................................................................................................ 4 4 PROJECT SCOPE................................................................................................................... 4 5 4.1 Goals and Objectives .................................................................................................. 4 4.2 Project Deliverables .................................................................................................... 4 4.3 Deliverables Out of Scope .......................................................................................... 5 PROJECT CONDITIONS ........................................................................................................ 5 5.1 Project Assumptions ................................................................................................... 5 5.2 Project Issues.............................................................................................................. 5 5.3 Project Risks ............................................................................................................... 6 5.4 Project Constraints ...................................................................................................... 6 6 PROJECT STRUCTURE APPROACH ................................................................................... 6 7 PROJECT REFERENCES ...................................................................................................... 6 8 APPROVALS ........................................................................................................................... 7 Confidential Page 2 3/18/2016 SG-ENTERPRISE 2.0 Project Charter 1 PROJECT CHARTER PURPOSE The project charter defines the scope, objectives, and overall approach for the work to be completed. It is a critical element for initiating, planning, executing, controlling, and assessing the project. It should be the single point of reference on the project for project goals and objectives, scope, organization, estimates, work plan, and budget. In addition, it serves as a contract between the Project Team and the Project Sponsors, stating what will be delivered according to the budget, time constraints, risks, resources, and standards agreed upon for the project. The scope of SG-ENTERPRISE is the systems and/or applications within and around the utility enterprise and the inter-systems related business functions and stops at the boundaries of applications and the edge of utility enterprise. The focus is on how these systems are to be integrated and composed to support AMI related business processes and functions. SG-ENTERPRISE 2.0 charter will leverage available and applicable industry best practices and standards for this work, and to tie the required pieces together to support the implementation of AMI related processes, applications, and infrastructure technologies. SG-Enterprise 2.0 will provide specific requirements and supporting artifacts that support the implementation of AMI profile (i.e. strongly typed profiles). 2 PROJECT EXECUTIVE SUMMARY The SG-ENTERPRISE 2.0 project will encompass: The creation of new deliverables; use-case, activity, integration requirements, and sequence diagrams Objectives o Refactor existing 1.0 deliverables to correct known errors o Incorporate feedback from IEC WG14 o Review use cases that became part of OpenADR and OpenADE for inclusion in scope o Align use case development and actors with appropriate reference organizations, e.g., IEC WG14, MultiSpeak o Develop new uses cases and standards-based message profiles as needed Assumptions: All contributions will be free of any intellectual property encumbrances (all meetings will cover the IP policy of the UCAIUG in the introduction) Risks o a contribution to this effort may have IP associated with it o This effort may overlap other industry efforts Labor will be voluntary, with deliverables to use the repository resources of the UCAIUG Timeline – flexible, to be determined by the completion of those items deemed to be in scope for the SG-ENTERPRISE 2.0 effort The approach will use the UCAIUG model of utilizing volunteer efforts of UCA members and subject to the operating policies Confidential Page 3 3/18/2016 SG-ENTERPRISE 2.0 Project Charter 3 PROJECT OVERVIEW The initial SG-ENTERPRISE work was begun in 2008 and completed in 2009. At the time of its ratification there were some known errors in the deliverables. The stated intention by the Task Force was that these deficiencies were going to be addressed by a future release. However, there has been approximately three year gap between the stated intent and any action being taken. In the interim the industry has advanced, with concepts such as Demand Response and Automated Data Exchange being advanced from business and user requirements to recognized standards. Additionally, while the deliverables from SGENTERPRISE were contributed to IEC TC57 WG14 and impacted the development of upcoming IEC 61968 parts as well as the IEC 61968-9 2nd Edition, feedback from the working group has yet to be incorporated into the current deliverables. This project will seek to rectify any current known errors in the 1.0 deliverables, refactor 1.0 deliverables, and also reexamine the use cases from the 1,0 work for completeness and validity. 4 PROJECT SCOPE 4.1 Goals and Objectives Goals Objectives The project will provide improved use case and integration guidance for utilities and vendors that serve this domain. [Replace this text with Objectives for each Goal. For example: 1. Correct known errors in SG-ENTERPRISE 1.0 deliverables. 2. Refactor deliverables to reflect feedback received from IEC WG14 3. Review Demand Response and Automated Data Exchange use cases for inclusion in scope (these efforts have been incorporated into other standards) 4. Identify new use cases, activity diagrams, integration requirements, and message profiles 5. Align use cases and actors with existing industry references, e.g. IEC WG14 (IEC 61968-1), MultiSpeak 4.2 Project Deliverables Milestone Deliverable 1. Create Enterprise Architect repository http://svn.ucaiug.org/svn/amientrepos 2. AMI-ENT 1.0 issue Address known issues logged in the UCAIUG Help Confidential Page 4 3/18/2016 SG-ENTERPRISE 2.0 Project Charter review 4.3 Desk; resolutions noted in the Help Desk Repository updated to reflect resolutions 3. Updated actors, activity diagrams, message profiles based on WG14 feedback Updated repository 4. Identification and development of new use cases Updated repository, e.g. DER, Load Management, Asset Monitoring 5. Business Requirements document Final deliverable reflecting the outputs of the SGENTERPRISE repository 6. Service Definitions Example WSDLs and XSDs for integration requirements identified in the use cases Deliverables Out of Scope The following items are considered out of scope for this effort: Organizational impact analysis – this would be dependent on a given implementation Service definition creation – while the effort may define new message profiles, the creation of a service definitions template is already adequately covered by IEC 61968-100 CD. This effort will use the existing template for any new WSDLs 5 PROJECT CONDITIONS 5.1 Project Assumptions 5.2 Any contributions will be free of any intellectual property encumbrances All labor is voluntary; there is no budget for paid contributions The project will utilize the UCAIUG Enterprise Architecture repository Project Issues Priority Criteria 1 − High-priority/critical-path issue; requires immediate follow-up and resolution. 2 − Medium-priority issue; requires follow-up before completion of next project milestone. 3 − Low-priority issue; to be resolved prior to project completion. 4 − Closed issue. # Date 1 [mm/dd/yy] Confidential Priority Owner Description Status & Resolution [Issue 1 description] [Replace this text with Status and Proposed or Page 5 3/18/2016 SG-ENTERPRISE 2.0 Project Charter # Date Priority Owner Description Status & Resolution Actual Resolution.] 2 5.3 5.4 [Issue 2 description] [Replace this text with Status and Proposed or Actual Resolution.] Project Risks # Risk Area Likelihood Risk Owner Project Impact-Mitigation Plan 1 Contribution IP Low Gerald Gray / Mark Ortiz All meetings will include the UCAIUG IP policy in the introduction. Any notification of an IP issue will be forwarded to the UCAIUG legal counsel 2 Overlapping industry effort Medium Gerald Gray / Mark Ortiz Task force leadership participates in the SGiP Architecture Committee, WG14, and MultiSpeak Technical committees. Every effort will be made to align with other industry initiatives. Project Constraints 6 [mm/dd/yy] As a volunteer effort the development of deliverables will be constrained by the bandwidth and contributions of the volunteers making up this task force Project Structure Approach This task force will be led by the Chair / Co-Chair utilizing weekly conference calls and triannual OpenSG meetings to solicit the contributions from UCAIUG membership 7 PROJECT REFERENCES Reference Description IEC 61968-1 Application integration at electric utilities, ed1.0 http://webstore.iec.ch/webstore/webstore.nsf/Artnum_PK/31109 IEC 61968-100 CD Implementation profiles for IEC 61968 [Committee Draft] Confidential Page 6 3/18/2016 SG-ENTERPRISE 2.0 Project Charter 8 APPROVALS Prepared by __________________________________ Project Manager Approved by __________________________________ UCAIUG Technical Committee Confidential Page 7 3/18/2016