DRAFT_-_JBADS_PWS_May_2017.pdf

DRAFT JBADS PWS 18 May 17

CONTRACT NUMBER: _____________________

CONTRACTOR: ___________________________

TASK ORDER NUMBER: ___________________

DRAFT PERFORMANCE WORK STATEMENT

TITLE: JOINT BIOLOGICAL AGENT DECONTAMINATION SYSTEM (JBADS)

1.0 SCOPE. This Performance Work Statement (PWS) describes the Contractor activities in support of the Engineering and Manufacturing Development (EMD) phase of the Joint Biological Agent Decontamination System (JBADS) program. There are contract Options for Production, Contractor Sustainment and Operational Readiness, Future Capabilities Analysis, System Deployment, System Operation, and Technical Data Package requirements.

1.1 BACKGROUND. The JBADS is an Acquisition Category III, Joint Program with participation from the United States Air Force. The Joint Program Executive Office for Chemical and Biological Defense (JPEO-CBD) is the Milestone Decision Authority (MDA). The Joint Project Manager for Protection (JPM P) manages the effort and the JBADS Product Management Office (PMO) executes the program.

1.1.1 The JBADS program ented the acquisition cycle at Milestone (MS) B in May 2017 and immediately began execution of EMD phase activities. The JBADS program was able to enter at MS B due to a Technology Readiness Level (TRL) assessment of 7 provided by the Defense Threat Reduction Agency (DTRA). DTRA based that assessment on the JBADS Joint Capability Technology Demonstration (JCTD) conducted in 2014-2015 that demonstrated a 6-log biological decontamination capability using hot, humid air. To accomplish the decontamination, the JCTD system was composed of an aircraft enclosure, control module, and aircraft decontamination units, the latter comprised of blowers, heaters, humidifiers, and chillers connected to the aircraft enclosure via ducting. These were the components used in the JCTD to perform the decontamination process and are described for the purpose of providing background information only - the Government is not directing that the JBADS design must include or only be comprised of these components. The JBADS sought under this PWS must meet the requirements as detailed in the JBADS Performance Specification (PSpec) (Attachment 1).

1.1.2 At the conclusion of the JCTD desired improvements to the JBADS were identified as follows:

1.1.2.1 Aircraft enclosure must allow for safe ingress/egress of aircraft. [Note: The JCTD system structure was built in a conformal fashion around and above the aircraft.]

1.1.2.2 Provide ability for sequential and potentially sustained decontamination operations.

1.1.2.3 Eliminate the escape of hot humid air from the aircraft enclosure.

1.1.3 Following completion of the JCTD the Government initiated improvements to the aircraft enclosure design.

To date the Government has not built or verified functionality of the JBADS using this modified aircraft enclosure design.

1.2 OVERVIEW. During the base period of this contract, the Contractor shall build and verify a JBADS during the EMD phase then refurbish the JBADS for fielding. This JBADS will undergo Contractor Specification Testing (CST), Product Verification Testing (PVT-2), an Operational Assessment (OA), and Initial Operational Test and Evaluation (IOT&E). The JBADS may consist of an aircraft enclosure, aircraft decontamination units, and a control module. The JBADS under this contract must have the capability for aircraft to enter and exit (allow for 5 feet clearance on all sides of the aircraft), provide heat (170 degrees F +/- 5 degrees), and humidity (90% relative humidity +/- 5%) during decontamination, provide adequate control to ensure no condensation forms within the aircraft enclosure or on the aircraft surfaces, and provide real-time monitoring.

1.3 OBJECTIVE: The objective of the JBADS is to provide the United States (US) Air Force Air Mobility Command (AMC) with the ability to decontaminate a U.S. Transportation Command (TRANSCOM) C-130 H/J/J- 30 model aircraft from biological warfare agents through the employment of hot, humid air to allow unrestricted worldwide use of the aircraft post-decontamination.

2.0 APPLICABLE DOCUMENTS. The following documents form a part of this PWS to the extent specified herein. The most recent revision of the referenced document at the time of award shall be used unless otherwise stated. In the event of conflict between the applicable documents and this PWS, the PWS shall take precedence.

Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained. For the purposes of this PWS, “Required” means that the requirements contained in the directly cited document are contractually applicable to the task order. All second tier and below references cited in mandatory compliance documents shall be considered as guidance only. The term “For Guidance Only” means the document is not contractually binding and is provided for guidance and information only. Documents listed below are required unless otherwise stated and are provided at the noted web site or as appendices to this PWS.

2.1 MILITARY SPECIFICATIONS.

2.1.1 MIL-STD-882E System Safety, 11-May-2012

2.1.2 MIL-STD-130N(1) Identification Marking of U.S. Military Property, 16-Nov-2012

2.1.3 MIL-STD-1839D NOT 1 Calibration and Measurement Requirements, 19-Dec-2016

2.1.4 MIL-STD- 147E(1) Palletized Unit Loads, 23-Dec-2013

2.1.5 MIL-STD-2073-1E(1) Standard Practice for Military Packaging, 07-Jan-2011

2.1.6 MIL-STD-129R Military Marking for Shipment and Storage, 18-Feb-2014

2.1.7 MIL-STD-1839D Calibration and Measurement Requirements, 19-Dec-2016

2.1.8 MIL-STD-31000A Technical Data Packages

