|
00939 |
DPAS QC Mod - Include MI - Missing Item as allowable result |
Warehouse |
USMC: DMC |
Done |
Description In Defense Property Accountability System's (DPAS) current build, version 3.2, there are currently 16 Quality Control (QC) types:
- Type 1. CALB - Calibration - Before Maint
- Type 2. CALA - Calibration - After Maint
- Type 3. COSB - COSIS - Before Maint
- Type 4. COSA - COSIS - After Maint
- Type 5. MNTB - Maintenance - Before
- Type 6. MNTA - Maintenance - After
- Type 7. OTHB - Other - Before Maint
- Type 8. OTHA - Other - After Maint
- Type 9. TSTB - Test - Before Maint
- Type 10. TSTA - Test - After Maint
- Type 11. RCPB - Receipt - Before Maint
- Type 12. RCPA - Receipt - After Maint
- Type 13. MROB - MRO - Before Maint
- Type 14. MROA - MRO - After Maint
- Type 15. MROB - MRO - Before Maint
- Type 16. MROA - MRO - After Maint
The aforementioned types each have a list of allowable results. The allowable results are dependent on the QC Type for the task. The complete list of allowable results is below:
- DF - Deferred,
- FL - Failed,
- PS - Passed,
- CP- Completed,
- DM - Damaged,
- II - Incorrect Item,
- MI - Missing Item,
- CN - Cancelled,
- CP - Completed,
- RJ - Rejected
QC Type 2, CANB - Cannibalization - Before Maint, is the only QC Type that includes an allowable result which indicates that an asset is not on location or missing, MI - Missing Item. 15 out of the 16 QC Types do not allow this value. Due to the inaccurate inventory levels and locations that DPAS currently reflects as well as human error, users are consistently attempting to execute QC for assets that are not on the prescribed location. Since there is no method of indicating this, users are currently attempting to work around this by failing the QC task whenever possible and either finding the asset in an offline process or progressing with QC by selecting another asset, if available. The users are in need of an allowable value that will indicate that an item is missing and will subsequently generate a Physical Inventory task for the Inventory Technicians to locate the missing asset. In the case that the asset is found, a new QC task, of the same QC type that was originally assigned, needs to be generated in order for the asset to progress through the intended process flow.
Recommended All aforementioned Quality Control Types should include an allowable value of 'MI - Missing Item'. When a user selects this value, the selection should suffice as 'Action Taken' for QC which should leave the user with the ability to close the QC task after 'Marking as Complete'. Subsequently, a Physical Inventory task should be generated in order to locate the asset or take appropriate action (e.g. Inventory Loss transactions), and if the asset is found as a result of the Physical Inventory, a new QC task, of the original QC Type, should be generated in order to allow the asset to progress through its intended process flow.
Mission Critical This is mission critical due to the fact that the current practices are cumbersome and unnecessarily lengthy. Not only does the excess time increase labor costs, but a lack of methodology to handle missing inventory during QC will skew Inventory accuracy.
Benefits The implementation of this solution will greatly reduce time and cost of completing Quality Control while also improving the accuracy and accountability of Physical Inventory.
Users This affects all users due to the direct, secondary, and exponential implications of Inventory accuracy.
Completed - Release 5.1 - 28 April 2017 |
|
|
00938 |
DPAS QC Mod - Allow Location Update |
Warehouse |
USMC: DMC |
Done |
Description In Defense Property Accountability System's (DPAS) current build, version 3.2, all allocated assets for a Quality Control (QC) task appear in the Quality Control Details gridline. The gridline contains selective attributesabout each asset, such as Serial Number, Condition Code, Location, Owning DoDAAC, ICN, etc... The attributes that appear in the gridline are a snapshot of the asset's attributes at the time that the asset was allocated to the QC task. Since these attributes are not dynamic, any changes that have been made to an asset since it was allocated to a QC task will not appear in the gridline. In many cases, an asset has been moved since being allocated to QC. In the scenario that an asset has been moved, the gridline reflects inaccurate results about the asset (inaccurate location). Users are in need of the ability to update the grid results location field. For 14 out of the 16 QC Types:
- Type 1. CALB - Calibration - Before Maint
- Type 2. CALA - Calibration - After Maint
- Type 3. COSB - COSIS - Before Maint
- Type 4. COSA - COSIS - After Maint
- Type 5. MNTB - Maintenance - Before
- Type 6. MNTA - Maintenance - After
- Type 7. OTHB - Other - Before Maint
- Type 8. OTHA - Other - After Maint
- Type 9. TSTB - Test - Before Maint
- Type 10. TSTA - Test - After Maint
- Type 11. RCPB - Receipt - Before Maint
- Type 12. RCPA - Receipt - After Maint
- Type 13. MROB - MRO - Before Maint
- Type 14. MROA - MRO - After Maint
users have the ability to update any asset's Condition Code in the 'Apply Changes to Details' frame (screenshot attached). Users should have the ability to update any asset's (any asset allocated to the QC task and consequentially visible in the grid results) location by checking the appropriate record and updating the location in a similar manner that they would update the Condition Code.
Recommended All 16 Quality Control Types should include a Location field in the 'Apply Changes to Details' frame of the QC form. When a user selects a checkbox for a grid result, enters a new the grid results should be updated to reflect the asset's new Location.
Mission Critical This is mission critical due to the fact that inaccurate locations reflected in DPAS will cause unnecessary wastes, including time spent searching for assets by personnel.
Benefits The implementation of this solution will greatly reduce time and cost of completing Quality Control while also improving the accuracy and accountability of Physical Inventory.
Users This affects all users due to the direct, secondary, and exponential implications of Inventory accuracy.
Completed - Release 5.1 - 28 April 2017 |
|
|
00937 |
Fuel data from Ext Source |
MU |
OSD |
Done |
Description Requirement for DPAS to accept fueling data from anexternal source (DLA, GSA, Commercial Vendor). Data to capture at minimum willbe; Vehicle ID, Fuel Type, Nbr of Gallons dispensed, Date/Time of transaction; Location & (if available) and Utilization at time of transaction.
Recommend The original request was to modify the current Utilization interfaceprocessor to allow for other than Tail Nbr reporting. This is a batch job thattakes the data that was previously written to the Utilization Inbound table andposts that data to each asset's Utilization record. We would also need tocreate a process to read the DLA file and then write the data in the file tothe Utilization Inbound table, if DLA could not provide it in the AIRRS format.
Mission Critical Yes.
Benefits Reduces keystrokes, time and errors while improving and increasing accuracy of fuel usage.
Users Users required to capture fuel data from external sources for reporting.
Completed – Release 6.0 – 27 April 2018 |
|
|
00936 |
Tunner/Halvorsen Report |
PA |
Air Force |
Done |
Description Unable to pull a UIC, Site or Agency report on the 25K Tunner and 60K Halvorsen 60K loaders.
Recommended Create a Site/Agency level report on the Tunner and Halvorsen loaders. The report would include monthly inventory data (UIC location), monthly current meter readings, monthly utilization readings (start and end), main W/Os open and closed (monthly) Sub W/Os (monthly), monthly parts charges and etc. We have included the reports to assist in creating the required report. Again there are numerous reports included however, the data fields are basically repeated so one report listing out the data fields will suffice.
Mission Critical The Tunner and Halvorsen report is a critical reporting tool between the Contractor and the USAF for accountability and serviceability accounting.
Benefits This solution will modernize and improve data reporting between the Contractor and USAF and meet all contractual obligations.
Users Yes
Completed – Release 6.0 – 27 April 2018 |
|
|
00935 |
DLA-DS AS3 Transaction |
Warehouse |
USMC: CSP |
Removed |
Description Currently, the Logistics Program 'CSP Enterprise' does not utilize the Disposal function to transmit to DLA-Disposition Services (DLA-DS) (via DLA-Transaction Services) (DLA-TS) the AS3 transaction (DLMS 856S).
Recommend the ability to have DPAS-WM, for Logistics Program 'CSP Enterprise' transmit to DLA-DS the AS3 transaction when a warehouse indicates they are sending gear/equipment to a DLA Disposition Service DoDAAC as 'Excess' under Material Management / Disposition. This serves as the electronic notification to DLA-DS that equipment is to be transferred to them (DLA-DS).
Mission Critical This is mission critical to help maintain an electronic audit trail and stay FIAR compliant.
Benefits Keeps up with property accountability as it moves from a Warehouse within DPAS and DLA Disposition Services.
Users All users.
11 Mar 2021 – cancelled per Jack Sanders No Longer Needed. |
|
|
00934 |
Recurrent processing and email output for schedule |
PA |
MDA |
New |
Description: All reports and inquires need the ability to be scheduled on recurring bases. Being able to schedule these reports to be processed to an email account would make the process even better. Recommend: Inquiry to allow generation for scheduling by frequency (daily, weekly, bi-weekly, monthly). Set up a check boxes to choose whether to print off line to an email address. Default would be to "print on line" box (already selected), another box would be "user address" (email address of user ID doing the transaction) or "other" box where it would be checked and sent to a specified email address. More than one check box could be chose. Mission Critical: All changes involve reports used to support controls for meeting or sustaining audit readiness. Benefits: Improved processing time because report does not have to be continually setup.? Reports can be obtained from email saving time over access and retrieval from DPAS.? Reports could be scheduled and routed to non-DPAS users if required. Users: This will affect many users, who use pending transactions report and CIP Attestation report. |
|
|
00933 |
Query attachment names by sub UIC |
PA |
MDA |
New |
Description: Currently there is no way to pull a report or query by the different types of attachments per asset. This report would allow users to query attachment name by each asset ID i.e. DD250, DD1149, DD1150 etc. Recommend: This could be developed through the use of a query that would support this output by UIC. This would allow quick determination of a file and the document type i.e. DD250, DD1150, Purchase Order. Mission Critical: This would be helpful to support the requirement to be audit ready in 2017. Benefits: If files were named in a convention that indicated their contents, the auditor could quickly determine those to open to support the audit.? This would improve speed to audit assets, improve DPAS data accuracy with a more consistent file naming convention, and lead to better accountability of assets with regards to source documentation. Users: This will affect all users since it would make entry of attachments more consistent and allow inquiry users the ability to find data in attachments easier. |
|
|
00932 |
Provide Mass Update Capability to Maintenance Schedule |
MU |
Leidos |
Done |
Description Currently DPAS provides for PM Scheduling one asset at a time. With several of the DPAS customers receiving 50+ vehicles at a time, it is very time consuming to set up PM schedules. With like assets receiving the same PM schedule, there is also quite a bit of effort to validate that all of the PM schedules are entered.
Recommend Provide for the establishing of PM schedules and update of the PM schedules en masse. Possibly use Equipment Group or Vehicle Group to select assets to apply the schedule to.
Mission Critical Yes - Many of the customers have stated they do not have the resources to individually set up PM Schedules and to validate that the schedules have been established correctly.
Benefits Reduces the amount of time to profile some assets 100 to 1 and improves accuracy.
Users This affects all DPAS users of M&U PM Scheduling. This SCR was requested by the attendees of the DPAS M&U Workshop held on November 13-15, 2015 and was given a priority of "4" out of 40.
03/22/2017 – per Randy and Jim's email, replacing SCR 01121 with this SCR.
This Feature was completed as part of SCR 01532 Schedule Preventive Maintenance |
|
|
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. |
|