V 0.1 - sgemfinalreport.fisgemfinalreport.fi/files/Use_Case_NSN_v012.pdf · Mervi Suni NSN Juhani Ahonen (NSN ... case must be associated with external actors that either call the

Task 6.6

SGEM Task D6.6.2

Use Case and RequirementsDocument for

Generic Microgrid Model /1, modified/·Demand Management based on criticality of load·State Resolver·MG Controller and Management System Applicability·

V 0.1.2

By: Petri Uusi-Äijö NSN (editor, mainauthor)Mervi Suni NSNJuhani Ahonen (NSN)

Last Update: 2012-02-29

Contribution &Review Credits

Reviewed 2012-02-14

Created: 2011-10-20

Distribution: SGEM II WP3

Print Date:

Version: 0.1.1

D 6.6.2

CLEEN OY Eteläranta 10, P.O. BOX 10, FI-00131 HELSINKI, FINLAND www.cleen.fi

Table of Contents

1. Preface 31.1 Purpose 31.2 Scope 3

2. Modeling Approach 42.1 Vision 42.2 Scenarios 4

2.2.1 Future Scenario 42.2.2 User Scenario 42.2.3 User Story 42.2.4 Market Scenario 5

2.3 Use Case 52.3.1 Use Case Realization 5

2.4 Summary 62.5 Glossary 6

3. System Overview 83.1 Application Scope 83.2 Interoperability 83.3 Technical Environment 8

3.3.1 How Microgrid is defined in this document 83.3.2 Demand Response Principles 9

4. Model 114.1 Use Case Model 11

4.1.1 Use Case Model 124.1.2 Actors 12

4.2 Actors 134.2.1 Primary Use Cases 17

4.3 Primary Use Cases 174.3.1 State Resolver 30

4.4 State Resolver Package 314.4.1 Demand Response 41

4.5 Demand Response 424.5.1 MG Controller and Management System Abblicability 56

4.6 MG Controller and Management System abblicability 575. Next Steps 636. References 63APPENDIX: 63

D 6.6.2


Preface1.This report is part of the results of the Finnish national research project "Smart Grid andEnergy Market" SGEM second funding period. The project has been funded by Tekes – theFinnish Funding Agency for Technology and Innovation and the project partners.

This document is compiled from the separate inputs from VTT, Vattenfall AB, TampereUniversity of Technology and Nokia Siemens Networks

Authors of this document have also co-operated with colleagues in SGEM WP1 and WP4.1especially discussing SGEM vision and privacy issues.

This document has been created and generated by using Enterprise Architect (v.9.2) modelingtool. Thus the use cases and material in this document can used as a basis for next stepmodeling, if using the same or compatible modeling tool.

Purpose1.1

Purpose of this document is to find requirements for Microgrid functions by starting fromPrimary Use Case and extract its definition towards different Use Cases and their requirements. Later on this use case documentation shall be refined to cover

more specific requirements·identify subsystems and their operations·more detailed contents of the use cases·more technical specifications serving the implementation·

Another purpose of the use cases is to serve as a communication tool between the partners torefine the next steps.

Primary Use Case used as reference model is based on Microgrid Model defined by the IEEE[1].

Scope1.2The scope of the system under study is to manage active electric resources at residentialcustomer sites and aggregating them to useful bundles for both technical and market operationpurposes. Turning on and off residential electric loads and energy sources remotely is called asDemand/Response (DR). It is a dynamic demand mechanism to manage customer consumptionof electricity in response to supply conditions.

Stakeholders for the scenarios and use cases are shown as actors of the model. An actor isactually a role, which can be played by several physical entities. Basically the systemboundaries can be defined exactly by specifying interfaces between the actors and the system.

The demo development is split into three phases, called sprints according to agile approaches.

D 6.6.2


Modeling Approach2.Our modeling approach is slightly modified from main stream use case modeling approachesand the ones used in ADDRESS and other EU projects.

The most important terms in the process of creating use cases are:

Vision·

Future Scenario·

User /Market Scenario·

Use Case·

Vision2.1Vision tells on general level in what kind of future environment from smart grid perspectivescenarios and use cases take place. Vision is created by WP1 and we use it as a background.The vision was studied and complemented in the UCEG workshop in June 2011.

Scenarios2.2

Future Scenario2.2.1Format for the future scenario documentation is totally free. Teams developing the use cases donot need to write their own future scenario.

User Scenario2.2.2User scenario(s) are the starting point for the use case modeling. User (usage) scenario isconcrete description of a very specific interaction, but one that is typically chosen for someparticular reason. I.e. they have clear scope and goal. E.g. it is important to discover, how ansuburban family uses EV in the morning.

Compared to use case the format of a user scenario is more creative, but also more freeformed. User scenarios are typically narrative versus the bulleted / numbered form of a usecase. They incorporate individual user characteristics (i.e. a persona) while outlining the tasksundertaken to achieve goals. Essentially, you tell a short story about your persona interactingwith a product.

User Story2.2.3User Story is one or two sentences in the everyday or business language that captures what theuser wants to achieve and benefit. User stories are used especially with agile softwaredevelopment methodologies (especially with SCRUM) for the basis of what features that canbe implemented. User story is one format of documenting a user scenario.

Each user story is a short text and should fit on a paper note/card. The user stories are writtentogether with SW customers and/or users. Focus in customer interviews is in functional

D 6.6.2

Trigger Action

...

The main goal with user stories is to reduce the excessive and complex requirementdocumentation i.e. requirement management. Instead of that selection of user stories areimplemented very quickly and used as a communication tool with users to verify and refine therequirements.

Market Scenario2.2.4The goal in market scenarios is to identify players, products and market potential in the certainscenario. Market scenarios can also be very personal and use real names, but typically peopleavoid using real company names.

Use Case2.3Use Case is a functional specification of the system under study. In the system model every usecase must be associated with external actors that either call the use case to occur or providenecessary external service in carrying out the requested functionality.

Use Case Realization2.3.1During system design phase use cases are refined in to use case realizations, which explain thefunctionality as sequence of interaction between the parts of the systems and external actors.Use case realizations are detailed and enlist the actors, a brief description, pre-conditions, themain flow (i.e. happy path) and any alternate flows, sub-flows and exception flows. It will alsodescribe the state of the system at the end of each flow, happy or otherwise (i.e.post-condition).

Use case realizations can be documented as diagrams (UML sequence diagram or activitydiagram) or as text, for example, like this:

User Story Format

Step n

Pre-Conditions

A Coarse Use Case Realization Documentation

A <role> I want to <goal/desire> sothat <benefit>

Step 1


requirements. SW developers can also write user stories, but then the focus is in non-functionalrequirements.

D 6.6.2

Association Technical A relationship between two or more entities.Implies a connection of some type - for exampleone entity uses the services of another, or oneentity is connected to another over a network link.

Category Definition

Class Technical A logical entity encapsulating data and behavior.A class is a template for an object - the class isthe design, the object the runtime instance.

End conditions

It is very important to keep use cases and also use case realizations technology agnostic asmuch as possible.

Summary2.4Figure below illustrates the use case development. Future scenario content is in fact defined byvision developed by WP1. All the user scenarios, stories and use cases share the same futurescenario.

The actual use case writing team starts with user scenarios and stories. Scenarios can bewritten together with customers and users. User stories must be written with users, customersor their representatives.

Use cases are documented based on user scenario and selection of user stories, which refine theuser scenario with more detailed (functional) user requirements.

Figure 1: Use Case Writing Process

Glossary2.5Quite many items are based on [2]

Component Model Technical The component model provides a detailed view ofthe various hardware and software componentsthat make up the proposed system. It shows bothwhere these components reside and how theyinter-relate with other components. Componentrequirements detail what responsibilities acomponent has to supply functionality or behaviorwithin the system.

Accounting Periods Business A defined period of time whereby performancereports may be extracted. (normally 4 weekperiods).

Exceptions


Term

D 6.6.2

Deployment Architecture

Extends Relationship Technical A relationship between two use cases in whichone use case 'extends' the behavior of another.Typically this represents optional behavior in ause case scenario - for example a user mayoptionally request a list or report at some point ina performing a business use case.

Technical A view of the proposed hardware that will makeup the new system, together with the physicalcomponents that will execute on that hardware.Includes specifications for machine, operatingsystem, network links, backup units &etc.

Includes Relationship Technical A relationship between two use cases in whichone use case 'includes' the behavior. This isindicated where there a specific business use caseswhich are used from many other places - forexample updating a train record may be part ofmany larger business processes.

A person or a company that requests An entity totransport goods on their behalf.

Customer

Use Case Technical A Use Case represents a discrete unit ofinteraction between a user (human or machine)and the system. A Use Case is a single unit ofmeaningful work; for example creating a train,modifying a train and creating orders are all UseCases.Each Use Case has a description which describesthe functionality that will be built in the proposedsystem. A Use Case may 'include' another UseCase's functionality or 'extend' another Use Casewith its own behavior.Use Cases are typically related to 'actors'. Anactor is a human or machine entity that interactswith the system to perform meaningful work.

Deployment Model Technical A model of the system as it will be physicallydeployed


Business

D 6.6.2


System Overview3.

Modeling of Microgrid is started from the Micro Source (MS) level. On that level basic idea isto keep MS and it's controller entity Micro Source Controller (MC) as self-autonomic aspossible. When Microgrid is connected to Utility Grid and other Microgrids there is need tohaggle from self-autonomic.

Application Scope3.1In the long run one specific scope in the research and development is of course Microgridcontrol itself and communication solutions needed to enable reasonable QoS. In applicationdomain sense the focus is on the customer site and its aspects:

Generic Microgrid Model [1, modified]·Demand Management based on criticality of load·State Resolver·MG Controller and Management System Applicability·

Interoperability3.2Microgrid application has several interfaces to other systems and a lot of internal interfaces. Itexploits heavily the functionality and information of the other applications and in turn servesother applications. Interoperability issues will be included here later.

Technical Environment3.3Technical environment is discussed in a separate deliverable.

How Microgrid is defined in this document3.3.1

In this document Microgrid is seen as a one area of Microsources and loads that are possible toisolate as one self organized island. Microgrid can operate parallel with utility grid also.Following picture can be one possible example how Microgrid is defined.

D 6.6.2


Circuit Breaker 1

Circuit Breaker 2

Circuit Breaker 3

Smart Switch

Utility Grid Microgrid

CHP Source Heat LoadEnergy Storage

and LoadElectricity Production

CHP Source Heat LoadEnergyStorage

Electricity Production

Local Router

Local Router

Local Router

Microgrid Central ControllerMGCC Data Transmission Bath

LAN /LON/WANWLANWired Logic2G/3G/LTE etc .

Firewall

Sectorization Relay

Sectorization Relay

Sectorization Relay

Sectorization Relay

Microsource Controller (MC)

MC MC

MC MC MC

Electric Vehicle

In picture above it can seen that also branch without Micro Sources can be a part of Microgridtopology /1, modified through/.

Demand Response Principles3.3.2

Following two figures describes how Smart Microgrid Algoritms can be used to tolerateMicrogrid Energy needs. Loads can be controlled and there is possible based on load character

D 6.6.2


also use Pre-emptive and After Generation

0

10

20

30

40

50

60

70

80

90

100

0 5 10 15 20 25 30

Teho

inde

ksi

t

Kulutus

Generointi (perinteinen)

Ostosähkön tarvePow

er

Ind

ex

Consumption

Generation (traditional)

Purchase need

Traditional Generation no Demand Response or Smart Generation in use

D 6.6.2


-80

-60

-40

-20

0

20

40

60

80

100

0 5 10 15 20 25 30

Teh

oin

de

ksi

t

Alkuperäinen kulutus

Generointi (perinteinen)

Generointi (kysynnänjousto)

Osto (+), Myynti(-)

Kysynnän jousto

Pre-emptive Generation After Generation

Original Consumption

Generation (traditional)

Generation (Demand Response)

Purchase (+), Sale (-)

Demand Response

Po

wer

Ind

ex

Generation when Demand Response or Smart Generation in use

Model4.

Use Case Model4.1

D 6.6.2


Use Case Model4.1.1

Actors4.1.2

D 6.6.2

Modified:

6.2.2012 13:56:21

Microgrid Owner (Home)

Actors4.2

Notes: The one owns the Microgrid or is a one operating Microgrid.

Actor:

Status: Proposed


Version: 1.0

D 6.6.2

Name:

Notes: Is a neighbor Microgrid owner in near location.

Unspecified

Name:

Flow/Assosiation:

Notes:

Name: Source -> Destination

Source -> Destination

Notes:

Name: Microgrid Owner (Neighbor)Association

Bi-Directional

Name: Microgrid Owner Association

Notes:

Bi-Directional

Actor: Utility Grid Owner

Notes:

Notes:

Status: Proposed Version: 1.0 Modified:

6.2.2012 13:36:47

Notes: One who owns Utility Grid infrastructure.

Flow/Assosiation:

Actor: Microgrid Owner (Neighbor)

Name: Utility Grid Owner Association Bi-Directional

Flow/Assosiation:

Notes:

Status: Proposed Version: 1.0


Modified:

6.2.2012 19:15:30

D 6.6.2

Bi-Directional

Flow/Assosiation:

Notes: Microgrids need to communicate between each other forexample in case of Power control. Other need forcommunication is that logical Microgrid is divided in separatephysical Microgrid.

Status: Proposed

Name: Microgrid Owner Association Bi-Directional

Version: 1.0

Name:

Notes:

Control Information Bi-Directional

UseCase: Neighbour Microgrid

Modified:

6.2.2012 13:56:13

Home Microgrid


6.2.2012 14:01:02

Notes:

Notes: In this document as Normal Microgrid owner but is seen as logically neighboringMicrogrid.

Flow/Assosiation:

Name:

Name: Control Information Bi-Directional

Control Information Bi-Directional

Notes:

Notes: Microgrid managed by Microgrid Owner

UseCase:

Name: Inter MicrogridCommunication

Bi-Directional

Notes:

Notes: Microgrids need to communicate between each other for

Name:


Inter MicrogridCommunication

D 6.6.2

Unspecified

UseCase: Use Case1

Notes:

Bi-Directional

UseCase: Utility Grid

Status: Proposed


6.2.2012 19:14:38

Version: 1.0 Modified:

6.2.2012 13:39:29

Notes: Utility Grid is connected to Home and Neighbour Microgrids buses. Other wordsUtility Grids sees Microgrids as Power flow absorber and producers.

example in case of Power control. Other need forcommunication is that logical Microgrid is divided in separatephysical Microgrid.

Notes:

Flow/Assosiation:

Notes:

Name: Control Information Bi-DirectionalNotes:

Name:

Flow/Assosiation:

Name: Utility Grid Owner Association Bi-DirectionalNotes:

Microgrid Owner (Neighbor)Association

Name:


D 6.6.2

Notes: This module is a part of secure arrangements. Authentication checks that Microgridoperator is authorized one.

UseCase:

Flow/Assosiation:


23.12.2011 11:37:16

Authentication and Integrity Check


Primary Use Cases4.2.1

Primary Use Cases4.3

D 6.6.2

UseCase: Branch X Circuit Breaker


2.1.2012 9:33:28


Notes:

Name: MG Home User

UseCase: Branch X Circuit Breaker

Bi-Directional


6.2.2012 16:22:00

Name:

Notes:

Notes:

Integrity Checked information flow

Name:

All Micro Sources behind the Branch CB remains functional and is able to product adnemit energy from branched area.

Proposed, Moderate stability, Medium priority:

Name: MG Neighbour Owner Use

Notes:

Bi-Directional



Notes:

Notes:

Integrity checked flow owned by Neighbor Microgrid.

Notes:


Notes:

D 6.6.2


Circuit Breaker Settings Source -> Destination

Notes:

Notes:

Name: Energy FLow Optimization Bi-DirectionalNotes: EMMs of separate Microgrids are well knowing the internal

status of Microgrids. They can balance power flows based oninformation like, initial power of each Microgrids, fuel statusof Microsources etc.

Flow/Assosiation:

UseCase:

UseCase: EMM_Home

EMM Neighbor

Notes:


13.2.2012 14:44:50

Settings for a Circuit Breaker in current Microgrid state.

Notes: Energy Management Module in home Microgrid.


Flow/Assosiation:

Modified:

6.2.2012 19:08:33

Name: Associate EMM Source -> DestinationNotes: EMM operates under MGCC control. Information flows are

logically visible for MGCC.

Notes:

Name:

Name: CHP Priorization Source -> Destination

Name:

Notes: With this flow it is possible to change Power and Heatproduction ratios.

Flow/Assosiation:

Detected Fault in Branch X



D 6.6.2

Name: Measured Voltage/Frequency Source -> Destination

Energy Flow Optimization

Notes:

Notes:

Name: MeasuredVoltage/Frequency/Load


Bi-Directional

Notes:

Name:

Name:

Name: Voltage Control Source -> Destination

Load Measuremets Source -> Destination

Notes: With this flow it can be requested MC controller Voltage stateto the required level.

Load Control Source -> Destination


Notes: Different Load Measurements can be sent to EMM.

Notes:


Name:

Name:

Notes:

Measured Voltage/Frequency Source -> Destination


Notes: This flow gives set up commands for different DemandResponse load settings.

Notes:

Notes: This flow is used to control Active/Reactive power sets ofMC.

UseCase: Electric CAR (moving vechile)

Notes:


22.2.2012 15:35:07

Name:

Notes:

Measured Voltage/Frequency Source -> Destination

Functional State information is sent to State Resolver.

This is energy balance flow control between Microgrids.

Name:


Notes:

Load Control



D 6.6.2

Notes:

Notes:

Notes:

Name: Synchronice_Connect_Load Source -> Destination

Detect reliable way if Electric Vechile is available for any needed purpose.

Notes:

Notes:


Flow/Assosiation:

Notes:

Algorith calculates, based on user parametrization, how battery is used in differentMicrogrid states.

Post-condition: Electric Vechicle can support ocassional Voltage Sag Status: Approved

State Resolver uses this information when makes decision of Microgrid optimization.

Name:

Notes: It is possible to use Electric Vechicle as a source of balancing Energy.

Load Control Source -> Destination

Notes: Vechicles battery absorbs energy from the Microgrid.

Notes:

Notes:

UseCase: Integrity Encryption (EMM)

Precondition:


29.12.2011 12:59:59

Detec if vechicle is plugged or unplugged.

Name:

Notes:

MeasuredVoltage/Frequency/Load


Status: Approved



D 6.6.2

UseCase: MC Any

Name: Energy Flow Optimization


6.2.2012 14:21:53

Bi-Directional

Name:

Notes: This is Micro Source Controller for any other type of Micro Source.

Energy FLow Optimization

Notes:

Flow/Assosiation:

This is energy balance flow control between Microgrids.

Bi-Directional

Name: Measured Voltage/Frequency Source -> DestinationNotes:

UseCase: Integrity Encryption (PCM)

Name: Synhronize Bi-Directional

Notes:

Notes:

Status: Proposed



29.12.2011 13:00:31

Notes:

EMMs of separate Microgrids are well knowing the internalstatus of Microgrids. They can balance power flows based oninformation like, initial power of each Microgrids, fuel statusof Microsources etc.

UseCase: MC Demand Response Loads

Notes:


Flow/Assosiation:

D 6.6.2

Status: Proposed

Notes: Different Load Measurements can be sent to EMM.

Name: Connect Loads

UseCase: MC Storage

Bi-Directional


13.2.2012 14:11:55

Notes: This entity controls loads of the network.

Notes:

Notes: Micro Source Controller that manages storage types of energy: capacitors, batteriesetc.

Whit this message selected demand response loads can bepicked up again.

Version: 1.0

Flow/Assosiation:Name: Measured Voltage/Frequency Source -> Destination

Name: Load Control

Notes: This flow is used to control Active/Reactive power sets ofMC.


Modified:

13.2.2012 14:12:59


Flow/Assosiation:

Notes:

Notes: In case of there is a need to bring dropped Micro Sourceback to connection this flow is giving a request for MC to dothis action. After synchronization is ready PCM is informed.

This flow gives set up commands for different DemandResponse load settings.

Name: Voltage Control Source -> DestinationNotes: With this flow it can be requested MC controller Voltage state

to the required level.

Name: Load Measuremets Source -> Destination


D 6.6.2


13.2.2012 14:12:26


Name: CHP Priorization

Notes:


UseCase:

UseCase: MGCC_Home

MC_CHP

Notes:


13.2.2012 14:10:57

With this flow it is possible to change Power and Heatproduction ratios.

Notes: Migcogrid Controlling Center. Home there refers home Microgrid controlresponses.

Notes: Micro Source Controller for Compined Heat and Power source.

Flow/Assosiation:

Name: Measured Voltage/Frequency

Name: Associate EMM Source -> Destination


Notes: EMM operates under MGCC control. Information flows arelogically visible for MGCC.

Notes:

Name: Assosiate PCM Source -> Destination

Status: Proposed

Notes: PCM operates under MGCC Control. Information flows arelogically visible for MGCC.

Flow/Assosiation:

Name: MG Home User Bi-Directional

Name: Synhronize

Notes: Integrity Checked information flow

Bi-Directional


Notes:

D 6.6.2

Notes: represent neighbor Microgrid. There can be zero to many this type of Microgriprelations. Influence between long distance Microgrids is minimal.

UseCase:

Notes:

Name: MG Neighbour Owner Use Bi-Directional

Flow/Assosiation:

Notes: Integrity checked flow owned by Neighbor Microgrid.

Status: Proposed

UseCase: MS 1 Circuit Breaker

Version: 1.0

Name:


29.12.2011 16:44:36


Notes:

Modified:

13.2.2012 14:09:50

MGCC_Neighbour

UseCase: MS in zone X Circuit Breaker

Notes:


6.2.2012 16:22:15

Notes:

Name:



D 6.6.2


6.2.2012 14:25:03


Name:

Notes: This is Protection and Safety Module in home Microgrid.

Control MS Switching

Notes:

Flow/Assosiation:

This flag is set when MC is autonomously disconnectedMicro Source from Microgrid Bus.


Name: Assosiate PCM Source -> DestinationNotes: PCM operates under MGCC Control. Information flows are

logically visible for MGCC.

UseCase: MS in zone X Circuit Breaker

Name: Circuit Breaker Settings Source -> Destination

Notes:

Notes: Settings for a Circuit Breaker in current Microgrid state.

Status: Proposed

Name: Connect Loads Bi-Directional


2.1.2012 9:56:05

Notes: Whit this message selected demand response loads can bepicked up again.

MS Switching can be managed from PCM module.

Name: Control MS Switching Source -> Destination

Notes:

Notes: MS Switching can be managed from PCM module.

Name: Detected Fault in Branch X Source -> Destination

Flow/Assosiation:

UseCase: PCM_Home

Name:


MS fault flag

D 6.6.2

This flag is set when MC is autonomously disconnectedMicro Source from Microgrid Bus.

Name: Synchronice_Connect_Load Source -> Destination

Notes:

Notes:

Name:


Relay setings Source -> Destination

Notes: In case of there is a need to bring dropped Micro Sourceback to connection this flow is giving a request for MC to dothis action. After synchronization is ready PCM is informed.

Notes: Help with this flow PMC can follow Utility Grid state andpower absorption direction. Based on this informationMicrogrid can control voltage settings and make decisions toMicrogrid State Transfers.


Notes: Relay settings in current Microgrid State.

Notes:


Name:

Notes:

Relay settings Source -> Destination

Name: Utility Grid State Source -> Destination

Name:

Name:

Notes: This flow contains information of the Utility Grid State

Notes: Relay settings in current Microgrid State.

Name: Voltage magnitude /Frequency


MS fault flag

Notes: Control Actice / Reactive Power between Microgrid andUtility Grid


Name:

UseCase: PCM_Neighbour

Smart Switch Control Bi-Directional


22.12.2011 13:50:21

Monitor Current Magnitude /Direction


Notes: With this message Smart Switch can be controlled. Forexample, if Microgrid detects un-isolated Microgrid bus faultSmart Switch can be opened to avoid short circuit currencyabsorption from Utility Grid.


Notes:

D 6.6.2

Notes:

Flow/Assosiation:

Flow/Assosiation:

Notes:

Name: Relay setings Source -> DestinationNotes: Relay settings in current Microgrid State.

UseCase: Sectorization Circuit Breaker for MS zone 1

UseCase: Sectorization Circuit Breaker MS zone 1 and X


13.2.2012 14:45:54

Notes: Sectorization is used to isolate part of the Microgrid in case of error occurs.

Status: Proposed

Functional This CB is able together with assosiated sectorication relays ore alone to isolate one toseveral Microsources as one islanded part of Microgrid.


13.2.2012 14:46:05


Name:

Notes:

Notes: Sectorization is used to isolate part of the Microgrid in case of error occurs.



D 6.6.2

Notes:



Modified:

2.1.2012 10:57:13

Notes:

Flow/Assosiation:


Notes:

Notes:

Notes:

Relay settings in current Microgrid State.

Flow/Assosiation:

Functional Smart Switch is able to make seampless separation from utility network.

Name: Monitor Current Magnitude /Direction

Bi-Directional

Notes:




Name:

UseCase:

Notes: Help with this flow PMC can follow Utility Grid state andpower absorption direction. Based on this informationMicrogrid can control voltage settings and make decisions toMicrogrid State Transfers.

Notes:

Name: Smart Switch Control Bi-Directional

Smart Switch

Notes: With this message Smart Switch can be controlled. For

Relay settings




D 6.6.2

Utility Grid State

UseCase: Utility Coupling Point

Name: Voltage Magnitude /Frequency


29.12.2011 17:27:18

Bi-Directional


Notes:

Notes:

Flow/Assosiation:

example, if Microgrid detects un-isolated Microgrid bus faultSmart Switch can be opened to avoid short circuit currencyabsorption from Utility Grid.


Bi-Directional

Notes:

Notes:

Name: Voltage magnitude /Frequency

Name: Voltage Magnitude /Frequency

Bi-Directional


This flow contains information of the Utility Grid State

Notes:

Name:

State Resolver4.3.1Component state refers to possibility to use component as load and energy source (energystorage, generator, inertia storage of the rotating machines). Previous viewpoints are givingdifferent rules to handle, different type of loads and energy sources, according to different ruleswhich are close depended on Microgrid Internal state.

Criticality classifications can be used to define how load or energy source is handled indifferent Microgrid Internal states. Criticality factors give sequential order for Microgrid

Notes: Control Actice / Reactive Power between Microgrid andUtility Grid


D 6.6.2

Black Start State

Controller how loads and energy sources are handled in case of different Microgrid InternalStates.

State Resolver Package4.4


UseCase:

D 6.6.2


Flow/Assosiation:

Notes: Microgrid is not connected to Utility Grid. It is even possible that there is notavailable energy (remain energy) to start up Microgrid. Depending on available remainenergy it can be entered back to any functional state or dead state from where it can bestarted for example manually.

Notes:


Most energy sources requires some energy to start up. This energy can be absorbed frombattery or some other source that is able to produce energy without energy involved MicroSource starting.

Version: 1.0

Notes:

Name: Black-Start-Timer Expiry Source -> Destination


Notes:

Modified:

5.1.2012 8:32:25

Functional

Name: Grid Secured Source -> Destination

Notes: In Dead State Microgrid can be started manually (energy from some external source). Onthe other hand there can be a system logic that waits until energy from non-start-energyrequired Micro Sources is available, After that EMM is started first and it still remains toDead Mode and wakes up Microgrid critical elements in predefined order.

Notes:

Microgrid is avare of available remain energy.

UseCase: Dead State


5.1.2012 8:13:43


Status: Proposed

Notes:


PCM itself requires some energy to monitor Microgrid remain energy and load condition.Also demand response changes towards reasonable Microgrid starting conditions requiresenergy. In case that all remaining energy is lost then grid is entering Dead State.

D 6.6.2

UseCase: Entity States from MCs

Flow/Assosiation:


22.2.2012 16:07:02

Notes:

Name:

Flow/Assosiation:

Black-Start-Timer Expiry Source -> Destination

Name: MC states Bi-Directional


Notes: In this state Microgrid is not containing any remain energy. It waits external energyor some Micro Source to wake it up when they bring energy to start up Microgrid.

Notes: This signal informs the status of Micro Sources, Loads andUtility Grid

Notes:

UseCase: Islandding state

Functional


19.1.2012 16:17:41

Notes:

Name:

Notes: In this mode Microgrid is operating as stand-alone -without utility network support.Own production and load of Microgrid is balanced on a level that Microgrid can operate.

Energy to Start Triggered Source -> Destination

Functional EMM monitores Microgrid ferquency

Microgrid is not abble to make blackstart, utility connection can not be supported.

Notes:


D 6.6.2

When Microgrid is eneterd to Islandind State, it will fast settling in to the operating pointwhere frequency is dropped (Micro Sources are picking up their increased propotion ofload) and Active Power of Micro Sources is increased. MC control loops can operatelocally and try to maintain allowed frequency, it may be so that Micro Sources collapses ifmaximum Active Power level is achieved. EMM can shded a loads (demand management)to support reasonable frequency and active power limits.

Name: ResolveIslanding state Signal Bi-Directional


Flow/Assosiation:

Notes:

UseCase: Maintenance Mode


4.1.2012 8:19:57

Name: Island In Maintenance

Notes: Whole Microgrid can be in Maintenance State. More sufficient scheme is that somesectorized part of Microgrid is under maintenance while rest of the Microgrid is operatingwithout interruption. It depend on maintenance are if Utility Network can be connectedwhile Maintenance Mode is utilized.

Bi-Directional

Functional Grounding for work can be done to whole Microgrid or sector of Microgrid.


Notes:


Notes:

Notes:


Name: Islanding Suport UG

Notes:

Bi-Directional

Notes:

Notes:


D 6.6.2


Flow/Assosiation:

Notes:

Name: Set Maintenance Parameters Source -> DestinationNotes:

Name: Island In Maintenance

UseCase: No own Production State

Bi-Directional

Status: Approved Version: 1.0 Modified:

4.1.2012 8:16:21


Notes:

Notes: For some reason Micro Sources of Microgrid are not able to produce any energy.Demand response principles can be utilized, but own production is zero. Power flow isfrom utility networks and possible further from neighbor Microgrid.

Functional In no own production mode Microgrid is connected to Utility Grid.

Notes:


Name: NoP In Maintenance

Notes:

Bi-Directional

Notes:


Notes:

Notes:


Name: PwU In Maintenance


Bi-Directional

D 6.6.2

Notes:

Flow/Assosiation:

Notes:

UseCase: Parallel with Utility Grid


19.1.2012 16:17:15

Notes: This is one of the most common states of the Microgrid. Microgrid is connected toUtility Network and Power flow is divided between Micro Sources and Utility Network.Power balance is dependent on how much there is own production available.

Name: NoP Suport UG

Functional EMM monitors voltage on the Utility and Microgrid side.

Bi-Directional

Notes:


Notes:

Notes: In case of voltage quality is not good enough Microgrid can be entered to Islanding State.

In case of voltage is lowering on Microgrid side, new set-point parameters are sent to MCs.

Name:


NoP In Maintenance

Notes: There is needed on-line power budget how much power can be transferred especiallytowards Utility Grid. This is basic requirement in all case when any distributed energysource is feeding Utility Grid. Utility grid capacity is limited and it is possible that someparts of Utility Grid is overloaded if energy load is towards Utility Network.

EMM can do energy balancing based on steering information. To get set-point values thereis needed communication between EMMs and Utility Grid Feeders.

Name: ResolveNo own productionSignal

Bi-Directional


Bi-Directional

D 6.6.2

Notes: This is main function to make decision into which state Microgrid can be entered. Ituses measurements and data-base values, switch position etc information to make thisdecision.

Bi-Directional

Name:

Functional Resolver calculates next possible state for Microgrid

PwU In Maintenance

Notes:


Bi-Directional

Notes: Based on measurement and switch position information Resolve Function makes decision instates that can be entered.


Name: ResolveParallel with UtilityGrid Signal

Notes: There is a need to monitor Utility Grid to make decision if energy flow between Microgridand Utility Network can be allowed )=Microgrid connected).

