TOS II_RFI_1_ATCH 2_Clause H115_OCI.pdf

PDF 718 KB Posted

Attached to
Test Operations and Sustainment (TOS) II Federal contract opportunity
Solicitation number
FA9101-22-R-B001
Issued by
Department of the Air Force Materiel Command Test Center

View the file

Other files for this federal contract opportunity

Other files attached to Test Operations and Sustainment (TOS) II, newest first.
File Type Posted
Instructions to Gain Access to Controlled Documents.pdf PDF
TOS II Attachment 7 PWS (3_26 excerpt).pdf PDF
TOS II Attachment L-9.1 Cost Model for Sub.xlsx XLSX spreadsheet
TOS II_DRFP_Amend_01_Revised Cost Model.pdf PDF
TOS II DRFP Cover Letter.pdf PDF
TOS II SF33 Draft RFP FA910122RB001 Part 1 of 2.pdf PDF
TOS II SF33 Draft RFP FA910122RB001 Part 2 of 2.pdf PDF
TOS II Exhibit A CDRLs.pdf PDF
TOS II Attachment 2 DD254.pdf PDF
TOS II Attachment 3 SCLS Wage Determinations.pdf PDF
TOS II Attachment 5 Award Fee Term Plan.pdf PDF
PPI tool.zip ZIP file
TOS II Exhibit C CBAs.pdf PDF
TOS II Attachment 8_1 CAP Arnold_NFAC_T9.pdf PDF
TOS II Attachment 8_2 GFP AVSF_LGTF_NRTF.pdf PDF
TOS II Attachment 8_3 CAP AVSF_LGTF_NRTF.pdf PDF
TOS II Attachment L_3 PPQ Cover Letter.pdf PDF
TOS II Attachment L_6 Relevancy Matrix.pdf PDF
TOS II Attachment L_8 Workload Resource Guide.pdf PDF
TOS II Attachment L_11 Surge Project Sample Task Questions.pdf PDF
TOS II Attachment L_12 SB Participation Template.pdf PDF
TOS II Attachment 1 Workload by WBS.pdf PDF
TOS II Attachment 8 GFP Arnold_NFAC_T9.pdf PDF
TOS II Attachment L_5 Subcontractor Consent Letter.pdf PDF
TOS II Attachment L_7 Cross Reference Matrix.pdf PDF
TOS II Attachment L_9 Cost Model.xlsx XLSX spreadsheet
TOS II Exhibit B DIDs.pdf PDF
TOS II OCI MultiStep Atch 1 Flow Chart.pdf PDF
TOS II OCI MultiStep Atch 3 Draft L and M.pdf PDF
TOS II OCI MultiStep Atch 2 Draft H115 OCI Clause.pdf PDF
TOS II_RFI_3_Amend_04_Final.pdf PDF
TOS II_RFI_3_Amend_04_ATCH 1_Draft Cost Model for Offerors.xlsx XLSX spreadsheet
TOS II_RFI_3_Amend_03_Final.pdf PDF
TOS II_RFI_3_Amend_02_Final.pdf PDF
TOS II_RFI_3_Amend_01_ATCH 1_Map to GLC.pdf PDF
TOS II_RFI_3_Amend_01_Final.pdf PDF
TOS II_RFI_3_ATCH 1_H115 Organizational Conflicts of Interest DRAFT.pdf PDF
TOS II_RFI_3_ATCH 2_H050 Rights in Information and Data Clause DRAFT.pdf PDF
TOS II_RFI_3_ATCH 3_TOS II PWS_26OCT22_DRAFT.pdf PDF
TOS II_RFI_3_Final.pdf PDF
TOS II_RFI_2_Amend_02_Final.pdf PDF
TOS II_RFI_2_Amend_01_Final.pdf PDF
TOS II_RFI_2_Amend_01_ATCH 1_Industry Day 2 Registration.xlsx XLSX spreadsheet
TOS II_RFI_2_Final.pdf PDF
TOS II_RFI_2_ATCH 1_Draft Industry Day 2 Agenda.pdf PDF
TOS II_RFI_1_Amendment_02.pdf PDF
FA910122RB001_Industry Day 1 Questions.xlsx XLSX spreadsheet
TOS II_RFI_1_Amendment_01.pdf PDF
TOS II_RFI_1_Final.pdf PDF
TOS II_RFI_1_ATCH 1_PWS_FA9101-13-0100.pdf PDF
Show all 50

