N68520-22-R-0012 EQ RFQ 10 Jan2022.docx

N6852022R0012

Section A - Solicitation/Contract Form

SECTION A

POINTS OF CONTACT

CONTRACTING OFFICER:

Meagan Foster meagan.foster@navy.mil

CONTRACT SPECIALIST:

Meghan Huett meghan.huett@navy.mil

TECHNICAL POC:

Christine Morelli christine.r.morelli@navy.mil

Section B - Supplies or Services and Prices

ALE Services

FFP

ALE Services IAW Section C FOB: Destination

PURCHASE REQUEST NUMBER: 1300976614

PSC CD: DA10

NET AMT

FFP

ALE Services- OOMA Integration to IFS IAW Section C FOB: Destination

NET AMT

FFP

ALE Services- Supply Integration IAW Section C

NET AMT

FFP

ALE Services - CMPI Phase 2 IAW Section C

NET AMT

IDRN Services

IDRN Services IAW Section C

NET AMT

FFP

IDRN Services - PSM Phase 2 IAW Section C

NET AMT

FFP

IDRN Services - EWI IAW Section C

NET AMT

FFP

FST Services IAW Section C

NET AMT

AvPLM Services

AvPLM Services IAW Section C

NET AMT

Section C - Descriptions and Specifications

SECTION C

AvPLM Statement of Objectives for ALE and IDRN

1.0 Background

1.1 Background

The Commander Fleet Readiness Centers (COMFRC) Headquarters (HQ) Digital Group has the overall responsibility to research, develop, analyze, and evaluate enterprise Information Technology solutions to implement and deploy the best Naval Aviation Logistics Information Technology (IT) solutions across the Naval Aviation Enterprise (NAE).

The NAVAIR Aviation Product Lifecycle Management (AvPLM) Integrated Product Team (IPT) is a modernization effort in the Digital Group focused on modernizing legacy Logistics IT systems through configuration of commercial off-the-shelf (COTS) Product Lifecycle Management (PLM) software to enable business process workflows and data access in a standard approach, to reduce capability duplication across Logistics IT systems, and improve logistics data quality and availability in support of increased material readiness for the fleet. This includes full lifecycle management of product data from receipt through disposition and data exchange to Organization, Intermediate and Depot (O/I/D) Maintenance Management systems.

AvPLM encompasses the requirements of both the Aviation Logistics Environment (ALE) and the Integrated Digital Resource Node (IDRN).

2.0 Scope

The primary purpose of this task order is to purchase services from eQ Technologic (eQ) for development within and configuration of COTS software to support the modernization of capability in current Legacy Logistics IT systems including process workflows and connectors to authoritative data sources.

The Contractor will have to obtain permission before delivering software under this task order that incorporates any software that is not free and open source. The Contractor must post all developed code to a repository designated by the AvPLM IPT.

3.0 General Requirements

3.1 System Requirements - The System will be hosted on a FedRAMP-certified cloud storage solution controlled by NAVAIR. The System must incorporate an intuitive web-based interface that is accessible from both internal and external platforms, including desktops, laptops, tablets, thin/zero clients, and mobile devices. The System architecture must incorporate Application Programming Interfaces (APIs) to intermediate major components. The System must have no single point of failure. The System will use elastic, dynamically-allocated computing resources that accommodate changing demand in real time. The System must include user authentication and authorization functionality that uses open source encryption protocols. NAVAIR expects any enterprise authentication/authorization mechanisms to be integrated into the System.

3.2 Software Requirements – The software architecture must be extensible to allow for future development. The code base must incorporate analytics, monitoring, continuous integration, and measurement tools. Application design and development must use plain language to the extent practical.

3.3 Environments – NAVAIR will be responsible for creating, maintaining, and managing an internet-connected staging environment, and an internet-connected production environment, on a FedRAMP-certified cloud storage solution. The Contractor will be responsible for creating, maintaining, and managing its own development environment, which will be the only environment that the Contractor will deploy to. The Contractor’s development environment must mirror NAVAIR’s staging and production environments, except that the Contractor’s development environment need not be FedRAMP-certified.

