1. Routing Identifier Code (RIC) to DoD Activity Address Code (DoDAAC)
Ellen Hilert
Defense Logistics Management Standards Office
October 19, 2016

2. RIC to DoDAAC Background
The DoDAAC brief identified that the existing method of using the RIC for identification of organizational entities (e.g., owner, manager, storage activity) is not sustainable due to limited number of available three- position RIC combinations
DLMSO is considering potential options for transitioning RIC-based transaction exchange to DoDAAC-based transaction exchange
Component feedback and preferences requested 

3. Considerations Must retain interoperability among trading partners
There will be a freeze on new/revised Service/ Agency Code alignment for RICs assignment post PDC/ADC 1243 – no additional codes available
Transition to DoDAACs means:
Programming impact on Components and Transaction Services
Changes also imposed on non-DLMS applications, e.g. FLIS
Elimination of RICs assigned without a corresponding DoDAAC (so-called orphan RICs)
Adoption of an alternative approach for creation of internal SAP plant codes (where applicable)

4. Goal – Eliminate Reliance on RICs Within DoD Transaction Processing
Approach 1:
Transaction Services implement DAAS functionality to support:
- Transaction routing by DoDAAC
- Use DoDAAC for all entities currently configured for a RIC:
DMARS WebVLIPS LMARS/MRA Reports
LOTS LDG WebSDR
Authorize early implementation on an intra-Component basis or within pre-coordinated trading partner systems (e.g. Air Force GFM-Accountability Capability Initiative)
Authorize DAAS conversion from RIC to DoDAAC for predesignated early implementers (e.g., by Component or system/COMMRI)

5. Approach 1 (Continued)
Authorize DAAS conversion from DoDAAC to RIC for legacy users. Methodology for conversion:
Components ensure one-to-one relationship - one RIC per DoDAAC
Build conversion table at DAAS to identify a “lead” RIC to be applied when converting from DoDAAC to RIC (applicable to DoDAACs associated with multiple RICs)
Establish mandatory requirement for transition to DoDAACs by DLMS users as soon as feasible based upon DAAS programming plus lead time for Component programming time - target date between January-December 2018

6. Goal: Implement Bilingual DLMS Transactions to Facilitate Transition
Approach 2:
DAAS logic update per Approach 1
Authorize early implementers per Approach 1
Modify DLMS transactions to include multiple occurrences of the Address Loop (N1) requiring the originator to identify organizations by both RIC and DODAAC. RIC universally identified as future “streamlined” data element
Establish mandatory requirement for transition to DoDAACs to align with the full DLMS compliance
Target date for bilingual capability: December 2019
Target date for removal of RICs: December 2021

7. Pros and Cons – Approach 1
Establishes deadline for expedited transition
Supports staggered implementation within restraints imposed by DAAS RIC-DoDAAC conversion
----
Significant DAAS impact for conversion processing
Components must research proposed conversion methodology: one-to-one versus “lead” RIC

8. Pros and Cons – Approach 2
Allows Inter-Component staggered implementation without DAAS impact for conversion
----
Postpones desired end state until full DLMS compliance
Greater impact on Component programming resources
Requires temporary bilingual functionality pending actual transition to DoDAACs
Delays in implementing DLMS may impede transition for selected trading partners currently using legacy formats:
Security Assistance (interface with countries)
Navy retail
Air Force wholesale

9. Way Ahead
Coordination with Transaction Services to assess impact and develop detailed requirements
DAAS modernization for DLMS compliance
Reach consensus on approach
Document via PDC/ADC
Questions?
Component feedback?