Iec pas 62559 2008

x Design engineers develop the Technical Specifications, which combine the user requirements from the domain experts, the strategic standards and technologies from the information speci

SCOPE AND OBJECTIVES

Scope of the Specification

This Publicly Available Specification (PAS) outlines a methodology for power system experts to identify and articulate their user requirements for automation systems, tailored to their utility business needs This approach was initially created as part of the IntelliGrid initiative.

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.

Overview of the Methodology

The IntelliGrid methodology, a key aspect of systems engineering, distinguishes between "user requirements" and "technical specifications." User requirements articulate the essential needs without tying them to specific designs or technologies, whereas technical specifications detail the implementation of automation systems to fulfill these user needs.

The IntelliGrid systems engineering methodology, as depicted in Figure 1, involves several key roles and project steps Executives and utility managers assess business cases to justify specific projects, which they subsequently approve A project team, led by domain experts and engineers, is then formed to execute the project One of the initial tasks for this team is to identify and include all relevant power system experts and stakeholders, whether full-time or part-time, who may influence or be affected by the project Additionally, domain experts evaluate existing IntelliGrid Use Cases for their relevance and potential insights.

Domain experts create a comprehensive list of Use Cases that address specific business needs, as well as other user requirements and potential future impacts related to the project This process may involve collaboration with project engineers who possess a deep understanding of the Use Cases.

The case process involves drafting key Use Cases that encompass all essential user requirements Domain experts then review and refine these Use Cases to ensure accurate representation of their needs, while also identifying potential misunderstandings, overlaps, gaps, and other inconsistencies.

Project engineers evaluate and coordinate Use Cases to create a comprehensive user requirements document that focuses solely on user needs Information specialists then implement relevant standards and technologies derived from this document, guided by the strategic vision of the IntelliGrid Architecture Subsequently, design engineers formulate the Technical Specifications, integrating user requirements from domain experts, strategic standards and technologies from information specialists, and the tactical system development approach recommended by the IntelliGrid Architecture.

Figure 1: IntelliGrid Methodology for Project Definition

The user requirements gathered through the Use Case process are comprehensively detailed in the user requirements document, which outlines the functions from the user's perspective This includes a functional description of processes, user choices, input data types, result types, and potential display appearances.

The article outlines several critical factors for internal use at MECON Limited in Ranchi and Bangalore It highlights configuration issues, including access to field data and challenges posed by electrically noisy environments Performance requirements are emphasized, focusing on availability, response times, and precision Security needs are also addressed, covering confidentiality, access restrictions, and failure detection Additionally, data management requirements are discussed, considering device numbers, data volumes, and growth expectations Finally, it notes various constraints, such as legal and regulatory issues, that may affect these requirements.

This PAS focuses solely on the methodology for identifying and documenting user requirements, distinct from a complete systems engineering approach that also includes the development of technical specifications.

The IntelliGrid methodology encompasses the complete system development process; however, this PAS specifically targets the development of User Requirements, focusing primarily on the initial three phases while also considering the subsequent phases as they relate to User Requirements.

The IntelliGrid Architecture outlines a comprehensive methodology for project execution, encompassing several key phases In Phase 1, executives evaluate Business Cases to authorize projects aimed at achieving business objectives.

In the decision-making process, executives must consider cost justification and other non-technical factors; however, from the perspective of the IntelliGrid Architecture, it is crucial that all issues related to the IntelliGrid Strategic Vision are thoroughly addressed before approving projects.

Business Cases must clearly outline the inclusion or exclusion of Strategic Vision issues in the project, addressing aspects such as Use Case modeling, abstract data models, security, network and system management, data management, and integration/interoperability In Phase 2, Domain Expert Stakeholders articulate their User Requirements through a formal Use Case process, allowing for a structured expression of needs that can be refined into detailed functional and performance requirements in the subsequent phase Phase 3 involves Project Engineers who develop these detailed requirements based on the Use Cases provided by domain experts Finally, in Phase 4, Project Engineers and IT Specialists evaluate the relevance of identified standards, technologies, and best practices to the project, ensuring alignment with the appropriate IntelliGrid framework.

Environments x Phase 5: Design Engineers develop Technical Specifications based on Strategic Vision,

LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU.

1.2.4 Phase 1: IntelliGrid Methodology for Executives

1.2.4.1 Step 1: IntelliGrid Recommendations for Executives

As described in the IntelliGrid Architecture report and web site, the following are the general

Utility executives are encouraged to adopt the IntelliGrid Architecture as the foundational vision for their information infrastructure It is essential for all users to comprehend how to effectively utilize the various components of the IntelliGrid Architecture, including its power system functional descriptions and strategic vision Additionally, a tailored implementation plan should be developed, taking into account the utility's specific business requirements, appropriate timelines, and financial limitations Lastly, providing feedback to EPRI and standards organizations is crucial for the continuous improvement of the IntelliGrid framework.

