ALEP_3_SOW_-_RFP_Draft.pdf

DRAFT

Aircrew Laser Eye Protection (ALEP) Systems Indefinite Delivery Indefinite Quantity (IDIQ)

Draft Statement of Work (SOW)

Air Force Materiel Command Human Systems Program Office

Wright-Patterson AFB, OH

27 March 2018

Prime Contract Number: FA8606-18-R-0013

Table of Contents

1.1 Introduction

1.2 Background

1.3 Scope

1.4 Reference Documents

2.0 Post-Award Conference and Initial

award IDIQ Requirements

3.0 Delivery Order Overview and

Requirements

3.1 Day Variant Ballistic Spectacles

3.2 Night Variant Ballistic Spectacles

3.3 Day Variant Basic Spectacles

3.4 Night Variant Basic Spectacles

3.5 Day Variant HGU-55/P Visor

3.6 Day Variant HGU-56/P Visor

3.7 Day Variant Joint Helmet

Mounted Cueing System (JHMCS)

3.8 Day Variant Joint Strategic Air

Mask for Strategic Aircraft

(JSAM SA)

4.0 Program Management and

Control

4.1 Program Management

4.2 Quality Assurance Management

4.3 Program Support - Program

Planning and Control

4.4 Security Management

4.5 Program Security

4.6 Acquisition Systems Protection

4.7 Information Security

4.8 Technology Control

4.9 Industrial Security

4.10 Personnel Security

4.11 Operational Security (OPSEC)

4.12 Documentation

4.13 Cost, Schedule, and Performance

Control

4.14 Reviews and Meetings

4.15 Monthly Status Report (MSR)

4.16 Subcontract Management

4.17 Risk Analysis & Management

5.0 Systems Engineering and Design

5.1 Systems Engineering and Design

Management

5.2 Systems Safety

5.3 Critical Design Activities

5.4 IDIQ Data Rights

6.0 Test and Evaluation (T&E)

6.1 T&E Management

7.0 Fabrication and Production

7.1 Fabrication and Production

Management & Support

7.2 Pre-DT&E Fabrication

7.3 Prototype Production DT&E

7.4 Producibility Demonstration &

Manufacturing Readiness Assessment (MRA)

7.5 Low Rate Initial Production

(LRIP)

7.6 Full-Rate Production

8.0 Product Support

8.1 Item Unique Identification (IUID)

8.2 Fielding

8.3 Packaging and Shipping

8.4 Supply Support

8.5 Government- Furnished

Property/Equipment/Information

8.6 Technical Data

8.7 Data Rights

8.8 Warranty

8.9 Diminishing Manufacturing

Sources/Material Shortages Parts Obsolescence

8.10 Disposal

9.0 Intermediate Logistics Support

(ILS)

9.1 ILS Strategy Planning & Working

Groups

9.2 Intermediate Logistics Support

Technical Data

10.0 Training

11.0 Problem Reporting System

12.0 End of Delivery Order Transition

13.0 Deliverables

Aircrew Laser Eye Protection (ALEP) Systems Indefinite Delivery Indefinite Quantity

1.1 Introduction

The intent of this Statement of Work (SOW) for the Aircrew Laser Eye Protection (ALEP) Indefinite Delivery Indefinite Quantity (IDIQ) contract is to identify and select contractors who can perform the specialty of Laser Eye Protection (LEP) and incorporate those technologies into eyewear and helmet/mask affixtures. The purpose of this effort is to further the development of ALEP and/or procure multiple variants of ALEP to fulfill government requirements for over 38,000 units. This SOW addresses the general performance requirements for the ALEP IDIQ contract. Performance requirements for specific ALEP variants shall be defined in specifications, requirements documents, and SOWs included in Delivery Orders (DO). The DOs issued under ALEP IDIQ may include all or a portion of the requirements within this SOW. For awardees at the Multi-award IDIQ level, Contract Data Requirements List (CDRL) A001 is the only required deliverable. All other listed CDRLs, if applicable, will be required at the DO level.

In order to meet the challenge of ALEP, the Air Force Life Cycle Management Center (AFLCMC) Agile Combat Support Directorate, Human Systems Program Office (AFLCMC/WNU) plans to award a multiple award ALEP Indefinite Delivery Indefinite Quantity contract in order to streamline ALEP development, test, and procurement. ALEP will identify a pool of qualified businesses/contractors that are capable of executing ALEP deliveries.

DOs will be incrementally released for the specific ALEP formats in the Block 3 family.

1.2 Background

ALEP provides aircrew with central and peripheral vision protection against laser devices during combat and training missions. The system provides tailored solutions for day and night operations in multiple configurations (Chemical, Biological, Radiological, Nuclear (CBRN), ballistic, and Helmet Mounted Displays (HMD) compatible) that meet requirements for laser protection and visual performance while ensuring flight safety. ALEP enhances aircrew safety by minimizing the effects of specific visible and near-infrared lasers throughout the full range of military operations. Additionally, it applies technology maturation for enhanced LEP to both spectacles and large curved substrates; as well as updating protection levels based on current laser threat climate and ensures compatibility with various head/helmet mounted devices.

Examples include, but are not limited to, ballistic variants for gunners, CBRN mask integration, and HGU-55P/56P day visors.

