• Welcome! The TrekBBS is the number one place to chat about Star Trek with like-minded fans.
    If you are not already a member then please register an account and join in the discussion!

Starfleet Procurement Policy Draft

We should also bear in mind that the NX class was the first warp 5 ship. Maybe Starfleet could build their old slow ships more like your TNG-era approach, but with the new ships they saw that this design is too weak. So they changed their later designs to "endo skeleton with compartments" and then in TMP they reached the tech level to slowly go for the lighter "exoskeleton with hull filled with modules" again.
 
New side-bar. Warp nacelle design and field configuration.

YES! Finally a good explanation for the different shapes of Starfleet vessels and their warp nacelles. It even applies perfectly for old ships like the Excelsior.

Your text also reminded me of an idea I recently had about the Galaxy class development. There is a third ship with Galaxy-class nacelles, the Challenger. That odd nacelle over nacelle design.
I think of it as a technology testbed especially for the new warp engines. On that ship they would be tested before implemented into the Nebula and Galaxy classes.
 
That's the alternate timeline. NX-01 already had some form of structural integrity fields back in the 22nd century; different technical progression there.

Not neccessarily, there are things which speak for it being the alternate timeline (I suppose you mean the Abramsverse) and things speaking against that, like the last episode of Enterprise. If things are as muddled as Enterprise, I think it's a matter of opinion. Since I don't like NuTrek, but I like Enterprise (at least in part) I want it to be part of the prime timeline, so I'm searching for ways to reconcile that series with it.
 
Yeah, the Challenger makes sense as a testbed. Though the name doesn't make a lot of sense unless NCC-71099 (named presumably in honor of OV-99) was commissioned after the testbed Challenger was prematurely decommissioned. (perhaps an accident?)
 
Challenger, as in "challenge every warp engine build to this point".

As for the accident, yeah, maybe even a TMP-style wormhole effect.
 
Yeah. Enterprise, Challenger, Endeavor, Venture ... all good names for something new and bold.
 
That's the alternate timeline. NX-01 already had some form of structural integrity fields back in the 22nd century; different technical progression there.

Not neccessarily, there are things which speak for it being the alternate timeline (I suppose you mean the Abramsverse) and things speaking against that, like the last episode of Enterprise.
Let me get this straight: you liked "These are the Voyages" but you DIDN'T like the last two Star Trek movies?:wtf:

If things are as muddled as Enterprise, I think it's a matter of opinion.
It's ALWAYS a matter of opinion, but we know for a fact that Enterprise is part of the Abrams timeline even if we do not for certain know this of the TOS timeline. Otherwise, it's just one more thing that cannot really BE reconciled between Enterprise and the rest of trek canon.
 
I don't think he said he liked TATV, just that he liked Enterprise but not Abramsflicks.

Also tie-in material at least tells us ENT is part of the Trek Timeline writ large, so I don't think it's a useful divergence point.
 
Let me get this straight: you liked "These are the Voyages" but you DIDN'T like the last two Star Trek movies?:wtf:

I knew I shouldn't have deleted the "(awful)" in front of "last episode of Enterprise". :lol:

No really, what I meant is that it's just a (rather strong) bit of canonical information supporting the stance of that series being part of the prime timeline. It was an example.
 
I don't actually recall a SIF being mentioned in ENT. What I do remember is Trip and Reed talking about making the ship's structural integrity (no field) bear the brunt of the phase cannon recoil. Poking around at Memory Alpha, there's also mention of NX-01 suffering all sorts of nasty stress microfractures during her mission in the Delphic Expanse and that they needed hull polarization to overcome it.

So there's definitely not an SIF in the way we know it in the 24th century going on in ENT.
 
I think of it as a technology testbed especially for the new warp engines. On that ship they would be tested before implemented into the Nebula and Galaxy classes.

Do wish the Pegasus had used one of the Wolf 359 models instead of an Oberth.
 
I really like and agree with what the latest sidebar has to offer on warp nacelles and warp field. I am a bit surprised you didn't discuss the concept of "subspace drag" at all, though, which seems to be responsible for a lot of the "streamlining" seen on starships.

Regarding SIF in the ENT era, I could see polarized hull plating somehow being a predecessor to the modern SIF, and I would also find it likely that the ENT era were probably assembled as one big pressure compartment, with areas like the catamarans that didn't need to be pressurized, not being pressurized at all.
 