Bi-Directional

Precondition: MGCC need to be defined functional state. Status: Approved

Notes:

Notes:

Notes: To ensure that remain energy is available and it is safe to make any control operation.

Flow/Assosiation:Name: MC states Bi-Directional

UseCase: RESOLVE State Function

Notes: This signal informs the status of Micro Sources, Loads andUtility Grid

Flow/Assosiation:

Name: Plan ready for start-up Source -> Destination

Status: Approved

Notes:


6.2.2012 16:55:21

Name:


PwU Suport UG

D 6.6.2

Set Utility Grid Parameters Source -> Destination

Name: ResolveNo own productionSignal

Notes:

Bi-Directional

UseCase: Safe State

Name:

Notes:


11.1.2012 8:29:07

Name:

Notes: Safe State is a State where Microgrid is secured without and with remain energy.Switch are reset in their natural position - "natural position" means that switches are onposition where they are switched for example by spring force.

ResolveIslanding state Signal

Functional Relay setting in this state is preconfigured.

Name: ResolveParallel with UtilityGrid Signal


Bi-Directional

Bi-Directional

Notes: If Microgrid still can maintain Control-plane new relay settings for Black Start can beconfigured.

Resolve Black Start Signal

Notes:


Notes:

Notes: Safe state is entered always if resolve function is not able to make decision to go any otherreasonable state.

