1 Defense Logistics Agency DOD Activity Address Directory (DODAAD) Reengineering

2 Background DODAAD Critical logistics reference repository that supports acquisition, supply, transportation, and financial business processes Applications access DoDAAD data a million+ times daily DoDAAC Six character alpha/numeric intelligent code Identify authorized requisitioners, ship to locations, and bill payers Occurs at least once in Nearly All 5.5B annual Logistics Transactions DoDAAD Reengineering Initiated to address timeliness and accuracy concerns Batch processes for update and distribution of data Planning began in 2001 DoDAAD Reengineering

3 DODAAC/DODAAD Gee Wiz Metrics Critical reference repository for over 40 years 300K active DODAACs 150K are Federal Agency and Contractor DODAACs 104 data elements associated with a DODAAC 900K activity addresses 40 central service points (CSPs) responsible for data accuracy 9K data maintenance actions monthly 100s of supply, transportation, financial & acquisition system access it 1M+ Component application system information accesses daily 500K monthly Web queries from 25K customers DoDAAD Reengineering

4 Reengineering Goals Met Improve data accuracy Key strokes of the authoritative source update the Master DoDAAD Repository real-time. Many discrete fields for line validation and many drop down menus Flexible database to accommodate Component data requirements Improve Timeliness Local application replicate databases controlled by Master DODAAD Near zero access latency DoDAAD Reengineering

5 Next Steps: Deliver Robust Web Query Capability Testing and implementation in February/March 2008 Elimination of the last batch transaction updates Support GSA unique data, last step in eliminating batch updates Sixteen new GSA unique data fields GSA only data maintenance via real-time Web updates Real-time data feeds to GSA from DAASC via data replication Testing and implementation in June/July 2008 Continue efforts to improve data quality Standardization of city names via drop down boxes; Employ USPS ZIP Code tables, insert city & county codes; CAGE Code match to DLIS GAGE master, etc. Determine JOQ data support requirements DoDAAD Reengineering

6 MAPAD Reengineering Military Assistance Program Address Directory (MAPAD) MAPAD Authoritative database for FMS/Grant Aid Resides at DAASC MAPAC Six character alpha/numeric intelligent code 36 data elements related to each MAPAC Allows 13 TACs Reengineering Initiated to address data accuracy and timeliness issues Manual data input by DAASC, batch distribution Planning began in Summer 2007

7 Real-time MAPAD Data Maintenance and Real-time Application System Access Improve data accuracy Key strokes of the authoritative source update the Master DoDAAD Repository real-time. Many discrete fields for line validation and many drop down menus Flexible database to accommodate Component data requirements Improve Timeliness Local application replicate databases controlled by Master DODAAD Near zero access latency MAPAD Reengineering Goals

8 Timeline/Where We’re Going June 2007: Meet with MAPAD stakeholders to define reengineering requirements July 2007: Arrange reengineered MAPAD prototyping with DLA’s Distribution Standard System (DSS) December 2007: Issue MAPAD Functional Requirements Document February 2008– May 2008: DAASC System Development June/July 2008: System Testing with Central Service Points and DSS July CSP Training Completed & MAPAD manual redrafted and staffed August IOC with DSS real-time replication and incorporate MAPAD in DLMS Manual MAPAD Reengineering