The file's text, extracted by GovTribe without its formatting.
N68936-16-R-0047
Section A - Solicitation/Contract Form
FOR YOUR INFORMATION
FOR YOUR INFORMATION:
The following addresses and points of contact are provided:
| Name: | Danielle McCarthy |
| Phone: | (760) 939-0008 |
| DSN: | 437-0008 |
Email address: danielle.mccarthy@navy.mil
U.S. Postal Service Mailing Address:
| COMMANDER |
| CODE 254220D (D. McCARTHY – 760-939-0008) |
| NAVAIRWARCENWPNDIV |
| 429 E. BOWEN RD. MAIL STOP 4015 |
| CHINA LAKE, CA 93555-6108 |
Direct Delivery Address (UPS, FedEx, etc.):
| COMMANDER |
| CODE 254220D (D. McCARTHY – 760-939-0008) |
| NAVAIRWARCENWPNDIV |
| 429 E. BOWEN RD. MAIL STOP 4015 |
| CHINA LAKE, CA 93555-6108 |
And
| Name: | Jessica Rodriguez |
| Phone: | (760) 939-3974 |
| DSN: | 437-3974 |
Email address: jessica.rodriguez@navy.mil
U.S. Postal Service Mailing Address:
| COMMANDER |
| CODE 254220D (J. RODRIGUEZ – 760-939-3974) |
| NAVAIRWARCENWPNDIV |
| 429 E. BOWEN RD. MAIL STOP 4015 |
| CHINA LAKE, CA 93555-6108 |
Direct Delivery Address (UPS, FedEx, etc.):
| COMMANDER |
| CODE 254220D (J. RODRIGUEZ – 760-939-3974) |
| NAVAIRWARCENWPNDIV |
| 429 E. BOWEN RD. MAIL STOP 4015 |
| CHINA LAKE, CA 93555-6108 |
*The Contractor has seven (7) days from posting for questions related to this RFQ.
Note: The Governement does not intend to provide financing for the awarded contract.
Section B - Supplies or Services and Prices
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
Test Seeker Van
FFP
The Contractor shall provide an IRSEV in accordance with the Statement of Work, in Section C.
FOB: Destination
NET AMT
Section C - Descriptions and Specifications
STATEMENT OF WORK
Statement of Work The Infrared Systems Evaluation Van Instrumentation and Data Processing Upgrade 05/10/2016
1.0 Background/Scope
The Infrared Systems Evaluation Van (IRSEV) is a fully equipped, mobile, self-contained field facility. The IRSEV is designed for comprehensive missile-seeker performance evaluation; it is also a validation platform for Threat Signal Processor-in-the-Loop (T-SPIL) simulations. The IRSEV is used in an open-air test environment with captive threat seekers against real aircraft and countermeasures in flight. IRSEV provides a means for testing the susceptibility of aircraft due to threat: Electro-Optical/Infrared Manportable Air Defense Systems (EO/IR MANPADS), vehicle-launched missiles, and air-to-air missiles.
In order to meet current and future requirements of joint services infrared countermeasure testing, IRSEV intends to procure an instrumentation and data processing system and tracking mount interface upgrade. The upgrade will have a commonality with the four (4) other seeker vans in the Department of Defense (DoD) test community required by the Program of Record, Common Infrared Countermeasure (CIRCM) Quick Reaction Capability (QRC), and Joint Urgent Operation Needs Statement (JUONS) requirements.
2.0 Applicable Documents
N/A
3.0 Requirements/Specifications
The Contractor shall provide an IRSEV. The following describes the specifications for systems to be procured required to support eight (8) seekers, including; two (2) control Boxes, ten (10) Pre-programmed power supplies, three (3) network switches and ten (10) data processing systems, high-definition video and operator interface components, two (2) high pressure control cabinets, and two (2) Eight (8) inch aperture mirror gimbals and six (6) six (6) inch aperture gimbals pre-programmed to communicate with the EO/IR seeker instrumentation. Each system shall meet the interoperability and compatibility to interface with the other test vans in the Seeker test Van community for IR Countermeasure testing. Each system type will be required to interface with current and future test items and have the ability to plug-n-play with assets from the other test vans. All specifications are the minimum requirements unless otherwise stated.
3.1 System A Shall Meet the Following Specifications:
General characteristics of control cabinets:
· Primary use: Controls seekers, gimbals, and gas pressure
· 56 analog input channels per cabinet
· 128 relay channels per cabinet
· 4 channel DAL per cabinet
3.1.1 Detailed specifications:
Table 1. Control Cabinet Requirements ( 2 Cabinets)
Communication and inputs
| Number of Channels per Cabinet |
| The system shall accept a minimum of 52 analog channels and 128 relay channels |
| Fiber optic and Ethernet |
| Fiber optic and Ethernet connection for operator control and feed back |
| Direct Input |
| Each analog input shall accept differential voltage up to +/- 60V. |
| Input Ranges |
| The system shall allow user selection of the input voltage conversion range via software, to include +/- 60V and +/- 1V at a minimum. |
| 4 Spin Cards per cabinet |
| Custom spin cards for operation of classified systems |
| Control Cabinets (2) |
| Control cabinets consisting of analog and digital channels required for operation of EO/IR seekers. Each Cabinet shall contain 4 seeker spin boards, serial communication hardware, ingress/ egress ports and all internal wiring. Each control cabinet should be 40” x 20” x 12” |
DC Power Supplies
There shall be 10 pre-programmed power supply mainframes required for operation of EO/IR Seekers. Each mainframe will consist of 4 power supply modules and be configured to operate with CompactRio hardware via the Ethernet.
| Low profile Mainframe |
| Low-profile Modular power system mainframe, 1200W, 4 Slots |
| DC Power Module |
| High-Performance Autoranging DC Power module 60V, 20A, 300W |
| Output Disconnect |
| Output Disconnect and polarity Reversal Relays |
| Power Module |
| Power Module, 100V, 3A, 300W |
| Network and Data Processing Systems |
| There shall be 3 network switches and 10 data processing systems that comprise the backbone architecture of a data collection system for field testing EO/IR seekers. All networking and data processing components shall be licensed, pre-programmed, tested, and fully functional as a monolithic data acquisition and storage environment. |
| DEWESOFT |
| DEWESOFT Professional License |
| Microsoft |
| Windows 10 Professional 64 Bit |
| Microsoft |
| Windows Enterprise Upgrade |
| Microsoft |
| Windows server 2012R2 Essentials |
| Gemalto |
| Safenet Client and Server Package |
| Video, Interconnect, and Operator Interface Components |
| The system shall be capable of delivering and recording High-Definition video, electro/optical interconnect, and operator interface components required to operate an EO/IR seeker test van. |
| Coolant Control |
| There shall be 2 coolant control cabinets consisting of high pressure electro-pneumatic hardware required for operation of EO/IR seekers. Each cabinet shell be capable of operating 4 seekers with 2 user-selectable input gases up to 6,000 psi. The coolant cabinets shall be preprogrammed to communicate with seeker instrumentation cabinets via analog and digital serial signals. |
| Gimbal Mirror Mounts |
| The mirror gimbals shall be pre-programmed to communicate with EO/IR seeker instrumentation via TCP/IP (Ethernet) or RS-232 (Serial) Ports. The Gimbal controllers shall be pre- loaded with configuration files and validated for operation with EO/IR seeker testing. |
| Gimbals |
| There shall be 6 Six-inch aperture mirror gimbals and 2 Eight-inch aperture mirror gimbals. |
| Warranty |
| The system shall be provided with a Standard Commercial Warranty. |
4.0 Delivery/Acceptance
The Contractor shall deliver the custom instrumentation is 270 days after award.
Section D - Packaging and Marking
CLAUSES INCORPORATED BY FULL TEXT
| 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 |
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 |
Section F - Deliveries or Performance
DELIVERY INFORMATION
| CLIN |
| DELIVERY DATE |
| QUANTITY |
| SHIP TO ADDRESS |
| DODAAC |
| 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). |
| _________________________Invoice__________________________________________________ | |
| (Contracting Officer: Insert applicable document type(s). Note: If a "Combo" document type is identified but not supportable by the Contractor's business systems, an "Invoice" (stand-alone) and "Receiving Report" (stand-alone) document type may be used instead.) | |
| | (2) Inspection/acceptance location. The Contractor shall select the following inspection/acceptance location(s) in WAWF, as specified by the contracting officer. |
| _________________________Not Applicable__________________________________________________ | |
| (Contracting Officer: Insert inspection and acceptance locations or "Not applicable.") | |
| | (3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system. |
| Routing Data Table* | | | | |
| Field Name in WAWF | | | Data to be entered in WAWF | |
| Pay Official DoDAAC: | | | ___*______________________ | |
| Issue By DoDAAC: | | | ___N68936______________________ | |
| Admin DoDAAC: | | | ___*______________________ | |
| Inspect By DoDAAC: | | | _________________________ | |
| Ship To Code: | | | | ___*______________________ |
| Ship From Code: | | | _________________________ | |
| Mark For Code: | | | _________________________ | |
| Service Approver (DoDAAC): | | _________________________ | | |
| Service Acceptor (DoDAAC): | | _________________________ | | |
| Accept at Other DoDAAC: | | _________________________ | | |
| LPO DoDAAC: | | | _________________________ | |
| DCAA Auditor DoDAAC: | | _________________________ | | |
| Other DoDAAC(s): | | | _________________________ | |
| (*Contracting Officer: Insert applicable DoDAAC information or "See schedule" if multiple ship to/acceptance locations apply, or "Not applicable.") | | | | |
| (4) Payment request and supporting documentation. The Contractor shall ensure a payment request includes appropriate contract line item and subline item descriptions of the work performed or supplies delivered, unit | | | |
price/cost per unit, fee (if applicable), and all relevant back-up documentation, as 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.
__danielle.mccarthy@navy.mil and jessica.r.rodriguez1@navy.mil__________________________________________________________________________ (Contracting Officer: Insert applicable email addresses or "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. |
*TO BE COMPLETED AT AWARD
| 5252.201-9502 | CONTRACTOR'S AUTHORIZED CONTRACT COORDINATOR AND TECHNICAL LIAISON (NAVAIR)(OCT 2005) | | | |
| (a) The contractor shall state below the name and telephone numbers of the contractor's employees responsible for coordination of contract functions/liaison with the Contracting Officer and/or Contract administrator, and providing technical assistance as required regarding product specifications, functionality, etc. | | | |
| | CONTRACT COORDINATOR: | | |
| | | NAME: | _________*______________________________ |
| | | PHONE (BUS): _____*______________________________ | |
| | | PHONE (AFTER HOURS): _*________________________ | |
| | ALTERNATE: | | |
| | | NAME: | _______________________________________ |
| | | PHONE (BUS): ___________________________________ | |
| | | PHONE (AFTER HOURS): _________________________ | |
| (b) The contractor shall notify the Contracting Officer and/or Contract Administrator in advance, in writing, of any changes in the above listed personnel. | | | |
*To be filled in at award
| 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: | |
(2) The following additional contract administration functions are assigned (see FAR 42.302(b)):
| Additional Functions |
| Retained for Performance By: |
All functions identified in FAR 43.302 and DFARS 242.302 not retained by PCO shall be assigned to DCMA.
DCMA
(c) Inquiries regarding payment should be referred to: MyInvoice at https://myinvoice.csd.disa.mil//index.html.
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.243-9504 | AUTHORIZED CHANGES ONLY BY THE CONTRACTING OFFICER (NAVAIR) (JAN 1992) |
| (a) Except as specified in paragraph (b) below, no order, statement, or conduct of Government personnel who visit the contractor's facilities or in any other manner communicates with contractor personnel during the performance of this contract shall constitute a change under the "Changes" clause of this contract. |
| (b) The contractor shall not comply with any order, direction or request of Government personnel unless it is issued in writing and signed by the Contracting Officer, or is pursuant to specific authority otherwise included as a part of this contract. |
| (c) The Contracting Officer is the only person authorized to approve changes in any of the requirements of this contract and notwithstanding provisions contained elsewhere in this contract, the said authority remains solely the Contracting Officer's. In the event the contractor effects any change at the direction of any person other than the Contracting Officer, the change will be considered to have been made without authority and no adjustment will be made in the contract price to cover any increase in charges incurred as a result thereof. The address and telephone number of the Contracting Officer is: Jessica Rodriguez, 760-939-3974, jessica.r.rodriguez1@navy.mil, Commander,NAWCWD (Code 254220D), Attn:Jessica Rodriguez, 429 E. Bowen Rd., Mail Stop 4015, China Lake, Ca 93555-6108 |
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 2015 |
| 52.204-19 |
| Incorporation by Reference of Representations and Certifications. |
| DEC 2014 |
| 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-14 |
| Integrity of Unit Prices |
| OCT 2010 |
| 52.215-21 |
| Requirements for Certified Cost or Pricing Data and Data Other Than Certified Cost or Pricing Data -- Modifications |
| OCT 2010 |
| 52.219-28 |
| Post-Award Small Business Program Rerepresentation |
| JUL 2013 |
| 52.222-19 |
| Child Labor -- Cooperation with Authorities and Remedies |
| FEB 2016 |
| 52.222-19 |
| Child Labor -- Cooperation with Authorities and Remedies |
| FEB 2016 |
| 52.222-20 |
| Contracts for Materials, Supplies, Articles, and Equipment Exceeding $15,000 |
| MAY 2014 |
| 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-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-3 |
| Federal, State And Local Taxes |
| FEB 2013 |
| 52.232-1 |
| Payments |
| APR 1984 |
| 52.232-8 |
| Discounts For Prompt Payment |
| FEB 2002 |
| 52.232-9 |
| Limitation On Withholding Of Payments |
| APR 1984 |
| 52.232-11 |
| Extras |
| APR 1984 |
| 52.232-25 |
| Prompt Payment |
| 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-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-5 |
| Competition In Subcontracting |
| DEC 1996 |
| 52.246-23 |
| Limitation Of Liability |
| FEB 1997 |
| 52.248-1 |
| Value Engineering |
| OCT 2010 |
| 52.249-1 |
| Termination For Convenience Of The Government (Fixed Price) (Short Form) |
| APR 1984 |
| 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-7000 |
| Disclosure Of Information |
| AUG 2013 |
| 252.204-7003 |
| Control Of Government Personnel Work Product |
| APR 1992 |
| 252.225-7013 |
| Duty-Free Entry--Basic (Nov 2014) |
| NOV 2014 |
| 252.232-7009 |
| Mandatory Payment by Governmentwide Commercial Purchase Card |
| DEC 2006 |
| 252.243-7001 |
| Pricing Of Contract Modifications |
| DEC 1991 |
| 252.247-7023 |
| Transportation of Supplies by Sea |
| APR 2014 |
| 252.247-7023 |
| Transportation of Supplies by Sea |
| APR 2014 |
| 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. |
| 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 INFORMATION (DEC 2015) | | | |
| (a) Definition. 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 defense information" means unclassified information that -- | | | |
| | (i) Is -- | | |
| | | (A) Provided to the contractor by or on behalf of DoD in connection with the performance of the contract; or | |
| | | (B) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract; and | |
| | (ii) Falls in any of the following categories: | | |
| | | (A) Controlled technical information. | |
| | | (B) Critical information (operations security). Specific facts identified through the Operations Security process about friendly intentions, capabilities, and activities vitally needed by adversaries for them to plan and act effectively so as to guarantee failure or unacceptable consequences for friendly mission accomplishment (part of Operations Security process). | |
| | | (C) Export control. Unclassified information concerning certain items, commodities, technology, software, or other information whose export could reasonably be expected to adversely affect the United States national security and nonproliferation objectives. To include dual use items; items identified in export administration regulations, international traffic in arms regulations and munitions list; license applications; and sensitive nuclear technology information. | |
| | | (D) Any other information, marked or otherwise identified in the contract, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies (e.g., privacy, proprietary business information). | |
| "Cyber incident" means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein. | | | |
| "Forensic analysis" means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data. | | | |
| "Malicious software" means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware. | | | |
| "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," http://dx.doi.org/10.6028/NIST.SP.800-171 that is in effect at the time the solicitation is issued or as authorized by the Contracting Officer, as soon as practical, but not later than December 31, 2017. The Contractor shall notify the DoD CIO, via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award; or |
| | | | (B) Alternative but equally effective security measures used to compensate for the inability to satisfy a particular requirement and achieve equivalent protection accepted in writing by an authorized representative of the DoD CIO; and |
| | | (2) Apply other security measures when the Contractor reasonably determines that such 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 this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve a covered contractor information system, including subcontracts for commercial items, without alteration, except to identify the parties; and | | |
| | (2) When this clause is included in a subcontract, require subcontractors to rapidly report cyber incidents directly to DoD at http://dibnet.dod.mil and the prime Contractor. This includes providing the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable. | | |
| 252.204-7012 | SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT INFORMATION (DEC 2015) | | | |
| (a) Definition. 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 defense information" means unclassified information that -- | | | |
| | (i) Is -- | | |
| | | (A) Provided to the contractor by or on behalf of DoD in connection with the performance of the contract; or | |
| | | (B) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract; and | |
| | (ii) Falls in any of the following categories: | | |
| | | (A) Controlled technical information. | |
| | | (B) Critical information (operations security). Specific facts identified through the Operations Security process about friendly intentions, capabilities, and activities vitally needed by adversaries for them to plan and act effectively so as to guarantee failure or unacceptable consequences for friendly mission accomplishment (part of Operations Security process). | |
| | | (C) Export control. Unclassified information concerning certain items, commodities, technology, software, or other information whose export could reasonably be expected to adversely affect the United States national security and nonproliferation objectives. To include dual use items; items identified in export administration regulations, international traffic in arms regulations and munitions list; license applications; and sensitive nuclear technology information. | |
| | | (D) Any other information, marked or otherwise identified in the contract, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies (e.g., privacy, proprietary business information). | |
| "Cyber incident" means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein. | | | |
| "Forensic analysis" means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data. | | | |
| "Malicious software" means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware. | | | |
| "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," http://dx.doi.org/10.6028/NIST.SP.800-171 that is in effect at the time the solicitation is issued or as authorized by the Contracting Officer, as soon as practical, but not later than December 31, 2017. The Contractor shall notify the DoD CIO, via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award; or |
| | | | (B) Alternative but equally effective security measures used to compensate for the inability to satisfy a particular requirement and achieve equivalent protection accepted in writing by an authorized representative of the DoD CIO; and |
This is the start of the file's text. The full file is on GovTribe.