I think you mean part or piece reject rate ... machinery inevitably requires maintenance and tweaks now and then. But I know from personal experience that in some penny pinching piece work industries, a measurable failure (meaning repair needed) rate for the production equipment is considered too high and will cause the owner of said equipment to start looking for something better.
George
Probably it could be handled by Windows only Monday through Friday, when staff is around to fix possible Windows hiccups. A blue screen on Friday night would leave the fermentation without control for longer than your proposed 2 days.
Obviously extending a 10ms "hard" realtime requirement to 48 hours doesn't make it "soft". It's still a hard one, although possibly easier to achieve.
A truely "soft" requirement would be if management decides to sell the beer at a lower price (eg under different brand), when fermentation went wrong. Then it would be "desireable" to meet the soft realtime requirement, but not "necessary".
Marc
Thanks for the pointers, I will look into some of them.
Paul
You're right, and that's an important point.
If we were certain that two extra days really ruined the beer, then you'd be right -- it's a hard realtime requirement. However, an extra two days might not hurt, either. It depends on the yeast and the temperature and a number of other things (although in a real system, these things could be controlled to some degree). I's still characterize it as a "soft" realtime requirement.
That's another way it could be a soft realtime system.
Ed
Have something to add? Share your thoughts — no account required.
Ask the community — no account required