Attachment_1_RADAR_POR_SOW.pdf

PMA-266 RADAR

N00019-15-R-4000 / Attachment (1)

Date: 2 September 2015 i

Table of Contents 1 Introduction

1.1 Background

1.2 Acquisition Approach

1.3 Scope

2 Applicable Documents

2.1 Specifications

2.2 Standards

2.3 Publications

2.4 Other Documents

3 Program Management Requirements (CLIN 0001)

3.1 Contractor Integrated Master Schedule (CLIN 0001)

3.2 Progress Reporting (CLIN 0001)

3.3 Risk Management (CLIN 0001)

3.4 Contract Work Breakdown Structure (CLIN 0001)

3.5 Contract Funds Status Report (CLIN 0001)

3.6 Subcontract Cost/Schedule Management and Reporting (CLIN 0001)

3.7 Priced Bill Of Materials (CLIN 0001)

4 Engineering Requirements

4.1 Radar Systems (CLIN 0004)

4.1.1 Mass Properties (CLIN 0004)

4.1.2 Electromagnetic Environmental Effects

4.2 Mission Control System (CLIN 0003)

4.3 System Engineering (CLIN 0001)

4.3.1 System Engineering Management Plan (CLIN 0001)

4.3.2 Systems Engineering Technical Reviews (CLIN 0001)

4.3.3 Meetings (CLIN 0001)

4.3.4 Requirements Traceability (CLIN 0001)

4.3.5 Configuration Management (CLIN 0001)

4.4 Manufacturing

4.4.1 General (CLIN 0002)

4.4.2 Design for Producibility (CLIN 0002)

4.4.3 Manufacturing Methods/Producibility Analysis (CLIN 0002)

4.4.4 RESERVED

4.4.5 Production Management System (CLIN 0002)

4.4.6 Special Tooling and Equipment (CLIN 0002)

4.5 System Safety Engineering

4.5.1 Safety Assessment Report (CLIN 0001)

4.5.2 Environment, Safety, and Occupational Health (CLIN 0001)

4.6 System Security Engineering

ii

4.6.1 System Security (CLIN 0001)

4.6.2 Protection Level (CLIN 0001)

4.6.3 Information Assurance/Cybersecurity (CLIN 0001)

4.6.4 Anti-Tamper Requirements (CLIN 0001)

4.6.5 Unauthorized Access To Critical Software Functionality (CLIN 0001)

4.6.6 Critical Program Information (CLIN 0001)

4.6.7 RESERVED

4.6.8 Export Compliance/Exemption (CLIN 0001)

4.7 Flight Certification (CLIN 0002)

4.7.1 Antenna Pattern Analysis (CLIN 0002)

4.7.2 Vibration Analysis and Test Data (CLIN 0002)

4.7.3 Thermal Survey (CLIN 0002)

4.8 Interface Documents

4.8.1 System Design Document (CLIN 0001)

4.9 Software Development

4.9.1 Software Metrics (CLIN 0001)

4.9.2 Software Requirements Analysis (CLIN 0001)

4.9.3 Software Design (CLIN 0001)

4.9.4 Software Formal Qualification Testing (CLIN 0001)

5 Test Requirements (CLIN 0002)

5.1 Electrical System Testing (CLIN 0002)

5.2 EMI Test (CLIN 0002)

5.3 Qualification Testing (CLIN 0002)

5.4 Acceptance Testing (CLIN 0002)

5.5 Radar System Lab Integration (CLIN 0002)

6 Logistics Requirements (CLIN 0001)

6.1 Technical Publications (CLIN 0001)

6.2 RESERVED

6.3 RESERVED

6.4 Maintenance Data (CLIN 0001)

6.5 Drawings (CLIN 0001)

6.6 Supply Support (CLIN 0001)

6.6.1 Engineering Data For Provisioning (CLIN 0001)

6.6.2 Package Handling, Storage and Transportation (CLIN 0001)

6.6.3 Interim Support Items List (CLIN 0001)

6.6.4 Long Lead Time Items List (CLIN 0001)

6.6.5 Provisioning Parts List (CLIN 0001)

6.6.6 Statement of Prior Submission (CLIN 0001)

6.7 Manpower and Personnel (CLIN 0001)

6.8 Reliability and Maintainability (CLIN 0001)

6.8.1 Reliability, Maintainability, and BIT Predictions (CLIN 0001)

6.8.2 Failure Modes Effects and Criticality Analysis (CLIN 0001) iii

6.8.3 Failure Reporting Analysis and Corrective Action System (CLIN 0001)

6.8.4 Environmental Stress Screening (CLIN 0001)

6.9 Support Equipment (CLIN 0001)

6.10 Bill of Materials (CLIN 0001)

7 Quality Requirements

7.1 Management System (CLIN 0001)

7.2 Standards and Procedures (CLIN 0001)

7.3 RESERVED

7.4 Anti-Counterfeit Parts and Material (CLIN 0001)

8 Production Kits – SOW Option 1

8.1 Scope

8.2 Requirements

8.2.1 Program Management Requirements (CLIN 0006)

8.2.2 Engineering Requirements (CLIN 0006)

8.2.3 Test Requirements (CLIN 0006)

8.2.4 Logistics Requirements (CLIN 0006)

9 Production Kits – SOW Option 2

9.1 Scope

9.2 Requirements

9.2.1 Program Management Requirements (CLIN 0008)

9.2.2 Engineering Requirements (CLIN 0008)

9.2.3 Test Requirements (CLIN 0008)

9.2.4 Logistics Requirements (CLIN 0008)

10 Production Kits – SOW Option 3

10.1 Scope

10.2 Requirements

10.2.1 Program Management Requirements (CLIN 0010)

10.2.2 Engineering Requirements (CLIN 0010)

10.2.3 Test Requirements (CLIN 0010)

10.2.4 Logistics Requirements (CLIN 0010)

11 Data Accession List 12 Acronyms Appendix A – NAVAIR Chemicals of Concern

1 INTRODUCTION

1.1 BACKGROUND

