Attch_3_-_Provisions_and_Clauses.pdf

Section I - Contract Clauses

CLAUSES INCORPORATED BY REFERENCE

52.204-19 Incorporation by Reference of Representations and Certifications.

DEC 2014

52.216-8 Fixed Fee JUN 2011 52.232-20 Limitation Of Cost APR 1984 52.232-22 Limitation Of Funds APR 1984 52.245-1 Government Property APR 2012 252.201-7000 Contracting Officer's Representative DEC 1991 252.203-7000 Requirements Relating to Compensation of Former DoD SEP 2011 Officials 252.203-7001 Prohibition On Persons Convicted of Fraud or Other Defense- DEC 2008 Contract-Related Felonies 252.203-7002 Requirement to Inform Employees of Whistleblower Rights SEP 2013 252.204-7000 Disclosure Of Information AUG 2013 252.204-7003 Control Of Government Personnel Work Product APR 1992 252.204-7005 Oral Attestation of Security Responsibilities NOV 2001 252.204-7006 Billing Instructions OCT 2005 252.204-7015 Disclosure of Information to Litigation Support Contractors FEB 2014 252.209-7004 Subcontracting With Firms That Are Owned or Controlled By DEC 2014 The Government of a Country that is a State Sponsor of Terrorism 252.211-7007 Reporting of Government-Furnished Property AUG 2012 252.223-7004 Drug Free Work Force SEP 1988 252.225-7048 Export-Controlled Items JUN 2013 252.231-7000 Supplemental Cost Principles DEC 1991 252.232-7003 Electronic Submission of Payment Requests and Receiving JUN 2012 Reports 252.232-7010 Levies on Contract Payments DEC 2006 252.237-7010 Prohibition on Interrogation of Detainees by Contractor JUN 2013 Personnel 252.239-7001 Information Assurance Contractor Training and Certification JAN 2008 252.242-7006 Accounting System Administration FEB 2012 252.245-7000 Government-Furnished Mapping, Charting, and Geodesy APR 2012 Property 252.245-7001 Tagging, Labeling, and Marking of Government-Furnished APR 2012 Property 252.245-7002 Reporting Loss of Government Property APR 2012 252.245-7003 Contractor Property Management System Administration APR 2012 252.245-7004 Reporting, Reutilization, and Disposal MAR 2015

CLAUSES INCORPORATED BY FULL TEXT

52.217-8 OPTION TO EXTEND SERVICES (NOV 1999)

The Government may require continued performance of any services within the limits and at the rates specified in the contract. These rates may be adjusted only as a result of revisions to prevailing labor rates provided by the Secretary of Labor. The option provision may be exercised more than once, but the total extension of performance hereunder shall not exceed 6 months. The Contracting Officer may exercise the option by written notice to the Contractor within fifteen (15) days prior to the expiration of the contract period.

(End of clause)

52.217-9 OPTION TO EXTEND THE TERM OF THE CONTRACT (MAR 2000)

(a) The Government may extend the term of this contract by written notice to the Contractor within five (5) days prior to the expiration of the contract period; provided that the Government gives the Contractor a preliminary written notice of its intent to extend at least fifteen (15) days before the task order expires. The preliminary notice does not commit the Government to an extension.

(b) If the Government exercises this option, the extended contract shall be considered to include this option clause.

(c) The total duration of this contract, including the exercise of any options under this clause, shall not exceed five (5) years from start of performance on the contract.

252.203-7999 PROHIBITION ON CONTRACTING WITH ENTITIES THAT REQUIRE CERTAIN INTERNAL CONFIDENTIALITY

AGREEMENTS (DEVIATION 2015-O0010)(FEB 2015)

(a) The Contractor shall not require employees or subcontractors seeking to report fraud, waste, or abuse to sign or comply with internal confidentiality agreements or statements prohibiting or otherwise restricting such employees or contactors from lawfully reporting such waste, fraud, or abuse to a designated investigative or law enforcement representative of a Federal department or agency authorized to receive such information.

(b) The Contractor shall notify employees that the prohibitions and restrictions of any internal confidentiality agreements covered by this clause are no longer in effect. (c) The prohibition in paragraph (a) of this clause does not contravene requirements applicable to Standard Form 312, Form 4414, or any other form issued by a Federal department or agency governing the nondisclosure of classified information.

