Abstract
The discussions by the International Maritime Organization for the introduction of a maritime autonomous surface ship (MASS) began in earnest. At the 27th ENAV meeting, the International Association of Marine Aids to Navigation and Lighthouse Authorities proposed the “sharing of a common operating picture for situational awareness of the waterway within vessel traffic service (VTS) environment” when developing a system to support MASS operation. Marine accidents caused by collisions on waterways still account for a high percentage of ship accidents that occur at sea, and many studies have investigated the risk of collision between ships. Collision risk assessment was primarily conducted in ship domain-based safety areas. This study evaluates the collision risk using the ship domain derived by the VTS operator (VTSO) and proposes a real-time collision risk assessment support system to improve the situational awareness of VTSOs and MASS remote operators (MASS ROs) regarding near-collision situations occurring in local waters. To evaluate the validity of the proposed system, a risk analysis was performed on near-collision scenarios at Busan Port. The results show that the distance to the closest point of approach (CPA), time to the CPA, and inter-ship distance converged within 0.5 nautical miles, 10 min, and 3 nautical miles, respectively.
Highlights
The International Maritime Organization (IMO) included discussions of maritime autonomous surface ships (MASSs) in the official agenda of the 99th meeting of the MaritimeSafety Committee (MSC) in 2018, and they have prepared a regulatory scoping exercise (RSE) for MASS operation [1,2,3,4,5,6]
The results show that the distance to the closest point of approach (CPA), time to the CPA, and inter-ship distance converged within 0.5 nautical miles, 10 min, and 3 nautical miles, respectively
A collision risk assessment method and risk assessment support system were proposed to enhance the situational awareness of the VTS operator (VTSO) and MASS remote operator (RO) in the event of a collision risk owing to an encounter between ships in a multi-ship environment in the vessel traffic services (VTS) area
Summary
The International Maritime Organization (IMO) included discussions of maritime autonomous surface ships (MASSs) in the official agenda of the 99th meeting of the MaritimeSafety Committee (MSC) in 2018, and they have prepared a regulatory scoping exercise (RSE) for MASS operation [1,2,3,4,5,6]. The discussions have defined MASS vessels for RSE work and categorized their autonomy level (degree one: ship with automated processes and decision support; degree two: remotely controlled ship with seafarers on board; degree three: remotely controlled ship without seafarers on board; degree four: fully autonomous ship) [1]. The document contains points related to the “sharing of a common operating picture for situational awareness of the waterway within vessel traffic services (VTS) environment” and “scoping and development of guidance on the interaction between VTS and the control for MASS shore control center (SCC),” among the prior considerations of MASS system guidance. When implementing a system for the situational awareness of collision risks in VTS areas and the interaction between MASSs and VTS centers, collision risk assessment and support technologies for VTS operators (VTSOs) and ROs in multi-ship encounter situations in VTS areas must be implemented in a real-time system as a key module
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
