Guy Hunt
| USS Victory |
|---|
 |
| Guy Hunt |
|
Personal Logs · Medical Records
|
FAMILY:
Father: Commander Perry Martin Hunt, Program Director for Shuttle Craft Development, Mar's Plant 12-1 A
Mother: Captain Helaina Martha "Davenport" Hunt, M.D., Chief Surgeon Mar's General Hospital.
Older Brother: Lt. Commander Jessie Hunt, M.D., CMO USS Tanner, Olympic Class
Youngest Brother: Perry Guy Hunt, Medical Student at John Hopkins
FRIENDS FROM THE DIPLOMATIC CORE:
Hunts friends and colleagues form his years in the Diplomatic Core
CHRONOLOGICAL HISTORY:
Guy Perry Hunt was born on the Greece Island of Crete. His mother was stationed there at the Star Fleet Medical Operations Center for Advanced Surgery. In Guy's young life he lived on 3 starships 2 moons and an Astrid station. In Guys adult life he has lived on 1 starship and 2 planets. Guy is an avid collector of artifacts to include his passion, ancient hand held weapons. His grandparent live on Earth's Moon were they have the largest Coffee Farm in the solar system. Guy never travels with out a case of his grandparent’s coffee beans, grander and a French press.
Guy Received a BS degree in Advanced Tech from M.I.T. A Masters degree from New York State in Diplomatic Law. Guy Mother urged him to enter Medical School. Guy became a Med student at John Hopkins. In his 3rd year Guy got a job offer from the Federation Diplomatic Core.
At the Age of 28 Hunt became the aid to the Earth Ambassador General. After two years became the Chief of Staff for the Star Ship Operations, a 50 year old Excelsior Class-Refit, USS Providence. Hunt Served on the Providence for 3 years aiding the Ambassador in all Diplomatic Duty's and 3 months on Romulus as a Plenipotentiary. While on the Providence Hunt went on 67 Federation Mission and worked on many agreements after 1st Contacts had been made. After Ambassador Hasten was killed when his shuttle was the target of an attack. Hunt entered Star Fleet with a degree in Intel and a minor in Strategic Operations. Hunt was also selected for Flight School in his 3rd year at the Academy. In Hunts 4th year he went to the Advanced Flight Academy Mars. While at the Academy Hunt meet his 1st love David Harrigan, a Pilot and flight School Instructor. David was the main driving force to why Hunt went to Flight school. Guy did not want to hold a station at the helm. David and Guy became very close while Guy was at the Academy. Guy wanted a deep-sace duty posting and David wanted him to stay on Earth or Mars, this conflict resulted in the two’s break up. Hunt was Selected for Duty aboard the USS Resolution by Commander Toni Turner. After a few Mission Lt. Hunt was Transferd to the USS Independence NX-1776-A as its Chief of Operations
Guy is a lover of classical music, his mother had him in music school at the age three. Guy attended the Julliard School of Music. He first learned the Piano and them ventured off to the Piccolo, Flute, Basset Clarinet and his favorite the Violin. Guy later took up the Pipe Organ, and played at his Parents Anglican Church for a year, until leaving for the Diplomatic Core. When transferred to the USS Independence, Guy was very happy to find that there are two Pipe organs on board, on in the Chapel and the other in the Theater. After long stressful days on duty you can find guy in ether the one that is not being used playing the Organ. Guy also holds the USS Independence Symphony practice every Thursday night. Guy plays the Violin mostly in the Symphony Concerts, but will also play the pipe organ from time to time. Guy was the music Director for the Phantom of the Opera play the was held on the Independence, also playing the Organ for the play.
2370 Dominion Contact Guy was 15 Years Old
2375 Breen Attack on Earth Guy was 20 Years Old
Current Post:
Helm-Communications- Operations
Main Responsibilities: Piloting and navigation of the vessel, scheduling of all major resources between departments eg Deflector dish, reserving of holodecks etc, co-ordination of away missions, monitoring of the ships communications
Other Responsibilities: Navigation references/course plotting, supervision of automatic flight operations, manual flight operations, position verification, and bridge liaison to engineering department. Sending and receiving distress signals, locating important people on or off the ship, sending and receiving: Ship to ground, ship to ship, and ship to StarBase communications.
The HCO Officer is responsible for all flight control operations of the ship. He/she is also responsible for co-ordinating ship activities in such a manner so as not to overload or oversubscribe any particular system/resource. The HCO Officer also monitors the away team(s) status when not onboard the ship. The HCO Officer also handles all communications both to and from the ship.
Notes: Even though most of the functions in flight are automated, a human officer is needed to oversee these operations and sometimes, make changes. During impulse powered flight, the HCO Officer is responsible for monitoring inertial dampening systems and relativistic effects. In the event of overload in a specific flight operation, the computer will request a change in the manoeuvre. The HCO Officer must then bring the plans into the inertial dampening perimeters for safety. During alert situations the HCO Officer is permitted to specify manoeuvres that are possibly dangerous to the crew of spacecraft.
Many shipboard operations involve scheduling resources or hardware (such as power or the use of sensors) that affect a number of departments. In many such cases, it is common for various operations to present conflicting requirements. It is the responsibility of the Operations Management Officer (normally referred to as the Operations Manager or Ops) to coordinate such activities so that mission goals are not jeopardized. Having a crew member in this decision-making loop is or crucial importance because of the wide range of unpredictable situations with which a starship must deal.
The Ops panels present the Operations Manager with a continually updated list of current major shipboard activities. This list permits Ops to set priorities and allocate resources among current operations. This is especially critical in cases where two or more requests require the use of the same equipment, entail mutually exclusive mission profiles, or involve some unusual safety or tactical considerations.
An example might be a situation where the Stellar Physics department is conducting an experiment using the lateral sensor array to study a nearby binary star. Simultaneously, part of the same array is being time-shared with a long-range cometary population survey. A request from the bridge for a priority scan of a planetary system might jeopardize both studies unless Ops authorizes a minor change in attitude, permitting the Stellar Physics observations to use the upper sensor array. Alternately, Ops may weigh the option of placing one of the ongoing studies on a lower priority to provide the bridge with immediate use of the lateral array.
Most routine scheduling and resource allocation is done automatically by the Ops program. This frees the Operations Manager from routine activity, leaving him/her able to concentrate on decisions beyond the scope of the artificial intelligence software. The level of these decision filter programs can be set by the Operations Manager, and also varies with the current Alert status of the ship.
In cases where priorities are ambiguous or where specific Ops approval is required, the panels will display a menu of the most probable options for action. In virtually all cases, the Operations Manager also has the ability to input choices beyond those presented by the action menus. This is important because it is impossible for mission planners to anticipate every possible situation. Action menus may be displayed for any current activity even those which would normally be handled automatically upon keyboard request from Ops.
During crisis situations and Reduced Power Mode operations, Ops is responsible for supervision of power allocation in coordination with the Engineering department. Load shedding of nonessential power usage in such situations is based on spacecraft survival factors and mission priorities.
The Operations Manager is also responsible for providing general status information to the main computer, which is then made available to all departments and personnel. Ops routes specific information to specific departments to inform them of anticipated changes and requirements that may affect their operations.
An example is a scenario where an Away Team is to be sent on a mission to a planetary surface. Typical Ops responsibilities might include
Notification of Away Team personnel of the assignment and providing said personnel with mission objective information. When Away Team personnel are drawn from operational departments, Ops will sometimes coordinate to provide cross-trained replacement personnel from other departments.
Coordination with Mission Ops for assignment of comm relay frequencies and preparations to monitor Away Team tricorder telemetry.
Notification for issuance of tricorders, phasers, environmental gear, and other mission specific equipment.
Assignment of personnel transporter room to handle transport operations, as well as the assignment of a transporter chief to the mission. If available, Ops will also provide transport coordinates to the transporter chief.
Notification of Engineering to prepare for power allocation for transporter operations, as well as deflector shield shutdown, if necessary.
Such notifications are generally accomplished automatically without the need for active intervention by Ops. However, because preprogrammed functions cannot be expected to anticipate all possible situations, Ops is responsible for monitoring all such coordination activity and for taking additional action as necessary. Such flexibility is particularly important during alert and crisis scenarios, during which unpredictable and unplanned conditions must frequently be dealt with.
Guy Perry Hunt's Current Posting
Career Overview
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Awards Received:
Award History
| ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
MISSION HISTORY:
Missions on U.S.S. Resolution
Missions on U.S.S. Independence
- Rescue of Minors
- Midway Incident
- Sector 12
Missions on USS Ronin
- Too Little, too Layte
Missions at M.I.T.
- Teaching Advanced Technology
- Vice Dean of Technology, Star Fleet Adviser
Mission on USS Eagle
- None, Served on Victory
Missions on U.S.S Victory
- The Eagle is Located
- Mining Incident
- Remote Control
- Transport One Away Mission
- Empire Falling
Guy's Photo's:
NPC Listing · USS Victory Crew Manifest · Crew History
| |||||||||||||||||||||||||||||||||||||
