Operators away: absence without a stand-in
Operators are ill or on leave, and the line runs with whoever came in: you want to see what absence costs before deciding on a stand-in or a larger crew.
Built in A field or setting does it directly.
How
Use a shared operator pool (Project settings → Operators → Shared operator pool, shared_operator_pool: true) and set Absence to the share of operators away on a day (operator_absence_pct: 8). Each day each operator is away with that chance, for the whole day, and no one stands in: the crew is smaller that day. An operator busy when the day starts finishes the job first. The draws have a random stream of their own, so the rest of the run (task times, breakdowns) is the same as without absence.
The results give the days, the operators away on an average day and the fewest at work (Run details → operator pool → Absence). To see what a stand-in is worth, run again with one more operator in the pool.
Absence by shift, planned holidays and a qualified stand-in for a given station are not built in.
Check
Four manual stations, one operator each, from a pool of four, at a 60 s takt for ten days. With a 25% absence an average day has 0.7 operators away and the worst day two: the line makes 12,948 control units against 14,400 with the full crew, and misses its demand.