HT9425-25-Q-0068 Amendment 1.docx

HT942525Q0068

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 16-Jul-2025 11:00 AM to 21-Jul-2025 11:00 AM.

SUPPLIES OR SERVICES AND PRICES

CLIN 0001

The CLIN extended description has changed from:

Orthopedic Templating Software that can support 125 users at any time. Multiple invoices are authorized for this CLIN.

To:

Orthopedic Templating Software that can support 125 users at any time. Multiple invoices are authorized for this CLIN.

CLIN 0002

The CLIN description has changed from Licenes to License.

CLIN 0003

Training vitrual for 12 sites. See list below for the twelve sites. Multiple invoices are authorized.12 Sites:i. Tripler Army Medical Center, HI;ii. Brian D. Allgood, Korea;iii. Evans Army Community Hospital, CO;iv. Madigan Army Community Hospital, WA;v. Brooke Army Medical Center;vi. Walter Reed National Military Medical Center;vii. Womack Army Medical Center;viii. Landstuhl Regional Medical Center, Germany: 30;ix. Blanchfield Army Community Hospital, KY;x. Eisenhower Arch Community Medical Center, GA;xi. Portsmouth Naval Medical Center, VA;xii. Naval Medical Center San Deigo, CA:

Training virtual for 12 sites. See list below for the twelve sites. Multiple invoices are authorized.12 Sites:i. Tripler Army Medical Center, HI;ii. Brian D. Allgood, Korea;iii. Evans Army Community Hospital, CO;iv. Madigan Army Community Hospital, WA;v. Brooke Army Medical Center;vi. Walter Reed National Military Medical Center;vii. Womack Army Medical Center;viii. Landstuhl Regional Medical Center, Germany: 30;ix. Blanchfield Army Community Hospital, KY;x. Eisenhower Arch Community Medical Center, GA;xi. Portsmouth Naval Medical Center, VA;xii. Naval Medical Center San Deigo, CA:

CLIN 0005

Surge LIcenses fo software

Surge Licenses for software

DELIVERIES AND PERFORMANCE

The following Delivery Schedule item for CLIN 0001 has been changed from:

DEFENSE HEALTH AGENCY

7700 ARLINGTON BLVD

FALLS CHURCH VA 22042

FOB: Destination

HT0070

ICS PMO

693 NEIMAN STREET

FORT DETRICK MD 21702

HT1267

The following Delivery Schedule item for CLIN 0002 has been changed from:

DEFENSE HEALTH AGENCY

7700 ARLINGTON BLVD

FALLS CHURCH VA 22042

HT0070

ICS PMO

693 NEIMAN STREET

FORT DETRICK MD 21702

HT1267

The following Delivery Schedule item for CLIN 0003 has been changed from:

DEFENSE HEALTH AGENCY

7700 ARLINGTON BLVD

FALLS CHURCH VA 22042

HT0070

ICS PMO

693 NEIMAN STREET

FORT DETRICK MD 21702

HT1267

The following Delivery Schedule item for CLIN 0004 has been changed from:

DEFENSE HEALTH AGENCY

7700 ARLINGTON BLVD

FALLS CHURCH VA 22042

HT0070

ICS PMO

693 NEIMAN STREET

FORT DETRICK MD 21702

HT1267

The following Delivery Schedule item for CLIN 0005 has been changed from:

DEFENSE HEALTH AGENCY

7700 ARLINGTON BLVD

FALLS CHURCH VA 22042

HT0070

ICS PMO

693 NEIMAN STREET

FORT DETRICK MD 21702

HT1267

The following have been modified:

CLAUSE(S) 52.212-1 - ADDENDUM TO FAR 52.212-1

ADDENDUM TO FAR 52.212-1

ADDENDUM TO 52.212-1 INSTRUCTIONS TO OFFERORS - COMMERCIAL ITEMS

This Request for Quote (RFQ) is in support of Picture Archiving and Communication Systems (PACS) Program Management Office (PMO), Integrated Clinical Systems (ICS) J-6 for Orthopedic Templating Software.

This requirement is being solicited as a full and open competition under the North American Industry Classification Code (NAICS) 513210, Software Publishers. The size standard for NAICS 513210 is $47 million.

1. SPECIFIC REQUIREMENTS.

