F25.05 - Computer Applications

SIGNIFICANCE AND USE
3.1 This guide is aimed at providing a general understanding of the various types of hardware devices that form the core of information processing systems for ship and marine use. Ship and marine information processing systems require specific devices in order to perform automated tasks in a specialized environment. In addition to providing information services for each individual installation, these devices are often networked and are capable of supplementary functions that benefits ship and marine operations.  
3.2 A variety of choices exists for deployment of information processing devices and greatly increases the complexity of the selection task for ship and marine systems. The choice of a particular device or system cannot be made solely on the singular requirements of one application or function. Modern information processing systems are usually installed in a complex environment where systems must be made to interact with each other. Ship and marine installations add an even further layer of complexity to the process of choosing adequate computerized systems. This guide aims to alleviate this task by giving users specific choices that are proven technologies that perform in a complex environment.  
3.3 Hardware resources used in ship and marine installations are a result of careful consideration of utility and function. These resources may require some physical specialization in order to inhabit a particular environment, but they are in no way different from equipment used in shore-based situations. Ship and marine computer system configurations, interconnections, and support services are essentially the same as those found in a land-based network environment and as a result, the skill sets of ship and marine information processing system users, administrators, and support personnel are interchangeable with those of shore-based activities.
SCOPE
1.1 This guide provides assistance in the choice of computing hardware resources for ship and marine environments and describes:  
1.1.1 The core characteristics of interoperable systems that can be incorporated into accepted concepts such as the Open System Interconnection (OSI) model;  
1.1.2 Process-based models, such as the Technical Reference Model (TRM), that rely on interoperable computing hardware resources to provide the connection between the operator, network, application, and information; and,  
1.1.3 The integrated architecture that can be used to meet minimum information processing requirements for ship and marine environments.  
1.2 The use of models such as OSI and TRM provide a structured method for design and implementation of practical shipboard information processing systems and provides planners and architects with a roadmap that can be easily understood and conveyed to implementers. The use of such models permit functional capabilities to be embodied within concrete systems and equipment.  
1.3 The information provided in this guide is understood to represent a set of concepts and technologies that have, over time, evolved into accepted standards that are proven in various functional applications. However, the one universal notion that still remains from the earliest days of information processing is that technological change is inevitable. Accordingly, the user of this guide must understand that such progress may rapidly invalidate or supersede the information contained herein. Nonetheless, the concept of implementing ship and marine computing systems based on these functional principles allows for logical and rational development and provides a sound process for eventual upgrade and improvement.  
1.4 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.

SIGNIFICANCE AND USE
3.1 Intended Use—Compliance with this guide will allow the sharing of electronic data between contracting parties that is normally done by hard copy. This can only be used when both parties use a database-derived software package to manage their contracts. Specifically, it will:  
3.1.1 Eliminate the duplication of manual entry of data into each party’s contract administration software package and  
3.1.2 Allow for wide access of the data to all authorized parties.
SCOPE
1.1 This guide provides the database structure of electronic data interchange (EDI) information between ship owner and a shipyard for contract administration. Ship owners (hereinafter referred to as owners) and shipyards may each have unique software programs to manage their respective portions of a ship repair period. There is information that must be exchanged between the parties during the contract period. This guide has been developed to establish common field lengths, names, and types such that the exchanged information can be used directly by the respective software programs without scanning, typing, or redundant keying of information.  
1.2 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.

SIGNIFICANCE AND USE
4.1 This guide is intended to provide an understanding of the wide range of communication protocols standards, allowing the user to understand better their applicability to shipboard networks and marine platform computerized systems. For computerized networks and systems, communication protocols are necessary for integrating various system devices, providing functionality between dissimilar subnetworks, or for enabling remote connections, either pier side or through geophysical communication technologies.  
4.2 The wide variety and scope of digital communication protocol standards adds greatly to the complex decision process for specifying compatible protocols for system applications and related devices for the myriad of potential shipboard systems. However, the user must identify the initial networking requirements, so once the network protocols under evaluation are well understood, the decision process should determine the appropriate network protocols. Therefore, this guide is intended to reduce the complexity involved with protocol selection and implementation.  
4.3 Network protocols define an agreed, quantifiable entity, or set of rules, by which user computers, system networks, and internetworking devices communicate and exchange information. Communication protocols specify essential networking guidelines, such as physical interface connections, or data format and control operations between two communicating computers. Ship and marine digital communication protocol requirements are no different than their land-based networked counterparts. Both require standardized protocol selection, in various protocol categories, including LAN standards, WAN protocols, LAN/WAN protocols, network management, wiring hub configurations/operations, hardware platforms, operating systems, and network applications.
SCOPE
1.1 The principal content of this guide provides a road map to implement a communication network applicable to ship and marine computer systems by:  
1.1.1 Examining the relationship of digital communication protocols as a network technological infrastructure,  
1.1.2 Outlining the basic building blocks of network topologies and transmission techniques associated with the implementation of transmission media in a network environment; and,  
1.1.3 Identifying operating system and environments.  
1.2 Using the Open System Interconnection (OSI) model, which provides a layered approach to network functionality and evaluation, common network communications protocols are identified and characterized in this guide according to lower and upper layer protocols corresponding to their degree and type of functionality.  
1.3 Although it is desirable that network users, designers, and administrators recognize and understand every possible networking protocol, it is not possible to know the intimate details of every protocol specification. Accordingly, this guide is not intended to address fully every hardware and software protocol ever developed for commercial use, which spans a period of about 25 years. Instead, the user of this guide will be introduced to a brief overview of the majority of past and present protocols which may comprise a ship or marine internetwork, to include Local Area Networks (LANs), Wide Area Networks (WANs), and related hardware and software that provide such network interoperability and data transfer.  
1.4 While this guide provides an understanding of the wide range of communication protocols, the user is recommended to consult the reference material for acquiring a more comprehensive understanding of individual communication protocols. However, by examining the basic functions of protocols and reviewing the protocol characterization criteria identified in this guide, the user will be more apt to understanding other protocols not mentioned or addressed herein.  
1.5 This international standard was developed in accordance with internationally recognized principles on...

