Difference between revisions of "Alert Status"

From Sim Central
Jump to navigation Jump to search
 
(18 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
== Ship's Status ==
 
== Ship's Status ==
<p align="justify">Federation Starships have been devising means to call for different levels of alertness from their crews depending on a given situation since before the founding of the Federation.  The earliest Earth starships used systems similar to that world's navies- "General Quarters" was a state of heightened readiness when the vessel was in danger or in combat.  But the system did not ultimately carry over to the Federation.</p>
+
<div style="background-color: #20242b; border-radius:4px; border: 1px solid #5b86bb; padding:10px; float: right; margin-bottom:15px; margin-left:15px;">
 +
[[File:No_Alert.png|400px|none]]</div><p align="justify">Federation Starships have been devising means to call for different levels of alertness from their crews depending on a given situation since before the founding of the Federation.  The earliest Earth starships used systems similar to that world's navies- "General Quarters" was a state of heightened readiness when the vessel was in danger or in combat.  But the system did not ultimately carry over to the Federation.</p>
  
 
<p align="justify">Instead, Starfleet implemented a system that used the three primary colors in the visible spectrum, those that most Humanoid species would be able to perceive.  By far the most common of these are Condition Yellow and Condition Red.  Less often used conditions include: Condition Blue, Condition Gray, and "Black Alert."</p>
 
<p align="justify">Instead, Starfleet implemented a system that used the three primary colors in the visible spectrum, those that most Humanoid species would be able to perceive.  By far the most common of these are Condition Yellow and Condition Red.  Less often used conditions include: Condition Blue, Condition Gray, and "Black Alert."</p>
Line 18: Line 19:
 
<li>A notable but momentary drop in Warp Core containment field strength;
 
<li>A notable but momentary drop in Warp Core containment field strength;
 
<li>Instability is detected in an Anti-matter Storage Pod;
 
<li>Instability is detected in an Anti-matter Storage Pod;
 +
<li>An uncontrolled fire is detected by sensors;
 
<li>An isolated, containable life support failure;
 
<li>An isolated, containable life support failure;
 
<li>An unplanned Shuttle departure;
 
<li>An unplanned Shuttle departure;
Line 27: Line 29:
 
<p align="justify">A Proximity Alert is when an object large enough to do harm to the starship's hull is detected on a collision or near-collision course by the sensors.</p>   
 
<p align="justify">A Proximity Alert is when an object large enough to do harm to the starship's hull is detected on a collision or near-collision course by the sensors.</p>   
  
=== Yellow Alert Reaction ===
+
=== Yellow Alert ===
 
<p align="justify"></p>
 
<p align="justify"></p>
 
<li>All essential personnel are to report to their duty stations and await further orders;   
 
<li>All essential personnel are to report to their duty stations and await further orders;   
Line 36: Line 38:
 
<li>Shuttlecraft are put on standby;
 
<li>Shuttlecraft are put on standby;
 
<li>Phaser and Torpedo launcher teams are to run Level Five diagnostics on their systems and standby;
 
<li>Phaser and Torpedo launcher teams are to run Level Five diagnostics on their systems and standby;
<li>Systems Engineers run a Level Five Diagnostic on criteria ship's computer systems;
+
<li>Systems Engineers run a Level Five Diagnostic on critical ship's computer systems;
 
<li>Engineering runs a Level Five diagnostic on the Main Antimatter Reaction Assembly, and all vital systems;
 
<li>Engineering runs a Level Five diagnostic on the Main Antimatter Reaction Assembly, and all vital systems;
 
<li>Navigational Control sets Deflector Shields to standby and runs a Level Five Diagnostic on the system;
 
<li>Navigational Control sets Deflector Shields to standby and runs a Level Five Diagnostic on the system;
Line 45: Line 47:
  
 
== Condition Red ==
 
== Condition Red ==
<p align="justify"></p>
+
<p align="justify">Condition Red or "[http://trekcore.com/audio/redalertandklaxons/tng_red_alert1.mp3 Red Alert]" is the highest awareness and readiness level on the ship.  The Commanding Officer and Operations Manager (by way of the Ops console) can call a Red Alert.  The criteria for a Red Alert that the ship is in imminent, near-certain and potentially life-threatening peril, be that a combat situation, an environmental disaster, a boarding action, or a widespread power failure.  </p>
 +
 
 +
=== Brace for Impact ===
 +
<p align="justify">An object or phenomena large enough to do damage to the hull has passed through the navigation deflector sensor band and is on an intercept course.  During a "Brace for Impact," crew are to take reasonable measures to secure their positions to minimize injury.  A call for Brace for Impact usually is followed by instructions from the Bridge.  In Sickbay, a call for Brace for Impact sets Emergency Medical Response Teams into motion: they report to muster stations and Sickbay.</p>
  
 
=== Battlestations ===
 
=== Battlestations ===
<p align="justify"></p>
+
<p align="justify">When the Bridge calls for "Battlestations," Red Alert is implied.  Battlestations is the most severe readiness drill with the intention in mind to still save the ship.  The vessel and its crew are expecting to enter combat.  Security and weapon systems are heightened to maximum awareness and Sickbay is fully staffed and prepares it's Emergency Response Team muster stations.  Security officers are posted to essential locations (Bridge, Engineering, Shuttlebay, Sickbay, Main Computer) and are fully armed and armored.  Security also guard all emergency shelters.  The Brig and the Armory are put on Lockdown with maximum containment fields in place which can only be disabled by the Chief of Security, Executive Officer, or Commanding Officer.</p>
 +
<p align="justify">During Battlestations, Auxiliary Control is fully manned in the event that the Bridge is lost but the ship must still be controlled.  The Bridge is fully staffed, with officers at auxiliary stations for Damage Control, Mission Operations (in this case monitoring of Security and any Boarding Parties), and Science coordinating sensor and information resources.</p>
  
 
=== Intruder Alert ===
 
=== Intruder Alert ===
<p align="justify"></p>
+
<p align="justify">[http://trekcore.com/audio/redalertandklaxons/tng_nemesis_intruder_alert.mp3 Intruder Alert]</p>
  
 
=== Abandon Ship ===
 
=== Abandon Ship ===
Line 58: Line 64:
 
=== Self Destruct Sequence ===
 
=== Self Destruct Sequence ===
 
<p align="justify"></p>
 
<p align="justify"></p>
 +
 +
=== Red Alert ===
  
 
<div style="background-color: #20242b; border-radius:4px; border: 1px solid #5b86bb; padding:10px; float: left; margin-bottom:20px; margin-right:15px;">
 
<div style="background-color: #20242b; border-radius:4px; border: 1px solid #5b86bb; padding:10px; float: left; margin-bottom:20px; margin-right:15px;">
Line 63: Line 71:
  
 
== Condition Blue ==
 
== Condition Blue ==
<p align="justify">Condition Blue is found only on some ships in the Federation Starfleet: by those vessels that can land (generally Frigate-sized or smaller) or by vessels that can engage in an emergency saucer separation action.  As a <I>Malachowski</i>-class Frigate, the <I>Ulysses</i> is capable of landing.  Condition Blue is a form of Condition Yellow- the vessel is in potential peril- but because of the specialized protocols required for landing, it is warranted its own alert status (crash landing is always a Condition Red situation).</p>
+
<p align="justify">[http://trekcore.com/audio/redalertandklaxons/voybluealert.mp3 Condition Blue] is found only on some ships in the Federation Starfleet: by those vessels that can land (generally Frigate-sized or smaller) or by vessels that can engage in an emergency saucer separation action.  As a <I>Malachowski</i>-class Frigate, the <I>Ulysses</i> is capable of landing.  Condition Blue is a form of Condition Yellow- the vessel is in potential peril- but because of the specialized protocols required for landing, it is warranted its own alert status (crash landing is always a Condition Red situation).</p>
  
 
<div style="background-color: #20242b; border-radius:4px; border: 1px solid #5b86bb; padding:10px; float: right; margin-bottom:20px; margin-left:15px;">
 
<div style="background-color: #20242b; border-radius:4px; border: 1px solid #5b86bb; padding:10px; float: right; margin-bottom:20px; margin-left:15px;">

Latest revision as of 02:38, 2 December 2020

Ship's Status

No Alert.png

Federation Starships have been devising means to call for different levels of alertness from their crews depending on a given situation since before the founding of the Federation. The earliest Earth starships used systems similar to that world's navies- "General Quarters" was a state of heightened readiness when the vessel was in danger or in combat. But the system did not ultimately carry over to the Federation.

Instead, Starfleet implemented a system that used the three primary colors in the visible spectrum, those that most Humanoid species would be able to perceive. By far the most common of these are Condition Yellow and Condition Red. Less often used conditions include: Condition Blue, Condition Gray, and "Black Alert."

Implementing an alert status (assuming the computer does not automatically do so) is done from the Operations Manager console on the Main Bridge. The Operations Manager directs crew and resources as defined by the alert status and special instructions from the Commanding Officer.

No Status (Green)

When a ship is under no form of potential or imminent danger, it is at normal operations, has no status, and is sometimes called Condition Green. This is indicated by an inert gray condition icon on most consoles. During normal operations, a starship has power diverted to necessary systems as everyday ship function demands. No systems are prioritized over any other, save at the direction of the Operations Manager.

Yellow-Alert.gif

Condition Yellow

A Commanding Officer, Operations Manager, or the ship's computer can call Condition Yellow. Criteria for Condition Yellow (or Yellow Alert) is that a heightened state of awareness and readiness is called for. The starship is in potential danger and may be operating with reduced resources not at immediately threatening levels. Conditions that call for a Yellow Alert include:

  • A computer core failure (but the other remains online as do most or all subprocessors);
  • Structural Integrity Fields see an unexpected drop of up to 20% while at Warp Speed;
  • A notable but momentary drop in Warp Core containment field strength;
  • Instability is detected in an Anti-matter Storage Pod;
  • An uncontrolled fire is detected by sensors;
  • An isolated, containable life support failure;
  • An unplanned Shuttle departure;
  • A hostile vessel is on long-range sensors but has not yet activated weapons or shields
  • A friendly vessel passes inside the 50,000 kilometers zone and has made no attempts at communication, automated hello, or hail.
  • A containment field failure in a Sickbay or Science Lab containment forcefield (often quickly upgraded to Red Alert).

    Proximity Alert

    A Proximity Alert is when an object large enough to do harm to the starship's hull is detected on a collision or near-collision course by the sensors.

    Yellow Alert

  • All essential personnel are to report to their duty stations and await further orders;
  • Sickbay fully activates and all staff report in;
  • Security activates and is to await further orders. Emergency Shelter designees are to arm themselves and report to their stations;
  • Non-essential personnel are ordered to "Ready-Set" mode: they are to prepare to evacuate to a secured environmental safety shelter;
  • Bridge, Navigational Control and Auxiliary Control energize defense fields;
  • Shuttlecraft are put on standby;
  • Phaser and Torpedo launcher teams are to run Level Five diagnostics on their systems and standby;
  • Systems Engineers run a Level Five Diagnostic on critical ship's computer systems;
  • Engineering runs a Level Five diagnostic on the Main Antimatter Reaction Assembly, and all vital systems;
  • Navigational Control sets Deflector Shields to standby and runs a Level Five Diagnostic on the system;
  • Captain and Executive Officer, report to the Main Bridge. Chief Engineer, report to Main Engineering. Chief Medical Officer, report to Sickbay.
    Red-Alert.gif

    Condition Red

    Condition Red or "Red Alert" is the highest awareness and readiness level on the ship. The Commanding Officer and Operations Manager (by way of the Ops console) can call a Red Alert. The criteria for a Red Alert that the ship is in imminent, near-certain and potentially life-threatening peril, be that a combat situation, an environmental disaster, a boarding action, or a widespread power failure.

    Brace for Impact

    An object or phenomena large enough to do damage to the hull has passed through the navigation deflector sensor band and is on an intercept course. During a "Brace for Impact," crew are to take reasonable measures to secure their positions to minimize injury. A call for Brace for Impact usually is followed by instructions from the Bridge. In Sickbay, a call for Brace for Impact sets Emergency Medical Response Teams into motion: they report to muster stations and Sickbay.

    Battlestations

    When the Bridge calls for "Battlestations," Red Alert is implied. Battlestations is the most severe readiness drill with the intention in mind to still save the ship. The vessel and its crew are expecting to enter combat. Security and weapon systems are heightened to maximum awareness and Sickbay is fully staffed and prepares it's Emergency Response Team muster stations. Security officers are posted to essential locations (Bridge, Engineering, Shuttlebay, Sickbay, Main Computer) and are fully armed and armored. Security also guard all emergency shelters. The Brig and the Armory are put on Lockdown with maximum containment fields in place which can only be disabled by the Chief of Security, Executive Officer, or Commanding Officer.

    During Battlestations, Auxiliary Control is fully manned in the event that the Bridge is lost but the ship must still be controlled. The Bridge is fully staffed, with officers at auxiliary stations for Damage Control, Mission Operations (in this case monitoring of Security and any Boarding Parties), and Science coordinating sensor and information resources.

    Intruder Alert

    Intruder Alert

    Abandon Ship

    Self Destruct Sequence

    Red Alert

    Blue-Alert.gif

    Condition Blue

    Condition Blue is found only on some ships in the Federation Starfleet: by those vessels that can land (generally Frigate-sized or smaller) or by vessels that can engage in an emergency saucer separation action. As a Malachowski-class Frigate, the Ulysses is capable of landing. Condition Blue is a form of Condition Yellow- the vessel is in potential peril- but because of the specialized protocols required for landing, it is warranted its own alert status (crash landing is always a Condition Red situation).

    Gray-Alert.gif

    Condition Gray