Sprint 12 · Project / Vessel / Activity Architecture

Connect vessels to projects through specific activities and events.

Intelatus should model tow-out, mooring pre-lay, heading control, hook-up, commissioning and long-term operations as distinct activity events. This supports market analysis while protecting granular vessel identity data behind entitlement controls.

Analysis-first model Subscriber views focus on activity signals, fleet demand, regions and trends. Internal analysts retain granular vessel/event evidence.

Core relationship model

Project / asset → activity event → vessel assignment.

A single activity can involve several vessels. A single vessel can participate in multiple activities over time. Role instances such as Ocean Towing 1, Ocean Towing 2, Mooring Pre-Lay AHTS 1 or Hook-Up Subsea Vessel 1 preserve analytical value even when individual vessel names are masked from subscribers.

Project / field / wind farm Primary asset Activity event Vessel assignment Role instance Location / route Validation confidence Analyst note

Lifecycle stages

Project activity timeline

FPSO · Floating Wind · Rigs · Platforms

EARLY_PREP

Early project preparation

Project/site preparation and long-lead planning before major offshore activity.

Timing: Months to years before installation
Subscriber value: Forward indicator for future vessel demand.

MOORING_PRELAY

Mooring pre-lay

AHTS, subsea and MSV spreads mobilize from port to site to install anchors, chains, lines and related components before asset arrival.

Timing: Often 2-4 months, sometimes 1-2 years before arrival
Subscriber value: Early warning of project execution and upcoming tow/hook-up demand.

TOW_OUT

Wet tow / dry tow / ocean towing

One or more towing vessels move a floating production unit, floater or turbine assembly from origin to site.

Timing: Days to weeks depending route
Subscriber value: Identifies major installation milestones and high-end AHT/tug demand.

HEADING_CONTROL

Heading control / station keeping

AHTS/tug vessels hold or control position during mooring connection, riser/umbilical installation or hook-up.

Timing: Static or near-static during operations
Subscriber value: Distinguishes towing from higher-value hook-up support demand.

HOOKUP

Hook-up and commissioning

AHTS, subsea vessels, SOVs and support craft connect and tension moorings, array cables, risers and utilities.

Timing: Weeks to months
Subscriber value: Key demand phase for specialized vessels and project execution signals.

OPERATIONS

Operations support

Once installed, assets receive regular support from standby, firefighting, supply, terminal tugs, offtake and utility vessels.

Timing: Multi-year / charter period
Subscriber value: Ongoing market demand and recurring support-vessel activity.

MAINTENANCE

Maintenance / intervention

Intervention, inspection, repair, subsea, utility and walk-to-work activity after commissioning.

Timing: Recurring or campaign based
Subscriber value: Ongoing activity level and fleet utilization intelligence.

Activity archetypes

Named event types for analysis and reporting

Controlled vocabulary