3.4 Section 508 Compliance - Unless the Government invokes an exemption, all Electronic and Information Technology (EIT) products and services proposed shall fully comply with Section 508 of the Rehabilitation Act of 1973, per the 1998 Amendments, 29 United States Code (U.S.C.) 794d, and 36 Code of Federal Regulations (CFR) 1194. The Contractor shall identify all EIT products and services proposed, identify the technical standards applicable to all products and services proposed, and state the degree of compliance with the applicable standards. Additionally, the Contractor must clearly indicate where the information pertaining to Section 508 compliance can be found (e.g., vendor’s website or other exact web page location). The Contractor shall ensure that the list is easily accessible by typical users and will be determined at Task Order Award and shall inform the COR and TPOC of the information location.

3.5 Work Location and Meeting Support

The Contractor may choose the location(s) from which to perform the required software development services.

The Contractor shall have the capability to host and conduct virtual meetings in support of the tasking outline herein at the classification levels up to unclassified.

3.6 Security

3.6.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:

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

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

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

d. A statement that access will be limited to a specific government contract (specify contract number).

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

3.6.2 Investigative Requirements

Unclassified: All Contractor personnel must be eligible to perform Non-Critical Sensitive work as defined by SECNAV M-5510.30. All Contractor personnel are required to have a favorably adjudicated Tier-3 investigation from the Office of Personnel Management. The Contractor shall submit a request for personnel security investigation to the Government Security Office. The Government Security Office shall initiate the Contractor's Electronic Questionnaire for Investigations Processing (eQIP)), shall do a preliminary screening of the Contractor's eQIP for suitability and derogatory information. The Contractor employee shall provide all requested information pursuant to the Privacy Act of 1974. The Government Security Office may deny the Contractor access to Government facilities and information and may prohibit the Contractor from performance of sensitive duties for failure to provide requested information or when derogatory or adverse information is present on the Contractor's eQIP, in such cases, the Contractor employee may not perform on the Contract.

The Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified information and to control distribution of controlled unclassified information in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), and SECNAV M-5510.36. All Contractor facilities shall provide an appropriate means of storage for controlled unclassified information and materials. All controlled unclassified information shall be appropriately identified and marked as For Official Use Only in accordance with DoDM 5200.01, Information Security Program: Controlled Unclassified Information (CUI) Volume 4 (enclosure 3).

Controlled Unclassified Information including For Official Use Only and Covered Defense Information (meeting the definition of 48 CFR 252.204–7012(a)) generated and/or provided under this contract shall be marked and safeguarded as specified in DoDM 5200.01 (DoD Information Security Program: Controlled Unclassified Information (CUI)) Vol. 4 (enclosure 3 pages 11-18) available at http://www.dtic.mil/whs/directives/corres/pdf/520001_vol4.pdf. 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):

Distribution Statement D: Distribution authorized to the Department of Defense and U.S. DoD contractors only (Critical Technology) (dated - _______). Other requests shall be referred to: Commander, Naval Air Systems Command, Attn: (Program/User Agency mailing address).

3.6.3 Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization Access Request (SAAR-N)

3.6.3.1 SAAR-N

All contractor personnel requiring access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR-N) Form OPNAV 5239/14 (Rev Sep 2011) on file, and complete required Annual Information Awareness Training. New employees must submit their SAAR forms within thirty (30) days of their first day of work. Instructions for processing the SAAR-N forms are available at: http://www.cnrc.navy.mil/publications/Forms/OPNAV_5239_14_SAAR_N.pdf.

SAAR-N forms shall be submitted to the Contracting Officer’s Representative (COR), Government Technical Point of Contact (TPOC), or to the assigned government Trusted Associate Sponsorship System (TASS) Trusted Associate.

3.6.4 Information Security

This work will be performed at the Contractor's facility. As such, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and controlled unclassified information (CUI) and to control distribution of CUI in accordance with DoD 5220.22-M (NISPOM), and SECNAV M-5510.36.

3.6.4.1 Marking

All information generated by the Contractor shall be properly marked. For Official Use Only information generated and/or provided under this contract shall be marked in accordance with DoDM 5200.01. Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings in accordance with DoDD 5230.24 and program Security Classification Guidance.

3.6.4.2 Public Release for Classified and Unclassified Information Any controlled information pertaining to this contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by appropriate U.S. government authority. Proposed public releases shall be submitted for approval prior to release via the PEO, and through the Public Affairs Office, 47123 Buse Road, RADM William A. Moffett Building, Patuxent River, MD 20670-1547.

