If you’ve been reading our blog recently you know that we’ve written pretty extensively on Wide Area Workflow, or WAWF for short. We’ve done this because WAWF is a critical element of DoD vendor compliance. In fact, it’s so essential we’ve built our software with that specifically with this in mind. Now, however, things are changing up a bit. WAWF has been renamed to iRAPT (Invoicing, Receipt, Acceptance and Property Transfer). Change like this has the potential to be a little jarring, so we want to use this post to fully explain what all of this means.
Before we get started, though, take a look at our blog post on the various acronyms associated with iRAPT, WAWF and ultimately UID. It will help clear up a lot of confusion if you’re unfamiliar with the terminology.
In November of last year, e-Business Suit 5.6 was released and thus changed the name of WAWF to iRAPT. Fear not, if you were familiar with WAWF, you’re also familiar with iRAPT. It’s still the secure web-based system used by the DoD for electronic submission of advance shipping data, invoicing, receipt, and acceptance, which allows DoD vendors to submit and track invoices and receipt/acceptance documents. That means that, critically, it allows government personnel to process those invoices in real-time.
iRAPT will manifest itself in a DoD vendor’s compliance efforts most frequently in submitting advance shipping information, including RFID and UID data as well as Invoices. Our blog post on the UID Registry Migrating to WAWF (now iRAPT) explains these processes further, but essentially, this means that iRAPT must be the method in which new acquisition UID and RFID data is submitted to the DoD. This is extremely important as RFID and UID data makes up the backbone of the DoD inventory control methodology and an asset’s lifecycle management.
The most important thing to note is that the name change doesn’t alter the critical nature of the iRAPT application or Odyssey’s position in the process. Because iRAPT Console is the core to what our software does (allowing DoD vendors to stay compliant in a manner that is both efficient and effective), we’ve built the Odyssey program specifically around submitting RFID and UID data to iRAPT by marshaling these unique identifiers, providing their management and incorporation within MIL-STD 129 R and MIL-STD 130 N interior and exterior label compliance.
So fear not, specifically if you use Odyssey’s platform to complete your DoD-related tasks. You’ll still submit your data to iRAPT in the same manner you did for WAWF, which breaks down to a few simple clicks after our software automatically marshals the appropriate RFID and/or UID data. You can rest assured that those processes will remain just as hassle-free as you’ve always known them to be.