BEFORE YOU SAY YES
The questions every operations leader, IT manager and procurement officer asks before piloting FaultPilot. If yours isn't here, get in touch.
01 / THE BASICS
A diagnostic and shift-handover app for mining maintenance. A tech logs a fault on their phone or tablet, gets a diagnosis built from your OEM manuals and your own fleet's history, and hands it cleanly to the next shift.
Operators, contractors and OEM service teams running mixed fleets: the techs on the tools, the supervisors, and the maintenance and asset bosses above them.
The paper logbooks, the group chats, the manuals nobody can search, and the "just ring the senior bloke" knowledge that walks out the gate every roster.
02 / DIAGNOSIS
Trace reads the OEM manuals and fleet history you give it, and hands back ranked causes and step-by-step checks with the source shown next to each step. If it can't back something with a real source, it says so instead of guessing.
No, on purpose. Every step points to a real source and shows a confidence rating. A wrong call out here can hurt someone, so it's built to say honestly that it does not know, rather than bluff.
Yes. It works across whatever's in your fleet, regardless of manufacturer. One spot to look, not five different manuals.
Yes. The app works fully offline and syncs when you're back in range, and you can pull procedures down before you head underground. A dropout never stops a tech mid-fault.
03 / HANDOVERS
One continuous fault record: timestamped, who did what, from first log to final fix. It pre-fills from the shift's actual work and locks once sent, so the next crew picks it up already across it instead of starting over. Roughly 40% of plant incidents happen at handover.
Yes. Ask a question right on the fault, and the answer stays stuck to it for whoever hits that fault next.
No. Supervisors see the work and the handovers, not where someone is or how they use their phone. That's deliberate; it's how you get crews to actually use it.
A reliability dashboard that turns the fault records into the numbers you already report on: MTTR, fleet uptime, fault hot lists, period comparisons. Board-ready and exportable.
04 / SETUP
Nothing heavy. It's a mobile app your techs open. iOS and Android, on the phones and tablets they already carry. No new hardware, no IT project.
Most teams are up and running within a day. We handle setup, import your machine list, and walk your crew through the app on site.
You give us your licensed OEM docs and we get you set up. We can bring in your older faults too, so the fleet's memory isn't blank on day one.
No. FaultPilot fits around how your crew already works. Logging, handovers and diagnostics are built to be faster than the paper or group-chat processes they replace, not more complicated.
Always. Export any fault to a clean PDF with the handover chain, steps, photos and notes, ready for your CMMS. Your data's yours to take with you.
05 / SECURITY
All data is encrypted in transit (TLS 1.2+) and at rest (AES-256), hosted on secure cloud infrastructure in Australia. Each organisation is walled off. One customer's data never touches another's.
Customer data is primarily stored in Australia (Sydney region). Some AI processing involves transfer to the United States, but no data is retained by third-party AI providers after processing.
No. Your data stays in your tenant, we don't train models on it, and our provider agreements ban it too.
You upload your own licensed docs. We don't scrape OEM IP or train on copyrighted content. It's processed privately, per organisation.
Yes, ready to go: InfoSec policy, incident response plan, data classification, acceptable-use policy and a vendor risk register. Built for due diligence, not bolted on. We'll hand your IT team the hosting details and an SLA for their review.
It's yours. Your data is available for export for 90 days after cancellation, then permanently deleted, or sooner on request under the DPA. No lock-in on your data. Full details are in our Data Retention Policy.
Yes. The suite's drafted by Australian counsel and available for procurement review: Privacy Policy, Data Processing Agreement, Data Retention Policy, Service Level Agreement and Authorised User Terms, all on our Legal page.
06 / FIT
No. They stay your system of record for planned work. FaultPilot grabs what actually happens in the field, the bit between the field and the office, and exports clean records into your CMMS. No rip-and-replace; it's in within days.
A CMMS is a record of what should happen. FaultPilot captures what actually happens when a tech's standing in front of the machine. Different job, different price.
Most tools out there are locked to one manufacturer's gear. We work across whatever's in your fleet. That's the whole point.
Enterprise tier includes API access and custom integrations with existing maintenance management systems. Contact us to discuss your requirements.
07 / GETTING STARTED
Fault logging, the Trace diagnosis engine, the shift-handover chain and the reliability dashboard. iOS and Android, full offline. Pilots are under way with Australian operators, contractors and OEM service teams. Fault diagnosis and handover is what's live and proven today, and that's what you'd be buying.
A 30-day pilot: $5,000 flat, no lock-in, and the pilot fee comes off year one. Bring one fleet and one crew, we agree what "good" looks like up front, and within weeks we measure time-to-diagnosis and time-to-repair on your own machines.
Priced per head per month across three tiers: Core, Pro and Enterprise. It's in within days, not the six-figure rollout a SAP or Maximo project takes. Contact us for a quote on your operation.
Depends on your site, but the maths isn't close. If an hour of unplanned downtime costs you around $5,000, and on a lot of gear it's well north of that, avoiding a handful of hours across the year covers the bill. Most sites lose that in a single bad shift. They're your numbers to run, not ours.
Email support@faultpilot.com.au and you'll hear back within a business day. Anything urgent on shift, your supervisor can escalate straight to us. Feature suggestions go straight to Aaron, the founder. He reads every one himself.