HANDBOOK/PROCEEDURES MANUAL FOR TACTICAL OPERATIONS
STARFLEET COMMAND
UNITED FEDERATED PLANETS
Prepared by:
Commodore Hugh Brower
Chief of Tactical Operations
stardate: 9703.13
Version 3.1
Table of contents:
Mission Statement
Tactical Operations
Reporting structure
Purpose of D.I.R.S.
Operational Readiness alerts
Type of Role Play simulations
Possible levels of interaction
Make-up of the simulation
Reporting of findings and archiving of results of role play
Maintaining listing of e-mail Adresses
Calling "no Joy"
Development of future role play sims
Staffing for Tactical Operations.
Summary
MISSION STATEMENT
The purpose of the Tactical Operatons division is to develop, at the direction of the FADM a system of role play simulations for the use and enjoyment of members, chapters, ships, starbases, civilian units of Starfleet Command - United Federated Planets
Further, it is the responsibility of the Chief of Tactical Operations to oversee the implimetation of such simulations, role play situations, and monitor its progress . The archiving of such material for the enjoyment of all concerned is a prime responsiblity of the Chief of Operations.
By the Direction of the FADM and the Director of Operations, the Chief of Tactical Operations will make such changes to the program in order that the mission statement is completed and complied with.
It shall be the role of the Chief of Tacticial Operations to search out new materials, ask for input from any and all sources within Starfleet command to create the strongest and most enjoyable role play program available.
TACTICAL OPERATIONS
Tactical Operations is a primary catalist of the role playing arm of Starfleet Command.
Reporting to the Director of Operations directly, the Chief of Tactical Operations does not act independently from but in concert with the Chief of Operations. The Chief of Tactical Operations will only begin a simulation with the full knowledge of the command staff. In such cases where guidelines have been established, then the Chief of Tactical Operations shall act within those guidelines.
REPORTING STRUCTURE
The chain of command:
The following is the chain of command to the level of Chief of Tactical Operations.
1. FADM
2 VADM
3. Director of Operations
4. Chief of Operations
5. Chief of Tactical Operations.
Reporting of status of events and role play simulations is necessary on a monthly basis. However, as the position is new to Starfleet Command, a more open reporting policy my be necessay. The format of the report is open at this time however, the format for monthly reporting is as follows:
1. Department reporting.
2. Goal for the reporting period.
3. Percent of goal reached
4. Number of contacts with chapters
5. Types of simulations conducted and results.
6. Evaluation of simulations by command staff and Unit Commanders
7. Types of suggestions made for future reference.
8. Goals for the next 30 day period.
9. Other comments and possible events to be scheduled: role plays.
Reports are directed to the Director of Operations who forwards it along with recommendations and comments to the VADM and finily to the FADM.
Failure to conform is not acceptable. Starfleet directives complience unless otherwise directed.
PURPOSE OF THE D.I.R.S.
1. To create interaction with specific levels within starfleet command with a spcific purpose.
Many times role play is designed to go up and down the latter and very few offer a chance to intereact within a level, i.e., Commanders of units, command staff, or chapter to chapter level. In addition, the D.I.R.S. is designed for interaction between levels as the role play may direct.
2. Create team response to a specific situation. The basis of the D. I. R. S. is a team response. This team can be formed out of any configuration. No matter the level in the set-up or simulation teamwork is stressed. Because the membership of the Starfleet Command and the UFP are scatered with little contact with other members other than thier own chapter, the need is there to create a means to a team approach.
3. Create and further bond and create a stronger team that will benefit invidual members of the Starfleet command.
4. Create communication with and to all levels of Starfleet command. As indicated earlier, creating a simulation that would involve multi levls within starfleet command opens the communication needed and necessary.
OPERATIONAL READINESS ALERTS
When the FADM has notifed the Chief of Ops that a role pay sim is to be inniciated, the Chief of Ops will send, via e-mail, a fleet allert. Depending on the type of simulation and to whom it is directed, a FLEET ALERT LEVEL ONE (1) message is sent.
A "FAL-1" is a first notice that the chapter, ship, starbasse of civilian chapter can expect a simuoation to be inniciated with a 24 hour period. This will give the unit the opportunity to stand ready for a RED ALERT.
As directed by the FADM or the Director of Ops, a "test run" for Early Readiness Response" (ERR) may be conducted to get some idea of the readiness of each unit.
When a FAL-1 is issued it will be issued to the commanding officer or the exec at the same time. As there is life away from Starfleet, that's hard to believe, this allows the unit to be able to respond if one or the other is occupied with other duties. One or both individuals or designated (OD) Officer of the Day may respond to the Chief of Tactical Op's by e-mail to hughlg19@idt.net . The speedyness of the response is rewarded by unit comindation.
Should a unit have and XO that does not have e-mail capabilities, the Commanding Officer with designate an (OD) to respond in his/her stead. The OD will then contact the XO and/or the CO of the RED ALERT or an ERR.
If the unit has not responded within the time frame allowed, the alert is reissued again as a 2nd notice with the FADM , the Chief of Staff, and Chief of Operations notified of non receipt of response.
The Chief of Tactical Operations with maintain a roster of senior officers in each chapter, unit, ship, starbase and civilian section. The list includes by the limited by or to:
1. Commanding Officer
2. Executive Officer
3. Tactical Officer (where there is one)
4. Science Officer
5. Communications Officer
6. Chief of Security
7. Legal
8. Chief of Intel
9. Counselor
10. Chief Engineer
11. Medical
While each unit may not have this compliment of officers, the roster from each unit will be posted with the Chief of Tactical Operations for that positions use in Tactical Allerts.
TYPE OF ROLE PLAY SIMULATIONS
The variations and type of simulations can be an endless list. However, the following set the basic, type and scope of what might be possible.
Criteria 1. Type of unit or chapter.
Criteria 2. Areas of specific interst (list) of the particular chapter. While each chapter is , of course, starfleet command which implies star trek as a basis for role play, each unit has some specific interests of their own. PLEASE NOTE: ALL OF THE AREAS INVOLVED WILL BE UTILIZED THROUGHOUT THE PROGRAM. It will be a learning experience for all and lots of enjoyment. This list of interests are as follows;
1. Star Trek
2. Star Wars
3. The X-files
4. Red Dwarf
5. Alien Nation
6. Battle star Galactica
7. Forever Knight
8. Night Stalker
9. Tek Wars
10. The Outer Limits
11. Planet of the Apes
12. Dr. Who
13. Dark Shadows:
14. The Highlander
15. Lost in Space
16. sea Quest
17. Space Above and Beyond
18. and Sci-fi in general
Criteria 3: Type of alert
(a) Galactic: This is a fleet wide alert. The role play simulation would be directed by the Chief
of Operation and Tactical Ops. A message would be sent to each unit identifing the type of simulation
that will be advanced. There would be communication between chapter, ships, and other chapters or units to Starfleet Command, Starfleet command to units and so on. This situation has endless capabilities and solutions /resoloves.
Depending on how each unit reacts, the situation can change. A WILD CARD EVENT or situation will be introduced by the tactical officer to add to the simuation, cause havic or just enhance the role play. The wild card will be one of 20 and will be introduced at random. This can chnage the tide of the simulation and could be fun as there is only one basic rule: HAVE FUN WITH THE SITUIATION.
All members of each unit would be involved. In this case, all activity would be done by e-mail. Individual members would either gather at a central location and interact or idividual members, all alerted to the simulation, would e-mail thier input to the CO of the unit. The CO would e-mail responses to the Chief of Tactical Operations for distribution throughout Starfleet chapters and other command authorities.
The best means of archiving this for historical purposes is add on to a previous message, i.e., member one sends e-mail to CO; CO adds on or just sends the message to Chief Tact. Op's. IIf the message is tactical in nature or a situation report, the CO reacts by taking the approriate action. He/she e-mails the report to Chief of Tactical Ops for further action and distribution is made to all commands where necessary.
All levels of command can or will be involved in thier type of sim. The situation can change at any moment adding to the excitement of the fame and the moment.
B. Unit Simulations: A situation/simulation is sent to a particular unti for their reaction. All messages or responses are e-mailed to the Chief of Tactical Ops. In this case, people would meet at several location with e-mail capabilities and forward the result between each other with "cc:" to Chief of Tactical Ops.
If the unit elects to have the material or simulation forwarded to all units, chapters, commands, ships and civilian authorities, a message much be logged with the Chief of Tactical Ops prior to the simulation.
C:. Individual simulaton: By occupational title. For example: All CO's given a tactical situation or unit type problem, or CMO's or science Officers. The interplay between all would be "cc:" to Chief of Tactical Operations and archived.
The main purpose would be to have fun with the sim------go with the flow.
Make it as real as you want. Use your immagination. Have fun.
POSSIBLE LEVELS OF INTERACTION
As indicated in the types of role play situations, the levels of interaction are as important as the type of role play.
Interplay between command levels of the chain of command from the entry level cadet to fleet adm create a wider scope of what is possible as role playing goes. All types of units and personnel are important to the total scope of the role playing simulation.
Not all simulations will go from highest to lowest level, but all who wish to participate will be able to do so.
The combination of type of role play and who is involved caused a whole new situation and sets of options.
MAKEUP OF A SIMULATION:
The basic premise- use the kiss method unless, of course, the addition of more complex elliments adds to or inhances the situation.
EXAMPLES:
Borg (This is ok, but to simple) There is just to little to go on.
Chigs (again, to simple)
Borg or Chig attack a federated outpost with a new weapon. A
General alarm is sent out. A new plasma weapon is detected. The
time traveler from Tau Alpha Cei has information on how to deal with situation. Time frame: 72 hours lengh of simulation.
Request: All commands take part. Type : Galactic.
Give just enough to get the ball rolling. Questions are always welcome, clerifications also.
REPORTING OF FINDING AND ARCHIVING OF RESULTS OF ROLE PLAY SIMULATIONS
For the benefit of current and future members each role play situation/simulation from first alert to finish will be archived by the Chief of Tactical Ops. The information will be archived by stardate, type of simulation, and unit(s) involved. For example: Starbase 64 takes part in an exercise on stardate 9703.15 . It is a unit simulation concerning deep space probes. It would be refered to in the archive by stardate, unit and title: deep space probe. The archive would be located at the home page at starbase Rushmore under keyword : sims. It would be a text account of the activity.
Procedure:
As a simulation takes shape, the results are e-mailed to the Chief of Tactical Ops. The message should include stardate and time (including time zone) so that an accurate and logical log can be kept.
Being online: If a particular unit elects to share whats happening, if a single unit simulation, the Chief of Tactical Operations will forward the e-mail transmissions to all chapters and command levels.
If the simulation is ordered by the Director of Operations or the FADM and it is the request that the simulation is closed for the duration of the simulation, it will be archived and only open for review at the completion. If the simulations is of a sensitive nature or classified, "eyes only" , the role play results will be kept in seperate data file maintained by the Chief of Tactical Ops with an "eyes only" access granted by FADM or Chief of Operations.
In such cases where Command staff direct a closed file, a patition may be forwarded to Chief of Tactical Operations which will be forwarded to Director of Operations, VADM, and finally the FAEM for consideration. The freedom of information act does not apply and Starfleet executive orders apply for Security reasons.
The command staff may order or request such simulations or role plays to assist them in determining citiations and awards for units or persons in units for outstanding effort or best creative response. This can be used for evaluation purposes for promotion or placement in a stratigic assignment in Command or special Starfleet development.
Any field command level officer may request a simulation alert if he/she believe there is a situation that warrents attention. The request for simulation can also be requested by a unit to interplay with another simular unit or different type of unit.
In all cases, the simulation will run through the Chief of Tactical Ops. A unit suggesting a role play should give the basic premise, some background regarding the simulation and the time frame that it role play should occure in or finish within.
Such role plays are not only suggested but encouraged. The FADM and Director of OPs would be advised and the incentive would be noted by all command aurhorities and levels.
If the playing units want others to see the sub-space transmissions, the tactical ops would relay the even to all. If it is closed, it will remain so but the cc: needs to be sent to the Chief of Tactical Operation in either case.
MAINTAINING LISTING OF E-MAIL ADDRESSES
It is the role of the tactical ops to have a current e-mailing address for the following:
1. All command staff
2. Adm's
3. All chaper CO's
4. All chapter XO's
5. All senior staff of each chapter, ship, starbase or civ. unit.
6. As many indivials members of starfleet units as possible.
The addresses can be acquired by direct communication with the Chief of Communications or with individual units. The list would be kept secure be request of FADM DC.
CALLING NO JOY
"No Joy" is old earth term used by avaitors meaning a break from action or cesasing of operations.
There are several situations where the call "no Joy" can be inniciated:
1. There is no solution to the role play and it has ended.
2. Chief of Tactical Ops makes the call because of lack of activity.
3. Called by command level (SC) for specific reasons. They must be specificed when called.
4. By unit commander
5. "no Joy" because time limit has run out. Requests for additional time should be directed to Tactical ops. Request will be reviewed and recommendations passed to Chief of Operations.
In each case, when calling "no joy" a reason for stoping the simulation must be stated. The above are a few of the acceptable reasons.
DEVELOPMENT OF FUTURE ROLE PLAYING SIMS
As there are a infinite number of role playing simulations possible the sky is the limit. The tactical position is responsible for sim development in the 19 areas of sci-fi interest. The Chief of Tactical ops will from time to time send notice to the chapters and civ units for input from anyone who would like to submit a sim for the archive with the intention of future use.
The format for submission is as follows;
1. Type of sim: Star Wars, SAAB, Star Trek etc.
2. Directed to: Unit, intra unit, galactic or individual
3. Time line requested or needed
4. Basic situation or structure
5. Author of simulation
6. Other notes or information
7. Name and address of person submitting (snail mail and e-mail)
OTHER CONSIDERATIONS:
1. give only as much information as will be needed to start the simulation. By getting to much info might cause early closure of the sim.
2. Request clarification of variables needed or required for everyone to know so they can set the direction of the simulation.
3. Time frame: time frame can be critical. Run the simulation to long and people loose interest, to short and people will get upset. Therefore if you ae unsure, set a min and max. The chief of tactical ops will made a decision and advise of any changes.
STAFFING OF TACTICAL OPERATIONS
While the chief of Tactical Operations is responsible for this section there may be situations where it may be necessary for staff positions to either provide support or act in the Chiefs absence from the Tactical Operations Desk.
Providing support to the Chief of Operations:
The following represents only a few of the possibilities for staffing in the area of support. As the simulations and role play grow, the management of same will take on an expanded role. This being the case, the following staffing for tactical ops is suggested:
a. Asst. Chief of Tactical Opeations. To work in tandum with the Chief of Tactical Operations in all areas of development and deplyment. In the absence of the Chief of tactical ops, the asst Chief would have the helm and would make all reports to the Director of Operations, chief of operations and Chief of Staff. The assistant chief will have additional responsibilities in the area of security, quiries to chapters, ships and units of Starfleet command as may be directed and deemed necessary.
Adminastrative Assistant : As the data base of completed simulations increases, the cataloging and editing of archivable material will also increase and become a necessary function of Tactical Operations. In addition, a careful catologing of all un-run simulations will have to be kept. While the position is not immediate, it will however be necessary in the near future.
SUMMARY
Simulation and role play can be and should be fun. In order that we can all enjoy the simulation to the fullest, follow a few simple rules set up. If any chapter, unit, or command level should question a proceedure a command board will be established to review the process and make recommendations.
This is the first draft of the procedures manual for tactical ops. It will be reviewed and revised to meet any change in situation or by direction of FADM or the Chief of Operations.
Submitted:
Hugh Brower
Commodore
Chief of Tactical Operations
StarFleet Command-UFP