Open Architecture/Automated Setup/Advanced DP Solutions
Open Dynamic Positioning Platform — Unified Core, Flexible Hardware Integration
Bridgix Marine develops an open DP architecture engineered from the ground up to integrate with third-party and legacy equipment. It is backed by an international team of marine control engineers with extensive experience in designing, commissioning, and supporting DP systems on real vessels.
Key Technical Highlights
Unified Software Platform
A single core codebase scalable across all operational levels: Joystick, DP1, DP2, and HIL simulation. Operational tiers are defined purely by system configuration.
Open Integration Architecture
A proprietary control core with documented, stable interfaces. Displays, panels, sensors, thruster interfaces, and external systems plug in without core changes — full hardware vendor flexibility.
Minimized Vessel-Specific Engineering
Each vessel is described in configuration files — no custom software development. HIL testing, FAT, and FMEA tests run on the simulator before delivery.
Automated Control Loop Tuning
Identifies the vessel's hydrodynamic response from its own data and tunes the controller parameters — reducing tuning at sea trials from days to hours. Already built and tested.
Proven Field Experience
Engineered by specialists with proven track records in DP control system architecture, hydrodynamic modeling, algorithmic design, and offshore commissioning.
Live Simulator Demo
Interactive demonstration on the vessel simulator available upon request. Schedule a technical session.
High-Frequency Station Keeping (10 Hz Control Loop)
A Dynamic Positioning system automatically maintains a vessel’s position and heading (or follows a predefined track) using active thrusters while compensating for environmental forces (wind, current, waves). Operating at a 10 Hz update frequency, the system continuously calculates position deviation and allocates optimal thrust vectors.
- Sensors & Reference Systems
- GNSS, gyrocompasses, anemometers, Motion Reference Units (MRU), and acoustic/laser position references.
- DP Controller
- Marine-grade industrial computers running the DP control core. DP2 configurations use dual-redundant controllers with automatic bumpless failover.
- Operator Workstation
- Human-Machine Interface (HMI) featuring graphic displays, mode selection panels, and precision joysticks.
- Thruster Interface Units
- An interface node at each thruster: passes the command to the thruster's own control system and returns its status.
- Network Backbone
- Industrial Ethernet and fieldbus links between all components. DP2 uses two independent networks.
DP Classes & Redundancy Levels (IMO / Classification Guidelines)
| Class | Redundancy Level | Single Failure Impact | Typical Vessel Types |
|---|---|---|---|
| Joystick DP 0 | None. Manual coordinated control via a single lever with thrust allocation; optional auto-heading. No IMO class; often called DP 0. | Operator takes over manually | Yachts, tugs, workboats, crew transfer and small survey vessels |
| DP 1 | None. Automatic station keeping on a single controller. | May cause loss of position | Yachts, survey and research vessels, light construction, smaller supply vessels |
| DP 2 | Dual-redundant controllers, networks, and power distribution. | No loss of position on a single active component failure | Platform supply, offshore construction, cable lay, wind farm service and installation |
| DP 3 | As DP 2, plus physical separation with a backup station in another compartment. | No loss of position, including fire or flooding of one compartment | Drilling, diving support, heavy lift, pipelay |
Equipment classes follow IMO MSC/Circ.645 and MSC.1/Circ.1580 and are assigned by Classification Societies (DNV, ABS, LR, BV, and others). Typical vessel types are indicative.
Decoupled, Socket-Based Modular Architecture
At the center is the DP Core — the control software engine. All other equipment connects to the core through documented interfaces ("sockets"). Who made the device does not matter: any component that follows the interface works with the core.
Decoupled Dynamic Control Core
The core logic functions independently of specific operator display units, sensors, or thruster controls. Single unified core across all vessel classes.
Open, Standardized Specifications
System integrators and OEM equipment manufacturers can interface proprietary hardware via documented APIs and adapter SDKs.
Comprehensive Protocol Compatibility
Standard marine and industrial buses connect directly or through standard gateways; analog and digital signals through I/O modules (see the list above).
Everything Available Through an API
Operator stations, mobile terminals, remote stations, and simulators are equal system clients. Remote monitoring and integration with other bridge systems come naturally.
Linux Core, Displays on Any OS
No OS licenses on the DP controllers. The core runs as a headless industrial appliance with software update and rollback.
Parameter-Driven Configuration
Thrusters, sensor suites, and operational topologies are fully configured via deployment files without modifying compiled core software.
Universal Thruster Control Layer
Standardized thruster interface logic eliminates vessel-specific PLC programming. Spare hardware modules pull configuration directly from the DP core upon insertion.
Built-In HIL Simulation Capabilities
System testing, control loop tuning, operator training, and fault injection run on the identical software image deployed to production hardware.
Black-Box Data Logging
Continuous recording of control states, sensor inputs, and operator actions enables high-fidelity replay for post-incident analysis and optimization.
Cybersecurity by Design
Designed from the start in line with IACS Unified Requirements UR E26 and E27 on cyber resilience — not added later.
Zero Third-Party Royalty Fees
Built only on free and open-source components — no per-delivery license fees.
Engineered to Eliminate Legacy System Constraints
Conventional Legacy DP Systems
- Proprietary closed-loop architecture tied to single-vendor ecosystems.
- Integrating third-party equipment requires complex custom engineering.
- Limited simulation testing requires extensive commissioning at sea.
- Manual gain and parameter tuning during sea trials increases trial duration.
The Bridgix Marine Platform
- Vendor Flexibility: Select thrusters, position sensors, and bridge workstations based on cost, lead time, or customer preference.
- Accelerated Commissioning: Configuration-driven setup with pre-validated core logic. System failure modes are simulated during FAT, and automated tuning replaces trial-and-error adjustments.
- Optimized Hardware Footprint: DP2 redundancy without a separate pair of redundant control PLCs. On a typical DP2 vessel, bridge enclosures drop from six to two, with fewer cables.
- Lifecycle Sustainability: Designed for 15–25 year vessel lifecycles. Open communication standards eliminate single-vendor lock-in and simplify future retrofits.
Tailored Integration Workflows
Bridge System Integrators
Integrate full DP capability into your bridge packages without importing closed vendor systems. The core logic interfaces with third-party operator stations, networks, and alarm management systems via documented APIs.
For Joystick and DP1 applications, software-only licensing options are available for custom hardware builds.
Propulsion and Thruster Manufacturers
Direct interface capabilities across all industrial protocols:
- Analog / Discrete: 4–20 mA or ±10 V command/feedback signals (pitch, RPM, azimuth), alongside digital discrete signals (Ready, In-Control, DP Mode, Alarms).
- Serial Communications: RS-232 / RS-422 / RS-485 interfaces running Modbus RTU or proprietary protocols.
- Industrial Buses & Ethernet: Direct CANopen, J1939, Modbus TCP, OPC UA; gateway support for PROFIBUS, PROFINET, EtherNet/IP, and EtherCAT.
Signal scaling, feedback mapping, and operational limits are defined in configuration files. The thruster interface runs on Bridgix hardware or as Bridgix software on a controller from the supported list — possibly yours — enabling OEMs to deliver propulsion and DP to the shipyard as one package.
Sensor & Navigation System Manufacturers
Direct communication with standard or proprietary NMEA telegrams over serial or Ethernet interfaces (NMEA 0183, IEC 61162-450, NMEA 2000).
Devices with non-NMEA protocols connect through a software adapter built to a published interface contract — by Bridgix, by you, or by an integrator.
Shipyards and Vessel Operators
Maintain freedom in equipment procurement, shorten commissioning timelines, and leverage integrated HIL simulation and black-box recording built into the production core software image.
Vessel Retrofits & System Modernization
Upgrade obsolete DP systems while retaining functional sensors, networks, operator panels, and thruster controls — sometimes even the computers. How much can be kept is confirmed by a protocol assessment of the vessel.
Flexible Platform Offerings
Turnkey DP Systems
Joystick, DP1, and DP2 systems — turnkey or with customer-specified hardware.
Core Software Licensing
DP Core software engine deployment on customer-qualified hardware (Joystick and DP1 levels).
Thruster Interfaces
Bridgix hardware with software, or Bridgix software on a controller from the supported list.
System Modernization / Retrofit
Targeted DP control replacements preserving existing thruster drives, power infrastructure, and sensor suites.
HIL Simulator & Test Bench
Vessel simulator running the actual sea-going control software — for FAT, testing before sea trials, and operator training.
Integrator Development Kits
Interface specifications, emulators, API documentation, and compliance testing suites for hardware partners.
Engineering & Service
Commissioning, tuning to the vessel, remote support, software updates, and incident analysis from black-box recordings.
DP2 Integration Principles
DP Class 2 requires instant, conflict-free failover between the two controllers. The devices between the controllers and the thrusters take part in that logic.
We state the rules up front, so there are no surprises in the project.
- Open Standard
Sensors, Operator Workstations, HMIs, and External Automation Systems — Open integration via documented interfaces, without conditions. - Conditional Compliance
Third-Party Thruster Interfaces & Bridge Units — Must follow our behavior requirements, pass compliance verification, and integrate into FMEA hazard analysis. Utilizing Bridgix thruster interfaces streamlines class compliance. - System Responsibility
Integrated DP Control System Compliance — Bridgix Marine maintains single-source engineering responsibility before Classification Societies for total DP system performance.
Running on the Simulation Test Bench
The first working version of the system runs on a test bench with an advanced simulator modeling vessel hydrodynamics, propulsion, environmental disturbances, and interface protocols. The core runs on Linux; operator HMIs and the simulator run on Windows, connected only through the documented interfaces.
Note: Classification Society approval has not yet been obtained — the demonstration validates the system architecture, not a finished product.
- Architecture & Core EngineClosed loop completed: Sensor Input → Core Processing → Thrust Allocation → Vessel Hydrodynamics Model.
- Advanced Simulation Test BenchVessel, propulsion, environment, and interface models — in progress.
- Marine Hardware Deployment & DP2 RedundancyDeployment to marine-grade physical controllers and dual-redundant failover testing.
- Classification Society ApprovalApproval by the Classification Society and sea trial verification.
Partner With Us
We are actively engaging system integrators, propulsion OEMs, and vessel operators for pilot implementations and joint developments. Interactive HIL simulator demonstrations are available upon request.