ALEP users will include Air Force (AF) Active Duty, AF Reserve, Air National Guard, and Department of Defense (DoD) joint warfighters. Aircraft platforms supported include: fighter, bomber, cargo/airlift/tanker, special purpose, and special operations that include helicopter platforms. ALEP performance specifications will be defined by requirements unique to each user’s mission and configuration needs.

1.3 Scope

This document establishes the requirements for the ALEP IDIQ contract. The requirements defined herein establish the scope of deliveries and products that may be exercised through specific DOs. The ALEP deliveries include the design, development, integration, testing, and production of tailored solutions for day, night, ballistic, and helmet mounted displays that balance requirements for laser protection and visual performance while ensuring flight safety. It is intended that detailed requirements will be appropriately documented in the performance specifications SOW as part of each individual DO.

1.4 Reference Documents

Unless otherwise specified, the following documents and the issue in effect on the date of the contract award form a part of this SOW to the extent specified herein. The intent of this list of reference documents is to provide as complete a list as possible of the documents that may be referenced on individual DOs. Not every document will necessarily be referenced within individual DO SOWs. Individual DOs may have additional reference documents unique to a specific program.

Document # Revision Date Title AFI 31-401 Change 1 19 Aug 09 Information Security Program Management AFI 31-501 27 Jan 05 Personnel Security Program Management AFI 31-601 29 Jun 05 Industrial Security Program Management

CJCSI 6510.01F 9 Feb 11 Information Assurance (IA) and Support to Computer Network Defense (CND)

CNSS Instruction

Version

15 Mar 12 Security Categorization and Control Selection for National Security Systems

CNSS Instruction 1253A

Version

15 Mar 12 Security Overlays Template

DoD 5200.2-R Jan 87 Personnel Security Program DoD Instruction 2040.02

10 Jul 08 International Transfer of Technology Articles and Services

DoD Directive 5000.01

20 Nov 07 The Defense Acquisition System

DoD Instruction 5000.02

8 Dec 08 Operation of the Defense Acquisition System

DoD Instruction 5200.01

Change 1 13 Jun 11 DoD information Security Program and Protection of Sensitive Compartmented Information

DoD Instruction 5200.01

P 24 Nov 03 Information Security Program

DoD Instruction 5200.39

Change 1 28 Dec 10 Critical Program Information (CPI) Protection Within the Department of Defense

DoD Instruction 5205.13

29 Jan 10 Defense Industrial Base (DIB) Cyber Security/Information Assurance (CS/IA) Activities

Document # Revision Date Title DoD Instruction 5220.22-M

28 Feb 06 National Industrial Security Program Operating Manual (NISPOM)

DoD Directive 5230.24

Change 1 18 Aug 95 Distribution Statements on Technical Documents

DoD Directive 5230.25

Change 1 18 Aug 95 Withholding Unclassified Technical Data from Public Release

DoD Directive 8500.01

E 24 Oct 02 Information Assurance (IA)

DoD Instruction 8500.2

6 Feb 03 Information Assurance (IA) Implementation

DoD Manual 5200.01 Vol 3 21 Mar 12 Information Security Program Regulation Federal Information Processing Standards (FIPS) Publication 199

Feb 04 Standards for Security Categorization of Federal Information and Information Systems

EAI-649-1 20 Nov 14 Configuration Management Requirements For Defense Contracts

MIL-STD-130 N 17 Dec 07 Identification marking of U.S. Military Property

MIL-STD-882 E 11 May 12 Military Standard, System Safety Program Requirements

TO 00-35D-54 1 Sep 15 USAF Deficiency Reporting, Investigation, and Resolution

AFI 63-101/20-101 9 May 17 Integrated Life Cycle Management

AFMAN 63-119 19 Feb 16 Certification of System Readiness for Dedicated Operational Test And Evaluation

AFI 63-145 30 Sep 16 Manufacturing and Quality Management AFPAM 63-128 10 Jul 14 Integrated Life Cycle Management

2.0 Post-Award Conference and Initial award IDIQ Requirements

As a result of an ALEP IDIQ award, the Government will host a post-award conference at which further program information will be discussed and awardees shall provide a detailed overview of their proposed program management, administrative, financial and technical resources, as well as, all required materials to accomplish the tasks defined in this SOW.

3.0 Delivery Order Overview and Requirements

Section 3 provide an overview of elements that will be addressed in future DOs. The individual DO Fair Opportunity Proposal Requests (FOPR) IAW FAR 16.505, SOW, and performance specification will stipulate the requirements and details of the following sections.

The contractor shall provide the program management, administration, financial and technical resources, required materials, and also facilitate and be responsible for the planning, execution, and control to accomplish the tasks and sub-tasks outlined in this SOW. Each individual DO will provide detailed requirements. The following paragraphs provide an overview of the deliveries that fall under ALEP IDIQ, but are not limited to the following variants.

3.1 Day Variant Ballistic Spectacles

This variant primarily fills the capability gap for aircrew identified as facing a day ballistic threat, primarily rotary-wing, tilt-rotor, and special operations aircraft.

3.2 Night Variant Ballistic Spectacles

This variant fills the capability gap for aircrew identified as facing a night ballistic threat, primarily rotary-wing, tilt-rotor, and special operations aircraft.

