______

_-' .   .`-_

|/ /  .. . '   .\ \|

|/ /            ..\ \|

\|/ |: .   ._|_ .. . | \|/

\/ |   _|_ .| . .:  | \/

\ / |.   |  .  .    .| \ /

\||| .  . .  _|_   .|||/

\__| \  . :.  .|.  ./ |__/

__| \_  .    .. _/ |__

__|  `-______-'  |__

-,____  ____,-

---'  `---

       ** UNITED CONFEDERATION OF INTERSTELLAR PLANETS **

       **     OPERATIONS COURSE GUIDE Version 2.10     **

       **             Course Guide - PDF Version            **

       **************************************************

Version 1.00 By Lieutenant Commander L. Horatio Hawke

Version 1.50 By Commander L. Horatio Hawke

Version 1.70 By Lieutenant Junior Grade Thera Ra’even

Version 2.00 By Lieutenant Major Matt Philips

Version 2.10 By Ensign Brex Larsen

TABLE OF CONTENTS

I.                Introduction

II.            Duty Description

III.        General Information

IV.            Prioritisation

A.    Who has priority?

B.    Other Departments

V.                Technical Briefing

A.    Computer Systems

B.    PADDs

C.    Sensors

D.    Tricorders

E.    Life Support Systems

VI.            Diagnostics

VII.        Operating Modes

VIII.    Miscellaneous

A.    “Pecking Order”

B.    Units of Measure

I. INTRODUCTION

Any person who would like to work in the Operations (Ops) position needs to be well rounded, flexible, and prepared for any situations that may arise. The Ops Manager is like a conductor, co-ordinating the actions of various other departments on the ship. This is why it has been said that the pulse of a starship runs through the Operations Station. You, as the Ops Manager, will have your finger on that pulse.

Note- It is advised that a potential Ops Manager also read the Engineering, Tactical, Science and Helm SIMGuides. This will, more than likely, help you when you are performing your duties as these posts are closely linked.

II. DUTY DESCRIPTION

Four areas fall under Ops: Main Ops, Mission Ops, Strategic Ops (Starbase Ops), and Flight Ops.

Main Ops

It is the responsibility of this post to schedule all the resources or hardware, live power or the use of sensors that may effect various departments in such a way that the mission goals are not jeopardised.

Mission Ops

This station is used specifically for monitoring activity related to secondary missions and primary away team missions. It also serves as a relief for Main Ops.

Strategic Ops (Starbase Ops)

Strategic operations aka Stratops aka Operations officer has a very important role on board a Starbase, not only is the Strategic operations manager to do the normal functions for their position, they are also expected to act like an air traffic controller. He or she assigns headings, docking ports, or a docking bay. If the vessel is large enough it may require docking inside the station, through the outer space doors and into the main starship docking area. Each ship needs to be prioritised on a need of aid basis. The strategic ops officer must make sure that the correct size port/bay is assigned for each ship, although most ports are generic and can fit any ship it is customary to, keep certain size vessels in certain areas in order to avoid any accidents. Another important task is to assist the CO on any strategic decisions that may arise when the station is under attack. Strategic operations is also responsible for the cooperation between tactical and security departments. Because of the size of a Star base those departments need to work side by side.

Flight Ops

This position is the Strategic Ops Post for a starship. It is a position that is usually left up to the CO on whether it’s available or not. But for those SIMs that have it, or would like to have it onboard, Flight Ops essentially handles the launching of all auxiliary craft to and from the ships.

The Ops Manager of a starship, who is on duty must declare all planetary sensor readings; this is one of your primary functions. You also declare in-ship sensor readings that would not be monitored by engineering, such as a minor drop in sensor efficiency, or electrical interference. Operations also declares all onboard damage during a battle, the status of the ship and non-combat status of antagonist/neutral ships and controls non-combat sensors. Science (Sci) is also designated as an extension of Ops, Ops detects the item and then Sci takes over to get all the details and information about the object. Since Sci is optional, if there is no Sci officer, Ops handles these tasks. The following sections give you a closer look at areas the Ops officer deals with.

III. GENERAL INFORMATION

The LCARS will handle most things for you but at times it may be necessary for you to intervene, after all the system is not perfect. Feel free to interfere with the running of the ship as and when you feel like it, just be sensible and remember that you should always warn any departments you would be drawing power from before starting to do so. A few examples of your duty are:

Transporters

You may be required to operate the transporters from your console and also to keep a transporter lock on personnel transported from the ship for fast recovery. Please read the Transporter guide found here.

Away Teams (AT)

This post is usually one who has the wonderful job of sitting on the bridge and worrying, keeping transporter locks, and updating the CO! (I would advise messaging the AT so that you are kept up-to-date on what's happening).

General/Planetary Sensors

If you are approaching a planet, star system or anomaly, you are required to give details on it. If it's not identifiable as a ship it's still yours to report on. If your sensors pick up what seems to be a cloaked ship, it is still an anomaly until it has been decided that it is a ship, therefore until that has been confirmed you must continue reporting on it.

Resource Management (Power, CPU Time, Sensor Data/Usage, Equipment)

It is your sole responsibility to ensure that everyone on the ship has quarters, food and supplies, and their own luggage (i.e. not the luggage of the poor fool who purchased a budget ticket to Mars)

IV. PRIORITISATION

A. Who has priority?

The Commanding Officer (CO) and Executive Officer (XO) are the most important officers on the ship, and so when they want data give them full priority. The view-screen is one of the most obvious means of giving the CO and XO information in a visual form. You will also be expected to inform them, in voice statements, of the things that are outlined in the duty description; i.e. other ships (non-combat only), up to date information on the ship status, etc.

Occasionally, other officers will have higher priorities. In military missions the Tactical (Tac) officer will have a higher priority, similarly if a science mission goal is in operation then the Sci officer will have a raised priority. This is normal and usually would only be reflected by increased information flows, and would be pre-set by the computer.

However, if the goals are scientific and the ship is attacked or called upon to initiate a military assignment, then it is your job to balance the resources at your disposal in the attempt to satisfy all the immediate, short term and long-term goals. The organisation of the ship is thus the problem of the Operations officer, if you cannot accomplish all of these at full, compromise.

Examples

·                     Immediate goals:  The ship may be under attack.

·                     Short term goals:  Insuring that the guest science team, on board to study a nebula, are able to finish their studies.

·                     Long term goals:  The ship does not run out of resources before it docks next

B. Other departments

·                     Tac - Tactical will usually have a sizeable chunk of long-range sensors that you can increase or decrease as the mission develops. It is the military post and anything involving combat is its information to report.

·                     Sci - Similar to Tac in so much as it will be a main user of the sensors; there is almost always some study or another going on, unless the ship was launched on a purely military mission.

·                     Med - Medical will need to know when they will need to respond to a medical emergency; occasionally they may need planetary sensors routed through to medlab so they can assess a planetary situation.

·                     Conn - Helm will need the relevant navigational data to set courses and to fly the ship with. Conn is also in contact with engineering; officially they are the liaison between the bridge and Eng on the propulsion systems only.

·                     Eng - Engineering is a special case with Operations, as with the job description above Eng are your task force to keep the ship going, by default you share almost all of your onboard data with them. Even though you report to the CO/XO the status, they are the ones who run around fixing things/coming up with complex solutions.

A few things you can't work with

·                     Specialised Tactical Systems - Phasers, Torpedoes, Cannons, Cloak, and shields Tac handle

·                     Specialised Helm Systems - Thrusters, Impulse and propulsion systems

·                     Engineering tasks that need manual operation - replacing/realigning crystals and such

·                     Medical Quarantine systems are off-limits and have their own short term emergency power systems (You can de-activate them but your CO and your CMO will not be happy, and that's likely to be an understatement, do so at your own peril)

·                     Security Brig systems are the same as Med, don't use up that reserve unless you have no choice or are ordered to (and even then be sure to check with Med and Sec if they need the power or not. If they are in use then question the CO's orders)

That leaves all the things you can work with (everything else, not forgetting that you will be kept busy by your CO so keep in plot of the SIM)

·                     Transporter, replicators and holodeck systems (these are all in the same general area)

·                     Main Deflector and Sensor Arrays

·                     Starbase gangways/loading connections and computer's umbilical

·                     Emergency evacuation systems (lifeboats, Captains Yacht)

·                     Shuttlebays, bay doors, shuttlecraft Medical facilities

·                     Using spare cargo bays (mainly done for Medical emergencies/drills)

·                     There are other items not listed here, if you are planning on using any of them please check with your CO in the SIM before doing so. The Ops instructor at the Academy can also be contacted if you need to check something about this with them.

V. TECHNICAL BRIEFING

A. Computer Systems

PLEASE NOTE - All statistics given below are taken from the Galaxy-class vessel. These statistics will vary from vessel to vessel.

1. Main Computer

·                     Cores - At the heart of the Main Computer system are three redundant main processing cores, each of which can handle the vessel's primary operational computing requirements. Each core incorporates miniature subspace field generators, which create a symmetrical field distortion within the Faster-Than-Light (FTL) core elements; this allows optical data to be processed at FTL speeds.

·                     Core Memory - Storage consists of 2,048 dedicated modules, each with 144 isolinear optical storage chips. Each module can store about 630,000 kiloquads. Average dynamic access under LCARS (Library Computer Access and Retrieval System) software control is 4,600 kiloquads per second.

·                     Subprocessors – A network of quadritonic optical subprocessors is distributed throughout the ship's sections, augmenting the main cores. Most of these subprocessors are located near main corridor junctions for easy access. Subprocessors do not employ FTL elements, however the distributed processing network improves overall system response and provides redundancy in emergency situations. Each subprocessor is linked into the optical data network (ODN), and most also have a dedicated optical link to one or more of the main cores. The Bridge of the ship usually have around seven dedicated and about 12 shared subprocessors, which permit operations even in the event of main core failure. These bridge subprocessors are linked to the main cores by means of protected optical conduits, which provide alternate control linkages in the event of a primary optical data network failure. Further redundancy is provided by dedicated short-range radio frequency (RF) links, providing emergency data communications with the bridge. Additional dedicated subprocessors can be installed as needed to support mission-specific operations. All terminals and control panels are linked to a subprocessor or directly into the optical data network. Each active panel is continually polled by LCARS at 30 millisecond intervals so that the local subprocessor and/or the main core is informed of all keyboard or verbal inputs. Each of the polling inquiry is followed by a 42 nanosecond compressed data stream, which provides panel update information. Also, short-range RF data links are available throughout a starship to provide information transmissions to portable and hand held devices such as tricorders and PADDs.

·                     Isolinear Optical Chip - Devices that use single-axis optical crystal layering to reach sub-wavelength switching distances. Onboard nano-processors reduce system access time by managing data independent of LCARS control. When energised by the Main Core's subspace flux, a 35% increase in processing speed is achieved.

This integrated network of computers, subprocessors, and panels forms the "nervous system" of the ship, and permits continuous real time analysis of the ship's operation status. The network is specifically designed to permit independent operation of remaining system elements in the event of a wide variety of partial systems failures.

B. PADDs

The Personal Access Display Device (PADD) is a handheld terminal that provides a convenient alternative to using the shipboard control panels. A PADD maintains links with the starship's Main Computer via a subspace transceiver assembly. The control functions mirror those of any multi-layer panel and it is, theoretically, possible to fly the starship from one of these devices. The three main sizes for SF PADDs are 10.16x5.24x0.95 cm, 20.32x25.41x0.95 cm, and 22.86x30.48x1.27 cm. Their mass ranges from 113.39 grams to 340.19 grams. Their total storage capacity ranges from 15.3 kiloquads to 97.5 kiloquads, depending on the variant. Most PADDs are isolinear-based, although there are bio-neural gel variants available.

C. Sensors

1. Lateral

UCIP Starship exteriors have a number of large sensor arrays comprised of a continuous rack of individual sensor instrument pallets. The array pallets provide microwave feed, ODN (Optical Data Network) links, cryogenic coolant feeds, mechanical mounting points, instrumentation steering servo clusters, and data sub-processor computers.

Pallet Types

·                     Wide-angle EM radiation imaging scanner, quark propulsion counter, Z-range particulate spectrometry sensor

·                     High-energy proton spectrometry cluster, gravimetric distortion mapping scanner

·                     Steerable life-form analysis instrument cluster

·                     Active magnetic interferometry scanner, low-frequency EM flux sensor, localised subspace field stress sensor, parametric subspace field stress sensor, hydrogen-filter subspace flux scanner, linear calibration subspace flux sensor

·                     Variable band optical imaging cluster, virtual aperture graviton flux spectrometers, high-resolution graviton flux spectrometer, very low energy graviton spin polarimeter

·                     Passive imaging gamma interferometry sensor, low-level thermal imaging sensor, fixed angle gamma frequency counter, virtual particle mapping camera

2. Long-Range

The instrument comprising the long-range sensors are probably the most powerful scientific instruments on a UCIP starship. On the majority of ship classes they are located in the engineering hull right behind the main navigational deflector dish.

Primary instruments include

·                     Wide-angle active EM scanner

·                     Narrow angle active EM flux scanner

·                     2.0m gamma ray telescope

·                     Variable frequency EM flux sensor

·                     Life form analysis instrument cluster

·                     Gravimetric distortion scanner

·                     Passive neutrino imaging scanner

·                     Thermal imaging array

In high-resolution mode, sensors have a maximum effective range of around five light years. In medium-to-low resolution mode, the effective range increases to about seventeen light years. It should, however, be noted that a sensor pulse sent at warp 9.9997 would take about ninety minutes to reach its destination and return to the ship when this range is used to cover such distances.

D. Tricorders

The standard tricorder is a portable sensing, computing and data communications device. It contains miniaturised versions of the instruments found to be of most use for both shipboard and away missions. Its capabilities may be enhanced with mission specific peripherals and its many functions are accessible by touch sensitive or voice commands. Note: I have classified the tricorders by generation (using the “mark” system). Mark I was used on Enterprise; Mark II was used by The Original Series. Marks III through VII were used in the TOS movies. TNG used the Mark VIII, DS9 used the Mark IX Tricorders, and VGR used the Mark X. (source: http://www.tricorder.cjb.net/)

  1. Features

      A. Mark VIII Tricorder (TR 580 series)

  The device measures 8.5 x 12 x 3 cm at 353 grams, with a hinged case of micromilled duranium foam. Main electronic components include the primary power loop, subspace communications unit, multiple memory storage units, parallel processing block, emergency dump button, control and display interface (CDI), and an ID touch pad. Power is provided by a rechargeable sarium crystal, which lasts 18 hours, with typical power at 15.48w.

      B. Mark IX Tricorder (Upgraded TR 580 series)

  The device measures 15.81 x 7.62 x 2.84 cm and weighs 298.3 grams. The casing is gamma-strengthened polyduranide. The CDI retains the familiar operator interface and 3.5 x 2.4 cm display screen. The Tricorder power is provided by, a rechargeable sarium-krellide energy cell, which is rated for 36 hours of continuous use with all subsystems active (this time increases with less subsystems online). Typical power level is 16.4w.

C. Mark X Tricorder (TR 590 series)

  The Mark X Tricorder (TR 590 series) is one of the first tricorders to use the bioneural circuitry developed in the mid-24^th Century for improved computing and response times. This devices measures at 13.46 x 7.71 x 2.84 cm, and weighs roughly 303.4 grams. The casing is a reinforced gamma-strengthened polyduranide alloy. The CDI retains the classic 24^th Century display. A rechargeable sarium-krellide energy cell also provides this tricorder’s power.

  2. Data Storage

  A. Mark VIII Tricorder (TR 580 series)

  The data storage sections of the device include fourteen wafers of nickel carbonitrium crystal for 0.73 kiloquads of interim processor data storage, and three built-in isolinear optical chips, each with a capacity of 2.06 kiloquads, for a total of 6.91 kiloquads. The swappable library crystal chips are each formatted to hold 4.5 kiloquads. In Emergency Dump Mode, all memory devices are read in sequence and transmitted, including any library chips in place. In practice, the total time to dump a standard tricorder's memory to a starship can be as long as 0.875 seconds.

  B. Mark IX Tricorder (Upgraded TR 580 series)

  The data storage sections include eight wafers of densified chromo polymer isolinear crystal for a total capacity of 9.12 kiloquads, in addition to the standard library disks of 4.5 kiloquads.

  C. Mark X Tricorder (TR 590 series)

  The data storage sections for this tricorder are all bioneural based. This allows for a greater organization of the data collected and recorded by the tricorder’s sensors. This tricorder makes use of 5 wafers of bioneural disks for a total capacity of 15.6 kiloquads, as well as the standard library disks of 4.5 kiloquads.

E. Life Support Systems

1. Atmospheric system

This system maintains a class M compatible nitrogen-oxygen atmosphere throughout the habitable volume of UCIP starships. Two independent primary atmospheric plenum systems deliver temperature and humidity controlled environmental gases throughout the ship.

A separate reserve system and emergency system provides an additional redundancy. Normal atmospheric values for class M compatible conditions are 26 degrees Celsius, and 45% relative humidity at a pressure of 101 kilopascals. Atmospheric composition is maintained at 78% nitrogen, 21% oxygen and 1% trace gases.

2. Emergency Environmental Support Systems

Emergency systems provide suitable life support for the crew for sufficient periods of time for engineering staff to restore normal function to the primary or reserve system. The contingency atmospheric and power supply system supplements and reserve backup system. It consists of self-contained air supply and power modules located throughout the vessel. These units allow about 30 minutes of atmosphere and lighting in the event of a total failure of all primary and reserve systems. In addition UCIP starships have emergency shelters designed to hold crew members up to 36 hours. They are equipped with emergency breathing gas, water, food and power for 24 hours and at least two emergency pressure garment (EPG) environment suits.

3. Waste Management

UCIP vessels sustain closed ecological systems by recycling waste material. Without this process, ships would be unable to carry sufficient food and water for extended voyages. Material that cannot by directly recycled by mechanical or chemical means is stored for matter synthesis recycling. The waste that can be treated easily is dematerialised into desirable objects. Approximately 5% of all liquid and solid wastes are considered to be hazardous materials under toxicity, reactivity, biohazard or radioactivity standards. Such materials are separated from other waste materials and are immediately diverted to a matter replicator, which converts them to inert carbon particles. This material is then stored for matter replication recycling.

VI. DIAGNOSTICS

When anything happens there's a diagnostic you can run. Even if nothing is happening, run a diagnostic! There are 5 main levels of diagnostic (numbered in reverse order of complexity)

·                     Level 5 Diagnostic - This automated procedure is intended for routine use to verify system performance. Level 5 Diagnostics, which usually require less than 2.5 seconds to complete, are typically performed on most systems at least on a daily basis, and are also performed during crisis situations when time and system resources are carefully managed.

·                     Level 4 Diagnostic - This automated procedure is intended for use whenever trouble is suspected with a given system. This protocol is similar to Level 5, but involves more sophisticated batteries of automated diagnostics. For most systems, Level 4 diagnostics can be performed in less than 30 seconds.

·                     Level 3 Diagnostic - This protocol is similar to Level 1 and 2 diagnostics but involves crew verification of only key mechanics and systems readings. Level 3 diagnostics can be performed in 10 minutes or less.

·                     Level 2 Diagnostic - This refers to a comprehensive system diagnostic protocol, which, like a Level 1, involves extensive automated routines, but requires crew verification of fewer operational elements. This yields a somewhat less reliable system analysis than a Level 1, but is a procedure that can be conducted in less than half the time of the more complex tests.

·                     Level 1 Diagnostic - This refers to the most comprehensive type of system diagnostic, which is usually conducted on ship's systems. Extensive automated diagnostic routines are performed, but a Level 1 diagnostic requires a team of crew members to physically verify operation of system mechanisms and to system readings, rather than depending on the automated programs, thereby guarding against possible malfunctions in self-testing hardware and software. Level 1 diagnostics on major systems can take several hours, and in many cases the subject system must be taken offline for all tests to be performed.

VII. OPERATING MODES

External Support Mode

This is usually the case when your ship is docked at a starbase.

Soft docked means you are maintaining your position in the docking area with the aid of tractor/repulsor. This is not often used in SIMs so unless your CO/XO says otherwise you will be hard docked.

Hard docked means you are physically attached to the facility, walkways, turbolift paths and conduits are made through what is termed as “direct sleeve” or "shirtsleeve access" where gangways and/or turbolift shafts are encased by conduits providing "Electro Plasma System" power, environmental support, SIF power, thermal and gravitational control.  These act as your ships “umbilical” to the station.

While Hard Docked, cold shutdown is permitted on ALL primary and secondary power plants, allowing full maintenance. However, it is preferred that at least one auxiliary fusion generator remain on-line, if possible.  Partial shutdown can be implemented taking for granted that the hard dock is providing for all inhabited portions of the ship.  Again this allows shutdown of systems for maintenance, note the partial, it means those tinkering engineers can only work on one section at a time.

Ventilator fans, air conditioning, thermal control and plumbing must be maintained to areas not under current maintenance.  Gravitational power generation may be discontinued as long as the umbilical provides field energy for synthetic gravity. Cold shut down of SIF, inertial dampers, navigational and tactical deflectors can be permitted as long as the ship is Hard Docked, note that it is preferred that at least one SIF generator remains on hot standby as a safety precaution.

Separated Flight Mode

This mode has to deal with the power reduction caused by ship separation. Most Confederation starships have a saucer separation feature that is primarily used in emergencies. The saucer module disconnects from the rest of the spacecraft. This allows the saucer module, containing most of the crew; to remain in relative safety while the star drive section goes into combat or hazardous situations. The new Prometheus class has a multi-vectored assault mode that allows the ship to separate into three fully functioning sections.

Cruise Mode

This is the usual mode that your ship should be in, sometimes referred to as "normal mode", or when standing down from another mode "returning to normal".  To implement a Minimum staff you will be needed, as will Conn and a command officer (CO or XO), a floating officer will also be present on the bridge, other staff will be present as and when the mission requires them to be.  You should run a level-4 diagnostic as you sit down.

Reduced Power Mode

Usually invoked due to emergency/tactical situations, this is a state of high power management, and low consumption, often implemented alongside red alerts, or if the ship is acting as a Hard Dock and supporting another ship.

Yellow alert

Usually invoked in preparation for a possible crisis situation, it is a shipwide alert and it prepares personnel for a possible red alert. When Yellow Alert sounds you must watch the level 4 diagnostics and report any oddities, and remember to shut down any leisure activities even for civilians unless the CO specifically asks for a silent yellow alert. Also terminate anything that is happening on board the sip that may increase the chance of accident or damage to the crew or the ship. This includes knocking extensive holodeck programs off, and insuring that all of the ships systems are ready to respond to ANY situation. Mission Operations will take his post and run another level 4 on everything and a level 5 on the lifeboats and environmental systems.

Red Alert

Red Alert is invoked during states of emergency that may endanger the vessel or the crew, impending emergencies, or combat situations. This is crunch time, everything is checked and double-checked, and anything can happen and often does!

Blue Alert

Blue Alert is initiated if the ship has this capability, the ship has to make a planetary landing, and can be used for a deck evacuation if necessary. This is one of the times where Ops has to work with Engineering. Blue Alert has in the past been used to announce a deck evacuation. In the event of a deck evacuation, depending on the reason for the evacuation of the deck, Ops may have to do some re-routing of power to the deck or from the deck. For example, if Deck 5 is being evacuated because of an EPS overload, then Ops would try and keep the overload from occurring long enough to get all personnel off the deck and in this situation, working with Engineering to establish forcefields to help with evacuation is necessary. When Blue Alert is initiated for a landing procedure, Ops would re-allocate power to the thrusters and the Inertial Dampening System to make the landing more smooth.

VIII. MISCELLANEOUS:

A. “Pecking Order”

This "Pecking Order," is not to be confused with the Chain of Command as specified by UCIP. This order is listed so you can prioritise and use your resources effectively. Note that the priorities are in a constant change of flux depending on the SIM.

·                     First and foremost is the CO, if he wants to do something then make sure that he can. (Note that this is when he has the bridge, if he's off duty and wants to have fun in the holodeck when you are in Reduced Power Mode YOU CAN REFUSE!)

·                     Secondly is the XO, to the same extent, your XO and CO should act in co-ordination so be aware of them. As above, having "The CONN" is being the person you respond to first.

·                     Thirdly is... well... you! All departments rely on your resource management (the nicer they ask the faster they get to that extent you are who they come to with their requirements, if you are watching power then you can say no to almost anyone! Exceptions being to the person with "The CONN" and Tactical (see notes below)

·                     Engineering - This is your band of helpers, when you can't fix something from where you are sitting these are the trouble shooters and fixers, it is in your best interests to keep these people happy, as, when something is broken, you will be asking these people to fix it.

·                     Tactical - Outside of red alert this person has the same right to your resources as everyone else, however in a Red Alert situation you must be able to give them all they need to do their job! **IMPORTANT** During a Red Alert You must treat give them as much priority as your CO/XO, outside of Red Alert, you are not bound to that.

·                     Everyone Else - SCI - Helm - CMO - and their teams According to their duties, provide them with what they need, if they are on CO/XO orders, then rank them higher on your priorities, other than that you only need to satisfy their needs, you can fulfil their wants at leisure.

B. Units of Measure

The following is a brief review of some of the international-system units commonly used and some used in Star Trek. If you have problems with any of these you can find conversion tables and calculators readily on the Internet. These tables are a good way to keep track of your “measurements.”

Metric Prefixes (taken from College Physics by Jerry D. Wilson)