Service Function Configuration

Standardized configuration enables reliable, traceable and supplier-independent management of complex railway systems.

Configuration is essential when systems consist of many interacting components, software versions, parameters and dependencies. A structured configuration model helps ensure that changes remain understandable, verifiable and reproducible.

Every Building Block Configuration is given a unique address in the repository and knows its own dependencies. This lets the full dependency tree be derived automatically from a release version, with the status of every configuration - from 'requires update' through 'preloaded' to 'installed' - tracked at all times.

Today we rely on the EULYNX Standard Maintenance Interface (SMI) v2 for field elements. The upcoming Europe's Rail SMI v3 extends this with local and adjacent Configuration Repositories, a central Configuration GUI, and the Safe Configuration Authority (SCA) for safety-related approval.

Structured handling of complex system configurations as a dependency tree
Traceability across versions and lifecycle phases
Supplier-independent configuration exchange via EULYNX SMI
Support for validation, activation and rollback processes
Migration path from SMI v2 (today) to Europe's Rail SMI v3 (from 2027)
Safety-related configuration approval through the Safe Configuration Authority (SCA)