DLMSO June 4, 2002

MEMORANDUM FOR RECORD

SUBJECT: Defense Logistics Management Standards (DLMS) Supply Discrepancy Report 

(SDR) Subcommittee Meeting, May 7, 2002

Purpose: The Defense Logistics Management Standards Office (DLMSO) chaired a 

meeting on May 7, 2002 at the HQC for the purpose of refining requirements for completion of 

Phase I of the DoD WebSDR application. DAASC presented a live demonstration of the system 

which accesses requisition history to pre-fill data for the submitter. Discussion addressed 

program improvements and integration of on-line submissions to Components SDR systems. A 

list of attendees is shown at Enclosure 1. 

 

Review of Meeting Topics:

A. DoD WebSDR Overview and Demonstration: Mr. Sean Humenansky, lead 

DAASC programmer, walked the Committee through the various input screens, providing 

background and processes associated with each. DoD WebSDR screenshots are available at: 

https://day2k1.daas.dla.mil/websdr/demo_files/demo.htm. (These will be updated as 

corrections/additions are incorporated.) Specific areas discussed are reflected below. Please note

Component follow-on actions.

? Discrepancy Codes: The DoD WebSDR site allows for selection of three discrepancy codes 

per SDR. DLA, USA, and USN indicated that their current design allows for a maximum of 

two. However, since identification of packaging discrepancies offers a detailed breakdown 

and there is more likelihood that multiples of such discrepancy conditions could occur, there 

was a suggestion that use of the third input box be retained but restricted to the P___ codes. 

No action has been taken as yet. Components should confirm the acceptability of the 

suggested approach. The third code would be passed in SDR transactions using the remarks 

field. 

 

? RIC Flips on the Pre-Fill Logic: Under DLA modernization (BSM) a single Routing Identifier 

Code “SMS” will be used to identify the source of supply (vice currently assigned ICP RICs). 

It is not yet clear what the impact of this will be on the WebSDR identification of the action 

activity. No action has been taken. 
? Requirements for the Activity Identification (To, Initiator). The program currently requires 

that selected address lines be filled. The system will prefill the address based upon the 

customer-entered RIC or DoDAAC. It allows the customer to alter the prefilled information or 

to type in a clear-text address. It is not clear how to handle this information when passing the 

SDR transaction to the action activity. Component suggestions should be provided. Also, 

Components must specify if we need to restrict the current flexibly which lets the customer 

chose to use either RIC or DoDAAC. Currently the application uses the TAC 1 (mailing) 

address. Components should comment if this is not acceptable.

? Transportation Control Number (TCN) and Recognition of Partial Shipments: Currently the 

program does not address multiple depot shipments in response to single MRO (identified by 

the partial indicator in the 16th position of the TCN). Because the inability to recognize such 

shipments is an ongoing problem, the DoD WebSDR application will be modified to improve 

visibility. DLMSO will propose search and display criteria.

? Shipment, Billing, and Receipt Data: Changes and clarification as follows.

? The application will prefill check box for EMALL requisitions based upon presence of 

Distribution Code = 4. Customer will have option to check and will be able to indicate 

payment method by purchase card.

? Shipped/billed Condition Codes (codes and narrative) will be copied to Discrepant 

Condition Codes selection box for ease of selection.

? The application currently allows for item identification by CAGE/part number. It uses 

a break-out according to MILSTRIP reflecting the 5 digit CAGE and a 10 digit part 

number. While this will work for prefilled data, it may not work for customer entries 

where the actual part-number exceeds 10 digits. Components should suggest the 

desired length if they prefer greater flexibility. 

? A new requirement to identify Controlled Inventory Item Code and Flight Critical 

Safety Parts/Critical Safety Item (FSCAP/CSI) was established. This will require 

changes to the FLIS interface, but will be incorporated in near future.

? Incorrect Item Received Data:

? Part number field size for incorrect item identification. Same as above. 

? For item identificationonly one ofthree IDs is needed: NSN or Cage/Part Number

(CAGE may be blank) or Description. A note will be provided to clarify.

? Condition Code selection box will reflect same possible entries as previous screen. 

? Preparing Official Data:

? The application will use a pop-up box to recommend that the customer provide an 

email address for efficient handling of the action activity response but will continue to 

accept a blank email address.
? DAAS will determine feasibility of prefilling the preparing official data based upon 

WebVLIPS ID/Password structure.

? Distribution Depot Packaging Data: This screen provides a strawman for data requirements as 

previously provided by the USA. USA and DLA are to evaluate usefulness and provide 

comments/revisions. 

B. Component/DoD WebSDR Interface: DLA, USA, and USN have begun 

working with DAASC to map SDR data to transactions which will feed directly into internal 

Component SDR applications. The Components will continue to work independently with 

DAASC to develop transaction interfaces. The USAF must provide email addresses to which their 

