1 / 24

DCMA Wide Area Workflow Presented By: Aristides (Tito) Maldonado DCMA e-Business Directorate

DCMA Wide Area Workflow Presented By: Aristides (Tito) Maldonado DCMA e-Business Directorate December, 2005. DCMA WAWF Use. DCMA WAWF Use. eInvoicing by System. GEX. UID Registry. Vendor. Vendor EDI. Invoice & Receiving Report VIEW. Invoice & Receiving Report. GEX. Vendor FTP.

noel-nielsen
Download Presentation

DCMA Wide Area Workflow Presented By: Aristides (Tito) Maldonado DCMA e-Business Directorate

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DCMA Wide Area Workflow Presented By: Aristides (Tito) Maldonado DCMA e-Business Directorate December, 2005

  2. DCMA WAWF Use

  3. DCMA WAWF Use

  4. eInvoicing by System

  5. GEX UID Registry Vendor Vendor EDI Invoice & Receiving Report VIEW Invoice & Receiving Report GEX Vendor FTP Vendor EDI Vendor Web Invoice & Receiving Report SIGN REJECT PROCESS CAPS One Pay MOCAS BSM JS SAMMS Government Workflow User WAWF EDA CCR View Only Users DAASC Email notices sent to next workflow user WAWF System Architecture

  6. Mark Items w/ IUID Data Elements Or Record Defined IUID w/ innate marks Legacy data submission has relaxed business rules for contract info DoD or Vendor Application IUID XML UDF (Oct 05) IUID XML Manual Web Entry Key: New Existing IUID Registry EDI – Electronic Data Interchange UDF – User Defined Format Legacy and Bulk GFPData Submission

  7. WAWF v. 3.0.9 • Government Furnished Property Phase I – process GFP transfer documentation • Zero Lot Transactions with UID/RFID Requirements • Group Administrator Enhancements – Limits 3rd. Party EDA Access, allows users and GAMS to add attachments to the registration, Archives Users, etc.    • Vendor to create Commercial Invoice from an archived Receiving Report • Service Receiving Reports for MOCAS – Vendors can now submit these transactions  if their CLINS are built as Service Line Items in MOCAS  • Pay Only for MOCAS – WAWF will process  documents for  non DCMA administered contracts paid by MOCAS • DSS Phase II -- Improves WAWF-DSS (DLA) Automation.  Major change involves DLA recording the UID in their system and if UID is duplicated they must put the material in condition code L and resolve the issue rather than accepting.  Jan 16, 2006 Deployment

  8. GEX (1) Contractor EDI Shipping Contractor GFP Ship Notice IUID Registry UID/GPF Info (4) (1) Contractor FTP Contractor EDI (1) (1) Contractor Web (4) UID/GFP Info GEX (2) 856 Due-In Notice (3) FTP Receipt GEX (3) Receipt (3) 856 Receipt WAWF DoD Receiver Paperless GFP and WAWF • Cases include: • Contractor to DoD (shown) • Contractor to Contractor • Contract to Contract • DoD to Contractor

  9. New GFP User Roles

  10. GFP Shipper Create Options

  11. GFP Shipper Screen

  12. GFP Inquiry Screen

  13. WAWF v. 3.0.9 • Government Furnished Property Phase I – process GFP transfer documentation • Zero Lot Transactions with UID/RFID Requirements • Group Administrator Enhancements – Limits 3rd. Party EDA Access, allows users and GAMS to add attachments to the registration, Archives Users, etc.    • Vendor to create Commercial Invoice from an archived Receiving Report • Service Receiving Reports for MOCAS – Vendors can now submit these transactions  if their CLINS are built as Service Line Items in MOCAS  • Pay Only for MOCAS – WAWF will process  documents for  non DCMA administered contracts paid by MOCAS • DSS Phase II -- Improves WAWF-DSS (DLA) Automation.  Major change involves DLA recording the UID in their system and if UID is duplicated they must put the material in condition code L and resolve the issue rather than accepting.  Jan 16, 2006 Deployment

  14. Zero Lot Actual Quantity Zero Lot Receiving Report New Actual Qty Field to Accommodate UID, MILSTRIP and RFID

  15. WAWF v. 3.0.9 • Government Furnished Property Phase I – process GFP transfer documentation • Zero Lot Transactions with UID/RFID Requirements • Group Administrator Enhancements – Limits 3rd. Party EDA Access, allows users and GAMS to add attachments to the registration, Archives Users, etc.    • Vendor to create Commercial Invoice from an archived Receiving Report • Service Receiving Reports for MOCAS – Vendors can now submit these transactions  if their CLINS are built as Service Line Items in MOCAS  • Pay Only for MOCAS – WAWF will process  documents for  non DCMA administered contracts paid by MOCAS • DSS Phase II -- Improves WAWF-DSS (DLA) Automation.  Major change involves DLA recording the UID in their system and if UID is duplicated they must put the material in condition code L and resolve the issue rather than accepting.  Jan 16, 2006 Deployment

  16. Vendor GAM Screen Vendor GAM when Creating Extension Can Set EDA Access to Y or N, Default is N when 309 is deployed for ALL extensions!

  17. WAWF v. 3.0.9 • Government Furnished Property Phase I – process GFP transfer documentation • Zero Lot Transactions with UID/RFID Requirements • Group Administrator Enhancements – Limits 3rd. Party EDA Access, allows users and GAMS to add attachments to the registration, Archives Users, etc.    • Vendor to create Commercial Invoice from an archived Receiving Report • Service Receiving Reports for MOCAS – Vendors can now submit these transactions  if their CLINS are built as Service Line Items in MOCAS  • Pay Only for MOCAS – WAWF will process  documents for  non DCMA administered contracts paid by MOCAS • DSS Phase II -- Improves WAWF-DSS (DLA) Automation.  Major change involves DLA recording the UID in their system and if UID is duplicated they must put the material in condition code L and resolve the issue rather than accepting.    Jan 16, 2006 Deployment

  18. WAWF v. 3.0.9 cont. • Corrects Problem with Invalid Issue By DODAAC from EDA  being generated on EDI or FTP submissions -- uploads to WAWF with a blank Issue By DODAAC and a warning message that this field was ignored. • Miscellaneous Pay Enhancements – USMC Pilot continues • WAWF to send Acknowledgement E-mail to vendor when Pack is Sent on Pack Later Receiving Reports • PIIN/SPIIN Edit  -  Validates the construct of the PIIN/SPIIN preventing errors/rejects at the pay system.  Allows use of GS contract number in the PIIN on MOCAS billings/shipments.  • Capability for IAPS to process EDI transactions WAWF will be deployed, actual processing depends on IAPS upgrade. • PIIN/SPIIN edits and GSA contract no. FLIP. • Batch Signing of Receiving Reports by DCMA.  Expect January 06 Deployment

  19. WAWF v. 3.0.10 Not fully defined yet: • GFP Phase II – Updates DoD Systems • DSS Phase III • Navy Interfaces – Increases Navy destination acceptance • UID Validation Enhancements – Adds UID checks during input to WAWF • E-mail Changes – Standardizes/improves e-mail messages • Non-USMC Miscellaneous Pay – Deploys enhancements that will allow expansion of the Miscellaneous Pay Pilot beyond USMC • Increase number of CLIN/Events to 250   Expect Summer 06 Deployment

  20. Information Sources WAWF Web-Based Training http://www.wawftraining.com WAWF Testing/Hands-on Experiment Site https://wawftraining.eb.mil WAWF Production Site https://wawf.eb.mil E-Invoicing Information http://www.dcma.mil (click on Electronic Invoicing) Unique Identification http://www.acq.osd.mil/dpap/UID Radio Frequency Identification http://www.acq.osd.mil/log/rfid/index.htm

  21. Questions

  22. Back Up

  23. Points of Contact DISA WAWF PMO Bob Baughman CACI WAWF Team Jim Craig Christina Mumm Brian Haller

  24. Registry Data Elements (3.0)

More Related