QA from Ktr Meetings_12-1-20.pdf

1 Dec 2020 Memo for Record

SUBJECT: Consolidation of Questions and Answers from Meetings with Contractors on

Remotely Piloted Aircraft Squadron Operations Center (RPA SOC) Enterprise

1. The purpose of this MFR is to share the common questions asked during the meetings with contractors in response to the Request for Information (RFI) on the RPA SOC Enterprise program.

2. The format below will show questions as solid bullets, and answers as open bullets.

a. Will there be an Industry Day? Will there be Site Visits? Will there be one on one meetings?

o Yes, but it will be virtual. We hope to schedule it soon, maybe within the next 2 months. More news to follow.

o We are working to develop a virtual site visit that will provide maps, some pictures, facility drawings, elevations for equipment to get an idea for technical requirement for install. All this must fit within the security, operations and COVID-19 restrictions.

o Our current plans are to allow 1 on 1’s, but they will also be virtual.

o Security of information will be an issue with the virtual format.

b. Will you issue a Draft Request for Proposals (RFP), and if so, when will it be issued?

Will there be a Section L or M, and what will it look like?

o We plan on issuing a Draft RFP in the spring, 2021.

o There will be both Sections L and M, but we are still developing the acquisition plan at this point. We are looking for ideas on how to make this the most optimum tool for procuring our requirements, while capitalizing on the expertise and business acumen only you can bring to the table.

c. When will the new contract begin? Will there be a transition period? How long?

o We expect the new contract to begin in the spring, 2022.

o We still have not determined the length of the transition period.

d. Will there be another RFI?

o There could be another issued, as we are very interested in learning how to do this acquisition the best way possible. Your input is always welcome.

e. What is the period of performance going to be?

o The current plan is a Base Year with seven (7) one year options.

f. What type of contract will it be? Will this be a Lowest Priced Technically Acceptable

(LPTA) or a Best Value type competition?

o We haven’t finished the Acquisition Plan yet, this is the Market Research portion of the process, and we are still processing the data.

o It will not be LPTA.

o We were looking to industry for feedback regarding the best type contract/trade-offs/incentives to use.

g. Will the contract be a multiple award, single award, ID/IQ, Set-Aside for Small Business, 8(a), Cost Plus or Fixed Price?

o We haven’t finished the Acquisition Plan yet, this is the Market Research portion of the process, and we are still processing the data.

o The UASOCS contract is a combination of FFP for labor and CR for over time, travel OCONUS travel and OCONUS allowances.

h. Who are the incumbents for the current four contracts?

o FA4890-16-C-0007 the “Unmanned Aircraft Systems Operation Center Support

(UASOCS)”; supporting ACC & AETC; Amentum Services, Inc.

o FA8620-20-C-2010, the “Remotely Piloted Aircraft-Squadron Operations Centers

(RPA-SOC) Field Maintenance Site Support”; supporting ANG; Cape Fox Federal Integrators Inc.

o FA8620-20-C-2011, the “RPA SOC Install and Warehouse Support”; Nisga'a Tek

LLC

o H92404-18-C-0002, the “Operations, Maintenance, and Engineering Support To AFSOC RPA Operations Centers And Ground Control Stations”; supporting AFSOC Leidos, Inc.

i. How will you distribute work amongst different task orders/contractors?

o We are still developing the Acquisition Plan and haven’t determined whether TO’s will be used.

j. What is the contract ceiling value? How many FTE’s are required?

o We are still developing the Acquisition Plan, but the value will probably be between $500M to $800M.

o This will be a performance work statement contract, so we won’t direct a set amount.

However, the four contracts named above use over 200 TS/SCI cleared FTEs.

k. Why is the USAF combining these contracts? How will the government manage the different expiration dates of the current contracts?

o The program has grown over the years from a ground up, stove piped, get it done environment, to an integrated well covered, and seamless environment. This effort will finish the ongoing standardization process, and bring “enterprise services” to the user community.

o Depending on the type of contract we use, there are various options to deal with the different expiration dates.

o Our objective will be to ensure continuity of service and retain historical knowledge and expertise.

l. Were there performance issues with the current contracts?

o No, this is an effort to take greater control of the process for procuring like requirements across the USAF.

o There are some gray areas at the demarcation lines, between existing contracts. This new contract is an attempt to clean that up and more clearly define responsibilities.

o However, the new contract will likely emphasize an adherence to USAF policies and cooperation with government requirements in the PWS and Section M.

m. What are the top risks you expect bidders to address, and how will you evaluate them?

o Hiring the large number of Cyber, TS/SCI, and SAP personnel required.

o Employee turnover & vacancies in cyber positions with clearance requirements.

o Past performance which shows high employee retention rates.

o Employee wages vs. price competition.

o Funding is always an uncertainty.

n. What is most important in this contract?

o As stated above in the question about risks, personnel management of Cyber centric, TS/SCI and SAP requirements, while keeping down turnover.

o A good understanding of the SOC requirement.

o Ability to retain historical knowledge of the program, requirements, configuration, and interconnections between SOC, GCS, and Reaper aircraft.

o SOC Integration in the RPA system and its importance to the mission.

o ACC is Lead Command for mission and funding, the 577th SWES is responsible for the configuration, design, programming, and setting the schedule for refresh cycles, software updates and builds.

o. What is the Enterprise concept?

o The Enterprise concept is a holistic approach to eliminate redundancy in an effort and provide a central focal point to the systems that tie the RPA mission operation together.

p. Please explain the organizational structure of the Procuring office, SPOs, and 577th SWES? Will the lines of communication be fully explained in the RFP?

o Yes, the lines of communications will be explained in the RFP, as well as at the

Virtual Industry Day.

o ACC provides mission direction and is managing this procurement (AMIC). RPA

SOC SPO is at WPAFB. 577th SWES at Robbins AFB, supports the SPO, provides the government integrator service, oversight for installation and configuration management, ISR Sustainment Engineering Center and provides software patches.

q. Will GCS be included in the support requirements?

o The majority of the requirement does not include supporting the GCSs, but the

AFSOC requirement does include GCS support.

r. Will contractors be required to provide their own buildings to support the contract performance? Will contractors be required to run Government owned facilities?

o We don’t have any contractor owned facilities; however, the current contractor rented/leased a warehouse for that requirement.

o The USAF is responsible for all government owned facilities.

o The USAF will also provide the contract required cleared facilities.

s. Can the Warehouse be located somewhere other than Warner Robbins GA? Will the USAF provide a plug number for the warehouse?

o The current contract uses a warehouse located in Warner Robbins, which is not on the

Air Force Base. That locations is most convenient for the 577th SWES to perform oversight and inspections. If you want to suggest another location, you will need to address how the 577th SWES oversight requirements can be performed without overburdening them with TDY and time expenses: address the benefits to the USAF.

o Still too early to know if we will use a plug number for the cost of the warehouse, however, it will be a consideration when developing the pricing requirements. Some kind of cost reimbursement will also be a pricing consideration for this requirement.

We understand that this can be an area that could be manipulated to appear to reduce the overall cost, and provide contractors an opportunity gain a competitive edge if not managed properly.

t. Will the contract require purchasing hardware and software? If so, will there be directed Subcontractors/Vendors based on proprietary systems?

o Yes – Both. There will be a large amount of purchasing required on this contract.

o The BOM will be provided and there will be specifically identified requirements.

Current pricing for purchasing requirements is cost reimbursement.

o There is a technical refresh schedule that will be provided, to upgrade systems, and there is a requirement to bring all organizations (except AFSOC) up to the same standardized solution. The standardization requirements are about 8 to 10 SOCs per year.

u. Will the USAF use a plug number for acquisitions? Will you provide an estimated annual amount? Will you provide a sample BOM for anticipated projects? Will you provide portal access to the AFLMSS COTS Module?

o We will consider using a plug number, and/or evaluating proposed rates applied to a plug number. Still too early to state definitively one way or the other. We understand that this can be an area that could be manipulated to appear to reduce the overall cost, and provide contractors an opportunity gain a competitive edge if not managed properly.

o Still too early to state definitively what the pricing requirement will be.

o We will provide a BOM.

o Yes, we will provide access to the AFLMSS COTS information and the required training to access and use the system.

v. Will all material be required to be received at the warehouse?

o Yes.

o Purchases will be shipped to warehouse, where they will be placed into AF inventory, tested, kitted, some will be combined with other purchases to form assemblies (reducing the final installation TDY costs), prior to shipping to install location.

w. Will the contract require software development capability?

o The AFSOC requirement does have some software development requirements, however, the rest of the contract will get their software development needs met through the 577th SWES.

x. Will the contract require engineering solutions, designs or developments? Is the USAF migrating this requirement to the cloud?

o Again, this is the 577th SWES domain, although the AFSOC requirement may utilize these needs.

o No migration plans at this time.

y. Will there be a bidder’s library available?

o Yes. It will be published soon, probably in time for the Industry Day.

z. Will the Appendices and CDRLs be included in the Draft RFP and RFP? Will the contract contain certification requirements? Are there GFE requirements, or a list?

o Yes. The plan is to provide these drafts by Industry Day.

o These attachments will include a GFE list and certification requirements.