Well "subspace drag" I think is going to come on the "hull design" side-bar, rather than the nacelle one. Also I think the longer nacelles and the "longer" hull geometry in the Excelsior also involves transwarp in that, perhaps Starfleet designers, finally having found out about peak transition thresholds, were then convinced that their transwarp project could let them cross additional thresholds with a really elongated warp nacelle design that would project the needed field.

Just food for thought.
 
Another side bar, this time on tactical systems.

Just as speculative as other sections, I'm sure I'll have plenty of disagreement on this one.

Arrayed for Success: The Evolution of Tactical Systems
A starship's mission payload will commonly included a wide variety of devices classified as tactical systems. Ranging from graviton based deflector shields to particle beam weaponry, these systems often have applications outside of combat. Starfleet energy weapons have often been used in secondary functions as scientific instruments, while projectile launchers have a wide set of applications in deploying automated sensor platforms. Consequently, Starfleet designers are encouraged to provide a minimal level of tactical capability to all starships.

At its foundation Starfleet had an eclectic mix of particle and EM based weaponry at its disposal. These ranged from UESF's phased plasma weapons ("Phase Weapons"), Centauran high-energy microwave lasers, Vulcan and Andorian teytron based particle cannons, and Tellarite verteron based heavy particle cannon. Eventually a hybrid weapon was developed on New Montana's Sloane High Energy Physics Institute that combined high-intensity EM pulses with energy phasing techniques from particle cannons. Although it behaved substantially differently from traditional laser weaponry, Starfleet adopted the nomenclature of lasers to this technology and utilized it as its primary shipboard armament until the 2240s.

Energetic particles named nadions were discovered in the 2220s. Experiments conducted at the Supraluminal Linear Collider in the 2230s confirmed that phased nadion particles created an efficient energy transfer effect. Weapons applications of this "rapid nadion effect" were rapidly developed in the 2240s. The resultant phaser has remained the baseline Federation weapon technology despite substantial advancements in the intervening century and a half.

Phasers come in three principle types when utilized aboard starships. The most basic design involves a self-contained emplacement consisting of a high-capacity sarium krellide power cell, target acquisition sensors, and omni-directional phaser emitter assembly. These emplacements are then connected to the ship's primary EPS conduits that are used to feed the power cell. These emplacements are capable of firing variable intensity beams using energy stored in their power cells. Typical starship mountings involve paired emitters sharing an enlarged power cell, cooling equipment, and enhanced targeting sensors.

Modern starships utilize a substantially improved phaser design simply referred to as "arrays". Arrays consist of large connected segments of multiple phaser emitter assemblies linked to provide wide angles of fire. A single array can range from between a few score to several hundred emitter segments. Each emitter segment consists of an energy-storage prefire chamber and a discharge emitter facet. EPS conduits feed the entirety of the array, allowing all of the prefire chambers in a given array to convert plasma to rapid nadions. These prefer chambers then use an annular confinement beam to condense the nadions into a single beam released through a limited number of emitter facets. The resultant is a beam with greater destructive potential and shield penetration characteristics.

In theory longer phaser arrays feature greater power, but array segments also present a vulnerability. Compared to standard duranium/tritanium hull or even transparent duranium windows, the LiCu 518 emitter facets lack structural strength. Further, due to the effects of subspace forcefield effects on beam coherence, emitter arrays do not feature SIF-emitter integration like other parts of the hull. Finally, a phaser array can present a tempting target for threat forces, as the array's contour also corresponds to a ship's major EPS conduit network.

Despite the advantages of larger arrays, a phaser array that covers too much of a starship's surface area represents a significant vulnerability for the ship in question. Unless a starship's structural frame is specifically designed for a large emitter array, most phaser arrays consist of sub-hull segments consisting only of prefire chambers that are channeled into emitter facets with limited exposure on the outer hull. On older starship designs like Miranda or Excelsior most of these exposed emitter elements are placed in locations that once housed phaser emplacements, giving the illusion of starships continuing to use old-style ball emitters.

Greater array surface area remains a powerful advantage for modern starships. Having a greater number of emitter facets allows more flexible fire angles, faster rate of fire, and substantially improved thermal dissipation. While the total number of prefire chambers are roughly equal between a mid-2360s Excelsior (Repulse configuration, 2358) and Intrepid, the substantially greater surface area of an Intrepid main phaser arrays allows for roughly twice the fire rate and three times the thermal endurance. This reality has increased calls to either retire hull designs not optimized for surface array segments or to find practical solutions to refit more surface segments to existing designs.

The final standard variation of phasers are pulse phaser cannons, first deployed on the Defiant-class starship. Pulse phasers require larger prefire chambers than standard starship phasers plus an additional rotary drum consisting of six high density sarium krellide power cells. The combined output allows a single relatively compact 35m long phaser cannon to match the destructive yield of a full power Excelsior-class primary phaser array. Flawless microgravity grown emitter crystals and beam focusing coils layer this energy into a multi-layered pulse. The resultant bolt provides substantially greater shield penetration characteristics than even narrow-band beam blasts.

The system's complexity and fixed emitter requirement makes it a narrow arc weapon. As a result current anti-starship models of pulse phasers are limited in application to a handful of ship designs with optimized hull geometry such as Defiant, Achilles and Vesta-class starships. Substantially smaller models are used as point defense weapons aboard larger starships or tactical fighters, taking advantage of their shield penetration characteristics to shoot down shielded torpedo weapons.

Additional types of nadion-based weaponry are theoretically available for Starfleet use. These include compressed nadion beam cannon (colloiquially known as "phaser lances"), nadion pulse cannon, and photon cannon. All of these technologies remain far too cumbersome for starship use, and only a handful are used for defense of fixed installations and planetary facilities.

Projectile weapon launchers provide substantial flexibility to Starfleet ships. Variable yield warhead packages and precise control software allow torpedo weaponry to be used in everything from combat to seismic engineering projects. A typical starship's torpedo stocks contain at least half a dozen warhead configurations along with various automated scientific probes.

Starfleet torpedo launchers are based on a combination of subspace field coils and a compressed gas acceleration system. Although modern superconductors allow for extremely efficient linear acceleration utilizing magnetic fields, the fact that most antimatter based weaponry utilizes magnetic containment for their payloads precludes their use for torpedo launching. The sacrifice in comparative efficiency and the greater mass of subspace field coils is considered an acceptable trade-off when weighed against the destructive power and flexibility of antimatter munitions.

Torpedo launchers range in size from short-barrel external mount torpedo launchers in Danube-class runabouts to the 12-torpedo capacity Mk.95 burst fire launchers found on Sovereign-class starships. Casing width is standardized across the range of Starfleet torpedo types at 76cm. Other dimensions can be altered to change a torpedo's payload and guidance characteristics, ranging from the standard 25 isoton Mk.IX Photon Torpedo of 210cm x 45cm to the 100 isoton Mk.VI Heavy Torpedo at 350cm x 70cm.

The term "torpedo" has come to be used for warp capable guided smart munitions utilizing sustainer engines. In Starfleet nomenclature a "Missile" refers to a self-accelerating guided warhead equipped with a more robust propulsion system. Missiles tend to be used on craft too small even for microtorpedo launchers, often carried on external hardpoints. "Rocket" is used to describe any warhead that does not have active guidance systems, while anything that does not fit the three previous descriptions is called a "device".

All current Starfleet projectile weapons are equipped with a graviton based penetration shield. These shields are responsible for the characteristic "glow" of a standard torpedo weapon and allow projectiles to survive glancing hits from energy weapon based defenses. Further, these shields serve as a penetrator against deflector shield systems and increase the possibility that a torpedo will detonate inside a threat vessel's shield perimeter.

Found primarily on runabouts, tactical fighters, and point defense systems for fixed installations, microtorpedo launchers are more akin to rapid fire shell guns than anti-shipping torpedoes. Firing quantum, kinetic, or antimatter warheads contained in a 13cm x 3cm x 3cm casing, these weapons are capable of rapid-fire, semi-guided attacks on larger targets. Despite their dimunitive size and limited ammunition capacity, these weapons can provide a sub-1000m³ vessel with hitting power similar to large, high-energy beam weapons at a fraction of the size.

