Solicitation N0042120R0149.pdf

SEE ADDENDUM

(No Collect Calls)

N0042120R0149 13-May-2020

b. TELEPHONE NUMBER

301-757-7032

8. OFFER DUE DATE/LOCAL TIME

02:30 PM 28 May 2020

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

N004219. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

SHANNON M. CANADA

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

1300845014

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED ORX

SMALL BUSINESS

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

NAWCAD PROCUREMENT GROUP

21983 BUNDY ROAD, BLDG 3272

PATUXENT RIVER MD 20670

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE 16. ADMINISTERED BY

SEE SCHEDULE

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

FAX:

TEL: SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$41,500,000

NAICS:

511210

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF26

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

N0042120R0149

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 1 Each

VXWORKS 653 MULTI CORE CERT ADDITION

FFP

1.00VxWorks 653 Multi-Core Edition Cert Edition 3 - Project License - Perpetual

PPC: Freescale: QorIQ T2xxx (500-185649).

NOTE: The requirements in DFARS 252.211-7003, Item Identification and

Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

FOB: Destination

NSN: 70301021191334

PURCHASE REQUEST NUMBER: 1300845014

PSC CD: 7030

NET AMT

0002 1 Each

PROJECT LICENSE MAINTENANCE

FFP

LIC 1.01 Project License Maintenance PPC: Freescale: QorIQ T2xxx (535-

186273).

NOTE: The requirements in DFARS 252.211-7003, Item Identification and

Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

FOB: Destination

NSN: 70301020739419

0003 2 Each

USI ELECTRONICS SUPPORT & MAINTENANCE

FFP

LIC 2.00 Support & Maintenance - Object Code, Node Locked, for VxWorks 653

Multi-Core Edition 3 PPC: Freescale: QorIQ T2xxx (5 35-103796).

NOTE: The requirements in DFARS 252.211-7003, Item Identification and

Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

FOB: Destination

NSN: 69101020588306

PSC CD: 6910

0004 2 Each

LIC 2.01 WIND RIVER VXWORKS 653 MULTI-CO

FFP

LIC 2.01 Wind River VxWorks 653 Multi-Core Edition 3, Perpetual, Node Locked

PPC: Freescale: QorIQ T2xxx (500-182725).

FOB: Destination

0005 13 Each

RUNTIME LICENSES

FFP

LIC 3.00 - VxWorks Safety Critical Production License Pre-Buy without Labels

PPC: Freescale: QorIQ T2xxx (540-184457).

FOB: Destination

NSN: 70301021168917

Section C - Descriptions and Specifications

STATEMENT OF WORK

Statement of Work

For Wind River VxWorks

Background:

The Atlantic Test Range, Range Display Systems (RDS) team is developing a Ground Based

Detect and Avoid System (GBDAA) for UAS operations. The system will be used to enhance aircraft test situational awareness and alleviate much of the visual observer and manned aircraft chase for flights in and between the Patuxent River Naval Air Station, MD (PAX) restricted airspace. The Guardian GBDAA system will be used to support ATR unmanned aircraft platforms and will serve as a safety of flight critical system. As a safety critical system, development is required on and for safety certified hardware and must run on a safety certified

Operating System (OS) which meets the DO-178C and MIL-STD-882E requirements, as well as customer, operational and system requirements in order to meet needed capabilities while maintaining system safety integrity.

The Guardian project falls under the authority of the Central Test and Evaluation Investment

Program (CTEIP). The Airspace, Integration, and Teaming (AIT) is the entity within CTEIP that is responsible for Guardian development and fulfill the vision for fully integrating Unmanned

Aerial Surveillance into the National Airspace System (NAS) allowing UAS operating harmoniously, side-by-side with manned aircraft, occupying the same airspace.

Scope:

The NAWCAD ATR has a requirement for the procurement of a one time firm-fixed priced

(FFP) order follow on contract number N0042119P0247 of Wind River VxWorks 653 Multi-

Core Software and Maintenance. While the VxWorks purchase is a perpetual purchase (the software belongs to the US Navy in perpetuity), Maintenance of that software is annually renewable. Maintenance includes access to the Wind River online Knowledge Base for your users to self-service any technical issues that may arise, as well as access to our customer support team for any issues they are having with the software. Maintenance is mandatory for the first year, and is optional for each 12-month period after the first year. Without an annual

