ATT_1_SOW_Draft.docx

N00421-17-R-0066

PERFORMANCE BASED STATEMENT OF WORK (PBSOW)

NAVAL TEST WING ATLANTIC (NTWL)

AIRCREW 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 fixed, rotary wing, unmanned aerial and lighter-than-air vehicles. NTWL executes flight management of these activities and air vehicles through authority delegated to subordinate Air Test and Evaluation Squadrons (VX/HX). These units are designated VX-20, HX-21, VX-23, USNTPS and the Carrier Vehicle Suitability competency (AIR-5.1.6) or others when assigned for command and control by NTWL. The test articles are provided to NWTL and its squadrons 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 for 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. The following Periods of performance apply to this PBSOW:

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. 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. (There are three categories of flight personnel described in OPNAVINST 3710.7 series: 1. Aircrew (Pilot, Naval Flight Officer, Navigator, Flight Engineer, Observer, Loadmaster and Photographer.); 2. Selected Passenger; 3. Project Specialist. 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. Supporting tasks related to flight scheduling, aircrew currency and qualification, administration, facilities, security and resource utilization are considered essential components of the entire flight test risk management system. The requirements of this statement of work include all labor positions necessary in supporting the flight test mission. 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.

2. APPLICABLE DOCUMENTS AND DEFINITIONS

2.1 REFERENCE DOCUMENTS

All work performed by the contractor shall be accomplished in accordance with applicable publications, technical directives, instructions, standards, and procedures contained in pertinent manuals using blueprints, drawings or schematics as provided by each work location.

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/.

NAVAL AIR SYSTEMS COMMAND INTEGRATED SYSTEMS EVALUATION, EXPERIMENTATION AND TEST

Test Planning Handbook

Local Directives, Instructions, SOPs, etc., as required by using activity and for execution of TDL.

2.2 ABBREVIATIONS AND ACRONYMS

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 state-of the-art 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 Geographic place of performance: 85 to 100 percent of this effort, not including temporary assigned duties or travel, is conducted on the Patuxent River, MD Naval Air Station (NAS) or nearby facilities in the respective program and competency office buildings, or hangar locations. The remaining 0 to 15 percent of the ISEET effort may be performed at other government sites. The following tenet commands locations will encompass a majority of the requirements of this contract:

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 MONTHLY PROGRESS AND FINANCIAL STATUS REPORT: The contractor shall provide a progress and financial status report in accordance with the Contract Data Requirement List. The Funds Expenditure and Progress report shall include work accomplished since submittal of the last report, both monthly and cumulative man-hour labor costs expended by labor category and material, travel costs and detailed invoices.

3.1.3.2 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://doncmra.nmci.navy.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.4 WORK SCHEDULE TO INCLUDE COMPRESSED WORK SCHEDULE (CWS), OVERTIME, HOLIDAYS, AND INSTALLATION CLOSURE.

3.1.4.1 WORK SCHEDULE:

Above is a work schedule example, the individual tenet locations that will be receiving services will determine the work schedules for their establishment. The Contractor will have to follow the individual schedules from each location.

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 to be discontinued. The Government reserves the right to adjust days/hours of operation to meet the needs of the individual locations or test programs.

3.1.4.2 COMPRESSED WORK SCHEDULE (CWS): 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.

3.1.4.2.1 The Contractor, with agreement by the COR/ACOR, may allow its employees to work a CWS schedule. If the Contractor chooses to allow its employees to work a CWS schedule in support of this contract, any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the Government. Additionally, the CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage when required by the Government. If agreement to implement the CWS schedule is reached with the COR, the overall schedule must be provided and approved. Key contractor personnel, at the discretion of the COR, may not be allowed to work a CWS schedule even if the remaining employees are permitted to do so.

3.1.4.3 OVERTIME: The contractor shall not work any overtime (OT) without prior approval by the TPOC/COR. The contractor shall provide an estimate of number of OT hours required for the OT effort.

3.1.4.4 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 direction.

3.1.4.5 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

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.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 Department of Defense Joint Travel Regulation (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 travel request, 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.3 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. The government will provide necessary office space, ADP equipment to include NMCI seats required office equipment and supplies, and access to telephone/fax machine for official business calls.

3.1.6 SUBCONTRACTORS: 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: The 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.

3.2.4.3 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.

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 HANGAR SPACES SECURITY: The Contractor shall coordinate and ensure the provision of security badges required to allow Contractor personnel access to designated workspaces; the Contractor shall comply with all applicable security requirements, abide by direction given by Military Police or other security personnel, and adhere to installation traffic laws. Personnel occupying positions that require a Secret Security Clearance shall meet that requirement prior to being placed in that position. The DD Form 254, DoD Contractor Security Classification Specification is required and will be completed and submitted to the PCO.

3.3 PURPOSE AND SCOPE

3.3.1 APPLICABLE SYSTEMS

This Performance Based Statement of Work (PBSOW) is intended to service aircrew assigned to any air vehicle system, sub-system, component or aviation operation process selected for test and evaluation or T&E support (refueling, transportation related to T&E, chase, target, etc.) by NAVAIR INST 3710.8.

3.3.2 PERFORMANCE REQUIREMENTS (X001)

The contractor shall:

3.3.2a RDT&E funding is associated with as described in section 3.3.1 in accordance with the appropriate publications, directives, and best practices to ensure Aircrew have the support necessary to ensure all administrative functions are available to complete their flight missions. The aircraft support concept is primarily Organizational (O) level; however, Limited Intermediate (I), and Limited Depot (D) level maintenance are prospective activities under this contract. The functions under this effort are in direct support of the administrative functions necessary for aircrew to fly aircraft supporting RDT&E missions. RDT&E appropriations may apply to primary paragraphs and all sub-paragraphs associated 3.3.2.1.1 through 3.3.2.1.8.1, 3.3.3.1 through 3.3.3.18.1, and 3.6.1 through 3.6.4.

3.3.2b OM&N funding primarily supports aircraft Organizational (O) level; however, Limited Intermediate (I), and Limited Depot (D) level maintenance are prospective activities under this contract. The functions under this effort are in direct support of the operational effort supporting the aircrew and flight test. OM&N appropriations may apply to all primary paragraphs and all sub-paragraphs associated with management functions to include policy development and guidance; management and distribution of resources; program performance review and evaluation; planning, programming and budgeting; travel of personnel; and other direct expenses. The following paragraphs and subparagraphs can be funded by OM&N 3.3.2.1.1 through 3.3.2.1.8.1, 3.3.3.1 through 3.3.3.18.1, and 3.6.1 through 3.6.4.

3.3.2c APN funding supports the necessary functions to ensure the squadron operations and administrative functions are available to maintain Flight Test and Evaluation. The support positions on this contract ensure all aircrew assigned to any air vehicle system, sub-system, component or aviation operation process selected for test and evaluation or T&E support (refueling, transportation related to T&E, chase, target, etc.) can complete the missions ensuring continuous testing to be scheduled and available. The following paragraphs and subparagraphs can be funded by APN 3.3.2.1.1 through 3.3.2.1.8.1, 3.3.3.1 through 3.3.3.18.1, and 3.6.1 through 3.6.4.

3.3.2.1 SQUADRON OPERATIONS AND FLIGHT ADMINISTRATION

3.3.2.1.1 AIR REFUELING (AR) FLIGHT SCHEDULING (RDT&E, OM&N, APN)

3.3.2.1.1.1 Compile and prepare the monthly, weekly, and daily flight schedules. Coordinate aircraft schedules with VX-23, AR Program Manager, and any other organization requesting services of AR aircraft. Provide scheduling support to coordinate aircraft availability to facilitate maintenance, modifications and equipment installation/removal. Draft fuel report must be submitted per Government Furnished Format to Operations and Platform Coordinator no later than the 15th of each month. Government furnished format. CDRL A001.

3.3.2.1.2 ADMINISTRATIVE SUPPORT (RDT&E, OM&N, APN)

3.23.2.1.2.1 Prepare aircrew designation letters, NATOPS certification forms for aircrew and instrument rating forms for aircrew. Prepare documentation and follow-up on aircrew and flight safety correspondence for the Squadron Operations and Safety Officers.

3.3.2.1.3 SQUADRON AIRCRAFT SCHEDULING (RDT&E, OM&N, APN)

3.3.2.1.3.1 Compile and prepare the daily flight schedules. Coordinate aircraft schedules with the Platform Coordinators and other organizations requesting services of support aircraft. Government furnished format. CDRL A002.

3.3.2.1.4 LIAISON WITH OPERATIONS ACTIVITIES (RDT&E, OM&N, APN)

3.3.2.1.4.1 Coordinate platform operations scheduler information. Maintain liaison with external agencies such as Air Operations, Federal Aviation Administration (FAA), Fleet Area Control and Surveillance Facility, Virginia Capes Operating Area (FACSFAC VACAPES), and other NAVAIRSYSCOM activities. Provide briefings to aircrew, as required, concerning matters of changes to airspace procedures, instrument procedures, Federal Air Regulations, Flight Information Publication (FLIP) and Foreign Clearance Guide (FCG) program and local facilities and procedures. Coordinate Prior Permission Requests (PPR's) for incoming aircraft and visiting aircrew. Coordinate scheduling of CNAF assets as required in support of ground and flight testing.

3.3.2.1.5 PROCESS MESSAGES AND OTHER INCOMING DOCUMENTS (RDT&E, OM&N, APN)

3.3.2.1.5.1 Review Navy messages on the Message Dissemination Subsystem. Maintain historical files on all naval messages and other documents that are related to operations and safety. Extract those documents that relate to Squadron type aircraft and those documents reflecting engineering investigations, publication changes, technical changes, reviews recommendations, Quality Deficiency Reports, NATOPS information, and other operational and safety related materials.

3.3.2.1.6 CREW RESOURCE MANAGEMENT (CRM) (RDT&E, OM&N, APN)

3.3.2.1.6.1 Coordinate qualification and documentation of annual CRM Training per OPNAVINST 3710.7 series.

3.3.2.1.7 COMPUTERIZED FLIGHT SCHEDULING SYSTEM (RDT&E, OM&N, APN)

3.3.2.1.7.1 Use, trouble shoot, and administer the Flight Information Scheduling and Tracking system (FIST). Support shall include all aspects of the system and not be limited to the flight schedule portion. Establish and maintain a process to include, but not be limited to; on-site testing, liaison with programmers to assist in the resolution of program deficiencies, coordination of team inputs, and initiation of upgrades to systems and reports of progress.

3.3.2.1.8NAVAL AIR TRAINING AND PROCEDURES STANDARDIZATION (NATOPS) PROGRAM SUPPORT (RDT&E, OM&N, APN)

3.3.2.1.8.1 Enter and verify flight statistics and data for flight personnel qualifications to include expiration dates and other relative information. Maintain the command NATOPS publications inventory and distribute all changes and updates. Perform semi-annual in-house audits on NATOPS training records and corroborate the FIST program records for accuracy and completeness with the Squadron training records and applicable instructions. Schedule aviation physiology training for all military, civil service, and contractor personnel to ensure they are qualified to fly in Squadron aircraft. Assist the Platform Coordinators in preparation for each of the model manager unit evaluation that is conducted both on and off-site. Distribute Naval message traffic and safety hazard reports to all aircrew and monitor the message data system for relevant Naval messages concerning operational and NATOPS information.

3.3.3 TECHNICAL SUPPORT AND SCHEDULING OF AIRCRAFT

The contractor shall provide the following technical effort to support the scheduling, coordination, and safety requirements of the Platform Coordinator/Team Leader/Competency in accordance with applicable documents in PBSOW 3.0.

3.3.3.1 DAILY AIRCRAFT STATUS (RDT&E, OM&N, APN)

3.3.3.1.1 Compile and disseminate information on the status of assigned aircraft. This information shall indicate the status of the aircraft by bureau number and type, and will be distributed daily via the inter/intra-departmental computer network mail system. Government furnished format. CDRL A003.

3.3.3.2 AIRCRAFT UTILIZATION (RDT&E, OM&N, APN)

3.3.3.2.1 Track utilization of aircraft for the prior week and determine projected utilization for the upcoming week through usage of the available database and inputs from project personnel. Provide a capsulated summary report to Squadron Operations. Submit per Government Furnished Format to Operations and print/post by each Wednesday at 0900. CDRL A004.

3.3.3.3 FLIGHT QUALIFICATIONS/CURRENCY (RDT&E, OM&N, APN)

3.3.3.3.1 Collect and review personnel flight qualifications and currency in accordance with applicable documents. Maintain daily Personnel Flight Qualifications and Currency. Submit per Government Furnished Format no later than 10 working days following end of month. CDRL A005

3.3.3.4 PROJECT SCHEDULES PLANNING (RDT&E, OM&N, APN)

3.3.3.4.1 Determine aircraft, facilities and personnel availability in addition to overall program milestones through the attendance of classified and unclassified conferences, seminars and/or meetings. Develop planning schedules. Contract Provided Government Approved Format monthly, no later than 15 working days following end of month. CDRL A006.

3.3.3.5 FLEET RDT&E SUPPORT REQUIREMENTS (RDT&E, OM&N, APN)

3.3.3.5.1 Collect inputs to the Quarterly Call for Fleet RDT&E support requirements. Submit per Government Furnished Format. Due by the 15th of January, April, July and October. CDRL A007.

3.3.3.6 CONFERENCES/COORDINATION MEETINGS (RDT&E, OM&N, APN)

3.3.3.6.1 Monitor changes in rules and regulations that could affect flight testing and frequency management promulgated by various agencies and organizations. Attend and provide inputs to coordination meetings and conferences for the purpose of identifying the requirements of agencies and organizations including, but not limited to: Federal Aviation Administration, North American Air Defense Command, Commander-in-Chief, U.S. Atlantic Fleet, Mid-Atlantic Area Frequency Coordinator, Fleet Quarterly RDT&E support, etc. Provide event summaries and trip reports per Government Furnished Format. Frequency varies pending operational requirements.

3.3.3.7 PROJECT STATUS/ASSIGNMENT (RDT&E, OM&N, APN)

3.3.3.7.1 Monitor the status of assigned projects. Develop Project Status Reports and Assignment Lists. Travel to external activities for the development and preparation of classified and unclassified presentations. Submit per Government Furnished Format no later than the 15th of each month. CDRL A008.

3.3.3.8 AIRCRAFT UTILIZATION TREND ANALYSIS (RDT&E, OM&N, APN)

3.3.3.8.1 Maintain accurate records of aircraft usage and flight hour data. Combine data and prepare a Utilization Trend Analysis depicting a floating 12 month history. Submit monthly per CDRL A009.

3.3.3.9 PROJECT FUNDING STATUS (RDT&E, OM&N, APN)

3.3.3.9.1 Gather appropriate financial data for tracking current funding, priority, expiration, and expenditures of funds for projects assigned. Attend classified and unclassified financial and budget meetings. Utilize current financial tracking systems and other computer software. Submit monthly per CDRL A010.

3.3.3.10 TRAVEL AND MATERIAL (RDT&E, OM&N, APN)

3.3.3.10.1 Track and coordinate travel and material requirements through the use of current inventory and travel databases.

3.3.3.11 SOFTWARE TECHNICAL LIBRARY (RDT&E, OM&N, APN)

3.3.3.11.1 Maintain a software technical library on software related projects. Collect and maintain records in support of software development and testing for aircraft and related systems. Write and process classified and unclassified technical reports from drafts provided from software engineering staff per applicable documents. Maintain schedule of activities involving software project teams on Government computer. Submit summary report upon request and no more than monthly per CDRL A011.

3.3.3.11.2 Coordinate storage of CVS documents on the VX-23 project Website and “S: drive 5.16.10 ATCALS Library.” This will include test plans, amendments, published reports originated by AIR 5.1.6.10 and 5.1.6.12 and engineer/pilot qualifications.

3.3.3.12 DAILY FLIGHT SCHEDULE (RDT&E, OM&N, APN)

3.3.3.12.1 Coordinate daily flight schedule requirements of cognizant project officers, engineers and other key personnel. Coordinate with Squadron team/Platform Coordinator. Provide daily inputs to the Squadron Operations Office using Government Furnished Format. Inputs may be sent electronically via network scheduling system.

3.3.3.13 WEEKLY FLIGHT SCHEDULE (RDT&E, OM&N, APN)

3.3.3.13.1 Coordinate weekly flight schedule requirements of cognizant project officers, engineers and other key personnel. Coordinate with Squadron team/Platform Coordinator. Provide weekly inputs to Operations Office using Government Furnished Format. Inputs may be sent electronically via network scheduling system. CDRL A012.

3.3.3.14DETAILED LONG RANGE PLANNER (RDT&E, OM&N, APN)

3.3.3.14.1 Coordinate detailed long range aircraft utilization/scheduling requirements. Conduct regularly scheduled recurring meetings with project test team personnel to update/maintain long range planning document. Document shall indicate projected utilization of each assigned platform specific aircraft by BUNO for a period of not less than 6 months. Items such as instrumentation periods, scheduled maintenance activities, project ground and flight test activities and scheduled detachments must be included. Updates are required at least bi-weekly, using Government Furnished Format and must be maintained on a Government computer. CDRL A013.

3.3.3.15 FISCAL YEAR FLIGHT AND GROUND HOUR ESTIMATE (RDT&E, OM&N, APN)

3.3.3.15.1Coordinate projected flight and ground test hour summaries for assigned platform aircraft. Contractor shall solicit and gather ground and flight test hour projections from individual project teams on a recurring basis, and collate the data to show projected aircraft utilization by project and BuNo for each calendar month. Separate projections shall be listed for ground hours and for flight hours. Summary data shall show total projected ground and flight hours for the entire fiscal year for each BuNo, and a total number of ground and flight hours for all assigned aircraft. The data shall be presented in spreadsheet format, formatted for printing on a single page. Updates for the current fiscal year are required at least once every calendar quarter. Initial projections for each fiscal year are required not later than 31 March of the preceding year, with quarterly updates thereafter. CDRL A014

3.3.3.16.1WEEKLY PROGRAM/FLIGHT HOUR SUMMARY (RDT&E, OM&N, APN)

3.3.3.16.1 Maintain the weekly program/flight hour summary report per Government Furnished Format. Print/post by each Wednesday at 0900. CDRL A015

3.3.3.17 FLIGHT SORTIE BREAKDOWN (RDT&E, OM&N, APN)

3.3.3.17.1 Maintain the flight sortie breakdown report. Prepare monthly summary report per Government Furnished Format NLT the 15th of the month. Submit to Operations Officer per CDRL A016

3.3.3.18 FREQUENCY MANAGEMENT REPORT (RDT&E, OM&N, APN)

3.3.3.18.1 Identify and evaluate Squadron frequency allocations and assignments, ECM notifications and other current and future frequency management requirements. Prepare documents, necessary to obtain frequency requirements and deliver to the appropriate agency/manager for review and disposition. Participate in frequency planning and coordination meetings and conferences with various commands and organizations such as the Mid-Atlantic Area Frequency Coordinator. Maintain records documenting the historical frequencies utilized by Test Squadrons. Maintain a listing of all currently assigned frequencies, their authorized area(s) of usage, emission type, date assigned, and the expiration date. Provide a quarterly report of frequencies expiring within 90 days and frequencies requiring reporting under the Five-Year Review Plan. Submit per CDRL A017.

3.4 CONTINUOUS PROCESS IMPROVEMENT

3.4.1 Participate in the implementation and development of NAVAIR sponsored initiatives for continuous improvements such as Airspeed, Theory of Constraints, Six Sigma and Reliability-Centered Maintenance.