 |
|
 |
|
|
USS
Ganymede
NCC-65675 |
|
|
Ship Manager in Training |
|
| |
|
The Ship
Manager in Training (hereafter known as SMiT) program will
provide trainees with the needed experience to become the SM of a ship.
During training, candidates will plan and run a mission arc that will
last around 5-6 weeks; write, email, and post mission orders; conduct
mission debriefs; write Intel and weekly reports; keep attendance; edit
and email transcripts (if applicable); ensure that crew writes, emails,
posts logs, etc. In short, do all tasks a Ship/Station Manager usually does!
Throughout
the 5-6 week training, the SMiT will receive help and feedback from the
SM, CO and the crew. This will give the SMiT the needed experience and
learning environment to develop the needed leadership skills and
administrative abilities required from Ship/Station Managers.
|
|
| |
| |
| |
| |
| |
|
Below is a detailed list of tasks the SMiT will perform during
the arc. This list offers links to examples and a clear run down of how
each show should be performed. If any questions arise pertaining these tasks,
email the Ganymede's SM and/or CO for help. |
|
|
|
|
|
MENTORS |
|
Being a
ship manager is quite different than being a player. Therefore, SMiTs
will not only be guided throughout training by the Ganymede SM but
also by a mentor.
A mentor is a SM or Chat Trainer. The mentor is
there to give the SMiT advice, constructive criticism, and answer
questions. After each mission on the training ship and if the mentor
didn't attend the mission, the mentor will be emailed the comments the
training ship crew gave the candidate so that the mentor can help the
trainee improve. When possible, the mentor will check the mission arc
plan and mission orders before the candidate sends those out to the
Ganymede SM for final approval. The mentor will be added to the
ship's roster for the duration of the candidate's training.
The SMiT can find his/her own mentor or the
Ganymede SM will assign one. The Ganymede SM can also act as mentor.
It is key that the mentor be someone that the candidate is comfortable
with. |
|
|
|
|
|
PLANNIFICATION OF ARC |
|
|
Two weeks
prior to SMiT, the trainee must email the Ganymede SM the mission
arc breakdown (example of a mission arc breakdown ***coming soon***) for
approval.
When
planning the mission arc, the SMiT should check the
ship's roster and verify with the
Ganymede SM if there will be a COiT or XOiT training at the same
time. This should be taken into account when planning the arc. The
mission arc should not be over complicated or require too many NPCs.
SMiT is to remember that this is training and that it is best to start
with a simple arc to get the feeling of how SMing works. The arc should
last 5-6 weeks (the Ganymede SM will let the SMiT know how many
weeks training will last) and the arc should be concluded in the final
week. |
|
|
|
|
|
MISSION
ORDERS |
|
|
Once the
SMiT planned the arc and it was approved by the SM, the SMiT will need
to write mission orders (if not already done in the arc planning). These
should be sent out at least a week before the first mission so that the
CO as enough time to read them, ask questions if need be, and write the
mission briefing. (Note: If there is a COiT or XOiT running at the same
time, that trainee will write the mission briefing.) Mission orders
contain information which pertain to the overall mission.
Mission orders must be emailed to
ussganymede@startrek.acalltoduty.com
and posted on the
Ganymede boards inside the SMiT's own
forum. The title of the email and of the thread should be: Mission
Orders SD (write stardate of mission here). Example: Mission Orders SD
10603.31.
Example of mission orders. |
|
|
|
|
|
PRE-MISSION TASKS |
|
The SMiT
should be in the mission room and OOC room at least 15 minutes prior to
mission. During those 15 minutes, the SMiT is to perform the following
tasks:
-
On a spreadsheet
(or other document), take attendance. This means to also note if a
player arrived late (within 15 minutes before mission or later), did
not attend but sent warning, left early, etc.
-
Ensure that CO (or
COiT/XOiT) verifies that all players are in both rooms with the
proper nickname.
-
Ensure that CO (or
COiT/XOiT) performs a location check so that everyone knows where
they are starting from.
-
Ask players if
they have any questions about the mission briefing and the mission.
-
Post the mission
opener in Mission Room.
Mission openers should include:
-
The ship's name
and mission stardate.
-
The mission
number, the arc/mission title, and the part number (if applicable).
-
A small summary of
what has happened so far and where the mission is starting.
-
A "resume mission"
or "begin mission" warning.
Example:
Host
SMiT_JohnDoe says:
USS Ganymede, 10603.31
Host
SMiT_JohnDoe says:
Mission #162, The Invisible, Part 2
Host
SMiT_JohnDoe says:
After receiving a distress signal from McKinley Station, the Ganymede changed
course to offer help. Now that they have arrived at the
Station, the crew is ready to assess the situation and take control of
the situation.
Host
SMiT_JohnDoe says:
<<<<<<<<<<<<<<<Resume Mission>>>>>>>>>>>>>>> |
|
|
|
|
|
DURING MISSION |
|
|
During
mission, the SMiT must provide crew with the needed ACTIONs in the
mission room and with additional information in the OOC room (or in whispers), as
required. The SMiT is to keep an eye on both rooms so to ensure that all
questions are answered (in OOC) and that ACTIONs are done in mission.
The
SMiT can play NPCs as required. |
|
|
|
|
|
DEBRIEFING |
|
|
Once the
mission is finished, two debriefings will be done. The first one will be
concerning the mission. The SMiT is to start a debrief where the SMiT
and CO will each give their comments about the mission and the weekly
tasks (such as emailing/posting of logs). During that debrief, SMiT will
let the crew know about time lapse between mission and any other relevant
mission info.
Then,
players and the Ganymede SM will give the SMiT feedback on the
mission and weekly tasks s/he performed. This feedback, known as
candidate debrief, will be key in helping the SMiT improve and learn.
|
|
|
|
|
|
LOGS |
|
|
The SMiT
is to ensure that crew writes, emails, and posts logs. If crew members
do not submit logs, SMiT is to react accordingly. |
|
|
|
|
|
TRANSCRIPTS |
|
|
The SMiT
will need to ensure that mission transcripts are edited and emailed. The
SMiT can decide to edit some/all of the transcripts (Note: If there is a
COiT or XOiT at the same time, that person will edit the transcripts).
The edited transcript is to be emailed to
ussganymede@startrek.acalltoduty.com
and transcripts@startrek.acalltoduty.com
at least 24 hours before the next mission. The file name of the
transcript should be Ganymede*stardate* (Example:
Ganymede1060331.rtf).
Examples
of edited transcripts:
here. |
|
|
|
|
|
INTEL REPORTS |
|
|
Intel
reports must be sent to
intelreports@startrek.acalltoduty.com
around the 25th of each month. When writing the intel report, the SMiT
is to focus on his arc and not what happened before on the Ganymede.
The SMiT is also required to send the intel report to the Ganymede SM first for
review and approval.
Example of intel reports.
|
|
|
|
|
|
WEEKLY REPORTS |
|
|
Each week,
the SMiT is to email the Ganymede SM with a small report on where
the mission arc is and with comments on the crew (if applicable), such
as behavior, lack of logs, absence, etc. Normally, a SM would send this
to his FM, as required.
Example of
weekly report:
Mission #162, SD 10603.28
The
mission went as planned. The crew enjoyed a short shore leave on Risa
and then went back on the ship to head to Vulcan to get some samples
from the Vulcan Science Institute.
Players
worked well together. They had no logs to write for last week's
missions. Some are forgetting the colon (:) after using **. It was
brought to their attention in debrief. The CMO did not attend mission
tonight and didn't send warning. The CNS arrived 5 minutes after the
mission started. All other crew were there on time for pre-mission
tasks. |
|
|
|
|
|
THE MOST IMPORTANT RULE! |
|
|
Have fun! |
|
|
Last
update: 10604.19 |
|
|
|
 |