23-R-0004 MSFTB AMD 1.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

See page 2.

1. CONTRACT ID CODE PAGE OF PAGES

U 1 19

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 30-Apr-2023

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W911W623R0004

X 9B. DATED (SEE ITEM 11)

24-Mar-2023

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

30-Apr-2023

CODE

ARMY CONTRACTING COMMAND (ACC)

REDSTONE/CCAM-MZD-B

BLDG 401 LEE BLVD

FORT EUSTIS VA 23604-5577

W911W6 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W911W623R0004

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

BLOCK 14 CONT.

1. The above numbered solicitation is hereby amended to make required changes. Those changes which are not readily apparent on subsequent pages of this amendment are described below:

a. Questions and Answers dated April 27, 2023, are hereby incorporated by reference. Please note: there are a few questions currently without a response; a subsequent amendment to the solicitation is forthcoming to provide a complete set of answers.

b. Section C, Statement of Work, paragraph 3, Requirements is modified to delete the following: ‘Task order

1 requirements are contained in Attachment 1.’

c. Section H, Special Contract Requirements has been modified to add clause H-4, Organizational Conflicts of Interest.

d. Section H, Special Contract Requirements, H-1 Task Order Procedures, is revised to reflect the basis for award of any Task Orders after Task Order 1 and paragraph l is modified.

e. Section I, clauses which are inapplicable to this requirement have been removed. All ‘added’ clauses are clauses that reflect the most current version and have been added to replace the outdated versions.

f. Section J, Exhibits/Attachments has been revised to replace Contract Data Requirements List (CDRLs)

Exhibits A-K. Changes to the CDRLs include:

A001 – Work Plan

Minor correction to DID nomenclature version change (section 10.2.7 changed to 3.9)

Distribution Statement C removed due to non-technical data

A002 – Technical Status Report

Block 11 corrected to reflect 15th of the month (versus 5th)

Export Control Warning Added

A003 – Cost Status Report

Block 11 corrected to reflect 15th of the month (versus 5th)

A004 – Test Plan

A005 – Test Report

A006 – System Integration Guide

Block 13 corrected to 60DAC (versus 30DAC)

A007 – GFI Utilization Report

A008 – MSUT Integration Model

A009 – Final Report

Removed note from Block 16 allowing for inclusion of proprietary markings

A010 – Briefing Materials

g. The Call has been modified to make minor revisions; the document with changes annotated is provided with this amendment. Changes include changing reference to Annex A to GFI Table in Section 8 and deleting item 10 from Proposal Instructions paragraph 3.1.

2. Note page 2 of this amendment which states the revised proposal due date and time. All other terms and provisions remain unchanged.

3. This amendment consists of the following documents: Amendment 0001; Revised Call; Questions and Answers;

and revised CDRLs.

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 08-May-2023 02:00 PM to 19-May-2023 02:00 PM.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0002

The CLIN description has changed from Travel (Direct and Indirect) to Travel.

The CLIN extended description has changed from:

The Contractor shall be reimbursed for travel at actual cost in accordance with FAR 31.205-46, this includes applicable indirect costs consistent withContractor’s approved accounting procedures.

To:

The Contractor shall be reimbursed for travel based upon actual cost incurred to include indirect costs applicable to direct travel costs and which are consistent with Contractor’s approved accounting procedures. Costs will be reimbursed in accordance with FAR 31.205-46.

The following have been modified:

AVAILABLE AND ALLOTTED FUNDS

Task Orders issued under this contract may be incrementally funded pursuant to the clause Limitation of Funds, FAR 52.232-22. When this applies, the following is applicable:

a. The amount presently available for payment and allotted to each order will be cited on individual Task

Orders.

b. Each order that is incrementally funded will contain the following: "It is estimated that the amount presently available for payment and allotted to the contract will fund performance through approximately (to be cited on individual Task Orders)."

c. The Government's liability under any order is limited to the funds actually obligated under that Order.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

1. Introduction

This Statement of Work for Mission Systems Flying Test Bed (MSFTB) defines the required Mission System

Integrator (MSI) tasks of: integrating a Mission System Under Test (MSUT) into the MSFTB, integrating the

MSFTB and MSUT into the target Air Vehicle (AV) platform, and verifying and demonstrating system operation.

Integration tasks include procurement of any hardware and software required for integration of the MSUT, fabrication of hardware integration items required, integration of the MSUT, demonstration, and test.

1.1 General Overview

The purpose of the Integrated Mission Equipment for Vertical Lift Systems (IME) Project is to apply innovative techniques to overcome Army aviation Mission Systems integration challenges caused by the rapid increase of system complexity and the pace of change necessary to keep ahead of emerging threats. These innovative techniques will utilize Air Vehicle Digital Backbones, Automated Software Integration techniques, and Mission

System Software Infrastructure developed specifically to overcome these challenges.

IME project’s goal is to enable rapid integration of flight capable technology in a sustainable manner over the life cycle of a platform, system or component. IME is a 6.3 Science & Technology (S&T) program managed by the

Combat Capabilities Development Command Aviation and Missile Center (DEVCOM AvMC) Technology

Development Directorate (TDD) that builds on the results of the Joint Multi-Role Technology Demonstrator (JMR

TD) Mission Systems Architecture Demonstration (MSAD) program and informs the Future Attack Reconnaissance

Aircraft (FARA), Future Long-Range Assault Aircraft (FLRAA), and other Future Vertical Lift systems.

1.2 Mission Systems Flying Test Bed (MSFTB) Overview

The MSFTB will be an enduring experimentation and test & evaluation asset used to integrate, demonstrate and mature next generation mission systems. The MSFTB is the culmination of efforts and products from other IME activities brought together to form a solution capable of enabling rapid evaluation of innovative technologies and efficient integration approaches, while reducing system evaluation costs.

The MSFTB will be a flight test capability that can be installed into multiple Air Vehicles (AV) to evaluate integration of various MSUTs. The MSFTB and MSUTs will be installed into an AV through the digital backbone and integrated utilizing government provided core software infrastructure capabilities. The MSFTB will conduct ground and flight demonstrations to evaluate the integration of MSUTs and impacts to changes of the MSUTs or the computing environment on the characteristics of integration. The MSFTB will exercise representative airworthiness, cybersecurity, and model based systems engineering processes to include virtual integration and analysis. The IME developed Architecture Verification Environment (AVE) and MSFTB fill a gap in traditional System Integration

Labs by enabling evaluation of MSUTs against their Modular Open Systems Architecture (MOSA) objectives. The

AVE independently validates and verifies a MSUT against its architecture requirements while the MSFTB evaluates its ability to be integrated and demonstrated in a representative environment. Figure 1 depicts a concept of operation for the various MSFTB elements, roles and activities.

Figure 2 below depicts conceptual use of the MSFTB in an experimental UH-60M. IME will upgrade the UH-60M or potentially other available AVs to include a DB with nodal points for installing MSUTs to support multiple S&T projects.

Overall, the MSFTB will be a hardware and software system that will be used to demonstrate and evaluate the integration and operation of MSUTs in ground and flight evaluations and will help mature and evaluate innovative approaches for integration of mission systems technologies acquired under MSAD and IME.

The MSFTB concept outlined in the following subsections provides a more detailed explanation of needs and system level capabilities included in the enduring experimentation and test & evaluation asset. In summary:

• The MSFTB will be a capability for the Government to assess the ability to independently integrate and evaluate

MSUTs.

• The MSFTB will be composed of a set of test equipment installed in a test rack that interfaces the MSUT to the AV.

• The MSFTB will provide all the capabilities necessary for test scenario simulation, generation of data for MSUT not provided by AV, operation of MSUT, and instrumentation for data collection.

• An experimental Flight Test UH-60M is the first target AV with Nodal Points to support installation of the MSFTB and MSUT(s).

• The AV DB provides the power, thermal and data distribution management functions for the MSFTB and MSUT(s).

• The Government will separately acquire various MSUT(s) that will be independently integrated by one or more MSIs into the MSFTB.

• MSI(s) will follow the integration approach for hardware and software using the principles and approaches described by Digital Backbone, Core Capabilities, and virtual integration.

• MSI(s) will use the IME Core Capabilities (CC) infrastructure software products that provide the infrastructure for data exchange, application management, systems management, persistent data management, time server, and event logging.

• MSI(s) will integrate MSUTs and configure MSFTB emulators, stimulators, and data collection.

• Excursions will occur by modifying the MSUTs or MSFTB to evaluate integration impacts.

1.2.1 Core Capabilities Overview

