Posted by Andrew Robinson in Templar Class Heavy Fighter - Language and Grammar Update - Public Comments

Posted by Andrew Robinson in Templar Class Heavy Fighter - Language and Grammar Update - Public Comments

Posted by Captain Philip Graham (Engineering Director) in Templar Class Heavy Fighter - Language and Grammar Update - Public Comments
Posted by… suppressed (6) by the Post Ghost! 👻
Howdy, all. Since coming back to the club, I’ve taken back maintainership of the specs I designed and expressed a desire to Phil to update some of the grammar and language. I was somewhat younger and significantly less experienced when I wrote them. The first one up is the Templar Class Heavy Fighter. No changes, substantial or otherwise have been made to systems or spec. There have been grammar and sentence structure changes that have no effect on the craft itself or its approved technology. Phil asked me to post them directly to the ED for review as I completed them.

---

History and Mission Overview

Starfleet has made use of fighter craft for more than three hundred years, long before it’s inception as the defensive and exploratory arm of the Federation. Largely in a role as planetary defenders and small scale combat craft. Until the outbreak of war with the Dominion, these fighters had rarely before seen extended combat actions in space.
During the Dominion war, vast numbers of Starfleet fighter craft were lost to the superior firepower and speed of Jem’Hadar fighters. Despite the valiant efforts of existing craft, there were no real equivalents that could match these enemies for sheer speed and overwhelming rate of fire and accuracy.

Starfleet Research and Development were unable to sacrifice the time or resources to adequately facilitate research into a potential new fighter craft. With material and personnel stretched almost to the breaking point fabricating new technologies and spare parts to aid the front line battle forces, it was determined that the project should be outsourced. Thus, the defence contract agency Wolfestar Systems, based in the Boliarus system was chosen.

Unfortunately, the Wolfestar development complex was destroyed almost completely in the conflicts along the Bolian front in early 2374 as the newly reassigned Sixth Fleet clashed with Dominion Forces. All project data was presumed lost.

In late 2378 however, recovery teams from Wolfestar’s now re-established headquarters on Boliarus VII discovered that the backup data core maintained in vaults deep beneath the planet’s crust had escaped almost unscathed. Amongst the recovered data were found the almost completed specifications for the new fighter craft.
With the approval and continued support of Starfleet Research and Development, the project was completed in late 2380 and the lead design advisor for Starfleet, Fleet Captain Andrew Robinson named the craft and its class Templar, in honour of its flagship role protecting Federation citizens rights to free travel.

The Templar Class Fighter is a multifunction red zone combat craft capable of fulfilling a number of varied roles including, but not limited to :

• Fighter to Fighter combat operations.
• Support of Capital Craft in Fighter operations.
• Reconnaissance and Patrol of contested/hazardous regions
• Convoy escort
• Starbase/Outpost Support Operations
• Quarantine enforcement operations
• Planetary troop support and atmospheric combat operations
• Atmospheric supply craft support

Structure and Construction

The primary frame of the Templar Class Fighter Craft is composed of fabricated duranium/tritanium macrofilament truss frames connected using transporter welding techniques. This basic framework provides physical integrity to the craft at rest.

A secondary framework of aluminium crystalfoam stringers are phase transition welded to the primary framework to prevent the extreme vibrational stresses suffered at high impulse manoeuvring speeds.

Due to size and mass constraints, rather than the traditional secondary hull provided in larger, less manoeuvrable craft, the Templar makes use of reinforcing micro extruded terminium plating, transporter welded into the primary frameworks, themselves reinforced and separated with polyduranide rodding.

The Templar nose is formed by a rounded, elongated triangular design, sweeping back into shortened, but wide, equidistant wings similar to the ‘Delta Flyer’ of the U.S.S Voyager. These then widened to become a more permanent part of the main fuselage, attaching to an aft, extended engine compartment with a single, wide range Impulse exhaust vent.

Science and Remote Sensing Systems

