Understand · 1.2
People, roles, workplaces and applications
Time: about 8–11 minutes including the task; estimate
Guiding question: Which people and applications exchange information, and why?
Learning objective: You distinguish person, role, workstation, device and application.
Prerequisites: Previous lessons through 1.1, particularly the case file developed there.
The same role, a different person
Amir takes over train 1234 from Lea. In this simplified example, each has their own reachable device. Niko selects ‘driver of train 1234’, but this destination is still mapped to Lea’s device. His call therefore reaches Lea instead of Amir. A reachable device does not prove that the right person has been reached.
Lea and Amir are people. An operational role describes their task and responsibility in railway operations. Here, it is the driver role for train 1234. Different people can hold a role at different times. “Driver of train 1234” must therefore resolve to the current assignment. [S01, S05]
The radio is their tool. It captures speech and plays received speech; it does not take on the driver's responsibility. Similarly, we distinguish Niko from his control-centre workstation. The control centre is the location or organisational setting where tasks are coordinated. The workstation is the technical equipment.
Applications also have counterparts
A technical application performs a particular task using software and data. The measurement application on the train collects temperature data from a component. It sends the data to the analysis application at the Talstadt maintenance workshop. Maintenance keeps vehicles operational; its staff use the analysis to assess the component's condition.
| Sender | Recipient | Purpose |
|---|---|---|
| Lea or Amir in the driver role | Niko as the responsible signaller | Take a delay into account when controlling train movements |
| Measurement application on the train | Analysis application at the Talstadt workshop | Assess the condition of a component |
The applications can exchange data while nobody is speaking. Conversely, a successful measurement transfer does not prove that Niko can reach the correct driver role.
What remains when the system changes?
GSM-R and FRMCS support communication for railway tasks. Even when the technology changes, the right parties must be reached. [S03–S05] Four details help: who or what sends? Who or what receives? What information is exchanged? Why is it needed?
A device inventory answers this only partly. “Radio, server, screen” identifies neither the responsible person nor the meaning of the information. The assignment is what turns reachable technology into useful communication.
Check your understanding
Amir takes over train 1234 from Lea. Each has their own reachable device. A role-based call to ‘driver of train 1234’ still reaches Lea’s device. What changed, what remained the same, and why might the call be wrong? Also name both parties in the measurement transfer.
Model answer
The person changed from Lea to Amir. The task of driving train 1234 continues; Amir now holds it. Both devices remained reachable. The destination ‘driver of train 1234’, however, is still mapped to Lea’s device; its reachability does not prove that the right person has been reached. The technical parties are the measurement application on the train and the analysis application in the workshop, not simply “the train” and “the railway”.
What to remember
- A person, operational role and device are not interchangeable.
- An application description also needs its counterpart and purpose.
- Technical reachability does not prove correct responsibility.
Your Talbahn case file
Add both relationships. Record Amir's role takeover as occurring on the following day. Lea remains the driver in our original case; later changes will be announced explicitly.
Sources
S01 · UIC EIRENE FRS
Version: 8.1.0 · Checked: 2026-10-11
Scope: Functional requirements: voice functions, groups, priority and functional addressing.
Limitations: Teaching reference; determine applicable requirements and MI markings for the project.
Used in: 1.1, 1.2, 1.3, 1.6
S03 · ERA: European Rail Traffic Management System
ERA: European Rail Traffic Management System
Version: Web overview · Checked: 2026-10-11
Scope: Relationship between ETCS and railway communication.
Limitations: Orientation; use S18/S30 additionally for specific ETCS statements.
Used in: 1.1, 1.2, 1.3, 1.7
S05 · UIC FRMCS FRS FU-7120
Version: 2.1.0, 29 April 2025 · Checked: 2026-10-11
Scope: Functional requirements, identities, Functional Alias, voice and hazard communication.
Limitations: Teaching foundation, not evidence of complete product support.
Used in: 1.2, 1.3, 1.6, 2.7, 2.8, 2.15, 2.20, 3.2
Your progress is stored in this browser on this device.