ASTROS II_Industry QA Matrix_GovResponses_Publication.xlsx
XLSX spreadsheet 42 KB Posted
- Solicitation number
- FA930027R6000-RFI04
About this file
This file is an Industry Question and Answer (Q&A) Matrix documenting government responses to industry inquiries regarding the ASTROS II (Aerospace Systems Technical Research & Operations Support Services II) federal contract opportunity. The matrix consolidates questions submitted by industry partners during the RFI #4 process following an Industry Day event held on July 23, 2026, at Edwards Air Force Base, with responses provided by the Government prior to final RFP release.
The Q&A matrix addresses 46 substantive inquiries across multiple disciplines including contracting strategy, technical requirements, security/cybersecurity, labor standards, personnel qualifications, transition planning, and program management. Key government responses clarify that: the estimated contract value is $250M–$400M over 10 years with detailed scope to be provided in the final RFP; the acquisition strategy remains under finalization with determination pending between FAR Part 15 or OASIS+ task order; facility clearance levels and CMMC Level 2 self-assessment requirements will be detailed in DD Form 254; a 90-day FFP phase-in period is anticipated; labor categories will include professional engineering, systems engineering, test engineering, range operations, instrumentation/telemetry, and safety roles; the Government intends to provide notional historical workload data as Government Furnished Information; Davis-Bacon and Service Contract Labor Standards apply only to construction-related activities meeting statutory definitions; and OCI mitigation will be addressed primarily through contractor-submitted mitigation plans rather than blanket exclusions. The Government confirmed that the final RFP will specify evaluation methodologies for past performance, key personnel requirements, transition plan realism, performance management frameworks, technical scenarios, and cost realism, while deferring final determinations on set-aside status, incentive-fee structures, and specific CLIN alignment to the formal solicitation.
View the file
Other files
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
Instructions
| Industry Question and Answer (Q&A) Matrix Instructions |
| The Industry Q&A Matrix template provided on the adjacent tab must be used by industry partners to submit all formal questions, comments, and recommendations regarding the ASTROS II draft acquisition documents. To ensure a thorough and timely review, respondents must provide complete and accurate entries in all required columns (Columns 2 through 6). |
CRITICAL FORMATTING REQUIREMENT: To facilitate the seamless consolidation of feedback from multiple industry sources, do not alter, delete, or adjust any column widths, cell formatting, or the overall structural layout of the worksheet. Submissions that modify the template's structure may be returned to the sender without review.
Submit completed matrices to the designated POCs by 1600 PST on July 30, 2026. Late or non-compliant submissions will not be reviewed. The Government will consolidate all inquiries and publish formal responses on or before August 06, 2026.
| Column | Title | Description |
| 1 | Item | [DO NOT ALTER] Sequential tracking number. The Government will automatically renumber all consolidated entries once all industry feedback is merged and sorted. |
| 2 | Contractor | Enter the full, legal name of the company representing the inquiry. |
| 3 | Reference (Para/Page) | Identify the specific source document, page number, and section/paragraph to which the question or comment pertains (e.g., PWS, Page 12, Section 4.2). |
| 4 | Type | Categorize the query by the relevant Subject Matter Expert (SME) discipline (e.g., Contracting, Finance, or Technical). |
| 5 | Question/Comment | State the inquiry clearly using complete sentences. For proposed Performance Work Statement (PWS) revisions, use strikethrough to indicate proposed deletions and underlining to indicate proposed additions. Rule: Submit each distinct inquiry as an individual row. Do not consolidate multiple unrelated questions into a single cell. |
| 6 | Rational | Provide a concise, objective explanation justifying the business or technical need for the question or proposed language change. |
| 7 | Decision | [GOVERNMENT USE ONLY] Indicates the formal disposition of the entry: |
• A – Accept (No justification required)
• R – Reject (Requires written justification)
• M – Accept with Modification (Requires written justification) 8 Government Response [GOVERNMENT USE ONLY] Official Government response, including the technical or contractual rationale for the final decision if applicable.
Q&A Matrix
| Industry Question and Answer (Q&A) Matrix | ||||||
| Item | Reference (Para/Page) | Type | Question/Comment | Rational | Decision | Government Response |
| 1 | Davis Bacon Act: Could the Govt clarify which activities are expected to be subject to Davis Bacon requirements and the associated level of effort? | Davis‑Bacon requirements would apply only to activities that meet the statutory definition of “construction, alteration, or repair” of a public building or public work, and not to general services, R&D, testing, integration, or typical contractor support. Based on federal regulations, the Government would need to clarify which ASTROS II tasks involve more than incidental construction, because only those tasks trigger Davis‑Bacon wage determinations. | ||||
| 2 | Labor Categories and Union Labor: Please provide guidance or supplemental documents that describe the anticipated labor categories required to execute the project? Additionally, please confirm whether union labor is required at the place of performance and which roles or activities would union labor be used to comply | The anticipated labor categories for ASTROS II are expected to include professional engineering, systems engineering, test engineering, range operations, instrumentation/telemetry, data systems, safety, project management, mechanical and technical support roles. The Government should provide any supplemental labor‑category guidance or mappings (e.g., SCLS applicability) to support accurate pricing and workforce planning. |
Union labor is not typically required at Edwards AFB for RDT&E or range‑support activities. Union labor would only be applicable if the contract includes construction, alteration, or repair of real property, in which case Davis‑Bacon trades (e.g., electricians, carpenters, laborers, pipefitters) may be required.
3 Estimated Contract Value Breakdown: The RFI provides an estimated total contract value of $250M–$400M. Could the Government provide a breakdown of the major activities included in this estimate (e.g., permitting, construction/installation, engineering, etc.) to better understand the expected level of effort? The Government cannot provide a specific cost or percentage breakdown of the estimated contract value. The $250M–$400M figure is a preliminary, high-level planning estimate covering the entire 10-year period of performance, including all option periods.
The final RFP will provide a detailed, structured CLIN matrix and a comprehensive Performance Work Statement (PWS) that will clearly define the scope of work for each activity. Offerors are expected to develop and propose their own independent staffing, management, and pricing models based on the detailed requirements established in the final solicitation.
4 Contract Terms: Could the Government share draft/final contract terms and conditions associated with this potential procurement? Onerous LOFC and OCI clauses often result in a no bid decision which limits competition. The Government acknowledges the importance of balanced OCI and LOFC terms in fostering open competition. The Government's intent is to resolve potential conflicts of interest primarily through contractor-submitted OCI Mitigation Plans rather than relying on restrictive, blanket exclusions or broad LOFC clauses.
The draft solicitation will include any contemplated OCI provisions and clauses, in accordance with FAR Subpart 9.5. Offerors will be given the opportunity to review these clauses and propose tailored mitigation strategies. The Government highly encourages industry to provide specific feedback on any proposed terms during the draft RFP comment period to ensure a balanced approach that protects both procurement integrity and industry's future participation in broader DoD programs.
| 5 | Industry Day Briefing, pages 29-30, Relevant Past Performance Factor | Evaluation/Past Performance | Given that Affiliate Past Performance benefits the agency and increases the field of competition, for purposes of evaluating relevant past performance and corporate experience, we recommend the Government consider the past performance and experience of an offeror's subsidiary or affiliated entity when the proposal demonstrates that the affiliate's resources, personnel, management, systems, or capabilities will be meaningfully involved in ASTROS II performance. | This approach allows offerors to present references that accurately represent the resources and capabilities committed to ASTROS II while enabling the Government to distinguish integrated mission experience from performance covering only individual support functions. | The Government acknowledges the recommendation. In accordance with RFO 15.202(c)(3)(iii), the evaluation will take into account the past performance of predecessor companies, key personnel, and subcontractors that will perform major or critical aspects of the requirement, provided that the proposal demonstrates the resources of the affiliate will be the resources performing the contract |
| 6 | Industry Day Briefing, pages 29-30, Relevant Past Performance Factor | Evaluation/Past Performance | We further recommend that greater relevance be assigned to efforts demonstrating integrated responsibility for propulsion RDT&E test operations, test-stand operations and maintenance, test-stand buildup and modification, hazardous or energetic systems, configuration management, logistics and property accountability, safety and environmental compliance, and Work Plan cost and schedule management, rather than efforts limited to isolated functional elements. | Defining relevance around that integrated mission will help distinguish complete operating-environment experience from references covering only individual support functions. | The Government acknowledges the recommendation and will take this feedback into consideration when finalizing the Past Performance evaluation factor. The Government's intent is to evaluate past performance in a manner that provides the best assessment of an offeror's probability of successfully performing the required work. |
| 7 | Industry Day Briefing, pages 5, 16, and 29-30; Draft PWS, Sections 3.3, 4.0, 5.2, and 5.3 | Personnel Recruitment and Retention/ Program Management | This approach will allow offerors to present references that accurately represent the resources and capabilities committed to ASTROS II while enabling the Government to distinguish integrated mission experience from performance covering only individual support functions. | ASTROS II requires specialized personnel to safely operate, maintain, modify, and support complex propulsion-test systems and hazardous operations. | See Item 8 |
| 8 | Industry Day Briefing, pages 5, 16, and 29-30; Draft PWS, Sections 3.3, 4.0, 5.2, and 5.3 | Personnel Recruitment and Retention/ Program Management | We recommend the Government require offerors to provide substantiation to demonstrate the credibility and availability of their proposed workforce including existing or committed personnel. | Evaluating workforce readiness, qualification continuity, and time to readiness will help the Government assess whether each proposed approach can support uninterrupted mission performance. | The Government acknowledges the recommendation. The evaluation of an offeror's recruitment and retention plan under the Mission Capability factor will consider the soundness of the approach to rapidly sourcing, qualifying, and retaining the specialized personnel required for this effort. Offerors are encouraged to provide evidence to substantiate their proposed approach. |
| 9 | Draft PWS, Appendix A and Section 6.0; Industry Day Briefing, pages 14, 26, and 29-30 | Technical/Mission Capability/ Configuration Management | We recommend the Government include in the PWS a requirement for a phased, integrated configuration-management and digital-engineering capability that connects test-stand PP&E, technical data, engineering changes, Work Plan records, verification evidence, and as-built and as-maintained configuration information. The requirement should address interoperability with mandatory Government repositories and applications; preservation of approved configuration-control processes; cybersecurity and information-control requirements; Government access and data rights; required data and model formats; records retention; data portability; and transfer or continued Government access at contract completion. | An integrated configuration-management and digital-engineering capability will improve technical traceability, engineering-change impact assessment, decision support, and configuration awareness while preserving mission continuity, Government ownership of technical data, cybersecurity compliance, and long-term portability. | The Government acknowledges this recommendation and is reviewing the PWS to ensure configuration and data management requirements are aligned with current digital engineering best practices and long-term data portability needs. Please refer to the final RFP and revised PWS for updated language. |
| 10 | Draft PWS, Section 5.5; Industry Day Briefing, pages 21 and 23 | Mission Capability/Program Management/Cost | Given the requirement to maintain uninterrupted propulsion-test operations during phase-in, we recommend the Government require offerors to submit and substantiate a transition plan addressing the time, cost, staffing, qualification, safety, property, technical-data, and active Work Plan impacts associated with assuming full responsibility for ASTROS II performance. | ||
| Transition to ASTROS II involves more than administrative contract turnover. It requires the incoming contractor to establish a qualified workforce, assume responsibility for safety-critical propulsion-test operations, validate the technical and property baselines, maintain active Work Plans and test schedules, and implement approved management and compliance processes without disrupting the AFRL/RQ-West mission. | See Item 11 | ||||
| 11 | Draft PWS, Section 5.5; Industry Day Briefing, pages 21 and 23 | Mission Capability/Program Management/Cost | We also recommned the Government evaluate the realism and mission risk of each offeror’s transition assumptions, including: |
• Availability and retention of qualified on-site personnel;
• Time required to obtain site-, system-, safety-, security-, environmental-, calibration-, and test-operation qualifications;
• Continuity of active tests, Work Plans, maintenance activities, and emergency-response capabilities;
• Independent validation of transferred property, technical records, procedures, qualifications, configuration information, and work status;
• Establishment and approval of required quality, safety, cybersecurity, environmental, property, and program-control processes;
• Dependencies upon hiring incumbent personnel, receiving incumbent cooperation, or obtaining Government-furnished training, records, access, and approvals; and
| • Temporary duplication of outgoing- and incoming-contractor personnel or activities necessary to protect mission continuity? | Evaluating realims of the transition plan and ability to address the mission risk ensures the transition runs smoothly without disrupting ongoing mission critical activities. | The Government acknowledges this recommendation. The final RFP will require a Transition Plan to be submitted as part of the proposal. The Government's evaluation will consider the degree to which the proposed transition plan is realistic and demonstrates a thorough understanding of the requirements and risks associated with assuming full performance responsibility without disruption to the mission. | ||||
| 12 | Industry Day Briefing, pages pages 29 and 30 | Technical Scenario | We recommend the Government designate at least one representative technical scenario as an awardable task or Work Plan. | Awardable tasks require offerors to propose realistic costs to ensure their ability to execute. Designating at least one representative scenario awardable avoids requiring every technical scenario to become an awardable task. | The Government acknowledges the recommendation. The Government is considering the best approach to evaluate technical understanding and cost realism for the proposed scenarios. The final RFP will detail the specific evaluation methodology. | |
| 13 | Industry Day Briefing, pages pages 29 and 30 | Technical Scenario / Cost / Price | We recommend the Government consider requiring offerors to submit a supporting Basis of Estimate for the scenarios with the Basis of Estimate identifying, as applicable, proposed labor categories, labor hours, schedule assumptions, materials, equipment, travel, other direct costs, subcontractor support, technical assumptions, and principal cost and schedule risks. | BOEs provide substantiation for the approach and staffing to demonstrate understanding of the work and ensure realistic costs. | The Government acknowledges the recommendation. The final RFP will provide instructions regarding the level of detail required for the cost/price proposal to allow for an adequate cost realism analysis. | |
| 14 | Industry Day Briefing, pages pages 29 and 30 | Areas of Evaluation | We recommend the Government consider requiring offerors to propose a performance-management framework that includes measurable performance objectives and Key Performance Indicators for critical contract outcomes, and Service Level Agreements where appropriate for recurring service areas. The framework should describe how the offeror will measure, monitor, report, govern, and continuously improve performance throughout contract execution. | A proposed performance-management framework will allow the Government to evaluate each offeror's understanding of required outcomes and its approach to measuring, managing, reporting, and continuously improving performance. | See Item 16 | |
| 15 | Industry Day Briefing, pages pages 29 and 30 | Areas of Evaluation | Section L Language for consideration: The Offeror shall propose a performance-management framework that includes measurable performance objectives and Key Performance Indicators for critical contract outcomes, and Service Level Agreements for recurring service areas. It shall demonstrate how the Offeror will measure, monitor, report, govern, and continuously improve performance. |
The proposal shall include, at a minimum:
1. Performance Management Approach
• Identify critical performance areas applicable to proposed technical solution.
• Describe how proposed performance metrics support contract objectives while appropriately balancing cost, schedule, technical performance, and quality.
• Describe the overall methodology for monitoring contract performance.
• Describe the governance structure, management reviews, and escalation procedures used to identify and resolve performance issues.
2. Performance Objectives, KPIs, and SLAs
• Propose measurable performance objectives and KPIs for critical outcomes.
• Where appropriate for recurring service areas, propose SLAs that identify the performance objective, standard or target, measurement method, data source, calculation methodology, reporting frequency, acceptable threshold, target level, and stretch or exceptional level.
4. Performance Reporting: Explain how performance data will be collected, validated, analyzed, maintained, and presented to the Government and describe the reports and dashboards that will provide Government visibility into performance trends, risks, and corrective actions.
| 5. Continuous Improvement: Describe how KPIs and SLAs lessons learned, performance analytics, corrective actions, and preventive actions will be incorporated into ongoing contract execution. The Government may refine final performance measures during post-award transition. The proposed framework will serve as the basis for establishing the Performance Management Plan following contract award. | The proposed framework will provide a substantive basis for evaluating performance-management maturity and for developing the contract's Performance Management Plan and Government surveillance approach following award. Final measures may be refined to align with evolving mission requirements. | See Item 16 | ||
| 16 | Industry Day Briefing, pages pages 29 and 30 | Areas of Evaluation | Section M Language for Consideration: The Government will evaluate the Offeror's proposed performance management approach to determine the extent to which it: |
• Demonstrates a clear understanding of the performance outcomes required under this contract.
• Includes meaningful, measurable, objective, and achievable SLAs and KPIs.
• Provides performance metrics that are relevant to contract objectives and aligned with industry best practices.
• Establishes effective methods for measuring, validating, and reporting performance.
• Demonstrates a proactive approach to performance management, continuous improvement, and risk mitigation.
• Provides Government visibility into contractor performance through regular reporting and performance dashboards.
• Supports effective management of cost, schedule, technical performance, and quality under the applicable cost-reimbursement, incentive-fee, and award-fee structure
| The Government may consider the appropriateness, realism, completeness, and usefulness of the proposed SLAs and KPIs in assessing proposal merit. | Proposed performance objectives, KPIs, and appropriate SLAs will enable the Government to evaluate each offeror's performance-management methodology, assess performance risk, and determine the effectiveness of its approach to monitoring quality, schedule, responsiveness, safety, and mission outcomes. | The Government acknowledges the detailed recommendations for a performance management framework. The Government intends to evaluate the offeror's overall management approach. The final RFP will specify the requirements for what offerors must submit to demonstrate a sound management approach and a clear understanding of the required performance outcomes. | ||
| 17 | Industry Day Briefing, pages pages 29 and 30 | Areas of Evaluation | To increase the likelihood that the contractor can successfully execute the work upon award, reduce performance risk, and improve evaluation quality, we recommend the Government please consider requiring offerors to identify and commit proposed key personnel as part of their proposal? | |
| Suggested Key Positions to include, but not limited to: Program Manager, Deputy Program Manager, Chief Engineer, Critical Workplan Manager(s). | Mission success is highly dependent upon the knowledge, experience, and leadership of contractor personnel responsible for managing and performing the work. Requiring offerors to identify proposed Key Personnel helps ensure that inidividuals evaluated during source selection are the individuals who will execute the contract, subject to Government approval of any substitutions. | See Item 18 | ||
| 18 | Industry Day Briefing, pages pages 29 and 30 | Areas of Evaluation | Key Person Requirements for consideration to include: |
• The individual's full name and proposed labor category.
• A resume not to exceed two (2) pages demonstrating education, certifications, relevant experience, and qualifications applicable to the proposed position.
• A summary describing how the individual meets or exceeds the minimum qualifications identified in the solicitation.
• A signed Letter of Commitment confirming the individual's availability to perform upon contract award.
| • Identification of any current contractual commitments that may affect the individual's availability during the proposed period of performance. | Requiring offerors to submit resumes enables the Government to evaluate the qualifications and experience of the individuals who will perform critical functions, assess performance risk, support best-value source selection, and promote continuity of performance following contract award. | The Government acknowledges the recommendation and is currently evaluating whether to include a Key Personnel clause in the final RFP. Should the Government decide to require Key Personnel, the final RFP will specify the designated positions, minimum qualifications, and proposal submission requirements. | ||||
| 19 | Attachment+1_ASTROS+II+Industry+Day+Briefing_20260723, PAGE 5 | Contracting | Slide 5 mentions "systems engineering" as a point of emphasis. Could you provide further context on the scope of this role and its relationship to test engineering and also the existing digital engineering initiative at AFRL? | Systems engineering is a very broad discipline, so the further clarification of this objective will help deliver partnership success. | Systems engineering serves as the program‑level integrator: managing requirements, architecture, interfaces, configuration, and V&V to keep technical baselines aligned across test campaigns. It supports test engineering and test system design by translating objectives into requirements and derived requirements, ensuring instrumentation/telemetry alignment, maintaining interfaces, integrating safety and readiness reviews, and sustaining the digital thread from modeling through test execution and analysis. It also anchors AFRL’s digital‑engineering initiative by maintaining MBSE artifacts, integrating digital test‑planning tools and range models, and ensuring contractor deliverables align with AFRL’s digital‑engineering standards. | |
| 20 | Industry Day Briefing, pp. 29-33 | Contracting | Please identify the acquisition strategy the Government currently expects to use for ASTROS II and the anticipated date for deciding between a FAR Part 15 procurement and an OASIS+ fair-opportunity task order. If OASIS+ is selected, please identify the specific domain, contract family, and applicable CLIN. | The final acquisition path determines which entities are eligible to serve as prime contractor, where the solicitation will be released, and how SSU should structure its team and proposal resources. | The Government is still finalizing its market research to determine the most appropriate acquisition strategy. The final determination will be made prior to the solicitation's release. The Government's objective is to select the path that provides the best value and most efficient procurement for this requirement. | |
| 21 | Industry Day Briefing, pp. 24 and 31-32 | Contracting | Please state whether the Government currently anticipates a total small business, SDVOSB, or other socioeconomic set-aside under either acquisition path. Please also clarify whether any applicable limitations on subcontracting or self-performance requirements will be evaluated at the task-order level, contract level, or by CLIN. | The set-aside and self-performance framework will affect prime eligibility, workshare, subcontracting strategy, and the allocation of technical and operational responsibilities. | The final set-aside determination is pending the results of ongoing market research. Should the acquisition be set aside for small businesses, the solicitation will include the applicable RFO clauses regarding limitations on subcontracting, and compliance will be evaluated in accordance with the terms of the solicitation. | |
| 22 | Industry Day Briefing, pp. 29-30 | Past Performance | Will the Government evaluate the relevant experience and past performance of the prime offeror together with that of proposed major subcontractors or strategic teaming partners? If so, please explain how the Government will consider each entity's recency, relevance, quality, proposed workshare, and responsibility for the work performed. | SSU may rely on specialized teammates for discrete rocket propulsion, test infrastructure, and technical integration functions. Clear attribution rules will support an accurate evaluation and a team structure aligned to the proposed workshare. | The Government will evaluate past performance in accordance with RFO 15.202(c)(3)(iii). The evaluation will take into account the past performance of the prime contractor and any proposed major subcontractors or teaming partners that will perform critical aspects of the requirement. The final RFP will provide the detailed methodology for how past performance will be evaluated. | |
| 23 | Industry Day Briefing, pp. 27 and 34 | Security/Cybersecurity | Please confirm the anticipated facility clearance level, safeguarding capability, personnel clearance levels, and CMMC requirement for the prime contractor and subcontractors. Please identify which requirements must be satisfied at proposal submission, contract award, phase-in, and before access to classified information or CUI, including whether CMMC Level 2 must be supported by a self-assessment or C3PAO certification. | Entity-level timing is necessary to plan staffing, information-system access, subcontractor participation, transition activities, and the protection of classified and controlled information. | All security requirements, including facility and personnel clearance levels, will be formally detailed in the DD Form 254 attached to the final solicitation. |
Regarding Cybersecurity Maturity Model Certification (CMMC), the Government confirms that a CMMC Level 2 self-assessment, with results posted in the Supplier Performance Risk System (SPRS), is a current requirement.
The previously briefed phased rollout timeline that would have mandated a C3PAO third-party certification is currently on hold across the Department of Defense, with no timetable for reinstatement.
The final solicitation will specify the exact CMMC requirements binding at the time of award.
| 24 | RFI #4 Notice, Section 4; Industry Day Briefing, pp. 14-16 | Technical | Please identify the positions the Government anticipates designating as key personnel and the minimum qualifications for each. Specifically, will a Chief Systems Engineer or equivalent be required, and must that individual be a direct employee of the prime contractor? Please identify anticipated education, professional credentials, clearance, on-site presence, and direct rocket propulsion or test-infrastructure experience. | Defined key-personnel requirements will allow industry to propose the appropriate technical authority, staffing model, recruiting plan, and level of direct prime-contractor control. | The Government is currently evaluating whether to designate Key Personnel for this effort. Should the Government decide to do so, the final solicitation will identify the specific positions and minimum qualifications. |
| 25 | Industry Day Briefing, pp. 14-16 and 25-26 | Technical | Please clarify the allocation of technical authority between the Government and contractor for new infrastructure and modifications to existing infrastructure, including requirements approval, design approval, configuration control, safety approval, test readiness approval, operational release, and final acceptance. Please also identify any professional engineering stamping, independent review, or Government design-agent requirements. | Clear decision rights and approval boundaries are necessary to establish the systems engineering process, price the required technical leadership, control liability, and avoid unauthorized or duplicative reviews. | The Government is expected to retain primary technical authority for requirements, design, configuration control, safety, test readiness, operational release, and final acceptance for any new or modified AFRL infrastructure. Contractor designs and changes would require Government review and approval. |
PE stamping may be required for structural, civil, electrical, mechanical, or pressure‑system work. Independent engineering or safety reviews may apply depending on scope, and AFRL may use a Government design agent (e.g., BCE, AFCEC, AFRL engineering authority) for facility‑affecting design validation.
| 26 | Industry Day Briefing, pp. 14-16 and 28-30 | Personnel/Program Management | Will the solicitation provide an incumbent organization chart and staffing matrix showing labor categories, authorized and filled FTEs, vacancies, work locations, shifts, overtime, on-call or emergency coverage, clearance levels, certifications, and minimum qualification requirements? | The staffing baseline is required to develop a credible recruitment, retention, phase-in, compensation, and continuity-of-operations plan for a remote and specialized labor market. | Incumbent-specific organizational charts and staffing information are considered proprietary to the current contractor and will not be released by the Government. Offerors must base their staffing approach on the requirements outlined in the PWS |
| 27 | Industry Day Briefing, pp. 15, 17-18 and 25 | Finance/Program Management | Will the solicitation provide historical workload data by CLIN and Work Plan, including the number and value of Work Plans, annual labor hours, test operations tempo, ad hoc test requests, PMI and TMDE workload, maintenance backlog, emergency-response activities, test-stand modifications, material and ODC usage, CAP purchases, and peak or surge staffing? | Historical workload and demand variability are needed to develop realistic staffing, cost, schedule, funding run-out, and surge-response assumptions for the cost-reimbursement CLINs. | The Government will consider providing notional or sanitized historical workload data as Government Furnished Information (GFI) with the final RFP to assist offerors. The Government makes no guarantee that future workload will match historical patterns. |
| 28 | Industry Day Briefing, pp. 18 and 25-28 | Property/Configuration Management | Will the RFP include a validated inventory of GFP and CAP showing ownership, location, condition, calibration status, maintenance history, open deficiencies, and disposition requirements, together with available as-built drawings, technical data packages, software and firmware baselines, configuration records, and applicable data-rights restrictions? | A verified property and technical baseline is essential for transition planning, cost realism, maintenance and calibration scheduling, configuration control, risk identification, and accurate turnover accountability. | The Government intends to provide a detailed list of Government Furnished Property (GFP) as an attachment to the final RFP. The availability of supporting technical data will also be addressed in the final solicitation. |
| 29 | Industry Day Briefing, pp. 9, 14-15 and 27-28 | Facilities/Operations | Please distinguish the facilities and base-support services that will be provided by the Government or Edwards AFB from those that will be the contractor's responsibility. Please address utilities, grounds maintenance, custodial services, fire and emergency medical support, security, refuse and pest control, telecommunications, warehouse support, facility repair, vehicles, fuel, and test-area transportation. | Clear responsibility boundaries are required to scope facilities operations, logistics, staffing, vehicle support, indirect costs, emergency response, and continuity requirements without duplicating Government-provided services. | The Government's intent is to provide the base support services as outlined in the Industry Day briefing and Appendix C of the Draft PWS attached to RFI#1. The final PWS and relevant attachments in the RFP will formally delineate all Government-provided versus contractor-responsible services and facilities. |
| 30 | Industry Day Briefing, pp. 18 and 25 | Construction/Labor Standards | Please clarify whether the Test Stand Build-Up and Modification CLIN may include site preparation, construction, utility integration, modular or prefabricated facilities, secure or controlled spaces, control rooms, technical equipment rooms, and associated testing and commissioning. Please identify the thresholds or criteria distinguishing construction from repair, maintenance, and equipment modification, along with any bonding, licensing, permitting, professional engineering, Davis-Bacon, or Service Contract Labor Standards requirements. | The anticipated physical scope and labor-standards treatment will affect team composition, subcontracting, estimating, insurance, bonding, schedule, and the allocation of engineering and construction responsibilities. | The Test Stand Build‑Up and Modification CLIN is expected to include equipment installation, system integration, and test‑stand configuration, but the Government must clarify whether the CLIN also includes site preparation, civil construction, utility tie‑ins, modular/prefabricated structures, secure/controlled spaces, control rooms, technical equipment rooms, and associated testing/commissioning. These activities vary significantly in scope and may trigger different regulatory requirements. Final determination will occur during contract execution through the Work Plan process, where the Government and contractor team will jointly develop each Work Plan on a case‑by‑case basis to define the specific activities and applicable requirements. |
| 31 | Industry Day Briefing, pp. 18, 21 and 23 | Transition | Please state the anticipated duration, scope, and acceptance criteria for the FFP phase-in period, including incumbent cooperation, site and system access, badging and clearance processing, employee transition activities, transfer of technical data, joint property inventory, calibration and maintenance backlog validation, open Work Plans, and any planned overlap with the incumbent. | The phase-in is separately priced on an FFP basis. Defined assumptions and Government support are necessary for comparable pricing and a credible transition without disruption to test operations. | The anticipated FFP phase‑in period is 90-days, but is subject to change. The phase‑in scope should address incumbent cooperation, site and system access, badging and clearance processing, employee transition, transfer of technical data, joint property inventory, calibration and maintenance backlog validation, and disposition of open Work Plans. |
| 32 | Industry Day Briefing, pp. 23 and 25 | Contracting/Finance | Please explain the anticipated criteria for assigning Work Plans to CPFF, CPIF, or CPAF CLINs; the planned incentive-fee or award-fee structure; and the process and target timelines for Work Plan request, proposal, negotiation, authorization, modification, and definitization. Please also clarify the treatment of fee, handling, and indirect costs on travel, materials, ODCs, and CAP. | The hybrid structure and Work Plan cycle will materially affect risk allocation, estimating, cash flow, management controls, and the contractor's ability to respond rapidly to emergent test requirements. | The Government is finalizing the hybrid contract structure. The final RFP will provide the detailed criteria for how work will be aligned to each CLIN and will include the full details of any incentive or award-fee structures. |
| 33 | Industry Day Briefing, pp. 7-10 and 25-28 | Technical/Acquisition | Does the Government plan to conduct a pre-proposal site visit and provide a controlled technical library or bidder data room? If so, please identify the anticipated timing and access requirements and whether the materials will include facility and test-stand descriptions, drawings, equipment inventories, maintenance and calibration backlogs, historical Work Plans, safety and environmental requirements, and current technical and configuration data. | The Rocket Lab contains specialized, safety-critical facilities that cannot be fully understood from the public briefing. Controlled access to site and technical information will improve proposal accuracy and reduce assumptions, contingencies, and cost risk. | The Government does not anticipate conducting an additional site visit after the Industry Day tour. The Government is evaluating the feasibility of providing a controlled technical library and will provide further information in the final solicitation, if applicable. |
| 34 | Industry Day Briefing, pp. 7-9 and 29-30 | Contracting/OCI | Given the AFRL Rocket Lab's public-private partnerships and support to commercial and national-security customers, please identify any anticipated organizational conflict-of-interest restrictions, customer proprietary-data protections, data-segregation requirements, firewall obligations, or limitations on the prime contractor and subcontractors supporting other propulsion customers. | Early guidance will allow offerors to identify potential unequal-access, impaired-objectivity, biased-ground-rules, and proprietary-data risks and to develop appropriate mitigation measures before proposal submission. | The Government will include an OCI clause in the final RFP, if deemed necessary. Offerors will be required to disclose any potential conflicts and may be required to submit a mitigation plan. It is the offeror's responsibility to identify and mitigate any potential OCIs. |
| 35 | Industry Day Briefing | Clarification | Will the Government release a crosswalk identifying the changes between ASTROS I and ASTROS II, including significant additions, deletions, and modified requirements? | A change matrix would help offerors quickly identify substantive changes from the predecessor effort and focus proposal development on new or modified requirements. | The Government does not intend to release a formal change matrix. The ASTROS II solicitation will supersede all previous documents and will stand on its own. Offerors are responsible for reading the final RFP and all associated attachments in their entirety to understand the full scope of the requirements |
| 36 | PWS 5.1 – Work Plans | Clarification | Will the Government provide the estimated annual Work Plan volume, average value, and historical distribution by technical discipline? | Historical workload information will enable offerors to develop realistic staffing models, management processes, and pricing assumptions for this dynamic RDT&E environment. | The Government will consider providing notional or historical workload data as Government Furnished Information (GFI) with the final RFP to assist offerors in developing their staffing and pricing models. The Government makes no guarantee that future workload will match historical patterns. |
| 37 | PWS 5.5 – Transition | Clarification | Will incumbent staffing data be released (e.g., position titles, labor categories, security clearance levels, and years of experience) in a manner that protects proprietary information? | Incumbent workforce information will support realistic transition planning, workforce continuity, and staffing strategies. | The Government typically releases sanitized incumbent staffing information, such as position titles, labor categories, clearance requirements, and general experience levels, only in a form that protects proprietary and personally identifiable information. If provided, this data would be aggregated or de‑identified to avoid revealing contractor‑specific compensation, performance, or competitive business information. |
| 38 | PWS 5.5 – Transition | Clarification | What is the anticipated transition period? | Clarification of the transition period will enable offerors to develop realistic transition schedules and minimize operational disruption. | The Government anticipates a 90-day transition period after contract award. This will be formally established in the final RFP |
| 39 | PWS 5.1 – Work Plans / Appendix B | Clarification | What are the Government's expected response timelines for contractor submission of Work Plans after receipt of a Work Plan Request (WPR), and what are the anticipated Government review and approval timelines? | Understanding expected timelines will help offerors develop responsive management processes and appropriate staffing levels. | The Government is expected to establish standard timelines for Work Plan processing. Typically, contractors are required to submit a Work Plan within a defined window after receiving a Work Plan Request, and the Government follows a corresponding review and approval timeline. |
| 40 | Final RFP – Pricing Structure (Pending) | Clarification | Will pricing be evaluated using representative sample Work Plans, proposed labor rates, estimated workload scenarios, or another pricing methodology? | Clarification of the pricing methodology will promote consistent pricing assumptions and proposal development by offerors. | Pricing may be evaluated using representative sample Work Plans, proposed labor rates, estimated workload scenarios, or another Government‑defined methodology. Confirmation of the specific evaluation method is needed so contractors can align pricing structure, labor mapping, and assumptions with the Government’s intended evaluation criteria. |
| 41 | PWS 5.2 – Security | Clarification | What security clearance levels are anticipated by labor category (e.g., SCI or SAP) and are higher clearance requirements expected for specific Work Plans? | Security clearance requirements directly affect recruiting, transition planning, and workforce availability. | The contract's security requirements, including personnel and facility clearance levels, will be formally detailed in the DD Form 254, Contract Security Classification Specification, attached to the final RFP |
| 42 | PWS 5.1.2 (Attachment 9 Reference) | Clarification | Will Attachment 9, including the Government's labor category qualification requirements, be released with the final solicitation? | The referenced qualification requirements are necessary for developing compliant staffing plans and Work Plan labor estimates. | Yes. Any documents referenced in the PWS that are necessary for proposal preparation, including any attachments detailing minimum labor category qualifications, will be provided with the final RFP. |
| 43 | Industry Day Briefing | Clarification | What key objectives or improvements was the Government seeking to achieve in developing the ASTROS II PWS compared to the predecessor contract? | Understanding the key lessons learned will help offerors tailor their management and technical approaches to address the Government's priorities and reduce execution risk. | PWS aims to improve mission flexibility, workload transparency, configuration control, test‑stand and range integration, safety and readiness processes, data and property accountability, and establish more robust systems engineering process. |
| 44 | Industry Day Briefing / Mission Objectives | Clarification | What mission outcomes would the Government consider indicative of an exceptional ASTROS II contractor during the first year of performance? | Understanding the Government's vision of exceptional performance will help offerors align their technical, management, and transition approaches with mission success. | Exceptional performance will be formally defined and measured against the standards established in the Performance Work Statement (PWS), the Incentive Fee Criteria, and the final Award Fee Plan. |
| 45 | Industry Day Briefing | Clarification | Are there emerging propulsion technologies, test capabilities, or mission areas that the Government anticipates becoming increasingly important during ASTROS II performance? | Provides insight into future mission priorities and allows offerors to highlight innovation and scalability in its technical approach. | The Government is always evaluating emerging technologies. The ASTROS II contract is intended to be a flexible vehicle to support the dynamic RDT&E environment at the AFRL Rocket Lab. Offerors should propose solutions that are agile, scalable, and more robust systems engineering process to accommodate evolving mission priorities. |
| 46 | Final RFP – Pricing Structure (Pending) | Clarification | For positions not directly supporting laboratory or test operations, does the Government anticipate any flexibility for hybrid or remote work arrangements? | Clarifies workforce planning assumptions and may influence recruiting and retention strategies for applicable labor categories. | Due to the integrated, hands-on nature of the site operations and security requirements, this is considered a full-time, on-site requirement. The final RFP will provide any clarification if this position changes. |
| 47 | |||||
| 48 | |||||
| 49 | |||||
| 50 | |||||
| 51 | |||||
| 52 | |||||
| 53 | |||||
| 54 | |||||
| 55 | |||||
| 56 | |||||
| 57 | |||||
| 58 | |||||
| 59 | |||||
| 60 |
Drop Down Options
| Drop Down Options |
| Decision |
| A |
| R |
| M |
File details come from the government source that posted it. Updated .