5. ARCHITECTURE MODEL DESCRIPTION
5.1 DSO Flexibility
The main target of the use case is to improve power quality in the network with the use of flexibility that the Prosumer possesses. The Aggregator, Flexibility Market Operator (FMO) and Service Provider supply services that support realization of the main func- tionality. Figure 47 displays the DSO Flexibility use case diagram. The DSO Flexibility use case is a HLUC and it invokes Primary Use Cases (PUC), for example the Microgrid Monitoring use case. Table 7 presents descriptions for logical actors.
Figure 47. DSO Flexibility use case diagram. uc DSO Flexibility
DSO Flexibility
«High Level U...
DSO Flexibility «Primary Use... Microgrid Monitoring «Logical Actor» MGMS «Logical Actor» AMS «Logical Actor» DMS «Logical Actor» CEMS «Logical Actor» SPP «Logical Actor» FMP «Primary Use ... State Forecast «Primary Use C... State Optimization «Primary Us... Weather Forecast
«Primary Use Case»
Flexibility Market Price Forecast «Primary Use C... Market Operations «Primary Us... Flexibility Management
«Primary Use Case»
Schedule & Dispatch
«Primary Use Case»
Offer Ranking «Primary Use... State Estimation «Primary Us... Verification «Primary Us... Data Acquisition «invokes» «invokes» «invokes» «invokes» «invokes» «invokes» «invokes» «invokes» «invokes» «invokes» «invokes» «invokes»
The Microgrid Monitoring takes care of delivering measurements, operation plans and notifications to Microgrid Management System (MGMS) level for utilization in other PUCs. In addition, the Microgrid Monitoring use case clarifies communication methods and order of operations needed for execution in the DSO Flexibility use case. Other PUCs provide functionalities needed in course of the DSO Flexibility and their detailed exami- nation are out of scope of this thesis.
Table 7. Logical actor descriptions.
Actor Type Description
Intelligent Electronic Device (IED)
Device A microprocessor-based controller, smart meter or gen- eral device for control & monitoring.
Customer Energy Management System (CEMS)
IT System A generic information system for monitoring and control of customer side's flexible resources that optimizes their consumption and generation portfolios to sell this flexibil- ity to upwards stakeholders.
Service Provider Platform (SPP)
IT System A system that provides the forecasts of weather and prices of flexibility market.
Aggregator Manage- ment System (AMS)
IT System A system that acquires and processes flexibility infor- mation of Microgrids and other controllable resources on different time-scales to propose flexibility services on markets or to upwards actors and provide the manage- ment of such services.
MicroGrid Manage- ment System (MGMS)
IT System A system that aggregates and processes technical infor- mation about Microgrid for different time periods to opti- mize scheduling of its resources in order to guarantee quality of supply as well as to allow maximum participa- tion of Microgrid's resources in flexibility services. Flexibility Market
Platform (FMP)
IT System A system for trading of flexibility between Aggregators and other market actors.
Distribution Manage- ment System (DMS)
IT System A collection of applications within the system designed to use Microgrids' flexibility for the support of the quality of supply of distribution network.
5.1.1 Business layer
The Aggregator acts as medium between the FMO and actors providing flexibility simi- larly to the DREAM and IDE4L architectures. The FMO links the Aggregator and DSO as in the IDE4L. Furthermore, the Microgrid Operator (MO) manages certain part of Prosumers network. Figure 48 presents business use case overview for the analyzed use cases. Moreover, the figure illustrates business actors, business cases, business goals, use cases and relations between them.
By utilizing flexibility, the DSO may improve power quality, performance indexes and efficiency in distribution network, thus benefiting economically. Furthermore, by utiliz-
ing flexibility the DSO may have access to local control indirectly as it may send com- mands to other actors systems. The Aggregator may do business by providing flexibility and promote green choices and efficiency. By providing flexibility, the Prosumer may decrease payback time of equipment, have access to energy market and reduce carbon footprint. Additionally, the MO, Service Provider and FMO may provide services that support use of flexibility and/or expand their businesses.
Figure 48. DSO Flexibility business case overview.
Business Use Cases (BUC) Flexibility Services of Microgrids and Network Management accommodates motives and business goals for cooperation for different actors. HLUC Flexibility management of Microgrids, which is superior to similar use cases as the DSO Flexibility, invokes the DSO Flexibility as shown in the figure. The Aggregator and MO have a contract so the Aggregator offers products that the MO possesses and both benefit in terms of money. The MO can be a company or a housing condominium, for example, or any party equivalent to them who has electrical equipment interconnected to the system and they are managing the equipment. In case the Prosumer has required capability, it can take on roles of the MO and Aggregator. Figure 49 illustrates the business layer for the use cases.
uc Business Case Analysis
Business Case Overview
Improve quality of electricity and optimize costs
Provide flexibility aggregation services and maximize profit
«Business Actor»
DSO
«Business Actor»
Aggregator
«High Level Use Case»
Flexibility management of Microgrids «Business Use... Flexibility Services of Microgrids «Business Actor» Microgrid Operator «Business Use ... Network Management
«High Level Use Case»
DSO Flexibility «Business Actor» Flexibility Market Operator «Business Actor» Service Provider «Business Actor» Prosumer Expand business by providing different forecast services and maximize profit
Maximize available flexibility. Minimize Microgrid costs and decrease payback time of Microgrid.
Optimize energy costs and decrease payback time of DER Provide flexibility market services and maximize profit Flexibility contract «invokes» Service contract «invokes» «invokes»
Figure 49. The business layer.
As shown in the figure, the FMO business actor sits on the Distribution domain since only flexibility market for DSO is considered. Similarly, the Service Provider business actor is located in the DER domain and market zone because it provides local weather and flexibility price forecasts.
5.1.2 Function layer
The DSO Flexibility use case and all of the PUCs on the function layer locate on the function layer as Figure 50 illustrates. Furthermore, red lines indicate function interrela- tion. Positions for Market Operations, Data Acquisition, State Optimization and Schedule & Dispatch are same as in similar functions from the IDE4L function layer. Moreover, positions for State Estimation and State Forecast are same as in the IDE4L. Function positioning especially promotes decentralized data acquisition and control instead of tra- ditional decentralized data acquisition and centralized control. However, it is not a re- quirement.
Generation Transmission Distribution DER Customer Premise
Market Enterprise Operation Station Field Process
«Business Use Case»
Network Management
Improve quality of electricity and optimize costs Provide flexibility aggregation services and maximize profit «Business Actor» DSO «Business Actor» Aggregator
«High Level Use C...
Flexibility management of
Microgrids
«Business Use Case»
Flexibility Services of Microgrids
«Business Actor»
Microgrid Operator
«High Level Use...
DSO Flexibility «Business Actor» Flexibility Market Operator «Business Actor» Prosumer
Maximize available flexibility. Minimize Microgrid costs and decrease payback time of Microgrid.
Optimize energy costs and decrease payback time of DER Provide flexibility market
services and maximize profit
«Business Actor»
Service Provider Expand business by providing different forecast services and maximize profit
«invokes»
«invokes» «invokes»
Figure 50. The function layer.
As shown in the figure, the Flexibility Market Price and Weather Forecasts use cases locate in Market/Enterprise zone as the SPP manages both of them. The Offer Ranking and Verification locate on the Market and Operation/Enterprise zones as FMP and DMS invoke them. Additionally, the Flexibility Management and Microgrid Monitoring use cases locate on border of several zones and connect various equipment in multiple do- mains.
The Microgrid Monitoring takes care of delivering measurements, operation plans and notifications to MGMS level for utilization. Data Acquisition provides measurements and states to DMS with DSOs own equipment. The Market Operations enables interaction between the DMS, AMS and FMP. Moreover, it covers participation to different markets, for example Day Ahead and Intraday markets. The Offer Ranking in the FMP organizes offered flexibility and ensures cost-effective use of offered power. With the State Opti- mization, the DSO defines required amount of flexibility. The Flexibility Management utilizes different forecasts, covers optimization tasks to calculate flexibility offers for dif- ferent markets, and schedules resources when offers are accepted. The Flexibility Market Price, Weather and State Forecast and Schedule & Dispatch to some extent, provide esti- mations so other use cases may utilize them and allow more consistent and efficient op- eration of the grid. The State Estimation provides information when to activate flexibility
Generation Transmission Distribution DER Customer Premise
Market Enterprise Operation Station Field Process
«High Level Use Case»
DSO Flexibility «Logical Actor» CEMS «Logical Actor» AMS «Logical Actor» DMS «Logical Actor» FMP «Logical Actor» MGMS «Logical Actor» SPP «Primary ... Microgrid Monitoring «Prima... Market Operations «Primar... Offer Ranking «Primary... State Forecast «Primary... State Optimization «Primary ... Verification «Primary... State Estimation «Primary ... Flexibility Management «Pri... Weather Forecast «Primary Use... Flexibility Market Price Forecast «Primar... Schedule & Dispatch «Logical Actor» IED «Primary... Data Acquisition
products. The Verification confirms that purchased product was activated and may be utilized for commercial purposes too. Appendix 7 presents sequence diagrams with in- formation objects (IO) for the DSO Flexibility and Microgrid Monitoring use cases.
5.1.3 Component layer
Before forming the component layer and placing logical actors’ hardware on it, an actor mapping model needs to be done. The actor mapping model presents relations between the business actors, logical actors, software and hardware components. Figure 51 presents the actor mapping model for logical actors.
Figure 51. Actor mapping model.
As shown in the figure, all logical actors with software components have their own and SGTP related software. Moreover, relations between DMS, SAU Computer and IED are simplified in comparison to the IDE4L project.
Before placing components on the information and communication layers and presenting ICT architecture, a more practical presentation with component layer is dealt with. Com- ponents of the MultiPower laboratory test setup and other actors’ components for the DSO Flexibility use case locate on the component layer as Figure 52 displays. Blue and red line indicate ICT and electrical connection, respectively. In addition, the Actuator represents a circuit breaker that the IED manages in the MultiPower.
deployment Actor Mapping Model
Actor Mapping Model
«Logical Actor»
AMS
«Logical Actor»
DMS «Logical Actor»FMP
«Logical Actor»
IED «Logical Actor»MGMS
«Logical Actor» SPP DMS FMP SPP AMS MGMS IED Sensor
ACT
Actuator SW SGTP Software SW SPP Software SW AMS Software SW FMP Software SW DMS Software «Business Actor» DSO «Business Actor» Aggregator «Business Actor» Flexibility Market Operator «Business Actor» Microgrid Operator «Business Actor» Prosumer «Business Actor» Service Provider «Logical Actor» CEMS CEMS DER:IED MG:IED D:IED SAU Computer «trace» «use» «trace» «use» «trace» «hosts» «use» «use» «hosts» «trace» «use» «hosts» «trace» «trace» «hosts» «trace» «hosts» «trace» «trace» «hosts» «hosts» «hosts» «trace» «hosts» «use» «trace»Figure 52. The component layer.
The present equipment test setup in the MultiPower conveys measurements and statuses from IEDs to MGMS level every time they are updated. Furthermore, the system conveys messages further from MGMS level after chosen period of time, certain activity or on request. With this setup the MGMS first stores information to in-memory and later dumps it to disk if one of the time and number of key changes conditions are true. All other equipment locate on different laboratories and pilot sites all over Finland except FMP.
5.1.4 Information layer
The IOs shifting between the logical actors hardware go as Figure 53 and Table 8 pre- sents. Furthermore, not all of the IOs refer to actual message types since some of them are clustered for illustration purposes. Downstream from the MGMS level, content of information flows depend on features of devices. Blue and black lines (solid) indicate
Generation Transmission Distribution DER Customer Premise
Market Enterprise Operation Station Field Process DSO Flexibility Use Case
ACT
Components: : Actuator AMS DMS FMP IED MGMS Sensor SPP MV Network MV/LV Transformer LV LV Network LAN2 Internet D:IED SAU Computer LANinformation flow and association, respectively. In comparison to the IDE4L, now the MGMS operates between the AMS and CEMS instead of direct information exchange.
Figure 53. The information layer.
The figure displays IOs in a situation where MGMS sends flexibility information to the AMS, who then decides commercial aspects for the flexibility offer and offers it to suita- ble market. Therefore, with this situation the MGMS does not need price forecast from the SPP. Other option is that MGMS receives price forecast and resolves commercial aspects completely itself and then delivers flexibility information to the AMS or to the market directly. In other words, these matters highly depend on features and connections of devices and choices of the Prosumer.
Table 8. Information object descriptions. Information object Description
Measurements Current and voltage measurements Apparent, active and reactive power Power factor
Circuit breaker state Control Signals Control signal
Setpoint
Operation Plan Load/generation schedule for certain period of time Flexibility Offer Id, flexibility type, power, start time and stop time Offer Offer Id, flexibility type, power, start time, stop time, price
class Business Context View
Generation Transmission Distribution DER Customer Premise
Market Enterprise Operation Station Field Process Business Context AMS CEMS DMS FMP IED MGMS SPP <<Information Object>> Reserve Notification <<Information Object>> Offer List <<Information Object>> Activation Notification <<Information Object>> Verification Notification <<Information Object>> Weather Forecast <<Information Object>> Reserve Notification <<Information Object>>
Activation Notification <<Information Object>> Operation Plan <<Information Object>> Measurements <<Information Object>> Measurements <<Information Object>> Control Signals <<Information Object>> Reserve Notification <<Information Object>> Activation Notification <<Information Object>> Flexibility <<Information Object>> Verification Notification <<Information Object>>
Flexibility Market Price Forecast
<<Information Object>>
Reserve Notification
<<Information Object>> Offer <<Information Object>> Bid
DER:IED MG:IED
D:IED <<Information Object>>
Offer List Offer list. Location and price dependent
Bid Offer Id, flexibility type, power, start time, stop time, price Weather Forecast Weather forecast for certain period of time
Reserve Notification Offer Id, flexibility type, power setpoint, start time, stop time, price. Reserve notification that is provided after market clearance Activation Notification Offer Id, flexibility type, power setpoint, start time, stop time. Acti-
vation notification that is provided when DSO activates product Verification Notification Offer Id, current power setpoint. Verification notification that is pro-
vided after MGMS activates product Flexibility Market Price
Forecast
Flexibility price forecast for certain period of time
The Measurements and Control Signals IOs group different measurements, states, differ- ent control signals and setpoints, respectively. Moreover, since the SGTP uses semantic messages there is no need to separate between different message types, for example for phase and line-to-line voltage measurements, since it can be done with reference to an ontology. Figure 54 illustrates standard mapping on the information layer.
Figure 54. Standard mapping on the information layer.
deployment Standard Mapping
Generation Transmission Distribution DER Customer Premise
Market Enterprise Operation Station Field Process AMS DMS FMP MGMS SPP CEMS IED MG:IED DER:IED
«Data Model Standard» CIM XML, SmartAPI &
QUDT ontologies
«Data Model Standard» IEC 61850 «Data Model Standard»
IEC 60870-5-101 «Data Model Standard»
IEC 62056
5.1.5 Communication layer
Figure 55 illustrates the communication protocols between the logical actors. The SGTP uses the MQTT and HTTP in general and for connections from the field protocol is cor- respondent to purpose of equipment use, similarly as in the SEAS architecture. In this case, downstream from the MGMS level communication protocol is IEC 61850 MMS, IEC 60870-5-104 or DLMS/COSEM.
Figure 55. The communication layer.
As shown in the figure, communication protocol depends on features of the devices down- stream from the MGMS level. The protocols are similar when compared to the IDE4L project. Furthermore, both MQTT and HTTP are presented as options upstream from the MGMS level now, instead of options in the IDE4L and DREAM (XMPP) projects that partly dictate format for messages. In addition, the MGMS and CEMS can be compared to GM in the SEAS architecture. As a result, the communication architecture hides legacy systems and provides flexible communication path with use of semantic data.
sd SGAM Communication Layer
Generation Transmission Distribution DER Customer Premise
Market Enterprise Operation Station Field Process Comm. Layer AMS CEMS DMS FMP IED MGMS SPP Protocol: MQTT/HTTP Protocol: MQTT/HTTP Protocol: IEC 61850 MMS/ IEC 60870-5-104/ DLMS/COSEM MG:IED DER:IED
6. MULTIPOWER IMPLEMENTATION
This chapter presents integration task and initial test set-up in the MultiPower laboratory environment. Furthermore, this chapter provides detailed description of configuration, programming and testing activities. Development of the SGTP and its actors operations are out of the scope generally and they are utilized as they are. However, some additions were made in order to carry out tests. Figure 56 highlights the integration problem (in orange), test set-up in the MultiPower laboratory environment and parts of the SGTP (purple).
Figure 56. Test set-up and integration task (highlighted with orange triple line) within the MultiPower laboratory environment and SGTP (highlighted with purple).
As shown in the figure, the COM600 is connected to NCC via IEC 60870-5-104 client. Moreover, here the NCC is not any kind of control center and it is illustrated just to indi- cate link with the COM600 material. The REF615s, COM600 and Computer represents the IED and MGMS, respectively, when comparing to components in the Figure 52.
6.1 Configuration
This chapter presents configurations that were made to the computer in the MultiPower laboratory and for another computer that represents the AMS in testing.
Chosen language for testing was Python programming language. To run test scripts on the computer in the MultiPower laboratory, installing several programs on the computer was necessary. Therefore, Python release 2.7.14, Windows x86-64 version, was down- loaded and installed on the computer [78]. The installer takes care of adding correct path
to environment variables path, if that is selected during the installation. Execution of py- thon command in command prompt confirms proper installation of the Python, as it returns the release number of the Python amongst other things.
Next, newest Microsoft Visual C++ Compiler for Python 2.7 (version 9.0.0.30729) in- staller was downloaded and the compiler was installed [79]. A package management sys- tem called pip was used to install rest of the things tests require. Moreover, the Python installer installed the pip as part of the Python installation. The pip downloaded and in- stalled the SmartAPI to the computer, when current folder is C:\Python27\Scripts\ with the command prompt and it executes following command: