23R0020 Solicitation.docx

N6893623R0020

Section A - Solicitation/Contract Form

CLAUSES INCORPORATED BY FULL TEXT

FOR YOUR INFORMATION:

The following addresses and points of contact are provided:

Note: This Request for Proposal (RFP) is being issued on an other than full and open competition basis, in accordance with the authority of 10 U.S.C. 3204(a)(1) Only one responsible source and no other supplies or services will satisfy agency requirements.

Section B - Supplies or Services and Prices

Engineering Services for Fibre Channel

CPFF

The contractor shall provide Labor in accordance with (IAW) Section C Statement of Work (SOW).

FOB: Destination

PURCHASE REQUEST NUMBER: 1301063750

PSC CD: 3670

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

V1151 XMC FPGA Card

FFP

The Contractor shall provide Fibre Channel Diagnositc Tool Hardware IAW SOW in Section C.

FOB: Destination

NET AMT

Annual Maintenance Plan (Hardware Only)

The contractor shall provide an Annual Maintenance Plan IAW Section C SOW.

NET AMT

Contract Data Requirements Lis (CDRLs)

The Contractor shall provide data in accordance with the Contract Data Requirements List (CDRL), DD Form 1423, at Exhibit A to the contract.

NET AMT

Section C - Descriptions and Specifications

STATEMENT OF WORK

Controlled by: Dept. of Navy Controlled by: NAWCWD Code E594000 CUI Category: Procurement & Acquisition Distribution/Dissemination Control: FEDCON

Statement of Work For Fibre Channel Diagnostic Tool March 2023

1 SCOPE:

This Statement of Work (SOW) defines the effort required for the design, development and delivery of a Fibre Channel Diagnostic Tool in support of the Cyber Test and Evaluation (T&E) Division, Code E594000, located at the Naval Air Warfare Center Weapons Division (NAWCWD), Point Mugu, CA. The objective is to upgrade the Fibre Channel Diagnostic Tool for software and hardware interface of New Wave V1151 (400-01151-12-00) Switched Mezzanine Card (XMC). This includes the associated upgrade of the Field-Programmable Gate Array (FPGA) firmware.

1.1 Introduction:

Fibre Channel high-speed data transfer protocol runs at up to a multi-gigabit rate with lossless delivery of real-time data over optical fiber or copper cabling. The Department of Defense (DoD) has a need to implement a Fibre Channel Diagnostic Tool to assess system performance and test new capabilities. The Fibre Channel Diagnostic Tool consists of XMC Mezzanine Card, which includes a FPGA and software for the FPGA and a host computer Application Programming Interface (API).

1.2 Background:

The Cyber T&E Division is part of the Weapon System Protection Engineering Department under the Research and Development (R&D) Group, Code E594000. The Mission of the Cyber T&E Division is to test Naval Aviation’s aircraft, weapons and stores cyber posture to eliminate vulnerabilities that can degrade the ability for mission success. Cyber T&E Division partners with the DOD’s Central Test and Evaluation Investment Program (CTEIP) to design, develop, produce, and deploy an improved cyber security tool that will fulfill the Navy’s requirements.

1.3 Acronyms and Definitions:

2 APPLICABLE DOCUMENTS:

2.1 Department of Defense specifications:

2.1.1 NISPOM 32 CFR Part 117, 24 Feb 2021

2.1.2 2.1.2 SECNAVINST5510.36B, Department of the Navy Information Security Program, 12 July 2019

2.1.3 DoDI 5200.48 Controlled Unclassified Information (CUI), 6 Mar 2020

2.1.4 DoDM 5400.07, Freedom of Information Act (FOIA) Program, 25 Jan 2017

2.1.5 DoDI 5230.24, Distribution Statements on Technical Documents, Change 3, 15 Oct 2018

2.2 Industry documents:

2.2.1 ANSI/INCITS 373-2003 Information Technology: Fibre Channel Framing and Signaling Interface (FC-FS)

2.2.2 ANSI/INCITS 404-2006 Information Technology: Fibre Channel Physical Interface 2 (FC-PI-2)

2.2.3 IRIG STANDARD 200-04 IRIG SERIAL TIME CODE FORMATS

2.2.4 IETF-OPSWAG-PCAPNG PCAP Next Generation (PCAPNG) Capture File Format

2.2.5 IEEE Std 1076™-2008 IEEE Standard VHDL Language Reference Manual

2.2.6 IEEE Std 1800™-2017 IEEE Standard for SystemVerilog

2.2.7 ANSI/VITA 42.0-2021 XMC: Switched Mezzanine Card (XMC) Auxiliary Standard

2.2.8 ANSI/VITA 42.3-2020 XMC PCI Express Protocol Layer Standard

2.2.9 American Society for Testing and Materials (ASTM) manual A

3 REQUIREMENTS:

3.1 General Requirements for Fibre Channel Tool Kit Capabilities:

3.1.1 The contractor shall provide the Fibre Channel Diagnostic Tool (the tool) that contains and provides the following:

3.1.1.1 Support for Fibre Channel bit rates of 1, 2, and 4 gigabits (Gb) per second.

a. The tool shall provide performance capability that supports all operations described below at data transfer rates up to the full rated 1, 2 or 4 gigabits per second (Gbps) capability of the Fibre Channel technology.

3.1.1.2 The ability to connect the tool inline between a Fibre Channel node device and a switch. When connected inline between a Fibre Channel node device and a switch, the tool shall allow two-way transfer of all Fibre Channel frames received from either side of its connections on to the other side. This transfer of frames shall be initiated and completed after performing frame data content analysis (see item 3.1.1.3a) and modification tasks (see item 3.1.1.3b) as described below.

a. The time delay introduced by the reception, analysis, modification and forwarding tasks cannot exceed the time allocated to receive the subsequent frame. The time delay introduced by the reception, analysis, modification, and forwarding tasks must not result in a steadily growing backlog of frames on the transmission side in comparison to operation without the tool inserted into the data path. In other words, the tool must perform all of its operations on each frame in less time than it takes to receive the subsequent frame.

3.1.1.3 A fully documented Field-Programmable Gate Array (FPGA) code image to perform the following tasks:

a. Analyze the entire content of each Fibre Channel frame after it has been received.

b. Optionally perform selective modifications on data within the analyzed frame.

c. Optionally generate data frames with arbitrary content and forward them to the receiving Fibre Channel device.

d. Either forward the received frame (with or without modifications) to the receiving Fibre Channel device or discard the frame without forwarding it.

3.1.1.4 The ability to connect the tool directly to a port on a Fibre Channel switch and then produce an arbitrary sequence of frames under control of customer-developed software on a host Personal Computer (PC).

a. This capability represents Fibre Channel traffic generation.

b. The data frames may be generated by code in real time or may be derived from previously recorded data frames stored on a host PC.

3.1.1.5 The tool shall be capable of logging Fibre Channel traffic continuously at least up to 2 Gbps Fibre Channel bit rate to the host PC.

