ADC 357 

Att 

2

ATTACHMENT TO ADC 357 

Revision to DLMS SDRs to Add BDN (Supply/SDR) 

1. ORIGINATOR: 

a. Service/Agency: Defense Logistics Agency (DLA)

b. Originator: Defense Distribution Center (DDC) 717-770-4084, DSN 771-4084 - DLA 

proposal for adding the BDN was submitted by DLA DDC (DDC-J3) on behalf of DLA 

Enterprise Kitting Community. 

2. FUNCTIONAL AREA: Supply/Logistics, Quality Notifications (SDR). 

3. REQUESTED CHANGE: 

a. Description of Change: 

1) DLA requires visibility of the BDN in the DS 842 series (report and reply). This 

change supports the medical and industrial kitting community requirements for tracking all 

reported discrepancies by a specific BDN in order to identify kitting assembly production 

impacts. This change applies to SDRs generated during storage activity receipt and may be 

prepared by DSS or on DoD WebSDR. Applicable Document Type Codes are: 

 DSS- Prepared:

8 - Depot originated, depot receipt from non-procurement source (other than RDO) 

9 - Depot originated, vendor delivery to depot 

R - Depot originated, redistribution order receipt 

 Web-Prepared:

N - Storage site receipt, depot shipment (RDO) 

P - Storage site receipt, vendor delivery (new procurement) 

A - Storage site receipt, customer return/other 

2) The BDN was previously added to the following DS (DS are available at: 

http://www.dla.mil/j-6/dlmso/elibrary/TransFormats/140_997.asp):

527D (see 2/N901/090 qualifier 'WO') 

527R (see 2/N901/090 qualifier 'WO') 

650A (see 1/REF01/0300 qualifier 'WO') 

650C (see 1/REF01/0300 qualifier 'WO') 

940R (see 2/N901/040 qualifier '77') 

945A (see 2/N901/040 qualifier '77') 

947I (see 2/N901/040 qualifier 'WO') 

867I (see 2/REF01/30 qualifier 'WO') 

 3) The BDN is defined in the DLMS manual as: 
3

BUILD DIRECTIVE NUMBER (BDN). BDN is a 4-position alphanumeric value used to identify a 

specific build order of a medical/industrial kit. It is system generated at the build manager level and 

serves as the first level identifier. 

 4) Background:  After PDC 329 was published, DLA personnel believed it would not be 

necessary for the BDN added to the SDR, and the PDC was placed on hold for further evaluation. 

Subsequently, it was found that DLA would the BDN for the Material Loss change (SCR BTQ-08-

001) that is being worked. DLA needs the BDN information on the SDR when DSS creates a ZN SDR 

for material quantity discrepancies. This will allow EBS to route the Quality Notification to the correct 

buyer (Procurement person) to ensure appropriate action is taken. It will also allow EBS to track 

discrepancies to ensure all material is accounted for on a Kit Build. 

b. Procedures: Revise DS 842 series as shown in the table below: 

# Location DS 842A/W SDR Report and 842A/R SDR Reply 

BDN Revision

Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 357 to introductory page:

- ADC 357, Revisions to DLMS SDR to Add BDN 

Identifies DLMS 

Changes included in 

the DLMS 

Supplement 

2. 2/REF01/0700 Revise both report and reply formats to add qualifier ‘WO’ and 

DLMS note to identify the BDN.:

WO Work Order Number 

DLMS note: 

1. Use to identify the Build Directive Number (BDN) for 

medical/surgical or other component assembly/kit. 

2. For future consideration, a data maintenance action was 

approved in X12 version 5010. The approved code/name is 

“BDN – Build Directive Number.”

Required 

information for 

kitting functionality. 

 

 c. Alternatives: There is no other systemic alternative to track discrepancies by specific 

assembly builds. 

4. REASON FOR CHANGE: EBS has no capability to see what discrepancies are reported that 

will impact assembly production, thereby missing critical delivery dates to the customer. DLA EBS 

requires the BDN in the DS 842 series in order to monitor and track discrepancies against specific 

assembly builds. 

5. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: EBS kitting mangers and assembly production personnel will be able to 

comply with management inquiries to the status of their specific builds. 
ADC 357 

Att 

4

b. Disadvantages: None identified.

6. IMPACT: 

 a. Systems: Defense Logistics Agency EBS, Distribution Standard System (DSS), and 

DAAS/WebSDR – it is not known if other Components will require this functionality in the future. 

 b. DLMS Data: There are no new data elements established under this change; however, an 

existing element for the BDN is being made available in the SDR transaction. 

 c. Implementation Schedule: Target implementation date is June-July 2011.