Seven films of Datum in use.

Each is a recording of the product itself, on demonstration data from an integrated paper mill, silent and captioned, with a transcript below. Start with the two-minute film for your role; the chapters go deeper.

Two minutes, for your role

One bearing, call to validated close, opened on the problem your role knows.

The outage came and went

2:10 · Silent, captioned · Reliability and maintenance managers at the plant

The report said replace at the next outage. Two minutes on one bearing, from the analyst’s call to a validated close.

What it shows and solves

The measurement of record: The work order closed, and three weeks later it’s worse, with nothing to check it against.
Production impact at the area’s rate: “Run it to the outage,” decided in a hallway, with no cost written down.
Plan work, set for the boiler outage: The report said replace at the next outage, and it never reached the planner.
Post-repair reading and “Did the repair work?”: A closed work order counted as a fix, with no reading behind it.

Read the transcript

The report said replace at the next outage.
The outage came and went. It never made the scope.
Or the work order closed, and three weeks later it’s worse.
Analyst
0.41 in/s at the drive end, against a 0.30 alert limit.
That number is the gate. Nothing counts as a save until it’s measured again.
Eight stages, one record, call to validated close.
Asset owner
The asset owner approves the work order, and the impact cost goes on the record with it.
Three hours of downtime, priced at this area’s own rate. That’s the impact cost.
Planner
Scheduled into the boiler outage. Search the work order number and this escalation comes up.
Maintenance crew
It wasn’t just the bearing. Six mils of misalignment, and that goes on the record too.
Asset owner
The owner confirms it’s back in service. That’s not the same as closed.
Field tech
The same point, measured again after the repair. Without it, there’s nothing to prove the repair against.
Analyst
88% lower and under the alert limit. Now it can close.
Root cause recorded, and it closes. Validated, not just completed.
Analyst
Another machine, a refiner: called at 0.38 in/s, 0.44 after the repair. It came back higher.
So it can’t close as a save. Back to the field tech to recheck the same point.
Your CMMS still runs the work. No integration project.
Datum holds why the work was needed, and whether it worked.
No post-repair reading, no save.
See it on your own equipment. A 30-minute walkthrough: one of your asset classes, from the analyst’s call to the validated close.

“What did we get for this?”

2:04 · Silent, captioned · PdM service providers, ahead of a renewal

At renewal: “What did we get for this?” Two minutes on one bearing, from your call to a save the plant can check.

What it shows and solves

Production impact at the area’s rate: Your savings report uses your numbers, so the plant discounts it.
What the crew found, on the record: What the crew found when they opened it never gets back to your analyst.
Post-repair reading at the same point: The next route is a month out, so nothing shows the repair worked.
“Did the repair work?” and Send back: A save on paper the plant can’t check against a reading.

Read the transcript

At renewal: “What did we get for this?”
Your savings report uses your numbers, so the plant discounts it.
And the call they never acted on becomes your miss.
Analyst
0.41 in/s at the drive end, against a 0.30 alert limit.
That number is the gate. Nothing counts as a save until it’s measured again.
Eight stages, one record, your call to validated close.
Asset owner
The asset owner approves the work order, and the impact cost goes on the record with it.
Three hours of downtime, priced at this area’s own rate. That’s the impact cost.
Maintenance crew
It wasn’t just the bearing. Six mils of misalignment, and that goes on the record too.
Asset owner
The owner confirms it’s back in service. That’s not the same as closed.
Field tech
The same point, measured again after the repair. Without it, there’s nothing to prove the repair against.
Analyst
88% lower and under the alert limit. Now it can close.
Root cause recorded, and it closes. Validated, not just completed.
Analyst
Another machine, a refiner: called at 0.38 in/s, 0.44 after the repair. It came back higher.
So it can’t close as a save. Back to the field tech to recheck the same point.
A call nobody acts on stays open, showing where it stopped.
Your renewal savings: figures your customer’s asset owner wrote down.
Counted only where a post-repair reading validated the repair.
No post-repair reading, no save.
Start with one customer: 30 minutes, one of their asset classes, your call to validated close.

What became of your call?

2:02 · Silent, captioned · Condition monitoring analysts, remote or on site

You called it three months ago. Two minutes on one call, from the reading it was raised on to the reading after the repair.

What it shows and solves

