1 descriptions of function · communication with remote cb attached to home appliances, and ev...
Post on 19-Mar-2020
2 Views
Preview:
TRANSCRIPT
C1_Use_Case_Hawaii_Final.doc 1
HHaawwaaiiii UUssee CCaassee ##11 HHiieerraarrcchhiiccaall CCoonnttrrooll ooff DDMMSS aanndd μμDDMMSS ffoorr llooccaall llooaadd//ssuuppppllyy ccoonnttrrooll
ttoo mmiittiiggaattee ttrraannssffoorrmmeerr//sseeccoonnddaarryy ffeeeeddeerr oovveerrllooaadd,, aanndd pprreevveenntt vvoollttaaggee vviioollaattiioonnss..
1 Descriptions of Function Hierarchical control of DMS and μDMS for local load/supply control to mitigate transformer/secondary feeder overload, and prevent voltage violations.
1.1 Function Name Control algorithms of DMS and μDMS are proprietary (non-publicly available).
1.2 Brief Description This use case describes how a DMS and μDMS can cooperatively control local loads (EV, water heater, water pump, battery), and local supply (battery) to reduce mitigate transformer / secondary feeder overload, and prevent voltage violations. There are four (4) levels of control in this use case:
1. EMS that monitors and controls generation units and DMS
2. EVECC that monitors and controls EV charging in the region
3. DMS controls a Bulk battery PCS and μDMS
4. μDMS monitors and controls a Local Battery, Home Gateway
C1_Use_Case_Hawaii_Final.doc 2
There are three(3) scenarios in this use case:
1. Normal Operations This scenario shows how the system operates when there are no violations or overloads.
2. Transformer/secondary feeder overload This scenario shows how the DMS detects the possibility of a feeder overload and responds through the μDMS and Home Gateway to control the EV charger and home appliances as necessary to mitigate it.
3. Voltage violation event This scenario shows what happens when the μDMS detects the possibility of a voltage violation (over voltage condition) and responds through the μDMS and Home Gateway to control the battery to prevent voltage violations.
C1_Use_Case_Hawaii_Final.doc 3
1.3 Narrative High penetration levels of variable generation from renewable energy resources and increased variability of demand caused by EV charging can have adverse impacts on the stability of distribution systems. The operations of distributed resources (DR) may significantly impact the voltages at different locations of the Maui grid. The impact on voltage-regulating devices of the Maui grid may have a potential of creating too high voltage; voltage imbalance; intermittent operations which may result in unacceptable voltage fluctuations; or impproper regulation during reverse power flow conditions. Hierarchical control schemes can be used to cordinate DR with voltage/var control devices and mitigate voltage fluctuations. This is a System Level Use Case that describes a hierarchical control scheme in which a DMS and μDMS can cooperatively control EV, home appliances, and local battery to mitigate transformer/secondary feeder overload and prevent voltage violations caused by PV intermittency and EV charging. This use case explains operation and control strategies that use a hierarchical control scheme that includes an EMS, EVECC, DMS, µDMS, and Home Gateway. The functions and operations of each of these are described below.
EMS, DMS, µDMS, and Home Gateway Functions
EMS Functions
System that monitors/controls the real-time network; includes generation control and load forecast functions.
Monitors and controls transmission lines and substations via SCADA.
EVECC Functions
EVEMS (Energy Management System) function that makes EV charging schedules based on available capacity sent from DMS.
EVCMS (Car Management System) function that monitors EV status, such as state of charge, and sends EVs’ SOC data to DMS via EVEMS Function.
DMS Functions
Monitors and controls distribution feeders via SCADA. .
Generation/Execution of Switching Procedures that automatically generate and execute switching procedures (after confirmation by DSO).
C1_Use_Case_Hawaii_Final.doc 4
Load Forecasts that calculates load forecasts for distribution feeders or sections between switches under its control. [Note: The load of feeder or section is Gross load and includes PV output.].
Distribution Simulation System that simulates power flow for distribution feeders under its control.
Demand Response Management that controls demand-side appliances through Home Gateways.
Communications with µDMS for data exchange and to exercise cooperative control. (Exchanges data and exercises cooperative control with µDMS,)
Communications with EVECC, EMS, and MDMS for data exchange
μDMS Functions
Monitors load and voltage of LV transformer.
Controls demand-side appliances directly through Home Gateways (in cooperation with the DMS and indirectly through the EMS). (Exchanges data and exercises cooperative control with the DMS and Home Gateway.)
Home Gateway
Communication with Remote CB attached to Home appliances, and EV Normal charger to exchanges data and controls Home appliances, and EV Normal charger.
Communication with µDMS
Communication with Home Display (Customer Laptop PC or Cell phone)
Management Asset Inventory data via Home Display
C1_Use_Case_Hawaii_Final.doc 5
Scenarios In each of the scenarios in this use case, the main control functions are conducted at the operations level of the distribution utility, namely the Maui grid EMS which controls dispatchable generation resources and the DMS. The distribution network is managed and controlled each level separately, as a subsystem. The μDMS manages at the local level, controlling EV, home appliances, and local batteries. The DMS manages at the substation level, controlling the μDMS and MV section switches. Then, global optimization is performed at the Maui grid level. 1-Normal operation During normal operations, the μDMS periodically monitors (i) EVs’ SOC (State of charge) through EVECC and the DMS, (ii) AMI meter data through ΜDMS and the DMS, (iii) SOC of local battery, (iv) transformer’s secondary voltage and current, (v) PV output and Home Gateway, and (vi) Home appliance status through Home Gateway. 2-Transformer/secondary feeder overload When the μDMS detects a violation (feeder overload), the μDMS sends control signal to the local batteries, and sends load shedding signal to EV normal charger in home, and Home Appliances via Home gateway. In case that Home gateway executes any load shedding, Home gateway sends information signal to EMS via the DMS and the μDMS. Then, the light on DMS’s DASH board changes to “red light” and the operator can recognize the load shedding execution. After the μDMS confirms that the violation situation has been corrected, it sends control signals in sequence to restore normal situation. The μDMS also periodically monitors transformer’s secondary current after the execution of load shedding to calculate the amount of shed load. If the amount of shed load is not enough, the μDMS implements an additional load shedding, if possible. If the μDMS detects the current achieves a target current and remains under it for an enough period, the μDMS starts restoring operation of Home Appliances, EV normal chargers, and Local Batteries. The amount of restored load is calculated from present current and restoring target in order to prevent transformer’s secondary feeder overload again. First, the μDMS restores Home Appliances. The order of restoring power is contrary to one of shedding. Second, the μDMS restores EV normal charger in home. The order of restoring is also contrary to one of shedding. Then, the μDMS tells Local Battery to recover. Finally, the μDMS informs the DMS of completion of restoring operation. 3-Voltage violation event When the μDMS detects a voltage violation event (over-voltage situation), the μDMS reports information of Middle voltage violation to the DMS, Then, the DMS sends this information to the EMS before starting control, to ask the EMS to decide whether Middle voltage violation is the EMS’s matter or not. If it is not the EMS’s problem, the DMS sends a control signal to local battery. After that, the μDMS sends information to the DMS. Then, the DMS transfers information to the EVECC.
C1_Use_Case_Hawaii_Final.doc 6
The EVECC sends new charge schedule data to EV. The μDMS also periodically monitors transformer’s secondary voltage after control of voltage violation. If the μDMS detects the voltage achieves a target voltage and remains in the target range for an enough period, the μDMS starts restoring operation of EVs, Local Batteries. The amount of restored load is calculated from present voltage and restoring target voltage, in order to prevent transformer’s secondary feeder voltage violation again. First, the μDMS restores EVs by sending the new schedule via the DMS and EVECC. Then, the μDMS tells the Local Batteries to recover. Finally, the μDMS informs the DMS of completion of restoring operation.
C1_Use_Case_Hawaii_Final.doc 7
1.4 Actor (Stakeholder) Roles
Actor Name Actor Type (person, organization, device, system, or subsystem)
Actor Description
EV Equipment Movable equipment that has a battery. Its battery can be charged by an EV charger in home, public EV charger or quick charger. It can send its information such as “SOC” to an EVECC via an EV network operation centers.
EVECC System System that manages EVs on a regional basis. The EVECC controls quick chargers directly, and controls pubic chargers via an EVNOC. The EVECC provides information to the DMS so that the DMS can control the EV charger in home via the μDMS and Home Gateway. It also can send text messages to EV users.
EV network operation centers (EVNOC)
Subsystem EVNOC controls public EV chargers.
EMS System System that monitors and controls generation units and DMS.
DMS System System that controls bulk battery, switches devices, feeder loads, and μDMS based on input from EMS, EVECC, and MV CT PT sensors. DMS also communicates information for operator DASH board monitor to EMS.
μDMS System System at pole transformer that can manage Home Gateways and local Battery PCSs based on the following input; I. Voltage and current measured by Sensor secondary transformer (low voltage level). II. Home appliances status via Home Gateway. III. Local battery’s SOC (State of charge). It also transfers EV charger control signals from DMS to EV charger in home via
C1_Use_Case_Hawaii_Final.doc 8
Actor Name Actor Type (person, organization, device, system, or subsystem)
Actor Description
Home Gateway.
AMI meter Device Device in home that measures load, and voltage in the home. It sends data to DMS and μDMS via ΜDMS.
Asset Inventory
Subsystem Subsystem that contains inventory of equipment and facility data concerning Distribution Grid and Home Appliances.
MV (Middle Voltage) CT PT Sensor
Device Device that measures voltage and current on the feeder. It is attached to switches and communicates with DMS.
LV (Low Voltage) CT PT Sensor
Device Device that measures voltage and current on the secondary side of transformer. It is located near LV transformer. It is attached to and communicates with μDMS.
LV transformer
Device Device that transforms MV to LV.
Bulk Battery and PCS
Subsystem Subsystem that is connected to Middle-voltage feeder and can charge or discharge the power. This action can be controlled by DMS. Bulk Battery in this use case has two roles. 1) To simulate a number of EV chargers. (only for Load control = charge: 1MWh) Another is Grid Connected Battery. (charge / discharge: depend on the usage)
Local Battery and PCS
Subsystem Subsystem that is connected to low-voltage distribution line and can change or discharge power. This action can be controlled by μDMS. Local Battery in this use case has two roles: 1) To simulate a number of EV chargers. (only for Load control = charge: 1MWh) 2) Grid Connected Battery. (charge / discharge: depend on the usage)
C1_Use_Case_Hawaii_Final.doc 9
Actor Name Actor Type (person, organization, device, system, or subsystem)
Actor Description
Home Gateway
Subsystem Subsystem that manages EV charger in home,and Home Appliances based on the following input: control signal from DMS and μDMS, information on on/off status of home appliances every T1 minutes and voltage every T2 sec (T1,T2:TBD). It is connected to the μDMS and sends home appliance status information data. It has a monitor to allow customers to override controls.
EV charger in home
Device Subsystem that charges EV’s battery in home. This action can be cut by Home Gateway’s command. EV charger Type has two types (Type 1-100V, Type 2-200V).
Home Appliances
Device Equipment such as water heater, pool water purifier, etc. It can be monitored and controlled by Home Gateway.
PV (Photovoltaic generation)
Device Device that is connected to low-voltage distribution line and converts solar energy to electric and supply it to low-voltage distribution line. The PV output is variable because it depends on irradiation.
ΜDMS Subsystem Subsystem that collects and archives data from AMI meters. DMS accesses data from ΜDMS on demand in the home to monitor the results of Demand Response instructions.
Public EV charger (Type1,Type 2)
Device EV charger is located in public spaces to charge EVs at low voltage (Type 1-100V, Type 2-200V). It communicates with EVNOC and EVNOC monitors it.
Quick EV charger (Type 3)
Device EV charger is located in public spaces to charge EVs at high voltage current DC. It is controlled directly by EVECC.
EMS Subsystem EMS controls all power generation and DMS to balance system wide demand and supply within a preset frequency.
C1_Use_Case_Hawaii_Final.doc 10
Actor Name Actor Type (person, organization, device, system, or subsystem)
Actor Description
MV Section Switches
Device Equipment that allows closing and opening circuits in MV feeders and includes FTU (Field Terminal Unit) for remote control and sensing.
RTU (Remote Terminal Unit)
Device Device located at substation output on distribution side that controls circuit breakers open/close status and provides information on V and I.
Operator Person Person who operates EMS.
Customer Person Person who uses Home appliances in home.
1.5 Information exchanged
Information Object Name Information Object Description
Actual home energy consumption data
The AMI Meter monitors actual home energy consumption data periodically (every 15 minutes) and sends the data to MDMS for storage. The μDMS needs this data to discern whether control signals have led to actual energy reductions. The μDMS receives actual home energy consumption data from MDMS via DMS.
EV State of Charge (SOC) The EV continuously sends its SOC data to the EVECC via telecommunication link. The μDMS needs this data to prioritize which EV to cut or start charging at times of scarce power. The μDMS receives this data from the EVECC via DMS. The data is measured in % and total capacity.
Home Appliances configuration information
Information that indicates existence of home appliances, EV charger and PV in home. Asset inventory can register this data and manage this data. (AI→DMS→μDMS)
Local Battery State of Charge The Local Battery PCS continuously sends SOC data to the DMS via μDMS. The μDMS needs this
C1_Use_Case_Hawaii_Final.doc 11
Information Object Name Information Object Description
(SOC) data to prioritize which Local Battery to cut or start charging at times of scarce power. The data is measured in % and total capacity. (Local Battery→μDMS)
Bulk Battery State of Charge (SOC)
The Bulk Battery PCS continuously sends SOC data to the DMS via telecommunication link. The μDMS needs this data to prioritize which Bulk Battery to cut or start charging at times of scarce power. The data is measured in % and total capacity. (Bulk Battery→DMS)
Ampere & Voltage value of the secondary side of transformer
μDMS periodically gets Ampere & Voltage value from sensor of the secondary side of transformer. μDMS checks this data. If μDMS detects overload (or voltage violation), μDMS executes Battery control, and load shedding according to violation situation. (Transformer→sensor→μDMS)
Status data of Home appliances Status data of Home appliances is ON/OFF status of Home appliances’ remote switch. Home Gateway periodically sends ON/OFF status to μDMS. μDMS periodically calculates amount of controllable load shedding each house, using this ON/OFF status. (Home Appliance→Home Gateway→μDMS)
μDMS operation status information
μDMS sends status information (no violation, no load shedding, no over load) to DMS. And DMS forwards this data to EMS. EMS displays green, red, yellow green light on DASH board. EMS operator recognizes load shedding occur or not by this light. (μDMS→DMS→EMS)
Control command “discharge”. Command for requesting Battery PCS to start discharge. This command is used in case of transformer secondary feeder overload to decrease downstream of transformer. (μDMS→Local Battery PCS )
Control command “start charge” Command for requesting Battery PCS to start charge. This command is used in transformer secondary feeder voltage violation. (μDMS→Local Battery PCS)
Control command “EV charger Command for requesting EV charger to stop EV charging. This command is used in case of
C1_Use_Case_Hawaii_Final.doc 12
Information Object Name Information Object Description
cut” transformer secondary feeder overload to decrease downstream of transformer. (μDMS→Home Gateway→EV Charger In Home)
Information signal “EV charger cut”
Information for EVECC to announce EV charging to stop by μDMS or DMS. This information is used to make mail to EV users by EVECC. (μDMS→DMS→EVECC→EV Users)
Information “EV charger increase” Information for EVECC to request start of EV charging. This information is used to make a new EV charging schedule to EV by EVECC and send the schedule to EVs. (μDMS→DMS→EVECC)
New charge schedule data EV charging Schedule. This is produced by the EVECC. (EVECC→EV)
Control command “Home Appliances equipment X cut”
Command for requesting Home Gateway to cut Home appliances Xn (X1: Water Heater X2: pool water purifier X3: KKK). This command is used to execute load shedding. (μDMS→Home Gateway→Home Appliances)
Shedding information of “Home Appliances equipment X ”
Information for μDMS to announce load shedding by Home Gateway. This information is used to confirm Home appliances cutting by μDMS. (Home Gateway→μDMS)
Information signal “load shedding” Information for EMS to announce load shedding by µDMS or DMS. This information is used to change red light on DASH board. EMS operator recognizes that load shedding is taking place by this light. (µDMS→DMS→EMS)
C1_Use_Case_Hawaii_Final.doc 13
1.6 Activities/Services N/A
1.7 Contracts/Regulations
Contract/Regulation Impact of Contract/Regulation on Function
N/A
Policy
From Actor
May Shall Not
Shall Description (verb) To Actor
Provide Energy ESP Provide power on demand Customer
Constraint Type Description Applies to
N/A
C1_Use_Case_Hawaii_Final.doc 14
1.8 Definitions and Acronyms
TERM DEFINITION
Electric Power System
Facilities that deliver electric power to a load. (This may include generation units.)
Over-voltage A sort of Voltage violation on the distribution grid that is caused by PVs and EV charging.
ACRONYM
EPS Electric power system
RTU Remote Terminal Unit
DSO Distribution System Operator
EMS Energy Management System
DR Distributed resources
AI Asset Inventory
C1_Use_Case_Hawaii_Final.doc 15
2 Step by Step Analysis of Function
2.1 Steps to implement Scenario 1 – Normal Operations
2.1.1 Preconditions and Assumptions
Actor/System/Information/Contract Preconditions or Assumptions
Asset Inventory (AI) MECO must maintain asset inventory of home devices
C1_Use_Case_Hawaii_Final.doc 16
2.1.2 Steps – Name of Sequence
# Event Primary Actor Name of Process/Activity
Description of Process/Activity
Information Producer
Information Receiver
Name of Info Exchanged Additional Notes
# Triggering event? Identify the name of the event.1
What other actors are primarily responsible for the Process/Activity? Actors are defined in section1.4.
Label that would appear in a process diagram. Use action verbs when naming activity.
Describe the actions that take place in active and present tense. The step should be a descriptive noun/verb phrase that portrays an outline summary of the step. “If …Then…Else” scenarios can be captured as multiple Actions or as separate steps.
What other actors are primarily responsible for Producing the information? Actors are defined in section1.4.
What other actors are primarily responsible for Receiving the information? Actors are defined in section1.4.
(Note – May leave blank if same as Primary Actor)
Name of the information object. Information objects are defined in section 1.5
Elaborate architectural issues using attached spreadsheet. Use this column to elaborate details that aren’t captured in the spreadsheet.
1.1.1 Periodic event AMI meter sends data to MDMS every 15 minutes
AMI meter Monitor AMI data
AMI meter measures actual home energy consumption (net of PV)
AMI meter ΜDMS Measure value (WH, Voltage)
Application protocol. Cycle of periodic event is T1. T1:15min See the “Normal operation 1”
1 Note – A triggering event is not necessary if the completion of a step transitions to the next step.
C1_Use_Case_Hawaii_Final.doc 17
# Event Primary Actor Name of Process/Activity
Description of Process/Activity
Information Producer
Information Receiver
Name of Info Exchanged Additional Notes
1.1.2 ΜDMS Home energy data is sent to DMS
ΜDMS send the data to DMS
MDMS DMS Measure value (WH, Voltage)
Application protocol.
1.1.3 DMS Send the data to μDMS
Home energy data is sent to μDMS
DMS μDMS Measure value (WH, Voltage)
Application protocol.
1.2.1 Periodic event EV sends SOC to EVECC every 30 minutes
EV Monitor EVs data
EVs send SOC data to EVECC.
EV EVECC EV SOC Application protocol. See “Normal operation 2”
1.2.2 EVECC Forwarding EVs’ data to DMS
EVECC sends EVSOC data to DMS
EV DMS EV SOC Application protocol. See “Normal operation 2”
1.2.3 DMS Forwarding EVs’ data to μDMS
DMS sends EVSOC data to μDMS
EV μDMS EV SOC Application protocol. See “Normal operation 2”
1.3.1 DMS gets the data from AI
AI Data update Operator updates home appliance configuration information; AI sends new information to DMS
AI DMS Home Appliances configuration information
TBD See “Normal operation 3”
C1_Use_Case_Hawaii_Final.doc 18
# Event Primary Actor Name of Process/Activity
Description of Process/Activity
Information Producer
Information Receiver
Name of Info Exchanged Additional Notes
1.3.2 DMS Load shedding priority table creation and forwarding to μDMS
DMS (DR) receives data from AI, then create load shedding priority table and sends it to μDMS.
ditto μDMS Home Appliances configuration information
Application protocol. See “Normal operation 3”
1.4.1 Periodic event Local battery PCS sends battery SOC to μDMS every 1 minute
Local Battery PCS
Monitor battery’s SOC
μDMS gets SOC data and stores it in database.
Local Battery PCS
μDMS Local Battery SOC
Application protocol. Cycle of periodic event is T2. T2:1min See “Normal operation 4”
1.5.1 Periodic event LV CT PT sensor senses ampere & voltage value of the LV Transformer every 1 minute
LV CT PT sensor
Sense ampere & voltage value of the LV Transformer
Sensor captures ampere and voltage value of the secondary side of transformer
LV Transformer
LV CT PT sensor
Ampere & Voltage value of the LV transformer
Analog line Cycle of periodic event is T3. T3:1min See “Normal operation 5”
C1_Use_Case_Hawaii_Final.doc 19
# Event Primary Actor Name of Process/Activity
Description of Process/Activity
Information Producer
Information Receiver
Name of Info Exchanged Additional Notes
1.5.2
sensor Monitor violations
DMS captures ampere and voltage value which is measured by a sensor
sensor μDMS Ampere & Voltage value of the LV transformer
Analog line
1.6.1 Periodic event
Home Appliances
Monitor home appliances status
Home Gateway captures ON/OFF status of Home appliances’ remote switch
Home Appliances
Home Gateway
Status data of Home appliances
IEEE 802.15.4 Cycle of periodic event is T4. T4:1min See “Normal operation 6”
1.6.2 Home Gateway
Forwarding the data
Home Gateway periodically sends Status data of Home appliances
Home Gateway
μDMS Status data of Home appliances
Application protocol
1.7.1 Periodic event DMS monitors μDMS every 10 minutes
μDMS Monitor μDMS status
μDMS sends its operational status (no violation or under load shedding).
μDMS DMS μDMS operation status information
Application protocol. Cycle of periodic event is T6. T6:10min See “Normal operation 8”
C1_Use_Case_Hawaii_Final.doc 20
# Event Primary Actor Name of Process/Activity
Description of Process/Activity
Information Producer
Information Receiver
Name of Info Exchanged Additional Notes
1.7.2 DMS Report μDMS status
DMS sends operational status of μDMS to EMS; EMS displays this status on dash board.
μDMS EMS μDMS operation status information
HTTP/HTTPS DASH board on DMS DISPLAY “green light” Green: no violation red : under load shedding.
C1_Use_Case_Hawaii_Final.doc 21
2.1.3 Post-conditions and Significant Results
Actor/Activity Post-conditions Description and Results
μDMS Gets all measurement data
EMS Displays green light on DASH board.
2.1.4 Architectural Issues in Interactions N/A
C1_Use_Case_Hawaii_Final.doc 22
2.1.5 Diagrams
Fig Scenarios 1) Normal Operation 1, 2
C1_Use_Case_Hawaii_Final.doc 23
Fig Scenarios 1) Normal Operation 3, 4, 5
C1_Use_Case_Hawaii_Final.doc 24
Fig Scenarios 1) Normal Operation 6, 7
C1_Use_Case_Hawaii_Final.doc 25
2.2 Steps to implement Scenario 2 – .
Transformer/secondary feeder overload
2.2.1 Preconditions and Assumptions
Actor/System/Information/Contract Preconditions or Assumptions
μDMS μDMS gets all measurement data.
EMS EMS displays green light on DASH board.
C1_Use_Case_Hawaii_Final.doc 26
2.2.2 Steps – Name of Sequence
# Event Primary Actor Name of Process/Activity
Description of Process/Activity
Information Producer
Information Receiver
Name of Info Exchanged Additional Notes
# Triggering event? Identify the name of the event.2
What other actors are primarily responsible for the Process/Activity? Actors are defined in section1.4.
Label that would appear in a process diagram. Use action verbs when naming activity.
Describe the actions that take place in active and present tense. The step should be a descriptive noun/verb phrase that portrays an outline summary of the step. “If …Then…Else” scenarios can be captured as multiple Actions or as separate steps.
What other actors are primarily responsible for Producing the information? Actors are defined in section1.4.
What other actors are primarily responsible for Receiving the information? Actors are defined in section1.4.
(Note – May leave blank if same as Primary Actor)
Name of the information object. Information objects are defined in section 1.5
Elaborate architectural issues using attached spreadsheet. Use this column to elaborate details that aren’t captured in the spreadsheet.
2.1.0 μDMS senses Transformer / secondary feeder overload
Sensor μDMS senses Transformer / secondary feeder overload
2.1.1 μDMS senses Transformer / secondary feeder overload
μDMS Local Battery control
μDMS sends control command to Local Battery PCS.
μDMS Local Battery PCS
Control command “discharge”
Application protocol
2 Note – A triggering event is not necessary if the completion of a step transitions to the next step.
C1_Use_Case_Hawaii_Final.doc 27
# Event Primary Actor Name of Process/Activity
Description of Process/Activity
Information Producer
Information Receiver
Name of Info Exchanged Additional Notes
2.2.1 μDMS senses Transformer / secondary feeder overload
μDMS EV charger cut
μDMS sends control command to Home Gateway.
μDMS Home Gateway
Control command “EV charger cut”
Application protocol
2.2.2 Home Gateway
Cutting remote CB of EV charger in Home
Home Gateway sheds the remote CB of EV charger.
Home Gateway
EV Charger In Home
- IEEE 802.15.4
2.3.1 μDMS senses Transformer / secondary feeder overload
μDMS Sending information
μDMS sends information to DMS.
μDMS DMS Information signal “EV charger cut”
Application protocol
2.3.2 DMS Forwarding information
DMS transfers information to EVECC.
DMS EVECC Information signal “EV charger cut”
Application protocol
2.3.3 EVECC Forwarding information
EVECC sends message “EV charger cut” to EV Users.
EVECC EV User Information signal “EV charger cut”
(e-mail)
2.4.1 μDMS senses Transformer / secondary feeder overload
μDMS Execution load shedding
μDMS sends control command to Home Gateway.
μDMS Home Gateway
control command “Home Appliances equipment X cut”
Application protocol. If μDMS still detects an overload, this activity executes.
C1_Use_Case_Hawaii_Final.doc 28
# Event Primary Actor Name of Process/Activity
Description of Process/Activity
Information Producer
Information Receiver
Name of Info Exchanged Additional Notes
2.4.2 Home Gateway
Cutting remote CB of Home appliances
Home Gateway sheds the remote CB of Home appliances
Home Gateway
Home Appliances
Control command “Home Appliances equipment X cut”
IEEE 802.15.4 After 1.10) HGW Change HGW LED green to red!!
2.5.1 Home Gateway
Sending information
Home Gateway sends information to μDMS.
Home Gateway
μDMS Shedding information of “Home Appliances equipment X
Application protocol
2.5.2 μDMS Forwarding information
μDMS sends message to DMS.
μDMS DMS Information signal “load shedding”
Application protocol
2.5.3 DMS Forwarding information
DMS sends message to EMS
DMS EMS Information signal “load shedding”
HTTP/HTTPS EMS gets information; DMS displays “red light (alarm)” in DASH board.
C1_Use_Case_Hawaii_Final.doc 29
2.2.3 Post-conditions and Significant Results
Actor/Activity Post-conditions Description and Results
μDMS μDMS gets secondary feeder current which is kept within pre-set range.
2.2.4 Architectural Issues in Interactions N/A
C1_Use_Case_Hawaii_Final.doc 30
2.2.5 Diagrams
Fig Scenario 2) Transformer/secondary feeder overload
C1_Use_Case_Hawaii_Final.doc 31
2.3 Steps to implement Scenario 3 – .
Voltage violation event
2.3.1 Preconditions and Assumptions
Actor/System/Information/Contract Preconditions or Assumptions
μDMS Gets measurement data and does not detect secondary feeder overload.
EMS Displays green light on DASH board.
C1_Use_Case_Hawaii_Final.doc 32
2.3.2 Steps – Name of Sequence
# Event Primary Actor Name of Process/Activity
Description of Process/Activity
Information Producer
Information Receiver
Name of Info Exchanged Additional Notes
# Triggering event? Identify the name of the event.3
What other actors are primarily responsible for the Process/Activity? Actors are defined in section1.4.
Label that would appear in a process diagram. Use action verbs when naming activity.
Describe the actions that take place in active and present tense. The step should be a descriptive noun/verb phrase that portrays an outline summary of the step. “If …Then…Else” scenarios can be captured as multiple Actions or as separate steps.
What other actors are primarily responsible for Producing the information? Actors are defined in section1.4.
What other actors are primarily responsible for Receiving the information? Actors are defined in section1.4.
(Note – May leave blank if same as Primary Actor)
Name of the information object. Information objects are defined in section 1.5
Elaborate architectural issues using attached spreadsheet. Use this column to elaborate details that aren’t captured in the spreadsheet.
3.1.0 μDMS detects Voltage violation (over-voltage)
μDMS μDMS detects Voltage violation (over-voltage) on high voltage side.
3.1.1 μDMS Checking voltage value on secondary side of transformer
μDMS checks voltage value of secondary side of transformer. If μDMS detects over voltage on secondary side, μDMS sends information to DMS.
μDMS DMS Information “Middle voltage is high”
Application protocol
3 Note – A triggering event is not necessary if the completion of a step transitions to the next step.
C1_Use_Case_Hawaii_Final.doc 33
# Event Primary Actor Name of Process/Activity
Description of Process/Activity
Information Producer
Information Receiver
Name of Info Exchanged Additional Notes
3.1.2 DMS Forwarding information
DMS sends information to EMS
DMS EMS Information “Middle voltage is high”
HTTP/HTTPS
3.1.3 DMS Forwarding information
Checking voltage of Middle voltage violation
DMS μDMS Control command “ ”
Application protocol
3.2.1 μDMS Local Battery control
μDMS sends control command to Local Battery PCS
μDMS Local Battery PCS
Control command “start charge”
Application protocol If voltage violation still occurs, (1.3) activity are executed.
3.3.1 μDMS Sending information
μDMS sends information to DMS
μDMS DMS Information "EV charger increase"
Application protocol If voltage violation still occurs, (1.4) activity are executed.
3.3.2 DMS Forwarding information
DMS transfers information to EVECC
DMS EVECC Information "EV charger increase"
Application protocol
3.3.3 EVECC Forwarding information
EVECC sends new charge schedule data to EV
EVECC EV New charge schedule data.
Application protocol
C1_Use_Case_Hawaii_Final.doc 34
2.3.3 Post-conditions and Significant Results
Actor/Activity Post-conditions Description and Results
μDMS μDMS gets voltage which is kept within pre-set range on low voltage side.
2.3.4 Architectural Issues in Interactions N/A
C1_Use_Case_Hawaii_Final.doc 35
2.3.5 Diagrams
Fig. Scenario 3) Voltage violation event
C1_Use_Case_Hawaii_Final.doc 36
3 Auxiliary Issues
3.1 References and contacts FUTURE USE
ID Title or contact Reference or contact information
[1]
[2]
3.2 Action Item List FUTURE USE
ID Description Status
[1]
[2]
C1_Use_Case_Hawaii_Final.doc 37
3.3 Revision History
No Date Author Description
0 08-04-2011 T.Onishi Initial draft
1 08-18-2011 T.Onishi Revision for 3rd Use Case Working Group Meeting, NEDO HI Project
2 10-10- 2011 J. Reilly and T.Onishi
Final Draft – Use Case for NEDO Hawaii Project
3 12-28- 2011 T.Onishi Revision as a Generic Use Case
top related