From the first call to live data in four weeks.

A proof of concept is a short, bounded engagement with one job: to show on your own network what continuous monitoring finds — and what finding it is worth.

  • 1working day for the installation on the vehicle
  • 4weeks until your network is on the dashboard
  • 6months a typical proof of concept

The path to live monitoring

Four phases. No guesswork.

The same sequence every time. Each phase has a date, an owner and one thing you hold in your hands at the end of it.

Live in four weeks. On your network for six months.
  1. 01Weeks 1–3

    Scope

    We define the need together: which routes, which vehicles, which faults actually cost you money. Nothing wider than that.

    You getA bounded pilot with a written objective.

  2. 02Week 4 · one working day

    Installation

    Sensor units, measurement device and gateway go onto one vehicle. Nothing is drilled or welded — the vehicle is not modified, and the fitting does not depend on the locomotive type.

    You getA vehicle that measures on its normal duty.

  3. 03From week 4

    Live view

    From the first day of data collection you are in the portal: track geometry, alarms, trends — the same views your team would work in every day.

    You getVisibility now, not a report in six months.

  4. 04Weeks 22–26

    Scale up

    We work out the setup for daily operation: how many vehicles, which routes, and which alarms go straight into your maintenance system.

    You getA costed plan for network-wide rollout.

Why a proof of concept

Low commitment. Real data.

A

Your network, not a reference network.

One installation over a defined period, on your own track and your own vehicles. The data describes your conditions — not a demonstration line under ideal weather.

B

The portal from day one.

You work in the same dashboard your team would use in daily operation. Nothing is held back for a closing presentation.

C

It ends with a number.

The POC closes with a concrete report: what was found, what maintenance value that represents, and what a network-wide rollout would return.

In revenue service since 2017.

Talk to us

Tell us about your network.

We come back with a focused POC proposal: your network, your priorities, the next practical step.

Also send me the following documents

Your details go to us and to no one else.

M4 Strategy

Four steps. One house.

M4 is Autech's approach to rail maintenance, and D-RAIL is the monitoring in it — continuously, from vehicles already in service. The other three steps come from the same house: Autech's measurement systems, its track management, and the grinding machines that do the work on site. Between the reading and the repair, nothing is handed to a third party.

Autech AG — autech.ch

D-RAIL AUTECH MEASUREMENT MANAGEMENT MAINTENANCE MONITORING
  • Measurement Autech Autech's measurement systems — such as the RML3000, RAILXS or the AT6200 modular measurement vehicle.
  • Management Autech Autech's track management turns readings into a condition forecast and a work order.
  • Maintenance Autech Autech's machines do the work on site — rail grinding and two-way vehicles, built in Rupperswil.
  • Monitoring D-RAIL Continuous monitoring from vehicles already in revenue service — so change in the network is seen while it is still small.

Next step

One vehicle is enough to start.

Tell us the route and the vehicle type. We will tell you what a proof of concept on it would look like.