NVD-N SOW UPDATE - (27Nov24).pdf
PDF 394 KB Posted
- Attached to
- Night Vision Device - Next (NVD-N) Federal contract opportunity
- Solicitation number
- W91CRB-25-R-0007
About this file
This Statement of Work (SOW) outlines requirements for the Night Vision Device-Next (NVD-N) program, managed by the Product Manager, Soldier Maneuver Sensors (PdM SMS) at Fort Belvoir, VA. The contractor shall develop, produce, and test a low-cost solution for a helmet-mounted, low light level amplification, binocular night vision device that includes the NVD-N Binocular Goggle, operator's manual, quick reference guide, sacrificial window, light interference filter, de-mist shield, objective lens cap, helmet NVG shroud mount, and soft carry case.
The SOW details comprehensive testing requirements including Engineering Development Testing (EDT), Early Abbreviated Demonstration (EAD), Limited User Test (LUT), Logistics Demonstration (LD), and Initial Operational Testing and Evaluation (IOT&E). Key program milestones include Post Award Conference within 14 days of award, Preliminary Design Review in conjunction with PAC, Critical Design Review 60 days after PDR, and Production Readiness Review 150 days after LUT/EAD. The contractor must meet reliability requirements including Mean Time Between Essential Function Failure (MTBEFF) targets and demonstrate system performance through qualification testing. The program includes requirements for technical manuals, training materials, logistics support, configuration management, and comprehensive security protocols. Foreign Military Sales variants are permitted with modified performance specifications.
View the file
Other files for this federal contract opportunity
Show all 28
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
Night Vision Device-Next (NVD-N)
Statement of Work (SOW)
27 November 2024
Office of Primary Responsibility (OPR): PdM SMS Category: SP CTI
Distribution Statement: D POC: Ron Boisvert ronald.a.boisvert.civ@army.mil 703.704.0133
DISTRIBUTION STATEMENT D
Distribution authorized to DoD and DoD Contractors only; Administrative or
Operational Use; Export Control; Feb 2021. Other requests for this document shall be referred to: Product Manager, Soldier Maneuver Sensors (PdM SMS) 9625
Middleton Rd., Bldg 1189 Fort Belvoir, VA 22060
WARNING:
This document contains technical data whose export is restricted by the Arms
Export Control Act (Title 22, U.S.C., Sec 2751, et. seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 in accordance with provisions of DoD Directive 5230.25.
CUI
1. SCOPE
The NVD-N effort is to develop, produce, and test a low-cost solution for a helmet-mounted, low light level amplification, binocular night vision device. This SOW specifies the tasks and efforts the Contractor shall perform during this contract for the NVD-N. This SOW also establishes the systems engineering, program management, quality assurance, logistics, configuration management, and safety requirements for NVD-N.
The contractor shall ensure the NVD-N systems comply with the requirements of the performance specification, this SOW and contract terms & conditions.
2. APPLICABLE DOCUMENTS
Table 1 below lists the documents which form a part of this SOW to the extent specified herein. Unless otherwise specified, the latest revision of each document shall apply.
Table 1 – Applicable Documents Guide/Regulation/ Specification/Standard Full Title Date
AR 381-12 Threat awareness and Reporting Program 1 Jun 2016 AR 530-1 Operations Security 26 Sep 2014 AR 710-2 Supply Policy Below the National Level 28 Mar 2008 AR 735-2 Property Accountability Policies 14 Jan 2022 DA Pam 710-2-1 Using Unit Supply System (Manual Procedures) 01 Dec 2016 DoD 4500.9-R Part II Defense Transportation Regulation Part II Cargo Movement 06 Aug 2020 DOD 5100.76-M Change 2 Physical Security of Sensitive Conventional Arms, Ammunition, and Explosives (AA&E) 05 Oct 2020
I2 Devices SCG Security Classification Guide (SCG) for Image Intensification (I2) Devices
9 April 2021
ISO/IEC 17025: 2017 General Requirements for the Competence of Testing and Calibration Laboratories
Nov 2017/Mar
Laser Protection SCG Security Classification Guide for Laser Protection Materiel 13 Dec 2019 MIL-PRF-A3309670 NVD-N Performance Specification 16 Sep 2024 MIL-STD-129R Military Marking for Shipment and Storage 27 Mar 2023 MIL-STD-130N Identification Marking of U.S. Military Property 26 Aug 2019 MIL-STD-810H Change 1 DOD Test Method Standard: Environmental Engineering
Considerations and Laboratory Testing 18 May
MIL-STD-40051-2D Change 1 Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)
22 Nov 2021
AR-700-145 Item Unique Identification 16 Dec 2020
2.1. ORDER OF PRECEDENCE
In case of conflict regarding requirements contained in this contract, the order of precedence is:
a. Performance Specification (MIL-PRF-A3309670)
b. Statement of Work (SOW)
c. Qualification Test Plan (QTP)
2.2. DISCREPANCIES
The contractor is responsible for notifying the Procuring Contracting Officer (PCO) immediately in the event that any information contained within this SOW contains any inconsistencies and or vacuities.
2.3. GOVERNMENT FURNISHED INFORMATION
Within 10 days after receipt of award, the Government will provide information that the Integrated Product Team (IPT) deems necessary for the program that was not provided in the contracting package.
2.4. COPIES OF SPECIFICATIONS
The contractor shall review the entire contract to identify all directly cited and subsequent referenced documents. Copies of the specifications required by contractors in connection with specific procurement functions should be obtained from the procuring activity, as directed by the PCO.
2.5. GOVERNMENT-FURNISHED DRAWINGS
The drawings specified in this contract depict the physical and functional requirements for the complete item and parts thereof. They do not contain complete details of all intervening processes, from raw material to finished products, which are necessary to fabricate, control, test, adjust, assemble and inspect the equipment on order. The system must qualify to meet the performance specification and drawing requirements.
Unclassified drawings and specifications furnished with this contract may be retained by the offeror for future reference or disposed of in any manner at the discretion of the contractor.
2.6. CLASSIFIED INFORMATION
The contractor shall comply with Federal Acquisition Regulation (FAR) 52.204-2, Security Requirement. This clause involves access to information identified as “Confidential,” “Secret,” or “Top Secret” and requires contractors, and any applicable subcontractors to comply with: (1) the Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (NISPOM) (DoD 5220.22-M); and (2) any revisions to the Department of Defense (DoD) 5220.22-M, notice of which has been furnished to the contractor.
3. REQUIREMENTS
This section is outlined in six sub-sections: Overall, Program Management, Quality Assurance and Test, Reliability, System Requirements, and Integrated Logistics Support. This section outlines terminology clarification and contractor responsibility with respect to required security trainings.
3.1. OVERALL
This section outlines terminology clarification and contractor responsibility with respect to required security trainings.
3.2. TERMINOLOGY
When the term “days” is used throughout this document, it shall refer to calendar days, unless explicitly specified as business days. All deliveries shall be made on a business day and Close of Business (COB) is defined as 1600 (Eastern Standard/Daylight Time). The contractor shall provide the Government with the tracking information for the delivery.
3.3. PROGRAM MANAGEMENT REQUIREMENTS
The contractor shall manage all aspects of the contract with respect to cost, schedule, system design, development, fabrication, engineering, configuration management, risk management, test, technical performance, and supply control.
3.3.1. Program Management Objective
The contractor shall manage all aspects of the contract with respect to cost, schedule, system design, development, fabrication, engineering, configuration management, risk management, test, technical performance, and supply control. The contractor, at a minimum, shall implement processes for the following:
3.3.1.1. Program Planning, Management, and Control
The contractor shall manage and participate in necessary business and administrative planning, test planning, organizing, directing, coordination, and approving actions designated to accomplish program objectives.
3.3.1.2. Sub-Contractor/Vendor Management
The contractor shall establish and maintain a subcontract management program. The contractor shall facilitate Government and subcontractor discussions/activities as required by the Government.
3.3.2. Informal Review/Integrated Product Team (IPT)
The contractor shall incorporate an IPT discipline with Government participation into the NVD-N program. All reporting for the IPT shall be in contractor format as agreed upon with the Government. The IPT shall consist of Government and contractor personnel associated with the NVD-N program and related efforts. The co-chairs shall define the membership of the IPT at the Post Award Conference (PAC), to be held within 14 days after contract award. Under CDRL B001, the following shall be delivered: Read-Ahead Briefing (including Meeting Agenda), and informal Meeting Minutes. The IPT shall:
a. Use risk management techniques to document, track, and manage program areas of risk.
b. Review/concur on program documentation.
c. Review Environmental Stress Screening (ESS), qualification testing, and lot acceptance testing results.
d. Review/concur on Failed Item Analysis Reports (FIARs) and Engineering Change Protocols (ECPs).
e. Review the Integrated Master Schedule (IMS).
3.3.3. Formal Reviews
Formal reviews shall be hosted by the contractor, unless otherwise agreed upon by the IPT. PAC, Preliminary Design Review (PDR), Critical Design Review (CDR), Test Readiness Review (TRR), and Production Readiness Review (PRR) formal reviews shall be held. Under CDRL B001, as part of the exit criteria for each formal review, the following shall be delivered: a Read-Ahead Briefing (including Meeting Agenda) and a Meeting Report (formal Meeting Minutes). Successful conclusion of each formal review shall include but is not limited to the following exit criteria:
3.3.3.1. PAC Exit Criteria
a. Mutual understanding of terms, conditions, and requirements.
b. Mutual understanding of provisioning requirements determination for kit and components.
c. Contractor’s proposed communication plan to include the establishment of the effective use of contractor’s file sharing system.
d. Submitted overview of contractor’s quality management system plan and approach including NVD-N-unique areas.
e. Contractor’s overview of their Reliability Program as a briefing at the PAC as required in Section 3.5.1.
f. Submittal of all PAC-related deliverables IAW CDRL B001.
3.3.3.2. PDR Exit Criteria
a. All required system performance is fully deconstructed and defined in the functional baseline.
b. Technical effort and design indicate operational test success (effective, suitable, and survivable).
c. Preliminary design, as disclosed, satisfies the NVD-N system-level performance and component specifications.
d. Preliminary design, as disclosed is affordable, producible, and sustainable.
e. Summarized status of the reliability and maintainability engineering design activities (i.e., allocations, models, block diagrams, predictions, anticipated failure modes and effects).
f. Established and documented system allocated baseline to enable the design to proceed with proper configuration management.
g. Established adequate processes and metrics for the program to succeed.
h. Included human integration design factors in the overall system design.
i. System Engineering Management Plan (SEMP) draft IAW CDRL A001.
j. The System Engineering Management Plan (SEMP)’s risk management section, IAW CDRL A001, shall include program risks identified and risk mitigation strategies for all functional areas.
k. Program schedule is executable (technically, cost-wise, and via risk mitigation).
l. Program is properly staffed.
m. Description of all required unique tooling and test equipment to produce and test the NVD-N.
n. Test, Measurement, and Diagnostic Equipment (TMDE) Adapter kit plan
o. Item Unique Identification (IUID) submission of IUID format and sample review IAW IUID Marking
Plan IAW CDRL D001 for concurrence at CDR.
p. All associated action items from previous reviews have been dispositioned/closed.
q. Meeting report delivered IAW CDRL B001.
3.3.3.3. CDR Exit Criteria
a. Technical effort and design indicate operational test success (effective, suitable, and survivable).
b. Detailed design, as disclosed, satisfies the NVD-N Performance Specification.
c. Documented reliability and maintainability engineering design activities (e.g., producibility, thermal analysis, stress analysis).
d. Documented software engineering activities including complete system state summary and state transition analyses, allocation of state transitions to digital logic and logic bearing components.
e. Processes and metrics indicate programmatic suitability and management success.
f. Human integration design factors included in the overall system design.
g. Update and agree upon program risks for all functional areas.
h. Program schedule identifies critical path drivers and is executable (technically, cost-wise, and via risk mitigation).
i. Program is properly staffed.
j. Identification of all required unique tooling and test equipment to produce and test the NVD-N.
k. All required system performance is fully deconstructed and defined in the functional baseline.
l. Establish system initial product baseline which describes the detailed design for production, fielding/deployment, operations, and support.
m. EMD schedule including but not limited to fabrication, test and evaluation, software coding, critical path drivers.
n. Logistics Support Plan delivered IAW CDRL-D002.
o. Identify all exposed materials of the design (to include ancillary items) to support Chemical, Biological, Radiological, and Nuclear (CBRN) Contamination Survivability (CS) analysis.
p. Identify all precious metals (including amount in grams), toxic or hazardous materials, and all material(s) for each optical element, of the entire design (to include ancillary items).
q. Submitted Level of Repair Analysis (LORA) IAW CDRL-D003.
r. Provisioning Tech Data and Parts List – Goal is to have the 80 percent solution.
s. TMDE Adapter kit plan/design/drawings.
t. SEMP final draft IAW CDRL A001.
u. IUID Marking Plan IAW CDRL D001 approved.
v. All associated action items from previous reviews have been dispositioned/closed.
w. Meeting report delivered IAW CDRL B001.
3.3.3.4. TRR Exit Criteria
The Contractor shall conduct a TRR to assess test objectives, schedule, test methods and procedures, scope of tests, safety, and to verify the required test resources have been properly identified and coordinated to support planned tests. The contractor shall host TRRs for required qualification tests no later than (NLT) thirty (30) days before the start of the test. At the TRR, the Government shall verify the traceability of planned tests to program requirements, determine the completeness of their test procedures, and their compliance with test plans and descriptions. The contractor shall provide evidence to assess the system for development maturity, cost/schedule effectiveness, and risk to determine readiness to proceed to formal testing. Exit criteria for the completion of the TRR shall (at a minimum) include:
a. Provide a summary of previous contractor and Government test results.
b. List significant open issues and failures from previous testing along with root cause, corrective action timeline, validation, and whether a corrective action is included in the current test. If corrective actions have not been implemented, discuss the status and planned implementation and validation.
c. Assess the risk (red/yellow/green) of each issue's potential impact on the upcoming test event, and any mitigations planned.
d. If the test involves a system of systems, address the total system from a Soldier mission perspective.
e. Assess the overall System Readiness (red/yellow/green) for successfully completing test event.
f. Test Plans shall be completed and accepted IAW CDRL C001.
g. Test Procedures shall be completed and accepted IAW CDRL C002.
h. Required test resources, to include roles and responsibilities of all test participants, shall be identified and coordinated.
i. Test/inspection data on subsystems and components verifying that the requirements in the System
Requirements Management System (SRMS) have been met for those items.
j. The Contractor shall address the planned reliability demonstration, to include sample size, number of planned test hours, description of the test profile and environments, operational checks to be performed, and facilities required.
k. Identified risk level acceptable to the program leadership.
l. Configuration of the systems to be tested is defined for the complete Bill of Materials, both hardware and software, and all units to be tested are of the same configuration.
m. All associated action items from previous reviews have been dispositioned/closed.
n. System Support Package per Section 5.3.
o. Meeting report delivered IAW CDRL B001.
3.3.3.5. PRR Exit Criteria
Successful exit of PRR is required to proceed from the EMD phase and enter into Production. Production minimum quantities will not be authorized/approved unless PRR exit criteria are met. However, the Government reserves the right to initiate an accelerated production schedule and conduct a PRR prior to completion of EMD based on a government Technical and Manufacturing Readiness Assessment and pending availability of funds. To successfully exit PRR, government approval is required that the contractor has accomplished/verified the following*:
a. EMD testing complete and root cause determinations made for all test incidents.
b. Corrective Actions have been identified and implementation plan presented for concurrence.
c. System product baseline to enable initial production to proceed is defined for the complete Bill of
Materials with proper configuration management established and documented.
d. Status of materials to support builds (e.g., on hand, on order, delivery schedules) has been identified.
e. Design meets the requirements of the Performance Specification. Any requirement that has not been met has an approved variance to start production.
f. Required tooling, test equipment, assembly documentation, and operator training is in place, has occurred, or the completion date has been identified.
g. Key tooling and test equipment parameters, to include tolerances or minimum/maximum values that are included in the calibration process and their relationship to performance parameters, have been identified and documented.
h. Calibration cycles for new tooling and test equipment have been identified and shall be tracked by Contractor.
i. Identification and documentation of production layout and flow analyses.
p. Identification and agreement of production risks and mitigation plans.
q. Identification of any significant changes to the contractor’s reliability process, reliability risk assessment, reliability predictions, System Reliability Model (SRM) and/or reliability verification as a result of engineering, process or design changes.
j. Established adequate processes and metrics for the program to succeed.
k. Executable program schedule (technically, cost-wise, and via risk mitigation).
l. Program is properly staffed for project execution.
m. Updated LORA IAW CDRL D003 and PPL IAW CDRL D004 based on any design changes from CDR.
n. Review of Packaging, Handling, Storage, and Transportation (PHST) e.g., markings per section 5.9.
o. All associated action items from previous reviews have been dispositioned/closed.
p. Meeting report delivered IAW CDRL B001.
*Elements may be waived for accelerated production schedule
3.3.3.6. Functional Configuration Audit (FCA)/Physical Configuration Audit (PCA) FCA and PCA shall be conducted IAW paragraph 4.6 of this SOW. Meeting report delivered IAW CDRL B001.
3.3.4. Data Submissions
3.3.4.1. Data Requirements
The data items shall be submitted to the Government via electronic media. The Contractor shall submit written program correspondence and documentation using a Microsoft product format agreed to by both the Government and the Vendor. No cost, non-email alternative correspondence submittal procedures may be allowed on a case-by-case basis with either Government IPT chairperson or Government Contracts Officer concurrence.
3.3.5. Data Rights
Government rights are defined in the Defense Federal Acquisition Regulation Supplement (DFARS) clauses 252.227-7013, 252.227-7014 and 252.227-7030. All NVD-N Interface Control Documents (ICDs) shall be delivered to the Government with Unlimited Data Rights. Per DFARS 252.227-7017, the Contractor asserts for itself, or the entities identified in a completed Data Rights Assertions table (template shown in Table 2), that the Government’s rights to use, release, or disclose the following technical data or computer software should be restricted.
Table 2 – Data Rights Assertions Technical Data or Computer Software to be Furnished w/
Restrictions
Basis for Assertion Asserted Rights Category Entity Asserting
3.4. QUALITY ASSURANCE AND TEST REQUIREMENTS
The contractor shall establish, maintain, and operate a quality system IAW ISO 9001:2015, or an equivalent quality system. The contractor shall provide the Government an overview of their quality management system plan and approach as a briefing to the PAC to include NVD-N unique areas. Quality Assurance, including reliability, shall be addressed at each contractually required review, to include Statistical Process Control (SPC), Pareto charts, and other metrics employed by the prime contractor and their major suppliers to control critical processes. The contractor shall ensure the NVD-N program incorporates the provisions, practices and protocols of their Quality Management System. The Government reserves the right to review or evaluate the contractor’s Quality Management System or specific program performance indicators as agreed to in advance, by both the Government and the contractor. The contractor shall maintain a calibration system IAW ISO/IEC 17025: 2017 or Government approved equivalent to demonstrate that test, modeling and simulation, measurement and evaluation are repeatable and reproducible while ensuring that all test/inspection, measurement, and diagnostic equipment are properly calibrated, identified by appropriate labeling, and are traceable to national measurement standards. This includes all accessories and all ancillary test equipment.
3.4.1. Supplier Quality Management
The contractor shall be responsible for verifying the quality of the work performed by suppliers, including any inspections and tests performed by the suppliers. The contractor shall describe any methods unique to this contract of supplier selection, retention, management, inspection, and test validation or other supplier controls above and beyond that which is described in the contractor’s Quality Management System. The contractor shall establish the appropriate procedures and process for managing and controlling their supply base to ensure that the quality and quantities of the materials/products and services provided do not adversely affect the program performance. The contractor shall also give recommendations for any new methods and procedures that will improve the quality and test of the material/product and will present to Government for review and approval decision. Suppliers of key/critical components or processes shall be identified including names and contact information of key supplier personnel. The Government reserves the right to review/audit any suppliers of key/critical components. No review/audit of any suppliers by the Government will relieve the contractor of the responsibility of managing suppliers.
3.4.1.1. Measurement Standards
Correlation testing shall be conducted with the Government laboratory, on an as-needed basis, to ensure acceptable standards are being maintained. Gauge Repeatability and Reproducibility (R&R) testing data shall be presented to the Government, on an as needed basis, to ensure all testing is repeatable and reproducible.
The Government will decide what is the standard of measurements for all image intensifier tubes and systems. This may require the Government to visit the contractor if there are correlation issues until they are resolved or until the Government is satisfied with the correlation results. The contractor shall perform and document these measurements using actual production test and acceptance equipment. IAW CDRL B001, measured data, whether raw or finalized, shall be presented to the Government at Informal Reviews to include comparisons to past data (both contractor and Government) and the identification of any trends, positive or negative. The contractor shall, at no additional expense to the Government, address and rectify to the Government’s satisfaction, any correlation issues identified through Government correlation testing.
Night vision goggle visual performance parameters requiring correlation and Gauge R&R shall be agreed upon at the PAC, and shall include, but not be limited to Luminance and System Gain, System Resolution, System Halo, and System Brightness Non-Uniformity.
3.4.1.2. Inspection Responsibility
The contractor shall perform all inspection requirements specified herein. Except as otherwise specified in the contract and with Government concurrence, the contractor may use his own or any other facilities that are suitable for the performance of the inspection requirements specified herein. The Government reserves the right to audit, perform, witness, or verify any of the inspections set forth herein from the contractor and/or subcontractors. The contractor shall correct any deficiencies found during required contractor and government testing in all affected contractor products at no additional cost to the Government.
3.4.1.3. Use of Government Property/Material
The contractor's quality program shall include procedures for the control, use, and maintenance of Government Furnished Property (GFP). GFP includes Government Furnished Equipment (GFE) and Government Furnished Material (GFM). The contractor shall notify the Government within seven (7) days after receiving the GFP, that they have conducted an initial inspection and report any damage or discrepancies in quantities received. The Government will assist the contractor when discrepancies with GFP are identified during inspection, testing, or use has started. The contractor shall maintain accounting records of GFP received by date, and disposition of GFP. The contractor shall provide a Government Property Inventory Report in accordance with CDRL C003.
3.4.1.4. Use of Contractor’s Inspection Equipment
The contractor's gauges, measuring tools, test benches, and testing devices shall be made available for use by the Government when requested to determine conformance with contract requirements. If requested by the Government, the contractor's personnel shall be made available for operation of such devices and for verification of their accuracy and condition.
3.4.1.5. Inspection and Test Records
The contractor shall maintain complete and accurate records of all inspections and tests performed and the corresponding results IAW contract data retention requirements. The contractor shall make those records available for review or audit by the Government upon request.
3.4.1.6. Measurement Interface Equipment
The contractor shall provide the Government with a minimum of two (2) sets of interface adapters for TMDE to support Government measurement of required performance parameters identified in this SOW and the NVD-N Performance Specification, MIL-PRF-A3309670.
3.4.2. Government and Contractor Testing
The contractor shall provide NVD-N test systems, for Government and contractor qualification testing. The contractor shall provide the required number of systems along with repair parts/System Support Package (SSP) as required for the various test events IAW with the schedule in Table 3. The contractor shall correct all deficiencies found during all Government and contractor testing events, conduct appropriate retest of EDT-C per section 3.4.2.2.2, as necessary, at no cost to the Government, and shall provide corrected units for continuance of the test schedule, at no cost to the Government.
3.4.2.1. Government Testing
The Government will conduct several test events to facilitate developmental and operational assessments, and to ensure the contract requirements are satisfied both technically and operationally per Table 3. The contractor will provide the quantity of systems for those tests per Table 3. During Government testing, the contractor shall provide on-call support at a location on or close to the test site. The contractor’s representative(s) shall inspect, repair, maintain, modify, perform failure analysis, consult and train the NVD-N as required. Government testing will encompass all testing required to confirm that the system adequately addresses all KPPs, Key System Attributes (KSAs), and conforms to the applicable performance specifications.
The planned events are discussed below.
Engineering Development Test – Government (EDT-G) The Government shall conduct testing on NVD-N systems to assess several user requirements. EDT-G will consist of the tests identified as such in the IAW the Requirements Verification Matrix (RVM) in the NVD-N Performance Specification MIL-PRF-A3309670.
Early Abbreviated Demonstration (EAD) An EAD is used to influence the supportability of the system during development and may include tailored tests, selected analysis, evaluations, and demonstrations that have been modified for each program by the Government. The contractor will insert/simulate faults. The Government will verify all repair actions using the contractor fault-tree analysis. The contractor shall support an EAD using NVD-N systems as outlined in Table 3. The contractor shall deliver an EAD plan IAW CDRL D005.
Limited User Test (LUT) LUTs are executed by the Government for operational assessment and to collect reliability data. The LUT will focus on convoy operations and associated skill levels 1 and 2 Soldier tasks, e.g., reconnaissance, surveillance, dismounted land navigation, driving a vehicle, reading a map, changing a tire, and loading/unloading cargo from a vehicle. Soldiers shall be surveyed on training, system usability, and human factors. Contractors shall be given the opportunity to interview Soldiers. The data collected shall be provided to the contractor.
Logistics Demonstration (LD) The LD is used to assess the adequacy of the System Support Package (SSP) and ensure the user has the logistical capability to achieve Initial Operational Capability (IOC). The purpose of the LD is to evaluate the achievement of maintainability goals, the adequacy and sustainability of tools, test equipment, selected test program sets, built-in test equipment, associated support items of equipment, technical publications, and maintenance instructions. It also evaluates the adequacy of troubleshooting procedures, personnel skill requirements, the selection and allocation of spare parts, tools, test equipment, and tasks to appropriate maintenance levels, and the adequacy of maintenance time standards. The LD can include nondestructive disassembly and reassembly of a production representative system using its related peculiar TMDE. The LD will be held concurrently with the TM Verification. The LD is used to influence the supportability of the system during development and may include tailored tests, selected analysis, evaluations, and demonstrations that have been modified for each program by the Government. The contractor will insert/simulate faults. The Government will verify all repair actions using the contractor fault-tree analysis.
The contractor shall support an LD using NVD-N systems as outlined in Table 3. The contractor shall deliver an LD Plan IAW CDRL D006 and LD Report IAW CDRL D007.
Initial Operation Testing and Evaluation (IOT&E) IOT&E is conducted on production, or production representative articles, to determine whether systems are operationally effective, suitable, and survivable in an operational environment for intended use by representative users to support the decision to proceed beyond Low-Rate Initial Production (LRIP). IOT&E will test the threshold and objective values from the Capability Development Document (CDD). Reduction in any Key Performance Parameters (KPP) threshold value will require a reassessment of the military utility of the reduced capability. The IOT&E scope will include system performance, driving performance, marksmanship, and human factors. IOT&E will focus on convoy operations and associated skill levels 1 and 2 Soldier tasks, e.g., reconnaissance, surveillance, dismounted land navigation, driving a vehicle, reading a map, changing a tire, and loading/unloading cargo from a vehicle. Soldiers shall be surveyed on training, system usability, and human factors. Contractors shall be given the opportunity to interview Soldiers. The data collected shall be provided to the contractor.
3.4.2.2. Contractor Testing
The contractor will conduct developmental testing including environmental screening (IAW MIL-STD-810H), reliability testing, and transportation testing.
Test Plans, Procedures, and Reports The contractor shall provide the following deliverables:
a. Test Plans. The contractor shall prepare and submit a test plan prior to Engineering Development Test-Contractor (EDT-C), Production Qualification Test (PQT), Acceptance Test (AT), Conformance Inspection (CI), or any other required qualification test. Test plans shall be delivered IAW CDRL C001.
b. Test Procedures. The contractor shall prepare and submit to the IPT for concurrence, test procedures for EDT-C, acceptance testing, qualification testing, and lot acceptance testing of the NVD-N systems, image intensifier assemblies, and major components IAW the RVM in the NVD-N Performance Specification. The contractor shall use the same procedures for all testing unless modifications are agreed upon by the IPT. Any modifications to the agreed-upon procedures shall be concurred with, in writing, by the IPT chairpersons prior to being implemented. Final approval of the test procedures shall occur prior to commencement of testing. Test procedures shall be delivered IAW CDRL C002.
http://acqnotes.com/acqNote/initial-operational-capability http://acqnotes.com/acqNote/low-rate-initial-production http://acqnotes.com/acqNote/capability-development-document-cdd http://acqnotes.com/acqNote/key-perfrormance-parameter
c. Test Reports. The contractor shall prepare and submit, to the IPT, test reports which shall reflect the test results, including raw data, compiled and calculated data (to include mathematical equations/models used), test conclusions, and test logs. The report shall address all testing performed and all failures encountered. All conclusions shall be clearly identified as such and shall be appropriately segregated from the objective results. Upon completion of any contractor test event, test reports shall be delivered IAW CDRL C004.
Engineering Development Test – Contractor (EDT-C)
The contractor shall conduct EDT-C for the NVD-N using approved test plans and procedures. During EDT-C, the contractor shall notify the IPT before any changes are made to the materials (to include suppliers), configuration, or processes utilized to manufacture the NVD-N. Changes to materials, configuration, processes, procedures, equipment, and facilities may require a portion of the respective EDT-C to be rerun, as determined, and agreed upon by the IPT. The EDT-C shall demonstrate all requirements of the NVD-N Performance Specification, MIL-PRF-A3309670. At the conclusion of each EDT-C, the contractor shall submit a test report IAW CDRL C004. If failures occur during testing, the contractor shall be responsible for all subsequent costs associated with any design modifications and corrective actions, support documentation updates, and retesting actions required to validate all corrective actions. The contractor shall present ESS, qualification tests, and lot acceptance testing results (e.g., number of units tested, failure rate, failure Pareto charts to include reasons for failures, corrective actions, and analysis of corrective action effectiveness) at each program review.
Delta EDT-C If EDT-C failures require retesting, the contractor shall conduct Delta EDT-C for the NVD-N using approved test plans and procedures. Delta EDT-C shall focus on any failures that occurred during EDT-C and/or high-risk performance parameters that USG determined were affected by corrective actions from all prior testing events.
Production Qualification Test (PQT) Production Qualification Test (PQT) is conducted to ensure the effectiveness of the manufacturing process, equipment, and procedures. PQT shall be required initially as well as in the event there are any configuration changes made to the qualified NVD-N product baseline. The extent of PQT (i.e., test requirements to be revalidated) will be as agreed to by the Government and contractor.
The contractor shall notify the IPT before any changes are made to the materials (to include suppliers), configuration or processes utilized to manufacture the qualified NVD-N. Changes to materials/suppliers, configuration, processes, procedures, equipment, or facilities may require a Delta PQT to be rerun as agreed to by the IPT. PQT shall be performed on all major components IAW the RVM in the NVD-N Performance Specification using approved test plans and procedures. Qualification shall require successful completion of the Government witnessed PQT to include reliability testing and Human Systems Integration (HSI) testing. If failures occur during testing, the contractor shall be responsible for all subsequent costs associated with any design subsequent modifications and corrective actions, support documentation updates, and retesting actions required to validate all corrective actions and successfully complete requalification.
Acceptance Test (AT) and Conformance Inspection (CI) The contractor shall conduct Acceptance Test (AT) and Conformance Inspection (CI) for each NVD-N, and all major components IAW the RVM in the NVD-N Performance Specification using approved test plans and procedures. If failures occur during testing, the contractor shall be responsible for all subsequent costs associated with any design modifications and corrective actions, support documentation updates, and retesting actions required to validate all corrective actions and successfully complete re-qualification. The contractor shall present Environmental Stress Screening (ESS) and AT results (number of units tested, failure rate, failure Pareto charts to include reasons for failures, corrective actions, and analysis of corrective action effectiveness) at each formal IPT review.
3.4.3. Quality Assurance and Test Schedule
Table 3 – Test, Validation, and Verification Event Schedule Test/Validation/Verification Event
Timeframe Location System Quantity
PAC 14 Days after contract award Contractor 0 PDR In Conjunction with PAC Contractor 0 CDR 60 Days after PDR USG 0 QRG Review 45 Days prior to LUT Virtual 0 TRR 30 Days prior to EDT-C, Delta EDT-C, and
LUT
Virtual 0
Safety Inspection/Verification 15-30 Days prior to EDT-C/G, and LUT Virtual 0 TM Review (-10) (-20&P) 30% 120 Days after CDR Virtual 0 EDT-C 150 Days after CDR Contractor 30 EDT-G 150 Days after CDR USG 14 LUT 150 Days after CDR USG 11 TM Review (-10) (-20&P) 50% 30 Days prior to EAD Virtual 0 EAD 150 Days after CDR with LUT Contractor 3 TM Review (-10) (-20&P) 70% 30 Days after EAD Virtual 0 TM Review (-10) (-20&P) 100% (TM Validation)
14 Days prior to PRR USG 3
PRR 150 days after LUT/EAD Contractor 0 PQT 150 days after PRR Contractor 43 FAT Upon successful completion of PQT Contractor Lot Production LD/TM Verification 30 days after successful completion of PQT Contractor 4 FCA 45 days prior to IOT&E Contractor 1 IOT&E 30 days after FAT USG 24 PCA 60 days after IOT&E Contractor 1
3.5. RELIABILITY REQUIREMENTS
3.5.1. Reliability Program Overview
The contractor shall establish, maintain, and operate a Reliability Program acceptable to the Government for the NVD-N program to meet the following objectives:
a. To understand the reliability requirements as specified in the NVD-N Performance Specification
b. To produce reliable systems
c. To design for reliability
d. To monitor and assess field reliability
The contractor shall provide the Government an overview of their Reliability Program as a briefing at the PAC, and at each contractually required review thereafter, to include assessment of field and Government test failures and corrective actions to improve reliability of the systems and spare parts being delivered.
3.5.1.1. System Reliability Model (SRM)
The contractor shall develop a System Reliability Model consisting of the lowest identifiable functions/elements in the NVD-N and their relationships to each other. The SRM shall encompass all hardware and non-hardware elements including, but not limited to, Commercial Off-the-Shelf (COTS), Non- Developmental Items (NDI), Government Furnished Equipment (GFE), software, human factors, and manufacturing. The contractor shall identify critical elements in the system design and additional design or testing activities required to achieve the reliability requirements. Critical elements are defined as those elements whose failure impacts mission completion, essential functions, or safety; or elements whose failure rates contribute significantly to the overall system. Detailed critical component stress and damage models shall be incorporated as appropriate.
3.5.1.2. Reliability Allocation
The contractor shall assign each element of the SRM an assessed and consistent reliability metric (e.g., MTBFs). The values shall be based on one of the following methods:
a. Reliability Analysis from comparable systems/elements
b. Historical reliability from predecessor systems/elements
c. Documented subject matter expert engineering estimation
3.5.1.3. SRM Elements
The contractor shall provide a table with all elements contributing to critical weaknesses of the SRM. Each SRM element shall include its associated reliability metric and risk criteria (low, medium, high) based upon the following guidance:
a. Low Risk – Test data or reliability analysis of comparable systems (under NVD-N-like Operational Mode Summary /Mission Profile (OMS/MP) conditions).
b. Medium Risk – Historical reliability of systems of similar complexity, test data, or reliability analysis of comparable systems (not following NVD-N-like OMS/MP conditions)
c. High Risk – Subject Matter Expert engineering estimates
3.5.1.4. Mitigation
The contractor shall develop a plan to mitigate all critical elements rated as high or medium risk. Mitigation plans may include additional testing, redesign, part selection, etc. The contractor shall provide the Government all mitigation plans upon development.
3.5.1.5. Reliability Verification
The contractor shall perform reliability assessments on data from analysis, modeling & simulation, and test (contractor and Government testing). The contractor shall track the assessments as a function of time and compare them against reliability allocations, reliability requirements, and values to be achieved at various points during development to verify implementation of corrective actions. Table 4 outlines the growth curve that the Government has established for the NVD-N for Mean Time Between Essential Function Failure (MTBEFF), and the IPT will track progress against the curve during program execution. The NVD-N shall demonstrate the required Mean Time Between Essential Function Failure (MTBEFF) and Mean Time Between System Abort (MTBSA); both with 80% confidence, as specified in the NVD-N performance specification. Only NVD-N units that have not been refurbished shall participate in reliability testing. Re-verification is required if the MTBEFF and MTBSA have not been achieved and shall be conducted only if determined necessary by the Government. The Offeror shall be prepared to institute all necessary corrective actions to bring the systems/components into reliability compliance at no additional cost to the Government.
Table 4 – NVD-N Planned Reliability Growth Targets
Test Phase Test Event Minimum Operating Hours Cumulative Operating Hours MTBEFF Point Estimate
EMD EDT-C 500 500
EMD LUT 1,500 2,000 150
LRIP FAT/PQT 1,200 3,200
LRIP IOT&E 1,800 5,000 434
Contractor Reliability Testing
Contractor Reliability testing is conducted IAW the NVD-N Performance Specification. The NVD-N system shall demonstrate the required Mean Time Between Failure (MTBF) with 80% confidence as specified in the NVD-N Performance Specification using MIL-HDBK-781A’s 20% Consumer’s Risk Fixed Length Test Plan. The Delta PQT Contractor – Corrective Action Verification is required if the MTBF and MTBEFF have not been achieved and shall be conducted only if determined necessary by the Government.
Production Reliability Acceptance Test (PRAT) Reports Upon completion of each production reliability test, the contractor shall prepare and submit PRAT reports IAW DI-NDTI-80809B Notice 2. The reports shall be in contractor format and shall include, but not be limited to, a test summary, test description, identification of item(s) under test, lot from which the test sample was taken, supplemental lots represented by the sample, test group number, performance requirements, test profile and operating hours, any anomalies, calculated reliability, measured values taken during the test, conclusions, and applicable FIARs and Sub-Contractor Corrective Action Reports (SCARs). NVD-N PRAT reports shall be prepared and submitted IAW CDRL C004.
3.5.2. Testing Failure Notification/Failed Item Analysis Reports (FIARs)
The contractor shall notify the Government within forty-eight (48) hours of a failure occurrence during all contractor testing. For all failures that occur in Government testing and contractor testing, the contractor shall document the results of their failure analysis and root cause corrective action investigation. A failure record spreadsheet including Test Incident Reports (TIRs) and NVD-N contractor test failures (reported as FIARs) shall be delivered. The contractor shall provide pertinent data on any related failures on other programs. No failure shall be closed without concurrence of the Government. NVD-N FIARs shall be prepared and submitted IAW CDRL C005.
3.5.3. Failure Reporting, Analysis, and Corrective Action System (FRACAS) The contractor shall utilize a closed-loop FRACAS in accordance with ANSI/GEIA-STD-0009A, as its mechanism for monitoring and communicating throughout the organization descriptions of test and field failures, analyses of failure modes and root cause failure mechanisms, the status of design- and/or process-corrective actions, risk mitigation decisions, the effectiveness of corrective actions, and lessons learned. The contractor shall address failure modes in a timely manner, consistent with their impact on safety, reliability, performance, and total life cycle cost.
3.5.4. Environmental Stress Screening (ESS)
Each NVD-N system shall be subjected to an ESS with an appropriate failure-free verification period that is accepted by the Government. The ESS profile shall include both vibration and temperature exposures. The contractor shall include a proposed ESS profile as part of the proposal and shall be designed to effectively reduce/eliminate workmanship and infant mortality type defects. Causes of ESS failures shall be tracked, investigated, and closed per contractor-internal procedures for the purpose of continuously improving the screen and the manufacturing processes. Modifications to the stress profile may be allowed with Government approval based on evaluation of supporting data. Modifications shall not be implemented prior to Government approval. NVD-N ESS reports shall be prepared and submitted IAW CDRL C004.
3.6. SYSTEM REQUIREMENTS
3.6.1. System Engineering Objective/Plan
The objective of systems engineering under this contract is to ensure the contractor successfully produces an NVD-N system kit. The SEMP shall be delivered under CDRL A001.
3.6.2. Complete System
The complete system kit shall meet all requirements per MIL-PRF-A3309670. It shall contain the NVD-N Binocular Goggle (1 ea.), Operator’s (-10) Manual (1 ea.), Quick Reference Guide (QRG) (1 ea.), Sacrificial Window (2 ea.), Light Interference Filter (2 ea.), De-Mist Shield (2 ea.), Objective Lens Cap (2 ea.), Helmet NVG Shroud Mount (1 ea.), and Soft Carry Case (1 ea.). The NVD-N complete system must include all required components and accessories for the user to operate and maintain the system. Any additional items (except batteries) such as lens wipes and ancillary items necessary to support NVD-N at the user level shall also be included in the complete system.
3.6.3. Test, Measurement, and Diagnostic Equipment (TMDE)
The NVD-N will utilize Test Set, Electronic Systems TS-3895A/UV as its TMDE to evaluate, troubleshoot, collimate, and conduct other necessary tests. The Government will provide two TS-3895A/UV test sets to the contractor. The GFE test sets shall be returned to the government within thirty (30) days of notification to the contractor. The TMDE special or common tools that will be used to repair and maintain the NVD-N shall be fully developed and available during the EAD and LD.
3.6.3.1. TMDE Tools, Fixtures and Interface Equipment
System-specific tools, fixtures and interface equipment for the TMDE shall be developed and delivered at EAD. Fixtures shall include any mounts or alignment fixtures not provided with the TMDE hardware that are necessary to evaluate, repair, or perform post-repair testing and validation on the NVD-N. Delivery of the base GFP TMDE hardware and software is anticipated to be delivered approximately one month after receipt of order. TMDE software, tools, fixtures and interface equipment shall function with the NVD-N design that successfully completes Government testing.
4. CONFIGURATION MANAGEMENT
4.1. CONFIGURATION MANAGEMENT OBJECTIVE
The objectives of the Configuration Management requirements are to assure the Government that the contractor maintains a structured approach to controlling the configuration integrity of production systems, maintains interchangeability of hardware, and assures the functional baseline of each system type is maintained throughout the life of the contract.
4.2. SYSTEM BASELINES
The NVD-N Performance Specification shall represent the functional baseline which will be maintained by the Government. The product baseline shall be established for each system type at the successful completion of qualification testing and shall be maintained by the contractor. The product baseline is defined by the product performance specifications, engineering drawings, parts lists, software baselines (version numbers), executing on the system components, and process specifications down to the spare parts level. The product baseline shall be in contractor format.
4.3. CONFIGURATION CONTROL
Any changes to the product baselines shall result in a common configuration…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .