1 / 13

USTRANSCOM

USTRANSCOM. Enhancing DoDAAD Phone Number Capability. Presented to: DoDAAD PRC Fairfax, VA 22031 18 March 2010. Gary Friedrich USTRANSCOM J6-AD 618-229-1236 Gary.Friedrich.ctr@ustranscom.mil. Enhancing DoDAAD Phone Number Capability. Overview Issue

adriel
Download Presentation

USTRANSCOM

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. USTRANSCOM Enhancing DoDAAD Phone Number Capability Presented to: DoDAAD PRC Fairfax, VA 22031 18 March 2010 Gary Friedrich USTRANSCOM J6-AD 618-229-1236 Gary.Friedrich.ctr@ustranscom.mil

  2. Enhancing DoDAAD Phone Number Capability Overview • Issue • Current configuration / limitations • CMOS briefing • USTRANSCOM J5/4 AT 21 Branch needs • Proposed solutions • Summary

  3. Enhancing DoDAAD Phone Number Capability Issue: DoD Activity Address Directory (DoDAAD) users such as CMOS, USTRANSCOM J5/4, and Fusion Center need shipment Point of Contact (POC) information that includes a readily accessible telephone number.

  4. Enhancing DoDAAD Phone Number Capability • Current configuration • Provides only one discrete telephone number field associated with TAC 1, DoDAAC Owner ID. Mandatory per DoD 4000.25-M, Volume 6. December 2009 Snapshot of DoDAACs source from USTRANSCOM’s TRDM showed ~ 35% have a value in the POC phone number field. • Phone numbers are not required for other TACs • TAC address lines 1-4 are freeform text max 35 characters • When entered, freight (Ship-To) POC telephone numbers are included in one of the address lines, typically line 2,3, or 4, without format control

  5. Enhancing DoDAAD Phone Number Capability • Current configuration -- continued • Existing phone numbers are in a wide variety of formats making machine extraction challenging • Using Dataflux against a DoDAAD snapshot from USTRANSCOM’s TRDM we identified 12,414 phone numbers: • Even when extracted, the phone numbers are difficult to enter into a single set format due to Commercial, Overseas, and DSN types, some with extensions, and the variety of user entry formats

  6. Enhancing DoDAAD Phone Number Capability • CMOS Briefing • Mr. Gordon Fitzpatrick • CMOS PMO • HQ 754th ELSG/ILT • MAFB-Gunter Annex, AL 36114 • Gordon.fitzpatrick@us.af.mil

  7. Enhancing DoDAAD Phone Number Capability • USTRANSCOM AT-21 Branch • Mr. Shawn Vosburg • USTC J5J4-LS • Scott AFB, IL 62225 • Shawn.Vosburg@ustranscom.mil • Issue: POC phone numbers are not an available field in the DLA DAASINQ application

  8. Enhancing DoDAAD Phone Number Capability • TCJ5J4-LS Issue -- continued • USTC Fusion Center -- Customer Service • Assist Warfighter to find shipment status and EDD • Action Officers require shipment POC information • Who sent shipment – always the start point • Who is supposed to receive it • When will it be in theater • GTN is current tool to start tracking shipment • GTN TCN query allows drill into a DoDAAC • Takes user to DAASINQ • While address is useful, phone number is much more • useful to Fusion Center Action Officer

  9. Enhancing DoDAAD Phone Number Capability • Short-Term Solution for CMOS, specifically • Using Dataflux, USTC J6-AD extract phone number from TAC 2 address lines, where available • Overwrite current POC phone field with TAC 2/1 phone • If no TAC 2 phone exists, leave current POC phone • Data transfer method to CMOS in negotiation

  10. Enhancing DoDAAD Phone Number Capability • Long-term solution for PRC consideration • Enhance capability of the DoDAAD database • Add two discrete Phone Number fields per TAC – text field, 35-character length, total 7 new phone fields • Commercial • DSN • New DoDAAC creations could require minimum of one phone number entry for Freight and Express TACs – new business rule • Initial phone number data source • Potentially, USTC J6-AD, could provide to DoDAAD a data extract of phone numbers from various TACs keyed on DoDAAC to populate new phone fields

  11. Enhancing DoDAAD Phone Number Capability • Summary • CMOS functionality is being impaired by poor access to relative TAC phone numbers • USTC J5/4 and Fusion Center Action Officers desire telephone numbers to coordinate shipper/receiver actions • Short-term solution for CMOS: USTC J6-AD extract and supply phone numbers from TAC 2, Freight Address

  12. Enhancing DoDAAD Phone Number Capability • Summary -- continued • Long-term, resolve DoDAAD shortfall by enhancing DoDAAD capability with seven new phone fields • Initial phone data source: Extract current phone numbers embedded in TAC address lines 1 – 4 to populate new phone fields (USTC assist) • Require phone number entry for user creations of new Freight and Express (TACs 2 and 4) addresses • Grow availability of TAC phone numbers over long-term

  13. Discussion / Questions

More Related