BOQA

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Bridge Operational (or Operations) Quality Assurance (BOQA - pronounced BOUQUA or / bəʊ'kwɒ /) is a methodology utilised in shipping and which originates from the similar FOQA (Flight operations quality assurance) concept in aviation. BOQA is a methodology with which ship owners/operators, ship Captains, and other associated shipping stakeholders can automatically and systematically monitor, track, trend and analyse operational quality of (seagoing) vessels. The main target with BOQA is to enhance maritime safety and to enable proactive decision making in ship operations. The BOQA methodology can be used in both conventional manned ships and in autonomous or unmanned vessels.

Description[edit]

BOQA is best developed as a non-punitive company-internal methodology or process, which has the overall target of assisting the ship Captain and the ship operator to maintain a high level of safety and operational quality.

BOQA has been described as:[1]

  • A system which delivers 24/7 electronic monitoring and electronic alarms when set operational parameters are deviated from
  • During normal operations, BOQA will collect and analyse digital operational data direct from ships operation equipment
  • BOQA data is unique because it can provide objective information that is not available through other methods
  • A BOQA program can identify operational situations in which there is increased risk, allowing operators to take early corrective action before that risk results in an incident or accident
  • The BOQA program is a tool in the operators overall operational risk assessment and prevention program
  • BOQA, being proactive in identifying and addressing risk will enhance safety

Methodology[edit]

BOQA is used to objectively monitor the human operational performance and external factors, such as weather and other traffic around the vessel, by utilising various types of sensor and external data and comparing this data with defined best-practices and Standard operating procedure (SOPs). BOQA is usually not used to monitor the internal technical performance of the vessel machinery and equipment-base, which in most cases already has a wide range of proprietary monitoring and alarm functions.

BOQA is often a software system consisting of shipboard real-time data collection and sensing, automated data transmission between the vessel and shore and a shore-based system which receives, combines, analyses, alerts and stores the data according to defined rules and logic.

BOQA usually includes three "time-domains", ie:

  1. a historical database of data and events and which is used for trend- and pattern analysis
  2. a real-time reactive stream analytics component which can react to events or deviations in real- or near-real-time (NRT)
  3. a predictive and pro-active component, which assists the operator in taking actions before an event occurs

Event types[edit]

BOQA is a continuously developing methodology, much in the same way as FOQA. At present time BOQA solutions are known to be able monitor following event types:

  • Cross-track error or deviation from a defined navigational route (the Costa Concordia disaster is known to be caused by such deviation)
  • Safety corridor, ie is the ship sailing within its defined safe waters
  • Collision risk based on Proximity (ship too close to own ship), CPA (Closest point of approach which measures the time and distance to a potential collision) and BCR (Bow Cross Range)
  • Entry into a restricted or protected area
  • Severe list, heel or roll
  • Excessive accelerations
  • Excessive turns (high ROT)
  • Crash stop
  • Heavy weather at present position and along a planned route (this is a predictive component)
  • Sudden change in atmospheric pressure (which is an indicator of oncoming change in weather)
  • Speed monitoring, which can be used for example in Charterparty Compliance monitoring
  • Unscheduled stops along the route, which may lead to schedule-deviations and unwanted changes in arrival time
  • Proximity to a shore line, ice edge or iceberg
  • Rescue boat launch
  • AIS (Automatic identification system) status change
  • Black-out
  • Port inactivity
  • Excessive use of engine controls
  • Under keel clearance
  • Excessive rudder angles
  • Traffic Separation Scheme violations

Inputs[edit]

BOQA relies on data from various sources. The key data sources are:

Applications[edit]

BOQA is not yet known to be officially mandated or regulated by any official maritime bodies, such as International Maritime Organization, Classification societies or Flag state administrations.

Royal Caribbean Cruise line stated in their 2012 Stewardship report that they were evaluating a BOQA system. [2]

In 2011, RCL began evaluating a voyage data recording analysis and trending system, known as Bridge Operations

Quality Assurance (BOQA), based on a similar program used in the aviation industry (the Flight Operations Quality Assurance program). In 2012 we made progress in the technical development of this system for marine use, and we have installed two prototypes on our vessels for testing purposes. This system will enhance our data analysis that supports our accident prevention initiatives.

Carnival Corporation & plc is known to have a large scale in-house developed BOQA solution, which consists of a data-system (Neptune) and a 24/7 manned Fleet Operations Centre in three locations around the world.[3]

AS Tallink Group is known to be in the process of testing a BOQA solution.[4]

Literature[edit]

References[edit]

  1. ^ Christie, David (25 March 2014). "Innovative Techniques to Enhance Safety" (PDF).
  2. ^ RCCL 2012 Stewardship report, page 13 "Maritime safety"http://www.royalcaribbean.com/content/en_US/pdf/13034530_RCL_2012StwrdshpTwoPgrs_v4.pdf
  3. ^ Carnival Corporation & plc (13 March 2017). "Carnival Corporation Expands Global Fleet Operations Centers, A First in Commercial Maritime Industry". Retrieved 15 April 2018.
  4. ^ AS Tallink Group (8 February 2018). "Tallink opts for IoT based operational awareness solution". Retrieved 15 April 2018.