Amendment_0001_HQ0034-12-A-3139_Remotely_Piloted_Aircraft.pdf

PDF 477 KB Posted

Attached to
Remotely Piloted Aircraft Support
Solicitation number
HQ0034-12-R-3129
Issued by

About this file

Amendment 0001-The purpose of this amendment is to incorporate the questions and answers update minimum requirements and to extend the due date from November 7 2012 at 2 00pm EST to November 14 2012 at 10 00 am. EST.

View the file

Other files

File Type Posted
RPA_Sole_Source.pdf PDF
Non_Disclosure_Agreement_HQ0034-12-R-3129.doc DOC document
Attachment_1 2_for_DD254.pdf PDF
Remotely_Piloted_Aircraft_RFP_HQ0034-13-R-3129_-_(Final_PLR).pdf PDF
DD254-RPA.pdf PDF
RPA_Support_Past_Performance_Questionaire.docx DOCX document

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Remotely Piloted Aircraft (RPA) Capabilities for the Office of the Under Secretary of Defense for Intelligence

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF) Combined Synopsis/Solicitation

HQ0034-12-R-3129, Amendment 0001

Amendment 0001

The purpose of this amendment is to:

1. Incorporate “Questions & Answers” received in response to Solicitation No. HQ0034-12-

R-3129.

2. Amend Section C, 4.2.8, MQ-9 SME minimum requirements. See replaced language below

(page 12).

3. Extend the closing date and time from November 7, 2012 to November 14, 2012 at 10:00

AM EST.

Q1: Is there an incumbent contractor? If so, what is the contract number?

A1: Yes, the incumbent contractor is Scitor Corporation. The contract number is HQ0034-07-A- 1040-0014.

Q2: In August 2001, the U.S. Department of Labor (DOL) issued its final rule implementing President Obama's Executive Order 13495 entitled "Nondisplacement of Qualified Workers Under Service Contracts." Can you confirm if the DOL ruling applies to this contract?

A2: No, this DOL ruling does not apply to this requirement.

Q3: The RFP states: "During the first ninety (90) calendar days of performance, the Contractor shall make no substitutions of key personnel unless illness, death, or termination of employment necessitates the substitution." Does the government require the personnel proposed in our proposal to remain on the job for the first 90 days regardless of the incumbent personnel decision regarding staying on the job?

A3: Yes, the government expects the personnel proposed to remain on the job during the first ninety (90) calendar days of performance, unless illness, death, or termination of employment necessitates the substitution.

Q4: Does the government require proposed personnel to be the personnel on site day 1 if other more qualified candidates accept job offers prior to contract start?

A4: The government requires that the personnel proposed or personnel with equivalent qualifications as those proposed to start on day 1 of the period of performance.

Q5: The first MQ-9 test vehicles were delivered to the USAF in 2012 greatly limiting the number of personnel who have "ten years experience supporting the MQ-9 ISR platforms and systems."

Can you confirm that the second portion of the sentence: "or their ancillary and integrated ISR sensors and associated command and control systems" gives personnel with MQ-1 experience sufficient background since the sensors and associated command and control systems are identical or very similar?

A5: To clarify, the MQ-9 has been in USAF operation since 2007. The ten years experience can include a combination of both MQ-1 and MQ-9 experience. Personnel with USAF MQ-1 experience have sufficient experience due to the similarity of sensors and command and control systems between the two platforms. Other services operate similar platforms but the differentiation between C2, ground support systems, and methods of utilization and employment are critical.

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

RFP: HQ0034-12-R-3129

Remotely Piloted Aircraft

Issue Date: 10/24/2012 Due Date: November 14, 2012 at 10:00 PM EST November 7, 2012 at 2:00 EST

Julie Fox, Contract Specialist Christopher Harris, Contracting Officer

This is a combined synopsis/solicitation issued in accordance with the streamlined procedures in FAR 12.6. The resultant contract will support remotely piloted aircraft in OUSDI, ISR.

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

(i) This is a combined synopsis/solicitation for commercial items prepared in accordance with FAR Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued.

(ii) The solicitation number is HQ0034-12-R-3129. This solicitation is issued as a Request for Proposal (RFP).

(iii) The solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular 2005-61.

(iv) This solicitation is a 100% set-aside for Service Disabled Veteran Owned Small

Business concerns. The NAICS code for this procurement is 541330, Engineering Services. The small business size standard for this NAICS code is $14,000,000.

(v) Contract line item numbers (CLINs), quantities, and units of measure are included in the solicitation.

(vi) The Government requires Subject Matter Experts (SMEs) in the following RPA

Capabilities: MQ-1 Predator, MQ-9 Reaper, RQ-4 Global Hawk, and RPA Command and Control. The RPA Capabilities Team will assist the ISR Task Force and the RPA Capabilities Division (AF/A2CU) in the functional management, capability development, and planning of the RPA force. This includes technical support to the broader management of ISR platforms, sensors, their associated Processing, Exploitation, Dissemination (PED) and communication architectures, as well as the development and fielding of RPA ISR capability. The RPA Capabilities Team will be responsible for supporting the ISR TF and AF/A2C in their missions to provide ISR and RPA capabilities supporting COCOM and theater requirements.

(vii) The period of performance is expected begin NLT December 1, 2012. The contract is for a 12-month base period and three 12-month option periods. The place of delivery is contained herein. Services are inspected and accepted at the Government facility. If there is any equipment, it is always FOB destination.

