Choose the use case
Select a machine, system or recurring event where investigation is currently difficult, slow or dependent on operator memory.
OUTPUTAgreed pilot scope and success questionRootTruth PILOT PROGRAMME
Prove the value on real events.
A RootTruth™ pilot is a focused engineering evaluation designed to answer one question: does better event evidence help your team investigate faster, reduce recurrence and protect production time?
PILOT SCORECARD
01BaselineHow investigations work today
02EvidenceReal machine events captured
03OutcomeTime, recurrence and impact compared
04DecisionFit, value and next steps reviewed
A CONTROLLED EVALUATION
Small scope. Real events. Measurable outcomes.
The pilot should be large enough to prove whether RootTruth™ helps, but small enough to remain easy to deploy and evaluate.
Establish the baseline
Record how the site investigates today: typical investigation time, repeat-event behaviour and operational impact.
OUTPUTBefore-RootTruth reference pointConnect RootTruth
Configure the required PLC signals, event trigger and relevant cameras using the existing site infrastructure wherever practical.
OUTPUTWorking capture and replay configurationCapture real events
Allow representative events to occur naturally and use RootTruth™ as part of the normal engineering investigation process.
OUTPUTReal investigation evidence and casesReview the result
Compare the pilot against the baseline and decide whether the outcome justifies a wider commercial deployment.
OUTPUTEvidence-based go / refine / stop decisionWHAT WE MEASURE
Evidence before claims.
Not every site will create value in the same way, so the pilot focuses on the measures that matter for that operation.
Investigation timeHow long it takes engineering to move from event occurrence to a credible root-cause conclusion.
Repeat-event frequencyWhether the same fault or failure mode returns after corrective action.
Downtime impactThe production time associated with diagnosis, repeated failures or delayed recovery.
Evidence qualityWhether engineers can see the relevant video, PLC transitions and event context when they need it.
Cases resolvedThe number of investigations that reach a documented root cause and resolution.
Knowledge retainedWhether useful root-cause and fix information becomes searchable for future investigations.
PILOT SCOPE
Start where the pain is clearest.
A useful first pilot does not need to cover an entire factory. A single machine, system or high-value event class can be enough to establish whether RootTruth™ changes the investigation process.
Good first targetsIntermittent faults, repeat stops, complex sequences, quality events and problems that clear before engineering arrives.
What RootTruth needsAccess to the relevant PLC data, an agreed event trigger, and camera coverage where video is part of the evidence set.
What the customer providesA technical contact, access approvals, the real-world use case and honest feedback throughout the evaluation.
What YellowCore providesPilot configuration support, workflow guidance, technical review and a structured end-of-pilot assessment.
END-OF-PILOT REVIEW
Finish with a decision, not an open-ended trial.
Value demonstrated
Define the wider deployment scope, licence tier and integration plan.
Promising, but incomplete
Adjust configuration, event selection or workflow and run a focused follow-up evaluation.
No meaningful fit
If RootTruth™ does not materially improve the investigation process, the pilot should make that clear too.
FROM PILOT TO PROOF
Successful trials become evidence.
Where a customer approves it, verified pilot outcomes can later become a case study using real metrics, a customer quote and approved branding. Until then, YellowCore will not publish invented proof.
HAVE A GOOD PILOT USE CASE?