Signed SAVE-IDD 15 Feb 23.pdf

Standardized A-Kit / Vehicle Envelope

(SAVE)

An Interface Description Document for

C5ISR Systems Integration into Army Ground Vehicles

Distribution A - Approved for Public Release, Distribution is Unlimited

PEO GCS, PL CTPI

Detroit Arsenal, MI

July 2022 version 1.01 ii

This page intentionally left blank.

i

Standardized A-Kit / Vehicle Envelope (SAVE) Interface Description Document (IDD)

Signature Blocks

MR. ANDREW DIMARCO

Program Executive Officer, Combat Support & Combat Service Support

MR. MARK C. KITZ

Program Executive Officer, Intelligence, Electronic Warfare and Sensors

GLENN A. DEAN

Brigadier General, USA Program Executive Officer, Ground Combat Systems

ANTHONY W. POTTS

Major General, USA Program Executive Officer, Soldier

ROBERT M. COLLINS

Major General, USA Program Executive Officer, Command Control Communications Tactical

DIMARCO.ANDREW.

JOHN.1022764442

Digitally signed by

DIMARCO.ANDREW.JOHN.1022

764442 Date: 2022.03.08 09:15:01 -05'00'

KITZ.MARK.C.1

242824748

Digitally signed by

KITZ.MARK.C.1242824748

Date: 2022.03.24 16:05:34 -04'00'

DEAN.GLENN.ALL

EN.III.1167281857

Digitally signed by

DEAN.GLENN.ALLEN.III.11672818

Date: 2022.04.05 14:02:01 -04'00'

POTTS.ANTHONY.W

AYNE.1068534328

Digitally signed by

POTTS.ANTHONY.WAYNE.1068

534328 Date: 2022.04.11 16:58:37 -04'00'

COLLINS.ROBERT.M

ORGAN.1039131060

Digitally signed by

COLLINS.ROBERT.MORGAN.10

39131060 Date: 2022.04.22 16:32:12 -04'00' v

Executive Summary

This is the Standardized A-Kit / Vehicle Envelope, or "SAVE" standard. This Interface Description Document (IDD) describes the size and shape of a standard mounting location and set of physical interfaces for integration of Command, Control, Computers, Communications, Cyber, Intelligence, Surveillance, and Reconnaissance (C5ISR) systems into Army ground vehicles. It is intended to provide long term predictability and stability for vehicle and systems development. SAVE was initially developed for radios but also applies to computers and other systems such as the Integrated Visual Augmentation System (IVAS) vehicle integration kit and its Tactical Cloud Package (TCP), the CMOSS Mounted Form Factor (CMFF) first instantiation of the C5ISR Modular Open Suite of Standards (CMOSS), Electronic Warfare (EW) kits, etc. SAVE is a subset of the overall PEO GCS Common Infrastructure Architecture (GCIA) - the over-arching framework for an in-vehicle network to facilitate the integration of radios, computers, networks, etc., into ground combat vehicles. GCIA prescribes a modular open systems approach (MOSA), using Vehicular Integration for C4ISR/EW Interoperability (VICTORY) and other open interface standards for data sharing, enabling CMOSS and other MOSA benefits. SAVE is one of the physical portions of system integration within GCIA. SAVE also applies to PEO CS&CSS and other platforms that have no dependency on GCIA.

This IDD documents SAVE as an appropriate compromise between rigid Military Specifications and loose general descriptions. While this is not a contractual requirement document, to facilitate re-use of language in this IDD by PMs in their requests for proposal (RFPs) and other contracts we use language such as "shall" and "must" to indicate requirements to comply with SAVE, versus "should" or "may" to indicate design suggestions that are not required to be SAVE compliant.

SAVE incorporates the standards negotiated between platform PMs and PM TR/PdM HMS MP during HMS MP ("Handheld, Manpack, and Small Form Fit – Manpack" a multi-function data radio/SINCGARS replacement) development in the 2013 timeframe, per the "Platform Requirements for the HMS Manpack System Full Rate Production (FRP)" memo dated 20 March 2013. We intend to build upon this progress, expanding to include all current and future radios, and other C5ISR systems.

Ground vehicle program offices and C5ISR system program offices have agreed that adopting SAVE should allow significant reduction in cost and schedule when integrating new C5ISR system technology into ground platforms. Platforms will provide a standardized integration space and connections for C5ISR systems, and system PMs will acquire C5ISR devices which fit into this space and use these connections either natively or via adapters (mounting trays, cables, etc.) which the system vendor or PM provides. SAVE will not eliminate the need for Non-Reoccurring Engineering (NRE) or safety testing, but in most cases it should accelerate the process.

By only specifying the outer envelope (maximum dimensions) and by providing for a range of possible connection configurations within this envelope, significant flexibility is retained for competitive acquisition. C5ISR systems can still come in a variety of sizes and shapes, and different connection techniques can be adapted as well. Our intent is to enable rapid flexible acquisition of advancing technology at competitive costs, while maintaining sufficient constraints to avoid prohibitive cost and schedule for vehicle integrations.

vi