Core Capabilities will provide a suite of reusable software products that can be used by the MSI to integrate MSUTs.

The Core Capability products will align to the Future Airborne Capability Environment (FACETM) Technical

Standard, Edition 3.0, and the IME airworthiness and cybersecurity approaches.

CC Infrastructure software products will be available for MSUT integration for the purpose of experiments and excursions. This infrastructure will be provided as GFI/GFE and will be made available to MS Providers and MSIs at various phases of execution. MS Providers may choose to incorporate Infrastructure elements into their MS instantiations. The MSIs may use infrastructure software as a tool for innovative integration. The Government may direct use of infrastructure software in specific integration scenarios to investigate how a MSUT uses mechanisms to achieve architecture quality attributes.

Table 2 contains description of CC Infrastructure software products. The architecture, performance, and interface specifications will be provided as GFI at contract award. Infrastructure software will be provided prior to the appropriate integration milestone.

Infrastructure GFI/GFE will include artifacts supporting partial qualification of reusable software components for airworthiness and cyber survivability guidance begun under MSAD that are being updated for IME. Final versions will be provided along with infrastructure software deliverables, with draft versions provided at earlier milestones as they mature.

The FACE Technical Standard, Edition 3.0, provides a framework for the underlying architecture. Table 1 below describes capabilities and additional detail as contained at Annex A.

Table 2: Core Capability Infrastructure Software Product Descriptions

Capability Description

Data

Exchange

Responsible for providing a connection between software components and independently managing data priorities and Quality of Service parameters.

Application

Management

It is also responsible for managing application state and mode transitions. In the context of

CC, a state change represents a condition change. An example would be the application or removal of power. A mode change represents a behavioral change. An example would be performing an initialization sequence or transitioning to Fault when a portion of the application is no longer performing correctly.

System

Management

Provides the capability to monitor and manage the startup, operation, and system state. It may respond to events that have been raised by other services. It provides recovery mechanisms for applications that have experienced a fault. System Management uses the data provided at the application level to monitor overall system health which includes managing faults at the system level.

Persistent

Data

Management

Responsible for providing high-speed data recording. Data types include: flight data, mission logs, mission data, raw experiment data, and post-processed experiment data. It is also responsible for precluding data overwrite and supporting queries made by a MS or an AVS.

Time Server Responsible for providing time data elements of appropriate accuracy. If Time Sync is in a

GPS denied environment, it will be able to maintain time with appropriate accuracy for a limited period of time.

Event

Logging

The capability to log application events, raise application faults, and notify interested parties of the events and faults that occur.

1.2.2 Digital Backbone Overview

The Digital Backbone (DB) concept is an architectural mechanism that expedites integration by provisioning for power, data, thermal management, and structural needs; and reduces qualification and certification timelines by separating AV and MS. Implementation of DB is an Air Vehicle subsystem. The DB whitepaper describes the overall concepts and scope.

2 Scope of Work

The primary task of the MSIs is the integration of MSUTs using the provided MSFTB hardware and software. MSIs will conduct end-to-end system checkout, such as establishing and verifying communications paths and information flow, establishing data storage routines and protocols, and verifying MS simulation and stimulation provides expected outcomes. The MSI will support airworthiness, cybersecurity, and virtual integration processes that support partial airworthiness certification for future Mission Systems airworthiness certification. Reviews are anticipated to begin with virtual integration and analysis, progressing through final demonstrations.

Integration scenarios:

• MSUT hardware installed at a Nodal Point of the DB which provides power, thermal, structural, and a Point of

Presence (PoP) to connect the MSUT to the MSFTB.

• MSUT software installed in the MSFTB general-purpose processor virtual machine.

Figure 3: Anticipated MSI Timeline

2.1 Mission System Integrator (MSI) Overview

The primary duties of an MSI are:

• Prepare for integration with the MSFTB

• Integrate MSUT(s) with the MSFTB

• Support installation of the MSFTB with integrated MSUT into the target AV platform

• Verify system operation

The MSIs are responsible for identifying and addressing gaps in both GFI and required materials for integration of the MSUTs into the MSFTB.

The MSIs will demonstrate MSUT integration, verify MSFTB operation, and support demonstration of the configuration.

3 Requirements