aa. Will there be any changes in the RFP’s PWS?

o Unknown. The AFSOC portion of the contract may or may not be part of the final requirement. We don’t have any plans to make any other significant changes to anything at this time.

bb. Are there staffing or retention issues?

o Yes, because this is a Cyber heavy requirement where the majority of the personnel will require TS/SCI clearances. Cyber positions have a high rate of turnover throughout the US. There are many requirements in competitive markets for these type personnel. The ability to manage personnel issues, provide the large number of personnel required, and retain these people will be a factor we use to determine who receives the award(s).

cc. How do you plan to evaluate contractors: past performance, similar experience, large contract experience, etc.?

o Still undetermined, but this is an ACAT III level program with significant risks. The proven capability to manage similar requirements is a likely requirement.

o The requirement is essentially a military system of systems, and we will likely use this concept as proof of past performance.

dd. How will you determine MAJCOM priorities?

o ACC determines mission priorities through the PAROC.

ee. Will you use an initial Task Order in the RFP competition that will be issued at time of award?

o It is too early to say at this point whether there will be a single award, or a multiple award; however, an initial Task Order is a good method of providing a valid price competition example and time saver for the requirement.

ff. Will the contract require contractor vehicles to support the contract?

o No, but incumbent contractors have acquired vehicles to provide rapid transport from one location to another on installations.

gg. Are all the MAJCOMs standardized to a common O&M baseline?

o The Guard is, ACC and AETC will be progressing toward a standardized baseline, but AFSOC may remain unique for the time being.

hh. Will the USAF provide the metrics and methods used to measure customer satisfaction?

o Yes.

ii. Where will the Program Management Office (PMO) be required to locate?

o The Contractor’s PMO is not mandated to be at any location, but common sense may drive specific locations. For example: operational concerns, concentrations of customers, and the PAROC might affect a decision regarding where a UASOCS type requirement located its PMO.

jj. Will there be any new SOC expansions, relocations, or stand-downs?

o We are not aware of any at this time.

kk. Is the ES Helpdesk distributed across multiple groups or a centralized function? Where is it located?

o The current plan is to have a Helpdesk that is centralized to serve across the entire contract.

o We would prefer that it be located at Creech AFB, to be on hand for the PAROC.

ll. Will Associate Contractor Agreements (ACA) be required?

o Yes, whenever there is a requirement to interface with another contractor, you will be expected to work together toward the benefit of the USAF.

o The nature of this work requires cooperation and a willingness to get things done.

We are interested in any ideas you may have to provide incentives to ensure that objective is achieved.

mm. Will a RFI respondents list be provided?

o Yes.

STS International, Inc.

Planned Systems International, Inc. (PSI)

JACOBS

Leidos, Inc.

Pinnacle Solutions, Inc.

MAG DS

Amentum Services, Inc.

Cape Fox Federal Integrators, LLC (CFFI) Chenega Professional & Technical Services (CPTS), LLC Broadleaf, Inc.

Intelligent Waves LLC General Dynamics Information Technology, Inc.

CACI, INC.-FEDERAL

Thunder Ridge Solutions Company

SAIC

System Dynamics International Inc.

Battlespace, Inc.

Hillsboro Aviation, Inc.

nn. Will the Government provide an RPA SOC Program Leads points of contact?

o The POC’s are:

Tony Wheeler – RPA SOC Enterprise Program Manager Madison DeGruy - Contracting Officer 1Lt Cortney Young – Contracting Officer Tony Burns - Contract Manager Stephen Copetas – Contract Manager (Contractor) Corey Collins – RPA SOC IPT Program Lead Stephen Hoover – ACC/A5IQ

oo. Request the government clarify if DPWS 5.1.11 Engineering Support (all) is part of assigned tasks as part of DWPS 2.1.2.3 Planning Support, or an independent function to be initiated by the offeror?

o For SOC PoR requirements, minor engineering support is provided remotely by reviewing drawings, configuration documents, and other documentation such as those that address cyber security concerns. No re-creation of the wheel or contractor derived requirements are expected. However, if the contractor has innovative suggestions for improvement and cost savings, those will be considered for implementation.

o Planning support ties to install and tech refresh efforts. When the tech refresh calls for contractor install, the contractor will be responsible for planning the install around operations in order to minimize the operational impact.

o 5.1.11 is about SOC Enterprise support and potential engineering support that might be required there. 2.1.2.3 is a legacy requirement from the current UASOCS PWS and we can discuss if it needs to remain. It will probably be needed for any SOC support that doesn’t get baselined.

3. There will be further opportunities to question the government during the future Virtual Industry Day.

Tony Burns

ACC AMIC/PKAA

Contract Manager