This requirement will result in a Firm-Fixed Price (FFP) contract. Performance requirements for this contract are provided in the Minimum Essential Characteristics (MECs).

2. DELIVERY DATE.

The estimated final delivery date for this contract is as follows:

3. ADDENDUM TO 52.212-1 INSTRUCTIONS TO OFFERORS.

In addition to the guidance included in FAR Provision 52.212-1 entitled “Instructions to Offerors – Commercial Products and Commercial Services” the following are applicable for the preparation and submission of quotes.

This section specifies the format and content that the Offeror shall use in this RFQ. The Offeror must submit a quote that is legible and comprehensive enough to provide the basis for a sound evaluation by the Government. Information provided should be precise, factual, and complete. Legibility, clarity, completeness, and responsiveness are of the utmost importance. The quote shall be in the form prescribed by, and shall contain a response to, each of the areas identified in the Addendum to 52.212-1.

Administrative Format Instructions.

Each quote should contain the following items in addition to the technical/descriptive data required by this RFQ:

- Cover Page which includes the following:

- RFQ Number;

- Offeror name, mailing address, and website address;

- Unique Entity ID;

- Commercial and Government Entity (CAGE) Code;

- Date submitted and quote expiration date;

- All of the above-cited information for each entity on the proposed team, if a team is proposed;

- Type of Company (i.e., Large Business, small business, 8(a), woman owned, veteran owned, etc.) as validated via the System for Award Management (SAM);

- Company Point of Contact (POC), Phone and Email address; and

- Table of contents, which provides sufficient detail as to allow the important elements to be easily located; and Each page of each document should have a footer indicating the name of the Offeror, “page X of Y,” and the following legend “Source Selection Information: See FAR Part 3.104.”

Formatting.

Quote content shall be in Microsoft Office for Windows format (2007 or 1997-2003), either .doc or .docx file and/or searchable Adobe Acrobat (.pdf file), with one (1) inch margins all around, Times New Roman font of not less than ten (10) point font size.

Page Limits.

Quote is limited to fifteen (15) single-sided pages. Pages should be numbered consecutively throughout the document and not by sections. For any sections of a quote with a defined page limit, pages exceeding the specified limit will be removed and not forwarded for evaluation. The following sections are not subject to the 15-page limit:

- Cover Page (Not to exceed one (1) single-sided page);

- Table of Contents; and

- Pricing sheet.

Quote: The Offeror’s quote shall clearly reflect the Offeror’s approach to execute and comply with the performance requirements identified in the MECs. The Offeror’s quote, including any supporting documentation, is to be clear and concise.

In accordance with file submission requirements given in this section, the Offeror shall submit a written Technical Quote that effectively demonstrates the following:

Factor 1 - Technical Approach: The Offeror shall submit a written technical approach, which effectively demonstrates: The overall ability to deliver the requirement in accordance with the MECs. This description should, at a minimum, specifically address the Offeror’s approach and ability to address these MEC. Proposed Technical Approach will be evaluated to determine whether it’s acceptable or unacceptable

Factor 2 - Past Performance: The Offeror is not required to submit any information regarding Past Performance. The Government will consider information obtained through other sources (Contractor Performance Assessment Report System (CPARS), Supplier Performance Risk System (SPRS), Responsibility/ Qualification, Electronic Document Access (EDA), etc.). Past performance information will be utilized to determine the acceptability of the contractor’s past performance as it relates to the Government’s requirements as described in the MECs. In the case of an Offeror without a record of relevant past performance or for whom information on past performance is not available, the Offeror will not be evaluated favorably or unfavorably on past performance (FAR 15.305(a)(2)(iv)). And it will be considered acceptable.

Factor 3 – Price: This contract will be awarded on Lowest Price Technically Acceptable (LPTA) basis evaluating price using one or more of the price analysis techniques in FAR 15.101-2 and 15.404-1(b) to determine the price to be fair and reasonable. If, after receipt of the quote, the Contracting Officer cannot determine the price to be fair and reasonable, the Offeror shall provide other information requested to be submitted to determine fairness and reasonableness of price, or certified cost or pricing data as requested by the Contracting Officer. If certified cost or pricing data is not allowable, the data will be submitted as other than certified cost and pricing data.

