I've been thinking about the crew complements of the Star Cruiser ship designs and I think they are somewhat too approximate. Several notes about the subject:
1) Starship crews have to work and spend their lives in cramped conditions for months, so at least three watches are needed.
2) Bridge and engineering crew members have two watches. Second engineering watch will be doing damage control during alerts, but what is second bridge watch doing?
3) TAC crew mans the TAC during alerts, but what are they doing during normal travel conditions?
4) When starship is travelling between stars effectively faster than light (several hundred times faster, actually), no communications contact can be made. So why all bridge work stations (including communications) are always manned?
So, these are the major problems. Quick fix for them is to keep given crew complements (2xBridge, 1xTAC, 2xEngineering, 1xOthers) but to re-schedule their watches. Crews are probably cross-trained, so two bridge watches and TAC crew can man brige work stations and for example sensor work stations. This usually gives more crew than work stations, so high ranking officers probably won't stand watches.
EXAMPLE: Kennedy Class Fast Missile Carrier
(different sources give different numbers)
Bridge 2x10, TAC 16-18, Engineering 22-24, Medical 3-4, Ship's Troops 10-27. I'll presume that numbers 20 for bridge (1 cmd, 1 nav, 1 hlm, 3 eng, 2 com, 2 cmp), 16 for TAC (2 sen, 10 gun, 4 rem) and 24 for engineering (9 drv, 9 ele, 6 mec) are correct. So we have 26 and 24 people to man brige and engineering work stations round the clock.
Not quite enough, so I would man only command (officer of the deck), navigation (quartermaster), helm and engineering (3), sensor (2) work stations. Engineering would do with 8 (out of 12) manned workstations. So we'd get sufficient manning for all critical work stations. During higher readiness half of the brige and TAC stations and all engineering work stations would be manned and during alert every man is on duty.
As mentioned before, we have extra 10 crew members during the alert. That would be the senior officers (Captain, XO, Ops, Comm, Weps etc.) making decisions while enlisted crew members operate the actual work stations.
I have based my crew calculations to what information I have about US and Royal Navy submarine services. US Navy subs have their crew devided to four divisions: Operations (led by Operations officer, Ops), Weapons (led by Weapons Officer, Weps), Engineering (led by Chief Engineering officer, Cheng) and Executive Division (led by Executive officer, XO). Other typical officer positions are Navigations, Communications, Sonar, Supply (under XO) and several junior engineering officers.
Submarine crews stand 6 hour watches which makes their "days" 18 hours long. Under the waves (as in space) it really won't matter. This way the crew endurance is sufficient for 2 or 3 month cruises.
These would be easy and reasonable fixes for starship crews, it remains to be seen if I settle with these or would I make my own ship design rules whit detailed crew complement calculations.
Hope this post isn't too long... Comments?
- Jeddak
1) Starship crews have to work and spend their lives in cramped conditions for months, so at least three watches are needed.
2) Bridge and engineering crew members have two watches. Second engineering watch will be doing damage control during alerts, but what is second bridge watch doing?
3) TAC crew mans the TAC during alerts, but what are they doing during normal travel conditions?
4) When starship is travelling between stars effectively faster than light (several hundred times faster, actually), no communications contact can be made. So why all bridge work stations (including communications) are always manned?
So, these are the major problems. Quick fix for them is to keep given crew complements (2xBridge, 1xTAC, 2xEngineering, 1xOthers) but to re-schedule their watches. Crews are probably cross-trained, so two bridge watches and TAC crew can man brige work stations and for example sensor work stations. This usually gives more crew than work stations, so high ranking officers probably won't stand watches.
EXAMPLE: Kennedy Class Fast Missile Carrier
(different sources give different numbers)
Bridge 2x10, TAC 16-18, Engineering 22-24, Medical 3-4, Ship's Troops 10-27. I'll presume that numbers 20 for bridge (1 cmd, 1 nav, 1 hlm, 3 eng, 2 com, 2 cmp), 16 for TAC (2 sen, 10 gun, 4 rem) and 24 for engineering (9 drv, 9 ele, 6 mec) are correct. So we have 26 and 24 people to man brige and engineering work stations round the clock.
Not quite enough, so I would man only command (officer of the deck), navigation (quartermaster), helm and engineering (3), sensor (2) work stations. Engineering would do with 8 (out of 12) manned workstations. So we'd get sufficient manning for all critical work stations. During higher readiness half of the brige and TAC stations and all engineering work stations would be manned and during alert every man is on duty.
As mentioned before, we have extra 10 crew members during the alert. That would be the senior officers (Captain, XO, Ops, Comm, Weps etc.) making decisions while enlisted crew members operate the actual work stations.
I have based my crew calculations to what information I have about US and Royal Navy submarine services. US Navy subs have their crew devided to four divisions: Operations (led by Operations officer, Ops), Weapons (led by Weapons Officer, Weps), Engineering (led by Chief Engineering officer, Cheng) and Executive Division (led by Executive officer, XO). Other typical officer positions are Navigations, Communications, Sonar, Supply (under XO) and several junior engineering officers.
Submarine crews stand 6 hour watches which makes their "days" 18 hours long. Under the waves (as in space) it really won't matter. This way the crew endurance is sufficient for 2 or 3 month cruises.
These would be easy and reasonable fixes for starship crews, it remains to be seen if I settle with these or would I make my own ship design rules whit detailed crew complement calculations.
Hope this post isn't too long... Comments?
- Jeddak