The contractor, as an independent contractor and not as an agent of the Government, shall perform all activities required to establish system requirements, integrate, test and demonstrate MSUTs per the scenarios described above.

The contractor shall provide the program management, personnel, engineering, test equipment, and operational and logistical support necessary for the performance of this effort.

3.1 Required Reporting and Deliverables

All Contractors shall participate in a kickoff meeting following award. Unless otherwise stated within each Task

Order, the following data items/deliverables will be required in accordance with the attached Contract Data

Requirements Lists (CDRL).

CDRL Title DID Due date

A001 Contractor Work Plan DI-MGMT-81117A Initial at KOM; update 15 days after

A002 Technical Status

Report

DI-MGMT-81928 15th day of each month

A003 Cost Report DI-FNCL-80912 15th day of each month

A004 Test Plan DI-NDTI-80566A 30 days prior to TRR

A005 Test Report DI-NDTI-80809 30 days after Test

A006 System Integration

Guide (SIG)

DI-SESS-82044 Initial 120 days following CA; final 180 days following CA

A007 GFI Utilization Report DI-MISC-80508B Initial at completion of TO#1; updates at completion of TO#2 and TO#3

A008 Virtual Integration

Cameo Model

DI-SESS-82304 Initial GFI model analysis at completion of TO#1; updated integration model at completion of TO#2 and any subsequent

TOs

A009 Final Report DI-MISC-80711A At completion of TO#2 or TO#3, as selected by the Government

A010 Briefing and presentation materials

DI-MGMT-81605 As required

A011 Small Business

Utilization Report

DI-MGMT-82041A QTRLY

4 Operational Security (OPSEC) Requirements

4.1.1 Antiterrorism (AT) Level 1 Training

All contractor employees, to include subcontractor employees, requiring access to government installations, facilities and controlled access areas shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable.

The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer, within 30 calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website:

https://jkodirect.jten.mil.

4.1.2 AT Awareness Training for Contractor Personnel Traveling Overseas

All United States (US) based contractor employees and associated sub-contractor employees shall make available and receive government provided Area of Responsibility (AOR) specific AT awareness training as directed by Army

Regulation (AR) 525-13. Specific AOR training content is directed by the combatant commander with the unit

Antiterrorism Officer (ATO) being the local point of contact.

4.1.3 iWATCH Training

The contractor and all associated subcontractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR no later than 30 calendar days after contract award.

4.1.4 Threat Awareness Reporting Program Training (TARP)

For all DoD contractors with security clearances. Per AR 381-12 TARP, contractor employees must receive annual

TARP training presented by a Counterintelligence Special Agent. Contact the Redstone Arsenal Military

Intelligence Detachment at 256-313-5186 for scheduling.

4.1.5 Identification of Contractor Employees

The Contractor, including subcontractors, shall provide each employee an Identification (ID) Badge, which includes at a minimum, the Company Name, Employee Name and a color photo of the employee. ID Badges for Key

Personnel shall also indicate their job title. ID Badges shall be worn at all times during which the employee is performing work under this contract. Each Contractor, including subcontractors, employees shall wear the ID

Badge in a conspicuous place on the front of exterior clothing and above the waist except when safety or health reasons prohibit. The Contractor, including subcontractors, shall be responsible for collection of ID Badges upon completion of the contract or termination of employee. A listing of issued identification cards shall be furnished to the Contracting Officer prior to the contract performance date and updated as needed to reflect Contractor and

Subcontractor personnel changes. Foreign owned companies and foreign national contractors will only be permitted to perform under this contract when there are no qualified US companies and /or US contractors. All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They shall also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

4.1.6 OPSEC Training

Level I OPSEC Awareness Training: Per AR 530-1, Operations Security, all contractor employees, including subcontractor employees, shall complete Level I OPSEC Awareness Training within 30 calendar days of their reporting for duty. All subcontractors shall take the Level 1 OPSEC Awareness Training located at the below website and print the certificates demonstrating completion. The contractor shall maintain current certificates of completion for each affected contractor employee and provide to the Contracting Officer upon request. OPSEC awareness training is available at the following website: https://securityawareness.usalearning.gov/

5 Government Furnished Data / Equipment / Information

To be specified within each Task Order.

SECTION G - CONTRACT ADMINISTRATION DATA

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (JAN 2023)

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

https://www.sam.gov/ https://wawf.eb.mil/ 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.