a. Logged frames must be stored in Packet Capture Next Generation format (PCAPNG, the specification is located at https://github.com/pcapng/pcapng).

3.1.1.6 Provide a software API to allow a C# application designed by the customer to:

3.1.1.1 3.1.1.2 3.1.1.3 3.1.1.4 3.1.1.5

a. Control the tool Fibre Channel ports.

b. Manipulate the configuration of the FPGA logic.

c. Enable and disable operation of the FPGA logic.

d. Transmit frame data from the host PC and receive frame data to the host PC.

e. Generate .NET event notifications to provide callbacks into customer-developed code in response to FPGA-initiated events such as the reception of a frame.

f. Control traffic generation operations of the Fibre Channel Diagnostic tool.

g. Data transfer to and from the host PC shall be via Direct Memory Access (DMA) over the PCI Express (PCIe) interface.

h. Perform the standard Fibre Channel login procedures and to establish upper layer protocol connection operations.

3.1.1.7 The design shall contain a System Time register that can be initialized by software and incremented by hardware.

a. The System Time register is used as a time stamp in PCAPNG frames.

b. The System Time register can optionally be driven by an IRIG-B time signal.

c. The System Time register can be used to time the delay of frame transmissions.

3.1.1.8 The Fibre Channel Diagnostic Tool supports IRIG format B only with BCD Time-of-Year (TOY) decoding.

3.1.1.9 Using the DC Level Shift (DCLS) IRIG signal specification, the design shall accept B00x formats where x can be 0-7 although only the BCD (TOY) information is decoded. Acceptable input signaling level is < 0.8V for logic 0, and > 2V for logic 1 into a 50 ohm load. Maximum input voltage is not to exceed +5V. The sample rate for DCLS is 10 nanoseconds providing a corresponding ±20 nanoseconds accuracy for DCLS IRIG-B System Time.

3.2 XMC Mezzanine Card Requirements:

Figure 1: New Wave V1151 XMC Card Block Diagram

3.2.1 The contractor shall deliver two units of the New Wave V1151 (400-01151-12-00) XMC mezzanine card containing encrypted Intellectual Property (IP) Core and proprietary software. Licenses for this IP were previously acquired by the government. As shown in Figure 1, the New Wave V1151 (400-01151-12-00) XMC Card provides the following:

3.2.1.1 At least four Small Form-Factor Pluggable (SFP28) ports capable of 1/2/4 Gb Fibre Channel.

3.2.1.2 Direct Memory Access (DMA) engine to transfer Fibre Channel frames to host PC memory.

3.2.1.3 Supports a minimum Peripheral Component Interconnect Express (PCIe) Generation 3 x8 interface to ensure adequate bandwidth for capturing frames to the host.

3.2.1.4 At least 8 gigabytes of Double Data Rate 4th Generation (DDR4) Synchronous Dynamic Random Access Memory (SDRAM) 64Bit operating at 1200MHz or better.

3.2.1.5 Pulse Per Second (PPS) time synchronization with 1 μSec resolution

3.2.1.6 Flash memory for FPGA configuration storage.

3.3 FPGA Software Requirements:

The New Wave V1151 (400-01151-12-00) XMC mezzanine card solution provides a real time high-bandwidth network interface. The FPGA (Xilinx Kintex Ultrascale FPGA (XCKU095-2FFVC1517I) implements complex logic designs.

Figure 2: Overview of New Wave V1151 (400-01151-12-0) XMC

Figure 3: IP Core Design

3.1 3.2 3.3

3.3.1 Figure 2 shows the required implementation for development on the V1151 (400-01151-12-00) XMC Card, which provides the following:

3.3.1.1 Provide a programming interface for registers or Random Access Memory (RAM) to be accessible from the host PC via the PCIe interface

3.3.1.2 Frame logging DMA connections shall write to a software configurable buffer on the host PC.

3.3.1.3 The ability to reprogram the FPGA through PCIe.

3.3.1.4 Each IP Core contains a Substitution Engine and DMA Engine as shown in Figure 3.

3.3.1.5 The transmit DMA is interleaved with incoming frames from a neighboring IP Core and sent out the Fibre Channel Port and into a receive DMA to be sent to the host.

a. The frames received on the Fibre Channel Port are passed to the Substitution Engine and a receive DMA to be sent to the host as shown in Figure 2 and Figure 3.

b. After the Substitution Engine the frames are passed out of the IP Core to a neighboring instance where they shall be transmitted as shown in Figure 2 and Figure 3

3.3.1.6 The user shall be able to perform modifications on Fibre Channel frames using Substitution Engine:

a. The Substitution Engine shall evaluate 4 operations in parallel on a frame. Operations may be chained together to create the desired functionality. Once all operations are complete, the frame shall be forwarded out of the engine for transmit.

b. Each Substitution Engine shall contain a 16KB block of user-defined Random Access Memory (RAM). This RAM can be manipulated by software over PCIe and used by Substitution Engine Operations.

c. Each Substitution Engine shall contain a Transmit Queue with a depth of 8 frames:

i. A Transmit Operation or Delay Operation are used to add frames to the queue.

ii. When adding a frame to the queue, a delay can be specified which is in microseconds from the time the frame is added to the queue.

iii. The queue is handled in first-in, first-out (FIFO) order.

iv. If a frame with a lower delay is queued after a frame with a higher delay the frame with the higher delay will block transmission of the second frame even though the delay was lower.

d. Each Substitution Engine shall contain a Linear Congruential Generator (LCG) to generate pseudo-random numbers.

i. The LCG can be seeded by setting the LCG Seed Register.

ii. Each time the LCG is used in a Save Operation or Overwrite Operation it will automatically calculate the next available number.

iii. The exact implementation of the LCG is the following equation:

Zn+1 = (1664525 × Zn + 1013904223) mod 232

e. The Substitution Engine Operation Table includes the following operations:

i. Save Operation: Shall allow the user to store data from the frame or modify already stored data for later use in another operation.

ii. Compare Operation: Shall allow the user to wait for a given condition to occur and specify which operation shall be next based on a given condition.

iii. Overwrite Operation: Shall overwrite a 4-byte word in the frame.

iv. Drop Operation: Shall trigger the frame to be dropped rather than forwarding it out when all operations are complete.

v. For-Loop Operation: Shall increment the Frame Offset on all subsequent operations by a given amount for a given number of loops.

vi. Transmit Operation: Shall queue transmission of a FC frame from User Defined RAM to the Transmit Queue.

vii. Delay Operation: Shall hold transmission of frame for a given amount of time while letting other traffic pass uninterrupted.

f. The Current Operation Register in the substitution engine shall enable series of operations and also can be read to see the operation index that shall be executed on receipt of the next frame.

g. Example configuration of all substitution engine operations shall be provided for the user as a demo.

3.3.1.7 Each instance of the IP Core shall have a DMA Engine that can be used to inject frames for transmission as well as receive frames.

a. Transmission of frames shall be interleaved with frames coming into the IP Core from the Substitution Engine of the adjacent IP Core.

b. Reception of frames shall be both from what is transmitted and what is received thus allowing full capture of the input and output of the port.

c. Each DMA connection available shall read/write from circular buffers in host

i. Software shall configure these buffers on the host PC and provide them to the hardware via registers in the DMA controller.

ii. Those registers allow configuration of the buffer location and size as well as hardware and software circular buffer write/read pointers.

d. For receive each frame written to the host shall be encapsulated in a PCAPNG Enhanced Packet Block. The frames shall be written sequentially to the buffer and wrap automatically at the end of the buffer.

e. For transmit each frame written by the host shall be encapsulated in a PCAPNG Enhanced Packet Block. The frames shall be transmitted sequentially from the buffer and wrap automatically at the end of the buffer. The relative timing of transmitted frames must be based on the time tags in the PCAPNG records relative to the time of the first frame in the file.

3.3.1.8 IRIG-B logic shall be implemented on the V1151. The IRIG-B signal is brought into the V1151 via a UMC connector on the card.

a. The System Time is stored in a pair of 32-bit registers for a 64-bit time with a resolution of 1ns. The System Time can be populated by directly writing the registers via software or an Inter-Range Instrumentation Group (IRIG)-B signal as specified in IRIG Standard 200-04

b. The V1151 card is only DCLS (PWM) capable. Input of this signal is via pin 25 on the P14 connector or the J2 SMA U.FL connector on the V1151 board. Maximum input voltage is not to exceed +5V.

3.4 Host Computer API Requirements:

3.4.1 The purpose of the host computer API is interacting with the FPGA and Fibre Channel communications from the host PC. A software interface shall be compatible with both Linux, Windows 10, and Windows 11, and Microsoft .NET.

3.4.2 The software interface shall provide the following:

3.4.2.1 Allow configuration of the Fibre Channel ports

a. Basic configuration and status of the ports shall be available via API calls. This includes items such as:

i. SFP laser control

ii. Fibre channel link status, control and parameters.

iii. Resettable counters shall be available for frames, bytes and errors.

3.4.2.2 Allow configuration of the Substitution Engine

a. Configuration of the Substitution Engine shall be available via API calls.

b. Each operation shall be defined with a C++ or C# structure.

c. API calls shall be available to write an operation to a specific location in the Operation Table or to load an array of operations sequentially into the table at a given location.

d. Functions to allow enable and disable processing of a given sequence of operations.

3.4.2.3 Allow configuration of DMA of Fibre Channel frames

a. For the DMA of Fibre Channel frames via host memory. The driver shall allocate a block of memory which the user can then use to configure the frame buffers.

b. For frame receive, the customer application can poll for data or optionally receive interrupt driven notifications.

i. When data is requested, software shall provide a pointer to the start of the data and the length of data that is valid which shall contain one or more PCAPNG Enhanced Packet Blocks.

ii. The user application may then consume the data as desired. Once done with the data, the user application shall make an API call to return the buffers to the hardware for reuse which shall update the read pointer register in the DMA Engine.

c. For frame transmit the customer application shall provide raw data to send and the API shall encapsulate that data in a PCAPNG Enhanced Packet Block or the API shall accept PCAPNG frames for transmission.

d. The transmission of Frames from PCAPNG files shall be at times matching the relative times of the frames in the PCAPNG files. For example: if the first two frames were recorded 2 ms apart, then they shall be played back the same 2 ms apart. If the receiver is not ready and its time-to-ready exceeds the recorded relative time in file, then the playback will be delayed until the receiver is ready. If the receiver is ready before the playback time delay is reached, the playback will occur at the recorded file time.

3.5 Automatic Configuration:

Optionally, the Fibre Channel Diagnostic Tool shall automatically load at power-on a configuration from non-volatile memory. Once software has configured the Fibre Channel Diagnostic Tool, the API shall support copying the configuration to the non-volatile memory. Once saved, on each subsequent reset of the Fibre Channel Diagnostic Tool the configuration shall be loaded without requiring any software intervention. This enables a Fibre Channel Diagnostic Tool to be configured and then moved to another environment where no software is available to do the configuration. This option can be disabled to return the tool to normal operation.

3.6 FPGA Firmware Upgrade:

3.6.1 API calls shall be available to upgrade the FPGA firmware as well as a command-line application that utilizes those API calls.

3.7 Milestones

3.7.1 The tool development shall be implemented into multiple phases:

a. FPGA integration along with substitution engine

b. DMA to and from Host

c. Hardware IRIG time and Automatic Configuration with FPGA firmware upgrade

3.7.2 Contractor shall use Microsoft Teams to provide a virtual live demonstration of functionality for each software build released. Each demonstration will include verification of all requirements implemented during the phase.(A001)

3.7.3 Contractor shall send FPGA integration and substitution engine software at the end of each phase (A001).

3.7.4 Contractor shall provide a Fibre Channel Tool user manual and API software for each build released (A001).

3.8 Status Meeting

3.8.1 Meeting support: In support of the tasking outlined in this SOW, the Contractor shall have the capability to host and conduct meetings at the classification levels up to Controlled Unclassified Information (CUI) with the capacity to support a minimum of 5 persons and have contractor furnished telephone and Microsoft Teams capability as well as sufficient equipment to conduct meetings with presentations including compatible software.

4 DELIVERABLES

All data deliverables under this contract shall be in accordance with Exhibit A, DD Form 1423s.

5 CONTRACT STATUS REPORTING:

5.1 The contractor shall provide the following documentation:

5.1.1 Monthly Progress and Financial Status Report: The contractor shall provide a progress and financial status report in accordance with the Contract Data Requirement List (CDRL A002). The report shall include work accomplished since submittal of the last report, both monthly and cumulative man-hour labor costs expended by labor category and material and travel costs.

6 WORK SCHEDULE:

6.1 Work schedule to include Government Installation Work Schedule (CWS), holidays, and installation closure.

6.2 The Holidays applicable to this contract are: New Year's Day, Birthday of Martin Luther King Jr., Washington’s Birthday (President's Day), Memorial Day, Juneteenth National Independence Day, Independence Day, Labor Day, Columbus Day, Veteran's Day, Thanksgiving Day, and Christmas Day.

6.2.1 In the event that any of the above holidays occur on a Saturday or Sunday, or alternate Friday, then such holiday shall be observed as they are by the assigned Government employees at the using activity.

6.3 The Naval Air Warfare Center Weapons Division works a 4/5/9 work schedule. Therefore, alternate Fridays are not a part of the normal workweek for work performed on-site at a Naval Air Warfare Center Weapons Division site. The majority of the Government offices are closed on alternate Fridays.

6.4 Installation closure: When Federal facilities are closed by the Government, or when Federal employees are officially excused from work due to a holiday or a special event, severe weather, a security threat, or any other Government facility related problem that prevents Federal personnel from working at the Government facility, contractor personnel assigned to work at that facility in support of such Federal employees shall follow their parent company’s policies.

7 SECURITY:

7.1 Citizenship Requirements: Only U.S. citizens may perform under this contract. If the Contractor cannot find qualified U.S. citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:

7.1.1 The individual's name, date and place of birth, position title, and current citizenship.

7.1.2 A statement that a qualified U.S. citizen cannot be hired in sufficient time to meet the contractual requirements.

7.1.3 A statement of the unusual expertise possessed by the applicant.

7.1.4 A statement that access will be limited to a specific government contract (specify contract number). A statement that the Contractor has obtained an export license for the information required to perform the contract.

7.1.5 A statement that the Contractor has obtained an export license for the information requires to perform the contract.

8 INVESTIGATIVE REQUIREMENTS:

8.1 Any product containing Covered Defense Information shall be assigned a distribution statement (distribution statements B through F) using the criteria set forth in DoDI 5230.24 (Distribution Statements on Technical Documents); and have this statement displayed per DoDI 5230.24, Enclosure 3. All controlled unclassified technical information shall be appropriately identified and marked with the following distribution statement(s):

8.1.1 Distribution Statement (D authorized to the Department of Defense and U.S. DoD contractors only), DISTRIBUTION D: Distribution authorized to Department of Defense (DoD) agencies and DoD contractors only. Administrative/Operational Use, 20 March 2023. Other requests for this report shall be referred to Commander, Code E594000, Naval Air Warfare Center, 575 I Ave, Point Mugu, CA.93042-5049,

8.1.2 In the case of an unclassified contract that requires no access to Classified Military Information (CMI), but that does require access to CUI, NAWCWD Restricted Areas, and/or Government IT systems, contractors are required to comply with non-NISP processing requirements before local access to CUI, Restricted Areas, and IT can be granted. This process shall be coordinated by the Technical Point of Contact (TPOC) through the NAWCWD Industrial Security office.

9 Marking:

All information generated by the Contractor shall be properly marked.

9.1 CUI generated and/or provided under this contract shall be marked in accordance with DoDI 5200.48(Controlled Unclassified Information (CUI))

9.2 All products and technical information shall be marked with appropriate Distribution Statements and Export Control warnings per above guidance and program Security Classification Guidance

Section D - Packaging and Marking

5252.247-9508 PROHIBITION AND LIMITATIONS FOR PACKAGING MATERIALS

(NAVAIR) (AUG 2019)

The use of loose fill materials, asbestos, excelsior, newspaper and shredded paper (all types) are prohibited. In addition, all Wood Packaging Materials (WPM) shall be heat treated or chemically treated in accordance with the requirements of the International Standards for Phytosanitary Measures (ISPM) 15:2009, "Regulation of Wood Packaging Material in International Trade."

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLAUSES INCORPORATED BY REFERENCE

Section F - Deliveries or Performance

DELIVERY INFORMATION

29-NOV-2024

29-NOV-2024

29-NOV-2024

29-NOV-2024

Contract Specialist (CS) Code E253000: shana.m.hwang.civ@ua.navy.mil Procuring Contracting Officer (PCO) E253000: helen.n.xiong.civ@us.navy.mil

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

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

________Invoice and Receiving Report (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.

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

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

Contract Specialist (CS), shana.m.hwang.civ@us.navy.mil Procuring Contracting Officer (PCO), helen.n.xiong.civ@us.navy.mil

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

(End of clause)

Payment shall be made in accordance with FAR Clauses 52.216-7, "Allowable Cost and Payment," and 52.216-8, "Fixed Fee."

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

GTXT-0001 PAYMENT INSTRUCTIONS (APR 2018)

Note: Payment Clause 52.216-7 & 52.232-1 apply to the contract.

FOR GOVERNMENT USE ONLY

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

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 Transportation-Related Services Contracts; and 52.232-6, Payments under Communication Service Contracts with Common Carriers

52.232-29, Terms for Financing of Purchases of Commercial Items;

52.232-30, Installment Payments for Commercial Items

*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 H - Special Contract Requirements

Section I - Contract Clauses