The purpose of this ECP was to provide a process whereby documents that have been awaiting action for longer than 7 days (parameter driven value) will be flagged to the responsible role and the responsible Government Administrator.

This applies to any documents in any workable status (post submission/ resubmission and prior to forwarding to pay office as well as “Make Available for Recall” to government locations) that have been unworked for longer than the system parameter.

A single daily summary notice will be provided to the responsible role using the org email address for each “action” citing all pending documents.

The purpose of this ECP was to provide a “View Only Folder (Contract Number)” folder which allows view only roles to search and view any contract in WAWF as long as they know the exact Contract Number.

View Only access is restricted to Contract Numbers based on a user’s registered/active location codes.

Additionally, the following action roles will also be given access to the ‘View Only Folder (Contract Number)’: Acceptor, Field Inspector, Inspector, Pay Official, CV Approver, Government Property Shipper, Government Receiver, Grant Approver, Local Processing Official (LPO).

Auto View Only Role Demos:

Document	Demo	Doc	Last Updated	Notes
Auto View Only Role			April 2015	This is an overview of the "View Only Folder (Contract Number)" folder that has been added to iRAPT. This folder will allow view only roles to search and contract in iRAPT as long as they know the exact Contract Number.

The purpose of this ECP was to provide the ability for all existing government view only roles to select multiple DoDAACs on the View Only Folder (By DoDAAC) search screen.

Government View Only Roles are:

Documents returned will be limited by the current standard WAWF search parameters on the View Only Folder (By DoDAAC) search screen.

Supervisor View Over Inspection DoDAACs Demo:

Document	Demo	Doc	Last Updated	Notes
Supervisor View Over Inspection DoDAACs			November 2015	This is an overview to describe the addition of the Supervisor View over Inspection DoDAACs. The purpose of this ECP was to provide the ability for all existing government view only roles to select multiple DoDAACs on the View Only Folder search screen.

The purpose of this ECP was for the WAWF system to send an email to Energy POCs when quality attachments are present on Direct Delivery vendor documents.

“Direct Vendor Delivery” is defined as “Destination Delivery” documents where there is no Energy QAR in the process.

The WAWF system will provide an email notification to an Energy POC for all Energy RR documents where the document type is “Destination/Destination”, “Destination/Other” or “Other/Other” and attachments added by the Initiator role are on the document.

Notification will be based upon a single e-mail address provided by DLA Energy. Parsing of the content to the various internal offices will be a DLA Energy responsibility.

The purpose of this ECP was for WAWF to create an automated workflow for an Intra-Governmental (IGT) Performance Evidence document. This document can be based on the current Receiving Report (RR).

WAWF will allow creation of the IGT RR by the Seller via the web or EDI. (Only including XML create)

WAWF will connect with EDA for pre-population of the IGT RR from the PRDS data stored in EDA. EDA will receive a copy of the Approved MIPR from IPP. (Not including EDA pre-population of data)

WAWF will route the IGT RR to the Buyer for acceptance and will also notify the buyer via email to take action. This is currently done today for commercial transactions. The buyer can then accept/reject the IGT RR document either on the web, or externally via XML. (External acceptance only via XML)

• Rejections by the Buyer will trigger a notification to the seller that the document needs to be voided or re-worked.
• Partial acceptance will not be allowed.

WAWF will extract the Accepted IGT RR to GEX for routing to the buyer’s entitlement system and other potential downstream systems.

IGT Receipt and Acceptance Demos:

Document	Demo	Doc	Last Updated	Notes
IGT Registration			November 2015	This is an overview of the Self Registration for IGT Roles. The purpose of this ECP was for iRAPT to create an automated workflow for an Intra-Government (IGT) Performance Evident Document.
IGT Originator			November 2015	This is an overview of the IGT Originator role and the actions this role may perform. This includes a demonstration of an IGT Originator creating an IGT Performance Evidence Receiving Report.
IGT Receiver			November 2015	This is an overview of the IGT Reviewer role and the actions this role may perform. This includes a description of the menu links and how a IGT Reviewer can view their documents.
IGT Administration Console			November 2015	This is an overview of the Administration Console for System Administrators. This includes a description of a new option added to look up IGT Receiving Report Documents.

The purpose of this ECP was to add a Master Test Code table above the commodity level to store the primary data associated with each test and to provide the DLA Admin the capability to identify a test with a Commodity/Sub Commodity.

When the test is added to a Commodity/Sub Commodity by the DLA Admin, the application will populate the default test values for that test from the master test table.

If the DLA Admin modifies the populated default values for a commodity/sub commodity, the application will flag the test as "locally modified.”

Reorganization of Test Code Management Demo:

Document	Demo	Doc	Last Updated	Notes
Reorganization of Test Code Management			June 2016	This is an overview of the reorganization of Test Code Management. This ECP gives the DLA Energy Admin a new menu option for the Energy Test Master List.

The purpose of this ECP was to modify WAWF to provide the capability for pre-population of data from EDA when creating an IGT Receiving Report.

When an IGT Originator creates an IGT Receiving Report, WAWF will check to see if a PRDS is available for the given IGT Order Number and Order Modification Number in EDA.

If the entered IGT Order Number/Modification Number is found in EDA, a list of available CLINs in EDA will be displayed. The PRDS will also contain Schedules. The user will select which Schedules to pre-populate. If the Service, Supplies or FOB matches for all selected Schedules, that field will be pre-populated at the header level.

CLINs that were selected to be pre-populated from EDA will be shown on the Line Item tab, where they may be edited by the Initiator.

IGT Receiving Report Prepop from EDA Demo:

Document	Demo	Doc	Last Updated	Notes
IGT Receiving Report Prepop from EDA			February 2017	This overview describes IGT Prepop from the EDA.

If the data on a contractual WAWF document differs from the data that was on the contract in EDA at the time of document creation:

• A warning will be provided against modifying the data.
• A log will be provided of the changes to the data (visible to downstream users as a means of providing a thorough review).
• Downstream users will be informed (both web and external) that the data on the WAWF document is different than the data on the latest conformed copy of the contract.

The process of pre-population of data from an EDA contract to an WAWF document involves special logic based on business rules specific to the document type, entitlement system, EDA source (synopsis, PDS, etc.), and WAWF edits. For example, a location code will only populate if the location code is valid.

For the purposes of this ECP, data comparisons will be done against the EDA data elements only after applying the same business rules that are used during the process of EDA pre- population during web create of an WAWF document.

The comparison of WAWF data to EDA data will occur when the contract is available in EDA, even if the data was not actually populated to the document from EDA.

Anytime an initiator opens a document to work it from a folder (recall, resubmit, save, etc.), the comparisons will be done against the latest contract data in EDA, which may not necessarily be the data that was pre-populated to the document when it was first created.

If EDA is down at the time the data comparison should be performed, the document will be submitted without the data comparisons.

Tightening Pre-population Business Rules Demo:

Document	Demo	Doc	Last Updated	Notes
Tightening Pre-population Business Rules			December 2017	This is an overview of the Tightening Prepopulation Business Rules. This explains the upcoming comparisons on the Reference Procurement Identifier and Pay Official location code against the data in EDA.