Phaser Types:
  • Type I - Concealed Handheld Weapon. Full energy discharge regarded as baseline output of all phasers. Discharge Rating: 1
  • Type II - Handheld Sidearm Weapon. Discharge Rating: 20.5
  • Type III - Two-handed Rifle Weapon. Available as beam, compression, and multi-configuration models. Discharge Rating: 30.75
  • Type IV - Fire Support/Light Anti-Vehicle Weapon. Discharge Rating: 120
  • Type V - Standard Anti-Vehicle Weapon. Discharge Rating: 350
  • Type VI - Heavy Anti-Vehicle/Starship Point-Defense Weapon. Discharge Rating: 700
  • Type VII - Light Anti-Starship Weapon. Discharge Rating: 2,000
  • Type VIII - Standard Anti-Starship Weapon. 4,500
  • Type IX - Heavy Anti-Starship Weapon. 7,500
  • Type X - Enhanced Range Anti-Starship Weapon. Discharge Rating: 10,000
  • Type XI - Planetary Defense Weapon. Discharge Rating: 15,000
  • Type XII - Heavy Planetary Defense Weapon. Discharge Rating: 20,000

Projectile Weapon Classifications:
  • Class I - Handheld support weapon. e.g. Photon Grenade
  • Class II - Anti-vehicle/fire support weapon. e.g. Photon Mortar
  • Class III - Light Anti-Starship Weapon. e.g. Microtorpedo
  • Class IV - Standard Anti-Starship Weapon. e.g. Mk.IX Photon Torpedo, Mk-IQ Quantum Torpedo.
  • Class V - Heavy Anti-Starship Weapon. e.g. Mk. VI High-yield Photon Torpedo, Mk-IIQ Quantum Torpedo.
  • Class VI - Heavy Planetary Defense Weapon. e.g. Sol Perimeter Defense Drone Warheads, Tricobalt Device.
 
Last edited:
Next full chapter. 2370 - 2381...
The Fight for Survival: 2370 - 2381
Despite coming to power as a herald of peace, Jaresh-Inyo's presidency was filled with rapidly building crises. The McAllistair Nebula Crisis of 2369 threatened to plunge the Federation back into full scale war with the Cardassian Union, undoing Amitra's hard-won armistice. A Starfleet task force led by Edward Jellico successfully forced the Cardassians to back down, but revealed the fragility of the Federation's new found peace. Other events during Jaresh-Inyo's first year in office included an incursion by Borg infected by individuality, the end of Cardassian occupation of the Bajor Sector, the discovery of the Bajoran Wormhole, and a diplomatic crisis with the Romulan Star Empire after the defection of Vice Proconsul M'Ret.

The following year, the final Federation-Cardassian Treaty led to widespread dissatisfaction and unrest in the newly established Demilitarized Zone. Groups of Starfleet officers abandoned their posts and even absconded with Starfleet hardware to assist the armed resistance group known as the Maquis. Assymetric warfare between the Maquis and Cardassian regular forces prevented Starfleet from demobilizing its forces along the Demilitarized Zone, negating the "peace dividend" expected when peace with the Cardassian Union was negotiated by the Amitra Administration.

Tensions in the Beta Quadrant direction also remained high. The diplomatic tensions created by the defection of M'Ret were exacerbated when illegal Starfleet research into phase cloaking technology was revealed in 2370. This major breach of the Treaty of Algeron nearly brought the Federation back into conflict with the Romulan Star Empire. Vice Admiral Erik Pressman refused to divulge the identities of his co-conspirators, requiring an extensive investigation of Starfleet's upper echelons by a combined Starfleet Internal Affairs and Federation Security task group. The final results of this investigation resulted in several high level resignations at Starfleet Command and Starfleet R&D, requiring substantial personnel redeployments and setbacks to existing research projects.

The ambitious 2365 Decennial Plan, expected to produce a new generation of anti-Borg optimized starship designs was hopelessly behind schedule by 2370. Admiral Batelle Toh was reassigned from ASDB to heading Starfleet R&D after the Pegasus Purges, resulting in substantial delays in ASDB development projects. Of the major projects initiated under the Shanthi Admiralty, only the Intrepid and Nova class development projects remained on schedule.

Disastrous first contact with the Dominion in 2370 resulted in the loss of USS Odyssey (NCC-71832). Further revelations in the following year led to a substantially elevated perception of danger within Starfleet's upper echelons. Despite this, the Jaresh-Inyo Administration remained steadfast in refusing calls for increased mobilization. Only the loss of Enterprise (NCC-1701-D) allowed Admiral Ruah Brackett to convince the Federation Council to activate the 6 reserve Galaxy class hulls. Authorization for series production of additional Galaxy-class hulls were denied by presidential veto in 2371, however, and Starfleet Command contented itself with procuring additional Nebula-class starships and series production of the brand new Intrepid-class light explorer.

Further conflict came in 2372 when the Klingon Empire invaded the Cardassian Union. The Federation's condemnation of the attack resulted in an abrogation of the Khitomer Accords and a series of border conflicts between the two Great Powers. Directed by a changeling who had replaced General Martok of the KDF, the brief conflict resulted in several high profile losses of isolated Starfleet vessels along the Klingon-Federation border. Already under fire for a lack of preparation in the Cardassian Demilitarized Zone, the Jaresh-Inyo Administration responded by sending Starfleet's remaining core sector fleets to the Beta Quadrant Frontier.

The combination of the Pegasus Purges, the Jaresh-Inyo Administration's production drawdown, and the revelation of the Dominion Threat allowed a small cabal of Starfleet flag officers led by Vice Admiral James Leyton to make secret preparations for a coup d'etat. Rear Admiral Galaen sh'Kelthris took advantage of his posting as chief of staff of the Starfleet Procurement Office to conduct several covert modernization projects of older starship hulls in smaller idled civilian dockyards, while the Vice Commandant of Starfleet Academy siphoned cadet squadrons off for coup preparations. As Chief of Starfleet Operations, Leyton was able to reposition most of Starfleet's assets not involved in his conspiracy outside of the Sol System. With the escalation of the conflict along the Klingon border, Leyton put his planned coup into effect. While the coup attempt was foiled by loyalist Starfleet officers, this final blow to Jaresh-Inyo's credibility effectively ended his chances at reelection.

Elected by a landslide in 2372, President Min Zife initiated a crash escalation program for Starfleet in early 2373. Taela Shanthi once again took the post of Commander in Chief, Federation Starfleet. Revelations that General Martok had been replaced by a changeling infiltrator allowed for rapid rapproachment between the Federation and Klingon Empire. The deescalation of hostilities along the Federation-Klingon border allowed redeployment of forces back to the Federation core worlds. This proved fortuitous when the Borg Collective once again invaded the Alpha Quadrant in 2373.

Unlike the Battle of Wolf 359, the Typhon Sector Task Force led by Vice Admiral Jeremiah Hayes consisted entirely of modernized, fully combat capable starships. Although Starfleet combat losses remained high with 30% of the 120 ship task force either lost or disabled, personnel losses were comparatively much lighter, allowing Starfleet to rapidly remobilize its forces by transferring personnel to newly built starships.

Under the Second Shanthi Admiralty, Starfleet emphasized procurement and modernization of proven starship designs in civilian shipyards, while using Starfleet Shipyards for repairs and construction of experimental ship types. The 2373 Procurement Memo authorized Admiral Theoderich Patterson, Chief of Fleet Yard Operations, to take "all necessary and proper measures" to prepare Starfleet for a potential war with the Dominion or Borg Collective. The Shanthi Admiralty gave Patterson the needed latitude to set production goals, while setting personnel training goals that were ambitious even by the metrics of the 2365 Decennial Plan.

Despite these preparations the start of the Dominion War in 2373 would extensively tax Starfleet resources. Pre-war estimates of both Dominion and Cardassian fleet strength proved to be wildly optimistic. Starfleet's technological edge was substantially smaller than in the Cardassian Wars of the previous decade, and the Dominion Expeditionary Force proved to be nearly equal in total strength as the Klingon Defense Force. Ship losses from early engagements numbered in the hundreds, taxing even the Federation's vast civilian ship building infrastructure's ability to replace war losses. In the year 2374 alone Starfleet lost nearly 1,500 starships (not including non-combatants such as tankers, transports, and tenders) while only managing to produce 437 new starships and repairing or refitting 600 others.

Additional pressures included high personnel losses. By mid-2374, Starfleet Operations issued directives to reduce crew complements by nearly 10% across the board. A further directive in early 2375 reduced crew complements to 80% of pre-war numbers to free up sufficient numbers to crew newly built replacements. Compared to past conflicts where loss rates were in the 10-15% range, the average destroyed starship lost 30% of its complement during the Dominion War. Accelerated officer training programs and 6-month rapid mobilization courses for enlisted crew somewhat alleviated these losses, but the major bottleneck for Starfleet mobilization during this period remained primarily personnel based.

The end of the Dominion War in 2375 resulted in the retirement of Taela Shanthi. Admiral Tujiro Nakamura succeeded Shanthi, while Chief of Starfleet Operations was filled by William Ross. The Nakamura Admiralty initiated the first post-war Decennial Plan in 2376 which sought to restore Starfleet to its pre-war strength. Resource demands required to rebuild Federation member worlds occupied during the war slowed down progress during this period. The new building programs emphasized a diverse mix of next generation starships, including the Luna, Merian, and Vesta class development projects.

Edward Jellico became commander in chief when Nakamura retired in 2380. Starfleet's strength remained about 15% below its pre-Dominion War peak at this time when it faced an unprecedented existential crisis. The final Borg Invasion of 2381 resulted in the loss of nearly 40% of Starfleet's fleet strength. Over 95% of the crew complements died aboard the lost ships, creating a crippling personnel shortage just when the Federation most needed Starfleet crews to deal with mounting humanitarian crises.
 
I appreciate your warp nacelle design past tremendously. It very much feels like a genuine engineering introductory text. Very impressive. I see no logical inconsistencies. And I'll be using it as an assumption base from now on. I hope you don't mind.

I'll have to re-read the weapons post to fully understand it. I admit to not paying much attention to the weapons systems in the past.

And the historical overview is a nice touch. Very nice.

Very nice all around. :techman:
 
Another side bar: Starfleet ship production capabilities and methods.

Starfleet Ship Production Capabilities
The scale of Starfleet operations requires a staggering amount of infrastructure. 75% of Starfleet's personnel requirements come from operating the vast network of starbases, outposts, fleet yards, and planetary facilities. Despite the staggering requirements, this percentage understates the Starfleet personnel dedicated to support functions. Another 10% of all personnel are employed aboard auxiliary starships serving numerous infrastructure needs ranging from fuel tankers, supply transports, and maintenance tenders to the more specialized operations of the SCE. For every crew member serving on a frontline starship, there are ten others working behind the scenes to make that deployment possible.

Filling Starfleet's vast starship production needs entirely with fleet operated facilities would require an unreasonable number of yard personnel. Starfleet demand for ship building and repair are dynamic rather than fixed, from as low as a few score per year to the thousands required during the Dominion War or after the Borg Invasion of 2381. Starfleet has taken a policy of ordering most of its basic hulls and drive systems from civilian dockyards and fitting ships with sensitive technology at fleet yards, spacedocks or starbase facilities.

Fleet Yard Operations divides starship drydock facilities into five classifications depending on the maximum volume of starships supported in each facility. These range from CLass I facilities capable of building ships of up to 10 million m³ to Class V facilities with a maximum capacity of 250,000 m³. Smaller yards exist within the Federation's outer periphery, but Starfleet itself does not operate or contract smaller yards for its own production. Vessels substantially smaller than 50,000 m³ in Starfleet service are generally mass produced in enclosed planetary or starbase production facilities. Starfleet itself no longer operates dockyards of Class V size and is in the process of transfering its Class IV facilities to civilian control.

Major civilian yards in Federation space include Federation Space Systems, Salazaar Shipyards, Chiokis Starship Construction and Yoyodyne Systems Engineering. Most of these yards are designed for a mix of civilian and Starfleet orders with a heavy emphasis on Class III dockyard facilities of 1.5 million m³. Smaller yards often contain a large number of Class IV or Class V facilities acquired from surplus auctions. A handful of civilian yards have Class II facilities, typically occupied by either Starfleet orders or components for orbital habitat construction.

Starfleet operates a number of large orbital fleet yards, with most of the major production focused in the Sol, Proxima, and Tellar systems. A number of Class III facilities are located outside of major population centers, but logistical requirements of fitting out preclude decentralization of Starfleet yard facilities. The largest Starfleet Yard remains Utopia Planitia Fleet Yards in Mars orbit, responsible for construction of Starfleet's largest and most advanced ship classes.

Drydock facilities assemble starship trussed frame components and external stress hulls using a combination of gamma welding and phase-transition bonding. Industrial replicators and fabricators are combined to produce structural components, while the dock enclosures are used to produce microtransporter effects necessary for phase-transition bonding. High mass components constructed of unreplicable materials like warp coils are also installed in this process, along with a temporary bridge module, basic sub-light drive coils, and a single structural integrity field generator.

Once the basic spaceframe is completed the ship is moved to a fitting out facility. These range from integrated facilities like the Class I Dockyards available at Utopia Planitia to pressurized microgravity docking bays at major starbases. A combination of high-fidelity transporters and engineering crews are used to install internal systems modules ranging from habitation units, life support systems, weapons, sensor palettes, and reactors. Fitting out can take anywhere from weeks to several months depending on ship class, payload configuration, and mission requirements..

Minor refits to a starship are conducted in similar facilities. Modular components are removed with industrial transporters or work pods, and specialist teams are called to assist in integrating new technology to the starship. Most fitting out facilities are capable of conducting limited structural repairs such as replacing exterior hull segments.

Major starship repair and refit operations require the use of full scale drydock facilities. Interior sections of a ship undergoing refit are stripped out at a fitting yard before the ship itself is towed to drydock. A combination of micro-scale transporters and work bee mounted gamma welders are used to repair structural frame components and vital systems. Major reconfigurations of external hull and replacement of warp nacelle components are also conducted during such refits. A careful quantum level survey of all ship hull components are also conducted prior to certifying the ship fit for duty.

Starfleet prefers to use their own fleet yard facilities for repairs and refits. The quantum surveys conducted during repairs and refits often reveal additional work requiring specialized expertise. Civilian yard engineers lack the experience needed to repair partially damaged spaceframes or even to spot quantum level damage structural components. As a result, they often underestimate the time and resources required to bring a starship back online. In addition, most civilian dockyards operate on a much tighter schedule for yard occupancy. A delay of as little as a week can disrupt the shipyard's operations and significantly increase the cost to Starfleet.

Starfleet starship manufacturing standards require higher resolution industrial replicators and tight tolerance fabricators than most civilian applications. Once configured for a particular ship type, replicators and fabricators can take a substantial time and resource investment to reconfigure to new designs. Most civilian yard operators will refuse contracts from Starfleet if they require frequent reconfiguration of their facilities. Many smaller operators still use older Starfleet equipment optimized for the production of Miranda or Excelsior class hull components. These yards continue to produce derivatives of older designs with updated technology. Despite the best efforts of Yard Operations Command to phase out production of these designs, the need to keep these yards in business often forces Starfleet to continue production of older hull frames.

Modern Starfleet Fleet Yard replicators and fabricators are designed with substantially greater flexibility. An integrated Class I production facility can switch rapidly between ship types and are therefore used for production of a greater variety of hull configurations and ship designs. For example, yard 37 at Utopia Planitia completed the Sovereign-class USS Gibraltar (NCC-75689) and Defiant-class USS Pactolus (NCC-76722) in 2375 without major retooling.

With the massive damage done to Federation infrastructure during the Borg Invasion of 2381, the Federation Council has requested that Starfleet Fleet Yard Operations assist in the establishing of new civilian yard facilities to support rebuilding efforts. Orders to civilian yards have decreased to free up capacity for civilian demand. Starfleet yards have also donated many of their older fabrication facilities to civilian agencies for reconstruction assistance. The donations aren't entirely driven by altruism, allowing Starfleet to increase its number of better equipped Class I facilities.

Current Starfleet Yards:
  • Sol System
    • San Francisco Fleet Yards
    • Earth Station McKinley
    • Utopia Planitia Fleet Yards
    • Tranquility Base, Luna
  • Proxima/Alpha Centauri
    • Proxima Construction Yards
    • Kentaurus Fleet Yards
    • New Montana Experimental Yards
  • Other
    • Antares Ship Yards
    • Beta Antares Fleet yards

Notable Civilian Yard Contractors:
  • Yoyodyne Systems Engineering
    • Copernicus Shipyards
    • 40 Eridani A
  • Federation Space Systems
    • Qualor II Ship Assembly Yards
    • Marin County Yard
  • Salazaar Ship Company
    • Gavor Ships Systems
    • Centauri Spaceworks
  • Chiokis Starship Construction
    • Phinda Shipyards
    • Procyon Imperial Fleet Yards
  • Other Yards
    • Okona Shipyards
    • Baikonur Cosmodome
 
Last edited:
If you are not already a member then please register an account and join in the discussion!

Sign up / Register


Back
Top