PRISM

From ST_ACTD Wiki

Jump to: navigation, search

Image:PrismLogoSmall.jpg

PRISM is the shortened name for the Project:Prism, or the 177th Special Forces Group, assigned to Starfleet Special Operations. PRISM operates as the counterintelligence and counterterrorism arm of SFSO.

Contents

History

They operate by sea, air, and deep space, appearing from the night sky, striking their targets with deadly efficiency, then vanishing into the darkness from which they emerged.

In 2362, Starfleet felt that one of the best ways of executing Federation policy in border worlds, along with preventing full-scale war between the Federation and the Cardassian government, was the formation of a new organization that was dubbed Special Operations, a designation derived from Starfleet Intelligence, whose operational teams in the field were given the same name in 2364. Starfleet allocated personnel slots for the unit and assigned it to New Berlin, Luna. In the spring of 2368, Special Operations were placed under the command of Commander Johnathan Wolfe, who went to New Berlin to choose a suitable location for a Psychological Operations/Special Operations center. He chose a remote area of the post known as Monolith Hill, not knowing that within ten years it would become one of the busiest places in the Army.

He then went about assembling a cadre of officers and NCOs who would serve as the hard-core foundation of the new unit, and who would act as a training staff to perpetuate and flesh out the fledgling organization. Wolfe didn't want raw recruits. He wanted the best troops in Starfleet, and he got them: former Starfleet Intel officers, Security troops, ex-undercover troops and combat veterans of the Maquis and Tzenkethi Wars. They were an unusual lot, a motivated bunch, men who were looking for new challenges to conquer - the more arduous the better. Virtually all spoke at least two languages, had at least a Petty Officer’s rank, and were trained in infantry and covert operations. They were all volunteers willing to work behind enemy lines, in civilian clothes if necessary.

That last item was no small matter. If caught operating in civilian clothes, a Starfleet officer was no longer protected by the New Geneva Convention and would more than likely be shot on sight if captured. But these first volunteers didn't worry about the risks: they were long accustomed to living with anger. Many of them had come straight from the Tzenkethi War, where Starfleet had taken frightening losses in nearly every engagement.

After months of intense preparation, Wolfe’s unit was finally activated June 19, 2369, at New Berlin. It was designated the 1st Special Forces Group, with Wolfe as commander. On the day of activation, the total strength of the group was ten individuals - Wolfe, one warrant officer, and eight enlisted men. That was soon to change.

Within months, the first volunteers reported to the 1st Group by the hundreds as they completed the initial phase of their Special Forces training. As soon as the 1st Group became large enough, Wolfe began training his troops in the most advanced techniques of unconventional warfare. As defined by Starfleet, the main mission of Wolfe's unit was "to infiltrate by land, sea, air, or space, deep into enemy-occupied territory and organize the resistance/guerrilla potential to conduct Special Forces operations, with emphasis on guerrilla warfare." But there were secondary missions as well.

In 2369, two Starfleet Special Operations teams, designation Project: Prism, were established. Called Prism for short, the teams drew their name from devices used to refract multitudes of individual colors from one whole. Commissioned to operate up behind enemy lines, they would act as commandos whose functions were to gather intelligence, raid, ambush, capture prisoners, and create havoc in enemy territory. These two Teams, Prism Team One and Prism Team Two were the end product of decades of political maneuvering and hard lessons learned on the field of battle.

The first Prism units came to being in May of 2370, when twenty Starfleet officers, ranging in rank from Lieutenant to Commander, were formed into the two static Prism teams. In most of their operations, they were limited to direct support of defensive forces against Cardassian, and later Dominion, attacks in the Beta and Alpha quadrants. Later a few of these men and women served with guerrilla units behind enemy lines on Betazed and other occupied worlds, and many more were blended in with the Klingon Special Forces and Romulan Tal Shiar involved in the counter-intelligence and terrorism campaigns against the Dominion in Alliance space. About a year after the formation of the Prism One and Prism Two, the first Starfleet Special Operations Volunteer Teams were formed. These units are generally considered the direct ancestors of the original Starfleet Prism teams.

After less than a year and a half together as a full Special Forces group, Wolfe's men proved to the Army's satisfaction that they had mastered the skills of their new trade. So, in response to growing tensions along the Cardassian/Federation border, half of the 1st Special Forces Group was permanently deployed to Starbase 375. The other half remained at New Berlin, where they were redesignated as the 177th Special Forces Group.

The split of the 1st and the 177th was the first sign that the Special Forces had established themselves as an essential part of the Starfleet's basic structure. For the rest of the decade, Special Forces would grow slowly but consistently into a formidable organization. On April 1, 2373, the 177th was transferred to the Galaxy Class USS Olympus along with a promotion for Commander Wolfe to the rank of Admiral and reassigned as Deputy Director of Starfleet Special Operations. In growing response to fears of counter-operations conducted by Cardassian and Dominion forces, the 177th’s primary goal was no longer deep penetration and guerrilla warfare, but became counterinsurgency and counterterrorism tactics and placed directly under the command of Admiral Wolfe. A highly mobile force of over 2000 people, the 177th, known by its less formal title of Prism, is Starfleet’s answer to terrorist threats and a premier counter-intelligence force.

In preparation for the invasion and Operation: Return, Prism teams joined frontline starships and facilities. These units scouted and collected intelligence from the Bajor system so the Allied invasion could proceed as smoothly as possible. During the invasion these units were hampered by heavy casualties, but still were able to complete the intelligence gathering. Some of the braver ones even continued inland with the ground troops to help secure the liberation of Bajor.

The static Prism teams were reconstituted shortly before 2374, and participated in Operation Whirlwind in November of 2375 (the liberation of Betazed), and in other operations in Dominion/Cardassian space during the war. They included deep-penetration raids, intelligence missions and counterinsurgency operations. It was a tall order, one which demanded a commitment to professionalism and excellence perhaps unparalleled in Starfleet military history. But Wolfe's men were up to the challenge.

On the home front, Prism teams were being created to assist in counter-intelligence and counter-terrorism activities. These teams participated in the strategy of "active resistance", by plugging Intelligence leaks and keeping major locations within the Federation secure from enemy activities. These teams were much greater in size than their frontline Prism teams. These units often contained more than 20 men and women. These teams helped in almost every major counter-intelligence and counter-terrorism operation after the retaking of the Tarawa System.

After the end of the Dominion War, the Prism units were drastically reduced in size and their role became increasingly diminished. They served in the clean-up and restabilization of the Cardassian infrastructure. The Prism units were also used as guerillas, sent on commando missions in possible occupied Starbases and planet-side facilities.

Even as you read this, Prism teams are quietly conducting their missions in systems all over the Federation. The Prism operators rarely receive any formal recognition for these "quiet" missions. Yet they continue to deploy, and train to deploy, for arduous and isolated missions, demonstrating that they are truly "the quiet professionals."

In 2377, President Jaresh Inyo, realizing that guerilla warfare was the battle of the future, ordered Starfleet and the Federation Council to increase funding and allocation of resources to Prism. These two teams, One and Two - still in active service - were the first in a long line of teams to come. Many Prism officers started out by serving advisory roles to the Alliance forces in Klingon space. Serving with Klingon Special Forces is where Prism teams learned and perfected their tactics and they became they finest fighting force in the Federation.

In 2379, another static permanent team was formed, under the codename Shughart. Shughart was assigned to the Defiant Class transport vessel USS Rodger Young. The Rodger Young and Shughart have faced numerous challenges, including the attempted Romulan invasion of 2381-2382.

In response to the Nacandarian peace initative of 2380, the USS Olympus was recalled to Earth orbit to assist in overseeing general security measures for the peace talks. The Olympus and Prism were caught off-guard when the Nacandarians instead captured the Federation President, returning to their own space with him. The Olympus was destroyed in the battle above Earth, with minimal loss of life. Shamed by the unpreparedness, Admiral Johnathan Wolfe stepped aside from managing Prism after twelve years. His replacement was Team One's Commanding Officer, Commander Timothy Richmond.

Richmond was promoted to the rank of Admiral, while his former Executive Officer, Commander Haru Haruko was tapped to take command of Shughart. Richmond's first task was to replace Prism's mobile headquarters. He selected the under construction Nebula Class USS T'Khut. After providing the construction corps with updated specifications, the T'Khut's completion was expedited and she entered service in 2381.

ACTD History

PRISM began in the Chat Division under the command of Steve Mallory and Mark Tucker with PRISM Alpha in January of 1999. Chat PRISM teams are unique in many ways. Players apply to participate in a PRISM mission, and participate with a current regular character in addition to their usual weekly ship or station missions.

In March of 2003, Mark Tucker retired from ST:ACTD, and the then-Game Manager James Young re-hired Steve Mallory to take overall control of PRISM along with Christopher Dickinson to manage the Chat Division teams.

Following the boom into other venues of role playing, it was decided to expand PRISM to those other opportunities. In April of 2003, a trial run of PRISM, codenamed Janus launched in the PBEM Division. Following Janus's successful run, PRISM Shughart opened in the division in November 2003, as part of the Tenth Fleet. Under the command of Steve Mallory, Shughart was different from the Chat teams in that, due to the nature of the PBEM Division, Shughart would be a static team, with assignments being indefinite. PRISM Shughart started out with an 'NC-17' rating, before being dropped to 'R', then back to 'NC-17' in February of 2004.

In March of 2004, the Chat team regulations were loosened to allow players who had already participated once to apply for a second run, with preference still being given to those who did not have the opporunity yet. This opportunity was first offered for the PRISM Omicron run, which began in April of the same year.

A game-wide decision in July of 2004 made all of ST:ACTD PG rated, to be effective in August. After having doggidly fighting for his higher rating, Steve Mallory decided to resign from PRISM, and ST:ACTD as a whole. Christopher Dickinson was tapped to take over all control of PRISM, including becoming the Ship Manager for Shughart. Many members of Shughart decided to follow Steve's example, and the team size shrank considerably. New members, however, discovered the call of duty that is PRISM Special Operations, and joined. PRISM has been blessed with a number of highly creative players.

A discussion in mid-2005 led to the idea of a name change for Shughart, and with the new year of 2006, PRISM unveiled the name of Vanguard. A vanguard is the foremost position in an army or fleet advancing into battle, a fitting name for the highly trained intelligence operatives.

Also in 2005, the Newsfleet Division Manager, Brian Frederickson, approached Christopher regarding opening a PRISM vessel in the Newsfleet Division. However, this idea did not come to full fruition until March of 2006. Brian and Chris tapped long-time Newsfleet Ship Manager Mike Yan to take the reigns of PRISM Eternity for this trial run.

Positions

Commanding Officer (CO)

[Any Department] Leads the Prism Team. First in the chain of command, and must hold a rank of AT LEAST Lieutenant Commander. The CO is hand-picked by the SM. Players may not apply for this position. Can be from any department within Starfleet, but must have held the position of Department head.

Executive Officer (XO)

[Any Department] Assists team leader. Second in command and must hold a rank of AT LEAST Lieutenant. The XO is hand-picked by the CO and the SM. Players may not apply for this position. Can be from any department in Starfleet.

Combat Pilot (CP)

[Flight Control Officer] The pilot is the squadron's transportation specialist. Pilots are trained in the operations of most vessels, fighters and starships. The pilot's main duties are course plotting/helm control, defensive perimeter maintenance, and team transportation.

  • Course Plotting/Helm Control - The pilot is responsible for plotting the best route to a destination. As such, the pilot is expected to keep up-to-date on regional starcharts. Furthermore, routine attitudinal changes are the pilot's responsibility.
  • Defensive Perimeter Maintenance - While en route to a destination, the pilot schedules and oversees fighter escort for a transport vessel. Defensive perimeter only applies to space flight.
  • Squadron Transportation - The pilot will fly any shuttle or drop-ship employed as a means of transportation for the Team. Furthermore, the Combat Pilot will also operate any ground transportation.

Logistics Officer (LO)

[Operations/Science] The Logistics Officer oversees the procurement, maintenance, and transportation of materials, personnel, and facilities for the team. Logistics also handles the tactical details of an operation. This is similar to the OPS officer on a starship, and many LO officers were once OPS Officers.

  • Procurement - The LO monitors the use and distribution of all materials, personnel, and facilities for the squadron. This includes re-supply efforts for extended missions. Prior to a mission, the logistics officer will outfit the team with the proper equipment.
  • Maintenance - Logistics will work with technicians to assure all stocks are in satisfactory condition. Repair efforts will be coordinated with the Engineer.
  • Transportation - If need be, the LO will organize transportation for special gear needed on an unusual assignment. Transportation of this nature should be cleared with the ship's pilot.

Assault Specialist (AS)

aka Assault Officer (AO)

[Tactical/Security] The AS (or AO) is an expert in combat, security, demolitions, and battlefield tactics.

  • Combat - The AS is an expert in both hand to hand and ranged combat. Furthermore, the Assault Specialist is familiar with the more exotic types of weaponry used by the Klingons, Romulans, Cardassians, and other galactic powers.
  • Security - The AS handles security on the base vessel and planet-side missions. Boarding parties, repelling and leading, are also the AS's territory.
  • Demolitions - Some instances may require the use of explosive devices. The AS is proficient in most kinds of explosive/demolition material.

Intelligence Officer (IO)

[Tactical/Security/Science] The Intelligence Officer is an expert in espionage and counter-espionage. Intelligence personnel are typically well-trained in covert operations, security systems, computer technology and communications. While an Intelligence specialist is an expert in undercover activities they are by no means "undetectable." Many a spy have been captured and executed. Duties include information acquisition and target infiltration.

  • Information Acquisition - The IO is responsible for obtaining information about a target’s strengths, weaknesses and overall abilities. The IO may lead a covert mission to observe a particular installation or to procure the technical schematics of a new super weapon. On the other hand, the IO may help the CE with their extensive computer skills to "hack" the needed information.
  • Target Infiltration - On occasion, a team may need someone "on the inside" of an organization or facility. The Intelligence specialist is an excellent choice for undercover missions. Furthermore, the IO may offer recommendations to the Commanding Officer regarding various covert operations.

Strategic Officer (SO)

[Tactical/Security] The SO's primary function is coordinate the teams movements with other intelligence teams or Starships in the area. It is the SO's job to plan the overall entry into an area, and the teams extraction route. As the position's name suggests, they are responsible for the overall strategies done by the team.

  • Communication - As the resident strategic specialist, the SO should keep appraised of communication activity in a region. Not only does the SO listen for communication from "hostiles," but also for distress calls and the like.
  • Battlefield Tactics - The SO will offer suggestions to the Commanding Officer in the tactics area.

Combat Engineer (CE)

[Engineering] The Combat Engineer provides technical guidance and assistance in several areas. Primary duties include ship maintenance, research/development and miscellaneous technical support. These characters are typically taken from Engineering Departments.

  • Ship Maintenance - The CE is responsible for the mechanical/technical upkeep of the teams equipment when on assignment. This includes both routine mechanical upkeep and damage control.
  • Research and Development - On occasion, the CE may need to develop a new device to assist the Team. A new shield booster, fire suppression device, computer sub-routine, or weapon my mean the difference between success and failure of a mission. All research and development must be approved by the SM prior to implementation. Furthermore, all new devices must be appropriate to the Star Trek megaverse.
  • Misc. Technical Support - Examples of misc. technical support include electronic warfare/countermeasures, general upkeep of arms, etc.

Combat Medic (CM)

[Medical] The squadron medic handles all issues of a medical nature including environmental precautions, general medical practice, and battlefield aid.

  • Environmental Precautions - The Medic will research foreign areas and inoculate the crew or warn them of potential biomedical/biochemical hazards.
  • General Medical Practice - The Medic is responsible for the general medical well-being of the crew. Physicals, post-mission biomedical screenings, general medicine (heartburn, pulled muscles, headaches, etc.) are expected of the Medic.
  • Battlefield Aid - The Medic's first priority on any mission is the care and treatment of injured squad members, no matter the situation.

