18-R-0017_Solicitation_.doc

Section A - Solicitation/Contract Form

FOR YOUR INFORMATION

FOR YOUR INFORMATION:

The following addresses and points of contact are provided:

CONTRACT SPECIALIST

Name: Janet Campbell

Phone: (760) 939-9507

DSN:

437-9507

FAX: (760) 939-0528

Email: janet.campbell@navy.mil U.S. Postal Service Mailing Address:

NAWCWD

CODE 254230D (J. Campbell 760-939-9507)

NAVAIRWARCENWPNDIV

429 E. BOWEN RD. MAIL STOP 4015

CHINA LAKE, CA 93555-610

Direct Delivery Address (UPS, FedEx, etc.)

NAWCWD

CODE 254230D (J. Campbell)

NAVAIRWARCENWPNDIV

BLDG 982, MAIL STOP 4015

CHINA LAKE, CA 93555-6108

CONTRACTING OFFICER:

Name: Sierra Trepanier

Phone: (760) 939-8958

DSN: 437-8958

FAX: (760) 939-0528

Email: sierra.trepanier@navy.mil

U.S. Postal Service Mailing Address:

NAWCWD

CODE 254230D (S. Trepanier – 760- 939-8958)

NAVAIRWARCENWPNDIV

429 E. BOWEN RD. MAIL STOP 4015

CHINA LAKE, CA 93555-6108

Direct Delivery Address (UPS, FedEx, etc):

NAWCWD

CODE 254230D (S. Trepanier – 760-939-8958)

429 E. BOWEN RD.

MAIL STOP 4015

CHINA LAKE, CA 93555-6108

The Government will not provide financing for the awarded contract.

Section B - Supplies or Services and Prices

JAGM MLE Software Updates

FFP

The contractor shall assemble, test, and deliver four-station MLE (PN JLE00010-4) software update in accordance with the Statement of Work (SOW) in Section C.

FOB: Destination

PURCHASE REQUEST NUMBER: 1300680785

NET AMT

Section C - Descriptions and Specifications

STATEMENT OF WORK

JAGM MLEJ Software Update (NAVY)

[MLE P/N JLE00010-4]

1.0 BACKGROUND:

The objective of this effort is to procure a Missile Launcher Emulator JAGM (MLEJ) systems software update in support of the Navy Hellfire K, P+, R and Joint Air-to-Ground Missile (JAGM) integration program. The MLEJs are existing Special Test Equipment used to support the integration, test, and verification of M299 Launchers and the Hellfire/JAGM series of missiles at the MIL-STD-1760 interface to host platforms. The Contractor will update, integrate, and test existing software to be integrated in the MLEJs to support: JAGM (current Army acquisition), Hellfire K, P+, and R candidate missile designs on M299 launchers. The MLEJs special test equipment includes a hardware and software design that has been applied to a number of platform-launcher-store configurations and programs over the past decade. The existing MLEJs that have specifically supported M-299 and Hellfire/JAGM efforts require development of updated launcher models/simulations and missile model/simulations to support the program objectives for planned laboratory and platform integration testing.

1.1 SCOPE

This requirement is for the assembly, test, and delivery of an updated software package that capable of being loaded on any of the four-station MLEJ systems, P/N JLE00010-4. The updated software shall provide user selectable embedded missile emulation of Hellfire K, P+, R, and JAGM missiles and their Captive Air Training Missile (CATM) equivalents on M299 launchers. The updated software shall emulate the planned production versions of Launcher software as specified by MIS-ICD-56599 and Missile software as specified by MIS-ICD-58352. The updated software will be used by the Navy to support of planned weapon integration laboratory and aircraft integration laboratory development activities.

2.0 APPLICABLE DOCUMENTS

Wintec document WPCN-JLE00010-20051216 (current version)

JAMS MIS-ICD-56599 JOINT ATTACK MUNITION SYSTEMS (JAMS) LAUNCHER TO PLATFORM INTERFACE CONTROL DOCUMENT VOLUME II