3.6.4.3 Loss, Compromise and/or Electronic Spillage of Classified or Controlled Unclassified Information All instances of loss, compromise and electronic spillage of classified or controlled unclassified information shall be reported to the COR, TPOC and Government Security Office within 24 hours of the incident occurring.

4.0 Description of Work to be Performed

The AvPLM IPT leverages Agile Software Development best practices in order to increase productivity, quality, and customer satisfaction through a collaborative implementation approach utilizing management tools such as Jira and Confluence. AvPLM work methodology is organized into three phases of support defined as: Deliverable 1 (D1) - Baseline Scoping, Requirements Definition and Design; Deliverable 2 (D2) - Implementation, User Acceptance Testing, Production Packaging and Deployment; and Deliverable 3 (D3) – Initial Sustainment.

4.1 Phases of Development

Below are detail definitions of the activities and corresponding artifacts that should be completed in each phase:

D1 - Baseline Scoping, Requirements Definition and Design D1 is comprised of the baseline scoping effort, requirements definition, and product design activities to define how requirements will be implemented and is the starting point for each capability delivery effort. D1 includes activities such as requirements workshops, design documentation creation and definition of data migration requirements, as required.

The initial part of the D1 phase is the baseline scoping effort, where requirements are defined and captured with end users, process owners and stakeholders through activities such as requirements workshops and technical interchange meetings. The objective of Requirements Gathering Sessions (RGS) is to obtain inputs and consensus from stakeholders pertaining to the determination and construction of the capability. To achieve this, the RGS shall be facilitated by a joint Government and Contractor team using methods such as creating activity diagrams, use case models and use case narratives to identify the main desired business flow and alternate flows as required.

Requirements are prioritized against the Agile Must Have/Should Have/Could Have/Won’t Have (MoSCoW) framework to finalize a Minimum Viable Product (MVP) for implementation in D2.

The Government prioritized and approved requirements shall be codified into an MVP-baseline requirements specification document generated collaboratively by the product team and approved by the Government. The requirement specification document is owned by the Government Product Manager/Product Owner, and shall outline the features and intended behavior of the capability. The Government owns the development and maintenance of epics and user stories with collaboration from the Contractor as needed.

It is the desire of AvPLM IPT to leverage out-of-the-box capabilities of the vendor software to the fullest extent possible. When customization is deemed required by the Contractor, options that include OOTB capability must be presented to AvPLM IPT to facilitate trade off analysis between OOTB solution and customized capability for final approval. Customization will be identified in the design documentation.

Additional artifacts generated by Contractor in the design portion of D1 including:

1. Enterprise Capability Diagram (a visual representation of Use Cases identifying how requirements relate to each other and to other elements)

1. Enterprise Data Dictionary (At a minimum: Field Names, Definitions, Metadata, and Attributes of Data Elements)

1. Data Mapping (documentation of the data element mapping between a legacy system(s) and the AvPLM Data Model to identify object relationships/attributes/data types)

2. Data validation activities will be a joint Contractor and Government activity or iterative set of activities and may occur in the design phase of D1 and also during the D2 phase

2. These activities will include a health assessment of the data to be migrated as part of D2

1. Technical tasks to support design approach as approved by Government

Artifacts generated in the design phase of D1 shall:

1. Adhere to and apply the MoSCoW framework where appropriate.

2. Shall consider and detail work required to achieve any future expansion beyond the initial MVP and the development required to achieve integrated Enterprise solutions across AvPLM to accommodate all known or potential business use cases. Expansion is defined as the ability for the capability to be scalable beyond a single product organizational structure.

Estimates of the projected scope of the D2 effort will be generated during D1 based on the sizing methodology outlined in Table A below.

Table A. - Sizing Estimation for D2

Size

The Design Review is the final D1 toll gate. Once the Design Review is complete and the Government has approved the design, the Government will change the status of the associated User Stories in Jira from “Design Review” to “Ready for Build”. Completion of the Design Review and subsequent Government approval of the agreed upon design, mark the transition from D1 to D2 for implementation.

Any additional work items identified through means such as discovery after D1 is completed that are outside the scope of the documented MVP will require Government review and determination on how to proceed with input from the Contractor. Items may either be accepted for inclusion during D2 or deferred until after the capability has been fielded, depending on the priority assessed based against the MoSCoW framework, level of effort determination, and impacts against the capability delivery schedule.

