Description
DPAS does not provide support for the DLMS 824R (Reject Advice).  The Army is planning to implement DLMS 824R generation/reporting of data errors for TPF transactions (DLMS 527D) that GCSS-Army does not successfully inbound by August 2021.  This SCR is to develop the processes DPAS requires to support the DLMS 824R Transaction Set.

1. The DLMS 824R supports the of MILSTRAP related DLMS transactions, and  other DLMS supply, contract administration and logistics bills transactions, but does not replace procedures for error identification addressed by the DLMS 140A Small Arms and Light Weapons (SA/LW) Reporting, DLMS 870S Supply Status, or DLMS 842A/R DoD Supply Discrepancy Report Reply. The DLMS 824R is also used by DLA Transaction Services for narrative message type rejects for all DLMS transactions subject to rejection by DAAS narrative messages
2. This transaction set is not used to reject a DLMS transmission due to ASC X12 syntax errors that DAAS reports via email.  The DLMS 824R that will be received will come from the trading partner system from their inability to process the transaction for reasons other than what is currently supported by the DoD Supply Discrepancy Report (SDR) process (DLMS 842). 

Recommended

1. Modify the DLMS inbound process to inbound the DLMS 824R notifying DAAS of the support and desired format that DPAS anticipates accepting the DLMS 824R transaction set (XML).
2. Develop logic to route the Reject Advice to the correct module / recipient (PA, WM, MM, DPAS Admin) using the DLMS Transaction Set and Document Nbr of the transaction set that was rejected, and the reason for the reject. 
3. Provide a user view of the rejected transaction to the user (code and text) provided in the DLMS 824R along with pertinent info from the original DLMS transmission, with the capability to mark the transaction as New (Default when a new reject is added), Read (when a user has viewed the transaction), In Process (provide the user with a text field to denote who was assigned to action the reject advice), and Resolved (with a text field for the user to denote action taken) - drops off the view when marked resolved. 
4. The dashboard of each module should be updated to include open DLMS rejects.
5. The design for supporting the DLMS 824R Reject Advice transaction set should provide methods for making the DPAS user as well as the receiving system that generated the reject advice ‘whole’.  This may include providing for the modification of the original data that caused transaction to be rejected, and the resubmission of the DLMS transaction, and in other instances it may include providing the capability to reverse/void the original action the user took providing the appropriate DLMS transactions to the receiving system to make them whole. The actual development of the processes required to make both parties whole may not be in scope for the initial fielding of this SCR given the number of transaction sets that can be rejected via the 824R.  When resources are available, the initial implementation of this capability should be to support the DLMS 527D reject notices.

Mission Critical
Yes. To support DPAS DLMS compliance, DPAS needs to inbound 824Rs

Benefits
Provide DPAS and its customer with visibility and resolution of DLMS data errors.

Users
This change affects customers/users who are generating DLMS transactions as part of the  business processes.

Completed - Release 2021.3 - 10 September 2021

Description
USMC MCCS has a need to systematically update their Real Property that is being managed with DPAS with critical information that is maintained and is available from the USMC real property system.  The data that MCCS requires is not available from the RPIM / DAIS data that DPAS currently imports, or is only updated once a year which does not meet the MCCS requirement in managing its real property facilities / projects.

Recommended
DPAS will develop a real-time import process that provides the capability to upload real property data that will be validated, then applied to existing real property records.

Mission Critical
Yes, without this information DPAS does not fully support USMC MCCS's business needs. It has been endorsed by the DPAS PM as part of supporting USMC NAF.

Benefits
Provides additional information for the customer's real property records and improves the accuracy of those records

Users
Yes, all USMC Real Property users.  It should also be usable by Defense Agencies that utilize USMC facilities that are managing their portion of the Real Property using DPAS.

Description
Request to establish a Naval Special Warfare (NSW) interface to transfer NSW DPAS data from DPAS POR to NSW Data Environment via established GEX channel. Currently receiving DPAS SOLMS data, but need to refine data requirements to NSW scope.

Recommended
Mirror SOLMS interface within scope of NSW data requirements. Replace SOLMS data file with NSW interface data file for relay via established GEX channel. Supporting documents can be sent via encrypted email or SAFE file transfer; please provide email address for receipt and ticket number to reference. To include: data requirements (xlsx), GEX interface agreement (pdf), SOLMS interface WPHRI09 - Asset Data Visibility Feed (pdf), and NSW Data Environment (NDE) ATO.

Mission Critical
Mission critical. NSW Data Environment (NDE) is a consolidated data engineering solution, pioneered and directed by Naval Special Warfare Command, that manages the integration, storage, and distribution of authoritative data from disparate data sources in order to model and analyze data efficiently and effectively. The NSW Operational Data Store (ODS) and the NSW Enterprise Data Warehouse (EDW) are components of the NDE. The NDE data as a service (DaaS) provides mission essential data to a wide variety of approved NSW and US Special Operations Command (USSOCOM) enterprise business systems, analytics tools, business and artificial intelligence, machine learning algorithms and statistical models, robotic process automation, resource management suites, software applications, data lakes, and data marts within the “hub and spoke” model of the Special Operations Forces Data Environment (SDE). The solution supports Special Operations Forces critical ability to develop enhanced situational understanding, fully inform options for decision makers, and wield influence when and where necessary.

Benefits
ISO CNO FRAGO to implement digital competitive advantage to improve accuracy and accountability for DPAS. The solution supports Special Operations Forces critical ability to develop enhanced situational understanding, fully inform options for decision makers, and wield influence when and where necessary.

Users
All. Allows for visual reporting at all levels.

Partially Completed – Release 2022.3 – 04 November 2022

Partially Completed – Release 2023.3.3 – 11 August 2023 

Partially Completed – Release 2024.3.2 – 26 July 2024

Description
Currently if any mass updates or uploads need to be processed, users are required to submit to DPAS via conversion spreadsheet. Then the user needs to wait for the Leidos team has run the file through validation, send the errors for correction and then resubmitted and finally uploaded. 

Recommended
Provide a capability for users to be able to upload conversion spreadsheets for validation and upload.

Mission Critical

Benefits
Reduces workload for DPAS contract support and time that users waits until file is finally uploaded.

Users
ALL

Description
FSM Auth On/Hand report does not break down which authorization id is short or excess. The current report gives a role up for the total allowable quantity and the FReq OReq OAuth for that specific Auth-id.

Recommended
Create a reference table that identifies where the on-hand balance should be applied as the UIC prioritization table outlines

Mission Critical

Benefits

Users

Description
The Air Force needs a file to report the unit readiness status to DRRS based on the data in PA and FSM.

Recommended:
Push report  that combines on-had and authorization quantities to DRRS or have it available to pull. Specific data fields are required on the report

Mission Critical
Services are mandated to report DRRS readiness capabilities IAW CJCSI 3401.02B

Benefits
Improves accuracy and accountability for DRRS readiness reporting

Users
Yes

Completed – Release 2022.3 – 04 November 2022

Description
Anyone with access to the Master Data tab can load or change the Organizational Data Elements for a UIC such as the FAD. IAW CJCSI 4110.01E 'Service Chiefs are required to implement policies, conduct administrative audits and inspections to eliminate and prevent abuse, misinterpretation and misapplication of UMMIPS.

Recommended
Create a profile as a Supervisory Master Data Manager. This role would be the only profile that can make FAD updates or create a FAD 1 UIC.

Mission Critical
IAW CJCSI 4110.01E the Service Chiefs are required to develop and implement policies on the use of and oversight of all FAD codes assigned to units.

Benefits
Improves accountability

Users

Completed - Release 2024.1.6

Description
The Master Data Manager profile allows users with access to manually load, update and delete a AUIC/UIC

Recommended
Recommend an interface to the Integrated Logistics System-Supply (ILS-S) UIC/FAD table to automate the FAD application to the UIC in the Master Data file.

Mission Critical
The equipment managers in the AF deem it as mission critical, as a units FAD code helps the order of importance a unit has as it pertains to procurements and future acquisitions. 

Benefits
Improves accountability, accuracy and oversight.

Users
All users

Description
The Due-In/Receive/Accept process is very time consuming because all items must individually process.  Additionally, all AF Vehicle Management activities order most parts for specific vehicles and current process does not allow the user to mark items against an Asset ID.

Recommended
Recommend adding the option to create Due-Ins and Receive/Accept multiple items in a single transaction under a single Document Number.  Additionally, request adding a "Mark For" field to the receiving process allowing the user to select available assets (vehicles) from the linked Maintenance Activity.  Vehicle selection needs to reflect on the Open Actions dashboard and transfer to all inventory listings. Lastly, request adding Priority Codes to prioritize different vehicle statuses.

Mission Critical
The Air Force vehicle community mandates per Air Force Instruction 24-302, Vehicle Management Chapter 5, all vehicle management activities must track and verify status of parts for all Non-Mission Capable vehicles.  The recommendation of grouping items and displaying Asset ID's will streamline requirement.

Benefits
Grouping items and processing in a single transaction will accelerate practices and streamline tracking procedures.  Additionally, the "Mark For" and Priority Labels facilitates mandated reconciliation practices.

Users
This change will improve part processing operations for all 8,000 Air Force Vehicle Management community warehouse users.