Architecture must adapt to future requirements and establish standards for upcoming developments It is essential for all Business Cases to clearly articulate the relevance of the Strategic Vision issues to the project This includes incorporating Use Case modeling for functionalities, abstract data models, security considerations, network and system management, data management, and ensuring integration and interoperability.

1.2.4.2 Step 2: Executives and Business Needs

When specific business needs are identified, executives have long used Business Cases as the method for assessing and determining which business needs can and should be met Business

Cases typically describe the business need, provide financial and organizational assessments of potential ways for meeting the business need, and recommend a specific solution with a justification for that recommendation

As the first phase in the IntelliGrid methodology, executives (or other utility decision-makers) are expected to review the Business Cases and approve those that meet certain justification criteria

After project approval by executives, the initial step is to assemble a project team comprising representatives from key stakeholders This inclusion is vital for gathering valuable functional requirements and securing buy-in from the end users While not all stakeholders need to be full-time team members, they should always participate in discussions pertinent to their expertise.

1.2.5 Phase 2: IntelliGrid Methodology for Domain Experts: Modeling User Requirements with

1.2.5.1 Step 1: Identification of All Potential Stakeholders

Objectives of this Specification

IEC TC8 focuses on developing international standards for electricity supply systems, emphasizing a balance between cost and quality for users This includes the coordination of transmission and distribution networks, as well as connected installations like generators and loads, ensuring comprehensive system aspects are addressed.

IEC TC8 is creating this PAS to establish a standardized methodology for consistently and comprehensively determining and defining user requirements, as existing standards typically focus solely on technical issues.

It is essential to establish clear standards that help users define their requirements comprehensively, distinguishing between "user requirements" (the "what" needed by power system experts) and "technical specifications" (the "how" detailing systems and applications) Currently, this distinction is often blurred, with project engineers focusing on the "how" without fully understanding the "what." It is critical to identify all user requirements before making any commitments on how to fulfill them, as the complexity of automation and control systems can lead to significant challenges if requirements are not clearly defined from the outset Additionally, a robust testing mechanism should be implemented to ensure that user requirements are met, regardless of the standards and technologies used by vendors.

Audience of this Specification

The target audience for this PAS includes executives assessing business needs and seeking to understand the implementation process for effective solutions It also caters to power system experts who possess knowledge in power engineering but lack familiarity with articulating their automation requirements for project engineers Additionally, it addresses project engineers who are well-versed in general project management but aim to adopt advanced methodologies to enhance the collection of user requirements, thereby reducing the necessity for unplanned modifications and replacements of systems and equipment due to unforeseen user demands.

NORMATIVE REFERENCES

Users can access the IntelliGrid Architecture documents or the IntelliGrid Architecture web site athttp://IntelliGrid.info.

DEFINITIONS AND ABBREVIATIONS

EPRI Electric Power Research Institute

IEEE Institute of Electrical and Electronic Engineers

GLOSSARY OF TERMS

Referenced Sources of Glossary Terms

x IEC TC/SC:ACEA IEC GUIDE 114, ed 1.0 (2005-05) Ref 3.13 x IEEE STD 1471, 2001

Terms and Definitions

4.2.1 Application (Software) Software designed to fulfill specific needs of a user: for example, software for navigation, payroll, or process control [IEEE Std 100-1992]

Software that is specific to the solution of an application problem [ANSI X3.172-1996]

4.2.2 Architecture An architecture is the fundamental organization of a system embodied in its components their relationships to each other and to the environment, and the principles guiding its design and evolution [IEEE Std 1471]

4.2.3 Business Need Requirement of a business to meet its mission, goals, and/or objectives

Business needs can be identified in a business case that describes a project or procedure to meet that business need [Common Usage]

4.2.4 Domain An area of knowledge or activity characterized by a set of concepts and terminology understood by practitioners in that area [OMG UML]

A methodology is a codified set of practices carried out to produce software

4.2.6 Project Engineer An engineer or team of engineers who undertake a project [Common Usage]

4.2.7 Project Management Project management is the discipline of defining and achieving finite objectives The challenge of project management is the optimized integration and allocation of the inputs needed to meet those pre-defined objectives The project, therefore, is a carefully selected set of activities chosen to use resources (time, money, people, materials, energy, space, provisions, communication, quality, risk, etc.) to meet the pre-defined objectives

4.2.8 Design Specification Document or set of documents that describe the organization and functioning of an item, and that are used as a basis for the implementation and the integration of the item IEC 62138, ed

4.2.9 Use Case Class specification of a sequence of actions, including variants, that a system (or other entity) can perform, interacting with actors of the system IEC 62390, ed 1.0 (2005-01)

Modeling language and methodology for specifying, visualizing, constructing, and documenting the artifacts of a system-intensive process IEC 61970-501, ed 1.0 (2006-03)

4.2.11 User Requirements Requirements of the function based on the business needs, without explicitly identifying any specific technologies or products The same document can also cover “non-functional” requirements, such as constraints, performance, security, and data interactions with other applications or systems [Common Usage]