(Contracting Officer: Insert applicable invoice and receiving report document type(s) for fixed price line items that require shipment of a deliverable.)

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

(Contracting Officer: Insert either “Invoice 2in1” or the applicable invoice and receiving report document type(s) for fixed price line items for services.)

(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 financing, submit a commercial 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 ____

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. If multiple ship to/acceptance locations apply, insert

“See Schedule” or “Not applicable.”)

(**Contracting Officer: If the contract provides for progress payments or performance-based payments, insert the

DoDAAC for the contract administration office assigned the functions under FAR 42.302(a)(13).)

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

(Contracting Officer: Insert applicable information or “Not applicable.”)

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

(End of clause)

The following have been deleted:

252.232-7006 Wide Area WorkFlow Payment Instructions DEC 2018

SECTION H - SPECIAL CONTRACT REQUIREMENTS

H-1 TASK ORDER PROCEDURES

H-1 TASK ORDER PROCEDURES

a. The contractor shall incur costs under this contract only in the performance of Task Orders and modifications to

Task Orders issued by the Contracting Officer in accordance with this procedure. No other costs are authorized without the express written consent of the Contracting Officer.

b. The Government will issue requests for task order proposal (RFTOP) based upon a the Government’s review of the Contractor’s technical progress and available funding. The Government’s selection process is an extension of Broad Agency Announcement (BAA) W911W6-21-R-0013 and W911W6-23-R-0004 that led to this

Contract award. As stated in W911W6-21-R-0013, Section 3.6, the Government issuance of RFTOPs for continued development are considered in the scope of this Contract and meets the requirements of the

Competition in Contracting Act.

c. Task Orders will be issued by the Contracting Officer to the contractor incorporating (i) the task to be performed to include deliverables; (ii) the required task dates or overall period of performance; and, (iii) any

Government-furnished property/data.

d. Task Orders will be issued on a Cost-Plus-Fixed-Fee and Cost Price basis with a specified period of performance on a DD Form 1155 Order for Supplies or Services which shall incorporate the Task Statement of

Work (SOW) provided by the Government. A revision to a Task Order will be issued on a Standard Form 30

Amendment of Solicitation/ Modification of Contract and may incorporate revisions to Task SOWs that will clearly indicate the revisions.

e. In accordance with FAR 16.504 Indefinite Quantity Contracts, the stated minimum guarantee dollar value for this contract will be set forth on the 1st individual task order issued under this contract.

f. No protest under FAR Subpart 33.1 is authorized in connection with the issuance or proposed issuance of a

Task Order, except on the grounds that the order increases the scope or maximum value of the contract in total

(not necessarily each contract period).

g. The contractor shall submit to the Contracting Officer a Task Proposal within thirty (30) calendar days after receiving a draft of the task SOW and written notification from the Contracting Officer that a Task Proposal is required. The Task Proposal shall provide the contractor’s detailed approach to accomplishing the requirements of the task and will identify the contractor’s overall estimate for completing the task.

h. The contractor shall initiate task performance promptly upon receipt of a fully executed Task Order that has been signed by the Contracting Officer. The signed Task Order will incorporate all items agreed upon during cost proposal discussions.

i. The Government’s anticipates each task order will be incrementally funded when issued; however when possible the Government will fully fund each task order when issued.

j. The “Limitations of Funds” clause contained in Section I herein will be applicable to all funding actions

(whether or not they are incremental or full funding type actions).

k. This ordering procedure is of a lesser order of precedence than the “Limitation of Funds” clauses of the contract. The contractor is not authorized to incur costs on task orders which are not in compliance with this clause.

l. Where the parties are unable to agree upon terms (including estimated cost and fixed fee) specific to a particular task order, the parties agree that the Contracting Officer may issue a unilateral undefinitized task order. The

Contractor shall immediately begin performance upon issuance of the Task Order but may appeal the definitization through the Disputes clause, starting with a request to the Contracting Officer. Where an

Organizational Conflict of Interest may result from issuance of a Task Order under this paragraph (l), the procedures outlined in H-4 shall take precedence over the Government’s right to issue a unilateral order as described in this paragraph (l).

H-2 ACCESS TO INSTALLATION

H.2 ACCESS TO GOVERNMENT INSTALLATION/EQUIPMENT

a. Access to Government facilities:

As required by Section 4, Statement of Work, the Contractor will have access to Joint Base Langley Eustis (IBLE) as well as to the facilities at the Technology Development Directorate Aviation Systems and Integation and

Demonstration (TDD-A SID), Fort Eustis, Virginia, to provide on-site support in performance of this effort

b. Accountability for government equipment:

For accountability and responsibility purposes for Government property that the contractor is provided access to for work under this contract (e.g. information technology resources or test equipment), the contractor shall receipt for all

Government equipment from the Property Book Officer or hand receipt holder and manage such property in a manner consistent with FAR Part 45. The property is not government furnished property subject to the requirements of FAR 52.245-1. The contractor is the Primary Hand Receipt Holder for the equipment used by the contractor and for that equipment determined by the COR. The contractor and Government representatives shall conduct a joint inventory of all Government equipment the contractor is given access. The contractor and Government representatives shall jointly determine the working order and condition of all equipment. Items of equipment missing or not in working order shall be recorded. The Government shall replace missing items and repair all items not in working order. Through the COR, the Government representative shall give disposition instructions for items beyond repair or obsolete. If the contractor does not participate in the inventory, the contractor shall accept as accurate the listing and stated condition of equipment provided by the Government. If the contractor participates in the inventory and does not agree with the Government representative's determination as to the working order of the equipment, the failure to agree shall be treated as a dispute pursuant to the clause of this contract entitled, "Disputes.

c. Risk of Loss, Damage, Destruction, or Theft (LDDT). In accordance with DFARS 45.104, Responsibility and

