Module 1: NEXUS for 3.4U Inspectors - Overview & Foundation

Module 1: NEXUS for 3.4U Inspectors

Overview & Foundation - Your First Steps
⏱️ Reading time: 15-20 minutes | 📱 Mobile-friendly | 🖨️ Printable

🎯 What You'll Learn

By the end of this module, you'll understand:

  • Why clients use NEXUS and your role in the inspection data chain
  • The 5 core concepts you need to start your first job (ignoring the other 95% for now)
  • How to navigate a workpack and understand your tasks
  • The basic workflow from receiving a job to completing inspection data entry
  • Common mistakes to avoid in your first week

Welcome to NEXUS - Let's Cut Through the Overwhelm

Here's the truth: When you first open NEXUS, you'll see screens full of buttons, menus, panes, grids, and options. It's overwhelming. Hundreds of features staring at you.

Here's what you actually need: For your first inspection job, you need to know about 5 things. That's it.

💡 The 80/20 Rule: 80% of your daily work uses 20% of NEXUS features. This module teaches you that critical 20%. The rest? You'll learn it when you need it.

What Is NEXUS?

NEXUS IC (Integrity Client) is inspection management software used by major offshore operators and clients like:

  • TechnipFMC
  • Subsea7
  • Shell
  • BP
  • Equinor
  • And many others

What it does: NEXUS manages the entire lifecycle of subsea asset inspections:

  • Asset hierarchies (what exists where)
  • Inspection planning (what needs inspecting when)
  • Data collection (recording inspection results)
  • Anomaly tracking (defects and their remediation)
  • Risk assessment (integrity scoring)
  • Reporting (client deliverables)
🎯 Your Role as 3.4U Inspector: You are the technical eyes and hands. Your job is to record accurate inspection data in NEXUS so the client can make informed decisions about asset integrity. The quality of your data directly impacts multi-million pound decisions.

Why Clients Use NEXUS

Instead of: Spreadsheets, Word docs, emails flying everywhere, data lost, inconsistent formats

NEXUS provides:

  • Single source of truth - All inspection data in one place
  • Historical tracking - See what was found on this asset 5 years ago
  • Standardized data - Everyone records the same way
  • Traceability - Who inspected what, when, and what they found
  • Automated reporting - Generate client reports with one click
  • Risk-based planning - Prioritize inspections based on asset condition
📊 Industry Standard: NEXUS experience on your CV = higher day rates. Clients specifically request NEXUS-trained inspectors. This skill pays.

Understanding the Inspection Data Chain

You're not working in isolation. Your NEXUS data flows through a chain of people and purposes:

📍 The Journey of Your Data

  1. You (3.4U Inspector)
    Record inspection events, findings, measurements, photos in NEXUS during/after the dive or ROV run.
  2. Client Representative
    Reviews your data for completeness and accuracy. Asks questions if something's unclear. Approves or requests corrections.
  3. Integrity Engineer
    Analyzes your findings. Assesses risk. Decides if anomalies need action. Plans future inspections.
  4. Asset Owner/Operator
    Makes business decisions: repair now? defer? change inspection frequency? All based on YOUR data.
⚠️ Why Data Quality Matters: If you log "corrosion observed" without measurements or photos, the integrity engineer can't assess severity. The asset might get unnecessarily shut down (costing £millions) OR dangerous corrosion might be missed. Accurate, complete data matters.

What Makes Good Inspection Data?

Good data is:

  • Accurate - Measurements are correct, descriptions match reality
  • Complete - All required fields filled, photos attached, measurements recorded
  • Timely - Entered during/immediately after inspection while fresh
  • Clear - Someone reading it 5 years later understands what you found
  • Consistent - Uses standard terminology and classifications

Bad data is:

  • Vague: "some damage noted" (what kind? where? how severe?)
  • Incomplete: Missing photos or measurements
  • Late: Entered days later from memory (details forgotten)
  • Inconsistent: Using non-standard terminology

The 5 Core Concepts You Must Understand

Everything in NEXUS revolves around these 5 concepts. Master these, and the rest makes sense:

1. Asset
The physical thing being inspected. Could be a manifold, pipeline, riser, PLET, anode, clamp, or any subsea structure/component.
2. Workpack
A collection of inspection tasks grouped together. Usually represents a campaign or mobilization (e.g., "2024-Q1-Subsea-ROV").
3. Task
A specific job to be done. "Perform GVI on Manifold XYZ-M001". Tasks live inside workpacks and are assigned to you.
4. Event
An inspection action that completes a task. When you actually DO the GVI and record it, that's an event. Events contain all your inspection data.
5. Finding
Something specific you discovered during the inspection. Corrosion, damage, wear, debris, missing components, etc. Findings attach to events.

How They Connect

🔗 Real Example - GVI on Subsea Manifold

Asset: "XYZ Field - Manifold M001"

Workpack: "2024-Q1-Subsea-Inspection"

Task: "GVI of Manifold M001 - Check all flanges, anodes, and structural integrity"

Event: "GVI performed on 15-Jan-2024 by ROV Hercules, Inspector: J.Smith"

Findings:

  • Finding 1: "Corrosion on NE corner flange - 25mm dia patch, depth ~2mm"
  • Finding 2: "Anode #3 (NW) depleted to 40% remaining"
  • Finding 3: "Marine growth - light coverage across top plate"
💡 Think of it like this:
Asset = The house
Workpack = The inspection contract
Task = "Inspect the roof"
Event = You actually inspecting the roof on Tuesday
Finding = "Found 3 missing tiles and moss growth"

Additional Terms You'll Encounter

Anomaly
A finding that's being tracked long-term. Not all findings become anomalies - only significant defects requiring monitoring or remediation.
Event Type
The kind of inspection: GVI (General Visual), CVI (Close Visual), UT (Ultrasonic Testing), ACFM, MPI, CP Survey, etc.
KP / Elevation
Location markers. KP = Kilometre Point (for pipelines). Elevation for vertical structures. Helps pinpoint exactly where something is.
Asset Hierarchy
How assets are organized in a tree structure. Field → Platform → System → Component. Like folders on a computer.
⏭️ Ignore for now: Planning Templates, Risk Models, Shutdowns, Sensors, Library Items, Functions, Configurations. You don't need these to complete your first inspection. Client reps handle this stuff.

Understanding Your Workpack

When you arrive on the vessel, the client rep will assign you a workpack. This is your job package - everything you need to complete your inspections.

What's Inside a Workpack?

A workpack contains:

  • Tasks list - What you need to inspect
  • Asset information - Details about each item
  • Previous inspection data - Historical context
  • Drawings/schematics - Visual references
  • Instructions - Specific requirements from client
📸 Screenshot Placeholder:
NEXUS Workpacks screen showing workpack list and tasks pane

Reading Your Task List

Each task tells you:

  • Asset - What to inspect (e.g., "Manifold M001")
  • Event Type - How to inspect it (e.g., "GVI", "UT", "ACFM")
  • Location - Where it is (KP, coordinates, or description)
  • Instructions - Specific requirements ("Focus on weld areas", "Check all anodes")
  • Status - Complete or incomplete

📋 Example Task Entry

Task #147:

  • Asset: XYZ-M001 (Subsea Manifold)
  • Event Type: GVI (General Visual Inspection)
  • Instructions: Visual inspection of all external surfaces. Check structural integrity, corrosion, marine growth, anodes condition, and flange connections.
  • Approximate Time: 45 minutes
  • Status: Incomplete

Pre-Job Preparation (What to Do BEFORE the ROV Launches)

  1. Review the workpack task list
    Know what you're inspecting and in what order
  2. Look at the assets
    Check asset information - what is it? What's it made of? When was it installed?
  3. Review previous inspections
    What was found last time? Are there known issues to monitor?
  4. Study drawings/schematics
    Orient yourself - where are the anodes? Where are critical welds?
  5. Read task instructions carefully
    Client may have specific requirements or areas of concern
⚠️ Common Mistake: Diving straight into data entry without reviewing the workpack first. You'll miss context, misunderstand requirements, or duplicate previous work. Always prep before starting.

Your First Inspection - Complete Workflow

Let's walk through a real scenario from start to finish:

🎬 SCENARIO: GVI on Subsea Manifold

Situation: You're on the vessel. ROV is ready. Client rep hands you workpack "2024-Q1-Subsea" with 3 tasks. First task: GVI on Manifold XYZ-M001.

Phase 1: Pre-Inspection (Before ROV Launch)

  1. Open NEXUS and navigate to WORKPACKS
    Find your workpack: "2024-Q1-Subsea"
  2. Select the workpack
    Tasks pane appears at bottom showing your 3 tasks
  3. Click on Task #1: "GVI Manifold XYZ-M001"
    Review task details, instructions, asset information
  4. Go to INSPECTION screen
    Navigate asset tree to find "XYZ-M001"
  5. Review historical data
    Check previous GVI events - what was found before?
  6. Open drawings/schematics
    Orient yourself to the manifold layout
💡 Pro Tip: Take 15 minutes to prep properly. It saves hours of confusion later and prevents missing critical details.

Phase 2: During Inspection (ROV in Water)

What you're doing during the actual inspection:

Taking detailed notes:

  • Paper notebook or clipboard with forms
  • Note every observation with timestamps
  • Record locations (compass directions, measurements from reference points)
  • Sketch quick diagrams if helpful
  • Log video timestamps for key findings
  • Record measurements as taken

Real-time data entry (if time permits):

  • Some inspectors enter data into desktop NEXUS during inspection
  • Requires good multitasking and familiarity with system
  • Only feasible if not primary ROV/dive supervisor
  • More common: focus on inspection, enter data afterward
💡 Best Practice: Most inspectors take thorough notes during the inspection and enter data into desktop NEXUS immediately afterward (same day). This ensures accuracy while observations are fresh, and gives time to ensure data quality.

Phase 3: Recording the Inspection (Creating the Event)

  1. Go to INSPECTION screen
    Select the asset "XYZ-M001" in the asset tree
  2. Go to Events pane (bottom right)
    This is where you'll create the inspection event
  3. Click "Add Event"
    A dialog opens to create new event
  4. Fill in Event Details:
    • Event Type: GVI
    • Date: Today's date
    • Inspector: Your name
    • Task: Select "Task #1: GVI Manifold XYZ-M001"
    • Duration: How long it took
    • Notes: General observations
  5. Save the Event
    Now you have a GVI event record linked to your task
📸 Screenshot Placeholder:
Add Event dialog showing fields to complete

Phase 4: Adding Findings

If you found something during inspection:

  1. With your event selected, go to Findings pane
    Usually below or next to the Events pane
  2. Click "Add Finding"
    A finding dialog opens
  3. Describe what you found:
    • Finding Type: Corrosion / Damage / Wear / Marine Growth / etc.
    • Location: "NE corner flange"
    • Description: Clear, detailed description
    • Dimensions: Length, width, depth (if applicable)
    • Severity: Minor / Moderate / Severe
    • Photos: Attach images
  4. Repeat for each finding
    One finding record per distinct issue
🎯 Critical Rule: One finding = one specific issue at one location. Don't combine multiple issues into one finding. "Corrosion on 3 flanges" should be 3 separate findings with specific locations and measurements.

Phase 5: Photos and Documentation

  1. Attach photos to your findings
    Each finding should have photos showing the issue
  2. Add overview photos to the event
    General condition shots even if no findings
  3. Annotate photos if needed
    Add arrows, measurements, labels to clarify
  4. Link video timestamps
    Note where in the ROV video each finding appears

Phase 6: Quality Check

Before handing over to client rep:

✅ QA Checklist:
  • ☐ Event created and linked to correct task
  • ☐ All required fields completed
  • ☐ All findings have descriptions, measurements, and photos
  • ☐ Photos are clear and properly labeled
  • ☐ Locations are specific (not vague)
  • ☐ Measurements are in correct units
  • ☐ All data saved and visible in NEXUS
  • ☐ Task marked as complete
  • ☐ Client-specific requirements addressed

Phase 7: Handover

  1. Mark task as complete
    Task status changes to "Completed"
  2. Double-check all data is saved
    Refresh NEXUS to confirm everything is there
  3. Inform client rep
    "Task #1 complete, ready for review"
  4. Be available for questions
    Client rep may ask for clarifications or additional details

Common Mistakes to Avoid (Your First Week)

❌ Mistake #1: Vague Descriptions

Bad: "Some corrosion observed"
Good: "Corrosion patch on NE corner flange, approx 25mm diameter, depth ~2mm, rust color, active (no marine growth coverage)"

❌ Mistake #2: Missing Measurements

Bad: "Large crack noted"
Good: "Crack in weld seam, length 150mm, width 2mm, depth not measurable from visual, oriented vertically"

❌ Mistake #3: Non-Specific Locations

Bad: "Damage on side"
Good: "Impact damage on west-facing support leg, 2.5m above mudline, 300mm below upper flange"

❌ Mistake #4: Combining Multiple Issues

Bad: One finding: "Corrosion on multiple flanges and some marine growth"
Good: Separate findings for each flange corrosion location, plus separate finding for marine growth

❌ Mistake #5: Poor Quality Photos

Bad: Blurry, no scale reference, unclear what you're showing
Good: Clear, in focus, scale reference visible, annotated if needed, multiple angles

❌ Mistake #6: Entering Data Days Later

Bad: Waiting 3 days, entering from memory, forgetting details
Good: Same day entry while observations fresh, details accurate

❌ Mistake #7: Not Reviewing Previous Data

Bad: Treating every inspection as fresh, missing trends
Good: Checking if corrosion has progressed, if known issues have worsened

❌ Mistake #8: Ignoring Task Instructions

Bad: Generic inspection, missing client-specific requirements
Good: Reading instructions, addressing specific areas of concern client mentioned

💡 The Golden Rule: If you can't explain it clearly in writing, you probably don't understand what you saw. Take more photos, get better angles, make more measurements. When in doubt, over-document rather than under-document.

NEXUS Interface - What You Need to Know

NEXUS has 6 main screens. As a 3.4U inspector, you'll use 2 of them regularly:

🎯 Screens You'll Use Daily:

1. WORKPACKS - Your job list

  • See your assigned workpacks
  • View task lists
  • Check what's complete vs incomplete
  • Access task instructions

2. INSPECTION - Where you record data

  • Navigate asset hierarchy
  • Create events
  • Add findings
  • Attach photos
  • Review previous inspections
  • Access drawings

⏭️ Screens You Can Ignore (For Now):

DASHBOARDS - Management overview, client rep uses this
ASSETS - Asset management, configuration, planning templates
LIBRARY - Document storage, procedures, drawings library
PLANNING - Campaign planning, scheduling, client rep territory

Key Interface Elements

Asset Tree (Left Side):

  • Hierarchical view of all assets
  • Click to expand/collapse
  • Select asset to view its data

Main Work Area (Center):

  • Changes based on what you're viewing
  • Task lists, event grids, forms appear here

Detail Panes (Right/Bottom):

  • Events, Findings, Photos, Drawings
  • Can be arranged/resized
  • Double-click headers to dock/undock

Toolbar (Top):

  • Add, Edit, Delete buttons
  • Import, Export, Reports
  • Context-sensitive (changes based on what's selected)
📸 Screenshot Placeholder:
NEXUS main interface showing labeled regions: Asset Tree, Work Area, Detail Panes, Toolbar

Keyboard Shortcuts (Time Savers)

Shortcut Action
Ctrl + N Add new (event, finding, etc.)
Ctrl + E Edit selected item
Ctrl + D Delete selected item
F5 Refresh / Reload data
Ctrl + F Find / Search
Space Open selected document/drawing

👔 For Client Representatives: Reviewing Inspector Data

Your role: Quality assurance and approval of inspection data before it goes to the client.

What to Check When Reviewing:

QA Checklist for Client Reps:
  • Completeness: All tasks marked complete? All events created?
  • Descriptions: Clear, specific, detailed enough for integrity engineer?
  • Measurements: Present where required? Units correct?
  • Photos: Clear, in focus, properly labeled, scale reference visible?
  • Locations: Specific enough to find the issue again next inspection?
  • Findings: Properly classified? Severity appropriate?
  • Consistency: Terminology matches client standards?
  • Anomalies: Significant findings flagged for tracking?

Common Feedback to Give Inspectors:

  • "Can you add measurements to Finding #3?"
  • "Photo of the corrosion patch is unclear - can you provide a closer shot?"
  • "Location says 'side' - which side specifically? Need compass direction."
  • "Finding description is good but needs dimensions."
  • "This looks significant - should we raise an anomaly?"

How to Provide Feedback in NEXUS:

  1. Add comments directly to events/findings
  2. Use email/Slack to communicate with inspector
  3. Don't change inspector's data without discussing first
  4. If corrections needed, ask inspector to make them (traceability)
💡 Pro Tip: Good feedback is specific and educational. Instead of "This is wrong", say "Need more detail on location - which flange specifically?" New inspectors learn fast when you explain WHY data quality matters.

🎓 Module 1 Key Takeaways

You now understand:

  • ✅ NEXUS is inspection management software used by major clients
  • ✅ Your data flows through a chain: You → Client Rep → Integrity Engineer → Asset Owner
  • ✅ The 5 core concepts: Asset, Workpack, Task, Event, Finding
  • ✅ How to read a workpack and understand your tasks
  • ✅ The basic workflow from pre-inspection to handover
  • ✅ Common mistakes to avoid in your first week
  • ✅ Which NEXUS screens you'll use daily (Workpacks & Inspection)

Most important lesson: Good inspection data is accurate, complete, timely, clear, and consistent. It directly impacts multi-million pound decisions.

📝 Practice Exercise

Before moving to Module 2, try this mental walkthrough:

🎯 Exercise: Your First GVI

Scenario: You're assigned a GVI on subsea manifold "ABC-M002". During the ROV inspection, you observe:

  • Light marine growth across the top plate
  • Corrosion on the northwest flange connection (estimated 30mm patch, 1-2mm deep)
  • Anode #2 appears 60% depleted
  • All structural components intact, no damage

Questions:

  1. How many findings would you create?
  2. What information would you include for the corrosion finding?
  3. What photos would you take?
  4. Would any of these warrant an anomaly? Why or why not?

Answers:

Click to reveal answers

1. Number of findings: 3 separate findings

  • Finding 1: Marine growth
  • Finding 2: Corrosion on NW flange
  • Finding 3: Anode depletion

2. Corrosion finding information:

  • Type: Corrosion
  • Location: Northwest flange connection
  • Description: Rust-colored corrosion patch, appears active
  • Dimensions: Approximately 30mm diameter, depth 1-2mm (estimated)
  • Severity: Minor to Moderate (depending on client standards)

3. Photos needed:

  • Overview shot of entire manifold (context)
  • Close-up of NW flange showing corrosion
  • Extreme close-up of corrosion with scale reference
  • Photo of Anode #2 showing depletion
  • Photo of marine growth coverage
  • Overview of all 4 sides for completeness

4. Anomaly consideration:

  • Marine growth: Probably not - this is common and expected
  • Corrosion: Maybe - depends on client standards and criticality. If on a Class 1 asset or if progressing from previous inspection, yes.
  • Anode depletion: Maybe - 60% might be within normal range, but if approaching end of life or inspection interval coming up, could raise anomaly to track.

When unsure: Ask the client rep. They know client-specific thresholds.

🚀 What's Next: Module 2

You now have the foundation. In Module 2: Understanding NEXUS Asset Hierarchy, you'll learn:

  • How subsea assets are organized in NEXUS
  • Navigating complex asset trees
  • Understanding asset relationships (parent-child)
  • Finding specific assets quickly
  • Asset information groups and what they mean
  • Why hierarchy matters for inspection planning
📚 Before Module 2: If you have access to a NEXUS test database or training environment, spend 30 minutes just exploring. Click around, open screens, look at data. You can't break anything in a test environment. Familiarity builds confidence.
💡 Coming in Future Modules:
  • Module 3: Your First Workpack - Complete walkthrough
  • Module 4: Recording Events & Findings - Deep dive
  • Module 5: Excel Export & Data Management
  • Module 6: NDT Data Entry (UT, ACFM, MPI)
  • Module 7: Working with Video Grabs & Photos
  • Module 8: Quality Checks & Client Handover