This page intentionally left blank.

vii

Table of Contents

1. Introduction ................................................................................................................................................................ 1-1

1.1. Background and Motivation ....................................................................................................................... 1-2

1.2. SAVE Implementation Plan ........................................................................................................................ 1-3

1.3. Relationship to Other Standards .............................................................................................................. 1-4

1.4. Intended Use of This Document ............................................................................................................... 1-5

1.5. A-Kit vs. B-Kit ................................................................................................................................................... 1-6

1.6. SAVE Standard Maintenance and Updates ........................................................................................... 1-9

2. SAVE Physical Attributes ..................................................................................................................................... 2-10

2.1. Dimensions and Connection Locations ............................................................................................... 2-11

2.2. Weight ............................................................................................................................................................... 2-13

2.3. External Amplifiers ...................................................................................................................................... 2-13

2.4. Remote Human Machine Interface ........................................................................................................ 2-14

2.5. Installation and Accessibility ................................................................................................................... 2-14

2.6. Color ................................................................................................................................................................... 2-15

3. SAVE Connectors and Connection Patterns ................................................................................................. 3-16

3.1. RF Connectors and Cables ......................................................................................................................... 3-16

3.2. Power ................................................................................................................................................................ 3-19

3.3. Data .................................................................................................................................................................... 3-20

3.4. Intercom (speakers / headsets) ............................................................................................................. 3-21

3.5. Mounting Tray/Plate Provisions ............................................................................................................ 3-23

4. SAVE Environmental Tolerances ...................................................................................................................... 4-25

4.1. Thermal Loading ........................................................................................................................................... 4-26

4.2. Environmental Testing ............................................................................................................................... 4-26

5. Information Assurance and Cybersecurity ................................................................................................... 5-27

6. Manuals and other Logistics and Sustainment ........................................................................................... 6-28

7. Examples and Caveats ........................................................................................................................................... 7-29

8. Subdivision for Smaller Devices ....................................................................................................................... 8-32

9. Future Extensions ................................................................................................................................................... 9-34

10. Conclusion ......................................................................................................................................................... 10-35

1. Appendixes ............................................................................................................................................................. 10-36

1.1. Abbreviations and Acronyms ............................................................................................................... 10-36

1.2. Technical References ............................................................................................................................... 10-38

1.3. Change Log ................................................................................................................................................... 10-39 viii

List of Figures

Figure 1. SAVE Envelope: Maximum Volume Allowed for SAVE Compliant Systems, Minimum Volume Provided by SAVE Compliant Vehicles .............................................................. 2-10 Figure 2. Example wiring for a Dual HMS MP with 2 MBAs ............................................................ 3-18 Figure 3. Example wiring for a Dual HMS MP with 4 MBAs ............................................................ 3-19 Figure 4. Rear M-1151 Vehicle Mount Audio Interface Connector .............................................. 3-21 Figure 5. MIL-DTL-55116 Front Radio Audio Interface Connector ............................................. 3-23 Figure 6. SINCGARS mounting hole pattern .......................................................................................... 3-24 Figure 7. SAVE mounting hole pattern ..................................................................................................... 3-24 Figure 8. SINCGARS is SAVE compliant - except for Ethernet connections ............................. 7-29 Figure 9. Collins Aerospace Dual HMS MP is SAVE compliant ....................................................... 7-29 Figure 10. Notional platform with 4 SAVE envelopes - e.g. for Command or Retrans ........ 7-30 Figure 11. Notional platform with 3 SAVE envelopes ....................................................................... 7-30 Figure 12. Examples of hardware installations that would be SAVE compliant .................... 7-31 Figure 13. More efficient example of 5 devices sharing a single SAVE envelope .................. 8-32 Figure 14. Less efficient example of 3 devices sharing a single SAVE envelope. ................... 8-33

List of Tables

Table 1. A-Kit versus B-Kit ............................................................................................................................... 1-7 Table 2. SAVE Dimensions ............................................................................................................................. 2-12 Table 3. Summary Table of SAVE Connectors ....................................................................................... 3-16 Table 4. Rear Vehicle Mount Audio Connector Pin Mapping .......................................................... 3-22 Table 5. MIL-DTL-55116 Front Radio Audio Connector Pin Mapping ....................................... 3-23

1-1

1. Introduction This document describes the Standardized A-Kit / Vehicle Envelope (SAVE) - the size and shape of a standard mounting location, or "envelope," and set of physical and electrical interfaces for C5ISR system integration into Army ground vehicles. The SAVE standard is intended to provide a clear and well-defined boundary for integration of C5ISR systems in vehicles, adding long term stable predictability for vehicle and C5ISR system developers.

The SAVE standard is an agreement between ground vehicle program offices and C5ISR system program offices. Discussion amongst PMs led to agreement that this will provide a significant reduction in time and resources to integrate new C5ISR system technology into ground platforms. Platforms will provide a standardized integration space for C5ISR systems, and system PMs will acquire C5ISR systems which fit in this space - either natively or via adapter trays and connectors as required. This will allow rapid and affordable technology update cycles on both the vehicle and system side, enabling the United States Army to maintain operational overmatch with near peer competitors in combat.

SAVE is intended to apply to any modular system electrically and/or digitally integrated into an Army platform. It is not intended to cover stowed equipment, vehicle intrinsic elements such as engines or weapons, or intrinsically external components such as antennas or armor. It may, however, apply to elements of systems such as a computer controller for an active protection system.

This document is organized into sections that cover various aspects of the SAVE standard;

compliance with all sections is necessary to fully meet the standard. Each element of compliance is beneficial in its own right, but these characteristics together were identified as those which drive integration costs.

Section 2 - Physical - size & shape of the SAVE envelope and related aspects such as which sides cables must be able to connect to;

Section 3 - Connectors - types of connectors for power, RF, etc., and patterns for how radios are wired to antennas Section 4 - Environmental - requirements for vibration, temperature, electromagnetic effects, etc.

SAVE does not cover cybersecurity, information assurance, or co-site interference – it is focused on internal physical aspects only. Many other standards cover these issues, such as ATP 6-02.53 appendix H covers co-site. SAVE is intended to remain bounded to internal C5ISR system physical integration challenges.

SAVE will also help with Logistics and Sustainment (Section 6) with rules following the pattern established in the sections listed above.

In this IDD "A-Kit" refers to the components managed/owned/provided by the vehicle PM, as opposed to the "B-Kit" components provided by the C5ISR system PM. See section 1.5 for more details and examples of A-Kit versus B-Kit.

This is a living document that will evolve based on the needs of the platform and C5ISR communities. Please review this document critically and send any suggestions for improvement to usarmy.detroit.peo-gcs.mbx.SAVE@army.mil and we will work to improve

it. In addition, we will update this document as needed to capture any changes, caveats, or

1-2 non-compliances and distribute to ensure that stakeholders are aware. Vehicle specific modifications or additional restrictions will be added as annexes as required. We will also review with PEO leaders on at least an annual basis to ensure that the stakeholders remain engaged and in agreement. The latest version can be found at:

https://kcp.army.mil/sites/apeosei/mosa/documents/SAVE

1.1. Background and Motivation

There is clear and pervasive direction from senior Army leadership to accelerate the pace of technology upgrades. Adversaries have learned how to defeat the 30-year-old radios currently fielded in our ground combat vehicles and are outpacing our technology updates in general. It is likely that any future C5ISR system will require updates at least as frequent as every few years to remain tactically viable.

The objective is to make installation of C5ISR systems in Army Vehicles as simple as the installation of appliances at home – where power, gas, etc. connections are already standardized, and appliances are purchased to fit in the available space rather than, for example, re-building a kitchen around a new refrigerator. The intent of SAVE is to work together to achieve this same sort of standardization for ground combat platforms and C5ISR systems. Radios and Waveforms now change faster than the standard ground platform integration timeline, so some sort of accelerating change is required. SAVE will provide part of that acceleration.

Exacerbating this problem are congressionally mandated multi-vendor and non-developmental approaches to C5ISR system acquisition. These impose additional challenges, leading to cost & schedule growth. Unstable funding over protracted periods of time cause additional problems that can be mitigated by accelerating fielding timelines.

In addition, in the near future we expect to field new platform Mounted Capability Sets (M- CS) which will include new systems that will change frequently such as:

New radios, New waveforms, A new Assured Position Navigation Timing (A-PNT) system, New Electronic Warfare (EW) systems, Vehicle Protective Systems (VPS) components and subsystems, Kit to harmoniously synchronize dismounted Soldier electronics with vehicle electronics (e.g. IVAS Mounted Soldier, and Nett-Warrior support kits), and Ubiquitous use of robotic systems in partnership with manned ground vehicles.

The expectation based on current planning from the Network Cross Functional Team and Army Futures Command is that there will be updated technology in capabilities sets on a two-year cycle. Thus, it is imperative that the Army community develop faster methods to safely and effectively integrate rapidly changing C5ISR systems into ground combat platforms.

The long-term objective of the SAVE standard is to render fielding C5ISR systems to ground vehicles as simple as fielding C5ISR systems to dismounted Soldiers. Training will be required, and the C5ISR systems must previously be vetted for performance, 1-3 environmental survivability, and system of systems compatibility, but lengthy new NRE cycles should not be required. New vehicles can be designed around, for example, a “SAVE Compliant Data Radio” instead of a specific vendor or model number; and design can safely begin years before the radio is available. It is unlikely that NRE and testing will be reduced to zero, and these will vary by C5ISR system and Platform, but with full adoption SAVE should greatly reduce the timelines required.

It will take time to reach a high level of standardization and compatibility, but in the meantime incremental steps of increasingly standardized systems and vehicles will yield increasing cost and schedule benefits. Adopting SAVE is not an all or nothing endeavor. We have already made significant steps in this direction, and savings are already being realized as a result.

1.2. SAVE Implementation Plan

