Technician copilot

Give technicians a diagnostic path, not just an alarm description

A field technician at Northfield Water sees E-41 on a PX-400. An alarm table identifies the code but leaves the next decision to experience. Structured troubleshooting can connect likely causes to checks and remedies for that unit.

See the comparison

The task in this example

E-41 on this PX-400. What do I check first?

Business goal: Build brand loyalty
Business metric: First-time fix rate

The alarm stays the same; the diagnostic evidence changes

The pump has a blocked flush line in both cases. The comparison concerns the guidance available to the technician.

The code has no diagnostic path

The alarm entry names E-41 without causes or checks.

The technician replaces a seal without first testing the actual cause.

Guidance: Alarm description only
Cause assessment: Unverified
Repair: Seal replaced; blockage remains

The problem requires another visit

The topic links cause, check, and remedy

The applicable topic places the flush-line check before unnecessary replacement.

The technician follows the approved safety procedure and diagnostic check, confirms the blockage, and applies the documented remedy.

Guidance: Applicable cause/check/remedy sequence
Cause assessment: Blocked flush line confirmed
Repair: Documented remedy verified

The first visit addresses the identified cause

Connect diagnostic guidance to the service outcome

The copilot’s recommendation is only an intermediate step. The technician must verify the cause, perform the approved work, and confirm operation before the visit counts as a successful fix.

Retrieve applicable checks

Use the model, options, and alarm to select guidance.
- Causes in the right order
- Lockout steps included
Confirm and repair

The technician records the cause and verifies the remedy.
- Unneeded parts
- Field fixes added

Business metric

First-time fix rate

Measure cases resolved on the first visit without a repeat visit for the same unresolved cause.

What to measure and how to interpret it

Review cases by alarm, configuration, and fault type. Have service experts assess applicability and diagnostic order; frequency in a model’s answer is not evidence of cause likelihood.

Causes in the right order: Share of reviewed answers following the service-approved diagnostic order for the identified unit.
Lockout steps included: Share retaining all applicable approved isolation and safety instructions in the retrieved procedure.
Unneeded parts: Parts replaced without evidence that replacement addressed the confirmed fault.
Field fixes added: Newly confirmed field findings reviewed and incorporated into maintained troubleshooting topics.

Check the business result

Compare first-time fix rate for similar service cases and track repeat visits, repair time, and parts use. Safety deviations remain a separate stop condition; a faster visit does not justify skipping the approved procedure.

Schedule a call

Structure the reasoning a technician needs to check

The content should separate a possible cause, the approved check that can confirm it, and the remedy that follows. This page illustrates that structure rather than supplying service instructions.

PX-400 / E-41 / Diagnostics

Troubleshooting entry

Cause → check → remedy

For this example, a blocked flush line is the cause to investigate before replacing a seal.

Applicability: Model, options, and firmware recorded
Safety dependency: Applicable approved isolation procedure
Possible cause: Blocked flush line
Check: Referenced approved diagnostic check
Remedy: Referenced approved procedure after confirmation
Completion: Record cause, work performed, and verification result

Intelligent content

Maintain cause, check, remedy, prerequisites, and safety dependencies together. Keep the diagnostic logic in retrievable units.

Taxonomy

Classify alarms, models, options, and firmware consistently so the copilot excludes checks for a different unit.

A practical starting point

Select one frequent alarm and have service experts validate its diagnostic topic against a sample of field cases. Test retrieval and safety-context retention before field use.

Service experts approve diagnostic and safety procedures. Installed-base data identifies the unit; the technician decides whether conditions permit the work and verifies the result.

See how this scenario works