As part of the D1 baseline scoping effort and requirements definition, an assessment of data migration activities and the health of the data to be migrated will also be included in the D1 assessment. These data migration activities will include Data profiling and mapping.

The Government will ensure data is provided in accordance with format and condition identified as part of D1 assessment and documented in Data Migration Plan which is generated by the Product Manager/Product Owner in collaboration with the Contractor. Any required staging of data detailed in Data Migration Plan will be completed prior to or as part of migration activity execution in D2. Contractor will perform migration scripting and import as part of D2.

D2 - Implementation, User Acceptance Testing, Production Packaging and Deployment D2 is defined as any software development and configuration activities that culminate in the implementation of the approved D1 baseline capability requirements into a Production environment within the DoD network. D2 activities shall follow Agile Software Development best practices for development of capability. Specific tasking for upcoming Sprints will be defined based on the Product Teams’ prioritization of User Stories in effort backlogs. D2 incorporates this framework in the implementation of both functionality and process.

D2 efforts include:

1. Continued development of technical tasks to support the user stories and artifacts to define how the requirements will be implemented in D2. These technical tasks and artifacts are delivered by the Contractor via management tools such as Confluence and Jira

2. Development and update of all documentation created during D1 including any artifacts identified in Section 3.3 paragraph 1.f. Contractor shall provide and deliver via Confluence

3. Construction of the technical solution, including interfaces with external systems

4. Completion and validation of development tasks to ensure requirement stories are fulfilled via customer Use Cases and the technical solution

5. Written test cases attached to each story to understand and execute the solution from a User standpoint based on Business Use Cases as defined by Government

6. Over-the-shoulder troubleshooting, support, and testing as needed within the Product Team

7. Successful deployment into the Government development and testing environments within the DoD network

8. Successful end-to-end testing, including all functional, integration penetration, and regression testing as appropriate for the complete capability delivery, in Government development and testing environments within the DoD network

9. Any data validation activities, which shall culminate in final review and approval by the Government documented in the form of completed tasks and/or acceptance tests marked “pass” in a management tool such as Jira

10. When necessary to support validation of a design concept, the product team may create a Government-approved limited functionality Proof of Concept (POC) during a sprint for demonstration to gain alignment on capability direction and confirmation of technical achievement

11. Initial user engagement / user adoption activities including initial strategy development

12. User acceptance testing (UAT), with final review and approval documented by the Government in the form of completed tasks and/or acceptance tests marked “pass” in a management tool such as JIRA

13. The packaging of required software code, scripts, or utilities and actual push of that package into the Government Production environment on the DoD network

Functional and integration testing can be an iterative process which could include over-the-shoulder testing events or beta testing events. UAT may be conducted through testing events orchestrated jointly by the Contractor and Government team and/or independent completion of acceptance tests by stakeholders, with results and feedback captured and reported back to the AvPLM team.

UAT is the final toll gate in which the Government makes the decision regarding whether the functionality that has been delivered is ready for promotion into the Production environment on the DoD network. The criteria for making this decision will be the agreement by the Government Stakeholders and AvPLM team that the standard for each requirement in the corresponding Jira Story content has been satisfied, the functionality is consistent with the templates and workflows documented in the quality assurance sessions and the application overall in addition to the specific capability has no significant vulnerabilities. Once UAT has been successfully completed, the Contractor shall provide a detailed installation and configuration guide including screenshots via a tools such as Subversion (SVN).

During any testing events, if blockers, issues, or bugs are encountered that prevent completion of a specific test case, those shall be given priority for resolution and be worked until the test case(s) can be completed with a status of “pass”. The Contractor shall make every effort to provide a response and identify a path forward as soon as possible, and shall not exceed five working (5) days in providing a response to any blocker, critical or issue agreed to by all parties.

The Contractor and the Government shall have a monthly progress review on the status of the capabilities defined for delivery in this SOW within the defined period of performance and review performance to plan. The Government and the Contractor will work collectively to identify and execute means to mitigate risks.

D3 – Initial Sustainment D3 is defined as the initial sustainment support of fielded capabilities for 90 days after completion of D2, including break/fix support of identified issues. It includes Tier 3 and Tier 4 Help Desk support to resolve problems elevated by the Tier 2 Help Desk team with escalation support as required.

