There are two central aspects to automating Wide-Area Workflow transactions:

  • Software to collect and organize data for WAWF submission
  • EDI Translation – to transform shipment data into electronic transactions using either:
    • ANSI-X12 (traditional EDI) via a DOD-certified Value-Added Network (VAN)
    • DISA-UDF/FTP via an approved SFTP/SSH account

There are a number of tradeoffs in choosing using of a VAN versus SFTP/SSH, that include:

  • Service cost versus network development / IT overhead
  • Ease of use
  • Need for compatibility with system other than WAWF, such as DLA (DIBBS), UID Registry, DISA, etc.
  • Transaction tracking and archival

Refer to Value-Added Network (VAN) discussion for more information.

WAWF Transactions – Technical Details

The general requirements for submitting transactions with X12-EDI versus SFTP/SSH are described in WAWF Made Easy, with the specific requirements found in these two WAWF documents:

The specific requirements for the standard WAWF transactions are described in the following EDI specifications that are available on the WAWF(/PIEE web site) . The UDF transactions are very similar, albeit with the formatting differently. When referencing these specifications, be sure they are for the current release of WAWF

  • Receiving Reports (DD250)
  • Invoices
  • Combos
  • RFID Pack Updates
  • Cost Vouchers (SF1034/SF1035)
  • Progress Billings (SF1443)
  • Navy Shipbuilding Invoices
  • Attachments (Binary Encoding)

WAWF EDI – Supplemental Technical Information

  • Shelf-Life Codes
  • Unit of Measure Codes
  • WAWF Certificate of Conformance(COC)
  • Shipment Method Codes
  • ANSI X12 Enveloping