Change Request: New System Process

Description: 

The setup of PIEE WAWF for the ELMS user must be performed within PIEE.  1) Often times the APO doesn't know who their WAWF coordinator is, 2) the setup isn't specific enough to prevent non-property book receipts from passing to ELMS causing review / deletion of unwanted Due Ins, and/or 3) it requires constant WAWF configuration maintenance between the Accountable Property Officer (APO), and their WAWF coordinator to tweak the WAWF setting in an attempt to receive the desired receipts.

 Create a WAWF filter process on the ELMS side that will provide the APO a filtering process to filter in / out receipts they want to see as Due Ins in PA and/or Warehouse. Once in place, ELMS will enable 100% of the organization's WAWF receipts to flow to ELMS using the ELMS WAWF filtering rules established by the APO to determine which receipts will become a Due In. ELMS will also provide the APO with a view of those receipts that were filtered out and allowing the user select ones that should have created a Due In to be processed into a Due In.

Mission Critical: This change incorporates additional PIEE WAWF functionality within ELMS.

Benefits: This change will provide improved integration between PIEE GFP and ELMS (APSR).

Frequency: Daily

Users: All ELMS users that use the PIEE WAWF interface.

Change Request: New System Process

Description: 

PIEE GFP is adding functionality that will enable it to report to the material owner's Accountable Property System of Record (APSR) such as condition code changes and disposition actions via the DLMS 947I Inventory Adjustment Transaction Set.  See DEDSO's website for the DLMS 947I Implementation Convention.

Modify ELMS to accept the DLMS 947I from PIEE GFP and update / remove the material from DPAS.  This change will require locating the item in ELMS (PA, WM or MM) and performing the action plus all sub actions to include reporting the financial change should item be financially reportable.

Mission Critical: This change incorporates the additional PIEE GFP functionality within ELMS.

Benefits: This change will provide improved integration between PIEE GFP and ELMS (APSR).

Frequency: Daily

Users: All ELMS user with GFP.

Change Request: Process Improvement

Description: 

Current ELMS processes do not provide the end user with serial number detail within the In-Transit Review process to search for and close intransit shipments with an approval process. When documents are sent to an outside entity that cannot reply transactionally confirming receipt of a shipment, it is the responsibility of the Inventory Manager, when Material Management (ICP) module is being utilized, to close out the intransit record once the Key Supporting Document (KSD) is supplied. The in-transit review process will need to have serial number detail to facilitate the processing and closeout of shipments. Serial number level details are specifically needed for instances where the confirmation quantity does not match the shipment information (Either with KSD or Responses that are short).

The ELMS system shall be enhanced to include a serial number search capability within the “Intransit Review” screen, allowing users to locate and verify specific intransit records. Upon selection of a shipment, all associated serial numbers will be displayed, automatically checked upon first entry. Users will have the ability to uncheck serial numbers not verified as received based on the Key Supporting Document (KSD). A new Stage Code “DS – Discrepant Shipment” is requested to flag and clearly display discrepant serial numbers or quantities. This is a critical enhancement, as current functionality lacks the capability to drill down by serial number for intransit shipment verification and closeout. This feature is necessary to enable Inventory Managers using the ICP module to validate and close shipments when transactional confirmation is not available, ensuring compliance with audit standards. Refer to the attached USMC BRD for additional detail.

Mission Critical: This process allows the user to properly adjudicate and confirm in transit shipments, when the receiving agency does not confirm receipt, or confirms receipt with errors or discrepant quantities.  

Benefits: 

Frequency: Daily

Users: This SCR will support all users of DPAS Material Management, and clean up an issue with the validation of serialized assets when the quantities do not match between what was shipped and the KSD Received.

Change Request: Process Improvement

Description: 

ELMS currently does not allow for Transportation Account Codes (TAC) value set to be added to, updated, or values deleted from within the Material Management (MM) module.  Inventory Manager (IMs) are often provided TAC codes to be used when redistributing inventory to other services or other entities from within the Marine Corps.  The ability to add, update, and delete TAC codes is inherently the responsibility of the IMs using the Material Management module.

