Att_1_SOW.docx

N00421-17-R-0047 Page | 25

Section C - Descriptions and Specifications

PERFORMANCE BASED STATEMENT OF WORK

For Naval Test Wing Atlantic Unmanned Aircraft Systems Test Directorate Aircrew, Engineering, Operations, and Scheduling Support Services

1.0 INTRODUCTION (Background)

Naval Test Wing Atlantic (NTWL), an echelon four command of the Naval Air Systems Command (NAVAIR), is a responsible cognizant authority for active test and evaluation (T&E) and participation in all phases of the weapon system life cycle process for unmanned aerial systems. NTWL executes flight management of these activities and air vehicles through authority delegated to the subordinate Air Test and Evaluation Activity. This unit is designated UAS Test Directorate when assigned for command and control by NTWL. The test articles are provided to NWTL and its test activity through several methods. The primary source of assignment is by a major program office for the development, procurement and sustainment of Navy, Marine or Joint Force use systems. However, other sources of assignment of articles subjected to T&E by NTWL are other service components of the Department of Defense, foreign national defense and commercial systems, other US government agencies engaged in flight operations, as well as commercial aviation flight activities. The scope and complexity of these test articles are not limited to full scale air vehicle systems. NTWL provides full system spectrum test capability from complete aircraft down to sub-system components, expendable weapon, sensor, and deception articles and flight worthy software designed to operate and configure the system and its components.

1.1 NWTL is the resource manager charged with reducing the risks associated with the hazards of flight as well as ground operations around flight equipment. The level of risk that will be experienced in the conduct of test flying is expressed in categories ranging from A, B, C and on occasion D (low to high). It is imperative the contractor understand the specialized nature of flight crew support requirements; contractor flight crew must meet and maintain physical requirements of the U.S. Navy. Current OPNAVINST 3710.7 series physical and physiological minimums are required for all aircrew positions. In compliance with NAVTESTWINGLANTINST 3710.7 series, governing Naval Air Warfare Center Aircraft Division General Flight and Operating Instructions is applicable. To mitigate these risks NTWL desires the most qualified, experienced and current personnel within its work force. The work force required to address and mitigate risk involves the application of skills that facilitate the tasks involved with every facet of the test event. These include planning (near and long term, daily, and un-programmed), scheduling (test assets, support facilities and equipment) and test crews (ground and flight)), test article preparation, briefing, pre-flight, flight, post flight, and debrief (including post flight test result analysis and reporting). In addition, gathering metrics related to flight scheduling, aircrew currency and qualification, and resource utilization are considered essential components of the entire flight test risk management system. The requirements of this statement of work include all of these phases and supporting tasks except test article preparation. The complexity of today’s flight test scenarios in the Research, Development, Test and Evaluation (RDT&E) community and the constant changes that are associated with RDT&E flying require constant monitoring, scheduling, frequency management and flight operations coordination.

1.2 The business of flight test presents challenges that typify project management. Unique skills are usually required in an asynchronous manner with peaks and valleys dependent on the perturbations inherent in system acquisition. Additionally, the most desirable human assets to fill these skill requirements are real user group members brought in to the Test Wing after considerable training investment and sacrifice by their fleet communities. NTWL is in constant competition for these resources while worldwide commitment for our military forces remains high, budgets are thin, and fleet units tasked at unprecedented levels. For these reasons, a contracted aviation service work force is feasible, desirable and affordable when considered an investment returned in schedule achieved to get the best equipment out to the Warfighter. In addition, the right contracted work force, one that is already trained, experienced (both in test and warfare specialty), and engrained with the best business practice of process discipline, brings both the opportunity to meet test commitments, and achieve the goal of safe flight operation.

1.3 The following types of funding will be utilized to support this contract:

1.3.1 Research Development Test & Evaluation (RDT&E) funding is used to pay the operating costs of dedicated activities engaged in the conduct of research, development, and test and evaluation efforts performed by a contractor and/or government organization.

1.3.2 Operation and Maintenance, Navy(O&MN) appropriations are used to finance “expenses” not related to military personnel or RDT&E. Types of expenses funded by O&MN appropriations include: DoD civilian salaries, supplies and materials, maintenance of equipment, certain equipment items, real property maintenance, rental of equipment and facilities, food, clothing, and fuel.

2. APPLICABLE DOCUMENTS AND DEFINITIONS

2.1. Abbreviations and Acronyms

2.2 APPLICABLE DOCUMENTS

