From the accepted answer to this question there have been times when astronauts have overslept.
The morning started disastrously. I slept through two alarms, one set for 0600 and another a half-hour later to remind me to take some COE pictures. My body apparently went on strike for better working conditions.
Given the intense scheduling pressure, what are the procedures for handling a thirty minute or more oversleep?
I'm probably going to miss actually answering your question about a procedure for handling oversleeps, if one exists. I think this answer will be worthwhile info on scheduling on the ISS anyway.
First, though, the closest thing I could find to a crewmember answering your actual question. This is from NASA/TM-2010-216130, the first of the two Stuster papers I linked previously.:
Skipped breakfast and finally made up the work and time. Otherwise it would have been a fairly nice pace today.
Schedule is a frequent subcategory of journal entries in both Stuster papers. Both have a portion of "Section 4: Implications" dedicated specifically to "Schedules and Time-Related Stress." Recurring themes to do with scheduling are that the ground schedulers have difficulties making good estimates as to the length of time any given task will take, and so schedules are often blown even without sleep issues.
Only 30 minutes [were scheduled] to execute a 55-step procedure that required collecting 21 items. It took 3 or 4 hours.
Had an uneventful rendezvous and docking, but then had to work quite a few hours that day in order to unpack the Soyuz and ready it for an emergency landing if necessary. I found myself getting pretty inefficient; by the time I go to bed tonight my work day will have been about 27 hours, and that’s on top of 2 nights with pretty minimal sleep. I don’t know what could be done about it, but I think they should give us time off after docking.
It has been a pretty tedious week with tasks that were clearly allotted too little time on the schedule. Talking to [the MCC] today, I realized he just doesn’t understand how we work up here.
Several of the procedures, as usual, just took much longer than timelined. We have some tasks, as is too often the case, that were written without our input and which we never actually performed, except on paper. [Erin's note - I have bad memories of trying to develop software procedures as the software developer. Quite the CF. Sorry astronauts, I tried.]
There's more in the second paper, NASA/TM-2016-218603:
I suspect the reality is that few, if any, have been able to accomplish the tasks on-time, at least this early in flight before we have locations and common procedures memorized. Telling the ground that it took longer to perform a task than scheduled is an admission of lack of ability. And telling the ground a little more privately, through typing a crew note in OSTPV, well, takes even more time. It’s low on my priority list when I’m pressing on to the next task.
The fatigue from these busy weeks comes not from physical labor but from mental strain. No matter what the ground tells us, we still feel the need to chase the red line on OSTPV. And we are constantly aware that the ground is watching and evaluating.
Essentially: you just do what you can. There's an ongoing feedback loop between the schedulers and the astronauts. A lot does have to get done, but ultimately the crew and the schedulers are both human and the schedule will inevitably take hits from that.
Each day starts with a "postsleep" period that allows time for breakfast, getting dressed, personal care, etc. (as shown in the OPTIMIS screenshot below). Postsleep is followed by the DPC (Daily Planning Conference) where the ground touches base with the crew before starting the workday. That's a blue-banded activity, which means it must be done at the scheduled time. If a crew member isn't out of their sleeping quarters by then, I'd assume the rests of the crew would wake them up.
There's no defined procedure if a crew member oversleeps, but the lost time will eventually be absorbed/replanned in the day's schedule by flight controllers in MCC-H and POIC. Doing so was one aspect of my job when I was a POIC Operations Controller. Here's an excerpt from one of my console logs dealing with shuffling schedules of several science experiments (crew member names redacted, since no one wants to be called out for running behind):
FE-2 is wrapping up PCG13, and moving on to the stow portion of the activity.
MELFI 1 Dewar 4
Open: 12:34:51
Close: 12:35:11
Flight asked if there's anything we can give up on the timeline, since FE-3 is running behind on her MCA install for JSC. He specifically asked about Lighting Effects. We informed him it had already gotten kicked off of yesterday's schedule, but we'd look into it. I asked PCG13 if they could give up at least 40 minutes, since FE-2 did an extra plate today, and they concurred. TCO pointed out it's got a 3 hour constraint prior to presleep, so LTE would have to go at the beginning of PCG13 tomorrow, starting at 1400, with PCG13 starting at 1440. I relayed all to POD, and Flight decided to keep it as hip pocket, so we may not end up giving up LTE after all - we'll see!
Update: FE-3 is back on track now that she's working on Sextant Navigation, so it looks like we'll get the LTE in today. However, PCG13 confirmed they no longer need the 2.006 Rehydrate procedure on tomorrow since FE-2 did it today, and the 2.007 PCG13 Card Fill can be shortened to 2 hours in duration. PD agreed sliding everything to the right would work for them, so if it ends up planned differently we'll need to notify PD again.
The backroom planners would take the information from those logs and re-plan the next day accordingly.
Acronyms used above:
