EASA Adds Real-Time Fusion Test to CBTC SIL4 Rules

On July 9, 2026, EASA updated its CBTC safety certification guidance and turned a technical performance issue into a formal compliance requirement: end-to-end real-time performance for trackside multi-source data fusion must now be verified within a threshold of no more than 150 ms for SIL4 certification. With a dual-report requirement taking effect from October 1, 2026 for suppliers exporting or deploying CBTC systems in the EU, the change deserves attention not as a routine standards revision, but as a direct adjustment to certification preparation, export compliance, and project delivery planning, especially for Chinese CBTC equipment manufacturers serving the European market.

What the updated guidance now requires

The confirmed facts are limited but clear. EASA updated its CBTC System Safety Certification Guidance on July 9, 2026. Under the update, end-to-end real-time performance for trackside multi-source data fusion, defined at no more than 150 ms, is included within the scope of mandatory verification for SIL4 level certification.

EASA also requires that, from October 1, 2026, all suppliers exporting CBTC systems to the EU or deploying such systems in the EU must provide two forms of verification documentation: a third-party timing simulation report and an on-site stress testing report. The information provided further indicates that this change directly affects the compliance path and project delivery cycle of Chinese CBTC equipment manufacturers exporting to Europe.

Where the pressure is likely to appear first

For equipment manufacturers pursuing EU projects

From an industry perspective, this group is the most directly exposed because the rule change is tied to SIL4 certification evidence, not only to product claims. The immediate impact is likely to appear in certification preparation, technical documentation, test coordination, and delivery scheduling. What deserves closer attention is whether existing product validation packages already cover end-to-end timing behavior for trackside data fusion in a form that can satisfy the new mandatory verification requirement.

For exporters and bid-facing commercial teams

Suppliers involved in export transactions or project bidding may be affected at the document and timeline level. The new requirement points to a compliance file that now needs both third-party timing simulation and field stress testing evidence. In practice, teams handling tenders, contract commitments, and delivery milestones should pay close attention to whether bid documents, technical submissions, and shipment readiness assumptions still match the updated certification path.

For testing, certification, and verification service providers

Analysis shows that service providers connected to simulation, testing, and certification support may see a more central role in project execution, because the guidance now explicitly requires dual verification. The relevant business impact is not simply additional testing work, but the need for documentation that aligns with the certification expectation attached to SIL4. Companies relying on outside verification support should therefore focus on report scope, sequencing, and acceptance readiness.

For buyers and project delivery participants

Procurement teams, integrators, and delivery managers may need to reassess timing assumptions around acceptance and deployment. Since the requirement applies to suppliers exporting to or deploying in the EU, the commercial effect may extend beyond certification teams into procurement scheduling, supplier qualification checks, and pre-delivery review gates. Observably, this is the type of rule change that can affect whether a project package is considered complete at the point of submission or handover.

What companies should review now

Check whether current certification evidence is still sufficient

Analysis shows that the first practical question is not broad strategy but evidence sufficiency. Companies should review whether their current SIL4-related files already address end-to-end real-time verification for trackside multi-source data fusion at the required threshold, and whether the evidence can be presented in the dual-report structure now required for EU export or deployment.

Revisit technical files, test reports, and bid materials

What deserves closer attention is the consistency between technical claims and submission materials. Where compliance packages, tender annexes, validation reports, or customer-facing technical documents were prepared under an earlier interpretation, companies may need to check whether those materials now require supplementation or reformatting to reflect the updated guidance.

Watch the delivery calendar around the October 1 effective point

Observably, the stated effective date creates an operational checkpoint. For projects that are being prepared for export or deployment close to that date, companies should pay attention to whether testing schedules, third-party engagement, and site-level stress verification can be completed in time. The provided information does not define how transitional cases will be handled, so this remains an area that requires careful monitoring rather than assumption.

Track execution language beyond the headline rule

The update establishes the mandatory verification item and the need for dual reports, but the input does not provide more detailed execution language. For that reason, companies should continue watching how the requirement is reflected in certification review practice, customer documentation requests, and project qualification materials. This is especially relevant for firms whose EU business depends on tightly managed delivery windows.

Why this reads as an execution signal

Analysis shows that this development is more appropriately understood as an execution-level compliance signal rather than a general policy discussion. The reason is straightforward: the update identifies a specific performance metric, ties it to SIL4 mandatory verification, and sets a defined date from which dual verification reports must be provided for EU export or deployment. That gives the rule immediate operational relevance.

At the same time, it is still too early to treat every downstream consequence as settled fact. Observably, the market still needs to see how certification reviews, procurement documents, and project-level acceptance practices reflect the updated guidance in day-to-day execution. For that reason, the rule appears implemented at the guidance level, while some practical interpretation points still warrant continued observation.

How the market may need to interpret this change

The most reasonable reading at this stage is that EASA has raised the documentary and verification threshold for CBTC suppliers seeking SIL4-related market access or deployment continuity in the EU where trackside multi-source data fusion is involved. The significance lies less in abstract regulatory language and more in the shift of real-time fusion performance into a mandatory, externally evidenced compliance item.

From an industry perspective, this should be treated as a concrete compliance change with direct implications for certification preparation and project timing, but not as a basis for overstated conclusions about market outcomes. The immediate task for affected companies is to verify readiness, align documents, and monitor how the requirement is applied in practice after October 1, 2026.

Basis of this article and what still needs verification

This article is based on the user-provided news title, event date, and event summary. For developments of this kind, relevant source categories typically include official notices, releases from regulatory bodies, documents issued by standards or certification organizations, trade or customs-related notices where applicable, industry association materials, and reporting by authoritative sector media.

No specific official source link was provided in the input, so the exact official publication link still needs to be verified on an ongoing basis. Observably, the key points that warrant further tracking are detailed implementation language, certification interpretation in practice, possible changes in tender and technical file requirements, market feedback, and how affected companies adjust their execution and delivery arrangements.