ASSIST is the official source of DoD specifications and standards and contains the most current information. Users should refer to the ASSIST database at http://assist.daps.dla.mil. The ASSIST Update (a bi-monthly summary of changes to the ASSIST document database) may be viewed or downloaded at http://dodssp.daps.dla.mil.

Unless otherwise specified, the revision level and date for each specification or standard cited for each Program/Project Task (including any specifications or standard cited in any drawing, handbook or referenced specification or standard contained within this contract) shall be that listed in the Department of Defense https://assist.dla.mil/online/start. Single Stock Point for Military Specifications and Standards (DODSSP). Archived copies of the DODISS Notice can be found at: http://dodssp.daps.dla.mil/.

2.3 APPLICABLE INSTRUCTIONS AND NOTICES

2.3.1 OPNAVINST 3710.7 series; NATOPS General Flight & Operating Instructions

2.3.2 CNAFINST 4790.2 series; Naval Aviation Maintenance Program

2.3.3 NAVAIRINST 3710.1 series; Contractors Flight & Ground Operations

2.3.4 NAVAL AIR SYSTEMS COMMAND INTEGRATED SYSTEMS EVALUATION, EXPERIMENTATION AND TEST; Test Planning Handbook.

2.3.5 NAVAIRINST 3710.8 series; Authority for Personnel to Pilot or Fly in Aircraft Under the Controlling Custody of Naval Air Systems Command to Include the Authority for Naval Air Systems Command Personnel to Participate in (Pilot or Fly in) Commercial Aircraft Conducting Aircraft Operations in Support of Test and Evaluation.

2.3.6 NAVAIRINST 3960.4 series; Project Test Plan Policy and Process for Testing of Air Vehicles, Weapons, & Installed Systems

2.3.7 NAVAIRINST 3960.5 series; Policies, Procedures, and Responsibilities for the Naval Air System Command Technical Assurance Board Monitoring of Aircraft Weapon System Development

2.3.8 NAVTESTWINGLANTINST 3710.7 series; Naval Test Wing Atlantic General Flight & Operating Instructions

2.3.9 NASPAXRIVINST 3710.5 series; Air operations Manual, Naval Air Station

2.3.10 Local Directives, Instructions, SOPs, etc., as required by using activity and for execution of the to-do-list (TDL).

3. REQUIREMENTS

3.1 GENERAL REQUIREMENTS

3.1.1 COMPATIBILITY - The Contractor shall maintain the capability to prepare documents and software packages compatible with the Government IT environment through the security classification of Secret. The current operating environment required for this contract includes:

Microsoft Windows 10 Microsoft Project 2010 Microsoft Office Professional Plus 2010 Adobe Acrobat XI (reader) Internet access

The Contractor shall maintain the ability to interface with and transfer data to and from requiring office software applications and their upgraded versions. The Contractor shall maintain virus software and ensure that all media are virus free when delivered. The Contractor shall be capable of Internet and LAN communications with the Government. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with the Government during working hours whether at Contractor work site or on travel.

3.1.2 WORK LOCATIONS AND FACILITIES

3.1.2.1 All work performance specified in this Performance Based Statement of Work (PBSOW) will be accomplished at St. Indigoes Maryland and the occasional off-site maintenance detachments. Alternate work sites may include, but are not limited to, United States Naval and Coast Guard Vessels, and several OCONUS/CONUS land based test related detachments. Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks.

3.1.3 CONTRACT STATUS REPORTING. The contractor shall provide the following documentation.

3.1.3.1 PROGRESS REPORTS (CDRL A001): Progress reports listing continuing work for each program/project task shall be submitted on a monthly basis and delivered to the appropriate codes no later than the 15th of each month. The first report shall be delivered no later than the 15th of the month following the first full month of the contract. The monthly progress reports shall be submitted to the COR and TPOC using Contractor Provided Government Approved Furnished Format and shall be submitted electronically.

3.1.3.2 PROGRAM/PROJECT COST REPORTS (CDRL A002): Cost reports listing continuing work for each program/project task shall be submitted on a monthly basis and delivered to the appropriate codes no later than the 15th of each month. The first report shall be delivered no later than the 15th of the month following the first full month of the contract. The monthly project cost reports shall be submitted to the COR Government Furnished Format and shall be submitted electronically.

3.1.3.3 CONTRACTOR’S FLIGHT AND GROUND OPERATIONS (CDRL A003): Contractors Flight and Ground Operations shall be submitted to the Wing Government Flight Representative (GFR) for approval within 30 days of contract award. Contractor’s Ground Operations must be approved by the GFR prior to first system-level ground evolution and Flight Operations procedures must be approved prior to first flight. GFR reports shall be submitted as required by NAVAIRINST 3710.1 series.

3.1.3.4 FLIGHT QUALIFICATIONS/CURRENCY (CDRL A004): Collect and review personnel flight qualifications and currency in accordance with applicable documents. Maintain daily Personnel Flight Qualifications and Currency. Submit to Operations Officer per Contractor Furnished Government Approved Format no later than 10 working days following end of month.

3.1.3.5 FLIGHT SORTIE BREAKDOWN (CDRL A005): Maintain the flight sortie breakdown report. Submit to Operations Officer no later than 10 working days following end of month. Prepare report per Contractor Furnished Government Approved Format.

3.1.3.6 Mishap Reporting: In performance of this contract the contractor may receive access to privileged information as addressed in OPNAVINST 3750.6 series. The Contractor shall use and examine this information exclusively in performance of this contract. Control and disclosure of this information is delineated in the OPNAVINST 3750.6 series. The Contractor shall indoctrinate all personnel who will have access to such information. These Contractor personnel shall also be informed that they shall not engage in any other action, venture or employment where the information will be disclosed to or used to benefit any party other than the Government furnishing this information. Contractor shall also restrict access to such privileged information to the minimum number of employees necessary for performance of this contract.

3.1.3.7 The Contractor shall notify the COR of any condition that may delay or prevent Contractor’s performance.

3.1.3.8 MISHAP REPORTING: In performance of this contract the contractor may receive access to privileged information as addressed in OPNAVINST 3750.6 series. The Contractor shall use and examine this information exclusively in performance of this contract. Control and disclosure of this information is delineated in the OPNAVINST 3750.6 series. The Contractor shall indoctrinate all personnel who will have access to such information. These Contractor personnel shall also be informed that they shall not engage in any other action, venture or employment where the information will be disclosed to or used to benefit any party other than the Government furnishing this information. Contractor shall also restrict access to such privileged information to the minimum number of employees necessary for performance of this contract.

3.1.3.9 The Contractor shall notify the COR of any condition that may delay or prevent Contractor’s performance.

3.1.3.10 ENTERPRISE-WIDE CONTRACTOR MANPOWER REPORTING APPLICATION (ECMRA): The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Navy via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address:

https://ecmra.mil

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at:

https://doncmra.nmci.navy.mil

3.1.3.11 NMCI INFORMATION REPORT. The contractor shall provide an updated monthly report covering Each Contractor with NMCI access or assets. The report is required to include the following (CDRL A006):

User Information: Last name/ First name/ Middle name/10 digit EDIPI # from ID card/Cyber Awareness Training Date/SAAR-N on file? And year/Complete NMCI email Address/Complete Company/Alternate Email Address.

Contract Information: COR Name/TPOC/Contract #/Delivery or Task Order #/PMA Program Supporting Location Information: FULL Building street address/City, State/Zip code/Building number/Floor/Room /Cube if applicable/Telephone number.

Funding Information: BFM Name Providing Funding Type/BFM Email Address/BFM Phone Number Existing/Current Information: NMCI Computer Name/NMCI Asset Tag#/ NMCI Service Tag#/ Wall jack number/Network Jack/ Who is assigned to this computer?/ Is this computer shared with others?/ List individuals you are sharing with.

3.1.4 WORK SCHEDULE, OVERTIME, HOLIDAYS, AND INSTALLATION CLOSURE.

3.1.4.1 WORK SCHEDULE:

The above stated hours are general operating hours for UASTD. A Compressed Work Schedule (CWS) is authorized, however, the government reserves the right to discontinue or adjust the CWS schedule; the contractor will be given a 30 day notice if this schedule is discontinued. The Government reserves the right to adjust days/hours of operation to meet the needs of test programs. All changes will be provided by the Chief Test Pilot and Technical Director. When the need for Weekend/Holiday flight operations arises, notice will be given by UASTD Operations to the Contractor.

3.1.4.2 OVERTIME: Overtime is anticipated. If required, overtime must be authorized by the TPOC/COR. The Contractor shall not work any overtime without approval by the TPOC/COR. The Contractor shall provide an estimate for approval to the TPOC/COR of OT hours required for any projected overtime effort. Contractor use of overtime and payment for overtime must be handled in accordance with FAR 52.222-2 and 52.222-4.

3.1.4.3 HOLIDAYS: The Government observes the following holidays:

New Year’s Day, January 1 Martin Luther King’s Birthday, the third Monday in January President’s Birthday, the third Monday in February Memorial Day, the last Monday in May Independence Day, July 4 Labor Day, the first Monday in September Columbus Day, the second Monday in October Veteran’s Day, November 11 Thanksgiving Day, the fourth Thursday in November Christmas Day, December 25

