logotype
13 -December -2017 - 05:38

 

StandingOperatingProcedures

 

DataDocs

 

A DataDoc (“Data Document”) is an official file of the Republic Navy that is logged on the Fleet Datanet (Forums).  These files represent written orders, briefings, reports, and requests.

All DataDocs must be written in the appropriate format, using the templates given in these operating procedures, before being submitted to the relevant files section of the Fleet Datanet for the unit or branch they concern (DataDocs of general or fleet-wide relevance should be submitted to the main “Fleet Datanet” directory).

 

Contents

Message Codes

Code Formatting
Example Message Codes
Message Accessibility
Document Code Acronyms
Personnel Code Acronyms

Operational Files

Operational Order (OPORD)
Mission Order (MISORD)
Assignment Order (ASGORD)
After Action Report (ACTREP)
Field Status Jacket (STATJAC)

Personnel Files

Personnel File (PERFIL)
Medical File (MEDFIL)
Training Report (TRAINREP)
Disciplinary Report (DISREP)
Transfer Request (TFREQ)
Request for Leave (LREQ)

Security Files

Security Report (SECREP)
Watch Shift Report (WATCHREP)
Authorisation Request (AUTHREQ)
Incident Report (INCREP)  
Detainee Report (DETREP)

Technical Files

Maintenance Request (MAINTREQ)
Equipment Requisition Request (EQREQ)
Engineering Report (ENGREP)
Medical Report (MEDREP)

Intelligence Files

Personal Dossier (PERDOS)
Organisational Dossier (ORGDOS)
Investigation Report (INVREP)
Interrogation Report (INTREP)

Miscellaneous Files

General Message (GENMES)
Personal Log (PERLOG)

 


 

Message Codes

Every Data Document should begin with a message code. This is a pre-set sequence of acronyms that represent various meta-information tags regarding the nature of the document. Each message code line should begin with a double forward-slash to indicate it is part of the code, in the following sequence:

//<DataDoc Type>
//<Security Level>
//<Priority Code>
//<System Message Type>
//o<Addressed Unit/Individuals>
//x<Author Code>

 

Code Formatting

DataDoc Type - Indicates the type of DataDoc being transmitted, with the relevant DataDoc abbreviation code listed here.

Security Level - Indicates how classified/secret the data contained in the document is.  Level Three is cleared for dissemination to all personnel.  Level Two is restricted to 2ICs, Team Leaders and Officers only.  Level One is restricted to Executive Officers and above only.  Level Zero is restricted to Commanding Officers only.

Priority Code - Indicates how urgent the data contained in the document is.  ‘Priority blue’ is standard non-urgent information.  ‘Priority gold’ represents important information.  ‘Priority red’ represents vital information of very high importance.

System Message Type - Indicates whether the document will be sent to all personnel, team leaders or officers within a specified unit, or only to specific individuals. The actual recipients of the message are not listed here; only how the message should be distributed.

Addressed Unit/Individuals - Designates the intended recipients of the document. If a particular unit is being addressed, the unit’s abbreviation code is listed here. If the DataDoc is being sent to a specific individual, the recipient’s position code, rank and surname is listed here, with the format POSITION-RANK-SURNAME.

Author Code - The sender’s position code, rank and surname is listed here, with the format POSITION-RANK-SURNAME.

 

Example Message Codes

An example code would be:

//MISORD
//SECLEV THREE
//PRIORITY GOLD
//SYSMETPER
//oETECMD
//xCORSS-CMDR-YASRA, B.

In this case, it is an Mission Order; with a security level accessible by all personnel; containing important information; which the system will send to personnel; within Empress Teta Command; and the message is sent by Commander Yasra.

A second example code:

//TRAINREP
//SECLEV TWO
//PRIORITY BLUE
//SYSMETLDR
//oETEMEU
//xXOMEU-GYSGT-RAGNARSON, E.

Here is a training report; with a security level accessible by team leaders, second-in-commands and above; containing non-urgent information; which the system will send to team leaders and second-in-commands; within the Marine Expeditionary Unit; and the message is sent by Gunnery Sergeant Ragnarson.

Another example code:

