|
00931 |
Modify WPACR1701R and WPACR1702R to process multiple UICs and run recurrently |
PA |
MDA |
New |
Description
Currently there is no way to generate multiple reports based on multiple UICs. MDA will process twenty UICs weekly for Non-Activated Capital Depreciating Capital Assets reports for a total of 40 reports. The ability to process multiple UICs and schedule recurrent processing from one report would save many hours.
Recommended
Allow the generation of multiple reports based on multiple UICs. Also, allowing a recurrent process for these type of reports would be a great improvement. Varying frequencies for these reports i.e. daily, weekly, monthly would make reports more user friendly. It is a control to ensure that all capital assets are depreciated properly.
Mission Critical
It is a control to ensure that all capital assets are depreciated properly.
It is critical to audit readiness that MDA have as much time as possible to work real issues rather than process reports.
Benefits
This will reduce time spent on report processing and free time to be used for more data analysis.
It will ensure that less opportunity exists to forgot to key a report.
Users
It affects Central Property Office users for oversight. |
|
|
00930 |
MU to PA Requirement |
OUSDDPAS |
OSD |
New |
Description: Currently when an asset or inventory is deemedUn-repairable or Repairs Exceeds Economical Threshold on a WO in M&U, thereis no notification on the PA or WM side for possible Disposition or ConditionCode change. Recommend: Once WO is Closed and WO State Cd is REET or UNRP, theCondition Cd should be prompted for change in M&U and a Pending Transactionreflected in PA or WM Open Actions. Update any SORTS/DRRS as well. Mission Critical: This ismission critical to ensure only mission capable assets are available andissued. Benefits: Improves accountability of assets by identifying those with reduced capabilities requiring some sort of Disposition. |
|
|
00929 |
Maintenance Module Integration with Warehouse |
OUSDDPAS |
OSD |
New |
Description: Currently DPAS allows a disposition of an asset in PAwithout regard of M&U status of asset (i.e. Open WO and Allocated/IssuedDispatch). Recommend: Restrict PA disposition for certain M&U actions toensure asset is ready and available. Mission Critical: Mission critical.? This will ensure only available and serviceable vehicles are used. Benefits: Accurate accountability of assets. Users: This will affect PA and M&U Users. Noreal workaround. System completes PA function. |
|
|
00928 |
Maintenance Jacket Mgmt |
MU |
OSD |
New |
Description: Current DPAS setup has the Work OrderJournal for assets remaining with the Maintenance Activity performing work. Sowhen an asset is transferred, previously completed WO do not accompany asset. Recommend: Will need to have previous WOs completed accompany assets. Mission Critical: This ismission critical for maintenance management and the only workaround is hardcopyWO accompany assets when transferred. Benefits: History of completed WO will ensure recalls are accomplished, part failures documented and a complete history of vehicle life. |
|
|
00927 |
Receiving Existing ICN Error |
Warehouse |
USMC: DMC |
Removed |
Description
In Materiel Management, Receiving, User was unable to receipt for an asset and received "Error 117: Stock Number Serial Number combination already exist". The cause of this error is the User trying to create a new Inventory Control Number (ICN) for a Stock Number/Serial Number combination that already has an existing ICN. The interim solution is to click on the Browse button for the ICN field when adding a record. The User would then select the already existing ICN for the Stock Number/Serial Number combination in question and utilize that ICN rather than try to create a new one.
Recommend
DPAS provide an automatic ICN when there is a ICN Stock Number conflict. The customer should not have to look up the ICN but have DPAS provide it.
Mission Critical
This is mission critical, because customer needs the ability to have DPAS automatically provide an alternate ICN when in conflict or has already been used.
Benefits
The benefit is this change will streamline processes by reducing the time it takes to find or create alternate ICNs.
Users
All
11 Mar 2021 – cancelled per Jack Sanders
No Longer Needed. |
|
|
00926 |
Inventory Reconciliation Rpt Time Length |
PA |
Navy |
New |
Description
Right now after an inventory has been reconciled and coded (CRC) its Reconciliation reports are no longer available after 15 days. Under the "Manage Inventories" process in DPAS, it offers the option to "Generate Rcl Report". Once I try to run this I get an error message that states "250 - A selected inventory does not have a Inv Process Cd = "OUA" Cannot perform selected action". As a manager I should be able to generate a Reconciliation report for inventories that have been completed after 15 days if someone had failed to do so. These are required audible documents and with the time it takes us to complete a wall to wall, 15 days is just not enough time to retrieve one if we need to do so.
Recommend
Make retrieving a Reconciled Inventory report accessible for inventories coded "CRC" after 15 days. This access should be available for the time required until the next inventory has been completed for that Custodian as the SECNAV Instruction 7320.10a states.
Mission Critical
These reconciliation reports are mandated per the SECNAV Instruction 7320.10A are audible documents.
Benefits
Benefits of implementing this is to ensure the proper documentation for accountability and for financial reporting during audits.
Users
This affects all Property Book Officers. |
|
|
00925 |
Component Exchange |
Warehouse |
USMC |
New |
Description: Currently, there is no Functionality to exchange components items in the IIF or UIF. This creates a problem by having to return the entire Kit for the exchange of only one component. Recommend: Recommend that an exchange component item function be added to the return process in the IIF and UIF. ?This will help with the exchange of the component process creating less time then to try to return the entire kit and reissue the kit again. Mission Critical: Yes. This will help speed up the process for exchanging component items and will reduce time. Benefits: This will reduce time with this functionality. Users: All IIF & UIF |
|
|
00924 |
Physical Inventory |
Warehouse |
USMC: DMC |
Done |
Description
There is no Functionality to be able to select multiple locations during a Physical Inventory thus, creating a problem of having to do multiple physical Inventories for locations.
Recommended
Recommend that the functionality be added to be able to do Multiple Locations during a Physical Inventory.
This added functionality would create less work when conducting a Physical Inventory by locations.
Mission Critical
Yes. This will help speed up the process for doing Physical Inventories by Locations and will reduce time.
Benefits
This will reduce time with this functionality.
Users
All IIF & UIF
Partially Completed - Release 5.1.2 - 23 June 2017
25 June 2020 – cancelled per Ryan Steele
No Longer Required. |
|
|
00923 |
Update the Real Property Module |
PA |
MDA |
Done |
Description
The DPAS Real Property module does not include all the fields required for real property reconciliation and does not meet current model requirements. For example, the Unit of Measure field does not include KW, TR, etc. which are frequently used for reporting. The Real Property module does not allow for recording Real Property at the Asset level. All sub-components must be lumped into a single record that creates difficulties in determining valuations.
Recommended
Update the Real Property Module to be in compliance with the OUSD Real Property Information Model and include the mandatory fields listed in Real Property Data Reconciliation Requirements to comply with the requirements of DoDI 4165.14.
Also allow for recording of Real Property items at the asset level. Currently DPAS is limited to a single entry per Real Property Unique Identifier (RPUID). However, current guidelines require tracking at an asset (or Category Code) level. A single RPUID may have multiple Category Code assets, each with its own unit of measure, valuation, description, etc.
Mission Critical
Yes, this requirement is mandated. Refer to Department of Defense Instruction (DoDI) 4165.14, OUSD I&E "Real Property Data Reconciliation Requirements" dated January 21, 2010, and OUSD I&E Real Property Information Model v8.1 dated March 31, 2015.
Benefits
Implementing this change will reduce duplicate record keeping in a separate system, greatly reduce reconciliation efforts and increase reliability in accountability and financial reporting.
Users
It will affect all users of the Real Property Module.
NOTE: Connected to all other RPUID SCRS:
- 00448,
- 00510,
- 00551,
- 00651,
- 00996,
- 01020,
- 01045,
- 01048,
- 01049,
- 01050,
- 01113,
- 01153,
- 01225
Partially Completed - Release 5.0 - 03 February 2017
Partially Completed - Release 5.0.1 - 10 March 2017
Partially Completed - Release 5.1 - 28 April 2017
Partially Completed - Release 5.2 - 29 September 2017
Completed - Release 5.2 |
|
|
00922 |
LPWHI13 - DLMS 856S, 856R Shipment Status - Include Serial Numbers, create missing Due-In Transactions |
Warehouse |
USMC: DMC |
Done |
Description
DPAS is receiving the 856S, 856R (AS1/AS2) from external users via the DLATS feed.
The 856S, 856R transactions are transmitted when the shipper confirms shipment from GCSS-MC.
The 856S, 856R will provide LOGCOM with the data required to establish a Due-In record at a serialized level.
Since 856S, 856R transactions are provided by GCSS-MC, containing Serial Number data this information is available.
DPAS is receiving the XML versions of the 856S, 856R containing Serial Numbers from DLATS.
Marine Corps requests the following business rule to be applied, in DPAS, in order to gain full visibility of serial number data within the Prepositioned Material Release (PMR), due-In management file.
This request is in line with the FIAR's policy initiative.
Serial numbers can be located in the REF SE loop of the 856S, 856R transaction.
Recommended
Read the incoming 856s, 856R transactions, if DUE-IN transactions exist, append the serial number data to the existing record.
Mission Critical
Yes, Marine Corps requires the following business rule to be applied in DPAS in order to gain full visibility of serial number data as it relates to Due-In records. This request is in line with FIAR’s policy initiative.
Benefits
The benefit of implementing this solution is, that it will improve accountability of inventory.
Users
All
Completed - Release 5.1 - 28 April 2017 |
|
Disclaimer | Accessibility