M67854-19-R-2000_Attachment_1_-PSPEC_Compliance_Matrix.xlsx
XLSX spreadsheet 31 KB Posted
- Attached to
- Next Generation Troposcatter Federal contract opportunity
- Solicitation number
- M67854-19-R-2000
- Issued by
- United States Marine Corps
About this file
This document is a performance specification compliance matrix for a Next Generation Troposcatter system solicitation from the United States Marine Corps. The Marine Corps requires a secure Beyond Line of Sight digital data transmission system operating in C-Band from 4.4-5 GHz and X-Band from 7.125-7.75 and 7.125-8.4 GHz, capable of retransmission and drop/insert using single or dual systems. The system must meet throughput, distance, emissions, interface, transportability, monitoring and control, reliability, maintainability, safety and environmental requirements. It must be transportable on vehicles and aircraft, have rapid setup and teardown, and include indicators, alarms and cybersecurity measures. The specification includes over 180 mandatory and objective performance requirements for the Next Generation Troposcatter system to ensure it meets Marine Corps needs.
Attachment 1
View the file
Other files for this federal contract opportunity
Show all 22
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
NGT PSPEC Matrix M67854-19-R-2000 Attachment 1 Performance Specification (PSPEC) Compliance Matrix Template Intent: This matrix is to assist in source selection. If there is a descrepency between this document and the PSPEC, the PSEPC takes precedence.
Instructions: Note the paragraph and page number in the proposal where information can be found related to a PSPEC requirement. It is acceptable if requirements refer to multiple sections. Requirements should be referenced in the technical description AND/OR the technical data.
| PSPEC Paragraph | PSPEC Requirement | Threshold or Objective Requirement | Meet or exceed indicator | |
| Paragraph/Page # within the Technical Proposal | Independent test report Appendix (if provided) | |||
| 3 | Requirements | |||
| 3.1 | General Requirements | |||
| 3.1.1 | The system shall operate in the C-Band frequency range from 4.400 to 5.000 GHz. | T | ||
| 3.1.2 | The system shall operate in the X-Band frequency range from 7.125 to 7.750 GHz. | T | ||
| 3.1.3 | The system shall operate in the X-Band frequency range from 7.125 to 8.4 GHz. (Objective) | O | ||
| 3.1.4 | The system Shall be capable of retransmission operations using two systems. | T | ||
| 3.1.5 | The system shall be capable of retransmission operations using a single system. (Objective). | O | ||
| 3.1.6 | The system shall have a drop and insert capability using two systems. (See Note 1 in Section 6 regarding drop and insert.) | T | ||
| 3.1.7 | The system shall have a drop and insert capability using a single system. (Objective). (See Note 1 in Secton 6 regarding drop and insert.). | O | ||
| 3.1.8 | The system shall shall be full duplex. | T | ||
| 3.2 | System Performance | |||
| 3.2.1 | Antenna | |||
| 3.2.1.1 | The system shall be capable of auto alignment. (See Note 4 in Section 6 regarding auto alignment.) | T | ||
| 3.2.1.2 | The system shall enable the local operator to control the antenna by slewing the antenna elevation using powered control. (See Note 4 in Section 6 regarding self-alignment.) | T | ||
| 3.2.1.3 | The system shall enable the local operator to control the antenna by slewing the antenna azimuth using powered control. (See Note 4 in Section 6 regarding self-alignment.) | T | ||
| 3.2.1.4 | The system shall enable the operator to set the antenna azimuth pointing manually without the aid of powered drive mechanisms. (See Note 5 in Section 6 regarding Manual Pointing.) | T | ||
| 3.2.1.5 | The system shall enable the operator to set the antenna elevation pointing manually without the aid of powered drive mechanisms. (See Note 5 in Section 6 regarding Manual Pointing.) | T | ||
| 3.2.1.6 | The antenna shall be capable of successfully performing the auto alignment process when manual alignment of the antenna is within +/- 5 degrees azimuth and +/- 2 degrees elevation of the optimal position. (See Note 4 in Section 6 regarding self-alignment.) | T | ||
| 3.2.2 | Distance and Throughput Requirements | |||
| 3.2.2.1 | The system with a clear takeoff angle, shall have a minimum throughput of 20 Mbps at a minimum distance of 120 statute miles with a Bit Error Rate (BER) less than or equal to 10E-6 with a link availability of 90%. (See Note 2 in Section 6 regarding Clear Takeoff Angles.) | T | ||
| 3.2.2.2 | The system with a clear takeoff angle, shall have a throughput of 50 Mbps at a minimum distance of 35 statute miles with a BER less than or equal to 10E-6 with a link availability of 90%. (See Note 2 in Section 6 regarding Clear Takeoff Angles.) | T | ||
| 3.2.2.3 | The system with a clear takeoff angle, shall have a range extension ability to provide a throughput of 20 Mbps at a minimum distance of 160 statute miles with a BER less than or equal to10E-6 with a link availability of 90%. (See Note 2 in Section 6 regarding Clear Takeoff Angles.) | T | ||
| 3.2.3 | System Emissions | |||
| 3.2.3.1 | The systems emissions shall adhere to the NTIA Redbook. | T | ||
| 3.2.3.2 | The system waveform(s) shall not exceed the channel size limitations identified in NTIA Redbook Section 4.3.18 figure 1 for C-Band operations. | T | ||
| 3.3 | Interface Definition | |||
| 3.3.1 | Signal Interfaces | |||
| 3.3.1.1 | The system signal interfaces shall use non-proprietary commercially available connectors. | T | ||
| 3.3.1.2 | The system shall provide RJ-45 console port interfaces. | |||
| 3.3.1.3 | The system RJ-45 console port interfaces shall be user accessible using a signal entry panel. | T | ||
| 3.3.1.4 | The system shall provide RS-232 serial-based management interfaces. | |||
| 3.3.1.5 | All system RS-232 serial-based management shall be user accessible using a signal entry panel. | T | ||
| 3.3.1.6 | All system modem management interfaces shall be user accessible using a signal entry panel. | T | ||
| 3.3.1.7 | The system shall provide MFOCA Mixed Mode Expanded Beam connector interfaces with two Single Mode and two Multi-Mode Channels. | T | ||
| 3.3.1.8 | The system MFOCA interfaces shall be user accessible using a signal entry panel. | |||
| 3.3.1.9 | The system Internet Protocol devices shall comply with the mandatory requirements of DoD IPv4 Standard Profiles. | T | ||
| 3.3.1.10 | The system Internet Protocol devices shall comply with the mandatory requirements of DoD IPv6 Standard Profiles. | T | ||
| 3.3.2 | Global Positioning System | |||
| 3.3.2.1 | The system shall not rely on commercial Global Positioning System (GPS) as a primary means of obtaining position, navigation, and timing. | T | ||
| 3.3.2.2 | If position, navigation, and timing is used by the system, the system shall be capable of interfacing with an AN/PSN-13A Defense Advanced GPS Receiver (DAGR) to obtain the needed information. (See Note 6 in Section 6 regarding Position, Navigation, and Timing.) | T | ||
| 3.3.2.3 | The system shall provide a DAGR if position, navigation, and timing is required for deployment and operations. | T | ||
| 3.3.2.4 | The system shall provide a means of obtaining timing data for operations in a GPS or satellite communications denied environment. | T | ||
| 3.3.3 | Power | |||
| 3.3.3.1 | The system shall be capable of operating with a commercial 3-phase power generator. | T | ||
| 3.3.3.2 | The system shall be capable of operating with a military 3-phase power generator. | T | ||
| 3.3.3.3 | The system shall not exceed the power capacity of a 10 KW power generator. | T | ||
| 3.3.3.4 | The system shall provide a 50 ft power cable to interface with Mobile Electric Power Tactical Quiet Generators. | T | ||
| 3.3.4 | Cabling | |||
| 3.3.4.1 | The system shall include all necessary internal interconnecting cables to facilitate operation of the transmission system. | T | ||
| 3.3.4.2 | The system cables shall be shielded in accordance with MIL-STD-188-124B Change Notice 3 Section 5.1.1.3.8.4. | T | ||
| 3.3.4.3 | The system waveguides shall be grounded in accordance with MIL-STD-188-124B Change Notice 3 Section 5.1.1.3.8.5. | T | ||
| 3.3.4.4 | The system cables shall be marked with individual cable reference designators. | T | ||
| 3.3.4.5 | The system cables shall be marked with individual cable part number. | T | ||
| 3.3.4.6 | The system cables shall be marked with individual cable manufacturer cage code. | T | ||
| 3.3.4.7 | The system shall comply with the design criteria in MIL-STD-1472G Section 5.4.5.7 for cable labeling. | T | ||
| 3.3.4.8 | The system shall comply with the design criteria in MIL-STD-1472G Section 5.9.14.4 for cable routing. | T | ||
| 3.3.4.9 | The system shall comply with the design criteria in MIL-STD-1472G Section 5.9.14.7 for cable identification. | T | ||
| 3.3.5 | Connectors | |||
| 3.3.5.1 | The system shall comply with the design criteria of MIL-STD-1472G Section 5.9.15.2 regarding uniquely keyed connectors to prevent improper mating. | T | ||
| 3.3.5.2 | The system shall comply with the design criteria of MIL-STD-1472G Section 5.9.15.12 regarding the use of captive covers. | T | ||
| 3.3.6 | Fastener Hardware | |||
| 3.3.6.1 | The system shall use captive fasteners in accordance with MIL-STD-1472G Section 5.9.10.3. | T | ||
| 3.3.6.2 | The system shall use corrosion resistant material. | T | ||
| 3.4 | Setup and Antenna Alignment | |||
| 3.4.1 | The system time for setup and joining the network (including auto alignment) shall be 60 minutes by no more than three men. (See Note 7 Section 6 regarding Setup.) | T | ||
| 3.4.2 | The system time for setup and joining the network (including auto alignment) shall be 30 minutes by no more than three men (Objective). (See Note 7 Section 6 regarding Setup.) | O | ||
| 3.4.3 | The system time for tear-down shall not exceed 60 minutes by no more than three men (See Note 8 Section 6 regarding Tear-Down.) | T | ||
| 3.4.4 | The system time for tear-down shall not exceed 30 minutes by no more than three men (Objective). (See Note 8 Section 6 regarding Tear-Down.) | O | ||
| 3.4.5 | The system shall include all tools required to place the system into an operational state from a transport state. | T | ||
| 3.5 | Transportability and Storage | |||
| 3.5.1 | General Transportability and Storage | |||
| 3.5.1.1 | The system C-Band shall be transportable on highways as secured cargo using a single M1097A1 HMMWV Heavy Variant Cargo Carrier in accordance with MIL-STD-1366E Section 5.1. | T | ||
| 3.5.1.2 | The system X-Band shall be transportable on highways as secured cargo using a single M1097A1 HMMWV Heavy Variant Cargo Carrier in accordance with MIL-STD-1366E Section 5.1. | T | ||
| 3.5.1.3 | The combined system shall be transportable on highways as secured cargo using a single M1097A1 HMMWV Heavy Variant Cargo Carrier in accordance with MIL-STD-1366E Section 5.1 (Objective). | O | ||
| 3.5.1.4 | The system C-Band shall be transportable on highways as secured cargo using a single JLTV Cargo Variant in accordance with MIL-STD-1366E Section 5.1. | T | ||
| 3.5.1.5 | The system X-Band shall be transportable on highways as secured cargo using a single JLTV Cargo Variant in accordance with MIL-STD-1366E Section 5.1. | T | ||
| 3.5.1.6 | The combined system shall be transportable on highways as secured cargo using a single JLTV Cargo Variant in accordance with MIL-STD-1366E Section 5.1 (Objective). | O | ||
| 3.5.1.7 | The system shall be rail transportable as secured cargo in accordance with MIL-STD-1366E Section 5.2. | T | ||
| 3.5.1.8 | The system shall be water transportable as secured cargo in accordance with MIL-STD-1366E Section 5.3. | T | ||
| 3.5.1.9 | The system shall be fixed wing air transportable as secured cargo in accordance with MIL-STD-1366E Section 5.4. | T | ||
| 3.5.1.10 | The system shall be USMC rotary-wing air transportable as internally secured cargo in accordance with MIL-STD-1366E Section 5.6. (See Note 10 in Section 6 regarding USMC rotary and tilt-wing.) | T | ||
| 3.5.1.11 | The system shall be USMC tilt-wing air transportable as internally secured cargo in accordance with MIL-STD-1366E Section 5.6. (See Note 10 in Section 6 regarding USMC rotary and tilt-wing.) | T | ||
| 3.5.1.12 | The system, with the addition of the range extension kit, may exceed the dimensions of a single transport platform. | T | ||
| 3.5.1.13 | The system, with the additional components for cold weather temperature extension, may exceed the dimensions of a single transport platform. | T | ||
| 3.5.2 | Transit Cases | |||
| 3.5.2.1 | The system shall be stored and transported in transit cases. | T | ||
| 3.5.2.2 | Latches and catches which have snap down and release forces shall not be hazardous to handle during operation. | T | ||
| 3.5.2.3 | Transit cases shall be provided with a pressure relief valve to equalize pressure. | T | ||
| 3.5.2.4 | Transit cases shall be constructed so that the covers mount to the sides of the transit case (Objective). | O | ||
| 3.5.2.5 | Transit cases shall be stackable. | T | ||
| 3.5.2.6 | Transit cases shall be constructed so that the covers do not interfere with stacking. | T | ||
| 3.5.2.7 | The interfaces needed for system setup shall be accessible by the user without obstruction during system setup. | T | ||
| 3.5.2.8 | The system indicators needed for system setup shall be visible by the user without obstruction during system setup. | T | ||
| 3.5.2.9 | The transit cases shall provide ready access to all Item Unique Identification (IUID) markings. | T | ||
| 3.5.2.10 | Transit cases shall comply with the design criteria in MIL-STD-1472G Section 5.9.6 for case and cover mounting. | T | ||
| 3.5.2.11 | Transit cases shall comply with the design criteria in MIL-STD-1472G Section 5.9.7 for cases. | T | ||
| 3.5.3 | Weight | |||
| 3.5.3.1 | The system transit cases shall be capable of being lifted by no more than three men, one transit case at a time, in accordance with MIL-STD-1472G. (See Note 11 in Section 6 regarding Weights). | T | ||
| 3.5.3.2 | The system transit cases shall be capable of being lifted by no more than three trained personnel, one transit case at a time, in accordance with MIL-STD-1472G (Objective). (See Note 11 in Section 6 regarding Weights). | O | ||
| 3.6 | Monitoring and Control | |||
| 3.6.1 | General Monitoring and Control | |||
| 3.6.1.1 | The system software shall be compatible with the USMC Windows Secure Host Baseline. | T | ||
| 3.6.1.2 | The system shall provide monitoring ports for all modem transmit paths. | T | ||
| 3.6.1.3 | The system shall provide monitoring ports for all modem receive paths. | T | ||
| 3.6.1.4 | The system transmit and receive modem monitoring ports shall be accessible to the user without obstruction. | T | ||
| 3.6.1.5 | The system software shall be compatible with a Government Furnished Equipment (GFE) USMC Common Hardware Suite (MCHS) general purpose laptop if used. | T | ||
| 3.6.1.6 | The system shall have a Built-in-Test (BIT) capability. | T | ||
| 3.6.1.7 | The system shall continuously display a BER. | T | ||
| 3.6.1.8 | The system shall provide the ability to monitor Receive Signal Level (RSL) status. | T | ||
| 3.6.1.9 | The system shall provide the ability to display RSL status. | T | ||
| 3.6.1.10 | The system shall provide a means for performing loopback testing for troubleshooting the system baseband transmission path. | T | ||
| 3.6.1.11 | The system shall provide a means for performing loopback testing for troubleshooting the system data path. | T | ||
| 3.6.2 | Transmission Security (TRANSEC) | |||
| 3.6.2.1 | The system shall include a TRANSEC capability for the transmission path between terminals carrying all data and signals, including control signals in accordance with FIPS 140-2. | T | ||
| 3.6.2.2 | The TRANSEC device shall be FIPS Publication 197 compliant. | T | ||
| 3.6.2.3 | The TRANSEC device shall be National Information Assurance Partnership (NIAP) certified. | T | ||
| 3.6.3 | Cybersecurity | |||
| 3.6.3.1 | The system shall record account creation in support of audit functions. | T | ||
| 3.6.3.2 | The system shall record account modification in support of audit functions. | T | ||
| 3.6.3.3 | The system shall record account enabling in support of audit functions. | T | ||
| 3.6.3.4 | The system shall record account disabling in support of audit functions. | T | ||
| 3.6.3.5 | The system shall record account removal actions in support of audit functions. | T | ||
| 3.6.3.6 | The system audits shall be viewable by personnel with appropriate privileges. | T | ||
| 3.6.3.7 | In the event that there is a shared account, the system administrator shall have the ability to add individual accounts. | T | ||
| 3.6.3.8 | In the event that there is a shared account, the system administrator shall have the ability to delete individual accounts. | T | ||
| 3.6.3.9 | The system shall allow operator level access to users with operator privileges. | T | ||
| 3.6.3.10 | The system shall allow administrator level access to users with administrator privileges. | T | ||
| 3.6.3.11 | The systems shall not allow for privilege escalations. | T | ||
| 3.6.3.12 | The system shall isolate subjects based on defined roles. (See Note 13 in Section 6 regarding Subjects) | T | ||
| 3.6.3.13 | The system shall isolate objects based on user defined roles. (See Note 14 in Section 6 regarding Objects) | T | ||
| 3.6.3.14 | The system shall allow administrators access to objects. (See Note 14 in Section 6 regarding Objects) | T | ||
| 3.6.3.15 | The system shall prevent operators from executing administrator functions. | T | ||
| 3.6.3.16 | The system shall record the execution of all administrator functions for auditing. | T | ||
| 3.6.3.17 | Before granting access, the system login page shall display a notification message or banner that states users are accessing a U.S. Government information system, in accordance with DoDI 8500.01 Cybersecurity Section 9.1.d. | T | ||
| 3.6.3.18 | Before granting access, the system login page shall display a notification message or banner that states system usage may be monitored, recorded, and subject to audit in accordance with DoDI 8500.01 Cybersecurity, Section 9.1.d. | T | ||
| 3.6.3.19 | Before granting access, the system login page shall display a notification message or banner that states unauthorized use of the information system is prohibited and subject to criminal and civil penalties, in accordance with DoDI 8500.01 Cybersecurity, Section 9.1.d. | T | ||
| 3.6.3.20 | Before granting access, the system login page shall display a notification message or banner that states use of the information system indicates consent to monitoring and recording, in accordance with DoDI 8500.01 Cybersecurity, Section 9.1.d. | T | ||
| 3.6.3.21 | The system login page shall retain the notification message or banner on the screen until users acknowledge the usage conditions. | T | ||
| 3.6.3.22 | The system shall allow a maximum of three concurrent operating sessions. | T | ||
| 3.6.3.23 | The system shall not allow remote wireless access other than the main RF transmission path. | T | ||
| 3.6.3.24 | The system shall generate audit records containing information that establishes what type of event occurred. | T | ||
| 3.6.3.25 | The system shall generate audit records containing information that establishes when the event occurred. | T | ||
| 3.6.3.26 | The system shall generate audit records containing information that establishes where (logical location) the event occurred. | T | ||
| 3.6.3.27 | The system shall generate audit records containing information that establishes the source of the event. | T | ||
| 3.6.3.28 | The system shall generate audit records containing information that establishes the outcome of the event. | T | ||
| 3.6.3.29 | The system shall generate audit records containing information that establishes the identity of any individuals or subjects associated with the event. | T | ||
| 3.6.3.30 | The system shall generate audit records containing each key stroke recording of administrator commands. | T | ||
| 3.6.3.31 | The system log memory shall be a minimum of 10 MB. | T | ||
| 3.6.3.32 | The system log memory shall have enough storage to accommodate six months of data. | T | ||
| 3.6.3.33 | The system log memory shall be non-volatile. | T | ||
| 3.6.3.34 | The system shall notify users when the audit record storage volume reaches 75% of repository maximum audit record storage capacity. | T | ||
| 3.6.3.35 | The system shall notify administrators upon login when the audit record storage volume reaches 75% of repository maximum audit record storage capacity. | T | ||
| 3.6.3.36 | The system shall have the capability of transferring system log data to Compact Disc or Digital Video Disk media. | T | ||
| 3.6.3.37 | The system shall alert system administrators in the event of an audit processing failure. | T | ||
| 3.6.3.38 | The system shall use internal system clocks to generate time stamps for audit records | T | ||
| 3.6.3.39 | The system shall record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). | T | ||
| 3.6.3.40 | If the system contains a GPS, the GPS shall be the authoritative source for time synchronization. | T | ||
| 3.6.3.41 | The system shall protect audit information from unauthorized access. | T | ||
| 3.6.3.42 | The system shall protect audit information from modification. | T | ||
| 3.6.3.43 | The system shall protect audit information from deletion. | T | ||
| 3.6.3.44 | The system shall protect audit tools from unauthorized access. | T | ||
| 3.6.3.45 | The system shall protect audit tools from modification. | T | ||
| 3.6.3.46 | The system shall protect audit tools from deletion. | T | ||
| 3.6.3.47 | The system shall provide audit record generation capability in accordance with applicable Security Technical Implementation Guides (STIGs). | T | ||
| 3.6.3.48 | The system shall allow system administrators to select which auditable events are to be audited by specific components of the system. | T | ||
| 3.6.3.49 | The system shall allow for provision of auditable events to support after-the-fact investigations of security incidents. | T | ||
| 3.6.3.50 | The system shall provide the capability for administrators to change the auditing to be performed on the system. | T | ||
| 3.6.3.51 | The system shall have the ability to record session audits | T | ||
| 3.6.3.52 | The system shall initiate session audits at system start-up. | T | ||
| 3.6.3.53 | The system shall allow administrators to limit privileges for changing software resident within software libraries. | T | ||
| 3.6.3.54 | The system shall have the ability to allow administrators to facilitate configuration changes. | T | ||
| 3.6.3.55 | The system shall have the ability to enable ports. | T | ||
| 3.6.3.56 | The system shall have the ability to disable ports. | T | ||
| 3.6.3.57 | The system shall have the ability to enable protocols. | T | ||
| 3.6.3.58 | The system shall have the ability to disable protocols. | T | ||
| 3.6.3.59 | The system shall have the ability to enable services. | T | ||
| 3.6.3.60 | The system shall have the ability to disable services. | T | ||
| 3.6.3.61 | The system shall allow administrators to "Whitelist" programs. (See Note 15 in Section 6 regarding Whitelist) | T | ||
| 3.6.3.62 | The system shall prohibit operator installation of software. | T | ||
| 3.6.3.63 | The system shall uniquely identify users. | T | ||
| 3.6.3.64 | The system shall uniquely authenticate users. | T | ||
| 3.6.3.65 | The system shall enforce passwords of at least 15 characters long consisting of a minimum of two of characters from each of the following categories: upper-case letters, lower-case letters, numbers, and special characters. | T | ||
| 3.6.3.66 | The system shall enforce at least a 50% difference in characters when a password is changed. | T | ||
| 3.6.3.67 | The system shall store only encrypted representations of passwords. | T | ||
| 3.6.3.68 | The system shall transmit only encrypted representations of passwords. | T | ||
| 3.6.3.69 | The system shall allow the use of a temporary password for system logons with an immediate change to a permanent password. | T | ||
| 3.6.3.70 | The system shall have the ability to obscure feedback of authentication information during the authentication process. | T | ||
| 3.6.3.71 | The system shall have the ability to implement privileged access authorization to administrators in order to perform vulnerability assessment activities. (See Note 16 in Section 6 regarding Vulnerability Assessment) | T | ||
| 3.6.3.72 | The system shall have the ability to implement privileged access authorization to administrators in order to perform selected penetration testing activities. (See Note 17 in Section 6 regarding Penetration Testing.) | T | ||
| 3.6.3.73 | The system shall have the ability to separate operator functionality (including user interface services) from system administrator functionality regarding application partitioning. | T | ||
| 3.6.3.74 | The system shall prevent access to security functions. | T | ||
| 3.6.3.75 | The system shall implement cryptographic mechanisms to conceal or randomize communication patterns. | T | ||
| 3.6.3.76 | The system shall protect the confidentiality of all data at rest. (See Note 18 in Section 6 regarding Data at Rest) | T | ||
| 3.6.3.77 | The system shall generate error messages for auditable events that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. | T | ||
| 3.6.3.78 | The system shall reveal error messages for auditable events only to system administrators. | T | ||
| 3.6.3.79 | The system shall prevent any reuse of unique individual identifiers. | T | ||
| 3.6.3.80 | The system shall maintain a separate execution domain for each executing process. | T | ||
| 3.6.3.81 | The system shall be configured for credentialed vulnerability scans using DoD approved vulnerability scanning tools. | T | ||
| 3.6.3.82 | The system Monitor and Control (M&C) device shall employ malicious code protection mechanisms at M&C device entry and exit points to detect and eradicate malicious code. | T | ||
| 3.6.3.83 | The system shall perform input validation. | T | ||
| 3.7 | Indicators and Alarms | |||
| 3.7.1 | Indicators | |||
| 3.7.1.1 | The system shall be capable of identifying errors at the Line Replaceable Unit (LRU) level and providing error notification to the user. | T | ||
| 3.7.1.2 | The system shall provide visual indicators when equipment is energized. | T | ||
| 3.7.1.3 | The system shall notify the user of faults using a visual indicator. | T | ||
| 3.7.1.4 | The system shall indicate critical malfunctions in accordance with MIL-STD-1472G Section 5.9.18.1.3. | T | ||
| 3.7.1.5 | The system visual fault indicators shall reset after a fault is repaired. | T | ||
| 3.7.2 | Alarms | |||
| 3.7.2.1 | The system shall notify the user of faults using an audible alarm. | T | ||
| 3.7.2.2 | The system audible alarms shall comply with the design criteria in MIL-STD-1472G Section 5.3.1.3.4a regarding compatibility with acoustical environment. | T | ||
| 3.7.2.3 | The system audible alarms shall comply with the design criteria in MIL-STD-1472G Section 5.3.1.4.3f regarding differentiation between alarms and routine signals. | T | ||
| 3.7.2.4 | The system audible alarms shall be capable of being muted by the user. | T | ||
| 3.8 | Reliability and Maintainability | |||
| 3.8.1 | Reliability | |||
| 3.8.1.1 | The system exclusive of GFE, Mean Time Between Operational Mission Failure (MTBOMF) shall be a minimum of 1000 hours. (See Note 19 in Section 6 regarding MTBOMF.) | T | ||
| 3.8.2 | Maintainability | |||
| 3.8.2.1 | The system shall meet an operator level Mean Time to Repair (MTTR) of less than 15 minutes. (See Note 20 in Section 6 regarding MTTR.) | T | ||
| 3.8.2.2 | The system shall comply with the design criteria in MIL-STD-1472G Section 5.9.1.10 regarding operational environment equipment handling. | T | ||
| 3.8.2.3 | The system shall comply with the design criteria in MIL-STD-1472G Section 5.9.1.13 regarding positioning of safety features supporting system maintenance. | T | ||
| 3.8.2.4 | The system shall comply with the design criteria in MIL-STD-1472G Section 5.9.2.1.4 regarding frequent access. | T | ||
| 3.8.2.5 | The system shall comply with the design criteria in MIL-STD-1472G Section 5.7.9.1.16 regarding electrical conductor insulation where maintenance activities occur. | T | ||
| 3.8.2.6 | The system special tools, if any, shall be provided by the vendor. (See Note 21 in Section 6 regarding Special Tools.) | T | ||
| 3.9 | Safety | |||
| 3.9.1 | General Safety | |||
| 3.9.1.1 | The system shall incorporate safety devices to protect personnel from serious injury or death during setup. | T | ||
| 3.9.1.2 | The system shall incorporate safety devices to protect personnel from serious injury or death during tear-down. | T | ||
| 3.9.1.3 | The system shall incorporate safety devices to protect personnel from serious injury or death during operation. | T | ||
| 3.9.1.4 | The system shall incorporate safety devices to protect personnel from serious injury or death during maintenance. | T | ||
| 3.9.1.5 | The system shall incorporate safety devices to protect personnel from serious injury or death during transport. | T | ||
| 3.9.1.6 | The system shall incorporate safety devices to protect personnel from serious injury or death during disposal. | T | ||
| 3.9.1.7 | The system shall not be constructed of any environmentally hazardous materials. | T | ||
| 3.9.1.8 | The system shall not produce any environmentally hazardous materials as a by-product. | T | ||
| 3.9.1.9 | The system shall have any hazards to personnel clearly marked and labeled. | T | ||
| 3.9.1.10 | The system safety markings shall comply with MIL-STD-1472G Section 5.9.6.6. | T | ||
| 3.9.1.11 | The system safety labels shall comply with MIL-STD-1472G Section 5.9.6.6. | T | ||
| 3.9.1.12 | The system shall be free of ozone depleting substances per applicable Federal regulations in effect on the date of manufacture. | T | ||
| 3.9.1.13 | The system shall contain warning labels on each piece of equipment weighing greater than 31 pounds listing the exact weight and the recommended number of personnel required for safe lifting in accordance with MIL-STD-1472G Section 5.8.6.3.12. | T | ||
| 3.9.1.14 | The system shall not produce a sound pressure level equal to or exceeding an 8-hour time weighted average of 85 dBA at a distance of at least one meter away from the system in accordance with MIL-STD 1472G Section 5.3.1.8.2B. | T | ||
| 3.9.1.15 | The system shall include warning labels where noise levels are exceeded in accordance with MIL-STD-1472 Section 5.5.4.4.4. | T | ||
| 3.9.1.16 | The system shall include the physical features (e.g., supports, guides, size or shape differences, fastener locations and alignment pins) necessary to prevent improper assembling. | T | ||
| 3.9.1.17 | The system shall include the physical features (e.g., supports, guides, size or shape differences, fastener locations and alignment pins) necessary to prevent improper installing. | T | ||
| 3.9.1.18 | The system shall include the physical features (e.g., supports, guides, size or shape differences, fastener locations and alignment pins) necessary to prevent improper connecting. | T | ||
| 3.9.1.19 | The system shall include the physical features (e.g., supports, guides, size or shape differences, fastener locations and alignment pins) necessary to prevent improper operating. | T | ||
| 3.9.2 | Electrical Safety | |||
| 3.9.2.1 | Equipment sensitive to electrostatic discharge shall be marked in accordance with MIL-STD-1686C Section 5.7. | |||
| 3.9.2.2 | The system shall not expose the operator to contact with voltages exceeding 30V in accordance with MIL-STD 1472G Section 5.7.9.1.1. | T | ||
| 3.9.2.3 | The system shall not expose the maintenance personnel to contact with voltages exceeding 30V in accordance with MIL-STD 1472G Section 5.7.9.1.1. | T | ||
| 3.9.2.4 | The system shall have terminal guarding to prevent inadvertent short circuiting for any batteries with a rating greater than 25Ampere-Hours in accordance with MIL-STD 1472G Section 5.7.9.1.15. | T | ||
| 3.9.2.5 | The system shall provide a means for maintainers to discharge capacitor charge to less than 30V prior to maintainer access or exposure in accordance with MIL-STD 1472G Section 5.3.1.8.2C. | T | ||
| 3.9.2.6 | The system shall completely enclose circuits with voltages exceeding 500V in accordance with MIL-STD 1472G Section 5.7.9.1.6. | T | ||
| 3.9.2.7 | The system shall provide an interlock for circuits with voltages exceeding 500V in accordance with MIL-STD 1472G Section 5.7.9.1.7a(3)(c). | T | ||
| 3.9.2.8 | The system shall completely enclose components with voltages exceeding 500V in accordance with MIL-STD 1472G Section 5.7.9.1.7(3)(c). | T | ||
| 3.9.2.9 | The system shall provide an interlock for components with voltages exceeding 500V in accordance with MIL-STD 1472G Section 5.7.9.1.7(3)(c). | T | ||
| 3.9.2.10 | System equipment shall be protected from damage when connected to incorrect input power/voltage levels or polarity in compliance with UL 60950-1. | T | ||
| 3.9.2.11 | Alternating Current (AC) supply conductors shall be color-coded IAW MIL-STD-686C Section 5.1.1.2.2. | T | ||
| 3.9.2.12 | The system shall comply with the design criteria IAW MIL-STD-1472G Section 5.7.9.1.6b regarding personnel electric shock prevention danger markings. | T | ||
| 3.9.2.13 | The system shall have protective measures that prevent accidental activation of power switches in accordance with MIL-STD 1472G Section 5.7.9.1.7B. | T | ||
| 3.9.2.14 | The system shall have protective measures that prevent accidental deactivation of power switches in accordance with MIL-STD 1472G Section 5.7.9.1.7B. | T | ||
| 3.9.2.15 | The system shall comply with the design criteria in MIL-STD-1472G Section 5.7.9.1.6c regarding personnel electric shock prevention danger signs. | T | ||
| 3.9.3 | Mechanical Safety | |||
| 3.9.3.1 | The system shall be made to prevent accidental pulling out of drawers or rack mounted equipment. | T | ||
| 3.9.3.2 | The system shall not expose the maintainer to stored energy shock in accordance with MIL-STD 1472G Section 5.7.7.9. | T | ||
| 3.9.3.3 | The system shall not expose the operator to stored energy shock in accordance with MIL-STD 1472G Section 5.9.20.1. | T | ||
| 3.9.4 | Other Safety | |||
| 3.9.4.1 | RF radiation hazards shall be marked using the signal word WARNING in accordance with MIL-STD 1472G Section 5.7.2.5.2. | T | ||
| 3.9.4.2 | RF radiation labels shall warn personnel of danger zones in accordance with MIL-STD 1472G Section 5.7.2.5.1. | T | ||
| 3.9.4.3 | All equipment capable of emitting RF radiation shall be limited to values listed in MIL-STD 1472G Section 5.7.7.2 where exposure by personnel is required to operate the system. | T | ||
| 3.9.4.4 | Covers which require removal during maintenance subjecting the maintainer to a radiation overexposure risk shall be interlocked (non-bypassable) in accordance with MIL-STD 1472G Section 5.7.9.1.7a(3)(c). | T | ||
| 3.9.4.5 | Fiber optic interfaces shall meet Class 1 or Class 1M laser accessible emission limits IAW ANSI Z136.1 during system operations. | T | ||
| 3.9.4.6 | Where power levels must exceed Class 1 levels during system operation with all fiber optic cables connected, Automatic Power Reduction (APR) shall be used to reduce laser radiation levels to Class 1 limits when fiber optic cables are disconnected. | T | ||
| 3.9.4.7 | Warning labels shall be applied to the equipment in accordance with ANSI Z136.1 where Class 1 levels are exceeded. | T | ||
| 3.10 | Electromagnetic Environmental Effects | |||
| 3.10.1 | General Electromagnetic Environmental Effects (E3) | |||
| 3.10.1.1 | The system shall be capable of normal operation following a near strike lightning environment as specified in MIL-STD-464C Section 5.5 Table 8. | T | ||
| 3.10.2 | Electromagnetic Radiation | |||
| 3.10.2.1 | The system shall protect against hazards of electromagnetic radiation to personnel by indicating safe stand-off distances through appropriate labeling in accordance with DoDI 6055.11 and IEEE Standard C95.3-2002. | T | ||
| 3.10.2.2 | The system shall protect against hazards of electromagnetic radiation to fuel by indicating safe stand-off distances through appropriate labeling in accordance with MIL-STD-464C Section 5.9.2. | T | ||
| 3.10.2.3 | The system shall protect against hazards of electromagnetic radiation to ordnance by indicating safe stand-off distances through appropriate labeling in accordance with MIL-STD-464C Section 5.9.3. | T | ||
| 3.10.3 | Electromagnetic Pulse (EMP) | |||
| 3.10.3.1 | The system shall be designed to survive the effects of an EMP as per MIL-STD-188-125-2. | T | ||
| 3.10.4 | Electromagnetic Interference (EMI) | |||
| 3.10.4.1 | The system shall meet the requirements of MIL-STD-461G CE-102 from 10 kHz to 10MHz. | T | ||
| 3.10.4.2 | The system shall meet the requirements of MIL-STD-461G CE-106 from 10 kHz to 40 GHz. | T | ||
| 3.10.4.3 | The system shall meet the requirements of MIL-STD-461G CS-101 from 30 Hz to 150 kHz. | T | ||
| 3.10.4.4 | The system shall meet the requirements of MIL-STD-461G CS-103 from 15 kHz to 10 GHz. | T | ||
| 3.10.4.5 | The system shall meet the requirements of MIL-STD-461G CS-104 from 30Hz to 20 GHz. | T | ||
| 3.10.4.6 | The system shall meet the requirements of MIL-STD-461G CS-105 from 30Hz to 20 GHz. | T | ||
| 3.10.4.7 | The system shall meet the requirements of MIL-STD-461G CS-114 from 10 kHz to 200 MHz. | T | ||
| 3.10.4.8 | The system shall meet the requirements of MIL-STD-461G CS-115. | T | ||
| 3.10.4.9 | The system shall meet the requirements of MIL-STD-461G CS-116 from 10 kHz to 100 MHz. | T | ||
| 3.10.4.10 | The system shall meet the requirements of MIL-STD-461G RE-102 from 2 MHz to 18 GHz. | T | ||
| 3.10.4.11 | The system shall meet the requirements of MIL-STD-461G RS-103 from 2 MHz to 40 GHz. | T | ||
| 3.11 | Grounding Bonding and Shielding | |||
| 3.11.1 | Grounding and Bonding shall be in accordance with MIL-STD-188-124B Change Notice 3 and MIL-STD-464C. | T | ||
| 3.12 | Environmental Compliancy | |||
| 3.12.1 | The system shall operate at a maximum temperature of 50 degrees C. | T | ||
| 3.12.2 | The system shall operate at a minimum temperature of -10 degrees C. | T | ||
| 3.12.3 | The system shall have the ability to add components that allow operation at a temperature of -40 degrees C. | T | ||
| 3.12.4 | The system shall be capable of storage at 95% humidity (non-condensing) ambient temperature 105F without system damage. | T | ||
| 3.12.5 | The system shall be capable of storage at 5% humidity (non-condensing) ambient temperature 120F without system damage. | T | ||
| 3.12.6 | The system shall be capable of full operations while withstanding rainfall of 1.7 millimeters per minute with a velocity of 45 miles per hour using varying droplets sized from 0.5mm to 4.5mm in diameter without system damage. | T | ||
| 3.12.7 | The system shall operate after being subjected to transportation shock. | T | ||
| 3.12.8 | The system shall be capable of operating when subjected to temperature shock. | T | ||
| 3.12.9 | The system shall be capable of operating when subjected to solar radiation. | T | ||
| 3.12.10 | The system shall be capable of operating when subjected to blowing sand. | T | ||
| 3.12.11 | The system shall be capable of operating after being subjected to secured cargo transportation. | T | ||
| 3.12.12 | The system shall be capable of operating when subjected to ice/freezing rain 6 - 13 millimeters. | T | ||
| 3.12.13 | The system shall be capable of storage/air transport at 40,000 feet. | T | ||
| 3.12.14 | The system shall be capable of full operations in sustained wind speeds of 45 mph while in operational mode. | T | ||
| 3.12.15 | The system shall withstand wind gusts up to 60 mph while in operational mode. | T | ||
| 3.12.16 | The system shall withstand wind gusts up to 80 mph while in operational mode. (Objective) | O | ||
| 3.12.17 | The system shall, in its operational configuration, withstand exposure to settling dust and shall sustain no dust penetration that affects operational service requirements. | T |
File details come from the government source that posted it. Updated .