Skip to main content

Data Requirements Checklist

What data to prepare and share with Enaimco to set up your Operational Twin and Asset Lifecycle Management modules.

Written by John Ennis

Data Requirements Checklist

This checklist outlines the data we need from you to build out your Operational Twin, broken into three steps. You don't need to share everything at once — start with what's readily available, and our team will work with you to fill any gaps.

Step 1: Structure Level Hierarchy

Required for structure identification and, ideally, structure positioning.

  • Required: Field Layout Drawing (PDF)

  • Recommended: Field Layout AutoCAD + GIS Datasource

  • Additional help: Asset Registries (or equivalent)

Step 2: Component Level Hierarchy + 2D Map & 3D Model

Required to break down structures into components (component-level hierarchy) and establish the 2D Map & 3D Model.

Module

Required Data Fields

Potential Data Sources

2D Map

Mapping data:

  • Structure names

  • GIS coordinates

Surveys: As-built survey data, field layout schematic, master AutoCAD file
(Only required if not provided via GIS Datasource in Step 1)

3D Virtual Environment

Properties:

  • Asset names and unique asset identifiers (e.g., SAP IDs)

Model Data:

  • GIS coordinates

  • Isometric and anatomical plane views

  • Cross-section views

  • Asset dimensions

Existing Asset Hierarchy: Export from Integrity Elementz, SAP, or other software (if applicable)
​Drawings/Schematics: General assembly drawings, engineering drawings, configuration drawings, AutoCAD files, field layout schematic, system schematics (electrical, hydraulic, flow), P&IDs
​Manuals: Operations and maintenance manuals, TDI sheets, rig books

Step 3: Module Specific Data

Only the modules relevant to your deployment will apply here.

Module

Required Data Fields

Potential Data Sources

Anomaly Management

Anomaly history:

  • Anomaly type

  • Discovery date

  • Revisions

  • Closeout actions

  • Related media

Anomaly codes:

  • Acceptable anomaly codes

  • Code descriptions

  • Severity levels

  • Severity level criteria

Existing Anomaly Register Hierarchy: Excel spreadsheet or export from existing software (e.g., Integrity Elementz)
​Anomaly guidelines/instructions: Naming conventions and process documentation

Valve Management

Valve characteristic data:

  • Tool interface

  • Nominal, Breakout, Damage Torques

  • Approximate turns

  • Linear Breakout Force and Stroke

Valve operation history (logs):

  • Operation date

  • Dive number (optional)

  • Start/End Position

  • Running/Breakout/Final Torque

  • Indicator status (optional)

  • Number of turns

Existing Valve Manipulation register: Excel spreadsheet or export from existing software

Historical Data Implementation

Asset properties/metadata:

  • Unique asset identifiers (e.g., SAP IDs)

  • Dimensions

  • Weights

  • Types (e.g., valve, XT, manifold)

  • Installation dates

Asset-file associations: Document registers
​Asset history: Engineering drawings, design specifications, revisions, installation certificates, Management of Change (MoC) reports

ROV Media Management

ROV Activity:

  • Dive log numbers

  • Dive activities, durations, and dates

  • Unique asset identifiers

  • Media identifiers

Multimedia files: Video, audio, images
​Dive logs

Integration

File attributes for DMS integration:

  • Document link

  • Unique ID

  • Document Number

  • File name (optional)

  • Title (optional)

  • Revision (optional)

  • Version (optional)

Other integrations:

  • API documentation

Integration Documentation: Dependent on client software

Risk Management

Risk Matrix Attributes:

  • Threat categories

  • Consequence of Failure (CoF) ratings

  • Control activities

  • Control activity frequency

  • Likelihood of Failure (LoF) ratings

Risk registers: Corporate or asset-level risk registers
​HAZID / HAZOP studies: Engineering safety documentation
​RBI studies: Damage mechanisms / failure modes

IMR Management

Activities & Tasks:

  • Inspection tasks by asset type

  • Last inspection dates

Inspection reports & registers: Closeout reports, work packs, spreadsheets with inspection activities and dates

Live Media Capture (ROV)

HTTP Connection:

  • IP Address

Serial Port Connection:

  • Baud rate

  • Data bits

  • Stop bits

  • Parity

  • Flow control

Integration Documentation: Dependent on client DVR system

Not sure which modules apply to you, or where to find a specific data source? Reach out to your Enaimco contact and we'll help you get started.

Related Articles
Did this answer your question?