GovCon Glossary

The network of companies, facilities, and workers (government and private) that research, design, develop, produce, and maintain military weapons systems and equipment for U.S. armed forces. It spans prime contractors down through subcontractors and suppliers, and DoD designates it a critical infrastructure sector subject to specific cybersecurity requirements like CMMC.

The primary regulation governing how executive branch agencies buy goods and services, covering solicitation, source selection, contract types, clauses, and administration. Codified in Title 48 of the CFR, it's supplemented by agency-specific rules like the DFARS and is currently being rewritten under the FAR overhaul to simplify and modernize its structure.

A federal law (5 U.S.C. § 552) giving the public the right to request records held by federal agencies, subject to nine exemptions covering classified information, trade secrets, and personal privacy, among others. Contractors run into FOIA when competitors request copies of awarded contracts or proposals, making it important to properly mark proprietary data for exemption.

A joint government-contractor review, held early in contract performance, to confirm that the program's performance measurement baseline realistically reflects the scope, schedule, and budget of the work. It's typically required on cost-type or incentive contracts subject to earned value management and is meant to surface risks in the plan before performance data starts flowing.

An event-driven document that lays out a program's key milestones and, for each one, the accomplishments and measurable criteria needed to call it complete. It's a top-down planning tool, paired with the time-based Integrated Master Schedule, used mainly on large DoD programs to track technical progress against the contract baseline.

State Department regulations (22 CFR 120-130) controlling the export, temporary import, and brokering of defense articles, technical data, and defense services listed on the U.S. Munitions List. Administered by the Directorate of Defense Trade Controls, ITAR requires registration, licensing, and access controls for any company that designs, manufactures, or handles controlled items or data, including with foreign-person employees.

A source selection method in which the government evaluates proposals on a pass/fail technical basis and awards to the lowest-priced offer among those judged acceptable. Unlike a best-value tradeoff, exceeding the technical requirements earns no extra credit, so LPTA works best for well-defined, low-risk requirements with little room for meaningful technical differentiation.

An acquisition approach that structures a contract's requirements, incentives, and payments around measurable performance outcomes rather than prescribing how the work should be done. It typically relies on a performance work statement or statement of objectives, paired with a quality assurance surveillance plan, to hold the contractor accountable for results instead of process compliance.

A systems engineering technical review, held after initial requirements analysis, that examines a system's preliminary design against its performance requirements before detailed design begins. Passing PDR establishes the allocated baseline and gives the program confidence that the proposed architecture and design trade-offs are sound enough to commit to detailed design.

A short, high-level document that states the government's broad goals for an acquisition without dictating the specific tasks, methods, or performance standards used to reach them. Offerors respond by proposing their own performance work statement and technical approach for meeting the objectives, giving industry room to drive the solution rather than following a government-written work statement.

A technical review conducted early in system development to confirm that the contractor's system requirements are complete, testable, and traceable to the government's capability documents, and consistent with cost, schedule, and technology constraints. Passing SRR signals the program is ready to begin preliminary design.

A technical review at which the government examines objective evidence (test data, analysis, demonstration) to confirm the as-built system actually meets the requirements documented in its functional baseline. It's often held alongside, or used interchangeably with, a system-level functional configuration audit.

The standard section structure that FAR-based solicitations and contracts follow, running Parts I through IV and Sections A through M: the schedule and specifications (A-H), contract clauses (I), attachments (J), and offeror representations, instructions, and evaluation factors (K-M). Knowing the UCF lets proposal teams map RFP requirements to the right contract section quickly.

The official, organized compilation of all permanent federal statutes, arranged by subject into numbered titles, such as Title 10 for the armed forces or Title 41 for public contracts. Government contracting rules like the FAR are written to implement authority granted somewhere in the USC, so regulatory citations often trace back to it.

The list, found at 22 CFR Part 121, identifying the specific defense articles, technical data, and defense services subject to ITAR export controls, organized into 21 categories such as firearms, spacecraft, and military electronics. Whether an item appears on the USML, versus the Commerce Department's Commerce Control List, determines which export-control regime and licensing process applies.

A Department of Labor schedule of minimum wage and fringe benefit rates that must be paid to workers on a covered federal contract, based on locality and labor category, under the Davis-Bacon Act (construction) or Service Contract Act (services). Contracting officers typically pull the applicable determination from SAM.gov and incorporate it directly into the solicitation and resulting contract.