Automatic AVO Leaks (AVO Response Ranges)

When a technician reports a failing AVO inspection, Chateau handles it one of two ways, depending on how the affected component's rules are set up:

Automatic AVO Leak — if the component has a rule with an AVO Response Range covering it, Chateau opens an AVO Leak immediately, with response deadlines taken from the rule. This works the same way OGI and M21 leaks do.
AVO Event (manual triage) — if no rule covers the component with an AVO Response Range, Chateau creates an AVO Event instead. The event waits in the AVO Events subtab for someone to decide whether it's really a leak. See AVO Events.

Which path a component follows is entirely a matter of its rule configuration — so you control it, component by component, through your rules.

Already using AVO Events? You can keep triaging failing AVOs by hand exactly as you do today — that's the behavior for any component whose rules have no AVO Response Ranges. Adding AVO Response Ranges is optional: do it only for the components where you want failing AVOs to become leaks automatically.

Which should I use?

Choose automatic AVO Leaks when a failing AVO on a component is always a leak with a known response clock — so a manual "is this really a leak?" step adds no value and only delays the response deadline. Common cases: OOOOb components, or any program where an AVO failure goes straight into a repair timeline.

Choose AVO Events when a failing AVO genuinely might not be a leak (a drip that could be water, a smell that could be something else) and a person should decide before the repair clock starts.

You can use both at the same facility — see Components with more than one rule.

Setting up automatic AVO Leaks

Go to the Rules module and edit (or create) the rule that applies to the components in question.
Open AVO Response Ranges — it sits alongside M21 PPM / OGI / Cooling Tower Response Ranges.
Add one or more response ranges, entering the response deadlines: First Attempt / First Retest / Final Resolution, in either calendar or business days. You can scope a range to specific component properties (physical state, component type, UTM/NDE/CVS flags) or leave it as a catch-all default.
Optionally check Index off First Attempt — First Retest and Final Resolution will show "TBA" until the first repair attempt is recorded, then count from that date (e.g., for OOOOb compliance).
Save the rule.

Any component assigned to a rule with AVO Response Ranges uses automatic AVO Leaks. See Rules Terms and Create and Select Rules for full detail on configuring response ranges.

What happens when a failing AVO comes in

For a component that has at least one applied rule with an AVO Response Range covering it, a failing AVO inspection results in:

An AVO Leak created automatically. No AVO Event is created.
The leak's open date set to the inspection's Date Performed.
Response deadlines taken from the best-matching response range on the rule. If several ranges could apply, Chateau uses the most specific match (same matching logic as OGI).
The regulation on the leak taken from the rule that produced the match.
The leak appearing directly on the Leaks grid, ready for repair — no manual triage step.

A passing AVO inspection does nothing.

Components with more than one rule

Most components have more than one rule applied. The decision is made per component, not per rule:

If any applied rule has an AVO Response Range that covers the component, a failing AVO creates an AVO Leak — and no AVO Event is created. It does not matter that the component's other rules have no AVO Response Ranges. One covering rule is enough.
An AVO Event is created only when none of the component's applied rules contribute a covering AVO Response Range.

In other words: a component produces AVO Events only when none of its rules are set up for automatic AVO Leaks. One covering rule is enough to route that component to automatic AVO Leaks instead.

(If more than one applied rule covers the component, each produces its own AVO Leak with its own deadlines — the same as OGI.)

At a facility with mixed setup

Because this is driven by the rules on each component, different components can behave differently at the same facility. If two failing AVOs arrive in the same batch — one component with a covering rule, one without — the first becomes an AVO Leak and the second becomes an AVO Event.

When a leak is NOT created automatically (safeguards)

Even with AVO Response Ranges configured, Chateau will not open a duplicate or competing leak. A failing AVO creates no new leak if, at the time of the inspection, the component already has:

an open leak of any type (M21, OGI, AVO, or Cooling Tower),
an active Delay of Repair (DOR), or
an open AVO Event.

Editing an inspection

Change a result from fail to pass → the automatically-created AVO Leak is removed.
Change a result from pass to fail → Chateau re-evaluates and creates the AVO Leak (if no safeguard above applies).

AVO Events — the manual triage workflow (used when a component has no rule with a covering AVO Response Range)
AVO Inspections
Rules Terms
Create and Select Rules