Description
Build a Work Order tool to support USMC NAF maintenance and repairs.

Recommended
Develop a tool to log, track, and support building maintenance and support and associated tasks and work orders. The tool will include the ability to schedule preventative maintenance on a recurring basis (e.g. Annual Check/Maintenance of the HVAC system).  tab within the RP asset that allows the user to view all of the Work Orders associated to that RP asset. Provide sufficient summary information to know what the WO was for with a hyper link to display the specific Work Order in a new Browser window. Store record of work orders performed on asset, populated from work order tool and ability to enter records.

Mission Critical
Currently DPAS does not support this functionality.  This would be necessary to support USMC NAF's requirements.

Benefits
Improvements to Accuracy, Accountability, Financial Reporting.

Users
This would provide additional functionality to all DPAS Real Property users.

Description
The current Real Property functionality in DPAS needs enhanced to support USMC NAF Real Property needs.

Recommended
Develop a means to realize RP CIP to the property book, develop ability to setup and manage a RP Improvement. Build a new tab to track Facility maintenance. Build a new tab to track CIP Improvements and projects associated with the Real Property asset. Build functionality to track funding for the Real Property asset. Develop tests to track facility maintenance spend and facility condition.

Mission Critical
Currently DPAS does not support this functionality. This would be necessary to support USMC NAF's requirements.

Benefits
Improvements to Accuracy, Accountability, Financial Reporting.

Users
T his would provide additional functionality to all DPAS Real Property users.

Linked to SCR #01620

Completed – Release 2020.3.2 – 13 November 2020

Description
Build a Project Planning tool within CIP to support USMC NAF Real Property life cycle management.

Recommended
Build a minimum viable product project planning tool.  The tool will include:  Additional fields to support different phases; ability to track through submitted / approved / design / construction; ability to pull in projects from Microsoft project; ability to build projects with associated funding fields, category types, calendars with alerts; Single Use Projects and Multi Use Projects; Project sub types: Capital Improvement and Maint.

Mission Critical
Currently DPAS does not support this functionality. This would be necessary to support USMC NAF's requirements.

Benefits
Improvements to Accuracy, Accountability, Financial Reporting.

Users
This would provide additional functionality to all DPAS Real Property users.

Partially Completed - Release 2021.3 - 10 Sept 2021

 Partially Completed – Release 2021.4 – 17 December 2021

Description
Enhance existing DPAS CIP Funding to support USMC NAF requirements.

Recommended
Develop the functionality to support multiple Funding sources to support development phase. Add ability to decrement funding based on funding phases and costs. Build a grid display to show all funding documents and the totals for all funding documents. Automation of USMC funding docs via GEX interface. Fix Source Desc Display.

Mission Critical
Currently DPAS does not support this functionality. This would be necessary to support USMC NAF's requirements.

Benefits
Improvements to Accuracy, Accountability, Financial Reporting.

Users
This would provide additional functionality to all DPAS Real Property users.

Description
The existing ST/STE database, eTIMS, generated a form called a "C-List" for every request created. The "C-List" contained: who created the request, who the list is addressed to (warehouse if a unit issue request, or vendor if an issue transfer), request number, date request created, aircraft, comments (remarks), ST/STE list, contract, UIC, expected return date, ship to (UIC and address), ship to contact (name and phone). The closest thing to this form in DPAS is the Issue Receipt form. This form does not have some information which used to be on the "C-List." Also, the Issue Receipt is only available once a UIR is Issued. NAVSUP WSS requires a form be generated upon the completion of a UIR on their end (once the UIR's status changed to PK-Picking). As of now, they have to take screen shots of the UIR page to provide to PCOs and vendors to show we have completed the request. A sample C-List from eTIMS and an example of what the new form should look like will be provided with the submittal of this SCR.

Recommended
Create a new form that includes all information as the provided C-List, or update the Issue Receipt to include this information.  The information that should be included on the form should be: Unit Issue Request Established By, Established Date/Time, To, Request or Transfer #, Reportable Commodity Type, Remarks (mainly for TAC information), Tooling List, UIC, Account Name, Expected Return Date, Ship to Address, and Contact Information of UIC Custodian.  Make this form available to view and print when the request is "In-Process" or "Pk-Picking" status. Also make this form available during the Unit Issue Transfer process.

Mission Critical
Mandated. Vendors and PCOs require some type of documentation to use as a receipt that the UIR has been started/completed. DCMA uses this documentation when inspection occurs, PCOs use this document when modifying their contracts.

Benefits
This solution will create a formal document that we can use as proof of completing a UIR. It will improve accountability and standardize the UIR process.

Users
This change will impact not only users of DPAS and the ST/STE community, but DLA, NAVSUP WSS, and NAVAIR PCOs/ACOs. Vendors also rely on a formal document as an inspection point that a UIR has been completed.

Description
There are 3 categories of ST/STE requests:

1. Warehouse Requests (ST/STE is stored at a warehouse and is requested to be shipped to a location for usage)
2. Contract Transfers (ST/STE is staying at the current location, but changing its contract accountability)
3. Loan Extensions (ST/STE is staying at the current location and being used under the current contract, but the expected return date needs changing).

The Unit Issue Request process works well for warehouse requests. However, for Contract Transfer Requests, utilizing the existing Unit Transfer Request process does not give us the ability to update the expected return date. There also isn't a separate process to allow for updating return dates when processing Loan Extension requests.  Lastly, Open Warehouse Actions for Unit Returns are not updating when an expected return date is updated.
The work around we have been using in order to add return dates is to return ST/STE to the warehouse, then issue it back out with a Unit Issue Request with a return date. This is creating unnecessary rework and longer touch times and cycle times to complete requests.

Recommended
Incorporate the ability to add an expected return date to the Unit Transfer Request process and the ability to update the expected return date to ST/STE on loan (without transferring the contract). Accommodate the Contract Transfer and Loan Extension Requests described above.  Open Warehouse Actions for Unit Returns need to be updated when expected return dates are updated.

Mission Critical
Mission critical. ST/STE must have accurate expected return dates in order to have proper accountability and traceability.

Benefits
This implementation should reduce the cycle time to complete Unit Transfers and Loan Extensions by at least 67%.

Users
This change will impact not only users of DPAS and the ST/STE community, but it will improve fleet readiness by allowing us to complete requests much faster than we currently do.

Description
Each Program Office/Commodity Type has a responsibility to do a wall-to-wall inventories of all government owned property.  When conducting physical inventories within DPAS, often multiple commodity types will show up in one location.  This is a problem because DPAS will not let one commodity type to reconcile their inventory when another commodity type is in the same location. 

Recommended
Recommending that when conducting physical inventories, let each commodity type reconcile the ST/STE inventory they own within that location.   

Mission Critical
Mission critical.  In order to be FIAR audit compliant, the program offices must be able to reconcile their inventories within DPAS.

Benefits
This correction would all for all commodities to complete physical inventory reconciliations and be in FIAR audit compliance.

Users
This change will impact not only users of DPAS and the ST/STE community, but it will improve fleet readiness by allowing us to insure that the ST/STE inventory is 100% accurate.

Description
NAVAIR is responsible for managing Special Tooling/Special Tooling Equipment associated with various weapon systems/reportable commodity types.   Manufacturing numbers that are created by vendors are used for the stock numbers of the tools.  However, the vendors' manufactured numbers have been known to be 25+ long.  The length of these numbers are not standardized across vendors.  More than 15 characters are assigned to ST/STE to uniquely identify the tool.  As such the current solution prevents the use of the Stock Number field and the associated capability within the DPAS system.   The Special Tooling Identifier is part of the Stock Number Description Field along with the Noun.  In addition, this practice makes it difficult to utilize the Master List Capability to building Tool to Tool and Tool to Part relationships.
The conversion into DPAS utilized a unique identifier from the source systems primary key, but after conversion future entries will require the generation of a unique DPAS key.  Loading large numbers of ST/STE from OEM will be further complicated as the OEM assign the Tool ID and the current practice of using the Stock Number Description will not trap duplicate entries on the Catalog.

Recommended
Request the expansion of the current 15 character limit of the Stock Number field to 30 characters in the Warehouse Module to accommodate future Special Tooling and Special Tooling Equipment (ST/STE).

Mission Critical
Mission Critical.  Over time the management of ST/STE by NAVAIR will be hampered with duplicate Catalog entries due to the 15 Character limit in the Stock Number field.  Future assignment of Inventory to the catalog and asset reporting will be hindered.  Duplicate Stock Number entries (via a description) will challenge audit-ability of this data.

Benefits

1. Tight control of the Tooling Catalog
2. Reduce workload on finding tooling associated with weapon system BOMs
3. Full benefit and reporting capability offered by the Stock Number Field
4. Easier loading of future PPSA files
5. Elimination of duplicate Catalog entries and association of Inventory to Catalog entries, removal of future audit findings.

Users
This change will impact current Navy ST/STE community and potentially the Air Force ST/STE community.  Additionally any future or current community for which the Stock Number field proves to be too short.

Description
Require a report of all transactions for a date range.

Recommended
Create new report, like the Increase Decrease Actions report, that captures all changes to asset records, not just Increase/Decrease.

Mission Critical
Mandated by agency Process Cycle Memo (PCM) for auditability.

Benefits
Improves accuracy and enables assertion of completeness.

Users
All DPAS users in our agency.

Description
The process for requesting access to DPAS is antiquated/not user friendly and is an analog process.  Propose automating the entire access request process and housing it on the DPAS site.

Recommended
Recommend automating the DPAS access request process by developing a process and housing it on the DPAS site.  Many sites the DoD uses have automated access request systems housed on the site access is being requested to.  Current DPAS access process has users download documents from the DPAS site, fill out the Documents, route for signature, and then have the IO review and upload the documents on the DPAS site.  Recommend a virtual access request system be housed on the DPAS site and automate the routing and review process like many other DoD sites.  The previous system utilized for IT asset Management AFEMS/AIM had this capability if an example is needed.

Mission Critical
Yes, automating this process would save hundreds of man hours spent downloading, reviewing and then uploading documents.  Documents can be created virtually and can disperse data where needed.  The current process is extremely cumbersome and time consuming.  So much to the point where SAF/A4 has stood up a help desk and hired contractors to process access request documents for users.

Benefits
If a user requesting access can do so on the site without downloading documents and routing them, hundreds of man hours can be saved and data integrity will improve by limiting the selections a user can make and routing the request to the appropriate approval authorities.  The automation of this process will save time for the user, IO, DPAS Security Team and any other offices/agencies currently involved in the access request process.

Users
Yes, this will affect all users of DPAS.