FAR 39.000—Scope of part.
Plain-English Summary
FAR 39.000 is the scope statement for FAR Part 39, and it tells contracting personnel what kinds of acquisitions this part governs. Specifically, it covers acquisition policies and procedures for information technology, including financial management systems, and for information and communication technology, as defined in FAR 2.101. It also makes clear that Part 39 must be read consistently with the rest of the FAR and with the applicable Office of Management and Budget guidance, including OMB Circular No. A-127 on financial management systems and OMB Circular No. A-130 on managing federal information resources. In practice, this section is important because it signals that IT buys are not handled as ordinary procurements; they must account for governmentwide policy on system planning, management, security, and lifecycle considerations. It helps contracting officers and program offices identify when Part 39 applies and reminds them that other FAR parts and OMB requirements may control or supplement the acquisition strategy.
Key Rules
Part 39 covers IT acquisitions
This part applies to acquisitions of information technology, including financial management systems. If the requirement involves IT, the contracting team should look to Part 39 for the governing policies and procedures.
Financial systems are included
Financial management systems are expressly within scope, so acquisitions for accounting, budgeting, finance, and related systems must be handled under the Part 39 framework as well as any other applicable rules.
ICT is covered
The part also applies to information and communication technology, using the definition in FAR 2.101. That means the scope is broader than traditional computer hardware or software and includes the ICT items and services captured by the FAR definition.
Read with other FAR parts
Part 39 must be used consistently with the rest of the FAR. Contracting officers cannot treat it as a stand-alone rule set; they must also apply any other FAR parts that govern the specific acquisition.
OMB guidance remains controlling
The section specifically ties Part 39 to OMB Circular A-127 and OMB Circular A-130. Agencies must align IT and financial system acquisitions with those policy requirements, not just with the FAR text.
Responsibilities
Contracting Officer
Identify whether the requirement is for IT, a financial management system, or ICT, and apply Part 39 together with any other relevant FAR parts and OMB policy. Ensure the acquisition approach is consistent with the applicable definitions and governmentwide information management requirements.
Program/Requirement Owner
Describe the need accurately so the acquisition team can determine whether the requirement falls within Part 39. Provide enough information about the system or technology to support compliance with OMB and FAR policy.
Agency
Establish acquisition practices for IT and financial systems that conform to Part 39 and the referenced OMB circulars. Ensure internal policies, reviews, and approvals support compliant planning and procurement of information resources.
IT/Information Management Officials
Support the acquisition team in determining whether the item or service is IT or ICT under the FAR definition and in applying agency and OMB information resource policies. Help ensure the proposed solution fits enterprise architecture, management, and lifecycle requirements.
Practical Implications
This section is a trigger for special handling: once a requirement is IT, financial management, or ICT, the acquisition team should immediately check Part 39 and related OMB policy rather than using a generic procurement approach.
A common pitfall is assuming that only software or computers are covered. The scope is broader, especially because ICT is defined in FAR 2.101 and can include a wider range of technology-related acquisitions.
Another frequent mistake is treating Part 39 as the only authority. In reality, it works alongside other FAR parts and OMB circulars, so compliance requires a broader policy review.
For contractors, the practical effect is that solicitations for IT-related work may include additional planning, security, interoperability, lifecycle, or management expectations beyond standard commercial terms.
For contracting officers, the key watch-out is scope identification early in acquisition planning, because misclassifying an IT requirement can lead to using the wrong procedures, missing required reviews, or conflicting with OMB guidance.
Official Regulatory Text
This part prescribes acquisition policies and procedures for use in acquiring— (a) Information technology, including financial management systems, consistent with other parts of this regulation, OMB Circular No.A-127, Financial Management Systems and OMB Circular No.A-130, Management of Federal Information Resources. (b) Information and communication technology (see 2.101 ).