This may not actually exist depending on if I take written or typed notes 🙂

Operations presentation

• Operators should be honest (disclose mistakes), good at documenting, able to handle “firefighter” workload (at times boring, then suddenly intense), punctual. Primary responsibility is to protect the spacecraft from harm
• Flight directors: pre and post contact, management, lead the shift
• Operations Engineers: Execute day to day vehicle activities, review and prepare for plan approved by FD, monitor behavior for anomalies
• Mission Planners: generate shift plans, set expected times for command sequences, schedule contacts
• Payload lead: manages experiment plan, coordinates with MPs to follow it

Some diagrams here about leadership/team structure + operations rhythm

• Operations is generally: experiment plan, weekly plan, shift log, contact log, commands/behavior, log archive

Realtime operations/day to day

• pre-pass: check commands and parameters beforehand, build commands, finalize pass plan, brief from FD, consult with subject matter experts (SME) as needed
• In-pass: monitor vehicle (wait to send commands until it’s okay), then send commands with FD approval, maintain comms and monitoring, collect data
• Post-pass: debrief, identify issues, document data/happenings, begin planning next pass

Data Visualization/operations

• Visualization: Should have State of Health easily digestible, general overview and/or subsystems
• Command and Control: for building and sending commands, access raw TLM, verify commands
• Ground station: information on itself, generally with C&C
• AFRL uses AWS to access their ground front end, Grafana for data vis, Enchilada is their in-house C&C, Confluence for data processing/documenting
• For payload, turn off command should always be scheduled and sent before the turn on command (so that it can’t be stuck on if you lose link while sending commands)