I do like it when you quote technical IT terms.You're talking boll@x.
I like it even more whern you make assumptions about my knowledge of issues.You've no knowledge of the contractual relationship of the parties.
Did anyone say they did?You would need to look at the warranty clause in their contracts. You will find both Oracle and SAP do not offer such warranties.
Talk about strawman arguments.
SAP is a software house. Systems Application Programming, or something like that. They design and rollout software solutions. They choose the best 'programme' on which to develop the system.e.g. . pretty clear - buy my software and make sure its fit for the purpose you wish to use it for.
For sure they will install some systems off-the-shelf for scenarios where a previously ready-made package will suit. I doubt they will tell you that. But they don't sell systems for self installation, development and roll-out. Programmes like Oracle will do so.
But they weren't the main contractor, Fujitsu was, so that discussion is irrelevant.
Why are you trying to teach granny to suck eggs?They are not alone. This is entirely standard, across the whole industry and is why System Integrators (such as Fujitsu Services) exist. Bring together different components and write software code on the platforms you have chosen to build a system for the customer according to their requirements.
Still trying to teach granny.Then we have standard warranties in IT services.. Typically they will have a limitation of Liability clause, capping exposure for damages, then they will have a reasonable skill and care clause to limit professional negligence and lastly they will limit their obligation to re-performing the defective service. That basically means if I got it wrong and you can show I didn't use reasonable skill and care, then my entire liability is to redo the specific defective service.
Still trying to teach granny.Now public sector contracts are rather different, but in the case of Horizon, there will have been external consultants involved in the requirements gathering and functional design. There will have been design specification and testing specification signed off by the client and there will have been acceptance test completed and signed off before go-live. This is how IT project are done.
I think you're boring everyone now.
And Horizon was evidently badly designed to not deal with network outages.It would be inherently bad design for an integration between two systems to rely on a network. Good design would handle transaction failure due to any cause. i.e. if I cannot guarantee the whole transaction on all the required systems, I must abort all of it.
The proof was in the pudding, and they replaced it.
Finally we got there.