| Sunday | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | |
| 1st shift | – | x | x | x | x | x | – |
| 2nd shift | – | – | – | – | – | – | – |
| 3rd shift | – | – | – | – | – | – | – |
Now, what is wrong with this picture?
Table created with: TableMaker.
24×7
Published
Fighting the automation paradox || Deployment θα κάνουμε φωνάζοντας "αέρα"
Managing organized complexity 
Can I make a wild guess?
“21 (3 shifts for each day) is usually very hard to divide evenly by 5, unless one uses a very special version of Pentium processors”
:)
I was thinking something like this:
– In Greece, most of the time, management requires 168 hours / week of support (that equals 7 days / week) but pays only 40 hours / week.
Only 168? What about shifts, rest after night shifts or weekends, overtime salaries, exceptional conditions (e.g. an accident of one eployee) etc?
24×7 support sounds like an absolute illusion in most (five nines ;-) ) cases …
@Petros:
In my statement above there were two commas missing (now fixed). I think the message is more clear now and in fact we are saying the very same thing. The main difference is that my table can be used in a slide, executive summary or any other means that a pointy-head can read in less than 10 seconds.
It states the problem, the current situation and what needs to be done with almost no words.