USS Copernicus, GSC-9035
| USS Copernicus, GSC-9035 | |
|---|---|
 | |
| Class | Einstein-class |
| Registry | GSC-9035 |
| Affiliation | Federation\Star Fleet |
| Status | Active () |
 | |
Contents
Lineage
Named for the famous astronomer Nicolaus Copernicus, the USS Copernicus is a Einstein Class Galactic Science Cruiser (GSC) assigned to the 1st Fleet. Equipped with conventional tactical and state of the art propulsion systems, as well as cutting-edge scientific and communication equipment, the Galactic Science Cruisers serve as the vanguard for Star Fleet’s scientific and exploration efforts.
The following Star Fleet vessels have carried the name Copernicus:
USS Copernicus, NCC-623, the first Starship to bear the name, was an Oberth-class Federation vessel in service during the late 23rd century.
Current: USS Copernicus, GSC-9035
Vessel Class: Einstein
Commanding Officer:
Captain Ysiadina Lanael (20306.01 - 20311.15)
Captain Darsyn Syntranos (20311.15 - 20402.23)
Captain Elisa Godard (20403.04 - 20812.31)
Commander Gloria Dys (20809.04 - 20901.25, ACO)
Captain Stovon Stewart (20901.25 - 21009.25)
Captain Jaden Hawk (21009.25 - 21302.19)
Captain Jane Fields (21302.19 - Present)
The USS Copernicus GSC-9035 was launched on Stardate 20306.01 from the Archimedes Shipyards in response to the Borg threat against the Federation.
The dedication plaque reads: "Courage is resistance to fear; mastery of fear - not absence of it."--Mark Twain
Specifications
| Type: | Galactic Science Cruiser (GSC) |
| Size | |
|---|---|
| Length: | 474 Meters |
| Width: | 156 Meters |
| Height: | 71 Meters (23 Decks) Deck Plans |
| Weight: | 3,651,000 Metric Tons |
| Crew | |
| Standard: | 173 Officers, 691 Enlisted Crew Breakdown |
| Emergency: | 1,500 |
| Warp Engines | |
| Type: | 2 Main Warp Engines (Type 6D) |
| Cruise Speed: | 6.2 (3 with saucer separation) |
| Sustainable Speed: | 9.3 (7 with saucer separation) |
| Emergency Speed: | 9.6 (12 hour automatic shutdown) |
| Impulse Engines | |
| Type: | 1 Main Impulse Engines (Class 5), 2 Secondary Impulse Engines (Class 3) |
| Max Impulse: | .93 C |
| Defensive Systems | |
| Type: | Type 3 Main Shield Generator (MSG-3) |
| Other: | None |
| Offensive Systems | |
| Phasers: | 1 bank of 4 Type 1 (F/360D) |
| Torpedoes: | 1 Quantum Photon Torpedo Tubes (1F) |
| Other: | Increased Sensor/Communication abilities. |
| Computer Systems | |
| Type: | Daystrom Industries HSCS-3SC |
| Tractor/Repulsor | |
| Type: | 2 Main Tractor/Repulsor Beams, 6 Docking Tractors, 2 Shuttle Tractors |
| Shuttles | |
| Type: | 1 Bay (A), 8 Shuttles (6 Type 7, 2 Type 9A) 1 Runabout (Type 1). 1 Lanthanum Class Science Escort (ESS) |
| Fighters | |
| Type: | None |
| Sensors | |
| Type: | Andorian Industries FSMSA-5 |
| Combat Ratings | |
| Offensive: | 45% |
| Defensive: | 90% |
| Maneuvering: | 60% |
| CER: | 65% |
Crew Manifest
| Command Staff | ||||
|---|---|---|---|---|
 |
Jane Fields | Commanding Officer | Human | |
 |
Alora Dys | First Officer | Ferengi/Human | |
| Tactical Department | ||||
 |
Mathew Briggs | Chief Tactical Officer | Human | |
|
Alex Nesmith | Tactical Officer | Human | |
| Engineering Department | ||||
 |
Harrison Boislevesque | Chief Engineer | Human | |
 |
Irisi Sen | Engineering Officer | Farian | |
| Security Department | ||||
| Vacant | Chief of Security | |||
 |
Astrid Peth | Security Officer | Human | |
|
Marcus Vesner | Security Officer | Human | |
| Science Department | ||||
| Vacant | Chief Science Officer | |||
 |
Luminara Bennett | Science Officer | Human/Vulcan | |
| Medical Department | ||||
 |
Daniel Brooks | Chief Medical Officer | Human | |
 |
Michael Levrock | Medical Officer | Human | |
See USS Copernicus NPC Crew Manifest
Captain's Logs
Mission Log 1 - Stardate 20304.22 "First Entry"
Mission Log 2 - Stardate 20401.15 "One Lump, or Two?"
Mission Log 3 - Stardate 20409.25 "The Borg Conduit"
Mission Log 4 - Stardate 20512.22 "Now You See it, Now You Don't: Rainbows "
Mission Log 5 - Stardate 20612.22 TBD
Mission Log 6 - Stardate 20802.03 "Into the Void."
Mission Log 7 - Stardate 20809.13 "If it Looks too Good to Be True"
Mission Log 8 - Stardare 20903.02 "Phoenix Into the Flames"
Mission Log 9 - Stardate 20910.15 "Paradise Lost and Paradise Regained"
Mission Log 10 - Stardate 21010.04 "Ghosts"
Mission Log 11 - Stardate 21107.16 "Past, Present, Future"
Auxiliary Craft
Science Escort, Lanthanum-Classed
USS Dysprosium, ESS-9035/A
Runabout, Type-1
USS Sagan, GSC-9035/R
Shuttles, Type-7
Argon, GSC-9035/1
Neon, GSC-9035/2
Xenon, GSC-9035/3
Krypton, GSC-9035/4
Radon, GSC-9035/5
Helium, GSC-9035/6
Shuttles, Type-9a
Palladium, GSC-9035/7
Iridium, GSC-9035/8
How points are awarded on the Copernicus
Summary
The policy being stated here initiates on December 16, 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 of Constitution.) Out of Context (OOC) posts 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. Points run from 16-15th of each month and are published in the Red Alert thread on the 1st of each month.
(1) During a mission:
1.1. Each in-game, player-character post (which could also include a Non-Playing Character post, see point 1.2 below) will merit 50 points, providing 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. DHs 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. The CO will make any adjustments they feel prudent. Note: NPC posts can accrue a player points in the same way as PC posts, though points may NOT be awarded in such instances if an NPC post appears to have been given priority over a PC post where the latter seems more urgent in moving along the mission/providing other players with a response.
1.3. An additional 100 points may be awarded to any player at the recommendation of the DH, FO, or CO for quality or other reasons. This is a subjective judgement.
1.4. Any player whose 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 for a response, 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 they can contact the CO to find out the reason for this.
1.6. Any time 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 and cc-ed to the FO.
(2) Non-Mission (shore leave):
2.1. A simple 50 points per post shall be awarded, up to a maximum of 400; plus the 100 quality judgement.
2.2. LOAs must still be requested as normal.
(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. During 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 18th 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 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.1.5 Persistent lateness in submitting points will result in deductions of 25-50 points dependent on the consistency and extent of lateness.
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 an explanation of why you recommended RPG’er. This is to help the CO decide on the final choice of 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 DHs and processing them.
4.2.2. Providing a points recommendation update and crew update to the CO on or before 21st 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 24th 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 you’ll get full (400) points with potential for an additional 100 points for quality. If you don’t, then you won’t.
Holding up missions and leaving other players waiting for a response will also be penalised and may see your character hijacked by the Command Staff to move things on.
If you have any questions, please contact the Commanding Officer and First Officer.