Test Operations and Sustainment (TOS) II has more files on GovTribe.

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

H115 ORGANIZATIONAL CONFLICTS OF INTEREST (MAY 2014)

(a) The purpose of this clause is to ensure that:

(1) In providing services to the Government and its customers under this contract, the Contractor's objectivity and judgment are not biased because of its present, or future, financial, contractual, organizational, or other interests;

(2) The Contractor does not obtain an unfair competitive advantage by virtue of its access to non-public Government information regarding the Government's program plans and resources;

(3) The Contractor does not obtain any unfair competitive advantage by virtue of its access to proprietary or competition sensitive information belonging to others;

(4) The Contractor ensures no bias or unfair competitive advantage exists while aggressively addressing any perception issue that may arise; and

(5) The contract complies with Section 207 of the Weapon Systems Acquisition Reform

Act of 2009, Pub. L. No. 111-23 (May 22, 2009).

(b) Definitions for purposes of this clause:

(1) "Contractor" means the business entity receiving the award of this contract, as well as its parents, affiliates, divisions, subsidiaries and successor entities. The term "affiliates" is defined in FAR 2.101 and 19.101. The term "contractor" includes the firm, or firms, who were required to sign the contract document (see FAR 4.102). The term contractor also includes participants in any formal contractor team arrangement as defined in FAR 9.601. Examples of formal contractor team arrangements include, but are not limited to, partnerships, joint ventures, and alliances. Finally, the term "contractor" includes the contractor's subcontractors who

(i) Operate AEDC test and evaluation facilities, or

(ii) Handle, receive, reduce, interpret, or transmit data obtained, utilized, or produced in conjunction with testing and evaluation or analysis.

(2) "Development" means all efforts taken toward the solution of broadly-defined problems. Development may encompass research, evaluating technical feasibility, proof of design and test, or engineering of programs not yet approved for acquisition or operation.

(3) "Organizational conflict of interest," or "OCI," means that a relationship or situation exists where an offeror or Contractor (including chief executives and directors, to the extent that they will or do become involved in the performance of the contract, and proposed consultants or

Attachment 2 subcontractors where they may be performing services similar to the services provided by the prime) has past, present, or currently planned interests that may directly or indirectly relate to the work to be performed under a Department of Defense contract which

(i) May diminish its capacity to give impartial, technically sound, and objective assistance and advice, or

(ii) May result in it having an unfair competitive advantage. OCI does not include the normal flow of benefits from the performance of the contract.

(4) "OCI mitigation plan" means the formal written description of the actions the Contractor has agreed to take to mitigate an OCI. The Government is responsible for approval and enforcement of the Contractor's plan. While implementation of the mitigation plan rests largely with the Contractor, the Government bears responsibility for ensuring the plan is properly implemented.

(5) "Proprietary information" means all information designated as proprietary in accordance with law and regulation, and held in confidence or disclosed under restriction to prevent uncontrolled distribution and unauthorized use. Examples include, but are not limited to, marked information, information submitted in confidence to the Government, limited or restricted data, trade secrets, sensitive financial information, and computer software. Proprietary information may also appear in cost and pricing data or involve classified information. Refer to FAR 3.104-1 for the definition of contractor bid and proposal information requiring protection.

Refer to FAR 3.104-4 for disclosure, protection, and marking of contractor bid or proposal information and source selection information.

(i) Proprietary information shall not include information which

(A) Was known to the contractor prior to its receipt from a company or the Government,

(B) Was independently developed by the contractor without access to a company's proprietary data,

(C) Is or becomes public knowledge without the fault of the Contractor,

(D) Has been lawfully obtained by the contractor without restrictions on disclosure from a source other than a company or the Government, or

(E) Is or becomes available to a third party from a company on an unrestricted basis.

(ii) Other limitations set forth in this contract may apply to the use of information and data. The burden of proof as to the applicability of any of the exceptions described in paragraph (b)(5)(i) shall rest on the contractor.

(6) "System" means a combination of two or more interrelated pieces of equipment (or sets) arranged in a functional package to perform an operational function or to satisfy a requirement. A system can include a grouping of hardware, software, and materials to perform a designated function with specified results. A "major subsystem" means a functional grouping of components that combine to perform a key function within an element such as electrical power, attitude control, sensor imaging, and propulsion. "Component" means any sub-part of a system or major subsystem that performs a specific function, but is not capable of executing the primary function of the system or major subsystem independent of other components.