JAMS MIS-ICD-58352 JOINT AIR TO GROUND MISSILE (JAGM) LAUNCHER TO JAGM INTERFACE CONTROL DOCUMENT VOLUME II

3.0 REQUIREMENTS:

3.1 The Contractor shall provide a software package that is able to be loaded on any of Navy MLEJ rev (2) systems that will provide user selectable embedded missile emulation of Hellfire K, P+, R and JAGM missiles on M299 launchers with the current M299 (AD05, FA0X software) interface per MIS-ICD-56599 and JAGM missile (1.13.0 software) interface per MIS-ICD-56599 and MIS-ICD-58352. Specifically the JAGM K Operational Mode (KOM), P operational Mode (POM), and JAGM Operational Mode (JOM) launcher and missile simulations shall be upgraded to planned production software (FA0A and 1.13.0). The logistical function of Health Maintenance Data will be implemented for all individual missile simulations.

The Multiple Launcher Emulator JAGM (MLEJ) software package shall be upgraded to operate on the Windows 10 operating system. The Multiple Launcher Emulator JAGM (MLEJ) software package shall have a Windows user interface installer for the laptop controller and MLEJ binary files for the Launcher Emulator Modules (LEMs). The updated software package replaces the MLEJ2, MLEJ and MLER software package, but the MLEJ2, MLEJ or MLER software may be reloaded over the MLEJx software at any time. The LEM shall load application software based on the configuration id switch (i.e., MLER, MLEJ, MLEJ2, MLEx). The Contractor shall assemble, test, and deliver four-station MLE (P/N JLE00010-4) software update to the Navy to support planned weapon integration laboratory and aircraft integration laboratory development activities. Each MLEJ shall be capable of supporting at least one, and up to four platform stations/launchers each supporting at least one, and up to four missiles per launcher.

3.2 Travel is required for test, evaluation, verification, and final acceptance of the updated software. It is estimated that 2 trips for 2 travelers for 2 days in the AMRDEC Weapon Integration Laboratory (WIL) facility in Huntsville Alabama shall be needed. In addition 2 trips to the JAMS JICWG in Huntsville Alabama for one traveler for 2 days shall be planned to support technical interchange meetings.

3.3 No special security requirements are required. This contract is unclassified.

3.4 Government Furnished Equipment items to be provided: A MLEJ hardware suite (laptop with 4 LEMs and cables) as GFE for development and test. The government will be responsible for shipping the GFE to the contractor after contract award and the contractor shall be responsible for return shipping the GFE to the government at the completion of the contract.

4.0 DELIVERABLES

4.1 The Contractor shall prepare the following and deliver to:

NAVAL AIR WARFARE CENTER WEAPONS DIVISION

1 ADMINISTRATION CIRCLE

CHINA LAKE CA 93555-6001

MARK FOR: MATTHEW ARTELT CODE 471K00D

PHONE 760-939-3920

4.2 Software: The Contractor shall deliver the four-station MLE system software configured to individual MLE units (to support up to four platform missile stations), the Emulator Control Station (ECS) test control computer, and MIL-STD-1760 and ECS cables. The Contractor shall include MLE System documentation and user Manual for operating the MLEs. Contractor format is acceptable.

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:

CLAUSES INCORPORATED BY REFERENCE

Section F - Deliveries or Performance

DELIVERY INFORMATION

FOB: Destination

CLAUSES INCORPORATED BY REFERENCE

Section G - Contract Administration Data

CLAUSES INCORPORATED BY FULL TEXT

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:

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.