3.3 Day Variant Basic Spectacles

This variant will update the current ALEP Block 2 spectacles and may leverage off existing Block 2 frames. Variant will be used across many platforms, however primarily with users of HMDs other than JHMCS.

3.4 Night Variant Basic Spectacles

This variant will update the current ALEP Block 2 spectacles, and may leverage off existing Block 2 frames, and integrate with night vision devices. Variant will be used across many platforms.

3.5 Day Variant HGU-55/P Visor

This variant will incorporate LEP technology into a visor configuration for HGU-55/P users, primarily fixed-wing aircraft. Must integrate with JSAM TA.

3.6 Day Variant HGU-56/P Visor

This variant will incorporate LEP technology into a visor configuration for HGU-56/P users, primarily rotary-wing aircraft. Must integrate with JSAM RW.

3.7 Day Variant Joint Helmet Mounted Cueing System (JHMCS)

This variant will incorporate LEP technology into a configuration for tactical aircraft aircrew that use JHMCS.

3.8 Day Variant Joint Strategic Air Mask for Strategic Aircraft (JSAM SA) This variant will incorporate LEP technology into a format that affixes to the JSAM SA mask.

4.0 Program Management and Control

4.1 Program Management

The contractor shall provide support of program management and engineering functions in the acquisition and development of ALEP. This shall include, but not be limited to, evaluation of system designs, documentation reviews, participation in design and management reviews, cost/schedule status tracking, and configuration and data management activities, as specified in individual DOs.

The contractor shall provide program management support to the ALEP Program. The contractor shall be responsible for meeting program performance/technical, cost and schedule requirements. The contractor shall provide direct management to test activities including pre-qualification, DT&E, and First Article Test (FAT) efforts. The contractor shall co-chair Risk Management activities with the Government ALEP Program Office. As a prime, the contractor is also responsible for subcontract/supplier oversight to subcontractors and key suppliers.

As specified in individual DOs, the contractor shall proactively manage the program through use of the integrated Contractor Work Breakdown Structure (CWBS), Contractor Statement of Work (CSOW), and Integrated Master Schedule. The contractor shall proactively monitor and maintain data, report at meetings, and provide responses to government inquiries. Data includes:

Integrated Master Schedule Technical Performance Measurement metrics Performance, cost, schedule, and manufacturing risks Quality assurance practices for system design, development, manufacturing, production, and deployment

4.2 Quality Assurance Management

As specified in individual DOs, the contractor shall provide Quality Assurance (QA) Management to direct and monitor the QA activities required. The contractor’s QA Management shall insure the ALEP device Quality Plan is generated, released and complied with, plus provide internal audit of the program.

4.3 Program Support - Program Planning and Control

As specified in individual DOs, the contractor shall provide program planning and control support to collect and track cost and schedule performance potentially including earned value management system support. Support shall include subcontract cost and schedule performance.

The contractor shall provide at a minimum Contract Performance Report and Contract Funds Status Report as required by the DO.

4.4 Security Management

The contractor shall execute its approved comprehensive Program Security Plan, defined in the Program Protection Plan (PPP). The PPP shall be submitted for Government approval prior to the Preliminary Design Review (PDR) for each DO. They shall assign a Security Officer who shall be responsible for management of all security aspects of the DO.

4.5 Program Security

The security requirements listed on the contract DD-254 - DoD Contract Security Classification Specification, addresses the general security requirements to participate in the ALEP IDIQ. All future ALEP DOs will be issued with a DD-254 tailored and issued specifically for the individual delivery. ALEP DO security requirements may vary depending upon performance specifications. Individual DOs could require contractor to access; UNCLASSIFIED (U) and up to SECRET (S). Individual deliveries may require contractor access to SIPRNET and other secure communication equipment. Regardless of the delivery specific requirements, each DD- 254 will address the specific security requirements for that DO. The contractor shall be responsible for the ALEP security in accordance with (IAW) the contract DD-254, as well as, each individual DO DD-254. In the event of a conflict between requirements in the DD-254 and this SOW, the DD-254 shall take precedence. The contractor shall create and maintain operating procedures IAW the DoD and AF security disciplines listed below. The contractor shall protect For Official Use Only (FOUO) and classified material from unauthorized access. The contractor shall report all security violations and/or anomalies to the Government program office no later than the morning of the next business day.

DCID 6/9 DOD 5200.1-R AFI 31-401 AFI 33-201 Volume 1

DCID 6/4 DOD 5200.2-R AFI 31-501 AFI 33-210

DODI 8510.01 DOD 5220.22-M AFI 31-601 JAFAN 6/3

DODI 8500.2 DOD 5220.22-R AFI 33-200 JAFAN 6/9

4.6 Acquisition Systems Protection

The contractor shall ensure security requirements are integrated into all aspects of the ALEP program execution as required by DoD Directive 5000.01, The Defense Acquisition System, DoD Instruction 5000.02, Operation of the Defense Acquisition System, and DoD Instruction 5200.39, Critical Program Information (CPI) Protection within the Department of Defense. The contractor shall establish, implement, and maintain these requirements IAW the provisions of DoD Manual 5200.1, the Acquisition Systems Protection Program, and the ALEP PPP.

4.7 Information Security

The contractor shall execute the ALEP IDIQ and subsequent DOs IAW DoD 5220-22-M, National Industrial Security Program Operating Manual (NISPOM), and DoD Instruction 5200.01, DoD Information Security Program and Protection of Sensitive Compartmented Information and other applicable instructions/regulations as indicated by the DD-254. The contractor shall protect classified materials and data received or generated as a part of the execution of this contract. Classification requirements are established in the current ALEP Security Classification Guide (SCG).

4.8 Technology Control

The contractor shall implement protection standards and guidance described in DoD Manual 200.1, The Acquisition Systems Protection Program, and Chapter 5, to prevent foreign intelligence collection and/or the unauthorized disclosure of information governed by the International Traffic in Arms Regulation (ITAR) and/or the Export Administration Regulation (EAR) during ALEP execution. No ALEP program information is releasable to any foreign person, company or country unless it has been properly vetted through an appropriate Foreign Disclosure Office (FDO) and authorized for release. DOs issued under ALEP IDIQ may require the awardees to address and/or comply with applicable PPP. Accordingly, some DOs may require the awardees to provide a Program Protection Implementation Plan (PPIP).

4.9 Industrial Security

The contractor shall comply with the requirements of the National Industrial Security Program Operating Manual (NISPOM), DoD 5200.22-M.

4.10 Personnel Security

The contractor shall comply with the requirements of the National Industrial Security Program Operating Manual (NISPOM), DoD 5200.22-M. The contractor shall maintain proper security clearances for its personnel.

4.11 Operational Security (OPSEC)

OPSEC requirements are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the lifecycle of the contract.

4.12 Documentation

The contractor shall develop, document, maintain, and deliver product baselines/drawings for purposes of maintenance and re-procurement, as specified in individual DOs. The standard Government electronic platform consists of the PC version of Microsoft Office Suite products, Adobe Product line and Adobe Acrobat XI Pro. The standard electronic mailing system is the MS Outlook, and the common project management software tool is MS Project.

4.13 Cost, Schedule, and Performance Control

As specified in individual DOs, the contractor shall maintain a financial management program that allows effective tracking of each DO’s schedule and cost. The scheduling management system shall provide for all specific work compatible with contract milestones and meaningful in terms of the technical and support requirements of the contract. The contractor shall interface scheduling with other planning and control systems to the extent necessary for measurement and evaluation of contract status.

4.14 Reviews and Meetings

As specified in individual DOs, the contractor shall plan for and participate (both Program and Technical Management support) in reviews, conferences, meetings, and teleconferences, e.g. test meetings, working group meetings, System Readiness Review, Integrated Baseline Review, Program Design Review, Critical Design Review, Design Readiness Review, Functional Configuration Audit, and Production Readiness Review. The contractor may convene Technical Interchange Meetings (TIM), between design reviews if mutually agreed upon by the contractor and Government. The contractor shall support these meetings at a location and frequency mutually agreed upon by the contractor and Government.

4.15 Monthly Status Report (MSR)

The contractor shall provide an MSR that describes the status of each DO. The MSR shall include a summary of all work accomplished-to-date, all program activities for the period, a forecast of work to be accomplished during the upcoming six months, all work outstanding, and a schedule of all deliverables. The contractor shall identify actions being taken to correct all schedule deficiencies. All changes from previous MSRs shall be highlighted and explained. The contractor shall report any problems requiring immediate action by the Government using the most expeditious means (phone or e-mail) and shall document the problem in the MSR. The contractor shall identify and report on maintenance trends and breakage data and provide recommendations to address those trends when applicable.

4.16 Subcontract Management

The contractor shall develop and maintain a subcontract management process as specified in individual DOs.

4.17 Risk Analysis & Management

4.17.1 Risk Management

The contractor shall have a focused risk management approach in support of Risk Assessment, Risk Analysis and Risk Mitigation in accordance with applicable sections of MIL-STD-882E.

The contractor’s Risk Manager shall prepare an internal risk process to ensure risks are identified, mitigated, and reviewed. Initial assessment shall be conducted and shall continue to modify this risk assessment to include potential risk issues that are specific to the contractor design approach as identified. The contractor shall proactively manage program risks (e.g.

performance, cost, schedule and manufacturing risks) using an integrated management approach of risk planning, risk assessment, risk handling and risk monitoring. The contractor shall address risk mitigation as an ongoing activity from design inception through SVR. The contractor shall track, monitor and maintain risk status for reporting at meetings and in response to government inquiries. The contractor internal risk reviews shall be conducted on a monthly basis and results communicated to the Government in the MSR.

4.17.2 Risk Assessments

Risk assessments shall be presented at Design/Verification Reviews and Formal Technical Interchange Meetings, and as required by the Government.

5.0 Systems Engineering and Design

The contractor shall implement systems engineering processes to ensure the integration of program requirements into the ALEP variants. Systems engineering disciplines shall include, but not be limited to, reliability/maintainability engineering, test engineering, producibility engineering, supportability, safety engineering, hazardous materials management, and the creation and maintenance of technical data, and other documentation associated therewith, as specified in individual DOs. The contractor shall comply with Government and/or industry guidelines. Such standards may govern the development and deployment of ALEP. Such guidelines shall take the form of specifications, standards, handbooks, etc., as specified herein or in individual DOs.