(viii) The provision at Federal Acquisition Regulation (FAR) 52.212-1, Instructions to

Offerors – Commercial Items, applies to this acquisition.

(ix) The provision at FAR 52.212-2, Evaluation -- Commercial Items is included.

(x) Offerors shall include a completed copy of the provision at FAR 52.212-3 Alt I, FAR 52.209-7, DFARS252.209-7999, and DFARS 252.212-7000, with its offer.

http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/52_000.htm#P1362_186138� http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/52_000.htm#P1423_197969� http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/52_000.htm#P1438_199992�

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

(xi) The clause at FAR 52.212-4, Contract Terms and Conditions -- Commercial Items, applies to this acquisition.

(xii) The clause at FAR 52.212-5, Contract Terms and Conditions Required To Implement

Statutes Or Executive Orders -- Commercial Items, applies to this acquisition.

(xiii) Additional Department of Defense terms and conditions terms and condition for the acquisition of commercial items apply.

(xiv) This is not a Defense Priorities and Allocations System (DPAS) rated order.

(xv) Offers are due no later than November 14, 2012 at 2:00 PM EST November 7, 2012 at 2:00 PM EST. Offers shall be emailed to:

Julie Fox Contract Specialist Tel: 703-545-1257 Email: julie.fox@whs.mil

Chris Harris Contracting Officer Tel: 703-545-3573 Email: chris.harris@whs.mil

(xvi) Offerors shall submit questions/clarifications to Julie Fox at julie.fox@whs.mil and copy (cc) Chris Harris at chris.harris@whs.mil. Before preparing a proposal, or requesting a clarification on this solicitation, offerors should first read the solicitation in its entirety. Questions that are vague, illegible, or irrelevant to the solicitation, or submitted after the cutoff date established may not receive a response. Questions are due no later than October 29, 2012 at 2:00 PM EST.

(xvii) All amendments to this solicitation will be posted on the FedBizOpps at www.fbo.gov. The amendments are linked to the solicitation at this site.

Amendments will NOT be posted in any other location other than at www.fbo.gov.

(xviii) This solicitation is being issued Subject to the Availability of Funds (STAF).

http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/52_000.htm#P1718_239297� http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/52_000.htm#P1910_277742� mailto:julie.fox@whs.mil� mailto:chris.harris@whs.mil� mailto:julie.fox@whs.mil� mailto:chris.harris@whs.mil� http://www.fbo.gov/� http://www.fbo.gov/�

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

Section B – Schedule of Supplies & Services

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 12 Months Base Period – RPA Capabilities Support

FFP

The contractor shall provide RPA Capabilities support services as delineated in the attached Performance Work Statement.

NET AMT

0002 1 Lot Base Period – Travel

COST

All travel shall be approved in advance by the COR and billed in accordance with FAR 31.205-46 “Travel Costs”.

ESTIMATED COST $40,000.00

1001 12 Months Option Period One – RPA Capabilities Support

FFP

1002 1 Lot Option Period One – Travel

COST

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

2001 12 Months Option Period Two – RPA Capabilities Support

FFP

2002 1 Lot Option Period Two – Travel

COST

3001 12 Months Option Period Three – RPA Capabilities Support

FFP

3002 1 Lot Option Period Three – Travel

COST

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

Section C – Performance Work Statement

1.0 BACKGROUND. The ISR TF oversees the rapid procurement and integration of ISR capability to US Central Command (CENTCOM) and US Special Operations Command (SOCOM). This includes the deployment, employment, and evaluation of ISR TF capabilities in the CENTCOM theater of operations. Support is required to provide the proper integration of these ISR systems in order to provide immediate impact to combat operations in Afghanistan.

The RPA Capabilities Division (AF/A2CU) supports the ISR TF in its mission as the HAF lead for ISR and unmanned aircraft capabilities employed by the Air Force. The RPA Capabilities Division serves as the Headquarters Department of the Air Force (HAF’s) primary RPA coordination point with DoD, Congressional, COCOM, and MAJCOM staffs on RPA ISR force issues. As the HAF functional manager of RPA ISR capabilities, AF/A2CU ensures consistency of effort by working inside HAF normal processes with DCSs, other HAF agencies, Office of the Secretary of Defense (OSD), ISR TF, Joint Staff, and AF MAJCOMs to provide AF ISR forces and assets to combatant commanders. AF/A2CU works with the OSD, the Office of Director of National Intelligence (ODNI), and Intelligence Community authorities to translate higher level guidance into Service specific policy and guidance on the utilization of RPA. AF/A2CU supports the HAF and the ISR TF in monitoring the performance and effectiveness of emerging and fielded unmanned assets and furnishes subject matter expertise to forums on RPA and Small Unmanned Aircraft System (SUAS) applications to enhance/expand ground and airborne ISR system/sensor capabilities. AF/A2CU provides critical support to both Joint and OSD staffs in the formulation of solutions to a wide range of RPA and ISR issues affecting RPA global force employment and contingency response. This support includes critical RPA technical and capability assessments and development and coordination of OUSD(I) and Joint Staff RPA issues and emerging requirements.

2.0 OBJECTIVE/SCOPE. The RPA Capabilities A&AS Team will assist the ISR TF and AF/A2CU in the functional management and capability development and planning of the Air Force’s RPA force. This includes technical support to the broader management of ISR platforms, sensors, their associated Processing, Exploitation, Dissemination (PED) and communication architectures, as well as the development and fielding of RPA ISR capability.

