Setting up the Alternate Work Practice involves three things: turning on AWP mode and its survey options, building an AWP rule, and building the tour the technician will survey. This is an administrator task.
New to AWP? Start with Alternate Work Practice (AWP): Overview and Terms.
1. Turn on AWP mode
Go to Settings > OGI Settings and configure the following:
- Testing Protocol — toggle from OOOOa to AWP. When you select AWP, Chateau displays a disclaimer confirming that Path Inspections are assigned based only on the Route Sequence or Tag Number order between two milestones and the technician's authorization to assign them. You must accept this to enable AWP.
- Path Inspection Basis — choose how Chateau decides which components fall between two milestones:
- Order of Tag Number — components whose tag numbers fall sequentially (natural sort) between the two milestone components.
- Route Sequence — components in the predefined route sequence between the two milestone components.
2. Set the Milestone Interval (per technician)
The Milestone Interval is the number of minutes after which a technician is reminded to record another milestone. It is set per technician in Resources > People.
- The person must have the Technician role for the setting to appear.
- You must be an Administrator of the database to edit it.
- New technicians default to 800 minutes, which effectively turns the reminder off. Choose the value based on how the technician places milestones:
- Leave it at 800 minutes if the technician creates milestones by physical area or section (their own boundaries) rather than on a clock. They will not be prompted at a time interval.
- Set a shorter interval if you want to remind the technician based on video length — so each session stays short enough to fit a single milestone video. A shorter interval (for example, 20 minutes) prompts them to close and open sessions on that cadence.
3. Build the AWP rule
Build a rule for the Alternate Work Practice and apply it to the components being surveyed. An AWP rule typically requires:
- an Annual Method 21 inspection frequency,
- an OGI inspection frequency (for example, bimonthly), and
- the repair/response deadlines your regulation requires.
Decide what a failing OGI inspection should do
How you configure the rule's OGI response ranges determines what happens when a technician records a failing OGI inspection:
- With OGI response ranges configured: a failing OGI inspection automatically opens an OGI leak with rule-driven response deadlines. Use this if you want the OGI inspection itself to drive the leak.
- Without OGI response ranges: a failing OGI inspection is recorded only as a fail — no leak is opened. This supports a common downstream workflow: use the OGI survey to find potential leaks, then schedule a technician to return and confirm each OGI fail with a Method 21 inspection. The confirming M21 inspection opens an M21 leak, which is then handled through your normal M21 leak-and-repair process.
Choose the approach that matches how your program confirms and documents leaks. See the Rules articles for the mechanics of building and applying rules.
4. Build and assign the tour
Build a tour that contains the components to be surveyed — typically all components in a LUnit or area — and assign it to the technician.
Important: Path Inspections are only created for components in the currently checked-out tour. Technicians should not merge tours while performing AWP, or components from other tours can interfere with path creation.
Comments
0 comments
Please sign in to leave a comment.