|
Eliminate DLMS 870s for TPFs
|
08156
|
Materiel Management |
Army: ASA(ALT) |
New |
Change Request: Process Improvement
Description:
ASA(ALT) utilizes the Materiel Mgmt. module to perform Total Package Fieldings (TPFs). When a push customer requisition is entered / approved, DPAS will generate / send a DLMS 870S Supply Status along with a DLMS 527D Prepositioned Materiel Receipt to the recipient of the intended recipient of the materiel. The DLMS 527D is determined by the customer profile while the DLMS 870S is automatic as if the push order was a pull order with DPAS responding to the receipt of a DLMS 511R. Army is encountering an issue when the DLMS 527D is not transmitted (customer profile incorrectly established), or when the 527D is rejected by GCSS-Army. When the DLMS 527D is not received / processed and a DLMS 870S is received, GCSS-Army will establish a Due In and transmit a DLMS 511R to National for the purchase of the materiel that is to be provided by the PEO/PM.
Recommended:
Army is requesting that DPAS not generate DLMS 870S Supply Statues for TPF type orders. The Supply Status is not needed and results in the generation of an order when there isn't one desired. All TPF activity is supported by the DLMS 527D Prepositioned Materiel Receipt (PMR). Should the PM change the qty or cancel the order DPAS sends the change via an updated PMR (DLMS 527D).
Mission Critical:
This functionality is needed to prevent unwanted orders being generated to national when the DLMS 527D prepositioned receipt is not received / processed.
Benefits:
This change will eliminate unwanted orders being systematically generated by GCSS-Army.
Frequency: Daily
Users:
This feature will be utilized by the ASA(ALT) PMs in fielding of the next generation of equipment to the U.S. Army and by USSOCOM for push orders to their customers.
|
|
DPAS Sub-Warehouse / Shop Code and DLMS
|
01855
|
Warehouse |
Leidos |
In Progress |
Change Request: Process Improvement
Description:
Currently each DPAS warehouse is required to have a unique RIC (Mandatory when external reporting is required) and / or DoDAAC. This value is used for routing DLMS transactional data between DPAS Warehouse Mgmt. and DPAS Materiel Management Mgmt. modules and to / from external systems. There are times where a DPAS Customer has an organization that has a requirement for multiple warehouses to manage different commodities that is not desired to have them commingled e.g. spare parts, tool crib, un-issued materiel with no avenue to acquire additional RICs. Note: The Department is running out of 3 character RICs with plans to replace the RIC with DoDAAC once logistics system are fully DLMS compliant (eliminate support for MILS format).
Recommended:
The proposed change will have DPAS implement the Planning / Maintenance Organization (Shop Service Center) name value as part of the warehouse business key. By including this value, DPAS will be able to use this value along with a RIC / DoDAAC to route DLMS transactions enabling an organization to have multiple warehouses without having each of them having a unique RIC / DoDAAC.
Mission Critical:
This change will enable an organization to have multiple DPAS warehouses which will enable them to have multiple Tool Cribs, Parts/Supply Rooms, Issuing locations, etc.
Benefits:
This SCR is identified as phase 1 of the DPAS effort to add flexibility to its Warehouse Mgmt. module. With this change DPAS customers will be better able to manage its different types of inventories / different physical locations within an organization. Additional efforts are planned to provide greater flexibility in configuring a DPAS warehouse.
Frequency: Daily
Users:
Currently SPECWARCOM and the Air Force has multiple warehouse requirements within a organization.
Partially Completed – Release 2023.1.1 – 13 January 2023
Partially Completed – Release 2023.1.2 – 27 January 2023 |
|
nformation Owner User Account Request Submission
|
01854
|
Enterprise |
Leidos |
New |
Change Request: Process Improvement
Description:
DOD has issued an updated DD Form 2875 that requires changes to the DPAS validation / import process. With the increased number of users to manage, to have DPAS personnel preform the validation, then report the error(s) to the security POC delays a new user in receiving an account. The proposed improvement is to provide capability for Information Owners that have an active DPAS account to perform the validation enabling DPAS to provide immediate feedback to the information owner as to what needs to revised, and the change would enable the information owner to submit the validated DD Form 2875 for processing.
Recommended:
DOD has issued an updated DD Form 2875 that requires changes to the DPAS validation / import process. With the increased number of users to manage, to have DPAS personnel preform the validation, then report the error(s) to the security POC delays a new user in receiving an account. The proposed improvement is to provide capability for Information Owners that have an active DPAS account to perform the validation enabling DPAS to provide immediate feedback to the information owner as to what needs to revised, and the change would enable the information owner to submit the validated DD Form 2875 for processing.
Mission Critical:
DOD has issued an updated DD Form 2875 that requires changes to the DPAS validation / import process. With the increased number of users to manage, to have DPAS personnel preform the validation, then report the error(s) to the security POC delays a new user in receiving an account. The proposed improvement is to provide capability for Information Owners that have an active DPAS account to perform the validation enabling DPAS to provide immediate feedback to the information owner as to what needs to revised, and the change would enable the information owner to submit the validated DD Form 2875 for processing.
Benefits:
Allow more efficient account creation and modification for both customers and account management staff.
Frequency: Daily
Users:
DPAS processes 1000s of DD Form 2875 yearly. |
|
Additional Details for FSM Auth On-Hand Report
|
01853
|
FSM |
AF: A4/HAF FH-AFHAF |
New |
Change Request: New System process
Description:
Current FSM Auth On-hand report does not auto populate the the Master NSN in the NSN column when running a report with the Interchangeable or Substitute NSN. Additionally FSM Auth on-hand capability can only be submitted as report and limits filtering data elements to only being able to run a report one NSN at a time. The current 'work around' is to run a report at either the MAJCOM, AUIC, UIC level to see all the NSN. UIC selection requires the user to scroll to find the UIC they
Recommended:
Populate the Master NSN in NSN column, regardless if the inquiry is for the Interchangeable or Substitute NSN. Include in the Pop-up screen for the search stock number a notice if the NSN is a Interchangeable or Substitute to a Master NSN. Allow to run reports for multiple NSN, UICs, Auth-id etc. Include intelliSense capability for all search by data elements
Mission Critical:
Current process is limited and requires more robust capabilities
Benefits:
This will provide the DAF the capability to make data driven decisions for the management and oversight of Support Equipment.
Frequency: Hourly
Users: [blank] |
|
Modification of LIMS-EV interface to support M&U changes
|
01852
|
MU |
Leidos |
New |
Change Request: Process Improvement
Description:
With the modernization of M&U, in addition to asset linkage between PA and M&U, user can direct input asset into M&U and there will be an eventual asset linkage between WM and M&U. To support these changes along with supporting a micro-service framework, the linkage of the Maint. Asset Master / Work Orders are no longer a direct association to Asset Master. Reference DPAS Ticket Nbr - 78525
Recommended:
Modify the LIMS-EV interface to incorporate an Equipment Master view and modify the linkage between various other LIMMS-EV views to utilize the Equipment Master view.
Mission Critical:
DPAS change how Maintenance records are linked to their source.
Benefits:
This is considered a mandatory change in order to maintain data integrity within the LIMS-EV views.
Frequency: Hourly
Users:
All consumers of the LIMS-EV interface data. Currently this is AF Discovery and DoD Advana. |
|
Impound Asset Manager
|
01851
|
MU |
USAF: AvSE |
New |
Change Request: New Role Design
Description:
Problem: Not currently able to lock down an asset in DPAS M&U when asset is impounded as directed by DAFI 91-204, Safety Investigations and Reports. This inability allows for the potential of users to change/update asset information in the system while the asset is still under investigation, causing a major safety and records management issue.
Recommended:
Create a new Impound Official role within DPAS M&U and add a check box to the Maintenance Asset Master screen labeled as "Asset Impounded". Selection of this check box by an authorized person will "lock out" all other users and lock all asset history while the asset is impounded. Once asset is released from impound, an authorized user will unlock this asset and it will be available for normal use/maintenance. Limit use of the new Asset Impounded check box to only the newly created Impoundment Official role.
Mission Critical:
Mandated by DAFI 91-204, Safety Investigations and Reports, and DAFI 21-101, Aircraft and Equipment Maintenance Management.
Benefits:
The addition of this role will allow for proper control and integrity of asset historical data within DPAS M&U and will make DPAS M&U compliant with Aircraft/Equipment impoundment procedures. This additional role and ability will also address safety concerns, by not allowing use when an asset condition is questionable or under investigation.
Frequency: Monthly
Users:
Hard to measure, possibly several times a month. |
|
Add SubWO Fields to WO Search Results Grid
|
01850
|
MU |
USAF: AvSE |
New |
Change Request: Process Improvement
Description:
Problem: Currently when users search Work Orders, the results that populate do not give specific enough information on what the Work Order is for.
Proposed Improvement: Addition of Sub-Work Order specific columns to Work Order search results grid.
Recommended:
Add an additional option to display Sub-Work Orders for each Basic-Work Order. Include fields that display Requested Service and Work Order Description.
Mission Critical:
(Not Provided)
Benefits:
The addition of these fields will save users time and aggravation, as when they are searching for a specific Work Order they are searching for the narrative of the work to be accomplished (i.e., 6 Month Inspection). The average user will not know the Work Order Reason, Work Order State Code, or Work Plan Type Code. Therefore, if there are several open Work Orders on a single asset (a common occurrence), users will have to click on all the search results until they find the specific Work Order they are looking for, this proposed improvement will solve that issue.
Frequency: Hourly
Users:
This function will be used by all AvSE users in DPAS M&U thousands of times a day. |
|
Authorized On-Hand Qty
|
01849
|
Warehouse |
Navy: NECC |
New |
Change Request: New Process
Description:
DPAS currently has high and low limits for stocking, but we would not want to affect those fields for inventory management purposes. NECC has a need for a data field that captures the allowance authorized per stock number / SKO at the Warehouse/ DoDAAC /UIC Level.
Recommended:
NECC would like to add a field in our Logistics Program that captures the Authorized Allowance Quantity (We might label the Field as "TOA" for simplicity for our Force) by Stock Number/SKO that we are able to edit at the LP Level only. The ability to set that and for it to appear on the ICN report would be a huge impact to our understanding of mission needs.
Mission Critical:
Multiple documents approved by OPNAV grant allowances for equipment to our commands based on Required Operating Capability and Projected Operating Environments (ROC/POE). These requirements build our Table of Allowance (TOA) and are a movable target as missions change and equipment gets refreshed.
Benefits:
The benefit is cost savings for identifying excess/shortages of materiel across our force and having better data for our leadership to make better risk and business decisions.
Frequency: Hourly
Users:
At this level we would expect the commodity managers at NECC to monitor and maintain these TOA levels in DPAS as well as the Property Book Office. Estimate 10 personnel would need access to monitor and maintain this field. |
|
Form requests for MRO process
|
01843
|
Warehouse |
Army: ASA(ALT) |
New |
Change Request: Process Improvement
Description:
DPAS currently offers the DD Form 1348 for its Materiel Release Order (MRO) process. This form is normally used with wholesale issues / returns. ASA(ALT) utilizes the MRO process for Total Package Fieldings (TPFs). To support TFPs, the use of the DA 2602, DD Form 1149 and or DA Form 3161 forms or their DoD equivalents is more appropriate.
Recommended:
Add the following options for forms within the Materiel Release Order process
a. Add DA Form 3161 REQUEST FOR ISSUE OR TURN-IN or the DD form equivalent
b. Add DD Form 1149 REQUISITION AND INVOICE SHIPPING DOCUMENT
c. Add DA Form 2602 HAND RECEIPT/ANNEX NUMBER or the DD form equivalent
Mission Critical:
The use of these forms are more appropriate for the U.S. Army fielding of new equipment. See AR 710-2 SUPPLY POLICY BELOW THE NATIONAL LEVEL.
Benefits:
This change reduces ambiguity to the receiver of the items, and enhances user acceptance.
Frequency:
Daily
Users:
ASA(ALT) performs thousands of fieldings / year. |
|
Ad Hoc Kit
|
01844
|
Warehouse |
Army: ASA(ALT) |
New |
Change Request: New System process
Description:
Add the capability to have a Set, Kit, Outfit / End Item->Component relationship with having to catalog a SKO.
Recommended:
ASA(ALT) utilizes DPAS to manage fieldings. Items are often purchased separately and fielded as a kit that is not 100% standard. It could be a kit that is assembled for evaluation / testing that is sent off. There could be multiple variations in order to conduct the valuation needed to determine what the final configuration will be.
Mission Critical:
ASA(ALT) utilizes DPAS to manage fieldings. Items are often purchased separately and fielded as a kit that is not 100% standard. It could be a kit that is assembled for evaluation / testing that is sent off. There could be multiple variations in order to conduct the valuation needed to determine what the final configuration will be.
Benefits:
Having the capability to create an ad hoc kit if needed. It will save countless hours of developing Catalog SKOs that will likely never be used in fielding.
Frequency: Monthly
Users:
All ASA(ALT) programs will use this capability |
|
FLIS/ AEMM Interface for Mfr Part Nbr data
|
01845
|
Warehouse |
Army: ASA(ALT) |
New |
Change Request: Process Improvement
Description:
FLIS and AEMM provides CAGE / Mfr data as part of their data feeds for NSNs / MCNs. DPAS does not currently auto import the data when the Stock Nbr (NSN / MCN) is established. DPAS requires the user to manually input this data without the benefit of the data provided by FLIS / AEMM. This effort is not trivial for ASA(ALT) as its mission is to field the next generation of equipment which require the continuous DPAS cataloging of the new items and the fact that the PA module requires the establishment of a Manufacturer Part Nbr record prior to receipting for materiel.
Recommended:
1. When cataloging a new item where the stock nbr is interfaced from FLIS or AEMM, and one or more manufacture records are available for the Stock Nbr, DPAS should display the Mfr Part Nbr records to the user and provide the user with the capability to select the ones they desire to be added to the Mfr Part Nbr table.
2. Upon selection, DPAS should auto establish the Mfr Part Nbr records in the user catalog.
3. DPAS also needs to update existing Mfr Part Nbr records when the interface provides updates and add new Mfr Part Nbr records when new ones arrive for stock nbrs that have been cataloged.
Mission Critical:
This functionality will significantly reduce the U.S. Army's DPAS cataloging effort.
Benefits:
This change will streamline cataloging for all DPAS users and improve the overall DPAS user experience.
Frequency: Daily
Users:
All cataloging users that utilize the FLIS and or AEMM data feeds. |
|
SKO Catalog Improvements
|
01846
|
Warehouse |
Army: ASA(ALT) |
New |
Change Request: Process Improvement
Description:
The current SKO catalog process is difficult to use to create a kit configuration that contains many items. It requires a lot of scrolling left to right and up and down. Note: U.S. Army has kits that contain as many as 500 items with kits within kits.
Recommended:
1. With ASA(ALT) having lots of kits containing many items, it is recommended that DPAS provide the capability to import kits using an Excel spreadsheet and/or another format that simplifies the process. The process should also allow for th export of a current kit, the update of it off-line, then the re-upload the updated kit configuration.
2. U.S. Army has many of its kit configurations available via LDAC. It is recommended that DPAS work with LDAC to determine the possibility of LDAC providing the kit configuration in a format that a DPAS user could directly import into DPAS and / or have the kit configurations included as part of the AEEM catalog data feed.
3. DPAS needs to display the kit configuration as a tree based upon the tree order. When there are kits within a kit, it needs to display the kit tree with the appropriate indents for the kits within a kit
4. DPAS needs to support at least 5 levels of kits within kits.
Mission Critical:
This functionality is needed to support U.S. Army kits.
Benefits:
This change will enable kits to be assembled with more items than the SKO catalog identities.
Frequency: Weekly
Users:
This feature will be utilized by the ASA(ALT) PMs in fielding of the next generation of equipment to the U.S. Army. It is believed that other DPAS users that are managing kits with large numbers of items and with kits within kits. |
|
Kit Assemble Enable Ad Hoc Items Addition
|
01847
|
Warehouse |
Army: ASA(ALT) |
New |
Change Request: Process Improvement
Description:
There are times when there is a need to add addtional items to a managed kit. Today, DPAS provides the capability for managed kits to be considered a complete kit when items are missing, but DPAS does not provide the capability to add additional items to a managed kit. The DPAS Kitting process should provide the capability to add additional items (items not listed in the SKO catalog) to a managed kit.
Recommended:
1. Modify the SKO Catalog for managed kits to denote whether additional items are authorized to be included in the kit.
2. Provide for the selection of additional items during the Kit build/update phases when the kit authorizes additional items to be included.
3. The completed kit form that lists the items in the kit should display the additional items and denote that these items are additional items (not part of the standard kit configuration).
Mission Critical:
This functionality is needed as often times the Army has are requirement to provide additional items in a kit.
Benefits:
This change will enable kits to be assembled with more items than the SKO catalog identities.
Frequency: Weekly
Users:
This feature will be utilized by the ASA(ALT) PMs in fielding of the next generation of equipment to the U.S. Army. It is believed that other DPAS users that are managing kits would benefit. |
|
Enable Kit Assembly Substitution Items
|
01848
|
Warehouse |
Army: ASA(ALT) |
New |
Change Request: Process Improvement
Description:
DPAS has the capability to manage configured kits, but currently does not provide for the capability to complete the kit using valid substitute items. The DPAS Kitting process should provide the capability to utilize substitute items to create managed kits.
Recommended:
1. Modify the SKO Catalog for managed kits to denote whether a substitute item is authorized to be used for the item in the kit.
2. Provide for the selection of substitute items for creating a kit when a substitute is authorized.
3. The completed kit form that lists the items in the kit should display the planned kit item with an annotation that the kit was assembled using the identified substitute Item.
Mission Critical:
This functionality is needed as the planned item is not always available when a fielding occurs, thus the PM must utilize valid substitutes.
Benefits:
This change will enable kit fielding to occur of Kits when substitute items are used and inform the user that the kit was assembled using one or more substitute items.
Frequency: Weekly
Users:
This feature will be utilized by the ASA(ALT) PMs in fielding of the next generation of equipment to the U.S. Army. It is believed that other DPAS users that are managing kits would benefit by having this functionality as all Services support the concept of substitutes. |
|
Materiel Movement pFRID Capabilities
|
01842
|
Warehouse |
Leidos |
In Progress |
Change Request: Process Improvement
Description:
Currently, the materiel movement processes with DPAS Warehouse do not support the identification of assets, container and locations utilizing passive RFID (pRFID) technologies. DPAS also does not support unique pRFID tag ids for bulk items in all modules as it should.
Recommended:
Provide the ability to identify and select assets and containers, for inventory relocation functions, using pRFID scanning technology.
Mission Critical:
Linear (barcode), 2D (data matrix) and Optical Character Recognition (OCR) scanning technologies require a direct line of sight in order to read the identification markings. RFID allows for the detection of one or more tags within an adjustable vicinity or read range without having to physically touch or move the asset or container. In most cases, RFID formats can determine the type of asset identified - location, container or asset.
Benefits:
Accuracy, efficiency and time savings. Provide consistently throughout the DPAS processes and conform to pRFID industry standard.
Frequency: Daily
Users:
All warehouse, inventory managers can benefit from using this functionality.
Partially Completed – Release 2023.1.5 – 10 March 2023 |
|
Appointment Scheduler Updates
|
01841
|
Warehouse |
Leidos on Behalf of USMC |
Done |
Change Request: Process Improvement
Description:
Currently, members arriving at the centers for an update to their unit assignments causes disruption to the flow of members seeking to receive or return their gear. This is administrative work and currently there is no method to channel them to a single lane, dedicated to making updates to the member's profile.
Additionally, the Appointment Queue, used to display a prioritized list of members who have checked in and awaiting service, only displays 3 columns of scheduled and 1 column of walk-in appointments, each column holding 9 member appointments. As there are no appointments being scheduled at this time, this only allows (at most) 9 'walk-in' members on a single display page before rolling to the next page. Using a 70" display monitor, it should be able to display more than 36 total or 9 walk-in appointments.
Recommended:
Add a new appointment type - Permanent Change of Assignment (PCA).
Modify the appointment display to provide for dynamic columns to better support the mix of walk-ins vs those members who have scheduled an appointment.
Mission Critical:
Provides improved member visibility of where they are in the queue for obtaining / returning gear.
Benefits:
Better information, visible to the facility, in order to staff according to the member traffic within the center throughout the day. Eliminates members sitting around idle, waiting for their selected service to begin.
Frequency: Hourly
Users:
All issue and return facilities within the USMC, varies by facilities; typically 50 to 200+ members per day.
Partially Completed – Release 2022.3.2 – 02 December 2022
Completed – Release 2023.1.1 – 13 January 2023 |
|
DPAS Generate Equipment Status Report AFTO Form 244
|
01840
|
MU |
USAF: SE |
New |
Description:
There is presently no M&U Report or Form that produces something similar to the AFTO Form 244. The AFTO form 244 is the AF-mandated hard-copy/manual means to track and document maintenance discrepancies and inspections for equipment and is maintained on the equipment at all times to allow ready validation of serviceability, or to document discrepancies discovered during use. Require the ability to print pre-filled forms with data from M&U. This allows maintainers and personnel to quickly identify the serviceability of the asset.
Recommended:
Using Data in DPAS, create a Report or Form that provides the data contained in the AFTO Form 244 with field names changed to match DPAS M&U field names.
Mission Critical:
Mandated and critical. If an asset is dispatchable an AFTO Form 244 must be affixed to, and accompany the asset at all times. This form is the only way a user on the flightline can determine if a piece of equipment is serviceable and safe for use.
Benefits:
Ensures equipment is in a safe condition prior to use. Reduces time and improves accountability. It is a safety issue as the AFTO Form 244 is the conduit to communicate discrepancies or status of the asset to operators of the equipment. Policy impacted - AFI 21-101 and 21-103.
Users:
Affects Maintainers, Users of the Equipment, QA personnel. Currently there are 160,000 pieces of equipment bridged to our maintenance group LM. Estimate 60% of the assets in M&U (FH-AFHAF) require hard-copy AFTO Form 244's accompany the equipment at all times. |
|
DISA FAMIS-CS Interface Update
|
01839
|
PA |
DISA |
New |
Change Request: Process Improvement
Description:
Update DISA's FAMIS-CS Interface to be the same as the FAMIS-WCF. Please use the FAMIS-WCF file layout specifications starting on page 21 for the FAMIS-CS file layout specifications starting on page 23 on the attached word file.
Recommended:
Update DISA's FAMIS-CS Interface to be the same as the FAMIS-WCF
Mission Critical:
Currently we are having to manually manipulate the interface every month for FAMIS to read/accept. This can lead to errors due to human intervention.
Benefits:
With DISA’s WCF moving to a OneFund (no split between the TSEAS & CS), we need the interfaces to be the same in order for FAMIS to read/accept both interface files.
Frequency: Monthly
Users:
All financial records and users managing this action DISA wide. |
|
Receive TCN data for ITV capability
|
01838
|
Materiel Management |
USAF AFHAF |
New |
Change Request: Policy/ Regulatory
Description:
As part of DOD mandated In-transit Visibility (ITV) the Air Force Distribution team assigns a Transportation control number upon receipt and acceptance of materiel being transfered off the installation. Currently, CMOS does not provide the TCN for assets being shipped via DPAS
Recommended:
Interface with source system to have this data element populated as part of the movement transaction, also include TCN for in-bound cargo
Mission Critical:
IAW Defense Transportation Regulation Part II Appendix L, Transportation Control Number (TCN) and Chap 202 Paragraph G Proof of Shipment, proof of delivery, and DOD In-Transit Visibility (ITV) Requirements
Benefits:
Compliance with DOD policy and regulations
Frequency:
Hourly
Users:
All |
|
Time Compliance Technical order (TCTO) Work Plan Modification
|
01837
|
MU |
USAF: AvSE |
New |
Description:
Currently, there are no specific field names to be populated for TCTO work plan addition. This lack of specific TCTO field names is causing users to incorrectly input information into the wrong DPAS fields which makes traceability impossible for compliance tracking/monitoring. Lack of ability to ensure TCTOs are complied with prior to using equipment causes risk to aircraft, equipment, and personnel.
Recommended:
Recommend specific DPAS Field Names be created under Maintenance Work Plans - Plan Modify Work Plan Type Code "TCTO" to allow mandated TCTO information to be input for work plan creation. Specific fields for "TCTO Number", "TCTO Title", "TCTO Data code", "Est Labor Hours", "Est Hours to Perform", "TCTO Rescission Date (MM/DD/YY)". This Work Plan Type code will be utilized by sustaining Program Offices in conjunction with the Centralized Work Plan capability.
Mission Critical:
Mission critical and mandated. DoD MIL-DTL-33804, Technical Order 00-5-15, and Air Force policy outline requirements for TCTO processes. Currently, TCTO compliance cannot be accurately tracked/measured due to incorrect/inconsistent entries into the work plans. These inconsistencies prevent utilizing the report feature to track compliance through filtered excel reports.
Benefits:
By allowing for these specific DPAS Field Names to be created and utilized for work plan generation you instantly make reporting accurate and viable, as well as ensure the necessary information is correctly input into the archive system. Also ensures compliance with DoD MIL-DTL-33804, Technical Order 00-5-15, and DoD and Air Force policy.
Users:
This SCR would be a global benefit for any and all M&U users of who input and document TCTOs. |
DPAS Support
Defense Property Accountability System