Building Tours through the Schedule vs. the Component Grid

The following can be considered reasons why not to build a tour from the component grid.

Detector Type

Tours built through the Schedule grid will automatically sort components by the detector type required for their specific stream (e.g., FID, PID, OGI). In contrast, tours built through the Component grid will mix all components, regardless of detector type.

Inspection Type

When using the Schedule grid, components are automatically added to tours based on the Inspection Type required by their respective rules (e.g., AVO, M21, OGI). With the Component grid, however, you must manually select the appropriate Inspection Type.

InspectionWhy

Building tours through the Schedule grid assigns each component the designated InspectionWhy based on the rules that add them to the schedule. In the Component grid, you must manually choose an InspectionWhy, which may not meet the requirements set by the rules.

Existing Tours

In the Schedule grid, you can see only components not currently assigned to another tour, reducing the risk of unintentionally reassigning components. However, the Component grid displays all components, including those already part of existing tours. So you may accidentally pull them out of one tour and into another.

Compliance Due Date

Tours built through the Schedule grid automatically apply the most stringent compliance due date assigned by rules for the relevant Inspection Type. When using the Component grid, you must manually set the due date, which then applies to all components within that tour.