Notes:


Name: Set Maintenance Parameters

Notes: In this state switch are in their natural position where any external are not needed to keepswitch in required position.


Precondition: Microgrid can be any other available state. Status: Approved

Notes:

Notes:



Name:

D 6.6.2

Notes:


19.1.2012 16:12:22

Flow/Assosiation:

Notes: In this state Microgrid will make "forced" Diagnostic and Database Set-upparameter updates. It will trigger all possible measurements to be sure that state resolverwill get a reliable information.

Name:

Functional It is possible to make automatic dignostic check based on predefined rules and limits forrequired state.

Resolve Black Start Signal Source -> Destination


Notes:

Notes:


Notes:

Name:

Post-condition:


Microgrid is safe to drop on "Black Start State". Status: Approved

Notes: It is possible that all required Microgrid control information is not available or it is old.

Grid Secured Source -> Destination


Notes:

Notes: It is possible that all required Microgrid control information is not available or it is oldafter this state.

Notes:

UseCase:


Self Diagnostic Function

D 6.6.2

Plan ready for start-up Source -> Destination

Name:

Notes:


UseCase: Support Utility Grid Stability State

Notes:


5.1.2012 10:31:43


Notes: In this mode Microgrid used to support Utility Grid or Neighbor Microgrids tomaintain overall stability. In this state it is possible to priorize Utility Network support.This state requires that Microgrids own critical loads are supported and uncritical load canbe switched off on a need base -to achieve a power balance between utility network needand own critical load demands.