(The aforementioned documents are available from: http://quicksearch.dla.mil/)

2.2 MILITARY HANDBOOKS (FOR GUIDANCE ONLY).

2.2.1 MIL-STD-881C Work Breakdown Structures for Defense Materiel Items, 03-Oct-2011

2.2.2 MIL-HDBK-61A Configuration Management Guidance, 07-Feb-2001

2.2.3 MIL-HDBK-781A NOT 1 Reliability Test Methods, Plans, and Environments for Engineering

Development, Qualification, and Production, 30-Jan-2015

2.2.4 MIL HDBK-1839A Calibration and Measurement Requirements, 19-Dec-2016

(The aforementioned documents are available from: http://quicksearch.dla.mil/)

2.3 TECHNICAL MANUALS.

2.3.1 TO 00-20-14 Technical Manual, Air Force Metrology and Calibration Program, 30 Jun 2016

(The aforementioned documents are available from: http://www.wpafb.af.mi/afmetcal)

2.4 Federal Standards.

2.4.1 FED-STD-313E Material Safety Data, Transportation Data, and Disposal Data for Hazardous Materials Furnished to Government Activities, 01-Jul-2014

(This Federal Standard is available from: http://quicksearch.dla.mil/)

2.5 OTHER GOVERNMENT DOCUMENTS.

2.5.1 JBADS Performance Specification (Attachment 1)

2.5.2 JBADS Program Schedule (Attachment 2)

2.5.3 DoDI 5000.02 Operations of the Defense Acquisition System, 2 February 2017

(This DoDI is available from: http://www.dtic.mil/whs/directives/corres/pdf/500002_dodi_2015.pdf)

2.5.4 FAR 23.302 Federal Acquisition Regulation, Hazardous Material Identification and Material

Safety Data

2.5.5 FAR Clause 46.202-4 Federal Acquisition Regulation, Higher-Level Contract Quality Requirement, 25-Nov-2014

2.5.6 DFARS clauses 252.211-7003, 252.211-7007 Defense Federal Acquisition Regulation Supplement

2.5.7 AR 525-13 Army Regulation, Antiterrorism, 23-Apr-2012

2.5.8 AR 530-1 Army Regulation, Operations Security OPSEC Program, 25-Feb-2014

2.5.9 FAR 52.204-2 Federal Acquisition Regulation, Security Requirements

2.5.10 SD-22 Diminishing Manufacturing Sources and Material Shortages, 01-Jan-2016

2.5.11 Notional aircraft enclosure drawings (per Vendor request)

2.6 NON-GOVERNMENT (INDUSTRY) DOCUMENTS.

2.6.1 ASTM-D3951 Packaging, Commercial, 21-Dec-1990

(American Society for Testing and Materials (ASTM) documents is available from www.astm.org)

2.6.2 EIA-649-1 Configuration Management Requirements for Defense Contractors, 04-Mar-2015

(This document is available from http://www.techstreet.com)

2.6.3 ISO 17025 General Requirements for the Competence of Testing and Calibration

Laboratories, May-2005

2.6.4 National Institute of Standards Technology (NIST)

International Standards Organization (ISO) is available: http://www.iso.org/iso/catalogue_detail?csnumber=39883.)

3.0 REQUIREMENTS. In accordance with (IAW) the basic contract, the Contractor, as an independent Contractor and not as an agent of the Government, shall provide the resources necessary [except for Government Furnished Information (GFI)] [see Para 7.0] to perform the tasks described herein. The Contractor shall fabricate, package, deliver, prepare associated documentation and deliverables, and provide management, technical and field service support for the JBADS program IAW the quantities, packaging and delivery schedule requirements identified in the JBADS PSpec (Attachment 1) and JBADS Program Schedule (Attachment 2). In addition, the Contractor shall support and participate in technical reviews and audits including a Critical Design Review (CDR), Physical Configuration Audit (PCA), and Manufacturing Readiness Assessments (MRAs) IAW with this PWS, and shall prepare and deliver data in accordance with the Contract Data Requirements List (CDRL). The Government has the unilateral right to exercise all contract options described in this PWS.

3.1 ENGINEERING AND MANUFACTURING DEVELOPMENT (CLIN 0001)

3.1.1 Program Management. The Contractor shall establish and maintain program management practices throughout the period of performance. Program management practices shall provide visibility into the Contractors’ organization and techniques used in managing the program, including subcontractor and data management. The Contractor shall provide monthly Progress, Status and Management Reports IAW the CDRL. These reports shall be submitted using a Government approved Work Breakdown Structure (WBS) indenture level and shall include narrative progress, program issues, schedules and all required cost expenditures. For periods where more than one CLIN is active at the same time, all CLIN activity shall be reported in one coordinated set of reports.

(CDRL AA001) DI-MGMT-80368A, Status Report- tailored to remove schedule

3.1.2 Schedule Planning. The Contractor shall develop and maintain a schedule of program activities in accordance with CDRL AA002.

(CDRL AA002) DI-MGMT-81861A, Integrated Program Management Report (IPMR) for schedule only.

3.1.3 Contract Work Breakdown Structure. The Contractor shall maintain the Contract Work Breakdown Structure (CWBS) and dictionary using MIL-HDBK-881 for guidance only. The Contractor shall use the CWBS as the primary framework for contract planning, budgeting, and reporting of the cost, schedule and technical performance status to the Government. The Contractor shall update the CWBS during the execution of the contract.

3.1.4 Integrated Program Management Reporting. The Contractor shall report Earned Value Management data in accordance with the requirements stated herein and the Contract Performance Report (CPR). All reporting shall correspond to applicable CWBS elements. The Contractor shall reconcile the cost/schedule data elements in the Contract Funds Status Report (CFSR) with the CPR when these documents are submitted in the same month. The Contractor shall provide a reconciliation of the CFSR with CPR as an addendum to the CPR.

(CDRL AA0003) DI-MGMT-81466A, Contract Performance Report (CPR)

3.1.4.1 Application to Subcontractors. The Contractor shall flow-down the CPR requirement to subcontractors meeting applicable thresholds and/or assigned critical tasks. Subcontractor performance management information shall be integrated into the Contractor's CPR and other cost reports.

3.1.5 Meetings, Formal Reviews, Conferences, and Audits.

3.1.5.1 Contractor Responsibilities. The Contractor shall attend and support the meetings, formal reviews, conferences, and audits (hereinafter called "reviews"). The reviews shall be conducted at a time and place mutually agreed to, or via teleconference and/or virtual collaboration. The Contractor may be required to provide the Government with a proposed agenda or meeting presentation materials prior to reviews, unless specified otherwise in the detailed section pertaining to individual reviews. The Government reserves the right to cancel or postpone any review or to require any review to be scheduled at critical points during the period of performance. The Contractor shall provide minutes of reviews as required by the Government to include action item documentation, assignment of responsibility for completion and due dates shall be determined prior to adjournment of all reviews.

3.1.5.2 Start of Work Meeting. The Contractor shall host a Start of Work Meeting at a place mutually agreed to within 30 calendar days after order award. The purpose of the Start of Work Meeting is to achieve a clear and mutual understanding of contract requirements, terms, and conditions and identify and resolve potential or actual problems. The Start of Work Meeting also provides the opportunity for the Contractor to review their program management, quality, and technical approaches for meeting PWS, PSpec, and JBADS schedule requirements.

Additionally, the Contractor shall introduce and review the assignment of key personnel and program execution processes. It is the Government’s intent to conduct the CDR ninety (90) days after the Start of Work Meeting (see paragraph 3.1.6.1.1). The Contractor shall provide meeting minutes in accordance with the CDRL.

(CDRL AA004) DI-ADMN-81505, Report, Record of Meeting/Minutes

3.1.5.3 Bi-weekly Joint Program Team Telephone Conference (Telecon). On a routine basis (every two weeks at a minimum) the joint Contractor/Government team shall hold a telecom to discuss program status, schedule progress, and to address issues that may arise. The Contractor shall provide meeting minutes in accordance with the CDRL.

(CDRL AA004) DI-ADMN-81505, Report, Record of Meeting/Minutes

3.1.5.4 In-Process Review. In-Process Reviews (IPRs) will be held on a quarterly basis or on an as needed basis if problems arise, at a date and location [e.g., in person or by teleconference and Defense Collaboration Services] mutually agreed upon. The Contractor may assume one review will be held at Aberdeen Proving Ground, MD each year. The Government reserves the right to cancel any review or to require any review to be scheduled during the period of performance. The Contractor’s progress, management, technical, administrative, program status, funding, problem identification and resolutions shall be agenda items. Performance of each area shall be addressed. The Contractor shall provide meeting minutes in accordance with the CDRL.

(CDRL AA004) DI-ADMN-81505, Report, Record of Meeting/Minutes

3.1.6 Systems Engineering.

3.1.6.1 Technical Reviews. The Government will conduct Technical Reviews IAW the Department of Defense Instruction (DoDI) 5000.02.

3.1.6.1.1 Critical Design Review (CDR). The Contractor shall participate in a CDR to be held ninety (90) days after the Start of Work Meeting and have all studies, estimates, analyses, designs, and reports available for the Government to review at least 20 calendar days prior to the CDR. The initial product baseline upon successful completion of the CDR shall include “build-to” specifications for hardware (product, process, material specifications, engineering drawings, Safety Data Sheets (SDS), and other related data). The Contractor shall provide a detailed review of the hardware design for the JBADS and all data items required by the contract. The Contractor shall provide traceability that demonstrates the product design and configuration established at CDR fulfills the performance requirements of the JBADS, and present the methods used to verify and validate the performance. The Contractor shall present the results of internal analyses conducted on product composition and system hardware for Government assessment. Upon successful completion of the CDR the Initial Product Baseline for JBADS is established and the system shall be under Government configuration control.

(CDRL AA0005) DI-ADMN-81249B, Conference Agenda (CDRL AA0006) DI-ADMN-81373, Presentation Material (CDRL AA07) DI-ADMN-81505 Report, Record of Meeting/Minutes (CDR)

3.1.6.2 Manufacturing Readiness Assessment (MRA). The Contractor shall demonstrate the ability to attain a minimum Manufacturing Readiness Level (MRL) of eight (8) at the conclusion of EMD in support of Milestone C.

The manufacturer will be assessed for manufacturing readiness IAW the MRA Handbook by an independent Government sponsored team. Contractor completion of questionnaires (IAW the CDRL) and site visits to each of the primary manufacturing facilities by Government Representatives may be conducted to assess manufacturing readiness and risks. If the required MRL is not met, the Contractor shall prepare a manufacturing maturation plan (IAW the CDRL) to obtain the required MRL. In addition, the Contractor's quality management system shall conform to FAR Clause 46.202-4, Higher Level Quality Requirements, and shall ensure product conformation to specification and configuration management requirements. The Contractor shall make available all quality management documentation for the Government to review upon request.

(CDRL AA008) DI-QCIC-81722, Quality Program Plan (CDRL AA009) DI-MISC-80508B, Technical Report, Study/Services (Manufacturing Readiness Questionnaire) (CDRL AA0010) DI-SESS-81974, Assessment of Manufacturing Risk and Readiness

3.1.6.3 Reliability, Availability, and Maintainability Program. The Contractor shall maintain a comprehensive Reliability, Availability, and Maintainability (RAM) program for equipment and components to ensure the RAM standards set forth in the JBADS Performance Specification are being met. The design shall be monitored throughout the delivery order period of performance to identify and assess any changes that will impact reliability, availability or maintainability. The Contractor shall develop reliability analysis and predictions, to ensure compliance with the JBADS PSpec IAW the CDRL.

(CDRL AA011) DI-MISC-80508B Technical Reports – Studies/Services (Logistics Analysis)

3.1.6.4 Failure Reporting, Analysis, and Corrective Action System (FRACAS). The Contractor shall develop a closed loop failure reporting system, procedures for analysis of failures to determine the root cause, and documentation for recording corrective actions taken. The FRACAS shall include uniform failure reporting, failure analysis reports and corrective actions IAW the CDRL. All failures shall be subject to these requirements throughout testing under the task order. The Contractor shall administer a single FRACAS database to encompass in-house (testing) failure reporting, and provide the Government access to the database. All failures shall be reported to the Government for review; System operating time (Elapsed Time, where applicable) shall be identified for each failure occurrence and included in the FRACAS data structure. The Contractor shall assess the failure data for the identification of trends, defined as five or more failures of the same root cause, and identify those trends in the failure summary and analysis report.

(CDRL AA012) DI-SESS-81315B, Failure Analysis and Corrective Action Report (FACAR)

3.1.6.5 Procedures and Controls. The Contractor shall maintain procedures and controls to ensure products, obtained from suppliers, vendors and subcontractors meet RAM requirements as per the JBADS PSpec. The Contractor shall establish, implement, and maintain documented procedures to detect and/or preclude the use of substandard or counterfeit parts in the production process, and impose similar requirements on subcontractors and component vendors.

3.1.6.6 Open Systems Design. The Contractor shall use an open systems approach as the systems design strategy to:

(1) choose commercially supported specifications and standards for selected system interfaces (external, internal, functional and physical), products, practices, and tools; and (2) build open system architectures as the primary foundation in developing the proposed system and its elements. To the extent that open systems design is used, the Contractor shall identify the means for ensuring conformance to open systems standards and profiles throughout the development process. The Contractor shall report on the progress of this effort during the CDR (see 3.1.6.1.1).

3.1.6.7 Producibility. The Contractor shall apply and implement effective producibility principles throughout the EMD phase to ensure that the JBADS production units can be manufactured using the anticipated production facilities, equipment, materials, manpower, and processes. The producibility planning effort shall also maximize the ease of production control, quality control, tooling, and inspection. The Contractor shall report on the progress of this effort during the CDR (see 3.1.6.1.1).

3.1.7 Environment, Safety, and Occupational Health (ESOH).

3.1.7.1 Environmental Considerations. The Contractor shall provide information on the potential for adverse environmental impacts from the manufacturing, operation, maintenance, and disposal of the JBADS IAW the CDRL. This information will be used to assist the Government in making a preliminary National Environmental Policy Act (NEPA) decision and in the preparation of formal NEPA documents to support test events. Such environmental impacts include air, soil, wetlands, water, flora, fauna, endangered species, emissions and toxic waste resulting from system maintenance, operation, and disposal.

(CDRL AA013) DI-MISC-80508B, Technical Report, Study/Services (Environmental Analysis)

3.1.7.2 System Safety. The Contractor shall identify and evaluate environmental, safety, and health hazards, define risk levels, and establish a program that manages the probability and severity of all hazards associated with development, use, and disposal of the system IAW MIL-STD-882. Risks will be evaluated IAW MIL-STD-882 prior to exposing people, equipment, or the environment to known system related ESOH risks.

3.1.7.2.1 Safety Assessment. The Contractor shall perform and document a Safety Assessment to identify all safety features of the system design and to identify all hazards that may be present in the JBADS, including specific procedural controls and precautions that should be followed.

3.1.7.2.2 Safety Assessment Report (SAR). The Contractor shall provide a SAR IAW the CDRL that documents the Safety Assessment and clearly identifies risks of the JBADS. The SAR shall include a signed statement that all identified hazards have been eliminated or their associated risks controlled to acceptable levels and that the JBADS is ready to test, field, and operate.

(CDRL AA014) DI-SAFT-80102C, Safety Assessment Report (SAR)

3.1.7.3 Health Hazard Considerations. The Contractor shall mitigate health hazards that could be encountered during assembly, operation, disassembly and packaging, or as a result of storage. The Contractor shall provide a Health Hazard Assessment report IAW the CDRL that documents the health hazards associated with the JBADS and the mitigation measures used.

(CDRL AA015) DI-SAFT-80106C Health Hazard Assessment Report

3.1.7.4 Safety Data Sheets (SDS). The Contractor shall develop SDS on the JBADS.

3.1.8 Risk Management. The Contractor shall conduct a technical risk management assessment and report risks, analyses, and mitigation plans IAW the CDRL.

(CDRL A023) DI-MGMT-81809, Risk Management Report

3.1.9 Configuration Management.

3.1.9.1 Configuration Management (CM) Process. The Contractor shall maintain a CM process for the control of all documentation, media, materials, deliverables, components, elements, items, parts and external system interfaces representing or comprising the JBADS. The principles contained in EIA-649-1, and MIL-HDBK-61A provides guidance. The Contractor shall notify the Government of any changes, which affect the execution of the Contractor's CM Plan. CM Processs will be applied to the development, production, operations, sustainment, and disposal of Configuration Items (CIs).

3.1.9.1.1 Configuration Item Identification. The Contractor shall employ methods to uniquely identify CIs and associated documentation, such as specifications, drawings, manuals, plans, procedures, instructions, software media, and other configuration-related documents. A permanent record of configuration identification documentation will be maintained throughout the life cycle of the CI, from the initial configuration and continuing with configurations resulting in the incorporation of approved changes.

3.1.9.1.2 Configuration Status Accounting (CSA). The Contractor shall establish and maintain a CSA database, which represents the configuration of the JBADS. All baselines, changes and planned systems upgrades shall be documented in the Contractor’s CSA database. The Contractor’s CSA database shall permit acceptance of commercial product information; if requirements to report data outside of the Contractor’s CSA database or format exist, the information shall be delivered as a supplement. The Contractor’s CSA database shall reconcile any differences between the supplier information and Contractor practices to provide the Government with clear accountability of product information. Additionally, the CSA database shall provide a reliable source of configuration information to support JBADS activities, including program management, systems engineering, logistics support, and modification/maintenance actions. The Contractor’s CSA database shall be capable of providing CSA data in a digital format IAW the CDRL. The Contractor shall provide the Government access to this database.

(CDRL AA017) DI-SESS-81253C, Configuration Status Accounting Information

3.1.9.2 Configuration Management Meetings/Audits.

3.1.9.2.1 Physical Configuration Audit (PCA). A PCA shall be performed to verify the JBADS and its CIs are accurate, complete, compatible, and that the CI/Software CI has achieved the performance and functional characteristics defined in the configuration baseline. The Government and the Contractor shall conduct the PCA jointly, at a time and place mutually agreed to, with the Government chairing the audit. Configuration audits occur at the times appropriate to specific schedules for the design, development, and production of CIs. Audits include verification of CM data, Functional Configuration Audit (FCAs) and PCAs. The PCA shall verify that drawings and training materials reflect the "as-built" configuration of the system; accurate form, fit or function information is provided on control drawings for Non-developmental Item (NDI) and Commercial-off-the-shelf (COTS) items and confirms that drawings accurately represent the "as-built" production configuration. Whenever possible, the PCA shall be conducted incrementally, concurrent with system fabrication and assembly of the full rate system production units. The Contractor shall develop a configuration audit plan IAW the CDRL and provide the system to be audited, facilities, personnel, and documentation. The Contractor shall participate and assist the Government in the development of the PCA, using the guidelines contained in Section 8 of MIL-HDBK-61A. The Contractor shall document the results of the PCA after the audit and shall correct all audit discrepancies documented in the configuration audit summary reports IAW the CDRL. In the event the Government finds evidence the drawings and/or documents do not adequately represent the equipment, production shall cease until all discrepancies are corrected and the Government approves the configuration audit summary report. The product baseline will be established upon completion of the PCA and resolution of audit discrepancies. Once complete, the Contractor shall submit the findings of the PCA IAW the CDRL.

(CDRL AA018) DI-SESS-81646B, Configuration Audit Plan (Physical) (CDRL AA019) DI-CMAN-81022D, Configuration Audit Summary Report (Physical)

3.1.9.2.2 Product Drawings/Models and Associated Lists. The Contractor shall provide Product Drawings, Models, and Associated Lists to the Government IAW the CDRL in support of the PCA. These processes will result in a complete audit trail of decisions and design modifications and will comply with the recommendations and best practices delineated in ANSI/EIA-649A, National Consensus Standard for CM, as supplemented by MIL-HDBK- 61A, Military Handbook.

(CDRL AA020) DI-SESS-81000E, Product Drawings/Models and Associated Lists

3.1.9.3 Configuration Change Control. The Contractor shall implement configuration control methods and procedures to maintain the integrity and traceability of an established baseline. Changes to established baselines shall only be made after Government approval of Engineering Change Proposals (ECPs) and Request for Variances (RFVs) via the Configuration Control Board process. Sufficient supporting data to evaluate the proposed change, such as drawings, supplemental drawings, sketches, specifications, or manufacturer’s data sheets, shall be submitted with ECPs and RFVs. Changes shall be identified to the effected assembly serial number, or if not part of an assembly, to the effected equipment serial number. The Contractor’s configuration control process shall be available for Government review. Configuration control will begin after the initial product baseline is established, at the conclusion of CDR and after any applicable corrective action plans have been implemented.

3.1.9.3.1 Engineering Change Release System. The Contractor shall maintain an engineering release system and shall use the system to issue configuration documentation to functional activities (e.g. manufacturing, logistics, quality control, engineering, and test and evaluation) and to authorize the use of configuration documentation associated with an approved configuration. The Contractor shall maintain current and historical engineering release information for all configuration documentation for the JBADS. The Contractor shall submit an Engineering Release Record (ERR) to release new or revised configuration documentation IAW the CDRL. The Contractor shall ensure all Government approved ERR information and documentation is reflected in the CSA database.

(CDRL AA021) DI-CMAN-80463D, Engineering Release Record (ERR)

3.1.9.3.2 Engineering Change Proposal. ECPs shall be submitted by the Contractor IAW the CDRL, and shall be limited to those that are necessary or offer significant benefit to the Government. MIL-HDBK-61A provides guidance concerning the classification of ECPs. All ECPs (Class I and Class II) shall be submitted to the Government for approval.

(CDRL AA022) DI-CMAN-80639D, Engineering Change Proposal (ECP)

3.1.9.3.3 Notice of Revision (NOR). The Contractor shall generate and submit NOR (IAW the CDRL), concurrently with ECPs.

(CDRL AA023) DI-CMAN-80642D, Notice of Revision (NOR)

3.1.9.3.4 Request for Variances (RFVs). The Contractor shall process RFVs from current approved configuration documentation IAW the CDRL. Authorized deviations are a temporary departure from the requirements and do not constitute a change in an approved baseline. Submission of recurring deviations is discouraged and shall be minimized. Where it is determined that a change should be permanent, the Contractor shall process an ECP. MIL- HDBK-6A1 provides guidance concerning the classification of RFVs.

(CDRL AA024) DI-SESS-80640D, Request for Variance (RFV)

3.1.9.3.5 Notification of Changes to Commercial Equipment/Software. The Contractor shall submit notification to the Government when changes occur to COTS equipment or software that is being procured or fabricated by the Contractor, and the Government does not control the developer’s design.

(CDRL AA025) DI-MISC-80508B, Technical Report - Study/Services

3.1.10 Item Unique Identification (IUID). The Contractor shall provide specific IUID marking, as defined in MIL- STD-130N (1) and Defense Federal Acquisition Regulation Supplement (DFARS) clauses 252.211-7003, 252.211- 7007 for items delivered under the contract, as applicable. The Contractor shall provide a plan for the application of IUID markings IAW the CDRL.

(CDRL AA026) DI-MGMT-81803 IUID Plan

3.1.11 Warranty Performance System. The Contractor shall establish and maintain a warranty performance system that identifies and documents all items to be warranted under this contract. Each item warranted shall be indexed and identified by serial number, model or part number, and date of acceptance by the Government. Warranties shall become effective based upon a negotiated agreement between the Government and the Contractor. All pertinent data required for the Government to pursue warranty provisions, remedy, and relief for each item shall be maintained by the Contractor for the duration of the warranty period. All warranty claims and transactions shall be documented and made available for Government review during scheduled meetings and/or reviews. The Contractor shall ensure that subcontractor and vendor warranties provide the same coverage and are passed through to the end item.

(CDRL AA027) DI-SESS-81639A, Warranty Performance Report

3.1.12 Test & Evaluation (T&E).

3.1.12.1 T&E Activities. The Contractor shall coordinate with the Government to assist in test planning and T&E activities in support of the EMD phase, to include:

Plan and execute Contractor Specification Testing (CST) testing that assesses the system or subsystem functional capabilities to meet the JBADS PSpec requirements. In conjunction with this test, provide a overall detailed test plan to the Government and lead Operational Test Agency (OTA)/Air Force Operational Test and Evaluation Command (AFOTEC) for review and approval IAW the CDRL. This test will be conducted at the Contractor facility with Government oversight.

Deliver 8ft x 8ft x 8ft Aircraft Enclosure scale test article for Customer Vapor Seal Test and ADU test articles for Mil-Std-810 testing to government test facility (either McKinney lab, Eglin AFB, FL or Aberdeen Test Center, Aberdeen, MD). The Government will provide test plan and personnel to conduct test. Contractor must provide personnel to operate the system during test. The Contractor should plan for a test duration of two to four weeks.

Plan and execute Product Verification Test-2 at Contractor facility/site. The Government will verify System/Subsystem Implementation at the Contractor Test Site to include Operational Configuration of the AE/ADU/CM integration; Storage and Transport Configuration; Assembly and Disassembly; Material Handling Equipment (MHE); Power; Decontamination Parameters, AE size; and verification of aircraft placement/dimensions within the AE.

Coordinate all test plans for review and approval with the Government and lead OTA/AFOTEC to ensure data used for system assessment and system evaluation, including safety confirmation is both verified and validated in accordance with approved Test Operation Procedures.

Develop in coordination with Government and lead OTA/AFOTEC a Failure Definition Scoring Criteria (FDSC) to identify test incident reports and to provide guidance for scoring conferences.

Conduct and report analyses of test failures to assist in isolating causes of failure and corrective action plans to lead OTA prior to the conduct of PVT-2. Failures in Contractor Testing will be corrected and fixes validated before proceeding to PVT-2. Provide failure data and traceability records IAW the CDRL.

Support lead OTA/AFOTEC and Government in the execution of the OA. Lead OTA/AFOTEC will conduct an OA during the PVT-2 to assess progress toward operational effectiveness, suitability, mission capability, and readiness for Initial Operational Test and Evaluation (IOT&E).

Plan and execute Contractor Logistics Support for IOT&E IAW the Lead OTA/AFOTEC Operational Test Plan and the JBADS Test and Evaluation Master Plan.

Train Government test personnel on system set-up, operation, and disassembly of JBADS.

Provide personnel needed for the system set-up, operations, and disassembly during tests.

Provide failure data and traceability records (IAW CDRL).

Ensure Contractor test participant personnel are properly trained on material handling equipment prior to being used during tests.

(CDRL AA028) DI-SESS-81704 Test Plan/Test Procedure (CDRL AA029) DI-SESS-80255A Failure Data and Traceability Records

3.1.12.2 The Contractor shall provide on-site/off-site support, as listed for each of the following T&E events:

3.1.12.2.1 Product Verification Test (PVT-2). The Contractor shall implement PVT-2 procedures to demonstrate the adequacy and suitability of the Contractor's product and procedures for achieving the requirements in the JBADS PSpec. PVT-2 is planned for 2QFY18. This will include a full system demonstration to support the OA. The PVT-2 shall be at the Contractor’s site with the exception of Government testing required such as MIL-STD-810G testing which will be conducted at a Government test facility. Note: preproduction verification testing shall be required if early verification leads to modifications of original item, production verification and additional testing shall be required.

3.1.12.2.2 Operational Assessment (OA). The OA will include lead OTA/AFOTEC observations of Developmental Test (DT)/Contractor test events and programmatic documents reviews. The OA is currently scheduled to begin in 3QFY18 to inform the Operational Test Readiness Review in 4QFY18. Throughout the DT phase, lead OTA/AFOTEC, Eglin, AFB will assess the Contractor activities and system performance, address issues, and review the operational testability of the requirements specified in the Capability Development Document. Additionally, the test and evaluation Working IPT will review plans and documentation for test planning, system design and performance, and test assets and support requirements. The Contractor shall provide a test support plan IAW the

CDRL.

(CDRL AA030) DI-NDTI-80603A, Test Procedure (OA)

3.1.12.2.3 IOT&E. The Contractor shall containerize and ship all required JBADS components to the IOT&E field test location using surface freight. After arrival at the test location, the Contractor shall perform JBADS container unloading operations. Inspect all components for damage when removed from packaging. Additionally, the Contractor shall inspect JBADS packaging to assess potential environmental impacts during storage. The Contractor team shall then assemble the JBADS and prepare it for operation. In conjunction with military personnel the Contractor shall connect electrical power supplies and water supplies as may be required. With the aircraft inside the aircraft enclosure, the Contractor shall operate the JBADS for one complete decontamination cycle (up to 240 hours (T) or 144 (O) to provide a minimum 96-hour environment) at 170oF (+/- 5 oF) and 90% (+/- 5%) relative humidity (RH). Two additional runs, at required environmental temperatures, shall be conducted, to further evaluate the system. The 240 hours includes warm up/cool down time. During the test, temperature and humidity data will be recorded by a data logger. The test team will also record reliability, availability, and maintainability data throughout JBADS operations. After completion of the decontamination cycle, the C-130 will be extracted from the aircraft enclosure. The Contractor will then, shut down and disassemble the system and prepare it for redeployment.

During the disassembly phase, JBADS will be prepared for re-deployment to the storage site. This test is planned for 1QFY19.

3.1.12.3 Reliability Testing and Reports. The Contractor shall conduct reliability testing of the JBADS system using MIL-HDBK-781A as a guide. Summary reports and a final report shall be provided IAW the CDRL. Summary reports shall be submitted when significant problems are encountered, that prevent reliability data from being attained.

(CDRL AA031) DI-TMSS-81586A, Reliability Test Reports

3.1.13 Logistics.

3.1.13.1 Logistics Activities. The Contractor shall plan, implement, and coordinate with the Government to provide logistics products and logistics support activities during the EMD phase, to include:

Support of systems engineering reviews and activities.

Support of test and evaluation events and activities.

Planning to facilitate yearly system health and availability inspection, including inventory Care of Systems in Storage (COSIS); a COSIS Plan shall be delivered IAW the CDRL.

Planning to facilitate conduct of biennial readiness exercises to demonstrate readiness to operate the system.

Planning to facilitate maintaining JBADS and storage containers, while in storage, to include painting, accomplishing anti-corrosion measures, and cleaning.

(CDRL AA032) TBD – COSIS Plan

3.1.13.2 Long Lead Time Items List. The Contractor shall provide a Long Lead Time Items List (LLTIL) IAW the CDRL that shall contain those items which may cause production or procurement cycles which would preclude timely and adequate delivery, if not ordered.

(CDRL AA033) DI-MGMT-80797 Producibility Analysis Report.

3.1.13.3 Spare Parts Kits. The Contractor shall conduct logistics analysis of the spare parts; to enable the system to meet RAM requirements as contained in the JBADS PSpec.

3.1.13.4 Calibration. The frequency of calibration shall be one year or longer. The Contractor shall perform calibration and calibration verification as needed.

3.1.13.4.1 Measurements Requirement Summary (CMRS). The Contractor shall ensure the developed system is capable of being calibrated and its calibration is verified IAW TO 00-20-14. Calibration and measurement traceability shall be identified and documented IAW MIL-STD-1839D.

(CDRL AA034) DI-QCIC-80278B Calibration Measurement Requirements Summary (CMRS)

3.1.13.4.2 Calibration Certificate. Calibration shall be provided by a laboratory complying with the requirements of ISO 17025 or equivalent standard. A calibration label, certificate/report if applicable, and documentation stating traceability to the National Institute of Standards Technology (NIST) must accompany each unit for which calibration services are provided IAW the CDRL.

(CDRL AA035) DI-QCIC-80798B Calibration Certificate

3.1.13.5 Technical Publications. The Contractor shall provide operator and maintenance manual(s) for the JBADS IAW the CDRL.

(CDRL AA036) DI-TMSS-80527C, Commercial Off-the-Shelf (COTS) Manual and Associated Supplemental Data

3.1.13.6 Support Equipment. The Contractor shall provide a listing of support equipment, defined as tools, test equipment, automatic test equipment, and built-in test/built-in test equipment (BIT/BITE) IAW the CDRL. New JBADS specific test equipment or repair equipment are not desired by the Government for the system. Support equipment should be broken down to include what will be provided by the Vendor and what will be required of the Government to provide.

(CDRL AA037) TBD

3.1.13.7 Mobilization Plan and Host Base Support. The Contractor shall provide plans for mobilization support (IAW the CDRL) along with a listing of the type and quantity of fuel, electrical power, and water required to operate the JBADS for one decontamination cycle.

(CDRL AA038) DI-MGMT-81837, Mobilization Plan

3.1.13.8 Packaging, Handling, Storage and Transportation. All JBADS components shall be stored and transported within 20 or 40 foot ISO containers or in system unique configurations that shall be ISO container certified. Use of 20 foot ISO containers is operationally preferred. The JBADS shall be transportable by military airlift and military sealift in the storage/transport configuration. The JBADS shall be transportable by commercial ground transport over paved roads in the storage/transport configuration without any special U.S. Department of Transportation or State permits.

3.1.13.8.1 Packaging Design. Packaging shall include preservation, unit packing, packing, unitization and marking.

The Contractor shall determine the methods for preservation, unit packing, packing and unitization and marking procedures. The Contractor shall use MIL-STD-147 to consolidate containers when applicable, and shall include bar coding and Military Shipping Labels (MSL).

3.1.13.8.2 Packaging and Preservation of Hazardous Materials. The Contractor shall ensure hazardous materials goes through Packaging and Preservation IAW the requirements of the Code of Federal Regulations (CFR) Title 49 and FED-STD-313.

3.1.13.8.3 Packaging Requirements. All items going into the military distribution system shall require military packaging. The Contractor shall prepare the required packaging documentation IAW MIL-STD-2073-1. The packaging shall protect the JBADS, against direct exposure to extremes of climate, operational, transportation, and storage environments, without protection other than that provided by the packaging. The Contractor shall design packaging for, as a minimum: (a) multiple handling during transportation and in transit storage from point of origin to final user; (b) the transportability requirements of the system; (c) shock, vibration and static loading during shipment; (d) environmental exposure during shipment or during in transit operations where port and warehouse facilities are limited or nonexistent; (e) storage environmental requirements of the system; and (f) outdoor storage in all climatic conditions for a minimum of one year.

(CDRL AA039) DI-PACK-80121C

3.1.13.8.4 Commercial Packaging. The Contractor shall ensure items that are not in the military distribution system are packaged IAW commercial practices as specified in ASTM D 3951 and marked IAW MIL-STD-129, including bar coding and MSL. Shipments do not require military packaging from a vendor to a subcontractor or a prime Contractor; between Contractors and subcontractors; or from a vendor or Contractor to a military arsenal, plant or other activity for immediate use or further processing. All items must arrive at their final destination in undamaged and operable condition.

3.1.13.9 Long Term Storage. The JBADS long term storage location is Holloman Air Force Base (AFB), NM.

3.1.13.10 Logistics Demonstration. The Contractor shall support a Logistics Demonstration (LD) in coordination with the requirements planned for IOT&E (see para 3.1.12.2.3). The LD, will be conducted to identify any potential improvements to the materiel design that may be necessary to enhance supportability and reduce life-cycle cost. LD findings shall be reported IAW the CDRL.

(CDRL AA040) DI-ILSS-80111A, Reliability-Centered Data Analysis (JBADS Log Demo)

3.1.14 JBADS End-Items and Components. The Contractor shall deliver one (1) JBADS during the EMD phase identified as JBADS #1 IAW the JBADS PSpec and JBADS program schedule. JBADS #1 shall be modified and refurbished to be ready for IOT&E. JBADS #1 shall be reconditioned to fieldable status after IOT&E and delivered to the Government at Holloman, AFB to satisfy IOC. Contractor shall deliver two (2) aircraft decontamination units during the EMD phase to support PVT-2/Government MIL-STD-810G testing.

3.2 OPTION 1 PRODUCTION (CLIN 0002). The Government reserves the right to exercise this option.

3.2.1 Program Management. The Contractor shall continue program management as per 3.1.1.

3.2.2 Schedule Planning. The Contractor shall continue schedule planning as per 3.1.2.

3.2.3 Contract Work Breakdown Structure. The Contractor shall continue the CWBS as per 3.1.3.

3.2.4 Meetings, Formal Reviews, Conferences, and Audits.

3.2.4.1 Bi-weekly Joint Program Team Telephone Conference (Telecon). The Contractor shall continue bi-weekly telecons per 3.1.5.3.

3.2.4.2 In-Process Review. The Contractor shall continue per 3.1.5.4.

3.2.5 Systems Engineering (SE). The Contractor shall provide SE activities necessary to support the Production and Deployment (P&D) phase.

3.2.5.1 Manufacturing Readiness Assessment (MRA). The Contractor shall demonstrate the ability to attain a minimum Manufacturing Readiness Level (MRL) of nine (9) at the conclusion of Production and Deployment. The MRA will be conducted as per 3.1.6.2.

3.2.5.2 Reliability, Availability, and Maintainability Program. The Contractor shall continue to maintain their RAM program as per 3.1.6.3.

(CDRL BB001) DI-SESS-81315B, Failure Analysis and Corrective Action Report

3.2.5.3 Environment, Safety, and Occupational Health, System Safety. The Contractor shall continue the systems safety activities as per 3.1.7.2.

(CDRL BB002) DI-SAFT-80102C, Safety Assessment Report (SAR)

3.2.5.4 Configuration Management Process.

3.2.5.4.1 Configuration Status Accounting. As needed, the Contractor shall continue Configuration Status Accounting as per 3.1.9.1.2.

(CDRL BB003) DI-CMAN-81253A, Configuration Status Accounting Information

3.2.5.4.2 Configuration Control. The Contractor shall continue the Configuration Control Process, as needed, per paragraph 3.1.9.3 and all appropriate sub-paragraphs.

(CDRL BB004) DI-CMAN-80463D, Engineering Release Record (ERR) (CDRL BB005) DI-CMAN-80639D, Engineering Change Proposal (ECP) (CDRL BB006) DI-CMAN-80642D, Notice of Revision (NOR) (CDRL BB007) DI-SESS-80640D Request for Variance (RFV) (CDRL BB008) DI-MISC-80508B, Technical Report - Study/Services

3.2.6 Diminishing Manufacturing Sources and Material Shortages (DMSMS). The Contractor shall identify the parts planned to be used as well as those used in the JBADS at a level TBD based upon system design and supply chain considerations IAW the CDRL. The data may be obtained progressively during any program life cycle phase using sources such as the preferred parts list, Bill of Materials, vendor surveys, inspections, etc. The information documented at the part level shall be updated as the design progresses or changes and be sufficient to enable forecasting and management of any associated DMSMS issues. The Contractor shall maintain a list of at least one alternate source of supply for each bill of material component.