Loading in 2 Seconds...
Loading in 2 Seconds...
Wide Area Work Flow (WAWF) Update March 9-10, 2004 James Craig email@example.com. DoD Paperless Contracting Initiative. Problem: Acceptance & payment process is predominately supported by hard copy today.
Wide Area Work Flow (WAWF)UpdateMarch 9-10, 2004James Craigjcraig@caci.com
DoD Paperless Contracting Initiative • Problem: Acceptance & payment process is predominately supported by hard copy today Eliminate the transmission of paper from one step to the next within the DoD contracting process • Objective: Create an electronic commerce environment using existing tools and systems * WAWF supports OMB initiatives Background
RFP Contracting Proposal Contract Vendor DFAS Requisition Goods/ Services Receiving Report $$$ Invoice WAWF-RA Supports Procurement Vendor’s Bank EFT Requiring Activity DOCUMENTS AVAILABLE VIA WAWF-RA
Contractor Contracting Officer Document Creation Financing Acceptance DCAA Voucher Approval DFAS Accounting Systems DFAS Pay Systems CCR/DAASC EDA DCMA Office Source Inspection & Acceptance Wide Area Workflow Receiving Activity Destination Acceptance Local Processing Pay Official Document Certification Payment Processing EFT Wide Area Workflow v3.0.x Web, EDI, and FTP “Intake” Email notices sent to next workflow user
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 • Perform receipt in logistics system, acceptance in WAWF • Requires process re-engineering at the receiving location • Allows for immediate implementation of WAWF • 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 • Perform Receipt and Acceptance in WAWF, update logistics system • Requires enhancements to WAWF • Proposed pilots of B and C
Wide Area Workflow Key: New Enhanced No change UID Data Capture Invoice, Receiving Report, UID Data Invoice, Receiving Report DoD Apps MOCAS MOCAS-RS One Pay SABRS SAMMS ACMS BSM CAPS EBIZ IAPS EDI UID XML UDF Direct Web User Interface Vendors Mark Items with UID Data Elements Shipment Notice Invoice UID Registry EDI – Electronic Data Interchange UDF – User Defined Format
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 UID “Pedigree” Data – Phase 1
Jan ‘04 May 03 ‘04 Jul ‘04 Future Data Capture Fixed Price End Item Manual WAWF XML 10/04 Interim Solution Data held pending interim solution WAWF Cost Type End Item EDI Other (DID + XML?) Components of End Items UDF Interim UID Timeline
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 = https://wawf.eb.mil