Microgrid can be seen as a available adjustable rotating reserve.

In case of Utility Grid QoS goes under allowed quality target limits Microgrid is connectedto Islanding mode. If there is several Microgrids on area there is a need to drop Microgridsvery carefully to avoid increase Utility Grid disturbance.

Flow/Assosiation:

Functional Microgrid can be used to stabilize Utility Network frequency variation.

Name: Energy to Start Triggered



Notes: PCM measures frequency from Utility side and is able to detect frequency differencescompared to allowed values. In case of frequency lowering Microgrid can do various set ofsupport actions. By increasing power production (if there is available reserve), by droppingsome non-critical loads (demand response) or by isolating itself from network, Microgridcan support utility network frequency lowering. If frequency is increasing too much onUtility side Microgrid can operate on opposite arrangements.

Notes:


Notes:


Name:

D 6.6.2

Bi-DirectionalNotes:


Name: NoP Suport UG Bi-Directional


Notes:

Notes:

Notes: This improvement is always available due to Microgrid own production which itselfimproves short circuit power requirements on local level. Actually this also decreases therequirements to strengthen Utility Grid (investment savings).

Name: PwU Suport UG Bi-DirectionalNotes:

Notes:

Flow/Assosiation:

Name: Set Utility Grid Parameters Source -> DestinationNotes:

