1. Payload Operations and Integration Center MSFC Daily Summary for PDs

2. Objectives 2 What is the Daily Summary? What are the different sections of DS? What are the Generic Guidelines for DS Inputs? What info should be included in DS? What info should be left out of DS?

3. Definition 3 What is the Daily Summary? The Daily Summary (DS) is a real time document intended to provide a concise overview of the upcoming crew day. It provides supplemental information regarding the crew day that is not contained in the OSTP or associated documents. It is a means of asking the crew questions that require brief, non- immediate responses. Inputs may include gotchas, reminders, payload status, constraints, and questions and answers for the crew. It is uplinked daily via JEDI message to the crew.

4. Outline of DS 4 What are the different sections of DS? ISS Key Parameters State of the Station (Systems Notes) Today’s Plan Comments New Task List Items Questions/Answers for Crew Payload Status Today’s ATL (Attitude Timeline) Today’s Control Center Rosters

5. Important DS Sections 5 As a PD, what sections are you interested in? New Task List Items Provides the crew with a summary of updates or additions made to the task list. May include a brief explanation of why a task is added or if there are any constraints. If the activity will be hard scheduled after a certain date, that info should also be included. Note: As a PD team, you may not have any activities which are candidates for the task list; if your payload is a candidate, this discussion usually occurs during your payload planning. Questions/Answers for Crew Can ask the crew an operational question not needing immediate response or answering a previous crew question. Sometimes a DS question can be answered in a DPC, or vice versa. Should require less than 5 minutes of crew time If asking the crew to recall information, questions should be submitted immediately Payload Status Identify pertinent OCA (uplinked) messages (topic and message ID). Brief comments on recent technical or scientific results. Updates on Payload troubleshooting. Changes to investigations as a result of previous work or ground training, providing big picture situational awareness.

6. Guidelines for DS Inputs 6 Generic Considerations for DS Inputs Write in active voice, using 1 st and 2 nd person liberally. Get to the point directly and avoid redundancy. Keep happy words to a minimum unless crew has asked for payloads feedback. 5 lines Maximum. If your content won’t fit into 1-4 short to moderate length sentences, consider an OCA message or another form of crew communication. If you use time references, please write in time of the publishing date, not the submission date. Use GMT days/times when making time references. Write as though you are talking to friends… you are!

7. Guidelines for DS Inputs 7 What info should be included in DS? This kind of info would all be part of the Payload Status section. Big Picture Overviews. Training refreshers, reminders, and gotchas. Letting the crew know which session they are performing.

8. Guidelines for DS Inputs 8 What info should be included in DS? Here are a few GOOD examples: New Task List Items: Dan: MSG Glove Locate activity has been added to the task list in an effort to find the missing glove rings. Questions/Answers for Crew: 1. Q for Don: On GMT 245, you indicated that you took some photos of the HRF Resupply Kits. We have not been able to locate those on the ground. Could you give us the SSC you used? Payload Status: Jeff: Today, you will perform a monthly body mass measurement on SLAMMD. This data will be used for the PROK and Nutrition experiments. The HRF1 PC will be powered on for you when you arrive at HRF Rack 1. Sam: This will be your final MSL sample run for this increment. The MSL team appreciates all of your support! Big Picture Overview Crew Session being Performed

9. Guidelines for DS Inputs 9 What info should be left out of DS? Changes to operations or resources. Direction or Actions for the Crew. Information already included in a procedure. Information already included in an execute note.

10. Guidelines for DS Inputs 10 What info should be left out of DS? The following are inputs for the Payload Status section that are POOR examples for the stated reasons: Don: Today you will perform a sample change out. You will remove the old sample, label it ‘used’, and install a new sample. This is info that is part of the procedure. Butch: Before you start your activity today, we need you to reboot the software, and set up the Node 2 camera to show the experiment rack. This is giving the crew an action and a change to operations. Terry: For Ops today, you should use sample #3 instead of using sample #1. This is giving the crew a change to an execute note.

11. Submission of Inputs 11 When should you submit your DS Inputs? PAYCOM should email you for inputs 2 days before (what we call E-2) your activity is scheduled. Your inputs should be in to PAYCOM by 12 PM (Noon) Central Time the day before your activity (what we call E-1). Once PAYCOM compiles the inputs, if you submitted one, you will receive an email to verify and concur with the input. Please provide a timely response. A couple of exceptions to this process. Please submit inputs early if there is an upcoming holiday. Weekends have 1 DS, for both Sat and Sun, so inputs for both days would need to be in by Friday at Noon.

12. Summary 12 What is a Daily Summary? It provides a concise overview of the crew’s day and provides supplemental info not contained in OSTP. What sections impact me as a PD? New Task List Items, Questions and Answers for Crew, and Payload Status. What are examples of good DS inputs? Big picture overviews, training refreshers, and reminders. What are examples of bad DS inputs? Changes to operations, actions for the crew, and info already in a procedure or execute note.

13. Daily Summary for PDs Backup Slides 13

14. Daily Summary for PDs 14

15. Daily Summary for PDs 15