Skip to content
Sattari

Fault Investigation

Something is wrong and no one can find it. A Fault Investigation traces the fault to its source, classifies its nature, and states what is required to resolve it. The question it answers is what is wrong, and what kind of fault is it?

When it is commissioned

A Fault Investigation is called for when something specific is wrong and the organization has not been able to resolve it. The cost may be time, money, safety, or trust. The trigger is usually one of three.

  • Something is wrong and no one can find it.

    The symptoms are known and well documented. The cause is not, and the people closest to the problem have run out of places to look.

  • A fix has been applied more than once and has not held.

    The same failure returns after each intervention. The repetition is itself the signal: the fixes are aimed at the symptom, because the nature of the fault has been misread.

  • An auditor, a regulator, or a review has named the failure, but not its cause.

    A response is due, and it has to say what is actually wrong, not only what went wrong.

What is delivered

A Fault Investigation reads as much of the system as the fault requires. It starts where the symptoms appear and follows them back, through the relations that feed them and across the lines between departments, until it reaches the place the fault actually sits. The report delivers three things.

1. The location and nature

The location is often some distance from where the symptoms appear. The nature is one of seven, set out in the Discipline. It matters as much as the location, because a fault whose nature is misread can be patched for years without being fixed.

2. The class of fault

Whether the fault is contained (fixable locally), structural (requiring a new arrangement), located in the system's purpose, or driven by a constraint outside the boundary.

3. The direction of the remedy

The direction of the remedy and the kind of specialist needed to execute it. The report is written to be handed on, so your own people, a vendor, or another firm can execute the repair without diagnosing the problem again.

How it runs

A fault may sit in a single handoff or run through the entire structure. Because we cannot know its reach until we look, every investigation begins by settling where the system's boundary lies and exactly what it is built to do. That first deliverable sets the access required, fixes the fee for the remaining work, and gives you a clean decision point on whether to proceed.

  1. Charter

    The engagement begins with the symptoms. The Charter records the presenting problem, what has already been tried, the system's purpose as you give it, a proposed boundary, and a not-to-exceed fee.

    The signed charter.

  2. First deliverable

    We settle the system's purpose and boundary, drawn around the system rather than the symptom. With them comes an inventory of the access the work requires, and fixed fees for the remaining milestones.

    The purpose and boundary judgment, and the access inventory.

  3. Investigation

    We start where the fault shows and follow it—through the relations that feed the symptom, across the lines between departments, and into the assumptions the system runs on—until the fault is located and its nature named.

  4. Draft report

    You review a draft for errors of fact, and may attach a written response to any finding. We correct the facts the evidence confirms. The findings themselves change only on new evidence, not on request. Your response travels with the final report, together with our reply.

    The draft report.

  5. Final report

    We take you through the findings and the direction of the remedy in a working session. The session equips you to govern the repair, and the engagement concludes with the handoff.

    The final report and working session.

What it asks of you

Your time at four points: at the start to frame the Charter, at the first deliverable to decide whether to proceed, at the draft for a factual review, and at the end for the working session. Access to the documents, the people, and the system in operation—including parts of the structure away from the presenting symptom. And the understanding that a finding may land outside the department that raised the problem: it is delivered to you unedited.

Terms

Fee
From $40,000 for a system within one department. From $60,000 for a multi-department system. From $80,000 for a system spanning organizations.
How it is set
The Charter sets a not-to-exceed ceiling. With the first deliverable, we fix the fee for the remaining work based on the scope and complexity the inventory reveals. Fees are paid by milestone. They change only if the boundary or purpose changes, and are never contingent on findings.
Timeline
The first deliverable generally arrives within two weeks. The final report follows five to eight weeks after your decision to proceed.
Private sector
If a Design Derivation of the same system follows within twelve months, a portion of this fee applies to the new engagement, regardless of the findings.
Public bodies
Invoiced in arrears. This work is usually procured as an organizational assessment, an operational review, or a Public Systems Assessment. We supply the scope-of-services language your procurement office requires.

What it is not

A Fault Investigation is not a Reading. A Reading comprehends the system and notes what it sees along the way. An Investigation starts from a known problem and follows it until its cause is found.

Where the sponsor needs to understand the system as a whole rather than diagnose a specific fault, the product is a Reading. Where every component and relation must be understood and scored, it is a Grade.

Begin with the situation

Describe the system, the symptoms, and what has already been tried. We will confirm whether an investigation is the right instrument, or direct you to the engagement that is.

Begin