DPS Release Causes SIT Errors

From the latest DPS Smart Book, a screen shot of SIT changes in DPS Version 1.4.08, installed over the weekend.

The last DPS update was installed with very few problems. So when the next major upgrade, version 1.4.08, was installed over the weekend, lots of people were wondering if it would be another “quiet” installation. Unfortunately, it appears that the recent update has caused some significant problems related to the SIT process in the DPS computer system.

The biggest problem caused by the update is that DPS is no longer automatically issuing SIT control numbers for shipments without a delivery address. After the update was installed, requests for SIT on all shipments, including those with no delivery address, require the TSP to create a SIT request. That request goes into a queue in DPS which must be monitored and approved by a PPSO.

It is our understanding that SDDC and JPMO-HHGs have acknowledged this problem, and are working with the developer to find a solution to reverse this inadvertent change. Until that fix is implemented, it will require extra work on behalf of the TSP, and especially the PPSOs, who must now manually perform a task that was being done automatically. Although it is the slow season, many PPSOs are already complaining of being understaffed, so this extra duty will likely not be appreciated.

We have also heard reports that since the update to DPS, some bases have been unable to issue SIT control number on certain shipments. It is unclear at this point how widespread this issue is, or if there is a common denominator between the problem shipments. However, considering there has only been one business day of use under DPS version 1.4.08, I would not be surprised to hear more about this issue in the coming days.

The final SIT related glitch we have heard about is more of a nuisance to the service members than an ongoing problem. Apparently the installation of the update inadvertently caused DPS to send lots of emails to service members informing them that their storage had expired. These emails referenced shipments that were completed years ago, which caused a bit of confusion and some unnecessary phone calls, but at least it appears to be a one-time problem.

It is not unexpected that the large number of SIT related changes in the DPS update caused the SIT process to experience problems. Now the question is how quickly can these problems be identified and fixed? If it is done in a matter of days, then these problems will be a blip on the radar. However, if they drag on for weeks or even months, then DPS release version 1.4.08 will likely be remembered as the one that broke SIT.

Have you seen any of the SIT errors since the DPS update? Do you think they will be resolved quickly? Please use the comments below to share your opinion.

Related Posts

1. CWA 3.7.3 Release Expected Today - March 1st, 2006
2. Million Dollar Audit Exception Problem Fixed; Rating Errors Return to Hiding - July 13th, 2011
3. CWA Software Release 4.3 - July 2nd, 2007