INTRODUCTION TO THE INTELLIGRID ARCHITECTURE

History and Rationale

In 2002, the Electric Power Research Institute (EPRI) launched a research project that led to the creation of the IntelliGrid Architecture This architecture emphasizes the need for an interactive design of both power system infrastructure and information infrastructure to achieve a future vision of a highly reliable, efficient, and self-healing power grid.

Since the advent of electrical power, utilities have meticulously designed, constructed, operated, and maintained the power system infrastructure With the increasing demand for information and automation, it is essential that the information infrastructure is also developed and managed in close alignment with the power system.

Power engineers depend on established standards and technologies to develop the power system infrastructure, while information engineers must also utilize these standards and technologies to create an information infrastructure that meets the needs of the power system.

A methodology is essential to connect power engineers with information engineers, enabling power system engineers to articulate their information user requirements without needing to become immediate "information experts." This approach will help identify the appropriate standards and technologies to be utilized.

The IntelliGrid Architecture employs a methodology grounded in Use Cases, recognized as a best practice in system engineering across various industries A Use Case serves as a narrative detailing how a system will be utilized, ideally crafted by the end-users themselves This approach enables users to articulate their information needs clearly and comprehensively, allowing information specialists and design engineers to create automation systems that precisely align with those requirements.

Basic Concepts

The IntelliGrid methodology provides a structured approach for utilities to design effective communication and information systems aimed at enhancing transmission and distribution networks, as well as improving customer interactions It outlines the applicable domain space for the IntelliGrid System Architecture, ensuring comprehensive integration within utility operations.

Real-time Simulation and Contingency Analysis

Distributed Generation and Alternate Energy Sources Distributed Generation and Alternate Energy Sources

Self-Healing Wide-Area Protection and Islanding Self-Healing Wide-Area Protection and Islanding Asset Management and On-Line Equipment Monitoring

Asset Management and On-Line Equipment Monitoring

Demand Response and Real-time Pricing Demand Response and Real-time Pricing Participation in Energy Markets

Shared Information – Continuously Optimizing – Intelligent Responses!

The IntelliGrid Architecture emphasizes key principles such as the integration of systems, particularly between the power system and its controlling communication system It advocates for the use of standards-based open systems that ensure interoperability Additionally, it encourages users to define their applications and requirements while aligning technology solutions with these specific needs.

The IntelliGrid Architecture offers a range of tools for designing utility communications and information systems, including templates for capturing and defining requirements, recommendations for applicable standards and technologies, and strategies for integrating security into systems.

MECON Limited is licensed for internal use in Ranchi and Bangalore, with resources provided by the Book Supply Bureau The article discusses strategies for migrating to open, standards-based systems and integrating them with existing systems It also emphasizes the development of "layered" solutions to reduce the impact of future technological changes.

An application of the IntelliGrid Architecture is the use of any or all of the above tools and high- level concepts

This chapter explores three effective methods for describing and utilizing the IntelliGrid Architecture, which are essential for gathering requirements The methods discussed include the conceptual pyramid, five sequential steps, and three concurrent streams, with a focus on their relevance to the current specification.

The Pyramid

The concepts and tools of the IntelliGrid Architecture discussed in the previous section can be viewed as a pyramid that consists of the following components Figure 3 depicts the IntelliGrid

The architecture pyramid illustrates how various components interconnect, starting with business needs that are recognized and validated through business cases approved by executives These needs drive the initiation of projects aimed at fulfilling them, which must incorporate the requirements of multiple stakeholders The IntelliGrid methodology emphasizes the importance of this integration.

“domain expert” stakeholders to describe their requirements in comprehensive sets of

Use Cases serve as a foundation for project engineers to create a unified document that encapsulates user requirements from all stakeholders A strategic vision emphasizes abstract modeling, security, network and system management, data management, integration, interoperability, and technology independence, which must be integrated into the system design phase as user requirements transition to detailed technical specifications A tactical approach employing technology-independent techniques, such as information models, common services, and interfaces, identifies the necessary technical concepts for effective system design that aligns with strategic requirements Additionally, adhering to established standards, technologies, and best practices can enhance the effectiveness of various projects.

The energy industry has diverse information requirements, some specific to its operations and others shared with various sectors To address these needs, the IntelliGrid Architecture classifies them into distinct environments, each defined by common requirements and associated standards and technologies Additionally, it outlines methodologies for utilizing the IntelliGrid Architecture, tailored for different stakeholders such as executives, automation architects, power system planners, project engineers, information specialists, regulators, and standards organizations.

Strategic Vision Abstract Modeling, Security, Network Mgmt, Data Mgmt, Interoperability

Business Needs Power System Functional Requirements

Tactical Approach Technology Independent Techniques, based on Information Models, Common Services, and Interface Adapters

IntelliGrid Environments: Categorization of Standards