All artifacts must be maintained and updated by the in collaboration with the Government POC as each effort progresses to account for any solution or system changes.

D3 initial sustainment support as defined is for the initial scheduled D2 deployment. Deployments of Production capability can be executed in a phased or non-phased manner depending on training and user adoption strategies. In the case of a phased roll-out approach, the 90-day initial sustainment period will start after the first go-live event.

4.2 Detailed Support Requirements

User Stories - Preliminary user stories will be the starting point for the development of software to be provided under this task order. These preliminary user stories are provided only for illustrative purposes, and do not comprise the full scope or detail of the project. NAVAIR expects that the Contractor will work closely with the Product Manager and Product Owner to perform regular user research, and to develop and prioritize a full gamut of user stories as the project progresses. NAVAIR also expects that the Contractor will work closely with the Project Manager, Project Owner and end-users to perform usability testing at regular intervals throughout the development process.

Individual user stories may be modified, added, retracted, or reprioritized by NAVAIR at any time, and NAVAIR expects that the user stories will be continuously refined during the development process. The backlog of user stories will be maintained in JIRA, a web-based project management application that will be provided by NAVAIR. The Contractor will be required to manage and update user stories and development tasks using JIRA.

CLIN

ALE Scope

Previous tasking included mapping existing OOMA PMA Service baseline data fields from Sybase to AvPLM via an ESB connector as well as capturing the OOMA PMA baseline manager server's as-is functions in the AvPLM Service Life Manager module.

CMPI Ph 1

Discrepancy Reporting

X

Support of Business Process Reengineering efforts for Discrepancy Reporting that aligns with an overall approach to discrepancy reporting across NAVAIR and ensures optimization of OOTB Teamcenter capability. D1 tasking includes requirements identification and design artifacts to support future implementation. Processes covered shall include TPDR, TMER, EI, AADR, AIDR and any other associated trouble reports.

BTR/BCR

Support of NAVAIR implementation tasking for Baseline Trouble Report (BTR)/Baseline Change Request (BCR) based on the proposed technical solution derived from requirements and design artifacts and the functioning prototype delivered as part of the D1 phase. Implementation shall include support of production deployment of user acceptance tested capability. Support initial sustainment and break/fix as required by the NAVAIR AvPLM Technical Team.

TMAPS

X

As-needed support for D1 requirements identification and design documentation in support of the TMAPS migration preparation efforts to include Posting Publication and Distribution (PPD).

JEDMICS Data Migration

Customer Onboarding E2-D F/A-18

MQ-4

NGJ/AURA

MQ-25

H-60

VH-92

Provide D1 requirements documentation and design artifacts as well as D2 implementation of supply integration from AvPLM to NOSS.

Provide integration between AvPLM, MRO (IFS) and MEGA systems to enable bi-directional sharing of component data.

OPQ PH3

(Contingent on Teamcenter 13.2 Upgrade)

IDRN Options

(Contingent on Teamcenter 13.2 Upgrade)

(Contingent on Teamcenter 13.2 Upgrade)

5.0 Deliverables and Performance Standards

5.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 A001).

The following chart sets forth the performance standards and quality levels the code and documentation provided by the Contractor must meet, and the methods the Court will use to assess the standard and quality levels of that code and documentation.

Version-controlled NAVAIR repository that comprises product that will remain in the government domain.

Testing to occur in NAVAIR environment.

508 Compliance

6.0 Special Requirements

Personnel Skills and Knowledge Key Personnel – The Contractor must designate both a Project Manager (PM) and a Technical Lead as Key Personnel for this project. The PM will be a direct liaison to the NAVAIR product team, and will be responsible for the supervision and management of all of the Contractor’s personnel. The Technical Lead must have a full understanding of the technical approach to be used by the Contractor’s development team and will be responsible for ensuring that the Contractor’s development team follows that approach.

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

Section F - Deliveries or Performance

SECTION F

Additional Delivery Information for Option CLINs:

OPTION CLINs 0002, 0003, 0004, 0006, 0007, 0009 and 0010: These option CLINs for additional services may be exercised within the Period of Performance (PoP) of the CLIN (1/22/2022 -1/21/2023). The PoP will be updated upon Option Exercise.

DELIVERY INFORMATION

20-JAN-2023

20-JAN-2023

20-JAN-2023

20-JAN-2023

