FAR 9.505-1—Providing systems engineering and technical direction.
Plain-English Summary
FAR 9.505-1 addresses organizational conflicts of interest when a contractor performs systems engineering and technical direction for a system but does not have overall contractual responsibility for the system’s development, integration, assembly and checkout, or production. The section explains the core prohibition: a contractor in that influential advisory role generally may not later be awarded the contract to supply the system or any major component, and may not serve as a subcontractor or consultant to a supplier of the system or major components. It also defines the kinds of activities that count as systems engineering and technical direction, including determining specifications, identifying and resolving interface problems, developing test requirements, evaluating test data, supervising design, developing work statements, determining parameters, directing other contractors’ operations, and resolving technical controversies. The purpose is to prevent a contractor from using its privileged role to shape requirements, technical judgments, or procurement outcomes in a way that favors its own products or capabilities. In practice, this section is meant to preserve fairness, objectivity, and competition by separating influential technical advisory work from downstream supply or implementation roles on the same system.
Key Rules
No supply award after advisory role
A contractor that provides systems engineering and technical direction for a system, but does not hold overall responsibility for development, integration, assembly and checkout, or production, generally cannot be awarded the contract to supply that system or any major component of it.
No subcontracting to supplier
The same contractor also may not act as a subcontractor or consultant to a supplier of the system or any major component. This prevents the contractor from indirectly benefiting from the system it helped shape.
Systems engineering defined broadly
Systems engineering covers substantially all of several technical functions, including determining specifications, identifying and resolving interface problems, developing test requirements, evaluating test data, and supervising design. The rule focuses on the contractor’s influence over the system’s basic technical direction.
Technical direction defined broadly
Technical direction includes substantially all of the following: developing work statements, determining parameters, directing other contractors’ operations, and resolving technical controversies. These activities place the contractor in a position to influence how the work is performed and by whom.
Influence creates conflict risk
The section recognizes that a contractor performing these functions occupies a highly influential and responsible position in shaping system concepts and supervising execution. Because of that influence, the contractor should not be able to make decisions that favor its own products or capabilities.
Responsibilities
Contracting Officer
Identify when a contractor’s systems engineering or technical direction role creates an organizational conflict of interest, and avoid awarding that contractor the supply contract or allowing it to support a supplier as a subcontractor or consultant when the rule applies.
Contractor performing systems engineering or technical direction
Recognize that performing these advisory and supervisory functions can disqualify the contractor from later supplying the system or major components, and from supporting a supplier as a subcontractor or consultant.
Agency
Structure acquisitions to separate influential systems engineering/technical direction work from supply and production roles, so the contractor shaping the system is not also positioned to benefit from the resulting procurement.
Supplier of the system or major components
Avoid engaging a contractor that performed the prohibited systems engineering or technical direction role as a subcontractor or consultant on the same system or major component.
Practical Implications
This rule is a classic OCI safeguard: if a contractor helps define the system, it usually cannot later compete to build or supply that same system or major parts of it.
The biggest pitfall is underestimating how broad the covered activities are; even partial involvement in specifications, interfaces, test requirements, or technical controversy resolution can trigger the restriction.
Contracting officers should look beyond job titles and examine the actual functions performed, because the rule turns on substance, not labels.
Contractors should screen proposed work carefully before accepting advisory or technical direction tasks, since those roles can foreclose later supply or subcontract opportunities on the same program.
Agencies should document the scope of the contractor’s influence and use acquisition planning to prevent a contractor from being both the architect of the requirements and a beneficiary of the resulting buy.
Official Regulatory Text
(a) A contractor that provides systems engineering and technical direction for a system but does not have overall contractual responsibility for its development, its integration, assembly, and checkout, or its production shall not- (1) Be awarded a contract to supply the system or any of its major components; or (2) Be a subcontractor or consultant to a supplier of the system or any of its major components. (b) Systems engineering includes a combination of substantially all of the following activities: determining specifications, identifying and resolving interface problems, developing test requirements, evaluating test data, and supervising design. Technical direction includes a combination of substantially all of the following activities: developing work statements, determining parameters, directing other contractors’ operations, and resolving technical controversies. In performing these activities, a contractor occupies a highly influential and responsible position in determining a system’s basic concepts and supervising their execution by other contractors. Therefore this contractor should not be in a position to make decisions favoring its own products or capabilities.