SPE4A518Q0437.PDF
PDF 348 KB Posted
- Attached to
- GYROSCOPE, RATE Federal contract opportunity
- Solicitation number
- SPE4A518Q0437
- Issued by
- Defense Logistics Agency Aviation
View the file
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
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)
1. REQUEST NO.
SPE4A5-18-Q-0437
2. DATE ISSUED
2018 FEB 03
3. REQUISITION/PURCHASE REQUEST NO.
0071797214
RATING
DO-A1
DLA AVIATION
ASC SUPPLIER OPER OEM DIVISION
8000 JEFFERSON DAVIS HIGHWAY
RICHMOND VA 23297
USA
Buyer: Gregory Orr DGO0001 Tel: DSN-695-6354 Email: Gregory.Orr@dla.mil
6. DELIVER BY (Date)
150 DAYS ADO
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
2018 FEB 10
NUMBER
FOB DESTINATION
OTHER
(See Schedule)
CAGE
b. TELEPHONE
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: ______________________________
CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 2 OF 21 PAGES
SPE4A5-18-Q-0437
CONTINUED ON NEXT PAGE
C04 UNUSED FORMER GOVERNMENT SURPLUS PROPERTY
DAAN-13-01 Evaluation and Award for Acquisitions Below the Simplified Acquisition Threshold (September 2016)
(b) Relative Important and Trade-offs. The Government will base the determination of best value on a comparative assessment of the quoters' prices, past performance, and the other evaluation factors identified elsewhere in this solicitation. The determination of best value also considers the relative importance of the evaluation factors. All evaluation factors, when combined, are:
[ ] significantly more important than cost or price. As other evaluation factors become more equal, the evaluated cost or price becomes more important.
[ ] approximately equal to cost or price; or
[ ] significantly less important than cost or price. As the evaluated cost/price becomes more equal, relative importance of all other evaluation factors becomes more significant.
(e) Past Performance Evaluation Factors. The Government will use the past performance evaluation factors marked below in addition to cost or price and other evaluation factors specified in the solicitation. Unless indicated otherwise, past performance is significantly more important than other non-price factors. Within the past performance subfactors, PPIRS assessments (as applicable) will be weighed most heavily. Historical quality history and delivery schedule compliance (not captured in PPIRS) will be weighed more heavily than the remaining past performance subfactors. All other non-price evaluation factors specified in this solicitation weigh equally, unless otherwise indicated.
[ ] PPIRS-SR Assessments (52.215-9003) (EProcurement)
[ ] PPIRS-RC Assessments
[ ] Historical Quality (not captured in PPIRS)
[ ] Historical Delivery Schedule Compliance (not captured in PPIRS)
[ ] Other (specify): (End of Notice)
DAAN-13-01 (ALT I) Evaluation and Award for Acquisitions Below the Simplified Threshold (ALT I) (September 2016)
(b) Non-Price Factors. Quoted delivery and past performance will be evaluated equally, unless indicated otherwise below.
( ) Quoted delivery is weighed more heavily than past performance.
( ) Past Performance is weighed more heavily than quoted delivery. (End of Notice)
CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 3 OF 21 PAGES
CONTINUED ON NEXT PAGE
SECTION B
SUPPLIES/SERVICES: 6615-01-247-7713
ITEM DESCRIPTION:
GYROSCOPE,RATE
RP001: DLA PACKAGING REQUIREMENTS FOR PROCUREMENT
RQ001: HIGHER LEVEL CONTRACT QUALITY REQUIREMENTS (MANUFACTURERS AND
NON-MANUFACTURERS)
Item Unique Identification is not required by request of the Service customer. DFARS 252.211-7003(c)(1)(i) applies.
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.
RQ011: REMOVAL OF GOVERNMENT IDENTIFICATION FROM NON-ACCEPTED SUPPLIES
SAMPLING:
THE SAMPLING METHOD SHALL BE IN ACCORDANCE WITH MIL-STD-1916 OR ASQ
H1331, TABLE 1 OR A COMPARABLE ZERO BASED SAMPLING PLAN UNLESS OTHERWISE
SPECIFIED BY THE CONTRACT. IF THE APPLICABLE DRAWING, SPECIFICATION,
STANDARD, OR QUALITY ASSURANCE PROVISION (QAP) SPECIFIES CRITICAL, MAJOR
AND/OR MINOR ATTRIBUTES, THEY SHALL BE ASSIGNED VERIFICAITON LEVELS OF
VII, IV AND II OR AQLS OF 0.1, 1.0 AND 4.0 RESPECTIVELY. UNSPECIFIED
ATTRIBUTES SHALL BE CONSIDERED AS MAJOR UNLESS SAMPLING PLANS ARE
SPECIFIED IN APPLICABLE DOCUMENTS. FOR MIL-STD-1916, THE MANUFACTURER
MAY USE THE ATTRIBUTE OR VARIABLE INSPECTION METHOD AT THEIR OPTION OR
PER THE CONTRACT. MIL-STD-105/ASQ Z1.4 MAY BE USED TO SET SAMPLE LOT
SIZE, BUT ACCEPTANCE WOULD BE ZERO NON-CONFORMANCES IN THE SAMPLE LOT
UNLESS OTHERWISE SPECIFIED IN THE CONTRACT.
CRITICAL APPLICATION ITEM
Atlantic Inertial Systems Inc. DBA 63395 P/N 103144-001
ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT .
0001 6615-01-247-7713 30.000 EA $ ________________ $ ________________
GYROSCOPE,RATE
PRICING TERMS: Firm Fixed Price
QTY VARIANCE: PLUS 0% MINUS 0%
INSPECTION POINT: DESTINATION
ACCEPTANCE POINT: DESTINATION
FOB: ORIGIN DELIVERY DATE: 150 DAYS ADO
PREP FOR DELIVERY:
PKGING DATA - MIL-STD-2073-1D, 15 DEC 1999
QUP:001 PRES MTHD:51 CLNG/DRY:1 PRESV MAT:XX
WRAP MAT:XX CUSH/DUNN MAT:AD CUSH/DUNN THKNESS:X
UNIT CONT:E5 OPI:M
INTRMDTE CONT:E5 INTRMDTE CONT QTY:AAA
PACK CODE:U
MARKING SHALL BE IN ACCORDANCE WITH MIL-STD-129.
SPECIAL MARKING CODE:05 -05 Delicate instrument
CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 4 OF 21 PAGES
CONTINUED ON NEXT PAGE
SECTION B
SUPPLY/SERVICE: 6615-01-247-7713 CONT'D
PALLETIZATION SHALL BE IN ACCORDANCE WITH MD00100452 REV B DATED JULY 01, 2008
PARCEL POST ADDRESS:
SW3119
DLA DISTRIBUTION WARNER ROBINS
455 BYRON STREET
BLDG 376
ROBINS A F B GA 31098-1887
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:
SW3119
DLA DISTRIBUTION WARNER ROBINS
455 BYRON STREET BLDG 376
ROBINS A F B GA 31098-1887
US
GOVT USE
External External External Customer RDD/ ITEM PR PRLI PR PRLI Material Need Ship Date .
0001 0071797214 0001 N/A N/A N/A 06/02/2018
CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 5 OF 21 PAGES
CONTINUED ON NEXT PAGE
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;
http://www.acq.osd.mil/log/rfid/
CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 6 OF 21 PAGES
SECTION D - PACKAGING AND MARKING (CONTINUED)
CONTINUED ON NEXT PAGE
(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.
(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)
SECTION F - DELIVERIES OR PERFORMANCE
52.211-8 TIME OF DELIVERY (JUN 1997) FAR
(a) The Government requires delivery to be made according to the following schedule:
REQUIRED DELIVERY SCHEDULE
ITEM NO. QUANTITY WITHIN DAYS AFTER
DATE OF CONTRACT
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
CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 7 OF 21 PAGES
SECTION F - DELIVERIES OR PERFORMANCE (CONTINUED)
CONTINUED ON NEXT PAGE
ITEM NO. QUANTITY WITHIN DAYS AFTER
DATE OF CONTRACT
The Government will evaluate equally, as regards time of delivery, offers that propose delivery of each quantity within the applicable delivery period specified above. Offers that propose delivery that will not clearly fall within the applicable required delivery period specified above, will be considered nonresponsive and rejected. The Government reserves the right to award under either the required delivery schedule or the proposed delivery schedule, when an offeror offers an earlier delivery schedule than required above. If the offeror proposes no other delivery schedule, the required delivery schedule above will apply.
OFFEROR'S PROPOSED DELIVERY SCHEDULE
ITEM NO. QUANTITY WITHIN DAYS AFTER
DATE OF CONTRACT
(b) Attention is directed to the Contract Award provision of the solicitation that provides that a written award or acceptance of offer mailed, or otherwise furnished to the successful offeror, results in a binding contract. The Government will mail or otherwise furnish to the offeror an award or notice of award not later than the day award is dated. Therefore, the offeror should compute the time available for performance beginning with the actual date of award, rather than the date the written notice of award is received from the Contracting Officer through the ordinary mails. However, the Government will evaluate an offer that proposes delivery based on the Contractor's date of receipt of the contract or notice of award by adding (1) five calendar days for delivery of the award through the ordinary mails, or (2) one working day if the solicitation states that the contract or notice of award will be transmitted electronically. (The term “working day” excludes weekends and U.S. Federal holidays.) If, as so computed, the offered delivery date is later than the required delivery date, the offer will be considered nonresponsive and rejected.
52.211-16 VARIATION IN QUANTITY (APR 1984) FAR
As prescribed in 11.703(a), insert the following clause:
(a) A variation in the quantity of any item called for by this contract will not be accepted unless the variation has been caused by conditions of loading, shipping, or packing, or allowances in manufacturing processes, and then only to the extent, if any, specified in paragraph (b) of this clause.
(b) The permissible variation shall be limited to:
Percent increase [Contracting Officer insert percentage]
Percent decrease [Contracting Officer insert percentage]
This increase or decrease shall apply to .* https://www.acquisition.gov/sites/default/files/current/far/html/Subpart%2011_7.html
CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 8 OF 21 PAGES
SECTION F - DELIVERIES OR PERFORMANCE (CONTINUED)
52.211-17 DELIVERY OF EXCESS QUANTITIES (SEP 1989) FAR
52.242-17 GOVERNMENT DELAY OF WORK (APR 1984) FAR
52.247-29 F.O.B. ORIGIN (FEB 2006) 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
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-13 SYSTEM FOR AWARD MANAGEMENT MAINTENANCE (OCT 2016) FAR
52.204-16 COMMERCIAL AND GOVERNMENT ENTITY CODE REPORTING (JUL 2016) 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) https://www.acquisition.gov/sites/default/files/current/far/html/Subpart%204_18.html
CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 9 OF 21 PAGES
SECTION I - CONTRACT CLAUSES (CONTINUED)
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:
(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.
http://www.acq.osd.mil/dpap/dars/dfars/html/current/252204.htm
CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 10 OF 21 PAGES
SECTION I - CONTRACT CLAUSES (CONTINUED)
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 --
(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.
CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 11 OF 21 PAGES
SECTION I - CONTRACT CLAUSES (CONTINUED)
CONTINUED ON NEXT PAGE
“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
(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 http://www.acq.osd.mil/dpap/dars/dfars/html/current/252227.htm 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 http://dibnet.dod.mil/
CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 12 OF 21 PAGES
SECTION I - CONTRACT CLAUSES (CONTINUED)
CONTINUED ON NEXT PAGE
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.
(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 a covered contractor information system, including subcontracts for commercial items, without alteration, except to identify the parties; and
(2) When this clause is included in a subcontract, require subcontractors to rapidly report cyber incidents directly to DoD at http://dibnet.dod.
mil and the prime Contractor. This includes providing the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable.
http://iase.disa.mil/pki/eca/Pages/index.aspx
CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 13 OF 21 PAGES
SECTION I - CONTRACT CLAUSES (CONTINUED)
CONTINUED ON NEXT PAGE
52.209-1 QUALIFICATION REQUIREMENTS (FEB 1995) FAR
(a) Definition. “Qualification requirement,” as used in this clause, means a Government requirement for testing or other quality assurance demonstration that must be completed before award.
(b) One or more qualification requirements apply to the supplies or services covered by this contract. For those supplies or services requiring qualification, whether the covered product or service is an end item under this contract or simply a component of an end item, the product, manufacturer, or source must have demonstrated that it meets the standards prescribed for qualification before award of this contract. The product, manufacturer, or source must be qualified at the time of award whether or not the name of the product, manufacturer, or source is actually included on a qualified products list, qualified manufacturers list, or qualified bidders list. Offerors should contact the agency activity designated below to obtain all requirements that they or their products or services, or their subcontractors or their products or services, must satisfy to become qualified and to arrange for an opportunity to demonstrate their abilities to meet the standards specified for qualification.
http://assist.daps.dla.mil/quicksearch/
(c) If an offeror, manufacturer, source, product or service covered by a qualification requirement has already met the standards specified, the relevant information noted below should be provided.
Offeror's Name: __________________________________
Manufacturer's Name: _____________________________
Source's Name: __________________________________
Item Name: ______________________________________
Service Identification: ______________________________
Test Number: ____________________________________
(to the extent known)
(d) Even though a product or service subject to a qualification requirement is not itself an end item under this contract, the product, manufacturer, or source must nevertheless be qualified at the time of award of this contract. This is necessary whether the Contractor or a subcontractor will ultimately provide the product or service in question. If, after award, the Contracting Officer discovers that an applicable qualification requirement was not in fact met at the time of award, the Contracting Officer may either terminate this contract for default or allow performance to continue if adequate consideration is offered and the action is determined to be otherwise in the Government's best interests.
(e) If an offeror, manufacturer, source, product or service has met the qualification requireme nt but is not yet on a qualified products list, qualified manufacturers list, or qualified bidders list, the offeror must submit evidence of qualification prior to award of this contract. Unless determined to be in the Government's interest, award of this contract shall not be delayed to permit an offeror to submit evidence of qualification.
(f) Any change in location or ownership of the plant where a previously qualified product or service was manufactured or performed requires reevaluation of the qualification. Similarly, any change in location or ownership of a previously qualified manufacturer or source requires reevaluation of the qualification. The reevaluation must be accomplished before the date of award.
52.211-5 MATERIAL REQUIREMENTS (AUG 2000) FAR
252.211-7005 SUBSTITUTIONS FOR MILITARY OR FEDERAL SPECIFICATIONS AND STANDARDS (NOV 2005) DFARS
(4) If the proposed SPI process has been accepted at the facility at which it is proposed for use, but is not yet listed at the Internet site specified in paragraph (b) of this clause, submit documentation of Department of Defense acceptance of the SPI process.
(d) Absent a determination that an SPI process is not acceptable for this procurement, the Contractor shall use the following SPI processes in lieu of military or Federal specifications or standards:
(Offeror insert information for each SPI process) SPI Process:
CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 14 OF 21 PAGES
SECTION I - CONTRACT CLAUSES (CONTINUED)
CONTINUED ON NEXT PAGE
Facility:
Military or Federal Specification or Standard:
Affected Contract Line Item Number, Subline Item Number, Component, or Element:
52.215-8 ORDER OF PRECEDENCE - UNIFORM CONTRACT FORMAT (OCT 1997) FAR
52.222-19 CHILD LABOR - COOPERATION WITH AUTHORITIES AND REMEDIES (OCT 2016) FAR
52.222-50 COMBATTING TRAFFICKING IN PERSONS (MAR 2015) FAR
52.223-18 ENCOURAGING CONTRACTOR POLICIES TO BAN TEXT MESSAGING WHILE DRIVING (AUG 2011) FAR
52.225-13 RESTRICTIONS ON CERTAIN FOREIGN PURCHASES (JUN 2008) FAR
252.225-7001 BUY AMERICAN AND BALANCE OF PAYMENTS PROGRAM—BASIC (DEC 2016) DFARS
252.225-7001 BUY AMERICAN AND BALANCE OF PAYMENTS PROGRAM—BASIC (DEC 2016), ALT I (DEC 2016) DFARS
252.225-7002 QUALIFYING COUNTRY SOURCES AS SUBCONTRACTORS (DEC 2016) DFARS
52.232-1 PAYMENTS (APR 1984) FAR
52.232-8 DISCOUNTS FOR PROMPT PAYMENT (FEB 2002) FAR
52.232-11 EXTRAS (APR 1984) FAR
52.232-25 PROMPT PAYMENT (JAN 2017) FAR
52.232-33 PAYMENT BY ELECTRONIC FUNDS TRANSFER-SYSTEM FOR AWARD MANAGEMENT (JUL 2013) FAR
52.232-40 PROVIDING ACCELERATED PAYMENTS TO SMALL BUSINESS SUBCONTRACTORS (DEC 2013) FAR
252.232-7003 ELECTRONIC SUBMISSION OF PAYMENT REQUESTS AND RECEIVING REPORTS (JUN 2012) DFARS
252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (MAY 2013) DFARS
As prescribed in 232.7004(b), use the following clause:
(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-
CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 15 OF 21 PAGES
(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).
(Contracting Officer: Insert applicable document type(s).
Note: If a “Combo” document type is identified but not supportable by the Contractor's business systems, an “Invoice” (stand-alone) and “Receiving Report” (stand-alone) document type may be used instead.)
(2) Inspection/acceptance location. The Contractor shall select the following inspection/acceptance location(s) in WAWF, as specified by the contracting officer.
(Contracting Officer: Insert inspection and acceptance locations or “Not applicable.”)
(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.
Routing Data Table*
Field Name in WAWF Data to be entered in
WAWF
Pay Official DoDAAC Issue By DoDAAC Admin DoDAAC
Inspect By DoDAAC Ship To Code
Ship From Code Mark For Code
Service Approver (DoDAAC)
Service Acceptor (DoDAAC)
Accept at Other DoDAAC LPO DoDAAC
DCAA Auditor DoDAAC Other DoDAAC(s)
(*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…
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.