SDR Transformation Initiative DoD WebSDR Overview

1. SDR Transformation InitiativeDoD WebSDROverview Information Exchange under the DLMS SDR Committee Meeting, Dec 6, 2006

2. Background • What is DoD WebSDR? • WebSDR Concept • Goals of Web SDR • SF 364 • DLMS Supplement to Fed IC

3. What is an SDR? • A Supply Discrepancy Report (SDR) is a tool used to report shipping or packaging discrepancies attributable to the responsibility of the shipper, (including Government sources, contractors/ manufacturers or vendors) and to provide appropriate responses and resolution. • The purpose of this exchange is to determine the cause of such discrepancies, effect corrective action, and prevent recurrence.

4. What is DoD WebSDR? • SDR Transformation Initiative • Transitions current mixed-environment to interoperable DoD Standard • Developed as a DLMS-compliant process, set in motion under OSD Business Initiatives Council in 2004 • WebSDR architecture is based upon a DAAS hub for communication and centralized data management • Eliminates the need for numerous point-to-point communications links • Transaction driven process eliminates the need to re-key SDRs within separate Component systems • Automatic e-mail reply to customer triggered by reply transaction eliminates action activity manual steps to print/mail/fax

5. WebSDR Concept • Phased development • Continuous process improvement beginning at initial operating capability (Feb 2005) • Working toward full DLMS compliant information exchange • Benefits include: • Near real time SDR reporting for immediate identification and more speedy resolution of reported discrepancies • Facilitates interoperability internal and external to DoD • Supports unique item identification and other DoD initiatives • Maximizes the economy, efficiency, effectiveness • Future capture of perfect order fulfillment computations

6. Goals of Web SDR • Quicker Response/Less Effort • Reduces delays resulting from misrouted SDRs or mailed documents • Electronic interface eliminates data entry at action activity • Transaction exchange through logistics hub • ILCOs (using AFSAC pilot, SDR-A) will interface with the DAAS/WebSDR on behalf of FMS customers • DoD Component processing systems will interface with DAAS on a staggered implementation schedule • Facilitated web-based entry available • Auto-fill feature uses DAAS requisition history to populate SDR • Data content targeted to specific discrepant condition • May be used by Military Services/Agencies (individual Service rules may differ) • Contractors may use for discrepancies related to Government Furnished Material

7. Business Object: DLMS 842A Derived from SF 364 • Modernized systems will use business objects to transmit SDRs • DLMS 842A available in X12 and XML format • Includes data fields from the original SF 364 plus more • DLMS codes to support transactional exchange • Component-unique data requirements • Place holders for future enhancements, e.g., UID

8. Business Object: DLMS 842A DLMS Supplement to Fed IC DoD 4000.25-M • Primary business object documentation is the DLMS Supplement (DS): • The DS establishes the DoD standard format for an electronic equivalent of the SF 364/SDR. • The DS provides specific business rules, conditions, and authorized codes necessary for appropriate use of this IC within the DLMS. • Used to replace Component unique formats and paper form.

9. SDR Submittal Process Level 2 drop window identifies conditions within selected category and completes the discrepancy code Drop Down Window

10. Email Distribution • Confirmation copy for Web input • Business rule driven • Transaction driven • Customer response

11. Discussion • Issues • Resource Constraints • System Interfaces • Timeline • Progress to date • DLMS Changes

12. Issues • As a relatively new system, not all Component interfaces have been implemented and WebSDR is experiencing many changes that must be worked with limited programming resources. • New requirements layered on top of incomplete baseline. • Competing priorities among Components.

13. Resource Constraints • WebSDR is currently funded out of the DAASC budget • Limited DAASC resources – available programmer/analyst support insufficient for volume of work • 77 tasks pending • 24 - 36 month backlog, causing delays and frustration among user community • New requirements added on an on-going basis • Initiative forwarded to BTA to request additional funding

14. Systems Implementation Phased implementation beginning with initial operating capability (IOC): • Ability to receive and pass SDR information using transactional exchange or email • Ability to create SDRs via DoD WebSDR (submission, follow-up, change, cancel, reply, request reconsideration) • DoD SDR data base • Limited query capability Phased Implementation of System Interfaces Implemented: __________________Development/testing: - - - - - - - - - - - - - -

15. Timeline

16. Next Steps for WebSDR • Electronic interfaces with Service systems: • AFSAC SDR-A operational; improvements ongoing – expand to other Service ILCOs • Two-way communication with AEPS (Army) • Testing DLMS X12 XML interface with NSDRS (Navy) • Testing DLMS X12 interface with PDREP for DoD-wide distribution of SA quality reports • Complete interface with GSA • Develop management reports and ad hoc queries (better & more functionality) • Associate financial view (debit/credit) with discrepancy report query • Complete implementation of DLMS Changes and ongoing enhancements • Support BTA submission for funding • Prioritize programming requirements