Previous fighter craft, such as the Argus and Peregrine Classes have used a standard computer system adapted from the larger Shuttlecraft Classes, and using the LCARS operating system with the MAJEL user interface. The nature of the Templar, however, and its intended use during high-speed close combat, precludes the use of such a generalised set of operating software. It was thus determined that a faster, more efficient, specialised operating system and interface were required.

The Templar utilises a bioneural-assisted isolinear data core, with bioneural interlinks to all other systems, shielded with EM and graviton reflective polyduranide sheeting to prevent system interference.

When designing the Templar Operating System, Wolfestar took into account the need for a simplified series of command pathways that would yield maximum speed and efficiency with minimum energy requirements and minimum processor load. It was with this in mind that Wolfestar Computer Innovations Systems Department created the Reduced Instruction Set Command and Control System, or RISCCS. When tested, RISCCS surpassed all possible expectations, processing command and control operations at an average speed of 9,300 kiloquads/sec, more than twice the speed of an isolinear data core using the LCARS operating system.

It was plain that using the standard MAJEL interface of keyboard and voice was impractical in the high-speed world of fighter combat, and to complement RISCCS, a simplified Interface was needed. It was with this in mind that the Computer Innovations Systems Department came through once more with the Command Operations Management Tactical control interface, or COMTAC.

COMTAC provides a verbal interface ability, used primarily for combat operations. This system is able to handle complex strings of verbal commands, including the rerouting of power and the manipulation of shielding, weaponry, propulsion, automated damage control systems, and all other primary and secondary systems. COMTAC displays system status through a three dimensional Heads Down Display across a series of chest height mounted display panels. There is also a tactile interface that allows manipulation of systems through the status display panels, rather than a keyboard system, though this is used primarily in non-combat operations when time is not a factor in systems control.

Impulse Propulsion Systems

The Templar is incapable of faster than light travel, as constraints on space made the addition of a warp propulsion system impractical. Main propulsion is provided by a single medium fusion generator, housed in the rear third of the craft. This generator contains an auxiliary boost system, capable of providing emergency acceleration thrust to 0.43c, albeit for extremely short periods of time – enough to escape a dangerous situation or accelerate into one should the need arise. Deceleration is slower, as the .25c impulse system isn’t capable of maintaining such a rapid pace and relativistic concerns are enhanced in a smaller craft.

Because of the increased maximum speed and the low acceleration times, the hull is lined with more than 200 mini Inertial Dampening Field generation units, providing over 300% more inertia dampening capability than standard. These are augmented by a comparable number of Structural Integrity Field generators, providing sufficient added hull integrity to survive extended travel at .92c. Despite these specifications far exceeding the crafts capacity, they give the Templar the redundancy that Wolfestar is known throughout the galaxy for.

Due to its lack of warp capability, the Templar relies on carrier support to ferry it from target to target. It does possess a series of magnetic grappling systems along the lower hull, which allows it to attach itself to the outer hull of a vessel. This permits it to travel with that vessel at warp speed, detaching once a destination is reached.

Tactical Systems

Defensive Shields

The Templar is equipped with a single, modified, Type IV shield generator contained within the aft secondary spaces between the COMTAC routing system and Computer Core. This modified system consists of a cluster of twelve 16MW graviton polarity sources feeding a single 900 millicochrane subspace field distortion amplifier. This producing an output of 192 MW and a maximum primary energy dissipation rate of approximately 52,123 kW. It should be noted that powering shielding at maximum levels reduces the effective output of the main pulse phaser cannons, and is designed primarily to function at that power level only in conjunction with the microtorpedo systems in strafing operations against larger craft. At approximately 65% of this power rating, the main pulse phaser cannons are at maximum effectiveness.

Phaser Systems

Following the success of the Defiant Class weapons systems, it was deemed appropriate by Wolfestar’s Tactical Systems Department to incorporate a similar, if less powerful design into the Templar. Above the main nose are mounted a pair of fixed pulse phaser cannons with a single forward firing angle. This fixture is mirrored below the nose, forming a quad.

