SPE7L318Q0108.PDF

REQUEST FOR QUOTATIONS THIS RFQ IS IS NOT A SMALL BUSINESS SET-ASIDE

4. CERT.FOR NAT. DEF.

UNDER BDSA REG. 2

AND/OR DMS REG. 1

5. ISSUED BY

7. DELIVERY

9. DESTINATION

10. PLEASE FURNISH QUOTATIONS TO THE

ISSUING OFFICE IN BLOCK 5 ON OR

BEFORE CLOSE OF BUSINESS (Date)

IMPORTANT: This is a request for information, and quotations furnished are not offers. If you are unable to quote, please so indicate on this form and return it to the address in Block 5. This request does not commit the Government to pay any costs incurred in the preparation of the submission of this quotation or to contract for supplies or services. Supplies are of domestic origin unless otherwise indicated by quoter. Any representations and/or certifications attached to this Request for Quotations must be completed by the quoter.

11. SCHEDULE (See Continuation Sheets)

12. DISCOUNT FOR PROMPT PAYMENT

d. CALENDAR DAYS

NUMBER PERCENTAGE

NOTE: Additional provisions and representations are are not attached.

13. NAME AND ADDRESS OF QUOTER

a. NAME OF QUOTER

14. SIGNATURE OF PERSON AUTHORIZED TO SIGN

QUOTATION

16. SIGNER

AUTHORIZED FOR LOCAL REPRODUCTION

Previous edition not useable

STANDARD FORM 18 (REV. 6-95)

Prescribed by GSA-FAR (48 CFR) 53.215-1(a)

SPE7L3-18-Q-0108

1. REQUEST NO.

2017 NOV 17

2. DATE ISSUED

0071145193

3. REQUISITION/PURCHASE REQUEST NO.

DO-C9

RATING

DLA LAND AND MARITIME

LAND SUPPLIER OPNS VEHICLE SPT

PO BOX 3990

COLUMBUS OH 43218-3990

USA

Buyer: Kenneth Young PLCLBDJ Tel: 614-692-7116 Fax: 614-693-1573 Email: Kenneth.Young@dla.mil

SEE SCHEDULE

6. DELIVER BY (Date)

8. TO:

c. CITY

d. STATE

b. STREET ADDRESS

a. NAME OF CONSIGNEE

e. ZIP CODE

a. 10 CALENDAR DAYS

b. 20 CALENDAR DAYS (%) c. 30 CALENDAR DAYS

15. DATE OF QUOTATION

a. NAME (Type or Print)

AREA CODE

c. TITLE (Type or Print)d. CITY

c. COUNTY

b. STREET ADDRESS

e. STATE f. ZIP CODE

See Schedule

2017 NOV 27

NUMBER

FOB DESTINATION

OTHER

(See Schedule)

CAGE

b. TELEPHONE

PAGE OF PAGES

1 24

See attached schedule to complete quote information.

Quoter must also complete the following:

a. Quotation is valid for 90 days from date specified in Block 10 above unless otherwise indicated: _____________ .

b. Prices quoted are:

___ Contained in Commercial Catalog or Published Price List No. ___________________ dated _______________ page __________ .

___ Contained in Internal Price List No. _______________dated ____________________, which may be examined at our facility.

___ Commercial sales of comparable quantities: Quantity ____________ ; Price _____________;

___ Customer ________________________.

___ Other (provide basis) ______________________________________ _______________________________________ .

c. FOB Point: ____ Destination ____ Origin Shipping Point (City, State) _________________________________________ .

d. If delivery period shown in Block 6 is unacceptable, provide best possible delivery: _________________________________.

e. Remittance Address (Name, Street, City, State, ZIP): Same as Block 13 unless otherwise indicated below:

f. Vendor FAX Number: ____________________ Vendor Toll-Free Number: ____________________ Vendor E-mail: ______________________________

CONTINUED ON NEXT PAGE

THIS SOLICITATION IS BEING ISSUED UNDER SEPA AUTHORITY. REQUIREMENT MAY BE AWARDED PRIOR TO SOLICITATION

RETURN DATE.

DAG 13.003 (B) Special Emergency Procurement Authority (a)(2) SAT is up to $750,000 for acquisitions awarded and performed or purchases to be made within the US; ($1.5 million for acquisitions awarded and performed or purchases to be made outside the US). FAR 2.101;

THE FOLLOWING CLAUSES ALSO APPLY:

FAR 52.203-12 LIMITATION ON PAYMENTS TO INFLUENCE CERTAIN FEDERAL TRANSACTIONS (OCT 2010) DFARS 252.209-7004 SUBCONTRACTING WITH FIRMS THAT ARE OWNED OR CONTROLLED BY THE GOVERNMENT OF A TERRORIST

COUNTRY.

52.203-11 Certification and Disclosure Regarding Payments to Influence Certain Federal Transactions 52.203-12 Limitations on Payments to Influence Certain Federal Transactions 52.209-7004 Subcontracting With Firms That Are Owned or Controlled By the Government of a Terrorist Country 252.209-7004 Subcontracting with Firms that are Owned or Controlled by the Government of a Terrorist Country

OFFER SUBMISSION INSTRUCTIONS: ALL OFFERORS MUST SUBMIT THIER QUOTES THROUGH DIBBS . Once the evaluation process begins, late quotations will only be considered if the contracting officer determines that considering the late quotation is in the best interest of the Government and would not unduly delay the award.

EVALUATION FACTORS FOR AWARD

Award will be made to the offeror(s) whose quote(s) conforms to the solicitation requirements and represents the best value to the Government. Past performance, offered delivery and price will be evaluated when making a comparative assessment of quotes. An award may be made to other than the lowest priced, technically acceptable, responsible offeror(s).

THIS SOLICITATION INCORPORATES THE TERMS AND CONDITIONS SET FORTH IN THE REVISION OF THE DLA MASTER SOLICITATION FOR EPROCUREMENT AUTOMATED SIMPLIFIED ACQUISITIONS IN EFFECT ON THE SOLICITATION ISSUE DATE. ALL REVISIONS OF THE DLA MASTER SOLICITATION FOR EPROCUREMENT AUTOMATED SIMPLIFIED ACQUISITIONS CAN BE FOUND ON THE WEB AT: http://www.dla.mil/HQ/Acquisition/Offers/eProcurement.aspx

DLAD PROCUREMENT NOTES

DLAD Procurement Notes are incorporated by reference, with the same force and effect as if they were in full text. The full text of a DLAD Procurement Note may be accessed electronically at http://www.dla.mil/HQ/Acquisition/Offers/eProcurement.aspx and via 'References' on the DIBBS homepage.

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

PAGE 2 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

SPE7L3-18-Q-0108

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

An invoice and WAWF receiving report (RR) are both required. The invoice and receiving report may be submitted separately or together as a combo type document. See DFARS Appendix F for detailed instructions on preparing the WAWF RR.

NOTE: For contracts in accordance with Fast Payment Procedures, a Fast Pay (FP) invoice must be connected with a receiving report (RR), so either submit a FP combo or submit a RR and follow with a FP invoice. If there is no registered acceptor, the RR portion of the combo cannot be processed. In this case, submit a stand-alone FP invoice (“accept by” DoDAAC/location is mandatory).

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

See Award.

(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 See Page 1 Issue By DoDAAC See Page 1 Admin DoDAAC See Page 1 Inspect By DoDAAC See Award Ship To Code See Award Ship From Code See Award/Purchase Order if applicable Mark For Code See Award/Purchase Order if applicable Service Approver (DoDAAC) See Award/Purchase Order if applicable Service Acceptor (DoDAAC) See Award/Purchase Order if applicable Accept at Other DoDAAC See Award/Purchase Order if applicable LPO DoDAAC DCAA Auditor DoDAAC Other DoDAAC(s)

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

Additional email notifications are not required.

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

PAGE 3 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

Contact the local contract administrator found in block 6 of the DD 1155, block 9 of the SF 1449, or block 5 of the SF 26.

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

(End of clause)

PAGE 4 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

SECTION B

SUPPLIES/SERVICES: 2541-01-557-6129

ITEM DESCRIPTION:

WINDOW, SIDE FRONT, LEFT HAND.

RP001: DLA PACKAGING REQUIREMENTS FOR PROCUREMENT

RA001: THIS DOCUMENT INCORPORATES TECHNICAL AND/OR QUALITY REQUIREMENTS

(IDENTIFIED BY AN 'R' OR AN 'I' NUMBER) SET FORTH IN FULL TEXT IN THE

DLA MASTER LIST OF TECHNICAL AND QUALITY REQUIREMENTS FOUND ON THE WEB

AT: http://www.dla.mil/HQ/Acquisition/Offers/eProcurement.aspx. FOR

SIMPLIFIED ACQUISITIONS, THE REVISION OF THE MASTER IN EFFECT ON THE

SOLICITATION ISSUE DATE OR THE AWARD DATE CONTROLS. FOR LARGE

ACQUISITIONS, THE REVISION OF THE MASTER IN EFFECT ON THE RFP ISSUE DATE

APPLIES UNLESS A SOLICITATION AMENDMENT INCORPORATES A FOLLOW-ON

REVISION, IN WHICH CASE THE AMENDMENT DATE CONTROLS.

RQ001: HIGHER LEVEL CONTRACT QUALITY REQUIREMENTS (MANUFACTURERS AND

NON-MANUFACTURERS)

RQ002: CONFIGURATION CHANGE MANAGEMENT - ENGINEERING CHANGE PROPOSAL

REQUEST FOR VARIANCE (DEVIATION OR WAIVER)

RQ009: INSPECTION AND ACCEPTANCE AT ORIGIN

RQ011: REMOVAL OF GOVERNMENT IDENTIFICATION FROM NON-ACCEPTED SUPPLIES

RC001: DOCUMENTATION REQUIREMENTS FOR SOURCE APPROVAL REQUEST (SAR)

THIS IS A BALLISTIC WINDOW WITH "CLEAR" GLASS.

For Production Lot Testing CLIN: All Suppliers must meet the production lot testing requirements listed in ATPD 2352, referenced in the solicitation.

NOTE: ALL TRANSPARENT ARMOR MUST BE APPROVED AND TESTED BY ENGINEERING

SUPPORT ACTIVITY.

THIS ITEM HAS TECHNICAL DATA SOME OR ALL OF WHICH IS SUBJECT TO

EXPORT-CONTROL REGULATIONS. DISTRIBUTION OF THE TECHNICAL DATA AND

ELIGIBILITY FOR AWARD ARE LIMITED TO THOSE SUPPLIERS QUALIFIED THROUGH

PAGE 5 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

SUPPLY/SERVICE: 2541-01-557-6129 CONT'D

JCP CERTIFICATION, OR TO THOSE LICENSED BY EITHER THE DEPARTMENTS OF

STATE OR COMMERCE; OR TO FOREIGN SUPPLIERS PURSUANT TO INTERNATIONAL

AGREEMENTS.

TO APPLY FOR JCP CERTIFICATION, COMPLETE DD FORM 2345, MILITARY CRITICAL

TECHNICAL DATA AGREEMENT, FORM IS AVAILABLE AT THE WORLD WIDE WEB

ADDRESS:

https://public.logisticsinformationservice.dla.mil/PublicHome/jcp/defaul t.aspx

OR BY WRITING TO:

DLA LOGISTICS INFORMATION SERVICE

FEDERAL CENTER

74 WASHINGTON AVE., NORTH

BATTLE CREEK, MI 49037-3084

TO MANUFACTURE THIS ITEM, NON-JCP CERTIFIED SUPPLIERS MUST SUBMIT A

CURRENT MANUFACTURING LICENSE AGREEMENT, TECHNICAL ASSISTANCE AGREEMENT,

DISTRIBUTION AGREEMENT OR OFF-SHORE PROCUREMENT AGREEMENT APPROVED BY

THE DIRECTORATE OF DEFENSE TRADE CONTROLS WITH THE OFFER, UNLESS AN

EXEMPTION UNDER THE PROVISIONS OF ITAR SECTION, 125.4 EXEMPTIONS OF

GENERAL APPLICABILITY, AND/OR EAR PART 740 ARE APPLICABLE.

NON-JCP CERTIFIED SUPPLIERS SEEKING EXPORT CONTROLLED TECHNICAL DATA ARE

REQUIRED TO PROVIDE THE CONTRACTING OFFICER WITH AN APPLICABLE AGREEMENT

OR IDENTIFY WHICH ITAR/EAR EXEMPTION APPLIES TO RECEIVE A COPY OF THE

EXPORT CONTROLLED TECHNICAL DATA.

NOTE: JCP CERTIFIED CONTRACTORS WHO RECEIVE TECHNICAL DATA PURSUANT TO

THEIR DD FORM 2345 CERTIFICATION MAY NOT FURTHER DISSEMINATE SUCH DATA

UNLESS FURTHER DISSEMINATION OF THE TECHNICAL DATA IS EXPRESSLY

PERMITTED BY DODD 5230.25.

CLASS I OZONE DEPLETING CHEMICALS ARE NOT TO BE

USED NOR INCORPORATED IN ANY ITEMS TO BE

DELIVERED UNDER THIS CONTRACT.THIS PROHIBITION

SUPERSEDES ALL SPECIFICATION REQUIREMENTS BUT

DOES NOT ALLEVIATE ANY PRODUCT REQUIREMENTS.

SUBSTITUTE CHEMICALS MUST BE SUBMITTED FOR

APPROVAL UNLESS THEY ARE AUTHORIZED BY THE

SPECIFICATION REQUIREMENTS.

NOTE: THIS IS A RESTRICTED SOURCE ITEM AND

REQUIRES ENGINEERING SOURCE APPROVAL BY THE

GOVERNMENT DESIGN CONTROL ACTIVITY.

The following Contract Data Requirements Lists (CDRLs), DD Form 1423s, apply to this procurement. Review the Technical Data Package (TDP) for additional information.

PAGE 6 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

Oran Safety Glass, Inc. 4M0Z0 P/N 4109043SCN13571

SIERRACINSYLMAR CORPORATION DBA 71355 P/N 707650-01

IAW REFERENCE DRAWING NR 19200 ATPD-2352

REVISION NR T DTD 05/08/2013

PART PIECE NUMBER:

IAW REFERENCE QAP 16236 SQAPATPD2352

REVISION NR B DTD 10/12/2017

PART PIECE NUMBER:

IAW REFERENCE QAP 16236 ATPD-DD-CLARIFICATION-LETTER

REVISION NR A DTD 10/17/2017

PART PIECE NUMBER:

IAW REFERENCE QAP 16236 CDRL-PLT-BALLISTIC

REVISION NR DTD 06/06/2016

PART PIECE NUMBER:

ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT .

0001 2541-01-557-6129 220.000 EA $ ________________ $ ________________

ARMOR,TRANSPARENT

,V

PRICING TERMS: Firm Fixed Price

QTY VARIANCE: PLUS 0% MINUS 0%

INSPECTION POINT: ORIGIN

ACCEPTANCE POINT: ORIGIN

FOB: ORIGIN DELIVERY DATE: 250 DAYS ADO

PREP FOR DELIVERY:

PKGING DATA - MIL-STD-2073-1D, 15 DEC 1999

QUP:001 PRES MTHD:10 CLNG/DRY:1 PRESV MAT:00

WRAP MAT:CA CUSH/DUNN MAT:AD CUSH/DUNN THKNESS:D

UNIT CONT:F2 OPI:M

PACK CODE:U

MARKING SHALL BE IN ACCORDANCE WITH MIL-STD-129.

SPECIAL MARKING CODE:ZZ -ZZ Special Requirements

PALLETIZATION SHALL BE IN ACCORDANCE WITH MD00100452 REV B DATED JULY 01, 2008

PAGE 7 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

SPECIAL MARKING REQUIREMENTS:

ZZ -ADDITIONAL SPECIAL MARKING:

Protected Cargo (Controlled, Sensitive, Classified, Pilferable items).

Special Marking Code 40 applies -- "Markings shall be omitted for sensitive, controlled or pilferable items per MIL-STD-129."

The item description (nomenclature) shall be omitted from all shipping containers of protected cargo. See MIL-STD-129, paragraph 5.4.1.6 (Protected Cargo) for more information.

In addition to MIL-STD-129 markings, each MRAP palletized shipment shall include two, 10 inch by 10 inch fluorescent yellow sticker/sign/placard with the letters MRAP in 2 inch bold black letters and applied to one side and one panel of palletized load. For better visibility, place the MRAP sticker/sign/placard on the outside of the multiwall container(s) or the pallet, not under any shrink-wrap. The stickers are to be placed high on each side of each container, so they are visible at eye level.

This sticker/sign/placard is required to expedite the receipt and inspection of these shipments. This requirement is only applicable for shipments directed to DDC depots and direct vendor deliveries to CCPs;

and does not apply to direct vendor deliveries to the customer.

ACCEPTABLE DEVIATIONS: Contractor is authorized to make adjustments to actual sticker size and font size when shipping containers are not large enough to adequately display all required MIL-STD-129 markings along with the standard size (as cited above).

OEM MRAP STICKERS: Each OEM has a designated background color in lieu of the standard yellow background MRAP sticker in an effort to apply Lean Six Sigma principles and concepts to packaging, storage, and transport of MRAP material to theater. The following are the official designations (background color # text required):

GREEN # MRAP BAE (TX)

TEAL # MRAP OSHKOSH

PURPLE # MRAP BAE (PA)

ORANGE # MRAP FPII

BLUE # MRAP NAVISTAR

PINK # MRAP GDLS

NOTE: If MRAP stickers are missing or OEM is exhausting yellow background stickers, no quality notification shall be submitted to Contract Administrating Activity.

PARCEL POST ADDRESS:

W25G1U

PAGE 8 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

W1A8 DLA DISTRIBUTION

DDSP NEW CUMBERLAND FACILITY

2001 NORMANDY DRIVE DOOR 113 TO 134

NEW CUMBERLAND PA 17070-5002

US

FOR TRANSPORTATION ASSISTANCE SEE DLAD 52.247-9034. FOR FIRST DESTINATION TRANSPORTATION (FDT) AWARDS SEE

DLAD 52.247-9059 AND

CONTRACT INSTRUCTIONS INSTEAD.

FREIGHT SHIPPING ADDRESS:

W25G1U

W1A8 DLA DISTRIBUTION

DDSP NEW CUMBERLAND FACILITY

2001 NORMANDY DRIVE DOOR 113 TO 134

NEW CUMBERLAND PA 17070-5002

US

Production Lot Testing (Contractor)

ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT .

0002 0001 - S00000062 1.000 EA $ ________________ $ ________________

PRICING TERMS: Firm Fixed Price

INSPECTION POINT: ORIGIN

ACCEPTANCE POINT: ORIGIN

FOB: ORIGIN DELIVERY DATE: 90 DAYS ADO

PREP FOR DELIVERY:

Not Applicable

PAGE 9 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

GOVT USE

External External External Customer RDD/ ITEM PR PRLI PR PRLI Material Need Ship Date .

0001 0071145193 0001 N/A N/A 2510015576129 10/25/2018 0002 N/A N/A N/A N/A N/A N/A

PAGE 10 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

SECTION A - SOLICITATION/CONTRACT FORM

TECHNICAL REQUIREMENTS

THIS DOCUMENT INCORPORATES TECHNICAL AND/OR QUALITY REQUIREMENTS (IDENTIFIED BY AN `R' OR AN `I' NUMBER IN SECTION B) SET FORTH IN FULL TEXT IN THE DLA MASTER LIST OF TECHNICAL AND QUALITY REQUIREMENTS FOUND ON THE WEB AT: http://www.dla.mil/HQ/Acquisition/Offers/eProcurement.aspx. FOR SIMPLIFIED ACQUISITIONS, THE REVISION OF THE MASTER IN EFFECT ON THE SOLICITATION ISSUE DATE OR THE AWARD DATE CONTROLS. FOR LARGE ACQUISITIONS, THE REVISION OF THE MASTER IN EFFECT ON THE RFP ISSUE DATE APPLIES UNLESS A SOLICITATION AMENDMENT INCORPORATES A FOLLOW-ON REVISION, IN WHICH CASE THE AMENDMENT DATE CONTROLS.

SECTION C - SPECIFICATIONS/SOW/SOO/ORD

C03 CONTRACTOR RETENTION OF SUPPLY CHAIN TRACEABILITY DOCUMENTATION (SEP 2016)

SECTION D - PACKAGING AND MARKING

252.211-7006 RADIO FREQUENCY IDENTIFICATION (SEP 2011) DFARS

(b)(1) Except as provided in paragraph (b)(2) of this clause, the Contractor shall affix passive RFID tags, at the case- and palletized-unit-load packaging levels, for shipments of items that—

(i) Are in any of the following classes of supply, as defined in DoD 4140.1-R, DoD Supply Chain Materiel Management Regulation, AP1.1.11:

(A) Subclass of Class I – Packaged operational rations.

(B) Class II – Clothing, individual equipment, tentage, organizational tool kits, hand tools, and administrative and housekeeping supplies and equipment.

(C) Class IIIP – Packaged petroleum, lubricants, oils, preservatives, chemicals, and additives.

(D) Class IV – Construction and barrier materials.

(E) Class VI – Personal demand items (non-military sales items).

(F) Subclass of Class VIII – Medical materials (excluding pharmaceuticals, biologicals, and reagents – suppliers should limit the mixing of excluded and non-excluded materials).

(G) Class IX – Repair parts and components including kits, assemblies and subassemblies, reparable and consumable items required for maintenance support of all equipment, excluding medical-peculiar repair parts; and

(ii) Are being shipped to one of the locations listed at http://www.acq.osd.mil/log/rfid/ or to—

(A) A location outside the contiguous United States when the shipment has been assigned Transportation Priority 1, or to—

(B) The following location(s) deemed necessary by the requiring activity:

Contract Line, Subline, or Exhibit Line Item Number

Location Name

City

State

DoDAAC

(2) The following are excluded from the requirements of paragraph (b)(1) of this clause:

(i) Shipments of bulk commodities.

(ii) Shipments to locations other than Defense Distribution Depots when the contract includes the clause at FAR 52.213-1, Fast Payment Procedures.

(c) The Contractor shall—

(1) Ensure that the data encoded on each passive RFID tag are globally unique (i.e., the tag ID is never repeated across two or more RFID tags and conforms to the requirements in paragraph (d) of this clause;

(2) Use passive tags that are readable; and

(3) Ensure that the passive tag is affixed at the appropriate location on the specific level of packaging, in accordance with MIL-STD-129 (Section 4.9.2) tag placement specifications.

PAGE 11 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

http://www.acq.osd.mil/log/rfid/

(d) Data syntax and standards. The Contractor shall encode an approved RFID tag using the instructions provided in the EPC™ Tag Data Standards in effect at the time of contract award. The EPC™ Tag Data Standards are available at http://www.epcglobalinc.org/standards/.

(1) If the Contractor is an EPCglobal™ subscriber and possesses a unique EPC™ company prefix, the Contractor may use any of the identifiers and encoding instructions described in the most recent EPC™ Tag Data Standards document to encode tags.

(2) If the Contractor chooses to employ the DoD identifier, the Contractor shall use its previously assigned Commercial and Government Entity (CAGE) code and shall encode the tags in accordance with the tag identifier details located at http://www.acq.osd.mil/log/rfid/tag_data.htm. If the Contractor uses a third-party packaging house to encode its tags, the CAGE code of the third-party packaging house is acceptable.

(3) Regardless of the selected encoding scheme, the Contractor with which the Department holds the contract is responsible for ensuring that the tag ID encoded on each passive RFID tag is globally unique, per the requirements in paragraph (c)(1).

(e) Advance shipment notice. The Contractor shall use Wide Area WorkFlow (WAWF), as required by DFARS 252.232-7003, Electronic Submission of Payment Requests, to electronically submit advance shipment notice(s) with the RFID tag ID(s) (specified in paragraph

(d) of this clause) in advance of the shipment in accordance with the procedures at https://wawf.eb.mil/.

(End of clause)

SECTION E - INSPECTION AND ACCEPTANCE

52.246-2 INSPECTION OF SUPPLIES FIXED PRICE (AUG 1996) FAR

52.246-11 HIGHER-LEVEL CONTRACT QUALITY REQUIREMENT (DEC 2014) FAR

As prescribed in 46.311, insert the following clause:

(a) The Contractor shall comply with the higher-level quality standard(s) listed below.

Title Number Date Tailoring

[Contracting Officer insert the title, number, date, and tailoring (if any) of the higher-level quality standards.]

(b) The Contractor shall include applicable requirements of the higher-level quality standard(s) listed in paragraph (a) of this clause and the requirement to flow down such standards, as applicable, to lower-tier subcontracts, in—

(1) Any subcontract for critical and complex items (see 46.203(b) and (c)); or

(2) When the technical requirements of a subcontract require—

(i) Control of such things as design, work operations, in-process control, testing, and inspection; or

(ii) Attention to such factors as organization, planning, work instruction, documentation control, and advanced metrology.

(End of Clause)

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

E05 PRODUCT VERIFICATION TESTING (SEP 2016)

E06 INSPECTION AND ACCEPTANCE AT ORIGIN (SEP 2016)

The contractor shall indicate the location where supplies will be inspected:

Commercial and Government Entity (CAGE) code:

Address:

PAGE 12 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

SPE7L3-18-Q-0108

http://www.epcglobalinc.org/standards/ http://www.acq.osd.mil/log/rfid/tag_data.htm http://www.acq.osd.mil/dpap/dars/dfars/html/current/252232.htm http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/dfars/%20https:/wawf.eb.mil/ http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/46.htm#P133_20154

Applicable to contract line-item numbers(s) (CLIN(s)):

The contractor shall indicate the location where packaging will be inspected:

( ) Same as for supplies OR CAGE code:

Address:

Applicable to CLIN(s):

52.246-9008 INSPECTION AND ACCEPTANCE AT ORIGIN (AUG 2007), ALT I (AUG 2007) DLAD

E03 PRODUCTION LOT TESTING – CONTRACTOR (SEP 2016)

(1) The purpose of production lot testing (PLT) is to validate quality conformance of products. PLT is to be completed on the production lot(s) after First Article approval, when a first article is required. The contractor shall price the PLT CLIN to cover the cost of the approved samples that are consumed, destroyed, or otherwise rendered unusable during testing.

(2) The contractor shall provide written notice to the contracting officer and the QAR of the time and location of the test at least fourteen (14) calendar days (or as otherwise specified in the contract) prior to the production lot test so the Government may witness the test.

(3) The QAR will select [12] samples at random from the production lot(s) produced.

(4) The contractor shall perform all tests on the PLT samples to verify/validate for the QAR that the items meet the contract technical/quality requirements.

(5) If a PLT sample fails, the entire production lot quantity produced fails. The contractor shall notify the contracting officer and propose corrective action, if appropriate.

(6) Prepare and disseminate the PLT report as follows:

(a) Prepare the test report in accordance with data item description DI-NDTI-80809B and mark the test report, “Production Lot Test Report, Contract Number [contractor insert] and Lot/Item Number [contractor insert].”

(b) Present the contractor’s PLT report to the QAR for review.

(c) Include the following documentation with all shipments of PLT Reports: DD Form 1222 and DD Form 250/iRAPT receiving report signed by the QAR; a copy of the contract/order; a copy of all applicable test reports showing actual results and tolerances specified in the technical data package; material and process certifications; process operations and inspection method sheets;

copies of drawings used to manufacture the PLT sample with proper marking to restrict public disclosure (if desired) and from Government use other than for evaluation to the extent consistent with the Government’s data rights under the contract, and documents required under a contract deliverables requirements list, if applicable.

(d) Submit all required documentation to the Government activity specified in the contract in time to allow for at least [14] calendar day period for review of the PLT report, and for the contracting officer to provide written notification of approval/disapproval to the contractor.

SECTION F - DELIVERIES OR PERFORMANCE

52.211-17 DELIVERY OF EXCESS QUANTITIES (SEP 1989) FAR

52.242-15 STOP-WORK ORDER (AUG 1989) FAR

52.242-17 GOVERNMENT DELAY OF WORK (APR 1984) FAR

SECTION I - CONTRACT CLAUSES

52.203-18 PROHIBITION ON CONTRACTING WITH ENTITIES THAT REQUIRE CERTAIN INTERNAL CONFIDENTIALITY

AGREEMENTS OR STATEMENTS-REPRESENTATION (JAN 2017) FAR

52.203-19 PROHIBITION ON REQUIRING CERTAIN INTERNAL CONFIDENTIALITY AGREEMENTS OR STATEMENTS (JAN

2017) FAR

252.203-7000 REQUIREMENTS RELATING TO COMPENSATION OF FORMER DOD OFFICIALS (OCT 2016) DFARS

PAGE 13 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

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

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

AGREEMENTS (NOV 2016) DFARS

52.204-10 REPORTING EXECUTIVE COMPENSATION AND FIRST-TIER SUBCONTRACT AWARDS (OCT 2016) FAR

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

52.204-16 COMMERCIAL AND GOVERNMENT ENTITY CODE REPORTING (JUL 2015) FAR

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

52.204-19 INCORPORATION BY REFERENCE OF REPRESENTATIONS AND CERTIFICATIONS (DEC 2014) FAR

52.204-20 PREDECESSOR OF OFFEROR (JUL 2016) FAR

As prescribed in 4.1804(d), insert the following provision:

(a) Definitions. As used in this provision– “Commercial and Government Entity (CAGE) code” means–

(1) An identifier assigned to entities located in the United States or its outlying areas by the Defense Logistics Agency (DLA) Commercial and Government Entity (CAGE) Branch to identify a commercial or government entity; or

(2) An identifier assigned by a member of the North Atlantic Treaty Organization (NATO) or by the NATO Support and Procurement Agency (NSPA) to entities located outside the United States and its outlying areas that the DLA Commercial and Government Entity (CAGE) Branch records and maintains in the CAGE master file. This type of code is known as a NATO CAGE (NCAGE) code.

“Predecessor” means an entity that is replaced by a successor and includes any predecessors of the predecessor.

“Successor” means an entity that has replaced a predecessor by acquiring the assets and carrying out the affairs of the predecessor under a new name (often through acquisition or merger). The term “successor” does not include new offices/divisions of the same company or a company that only changes its name. The extent of the responsibility of the successor for the liabilities of the predecessor may vary, depending on State law and specific circumstances.

(b) The Offeror represents that it [ ] is or [ ] is not a successor to a predecessor that held a Federal contract or grant within the last three years.

(c) If the Offeror has indicated “is” in paragraph (b) of this provision, enter the following information for all predecessors that held a Federal contract or grant within the last three years (if more than one predecessor, list in reverse chronological order):

Predecessor CAGE code: (or mark “Unknown”) Predecessor legal name:

(Do not use a “doing business as” name) (End of provision)

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

252.204-7004 ALTERNATE A, SYSTEM FOR AWRD MANAGEMENT (FEB 2014) DFARS

252.204-7009 LIMITATIONS ON THE USE OR DISCLOSURE OF THIRD-PARTY CONTRACTOR REPORTED CYBER INCIDENT

INFORMATION (OCT 2016) DFARS

(a) Definitions. As used in this clause—

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

“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 defense information” means unclassified information that—

(1) Is—

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

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

(2) Falls in any of the following categories:

PAGE 14 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

https://www.acquisition.gov/sites/default/files/current/far/html/Subpart%204_18.html#wp1076846

(i) Controlled technical information.

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

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

(iv) Any other information, marked or otherwise identified in the contract, that requires safeguarding or dissemination controls 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 a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein.

(b) Restrictions. The Contractor agrees that the following conditions apply to any information it receives or creates in the performance of this contract that is information obtained from a third-party’s reporting of a cyber incident pursuant to DFARS clause 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting (or derived from such information obtained under that clause):

(1) The Contractor shall access and use the information only for the purpose of furnishing advice or technical assistance directly to the Government in support of the Government’s activities related to clause 252.204-7012, and shall not be used for any other purpose.

(2) The Contractor shall protect the information against unauthorized release or disclosure.

(3) The Contractor shall ensure that its employees are subject to use and non-disclosure obligations consistent with this clause prior to the employees being provided access to or use of the information.

(4) The third-party contractor that reported the cyber incident is a third-party beneficiary of the non-disclosure agreement between the Government and Contractor, as required by paragraph (b)(3) of this clause.

(5) A breach of these obligations or restrictions may subject the Contractor to—

(i) Criminal, civil, administrative, and contractual actions in law and equity for penalties, damages, and other appropriate remedies by the United States; and

(ii) Civil actions for damages and other appropriate remedies by the third party that reported the cyber incident, as a third party beneficiary of this clause.

(c) Subcontracts. The Contractor shall include this clause, including this paragraph (c), in subcontracts, or similar contractual instruments, for services that include support for the Government’s activities related to safeguarding covered defense information and cyber incident reporting, including subcontracts for commercial items, without alteration, except to identify the parties.

(End of clause)

252.204-7012 SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT REPORTING (OCT 2016)

DFARS

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

PAGE 15 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

SPE7L3-18-Q-0108

http://www.acq.osd.mil/dpap/dars/dfars/html/current/252204.htm

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

“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 or 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, as soon as practical, but not later than December 31, 2017. The Contractor shall notify the DoD 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; or

PAGE 16 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

SPE7L3-18-Q-0108

http://www.acq.osd.mil/dpap/dars/dfars/html/current/252227.htm#252.227-7013 http://www.acq.osd.mil/dpap/dars/dfars/html/current/252239.htm http://dx.doi.org/10.6028/NIST.SP.800-171 mailto:osd.dibcsia@mail.mil

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

(2) Apply other information systems security measures when the Contractor easonably determines that information systems security 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/Pages/index.aspx.

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

PAGE 17 OF 24 PAGESCONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

SPE7L3-18-Q-0108

http://dibnet.dod.mil/ http://dibnet.dod.mil/ http://iase.disa.mil/pki/eca/Pages/index.aspx

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