Type: UIC working group · ID: G06
The UIC working group for the Form Fit Functional Interface Specification (FFFIS) handles the interfaces between applications and FRMCS. UIC: FRMCS – organisation and document directory
Role in the FRMCS Context
The reviewed FFFIS-7950 describes OBAPP between the on-board application and On-Board FRMCS, as well as TSAPP between the trackside application and the FRMCS Trackside Gateway. It defines protocols, messages and information formats for these transitions. UIC: FRMCS FFFIS FFFIS-7950, version 2.1.0 (at ERA)
For software and system integrators, the FFFIS is therefore the entry point whenever an application is to use FRMCS communication services. Agreeing on an interface name alone is not sufficient for an integration project. A recommended step is to explicitly align version, required functions and the behaviour of both sides.
Significance and Binding Nature
The specification distinguishes requirements, options and information, as well as different target states. It is part of a coherent set of FRMCS documents and should not be used in isolation. UIC: FRMCS FFFIS FFFIS-7950, version 2.1.0 (at ERA)
Working Groups and Cooperation
For project cooperation, TOBA provides the vehicle context, the SRS the system model, and the FIS the end-to-end procedures. The specific interface design must be consistent with these foundations. UIC: FRMCS FFFIS FFFIS-7950, version 2.1.0 (at ERA)
Practical Guidance
Recommendation for interface acceptance: document the agreed version, parameters, expected responses and error behaviour for each function used. Tie the evidence to the relevant clause.