Omake - Increasing the Force - cast2007
Increasing the Force

To: Admiral Kahurangi, Commander Starfleet
From: Rear Admiral Seruk, Commander Personnel Command
CC: Rear Admiral, Guk Commandant Starfleet Academy
Subject: Integration of Prior Service Individuals

With the Federation set to admit its first member since its foundation nearly a hundred and fifty years ago and a number of other affiliates slated to join over the next decade, Starfleet is facing an issue that hasn't arisen since the founding of the Federation: how to integrate individuals with prior service into Starfleet. Although we prefer to recruit personnel with no prior experience in order to train them from the ground up, it would be foolish of us to dismiss those individuals with an desire to serve in Starfleet who had the misfortune to be born prior to their home government's contact with the Federation. This is especially true given the goals set for fleet expansion and a bottleneck in terms of trained personnel.

While Rear Admiral Guk and I agree that such individuals will need to be subject to training to ensure that they are up to Starfleet Standards, we believe that requiring such individuals to attend Starfleet Academy for four years and commissioning them as an Ensign afterwards would be an improper use of resources and patronizing towards said individuals. We have identified three distinct pathways each with a one year curriculum which we believe will allow us to integrate said individuals into Starfleet quickly and while maintaining the high standards expected of Starfleet. Applicants to the below programs must be in good standing with their current uniformed organization as well as the recommendation of at least one Starfleet Officer.

Pathway A

This pathway is intended for those personnel with 2-5 years worth of experience. The goal of said curriculum is to get said personnel acclimated into Starfleet and into the Fleet as an experienced Junior Officer. Upon completion, the Candidate will receive a Commission of Lieutenant (Junior Grade).

Pathway B

This pathway is indented for those personnel with 5-8 years of experience. The purpose behind this curriculum is to ensure that the candidate is capable of serving as the Second in Command to a Ship's Department Head or in the case of an Escort, a Department Head if need be. Upon completion, the Candidate will receive a Commission of Lieutenant.

Pathway C

This pathway is intended for those personnel with 8-12 years of experience. The objective behind this curriculum is to train said candidate into a Department Head or prospective First Officer. Upon completion, the Candidate will receive a Lieutenant Commander's Commission.

In the case of very experienced individuals outside our proscribed ranges, we believe that such applications will be rare and should be reviewed on a case by case basis.

Although we foresee some traditionally minded officers opposing this, we would like to remind them that the first generations of Starfleet Officers did not come from the Academy but were drawn from the ranks of their Member Uniformed Organizations. If it was good enough for them, we see no reason why it cannot work for us.
 
Last edited:
So Given that we don't have Q4 decisions to make, I suppose we might as well discuss the 2307Q1 Build Plan. I know it's two Captain's Logs out, but why not?

Now the Centaur-A won't be available until the end of 2307Q4, so there's no use building new Centaurs right now. Nor new Constellations. So basically, I think we start a new Excelsior in the Andorian dock that will be open and otherwise start no new construction.

2308Q1 is when we begin a massive tide of Centaur-A models. I would go big out the gate and build 4 at once then. But as of 2307Q1 I don't see anything worth starting other than another Excelsior. No point in building a ship we would then be immediately sending back to the docks for an upgrade.
 
So Given that we don't have Q4 decisions to make, I suppose we might as well discuss the 2307Q1 Build Plan. I know it's two Captain's Logs out, but why not?

Now the Centaur-A won't be available until the end of 2307Q4, so there's no use building new Centaurs right now. Nor new Constellations. So basically, I think we start a new Excelsior in the Andorian dock that will be open and otherwise start no new construction.

2308Q1 is when we begin a massive tide of Centaur-A models. I would go big out the gate and build 4 at once then. But as of 2307Q1 I don't see anything worth starting other than another Excelsior. No point in building a ship we would then be immediately sending back to the docks for an upgrade.
That makes sense. And once those Centaurs are built, we can refit the ones we have while possibly building more.
 
You're overstating the effect of the doctrine, I think. The Lone Wolf Doctrine mostly helps Explorers. The Constitution -B isn't an Explorer, it's a slightly oversized cruiser. It's only 200k bigger than our modern-ish escort. The Lone-Wolf doctrine help with ship fighting alone, but I don't think we should be sending the Constitution-B into skirmishes unsupported. The only ship that we should be doing that with is the Excelsior.
Lone Ranger doctrine gives a bonus when fighting outnumbered, not just when alone. Which does mean that the Connie-B fits into that sort of fleet paradigm fairly well. Smaller numbers of superior ships & all that.
 
Alright, after playing around some more, I figured out what the heck I was doing wrong(namely editing the orange fields instead of the yellow one s a little further to the right-thankfully on a copy!), and now I have a different problem: I can't seem to figure out how to bring BR costs down to something that matches what the Rennie is supposed to cost. What techs reduce BR?
 
Lone Ranger doctrine gives a bonus when fighting outnumbered, not just when alone. Which does mean that the Connie-B fits into that sort of fleet paradigm fairly well. Smaller numbers of superior ships & all that.
Lone ranger fits Star Trek, because heroic odds.

Well, until Wolf 359. Then, the fleet scrambles to shift to Combined Arms. If you think about it, the fleet didn't get its outnumbered bonus there, because they were against a singular Borg cube.

Alright, after playing around some more, I figured out what the heck I was doing wrong(namely editing the orange fields instead of the yellow one s a little further to the right-thankfully on a copy!), and now I have a different problem: I can't seem to figure out how to bring BR costs down to something that matches what the Rennie is supposed to cost. What techs reduce BR?
BR is fine.

Also, we should design the Rennie as a heavier light cruiser.
 
Alright, after playing around some more, I figured out what the heck I was doing wrong(namely editing the orange fields instead of the yellow one s a little further to the right-thankfully on a copy!), and now I have a different problem: I can't seem to figure out how to bring BR costs down to something that matches what the Rennie is supposed to cost. What techs reduce BR?
None do it directly, but don't sweat increased BR costs. SR is the real bottleneck for the forseable future.

Also, we should design the Rennie as a heavier light cruiser.
What does that mean?
 
Huh, playing with the spreadsheet, I'm sure I fucked something up. Can someone point to me what I did wrong and why this shouldn't work like it says it does? Otherwise you guys have been doing strange things to get your rennie builds...
Your 'Structural Integrity Field Efficacy' looks absurd and your 'Warp Core Power Rating' seems to take ten levels of design tech. Trying to reverse engineer what you did required ~24 techs and gave a reliability of 91.31%. It looks like you broke something while playing around with the sheet, so you should check for that.

*ninja'd*
Alright, after playing around some more, I figured out what the heck I was doing wrong(namely editing the orange fields instead of the yellow one s a little further to the right-thankfully on a copy!), and now I have a different problem: I can't seem to figure out how to bring BR costs down to something that matches what the Rennie is supposed to cost. What techs reduce BR?
None.
 
BR is only determined by the tonnage of your ship.

SR can be reduced using the SR efficiency tech, but at the cost of reliability.
 
They all influence the weight (technically, it would be mass, not weight) of the ship, thus increasing the BR. Bulk resources are dependent on the weight.
 
Last edited:
After some experimenting I was able to squeeze H+1 and D+1 out of the Defender design by adding a 0.50 scale module and one more extra tech. Cost has increased by 10 BR and 5 SR. Tonnage has slightly decreased.

Defender Type 2 (working title) [315m 795k t]
C3 S1 H4 L3 P1 D4
Cost[80br, 40sr, 2 years], Crew [O-?, E-?, T-?]
99.6% Reliability, 3 extra techs required

@OneirosTheWriter A short question: Does reusing components such as the Miranda roll-bar mean you don't have to research the Weight Sv Levels those components already have, or do you still have to research them as extra-tech?
 
Last edited:
Captain's Log - 2306.Q3
Captain's Log, USS Enterprise, Stardate 22335.6 - Captain Nash ka'Sharren

Apinae is a beautiful world, from its verdant forests and plains, to its delicate cities. Tall spindly towers, buildings clustered and intertwined. The Apiata working caste seems to have little care for ideas of personal space, and seem quite happily to clump up. I nearly blew up the Universal Translator when I said "introvert". We have been feted a few times at the Grand Comb of Apiata, then retiring to the Enterprise, which is working well so far. Izzidiera is staying with us, though that is ... causing it's own fair share of headaches.

I'm starting to dread seeing those antennae coming around the corner! She has a lot of charming moments, such as when she hosted me for dinner. But the next day when I had the Yeoman deliver a report she was looking for, she came to main engineering to berate me for not doing it myself! Which reminds me...


Note to self: find out how Izzidiera got access to main engineering...

-

Captain's Log, USS Courageous, Stardate 22336.5 - Maryam Ajam

After entering the system of Ulysses-34 and discovering it to be inhabited, we were immediately accosted by a number of small frigates. After being hailed by them, we learned that they were the Apiata that Nash's Enterprise reported recently. Not wishing to spoil things, and curious as to what this was about, I agreed to power down weapons, but left my shields up, and asked to talk it out with their Queens.

The soldiers on the ships spent a long time debating, but then asked us to maintain orbit around the nearest planet, Ulysses-34 IX. A Queenship is coming to deliver a representative.

-

Captain's Log, USS Sarek, Stardate 22337.2 - Captain Straak

After a truly inefficient series of months spent dealing with a wide variety of the most illogical sentients, I am pleased to report that the USS Sarek has returned to mapping unexplored star systems. This is a most satisfactory course of action.


After all, pulsars emit their destructive bursts of energy and radiation with logical predictable regularity. I can say no such thing for Gaeni Tech-Cruisers, the wisdom of whose designs are still a matter of meditation for me.

-

Captain's Log, USS Miracht, Stardate 22337.4 - Captain Michel Thuir

Rim-ward of Borandt III we've discovered a colony world of the Sydraxian Hierarchy. It's home to about half a billion Sydraxians, and seems to have been one of their first colonies. A large starbase sits in orbit protecting it, as well a considerable shipyard. I am heading into orbit and keeping up a dialogue with the colony administrators.

Buying time, of course, to host a singing contest aboard ship.

After all, reviewing the logs of Commodore T'Lorel's experience here tells me that I may need a good singer. Not to mention finding one I can trust not to sing of any propensity towards blowing things up.

-

Captain's Log, USS Enterprise, Stardate 22337.8

Thanks to Izzidiera's intervention, I have been given access to the High Council of Queens. I believe that I gave a good account of my ship and the Federation. Meeting all these illustrious queens, though... I am worried. I think a big question still looms over how the Queen/Worker scenario works with the Federation's stance on individual freedoms. The workers are, after all, born with the urge to serve their Queens and from what I'm told, being cut off from them for an extended period is extremely upsetting. But this gives us a scenario whereby a great swathe of sentient people are held in willing servitude.

I admit, I'm a little concerned about how it will play out.

-

Personal Log, Nash ka'Sharren, Stardate 22337.9

I, uh, winked at a one of the Queens who was flirting with me during a soiree. and Izzidiera buzzed loud enough that my security chief came from three doors over to investigate.

By the star of Andor...

Also, I received a very angry private communique from a Federation diplomat. I don't see how this whole Queen/Worker problem is my fault. It's not like a go looking for curly issues to hand the diplomats.

-

Captain's Log, USS Cheron, Stardate 22338.1

We have arrived at the Indorian colony world of Pridorin IV, a mining colony just on the Federation side and core-ward of their homeworld, responding to a distress call. It seems that a large escort ship has been attempting to intimidate Indorian trade vessels in the area that were headed for Amarkian space. We are first on the scene, but the Kumari and Challorn are responding as well, and should be here within the hour.

The CDF Parok responded to our hails, but denied harassing Indorian ships. Instead they claimed to be trying to help the Indorians prevent "wasting valuable resources on Starfleet decadence."


As per our rules of engagement, we have closed with the Parok at Red Alert, and they have withdrawn. However, a Jaldun-class destroyer has appeared immediately in their stead.

I have withheld fire and am buying time for the arrival of the Kumari and Challorn. Hopefully, no further Cardassian reinforcements are en route as well.

-

Captain's Log, USS Enterprise, Stardate 22338.3

A deep sea kraken has breached in the middle of our attempts at diplomacy, to borrow an old Andorian phrase. It seems that reports have reached Apinae that one of our sister ship was attacking Apiata foragers in a nearby system according to sensor logs recovered from the wreckage. This is completely preposterous, but as the Apiata have only just met us, there isn't much past history to draw on! It got even more ludicrous when I learned it is Maryam's ship, the Courageous, that is alleged to have done this.

When I explained it was my old first officer, they immediately grew less angry (when they first confronted me with these sensor logs, there was so much buzzing in the room I could hardly hear myself think), but they also then demanded I go to Dorsata to help prove the Courageous' innocence. Well, I was going to do that anyway, as Maryam has sent me a not-distress call asking if the Enterprise was up to much.

-

Captain's Log, USS Courageous, Stardate 22338.6

Logs! Entire sensor logs stuffed full of nothing but lies!

The Apiata have confronted us with these phony sensor logs that were apparently "kindly" retreived by the CDF Trager, which we had the displeasure of discovering was sitting in orbit. Of course, while we know they are lies, proving them to be is anothing thing entirely. Nonetheless, we have agreed to present our case to the Council of Queens at Dorsata colony. I have put in a call to the Enterprise as well. Although an Excelsior has little to fear from a Jaldun-class destroyer, we did get a sensor reading briefly of something rather larger hiding out in the outskirts of the system, and I'd rather have the backup.

-

Bridge Transcript, USS Enterprise, Stardate 22338.8

[Cdr Zaardmani] We have dropped out of warp ... bang on target.

[Qn Izzidiera] Bleh, Dorsata. Boring place.

[Cdr Zaardmani] We have Cardassian contacts in orbit.

[Capt ka'Sharren] Imagine my surprise.

[Cdr Mrr'shan] Looks like our old friends, the Trager.

[Capt ka'Sharren] Ah! Gul Miran! Hail them, comms, on screen.

[Gul Miran] Captain, we meet again.

[Capt ka'Sharren] Gul Miran, why do I suspect you've been causing mischief?

[Gul Miran] Mischief? Me? Starfleet is the one who has been destroying Apiata foragers. Such a shame, to stoop to that to feed your decadent, soft lifestyles.

[Capt ka'Sharren] I've told you Miran, we have no need of that to support our lifestyles. Really, you should take a trip to Andoria with me some day, see what post-scarcity looks like.

[Loud buzzing noise]

[Gul Miran] That ... would ... ah, not be possible.

[Capt ka'Sharren] Shame... also a shame that we have telemetry of Cardassian ships harassing Apiata foragers, including the testimony of the crew, proving that they were attacked by your colleagues. I wonder what finger prints we'll find when we start to unravel that senor log you presented...

[Gul Miran] ... take care, Captain. Trager out.



-

Captain's Log, USS T'Kumbra, Stardate 22339.2

A distress call received one hour ago has been responded to by USS T'Kumbra. Near the Vulcan mining colony of Chelak-Kaw the USS Vokau has experienced a power failure.

After bringing her under tow and dispatching additional engineers to assist, we have the following report: a failure of the deuterium flow compounded by a stress fracture in a magnetic constrictor segment caused the matter feed to the Vokau's MARA assembly to fall too low. The anti-matter feed had to be cut off by emergency fail-safe, as it was exceeding the amount of matter reactant being fed into the reaction chamber. This excess anti-deuterium instead began to interact with the dilithium armature and the primary plasma phase manifold. If it had proceeded for even a few seconds more the core's integrity would have been compromised, destroying the ship. It appears that the TKumbra will require a replacement warp core on the preliminary assessment.

[+5pp, all Soyuz hauled into drydocks a second time, will be out for 6 months for refits]

-

Captain's Log, USS Miracht, Stardate 22339.3

I have been awoken to news that a serious disturbance has occurred on the planet. It appears that one of my officers may have violated a sacred local custom by mistake. The Sydraxians are ... not furious, and I am told violence has already begun. I am doing my best to gather my officers and crew and organise an emergency beam out.


-

Captain's Log, USS Courageous, Stardate 22339.5


Both the Trager and the large sensor contact disappeared shortly before we finished cracking the sensor log's encoding to prove the Cardassians had faked the log. Using long-range comm, Gul Miran of the Trager managed some very quick talking and chalked up the ruse to wishing the very best for the Apiata, to save them from making a mistake with the Federation. However, they protested that they did not destroy the foragers, but rather simply took the opportunity.

I don't think anyone in a Starfleet uniform believes them, but the Apiata are accepting it for now.

[Cardassian Relations with Apiata -25, +10rp]

-

Personal Log, Maryam Ajam, Stardate 22339.6

Watching that Queen on the Enterprise torment Nash, I don't know how I stopped from laughing while I was aboard, but the moment I got back to the Courageous I nearly did myself harm from laughing. Leaniss agrees with me the Captain had a woman like her coming.

-

Captain's Log, USS Cheron, Stardate 22339.7

After the arrival of the rest of the Cardassian Border Zone fleet, including Commodore Uhura on the Kumari, the Jaldun harassing the Indorians has bugged out. Not, however, before giving the Challorn a very close fly-by and intensive scan. Captain Mbeki ordered weapons targeting on the ship as it went by and for a moment it seemed that it would break out into combat after all, but the Jaldun continued on and then left the system.

[+25 Relations with Indorians]
[Cardassians -5 Relations with Indorians]
[+1 Militarisation Point]

-

Captain's Log, USS Sarek, Stardate 22339.9

It appears that we have located a population of Vertorium Nesters, rare deep-space organisms that are drawn to subtle radiation bands emitted by some ores. These have led us to a number of ore deposits in the asteroid belts of Beta Corridan 31. I believe that there is considerable opportunity for further exploitation of this resource.

[+15br, +15sr, new BR/SR mining Colony available, +10br/+10sr per year]

I must say, deep space has proven to be very helpful with my meditation.

-

First Officer's Log, USS Miracht, Stardate 22340.0

Captain Thuir has been gravely injured. A phaser blast very nearly killed him. If we'd gotten him to sickbay even a minute later...

Despit that, many crew members are dead. I have organised the recovery of wounded and bodies as best I can, and at most recent count, all crew are accounted for. Sydraxian ships harried us as we escaped the system, and our shields collapsed. I have set a maximum warp course to Leas Akaam to begin organising repairs.

We still are unclear as to exactly what local custom we broke. I do not know for sure if we will ever know, but the Sydraxians are apparently nearly as angry we deprived them of the "trophy" of the offending party as with the original offence itself.

[2 Hp damage, 1 Officer, 1 Enlisted Killed, will be towed back to shipyard, -100 Relations with Sydraxians]

-

Personal Log, Nash ka'Sharren, Stardate 22341.2

Leaniss is now telling me I deserved to run into a girl like Izzidiera.


The nerve of her! However, Izzidiera has apparently spoken very well of us behind doors to the High Council again upon our return to Apinae, and the Dorsata Queens as well sent on a glowing report. It seems that in competition between us and the Cardassians, Starfleet is the more attractive option.

I like to think it's because we both have antenna.

[Starting Relations 100 - Apiata join as Affiliates, +10 pp]

-


Starfleet Commander's Log, Stardate 22348.4

Let the record show that Captain Michel Thuir has been officially reprimanded over the catastrophic diplomatic failure with the Sydraxian Hierarchy. As the commanding officer on the scene, he is considered responsible for the actions of his crew.

A Board of Inquiry will be established to investigate the matter during the six-month drydock stint of the USS Miracht.

-

Director Sirvk, 40 Eridani A Shipyards, Stardate 22353.7

Assessment of the USS Vokau has led to further assessments of the remaining Soyuz-class vessels. We estimate that all four will require replacement warp cores within the next five years. The future of these escorts is now the matter of considerable debate, most of it intensely negative. This is the second serious breakdown of a Soyuz-class vessel in recent times, and it is the opinion of many in this department that they are becoming liabilities. There should be another ten years on their current refit cycle, but it remains doubtful the hulls will last to that point.

[Next Shipyard Operations phase will include a formal recommendation by Shipyard Operations and Starfleet Engineering Command to scrap all remaining Soyuz-class escorts]

-
 
0/4 Cardassians :D

And the Apiata start off as affiliates! Very nice :)

The Soyuz being in bad shape is less nice, and that huge incident with Syndraxians is even worse though.

I think that drops them to something like -40 :(
 
Last edited:
So, here's my take on the Rennie, with a scale 1.25 hull and a 2.15 saucer:



Sure, it takes 26 extra techs, but it has a sub 2% fail rate, and 3 extra power for refits. I can get similar results for less techs, but that requires reusing components-Specifically using the constellation hull, constitution saucer, and Miranda rollbar, which seems more a frankenship than a Rennie to me
 
@OneirosTheWriter, could you go into more detail on what exactly the Annual Hilarious Breakdown chance means for ships? Like how serious are they usually?
Exploding Consoles?

Also, has anyone tried making a shuttle/runabout yet?

Shuttle building is very hard. Fudge factors are not a factor :(

@OneirosTheWriter
Can the defense minimum be lowered for shuttles? Also, are we allowed to use 0.05 increments as values for shuttles? Everything gets hit with a status over scale penalty without it :(

Also, for some reason, Presence takes up 1.72 power out of 4 on my shuttle, which is why I'm having issues right now.
 
Last edited:
Back
Top