Inspection

Online inspection is generally carried out in IC-Inspection (see IC-Inspection) or IC-Inspector (see IC-Inspector) . Inspection data is then synchronised and transferred to NEXUS IC, where you can perform an offline review of inspection data on the INSPECTION screen.

The general process is depicted in the figure and described below.

Note

This workflow represents a simplified version of a basic inspection process. Your specific process may vary based on your unique business requirements and implementation.

Click a node for more information.


Data Aquisition
Create in NEXUS IC
Event
Import
Sync from
IC-Inspector
Sync from 
IC-Inspection
Review
Event
Finding
Anomaly
Review
Finding
Automatic/Manual
Record
Optional record
Track Repositioning
Rerun Anomaly Triggers
Automatic
Process step
Optional process step
Link to Anomaly
Mark Insignificant

  1. In general, inspectors complete tasks in IC-Inspector or IC-Inspection and from the tasks, events are created. Event data are then synchronised to NEXUS IC. However, it’s also possible to import events or create them manually in NEXUS IC (see Create Events).

  2. In case data in an event violates an anomaly trigger, a finding is automatically created.

  3. Engineers or review teams review events in NEXUS IC (see Review Events) and if they have concerns or significant observations regarding an event, they can raise a finding manually (see Create Findings).

  4. Findings are then reviewed to decide if they have to be escalated and linked to an anomaly (see Link Finding to Anomaly).

  5. In case you use the services of a survey company that performs the post-processing of survey data, you need to perform track repositioning, that is, you need to update the survey data in the NEXUS IC database by importing the smoothed survey data that they provided (see Track Repositioning).

  6. After track repositioning, we recommend that you re-run the anomaly triggers (see Run Anomaly Triggers).