Utilizing IntelliGrid environments allows for the effective categorization of relevant standards, technologies, and best practices, aligning with strategic vision concepts This tactical approach is essential for managing legacy systems while also planning for future methodologies, catering to the needs of executives, stakeholders, project engineers, and IT specialists.

Need s St anda rds and

Ass essed toM eet Bu sine ssN eeds

1 Executives use Business Cases to approve projects to meet Business Needs

2 Domain Expert Stakeholders describe their Business Needs through the formal Use Case process

3 Project Engineers develop Functional and Performance Requirements from the Use Cases

4 Project Engineers and IT Specialists assess Applicability of the Standards identified in the Environments

5 Design Engineers develop Specifications based on Strategic Vision, Tactical Approach, & Standards

Strategic Vision Abstract Modeling, Security, Network Mgmt, Data Mgmt, Interoperability

Business Needs Power System Functional Requirements

Tactical Approach Technology Independent Techniques, based on Information Models, Common Services, and Interface Adapters

IntelliGrid Environments: Categorization of Standards

Utilizing IntelliGrid environments allows for the effective categorization of relevant standards, technologies, and best practices, aligning with strategic vision concepts This tactical approach is essential for managing legacy systems while also planning for future methodologies, catering to the needs of executives, stakeholders, project engineers, and IT specialists.

Need s St anda rds and

Ass essed toM eet Bu sine ssN eeds

1 Executives use Business Cases to approve projects to meet Business Needs

2 Domain Expert Stakeholders describe their Business Needs through the formal Use Case process

3 Project Engineers develop Functional and Performance Requirements from the Use Cases

4 Project Engineers and IT Specialists assess Applicability of the Standards identified in the Environments

5 Design Engineers develop Specifications based on Strategic Vision, Tactical Approach, & Standards

Figure 3: The IntelliGrid Architecture Pyramid

Business Needs and Functional Requirements

At the top of the IntelliGrid pyramid lies the business needs of the power system, which serve as the primary drivers for all other components of the IntelliGrid Architecture Projects aimed at fulfilling these business needs are usually identified through business cases that outline the project's rationale, anticipated benefits, and the various options evaluated.

The article outlines the process of evaluating project options, including reasons for acceptance or rejection, anticipated project costs, a gap analysis, and potential risks After obtaining high-level authorization for projects, the subsequent step involves identifying the functional requirements necessary for successful implementation.

Historically, transitioning from project authorization to implementation primarily required power system engineers to create a technical specification for vendors or internal use, aimed at procuring power system equipment and software applications This process typically involved minimal collaboration with other teams, as engineers focused solely on detailing their requirements.

That process is no longer the optimal methodology except possibly for the simplest purchases

The integration of power system equipment, computer systems, and software applications is essential for creating a cohesive infrastructure An increasing number of users are eager to leverage the information generated by these systems, which often extends beyond the interests of core users For example, operators utilize SCADA systems to access and manage this valuable data.

MECON Limited is licensed for internal use in Ranchi and Bangalore, with resources supplied by the Book Supply Bureau While systems are primarily designed to monitor essential power system states, they often overlook routine maintenance activities, distribution transformer loadings, and customer power quality measurements Nevertheless, operators can enhance their effectiveness by accessing a broader range of information, which can also benefit other users.

Islands of automation are no longer cost-beneficial Yet the process for determining and amalgamating all the new requirements from all the new users seems like a very daunting task

Top-down system engineering addresses the challenges of project initiation by forming cross-functional teams that evaluate the business and functional requirements of the information system in question These teams employ a methodology known as Use Cases, which focuses on the practical application of the information system upon deployment, rather than being limited by the designs of existing products.

The utility’s intent is to clearly define the desired requirements, leaving vendors as free as possible to come up with innovative solutions.

Development Phases

Another way to view the IntelliGrid architecture is to think of phases of development The overall process for undertaking IntelliGrid projects consists of the following phases, as illustrated in

Figure 4 x Phase 1: Executives use Business Cases to approve projects in order to meet Business

Needs Although financial needs are paramount, from a technical point of view the key requirement for executives in approving projects is that they should require all IntelliGrid

The Business Cases must address Strategic Vision issues such as security, network management, and data management It is essential for these cases to clearly outline whether these Strategic Vision issues will be included in the project and provide justification for their inclusion or exclusion.

In the process of case modeling, various aspects such as abstract data models, security issues, and network management are addressed During Phase 2, domain expert stakeholders articulate their user requirements through a formal Use Case process, allowing for a structured expression of needs that can be refined into detailed functional and performance requirements In Phase 3, project engineers take these Use Cases and develop more comprehensive functional and performance specifications Finally, Phase 4 involves project engineers and IT specialists evaluating the relevance of identified standards, technologies, and best practices to ensure alignment with the IntelliGrid framework.

Environments x Phase 5: Design Engineers develop Technical Specifications based on Strategic Vision,

Standards, Technologies, and Best Practices

Best Practices, based on Strategic Concepts, while using

Technology Independent Techniques to manage legacy systems

