Operations Billet Specialty Operations Billet Specialty SURFACE WARFARE OFFICERS SCHOOL COMMAND
DEPARTMENT HEAD COMBAT SYSTEMS
NEWPORT, RHODE ISLAND
02841-5012
INFORMATION SHEET
TITLE: FORMATTED MESSAGES REV 2/96
OPERATIONS OFFICER SPECIALTY
LESSON TOPIC: 72.10
REFERENCES:
a. COMNAVSURFLANT/COMNAVSURFPACINST 3502.2B (SURFTRAMAN)
b. NWP-10-1-10 (Operational Reports)
c. APP-4, Vol. I
I. TRAINING REPORT (TRNGREP)
A. References: COMNAVSURFLANT/COMNAVSURFPACINST 3502.2B (SURFTRAMAN) and Bulletins
B. Background: The TRNGREP is a report of great importance to Operations Officers. It is used to update the type commander's (TYCOM) data base of exercises and inspections completed by your ship. The exercises completed are an input to the SORTS for the CRTNG resource area and the associated mission areas (AAW, MOB(N), etc.). This data is valuable to your ship when it's time to prepare your Battle "E" nomination, to document qualification for departmental awards and for other historical recaps.
C. Periodicity: There is no specific periodicity for TRNGREP submission. Rather, a TRNGREP should be submitted as frequently as is needed to keep the TYCOM's data base current. Logical times to submit your TRNGREP might be when returning to port (to cover brief underway periods) and when getting underway. As a minimum, submit reports monthly to reach the type commander by the last day of the month.
D. Classification: TRNGREPs are classified confidential.
E. TYCOM Readiness Management System (TRMS): Designed to streamline training reporting procedures and simplify M-rating computations. The TRMS system tracks training accomplishment, computes scores and exercise caps, generates monthly TRNGREP, and generates a detailed training status summary report. Whenever you update exercises, TRMS puts them in a cue for your next TRNGREP. When you generate your message, all updates since your last message will be included in it.
F. Message Format and Content (found on pg. 6-2-4 of SURFTRAMAN)
1. DO NOT use GENADMIN format for TRNGREP
2. Classification/SSIC line
3. Message identifier line. "TRNGREP", serial number (001-999), "AS OF" date-time-group (in zulu time).
4. Reporting unit identifier line. Ship's hull number, name and UIC.
5. Training data lines.
(a) (b) (c) (d) (e) (f)
N61102123456 / 950101 / 0 / 0982 / A / AAW-3-I
a. Twelve digit exercise code assigned by the type commander. Taken from the type commander's monthly exercise and inspection status report (TRA).
b. Date of exercise completion. A six digit code in year, month, day format.
c. A single digit evaluation code, usually either "0" or "2", signifying the exercise as observed or self-observed respectively.
d. Grade/hours/percent. A four digit number. Furthest right position is tenths when reporting a grade or percentage. If none, use "NONE".
e. An alpha code of "A" meaning add, "D" for delete, or "R" for reset.
f. The exercise/inspection/qualification/assist visit title as reflected on the monthly training summary from the type commander (e.g. MOB-N-1-SF, OPPE, HARPOON CERT, etc.).
6. Gram analysis data. For ASW capable ships, each analyst will be assigned an exercise code taken from the list appearing in the inspections/evolutions section of the type commander's monthly TRA. The analyst will retain this exercise code for reporting purposes until transferred. Total hours of gram analysis training during the last six months will be reported each month for each analyst on board. Format as follows:
exercise code / date / 0 / hours to nearest tenth / A / ANALYST NEC last name rate.
N11053123456 / 950315 / 0 / 1230 / A / ANALYST 0446 SMITH STG1
7. Sonar Contact Time. Report last date on which ship accumulated the required hours for a six month period and total number of contact hours for that period. Required hours to maintain M-1 periodicity over a six month period are found in the SURFTRAMAN ASW Bulletin for each type of sonar contact.
exercise code / date / 0 / hours / A / Sonar Contact Designator
N11052123456 / 950726 / 0 / 0362 / A / CONTACT DIR PATH
N11043123456 / 950714 / 0 / 0460 / A / CONTACT CZ
8. Degaussing status. Report during all training phases the satisfactory or unsatisfactory completion of an entire reciprocal degaussing run. Must be satisfactory in both directions to be considered SATT. If not SATT, report USAT.
N61105620123 / 950513 / 0 / SATT / A / Degaussing Check Range Steel Hull
9. Remarks. The TRNGREP is also used to collect unique information of interest to the type commander, the group commander, and/or ISIC on both a regular and a one time only basis. Information of this type will be reported in the Remarks section of the TRNGREP message if no TYCOM exercise code is assigned.
10. Declassification. "AS OF" date plus six years.
G. Training readiness computation. Computed for each mission area of the ship. (This will be computed by the TYCOM and is not included in ship’s TRNGREP)
Mission area 4(A)+3(B)+2(C)
readiness percentage = 4(A+B+C+D) X 100
A = Total number of exercises at M1 M1 = 1.000 - 0.850
B = Total number of exercises at M2 M2 = 0.849 - 0.700
C = Total number of exercises at M3 M3 = 0.699 - 0.550
D = Total number of exercises at M4 M4 = 0.549 and below
II. LOGISTICS REQUIREMENTS (LOGREQ)
A. Reference: NWP 10-1-10 (Chapter 7)
B. Background:
1. Prior to entering port, ships submit a request for support needed upon arrival via the LOGREQ. Ships proceeding in company usually furnish this information to the senior commander (OTC) for consolidation. The action and information addees on the LOGREQ will vary with each port. The cognizant USDAO, for example, will be the action addee on most foreign port visits. Check the local SOPA regulations and instructions, fleet commander's OPORD, the FLEET GUIDE and PORT DIRECTORY for specific addees required.
2. The stated lead time for LOGREQs is 48 hours. In practice, ships should give as much lead time as they can (a work week is suggested) to ensure a smooth arrival. For many foreign ports or U.S. ports which do not frequently support navy ships, a much longer lead time (perhaps a month) may be required. This is especially critical if complicated requirements are being requested.
C. Classification: LOGREQs are not normally classified. Chapter 7 of NWP 10-1-10 contains instructions for classified movements. If transmission of classified information is unavoidable, consolidate it in a separate message and reference it in the unclassified LOGREQ. LOGREQs are disseminated to many parties without clearances (ship's chandlers and other suppliers) and classification of the LOGREQ impedes dissemination of the message.
D. Gathering Information for the LOGREQ:
1. During the week that precedes the transmission deadline for the LOGREQ, gather information from other ship's officers for inclusion in the LOGREQ:
a. Chief Engineer: fuel and water requirements, CASREP or techrep assistance on arrival.
b. Supply Officer: provisions
c. Weapons Officer / 1st LT: retrograde off load, deck equipment (paint float, camels) needed.
d. Transportation Officer: ship's vehicles
e. Navigator: Sea buoy arrival time, Notice to Mariners, Local Notice to Mariners, Broadcast Notice to Mariners, and HYDROPAC / HYDROLANT numbers.
f. Air Officer: fly-off information.
2. LOGREQs for ports other than your home port may also require inputs regarding tour and/or hotel arrangements, banking and currency exchange, request for official calls, information for general visiting on your ship, free pratique request or arrangements for athletic events. Be sure all personnel with an input have the opportunity to make an input the first time thereby minimizing the number of LOGREQ changes required.
III. STRUCTURED MESSAGES
A. Reference: APP-4 (A) Vol. I
B. General formatting guidelines:
a. Each message contains a message identification line followed by a series of line sequences. Each sequence begins with an alpha-numeric identifier, a slant, and then a self-explanatory abbreviation which indicates what kind of data is found in that sequence.
b. Each data element can be separated by a slant, or a paragraph/subparagraph format can be used.
c. DO NOT use slants within data elements. Periods and hyphens can be used. Use "NA" for elements which do not apply.
d. Data elements and sequences can be amplified and repeated in various ways. Follow instructions in Ref A.
e. Changes can be promulgated by either deleting and adding sections of a previously promulgated message or by promulgating an entirely new replacement message.
IV. OPSTAT RASREQ
A. References: APP-4(A) Vol. I
Fleet Replenishment Guides (CNSLINST C9010.1/CNSPINST 3180.2)
B. Background - The various types of replenishment messages are:
1. OPSTAT RASREQ: Signals RAS requirements to the OTC and/or the CLF ship
2. OPTASK RAS: the OTC/URG commander's or replenishment ship's confirmation message, containing details of the UNREP event.
3. OPSTAT RAS: UNREP ship provides details of rigs and stations.
4. OPSTAT CARGO: CLF ship report of major cargo remaining after an UNREP.
C. Classification:
1. Normally, position/movement data will classify a replenishment, although transferring some types of cargo may as well.
2. The contents of an OPSTAT RASREQ "standard replenishment" in peacetime, which includes only fuel and provisions, is not confidential.
D. Gathering information for the OPSTAT RASREQ - The very nature of a RAS, be it VERTREP or CONREP, suggests that you have to get it right the first time. Therefore, when planning for a RAS, ensure you receive inputs from the following personnel:
1. Weapons Officer / 1st LT: armament, rig preferences and limitations. You will not always be able to resupply from the side you prefer. Therefore, if there is a real limitation, make sure your message is clear on this point. Your Fleet Replenishment guide contains RAS station compatibility information which is needed to plan the RAS.
2. Chief Engineer: fuel required.
3. Supply Officer: supplies. The SUPPO normally conveys his needs to the replenishment ship via SEPCOR, but you should confirm these arrangements prior to sending the OPSTAT RASREQ.
4. If it is appropriate, try to conduct advance liaison via TGO with the CLF ship Operations Officer for rendezvous information and other arrangements.
E. Timeliness:
1. A frequent criticism from CLF ships is that RAS messages are not submitted in a timely manner. Failure to provide an adequate lead time frustrates everyone's planning efforts.
2. In the absence of other guidance, give the replenishment ship 48 hours to plan the UNREP and promulgate the OPTASK RAS. If you are using record message traffic, allow 72 hours; for TGO and flashing light, somewhat less.
V. OPSTAT UNIT
A. Reference: APP-4(A) VOL I
B. Writing the Message:
1. The message is lengthy. If you are building the database for the first time or you are verifying information, ensure that you allow yourself plenty of time to contact personnel on your ship in a position to verify or provide the data you need.
2. Keep the OPSTAT UNIT information in a database once it is collected to simplify later submissions. Ensure, however, that this information is reviewed frequently for currency. Operational Commanders use this information in exercise planning, to determine the tactical employment and disposition of forces assigned and to determine warfare commander assignments.
C. Operational Use of the Message:
1. Keep copies of your ship's OPSTAT UNIT in the OOD Notebook along with those for the other ships with which you are operating. Doing so will provide the most accurate information available regarding the capabilities of ships in company.