The implementation plan for SAVE begins with Assistant Secretary of the Army for Acquisition Logistics and Technology (ASA(ALT)) endorsement of this document as applicable to the above signed PEOs. Recognized as a best practice by these PEOs, this document, or the specifications in this document, will be included as requirements in new C5ISR system acquisitions, new vehicle acquisitions, and any new integration effort. Where full incorporation is not practical, exceptions should be negotiated between vehicle and system PMs, and Army Capability Managers (ACMs). PdL GCPI will help facilitate these negotiations.

The initial objective is to implement the first generation of SAVE compatibility during M-CS fielding to SBCT and ABCT formations, and during new vehicle acquisitions.

SAVE can also be included in new vehicle recapitalization or refresh efforts. It is intended to become part of existing vehicle and system upgrades, not to force a separate independent effort just to adapt vehicles or systems to the SAVE standard.

In most cases this will result in relatively minor cost changes to an existing effort. The current HMS MP radios are mostly SAVE compliant already, and integration efforts to accommodate these radios are therefore also mostly SAVE compliant. Full compliance may require the addition of a few extra cables or cable paths to ensure future flexibility. The key focus going forward will be on including SAVE standards in acquisition programs for future systems, such as CMFF and the Optionally Manned Fighting Vehicle (OMFV), so that integrating standard Army equipment is much easier in standard Army platforms.

Cost/benefit analyses will be required when considering SAVE updates to integration efforts already underway, or when integrating into difficult to modify legacy vehicles.

The focus will also be on a paradigm shift in how the community considers integration into vehicles. For example, instead of contracting an effort to integrate a PRC-155 LRIP HMS MP radio into a vehicle variant, one would contract an effort to add a SAVE compliant C5ISR system envelope into that vehicle. The initial integration effort would require the standard cost and time, plus some additional cost to provide future upgrade flexibility as specified here, but subsequent integration of SAVE compliant C5ISR systems to that vehicle would require only minimal cost and schedule. More importantly, new vehicles can be designed around an appropriate number of SAVE compliant devices years before those devices are

1-4 available, and still retain high confidence that they can be readily integrated at the appropriate time.

Imagine that by 2028 we have fielded not only robust, resilient, and highly capable C5ISR systems and integrated tactical networks to our forward units, but that we have also acquired the ability to upgrade those systems across all of these modernized brigades in a matter of months instead of years at a fraction of the current cost. That is the ultimate motivation for the SAVE standard.

1.3. Relationship to Other Standards

SAVE is intended to nest within the GCIA standard and to be compatible with and to supplement VICTORY, CMOSS, SOSA and other current standards that are in use or being developed to help move the Army to better MOSA architectures in our combat platforms.

SAVE covers the purely physical elements while other standards focus on the data flowing between systems and the logical organization of those systems within a vehicle. For example, rather than calling for any specific VICTORY component types or versions here, we refer to the current CMOSS and VICTORY documentation for such details.

GCIA - the PEO GCS Common Infrastructure Architecture - provides a common vision for PEO GCS platforms for how components are connected logically inside of vehicles and where open interfaces exist to allow modular replacement of systems, enabling upgrade and re-use of individual capabilities within and between platforms. It provides a ready to use open systems architecture and software modules, with common GCS applications and services, and standard interface specifications, as well as common scope language and test strategies. The intent is to enable platform PMs to more rapidly coordinate MOSA processes in contracting with industry providers, and to ensure cross compatibility within GCS. GCIA incorporates SAVE to cover the physical size and shape of components.

The VICTORY standard, which is also incorporated within GCIA, further specifies data types for messages sent between devices on platforms - such as the underlying Ethernet standard, PNT messages, Radio Control messages, etc. between systems. VICTORY also does not specify connectors or physical attributes, and so does not overlap or conflict with

SAVE.

CMOSS is a suite of standards that cover connection and data interfaces for card or modular devices within a common chassis to provide multiple functionalities within a smaller space.

CMOSS does cover some physical attributes of systems, but only internal to a CMOSS compliant device (CMFF being the first), while SAVE covers the outer envelope and external interfaces of that device. The first CMFF systems will fit within a SAVE envelope, with SAVE specifying external interfaces while the CMOSS standard covers internal interfaces and data specifications over those interfaces. CMOSS also includes the VICTORY standard and is compatible with GCIA, as devices can be organized within CMFF and communicate with each other using GCIA principles and software. It will be important as CMOSS and SAVE evolve to ensure that they remain compatible with clear delineation of areas of responsibility.

The SOSA (Sensor Open Systems Architecture) initiative is another new standard that will complement SAVE. It has been added to the CMOSS standard. Formed as a Consortium of

1-5

The Open Group, SOSA addresses the challenges of rapid, affordable capability evolution for today’s military community, focused on electromagnetic sensor technology. Part of the SOSA approach is to develop an Open Systems Architecture (OSA), captured in the SOSA Technical Standard, that addresses software, hardware, and interfaces. This OSA is designed to promote software, hardware, and interface portability and create product families across the Communications, EO/IR, EW, Radar, and SIGINT community. The SOSA Technical Standard is intended to promote the development of reusable sensor components applicable to a broad class of sensors and host platforms. The SOSA standard focuses on software and architectural aspects as opposed to the physical volume focus of SAVE. Both standards call out MIL-DTL-38999/Series III connectors, though SOSA provides more detailed specifications for data and signal connections and SAVE provides more options for power connections. Where there is overlap, either connector standard may be used (more detail is provided in Table 3 – Summary Table of Save Connectors). As both standards evolve, we will work to avoid overlap or conflicts between SAVE and SOSA.

