ETENAR Rail

Modular control.
For vehicles and infrastructure.

Safe Modular Secure by Design

ETENAR Safe Config and ETENAR Safe Kit connect system design and engineering for On-Board and wayside applications. Safe computing, configurable inputs and outputs, and communication are matched to your railway application.

For new and existing railway systems: assess obsolescence early, plan replacements and modernise functions in stages.

A main station, an intercity train and a freight train are connected by tracks to the shared ETENAR technology platform. Wayside is shown at the infrastructure, and On-Board at both trains. Modular, distributed technology connects SIL and NON-SIL functions.
RailETENAR technology platform
On-Board and waysideCentral station: Wayside · Signals · PointsIntercity: On-Board · Vehicle controlFreight train: On-Board · diagnosticsModular · Distributed · End to end
SIL functions · NON-SIL functions

Background imageAI-generated concept visualisation

Three principles. One technical foundation.

Safe

Safety functions and system boundaries determine the design. Verification, validation and application-specific evidence accompany the development process.

Modular

Compute assemblies, I/O and segments form a central or distributed architecture. Installation and communication follow the On-Board or wayside task.

Secure by Design

Secure Boot, secure updates and access control are considered in the architecture. Selection and operating conditions follow protection needs and the product variant.

Railway applications

On the vehicle.
Along the track.

A shared technical foundation connects different railway tasks. Functions, interfaces and operating conditions determine the design for each system.

Signalling · Wayside

Wayside signalling infrastructure includes signals, axle counters, turnouts and point machines, computer-based interlockings, level crossings and object controllers. Distributed assemblies connect sensors and actuators with their control and safety functions. Replacement and modernisation take existing interfaces and operating conditions into account in the system design.

Rolling stock · On-Board

Door systems and controls, TCMS, propulsion and vehicle communication connect local tasks with the vehicle architecture. Braking, SiFa and speed functions are further application areas. Safe computing, I/O and communication interfaces are matched to the On-Board application and the existing system baseline.

Train protection & control

ETCS, RBTC, CBTC, ATO and ATP are among the engineering application areas, alongside safe displays, ATS and ATC. EULYNX, RaSTA and FSE form part of the interface and communication context. The specific railway application determines which functions, interfaces and evidence are required.

The ETENAR technology platform

System design.
Connected engineering.

ETENAR Safe Config and ETENAR Safe Kit together form the platform for industry and rail. Architecture, system software and engineering work together for your railway application.

System design

ETENAR Safe Config

Functions, assemblies, signals and installation locations are designed alongside the system software. This defines architecture, signal mapping and integration requirements, from compact configurations to distributed systems.

Engineering toolchain

ETENAR Safe Kit

Tools and libraries support configuration, application development and extension. The appropriate toolchain connects engineering tasks with diagnostics and commissioning preparation. The agreed version defines the available functions.

The development foundation comprises SiTCommand with generic hardware and system software, and SiTKit with engineering tools and libraries.

Explore the technology platform
Modular

Suitable building blocks.
Flexible distribution.

Compute assemblies, binary and analogue I/O, and mixed assemblies form the required structure. Form factor and distribution follow the application.

ETENAR Controls with processing and I/O modules in different form factors.
ETENAR Controls in different form factors
AI-generated concept visualisation of a modular system architecture from a compact assembly to a distributed control system.
From a compact assembly to a distributed control systemAI-generated concept visualisation. Choose the form factor, I/O mix and deployment topology to suit the application – while maintaining a consistent platform approach.
  1. Module

    An individual module for processing, I/O or fieldbus functions.

  2. Assembly

    Selected modules combined in one unit.

  3. Segment

    Assemblies for one functional part of the application.

  4. System

    Connected segments for the complete application.

Matched to your application.

Three areas that shape the system design.

Connect safely over Ethernet

SiTCSafeCom supports safety-related Ethernet communication between assemblies and segments.

Compute and I/O resources can be distributed according to the selected configuration. Independent or communicating applications can run on one or more controllers.

Match installation and power

3U and DIN-rail formats, independent or redundant supplies, and UPS integration support different installation concepts.

The configuration is selected according to operating conditions. Galvanically isolated, hot-pluggable I/O assemblies can form part of the selected configuration.

Check placement at startup

The technical foundation supports a geographic configuration check: intended assembly placement is verified at startup.

An incorrect placement detected during this check stops the system. Behaviour follows the defined system configuration.

Engineering

Four responsibilities.
One shared system baseline.

ETENAR Safe Config defines the system design. ETENAR Safe Kit supports engineering from functions and installation through to application and commissioning. Defined roles make handovers between functional specification, physical installation and application traceable.

  1. 01

    System engineering

    Define functions, system boundaries and logical architecture. Sensors, actuators and required control tasks establish a common starting point.

  2. 02

    Installation engineering

    Map sensors and actuators to physical I/O. Modules, segments, locations and power supplies are brought together in the installation.

  3. 03

    Application engineering

    Implement specified behaviour on controllers and, where applicable, I/O assemblies. Configuration and application logic are aligned.

  4. 04

    Commissioning and validation

    Integrate application and hardware in the target system. Diagnostics, testing and documentation support commissioning and final validation.

A shared system baseline provides the foundation for managing obsolescence. When assemblies are discontinued, affected functions, interfaces and existing evidence are assessed together. Replacement, migration and additional testing can then be planned as one coordinated change.

Obsolescence · Installed systems and modernisation

Manage obsolescence.
Keep railway systems in service.

Vehicles and infrastructure often remain in service longer than individual electronic assemblies are available. Discontinuation and limited spare-part availability make obsolescence a system-level concern. Modular architecture supports targeted replacement and staged modernisation.

The starting point is the existing hardware and software baseline, interfaces, operating conditions and evidence. Together, we assess replacement options, effects on existing functions and the migration step required. Evidence that remains applicable and any additional testing are determined for the new configuration.

Discuss obsolescence and modernisation
  1. 01

    Record the baseline and discontinuations

    Identify hardware, software, configuration and evidence; record discontinued assemblies and spare-part needs.

  2. 02

    Assess replacement and migration

    Review replacement options, interfaces and effects on functions and unchanged parts of the system.

  3. 03

    Demonstrate integration

    Define migration steps, additional tests, documentation and responsibilities for the specific railway application.

Your benefit throughout the lifecycle.

Plan replacements ahead.

Identifying discontinuations early creates time to coordinate replacement options and testing. Evidence that remains applicable can limit additional effort. Scope and timing depend on the specific railway application.

Protect your investment.

Assemblies, functions and evidence that remain suitable provide the starting point for modernisation. Targeted replacement can help retain proven parts of the system and focus engineering and testing on the affected changes.

Keep changes under control.

Replacement assemblies and migrations remain linked to a clear system baseline. Effects on safety, security and interfaces are assessed together, helping coordinate modernisation, integration and recommissioning.

Obsolescence becomes part of planned railway system development rather than a short-term replacement problem.

Assessment and authorisation requirements are determined for the specific vehicle or infrastructure application. Evidence for an assembly does not replace assessment of its integration.

Safety & security

Plan around the function.
Demonstrate it in the system.

Functional safety and cybersecurity accompany architecture and engineering. Measures, tests and responsibilities are defined for the specific configuration.

Safe · Functional safety

The technical foundation supports Basic Integrity functions and SIL applications up to SIL 4. Safety integrity and evidence relate to the specific function and system configuration. Safety support, verification, validation, qualification and test automation support development.

Secure by Design · Cybersecurity

Secure Boot, secure updates, access control and key management are among the security building blocks available in the technical foundation. Selection and operating conditions depend on the product variant, protection needs and security concept.

Approval of a railway application remains tied to its requirements, integration and application-specific evidence.

Standards and engineering context

The technical context includes IEC 61508, EN 50126, EN 50128, EN 50129 and EN 50716, alongside IEC 62443 and railway cybersecurity under IEC 63452 or CLC/TS 50701. Applicable requirements are established for each project.

Collaboration & further development

Bring technology and
railway expertise together.

New applications and existing systems need coordinated development. Changes to functions and interfaces are connected with integration, testing and documentation. For modernisation, affected interfaces and existing system assumptions remain the starting point for assessing changes.

ETENARSafe.inTrain

ETENAR and Safe.inTrain work together on architecture, hardware, software and test planning. Platform technology and railway-specific engineering are combined for the railway application. Delivery scope and responsibilities are agreed for each project.

Our partnership
Starting a project

From your task
to the right scope.

How do we start a railway project?

With functions, interfaces and operating conditions. For obsolescence, we also examine the existing system baseline, affected assemblies and known discontinuations. Together, we agree the replacement or migration approach, engineering scope and evidence required.

What does technical handover include?

Hardware, software version, configuration and documentation are agreed within the delivery scope. Test results and operating conditions remain associated with the system baseline, supporting integration, maintenance and later extensions. This makes it possible to identify the tested baseline on which a new variant is built.

Let’s discuss your railway application.

On-Board or wayside: let’s discuss your new development, discontinued assemblies or modernisation of an existing system.

Discuss your project