20-JAN-2023

20-JAN-2023

20-JAN-2023

20-JAN-2023

20-JAN-2023

Section G - Contract Administration Data

CLAUSES INCORPORATED BY REFERENCE

CLAUSES INCORPORATED BY FULL TEXT

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

(a) Definitions. As used in this clause—

“Department of Defense Activity Address Code (DoDAAC)” is a six position code that uniquely identifies a unit, activity, or organization.

“Document type” means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

“Local processing office (LPO)” is the office responsible for payment certification when payment certification is done external to the entitlement system.

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

(b) Electronic invoicing. The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation Supplement (DFARS) 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(c) WAWF access. To access WAWF, the Contractor shall—

(1) Have a designated electronic business point of contact in the System for Award Management at https://www.sam.gov; and

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this web site.

(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the “Web Based Training” link on the WAWF home page at https://wawf.eb.mil/.

(e) WAWF methods of document submission. Document submissions may be via web entry, Electronic Data Interchange, or File Transfer Protocol.

(f) WAWF payment instructions. The Contractor shall use the following information when submitting payment requests and receiving reports in WAWF for this contract or task or delivery order:

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

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

(ii) For fixed price line items—

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

(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 item financing, submit a commercial item financing request.

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

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

(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.

Routing Data Table*

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

Section I - Contract Clauses

CLAUSES INCORPORATED BY REFERENCE

CLAUSES INCORPORATED BY FULL TEXT

52.212-4 CONTRACT TERMS AND CONDITIONS--COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (NOV 2021)

(a) Inspection/Acceptance. The Contractor shall only tender for acceptance those items that conform to the requirements of this contract. The Government reserves the right to inspect or test any supplies or services that have been tendered for acceptance. The Government may require repair or replacement of nonconforming supplies or reperformance of nonconforming services at no increase in contract price. If repair/replacement or reperformance will not correct the defects or is not possible, the Government may seek an equitable price reduction or adequate consideration for acceptance of nonconforming supplies or services. The Government must exercise its post-acceptance rights-

(1) Within a reasonable time after the defect was discovered or should have been discovered; and

(2) Before any substantial change occurs in the condition of the item, unless the change is due to the defect in the item.

(b) Assignment. The Contractor or its assignee may assign its rights to receive payment due as a result of performance of this contract to a bank, trust company, or other financing institution, including any Federal lending agency in accordance with the Assignment of Claims Act (31 U.S.C. 3727). However, when a third party makes payment (e.g., use of the Governmentwide commercial purchase card), the Contractor may not assign its rights to receive payment under this contract.

(c) Changes. Changes in the terms and conditions of this contract may be made only by written agreement of the parties.

(d) Disputes. This contract is subject to 41 U.S.C. chapter 71, Contract Disputes. Failure of the parties to this contract to reach agreement on any request for equitable adjustment, claim, appeal or action arising under or relating to this contract shall be a dispute to be resolved in accordance with the clause at Federal Acquisition Regulation (FAR) 52.233-1, Disputes, which is incorporated herein by reference. The Contractor shall proceed diligently with performance of this contract, pending final resolution of any dispute arising under the contract.

(e) Definitions. The clause at FAR 52.202-1, Definitions, is incorporated herein by reference.

(f) Excusable delays. The Contractor shall be liable for default unless nonperformance is caused by an occurrence beyond the reasonable control of the Contractor and without its fault or negligence such as, acts of God or the public enemy, acts of the Government in either its sovereign or contractual capacity, fires, floods, epidemics, quarantine restrictions, strikes, unusually severe weather, and delays of common carriers. The Contractor shall notify the Contracting Officer in writing as soon as it is reasonably possible after the commencement of any excusable delay, setting forth the full particulars in connection therewith, shall remedy such occurrence with all reasonable dispatch, and shall promptly give written notice to the Contracting Officer of the cessation of such occurrence.

(g) Invoice.

(1) The Contractor shall submit an original invoice and three copies (or electronic invoice, if authorized) to the address designated in the contract to receive invoices. An invoice must include--

(i) Name and address of the Contractor;

(ii) Invoice date and number;

(iii) Contract number, line item number and, if applicable, the order number;

(iv) Description, quantity, unit of measure, unit price and extended price of the items delivered;

(v) Shipping number and date of shipment, including the bill of lading number and weight of…