1.4. Intended Use of This Document

The management approach for SAVE is centralized planning with de-centralized execution.

This is written as an IDD to avoid the challenges and intrinsically brittle nature of providing an interface control document (ICD) or a formal specification document. The implementation of SAVE will vary with each platform, new technology will dictate shifts in design by the C5ISR systems, and thus it is anticipated that some exceptions from both sides will be required. Our intent is to allow enough flexibility for affordable and prompt adoption by all PMs involved, while providing enough guidance to ensure that the implementations developed by each vehicle PM have a high probability of supporting all new C5ISR systems acquired over the next decade.

The intent for SAVE is that C5ISR system PMs and vehicle PMs adopt, include, or reference appropriate pieces of this document as a threshold requirement in future acquisitions in whatever form is most appropriate for their acquisition process. This will include adapting the requirements here to appropriate language in their RFPs and other legal/contractual documents. To facilitate re-use of language in this IDD, we use terms like "shall" and "must" to indicate requirements to comply with SAVE, versus terms like "should" or "may" to indicate design suggestions that are not required to be SAVE compliant. Modification to the SAVE requirements should be coordinated between system and vehicle PMs - PdL GCPI can assist with this coordination.

Coordination is still required between PEOs and with Army Capability Managers (ACMs) to determine the correct number of SAVE envelopes required per vehicle role. Cost/Benefit analyses will be required and a complete specification for all vehicles and roles is beyond the scope of this document.

It is assumed that C5ISR PMs will develop and coordinate batches of equipment to fit within a single SAVE envelope where appropriate – e.g. for CS fielding where multiple small systems are required. It would be inefficient and unnecessary to allocate an entire SAVE envelope for each small item. This empowers PEO C3T with flexibility to develop and evolve their system of systems approach while platform PMs can provide a long-term

1-6 stable space within which to do so. Section 8 suggests compatible sizes to design towards with smaller devices, to facilitate sharing SAVE slots.

Vehicle PMs will upgrade to SAVE standards as part of each new C5ISR system integration so that the vehicle acquires not only capability to host the current system, but also compatibility with any future SAVE compliant C5ISR system. They will also include as threshold requirements that any new vehicle include an appropriate number of SAVE envelopes based on its anticipated role (e.g. 1 for CMFF or a data radio system and 1 for CS support equipment in a simple vehicle role, while a command vehicle role may require 3 for POP equipment, 2 for additional RF equipment, and 1 for additional compute capability, with 6 envelopes total, etc.). Vehicle PMs must work with their ACMs to determine the appropriate number.

Distinction is included in this document regarding what constitutes A-Kit (Platform PM responsibility) versus B-Kit (C5ISR PM responsibility) and the interfaces between them.

The intent here is to provide complete clarity of the interface points between the vehicle and the system so that development of C5ISR systems and vehicles can occur independently while retaining a high confidence that modern systems will readily integrate into modern vehicles.

The intent is also that the SAVE standard will be socialized to industry so that they can adapt their efforts in new product development accordingly. Thus, with wide and fair distribution of this intent, competitive pressure will automatically move industry towards SAVE compliance even without direct Government investments. The SAVE standard leaves plenty of room for innovation within the SAVE volume, it simply requires industry to not build systems that are, for example, too large or power hungry for Army platforms to support.

Partial compliance with the SAVE standard will still provide partial benefit, so perfect implementation is not required for SAVE to provide value. Until otherwise directed, PEO GCS / PL Capability Transition & Product Integration (CTPI) / PdL Ground Combat Product Integration (GCPI) shall create and moderate IPTs as required to engage all necessary stakeholders and communicate updates and nuances of implementation. As exceptions are identified, PdL GCPI will facilitate negotiations between PMs and will facilitate capture of decisions in memorandums of agreement. These will also be added as appendices in this document to maintain visibility to all stakeholders.

1.5. A‐Kit vs. B‐Kit

The following table provides further clarity about what is A-Kit provided by the vehicle versus what is B-Kit, provided by the C5ISR system vendor and/or PM. The SAVE concept is intended to allow designs where new B-Kit can be installed in vehicles without modification to A-Kit. It is anticipated that most C5ISR systems will require some level of adapter kit to meet the SAVE standard, in the form of connector adapters, extension cables, etc. These will be provided by the C5ISR system PM as part of the B-Kit. This could be either a requirement imposed on the system vendor, or additional interface components that the PM acquires separately & provides along with the primary system.

1-7

