Attachment_2_Sustainment_Technical_Acceptability_Matrix.pdf
PDF 35 KB Posted
- Attached to
- HH-60G Degraded Visual Environment System(DVES)
- Solicitation number
- FA8552-18-R-0005
About this file
Sustainment Technical Acceptability Matrix
View the file
Other files
Show all 44
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
RFP FA8552-18-R-0005
ATTACHMENT 2
SUSTAINMENT TECHNICAL ACCEPTIBILITY MATRIX
TECHNICAL
RQMTS DOC
Section L
Section M
Threshold Requirement Proposal Specification (Offeror Completes)
SRD para 3.7.1 II.C.2.d II.C.1.d N/A
SRD para 3.7.1.1 II.C.2.d II.C.1.d Storage life of 5 years SRD para 3.7.1.2 II.C.2.d II.C.1.d Predicted MTBF 350 hours SRD para 3.7.1.3 II.C.2.d II.C.1.d Observed MTBF 350 hours SRD para 3.7.2 II.C.2.d II.C.1.d N/A
SRD para 3.7.2.1 II.C.2.d II.C.1.d MTTR of 45 minutes
SRD para 3.7.2.2.1 II.C.2.d II.C.1.d
Integrated diagnostics to provide system status information and to detect and isolate all faults that degrade DVES functions (software & hardware) and operations
SRD para 3.7.2.2.3 II.C.2.d II.C.1.d Utilizes existing data bus maintenence ports
SRD para 3.7.2.2.4 II.C.2.d II.C.1.d Maintenance/diagnostic data preserved despite power loss, reboot, sanitization, etc.
SRD para 3.7.2.2.5 II.C.2.d II.C.1.d Interfaces with existing downloadable data interfaces
SRD para 3.7.2.2.6 II.C.2.d II.C.1.d Maintenance and diagnostic data unclassified
SRD para 3.7.2.3 II.C.2.d II.C.1.d Contains Power-up BIT, Continuous BIT, Initiated BIT, and Maintenance
BIT
SRD para 3.7.2.3.1 II.C.2.d II.C.1.d BIT shall detect and report all DVES faults within 2 seconds
SRD para 3.7.2.3.2 II.C.2.d II.C.1.d DVES BIT isolates faults with 95% probability at field level
SRD para 3.7.2.3.3 II.C.2.d II.C.1.d DVES BIT isolates faults with 99% probability at intermediate level maintenance
SRD para 3.7.2.3.4 II.C.2.d II.C.1.d 98% of all faults detected and isolated to the repairable, adjustable, or replaceable assembly
SRD para 3.7.2.3.5 II.C.2.d II.C.1.d BIT logs faults to existing HH-60G fault diagnostics system
SRD para 3.7.2.3.6 II.C.2.d II.C.1.d Detected faults recorded with time stamps
SRD para 3.7.2.3.7.1
II.C.2.d II.C.1.d
Fault information used as the basis of fault isolation to the LRU or interconnect wiring (if applicable) shall be provided for USAF incorporation into unit level technical manuals
3.7.2.3.7.2
II.C.2.d II.C.1.d
Fault designation and associated cockpit displays and data records shall be in plain English to preclude the use of fault codes or cross-referencing of multiple codes
3.7.2.3.7.3
II.C.2.d II.C.1.d
BIT of any kind shall be described by text, tables, and diagrams as required to achieve a reasonable understanding at the Field Level and include all faults detected in any BIT mode
3.7.2.3.7.4
II.C.2.d II.C.1.d
Each fault detected shall be described in functional path operating characteristics, detection thresholds, time to set, and requirements for reset or clearing the fault detected
SRD para 3.7.2.3.8 II.C.2.d II.C.1.d
DVES False Alarms (FA) and software reloads will be considered failures and are to be included in the computation of software reliability. A false alarm is a fault detected during normal operations that cannot be repeated during the fault isolation process. Two false alarm types will be included, Type 1 and Type 2
3.7.2.3.8.1
II.C.2.d II.C.1.d
A Type 1 false alarm is a Can Not Duplicate (CND) case. CND rates shall not exceed 2% of faults detected
3.7.2.3.8.2
II.C.2.d II.C.1.d
A Type 2 false alarm is a fault detected and isolated to a LRU when it does not have an actual fault. A Type 2 false alarm is a Re-Test OK
(RTOK). LRU RTOK shall not exceed 1% for units received for BIT indicated failures
SRD para 3.7.2.4 II.C.2.d II.C.1.d The maintenance and checkout of
DVES shall not require a conditioned environment
SRD para 3.7.2.5 II.C.2.d II.C.1.d
DVES shall be designed in modular LRU architecture so that maintenance personnel can easily identify, remove, and replace failed components
SRD para 3.9.3 II.C.2.d II.C.1.d N/A
SRD para 3.9.3.1 II.C.2.d II.C.1.d
DVES maintainability features shall meet requirements of MIL-STD-
1472G Sections 5.8 Physical accommodation and 5.9
Maintenance accessibility
SRD para 3.9.3.2 II.C.2.d II.C.1.d
The system shall be maintainable for all field maintenance actions by the median 90 percent of all USAF military maintainers, as expressed by four multivariate representative cases in Table 3-10, under day/night/all weather conditions, while accommodating maintainers wearing arctic clothing or the chemical, biological, radiological and nuclear (CBRN) gear as shown in Table 3-11
SRD para 3.9.3.3 II.C.2.d II.C.1.d
Routine maintenance actions for removal, replacement, and alignment of DVES shall require no more than the existing HH-60G line maintenance tool kit (e.g. the
General Mechanics Tool Kit (NSN:
5180-01-587-8129) and/or an
Electrical Repairer Tool Kit (NSN:
5180-01-587-8128)). Use of embedded boresight and calibration devices and aids are permitted
SRD para 3.9.3.4 II.C.2.d II.C.1.d
Removal and replacement of DVES shall be accomplished without requiring removal of other components or equipment excluding shrouds or a radome – if equipped
SRD para 3.9.3.5 II.C.2.d II.C.1.d
Each LRU shall be equipped with sufficient design features (as per
MIL-STD-1472G, Section 5.9, design for the maintainer) to aid inspection, removal and replacement. The type of handles / grips required should be considered in conjunction with the weight, size, center of gravity (CG), and angle of the equipment, and below lift/distance/twist/frequency information
SRD para 3.9.3.6 II.C.2.d II.C.1.d
Any equipment assembly requiring more than a single maintainer lift shall be prominently labeled with the weight of the object and lift limitation (e.g. “two-maintainer lift only”) based on analysis of specific
LRU maintainer tasks using limits as per Table 3-12 and Table 3-13
SRD para 3.9.3.7 II.C.2.d II.C.1.d
Any DVES component with data storage that requires transportation back to the vendor for maintenance/repair shall include a function to completely and irrevocably erase all mission-related data on that device
The Sustainment Technical Acceptability Matrix will be utilized to evaluate the technical acceptability of Subfactor Four: Sustainment. Requirements information has been provided in columns 1-4. The offeror shall complete column 5 with the projected performance of the offeror’s technical solution in regard to the requirement. The offeror shall provide any necessary details, explanations, and evidence to support the projected performance specification in column 5.
FOR OFFICIAL USE ONLY
RFP FA8552-18-R-0005
File details come from the government source that posted it.