ACTS Industry Q A.docx
DOCX document 31 KB Posted
- Attached to
- Air Combat Training System (ACTS)
- Solicitation number
- FA3002-10-R-0009
About this file
Industry Comments/Questions and Answers
View the file
Other files
Show all 48
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
Industry Comments/Questions and Answers Air Combat Training System (ACTS), Pre-Solicitation No. FA3002-10-R-0009
1) Q: Does the Government plan to release a draft RFP prior to the RFP release?
A: Yes, but not the entire RFP. Draft Schedule B and draft Sections L&M will be posted in about 10 days from today.
2) Q: PWS para 1.2.3.1.2. “Unrated personnel formerly “Grandfathered” into the “previously rated” experience required position without legitimate prior rating, listed above, will not be accepted.”
All the requirements listed in this PWS were incorporated in the current contract in MOD P00040 and the employees were considered qualified at that time. Is it the governments’ intent to disregard current employees 5 to 8 years of demonstrated proficiency and experience in this position?
A: As this is a new contract, the Govt. has deemed it necessary to incorporate new requirement to better maintain and support this high visibility, flight-safety oriented facility in accordance with Luke Supplement to AFI 13-212. As stated in the new PWS, para. 2.2.2.1.3.1. MINIMUM EXPERIENCE REQUIREMENTS: Based on the unique nature of the range, all radar operators shall have been have previous rated, ATC, or weapons controller experience. . Previous experience within the ROCC does not meet this minimum requirement because it is not an ATC, RAPCON/MRU/GCI facility. The Govt’s objective with this requirement is to provide properly trained individuals to handle this highly visible flight safety facility and to comply with the Luke Supplement to AFI 13-212. Any previously incorporated contract modifications are irrelevant as this is a new requirement that applies only to the new contract.
3) Q: PWS, para 1.2.3.1.2. Contractor personnel who perform duties in controlled or restricted areas shall wear badges clearly depicting the company’s name, employee’s name and employee’s picture. Contractor personnel shall have government provided CAC cards. If an employee has a CAC card and/or USAF restricted area badge is a company ID card also required?
A: PWS should change to read, “Contractor personnel who perform duties in controlled or restricted areas shall wear USAF issued Restricted Area Badges (AF Form 1199A or equivalent). Contractor personnel shall have Government provided CAC cards.”
4) Q: PWS, para, 2.2.3.2. The contractor shall provide maintenance, service, load and operate Remote Smokey Sam launcher systems. How many launch sites are there? And what is the average travel time/mileage to each one?
A: 7 Sites; Average driving time per site is 1 hour each way for an average of 2 hours total trip time per site.
5) Q: PWS, para 2.18 and 2.19 What is the Travel time to Smith Peak and Keystone Peak?
A: Travel time to Smith Peak is aprox. 110 miles from Luke AFB, driving time of 2.5 hours. Travel time to Keystone Peak is 175 miles from Luke AFB, driving time of 3.5 hours.
6) Q: PWS para 2.2.3.1.2.2. A Smokey SAM/AAA burst is launched for IR-SAM/AAA weapon simulations (when requested). Where are the Smokey SAMS stored on the range and who is responsible for the structures?
A: Smokey SAMs are stored at MSA (Munitions Storage Area) at Gila Bend Aux. Air Field (GBAFAF); on range, there are CONEX storage at Comm points (check-in points for range entry.) Govt. is responsible for storage structures; Contractor is responsible of transportation of Smokey SAMs, from GBAFAF to range sites and/or CONEX to launcher.
7) Q: PWS para 4.2.6. Report via web page the real-time operational status of Equipment and Systems listed in Appendix3. Immediately notify the appropriate Government personnel and affected ACTS users of equipment/system status changes and known impact to operations. Is this web site government or contractor built and maintained?
A: The Contractor must develop and maintain a web page in order to meet this requirement.
8) Q: PWS para 2.2.3.1.6.1. Prepare all Data Record Devices (DRD) for the day’s missions. Issue DRDs to the users as provided in the Unit Operating Instructions (OI). Does “issue” mean deliver them to the fighter squadrons or will the fighter squadrons pick them up from the ACTS facility?
A: Issue means sign-out DRD’s to Fighter Squadrons; Fighter Squadron’s will be responsible for delivering/pick-up of DRD’s.
9) Q: PWS para 1.2.3. PERSONNEL. “The contractor shall establish and maintain the total manning levels and skill levels denoted in the contractor's proposal or best and final offer. Manning shall not be reduced below this threshold without approval by the CO (such approval will not be unreasonably withheld). Employee qualifications shall be provided to the CO.”
Performance-based solicitations require the contractor to perform the requirements of the PWS, rather than provide a specified number of personnel. Requiring the contractor to not reduce manning below the threshold of the proposal unduly limits the ability of the contractor to respond to fluctuations in the workload. In addition, please specify what is meant by “unreasonable” with respect to withholding approval.
A: PWS para 1.2.3. Personnel, will be revised to allow offerors to meet the requirement by applying alternative sets of resources as long as the desired outcome is achieved in accordance with the stated performance standards and any other requirements in the contract.
10) Q: PWS para 1.2.4. TRANSITION Does the term “incumbent” refer to the present contractor or is it a reference to the successful bidder for this contract at phase-out of the contract? In other words, is the present contractor contractually obligated to carry out the requirements of PWS 1.2.4.2 during the transition to the new contract?
A: The term “incumbent” refers to the present contractor. During the transition, the “incumbent” is therefore required to fulfill the requirements of the old contract.
11) Q: PWS para .1.2.1. GILA BEND AFAF HOURS OF OPERATION. The paragraph provides insufficient information for bidders to determine the daily staffing requirements and derive a Basis of Estimate (BOE) for a fixed price bid. The Government should provide a matrix showing the number of ranges and systems to be operated simultaneously versus the number of missions that will require each configuration of ranges and range systems, on an annual basis.
A: In the PWS 2.1.2.1. GILA BEND AFAF HOURS OF OPERATION, we give the number of ranges, 1,2,3, and 4. Additionally, Appendix 3 lists locations, types and numbers of equipment. Appendix 6 lists “Work Load Estimates”, complete with previous year sortie counts, mission times, etc. to help with any staffing requirements. Simultaneous operations are varied and are determined by Luke’s Daily Flying Schedule which varies in such degree that a predictable matrix could not be accurately developed.
12) Q: PWS para 2.2.2.1.1. ROCC HOURS OF OPERATION states in part, “Provide a certified ROCC operator on scheduled fly weekends unless additional manpower is required to support the mission as determined by the government.”
How are bidders to determine the extent of the Government’s needs for additional manpower in order to determine their BOE for a fixed price contract? Will additional manpower requirements be separately negotiated/priced, or will the Government provide historical data from which we can construct a BOE?
A: The PWS explains this entire question within this same para. 2.2.2.1.1 ROCC Hours of Operation: there will be 4 fly weekend days per month, any additional manpower requirements will be paid for on a negotiated overtime price through the reimbursable CLIN.
13) Q: PWS para 2.2.2.1.3.1. MINIMUM EXPERIENCE REQUIREMENTS Since finding radar operators with the required ratings may not be possible on short notice, will the Government allow the contractor to hire qualified radar operators who do not have the rating and permit the contractor to upgrade them the required rating? This would also provide a means to cross train and upgrade top performing contractor employees
A:The Govt. will not allow the contractor to deviate from this requirement.
14) Q: PWS para 2.2.2.1.3.2. TRAINING. How is training to be priced? Is it to be included in the fixed price bid or is it to be separately priced? Will the Government provide historical information on the training and certification of contractor personnel in order that bidders should have the same level of understanding of training requirements as the incumbent contractor?
A: The PWS para. 2.2.2.1.3.3. Academic Training lists the requirements for training, and the mode for that training. Training is not separately priced.
15) Q: PWS para 2.2.2.2.1.2.3. ACADEMIC TRAINING Is the existing training program owned by the Government or the incumbent contractor? If owned by the Government, will it be made available to the successor contractor or must the new contractor plan on developing its proprietary training program?
A: The Contractor is responsible for developing its own training program to ensure employees are trained to meet the needs of the contract. The Govt provides necessary references and guidance, as stated within the PWS, to facilitate the Contractor’s training.
16) Q: PWS para 2.2.3.1.2.1. EW THREAT OPERATIONS. The PWS states, “The contractor shall provide a variety of threats tailored and applied to meet aircrew training requirements. The contractor shall operate the type and quantity of EW Threat systems IAW the scheduled profile or scenario and apply the appropriate threat operations doctrine for the weapons systems being simulated.”
This statement is far too broad and vague for bidders to determine EW Threat staffing needs in a fixed price scenario. The PWS fails to provide information as to the number of threats, ranges and participant aircraft that characterize annual aircrew training requirements on a mission-by-mission basis. The Government should provide a matrix of the available threat types required for each aircrew training requirement versus the number of missions anticipated for each requirement, on an annual basis.
A: The PWS lists in Appendix 3 the various Threat Systems and locations. The structure of each Site Specific section within the PWS, sections 2 and 3, Luke and Tyndall respectively list the various systems utilized at each site. Appendix 6 also lists mission and sortie data from previous years to help potential bidders understand operation requirements. Again, the Threat use is varied and determined by the individual air crew’s requirements. The air crew’s requirements are identified when they request EW support.
17) Q: PWS para 2.2.3.5.1. AIRBORNE INSTRUMENTATION SUBSYSTEM (AIS) POD SUPPORT.The paragraph provides no indication of the number of aircraft to be podded on a daily basis for each training support requirement. Bidders therefore have no workload basis for determining the staffing required for pod support. We suggest the Government provides historical data of aircraft podding requirements for each training support requirement, on an annual basis.
A: Appendix 6 lists sortie counts and mission data; this data is specifically listed to assist potential bidders with this type of information and any podding numbers can be determined with sortie counts/mission data information.
18) Q: PWS para 2.3.5. OPERATIONS The wording of this paragraph suggests that the “2 data link GTSs proposed” are future requirements, rather than equipment that is presently in place. Please clarify the status of the 2 data link GTSs. If they are future requirements with an indeterminate schedule for bringing them on line, they should not be included in the FFP contract pricing, but should be separately negotiated and priced.
A: This is a “typo”; there are currently 2 data link sites at Luke. The word “proposed” will be deleted.
19) Q: PWS para 2.4. HELICOPTER LOGISTICS The PWS statement needs better definition in order for bidders to estimate helicopter logistics costs. The solicitation should state the number of flights anticipated, payload requirements, average round trip distances, or provide historical data of flight hours by aircraft type. If we assume that the Government intends the contractor to procure air transport services from a subcontracted commercial source using commercial fuel sources, then uncertainties of fuel costs over the duration of the contract will provide additional financial risk to the contractor in a fixed price contract. Some method to adjust air transportation costs due to changes in fuel prices must be made. In addition the contractor’s liability is undefined in this requirement and there is insufficient workload data to develop an adequate BOE for this requirement.
A: The Govt does not determine how frequently the contractor should or will have to utilize helicopter transport. The systems listed in Appendix 3 and the references within Appendix 2 determine PMI data, and maintenance frequency. It is therefore up to the contractor to determine, with the information provided, the need for the use of helicopter transport.
20) Q: PWS para 3.4.4. OPERATIONS. The PWS states, “There are four Tyndall Link-16 terminals proposed: two at Tyndall (one in Bldg 503 and one in 1801), and two at Carrabelle (Bldg 9908).”
The “proposed” wording suggests that this is a future requirement, undefined as to when it will be implemented. Pricing this requirement within the FFP CLIN provides a financial risk to the successful offeror, because of the unknown escalation in wages, etc. when the terminals are brought into operation. The PWS should therefore state that this requirement will be separately negotiated and priced, as and when required.
A: There are three terminals operational at Tyndall (one in Bldg 503 and two in Bldg 9908) with the fourth as a spare.
21) Q: PWS para 3.6.2. WATERCRAFT MAINTENANCE. (a) We can find no reference to GFE watercraft in the Government Furnished Property list for Tyndall AFB, although the PWS indicates that these are to be Government furnished. Please provide the number and type of watercraft provided and the running hours per year from historical data. This information is required in order that bidders can accurately forecast watercraft maintenance costs. (b)The PWS indicates that “Repairs beyond the contractor’s capabilities shall be accomplished by requesting depot level support.” Please define “beyond the contractor’s capabilities”. How will depot level repairs be funded? Will these be paid by the contractor and subsequently reimbursed by the Government?
A: (a) There are two watercraft at Carrabelle; 65’ heavy work boat with crane (CACRL) and 34’ fast response/SAR craft (GFE listing) See appendix 4.
34’ Boat 2008 26 trips, 81 hours 65’ Boat 2008 63 trips, 918 hours
(b) The watercraft require a Capt and Engineer. They are responsible for the operation and upkeep of both watercraft. Depot repairs will be repair/replacement of major equipment. Routine maintenance (i.e. oil changes, electrical repairs, servicing, ect.) are the responsibility of the contractor. Haulout or major repairs are contracted and purchased separately by the government (local contracting).
22) Q: PWS para 4.2.8.2. COMMAND SUPPORTED EQUIPMENT. The PWS states: “The contractor shall perform all levels of maintenance including overhauls on equipment and systems not currently supported by the Air Force or when the Air Force no longer supports a system. The contractor shall be tasked to perform depot level repair on overhauls on systems not Air Force supported.”
This is an indefinite requirement that cannot be priced as stated. The Government must provide lists of equipment and systems not currently supported by the Air Force, and equipment and systems that will no longer be supported during the next contract term. In addition, some assessment of the condition of the equipment must be provided in order for bidders to estimate the need for depot level repair or overhaul. Alternatively, these maintenance actions could be a separately negotiated and priced.
A: All equipment types and numbers are listed in Appendix 3. Appendix 2 identifies references and technical orders to help contractors determine Air Force Supported equipment.
23) Q: PWS para 4.2.14. TIME COMPLIANCE TECHNICAL ORDERS (TCTO)/COMMAND MODIFICATIONS. These are indefinite delivery, indefinite quantity requirements that cannot be estimated within a firm fixed price bid. The PWS should indicate that they will be separately negotiated and priced as they occur.
A: TCTO’s occur on a random “as needed” basis, the Govt provides the necessary materials and references to accomplish each TCTO. The Contractor is then required to accomplish the TCTO as required utilizing the references and materials provided during normal duty hours. No separate price negations are necessary to accomplish TCTO’s. In the unlikely event that a TCTO adherence requires additional manpower or expertise, the Government will negotiate with the contractor suitable compensation.
24) Q: PWS para 4.3.4. SHIPPING AND RECEIVING. There is no basis in this PWS requirement on which bidders can estimate shipping and receiving staffing requirements. Shipping and receiving therefore presents a financial risk to bidders. The Government should provide historical data the number of line items (1) purchased, (2) shipped and received, on an annual basis for Tyndall and Luke AFBs locations.In addition, the Government should provide the annual dollar value of consumables at each location for pricing purposes, or these should be accommodated in a reimbursable CLIN.
A: All shipping and receiving is through base supply systems, or commercial sources, costs are paid via reimbursable CLIN. Section 1.2.3.5 Logistic Administrative Personnel, clearly identifies the need for Logistic Personnel, and the desired requirements therein.
25) Q: PWS para 4.3.6.1. CONTRACTOR VEHICLES. The contractor is required to “Provide adequate vehicles via GSA (e.g. 4WD vehicles, ATV, etc) to meet the requirements of this contract when the contractor is responsible for such support.” In addition, the PWS states that vehicles are to be obtained from GSA, and that transport includes moving threat systems and providing flight line certified vehicles.
At present, the PWS lacks information on the numbers and types of vehicles to be provided. As a result, the requirement cannot be accurately priced for a FFP contract. The PWS attachments should specify the numbers and types of vehicles to be provided at each ACTS location, and the number of flight line certified vehicles to be provided. The PWS paragraph also states that the contractor is responsible for vehicle maintenance. Most commonly, GSA vehicles are returned to GSA-approved vehicle maintenance stations for maintenance and the contractor’s maintenance responsibilities are limited to routine operator maintenance (fluid levels, tire pressures, etc.). The PWS should state the required maintenance responsibilities of the ACTS contractor.
A: It is up to the Contractor to “bid” a specific number of vehicles. Based on Systems, Locations and Work Load Estimates provided within the Appendices, the Contractor has the information to determine their vehicle needs. Major maintenance is performed via approved GSA vendors; the contractor is required to perform “minor daily use maintenance” which includes tire pressure, fluid levels, etc.
26) Q: PWS para 4.4.4. INTEGRATION, TEST, AND EVALUATION. The PWS requires the ACTS contractor to, “Perform system analysis, integration, test and evaluation of all current and future ACTS hardware, firmware, technical documentation, and software systems”.
The requirement of future ACTS hardware cannot be defined as to technical scope, complexity or schedule and therefore the requirement to provide integration, test and evaluation cannot be priced with any degree of certainty. This presents an unacceptable financial risk to the contractor, particularly in view of new pods and range systems that will be incorporated during the contract period. The requirements for future systems integration, test and evaluation should be separately stated and defined as negotiable task orders.
A: System analysis, integration and test and eval of current systems is part of daily contract duties. Any “future” major system will be handled on a case by case basis, with the contractor and contract modification will be accomplished to incorporate the system/service and support.
27) Q: PWS para 4.4.5.4. ACCEPTANCE TESTING. The requirement for acceptance testing of “scheduled modifications, upgrades, additions to, relocation, reconfiguration, and/or replacements of ACTS hardware, software, and firmware systems and equipment” is an indefinite delivery, indefinite quantity requirement that cannot be adequately defined in the contractor’s fixed price proposal. The requirements therefore present a financial risk to the contractor and should be restated as negotiable separately priced tasks, when required.
A: The contractor as the operator and maintainer of systems, hardware, software, upgrades, etc. needs to be involved in the acceptance process with the Govt for these items. This is not a separate requirement than those of day to day operations and therefore the Govt does not consider a separately priced task.
28) Q: PWS para 7.11. TRAINING. The requirement currently lacks information that bidders can use to generate a BOE for training. The PWS should provide historical man hour data on the annual requirements for contractor support for familiarization, customer support, ACTS overview, personal instruction and general assistance.
A: This is normal daily operations for the Contractor per duty position, i.e. teaching a new air crew member on operations of current ACTS systems, etc. This is not a separate service the contractor provides.
29) Q: PWS para 7.13. CONFIGURATION MANAGEMENT. The successful contractor should not be unduly penalized for configuration management documentation that is not current at contract start and is the responsibility of the incumbent contractor. The Government should provide Report 32: ACTS Hardware and Software Configuration Report, and Report 33: ACTS Physical Configuration Report for the current contract with the final RFP. This will allow bidders to assess the status of configuration management documentation and staff/price the initial task accordingly, to provide updated documentation within the required timeframe at contract start.
A: Configuration Management acceptance is accomplished during Phase-In time frame; upon phase-in, contractor is responsible for review and acceptance of configuration management documentation alongwith all contract management documents.
30) Q: PWS para 7.14. CUSTODIAL SERVICES. The PWS provides no information for bidders to develop a BOE for the custodial services at those ACTS locations where the Government does not provide custodial service. The PWS should provide square footage of carpeted and hard surface areas that the ACTS contractor has responsibility for in order to estimate the staffing required to vacuum and clean carpets, sweep, mop, strip, and wax floors.
A: Building square footage is listed in Appendix 5.
File details come from the government source that posted it. Updated .