About FleetOps
Simulation architecture, data boundaries and the operational scope of Haiyi FleetOps.
Haiyi FleetOps is a customer, exhibition and technical-exchange demonstration of a global shore fleet operations center. It is not connected to any real vessel, customer or production control system.
Simulation architecture
A deterministic simulator builds one immutable fleet snapshot per tick and publishes it atomically. Sequence, UTC generation time, simulation run and seed version stay coherent across all vessel systems.
What is simulated
Vessel identities, registry numbers, routes, positions, equipment states, operating values, communication quality and alarm events are generated entirely by software profiles and scenarios.
Data model
Latest telemetry lives in the atomic in-memory snapshot. Historical trends are generated deterministically. SQLite stores only simulation runs, alarm events, system events and diagnostics.
Read-only boundary
The UI and versioned API provide monitoring queries only. There are no public start, stop, breaker, alarm acknowledgement, reset or remote-control operations.
Privacy and no customer data
No real customer names, IMO numbers, MMSI numbers, passenger identities, vessel photos or ship-to-shore operational data are used or represented.
Local-first presentation
The world outline, vessel markers, icons, styles and Apache ECharts runtime are served locally. Core pages require no map tiles, fonts, chart CDN or unknown third-party API.
Operational data flow
single process · read onlyTechnical details
All vessel names, routes, positions, equipment states, operating parameters and alarm events shown on this platform are generated by simulation software. They do not represent any real vessel, customer or actual operating condition. The current system is monitoring-only and provides no remote-control capability.