The RPA Capabilities A&AS Team supports the ISR TF and AF/A2C in their missions to provide ISR and RPA capabilities supporting COCOM, theater and MAJCOM requirements.

3.0 TASKS. The following comprise the expected tasks, subtasks, and principal focus of the RPA Capabilities A&AS Team subject matter experts (SMEs) and support personnel. Daily work priority will generally be determined by AF/A2CU. Tasks associated with the ISR TF’s near-term capabilities development and fielding will generally have priority over other AF/A2CU near-term ISR capability tasking, with the exception of SECDEF, SECAF, and CSAF time critical tasks. The RPA Capabilities A&AS Team’s expertise will be applied to ISR TF critical and time-sensitive tasks including the rapid identification and fielding of RPA technologies and capabilities as well as advanced sensors and payloads that provide near-term

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF) utility for military use beyond current missions. Specifically, the RPA Capabilities A&AS Team will directly support AF/A2CU and the ISR TF by providing expertise and support for the following high demand ISR platforms and systems: MQ-1 Predator, MQ-9 Reaper, RQ-4 Global Hawk, and Small Unmanned Aircraft Systems (SUAS); and their ancillary and integrated ISR sensors and associated command and control systems.

4.1. The contractor shall function as MQ-1 Predator SME (Government Estimate: 1 FTE):

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

4.1.2. Provide recommendations based on research, analyses, risk assessments, and review of concepts, staff packages and other reports assessments based on current agency personnel and equipment.

4.1.3. Provide expert support to government personnel in various forums and meetings.

4.1.4. Support drafting and the coordination through senior leaders of staff packages for review and approval.

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

4.1.6. Build and present briefings. Rapidly research past decisions and guidance, technical details, and stakeholder positions. Prepare cogent slides that are appropriate to present to senior leaders.

4.1.7. Setup, prepare, facilitate, and provide post-event minutes and summaries for action officer, executive, and Congressional level hearings, meetings, seminars, conferences, boards and related activities.

4.1.8. Support HQ AF/A2C:

4.1.8.1. Support HQ USAF/A2C in its mission as the HAF lead for ISR RPA and SUAS capabilities.

4.1.8.2. Serve as senior subject matter expert for AF/A2CU MQ-1 Functional Manager.

4.1.8.3. Work with the offices of OSD, ODNI, ISR TF, and other intelligence community authorities to translate higher level guidance into recommendations for Service-specific policy and guidance on the utilization of the MQ-1 Predator.

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

4.1.8.4. Monitor the performance and effectiveness of the Air Force’s MQ-1 fleet and serve as SME for the AF/A2CU focal point to forums regarding MQ-1 applications to enhance and expand ground and airborne ISR systems and sensor capabilities.

4.1.8.5. Serve as senior SME to the primary AF/A2CU liaison between

SAF/AQIJ, AF/A8PI, ACC/A3C, ACC/A8Q/Y, AFSOC/A5K, JS/J8, OUSD

(AT&L), OUSD(I), and other Services providing detailed actionable strategic recommendations and deliverables on matters concerning MQ-1 capabilities planning, technology assessment, programming and prioritization.

4.1.8.6. Serve as senior advisor to primary AF/A2CU interface with Congressional staffs to provide information concerning Air Force remotely piloted ISR forces and assets.

4.1.8.7. Identify and develop recommended standards, procedures, policy, and enabling technology necessary to maximize MQ-1 capabilities in contested and non-contested airspace supporting emerging COCOM and service requirements.

4.1.8.8. Provide MQ-1 planning and programming expertise in the areas of Medium Altitude RPA program management, test and evaluation, CONOP and doctrine development, participation and review requirement development and technology transition.

4.1.8.9. Serve as senior advisor to A2CU liaison with ACC, AFSOC, ANG, AFRC and other stakeholders, assessing and making recommendations for MQ-1 technology planning and road-mapping.

4.1.8.10. Develop presentations and briefings through senior leaders to support programmatic actions and technology outreach for the Air Force’s MQ-1 fleet.

4.1.8.11. Provide expert strategic assessments of current and planned MQ-1 programs and Joint Concept Technology Demonstrations (JCTDs) for possible transition to service program of records.

4.1.8.12. Evaluate MQ-1 program issues and develops recommendations to resolve substantive DOD, Joint Staff, and COCOM issues of providing increased ISR effectiveness and efficiency.

The minimum requirements are for the MQ-1 SME are as follows (all minimum requirements must be met):

• Bachelor’s Degree from accredited college or university

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

• ten years experience supporting the MQ-1 ISR platforms and systems or their ancillary and integrated ISR sensors and associated command and control systems;

• five (5) years of Joint Capability Integrated Development (JCID) process experience to support government oversight of programs, processes, operations, exercises and other activities;

• five (5) years of experience planning and programming experience with Medium Altitude RPA program management, test and evaluation, CONOP and doctrine development, participation and review requirement development and technology transition;

• five (5) years of experience interfacing with Congressional staffs to provide information concerning Air Force remotely piloted ISR forces and assets;

• five (5) years of Air/Joint/OSD Staff Experience that demonstrates the ability to analyze complex RPA issues and developed recommendations for USAF and OSD senior leadership;

