Notes

Modern Navy Plan Revisions - All classes phaser array count limits - Passed/Closed on Engineering Department

rarcher — Mon, 20 May 2013 15:00:56 -0400

[snip]

Given there was no issues brought up with regards to the phaser array count limits MNP array limits will now be accepted and passed into the assembling modern navy plan document. Any questions please bring them to me in an e-mail thank you.

Robert Archer EDir

Engineering Department

Modern Navy Plan Revisions - All classes Torpedo launcher/casing limits - Closed/Passed on Engineering Department

rarcher — Mon, 20 May 2013 15:01:23 -0400

[snip]

Double post....

Engineering Department

Modern Navy Plan Revisions - All classes Torpedo launcher/casing limits - Passed/Closed on Engineering Department

rarcher — Mon, 20 May 2013 15:02:27 -0400

[snip]

Given there was no issues raised in the past two weeks on torpedo launcher limits nor ship casings limits this section of the modern navy plan is passed and accepted into the modern navy plan document. Any further questions should be brought to me in e-mail.

Robert Archer EDir

Engineering Department

Going forward plans on Engineering Department

rarcher — Mon, 20 May 2013 15:44:13 -0400

Ok since no issues were raised on the MNP revisions i posted two weeks back the final issues that had been brought up to be of concern for n3p revising has been handled between last term and this one. As such Aaron and I will be making updates to submit to the internet department in a week or so time to replace the NNP page and the other edept associated pages with nnp links to reference the updates. Much of the work is already done with coding things its just ironing out a few layout forms.

Aaron and i will also be looking at getting a new MOTD layout for the edept when we have the time as well so keep the eye out for that

The next plans we will be doing will entail contacting those maintainers for those designs in use, inquiring about correcting the spelling/grammar/etc issues present and then balancing them to modern navy plan standards so that we can hold all designs to equal standards. Now for contacting these people I will be giving a one months notice from the date sent to get back to me with an answer in some form.

Mainters/Designers of those designs will have several options for this overhaul.

1) They can turn over the design to edept maintaining permanently and aaron and i will update and fix them, they'll then go through a standard review process to iron out any missing details that we may have missed, while keeping to the basic profiles the design already has.

2) They can update the design themselves fixing the errors that I and Aaron have compiled that need the most fixing, again they'll go through a standard review process to iron out any missing details that may have been missed, while keeping to the basic profiles the design already has.

3) They can decline updating themselves, and temporarily given mainterhsip to the edept to update the design and then give it back to them for a check over giving three weeks time to return it back to me oked to put it up for a standard review process to iron out any errors that may have been missed, again keeping to the basic profile the design already has.

4) They can decline to update for any reason, in such a case the design will remain in use until an appropriate design is created to replace it.

Now for those that choose to update and revise their designs it will be attempted to be handled for up in review within a reasonable time frame, basically we dont want things to drag too long (ala years etc). So Aaron and i will be working closely with any maintainers that update to help them along providing help where asked or wanted.

Now one other trouble spot that I and Aaron have found is for those maintainers that are no longer in the club for a long period of time, and for all intents are impossible to get a hold of. I will make EVERY effort I can to do so within the next month to send a notice to these people who will then have a month's time from the date the notice is sent to get back to me on the choices above.

If say I can not get a hold of person X by that time then their designs will remain in use until a new one can be created to replace it, given current wordings in the charter this is my only option given our plans to hold all designs to equal standards and quality.

Now this said that is another point going forward that will be opened for dissucssion the exact details of the rewording etc and additions will be handled in that post when it comes up soon.

Finally, Aaron and I in the times for these talks since the start of the term or so have been working on updating the edept maintained designs and will be posting them for review in the coming days.

If anyone has any questions please address them here or in an e-mail to me, thank you

Robert Archer EDir

Engineering Department

Going forward plans on Engineering Department

jkurz — Tue, 21 May 2013 08:15:38 -0400

