Difference between revisions of "LOGS (procedures)"
m |
Jared Kelly (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | == | + | == MC-LOGS Procedures== |
| − | === | + | === Job Description=== |
LOGS must record, with timestamp, all interesting occurances during the mission, especially those pertaining to [[Mission Control]] and plans to control the mission. | LOGS must record, with timestamp, all interesting occurances during the mission, especially those pertaining to [[Mission Control]] and plans to control the mission. | ||
Because there is often a chatlog from [[AUXCOM]], LOGS is not required to contain all the details of the current situation, and should be considered a minute by minute summary. | Because there is often a chatlog from [[AUXCOM]], LOGS is not required to contain all the details of the current situation, and should be considered a minute by minute summary. | ||
| − | === | + | === Log Worthy Events=== |
This list is not exhaustive: | This list is not exhaustive: | ||
*Launch | *Launch | ||
| Line 15: | Line 15: | ||
*Shift change outside of normal procedure | *Shift change outside of normal procedure | ||
| − | === | + | === Unworthy Events=== |
This list is not exhaustive: | This list is not exhaustive: | ||
*Any events relating to [[Time Acceleration]] - Note: Time Acceleration should be noted in the [[Unofficial Logs]] in accordance with Unofficial Logs procedures. | *Any events relating to [[Time Acceleration]] - Note: Time Acceleration should be noted in the [[Unofficial Logs]] in accordance with Unofficial Logs procedures. | ||
| − | === | + | === LOG Header=== |
The top of each log file should contain the following template, filled out appropriately by the first person to man LOGS. | The top of each log file should contain the following template, filled out appropriately by the first person to man LOGS. | ||
<pre> | <pre> | ||
| Line 38: | Line 38: | ||
Note that the [[Simulator Commander]]'s full name should be appended to the LOG on a line indicated by "SimCom:" after the mission is completed. This delay is to preserve mission integrity. | Note that the [[Simulator Commander]]'s full name should be appended to the LOG on a line indicated by "SimCom:" after the mission is completed. This delay is to preserve mission integrity. | ||
| − | === | + | === Stations Check=== |
====Mission Control Check==== | ====Mission Control Check==== | ||
It is the responsibility of MC LOGS to remind the [[Flight Director]] at 20 minute intervals to verify that each station in [[Mission Control]] is manned by an appropriate staff member, and that all stations report green. | It is the responsibility of MC LOGS to remind the [[Flight Director]] at 20 minute intervals to verify that each station in [[Mission Control]] is manned by an appropriate staff member, and that all stations report green. | ||
| Line 71: | Line 71: | ||
It is the responsibility of MC LOGS to remind the [[Flight Director]] at 30 minute intervals to verify that all stations in the [[Habitat]] are manned by an appropriate [[Astronaut]]. In addition, during this check, each piece of software should be tested to ensure that [[Mission Control]] is receiving the correct telemetry from the [[Habitat]]. Testing the software consists of verifying that all software reads the same time as all the software in the habitat with accounting for the 5s lag in updates. | It is the responsibility of MC LOGS to remind the [[Flight Director]] at 30 minute intervals to verify that all stations in the [[Habitat]] are manned by an appropriate [[Astronaut]]. In addition, during this check, each piece of software should be tested to ensure that [[Mission Control]] is receiving the correct telemetry from the [[Habitat]]. Testing the software consists of verifying that all software reads the same time as all the software in the habitat with accounting for the 5s lag in updates. | ||
| − | === | + | === Logging Best Practices=== |
At the start of a new day on Earth, the log should read | At the start of a new day on Earth, the log should read | ||
<pre> | <pre> | ||
| Line 111: | Line 111: | ||
</pre> | </pre> | ||
| − | === | + | === Unofficial Logs=== |
It is also the job of LOGS to record unofficial occurrences in the [[unofficial logs]]. This includes such things as unprofessional behaviour that is particularly amusing, events relating to time acceleration, or anything noteworthy that in some way impinges on [[Mission Integrity]]. | It is also the job of LOGS to record unofficial occurrences in the [[unofficial logs]]. This includes such things as unprofessional behaviour that is particularly amusing, events relating to time acceleration, or anything noteworthy that in some way impinges on [[Mission Integrity]]. | ||
{{Procedure|PrevTopic=GNC Procedures|NextTopic=Observer Procedures}} | {{Procedure|PrevTopic=GNC Procedures|NextTopic=Observer Procedures}} | ||
Revision as of 14:58, 26 April 2013
Contents
MC-LOGS Procedures
Job Description
LOGS must record, with timestamp, all interesting occurances during the mission, especially those pertaining to Mission Control and plans to control the mission.
Because there is often a chatlog from AUXCOM, LOGS is not required to contain all the details of the current situation, and should be considered a minute by minute summary.
Log Worthy Events
This list is not exhaustive:
- Launch
- Engine Burn
- Docking
- Depressurization
- Permissions given by Mission Control
- Requests from the Habitat
- Shift change outside of normal procedure
Unworthy Events
This list is not exhaustive:
- Any events relating to Time Acceleration - Note: Time Acceleration should be noted in the Unofficial Logs in accordance with Unofficial Logs procedures.
LOG Header
The top of each log file should contain the following template, filled out appropriately by the first person to man LOGS.
Earth Date (E.g. March 26, 2010)
Mission Type (Mini, Training, Main)
Mission Name (Alpha, Revenge, Coronis, etc.)
Destination: Mission Destination
Purpose: 1. Mission Goal #1
2. Mission Goal #2
3. Mission Goal #3 (see: associated documentation)
MCCom: Mission Control Commander's full name
HabCom: Habitat Commander's full name
SubCom: Habitat Sub-Commander's full name
Astros: Other astronauts. Full names.
Note that the Simulator Commander's full name should be appended to the LOG on a line indicated by "SimCom:" after the mission is completed. This delay is to preserve mission integrity.
Stations Check
Mission Control Check
It is the responsibility of MC LOGS to remind the Flight Director at 20 minute intervals to verify that each station in Mission Control is manned by an appropriate staff member, and that all stations report green.
Example MC Shift Monitoring
2013 - LOGS reminds FLIGHT to perform station check.
Position Name Status
FLIGHT Ramclam Green
CAPCOM Storey Green
AUXCOM stand-by stand-by
EECOM Pelletier Red
GUIDO Pelletier Green
ENG De Young Orange
LOGS De Young Green
FLIGHT Sign-off: Issues same as previous check.
- Position:
- As shown.
- Name:
- The surname of the Mission Controller responsible for that station, including duplicates.
- Status:
- Either Green, Orange, Red, or Stand-by
- Green: All is well
- Orange: Minor malfunction or concern. (E.g. ln1 is grey on the Power Grid because the astronauts turned it off)
- Red: A major malfunction has occured. (E.g. The Hotlab has no interior air pressure, and this issue has not yet been resolved.)
- Stand-by: This station is not being monitored, or is not able to report their status.
- Either Green, Orange, Red, or Stand-by
Habitat Check
It is the responsibility of MC LOGS to remind the Flight Director at 30 minute intervals to verify that all stations in the Habitat are manned by an appropriate Astronaut. In addition, during this check, each piece of software should be tested to ensure that Mission Control is receiving the correct telemetry from the Habitat. Testing the software consists of verifying that all software reads the same time as all the software in the habitat with accounting for the 5s lag in updates.
Logging Best Practices
At the start of a new day on Earth, the log should read
End of DAY X Start of DAY Y
Timestamps should be in HHMM corresponding to a 24-hour clock. This means that 8:32 pm would be logged as 2032.
Following the timestamp should be a space, dash, and space.
The Logger should identify himself upon taking over logs and upon ceding logs to the next logger.
Record the launch and landing times as exactly as possible, to the second.
Start the log entry with the person who is performing the action and not the person who is receiving. I.e. if the Habitat asks for permission, the log entry starts with "Habitat asks," and if MC grants it, that entry starts with "MC grants" and not "Habitat is granted"
Example Log
Start of DAY 1 ... 1230 - Ms. Alice on MC LOGS 1232 - Habitat requests permission to Launch 1233 - MC grants permission to Launch 1235 - SRBs engaged 1236 - Hab at 300km from Earth 1237 - SRBs disengaged 1237 - Hab Engines at 100% in ccwPrograde 1238 - Astronauts report loud impacts on C&C roof 1239 - Hab Engines at 0% 1240 - ENG reports RAD shields malfunctioning 1241 - EECOM reports decompression in C&C 1243 - EECOM reports internal radiation at 4.23E-09 S/s and climbing 1244 - Astronauts evacuated to Interlock 1246 - CAPCOM reports loss of communication ... 1313 - Ms. Alice cedes MC LOGS 1314 - Mr. Bob on MC LOGS
Unofficial Logs
It is also the job of LOGS to record unofficial occurrences in the unofficial logs. This includes such things as unprofessional behaviour that is particularly amusing, events relating to time acceleration, or anything noteworthy that in some way impinges on Mission Integrity.
| OCESS Procedures Manual |
|---|
| Table of Contents |
| Document Usage |
| Missions |
| Common Positions |
| Mission Control Staff |
| Habitat |
| Engineering |
| Flight (chapter) |
| Habitat Activities |
| Experiments |
| Emergency |
| Alpha Procedures |
