{
  "id": 12712690,
  "title": "IMarEST: From MASS Code to Maritime Practice",
  "url": "https://urgent.news/2026/10/07/imarest-from-mass-code-to-maritime-practice",
  "topic": "business",
  "section": "Business",
  "published": "2026-10-07T21:00:59.000Z",
  "source": {
    "name": "Hellenic Shipping News",
    "slug": "hellenic-shipping-news",
    "url": "https://www.hellenicshippingnews.com/imarest-from-mass-code-to-maritime-practice/"
  },
  "original_language": "en",
  "account": "The International Maritime Organization (IMO) has introduced the Maritime Autonomous Surface Ships (MASS) Code to ensure safe and secure future technology in the shipping industry. However, the transition of this code from policy to practical implementation presents significant challenges. Adopted at Marine Safety Committee (MSC) 111, the MASS Code is non-mandatory as of July 2026, with a mandatory code scheduled for 2032. The code's goal-based approach, rather than prescribing a single technical architecture, establishes goals, functional requirements, and expected performance across various areas. This approach is sensible due to the broad scope of maritime autonomy, ranging from small uncrewed survey vessels to large remotely operated ships, and the rapid development of technology.\n\nThe Operational Design Domain (ODD), which defines the design range in which a system can operate as intended, is a crucial aspect of the MASS Code. However, translating this concept into real-world practice is complex. The ODD encompasses ephemeral and environmental conditions, geographical constraints, and the vessel's condition. A critical concern is the vessel's response when conditions fall outside its ODD, especially during adverse weather. The code addresses this with fallback states and contingency measures to maintain safety, but determining the boundary of environmental parameters, the vessel's ability to assess its operational limits, and providing evidence of safe fallback behavior are significant challenges.\n\nThe translation of the MASS Code into practical systems and operations is the most complex part of the process. For example, a coastal survey vessel faces demanding questions, whereas a harbor tug working in crewed traffic faces even harder challenges. These questions are not against the code but highlight the need for industry, regulators, and the engineering profession to address them. The challenge lies in moving from writing the rules to translating them into practical implementation.\n\nTo ensure seamless operation of MASS, it is essential to develop a common engineering interpretation between regulatory requirements and practical implementation. This traceability, from the intent of the code to the functions required, the evidence needed, and the organizations responsible, is vital. Independently translating the code by each operator, supplier, class society, and regulator risks sector fragmentation. Therefore, there is a value in establishing a common, vendor-neutral foundation for these approaches, which professional institutions like IMarEST can provide through the MASS Special Interest Group (SIG). By convening maritime autonomy communities around practical implementation and capturing lessons for routine autonomous operations, the industry can establish accepted operating boundaries, repeatable assurance frameworks, and clear responsibilities during changing circumstances.",
  "summary": "As shipping becomes increasingly automated, the International Maritime Organization (IMO) has introduced legislation to ensure future technology is safe and secure. But there are significant challenges with taking the new Maritime Autonomous Surface Ships (MASS) Code from policy to practice. The adoption of the International Maritime Organization’s MASS Code marks an important step in the ...",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}