The file's text, extracted by GovTribe without its formatting.
Attachment 2 Vendor System Requirements Compliance Using the instructions and matrix below, provide the capability of your system(s) to meet the requirements listed.
Compliance Codes:
· C (Compliant): The system meets the requirement completely off-the-shelf (COTS) with no hardware or software modification.
· M (Modification): The system requires modification to meet the requirement and there is a plan in place to achieve compliance.
· N (Non-Compliant): The system does not meet the requirement and there is not a current plan to achieve compliance.
Justification: Describe how the requirement is met or not met by the system. If the system requires modification and there is a plan in place to achieve compliance, provide additional details.
Supporting Artifacts and Verification: Provide authoritative source material that verifies compliance and the method of verification (e.g. Inspection, Demonstration, Test, Analysis).
Responses may include but are not limited to:
· Pictures
· Training videos
· Architecture views
· Drawings
· Associations or connectivity with other end items/systems
· Test results to support meeting threshold and objective requirements
| Req # |
| Requirement Text |
| Compliance Code |
| Justification |
| Supporting Artifacts and Verification |
| 1 |
| The NGOCS shall not exceed a total system weight ≤ 8 lb (threshold) / ≤ 4 lb (objective) including display unit (if any), compute, hub, power manager, and all cables. |
| 2 |
| The NGOCS Hub shall physically mount to tactical gear utilizing standard Pouch Attachment Ladder System (PALS) / MOLLE webbing grids. |
| 3 |
| The NGOCS Hub shall not protrude more than 1.5 inches from the point at which it is mounted. |
| 4 |
| The NGOCS Cables shall remain fully functional after repeated 180° bends at a maximum bend radius of 1 inch. |
| 5 |
| The NGOCS shall incorporate a positive quick-disconnect (push-pull or breakaway) for every cable-to-hub and cable-to-device interface whose disconnect force is stated in Newtons and is consistent with emergency doffing. |
| 6 |
| The OCS Hub shall have a configuration that provides connection points for at least four (4) peripheral devices in addition to an EUD and power source. |
| 7 |
| The NGOCS Hub shall have a configuration that provides connection points for two (2) peripheral devices in addition to an EUD and power source. |
| 8 |
| The NGOCS Hub shall be capable of simultaneous control of connected devices. |
| 9 |
| The NGOCS Hub peripheral ports shall be capable of receiving power from any port. |
| 10 |
| The NGOCS shall be capable of receiving power from different power sources / battery types. |
| 11 |
| The NGOCS system shall have a holdup (UPS) battery/power source for swapping power sources. |
| 12 |
| The NGOCS Hub shall incorporate an onboard or attachable compute module capable of hosting and executing user-defined logic, scripts, or compiled code locally. |
| 13 |
| The NGOCS Hub onboard or attachable compute module shall execute localized processing tasks independently of external network connectivity or cloud backhaul. |
| 14 |
| The NGOCS Peripheral interfaces shall use open, published standards (USB 2.0 or higher and/or applicable NATO STANAGs). Proprietary pinouts are non-compliant. |
| 15 |
| The NGOCS software shall accept connections to hardware with an Open (Nonproprietary) API for additional hardware integration. |
| 16 |
| The NGOCS software shall provide a well-documented Open API for third-party integration, supporting data exchange, control, and extension of system capabilities. |
| 17 |
| The NGOCS software API endpoints shall be authenticated, authorized, and encrypted. |
| 18 |
| The NGOCS software shall support versioned APIs and granular permissions. |
| 19 |
| The NGOCS hub shall process classified data utilizing volatile memory only, ensuring that all classified data is completely sanitized upon loss of power. |
| 20 |
| The NGOCS shall route bidirectional IP and serial data between the EUD and the following Government Furnished Equipment (GFE) radios: PRC-163, PRC-117G, PRC-167, KOR-24A (STT), PRC-160, PRC-161, PRC-152A,VDL (TNR2E or Harris Mission Module), GPS, LRF(s), M-Code Device(s) (USB-C Connectors). |
| 21 |
| The NGOCS EUD Cable shall physically interface with tactical EUD cases without modification to the case, cable, or the EUD (e.g. Kagwerks, Juggernaut). |
| 22 |
| The NGOCS shall be operable at elevations from 100 feet below mean sea level (MSL) to 18,000 feet MSL. |
| 23 |
| The NGOCS shall be capable of non-operational transport at cabin altitudes up to 15,000 feet per MIL-STD-810H Method 500.6 Procedures I-IV. |
| 24 |
| The NGOCS shall operate from -46 C to +55 C in accordance with MIL-STD-810G Methods 501.7, 502.7, and 503.7. |
| 25 |
| The NGOCS shall withstand non-operational shock and vibration per MIL-STD-810H Method 514.8 and 516.8. |
| 26 |
| The NGOCS shall withstand operational shock and vibration per MIL-STD-810G Method 516.6 Simulated shock and vibration from entering combat, rotary wing, and maritime vehicles or transport. |
| 27 |
| The NGOCS System shall meet IP67 (threshold) / IP68 (objective) and the corresponding MIL-STD-810H rain and immersion methods. |
| 28 |
| The NGOCS shall operate when exposed to fine dust with IP6X protection in accordance with MIL-STD-810H. |
| 29 |
| The NGOCS System shall produce no visible light, no audible noise above 20 dB at 1 m, no detectable odor, and no specular surfaces. |
| 30 |
| The NGOCS electrical subsystems and components shall be designed and installed in accordance with NFPA 70 (National Electrical Code). |
| 31 |
| The NGOCS shall comply with the requirements of MIL-STD-461G tests CS101, CS114, CS115, CS116, RE102, and RS103. |
| 32 |
| The NGOCS shall suffer no degradation of performance or loss of functionality when tested to MIL-STD-461G, CS118 (Personnel Borne Electrostatic Discharge). |
| 33 |
| The NGOCS shall comply with DoDI 6055.11 to ensure that electromagnetic radiation emissions do not exceed safe levels for personnel exposure (HERP). |