Diplomatic Corps Officer (DCO)

[Counselor/Medical/Ambassador(Civilian)] In many instances a Team may be required to enter a potentially hostile area in hopes of negotiating a settlement, treaty, etc. As such, the United Federation of Planets tries to equip each squad with a Diplomat. Languages and linguistics, cultural anthropology and knowledge, and general diplomatic skills are all responsibilities of the Diplomat.

  • Linguistics - Most Diplomats speak a variety of languages.
  • Cultural Anthropology - A Diplomat is an expert in Cultural behavior for most of the well known races. If a mission takes the squad into unfamiliar territory or covert operations within a particular society, the Diplomat is expected to research the culture in question and brief/train the mission participants.
  • General Diplomacy - Conflict mediation, first contact, and treaty negotiations are the specialty of the Team Diplomat.

Specialized Equipment

PRISM Special Forces and its operatives are granted access to a wide variety of weaponry and equipment. This equipment encompasses the standard compliments of phasers and rifles Starfleet officers typically use, non-aligned and foreign weaponry depending on the mission, and specialized equipment including armor.

Starfleet Special Operations also designates several starships to the efforts of PRISM.

Teams

Static

PRISM One and PRISM Two are two static teams kept in operation by PRISM at all times. Players cannot be assigned to One or Two, but they do make special appearances in missions. Two was temporarily assigned to the USS Hayden for the latter half of 2006, and remained aboard in the service of the Starship Recovery Bureau until mid 2007.

Chat

  • PRISM Alpha was the inaugural Chat mission, and ran three missions from 9901.27 through 9902.10.
  • PRISM Beta ran three missions between 9903.06 and 9903.20.
  • PRISM Gamma ran four missions between 9909.01 and 9909.22.
  • PRISM Delta consisted of three missions between 9909.18 and 9910.02.
  • PRISM Epsilon ran four missions between 10005.16 and 10006.06.
  • PRISM Zeta consisted of four missions between 10009.24 and 10010.15.
  • PRISM Eta encompassed six missions between 10010.10 and 10011.25.
  • PRISM Theta ran for four missions between 10101.31 and 10102.21.
  • PRISM Iota ran five missions beween 10103.23 and 10104.27.
  • PRISM Kappa consisted of four missions between 10108.16 and 10109.06.
  • PRISM Lambda ran for four missions between 10109.15 and 10110.13.
  • PRISM Sojourn was a special team gathered for the sixth ACTD-Wide, "Journey's End". Sojourn ran for two missions on 10112.04 and 10112.11.
  • PRISM Mu ran four missions between 10206.08 and 10206.29.
  • PRISM Nu was the first mission under the management of Christopher Dickinson, nearly a year after the previous PRISM mission. Nu ran for five missions from 10306.19 through 10308.14.
  • PRISM Xi ran for four missions between 10401.27 and 10402.17.
  • PRISM Omicron participated in the eight ACTD-Wide, "Debt of Honor". Omicron lasted for a record ten weeks between 10404.18 and 10406.27.
  • PRISM Pi had a ten week run, lasting from 10411.09 through 10502.22.
  • PRISM Rho lasted eight weeks between 10508.16 and 10510.04.
  • PRISM Sigma lasted eight weeks between 10601.30 and 10603.20.
  • PRISM Tau lasted five missions over two and a half weeks between 10611.29 and 10612.13.
  • PRISM Upsilon
  • PRISM Phi
  • PRISM Chi
  • PRISM Psi
  • PRISM Omega

PBEM

  • PRISM Janus was a trial run for PBEM, running for three months starting April 2003.
  • PRISM Shughart was the static PBEM team, opened in November 2003.
  • PRISM Vanguard is the re-launch of Shughart in 2006.

Newsfleet

  • PRISM Eternity is the trial run for Newsfleet, and went nine months starting in March 2006.
  • A Future NF PRISM may be possible...
Personal tools