|
SIST-TP IEC/PAS 62559:2009
01-junij-2009
Metodologija IntelliGrid za razvojne zahteve energetskega sistema
IntelliGrid Methodology for Developing Requirements for Energy Systems
Ta slovenski standard je istoveten z: IEC/PAS 62559
ICS:
29.020 Elektrotehnika na splošno Electrical engineering in
general
SIST-TP IEC/PAS 62559:2009 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST-TP IEC/PAS 62559:2009
---------------------- Page: 2 ----------------------
SIST-TP IEC/PAS 62559:2009
IEC/PAS 62559
Edition 1.0 2008-01
PUBLICLY AVAILABLE
SPECIFICATION
PRE-STANDARD
IntelliGrid Methodology for Developing Requirements for Energy Systems
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XF
ICS 29.020 ISBN 2-8318-9525-1
---------------------- Page: 3 ----------------------
SIST-TP IEC/PAS 62559:2009
– 2 – PAS 62559 © IEC:2008(E)
CONTENTS
FOREWORD .9
EPRI DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITIES .11
1. SCOPE AND OBJECTIVES .12
1.1 Scope of the Specification .12
1.2 Overview of the Methodology .12
1.2.1 Concept of System Engineering .12
1.2.2 IntelliGrid System Engineering Methodology.12
1.2.3 Overview of Phased Approach .14
1.2.4 Phase 1: IntelliGrid Methodology for Executives .15
1.2.5 Phase 2: IntelliGrid Methodology for Domain Experts: Modeling User
Requirements with Use Cases.15
1.2.6 Phase 3: IntelliGrid Methodology for Project Engineers: Developing Detailed
User Requirements .17
1.3 Objectives of this Specification .17
1.4 Audience of this Specification .18
2. NORMATIVE REFERENCES.19
3. DEFINITIONS AND ABBREVIATIONS .21
4. GLOSSARY OF TERMS . 21
4.1 Referenced Sources of Glossary Terms. 21
4.2 Terms and Definitions . 22
5. INTRODUCTION TO THE INTELLIGRID ARCHITECTURE . 23
5.1 History and Rationale. 23
5.2 Basic Concepts . 24
5.3 The Pyramid. 25
5.4 Business Needs and Functional Requirements. 26
5.5 Development Phases. 27
5.6 Development Streams. 29
5.7 Scope Addressed in this Specification. 30
6. PHASE 1: EXECUTIVES DETERMINE BUSINESS NEEDS AND PLAN PROJECTS . 32
6.1.1 Determine Business and Regulatory Drivers. 32
6.1.2 Choose Projects. 32
6.1.3 Identify Candidate Technologies. 32
6.1.4 Define a High-Level Business Case . 32
---------------------- Page: 4 ----------------------
SIST-TP IEC/PAS 62559:2009
PAS 62559 © IEC:2008(E) – 3 –
6.1.5 Refine Process for Your Organization .32
6.1.6 Identify Stakeholders .32
6.1.7 Establish a Project Team .33
6.1.8 Select Teams .33
7. PHASE 2: STAKEHOLDERS DEFINE USER REQUIREMENTS WITH USE CASES.35
7.1 Use Case Methodology.36
7.1.1 Use Case Introduction . 37
7.1.2 Use Case Selection.37
7.2 Use Case Workshops to Develop Requirements .37
7.2.1 Use Case Workshop Goals.37
7.2.2 Use Case Workshop Membership .38
7.2.3 Use Case Workshop Planning.38
7.2.4 Use Case Workshop Agendas.38
7.2.5 Developing Requirements and Business Value.39
7.2.6 Writing Good Requirements.40
7.3 Use Case Analysis.42
7.3.1 Global Actor List.42
7.3.2 Activity Diagrams .42
7.3.3 Interface Diagrams.44
7.3.4 Message Sequence Diagrams.44
7.3.5 Use Case Interaction Diagrams.45
7.3.6 Refining Requirements .45
7.3.7 Identify Security Risks.45
7.3.8 Distill Requirements .46
7.3.9 Evaluate Requirements vs. Business Case.46
7.3.10 Publish Requirements.46
8. PHASES 3-5: TECHNOLOGY SELECTION AND DEPLOYMENT .47
8.1 Design an Architecture.48
8.1.1 Resolve List of Actors .48
8.1.2 Identify Messages Exchanged.49
8.1.3 Define Interfaces.49
8.1.4 Define Security Domains .49
8.1.5 Define Security and Network Management Policies.49
8.1.6 Break Down Actors into Components.50
8.1.7 Assess Candidate Technologies.50
8.1.8 Map Candidate Technologies to Interfaces .50
8.1.9 Define Integration Interfaces.51
8.1.10 Test Architecture against Use Cases.51
---------------------- Page: 5 ----------------------
SIST-TP IEC/PAS 62559:2009
– 4 – PAS 62559 © IEC:2008(E)
8.2 Select Technologies.51
8.2.1 Build Technology Capability Scales.51
8.2.2 Request Proposals.51
8.2.3 Evaluate Requirements and Proposals.53
8.2.4 Perform Gap Analysis . 53
8.2.5 Trade-Off Requirements .53
8.2.6 Identify Missing Standards and Technologies .53
8.2.7 Create Technology Roadmap.53
8.2.8 Submit Proposals to Standards Bodies and Industry Groups .54
8.2.9 Complete Final Business Case.54
A. ANNEX A: HOW TO DEVELOP USE CASES .55
A.1 What is a Use Case? .55
A.2 Purpose of the IntelliGrid PAS Use Case Template .55
A.3 IntelliGrid PAS Use Case Template: Setting the Stage.55
A.3.1 Domain Expert(s) Responsible for Use Case .55
A.3.2 Name of Function.56
A.3.3 Scope and Objectives of Function .56
A.3.4 Narrative of Function.56
A.3.5 Actors: People, Systems, Applications, Databases, the Power System, and
Other Stakeholders .56
A.3.6 Legal Issues: Contracts, Regulations, Safety Rules, and Other Constraints .56
A.3.7 Preconditions and Assumptions.56
A.4 IntelliGrid PAS Use Case Template: A Picture is Worth a Thousand Words .56
A.5 IntelliGrid PAS Use Case Template: Step-by-Step Interactions within Function.57
A.5.1 Steps Describe the Detailed Interactions.57
A.5.2 Contents of Steps.57
A.6 IntelliGrid PAS Use Case Template: Characteristics of Steps.58
A.6.1 Characteristics of Steps Capture Constraints and Details of User Requirements .58
A.6.2 Configuration Issues .58
A.6.3 IntelliGrid Quality of Service (QoS) Issues .62
A.6.4 IntelliGrid Security Issues .64
A.6.5 IntelliGrid Data Management Issues.67
A.6.6 IntelliGrid Constraints and Other Issues .71
B. ANNEX B: USE CASE TEMPLATE.72
B.1 Description of the User Requirements of a Function.72
B.1.1 General .72
B.1.2 Domain Expert(s) .72
B.1.3 Name of Function.72
---------------------- Page: 6 ----------------------
SIST-TP IEC/PAS 62559:2009
PAS 62559 © IEC:2008(E) – 5 –
B.1.4 Scope and Objectives of Function .72
B.1.5 Narrative of Function.73
B.1.6 Actors: People, Systems, Applications, Databases, the Power System, and
Other Stakeholders .73
B.1.7 Legal Issues: Contracts, Regulations, Policies, and Constraints .73
B.1.8 Preconditions and Assumptions.73
B.2 Drawing or Diagram of Function .75
B.3 Step by Step Analysis of Function .76
B.3.1 Steps – Normal Sequence .76
B.3.2 Steps – Alternative, Error Management, and/or Maintenance/Backup
Sequences .77
C. ANNEX C: EXAMPLE OF TRANSMISSION SYNCHRO-PHASOR USE CASE .79
C.1 Description of the User Requirements of a Function.79
C.1.1 General .79
C.1.2 Domain Expert(s) .79
C.1.3 Name of Function.79
C.1.4 Scope and Objectives of Function .79
C.1.5 Narrative of Function.79
C.1.6 Actors: People, Systems, Applications, Databases, the Power System, and
Other Stakeholders .82
C.1.7 Legal Issues: Contracts, Regulations, Policies, and Constraints .83
C.2 Drawing or Diagram of Function .84
Step by Step Analysis of Function .85
C.2.1 Preconditions and Assumptions.85
C.2.2 Steps – Normal Sequence .86
C.2.3 Steps – Alternative, Error Management, and/or Maintenance/Backup
Sequences .89
EXAMPLE OF DISTRIBUTION AUTOMATION USE CASE .91
C.3 Description of the User Requirements of a Function.91
C.3.1 General .91
C.3.2 Domain Expert(s) .91
C.3.3 Name of Function.91
C.3.4 Scope and Objectives of Function .91
C.3.5 Narrative of Function.92
C.3.6 Actors: People, Systems, Applications, Databases, the Power System, and
Other Stakeholders .97
C.3.7 Legal Issues: Contracts, Regulations, Policies, and Constraints .100
C.3.8 Preconditions and Assumptions.101
C.4 Drawing or Diagram of Function .104
---------------------- Page: 7 ----------------------
SIST-TP IEC/PAS 62559:2009
– 6 – PAS 62559 © IEC:2008(E)
C.5 Step by Step Analysis of Function .104
C.5.1 Steps – Normal Sequence .104
C.5.2 Steps – Alternative, Error Management, and/or Maintenance/Backup
Sequences . 112
D. EXAMPLE OF CONSUMER USE CASE . 114
D.1 Description of the User Requirements of a Function. 114
D.1.1 General . 114
D.1.2 Domain Expert(s) . 114
D.1.3 Name of Function. 114
D.1.4 Scope and Objectives of Function . 114
D.1.5 Narrative of Function. 115
D.1.6 Actors: People, Systems, Applications, Databases, the Power System, and
Other Stakeholders . 116
D.1.7 Legal Issues: Contracts, Regulations, Policies, and Constraints . 118
D.1.8 Preconditions and Assumptions. 118
D.2 Step by Step Analysis of Function . 120
D.2.1 Steps – Normal Sequence . 120
D.2.2 Steps – Alternative, Error Management, and/or Maintenance/Backup
Sequences . 125
---------------------- Page: 8 ----------------------
SIST-TP IEC/PAS 62559:2009
PAS 62559 © IEC:2008(E) – 7 –
Figures
Figure 1: IntelliGrid Methodology for Project Definition .13
Figure 2: IntelliGrid Applications . 24
Figure 3: The IntelliGrid Architecture Pyramid. 26
Figure 4: Phases of the IntelliGrid Development Process . 28
Figure 5: Streams of the IntelliGrid Development Process. 29
Figure 6: Potential Stakeholders and Requirements Team Structure . 33
Figure 7: The Use Case Workshop Requirements Development Process. 36
Figure 8: Example of an Activity Diagram. 43
Figure 9: Interface Diagram Example . 44
Figure 10: Message Sequence Diagram Example .45
Figure 11: Requirements and Systems Architecture Process . 47
Figure 12: Technology Selection, Business Case, and Deployment Process. 48
Figure 13: Overview of the Technology Selection Process . 51
Figure 14: Example of a Technology Capability Measurement Scale . 52
Figure 15: Illustrative Diagram of a Function Described in a Use Case . 57
---------------------- Page: 9 ----------------------
SIST-TP IEC/PAS 62559:2009
– 8 – PAS 62559 © IEC:2008(E)
Tables
Table 1: Checklist of IntelliGrid Configuration Issues .59
Table 2: Checklist of IntelliGrid Quality of Service Issues .63
Table 3: Checklist of IntelliGrid Security Issues.65
Table 4: Checklist of IntelliGrid Data Management Issues.67
---------------------- Page: 10 ----------------------
SIST-TP IEC/PAS 62559:2009
PAS 62559 © IEC:2008(E) – 9 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
IntelliGrid Methodology for Developing Requirements for Energy Systems
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising all
national electrotechnical committees (IEC National Committees). The object of IEC is to promote international co-
operation on all questions concerning standardization in the electrical and electronic fields. To this end and in
addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports,
Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publication(s)”). Their preparation
is entrusted to technical committees; any IEC National Committee interested in the subject dealt with may participate
in this preparatory work. International, governmental and non-governmental organizations liaising with the IEC also
participate in this preparation. IEC collaborates closely with the International Organization for Standardization (ISO)
in accordance with conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all interested
IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence between any
IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter.
5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any equipment
declared to be in conformity with an IEC Publication.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or other
damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and expenses arising
out of the publication, use of, or reliance upon, this IEC Publication or any other IEC Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
The International Electrotechnical Commission (IEC) draws attention to the fact that it is claimed that compliance with this
SM
document may involve the use of a service mark concerning EPRI .
Electric Power Research Institute and EPRI are registered service marks of the Electric Power Research Institute, Inc.
EPRI. ELECTRIFY THE WORLD and EPRI. SHAPING THE FUTURE OF ELECTRICITY are service marks of the Electric
Power Research Institute, Inc.
IEC takes no position concerning the evidence, validity and scope of this service mark right.
The holder of these service mark rights has assured the IEC that it is willing to negotiate licences under reasonable and
non-discriminatory terms and conditions with applicants throughout the world. In this respect, the statement of the holder
of these service mark rights are registered with IEC. Information may be obtained from:
EPRI, 3420 Hillview Avenue, Palo Alto, California 94303 USA
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights other
than those identified above. IEC shall not be held responsible for identifying any or all such patent rights.
A PAS is a technical specification not fulfilling the requirements for a standard but made available
to the public .
IEC-PAS 62559 has been processed by technical committee 8: Systems aspects for electrical energy
supply.
The text of this PAS is based on the This PAS was approved for
following document: publication by the P-members of the
committee concerned as indicated in
the following document
Draf
...