Due to the power requirements and overheating issues inherent in providing such powerful primary weapons for a fighter craft, it is not possible to fire all four cannons simultaneously for extended periods of time. As such, standard firing is conducted in a linear sequence, a single barrel at a time. They can, however, be linked into a dual fire mode. With reductions of up to 50% in shield power to prevent complete power drain and for significantly shorter periods of time, a full quad fire mode is available.

Torpedo Systems

Unlike other fighter craft, the Templar is designed to function as an extended use strike unit, and it was with that in mind that the Wolfestar Ballistic Projectile Division added wings to the initial design. These serve no aerodynamic or manoeuvring purpose but are instead solely intended as torpedo firing platforms.

Each wing contains a single micro-torpedo tube, supplied by a high capacity, quick loading belt system. The wings, with an internal dimension of 16.5 cubic metres are of sufficient size to contain a standard payload of 100 micro-torpedos each, in a reinforced magazine; this magazine is linked directly to the loading belt mechanism.
Due to the solid belt design, the torpedo loading system is capable of reloading a single torpedo tube in 2.4 seconds. Each tube is reloaded behind a 24 torpedo buffer stock, eliminating lag time between launches.

Command and Support Systems

Unlike similar craft, the cockpit is hidden beneath ablative armour. This cockpit is sunk ahead of the main computer core, to either side of the wings. With the seat set to an ergonomic 16 degrees rear angle, the pilot has a series of four monitor screens directly before his eyes. Each screen in this manner links to a series of visual sensors capable of projecting on each of these screens a visual from any angle, though the two centre screens by default provide forward views to aid in navigation.

Directly below these screens, requiring some minor lowering of the head are a series of 6 smaller screens and one central, larger screen depicting primary and secondary system status in any customisable format, though the default settings are:

• Far Left Screen 1 - Engine Status
• Left Screen 2 - Power Status
• Left Screen 3 - Computer Status
• Centre Screen - Tactical Threat Analysis Monitor - Provides information on all detected threats and current locations relative to the craft. This also includes information concerning friendly units and a threat analysis by grading of all vessels e.g. Capital ships no immediate mobile threat, fighters, immediate threat, friendly ships no threat. Using a predictive algorithm to highlight any targets classified as a critical threat the system issues an audible warning, highlighting that threat on the main forward screen if visible within that range.
• Right Screen 3 - Pulse Phaser Cannon Status
• Right Screen 2 – Micro-torpedo Assembly Status
• Far Right Screen 1 - Environmental Control, Secondary Power Systems and Auxiliary Systems Status.

Primary flight control is provided by the standard auxiliary helm control stick supplied to larger Starships. This control stick uses thumb and finger control mechanisms for weapons select and a larger forefinger control to fire selected weapons. Torpedos and phasers can be fired, and weapons selected using the COMTAC verbal interface, though this procedure is of course slowed by the need for speech.

Velocity and engine power are controlled by a raised control lever to the right of the pilots seat which provides COMTAC access through a thumb key along the left-hand side. Depression of this key provides the same input as the “TAC” mode of verbal address which itself is an adaptation of the more traditional “computer” verbal command.

Utility Systems

Because of its nature as a sublight fighter craft, the Templar cockpit is designed to function as an extended duration life pod. Upon verbal or emergency tactile request, the cockpit is blown away from the main craft using explosive bolt devices. Small, shaped, solid state explosives, drive the cockpit, including its armour panelling away from the craft at approximately 4 m/s. Once ejected, the cockpit systems are powered by an emergency micro fission generator with a battery backup, providing approximately 72 hours of continuous life support, or 300 hours if the emergency medkit is used to induce sleep.

Provided a larger friendly craft is on site, the life pod will activate small reaction control thrusters to propel the lifeboat at 16 m/s towards that craft, emitting a coded or open frequency emergency distress signal. Once within range, the larger craft can tractor the pod in, or transport the pilot aboard.
In case of landing on a planetary or atmospheric body, the life pod systems are capable of recharging through solar power cells. The pod contains a three-day emergency ration kit, medkit and a Type IIIa Pulse Compression Phaser Rifle with twelve power packs.

