2.1 FAR Structure, Authority & Hierarchy (Part 1)

Every CON 3990V scenario sits inside a regulatory hierarchy. If you cannot place a rule in the correct layer—statute, FAR, DFARS, agency policy, or local procedure—you will pick the wrong procedure even when you remember a dollar threshold. This section builds the map: what the FAR is, how it is organized, who has authority to act, and how DoD supplements fit without replacing the baseline.

The FAR as Primary Acquisition Regulation

The Federal Acquisition Regulation (FAR) is the primary regulation for use by all executive agencies in their acquisition of supplies and services with appropriated funds. It is jointly issued under the statutory authority of the Administrator of General Services, the Secretary of Defense, and the Administrator of NASA, acting through the Federal Acquisition Regulatory Council (FAR Council). For DoD contracting professionals, the FAR is not optional background reading—it is the default rule set that governs how the Government buys.

Think of the FAR as the national playbook. Agency supplements (including DFARS) and internal guidance add DoD-specific plays, but they do not rewrite the Constitution of federal buying. When a scenario asks which regulation applies first, start with the FAR unless a statute, Executive Order, or authorized deviation clearly controls.

Why hierarchy shows up on CON 3990V

CON 3990V is closed-book. WarU/FAI materials emphasize that you must recognize titles, purposes, and relationships without opening acquisition.gov. Hierarchy items typically test whether you:

• Apply FAR commercial procedures when the requirement meets the commercial product/service definition
• Use simplified acquisition procedures when the estimated value is within the simplified acquisition threshold and other conditions are met
• Recognize that a local "how we do it here" memo cannot override the FAR or DFARS
• Know that DFARS implements or supplements FAR—it does not create a parallel universe that replaces FAR Parts

FAR System Architecture: Parts, Subparts, Sections, Subsections

The FAR is organized in a numbered citation scheme you must read fluently:

Citation literacy matters because exam stems often say "under FAR Part 6" or "consistent with Part 12" without quoting the text. You must already know what each Part covers at the title/substance level (covered in section 2.3 of this chapter).

Practical reading habit

When you later drill practice questions, force yourself to name the controlling Part before you pick an answer. Example: a protest of a contract award points to FAR Part 33; a commercial item acquisition points to Part 12 (and often Part 13 or 15 procedures as allowed); a set-aside decision points to Part 19. That mental "Part tag" is how closed-book performers stay oriented under time pressure.

FAR Part 1: Purpose, Authority, and the FAR System

FAR Part 1 — Federal Acquisition Regulations System is the meta-rulebook. It explains why the FAR exists, who issues it, how it is maintained, and how agencies may deviate.

Purpose of the FAR (high-yield)

FAR Part 1 frames the System as delivering best value products and services while maintaining public trust and fulfilling public policy objectives. In exam language, "best value" is not a slogan—it is the acquisition outcome standard that balances cost, quality, and other factors under the applicable source selection approach. Public trust ties directly to competition, integrity, and documentation standards you will meet again in Guiding Principles and Award phases.

Authority and issuance

The FAR is codified in Title 48 of the Code of Federal Regulations (CFR), Chapter 1. Agency acquisition regulations that implement or supplement the FAR are published in subsequent CFR chapters (DoD's DFARS is Chapter 2). That codification structure is why "acquisition.gov and the CFR" are the official text sources—not contractor blogs or local slide decks.

Deviations: individual vs class

A deviation is an authorized departure from the FAR (or from an agency supplement) when needed for a specific situation or class of situations. Part 1 distinguishes:

Key exam traps:

• A deviation is not informal "CO judgment" to ignore a mandatory clause. Deviations require proper approval authority under Part 1 / agency procedures.
• Class deviations often address systemic issues (e.g., interim policy pending formal rulemaking). Individual deviations solve one-off problems.
• Using a past practice that "everyone does" without documented deviation authority is not a defense if the FAR mandates a procedure.

On CON 3990V, if a stem describes skipping a required publicizing step or competition rule "because leadership wants speed," the correct analysis is usually: follow the FAR, seek an authorized exception or deviation path if one exists, and document—do not invent shortcuts.

Agency Supplements: DFARS Implements and Supplements the FAR

The Defense Federal Acquisition Regulation Supplement (DFARS) is DoD's agency acquisition regulation. Critical relationship:

DFARS implements and supplements the FAR for DoD acquisitions. It does not replace the FAR.

Implementation means DFARS may prescribe how DoD applies a FAR rule (additional procedures, clauses, approvals). Supplementation means DFARS may add DoD-unique policies where the FAR is silent or where DoD has distinct statutory requirements. Replacement is never the correct mental model: you still need FAR Part 12 for commercial acquisition policy, FAR Part 15 for negotiation architecture, FAR Part 33 for protests and disputes framework, and so on—even when a DFARS provision adds DoD detail.

Hierarchy snapshot for DoD buyers

When rules conflict, the higher authority controls. Local SOP cannot legalize an unauthorized sole-source if FAR Part 6 competition requirements are not met (unless a valid exception/justification path is used).

The Acquisition Team Concept

FAR Part 1 promotes the acquisition team concept: successful contracting is a multi-disciplinary effort. The team includes the Contracting Officer, requirements personnel (program managers, technical experts), finance/budget, legal counsel, small business specialists, quality assurance, logistics, and other stakeholders as needed.

Why this matters on the exam:

• Guiding Principles questions test collaboration, communication, and documentation across roles—not only clause knowledge
• Pre-award planning (Part 7), market research (Part 10), and source selection (Part 15) fail when the CO works in isolation
• Post-award administration (Part 42) and quality (Part 46) depend on clear role handoffs between CO, COR, and the requiring activity

The Contracting Officer remains the business advisor and authorized agent of the Government for the contract action, but mission success is a team product.

Contracting Officer Authority and Warrants (High Level)

A Contracting Officer (CO) is a person with the authority to enter into, administer, or terminate contracts and make related determinations and findings—to the extent of the authority delegated in a warrant (or other written authorization).

Exam-critical ideas:

1. Warrant limits control. A CO cannot bind the Government beyond the dollar, type, or subject-matter limits of the appointment.
2. Only authorized agents bind the Government. Unauthorized commitments (someone without authority promising the Government will pay) generally require ratification under FAR procedures—not automatic payment.
3. Delegations are personal and documented. Titles like "project lead" or "COR" do not automatically include contracting authority to award or modify contracts unless properly designated.
4. Responsibility and integrity travel with the authority. The CO's signature means the action complies with law, regulation, and available funds within the warrant.

CO vs COR (preview for later chapters)

The Contracting Officer's Representative (COR) typically provides technical monitoring and surveillance under a designation letter. CORs do not award contracts, do not independently change contract terms, and do not bind the Government outside their written designation. Hierarchy and role clarity prevent constructive changes and unauthorized commitments—both classic post-award traps.

Why Hierarchy Mastery Wins Closed-Book Points

Closed-book exams reward structure over trivia. Train this reflex:

1. Identify the life-cycle phase (pre-award, award, post-award) and the competency being tested
2. Name the controlling FAR Part by title (competition, commercial, simplified, negotiation, types, protests, administration, termination)
3. Check for DoD-unique DFARS overlays only after the FAR baseline is clear
4. Apply authority limits (warrant, ratification, deviation approval)
5. Document the rationale as if a file review or protest will follow

If two answers look plausible, the one that respects hierarchy (FAR first, authorized exception second, informal preference last) is usually correct.

Memory anchor

"Statute → FAR → DFARS → local → contract." Memorize that ladder. Everything else in CON 3990V hangs on it.