As specified in individual DOs, the contractor shall complete the design, fabricate, qualify, manufacture, and produce tasks for an ALEP Block 3 system that meets the Key Performance Parameters (KPP) and Key System Attributes (KSAs) thresholds and objectives as practicable within cost and scheduled constraints. The Performance Specification (PS) and PS annex shall be updated prior to the respective variant Critical Design Reviews (CDR) to capture essential changes/modifications to requirements, based upon insight gathered during design trade studies and operational filed evaluations. The "final" ALEP solution(s) shall meet the requirements as delineated in the individual DOs.

The contractor(s) may be tasked to provide studies and analysis to support design concept and prototype development. Additionally, the contractor shall produce Rough Orders of Magnitude (ROMs) for various system options and assist in accident/incident investigations.

5.1 Systems Engineering and Design Management

As specified in individual DOs, the contractor shall be responsible for ensuring the compatibility, interoperability and integration of all ALEP functional and physical interfaces. The contractor shall ensure a safe, suitable and effective ALEP system is developed. The contractor shall participate in all Government-formed Working Groups and conduct Design and Verification Reviews.

5.1.1 Configuration Management (CM)

The contractor shall develop and implement a CM program and document it in a Configuration Management Plan (CMP) that addresses the entire lifecycle. The CMP shall implement the contractor’s configuration management functions and their underlying principles throughout the product’s life cycle using EAI-649-1 as a guide.

The contractor shall also implement existing data management procedures for the preparation, quality control, administration and delivery of data required by the CDRL. Additionally, they shall have a documented process for configuration identification (CI) and configuration documentation to be used to define the functional allocated and product baselines for hardware which shall provide to the Government for approval. The contractor shall ensure product configuration changes and variances are documented, coordinated, evaluated, dispositioned, and recorded in a CM/status accounting system and the released/approved changes are incorporated into all product configuration documentation.

The Contractor shall use an Engineering Change Proposal (ECP), with sufficient data attached, to document changes to the specification, drawings or other baseline documentation using DD Form 1692 or equivalent changes to the Government’s requirements and shall be approved by the Government. The contractor shall submit a Contract Change Proposal (CCP) with data necessary to propose, control, and approve non-baseline changes to the contract.

The Contractor shall maintain a current listing of all CDRL and non-CDRL data generated in performance of the contract in a Data Accession List (DAL). All documentation and other data generated in performance of this program shall be made available to the Government. The Contractor shall provide a central point of contact for Data Management who shall ensure contract data compliance with the contract. The Contractor shall support and participate in the Functional Configuration Audit (FCA) and Physical Configuration Audit (PCA) on production representative units. The Contractor shall prepare an agenda for each audit, and ensure that it lists the information required to conduct the audit, as well as the availability of the items required in accordance with the IMS.

The Contractor shall investigate Deficiency Reports (DRs) as required. The Contractor shall provide a coordinator and the necessary staff for the receipt, status control, conduct, preparation, and transmittal of engineering/investigative analysis and recommended solutions to deficiency reports as described in TO 00-35D-54, USAF Deficiency Reporting and Investigating System.

5.1.2 Product Baseline Configuration Identification

The contractor shall document, update, and maintain the product baselines for the ALEP system and provide them to the government. The product baseline shall be in the form of item, process specifications, engineering drawings, and other technical documentation comprising a complete technical data package. The product baseline shall prescribe the necessary physical and functional characteristics of the ALEP device and the verifications demonstrating required performance.

5.1.3 Change Management

The contractor shall accomplish timely updates to all device baselines to maintain a current, common, validated system configuration. The contractor shall implement, maintain, and update a CM system to effectively support change activity across all system components.

Engineering Change Proposals (ECP): The contractor shall prepare and submit ECPs as requested by the contracting officer (CO) when changes to the requirements specifications are required.

Contract Change Proposals (CCP): The contractor shall prepare and submit a CCP when proposing a change to the contract not impacting the requirements specifications.

Requests for Deviation: The contractor shall prepare and submit a Request for Deviation if it seeks a deviation from the requirements specifications or their appendices.

5.1.4 Technical Data Package (TDP)

The contractor shall document, maintain, update, and deliver the engineering data baseline of each ALEP device and all associated support items for all modifications performed. The technical data package shall consist of hardware specifications, technical publications, test procedures, engineering drawings, baseline documentation, and all technical data and other related documentation. The TDP shall include existing data, contractor developed and/or obtained from associated contractors and Government furnished data (if applicable). The documentation (drawings, manuals etc.) shall be delivered in an editable electronic format, using commercial software tools.

5.1.5 System Integration

The contractor shall integrate system components, as specified in individual DOs.

5.1.6 Interoperability

The contractor shall support interoperability between aircraft and Aircrew Flight Equipment (AFE). Each individual DO will provide detailed interoperability requirements.

5.1.7 Technology Insertion

As specified in individual DOs, the contractor shall upgrade ALEP components due to parts obsolescence or technological advances.

5.2 Systems Safety