Systems and major subsystems include, but are not limited to, aircraft, missiles, bombs or other weapons, air-breathing engines, liquid and solid propellant rockets, rocket motors, spacecraft, reentry vehicles, satellite mission payloads, solar arrays, and power generating systems.

Components include, but are not limited to, electrical harnesses, star trackers, gyroscopes, line replaceable units, linkages, integrated circuits, and bolts.

(c) Except to the extent required in the performance of this contract according to its terms, the Contractor shall not, during the performance of the contract and for a period of three (3) years following completion of performance thereof, engage as a prime contractor (or subcontractor without an approved OCI mitigation plan) in any design, development, or production of aerospace systems or major subsystems of a type normally developed, tested, or evaluated in AEDC facilities, or facilities similar to AEDC facilities. The Contractor also shall not engage in studies or act as a consultant in those regards during the foregoing timeframe. These restrictions do not apply to prime contracts or subcontracts for components.

(d) The Contractor may gain access to proprietary information of other companies during contract performance. When the Contractor has access to the proprietary information of other companies, the Contractor must enter into a company-to-company agreement to:

(1) Protect another company's information from unauthorized use or disclosure; and

(2) To refrain from using the information for any purpose other than that for which it was furnished. The Contractor shall furnish these agreements to the Contracting Officer for review and approval. The Contractor is not permitted to use the proprietary information obtained in performing this contract for any other purpose without the prior approval of the Contracting Officer.

(e) The Contractor shall comply with all restrictions described in FAR 9.505. The Contractor must also thoroughly inculcate in its employees, through formal training in company policies and procedures, an awareness of the philosophy of both this clause and FAR Subpart 9.5. All employees shall be educated in and formally acknowledge the absolute necessity of refraining from divulging proprietary information from other companies received in connection with work under this contract to any unauthorized person.

(f) The Contractor shall require its employees to sign written agreements prohibiting proprietary information disclosure except in accordance with a Government-approved plan. This written agreement shall in substance provide that such employee will not, during their employment by the contractor or thereafter, disclose to others or use for their own behalf, proprietary information from other companies received in connection with the work under this contract. The agreement shall acknowledge the employee is trained regarding handling proprietary information and discuss penalties for violations.

(g) If the Contractor discovers an actual or potential OCI not previously considered and adequately mitigated under this clause and a Government-approved OCI mitigation plan, the contractor shall make a prompt and full disclosure in writing to the Contracting Officer. This disclosure shall include a description of the action the Contractor has taken or proposes to take, or actions recommended to be taken by the Government, in order to avoid, neutralize, or mitigate the conflict.

(h) The contractor shall report any violation or suspected violation of this clause or a Government-approved OCI mitigation plan, whether by its own personnel or those of its subcontractors, to the Contracting Officer. This report shall include a description of the violation and the actions the contractor has taken or proposes to take to mitigate and avoid repetition of the violation. The Contractor shall routinely monitor its proposed business development and shall discuss any real or perceived OCI issues with the Contracting Officer and affected AEDC customers to proactively resolve and / or mitigate potential OCI issues. After conducting any necessary discussions, the Contracting Officer and the Contractor shall agree on appropriate corrective action, if any, or the Contracting Officer shall direct such action, subject to the terms of this contract.

(i) OCI violations are a significant contract performance issue. Violations of an OCI mitigation plan or this clause may have consequences such as award fee decrements, contract termination, suspension and debarment, or other appropriate remedies or administrative actions.

(j) The Contractor may propose changes to an approved OCI mitigation plan. Such changes are subject to the mutual agreement of the parties and will become effective only upon incorporation by contract modification or written approval of the revised plan by the Contracting Officer.

(k) The Government shall require proper checks and balances in contract performance and minimization of the potential conflicts of interest between the Test Operations and Sustainment (TOS) and Test Services advisory and assistance services (A&AS) efforts. Therefore, a company cannot be a Contractor on the TOS contract and perform work at AEDC under the Test Services A&AS contract.

(l) For all other AEDC support contracts, the Government realizes the potential exists for actual or perceived OCIs to develop if the same Contractor performs work on both the TOS contract and another AEDC contract. To alleviate these concerns, a Contractor performing work in any role on the TOS contract must have an approved mitigation plan prior to performing any work on any other AEDC contract.

(m) The Contractor shall include paragraphs (a) through (l) of this clause in every subcontract, purchase order, or other agreement. Exceptions must be approved in writing by the Contracting Officer.

File details come from the government source that posted it. Updated .