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 |
02122
|
Multi line-item Acquisition data form
|
Materiel Management |
NAWC WOLF |
New |
Change Request:
Process Improvement
Description:
Currently can only and single items with the existing Leidos Single line-item Acquisition data form. After the award of a Government Contract which consists of multiple line items causing increased manual transactions A single contract can have a hundred plus line items.
Recommended:
To have the capability of uploading multiple line items / CLINS into the MM/ICP module of DPAS, after the award of a Government Contract consisting of multiple line items, which will in-turn create the Due-ins within the WM module.
Mission Critical:
Benefits:
Increased productivity and efficiency of the user.
Frequency:
Daily
Users:
At the very minimum 40 users |
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
|
Entity Identifier CA on 945A, 856R and 856S
|
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. |
|