//PERLOG
//SECLEV THREE
//PRIORITY RED
//SYSLOG
//oETECMD
//xACM-SPC-NOST, R.

This example shows a personal log; with a security level accessible by all personnel; containing critically important information; which the system will store on file; within the Empress Teta Command; and the file is recorded by Specialist Nost.

A final example code is as follows:

//GENMES
//SECLEV THREE
//PRIORITY BLUE
//SYSMETPRIV
//oACM-SPC-KARDAL, M., oNIO-PVT-BISHTO, B., oSTM-CPL-MAKESA, C.
//xACM-LT-VRAND, A.

This is a general message; with a security level accessible by everyone; containing non-urgent information’ which the system will send to specific individuals; those individuals being Specialist Kardal, Private Bishto, and Corporal Makesa; and the message is sent by Lieutenant Vrand.

 

Message Accessibility:

Messages are sent to the recipients listed in the <Addressed Unit/Individuals>, and can only be read by the recipients and the message author. (If your character wasn’t listed as a recipient, you can read the message OOCly, but ICly, your character cannot read the message).

However, anyone may (ICly) gain access to read any messages sent within their level of security clearance (SECLEV) with a security override, even when they were not among the original recipients of the message. This is usually done during investigations; for example, any individual with security clearance level three (all personnel) may access any messages sent with SECLEV THREE coding, providing they have good reason to do so, such as investigating a fellow comrade’s medical records, personal logs and correspondence with other crewmembers, following their unexplained disappearance, or a serious incident aboard the ship involving them.

Of course, characters accessing messages in this manner without a good reason, or without obtaining clearance from their superiors risk breaching military regulations, which, depending on the DataDoc accessed, can vary from a simple invasion of privacy, to professional misconduct or negligence. Characters cannot access files above their own security clearance level without slicing into the military Datanet, which, if caught, might result in charges of espionage and conspiracy being brought against them.

 

Document Code Acronyms

SECLEV - Security Level - indicates how classified/secret the data contained in the document is.

SYSMETPER  - System Message to Personnel - indicates the intended audience of the DataDoc are all active personnel in the appropriate unit.

SYSMETLDR  - System Message to Team Leaders - indicates the intended audience of the DataDoc is all team leaders and second-in-commands within the appropriate unit.

SYSMETOFF - System Message to Officers - indicates the intended audience of the DataDoc is all officers within the appropriate unit.

SYSMETPRIV - System Message to Private - indicates the intended audience of the DataDoc is specified private individuals.

SYSLOG - System Log Entry - indicates the DataDoc is a particular log or record, rather than a message being sent. This is used for personal logs, as well as personnel files, medical records, and any other document that may be revised and updated over time.

ETECMD - Empress Teta Command - anyone stationed or assigned to the RSS Empress Teta and its command group.

ETENAVOPS - Empress Teta Naval Operations - the members of RSS Empress Teta’s Able-bodied crew.

ETESFOPS - Empress Teta Starfighter Operations - the Republic Navy Starfighter Corps personnel assigned to the RSS Empress Teta.

ETEINTDIV - Empress Teta Naval Intelligence Division - the Republic Naval Intelligence personnel assigned to RSS Empress Teta.

ETEMEU - Empress Teta Marine Expeditionary Unit - the Republic Marine Corps personnel assigned to RSS Empress Teta.

 

Personnel Code Acronyms

Position Codes

CORSS - Commanding Officer, Republic Starship

COMEU - Commanding Officer, Marine Expeditionary Unit

XORSS - Executive Officer (Second in Command), Republic Starship

XOMEU - Executive Officer (Second in Command), Marine Expeditionary Unit

SQLDR - Squadron Leader, Starfighter Operations

SCNI - Section Chief, Naval Intelligence

LCM - Leading Crew Member

FTLDR - Flight Leader

STL - Strike Team Leader

SLNI - Section Leader, Naval Intelligence

ACM - Able Crew Member

SQM - Squadron Member

STM - Strike Team Member

NIO - Naval Intelligence Operative

 

Rank Codes

Naval Rank Codes

CAPT - Captain

CMDR - Commander

LTCMDR - Lieutenant Commander

LT - Lieutenant

ENS - Ensign

MID - Midship

MCPO - Master Chief Petty Officer

MWO - Master Warrant Officer

CPO - Chief Petty Officer

CWO - Chief Warrant Officer

PO - Petty Officer

WO - Warrant Officer

CPL - Corporal

SPC - Specialist

PVT - Private

 

Marine Rank Codes

COL - Colonel

MAJ - Major

CPT - Captain

1LT - First Lieutenant

2LT - Second Lieutenant

SGTMAJ - Sergeant Major

GYSGT - Gunnery Sergeant

SSGT - Staff Sergeant

SGT - Sergeant

CPL - Corporal

SPC - Specialist

LCPL - Lance Corporal

PVT - Private

 


 

OPERATIONAL FILES

Operational Order (OPORD)

Operational Orders are written briefings that contain all relevant information required for operational personnel to know and are designed for the largest scale deployments and campaigns undertaken by the Republic Navy. Operational orders should be lodged at least 1 week prior to any combat deployment.

Operation Codename:
The operation’s codename.

Operational Background:
Explain the context of the operation, detailing the relevant situation and history, along with what the operation’s strategic significance is.

Operational Objective(s):
List the operation's primary, secondary, and tertiary goals, where applicable.

Operational Orders:
Detail what forces will be deployed, where, and how. Outline the tactical plan for the operation and what everybody’s role in it is expected to be, as well as the withdrawal plan and any other relevant directions for personnel.

Anticipated Threats:
Outline any opposing forces that are expected to be faced, including their size and composition if known.  Also explain any specific environmental hazards or other threats to personnel that should be taken into considered.

Operational Chain-of-Command:
List the personnel who are expected to be in direct command of the operation, and what their role should be. 

Operational Dates & Times:
An estimated schedule for the operaation should be provided with the dates and times of any of the following key events:
###

 

Mission Order (MISORD)

Mission Orders are written briefings for any planned combat engagement or deployment, including both space and ground operations. Though not as comprehensive as an operational order, mission orders provide information for a wider variety of deployments, from small skirmishes to moderately large battles. Mission orders should be lodged at least 48 hours prior to execution.

Mission Background:
Explain the context of the mission, detailing the relevant situation and history, along with what the mission’s strategic significance is.

Mission Objective(s):
List the mission’s primary, secondary, and tertiary goals, where applicable.

Mission Orders:
Detail what forces will be deployed, where, and how. Outline the tactical plan for the mission and what everybody’s role in it is expected to be, as well as the withdrawal plan and any other relevant directions for personnel.

Anticipated Threats:
Outline any opposing forces that are expected to be faced, including their size and composition if known.  Also explain any specific environmental hazards or other threats to personnel that should be taken into considered.

Chain-of-Command:
List the personnel who are expected to be in direct command of the mission, and what their role should be.  

Mission Dates & Times:
An estimated schedule for the mission should be provided with the dates and times of any of the following key events:
###

 

Assignment Order (ASGORD)

Assignment Orders are issued for non-combat operations and assignments both aboard ship and on the ground which require minimal direct supervision from the chain of command. The order covers a multitude of possibilities including anything from a simple security patrol to comprehensive disaster relief on a planet’s surface. Assignment Orders should be lodged at least 24 hours prior to execution.

Assignment:
Detail the assignment and any relevant background information.

Assignment Objectives:
List the assignment’s primary, secondary, and tertiary goals.

Assignment Orders:
Detail what personnel will be deployed, where, and how. Outline the plan for the assignment and what everybody’s role in it is expected to be, as well as the withdrawal plan and any other relevant directions for personnel.

 

After Action Report (ACTREP)

After Action Reports are post-mission reports/debriefings used to chronicle the sequence of events and provide a summary of any deployment or engagement, whether planned or not. They are usually written by the officer in charge of the mission, but may also be submitted by any personnel that wish to officially document their own point of view.

Operation Codename:
The operation’s codename or other descriptive title of the engagement.

Dates & Times:
The dates which the relevant action took place, and the approximate times that the action commenced and concluded.

