Performance Work Statement.docx

Performance Work Statement

HQ United States Air Force Directorate for ISR Innovation and Unmanned Aircraft Systems (UAS) Task Force (A2U) UAS Task Force Technical & Management Support 3 April 09

TABLE OF CONTENTS

1. DESCRIPTION of SERVICES.

The contractor(s) must be able to interface and perform regular and frequent technical and programmatic liaison functions as required with the Air Staff, OSD, Joint Staff, National Reconnaissance Office, National Security Agency, other Services, Unified Commands, other Air Force MAJCOMs, Numbered Air Forces, appropriate wings and sub-organizations, program offices, and other organizations conducting or interfacing with UAS program or system requirements, operations, planning, RDT&E, and system sustainment. The contractor(s) must be able to support appropriate planning and development forums and technical interchange meetings and IPTs to further understand and develop background information as a basis for technical analyses in support of the above organizations.

1.3 DEFINITIONS.

“Advisory and assistance services” means those services provided under contract by nongovernmental sources to support or improve strategic deterrence and nuclear integration “Down Days” a day that AF leadership designates as a minimal manning/liberal leave day “Performance Work Statement (PWS)” means a statement of work for performance-based acquisitions that describes the required results in clear, specific, and objective terms with measurable outcomes.

Services Summary (AQL) The minimum level of acceptable performance that the contractor must meet and still be considered a satisfactory performer Note: additional definitions can be found throughout the FAR (2.101) and Sups,

1.4. ACRONYMS-LIST

2.0 SUMMARY of REQUIREMENTS.

2.1 SPECIFIC TASKS. The following activities/focus areas comprise the expected tasks and principal focus of assigned contractor personnel in support of the UAS Task Force:

2.1.1 Staff Support. In general, the contractor shall provide staff support across all performance requirements in this call order, to include:

2.1.1.1 Support government oversight of programs, processes, operations, exercises and other activities

2.1.1.2 Provide recommendations based on research, analyses, risk assessments, and review of concepts, staff packages and other reports

2.1.1.3 Provide expert support to government personnel in various forums and meetings

2.1.1.4 Support drafting and the coordination of staff packages for review and approval

2.1.1.5 Support the creation of issue/point papers, reports, publications, and other documents

2.1.1.6 Build and present briefings

2.1.1.7 Set up, prepare, facilitate, and provide post-event minutes and summaries for action officer, executive, and Congressional level hearings, meetings, seminars, conferences, boards and related activities

0. UAS Strategy, Plans and Programs: The contractor(s) shall provide technical programmatic and SME support to the functional managers, requirements officers, and PEMs for all UAS, and their ground stations, under the organizational responsibility of AF/A2U UAS Task Force. These include, but are not limited to the MQ-1, RQ-4, MQ-9, the category of “small UAS,” the next-generation MQ-X, and other UAS or reconnaissance and intelligence systems as directed by A2U. This support is required in the areas of planning, budget development and justification, requirements analyses, technical assessments, and development program reviews in support of operations, communications, research, development and acquisition, and sustainment activities. The contractor(s) will also perform a variety of capabilities-based planning, programming, and requirements duties to support CONOPS and CONEMP development and the JCIDS.

0. UAS Operational Issues Management: The UAS Task Force is the Air Staff center for UAS operational expertise. As such, the UAS Task Force requires contractor support to respond to Air Staff, Joint Staff, OSD, and other organizational requests for UAS operations information, planning, and solutions to issues affecting the full integration of UAS into Air Force, DoD, and national operations. The UAS Task Force requires contractor UAS expertise to provide guidance, review, and coordinate on CONOPS, CONEMPs, TTPs, and other similar products to ensure the optimum utility is gained from UAS operations. Specific areas of interest are the progression and maturation of UAS technologies, including advanced sensors and payloads that provide utility for military use beyond current missions, including BMC2, communications relay, and environmental sensing.

0. UAS Communications Architecture: Contractor(s) shall provide technical expertise in the development and proposal of solutions for unmanned aircraft C2. In addition, technical expertise is required to work end-to-end data dissemination with other elements of the DoD and Air Force ISR enterprise – to include DCGS. The contractor(s) will provide support in the planning/identifying future UAS requirements for electromagnetic spectrum, terrestrial and space-based communication capabilities.

