Description:
DPAS currently receives updates from multiple external cataloging systems to include AESIP(AEMM). When DPAS performs a validation of the data to determine which fields are be updated, there are instances where DPAS does not perform the required update. For example: One of the fields that is sometimes modified is the Management Code (bulk vs. serially managed). For this to occur within DPAS, e.g. serial to bulk, the user will lose all of the serial nbr / uii data that is present in DPAS. If it is updated from bulk to serial, then the user must provide serial nbrs (minimum value of data) for the entire asset qty on hand prior to DPAS being able to process the request. This poses issues when the cataloging system made a mistake with that update. If it was going from serial to bulk, then when the cataloging system changes it back, the DPAS user would need to provide all of the Srial Nbrs / UIIs. DPAS doesn't know which assets were issued during the interim. This is no small feat given there could be thousands of assets involved. BLUF: DPAS needs to maintain synchronization with an external feeder system in a prudent manner.
Recommended:
To enable the user to validate changes in master catalog data prior to implementing the change that could result in a catastrophic mistake caused by the external cataloging system, DPAS should incorporate a process to display the pending update to their catalog and the reasons why DPAS did not systematically process the update upon receipt. This will enable the DPAS user to see the impact and if they non-concur to consult with their external catalog team to confirm the change is correct. If there is concurrence, then enable the user to apply the update to all asset records that the catalog is associated to. If the catalog team was incorrect with change when they processed the update, DPAS user can deny the update. If correct, then allow for the user to accept the update with DPAS providing the necessary screens to enable the update to occur. In the end, every update received from an external cataloging system must be able to be processed by DPAS.
Mission Critical:
DPAS must be in sync with the authoritative source. In this instance AEMM.
Benefits:
Implementing this solution will provide users greater visibility to the updates coming in from the external catalogs and ensure they have a way to correctly align their catalogs to what is defined by the Source of Truth. Ensuring this alignment will increase data integrity when interfacing with other external sources whom also pull data from FEDLOG
Frequency: Daily
Users:
This would directly affect the stock number catalog which impacts all associated assets in the system.