FAR 34.005—General requirements.

Competition.

FAR 34.005-1 addresses competition in major system acquisitions and is aimed at preventing early lock-in to a single concept or source before the government has had a fair chance to compare alternatives. It requires the program manager to promote full and open competition throughout the acquisition process, sustain effective competition between alternative major system concepts and sources, and do so only to the extent it is economically beneficial and practicable. The section also requires broad, effective notice of the proposed acquisition across business, academic, and Government communities so that capable sources have a real opportunity to participate. In addition, it recognizes that foreign contractors, technology, and equipment may be considered when feasible and permissible, which broadens the competitive field where allowed. Finally, it directs the contracting officer to time solicitation issuance and contract award to preserve continuity of concept development when transitioning from the withdrawing concept proposer to a new contractor. In practice, this section is about preserving competition, widening market awareness, and managing transitions carefully so major system development does not lose momentum or become unnecessarily constrained by an early source choice.

Mission-oriented solicitation.

FAR 34.005-2 addresses how a contracting officer should structure and distribute a mission-oriented solicitation for major systems or other acquisitions where the Government is focused on required mission capabilities rather than prescribing a specific solution. It covers advance notice of the acquisition, broad market outreach, presolicitation conferences and draft-solicitation comment opportunities, distribution of the final solicitation, the required content of that solicitation, the use of mission-capability language instead of system-specific descriptions, access to Government data, selection requirements tied to the acquisition strategy, freedom for offerors to propose alternative technical approaches and tradeoffs, mandatory Earned Value Management System (EVMS) requirements when applicable, and the general preference to avoid Government specifications and standards unless a subsystem or component is specifically mandated under agency procedures. In practice, this section is meant to encourage competition, innovation, and broader industry participation by telling the market what outcome the Government needs rather than dictating how to achieve it. It also helps reduce lock-in to a particular design or vendor solution and supports better acquisition planning by allowing industry to comment before the solicitation is finalized. For contractors, this means proposals can be more creative and solution-driven; for contracting officers, it means the solicitation must be carefully written to preserve flexibility while still giving offerors enough information to compete intelligently.

Concept exploration contracts.

FAR 34.005-3 addresses how agencies should structure and continue concept exploration contracts in major system acquisition. It covers four main ideas: keeping concept exploration contracts relatively short in duration, setting them at planned dollar levels, using them to refine the proposed concept and reduce technical uncertainty, ensuring the scope of work matches the Government’s planned budget for the phase, and deciding whether to award follow-on contracts during the exploration phase. In practice, this section is meant to prevent agencies from overcommitting too early, while still allowing promising concepts to be explored efficiently and economically. It gives contracting officers and program managers a framework for controlling risk, limiting exposure, and making incremental funding and award decisions based on technical progress and affordability. For contractors, it signals that concept exploration work is expected to be tightly scoped, budget-aware, and subject to continued performance review before additional work is awarded.

Demonstration contracts.

FAR 34.005-4 addresses how contracting officers should structure demonstration-phase contracts when an agency is evaluating a system or concept before committing to full-scale development. It covers two main topics: first, the preference that, whenever practicable, the demonstration contract require the contractor to submit a priced proposal for full-scale development by the end of the demonstration phase; and second, the contracting officer’s duty to give the contractor the information needed to prepare that proposal, including operational test conditions, performance criteria, life cycle cost factors, and any other selection criteria. The purpose of the section is to make the transition from demonstration to development more disciplined, comparable, and cost-informed, rather than leaving the Government to negotiate the next phase with incomplete information. In practice, this means the demonstration phase should be designed not just to prove technical feasibility, but also to generate a credible basis for selecting a contractor for the next phase. The requirement that the proposal be “totally funded by the Government” reflects that the Government should bear the cost of obtaining the proposal as part of the demonstration effort, rather than shifting that burden to the contractor. This section is especially important in research, prototype, and advanced development efforts where agencies need a fair, structured way to compare competing approaches before awarding full-scale development.

Full-scale development contracts.

FAR 34.005-5 addresses how full-scale development contracts should be structured when an agency is moving from development into a possible production decision. The section focuses on one practical topic: whether, and how, the contract should require contractors to submit priced production proposals during development. It says that, whenever practicable, those proposals should be based on the latest quantity, schedule, logistics requirements, and other factors that will be used to decide whether to buy production. In practice, this helps the Government compare realistic production pricing before committing to a production buy, and it helps avoid relying on outdated assumptions from earlier development stages. The rule is aimed at improving the quality of the production decision, reducing rework, and making sure the eventual production proposal reflects current program needs rather than stale estimates. It is a planning and solicitation/contract-structure requirement, not a mandatory requirement in every case, because it applies only when practicable.

Full production.

FAR 34.005-6 addresses when an agency may move from full-scale development into full production for a major system. It covers two core topics: the condition that the system must have been successfully tested during development, and the approval steps required before production can be awarded. In practice, this section is a gatekeeping rule that prevents agencies from committing to full-rate production too early, before the system has demonstrated it can perform as intended. It also makes clear that the decision is not automatic: the agency head must personally or formally reaffirm the mission need and program objectives and then approve proceeding with production. For contractors, this section signals that a production award depends not just on technical success, but also on high-level program validation and authorization. For contracting officers and program officials, it is a reminder that production decisions must be tied to documented test results and senior-level approval.