Users with the role will have access to additional processes to perform their job.

Anyone with the Regional Customer Assistant role.

Increased productivity and efficiency of the user.

At the very minimum 100+ users

Increased productivity and efficiency of the user.

At the very minimum 40 users

This change will ensure DPAS is consuming all data provided from webFLIS to ensure greater data consistency between NSNs visible from webFLIS and those loaded into DPAS

Application Upgrade

DoD is modifying how the reporting of SA/LW will be responded.  They will be responded through the use of APIs referred to as LLASIE.  Once this process is implemented, the DLMS 140A and DLMS 888A transaction sets will be eliminated.  The required changes are detailed in ADC 1244 and its addendum's. The elimination of the SA/LW transactions requires several changes to the DLMS changes in reporting receipts, gains, losses and turn-ins.   The implementation of LLASIE is covered by DPAS SCR 01988.

This SCR is to cover the business changes. and the DLMS reporting changes required to comply with DLMS 1244B as it relates to the changes outlined in enclosure 5 - DLMS 856S, 856R, and 947I

Ensure DPAS maintains DLMS compliant, and provides for additional materiel reporting that enables the elimination of separate SA/LW reporting outside of the standard supply reporting.  

This change impacts all users that manage SA/LW within DPAS

1.  The system shall provide the Inventory Manager with the capability to enter the Purpose Code element from within the Material Management module.  This capability will be restricted to Inventory Manager role when the Inventory Control Point (ICP) is utilizing the Material Management module.

2.   The system shall be set to NOT allow the Warehouse module to adjust the Purpose Code element when a DoDAAC is assigned to an ICP.

3.   When a new due-in is presented for receipt processing at a Remote Storage Activity (RSA) that has been assigned to Inventory Control Point (ICP), an initial Purpose Code assignment of “A” shall be made.  It is the responsibility of the Inventory Manger to reassign the Purpose Code to it proper location utilizing the Material Management module not the warehousing module. Note:  The reassignment of the Purpose Code is a dynamic process which may require an Inventory Manager to adjust the Purpose Code several times, by serial number over the life cycle of an asset.

4.  The ELMS system shall ensure the LQ (Industry Code) “99”, representing Purpose Code, is present in all required DLMS transactions and represents the correct values as entered in the Material Management module.  In the case of the 947I “Warehouse Inventory Adjustment Advice” transaction, the W19/AD element must be included identifying a change in Purpose Code assignment.

5.  The ELMS system shall ensure all historical transactional records contain the Purpose Code value when assigned.

6.  The ELMS system shall ensure the Purpose Code value is available to be selected in search criteria when users are isolating data in inquiries.

• Meets MARCORLOGCOM’s business model.

• Complies with current audit controls.

All system users within the Marine Corps Logistics Command, including Material Managers, Warehouse Managers, and Inventory Control Points, will benefit from these enhancements.

1.  The system shall include the N1 Entity Identifier Code “CA” providing the additional information on the outputted 945A and 856S transactions.

Format of required data as prescribed by DLMS is as follows:

Transactions Type: 945A and 856S

Example: N1*CA*ARL LOGISTICS*2*AGQC

N1 : Name qualifier

CA:  [Entity Identifier Code] representing the carrier used for the shipment

2: [Identification Code Qualifier] “2” identifies the Standard Carrier Code (SCAC)

AGQC:  Identifies the code represented as specified by the SCAC.  Complete listing can be queried using:   https://scaccodelookup.com/scac-name-lookup/#

• Meets MARCORLOGCOM’s business model.

• Complies with current audit controls.

All system users within the Marine Corps Logistics Command, including Material Managers, Warehouse Managers, and Inventory Control Points, will benefit from these enhancements.

Establish triggers in place to mask the data when the FAD code for a UIC is inserted or updated to a FAD 1. Additionally establish controls within the system that would limit the combination of data elements that could pose a risk and produce an error notifying the user that there is a security risk. The error should not allow the user to bypass the warning if they do not make any adjustments to the combination of data elements. Potentially move the UIC management process out of the APO/Property Administrator profile and move it all to a SIPR environment fro better controls of access.

b. Any compilation of forces, units, activities, projects, or programs associated with the FAD I level designator is classified SECRET.

Reduces the risk of spillage of sensitive or classified information on unclassified networks.

Daily files are sent to ADVANA as the DAF Data Repository where users can access information to build reports.  Currently there are ~1600 users that have access to DPAS PA that could have access to Master Data information.

Create a new ICP role, that give a user only Read/Update permission while limiting access to other features in the ICP.