With the exception of the events in section 3.1.4.5 below, the contractor is permitted to observe the above Holidays in accordance with its corporate policy. In the event any of the above holidays occur on a Saturday or Sunday, or CWS alternate Friday, then such holiday shall be observed in accordance with COR concurrence.

3.1.4.4 INSTALLATION CLOSURE: When Federal employees are officially excused from work due to a holiday or a special event, severe weather, a security threat, or any other Government facility related problem that prevents Federal personnel from working at the Government facility, contractor personnel assigned to work at that facility performing non-mission essential work in support of such Federal employees shall follow their parent company’s policies

3.1.4.5 While generally contractor personnel may not perform work on-site at a Government facility without supervision from Federal personnel, in very limited circumstances, work being performed by contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the Government facility despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant Contracting Officer must concur with any determination that work being performed by contractor personnel is mission essential.

3.1.4.6 COMPRESSED WORK SCHEDULE (CWS) is an alternative work schedule to the traditional five 8.5 hour workdays (which includes a 30-minute lunch) worked per week. Under a CWS schedule, an employee completes the following schedule within a two-week period of time: eight weekdays are worked at 9.5 hours each (which includes a 30-minute lunch), one weekday is alternately worked as 8.5 hours (which includes a 30-minute lunch) and one weekday is not worked by the employee. The result is 80 hours worked every two weeks, with 44 work hours one week and 36 work hours the other. A Compressed Work Schedule (CWS) is authorized.

3.1.5 CONTRACTOR PROCESS FOR APPROVAL OF TRAVEL, MATERIAL, and OTHER DIRECT CHARGES (ODC): The Contractor shall have an electronic or web process for submission of travel requests, material purchases or ODCs to submit to COR for approval.

