中文 Request a demo

Investigations

When an incident occurs, an investigation establishes what each vessel did, when and where, in English and Traditional Chinese. Every statement cites an evidence item, and every evidence item resolves to sealed source data, so opposing experts can verify it independently.

Discuss a case How we decide

Reconstruct incidents at sea to an evidential standard

NeroInvestigationsR-0412Demo vessel E18:14:07Z
A tanker at anchor on dark water, seen from directly above
Demo vessel E · SIM-E
Status
At anchor
In zone
2 h 16 min
Level
Warning · 40
Evidence
14 files · sealed
Built for
Legal teams at telecom and energy companiesInsurers and loss adjustersLaw firmsProsecutors and maritime investigatorsPolicy researchers and journalists
NeroInvestigationsTrack replayDemo eventSimulated
21:22
23:38

From a single incident to a full case

Incident reconstruction
A bilingual, hash-backed timeline of what each vessel did around an incident, delivered as a report with its evidence file.
Claims support
Vessel histories, timelines and exposure summaries for insurers, adjusters and counsel working a marine claim.
Evidence packages
The source data, hashes, and code and configuration versions behind a finding, prepared for an opposing expert or the court.
Identity of every vessel involved
The identity history of every vessel involved: names across scripts, identifier changes and shared numbers, with the evidence for every link.
One clock

The whole night, laid out on one clock

Speed, navigation status, zone, level, sources and evidence files run on one timeline, in Taiwan time and UTC. Where a source could not see, the gap is marked, never read as nothing happening.

凝瀚Reconstruction R-0412 · Demo vessel E · illustrative cableSimulated data
21:0013:00 UTC22:0014:00 UTC23:0015:00 UTC00:0016:00 UTC
Speed 0–10 kn
Navigation status
Under wayAt anchor
Zone
OutsideInside the protection zone
Level
MonitoringWatchWarning
Sources
AIS · vendor ACoastal radar · customer C-1No radar coverage
Evidence files
3f9a…c21e77b0…19dee4c2…5a07
23:22 Taiwan · 15:22 UTCSpeed0.1 knStatusAt anchor 2 hLevelWarning · 40SourcesAIS, radar
The report

One report, two languages, the same evidence

English and Traditional Chinese side by side. Every statement carries the number of the evidence it cites, and both versions point at one evidence package with one hash.

凝瀚Reports · R-0412 · page 1 of 14EN中文
ReconstructionR-0412

Demo vessel E at the illustrative cable

Illustrative cable · protection zone · Taiwan time (UTC+8)

1Summary

At 21:22 Taiwan time (13:22 UTC), Demo vessel E anchored inside the protection zone of the illustrative cableE2. It remained at anchor until the end of the period reviewedE3. Its behavior is consistent with an anchored vessel; the data does not establish intent.

Figure 1 · Track and protection zone

2Timeline
21:10Slowed below 3 kn over the cableE1
21:22Anchored inside the zoneE2
22:22Watch: slow in the zone over 1 hE4
23:22Warning: at anchor 2 hE5
sha256 9c41…07abPage 1 of 14
Evidence citedE1–E6
  • E1raw/ais-2026-10-14.gz3f9a…c21e
  • E2episodes/demo-e.jsone4c2…5a07
  • E3raw/ais-2026-10-15.gz77b0…19de
  • E4alerts/a-21.json5d18…a3c0
  • E5config/detectors.toml0b6d…f3e1
  • E6identity/sim-e.jsonc07e…812b
Chain of custodysha256 9c41…07ab
  1. Received21:00:03
  2. Sealedsha256 3f9a…c21e
  3. Chainedmanifest #0412
  4. Re-runconfig demo-1
  5. Exportedsha256 9c41…07ab

Built for the people who have to prove it

The exposure, measured

For a marine claim, Nero sets out how long each vessel spent near the asset, how close it came and what it was doing at the time, with every figure tied to sealed data.

NeroInvestigationsClaims supportDemo event18:14:07Z
Exposure summary · demo vessel E
Asset
Illustrative cable · protection zone
Time within 1 NM
4 h 12 min
Closest approach
0.01 NM · 21:24
Status at closest
Under way · 5.8 kn
Evidence items
14
Within 1 NM of the cable · 4 h 12 min