The contractor shall implement a systems safety engineering approach consistent with the Military Standard (MIL-STD)-882E to identify, analyze and mitigate safety hazards. Hazard mitigation includes designing out the hazard, incorporating safety features, and/or placing warnings/cautions in the technical manuals. They shall document the analysis with a System Safety Hazard Analysis Report and a Health Hazard Assessment Report to summarize the results of the hazard analysis for each variant as stipulated in the DO. They shall all ensure sound systems engineering design practices are in place to document a safety hazard analysis and health hazard assessment ensuring the ALEP system is operationally safe, suitable and effective for use in the user's operational environment. The contractor shall provide updates to the SSHAR and HHAR as a result of any changes that affect system safety.

5.2.1 Environment, Safety, and Occupational Health (ESOH)

As specified in individual DOs, the contractor shall execute, maintain, and update a documented system safety program in accordance with MIL-STD-882E. The contractor shall document their approach for analyzing, eliminating or minimizing hazards during all phases of the program.

The contractor shall have the responsibility of identifying, analyzing, and mitigating all ESOH hazards to minimum acceptable levels in accordance with MIL-STD-882E criteria. The contractor shall brief ESOH-related mishaps and deficiency reports and their associated risk status to the Government at program and technical reviews. For ESOH, particularly safety, issues that are identified during operation or maintenance, the contractor shall notify the using organization and the contracting officer immediately. Designs shall comply with ESOH laws and regulations and the Air Force Occupational Safety and Health (AFOSH) standards applicable to minimize threats to the environment and minimize safety and health hazards to all personnel using or maintaining the equipment. The contractor shall manage Hazardous Materials, including those embedded in the system or used during operation or maintenance, as an element of the Systems Engineering process. The ALEP device shall not generate or use Class I or Class II Ozone Depleting Substances during operation or disposal.

5.3 Critical Design Activities

As specified in individual DOs, the contractor shall provide engineering design concepts and prototype development. Upon successful completion of Preliminary Design Review (PDR), the contractor team composed of representative(s) from Program Management, Engineering, Production, Quality Assurance, Procurement, including subcontractors and/or others as required;

shall complete the design analysis and produce the final ALEP variant configuration design(s).

Based upon its mission centric approach, the contractor shall complete the minimum number of designs/variants to meet combat, operational, and training missions along with visual and physical compatibility to aircraft cockpits, outside environments and life support equipment including helmet mounted devices, night vision devices, and CBRN equipment. The contractor shall maximum the use of available technologies and hardware. As specified in individual DOs , they shall complete development, test, and evaluate variants in lab and field conditions, verify optical quality, complete LEP designs and verify optical performance. Spectacle variants that do not use the Randolph P-2 Frame (ALEP Block 2 frame) shall be fabricated with both clear lenses and with LEP designs for evaluation at operational sites as frame, lens, and LEP designs are iterated and finalized. The process shall be conducted to consolidate variant design, development and test activities to the maximum extent possible. The team shall complete this process by verifying the design from key suppliers and the contractor is producible. Designs shall be fabricated and tested including field evaluation. The contractor shall implement its Failure Review Analysis and Corrective Action System (FRACAS) process for any failures encountered during field evaluation, commence redesign activities and fabricate additional prototypes. The final designs sustained by analysis and/or fabrication measurements shall be presented at the CDR for Government approval.

The following paragraphs provide an overview of the design concepts and prototype development deliveries that may be required under ALEP IDIQ. Each individual DO will provide detailed design concepts and prototype development requirements.

5.3.1 Technology Assessments and Forecasts

As specified in individual DOs, the contractor shall provide evaluation and determination of technologies that have, or may have, an impact on the evolution of the LEP industry and ALEP applications.

5.3.2 Spectral Analyses

As specified in individual DOs, the contractor may provide analysis of gathered aircraft cockpit spectral data for design assessments.

5.3.3 Preliminary Design Review

As specified in individual DOs, the contractor shall at a minimum present preliminary designs, analysis or prototypes, and initial presentations of TPM metrics. Required presentations at all formal reviews include presentations of the Integrated Master Schedule. TPM metrics, performance, cost, schedule and manufacturing risks, Quality Assurance (QA) practices for system design, development, manufacturing; plus production and deployment at the CDR.

5.3.4 Technical Performance Measurement (TPM) Approach

The contractor shall implement a TPM process that projects the probable performance of selected technical parameters over a period of time, records the actual performance of the technical parameter, and compare actual versus projected performance to assist in decision making. The contractor shall establish an initial TPM metric for each of the KPPs and KSAs in the requirements matrix (ref doc)

5.3.5 Critical Design Review

As specified in individual DOs, the contractor shall at a minimum present final designs, pre- DT&E test results, pre-DT&E prototypes and required presentations. Required presentations at all formal reviews include presentations of the Integrated Master Schedule, TPM metrics, performance, cost, schedule and manufacturing risks, Quality Assurance (QA) practices for system design, development, manufacturing; plus production and deployment at the CDR.

Meeting deliverables shall include submittal of Conference Agenda, presentations, Conference Minutes, and closure of all assigned action items.

5.3.6 Critical Design CDRLs

As specified in individual DOs, the contractor shall prepare and submit the following required minimum data items prior to CDR. System Safety Hazard Analysis, Mishap Risk Assessment, Performance Specification, and DT&E Test Plan, and shall be submitted as IAW the contract.

5.4 IDIQ Data Rights