In general, the C5ISR system PM provides everything inside the SAVE envelope, and also some systems such as antennas and triplexers that may be mounted outside. Vehicle PMs provide power, RF, etc. connections coming from the vehicle to the SAVE envelope. These are only general requirements and may not apply in all cases given the wide range of roles for some platforms. For example, many FMTV platforms may not utilize any C5ISR equipment, whereas a Stryker platform almost certain to need at least two systems. For vehicles needing less systems, providing a path for RF, intercom and data cables instead of including the cables themselves in every platform is an economical and appropriate compromise. Vehicle PMs may determine in consultation with their ACMs whether to provide all cables in advance or just paths for cables to be installed as needed later.

In the case of a large System of Systems suite of equipment (e.g. PoP or SNE), multiple SAVE envelopes will be required. An analysis by the vehicle and system PMs would be in order to effectively and efficiently utilize these envelopes. If it is determined that the last envelope is only partially filled then it may be appropriate to mount smaller components in a non-SAVE envelope location, or to share that location with other smaller systems. The intention going forward is that future generations of equipment will be designed at inception to be mounted in SAVE envelopes and to utilize those spaces efficiently.

Table 1. A‐Kit versus B‐Kit

A‐Kit (Vehicle Provides) B‐Kit (C5ISR System PM Provides)

Metal plate physically attached to the vehicle providing a MT-6352 bolt hole pattern to mount the C5ISR system

Baseplate, Trays, Radios / Computers / etc., and connection hardware such as bolts, nuts, washers, etc.

Vehicle power cables Any required power conditioning or routing beyond the basic vehicle power connections (see Section 3.2 Power)

RF cables between SAVE envelope and antennas

(See section 3.1 – discussions with ACMs about vehicle roles are required to determine the appropriate # of cables or cable paths to provide off the assembly line for each vehicle type)

Triplexers, Diplexers etc. to merge/split signals, RF connector adapters, RF angle connectors, etc. as required

Intercom systems throughout the vehicle per vehicle requirements, where already required by that vehicle; including addition of radio interface terminals (RIT) if required.

(Does not imply addition of intercoms to vehicles that do not already have this requirement. For families of vehicles where many do not but some do, providing a path

Handsets/Headsets & Loudspeakers that connect to the front of the radio, and connectors on the radio that can connect to standard intercoms

1-8

A‐Kit (Vehicle Provides) B‐Kit (C5ISR System PM Provides) for cabling to be added as appropriate is acceptable.)

Ethernet data cables to vehicle C5ISR router when present, cable mounting locations at SAVE envelopes to facilitate additional cables between SAVE envelopes if required.

(Does not imply a requirement to add a router/switch where one is not already required by the vehicle)

Additional switching and routing between C5ISR systems as required beyond the connections provided by the vehicle, including cables between SAVE envelopes to connect C5ISR systems.

Serial cables to vehicle provided Mounted Assured PNT System, Inertial Navigation Unit, etc. as required if not satisfied by standard Ethernet links

(As above, this applies to systems already required on the vehicle side, interfacing to new C5ISR systems)

Antennas and RF Power Amplifiers

Software: updates as necessary for any digital integration of C5ISR components in the SAVE envelope to appropriate vehicle components, including associated cybersecurity, authority to operate, etc.

testing & certifications. Not applicable if the vehicle has no digital systems interacting with the C5ISR components in the SAVE envelope.

Software: as necessary for digital integration of C5ISR components to appropriate vehicle components, and between C5ISR components in the same SAVE envelope or other SAVE envelopes on the vehicle, including associated cybersecurity, authority to operate, etc.

testing & certifications.

This IDD serves as an agreement between PEOs that the vehicle PMs will handle the left column A-Kit and the C5ISR system PMs will handle the right column B-Kit. The clear delineation of responsibilities eases everyone's integration planning and development efforts going forward.

Note that software falls on both sides - the SAVE standard will not eliminate the need for close coordination on digital interaction between the vehicle and C5ISR systems, and collaboration to achieve the necessary performance, safety, and cybersecurity certifications required. It is expected that software updates will be key elements of future modernization.

Note that VIC (vehicle intercom / headsets) systems and the infrastructure required to enable additional radio connections to those systems where they already exist are not covered here. This is beyond the scope of the SAVE standard, though it is important that vehicle and system PMs coordinate and come to agreement on how to resolve this prior to

1-9 any modernization effort. As of this writing there is no general or universal agreement as to where this responsibility lies.

Also note that this does not replace the need for coordination between PMs prior to integration and fielding activities in general – many responsibilities and execution plans need to be worked out that are not covered here, and modifications to the above may be appropriate in some cases. Responsibility for costs are one example of coordination not covered by the SAVE IDD, and for many efforts A-Kit costs are covered by B-Kit owners.

1.6. SAVE Standard Maintenance and Updates

This document will be routinely reviewed and updated, with PEO GCS / PL CTPI / PdL GCPI taking the lead for now, working in concert with all stakeholder PEOs and PMs. In general, changes will be accumulated throughout the year, to be briefed, reviewed, and adopted at the Network Modernization and Fielding Synchronization TEMs, typically bi-annual, hosted by PEO C3T and PEO GCS, or other similar network community gatherings. Ad hoc changes will be implemented and socialized on an accelerated schedule if required.

Key Stakeholders Include

PEO GCS: PM SPHS, PM MAV, PD MBTS, PM SBCT, PL MPF, PM MCS, PL CTPI

PEO CS&CSS: JPO JLTV, PM TS

PEO C3T: PM TR, PM MC, PM TN, PM I2S

PEO IEW&S: PM PNT, PM EW&C, PM IS&A

PEO Soldier: PM IVAS

Please send comments and suggestions, including additions to the stakeholder list above, to PEO GCS/PL CTPI/PdL GCPI:

usarmy.detroit.peo-gcs.mbx.SAVE@army.mil.

The current version of this document will be posted at:

https://kcp.army.mil/sites/apeosei/mosa/documents/SAVE

2-10

2. SAVE Physical Attributes This section covers the physical envelope and connection points of SAVE. The concept of the physical envelope of the SAVE standard is illustrated in the figure below. Dimensions of the envelope are detailed in Section 2.1 below. This section also covers the physical locations (surfaces of the envelope) that cables must be able to reach. Note that environmental requirements are included as well. This is particularly key in heavily armored platforms which tend to have a) the most challenging requirements and b) the least amount of available space. If cooling fans or other mechanisms are required for a system to survive the specified environment, those mechanisms must also be contained within this envelope.

