... | ... | @@ -55,13 +55,13 @@ To emulate the intended behavior, the Orchestrator (`O(0)`) sends a request (`rp |
|
|
```
|
|
|
|
|
|
The arrows define the relations between events:
|
|
|
For example, the relations below represent the flow of the process,
|
|
|
so, when the `O(0)` requests the production forecasts of the prosumers, they are mandatory to generate their production forecast (by execution of the event gpf_0), then the `O(0)` needs to update the energy accounting
|
|
|
due to the milestone and include relation. After the execution of the `acc`, the event is excluded.
|
|
|
```ruby
|
|
|
rpf *--> gpf_0
|
|
|
rpf *--> acc
|
|
|
gpf0 --><> acc
|
|
|
gpf0 -->+ acc
|
|
|
acc -->% acc
|
|
|
``` |
|
|
\ No newline at end of file |
|
|
```
|
|
|
For example, the relations below represent the flow of the process,
|
|
|
so, when the `O(0)` requests the production forecasts of the prosumers, they are mandatory to generate their production forecast (by execution of the event gpf_0) due to the response relation (*-->), then the `O(0)` needs to update the energy accounting
|
|
|
due to the milestone and include relation (--><> , -->+). After the execution of the `acc`, the event is excluded (-->%). |