Activity	Vessel roles	Speed / behavior pattern	Analysis use	Subscriber view	Internal view
Ocean towing OCEAN_TOWING · FPSO / floating wind / floating assets	Ocean towing AHT/tug 1, 2, 3...	Moving at low tow speed; often 2-3 knots for wet tow Days to weeks	Major project milestone, high bollard-pull vessel demand and route intelligence.	Aggregated tow activity by basin, project stage and period	Full vessel identities, IMO/MMSI, route, validation confidence and assignment numbers
Heading control HEADING_CONTROL · FPSO / FLNG / floating wind	Heading control vessel 1, 2, 3...	Static or near-static, generally around 0 knots Hours to days per operation	Identifies hook-up/station-keeping activity rather than ordinary transits.	Activity count, duration and region	Full vessel IDs, tracks, project association and analyst override
Mooring pre-lay AHTS MOORING_PRELAY_AHTS · Floating wind / FPSO	Mooring pre-lay AHTS 1, 2, 3...	Transit to site around service speed; installation work can show low-speed patterns Often 2-4 months	Forward signal for project execution and upcoming floater/FPS arrival.	Pre-lay campaigns by region/project type	Full spread composition, vessel IDs, ports, timing and internal validation notes
Mooring pre-lay subsea/MSV MOORING_PRELAY_SUBSEA · Floating wind / FPSO	Mooring pre-lay subsea vessel 1, 2...	Transit to site and low-speed work near installation area Often 2-4 months	Measures demand for MSVs/subsea vessels and installation capacity.	Subsea/MSV demand by period and basin	Full vessel identities, equipment fit and validation confidence
Hook-up AHTS HOOKUP_AHTS · FPSO / FLNG / floating wind	Hook-up AHTS 1, 2, 3...	Low-speed or static near asset during connection/tensioning Weeks to months	Key specialized vessel demand during final installation.	Hook-up activity signals and charted trends	Full assignments, vessel identities, tracks, project link and analyst notes
Hook-up subsea/MSV HOOKUP_SUBSEA · FPSO / FLNG / floating wind	Hook-up subsea vessel 1, 2...	Low-speed work near site; may include port/site cycling Weeks to months	Connects subsea activity to project stage and vessel demand.	Aggregated hook-up subsea activity	Full detail for analysts and consulting output
Hook-up SOV / W2W HOOKUP_SOV · Floating wind / FPSO support	Hook-up SOV or W2W vessel	Stationary or repeated site visits Weeks to months	Identifies W2W/SOV demand in installation and commissioning.	SOV demand signals by market	Full vessel identity and project assignment
Long-term operations support OPERATIONS_SUPPORT · FPSO / FLNG / FSRU / wind farm	Safety standby, firefighting, resupply, terminal tug, utility, offtake support	Regular calls or station/standby patterns Years; often long-term charter	Ongoing fleet demand, charter opportunity and regional support profile.	Aggregated support activity and recurring call patterns	Full granular vessel-call and company relationship access

Design rules

How the data should behave

Activity is not always one vessel: A single activity can involve one asset/project and multiple vessels, and one vessel can participate in multiple activities over time. This supports towing spreads, mooring campaigns, hook-up spreads and long-term support patterns.
Use role instances: Vessels should be assigned numbered role instances such as Ocean Towing 1, Ocean Towing 2, Heading Control 1, Mooring Pre-Lay AHTS 1. This preserves analysis value even when subscriber views mask vessel identities.
Separate asset, event and vessel: The floating asset/project, the activity/event, and the vessels assigned to that event should be separate data entities. It lets the same vessel, FPSO, rig, port or wind project connect to multiple activities without forcing bad table relationships.
Speed patterns are evidence, not truth: AIS speed/behavior patterns help infer activity type, but analyst confirmation and validation confidence must be stored. Terrestrial AIS gaps and incomplete tracking require confidence fields and internal review.
Subscriber output is aggregated: Client-facing views should summarize activity, vessel demand, region, time period and market signal unless entitlement allows granular detail. Protects the database while delivering market intelligence.
Internal output is granular: Analysts/admins need full vessel IDs, company links, source comparison, notes and overrides for consulting and editorial analysis. This is where Intelatus converts raw data into differentiated intelligence.

Data entities

Production table/view foundation

Admin activity types →

EntityProject / field / wind farm

The commercial project or field being developed or supported.

Subscriber exposure: Named project may be visible by module and package.
Internal exposure: Full project metadata, client, country, basin, internal validation notes and forecast fields.

EntityPrimary offshore asset

FPSO, FLNG, FSRU, rig, platform, floating wind unit or other asset linked to activities.

Subscriber exposure: Visible in dashboards or masked depending entitlement.
Internal exposure: Full asset details and source comparisons.

EntityActivity event

A time-bound market event such as tow, pre-lay, hook-up, commissioning, support or intervention.

Subscriber exposure: Usually visible as aggregated event/activity signal.
Internal exposure: Full event details, confidence, dates, location and analyst notes.

EntityVessel assignment

A vessel’s role inside an activity, including numbered role instance and dates.

Subscriber exposure: Aggregated or masked unless entitled.
Internal exposure: Full vessel identity, role, IMO/MMSI, confidence, speed pattern and route.

EntityLocation / route

Port, site, field, country, basin, from/to, work area and movement corridor.

Subscriber exposure: Region/basin/port-level analysis.
Internal exposure: Full coordinates, route traces, port calls and AIS evidence.

EntitySource confidence

How Intelatus knows the relationship/activity is likely correct.

Subscriber exposure: Generally hidden or summarized.
Internal exposure: Full internal evidence, analyst validation and override history.