The Chief of Naval Operations, supported by a NAVCENT Urgent Operational Needs Statement, directed PMA-266 to field a Rapid Deployment Capability (RDC) RADAR System Program for the MQ-8B Fire Scout. As part of that effort, Northrop Grumman Corporation procured and integrated a Telephonics RADAR system, on-board software, and RADAR Ground Control Work Station. The MQ-8B RADAR has undergone lab testing, Development Testing, and a Quick Reaction Assessment. Because of the success of the RDC, PMA-266 was directed to field a RADAR System for the MQ-8C Fire Scout as a Program of Record.

The MQ-8C provides real-time and non-real-time intelligence, surveillance, and reconnaissance (ISR) data to tactical users including line-of-sight tactical reconnaissance, classification, targeting and laser designation, and battle management (including communications relay) without the use of manned aircraft or reliance on limited joint theater or national assets. The MQ-8C can operate from all air capable ships as well as confined area land base and is designed for modular mission payloads, autonomous vertical launch and recovery, autonomous waypoint navigation, and command override capability.

To support the Surface Warfare mission, the MQ-8C will conduct ISR missions with a variety of payloads, including a maritime search RADAR. The ability of the maritime RADAR to cue the Electro- Optic (EO)/Infrared (IR)/Laser Designator and Range Finer sensors will expand the utility of the MQ-8C as a Surface Surveillance Coordination asset enabling a contact to be classified and tracked on RADAR and refined to positive identification with the EO/IR sensor.

1.2 ACQUISITION APPROACH

The Government’s overall strategy for this acquisition is to conduct the effort over two phases with a single RADAR Original Equipment Manufacturer (OEM) contractor. The RADAR OEM’s competitively awarded contract will span both Phases I and II.

Phase I In the first phase, the winner of the RADAR OEM competition will work with the current Fire Scout Prime Contractors (Northrop Grumman Aerospace Systems (NGC-AS) and Raytheon Company), who will be associate contractors to the competitive contract, and will be contracted by the Government separately. Perfomance under these contracts will result in a consolidated Systems Requirements Review (SRR). Additionally, during this first phase, the Government will begin preparations for commencement of Phase II, the Integration and Test phase of the RADAR system effort.

Phase II In the second phase, the RADAR OEM will continue work under this contract to complete Weapons Replaceable Assembly (WRA) qualification, production of test kits, and Tactical Control System (NCS) Non Recurring Engineering (NRE). It is also intended for the RADAR OEM to be a directed subcontractor to NGC-AS and Raytheon under the planned Integration and Test contracts for: Completion of the integration design of the selected RADAR into the MQ-8C Fire Scout System, Systems Engineering Technical Review (SETR) events associated with the integration design, modifications to Fire Scout software baselines required for the integration, Fire Scout Hardware-In-The-Loop (HITL) Formal Qualification Testing/System Integration Testing, A-kit fabrication and installation, and ground and flight test. The primary interface between the RADAR and the Fire Scout System will be in the MQ-8C AV. As such, it is envisioned that the subcontracted effort with Raytheon for the Phase II will consist mostly of reachback Subject Matter Expert (SME) support.

This SOW covers the following RADAR OEM efforts:

1) Preparation for, conduct of, and successful completion of an SRR (CLIN 0001);

2) Qualification of the RADAR Weapons Replaceable Assemblies (WRAs) for the Fire

Scout Environment (CLIN 0002);

3) Any RADAR OEM NRE required for Tactical Control System (TCS) compatibility

(CLIN 0003);

4) Production of RADAR B-kits for the HITL, ground, and flight test (CLIN 0004);

5) Data for the above CLINs (CLIN 0005)

6) Options for production B-kits (CLINs 0006, 0008, and 0010).

7) Data for the above CLINs (CLINs 0007, 0009, and 0011)

The relationship between the anticipated contracts is shown in Figure 1. The notional program schedule is also provided in Section L of the Request for Proposal (RFP).

Figure 1 – RADAR Contracting Structure The RADAR OEM competitively awarded contract will span Phases I and II.

1.3 SCOPE

The effort described in this solicitation is intended to cover the following:

1) Preparation for, conduct of, and successful completion of an SRR (CLIN 0001);

2) Qualification of the RADAR Weapons Replaceable Assemblies (WRAs) for the Fire Scout

Environment (CLIN 0002);

3) Any RADAR OEM NRE required for Tactical Control System (TCS) compatibility (CLIN

0003);

4) Production of RADAR B-kits for the HITL, ground, and flight test (CLIN 0004);

5) Data for the above CLINs (CLIN 0005)

6) Options for production B-kits (CLINs 0006, 0008, and 0010).

7) Data for the above CLINs (CLINs 0007, 0009, and 0011)

2 APPLICABLE DOCUMENTS

The following documents form compliance requirements and the basis for efforts to be performed in accordance with this Statement of Work (SOW). Unless otherwise specified, the documents listed in this section shall be used to determine technical compliance as specified in this SOW. Documents listed in this section reference other documents that shall be used for guidance only. Documents apply only to the extent of the issues and revisions of these documents as specified herein unless otherwise noted.

In the event of a conflict between a drawing or model specified herein and any other drawing or model specified alone or as part of any other document (including the equipment Specification), the former shall take precedence. In the event of conflict between the SOW and the RFP/contract, the RFP/contract shall be considered the superseding document, and take precedence. In the event of conflict between the requirements of the documents referenced herein and the contents of this SOW, the SOW shall take precedence.

The Contractor shall review the specifications, drawings, and standards specified herein and submit recommended changes to the cited documents, together with the rationale. MIL-HDBK-61A(SE), reference 2.2-6, shall be used as a guide. Total ownership cost is an important consideration.

Submissions of corporate best commercial practices (in lieu of information specified herein) that provides equivalent information at a reduced cost is encouraged.

2.1 SPECIFICATIONS

These specifications will be updated upon successful closure of the RADAR SRR. The Contractor shall comply with the RADAR SRR specifications.

1. Radar System Performance Specification for the VTUAV (MQ-8C), Attachment (2) to the RFP.

2. C72-1100-122, Finishes & Coatings, General Specification for MQ-8C Weapons System

3. MIL-PRF-32216, Performance Specification: Evaluation of Commercial Off-the-Shelf (COTS)

Manuals and Preparation of Supplemental Data, 17 Oct. 2006

