Non-LDAR Inspection Tasks

You can use the scheduling and tracking function in Chateau to schedule and track non-inspection tasks important to your LDAR program.

You do this by creating a special Task LUnit, a Task Rule, and then inputting each Task into Chateau as a component. This will enable you to schedule, assign, track, and confirm all of the regularly-occurring tasks important to your LDAR program.

  1. Create LUnit in Resources equal to Tasks.

  2. Create a Stream equal to Tasks.

  3. Create a Type in Settings / Picklists equal to Task.

  4. Create SubTypes in Settings / Picklists equal to the type of Task you will be scheduling, such as:

    a. Cooling Tower

    b. Quarterly PreCal

    c. Probe Integrity Checks

    d. Audit Cylinder Certification Documents

    e. Etc.

  5. Create a Task Rule.

    a. Regulation equal to Task.

    b. Edit the Rule specs to set the frequency for each SubType using GV as the Physical State.

    c. Assign Rule to the LUnit equal to Task.

  6. Create a “Component” for each task with Add Component from Scratch in the Component grid. Assign a Tag number with a leading T, such as T1, T2, T3, etc. For Instance:

           a. Tag Number: T1

           b. Type: Task

           c. Subtype: Cooling Tower

           d. Physical State: GV

           e. Location Description (be as general or specific as you want)

           f. Stream: Task

  • Note: In this as in other cases, you can make the Cooling Tower task “all of the cooling towers” or you can create a separate task for each Cooling Tower, or for the Cooling Towers in
  1. When the rules are run, the LUnit will appear in the Queue with the Tasks shown on the schedule.

  2. When each task is complete, you can mark the tasks with an AVO equal to DONE either in Chateau Mobile, or with a manual AVO inspection entry in the Inspections Attempts tab.

Was this article helpful? If not, please submit feedback below.


Queue Terms