9 SYSTEMS: INTERNATIONAL SPACE STATION PLANNING—A ROADMAP TO GETTING IT ALL DONE CHAPTER 1 Figure 5. The development cycle of the STP and OSTP generation cycle starting 7 days prior to the Day of Execution (Day of Exe) with each day indicated as Execution, or E, minus the day. All Planning Product Change Requests (PPCRs) are due 3 days prior to execution. The final plan is uplinked to the crew the day before execution and reviewed during the evening Daily Planning Conference (eDPC) on the planning or orbit 3 (O3) shift. The beginning of the execution plan development process begins 2 weeks prior to a week of plan execution with the development of the WLP. The LRP team begins WLP development by revisiting a particular week from the OOS to update the planned information based on recent changes encountered during the execution of the increment since the OOS was published. Figure 4 shows the WLP plan, which has a detailed list of crew activities assigned to each crew member for each day of a particular week in the increment, in addition to any significant non-crew operations on each day. The operations team or payload organization provides the crew time requirements for each crew activity planned and summarizes to ensure compliance with GGR&C crew time constraints (e.g., 6.5 hours of schedulable crew time each crew workday). The WLP plan looks similar to the OOS, but it contains the information for only a single week of the increment, as can be seen in Figure 4. Up to this point in the planning process, managers have planned and assigned all tasks to specific days or weeks of the increment, with an emphasis on crew time availability. Now, planners look at the details of the planned activities and begin the process of creating a timeline or schedule of events. Other constraints and resources, such as communications coverage, equipment use, day/night cycles, data bandwidth availability, etc., are considered at this phase of the planning process, in addition to crew time constraints. Details of unique activity constraints are contained in an activity database maintained by the planners as well as in a Gr&C document created by the international planning team at the start of the increment. For example, it might be the case that astronauts cannot eat or perform certain types of exercise within a certain amount of time prior to a medical procedure, such as a blood draw. Operations that were not completed earlier in the increment due to problems or a lack of time may, depending on priorities, get pushed to a later week. Although the program previously baselined the requirements for the increment, changes are inevitable. During the increment, the ISS Mission Management Team (see Introduction) approves the updates, which the planners also incorporate during this time frame. Once drafted and before implementation, the IEPT, flight controllers, and program managers conduct a final review to ensure everything fits within the requirements and needs of the program, as well as within the capability of the crew, ground team, and vehicle. This level of attention to detail is required since crew time is extremely precious and any wasted time can impact the success of the program goals. The Final WLP then serves as a type of contract between the flight team and the ISS Program regarding what will happen for that particular week. The STP is a timeline derived directly from the WLP and consists of all activities to be performed on the ISS for a particular day. Figure 5 shows the development timeline for an STP covering 1 day of ISS operations to take place 7 days in the future. As mentioned, an STP is created (following the template outlined in Figure 5) for each day represented in the Final WLP. The STP is presented as a graphical timeline of crew and ground activities for a particular day (Figure 6) to be used as an output from a common planning system shared by all ISS planning communities. The format includes horizontal bands for individual crew member activities, trajectory information (day/night, Tracking Data Relay Satellites for communications coverage, Russian Ground Sites, Daily Orbit Number, spacecraft attitude), systems and payload commanding, automated systems and payload operations, and ground