U NIQUE ID ENTIFICATION (UID) Wide Area Work Flow (WAWF) Update March 9-10, 2004 James Craig

Background Eliminate the transmission of paper from one step to the next within the DoD contracting process  Problem: Acceptance & payment process is predominately supported by hard copy today  Objective: Create an electronic commerce environment using existing tools and systems DoD Paperless Contracting Initiative * WAWF supports OMB initiatives

WAWF-RA Supports Procurement Requiring Activity Contracting Requisition Vendor RFP Proposal Receiving Report Invoice Contract Goods/ Services DFAS $$$ Vendor’s Bank EFT DOCUMENTS AVAILABLE VIA WAWF-RA

EFT Web, EDI, and FTP “Intake” Wide Area Workflow v3.0.x DFAS Pay Systems DFAS Accounting Systems notices sent to next workflow user DCMA Office Source Inspection & Acceptance Receiving Activity Destination Acceptance Local Processing Document Certification Pay Official Payment Processing Contractor Document Creation Wide Area Workflow EDACCR/ DAASC DCAA Voucher Approval Contracting Officer Financing Acceptance

Tri-Domain Working Group  Purpose –Integrate Logistics functions with Acquisition processes for Receipt and Acceptance to support Accounting and Finance –Establish WAWF as the DoD Enterprise solution vendor invoicing and delivery  Current recommended options A.Perform receipt in logistics system, acceptance in WAWF –Requires process re-engineering at the receiving location –Allows for immediate implementation of WAWF B.Perform Receipt and Acceptance functions within logistics system with updates to WAWF –Must meet same GAO security standards as WAWF –Viable solution will outfit logistics system with a server signer, a PKI for the server C.Perform Receipt and Acceptance in WAWF, update logistics system –Requires enhancements to WAWF  Proposed pilots of B and C

UID Data Capture DoD Apps Vendors UDF Direct Web User Interface Invoice, Receiving Report, UID Data UID XML Invoice, Receiving Report Mark Items with UID Data Elements Shipment Notice Invoice Wide Area Workflow EDI UID Registry Key: New Enhanced No change EDI – Electronic Data Interchange UDF – User Defined Format ACMS BSM CAPS EBIZ IAPS MOCAS MOCAS-RS One Pay SABRS SAMMS

WAWF - Acceptance By UID

UID “Pedigree” Data – Phase 1 End Item Data (15)  UID (Concatenated)  Descriptive Data –UID Type –Issuing Agency Code –Enterprise Identifier –Part Number –Serial Number –Item Description –Unit of measure  Acquisition Data –Contractor DUNS –Contract Number –CLIN/SLIN/ELIN –Price –Acceptance Location Code (identifies acceptor) –Acceptance Date –Ship to code Embedded Items of End Items (10)  UID (Concatenated)  Descriptive Data –UID Data Elements (5) –Item Description –Unit of measure  Parent UID as of delivery date  GFP flag

Interim UID Timeline Jan ‘04May 03 ‘04Jul ‘04Future Fixed Price End Item Cost Type End Item Component s of End Items Data Capture WAWF Other (DID + XML?) Interim Solution 10/04 XML EDI UDF Manual Data held pending interim solution

What’s Next  Registry –Identifying requirements for internal and external data sources –Identifying parameters for registry access and views  WAWF enhancement –Cost type contracts –Integration with logistics systems –Third party shipping  Infrastructure support for –Embedded items –Depot UID submission –Error reconciliation –Container UID content concept –Submission and extraction of UID data in net-centric model WAWF-RA URL =