Ask a captain what an integrated bridge system is, and you will hear a mix of marketing language and personal history. Ask a class surveyor and you will get a fairly precise answer rooted in IMO and IEC standards. The buyer who has to spec the hardware sits in between. An IBS is more than a cluster of monitors wired together, and getting that distinction right is the difference between a workspace that earns type approval the first time and one that has to be rebuilt at sea trial. This walkthrough covers what counts as an IBS, which subsystems belong inside it, which standards apply, and how the architecture actually changes the displays and computers you put behind the helm.
What Counts As An Integrated Bridge System?
An integrated bridge system, usually shortened to IBS, is a coordinated set of navigation and ship-control workstations that share data, alarms, and control across a common backbone. The IMO definition in the Performance Standards for Integrated Bridge Systems, MSC.64(67) Annex 1, describes it as a combination of systems that are interconnected to allow centralized access to sensor information or command and control from workstations, with the objective of increasing safe and efficient ship management by suitably qualified personnel. That definition is doing a lot of work. The key word is interconnected. Two ECDIS plotters and a radar bolted to the overhead are not an IBS. They are three boxes near each other.
Where Did The IBS Concept Come From?
The IBS concept was formalized in the late 1990s as bridges started accumulating dedicated screens for chart display, radar, conning, autopilot, AIS, and engine monitoring. Each system had its own UI, its own alarm policy, and its own failure mode. Watch officers ended up scanning eight different displays and acknowledging duplicate alarms from three different sources. The IMO response was to define how those systems should be wired together, share data through a documented network, present alarms through a single hierarchy, and route control to whichever workstation the watch officer was using.
How An IBS Differs From A Pile Of Standalone Electronics
A standalone bridge has navigation electronics that can each function on their own. The chart plotter draws charts whether the radar is on or off. An IBS is the opposite. Each workstation is designed to share sensor data with the others through a fault-tolerant LAN, usually a redundant pair of Ethernet rings, and to fail over to a peer workstation if its own hardware drops out. That single design choice is what triggers the IBS performance standard. Once the workstations share sensor data and back each other up, the system has to be type-approved as a whole, not piece by piece.
Which Subsystems Live Inside An Integrated Bridge System?
An IBS is built around a core set of functions that MSC.64(67) calls task stations. The exact number and layout vary by vessel class, but every modern IBS includes voyage planning, route monitoring, collision avoidance, automatic steering, manual override, alarm management, and a documented interface to the engine and cargo systems. On a commercial bulker the layout might be two workstations and a conning display. On a naval auxiliary it might be five workstations, two conning displays, and a dedicated tactical position. The functions are the same. The footprint is what changes.
Voyage Planning And ECDIS
The ECDIS workstation is usually the visual anchor of the bridge. It is where the route is planned, the chart is monitored, and most of the day-to-day watchkeeping happens. Inside an IBS, the ECDIS is not optional. SOLAS Chapter V Regulation 19 requires ECDIS on most SOLAS-class vessels, and the IBS performance standard requires that the ECDIS be the primary route-monitoring task station. That means the display behind it has to satisfy both the ECDIS presentation standard and the broader IBS environmental envelope. Before you sign off on a panel, it is worth reviewing what type approval actually means for the chart display, because an ECDIS-ready monitor that is not type-approved as part of the system will not satisfy the IBS surveyor.
Radar, AIS, And Conning
The radar task station feeds target data into the ECDIS and into the conning display. AIS data is overlaid on both. The conning display is its own animal: a fixed-format readout of heading, speed over ground, rate of turn, rudder angle, and engine telegraph, presented in a way that any watch officer can read at a glance without having to drive a UI. That conning display is one of the most demanding monitor positions on the bridge because it never sleeps. It is on a fixed mount, often above the centerline window, and it has to remain readable from sunrise glare through midnight dark with no operator interaction.
Steering, Autopilot, And Track Control
An IBS includes an autopilot with a documented interface to the ECDIS for track control, plus an independent manual steering position. The control logic is split across two physically separate processors so that a fault in one path does not take both down. That redundancy requirement bleeds directly into the computer specs behind the workstation. The processing hardware has to keep running through vibration, voltage transients, and EMI from the radar and the engine room, and it has to be supportable for the life of the ship. A standard office tower will not survive this duty cycle, which is part of why a purpose-built marine navigation computer lives behind every serious task station.
Alarms, BNWAS, And Watchkeeping
The alarm management function is what separates an IBS from a row of standalone displays more than anything else. Every alarm in the system, from a GPS dropout to a low lube-oil pressure on the main engine, has to be presented through a single hierarchy with consistent priority levels. The IBS routes the alarm to the active workstation, logs it, and tracks acknowledgement. The Bridge Navigation Watch Alarm System, or BNWAS, runs alongside this and is required under SOLAS V/19 on most ships built since 2011. The BNWAS resets when the watch officer interacts with any IBS workstation, so the input devices on each station have to feed the watch-alert logic without being driven by a dedicated dead-man switch.
Which Class Rules And Standards Apply?
The IBS sits at the top of a stack of standards. Getting the stack right is the difference between a system that books type approval cleanly and one that has to be re-tested after the install.
IMO Performance Standards For Integrated Navigation
MSC.252(83) defines performance standards for Integrated Navigation Systems, the modern successor to the original IBS standard. INS is a stricter superset: it inherits the IBS requirements for interconnection and alarm hierarchy, then adds explicit task-oriented presentation requirements and a documented method for sensor integrity monitoring. On newer commercial newbuilds, INS is increasingly what the owner specifies even when the contract uses the older IBS label.
IEC 61924-2: The IBS And INS Test Standard
IEC 61924-2 is the test standard that gives MSC.252(83) teeth. It defines the test cases a notified body actually runs against the integrated system: alarm hierarchy verification, fail-over timing, sensor switching, and graceful degradation. The certificate at the bottom of the type approval is issued against this standard, and the audit trail is what the flag state inspector reviews at port. Hardware that is approved in isolation but cannot demonstrate the IEC 61924-2 fail-over scenarios will not satisfy the audit.
Type Approval At The System Level
The single most common mistake on an IBS procurement is buying components that are each type-approved on their own and assuming that gets you a type-approved IBS. It does not. The classification society, whether that is ABS, DNV, Lloyds Register, Bureau Veritas, or another IACS member, issues the IBS type approval against the as-installed system, not against the parts list. The displays, computers, network switches, and software all have to be tested together in the actual topology that ships on the vessel. Changing a monitor model after the type approval is granted forces a re-test of every interaction that monitor participates in.
How Does An Integrated Bridge System Change Your Display And Computer Specs?
Once you accept that the IBS is a system rather than a pile of boxes, the spec sheet for each piece of hardware changes. The bezel dimensions, the brightness range, the input ports, and the operating system support window all become system-level decisions.
Workstation Layout And Display Sizing
The IBS performance standard requires that each task station present its information in a consistent layout, and that the layouts share a common visual grammar across workstations. In practice this means matched panels: a 26-inch ECDIS monitor on every workstation, identical conning displays at every helm position, and matching aspect ratios across the conning array. Mixing a 24-inch and a 27-inch display at adjacent stations will fail the presentation review even if both panels are individually compliant. Most newbuilds standardize on a single panel family across the bridge, sized to the longest viewing distance.
Redundancy, Sensor Failover, And Common-Mode Failure
The IBS standard requires that no single failure cause a complete loss of navigation function. That requirement reaches into the hardware spec. Each workstation needs its own processor, its own video path to its primary display, and its own power feed from a separate distribution panel. Network switches are doubled. Cables are run in physically separated trays. The video bonding between the chart computer and the panel has to handle a switch-over in under the time the standard allows, with no operator action. This is where a marine-grade backplane, hot-swappable PSU, and dual NIC configuration earn their cost.
Input Devices Built For An Integrated Workspace
The IBS performance standard does not prescribe a particular input device, but the way alarms and task control move between workstations puts real pressure on the input choices. Touchscreens are useful for direct chart manipulation, but they are sensitive to gloves, condensation, and the heeling of the vessel. A glove-rated trackball or pointer is the standard fallback at almost every demanding station, partly because operators can keep one hand on it through a sea state and partly because what makes industrial trackballs work on a moving deck is the same thing that lets the IBS log every action against the watch officer who actually made it. Keyboards are usually wash-down rated with sealed membranes. A pure tablet workflow is rare in an IBS context, and the systems that try it usually run into the watch-alert and audit-trail requirements before commissioning.
Operating System Lifecycle And Long-Term Supply
A type-approved IBS is not just hardware. The operating system version, the application versions, and the firmware on the network switches are all part of the certificate. The vessel is expected to run the same software baseline for the life of the type approval, which can be a decade or more. That makes the operating system support window one of the most important line items on the computer spec. A consumer-grade workstation that lands in the IBS architecture and then loses OS support five years in will force a re-certification cycle the owner did not budget for. Long-term support, controlled BIOS updates, and a documented end-of-life roadmap are not optional features on an IBS computer.
What Should You Do Before You Buy?
Three steps separate a smooth IBS commissioning from a sea-trial scramble. First, lock the system topology before you lock the parts list. The integrator should publish a network diagram, a power one-line, and a sensor map that the classification society can review against MSC.64(67) and MSC.252(83) before any hardware is ordered. Second, confirm that every display, computer, and input device on the topology comes from a supplier that can produce a current type-approval letter and an environmental test report under IEC 60945 and, where applicable, IEC 61924-2. Third, plan the lifecycle from day one. Get the spare-parts list, the OS support window, and the firmware update policy in writing before the equipment leaves the yard. Working from a hardware portfolio like the Seatronx marine displays line that has been built around these constraints is usually less expensive than retrofitting a generic workstation midway through commissioning.
Frequently Asked Questions
Is An Integrated Bridge System Required By SOLAS?
SOLAS does not mandate an IBS on every ship. It mandates ECDIS on most SOLAS-class vessels and BNWAS on most ships built since 2011, both of which fit naturally inside an IBS. The IBS itself is required when the owner, the flag state, or the classification society specifies it, which is increasingly the default on newbuilds above a certain size.
What Is The Difference Between An IBS And An INS?
An IBS is the older performance standard, MSC.64(67), defining how navigation and ship-control workstations interconnect and share alarms. An INS is the newer standard, MSC.252(83), which inherits the IBS requirements and adds explicit task-oriented presentation rules and stricter sensor integrity monitoring. On modern newbuilds the contract often says IBS but the spec actually describes an INS.
Can You Add A Workstation To An Existing IBS Without Re-Certifying?
Usually no. The IBS type approval is granted against the as-installed topology. Adding a workstation changes the sensor sharing pattern, the alarm routing, and the fail-over behavior, all of which are tested at certification. Most class societies treat a new workstation as a major modification that requires a re-test of the affected interactions before the certificate is updated.
Does Every Display In An IBS Need ECDIS Type Approval?
No. Only the displays designated as ECDIS task stations need ECDIS type approval against IEC 61174. The conning display, the radar display, and other task stations are approved under their own performance standards. All of them, however, share the IBS environmental envelope under IEC 60945, which is why mixing consumer monitors into an IBS will not pass.
Can An IBS Use Standard Office Computers Behind The Displays?
Office hardware cannot satisfy the IBS environmental and EMC requirements. The processors and storage drives behind each workstation are tested under IEC 60945 for temperature, humidity, vibration, and electromagnetic compatibility. A consumer tower will fail the EMC scan in the first hour of testing and will not survive a sea state on the bridge floor.
How Does A BNWAS Interact With An IBS?
The BNWAS is a watch-alert system that fires escalating alarms if the bridge appears unattended. Inside an IBS, the BNWAS resets when the watch officer interacts with any approved IBS workstation, rather than only when a dedicated panel is touched. The interconnection between BNWAS and the IBS workstations is documented in the type approval and is one of the items tested under IEC 61924-2.
Who Issues The Type Approval For An IBS?
A classification society that is a member of the International Association of Classification Societies issues the IBS type approval. ABS, DNV, Lloyds Register, Bureau Veritas, ClassNK, RINA, and other IACS members all run their own approval programs against the same IMO and IEC standards. The chosen society is usually whichever one classes the vessel.