3.1.5.1 TRAVEL ORDERS - The Contractor shall prepare and submit to the COR for approval travel requests for all personnel authorized to perform off-site support. Travel requests shall be submitted electronically. All travel and Government billeting shall be in accordance with the Federal Travel Regulations and the Joint Travel Regulations (if Applicable) (http://www.defensetravel.dod.mil/site/travelreg.cfm). The Contractor shall be responsible for making all car/truck rental, airfare, and lodging and subsistence arrangements. All Travel costs will be on a reimbursable basis and funded separately. The Government shall reimburse the Contractor for travel and per diem. Contractor shall return all receipts for expenses incurred, or the contractor shall not be reimbursed. Travel may include general and administrative expenses, but shall not include profit. Travel authorization request shall be prepared in accordance with the sample in Section J, Attachment 11 and submitted no less than 5 business days prior to travel for COR approval.

3.1.5.2 MATERIAL: Prior written approval of the COR shall be required for all purchases of materials. If the contractor’s proposal includes a list of materials with associated prices, then the (COR’s/ACO/PCO as applicable) acceptance of the contractor’s proposal shall constitute written approval of those purchases. Any material provided by the contractor is subject to the requirements of the Federal Acquisition Regulation (FAR), the Defense Federal Acquisition Regulation Supplement (DFARS), and applicable Department of the Navy regulations and instructions. All materials not depleted during the performance of this contract shall become Government property upon completion of this contract. The contractor shall transfer all materials not depleted to the COR by way of Material Inspection and Receiving Report (DD Form 250). Other Direct Charges may include general and administrative expenses but shall not include profit.

3.1.5.2.1 The costs of general purpose business expenses required for the conduct of the contractor’s normal business operations are not an allowable direct cost in the performance of this contract. General purpose business expenses include, but are not limited to, the cost for items such as telephones and telephone charges, reproduction machines, word processing equipment, personal computers and other office equipment and office supplies.

3.1.6 SUBCONTRACTORS:

3.1.6.1 Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this contract. All provisions of this PWS/SOW shall flow down to subcontractors providing support under this contract

3.1.7 MANAGEMENT OF CONTRACTOR PERSONNEL:

3.1.7.1The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees. The contractor shall manage its employees and guard against any actions that are of the nature of personal services, or give the perception of personal services.

3.1.8 TRANSITION STRATEGY: The overall strategy shall be built around maintaining the mission of UASTD with minimal impact, not only in terms of timeliness of performance but also to ensure that critical data and knowledge transfer occurs. Upon termination or expiration of the contract, the contractor shall ensure an orderly transition of responsibilities, while minimizing impact to the operation. The contractor shall submit a Transition Out Plan, to include the minimum elements listed below.

3.1.8.1WORK TURNOVER: The contractor shall provide a plan of action to effectively transfer tasked work that is in process at the expiration or termination of the contract to the successor company. Establish and maintain effective communication with the incoming contractor or Government personnel for the period of transition via weekly status meetings.

3.1.8.2 QUALITY ASSURANCE: The contractor shall provide a plan of action to ensure continuation of quality review processes during the transition period to the successor company.

3.1.8.3 RISK MITIGATION STRATEGIES: The contractor shall provide a plan of action to mitigate contract performance risks (quality and schedule) encountered during the transition period.

3.1.8.4 DATA/INFORMATION TRANSFER: The contractor shall provide a plan of action for the efficient inventory and transfer of program data to the successor company.

3.2 SECURITY

3.2.1 CITIZENSHIP REQUIREMENTS: Only U.S. citizens may perform under this contract. If the Contractor cannot find qualified U.S. citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:

a. The individual's name, date and place of birth, position title, and current citizenship.

b. A statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements.

c. A statement of the unusual expertise possessed by the applicant.

d. A statement that access will be limited to a specific government contract (specify contract number).

e. A statement that the Contractor has obtained an export license for the information required to perform the contract.

3.2.2 INVESTIGATIVE REQUIREMENTS:

Investigative requirements for Department of Navy (DON) contractor personnel requiring access to classified information are managed under the National Industrial Security Program (NISP). During performance of this contract, the Contractor will require access to Government facilities or installations; and/or to Department of Defense (DOD) Information Technology (IT) systems including networks to perform sensitive or non-sensitive duties. The Contractor shall flow the following requirements down in all subcontracts when the Subcontractor will be required to have access to Government facilities or installations; and/or to a DoD IT systems including networks to perform sensitive or non-sensitive duties in support of this contract. In accordance with SECNAV M-5510.30, DON Personnel Security Program Non-NISP investigations will be conducted for Contractors and its Subcontractors requiring access to Government facilities or installations, Common Access Card (CAC), and IT-I or IT-II level system network access, but who do not require access to classified information. All Contractor personnel that require access to DON information systems and/or work on-site, but do not require clearance eligibility, are designated Non-Critical Sensitive for IT-II system access or Critical Sensitive for IT-I system access. Non-NISP adjudications are completed by the DOD Consolidated Adjudication Facility (DOD CAF) in accordance with SECNAV M-5510.30.

The Contractor shall conform to the security provisions of SECNAVINST 5510.30, DoD-8570.01M, Information Assurance Workforce Improvement Program, /DoD Directive -8140.01 Cyberspace Workforce Management, and the Privacy Act of 1974. The Contractor shall ensure their personnel can possess and maintain the appropriate background investigation, and are certified/credentialed for the Information Assurance Workforce (IAWF)/Cyber Security Workforce (CSWF), as applicable. At a minimum, the Contractor shall validate that the background information provided by its employees charged under this contract is correct, and the employee shall hold a favorable determination. In accordance with DoD Directive 8570.01, Contractor personnel shall meet requirements in DOD 8570.01M for task order performance as applicable to the work being performed.

3.2.2.1 Background Vetting: Non-NISP investigations shall be conducted using the Questionnaire for National Security Positions (SF-86) Form for the SSBI and the NACLC review, as applicable. The contractor employee shall submit the completed SF-86 to the local Navy Command Security Office. The Contractor employee shall provide any and all mitigating information to clarify derogatory information that may be present on their SF-86 at the time of submission. The local Navy Command Security office will review the SF-86 for a local access determination pending a final determination by DOD CAF.

If an unfavorable adjudication is determined by DOD CAF all access will be terminated. The contractor employee is afforded due process to attempt to mitigate any derogatory information that is listed as a concern by the DOD CAF in accordance with DOD 5200.2-R.

3.2.3 COMMON ACCESS CARD (CAC)/PUBLIC KEY INFRASTRUCTURE (PKI), SYSTEM AUTHORIZATION ACCESS REQUEST (SAAR-N).

3.2.3.1 SAAR-N: All contractor personnel requiring access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR-N) Form OPNAV 5239/14 (Rev Sep 2011) on file, and complete required Annual Information Awareness Training. New employees must submit their SAAR forms within thirty (30) days of their first day of work. Instructions for processing the SAAR-N forms are available at: http://www.cnrc.navy.mil/publications/Forms/OPNAV_5239_14_SAAR_N.pdf.

