CBP TECHNOLOGY PRINCIPAL · SYSTEM DIAGNOSTICS

Plasser Diagnostics

Plasser Diagnostics is most useful when the railway needs more than one isolated measurement. It combines track, rail, turnout, catenary, clearance, visual and vehicle diagnostics into a synchronized architecture.

FULL TECHNOLOGY OFFERING

Choose the measurement domains, then integrate only what changes maintenance decisions.

Plasser Diagnostics' breadth is a strength only when the architecture remains tied to real operating questions.

Track & turnout

TGMS / TCMS routes measure track geometry and complex turnout/crossing condition.

TRACK GEOMETRYTURNOUTSPOSITION

Rail surface

RPMS / RCMS address rail profile, wear and corrugation measurement.

RAIL PROFILEWEARCORRUGATION

Electrification & clearance

CPMS, WGMS, WWMS and PwRMS cover structural clearance, catenary geometry/wear and third-rail measurement.

CLEARANCECATENARYWIRE WEARTHIRD RAIL

Visual / vehicle / software

Visual inspection, wheel profile, axle-box acceleration, hunting measurement, TracksNet® and Contact™ connect images, vehicle behavior and data history.

VIDEOWHEELSDYNAMICSTRACKSNETCONTACT

CAPABILITY MAP

Plasser Diagnostics can turn one diagnostic vehicle into a coordinated measurement platform.

Track geometry

Repeated route geometry tied to position.

Rail profile & corrugation

Surface wear and rail condition.

Turnout measurement

Focused geometry for switches and crossings.

Clearance

Infrastructure envelope against the track reference.

Catenary / third rail

Power-collection geometry and wear.

Visual inspection

Synchronize imagery with measured location.

Rolling-stock screening

Wheel profile and vehicle-dynamics measurements.

Data management

TracksNet® organizes trends, defects and maintenance history.

DIAGNOSTIC ARCHITECTURE BUILDER

Build the measurement architecture from domains, integration and data workflow.

Use a single subsystem when one domain answers the job. Integrate only when synchronized evidence changes maintenance decisions.

PRIMARY MEASUREMENT DOMAIN

SECONDARY DOMAIN 1

SECONDARY DOMAIN 2

MEASUREMENT SPEED / DEPLOYMENT MODE

REQUIRED ACCURACY LEVEL

SAMPLING / SPATIAL RESOLUTION

LOCALIZATION METHOD

PLATFORM / VEHICLE INTEGRATION

DATA OWNERSHIP / EXPORT

MAINTENANCE WORKFLOW

OPTIONAL ENGINEERING NOTES

GUIDED SELECTION

What do you need to measure?

This is an architecture selector, not a model picker. Select one domain or combine several.

TGMS / TCMS architecture

Start here when the maintenance decisions concern geometry, track position or turnout condition.

Measurement objectives, vehicle integration, speed, uncertainty, environment, positioning, data ownership and maintenance workflow determine the final Plasser Diagnostics system.

WHY THIS PRINCIPAL?

Integration is useful when location and history stay attached to every measurement.

A pile of sensor files does not create a maintenance system. Plasser Diagnostics' differentiation is the ability to synchronize multiple diagnostic domains and carry the information into software that supports repeated comparison and prioritization.

Need	Plasser Diagnostics capability	Why it matters
One condition domain	Dedicated measurement subsystem	Avoid unnecessary system complexity
Several domains	Integrated diagnostic platform	One synchronized run / shared position context
Repeated network measurement	Trainborne / wayside architecture	Build trend history instead of snapshots
Maintenance planning	TracksNet®	Connect defects, history and action workflow

INTEGRATED DIAGNOSTICS

One architecture for multiple railway condition domains.

SYSTEM CAPABILITY

Coordinated multi-domain diagnostics

Plasser Diagnostics brings track, rail, turnout, catenary, clearance, visual inspection and vehicle-condition monitoring into a coordinated diagnostic architecture. CBP supports Indonesian applications by aligning the required measurement domains, vehicle platform, operating conditions and maintenance workflow with the appropriate system configuration.

WHAT CBP ADDS

CBP starts Plasser Diagnostics projects from the maintenance decisions, not the sensor list.

01 · Define decisionsWhat actions should the data trigger?

02 · Select domainsTrack, rail, catenary, clearance, visual, wheels or dynamics.

03 · Engineer integrationVehicle, positioning, speed, environment and data interfaces.

04 · Operationalize dataReporting, thresholds, history and maintenance ownership.

APPLICATION SUPPORT

Discuss your railway application with CBP.

Tell us the operating problem, vehicle or infrastructure involved, and the result you need. We will connect you with the relevant technology route.

CONTACT CBP

Find a solution

Find a principal

See our work

Know CBP