Personnel:
A list of all personnel who participated in the mission or combat, ordered by position, rank, and name.

Sequence of Events:
Give a factual description of what occurred during the mission or combat engagement in an objective, step-by-step manner.

Objectives Achieved/Failed:
Provide a summary list of any mission objectives that were successful or unsuccessful.

OPFOR Damage:
A list of any opposing forces injured, killed, or destroyed during combat.

ALFOR Casualties:
A list of any allied forces injured, killed, or destroyed during combat.

Additional Notes:
This is where the author should write any subjective tactical analysis of successes/failures and provide critique, as well as noting particular personnel for commendations or awards.

 

Field Status Jacket (STATJAC)

Field Status Jackets are ongoing operational reports of personnel currently in the field on assignment.

Personnel ID:
The rank, name, position, and billet of the author.

Serial Number:
The subject's Republic Navy serial identification.

Alias:
Subject’s current alias or callsign, if applicable. Include all relevant details.

Assignment:
Concise description of current assignment. Link to relevant OPORD/MISORD/ASGORD, if applicable.

Report History:
Links to any other DataDocs containing relevant information about the mission or deployment, including reports, dossiers, or previous field status jackets.

Contact Details:
Detailed descriptions on how to contact the operative, including dead drop locations, encrypted comm channels and coded holonet pages. This is applicable only if personnel/teams in question are undercover, operating behind enemy lines, or are otherwise prevented from using regular channels of communication.

Status:
A factual description of what has occurred so far during the mission or deployment in a step-by-step manner, noting anything that might impact the success or failure of the mission, as well as any other important developments.

Support:
List of relevant support units in place to provide assistance. Include local station chiefs, military units and local contacts.

Emergency Procedures:
Detailed list of procedures to be carried out in an emergency, including evacuation, medical emergency, undercover exfiltration.

Assessment:
The author’s assessment on whether or not to continue assignment, discontinue assignment, or act on any information gathered.

Additional Comments:
Other remarks.

 


 

Personnel Files

Personnel File (PERFIL)

Personnel Files serve as an administrative record of an individual within the Republic Military. To contain a complete service history, medical record (including psychological evaluations) and pertinent personal information.

Name:
The serviceman’s full name.

Rank:
The serviceman’s rank, written in full.

Position:
The serviceman’s position, written in full.

Serial Number:
The serviceman’s republic military serial identification.

Status:
The serviceman’s current status. Update as applicable; Active/Inactive/Retired/Discharged/Deceased/Missing in Action/Wounded in Action/Killed in Action/Prisoner of War.

Age:
The serviceman’s age in galactic standard.

Physical Description:
The serviceman’s race, gender, height, weight, scars or other noticeable physical traits.

Homeworld:
The serviceman’s homeworld.

Next of kin:

Contact details for next of kin, in event of serious injury or death.

Date of Enlistment/Commission:
Date subject joined Republic Navy.

Unit:
The serviceman’s current assigned unit.

Service History:
Concise chronological account of the serviceman’s past unit assignments and operational participation.

Training:
Training received by the serviceman, include all relevant qualifications and certifications.

Commendations:
The serviceman’s written awards/commendations/decorations.

Disciplinary Record:
The serviceman’s written disciplinary actions. Attach links to relevant reports as needed.

Medical Record:
Concise medical record of the serviceman. Attach links to subject’s Medical File and any relevant reports as needed.

Psychological Profile:
The serviceman’s written psych profile as compiled by a certified psychologist.

Additional Comments:
Other remarks from evaluating personnel. For example, the serviceman’s commanding officers.

 

Medical File (MEDFIL)

Medical Files contain all relevant information regarding an individual’s medical condition, and a record of their medical history and treatment. Medical Files are a source of medical information only; for recording specific medical interventions or incidents, Medical Reports should be filed instead.

Personnel ID:
The rank, name, position, and billet of the subject.

Serial Number:
The subject’s republic military serial identification.

Personnel File:
Link to the subject’s Personnel File.

Status:
Whether the subject is alive or deceased. If deceased, list date and cause of death.

Physical Description:
The subject’s race, gender, height, weight, scars or other noticeable physical traits.

Respiratory and Cardiovascular Health:
The condition of the subject’s heart, lungs, airways and blood vessels, including an assessment of the subject’s pulse, blood pressure and respiratory rate.

Musculoskeletal Health:
The condition of the subject’s bones, muscles and joints, including an assessment of the subject’s range of motion and ability to move.

Abdominal Health:
The condition of the subject’s abdominal area and internal organs, such as the gastrointestinal and urinary systems.

Sensory Awareness:
The condition of the subject’s eyes and ears, including an assessment of the subject’s visual and auditory acuity.

Mental and Neurological Health:
The condition of the subject’s brain and nervous system, including any mental health conditions.

Chronic Conditions and Medications:
Any long-term conditions or maladies the subject has, as well a list of ongoing medications being taken, if any.

Cybernetics:
A list of the subject’s cybernetics, if they have undergone cybernetic enhancement, including both implants and prostheses.

Allergies:
A list of any allergies the subject is known to possess, especially to particular medications.

Immunisations:
A list of the immunisations and vaccinations the subject has received, and the date they were administered.

Diet and Habits:
The general diet of the subject, as well as any personal habits that affect the subject’s health, such as level of exercise, consumption of alcohol, smoking, or spice use. Note substance dependency or addiction, if applicable.

Additional Comments:
Any other notes or observations about the subject’s health and wellbeing.

Medical History:
A list of all medical reports pertaining to the subject’s health and treatment, with links to each report.

 

Training Report (TRAINREP)

Training Reports are used to log particular training sessions and the results of that training, whether it be physical, mental, professional or specialisation-specific. Training Reports are normally authored by those conducting training sessions, but may also be written by trainees to keep a personal account of the session and their progress.

Trainer(s):
The individual(s) conducting the training session, listed with their position, rank and name.

Trainee(s):
The individual(s) participating in the training session, listed with their position, rank and name.

Location:
Location of the training session.

Subject:
A concise description of the subject of the training session.

Summary:
Summary of findings, including progress made, shortcoming or setbacks, as well as any recommendations or observations for future training sessions.

Signed:
The author’s written or electronic signature attesting to the above report.

 

Disciplinary Report (DISREP)

Disciplinary Reports are used to record cases of misconduct by military personnel, the proceedings of any administrative or disciplinary action taken against them, and the results of those proceedings. Disciplinary reports document the full legal proceedings of military justice, from small misdemeanours through to the prosecution of a full court-martial.

Defendant:
The rank, name, position, and billet of the defendant.

Arbitrator:
The rank, name, position, and billet of the author/arbitrator.

Plaintiff:
The rank, name, position, and billet of the plaintiff. If there is no individual plaintiff, cite the Republic Navy as the plaintiff.

Time:
The date and time of the disciplinary proceeding.

Disciplinary Proceeding:
The type of disciplinary proceeding convened; administrative action, summary hearing or court-martial. If the proceeding is an appeal, this should also be noted. Additionally for courts-martial, name the prosecution and defence counsels and the presiding judge advocate.

Charges:
A concise list of the crimes and breaches of military protocol the defendant has allegedly committed. Any alleged violations of the Articles of Defence or the Galactic Constitution should be specifically noted.

Defendant’s Plea:
The defendant’s plea to all or each of the specific charges brought against them.

Incident Reports:
Links to any relevant incident reports.

Testimony:
A summary of the testimony of the defendant and the testimony of any witnesses or expert witnesses.

Evidence:
A summary of the evidence presented during the proceeding to establish the culpability of the defendant. Link to relevant files, reports and correspondence as necessary.

Verdict:
The establish verdict or ruling for all or each of the charges lodged against the defendant.

Action Taken:
The disciplinary action or punishments, if any, pursued as a result of the verdict.

Additional Comments:
Further notes or recommendations.

Signed:
The author’s written or electronic signature attesting to the above report.

 

Transfer Request (TFREQ)

Transfer Requests are used to submit a request to change from one division or service branch to another. Be sure to address them to both the officers of the division you wish to depart, and that you wish to join. The request will be discussed by all affected parties and a decision made based on the information you include.

Personnel ID:
The rank, name, position, and billet of the request author.

