FA8650-18-S-1672-Atch1.pdf

PDF 5 MB Posted

Attached to
Precision Real-Time Engagement Combat Identification Sensor Exploitation (PRECISE) Federal contract opportunity
Solicitation number
FA8650-18-S-1672
Issued by
Department of the Air Force Materiel Command Research Laboratory

About this file

Model Contract

View the file

Other files for this federal contract opportunity

Other files attached to Precision Real-Time Engagement Combat Identification Sensor Exploitation (PRECISE), newest first.
File Type Posted
FA8650-18-S-1672-BAA.pdf PDF
FA8650-18-S-1672-NOCA.pdf PDF

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

SOLICITATION, OFFER AND AWARD

1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 350)

RATING

DO-A7

PAGE OF PAGES

1 26

2. CONTRACT NO. 3. SOLICITATION NO. 4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

5. DATE ISSUED

21 MAR 2018

6. REQUISITION/PURCHASE NO.

FA8650-18-R-1672

7. ISSUED BY AFRL/RQKSR CODE FA8650 8. ADDRESS OFFER TO (If other than Item 7)

USAF/AFMC

AFRL WRIGHT RESEARCH SITE

2130 EIGHTH STREET, BUILDING 45

WRIGHT-PATTERSON AFB OH 45433-7541

BRYAN FLECKENSTEIN 937 713 9982

BRYAN.FLECKENSTEIN@US.AF.MIL

NOTE: In sealed bid solicitations “offer” and “offeror” mean “bid” and “bidder”.

SOLICITATION

9. Broad Agency Announcement (BAA) for PRECISION REAL-TIME ENGAGEMENT COMBAT IDENTIFICATION SENSOR EXPLOITATION (PRECISE)

10. FOR

INFORMATION

CALL:

A. NAME

BARRY E. KAIN

B. TELEPHONE (Include area code)

(NO COLLECT CALLS)

(937)713-9986

C. E-MAIL ADDRESS

barry.kain@us.af.mil

11. TABLE OF CONTENTS

() SEC. DESCRIPTION PAGE(S) () SEC DESCRIPTION PAGE(S)

PART I - THE SCHEDULE PART II - CONTRACT CLAUSES

A SOLICITATION/CONTRACT FORM 1 I CONTRACT CLAUSES 13

B SUPPLIES OR SERVICES AND PRICES/COSTS 2 PART III - LIST OF DOCUMENTS, EXHIBITS, AND OTHER ATTACH.

C DESCRIPTION/SPECS./WORK STATEMENT 5 J LIST OF ATTACHMENTS 26

D PACKAGING AND MARKING 6 PART IV - REPRESENTATIONS AND INSTRUCTIONS

E INSPECTION AND ACCEPTANCE 7 K REPRESENTATIONS, CERTIFICATIONS, K - 1

F DELIVERIES OR PERFORMANCE 8 AND OTHER STATEMENTS OF OFFERORS

G CONTRACT ADMINISTRATION DATA 10 L INSTRS, CONDS, AND NOTICES TO OFFERORS L - 1

H SPECIAL CONTRACT REQUIREMENTS 12 M EVALUATION FACTORS FOR AWARD M - 1

OFFER (Must be fully completed by offeror) NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

12. In compliance with the above, the undersigned agrees, if this offer is accepted within ____ ____ calendar days (60 calendar days unless a different period is inserted by the offeror) from the date of receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

10 CALENDAR DAYS

20 CALENDAR DAYS

30 CALENDAR DAYS

CALENDAR DAYS

14. ACKNOWLEDGEMENTS OF AMENDMENTS

(The offeror acknowledges receipt of amend-

AMENDMENT NO. DATE AMENDMENT NO. DATE

ments to the SOLICITATION for offerors and related documents numbered and dated:

15A. NAME

AND

CODE FACILITY 16. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN

OFFER (Type or print)

ADDRESS

OF

OFFEROR

15B. TELEPHONE NO. (Include area code)

15C. CHECK IF REMITTANCE ADDRESS

IS DIFFERENT FROM ABOVE - ENTER

SUCH ADDRESS IN SCHEDULE.

17. SIGNATURE 18. OFFER DATE

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETI-

TION: 23. SUBMIT INVOICES TO ADDRESS SHOWN IN

(4 copies unless otherwise specified)

ITEM

10 U.S.C. 2304(c) ( ) 41 U.S.C. 253(c) ( )

24. ADMINISTERED BY (If other than Item 7) CODE 25. PAYMENT WILL BE MADE BY CODE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

28. AWARD DATE

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

AUTHORIZED FOR LOCAL REPRODUCTION STANDARD FORM 33 (REV. 9-97)

PREVIOUS EDITION IS UNUSABLE Prescribed by GSA ConWrite Version 6.15.4 FAR (48 CFR) 53.21(c) Created 20 Mar 2018 2:29 PM

PART I - THE SCHEDULE

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

SECTION B FA8650-18-R-1672

Qty Unit Price ITEM SUPPLIES OR SERVICES Purch Unit Total Item Amount

RESEARCH AND DATA

0001 1 __________ Each __________ Noun: RESEARCH AND DATA

PSC: AC63

NSN: U - Unknown DD1423 is Exhibit: A Contract type: U - COST PLUS FIXED FEE Inspection: DESTINATION Acceptance: DESTINATION

FOB: DESTINATION

Descriptive Data:

The contractor shall conduct research and development entitled "Precision Real-Time Engagement Combat Identification Sensor Exploitation (PRECISE)", in accordance with Statement of Work, dated XXXXXX, attached in Section J, Attachment 1. Deliver data in accordance with Exhibit A, Contract Data Requirements List, DD Form 1423, as attached in Section J.

The estimated cost and fixed amounts are shown below:

Cost: $ TBD Fee: $TBD

Pursuant to FAR 52.232-22, "Limitation of Funds" in Section I, the total amount available for payment and allotted to this contract for CLINs 0001-0003 is $TBD. It is estimated that this amount is sufficient to cover performance through TBD.

SOFTWARE

0002 1 __________ Each __________ Noun: SOFTWARE

PSC: AC63

NSN: N - Not Applicable Contract type: U - COST PLUS FIXED FEE Inspection: DESTINATION Acceptance: DESTINATION

FOB: DESTINATION

Descriptive Data:

The Contractor shall deliver software in accordance with Section J, Attachment 1, Statement of Work dated XXX. The contractor shall deliver any and all software developed and/or acquired via the course of this effort. Software deliverables include, but are not limited to the following: See SOO paragraph 4.1 for more information

Qty Unit Price ITEM SUPPLIES OR SERVICES Purch Unit Total Item Amount

HARDWARE

0003 1 __________ Each __________ Noun: HARDWARE

PSC: AC63

NSN: N - Not Applicable Contract type: U - COST PLUS FIXED FEE Inspection: DESTINATION Acceptance: DESTINATION

FOB: DESTINATION

Descriptive Data:

The Contractor shall deliver hardware in accordance with Section J, Attachment 1, Statement of Work dated XXX. The contractor shall deliver any and all hardware developed and/or acquired via the course of this effort. Hardware deliverables include, but are not limited to the following:

TBD

IAW Clause 252.211-7003, "Item Unique Identification and Valuation ", the contractor shall identify the unit acquisition cost for all deliverable end items for which item unique identification applies.

NO CLAUSES OR PROVISIONS IN THIS SECTION

SECTION C - DESCRIPTION/SPECS./WORK STATEMENT

SECTION C FA8650-18-R-1672

SECTION D - PACKAGING AND MARKING

SECTION D FA8650-18-R-1672

SECTION E - INSPECTION AND ACCEPTANCE

SECTION E FA8650-18-R-1672

NOTICE: The following contract clauses pertinent to this section are hereby incorporated by reference:

A. FEDERAL ACQUISITION REGULATION CONTRACT CLAUSES

52.246-09 INSPECTION OF RESEARCH AND DEVELOPMENT (SHORT FORM) (APR 1984)

B. DEFENSE FEDERAL ACQUISITION REGULATION SUPPLEMENT CONTRACT CLAUSES

252.246-7000 MATERIAL INSPECTION AND RECEIVING REPORT (MAR 2008)

SECTION F - DELIVERIES OR PERFORMANCE

SECTION F FA8650-18-R-1672

SHIP MARK TRANS

ITEM SUPPLIES SCHEDULE DATA QTY TO FOR PRI DATE

0001 1 F4FBBG F4FBBG 63 MARO

Noun: RESEARCH AND DATA Descriptive Data:

The scheduled delivery date for the approved final technical report is XXX. The technical effort shall be completed no later than XXX. The contractor shall deliver data in accordance with Exhibit A, Contract Data Requirements List (CDRL), DD Form 1423, dated 09 FEB 2018. Deliver CDRL Data Reports as indicated in Box 14 of each data item to the following:

Andrew Freeman, AFRL/RYZT 2241 Avionics Circle Wright-Patterson AFB, OH 45433

(937) 713-8158 andrew.freeman.6@us.af.mil

AFRL/RYOX (STINFO)

2261 Monahan Way Bldg 196 Rm 1 Wright-Patterson AFB, OH 45433 afrl.wrs.stinfo@us.af.mil

Kathleen Hall, AFRL/RYF 4170 Hebble Creek Road Wright-Patterson AFB, OH 45433

(937) 713-8459 kathleen.hall@us.af.mil

Bryan Fleckenstein, AFRL/RQKSR 2130 8th Street, Bldg 45 Wright-Patterson AFB, OH 45433

(937) 713-9982 bryan.fleckenstein@us.af.mil

DCMA/ACO-See SF 26 Block 6 for address

AFRL/DO

Antonio Straight

(937) 255-6619 antonio.straight.ctr@us.af.mil

"If, pursuant to FAR 52.232-22, full funding isn't provided, the Contractor is required to deliver the final report. During the life of the contract, the contractor shall continuously reserve sufficient funds from the amount allotted to guarantee the preparation and delivery of the final report. "

SECTION F - DELIVERIES OR PERFORMANCE

SECTION F FA8650-18-R-1672

SHIP MARK TRANS

ITEM SUPPLIES SCHEDULE DATA QTY TO FOR PRI DATE

0002 1 F4FBBG F4FBBG 63 MARO

Noun: SOFTWARE Descriptive Data:

The scheduled delivery date for software is XXX. The shipping address is as follows:

Andrew Freeman, AFRL/RYZT 2241 Avionics Circle Wright-Patterson AFB, OH 45433

(937) 713-8158 andrew.freeman.6@us.af.mil

Mark For: FA8650-18-C-1672 (Include contract number and the AF Program Manager's name, office symbol, and phone number on the shipping documents.)

0003 1 F4FBBG F4FBBG 63 MARO

Noun: HARDWARE Descriptive Data:

The scheduled delivery date for hardware is XXX. The shipping address is as follows:

Andrew Freeman, AFRL/RYZT 2241 Avionics Circle Wright-Patterson AFB, OH 45433

(937) 713-8158 andrew.freeman.6@us.af.mil

Mark For: FA8650-18-C-1672 (Include contract number and the AF Program Manager's name, office symbol, and phone number on the shipping documents.)

NOTICE: The following contract clauses pertinent to this section are hereby incorporated by reference:

FEDERAL ACQUISITION REGULATION CONTRACT CLAUSES

52.242-15 STOP-WORK ORDER (AUG 1989) - ALTERNATE I (APR 1984)

52.247-34 F.O.B. DESTINATION (NOV 1991)

SECTION G - CONTRACT ADMINISTRATION DATA

SECTION G FA8650-18-R-1672

NOTICE: The following contract clauses pertinent to this section are hereby incorporated in full text:

A. DEFENSE FAR SUPP CONTRACT CLAUSES IN FULL TEXT

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

(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).

Cost Voucher.

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.

Destination/Destination

SECTION G - CONTRACT ADMINISTRATION DATA

SECTION G FA8650-18-R-1672

(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 TBD Issue By DoDAAC TBD Admin DoDAAC TBD Inspect By DoDAAC TBD Ship To Code TBD Ship From Code TBD Mark For Code TBD Service Approver (DoDAAC) TBD Service Acceptor (DoDAAC) TBD Accept at Other DoDAAC TBD LPO DoDAAC TBD DCAA Auditor DoDAAC TBD Other DoDAAC(s) TBD

(*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 e-mail address identified below in the “Send Additional Email Notifications” field of WAWF once a document is submitted in the system.

TBD

(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.

TBD

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

B. OTHER CONTRACT CLAUSES IN FULL TEXT

G019 204.7108 (B) (2) PAYMENT INSTRUCTIONS (JAN 2018)

The payment office shall allocate and record the amounts paid to the accounting classification citations in the contract using the table shown in Section J, Attachment No. 6 based on the type of payment request submitted (see DFARS 252.232-7006) and the type of effort.

SECTION H - SPECIAL CONTRACT REQUIREMENTS

SECTION H FA8650-18-R-1672

PART II - CONTRACT CLAUSES

SECTION I - CONTRACT CLAUSES

SECTION I FA8650-18-R-1672

Contract Clauses in this section are from the FAR, Defense FAR Sup, Air Force FAR Sup, and the Air Force Materiel Command FAR Sup, and are current through the following updates:

Database_Version: 6.15.x1200; Issued: 1/25/2018; FAR: FAC 2005-96; DFAR: DPN20171228; DL.: DL 98-021;

Class Deviations: CD 2018-O0010; AFFAR: 2002 Edition; AFAC: AFAC 2017-1003; IPN: 98-009

I. NOTICE: The following contract clauses pertinent to this section are hereby incorporated by reference:

A. FEDERAL ACQUISITION REGULATION CONTRACT CLAUSES

52.202-01 DEFINITIONS (NOV 2013)

52.203-03 GRATUITIES (APR 1984)

52.203-05 COVENANT AGAINST CONTINGENT FEES (MAY 2014)

52.203-06 RESTRICTIONS ON SUBCONTRACTOR SALES TO THE GOVERNMENT (SEP 2006)

52.203-07 ANTI-KICKBACK PROCEDURES (MAY 2014)

52.203-08 CANCELLATION, RESCISSION, AND RECOVERY OF FUNDS FOR ILLEGAL OR

IMPROPER ACTIVITY (MAY 2014)

52.203-10 PRICE OR FEE ADJUSTMENT FOR ILLEGAL OR IMPROPER ACTIVITY (MAY 2014)

52.203-12 LIMITATION ON PAYMENTS TO INFLUENCE CERTAIN FEDERAL TRANSACTIONS

(OCT 2010)

52.203-13 CONTRACTOR CODE OF BUSINESS ETHICS AND CONDUCT (OCT 2015)

52.203-17 CONTRACTOR EMPLOYEE WHISTLEBLOWER RIGHTS AND REQUIREMENT TO

INFORM EMPLOYEES OF WHISTLEBLOWER RIGHTS (APR 2014)

52.203-19 PROHIBITION ON REQUIRING CERTAIN INTERNAL CONFIDENTIALITY

AGREEMENTS OR STATEMENTS (JAN 2017)

52.204-02 SECURITY REQUIREMENTS (AUG 1996)

52.204-04 PRINTED OR COPIED DOUBLE-SIDED ON POSTCONSUMER FIBER CONTENT

PAPER (MAY 2011)

52.204-10 REPORTING EXECUTIVE COMPENSATION AND FIRST-TIER SUBCONTRACT

AWARDS (OCT 2016)

52.204-13 SYSTEM FOR AWARD MANAGEMENT MAINTENANCE (OCT 2016)

52.204-18 COMMERCIAL AND GOVERNMENT ENTITY CODE MAINTENANCE (JUL 2016)

52.204-19 INCORPORATION BY REFERENCE OF REPRESENTATIONS AND CERTIFICATIONS

(DEC 2014)

52.204-22 ALTERNATIVE LINE ITEM PROPOSAL (JAN 2017)

52.209-06 PROTECTING THE GOVERNMENT'S INTEREST WHEN SUBCONTRACTING WITH

CONTRACTORS DEBARRED, SUSPENDED, OR PROPOSED FOR DEBARMENT

(OCT 2015)

52.209-09 UPDATES OF PUBLICLY AVAILABLE INFORMATION REGARDING RESPONSIBILITY

MATTERS (JUL 2013)

52.209-10 PROHIBITION ON CONTRACTING WITH INVERTED DOMESTIC CORPORATIONS

(NOV 2015)

52.210-01 MARKET RESEARCH (APR 2011)

52.211-05 MATERIAL REQUIREMENTS (AUG 2000)

52.215-02 AUDIT AND RECORDS -- NEGOTIATION (OCT 2010)

52.215-08 ORDER OF PRECEDENCE--UNIFORM CONTRACT FORMAT (OCT 1997)

52.215-10 PRICE REDUCTION FOR DEFECTIVE CERTIFIED COST OR PRICING DATA (AUG

2011)

52.215-11 PRICE REDUCTION FOR DEFECTIVE CERTIFIED COST OR PRICING DATA--

MODIFICATIONS (AUG 2011)

52.215-12 SUBCONTRACTOR CERTIFIED COST OR PRICING DATA (OCT 2010)

52.215-13 SUBCONTRACTOR CERTIFIED COST OR PRICING DATA--MODIFICATIONS (OCT

2010)

52.215-14 INTEGRITY OF UNIT PRICES (OCT 2010)

52.215-15 PENSION ADJUSTMENTS AND ASSET REVERSIONS (OCT 2010)

52.215-18 REVERSION OR ADJUSTMENT OF PLANS FOR POSTRETIREMENT BENEFITS

(PRB) OTHER THAN PENSIONS (JUL 2005)

52.215-19 NOTIFICATION OF OWNERSHIP CHANGES (OCT 1997)

52.215-21 REQUIREMENTS FOR CERTIFIED COST OR PRICING DATA AND DATA OTHER

THAN CERTIFIED COST OR PRICING DATA--MODIFICATIONS (OCT 2010)

52.215-23 LIMITATIONS ON PASS-THROUGH CHARGES (OCT 2009)

52.216-07 ALLOWABLE COST AND PAYMENT (JUN 2013)

52.216-08 FIXED FEE (JUN 2011)

52.219-04 NOTICE OF PRICE EVALUATION PREFERENCE FOR HUBZONE SMALL BUSINESS

CONCERNS (OCT 2014)

52.219-08 UTILIZATION OF SMALL BUSINESS CONCERNS (NOV 2016)

52.219-09 SMALL BUSINESS SUBCONTRACTING PLAN (JAN 2017)

52.219-09 SMALL BUSINESS SUBCONTRACTING PLAN (JAN 2017) - ALTERNATE II (NOV

2016)

52.219-16 LIQUIDATED DAMAGES -- SUBCONTRACTING PLAN (JAN 1999)

52.219-28 POST-AWARD SMALL BUSINESS PROGRAM REREPRESENTATION (JUL 2013)

52.222-02 PAYMENT FOR OVERTIME PREMIUMS (JUL 1990)

Para (a), Dollar amount is 'zero'

52.222-03 CONVICT LABOR (JUN 2003)

52.222-21 PROHIBITION OF SEGREGATED FACILITIES (APR 2015)

52.222-26 EQUAL OPPORTUNITY (SEP 2016)

52.222-35 EQUAL OPPORTUNITY FOR VETERANS (OCT 2015)

52.222-36 EQUAL OPPORTUNITY FOR WORKERS WITH DISABILITIES (JUL 2014)

52.222-37 EMPLOYMENT REPORTS ON VETERANS (FEB 2016)

52.222-40 NOTIFICATION OF EMPLOYEE RIGHTS UNDER THE NATIONAL LABOR RELATIONS

ACT (DEC 2010)

52.222-50 COMBATING TRAFFICKING IN PERSONS (MAR 2015)

52.222-54 EMPLOYMENT ELIGIBILITY VERIFICATION (OCT 2015)

52.223-06 DRUG-FREE WORKPLACE (MAY 2001)

52.223-18 ENCOURAGING CONTRACTOR POLICIES TO BAN TEXT MESSAGING WHILE

DRIVING (AUG 2011)

52.224-01 PRIVACY ACT NOTIFICATION (APR 1984)

52.224-02 PRIVACY ACT (APR 1984)

52.225-13 RESTRICTIONS ON CERTAIN FOREIGN PURCHASES (JUN 2008)

52.227-01 AUTHORIZATION AND CONSENT (DEC 2007) - ALTERNATE I (APR 1984)

52.227-02 NOTICE AND ASSISTANCE REGARDING PATENT AND COPYRIGHT

INFRINGEMENT (DEC 2007)

52.227-10 FILING OF PATENT APPLICATIONS -- CLASSIFIED SUBJECT MATTER (DEC 2007)

52.227-11 PATENT RIGHTS - OWNERSHIP BY THE CONTRACTOR (MAY 2014)

Para (j), Communications: 'TBD'

52.228-07 INSURANCE -- LIABILITY TO THIRD PERSONS (MAR 1996)

52.230-02 COST ACCOUNTING STANDARDS (OCT 2015)

52.230-03 DISCLOSURE AND CONSISTENCY OF COST ACCOUNTING PRACTICES (OCT

2015)

52.230-05 COST ACCOUNTING STANDARDS - EDUCATIONAL INSTITUTION (AUG 2016)

52.230-06 ADMINISTRATION OF COST ACCOUNTING STANDARDS (JUN 2010)

52.232-09 LIMITATION ON WITHHOLDING OF PAYMENTS (APR 1984)

52.232-17 INTEREST (MAY 2014)

52.232-22 LIMITATION OF FUNDS (APR 1984)

52.232-23 ASSIGNMENT OF CLAIMS (MAY 2014) - ALTERNATE I (APR 1984)

52.232-25 PROMPT PAYMENT (JAN 2017)

52.232-33 PAYMENT BY ELECTRONIC FUNDS TRANSFER - SYSTEM FOR AWARD

MANAGEMENT (JUL 2013)

52.232-39 UNENFORCEABILITY OF UNAUTHORIZED OBLIGATIONS (JUN 2013)

52.232-40 PROVIDING ACCELERATED PAYMENTS TO SMALL BUSINESS

SUBCONTRACTORS (DEC 2013)

52.233-01 DISPUTES (MAY 2014)

52.233-03 PROTEST AFTER AWARD (AUG 1996) - ALTERNATE I (JUN 1985)

52.233-04 APPLICABLE LAW FOR BREACH OF CONTRACT CLAIM (OCT 2004)

52.242-01 NOTICE OF INTENT TO DISALLOW COSTS (APR 1984)

52.242-03 PENALTIES FOR UNALLOWABLE COSTS (MAY 2014)

52.242-04 CERTIFICATION OF FINAL INDIRECT COSTS (JAN 1997)

52.242-05 PAYMENTS TO SMALL BUSINESS SUBCONTRACTORS (JAN 2017)

52.242-13 BANKRUPTCY (JUL 1995)

52.243-02 CHANGES -- COST-REIMBURSEMENT (AUG 1987) - ALTERNATE V (APR 1984)

52.243-06 CHANGE ORDER ACCOUNTING (APR 1984)

52.243-07 NOTIFICATION OF CHANGES (JAN 2017)

Para (b), Number of calendar days is (insert 30 for RDSS/C) '30 days' Para (d), Number of calendar days is (insert 30 for RDSS/C) '30 days'

52.244-02 SUBCONTRACTS (OCT 2010)

Para (d), approval required on subcontracts: 'N/A' Para (j), Insert subcontracts evaluated during negotiations. 'N/A'

52.244-05 COMPETITION IN SUBCONTRACTING (DEC 1996)

52.244-06 SUBCONTRACTS FOR COMMERCIAL ITEMS (NOV 2017)

52.245-01 GOVERNMENT PROPERTY (JAN 2017)

52.245-09 USE AND CHARGES (APR 2012)

52.246-23 LIMITATION OF LIABILITY (FEB 1997)

52.247-01 COMMERCIAL BILL OF LADING NOTATIONS (FEB 2006)

52.249-06 TERMINATION (COST-REIMBURSEMENT) (MAY 2004)

52.249-14 EXCUSABLE DELAYS (APR 1984)

52.251-01 GOVERNMENT SUPPLY SOURCES (APR 2012)

52.253-01 COMPUTER GENERATED FORMS (JAN 1991)

B. DEFENSE FEDERAL ACQUISITION REGULATION SUPPLEMENT CONTRACT CLAUSES

252.203-7000 REQUIREMENTS RELATING TO COMPENSATION OF FORMER DOD OFFICIALS

(SEP 2011)

252.203-7001 PROHIBITION ON PERSONS CONVICTED OF FRAUD OR OTHER DEFENSE-

CONTRACT-RELATED FELONIES (DEC 2008)

252.203-7002 REQUIREMENT TO INFORM EMPLOYEES OF WHISTLEBLOWER RIGHTS (SEP

2013)

252.203-7003 AGENCY OFFICE OF THE INSPECTOR GENERAL (DEC 2012)

252.203-7004 DISPLAY OF HOTLINE POSTERS (OCT 2016)

252.204-7003 CONTROL OF GOVERNMENT PERSONNEL WORK PRODUCT (APR 1992)

252.204-7005 ORAL ATTESTATION OF SECURITY RESPONSIBILITIES (NOV 2001)

252.204-7008 COMPLIANCE WITH SAFEGUARDING COVERED DEFENSE INFORMATION

CONTROLS (OCT 2016)

252.204-7015 NOTICE OF AUTHORIZED DISCLOSURE OF INFORMATION TO LITIGATION

SUPPORT (MAY 2016)

252.205-7000 PROVISION OF INFORMATION TO COOPERATIVE AGREEMENT HOLDERS (DEC

1991)

252.209-7004 SUBCONTRACTING WITH FIRMS THAT ARE OWNED OR CONTROLLED BY THE

GOVERNMENT OF A COUNTRY THAT IS A STATE SPONSOR OF TERRORISM

(OCT 2015)

252.211-7003 ITEM UNIQUE IDENTIFICATION AND VALUATION (MAR 2016)

Para (c)(1)(i). Insert Contract Line, Subline, or Exhibit Line Item Number and Item

Description or n/a. 'N/A'

Para (c)(1)(ii). Identify Contract Line, Subline, or Exhibit Line Item Nr and Item Description. If items are identified in the Schedule, insert "See Schedule" 'N/A'

Para (c)(1)(iii). Attachment Nr. 'N/A' Para (c)(1)(iv). Attachment Nr. 'N/A' Para (f)(2)(iii). Line item number or n/a. 'N/A'

252.211-7007 REPORTING OF GOVERNMENT-FURNISHED PROPERTY (AUG 2012)

252.211-7008 USE OF GOVERNMENT-ASSIGNED SERIAL NUMBERS (SEP 2010)

252.215-7000 PRICING ADJUSTMENTS (DEC 2012)

252.215-7002 COST ESTIMATING SYSTEM REQUIREMENTS (DEC 2012)

252.222-7006 RESTRICTIONS ON THE USE OF MANDATORY ARBITRATION AGREEMENTS (DEC

2010)

252.223-7004 DRUG-FREE WORK FORCE (SEP 1988)

252.225-7004 REPORT OF INTENDED PERFORMANCE OUTSIDE THE UNITED STATES AND

CANADA--SUBMISSION AFTER AWARD (OCT 2015)

252.225-7009 RESTRICTION ON ACQUISITION OF CERTAIN ARTICLES CONTAINING SPECIALTY

METALS (OCT 2014)

252.225-7012 PREFERENCE FOR CERTAIN DOMESTIC COMMODITIES (DEC 2017)

252.225-7017 PHOTOVOLTAIC DEVICES (JAN 2018)

252.225-7048 EXPORT-CONTROLLED ITEMS (JUN 2013)

252.226-7001 UTILIZATION OF INDIAN ORGANIZATIONS, INDIAN-OWNED ECONOMIC

ENTERPRISES, AND NATIVE HAWAIIAN SMALL BUSINESS CONCERNS (SEP 2004)

252.227-7013 RIGHTS IN TECHNICAL DATA--NONCOMMERCIAL ITEMS (FEB 2014)

252.227-7014 RIGHTS IN NONCOMMERCIAL COMPUTER SOFTWARE AND NONCOMMERCIAL

COMPUTER SOFTWARE DOCUMENTATION (FEB 2014)

252.227-7016 RIGHTS IN BID OR PROPOSAL INFORMATION (JAN 2011)

252.227-7019 VALIDATION OF ASSERTED RESTRICTIONS--COMPUTER SOFTWARE (SEP 2016)

252.227-7025 LIMITATIONS ON THE USE OR DISCLOSURE OF GOVERNMENT-FURNISHED

INFORMATION MARKED WITH RESTRICTIVE LEGENDS (MAY 2013)

252.227-7027 DEFERRED ORDERING OF TECHNICAL DATA OR COMPUTER SOFTWARE (APR

1988)

252.227-7030 TECHNICAL DATA--WITHHOLDING OF PAYMENT (MAR 2000)

252.227-7037 VALIDATION OF RESTRICTIVE MARKINGS ON TECHNICAL DATA (SEP 2016)

252.227-7038 PATENT RIGHTS--OWNERSHIP BY THE CONTRACTOR (LARGE BUSINESS) (JUN

2012)

252.231-7000 SUPPLEMENTAL COST PRINCIPLES (DEC 1991)

252.232-7003 ELECTRONIC SUBMISSION OF PAYMENT REQUESTS AND RECEIVING REPORTS

(JUN 2012)

252.232-7010 LEVIES ON CONTRACT PAYMENTS (DEC 2006)

252.235-7010 ACKNOWLEDGMENT OF SUPPORT AND DISCLAIMER (MAY 1995)

Para (a), name of contracting agency(ies): 'United States Air Force' Para (a), contract number(s): 'FA8650-18-R-1672' Para (b), name of contracting agency(ies): 'United States Air Force'

252.235-7011 FINAL SCIENTIFIC OR TECHNICAL REPORT (JAN 2015)

252.239-7000 PROTECTION AGAINST COMPROMISING EMANATIONS (JUN 2004)

252.242-7004 MATERIAL MANAGEMENT AND ACCOUNTING SYSTEM (MAY 2011)

252.242-7005 CONTRACTOR BUSINESS SYSTEMS (FEB 2012)

252.242-7006 ACCOUNTING SYSTEM ADMINISTRATION (FEB 2012)

252.243-7002 REQUESTS FOR EQUITABLE ADJUSTMENT (DEC 2012)

252.244-7000 SUBCONTRACTS FOR COMMERCIAL ITEMS (JUN 2013)

252.244-7001 CONTRACTOR PURCHASING SYSTEM ADMINISTRATION - BASIC (MAY 2014)

252.245-7001 TAGGING, LABELING, AND MARKING OF GOVERNMENT-FURNISHED PROPERTY

(APR 2012)

252.245-7002 REPORTING LOSS OF GOVERNMENT PROPERTY (DEC 2017)

252.245-7003 CONTRACTOR PROPERTY MANAGEMENT SYSTEM ADMINISTRATION (APR 2012)

252.245-7004 REPORTING, REUTILIZATION, AND DISPOSAL (DEC 2017)

Insert Item(s) 'TBD'

Insert Item(s) 'TBD'

252.246-7007 CONTRACTOR COUNTERFEIT ELECTRONIC PART DETECTION AND AVOIDANCE

SYSTEM (AUG 2016)

252.247-7024 NOTIFICATION OF TRANSPORTATION OF SUPPLIES BY SEA (MAR 2000)

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

Para (f), Contractor's address is 'TBD' Para (f), Government remittance address is 'TBD'

C. AIR FORCE FEDERAL ACQUISITION REGULATION SUPPLEMENT CONTRACT CLAUSES

5352.201-9101 OMBUDSMAN (JUN 2016)

Para (c). Ombudsmen names, addresses, phone numbers, fax, and email addresses.

'Ms. Lisette K. LeDuc, Director of Contracting, AFRL/PK, 937-904-4407, lisette.leduc@us.af.mil'

II. NOTICE: The following contract clauses pertinent to this section are hereby incorporated in full text:

A. FEDERAL ACQUISITION REGULATION CONTRACT CLAUSES IN FULL TEXT

52.211-15 DEFENSE PRIORITY AND ALLOCATION REQUIREMENTS (APR 2008)

This is a rated order certified for national defense, emergency preparedness, and energy program use, and the Contractor shall follow all the requirements of the Defense Priorities and Allocations System regulation (15 CFR 700).

52.252-02 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es): http://farsite.hill.af.mil/

52.252-06 AUTHORIZED DEVIATIONS IN CLAUSES (APR 1984)

(a) The use in this solicitation or contract of any Federal Acquisition Regulation (48 CFR Chapter

1) clause with an authorized deviation is indicated by the addition of "(DEVIATION)" after the date of the clause.

(b) The use in this solicitation or contract of any Defense Federal Acquisition Regulation Supplement (48 CFR Chapter 2) clause with an authorized deviation is indicated by the addition of "(DEVIATION)" after the name of the regulation.

B. DEFENSE FAR SUPP CONTRACT CLAUSES IN FULL TEXT

252.204-7012 SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT

REPORTING (OCT 2016)

(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 unclassified information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information.

“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 controlled technical information or other information, as described in the Controlled Unclassified Information (CUI) Registry at http://www.archives.gov/cui/registry/category-list.html, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies, and is—

(1) Marked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract; or

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

“Cyber incident” means actions taken through the use of computer networks that result in a compromise or 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.

“Information system” means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information.

“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 covered defense information is recorded, stored, or printed within a covered contractor 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.

“Rapidly report” 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-Noncommercial 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 on all covered contractor information systems. To provide adequate security, the Contractor shall implement, at a minimum, the following information security protections:

(1) For covered contractor information systems that are part of an Information Technology (IT) service or system operated on behalf of the Government, the following security requirements apply:

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

(ii) 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.

(2) 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) of this clause, the following security requirements apply:

(i) Except as provided in paragraph (b)(2)(ii) of this clause, the covered contractor information system shall be subject to 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,” (available via the Internet at http://dx.doi.org/10.6028/NIST.SP.800-171) in effect at the time the solicitation is issued or as authorized by the Contracting Officer.

(ii)(A) The Contractor shall implement NIST SP 800-171, as soon as practical, but not later than December 31, 2017. For all contracts awarded prior to October 1, 2017, the Contractor shall notify the DoD Chief Information Officer (CIO), via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award.

(B) The Contractor shall submit requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO. The Contractor need not implement any security requirement adjudicated by an authorized representative of the DoD CIO to be nonapplicable or to have an alternative, but equally effective, security measure that may be implemented in its place.

(C) If the DoD CIO has previously adjudicated the contractor’s requests indicating that a requirement is not applicable or that an alternative security measure is equally effective, a copy of that approval shall be provided to the Contracting Officer when requesting its recognition under this contract.

(D) If the Contractor intends to use an external cloud service provider to store, process, or transmit any covered defense information in performance of this contract, the Contractor shall require and ensure that the cloud service provider meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline https://www.fedramp.gov/resources/documents/) and that the cloud service provider complies with requirements in paragraphs (c) through (g) of this clause for cyber incident reporting, malicious software, media preservation and protection, access to additional information and equipment necessary for forensic analysis, and cyber incident damage assessment.

(3) Apply other information systems security measures when the Contractor reasonably determines that information systems security measures, in addition to those identified in paragraphs (b)(1) and (2) of this clause, may be required to provide adequate security in a dynamic environment or to accommodate special circumstances (e.g., medical devices) and any individual, isolated, or temporary deficiencies based on an assessed risk or vulnerability. These measures may be addressed in a system security plan.

(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 and identified in the contrac, 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/Pages/index.aspx.

(d) Malicious software. When the Contractor or subcontractors discover and isolate malicious software in connection with a reported cyber incident, submit the malicious software to DoD Cyber Crime Center (DC3) in accordance with instructions provided by DC3 or the Contracting Officer. Do not send the malicious software to 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 32 CFR part 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 this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve covered defense information, including subcontracts for commercial items, without alteration, except to identify the parties. The Contractor shall determine if the information required for subcontractor performance retains its identity as covered defense information and will require protection under this clause, and, if necessary, consult with the Contracting Officer; and

(2) Require subcontractors to—

(i) Notify the prime Contractor (or next higher-tier subcontractor) when submitting a request to vary from a NIST SP 800-171 security requirement to the Contracting Officer, in accordance with paragraph (b)(2)(ii)(B) of this clause; and

(ii) Provide the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable, when reporting a cyber incident to DoD as required in paragraph (c) of this clause.

252.219-7003 SMALL BUSINESS SUBCONTRACTING PLAN (DOD CONTRACTS) (DEVIATION

2018-O0007) (DEC 2017)

This clause supplements the Federal Acquisition Regulation 52.219-9, Small Business Subcontracting Plan, clause of this contract.

(a) Definitions. “Summary Subcontract Report (SSR) Coordinator,” as used in this clause, means the individual who is registered in the Electronic Subcontracting Reporting System (eSRS) at the Department of Defense (9700) and is responsible for acknowledging receipt or rejecting SSRs in eSRS for the Department of Defense.

(b) Subcontracts awarded to workshops approved by the Committee for Purchase from People Who are Blind or Severely Disabled (41 U.S.C. 8502-8504), may be counted toward the Contractor’s small business subcontracting goal.

(c) A mentor firm, under the Pilot Mentor-Protege Program established under section 831 of Public Law 101-510, as amended, may count toward its small disadvantaged business goal, subcontracts awarded to-

(1) Protege firms which are qualified organizations employing the severely disabled; and

(2) Former protege firms that meet the criteria in section 831(g)(4) of Public Law 101-510.

(d) The master plan is approved by the Contractor's cognizant contract administration activity.

(e) In those subcontracting plans which specifically identify small businesses, the Contractor shall notify the Administrative Contracting Officer of any substitutions of firms that are not small business firms, for the small business firms specifically identified in the subcontracting plan. Notifications shall be in writing and shall occur within a reasonable period of time after award of the subcontract. Contractor-specified formats shall be acceptable.

(f)(1) For DoD, the Contractor shall submit reports in eSRS as follows:

(i) The Individual Subcontract Report (ISR) shall be submitted to the contracting officer at the procuring contracting office, even when contract administration has been delegated to the Defense Contract Management Agency.

(ii) Submit the consolidated SSR for an individual subcontracting plan in eSRS by selecting “Department of Defense (DoD) (9700)” from the top of the second dropdown menu. The contractor shall not select anything lower.

(2) For DoD, the authority to acknowledge receipt or reject reports in eSRS is as follows:

(i) The authority to acknowledge receipt or reject the ISR resides with the contracting officer who receives it, as described in paragraph (f)(1)(i) of this clause.

(ii) The authority to acknowledge receipt or reject SSRs resides with the SSR Coordinator.

252.239-7010 CLOUD COMPUTING SERVICES (OCT 2016)

(a) Definitions. As used in this clause—

“Authorizing official,” as described in DoD Instruction 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), means the senior Federal official or executive with the authority to formally assume responsibility for operating an information system at an acceptable level of risk to organizational operations (including mission, functions, image, or reputation), organizational assets, individuals, other organizations, and the Nation.

“Cloud computing” means a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. This includes other commercial terms, such as on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. It also includes commercial offerings for software-as-a-service, infrastructure-as-a-service, and platform-as-a-service.

“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.

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

“Government data” means any information, document, media, or machine readable material regardless of physical form or characteristics, that is created or obtained by the Government in the course of official Government business.

“Government-related data” means any information, document, media, or machine readable material regardless of physical form or characteristics that is created or obtained by a contractor through the storage, processing, or communication of Government data. This does not include contractor’s business records e.g. financial records, legal records etc. or data such as operating procedures, software coding or algorithms that are not uniquely applied to the Government data.

“Information system” means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information.

“Media” means physical devices or writing surfaces including, but 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.

“Spillage” security incident that results in the transfer of classified or controlled unclassified information onto an information system not accredited (i.e., authorized) for the appropriate security level.

b) Cloud computing security requirements. The requirements of this clause are applicable when using cloud computing to provide information technology services in the performance of the contract.

(1) If the Contractor indicated in its offer that it “does not anticipate the use of cloud computing services in the performance of a resultant contract,” in response to provision 252.239-7009, Representation of Use of Cloud Computing, and after the award of this contract, the Contractor proposes to use cloud computing services in the performance of the contract, the Contractor shall obtain approval from the Contracting Officer prior to utilizing cloud computing services in performance of the contract.

(2) The Contractor shall implement and maintain administrative, technical, and physical safeguards and controls with the security level and services required in accordance with the Cloud

Computing Security Requirements Guide (SRG) (version in effect at the time the solicitation is issued or as authorized by the Contracting Officer) found at http://iase.disa.mil/cloud_security/Pages/index.aspx, unless notified by the Contracting Officer that this requirement has been waived by the DoD Chief Information Officer.

(3) The Contractor shall maintain within the United States or outlying areas all Government data that is not physically located on DoD premises, unless the Contractor receives written notification from the Contracting Officer to use another location, in accordance with 239.7602-2 (a).

(c) Limitations on access to, and use and disclosure of Government data and Government-related data.

(1) The Contractor shall not access, use, or disclose Government data unless specifically authorized by the terms of this contract or a task order or delivery order issued hereunder.

(i) If…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it.