USS Vendetta
 
 Main
 • Welcome
 • Introduction
 • Announcements
 • Expedition Fleet
  Forums


 Personnel
 • Crew Manifest
 • Open Positions
 • Chain of Command
 • Personal Logs
 • Rules & Protocol
 • Join

 Ship
 • Vendetta Time Line
 • Weapons Index
 • Tour
 • Ship History
 • Class Data Log
 • History of
  The Reapers

 • Specifications
 • Departments
 • Database

 The SIMM
 • Current Mission
 • Mission Logs
 • Crew Awards
 • Contact Us

10 Flight Operations

Operations aboard an Intimidator Refit class starship fall under one of four categories: flight operations, primary mission operations, secondary mission operations, and flight deck operations.

Flight Operations are all operations that relate directly to the function of the starship itself, which include power generation, starship upkeep, environmental systems, and any other system that is maintained and used to keep the vessel space worthy.

Primary Mission Operations entail all tasks assigned and directed from the Main Bridge, and typically require full control and discretion over ship navigation and ship's resources.

Secondary Mission operations are those operations that are not under the direct control of the Main Bridge, but do not impact Primary Mission Operations. Some examples of secondary mission operations include long-range cultural, diplomatic or scientific programs run by independent or semi-autonomous groups aboard the starship.

Flight Deck Operations are those operations that typically fall under Secondary Mission operations.
Back to Top


10.1 Mission Types

Despite the fact that the Intimidator Refit class design philosophy leaned heavily toward Tactical and Defensive Missions, she is still classified as a multi-role starship, in keeping with Federation Council Policy. This offers the Federation, and Starfleet, flexibility in assigning nearly any objective within the realm of Starfleet's assigned duties. Missions for an Intimidator Refit class starship may fall into one of the following categories, in order of her strongest capable mission parameter to her weakest mission parameter. Tactical/Defensive Operations: Typical Missions include patrolling the Gorn and Cardassian boarders, or protecting any Federation interest from hostile intent in planetary or interstellar conflicts.

• Emergency/Search and Rescue: Typical Missions include answering standard Federation emergency beacons, extraction of Federation or Non-Federation citizens in distress, retrieval of Federation or Non-Federation spacecraft in distress, small-scale planetary evacuation. The Intimidator Refit is rated to assist in medium or large scale planetary evacuation operations.

• Federation Policy and Diplomacy: An Intimidator Refit class starship can be used as an envoy during deep-space operations.

• Deep-space Exploration: The Intimidator Refit class is equipped for long-range interstellar survey and mapping missions, as well as the ability to explore a wide variety of planetary classifications.

• Contact with Alien Life forms: Pursuant to Starfleet Policy regarding the discovery of new life, facilities aboard the Sovereign class include a variety of exobiology and xenobiological suites, and a small cultural anthropology staff, allowing for limited deep-space life form study and interaction.

• Ongoing Scientific Investigation: A Intimidator Refit class starship is equipped with scientific laboratories and a wide variety of sensor probes and sensor arrays, giving her the ability to perform a wide variety of ongoing scientific investigations.
Back to Top


10.2 Operating Modes

The normal flight and mission operations of the Intimidator Refit class starship are conducted in accordance with a variety of Starfleet standard operating rules, determined by the current operational state of the starship. These operational states are determined by the Commanding Officer, although in certain specific cases, the Computer can automatically adjust to a higher alert status. The major operating modes are:

• Cruise Mode: The normal operating condition of the ship. In Cruise mode the Intimidator Refit operates on minimal deflector shield power, and is in a minimally combat ready state.

• Yellow Alert: Designates a ship wide state of increased preparedness for possible crisis situations. Yellow alert automatically raises the Intimidator Refits MLSS shield system, and sets all other tactical systems to stand by. The Phaser Cannon sets to a low build charge to decrease the amount of time needed to charge and fire the cannon in a combat situation.

• Red Alert: Designates an actual state of emergency in which the ship or crew is endangered, immediately impending emergencies, or combat situations.

• External Support Mode: State of reduced activity that exists when a ship is docked at a starbase or other support facility.

• Reduced Power Mode: this protocol is invoked in case of a major failure in spacecraft power generation, in case of critical fuel shortage, or in the event that a tactical situation requires severe curtailment of onboard power generation.

• Silent Running Mode: A state of reduced sensor profile operation, generally related to the activation of the cloaking device, and the shutdown of all but a few critical sensor pallets used for navigation.

During Cruise Mode, the ship’s operations are run on three 8-hour shifts designated Alpha, Beta, and Gamma. Should a crisis develop, it may revert to a four-shift system of six hours to keep crew fatigue down.
Back to Top


10.3 Maintenance

Though much of a modern starship’s systems are automated, they do require regular maintenance and upgrade. Maintenance is typically the purview of the Engineering, but personnel from certain divisions that are more familiar with them can also maintain specific systems.

Maintenance of onboard systems is almost constant, and varies in severity. Everything from fixing a stubborn replicator, to realigning the Dilithium matrix is handled by technicians and engineers on a regular basis. Not all systems are checked centrally by Main Engineering; to do so would occupy too much computer time by routing every single process to one location. To alleviate that, systems are compartmentalized by deck and location for checking. Department heads are expected to run regular diagnostics of their own equipment and report anomalies to Engineering to be fixed.

Systems Diagnostics: All key operating systems and subsystems aboard the ship have a number of preprogrammed diagnostic software and procedures for use when actual or potential malfunctions are experienced. These various diagnostic protocols are generally classified into five different levels, each offering a different degree of crew verification of automated tests. Which type of diagnostic is used in a given situation will generally depend upon the criticality of a situation, and upon the amount of time available for the test procedures.

Level 1 Diagnostic - This refers to the most comprehensive type of system diagnostic, which is normally conducted on ship's systems. Extensive automated diagnostic routines are performed, but a Level 1 diagnostic requires a team of crew members to physically verify operation of system mechanisms and to system readings, rather than depending on the automated programs, thereby guarding against possible malfunctions in self-testing hardware and software. Level 1 diagnostics on major systems can take several hours, and in many cases, the subject system must be taken off-line for all tests to be performed.

Level 2 Diagnostic - This refers to a comprehensive system diagnostic protocol, which, like a Level 1, involves extensive automated routines, but requires crew verification of fewer operational elements. This yields a somewhat less reliable system analysis, but is a procedure that can be conducted in less than half the time of the more complex tests.

Level 3 Diagnostic - This protocol is similar to Level 1 and 2 diagnostics but involves crew verification of only key mechanics and systems readings. Level 3 diagnostics are intended to be performed in ten minutes or less.

Level 4 Diagnostic - This automated procedure is intended for use whenever trouble is suspected with a given system. This protocol is similar to Level 5, but involves more sophisticated batteries of automated diagnostics. For most systems, Level 4 diagnostics can be performed in less than 30 seconds.

Level 5 Diagnostic - This automated procedure is intended for routine use to verify system performance. Level 5 diagnostics, which usually require less than 2.5 seconds, are typically performed on most systems on at least a daily basis, and are also performed during crisis situations when time and system resources are carefully managed.
Back to Top
A Proud Member of Expedition Fleet!

Site Maintained by Robert Morris
USS Vendetta run by Fleet Captain Sayid Jarrah (CO) and Zak Arden (XO)
SIMM Management System © 2004-2005 by Anodyne Productions
Vendetta SMS Template Designed by Cody Logan
Rank images created by Kuro-chan of Kuro-RPG