Serial Number:
Republic Military serial identification.

Personnel File:
Link to subject’s Personnel File, if applicable.

Current Division:
The subject’s current division or service branch.

Intended Division:
The division or service branch the subject intends to transfer to.

Reason:
The reasoning that the subject wishes to transfer.

 

Request for Leave (LREQ)

A Request for Leave is used to submit a request for a leave of absence, which is necessary for those leaving the ship for their own business or pleasure. Be sure to address them to both the Commanding and Executive Officer of your division to ensure a timely reply. The request will be discussed by all affected parties and a decision made based on the information you include. Being absent without leave ('AWOL') constitutes a breach of military protocol.

Personnel ID:
The rank, name, position, and billet of the request author.

Departure:
The date and time of your intended departure.

Return:
The date and time of your intended return.

Reason:
The reason that you are requesting a leave of absence.

 


 

SECURITY FILES

Security Report (SECREP)

Security Reports are used to log the processing of any persons through security checkpoints, whether aboard a capital ship or an area under military occupation or administration. Security reports are a key method of tracking persons not part of the RSS Empress Teta’s crew, and should be filed with all new arrivals aboard the ship.

Supervising Personnel:
The rank, name, position, and billet of the author.

Check-listed visitors:
A list of all arrivals processed.

Accompanying Staff:
If the arrival was accompanied by a listed member of the crew, note their rank, name, position and billet.

Personal Identification:
For each arrival, list whether they were carrying appropriate Identification, and whether it was cleared.

Background Check:
For each arrival, provide a concise summary of their background, and any notable affiliations. In particular, any evidence of criminality or association with organisations hostile to the Republic should be noted.

Summary of Possessions:
Checklist of all articles carried about their person, and what items, if any, were confiscated for the duration of their visit.

Risk Assessment:
The author’s assessment of the potential risk, if any, that the arriving persons pose to allied personnel and materiel.

Additional Notes:
Any other comments the author wishes to make regarding the process, or the arrival.

Signed:
The author’s written or electronic signature attesting to the above report.

 

Watch Shift Report (WATCHREP)

Watch Reports are lodged at the end of a watch shift by the retiring Officer of the Watch.  They are a key means of tracking shipboard events and form the heart of the ship’s log.

Watch:
The date and shift of the watch. The watch shift is simply either ‘first watch’, ‘mid watch’ [...]

Officer of the Watch:
The rank, name, position, and billet of the Officer of the Watch.

Watch Personnel:
A list of all personnel who were on duty during the watch, list by position, rank, and name.

Summary of Events:
Give a list of any events of note which occurred during the watch shift  in an objective, chronological manner.

Additional Notes:
Any other comments the Officer of the Watch wishes to make regarding events of the Watch.

Signed:
The author’s written or electronic signature attesting to the above report.

 

Authorisation Request (AUTHREQ)

Authorisation Requests are used to submit a request for authorisation to undertake a certain activity or make use of facilities that fall outside your usual field of duty, thus needing to be reviewed and signed off by an officer of the appropriate division.

Personnel ID:
The rank, name, position, and billet of the request author.

Authorisation Request:
A short summary or title, followed by the request proper. Be as specific as possible, using proper military designations, where applicable.

Duration:
The anticipated period of time for which the authorisation is requested.

 

Incident Report (INCREP)

Incident Reports are used to document any non-critical incident aboard ship, whether or not it resulted in injury. For example; accidents, breaches of discipline, theft of equipment etc. For combat engagements or a critical incident, an After Action Report should be filed instead.

Supervising Personnel:
The rank, name, position, and billet of the author.

Incident:
Brief description of incident.

Time:
Date and time of incident.   

Location:
Deck, compartment/billet of incident.

Persons involved:
List of personnel and other persons involved in the incident. Personnel should be listed first, with rank, name and position.

Sequence of Events:
Give a factual description of what occurred during the incident in an objective, step-by-step manner.

Actions:
Either actions taken or suggested actions.       

Additional Notes:
Other pertinent information.

Signed:
The author’s written or electronic signature attesting to the above report.  

                           

Detainee Report (DETREP)                   