Links between IntelliGrid Environments and Technologies/

IntelliGrid Methodology for Planners, Project Engineers, and System Engineers

Identify Business Needs and associated IntelliGrid Environments

Review Strategic Vision based on High Level Concepts of Distributed Information

Review Tactical Approach based on Technology Independent Techniques

Use links from IntelliGrid Environments to Recommended Technologies and

Best Practices to determine which to use in the specific implementation

In fo rm ati o n a nd

D e riv ed fr om B u sin es s N ee d s

A ss es se d to M ee tB us in es s Ne ed s

Approve Projects based on Business Cases which address Strategic Vision issues

Develop Use Cases to Address Business Needs, brainstorming on new approaches and current processes

Develop Functional and IT Requirements based on all of the Use

Step 4: Project Engineers and IT Specialists

Assess Applicability to the Project of the Standards, Technologies, and Best Practices identified in the appropriate IntelliGrid Environments

Develop Technical Specifications based on Strategic Vision, Tactical Approach, & Standards

Approve Projects based on Business Cases which address Strategic Vision issues

Develop Use Cases to Address Business Needs, brainstorming on new approaches and current processes

Develop Functional and IT Requirements based on all of the Use

Step 4: Project Engineers and IT Specialists

Assess Applicability to the Project of the Standards, Technologies, and Best Practices identified in the appropriate IntelliGrid Environments

Develop Technical Specifications based on Strategic Vision, Tactical Approach, & Standards

Figure 4: Phases of the IntelliGrid Development Process

Development Streams

An alternate way to view the IntelliGrid system engineering development process is as three separate streams as shown in Figure 5

External Engagement System Design Technology Development

Figure 5: Streams of the IntelliGrid Development Process The three streams are:

The Business and Functional Assessment stream is essential for clarifying the rationale behind project investments, identifying system functions and capabilities, and determining user involvement in the information system It also addresses data source identification for required functions and the integration of organizational and technology components into a coherent architecture Additionally, it outlines the necessary systems, subsystems, and components to fulfill utility requirements, as well as the standards, technologies, and vendor solutions that will be employed to achieve project objectives This comprehensive approach enables utilities to effectively capture their Business and Functional needs.

Requirements, create a Conceptual & Reference Architecture, and perform the Trade- off Analysis and Cost/Benefit Analysis.

Various stakeholders influence a utility's operations and contribute to its regulation, including regulatory personnel, the Technology Advisory Board, industry standards, and the utility itself.

Collaboration and user groups These external stakeholders are also sources of requirements that need to be taken into account in the development of systems.

The IntelliGrid process focuses on creating specifications and technologies that facilitate interoperability among equipment from various vendors Current projects implementing these systems will engage extensively with vendors to evaluate market capabilities and ensure they meet essential interoperability standards This approach necessitates a thorough examination of the technology involved.

Technology Evaluation, along with Vendor Product Bench Testing against requirements

Final Business Case & Regulatory Application

To gain support from management and regulators for the implementation of an information system, it is essential to create a robust business case that outlines the benefits of the new system while evaluating the total costs, including both initial and ongoing expenses This high-level business case should be developed early in the process.

During the development process, the Business Needs and Functional Requirements are continuously refined to ensure that executives have the necessary information for a final go/no-go decision at deployment Additionally, some utilities may need to obtain regulatory approval at this stage.

Scope Addressed in this Specification

This Publicly Available Specification emphasizes the IntelliGrid methodology, which addresses business needs by outlining user requirements Additionally, it briefly covers strategic and tactical guidelines to demonstrate how functional requirements can be transformed into comprehensive technical specifications by project engineers and information specialists.

The IntelliGrid development process encompasses three key streams: business and functional assessment, external engagement, and technology development This specification will primarily concentrate on the requirements aspect of the business and functional assessment.

As discussed in the previous sections, the IntelliGrid Architecture development process can be described either as five phases, or as three separate streams running throughout the process

The five phases can be further simplified into:

1 A METHODOLOGY for addressing business needs through the development of user requirements that reflect all stakeholder needs This methodology includes requesting that all stakeholders describe their requirements through formal Use Case methods to ensure that the functional requirements reflect all these needs These Use

Cases also define the constraints, performance, security, and data requirements of all new applications and systems – before any implementation activities are commenced

2 Strategic and tactical GUIDELINES for meeting these functional requirements based on the Strategic Vision, Tactical Approach, and assessment of standards through “IntelliGrid Environments” These guidelines are intended to help engineers assess the applicability of the different standards for meeting the functional requirements, based on an analysis of their specific utility situations, the performance and security implications of different power system “environments”, and the capabilities of the various standards and technologies

The remainder of this document is organized according to the five phases, and discusses the steps to be executed within each phase

PHASE 1: EXECUTIVES DETERMINE BUSINESS NEEDS AND PLAN PROJECTS

Determine Business and Regulatory Drivers

It is important that all subsequent steps be driven by the business needs of the organization

