## 4 The Concept Alignment Example Setup and Modeling
### CAE-ATG Control Events and Interconnection Model
#### 4.3.2 Fire Station CS block  
The fire station communicates with the environment with two ports. Port _pDistrict_ encapsulates the interactions with the district; port _ffm_ with multiplicity 3 allows the dispatch of the commands from the district to the three firefighting machines. The exchanged events are summarized in Table 2.  
\begin{table}
\begin{tabular}{c c c c} \hline \hline  & \multicolumn{3}{c}{**District Block**} \\ \hline  & \multicolumn{2}{c}{**Event**} & \\ \hline
**Name** & **Send/Received** & **Description** & **Destination/Source Block** \\ \hline _heOnFire_ & Received & Notification of the presence of fire. & None \\ \hline _evEst_ & Received & Notification of ceased fire alarm. & Firefighting machine \\ \hline _evOnFire_ & Sent &
\begin{tabular}{c} Alarm signal emitted in case of fire presence (_heOnFire_ event). \\ The event represents the request of a firefighting machine from \\ the district to the fire station. \\ \end{tabular} & Fire station \\ \hline \hline \end{tabular}
\end{table}
Table 1: Events list of the district CS block with event name, direction (send/received), description, and its destination/source block.  
\begin{table}
\begin{tabular}{c c c c} \hline \hline  & \multicolumn{3}{c}{**Fire Station Block**} \\ \hline  & \multicolumn{2}{c}{**Event**} & \\ \hline
**Name** & **Send/Received** & **Description** & **Destination/Source Block** \\ \hline _evOnFire_ & Received & The event models the notification of the presence of the fire in the district. & District \\ \hline _ev_Go & Sent & \begin{tabular}{c} The event models the dispatch command sent to the first available \\ machine when a fire event has been notified. \\ \end{tabular} & \begin{tabular}{c} Firefighting machine 1 \\ Firefighting machine 2 \\ Firefighting machine 3 \\ Firefighting machine 3 \\ \end{tabular} \\ \hline _evCarReturnal_ & Received & \begin{tabular}{c} The event is received when a firefighting machine returns after a fire \\ has been extinguished. \\ \end{tabular} & \begin{tabular}{c} Firefighting machine 1 \\ Firefighting machine 2 \\ Firefighting machine 3 \\ \end{tabular} \\ \hline _fiComm_ & Received & \
\begin{tabular}{c} The event models a possible fault in the communication infrastructure \\ of the fire station. \\ \end{tabular} & None \\ \hline _restoreComm_ & Received &
\begin{tabular}{c} The event models a restore event following a fault of the \\ communication infrastructure. \\ \end{tabular} & None \\ \hline \hline \end{tabular}
\end{table}
Table 2: Events list of the fire station CS block with event name, direction (send/received), description, and its destination/source block.  
Events _evOnFire_, _evGo_, and _evCarReturned_ model the messages exchanged by the fire station as part of the control loop. Events _fnComm_ and _restoreComm_ model the presence of faults. The failure of communication (_faComm_) is a \"random\" transient fault that affects the capability of the fire station to effectively respond to an alarm: when present, the system moves to a \"degraded\" mode in which all the communications are disabled. The fire station returns to the normal state when the restore event (_restoreComm_) happens.