F41 - Unmanned Maritime Vehicle Systems (UMVS)

SCOPE
1.1 This guide establishes the basic communications requirements for Unmanned Undersea Vehicles (UUVs). In its first instantiation, this guide serves as only a guideline, and not a definitive directive on acceptable UUV communication standards. In fact, this initial version is more accurately considered a compendium that addresses myriad communication modalities, where the selection of listed standards is determined after communication requirements are tailored to specific UUV applications and payloads.
1.2 This guide is intended to influence the design and development process for the acquisition and integration of vehicles, payloads, and communication system components, while at the same time to avoid specifying particular solutions or products. In its initial release, an additional intent of this guide is to address the communication standards required for operation of the U.S. Navy's planned 21-in. Mission Reconfigurable UUV System (MRUUVS) which is representative of its heavy weight class of UUVs. Guidance provided by the newly mandated and continually evolving, DoD IT Standards Registry (DISR) in the realm of existing military communication standards is also provided as a reference. Although there is a certain emphasis on U.S. Navy UUV missions, there is broad utility across the spectrum of commercial applications as well.
1.3 The breadth of standards addressed within this guide encompasses widely recognized Network standards and RF communications standards, including line of sight (LOS) and beyond line of sight (BLOS). Discussion of optical laser and underwater acoustic communications standards that are in development is also included. Besides identifying existing communication infrastructure, waveforms, and standards, this guide also briefly addresses related issues, security considerations, and technology forecasts that will impact fleet communication systems in the near future (5 to 10 years).
1.4 For ease in reading and utility, specific recommendations of existing standards are captured in tables segregated by communication domain. In some cases where standards are still under development or do not yet exist, details have been reserved for future revisions to this guide. Similarly, in various sections, elaboration of certain topics has either been determined to be beyond the scope of this guide or more appropriate for forthcoming revisions.
1.5 Readers of this guide will also find utility in referencing the related Committee F41 Guides on UUV Sensor Data Formats, UUV Payload Interfaces, and UUV Autonomy and Control. There is a clear relationship that exists in terms of communication systems, external interfaces, data formats, and information/data exchange which can be applied in context with the standards invoked in those documents.
1.6 The values stated in SI units are to be regarded as the standard. The values given in parentheses are for information only.
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 limitations prior to use.
1.7 Table of Contents

SCOPE
1.1 This guide establishes the basic sensor data format requirements for Unmanned Undersea Vehicles (UUVs). This guide is intended to influence the development process for the acquisition and integration of various sensor packages, but at the same time, not specify particular solutions or products. An additional intent of this guide is to address the data format standards specifically required for operation of the U.S. Navy's planned 21-in. Mission Reconfigurable UUV System (MRUUVS), which is representative of its heavy weight class of UUVs. Although this initial release of UUV sensor data formats standards primarily focuses on the U.S. Navy's UUV missions comprising intelligence, surveillance and reconnaissance (ISR), mine countermeasures (MCM), and oceanographic data collection, there is broad utility across the spectrum of commercial applications as well.
1.2 Readers of this guide will find utility in referencing Guides F 2541, F 2594, and WK11283. There is a clear relationship that exists in terms of data formats, external interfaces, and information/data exchange that can be applied in context with the standards invoked in these documents.
1.3 The main body of this guide, Section , provides general guidelines for sensor data, including water column and ocean bottom undersea search and survey (USS) measurements, and above-waterline data. It describes required records, but does not attempt to specify individual record formats, except as already established in existing documentation. Whenever possible, data formats are suggested to conform to existing convention to facilitate data processing and use. This guide generally notes where standard U.S. Department of Defense (DoD) formats are established or de facto commercial formats exist and are adequate, such as widely accepted World Meteorological Organization (WMO) or Intergovernmental Oceanographic Commission (IOC) standards.
1.4 Though the general guidelines established in this guide apply to most oceanographic sensor data, the data types specifically considered here are limited to: water column measurements (including temperature, salinity, currents, optical clarity, and bioluminescence), ocean bottom measurements (including bathymetry, acoustic images, and sub-bottom), ambient noise, and related geophysical parameters. Specific above-waterline ISR sensor data is addressed by reference to governing U.S. military standards for certain data types. Discussion of electromagnetic and electro-optical (EM/EO) data formats (including atmospheric refractivity) is also included.
1.5 Section covers related mission data formats such as timing. It also serves as a placeholder for future discussion of vehicle-specific mission data formats. Navigation, vehicle status, and related vehicle information data formats are expected to be addressed in subsequent versions of this guide. Also included in this section are brief discussions on external interface and command and control formats. Section introduces the topic of metadata formats. Amplification of this subject is warranted and will be incorporated into future versions of the guide. Section briefly identifies general data storage media concerns for UUVs, but does not attempt to mandate decisions best made by system developers based on mission needs. Onboard data storage decisions will be driven by power requirements, data volume, and media cost. Section presents an abbreviated summary of the currently recommended data format standards where they could be identified. Finally, Section exists primarily as a placeholder to address relevant technology forecasts that could impact future data formats.
1.6 The values stated in SI units are to be regarded as the standard. The values given in parentheses are for information only.
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 healt...