Crew Support Systems

The Templar uses a standard environmental control system to provide air to the cockpit compartment. This system can be adapted to provide air to other areas of the craft for the purpose of emergency repairs in space. Other areas are reached via small crawlways which run the length and width of the craft, centred on the cockpit area.
Subspace communications are provided by a modified antenna array tied directly into the COMTAC Interface and controlled by a pad activated by the left foot. When depressed, this triggers the communications subroutine and verbal input is required to direct encrypted communications to a target, e.g. depressing the pad and calling “Red 2” would place the pilot in contact with the craft designated Red 2. Communications systems can be accessed directly through Far Right Panel 1 of the status display screens, using the tactile screen interface.

Pilot ablution and sanitation facilities are provided by a series of flight suit mounted tubing which carries waste away and recycles it using a primitive replicator unit, converting it to pure water for the pilot’s emergency supply and general convenience.

Technical Specifications

Dimensions and Structure

Length
19 meters

Beam (Width)
24 meters

Height
9 meters

Crew Complement
Officers and Crew - 1 Pilot

Computer Systems

Core
Bio-neural data core

Operating System
Reduced Instruction Set Command and Control System (RISCCS)

User Interface
Command Operations Management Tactical control interface (COMTAC)

Impulse Systems

Power Systems
Single Medium Fusion Reactor Core

Full Impulse
0.25c

Accelerate
4 seconds

Decelerate
6 seconds

Emergency Booster System Maximum Speed
0.43c

Emergency Booster System Maximum Acceleration
0.3 seconds

Emergency Booster System Average Decelleration
19 seconds uncontrolled

Defensive Systems

Shield Maximum Graviton Load (Continuous)
192 MegaWatts

Shield Maximum Energy Dissipation Rate
54300 kilowatts

Offensive Systems

Micro-Torpedoes

Torpedo Tubes
2

Standard Payload (total)
200 micro-torpedoes

Phasers
4 Heavy Pulse Phaser Cannons

Conclusion

The Templar Class Heavy Fighter is the leading edge of Starfleet’s commitments to further fighter production and is now in mass production. Doubtless, it will prove itself to be the preferred and primary multipurpose combat fighter in use by Starfleet. Wolfestar systems have proven themselves more than capable of matching Starfleet Research and Development in the production of cutting edge craft and technology.

Multi-purpose, simplified control mechanisms make this the future of all further fighter designs and will no doubt become the benchmark as this class bridges the gaps in current fighter theory and practical tactical application.

Status - Under Review

What’s the end date on the review?

Andy

I’d also like to know this....

Robert Archer

My goal is to get to these within 5 days,

With that I see no change to the model itself. This model is advanced to Public Comments - Public Comments end on 05/05/19

Philip Graham
EDir

While I applaud wanting to push these through quick keep in mind at a MINIMUM specs review periods are two weeks per the edept charter

Robert Archer

Rob,

Can you link that section.. What i see in energie is

“The Engineering Director shall set approval criteria by Departmental Mandate and shall serve as the approving authority.”

Can you point out a diffrent section mandating two weeks?

I did find the section about non-substantive changes that gives the EDir permission to pass them without review :P

“Where the last-approved version of the design is currently in service: the new design shall be considered a revised version when substantial changes, such as in balance, layout or mission focus, and determined as such by the Engineering Director, have been made to the original design. If non-substantial changes have been made, the Engineering Director is empowered to pass the design without a review period. The design shall be given a new Mark number only if it is considered a revised version.”

But no, despite the tradition for a two week review period, it has always been a matter of departmental policy, rather than edicted requirement. I originally set the two week review period because it seemed a reasonable time to allow the usual tech-heads to get their licks in for each review cycle.

Andy

The current and, relatively unchanged for quite some years, submission policy which includes a two week review period can be found here https://www.star-fleet.com/ed/ship-submission-policy.html

Andy

Given that there is no further comments, this is herby approved, the Temp Spec will be posted shortly on the EDept Page.

Philip Graham
Director
Engineering Department