18R0019_Solicitation.docx
DOCX document 120 KB Posted
- Attached to
- HARM Thermal Battery
- Solicitation number
- N6893618R0019
About this file
N6893618R0019 Solicitation
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 18R0019_Solicitation_Amendment.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
N6893618R0019
Section A - Solicitation/Contract Form
CLAUSES INCORPORATED BY FULL TEXT
FOR YOUR INFORMATION:
The following addresses and points of contact are provided:
PROCURING CONTRACTING OFFICER
| Name: | Tara Brandt |
| Phone: | (760) 939- 2719 |
| DSN: | 437- 2719 |
| FAX: | (760) 939-2719 |
Email address: tara.brandt@navy.mil
U.S. Postal Service Mailing Address:
| COMMANDER |
| CODE 25440D (T. BRANDT – 760-939-2719) |
| NAVAIRWARCENWPNDIV |
| 1 Administration Circle, MAIL STOP 1303 |
| BLDG 02334 |
| CHINA LAKE, CA 93555-6108 |
Direct Delivery Address (UPS, FedEx, etc.):
| COMMANDER |
| CODE 25440D (T. BRANDT) |
| NAVAIRWARCENWPNDIV |
| BLDG 02334, MAIL STOP 1303 |
| CHINA LAKE, CA 93555-6108 |
CONTRACT SPECIALIST
| Name: | Rhett Beswick |
| Phone: | (760) 939- 2352 |
| DSN: | 437- 2352 |
| FAX: | (760) 939-2352 |
Email address: rhett.beswick@navy.mil
U.S. Postal Service Mailing Address:
| COMMANDER |
| CODE 254320D (R. BESWICK – 760-939-2352) |
| NAVAIRWARCENWPNDIV |
| 1 Administration Circle, MAIL STOP 1303 |
| BLDG 02334 |
| CHINA LAKE, CA 93555-6108 |
Direct Delivery Address (UPS, FedEx, etc.):
| COMMANDER |
| CODE 254320D (R. BESWICK) |
| NAVAIRWARCENWPNDIV |
| BLDG 02334, MAIL STOP 1303 |
| CHINA LAKE, CA 93555-6108 |
Section B - Supplies or Services and Prices
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
| 600 |
| Each |
Batteries
FFP
The contractor shall deliver batteries in accordance with with the Section C: Statement of Work.
FOB: Destination
PURCHASE REQUEST NUMBER: 1300681458
NET AMT
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
| 600 |
| Each |
Batteries
FFP
The contractor shall deliver batteries in accordance with with the Section C: Statement of Work.
NET AMT
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
| 600 |
| Each |
| OPTION |
| Batteries |
FFP
NET AMT
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
| 600 |
| Each |
| OPTION |
| Batteries |
FFP
NET AMT
Section D - Packaging and Marking
| 5252.247-9508 | PROHIBITED PACKING MATERIALS (NAVAIR)(JUN 1998) |
| The use of asbestos, excelsior, newspaper or shredded paper (all types including waxed paper, computer paper and similar hydroscopic or non-neutral material) is prohibited. In addition, loose fill polystyrene is prohibited for shipboard use. |
Section E - Inspection and Acceptance
INSPECTION AND ACCEPTANCE TERMS
Supplies/services will be inspected/accepted at:
| CLIN |
| INSPECT AT |
| INSPECT BY |
| ACCEPT AT |
| ACCEPT BY |
| 0001 |
| Destination |
| Government |
| Destination |
| Government |
| 0002 |
| Destination |
| Government |
| Destination |
| Government |
| 0003 |
| Destination |
| Government |
| Destination |
| Government |
| 0004 |
| Destination |
| Government |
| Destination |
| Government |
CLAUSES INCORPORATED BY REFERENCE
| 52.246-2 |
| Inspection Of Supplies--Fixed Price |
| AUG 1996 |
| 52.246-16 |
| Responsibility For Supplies |
| APR 1984 |
| 252.246-7000 |
| Material Inspection And Receiving Report |
| MAR 2008 |
| 5252.246-9512 | INSPECTION AND ACCEPTANCE (NAVAIR)(OCT 2005) |
| (a) Inspection and acceptance of the supplies or services to be furnished hereunder shall be performed by the Government. | |
| (b) Acceptance of all Contract Line Items/Sub Line Items (CLINs/SLINs) shall be made by signature of the accepting authority on a DD 250 submitted through the WAWF system. Acceptance will only occur when the accepting authority is sure that inspections performed demonstrate compliance with contract requirements. |
Section F - Deliveries or Performance
DELIVERY INFORMATION
| CLIN |
| DELIVERY DATE |
| QUANTITY |
| SHIP TO ADDRESS |
| DODAAC / CAGE |
| 0001 |
| 30-SEP-2018 |
| 600 |
| LETTERKENNY MUNITIONS CENTER |
J.F. CARBAUGH
RTE 997, VOELZ GATE
CHAMBERSBURG PA 17201-4150
717-267-8615
W25G1R
| 0002 |
| 30-SEP-2018 |
| 600 |
| (SAME AS PREVIOUS LOCATION) |
W25G1R
| 0003 |
| 30-SEP-2019 |
| 600 |
| (SAME AS PREVIOUS LOCATION) |
W25G1R
| 0004 |
| 30-SEP-2020 |
| 600 |
| (SAME AS PREVIOUS LOCATION) |
W25G1R
| 52.211-17 |
| Delivery of Excess Quantities |
| SEP 1989 |
| 52.242-15 |
| Stop-Work Order |
| AUG 1989 |
| 52.242-17 |
| Government Delay Of Work |
| APR 1984 |
| 52.247-34 |
| F.O.B. Destination |
| NOV 1991 |
Section G - Contract Administration Data
| 252.232-7006 | WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (MAY 2013) | |
| (a) Definitions, as used in this clause-- | ||
| "Department of Defense Activity Address Code (DoDAAC)" is a six position code that uniquely identifies a unit, activity, or organization. | ||
| "Document type" means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF). | ||
| "Local processing office (LPO)" is the office responsible for payment certification when payment certification is done external to the entitlement system. | ||
| (b) Electronic invoicing. The WAWF system is the method to electronically process vendor payment requests and receiving reports, as authorized by DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports. | ||
| (c) WAWF access. To access WAWF, the Contractor shall-- | ||
| (1) Have a designated electronic business point of contact in the System for Award Management at https://www.acquisition.gov; and | ||
| (2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this Web site. | ||
| (d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the "Web Based Training" link on the WAWF home page at https://wawf.eb.mil/. | ||
| (e) WAWF methods of document submission. Document submissions may be via Web entry, Electronic Data Interchange, or File Transfer Protocol. | ||
| (f) WAWF payment instructions. The Contractor must use the following information when submitting payment requests and receiving reports in WAWF for this contract/order: | ||
| (1) Document type. The Contractor shall use the following document type(s). | ||
| COMBO | ||
| (2) Inspection/acceptance location. The Contractor shall select the following inspection/acceptance location(s) in WAWF, as specified by the contracting officer. | ||
| 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: | N64141 | |||
| Issue By DoDAAC: | N68936 | |||
| Admin DoDAAC: | N68936 | |||
| Inspect By DoDAAC: | N68936 | |||
| Ship To Code: | N68936 | |||
| 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 defined in DFARS Appendix F, (e.g. timesheets) in support of each payment request. | ||||
| (5) WAWF email notifications. The Contractor shall enter the email address identified below in the "Send Additional Email Notifications" field of WAWF once a document is submitted in the system. |
Not applicable
| (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. For Navy WAWF questions call DFAS Customer Care 1-800-756-4571 option 6 | |
| (2) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988. |
| 5252.201-9500 | TECHNICAL POINT OF CONTACT (TPOC)(NAVAIR)(SEP 2012) |
| (a) The Technical Point of Contact (TPOC) for this contract is: Denice Hunter, 663300D, (760) 939-4576 | |
| (b) This individual is not a Contracting Officer nor a Contracting Officer's Representative (COR)/Task Order COR (TOCOR) and has no authority to make changes, verbally or otherwise, to the existing contract or order. Further, no authority has been delegated to this individual by the Procuring Contracting Officer (PCO). | |
| (c) The contractor may use this technical POC for technical questions related to the existing contract or order. Also, as a representative of the requiring activity, the TPOC may perform or assist in such areas as: base access forms, security related issues, IT access requirements, Contractor Performance Assessment Reporting System (CPARS), clarification of technical requirements, and statement of work inquires. | |
| (d) The contractor shall immediately notify the Procuring Contracting Officer in writing if the contractor interprets any action by the TPOC to be a change to the existing contract. |
| 5252.204-9503 | EXPEDITING CONTRACT CLOSEOUT (NAVAIR) (JAN 2007) |
| (a) As part of the negotiated fixed price or total estimated amount of this contract, both the Government and the Contractor have agreed to waive any entitlement that otherwise might accrue to either party in any residual dollar amount of $1,000 or less at the time of final contract closeout. The term "residual dollar amount" shall include all money that would otherwise be owed to either party at the end of the contract, except that, amounts connected in any way with taxation, allegations of fraud and/or antitrust violations shall be excluded. For purposes of determining residual dollar amounts, offsets of money owed by one party against money that would otherwise be paid by that party might be considered to the extent permitted by law. | |
| (b) This agreement to waive entitlement to residual dollar amounts has been considered by both parties. It is agreed that the administrative costs for either party associated with collecting such small dollar amounts could exceed the amount to be recovered. |
| 5252.242-9511 | CONTRACT ADMINISTRATION DATA (NAVAIR)(SEP 2012) | |
| (a) Contract Administration Office. | ||
| (1) Contract administration functions (see FAR 42.302(a) and DFARS 242.302(a)) are assigned to: See the ADMINISTERED BY Block on the face page of the contract, modification, or order. | ||
| (b) Special Instructions (see FAR 42.202(b) and (c)): | ||
| (1) The following contract administration functions are retained (see FAR 42.302(a) and DFARS 242.302(a)): | ||
| Functions Retained* | ||
| Retained for Performance By*: |
| (3) Conduct post-award orientation conferences. |
| PCO |
| (16) Ensure timely notification by the contractor of any anticipated overrun or underrun of the estimated cost under cost-reimbursement contracts. |
| PCO |
(44) Perform engineering analysis of contractor cost proposals.
PCO
| (47) Assist in evaluation and make recommendations for acceptance or rejection of waivers and deviations. |
| PCO |
| (51) Consent to the placement of subcontracts. |
| PCO |
| (58) Ensure timely submissions of required reports. |
| PCO |
| (70) De-obligate excess funds after final price determination |
| ACO/PCO/COR as required. |
(2) The following additional contract administration functions are assigned (see FAR 42.302(b)):
| Additional Functions |
| Retained for Performance By: |
| All other items not listed above. |
| “See the ADMINISTERED BY Block on the face page of the contract, modification or order”. |
© Inquiries regarding payment should be referred to: MyInvoice at https://myinvoice.csd.disa.mil//index.html.
| G-TXT-01 | ATTENTION! E-MAIL ADDRESS REQUIRED FOR DISTRIBUTION |
| All Naval Air Warfare Center Weapons Division Contracts/ Purchase Orders and other related documents are now distributed by electronic mail. | |
| Please provide the e-mail address to which distribution of contracts/purchase orders should be made. | |
| E-Mail Address:___________________________________________________ |
Section H - Special Contract Requirements
| 5252.211-9502 | GOVERNMENT INSTALLATION WORK SCHEDULE (NAVAIR)(DEC 2014) |
| (a) The Holidays applicable to this contract are: New Year's Day, Martin Luther King's Birthday, Presidents' Birthday, Memorial Day, Independence Day, Labor Day, Columbus Day, Veteran's Day, Thanksgiving Day, and Christmas Day. | |
| (b) In the event that any of the above holidays occur on a Saturday or Sunday, or alternate Friday, then such holiday shall be observed as they are by the assigned Government employees at the using activity. | |
| (c) The Naval Air Warfare Center Weapons Division works a 4/5/9 work schedule. Therefore alternate Fridays are not a part of the normal workweek for work performed on-site at a Naval Air Warfare Center Weapons Division site. The majority of the Government offices are closed on alternate Fridays. | |
| (d) No deviation in the normal workweek will be permitted without express advance approval by the designated Contracting Officer with coordination of the using departments. |
| 5252.211- 9510 | CONTRACTOR EMPLOYEES (NAVAIR)(MAY 2011) | |
| (a) In all situations where contractor personnel status is not obvious, all contractor personnel are required to identify themselves to avoid creating an impression to the public, agency officials, or Congress that such contractor personnel are Government officials. This can occur during meeting attendance, through written (letter or email) correspondence or verbal discussions (in person or telephonic), when making presentations, or in other situations where their contractor status is not obvious to third parties. This list is not exhaustive. Therefore, the contractor employee(s) shall: | ||
| (1) Not by word or deed give the impression or appearance of being a Government employee; | ||
| (2) Wear appropriate badges visible above the waist that identify them as contractor employees when in Government spaces, at a Government-sponsored event, or an event outside normal work spaces in support of the contract/order; | ||
| (3) Clearly identify themselves as contractor employees in telephone conversations and in all formal and informal written and electronic correspondence. Identification shall include the name of the company for whom they work; | ||
| (4) Identify themselves by name, their company name, if they are a subcontractor the name of the prime contractor their company is supporting, as well as the Government office they are supporting when participating in meetings, conferences, and other interactions in which all parties are not in daily contact with the individual contractor employee; and | ||
| (5) Be able to provide, when asked, the full number of the contract/order under which they are performing, and the name of the Contracting Officer’s Representative. | ||
| (b) If wearing a badge is a risk to safety and/or security, then an alternative means of identification maybe utilized if endorsed by the Contracting Officer’s Representative and approved by the Contracting Officer. | ||
| (c) The Contracting Officer will make final determination of compliance with regulations with regard to proper identification of contractor employees. |
| 5252.216-9512 | PAPERLESS CONTRACTING (NAVAIR)(JUN 2009) |
| (a) Orders and requests for proposals are hereby authorized to be issued by facsimile or by electronic commerce (including e-mail and paperless methods of delivery). Nothing in this contract should be read to prohibit these types of orders. In the event of a conflict with any other provision of this contract, this clause shall govern. | |
| (b) To the extent the terms "written", "mailed", or "physically delivered" appear in other provisions of this contract, these terms are hereby defined to explicitly include electronic commerce, email, or paperless delivery methods. |
Section I - Contract Clauses
| 52.202-1 |
| Definitions |
| NOV 2013 |
| 52.203-3 |
| Gratuities |
| APR 1984 |
| 52.203-5 |
| Covenant Against Contingent Fees |
| MAY 2014 |
| 52.203-6 |
| Restrictions On Subcontractor Sales To The Government |
| SEP 2006 |
| 52.203-7 |
| Anti-Kickback Procedures |
| MAY 2014 |
| 52.203-8 |
| Cancellation, Rescission, and Recovery of Funds for Illegal or Improper Activity |
| MAY 2014 |
| 52.203-10 |
| Price Or Fee Adjustment For Illegal Or Improper Activity |
| MAY 2014 |
| 52.203-12 |
| Limitation On Payments To Influence Certain Federal Transactions |
| OCT 2010 |
| 52.203-17 |
| Contractor Employee Whistleblower Rights and Requirement To Inform Employees of Whistleblower Rights |
| APR 2014 |
| 52.204-4 |
| Printed or Copied Double-Sided on Postconsumer Fiber Content Paper |
| MAY 2011 |
| 52.204-10 |
| Reporting Executive Compensation and First-Tier Subcontract Awards |
| OCT 2016 |
| 52.209-6 |
| Protecting the Government's Interest When Subcontracting With Contractors Debarred, Suspended, or Proposed for Debarment |
| OCT 2015 |
| 52.209-9 |
| Updates of Publicly Available Information Regarding Responsibility Matters |
| JUL 2013 |
| 52.209-10 |
| Prohibition on Contracting With Inverted Domestic Corporations |
| NOV 2015 |
| 52.211-5 |
| Material Requirements |
| AUG 2000 |
| 52.215-2 |
| Audit and Records--Negotiation |
| OCT 2010 |
| 52.215-8 |
| Order of Precedence--Uniform Contract Format |
| OCT 1997 |
| 52.215-10 |
| Price Reduction for Defective Certified Cost or Pricing Data |
| AUG 2011 |
| 52.215-11 |
| Price Reduction for Defective Certified Cost or Pricing Data--Modifications |
| AUG 2011 |
| 52.215-12 |
| Subcontractor Certified Cost or Pricing Data |
| OCT 2010 |
| 52.215-13 |
| Subcontractor Certified Cost or Pricing Data--Modifications |
| OCT 2010 |
| 52.215-14 Alt I |
| Integrity of Unit Prices (Oct 2010) - Alternate I |
| OCT 1997 |
| 52.215-15 |
| Pension Adjustments and Asset Reversions |
| OCT 2010 |
| 52.215-17 |
| Waiver of Facilities Capital Cost of Money |
| OCT 1997 |
| 52.215-21 |
| Requirements for Certified Cost or Pricing Data and Data Other Than Certified Cost or Pricing Data -- Modifications |
| OCT 2010 |
| 52.215-23 |
| Limitations on Pass-Through Charges |
| OCT 2009 |
| 52.219-8 |
| Utilization of Small Business Concerns |
| NOV 2016 |
| 52.219-16 |
| Liquidated Damages-Subcontracting Plan |
| JAN 1999 |
| 52.222-3 |
| Convict Labor |
| JUN 2003 |
| 52.222-19 |
| Child Labor -- Cooperation with Authorities and Remedies |
| JAN 2018 |
| 52.222-20 |
| Contracts for Materials, Supplies, Articles, and Equipment Exceeding $15,000 |
| MAY 2014 |
| 52.222-21 |
| Prohibition Of Segregated Facilities |
| APR 2015 |
| 52.222-26 |
| Equal Opportunity |
| SEP 2016 |
| 52.222-35 |
| Equal Opportunity for Veterans |
| OCT 2015 |
| 52.222-36 |
| Equal Opportunity for Workers with Disabilities |
| JUL 2014 |
| 52.222-37 |
| Employment Reports on Veterans |
| FEB 2016 |
| 52.222-40 |
| Notification of Employee Rights Under the National Labor Relations Act |
| DEC 2010 |
| 52.222-50 |
| Combating Trafficking in Persons |
| MAR 2015 |
| 52.222-54 |
| Employment Eligibility Verification |
| OCT 2015 |
| 52.223-6 |
| Drug-Free Workplace |
| MAY 2001 |
| 52.223-11 |
| Ozone-Depleting Substances and High Global Warming Potential Hydrofluorocarbons. |
| JUN 2016 |
| 52.223-18 |
| Encouraging Contractor Policies To Ban Text Messaging While Driving |
| AUG 2011 |
| 52.225-13 |
| Restrictions on Certain Foreign Purchases |
| JUN 2008 |
| 52.227-1 |
| Authorization and Consent |
| DEC 2007 |
| 52.227-2 |
| Notice And Assistance Regarding Patent And Copyright Infringement |
| DEC 2007 |
| 52.229-4 |
| Federal, State, And Local Taxes (State and Local Adjustments) |
| FEB 2013 |
| 52.230-3 |
| Disclosure And Consistency Of Cost Accounting Practices |
| OCT 2015 |
| 52.232-1 |
| Payments |
| APR 1984 |
| 52.232-9 |
| Limitation On Withholding Of Payments |
| APR 1984 |
| 52.232-11 |
| Extras |
| APR 1984 |
| 52.232-25 |
| Prompt Payment |
| JAN 2017 |
| 52.232-33 |
| Payment by Electronic Funds Transfer--System for Award Management |
| JUL 2013 |
| 52.232-39 |
| Unenforceability of Unauthorized Obligations |
| JUN 2013 |
| 52.232-40 |
| Providing Accelerated Payments to Small Business Subcontractors |
| DEC 2013 |
| 52.233-1 |
| Disputes |
| MAY 2014 |
| 52.233-3 |
| Protest After Award |
| AUG 1996 |
| 52.233-4 |
| Applicable Law for Breach of Contract Claim |
| OCT 2004 |
| 52.242-13 |
| Bankruptcy |
| JUL 1995 |
| 52.243-1 |
| Changes--Fixed Price |
| AUG 1987 |
| 52.244-2 |
| Subcontracts |
| OCT 2010 |
| 52.244-5 |
| Competition In Subcontracting |
| DEC 1996 |
| 52.244-6 |
| Subcontracts for Commercial Items |
| NOV 2017 |
| 52.245-1 |
| Government Property |
| JAN 2017 |
| 52.245-9 |
| Use And Charges |
| APR 2012 |
| 52.246-23 |
| Limitation Of Liability |
| FEB 1997 |
| 52.249-2 |
| Termination For Convenience Of The Government (Fixed-Price) |
| APR 2012 |
| 52.249-8 |
| Default (Fixed-Price Supply & Service) |
| APR 1984 |
| 52.253-1 |
| Computer Generated Forms |
| JAN 1991 |
| 252.203-7000 |
| Requirements Relating to Compensation of Former DoD Officials |
| SEP 2011 |
| 252.203-7001 |
| Prohibition On Persons Convicted of Fraud or Other Defense-Contract-Related Felonies |
| DEC 2008 |
| 252.203-7002 |
| Requirement to Inform Employees of Whistleblower Rights |
| SEP 2013 |
| 252.204-7003 |
| Control Of Government Personnel Work Product |
| APR 1992 |
| 252.209-7004 |
| Subcontracting With Firms That Are Owned or Controlled By The Government of a Country that is a State Sponsor of Terrorism |
| OCT 2015 |
| 252.211-7008 |
| Use of Government-Assigned Serial Numbers |
| SEP 2010 |
| 252.215-7000 |
| Pricing Adjustments |
| DEC 2012 |
| 252.225-7001 |
| Buy American And Balance Of Payments Program-- Basic |
| DEC 2017 |
| 252.225-7002 |
| Qualifying Country Sources As Subcontractors |
| DEC 2017 |
| 252.225-7012 |
| Preference For Certain Domestic Commodities |
| DEC 2017 |
| 252.225-7013 |
| Duty-Free Entry--Basic |
| MAY 2016 |
| 252.227-7013 |
| Rights in Technical Data--Noncommercial Items |
| FEB 2014 |
| 252.231-7000 |
| Supplemental Cost Principles |
| DEC 1991 |
| 252.232-7003 |
| Electronic Submission of Payment Requests and Receiving Reports |
| JUN 2012 |
| 252.232-7006 |
| Wide Area WorkFlow Payment Instructions |
| MAY 2013 |
| 252.239-7001 |
| Information Assurance Contractor Training and Certification |
| JAN 2008 |
| 252.242-7004 |
| Material Management And Accounting System |
| MAY 2011 |
| 252.243-7001 |
| Pricing Of Contract Modifications |
| DEC 1991 |
| 252.244-7000 |
| Subcontracts for Commercial Items |
| JUN 2013 |
| 252.245-7001 |
| Tagging, Labeling, and Marking of Government-Furnished Property |
| APR 2012 |
| 252.245-7002 |
| Reporting Loss of Government Property |
| DEC 2017 |
| 252.245-7003 |
| Contractor Property Management System Administration |
| APR 2012 |
| 252.247-7023 |
| Transportation of Supplies by Sea |
| APR 2014 |
| 52.204-19 | INCORPORATION BY REFERENCE OF REPRESENTATIONS AND CERTIFICATIONS (DEC 2014) |
| The Contractor's representations and certifications, including those completed electronically via the System for Award Management (SAM), are incorporated by reference into the contract. |
| 52.219-28 | POST-AWARD SMALL BUSINESS PROGRAM REREPRESENTATION (JUL 2013) | ||
| (a) Definitions. As used in this clause-- | |||
| Long-term contract means a contract of more than five years in duration, including options. However, the term does not include contracts that exceed five years in duration because the period of performance has been extended for a cumulative period not to exceed six months under the clause at 52.217-8, Option to Extend Services, or other appropriate authority. | |||
| Small business concern means a concern, including its affiliates, that is independently owned and operated, not dominant in the field of operation in which it is bidding on Government contracts, and qualified as a small business under the criteria in 13 CFR part 121 and the size standard in paragraph (c) of this clause. Such a concern is “not dominant in its field of operation” when it does not exercise a controlling or major influence on a national basis in a kind of business activity in which a number of business concerns are primarily engaged. In determining whether dominance exists, consideration shall be given to all appropriate factors, including volume of business, number of employees, financial resources, competitive status or position, ownership or control of materials, processes, patents, license agreements, facilities, sales territory, and nature of business activity. | |||
| (b) If the Contractor represented that it was a small business concern prior to award of this contract, the Contractor shall rerepresent its size status according to paragraph (e) of this clause or, if applicable, paragraph (g) of this clause, upon the occurrence of any of the following: | |||
| (1) Within 30 days after execution of a novation agreement or within 30 days after modification of the contract to include this clause, if the novation agreement was executed prior to inclusion of this clause in the contract. | |||
| (2) Within 30 days after a merger or acquisition that does not require a novation or within 30 days after modification of the contract to include this clause, if the merger or acquisition occurred prior to inclusion of this clause in the contract. | |||
| (3) For long-term contracts-- | |||
| (i) Within 60 to 120 days prior to the end of the fifth year of the contract; and | |||
| (ii) Within 60 to 120 days prior to the date specified in the contract for exercising any option thereafter. | |||
| (c) The Contractor shall rerepresent its size status in accordance with the size standard in effect at the time of this rerepresentation that corresponds to the North American Industry Classification System (NAICS) code assigned to this contract. The small business size standard corresponding to this NAICS code can be found at http://www.sba.gov/content/table-small-business-size-standards/ . | |||
| (d) The small business size standard for a Contractor providing a product which it does not manufacture itself, for a contract other than a construction or service contract, is 500 employees. | |||
| (e) Except as provided in paragraph (g) of this clause, the Contractor shall make the rerepresentation required by paragraph (b) of this clause by validating or updating all its representations and Certification section of the System for Award Management (SAM) and its other data in SAM, as necessary, to ensure that they reflect the Contractor's current status. The Contractor shall notify the contracting office in writing within the timeframes specified in paragraph (b) of this clause that the data have been validated or updated, and provide the date of the validation or update. | |||
| (f) If the Contractor represented that it was other than a small business concern prior to award of this contract, the Contractor may, but is not required to, take the actions required by paragraphs (e) or (g) of this clause. | |||
| (g) If the Contractor does not have representations and certifications in SAM, or does not have a representation in SAM for the NAICS code applicable to this contract, the Contractor is required to complete the following rerepresentation and submit it to the contracting office, along with the contract number and the date on which the rerepresentation was completed: | |||
| The Contractor represents that it [ ] is, [ ] is not a small business concern under NAICS Code 335912 assigned to contract number [______________]. |
[Contractor to sign and date and insert authorized signer's name and title].
Signature Date Signer’s Printed Name Signer’s Title
| 52.252-2 | CLAUSES INCORPORATED BY REFERENCE (FEB 1998) |
| This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es): https://www.acquisition.gov/far/ or http://farsite.hill.af.mil. |
| 52.252-6 | AUTHORIZED DEVIATIONS IN CLAUSES (APR 1984) |
| (a) The use in this solicitation or contract of any Federal Acquisition Regulation (48 CFR Chapter 1) clause with an authorized deviation is indicated by the addition of "(DEVIATION)" after the date of the clause. | |
| (b) The use in this solicitation or contract of any Defense Federal Acquisition Regulation (48 CFR Chapter 2) clause with an authorized deviation is indicated by the addition of "(DEVIATION)" after the name of the regulation. |
252.204-7006 BILLING INSTRUCTIONS (OCT 2005)
As prescribed in 204.7109, use the following clause:
| When submitting a request for payment, the Contractor shall-- | |
| (a) Identify the contract line item(s) on the payment request that reasonably reflect contract work performance; and | |
| (b) Separately identify a payment amount for each contract line item included in the payment request. |
| 252.204-7012 | SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT INFORMATION (OCT 2016) | |||
| (a) Definitions. As used in this clause -- | ||||
| "Adequate security" means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information. | ||||
| "Compromise" means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred. | ||||
| "Contractor attributional/proprietary information" means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company. | ||||
| "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 unclassified information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information. | ||||
| "Covered defense information" means unclassified controlled technical information or other information, as described in the Controlled Unclassified Information (CUI) Registry at http://www.wrchives.gov/cui/registry/category-list.html, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies, and is -- | ||||
| (1) Marked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract; or | ||||
| (2) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract. | ||||
| "Cyber incident" means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein. | ||||
| "Forensic analysis" means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data. | ||||
| "Information system" means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information. | ||||
| "Malicious software" means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware. | ||||
| "Media" means physical devices or writing surfaces including, but not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which covered defense information is recorded, stored, or printed within a covered contractor information system. | ||||
| "Operationally critical support" means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation. | ||||
| "Rapidly report" means within 72 hours of discovery of any cyber incident. | ||||
| "Technical information" means technical data or computer software, as those terms are defined in the clause at DFARS 252.227-7013, Rights in Technical Data - 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 date, 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 contractor information systems. To provide adequate security, the Contractor shall implement, at a minimum, the following information security protections: | ||||
| (1) For covered contractor information systems that are part of an information technology (IT) service or system operated on behalf of the Government, the following security requirements apply: | ||||
| (i) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010, Cloud Computing Services, of this contract. | ||||
| (ii) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract. | ||||
| (2) For covered contractor information systems that are not part of an IT service or system operated on behalf of the Government and therefore are not subject to the security requirement specified at paragraph (b)(1) of this clause, the following security requirements apply: | ||||
| (i) Except as provided in paragraph (b)(2)(ii) of this clause, the covered contractor information system shall be subject to the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, "Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations," (available via the internet at http://dx.doi.org/10.6028/NIST.SP.800-171) that is in effect at the time the solicitation is issued or as authorized by the Contracting Officer. | ||||
| (ii)(A) The Contractor shall submit requests to vary from NIST SP 800-171, as soon as practical, but not later than December 31, 2017. For all contracts awarded prior to October 1, 2017, the Contractor shall notify the DoD Chief Information Officer (CIO), via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award. | ||||
| (B) The Contractor shall submit requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO. The Contractor need not implement any security requirement adjudicated by an authorized representative of the DoD CIO to be nonapplicable or to have an alternative but equally effective, security measure that may be implemented in its place. | ||||
| (C) If the DoD CIO has previously adjudicated the contractor's requests indicating that a requirement is not applicable or that an alternative security measure is equally effective, a copy of that approval shall be provided to the Contracting Officer when requesting its recognition under this contract. | ||||
| (D) If the Contractor intends to use an external cloud service provider to store, process, or transmit any covered defense information in performance of this contract, the Contractor shall require and ensure that the cloud service provided meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline (https://www.fedramp.gov/resources/documents/) and that the cloud service provider complies with requirements in paragraphs (c) through (g) of this clause for cyber incident reporting, malicious software, media preservation and protection, access to additional information and equipment necessary for forensic analysis, and cyber incident damage assessment. | ||||
| (3) Apply other information systems security measures when the Contractor reasonably determines that information systems security measures, in addition to those identified in paragraph (b)(1) and (2) of this clause, may be required to provide adequate security in a dynamic environment or to accommodate special circumstances (e.g., medical devices) and any individual, isolated, or temporary deficiencies based on an assessed risk or vulnerability. These measures may be addressed in a system security plan. | ||||
| (c) Cyber incident reporting requirement. | ||||
| (1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor's ability to perform the requirements of the contract that are designated as operationally critical support, the Contractor shall -- | ||||
| (i) Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts. This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other information systems on the Contractor's network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the Contractor's ability to provide operationally critical support; and | ||||
| (ii) Rapidly report cyber incidents to DoD at http://dibnet.dod.mil. | ||||
| (2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at http://dibnet.dod.mil. | ||||
| (3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see http://iase.disa.mil/pki/eca/Pages/index.aspx. | ||||
| (d) Malicious software. When the Contractor or subcontractors discover and isolate malicious software in connection with a reported cyber incident, submit the malicious software to DoD Cyber Crime Center (DC#) in accordance with instructions provided by DC3 or the Contracting Officer. Do not send the malicious software to the Contracting Officer. | ||||
| (e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest. | ||||
| (f) Access to additional information or equipment necessary for forensic analysis. Upon request by DoD, the Contractor shall provide DoD with access to additional information or equipment that is necessary to conduct a forensic analysis. | ||||
| (g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause. | ||||
| (h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released. | ||||
| (i) Use and release of contractor attributional/proprietary information not created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD-- | ||||
| (1) To entities with missions that may be affected by such information; | ||||
| (2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents; | ||||
| (3) To Government entities that conduct counterintelligence or law enforcement investigations; | ||||
| (4) For national security purposes, including cyber situational awareness and defense purposes (including with Defense Industrial Base (DIB) participants in the program at 32 CFR part 236); or | ||||
| (5) To a support services contractor ("recipient") that is directly supporting Government activities under a contract that includes the clause at 252.204-7009, Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information. | ||||
| (j) Use and release of contractor attributional/proprietary information created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph (c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph (i) of this clause, and for any other lawful Government purposes or activity, subject to all applicable statutory, regulatory, and policy based restrictions on the Government's use and release of such information. | ||||
| (k) The Contractor shall conduct activities under this clause in accordance with applicable laws and regulations on the interception, monitoring, access, use, and disclosure of electronic communications and data. | ||||
| (l) Other safeguarding or reporting requirements. The safeguarding and cyber incident reporting required by this clause in no way abrogates the Contractor's responsibility for other safeguarding or cyber incident reporting pertaining to its unclassified information systems as required by other applicable clauses of this contract, or as a result of other applicable U.S. Government statutory or regulatory requirements. | ||||
| (m) Subcontracts. The Contractor shall -- | ||||
| (1) Include this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve covered defense information, including subcontracts for commercial items, without alteration, except to identify the parties. The Contractor shall determine if the information required for subcontractor performance retains its identity as covered defense information and will require protection under this clause, and if necessary, consult with the Contracting Officer; and | ||||
| (2) Require subcontractor to-- | ||||
| (i) Notify the prime Contractor (or next higher-tier subcontractor) when submitting a request to vary from a NIST SP 800-171 security requirement to the Contracting Officer, in accordance with paragraph (b)(2)(ii)(B) of this clause; and | ||||
| (ii) Provide the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable, when reporting a cyber incident to DoD as required in paragraph (c) of this clause. |
| 252.211-7003 | ITEM UNIQUE IDENTIFICATION AND VALUATION (MAR 2016) | ||||
| (a) Definitions. As used in this clause-- | |||||
| “Automatic identification device” means a device, such as a reader or interrogator, used to retrieve data encoded on machine-readable media. | |||||
| “Concatenated unique item identifier” means-- | |||||
| (1) For items that are serialized within the enterprise identifier, the linking together of the unique identifier data elements in order of the issuing agency code, enterprise identifier, and unique serial number within the enterprise identifier; or | |||||
| (2) For items that are serialized within the original part, lot, or batch number, the linking together of the unique identifier data elements in order of the issuing agency code; enterprise identifier; original part, lot, or batch number; and serial number within the original part, lot, or batch number. | |||||
| “Data matrix” means a two-dimensional matrix symbology, which is made up of square or, in some cases, round modules arranged within a perimeter finder pattern and uses the Error Checking and Correction 200(ECC200) specification found within International Standards Organization (ISO)/ International Electrotechnical Commission (IEC) 16022. | |||||
| “Data qualifier” means a specified character (or string of characters) that immediately precedes a data field that defines the general category or intended use of the data that follows. | |||||
| “DoD recognized unique identification equivalent” means a unique identification method that is in commercial use and has been recognized by DoD. All DoD recognized unique identification equivalents are listed at http://www.acq.osd.mil/dpap/pdi/uid/iuid_equivalents.html. | |||||
| “DoD item unique identification” means a system of marking items delivered to DoD with unique item identifiers that have machine-readable data elements to distinguish an item from all other like and unlike items. For items that are serialized within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier and a unique serial number. For items that are serialized within the part, lot, or batch number within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier; the original part, lot, or batch number; and the serial number. | |||||
| “Enterprise” means the entity (e.g., a manufacturer or vendor) responsible for assigning unique item identifiers to items. | |||||
| “Enterprise identifier” means a code that is uniquely assigned to an enterprise by an issuing agency. | |||||
| “Government's unit acquisition cost” means-- | |||||
| (1) For fixed-price type line, subline, or exhibit line items, the unit price identified in the contract at the time of delivery; | |||||
| (2) For cost-type or undefinitized line, subline, or exhibit line items, the Contractor’s estimated fully burdened unit cost to the Government at the time of delivery; and | |||||
| (3) For items produced under a time-and-materials contract, the Contractor’s estimated fully burdened unit cost to the Government at the time of delivery. | |||||
| “Issuing agency” means an organization responsible for assigning a globally unique identifier to an enterprise, as indicated in the Register of Issuing Agency Codes for ISO/IEC 15459, located at http://www.aimglobal.org/?Reg_Authority15459. | |||||
| “Issuing agency code” means a code that designates the registration (or controlling) authority for the enterprise identifier. | |||||
| “Item” means a single hardware article or a single unit formed by a grouping of subassemblies, components, or constituent parts. | |||||
| “Lot or batch number” means an identifying number assigned by the enterprise to a designated group of items, usually referred to as either a lot or a batch, all of which were manufactured under identical conditions. | |||||
| “Machine-readable” means an automatic identification technology media, such as bar codes, contact memory buttons, radio frequency identification, or optical memory cards. | |||||
| “Original part number” means a combination of numbers or letters assigned by the enterprise at item creation to a class of items with the same form, fit, function, and interface. | |||||
| “Parent item” means the item assembly, intermediate component, or subassembly that has an embedded item with a unique item identifier or DoD recognized unique identification equivalent. | |||||
| “Serial number within the enterprise identifier” means a combination of numbers, letters, or symbols assigned by the enterprise to an item that provides for the differentiation of that item from any other like and unlike item and is never used again within the enterprise. | |||||
| “Serial number within the part, lot, or batch number” means a combination of numbers or letters assigned by the enterprise to an item that provides for the differentiation of that item from any other like item within a part, lot, or batch number assignment. | |||||
| “Serialization within the enterprise identifier” means each item produced is assigned a serial number that is unique among all the tangible items produced by the enterprise and is never used again. The enterprise is responsible for ensuring unique serialization within the enterprise identifier. | |||||
| “Serialization within the part, lot, or batch number” means each item of a particular part, lot, or batch number is assigned a unique serial number within that part, lot, or batch number assignment. The enterprise is responsible for ensuring unique serialization within the part, lot, or batch number within the enterprise identifier. | |||||
| “Type designation” means a combination of letters and numerals assigned by the Government to a major end item, assembly or subassembly, as appropriate, to provide a convenient means of differentiating between items having the same basic name and to indicate modifications and changes thereto. | |||||
| “Unique item identifier” means a set of data elements marked on items that is globally unique and unambiguous. The term includes a concatenated unique item identifier or a DoD recognized unique identification equivalent. | |||||
| “Unique item identifier type” means a designator to indicate which method of uniquely identifying a part has been used. The current list of accepted unique item identifier types is maintained at http://www.acq.osd.mil/dpap/pdi/uid/uii_types.html. | |||||
| (b) The Contractor shall deliver all items under a contract line, subline, or exhibit line item. | |||||
| (c) Unique item identifier. | |||||
| (1) The Contractor shall provide a unique item identifier for the following: | |||||
| (i) Delivered items for which the Government's unit acquisition cost is $5,000 or more, except for the following line items: | |||||
| Contract Line, Subline, or Exhibit Line Item Number Item Description | |||||
| ________________________________________________________________________________ | |||||
| ________________________________________________________________________________ | |||||
| ________________________________________________________________________________ | |||||
| (ii) Items for which the Government's unit acquisition cost is less than $5,000 that are identified in the Schedule or the following table: | |||||
| Contract Line, Subline, or Exhibit Line Item Number Item Description |
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.