Fault Code Rules Engine

What is this?

Fault codes come in from your equipment all day long. Some are critical and need a mechanic on site immediately. Others are nuisance codes that fire every time a machine starts up cold. Until now, you had to manually triage every single one.

The Fault Code Rules Engine lets you set rules once and let the system handle the rest. You pick a fault code, decide what should happen when it comes in, and Clue follows that rule every time. Critical codes can auto-create work orders. Nuisance codes can be auto-dismissed. You stay in control without watching every alert.

Who is this for?

• Maintenance Managers - Set critical fault codes to auto-create work orders. Your shop gets the job before you even see the alert.
• Fleet Admins - Override OEM severity levels. Just because the manufacturer calls it "Minor" does not mean it is minor for your operation.
• Mechanics - Fewer false alerts cluttering your queue. The codes that do not matter get handled automatically.

How to use it

Step 1: Open Fault Code Rules

Go to Company Settings in the sidebar, then Configuration, then click the Fault Code Rules tab. You will see a list of all active rules for your company.

Step 2: Create a new rule

Click + Add Rule. Fill in the rule name, the fault code identifier, choose a severity override if needed, and pick the action.

Each rule has four parts:

• Rule Name - A label your team will recognize (like "DEF SCR Inducement" or "Regen Needed")
• Code Identifier - The exact fault code to match (like E1389, SPN 3936, or any code your OEM sends)
• Override Severity - Change the OEM severity to what makes sense for your fleet (Critical, Monitor, Minor, or leave as-is)
• Action - What happens when this code comes in

Step 3: Pick the right action

Every rule needs an action. Here is what each one does:

• Keep Alert - Shows the fault code as a normal alert. Use this when you only want to change the severity level.
• Auto-Dismiss - Marks the code as dismissed automatically. The code still gets recorded in history, but it will not show up in active alerts.
• Create Work Order - Generates a work order automatically, linked to the asset. Pick the priority: High, Medium, or Low. The system checks for existing open work orders on the same asset and code before creating duplicates.
• Log Silently - Records the code in history but does not show it anywhere. Useful for codes you want to track long-term but do not need to act on.

Common rules to set up

Here are examples that most fleets benefit from right away:

DEF/SCR inducement alerts (auto-create work order)

When a machine enters DEF inducement, it will derate or shut down if not addressed. Set code E1389 (or your OEM equivalent) to Create Work Order at High priority with severity Critical. A mechanic gets the job immediately.

Engine overtemp or low oil pressure (auto-create work order)

These are safety-critical. Continued operation causes permanent damage. Set these to Create Work Order at High priority. Better to pull a machine off the line than replace an engine.

DPF regen needed (keep alert, bump severity)

Not an emergency, but ignoring it leads to forced regen and downtime. Override severity to Monitor and use Keep Alert. The maintenance team sees it and can schedule a regen during a break.

Cold-start idle codes (auto-dismiss)

Many machines throw fault codes during cold startup that clear on their own. If a code fires every morning and resolves in 5 minutes, set it to Auto-Dismiss. It still shows in history if you ever need to look back.

Tire pressure monitoring (log silently)

Some tire pressure warnings trigger constantly on rough terrain. Use Log Silently to keep a record without filling the alert queue. Review the logs monthly to spot real trends.

The full details

• Works on: Web app (rules apply to all incoming OEM telematics data)
• Location: Company Settings > Configuration > Fault Code Rules
• One rule per code: Each fault code identifier gets exactly one rule per company
• Severity scale: Critical (3), Monitor (2), Minor (1), Unknown (0)
• Overridden codes are visually marked throughout the app so your team knows the severity was changed from the OEM default
• Work order deduplication: If a fault code already has an open work order on the same asset, the system will not create another one
• Applies to new data only. Rules take effect as new codes arrive from OEM sources. Existing fault codes are not changed retroactively.
• Migrated from auto-dismiss: If you had auto-dismiss settings before, they have been automatically converted to rules
• Permissions: Admin access required to create and edit rules

Tips

• Start with your top 5 noisiest codes. Check your fault code dashboard for the codes that fire most often. Set rules for those first and your alert queue gets quieter immediately.
• Use descriptive rule names. "DEF SCR Inducement" is better than "Rule 1". Six months from now, you will want to know what each rule does at a glance.
• Review your rules quarterly. Fleet composition changes. A code you dismissed on older machines might matter on newer ones.
• Do not over-dismiss. It is tempting to auto-dismiss everything annoying, but some of those codes carry useful diagnostic information. Use Log Silently if you are unsure.
• Set Create Work Order for anything that causes derate or shutdown. DEF inducement, high exhaust temperature, critical oil pressure. If a machine stops working because of it, it deserves an automatic work order.