Before starting a utility automation project, it is crucial to identify the specific financial challenges or regulatory compliance issues to be addressed Key considerations include the need for information sharing with other organizations, enhancing energy efficiency and reliability, exploring potential new service offerings or revenue streams, and reducing costs through the automation of previously manual processes.

Choose Projects

Within the chosen focus areas, select particular projects to be implemented; for instance, implementing a demand response program or advanced metering system would fall within the category of Consumer Participation.

Identify Candidate Technologies

Determine which international and national standards, industry agreements, best practices, and de facto standards may apply in this environment The list of applicable technologies on the

IntelliGrid Architecture web site may serve as a starting point.

Define a High-Level Business Case

Evaluate the anticipated high-level benefits and costs of the project in relation to your organization's business and regulatory objectives This initial assessment is crucial for determining the feasibility of moving forward with the project.

Refine Process for Your Organization

Evaluate the remaining steps of this process to identify those relevant to your organization and its specific project As shown in Figure 5, the project should progress through three simultaneous streams: external engagement, business and functional assessment, and technology development.

Identify Stakeholders

Identify the stakeholders within your organization and other relevant organizations impacted by the proposed project Focus on breaking down traditional silos and include groups that may not typically engage in information technology initiatives For instance, Figure 6 highlights various groups to consider, using advanced metering as a case study.

All stakeholders should be briefly informed about the project and invited to share any user requirements that may influence or be influenced by it They should be encouraged to think creatively, brainstorm future scenarios, and envision new capabilities instead of merely reiterating existing functions This innovative thinking and the development of idealized designs can significantly transform business operations and project implementation However, this process can be challenging, as it requires a shift from understanding current practices to exploring possibilities under varying conditions and technologies.

Vision & Design Systems Integration Operational Support Business

Figure 6: Potential Stakeholders and Requirements Team Structure

Establish a Project Team

After project approval by executives, the initial step is to assemble a project team comprising representatives from key stakeholders This inclusion is vital for gathering valuable functional requirements and securing buy-in from the end users While not all stakeholders need to be full-time team members, they should participate in discussions pertinent to their expertise.

Select Teams

To effectively carry out the requirements definition process, it is essential to establish cross-functional teams that comprise both technical experts and their managers This collaboration ensures that the team can accurately distinguish between genuine organizational requirements and features that are merely desirable.

The selection of the "systems architecture" or "vision and design" team is crucial, as they will lead the process, offer guidance, and develop and document business cases and architecture based on the outputs from the requirements teams.

PHASE 2: STAKEHOLDERS DEFINE USER REQUIREMENTS WITH USE CASES

Use Case Methodology

To effectively develop requirements from Use Cases, utilities should conduct a series of workshops with cross-functional teams This approach focuses on the practical application of the system upon deployment, rather than being limited by existing product designs It is essential for utilities to clearly articulate their desired requirements, allowing vendors the flexibility to propose innovative solutions.

Figure 7: The Use Case Workshop Requirements Development Process

A use case is a narrative that outlines the interactions between various actors and the steps they take to achieve a specific functional goal By analyzing the actions of these actors, a comprehensive use case documents multiple scenarios, each detailing a sequence of steps that illustrate an end-to-end process These steps define the necessary functions that the proposed systems and processes must deliver, ultimately leading to the requirements for the use case.

A use case may have many parts, but the following are the most important:

The use case aims to illustrate a specific scenario, such as "Utility remotely connects or disconnects customer." It includes a narrative that provides a brief description of the story, identifies the actors involved—such as customers, devices, or software—that communicate and have their own goals and responsibilities The use case is built on certain assumptions that may also serve as requirements Additionally, it outlines the contracts and preconditions between actors, for instance, an agreement where the customer limits demand on selected days for a lower tariff A triggering event initiates the scenario, followed by a detailed, numbered list of steps that describe the actions of each actor, the information exchanged, and the recipients of that information, such as "7 The operator sends a curtailment command to the meter."

The choice of use cases is guided by overarching project objectives and business motivations The IntelliGrid Architecture has identified a range of use cases that encompass a broad utility scope.

Project The IntelliGrid Architecture team organized the energy industry into six functional domains: x Market operations x Transmission operations x Distribution operations x Centralized generation x Distributed energy resources x Customer services

A seventh domain, known as federated systems management, encompasses technological functions like network management and security that intersect with all other domains These activities serve as a foundation for developing relevant use cases.

Use Case Workshops to Develop Requirements

This section describes the process of holding use case workshops

A Use Case outlines a series of events that illustrate how a specific system is utilized It narrates the journey of a user or group of users as they attempt to achieve a goal, highlighting both successful and unsuccessful outcomes Each Use Case may encompass various scenarios, each presenting a unique twist on the narrative while ultimately focusing on the same objective.

When identifying system requirements, challenges often arise, such as distinguishing between genuine requirements and mere wish lists, ensuring all necessary aspects are considered, and effectively organizing and tracking the compiled list of requirements.

