U.S.S. Ain Jalut
USS Ain Jalut | |
---|---|
Class: Registry: Owner: Operator: Status: |
Sovereign Class NCC-74012 United Federation of Planets Starfleet Active |
History
The USS Ain Jalut was one of a small number of Sovereign-class shipped ordered by Starfleet prior to the Dominion War. The ship’s story begins in 2375 shortly after the Breen launched their attack on the Federation after allying with the Dominion. As part of the shock and panic that resulted from this the Ain Jalut’s construction was rushed to completion and the ship was pressed into service well before it would ordinarily have been permitted. The Engineering team described the ship’s construction as ‘slipshod, with an equal chance of being destroyed by going to warp as by enemy fire’. Despite this adversity the engineering team managed to keep the ship not just serviceable but combat effective throughout the rest of the conflict.
As the war concluded the Ain Jalut was ordered back to drydock in early 2376 for a massive overhaul or, as the Chief Engineer of the time put it, to “finish construction”. The ship would return to active duty in 2378 with most of its original engineering crew specifically requesting reassignment to the vessel. Despite these overhauls, the legacy of the Ain Jalut’s rushed construction would continue to plague its screw. While being posted to trouble spots throughout the 2180s, it would be forced to return to starbase once every two years owing to a technical malfunction - despite this the engineering staff reported high job satisfaction. For most of them, working on the ship and getting it perfect despite its sloppy start was a “project”. However, as a ship of the line, command viewed this unreliability as simply unacceptable and it was mothballed in 2187.
In 2190, the ship was scheduled for demolition, its parts to be stripped and either put into other vessels or stored for other ships of the class. When word of this spread amongst the fleet, former crew of the Ain Jalut organized a petition for the ship to be reinstated, all stating that despite its many technical faults the ship had “character” and insisted that with the right team it would be as good if not better than any other Sovereign-class vessel in service. Eventually, a former Chief Engineer who had recently made Captain threw down the gauntlet and promised that he would take command of the ship and see it brought up to full service standards within the span of one year. With the chance to preserve what was still an expensive investment, a clear deadline established, and the willingness of a surprising number of officers to gamble their reputations and careers on this command bent and gave them the chance.
Over the next year the Ain Jalut was given its most extensive overhaul and refit, and underwent the most rigorous technical inspection any Starfleet vessel could go through. It passed with flying colors much to the adulation of its new crew, who then set off with a vessel that they felt truly belonged to them. Wanting to preserve the memory of what they went through to preserve the ship, the engineering team etched their names into bulkheads and panels near or covering systems that they worked on. This started a tradition where an engineer responsible for a rebuild of a major system or component would etch their name into a nearby bulkhead with a date - future engineers who rebuilt that same system would simply add their name down below with a later date. This not only personalized the regular maintenance work of the ship, but also acted as a hard copy record of who last did a major overhaul or rebuild of a critical system. The practice was permitted by later Captains, though more than one former engineer has received a late night comm call years after reassignment asking exactly what they did.
The ship would find itself assigned to numerous conflicts over the years of service being noted by commanders for its reliability and seemingly preternatural ability to endure enemy fire. It began to attract engineers in particular who wanted a ‘challenge’ for their next or even their first posting. Its storied history giving engineering teams that extra motivation to do right by the ship and ensure its legacy would continue on for generations to come. As the 25th century proved to be a time of near constant warfare for Starfleet, the Ain Jalut would find its reliability tested, becoming a major warhorse for the fleet that somehow survived its numerous engagements - often owing to a system holding out just long enough for the ship to reach safety before falling apart.
This lucky streak ended with the Terran invasion in 2422 where it was struck by an energy torpedo launched by the entity that would later be known as C’qer. Like other digitized vessels the ship would be restored as it was - the names lining Jeffries tubes and maintenance hatches fully intact. It would return to spacedock in 2423 for a major rebuild intended to upgrade ship systems to bring them in line with Federation standard. The various ‘signed’ bulkheads and plates mysteriously vanished before the crews of Utopia-Planetia could start work, not appearing again until the ship’s return to active service and assignment to the 38th fleet.
Technical Data
Physical Arrangement & Crew Support
Specifications | |
---|---|
Length: Beam: Draft: Mass: |
685.3 m 250.6 m 88.2 m 3,205,000 mt |
Decks: Crew: Capacity.: |
29 855 6500 - 9800 |
Avg. Cruise: Max Cruise: Maximum Speed: |
Warp 6 Warp 8 Warp 9.95 (for 12 hours) |
Armaments: |
16x Type-XII Phaser Arrays 6x Forward Torpedo Tubes 4x Aft Torpedo Tubes |
Defenses: |
Regenerative Shielding Ablative Hull Armor |
Auxiliary Craft: |
4x Shuttlecraft 4x Attack Fighters 8x Shuttlepods 4x CMU Workbees 1x Integrated Yacht |
The USS Ain Jalut is a modified variation of the standard Sovereign-class vessel intended to act primarily as a combat vessel but recent refits have brought its scientific and exploration capabilities back in line with Sovereign-class spec while maintaining its tactical upgrades. Overall the ship boasts a grand total of 29 decks including various smaller and underutilized decks. As is standard for Starfleet ship designs it boasts a saucer section and an engineering section that also mounts the two warp nacelles. Standard crew complement is 850 personnel, with a rated evacuation capacity of 6500. It could in theory carry up to 9800 individuals in cramped conditions though this would tax the life support system and is not recommended beyond the most dire of emergencies.
Command and Control Systems
The primary control hub for the Ain Jalut is the bridge providing multiple information displays. Three chairs dominate the central area of the main bridge allowing for the Captain and two officers to occupy them at any time. Typically this would be the first officer and a high-ranking guest or other official, though it could be occupied by any number of officers based on need. Other consoles handle tactical, operations, engineering, security, the sciences, and more. Each console could be reconfigured for a different function based on the needs of the moment.
In addition to standard officer’s quarters, deck 2 houses an additional Combat Information Center. In addition to numerous sensor and communication displays this room contains added holographic imaging systems and communications stations and is designed to act as an Admiral’s command center. This allows an Admiral to focus on the business of commanding fleet actions without looking over the shoulder of their flag captain at all times. Hardline communications systems ensure continual communication between the CIC and bridge so long as both remain undamaged. When not acting as an admiral’s flag ship this location is used for backup communications and is usually unpowered and unoccupied.
Tactical & Defensive Systems
The Ain Jalut’s tactical systems have been greatly modified from the baseline. All of its torpedo launchers are capable of firing either photon or quantum torpedoes to allow for greater flexibility in the field and to adapt to changing logistical situations. Most notable is the fact that two of the aft torpedo tubes have been moved to be forward facing, necessitating substantial rearrangement of internal space but allowing for greater forward firepower when compared to baseline Sovereign models. The dorsal phaser arrays have been modified as well. In addition to maintaining the primary phaser bank in an oval shape covering dorsal bow, port, and starboard sections the six aft facing arrays have been shifted to just underneath the main array. This configuration greatly enhanced forward, port, and starboard firepower at the expense of aft fire. Four additional ventral arrays cover specifically the starboard and port sides of the saucer section giving the Ain Jalut potent broadsides with a grand total of five possible overlapping phaser arrays. Another array covers the ventral section of engineering perpendicular to the hull allowing for more direct firepower to targets directly beneath the ship. Additional arrays on the trailing edge of the warp nacelle pylons covers the most notable blindspot in the Sovereign’s aft firing arc.
Shield systems have been upgraded with regenerative shielding and ablative armor to bring the ship’s defenses into line with modern standards. This allows for greater ability to absorb fire - though after combat damaged armor sections have to be replaced using on-board replication systems or space dock facilities.
Another adjustment to the tactical capabilities of the Ain Jalut is the replacement of 4 of its standard shuttle craft with attack fighters. Two of these fighters have been modified to carry substantial sensor and communications packages allowing them to effectively extend the sensor and targeting range of the Ain Jalut beyond the norm. Due to limitations in directed energy weapons this primarily is used for torpedo guidance. The modified attack fighters also feature substantial jamming and stealth capabilities (though no cloaking due to federation treaty limitations), but have had most of their firepower stripped down to but a single forward phaser bank limiting their direct combat utility. The other two fighters are of standard configuration and are intended to act as escorts for the ECM fighters.
Industrial Capacity
Thanks to the prevalence of matter replicator technology the Ain Jalut has its own small scale industry allowing for a degree of self-sufficiency that would have been unheard of 200 years ago. In general, so long as the ship has reliable power the Ain Jalut can replicate any individual parts and components it might need for any ship board device and can even undertake more complex manufacturing if allowed enough time to complete the replication process.
In addition to the prevalent individual replicators found in lounges, crew quarters, and the Captain’s Ready Room the ship boasts several large scale replicators that can be used to replicate large pieces and components. These replicators are primarily used for heavier engineering components that cannot be easily replicated with the smaller scale versions - things like long tubing and wiring, warp core components, replacement consoles, and more. The ship has only four of these replicators and can manufacture anything that fits within a 3m x 3m x 3m square space. For safety reasons they cannot replicate explosives or other devices with sensitive components that must be put together in a precise way - however, the individual components can be replicated and assembled manually with the assistance similarly replicated precision tools and instruments. This means, in theory, the Ain Jalut can build its own photon or quantum torpedoes. In practice this is a very bad idea.
Finally, the Ain Jalut boasts a single vehicle replicator in the hangar bay intended for the replacement of lost small vessels. Unlike the larger scale replicators, the vehicle replicator is capable of precision replication and manufacture, but extensive prototyping is required for any new designs. As a result the vehicle replicator is limited to a few standard designs. While capable of replicating new fighters and shuttles it cannot replicate something as large as the Captain’s Yacht. In addition, the time to replication is often in the order of hours making it impractical for replacing vessels where time is a factor. The vehicle replicator also occupies sufficient space for a full shuttle - as such when the Ain Jalut has its full compliment of small craft the replication space is used as an additional bay and the replicator itself is unpowered for safety reasons.
Crew Accommodations
Standard compliment for the ship is 850 personnel including both officers and enlisted. The crew quarters are able to be easily configured to comfortably accommodate up to 4 people each. Officers and senior enlisted tend to enjoy private quarters, while Lieutenant JGs, Ensigns, Petty Officers, and Crewmen will usually be assigned to shared spaces. Unlike smaller ships however, there are no ‘living corridors’ that abandon all semblance of privacy making assignment to the Ain Jalut a luxury for those used to much smaller vessels. As standard each room has a bed with several cubic meters of storage space per bed and a small replicator with full access to the ship library - though weapons, explosives, and the like cannot be replicated from room units (attempts to do so are flagged for review by ship security).
Taking full advantage of replicator technology, officers on move in are permitted to customize room furnishings. All within the room have to agree and ship-board large scale replicators and transport systems allow for easy setup of furnishings. Old furnishings are recycled into the replication systems to minimize waste, however it is worth noting that such systems are prioritized to official functions first so it is not uncommon for people to have to live with decorations and furnishings they dislike for days or weeks after move in until the systems are freed up or until the ship is docked at Starbase.
Outside crew quarters the Ain Jalut has a full range of amenities. A spacious crew lounge with food replicators permits a common social space. This lounge had a full galley installed years ago allowing for chefs and bartenders to prepare specific meals using ingredients replicated, found on away missions (and cleared by medical), or simply brought from home. Whether or not an actual full time chef and/or bartender is assigned varies from captain to captain - under its current commander the Ain Jalut does not employ a full time chef or bartender but crew are permitted to make use of the facilities. There is one primary rule to follow - use of the galley is logged, anybody who fails to do the dishes will be assigned to do ALL of the dishes for the entire crew for a week in addition to regular duties.
The Ain Jalut also features several full gyms, athletics courts, and firing ranges to allow for the maximum number of crew to maintain physical fitness without needing to reserve holodeck time. Like most federation vessels the Ain Jalut features multiple holodecks allowing for basically any scenario the user can imagine. While priority is given to official ship functions (training, prototyping, and other needs), when not in use crew are free to use the holodecks for any purposes. By order of the Captain safety protocols are to remain active at all times and require senior staff override with a reason to be given for that override. If reason for override is deemed insufficient cause for disabling safety protocols any resulting injuries gets logged as ‘user error’ or ‘negligence’.
Civilian Policy
The short form policy is that there are no civilians on the Ain Jalut.
The long form understanding is that some positions that might be needed are not occupational specialties of Starfleet and thus may find themselves as serving on board the Ain Jalut. Personal trainers, non-medical dieticians, and clergy are a few examples of roles useful to the wellbeing of a crew while not being specialties for officers to train in. Ultimately the decision to allow for these or other civilian personnel is up to the Captain of the ship.
Under current policy all civilians wishing to live aboard must be sponsored by at least one commissioned officer, with a stated reason why this accommodation is necessary for the health and well-being of the sponsoring crew (as many sponsors are permitted as one can get - the more sponsors the more likely the civilian candidate will be granted a berth). If the civilian is permitted to serve aboard they are made to sign legal waivers drafted by Starfleet JAG indicating they waive their right to civilian protections while on board the Ain Jalut and no special consideration to their safety will be extended or granted in a ship-wide emergency and that for all legal purposes they are combatants subject to the authority of ship chain of command. Because of this waiver, for all intents and purposes civilians serving on the Ain Jalut are not legally civilian.
An officer or other crewman who sponsors a family member for a berth is considered to be invoking General Order 27 and thus will always have their request granted. Those who do are required to affirm that they understand that in invoking General Order 27 they are potentially putting family members in harms way and their duties do not permit them to grant family members special privilege in an emergency.
Diplomats, VIPs, and any other civilian being granted passage on the Ain Jalut as a result of official Starfleet orders do not fall under the above civilian policy. In an emergency these individuals are afforded all standard civilian protections and are not required to sign any waivers as their transit on the Ain Jalut is treated as a necessity of circumstance rather than an individual choice.
Life Aboard
While the Captain himself expects professionalism when on-duty, life board the Ain Jalut can come across as somewhat relaxed compared to other postings. The ship operates on a 3-shift rotation when out of space dock, with Alpha Shift starting at 0800, Beta Shift starting at 1600, and Gamma Shift starting at 0000. This is done to balance readiness with long term operations in deep space. When the Ain Jalut is in space dock the entire crew is granted shore leave - with travel restrictions only imposed on the basis of expected fleet readiness (for example: one might be restricted to traveling no further than ship transporter range during war time, while during times of extended peace might be permitted a one-week transit time).
On duty the most important thing for personnel is to do your job. If you and a partner can do your job better when chit-chatting that is generally permitted as long as there isn’t an inspection going on. “Flex time” or “buffer time” is generally frowned upon on the logic that as a Starfleet officer, your word should be sufficient. If you cannot be trusted to give good-faith estimates on task times then you cannot be trusted, and an officer not worthy of trust is not worthy of Starfleet. Beyond these two major rules the main mantra the Captain lives by is “my ship, your department”. As a result how a given department operates will depend almost entirely on the department head, with the XO only intervening if that department fails to perform to expectations.
Off duty officers are encouraged to “let their hair down”. The only major rule is that whatever you do off-duty cannot interfere with shipboard operations or impede your ability to return to duty. Light drinking is acceptable, a hangover is not. One could even turn an unused corridor into a bowling alley in theory, but in practice if you do that it better be cleaned up before an Ensign shows up to replace conduit or inspect the bulkheads. Self-destructive behaviors however will be noted and forwarded to relevant medical authorities. While officers are given vast leeway when off duty the unspoken rule is that you never do anything to hamper the ability of yourself or others to do their job.
Of special note are the holodecks. Due to many recorded incidents of holodeck malfunctions various safety protocols have been introduced to prevent harm to users. The most important of these are the inclusion of internal and external hard-kill switches that when tripped physically sever the holodeck from power sources. An algorithm installed in the base operating software requires that all scenes have the hard-kill switch present in some manner that is user accessible. However, as such things can be corrupted, external hard-kill switches are found just to the right of the main control panel at the holodeck entrance in the corridor.
Alert Protocols
When the ship is on yellow alert all awake personnel are required to report to their duty stations. Power is cut to the holodecks and other non-essential systems in anticipation of hostilities and to ensure crew engaging in recreational activities are sufficiently alerted to something happening if they somehow miss the increase in alert level. Science labs will continue to receive power from the ship’s main feed. Shields are raised but weapons remain offline during this time. During this time all civilians on board are required to follow any lawful orders given by any Starfleet personnel.
When the ship goes to red alert all personnel are required to report to battle stations. Power is cut from holodecks and every system not essential for maintaining ship combat status including most science stations and replicators. Some systems may be brought online by command override if red alert must be maintained for an extended duration. All tactical systems are fully powered during this time and security personnel are to arm themselves with phaser rifles as a precaution against boarding parties during combat. All personnel certified for small arms use are to equip themselves with phasers at earliest opportunity so long as doing so does not delay reporting to their station. Small arms lockers are maintained in critical areas for this purpose. Civilians are to be relocated to designated ‘safe zones’ on board ship near escape pods.
During red alert, if the ship is boarded by a party known to not distinguish civilians from combatants (e.g.: Borg, Undine, Terrans) then Starfleet personnel may at their discretion arm appropriately trained civilians with phaser weapons. Although civilians living on board waive their right to civilian protections the actual arming of said individuals is a legal grey area and must be treated gravely and personnel who do this must be prepared to justify their action to Starfleet legal authorities after the incident. Under no circumstances is an untrained civilian to be armed.
Senior Personnel
ALERT: Personnel records for this vessel not yet finalized. Please contact records for further information