Software guide

CZ800: Inspection routes and execution

Create route plans, capture each execution point, record skipped or abnormal points and complete a reportable inspection.

On this page
CZ800 guide chapters

Based on operating notes recorded on 21 September 2026. This date is not a release version; applicability to your installed software must be confirmed.

A route is a plan; an execution is one inspection

An inspection route organizes equipment measurement points into an order and assigns an acquisition template to each. An execution records which points were measured, abnormal or skipped during one inspection and associates the actual acquisition records.

Editing a route plan does not change the saved snapshot of an execution that has already started.

Create an inspection route

  1. Create the necessary equipment and points in Equipment Management.
  2. Open Inspection Routes, click New Route and enter a name.
  3. Select one or more points in the point selector and add them to the end of the route.
  4. Choose an existing template for each point and check its name, sample rate and sample count.
  5. Use Move Up to adjust order and Remove to remove a point added by mistake. A route needs at least one point.
  6. Save the route and inspect its name, point count, order and templates on the route card.

Template selection assigns an existing template. It does not establish that this page can create or edit arbitrary templates. Repeated selection of the same point does not create unlimited distinct locations; create real, separate measurement points when locations differ.

Start or continue an execution

Click Start/Continue on the route. If an execution is already in progress, the page continues it. Otherwise, it creates a new execution and saves a snapshot. Before measuring, check the current route, point names, templates and statuses.

Progress displays processed points out of total points. Skipped points count as processed but were not acquired. Distinguish measured points from skipped points in reports and human review.

Acquire an execution point

  1. Click Acquire This Point or Acquire Next Point in the execution panel.
  2. The software opens the acquisition/analysis workspace with this execution and point context.
  3. Check the point, template parameters and connection state, then start acquisition as required by that page.
  4. After a complete record is saved, the inspection workflow links it to the execution and submits progress.
  5. If progress submission fails, check the saved record and use the submission-retry flow. A submission error does not establish that the capture was lost.
  6. Return to the inspection panel and check the result, record ID and processed count before moving to the next point.

Independently selecting a point in ordinary acquisition does not necessarily update an inspection execution. Enter from the execution point when a route association is required, so the record is linked to the correct inspection.

Skipped points, status and field notes

For a point that has not been processed, enter a skip reason and choose Skip This Point. For a point with an acquisition record, review it, choose Normal or Abnormal, add field notes and save.

Skipping truthfully records a measurement that was not performed; it does not generate measurement values. Normal/Abnormal status can include human judgment and should reflect the record and operating condition. It is not a standards-based grade conclusion.

Skipped and measured points have different subsequent actions. Use the controls actually available for that point state.

Complete an inspection and review history

Complete Inspection becomes available when all points have been processed and the execution is still in progress. Complete it and check the resulting status. All points being processed does not mean all were successfully measured; review skip counts and reasons.

Open Execution History on the route to inspect batches, times, progress and status. Open a batch to view its saved execution snapshot.

In the Report Center, select Inspection Execution as the scope, then select the same route and the specific execution batch. See reports and data export.

Edit or delete a route

Route editing changes the planned name, point order and templates. An active execution continues to use its saved snapshot.

Deleting a route requires confirmation and remains subject to backend rules. Deleting the route does not stop a current acquisition task and should not be used to clear an unresolved inspection problem.

The recorded AI integration provides read-only route and execution queries. Manual route controls do not imply equivalent AI operation support.