ABSTRACT
This guide provides a uniform format and definition of general vessel-related technical information, including ship safety data, to be used by ship owners and operators, at their option and to the extent that they consider beneficial to their operation. It is recognized that all of the data is already contained in various documents on the vessel, but normally not electronically and normally not in one location. The ship safety record is designed to provide an industry-accepted common method of identifying, maintaining, and subsequently communicating the safety-related information needed for maritime operations. The ship safety record is an electronic database of information pertaining to a specific vessel including information related to the safe operation of the vessel and the safety of its crew and the environment. The vessel particulars, vessel status, crew requirements, status of crew and persons other than passengers on board, voyage specific data, record of inspection, record of incidents and corrective actions are presented in details.
SIGNIFICANCE AND USE
4.1 The Ship Safety Record is an electronic database of information pertaining to a specific vessel including information related to the safe operation of the vessel and the safety of it’s crew and the environment. The data is grouped and organized under the following key categories: vessel particulars, vessel status, crew requirements, crew status, voyage specific data, record of inspection, record of incidents, and corrective actions.  
4.2 The Ship Safety Record is created and maintained in each instance for the primary benefit of the owner, technical manager, or operator who is required through the implementation of the ISM Code to be cognizant of such information. The information in the database is at all times the property of the owner who will maintain and control the dissemination of any and all of the information. It is expected that operators will elect to make portions of their Ship Safety Record database available to other interested parties such as flag states, class societies, and port states.14 The Ship Safety Record should provide for the implementation of several levels of electronic database security as may be required by the vessel owner or operator. The data that becomes part of the Ship Safety Record can be thought of in a number of subsets:  
4.2.1 Data that is not subject to change, including particulars of the vessel, and so forth.  
4.2.2 Data that is subject to change but not normally by the ship’s crew.  
4.2.3 Data that will be updated periodically either manually or as a result of updates to other computer systems or applications. This would include, as an example, cargo information, ballast conditions, the names/identification of crew members, and passenger details. This would also include information relative to internal inspections, maintenance records, internal audits, safety audits, and so forth.  
4.3 Guides F1756 and F1757 may be used as the basis for implementation of a shipboard electronic database and ship safety record.
SCOPE
1.1 This guide provides a uniform format and definition of general vessel-related technical information, including ship safety data, to be used by ship owners and operators, at their option and to the extent that they consider beneficial to their operation. It is recognized that all of the data is already contained in various documents on the vessel, but normally not electronically and normally not in one location. The Ship Safety Record is designed to provide an industry-accepted common method of identifying, maintaining, and subsequently communicating the safety-related information needed for maritime operations. It is recognized that many of the data fields are not applicable for every vessel. Appendix X1 and Appendix X2 provide examples of how data elements in this guide may be used for a specific purpose, that is, the USCG’s Automated Identification System (AIS) and the...

SIGNIFICANCE AND USE
4.1 This guide provides a recommended transition plan for a marine software maintainer, when the maintainer is other than the supplier, to develop the capability to make extensive changes or extensions to the programs. Further, this guide provides a recommended interactive process model for managing and executing software maintenance activities. This guide applies principally to the marine software that requires design effort and for which the product requirements are stated principally in performance terms.
SCOPE
1.1 This guide covers a recommended plan for transition and acceptance of marine software that was developed by an activity other than the maintaining activity. It further provides a recommended iterative process model for managing and executing software maintenance activities.  
1.2 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.

SIGNIFICANCE AND USE
4.1 Capturing high quality RAM performance data requires careful and consistent collection of equipment failure and repair data, operating hours, and repair time. A standard hierarchy of equipment boundaries has been needed for machinery data exchange among the stakeholders in shipbuilding, ship classification, and ship operations.  
4.2 Industry and government will use a world standard method for setting the hierarchy of indentures and boundaries required for assigning failure and repair events to equipment for the tracking and calculation of equipment RAM performance.  
4.3 Agreed boundaries and equipment identifiers make it possible to share equipment data among organizations, benchmark equipment performance, perform modeling and simulation of current and proposed systems, or use performance data to improve operations of commercial and naval vessels.  
4.4 RAM analysis is primarily based on the observation of individual components among which identical items contribute to the same data sample. This classification is designed to be used for the identification of individual (unique) components in such a way that identical components can be identified within a given data sample.
SCOPE
1.1 This classification is to serve as an international standard for marine equipment nomenclature, taxonomy, hierarchical data structure, unique identifiers, and boundary definition for the consistent acquisition and exchange of equipment RAM performance data. The standard addresses the classification of mechanical and software products.  
1.2 RAM in an acronym for Reliability, Availability, and Maintainability where:  
1.2.1 Reliability is the probability that an item can perform a required function under given conditions for a given time interval (t1, t2). It is generally assumed that the item is in a state to perform this required function at the beginning of the time interval.  
1.2.2 Availability is the probability that an item is in a state to perform a required function under given conditions at a given instant of time, assuming that the required external resources are provided.  
1.2.3 Maintainability is the probability that a given active maintenance action, for an item under given conditions of use can be carried out within a stated time interval, when the maintenance is performed under stated conditions and using stated procedures and resources.  
1.3 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety, health, and environmental practices and determine the applicability of regulatory limitations prior to use.  
1.4 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.

