Skip to main content

Paid 30-day pilot

Start narrow. Earn the rollout.

A paid operating test for one site, one crew and one workflow, with the scope and evidence agreed before work begins.
  1. 01

    Scope

    Agree the site, crew, fleet slice, workflow, devices and success criteria.

  2. 02

    Configure

    Set up the organisation, approved technical sources and demonstration or site records required for the test.

  3. 03

    Operate

    Run the agreed workflow with direct onboarding, support and a defined escalation path.

  4. 04

    Review

    Compare the agreed evidence, document limitations and decide whether a broader rollout is justified.

Included

A defined operating test, not an open-ended trial.

  • One site and one agreed crew
  • One supported operating workflow
  • Configuration and onboarding
  • Agreed measurement plan
  • End of pilot review and next scope recommendation

Mutual operating commitment

Named owners on both sides.

The responsibilities and stop conditions are agreed before the test begins.

CommitmentFaultPilotSite
OwnershipA named product owner and documented support pathA named site counterpart and decision owner
Operating inputsConfiguration of the agreed workflow and evidence planApproved access, source data, devices and crew availability
Review cadenceDocument progress, issues, limitations and actionsAttend agreed checkpoints and confirm site decisions
Stop and decidePause if the agreed safety, access, data or workflow boundary cannot be maintainedEnd with an evidence summary and a rollout or no rollout decision
What we will measure

Compare the way the work moves.

BaselineDay 30

Pilot evaluation measures and their evidence sources
MeasureDefinitionEvidence source
Fault context completenessAsset, symptom, evidence, owner and next actionFault and activity records
Handover continuityWork completed, blockers and next action carried forwardJob and shift handovers
Time to useful actionFrom fault report to the first recorded check or decisionAttributed workflow activity
Repeat fault visibilityPrior repair history available when the same asset returnsAsset and fault history
The baseline, target and acceptance method are agreed with the site before the pilot starts.

At the end of the pilot

A decision package, not a demo recap.

The review stays tied to the operating boundary and evidence agreed before work began.

  1. 01

    Evidence summary

    The agreed baseline, pilot evidence and observed limitations in one review.

  2. 02

    Fit and gaps

    A documented view of what FaultPilot supports, what the current process keeps and what remains separately scoped.

  3. 03

    Rollout decision

    A rollout or no-rollout recommendation, with a next scope defined only where the evidence supports it.

The commercial terms, operating scope and success measures are confirmed in the proposal before kickoff. Read the pilot checklist.

Request pilot scoping