|
Duties and
Responsibilities
Coordinating shift rotations
with department managers All department heads enter their rosters into LCARS {Library Computer Access and Retrieval System}. Once the information is in the system, OPS can then coordinate with the departments on the allocation of personnel.
**NOTE:THE OPS OFFICER IS NOT IN CONTROL OF SHIFT ** **ROSTERS. The OPS officer DOES NOT control personnel** ** he or she ALLOCATES the information stored on LCARS** **of the personnel. **
************************************************** Shifts are as follows: Ranking personnel and
assigning away teams Assign Crew Quarters When new personnel are
assigned to a Starship or Station, they are assigned living quarters. This
responsibility also falls to Operations. The OPS officer checks LCARS to
see what quarters are available, how suitable the quarters would be for
the new crew member in association
with their job and weather or not the crew member has a family or not.
Also, coordinating with engineering to develop specialized quarters for
those with handicaps, different species requiring special atmospheres
and/or requiring special instrumentation. Many shipboard operations
involve scheduling of 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 a crucial importance because of the wide range of
unpredictable situations with which a starship must deal.
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 Alert status of the ship. During crisis situations and
Reduces Power Mode operations, OPS is responsible for supervision of power
allocation in coordination with the Engineering department. Load
scheduling on nonessential power usage in such situations is based on
spacecraft survival factors and mission priorities. Power allocation and rerouting power during emergencies
Scheduling usage of recreational facilities The holodeck and other recreational facilities are vital to the emotional well being of the crew, especially on long missions without a port of call. Operations is responsible for overseeing the scheduling and appropriate use of these facilities, especially if the occupants are guests and/or civilians. Some priorities in schedule are used. For instance, the CO and XO have first priority followed by the senior staff in regard to their rank. This is due to the idea that because of their duties, relaxation time is scarce and any time they have available should be given to them. After the senior and command
staff, all other personnel are treated on a first come first served basis
regardless of rank or position. Except when ordered by the medical staff,
any ‘prescriptions’ for the use of the recreational facilities will always
be given top priority even over the senior staff. {Note: Due to the way that
ACTD is set up…these tasks by the Mission OPS is normally done by the OPS
officer or an OPS NPC}
Traffic Control Coordinating the shuttle bays is a process that puts the OPS officer and the FCO working together to make sure things are handled properly. While the FCO is responsible for shuttles the OPS officer is responsible for communicating with incoming and outgoing shuttles to make sure there are no accidents. o Starship protocol leaving
and docking at a station and/or docking rings
Every Starbase and station has a supply depot. Plus there are supply runs continuously throughout the quadrant. Anything that is Starfleet issued and not replicatable can be obtained from these supply depots and supply drops. One other Starfleet resource is other ships. Many times extra parts can be found on a sister ship. Every OPS officer should be aware of who is in the area and where they are. Disasters can often be prevented by the quick procurement of parts.
There are many items that are required for a ship or station due to the diverse amount of species. Although many of these items can be found in Starfleet stores…personal icons, exotic foods and even some custom furniture may need to be gotten from elsewhere. There are several resources available. Civilian shops along the promenades of most stations and starbases. Even on various planets. But the biggest resource is the independent trader. A good OPS will build a network of traders with their territory. Although latinum is the currency most used in the quadrant….there is a large bartering system in place. Older OPS often mentor newer OPS in the ways and means of bartering, although Starfleet ‘unofficially’ looks for those qualities in their OPS candidates. One thing that a good OPS officer must be aware of is the different bartering systems in different areas. What may be valuable in one sector may be common place in another. OPS officers are in constant communication with each other so that these things may be shared.
Any communications coming in or going out passes through the OPS station. Although most of it is handled automatically there are many instances where a message is flagged or needs special handling. All traffic going to and from the bridge must be handled directly through the Operations Console. Certain criteria can be set on each individual ship or station to scan for anything within any communication leaving or arriving, regardless of who sent it and to where. This must only be done at the direct order of the Captain or the Executive Officer and then must be able to be justified to Starfleet Command at a later date. This is due to Starfleet’s profound respect for individual rights and privacy. The proper communication protocol is taught in the academy to all cadets (ie: ACTD training sessions before the cadets first assignment).
The OPS department is responsible for the maintenance and usage of all of the transporters. Including the ones in all of the cargo bays. Each transporter room has a transporter chief on duty at all times. Regularly scheduled maintenance is performed and each circuit is meticulously checked and double checked. Tests are done at the beginning of each shift. OPS is also responsible for equipping away teams with pattern enhancers if there is a slight chance that they will be needed. o Maintaining transporter lock From the bridge it is the OPS
responsibilities to maintain a transporter lock on whoever they are
assigned to. In the case of multiple away team members scattered
throughout different areas...the OPS officer will divvy up the personnel
among the transporter rooms and even the cargo bay transporters if needed.
The computers on board a ship or station are immense, with the core extending down through multiple decks. Next to the crew, the computer is probably the most important single operational element. It could be and has been described as being the central nervous system of the ship or station. It is responsible in some way for the operation of virtually every other system. The maintenance and upgrading of this system is an immense task and one that falls under the responsibilities of the OPS department. Extensive programming knowledge and skills are required and the ability to quickly diagnose and correct any problems are mandatory. Maintenance The main interface used by
virtually every crewmember is provided by the Library Computer Access and
Retrieval System software (LCARS). LCARS provides both keyboard and vocal
interface ability. It is composed of highly artificial intelligence
routines. These routines have the ability to run diagnostics on itself to
check for anomalies, but the output must always be reviewed by the OPS
officer before being signed off as operating within standard parameters.
Periodically these routines need to be upgraded or additions and
enhancements added. This is done by the OPS officer. No one except the OPS
officer, the XO and the CO have access to the central core operating
system.
Whenever a system has crashed a Level 1 diagnostic will be run on that system. And whenever it is feasible a level 1 is run on the entire core and network. This is usually done when docked and the major systems are run from the station or port through an umbilical cord thus ensuring that life support, power and engineering are not interrupted in anyway.
Isolinear optical chips are a
sophisticated information storage and processing device that can be used
for both data storage and processing. Composed of linear memory crystal
material, these isolinear chips are often mounted in wall racks permitting
the computer access to anywhere from a dozen up to hundreds of chips at
one time. These must be regularly check for both physical or data damage.
These chips can be found in almost every unit and system. User Access and Control Interfaces User Accounts As part of their computer administrator duties, OPS is responsible for creating user accounts for each new crewmember so that they have connectivity to LCARS and their own personal files. These accounts are based on the following criteria: Their security clearance which is established by Starfleet Headquarters. Their job requirements. Their rank. Whether their assignment is permanent or temporary. And what their current access level is, which again is established by Starfleet Headquarters. All of this information will be provided in the personnel database which is kept in a secured section of the computer. OPS cannot change or set a person's clearance and/or access level. That must be done through Starfleet Headquarters. All crewmembers are given at least the most basic accounts so as to allow them to enter their personal logs. Access to all Starfleet
computer systems is highly regulated. A standard set of authorization
codes have been programmed in to the starboard and engineering computer
cores of all ships in order to stop any undesired access to the systems.
The codes are as follows: ALPHA - TWO Unlimited access to all ship's records, systems, commands and computers. ALPHA - ONE Unlimited access to all ship's records, systems and computers. No access to ship localized command functions. BETA - TWO Unlimited access to all ship's records, systems and computers. Limited access to command functions (except if stated otherwise by Commanding Officer). BETA - ONE Unlimited access to all ship's records, and computers. Limited access to command functions (except if stated otherwise by Commanding Officer). Access to ship systems is limited to duty related functions. DELTA - TWO Limited access to all ship's records, systems, commands and computers. Access Limited to duty related functions. DELTA - ONE Limited access to all ship's records, and computers. Access limited to job related functions. The following codes have been assigned to: Commanding Officer -------------------------------------- ALPHA-TWO Executive Officer ----------------------------------------- ALPHA-TWO Operations Officer ---------------------------------------- ALPHA-ONE Chief Medical Officer ------------------------------------ BETA-ONE Chief Engineering Officer -------------------------------- BETA-TWO Chief Tactical Officer ------------------------------------- BETA-ONE Flight Control Officer ------------------------------------- BETA-ONE Counselor ------------------------------------------------ BETA-TWO The Commanding Officer reserves the privilege of permitting limited access to unspecified section of the ship to any personnel whose functions, in the eyes of the CO, require it. This section also deals with access levels. Access to all Starfleet data is highly regulated. A standard set of access levels have been programmed in to the starboard and engineering computer cores of all ships in order to stop any undesired access to confidential data. The following access levels have been assigned to: Admirals and Commodores ----------------------------------------- Level 5 Captains, Commanders and certain specific personnel (duty related) -------------------------------------------------------- Level 4 Lieutenants, Lt(jg), and certain specific personnel (duty related) --------------------------------------------------------- Level 3 All personnel in operational duties --------------------------------- Level 2 All personnel and Civilians in Starfleet service ------------------ Level 1
Troubleshooting Level-4 memory fragmentation: Serious cascading memory degradation in a sophisticated computer program...such as the EMH or a holodeck program |
|