USS Nova, BB-106
| STARSHIP | |
|---|---|
 USS Nova, BB-106
| |
 | |
| Class | Pulsar Class Battleship |
| Registry | BB-106 |
| Allegiance | United Federation of Planets |
| Launched | 241002.20 |
| Status | Mothballed (242004.01) |
 | |
 | |
| Specifications | |
| Type: | Battleship (BA) |
| Length: | 1100 Meters |
| Beam: | 712 Meters |
| Height: | 300 Meters |
| Mass: | 4,800,000 Metric Tons |
| Decks: | 48 Deck Plans |
| Crew Compliment: | Standard: 600 Officers, 2,800 Enlisted Crew Breakdown Emergency: 6,000 |
| Warp Speed: | Type: 4 Main Warp Nacelles(Type 5E3) Cruise Speed: 5 (3 with saucer separation) Sustainable Speed: 9 (5 with saucer separation) Emergency Speed: 9.3 (12 hour automatic shutdown) |
| Impulse Engines: | Type:2 Main Impulse Engines (Class 8), 2 Secondary Impulse Engines (Class 5A) Speed: .93 C |
| Defensive Systems: | Type 1 Main Shield Generator (MSG-1) |
| Armament: | Phasers: 3 banks of 4 Type 1 (P/S/A) 3 banks of 3 Type 1 (1F/2A-360D) Torpedoes: 8 Torpedo Launchers (6F/2A) Payload: 500 Quantum Torpedoes, 1,000 Photon Torpedoes. |
| Computer System: | Daystrom Industries HSCS-1 |
| Tractor/Repulsor: | 2 Main Tractor/Repulsor Beams, 6 Docking Tractors, 6 Shuttle Tractors |
| Shuttlecraft: | 2 Bays (A), 12 Shuttles (8 Type 7, 4 Type 9A) 1 Runabouts (Type 1) 5 Dropships (2 MAD, 3 Type 2). 1 Seleya Class Captains Yacht |
| Fighters: | 1 Bay (A) 12 F-1 Fighters, 12 A-1 Heavy Attack Fighters, 1 EW-2 Electronic Warfare Fighters |
| Sensors: | Andorian Industries FSMSA-2 |
| Offensive Rating: | 90% |
| Defensive Rating: | 90% |
| Maneuverability Rating: | 50% |
| CER: | 70% |
The USS Nova is a Pulsar Class Battleship in service to Star Fleet. She was involved in the Attack on the Borg Megasphere, after which she was deemed unfit for continued service and remanded to Surplus Depot Z15 for storage.
Contents
Lineage
BB-106, USS Nova, is the latest addition to the Star Fleet. As a Pulsar-classed battleship, the Nova is as are most Star Fleet ships, a multi-role vessel capable of performing a variety of mission profiles including offensive, defensive, diplomatic, and exploration missions.
On Star Date 240607.22, Star Fleet Command ordered construction of a new Pulsar-classed battleship, construction contract BB-106. The ship was unnamed at that time. Construction was due to complete on Star Date 241009.27. When the Romulan conflict erupted on Star Date 20806.20, Star Fleet Corps of Engineers was ordered to accelerate production of all combat vessels, and BB-106's launch date was updated to Star Date 20912.31. The ship was also named USS Nova, and assigned under the command of Commodore Laurence Green. Green's untimely illness and death resulted in a vacancy for command of the Nova.
Nova also serves as the flagship of the 4th Fleet and as Vice Admiral Thomas Grayson's official flagship.
Current: USS Nova, BB-106
Vessel Class: Pulsar
Assigned: 4th Battle Group
Commanding Officers:
Derrick Grant, Star Date 241003.01-241004.13
Thomas Grayson, Star Date 241004.13-241101.02
Draev {Torkav}, Star Date 241101.02-present
Previous Star Fleet Vessels named USS Nova
NCC-73515, Earth Year 2379, deployed to Romulan Neutral Zone in anticipation of an invasion.
Vessel Dedication Quote
"If we desire to avoid insult, we must be able to repel it; if we desire to secure peace, one of the most powerful instruments of our rising prosperity, it must be known, that we are at all times ready for War."
- George Washington
Images
Pulsar Classed Battleship
Aft Approach
Forward Approach
Bye Bye Gettysburg
Deck One
Flight Deck
Strategic and Tactical Operations
Ten Forward Lounge
Runabout
Type-7 Shuttle
Type-9A Shuttle
CO Quarters
Patch
Command Patch
Tactical Patch
Security Patch
Engineering Patch
Medical Patch
Science Patch
Marine Patch
Air Patch
Support Patch
Dedication Plaque
Auxiliary Craft
Admiral's Yacht, Seleya-Classed
USS Blackstone, BC-106/Y
Runabout, Type-1
USS Charles, BC-106/R
Shuttles, Type-7
Oklahoma, BC-106/1
John Wayne, BC-106/2
Alamo, BC-106/3
Pauling, BC-106/4
Brown, BC-106/5
Rutherford, BC-106/6
Diamond, BC-106/7
Amethyst, BC-106/8
Shuttles, Type-9A
Charaka, BC-106/9 - Security
Cayley, BC-106/10 - Engineering
Zion, BC-106/11 - Medical
Moses, BC-106/12 - Science
Marine Support Craft
The USS Nova carries the following Marine Support Craft within her large flight deck. These craft are used for Marine deployments and fall under the direct command of the Marine Commander (MARCO).
Marine Assault Dropship (MAD) Vessels
USS Rommel, BC-106/MAD1
USS Francis, BC-106/MAD2
Type-2 Marine Dropships
Abrams, BC-106/MD1
Challenger, BC-106/MD2
Tiger, BC-106/MD3
Crew Manifest
| Command Staff | ||||
|---|---|---|---|---|
 |
Grant, Derrick Hiram Ulysses {Torgh} | Commanding Officer | Human | |
| Tactical Department | ||||
 |
David Sheppard {DeWitt} | Chief Tactical Officer | Human | |
 |
Joseph Tyler | Operations Officer | Human | |
| Engineering Department | ||||
| Security Department | ||||
 |
Angel Reverez {Banks} | Chief of Security | Human / Betazoid | |
| Science Department | ||||
| Medical Department | ||||
 |
Taar {Adaran} | Acting Chief Medical Officer | Tellarite | |
| Star Fleet Marine Corps | ||||
| Civilians | ||||
| LOA | ||||
Bridge Positions
Helm
The primary job of the helm officer is obvious: steer the ship. However, the nuances of this job are more subtle. A Helm officer is not only responsible for punching coordinates into the ship’s console; their position is also relevant when the ship is stopped. The Helm officer is responsible for ensuring that ship stays in position relative to other objects around it. This can include monitoring orbit around a planet or ensuring that the ship doesn’t drift into a starbase or another ship. Additionally, the helm officer is responsible for engaging in evasive maneuvers and attack patterns during an encounter.
External Communications
The External Communications officer is responsible for all communication that comes in from outside the ship, and all communication that is direct from the ship to the outside universe. This includes ship-to-ship communications as well as sending reports and data to Star Fleet, and monitoring the in- and outflow of personal communications.
Internal Communications
The Internal Communications officer’s most important duty is maintaining the flow of information between departments. Events on the Bridge can get very busy, and it is not always possible for stations to share information with their own department, let alone other departments. That is when the Internal Communications officer steps in to send regular reports about Bridge activity to each department.
In times of lower Bridge activity, the Internal Communications station can also be used an auxiliary station.
Science
The main Science station is used to monitor external sensors pertaining to scientific data. This includes the study of space particles, spacial anomalies, planetary bodies, etc. Most other external sensor duties fall to the officer at the Weapons station.
In cases of extensive study, the auxiliary station beside the main Science station is used as a secondary science station.
Flight Control
The Flight Control console is dedicated to managing the fighters, shuttles, and runabouts of the ship. When none of these auxiliary craft are in operation, the console is unmanned or used for other purposes.
Weapons
The officer at the Weapons console is responsible for external weapons pertaining to surrounding ships and starbases. It is necessary for this officer to manage these sensors in order to be ready for battle and weapons locks. This officer is also usually responsible for tractor beams, along with Operations and Engineering.
Strategic Operations
The officer at the Strategic Operations console is specialized for managing the big picture. This officer monitors the entire flotilla, including all auxiliary craft. They provide verbal information to the Commanding Officer so that he or she is able to make informed decisions regarding fleet activity.
Engineering
The officer at the Engineering console is responsible for managing systems and power distribution ship-wide. They maintain open communications with Engineering to ensure that repair teams are sent where they are needed. They may also be responsible for deflector dish control and tractor beams along with Weapons and Operations.
Security
The officer at the Security station is responsible for monitoring the positions of personnel around the ship to ensure that conflicts do not occur. They may direct security teams depending on Bridge orders, and they may be called upon to monitor the safety of an away team.
Operations
Whereas the Strategic Operations officer is responsible for the big picture of the flotilla, the Operations officer is responsible for the big picture of the ship. The provide backup to Security, Engineering, Communications, Weapons, and Science. Because their console is specialized to show multiple viewpoints at once, the officer there should be specialized to view patterns and put things together to provide input on the situation at hand.}
How points are awarded on the Nova
Summary
The policy being stated here initiates on January 1, 2010.
Constitution directive 1.3.4 states that “All applicants/members must agree to make at least two story oriented posts a week. (Exception: See 3.6) Out of Context (OOC) post don’t count towards this total”. The maximum participation points awarded is 500 per month. The Commanding Officer of the ship is charged with determining how to rate participation.
1. During a mission:
1.1. Each in-game, player-character (not NPC) post will merit 50 points, provided it meets one of the following criteria (up to a maximum of 400 points per month):
1.1.1. Mission value: A post which helps to move the mission along or helps to develop the storyline.
1.1.2. Post length/quality overall: A post which has full paragraphs and detail. Two-liners do not rate well!
1.1.3. Character building: A post which may not accomplish either of the above but builds the character should be given a higher consideration.
1.2. These are GUIDELINES. DH’s should use them when evaluating the posts of their subordinates, and making their recommendations to the FO; who will use the same guidelines when making their recommendation to the CO (me). Then I will use them as I make any adjustments I feel prudent.
1.3. An additional 100 points may be awarded to any player at the recommendation of the DH, FO, or CO (me again!) for quality or other reasons. Again, this is subjective.
1.4. Any player who’s absence (announced LOA or otherwise) of more than 5 days causes one of the main plotlines on the ship to be held up, or causes other players to be forced to wait on them in the mission, will have points deducted based on the following criteria:
1.4.1. 100 points per 5-day period after the third day of absence;
1.4.2. Additional points as determined by the CO based on the level of disruption.
1.4.3. If the player informs the CO or FO that they will be gone and that their character can be ‘hijacked’ or placed in a non-pivotal role for that time, then the penalty will be automatically waived. However, in order to receive full points, the player must make a minimum of 8 posts during the rest of the month.
1.5. Any time a player is awarded less than the maximum 500 points recommended for the month; he/she/it will be notified via email from the Captain. This will generally be after points are finalized and sent to the GC.
1.6. Anytime a DH or FO points recommendation is overridden, then the CO will email the FO and associated DH with an explanation as to the alteration and why.
1.7. Points awards issues or questions should be addressed to the CO in email at all times.
2. Non-Mission (shoreleave):
2.1. A simple 50 points per post shall be awarded, up to a maximum of 400; plus the 100 quality judgment.
2.2. LOA’s must still be requested, as normal, however points calculations will not account for the missing time unless it infringes upon the beginning or end of a mission.
3. Department Head (DH) points:
3.1. The rules allow for up to 100 points per month for DH duties as judged by the CO.
3.2. These points are a combination of two administrative aspects of your duties as a DH:
3.2.1. Keeping your subordinates involved and posting. This accounts for 50 points per month-prorated.
3.2.1.1. In a mission, this means that they have something to do , regardless of the mission parameters. As a senior player, a DH should ALWAYS be able to find something to keep their people busy.
3.2.1.2. Outside of a mission, this includes helping them (as necessary) to come up with subplots or involving them in other activities in game.
3.2.2. Performing administrative duties. This accounts for 50 points per month-prorated.
3.2.2.1. Submitting points at end of month, prior to the 21st of each month at midnight site time, unless otherwise instructed by the CO or FO. You should NOT need to be reminded to do points.
3.2.2.1.1. Missing points one month will result in a 25-point positional deduction;
3.2.2.1.2. 2nd consecutive month will result in a 50-point positional deduction;
3.2.2.1.3. 3rd consecutive month will result in 100-point positional deduction (no positional points) and may also result in being put on probation for your position at the discretion of the CO.
3.2.2.1.4. 4th consecutive month and beyond will most certainly result in dismissal in your position.
3.2.2.2. Submitting an RPG’er recommendation for the month. Recommending NO ONE is valid, provided you explain it. If you simply do not mention RPG’er at all, you will have 20 points deducted from your positional points.
3.2.2.3. With your points and RPG’er you are asked to provide a briefing on your subordinates and the department and why you recommended RPG’er.
3.2.2.4. Keeping in contact with crew members who are not posting regularly.
3.2.2.4.1. If you see one of your subordinates not posting for 5 or more days, drop them a friendly line asking them if everything is OK, etc.
3.2.2.4.2. Contacting crew for various reasons at the request of the CO or FO.
4. First Officer (FO) points:
4.1. FO is awarded up to 200 points per month at the discretion of the CO.
4.2. Points are based on the above, plus:
4.2.1. Accepting points recommendations from the DH’s and processing them.
4.2.2. Providing a points recommendation update and crew update to the CO on or before 23rd of each month except where changed by the CO.
5. Commanding Officer (CO) points:
5.1. CO is awarded up to 300 points per month at the discretion of the GC and CinC.
5.2. Points are based on all of the above, plus:
5.2.1. Processing points from the FO and submitting to the GC prior to 25th of each month except where ordered otherwise.
5.2.2. Administrative duties relating to mission, timelines, etc.
Conclusion
The short of the above is… if you post (and in the case of DH’s and above do your other duties), you’ll get full (400) points with potential for an additional 100 points for quality. If you don’t, then you won’t.
If you have any questions, please contact the Commanding Officer.
Mission Logs
