Problems with the ground system would have "put current GPS military and civilian capabilities at risk."
See full article...
See full article...
We should all keep this speech handy. Ike was definitely a prescient President.
View: https://youtu.be/Gg-jvHynP9Y?si=wTBs1sDu6zmC6nzF
Word salad.the challenges of onboarding the system in an operationally relevant timeline proved insurmountable
Since the product was "delivered" last year, and the Space Force "accepted" it, despite the remaning problems, the RTX program manager and lawyers are no doubt breathing a huge sigh of relief. I imagine that puts RTX on pretty firm legal ground for a "no refunds" policy.RTX Corporation is obliged to give us that money back, since they failed to deliver a working product, right? … Right?
Since the product was "delivered" last year, and the Space Force "accepted" it, despite the remaning problems, the RTX program manager and lawyers are no doubt breathing a huge sigh of relief. I imagine that puts RTX on pretty firm legal ground for a "no refunds" policy.
I think it's reasonable to ask some pretty pointed questions of the procurement team who wrote the contracts and acceptance criteria that made it possible for a non-functional system to be signed off as "delivered".
Nice work, if you can get it.Imagine being able to get away with delivering results like these for 16 years.
And getting paid multiple billions to not deliver. Hey congress? I could fail to deliver for half that amount!Imagine being able to get away with delivering results like these for 16 years.
We should all keep this speech handy. Ike was definitely a prescient President.
View: https://youtu.be/Gg-jvHynP9Y?si=wTBs1sDu6zmC6nzF
And STILL KEEP THE MONEY.Imagine being able to get away with delivering results like these for 16 years.
Translation: it doesn’t work and it never willWord salad.
I'm sure it's not quite that simple but it is absolutely flabbergasting how they managed to fail this hard. Well, that's what I would say, except I know what old guard defense contractors are willing to pay software engineers, so the results are somewhat to be expected.Get me $100MM and I will get 6 engineers together than can have this system running at design parameters in 2 years.
The more money and the more people and the more time allotted translates to shitty execution, I have seen it in different shades of gray a couple of dozen times in the last 25 years in my software career.
1/2? Are you trying to fleece the American Public?! I can deliver that same results at 1/3 the cost!And getting paid multiple billions to not deliver. Hey congress? I could fail to deliver for half that amount!
Less it was terminated and more that the government accepted delivery 10 years late after paying over twice the original price then decided it was a pile of crap and trashed it. And no Air Force Generals were punished in the process for dereliction of duty or civilian Project Managers fired for failure to properly supervise the project.I am encouraged that the government was able to terminate a program. I will leave it to others to debate if the program was worthy of our money or not.
Because it was way too late as the money was already spent. The time to stop this was in 2016 when they missed the first deadline. Or any of the 2000 chances since then the Air Force and Space Force had to cancel.gee I wonder why DOGE didn't flag this one!
And they will never get another new contract with the government ever again, right? … right?RTX Corporation is obliged to give us that money back, since they failed to deliver a working product, right? … Right?
Tell me you've only done trivial work without saying the words.Get me $100MM and I will get 6 engineers together than can have this system running at design parameters in 2 years.
The more money and the more people and the more time allotted translates to shitty execution, I have seen it in different shades of gray a couple of dozen times in the last 25 years in my software career.
What debate? It never worked, it wasn’t going to work and it cost twice as much as expected, is a decade late and is going to be thrown away.I will leave it to others to debate if the program was worthy of our money or not.
Tell me you’ve never delivered a project on time without saying it.Tell me you've only done trivial work without saying the words.
Boeing: Hold my beer...Imagine being able to get away with delivering results like these for 16 years.
Having done some Defense Dept adjascent work myself, I am not at all surprised. I have no doubt that RTX does not shoulder ALL the blame here. The Government is an absolutely horrible client to work for and with.Worked on GPS-OCX for 6 months in the late 'teens. Background - over 20 years in aerospace software development. The system integrated the historical code in 4 different programming languages (fortunately, I was fluent in all 4) as well as the new stuff. 3 months into my escapade there, TPTB decided that we should all migrate to the Agile approach to development with almost no training. But the USAF loved the idea. Our morning scrum took over an hour with over 40 people in the room.
TPTB decided that one of the most important changes to embrace Agile was to re-org the seating arrangements. Previously the software people were in groups of 4, movable walls, backs to each other and we all had storage space above on the walls. But no, Agile means groups of 4 in a very large room (seating about 100 or more) in an open space with the computer monitors in the center, and we're all basically facing each other over the monitors. One person sneezed and all 4 of us got sick.
At the meeting when this was announced, someone in the back of the room sent a little piece of paper around with the words "deck chairs again". Plus all the computer had to be replaced because they were not made in the US.
Know who was the USAF general in charge of all this during this period? Hyten. Look him up.
When I left, knowing my background, the security officer was surprised I lasted as long as I did.
Want to know where $XX billions went? I appreciate that paycheck for 6 months.
Word salad.
The problem isn't so much that the systems are so complex. The problem is that the documentation is poor to non-existent and no-one has bothered to actually write down the exact use cases on what software needs to do. There's decades of legacy and lessons learned in that code that is just patch on patch on patch on cludge on hack on fix on patch. The only realistic fix is to replace the systems bit by bit, building on replacing specific functions one at a time. But the problem is that such a thing then can't really work because you need the entirety of the thing to function in one go. And replacing everything in one go is just not a realistic proposition.I've noticed a recurring issue where we've built systems so complex, we can't reliably improve on, or even maintain them. FAA NextGen is another example.
Not so fast!1/2? Are you trying to fleece the American Public?! I can deliver that same results at 1/3 the cost!
Out of those 6 you'll have 1 that gets to work on code that the requirements change for on a weekly basis given ADHD nature of acquisition programs.Get me $100MM and I will get 6 engineers together than can have this system running at design parameters in 2 years.
The more money and the more people and the more time allotted translates to shitty execution, I have seen it in different shades of gray a couple of dozen times in the last 25 years in my software career.