ABSTRACT
This guide covers the interface requirements for the physical payload interface of Unmanned Undersea Vehicles (UUVs), specifically the 21-in. heavyweight UUV body. This guide is intended to provide the developer with parameters necessary to integrate various combinations of system components and mission payload packages into the UUV, but at the same time not specify particular versions of a commercial product or tool. This guide does not address specific system functionality required of UUVs, but rather evaluates several autonomous vehicle architectures, performs a functional decomposition, and identifies key aspects that are common throughout.
SCOPE
1.1 This guide covers the interface requirements for physical payload interface for Unmanned Undersea Vehicles (UUVs). In its initial release, the purpose of this standard is to specify the physical, electrical, and operational interfaces between the host UUV and the modular payload sections. This guide provides specific requirements for the 21-in. heavyweight UUV body. Future iterations of this standard will add requirements for additional bodies.
1.2 The desired system is based on the qualitative features defined in this guide and the quantitative requirements as specified in individual performance specifications. Quantitative measures are beyond the scope of this guide. The resulting system is a combination of both.
1.3 This guide is intended to provide the developer with parameters necessary to integrate various combinations of system components and mission payload packages into the UUV, but at the same time not specify particular products. The established standard evaluates several autonomous vehicle architectures, performs a functional decomposition, and identifies key aspects that are common throughout. Through this process, a common architecture standard can be adopted that covers the family of unmanned undersea vehicles (UUVs) and the integration of emerging technologies.
1.4 This guide should be tailored to each application.
1.5 This guide does not attempt to specify a particular version of a commercial product or tool, but it does show examples that might conform. This guide does not address specific system functionality required of UUVs, but focuses on architectural matters.
1.6 The values stated in inch-pound units are to be regarded as standard.
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 limitations prior to use.
WITHDRAWN RATIONALE
This guide covers the interface requirements for physical payload interface for Unmanned Undersea Vehicles (UUVs).
Formerly under the jurisdiction of Committee F41 on Unmanned Undersea Vehicle (UUV) Systems, this guide was withdrawn in January 2016 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.