Liability for Government Property. [Deviation] [DARS Tracking Number 2010-00003, dated 12 Feb 2010 http://www.acq.osd.mil/dpap/policy/policyvault/USA000633-10-DPAP.pdt], the Government retains risk of

LDDT.

H-3 SB SUBCONTRACTING

H-3 SMALL BUSINESS SUBCONTRACTING

In accordance with DI-MGMT-82041A, contractor shall submit a list of small business suppliers and/or service providers (subcontractors) and shall include how they will utilize those suppliers and/or service providers in performing this work effort. The list of small business suppliers and/or service providers will become part of the resultant contract. Contractor shall submit to the Procuring Contracting Officer (PCO) a report that documents (at least quarterly) how they are adhering to or exceeding their proposed utilization of small business suppliers and/or service providers. The PCO will use this report in determining an overall CPARS rating, if applicable, for subcontracting management. Contractor shall coordinate with the PCO if small business firms identified in the list are substituted or not utilized over the quarter. The PCO must agree with the substitution prior to replacements performing on this contract.

Small Business Subcontracting Plan – applicable to contractors required to submit a SB Subcontracting Plan only.

Contractor shall make a good faith effort to find opportunities for small business suppliers and service providers in the performance of this work effort. The Contractor should contact the local Procurement Technical Assistance

Center (PTAC), the local Office of Small Business Programs, and utilize the Small Business Dynamic Search

Website to assist in finding small business suppliers and services providers that are capable of performing the subcontracted work. For large business firms with an approved Comprehensive Subcontracting Plan (through

December 2027), FAR Part 52.219-16, Liquated Damages, will not be part of the resultant contract nor are you required to report in eSRS/iSRS; however not adhering to and/or utilizing your proposed list of suppliers and/or service providers may result in a negative CPARS rating.

Small Business Opportunities. Contractor shall support small business opportunities throughout the period of performance. Contractor shall make a good faith effort in identifying opportunities for small business suppliers and service providers including all socio-economic small business categories. The list of subcontractors shall be submitted with the proposal and revisions to the list can be made throughout the contract performance.

H-4 ORG CONFLICT OF INTEREST

H-4 ORGANIZATIONAL CONFLICT OF INTEREST (OCI)

a. Due to the nature of this contract, OCI implications will be reviewed on an individual Order basis, prior to the issuance of each Order. Each situation will be examined on the basis of its particular facts and the nature of the proposed support/ services/deliverables. The exercise of common sense, good judgment and sound discretion will be employed in determining whether a significant potential conflict exists and, if it does, the development of an appropriate means for resolving it. The two underlying principles are-

- preventing the existence of conflicting roles that might bias a contractor’s judgment

- preventing an unfair competitive advantage

b. Prospective offerors are invited to review Federal Acquisition Regulation Subpart 9.5 “Organizational and

Consultant Conflicts of Interest.” Particular attention is directed to FAR 9.505, 9.505-1, 9.505-2, 9.505-3 and 9.505-

4.

c. Contractor and subcontractor personnel performing work under any Task Order issued under the terms of this contract may perform services which may create a current or subsequent OCI as defined in FAR 9.5. The contractor shall notify the Contracting Officer and COR immediately whenever it becomes aware that access or participation may result in any actual or potential OCI, and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The contractor’s mitigation plan shall be reviewed by the Contracting Officer to determine acceptability. In the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided/mitigated, the Contracting Officer may affect other remedies as deemed necessary.

SPECIAL CONTRACT REQUIREMENT

SECTION I - CONTRACT CLAUSES

The following have been added by reference:

52.215-21 Requirements for Certified Cost or Pricing Data and Data

Other Than Certified Cost or Pricing Data -- Modifications

NOV 2021

52.219-8 Utilization of Small Business Concerns OCT 2022

52.219-9 Small Business Subcontracting Plan OCT 2022

52.219-28 Post-Award Small Business Program Rerepresentation MAR 2023

52.232-40 Providing Accelerated Payments to Small Business

Subcontractors

MAR 2023

52.242-3 Penalties for Unallowable Costs DEC 2022

52.244-6 Subcontracts for Commercial Products and Commercial

Services

MAR 2023

252.203-7001 Prohibition On Persons Convicted of Fraud or Other Defense-

Contract-Related Felonies

JAN 2023

252.203-7002 Requirement to Inform Employees of Whistleblower Rights DEC 2022

252.203-7004 Display of Hotline Posters JAN 2023

252.204-7012 Safeguarding Covered Defense Information and Cyber

Incident Reporting

JAN 2023

252.204-7018 Prohibition on the Acquisition of Covered Defense

Telecommunications Equipment or Services

JAN 2023

252.204-7020 NIST SP 800-171 DoD Assessment Requirements JAN 2023

252.225-7001 Buy American And Balance Of Payments Program--Basic JAN 2023

252.227-7013 Rights in Technical Data--Other Than Commercial Products and Commercial Services

JAN 2023

252.227-7014 Rights in Other Than Commercial Computer Software and

Other Than Commercial Computer Software Documentation

JAN 2023

252.227-7016 Rights in Bid or Proposal Information JAN 2023

252.227-7019 Validation of Asserted Restrictions--Computer Software JAN 2023

252.227-7037 Validation of Restrictive Markings on Technical Data JAN 2023

252.243-7002 Requests for Equitable Adjustment DEC 2022

252.244-7000 Subcontracts for Commercial Products or Commercial

Services

JAN 2023

252.247-7023 Transportation of Supplies by Sea JAN 2023

52.203-16 Preventing Personal Conflicts of Interest JUN 2020

52.215-13 Subcontractor Certified Cost or Pricing Data--Modifications JUN 2020

52.215-21 Alt I Requirements for Certified Cost or Pricing Data and Data

Other Than Certified Cost or Pricing Data -- Modifications

(NOV 2021) - Alternate I

OCT 2010

52.217-8 Option To Extend Services NOV 1999

52.219-8 Utilization of Small Business Concerns OCT 2018

52.219-9 Small Business Subcontracting Plan NOV 2021

52.219-28 Post-Award Small Business Program Rerepresentation SEP 2021

52.223-11 Ozone-Depleting Substances and High Global Warming

Potential Hydrofluorocarbons.

JUN 2016

52.223-20 Aerosols JUN 2016

52.224-3 Privacy Training JAN 2017

52.227-5 Waiver of Indemnity APR 1984

52.229-3 Federal, State And Local Taxes FEB 2013

52.229-12 Tax on Certain Foreign Procurements FEB 2021

52.232-1 Payments APR 1984

52.232-34 Payment By Electronic Funds Transfer--Other Than System for Award Management

JUL 2013

52.232-40 Providing Accelerated Payments to Small Business

Subcontractors

NOV 2021

52.242-3 Penalties for Unallowable Costs SEP 2021

52.244-6 Subcontracts for Commercial Products and Commercial

Services

JAN 2022

52.249-8 Default (Fixed-Price Supply & Service) APR 1984

252.203-7001 Prohibition On Persons Convicted of Fraud or Other Defense-

Contract-Related Felonies

DEC 2008

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

252.203-7004 Display of Hotline Posters AUG 2019

252.204-7012 Safeguarding Covered Defense Information and Cyber

Incident Reporting

DEC 2019

252.204-7018 Prohibition on the Acquisition of Covered Defense

Telecommunications Equipment or Services

JAN 2021

252.211-7003 Item Unique Identification and Valuation MAR 2022

252.215-7003 Requirement for Submission of Data Other Than Certified

Cost or Pricing Data--Canadian Commercial Corporation.

JUL 2012

252.225-7001 Buy American And Balance Of Payments Program-- Basic JUN 2022

252.225-7004 Report of Intended Performance Outside the United States and Canada--Submission after Award

OCT 2020

252.225-7013 Duty-Free Entry--Basic MAR 2022

252.225-7016 Restriction On Acquisition Of Ball and Roller Bearings JUN 2011

252.226-7001 Utilization of Indian Organizations and Indian-Owned

Economic Enterprises, and Native Hawaiian Small Business

Concerns

APR 2019

252.227-7013 Rights in Technical Data--Noncommercial Items FEB 2014

252.227-7014 Rights in Noncommercial Computer Software and

Noncommercial Computer Software Documentation

FEB 2014

252.227-7016 Rights in Bid or Proposal Information JAN 2011

252.227-7019 Validation of Asserted Restrictions--Computer Software SEP 2016

252.227-7037 Validation of Restrictive Markings on Technical Data APR 2022

252.228-7001 Ground And Flight Risk JUN 2010

252.228-7005 Mishap Reporting And Investigation Involving Aircraft, Missiles, And Space Launch Vehicles

NOV 2019

252.233-7001 Choice of Law (Overseas) JUN 1997

252.239-7001 Information Assurance Contractor Training and Certification JAN 2008

252.243-7001 Pricing Of Contract Modifications DEC 1991

252.243-7002 Requests for Equitable Adjustment DEC 2012

252.244-7000 Subcontracts for Commercial Items JAN 2021

252.247-7023 Transportation of Supplies by Sea FEB 2019

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The Table of Contents has changed from:

Exhibit/Attachment Table of Contents

DOCUMENT TYPE DESCRIPTION PAGES DATE

Exhibit A A001- WORK PLAN 16-NOV-2021

Exhibit B A002- TECHNICAL

STATUS PLAN

16-NOV-2021

Exhibit C A003- COST STATUS

REPORT

29-NOV-2021

Exhibit D A004- TEST PLAN 29-NOV-2021

Exhibit E A005- SYSTEM

INTEGRATION TEST

REPORT

29-NOV-2021

Exhibit F A006- SYSTEM

INTEGRATION GUIDE

29-NOV-2021

Exhibit G A007- GFI

UTILIZATION REPORT

29-NOV-2021

Exhibit H A008- MSUT

INTEGRATION MODEL

29-NOV-2021

Exhibit J A009- FINAL REPORT 29-NOV-2021

Exhibit K A0010- BRIEFING

MATERIALS

29-NOV-2021

Exhibit L CDRL-SMALL

BUSINESS

UTILIZATION REPORT

19-JAN-2023

to:

Exhibit/Attachment Table of Contents

DOCUMENT TYPE DESCRIPTION PAGES DATE

Exhibit A A001- WORK PLAN

UPDATE

20-APR-2023

Exhibit B A002- TECHNICAL

STATUS REPORT

UPDATE

20-APR-2023

Exhibit C A003-COST STATUS

REPORT UPDATE

20-APR-2023

Exhibit D A004- TEST PLAN

UPDATE

20-APR-2023

Exhibit E A005- TEST REPORT

UPDATE

20-APR-2023

Exhibit F A006- SYSTEM

INTEGRATION GUIDE

20-APR-2023

Exhibit G A007- GFI

UTILIZATION REPORT

20-APR-2023

Exhibit H A008-MSUT

INTEGRATION MODEL

UPDATE

20-APR-2020

Exhibit J A009- FINAL REPORT

UPDATE

20-APR-2023

Exhibit K A010- BRIEFING

MATERIALS UPDATE

20-APR-2023

Exhibit L CDRL-SMALL

BUSINESS

UTILIZATION REPORT

19-JAN-2023

(End of Summary of Changes)