02121
|
FLIS Overlay Consumption
|
PA,MU,Warehouse,Materiel Management,FSM,Registry (SA/LW),Enterprise |
Leidos |
New |
Change Request:
Process Improvement
Description:
Within the last year FLIS has updated their data to a new IDV8 XML format for deltas which DPAS has successfully accomidated and receives daily, however, the monthly data overlays which contain additional NSNs from webFLIS are provided via bar (|) delimited lst files for which DPAS does not currently have a parser for outside of the one used for the annual surcharge data.
Recommended:
The DPAS application should be updated to detect these overlay files and consume them into DPAS_FED_LOG consistent with the existing jobs
Mission Critical: The requested change is to provide an automated method for processing overlays which will improve the FLIS data for the DPAS customers.
Benefits:
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
Frequency:
Monthly
Users:
Application Upgrade |
02120
|
SA/LW DLMS Changes (ADC 1244)
|
Warehouse,Materiel Management |
Leidos |
New |
Change Request:
Process Improvement
Description:
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.
Recommended:
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
Mission Critical: The implementation of this SCR will improve materiel activity reporting within the DLMS transactions sets as outlined in ADC 1244B.
Benefits:
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.
Frequency:
Daily
Users:
This change impacts all users that manage SA/LW within DPAS |
02119
|
Purpose Code Functionality
|
Warehouse,Materiel Management |
USMC |
New |
Change Request: Process Improvement
Description:
During the System Acceptance Test (SAT) conducted by MARCORLOGCOM personnel on March 4, 2025, it was discovered that the Purpose Code logic development was done incorrectly and if not corrected will result in a failure point when conducting the MARCORLOGCOM GAP analysis. When an Inventory Control Point (ICP) is being utilized within the ELMS application, full control of assigning the Purpose Code element is to be done by Inventory Managers through use of the Material Management module. Observations during SAT showed the functionality and entry point for Purpose Code was programed to be only accomplished through the Warehouse module. This method of entry should be allowed ONLY when a warehouse DoDAAC is separated from an ICP and is not being managed through the Material Management module. Assignment of the Purpose Code is the inherent responsibility of the Inventory Manager and as such should be accomplished within the Material Management module. Purpose Code is used by the ICP to stratify inventory and is not a warehouse function. This request for modification aligns the business processes required by MARCORLOGCOM WSMC.
Recommended:
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.
Mission Critical: MARCORLOGCOM Inventory Management personnel are required to know, at all times, where managed inventory resides within the Purpose Code stratification. Rolls separation between the Warehousing and Material Management, when it pertains to the entry and management of the Purpose Code value is strictly adhered to in MARCORLOGCOM’s business processes.
Benefits:
• Meets MARCORLOGCOM’s business model.
• Provides 100% accountability of assets.
• Complies with current audit controls.
Frequency:
Hourly
Users:
All system users within the Marine Corps Logistics Command, including Material Managers, Warehouse Managers, and Inventory Control Points, will benefit from these enhancements. |
02118
|
Include Carrier Data in all DLMS 856S/856R/945A Transactions when the shipment involves a commercial carrier
|
PA,Warehouse,Materiel Management |
USMC |
New |
Change Request:
Policy/Regulatory
Description:
Warehouse Module (WM), When the 945A and the 856S transactions are generated, the N1 (Name) Entity Identifier Code of CA (Carrier) needs to be added to the transactions to identify the type of carrier a shipment has been assigned to for the purpose of tracking shipments (Identified as USMC System GAP ID # 11. The N1 Entity Identifier Code “CA” is missing from the to the outputted 945A and 856S transactions. This element provides additional tracking information to the end user.
Recommended:
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/#
Mission Critical: Warehouse Module (WM), When the 945A and the 856S transactions are generated, the N1 (Name) Entity Identifier Code of CA (Carrier) needs to be added to the transactions to identify the type of carrier a shipment has been assigned to for the purpose of tracking shipments.
Benefits:
• Meets MARCORLOGCOM’s business model.
• Provides 100% accountability of assets.
• Complies with current audit controls.
Frequency:
Hourly
Users:
All system users within the Marine Corps Logistics Command, including Material Managers, Warehouse Managers, and Inventory Control Points, will benefit from these enhancements. |
02117
|
UIC management and Data Masking
|
PA,Materiel Management |
FH-AFHAF |
New |
Change Request:
Policy/Regulatory
Description:
Currently the user is required to manually update the Unit Kind Code when, UIC name and APO City when a UIC has been designated as a FAD1. The combination of certain data elements potentially change the classification of the UIC, and could potentially cause a security risk or spillage. Additionally, when users run inquires under the 'Asset Inquires' process there is a potential that certain combinations of data elements could pose a risk.
Recommended:
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.
a. The association of the nomenclature of any single unit or program with the FAD I level designator is classified SECRET.
b. Any compilation of forces, units, activities, projects, or programs associated with the FAD I level designator is classified SECRET.
Mission Critical: AW CJCSI 4110.01F The Service Chiefs are required to develop and implement policies on the use of and oversight of all FAD codes assigned to units. Security Information – United States Only. Classified lists reflecting authorized FAD I requisitioning entities are distributed and maintained by the Joint Staff Directorate for Logistics, J-4/J-44. This list is distributed on a strict “need-to-know-basis.” DoD components and associated agencies are authorized to determine the appropriate distribution within their organizations following standard security procedures. The following classification guidance applies when information is extracted from the lists:
Benefits:
Reduces the risk of spillage of sensitive or classified information on unclassified networks.
Frequency:
Daily
Users:
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. |
02116
|
ICP Role Add
|
Materiel Management |
NSWC |
New |
Change Request:
New Role Design
Description:
Current roles in the ICP do not include an option for a user to only have Read/Update permissions to the Stock Item catalog.
Recommended:
Create a new ICP role, that give a user only Read/Update permission while limiting access to other features in the ICP.
Mission Critical:
Benefits:
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.
Frequency:
Weekly
Users:
All users |
02115
|
Sub Location Tab in WM User Profile
|
Warehouse |
DISA |
New |
Change Request:
New System Process
Description:
When adding equipment to a users profile, the WMS does not allow for a sub location can be added to a users account for any equipment they sign for. Some customers sign for multiple pieces of equipment, and they may forget where the equipment is located. Having this option will provide DISA additional audit readiness for asset visibility.
Recommended:
Build or modify the WMS where all equipment issued out to a customer has a sub location option.
Mission Critical: DOD INSTRUCTION 5000.64 4.2c
Benefits:
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.
Frequency:
Daily
Users:
This would affect all government users assigned to DISA which could be in the in excess of $5K. |
02112
|
Requisition Phase 2 PA Application
|
PA |
Leidos |
New |
Change Request:
Process Improvement
Description:
This SCR documents the development effort to implement the DPAS Requisition Service within the Property Accountability application. The initial implementation of the Requisition Service provided support to the DPAS Maintenance application (SCR 02035).
Recommended:
• 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.
• Requisition Approval process that can be customized for the individual needs of a DPAS PA UIC. The initial Requisitions submitted will go through an Approval process to confirm they have the funding and authorization to submit these Requisitions
• Ability to view Requisition history
• Submit modification requests, cancellation requests, and followups.
• Support the establishment and maintenance of Fund Operating Targets.
• For DAI users, enable Operating Targets to be linked to the DAI Projects / Tasks .
• For DAI users, report commitment, obligations and receipts electronically to DAI.
Mission Critical: The implementation of this SCR is in support users of the property accountability application that have a requirement to requisition items. This will streamline the effort.
Benefits:
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.
Frequency:
Daily
Users:
This change impacts the Air Force as well as other users of the Property Accountability application e.g. USMC. |
02113
|
Labor Hour Process Improvement
|
MU |
USAF: FH-AFHAF |
New |
Change Request:
Policy/Regulatory
Description:
Labor hours are an analytical function to devise the overall cost during the life cycle of an equipment asset. Viewing multiple shops across the enterprise there are currently 1000s of work orders closed out without the maintenance team quantifying their labor. A recommended improvement would be to make it a mandatory field prior to closing out a work order. Previously in IMDS, it was a mandatory field.
Recommended:
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.
Mission Critical: PAD 22-02 signed by the Chief of Staff of the Air Force (CSAF) directs the centralized management of CAvSE at the enterprise level, residing within the 440 SCOS Aviation Support Equipment Management Flight. This change will allow for future data mining actions seeing equipment maintenance hours and for career fields who use the data from DPAS M&U for manpower studies to have accurate information to enable the force to have correct manpower based upon the actual workflow. 00-20-2 para 4.23, 4.26 requires labor documentation.
Benefits:
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.
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 conduct maintenance on their support equipment. |
02114
|
TFSMS to DPAS USMC Allowance Interface
|
PA,Warehouse,Materiel Management |
Leidos |
New |
Change Request:
New System Process
Description:
USMC is transitioning their equipment inventory held for issue as well as the equipment in possession of the operating forces to use DPAS for the management of. USMC utilizes the Total Force Structure Management System "TFSMS" to manage their allowance. DPAS does not currently support an interface with TFSMS. It is a must have to support readiness reporting.
Recommended:
1. Develop the capability to inbound files that contain TFSMS Allowance data via DAAS GEX.
2. Import the TFSMS data and present it the USMC user community with the data along with the on-hand quantities to enable the operating forces and mgmt to know their state of readiness based upon equipment required to on hand.
3. This SCR likely applies to the Materiel Mgmt., Warehouse Mgmt. and Property Accountability, and Requisition service applications of DPAS
Mission Critical: The implementation of this SCR is in support of USMC's DPAS implementation of their operating forces.
Benefits:
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.
Frequency:
Daily
Users:
This change impacts USMC users. |
02111
|
Include CAGE and Mfr Part Nbr data in views
|
Warehouse |
ASAALT |
New |
Change Request:
Process Improvement
Description:
The MFR Part number is not list of the DPAS grids and /or reports that are associated to inventory data. The stock number and specifically the AESIP stock number that is created for MANP records is not physically labeled on the equipment. Since this stock number is created by AESIP and can only been seen in DPAS the users had no way of easily referencing the equipment when the equipment is labeled by MFR part number.
Recommended:
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.
Mission Critical: 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).
Benefits:
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).
Frequency:
Daily
Users:
All users of the DPAS Warehouse Mgmt application. |
02110
|
DD Form 1149 Warehouse Transfer form improvements
|
Warehouse |
ASAALT |
New |
Change Request:
Process Improvement
Description:
When performing a warehouse to warehouse transfer the DD1149 that is generated as a PDF states that the transfer is a "LOCAL DELIVERY". This is not alway the case. This text isn't easily remove or edited. When performing a warehouse to warehouse transfer the users needs to the option to populate the required data elements of the DD 1149. The user needs the option to populate this within DPAS so that the DD 1149 can be regenerated with all data elements at any time.
Recommended:
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.
Mission Critical: Improves the use of the DD Form 1149 for Warehouse transfers
Benefits:
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.
Frequency:
Monthly
Users:
All DPAS users of the Warehouse Transfer process. |
02109
|
Generate a Physical Inventory request upon receipt of a MRO denial
|
Materiel Management |
Leidos |
New |
Change Request:
Process Improvement
Description:
When DPAS Materiel Mgmt. receives a denial response (DLMS 945A) from a RSA that was requested to perform an issue, DPAS sets the CR/DRO/RDO to "plan" for the item manager to take additional action. They have the option to deny, back order, DVD or issue a substitute. What the system is missing is the systematic generation of the request to conduct a physical inventory as a result of the denial.
Recommended:
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.
Mission Critical: The implementation of this SCR is in support of USMC's DPAS implementation (Phase 1a).
Benefits:
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).
Frequency:
Daily
Users:
This change impacts all customers of Materiel Mgmt. and those users of the MRO within Warehouse Mgmt. |
02102
|
Receipt Reversal
|
PA,Materiel Management |
AF: A4/HAF FH-AFHAF |
New |
Change Request:
Policy/Regulatory
Description:
Currently the only transaction that has a reversal process is the 'Disposal' process. In order for the ICP requisition to close out the 'Local Due-in' needs to be processed in PA for the 527R DLMS to be sent from the ICP to the SOS Materiel Receipt Acknowledgment (MRA) to close the requisition. However there have been instances where a receipt was processed in error, which has caused the ICP requisition to remain open. This has caused additional work, that requires DPAS to manually close out the requisition in ICP, and remove the 'Local Due-in' in PA, which neither process sends out the 527R TH MRA. Additionally the SOS also needs to manually close out the requisition on their end, all causing a break in the audit trail.
Recommended:
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'.
Mission Critical: DLMS 4000.25 Vol 2 Chap 10
Benefits:
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.
Frequency:
Daily
Users:
All DAF activities processing receipts for ICP requisitions. |
02108
|
Unit Issue Appt Edit Capability and Cancellation Job Updates
|
Warehouse |
Leidos |
New |
Change Request:
Process Improvement
Description:
DPAS currently does not update an existing appointment if you edit the unit issue request, requested date and time. For unit issue requests that require staging, the appointment immediately goes into an in-progress state, however an appointment date/time does not populate on the appointment grid. Once the appointment is in progress, it triggers a count down for the appointment cancel job. This issue was reported by CSP (Help Ticket 102384 / ADO 132620) during research and testing, it was determined that there were a couple of pieces of code that were missed.
Recommended: The recommended solution that when a unit issue request appointment is created, start_dt_tm and end_dt_tm are set based off the requested date/time in the Unit Issue Request. This would create an Appointment Date/Time to populate in the appointment grid, which would let the appointment cancel job cancel appointments correctly.
Mission Critical: Will improve user functionality for unit issue appointments. The goal is for appointments to accurately receive for the service center.
Benefits:
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.
Frequency:
Daily
Users:
All members that use Unit Issue Request for Appointment processes. |
02107
|
Incorporate FMS fields into Customer Requisition / Materiel Release Order
|
Warehouse,Materiel Management |
Leidos |
New |
Change Request:
Process Improvement
Description:
1. USMC requires the capability to issue materiel in support of the Security Assistance Program. There is a requirement to additional fields to track the issuance of this materiel and in some instances the cost could be different than the DOD Standard Price.
2. The price/cost used is to be the the security assistance agreement price.
2. This SCR incorporates additional fields into Customer Requisition in MM and Materiel Release Order in WM that identify the Security Assistance agreement number.
Recommended:1. Modify CR in MM to provide for the entry of additional Security Assistance data elements and the entry of the agreement price.
2. Modify DLMS 940R and DLMS 945A to enable data exchange of the additional fields / cost between MM/WM and WM/TMS.
3. Modify MRO in WM to display and/or the entry of additional Security Assistance fields.
4. Modify DLMS 856S Shipment Status to contain the additional fields.
5. Modify DD Form 1348 to display additional FMS field and the cost the government has approved for the item.
6. Modify MM In-transit tracking to contain the security assistance fields.
Mission Critical:Supports DLM 4000.25
Supports DLMS 940R, 945A, and 856S Implementation Conventions (ICs)
The implementation of this SCR is in support of USMC's DPAS implementation (Phase 1b).
Benefits: Provides all DPAS customers with the capability to perform manage Security Assistance issues.
Frequency:
Weekly
Users:
This change impacts all customers of Materiel Mgmt. and those users of the MRO within Warehouse Mgmt. |
02106
|
FAST Disposition Reason
|
MU |
AF: VSCOS |
New |
Change Request:
Process Improvement
Description:
Process disconnect within UIC to UIC transfers for FAST Reportable vehicles. System requires FAST Disposition Reason input during transfer, however, the PA and M&U transactions prevent the gaining and losing Maintenance Activity (MA) to complete action. The gaining MA can profile a transferred asset if there is not a work order open for the asset. Normal process is the gaining MA profiles and opens a work order processing asset into new UIC. However, this actions prevents the losing MA inputting a FAST Disposition Reason to drop the asset from losing MA causing asset to remain within AWD status in the losing MA. This presents data integrity issue during FAST reporting as MA cannot input FAST disposition reason.
Recommended: Completing PA UIC to UIC transfers within specific site generates an automatic system action (i.e., M&U) to remove AWD status from losing Maintenance Activity (MA). System must automatically clear the FAST Disposition Reason with ‘N/A – Not Applicable; vehicle is not disposed’ and generate an Open Action (e.g., Homepage display) notifying losing MA asset is no longer within MA and system transferred asset to gaining MA is complete. Additionally, system must generate an Open Action to clear any FAST Disposition Reason for all FAST Reportable assets disposition within PA. Finally, add a column to M&U MAM Search Results for AWD status. This allows another search tool identifying assets are ready for FAST Disposition Reason after PA disposition other than UIC to UIC as this is automatic as recommended above.
Mission Critical: Department of the Air Force Instruction 24-302 VEHICLE MANAGEMENT, Section 8.4 Annual FAST Report
Benefits: Streamline UIC to UIC transfer process by automating some of the steps, while ensuring accurate FAST Reporting by informing maintenance activity that FAST Disposition Reasons are ready/require action.
Frequency:
Daily
Users:
This process improvement benefits DOD agencies and military services on a daily basis. |
02105
|
Work Plan Site Restriction
|
MU |
AF: VSCOS |
New |
Change Request:
Process Improvement
Description:
DPAS flexibility searching and selecting Work Plans causes data integrity issues within DF-VEHS site. Currently, DPAS does not limit search results to within specific site(s) and wide-open searches present all DPAS Work Plans allowing user to select incorrect plan. While Work Plan may look similar, the differences drive data inconsistencies easily preventable with site specific work plans.
Recommended: Limit Work Plans (public work plans) to owning site (i.e., DF-VEHS), or an option within Master Data/Maintenance Program restricting system to site specific Work Plans (e.g., toggle). A toggle or restriction will resolve data integrity isse with reference to Work Plans and eliminate Work Plan selection confusion for all sites utilizing DPAS M&U.
Mission Critical: Department of the Air Force Instruction 24-302 VEHICLE MANAGEMENT, Section 7C Vehicle & Equipment Work Order
Benefits:
Significantly increase data accuracy and streamline user experience with work order creation process.
Frequency:
Daily
Users:
This process improvement benefits DOD agencies and military services on a daily basis. |
02105
|
Work Plan Site Restriction
|
MU |
AF |
New |
Change Request:
Process Improvement
Description:
DPAS flexibility searching and selecting Work Plans causes data integrity issues within DF-VEHS site. Currently, DPAS does not limit search results to within specific site(s) and wide-open searches present all DPAS Work Plans allowing user to select incorrect plan. While Work Plan may look similar, the differences drive data inconsistencies easily preventable with site specific work plans.
Recommended: Limit Work Plans (public work plans) to owning site (i.e., DF-VEHS), or an option within Master Data/Maintenance Program restricting system to site specific Work Plans (e.g., toggle). A toggle or restriction will resolve data integrity isse with reference to Work Plans and eliminate Work Plan selection confusion for all sites utilizing DPAS M&U.
Mission Critical: Department of the Air Force Instruction 24-302 VEHICLE MANAGEMENT, Section 7C Vehicle & Equipment Work Order
Benefits:
Significantly increase data accuracy and streamline user experience with work order creation process.
Frequency:
Daily
Users:
This process improvement benefits DOD agencies and military services on a daily basis. |
02104
|
Incorporate "Mark For" capabilities within Materiel and Warehouse Mgmt. applications
|
Warehouse,Materiel Management |
Leidos |
New |
Change Request: Process Improvement
Description:
USMC requires the capability to enter a "Mark For" Address. Currently DPAS does not support the "Mark For". The proposed solution is to incorporate the entry/selection of a Mark For (RIC/DoDAAC/MAPAD/Text) within CR, DRO and RDO within Materiel Mgmt and within MRO within Warehouse Mgmt.
Recommended:1. Modify CR, DRO, RDO to allow for the entry of the "Mark For". The "Mark For" will be transmitted to the RSA via the DLMS 940R.
2. The Warehouse Mgmt. application will inbound the DLMS 940R and include the Mark For" data in the MRO. When present in the DLMS 940R, do not permit change by warehouse personnel. When absent, allow warehouse personnel to enter a Mark For.
3. Include the "Mark For" data in the Transshipment DLMS 940R request that is transmitted to the TMS for inclusion in the print of the Shipping Label.
4. Incorporate the applicable "Mark For" data in the print of the DD Form 1348.
Mission Critical:Supports MIL-STD-129P
Supports DLM 4000.25
Supports DLMS 940R IC
Benefits: Provides all DPAS customers that utilize Materiel Mgmt., and MRO within Warehouse Mgmt. with the capability to utilize "Mark For".
Frequency:
Hourly
Users:
This change impacts all customers of Materiel Mgmt. and those users of the MRO within Warehouse Mgmt. |
|