To submit a Receiving Report (RR/DD250) to WAWF, MIL-Comply starts with a shipment created in Shipper, or Labeling.   Much of the data required for a DD250 is gathered in the process of creating Mil-Std-129 labels, especially if UID and RFID are involved.  For shipments that were started in Labeling, Shipper gets involved to add data not found on labels, such as the contract administrative and payment office addresses, and it is required for launching the WAWF submission.

The WAWF transaction process has a few steps, but is generally not all that complicated because it happens transparently.   For the typical shipment

1.Shipment data is translated into an EDI (X12-856) transaction

2.Shipper transmits the transaction to the Mil-Pac VAN

3.The DLA GEX (the Government's VAN) picks up the transaction from the Mil-Pac VAN

a.It is translated from EDI into a WAWF-defined format

4.WAWF attempts to import the shipment

a.WAWF sends you an Import Status email, detailing any errors that were detected

i.If successful, the shipment is processed as if it were entered in manually

ii.If errors occurred, like you forgot the UIDs, the shipment is simply corrected and resubmitted

Depending on your process, you can choose to submit the invoice and any required RFID data at the same time, or after the RR is accepted by DCMA.  It is not unusual for companies to follow up with RFID data after the shipment has been accepted and is heading out the door.

There are two levels of process notification:

•WAWF Import Status emails in response to EDI transactions, indicating successful import of the EDI, or any errors that occurred.  These go to the Organizational Email Address designated by your WAWF GAM.

•WAWF Workflow Notifications are sent to the organizational email, as well as up to nine other addresses that you designate by including them in the transaction.   These can go to other functionaries in your company, your QAR, your customer, etc.  

Access to a DoD-certified Value-Added Network (VAN), such as the Mil-Pac VAN.