The ELMS Material Management (ICP) module shall enable Inventory Managers to Add, Update, and Delete Transportation Account Codes (TACs) within a controlled value set. Once valid TACs are available, managers can select a TAC when generating a 940R Material Release, which will be embedded in the transaction (segment N9, code "TH") and transmitted to the appropriate Remote Storage Activity (RSA) for further distribution. TAC control remains with the ICP when warehouses are linked. Refer to the attached BRD for additional details.

Mission Critical: This process improvement is to allow for the USMC Enterprise Help Desk to make quick updates to the TAC Code to support emerging mission requirements. The DPAS Support help desk ticket to add a TAC Code has been determined pose risks to MARCORLOGCOM Weapon System Managers meeting mission timelines, and hence a User Update Process for this field is required.

Benefits: -Meets MARCORLOGCOM’s business model.

-Ensures Accuracy of TAC Code Submissions to support interface with DLA Transportation Systems.

Frequency: Daily

Users: All MARCORLOGCOM Material Managers, and other DPAS Users who will use this process.

Change Request: New System Process

Description: 

Disconnected ELMS instances currently lack a scalable and reliable method to exchange data with the enterprise system. This limits both the reporting of maintenance activity and the visibility of asset data at the enterprise level, which is critical for decision-making and readiness tracking.

Recommend implementing a Data Warehousing layer to act as a central hub for integrating and synchronizing data from both connected and disconnected ELMS instances. This would be supported by a synchronization process to export, encrypt, and transmit data from a disconnected ELMS instance, then decrypt, validate, and apply updates to an Enterprise ELMS instance. The same process would support downstream updates, such as catalog changes, to disconnected environments.

Mission Critical: This is a new system process involving architecture enhancements, data synchronization routines, and visualization/dashboard capabilities for enterprise-wide maintenance and asset visibility. Note: This SCR is to develop a prototype for 2-way communication between the ELMS enterprise and disconnected copies of ELMS running in their environment.  The success of the prototype will determine whether the functionality will become an operational element of the ELMS environment.

Benefits: The proposed solution supports disconnected operations while enabling timely, secure, and controlled data exchange with the enterprise system. It provides a foundation for enhanced visibility, cross-service analytics, and future expansion while simplifying system-to-system communication and improving the scalability of ELMS architecture..

Frequency: Daily

Users: This SCR should it go to production could impact all users of ELMS.

Improved Data Accuracy – Adding an "Other" option for paint colors ensures that all corrosion coatings can be properly documented, preventing inaccurate or incomplete entries.

Compliance and Readiness – Proper documentation of corrosion assessments supports preventative maintenance efforts, ensuring assets remain in operational condition and reducing unexpected failures.

The inquiry process is used by 100s of users multiple times a day.  

Supports mandatory DRRS reporting and eliminates disparity from users manually entering FMC/NMC data. Strengthens Air Force Enterprise visibility of Readiness posturing.

This change will be applicable to 15,000+ users assigned to Site FH-AFHAF, as well as other agencies or departments that utilize Support Equipment assets in DRRS.

The change will allow the Air Force to effectively manage it's WRM fleet, ensuring correct maintenance actions and proper expenditure of funds. With the delineation of assets within the AvSE MIS, the ultimate impact will be strengthening war readiness posturing and eliminating the risk of misappropriation of funds.

This change will be applicable to 15,000+ users assigned to Site FH-AFHAF, as well as other agencies or departments that manage WRM assets.

Users can handle mass appropriation updates that involve AY or AG without having to request scripts that have the possibility of handling thousands of transactions.  The functionality is already largely in the program, it just needs improved to support different accounting interfaces.

Many users use this program and can use it at any time.  The job runs daily through queued appropriation updates.

LDAC will be able to provide advance Asset Visibility of the stocks/assets are being transfered from the DPAS warehouse to the Army New Equipment Fielding Facility (NEFF) site for distribution. This will aid in the coordination synchronization at these NEFF sites for Units receiving new equipment, facilitates training, and prepares vehicles for installation of weapons platform at these facilities prior to hand off.  Provides end to end In-Transit Visibility of asset the are in the Supply Chain as required by the Presidential Drawdown  Closure of Proposed Sourcing Decisions (PSDs) in DST via DST automated processes.

DST currently has 64,355 active users.  High Priority.  

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.