DT-III DRAFT PBSOW 21JUN2010_MASTER.doc

3:01 PM

Performance-Based SOW for DT-III Contract

(DRAFT) Performance-Based

Statement of Work for

DT-III Contract Support of the

F/A-18 Project Team

June 2010

TABLE OF CONTENTS

1.0

INTRODUCTION

2.0

BACKGROUND

3.0

SCOPE

4.0

APPLICABLE DIRECTIVES

5.0

PERFORMANCE REQUIREMENTS

5.1

ENGINEERING SUPPORT

5.2

INSTRUMENTATION SUPPORT

5.3

MAINTENANCE/MANUFACTURING OF PARTS SUPPORT

6.0

DELIVERABLES

7.0

QUALITY ASSURANCE SURVEILLANCE PLAN

8.0

SECURITY

8.1

PROGRAM SECURITY, F/A-18E/F AND EA-18G

8.2

INFORMATION ASSURANCE

8.3

SYSTEM SECURITY

1.0 INTRODUCTION

The F/A-18 Project Team requires support that includes maintenance, manufacturing of parts, instrumentation and engineering support for all models of the F/A-18 & EA-18G aircraft and future variants (domestic and Foreign Military Sales) for ground and flight test programs conducted at the Naval Air Warfare Center Aircraft Division (NAWCAD), Patuxent River, MD.

2.0 BACKGROUND

The F/A-18A-F and EA-18G and future variants aircraft/systems ground and flight test programs are managed by the F/A-18 Project Team assigned to the VX-23 Squadron located at the NAWCAD, Patuxent River, MD. The Project Team is responsible for all project coordination, execution, and support issues related to the ground and flight test of these aircraft models. Additionally, the Project Team ensures compliance with test Squadron Standard Operating Procedures (SOPs) and of the processes/procedures governing all phases of test projects including development, maintenance, and implementation.

Developmental test for the F/A-18 aircraft/systems has been ongoing at the NAWCAD, Patuxent River since 1978. These aircraft/systems are designed to perform Strike Fighter and Electronic Attack missions. Developmental test efforts for all F/A-18 and future variants aircraft/systems in support of both the domestic Fleet and Foreign Military Sales (FMS) programs is expected to continue into the foreseeable future.

3.0 SCOPE

The contractor shall provide technical services in support of Project Team developmental ground and flight test programs. Contractor services shall include aircraft maintenance on unique pre-production and production, F/A-18A-F & EA-18G and future variant aircraft including manufacturing of parts, instrumentation and engineering support, and aircraft modifications. This support shall be for any NAWCAD, Patuxent River assigned F/A‑18A-F & EA-18G and future variants model aircraft, including production aircraft, pre-production uniquely configured aircraft, and a limited number of transient aircraft. Support will occur at Patuxent River, at contractor facilities, during off-site detachments, special events, and divert fields as required.

The contractor shall maintain an average number (outlined below) of aircraft along with required laboratories, machine/metal shops, tooling, tool cribs, aircraft parts/aircraft ancillary equipment (AAE)/support equipment (SE), and personnel to support the project requirements. The contractor shall maintain, as required, one to two F/A-18E/F EMD and EA‑18G plus future variant aircraft in flying status and/or flyable storage. The contractor shall also provide support for USN maintained production F/A-18A-F & EA-18G and future variants aircraft, as required. In addition, the contractor shall support the tactical static display aircraft as required. This support shall be based on a 2-shift operation and include the following specific items: technical engineering and aircraft instrumentation support; scheduled/unscheduled aircraft maintenance; parts manufacturing and fabrication support; aircraft systems support; aircrew support; laboratory support; material handling support and hazardous material program; documentation support; inventory control; quality assurance; and facilities support. Additionally, the contractor shall provide engineering and maintenance support as required for NADEP Integrated Maintenance Concept (IMC) Periodic Maintenance Inspections (PMI-2) level efforts at NAWCAD, Patuxent River for NAVAIR assigned F/A-18 and future variants aircraft.

Off-site contractor support shall primarily include engineering and technical support (system studies, data reduction/analysis, reports, simulations, instrumentation, etc.).

4.0 APPLICABLE DIRECTIVES

The contractor shall adhere, when applicable to the airframe, to the following directives, and their respective updates/revisions, in accordance with the Performance Requirements of this performance-based SOW.

Due to frequent changes to Documents and Directives, it is expected that the most current version will be used.

5.0 PERFORMANCE REQUIREMENTS

5.1 ENGINEERING SUPPORT. The contractor shall provide engineering and technical support at both Patuxent River and off-site, including the use of contractor facilities, as required.

5.1.1. The engineering and technical support shall include design, development, fabrication/manufacturing, integration/installation, calibration, checkout/troubleshoot and repair of new or modified systems/structures in F/A‑18A-F & EA-18G and future variants aircraft. The effort shall include support of system studies, test planning (including Test Working Documents) and execution including daily operations, data reduction/analysis, reports, simulations, system/clearance recommendations, and procurement of components/systems.

5.2 INSTRUMENTATION SUPPORT. The contractor shall provide aircraft instrumentation and technical support at both Patuxent River and off-site, including the use of contractor facilities, as required.

5.2.1. The aircraft instrumentation and technical support shall include both on-/off-aircraft efforts including system design, development, fabrication/manufacturing of parts, hardware procurement, integration/installation, pre-/post-flight checkout/troubleshoot and repair, system calibrations, and database support of instrumentation systems installed in F/A‑18A-F & EA-18G and future variants aircraft to ensure their technical adequacy for required test efforts. Instrumentation support shall ensure the accuracy, resolution, and reliability of the aircraft instrumentation systems.

5.2.2. The contractor shall ensure that contractor data processing systems and Navy aircraft instrumentation systems remain compatible. The contractor shall monitor the development of Navy aircraft instrumentation systems and modify their data processing systems to remain compatible. Upgrades to hardware and software for the contractor data processing systems shall be incorporated as required.

5.2.3. The contractor shall provide material control for all aircraft instrumentation test equipment and ensure the proper handling and accountability of Government Property (including data) in support of aircraft test requirements.

5.3 MAINTENANCE/MANUFACTURING OF PARTS SUPPORT. The contractor shall provide aircraft maintenance/manufacturing of parts and technical support at both Patuxent River and off-site, including the use of contractor facilities, as required.

5.3.1. The contractor shall supply the following aircraft maintenance/manufacturing of parts and technical support:

· Scheduled/unscheduled aircraft maintenance and Quality Assurance (QA) based on a 2-shift operation;

· Parts manufacturing and fabrication support for the replacement of unique or limited supply parts;

· Aircraft systems support for the integration/installation, checkout/troubleshoot and repair of avionics, unique systems, structural components, etc;

· Laboratory support for avionics systems and data handling;

· Material Control handling support for all aircraft and instrumentation equipment/parts;

· Hazardous material program for the associated hazardous material at the storage sites;

· Documentation support including a Maintenance Data Center with blue print files, aircraft technical manuals and aircraft/system design specifications requirements for the F/A‑18A-F and future variants aircraft. All non-production or project modifications incorporated onto aircraft by the contractor shall include documentation of the installation(s) sufficient to support maintenance and associated Logs and Records entries;

· Inventory control for tools/tool cribs, aircraft parts, aircraft ancillary equipment (AAE), and support equipment (SE) in contractor custody at the hangar and warehouse storage sites; and

· Facilities support at both Patuxent River and off-site.

5.3.2. The contractor shall provide aircraft maintenance and QA support with intent of meeting the requirements of the latest version of the OPNAVINST 4790 NAMP and INST 8210 series documents for production aircraft, and pre-production aircraft. To meet this intent, the contractor shall provide a documented plan in accordance with the latest version of the NAVAIRINST 3710 series. This plan, the Patuxent River Ground Operating Procedures, shall be made available to the VX-23 Commanding Officer (CO), Maintenance Officer (MO), Government Flight Representative (GFR), and the F/A-18 Project Team for review and approval. The contractor shall also work within the host-Navy squadron’s guidelines for daily operations, specified in the VX-23 Strike Aircraft Test Squadron SOP.

5.3.3. The contractor shall be responsible for the Repair or Replacement (ROR) of aircraft/system parts which includes the repair, modification (excludes Class I) and/or calibration of all EMD/SDD-unique aircraft/system and support equipment components. The contractor shall repair, modify, restore and/or return items to be serviceable, but not like new, operating condition. The contractor shall not begin servicing or continue to service any article, where it is apparent that a reasonable service life will not be attained or that the resulting total repair price (labor and parts) to the Navy is expected to exceed eighty percent (80%) of an item's replacement price. The ROR price shall be estimated by the contractor based on current production prices. The contractor shall promptly notify the COR and/or the Assistant Contracting Officer Representative (ACOR), which shall include confirmation by the U.S. Government QAR of the contractor’s beyond economic/physical repair (BER/BPR) evaluation. No further repair action shall occur until written authorization to proceed or disposition instructions are received from the COR and/or the ACOR. The contractor is authorized to interchange components on inducted assets during the repair cycle, on a part number for part number basis.

5.3.4. The contractor shall provide engineering and maintenance support as required for NADEP IMC (PMI-2) and for the incorporation of Technical Directives (TDs) level efforts at NAWCAD, Patuxent River for NAVAIR assigned F/A-18 and future variants aircraft.

6.0 DELIVERABLES

6.1. The contractor shall provide documents to the Navy in accordance with the following Contract Data Requirements Lists (CDRLs):

Test Work Descriptions (TWDs). The contractor shall submit TWDs in accordance with CDRL A0001.

Provide Patuxent River Maintenance SOP. The contractor shall submit a Patuxent River Maintenance SOP to VX-23 for review and approval in accordance with CDRL A0002/A0003.

Contract Status reports. The contractor shall submit expenditure reports in accordance with CDRL A0004 and organize meetings with the Navy or any sub-contractors to discuss any up-coming or on-going test issues/topics, as required.

Operations Security (OPSEC) plan. The contractor shall submit an OPSEC plan in accordance with CDRL A0005.

7.0 QUALITY ASSURANCE SURVEILLANCE PLAN

The PBSOW contains a Quality Assurance Surveillance Plan (QASP), which establishes the acceptable quality level, and the method by which the COR will perform the performance assessment. Some of the methods to be used will be the review of reports, random auditing of tracking databases, customer feedback, CPARS, and review of CDRLs.

8.0 SECURITY

The security guidelines listed in this section are applicable to F/A-18 and EA-18G. Any references to F/A-18E/F will also encompass the Legacy models F/A-18 A/B/C/D.

8.1 PROGRAM SECURITY, F/A-18E/F AND EA-18G. The contractor shall maintain and update the F/A-18E/F and EA-18G Security Program as mandated by the Program Protection Plan (PPP) for the F/A-18E/F and EA-18G Program, dated 14 March 2007, and the DD254. The contractor shall comply with, and ensure its subcontractors comply with, DoD 5200.1R, dated 14 January 1997 (certified current as of 24 November 2003), as it pertains to this contract. The contractor shall classify appropriately marked documents developed for this effort in accordance with the Security Classification Guide (SCG) for the F/A‑18 Hornet (All Series) and Electronic Attack EA-18G Aircraft, dated 2 April 2007, and DoD 5200.1R, dated 14 January 1997 (certified current as of 24 November 2003). The contractor shall assess new acquisitions (ECPs) for Critical Program Information and Critical Technologies as indicated by DoD 5200.39, DoD 5200.1-M, DoD S-5230.28, and MCTL. The contractor shall address these requirements within the Program Protection Implementation Plan (PPIP). Until CDR PM03 is approved by the Government, the current PPIP, F/A-18E/F Hornet Program Protection Implementation Plan, MDC 98A0022, Rev C, 31 October 2000 shall be adhered to by the contractor. (CDRL A0005) PM03 Program Protection Implementation Plan (PPIP))

8.2 INFORMATION ASSURANCE

8.2.1. ARCHITECTURE. The network architecture shall maximize us of the contractor’s existing infrastructure and that of its subcontractors, suppliers, the Internet, and the Government Wide Area Networks (WANs), such as NIPRNET, DREN, NMCI and shall maintain compatibility with the NMCI architecture. The contractor shall continue to utilize a network architecture which shall support the mission needs of the F/A-18E/F and EA-18G Program for the purposes of interoperability while maintaining the quality and timeliness of the technical information data access and delivery. The contractor shall share all observed network trends to be utilized in quarterly IA reviews for the purposes of ascertaining the success of the accomplishment of the preceding. The contractor shall implement electronic data sharing for the purposes of data reduction and to avoid transmitting large data files over the network. Appropriate security measures shall be put in place in accordance with SECNAVINST 5239.3B, OPNAVINST 5239.3A, CJCS 6211.02C, DODD 8100.02, DODD 8500.01E, DODI 8500.2 and DODI 8520.2. The contractor shall address these requirements within the Program Protection Implementation Plan (PPIP). (CDRL A0005) PM03 Program Protection Implementation Plan (PPIP))

8.2.2. INFORMATION ASSURANCE PRACTICES. The contractor shall adhere to the Department of the Navy’s (DON’s) Information Assurance Program prescribed methodologies for the protection of information to support DON missions. The contractor shall utilize existing methods and processes in order to deliver secure, interoperable and integrated information management (IM) and information technology (IT) to the DON and its contract support. The contractor shall ensure that all IT systems, software and interfaces meet Government security certification standards and requirements appropriate to the particular classification level of operation as specified by the U.S. Navy, Department of Defense, or the cognizant Government authority for the purposes of the above mentioned DON goals. The contractor shall address these requirements within the Program Protection Implementation Plan (PPIP). (CDRL A0005) PM03 Program Protection Implementation Plan (PPIP))

8.2.3. PUBLIC KEY INFRASTRUCTURE (PKI). PKI encryption is the chosen compliant DoD standard for protecting Controlled Unclassified Information (CUI) during transmission. Failure to encrypt CUI during electronic transmission outside of the .mil domain network is considered a security weakness and must be reported to VX-23 Security. The contractor shall require their personnel corresponding with the Government to adhere to the required PKI policies stated herein. The contractor shall implement Department of Defense (DoD) PKI policy per DODI 8520.2. The contractor shall obtain and utilize PKI certificates issued by approved External Certificate Authority (ECA), for the purposes of protecting all controlled unclassified information (CUI). ECA PKI will be utilized by the contractor and their subcontractors when transmitting sensitive information via electronic means to/from the .mil domain. Encryption methods shall be utilized for transmitting information in between addresses outside the .mil domain. The contractor shall address these requirements within the Program Protection Implementation Plan (PPIP). (CDRL A0005 Program Protection Implementation Plan (PPIP)) The contractor shall utilize encryption on all e-mail messages containing sensitive information, including but not limited to: For Official Use Only (FOUO) content, Privacy data, Contract Information, Unclassified Technical Data, Accountability Information, Department of Defense (DoD) Sensitive But Unclassified (SBU), and e-mail that discusses any matter that may serve as an OPSEC indicator, per DODI 8520.2. The contractor shall utilize PKI when interacting with DoD PKI enabled information systems; accessing DoD sensitive information on PKI enabled information systems or engaging in any other transactions with DoD PKI enabled information systems requiring data integrity, confidentiality, or non-repudiation of DoD Information. Encryption methods will be utilized when electronically accessing non-Government sites containing sensitive information (for example CITIS access is to be utilized for Message Courier transmission, electronic submittal of CDRL items, and to access internal customer websites). The contractor shall address these requirements within the Program Protection Implementation Plan (PPIP). (CDRL A0005) Program Protection Implementation Plan (PPIP))

8.2.4. CLASSIFIED INFORMATION. All classified information transmitted via electronically by the contractor shall be in compliance with DoD 5220.22-M, “National Industrial Security Program Operating Manual.” The contractor shall address these requirements within the Program Protection Implementation Plan (PPIP). (CDRL A0005) PM03 Program Protection Implementation Plan (PPIP))

8.2.5. INFORMATION ASSURANCE POINT OF CONTACT. The contractor shall provide a counterpart point of contact to the PMA265 Information Assurance Officer (IAO), herein identified as the IA POC. The IA POC shall ensure all Information Assurance (IA) requirements are adhered to. The IA POC will ensure that the contractor team is aware of all IA requirements. The IA POC shall coordinate with the PMA265 IAO in all matters related to IA. The IA POC and all other positions involving IA as defined in DODD 8570.01 and DoD 8570.01-M are considered part of the IA workforce. For this contract the IA workforce is limited to the IA POC. The IA workforce for newly developed programs shall be identified per the requirements in DoDD 8570.01 and DoD 8570.01-M. Personnel in the IA workforce in support of the Government will be required to fulfill the certification requirements of DoDD 8570.01, Information Assurance Training, Certification, and Workforce Management, August 15, 2004, certified current as of April 23, 2007 and DoD 8570.01-M, Information Assurance Workforce Improvement Program, December 19, 2005, Incorporating Change 1, May 15, 2008. All identified Information Assurance WorkForce (IAWF) personnel identified by the contractor are required to be certified with criteria established in DoDD 8570.1 within 12 months of contract award. The contractor shall support entering the IA personnel certification in the personnel system referenced in DoDD 8570.01. The contractor is not required to flow down the requirement for an IA POC certified per DoDD 8570.01 and DOD 8570.01-M to its subcontractors except as described in Section 8.2.6.

8.2.6. CERTIFICATION AND ACCREDITATION. For newly developed systems to be delivered to the Government, the contractor shall coordinate with the Program Manager (PM), Information Assurance Officer (IAO) to determine the Information Assurance (IA) requirements for Certification and Accreditation (C&A), or Platform Information Technology (PIT), as defined in DODD 8500.01E, DoDI 8200.2, DoDI 8520.2, DODI 5000.02, DODI 8580.1, SECNAVINST 5239.3B, OPNAVINST 5239.3A, and OMB A-130, appendix III (reference (v)). This is to include Platform IT systems including all ground-based support systems. The contractor shall also employ all IA controls that are deemed appropriate by the agents listed above. The contractor shall demonstrate the intended IA design features of all systems, software and interfaces to meet the certification standards specified by the cognizant Government agency (DONCIO, NETWARCOM, SPAWAR, PEO(T), and PMA265). The results of certification testing shall be submitted to the Government to support a recommendation to the Designated Approving Authority (DAA) for accreditation or PIT Designation. The contractor shall share the results of certification testing and compliance activities to be utilized in quarterly IA reviews for the purposes of ascertaining the success of the accomplishment of the preceding.

For newly developed systems, the contractor shall provide all pertinent information to comply with Federal Information Security Management Act of 2002 (FISMA) requirements. Newly developed F/A-18 platform information systems that receive, process, store, display or transmit DoD information and which are not connected, interconnected or connected to external networks shall be tested for IA requirements in accordance with the Information Technology Management Reform Act (Clinger-Cohen Act), and DoDD 8500.01E. For newly developed systems, the contractor shall be familiar with and apply the following IA, IT and INFOSEC standards where applicable: Federal Information Security Management Act of 2002 (FIMSA), Information Technology Management Reform Act (Clinger-Cohen Act), NSTISSI No. 1000, No. 7000, No. 7001, DoDI 8500.2, DoDI 8520.2, DoDI 8510.01, DoDD 8500.01E, SECNAVINST 5239.3B, OPNAVINST 5239.3A, DODD 8500.01E, DODD 5000.01, CJCSM 6510.01, CJCSI 6510.01E, and CJCSI 6211.02C. (CDRL A0005) PM03 Program Protection Implementation Plan (PPIP))

8.3 SYSTEM SECURITY

8.3.1. PROGRAM PROTECTION PLAN (PPP). The contractor shall develop, implement, and maintain an Acquisition Program Protection Plan (AP3) in accordance with the Program Protection Plan for the F/A-18E/F and EA-18G Program, dated 14 March 2007. (CDRL A0005) Program Protection Implementation Plan)

8.3.2. PROGRAM PROTECTION IMPLEMENTATION PLAN (PPIP). The contractor shall develop a contractor specific Program Protection Implementation Plan (PPIP) addressing the requirements of the Program Protection Plan (PPP) for the F/A-18E/F and EA-18G Program, dated 14 March 2007. The contractor shall review the PPIP at least annually and update it as required, based on revised information provided by the U.S. Navy, or as a result of changes in the contractor’s procedures. The contractor shall conduct PPIP unique training to personnel with access to sensitive, technical, and CPI information at least annually, to include all contractor developed PPIP requirements and emphasizing the changes in the latest version of the contractor’s PPIP. The contractor shall flowdown this requirement to all subcontractors that have access to CPI information, as defined in the Program Protection Plan for the F/A-18E/F and EA-18G Program, dated 14 March 2007. The contractor shall determine the need for subcontractors without access to CPI information, as defined in the Program Protection Plan for the F/A-18E/F and EA-18G Program, dated 14 March 2007 to develop OPSEC plans. (CDRL A0005 Program Protection Implementation Plan (PPIP))

8.3.3. PUBLIC RELEASE. The contractor shall ensure program related information and graphics intended for public release or posting on internet and World Wide Web sites are processed through the PEO(T) Public Affairs Officer before release. The contractor shall include note pages in all briefings and slide presentations submitted to the PEO(T) Public Affairs Officer/Security Manager for review and release.