2.1.5 UAS Standards and Interoperability: The UAS Task Force desires technical support in standards and interoperability to support proposals for enhancing joint war fighting capabilities, specifically as they relate to current and future UAS systems and any associated technologies. The support includes the ability to propose integration strategies for operational requirements development, acquisition management, and flight plan development. The UAS TF must be represented in DoD and other agency forums whose purpose is standardization and interoperability of various types of UAS and their enabling technologies.

2.1.6 Strategic Communications: The UAS TF must develop key messages and communications plans related to USAF UAS current operations and future development. Of primary concern are the development, management, and annual publishing of the Air Force’s UAS Flight Plan and Roadmap. The UAS TF needs to identify key outreach opportunities including UAS conferences, seminars, and other public events. The UAS TF must prepare Congressional testimony, public affairs statements and briefings.

2.2 ADDITIONAL REQUIREMENTS.

2.2.1 Required Qualifications. The contractor is responsible for providing senior personnel meeting the following qualifications and will certify that all personnel assigned to this task order have the required levels of expertise by providing, upon request, appropriate documentation (i.e. copies of DD214 or other official government documents that provide proof of service and/or qualifications).

2.2.1.1 Specific UAS Expertise: The particular depth and breadth of experience and credentials is expected to vary among the FTEs dedicated to UAS Task Force tasks.

1. Extensive MQ-1 Predator operational experience required

1. Other UAS operational experience highly desired, e.g. RQ-4, MQ-9, small UAS

1. Minimum 10 yrs in Air Force flight operations – UAS specific, highly desired

1. Required: in-depth knowledge and recent/current experience in Air Force UAS systems to include aircraft, sensors, payloads, weapons, ground control stations, C2 links, communications architecture and TPED

1. Experience in Predator operational test and evaluation, flight crew training, training device development, technical order development, Air Force UAS Instruction development required

1. Expertise in the development of UAS career field issues is required

2.2.1.2 ADP Skills: Personnel assigned to this task must possess skill in the area of software/hardware systems as specified in paragraph 2.4 of this PWS.

2.2.1.3 Functional Skills: The contractor will certify that all personnel assigned to this task order are capable of working independently and with the demonstrated knowledge, skills, and expertise in their respective areas, necessary to perform all assigned duties. If the contractor does not possess the expertise necessary outlined in the contract, then the contractor is responsible for providing the appropriate training.

1. Contractor personnel must be able to work independently, assess problems, and develop creative recommended solutions with minimum supervision

1. Knowledge of system acquisition and operational employment principles with the ability to analyze, evaluate and perform studies of operational requirements, test/evaluation, concepts, applications and technological advances

1. Ability to interface and perform technical and programmatic liaison functions with the Air Staff, Office of Secretary of Defense, the Joint Staff, the Department of Homeland Security, Air Force MAJCOMs, and other US Government agencies

2.2.1.4 Technical Skills: There will be a wide range of technical knowledge and relevant experience required within the UAS Task Force contractor team. The particular depth and breadth of experience and credentials is expected to vary among the FTEs dedicated to UAS Task Force tasks.

1. The contractor team must include personnel experienced in program management of UAS programs and PPBE

1. The contractor team must also include individuals with extensive experience in requirements analysis, requirements documentation, and long range planning

1. Experience in operations and logistics management is required

1. The team must include individual(s) with thorough knowledge of joint intelligence doctrine and an understanding warfighter RSTA needs

1. Contractor personnel must be able to prepare, coordinate, and present information on complex subjects in a concise and understandable manner at any level, including senior Service, Joint, and Department leadership

1. Extensive knowledge of Air Staff responsibilities and previous experience serving on the Air Staff is required

1. Congressional liaison experience desired

1. Strategic communications and media relations experience desired

1. Education: Bachelor’s degree required. Master’s preferred in management or related field. Equivalent work experience or equivalent military Service school may be substituted.

1. Security Clearance: Top Secret – SCI, or SCI eligible

2.2.1.5 Strategy, Plans, and Programs. The particular depth and breadth of experience and credentials is expected to vary among the FTEs assigned to support the development of UAS strategies, plans, and programs.

