IntelliGrid methodology for developing requirements for energy systems

This Publicly Available Specification (PAS) defines a methodology for power system domain experts to determine and describe their user requirements for automation systems, based on their utility business needs. This methodology was originally developed as part of the IntelliGrid Architecture developed by the Electrical Power Research Institute (EPRI), as a means to implement the 'IntelliGrid vision' of the automated, self-healing, and efficient power system of the future.

Metodologija IntelliGrid za razvojne zahteve energetskega sistema

General Information

Status
Not Published
Current Stage
PPUB - Publication issued
Start Date
29-Jan-2008
Technical report
TP IEC/PAS 62559:2009
English language
126 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)


SLOVENSKI STANDARD
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
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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
– 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

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

– 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) .
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.