Growing a Training System and Culture for the Ares I Upper Stage Project
The Mission Control Center Console is shown in quicktime along with the launching of the Ares I Upper Stage Vehicle.
Engineering topics
Publications and source records attributed to Scott, David W..
The Mission Control Center Console is shown in quicktime along with the launching of the Ares I Upper Stage Vehicle.
Marshall Space Flight Center's (MSFC) Payload Operations Integration Center (POIC) for the International Space Station (ISS) uses a number of formal databases to manage and track flight plan changes, onboard and ground equipment anomalies, and other events. However, individual console positions encounter many action items and/or occurrences that don't fit neatly into the databases, and while console logs are comprehensive, manual or automated searches do not always yield consistent results. The Payload Communications Manager (PAYCOM) team, whose members speak directly with the ISS onboard crew with respect to NASA payload operations, has found a creative way to reformat a mandatory Daily Report to organize action items, standing reminders, significant events, and other comments. While the report keeps others appraised of PAYCOMs activities and issues of the moment, the format makes it easy to capture very brief summaries of the items in a "Roll Off Matrix", including start and stop dates, resolution, and possible applicability to future ops. The matrix provides accountability for all action items, gives direct insight into the issues surrounding various payloads and methods of dealing with them, yields indirect information on PAYCOM priorities and processes, and provides a roadmap that makes it easier to get back to extensive details if needed. This paper describes how the ISS PAYCOM Daily Report and Roll Off Matrix are organized, used, and inter-related to each other and the PAYCOM operations log. While the application is for a manned vehicle, the concepts could apply in a wide spectrum of operational settings.
At the Marshall Space Flight Center's (MSFC) Payload Operations Integration Center (POIC) for International Space Station (ISS), each flight controller maintains detailed logs of activities and communications at their console position. These logs are critical for accurately controlling flight in real-time as well as providing a historical record and troubleshooting tool. This paper describes logging methods and electronic formats used at the POIC and provides food for thought on their strengths and limitations, plus proposes some innovative extensions. It also describes an inexpensive PC-based scheme for capturing and/or transcribing audio clips from communications consoles. Flight control activity (e.g. interpreting computer displays, entering data/issuing electronic commands, and communicating with others) can become extremely intense. It's essential to document it well, but the effort to do so may conflict with actual activity. This can be more than just annoying, as what's in the logs (or just as importantly not in them) often feeds back directly into the quality of future operations, whether short-term or long-term. In earlier programs, such as Spacelab, log keeping was done on paper, often using position-specific shorthand, and the other reader was at the mercy of the writer's penmanship. Today, user-friendly software solves the legibility problem and can automate date/time entry, but some content may take longer to finish due to individual typing speed and less use of symbols. File layout can be used to great advantage in making types of information easy to find, and creating searchable master logs for a given position is very easy and a real lifesaver in reconstructing events or researching a given topic. We'll examine log formats from several console position, and the types of information that are included and (just as importantly) excluded. We'll also look at when a summary or synopsis is effective, and when extensive detail is needed.