SIGNIFICANCE AND USE
5.1 To maintain the integrity of potentially vulnerable information systems while the vessel is at sea or in port, strategies and procedures can be used by every company, organization, and ship. Mitigating potential cyberattack events will allow for a better economic environment through secure consumer, employee, and corporate data. Informational infrastructure between ships, platforms, and onshore facilities are more interconnected today than a decade ago. The long-term health and economic viability of ship owners and operators depend on establishing and maintaining security that can measured and monitored.  
5.2 With the increase in cyberattacks in recent decades, maritime-based companies and governments have cited a need to update and train their workforce to mitigate the loss of data or intellectual theft from onboard systems.  
5.2.1 Vulnerable onboard systems can include, but are not limited to:
5.2.1.1 Cargo management systems;
5.2.1.2 Bridge systems;
5.2.1.3 Propulsion and machinery management and power control systems;
5.2.1.4 Access control systems;
5.2.1.5 Passenger servicing and management systems;
5.2.1.6 Passenger facing public networks;
5.2.1.7 Administrative and crew welfare systems;
5.2.1.8 Communications systems;
5.2.1.9 Distributed computing devices that support an internet of things (IoT)-enabled ship; and
5.2.1.10 Onboard sensors that facilitate wheelhouse automation, alerting, and IoT transmission.  
5.2.2 Many of these systems are critical to mariners while at sea. If any of said systems failed or were compromised while at sea because of a cyberattack, then the ship and its security could be compromised.  
5.3 By adopting these practices, mariners and shoreside employees at all levels of the organization should be able to identify potential threats or risk factors, as well as the abnormal indications that show a cyberattack underway.  
5.4 Cyberattacks can occur in multiple forms including, but not limited to, the foll...
SCOPE
1.1 This guide addresses the company or government organizational need to mitigate the likelihood of cyberattacks and reduce the extent of potential cyberattacks, which can leave sensitive personal data, corporate information, and critical infrastructure vulnerable to attackers.  
1.2 These recommendations are meant to serve as a guideline for corporate and government organizations to adopt for the protection of sensitive personal information and corporate data against hackers.  
1.3 Cybersecurity and cyberattacks are not limited to the maritime industry. With greater advancement in computer and information technology (IT), cyberattacks have increased in frequency and intensity over the past decade. These advancements provide hackers with more significant tools to attack vulnerable data and communication infrastructures. Cyberattacks have become an international issue to all governments and companies that interact with each other.  
1.4 Cybersecurity and the safety of cyber-enabled systems are among the most prevailing issues concerning the maritime industry as well as the global economy. Cyberattacks could affect the flow of trade or goods, but operator errors in complex, automated systems may also cause disruptions that may be mitigated with proper policies and personnel training.  
1.5 This guide is meant to provide strategies for protecting sensitive data onboard vessels and offshore operations.  
1.6 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety, health, and environmental practices and determine the applicability of regulatory limitations prior to use.  
1.7 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides ...

SIGNIFICANCE AND USE
4.1 This guide provides a recommended transition plan for a marine software maintainer, when the maintainer is other than the supplier, to develop the capability to make extensive changes or extensions to the programs. Further, this guide provides a recommended interactive process model for managing and executing software maintenance activities. This guide applies principally to the marine software that requires design effort and for which the product requirements are stated principally in performance terms.
SCOPE
1.1 This guide covers a recommended plan for transition and acceptance of marine software that was developed by an activity other than the maintaining activity. It further provides a recommended iterative process model for managing and executing software maintenance activities.

SIGNIFICANCE AND USE
4.1 This guide is intended to provide an understanding of the wide range of communication protocols standards, allowing the user to understand better their applicability to shipboard networks and marine platform computerized systems. For computerized networks and systems, communication protocols are necessary for integrating various system devices, providing functionality between dissimilar subnetworks, or for enabling remote connections, either pier side or through geophysical communication technologies.  
4.2 The wide variety and scope of digital communication protocol standards adds greatly to the complex decision process for specifying compatible protocols for system applications and related devices for the myriad of potential shipboard systems. However, the user must identify the initial networking requirements, so once the network protocols under evaluation are well understood, the decision process should determine the appropriate network protocols. Therefore, this guide is intended to reduce the complexity involved with protocol selection and implementation.  
4.3 Network protocols define an agreed, quantifiable entity, or set of rules, by which user computers, system networks, and internetworking devices communicate and exchange information. Communication protocols specify essential networking guidelines, such as physical interface connections, or data format and control operations between two communicating computers. Ship and marine digital communication protocol requirements are no different than their land-based networked counterparts. Both require standardized protocol selection, in various protocol categories, including LAN standards, WAN protocols, LAN/WAN protocols, network management, wiring hub configurations/operations, hardware platforms, operating systems, and network applications.
SCOPE
1.1 The principal content of this guide provides a road map to implement a communication network applicable to ship and marine computer systems by:  
1.1.1 Examining the relationship of digital communication protocols as a network technological infrastructure,  
1.1.2 Outlining the basic building blocks of network topologies and transmission techniques associated with the implementation of transmission media in a network environment; and,  
1.1.3 Identifying operating system and environments.  
1.2 Using the Open System Interconnection (OSI) model, which provides a layered approach to network functionality and evaluation, common network communications protocols are identified and characterized in this guide according to lower and upper layer protocols corresponding to their degree and type of functionality.  
1.3 Although it is desirable that network users, designers, and administrators recognize and understand every possible networking protocol, it is not possible to know the intimate details of every protocol specification. Accordingly, this guide is not intended to address fully every hardware and software protocol ever developed for commercial use, which spans a period of about 25 years. Instead, the user of this guide will be introduced to a brief overview of the majority of past and present protocols which may comprise a ship or marine internetwork, to include Local Area Networks (LANs), Wide Area Networks (WANs), and related hardware and software that provide such network interoperability and data transfer.  
1.4 While this guide provides an understanding of the wide range of communication protocols, the user is recommended to consult the reference material for acquiring a more comprehensive understanding of individual communication protocols. However, by examining the basic functions of protocols and reviewing the protocol characterization criteria identified in this guide, the user will be more apt to understanding other protocols not mentioned or addressed herein.