1. A minimum of 2 years experience with government PPBES required

1. Must have experience with POM, use of ABIDES, RAPIDS and financial spreadsheet tools

1. A minimum of 2 years experience in airborne SIGINT sensor development, control, collection or exploitation required

1. Prior experience with requirements planning, programming and development of capability roadmaps is highly desired

1. Knowledge of ISR sensors, weapons integration and advanced payloads experience on UAS programs is highly desired

1. Generation, staffing, validation and approval process for CONOPS, attrition studies, AF Planner’s Memos, Mission Needs Statements, JCIDS documents, flight plans, roadmaps, FAA UAS guidance highly desired

1. Knowledge of MAP, flight plans and roadmap development and similar processes is desirable. Predator and other UAS OCONUS deployment and command experience highly desired

0. UAS Operational Issues Management: The particular depth and breadth of experience and credentials is expected to vary among the FTEs assigned to support the UAS Task Force in meeting its mission as the Air Staff center for UAS operational expertise.

1. Extensive experience in operations and/or management of MQ-1, MQ-9, RQ-4 or similar UAS required

1. A minimum of 2 years experience developing CONOPS and/or CONEMP plans required

1. Experience on UAS programs and specific experience with the JCIDS, PPBES, and systems acquisition highly desired

1. Ability to interface and perform frequent technical and programmatic liaison functions with the Air Staff, the Office of the Secretary of Defense, the Joint Staff, the Department of Homeland Security, Air Combat Command, Special Operations Command, and other US government and allied organizations

1. Knowledge of operational architectures and integrating ISR capabilities (aircraft, communications suites and ground stations), BMC2, weapons employment, airborne communications, and electronic warfare required

1. Military or civilian aeronautical rating highly desired

0. Communications Architectures: The particular depth and breadth of experience and credentials is expected to vary among the FTEs assigned to support UAS Task Force efforts in UAS communications architectures.

1. Minimum of 15 years communications experience required

1. Minimum 3 years experience working UAS communications architectures required

1. USAF communications experience highly desired

1. Must understand spectrum and frequency management, line-of-sight and beyond line-of-sight architectures

1. Education: Electrical engineering degree or equivalent technical degree highly desired. Master’s degree in communications and/or equivalent military Service school highly desired

0. UAS Standards and Interoperability: The particular depth and breadth of experience and credentials is expected to vary among the FTEs assigned to the UAS Task Force.

1. Minimum 10 years military, DoD, or DoD contractor experience required

1. Minimum 2 years specific work with DoD technical studies and analysis

1. Technical background in UAS standards and interoperability required

1. Experience with UAS standards and interoperability matters highly desired

1. Experience with JCIDS

1. Education: Technical academic degree and/or equivalent experience with DoD-related technical analytical studies required

0. Strategic Communications: The particular depth and breadth of experience and credentials is expected to vary among the FTEs assigned to the UAS Task Force.

1. Minimum 2 years experience in strategic communications required

1. USAF strategic communications & media relations experience highly desired

1. USAF Congressional liaison experience highly desired

1. Senior USAF staff experience and UAS operational experience highly desired

1. Bachelor’s degree required. Master’s degree in communications, US military doctrine/strategy or equivalent military Service school highly desired

2.2.2 Work Priority. Due to the nature of the UAS Task Force’s mission, the number and types of tasks contractor personnel will support in will vary daily. Likewise, the deadlines for product submission will also vary from task to task. Work priority will be determined by the UAS Task Force Director or his designee and will make all efforts to ensure the assigned contractor personnel are provided reasonable time to accomplish the assigned tasks. Generally, all SECDEF, SECAF and/or CSAF tasks will have priority over all other events for contractor’s schedule.

2.2.3 Seminars/Conferences. Contractor personnel assigned to this task may be required to attend and participate in various UAS seminars and conference. Participation in such events will be at the government’s discretion, contingent on the contractor personnel’s role, event objectives, scheduling and funding.

2.2.4 Place of Performance. Work is to be performed at the following locations: Pentagon, Bolling AFB, and or AF/A2U Crystal City offices, contractor facilities, and other locations in the National Capital Region. Occasionally, other off-site locations may be required to support UAS Task Force meetings, seminars and conferences hosted at other off-site locations. In the event of a natural or man-made disaster that may necessitate the re-location of the Task Force, appropriate arrangements will be made with the contractor prior to relocation.

