Coordinate a crew across a partnership

Chris Hadfield’s Expedition 34/35 responsibilities included science and robotics. CSA records his participation in Dragon capture and berthing in March 2013. During the May 11 spacewalk by Tom Marshburn and Chris Cassidy, Hadfield supported the operation from inside the station. Supporting a spacewalk is a different role from being outside in a spacesuit.

NASA’s April 2, 2013 photograph documents Hadfield and Thomas Henry Marshburn removing communications equipment in Destiny to install a replacement unit and associated cabling. The scene shows another part of a crew’s work: maintaining the services on which experiments and communication depend.

These duties illustrate a system of shared responsibilities. A national corps supplies people; a mission connects them to spacecraft, laboratories, controllers and researchers. A completed scientific activity may depend on earlier maintenance performed by someone outside the experiment’s immediate team.

Consider a fictional planning window of 40 minutes. A maintenance task needs two crew members together for 15 minutes. A later sample task needs one of them for 20 minutes after maintenance is complete. The sequence takes 35 elapsed minutes, leaving 5 minutes in the window.

The same plan consumes 2 × 15 + 1 × 20 = 50 crew-minutes. Crew-minutes add the time contributed by each person; elapsed time measures the clock duration. A plan can fit the time window while still requiring two available people at the same time.

If only one trained person is available, the maintenance task cannot simply be assumed to take 30 minutes instead. Its requirement for simultaneous participation may be part of the task design. These invented values illustrate resource constraints, not an actual station schedule or maintenance procedure.

Elapsed time and crew time differ

CSA’s mission-specific training description includes spacecraft systems, robotics and rehearsals in simulators and other practice environments. An analog setting allows teams to work through tasks, but it does not reproduce every orbital condition. Successful rehearsal is evidence for the conditions tested.

In an original handover example, a departing operator reports that a unit has been replaced but its functional check is still pending. The next operator should inherit both facts. Writing only “replacement done” would hide the unfinished verification and could distort later planning.

The same distinction improves historical records. Preserve completed work, unresolved tasks and the timing of a change in responsibility. That makes the people’s contributions easier to understand than a list of launches or a set of national firsts alone.