4. S1000D, International Specification for Technical Publications Using a Common Source

Database

5. C72-6100-013 Rev B, System Specification for the Vertical Take-Off and Landing Tactical

Unmanned Aerial Vehicle System, 19 Apr. 2013

6. PMA266 11-002 Rev 5, Performance Specification for the VTUAV Endurance Upgrade, 18 Jan.

2.2 STANDARDS

1. TA-HB-0007-1, Logistics Product Data Reports Handbook

2. DoD-STD-1399/070 - Part 1, Military Standard: Interface Standard For Shipboard Systems

(Section 070 - Part 1) D.C. Magnetic Field Environment, 26 Feb 1979

3. MIL-HDBK-217F, Military Handbook Reliability Prediction of Electronic Equipment

4. MIL-HDBK-472, Military Standardization Handbook: Maintainability Prediction, 24 May 1966

5. MIL-HDBK-502A, Department of Defense Handbook: Acquisition Logistics, 30 May 1997

6. MIL-HDBK-61A(SE), DoD Configuration Management Guidance, 7 Feb 2001

7. MIL-HDBK-704-8, Department of Defense Handbook: Guidance for Test Procedures for

Demonstration of Utilization Equipment Compliance to Aircraft Electrical Power Characteristics

28 VDC

8. MIL-HDBK-781A, Reliability Test Methods, Plans, and Environments for Engineering, Development Qualification, and Production

9. MIL-STD-1629A Military Standard Procedures for Performing a Failure Mode, Effects and Criticality Analysis

10. MIL-STD-1686C, Military Standard: Electrostatic Discharge Control Program for Protection of Electrical And Electronic Parts, Assemblies and Equipment

11. MIL-STD-196E, Joint Electronics Type Designation System

12. MIL-STD-2165, Military Standard Procedures for Testability Program for Electronic Systems and Equipment

13. MIL-STD-3001/1, Department of Defense Standard Practice: Preparation of Digital Technical

Information for Multi-Output Presentation of Technical Manuals, 15 May 2001

14. MIL-STD-461F, Requirements for the Control of Electromagnetic Interference Characteristics of

Subsystems and Equipment

15. MIL-STD-464C, Department of Defense Interface Standard: Electromagnetic Environmental

Effects, Requirements for Systems, 01 Dec 2010

16. MIL-STD-704F, Military Standard: Electric Power, Aircraft, Characteristics and Utilization of

17. MIL-STD-785B (NOTICE 3), Military Standard: Reliability Program for Systems and Equipment

Development and Production, 30 July 1998

18. MIL-STD-881C, Department of Defense Standard Practice Work Breakdown Structures for

Defense Materiel Items, 03 Oct. 2011

19. MIL-STD-882E, Department Of Defense Standard Practice for System Safety

20. NAS-411, National Aerospace Standard, Hazardous Materials Management Program

21. SAE-GEIA-HB-0007B, Logistics Product Data Handbook

22. SAE TA-STD-0017, Product Support Analysis, 1 Nov 2012

23. SAE/AS 5553, Fraudulent/Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, and

Disposition

24. SAE/AS 9100C, Quality Management Systems - Requirements for Aviation, Space and Defense

Organizations

25. FED-STD-313D, Federal Standard: Material Safety Data, Transportation Data And Disposal Data

For Hazardous Materials Furnished To Government Activities

26. FIPS 140-2, National Institute of Standards and Technology Federal Information Processing

Standards Publication, Security Requirements For Cryptographic Modules, 11 Jan. 1994

27. MIL-STD-2073/1E, Department of Defense Standard Practice for Military Packaging, 23 May

28. MIL-HDBK-263B, Military Handbook: Electrostatic Discharge Control Handbook for Protection of Electrical and Electronic Parts, Assemblies, and Equipment (Excluding Electrically Initiated Explosive Devices), 31 Jul 1994

29. PPP-C-795D, Federal Specification: Cushioning Material, Packaging (Flexible Closed Cell Plastic Film, For Long Distribution Cycles), 13 Jun 1994

30. MIL-P-81997B, Military Specification: Pouches, Cushioned, Flexible, Electrostatic-Free, Reclosable, Transparent, 30 Sep 1983

31. MIL-B-117G, Military Specification: Bags, Heat-Sealable, 18 Aug 1998

32. MIL-B-81705C, Military Specification: Barrier Materials, Flexible, Electrostatic Protective, Heat-Sealable, 25 Jan 1989

33. International Standards For Phytosanitary Measures, Publication 15, "Guidelines For Regulating

Wood Packaging Material In International Trade, Mar 2002

34. MIL-STD-129P, Department of Defense Standard Practice: Military Marking for Shipment and

Storage, 15 Dec 2002

35. GEIA-STD-0007B, Logistics Product Data, 1 May 2013

36. SDDC Freight Traffic Rules Publication NO. 1C, Rules and Accessorial Services Governing the

Movement of Department of Defense Freight Traffic by Motor Carrier, Item 13

2.3 PUBLICATIONS

1. FAR 52.223-3, Hazardous Material Identification and Material Safety Data (Jan 1997)

2. DoD 5220.22-M, National Industrial Security Program Operating Manual, 28 Feb. 2006

3. DFAR 252.211-7003, Item Unique Identification and Valuation

4. Technical Manual Contract Requirements, Number 04-012, 10 Apr. 2006

5. DON CIO Memorandum, Encryption of Sensitive Unclassified Data at Rest on Mobile

Computing Devices and Removable Storage Media, 3 July 2007

6. DoDI 8500.01, Cybersecurity, 14 Mar. 2014

7. DoD Interim Defense Acquisition Guidebook, (formerly 5000.2-R), 30 Oct. 2002

8. DoD Inst 8510.01, Risk Management Framework for DoD Information Technology, 12 Mar.

9. CJCSI 6510.01,Information Assurance and Computer Network Defense, 9 Feb. 2011

10. DoDM 5200.01, Information Security Manual, 14 Feb. 2012

11. DoD Inst 5200.39, Critical Program Information Protection Within the Department of Defense, 28 Dec. 2010

12. DoD Inst 5000.2, Operation of the Defense Acquisition System, 07 Jan. 2015

