No edit summary |
No edit summary |
||
Line 97: | Line 97: | ||
* Chief Engineer reports to main engineering ready to assume control of systems if other areas are compromised. | * Chief Engineer reports to main engineering ready to assume control of systems if other areas are compromised. | ||
* Security Chief organizes search teams and patrol teams. | * Security Chief organizes search teams and patrol teams. | ||
* Non-essential personnel return to quarters. | * Non-essential personnel return to quarters. | ||
* Secure all communication lines. | * Secure all communication lines. | ||
Line 108: | Line 107: | ||
* Operations Officer begins continuous internal sensor scans and reports all anomalous signals to chief of security. | * Operations Officer begins continuous internal sensor scans and reports all anomalous signals to chief of security. | ||
* Department heads secure their areas and account for all personnel. | * Department heads secure their areas and account for all personnel. | ||
|- | |||
|6A | |||
|style="white-space: nowrap;"|Security Readiness<br>Heightened Security | |||
| | |||
* Security officers issued [[Phaser]] Rifles and body armor. | |||
* Security teams deploy to critical areas. | |||
* Post guards in critical areas. | |||
* Post guards at turbolifts, access points to adjacent decks, and [[transporter]] rooms. | |||
* Flag officers, commanding officer, along with 2nd and 3rd in command are encouraged to accept armed escorts. | |||
* Security Chief organizes additional patrol teams. | |||
* Secure all communication lines. | |||
* Restrict computer access to ''Level 1'' and above. | |||
* Seal all external hatches and doors. | |||
* Seal all decks from adjacent decks. | |||
* Seal all access to jefferies tubes. | |||
|- | |- | ||
|7 | |7 | ||
Line 127: | Line 141: | ||
* Initiates organization wide '''Condition 2''' across all [[Solas Tempus]] vessels, stations, and facilities. | * Initiates organization wide '''Condition 2''' across all [[Solas Tempus]] vessels, stations, and facilities. | ||
* Recalls all available [[Temporal Operatives]] and places them on active duty. | * Recalls all available [[Temporal Operatives]] and places them on active duty. | ||
* Blue Leader is put in de facto command of all Solas Tempus resources. | * Blue Leader is put in de facto command of all [[Solas Tempus]] resources. | ||
* All Temporal Operatives not involved in necessary operations are diverted to assemble at [[Integro Base]] immediately. | * All [[Temporal Operatives]] not involved in necessary operations are diverted to assemble at [[Integro Base]] immediately. | ||
* The '''Prometheus Association''' is assembled at [[Integro Base]]. | * The '''Prometheus Association''' is assembled at [[Integro Base]]. | ||
* All communications networks are placed under control of [[HAL 9000]] and [[BlueNet]]. | * All communications networks are placed under control of [[HAL 9000]] and [[BlueNet]]. | ||
|} | |} | ||
== Security Alert / Security Readiness == | |||
These conditions go hand in hand. However, a full security alert is not meant to be a prolonged status except in the most dire situations. As such ''Condition 6A'' is designed as a long-term status of heightened security with as little disruption to station life as possible. Many times one condition is a prelude to the other and department heads as well as command crews should maintain the ability to transition smoothly from one condition to the other. | |||
== Theta Protocol == | |||
A protocol developed for the [[Temporal Reconciliations]] to signal that a temporal catastrophe is imminent and must be responded to with as many resources as possible. This protocol has been used only once, and was invoked to give additional resources to governments in combating an [[Infinity Wave]] while a team was dispatched to the waves epicenter. The operation was successful and proved both the need for and the acceptable use of Theta Protocol. | |||
[[Category:Solas Tempus]] | [[Category:Solas Tempus]] |
Revision as of 07:11, 8 January 2017
Alert condition codes allow for standard procedures to be followed in specific conditions.
Colored Conditions
There are three standard conditions named after colors - these also correspond to the color of alert notification lights throughout a location.
- Condition Red / Red Alert corresponds to Condition 1
- Condition Blue / Temporal Alert corresponds to Condition 2
- Condition Yellow / Yellow Alert corresponds to Condition 3
- Condition Green / Normal Operations corresponds to Condition 0
- Grey Mode corresponds to Condition 7
Numbered Conditions
Number | Name | Description |
---|---|---|
0 | Condition Green |
|
1 | Tactical Alert Red Alert General Quarters Battle Stations |
|
2 | Temporal Alert Condition Blue |
|
3 | Yellow Alert |
|
4 | Environmental Alert |
|
5 | Decompression Alert Collision Alert |
|
6 | Security Alert |
|
6A | Security Readiness Heightened Security |
|
7 | Grey Mode |
|
Theta | Theta Protocol |
|
Security Alert / Security Readiness
These conditions go hand in hand. However, a full security alert is not meant to be a prolonged status except in the most dire situations. As such Condition 6A is designed as a long-term status of heightened security with as little disruption to station life as possible. Many times one condition is a prelude to the other and department heads as well as command crews should maintain the ability to transition smoothly from one condition to the other.
Theta Protocol
A protocol developed for the Temporal Reconciliations to signal that a temporal catastrophe is imminent and must be responded to with as many resources as possible. This protocol has been used only once, and was invoked to give additional resources to governments in combating an Infinity Wave while a team was dispatched to the waves epicenter. The operation was successful and proved both the need for and the acceptable use of Theta Protocol.