All products developed under DOs resulting from this basic IDIQ contract shall be considered Government work and shall have no license encumbrances. Data Rights will be provided in the basic IDIQ contract and identified as an individual DO. Unless the Contractor has expressed a claim to providing data to the Government with less than unlimited data rights, the Government will assume unlimited data rights in accordance with DFARS clause 252.227-7013.

6.0 Test and Evaluation (T&E)

As further delineated in individual DOs, test and evaluation programs shall be established under the guidelines of the ALEP Block 3 Test and Evaluation Master Plan (TEMP), which will help ensure successful completion of operational testing in support of full-rate production. The following paragraphs provide an overview of the contractor test and evaluation deliveries that are required under ALEP IDIQ. Each individual DO shall provide detailed qualification and test requirements.

6.1 T&E Management

As specified in individual DOs, the contractor shall provide management support to the T&E process. Responsibilities may include developing the System Definition Document, DT&E System Test & Evaluation Plan (e.g. includes test plans, test procedures, and operationally relevant test scenarios) for aircraft compatibility testing, in conjunction with the ALEP Block 3 ITT. Also responsible for supporting and insuring successful coordinating activities for conducting integration T&E for aircraft identified on the final aircraft compatibility list. The contractor will provide liaison with various T&E organizations in support of program and technical reviews, test events, and other activities as deemed necessary.

6.1.1 Test Planning

As specified in individual DOs, the contractor shall accomplish test planning activities. Test planning shall include, but not be limited to, the development of test plans, test and evaluation master plans, test procedures and instructions, test discrepancy tracking, and organization of and participation in test planning working groups. The contents of test documents shall require concurrence from the Government.

6.1.2 Test Team Support (Planning and Working Groups)

The contractor shall form a test support team and foster a test environment to assist in planning, execution, and reporting testing activities is support of development and/or operational testing.

The contractor shall participate fully in a Government-formed Integrated Test Team (ITT). The contractor shall support the ITT in development of a Test and Evaluation Plan. The contractor shall perform all required testing of ALEP device performance, in accordance with the Performance Specification. The contractor shall support Government efforts to integrate operational T&E with developmental T&E to develop a seamless T&E approach. The contractor shall further support T&E activities through participation in working groups. The contractor may conduct early field-testing of ALEP devices by visiting multiple locations and performing human factors measurements, fittings of candidate devices and conducting LSE/aircraft integration test activities. Visits of multiple locations may include trips to manufacturers/suppliers of JHMCS, JSAM and NVG systems, as required. The contractor shall employ adequate resources (e.g. cost, schedule and personnel) for multiple trips to collect sufficient compatibility/integration data for design and system qualification for each aircraft platform. With the agreement of the Government regarding scope and depth, the contractor may assume full systems engineering and integration responsibility for all aspects of ALEP device DT&E, including conducting and directing all test and evaluation required for integration of ALEP onto aircraft platforms and insure compatibility with LSE.

6.1.3 Test Readiness Review (TRR)

Prior to commencement of DT&E, the contractor shall conduct a TRR for each ALEP device at which time test objectives, procedures for test conduct and resources shall be presented and discussed. Build documentation including drawings and DT&E test devices shall be able to confirm compliance to ALEP requirements. Meeting deliverables shall include submittal of Conference Agenda, presentations, Conference Minutes, and closure of all assigned action items.

6.1.4 Pre-Developmental Test & Evaluation (P-DT&E) Testing

As specified in individual DOs, final, pre-CDR prototypes of each ALEP device will be fabricated and evaluated for compliance to requirements in a lab scenario. Initial build documentation shall be revised as prototypes are finalized and build documentation released through the formal configuration management process. Prototypes shall be tested in accordance with the contractor’s Pre-Developmental Test and Evaluation Plan. Testing shall include laboratory tests and user evaluations and will be performed to verify requirement attainment. P- DT&E testing will be conducted as required to verify design performance data in support of CDR and risk mitigation efforts. This test effort shall include risk reduction component testing, measurements of eye protection performance, evaluation/demonstration of performance including design environmental performance, fit, physical coverage, and further evaluate human factors performance, e.g. visual compatibility and Life Support Equipment (LSE) compatibility.

The contractor shall employ a sound and effective systems engineering approach that develops, qualifies, manufactures, and deploys ALEP systems solution(s) that satisfies requirements. The contractor shall comply with its FRACAS by notifying the Government of failures, providing failure analysis results, development and verification of corrective action. The contractor shall employ adequate resources (e.g. cost, schedule, and personnel) for multiple trips using initial prototype devices to collect compatibility integration data for design and system qualification.

6.1.5 P-DT&E Test Results

Tests data shall be analyzed and FRACAS performed if anomalies or failures are noted. All P- DT&E results shall be presented at CDR by the contractor.

6.1.6 DT&E Testing

The contractor shall support the ground evaluation testing and suitability evaluation of the ALEP designs in the DT&E testing planned by the ITT. The contractor shall deliver approximately 50 of each ALEP variant for test activities (amount determined in DO). Quantity required shall be no more than needed to complete test activities including test by similarity as documented in the DT&E Test Plan. They shall conduct test activities at aircraft integration sites to be selected by the ITT. Test activities shall include appropriate aircraft platforms and missions to verify mission-centric ALEP system approach. Multiple DT&E activities shall be planned and conducted by variant, but shall be combined as much as possible to minimize number of tests.