SAAR-N forms shall be submitted to the Contracting Officer’s Representative (COR), Government Technical Point of Contact (TPOC), or to the assigned government Trusted Associate Sponsorship System (TASS) Trusted Associate.

3.2.3.2 COMMON ACCESS CARDS (CAC) / LOCAL BADGES: Contractor CACs and facility specific identification badges will be issued by the Government to on-site contractor personnel and shall be visible at all times while personnel are at the Government site. The contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to all instructions/guidance required by the facility. All CACs and identification badges issued to Contractor employees shall be returned to the Government Security Department at the Government site in accordance with the instructions/ guidance required by your facility following completion of the contract, relocation or termination of an employee, or upon request from the Contracting Officer’s Representative. The Government will provide the contractor access to Government facilities, as required, for performance of tasks under this contract. Contractor personnel shall comply with the instructions/ guidance required by your facility.

3.2.3.3 DD-254: The contractor shall comply with security requirements specified in the DD-254 attached to this contract. Information or data that the contractor accesses shall be handled at the appropriate classification level, unclassified information shall be handled as “For Official Use Only” and safeguarded IAW DoD 5200.01, Vol. 4, “DoD Information Security Program: Controlled Unclassified Information (CUI). Distribution is authorized to the Requiring Office’s Organization and supported Activity only. Other requests for deliverables under this contract shall be referred to the TPOC/COR of this contract for approval.

3.2.4 INFORMATION SECURITY: If the work is performed at the Contractor’s facility, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and controlled unclassified information (CUI) and to control distribution of CUI in accordance with 5200.01 Vol. 4. If the work is performed at the Government’s facility, the Contractor shall comply with the Facilities Instructions/Guidance, the latest applicable Program Protection Plan(s) and applicable Security Classification Guide(s).

3.2.4.1 MARKING: All information generated by the Contractor shall be properly marked. For Official Use Only information generated and/or provided under this contract shall be marked in accordance with DoDM 5200.01. Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings in accordance with DoDD 5230.24 and program applicable Security Classification Guidance.

3.2.4.2 PUBLIC RELEASE: No information pertaining to this contract shall be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by the appropriate U.S. government authority. Proposed public releases shall be submitted for approval prior to release through NAS Patuxent River Public Affairs Office. Briefing / Debriefing. Upon reporting to the Test Squadron, contractor personnel, assigned for a period in excess of 30 days are required to attend Squadron security and safety orientations provided by the Security Officer and the Safety Officer. The orientations are to provide the contractor personnel with awareness of basic requirements for protection of individuals, classified information and the procedures that coincide. Applicable instructions will be used as the basis for the orientation and the contractor shall comply with the information within these instructions regardless of the timeframe onsite.

3.2.4.3 For contractor personnel assigned for a period in excess of 30 days, an exit debriefing is required from the Security Officer and the Safety Officer when they depart.

3.2.4.4 Identification of Contractor Personnel. Corporation affiliation shall be referenced on all written documentation that refers to contractor personnel. This is required for internal and external communication. Similarly, the contractor affiliation shall be identified at the beginning of any meeting or conference where contractor personnel are in attendance. Proper identification of Squadron contractor personnel is required. All Squadron contractor personnel must wear an official badge issued by NAS Security Department while occupying Government spaces.

3.2.4.5 If a contractor is to support a squadron for over 90 days, a Common Access Card (CAC) will be issued from the appropriate NAS Security Office. The badge shall not have an expiration date that exceeds the expiration date of the contract.

3.2.4.6 If a contractor is to support a squadron for 90 days or less, a CAC or E-CAC will be issued from the appropriate NAS Security Office. The badge shall have the expiration date that shall coincide with the expiration date of the individual’s tenure at the squadron while working under a contract.

3.2.4.7 Loss, Compromise and/or Electronic Spillage of Classified or Controlled Unclassified Information: All instances of loss, compromise and electronic spillage of classified or controlled unclassified information shall be reported to the COR, TPOC and Government Security Office within 24 hours of the incident occurring.

3.2.5 OPERATIONS SECURITY (OPSEC):

The Contractor shall develop, implement and maintain a facility level Operations Security (OPSEC) program that entails security procedures and controls to prevent unauthorized disclosure and control the distribution of controlled unclassified and classified activities, information, equipment, and material used or developed by the Government, Contractor and any Subcontractor during performance of the contract (While performing aboard NAVAIR or NAVAIR sites, the contractor shall comply with the provisions of OPNAVINST 3432.1A, the local Command/Facility OPSEC policies, as well as any procedures identified in Program-Specific Operations Security Plans, and Program Protection Plans (PPP) as applicable).