Allows users to update replenishment information on their own without needing intervention from NSW 41 or APSR Support, while still limiting them to not having the ability to Create and Update other vital information in the ICP.

All users

Build or modify the WMS where all equipment issued out to a customer has a sub location option.

Having the ability to annotate a sub-location will provide DISA the physical location of equipment sub
hand receipted in the WMS module. Will assist DISA with audit readiness.

This would affect all government users assigned to DISA which could be in the in excess of $5K.

• Capability for PA users to submit MILSTRIP / DPAS Warehouse Requisitions. They can submit Requisitions to DPAS Warehouses and submit DLMS compliant orders to external Sources of Supplies.

Streamline and standardize the requisitioning process for DPAS and its Property Accountability customers. It eliminates the need to create a Materiel Mgmt. application environment and maintain user accounts within.  It will also provide electronic reporting of the commitment and obligations to DAI accounting system for customer that utilize that system for financial reporting.

This change impacts the Air Force  as well as other users of the Property Accountability application e.g. USMC.

Make it a mandatory field, where the user cannot close out any work-orders without submitting labor. This should be controlled at the maintenance program configuration where it can be turned on/off for at the site level only to alleviate concerns for agencies that may not require it in the same manner; where aviation support equipment would need it.

This will enable the Air Force to achieve the desired effects in improving overall readiness and warfighter support by having accurate labor hour calculations across the enterprise.

This change will be applicable to 15,000+ users assigned to Site FH-AFHAF, as well as other agencies or departments that conduct maintenance on their support equipment.

1. Develop the capability to inbound files that contain TFSMS Allowance data via DAAS GEX.

3. This SCR likely applies to the Materiel Mgmt., Warehouse Mgmt. and Property Accountability, and Requisition service applications of DPAS

Enable USMC to determine their state of readiness as well as equipment overages / underages.
The number of daily updates to the allowances within TFSMS precludes a manual data reconciliation of change and manual input of the changes to DPAS.

This change impacts USMC users.  

Add the MFR part number(s), MFR name(s), and MFR CAGE(s) as optional data fields to be added to each grid search, grid data view and the reports such as the ICN report that relate to inventory information. These data fields should be optional and should be available for export when saving out a report.

Provides the CAGE and Part Nbr of the actual item (real identifiers) to the user whereas the AESIP Stock Nbr represents the AESIP database row ky which has no relationship to the item.  It also provides more informed information when the Mfr Part Nbr data is more than 15 characters (Stock Nbr max length).

All users of the DPAS Warehouse Mgmt application.

Please remove the words "LOCAL DELIVERY" from the DD 1149 that is generated when performing a warehouse to warehouse transfer.
Provide an additional warehouse to warehouser transfer page (or shipping detail page) containing the following DD 1149 data elements: Ship to - Marked For, Appropriations Data,Requisition Num, Priority, Authority or Purpose, Voucher Number &Date (a and b), Date Shipped, Mode of Shipment, Bill of Lading Number, Air Movement Designator or port reference no. along with the option to populate the container type information with description, size and weight.

This request is mandatory to help the PEO be audit ready. This information should be easily accessible within the APSR. The users should not have to maintain addition shipping details information outside the application being used to document the shipping (transfer) transaction.

All DPAS users of the Warehouse Transfer process.

1. When processing the MRO denial from the RSA, systematically schedule a physical inventory request to the RSA using the key data from the CR/DRO/RDO - Stock Nbr, Condition Code, Purpose Code, and Project Code.
2. Transmit the inventory request via a DLMS 846P.

Provides all DPAS MM customers with the systematic generation of a Physical Inventory request for a MRO denial.   The PI, once conducted will result in the warehouse locating the materiel or making the needed inventory adjustment(s).

This change impacts all customers of Materiel Mgmt. and those users of the MRO within Warehouse Mgmt.

Partially Completed - Release 2025.1.5

Create a reversal process for receipts that will also allow for the stock number/serial number combination to be utilized when reprocessing the receipt with the correct 'Local Due- In'.

This will limit the additional workload of manually closing out a requisition and rejecting the 'Local Due-in'. This will also ensure that the audit trail can be traced from the initial requirement to the receipt acknowledgment (527R TH) back to the SOS to close out the requisition.

All DAF activities processing receipts for ICP requisitions.

By improving the unit issue appointments process, it alleviates undue stress on custodians who currently receive email notification their appointments have been canceled. It also provides the service center with accurate appointment information for planning and staffing purposes.

All members that use Unit Issue Request for Appointment processes.

This change impacts all customers of Materiel Mgmt. and those users of the MRO within Warehouse Mgmt.

This process improvement benefits DOD agencies and military services on a daily basis.