Your tax dollar at work - Army's $2.7 billion dollar cloud based computer supposed to be helping troops doesn't work (Congress, Whitehouse)
Please register to participate in our discussions with 2 million other members - it's free and quick! Some forums can only be seen by registered members. After you create your account, you'll be able to customize options and access all our 15,000 new posts/day with fewer ads.
Not buggy software, but access software that had too many requirements that took it from a simple to use program and turned it into a multilevel program with too many embedded nests.
Not buggy software, but access software that had too many requirements that took it from a simple to use program and turned it into a multilevel program with too many embedded nests.
Oh? I thought it worked "just fine", that it was just a matter of "the Army doesn't have a strong enough wi-fi connection to connect to it." The guy who posted that sounded very sure of himself, actually.
I will say, though, that "too many requirements" is one of the ballsier excuses for IT project failure that I've heard. Couldn't you just have said "It was too hard"?
Research DCGS-A on how it connects to the network in a desert environment where you can't set up a fixed antenna and how continuously moving nodes in the air in non-secure airspace can't hold a continuous wifi signal.
Or does this need to made simpler to understand for the simple-minded?
its just the 30 DIFFERENT systems that the army used most dont match with each other
its the same with the army's HR systems DIMARS(a civilian HR program) was supposed to take over fram RLAS, RSMA, AHORS, ITTRS, ATTRS etc....for the army( the LARGEST EMPLOYEER in the world)
one of the problems ...the army uses a SSN , not a payroll number...the other problems with rolling 30 datebases into one...MISMATCH
its just the 30 DIFFERENT systems that the army used most dont match with each other
its the same with the army's HR systems DIMARS was supposed to take over fram RLAS, RSMA, AHORS, ITTRS, ATTRS etc....
one of the problems ...the army uses a SSN , not a payroll number...the other problems with rolling 30 datebases into one...MISMATCH
See, someone who didn't need breadcrumbs.
But back to the other posters: Research the Bradley Fighting Vehicle. Look at what it was originally designed to do and all the modifications to it through numerous years and then what it bacame, then compare its original cost to its total cost. Then trade the word Bradley for this system.
Quote:
I will say, though, that "too many requirements" is one of the ballsier excuses for IT project failure that I've heard. Couldn't you just have said "It was too hard"?
So these fools subcontracted two different software vendors that can't "talk" to each other for a communications system? Yep sounds about right for government work.
Jeez who said use walkie talkies? Yep I think the troops have probably already tossed this thing off a cliff somewhere over in the "sticks" and is back to doing what they know. Adapt and overcome.
Research DCGS-A on how it connects to the network in a desert environment where you can't set up a fixed antenna and how continuously moving nodes in the air in non-secure airspace can't hold a continuous wifi signal.
Or does this need to made simpler to understand for the simple-minded?
Why wouldn't they use satellite telecom connections - isn't that enough wi-fi for you?
Too many protocols. but your welcome to research it and bring back your findings to this thread.
There are still people using satellite phones, so the 'protocols' must be functional, even if the defense phones aren't
Please register to post and access all features of our very popular forum. It is free and quick. Over $68,000 in prizes has already been given out to active posters on our forum. Additional giveaways are planned.
Detailed information about all U.S. cities, counties, and zip codes on our site: City-data.com.