SIGNIFICANCE AND USE
3.1 Intended Use—Compliance with this guide will allow the sharing of electronic data between contracting parties that is normally done by hard copy. This can only be used when both parties use a database-derived software package to manage their contracts. Specifically, it will:  
3.1.1 Eliminate the duplication of manual entry of data into each party’s contract administration software package and  
3.1.2 Allow for wide access of the data to all authorized parties.
SCOPE
1.1 This guide provides the database structure of electronic data interchange (EDI) information between ship owner and a shipyard for contract administration. Ship owners (hereinafter referred to as owners) and shipyards may each have unique software programs to manage their respective portions of a ship repair period. There is information that must be exchanged between the parties during the contract period. This guide has been developed to establish common field lengths, names, and types such that the exchanged information can be used directly by the respective software programs without scanning, typing, or redundant keying of information.

ABSTRACT
This guide provides a uniform format and definition of general vessel-related technical information, including ship safety data, to be used by ship owners and operators, at their option and to the extent that they consider beneficial to their operation. It is recognized that all of the data is already contained in various documents on the vessel, but normally not electronically and normally not in one location. The ship safety record is designed to provide an industry-accepted common method of identifying, maintaining, and subsequently communicating the safety-related information needed for maritime operations. The ship safety record is an electronic database of information pertaining to a specific vessel including information related to the safe operation of the vessel and the safety of its crew and the environment. The vessel particulars, vessel status, crew requirements, status of crew and persons other than passengers on board, voyage specific data, record of inspection, record of incidents and corrective actions are presented in details.
SIGNIFICANCE AND USE
4.1 The Ship Safety Record is an electronic database of information pertaining to a specific vessel including information related to the safe operation of the vessel and the safety of it’s crew and the environment. The data is grouped and organized under the following key categories: vessel particulars, vessel status, crew requirements, crew status, voyage specific data, record of inspection, record of incidents, and corrective actions.  
4.2 The Ship Safety Record is created and maintained in each instance for the primary benefit of the owner, technical manager, or operator who is required through the implementation of the ISM Code to be cognizant of such information. The information in the database is at all times the property of the owner who will maintain and control the dissemination of any and all of the information. It is expected that operators will elect to make portions of their Ship Safety Record database available to other interested parties such as flag states, class societies, and port states.14 The Ship Safety Record should provide for the implementation of several levels of electronic database security as may be required by the vessel owner or operator. The data that becomes part of the Ship Safety Record can be thought of in a number of subsets:  
4.2.1 Data that is not subject to change, including particulars of the vessel, and so forth.  
4.2.2 Data that is subject to change but not normally by the ship’s crew.  
4.2.3 Data that will be updated periodically either manually or as a result of updates to other computer systems or applications. This would include, as an example, cargo information, ballast conditions, the names/identification of crew members, and passenger details. This would also include information relative to internal inspections, maintenance records, internal audits, safety audits, and so forth.  
4.3 Guides F1756 and F1757 may be used as the basis for implementation of a shipboard electronic database and ship safety record.
SCOPE
1.1 This guide provides a uniform format and definition of general vessel-related technical information, including ship safety data, to be used by ship owners and operators, at their option and to the extent that they consider beneficial to their operation. It is recognized that all of the data is already contained in various documents on the vessel, but normally not electronically and normally not in one location. The Ship Safety Record is designed to provide an industry-accepted common method of identifying, maintaining, and subsequently communicating the safety-related information needed for maritime operations. It is recognized that many of the data fields are not applicable for every vessel. Appendix X1 and Appendix X2 provide examples of how data elements in this guide may be used for a specific purpose, that is, the USCG’s Automated Identification System (AIS) and the...

SIGNIFICANCE AND USE
3.1 This guide is aimed at providing a general understanding of the various types of hardware devices that form the core of information processing systems for ship and marine use. Ship and marine information processing systems require specific devices in order to perform automated tasks in a specialized environment. In addition to providing information services for each individual installation, these devices are often networked and are capable of supplementary functions that benefits ship and marine operations.  
3.2 A variety of choices exists for deployment of information processing devices and greatly increases the complexity of the selection task for ship and marine systems. The choice of a particular device or system cannot be made solely on the singular requirements of one application or function. Modern information processing systems are usually installed in a complex environment where systems must be made to interact with each other. Ship and marine installations add an even further layer of complexity to the process of choosing adequate computerized systems. This guide aims to alleviate this task by giving users specific choices that are proven technologies that perform in a complex environment.  
3.3 Hardware resources used in ship and marine installations are a result of careful consideration of utility and function. These resources may require some physical specialization in order to inhabit a particular environment, but they are in no way different from equipment used in shore-based situations. Ship and marine computer system configurations, interconnections, and support services are essentially the same as those found in a land-based network environment and as a result, the skill sets of ship and marine information processing system users, administrators, and support personnel are interchangeable with those of shore-based activities.
SCOPE
1.1 This guide provides assistance in the choice of computing hardware resources for ship and marine environments and describes:  
1.1.1 The core characteristics of interoperable systems that can be incorporated into accepted concepts such as the Open System Interconnection (OSI) model;  
1.1.2 Process-based models, such as the Technical Reference Model (TRM), that rely on interoperable computing hardware resources to provide the connection between the operator, network, application, and information; and,  
1.1.3 The integrated architecture that can be used to meet minimum information processing requirements for ship and marine environments.  
1.2 The use of models such as OSI and TRM provide a structured method for design and implementation of practical shipboard information processing systems and provides planners and architects with a roadmap that can be easily understood and conveyed to implementers. The use of such models permit functional capabilities to be embodied within concrete systems and equipment.  
1.3 The information provided in this guide is understood to represent a set of concepts and technologies that have, over time, evolved into accepted standards that are proven in various functional applications. However, the one universal notion that still remains from the earliest days of information processing is that technological change is inevitable. Accordingly, the user of this guide must understand that such progress may rapidly invalidate or supersede the information contained herein. Nonetheless, the concept of implementing ship and marine computing systems based on these functional principles allows for logical and rational development and provides a sound process for eventual upgrade and improvement.