SDRs should be forwarded. The Air Force expressed concern about the limited scope of the initial 

deployment. They had hoped to be able to integrate the WebSDR application with their receiving 

process. It is unclear how this would be accomplished. 

C. Automated SDR Distribution: A strawman guide delineating the business 

rules for SDR distribution was distributed for Component review and comment. (See Enclosure 

2.) The concept behind this approach is that the customer should not need to understand the 

sometimes confusing rules dictating where to forward their SDR. Instead the rules can be built 

into the system, although the customer will be able to override or supplement the distribution. 

Components should complete their review of the strawman guide and forward corrections and 

additions to DLMSO.

E. WebSDR Option under WebVLIPS: DAASC is exploring the potential 

benefits of controlling access to the DoD WebSDR website though the existing WebVLIPS 

application. WebVLIPS currently offers the user the ability to track logistics transactions from 

inception to completion. The planned approach would leverage WebVLIPS security features and 

consolidate password/login accounts for the customer. However, the restrictive nature of 

WebVLIPS creates a significant drawback to be considered. Many DoD WebSDR customers 

would be low volume, infrequent users. This customer profile is inconsistent with the DoD 

WebVLIPS security concept which locks accounts not used at least once in 45 consecutive days 

and requires that account passwords be changed every 90 days. It is not clear how to reconcile 

this conflict.

F. DAAS On-line History: DAAS retention of on-line data is currently limited 

to 30 days from closeout (e.g. MRA posted). DAAS will extend on-line accessibility to meet 

SDR requirements when clarification of the exact requirement has been provided. Components 

should make recommendations to DLMSO. The on-line history does not currently retain the 

AB_ series Direct Delivery Notice transactions. DAAS will explore the feasibility of including 

these so that the contract information can be accessed for prefilling the SDR and identifying the 

ICP as the appropriate action activity. 

G. Phase II Development: The initial deployment of the DoD WebSDR will 

only address submission of SDRs. The Components all expressed interest in expanding the 
functionality to include capturing disposition/response for customer access and historical 

analysis. This will be pursued at the next meeting.

H. Wrap-up, Next Meeting: 

? The Components and DLMSO continued to voice concern regarding resource expenditures 

on “competing” web applications. However, this review of the DoD WebSDR application 

was very positive and all agreed that the DoD effort should proceed. The long-term goal will 

be to integrate the DoD application into Component systems to become the primary method 

of SDR submission. An alternative goal will be to provide access for smaller DoD agencies 

and contractors.

? Components representatives wishing to obtain access to the test application may do so by 

contacting Ms. Hilert. Subsequent to the meeting, DLA centers were provided 

password/login for independent exploration of the cite.

? This meeting did not address Security Assistance (SA) customer use of the DoD WebSDR 

application. The Defense Security Cooperation Agency (DSCA) has indicated that SDR 

submission will be incorporated in the SA system now under development and the DoD 

application will not be used. The AFSAC office has expressed some interest in the potential 

use of the DoD application for interim support for SA customers depending on timing and 

suitable programming. 

? Ms. Hilert thanked all the participants for their attendance and urged each one to review and 

identify their respective Component requirements for the DoD WebSDR application. The 

attendees suggested quarterly meetings to maintain open communication and help advance 

the development effort. The next meeting will be planned for September 25, 2002. 

/signed/

_________________________

ELLEN HILERT

DoD SDR System Administrator

Supply PRC Chair

APPROVE: /signed/ 

JAMES A. JOHNSON ___________________

Director, DLMSO
Strawman Business Rules for Automated Distribution of SDRs

SOS Discrepancy Type /

Special Criteria

Action Activity Distribution 

Copy *

Distribution

Copy 2

DLA Issuing error or packaging 

deficiency (Discrepancy Codes=C, 

D, L, M, O, P, S, T, W)

Shipping depot if 

known, otherwise 

ICP

DLA DVD

(AB_, Direct Delivery Notice, 

posted)

ICP

DLA Other than above ICP

USA ICP Shipping depot if 

applicable/known

USMC ICP Shipping depot if 

applicable/known

USN Shipping depot if 

applicable/known, 

otherwise ICP

USAF Shipping depot if 

applicable/known, 

otherwise ICP

GSA GSA NCSC DLA depot if 

shipper

Other

Constructed Document No 

(“U” in first position of serial 

number)

ICP

Lateral Redistribution

(A4_ w/Distribution Code 2 or 3)

Depot ICP

Shipments from DRMS

(A0_, RP 4-6 = S9D)

DRMO DRMS

Shipments to DRMS Shipper DRMS ICP

Material Returns ICP Returning activity

National Defense Property, Plant, 

and Equipment (ND PP&E)

(applicable data contents?)

DSCR

Personal Property Shipments

(applicable data contents?)

MTMC

Redistribution (A2_) Depot

* Distribution Copy to Navy SDR application if document number Service = N, R, V