2

ADC 383

DOD Activity Address Directory (DoDAAD) Container Consolidation Point (CCP) 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

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

b. Originator: DLA J-3312 

2. FUNCTIONAL AREA: DOD Activity Address Directory (DoDAAD) and Supply 

3. REFERENCE: 

a. DoD 4000.25-M, Defense Logistics Management System (DLMS) DLMS 

Volume 6 (DoD Logistics Systems Interoperability Support Services), Chapter 2 

- Department of Defense Activity Address Directory 

4. REQUESTED CHANGE:

a. Description of Change: This change is to implement the use of the Break 

Bulk Point (BBP) and Container Consolidation Point (CCP) data fields in the 

DoDAAD for their intended purpose under DoDAAD reengineering, as 

separate, discrete data fields, rather than as a single, multi-use field. This will 

require phased implementation. 

b. Background: Prior to the reengineering of the DoDAAD, the BBP field was 

used for both the CCP and the BBP. Systems using the DoDAAD data were 

able to identify that the BBP was actually a Consolidation Point based on the 

DoDAAC entered in the BBP field, as there were only two CONUS 

consolidation points (W25N14 is the East Coast Consolidation Point, and 

W62N2A is the West Coast Consolidation Point). The reason for the multi-use 

field was a space limitation. The original DoDAAD was dependent on batch 

processing to update the address information stored on the file. The MILS 

formatted 80-column card record restricted information to only what was 

necessary; hence the multi-use BBP field was used to identify both BBPs and 

CCPs. The multi-use of a single data field for two differing purposes 

complicates application programs and limits a given DoDAAC to either 

identifying a BBP or a CCP, but not both. In the case of many overseas delivery 

locations both a CCP and BBP are essential data to ensure efficient supply 

system support. As a part of DoDAAD reengineering, the DoDAAD was 

designed to handle updates real-time through a web interface, and data output 

was changed from batch transactions to data replication across most servers. 

The reengineered system removed the space restriction associated with the 

fixed-length batch transaction, and was designed to support the CCP as a 
 3

separate and distinct field. 

c. Procedures: The following procedures are approved: 

PHASE 1

1) DAASC load the CCP data using the DODAACs stored in the BBP field. 

If the BBP is W25N14 or SW3123, the CCP should be set to 101 (East 

Coast Consolidation Point – New Cumberland). If the BBP is W62N2A 

or SW3225, the CCP should be set to 301 (West Coast Consolidation 

Point – San Joaquin). STAFFING NOTE: W25N14 and W62N2A are 

“inbound” DoDAACs and indicate inventory being sent to the CCP for 

consolidation. SW3123 and SW3225 are “outbound” DoDAACs and 

indicate inventory leaving the CCP. The “SW” DoDAACs should never 

appear in the BBP or CCP fields of the DoDAAD. 

2) DAASC add logic to populate the CCP field appropriately when the BBP 

is populated with any of the following DoDAACs: W25N14, SW3123, 

W62N2A or SW3225. 

3) DSS validate that the CCP field is being processed as expected. During 

a meeting held in October 2009, DSS reported that the code to process 

CCP data is already in place. If DSS finds CCP data, it will use the CCP 

data. If CCP is blank or null, the program will look to the BBP field for 

consolidation information. 

4) Add the “W” DoDAACs to the CCP drop down display. W25N14 for 

CCP 101 and W62N2A for CCP 301. 

5) Add logic to eDAASINQ to display “W” DoDAACs (W25N14 for CCP 

101 and W62N2A for CCP 301) in parenthesis after the CCP code within 

the Transportation tab. Create a hotlink on eDAASINQ for the “W” 

CCP DoDAACs to take the user to the appropriate DoDAAC when user 

clicks on the link. 

6) Army DoDAAC monitors change the two “W” DoDAACs TAC 2 

addresses to match the information on file at DDC as follows: 

o W25N14: 

CONSOL AND CONTAINERIZATION PT DDSP 

NEW CUMBERLAND, DOOR 135 THRU 168 

BLDG 2001 NORMANDY DRIVE 

NEW CUMBERLAND PA 17070-5001 

o W62N2A: 

XU DEF DIST DEPOT, SAN JOAQUIN 

CCP WHSE 30 

25600 SOUTH CHRISMAN ROAD 

TRACY CA 95304-5000 

7) DAASC block updates to DoDAACs W25N14 and W62N2A. If 

changes to these two DoDAACs are required, a request must be 

submitted jointly by Army/DLA DoDAAC monitors to DAASC. Only 

administrators will be able to change these two DoDAACs. 

8) DAASC add the CCP DoDAAC to outbound DoDAAD replication, if 
 4