13. DoD Inst S-5230.28, Low Observable and Counter Low Observable Programs, 26 May 2005

14. International Traffic In Arms Regulations, parts 120-130

15. DoDM 5200.01 Volume 4, Information Security Program: Controlled Unclassified Information, 24 Feb. 2012

16. DoD 5400.7-R, DoD Freedom of Information Act Program, Sep. 1998

17. National Security Decision Directive Number 298, 22 Jan. 1988

18. DoD Inst 8520.02, Public Key Infrastructure (PKI) and Public Key (PK) Enabling, 24 May 2011

19. DoD Directive 5200.39, Security Intelligence, and Counterintelligence Support to Acquisition

Program Protection, 10 Sept. 1997

20. DFAR 252.211-7006, Passive Radio Frequency Identification, Sep 2011

21. DoD Inst 6055.11, Protecting Personnel from Electromagnetic Fields, 19 Aug 2009

2.4 OTHER DOCUMENTS

1. 266-12-002 Rev A, PMA-266 Configuration Management Plan

2. ISO 9001:2008 Quality Management Systems AS9100 Aerospace Quality System Standard

3. MIL-DTL-81310F, Detail Specification: Manuals, Technical: Airborne Weapons/Stores

Loading/Weapons Assembly/Support Equipment Configuration, 19 Mar 2004

4. MIL-DTL-85025B, Department of Defense Detail Specification: NATOPS Program Technical

Publications and Products; Style, Format, And Common Technical Content, 28 Sep 2007

5. NAVAIR 00-25-406, Design Interface Maintenance Planning Guide, 6 August 2004

6. DoD 4500.9-R, Defense Transportation Regulation, Part 2, June 2008

7. NAVAIR Instruction 4200.25D, Management of Critical Application Items Including Critical

Safety Items, 20 Jun 02

8. NAVAIR Instruction 4790.22, NAVAIR Acquisition Guide 2014/2015

9. NAVAIRINST 4120.11, Policy for Preparation and Standardization of NAVAIR Interactive

Electronic Technical Manuals

10. NAVAIRINST 4355.19D, System Engineering Technical Review Process

11. NAVAIRINST 5100.11, Research and Engineering Technical Review of Risk Process and

Procedures for Processing Grounding Bulletins

12. OPNAVINST 3710.9D, Anthropometric Accommodation in Naval Aviation, 1 Nov 2006

13. PMA-266 Risk Management Plan, 26 June 2009

14. American Lumber Standard Committee, Incorporated Wood Packaging Material Policy, 8 Nov

15. American Lumber Standard Committee, Incorporated Wood Packaging Material Enforcement

Regulations, 7 Nov 2014

16. SECNAVINST 5510.30, DON Personnel Security Program Instruction, 6 Oct. 2006

17. Security Classification Guide for Vertical Takeoff and Landing Tactical Unmanned Air Vehicle, 11 Sept. 2009

18. ANSI/EIA-649-B Configuration Management Standard

3 PROGRAM MANAGEMENT REQUIREMENTS (CLIN 0001)

The Contractor shall maintain and utilize existing MQ-8C program management processes and procedures to include: use of the MQ-8C Integrated Data Environment, PMA-266 Risk Management Plan (reference 2.4-13), and the PMA-266 Configuration Management (CM) Plan (reference 2.4-1). The Contractor shall identify a single point of contact as the RADAR System Integrated Product Team (IPT) Lead who will be responsible for the program management of their team. The Contractor shall provide all materials, services, personnel, and facilities for the management of the tasks identified in this SOW. The Contractor shall plan for and conduct twice monthly IPT meetings (teleconferences or collaborative environment) with Government attendance. Agendas for the meetings shall include schedule status (tasks scheduled in the Integrated Master Schedule (IMS) for the current period vs. tasks completed), technical risks and issues, and thirty-day look-ahead forecasting.

3.1 CONTRACTOR INTEGRATED MASTER SCHEDULE (CLIN 0001)

The Contractor shall develop a program IMS for efforts required to support the RADAR Program of Record Tier 0 Schedule Milestones shown in Figure 1. The Contractor shall schedule all of the events defined in this SOW to ensure integration with design, test, analysis, and Integrated Logistics Support.

The IMS shall include a Work Breakdown Structure (WBS) framework that supports schedule reviews, tracking of key program milestones, and cost collection structure for contract efforts. Status updates shall also be provided monthly. The IMS shall be delivered in accordance with CDRL PM01.

3.2 PROGRESS REPORTING (CLIN 0001)

The Contractor shall provide a Monthly Status Report and Financial Status Report (MSR/FSR), as Work Product WP01, for all activities conducted under this SOW. The MSR shall detail current activities, significant accomplishments to date, planned activities, travel, and any issues. The FSR shall detail planned and actual expenditures by month.

3.3 RISK MANAGEMENT (CLIN 0001)

The Contractor shall conduct risk assessments and provide mitigation plans for each identified risk.

These assessments shall be provided in the MSR and shall include the areas of performance, cost, schedule, supportability, quality assurance, test and evaluation, and producibility as they apply to each risk. Project Risk Management shall be in accordance with the PMA-266 Risk Management Plan, reference 2.4-13. The Contractor shall participate in PMA-266 RADAR Risk boards monthly (virtual participation is acceptable).

3.4 CONTRACT WORK BREAKDOWN STRUCTURE (CLIN 0001)

The Contractor shall maintain the Contract Work Breakdown Structure (CWBS) and CWBS dictionary using the WBS, provided as Government Furnished Information, as a baseline and shall update the linked CWBS dictionary as additional elements, in accordance with MIL-STD-881C, reference 2.2-18. The WBS shall be the basis for further extensions to control accounts and work packages during performance of the contract. The Contractor shall use the CWBS as the framework for reporting contract planning, budgeting, technical status, and schedule status. During the performance of the contract, the Contractor shall not change the approved CWBS or associated definition, or any of the reporting elements, without prior written approval from the Government. The CWBS and CWBS dictionary shall be delivered in accordance with CDRL PM02.

3.5 CONTRACT FUNDS STATUS REPORT (CLIN 0001)