The Use Case process emphasizes the identification of genuine requirements by focusing on the users' perspective, making it easier to discern essential needs By following a comprehensive path, it enhances confidence in capturing all necessary elements Additionally, as use cases are centered around user goals, they provide a natural framework for organization.

As each cross-functional team develops its story about the system, the team members will discover and make a list of requirements

The utility assembles the Use Case Workshop members and plans a series of Use Case workshops There are a number of industry tools that help to facilitate the development of Use

Cases The industry has standardized on a technology suite called Universal Modeling

Language (UML) to help facilitate this process

Effective use case teams should consist of internal stakeholders and actors, including both subject matter experts and decision makers Subject matter experts bring essential technical knowledge, while decision makers, typically senior managers, are responsible for policy selection Additionally, incorporating a workshop facilitator experienced in use case development and requirements gathering can enhance the process Each team should also have a designated leader to guide discussions and represent the team in system architecture meetings.

Before conducting the use case workshop, the team leader and facilitator should develop a narrative outlining the overarching goal of the use case Additionally, the facilitation team can prepare preliminary content for the workshop, which includes identifying actors and stakeholders, outlining scenario steps, and specifying discussion topics that are either included or excluded from the scope.

During the meeting, team members can utilize slides or handouts to present the preparatory materials It is essential to review and update these materials for each subsequent workshop to ensure they accurately reflect the decisions made by the use case team.

A key takeaway from previous implementations of the IntelliGrid use case process is the importance of formally orienting stakeholders in the requirements capture process The project's scale will determine the most effective way to introduce team members to the use case methodology.

A focused training session involving all project participants can be used, or the training can occur in the initial use case workshop

To ensure effective participation in use case workshops, it is essential to structure them in a way that accommodates team members with diverse backgrounds and skill sets A well-organized agenda may include reviewing and validating the use case narrative, identifying key actors and their roles, discussing relevant scenarios, setting clear goals for the workshop, establishing ground rules, and outlining the necessary steps and requirements derived from the session.

For second and following sessions…a review of outcomes of the prior session(s) and updates on any issues, action items, and parking lot items documented previously

The use case team leader sets the strategic direction for workshop sessions, while the facilitator manages the agenda and process Workshop discussions lead to proposed scenario steps, which are adopted upon general agreement, continuing until the scenario is fully developed To ensure completeness, focus on what needs to be done rather than the technology involved, maintain the primary actor's perspective to avoid usability issues, ensure the steps provide value to the actor's goals, and confirm that the scenario encompasses its beginning and reaches the intended goal.

7.2.5 Developing Requirements and Business Value

The group should assess the scenario steps to determine both functional and non-functional requirements This evaluation will also help identify potential business benefits, whether quantifiable or non-quantifiable, that arise from the scenarios outlined in the use case, and these findings should be thoroughly documented.

Identifying the qualitative business value of each requirement is crucial, as it helps articulate the benefits, such as "reducing costs by eliminating specific manual steps." These qualitative statements will play a significant role in the business case analysis during the requirements definition phase.

The outcomes of the use case workshop must be shared with team members and verified for accuracy Any questions or issues that emerge during the workshop should be resolved by the architecture team, with the responses documented in the post-workshop notes This workshop process continues until the use case is fully developed.

A requirement is an expression of a perceived need that something be accomplished or realized

Note that this definition is intended to encompass all possible requirements for a project Be aware that in the real world, a “requirement” may merely be something that someone wants

The following items help to define “What’s a Good Requirement?”

Binding x Makes it clear what is optional and what is not x Creates a “contract” with the reader

Shows Responsibility x Identifies what component must take action x Implies whose job it is to ensure it happens

Consistent in Level x Target a consistent level: customer, strategic, functional, design, test, etc x Should not “jump ahead” to the next level

Measurable x To be used later in the process to determine whether they’ve been met

Testable x So one can determine whether the requirement has been met

Good requirements are best expressed as complete sentences, in the form Subject-Verb-

Object-Qualifier One should not use “and” because such a sentence links two requirements together that may not actually be linked Some rules are listed below:

When discussing a system, it is essential to clearly identify the subject and object, ensuring they are well-defined components Avoid vague terminology like "the system" and instead specify your terms upfront If individuals are involved, assign them specific roles to enhance clarity and understanding.

LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU. x GOOD: “operator”, “administrator”, “maintenance worker” x NOT AS GOOD: “user”, or “client”

When writing instructions, use action-oriented verbs to enhance clarity and engagement Opt for binding words like "must" or "shall" to convey necessity, while "may optionally" can indicate alternatives Reserve "will" for supplementary information, such as "this will ensure that " Avoid passive voice to maintain accountability and ownership in your writing Strive for precision with strong action words like "transmit," "display," "activate," "print," "notify," and "connect." Refrain from using weak verbs such as "is," "be," "have," "contain," "process," "handle," or "support." Additionally, "permit" serves as an effective action word in user interfaces, placing responsibility on the system providing the interface.

