|
02142
|
Inclusion of TFSMS Attribute Data in the Enterprise Catalog
|
PA,MU,Warehouse,Materiel Management |
USMC |
New |
Change Request: New System Process
Description:
The interface being constructed between TFSMS and ELMS was lacking key attributes that are essential in identifying and defining the LIN/TAMCN used by the Marine Corps. Inventory Managers and Equipment Specialists throughout the Marine Corps rely on the additional data being requested to assist in their day to day management of Class VII inventory. The data being asked for should be added to the Enterprise catalog.
Recommended:
1.0 The ELMS system shall include in it interface with the Marine Corps TFSMS system the following key attributes used to minimally assist in identification and defining controlled Class VII inventory:
TAMCN
NATIONAL_STOCK_NUMBER
STANDARDIZATION_CATEGORY_CODE
TAM_STATUS
TAM_STATUS_DATE
ITEM_EXIT_DATE
COLLOQUIAL_NAME
MODEL_NUMBER
DIMENSION_HEIGHT_IN_FEET
DIMENSION_WIDTH_IN_INCHES
DIMENSION_WIDTH_IN_FEET
DIMENSION_LENGTH_IN_FEET DIMENSION_LENGTH_IN_INCHES
DIMENSION_HEIGHT_IN_IN
STAND_PKG_CUBECHES
STD_PKG_LB_WT
1.1 Once the interface is established, the ELMS system shall include all identified attributes in the Enterprise level catalog for the Marine Corps. the primary key to link the information to the catalog is [National_Stock_Number].
1.2 Once the information is included in the Enterprise level catalog, ELMS will make that information available to sub-catalogs (ie, SKO, Stock Item, M&U, Material Management, PA)
1.3 The frequency of the update shall be dependent on the interface agree established between Marine Corps TFSMS system and ELMS.
2.0 NSN SUBSTITUTION: The ELMS system shall provide the inventory Manager, operating in the Material Management module, with the capability to substitute an NSN within a TAMCN group, taking into consideration STANDARDIZATION_CATEGORY_CODE from the TFSMS attributes, which will be added to the Enterprises Catalog.
2.1 In the case where a denial is received at the Material Management module and the document is placed back into a backorder status. ELMS shall provide the Inventory Manager with a capability to substitute and NSN only when the replacement NSN is with the like LIN\TAMCN group. The criteria for the replacement will be strictly controlled by NSNs that have "In Service" (IS), "Plan Allowance" (PL), Disposal Plan (DP) assets available based on the [TAM_STATUS] attribute in the catalog.
2.1.1 At no time shall the system provide the Inventory Manager with the ability to select and alternate asset that is in Achieve (AR) status.
2.2 At the time of substitution, the Inventory Manager shall be provided with the capability to chose a replacement NSN with a different Condition Code and Purpose Code availability.
2.3 ELMS shall be programed to conduct a virtual verification of the selection being made by the Inventory Manager ensuring the warehouse selected, the NSN, quantity, Condition Code and the Purpose Code and support the requested MRO. If the asset is not available matching the specifications identified for the substitution, ELMS will provide the Inventory Manager with an alert and the process will be halted until the error is corrected.
Mission Critical:
Benefits:
- Meets MARCORLOGCOM's business model
- Assists in 100% accountability of assets
- Complies with current audit controls
Frequency: Daily
Users: Affects all USMC users
|
|
02141
|
Inbound Serial Number Enforcement for EDI
|
Materiel Management |
USMC |
New |
Change Request: New System Process
Description:
ELMS must enforce Serialized Item Management (SIM) for designated National Item Identification Numbers (NIINs) across various Enterprise Logistics Management System (ELMS) modules. Data exchanges with external trading partner systems via DLMS EDI/X12 transactions sometimes fail to include required serial numbers for serialized assets. This occurs primarily in, but not limited to:
• 856S (Shipment Notices – Due-In Transactions)
• 945A (Materiel Release – Advice Transactions)
• 947I (Inventory Adjustment Transactions)
The absence of serial numbers in these transactions compromises data integrity and prevents compliance with DoD serialized property management regulations outlined in:
• DoDM 4140.01 (DoD Supply Chain Materiel Management Procedures)
• DLMSO Manuals (DLMS Volume 2, Supply)
• MILSTRAP/DLMS Mapping for EDI transactions
This System Change Request (SCR) proposes a standardized method to detect, report, manage, and resolve these data quality format issues within ELMS. These changes are required to enforce compliance with SIM policies within DPAS modules and ensure accurate logistics accountability and audit readiness.
Recommended:
Implement an automated edit-check mechanism within ELMS to identify inbound DLMS EDI transactions missing required serial numbers, route them to an error handling interface for user remediation, and support transaction reprocessing once corrected. This ensures serialized assets are tracked consistently across the enterprise.
Scope: This change applies to all ELMS modules ingesting DLMS EDI/X12 transactions involving serialized asset movement, including but not limited to:
• Receipt and Due-In processing
• Inventory management and adjustments
• Inbound shipment confirmations
• Materiel Release Orders
Requirements:
1.1. Edit Checks for Serialized Transactions. ELMS shall implement automated validation logic for inbound EDI 856S, 945A, and 947I transactions to detect when a transaction line item is for a NIIN that is marked as serialized but lacks an associated serial number(s).
1.1.2 Enforcement Against Serialized NIIN Catalog. The system shall reference the ELMS NIIN Catalog or Master Item File to determine if an item requires serialized tracking before enforcing serial number validation.
1.1.3. Transaction Error Flagging. Transactions missing required serial numbers shall not be ingested into ELMS records but instead flagged as “Unprocessed” and queued for user intervention in the Interface Queue Manager.
1.1.4. Error Queue Management Dashboard. ELMS shall provide an enhanced dashboard view in the Interface Queue Manager that displays:
• Transaction type (i.e., 856S, 945A, 947I, etc.)
• Originating trading partner
• NIIN and quantity
• Serial number missing status
• Error message: “Serialized NIIN reported without corresponding serial numbers”
1.1.5. Manual Update Interface. The dashboard shall support manual entry of missing serial numbers by the ELMS User after collection from the originating trading partner system.
1.1.6 Audit Trail Capture. The system shall capture all entries made manually to enhance the inbound EDI transactions:
• User ID
• Date/time stamp
• Action performed
• Original vs. updated values
1.1.7 Reprocessing Capability. Once updated with the required serial numbers, the transaction shall be made available for resubmission ingestion using standard processing logic. Successful ingestion will update the transaction status to “Processed” and remove it from the error queue.
1.1.8 System Alerts. ELMS shall provide automated notifications (email or in-system alert) to designated user roles when transactions are flagged as unprocessed due to missing serial numbers.
1.1.9 Metrics and Reporting. The system shall generate periodic reports that include:
• Number of transactions flagged for missing serials
• Time to resolution
• Frequency by trading partner
• NIINs most affected
1.1.10. Configuration Flexibility. Administrators shall be able to update the list of NIINs subject to Serialized Item Management without requiring code changes, using an ELMS catalog or configuration table.
Mission Critical:
Benefits:
- Meets MARCORLOGCOM's business model
- Assists in 100% accountability of assets
- Complies with current audit controls
Frequency: Daily
Users:
|
|
02140
|
Upload of Supporting Documentation to Documents that are Closed
|
PA,Warehouse,Materiel Management |
USMC |
New |
Change Request: New System Process
Description:
ELMS currently does not possess the ability to attach Key Supporting Documents (KSA) (ie. LTI's, signed 1348s, 1149) to a document that is in a closed status. This was discussed during the on site visit to the ELMS LEIDO's facility in early March 2025. This will impact MARCORLOGCOM's ability to answer audit related inquires if not resolved.
Recommended:
1.0 Inventory Managers, using the Material Management (MM) module, shall be provided with the capability to upload an attached Key Supporting Documentation (KSDs) to documents considered closed in ELMS. This is to facility the requirement to extract supporting documentation during an audit evaluation.
1.1 ELMS shall provide the Inventory Manager, the Material Management (MM) module with a capability retrieve attachments from any document recorded in the system.
2.0 Warehouse personnel, using the Warehouse Module (WM) module, shall be provided with the capability to upload an attached Key Supporting Documentation (KSDs) to documents considered closed in ELMS. This is to facility the requirement to extract supporting documentation during an audit evaluation.
2.1 ELMS shall provide warehouse personnel, in the Warehouse Module (WM) module with a capability retrieve attachments associated to the warehouse they are assigned to.
3.0 Personnel using the Property Accountability (PA) module, shall be provided with the capability to upload an attached Key Supporting Documentation (KSDs) to documents considered closed in ELMS. This is to facility the requirement to extract supporting documentation during an audit evaluation.
3.1 ELMS shall provide personnel using the Property Accountability (PA) module with a capability retrieve attachments associated to the account which they are assigned to.
Mission Critical:
Benefits:
- Meets MARCORLOGCOM's business model
- Assists in 100% accountability of assets
- Complies with current audit controls
Frequency: Daily
Users: This change impacts all USMC users
|
|
02139
|
Warehouse Financial Accounting
|
Warehouse,Materiel Management |
MDA |
New |
Change Request: Process Improvement
Description:
MDA has a requirement to manage operating materiel and supplies "OM&S" that are currently being managed using MS Excel spreadsheets. In addition, MDA is requesting DPAS system enhancements to support “actual cost” accounting for OM&S within the warehouse module. On occasion, MDA may have assets (non-capital and capital) that are awaiting transfer / disposition that it would like to have stored in a warehouse. DPAS does not currently support fixed asset accounting or OM&S accounting by actual cost for items that are accounted for in the warehouse. The proposed solution is for DPAS to configure to manage fixed assets within the warehouse module or through integration with a fixed asset module and to be able to electronically report those items to the MDA financial statements supported by Defense Agencies Initiative (DAI).
Recommended:
• By Stock Nbr, permit the user to determine how they want to financially account for the $ value of OM&S (MAC, LAC, ACT). Note: MAC = Moving Average Cost, LAC = Latest Acquisition Cost and ACT = Actual Cost. Actual cost would be limited to serialized OM&S.
• Develop a DAI accounting interface reporting capability to report capital assets and OM&S managed within the warehouse similar to how property accountability performs the financial reporting.
• Enable fixed assets and OM&S to transfer between DPAS modules along with their cost and depreciation. Items transferred between organizations with different catalogs will need to have the valuation set based upon the receiving entity's catalog.
Mission Critical:
The implementation of this SCR is in support of customers of the Warehouse / Materiel Mgmt. modules in support of financial accounting of fixed capital assets and OM&S. Methodologies must be DoD 7000.14R / FASAB / US. Treasury USSGL compliant to support an agency's Financial Improvement Audit Readiness "FIAR".
Benefits:
Supports financial compliance for all assets / supplies accounted for using DPAS regardless of module.
Frequency: Daily
Users: This change impacts all users of the Warehouse module.
|
|
02138
|
Update DRRS reporting for DAF Site-ids
|
PA,MU,Warehouse,FSM |
HQ AF/A4LR |
New |
Change Request: Policy/Regulatory
Description:
With the implementation of SCR 1935, we now require an updated Defense Readiness Reporting System (DRRS) report that will include the Authorization identification code on the property record. Additionally now the the Aviation Support (AvSE) community has completed the implementation of the M&U module we will also need to include the status of the assets that have been profiled in M&U.
Recommended:
Recommend updating the current DRRS report to include all DAF assets and add in the new data elements that are required for reporting
Mission Critical: IAW CJCSI 3401.02B Services are mandated to report DRRS readiness capabilities
Benefits: DAF will be in compliance with CJCSI 3401.02B
Frequency: Weekly
Users: |
|
02137
|
MRP 870M / FTR FTZ response to 180M/FTE -1b
|
Warehouse,Materiel Management |
USMC |
New |
Change Request: Process Improvement
Description:
From MARCORLOGCOM's initial walk-thru in ELMS on the Material Returns Program (MRP) processes, it does not appear the system is in compliance with DoD policy as it relates to the appropriate response to a report of excess. This BRD is to clarify and levee a more comprehensive requirement to ensure the system is providing the necessary information to the Inventory Manager, in the Material Management Module (MM/ICP) to respond to the DLMS 180M/FTE report of excess.
Recommended:
1.0 Material Management (ICP) module required changes to respond to incoming Material Returns Program (MRP) DLMS180M/FTE DLMS transactions in accordance with DLM 4400.25 Vol 2 Chapter 11 (see attachment)
1.1 The ELMS system shall intake all incoming 180M MRP transitions, from DAAS, and route them to the appropriate Owning-RIC also known as the Primary Issue Control Activity (PICA) within the Material Management (MM) module.
1.1.1 Once the 180M transaction has been inbound within the proper ICP management area, in Material Management, the system shall assigned the work to the appropriated Inventory Manager designated by the association of the NSN to the [Program Name].
1.1.2 The system shall provide the Inventory Manager with the capability to respond back to the 180M with the appropriate 870M/FTR transactional response. (see attachment for appropriate response codes)
1.1.3 The system shall provide the Inventory Manager with a set of values representing the FTR response statuses for selection during the 870M transaction build. (See MRP Process Flow attachment)
1.1.3.1 If the Inventory Manager responds with any Status codes begin with "S" (Rejected) the system will created and respond back to the originator via DAAS with an (870M, LQ*0*FTR, LQ*81*S_) noting the selected Status code.
1.1.3.1.2 If the Inventory Manager responds with any Status codes begin with "S" (Rejected), following the transmission of the 870M response, the system will mark the transaction as closed, no further action required. (example of DLMS X12 870M transactions attached)
1.1.3.2 If the Inventory Manager responds with Status codes [TA, TB, TH, TJ] the system will created and respond back to the originator, via DAAS with an (870M, LQ*0*FTR, LQ*81*T_) noting the selected Status code. The 870M will remain open until the equipment is received or the 180M cancellation is received by the originator.
1.1.3.2.1 The system shall provide the Inventory Manager with the ability to Identify the location the equipment will be shipped to ( example: N1*ST**M4*BR4) and the PICA or Owning RIC the asset will be managed by (N1*Z8**M4*MPT).
1.1.3.2.2 The system shall produce a 527D (Due-in/Advance Receipt) notification also known as the Preposition Material Receipt (PMR) directed to the receiving storage point and Owning-RIC as directed in the 870M.
1.1.4 If the system receives a 180M / FTC (Cancellation Request) the original document will be marked closed and retired in ELMS.
2.0 The Warehouse Module (WM) will be prepared to receive the inbound due-in transactions as directed by the 527D PMR.
2.1 The system shall possess the capability to receive 870M/FTL and 856R/FTM transactions coming for the originator via DAAS as directed in the aforementioned 870M/FTR response.
2.1.1 The system shall provide the Inventory Manager, using the Material Management (ICP) module and the receiving warehouse person using the Warehouse Module (WM) with the ability to see all transactions relating to MRP.
2.1.2 The system shall provide the receiving warehouse with a capability to receipt for the inbound shipment using the designated 870M/ FTZ transactions with the appropriate status codes. (See MRP Process Flow attachment)
2.1.2.1 If the shipment is received and all assets are accounted for, the WM module will produce the 870M/FTZ transactions that will be transmitted back to the Owning RIC/ICP via DAAS.
2.1.2.2 The receiving ICP, using the Material Management/ICP module, shall verify the transactions document received and mark the MRP transaction as closed. The 870M/FTZ will record the appropriate elements (870M, LQ*0*FTR, LQ*81*T_) noting the selected Status code.
Mission Critical:
Benefits: Meets MARCORLOGCOM's business model
Assists in 100% accountability of assets
Complies with current audit controls
Frequency: Daily
Users: All users with Material Managers, WH Managers, ICP and all USMC users
|
|
02136
|
Changes to SKO Screens - 1b
|
Warehouse,Materiel Management |
USMC |
New |
Change Request: Compliance Requirement
Description:
During MARCORLOGCOM's evaluation of the Set, Kit, and Outfit (SKO) capability, it was observed that in several location in the process the LIN/TAMCN and or National Stock Number (NSN) of the Parent were missing in search grids and component grids. In addition, the Marine Corps is requesting the ability to add a component type when adding associations for the parent to its components.
Recommended:
1.0 "ICN Inventory Update Inquiry" when selecting the components of a Parent NSN, the system does not display the Parent NSN nor Parent LIN/TAMCN in the SKO summary view. The following requirements are required to gain the required functionality associated with WSMC business processes.
1.1 On the "Inventory Update Inquiry", after selecting a specific serial number known to have a TAMCN, the component Grid did not contain the Parent LIN/TAMCM or the Parent NSN. The system shall be modified to display the Parent LIN/TAMCM and the Parent NSN on the SKO summary view. (see attachment)
1.2 The system shall add ‘Component Type’ drop down containing the below value set on the ‘Component’ tab of the "SKO" Add screen. (see attachment)
a. SSRI (child)
b. SL3
c. SL4
d. DLR
e. Collateral Material
1.2.1 The system shall add the "Component Type" to all search criteria associated to SKO.
1.3 The system shall provide the end user with a capability to search by LIN/TAMCN, This functionality is currently missing from the SKO Add screen. (see attachment)
1.4 The system shall add a criteria for the end user to be able to search by LIN/TAMCN on the “SKO Catalog Landing Page”
1.5 The system shall add a criteria for the end user to be able to search by LIN/TAMCN on the “SKO Catalog Landing Page” Options selection.
1.6 In the “ICN Inquiry” add ‘Component Type’ drop down containing the below value set as a ‘Search Criteria’ Field to the ICN Inquiry Landing Page:
a. SSRI (child)
b. SL3
c. SL4
d. DLR
e. Collateral Material
1.7 On the “SKO Assembly Process Screen”, the system shall add LIN/TAMCN as a default grid option and a search criteria option. (see attachment)
1.8 On the "Kit Assemble" screen, when selecting serial number in the search criteria, the system shall be modified to display the Parent LIN/TAMCN.
1.9 On the "Kit Assemble" screen, when selecting serial number in the search criteria, the system shall be modified to display the Parent LIN/TAMCN in the Kit Details area.
Mission Critical: This is a critical 1.b requirement that must be satisfied prior to MARCORLOGCOM's implementation.
Benefits:
Meets MARCORLOGCOM's business model
Assists in 100% accountability of assets
Complies with current audit controls
Frequency: Daily
Users:
|
|
02135
|
Assignment of Orphan Status and Shipping Translations - 1b
|
Warehouse,Materiel Management |
USMC |
New |
Change Request: Process Improvement
Description:
Currently, it has been observed in ELMS that when Status and Shipping notifications (870S, 856S, 870M/FTL, and 856R/FTM) DLMS transactions are received and there is no due-in present, the intended ICP nor warehouse has the inbound shipment recorded in the system as due in to their location. In short, the transaction exceptions out and no further action is done in ELMS to allow visibility of these transactions without manually hunting them down. This lends itself to frustrated shipments.
Recommended:
1.0 Requirements for dealing with intransit transactions transmitted by DAAS where there are missing due-in leading header transactions records.
1.1 When and inbound transactions indicates an Owning-RIC tied to and ICP within ELMS (MPT) or is intended for one of the Remote Storage Locations (RSAs) connected to an ICP, ELMS shall automatically generate a 527D/DWZ (Preposition Material Receipt (PMR)) record for all inbound DLMS transactions (870S, 856S, 870M/FTL, and 856R/FTM) That does not have a due-in resident in ELMS.
1.1.1 If the inbound transactions has a REF/SE or REF/U3 segment populated identifying serial numbers or IUID. the ELMS system shall record that information as part of the due-in record.
1.1.2 The newly established due-in and follow-on status should be recorded at the Material Management (ICP) level and on the document control records of the intended receiving warehouse as an intransit due-in.
1.1.3 If the NSN identified on the inbound transactions is not loaded to the Stock Item catalog of the RSA where the asset has been shipped to, and the NSN resides on the Enterprise LP catalog, ELMS will automatically load the NSN to the Stock Item catalog for that RSA.
1.2 Upon receipt, ELMS shall record the document as a 527R/D6Z showing that the document was receipted for from a document that had NO due-in recorded.
1.2.1 ELMS shall allow all KSDs to be attached to the document in support of audit requirements.
1.2.2 ELMS shall provide a capability to access and retrieve the completed document both from the Material Management (MM) module and the Warehouse Module (WM).
1.2.3 At the same time ELMS produces the 527R/D6Z DLMS transactions it shall also produce the required 527R/DRA and transmit it back to the originator of the shipment.
2.0 If a 527R/D6_ is received from an external storage point, the system shall build the corresponding 527D/DW_ (Preposition Material Receipt (PMR)) record and allow for the posting of the receipt under the Material Management (MM) module under the associated ICP.
Mission Critical:
Benefits: Meets MARCORLOGCOM's business model
Assists in 100% accountability of assets
Complies with current audit controls
Frequency: Daily
Users: All users with Material Managers, WH Managers, and ICP users |
|
02134
|
Filtering Process for PIEE WAWF Receipt Transactions
|
PA,Warehouse,Materiel Management |
Leidos |
New |
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.
Recommended:
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. |
|
02133
|
PIEE GFP Business Process Improvements
|
PA,Warehouse,Materiel Management |
Leidos |
New |
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.
Recommended:
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. |
|
02132
|
Intransit Document Review and Verification - 1b
|
Materiel Management |
USMC |
New |
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).
Recommended:
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:
-Meets MARCORLOGCOM’s business model.
-Ensures the accurate closeout of in-transit shipments based on Key Supporting Documents received at external RSA's, DLA-DS, or other entities that do not respond appropriately via DLMS Transactions.
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. |
|
02131
|
TAC Code AUD Table - 1b
|
PA,Warehouse,Materiel Management,Enterprise |
USMC |
New |
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.
Recommended:
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 timely processing of shipments in support of Global Force Management and Contingency requirements, that require the quick update of TAC Codes.
-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. |
|
02130
|
ELMS Synchronization of Disconnected Environments
|
PA,MU,Warehouse,Materiel Management |
Leidos |
New |
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.
Recommended:
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. |
|
02129
|
Updating Corrosion Scoring Fields
|
MU |
USAF |
New |
Change Request:
Process Improvement
Description:
TO 35-1-3 CORROSION PREVENTION AND CONTROL, CLEANING, PAINTING, AND MARKING OF USAF SUPPORTEQUIPMENT (SE), Chapter 3 requires new paint and paint scoring to be documented. The current system issue e run into is that DPAS M&U only provides four predefined paint color options for corrosion scoring, which limits flexibility when tracking non-standard coatings. Additionally, the field units are getting confused on scoring documentation with only a Last Painted Date field available. This confusion and lack of documentation makes it difficult to track the most recent corrosion assessment separately from the last painting event. Proposed Improvement:
Add an "Other" option to the corrosion scoring paint color selection, allowing users to account for additional coatings not covered by the existing four options.
Change "Last Paint Date" field to read "Last Scoring Date" to reduce confusion for the field and accurately record the most recent corrosion assessment, improving tracking and maintenance scheduling.
Recommended:
Add an "Other" option to the corrosion scoring paint color selection, allowing users to account for additional coatings not covered by the existing four options.
Change "Last Paint Date" field to read "Last Scoring Date" to reduce confusion for the field and accurately record the most recent corrosion assessment, improving tracking and maintenance scheduling.
Mission Critical:
The current DPAS M&U system only provides four predefined paint color options for corrosion scoring, which does not accommodate all possible coatings. We have received multiple requests to expand these options since the existing selections do not cover all use cases. Adding an "Other" option will allow users to input coatings that do not fit within the preset choices, improving accuracy in tracking corrosion treatments. Additionally, the field units are getting confused on scoring documentation with only a Last Painted Date field available. This confusion and lack of documentation makes it difficult to track the most recent corrosion assessment separately from the last painting event. Changing "Last Paint Date" field to read "Last Scoring Date" to reduce confusion for the field and accurately record the most recent corrosion assessment, improving tracking and maintenance scheduling. These changes will ine up DPAS M&U documentation with requirements in TO 35-1-3 CORROSION PREVENTION AND CONTROL, CLEANING, PAINTING, AND MARKING OF USAF SUPPORTEQUIPMENT (SE), Chapter 3, requiring new paint and paint scoring to be documented and repainting of SE for purely cosmetic reasons is prohibited
Benefits:
Improved Data Accuracy – Adding an "Other" option for paint colors ensures that all corrosion coatings can be properly documented, preventing inaccurate or incomplete entries.
Enhanced Maintenance Tracking – The "Last Scoring Date" field will allow for better differentiation between corrosion assessments and painting events, leading to more precise tracking of maintenance history.
Better Decision-Making – More accurate corrosion data helps maintenance personnel make informed decisions on when additional treatment or repainting is necessary, improving asset longevity.
Increased Flexibility – Expanding paint color options prevents users from being forced into selecting an inaccurate color, making the system more adaptable to real-world scenarios.
Compliance and Readiness – Proper documentation of corrosion assessments supports preventative maintenance efforts, ensuring assets remain in operational condition and reducing unexpected failures.
Frequency:
Daily
Users:
The inquiry process is used by 100s of users multiple times a day. |
|
02128
|
Update DRRS Report File to include MU Data
|
MU |
USAF |
New |
Change Request:
Policy/Regulatory
Description:
Current DPAS data push to DRRS is limited to data from PA and FSM modules, providing on hand and authorized quantities(S ratings). FMC and NMC data is not being fed to DRRS, resulting in inaccurate data for R ratings. Manual data is being entered due to the information not feeding into DRRS.
Recommended:
Update report to incorporate M&U feed for FMC/PMC/NMC rates. Rates should be a roll-up of UIC and Stock Number. Asset data should reflect total number of FMC/PMC/NMC status based on Stock Number and UIC.
Mission Critical:
Per CJCSI 3401_02B, page C-11, section c. Equipment Condition (R-Level), it states units will report the lowest equipment condition level between designated combat-essential equipment and designated support equipment. (Requirement also IAW DAFI's 10-201 & 10-401)
Benefits:
Supports mandatory DRRS reporting and eliminates disparity from users manually entering FMC/NMC data. Strengthens Air Force Enterprise visibility of Readiness posturing.
Frequency:
Weekly
Users:
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. |
|
02127
|
WRM Maintenance Attribute
|
MU |
USAF |
New |
Change Request:
Process Improvement
Description:
MU assets that are in War Readiness Materiel (WRM) status are not identified and segregated from the standard mission support assets. Air Force policy requires WRM assets to be maintained separately and sustained using WRM funds, not O&M funds used to maintain the regular equipment fleet. MU does not provide an indicator alerting users to the assets WRM status, nor the ability to search assets in that status.
Recommended:
Create a maintenance attribute for WRM, similar to the Mission Critical and Nuclear Certified attribute currently available in the Maint Asset Master. WRM attribute indicator should be visible on the work order alerting the user to the assets status. Additionally, the attribute should be available as search criteria in the Maint Asset and Work Order inquiries, as well as be included in the Advana (LIMS/BLADE) data feed.
Mission Critical:
Per DAFI 25-101, War Readiness Materiel, WRM support equipment will be managed in the AF Maint Information System (AvSE MIS), maintained separately from the base support equipment, repaired and maintained using WRM funds.
Benefits:
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.
Frequency:
Daily
Users:
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. |
|
02126
|
Mass Appropriation Update Interface Code Improvements
|
PA |
Leidos |
New |
Change Request:
Process Improvement
Description:
Mass Appropriation Update only supports moving to fund codes that follow the same interface system code. Most Accounting systems require cost elements that do not lend them to an automated transition from one accounting system to another. The AY (no automated interface) and AG (GAFS-R) accounting interface does not require cost elements, thus the Mass Appropriation Update process should permit the user to update the interface system code when the from or to is either AY or AG.
Recommended:
Update the Mass Appropriation Update program to allow users to update DPAS supported accounting interfaces to accounting interface cd of "AY" (No Automated Interface) or AG (GAFS-R) .
Mission Critical:
Mass Appropriation Update currently exists but is limited by its current design. This change will enable users to perform the update without customer support / scripting by the DPAS support teams.
Benefits:
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.
Frequency:
Daily
Users:
Many users use this program and can use it at any time. The job runs daily through queued appropriation updates. |
|
02125
|
LDAC Data Modification
|
PA,Warehouse,Materiel Management |
US Army |
New |
Change Request:
Process Improvement
Description:
LDAC is requesting a modification of the data elements we are currently getting daily from DPAS. These additional data elements are required to start the development / enhancements of the Asset Visibility and Supply Viewer modules in Decision Support Tool (DST). These enhancements were directed by Assistant Secretary of the Army (Acquisition,Logistics, and Technology) ASA(ALT), Headquarters Department of the Army and the Army Materiel Command Commanding General approved on the DST 1 to N List.
Recommended:
LDAC is receiving Unique Item Tracking data daily from DPAS: WE WOULD LIKE TO ADD THESE ADDITIONAL DATA ELEMENTS: Document Identifier Code (DIC)l; Document Number; NSN; Nomenclature; Quantity, LIN; Unit Identification Code (UIC); Unit of Issue; Status Code; Ship to DODAAC; Ship from DODAAC; Estimated Shipment Date; Storage location (SLOC); Ship from RIC; Ship to RIC; Gaining UIC Serial number and Losing UIC.
Mission Critical:
Army Regulation (AR), AR710-2, AR735-5, AR770-2 par 1-6; par 1-13; Decision Support Tool is the Army's authoritative source for the distribution / redistribution of the allocations to the unit identification code (UIC) level of detail. The DST is the Army's collaborative tool used to synchronize the distribution and redistribution of equipment and materiel in accordance with Army priorities. OPERATION ORDER, 24-231, U.S. Army Materiel Command Implements Auditable Presidential Drawdown Authority Article Transfer Accountability and Tracking Processes
Benefits:
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.
Frequency:
Daily
Users:
DST currently has 64,355 active users. High Priority. |
|
02124
|
Regional Customer Assistant Role change
|
Warehouse |
USMC |
New |
Change Request: New Role Design
Description:
USMC uses the DPAS role Regional Customer Assistant quite frequently, and specific Inquiries are not currently visible to users assigned this role.
The Inquiries that appear to be omitted from access include:
• Quality Control / Inspection Results Inquiry
• Appointment Inquiry
• Additional Info Inquiry
• Member Feedback Inquiry
• Stock Item Inventory Inquiry
Recommended:
Add the following inquiries to the Regional Customer Assistant role:
• Quality Control / Inspection Results Inquiry
• Appointment Inquiry
• Additional Info Inquiry
• Member Feedback Inquiry
• Stock Item Inventory Inquiry
• Inventory Adjustment Money Value Gain/Loss Inquiry
Mission Critical:
Adding additional processes to the Regional Customer Assistant role.
Benefits:
Users with the role will have access to additional processes to perform their job.
Frequency:
Daily
Users:
Anyone with the Regional Customer Assistant role. |
|
02123
|
Manufacturer Part Number
|
Warehouse,Materiel Management |
NAWC WOLF |
New |
Change Request:
Process Improvement
Description:
Currently the only place that ties the Manufacturer Part Number to the Stock Number is in the Manufacturer Part Nbr table. It does not cross to the inventory records. This causes the users to first search that table to cross part numbers to stock numbers.
Recommended:
To have the Manufacturer Part number to be added to the inventory record and have it added to the search criteria, inventory reports, and to the grid options.
Mission Critical:
Benefits:
Increased productivity and efficiency of the user.
Frequency:
Daily
Users:
At the very minimum 100+ users |
|
|
Disclaimer | Accessibility
