16-T-0096_RFQ_Solicitation.docx
DOCX document 99 KB Posted
- Attached to
- 50 Ton Press Federal contract opportunity
- Solicitation number
- N6893616T0096
About this file
16-T-0096 RFQ Solicitation
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Questions_and_Answers.docx | DOCX document | |
| 16-T-0096_RFQ_Amendment.docx | DOCX document | |
| SOW.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
N68936-16-T-0096
Section A - Solicitation/Contract Form
CLAUSES INCORPORATED BY FULL TEXT
FOR YOUR INFORMATION:
The following addresses and points of contact are provided:
| Name: | Crystal Crawford | |
| Phone: | (760) 939- 1441 | |
| DSN: | 437- 1441 | |
| FAX: | (760) 939- 3095 |
Email address: crystal.a.crawford@navy.mil
U.S. Postal Service Mailing Address:
| COMMANDER |
| CODE 254230D (C. Crawford– 760-939-1441) |
| NAVAIRWARCENWPNDIV |
| 429 E. BOWEN RD. MAIL STOP 4015 |
| CHINA LAKE, CA 93555-6108 |
Direct Delivery Address (UPS, FedEx, etc):
| COMMANDER |
| CODE 254230D (C. Crawford) |
| NAVAIRWARCENWPNDIV |
| BLDG 982, MAIL STOP 4015 |
| CHINA LAKE, CA 93555-6108 |
THE INFORMATION BELOW IS NOT ALL INCLUSIVE AS TO WHAT IS REQUIRED FOR A TECHNICAL EVALUATION. IT IS THE RESPONSIBILITY OF THE VENDOR TO SUBMIT ENOUGH INFORMATION FOR A SOUND TECHNICAL EVALUATION TO BE REVIEWED BY OUR TECHNICAL POINT OF CONTACT.
ANY CONTRACT RESULTING FROM THIS SOLICITATION WILL UTILIZE WIDE AREA WORKFLOW (WAWF) FOR INVOICING AND PAYMENT REQUEST.
THE BELOW INFORMATION IS REQUIRED FOR ANY AWARD RESULTING FROM THIS SOLICITATION.
VENDOR NAME:
Address Line 1:
Address Line 2:
VENDOR POC:
VENDOR PHONE:
VENDOR FAX:
VENDOR EMAIL:
CAGE CODE:
DUN & BRADSTREET #
PRODUCT COUNTRY of ORIGIN:
BUSINESS SIZE:
SHIPPING DESTINATION or ORIGIN:
SHIPPING COST:
WAWF REGISTERED: https://wawf.eb.mil/
SAM: https://www.sam.gov/portal/public/SAM
WARRANTY IF ANY:
DID YOU INCLUDE YOUR SPECIFICATIONS:
Section B - Supplies or Services and Prices
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
| 1 |
| Each |
50 Ton Press
FFP
50 ton down-acting Hydraulic Press System See SOW FOB: Destination
PURCHASE REQUEST NUMBER: 1300535072
NET AMT
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 |
| N/A |
| N/A |
| N/A |
| Government |
Section F - Deliveries or Performance
DELIVERY INFORMATION
| CLIN |
| DELIVERY DATE |
| QUANTITY |
| SHIP TO ADDRESS |
| DODAAC |
| 0001 |
| 30-SEP-2016 |
| 1 |
| SEE SECTION F |
SHIPPING INSTRUCTIONS
FOR DELIVERIES TO NAWCWD CA
FOB: Destination N68936
CLAUSES INCORPORATED BY REFERENCE
| 52.242-15 |
| Stop-Work Order |
| AUG 1989 |
| 52.247-34 | F.O.B. DESTINATION (NOV 1991) | ||
| (a) The term "f.o.b. destination," as used in this clause, means- | |||
| (1) Free of expense to the Government, on board the carrier's conveyance, at a specified delivery point where the consignee's facility (plant, warehouse, store, lot, or other location to which shipment can be made) is located; and | |||
| (2) Supplies shall be delivered to the destination consignee's wharf (if destination is a port city and supplies are for export), warehouse unloading platform, or receiving dock, at the expense of the Contractor. The Government shall not be liable for any delivery, storage, demurrage, accessorial, or other charges involved before the actual delivery (or "constructive placement" as defined in carrier tariffs) of the supplies to the destination, unless such charges are caused by an act or order of the Government acting in its contractual capacity. If rail carrier is used, supplies shall be delivered to the specified unloading platform of the consignee. If motor carrier (including "piggyback") is used, supplies shall be delivered to truck tailgate at the unloading platform of the consignee, except when the supplies delivered meet the requirements of Item 568 of the National Motor Freight Classification for "heavy or bulky freight." When supplies meeting the requirements of the referenced Item 568 are delivered, unloading (including movement to the tailgate) shall be performed by the consignee, with assistance from the truck driver, if requested. If the contractor uses rail carrier or freight forwarded for less than carload shipments, the contractor shall ensure that the carrier will furnish tailgate delivery, when required, if transfer to truck is required to complete delivery to consignee. | |||
| (b) The Contractor shall- | |||
| (1)(i) Pack and mark the shipment to comply with contract specifications; or | |||
| (ii) In the absence of specifications, prepare the shipment in conformance with carrier requirements; | |||
| (2) Prepare and distribute commercial bills of lading; | |||
| (3) Deliver the shipment in good order and condition to the point of delivery specified in the contract; | |||
| (4) Be responsible for any loss of and/or damage to the goods occurring before receipt of the shipment by the consignee at the delivery point specified in the contract; | |||
| (5) Furnish a delivery schedule and designate the mode of delivering carrier; and | |||
| (6) Pay and bear all charges to the specified point of delivery. |
| F-TXT-10 | SHIPPING INSTRUCTIONS (CHINA LAKE) (AUG 2015) | ||
| SHIP TO: | NAVAL AIR WARFARE CENTER WEAPONS DIVISION (NAWCWD) | ||
| Receiving Officer, Code FLCSD400G | |||
| Bldg. 1024, Blandy Ave. | |||
| N68936-XX-X-XXXX | |||
| China Lake, CA 93555-6100 | |||
| Attn: | |||
| Code & Phone: |
Failure to mark each shipping label and packing list as indicated above may result in return of shipment at your expense, or will cause a delay in processing your invoice for payment.
DOCK HOURS are Monday through Thursday, and Alternating Fridays, 0730-1530. If you anticipate making delivery on a Friday please call Receiving at (760)939-2305 to verify receiving dock hours.
COMPLETED AT TIME OF AWARD
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
**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. N68936
(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: | “Leave Blank” | ||
| Ship To Code: | N68936 | ||
| Ship From Code: | “Leave Blank” | ||
| Mark For Code: | “Leave Blank” | ||
| Service Approver (DoDAAC): | “Leave Blank” | ||
| Service Acceptor (DoDAAC): | “Leave Blank” | ||
| Accept at Other DoDAAC: | “Leave Blank” | ||
| LPO DoDAAC: | “Leave Blank” | ||
| DCAA Auditor DoDAAC: | “Leave Blank” | ||
| Other DoDAAC(s): | “Leave Blank” |
(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.
POC:
(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. N/A
(2) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988.
TO BE COMPLETED AT TIME OF AWARD
| 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 I - Contract Clauses
CLAUSES INCORPORATED BY REFERENCE
| 52.204-10 |
| Reporting Executive Compensation and First-Tier Subcontract Awards |
| OCT 2015 |
| 52.212-4 |
| Contract Terms and Conditions--Commercial Items |
| MAY 2015 |
| 52.219-6 |
| Notice Of Total Small Business Set-Aside |
| NOV 2011 |
| 52.222-3 |
| Convict Labor |
| JUN 2003 |
| 52.222-50 |
| Combating Trafficking in Persons |
| MAR 2015 |
| 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.233-3 |
| Protest After Award |
| AUG 1996 |
| 252.203-7000 |
| Requirements Relating to Compensation of Former DoD Officials |
| SEP 2011 |
| 252.203-7002 |
| Requirement to Inform Employees of Whistleblower Rights |
| SEP 2013 |
| 252.204-7000 |
| Disclosure Of Information |
| AUG 2013 |
| 252.211-7008 |
| Use of Government-Assigned Serial Numbers |
| SEP 2010 |
| 252.232-7010 |
| Levies on Contract Payments |
| DEC 2006 |
| 252.239-7001 |
| Information Assurance Contractor Training and Certification |
| JAN 2008 |
| 252.243-7001 |
| Pricing Of Contract Modifications |
| DEC 1991 |
| 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.212-5 | CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT STATUTES OR EXECUTIVE ORDERS--COMMERCIAL ITEMS (DEVIATION 2013-O0019)(NOV 2015) - ALT I (JUL 2014) | ||
| (a) Notwithstanding the requirements of any other clause in this contract, the Contractor is not required to flow down any FAR clause, other than those in this paragraph (b)(1) in a subcontract for commercial items. Unless otherwise indicated below, the extent of the flow down shall be as required by the clause-- | |||
| (1) 52.203-13, Contractor Code of Business Ethics and Conduct (Apr 2010)(Pub. L. 110-252, Title VI, Chapter 1 (41 U.S.C. 251 note)). | |||
| (2) 52.219-8, Utilization of Small Business Concerns (Oct 2014)(15 U.S.C. 637(d)(2) and (3)), in all subcontracts that offer further subcontracting opportunities. If the subcontract (except subcontracts to small business concerns) exceeds $650,000 ($1.5 million for construction of any public facility), the subcontractor must include 52.219-8 in lower tier subcontracts that offer subcontracting opportunities. | |||
| (3) 52.222-17, Nondisplacement of Qualified Workers (May 2014)(E.O. 13495). Flow down required in accordance with paragraph (1) of FAR Clause 52.222-17. | |||
| (4) 52.222-21, Prohibition of Segregated Facilities (Apr 2015). | |||
| (5) 52.222-26, Equal Opportunity (Apr 2015)(E.O. 11246). | |||
| (6) 52.222-35, Equal Opportunity for Veterans (Jul 2014)(38 U.S.C. 4212). | |||
| (7) 52.222-36, Equal Opportunity for Workers with Disabilities (Jul 2014)(29 U.S.C. 793). | |||
| (8) 52.222-37, Employment Reports on Veterans (Jul 2014)(38 U.S.C. 4212). | |||
| (9) 52.222-40, Notification of Employee Rights Under the National Labor Relations Act (Dec 2010)(E.O. 13496). Flow down required in accordance with paragraph (f) of clause 52.222-40. | |||
| (10) 52.222-41, Service Contract Labor Standards (May 2014)(41 U.S.C. Chapter 67). | |||
| (11)(A) 52.222-50, Combating Trafficking in Persons (Mar 2015)(22 U.S.C. chapter 78 and E.O. 13627). | |||
| (B) Alternate I (Mar 2015) of 52.222-50 (22 U.S.C. 78 and E.O. 13627). | |||
| (12) 52.222-51, Exemption from Application of the Service Contract Labor Standard to Contracts for Maintenance, Calibration, or Repair of Certain Equipment--Requirements (May 2014) (41 U.S.C. Chapter 67). | |||
| (13) 52.222-53, Exemption from Application of the Service Contract Labor Standard to Contracts for Certain Services-Requirements (May 2014) (41 U.S.C. Chapter 67). | |||
| (14) 52.222-54, Employment Eligibility Verification (Aug 2013). | |||
| (15) 52.222-55, Minimum Wages Under Executive Order 13658 (Dec 2014)(Executive Order 13658). | |||
| (16) 52.225-26, Contractors Performing Private Security Functions Outside the United States (Jul 2013)(Section 862, as amended, of the National Defense Authorization Act for Fiscal Year 2008; 10 U.S.C. 2302 Note). | |||
| (17) 52.226-6, Promoting Excess Food Donation to Nonprofit Organizations (May 2014)(42 U.S.C. 1792). Flow down required in accordance with paragraph (e) of FAR clause 52.226-6. | |||
| (18) 52.247-64, Preference for Privately-Owned U.S.- Flag Commercial Vessels (Feb 2006)(46 U.S.C. Appx 1241(b) and 10 U.S.C. 2631). Flow down required in accordance with paragraph (d) of FAR clause 52.247-64. | |||
| (b) While not required, the contractor may include in its subcontracts for commercial items a minimal number of additional clauses necessary to satisfy its contractual obligations. |
| 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 [333517] 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.232-39 | UNENFORCEABILITY OF UNAUTHORIZED OBLIGATIONS (JUN 2013) | |
| (a) Except as stated in paragraph (b) of this clause, when any supply or service acquired under this contract is subject to any End User License Agreement (EULA), Terms of Service (TOS), or other legal instrument or agreement, that includes any clause requiring the Government to indemnify the Contractor or any person or entity for damages, costs, fees, or any other loss or liability that would create an Anti-Deficiency Act violation (31 U.S.C. 1341), the following shall govern: | ||
| (1) Any such clause is unenforceable against the Government. | ||
| (2) Neither the Government nor any Government authorized end user shall be deemed to have agreed to such clause by virtue of it appearing in the EULA, TOS, or similar legal instrument or agreement. If the EULA, TOX, or similar legal instrument or agreement is invoked through an "I agree" click box or other comparable mechanism (e.g., "click-wrap" or "browse-wrap" agreements), execution does not bind the Government or any Government authorized end user to such clause. | ||
| (3) Any such clause is deemed to be stricken from the EULA, TOS, or similar legal instrument or agreement. | ||
| (b) Paragraph (a) of this clause does not apply to indemnification by the Government that is expressly authorized by statute and specifically authorized under applicable agency regulations and procedures. |
52.233-4 APPLICABLE LAW FOR BREACH OF CONTRACT CLAIM (OCT 2004)
United States law will apply to resolve any claim of breach of this contract.
| 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-7004 | SYSTEM FOR AWARD MANAGEMENT (52.204-7)(JUL 2013) - ALT A (FEB 2014) | ||
| (a) Definitions. As used in this provision-- | |||
| “System for Award Management (SAM) database” means the primary Government repository for contractor information required for the conduct of business with the Government. | |||
| “Commercial and Government Entity (CAGE) Code” means - | |||
| (1) A code assigned by the Defense Logistics Information Service (DLIS) to identify a commercial or Government entity: or | |||
| (2) A code assigned by a member of the North Atlantic Treaty Organization that DLIS records and maintains in the CAGE master file. This type of code is known as an "NCAGE code." | |||
| “Data Universal Numbering System (DUNS) number” means the 9-digit number assigned by Dun and Bradstreet, Inc. (D&B) to identify unique business entities. | |||
| “Data Universal Numbering System +4 (DUNS+4) number” means the DUNS number assigned by D&B plus a 4-character suffix that may be assigned by a business concern. (D&B has no affiliation with this 4-character suffix.) This 4-character suffix may be assigned at the discretion of the business concern to establish additional SAM records for identifying alternative Electronic Funds Transfer (EFT) accounts (see FAR 32.11) for the same parent concern. | |||
| “Registered in the System for Award Management (SAM) database” means that-- | |||
| (1) The contractor has entered all mandatory information, including the DUNS number or the DUNS+4 number, and Contractor and Government Entity (CAGE) code into the SAM database; and | |||
| (2) The contractor has completed the Core Data, Assertions, Representations and Certifications, and Points of Contact sections of the registration in the SAM database; | |||
| (3) The Government has validated all mandatory data fields, to include validation of the Taxpayer Identification Number (TIN) with the Internal Revenue Service (IRS). The contractor will be required to provide consent for TIN validation to the Government as part of the SAM registration process; and | |||
| (4) The Government has marked the record "Active." | |||
| (b)(1) By submission of an offer, the offeror acknowledges the requirement that a prospective awardee shall be registered in the SAM database prior to award, during performance, and through final payment of any contract, basic agreement, basic ordering agreement, or blanket purchasing agreement resulting from this solicitation. | |||
| (2) The offeror shall enter, in the block with its name and address on the cover page of its offer, the annotation “DUNS” or “DUNS +4” followed by the DUNS or DUNS +4 number that identifies the offeror's name and address exactly as stated in the offer. The DUNS number will be used by the Contracting Officer to verify that the offeror is registered in the SAM database. | |||
| (c) If the offeror does not have a DUNS number, it should contact Dun and Bradstreet directly to obtain one. | |||
| (1) An offeror may obtain a DUNS number-- | |||
| (i) Via the Internet at http://fedgov.dnb.com/webform or if the offeror does not have internet access, it may call Dun and Bradstreet at 1-866-705-5711 if located within the United States; or | |||
| (ii) If located outside the United States, by contacting the local Dun and Bradstreet office. The offeror should indicate that it is an offeror for a U.S. Government contract when contacting the local Dun and Bradstreet office. | |||
| (2) The offeror should be prepared to provide the following information: | |||
| (i) Company legal business. | |||
| (ii) Tradestyle, doing business, or other name by which your entity is commonly recognized. | |||
| (iii) Company physical street address, city, state, and Zip Code. | |||
| (iv) Company mailing address, city, state and Zip Code (if separate from physical). | |||
| (v) Company telephone number. | |||
| (vi) Date the company was started. | |||
| (vii) Number of employees at your location. | |||
| (viii) Chief executive officer/key manager. | |||
| (ix) Line of business (industry). | |||
| (x) Company Headquarters name and address (reporting relationship within your entity). | |||
| (d) If the Offeror does not become registered in the SAM database in the time prescribed by the Contracting Officer, the Contracting Officer will proceed to award to the next otherwise successful registered Offeror. | |||
| (e) Processing time, which normally takes 48 hours, should be taken into consideration when registering. Offerors who are not registered should consider applying for registration immediately upon receipt of this solicitation. | |||
| (f) Offerors may obtain information on registration at https://www.acquisition.gov. |
252.204-7006 BILLING INSTRUCTIONS (OCT 2005)
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 REPORTING (DEVIATION 2016-O0001)(OCT 2015) | |||
| (a) Definitions. As used in this clause -- | ||||
| "Adequate security" means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information. | ||||
| "Compromise" means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred. | ||||
| "Contractor attributional/proprietary information" means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company. | ||||
| "Contractor information system" means an information system belonging to, or operated by or for, the Contractor. | ||||
| "Controlled technical information" means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination. Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements on Technical Documents. The term does not include information that is lawfully publicly available without restrictions. | ||||
| "Covered contractor information system" means an information system that is owned, 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 an actual or potentially adverse effect on an information system and/or the information residing therein. | ||||
| "Forensic analysis" means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data. | ||||
| "Malicious software" means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware. | ||||
| "Media" means physical devices or writing surfaces including, but 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 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 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, as 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," (see http://dx.doi.org/10.6028/NIST.SP.800-171) that is in effect at the time of the solicitation is issued or as authorized by the Contracting Officer with the exception of the derived security requirement 3.5.3 "Use of multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts", which will be required not later than 9 months after award of the contract, if provision 252.204-7008, Compliance with Safeguarding Covered Defense Information Controls (Deviation 2016-O0001)(OCT 2015); or | ||||
| (B) Alternative but equally effective security measures used to compensate for the inability to satisfy a particular requirement and achieve equivalent protection approved in writing by an authorized representative of the DoD Chief Information Officer (CIO) prior to contract award; and | ||||
| (2) Apply other information systems security measures when the Contractor reasonably determines that information system 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://didnet.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://didnet.dod.mil. | ||||
| (3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see http://iase.disa.mil/pki/eca/Pages/index.aspx. | ||||
| (d) Malicious software. The Contractor or subcontractors that discover and isolate malicious software in connection with a reported cyber incident shall submit the malicious software in accordance with instructions provided by the Contracting Officer. | ||||
| (e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest. | ||||
| (f) Access to additional information or equipment necessary for forensic analysis. Upon request by DoD, the Contractor shall provide DoD with access to additional information or equipment that is necessary to conduct a forensic analysis. | ||||
| (g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause. | ||||
| (h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released. | ||||
| (i) Use and release of contractor attributional/proprietary information not created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD-- | ||||
| (1) To entities with missions that may be affected by such information; | ||||
| (2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents; | ||||
| (3) To Government entities that conduct counterintelligence or law enforcement investigations; | ||||
| (4) For national security purposes, including cyber situational awareness and defense purposes (including with Defense Industrial Base (DIB) participants in the program at 32 CFR part 236); or | ||||
| (5) To a support services contractor ("recipient") that is directly supporting Government activities under a contract that includes the clause at 252.204-7009, Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information. | ||||
| (j) Use and release of contractor attributional/proprietary information created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph (c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph (i) of this clause, and for any other lawful Government 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 the substance of this clause, including this paragraph (m), in all subcontracts, including subcontracts for commercial items; and | ||||
| (2) Require subcontractors to rapidly report cyber incidents directly to DoD at http://dibnet.dod.mil and the prime Contractor. This includes providing the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable. |
| 252.211-7003 | ITEM UNIQUE IDENTIFICATION AND VALUATION (DEC 2013) | |||
| (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 (e.g., Dun & Bradstreet's Data Universal Numbering System (DUNS) Number, GS1 Company Prefix, Allied Committee 135 NATO Commercial and Government Entity (NCAGE)/Commercial and Government Entity (CAGE) Code, or the Coded Representation of the North American Telecommunications Industry Manufacturers, Suppliers, and Related Service Companies (ATIS-0322000) Number), European Health Industry Business Communication Council (EHIBCC) and Health Industry Business Communication Council (HIBCC)), as indicated in the Register of Issuing Agency Codes for ISO/IEC 15459, located at http://www.nen.nl/Normontwikkeling/Certificatieschemas-en-keurmerken/Schemabeheer/ISOIEC-15459.htm. | ||||
| “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 |
N/A
| (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 |
N/A
| (iii) Subassemblies, components, and parts embedded within delivered items, items with warranty requirements, DoD serially managed reparables and DoD serially managed nonreparables as specified in Attachment Number: N/A. | ||||
| (iv) Any item of special tooling or special test equipment as defined in FAR 2.101 that have been designated for preservation and storage for a Major Defense Acquisition Program as specified in Attachment Number: N/A. | ||||
| (v) Any item not included in (i), (ii), (iii), or (iv) for which the contractor creates and marks a unique item identified for traceability. | ||||
| (2) The unique item identifier assignment and its component data element combination shall not be duplicated on any other item marked or registered in the DoD Item Unique Identification Registry by the contractor. | ||||
| (3) The unique item identified component data elements shall be marked on an item using two dimensional data matrix symbology that complies with ISO/IEC International Standard 16022, Information technology - International symbology specification - Data matrix; ECC200 data matrix specification. | ||||
| (4) Data syntax and semantics of unique item identifiers. The Contractor shall ensure that-- | ||||
| (i) The data elements (except issuing agency code) of the unique item identifier are encoded within the data matrix symbol that is marked on the item using one of the following three types of data qualifiers, as determined by the Contractor: | ||||
| (A) Application Identifiers (AIs) (Format Indicator 05 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology--EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard. | ||||
| (B) Data Identifiers (DIs) (Format Indicator 06 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology--EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard. | ||||
| (C) Text Element Identifiers (TEIs) (Format Indicator 12 of ISO/IEC International Standard 15434), in accordance with the Air Transport Association Common Support Data Dictionary; and |
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. Updated .