A fixed vehicle envelope and a requirement to physically separate security enclaves can move a design decision from the system architecture into the enclosure layout. In that case, the number of chassis is not just a packaging choice. It affects the interfaces, thermal paths, mechanical installation, and configuration records that must work together.
What the Announcement Describes
On November 17, 2026, Pacific Defense announced the RCH9070VP, a seven-slot chassis positioned as a lower size, weight, power, and cost alternative to the company’s nine-slot CMFF chassis. The supplier says the compact design allows two chassis to fit side by side within the Army’s Standardized A-Kit / Vehicle Envelope (SAVE), enabling physical separation of red/black security enclaves at the chassis level. The announced configuration includes four dedicated RF mission payload slots, backplane connectivity up to 100 Gb/s to each RF payload slot, and up to 16 RF analog interfaces. The release also describes tray-mounted ground vehicle installations, conduction-cooled configurations for high-altitude applications, ruggedized construction, and integrated chassis management. (Pacific Defense announcement{target="_blank" rel="noopener"})
Those are product-positioning statements from the supplier. They are not, by themselves, evidence of a certification or Army approval.
The larger engineering question is what happens when the enclosure count increases while the mounting envelope stays fixed.
The Envelope Is the Constant; the Chassis Count Is the Variable
The SAVE envelope is commonly summarized as 9.3 inches high, 15.9 inches wide, and 16.1 inches deep. Those dimensions and the summary of SAVE’s interface scope are reported by LCR Embedded Systems, rather than quoted here as a direct statement from the Army’s standard. (LCR Embedded Systems’ SAVE summary{target="_blank" rel="noopener"})
Within a fixed envelope, the design can use one enclosure or divide the equipment between two. With two enclosures, each receives only a portion of the available volume, but each still needs its own backplane, power entry, card cage, panels, connectors, mounting-tray interface, and management path. The pair also has to be installed, aligned, and removed as a coordinated assembly.
The Army describes CMFF as a common chassis for CMOSS-compliant cards, with power and networking already provided, to support capabilities such as positioning, navigation, and timing; electronic warfare protection; and radio waveforms. The Army identifies the common-chassis approach as a way to reduce platform size, weight, and power. (U.S. Army CMFF program announcement{target="_blank" rel="noopener"}) Splitting that architecture may establish a physical boundary between equipment groups, but it also means the vehicle integrator now has two sets of enclosure infrastructure to package and control.
The Enclosure Boundary as a Security Boundary
A chassis-level separation is a mechanical and electrical design claim. Its effectiveness depends on the detailed boundary, not on the presence of two boxes alone. The design review should identify potential paths between enclosures, including shared conductors, backplanes, chassis-management paths, and mounting hardware.
That review should also cover cover gaskets, bonding and grounding strategy, feedthroughs, filtering where signals must cross, cable routing between enclosures, and clear labeling. A shared power source still requires a defined grounding and filtering approach. Any connection that crosses the boundary should be treated as an intentional interface, with its function and implementation documented.
The program’s security authority, not the chassis supplier, defines the acceptance criteria for red/black separation. The enclosure design must be verifiable against those criteria. The Army’s xTech CMFF Integration Fest announcement also illustrates the controlled nature of technical interface information: it required evidence of ITAR compliance, an NDA, and a compliance certification to receive CMFF technical documentation. (U.S. Army xTech CMFF Integration Fest announcement{target="_blank" rel="noopener})
Thermal Budget: Same Heat, Less Surface per Enclosure
If the mission load and total dissipated power remain the same, dividing the system into two chassis does not remove that heat. It changes where the heat is generated, the surface available to reject it in each enclosure, and the airflow or conduction path available to each group of cards. Permissible skin temperature and interface requirements must also be considered for the actual installation.
The design should account for airflow and pressure drop in each enclosure, as well as the effects of installing two units side by side. Adjacent chassis can influence inlet-air availability and create recirculation paths, depending on the vehicle installation. A tray-mounted ground vehicle configuration and a conduction-cooled high-altitude configuration have different thermal interfaces and should not be treated as interchangeable layouts.
The Army has identified heat dissipation in tactically relevant vehicle environments, vehicle shock and vibration, and vehicle SWaP-C constraints as anticipated challenges for CMOSS participants. (U.S. Army xTech CMFF Integration Fest announcement{target="_blank" rel="noopener}) For a split architecture, thermal characterization should therefore address the pair in its intended envelope and installation, not only each chassis tested separately.
Backplane Topology After the Split
The announced seven-slot configuration’s four RF payload slots, connectivity up to 100 Gb/s per RF payload slot, and up to 16 RF analog interfaces make the partition a slot-profile decision as well as a packaging decision. Engineers must determine which slots, profiles, fabrics, and control-plane functions belong in each enclosure, and which links need to cross between them.
OpenVPX defines slot, backplane, module, and standard development chassis profiles. The current VITA listing identifies ANSI/VITA 65.0-2025 and ANSI/VITA 65.1-2025 as ANSI/VITA Approved. (VITA standards list{target="_blank" rel="noopener}) A split system consequently has two backplane profiles to define and control. Any inter-enclosure link becomes a cable interface with its own signal-integrity budget, routing constraints, and documented endpoints. System management also needs an explicit allocation: ANSI/VITA 46.11-2022 defines a management framework spanning field-replaceable-unit, chassis, and system levels. (VITA standards list{target="_blank" rel="noopener})

Mechanical Integration in a Vehicle
Tray mounting, retention, mass distribution, and service access must be resolved for the two-enclosure assembly. Two smaller units may be easier to handle individually, yet harder to align as a pair once both are installed. Vehicle shock and vibration requirements apply to the installed configuration, including the tray interfaces and any hardware that couples the enclosures.
Panel layout is another integration constraint. RF interfaces may concentrate on a front or rear panel, where connector placement, panel flatness, and connector-to-panel tolerances affect the fit and alignment of the interface. Those requirements should be controlled in the panel design and verified in the assembled configuration, rather than left to late-stage fit adjustment.
Program Execution: Two of Everything, One Configuration
The two enclosures should be managed as a coupled configuration. That means linking the relevant chassis and backplane revisions, panel drawings, build records, and interface definitions. The exact record structure depends on the program, but the relationship between the two halves must remain clear through production and changes.
The program should also define its spares philosophy and acceptance-test scope. Some tests may be performed on each enclosure; others need to verify the paired installation and cross-enclosure interfaces. If one half is revised, the team must determine whether the other half, cable set, thermal characterization, or pair-level acceptance evidence is affected. The control question is not only whether each enclosure is buildable, but whether the documented pair remains the approved configuration.
What Engineers and Program Teams Should Consider
- Define the mounting envelope and the security boundary as separate requirements.
- Allocate slot profiles and system functions to each enclosure before selecting hardware.
- Treat every inter-enclosure link as a designed interface with its own signal-integrity and routing budget.
- Characterize thermal performance of the pair in the intended envelope and installation.
- Define grounding, bonding, and filtering across the boundary, including shared power arrangements.
- Manage the two enclosures as one configuration item with linked drawings, revisions, and build records.
- Plan service access, replacement, testing, and spares by enclosure and by pair.
How Vector Supports Enclosure and System Integration
Vector manufactures 19-inch rackmount chassis and system enclosures to customer configuration, precision-machined front and rear panels, card guides, and backplanes across VME, VME64x, CompactPCI, and OpenVPX families. The company also makes VECTORBORD® extender boards for bring-up and test access.
For programs requiring more than individual hardware, Vector provides box build and system assembly to customer specifications, with configuration control and traceability. Its manufacturing experience includes legacy refresh work. Vector manufactures in the United States and has more than 70 years of manufacturing experience. These capabilities do not constitute a claim of CMFF or SAVE compliance, security-enclave certification, environmental qualification, or Army approval.
Relevant product information: Chassis and system enclosures{target="_blank" rel="noopener"} and Backplanes{target="_blank" rel="noopener"}.
When the envelope is fixed but the security boundary moves inside it, the chassis count becomes an architectural variable. The design decision is complete only when the two enclosures, their crossing interfaces, and their shared configuration are treated as one verifiable system.