Baselines, regulation and applicability

“FRMCS-compliant” leaves too much open

Talbahn receives two offers with the same claim: “complies with FRMCS”. One references published documents, the other a planned development. Both may describe their work, but they do not establish the same state.

A project baseline is the controlled set of governing documents and decisions established for a project. It identifies individual documents, versions, applicable parts and justified deviations. Changes are traceable so requirements and tests retain the same foundation.

This must be distinguished from the name of a published FRMCS specification family. “V2” or “V3” is not a complete list of all applicable document editions. A 3GPP Release likewise groups a development state of mobile-network functions; it is neither an FRMCS acceptance report nor an automatically identical FRMCS version.

Maintain current status in one place

The “Status and timeline” page contains the dated information for this course. It separates published foundations from announced milestones. The lessons thus remain understandable even if a date later moves.

Status and timeline

A central reference is FRMCS Baseline 0 in the ERA reference list associated with the CCS TSI 2023. The list itself notes that the on-board specifications are incomplete for tendering. Legal reference status therefore cannot be taken as proof of a complete, procurable functional scope. [S16]

The CCS TSI has since been amended by Implementing Regulation (EU) 2026/693 of 19 March 2026; the amendment entered into force on 5 May 2026. The legal reference for this revision is therefore the CCS TSI 2023 including this amendment. This is not publication of FRMCS V3 and does not automatically replace B0 references with the 2.1.0 teaching editions. [S40, S41]

B0 is not version 2.1.0. For FRMCS B0, the ERA list considered references FFFIS-7950 (index 092), FU-7120/FRS (093), AT-7800/SRS (094), FIS-7970 (095) and TOBA-7510/TOBA FRS (099), each in version 1.0.0. This course deliberately uses the newer 2.1.0 teaching editions for FRS, SRS, FFFIS and TOBA FRS. The ERA list consulted at the reference date continues to list these B0 indices at 1.0.0. The teaching editions do not automatically replace that TSI reference baseline. [S16, S41, S05, S06, S10, S39]

A project therefore records the regulatory reference edition, supplementary technical teaching or development source, and actually agreed project baseline separately. Version 2.1.0 must not be treated as an unqualified complete tendering foundation either: Annex A of the TOBA FRS still contains a corresponding limitation. [S39]

UIC's April 2026 announcement names V3p for November 2026 and an ERA-aligned V3 set for December 2027 as planned targets. This plan must be separated from completed publication and, still more, from national implementation. [S17]

Four columns prevent a false conclusion

For TB-REQ-017, Talbahn establishes the following view:

The columns are not necessarily a linear authorisation process. They help organise different claims. A planned capability may appear in a development agreement; its later delivery and verification must then be visible conditions.

Maturity relates to a capability

Here, maturity describes how far a specific capability is substantiated in specification, implementation and evidence. A product may have demonstrated a basic group call while role mapping across an IWF remains open. One traffic-light colour for the whole product would hide that difference.

Talbahn therefore adds not only a document version to the case file, but also the implementation known for each requirement and the evidence still missing. Planned dates occupy a separate column.

Check your understanding

An offer refers to “FRMCS B0, 3GPP Release 18 and V3-ready”. Which three follow-up questions are especially important?

Model answer

Which exact document versions and applicable requirements are meant? Which functions are already implemented in the offered software version? Which have been tested in our combination, and which are only contractually planned deliveries? The applicable legal and project baseline must also be clarified. The three labels replace none of these details.

What to remember

A version designation becomes useful through its scope, status and associated evidence.

Your Talbahn case file

Add separate columns for the B0 reference edition, 2.1.0 teaching source, project baseline and demonstrated product version.