SCOPE
1.1 This guide establishes the basic sensor data format requirements for Unmanned Undersea Vehicles (UUVs). This guide is intended to influence the development process for the acquisition and integration of various sensor packages, but at the same time, not specify particular solutions or products. An additional intent of this guide is to address the data format standards specifically required for operation of the U.S. Navy's planned 21-in. Mission Reconfigurable UUV System (MRUUVS), which is representative of its heavy weight class of UUVs. Although this initial release of UUV sensor data formats standards primarily focuses on the U.S. Navy's UUV missions comprising intelligence, surveillance and reconnaissance (ISR), mine countermeasures (MCM), and oceanographic data collection, there is broad utility across the spectrum of commercial applications as well.
1.2 Readers of this guide will find utility in referencing Guides F 2541, F 2594, and WK11283. There is a clear relationship that exists in terms of data formats, external interfaces, and information/data exchange that can be applied in context with the standards invoked in these documents.
1.3 Technical sections of this guide are broken down as follows:
1.3.1 Section 5, the main body of this guide, provides general guidelines for sensor data, including water column and ocean bottom undersea search and survey (USS) measurements, and above-waterline data. It describes required data records, but does not attempt to specify data recording formats, except as already established in existing documentation. Whenever possible, data recording formats are suggested to conform to existing convention, facilitating data processing and use. This guide references standard U.S. Department of Defense (DoD) formats or de facto commercial formats where appropriate, such as widely accepted World Meteorological Organization (WMO) or Intergovernmental Oceanographic Commission (IOC) standards.
1.3.2 Section 6 covers related mission data formats such as timing. It also serves as a placeholder for future discussion of vehicle-specific mission data formats. Navigation, vehicle status, and related vehicle information data formats are expected to be addressed in subsequent versions of this guide. Also included in this section are brief discussions on external interface and command and control formats.
1.3.3 Section 7 introduces the topic of metadata formats. Amplification of this subject is warranted and will be incorporated into future versions of the guide.
1.3.4 Section 8 briefly identifies general data storage issues. Onboard data storage decisions will be driven by power requirements, data volume, and media cost.
1.3.5 Section 9 presents an abbreviated summary of the currently recommended data format standards where they could be identified.
1.3.6 Section 10 exists primarily as a placeholder to address relevant technology forecasts that could impact future data formats.
1.4 Though the general guidelines of this guide apply to most oceanographic sensor data, the data types specifically considered here are limited to: water column measurements (including temperature, salinity, currents, optical clarity, and bioluminescence), ocean bottom measurements (including bathymetry, acoustic images, and sub-bottom), ambient noise, and related geophysical parameters. ISR sensor data and other data collected on or above the surface are addressed by reference to governing U.S. military data standards. Discussion of electromagnetic and electro-optical (EM/EO) data formats (including atmospheric refractivity) is also included.
1.5 The values stated in SI units are to be regarded as the standard. The values given in parentheses are for information only.
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 and health practices and determine the appl...

SCOPE
1.1 This guide establishes the basic communications requirements for Unmanned Undersea Vehicles (UUVs). In its first instantiation, this guide serves as only a guideline, and not a definitive directive on acceptable UUV communication standards. In fact, this initial version is more accurately considered a compendium that addresses myriad communication modalities, where the selection of listed standards is determined after communication requirements are tailored to specific UUV applications and payloads.
1.2 This guide is intended to influence the design and development process for the acquisition and integration of vehicles, payloads, and communication system components, while at the same time to avoid specifying particular solutions or products. In its initial release, an additional intent of this guide is to address the communication standards required for operation of the U.S. Navy's planned 21-in. Mission Reconfigurable UUV System (MRUUVS) which is representative of its heavy weight class of UUVs. Guidance provided by the newly mandated and continually evolving, DoD IT Standards Registry (DISR) in the realm of existing military communication standards is also provided as a reference. Although there is a certain emphasis on U.S. Navy UUV missions, there is broad utility across the spectrum of commercial applications as well.
1.3 The breadth of standards addressed within this guide encompasses widely recognized Network standards and RF communications standards, including line of sight (LOS) and beyond line of sight (BLOS). Discussion of optical laser and underwater acoustic communications standards that are in development is also included. Besides identifying existing communication infrastructure, waveforms, and standards, this guide also briefly addresses related issues, security considerations, and technology forecasts that will impact fleet communication systems in the near future (5 to 10 years).
1.4 For ease in reading and utility, specific recommendations of existing standards are captured in tables segregated by communication domain. In some cases where standards are still under development or do not yet exist, details have been reserved for future revisions to this guide. Similarly, in various sections, elaboration of certain topics has either been determined to be beyond the scope of this guide or more appropriate for forthcoming revisions.
1.5 Readers of this guide will also find utility in referencing the related Committee F41 Guides on UUV Sensor Data Formats, UUV Payload Interfaces, and UUV Autonomy and Control. There is a clear relationship that exists in terms of communication systems, external interfaces, data formats, and information/data exchange which can be applied in context with the standards invoked in those documents.
1.6 The values stated in SI units are to be regarded as the standard. The values given in parentheses are for information only.
1.7 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 limitations prior to use.
1.8 Table of Contents:SectionScope1Referenced Documents2Terminology3Significance and Use4Interoperability4.1U.S. Navy UUV Master Plan4.2FORCEnet and DISR Compliance4.3Global Information Grid (GIG) and FORCEnet4.3.1DISR4.3.2Undersea FORCEnet Process Implementation Working Group4.3.3Security4.4Security Considerations4.4.1Data4.5Environmental Measurements4.5.1Anti-submarine Warfare (ASW) Related Data4.5.2Geo positions4.5.3Imagery4.5.4ISR Data4.5.5Command and Control4.5.6Data Gathering4.5.7Data Off-Loading4.5.8Timing4.6Recommended UUV Communication Standards5Introduction5.1Optical Communications Standards5.2Laser Communications5.2.1Acoustic Communications Standards5.3Introduction5.3.1Acoustic Communications Architecture5.3.3RF Communications Standards5.4RF LOS S...

SCOPE
1.1 This guide covers the need for UUVs to operate autonomously, without constant human intervention, and with flexibility based on their payloads and missions places unique requirements on UUV developers. Because the UUV community is expected to expand both its developer base and its user base in the next several years, it recognizes that success relies upon a well-written standard. The standard must encourage compatibility and reconfigurability, provide a common language to describe functional capabilities, and enable meaningful quantitative performance evaluation.
1.2 The scope of this guide includes those characteristics in a UUV system which, when implemented in a detailed design, result in a UUV that is capable of operating for extended periods of time without external intervention. Implicit in this statement is the requirement that the UUV execute its designated sortie plan. Non-expendable UUVs must also return to a rendezvous point for recovery. The top level concept of such an autonomous system is presented in Fig 3. The functional relationships identified in this block diagram will be discussed further in Section 4.
1.3 This guide contains a table of terminology so that autonomy and control can be described within the context of a common language, where all terms have consistent and clearly defined meaning. As introduced in Fig 3, this guide defines high level functional capabilities of the autonomy controller, the vehicle controller, and the payload controller. Correspondingly high level interfaces are also defined.
1.4 Section presents the capabilities that an autonomous system is required to have. The table in this section concentrates on the functional capabilities of the total system, as opposed to the capabilities of the component controllers. A method for verification of the capability is also presented.
1.5 Section presents a set of tables that index the system autonomy capabilities according to three criteria: Situational Awareness, Decision-making, Planning, and Control, and External Interactions. Such a set of qualifiers determines a Level of Autonomy (LOA) measurement for each of the three criteria. No attempt is made to combine these disparate measures into a single index.
1.6 The following are outside the scope of this guide and no part of this guide should be construed to prescribe requirements associated with these areas.Payloads-outside of the generic functions of the Payload controller and the top level interfaces, the design and implementation of payload subsystems are not addressed in this guide. Vehicles-outside of the generic function of the Vehicle controller and the top level interfaces, the design and implementation of the vehicle subsystems are not addressed in this guide. Safety-this guide does not address safety concerns, if any, associated with the use of the UUV system. It is the responsibility of the system designer to establish appropriate safety and health practices and determine the applicability of the regulatory limitations prior to use. Security-this guide does not address security concerns. It is the responsibility of the program referencing this guide to establish security mechanisms that are appropriate for the intended use of the UUV system and the requirements of the end-user of the system data.
1.7 These standards are intended to support the decision process for the acquisition and development of non-specific UUV systems. To the extent that UUV systems are specified, procured, and developed under a modular open system design approach, the autonomy standards presented herein will foster interoperability and reusability within the UUV community.
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 limitations prior to use.
WITHDRAWN RATIONALE
This gu...