(d)(1) In accordance with section 743 of Division E, Title VIII, of the Consolidated and Further Continuing Resolution Appropriations Act, 2015, (Pub. L. 113-235), use of funds appropriated (or otherwise made available) under that or any other Act may be prohibited, if the Government determines that the Contractor is not in compliance with the provisions of this clause.

(2) The Government may seek any available remedies in the event the Contractor fails to perform in accordance with the terms and conditions of the contract as a result of Government action under this clause.

252.204-7012 SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT REPORTING (AUG 2015)

(a) Definitions. As used in this clause--

Adequate security means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information.

Compromise means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred.

Contractor attributional/proprietary information means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company.

Contractor information system means an information system belonging to, or operated by or for, the Contractor.

Controlled technical information means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination.

Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements on Technical Documents. The term does not include information that is lawfully publicly available without restrictions.

Covered contractor information system means an information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information.

Covered defense information means unclassified information that--

(i) Is--

(A) Provided to the contractor by or on behalf of DoD in connection with the performance of the contract; or

(B) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract; and

(ii) Falls in any of the following categories:

(A) Controlled technical information.

(B) Critical information (operations security). Specific facts identified through the Operations Security process about friendly intentions, capabilities, and activities vitally needed by adversaries for them to plan and act effectively so as to guarantee failure or unacceptable consequences for friendly mission accomplishment (part of Operations Security process).

(C) Export control. Unclassified information concerning certain items, commodities, technology, software, or other information whose export could reasonably be expected to adversely affect the United States national security and nonproliferation objectives. To include dual use items; items identified in export administration regulations, international traffic in arms regulations and munitions list; license applications; and sensitive nuclear technology information.

(D) Any other information, marked or otherwise identified in the contract, that requires safeguarding or disseminationcontrols pursuant to and consistent with law, regulations, and Governmentwide policies (e.g., privacy, proprietary business information).

Cyber incident means actions taken through the use of computer networks that result in an actual or potentially adverse effect on an information system and/or the information residing therein.

Forensic analysis means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data.

Malicious software means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware.

Media means physical devices or writing surfaces including, but is not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which information is recorded, stored, or printed within an information system.

Operationally critical support means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation.

Rapid(ly) report(ing) means within 72 hours of discovery of any cyber incident.

Technical information means technical data or computer software, as those terms are defined in the clause at DFARS 252.227-7013, Rights in Technical Data-Non Commercial Items, regardless of whether or not the clause is incorporated in this solicitation or contract. Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code.

(b) Adequate security. The Contractor shall provide adequate security for all covered defense information on all covered contractor information systems that support the performance of work under this contract. To provide adequate security, the Contractor shall--

(1) Implement information systems security protections on all covered contractor information systems including, at a minimum--

(i) For covered contractor information systems that are part of an Information Technology (IT) service or system operated on behalf of the Government--

(A) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010, Cloud Computing Services, of this contract; and

(B) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract; or

(ii) For covered contractor information systems that are not part of an IT service of system operated on behalf of the

Government and therefore are not subject to the security requirement specified at paragraph (b)(1)(i) of this clause--

(A) The security requirements in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, ``Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations, http://dx.doi.org/10.6028/NIST.SP.800-171 that is in effect at the time the solicitation is issued or as authorized by the Contracting Officer; or

(B) Alternative but equally effective security measures used to compensate for the inability to satisfy a particular requirement and achieve equivalent protection approved in writing by an authorized representative of the DoD CIO prior to contract award; and

(2) Apply other security measures when the Contractor reasonably determines that such measures, in addition to those identified in paragraph (b)(1) of this clause, may be required to provide adequate security in a dynamic environment based on an assessed risk or vulnerability.

(c) Cyber incident reporting requirement.

(1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor's ability to perform the requirements of the contract that are designated as operationally critical support, the Contractor shall--

(i) Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts. This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other information systems on the Contractor's network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the Contractor's ability to provide operationally critical support; and

(ii) Rapidly report cyber incidents to DoD at http://dibnet.dod.mil.

(2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at http://dibnet.dod.mil.

(3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see http://iase.disa.mil/pki/eca/certificate.html.

http://dx.doi.org/10.6028/NIST.SP.800-171 http://dibnet.dod.mil/ http://dibnet.dod.mil/ http://iase.disa.mil/pki/eca/certificate.html

(d) Malicious software. The Contractor or subcontractors that discover and isolate malicious software in connection with a reported cyber incident shall submit the malicious software in accordance with instructions provided by the

Contracting Officer.

(e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest.

(f) Access to additional information or equipment necessary for forensic analysis. Upon request by DoD, the

Contractor shall provide DoD with access to additional information or equipment that is necessary to conduct a forensic analysis.

(g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause.

(h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released.

(i) Use and release of contractor attributional/proprietary information not created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD--

(1) To entities with missions that may be affected by such information;

(2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents;

(3) To Government entities that conduct counterintelligence or law enforcement investigations;

(4) For national security purposes, including cyber situational awareness and defense purposes (including with Defense Industrial Base (DIB) participants in the program at 32CFR 236); or

(5) To a support services contractor (``recipient'') that is directly supporting Government activities under a contract that includes the clause at 252.204-7009, Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information.

(j) Use and release of contractor attributional/proprietary information created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph (c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph (i) of this clause, and for any other lawful Government purpose or activity, subject to all applicable statutory, regulatory, and policy based restrictions on the Government's use and release of such information.

(k) The Contractor shall conduct activities under this clause in accordance with applicable laws and regulations on the interception, monitoring, access, use, and disclosure of electronic communications and data.

(l) Other safeguarding or reporting requirements. The safeguarding and cyber incident reporting required by this clause in no way abrogates the Contractor's responsibility for other safeguarding or cyber incident reporting pertaining to its unclassified information systems as required by other applicable clauses of this contract, or as a result of other applicable U.S. Government statutory or regulatory requirements.

(m) Subcontracts. The Contractor shall--

(1) Include the substance of this clause, including this paragraph (m), in all subcontracts, including subcontracts for commercial items; and

(2) Require subcontractors to rapidly report cyber incidents directly to DoD at http://dibnet.dod.mil and the prime

Contractor. This includes providing the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable.

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (MAY 2013)

(a) Definitions. As used in this clause--

Department of Defense Activity Address Code (DoDAAC) is a six position code that uniquely identifies a unit, activity, or organization.

Document type means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

Local processing office (LPO) is the office responsible for payment certification when payment certification is done external to the entitlement system.

(b) Electronic invoicing. The WAWF system is the method to electronically process vendor payment requests and receiving reports, as authorized by DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(c) WAWF access. To access WAWF, the Contractor shall--

(1) Have a designated electronic business point of contact in the System for Award Management at https://www.acquisition.gov; and http://dibnet.dod.mil/

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this Web site.

(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training

Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the “Web Based Training” link on the WAWF home page at https://wawf.eb.mil/.

(e) WAWF methods of document submission. Document submissions may be via Web entry, Electronic Data Interchange, or File Transfer Protocol.

(f) WAWF payment instructions. The Contractor must use the following information when submitting payment requests and receiving reports in WAWF for this contract/order:

(1) Document type. The Contractor shall use the following document type(s).

Invoice

(Contracting Officer: Insert applicable document type(s). Note: If a “Combo” document type is identified but not supportable by the Contractor's business systems, an “Invoice” (stand-alone) and “Receiving Report” (stand-alone) document type may be used instead.)

(2) Inspection/acceptance location. The Contractor shall select the following inspection/acceptance location(s) in WAWF, as specified by the contracting officer.

F3LFF6

(Contracting Officer: Insert inspection and acceptance locations or “Not applicable”.)

(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.

Routing Data Table* Field Name in WAWF Data to be entered in WAWF Pay Official DoDAAC F03000 Issue By DoDAAC FA2543 Admin DoDAAC FA2543 Inspect By DoDAAC F3LFF6 Ship To Code N/A Ship From Code N/A Mark For Code N/A

Service Approver (DoDAAC) F3LFF6 Service Acceptor (DoDAAC) F3LFF6 Accept at Other DoDAAC N/A LPO DoDAAC N/A DCAA Auditor DoDAAC N/A Other DoDAAC(s) N/A

(*Contracting Officer: Insert applicable DoDAAC information or “See schedule” if multiple ship to/acceptance locations apply, or “Not applicable.”)

(4) Payment request and supporting documentation. The Contractor shall ensure a payment request includes appropriate contract line item and subline item descriptions of the work performed or supplies delivered, unit price/cost per unit, fee (if applicable), and all relevant back-up documentation, as defined in DFARS Appendix F, (e.g. timesheets) in support of each payment request.

(5) WAWF email notifications. The Contractor shall enter the email address identified below in the “Send

Additional Email Notifications” field of WAWF once a document is submitted in the system.

lee.cornelius.2@us.af.mil

21CONS.LGCCB.OASIS@us.af.mil

(g) WAWF point of contact. (1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity's WAWF point of contact.

lee.cornelius.2@us.af.mil

(2) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988.

252.251-7000 ORDERING FROM GOVERNMENT SUPPLY SOURCES (AUG 2012)

(a) When placing orders under Federal Supply Schedules, Personal Property Rehabilitation Price Schedules, or Enterprise Software Agreements, the Contractor shall follow the terms of the applicable schedule or agreement and authorization. Include in each order:

(1) A copy of the authorization (unless a copy was previously furnished to the Federal Supply Schedule, Personal

Property Rehabilitation Price Schedule, or Enterprise Software Agreement contractor).

mailto:lee.cornelius.2@us.af.mil mailto:21CONS.LGCCB.OASIS@us.af.mil mailto:lee.cornelius.2@us.af.mil

(2) The following statement: Any price reductions negotiated as part of an Enterprise Software Agreement issued under a Federal Supply Schedule contract shall control. In the event of any other inconsistencies between an Enterprise Software Agreement, established as a Federal Supply Schedule blanket purchase agreement, and the Federal Supply Schedule contract, the latter shall govern.

(3) The completed address(es) to which the Contractor's mail, freight, and billing documents are to be directed.

(b) When placing orders under nonmandatory schedule contracts and requirements contracts, issued by the General Services Administration (GSA) Office of Information Resources Management, for automated data processing equipment, software and maintenance, communications equipment and supplies, and teleprocessing services, the Contractor shall follow the terms of the applicable contract and the procedures in paragraph (a) of this clause.

(c) When placing orders for Government stock on a reimbursable basis, the Contractor shall--

(1) Comply with the requirements of the Contracting Officer's authorization, using FEDSTRIP or MILSTRIP procedures, as appropriate;

(2) Use only the GSA Form 1948-A, Retail Services Shopping Plate, when ordering from GSA Self-Service Stores;

(3) Order only those items required in the performance of Government contracts; and

(4) Pay invoices from Government supply sources promptly. For purchases made from DoD supply sources, this means within 30 days of the date of a proper invoice (see also Defense Federal Acquisition Regulation Supplement (DFARS) 251.105). For purchases made from DoD supply sources, this means within 30 days of the date of a proper invoice. The Contractor shall annotate each invoice with the date of receipt. The Contractor's failure to pay may also result in the DoD supply source refusing to honor the requisition (see DFARS 251.102(f)) or in the Contracting Officer terminating the Contractor's authorization to use DoD supply sources. In the event the Contracting Officer decides to terminate the authorization due to the Contractor's failure to pay in a timely manner, the Contracting Officer shall provide the Contractor with prompt written notice of the intent to terminate the authorization and the basis for such action. The Contractor shall have 10 days after receipt of the Government's notice in which to provide additional information as to why the authorization should not be terminated. The termination shall not provide the Contractor with an excusable delay for failure to perform or complete the contract in accordance with the terms of the contract, and the Contractor shall be solely responsible for any increased costs.

(d) When placing orders for Government stock on a non-reimbursable basis, the Contractor shall—

(1) Comply with the requirements of the Contracting Officer's authorization; and

(2) When using electronic transactions to submit requisitions on a non-reimbursable basis only, place orders by authorizing contract number using the Defense Logistics Management System (DLMS) Supplement to Federal Implementation Convention 511R, Requisition; and acknowledge receipts by authorizing contract number using the DLMS Supplement 527R, Receipt, Inquiry, Response and Material Receipt Acknowledgement.

(e) Only the Contractor may request authorization for subcontractor use of Government supply sources. The Contracting Officer will not grant authorizations for subcontractor use without approval of the Contractor.

(f) Government invoices shall be submitted to the Contractor's billing address, and Contractor payments shall be sent to the Government remittance address specified below:

Contractor's Billing Address: see Block 9 of the DD Form 1155.

Government Remittance Address: see Block 14 of the DD Form 1155.

5352.204-9000 NOTIFICATION OF GOVERNMENT SECURITY ACTIVITY AND VISITOR GROUP

SECURITY AGREEMENTS (MAR 2012)

This contract contains a DD Form 254, DOD Contract Security Classification Specification, and requires performance at a government location in the U.S. or overseas. Prior to beginning operations involving classified information on an installation identified on the DD Form 254, the contractor shall take the following actions:

(a) At least thirty days prior to beginning operations, notify the Information Protection Office shown in the distribution block of the DD Form 254 as to:

(1) The name, address, and telephone number of this contract company’s representative and designated alternate in the U.S. or overseas area, as appropriate;

(2) The contract number and military contracting command;

(3) The highest classification category of defense information to which contractor employees will have access;

(4) The Air Force installations in the U.S. (in overseas areas, identify only the APO number(s)) where the contract work will be performed;

(5) The date contractor operations will begin on base in the U.S. or in the overseas area;

(6) The estimated completion date of operations on base in the U.S. or in the overseas area; and

(7) Any changes to information previously provided under this clause.

This requirement is in addition to visit request procedures contained in DOD 5220.22-M, National Industrial Security Program Operating Manual.

(b) Prior to beginning operations involving classified information on an installation identified on the DD Form 254 where the contractor is not required to have a facility security clearance, the contractor shall enter into a Visitor Group Security Agreement (or understanding) with the installation commander to ensure that the contractor’s security procedures are properly integrated with those of the installation. As a minimum, the agreement shall identify the security actions that will be performed:

(1) By the installation for the contractor, such as providing storage and classified reproduction facilities, guard services, security forms, security inspections under DOD 5220.22-M, classified mail services, security badges, visitor control, and investigating security incidents; and

(2) Jointly by the contractor and the installation, such as packaging and addressing classified transmittals, security checks, internal security controls, and implementing emergency procedures to protect classified material.

5352.209-9000 ORGANIZATIONAL CONFLICT OF INTEREST (OCT 2010)

(a) The following restrictions and definitions apply to prevent conflicting roles which may bias the Contractor's judgment or objectivity, or to preclude the Contractor from obtaining an unfair competitive advantage in concurrent or future acquisitions.

(1) Descriptions or definitions:

"Contractor" means the business entity receiving the award of this contract, its parents, affiliates, divisions and subsidiaries.

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

"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. Examples include limited or restricted data, trade secrets, sensitive financial information, and computer software; and may appear in cost and pricing data or involve classified information.

"System" means the system that is the subject of this contract.

"System Life" means all phases of the system's development, production, or support.

"Systems Engineering" means preparing specifications, identifying and resolving interface problems, developing test requirements, evaluating test data, and supervising design.

"Technical Direction" means developing work statements, determining parameters, directing other Contractors' operations, or resolving technical controversies.

(2) Restrictions: The Contractor shall perform systems engineering and/or technical direction, but will not have overall contractual responsibility for the system's development, integration, assembly and checkout, or production. The parties recognize that the Contractor shall occupy a highly influential and responsible position in determining the system's basic concepts and supervising their execution by other Contractors. The Contractor's judgment and recommendations must be objective, impartial, and independent. To avoid the prospect of the Contractor's judgment or recommendations being influenced by its own products or capabilities, it is agreed that the Contractor is precluded for the life of the system from award of a DoD contract to supply the system or any of its major components, and from acting as a subcontractor or consultant to a DoD supplier for the system or any of its major components.

5352.223-9001 HEALTH AND SAFETY ON GOVERNMENT INSTALLATIONS (NOV 2012)

(a) In performing work under this contract on a Government installation, the contractor shall:

(1) Take all reasonable steps and precautions to prevent accidents and preserve the health and safety of contractor and Government personnel performing or in any way coming in contact with the performance of this contract; and

(2) Take such additional immediate precautions as the contracting officer may reasonably require for health and safety purposes.

(b) The contracting officer may, by written order, direct Air Force Occupational Safety and Health (AFOSH) Standards and/or health/safety standards as may be required in the performance of this contract and any adjustments resulting from such direction will be in accordance with the Changes clause of this contract.

(c) Any violation of these health and safety rules and requirements, unless promptly corrected as directed by the contracting officer, shall be grounds for termination of this contract in accordance with the Default clause of this contract.

5352.242-9000 CONTRACTOR ACCESS TO AIR FORCE INSTALLATIONS (Nov 2012)

(a) The contractor shall obtain base identification and vehicle passes, if required, for all contractor personnel who make frequent visits to or perform work on the Air Force installation(s) cited in the contract. Contractor personnel are required to wear or prominently display installation identification badges or contractor-furnished, contractor identification badges while visiting or performing work on the installation.

(b) The contractor shall submit a written request on company letterhead to the contracting officer listing the following: contract number, location of work site, start and stop dates, and names of employees and subcontractor employees needing access to the base. The letter will also specify the individual(s) authorized to sign for a request for base identification credentials or vehicle passes. The contracting officer will endorse the request and forward it to the issuing base pass and registration office or Security Forces for processing. When reporting to the registration office, the authorized contractor individual(s) should provide a valid driver’s license, current vehicle registration, valid vehicle insurance certificate, and Full Name, US Citizenship Status, Date of Birth, and Social Security Number to obtain a vehicle pass.

(c) During performance of the contract, the contractor shall be responsible for obtaining required identification for newly assigned personnel and for prompt return of credentials and vehicle passes for any employee who no longer requires access to the work site.

(d) When work under this contract requires unescorted entry to controlled or restricted areas, the contractor shall comply with AFI 31-101, Volume 1, The Air Force Installation Security Program, and AFI 31-501, Personnel Security Program Management citing the appropriate paragraphs as applicable.

(e) Upon completion or termination of the contract or expiration of the identification passes, the prime contractor shall ensure that all base identification passes issued to employees and subcontractor employees are returned to the issuing office.

(f) Failure to comply with these requirements may result in withholding of final payment.

5352.242-9001 COMMON ACCESS CARDS (CACs) FOR CONTRACTOR PERSONNEL (NOV 2012)

(a) For installation(s)/location(s) cited in the contract, contractors shall ensure Common Access Cards (CACs) are obtained by all contract or subcontract personnel who meet one or both of the following criteria:

(1) Require logical access to Department of Defense computer networks and systems in either:

(i) the unclassified environment; or

(ii) the classified environment where authorized by governing security directives.

(2) Perform work which requires the use of a CAC for installation entry control or physical access to facilities and buildings.

(b) Contractors and their personnel shall use the following procedures to obtain CACs:

(1) Contractors shall provide a listing of personnel who require a CAC to the contracting officer. The government will provide the contractor instruction on how to complete the Contractor Verification System (CVS) application and then notify the contractor when approved.

(2) Contractor personnel shall obtain a CAC from the nearest Real Time Automated Personnel Identification Documentation System (RAPIDS) Issuing Facility (typically the local Military Personnel Flight (MPF)).

(c) While visiting or performing work on installation(s)/location(s), contractor personnel shall wear or prominently display the CAC as required by the governing local policy.

(d) During the performance period of the contract, the contractor shall:

(1) Within 7 working days of any changes to the listing of the contract personnel authorized a CAC, provide an up-dated listing to the contracting officer who will provide the updated listing to the authorizing government official;

(2) Return CACs in accordance with local policy/directives within 7 working days of a change in status for contrac-tor personnel who no longer require logical or physical access;

(3) Return CACs in accordance with local policy/directives within 7 working days following a CACs expiration date; and

(4) Report lost or stolen CACs in accordance with local policy/directives.

(e) Within 7 working days following completion/termination of the contract, the contractor shall return all CACs issued to their personnel to the issuing office or the location specified by local policy/directives.

(f) Failure to comply with these requirements may result in withholding of final payment.