: Posted by Fleet Captain Robert Archer (Engineering Director) in Going forward plans
: Ok since no issues were raised on the MNP revisions i posted two weeks back the final issues that had been brought up to be of concern for n3p revising has been handled between last term and this one. As such Aaron and I will be making updates to submit to the internet department in a week or so time to replace the NNP page and the other edept associated pages with nnp links to reference the updates. Much of the work is already done with coding things its just ironing out a few layout forms.
:
: Aaron and i will also be looking at getting a new MOTD layout for the edept when we have the time as well so keep the eye out for that
:
: The next plans we will be doing will entail contacting those maintainers for those designs in use, inquiring about correcting the spelling/grammar/etc issues present and then balancing them to modern navy plan standards so that we can hold all designs to equal standards. Now for contacting these people I will be giving a one months notice from the date sent to get back to me with an answer in some form.
:
: Mainters/Designers of those designs will have several options for this overhaul.
:
: 1) They can turn over the design to edept maintaining permanently and aaron and i will update and fix them, they'll then go through a standard review process to iron out any missing details that we may have missed, while keeping to the basic profiles the design already has.
:
: 2) They can update the design themselves fixing the errors that I and Aaron have compiled that need the most fixing, again they'll go through a standard review process to iron out any missing details that may have been missed, while keeping to the basic profiles the design already has.
:
: 3) They can decline updating themselves, and temporarily given mainterhsip to the edept to update the design and then give it back to them for a check over giving three weeks time to return it back to me oked to put it up for a standard review process to iron out any errors that may have been missed, again keeping to the basic profile the design already has.
:
: 4) They can decline to update for any reason, in such a case the design will remain in use until an appropriate design is created to replace it.
:
: Now for those that choose to update and revise their designs it will be attempted to be handled for up in review within a reasonable time frame, basically we dont want things to drag too long (ala years etc). So Aaron and i will be working closely with any maintainers that update to help them along providing help where asked or wanted.
:
: Now one other trouble spot that I and Aaron have found is for those maintainers that are no longer in the club for a long period of time, and for all intents are impossible to get a hold of. I will make EVERY effort I can to do so within the next month to send a notice to these people who will then have a month's time from the date the notice is sent to get back to me on the choices above.
:
: If say I can not get a hold of person X by that time then their designs will remain in use until a new one can be created to replace it, given current wordings in the charter this is my only option given our plans to hold all designs to equal standards and quality.
:
: Now this said that is another point going forward that will be opened for dissucssion the exact details of the rewording etc and additions will be handled in that post when it comes up soon.
:
: Finally, Aaron and I in the times for these talks since the start of the term or so have been working on updating the edept maintained designs and will be posting them for review in the coming days.
:
: If anyone has any questions please address them here or in an e-mail to me, thank you
:
: Robert Archer EDir

Just a quick note from terms previous; The Avenger's specification page still lists the EDept as the maintainer, despite the fact that I had requested (and received approval) to have it returned to me in all respects. I know the IDept was slammed with work at the time, and this was likely missed as it is a low priority. I am slowly working on the Mark II version of the spec, and should have a draft ready for the EDept within the next month. I'll keep you updated as events warrant.

Jared

Engineering Department

Going forward plans on Engineering Department

rarcher — Tue, 21 May 2013 09:09:49 -0400