Figure 1. SAVE Envelope: Maximum Volume Allowed for SAVE Compliant Systems, Minimum Volume Provided by SAVE Compliant Vehicles

The oval loops in the diagram illustrate that cables shall be provisioned with additional length to allow for new attachments with the SAVE envelope or adjacent SAVE envelopes to future C5ISR systems. The exact spare length requirements are not specified as they will depend on vehicle dimensions, but are intended to be on the order of one to two feet to reach the necessary locations depending on vehicle rack layout, cable bend radius etc. It is not intended that enough spare cable be included to reach a non-adjacent SAVE location, e.g. externally or on the opposite side of the vehicle. This is discussed in more detail at the end of section 2.1 below.

SAVE was originally developed to hold a dual HMS MP Gen 2 four channel radio, but it can accommodate a wide range of C5ISR systems. The new CMFF radio/computer/APNT system shall fit within a SAVE envelope, and the new TCP on-board computing and routing capability to support IVAS is also being designed around the SAVE standard. SAVE can also

2-11 support any legacy SINCGARS radio, VRC-87 through VRC-91, with only a few RF cable adapters required. It also easily holds a Mounted Leader Radio (VRC-135). It will not apply to all C5ISR systems, but compliance is possible for most of them. Going forward, the goal is to ensure that all future C5ISR systems can be incorporated into the SAVE envelope.

However, this effort does not dictate retrofitting of vehicles or systems already fielded.

For radios, at least two amplifiers shall fit within the SAVE envelope where such amplifiers are required. For CMFF it is anticipated that they will mount on the antenna risers external to the vehicle, which is also acceptable assuming an appropriate design to meet survivability requirements. In general, all system ancillaries should fit within the SAVE envelope, except where there are significant technical reasons to do otherwise – such as mounting a triplexer close to an antenna to enable one long cable instead of three to support all bands, or where an amplifier must be mounted close to the antenna to minimize noise.

A vehicle may have several SAVE envelopes if multiple C5ISR systems are required, as is typical with Command or Retransmission roles. For example - in a vehicle intended to provide links between physically isolated networks - up to 6 channels of SINCGARS may be required. Thus the vehicle may need one SAVE envelope to hold a 4 channel dual HMS MP radio, and a second SAVE envelope to hold a 2 channel single HMS MP radio. Then the new CS equipment providing IVAS interfaces, radio routing, TCP etc., would likely require a third SAVE envelope to be added as well. The savvy vehicle designer should provide a fourth SAVE envelope as margin for future growth.

The following section details the physical dimensions of the SAVE envelope.

2.1. Dimensions and Connection Locations

The table below provides dimensions and connection locations within a SAVE envelope.

These dimensions shall be inclusive of baseplates, mounting trays, etc., i.e. from the bare metal of the vehicle. All baseplates and trays as well as radios, computers, etc. must fit within these overall dimensions. These represent the inner solid line shown in Figure 1 above. It is anticipated that in most cases one or more C5ISR systems will attach to some sort of baseplate or tray system with adapting hole patterns, which allows most existing systems to be adapted into a SAVE compliant version without modification to the system itself. This tray will usually perform a shock absorbing function as well.

Platforms shall provide a mounting plate suitable to hold the C5ISR system. Most vehicles have that capability today for a SINCGARS radio, providing the base for one SAVE envelope.

Platforms that do not have a radio mounting location shall be responsible for adding one – for example adding a digi-rack to older HMMWV models to support both BFT installations and SINCGARS. Recall that while this falls on the vehicle side of the SAVE responsibility definitions, the assignment of responsibility for funding this or any related efforts is beyond the scope of this document and must be negotiated separately.

