In This Week’s Newsletter:
- Opportunity Spotlight of the Week: DAF TETRAS III
- Four To Follow: Four Interesting Pursuits
- Capture Corner: Product End of Life (EOL) & Capture Impact
- Pricing Insights: Why You Need a Written Estimating Manual
Opportunity Alert – DAF TETRAS III
Contact Katie: katie.clatterbuck@hinzconsulting.com
Department of the Air Force, Air Force Materiel Command, Air Force Test Center, Test and Evaluation Technologies for Ranges, Armaments and Spectrum III (TETRAS III).
The Air Force Test Center’s 96th Test Wing at Eglin Air Force Base has a continued need to support major test facilities and simulators across the Department of War for testing weapon systems, command, control, communications, computers, cyber-defense, combat systems, intelligence, surveillance, and reconnaissance, and electronic combat systems and components, spanning environmental and climatic behaviors, vulnerabilities, performance, warhead characterization, and data distribution. The primary objective is to give the 96th Range Group and other Defense organizations the ability to rapidly develop and modify test systems and facilities for fifth and sixth generation weapons and cyber systems, with the surge capacity to meet requirements that cannot move through the traditional acquisition lifecycle. The multiple-award IDIQ carries an estimated value of $20B over a five-year base and a five-year option period and will be competed on a full and open unrestricted basis. The final RFP is estimated for release in October 2026, with an award in June 2028.
Four to Follow
- Department of Defense, U.S. Special Operations Command (USSOCOM), SOF Enterprise Professional Services II (SEPS II). USSOCOM requires engineering management, program management covering research, development, test and evaluation support, special studies and operations research, management support including data collection, accounting and financial services and performance auditing, and administrative services. Work is performed primarily at USSOCOM headquarters at MacDill Air Force Base in Tampa, and reaches the four components, Joint Special Operations Command, and the Theater Special Operations Commands. The effort carries an estimated value of $250M and is estimated for release in September 2026 as a SDVOSB with an award in April 2027.
- Department of the Army, Army Contracting Command, Army Information Enterprise Information Technology Services (AIE-ITS). The Army is preparing AIE-ITS, which would consolidate the Army Intelligence Enterprise from nineteen legacy level-of-effort contracts into a single unified vehicle supporting the Army INSCOM. The scope covers managed IT services, global DevSecOps, multi-cloud architecture, data science, cybersecurity, and enterprise infrastructure supporting more than 14,000 active users and 26,000 classified devices across more than 680 global locations. The final $3.8B solicitation is estimated for release in September 2026, with an award in March 2027.
- Department of Justice (DOJ), Data Analytics Solution and Services (DASS). DOJ requires a solution to support criminal and civil investigations. This solution must analyze large volumes of structures and unstructured data, identify relationships among people, entities, and transactions, and support investigative and litigation needs. The final solicitation for this $500M Full and Open/Unrestricted opportunity is estimated for release in December 2028 via GSA MAS with an award in September 2029.
- Department of Treasury, Internal Revenue Services (IRS), Long Term Integration Support 4 (LTIS 4). IRS has need for a contractor to assist in implementing a single integrated environment for managing individual taxpayer accounts, improving digital services, security, and data accuracy. The work includes tasks such as transition support, program and project management, architecture and engineering, solution engineering, testing, development integration and business tools support. This $390M SDB Set-Aside is estimated for release via GSA MAS around September 2026 with a potential award date in December 2026.
Product End of Life (EOL) & Capture Impact
Contact John: john.amoriello@hinzconsulting.com
When a core product in your solution reaches End of Life (EOL)during a capture, it introduces critical risks to your proposal’s viability, compliance, and profitability—but it can also present a strategic advantage if managed proactively.
Direct Impacts on the Capture:
1. Solution & Compliance Risk
- RFP Non-Compliance: If the RFP requires supported, active hardware/software throughout the contract lifecycle, offering an EOL product can lead to immediate disqualification or low technical scoring.
- Architecture Redesign:Engineering and solution teams must scramble to identify, validate, and integrate an active replacement product late in the capture cycle, delaying proposal drafting.
- SLA & Warranty Failures:Original Equipment Manufacturers (OEMs) stop issuing software patches, security updates, and replacement parts post-EOL, making it impossible to meet client Service Level Agreements (SLAs).
2. Commercial & Cost Disturbances
- Pricing Volatility:Replacement products rarely cost the exact same amount. Switching products can force significant adjustments to your Bill of Materials (BOM), altering your Price-to-Win (PTW) target.
- Margin Compression:Transitioning to a newer product line might require unforeseen integration, training, or certification costs for delivery personnel, eating into deal margins.
- Extended Support Premiums: If forced to maintain the EOL product temporarily, custom or extended OEM support fees can dramatically inflate operational costs.
3. Customer & Competitive Positioning
- Evaluation: Evaluators closely inspect lifecycle roadmaps. Presenting obsolete tech signals a lack of market awareness or a short-sighted technical solution.
If handled early in the capture cycle, a product EOL event can be leveraged to differentiate your proposal:
- Offer a Seamless Migration Roadmap:Frame the situation around lifecycle modernization. Detail a clear, risk-mitigated transition plan from the legacy tool to its next-generation successor.
- Lock in Preferred OEM Pricing: Engage the vendor immediately. OEMs often offer aggressive discounts or incentive pricing on replacement product lines to convert existing capture pipelines.
- Build Stronger Value Propositions: Highlight how the newer alternative improves performance, security compliance, energy efficiency, or total cost of ownership (TCO) compared to maintaining legacy tech.
- Competition: Competitors who recognize the product’s status will highlight the EOL status as a key weakness in their counter-messaging and “ghosting” strategies.
Why You Need a Written Estimating Manual
Contact Dr. Tom: thomas.hudgins@hinzconsulting.com
A written estimating system manual is one of the least glamorous and most protective documents a federal contractor can own. Having written policies and processes can be your best friend in difficult times!
Certain elements/processes addressed in an Estimating system can include:
- Discussions of actions for proposals of 30 and 10/7 day turn-around times
- Discussions of how indirect rates were estimated and how they are used
- Discussions on direct rates
- Discussions on many non-labor elements, like travel, subcontractor costs, direct materials, OCONUS allowances, etc.
- Discussions on all pricing actions before, during and after proposal cycles
DFARS 252.215-7002 defines an estimating system as the contractor’s policies, procedures, and practices for budgeting and planning controls and for generating cost estimates in proposals, then lists seventeen functions an acceptable system must perform. The last is explicit: an adequate system description — policies, procedures, and estimating and budgeting practices — that complies with the FAR and DFARS. Those requirements bite when a contractor is a large business that received $50 million or more in DoD prime contracts or subcontracts requiring certified cost or pricing data in the prior fiscal year, or between $10 and $50 million and was notified in writing by the contracting officer.
The stakes are cash. If the contracting officer makes a final determination disapproving the system and the contract carries DFARS 252.242-7005, payments are withheld under that clause — five percent for weaknesses in a single business system, up to ten percent across multiple. You get 45 days to correct the weaknesses or submit an acceptable corrective action plan, and the withhold drops to two percent once that plan is accepted and being effectively implemented.
Consistency is the second driver. CAS 401 requires estimating practices to align with how costs are actually accumulated and reported — nearly impossible to demonstrate when every capture manager builds a basis of estimate from memory.
Third, defective pricing. Above the $2.5 million certified cost or pricing data threshold, inaccurate, incomplete, or noncurrent data entitle the government to a price adjustment, plus interest and a penalty equal to the overpayment if the submission was knowing. Documented sweep and update procedures are your evidence of good faith.
One final thought; in some efforts, higher scores are possible for offerors who have a documented cost estimating system/manual; for example, CIO-SP4.
Having a written estimating system guides you, protects you, helps you win, and stops the scramble when things go wrong!
- August 17-20th: Premier Navy Procurement Expoin San Diego, CA
- August 27th: 2026 Navy Summit 27th in Falls Church, VA
- September 24th: 2026 Intel Summit in Falls Church, VA