HADES DRFP Questions First and Second Round-GovermentResponse_05May2026.xlsx
XLSX spreadsheet 152 KB Posted
- Attached to
- HADES (Hybrid Architecture and Development for Experimental Systems) Draft Request for Proposal
- Solicitation number
- FA8809-26-R-B002
- Issued by
-
Department of the Air Force
About this file
This document is a comprehensive Question and Answer (Q&A) response file addressing industry feedback on the HADES (Hybrid Architecture and Development for Experimental Systems) Draft Request for Proposal (DRFP) released by the Space Systems Command (SSC) Innovation and Prototyping Delta at Kirtland Air Force Base.
The HADES contract is a competitive, multi-year Indefinite Delivery/Indefinite Quantity (IDIQ) acquisition using Cost-Plus-Award-Fee (CPAF), Cost-Reimbursable (CR), and Firm-Fixed-Price (FFP) contract types to procure satellite ground system and satellite operations center engineering, development, integration, and sustainment services at the Research, Development, Test, and Evaluation (RDT&E) Support Complex in Albuquerque, New Mexico. The contract structure includes an initial 60-day transition period (FFP) followed by performance start on February 10, 2027, with base ordering period through February 9, 2030, and four option periods extending through February 9, 2034. Four task orders will be awarded at contract start: one transition task order and three operational task orders (Ground Control, JAGUAR, and Ground Support), with anticipated additional task orders issued during performance. Award fee will be evaluated at the IDIQ level holistically across all task orders using three evaluation areas (Management 40%, Quality of Technical Services 40%, Cost Control 20%), with evaluation periods occurring every six months, and maximum fee limited to 10-12% of direct labor costs. The Government anticipates contract award in October/November 2026, with the final RFP expected by end of May 2026. Key evaluation factors include program management, systems engineering approach, staffing/labor profile, past performance, small business participation (25% overall contract level with 5% Socioeconomic Disadvantaged Business goal), and cost reasonableness, with technical approach and past performance identified as the most important factors in source selection.
View the file
Other files
Show all 41
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
SecondDraftQuestions
| Section | ||||
| - Document | Paragraph - | |||
| Clause | Table / Chart | |||
| (if App) | Paragraph Verbiage in Question | Question / Comment | Government Response | |
| Award Fee Plan | Annex 1: Award Fee Review Board | |||
| Performance Monitors: Personnel in the Innovation and Prototyping Delta Divisions, as appointed by Area Leads. | Will performance monitors be known to the contractor? | They will be assigned at the start of each task order, and will be known to the contractor at that time. |
They will be local Government personnel, attached to the organization. Which individuals are assigned as performance monitors will evolve over the course of the contract and potentially over the course of the task order.
Award Fee Plan Completeness, Clarity, and Understanding The draft Award Fee Plan is well-structured and transparent. The 4 evaluation categories and point allocation are easy to understand.
Recommendation for improvement: Add a specific sub-metric under the “Innovation & Technical Excellence” or “Cost Control” category:
. “Demonstrated reduction in sustainment costs through predictive analytics or AI-driven maintenance (measured by predicted vs. actual failure rates and O&M savings).” This would directly incentivize the innovative solutions the program seeks and align with the stated goal of “reducing operations and maintenance costs through hybrid architectures and automation.”
Our FracAdapt dashboard already provides real-time fleet health, terrain intelligence, and component wear forecasts — exactly the type of innovation that could earn award fee under this
| metric. | The Government will consider this recommendation, but will unlikely be incorporated. | ||||
| Award Fee Plan | 3.2 | Section 3.2: Recommend the 90-day transition be an independent award fee period. | The transition period will not be part of an award fee period because it happens prior to the start of the contract, and will be Firm Fixed Price | ||
| Award Fee Plan | Given the nature of the work will the Government allow offerors to propose an award fee over 8%? | Yes, the initial limit of 8% fee will be revised. Expect a maximum fee limited to between 10-12%, which will be proposed by the bidder. | |||
| Award Fee Plan | Annex 1: Award Fee Review Board | ||||
| Fee Determining Official: If delegated: Director, Innovation and Prototyping Delta | If the FDO is not delegated, who will be the FDO? | FDO is delegated to the director for Innovation and Prototyping Delate. | |||
| Award Fee Plan | Annex 2: Award Fee Evaluation Criteria | ||||
| 5: Excellent: Ensure all key positions are filled with qualified and cleared personnel and do not remain vacant or filled with other than a qualified or cleared person no more than 5 business days (interim filling of key positions acceptable as long as permanently fill is in place within 30 days). | Will delays on the Government part to grant TS/SCI and SAP read-ins count against the contractor? | The bidders should be ready to begin execution on day one. However, it is possible that there may be some delays due to read ins or clearances, and will need to be handled on a case-by-case basis. If beginning execution requires a delay while clearances are sought and approved (potentially a year-long process), this would be detrimental to the organization. | |||
| Award Fee Plan | Award Fee Period | Industry requests the 90 day transition be its own award fee period. | There will be no award fee period during the transition period. | ||
| Award Fee Plan | Note 1 in Annex 2 states "Any contractor effort rated “Unsatisfactory” in a particular area shall receive zero award- fee dollars ($0) for that area. In addition, if the Contractor’s overall performance is rated “Unsatisfactory,” the Contractor shall receive zero award-fee dollars ($0) for the award- fee period." | Suggest this be included in language in the main body (e.g. section 3.5) | The Government has reviewed industry's recommendation to relocate the award fee consequence language from Annex 2, Note 1 (page 14 of the Award Fee Plan) to Section 3.5 (Award-Fee Ratings). The Government will not make this change | ||
| Award Fee Plan | 3.1.2 | 3.1.2 states, "The GPM will ensure that the Recorder collects these inputs, prepares a consolidated briefing to the AFRB, re-distributes the briefing to the Area Leads for review, and makes any necessary edits. Next, the GPM and Area Leads conduct the briefing to the AFRB, and the AFRB evaluates the Contractor’s performance and provides the award-fee recommendation to the FDO" | Recommend to add that the Offeror be provided a draft of the evaluation and be provided an opportunity to provide a written rebuttal that is included in the briefing to the FDO before the FDO makes a final determination on the award fee. | The Government will not modify Section 3.1.2 to include a contractor rebuttal process prior to FDO determination. |
It is expected that issues leading up to the award fee board are identified and discussed between the Government team and contractor team and resolved if possible. The contractor will still have an opportunity during the award fee board to present for 30 minutes.
Award Fee Plan 3.8 In an effort to further incentivize contractor performance, will the Government please consider modifying the Award Fee Plan to include the opportunity and ability, at the Government's discretion, to disposition unearned award fee to special emphasis areas or subsequent award fee evaluation periods?
With other U.S. Government customers, we have seen successful implementation of dispositioning and repurposing unearned award fee. Sample Disposition of Unearned Award Fee language from other current U.S. Government award fee plans states" Redistribution of unearned award fee shall remain a unilateral decision of the FDO. At the discretion of the FDO, all or any portion of the unearned award fee may be (1) de-obligated and removed from further consideration of payment under the terms of the contract and this fee plan, thereby reducing contract value; or (2) be reserved for future application to special milestone incentive(s) related to exceeding overall contract performance objectives following contract completion. Any fee available for earning in this manner may not be provisionally billed and must be funded from then current appropriations at the time of final determination. The adjudication for any special emphasis milestone(s) shall be accomplished concurrently with the determination for the final award fee period. Under no circumstances can the contractor be allowed to earn total fees greater than the negotiated contract maximum fee. Any unearned award fee that has not been otherwise allocated to special emphasis milestone incentives per the terms of this paragraph at the end of the final award fee period shall be de-obligated and removed from the terms of the contract."
| The Government has carefully reviewed industry's recommendation to include provisions for redistribution of unearned award fee to special emphasis areas or subsequent evaluation periods. The Government will not incorporate this provision into the HADES Award Fee Plan | ||
| Award Fee Plan | Annex 2 | Annex 2 of the Award Fee Plan it states "If the Contractor or subcontractor is responsible for a security violation and is determined significant by the FDO, the award fee may be reduced up to 100% of the earned award fee for the evaluation period in which the action occurred." |
Would the Government please consider rolling up security evaluation criteria under Area A: Management, as well as remove the language "may be reduced up to 100% of the earned award fee" and replace with more constructive language (i.e. sample language below)? This not only incentives Contractors to ensure security awareness and compliance is at attention at all times, but gives Contractors an opportunity to improve and emphasis security performance during execution.
Sample language: Demonstrated compliance with all security requirements as identified in the DD254. Proactively fosters awareness at all levels to ensure no security violations. Ensures strict adherence to security procedures and requirements. *You can then establish evaluation thresholds on compliance to determine each grade (i.e. Excellent, Very Good, etc.). The Government has carefully reviewed industry's recommendation regarding security violation consequences in Annex 2 of the Award Fee Plan.
The Government will not make the requested changes Award Fee Plan 3.1.2 Section 3.1.2: We request to add that the offeror be provided a draft of the evaluation and be provided an opportunity to provide a written rebuttal that is included in the briefing to the FDO before the FDO makes a final determination on the award fee. The Government will not modify Section 3.1.2 to include a contractor rebuttal process prior to FDO determination.
It is expected that issues leading up to the award fee board are identified and discussed between the Government team and contractor team and resolved if possible. The contractor will still have an opportunity during the award fee board to present for 30 minutes.
| Award Fee Plan | 3.8 | Section 3.8: We request 60 minutes to brief the AFRB. | The Government has established a 30-minute time limit for the Contractor's presentation to the AFRB as outlined in Section 3.8 of the Award Fee Plan. This timeframe is designed to allow the Contractor to present their self-assessment efficiently while ensuring adequate time for the AFRB's evaluation, deliberation, and FDO briefing within the overall timeline requirements. |
| Award Fee Plan | 4 | Section 4.0: Clarification: If adjustments to the Award Fee Plan are recommended when the AFRB meets, please confirm that those changes will be interpreted to be within the 15-day criteria and will require bilateral agreement. | The Government confirms that Award Fee Plan changes recommended by the AFRB are subject to the timing-based procedures specified in Section 4.0. The source of the recommended change does not alter these procedures. |
Section 4.0 of the AFP establishes the following:
Unilateral Incorporation: If the PCO provides written notification to the Contractor at least 15 calendar days before the start of a new evaluation period, changes will be incorporated unilaterally for the upcoming period.
Bilateral Agreement Required: Changes made within 15 days of a new evaluation period or changes affecting a current evaluation period must be made by bilateral agreement.
Award Fee Plan Annex 2 Annex 2 Areas A and C: We request relative weighting for the multiple scoring criteria. For example, if small business utilization drops below 25% for any given period, does that make the entire Area C Management score a 0% even if the other 4 areas are better? Or are they evenly weighted where each of the 5 bulleted criteria are really worth up to 4%? The evaluation criteria within each area in Annex 2 are not independently weighted or scored. The Award Fee Plan uses a holistic evaluation approach where the AFRB assesses overall contractor performance within each area by considering all applicable criteria collectively.
The Government does not:
Assign point values or percentages to individual criteria Score each criterion separately and calculate an average Apply mechanical formulas where failure in one criterion automatically determines the area rating
The Government does:
Consider all criteria within an area collectively Assess the relative impact and significance of performance in each criterion Assign a single overall rating (Excellent, Very Good, Good, Satisfactory, or Unsatisfactory) for each area based on totality of performance Exercise judgment based on mission impact and the specific circumstances Regarding the specific example: If small business utilization drops below 25%, this does not automatically result in 0% for Area A: Management. The AFRB will consider the severity, reasons, contractor efforts, performance in other management criteria, and overall mission impact. Strong performance in other management areas may offset weaknesses in small business utilization, and vice versa.
| Award Fee Plan | Annex 2 | Annex 2 Area A: In order to achieve a score of Excellent, small business utilization of 34% or more is required. Since a downgrade from Excellent is a penalty, this makes the Small business utilization minimum 34%, not 25%. Request either change the small business requirement for the entire contract to 34% or remove the requirement to exceed 25% for an Excellent rating. | Ratings for small business utilization will be updated to unsatisfactory less than 25% and excellent 25% or more with no ratings in-between. Changing the criteria to succeeding or not succeeding. |
| Award Fee Plan | Annex 2 | Annex 2 Area C: The award fee plan currently evaluates the cost on a monthly basis. Since cost type contracts naturally fluctuate per month, it creates a higher risk of not meeting the cost control goals since they are evaluating our cost management on "any monthly report." Monthly reporting is timing and not reflective of true performance. Feedback: Since cost type contracts naturally fluctuate on a monthly basis, recommend updating the evaluation on any monthly report to cumulative reporting to reflect an accurate representation of the contractor's cost control performance. | The Government will not change the monthly reporting basis in Area C. |
The monthly threshold enables early identification of cost issues while the holistic evaluation approach considers the totality of performance over the six-month period. The AFRB will consider legitimate reasons for monthly fluctuations (invoice timing, material deliveries, scheduled activities) and contractor explanations provided during monthly surveillance meetings.
The evaluation focuses on cost management and forecasting accuracy, not simply whether costs fluctuate. Contractors who maintain accurate forecasts and communicate proactively will demonstrate effective cost control even with normal monthly variations. The 10% over / 20% under thresholds provide significant tolerance for cost-type contract fluctuations.
Award Fee Plan Annex 2 Annex 2 Area C: The excellent scoring seems contradictory. For excellent, offeror will be penalized for an under run by 10% but the government wants more than 10% cost savings. There should be clarity on which cost baseline the variance is being evaluated on so that the offeror doesn’t get penalized on government approved efficiencies, scope adjustment, process improvements, etc. Feedback: Recommend rewrite to say “Excellent: Accurately execute cost type task orders with no task orders above the task order cumulative cost and no task orders below 10% of task order’s cumulative cost on any during the evaluation period except as indicated in the criteria below. Proactively recommend changes to achieve cost savings of greater than 10% relative to the original baseline with associated rational and shall not be considered negative variance.” The Government appreciates industry's feedback but will not revise Area C evaluation criteria.
The Government's Position:
Cost estimation accuracy is a fundamental requirement for effective contract management. The evaluation criteria appropriately balance two objectives:
Accurate execution to negotiated estimates (demonstrates sound cost forecasting) Proactive value engineering during performance (demonstrates continuous improvement) These objectives are complementary. The Government expects contractors to:
Propose accurate, realistic cost estimates that reflect planned efficiencies and process improvements Identify additional cost-saving opportunities during execution and recommend them with supporting analysis Addressing the "penalty" concern: Significant underruns reflect estimation inaccuracy, not superior performance. Overestimation creates the same planning and budgeting challenges for the Government as underestimation. The criteria incentivize contractors to develop rigorous cost estimating processes and propose realistic, well-supported cost estimates.
The baseline for variance evaluation is the negotiated task order cost as modified by any bilateral contract changes.
| Award Fee Plan | Annex 2 | Pricing - Award Fee - Annex 2 Area A: In order to achieve a score of Excellent, small business utilization of 34% or more is required. Since a downgrade from Excellent is a penalty, this makes the Small business utilization minimum 34%, not 25%. Request either change the small business requirement for the entire contract to 34% or remove the requirement to exceed 25% for an Excellent rating. | Request feedback regarding appropriateness, adequacy, and sufficiency on documents currently provided in the draft RFP. Please note that on this initial Draft RFP there are some documents missing such as the complete CDRL list, and the Government intends to add to the draft RFP and make changes throughout the comment period in response to feedback. | Ratings for small business utilization will be updated to unsatisfactory less than 25% and excellent 25% or more with no ratings in between. Changing the criteria to succeeding or not succeeding. | |
| Award Fee Plan | 3.3.1 | In Award Fee Plan Section 3.3.1, the Government states that for each task order, at least 40 percent of the available award fee must be assigned to the last award-fee event, and that exit criteria will be established for each award-fee event. Will the Government please clarify whether the final award-fee event is expected to be tied primarily to task completion, acceptance of final deliverables, sustained operational performance, or another exit criterion established at task-order award? | The exit criteria for the final award-fee event will be defined at task order award and will vary based on each task order's specific requirements and objectives. |
The final event may be tied to task completion, deliverable acceptance, sustained operational performance, transition activities, or a combination thereof, depending on the nature of the work.
All award-fee event exit criteria, including the final event, will be clearly specified in the individual task order to ensure objective, measurable performance assessment.
Consistent with Class Deviation—Revolutionary Federal Acquisition Regulation (FAR) Overhaul Part 16, Defense FAR Supplement (DFARS) Part 216: 216.402-4, at least 40 percent of the available award fee will be assigned to the final award-fee event for each task order.
Award Fee Plan 5.1 In Award Fee Plan Section 5.1, Termination for Default, the plan states that Award fee earned or earnable for completed periods prior to termination will not be affected, unless other provisions of the contract and/or award-fee plan (e.g., negative incentive) require payback of previously earned fee. Will the Government please clarify under what circumstances previously paid or previously earned award fee may be subject to payback, and whether such payback would be limited to the evaluation period in which the triggering event occurred or could extend to prior evaluation periods? Award-fee earned or earnable by the Contractor for award-fee evaluation periods completed prior to the effective date of a termination for default will not be affected by the termination.
This Award Fee Plan does not contain negative incentive or fee payback provisions.
Award Fee Plan 3.1 Annex 3 Includes 3.3.1 In Section L 5.3.1, the solicitation states that each Task Order will define its own award-fee events and corresponding award-fee pool allocations, while Government award-fee evaluations will occur at the IDIQ level in accordance with the Award Fee Plan. In AF Plan Sections 3.1 and 3.3.1, the plan further states that task-order-specific award-fee pools are established at task order award and allocated to award-fee events, and Annex 3 illustrates a single evaluation period containing completed events from multiple task orders. Will the Government please clarify how IDIQ-level award-fee evaluations will be applied when multiple task orders contribute award-fee events within the same evaluation period, including whether earned fee is assessed holistically across all completed TO events in that period or remains attributable only to the specific TO events completed? Needs government input.
Award-fee evaluations are conducted at the IDIQ level across all active task orders, not separately by task order.
At the end of each evaluation period, the available award-fee pools for all completed award-fee events from all task orders are summed to create the total available pool for that period (Award Fee Plan Section 3.3.2). The Award-Fee Review Board evaluates contractor performance holistically across all task orders using the criteria in Award Fee Plan Annex 2 (Management, Quality of Technical Services, Cost Control), resulting in a single adjectival rating and award-fee percentage for the period (Award Fee Plan Section 3.5). This percentage is applied to the total available pool, producing one award-fee dollar amount for the evaluation period.
Earned fee is assessed holistically across all completed task order events in the evaluation period. Performance on all active task orders contributes to the single IDIQ-level rating. Strong performance on one task order cannot compensate for poor performance on another. An overall Unsatisfactory rating results in zero award fee for the entire period, regardless of which task order(s) contributed to that rating (Award Fee Plan Annex 2, Note 1).
The Government will incorporate clarifying language into Section L , Section M, and the Award Fee Plan to enhance understanding of the cross-task-order evaluation process.
Award Fee Plan ● Some adjectival rating descriptions remain somewhat subjective. Award fee determinations involve professional judgment as authorized by RFO 16.405-2. The Award Fee Plan Annex 2 provides specific, measurable numeric criteria for the substantial majority of evaluation elements. The limited subjective elements are necessary to assess performance aspects that cannot be reduced to purely numeric metrics.
If the offeror has specific concerns about particular evaluation criteria, the Government requests those be identified with proposed alternative language for consideration.
No changes are planned.
Award Fee Plan ● Recommendation for Flexibility: Add language allowing the Fee Determining Official to adjust evaluation criteria mid-period (with 30-day notice) if new opportunities or risks emerge or mission priorities change. The Government will not adopt mid-period changes to award fee evaluation criteria.
Changing evaluation criteria mid-period would undermine fairness and predictability by evaluating contractors against standards that did not exist when work was performed. Award Fee Plan Section 4.0 provides appropriate flexibility by allowing criteria changes before new evaluation periods begin, with required FDO approval and advance notice.
Emerging opportunities and mission priorities are appropriately addressed through new task orders with separately defined award fee criteria, and through monthly surveillance meetings that provide ongoing performance feedback.
No changes will be made.
| Award Fee Plan | ● Alternatives to Cost-Plus-Award-Fee (CPAF): Consider a hybrid Fixed-Price Incentive (FPI) for well-defined sustainment tasks combined with CPAF only for developmental/prototype elements, or Cost-Plus-Incentive-Fee (CPIF) with objective performance metrics. These alternatives reduce administrative burden, lower the Government’s risk exposure to subjective fee determinations, and incentivize cost control more effectively. | The Government has determined that Cost-Plus-Award-Fee (CPAF) is the appropriate contract type for this acquisition and will not adopt alternative contract types or hybrid approaches. | |
| B | Section B – Supplies or Services & Prices or Costs | Will the Government confirm that CLIN X002 Award Fee should contain the Award Fee for cost-plus CLINS X001 and X005? | Yes. CLIN X002 (Basic Award Fee Management) contains the award fee pool for CLINs X001 (Mission Support) and X005 (Special Studies/Concept Exploration). |
Per Section L and Section M, offerors shall propose award fee percentages for CLINs X001 and X005. These percentages are applied to direct labor and associated indirect costs to calculate the available award fee pool cited in CLIN X002 on each task order.
Award fee is earned based on performance evaluated per the Award Fee Plan (Section J, Attachment 3) and paid through CLIN X002.
Bidder's Library Will the Government reconsider providing either a classified bidders' library or a sanitized, and unclassified, version that allows for all bidders to have a fair and equitable understanding of the ground system as a whole?
The Government will not establish a classified bidders' library or provide sanitized system documentation beyond what is included in the solicitation.
The Performance Work Statements (Section J, Attachments 1-4), Government Furnished Property List (Section J, Attachment 7), and other solicitation attachments provide sufficient information for proposal preparation. [If applicable: A site visit will be conducted on [date] to allow observation of the facility and operational environment.]
Offerors shall demonstrate their technical capability and understanding through relevant past performance and proposed technical approaches that address the requirements specified in the solicitation.
CDRLs A017 Block 16, paragraph 6, also includes A001 and L 4.3.1.3 In CDRL A017, the Government states that within 60 days of contract award it will meet with the Contractor to develop an Integrated Master Schedule (IMS) for audit prioritization, while CDRL A001 requires a PMO Approach and Section L 4.3.1.3 evaluates the Offeror’s management process for addressing emerging requirements across multiple TOs. Will the Government please clarify whether the contractor is expected to maintain a single enterprise IMS spanning all active TOs and emerging work, or whether separate TO-level schedules with PMO roll-up are acceptable? The Government requires an Integrated Master Schedule (IMS) structure consisting of:
Task Order IMS's: Each Task Order (Ground Control, JAGUAR, Ground Support, and future TOs) shall have a separate detailed IMS showing task-level schedules, dependencies, milestones, and resources.
Master IMS: A contract-level Master IMS that consolidates and rolls up all Task Order IMS's to provide organizational-level visibility across the entire HADES contract.
The Master IMS shall reflect schedule issues, critical path activities, resource conflicts, and cross-TO dependencies identified from the Task Order roll-ups. Both the Master IMS and individual Task Order IMS's shall be maintained and updated throughout contract performance
| CDRLs | A011 | Please confirm that CDRL A011 should have EVMS removed as a requirement from Block 3? | Yes - EVMS is to be removed. | ||
| CDRLs | A017 | In reference to CDRL A017, does the “annual completion date NLT 15 June” requirement apply to this IDIQ contract or at the Task Order level? | |||
| This date will be updated after award, for now the 15 June date is notional and was based on a estimated award date, and based on block 12 for delivery of 45 days after award. | |||||
| CDRLs | Reference in Section B data CLINs and PWS, but not yet provided | Drives recurring/non-recurring reporting, documentation, and review workload for each TO; without CDRLs, offerors must either assume scope or price conservatively. | |||
| Provide a draft CDRL package showing data items, frequency, distribution, classification, and mapping to Basic and TO PWS paragraphs. | Draft CDRL list was released on 9 March with the updated RFP. | ||||
| CDRLs | Includes all CDRLs Block 12 and 13 | As currently written, stated durations in Blocks 12 and 13 on all pages fluctuate between “Business” and “Calendar” days. Will the Government please consider specifying all durations in Business days? This will eliminate due dates falling on weekends and holidays. | The Government will consider this recommendation, but will unlikely be incorporated. | ||
| CDRLs | A008 | Blocks 12,13,16 | A008 is titled “Physical Inventory Report” but in Block 16 it is referred to as the CFO Report. Will the Government please clarify whether this is a Physical Inventory Report or CFO Report? | A008 is the Physical Inventory Report. | |
| CDRLs | A026 | Block 16 | A026 is titled “Risk Management Framework (RMF) Packages but Block 16 refers to A027. Will the Government please clarify? | This is an error, and has been corrected. | |
| Data Rights | The (Company name withheld) recommends that the final HADES solicitation place greater emphasis on clearly defined Government data rights and intellectual property ownership to ensure long-term flexibility, competition, and mission continuity. In complex development and sustainment environments, there is inherent risk that portions of a system may be delivered with restricted, limited, or otherwise constrained rights if developed through a mix of contractor-funded research and development and Government-funded efforts. This can create unintended vendor lock, reduce the Government’s ability to compete for future work, and limit long-term flexibility in sustaining or evolving mission systems. |
To reduce this risk, the Government should consider reinforcing expectations that Government-funded development results in Government Purpose Rights or Unlimited Rights for core mission systems, technical baselines, architectures, interfaces, and code necessary to operate, maintain, enhance, and recompete the effort in the future. Proprietary tools may still be appropriate where clearly identified and segregated, but they should not constrain the Government’s ability to sustain or transition critical capabilities. This approach aligns with(Company Name withheld)s delivery philosophy. When we develop solutions on behalf of the Government, we do so with the understanding that the mission must continue beyond any single contractor. Our model emphasizes transparent, scalable, and supportable solutions that allow the Government to retain ownership of the capabilities it funds and to adapt those capabilities over time without unnecessary dependency. "The Government expects that all technical data and computer software developed with Government funds or mixed funding under the HADES contract will be delivered with Government Purpose Rights or Unlimited Rights in accordance with DFARS 252.227-7013 and DFARS 252.227-7014. This includes system architectures, interface specifications, source code, integration scripts, and all technical data necessary to operate, maintain, sustain, and compete future requirements.
Offerors may assert Limited Rights or Restricted Rights only for items developed exclusively at private expense. All assertions must be clearly identified in the proposal with supporting rationale. The Government will evaluate whether such assertions create unacceptable vendor lock-in or restrict future competition.
Standard FAR commercial rights provisions apply to unmodified commercial items. Contractors may use proprietary development tools provided they do not restrict Government rights in Government-funded deliverables.
The contract will include standard DFARS data rights clauses (DFARS 252.227-7013 and 252.227-7014). Offerors should review these clauses carefully when preparing proposals."
| Data Rights | Referenced in Section M for TEP calculation but not yet provided. | |
| Data Rights expectations influence software/IP strategy, use of COTS vs. custom, and licensing cost; lack of visibility increases pricing and negotiation risk. | ||
| Provide a draft Attachment 9 with the desired rights categories and pricing template so offerors can align technical and licensing approaches. | The Government will include data rights requirements and guidance with the RFP. |
The Government acknowledges this concern and agrees that early visibility into data rights requirements is essential for accurate pricing and appropriate technical approach development.
Section J, Attachment 9 (Data Rights Assertions and Pricing) will be included in the final RFP and will provide:
1.) A structured data rights assertion template 2.) Clear definitions of rights categories (Unlimited Rights, Government Purpose Rights, Limited Rights, Restricted Rights, commercial licenses) 3.) A pricing template for data rights and commercial licenses Explanation of how data rights costs factor into Total Evaluated Price (TEP) calculation
Regardless of the specific template format, offerors should plan their approaches based on the following principles:
1.) All Government-funded development should result in Government Purpose Rights or Unlimited Rights deliverables 2.) Commercial software licenses should be clearly identified with transparent pricing 3.) Assertions of restricted rights should be limited to items developed exclusively at private expense 4.) Technical approaches should minimize dependencies on restricted-rights items for mission-critical functions"
| F | What is the anticipated contract award date and desired transition completion date? | Anticipated contract award date is Oct/Nov 2026, to provide for an adequate transition period, with contract performance start of 10 Feb 2027. These dates are subject to change based on source selection. | ||
| F | 52.216-18 | Ordering Period | Please confirm how offerors should apply the task order POP limitation to the initial sample task orders and any follow-on or option-period assumptions used for pricing and staffing. | It is expected the initial TO's will endure for the duration of the contract. They should be priced accordingly. |
| General | 52.216-18 | Ordering Period | Please confirm the final, controlling IDIQ ordering-period dates that offerors should use for proposal assumptions, pricing, and contract phasing. | Assume base ordering period of |
10 Feb 2027 -9 Feb 2030, Option 1 10 Feb 2030 - 9 Feb 2031, Option 2 10 Feb 2031 - 9 Feb 2032, Option 3 10 Feb 2032 - 9 Feb 2033, Option 4 10 Feb 2033 - 9 Feb 2034
Disclaimer: the above ordering periods are based on full contract perform start after a transition period currently set at 60 days.
General System How long do you keep data before archiving? Is there a timing requirement to decompress, retrieve and display archived data? "Data retention and retrieval requirements are mission-specific and will be defined in individual Task Order Performance Work Statements in accordance with Air Force and DoD records management policies.
Offerors should propose flexible data management solutions capable of supporting retention periods ranging from mission duration to indefinite retention. Archived data must remain accessible, retrievable, and displayable in usable format throughout the retention period. Specific performance requirements for data retrieval timing will be specified in each Task Order."
| General | System | Do you have enough storage for your current needs and if not, do you have the space and hardware for expanding that storage? | Depends on the mission as well as records retention requirements. |
| General | ● Technical Baseline Artifacts: Current-state architecture diagrams, interface descriptions, and baseline drawings for the RSC and Jaguar systems would assist offerors in developing accurate technical approaches. | Due to OPSEC concerns no Technical Baseline Artifacts will be released to bidders. Bidders should describe their technical approach based on the required need. | |
| General | System | What is the total amount of data downloaded from all programs every day? | Information to be provided to the successful bidder. |
| General | Past Performance | If the Government chooses to include past performance as an evaluation factor, we highly recommend the prime contractor must have at least one recent and relevant contract of similar magnitude at Kirtland AFB. Given the difficult nature of hiring and recruiting qualified staff, this would ensure the Government receives a low-risk prime who has proven experience hiring in ABQ. | "The Government will not require past performance at Kirtland AFB as a mandatory criterion. While the Government recognizes that local presence and experience in the Albuquerque market can be advantageous for workforce recruitment and retention, limiting past performance evaluation to a single geographic location would unnecessarily restrict competition. |
Offerors should address their recruitment and retention strategies for the Albuquerque/Kirtland AFB area in their technical proposals (Section L 4.3.1.3, Personnel Security Requirements). The Government will evaluate whether proposed approaches provide reasonable assurance of maintaining required staffing levels with qualified, cleared personnel.
Past performance contracts demonstrating successful workforce management in similar challenging recruitment environments (cleared personnel, specialized skill sets, competitive labor markets) will be considered during the relevancy assessment in Section M 6.4."
General System Performance Has the system met the availability requirement as originally specified? Are you allowed to give a percentage number? Most of the time. It is important to remember this is a single-string system. Every installation and/or corrective action brings the system down. There is a strong emphasis on return-to-service.
The Government cannot provide specific historical availability percentages, as this information can be sensitive in nature.
| General | Requirements | Do your requirements adhere to INCOSE (International Council of Systems Engineers) standards -> Necessary, Concise, Singular, Feasible, Verifiable, Testable, Measurable, Technology Independent, Consistent, Complete, Identifiable | The HADES Contract does not mandate strict adherence to INCOSE standards. The Government expects requirements to follow sound systems engineering principles. |
| General | Verification | Does the government customer have a VCRM (Verification Cross Reference matrix) that includes all requirements verified by Inspection Analysis Demonstration and Test? In addition, have those line items been mapped to verification artifacts and test reports. | There are processes followed similar to those stated. Due to the R&D nature of the mission, Strict adherence to these formal processes is not practical. |
| General | System Performance | Does the government customer have a list of requirements or specifications that are no longer met by the existing system? | No, the system evolves continuously based on mission requirements. |
| General | RF Antennas | Do offerors have to provide support to RF antennas and modems? | No - except as identified below: |
The organization primarily uses the Satellite Control Network (SCN). We have used (and will again) used the Swedish Space Network. We have used both NISN and TDRSS. Mission specific antenna come and go (depending on the mission). With the loss of the MRF, there is no expectation of the HADES contractor being responsible for physical maintenance of antennas. For at least one mission, the HADES contractor will be responsible for serving as a help desk for antennas (local and remote) as they connect to and work with the mission.
General Test Does the government customer have a formal test template that directed any incumbents on the system to write in a consistent test case format that included Test Case ID, Test Case Title, Entry and Exit Criteria, calibration of test equipment at the time of test, Step by step user procedures, summary of results, pass/fail criteria? The Government does not have a mandatory test template or standardized test case format. Test documentation requirements are specified in the Contract Data Requirements List (CDRL) at Section J, Attachment 8, and in the applicable Performance Work Statement requirements.
Offerors shall propose test approaches and documentation formats that meet all CDRL and PWS requirements. The Government will evaluate proposed approaches for adequacy and completeness during source selection
| General | Verification | Does the government customer have verification plans (Not test plans or test cases) that tell the story of how each requirement is verified. If so, at what levels? (System or lower level) | No - these plans are generated by the engineering contractor (e.g. HADES) and submitted for approval. |
| General | System | Will the offeror be responsible for maintenance of any HW or SW at a backup facility? If not, does the offeror have to support the backup facility team in any way? | No and no |
| General | Software Performance | Have you identified any impairments/bottlenecks in Software Performance that is due to Software? | None identified, several suspected. |
| General | Hardware Performance | Have you identified any impairments/bottlenecks in hardware Performance that is due to hardware? | None identified, several suspected. Likely room for configuration improvement. |
| General | Network Performance | Have you identified any network latency, network data congestion issues with the existing system. | None identified, some suspected. |
| General | System | Does the Government have a list of all Liens, Waivers, and Deviations? | Not at the present time. |
| General | System | Has the government Customer estimated the cost for any existing Liens and what are the due dates to resolve the liens? | Not at the present time. |
| General | Hardware | If the existing facility is not EMP protected, do you have at least one replacement item for every part/component/computer card/etc.? | Not at this time. |
| General | Past performance Evaluation Criteria - Section M notes that more information will be provided in a latest draft. | Offerors cannot fully shape past performance volumes or teaming to maximize relevancy without size, scope, recency, and weighting guidance. |
Provide draft Past Performance factor/subfactor language, including relevancy definitions and how CPARS vs. questionnaires will be used. Comprehensive Past Performance evaluation criteria were released in the second draft RFP on 9 March 2026 and are available in Section L (paragraphs 6.1-6.6) and Section M (paragraphs 6.1-6.6).
Key Elements Provided:
Relevancy definitions with detailed scoring criteria (Section M, Table 6.2 and 6.2-S1) Quality assessment ratings (Section M, Table 6.3) Recency: 5 years from RFP release (Section M 6.3) Contract limits: Prime = 5 max, Major subs = 3 max (Section L 6.3.1) Questionnaire and CPARS integration approach (Section L 6.6, Section M 6.2) Confidence assessment methodology (Section M 6.6)
The final RFP will include minor clarifications but no material changes from the 9 March 2026 version. Offerors should use the current criteria for proposal preparation and teaming decisions.
| General | Staff | What is the total number of personnel needed by the existing incumbent to perform the mission? | Staffing plan provided are estimates. Alternative staffing levels are anticipated. The expectation is that bidders will demonstrate an understanding of what needs to be done and have an efficient strategy for executing against that requirement. |
| General | Hardware | Please provide a list of all model number ID's and web links for ordering for parts/components/computer cards/ in case these items have to be replaced in the future. Your existing incumbent should have this. | The existing incumbent does have this. It will be provided to the awardee during transition. |
| General | Hardware | Please provide a quantity accounting of all parts/components/computer cards/ you are currently using and how many backup items you have in storage. Your existing incumbent should have this. | The existing incumbent does have this. It will be provided to the awardee during transition. |
| General | Is there a file size limitation for electronic proposal submission, and should Offerors submit documents in Word, PDF, or both formats? | The file size limitation reflect the current page limits. Submissions will be in PDF format, with the exception of pricing information and rates where Excel is more appropriate. | |
| General | Configuration management | Does the Government have configuration management applications to maintain revisions of documents, software and requirements? | The Government does not at this time. |
| General | Staffing | What kind of staffing do you expect for a 24/7 maintenance and operations? Please provide staffing expectation from 8am to 5pm, 5pm to 1am, 1am to 8am. | The government expects the availability requirements to be met. As a successful bidder - with an appropriate technology enabled strategy - the bidders are expected to be able to staff appropriately, although most staffing will be 8AM-5PM M-F, with on call and after hours assistance as required. |
| General | Staff | What is the total number of personnel needed by the government customer (minus the incumbent) to perform the mission? | The government is unsure of what the question is referencing or seeking information on. The questions presumably is asking for the total number of Government (Civilian and Military) which should not have a bearing on the number of personnel proposed by the bidder to accomplish the scope of work in the contract. |
| General | Software | What software code if any, is an incoming contractor expected to inherit and what are the software languages utilized? | The incoming contractor inherits the responsibility for all of the existing software. This does not imply that they "own" any of it. Software languages include (and may not be limited to) C, C#, C++, JAVA, assorted shell languages (for both UNIX and Windows). |
| General | RF Antennas | How many Operational antennas, Dish or otherwise do you use? How many are active and how many redundant? Are the antenna’s at different geographical locations? | The organization primarily uses the Satellite Control Network (SCN). We have used (and will again) used the Swedish Space Network. We have used both NISN and TDRSS. Mission specific antenna come and go (depending on the mission). With the loss of the MRF, there is no expectation of the HADES contractor being responsible for physical maintenance of antennas. For at least one mission, the HADES contractor will be responsible for serving as a help desk for antennas (local and remote) as they connect to and work with the mission. |
| General | Operational Users | How many operational users utilize the existing system | There are currently roughly (goes up and down) eight missions operating in various configurations. |
| General | Software Licensing | Does the government customer have the ability/authority to provide a list of all software licenses, expiration and last known cost? | This information will be provided after award during the transition |
| General | Hardware | Please list all the certifications necessary for the program (NSA cryptography, Cyber Security, etc.) and when they need to be renewed | This information will be provided to the awardee at transition. |
| General | Verification | Has the Government customer mapped requirements that are verified by Demonstration and Test to test cases in a VTM (Verification Test Matrix? | This is a task reserved to the engineering contractor (HADES) and reviewed/approved by the government customer. |
| General | IDIQ Structure/Future Task Orders | If additional Task Orders are anticipated, can the Government provide insight into the expected sequencing and potential scope expansion of those future Task Orders? | Unknown, dependent on the number of accepted missions and the available funding. |
| General | Information Assurance and Cyber Security | Does the system currently meet all Department of War and NSA information assurance, Cryptographic and cyber security standards? | Yes |
| General | Hardware | Is the facility for this contract EMP protected? | Yes |
| General | Aside from PPQ submissions via DoD SAFE, will the Government will the Government consider DoD SAFE for proposal submission to account for file sizes and security? | DoD safe can be used for past performance, but proposal submission will be through PIEE. Instruction will be updated in section L. | |
| General | IDIQ Structure/Future Task Orders | Will the Government please clarify whether additional Task Orders are anticipated beyond the three evaluated in this solicitation? | Yes, please reference notional schedule for anticipated future task orders. There may be additional task orders, but they are not known at this time. |
| General | Will the Government release the page count for the Past Performance citations and volume, in total, before the Final RFP is released? | Yes, updated Past Performance volume will be included with this Q&A release. | |
| General | Resilience | Beyond the JAGUAR TO scope, does the existing system have a resilience requirement and if so, have the requirements been decomposed into lower levels? What is the maximum down-time the system is allowed to experience? | Yes, to the first question and. No. . The maximum downtime is set (by the requirement owner) to be four hours. We re-iterate - this is a single-string system. |
| General | Process Certifications | What CMMI (Capability Maturity Model Integration) level has the current system been certified for? When was the last audit? When is the next audit due? | The HADES solicitation does not require CMMI certification, at this time. The contract scope is primarily operations, sustainment, and integration rather than large-scale software development, and CMMI certification is not aligned with the nature of this work. |
Offerors shall demonstrate organizational capability and process maturity through:
| • | Government-approved business systems: Accounting, Estimating, and Purchasing Systems (Section L 5.5.1) |
| • | Quality Control Plan with documented procedures for defect prevention and corrective action (PWS 2.2.5) |
| • | Configuration Management processes and tools (PWS 2.2.8, Section M 4.3.2.2) |
| • | Systems Engineering methodology addressing the full lifecycle (Section M 4.3.2.1) |
| • | Program Management approach (Section M 4.3.1) |
| • | Past Performance on similar operations, sustainment, and integration contracts (Section M 6.0) |
These requirements collectively ensure contractors have appropriate process discipline and organizational capability without requiring CMMI certification, which is designed primarily for software development organizations."
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 .