(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 FILLED IN AT AWARD

5252.201-9500

TECHNICAL POINT OF CONTACT (TPOC)(NAVAIR)(SEP 2012)

(a) The Technical Point of Contact (TPOC) for this contract is:[insert name, code, mailing address, and telephone number]*

(b) This individual is not a Contracting Officer nor a Contracting Officer's Representative (COR)/Task Order COR (TOCOR) and has no authority to make changes, verbally or otherwise, to the existing contract or order. Further, no authority has been delegated to this individual by the Procuring Contracting Officer (PCO).

(c) The contractor may use this technical POC for technical questions related to the existing contract or order. Also, as a representative of the requiring activity, the TPOC may perform or assist in such areas as: base access forms, security related issues, IT access requirements, Contractor Performance Assessment Reporting System (CPARS), clarification of technical requirements, and statement of work inquires.

(d) The contractor shall immediately notify the Procuring Contracting Officer in writing if the contractor interprets any action by the TPOC to be a change to the existing contract.

5252.242-9511

CONTRACT ADMINISTRATION DATA (NAVAIR)(NOV 2017)

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

[Repeat as necessary.

(2) The following additional contract administration functions are assigned (see FAR 42.302(b)):

[Repeat as necessary.

(c) Inquiries regarding payment should be referred to: MyInvoice through the Wide Area Workflow eBusiness Suite: https://wawf.eb.mil.

CLAUSES INCORPORATED BY FULL TEXT

G-TXT-01

ATTENTION! E-MAIL ADDRESS REQUIRED FOR DISTRIBUTION

All Naval Air Warfare Center Weapons Division Contracts/ Purchase Orders and other related documents are now distributed by electronic mail.

Please provide the e-mail address to which distribution of contracts/purchase orders should be made.

E-Mail Address:___*________________________________________________

Section H - Special Contract Requirements

CLAUSES INCORPORATED BY FULL TEXT

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.

Section I - Contract Clauses

CLAUSES INCORPORATED BY REFERENCE

52.204-19

INCORPORATION BY REFERENCE OF REPRESENTATIONS AND CERTIFICATIONS (DEC 2014)

The Contractor's representations and certifications, including those completed electronically via the System for Award Management (SAM), are incorporated by reference into the contract.

52.219-28

POST-AWARD SMALL BUSINESS PROGRAM REREPRESENTATION (JUL 2013)

(a) Definitions. As used in this clause--

Long-term contract means a contract of more than five years in duration, including options. However, the term does not include contracts that exceed five years in duration because the period of performance has been extended for a cumulative period not to exceed six months under the clause at 52.217-8, Option to Extend Services, or other appropriate authority.

Small business concern means a concern, including its affiliates, that is independently owned and operated, not dominant in the field of operation in which it is bidding on Government contracts, and qualified as a small business under the criteria in 13 CFR part 121 and the size standard in paragraph (c) of this clause. Such a concern is “not dominant in its field of operation” when it does not exercise a controlling or major influence on a national basis in a kind of business activity in which a number of business concerns are primarily engaged. In determining whether dominance exists, consideration shall be given to all appropriate factors, including volume of business, number of employees, financial resources, competitive status or position, ownership or control of materials, processes, patents, license agreements, facilities, sales territory, and nature of business activity.

(b) If the Contractor represented that it was a small business concern prior to award of this contract, the Contractor shall rerepresent its size status according to paragraph (e) of this clause or, if applicable, paragraph (g) of this clause, upon the occurrence of any of the following:

(1) Within 30 days after execution of a novation agreement or within 30 days after modification of the contract to include this clause, if the novation agreement was executed prior to inclusion of this clause in the contract.

(2) Within 30 days after a merger or acquisition that does not require a novation or within 30 days after modification of the contract to include this clause, if the merger or acquisition occurred prior to inclusion of this clause in the contract.

(3) For long-term contracts--

(i) Within 60 to 120 days prior to the end of the fifth year of the contract; and

(ii) Within 60 to 120 days prior to the date specified in the contract for exercising any option thereafter.

(c) The Contractor shall rerepresent its size status in accordance with the size standard in effect at the time of this rerepresentation that corresponds to the North American Industry Classification System (NAICS) code assigned to this contract. The small business size standard corresponding to this NAICS code can be found at http://www.sba.gov/content/table-small-business-size-standards/ .

(d) The small business size standard for a Contractor providing a product which it does not manufacture itself, for a contract other than a construction or service contract, is 500 employees.

(e) Except as provided in paragraph (g) of this clause, the Contractor shall make the rerepresentation required by paragraph (b) of this clause by validating or updating all its representations and Certification section of the System for Award Management (SAM) and its other data in SAM, as necessary, to ensure that they reflect the Contractor's current status. The Contractor shall notify the contracting office in writing within the timeframes specified in paragraph (b) of this clause that the data have been validated or updated, and provide the date of the validation or update.

(f) If the Contractor represented that it was other than a small business concern prior to award of this contract, the Contractor may, but is not required to, take the actions required by paragraphs (e) or (g) of this clause.

(g) If the Contractor does not have representations and certifications in SAM, or does not have a representation in SAM for the NAICS code applicable to this contract, the Contractor is required to complete the following rerepresentation and submit it to the contracting office, along with the contract number and the date on which the rerepresentation was completed:

*The Contractor represents that it [ ] is, [ ] is not a small business concern under NAICS Code 541511assigned 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

*To be completed at award.

CLAUSES INCORPORATED BY FULL TEXT

52.222-54

EMPLOYMENT ELIGIBILITY VERIFICATION (OCT 2015)

(a) Definitions. As used in this clause-

“Commercially available off-the-shelf (COTS)” item--

(1) Means any item of supply that is--

(i) A commercial item (as defined in paragraph (1) of the definition at 2.101);

(ii) Sold in substantial quantities in the commercial marketplace; and

(iii) Offered to the Government, without modification, in the same form in which it is sold in the commercial marketplace; and

(2) Does not include bulk cargo, as defined in 46 U.S.C. 40102(4), such as agricultural products and petroleum products. Per 46 CFR 525.1(c)(2), “bulk cargo” means cargo that is loaded and carried in bulk onboard ship without mark or count, in a loose unpackaged form, having homogenous characteristics. Bulk cargo loaded into intermodal equipment, except LASH or Seabee barges, is subject to mark and count and, therefore, ceases to be bulk cargo.

“Employee assigned to the contract” means an employee who was hired after November 6, 1986 (after November 27, 2009, in the Commonwealth of the Northern Mariana Islands), who is directly performing work, in the United States, under a contract that is required to include the clause prescribed at 22.1803. An employee is not considered to be directly performing work under a contract if the employee--

(1) Normally performs support work, such as indirect or overhead functions; and

(2) Does not perform any substantial duties applicable to the contract.

“Subcontract” means any contract, as defined in 2.101, entered into by a subcontractor to furnish supplies or services for performance of a prime contract or a subcontract. It includes but is not limited to purchase orders, and changes and modifications to purchase orders.

“Subcontractor” means any supplier, distributor, vendor, or firm that furnishes supplies or services to or for a prime Contractor or another subcontractor.

“United States”, as defined in 8 U.S.C. 1101(a)(38), means the 50 States, the District of Columbia, Puerto Rico, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands.

(b) Enrollment and verification requirements.

(1) If the Contractor is not enrolled as a Federal Contractor in E-Verify at time of contract award, the Contractor shall--

(i) Enroll. Enroll as a Federal Contractor in the E-Verify program within 30 calendar days of contract award;

(ii) Verify all new employees. Within 90 calendar days of enrollment in the E-Verify program, begin to use E-Verify to initiate verification of employment eligibility of all new hires of the Contractor, who are working in the United States, whether or not assigned to the contract, within 3 business days after the date of hire (but see paragraph (b)(3) of this section); and

(iii) Verify employees assigned to the contract. For each employee assigned to the contract, initiate verification within 90 calendar days after date of enrollment or within 30 calendar days of the employee's assignment to the contract, whichever date is later (but see paragraph (b)(4) of this section).

(2) If the Contractor is enrolled as a Federal Contractor in E-Verify at time of contract award, the Contractor shall use E-Verify to initiate verification of employment eligibility of--

(i) All new employees.

(A) Enrolled 90 calendar days or more. The Contractor shall initiate verification of all new hires of the Contractor, who are working in the United States, whether or not assigned to the contract, within 3 business days after the date of hire (but see paragraph (b)(3) of this section); or

(B) Enrolled less than 90 calendar days. Within 90 calendar days after enrollment as a Federal Contractor in E-Verify, the Contractor shall initiate verification of all new hires of the Contractor, who are working in the United States, whether or not assigned to the contract, within 3 business days after the date of hire (but see paragraph (b)(3) of this section); or

(ii) Employees assigned to the contract. For each employee assigned to the contract, the Contractor shall initiate verification within 90 calendar days after date of contract award or within 30 days after assignment to the contract, whichever date is later (but see paragraph (b)(4) of this section).

(3) If the Contractor is an institution of higher education (as defined at 20 U.S.C. 1001(a)); a State or local government or the government of a Federally recognized Indian tribe; or a surety performing under a takeover agreement entered into with a Federal agency pursuant to a performance bond, the Contractor may choose to verify only employees assigned to the contract, whether existing employees or new hires. The Contractor shall follow the applicable verification requirements at (b)(1) or (b)(2), respectively, except that any requirement for verification of new employees applies only to new employees assigned to the contract.

(4) Option to verify employment eligibility of all employees. The Contractor may elect to verify all existing employees hired after November 6, 1986 (after November 27, 2009, in the Commonwealth of the Northern Mariana Islands), rather than just those employees assigned to the contract. The Contractor shall initiate verification for each existing employee working in the United States who was hired after November 6, 1986 (after November 27, 2009, in the Commonwealth of the Northern Mariana Islands), within 180 calendar days of--

(i) Enrollment in the E-Verify program; or

(ii) Notification to E-Verify Operations of the Contractor's decision to exercise this option, using the contact information provided in the E-Verify program Memorandum of Understanding (MOU).

(5) The Contractor shall comply, for the period of performance of this contract, with the requirements of the E-Verify program MOU.

(i) The Department of Homeland Security (DHS) or the Social Security Administration (SSA) may terminate the Contractor's MOU and deny access to the E-Verify system in accordance with the terms of the MOU. In such case, the Contractor will be referred to a suspension or debarment official.

(ii) During the period between termination of the MOU and a decision by the suspension or debarment official whether to suspend or debar, the Contractor is excused from its obligations under paragraph (b) of this clause. If the suspension or debarment official determines not to suspend or debar the Contractor, then the Contractor must reenroll in E-Verify.

(c) Web site. Information on registration for and use of the E-Verify program can be obtained via the Internet at the Department of Homeland Security Web site: http://www.dhs.gov/E-Verify.

(d) Individuals previously verified. The Contractor is not required by this clause to perform additional employment verification using E-Verify for any employee--

(1) Whose employment eligibility was previously verified by the Contractor through the E-Verify program;

(2) Who has been granted and holds an active U.S. Government security clearance for access to confidential, secret, or top secret information in accordance with the National Industrial Security Program Operating Manual; or

(3) Who has undergone a completed background investigation and been issued credentials pursuant to Homeland Security Presidential Directive (HSPD)-12, Policy for a Common Identification Standard for Federal Employees and Contractors.

(e) Subcontracts. The contractor shall include the requirements of this clause, including this paragraph (e) (appropriately modified for identification of the parties), in each subcontract that -

Is for--

(i) Commercial or noncommercial services (except for commercial services that are part of the purchase of a COTS item (or an item that would be a COTS item, but for minor modifications), performed by the COTS provider, and are normally provided for that COTS item); or

(ii) Contraction;

(2) Has a value of more than $3,500; and

(3) Includes work performed in the United States.

52.223-19

COMPLIANCE WITH ENVIRONMENTAL MANAGEMENT SYSTEMS (MAY 2011)

The Contractor's work under this contract shall conform with all operational controls identified in the applicable agency or facility Environmental Management Systems and provide monitoring and measurement information necessary for the Government to address environmental performance relative to the goals of the Environmental Management Systems.

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.232-40

PROVIDING ACCELERATED PAYMENTS TO SMALL BUSINESS SUBCONTRACTORS (DEC 2013)

(a) Upon receipt of accelerated payments from the Government, the Contractor shall make accelerated payments to its small business subcontractors under this contract, to the maximum extent practicable and prior to when such payment is otherwise required under the applicable contractor or subcontract, after receipt of a proper invoice and all other required documentation from the small business subcontractor.

(b) The acceleration of payments under this clause does not provide any new rights under the Prompt Payment Act.

(c) Include the substance of this clause, including this paragraph (c), in subcontracts with small business concerns, including subcontracts with small business concerns for the acquisition of commercial items.

52.251-1

GOVERNMENT SUPPLY SOURCES (APR 2012)

The Contracting Officer may issue the Contractor an authorization to use Government supply sources in the performance of this contract. Title to all property acquired by the Contractor under such an authorization shall vest in the Government unless otherwise specified in the contract. The provisions of the clause at FAR 52.245-1, “Government Property”, apply to all property acquired under such authorization.

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 (OCT 2016) - ALTERNATE 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 "Unique Entity Identifier" followed by the unique entity identifier that identifies the Offeror's name and address exactly as stated in the offer. The Offeror also shall enter its EFT indicator, if applicable. The unique entity identifier 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 unique entity designator, it should contact the entity designated at www.sam.gov for establishment of the unique entity identifier directly to obtain one. The Offeror should be prepared to provide the following information:

(1) Company legal business.

(2) Tradestyle, doing business, or other name by which your entity is commonly recognized.

(3) Company Physical Street Address, City, State, and Zip Code.

(4) Company Mailing Address, City, State and Zip Code (if separate from physical).

(5) Company Telephone Number.

(6) Date the company was started.

(7) Number of employees at your location.

(8) Chief executive officer/key manager.

(9) Line of business (industry).

(10) 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 (OCT 2016)

(a) Definitions. As used in this clause --

"Adequate security" means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information.

"Compromise" means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred.

"Contractor attributional/proprietary information" means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company.

"Controlled technical information" means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination. Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements on Technical Documents. The term does not include information that is lawfully publicly available without restrictions.

"Covered contractor information system" means an unclassified information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information.

"Covered defense information" means unclassified controlled technical information or other information, as described in the Controlled Unclassified Information (CUI) Registry at http://www.wrchives.gov/cui/registry/category-list.html, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies, and is --

(1) Marked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract; or

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

"Cyber incident" means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein.

"Forensic analysis" means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data.

"Information system" means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information.

"Malicious software" means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware.

"Media" means physical devices or writing surfaces including, but not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which covered defense information is recorded, stored, or printed within a covered contractor information system.

"Operationally critical support" means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation.

"Rapidly report" means within 72 hours of discovery of any cyber incident.

"Technical information" means technical data or computer software, as those terms are defined in the clause at DFARS 252.227-7013, Rights in Technical Data - Non Commercial Items, regardless of whether or not the clause is incorporated in this solicitation or contract. Examples of technical information include research and engineering date, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code.

(b) Adequate security. The Contractor shall provide adequate security for all covered contractor information systems. To provide adequate security, the Contractor shall implement, at a minimum, the following information security protections:

(1) For covered contractor information systems that are part of an information technology (IT) service or system operated on behalf of the Government, the following security requirements apply:

(i) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010, Cloud Computing Services, of this contract.

(ii) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract.

(2) For covered contractor information systems that are not part of an IT service or system operated on behalf of the Government and therefore are not subject to the security requirement specified at paragraph (b)(1) of this clause, the following security requirements apply:

(i) Except as provided in paragraph (b)(2)(ii) of this clause, the covered contractor information system shall be subject to the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, "Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations," (available via the internet at http://dx.doi.org/10.6028/NIST.SP.800-171) that is in effect at the time the solicitation is issued or as authorized by the Contracting Officer.

(ii)(A) The Contractor shall submit requests to vary from NIST SP 800-171, as soon as practical, but not later than December 31, 2017. For all contracts awarded prior to October 1, 2017, the Contractor shall notify the DoD Chief Information Officer (CIO), via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award.

(B) The Contractor shall submit requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO.