When you find a leak during an Alternate Work Practice survey, the leaking component must be recorded as a standard failing OGI inspection — never as a milestone or a path inspection. A failing OGI inspection does not trigger the milestone prompt and stops the Milestone Interval timer.
There are two accepted ways to handle a leak. The choice is mainly about how you want to survey the section and tag its milestone video — not about when you happened to spot the leak.
Method 1 — End the session before the leak
Use this when you want to break the section at the leak — ending the session (and its milestone video) on the component just before the leaking one.
- Record an Ending Milestone on the component immediately before the leaking component in the route. This closes the current session and creates path inspections up to (but not including) the leaking component.
- Select the leaking component and record a failing OGI inspection. No milestone prompt appears for a failing inspection.
- Tag the image/video and complete the standard leak workflow (repair attempt, retest, etc.).
- Record a Starting Milestone on the component immediately after the leaking component to begin the next session.
Method 2 — Survey the whole section, then correct
Use this when you want to survey the entire planned section in one continuous pass and tag a single milestone video for the whole section. You note the leaks as you go, close the section with one ending milestone, then go back and correct the leaking components. This is common when several leaks are found in one section.
- Note the leaking component(s) but continue the session.
- Record an Ending Milestone on a component past the leaking component(s). Chateau creates path inspections for everything in between — including the leaking components.
- For each leaking component: open its Full Details > History, select the auto-created Path Inspection, and delete it.
- Record a failing OGI inspection on that component, tag the image/video, and complete the leak workflow.
- Repeat for each leaking component in the session.
- Return to the ending milestone component and record a Starting Milestone on the component immediately after it to begin the next session.
Key rule
For any OGI inspection with a result of fail, the milestone prompt never appears. The failing inspection is recorded as a standard OGI inspection and does not participate in the session. This is why a leaking component must never be left as an auto-created path inspection — the path inspection would incorrectly show the component as passing.
Comments
0 comments
Please sign in to leave a comment.