After Utility Grid is adjusted in "first phase" on the possible voltage level there still remainstypically "phase two" system deviation of voltage which need to be removed by adjustinggenerator voltage. Microgrid can support this operation locally by adjusting its feedervoltage.

Demand Response4.4.1Electricity network contains different components that can be classified by criticality ofcomponent usage and on the other hand the state of component itself. Criticality viewpoints canbe different depending on demand of operating situation. Operating situation can be forexample MG-startup, MG going to island usage, MG return to parallel usage with main grid oreven utility (main) grid stability support etc.

PCM measures voltage from Utility side and is able to detect voltage differences comparedto allowed values Voltage sags can be suported by increasing power prod . Because voltagesag

Name:


Islanding Suport UG

D 6.6.2


Demand Response4.5

D 6.6.2


D 6.6.2


6.2.2012 14:07:57


6.2.2012 14:05:23

Notes: Loads are switched from/to underlying net on the equipment level.

Name:

Functional Equipment contains interface to remotely switch on and off


UseCase:


EMM

Notes:

Notes:

Flow/Assosiation:

Notes: This function controls energy flows inside/between Microgrids.


Name: MC Demand Response Loads

Notes:



Notes:

Notes:

Status: Proposed

Post-condition: Equipment is switched on/off Status: Approved

Flow/Assosiation:

Notes:

UseCase: Equipment Switching


D 6.6.2

Functional DRMC can control any passive load



Modified:

18.1.2012 11:30:13

MC Demand Response

Notes: DRMC can drop based it priority algorithm those

Notes: Demand Response Micro Source Controller is just one type of Microsourcecontroller. EMM and PCM do control it's functions on upper hierarchy.

Some loads like hot water boilers, floor heating or other loads which are able to maintainbig heat accumulation are loads which can be used as non-critical loads. They are likenatural energy storages for short- to middle term balancing purposes. Also chargedaccumulators are in same group until charge level is not optimal for existing MicrogridInternal Sate. When extra energy for non-critical use is available according to MicrogridController Algorithm, these big hysteresis load elements can be loaded again. In countrieswhere fireplaces are commonly used, it is natural to take this, often very long term energystorage, in to criticality calculation. It can be done for example with thermo coupleconnection or any other thermal feedback information. One important topic concerning toSmart Home Automation is of course the indication if human is presence when home loadcriticalities are calculated.

Short circuit motors can be a problem from MG startup view. It is highly dependent onsituation, motor starting appliances and motor size how to classify SC-motor criticalityalso used starting support equipments are effecting how grid do see motor. In case ofrelative big motors connected as DOL (Direct-On-Line) motors can be problem. Thisrelativity comes from motors nominal powers / starting current compared to grids nominalshort-circuit power. If DOL motor need to accelerate from zero rotation speed to nominalspeed or load speed, there is some topics need to take in account from criticality viewpoint.Motor can take 5 to 7 times its nominal currency in start phase which can cause collapsingof weak grid. DOL motor can be kept connected if it already rotates near its nominal speedand short-circuit power of the underlying grid is enough big. All previous phenomena’s doeffect how underlying grid do see the load criticality. When underlying network collapses,rotating motor is seen as generator (this means that energy stored in motor’s inertia ispushed back to grid) from grid viewpoint this gives requirements to safety automation. Invery minor viewpoint rotating inertia is seen as short term energy storage.