6.1.7 DT&E Test Results

Tests data shall be analyzed and FRACAS performed if anomalies or failures are noted. Results of the DT&E effort, including actions taken resulting in the mitigation or correction of anomalies and failures, shall be summarized in the Final Qualification Test Report deliverable prior to System Verification Review (SVR). Submission of the Training Program and Final Production Plan and Schedule shall also be made prior to SVR as required. All DT&E results shall be presented at SVR by the contractor. Meeting deliverables shall include submittal of Conference Agenda, presentations, Conference Minutes, and closure of all assigned action items.

6.1.8 System Verification Review (SVR)

The contractor shall present DT&E test results, resolution for any anomalies or failures, as required and completion of design configuration control to ensure that the ALEP variants meet the verification and qualification criteria. They shall confirm completeness of system verification testing, completeness of integrated logistics support, production, training, and deployment planning as developed and maintained in the SEI IPT and the ILS Working Group (ILSWG), AIWG, ICWG and TPWG. The draft ALEP Repair Parts Recommendations document is delivered prior to SVR as part of the ILSWG preparation for the review. Finally, the SVR process reviews and approves all design drawings as appropriate for the ALEP device.

A Functional Configuration Audit (FCA) shall be conducted. Status of the Integrated Master Schedule (IMS), TPM metrics, performance, cost, schedule and manufacturing risks and Quality Assurance practices for system design, development, manufacturing, production and deployment will be presented. Meeting deliverables shall include submittal of Conference Agenda, presentations, Conference, and closure of all assigned action items.

6.1.9 First article test - LRIP Engineering Test Activities

The contractor shall develop and submit the ALEP Acceptance Test Procedure – FAT and Production Acceptance, to include the schedule, 45 days in advance of FAT. The contractor shall plan and conduct the First Article Test effort IAW the requirements of the ALEP performance specifications. They shall conduct the PCA prior to commencement of FAT. The contractor shall provide the complete ALEP system at PCA including production-representative Repair Kits, if applicable. The contractor shall conduct FAT and PCA with production units fabricated using production processes, production drawings, work instructions, tooling and equipment that will be used during FRP. However, a fully compliant production representative unit from the System Development and Demonstration (SDD), producibility demonstration is acceptable for destructive type tests. The contractor shall test as required and ensure all system safety hazards/risks have been fully mitigated to the greatest extent possible for the production ALEP System. They shall document the results of First Article testing in the First Article Test Report. Also, they shall provide status of LRIP testing activities, test data and results during the weekly telecons and in the monthly Status Reports. The contractor shall submit Engineering Change Proposals for any design changes that occur after PCA.

6.1.10 Operational Test Support

The contractor shall provide support to the Government-led ALEP operational test activity as identified by the Government. If anomalies or failures are noted, test data shall be analyzed and FRACAS performed.

7.0 Fabrication and Production

7.1 Fabrication and Production Management & Support

As specified in individual DOs, the contractor shall continue to provide management support to the pre-production fabrication activities required to prepare the ALEP design and build of required number of prototypes of each variant in support of planned T&E activities. The contractor shall employ a sound and effective systems engineering approach that develops, qualifies, manufactures, and deploys an ALEP system solution(s) that satisfies customer requirements. The contractor shall generate and submit Design-to-Cost/Life Cycle Cost/Variance Analysis, Production Plan and Schedule (Draft and Final) and Environmental Health & Safety Plan for Production Readiness Review. The contractor shall provide relevant updates on the production status at all program reviews.

7.1.1 Low Rate Initial Production (LRIP) Manufacturing Management The contractor shall provide management support to the LRIP effort. The support shall include oversight of the fabrication and test in support of LRIP. Manufacturing management shall ensure data from production yields are provided for reporting to the Human Systems Program Office during weekly telecons, and in the MSRs and provide support to the Program Office for preparing the MRA

7.1.2 Supplier Management

The contractor shall continue manage its suppliers closely. A comprehensive list of all materials utilized by the ALEP device shall be finalized. Specific attention shall be given to dye, lens and frame suppliers to ensure complaint key supplies can be procured in a timely fashion and at an affordable price. The contractor should visit/audit suppliers, conduct cost/schedule status meetings/telecons and risk reviews meeting/te1econs to verify compliance with requirements, to confirm no change in processes or configurations and endure product is available when required.

7.1.3 Procurement of Material & Engineering Efforts

The contractor shall work with key suppliers to complete engineering tasks in support of fabrication and production. Material specifications shall be revised as needed to insure compliant product is received consistently from suppliers and to reflect improvements or changes as the program progresses. The contractor shall procure materials, supplies and components required for LRIP manufacturing of ALEP LRIP devices.

7.1.4 Procure Material - Material Qualification

Material procurement for ALEP devices shall be from qualified suppliers and available when needed. Agreed upon lead times shall be documented and scheduled in the contractor’s pre-production fabrication and production planning.

7.1.5 Process Development & Qualification

The contractor shall employ sound and effective quality assurance practices for system design, development, manufacturing/production and deployment to ensure the ALEP system(s) is operationally safe, suitable and effective.