Nett Warrior ECD Capabilities and Validation Mapping Matrix_012726 V4.xlsx
XLSX spreadsheet 25 KB Posted
- Attached to
- Nett Warrior Edge Compute Device RFI
- Solicitation number
- Not on record
About this file
This file is a capabilities and validation mapping matrix for the Nett Warrior End User Device (EUD) system that establishes technical requirements and performance thresholds. The document outlines the ECD Full System Requirements category, which includes a weight threshold specification requiring the total system weight with EUD to be less than 64 ounces. This requirement is categorized with both threshold and objective performance levels, indicating minimum acceptable performance and desired capability targets respectively, with an associated weighting factor for evaluation purposes.
The matrix serves as a technical specification tool for the Nett Warrior RFI solicitation issued by the Department of the Army Materiel Command Army Contracting Command Aberdeen Proving Ground. It is designed to guide industry responses and evaluate proposed solutions against established performance criteria. The weight requirement directly supports the program's objective to reduce the overall size, weight, and power (SWaP) burden on dismounted leaders by consolidating multiple separate components—chest mount, power hub, and tactical radio—into a single integrated system powered by the existing Conformable Wearable Battery.
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Requirements
| Category | ID | Requirement | Threshold | Objective |
| 1- ECD Full System Requirements | ||||
| Weight | 1.1 | The total weight of the system with EUD shall be less than 64oz threshold | <64oz | <48oz |
| Size | 1.2 | The system shall fit within a 6” x 4” x 4” volume. | T=R | |
| Power | 1.3 | The system shall be capable of receiving power and data from CWB and passing it to the EUD in Case. | ||
| Ergonomics | 1.4 | The system shall allow for operation by both left-handed and right-handed users. Placement of system modules, cables and connectors shall not impede the soldier's ability to move, perform mission tasks and individual movement techniques. | T=R | |
| Ruggedization | 1.5 | The sytem shall be operable during and after subjection to a range of environmental factors defined in MIL-STD-810H including but not limited to Rain, Dust, Sand, Mud, Immersion (3 ft 30 min), Salt Fog, High/Low Temp, Shock, Vibration, Explosive Atmosphere, etc. | T=R | |
| Water Resistance | 1.6 | The system shall be water-resistant (IP65). | T=R | Goal: Submersible to 1m for 30 mins - IP67. |
| EMI | 1.7 | The system shall not noticeably interfere with RF signals; MANET, Bluetooth, Wi-Fi, Cellular or GPS (MIL-STD 461, MIL-STD 464 (i.e. DESENS etc.)). | T=R | |
| Electrical protection | 1.8 | The system shall have protection of ESD (electro-static discharge) of all mechanical ports and circuitry. | T=R | |
| 1.9 | The system shall have over voltage protection (OVP) of all input/output ports. | T=R | ||
| 1.10 | The system shall have over current protection (OCP) for all input power sources. | T=R | ||
| Standards Compliance | 1.11 | The system is designed in accordance with a Modular Open Systems Approach (MOSA) as required by Title 10 U.S.C. § 4401 for MDAPs. | T=R | |
| Thermal | 1.12 | Electronics Package's housing shall comply with thermal contact limits defined in MIL-STD-1472G section 5.7.6.9 | <60 C (momentary contact) | <49 C (prolonged contact or handling) |
| Additional Capabilities | 1.13 | The system shall have four momentary USB buttons integrated to interact with the ARA SW application and provide functionality to ENVG-B or similarly operated components. | T=R | |
| 2- S23 Case Requirements | ||||
| Compatibility | 2.1 | The case shall be geometrically and electronically compatible with the Samsung Galaxy S23 Tactical Edition (TE) EUD. | T=R | |
| EUD Protection | 2.2 | The case shall protect the EUD from shocks, scratches, and debris. | T=R | |
| Functionality | 2.4 | Case shall allow for clear camera pictures both with and without flash. | T=R | |
| 2.6 | EUD case shall be attachable / detachable from MOLLE Mount via quick connect feature. | T=R | ||
| 2.7 | EUD in case shall be capable of being fast charged (5-25+ W) from USB PD external power supplies. | T=R | ||
| 3- Mount Requirements | ||||
| Functionality & Compatibility | 3.1 | The mount shall be MOLLE vest Mountable; to be primarily mounted on the chest. | T=R | |
| 3.2 | The mount shall interface with the EUD Case which can be easily “stored” and secured in place on the chest when not in use | T=R | ||
| 4- Electronics Package Requirements | ||||
| Power Management | 4.1 | Electronics Package shall contain a power on/off button | T=R | |
| 4.2 | Electronics Package shall externally indicate it's power on or off status | T=R | ||
| MANET | 4.3 | Electronics Package shall integrate a MANET Tactical Radio capable of transmitting and receiving voice and data in accordance with PdM TCS radio requirements/specifications | MANET waveforms shall have a single hop (point-to-point unobstructed without relaying) range in open terrain no less than 3km at a 90% Call Completion Rate (CCR) for voice and an 85% Message Completion Rate (MCR) for data | MANET waveforms shall have a single hop (point-to-point without relaying) range in open terrain no less than 5km. (T for SINCGARS) at a 90% Call Completion Rate (CCR) for voice and an 85% Message Completion Rate (MCR) for data |
| 4.4 | System shall support multiple MANET waveforms (O) | SDR or physical swapability at either user or warehouse level | ||
| Transport | 4.5 | Electronics Package shall integrate the ability to transport voice and data over 5G commercial and private networks | T=R | Simultaneous to MANET transceiving |
| 4.6 | Electronics Package shall integrate the ability to transport voice and data over Iridium Satcom networks | T=R | Simultaneous to MANET transceiving |
Simulataneous to 5G transceiving
| 4.7 | Electronics Package shall house the Alereon ISW UWB combat board 256 bit encryption | T=R | ||
| 4.8 | Electronics Package shall contain a wifi module (both 2.4GHz and 5GHz Wi-Fi bands; other legacy standards (802.11b/g/n/ac) must also be supported) to allow downstream devices to connect to it | T=R | ||
| 4.9 | Electronics Package shall supply Bluetooth 5.0, Bluetooth Low Energy, and Bluetooth 2.1+EDR (O) | O=R | ||
| PNT | 4.10 | System shall support advanced APNT (O) | O=R | |
| Compute | 4.11 | Electronics Package shall contain an Edge Compute Device (ECD) capable of performing tasks such as video compression, target detection, and housing large language models. | 8 Core processor, 1 TB SSD, 16GB RAM or equivalent |
| Interfaces | 4.12 | Electronics Package shall contain 2 downstream NW PAN receptables (T) 3 receptacles(O) for peripheral devices to connect to that are capable of providing CWB voltage to any device plugged in. The 5V usb pin must support at least 2A on each downstream port | 2 downstream NW PAN receptables @ 5V 2A | 3 downstream NW PAN receptables @ 5V 2A |
| 4.13 | Electronics Package shall contain an ODU 7 pin port to connect to PTT/headsets (T). | T=R | And an ODU 12 pin port to connect to external systems (O) | |
| 4.14 | Electronics Package shall contain a downstream 3.x USB-C port | downstream only | USB-CM (militarized) connector |
Supports USB PD Dual Role Port (Downstream/upstream)
| 4.15 | Electronics Package shall contain Radio Frequency (RF) output ports to accommodate all onboard waveforms that require external antennas | T=R | ||
| Additonal Capabilities | 4.16 | Electronics Package shall be capable of bridging voice and data transmitted across all supported onboard and connected/external waveforms such as MANET Tactical Radio waveforms, commercial and private 5G, wifi, bluetooth, and Iridium | T=R | |
| 4.17 | The system shall manage power consumption by prioritizing and enabling or disabling communications and system functions based on mission priority and communications posture (Primary, Alternate, Contingency, and Emergency) to sustain critical capabilities under constrained power conditions. | T=R | ||
| 5- Software Requirements | ||||
| Core OS | 5.1 | The device shall operate a hardened, government-approved OS . | T=R | |
| 5.2 | The OS shall be modular and container-friendly environment to allow mission app isolation. | T=R | ||
| Application Framework | 5.3 | The device shall support third-party mission apps via approved SDK/API interfaces. | T=R | |
| Cybersecurity | 5.4 | The device shall comply with DoD Zero Trust principles. | T=R | |
| 5.5 | The device shall be DoD STIG compliant with all current policies. | T=R | ||
| 5.6 | The device shall support remote policy enforcement and device lockdown, and remote wipe. | T=R | ||
| Provisioning | 5.7 | The device shall support OTA updates via approved Army network pathways. | T=R | |
| 5.8 | The system shall incorporate or integrate with a software configuration application to provide device provisioning, configuration, update, and lifecycle management capabilities (e.g. MDM-WT). | T=R | ||
| Additional Capabilities | 5.9 | The software must provide full management control over all hardware components. | T=R | |
| 5.10 | The system shall support self-selecting, semi-autonomous PACE communications, dynamically evaluating available transport paths (Primary, Alternate, Contingency, Emergency) and selecting the optimal path based on policy, network conditions, and mission priority, without requiring soldier intervention or system reconfiguration (O). | O=R | ||
| 5.11 | The system shall provide a simple and intuitive unified graphical user interface (GUI) running on the S23 EUD that enables the operator to configure, manage, and monitor all integrated ancillary devices and system integrations from a single interface. | T=R |
File details come from the government source that posted it. Updated .