requested. STAFFING NOTE: Affected Components should notify 

DAASC if they would like the CCP DoDAAC included in the replicated 

data. 

9) In LOGDRMS, appended to the CONSOLIDATION AND 

CONTAINERIZATION POINT CODE http://www.dla.mil/j6/dlmso/eApplications/LOG.NET/UIL/Log_Qualifiers/lqvqcDetails.aspx

?code=38. Remarks below: 

DoDAACs W25N14 and W62N2A are “inbound” DoDAACs for 

CCP 101 and CCP 301 respectively, and indicate inventory being 

sent to the CCP for consolidation. SW3123 and SW3225 are 

“outbound” DoDAACs for CCP 101 and CCP 301 respectively, and 

indicate inventory leaving the CCP 

10) Components/Agencies submit PDCs for future CCPs, if required. 

PHASE 2

1) Components identify systems other than DSS that are utilizing the BBP 

field for Consolidation Point information, and identify issues with 

conversion along with target conversion dates. 

2) After it has been determined all applicable systems can properly process 

CCP data, Components will remove the four CCP DoDAACs (W25N14, 

SW3123, W62N2A and SW3225) from the BBP field of their 

DoDAACs. DAASC, Air Force and Army DoDAAD update 

applications will develop an edit to prevent these four DoDAACs from 

being entered as BBPs in the future. Air Force and Army will update 

their system to store the CCP data in a separate CCP field to mirror the 

processing currently in place at DAASC. STAFFING NOTE: Removing 

these DoDAACs from the BBP field is dependent on all systems that 

require BBP/CCP information being able to use the CCP field. Any 

Component that cannot accomplish this must so indicate, and indicate if 

future enhancement is planned to accommodate the CCP field with 

projected conversion date. Phase 1 portions of this change may still be 

accomplished, if this step is not possible. 

3) Only the BBP is sent in the transactions used in batch output processing. 

Systems using batch processing should strongly consider switching to 

database-to-database replication prior to DAASC dropping the 

consolidation DoDAACs from the BBP field. Otherwise systems 

dependent on batch transaction will only receive BBP data. STAFFING 

NOTE: Affected Components should comment on this impact. 

d. Alternative. DAASC could develop program logic to pass the CCP DoDAAC 

in the BBP field of the batch output transactions in cases where there is a CCP 

value and the BBP field is null or blank. This option will allow activities 

receiving batch to still get the CCP data, as long as there is no BBP data 

associated with the DoDAAC. STAFFING NOTE: Affected Components should 

comment on this alternative. 
 5

5. REASON FOR CHANGE: The BBP is currently being used as both the Break 

Bulk and Consolidation Points, which prevents identification of both a BBP and a 

CCP. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: This change facilitates identification of both a CCP and a BBP in 

the DoDAAD and implements steps to achieve this. This change will free the 

BBP field for the 26,000 DoDAACs where the BBP is being used for CCP, and 

will allow the Break Bulk Point to be stored for those DoDAACs and for future 

DoDAACs. 

b. Disadvantages: Components relying on batch output transactions will still only 

get the data stored in the BBP field, and will not get CCP information. 

7. IMPACT: 

a. Data Content/Procedures: The BBP data will be used to load the CCP. If the 

BBP is W25N14, the CCP should be set to 101 (East Coast Consolidation 

Point). If the BBP is W62N2A, the CCP should be set to 301 (West Coast 

Consolidation Point). The BBP and CCP fields will be used as separate data 

fields going forward.

b. Unresolved Issues: None noted.

c. Implementation: The implementation will be handled in phases, as discussed 

above. In Phase 1, the CCP field will be loaded using the existing BBP as a 

reference, and systems utilizing CCP data will be modified and/or validated to 

ensure CCP processing is handled correctly. In Phase 2 the BBP field will be 

cleared of the two CCP DoDAACs, and logic will be added to update 

applications to block usage of CCP DoDAACs in the BBP field. 

d. Publication: No change.

e. LOGDRMS. In LOGDRMS, appended to the CONSOLIDATION AND 

CONTAINERIZATION POINT CODE http://www.dla.mil/j6/dlmso/eApplications/LOG.NET/UIL/Log_Qualifiers/lqvqcDetails.aspx?code=

38. Remarks below:

DoDAACs W25N14 and W62N2A are “inbound” DoDAACs for 

CCP 101 and CCP 301 respectively, and indicate inventory being 

sent to the CCP for consolidation. SW3123 and SW3225 are 

“outbound” DoDAACs for CCP 101 and CCP 301 respectively, and 

indicate inventory leaving the CCP. 

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: DoDAAC PRC members should 

identify any savings/cost avoidance associated with this change.