- The Offeror shall propose on all contract line items, either by price or “NSP” (Not Separately Priced). A line-item price left blank will be considered nonresponsive to this request and the quote may not be considered for award.

- The Offeror shall provide a POC authorized to hold discussions/negotiations with the Government who has the full authority to bind the Offeror to a contract award. Information required includes: First name, last name, title, email address, phone number, and level of authority.

- The Offeror shall provide a POC who will be responsible for reviewing any applicable performance evaluation reports rendered by the Government. This will include electronic performance reports produced via the CPARS Reports. Information required includes: First name, last name, title, email address, phone number, and level of authority.

- The Offeror must be registered in SAM in accordance with FAR 52.204-7 and FAR 52.204-13. The Offeror shall verify its SAM record is current, accurate, complete and applicable to this RFQ as of the date of this offer and is incorporated in this offer by reference. This includes the completion of FAR Provision 52.204-24 [Representation Regarding Certain Telecommunications and Video Surveillance Services or Equipment] and FAR Provision 52.204-26 [Covered Telecommunications Equipment or Services-Representation]. Failure to complete these provisions may delay the execution of the award.

- The Offeror shall complete and submit FAR Provision 52.209-11 [Representation By Corporations Regarding Delinquent Tax Liability or a Felony Conviction under any Federal Law (Feb 2016)] (Refer to FAR Provision 52.209-11).

- The Offeror’s quote shall remain valid for a minimum of 120 days from the date of submission.

4. FILE SUBMISSION.

- The Quote shall be submitted via email on or before the RFQ closing date/time list in Block 8, to the point of contact for this RFQ, Nathan Anderson: Nathan.p.Anderson19.civ@health.mil. Subject: HT9425-25-Q-0068. The firewall utilized by the Government Contracting Office goes not authorized or accept zip files.

Any data previously submitted in response to another solicitation, whether submitted to the USAMRAA or another agency, should be assumed to be unavailable during this quote’s evaluation and award process. Quotes data shall not be incorporated into the quote by referring to another quote or other source.

The Government reserves the right to request additional information after receipt of Offeror’s response to the RFQ.

Offerors are cautioned that in order for their quote to be eligible for award, the quote shall be in compliance with all of the terms and conditions set forth in the RFQ.

- RFQ Questions. Questions concerning the RFQ are due no later than 2 July 2025, 11 AM Eastern Time. Questions may not be addressed after this cutoff date. Questions shall be submitted via email to Nathan.p.Anderson19.civ@health.mil (Subject: HT9425-25-Q-0068). Offerors shall submit one set of questions only; multiple submissions shall not be accepted. An amendment to the RFQ will be issued providing responses to the questions.

- Discussions. The Government intends to evaluate the quotes and award a single contract without discussions with the Offeror. The Government reserves the right to conduct discussions if the Contracting Officer later determines them to be necessary.

5. ADDITIONAL INFORMATION.

- Alternate Quotes (FAR 52.212-1(e) Multiple Offerors is removed and replaced with this language). Only one quote from the Offeror will be accepted/evaluated by the Government. No alternate quotes will be accepted/evaluated from the Offeror. If alternate quotes are provided, only the first quote received by the Government will be accepted/evaluated.

- Provisions and Clauses. See the RFQ for the list of applicable provisions and clauses that will be included in the RFP (the clauses will be included in the contract award). By submission of a quote, the Offeror agrees to the inclusion of these provisions and clauses.

MECS

Minimum Essential Characteristics (MECS) Orthopedic Templating Software

The contractor shall deliver software and configure it as necessary to establish connectivity throughout the infrastructure. The ultimate service goal is to consolidate site local Picture Archiving and Communication Systems (PACS) to a Hub and Spoke model throughout the enterprise to provide standardization across the Defense Health Agency (DHA). This task includes but is not limited to:

i. Implementation at government hosted virtual environment not directly associated with any currently deployed PACS. The Government Host Environment will provide a backup solution. The selected vendor will provide the server(s) files and location(s) for what needs to be backed up during implementation.

ii. Standardize system configurations throughout the DHA Enterprise

iii. Fully capable to integrate with the PACS desktop

iv. Utilize a Web version of the client to allow reconstructions without limitation of location with thick client.

A: Delivery and configuration of software

1. Must be capable of 2-dimentional radiographic templating software compatibility within the PACS