2.2.8 Period of Performance. The period of performance is one year from date of award, with two (2), one (1) year option periods.

2.3 SERVICES SUMMARY.

2.3.1 Performance and Workload Requirements.

2.3.1.1 Performance Requirements.

Paragraph(s) Performance Threshold

SS1: Support government oversight of programs, processes, operations, exercises and other activities

1.0, 2.1.1, 2.1.2, 2.1.3, 2.14, 2.1.5, 2.1.6, 2.2.1.3, 2.2.1.4 2.2.1.5, 2.2.1.6, 2.2.1.7, 2.2.1.8, 2.2.1.9, 2.2.2, 2.2.3 Scheduled Reports and Tasks meet deadlines - 100% compliance.

Compliant with PWS requirements by required due dates- no more than two requested extensions per month.

Document Quality:

90% accuracy and completeness of drafts.

100% resolution of all issues, accuracy and completeness of final draft.

2.2.1.5, 2.2.1.6, 2.2.1.7, 2.2.1.8, 2.2.1.9, 2.2.2 Scheduled Reports and Tasks meet deadlines - 100% compliance.

Compliant with PWS requirements by required due dates- no more than two requested extensions per month.

Document Quality:

Multiple Revisions may be required—100% turn-in of requested documents

90% accuracy and completeness of drafts.

100% resolution of all issues, accuracy and completeness of final draft.

Documents must be in compliance with local policy and Tongue and Quill Guidelines.

Documents need to be suitable for senior executive level review and action.

2.2.1.5, 2.2.1.6, 2.2.1.7, 2.2.1.8, 2.2.1.9, 2.2.2 Compliant with PWS requirements by required due dates- no more than two requested extensions per month.

Document Quality:

Multiple Revisions may be required—100% turn-in of requested documents

90% accuracy and completeness of drafts.

100% resolution of all issues, accuracy and completeness of final draft.

Documents must be in compliance with local policy and Tongue and Quill Guidelines.

Documents and presentations need to be suitable for senior executive level review and action.

2.2.1.5, 2.2.1.6, 2.2.1.7, 2.2.1.8, 2.2.1.9, 2.2.3 Zero (0) technical knowledge discrepancies with reports, analysis, and recommendations.

2.2.1.5, 2.2.1.6, 2.2.1.7, 2.2.1.8, 2.2.1.9, 2.2.2, 2.2.3 No more than three (3) substantiated errors in event planning, execution, post-event minutes.

2.4 GOVERNMENT FURNISHED EQUIPMENT/DATA. The contractor must

identify in the task proposal the type, amount, and time frames for government resources, excluding those listed in this paragraph. The government will furnish or make available to the assigned contractor personnel any documentation deemed necessary by AF/A2U to accomplish duties identified in this task order. AF/A2U will provide office space, furniture, supplies, and automated office equipment. Access will be granted to classified and unclassified military LAN services, LAN support, telephones and reproduction facilities at the places of performance. The government will provide access to relevant government organizations, information, and documentation, manuals, texts, briefs, and associated materials as required and available. Access will be granted to classified networks as directed by the designated security authority.

2.5 TRAVEL. The contractor may be required to perform periodic travel within the Continental United States. When the government requires contractor travel in performance of this effort, the contractor will be reimbursed for actual travel costs incurred. When necessary to use air travel, the contractor shall use the tourist class, economy class, or similar lodging accommodations to the extent they are available and commensurate with the mission requirements. No profit will be paid in support of cost reimbursable travel. G&A shall be negotiated at time of proposal submission only. Contractor shall follow JFTR as do government civilians and military personnel in calculating all travel expenditures. Travel shall be reimbursed IAW the JFTR. A separate travel CLIN shall be established and funded at contract award. Travel shall be determined by the government by a not to exceed amount at time of award. The contractor shall notify the government when 80% of the NTE amount has been reached. The Contractor will be required to travel to attend meetings in support of tasks listed above.

