For your team

Stop firefighting. Start closing the loop.

You don't need another dashboard. You need the failure localized, the work order filed, and the false alarms gone. Tokoaido grounds root cause in the asset graph and closes the loop into your work-order system.

27 hours/month
25 incidents/month
A typical large plant still loses 27 hours a month to unplanned downtime, across about 25 incidents.
Siemens, The True Cost of Downtime 2024 (2024)
$119.1B losses
$57.3B maintenance spend
US discrete manufacturers lose about $119 billion a year to preventable maintenance issues, on top of $57 billion in maintenance spending.
NIST (US Department of Commerce), Economics of Manufacturing Machinery Maintenance (NIST AMS 100-34) (2020)
9 in 10 monitor
~half have PdM teams
Condition monitoring is now mainstream: nine in ten manufacturers do some form of it, and almost half have dedicated predictive-maintenance teams.
Siemens, The True Cost of Downtime 2024 (2024)

How Tokoaido helps

What changes.

Graph-grounded root cause

The visible symptom is rarely the cause. Traversal over the asset twins localizes the real culprit.

Governed work orders, automatically

A confirmed condition becomes a risk-tiered, approved maintenance work order, then the outcome is verified.

Per-machine telemetry with real history

Gauges, spectra and 24h–90d trends for every asset.

A safety boundary that can't be overridden

Never a direct PLC or SIS write.

Sound familiar?

The work nobody signed up for.

If you have said one of these this month, the rest of this page is for you.

I get forty threshold alarms a day. Two of them matter, and I cannot tell which two.
Reliability engineer
The symptom shows up at final inspection. The cause is a pump two buildings away.
Quality engineer
My planners spend the morning working out which asset an alert is even about.
Maintenance planning lead
We bought condition monitoring three years ago. It still ends in an email to me.
Reliability manager
Before anything writes to the floor, I need proof it cannot reach the safety system.
Controls engineer
Getting a clean vibration history out to train our own model takes a ticket and a week.
Data scientist, operations

Use cases

What you would use it for, first.

Each one starts from a problem you can name, and ends with something a person can see has changed. Live means it runs in the product today; pilot means we build it with you.

  1. 01

    Root cause traced across the asset graph

    Live today
    Today

    Rework climbs at inspection and the team argues about whose station is at fault.

    With the platform

    The diagnostic tier traverses the asset twins from the symptom to the upstream asset that is degrading, and names it with the evidence.

    What changes

    The fix goes to the coolant pump, not to the inspection station.

  2. 02

    Findings instead of a wall of alarms

    Live today
    Today

    Static thresholds fire on every spike, so the alarms that matter drown.

    With the platform

    A finding is raised on a trend against ISO 20816-3 zones and confirmed by the diagnostic tier before anyone is asked to act. Each confirmed or dismissed finding feeds the agent's track record.

    What changes

    The team reads a short list of evidenced findings each morning.

  3. 03

    Every repair checked against the trend

    Live today
    Today

    A work order is closed as done, and nobody checks whether the vibration actually came down.

    With the platform

    After the work order, the platform measures again, keeps the change if the metric improved and rolls back if it did not, then records the outcome.

    What changes

    Every closed work order says whether it worked.

  4. 04

    Clean history for your own models

    Live today
    Today

    Your data team waits a week for a vibration extract and gets averages instead of spectra.

    With the platform

    Each machine keeps 24-hour to 90-day history and its vibration spectrum, with a CSV export shaped for anomaly and remaining-life models.

    What changes

    Your data scientists train on clean history the same afternoon.

Business value

Where the return comes from.

The levers, and the range other organizations have published for each. Ranges are typical of the category, not a promise and not our customers' results.

Breakdowns

−70–75%

The upper-end range from surveys compiled by the US DOE in 2010. Plan on the more conservative figures alongside it.

US Department of Energy (FEMP), Operations & Maintenance Best Practices Guide, Release 3.0 (2010)

Maintenance cost

−5–10%

Deloitte's typical range when maintenance moves from the calendar to the condition of the asset.

Deloitte Insights, Predictive maintenance and the smart factory (2017)

Downtime at plants leaning on prediction

−15% (association)

An association in NIST survey data among proactive plants, not a controlled result.

NIST (US Department of Commerce), Economics of Manufacturing Machinery Maintenance (NIST AMS 100-34) (2020)

Time spent sorting alarms

Engineers read evidenced findings instead of raw threshold alarms. Measure it against your own alarm counts.

Run your numbers

Unplanned downtime you could avoid.

Every input is yours to change, and the arithmetic is shown in full. Nothing is hidden in a multiplier.

Estimate
≈ €2M
downtime cost avoided a year

324 × €25,000 × 25% = €2,025,000

An estimate on the numbers above, not a measurement and not a customer result. In an Operations X-Ray we replace the assumptions with figures measured on your own systems.

Before and after

The same week, run differently.

Forty alarms a day, two of them real.

A short list of findings, each with its evidence.

The symptom is fixed where it shows up.

The cause is fixed where it starts.

Work orders close without checking the trend.

Each work order closes with a measured result.

A vibration extract takes a ticket and a week.

Ninety days of history export in one click.

Every write to the floor is a meeting about safety.

Writes go through SCADA or MES with approval, and the safety system is out of reach.

In practice · Example scenario

Rework at inspection → a failing pump upstream

The symptom shows at QA, but the cause is a degrading coolant pump. The graph localizes it and emits a specific, governed fix.

Capabilities in play
Twin-grounded root causePlant floor (OT)Machine telemetry & PdMClosed-loop actionHard safety boundary
See the platform

Operations X-Ray

Bring us your noisiest asset.

We read its trend, trace the cause and show the work order the platform would have raised.