|
01130 |
Real Property Reconciliation |
PA |
Leidos |
New |
Description: With DPAS Release 5.0, DPAS began to incorporate the features to have DPAS become a Real Property Accountable Property System of Record (APSR). The capability that was incorporated in Release 5.0 contained no RP Reconciliation Process.
Recommended: This SCR is requesting DPAS incorporate a Real Property reconciliation process that will enable the Defense Agencies/Activities (Users of DPAS) to be able to provide the DoD Real Property registry with data necessary for the production of an automated reconciliation. It is recommended that DPAS develop a web service for the DoD system to retrieve the required data or provide a file with the required data, whichever method the DoD system prefers.
Mission Critical: Yes. As an APSR, there is an requirement for a reconciliation with the "Host" data.
Benefits: Provides for an automated method for reconciling key Real Property data between the Host and the User/Financial reporting organization.
Users: All organizations that are using DPAS to manage their Real Property. |
|
|
01129 |
Incorporate Real Property BOSS Business Rules |
PA |
Leidos |
New |
Description: With DPAS Release 5.0, DPAS began to incorporate the features to have DPAS become a Real Property Accountable Property System of Record (APSR). Since this incorporation, OSD has issued a document that outlines the responsibility for certain attributes. The attributes in question could be managed by the Host, Financial Reporting Org, Facility User. The Host is the Service/WHS that maintains the official record while the other 2 organizations have some sort of vested interest in it. With the requirement to be able to have differences in the attributes, DPAS will need to modify the system to provide the capability to have 2 or more values for these attributes (what the Host says the value is, what the finanical reporting org says the value is and what the organization that has a vested interest says the value is).
Recommended: This SCR is requesting the incorporation of the Real Property BOSS business rules into the DPAS real property process as outlined in the attached document.
Mission Critical: Yes. As an APSR, there is an requirement for additional Real Property reports.
Benefits:
Incorporates additional business rules relating to the Real Property BOSS document
Users: All organizations that are using DPAS to manage their Real Property. |
|
|
01128 |
Add Two Real Property Reports |
PA |
Leidos |
New |
Description: With DPAS Release 5.0, DPAS began to incorporate the features to have DPAS become a Real Property Accountable Property System of Record (APSR). There were no new RP reports added. There is a need for additional RP reports as a result of DPAS becoming an APSR for Real Property.
Recommended: This SCR is requesting 2 new Real Property reports be added to DPAS. The one will be a summary report that displays the number/type of facilities the organization has an interest in and the other report will be a detail report that displays specifics about the facilities the organization has an interest in. Both reports will be pattern off 2 existing MDA reports they produce from their Real Property system that is being phased out with it being replaced by the DPAS RP capabilities. It is recommended that the system provides for the printing of these reports based upon the RP tier structure (Installation, Site, Asset) using the DPAS Security framework.
Mission Critical: Yes. As an APSR, there is an requirement for additional Real Property reports.
Benefits:
Provides for Real Property reports that do not currently exist within DPAS
Users: All organizations that are using DPAS to manage their Real Property. |
|
|
01127 |
Provide a Real Property Physical Inventory Capability |
PA |
Leidos |
New |
Description: With DPAS Release 5.0, DPAS began to incorporate the features to have DPAS become a Real Property Accountable Property System of Record (APSR). The initial SCR did not provide for a process of scheduling and managing physical inventories for Real Property as would be required of an APSR.
Recommended: Provide a process to schedule and manage real property physical inventories. As the Real Property physical inventory resides within the Real Property Review process, it is recommended that the design includes the capability to schedule and manage all times of reviews. To support this, it is recommended that DPAS provide a form for conducting the Physical Inventory, and a separate form for the types of reviews. This form should be printable on 8 1/2 x 11 paper and be able to be attached to the review. It is imperative that the user be able to view prior reviews and be able to view/print the documentation of those prior reviews.
Mission Critical: Yes. As an APSR, a Physical Inventory process must be a part of the system.
Benefits: Provides for physical inventory and the retention of the documentation within one solution. Organizations will not need to develop/maintain another system to track and manage RP physical inventories.
Users: All organizations that are using DPAS to manage their Real Property. |
|
|
01126 |
Associate Receipt Documents to Serialized Inventory |
Warehouse |
Navy |
New |
Description: Today, the warehouse module provides for associating purchase documents with the Document Nbr within the Document Register. This register will be deleted not later than 10 years due to the reuse of the Document Nbr. Typically DoD requires this register to be maintained by the organization for the current year plus the previous 2 years. When the delete occurs, all supporting purchase documents will be lost. There is also not a good way to find the receipt document nbr for the serialized equipment that is in inventory (what the Existence and Completeness (E&C) auditors view to be able to query the Document Register to locate the purchase documents assuming they have not been removed. For E&C, the organization must be able to provide supporting documentation to the auditor for equipment as well as OM&S purchases (support the Purchase Price entered). With the DPAS Warehouse module supporting the tracking of more equipment (kept much longer) than OM&S today, there is a need for a better way to associate the purchase documents to the asset and for the life of the asset when it is a serialized asset.
Recommended: Provide a permanent link to the receipt document and to the materiel received when the materiel is serialized. There are a number of options that this can be accomplished. One of those options might be to create a 'unique identifier' for the receiving documents and associate the "unique identifier" the Document Register Document Nbr and to the Inventory Control Nbr records representing the materiel receipts. As long as the Document Nbr or the ICN exists, the Receipt attachments would not be removed. Provide an Inventory inquiry that would permit the display of the Receipt attachments. For organizations using the Materiel Management module, the purchase documents may actually reside within the Requisitioning process. The overall design should provide for the system to view the purchase/receipt documentation for a serialized asset regardless of where it is create/held and viewable from within the Warehouse and Materiel Management modules. As capital assets begin to be accounted for within the Materiel Management / Warehouse modules, the need for this capability with become a necessity for FIAR compliance.
Mission Critical: Required for E&C by the organization. While the organization could retain hard copy using a manual file system this is time consuming and is not as easy to support an audit as having the documents directly associated with the equipment within the automated tracking system. This SCR has been advocated by SPECWAR on behalf of all users of the that are managing equipment within the Warehouse Module.
Benefits: This capability will improve financial compliance and improve the organization's auditability.
Users: Yes, this capability will benefit all users of the Warehouse Module. |
|
|
01125 |
Provide for Contract Order Management |
Materiel Management |
Leidos |
New |
Description The Requisition process of the Materiel Management module of DPAS does not provide for the management of Contracts awarded for materiel, supplies and equipment destined for a Warehouse. Without this, there is no way to setup delivery schedules for each Warehouse. The Requisition module needs to contain the functionality for the user to be able to enter Contracts, CLINS and Delivery Order data.
Recommended Modify the Requisition process in the Materiel Management module to allow the user to create Due Ins for Contracts and Delivery Order Numbers. The module should provide for the entry of One-Time contracts providing for CLIN, Stock Nbr, Desc, Qty, Dollar Amt, Extended Price, Owning DoDAAC, Condition Cd, Project Cd, Est Delivery Dt, and Warehouse (RIC/DODAAC). For Delivery Order contracts, the process should provide the ability to enter the same, plus be able to break the Ordered Qtys into a deliver schedule depicting the dates when the Qtys will be delivered to each warehouse. The process should provide for modify and cancel the order. The process should allow the user to depict how the materiel was purchased (Contract or Purchase Card). The order types should be able to be aligned with the Document Sub Types LKP. As the Due In is established, the process should generate 527Ds for each warehouse to establish Due Ins in each warehouse that is scheduled to receive materiel. As the materiel is received by the warehouse, the 527R will update the qty received and should close the requisition once the Qty Ordered = Qty Received.
Mission Critical This functionality is essential in managing Due Ins that are expected to be delivered to the warehouse.
Benefits Provide for the management and reporting of Due for other than MILSTRIP purchases.
Users It is beneficial for all users of the Materiel Management module. |
|
|
01124 |
Add DLMS 856S/527R (MRA) Support to the DPAS-PA Module |
PA |
Leidos |
Done |
Description: Today, the DPAS-PA module utilizes iRAPT for external Dispositions/Transfers. Not all activities utilize iRAPT for equipment transfers. There are activities that use DPAS-PA that want to report transfers actions via DAAS using the DLMS 856S - Shipment Advice (DPAS to Non-DPAS Property Book Transfers). For DLA Disposition Services Actions, the transfers should be reported via DAAS using the 856S.
Recommended: Modify the DPAS-PA Address Directory process to allow for equipment transfer/disposition to notify the gaining party using the DLMS 856S in addition to the current iRAPT capability. When the notification for the party that identified by the Address is via DLMS 856S, generate the 856S and place the transaction into the DLMS Outbound folder. The DLMS 856S will mark the materiel intransit pending the receipt of the 527R (Materiel Receipt Acceptance). Upon receipt of the Materiel Receipt Acceptance, close the Intransit and drop the asset from the property book. In some instances, the gaining party may not be able to accept the 856S or generate 527Rs. To support those instances, DPAS must provide a process to enable the losing party to close the intransit and drop the materiel from the property book.
Mission Critical: Yes. As DPAS is implemented by other parties, such as SOCOM which has equipment transfers to other Services that use systems other than DPAS, there is a need to support other methods of notifying the gaining party of the equipment transfer
Benefits: Improves Accountability of equipment by enable notification to the gaining activity as well as tracking equipment intransit.
Users: This change will be available to all users of the DPAS-PA module. As a minimum, it should be used for all "Turn Ins"/ "Disposal Actions" with DLA Disposition Services.
Completed – Release 6.0 – 27 April 2018 |
|
|
01123 |
Work Order Inquiry Enhancement |
Warehouse |
AF: VSCOS |
Removed |
Description: Vehicle Management Materiel Control sections are required to pull information regarding parts ordered, Due-ins and back orders. Asset Id information, Requisition Status, Parts Cost, Work Order State Code and location are paramount for retrieving part inquiries and supplying high visibility reports. This information cannot be retrieved from warehouse as of today. Recommend to add the Asset Id Information, Requisition Status, Cost and location to the Work Oder Inquiry.
Recommended: Recommend adding Asset Id, Requisition Status, Parts Cost, Work Order State Code and location to the Work Oder Inquiry Grid Options. Add Asset Id to Work Order Inquiry Search Criteria as well.
Mission Critical: Mandated by Air Force Instruction 24-302. Air Force Materiel Control sections need a very detailed process to track, account and issue vehicle parts. See AFI 24-302 references below 5.2.1. Keep FM&A and key personnel informed of overall supply (parts, tools and shop equipment) situation as it affects the shop. 5.2.6. Check daily and verify the need and status of parts for all Non-Mission Capable Supply (NMCS) vehicles. 5.2.7. Check, verify and re-validate all parts requirements on delayed AF Form 1823/-1. Inform the FM&A Workload Controller of their status, as directed by the VFM/VMS. 5.2.23. Perform monthly or quarterly (as directed by VFM/VMS) AF Form 1823/-1 backorder validation with FM&A.
Benefits: Adding all information requested above to the Work order inquiry will enable Materiel Control personnel, technicians and Fleet Managers to have direct access to this critical information. Added information allows Fleet Managers to approve or disapprove requisitions based on priorities assigned to those assets. Further more, it will lead to enhanced supply discipline as mandated in AFI 23-101, Air Force Materiel Management.
Users: This added information will help not only Air Force Materiel Control operations but also all organizations which use the Maintenance Issue process in coordination with the M&U module.
21Nov2017 – cancelled per Fabian Cardona These two SCRs seem to be the same. Please cancel 1123 and proceed with suggested SCR 01144. |
|
|
01122 |
All Work Order Fields Available for Inquiries |
Warehouse |
Air Force |
Done |
Description When doing inquiries on Work Orders and Sub Work Orders not all information inputted into these are viewable or search-able by using the fields tab when setting up an Inquiry. Having to piecemeal a report together between multiple inquiries in an effort to generate required information is not taking advantage of the system capabilities and time consuming.
Recommended Add all Work Orders/Sub Work Orders data field information to be available to be searched in Inquiries.
Mission Critical This is critical. Fleet Managers count on maintenance information being available to make informed/sound vehicle management decisions.
Benefits Allowing all fields of a Work order to be viewed in Inquiries will enhance reports and inquiries for all. Enabling user to search and build reports on any data fields available within the work- order and sub/worker.
Users This SCR will affect the entire AF Agency, all Air Force fleet managers/maintenance controllers utilize this information for day to day fleet management purposes.
Partially Completed – Release 6.2 – 31 August 2018
Completed – Release 6.3 – 21 December 2018 |
|
|
01121 |
PM Mass Updates |
MU |
DLA |
Removed |
Description At the present there is no way to do a mass update in Schedule Preventive Maintenance Add/Update/Delete module. You can schedule in mass however, if you need to go back and change anything you have to do it individually.
Recommended Please add an option to do mass update in the Schedule Preventive Maintenance Add/Update/Delete module.
Mission Critical Mission Critical
Benefits We have over 6,000 assets and 150 PMs that are scheduled each week. Most are scheduled en masse however, if we need to change a day or week we have to update each one individually which is inconvenient especially with the size of our equipment pool.
Users All M&U users
22Mar2017 – cancelled per Jim and Randy Duplicate of SCR 00932. |
|