2. Must have an extensive and evolving template database (to account for new implants, etc.) that is implant company agnostic

3. Must have the ability to calculate angles/Cobb angles/lengths

4. Must have the ability to perform fracture-specific planning (manipulating fracture fragments and a ‘reduction’ function)

5. Shall incorporate use of Artificial Intelligence (AI) tools (‘assistants’ or ‘wizards’ for preoperative planning)

6. Ability to measure/manipulate images in 3-dimensions prior to Go-Live

7. Must support 125 users at any given time

8. Shall have the ability to support additional users over the course of the contract

9. Any templating licenses already purchase by DHA can be re-utilized, if possible, to reduce procurement cost to the government. Prior purchased license can be accounted for they do not have to be 5-years of maintenance must be included in the vendors offer regardless if prior purchased licenses are accounted for and if there is a current SMA on licenses.

B: Additional required Information

1. The contractor shall provide a detailed topography document to include how the enterprise system will be configured and deployed with submission. The document will be updated to reflect any changes during implementation within 7 days after to Go-Live (Deliverable #1 and #2)

2. Must offer/implement the most commercially available software version with the ability to obtain a DHA Enterprise level Authority to Operate (ATO) within 12 months. The entire solution must commercially available solution at time of submission that meets or exceeds the standards in this MECS, no future features and functionality of the solution will be considered.

3.The contractor shall include maintenance support for the enterprise software solution over the contract period of 5 years.

4. The contractor must include software updates/upgrades, to include any professional services required. The application version deployed is the current commercially available software version.

5. Software updates and upgrades will not be made without the written approval from the designated Government’s official.

6. The contractor shall provide applications training for 150 individuals at the 12 PACS Hubs across the enterprise. Training shall be conducted twice virtually per PACS Hub. One virtual session shall be recorded and saved for future training purposes.

Hub locations are as follows:

i. Tripler Army Medical Center, HI

ii. Brian D. Allgood, Korea

iii. Evans Army Community Hospital, CO

iv. Madigan Army Community Hospital, WA

v. Brooke Army Medical Center

vi. Walter Reed National Military Medical Center, MD

vii. Womack Army Medical Center, NC

viii. Landstuhl Regional Medical Center, Germany

ix. Blanchfield Army Community Hospital, KY

x. Eisenhower Arch Community Medical Center, GA

xi. Portsmouth Naval Medical Center, VA

xii. Naval Medical Center San Deigo, CA

7. The contractor shall provide virtual trainings at each PACS Hub when an upgrade to the software application is applied.

8. The contractor shall assign a Project Manager (PM) within 30 calendar days after award.

9. The contractor shall conduct meetings weekly with project updates until project completion. and provide weekly reporting regarding the status of each site’s progress.

10. The contractor shall deliver a draft project plan at proposal submission and final project plan within 30 days after award of the contract The contractor shall provide a detailed implementation plan and timeline for all sites at time of submission. (Deliverable #3 and #4).

Implementation plan shall include the following:

i. The project plan shall include the start of delivery of software within 60 calendar days of award of the contract and installation shall begin within 90 calendar days of award. All sites must Go-live (clinically in use) within 12-months of contract award.

ii. The detailed project plan shall highlight the key deliverables, timelines, and expectations of each party responsible for delivery, configuration, and final acceptance of the systems Comprehensive implementation plan to install all systems, including total number of project managers and implementation team(s) involved.

iii. Detailed steps and task owners for implementation as well as expected completion time for each task.

iv. Proposed timeline for production Go-live for all implementations. “Go-live” date is met by full clinical usage of the system with fulfillment of migration requirements related to Go-live with no reliance on the legacy system.

11. The contractor shall host weekly status meetings with the Government representatives; contractor shall provide meeting agenda 24 hours prior to meeting and provide meeting minutes within 48 hours of the meeting conclusion. Meeting minutes will be provided in PDF format.

12. The contractor shall provide all the following, included in the setup/configuration of the system to ensure proper installation.

13. The contractor shall validate functionality of software in accordance with Risk Management Framework (RMF) accreditation documentation. RMF/Authority to Operate (ATO) must continually be updated to meet the requirement of item number 4.

14. The contractor shall validate RMF Security Technical Implementation Guide (STIG) requirements and scan for vulnerabilities with Department of Defense (DoD) provided Nessus vulnerability scan software.

15. The contractor shall resolve or mitigate any Category 1 or High Category 2 vulnerabilities

16. The contractor shall upon site installation validate configuration is correct and working

17. The contractor shall agree to the DHA Cybersecurity/RMF requirements, receive an ATO and maintain the ATO for the life of the contract in accordance with the contractual period of performance or as long as mutually agreed to by both parties. (Deliverable #5).

18. The contractor shall maintain an ATO on all product versions owned by the DHA and originally purchased through the awarded contract. If a contractor cannot support the ATO for all DHA owned versions of the product, the contractor can meet this requirement by offering to provide all upgrades to the product that are required to maintain the ATO for u for the life of the contract in accordance with the contractual period of performance or as long as mutually agreed to by both parties. (Deliverable #6).

19. The contractor shall provide all costs/prices needed to meet the requirements in this document as part of their offer/quote and any items not included in the contractors offer/quote shall be offered at no cost for up to five (5) years in accordance with the contractual period of performance or as long as mutually agreed to by both parties. Contractors who cannot support all versions of the product and cannot offer upgrades required to maintain the ATO for up to five (5) years shall not be considered. Maintaining the RMF ATO shall be included as part of the contractor’s warranty period.

20. The awarded contractor shall maintain the ATO; for up to five (5) years in accordance with the contractual period of performance or as long as mutually agreed to by both parties. If the patches are separate from updates as required by the contractor’s contract, the contractor shall offer the cybersecurity patches under a maintenance offering on their contract that provides for all required cybersecurity patches/updates needed to maintain the ATO.

21. The contractor shall agree to the DHA Cybersecurity requirements for all software purchased as part of this contract. Contractors may otherwise request an exception to cybersecurity policy. Exceptions to cybersecurity policy are contingent on approval by local and DHA Chief Information Officer (CIO) and Approving Official (AO).

22. The contractor shall agree to the DHA Cybersecurity requirements for all upgrades. Although there is an exception to cybersecurity policy process for upgrades similar to maintenance, the DHA does not envision granting exceptions to cybersecurity policy and would instead replace the software in lieu of approving upgrades that do not comply with cybersecurity policy.

23. The contractor shall ensure that personnel accessing information systems have the proper and current IA certification to perform IA functions at contract award in accordance with DoD 8140.03–M, IA Workforce Improvement Program. The contractor shall meet the applicable IA certification requirements as outlined in DFARS 252.239-7001, including.

24. The contractor shall have DoD-approved IA workforce certifications appropriate for each category and level as listed in the current version of DoD 8140.03–M.

25. The contractor shall have appropriate operating system certification for IA technical positions as required by DoD 8140.03–M.

26. Upon request by the Government, the contractor shall provide documentation supporting the IA certification status of personnel performing IA functions. Contractor personnel who do not have proper and current certifications shall be denied access to DoD IS for the purpose of performing IA functions.

28. All contractor employees that require access to DHA IT must comply with the requirements of DHA-Procedural Instruction 8140.01, Acceptable Use of DHA IT, to include those contract employees with privileged access.

29. The contractor shall provide vulnerability scan and Security Content Automation Protocol (SCAP) scan results to Government monthly. Contractor shall provide raw scan results and administrative reports no later than the 10th calendar day of each month (Deliverable #7).

30. If the contractor had a current ATO, the contractor will submit drawing from RMF/ATO package to clearly demonstrate any 3rd party contractors being quoted are within the contractors boundary with submission. If the contractor does not have a current ATO the contractor will submit a completed MEDRA with submission (Deliverable #8).

31. Business-to-Business (B2B) remote connection cannot be guaranteed, contractor should include costs for onsite installation and maintenance in the event B2B connection is not available or is not approved for a connection. The absence or lack of remote connectivity shall not delay implementation of system or configuration.

MILESTONE PERFORMANCE SCHEDULE

Orthopedic Templating Solution

Month 1

Kick Off Meeting with DHA PMO and vendor, project plan presented and agreed to by Govt and vendor.

Month 2 - 3

Kick Off meeting with PACS hubs, Network hosting team and software/licenses delivered

Month 4-9

Implementation and configuration of software PACS desktop integration configuration

Month 10

Configuration and integration testing with Super Users and DHA PMO

Month 11

System Administrator and User applications training

Month 12

System Go-live and DHA acceptance testing and validation

Deliverable Schedule

Initial

Due

Deliverable 1

Deliverable 2

Deliverable 7

Deliverable 8

Attachments:

Attachment #1 MDERA

52.212-2 EVALUATION--COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (NOV 2021)

(a) The Government will award a contract resulting from this solicitation to the responsible offeror whose offer conforming to the solicitation will be most advantageous to the Government, price and other factors considered. The following factors shall be used to evaluate offers:

Factor 1 - Technical Approach Factor 2 - Past Performance Factor 3 - Price

Basis for Award Award shall be issued using the Lowest Price Technically Acceptable (LPTA) evaluation process IAW FAR FAR 15.101-2. A contract will be issued upon the receipt of a quote that includes An acceptable technical capabilities statement that clearly shows the Offeror’s capability to perform the Minimum Essential Characteristics (MECs) at a fair market price, by an Offeror who has been determined to have Acceptable past performance.

The non-price factors, technical approach and past performance, will each be rated “Acceptable” or “Unacceptable” using the rating standard definitions below.

The non-price factors are collectively more important than price in that both non-price factors must receive a rating of Acceptable to be eligible for award. After both of the non-price factors are rated individually, an overall rating will be assigned collectively to these factors. If either of the non-price evaluation factors receives an individual rating of “Unacceptable,” the collective overall rating will also be “Unacceptable” and the proposal will not be eligible for award.

Rating Standards for the Technical Quote

Rating Standards for Past Performance

Government evaluators will not assume that the Offeror possesses any capability or knowledge unless it is specified in the quote.

Volume I – Technical Quote. The following criteria will be used to evaluate the non-price factors of the Technical Quote.

Factor (a) Technical Approach: The technical approach will be evaluated as to how the Offeror adequately demonstrates: The overall ability to perform services in accordance with the MECS. This description should, at a minimum, specifically address the Offeror’s approach and ability to address these tasks. Based on the Offeror’s proposal, the Government will determine the Offeror’s Technical Approach to be either Acceptable or Unacceptable.

Factor 2 - Past Performance: The Government will conduct a Past Performance evaluation of the Offeror’s Past Performance, as well as that of its Subcontractors. The Offeror’s own Past Performance is significantly more important than the Past Performance provided for each Subcontractor. The Government will evaluate the Offeror’s past performance information obtained through other sources (CPARS, SPRS, Responsibility/ Qualification, EDA, etc.) to determine the acceptability of recent efforts accomplished by the Offeror. Based on the offeror’s performance record, the Government will determine if there is a reasonable expectation that the offeror will successfully perform the required effort and determine the Offeror’s past performance to be either Acceptable or Unacceptable.

Factor 3 – Price: will not be scored or rated. Evaluation of price will be performed using one or more of the price analysis techniques in 15.404-1(b).

The total evaluated price will be evaluated for reasonableness in terms of:

a) Consistency with the technical quote in that the pricing is consistent with and reflects the quoted requirement.

b) The evaluated price will be the total of all the priced line items.

c) Unsubstantiated costs that are considered unreasonable, not fully supported, or both, may cause the overall technical evaluation to be adjusted in one or more of the non-cost/price evaluation factors.

Award will be made to the Offeror whose price is considered fair and reasonable and is the lowest evaluated price of proposals which meet or exceed the acceptability standards for non-cost factors.

(b)Options. The Government will evaluate offers for award purposes by adding the total price for all options to the total price for the basic requirement. The Government may determine that an offer is unacceptable if the option prices are significantly unbalanced. Evaluation of options shall not obligate the Government to exercise the option(s).

(c)A written notice of award or acceptance of an offer, mailed or otherwise furnished to the successful offeror within the time for acceptance specified in the offer, shall result in a binding contract without further action by either party. Before the offer’s specified expiration time, the Government may accept an offer (or part of an offer), whether or not there are negotiations after its receipt, unless a written notice of withdrawal is received before award.

(End of provision)

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.

__2in1 Invoice__________________________________________________________

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

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

____To be determined at the time of Award__________________________________________________

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

(End of clause)

(End of Summary of Changes) image1.wmf