Sometimes MG can be used to maintain utility grid stability. Then main grid operator canoperate one of the following ways. Operator can request to off-switch non critical load butkeep rotating energy sources connected and even command extra generators (diesel) tosupport main grid stability. One possible scenario is that operator MG is commanded toisland mode then utility grid is supported by degreased load. In both case Overlay GridOperator should give compensation to MG Operator and there is needed Control Logic torespond Utility Grid Operator’s demands.

UseCase:


D 6.6.2



19.1.2012 12:53:42

Notes:


Name: No Source -> Destination

Notes:

Notes:

Process: Poll State Priorization Request

Flow/Assosiation:


19.1.2012 14:01:28

Notes: Poll until Priorisation Calculation is requested

Process: Define priority level in all possible States

Flow/Assosiation:

Name:



Notes:

Notes:

Notes:


Status: Proposed


Name:

D 6.6.2




Notes:

Notes:

Process: Receive Priorization Request

Notes:


19.1.2012 13:43:50

Process:

Notes:

Read Component Data fromatabase

Notes:

Flow/Assosiation:Name: Source -> Destination


Notes:

Modified:

19.1.2012 12:37:49

Name: Source -> DestinationNotes:

Notes:

Name:

Process: Refresf Mesurements Triggers

Name:

Flow/Assosiation:


D 6.6.2


Status: Proposed

Notes:

Name:

Process: Set Timer for next loop



19.1.2012 13:07:55

Notes:

Notes:

Notes:

Version: 1.0

Flow/Assosiation:Name: Source -> Destination

Name:

Notes:


Modified:

19.1.2012 13:06:56

Process: Take highest priority level to handle.

Flow/Assosiation:

Notes:


18.1.2012 14:22:22

Notes:

Name:


D 6.6.2

Name: No



Name:

Notes:

Notes:



Notes:

Name: No Source -> Destination

Decision: Is component measurement data available

Notes:

Notes:

Decision: Is this request from highest priority level?

Status: Proposed


18.1.2012 14:10:44


19.1.2012 12:44:06

Notes:

Flow/Assosiation:

Notes:


Flow/Assosiation:

Flow/Assosiation:


D 6.6.2


Storage: Component Data

Name:


19.1.2012 12:59:02


Notes: Component Data contains predefined information of load.

Name:

Notes:

Flow/Assosiation:

Name:

Name: Read_Component_Data Destination -> SourceNotes:

Name:

Name: Store_Component_Data Source -> Destination



Notes:

Notes:

Storage: Measurement Data

Notes:


19.1.2012 12:55:53

Notes:

Notes:

Name: No

Flow/Assosiation:

Source -> DestinationNotes:


D 6.6.2

Destination -> Source

Name: Read_Component_Data Destination -> Source

Notes:

Notes:

InputOutput: Read Component Measurement data

Name:

Flow/Assosiation:


19.1.2012 12:48:27

Notes:

InputOutput: Read Component Data from database

Flow/Assosiation:

Name:



Read_Measurement_Data

Notes:

Notes:

Notes:


Status: Proposed

Name: Read_Measurement_Data Destination -> Source

Name:

Notes:



3.2.2012 10:36:52


Notes:

D 6.6.2

Notes:

Flow/Assosiation:

Flow/Assosiation:

Status: Proposed


Version: 1.0

Name:

Notes:



Modified:

19.1.2012 13:50:43

Receive Priorization Request

Notes:

Notes:

Name: Store_Component_Data Source -> DestinationNotes:

InputOutput:

Begin: Initialize LoadmCriticality Algorithm

Store changed Component Data

Notes:


19.1.2012 13:12:44

InputOutput:

Notes:


19.1.2012 13:02:54


D 6.6.2

Flow/Assosiation:


Name:

Notes:


Name:


Notes:

Notes:



Name: MC Demand Response Loads Source -> Destination

Notes:

Name:

Notes:


Name: MC Demand Response Loads Source -> DestinationNotes:

Notes:


D 6.6.2


D 6.6.2

Flow/Assosiation:

UseCase: MIcrosource Controller (MC)