: Posted by Jared Kurz (Journeyman Designer) in Going forward plans
: : Posted by Fleet Captain Robert Archer (Engineering Director) in Going forward plans
: : Ok since no issues were raised on the MNP revisions i posted two weeks back the final issues that had been brought up to be of concern for n3p revising has been handled between last term and this one. As such Aaron and I will be making updates to submit to the internet department in a week or so time to replace the NNP page and the other edept associated pages with nnp links to reference the updates. Much of the work is already done with coding things its just ironing out a few layout forms.
: :
: : Aaron and i will also be looking at getting a new MOTD layout for the edept when we have the time as well so keep the eye out for that
: :
: : The next plans we will be doing will entail contacting those maintainers for those designs in use, inquiring about correcting the spelling/grammar/etc issues present and then balancing them to modern navy plan standards so that we can hold all designs to equal standards. Now for contacting these people I will be giving a one months notice from the date sent to get back to me with an answer in some form.
: :
: : Mainters/Designers of those designs will have several options for this overhaul.
: :
: : 1) They can turn over the design to edept maintaining permanently and aaron and i will update and fix them, they'll then go through a standard review process to iron out any missing details that we may have missed, while keeping to the basic profiles the design already has.
: :
: : 2) They can update the design themselves fixing the errors that I and Aaron have compiled that need the most fixing, again they'll go through a standard review process to iron out any missing details that may have been missed, while keeping to the basic profiles the design already has.
: :
: : 3) They can decline updating themselves, and temporarily given mainterhsip to the edept to update the design and then give it back to them for a check over giving three weeks time to return it back to me oked to put it up for a standard review process to iron out any errors that may have been missed, again keeping to the basic profile the design already has.
: :
: : 4) They can decline to update for any reason, in such a case the design will remain in use until an appropriate design is created to replace it.
: :
: : Now for those that choose to update and revise their designs it will be attempted to be handled for up in review within a reasonable time frame, basically we dont want things to drag too long (ala years etc). So Aaron and i will be working closely with any maintainers that update to help them along providing help where asked or wanted.
: :
: : Now one other trouble spot that I and Aaron have found is for those maintainers that are no longer in the club for a long period of time, and for all intents are impossible to get a hold of. I will make EVERY effort I can to do so within the next month to send a notice to these people who will then have a month's time from the date the notice is sent to get back to me on the choices above.
: :
: : If say I can not get a hold of person X by that time then their designs will remain in use until a new one can be created to replace it, given current wordings in the charter this is my only option given our plans to hold all designs to equal standards and quality.
: :
: : Now this said that is another point going forward that will be opened for dissucssion the exact details of the rewording etc and additions will be handled in that post when it comes up soon.
: :
: : Finally, Aaron and I in the times for these talks since the start of the term or so have been working on updating the edept maintained designs and will be posting them for review in the coming days.
: :
: : If anyone has any questions please address them here or in an e-mail to me, thank you
: :
: : Robert Archer EDir
:
: Just a quick note from terms previous; The Avenger's specification page still lists the EDept as the maintainer, despite the fact that I had requested (and received approval) to have it returned to me in all respects. I know the IDept was slammed with work at the time, and this was likely missed as it is a low priority. I am slowly working on the Mark II version of the spec, and should have a draft ready for the EDept within the next month. I'll keep you updated as events warrant.
:
: Jared

Thanks for the fyi on that Jared! I was not aware of that detail i'll edit our maintainer list i made with aaron the other day to list you as its current maintainer. I'm still compiling a full list of all errors and noting where in the various specs they are so i can provide maintainers if they wish a full list and suggested edits/changes to help hopefully ease any efforts on their parts along.

Just fyi the only thing on the avenger spec i would point out atm may need looking at more closely is those multi torp things, it might work as a new designer addition as a tech entry, anyhow we can talk it more once it comes up etc.

Again basically trying to help folks out with this work.

Also FYI the link for a word doc version of MNP is shared on my mediafire account if anyone wants it

Robert Archer EDir

Engineering Department

MNP Revision - Armadillo class shuttle on Engineering Department

rarcher — Thu, 23 May 2013 22:10:38 -0400

For our first revision design is the edept maintained Armadillo class shuttle, now approaching this in revising I went on the assumption is was a 'heavy' variant with some systems for the mnp ranges, and added in the micro launcher with such loads as a result as you'll see below. Some of the description of how the class looked was revised as well to match what was originally said but made it more clear for anyone that didnt know what say a Class-X or what not shuttles was without looking it up

Overall the design was an easy fix for the most part, and took me about 15 minutes to totally revise Aaron found a few odds and ends i missed so in total figure an event 30 minutes of work. The main point of this in review is seeing if it fits the profile design of being a 'armored shuttle' as the conclusion area notes given for use on a combat styled vessel like the Pendragon, personally I think it fits that role well for a shuttle, its not gonna go toe to toe by any measure as a fighter can but its still got some teeth etc.