Qualifier x Specifies constraints or performance x Must be measurable x Include a qualifier as often as you can

The system is defined by two key types of requirements: functional and non-functional Functional Requirements specify the actions the system must perform in response to events or autonomously, outlining the operations and features it provides In contrast, Non-Functional Requirements focus on the qualities the system must exhibit regarding execution and performance, often referred to as "constraints."

Use Case Analysis

The use case analysis aims to create a cohesive set of use cases for future architecture development This process should commence during the ongoing workshop sessions The architecture team is responsible for reviewing workshop outputs to assess preliminary requirements and offer feedback Additionally, they can resolve questions and issues raised by the use case teams while identifying and addressing any gaps or overlaps in scenarios among different teams.

The workshop process will generate a comprehensive list of actors and their respective roles, which must be reviewed to establish a standardized naming convention Due to the iterative nature of the workshops and varying perspectives from use case teams, duplicates, redundancies, and conflicts among actors may arise The standardization process is essential to address and resolve these inconsistencies effectively.

Activity diagrams are a graphical method to display the events occurring in a use case scenario

Utilizing this UML tool offers numerous advantages, as it visually represents use case scenarios, enhancing user comprehension of event sequences and clarifying the roles of different actors The diagram highlights areas where a textual event list may fall short in capturing potential outcomes, while also illustrating the interactions between actors, which can be effectively documented in the UML sequence diagram.

Figure 8: Example of an Activity Diagram

The interface diagram serves as a conceptual representation of data flow and sequence within a system, derived from actor interactions shown in the activity diagram During use case workshops, the architecture team can create a preliminary interface diagram to offer a high-level view, utilizing accepted design patterns and adapting to changes identified in the workshops While there is no specific UML diagram for interface diagrams, the Yourdon dataflow diagram has proven effective in past projects.

A message sequence diagram is a standard UML tool that depicts the interactions between actors in a scenario, highlighting the interfaces and the types and frequency of data exchanged It can be derived from use case scenarios or activity diagrams, and ensuring consistency among these diagrams confirms the accurate capture of use case data Additionally, documenting the messages in a spreadsheet or database helps in adding more information about the exchanges and supports the architecture team during system analysis.

Figure 10: Message Sequence Diagram Example

Use case interaction diagrams focus on the specific actors and interfaces related to each use case, serving as a refined version of the interface diagram These diagrams effectively highlight the essential components of a use case and facilitate comparisons across different use cases.

Refining requirements involves reviewing, classifying, and consolidating project needs This process should start during the use case workshop led by the architecture team, which offers valuable feedback to ensure that the generated requirements are comprehensive enough to meet project objectives.

After completing the use case workshops, the final requirements can be organized into groups for consistency checks and to eliminate any redundancies This classification can be based on system components or interfaces Additionally, non-functional requirements from various use cases may outline the same metrics but with varying performance levels The evaluation of associated costs and values will guide the determination of the required performance level It is also essential to document the assumptions made by the use case teams during this phase to ensure they are validated against other system requirements.

Throughout the workshop process, record any potential security risks of each use case In general, a security analysis will involve the following steps: x Identify what assets need to be protected

To ensure the security of assets, it is essential to identify potential threats that require protection, assess existing vulnerabilities within the system, and explore various security measures available Additionally, it is crucial to determine the most effective measures tailored to safeguard specific assets.

This stage begins the security analysis process by identifying assets, threats and vulnerabilities and recording them along with the requirements

The workshop process will identify many requirements, perhaps several hundred It will be necessary to eliminate duplicates, make wording consistent, and verify business value statements

7.3.9 Evaluate Requirements vs Business Case

During the workshop process, the business case teams evaluate each identified requirement and qualitative business value by assigning quantitative benefits and calculating complete lifecycle costs This analysis helps refine the requirements and may lead to the exclusion of certain use cases and scenarios from consideration.

Even if an organization decides not to implement certain requirements or scenarios at this stage, it is crucial for the systems architecture team to keep them in mind These elements may be integrated into future projects, so the architecture must remain adaptable to accommodate potential changes.

To benefit the industry, utilities, and potential vendors, it is essential to publish a clear list of project requirements at this stage Additionally, having these requirements evaluated by an advisory board of industry representatives, particularly from utilities not directly involved in the project, can provide valuable insights.

PHASES 3-5: TECHNOLOGY SELECTION AND DEPLOYMENT

ANNEX A: HOW TO DEVELOP USE CASES

ANNEX B: USE CASE TEMPLATE

ANNEX C: EXAMPLE OF TRANSMISSION SYNCHRO-PHASOR USE CASE

Tiêu đề	IntelliGrid Methodology for Developing Requirements for Energy Systems
Chuyên ngành	Electrical and Electronic Technologies
Thể loại	publicly available specification
Năm xuất bản	2008
Thành phố	Geneva

Định dạng
Số trang	130
Dung lượng	3,01 MB