Raise escalation, with the measurement of record: Your call sits in a PDF, and by October, what did it read in March?
Verify, at the machine: A remote call can point at the wrong pump, and the site doubts it.
What the crew found, on the record: What they found when they opened it never reaches you.
Post-repair reading at the same point: No reading until the next route, weeks away, so a bad install goes unseen.

Read the transcript

You called it three months ago. What became of it?
Four reports later, no sign of a work order.
What they found when they opened it never reaches you.
Analyst
0.41 in/s at the drive end, against a 0.30 alert limit.
That number is the gate. Nothing counts as a save until it’s measured again.
Eight stages, one record, call to validated close.
Field tech
At the machine: right pump, sensor mount good, 0.41 on the handheld. Confirmed before labor is spent.
Maintenance crew
It wasn’t just the bearing. Six mils of misalignment, and that goes on the record too.
Asset owner
The owner confirms it’s back in service. That’s not the same as closed.
Field tech
The same point, measured again after the repair. Without it, there’s nothing to prove the repair against.
Analyst
88% lower and under the alert limit. Now it can close.
Root cause recorded, and it closes. Validated, not just completed.
Analyst
Another machine, a refiner: called at 0.38 in/s, 0.44 after the repair. It came back higher.
So it can’t close as a save. Back to the field tech to recheck the same point.
See which stage your call is waiting at.
Then what they found when they opened it, and the reading after.
You’ll know what became of it.
Tell us about one call that went nowhere. We’ll walk one like it through all eight stages in 30 minutes.

Chapters

Each goes deeper into one part: the whole escalation, the wait for an outage, the program, setup.

One escalation, all eight stages

5:42 · Silent, captioned · Anyone weighing the whole process, stage by stage

A closed work order isn’t a fixed fault. Follow one bearing through all eight stages and five roles, with a card before each stage saying what it prevents.

What it shows and solves

The measurement of record: By October, what did it read in March?
Production impact at the area’s rate: “Run it to the outage,” decided in a hallway, with no cost written down.
“What did you find?” at execution: The closing note says “replaced brg.” Nothing else.
“Did the repair work?” and Send back: A save on paper, with no reading behind it.

Read the transcript

Analyst
88% lower and under the alert limit. Now it can close.
A closed work order isn’t a fixed fault.
Here’s how this one got there, call to validated close.
Stage 1 of 8 · Raise · Analyst
By October, what did it read in March?
The reading it was raised on stays with the call.
Analyst
Every open escalation, ranked by criticality, severity and remaining life.
The analyst calls it. Outer race defect on the #2 boiler feed pump.
High severity, 35 days of remaining life: the window the analyst gives you to plan.
0.41 in/s at the drive end, against a 0.30 alert limit.
That number is the gate. Nothing counts as a save until it’s measured again.
It’s in the field tech’s queue now. Copy the field link and it opens on a phone.
Stage 2 of 8 · Verify · Field tech
A remote call can point at the wrong pump.
Field tech
At the machine: right pump, sensor mount good, 0.41 on the handheld. Confirmed before labor is spent.
Approving the work order isn’t his call. It goes to the asset owner.
Stage 3 of 8 · Approve · Asset owner
“Run it to the outage,” decided in a hallway.
Asset owner
It’s in their queue now. The stage decides whose.
The asset owner approves the work order, and the impact cost goes on the record with it.
Three hours of downtime, priced at this area’s own rate. That’s the impact cost.
Stage 4 of 8 · Plan · Planner
The work request says “vibration high,” and nothing else.
Planned from the call itself. Your CMMS still runs it.
Planner
Scheduled into the boiler outage. Search the work order number and this escalation comes up.
Stage 5 of 8 · Execute · Maintenance crew
The closing note says “replaced brg.” Nothing else.
The analyst sees what they found when they opened it.
Maintenance crew
It wasn’t just the bearing. Six mils of misalignment, and that goes on the record too.
Actual hours and parts go on the record, beside what was planned.
The crew’s part is done. The asset owner signs it back into service.
Stage 6 of 8 · Sign off · Asset owner
“Work order closed” gets read as “problem solved.”
Asset owner
The owner confirms it’s back in service. That’s not the same as closed.
Stage 7 of 8 · Baseline · Field tech
No reading until the next route, weeks away.
Field tech
The same point, measured again after the repair. Without it, there’s nothing to prove the repair against.
On the record beside the first reading. Whether the repair worked is the analyst’s call.
Stage 8 of 8 · Validate · Analyst
A save on paper, with no reading behind it.
Analyst
88% lower and under the alert limit. Now it can close.
Root cause recorded, and it closes. Validated, not just completed.
One record: the call, each decision, and the reading that shows the repair worked.
Analyst
Another machine, a refiner: called at 0.38 in/s, 0.44 after the repair. It came back higher.
So it can’t close as a save. Back to the field tech to recheck the same point.
A closed work order isn’t a save.
See it on your own equipment. A 30-minute walkthrough: one of your asset classes, from the analyst’s call to the validated close.

