Type: UIC working group · ID: G02
The FRMCS Functional Working Group (FWG) translates operational communication needs into functional requirements. It belongs to the UIC's FRMCS programme. UIC: FRMCS Functional Working Group, 27 November 2020
Role in the FRMCS Context
Its starting point is the user perspective: which communication function is needed in rail operations? The UIC names the User Requirements Specification (URS) as the group's first major work product and then describes the work on the Functional Requirements Specification (FRS). UIC: FRMCS Functional Working Group, 27 November 2020
The FRS organises functions such as voice and data communication, role management and priorities into a shared application concept. This functional structuring is not yet a concrete technical architecture. The document explicitly distinguishes the description of the need from its technical implementation. UIC: FRMCS FRS FU-7120, version 2.1.0 (at ERA)
Significance and Binding Nature
The URS serves as a basis for derivation; according to the FIS it is not among the normative FRMCS specifications. For the FRS, the applicable requirement categories and the chosen version must be observed. UIC: FRMCS FIS FIS-7970, version 2.1.0 UIC: FRMCS FRS FU-7120, version 2.1.0 (at ERA)
Working Groups and Cooperation
The ATWG translates functional requirements into system and architecture capabilities. Coordination between the FRS and SRS is therefore a key link to the FWG. UIC: 100th ATWG meeting, 12 June 2026
Practical Guidance
Recommendation for requirements engineers: first map an operational need onto the FRS. Only then determine which system components are to fulfil it.