ABSTRACT
This guide provides a uniform format and definition of general vessel-related technical information, including ship safety data, to be used by ship owners and operators, at their option and to the extent that they consider beneficial to their operation. It is recognized that all of the data is already contained in various documents on the vessel, but normally not electronically and normally not in one location. The ship safety record is designed to provide an industry-accepted common method of identifying, maintaining, and subsequently communicating the safety-related information needed for maritime operations. The ship safety record is an electronic database of information pertaining to a specific vessel including information related to the safe operation of the vessel and the safety of its crew and the environment. The vessel particulars, vessel status, crew requirements, status of crew and persons other than passengers on board, voyage specific data, record of inspection, record of incidents and corrective actions are presented in details.
SIGNIFICANCE AND USE
4.1 The Ship Safety Record is an electronic database of information pertaining to a specific vessel including information related to the safe operation of the vessel and the safety of it’crew and the environment. The data is grouped and organized under the following key categories: vessel particulars, vessel status, crew requirements, crew status, voyage specific data, record of inspection, record of incidents, and corrective actions.
The Ship Safety Record is created and maintained in each instance for the primary benefit of the owner, technical manager, or operator who is required through the implementation of the ISM Code to be cognizant of such information. The information in the database is at all times the property of the owner who will maintain and control the dissemination of any and all of the information. It is expected that operators will elect to make portions of their Ship Safety Record database available to other interested parties such as flag states, class societies, and port states.13 The Ship Safety Record should provide for the implementation of several levels of electronic database security as may be required by the vessel owner or operator. The data that becomes part of the Ship Safety Record can be thought of in a number of subsets:
4.2.1 Data that is not subject to change, including particulars of the vessel, and so forth.
4.2.2 Data that is subject to change but not normally by the ship’crew.
4.2.3 Data that will be updated periodically either manually or as a result of updates to other computer systems or applications. This would include, as an example, cargo information, ballast conditions, the names/identification of crew members, and passenger details. This would also include information relative to internal inspections, maintenance records, internal audits, safety audits, and so forth.
Guides F 1756 and F 1757 may be used as the basis for implementation of a shipboard electronic database and ship safety record.
SCOPE
1.1 This guide provides a uniform format and definition of general vessel-related technical information, including ship safety data, to be used by ship owners and operators, at their option and to the extent that they consider beneficial to their operation. It is recognized that all of the data is already contained in various documents on the vessel, but normally not electronically and normally not in one location. The Ship Safety Record is designed to provide an industry-accepted common method of identifying, maintaining, and subsequently communicating the safety-related information needed for maritime operations. It is recognized that many of the data fields are not applicable for every vessel. Appendix X1 and Appendix X2 provide examples of how data elements in this guide may be used for a specific purpose, that is, the USCG's Automated Identification System (AIS) and the Advance Notice...

SCOPE
1.1 This guide provides the database structure of electronic data interchange (EDI) information between ship owner and a shipyard for contract administration. Ship owners (hereinafter referred to as owners) and shipyards may each have unique software programs to manage their respective portions of a ship repair period. There is information that must be exchanged between the parties during the contract period. This standard has been developed to establish common field lengths, names, and types such that the exchanged information can be used directly by the respective software programs without scanning, typing, or redundant keying of information.
WITHDRAWN RATIONALE
This guide provides the database structure of electronic data interchange (EDI) information between ship owner and a shipyard for contract administration.
Formerly under the jurisdiction of Committee F25 on Ships and Marine Technology, this guide was withdrawn in January 2015 in accordance with section 10.6.3 of the Regulations Governing ASTM Technical Committees, which requires that standards shall be updated by the end of the eighth year since the last approval date.

SIGNIFICANCE AND USE
Capturing high quality Reliability, Availability, and Maintainability (RAM) performance data requires careful and consistent collection of equipment failure and repair data, operating hours, and repair time. A standard hierarchy of equipment boundaries has been needed for machinery data exchange among the stakeholders in shipbuilding, ship classification, and ship operations.
Industry and government will use a world standard method for setting the hierarchy of indentures and boundaries required for assigning failure and repair events to equipment for the tracking and calculation of equipment RAM performance.
Agreed boundaries and equipment identifiers make it possible to share equipment data among organizations, benchmark equipment performance, perform modeling and simulation of current and proposed systems, or use performance data to improve operations of commercial and Naval vessels.
RAM analysis is primarily based on the observation of individual components among which identical items contribute to the same data sample. This classification is designed to be used for the identification of individual (unique) components in such a way that identical components can be identified within a given data sample.
SCOPE
1.1 This classification is to serve as an international standard for marine equipment nomenclature, taxonomy, hierarchical data structure, unique identifiers, and boundary definition for the consistent acquisition and exchange of equipment RAM performance data. The standard addresses the classification of mechanical and software products.
1.2 RAM in an acronym for Reliability, Availability, & Maintainability where:
1.2.1 Reliability is the probability that an item can perform a required function under given conditions for a given time interval (t1, t2). It is generally assumed that the item is in a state to perform this required function at the beginning of the time interval.
1.2.2 Availability is the probability that an item is in a state to perform a required function under given conditions at a given instant of time, assuming that the required external resources are provided.
1.2.3 Maintainability is the probability that a given active maintenance action, for an item under given conditions of use can be carried out within a stated time interval, when the maintenance is performed under stated conditions and using stated procedures and resources.
1.3 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory requirements prior to use.