11.1.2012 11:04:41


25.1.2012 10:53:28

Notes:

Name:

UseCase: PCM


UseCase:


6.2.2012 14:04:46

MGCC

Notes:

Notes: This function manages switching and safety functions of icrogrid.

Flow/Assosiation:

Notes: Micro Grid Central Controller


Name:

Notes:


Name: MC Demand Response Loads Source -> Destination

Notes:

Status: Proposed


D 6.6.2

Modified:

6.2.2012 14:07:42

Precondition: Supply line is switched off/on Status: Approved

UseCase:

Notes:

Notes: Loads are switched to/from underlying grid on supply line level.

Supply Line Switcher

Flow/Assosiation:

Notes:


Functional Supply line is equipped with switching coupler.

Notes:



Notes:

Status: Proposed

MG Controller and Management System Abblicability4.5.1MG Controiller and Management system need to be available on a wide range of Microgrids.Controller and Management system with generic configuration will support several types ofMicrogrids setups.

Version: 1.0

Notes:


D 6.6.2

Modified:

3.2.2012 11:26:49

Microgrid Operator

MG Controller and Management System abblicability4.6

Notes:

Actor:

Status: Proposed


Version: 1.0

D 6.6.2

Flow/Assosiation:

Notes:

Actor: Microgrid operator (Field Engineer)

UseCase: External Configuration function

Name:


6.2.2012 11:27:53

Status: Proposed

Notes:


6.2.2012 13:31:00

Flow/Assosiation:

Unspecified

Name: Added Measurement data Source -> Destination

Notes: One who operates with field instruments and configures components on the physicallevel.

Notes: It is possible to set up external measurement equipments likespeed meters, torque meters, state switch etc. Thisinformation is possible to handle this function and it makesPassive component as Semi Active Component.


Notes:

Flow/Assosiation:

Notes:

Name: Added Measurement data Source -> DestinationNotes:

Name: Component Info (HandTerminal)

Bi-Directional


D 6.6.2


UseCase: MGCC Ablicability management

Notes: When topology of Database is requested MGCC can pre-process data to requested format.It is also possible to requested data without pre-processing if requester want to do it itself.

Name:

Flow/Assosiation:

Status: Proposed

Name: Unspecified


6.2.2012 11:17:06

Notes:

Name: Signal Conversion

Name: Set Parameters Bi-Directional

Notes: Centralized Migrogrid management part is a central part to manageAblicability/asset content of Microgrid.

Notes:

Bi-Directional

Name: Set/Confirm parameters Bi-Directional

Set/Confirm Parameters

Functional

Notes:

MGCC contains interface towards topology view.

Notes:

Name: Set/Confirm Parameters Bi-Directional

Notes:

Notes:


Possible communication in case of protocol conversionneeds.

UseCase: Microgrid Component 2 Passive (with External Configuration function)

Notes:


Network topology on component level can be asked from MGCC. MGCC can keeptopology in its own memory as well request information from components and MicrogridDatabase.

Bi-Directional


D 6.6.2

Manual configuration Unspecified

Notes: It is possible to set up external measurement equipments likespeed meters, torque meters, state switch etc. Thisinformation is possible to handle this function and it makesPassive component as Semi Active Component.

Notes: If component do not support Auto-configuration function it ispossible to define component's parameters with manually.

Flow/Assosiation:

Name: Modified Component Info Source -> Destination

Name:

Notes:

Autoconfigure Unspecified

Name: Signal Conversion Bi-Directional

Notes:

Notes: Possible communication in case of protocol conversionneeds.

Notes: Microgrid components can support autoconfiguration. Withthis relation components can make automatic initializationand later parameter change operations. MGCC supports thiswith "Set parameter" flow.

UseCase: Microgrid Component Active (Own Configuration function)

6.2.2012 11:22:50


6.2.2012 11:22:26

Name:

Name:

Notes: Active component contains own or external configuration management function.

Component Info Source -> Destination

Functional Own Configuration management function

Added Measurement data Source -> Destination


Notes:

Notes: This function is build in component. Component is using a plug-and-play type ofphilosophy.


Name:

D 6.6.2

Autoconfigure

Name: Set/Confirm parameters Bi-Directional

Unspecified

Name:

Notes:

Added Measurement data

Notes:

UseCase: Microgrid Component n Passive

Microgrid components can support autoconfiguration. Withthis relation components can make automatic initializationand later parameter change operations. MGCC supports thiswith "Set parameter" flow.



6.2.2012 13:27:09

Notes: This component is manually Configured to part of Microgrid. Static data for thiscomponent is stored manually to Database.

Name: Component Info

Flow/Assosiation:



Notes:

Notes:

Notes:

Name: Manual configuration UnspecifiedNotes: If component do not support Auto-configuration function it is

possible to define component's parameters with manually.

Name: Modified Component Info

UseCase: Microgrid Database



6.2.2012 11:09:48

Flow/Assosiation:

Notes:

Name:


D 6.6.2

Name: Component Info Source -> Destination


Notes:

Name: Component Info (HandTerminal)

Bi-Directional

Notes: This structure contains different values for component managing and controlling. Valuescan be, for example, characteristic values, state information, measurement data, componentinstallation time, component maintenance time, component expected replacement time etc.

Notes:



Notes: This database do contain component information. This information can be related tocomponent behavior in case of different Microgrid operational states. Also componentnominal values are written to database structure.

Flow/Assosiation:

Notes:


Functional

Notes:

Notes:

Name: Component Info

Name: Set Parameters Bi-Directional


There is unique ID for each component installed to Microgrid. Also Unique Microgrididentification is added as prefix for component to ensure that it is possible to dig outcomponent over several Microgrids.

Notes:

Microgrid Database contains Equipment ID

Notes:


D 6.6.2


Next Steps5.The work continues by collecting and considering the comments to this document version.

In defined task sense requirement specification work starts immediately.

References6.[1] Microgrids and Active Distribution Networks, S. Chowdhury, S.P.

Chowdhury and P.Crossley, ISBN 978-1-84918-014-5

[2] FI.ICT-2011-285135, FINSENY Glossary of Terms v.1

APPENDIX:

Documents

V 0.1 - sgemfinalreport.fisgemfinalreport.fi/files/Use_Case_NSN_v012.pdf · Mervi Suni NSN Juhani Ahonen (NSN ... case must be associated with external actors that either call the