These procedures shall be in accordance with the DoD 5220.22-M National Industrial Security Program Operating Manual (NISPOM) and the DoD Information Security Program and Protection of Sensitive Compartmented Information (SCI) (DoDI 5200.01). All controlled unclassified information (CUI) shall be appropriately identified and marked as For Official Use Only (FOUO) in accordance with DoD 5200.01, Information Security Program: Controlled Unclassified Information (CUI) Volume 4 and DoD 5400.7-R (Freedom of Information Act Regulation) (Chapter 3). All Contractor facilities shall provide an appropriate means of storage for controlled unclassified and classified documents, equipment and materials in accordance with OPSEC requirements.

The Contractor shall practice OPSEC IAW the following policies:

The Contractor shall maintain an effective OPSEC program that implements countermeasures to protect critical information (CI) and other sensitive unclassified information and activities, , especially those activities or information which could compromise classified information or operations, or degrade the planning and execution of military operations performed or supported by the contractor in support of the mission. While performing aboard NAVAIR or NAVAIR sites, the contractor shall comply with the provisions of OPNAVINST 3432.1A, the local Command/Facility OPSEC policies, as well as any procedures identified in Program-Specific Operations Security Plans, and Program Protection Plans (PPP) as applicable.

3.2.6 ANTI-TERRORISM FORCE PROTECTION AND EMERGENCY MANAGEMENT:

The work performed on this contract is not Emergency Essential in accordance with OPNAVINST 3440.17A and Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans. Contractor personnel shall comply with all Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans and directives. Contractor personnel shall not report for work at Government facilities upon declaration of Force Protection Condition CHARLIE or in any event or emergency where Government officials direct curtailment of operations to “Mission Essential Only”. All Contractor personnel assigned to a government facility shall complete annual Antiterrorism (Level One) and Active Shooter training.

3.2.7 TELEWORK

Telework will be permissible on a case by case basis depending on the circumstances. However, the Contractor is responsible for ensuring that telework does not interfere with the normal operations and performance of the contract.

3.3 PURPOSE AND SCOPE

The contractor shall perform the following tasks in accordance with the flight schedule and applicable policies and directives as defined and aligned to the appropriation type funding at award of the IDIQ Contract and Task Orders.

3.3a RDT&E appropriations are associated with Research and Development efforts that require aircraft, aircraft mission systems, and weapon system development. RDT&E efforts may include efforts such as flight test engineering, flight technical support, flight and ground tests, administrative support, functional check flights, flight and maintenance support dynamic studies, impact studies and testing such as Hazard of Electromagnetic Radiation to Ordnance (HERO), Electromagnetic Compliance (EMC), and Electromagnetic Interference (EMI) for Groups 1-4 UAS type Unmanned Air Vehicles. RDT&E appropriations may apply to paragraphs 3.3.1 through 3.3.21 only during the RDT&E life-cycle phase efforts.

3.3b O&M, (Navy (N) and Marine Corp (MC)) appropriations fund aircraft, aircraft mission systems, and weapon system operations required to maintain combat ready forces necessary to respond to national objectives in Joint, Naval and Combined operations. The functions under this effort are in direct support of the operational effort supporting the aircrew and flight test. O&M efforts may include efforts to support aircraft operations such as aircrew functions, sustainment engineering, flight and ground test dynamic and impact studies, administrative support, functional check flights for Groups 1-4 UAS type Unmanned Air Vehicles. O&M appropriations may apply to paragraphs 3.3.1 through 3.3.21 only during the sustainment (Operations and Maintenance) life-cycle phase efforts.

3.3c Overseas Contingency Operations (OCO)appropriations support functions under this effort which are in direct support of the operations for currently deployed forces and equipment. Groups 1-4 UAS type Unmanned Air Vehicles may utilize OCO appropriations for aircraft, aircraft mission systems, and weapon system operations required to maintain combat ready forces necessary to respond to national objectives in Joint, Naval and Combined operations. The functions under this effort are in direct support of the operational effort supporting the aircrew and flight test. OCO efforts may include efforts to support aircraft operations such as aircrew functions, sustainment engineering, flight and ground test dynamic and impact studies, administrative support, functional check flights. OCO appropriations may apply to paragraphs 3.3.1 through 3.3.21 only during efforts in direct support of Overseas Contingency Operations.

