Skip to comments.DEFENSE PLANS TO REPLACE 19-YEAR-OLD RETIREE PAY SYSTEM
Posted on 05/14/2014 4:55:12 AM PDT by markomalley
The Defense Department has decided to retire its 19-year-old retiree pay system written in antiquated computer code and replace it with a lower cost, easier to use application based on off-the-shelf technology.
The Defense Retiree and Annuitant Pay System, or DRAS, maintains military pay accounts for more than 2.6 million military retirees, former spouses and survivor beneficiaries totaling $40 billion a year. The system was introduced in 1995 and is based on Common Business Oriented Language computer code of the time.
DRAS uses antiquated mainframe technology dating back to 1980 that has exceeded the end of its planned lifecycle, the Defense Logistics Agency said in a request for proposals released last week for a new DRAS2 to go to the Defense Finance and Accounting Service.
The current, aging DRAS, the solicitation said, has 40 internal interfaces between subcomponents for data file transfers, and over 220 external interfaces resulting in a system that is difficult and costly to maintain and modify and is highly susceptible to errors and rework.
The old pay system only offers limited automated data validation checks, does not conform to the current Defense data standard taxonomy and does not have a common data environment (master data model). Further, the data elements are not compliant with Standard Financial Information Systems requirements, DLA said, explaining the need for a new system.
DLA seeks a vendor versed in the seven-stage Business Capability Lifecycle for planning, design, acquisition, deployment, operations, maintenance and modernization of Defense Business Systems.
The RFP calls for the winning vendor to develop new system architecture, a functional and technical design, convert and manage data migration from the old to new systems, develop new data interfaces, and provide a software development methodology, among other tasks. Interested vendors must reply to the RFP by June 4.
Paul Strassmann, an information technology consultant who served as director of Defense Information from 1991 to 1993, doubted the departments timing and priorities with the DRAS2 contract. DoD should not replace retiree systems until it can be integrated with the employee personnel database, he said. There are too many duplicate databases involved in human resources. The savings are in overhead costs, not in the operating costs on hardware.
Strassmann added, With [computer] security spending 19.3 percent of its 2015 funding, and a 6 percent cut in the IT budget, there is no money available to replace a legacy system. DLA should be allocating scarce funds to improve the security of the legacy retiree pay system, which is likely to be vulnerable to hacking and corruption, before spending money on anything else.
I guess literacy is a bit much to ask.
IOW, it’s in COBOL, and no one wants to or has learned how to hack it? They want a phone app...
I think the company that did the first pass on healthcare.gov is available. The VA should dial up Michelle Obama for the “right” contacts.
They deployed a mainframe-based system, using COBOL, in 1995?
COBOL was considered a "legacy" system a decade earlier.
If you don't believe me, check the link in the article. (in red and underscored). And yes, there were still a lot of mainframes using it--which made Y2K a potentially big deal before billions were spent on system remediation.
Yep. Archaic now, but difficult to hack. But they want a modern system, meaning some of us old folks will be robbed blind.
That’s what I figured.
You say that half jokingly. But if you were familiar with how the DLA Troop Support contracting office worked (that is the contracting office that is running this procurement), you'd realize that your statement is not too far off the mark.
Good God...what’s THIS gonna cost us?
That sounds more like an RFI than an RFP. An RFP is very specific with an available statement of work for potential contractors to formulate the costs of a bid.
Yeah... odd that. Since COBOL still acounts for a huge majoraty of account code out there.
Maybe because it was written for accounting? Naw... can’t be that... right?
So they’ll replace it with a system that costs 10x to build and 100x to maintain. One has to love... “Progress”.
The people who can't build a website are going to replace an accounting system written in 'ancient' computer language?
What could possibly go wrong?