Detainee Reports are used to report the arrest/capture/detention of anyone by a command group.

Supervising Personnel:
The rank, name, position, and billet of the author.

Number:
Number of detainees. Further categorization is allowed.

Individuals Detained:
Names, age, gender, species of detainees. Can cover any details known or freely given without interrogation.

Location:
Location of arrest/capture/detention.

Reason:
Reason for detention. List for each individual.

Medical Condition:
List the medical condition of each detainee. If medical assistance is required, take note, and link to any medical reports if applicable.

Detention Orders:
List location where each detainee is incarcerated, and the terms of their incarceration. For example; Brig, Confined to Quarters, Guard Detail etc.

Additional Notes:
Other pertinent information.

Signed:
The author’s written or electronic signature attesting to the above report.

 


 

Technical Files

Maintenance Request (MAINTREQ)   

Maintenance Requests are used to request maintenance support, which can include maintenance to small arms and standard-issue equipment, through to maintenance to particular sections of the ship, including janitorial duties. Significant work undertaken on major starship systems or as part of starfighter repairs or upgrades should be noted with an Engineering Report instead.                                                  

Personnel ID:
The rank, name, position, and billet of the request author.   

Equipment:
Name, location and number of pieces in need of maintenance.   

Condition:
Condition of equipment. Need for maintenance. Known faults.

Additional Notes:
Other pertinent information.

 

Equipment Requisition Request (EQREQ)

Equipment Requisition Requests are lodged to order specific equipment from the ship’s Quartermaster. This is typically used to order standard-issue uniforms and equipment for new recruits, but also includes all manner of other equipment necessary for specialised equipment loadouts, through to machinery, engineering parts, vehicles, and food and medical supplies.

Personnel ID:
The rank, name, position, and billet of the request author.

Items Requested:
An itemised list of the required materiel.  Be as specific as possible, using proper military designations.

Reason:
The nature of the request, explaining the purpose for which the item(s) are to be used.

Duration:
The anticipated period of time for which the requisitioned item(s) will be required.

 

Engineering Report (ENGREP)

Engineering Reports are used to document work to the ship’s systems, or significant repairs or upgrades to the ship’s starfighter  compliment. Though maintenance of the ship’s systems falls under the purview of the Engineering Department, Engineering Reports may be submitted by any crewmembers involved in the work.  Any alterations made to any subsystem, or any craft (transport or fighter etc.) berthed aboard the ship, must be reported.

Supervising Personnel:
The rank, name, position, and billet of the crew member overseeing the work.

Personnel:
The rank, name, position, and billet of other crew participating in the work.

Affected Systems:
A description of the specific systems/craft requiring attention.

Damage Assessment:
The nature of the damage or malfunction requiring the equipment to be repaired or modified.

Repair Assessment:
Explain the repairs made and their sustainability/expected duration.

Additional Comments:
Further notes or recommendations.

Signed:
The author’s written or electronic signature attesting to the above report.

 

Medical Report (MEDREP)

With the ship’s Medical Department having responsibility for primary care of all aboard ship, the vessel’s physicians are required to file Medical Reports regarding all patients’ care with the Admiralty and Republic High Command. Medical Reports may also be filed by marine combat medics, or any other trained crewmember that administers first aid.

Patient:
The patient’s rank, name and position.

Attending Medic:
The rank, name, position, and billet of the author.

Triage:
Classification of the severity of the patient’s condition, and the effect of medical care.

Condition:
Give a medical description of the injuries or illnesses affecting the patient, particularly the patient’s symptoms.

Diagnosis:
Provide a formal diagnosis, if applicable.

Treatment:
Explain the course of treatment pursued and the patient’s response to it.

Prognosis:
Predict the patient’s likelihood of survival, the rate of recovery, further treatment that might be required, as well as an estimation as to if and when the patient will be fit to return to active duty.

Additional Comments:
Further notes or recommendations.

Signed:
The author’s written or electronic signature attesting to the above report.

 


 

Intelligence Files

Personal Dossier (PERDOS)

Personal Dossiers are collected, written, and kept updated on any designated persons of interest to Naval Intelligence.  This may range from Sith Lords and Imperial officers to underworld figures and shady businessmen.