3.3d Aircraft Procurement Navy (APN) appropriations are used to support operations and administrative efforts required to support aircraft and aircraft system acquisition, system test and evaluation to include modification to align to service requirements, major service life extension programs of the Groups 1-4 UAS type Unmanned Air Vehicles. APN efforts may include efforts to support aircraft, aircraft mission systems, and weapon system operations such as aircrew functions, engineering, flight and ground test dynamic and impact studies, administrative support, and flight and ground test and functional check flights in support of the acquisition life-cycle phase. APN funding may apply paragraphs 3.3.1 through 3.3.21 only during efforts in direct support of procurement functions.

3.3.1 FLIGHT TEST SUPPORT As aligned to the appropriations defined in paragraphs 3.3a, 3.3b, 3.3c, or 3.3d CLINS X001-X036)

3.3.1.1 Provide Test Flight Support and Conduct Category A and B, and when determined by the Commanding Officer, Category C and D flying and weapon system operations, flight test engineering, navigation, flight technical support, flight and ground tests, administrative flights, training flights, functional check flights, mission systems, performance, flying qualities, ordnance, HERO, Electromagnetic Compliance (EMC), and EMI support in Groups 1-4 UAS type, model and series provided by the government. Additionally, the contractor shall participate in evaluations of flight simulation devices such as operational flight trainers, weapon system trainers, position/tactics trainers, scenario development, mission planning and flight crew brief and debrief or any other simulation device for an air vehicle. The contractor shall coordinate with test data analysis to access quick-look data results and evaluate reduced flight test data to assess progress being made in achieving flight test objectives. Contractor category aircrew A and B (or C and D when mission requirements dictate) aircrew pilot, test flight officer, flight test engineer, navigator, in-flight technician, aircrewman/crew chief, and sensor operator, Air Vehicle Operator (AVO), Mission Payload Operator (MPO) and Flight Coordinator conduct mission preflight planning, in-flight system operation and data collection, analysis of flight test data, coordination of test data gathering, assist in the preparation of test plans and test progress reporting in support of the flight test team. Reporting will include test program status, progress made to date, and inputs to future test team objectives.

3.3.1.2 Pre-Mission Flight Planning. The contractor shall provide aircrew preflight planning for test missions as coordinated with mission briefers and engineering test team members. Preflight planning shall include, but not be limited to: obtaining current, enroute and forecast weather for the flight; completing appropriate flight planning and flying requirements; and outlining crew duties, communications plans, test procedures, test data cards, and safety of flight requirements. Additionally, the contractor shall prepare preliminary inputs for preflight data packages and data requirements.

3.3.1.3 Air Vehicle Operations. The contractor shall operate the assigned aircraft, associated systems and instrumentation using proper and thorough preflight, in-flight, and post-flight procedures in compliance with the Naval Aviation Training and Operations Procedures Standardization (NATOPS) program or other flight operations procedures manuals provided by other DoD or commercial systems authorities for vehicles and systems under evaluation.

3.3.1.4 The contractor aircrew / ground launch and recovery crew shall comply with all policies for the operation of and qualification within the NAVAIRSYSCOM aviation competency and Naval Aviation program as prescribed in the Applicable Documents listed in paragraph 3.0.

3.3.1.5 In-flight Test Engineering Support. The contractor shall provide in-flight test engineering support through the completion of mission tasks assigned by the test director and operation of assigned data collection equipment. The contractor shall verbally present the data, and provide a written narrative report for discussion and submission during the post-flight debrief.

3.3.1.6 Test Data Collection. The contractor shall support test data collection compilation efforts by ensuring that data items collected are retrieved, annotated and delivered to test data analysis facilities. The contractor shall draft inputs for test progress reports via contractor provided government approved form.

3.3.1.7 System Assessment. The contractor shall assess the performance of the system undergoing testing. The contractor shall compare system performance to specifications and analyze design problems noted with the proposed system implementation. The contractor shall deliver draft recommendations for system deficiency reports within 15 calendar days of discovery of Part II or III deficiencies and within 5 calendar days of discovery of Part I deficiencies (NAVAIRINST 3960.5 series germane).

3.3.2 SIMULATOR SUPPORT (As aligned to the appropriations defined in paragraphs 3.3a, 3.3b, 3.3c, or 3.3d CLINS X001-X036)

3.3.2.1 Provide AVOs and MPOs for acquisition, development, test, evaluation, and acceptance of simulators including Operational Flight Trainers, Weapons System Trainers, and other aviation training devices to include, but not limited to: attending simulator system requirements reviews (SRR), preliminary design reviews (PDR), critical design reviews (CDR), design working groups; providing technical analysis of issues, report meeting results, analysis of significant issues and recommendation in a trip report per Government Furnished Format; review of simulator…