(b)(i) For contractors, other than litigation support contractors, accessing third party proprietary technical data or computer Software, non-disclosure requirements are addressed at 227.7103-7(b), through use of the clause at 252.227-7025 as prescribed at 227.7103-6(c) and 227.7203-6(d). Pursuant to that clause, covered Government support contractors may be required to enter into non-disclosure agreements directly with the third party asserting restrictions on limited rights technical data, commercial technical data, or restricted rights computer software. The contracting officer is not required to obtain copies of these agreements or to ensure that they are properly executed.

(ii) For litigation support contractors accessing litigation information, including that originating from third parties, use and non-disclosure requirements are addressed through the use of the clause at 252.204-7014, as prescribed at 204.7403(a). Pursuant to the clause, litigation support contractors are not required to enter into non-disclosure agreements directly with any third party asserting restrictions on any litigation information.

“Lead system integrator,” as used in this section, is defined in the clause at 252.209-7007 , Prohibited Financial Interests for Lead System Integrators. See PGI 209.570-1 for additional information.

(a) Except as provided in paragraph (b) of this subsection, 10 U.S.C. 2410p prohibits any entity performing lead system integrator functions in the acquisition of a major system by DoD from having any direct financial interest in the development or construction of any individual system or element of any system of systems.

(b) The prohibition in paragraph (a) of this subsection does not apply if—

(1) The Secretary of Defense certifies to the Committees on Armed Services of the Senate and the House of Representatives that—

(i) The entity was selected by DoD as a contractor to develop or construct the system or element concerned through the use of competitive procedures; and

(ii) DoD took appropriate steps to prevent any organizational conflict of interest in the selection process; or

(2) The entity was selected by a subcontractor to serve as a lower-tier subcontractor, through a process over which the entity exercised no control.

(c) In accordance with Section 802 of the National Defense Authorization Act for Fiscal Year 2008 (Pub. L. 110-181), DoD may award a new contract for lead system integrator functions in the acquisition of a major system only if—

(1) The major system has not yet proceeded beyond low-rate initial production; or

(2) The Secretary of Defense determines in writing that it would not be practicable to carry out the acquisition without continuing to use a contractor to perform lead system integrator functions and that doing so is in the best interest of DoD. The authority to make this determination may not be delegated below the level of the Under Secretary of Defense for Acquisition, Technology, and Logistics. (Also see 209.570-3 (b).)

(d) Effective October 1, 2010, DoD is prohibited from awarding a new contract for lead system integrator functions in the acquisition of a major system to any entity that was not performing lead system integrator functions in the acquisition of the major system prior to January 28, 2008.

(a) In making a responsibility determination before awarding a contract for the acquisition of a major system, the contracting officer shall—

(1) Determine whether the prospective contractor meets the definition of “lead system integrator”;

(2) Consider all information regarding the prospective contractor’s direct financial interests in view of the prohibition at 209.570-2 (a); and

(3) Follow the procedures at PGI 209.570-3 .

(b) A determination to use a contractor to perform lead system integrator functions in accordance with 209.570-2 (c)(2)—

(1) Shall specify the reasons why it would not be practicable to carry out the acquisition without continuing to use a contractor to perform lead system integrator functions, including a discussion of alternatives, such as use of the DoD workforce or a system engineering and technical assistance contractor;

(2) Shall include a plan for phasing out the use of contracted lead system integrator functions over the shortest period of time consistent with the interest of the national defense; and

(3) Shall be provided to the Committees on Armed Services of the Senate and the House of Representatives at least 45 days before the award of a contract pursuant to the determination.

(a) Use the provision at 252.209-7006 , Limitations on Contractors Acting as Lead System Integrators, in solicitations for the acquisition of a major system when the acquisition strategy envisions the use of a lead system integrator.

(b) Use the clause at 252.209-7007 , Prohibited Financial Interests for Lead System Integrators—

(1) In solicitations that include the provision at 252.209-7006 ; and

(2) In contracts when the contractor will fill the role of a lead system integrator for the acquisition of a major system.

This subpart implements section 207 of the Weapons System Acquisition Reform Act of 2009 (Pub. L. 111-23).

As used in this section—

“Lead system integrator” includes “lead system integrator with system responsibility” and “lead system integrator without system responsibility”.

(i) “Lead system integrator with system responsibility” means a prime contractor for the development or production of a major system, if the prime contractor is not expected at the time of award to perform a substantial portion of the work on the system and the major subsystems.

(ii) “Lead system integrator without system responsibility” means a prime contractor under a contract for the procurement of services, the primary purpose of which is to perform acquisition functions closely associated with inherently governmental functions (see section 7.503(d) of the Federal Acquisition Regulation) with respect to the development or production of a major system.

“Major subcontractor” means a subcontractor that is awarded a subcontract that equals or exceeds—

(i) Both the certified cost or pricing data threshold and 10 percent of the value of the contract under which the subcontract is awarded; or

(ii) $55 million.

“Pre-Major Defense Acquisition Program” means a program that is in the Materiel Solution Analysis or Technology Development Phases preceding Milestone B of the Defense Acquisition System and has been identified to have the potential to become a major defense acquisition program.

“Systems engineering and technical assistance.”

(1) “Systems engineering” means an interdisciplinary technical effort to evolve and verify an integrated and total life cycle balanced set of system, people, and process solutions that satisfy customer needs.

