STBC HQ Missions

< back to home

STBC    Command    Missions      STBC HQ Missions

STBC HQ missions are intelligence-gathering missions bridge crews can perform to add to the STBC HQ database. Reports of completed STBC HQ missions may be submitted in the missions log discussion board below. Submission of visual images, video recordings, and other scans is encouraged but not required. STBC HQ missions include exploration, scientific investigation, military reconnaissance, and systems testing. All mission parameters listed below are optional; parameters may be adjusted by the ship captain as circumstances require.
Submit a mission log by posting in the Mission Logs discussion board.

Surveying

• Explore and chart a star system, system region, or local region in the Local Sector, identifying planets, planetoids, and other regions of interest for further study
• Note any activity by pirates or other potentially hostile forces
• Note any dangerous or unusual anomalies or other natural phenomena

Scientific Investigation

• Document unusual anomalies and other natural phenomena
• Note the location, and whether the effects are localized to a certain distance or region of space
• Note the amount of damage to systems, if any, or other significant effects
• Test whether damage increases as range decreases

Military Reconnaisance

• Observe friendly and hostile ships and gather intelligence regarding their capabilties
• Engine recon: maximum observed speed, observed time to impulse between regions (note the regions)
• Weapons recon: note number of phasers and torpedoes fired per volley, damage to your shields or hull per phaser or torpedo hit received
• Defense recon: document damage to enemy shields or hull per phaser or torpedo hit (note phaser strength)
• Note any effective tactics, enemy weaknesses, or other useful intelligence

Systems Testing

• Test various ship systems on Aegis, Galaxy, and/or Constitution class vessels and report the results
• Examples:
• Test novel power reroute patterns , measure time to overload per system, and/or document exact effects of overload per system
• Test operations console system benefits and/or develop new crew assignments patterns for various field situations
• Document transporter lock time per unit of range: how long will a transporter lock take at 30k, 20k, 10k, etc.
• Document relationship scan time per unit of range: how close for optimal scan speed? How much does extended range reduce scan speed?
• Document maximum actual speed (kilometers per second/minute/hour) per unit of power allocated to engines: if the ship is 40km away and needs 30 seconds to ready weapons, how fast should it travel so it doesn't get within weapons range too soon?
• Test shield recycling optimization (if any) for Galaxy and Constitution class vessels
• Bridge officers are encouraged to devise new tests that will expand Starfleet's understanding of ship systems; review existing STBC HQ articles to find areas of potential expansion
• To ensure the integrity and reproducability of tests, video recordings are highly encouraged when possible