Maintenance agreement in place for the software referenced above, our development team would run the risk of having to self-diagnose and solve any Wind River software related issues independent of support from our team causing delays and quality of product.

The following are minimum requirement of the government:

Solution MUST be a real-time operating system

Solution MUST support avionics systems

Solution MUST satisfy DO-178C DAL-B certification standards

Solution MUST be able to provide DO-178C certification evidence

Solution MUST support ARINC 653 applications

Solution MUST provide development and debugging tools

Solution MUST support multi-core processors

Solution MUST support time and space partitioning

Solution MUST provide installation and integration support

Solution MUST provide system engineering and architecture support

Solution MUST provide DO-178 compliant Network Stack

Solution MUST provide virtual simulated target hardware capability for software development

Solution MUST support Future Airborne Capabilities Environment (FACE) Technical

Standards

Solution MUST provide product update and maintenance support

The following capabilities are provided by the identified solution:

RTCA DO-178C CERTIFICATION EVIDENCE

To ensure that airborne systems meet the demands of a variety of safety criticality levels, the global aerospace community developed the RTCA DO-178C and EUROCAE

ED-12C airborne avionics standards. These standards provide guidance on creating, certifying, and deploying airborne systems. They are now uniformly enforced by a wide range of commercial aviation control organizations, including the U.S. Federal Aviation

Administration (FAA), the European Aviation Safety Agency (EASA), Transport

Canada, and others.

VxWorks 653 Multi-core Edition offers a commercial off-the-shelf (COTS) DO-

178C and ED-12C Certification Evidence package, which provides comprehensive safety certification evidence, enabling avionics manufacturers to meet the stringent DO-178C.

This certification evidence contains artifacts from core components VxWorks GOS APIs, and ARINC 653 APEX APIs. These artifacts include designs, tests, reviews, source code, build files, test results, annotated object-level code coverage, and tool qualification data for critical IMA systems.

VxWorks 653 Multi-core Edition offers a range of benefits for avionics development teams, including the following:

Industry standards conformance: Runtime conformant to global avionics and to business safety standards such as ARINC Specification 653, POSIX®, the Future

Airborne Capabilities Environment (FACE™) Technical Standard, RTCA DO-

178C, and RTCA DO-297

Safety and security: Time and space partitioning with MMU and hardware virtualization assist, deterministic software, and strict communications control

Certification evidence: COTS certification evidence to support rapid customer certification

Portability: The ability to reuse existing ARINC 653 applications and VxWorks kernel mode applications and drivers, from “simple” systems to complex systems and next generation virtualized multi-core platforms

Development tools: Powerful kernel-aware development and debugging tools including Wind River® Workbench

Wind River DO-178 Network Stack for VxWorks 653, a configurable option for Wind

River VxWorks 653 Multi-core Edition, is a UDP/TCP IPv4 network stack that provides the following main features:

UDP/TCP IPv4 stack over Ethernet

BSD sockets API

ICMPv4

IGMPv1

Multi-cast

Certification evidence for DO-178C Level A is available

Installation and orientation service

Onsite installation: Guided installation on your hardware and host platform, along with a sample build process, demonstrations, and examples of customizations

Hands-on orientation: Architecture, development file system, adding open source packages, porting drivers, addressing design issues

Advice: Introduction to Wind River support channels and processes, additional services, project review, and consultation The Wind River Installation and

Orientation Service accelerates engineering productivity and helps our customers reach the full potential of the VxWorks 653 3.x Platform.

Delivery Items:

LIC 1.00 VxWorks 653 Multi-Core Edition Cert Edition 3 - Project License – Perpetual PPC:

Freescale: QorIQ T2xxx

Qty: 1

LIC 1.01 Project License Maintenance PPC: Freescale: QorIQ T2xxx

P/N: 535-186273

Qty: 1

LIC 2.00 Support & Maintenance - Object Code, Node Locked, for VxWorks 653 Multi-Core

Edition 3 PPC: Freescale: QorIQ T2xxx

P/N: 535-103796

Qty: 2

LIC 2.01Wind River VxWorks 653 Multi-Core Edition 3, Perpetual, Node Locked PPC:

Freescale: QorIQ T2xxx

P/N: 500-182725

Qty: 2

LIC 3.00 - VxWorks Safety Critical Production License Pre-Buy without Labels PPC: Freescale:

QorIQ T2xxx

P/N: 540-184457

Qty: 13

PoP:

12 Months after the receipt of the order (ARO).

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 N/A N/A N/A Government

0002 N/A N/A N/A Government

0003 N/A N/A N/A Government

0004 N/A N/A N/A Government

0005 N/A N/A N/A Government

Section F - Deliveries or Performance

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

0001 31-MAY-2021 1 N/A

0002 31-MAY-2021 1 N/A

0003 31-MAY-2021 2 N/A

0004 31-MAY-2021 2 N/A

0005 31-MAY-2021 13 N/A

CLAUSES INCORPORATED BY REFERENCE

52.247-34 F.O.B. Destination NOV 1991

Section G - Contract Administration Data

CLAUSES INCORPORATED BY FULL TEXT

252.232-7003 ELECTRONIC SUBMISSION OF PAYMENT REQUESTS AND RECEIVING REPORTS (DEC

2018)

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

Contract financing payment means an authorized Government disbursement of monies to a contractor prior to acceptance of supplies or services by the Government.

(1) Contract financing payments include--

(i) Advance payments;

(ii) Performance-based payments;

(iii) Commercial advance and interim payments;

(iv) Progress payments based on cost under the clause at Federal Acquisition Regulation (FAR) 52.232-16, Progress

Payments;

(v) Progress payments based on a percentage or stage of completion (see FAR 32.102(e)), except those made under the clause at FAR 52.232-5, Payments Under Fixed-Price Construction Contracts, or the clause at FAR 52.232-10, Payments Under Fixed-Price Architect-Engineer Contracts; and

(vi) Interim payments under a cost reimbursement contract, except for a cost reimbursement contract for services when Alternate I of the clause at FAR 52.232-25, Prompt Payment, is used.

(2) Contract financing payments do not include--

(i) Invoice payments;

(ii) Payments for partial deliveries; or

(iii) Lease and rental payments.

Electronic form means any automated system that transmits information electronically from the initiating system to affected systems.

Invoice payment means a Government disbursement of monies to a contractor under a contract or other authorization for supplies or services accepted by the Government.

(1) Invoice payments include--

(i) Payments for partial deliveries that have been accepted by the Government;

(ii) Final cost or fee payments where amounts owed have been settled between the Government and the contractor;

(iii) For purposes of subpart 32.9 only, all payments made under the clause at 52.232-5, Payments Under Fixed-

Price Construction Contracts, and the clause at 52.232-10, Payments Under Fixed-Price

Architect-Engineer Contracts; and

(iv) Interim payments under a cost-reimbursement contract for services when Alternate I of the clause at 52.232-25, Prompt Payment, is used.

(2) Invoice payments do not include contract financing payments.

Payment request means any request for contract financing payment or invoice payment submitted by the Contractor under this contract or task or delivery order.

Receiving report means the data prepared in the manner and to the extent required by Appendix F, Material

Inspection and Receiving Report, of the Defense Federal Acquisition Regulation Supplement.

(b) Except as provided in paragraph (d) of this clause, the Contractor shall submit payment requests and receiving reports in electronic form using Wide Area WorkFlow (WAWF). The Contractor shall prepare and furnish to the

Government a receiving report at the time of each delivery of supplies or services under this contract or task or delivery order.

(c) Submit payment requests and receiving reports to WAWF in one of the following electronic formats:

(1) Electronic Data Interchange.

(2) Secure File Transfer Protocol.

(3) Direct input through the WAWF website.

(d) The Contractor may submit a payment request and receiving report using methods other than WAWF only when-

(1) The Contractor has requested permission in writing to do so, and the Contracting Officer has provided instructions for a temporary alternative method of submission of payment requests and receiving reports in the contract administration data section of this contract or task or delivery order;

(2) DoD makes payment for commercial transportation services provided under a Government rate tender or a contract for transportation services using a DoD-approved electronic third party payment system or other exempted vendor payment/invoicing system (e.g., PowerTrack, Transportation Financial Management System, and Cargo and

Billing System);

(3) DoD makes payment on a contract or task or delivery order for rendered health care services using the

TRICARE Encounter Data System; or

(4) The Governmentwide commercial purchase card is used as the method of payment, in which case submission of only the receiving report in WAWF is required.

(e) Information regarding WAWF is available at https://wawf.eb.mil/.

(f) In addition to the requirements of this clause, the Contractor shall meet the requirements of the appropriate payment clauses in this contract when submitting payment requests.

