Functional infrastructure design

Infrastructure only serves its purpose well if it enables the intended service to be delivered reliably and efficiently. It is not size or complexity that determines quality, but how well the infrastructure fits operational realities.

Densely interwoven track field with numerous switches and overhead line equipment, with an SBB double-deck multiple unit in the background — A track field shows at once which movements operations can make – and which they cannot.

Example: design requirements for station topology

Diagram of a functionally designed station topology

Example: optimisation of a station layout

Track layout of a station in its initial state — Before.

Optimised track layout of the same station — Optimised by Otimon.

Bar chart comparing key figures before and after optimisation — Effect of the optimisation in comparison.

We never view infrastructure in isolation, but always in the context of its function. Each individual element is analysed in terms of its role and its contribution to the overall process: what part does it play in operations? Where do bottlenecks occur? What level of reserve capacity is needed?

Our approach consistently starts with the service: what is to be operated? When? How frequently? And with what rolling stock? From these service objectives we derive the infrastructure requirements – from track lengths and platform positions to stabling facilities. This leads to functional topologies tailored to operations, not the other way around.

This approach ensures that infrastructure is neither over- nor under-dimensioned, but designed to be fit for purpose and economically viable.

The result: infrastructure that works – for operations, for passengers and for the future.

Functional. Efficient. Future-ready.