Anyhow the design will remain up for review from 9pm Eastern on May 23rd 2013 until 9pm Eastern June 7th at 9am Eastern if no comments or concerns are raised the design will be filed under a google drive folder to await a page revision update. Again we're looking for detail errors, spelling/grammar errors and issues on 'tech' balance for its role as a heavy/armored shuttle by what the Modern Navy Plan now allows for such craft.

=====

Change Log from revision 1 to 2:

*Numerous grammar and spelling errors fixed
*Text layout changes to better flow and read
*Mission profile list added to better explain designs uses
*Revised shuttle shape to be more clear on description (aft section was 'settling to a one width' not really sure what that meant so scrapped it)
*Defined the types of systems the shuttle has to fit with Modern Navy Plan specific targets for this was sensor systems (none listed before!)
*Revised acceleration and deceleration rates to better match balance with fighter type craft. From 15/20 seconds to an even 30/30 seconds.
*Added a single torp/probe launcher with limited casing count
*Numerous more grammar changes
*Edited design and construction date to 2376 to account for the co-design work used with the Pendragon
*Minor layout edits to better read the computer and network systems

History and Mission Overview

The Armadillo shuttlecraft was developed at Avalon Ship Yards in early 2376, for two reasons.

The first reason for the shuttle’s development was the creation of the Pendragon Class battle cruiser. It was felt that a new shuttlecraft, more suited for the needs of combat vessels, was required.

The second reason for the development of the shuttle was the massive crew reassignments both during, and in the aftermath of, the Dominion War. With many ships in the field, a warp capable shuttle was deemed more suitable for transferring low numbers of crew members to various assignment postings.

The Armadillo class shuttle is named for a species of mammal native to Earth.

Mission Profiles

The Armadillo was designed to fit the following mission profiles.

*Transport for crew transfers or away teams
*Minor scientific surveys for parent craft
*Transport of ground forces for planetary or ship boarding combat
*Minor support of ground forces as air cover

Structure and Construction

The Armadillo has a narrow nose, widening as it approaches the mid-section, at which point it settles down to a streamlined curved box shape. The overall shape is a curved upper surface, starting at the nose, with comparatively flat underside and a flat rear hull surface. Warp nacelles are attached to the craft's sides towards the rear of the shuttle.

The shuttle is constructed from standard Tritanium and Duranium alloys. The main space frame is constructed in a single piece, which is intended to reduce the power required for the structural integrity fields.

Science and Remote Sensing Systems

Computer & Network Systems

The Armadillo carries a single isolinear rod computer core. User interface is provided by LCARS/MAJEL system combination. The system works on a standard isolinear data transfer network

Sensor Systems

The Armadillo class utilizes a Type 2 Sensor system with a Hi-Res scanning range of 0.7 light years and a Low-Res range of 1.2 light years.

Warp Propulsion Systems

The Armadillo is equipped with a Class 3, 5,000+ Milli-Cochrane Warp core. This allows for a sustainable cruise of Warp Factor 1.6 and a Maximum Sustainable speed of warp 2 for 48 hours.

Impulse Propulsion Systems

Sub-light propulsion is provided by a combination of standard RCS packages and a single impulse engine at the top aft of the hull, which is designed to provide adequate sub-light speed. These provide a sustainable speed of 0.23c. It can reach full impulse in 30 seconds and a full stop in that same time frame. Although not the fastest craft around, its maneuvering ability is exceeded only by standard fighter craft.

Tactical Systems

Given the general wartime conditions during development, it would have been foolish not to give the Armadillo some tactical systems. It is important to note that, although present, weaponry on the Armadillo does little more than comfort the crew against anything larger than another shuttle.
Shield Systems

The Armadillo was given a Type 3 Shield system providing a Maximum Gravitation Load of 268 MW, with a Maximum Energy Dissipation rate of 7.3x10^4 kW.

Phaser Systems

Phaser systems consist of two Type 5 phasers as standard they are mounted to port and starboard at the forward edge of the shuttle, with a maximum energy output of 0.3 MW and an effective range of 18,750 km. non-upgradeable, each array has 5 emitters each.

Torpedo/Probe Systems

Torpedo/probe launching is handled by a single forward mounted, Type-1 micro torpedo/probe launcher. This launcher can fire a single micro torpedo/probe every eight seconds. These micro torpedoes/probes have a maximum effective range of 175,00 km. The Armadillo carries 5 micro probes and 7 micro torpedoes as standard.

Utility Systems

The Armadillo is equipped with a single Transporter Pad, which can transport two people up to 5,000 km.

Crew Support Systems

Although extensive crew support facilities are impossible on a shuttlecraft, some were included. A single replicator is found within the craft, limited to a single beverage or small dish at a time, along with two emergency med-kits, should the need to use them arise. Survival rations are stored next to the replicator, should the latter be inoperable.

Technical Specifications

Dimensions and Structure

Length: 9.43 meters
Beam (Width):5.72 meters
Height: 3.24 meters

Decks: 1

Crew Complement

Officers and Crew: 1-3
Total Capacity: 10
Maximum Evacuation Limit: 17

Computer Systems

Core: Isolinear Rod Based Computer Core
Operating System: Starfleet Library Computer Access and Retrieval System (LCARS)
User Interface: MAJEL

Warp Systems

Power Plant: 1x 5,000+ Milli-Cochrane M/ARA core feeding two nacelles
Cruising Velocity: Warp 1.6
Maximum Sustainable Velocity: Warp 2 (48 Hours)

Impulse Systems

Full Impulse: 0.23c
Accelerate: 30 seconds
Decelerate: 30 seconds

Defensive Systems

Shield Maximum Graviton Load (Continuous): 268 Megawatts
Shield Maximum Energy Dissipation Rate: 7.3x10^4 kilowatts

Offensive Systems

Phasers: 2x Type-5 Phaser Emitters

Torpedoes/Probes:

1x Type-1 Micro torpedo/probe launcher
5x assorted micro probes
7x micro torpedoes

Conclusion

Following the development of the Armadillo as an armored shuttlecraft, the design has been used extensively by Avalon and other shipyards, due to its versatile and resilient design. As such the Armadillo will continue to see service in a variety of situations in the years to come.

Robert Archer EDir

Engineering Department

MNP Revision - Liberty Class Runabout on Engineering Department

rarcher — Thu, 23 May 2013 22:31:42 -0400

The second design up for revisions maintained by the EDept is the liberty class runabout, given the read of the original design spec i classed this as a 'medium' variant for purposes of MNP tech ranges and outfitting. As with the Armadillo I gave careful consideration to the fact that this design was meant as an stf version akin to the danube given its history of design. As such I did what I could to make it semi-multipurpose in nature to fit a more broad range of away team needs in a sim. I've also revamped some details for various things as is noted below in the change log

Overall this took me a little more work then the Armadillo did, but still kept it in at the 40 minute mark, revising by Aaron for a double check probably added another 5-10 mins or so so say 50 at the outside.

In reviewing this keep in mind that a runabout blurs the lines between a shuttle/aux craft but is much like a fast courier or similar ship, kind of like the Jenolen from 'Relics' in TNG where scotty is trapped in stasis in a transporter now granted there likely that ship was some sort of two or so deck ship but the idea i think is the same somewhat

In either case this review is open from 9pm Eastern on May 23rd 2013 until June 7th 2013 at 9am Eastern time. If no comments or concerns are raised it will go into a google drive folder to await a page update. Again we're looking for spelling/grammar errors, detail errors and balance considerations with what the Modern Navy Plan now allows for runabouts

====

Change Log from Revision 1 to 2:

*Various grammar and spelling errors fixed
*Minor edits to spec page layout to better flow with SSSF and read better
*Updated tech specs to MNP standards across the design
*Filled in details of where the two mini computer cores are on the Liberty
*Gave details of where the Liberty's warp core is, and its ejection systems
*Revised impulse speed acceleration and deceleration to 30 seconds to fit more balanced with other Aux craft
*Merged the metaphasic shields entry into the standard shield system entry, since it is not a separate system but rather a modification to standard shields by programming.
*Merged probe systems entry with the Torpedo entry
*Defined where the Liberty's tractor emitter was placed on the vessel
*Changed 'Bridge' to 'cockpit' where applicable to better fit the role of this being an Aux sized craft
*Defined where the transporter pads were on the Liberty it was just 'aft' somewhere on the original
*Added some details to the 'Bunk Room' as well as defined just where it was more clearly
*Defined general commissioning date
*Removed defining mark of Micro from Impulse Engines
*Reworded Impulse section to flow better

History And Mission Overview

In early 2377, Star Fleet decided that a new runabout was needed to complement the existing Danube-class. Step forward Avalon Ship Yards, a busy group of designers who had proved themselves a valuable tool for Starfleet with their previous designs.
The designers at Avalon realized that they didn't need to make a new Danube-class, and so they set about coming up with a design that would be just as reliable and enduring, but suitably different. After several weeks of nose-to-the-grindstone work they presented Star Fleet with three possible designs. Star Fleet chose the third of these, dubbed "Liberty" by the designer. This became the prototype for the Liberty-class runabout.

Mission Profiles

As a Runabout, the Liberty-class falls between the roles of a shuttlecraft and a general purpose starship. The Liberty-class is expected to perform such tasks as

*Rapid response rescue missions
*Short-term scientific missions
*Transport of cargo and personnel
*Emergency tactical missions

Structure And Construction

The designers at Avalon "borrowed" from recent Star Fleet designs when designing the hull of the Liberty-class. The main hull looks like a scaled down version of the saucer section of the Nova-class, included the "cut-away" section at the front, which on the Liberty-class houses the deflector array.

The warp nacelles inherited the engine cowling of the Defiant-class warp propulsion system. They are located on the dorsal surface of the hull, with the cowling covering them on the dorsal surface. The ventral surface is smooth, aside from the landing gear.

The interior of the craft is built around a central corridor, which connects to the key areas of the runabout.

Access hatches are mounted to the front port and starboard of the craft. Four landing struts located on the four belly corners of the Liberty allow it to land on any surface that will support the weight of the craft.

The Liberty-class is constructed from tritanium and duranium alloys, with transparent aluminum used for the view ports. Avalon used Transporter Welding when making Liberty-class runabouts, although some secondary shipyards that did construction did not.

Science And Remote Sensing Systems

Sensor systems

The Liberty-class Runabout has a Type-4 sensor system. This unit has a long range effective scan of 2.4 light years, and a short range effective scan of 1.0 light year. The sensor pallets are arranged in clusters along the exterior of the hull. The main deflector is located at the forward nose cone area at the front of the runabout.

Computer Systems

The Liberty-class has two computer cores. Both are comprised of 8 processing units utilizing isolinear chips with a single bio-neural gel pack attached to each core for enhanced processing speed. The cores are mounted to port and starboard at the rear of the cockpit.

Warp Propulsion Systems

The Liberty-class Runabout is fitted with a class-2 starship warp core rated at 215 Cochranes. This allows a Cruising Velocity of Warp 2.0, a Max Sustainable Velocity of Warp 4.0, a Max Velocity of Warp 5.0 for 12 hours, and an Emergency Speed of Warp 5.8.

The core and its associated systems feed both wing mounted warp nacelles. In an emergency, ejection systems propel the core and the antimatter pods out the bottom belly of the Liberty.

Impulse Propulsion Systems

Two sub-scaled impulse units provide sub-light propulsion and primary power generation for the Liberty-class. It can reach a full impulse speed of 0.24c in 30 seconds and can come to a full stop in that same amount of time.

Tactical Systems

Defensive Shields

The Liberty mounts a Type-3 shield system, it has a Maximum Graviton Load of 268 MW and a max dissipation rate of 7.3x10^4 KW. The system also includes metaphasic shielding to aid in protecting the Liberty from solar body entry or similar phenomena in the course of its missions.

Phaser Systems

The Liberty-class is fitted with six Type-5 Phaser arrays, consisting of 5 emitters to each array. These are located forward-dorsal, forward-ventral, aft-dorsal, aft-ventral, port and starboard, to provide maximum protection. The system has a max energy output of 0.3 MW, and a max effective range of 18,750 km.

Torpedo/Probe Systems

There are two Type-2 micro-torpedo launchers on the Liberty-class; one mounted forward, one mounted aft. The Liberty holds 30 casings, 10 are assorted micro probes, 20 micro photon torpedoes. The launching system can fire a probe/torpedo once every four seconds.
Unlike the Danube runabout or other more recent designs, the Liberty can not mount any external torpedoes even in special cases.

Command And Support Systems

Cockpit

The cockpit of the Liberty-class is located at the front of the craft. Conn and Ops are at the front, with science to port and engineering to starboard. Any of these can double as Tactical in combat. Although intended for 4 people to crew the craft, it is possible for as few as a single person to fly the Liberty-class if needed.

Science Lab

There is a small, general use science lab found in the port compartment behind the cockpit.

Utility Systems

Tractor Beam Systems

The Tractor beam has a range of 7,500km, dependent on the speed and mass of the object being tractored. The emitter is mounted along the aft belly edge of the Liberty.

Transporter Systems

A 4 person transporter pad is located behind the cockpit to starboard, which has a maximum effective range of 10,000km.

Crew Support Systems

Sickbay

A small 'Sickbay' area is located starboard, opposite the transporter pads. This is composed of a single bio-bed and basic medical supplies, plus Med-kits for field use.

Bunk Room

A "bunk room" contains 3 wall-mounted beds for the crew to use. An additional 3 beds can be added with a six hour refit time, but space will be cramped as a result. It is located along the aft most portion of the Liberty, a pair of small windows look out to the rear of the craft.
There is also a four person table and replicator along the port wall here. The area can also double as a briefing room for the crew when needed.

Technical Specifications

Dimensions and Structure

Length: 23.44 meters
Beam (Width): 20.29 meters
Height: 5.56 meters

Decks: 1

Crew Complement: 1-4
Maximum Evacuation Limit: 30

Computer Systems: 2x Isolinear Chip Data Cores, with a single bio-neural gel pack
Operating System: Starfleet Library Computer Access and Retrieval System (LCARS)
User Interface: MAJEL
Warp Systems

Power Plant: 1x 215+ cochrane M/ARA core feeding two nacelles
Cruising Velocity: Warp 2
Maximum Sustainable Velocity: Warp 4
Maximum Velocity: Warp 5.0 (12 hours)
Emergency Speed: Warp 5.8

Impulse Systems

2x Impulse engines
Max Speed: 0.24c
Accelerate: 30 seconds
Decelerate: 30 seconds

Defensive Systems

Shield Maximum Graviton Load (Continuous): 268 MegaWatts
Shield Maximum Energy Dissipation Rate: 7.3 x 10^4 kilowatts

Offensive Systems

Torpedoes/Probes: 2x Type-2 Micro-Torpedo Launchers
Standard Torpedo Payload: 20 micro-photon torpedoes
Standard Probe Payload: 10 assorted micro-probes
Phasers: 6x Type-5 Phaser Arrays

Ships Of The Class

USS Liberty, NCC-99301
USS Freedom, NCC-99302
USS Justice, NCC-99303
USS Peace, NCC-99304
USS Loyalty, NCC-99305
USS Dignity, NCC-99306

Conclusion

The Liberty-class is a general purpose Runabout, designed to serve as a complement to the larger ships of Starfleet. While it lacks the modular design of the highly successful Danube, it compensates with lower maintenance requirements associated with only having to deal with a complete craft.

====

Robert Archer EDir

Engineering Department