Prepared for a demo insurer. It describes behavior; liability is for the parties and the court.

  • Time within range and closest approach
  • Status at each moment, as broadcast
  • Plain language, no inference of intent

Hand over the evidence, not just the conclusion

An evidence package holds the source files, their hashes and the code and configuration versions behind a finding, so an opposing expert can re-run it and get the same result.

NeroInvestigationsEvidence packageDemo eventSimulated
Evidence package · demo eventRe-run from source: identical output
  1. raw/ais-2026-10-14.gzsha256 3f9a…c21e
  2. raw/ais-2026-10-15.gzsha256 77b0…19de
  3. episodes/demo-a.jsonsha256 e4c2…5a07
  4. config/detectors.tomlsha256 0b6d…f3e1
  5. report/reconstruction-en.pdfsha256 5d18…a3c0
  6. report/reconstruction-zh.pdfsha256 c07e…912b
  7. manifest.jsonmanifest 4e7a…d20c
  • Source files and SHA-256 hashes
  • Code and configuration versions
  • Re-runs produce identical output

Know every vessel involved

Each vessel in a reconstruction comes with its identity history: names across scripts, identifier changes and shared numbers, with the evidence for every link.

NeroInvestigationsDossierDemo vessel B18:14:07Z
Demo vessel B · identity history
  1. 2019-03First seen as 示範海辰 6 號 (SHIFAN HAICHEN 6), ID SIM-1001Source: raw messages in sealed daily files
  2. 2021-08Renamed 示範海辰六號Same ID, type and dimensions: a rename, not a different hull
  3. 2022-01ID SIM-1001 reported at two positions too far apart to be one vesselSplit into two identities, pending review
  4. 2023-05Simplified-script spelling 示范海辰六号 appears in a second sourceMatched across Traditional and Simplified script
  5. 2024-11Switches to ID SIM-1002Name, type and dimensions match; confidence: medium
  • Drawn from Nero's identity graph
  • Uncertain links are marked as pending

Inside a reconstruction

TimeTimeline

Taiwan time and UTC side by side, with zone entries and exits and changes in navigational status and speed.

MovementTrack replay

The tracks of every vessel involved, before and after the event.

LanguageMeasured language

Reports state what the data shows, such as “behavior consistent with a dragging anchor”, and never infer intent.

EvidenceEvidence manifest

File hashes, data sources, licenses, and code and configuration versions for every evidence item, so the result can be reproduced from source data.

Known limits

Where a reconstruction stops

Approach & Limits
  • We describe behavior in the data. We do not judge intent or liability, and we do not give legal advice.
  • We can only reconstruct from data that exists and that we are licensed to use.
  • Admissibility is for the court to decide.

Works with Cable Watch

Any Cable Watch alert or disturbance can go straight into a reconstruction, with the evidence already sealed.

Explore Cable Watch

NeroCable WatchHow an alert buildsSimulated replaySimulated
23:38 TaiwanSpeed 0.0 kn
  1. 22:32Slow inside the protection zone for over an hour+20
  2. 23:32At anchor in a no-anchoring zone for 2 hours+20
Score · Watch at 20, Warning at 4040
WarningAlert raised · A-21 · 23:32
Simulated replay: the demo ship slows inside the cable's protection zone, anchors and stays. Each indicator adds its points until the score reaches the Warning threshold. Ships and tracks come from Nero's synthetic track generator; the cable is illustrative.

Common questions

Can the report be used in court?
It is designed with court use in mind: sealed source data, file hashes and results that can be re-run from the original records. Admissibility remains for the court to decide.
What data do you use?
Data licensed for the case, plus anything you provide, such as radar records or cable alarms.
Can we have a single language?
Yes. By default, both languages appear in one report with identical content.
First pilots

Put Nero to workon your waters

We are choosing a small number of cable and offshore wind operators for the first pilots. Write to us in English or Chinese.

Request a demo Or write tocontact@nero.com.tw