These are MAXIMUM dimensions for C5ISR systems - any size or shape within these dimensions is allowed, including mounting a tray system with multiple smaller radios or devices within a single SAVE envelope. This allows for significant flexibility in C5ISR system

2-12 design while stabilizing platform NRE efforts. Similarly, platforms may provide larger spaces as SAVE envelopes.

Table 2 below summarizes the dimensional requirements. See Figure 1 above and Figure 7 below for clarity on which direction are width, height, and depth. Depth = 0 refers to the front face of the system, typically facing the crew compartment. Height = 0 refers to the base of the system, where it mounts to the vehicle.

Table 2. SAVE Dimensions

Dimension Location Notes width (W) 15.9 inches exactly fits SINCGARS mounting base depth (D) 16.1 inches fits SINCGARS VRC91 height (H) 9.3 inches fits SINCGARS VRC91 (MP PRD uses 9.3” instead of 9.1”) vibration margin 1 inch sides & top

2 inches front & back

Vehicles should provide margin space around the SAVE envelope to allow for vibration / sway, installation, and cable runs. Where not practical, platform PMs shall provide appropriate vibration margin for their vehicles.

Connection Orientation Straight or Right Angle

To facilitate flexible cable attachments maintaining appropriate bend radius while avoiding cable extension into crew compartments, Vehicle PMs shall use 90° connectors at the ends of vehicle provided cables. C5ISR PMs shall design system connection point locations and overall dimensions such that these mating connectors also fit within the SAVE envelope. Where C5ISR PMs provide cable adapters to non-standard connection types, these will also be provided with options for 90° bend attachment.

RF Cable Locations Anywhere in front (D=0)

All C5ISR systems integrated to date have RF connections in the front. Vehicles will provide sufficient cable lengths for RF cable to reach the front of any SAVE location within the vehicle.

Power Cable Locations Anywhere in back panel (D=16.1)

Power cables attach in the rear, and provide pass-through capability to enable powering other devices, as is done by the SINCGARS 6352 baseplate.

Headset Cable Locations Front & Back (D=0, 16.1)

Front connections are easily accessible during missions to allow attachment/removal of handsets, headsets, etc.

Rear connections integrate with vehicle intercom systems.

Data Cable Locations Anywhere in front panel (D=0)

Must be accessible when C5ISR system is integrated into the vehicle.

Bolt Locations (H=0) Matching MT-6352 SINCGARS vehicular mounting base, see section 3.5, figure 7.

Ground Braid As required to permit tray to be tied to vehicle structure

Vehicle racks must provide a proper ground path to the vehicle chassis. Where the vehicle tray may not provide the same or better ground to the vehicle structure, a low resistance ground braid of 10 milli Ohms max is to be provided. See MIL-HDBK-419A on grounds and bonds.

Cable management is a key issue in C5ISR system integration. Cables that route too far from the edge of a system can cause a hazard to Soldiers moving past the system, could be damaged, used as handholds, etc. Thus there is a requirement that C5ISR systems shall come with 90° adapters to allow platforms to route cables appropriately along the edges of

2-13 the SAVE volume. In some cases, a radio may have handles that can be used to provide cable protection and in others it may be appropriate to provide similar cable protection on the vehicle side. As this varies significantly across platforms and systems, no single requirement for cable protection at the device interface is specified here.

In the case of a vehicle with multiple adjacent envelopes, the antenna and other cables shall be designed with sufficient lengths to extend to adjacent SAVE locations in the vehicle. This allows for future re-configuration, e.g. if a radio capability is absorbed into a future CMFF system the antenna connection could be shifted to that system without re-wiring the vehicle. This requirement is intended for configurations where SAVE locations are close together, so the amount of cabling required is reasonable, e.g. on Stryker platforms with 6 adjacent SAVE envelopes on the same equipment rack. Vehicles shall also provide mounting / storage locations for excess cable (e.g. holes for zip ties around cable loops, as already exist in Stryker equipment rack legs) to accommodate this. These mounting locations will also facilitate connections between C5ISR devices in different SAVE envelopes using short cables provided by the C5ISR PMs as B-Kit. These mounting locations will also facilitate cable control to prevent hazards as mentioned above. The details of locations of mounting points and the amount of additional cable are left to individual platform PMs to determine, as designs will vary based on vehicle geometry and the required bend radius of the selected cables.

In cases where there are large distances between SAVE envelopes (i.e. other end of the vehicle, external versus internal, hull versus turret, etc.), providing the ability to reach between SAVE envelopes is NOT required. Cable re-routing or addition of longer bridging cables will be done as additional integration work if and when systems require it.

2.2. Weight

C5ISR systems shall not exceed 100 pounds for all items and support structures or equipment to be mounted within a single SAVE envelope. This limit is similar to the VRC-89 legacy SINCGARS radios (92.81 lbs) with a small margin. In addition, the system and its mounting tray and other ancillaries must be able to withstand shock and vibration per section 4 SAVE Environmental below.

Systems should be decomposable during installation to enable single Soldier installation, in compliance with MIL-STD-1472 Rev G and MANPRINT which call for a limit of 44lbs for individual Soldier lift items. (i.e.