Name:
The subject’s full name.

Rank:
The subject’s rank, if applicable, written in full.

Position:
The subject’s position, if applicable, written in full.

Alias:
The subject’s known aliases.

Affiliation:
The subject’s known state or organisation allegiance and/or affiliations.

Age:
The subject’s age in galactic standard.

Physical Description:
The subject’s race, gender, height, weight, scars or other noticeable physical traits.

Homeworld:
The subject’s known homeworld, sector, and region of birth or other location of birth.

Location:
The subject’s last known whereabouts or domicile.

Relations:
The subject’s known interpersonal relationships or family.

Mentality:
The subjects presumed psychological disposition.

Assets:
The subject’s known assets at their disposal, including money, materiel, holdings, ships, and personnel.

Relative History:
The subject’s relative history, including notable events, encounters, and meetings.

Additional Comments:
Other pertinent information.

 

Organisation Dossier (ORGDOS)

Organisation Dossiers are collected, written and kept updated on any organization of interest to Naval Intelligence. This may range from Sith cabals and Intelligence services to Imperial strike groups and underworld cartels.

Name:
The organisation’s name.

Base of Operations:
The organisation’s headquarters and/or operational base(s).

Leadership:
The organisation’s chain of command and leadership.

Affiliation:
The organisation’s affiliation to other galactic states or power blocs.

Threat Assessment:
The organisation’s potential threat to the Galactic Republic.

Assets:
The organisation's available assets including money, materiel, holdings, ships and personnel.

Membership:
The organisation’s known membership, it’s structure, composition and personnel.

Agenda:
The organisation’s known goals and interests, be it monetary, militaristic, political or fanatical ideals.

Organisational Interactions:
The organisation’s known intra-organization contacts, be them stalwart friend or dastardly foe.

Relevant History:
The organisation’s relevant history, including notable events, encounters, or meetings.

Additional Comments:
Other pertinent information.

 

Investigation Report (IVREP)

Investigation Reports are compiled and written on investigations performed under military administration and direction. These can range from internal affairs investigation of misconduct, the gathering of valuable military intelligence in the field, to investigating past events both from within and from without.

Investigating Personnel:
The personnel charged with the investigation, including position, rank and name.

Subject:
The person, place, or event being investigated.

Objectives:
The stated objective of the investigation and its intended result.

Time:
The date and time of the initial investigation.

Related Documentation:
Links to relevant documents or files.

Report:
The findings of the investigation; evidence, interviews and testimony, and their analysis.

Summary:
The results of the investigation; the author’s conclusions and recommendations.

Signed:
The author’s written or electronic signature attesting to the above report.

 

Interrogation Report (INTREP)

Interrogation Reports are compiled and written on subject’s brought into custody, be it a informal interrogation following disorderly conduct or long-term debrief and multiple evaluative interrogation.

Interrogation Subject’s Name:
The interrogation subject’s name.

Interrogating Personnel:
The interrogator’s position, rank, and name.

Charges:
The subject’s reason for imprisonment and/or interrogation.

Location:
The location(s) that the interrogation took place.

Time:
The date(s) and time(s) that the interrogation took place.

Report:
The questions and answers conducted during the interrogation in addition to the final report from the interrogator.

Summary:
The results of the interrogation; the author’s conclusions and recommendations.

Signed:
The interrogator’s written or electronic signature attesting to the above report.

 


 

Miscellaneous Files

General Message (GENMES)

General messages are used to transfer information not found in any other report, and are also frequently used to respond to requests, and for casual correspondence between crewmembers.

Subject:
Subject of message.

Narrative:
Body of message.

 

Personal Log (PERLOG)

Personal Logs are the private journals of particular crewmembers, and serve to record their opinions and observations for posterity and personal reflection.

Personnel ID:
The rank, name, position, and billet of the request author.

Time:
Date and time of log submission.

Subject:
Subject of message.

Log Entry:
Body of the log entry.

Supplemental:
Body of the supplemental entry. Used for additions, corrections or other comments regarding the original entry.

 

 

2017  First Expeditionary Fleet