While it waits for the outage

1:02 · Silent, captioned · Asset owners with work waiting on an outage

Some work can’t move until the outage. One minute on what the escalation carries while it waits.

What it shows and solves

Escalation clauses on the watchlist entry: It’s worse on nights. What did the analyst say?
Duty coverage and site contact: Weeks waiting for the outage, with no named contact if it gets worse.
The Watchlist tab: Work waiting on an outage drops out of sight.

Read the transcript

It’s worse on nights. What did the analyst say?
Waiting for the outage, it carries its own instructions.
Asset owner
Some of this can’t move until the outage. That’s not the same as nothing happening to it.
Two levels and an instruction, written down before anyone needs them.
Coverage — weekday, weekend, overnight — and who to call on site.
Everything under watch, in one place, with its clauses attached.
Written once, while there was time.
See it on your own equipment. A 30-minute walkthrough: one of your asset classes, from the analyst’s call to the validated close.

What the program adds up to

2:06 · Silent, captioned · Reliability directors and PdM program managers

Budget season, and the answer is anecdotes. Two minutes on what the escalation record adds up to.

What it shows and solves

Reliability dashboard: validated saves: “What did the program save us?” Which closed work orders actually fixed something?
Chronic bad actors, with Initiate RCA: The same pump keeps coming back, and nobody has tied the failures together.
Defect analytics: root cause by defect type: Every work order says “bearing,” and the lubrication problem behind them stays hidden.
Missed opportunities and Program health: The failure the program missed gets blamed on “vibration,” or on nothing.

Read the transcript

“What did the program save us?”
Which closed work orders actually fixed something?
Reliability manager
The state of the program, drawn from the escalations, not pulled together by hand.
A save counts only where the repair was validated. An accepted risk is counted as that.
The same pump keeps coming back.
Reliability manager
Repeat offenders surface on their own, with what they’ve cost you.
Second bearing on the same pump. That’s the trigger for a root cause analysis.
It opens here, linked to the escalations that triggered it.
Every validated close carries a root cause. This is what they add up to.
What did the program miss, and why?
Reliability manager
And what the program missed, logged with the same discipline.
Validated closes and logged misses, side by side. A hit rate only counts misses someone logged.
Program health, bad actors, on-time performance — PDF or CSV, on demand.
Counted from the escalations, not assembled by hand.
See it on your own equipment. A 30-minute walkthrough: one of your asset classes, from the analyst’s call to the validated close.

Your asset list in, and how it’s ranked

1:42 · Silent, captioned · Reliability engineers who would set it up

Setup starts with your asset list. See one imported from a CSV, previewed, then an asset scored for criticality.

What it shows and solves

Import loadsheet: map your columns: Months of setup, starting with retyping the asset list.
Preview & commit: An import that rewrites your hierarchy before you’ve seen what changes.
Criticality assessment: four questions: “Everything’s priority one,” so work goes in arrival order.
Provenance on every rating: A stale criticality list, with no telling where each rating came from.

Read the transcript

Months of setup, starting with retyping the asset list.
Reliability manager
Your asset hierarchy, from a CSV: a row per asset or component.
No template to fill in. Keep your column names; confirm what each one means.
What’s new, what’s updated, what would get restructured — before anything is written.
Committed. Assets, components and their ratings, in one pass.
“Everything’s priority one,” so work goes in arrival order.
Criticality feeds the queue, so consequence sets the order.
Reliability manager
Criticality, scored per asset. It’s one of the inputs that ranks every open escalation.
Four questions: safety, production, repair cost and lead time, redundancy.
The tier follows from the four scores, and the reasoning stays on record.
Every rating says where it came from, and when.
Your asset list in. Consequence sets the order.
See it on your own equipment. A 30-minute walkthrough: one of your asset classes, from the analyst’s call to the validated close.

See it on your own equipment.

A 30-minute walkthrough: one of your asset classes, from the analyst’s call to the validated close.

Request a demo