SIGNIFICANCE AND USE
This guide is intended to provide an understanding of the wide range of communication protocols standards, allowing the user to understand better their applicability to shipboard networks and marine platform computerized systems. For computerized networks and systems, communication protocols are necessary for integrating various system devices, providing functionality between dissimilar subnetworks, or for enabling remote connections, either pier side or through geophysical communication technologies.
The wide variety and scope of digital communication protocol standards adds greatly to the complex decision process for specifying compatible protocols for system applications and related devices for the myriad of potential shipboard systems. However, the user must identify the initial networking requirements, so once the network protocols under evaluation are well understood, the decision process should determine the appropriate network protocols. Therefore, this guide is intended to reduce the complexity involved with protocol selection and implementation.
Network protocols define an agreed, quantifiable entity, or set of rules, by which user computers, system networks, and internetworking devices communicate and exchange information. Communication protocols specify essential networking guidelines, such as physical interface connections, or data format and control operations between two communicating computers. Ship and marine digital communication protocol requirements are no different than their land-based networked counterparts. Both require standardized protocol selection, in various protocol categories, including LAN standards, WAN protocols, LAN/WAN protocols, network management, wiring hub configurations/operations, hardware platforms, operating systems, and network applications.
SCOPE
1.1 The principal content of this guide provides a road map to implement a communication network applicable to ship and marine computer systems by:
1.1.1 Examining the relationship of digital communication protocols as a network technological infrastructure,
1.1.2 Outlining the basic building blocks of network topologies and transmission techniques associated with the implementation of transmission media in a network environment; and,
1.1.3 Identifying operating system and environments.
1.2 Using the Open System Interconnection (OSI) model, which provides a layered approach to network functionality and evaluation, common network communications protocols are identified and characterized in this guide according to lower and upper layer protocols corresponding to their degree and type of functionality.
1.3 Although it is desirable that network users, designers, and administrators recognize and understand every possible networking protocol, it is not possible to know the intimate details of every protocol specification. Accordingly, this guide is not intended to address fully every hardware and software protocol ever developed for commercial use, which spans a period of about 25 years. Instead, the user of this guide will be introduced to a brief overview of the majority of past and present protocols which may comprise a ship or marine internetwork, to include Local Area Networks (LANs), Wide Area Networks (WANs), and related hardware and software that provide such network interoperability and data transfer.
1.4 While this guide provides an understanding of the wide range of communication protocols, the user is recommended to consult the reference material for acquiring a more comprehensive understanding of individual communication protocols. However, by examining the basic functions of protocols and reviewing the protocol characterization criteria identified in this guide, the user will be more apt to understanding other protocols not mentioned or addressed herein.

SIGNIFICANCE AND USE
This guide is aimed at providing a general understanding of the various types of hardware devices that form the core of information processing systems for ship and marine use. Ship and marine information processing systems require specific devices in order to perform automated tasks in a specialized environment. In addition to providing information services for each individual installation, these devices are often networked and are capable of supplementary functions that benefits ship and marine operations.
A variety of choices exists for deployment of information processing devices and greatly increases the complexity of the selection task for ship and marine systems. The choice of a particular device or system cannot be made solely on the singular requirements of one application or function. Modern information processing systems are usually installed in a complex environment where systems must be made to interact with each other. Ship and marine installations add an even further layer of complexity to the process of choosing adequate computerized systems. This guide aims to alleviate this task by giving users specific choices that are proven technologies that perform in a complex environment.
Hardware resources used in ship and marine installations are a result of careful consideration of utility and function. These resources may require some physical specialization in order to inhabit a particular environment, but they are in no way different from equipment used in shore-based situations. Ship and marine computer system configurations, interconnections, and support services are essentially the same as those found in a land-based network environment and as a result, the skill sets of ship and marine information processing system users, administrators, and support personnel are interchangeable with those of shore-based activities.
SCOPE
1.1 This guide provides assistance in the choice of computing hardware resources for ship and marine environments and describes:
1.1.1 The core characteristics of interoperable systems that can be incorporated into accepted concepts such as the Open System Interconnection (OSI) model;
1.1.2 Process-based models, such as the Technical Reference Model (TRM), that rely on interoperable computing hardware resources to provide the connection between the operator, network, application, and information; and,
1.1.3 The integrated architecture that can be used to meet minimum information processing requirements for ship and marine environments.
1.2 The use of models such as OSI and TRM provide a structured method for design and implementation of practical shipboard information processing systems and provides planners and architects with a roadmap that can be easily understood and conveyed to implementers. The use of such models permit functional capabilities to be embodied within concrete systems and equipment.
1.3 The information provided in this guide is understood to represent a set of concepts and technologies that have, over time, evolved into accepted standards that are proven in various functional applications. However, the one universal notion that still remains from the earliest days of information processing is that technological change is inevitable. Accordingly, the user of this guide must understand that such progress may rapidly invalidate or supersede the information contained herein. Nonetheless, the concept of implementing ship and marine computing systems based on these functional principles allows for logical and rational development and provides a sound process for eventual upgrade and improvement.

SIGNIFICANCE AND USE
This guide provides a recommended transition plan for a marine software maintainer, when the maintainer is other than the supplier, to develop the capability to make extensive changes or extensions to the programs. Further, this guide provides a recommended interactive process model for managing and executing software maintenance activities. This guide applies principally to the marine software that requires design effort and for which the product requirements are stated principally in performance terms.
SCOPE
1.1 This guide covers a recommended plan for transition and acceptance of marine software that was developed by an activity other than the maintaining activity. It further provides a recommended iterative process model for managing and executing software maintenance activities.

SCOPE
1.1 This classification is to serve as an international standard for marine equipment nomenclature, taxonomy, hierarchical data structure, unique identifiers, and boundary definition for the consistent acquisition and exchange of equipment RAM performance data. The standard addresses the classification of mechanical and software products.
1.2 RAM in an acronym for Reliability, Availability, Maintainability where:
1.2.1 Reliability is the probability that an item can perform a required function under given conditions for a given time interval (t1, t2). It is generally assumed that the item is in a state to perform this required function at the beginning of the time interval.
1.2.2 Availability is the probability that an item is in a state to perform a required function under given conditions at a given instant of time, assuming that the required external resources are provided.
1.2.3 Maintainability is the probability that a given active maintenance action, for an item under given conditions of use can be carried out within a stated time interval, when the maintenance is performed under stated conditions and using stated procedures and resources.
This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory requirements prior to use.

SCOPE
1.1 This guide provides assistance in the choice of computing hardware resources for ship and marine environments and describes:
1.1.1 The core characteristics of interoperable systems that can be incorporated into accepted concepts such as the Open System Interconnection (OSI) model;
1.1.2 Process-based models, such as the Technical Reference Model (TRM), that rely on interoperable computing hardware resources to provide the connection between the operator, network, application, and information; and,
1.1.3 The integrated architecture that can be used to meet minimum information processing requirements for ship and marine environments.
1.2 The use of models such as OSI and TRM provide a structured method for design and implementation of practical shipboard information processing systems and provides planners and architects with a roadmap that can be easily understood and conveyed to implementers. The use of such models permit functional capabilities to be embodied within concrete systems and equipment.
1.3 The information provided in this guide is understood to represent a set of concepts and technologies that have, over time, evolved into accepted standards that are proven in various functional applications. However, the one universal notion that still remains from the earliest days of information processing is that technological change is inevitable. Accordingly, the user of this guide must understand that such progress may rapidly invalidate or supersede the information contained herein. Nonetheless, the concept of implementing ship and marine computing systems based on these functional principles allows for logical and rational development and provides a sound process for eventual upgrade and improvement.

SCOPE
1.1 This guide provides a uniform format and definition of general vessel-related technical information, including ship safety data, to be used by ship owners and operators, at their option and to the extent that they consider beneficial to their operation. It is recognized that all of the data is already contained in various documents on the vessel, but normally not electronically and normally not in one location. The Ship Safety Record is designed to provide an industry-accepted common method of identifying, maintaining, and subsequently communicating the safety-related information needed for maritime operations. It is recognized that many of the data fields are not applicable for every vessel. Appendix X1 and Appendix X2 provide examples of how data elements in this guide may be used for a specific purpose, that is, the USCG's Automated Identification System (AIS) and the Advance Notice of Arrival.

SCOPE
1.1 This guide provides a uniform format and definition of general vessel-related technical information, including ship safety data, to be used by ship owners and operators, at their option and to the extent that they consider beneficial to their operation. It is recognized that all of the data is already contained in various documents on the vessel, but normally not electronically and normally not in one location. The Ship Safety Record is designed to provide an industry-accepted common method of identifying, maintaining, and subsequently communicating the safety-related information needed for maritime operations. It is recognized that many of the data fields are not applicable for every vessel. Appendix X1 and Appendix X2 provide examples of how data elements in this guide may be used for a specific purpose, that is, the USCG's Automated Identification System (AIS) and the Advance Notice of Arrival.

SCOPE
1.1 This standard provides the database structure of electronic data interchange (EDI) information between ship owner and a shipyard for contract administration. Ship owners (hereinafter referred to as owners) and shipyards may each have unique software programs to manage their respective portions of a ship repair period. There is information that must be exchanged between the parties during the contract period. This standard has been developed to establish common field lengths, names, and types such that the exchanged information can be used directly by the respective software programs without scanning, typing, or redundant keying of information.

SCOPE
1.1 This guide provides an overview and guide for the selection and implementation by shipowners and operators of a Fleet Management System (FMS) network of computer services in a client/server architecture (see Fig. 1). The FMS is based upon a wide area enterprise network consisting of an unspecified number of Shipboard Information Technology Platforms (SITPs) and one or more shoreside Land-Based Information Technology Platforms (LITPs), which provides management services for the shipping enterprise. The FMS can be understood as a computer system comprised of one or more LITPs and one or more SITPs. It can be characterized as mission critical 24 365 (24 h/day, 365 days/year).
1.2 The SITP (see Fig. 1) provides a set of software services, including:
1.2.1 Communications Services, to communicate between vessels and with shore via multiple wireless communication technologies;
1.2.2 Data Acquisition Services, providing access to shipboard system data as required for use by other systems and management purposes; and,
1.2.3 Executive Services, providing software process administration and control.
1.2.4 In total, the SITP provides the capability for multiple shipboard computer systems to share data with each other and to communicate with shore-based management or other vessels or both.
1.3 The SITP is understood to consist of integrated hardware, software, a data repository, and standardized procedures, which provide the ability to send, receive, process, transfer, and store data or messages in digital form in a common mode from shipboard systems or administrative utilities or both, and from designated sources outside the network, for example, systems accessed through wireless communication services, such as satellite, VHF, HF, and so forth. Shipboard systems include navigational, machinery control and monitoring, cargo control, communications, and so forth. The SITP also will provide the capability for the remote administration and maintenance of associated computer systems aboard the vessel.
1.4 The SITP requires an underlying hardware and network infrastructure, including a shipboard computer local area network (LAN), file servers, workstations, wireless communications transceivers, cabling, other electronic and optical devices, video display units, keyboards, and so forth.
1.5 The SITP also requires underlying system software providing network operating system (NOS) services, DBMS services, and other system software.
1.6 There also is a layer of shipboard application systems, which are designed to capitalize on the FMS infrastructure to share data with other shipboard systems and management ashore. Those systems also would be able to capitalize on the remote management capabilities of the FMS.
1.7 The LITP is an asset that can exchange operating and administrative data from individual ships and maintain a DBMS to support fleet management and other maritime applications. The LITP will support data repositories, file servers, workstations or personal computers (PCs), and a communication hub providing connectivity to distributed satellite services, VHF (very high frequency), HF/MF (high frequency/medium frequency), and land lines. The DBMS makes possible the development of knowledge-based "decision aids" by providing the ability to retrieve, process, and analyze operational data.
1.8 This guide does not purport to address all the requirements for a SITP, which forms a path for data for direct control of the operation or condition of the vessel or the vessel subsystems.
1.9 In all cases, it shall be possible for all units of navigation equipment resident on the Navigation Equipment Bus to operate and display essential operating data independently of the FMS.
1.10 In all cases, it shall be possible for all units resident on the Control, Monitoring, and Alarm Bus to operate and display essential operating data independently of the FMS.
1.11 In all cases, it shall be possible for all units resident on th...

SCOPE
1.1 The principal content of this guide provides a road map to implement a communication network applicable to ship and marine computer systems by:
1.1.1 Examining the relationship of digital communication protocols as a network technological infrastructure.
1.1.2 Outlining the basic building blocks of network topologies and transmission techniques associated with the implementation of transmission media in a network environment; and,
1.1.3 Identifying operating system and environments.
1.2 Using the Open System Interconnection (OSI) model, which provides a layered approach to network functionality and evaluation, common network communications protocols are identified and characterized in this guide according to lower and upper layer protocols corresponding to their degree and type of functionality.
1.3 Although it is desirable that network users, designers, and administrators recognize and understand every possible networking protocol, it is not possible to know the intimate details of every protocol specification. Accordingly, this guide is not intended to address fully every hardware and software portocol ever developed for commercial use, which spans a period of about 25 years. Instead, the user of this guide will be introduced to a brief overview of the majority of past and present protocols which may comprise a ship or marine internetwork, to include Local Area Networks (LANs), Wide Area Networks (WANs), and related hardware and software that provide such network interoperability and data transfer.
1.4 While this guide provides an understanding of the wide range of communication protocols, the user is recommended to consult the reference material for acquiring a more comprehensive understanding of individual communication protocols. However, by examining the basic functions of protocols and reviewing the protocol characterization criteria identified in this guide, the user will be more apt to understanding other protocols not mentioned or addressed herein.

SCOPE
1.1 The principal content of this guide provides a road map to implement a communication network applicable to ship and marine computer systems by:
1.1.1 Examining the relationship of digital communication protocols as a network technological infrastructure.
1.1.2 Outlining the basic building blocks of network topologies and transmission techniques associated with the implementation of transmission media in a network environment; and,
1.1.3 Identifying operating system and environments.
1.2 Using the Open System Interconnection (OSI) model, which provides a layered approach to network functionality and evaluation, common network communications protocols are identified and characterized in this guide according to lower and upper layer protocols corresponding to their degree and type of functionality.
1.3 Although it is desirable that network users, designers, and administrators recognize and understand every possible networking protocol, it is not possible to know the intimate details of every protocol specification. Accordingly, this guide is not intended to address fully every hardware and software portocol ever developed for commercial use, which spans a period of about 25 years. Instead, the user of this guide will be introduced to a brief overview of the majority of past and present protocols which may comprise a ship or marine internetwork, to include Local Area Networks (LANs), Wide Area Networks (WANs), and related hardware and software that provide such network interoperability and data transfer.
1.4 While this guide provides an understanding of the wide range of communication protocols, the user is recommended to consult the reference material for acquiring a more comprehensive understanding of individual communication protocols. However, by examining the basic functions of protocols and reviewing the protocol characterization criteria identified in this guide, the user will be more apt to understanding other protocols not mentioned or addressed herein.

SCOPE
1.1 This guide covers a recommended plan for transition and acceptance of marine software that was developed by an activity other than the maintaining activity. It further provides a recommended iterative process model for managing and executing software maintenance activities.

SIGNIFICANCE AND USE
Competent information management is essential for safe and productive operation and regulatory compliance. A short list of the functions affected includes decision aids for navigation, communications, ship handling, machinery control, cargo operations, maintenance and repair, personnel records, and environmental protection.
The shipbuilding and shipping industries have identified a need to develop comprehensive standards and guides for implementing computer-based shipboard data management systems.
The FMS may include single or multiple SITPs and single or multiple LITPs and provides the means to integrate shipboard and shoreside computer systems with multivendor connectivity, distributed processing, and electronic data interchange between noncompatible networks, computers, workstations, and peripherals and maintain databases, which promote safety of life at sea, protection of the environment, and operational efficiencies throughout the life cycle of the vessel/fleet. The FMS may incorporate satellite gateways to coastal communication hubs providing access to land-based networks, such as telephone lines, facsimile, e-mail, and expanded satellite services through land earth stations.
The SITP can be configured to provide the ship’control center with access to local control centers, such as for cargo operations, which may be located on the main deck.
This guide has provisions relevant to all components of the FMS platform including the ship earth station, interface devices for subsystems and administrative systems connected to or forming part of the network, communication services, and certain land-based facilities under the direct control of the ship’management.
It is the intent of this guide to provide guidelines for the design and implementation of open client/server architecture for computer and communication networks for shipboard and shore-based applications.
This guide is intended to assist vessel owners, designers, shipyards, equipment suppliers, an...
SCOPE
1.1 This guide provides an overview and guide for the selection and implementation by shipowners and operators of a Fleet Management System (FMS) network of computer services in a client/server architecture (see Fig. 1). The FMS is based upon a wide area enterprise network consisting of an unspecified number of Shipboard Information Technology Platforms (SITPs) and one or more shoreside Land-Based Information Technology Platforms (LITPs), which provides management services for the shipping enterprise. The FMS can be understood as a computer system comprised of one or more LITPs and one or more SITPs. It can be characterized as mission critical 24 × 365 (24 h/day, 365 days/year).
1.2 The SITP (see Fig. 1) provides a set of software services, including:
1.2.1 Communications Services, to communicate between vessels and with shore via multiple wireless communication technologies;
1.2.2 Data Acquisition Services, providing access to shipboard system data as required for use by other systems and management purposes; and,
1.2.3 Executive Services, providing software process administration and control.
1.2.4 In total, the SITP provides the capability for multiple shipboard computer systems to share data with each other and to communicate with shore-based management or other vessels or both.
1.3 The SITP is understood to consist of integrated hardware, software, a data repository, and standardized procedures, which provide the ability to send, receive, process, transfer, and store data or messages in digital form in a common mode from shipboard systems or administrative utilities or both, and from designated sources outside the network, for example, systems accessed through wireless communication services, such as satellite, VHF, HF, and so forth. Shipboard systems include navigational, machinery control and monitoring, cargo control, communications, and so forth. The SITP also will provide the capability for the remo...