Probably a bleed-over from the embedded side. Spent a lot of years working embedded control systems for NASA and DoD - bare metal systems, often interrupt driven - and it was common to have 50% margin requirements. They know those systems will grow over time, and they often have lifespans measured in decades.
That would make sense, i hadn’t put that together but they had a lot of embedded control systems. This was water treatment but entirely separate from the control systems but i can see them having that a standard requirement
So was it a government (state or federal) water treatment plant? If so, I can tell you how it happened. The government contracting agencies have boilerplate text they’re supposed to add to contracts to make sure salient requirements get flowed. They’re supposed to delete or tailor anything that doesn’t make sense, but the contracts people aren’t usually very technical. We had requirements flowed to us about password management and account monitoring, but no one logs into a rocket engine or a torpedo. When we’d point it out, they’d say “oops, we should have deleted that.”
Not in the US, our water infrastructure was sold off in 90s but that makes sense. Was probably something similar
They held us to it though so they overpaid for hardware beyond their needs and we forced the software to run slower
Probably a bleed-over from the embedded side. Spent a lot of years working embedded control systems for NASA and DoD - bare metal systems, often interrupt driven - and it was common to have 50% margin requirements. They know those systems will grow over time, and they often have lifespans measured in decades.
That would make sense, i hadn’t put that together but they had a lot of embedded control systems. This was water treatment but entirely separate from the control systems but i can see them having that a standard requirement
So was it a government (state or federal) water treatment plant? If so, I can tell you how it happened. The government contracting agencies have boilerplate text they’re supposed to add to contracts to make sure salient requirements get flowed. They’re supposed to delete or tailor anything that doesn’t make sense, but the contracts people aren’t usually very technical. We had requirements flowed to us about password management and account monitoring, but no one logs into a rocket engine or a torpedo. When we’d point it out, they’d say “oops, we should have deleted that.”
Not in the US, our water infrastructure was sold off in 90s but that makes sense. Was probably something similar They held us to it though so they overpaid for hardware beyond their needs and we forced the software to run slower