(End of clause) https://wawf.eb.mil/

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (DEC 2018)

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

“Payment request” and “receiving report” are defined in the clause at 252.232-7003, Electronic Submission of

Payment Requests and Receiving Reports.

(b) Electronic invoicing. The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation Supplement (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.sam.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 shall use the following information when submitting payment requests and receiving reports in WAWF for this contract or task or delivery order:

(1) Document type. The Contractor shall submit payment requests using the following document type(s):

(i) For cost-type line items, including labor-hour or time-and-materials, submit a cost voucher.

(ii) For fixed price line items—

(A) That require shipment of a deliverable, submit the invoice and receiving report specified by the Contracting

Officer.

COMBO

(B) For services that do not require shipment of a deliverable, submit either the Invoice 2in1, which meets the requirements for the invoice and receiving report, or the applicable invoice and receiving report, as specified by the

Contracting Officer.

N/A https://www.sam.gov/

(iii) For customary progress payments based on costs incurred, submit a progress payment request.

(iv) For performance based payments, submit a performance based payment request.

(v) For commercial item financing, submit a commercial item financing request.

(2) Fast Pay requests are only permitted when Federal Acquisition Regulation (FAR) 52.213-1 is included in the contract.

[Note: The Contractor may use a WAWF “combo” document type to create some combinations of invoice and receiving report in one step.]

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

Issue By DoDAAC N00421

Admin DoDAAC** N00421

Inspect By DoDAAC N00421

Ship To Code N00421

Ship From Code N/A

Mark For Code N/A

Service Approver (DoDAAC) N00421

Service Acceptor (DoDAAC) N00421

Accept at Other DoDAAC N/A

LPO DoDAAC N/A

DCAA Auditor DoDAAC N/A

Other DoDAAC(s) N/A

(4) Payment request. The Contractor shall ensure a payment request includes documentation appropriate to the type of payment request in accordance with the payment clause, contract financing clause, or Federal Acquisition

Regulation 52.216-7, Allowable Cost and Payment, as applicable.

(5) Receiving report. The Contractor shall ensure a receiving report meets the requirements of DFARS Appendix F.

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

chris.a.robertson@navy.mil

(2) Contact the WAWF helpdesk at 866-618-5988, if assistance is needed.

G-TXT-PAY PAYMENT INSTRUCTIONS (APR 2018)

For Government Use Only

Contract/Order

Payment Clause

Type of

Payment

Request Supply Service Construction

Payment Office

Allocation Method

52.212-4 (Alt I), Contract Terms and

Conditions—

Commercial Items

52.216-7, Allowable

Cost and Payment

52.232-7, Payments under Time-and-

Materials and Labor-

Hour Contracts

Cost Voucher X X N/A Line item specific proration. If there is more than one ACRN within a deliverable line or deliverable subline item, the funds will be allocated in the same proportion as the amount of funding currently unliquidated for each ACRN on the deliverable line or deliverable subline item for which payment is requested.

52.232-1, Payments Navy

Shipbuilding

Invoice (Fixed

Price)

X N/A N/A Line Item specific by fiscal year. If there is more than one

ACRN within a deliverable line or deliverable subline item, the funds will be allocated using the oldest funds. In the event of a deliverable line or deliverable subline item with two ACRNs with the same fiscal year, those amounts will be prorated to the available unliquidated funds for that year.

52.232-1, Payments;

52.232-2, Payments under Fixed-Price

Research and

Development

Contracts;

52.232-3, Payments under Personal

Services Contracts;

52.232-4, Payments under Transportation

Contracts and

Invoice X X N/A Line Item Specific proration. If there is more than one ACRN within a deliverable line or deliverable subline item, the funds will be allocated in the same proportion as the amount of funding currently unliquidated for each ACRN on the deliverable line or deliverable subline item for which payment is requested.

Transportation-Related

Services Contracts; and

52.232-6, Payments under Communication

Service Contracts with

Common Carriers

52.232-5, Payments

Under Fixed-Price

Construction Contracts

Construction

Payment

Invoice

N/A N/A X Line Item specific by fiscal year. If there is more than one

ACRN within a deliverable line or deliverable subline item, the funds will be allocated using the oldest funds. In the event of a deliverable line or deliverable subline item with two ACRNs with the same fiscal year, those amounts will be prorated to the available unliquidated funds for that year.

52.232-16, Progress

Payments

Progress

Payment*

X X N/A Contract-wide proration. Funds shall be allocated in the same proportion as the amount of funding currently unliquidated for each ACRN. Progress

Payments are considered contract level financing, and the

“contract price” shall reflect the fixed price portion of the contract per FAR 32.501-3.

52.232-29, Terms for

Financing of Purchases of Commercial Items;

52.232-30, Installment

Payments for

Commercial Items

Commercial

Item

Financing*

X X N/A Specified in approved payment.

The contracting officer shall specify the amount to be paid and the account(s) to be charged for each payment approval in accordance with FAR

32.207(b)(2) and 32.1007(b)(2).

52.232-32, Performance-Based

Payments

Performance-

Based

Payments*

X X N/A Specified in approved payment.

The contracting officer shall specify the amount to be paid and the account(s) to be charged for each payment approval in accordance with FAR

32.207(b)(2) and 32.1007(b)(2).

252.232-7002, Progress Payments for

Foreign Military Sales

Acquisitions

Progress

Payment*

X X N/A Allocate costs among line items and countries in a manner acceptable to the Administrative

Contracting Officer.

*Liquidation of Financing Payments. Liquidation will be applied by the payment office against those ACRNs which are identified by the payment instructions for the delivery payment and in keeping with the liquidation provision of the applicable contract financing clause (i.e., progress payment, performance-based payment, or commercial item financing).

Section I - Contract Clauses

CLAUSES INCORPORATED BY REFERENCE

52.202-1 Definitions NOV 2013

52.204-7 Alt I System for Award Management-- Alternate I OCT 2018

52.212-4 Contract Terms and Conditions--Commercial Items OCT 2018

52.216-21 Requirements OCT 1995

52.222-50 Combating Trafficking in Persons JAN 2019

52.232-39 Unenforceability of Unauthorized Obligations JUN 2013

252.203-7002 Requirement to Inform Employees of Whistleblower Rights SEP 2013

252.223-7004 Drug Free Work Force SEP 1988

CLAUSES INCORPORATED BY FULL TEXT

52.213-2 INVOICES (APR 1984)

The Contractor’s invoices must be submitted before payment can be made. The Contractor will be paid on the basis of the invoice, which must state (a) the starting and ending dates of subscription delivery, and (b) either that orders have been placed in effect for the addresses required, or that the orders will be placed in effect upon receipt of payment.

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-7012 SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT

REPORTING (DEC 2019)

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.archives.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 is 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--Noncommercial Items, regardless of whether or not the clause is incorporated in this solicitation or contract. Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code.

(b) Adequate security. The Contractor shall provide adequate security on 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:

http://www.archives.gov/cui/registry/category-list.html http://www.archives.gov/cui/registry/category-list.html

(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 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” (available via the internet at http://dx.doi.org/10.6028/NIST.SP.800-171) in effect at the time the solicitation is issued or as authorized by the Contracting Officer.

(ii)(A) The Contractor shall implement NIST SP 800-171, as soon as practical, but not later than December 31, 2017. For all contracts awarded prior to October 1, 2017, the Contractor shall notify the DoD Chief Information

Officer (CIO), via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award.

(B) The Contractor shall submit requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO. The Contractor need not implement any security requirement adjudicated by an authorized representative of the DoD CIO to be nonapplicable or to have an alternative, but equally effective, security measure that may be implemented in its place.

(C) If the DoD CIO has previously adjudicated the contractor's requests indicating that a requirement is not applicable or that an alternative security measure is equally effective, a copy of that approval shall be provided to the Contracting Officer when requesting its recognition under this contract.

(D) If the Contractor intends to use an external cloud service provider to store, process, or transmit any covered defense information in performance of this contract, the Contractor shall require and ensure that the cloud service provider meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline

(https://www.fedramp.gov/resources/documents/) and that the cloud service provider complies with requirements in paragraphs (c) through (g) of this clause for cyber incident reporting, malicious software, media preservation and protection, access to additional information and equipment necessary for forensic analysis, and cyber incident damage assessment.

(3) Apply other information systems security measures when the Contractor reasonably determines that information systems security measures, in addition to those identified in paragraphs (b)(1) and (2) of this clause, may be required to provide adequate security in a dynamic environment or to accommodate special circumstances (e.g., medical devices) and any individual, isolated, or temporary deficiencies based on an assessed risk or vulnerability. These measures may be addressed in a system security plan.

(c) Cyber incident reporting requirement.

(1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor's ability to perform the requirements of the contract that are designated as operationally critical support and identified in the contract, 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 http://dx.doi.org/10.6028/NIST.SP.800-171 mailto:osd.dibcsia@mail.mil https://www.fedramp.gov/resources/documents/ 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 https://dibnet.dod.mil.

(2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at https://dibnet.dod.mil.

(3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the

Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see https://public.cyber.mil/eca/.

(d) Malicious software. When the Contractor or subcontractors discover and isolate malicious software in connection with a reported cyber incident, submit the malicious software to DoD Cyber Crime Center (DC3) in accordance with instructions provided by DC3 or the Contracting Officer. Do not send the malicious software to the

Contracting Officer.

(e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest.

(f) Access to additional information or equipment necessary for forensic analysis. Upon request by DoD, the

Contractor shall provide DoD with access to additional information or equipment that is necessary to conduct a forensic analysis.

(g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the Contracting

Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause.

(h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the

Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released.

(i) Use and release of contractor attributional/proprietary information not created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD--

(1) To entities with missions that may be affected by such information;

(2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents;

(3) To Government entities that conduct counterintelligence or law enforcement investigations;

(4) For national security purposes, including cyber situational awareness and defense purposes (including with

Defense Industrial Base (DIB) participants in the program at 32 CFR part 236); or http://dibnet.dod.mil/ http://dibnet.dod.mil/ https://public.cyber.mil/eca/

(5) To a support services contractor (“recipient”) that is directly supporting Government activities under a contract that includes the clause at 252.204-7009, Limitations on the Use or Disclosure of Third-Party Contractor Reported

Cyber Incident Information.

(j) Use and release of contractor attributional/proprietary information created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph (c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph (i) of this clause, and for any other lawful Government purpose or activity, subject to all applicable statutory, regulatory, and policy based restrictions on the Government's use and release of such information.

(k) The Contractor shall conduct activities under this clause in accordance with applicable laws and regulations on the interception, monitoring, access, use, and disclosure of electronic communications and data.

(l) Other safeguarding or reporting requirements. The safeguarding and cyber incident reporting required by this clause in no way abrogates the Contractor's responsibility for other safeguarding or cyber incident reporting pertaining to its unclassified information systems as required by other applicable clauses of this contract, or as a result of other applicable U.S. Government statutory or regulatory requirements.

(m) Subcontracts. The Contractor shall--

(1) Include this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve covered defense information, including subcontracts for commercial items, without alteration, except to identify the parties. The Contractor shall determine if the information required for subcontractor performance retains its identity as covered defense information and will require protection under this clause, and, if necessary, consult with the Contracting Officer; and

(2) Require subcontractors to--

(i) Notify the prime Contractor (or next higher-tier subcontractor) when submitting a request to vary from a NIST

SP 800-171 security requirement to the Contracting Officer, in accordance with paragraph (b)(2)(ii)(B) of this clause; and

(ii) Provide the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable, when reporting a cyber incident to DoD as required in paragraph (c) of this clause.

252.211-7003 ITEM UNIQUE IDENTIFICATION AND VALUATION (MAR 2016)

“Automatic identification device” means a device, such as a reader or interrogator, used to retrieve data encoded on machine-readable media.

“Concatenated unique item identifier” means--

(1) For items that are serialized within the enterprise identifier, the linking together of the unique identifier data elements in order of the issuing agency code, enterprise identifier, and unique serial number within the enterprise identifier; or

(2) For items that are serialized within the original part, lot, or batch number, the linking together of the unique identifier data elements in order of the issuing agency code; enterprise identifier; original part, lot, or batch number;

and serial number within the original part, lot, or batch number.

“Data matrix” means a two-dimensional matrix symbology, which is made up of square or, in some cases, round modules arranged within a perimeter finder pattern and uses the Error Checking and Correction 200(ECC200) specification found within International Standards Organization (ISO)/ International Electrotechnical Commission

(IEC) 16022.

“Data qualifier” means a specified character (or string of characters) that immediately precedes a data field that defines the general category or intended use of the data that follows.

“DoD recognized unique identification equivalent” means a unique identification method that is in commercial use and has been recognized by DoD. All DoD recognized unique identification equivalents are listed at http://www.acq.osd.mil/dpap/pdi/uid/iuid_equivalents.html.

“DoD item unique identification” means a system of marking items delivered to DoD with unique item identifiers that have machine-readable data elements to distinguish an item from all other like and unlike items. For items that are serialized within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier and a unique serial number. For items that are serialized within the part, lot, or batch number within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier;

the original part, lot, or batch number; and the serial number.

“Enterprise” means the entity (e.g., a manufacturer or vendor) responsible for assigning unique item identifiers to items.

“Enterprise identifier” means a code that is uniquely assigned to an enterprise by an issuing agency.

“Government's unit acquisition cost” means--

(1) For fixed-price type line, subline, or exhibit line items, the unit price identified in the contract at the time of delivery;

(2) For cost-type or undefinitized line, subline, or exhibit line items, the Contractor’s estimated fully burdened unit cost to the Government at the time of delivery; and

(3) For items produced under a time-and-materials contract, the Contractor’s estimated fully burdened unit cost to the Government at the time of delivery.

“Issuing agency” means an organization responsible for assigning a globally unique identifier to an enterprise, as indicated in the Register of Issuing Agency Codes for ISO/IEC 15459, located at http://www.aimglobal.org/?Reg_Authority15459.

“Issuing agency code” means a code that designates the registration (or controlling) authority for the enterprise identifier.

“Item” means a single hardware article or a single unit formed by a grouping of subassemblies, components, or constituent parts.

“Lot or batch number” means an identifying number assigned by the enterprise to a designated group of items, usually referred to as either a lot or a batch, all of which were manufactured under identical conditions.

“Machine-readable” means an automatic identification technology media, such as bar codes, contact memory buttons, radio frequency identification, or optical memory cards.

“Original part number” means a combination of numbers or letters assigned by the enterprise at item creation to a class of items with the same form, fit, function, and interface.

“Parent item” means the item assembly, intermediate component, or subassembly that has an embedded item with a unique item identifier or DoD recognized unique identification equivalent.

“Serial number within the enterprise identifier” means a combination of numbers, letters, or symbols assigned by the enterprise to an item that provides for the differentiation of that item from any other like and unlike item and is never used again within the enterprise.

“Serial number within the part, lot, or batch number” means a combination of numbers or letters assigned by the enterprise to an item that provides for the differentiation of that item from any other like item within a part, lot, or batch number assignment.

“Serialization within the enterprise identifier” means each item produced is assigned a serial number that is unique among all the tangible items produced by the enterprise and is never used again. The enterprise is responsible for ensuring unique serialization within the enterprise identifier.

“Serialization within the part, lot, or batch number” means each item of a particular part, lot, or batch number is assigned a unique serial number within that part, lot, or batch number assignment. The enterprise is responsible for ensuring unique serialization within the part, lot, or batch number within the enterprise identifier.

“Type designation” means a combination of letters and numerals assigned by the Government to a major end item, assembly or subassembly, as appropriate, to provide a convenient means of differentiating between items having the same basic name and to indicate modifications and changes thereto.

“Unique item identifier” means a set of data elements marked on items that is globally unique and unambiguous.

The term includes a concatenated unique item identifier or a DoD recognized unique identification equivalent.

“Unique item identifier type” means a designator to indicate which method of uniquely identifying a part has been used. The current list of accepted unique item identifier types is maintained at http://www.acq.osd.mil/dpap/pdi/uid/uii_types.html.

(b) The Contractor shall deliver all items under a contract line, subline, or exhibit line item.

(c) Unique item identifier.

(1) The Contractor shall provide a unique item identifier for the following:

(i) Delivered items for which the Government's unit acquisition cost is $5,000 or more, except for the following line items:

Contract Line, Subline, or Exhibit Line Item Number Item Description

_________________________________N/A____________________________________________

(ii) Items for which the Government's unit acquisition cost is less than $5,000 that are identified in the

Schedule or the following table:

Contract Line, Subline, or Exhibit Line Item Number Item Description

__________________________________N/A_____________________________________________

(If items as identified in the Schedule, insert "See Schedule" in this table.)

(iii) Subassemblies, components, and parts embedded within delivered items, items with warranty requirements, DoD serially managed reparables and DoD serially managed nonreparables as specified in Attachment

Number __N/A____.

(iv) Any item of special tooling or special test equipment as defined in FAR 2.101 that have been designated for preservation and storage for a Major Defense Acquisition Program as specified in Attachment Number ______.

(v)…