• and five (5) years of Technical experience with planning/identification of future MQ-1, requirements for electromagnetic spectrum capabilities and requirements.

In addition, to the aforementioned minimum requirements the successful candidate must demonstrate the following:

• Demonstrated technical expertise and systems knowledge needed to address DoD critical and time-sensitive issues regarding rapid identification and fielding of RPA technologies and capabilities (advanced sensors, payloads, BMC2, communications) that provide near term utility for military use beyond current missions.

• Specialized RPA knowledge and expertise that can provide viable, informed recommendations to Air Staff, Joint Staff, OSD, OSD(I) etc regarding RPA contingency technical and capability assessments, CONOPS and CONEMP development.

Recommendations will be used to scope emerging DoD operational utilization.

4.2 The contractor shall function as MQ-9 Reaper SME:

4.2.1. Support government oversight of programs, processes, operations, exercises and

4.2.2. Provide recommendations based on research, analyses, risk assessments, and review of concepts, staff packages and other reports. Recommend future strategic assessments based on current agency personnel and equipment.

4.2.3. Provide expert support to government personnel in various forums and meetings.

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

4.2.4. Support drafting and the coordination through senior leaders of staff packages for review and approval.

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

4.2.6. Build and present briefings. Be able to rapidly research past decisions and guidance, technical details, and stakeholder positions then prepare cogent slides that are appropriate to present to senior leaders.

4.2.7. Setup, prepare, facilitate, and provide post-event minutes and summaries for action officer, executive, and Congressional level hearings, meetings, seminars, conferences,

4.2.8. Support HQ AF/A2C:

4.2.8.1. Support HQ AF/A2C in its mission as the HAF lead for ISR, RPA and SUAS capabilities.

4.2.8.2. Serve as senior subject matter expert for AF/A2CU MQ-9 FAM.

4.2.8.2. Work with OSD, ODNI, and other intelligence community authorities to translate higher level guidance into recommendations for Service-specific policy and guidance on the utilization of the MQ-9.

4.2.8.3. Monitor the performance and effectiveness of the Air Force’s MQ-9 fleet and serve as the senior SME for AF/A2CU focal point to forums regarding MQ-9 applications to enhance and expand ground and airborne ISR systems and sensor capabilities.

4.2.8.4. Serve as the senior SME to the primary AF/A2CU liaison between

SAF/AQIJ, AF/A8PI, ACC/A3C, ACC/A8Q/Y, AFSOC/A5K, JS/J8,

OUSD(AT&L), OUSD(I), and other Services providing detailed actionable strategic recommendations and deliverables on matters concerning MQ-9 capabilities planning, technology assessment, programming, and prioritization.

4.2.8.5. Serve as senior advisor to primary AF/A2CU interface with Congressional staffs to provide information concerning Air Force medium altitude remotely piloted ISR forces and assets.

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

4.2.8.6. Identify and develop recommended standards, procedures, policy, and enabling technology necessary to maximize MQ-9 capabilities in contested and non-contested airspace supporting emerging COCOM and service requirements.

4.2.8.7. Provide MQ-9 planning and programming expertise in the areas of Medium Altitude RPA program management, test and evaluation, CONOP and doctrine development, participation and review requirement development and technology transition.

4.2.8.8. Senior advisor to the AF/A2CU liaison with ACC, AFSOC, ANG, AFRC, and other stakeholders, assessing and making recommendations for MQ-9 technology planning and road-mapping.

4.2.8.9. Develop presentations and briefings through senior leaders to support programmatic actions and technology outreach for the Air Force’s MQ-9 fleet.

4.2.8.10. Provides expert strategic assessments of current and planned MQ-9 programs and Joint Concept Technology Demonstrations (JCTDs) for possible transition to service program of records.

4.2.8.11. Evaluate MQ-9 program issues and develops recommendations to resolve substantive DOD, Joint Staff, and COCOM issues of providing increased ISR effectiveness and efficiency.

The minimum requirements are for the MQ-9 SME are as follows (all minimum requirements must be met):

• Bachelor’s Degree from accredited college or university;

• ten years experience supporting a combination of both MQ-1 and MQ-9 ISR platforms and systems or their ancillary and integrated ISR sensors and associated command and control systems.

• five (5) years of Joint Capability Integrated Development (JCID) process experience to support government oversight of programs, processes, operations, exercises and other activities;

• five (5) years of experience planning and programming experience with Medium Altitude RPA program management, test and evaluation, CONOP and doctrine development, participation and review requirement development and technology transition;

• five (5) years of experience interfacing with Congressional staffs to provide information concerning Air Force remotely piloted ISR forces and assets;

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

• five (5) years of Air/Joint Staff Experience that demonstrates the ability to analyze complex RPA issues and developed recommendations for USAF and OSD senior leadership;

• and five (5) years of Technical experience with planning/identification of future MQ-9, requirements for electromagnetic spectrum capabilities and requirements.

In addition, to the aforementioned minimum requirements the successful candidate must demonstrate the following:

• Demonstrated technical expertise and systems knowledge needed to address DoD critical and time-sensitive issues regarding rapid identification and fielding of RPA technologies

4.3. The contractor shall function as RQ-4 Global Hawk SME:

4.3.1. Support government oversight of programs, processes, operations, exercises, and

4.3.2. Provide recommendations based on research, analyses, risk assessments, and review of concepts, staff packages and other reports. Recommend future strategic assessments based on current agency personnel and equipment.

4.3.3. Provide expert support to government personnel in various forums and meetings.

4.3.4. Support drafting and the coordination through senior leaders of staff packages for review and approval.

4.3.5. Support the creation of issue and point papers, reports, publications, and other documents.

4.3.6. Build and present briefings. Be able to rapidly research past decisions and guidance, technical details, and stakeholder positions then prepare cogent slides that are appropriate to present to senior leaders.

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

4.3.7. Set up, prepare, facilitate, and provide post-event minutes and summaries for action

4.3.8 Support HQ AF/A2C:

4.3.8.1. Support HQ AF/A2C in its mission as the HAF for ISR, RPA and SUAS capabilities.

4.3.8.2. Serve as senior SME for AF/A2CU RQ-4 FAM.

4.3.8.3. Work with OSD, ODNI, and other intelligence community authorities to translate higher level guidance into recommendations for Service-specific policy and guidance on the utilization of the RQ-4.

4.3.8.4. Monitor the performance and effectiveness of the Air Force’s RQ-4 fleet and serve as the senior SME for AF/A2CU focal point to forums regarding RQ-4 applications to enhance and expand ground and airborne ISR systems and sensor capabilities.

4.3.8.5. Serve as the senior SME for the primary AF/A2CU liaison between

SAF/AQIJ, AF/A8PI, ACC/A3C, ACC/A8Q/Y, JS/J8, OSD(AT&L), OUSD(I),

and other Services providing detailed actionable strategic recommendations and deliverables on matters concerning RQ-4 capabilities planning, technology assessment, programming and prioritization.

4.3.8.6. Serve as senior advisor to primary AF/A2CU interface with Congressional staffs to provide information concerning Air Force high altitude remotely piloted ISR forces and assets.

4.3.8.7. Identify and develop recommended standards, procedures, policy, and enabling technology necessary to maximize RQ-4 capabilities in contested and non-contested airspace supporting emerging COCOM and service requirements.

4.3.8.8. Provides RQ-4 planning and programming expertise in the areas of high-altitude RPA program management, test and evaluation, CONOP and doctrine development, participation and review requirement development and technology transition.

4.3.8.9. Senior SME for AF/A2CU liaison with Air Force MAJCOMS, COCOMS and other stakeholders, assessing and making recommendations for RQ-4 technology planning and road-mapping.

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

4.3.8.10. Develop presentations and briefings through senior leaders to support programmatic actions and technology outreach for the Air Force’s RQ-4 fleet.

4.3.8.11. Provide expert strategic assessments of current and planned RQ-4 programs and JCTDs for possible transition to service program of records.

4.3.8.12. Evaluate RQ-4 program issues and develops recommendations to resolve substantive DOD, Joint Staff, and COCOM issues of providing increased ISR effectiveness and efficiency.

4.3.8.13. Assist government lead in managing the acceleration of the Global Hawk Block 40 program whose purpose is to coordinate among USAF, COCOM and OSD agencies to ensure a smooth entry of this capability into the respective missions.

4.3.8.14. Key senior SME for of all RQ-4 Requirements High Performance Teams (HPT), drafting JCIDS documents to support acquisition milestones.

The minimum requirements are for the RQ-4 Global Hawk SME are as follows (all minimum requirements must be met):

• Bachelor’s Degree from accredited college or university;

• ten years experience supporting the RQ-4 ISR platforms and systems or their ancillary and integrated ISR sensors and associated command and control systems;

• five (5) years of Joint Capability Integrated Development (JCID) process experience to support government oversight of programs, processes, operations, exercises and other activities;

• five (5) years of experience planning and programming experience with High Altitude RPA program management, test and evaluation, CONOP and doctrine development, participation and review requirement development and technology transition;

• five (5) years of experience interfacing with Congressional staffs to provide information concerning Air Force remotely piloted ISR forces and assets;

• five (5) years of Air/Joint/OSD Staff Experience that demonstrates the ability to analyze complex RPA issues and developed recommendations for USAF and OSD senior leadership;

• And five (5) years of Technical experience with planning/identification of future RQ-4, requirements for electromagnetic spectrum capabilities and requirements.

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

In addition, to the aforementioned minimum requirements the successful candidate must demonstrate the following:

• Demonstrated technical expertise and systems knowledge needed to address DoD critical and time-sensitive issues regarding rapid identification and fielding of RPA technologies

4.4. The contractor shall function as Remotely Piloted Aircraft Command and Control SME:

4.4.1. Support government oversight of RPA and SUAS programs, processes, operations, exercises and other activities related to RPA communications architecture

4.4.2. Provide recommendations based on research, analyses, risk assessments, and review of concepts, staff packages and other reports. Recommend future strategic assessments based on current agency personnel and equipment.

4.4.3. Provide expert support to government personnel in various forums and meetings.

4.4.4. Support drafting and the coordination through senior leaders of staff packages for review and approval.

4.4.5. Support the creation of issue and point papers, reports, publications, and other documents.

4.4.6. Build and present briefings. Be able to rapidly research past decisions and guidance, technical details, and stakeholder positions then prepare cogent slides that are appropriate to present to senior leaders.

4.4.7. Set up, prepare, facilitate, and provide post-event minutes and summaries for action

4.4.8. Support HQ AF/A2C:

4.4.8.1. Support HQ USAF/A2C in its mission as the HAF for ISR and RPA capabilities.

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

4.4.8.2. Serves as senior SME for AF/A2CU MQ-1, MQ-9. RQ-4 and SUAS FAM senior Line of Sight (LOS) and Beyond LOS C2.

4.4.8.3. Senior advisor for planning/identification of future MQ-1, MQ-9, RQ-4, and SUAS requirements for electromagnetic spectrum capabilities and requirements.

4.4.8.4. Senior advisor to AF representative to the OSD Frequency and Bandwidth Integrated Product Team (IPT). Provide supporting information regarding AF RPA spectrum plans.

4.4.8.5. Coordinates with MAJCOMs, Program Offices, COCOM Spectrum Managers, and AF Spectrum Management Office on migration plans for current and future RPAs.

4.4.8.6. Serve as AF SME in support of OSD Interoperability IPT, and satellite communications SME, leading development and modifications to MQ-1 and MQ- 9 RPA satellite transmission standards across Joint community. Provide subject matter expertise for development of Unmanned System Interoperability Profiles (USIPs) covering such key areas as line-of-sight full motion video, bandwidth efficient common data link, wide area sensor, and weapons interfaces.

4.4.8.7. Coordinate with other Service and OSD representatives and with key AF technical experts at MAJCOMs, SPOs, and Research Laboratories to make recommendations that enable interoperability beyond line of sight.

4.4.8.8. Review USIPs for accuracy and coordinate their review across key AF offices.

4.4.8.9. Primary senior SME and AF RPA point of contact for current and emerging family of specifications of the common data link (CDL). Attends Joint CDL Working IPT meetings and coordinates with AF CDL Lead agency (AFISRA) on AF’s CDL roadmap and recommends projects and plans that support AF interoperability across the joint warfighting community.

4.4.8.10. Develop recommended concepts and plans for furthering and improving AF ISR Enterprise interoperability to include organizational and process changes and action needed. Work closely with CDL Executive Agent to understand new CDL initiatives and their impact on AF programs.

4.4.8.11. Senior SME for AF Lead SME for RPA Encryption supporting MQ-1, MQ-9, RQ-4, and SUAS.

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

4.4.8.12. Orchestrate AF RPA Encryption Working Group to include establishing recurring VTCs, developing necessary technical and process briefings, identifying potential problems areas and proposes action items and recommending plans to mitigate.

4.4.8.13. Liaison with other HAF, MAJCOM, SPO offices with the Cryptographic Systems Group, and with Industry to recommendations that ensure all actions and equipment will be developed in a timely manner to include cryptographic systems and key management plans.

4.4.8.14. Senior SME for HAF functional lead for SUAS Data Link and Encryption Initiative and focal point for Secure Micro Digital Data Link (SMDDL), an AFRL and Draper Labs initiative, supported by AFSOC, to develop an light weight, NSA approved Type 1 cryptographic solution for Secret and below data that allows for over-the-air-rekeying, is disposable, and combined with a network enable data link supporting size, weight, and power (SWaP) constrained RPAs.

4.4.8.15. Senior SME for AF RPA Capabilities Division lead for RPA satellite communications for MQ-1, MQ-9, RQ-4, and SUAS.

4.4.8.16. Interact with AFSPC and SMC SATCOM POCs, and ACC and AFSOC RPA requirements offices to capture RPA SATCOM needs for current and future operations.

4.4.8.17. Coordinate with SAF/A6, AF/A2, SAF/AQ staffs to recommend RPA Long Haul communications architectures.

4.4.8.18. Assists AF/A2CU with AF position development regarding lead command and SPO; help develop and coordinate positions for CORONA.

4.4.8.19. Senior SME on long endurance RPA communications capability and studies.

4.4.8.20. Develop analysis and briefings and writes white papers as needed to articulate recommended long endurance RPA communications capability; work with SAF/AQRT and with research agencies to include DARPA, MIT Lincoln Labs, Johns Hopkins, Rand Corporation, and Industry to identify technology opportunities to support long endurance communications needs supporting the warfighter.

4.4.8.21. Develop recommendations and coordinate communications sections in support of the AF RPA Vector.

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

4.4.8.22. Develop recommended communications goals and objectives, identify interconnections and timelines for developing and implementing RPA communications capability, and assists with synchronizing across DOTMLPF.

The minimum requirements are for the RPA Command & Control SME are as follows (all minimum requirements must be met):

• Bachelor’s Degree from accredited college or university;

• ten years experience that demonstrates a comprehensive knowledge and understanding of RPA Global Communications architectures, systems, and associated command and control (C2) systems and relationships

• five (5) years of Joint Capability Integrated Development (JCID) process experience to support government oversight of programs, processes, operations, exercises and other activities;

• five (5) years of experience planning and programming experience with Medium and High Altitude RPA communications, C2, test and evaluation, CONOP and doctrine development, participation and requirements development and technology transition;

• five (5) years of experience interfacing with Congressional staffs to provide information concerning Air Force RPA and SUAS C2 system operations remotely piloted ISR forces and assets;

• five (5) years of Air/Joint/OSD Staff Experience that demonstrates the ability to analyze complex RPAC2 issues and develop recommendations for USAF and OSD senior leadership;

• and five (5) years of Technical experience with planning/identification of future RPA and SUAS, requirements for electromagnetic spectrum capabilities and requirements.

In addition, to the aforementioned minimum requirements the successful candidate must demonstrate the following:

• Demonstrated technical expertise and systems knowledge needed to address DoD critical and time-sensitive issues regarding rapid identification and fielding of RPA technologies

• Specialized RPA C2 knowledge and expertise that can provide viable, informed

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

5.0 Deliverable(s): The Contractor shall provide task order deliverable(s) in a format mutually agreed upon by the Government and the Contractor. The COR and the CO may require copies of listed deliverables when and as requested/appropriate. (All deliverables become the Government’s sole property and can be distributed to others as the Government deems necessary.

The contractor retains no ownership rights in any deliverables and cannot share or distribute the information to persons outside the Government).

Support Area Title Delivery

Date/Description Analysis, Evaluation, Studies and Recommendations 4.1, 4.2, 4.3, 4.4, 4.5 Includes all applicable sub-tasks

Analyze, conduct reviews, provide recommendations and insights on the development & implementation of DOD Strategic Guidance impacting RPA/ISR. Coordinate on CONOPS, CONEMPs, TTPs, test/evaluation reports, and other similar products to maximize UAS utility.

As Required

Develop Briefings, Plans, Issue/Point Papers, Reports or Publications 4.1, 4.2, 4.3, 4.4, 4.5 Includes all applicable sub-tasks

Prepare, coordinate & present professional briefings and other forms of documents for seminars, working groups, conferences, congressional and media inquiries, and other A2C related activities

As Required

Budget Development and Justification 4.1, 4.2, 4.3, 4.4 Includes all applicable sub-tasks

Provide various forms of documents for UAS program validation and justification--existing and future UAS programs (end-to-end: aircraft, sensors, payloads, weapons, ground control stations, C2 links, communications architecture and TPED.

As Required

Data Gathering and Analysis 4.1, 4.2, 4.3, 4.4 Includes all applicable sub-tasks

Gather data from across the DoD and industry, and from recent studies and analyze the needs/benefits and provide recommendations

As Required

Planning, Requirements Analyses, Technical Assessments and Program Reviews 4.1, 4.2, 4.3, 4.4 Includes all applicable sub-tasks

Develop required documentation for implementation of SECDEF and SECAF directed operations, research, development and acquisition, and sustainment activities.

As Required

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

Planning, Requirements Analyses, Technical Assessments and Program Reviews 4.1, 4.2, 4.3, 4.4 Includes all applicable sub-tasks

Provide required documents in support of development and proposal of solutions for RPA/UAS C2. Identify future UAS requirements.

As Required

Plan, Organize, & Facilitate Meetings, Working Groups, Seminars, Conferences and Other Related Activities 4.1, 4.2, 4.3, 4.4 Includes all applicable sub-tasks

Develop activity plans relating to the specific event and coordinate related actions as required/applicable to related meetings, etc.

As Required

Trip Reports 4.1, 4.2, 4.3, 4.4 Includes all applicable sub-tasks

Trip Reports Provide report within 5 Working Days of return

Attachment A: Services Summary

Table 2 - Services Summary Performance Objective PWS Paragraph Performance Threshold

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

4.1, 4.2, 4.3, 4.4 Includes all applicable sub-tasks

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.

SS2: Provide recommendations and propose solutions based on research, analyses, risk assessments, and review of concepts, staff packages and other reports

4.1, 4.2, 4.3, 4.4 Includes all applicable sub-tasks

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.

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

SS3: Provide all required reports, analyses, briefings, and other related documents as outlined in the PWS

4.1, 4.2, 4.3, 4.4 Includes all applicable sub-tasks

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.

SS4: Provide RPA & UAS support to govt personnel in various forums and meetings

4.1, 4.2, 4.3, 4.4 Includes all applicable sub-tasks

Zero (0) technical knowledge discrepancies with reports, analysis, and recommendations.

SS5: Prepare and facilitate events;

provide post-event minutes and summaries within 5 business days

4.1, 4.2, 4.3, 4.4 Includes all applicable sub-tasks

No more than three (3) substantiated errors in event planning, execution, post-event minutes.

Section D – Packaging and Markings

All deliverables shall be marked with the contractor’s name, contact information, date delivered, and contract number

Section E – Deliveries & Performance

E.1 All inspection and acceptance terms are contained in FAR 52.212-4 for firm-fixed-price CLINs.

E.2 Contractor Responsibility. The Contractor is responsible for the day-to-day inspection and monitoring of the Contractor work performed to ensure compliance with contract requirements.

All work performed under this contract shall be of the highest quality and in keeping with the best practices of the industry.

E.3 Services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 Destination Government Destination Government 0002 Destination Government Destination Government 1001 Destination Government Destination Government

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

1002 Destination Government Destination Government 2001 Destination Government Destination Government 2002 Destination Government Destination Government 3001 Destination Government Destination Government 3002 Destination Government Destination Government

Section F – Deliveries & Performance

F.1 Period of Performance. The period of performance for this contract will be a 12-month base period and three 12-month option periods.

F.2 Place of Performance. Work will be performed at the Pentagon, Arlington VA; Crystal City, VA; or other government sites within the National Capital Region. The standard workweek is Monday through Friday, except on Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government-directed facility closings. Actual hours vary from office to office within OUSD(I).

F.3 Recognized Holidays. Unless required under the terms of the contract or authorized by the contracting officer, the contractor shall not plan to work at a Government facility on any of the following Government observed legal holidays: New Year’s Day, Labor Day, Martin Luther King Jr.’s Birthday, Columbus Day, President’s Day, Veteran’s Day, Memorial Day, Thanksgiving Day, Independence Day, and Christmas Day.

Section G – Contract Administrative Data

G.1 Submission of Invoices

WHS AD WAWF INVOICING INSTRUCTIONS (Apr 2010)

To implement DFARS 252.232-7003, "Electronic Submission of Payment Requests and Receiving Reports (March 2008)", Washington Headquarters Services, Acquisition Directorate (WHS/AD) utilizes WAWF to electronically process vendor requests for payment. The web based system is located at https://wawf.eb.mil, and allows government contractors and authorized Department of Defense (DoD) personnel to generate, capture, process and track invoice and acceptance documentation electronically. The contractor is required to utilize this system when submitting invoices and receiving reports under this contract. Submission of hard copy DD250/Invoice/Public Vouchers (SF1034) is no longer permitted.

The contractor shall ensure an Electronic Business Point of Contract is designated in Central Contractor Registration at http://www.ccr.gov/ and register to use WAWF at https://wawf.eb.mil https://wawf.eb.mil/� http://www.ccr.gov/� https://wawf.eb.mil/�

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF) within ten (10) days after award of the contract or modification incorporating WAWF into the contract. Step by step instructions to register are available at http://wawf.eb.mil.

The contractor is directed to submit the following invoice type:

2-n-1 - Services Only, including Construction **Do NOT use the WAWF Construction invoice type – it is not permitted for invoices paid in the MOCAS system

Back up documentation may be attached to the invoice in WAWF under the “Misc Info” tab.

Fill in all applicable information under each tab.

With the exception of extensions, the following required information should automatically populate in WAWF; if it does not populate, or does not populate completely or correctly, enter the following information as noted:

Contract Number TBD

Delivery Order n/a

Pay DoDAAC HQ0347

Issue By DoDAAC HQ0034

Admin By DoDAAC HQ0034

Inspect By DoDAAC/Extension HQ0208

Service Acceptor DODAAC/Extension or

Ship to DODAAC/Extension or

Service Approver DODAAC/Extension or

Grant Approver DODAAC/Extension

HQ0034/OSDTM2

DCAA Auditor DODAAC/Extension

LPO DODAAC Leave Blank

The Contractor shall verify that the DoDAACs automatically populated by the WAWF system match the above information. If these DoDAACs do not match then the contractor shall correct the field(s) and notify the contracting officer of the discrepancy (ies).

The Contractor will need to enter a Shipment (or Voucher) Number in a specific format.

http://wawf.eb.mil/�

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

• The correct format for a shipment number for MOCAS invoices is AAAXNNN where A = alpha, X = alphanumeric and N = numeric characters, followed by a “Z” suffix if it is a final invoice. (e.g. SER0001, BVN0002Z, SERA003)

• WAWF will affix the prefix “SER” for 2-in-1 invoices and prefix “BVN” for cost vouchers to the Shipment (or Voucher) Number fields. For Combo documents, the contractor may enter their own three letter prefixes.

Take special care when entering Line Item information. The Line Item tab is where you will detail your request for payment and material/services that were provided based upon the contract.

Be sure to fill in the following items exactly as they appear in the contract:

• Item Number: If the contract schedule has more than one ACRN listed as sub items under the applicable Contract Line Item Number (CLIN), use the 6 character, separately identified Sub Line Item Number (SLIN) (e.g. – 0001AA) or Informational SLIN (e.g. – 000101), otherwise use the 4 character CLIN (e.g. – 0001).

• Unit Price

• Unit of Measure

• ACRN: Fill-in the applicable 2 alpha character ACRN that is associated with the CLIN or

SLIN.

Note – DO NOT INVOICE FOR MORE THAN IS STILL AVAILABLE UNDER ANY

CLIN/SLIN/ACRN.

Before closing out of an invoice session in WAWF but after submitting your document or documents, the contractor will be prompted to send additional email notifications. Contractor shall click on “Send More Email Notification” on the page that appears. Add the following email address michael.olsen@osd.mil in the first email address block and add any other additional email addresses desired in the following blocks. This additional notification to the government is important to ensure that all appropriate persons are aware that the invoice documents have been submitted into the WAWF system.

If you have any questions regarding WAWF, please contact the WAWF Help Desk at 1-866- 618-5988.

G.2 Contracting Officer's Representative (COR). The COR shall be the focal point for all contract administration matters related to performance of this PWS. Only the Contracting Officer can make changes to the contract or this PWS, and any such changes are not effective unless directed in writing by the Contracting Officer. The initial COR for this contract is:

LtCol Michael Olsen OUSD(I)/ISR Task Force michael.olsen@osd.mil mailto:michael.olsen@osd.mil�

Intelligence, Reconnaissance, and Surveillance Task Force (OUSD(I)/ISR TF)

The contractor will be notified in writing concerning the replacement of the COR for this contract. Subsequent CORs will be appointed in writing and a copy of the appointment letter will be provided to the contractor.

The COR is NOT authorized to take any direct or indirect actions or make any commitments that will result in changes to price, quantity, quality, schedule, place of performance, delivery or any other terms or conditions of the written contract.

The Contractor is responsible for promptly providing written notification to the Contracting Officer if it believes the COR has requested or directed any change to the existing contract.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .