Intelligence Officer Simming Guide

From 118Wiki
Jump to navigation Jump to search
Header-intel.png






Edit this nav

General Parameters & Requirements

  • Main Responsibility: The gathering of information on advarsaries of Starfleet, or in regards to the current mission
  • Other Responsibilities: Should be able to perform any duty assigned, and must have at least minimal skill in all other key areas of operation (helm, comm, ops, etc.)
  • Intelligence operatives duties are primarily to engage in intel gathering activites regarding any mission they be assigned to. Using personal contacts, espionage, stealth, subterfuge or negotiation are some of the ways this can be accomplished. Although violence is sometimes unavoidable, it is not stricken from means of gathering intel. It should be used as a last resort.
  • Intelligence officers are generally required to obtain classified and top secret clearances upon their appointment to a vessel. Orders from Starfleet Intelligence will often come with a clearance level, and the appropriate means must be secured.
  • Close knit cooperation with an Operative's CO must be taken into account, as SFI DOES NOT superceed the Captain's authority. Due regard should be given to orders from SFI, and conversely, orders that may violate Starfleet Regulations should be reported to the proper channels.
  • Although not required, a secure workspace should be provided to an Operative aboard a vessel (i.e and Intel lab)

Requirements

  • Permission first, always
  • One should be holding the rank of Lt for a minimum duration
  • Unless the ship has an active Intelligence Branch, it is considered a secondary assignment, and not the character’s primary.
  • There should not be a reference to Section 31 (see Sect.31 below)
  • The officer first answers to the ship’s CO, then SFI (not the other way around).
  • Sim appropriately to group participation
  • Applies equally to NPCs (or PNPCs)
  • The unwritten rule applies: if as an NPC, the character holds an equal rank to the player's primary or below.


Before the Mission

During the Mission

  • All matters pertaining to intelligence, such as species that are on the watch list, or encounters with thereof, should be documented with the proper coding and security to be reported to SFI. Information sharing with your CO is permitted, and is often at the discretion of the operative. A close knit line of communication between operatives and their CO's is crucial to a smooth and working relationship aboard a vessel.
  • All actions that may include force or use of stealth should be a joint effort between the operative and the CO, and should also include a member from Security when the discussion arises. Making sure our operations are conducted ethically from a Starfleet perspective is just one way to cut down on the need for "plausible deniability".
    • Any action that may be percieved as unauthorized can be punished by Starfleet Disciplinary codes, and plausible deniability may be rendered on the offending operative.

After the Mission

  • Official debrief reports should be filed to BLACKNET located in the Intelligence Forums

Away Missions

  • The Operative may typically act as a security or tactical officer until their expertise is needed. Before entering into a solo operation (espionage), the operative should seek approval from his XO or CO before embarking.
    • Is skilled in many forms of combat and stealth.

A General Hierarchy

  1. Intelligence Officer
  2. Division Head
  3. Deputy Chief
  4. Chief

The Section 31 Factor

Canon source divides Section 31 from SFI, although there is an ongoing debate whether the two groups are separate or Sect.31 falls into a section of the branch SFI can officially claim “plausible deniability” on some of the nastier aspects of Field operatives.

In the UFOP, Section 31 has never been used. It’s proper section is Field Operations and should not be treated any differently.


Sources

Starfleet Intelligence