(2) “Technical assistance” means the acquisition support, program management support, analyses, and other activities involved in the management and execution of an acquisition program.

(3) “Systems engineering and technical assistance”—

(i) Means a combination of activities related to the development of technical information to support various acquisition processes. Examples of systems engineering and technical assistance activities include, but are not limited to, supporting acquisition efforts such as—

(A) Deriving requirements;

(B) Performing technology assessments;

(C) Developing acquisition strategies;

(D) Conducting risk assessments;

(E) Developing cost estimates;

(F) Determining specifications;

(G) Evaluating contractor performance and conducting independent verification and validation;

(H) Directing other contractors’ (other than subcontractors) operations;

(I) Developing test requirements and evaluating test data;

(J) Developing work statements (but see paragraph (ii)(B) of this definition).

(ii) Does not include—

(A) Design and development work of design and development contractors, in accordance with FAR 9.505-2(a)(3) or FAR 9.505-2(b)(3), and the guidance at PGI 209.571-7 ; or

(B) Preparation of work statements by contractors, acting as industry representatives, under the supervision and control of Government representatives, in accordance with FAR 9.505-2(b)(1)(ii).

(a) This subsection applies to major defense acquisition programs.

(b) To the extent that this section is inconsistent with FAR subpart 9.5, this section takes precedence.

It is DoD policy that—

(a) Agencies shall obtain advice on major defense acquisition programs and pre-major defense acquisition programs from sources that are objective and unbiased; and

(b) Contracting officers generally should seek to resolve organizational conflicts of interest in a manner that will promote competition and preserve DoD access to the expertise and experience of qualified contractors. Accordingly, contracting officers should, to the extent feasible, employ organizational conflict of interest resolution strategies that do not unnecessarily restrict the pool of potential offerors in current or future acquisitions. Further, contracting activities shall not impose per se restrictions or limitations on the use of particular resolution methods, except as may be required under 209.571-7 or as may be appropriate in particular acquisitions.

(a) Mitigation is any action taken to minimize an organizational conflict of interest. Mitigation may require Government action, contractor action, or a combination of both.

(b) If the contracting officer and the contractor have agreed to mitigation of an organizational conflict of interest, a Government-approved Organizational Conflict of Interest Mitigation Plan, reflecting the actions a contractor has agreed to take to mitigate a conflict, shall be incorporated into the contract.

(c) If the contracting officer determines, after consultation with agency legal counsel, that the otherwise successful offeror is unable to effectively mitigate an organizational conflict of interest, then the contracting officer, taking into account both the instant contract and longer term Government needs, shall use another approach to resolve the organizational conflict of interest, select another offeror, or request a waiver in accordance with FAR 9.503 (but see statutory prohibition in 209.571-7 , which cannot be waived).

(d) For any acquisition that exceeds $1 billion, the contracting officer shall brief the senior procurement executive before determining that an offeror’s mitigation plan is unacceptable.

For limitations on contractors acting as lead systems integrators, see 209.570 .

When evaluating organizational conflicts of interest for major defense acquisition programs or pre-major defense acquisition programs, contracting officers shall consider—

(a) The ownership of business units performing systems engineering and technical assistance, professional services, or management support services to a major defense acquisition program or a pre-major defense acquisition program by a contractor who simultaneously owns a business unit competing (or potentially competing) to perform as—

(1) The prime contractor for the same major defense acquisition program; or

(2) The supplier of a major subsystem or component for the same major defense acquisition program.

(b) The proposed award of a major subsystem by a prime contractor to business units or other affiliates of the same parent corporate entity, particularly the award of a subcontract for software integration or the development of a proprietary software system architecture; and

(c) The performance by, or assistance of, contractors in technical evaluation.

(a) Agencies shall obtain advice on systems architecture and systems engineering matters with respect to major defense acquisition programs or pre-major defense acquisition programs from Federally Funded Research and Development Centers or other sources independent of the major defense acquisition program contractor.

(b) Limitation on Future Contracting.

(1) Except as provided in paragraph (c) of this subsection, a contract for the performance of systems engineering and technical assistance for a major defense acquisition program or a pre-major defense acquisition program shall prohibit the contractor or any affiliate of the contractor from participating as a contractor or major subcontractor in the development or production of a weapon system under such program.

(2) The requirement in paragraph (b)(1) of this subsection cannot be waived.

(c) Exception.

(1) The requirement in paragraph (b)(1) of this subsection does not apply if the head of the contracting activity determines that—

(i) An exception is necessary because DoD needs the domain experience and expertise of the highly qualified, apparently successful offeror; and

(ii) Based on the agreed-to resolution strategy, the apparently successful offeror will be able to provide objective and unbiased advice, as required by 209.571-3 (a), without a limitation on future participation in development and production.

(2) The authority to make this determination cannot be delegated.

(a) Use the provision at 252.209-7008 , Notice of Prohibition Relating to Organizational Conflict of Interest—Major Defense Acquisition Program, if the solicitation includes the clause at 252.209-7009 , Organizational Conflict of Interest—Major Defense Acquisition Program; and

(b) Use the clause at 252.209-7009 , Organizational Conflict of Interest—Major Defense Acquisition Program, in solicitations and contracts for systems engineering and technical assistance for major defense acquisition programs or pre-major defense acquisition programs.

NO DFARS TEXT