The Contractor shall prepare and deliver Contract Funds Status Reports in accordance with CDRL PM03. The Contract Funds Status Reports shall include Software as a separate item.

3.6 SUBCONTRACT COST/SCHEDULE MANAGEMENT AND REPORTING (CLIN

0001)

The Contractor shall manage all subcontracts, including those that are Firm Fixed Price, to include the timely award of the subcontract, integration of the Subcontractor’s plans into appropriate schedules with sufficient detail, and monitoring the Subcontractor’s staffing plans, to include the execution of those staffing plans to the required levels with the required skills.

The Contractor shall provide, as Work Product WP11, any hardware and software related Supplier Data Requirements List (SDRL) documents.

Each Subcontractor, with an IMS SDRL requirement working any portion of the RADAR System development and integration, will be fully integrated into the Prime’s IMS.

3.7 PRICED BILL OF MATERIALS (CLIN 0001)

The Contractor shall prepare a report utilizing the Contractor’s standard Priced Bill of Materials (PBOM) format with the additional requirement for supplier CAGE code, proposed cost, proposed profit/fee, finalized cost, and finalized profit/fee in accordance with CDRL PM04.

The pre-negotiation and post-settlement reports shall utilize the Contractor’s standard PBOM format, but shall contain the additional data required above, as well as supplier CAGE or DUNS code, in accordance with CDRL PM04.

Pre contract award:

The Contractor shall prepare a complete PBOM, which includes the quantities and cost of all components or subcomponents that the Prime Contractor outsources, in Contractor format (both PDF and Excel). This shall be inclusive of all subcontractors regardless of nomenclature used (i.e. Major Subcontractors, General Procurement Subcontractors, Value-added, Non-value Added, etc.). The PBOM shall be submitted with the proposal to include supplier CAGE code (DUNS number is an acceptable alternate if CAGE Code is unavailable) and proposed profit/fee.

Post Contract Award:

The Contractor shall prepare a complete PBOM, which includes the quantities and cost of all components or subcomponents that the Prime Contractor outsources, in Contractor format (both PDF and Excel). This shall be inclusive of all subcontractors regardless of nomenclature used (i.e. Major Subcontractors, General Procurement Subcontractors, Value-added, Non-value Added, etc.) The PBOM shall be delivered 180 days after contract award. The PBOM shall include supplier CAGE Code if available (DUNS number is an acceptable alternate if CAGE Code is unavailable) and finalized profit/fee percent applied on a per part basis.

If different profit or fee amounts (or percentages) were applied to different subcomponents from the same supplier, the information containing within the PBOM format shall reflect these differences and contain rationale to explain the differences. The post negotiation report shall also identify any parts, materials, or subcomponents that were actually purchased in a different quantity than identified before the prime contract was negotiated.

CAGE or DUNS information shall be included for each supplier on both Pre- and Post-award versions of the report and represent the manufacturing site (not the sales office or contracting site) for the part/s. If the supplier is a distributor with multiple warehouses, provide the CAGE or DUNS code for the warehouse that is shipping the part/s.

Finalized cost shall include 100% of the entire PBOM value based upon part “unit cost” and “total parts cost”.

The Contractor shall report proposed cost, proposed profit/fee, negotiated cost, and negotiated profit/fee for all subcontractors.

After negotiating and awarding subcontracts (not to exceed 180 days after prime contract award), the Contractor shall update and submit the proposed PBOM with negotiated costs and the negotiated profit/fee amount and percent applied to each supplier.

If subcontracted efforts are involved, the following additional fields are required in the PBOM: supplier part number, next higher assembly, and CLIN.

4 ENGINEERING REQUIREMENTS

4.1 RADAR SYSTEMS (CLIN 0004)

The Contractor shall provide five (5) RADAR System test kits (B-kits) to support environmental qualification, integration, and test. RADAR System test kits do not include radomes. Any modifications to the Contractor's Non-Developmental Item RADAR System that they deem necessary to meet RFP requirements, prior to the Critical Design Review, shall be covered under this effort. Any additional modifications that may be required in the post Critical Design Review performance period shall be covered under the Engineering Change Proposal (ECP) process described in Section 4.3.5.1 of this SOW.

The Radar System Test kits provided under this provision will be installed on production-representative Flight Test MQ-8C Air Vehicles and used in laboratory testing. The RADAR System, when installed, shall meet all performance requirements in the Radar System Performance Specification for the VTUAV (MQ-8C), reference 2.1-1.

4.1.1 MASS PROPERTIES (CLIN 0004)

The Contractor shall provide an estimate of the RADAR System's weight and 3-axis center of gravity in aircraft coordinates. The Contractor shall provide suitable diagrams of the RADAR System WRAs integrated on the MQ-8C Air Vehicle to insert into the Chart A - Basic Weight Checklist Record and the Chart E - Aircraft Loading Data in accordance with CDRL SE02.

The Contractor shall track the weight and center of gravity of the RADAR System and identify any risks that may require a physical change to hardware, location change of hardware, and updates to original weight estimates or calculations. The Contractor shall have a process in place that, at a minimum, describes actions to take place if the RADAR System is in danger of exceeding the threshold weight limit defined in the performance specification. The Contractor shall execute the strategies outlined in their weight management process. The Mass Properties Control & Management Process shall be provided as Work Product WP02.

4.1.2 ELECTROMAGNETIC ENVIRONMENTAL EFFECTS

4.1.2.1 SPECTRUM SUPPORTABILITY (CLIN 0004)

At SRR, the Contractor shall present the Electromagnetic Environmental Effects (E3) spectrum supportability approach for the RADAR System. At SRR, the Contractor shall present the information required to update the MQ-8C Spectrum Supportability Risk Assessment for inclusion of the RADAR System. The Contractor shall support the spectrum certification in the Equipment Location-Certification Information Database. The RADAR System shall comply with Department of Defense (DoD), national, and international spectrum regulations for use of the electromagnetic spectrum.

4.1.2.2 E3 INTEGRATION & ANALYSIS (CLIN 0004)

The Contractor shall develop and submit to the Government an Electromagnetic Environmental Effects Integration & Analysis Report (E3IAR). The E3IAR shall describe the design measures and test data by which E3 performance requirements are to be assured. Additionally, the E3IAR shall enable the Government to identify possible design deficiencies; shall provide a citation of other documents, test reports, etc. that are relevant to the E3 design effort; and shall serve as the baseline record of the E3 design. The E3IAR shall be delivered in accordance with CDRL SE05.

The E3IAR shall contain an analysis of electromagnetic radiation hazards risk to fuel, ordnance, and personnel and shall describe how to mitigate the risk, if required. The E3IAR shall contain a description of the electrical bonding used in the RADAR System and the levels of electromagnetic emissions in accordance with MIL-STD-464C, reference 2.2-15.

The E3IAR shall contain a list of electrical/electronic components that require protection against damage due to electrostatic discharge during equipment handling. Any need for special electrostatic discharge protective handling procedures shall be called out, in accordance with MIL-STD-1686C, reference 2.2-10.

The Contractor shall perform analysis and testing to characterize the equipment, where necessary.

4.1.2.3 INTRA-SYSTEM ELECTROMAGNETIC COMPABILITY (CLIN 0004)

The RADAR System shall be electromagnetically compatible within itself such that system operational performance requirements are met. Induced levels appearing at antenna ports of antenna-connected receivers caused by unintentional radio frequency (RF) emissions from equipment and subsystems shall be controlled with respect to defined receiver sensitivity such that system operational performance requirements are met.

4.1.2.4 EXTERNAL RF ELECTROMAGNETIC ENVIRONMENT (CLIN 0004)

The RADAR System shall be electromagnetically compatible with its defined External RF Electromagnetic Environment such that its system operational performance requirements are met. MIL- STD-464C Tables 1, 2, 4, and 5 shall apply, reference 2.2-15.

4.1.2.5 SUBSYSTEM AND EQUIPMENT ELECTROMAGNETIC INTERFERENCE (CLIN

0004)

The RADAR System and equipment shall meet interference control requirements so that the overall system complies with all applicable requirements of MIL-STD-461F and MIL-STD-464C, references 2.2- 14 and 2.2-15.

4.1.2.6 NON-DEVELOPMENTAL ITEMS AND COMMERCIAL ITEMS (CLIN 0004)

Non-developmental items and commercial items shall meet Electromagnetic Interference (EMI) interface control requirements suitable for ensuring that system operational performance requirements are met.

4.1.2.7 SHIPBOARD DC MAGNETIC FIELD ENVIRONMENT (CLIN 0004)

The RADAR System and equipment used aboard air capable ships shall not be degraded when exposed to its operational direct current magnetic environment (such as DoD-STD-1399/070-Part 1, reference 2.2-2).

4.1.2.8 LIFE CYCLE, E3 HARDNESS (CLIN 0004)

The RADAR System shall met operational performance and E3 requirements throughout the rated life cycle of the system and shall include, but not be limited to, the following: maintenance, repair, surveillance, and corrosion control.

4.1.2.9 ELECTRICAL BONDING (CLIN 0004)

The RADAR System and all equipment shall include necessary electrical bonding to meet the E3 requirements of MIL-STD-464C, reference 2.2-15.

4.1.2.10 EXTERNAL GROUNDS (CLIN 0004)

The RADAR System shall provide external grounding provisions to control electrical current flow and static charging for protection of personnel from shock, prevention of inadvertent ignition of ordnance, fuel and flammable vapors, and protection of hardware from damage.

4.1.2.11 EMISSION CONTROL (CLIN 0004)

When tactical Emission Control conditions are imposed, electromagnetic radiated emissions shall not exceed -110dBm/m2 at one nautical mile in any direction from the system over the frequency range of 500 kHz to 40 GHz, when using the resolution bandwidths listed in MIL-STD-464C, reference 2.2-15.

4.1.2.12 ELECTROMAGNETIC RADIATION HAZARDS (CLIN 0004)

The Contractor shall comply with current DoD criteria for protection of personnel against the effects of electromagnetic radiation, reference 2.3-21.

4.2 MISSION CONTROL SYSTEM (CLIN 0003)

The Contractor shall provide any required ground station components as part of the RADAR System kits.

The Contractor shall provide support for integration of the RADAR System with the RADAR Ground Control Work Station. The envisioned interface between the RADAR and the MQ-8C Fire Scout System is envisioned to be, primarily in the Air Vehicle. As such, it is anticipated that Phase 1 support will consist of telephone calls between the Contractor and the Ground Station OEM to resolve interface issues and to allocate requirements.

4.3 SYSTEM ENGINEERING (CLIN 0001)

The Contractor shall provide a complete technical and operational analysis for the RADAR System. The technical analysis should include a thermal analysis and size, weight, and power impacts. The Contractor shall provide a Baseline Description Document describing payload functionality and performance. The Baseline Description Document shall be delivered in accordance with CDRL SE01.

4.3.1 SYSTEM ENGINEERING MANAGEMENT PLAN (CLIN 0001)

The Contractor shall provide either their existing Systems Engineering Management Plan (SEMP) for the development and manufacture of the Radar System or one which has been updated to support this contract. The SEMP shall be provided as Work Product WP19.

4.3.2 SYSTEMS ENGINEERING TECHNICAL REVIEWS (CLIN 0001)

The Contractor shall participate in tailored SETR events with the Government Technical Team. The only SETR event for the efforts covered by this SOW shall be an SRR. The review will include tailored entrance and exit criteria, in accordance with NAVAIRINST 4355.19D, reference 2.4-10, and its associated modules. Entrance and exit criteria selection shall be provided by the Government Systems Engineering team as part of SETR planning.

The SETR shall be conducted as a multi-day event (not to exceed 5 days for travel and meeting conduct) and shall be held in the Patuxent River area no later than 5 months after contract award. Minimal Contractor representation (i.e., 3-4 personnel) is required. Video conferencing will be provided for personnel who will not be attending in person. All Contractor SETR input shall be submitted no later than thirty days prior to the noted event in accordance with CDRL SE08.

The SETR shall be considered closed when all the action items assigned at the meeting have been closed to the mutual satisfaction of both the Government and Contractor.

4.3.3 MEETINGS (CLIN 0001)

The Government desires Technical Interface Meetings (TIMs) as required to support the Program through SRR. The Contractor shall propose an appropriate number of TIMs, to support their approach up to SRR.

Interface Control Working Group meetings, Crew Systems Working Group meetings, and System Safety Working Group meetings are not covered by the scope of this SOW. Those efforts will be covered under the integration contract with the Air Vehicle Contractor.

4.3.4 REQUIREMENTS TRACEABILITY (CLIN 0001)

The Contractor shall deliver a Requirements Traceability Document for the RADAR System Performance Specification for the VTUAV (MQ-8C), reference 2.1-1. The RADAR Performance Specification requirements shall trace to the System Specification and System Design Document (SDD), as appropriate.

The Requirements Traceability Document shall be delivered in accordance with CDRL SE09.

The Contractor shall perform requirement analysis, decomposition, and allocation from source requirements to the lowest Configuration Item. The Contractor shall maintain traceability through all systems, software and test documentation. The traceability shall be demonstrated through a Government approved requirements management database. Use of IBM® Rational® DOORS® requirements data base is acceptable.

4.3.5 CONFIGURATION MANAGEMENT (CLIN 0001)

The Contractor shall maintain a CM program to control products, processes, and related documentation to ensure the integrity of design and supportability for both hardware and software configuration items (CIs) consistent with the American National Standards Institute (ANSI) / Electronic Industries Alliance (EIA) Configuration Management Standards (ANSI/EIA-649-B), reference 2.4-18, and in accordance with the Contractor's Government-approved Configuration Management Plan (CMP) in support of DoD MIL- HDBK-61A(SE), reference 2.2-6, and the PMA-266 CMP, references 2.4-1. The CM effort shall include identification and control of all system functional, allocated, and product baselines; establishment of a configuration status accounting system to provide an audit trail of all configuration changes; and identification, documentation, and verification of the functional and physical characteristics of each CI.

The Contractor shall impose configuration management requirements on all subcontractors to ensure that configuration integrity of the procured items will be maintained throughout system life.

4.3.5.1 CLASS I ENGINEERING CHANGE PROPOSALS (CLIN 0001)

Class I changes shall be submitted to the Government for assessment and RFP decision, as defined in the PMA-266 CM Plan, reference 2.4-1, to include any changes to the requirements, allocated baseline, or to the product baseline. The Contractor shall use the Contractor’s CM Plan in support of ANSI/EIA-649-B and the PMA-266 CM Plan, references 2.4-18 and 2.4-1. This SOW only covers the non-recurring efforts required to facilitate the Joint Contractor/Government IPT planning and Estimation Process for configuration change solution, which ends at the Joint Change Review Meeting. Any decision by the Government to implement a change to the configuration will be addressed through the release of an RFP for a formal ECP to be processed through the Government Configuration Control Board (CCB) for approval as a separate contract action.

4.3.5.2 CONFIGURATION MANAGEMENT PLAN (CLIN 0001)

The Contractor shall use a CMP utilizing guidelines established in MIL-HDBK-61A(SE), reference 2.2-6, detailing requirements of paragraph 5.2.4 above. The Contractor shall prepare and submit updates to this CMP as required for review and approval by the Navy utilizing guidelines established in MIL-HDBK- 61A(SE), reference 2.2-6. The CMP shall be submitted to the Government for approval in accordance with CDRL CM01.

4.3.5.3 CONFIGURATION STATUS ACCOUNTING DATA (CLIN 0001)

The Contractor shall maintain a Configuration Status Accounting system to collect and record data of the current and approved baseline configuration throughout the CI(s) life cycle in order to support and enable an efficient configuration management process. These practices shall be in accordance with the Contractor's Government approved CMP and shall be provided to the Government in accordance with Work Product WP20.

4.3.5.4 PROPOSED SPECIFICATION CHANGE NOTICES (CLIN 0001)

The Contractor shall submit Proposed Specification Change Notices (PSCNs) for any changes or revisions to detailed or performance specifications that have established functional baselines or government-controlled allocated baselines for configuration items. Multiple PSCNs may be submitted under a single ECP. PSCNs shall be submitted in accordance with CDRL CM03.

4.3.5.5 DEVIATIONS (CLIN 0001)

A deviation is a written authorization to depart from the performance or design requirement of a specification, drawing, ECP, or other contractual document for a specified number of items or period of time. The Contractor shall submit all major Requests For Deviations to the Government for review via the CM Manager for processing through the CCB. Disposition of minor deviations shall be in accordance with ANSI/EIA-649-B, MIL-HDBK-61A(SE), the Contractor's Government-approved CMP and the PMA-266 CMP; references 2.4-18, 2.2-6, and 2.4-1. The Contractor shall develop and submit requests for any major deviations in accordance with CDRL CM04.

4.3.5.6 ITEM IDENTIFICATION AND VALUATION (CLIN 0001)

The Contractor shall obtain a Joint Electronics Type Designation System nomenclature and identification of electronic materiel in accordance with MIL-STD-196E, reference 2.2-11.

In accordance with DFARS 252.211-7003 Item Unique Identification and Valuation, reference 2.3-3, where the Government has technical authority of design control responsibilities, the Contractor shall provide a Unique Item Identifier candidate list, in accordance with CDRL LG11, that includes all of the following items:

• Items that are serially managed (i.e., Life-Limited Items)

• Items that are Depot Level Repairables

• Items that have a controlled inventory

• Items designated by the Government

4.4 MANUFACTURING

4.4.1 GENERAL (CLIN 0002)

The Contractor shall manufacture hardware consistent with the quality requirements of International Organization for Standardization (ISO) Q9001-2008, reference 2.4-2. Manufacturing shall include tooling, material, and processes to fabricate, assemble, inspect, check out, test, and deliver the specified hardware.

The Contractor shall ensure that the system is finished in accordance with the MQ-8C finish specification, reference 2.1-2, and provides adequate corrosion protection for specific parts, surfaces of similar and dissimilar materials, and attaching parts and fasteners.

4.4.2 DESIGN FOR PRODUCIBILITY (CLIN 0002)

For items modified under this contract , the Contractor shall maintain a design engineering process that makes producibility of the design a priority early in the design and development effort. The Contractor shall develop product designs and the required manufacturing processes to be used during fabrication and assembly. The manufacturing processes selected shall be statistically capable and have adequate capacity to meet expected production rate. The product shall be designed in such a manner that fabrication and manufacturing methods and processes have flexibility in producing the product at a reasonable cost while maintaining required functionality, performance, quality, and reliability. As part of the design for producibility, the Contractor shall identify and document key characteristics as defined in the current revision of SAE/AS 9100, reference 2.2-24. The design of the RADAR system shall address supportability impacts to the end user, such as troubleshooting and removing and replacing failed components or sub-systems. The Contractor shall provide this documentation as Work Product WP03.

4.4.3 MANUFACTURING METHODS/PRODUCIBILITY ANALYSIS (CLIN 0002)

For items modified under this contract, the Contractor shall document that the design meets all functional requirements, is ready for implementation as an air vehicle modification, production/engineering problems have been resolved, and adequate planning has been accomplished to ensure a low risk production. The Contractor shall provide this documentation as Work Product WP03.

4.4.4 RESERVED

4.4.5 PRODUCTION MANAGEMENT SYSTEM (CLIN 0002)

For items modified under this contract, the Contractor shall establish and maintain an effective Production Management System. The process shall include utilization of a multi-disciplinary approach to problem identification and resolution, production milestone management, continuous resource evaluation, and status meetings to avoid potential manufacturing conflicts.

4.4.6 SPECIAL TOOLING AND EQUIPMENT (CLIN 0002)

A list of Contractor-owned Special Tooling and Special Test Equipment required for the integration and test of deliverable items shall be made available by the Contractor and delivered in accordance with

CDRL SE10.

4.5 SYSTEM SAFETY ENGINEERING

4.5.1 SAFETY ASSESSMENT REPORT (CLIN 0001)

The Contractor shall generate a Safety Assessment Report that follows the guidelines of DI-SAFT- 80102B, reference 2.3-5. The System Hazard Analysis, Subsystem Hazard Analysis, and Operation & Support Hazard Analysis shall be included as appendices in the report. The Safety Assessment Report shall be delivered in accordance with CDRL SE11.

4.5.1.1 SYSTEM HAZARD ANALYSIS (CLIN 0001)

The Contractor shall generate a System Hazard Analysis (SHA) to fulfill the intent of Task 205 of MIL- STD-882E and DI-SAFT-80101B, reference 2.2-19. All identified real or potential hazards and their hardware, software, and human system integration causal factors shall be documented and assessed in the SHA, along with their appropriately identified mitigations.

4.5.1.2 SUBSYSTEM HAZARD ANALYSIS (CLIN 0001)

The Contractor shall generate a Subsystem Hazard Analysis (SSHA) to fulfill the intent of Task 204 of MIL-STD-882E and DI-SAFT-80101B, reference 2.2-19. All identified real or potential hazards and their hardware, software, and human system integration causal factors shall be documented and assessed in the SSHA, along with their appropriately identified mitigations.

4.5.1.3 OPERATION & SUPPORT HAZARD ANALYSIS (CLIN 0001)

The Contractor shall generate an Operation & Support Hazard Analysis (O&SHA) to fulfill the intent of Task 206 of MIL-STD-882E and DI-SAFT-80101B, reference 2.2-19. Task 206 should be performed primarily to identify and evaluate hazards associated with the environment, personnel, procedures, and equipment involved throughout the operation of a system/element. The O&SHA should be performed on such activates as testing, installation, modification, maintenance, support, transportation, ground servicing, storage, operations, and training. All identified real or potential hazards and their hardware, software, and human system integration causal factors shall be documented and assessed in the O&SHA, along with their appropriately identified mitigations.

The Contractor shall generate a Hazardous Material Report, include it as part of the O&SHA, and support the Environment, Safety, and Occupational Health (ESOH) Point Of Contact, if necessary, with this information. Material Safety Data Sheets shall be provided as necessary.

4.5.1.4 SYSTEM SAFETY RISK ASSESSMENT (CLIN 0001)

The Contractor shall support the development of System Safety Risk Assessments, as necessary, that identify the conditions under which a mishap may occur and categorize the system level impact based on severity and probability as defined in NAVAIRINST 5100.11, reference 2.4-11.

4.5.2 ENVIRONMENT, SAFETY, AND OCCUPATIONAL HEALTH (CLIN 0001)

The Contractor shall ensure ESOH requirements are incorporated into the systems engineering process and shall ensure ESOH compliance to avoid adverse program impacts. The Contractor shall eliminate/reduce ESOH hazards and their risks, use of hazardous materials (HAZMAT), hazardous wastes, and pollution/pollutants for processes used during the lifecycle.

The Contractor shall implement a management approach and conduct operations accordingly to ensure the system and associated processes are environmentally safe, do not cause health hazards, and comply with all federal, state, and local environmental laws, regulations, Executive Orders, and policies for all activities defined in this SOW, whether conducted at Government or Contractor facilities. Upon request, the Contractor shall make available to the Government applicable environmental permits and documentation.

The Contractor (and their Subcontractors) shall avoid or minimize use of materials that pose ESOH risks throughout the system’s life cycle as part of systems engineering, logistics, material, and process decisions. The Contractor shall recommend HAZMAT substitutes/changes (alternative materials, processes, or other technologies) to reduce ESOH hazards and disposal problems during operations. The Contractor shall use recycled, recovered, or environmentally-friendly preferable materials where possible.

The Contractor shall develop, implement, and manage HAZMAT in accordance with National Aerospace Standard 411, reference 2.2-20. A Hazardous Materials Management Program (HMMP) Plan and HMMP Report shall be developed in accordance with National Aerospace Standard 411, reference 2.2-20. The Contractor shall provide the Government, in the HMMP Report, its pollution prevention initiatives, a list of hazardous materials inherent in the equipment delivered to the Government, and a list of hazardous materials needed for maintenance. ESOH related attributes (such as noise, emissions, laser safety, etc.) of the system and/or constraints (ESOH risks) shall be identified in the HMMP Report. The HMMP Plan and HMMP Report shall be delivered in accordance with CDRL SE12 and CDRL SE13.

The Contractor shall assess the hardware, applicable processes, methods, and procedures used…