2.6 SECURITY REQUIREMENTS. Personnel assigned to this project will require access to information up to and including Top Secret/SCI. A2U shall implement and administer a security program to ensure that classified information and documentation are protected in accordance with the latest appropriate Security Classification Guide for each project identified in the Department of Defense Contract Security Classification Specification (DD Form 254). Access will be required to cleared facilities, including, but not limited to, the Pentagon. Identification badges will be furnished by installation security for the contractor task employee upon presentation of evidence of assignment to this task and appropriate clearance paperwork.

2.6.1 Personnel Security Clearance Requirements. Contractor will ensure personnel assigned have a Top Secret/SCI clearance at time of contract award. As a minimum, key contract personnel shall have active clearance prior to start of work in accordance with the DD Form 254.

2.7 CONFLICTS OF INTERESTS. The contractor shall adhere to the requirements of FAR 9.5 and recuse themselves from any and all potential situations that may suggest a conflict of interest. Prior to the start of the contract the contractor shall provide a statement that they have read FAR 9.5, which outlines Organizational and Consultant Conflicts of Interest and know of no potential conflicts, to include past employment (military or civilian), that would preclude them with fulfilling the requirements of this PWS. Additionally, during the life of the contract the contractor must identify, in writing, any possible conflicts of interest and officially recuse themselves from any such activity or action.

2.8 DELIVERABLES. In addition to the reports listed below in paragraph 2.8.1, a monthly progress report will be provided to the A2U Technical and Financial POCs listed in this contract. All deliverables produced are property of the government.

2.8.1 Deliverables

2.8.2 Criteria for Acceptance. All deliverables shall be submitted within the timeframes given and in the appropriate/standard formats as required by the originating task authority.

3.0 QUALITY ASSURANCE PLAN: Quality Assurance Personnel shall conduct, document, track, and analyze contractor performance via quarterly scheduled assessments. The assessment results shall be maintained as Past Performance Information and utilized to prepare and support annual Performance Assessment Report System (CPARS) reporting. Satisfactory performance assessments may be rewarded with letters of recognition, decreased surveillance, reduced assessments, positive CPARS, and exercise option years. Unsatisfactory performance assessments may result in increased surveillance of work performed with increased QA team meetings, negative CPARS and/or option years not being exercised. Remedies for non-compliance include:

4.0 NON-PERSONAL SERVICES. The Government will 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. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the contractor feels that any actions constitute, or are perceived to constitute personal services, it shall be the contractor’s responsibility to notify the CO immediately. These services shall not be used to perform work of a policy/decision making or management nature, i.e., inherently Governmental functions. All decisions relative to programs supported by the contractor shall be the sole responsibility of the Government.

5.0 CONTRACTOR IDENTIFICATION. All contractor/subcontractor personnel shall wear company picture identification badges so as to distinguish themselves from Government employees. When conversing with Government personnel during business meetings, over the telephone or via electronic mail, contractor/subcontractor personnel shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors/subcontractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, contractor/subcontractors occupying collocated space with their Government program customer should identify their work space area with their name and company affiliation, or as a minimum “Contractor” after name.

6.0 HOURS OF OPERATION. It should be noted that weekly hours may exceed a forty (40) hour work week and some weekends may be required. However a typical work day will be 0730 to 1630 Monday through Friday. The Government reserves the right to change hours of operation or restrict contractor access. Contractor(s) shall not work overtime without prior written approval the A2U Task Force COTR or QAPC.

6.1 SCHEDULED HOLIDAYS. New Year’s Day; Dr. Martin Luther King, Jr. Birthday; President’s Day; Memorial Day; Independence Day; Labor Day; Columbus Day; Veteran’s Day; Thanksgiving Day; Christmas Day.

6.1.1 Government agencies will not be available during scheduled holidays, inclement weather, weekends, after duty hours, or AF down days. All chargeable work will be directly attributable to the task being performed by the individual.

6.2 BILL-ABLE HOURS. Government surveillance of contractor performance is required to give reasonable assurance that efficient methods and effective cost controls are being used. In order for man-hours to be billed on this requirement deliverable services must have been performed in direct support of a requirement in the PWS. In the course of business, situations may arise where Government facilities may not be available for performance of these requirements (i.e., base closure due to weather, down day etc.). During these situations contractor personnel will not be paid or will report to there corporate offices.