| Excerpt |
|---|
General overview of the system architecture and functionalities |
There are the following types of clients (and services):
...
All need for specific knowledge of components in the system, e.g. physical location of pillars, must be avoided.
Specific implementation of services
In the reference implementation there have been made a choice to have a special service to take care of audit trails. This also include consideration on
- collection of alarms from any component in the system
- how alarm are mirrored in audit trails
- how relevant information from monitor service is passed
this is illustrated in the following figure:
Black arrows indicates communication via the coordination layer and the direction of the arrows indicates the way the requested information is passed. The grey arrows indicates information flow outside the coordination layer.
Note that different status from pillars e.g. ”Water level” is implemented via alarms, i.e. if agreed the pillars will send alams if the "water level" grows to high. In this way it is up to the pillar to actively give status information when necessary.
See also
| Filter by label (Content by label) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Gliffy | ||||||||
|---|---|---|---|---|---|---|---|---|
|