Description
The current DPAS Warehouse and ICP architecture does not provide for the delineation of property beyond Owning DODAAC and Project Cd.
The Project Cd is somewhat controlled by DoD (several restrictions on what is user controlled) and is limited to 3 characters.
The Owning DODAAC is limited to 6 characters and must be a valid DODAAC when routing transactions through DAAS.
USSOCOM, as a Source of Supply is somewhat unique in that it with the Services' Special Forces to determine equipment requirements and in some instances secures funding from the Services to acquire the equipment.
When this occurs USSOCOM requires the capability to "Segregate" the inventory to know how many are allocated to each special force along with what program the materiel/equipment belongs to.
Reportable Commodity Types will not suffice as the same Stock Nbr exists within multiple programs.
We conferred with EBSO concerning the possibility of expanding the Purpose Code (similar usage, but currently only 1 character), and the Project Code (3 characters) to prevent adding a new attribute.
That was vetoed stating this would impact all DoD users and possibly the current DLMS to MILS conversion.
Recommended
USSOCOM is preparing a DLMS PDC to add a new Industry Cd value to allow for the Segregation of the equipment in inventory.
General concurrence has been given by EBSO for the new Industry Code pending receipt of the PDC and staffing.
USSCOM desires the segregation code to be available for use with all DLMS transactions that flow between ICP and the RSA.
Currently USSOCOM has in excess of 1K Segregation Codes.
The Segregation Cd must be table driven with a user process that is role based to allow for the Add Update and Delete of the values.
The Warehouse and ICP inventories must be Searchable and viewable by Segregation Code.
Screens that are modified to allow for the input/selection of a Segregation Code e.g. Receiving, Update, Issue should provide intellisense as well as a drop-down along with a Browse selector for selecting the correct Segregation Code.
It is recognized that some users of the DPAS application may not want to use the Segregation Code, but USSOCOM believes for its wholesale warehouses it is a must, thus there must be system controls to force the selection of a Segregation Code when applicable.
It is requested that this SCR be developed in concert with the DLMS PDC to ensure the characteristics of the Segregation Code are the same.
Lastly, it is noted that DPAS does not currently have the standard DoD Supply Chain Purpose Code attribute as part of its inventory attributes.
Consideration should be given to adding it as part of this SCR.
Purpose Cd is "Service" defined as will be the Segregation Cd.
The 2 values will mirror each other in functionality, except for it length and actual values.
The benefit of having the Purpose is that all DoD Supply Chain system recognizes the Purpose Cd attribute.
EBSO appears to be planning to limit Segregation Cd to use by USSCOM / DPAS.
Mission Critical
Yes - USSOCOM is unable to implement DPAS to manage the inventory in its Lexington warehouse without this change.
Benefits
With numerous programs and various sources of funding, this permits USSSOCOM and other users of DPAS to segregate its inventory as they need.
Users
This will affect all users of the Warehousing and Materiel Mgmt modules.
Disclaimer | Accessibility