• Welcome to the new COTI server. We've moved the Citizens to a new server. Please let us know in the COTI Website issue forum if you find any problems.
  • We, the systems administration staff, apologize for this unexpected outage of the boards. We have resolved the root cause of the problem and there should be no further disruptions.

My New Campaign-Patrol Cruiser

jwdh71

SOC-12
Well, after getting a group together (finally!) and giving them a choice of campaigns to play in, they choose the one I least expected (isn't that just like a group of players!). I will be running them as the Officers and Crew of a 400 dton Type T patrol cruiser, in my Terran Confederation universe (a homegrown TU).

My question for the board is this, I'm writing up a number of papers detailing some of the campaign background. Most of these are easy to write, and I have had no problems. However, I decided to give them a copy of their ships Operations Orders, and having never been in any Navy anywhere, have no idea how to write something like this up. Do any of you have any ideas on how this would look. None of my current players are vets, but I would prefer it to have a realistic look to it.Any help in this matter would be appreciated.
 
Here is one example
and here is another
This is an example of how the Navy does it
With the Navy one you can go back and forward within an online text that explains all the procedures of how to build a message.
Some Main points to consider are that the message explains who is doing what, when, and where.
Everything else is by the book (Standard Naval Regulations) unless you append special exceptions to the original OPORD (Operations Order).
Like: Render all assistance to merchant and private registry vessels in distress in your Area of Operations.
Or: Do not reveal your operations, undergoing COMSEC (Communications Security) and EMSEC (Emissions Security) throughout the operation, do not provide assistance to vessels in distress until mission completion and returning to base.
I hope this gives you some ideas. An OPORD can be very broad or very narrow in conception. It gives you a great tool to send PCs into places they otherwise would not touch with a 10 meter rod.
:D
omega.gif
 
Thanks Father Fletch! Those links really help, it gives me some ideas how to go about writing their OPORD up.

I was surprised that my players chose the active-duty campaign, as it's the one where I can mess with them the most. They usually are chaos with stats, and hard to control, but now I have them right where I want them. MUAHAHAHAHAHAHAHAHAHAHAH!!! ;)
 
As usual, Father Fletch, good stuff. Thank you! But I think I need someone to sit down and explain it to me...
 
Essentially, Milistary orders need the following sections:

TO: Usually addressed to the unit commander, who then cuts the orders for his subordinates. Sometimes addressed to the unit; this is more likely in a Traveller Wartime setting, due to lack of direct knowledge of unit commander.
FROM: Who is giving the orders, including rank and office symbol. Sometimes, name of issuer is NOT included.
EG: Headquarters, Solomani Rim Sector Army, Adjutant to the Commander's office.
EG of office symbols: "James Hostman, Command Environmental, 11AF/DEPV" No rank, since he's a civil servant, verbose office title, and then office symbol, including "Eleventh Air Force, Civil Engineering (DE) PV (Programs, environmental)"
Date of Issue: When the orders were signed.
Date Effective sometimes a header, sometimes in the body, but always present, this says when the actions specified will be begun.
Clearance: clearance level required to read the orders. If non listed, assume "Sensitive", but not classified; IE, don't tell anybody wihtout need to know.
Action Required: details what action or actions are required. Can be as simple as "Hold until relieved", or as detailed as any operation you care to name.
Acknowledgement: What you have to do to indicate you recieved the orders. Often omitted, if orders are to be hand delivered or direct radioed.
Command Authority: Not always present, but assume normal chain of command if not. Tell you who is now your immediate commander. They are supposed to keep you inside your extant orders if they are not the issuer. If the action is simply a transfer, and is essentially permanent, they and their chain of command are now your chain of command. Transfers ARE different from Attachements.
EG: "You are hereby attached to the 1234th LIR, Regina, while on station at Wypoc." This means that the order put the recipient in the charge of the commander of the 1234th infantry so long as both are at wypoc. Anyplace else, and it gets dicey.
EG: "Command Authority: Commander, 123rd Marches CruRon" as a header...
means that the orders put you directly under the commander of said unit, and interpretation issues are his to decide..., even if the orders were cut by a wholly different authority.
Rules of Engagement are optional, but common for deployment orders. They delineate, clearly, often in excessive detail, when you are allowed to shott, when you may run, and when you are expected to simply take it, or even when you need to find non-combat solutions to combat threats. Nature, wording, and details vary so widely that any examples would be effectively single-case examples.
Distribution List: Who gets copies, besides the listed parties in the to and from lines.
Order ID Number is used by some forces, not by others... but it is a sequential numbering with some from of issuerID (usually a prefix) of issued orders. Used to prevent confusion of which set of orders takes precedence, since the precedence of the issuer is often more clear from the prefix than from the issuer's office data.
Signature Block includes signature, namme and rank of issuer OR THEIR AUTHORIZED SIGNATOR. Many orders out of higher commands are signed by functionaries.
Transmittal Date: date orders sent. Filled in by transmitting clerk. Not always present.
Reciept date: Date orders recieved, added by recipient, often by time-date stamp

Hope this helps somewhat.
 
Thanks Aramis, it does. Between you and Father Fletch, I think I will be able to pull this off. Thanks again.
 
Well, we had the first full session this past Wednesday, where we got the crew together and began preparing for their first patrol together.

The Place: Svenson Naval Base, Manfred C. Wolchester Memorial Starport, Easter (Easter Subsector)

The Ship: TCNS (Terran Confederation Naval Starship) Narwhal CT-765 (Type T patrol cruiser, based on Ron Vutpakdi's excellent Timberhawk deckplans)

The Time: 17Feb2301

The Crew:
Lt. Commander Chaz Vaughan, Captain (Lvl 7 Navy). Lt. Comm Vaughan came up through the ranks, not uncommon in Patrol Fleet, and as the ranking officer of B Flight of 138th Squadron, is in administrative command of it as well (Which means he's responsible for its paperwork and little else, as Patrol Fleet ships usually patrol solo).

LT Godric Strangelove, Pilot (Lvl 5 Navy). A cipher so far, seems to be a very competent pilot, but all around strange character otherwise.

LT Albrecht Worthing III, Astrogator/Commo/ Sensors (Lvl 6 Navy). Al, as he calls himself, is an easygoing partyguy, but very knowlegable about his job. (He also happens to be heir to the CEO/Owner of a LARGE corporation, which he keeps very quiet.)

LT Reiko Mizuhara M.D. Ships Doctor (Lvl 2 Academic, Lvl 2 Navy). Descended from a long line of Naval officers, Reiko never wanted to be one. She only joined the Navy after college and Med school to please her mother, Admiral Mizuhara.

Marine Sgt. Pedro Gomez (Lvl 5 Marine). Sgt. Gomez appears to be a bit of a brutal burnout case, beating on two new privates and attempting to sneak a bit of recreational smoking on the cargo deck.

Two other PC's did not make their appearance at this session, the rest of the crew are NPC's.

The players seem to be adjusting to the setting well, most have never done SF RPG's, except for Cyberpunk and Star Wars. Two standouts are the the Captain and LT Worthing, both seem to be really getting into their parts, with the Captain giving a good performance and LT Worthing's character doing a very good job schmoozing for information. We'll see how it goes.
 
Second session this past Wednesday, new crew member (PC) CPO Troy McClure, Master Gunner was added to the roster, the crew made their final preparations to leave, getting their weapons loadout and final stocks of supplies. The Captain continues to run alerts and simulations, getting a feel for the crew and allowing them to get a feel for him. The only weak link seems to be Sgt. Gomez, who neglects to make up a duty roster when requested, and the Captain grabs two Marines and puts them on ramp guard himself. A dressing down ensued soon after. Next time, Launch!
 
Back
Top