JOINT PUB 1-03

JOINT REPORTING STRUCTURE

(JRS)

GENERAL INSTRUCTIONS

10 January 1994

DTK QUALITY IHSPECTED 4
A large body of joint doctrine (and its supporting tactics, techniques,

and procedures) has been and is being developed by the US Armed Forces

through the combined efforts of the Joint Staff, Services, and combatant

commands. The following chart displays an overview of the development

process for these publications.

MAKING A JOINT PUB

All joint doctrine and tactics, techniques, and procedures are organized

into a comprehensive hierarchy. Joint Pub 1-03 is located in the

reference series of joint publications.

JOINT DOCTRINE

PUBLICATIONS HIERARCHY

WARFARE

1

REFERENCE

M

MTELU- »0

OPERATIONS

44 M «0

LOOOT1C3 PLANS C*

SYSTEMS

ZL

Joint Pub 1-01, «Joint Publication System," provides a detailed list of

all joint publications. Joint pubs are also available on CD-ROM through

the Joint Electronic Library (JEL). For information, contact- Joint

^OSlflOOO01^

81011'J

"

7

'

700°J

°

int Staff Penta*°n

' Washington, D.C.
OFFICE OF THE CHAIRMAN

THE JOINT CHIEFS OF STAFF

WASHINGTON, O.C. 20318-0001

Reply ZIP Code:

20318-0400 Joint Pub 1-03

10 January 1994

MEMORANDUM FOR: Distribution List

Subject: Joint Pub 1-03, «Joint Reporting Structure (JRS)

General Instructions"

lh* rh!SP

ublifa

tion has been prepared under the direction of

the Chairman of the Joint Chiefs of Staff, it sets forth

fnS n

1

^

and militar

y guidance to govern the joint activities

and performance of the Armed Forces of the United State!

submitter?n^hi°n- f°f

chfn

9

es to this publication should be

er tw^ ;^°! -°f °Perational Plans and Inter2ltll-70ol nt Staff Penta9°

n

' Washington, D.C.

2i.iEE If^fJoln^nleffoTstaffthat * ^T' t0 ^

S^^wl?^ f^^^^is^^oUcät^on0"tnat50"^6

as

r

:re

0nS^sure\on

^fper^s

raf?Sed

^^ t0 thi» **"««<>»

in nl^f

MiHtB

^

Services and other organizations are requested

6

K- u

h

^

S

P

u

5

lication

supersedes Joint Pub 1-03, 30 June 3Q77 which includes Changes 1 through 5. '

U JUne 1977'

l*H^°Ca^

rePfoduction is authorized and access to unclassified

publications is unrestricted. However, access to and

reproduction authorization for classified joint publications

must be in accordance with DOD Regulation 5200 1-R
?HQ

°

nlK fp

Pfoved P

ubs and test pubs are releasable outside

anv n°tat:

n

r°TandS' Services, and Joint Staff. Release of

any joint publication to foreign governments or foreign

Attachfoffice^Jn^rfed.

thr

°V

gh the local embassy9

(Defense

YA*?J r, 5

} t0 DIA Forei9n

Liaison Branch, C-AS1, Room 1A674, Pentagon, Washington, D.C. 20301-6111.

Contro? 1rolf9-

nt

.-°

r this Public

ati°n is the Command,

(J-6)? JoinTs^af? nS'

a ComPuter Systems Directorate

10.^ The Joint Staff doctrine sponsor for this publication is

For the Chairman of the Joint Chiefs of Staff:

T. R. PATRICK

Colonel, USA

Secretary, Joint Staff

Enclosure
Joint Pub 1-03

Distribution:

By Secretary, Joint Staff:

iZ1^

Staff °SD NSA CIA CIO USELMNORAD

FEMA DISA DIA DLA DMA DNA

L

MCCDC JEWC AFSC JDC DISA-JIEO JWFC

Additional copies may be obtained from the Secretary,

Joint Staff (Documents Division).

Five copies each to: Offices of CSA, CNO, CSAF, CMC,

USCG

Twenty-five copies each to:

USACOM USCENTCOM USEUCOM

USPACOM USSOUTHCOM USSPACECOM

USSOCOM USSTRATCOM USTRANSCOM

Additional copies should be obtained from the Military

n^nV^

e a

f

si

9

ned administrative support responsibility by

DOD Directive 5100.3, 1 November 1988, "Support of the

Headquarters of Unified, Specified, and Subordinate Joint

commands.

By Military Services:

Army: US Army AG Publication Center,

2800 Eastern Boulevard,

Baltimore, MD 21220-2898.

Air Force: Air Force Publications Distribution Center,

2800 Eastern Boulevard,

Baltimore, MD 21220-2896.

Navy: CO, Navy Aviation Supply Office,

Distribution Division (Code 03443)

5801 Tabor Ave,

Philadelphia, PA 19120-5000.

Marine Corps: Marine Corps Logistics Base,

Albany, GA 31704-5000.

Coast Guard: Coast Guard Headquarters, COMDT (G-REP)

2100 2nd Street, SW

Washington, D.C. 20593-0001
(INTENTIONALLY BLANK)
Joint Pub 1-03

JOINT REPORTING STRUCTURE—GENERAL INSTRUCTIONS

RECORD OF CHANGES

CHANGE

NUMBER

COPY

NUMBER

DATE OF

CHANGE

DATE

ENTERED

POSTED

BY REMARKS

In accordance with the procedures contained in Joint Pub

^° ' ^

n

?

e recon»n>endations to this publication will be forwarded to

Urgent:

Routine:

TO: JOINT STAFF WASHINGTON DC//J6I/J7-JDD//

Operational Plans and Interoperability

Directorate, J-7, JDD

7000 Joint Staff Pentagon

Washington, D.C. 20318-7000
LIST OF EFFECTIVE PAGES

verifS^ho1"

9 iS 3 liS^ °f effectiv

e pages. Use this list to

-S- fn*?S\currency and completeness of your document. An

O indicates a page in the original document.

PAGE CHANGE

i thru vi o

1-1 thru 1-4 o

II-l thru II-2 o

III-l thru III-4 0

IV-1 thru IV-2 0

V-l thru V-12 o

VI-1 thru VI-2 0

VII-l thru VII-4 O

p

AGE CHANGE

VIII-1 thru VIII-2 0

A-l thru A-2 o

A-A-l thru A-A-2 0

A-B-l thru A-B-4 0

A-C-l thru A-C-4 0

B-l thru B-10 0

C-l thru C-4 o

D-l thru D-4 o

E-l thru E-4 o

li
Joint Pub 1-03

JOINT REPORTING STRUCTURE—GENERAL INSTRUCTIONS

PREFACE

1. Purpose. This publication sets forth doctrine (or

doctrine and selected tactics, techniques, and procedures) to

govern the joint activities and performance of the Armed

Forces of the United States in joint operations as well as

the doctrinal basis for US military involvement in

multinational and interagency operations. It provides

military guidance for the exercise of authority by combatant

commanders and other joint force commanders and prescribes

doctrine (or doctrine and selected tactics, techniques, and

procedures) for joint operations and training. It provides

guidance for use by the Armed Forces in preparing their

appropriate plans. It is not the intent of this publication

to restrict the authority of the joint force commander (JFC)

from organizing the force and executing the mission in a

manner the JFC deems most appropriate to ensure unity of

effort in the accomplishment of the overall mission.

2. APDliraMnn

a. Doctrine (or doctrine and selected tactics,

techniques, and procedures) and guidance established in

this publication apply to the commanders of combatant

commands, subunified commands, joint task forces, and

subordinate components of these commands. These

principles and guidance also may apply when significant

forces of one Service are attached to forces of another

Service or when significant forces of one Service support

forces of another Service.

b. In applying the doctrine (or doctrine and selected

tactics, techniques, and procedures) set forth in this

publication, care must be taken to distinguish between

distinct but related responsibilities in the two channels

of authority to forces assigned to combatant commands.

The Military Departments and Services recruit, organize,

train, equip, and provide forces for assignment to

combatant commands and administer and support these

forces. This authority is, by law, subject to the

provisions of title 10, United States Code, chapter 6,

which is the section that details the authority of

combatant commanders. Commanders of the unified and

specified commands exercise combatant command (command

authority) over their assigned forces. Service component

commanders are subject to the orders of combatant

commanders, and subject to the combatant commander's

direction, are also responsible to the Military

Departments and Services in the exercise of their

administrative and support responsibilities.

in
rAmm^HS pubf^

ation

is authoritative but not directive.

Commanders will exercise judgment in applying the

procedures herein to accomplish their missions. This

doctrine (or doctrine and selected tactics, techniques,

and procedures) should be followed, except when, in the

älrt^tT °,i th-

command"' exceptional circumstances

nlZtl? otherwise, if conflicts arise between the

contents of this publication and the contents of Service

t£ in?— ??' thi

s

.P

ublicati°n will take precedence for

TS?«J r^1J

ie8

*°

f D°int f0rces unless the Chairman of the

2

X

2

fB

°

f

,

S

^

ff

'

nor^lly in coordination with the

other members of the Joint Chiefs of Staff, has provided

aZr^Tient and sP

ecific guidance. Commanders of forces operating as part of a multinational (alliance or

Sonii^010 mill^

ar

y command should follow multinational

doctrine and guidance ratified by the United States. For

doctrine and procedures not ratified by the United

btates, commanders should evaluate and follow the

applicable 1 COrnmand'

s doctrine and procedures, where

process to^aL^n1^

3

'

10

" ?

6tS

?°rth d°ctrine and selected ES» !» govern the joint activities and performance of

the Armed Forces of the United States. It sets forth tht

general instructions, guidelines, and standards to be usld in

l«l °S?ani

2ation

' writing, and promulgation of the

URS? ?hLPn

b

ii •

ati?nS ?f the J

°i"t Reporting Structure

series nf H?-bl;

catlon 1S the keystone document for the JRS

4. Basis.

forcesISNSF)0«

2

'

X DeCember 1986' "Unified Action Armed

5" t. **/?*1"

01

! ?° July

1992' "J

oint Publication System: Joint Doctrine and Joint Tactics, Technioues

and Procedures Development Program.« iecnniques,

c Joint Pub 1-02, 1 December 1989, "DOD Dictionary of

Military and Associated Terms." Y

d. SM-639-69, "Development of a Joint Reporting

Structure." r y

IV
Joint Pub 1-03

TABLE OF CONTENTS

CHAPTER ^

I OVERVIEW I_1

II CONCEPT AND DESCRIPTION IZ_±

III PARTICIPANT RESPONSIBILITIES IH»!

IV CHANGE PROCEDURES Iv_1

V EXECUTIVE SUMMARIES v_±

VI REPORT DESCRIPTION FORMAT VI-1

VII ANNIVERSARY REPORT (ANNREP) VII-1

VIII US MESSAGE TEXT FORMATTING PROGRAM VIII-1

APPENDIX

A INDEXES FOR REPORTING INSTRUCTIONS A_l

ANNEX

A-A ORGANIZATIONAL INDEX A-A-l

A-B SHORT TITLE INDEX A-B-l

A-C REPORT INDICATOR CODE INDEX A-C-l

B DESCRIPTIONS OF INFORMATION ELEMENTS B-l

C DATA RECORD FORMATS c_x

D TRANSACTION CODES D ,

E USERS EVALUATION REPORT E_1
(INTENTIONALLY BLANK)

VI
Joint Pub 1-03

CHAPTER I

OVERVIEW

1. General. This publication provides:

a. The organizational and short title indexes to the

subordinate publications, executive summaries for all

reports in the structure, instructions for the Anniversary

Report, a listing of report indicator codes, and a

discussion of management procedures regarding message text

formatting (MTF).

b. Descriptions of the responsibilities of JRS

participants and the procedures for maintaining,

monitoring, and reviewing the JRS.

c. The general instructions, guidelines, and standards to

?LUS6K "J-th?

or9an

i

za

ti°n, writing, and promulgation of

the subordinate publications of the JRS.

^aff

ar

^

Cipan

!!

P

:

The JRS Primar

y Participants are the Joint

btatt, the combatant commands and subordinate joint forces, the

offIiSe^Tm

d

n

h

?

followin9Def

e*se agencies: 'centra^magery

S^;.(?

I

?

)

i',?efeni,e formation Systems Agency (DISA),

(SS? Di?^ii12

enC"A9?nCy (DJA)'Defense logistics Agency

fDNA ' Jn e2f?-Map?

in

9

A

9?ncy (°MA)' Defense Nuclear Agency (DNA), and National Security Agency (NSA). The Joint

n!lerw

e

.

raJ i-y and En9ine

ering Organization (JIEO), formerly

JRS6 fo^^^tt^rs03 A96nCy (JTC3A)'

iS -sociated'with the

n»h1?^??"l,tl°!! ?f-fhf> JFpt The JRS is asystem of publications detailing standard reports. The JRS has one basic

Sonlr^T0"; J°int PUb 'T03' "

Joint sporting St?uc?ure (JRI) General instructions," with several subordinate publications

JRS ;«trlyH?'U?- the JRS °

r the Joint Pub i-W ser"s ?he JRS basic publication, «General Instructions," provides

i

n

h^CJ-°nS and Procedures for configuration management of the

^ iSatl°

nS ln

."?

e 1

"

03

series. All 1-03 series publications

should comply with the Joint Pub 1-01 format to the maximum

extent possible. All publications in the 1-03 series will be

SS2I?rte2 K° S

CS Instructions in accordance with the schedule developed by the Joint Staff (J7-JDD).

1- plication pr Report Lead Agent fT.ft). Each subordinate

JRS publication and each report within a subordinate JRS

publication has a LA assigned; in most instances they are the

same office, but they may be different organizations, commands,

offices, or persons. For example, the Joint Staff/J6 is the LA

for Joint Pub 1-03.10, but DISA is the LA for the reports The

publication LAs are listed in Annex A to Appendix A of this

publication.

1-1
£• Identification of JRS Repprtp. Reports within the JRS may

be identified in four different ways:

a. Report Title. Each report has a report title, e.g.,

"Commander's Situation Report," "Status of Resources and

Training System." (See Annex B to Appendix A.)

b- Short Title. Most reports also have a short title or

acronym code listing; e.g., SITREP, SORTS. For an

alphabetical listing of report short titles tying them to

the various report titles in the JRS, see Annex B to

Appendix A.

c. identification (Tp) Symbol. JRS reports have an ID

symbol that appears on the first page of each report

description. It is used to identify the location of the

report in the structure. The ID symbol, "Joint Pub

1-03.8-1," indicates that the report (SITREP) is located in

Joint Pub 1-03.8, Chapter I. ID symbols are also found in

Annex B to Appendix A.

d

- Peport Indicator Code.. Some reports have a

two-character report indicator code; only those reports or

computer files that use an 80-character data record format

require a report indicator code. A listing of these codes,

AppendixSA

tltlC and report title'is found in Annex C to

6

' fficvitive frunmariPF. Chapter V provides a summary of each

hv ,hTrf*n It summariesare arranged in alphabetical order

nr ?2f ^"^ £

he J

?

SYmho1 and title are al*° shown. They provide a brief description of the report, the sender, the

receiver, when and how it is transmitted, and whether it is in

US Message Text Format (USMTF).

7. Bfiggongibilitiep. The JRS participants have specific

responsibilities for monitoring, maintaining, and reviewing the

JRS. These are outlined in Chapter III.

8. Change Procedure?;, changes to the JRS may be proposed by

any of the participants. Changes will be processed by the

publication or report LA in accordance with CJCSI 5711 01

"Policy on Action Processing." Chapter IV outlines these'

procedures.

9

1 Eeport Description Format. Chapter Vl details the format

J^Iel°Ttdescription, a standard arrangement of paragraphs

and headings for all reports in the JRS.

10. Anniversary Report. The Anniversary Report (ANNREP)

requests inputs from both preparers and users of all joint

reports to aid in the monitoring and review process.

Instructions for the ANNREP are in Chapter VII.

1-2
Joint Pub 1-03

11

• Message Text Formatting. The DOD program to apply USMTF

methodology to all reports includes the JRS. Such formatting

will be accomplished in accordance with the procedures in JIEO

(JTC3A) Circular 9000 and the Joint Pub 6-04 series (which will

be revised in the CJCSI 5725- series of instructions). The

message text formatting program is described in Chapter VIII.

\

2

'. Temporary Report. The Temporary Report (TEMPREP) was

designed to be used when a one-time reporting requirement

existed or when the urgency of the reporting requirement was

sucn that formal coordination was not feasible. The

availability of standardized reports in USMTF format, e.g.,

GENADMIN, has obviated the need for the TEMPREP

1-3
(INTENTIONALLY BLANK)

1-4
Joint Pub 1-03

CHAPTER II

CONCEPT AND DESCRIPTION

1

- Features of the» Joint Reporting Strurbirp

a. The JRS satisfies:

(1) The National Command Authorities (NCA) need for

military information to perform their functions.

(2) The JRS participants' need for a central catalog

of recurring reports to support command decisions

regarding military operations and minimize duplicative

reporting.

(3) The general need for standardization in reporting

systems of the Joint Staff, combatant commands and

subordinate joint forces, Services, and DOD agencies.

(4) The need for central management and standard rules

regarding the application of USMTF to reporting systems.

b. The JRS provides:

(1) A standard procedure to ensure coordination of

changes to the JRS.

(2) Standardized formats for report descriptions,

executive summaries, and data transmission formats.

(3) Standardized information element definitions,

transaction codes, and report indicator codes.

(4) Standardized formats for messages, sets, fields,

and data elements associated with message text

formatting.

2. Concept. The JRS reports are a major information source

for the National Military Command System (NMCS). They provide

information to the command centers of the NCA, Chairman of the

Joint Chiefs of Staff, commanders of combatant commands and the

subordinate joint force commanders, Defense agencies, and the

Services. Thus, the JRS covers numerous functional areas, such

as personnel, materiel and equipment status, operation and

logistic planning, situation monitoring, and intelligence, as

well as actual military operations and exercises.

3. Description of the JRS Publications

a- The Joint Pub 1-03 Series. JRS Reports. The JRS is

composed of multiple subordinate publications. Each

publication contains descriptions of reports within similar

functional areas.

II-l
The JRS reports described in these publications may contain

supplemental instructions to handle unique reporting

characteristics.

b. Information Kl^mpnf pfanH?r^p JRS participants will

use standards established through the DOD standard data

administration program. See DOD Directives 5000.12M,

7750.5, 8320.1, and 8320.IM (Draft - issued as interim

guidance).

II-2
Joint Pub 1-03

CHAPTER III

PARTICIPANT RESPONSIBILITIES

j' P

ir

e^pr for Command, Control. Cr>nmmni,cations. and Comon^r

Systems (J-fi>. ^mt si-affvw K

a. General. In matters relating to the JRS in general,

the J-6, Joint Staff, has the responsibility to:

(1) Coordinate changes and guidance for operation and

maintenance of the JRS in accordance with this

publication, CJCSI 5711.01, and Joint Publication 1-01.

(2) Administer, publish, and maintain the JRS.

(3) Monitor the overall effectiveness of the JRS and

propose changes when necessary.

(4) Be the central point of contact for all matters

concerning the JRS and effect coordination between the

participants in accordance with Chapter IV.

(5) Be the LA for Joint Pub 1-03, "Joint Reporting

Instructions (JRS) General Instructions."

(6) Be the component data administrator within the Joint Staff.

5oin?

R

p,,he?

P

n^' -

n ma"ers relating to JRS reports in the

JP1HH-?"J series, the J-6, Joint Staff, has the responsibility to:

(1) Determine the publication or report LA for an

information requirement.

(2) Coordinate reviews of JRS reports to ensure the

reports continue to satisfy information needs and,

where appropriate, to initiate additions, deletions, or

modifications of reports.

(3) Assign report indicators to all information

requirements.

2. JIRS_LA5.. Each JRS publication has an LA assigned. Reports

?? ^publication also have an LA assigned. The publication

LA and the report LA may not be the same.

a. JRS publication LAs have the responsibility to:

(1) Coordinate reviews of their JRS publications and

related reports. Reviews will be completed on a

5-year cycle, as a minimum, beginning with the

III-l
effective date of the publication or the last change

onrrfe^

Urri

"

9 CVery 5 years upon completion of the most current review.

(2) Coordinate new reporting requirements within the

areas of their publication and participate in the

requirements validation process for JRS reports.

b. JRS report LAs have the responsibility to:

5iLJ^ermine information requirements within their

respective areas of responsibility and participate in

the requirements validation process for JRS reports.

(2) Determine, before developing a new reportinq

th?nnohmen- ' "

hether such * requirement can be met through existing reports.

of>dataninSr-

t

-?-

J

?

S rep0rt f0r ^^y and validity of data and initiate any necessary corrective action.

(4) Be the single point of contact for coordinating

and processing changes to the report. "pacing

3. Services. The Services have the responsibility to:

a. Designate to the J-6 Directorate, Joint Staff a noiniSncXSS tneh

JRn

S?

he

^^ »"*» ".„ f£'2i LlllTs

and/or publication LA include approved changes in the JRS?

C

K D

etermin

e, before issuing a new reporting reouiremenf

whether such a requirement can be met through existing joint or Service reports. 9

existing

the JoInrP^

S

i

r

n?

0rtS

-

and f

°

rWard Pr

°P°sals for changes to the Joint Pub 1-03 series to the publication LA, in

accordance with Chapter IV.

®* *

ssue supplements at their discretion. Before

publication, the Services will forward supplements to the

publication or report LA for coordination.

f. Establish data administrators for Service-unique reporting systems. unique

4

' Pefense Agencies. The Directors, CIO, DISA, DIA DLA niwa

DNA, and NSA have the responsibility to: ' '

III-2
Joint Pub 1-03

a. Review their existing reporting systems and forward to

the J-6 Directorate, Joint Staff, the reports that are

appropriate for inclusion in the Joint Pub 1-03 series.

b. Designate to the J-6 Directorate, Joint Staff, a point

of contact within the agency headquarters for all matters

concerning the JRS.

c. Review JRS reports and forward proposals for changes to

the Joint Pub 1-03 series to the publication or report LA,

in accordance with Chapter IV.

d

u . J

etermine' before issuing a new reporting requirement,

whether such a requirement can be met through existing

3omt or Service reports.

5. Commanders pf Combatant Commands.. Commanders of combatant

commands have the responsibility to:

a. Develop a single reporting structure that provides the

information required by the NCA, Chairman of the Joint

Chiefs of Staff, subordinate joint forces, and component

commands and their headquarters. Commanders should make

maximum use of the JRS and existing Service reports.

O'K ?°üitorreporting requirements appearing in the Joint

ZU 1-P

3

.

ser

i

es

and recommend changes for improvement to

the publication or report LA.

c. Where necessary, publish supplements to JRS

publications.

III-3
(INTENTIONALLY BLANK)

III-4
Joint Pub 1-03

CHAPTER IV

CHANGE PROCEDURES

General

?;.^Cha??

eS t0 the

.

JRS ma

y include policy, procedures, or

instructions; new information requirements or data

elements; or revisions or deletions of existing JRS

publications or reports. Any one of the JRS participants

may originate a change proposal to the Joint Pub 1-03

SG3TX6S •

?Arrt,

ChKn

?KSV* ftaffed bv the publication or report LA,

through the Joint Staff/J-6, as a CJCSI 5711.01 action

Changes are staffed with the Joint Staff/J-7/JDD before

nnai approval, in accordance with Joint Pub 1-01.

lnfJ^t

nt R

?

Pprtl"? Ppquirementp. There may be occasions when

information is required sooner than a change proposal can be

reauir^n?-^^5111119 °

ffice wil1

U

coordinate ?he urgent

f "ith^

he a

PP

r

°Priate publication or report LA and

f??if* D^

rectorate

-

J

oint Staff; the requirement will be

iiiü! USin9 5

n existinq rePort or standardized report in

USMTF, e.g., GENADMIN (see Chapter VI). Should this urqent

o

r?Iicere"n SiS:^0

H

3 recurri*9 -port, the requesting' ottice wxll initiate a change procedure to formalize the report.

3

- Changes to Sprvjr^e Retmrt-p

Jh« l

hB ?inal resPonsibility for Service reports rests with

th?. .hi1?

6 concerned. The change procedures sit forth in

re

h

po

SrtC?ngPt^ystaer:sn0t ^^ t0 r6gUlate the Se

~

ic

*

be made°avai5^hir^rt^

in Service-controlled reports may De made available to other organizations with the

concurrence of the controlling Service. The Services will

fndninLrLf?-

mati0n ?ertinent to joint plans oToperltTons and information requirements of the NMCS.

IV-1
(INTENTIONALLY BLANK)

IV-2
Joint Pub 1-03

CHAPTER V

EXECUTIVE SUMMARIES

1. This chapter contains summaries of each report in the JRS

Each summary presents a brief description of the report? the

"rS« VieiS£Je£'

Wh

r

and h

°

W U is

it nas a USMTF format. t^nsmitted, and whether

titleaCh rePOrt iS identified by acronym, report symbol, a

3

- Guide to Abhrpv? afi nn«.

One asterisk (*) indicates reports under staffing.

ICP Interface Change Proposal Pending.

JUH JIEO (JTC3A) Handbook 9000, "Joint User Handbook."

nd

Report Summaripp

AAR

ANNREP

APORTSREP

TO

WHEN

HOW:

1-03.30-1 JOINT AFTER-ACTION REPORTING SYSTEM

Provides the official description of an operation

or exercise and identifies significant lesson(s)

learned.

FROM: Supported combatant command; supporting

combatant commands, Services, and agencies.

as directed.

Joint Staff/j-7, EAD.

Within 60 days after completing an

operation or exercise, not including

redeployments.

Submitted in two formats. Joint Universal

Lessons Learned (JULLS) computer

program-generated data, delivered by mail

courier, or WWMCCS Intercomputer Network

(WIN). Paper copy format delivered by mail

or courier.

1-03-7 ANNIVERSARY REPORTS REVIEW

Facilitates monitoring and review of all ioint

reports. J

FROM: Joint Staff, combatant commands, Services

and agencies. '

Joint Staff (J6I).

31 August, 1 year before the 5-year

anniversary review of the applicable

publication.

Letter, message.

TO:

WHEN:

HOW:

1-03.25-1 AERIAL PORTS AND AIR OPERATING BASES

REPORT

Provides airport operation characteristics.

FROM: Combatant commands, supporting and

component commands, and Defense aqencies

TO: DISA WASHINGTON DC //JNCP//.

V-l
WHEN:

HOW:

Quarterly (JAN, APR, JUL, OCT).

Defense Message System (DMS(AUTODIN)), data

format.

ASSETSREP 1-03.23-1 TRANSPORTATION ASSETS REPORT

Reports availability of common-user sealift and

airlift assets.

FROM: USCINCTRANS.

DISA WASHINGTON DC //JNCP//

Biennially, or within 90 days subsequent to

Joint Staff approval of Annex J to JSCP

Approved changes that occur between

editions of Annex J will also be reported

within 90 days.

DMS(AUTODIN), data format.

BULLETIN

CEDREP

CEF

CEPODA

TO:

WHEN :

HOW:

1-03.15-5 NATIONAL MILITARY JOINT

CENTER BULLETIN

Provide timely notification of fast

real-world and exercise events that

immediate impact on US plans, opera

equipment, or personnel.

FROM: Joint Staff (J2).

Defense Address Group (DAG)

Special Intelligence (SI) t

addressees in the Pentagon.

Direction of Duty Director

in the National Military Jo

Center.

Message and/or courier.

NMJIC BULLETIN (JUH).

TO:

WHEN:

HOW:

USMTF:

INTELLIGENCE

-breaking

could have an

tions,

KODAV for

raffic; selected

for Intelligence

int Intelligence

1-03.11-1 COMMUNICATIONS-ELECTRONICS DEPLOYMENT

REPORT

Monitors movement and status of contingency

communications equipment.

FROM: Equipment custodians.

W»S!: "fc1

^

Sta?f (J6) and Services.

2

5 days after deployed on site.

HOW: Message; mail during MINIMIZE.

1-03.27-1 CIVIL ENGINEERING FILES

Reports standard planning factors for civil

engineering support plan of joint OPLANs

FROM: USA, USN, USAF, USMC.

TO: Joint Staff.

WHEN: l April or as changes occur.

HOW: Data format, hand delivered.

1-03.11-2 COMMUNICATIONS-ELECTRONICS

POST-DEPLOYMENT (A)

Provides performance and utilization of contingency

communications equipment from responsible custodian

FROM: Equipment user. '

V-2
Joint Pub 1-03

CEPODB

CHSTRREP

COMSPOT

COMSTAT

CRAFREP

TO:

WHEN:

HOW:

Joint Staff (J6), Services, DISA.

15 days after deployment ends.

Message; mail during MINIMIZE.

1-03.11-3 COMMUNICATIONS-ELECTRONICS

POST-DEPLOYMENT (B)

Reports performance and utilization of contingency

equipment from user.

FROM: Combatant commands, Services, and agencies

TO: Joint Staff (J6).

WHEN: 15 days after deployment ends.

HOW: Message; mail during MINIMIZE.

1-03.24-1 CHARACTERISTICS OF TRANSPORTATION

RESOURCES REPORT

Provides planning factors and characteristics of

certain sea and air vehicles.

FROM: USCINCTRANS.

Joint Staff (J3/J4).

In conjunction with ASSETREP file

information (biennially), or within 90 days

subsequent to Joint Staff approval of any

new or revised Annex J to JSCP.

DMS(AUTODIN), data format.

TO:

WHEN:

HOW:

1-03.10-2 COMMUNICATIONS SPOT REPORT

Provides near-real-time status information on a

serious degradation of the Defense Communications

System.

FROM:

TO:

WHEN:

HOW:

USMTF:

DISA.

Joint Staff (J3/J6), combatant commands,

Services, and agencies.

When occurs.

DMS(AUTODIN).

COMSPOT.

1-03.10-1 COMMUNICATIONS STATUS REPORT

Provides a summary of significant status

information on Defense Communications System

elements.

FROM: DISA.

Joint Staff (J3/J6), combatant commands,

Services, and agencies.

Daily as of 0800Z or as directed by the

Joint Staff.

DMS(AUTODIN).

GENADMIN.

TO:

WHEN:

HOW:

USMTF:

1-03.18-4 CIVIL RESERVE AIR FLEET SUMMARY REPORT

Reports status of Civil Reserve Air Fleet

FROM: USCINCTRANS.

TO: AIG 932.

WHEN: As directed by Joint Staff.

HOW: Message.

V-3
CSADR 1-03.32-2 COMBAT SUPPORT AGENCY DIRECTOR'S REPORT

Provides a biennial appraisal of an agency's

responsiveness and readiness to support the

combatant commands. It consists of two parts—the

CSADR Narrative Report and the CSADR Detailed

Assessment. The Narrative Report summarizes

overall agency preparedness, in terms of JSCP

taskings, to support the combatant commands and it

documents the agency director's top 20

responsiveness or readiness shortfalls. The

Detailed Assessment is a data base of individual

concerns or deficiencies and of summary reports of

agency capability to support each CINC.

FROM: Combat support agencies.

TO: AIG 951 (Narrative Report);

Joint Staff, J-7/EAD (Detailed Assessment).

WHEN: Biennial (normally 31 December of odd

years).

HOW: (Narrative Report) Defense Message System

(AUTODIN).

(Detailed Assessment) WWMCCS data file or

floppy disc.

CSPAR 1-03.31-2 CINC'S PREPAREDNESS ASSESSMENT REPORT

Provides a biennial appraisal of the unified and

specified commands to accomplish JSCP tasks within

the constraints of apportioned forces. It consists

of two parts—the CSPAR Narrative Report and the

CSPAR Detailed Assessment. The Narrative Report

summarizes overall preparedness in terms of JSCP

taskings and documents the CINC's top 20

preparedness shortfalls. The Detailed Assessment is

a data base of individual concerns and deficiencies

(ICADs) documenting specific capability shortfalls,

and CINC summary reports (CSRs) assessing overall

capability in particular warfare or functional

areas. CSRs are also included on each of the

combat support agencies, assessing their

responsiveness and readiness to support the

operating forces in time of war.

FROM: Combatant commands.

TO: (Narrative Report) AIG 951.

(Detailed Assessment) Joint Staff, J-7/EAD.

WHEN: Biennial (normally 15 August of odd years).

HOW: (Narrative Report) Defense Message System

(AUTODIN).

(Detailed Assessment) WWMCCS data file.

DISUM 1-03.15-3 DAILY INTELLIGENCE SUMMARY

Provides daily analysis of actual or exercise

crisis situation and intelligence produced.

FROM: CINCs, Services, and DIA.

TO: As appropriate.

WHEN: As directed.

V-4
Joint Pub 1-03

HOW:

USMTF:

Message,

DISUM.

GEOREQ 1-03.19-1 SPECIFIED GEOLOCATION CODE REQUEST

Standardizes data codes representing geographic

locations of military installations. Supports

SORTS and others. PF^Uö

FROM: Combatant commands, Services.

TO: DISA WASHINGTON DC //JNCP//.

WHEN: Changes occur; originator option.

HOW: DMS(AUTODIN), data format.

INTELSITSUM 1-03.15-4 INTELLIGENCE SITUATION SUMMARY

Provides periodic summaries of actual or exercise

crisis situations that could affect US operations

JADREP

JCASREP*

JOPESREP

FROM:

TO:

WHEN:

HOW:

USMTF:

DIA.

For real world crises:

1. DAG KODAV for SI information only.

2. Selected addresses in Washington,

D.C., by courier.

For exercise*: AIGs and DAGs provided

1200Z and 2400Z when directed to the Duty

Director for Intelligence or the

Intelligence Task Force Commander.

Message or courier.

INTELSITSUM (JUH).

1-03.12-1 JOINT RESOURCE ASSESSMENT DATA BASE

REPORT

Reports materiel status of static military

resources.

FROM:

TO:

WHEN:

HOW:

USMTF:

Combatant commands, Services.

DSSO (DISA WASHINGTON DC //JNGA//),

cognizant combatant commands, and Services

Review annually, submit as changes occur.

DMS(AUTODIN), data format or message.

ICP.

1-03.17-2 JOINT CASUALTY REPORT

Provides data on personnel strength and casualties

under the operational control of a combatant

commander.

FROM:

TO:

WHEN:

HOW:

USMTF:

1-03.21

Services.

Joint Staff (Jl).

By 0400Z as of 2359Z the day before

DMS(AUTODIN), immediate, free-form message

format.

GENADMIN (JUH).

JOINT OPERATION PLANNING AND EXECUTION

REPORTING SYSTEM

Provides time-phased force and deployment data

(TPFDD) among the commands and agencies involved in

joint planning and execution activities.

V-5
FROM:

TO:

WHEN:

HOW:

Combatant commands, Services, and selected

DOD agencies.

Joint Staff (J3), combatant commands,

Services, and selected DOD agencies.

Situationally dependent.

WWMCCS, DMS (AUTODIN), or appropriate

backup.

MID

LOGFACREP 1-03.28-1 LOGISTIC FACTORS REPORT

Provides data for Logistic Factor file in support

of joint operation planning.

FROM: USA, USN, USAF, USMC, DLA, CINCs.

TO: Joint Staff (J4).

WHEN: Annually.

HOW: DMS(AUTODIN), data format.

1-03.15-1 MILITARY INTELLIGENCE DIGEST

Provides timely, finished intelligence regarding

events that could have a significant effect on

ruture planning and operations.

FROM: DIA, combatant commands, Services T0: For rpal world 0^^.

1. For CONFIDENTIAL or SECRET: current

2. DAG KODAV for SI information.

Releasable to Canada: Combat

Communications Sguad and National Defence

Headquarters, Ottawa.

For expr^ipfog1. For CONFIDENTIAL or SECRET: current

2. EXDAG for SI information.

By 2000Z each day when:

1. Defense Condition (DEFCON) 3 or

higher is in effect or when significant

politico-military situations require.

2. Directed by CJCS.

3. Anytime reporting activity deems

appropriate.

Message.

MOBREP*

WHEN:

HOW:

1-03.17-1 MILITARY MANPOWER MOBILIZATION AND

ACCESSION STATUS REPORT

Provides tabulated total force manpower data during

TMTM°

ds °f crises' emergencies, or exercises. FROM: Services.

Joint Staff (Jl).

By 2359Z as of 1600Z.

1. As directed by the Joint Staff.

2. Automatically upon mobilization

DMS(AUTODIN), immediate, free-form message

format. a

GENADMIN (JUH).

V-6

TO:

WHEN :

HOW:

USMTF:
Joint Pub 1-03

MUREP

NICKA

NUDETSUM

NUREP

OPREP-1

1-03.18-7 MUNITIONS STATUS REPORT

Provides the ability to monitor critical munition

items worldwide that affect warfighting

capabilities during hostilities, emergencies, or

exercises.

FROM:

TO:

WHEN:

HOW:

USMTF:

Combatant commands less USTRANSCOM and

USSTRATCOM.

Joint Staff (J4).

By 0600Z as of 2400Z the day before:

1. DEFCON 2.

2. Directed by CJCS.

3. When considered appropriate by

reporting commanders.

Immediate message.

MUREP (JUH).

1-03.19-4 CODEWORD, NICKNAME, AND EXERCISE TERM

REPORT

Registers subject terms for use in WWMCCS.

FROM: Combatant commands, Services, and Defense

agencies.

Joint Staff (J36/CSOD).

To register, change, or cancel nicknames.

DMS(AUTODIN), data format or hand deliver.

TO:

WHEN:

HOW:

1-03

Prov

outs

FROM

TO

WHEN

HOW

USMTF

.6-2 SUMMARY OF NUCLEAR DETONATIONS

ides rapid reports of nuclear detonations

ide of North America.

USCINCCENT, USELMNORAD, USACOM, USEUCOM,

USPACOM, USSOUTHCOM.

Per NORAD Manual 55-19, National Military

Command Center, AIG 931.

When occurring.

NORAD Forward Automated Reporting System

(NFARS) voice and Message.

NUDETSUM (JUH).

1-03.7-1 NUCLEAR WEAPONS REPORTS

Describes the Nuclear Weapons Reporting System and

prescribes the procedures for reporting nuclear

weapon information for all DOD storage and

operational custodial units.

FROM: Custodial sites.

TO: Defense Nuclear Agency.

WHEN: Daily (by exception).

HOW: DMS (AUTODIN).

1-03.8-2 OPERATION(S) PLANNING REPORT

Describes plan for military operations for specific

situations.

FROM: Commanders designated in implementer.

TO: As designated in implementer.

WHEN: As specified in implementer.

HOW: Message.

V-7
OPREP-2

OPREP-3

OPREP-4

OPREP-5

POLCAP

PORTSREP

RECON-1

1-03.8-2 OPERATION(S) START REPORT

Executes a plan (fragmentary order) that advises

start of operations in response to OPREP-1.

FROM: Commanders designated in implementer.

TO: As designated in implementer.

WHEN: As specified in implementer.

HOW: Message.

1-03.6-1 OPERATION(S) EVENT/INCIDENT REPORT

Forwards incidents and events of potential

national-level interest.

FROM: Commanders designated in implementer.

As designated in implementer.

As specified in implementer.

Message.

OPREP-3 (JUH).

TO:

WHEN:

HOW:

USMTF:

1-03.8-2 OPERATION(S) STOP/RESULTS REPORT

Reports completion of an operation and

quick-response results.

FROM: Commanders designated in implementer.

TO: As designated in implementer.

WHEN: As specified in implementer.

HOW: Message.

1-03.8-2 OPERATIONS SUMMARY REPORT

Summarizes an operation upon completion.

FROM: Commanders designated in implementer.

TO: As designated in implementer.

WHEN: As specified in implementer.

HOW: Message.

1-03.18-2 BULK PETROLEUM CAPABILITIES REPORT

Provide current data on petroleum operations and

contingency support capabilities for a specific

theater or country.

FROM: Theater combatant commands.

AIG 935.

1 May of each year or as directed by Joint

Staff.

Priority message.

TO:

WHEN:

HOW:

1-03.26-1 PORT CHARACTERISTICS REPORT

Provides characteristics of selected ports

«•«'«•- USN, USTRANSCOM.

Joint Staff (J3/J4).

Quarterly (JAN, APR, JUL, OCT).

DMS(AUTODIN), data format.

FROM

TO

WHEN

HOW

1-03.9-3 RECONNAISSANCE NICKNAME REPORT

Registers nicknames for all reconnaissance

operations.

FROM: Combatant commands.

V-8
Joint Pub 1-03

RECON-2

RECON-3

RECON-4

REPOL

SEV

TO:

WHEN:

HOW:

USMTF:

JOINT STAFF WASHINGTON DC //J-3/JRC//,

JOINT RECONNAISSANCE CENTER WASHINGTON DC.

New nickname activated or existing nickname

changed/deleted.

DMS(AUTODIN), data format.

RECON-l (JUH).

1-03.9-4 RECONNAISSANCE TRACK REPORT

Provides details on reconnaissance track objectives

FROM

TO:

WHEN:

HOW:

USMTF:

Combatant commands.

JOINT STAFF WASHINGTON DC //J-3/JRC//,

JOINT RECONNAISSANCE CENTER WASHINGTON DC.

Additions, deletions, and changes.

DMS(AUTODIN), data format.

RECON-2 (JUH).

1-03.9-5 RECONNAISSANCE SCHEDULING REPORT

Provides details of monthly peacetime

reconnaissance schedules

FROM:

TO:

WHEN :

HOW:

USMTF:

Combatant commands.

JOINT STAFF WASHINGTON DC //J-3/JRC//,

JOINT RECONNAISSANCE CENTER WASHINGTON DC.

15th day of month before.

DMS(AUTODIN), data format.

RECON-3 (JUH).

1-03.9-6 RECONNAISSANCE MISSION FOLLOWING REPORT

Provides notice of reconnaissance mission

1aunch/recovery.

From

To:

WHEN:

HOW:.

Combatant commands.

JOINT STAFF WASHINGTON DC //J-3/JRC//,

JOINT RECONNAISSANCE CENTER WASHINGTON DC.

Within 15 minutes of launch or recovery

event occuring.

DMS(AUTODIN), data format.

1-03.18-1 BULK PETROLEUM CONTINGENCY REPORT

Reports current inventory and deficiencies

affecting bulk petroleum, oil, and lubricant (POL)

supplies, storage, and distribution during periods

of increased tension.

FROM: Combatant commands, Defense Fuel Supply

Center, and USAF.

AIG 935.

Every 48 hours during DEFCON 1. Twice

yearly under peacetime conditions.

Immediate message (DEFCON 1).

Routine message (peacetime).

REPOL (JUH).

TO:

WHEN:

HOW:

USMTF:

1-03.7-4 STOCKPILE EMERGENCY VERIFICATION

Determines validity of suspected loss of nuclear

weapons and components.

V-9
SIR

SITREP

SORTSREP

FROM:

TO:

WHEN:

HOW:

Reporting units, Service logistic agencies,

inventory control locations.

DNA.

When initiated by Joint Staff.

Voice or message.

1-03.7-5 SEMIANNUAL INVENTORY REPORT

Reconciles DOD, Department of Energy (DOE), DNA,

combatant commander, and Service records with

physical inventories.

FROM: Custodians.

TO: DNA, combatant commands, Services.

WHEN: Semiannually. Report month varies by

command.

HOW: DMS(AUTODIN).

1-03.8-1 COMMANDER'S SITUATION REPORT

Keeps the NCA, Chairman of the Joint Chiefs of

Staff, combatant commanders, and Services apprised

of combatant commander's significant events,

n!!o^i9e?i:e\.

0rce disposition, etc., and assesses

nlSEl situation. Also submitted semiannually by combatant commanders.

FR?oi A?Gb

93fnt COmmands'

Services, and agencies.

WHEN: DEFCON 4 and 5: Daily as of 2400Z, as

required by the situation, or as directed

by CJCS.

Message.

SITREP (JUH).

Joint Staff.

AIG 7044.

DEFCON 4 and 5;

Message.

SITREP (JUH).

AIGb934nt COmmands'

Services, and agencies,

DEFCON 1-3: Daily as of 2400Z.

Message.

SITREP (JUH).

Joint Staff.

AIG 7045.

DEFCON 1-3: As required by situation.

Message.

SITREP (JUH).

HOW:

USMTF:

FROM:

TO:

WHEN:

HOW:

USMTF:.

FROM:

TO:

WHEN:

HOW:

USMTF:

FROM:

TO:

WHEN:

HOW:

USMTF:

As required by situation.

1-03.3 STATUS OF RESOURCES AND TRAINING SYSTEM

JOINT REPORT

Provides the National Command Authorities with

authoritative identity, location, and resource

information on operational units of the Armed

Forces.

FROM: Combatant commands, Services, major

commands, or subordinate units.

V-10
Joint Pub 1-03

SPIREP

TEDREP

TUCHAREP

WSR

WSR-EMERG

TO:

WHEN :

HOW:

USMTF:

Joint Staff (J3), combatant commands,

Services, and major commands.

As changes occur.

DMS(AUTODIN) or WWMCCS Information System

Message;

SORTSREP.

1-03.15-2 SPOT INTELLIGENCE REPORT

Reports intelligence of immediate significant

impact.

Combatant commands, Services.

AIG 930.

When occurring.

Message, voice to NMCC if very urgent.

SPIREP (JUH).

FROM:

TO:

WHEN:

HOW:

USMTF:

1-03.22-1 TYPE UNIT EQUIPMENT DETAIL REPORT

Provides data for the Type Unit Eguipment Detail

(TUDET) file.

FROM: USA, USN, USAF, USMC.

TO: DISA WASHINGTON DC //JNCP//.

WHEN: Quarterly validation, as required.

HOW: DMS(AUTODIN), data format or hand delivered,

1-03.29.1 TYPE UNIT CHARACTERISTICS REPORT

Registers standard codes for military organizations

and compiles transportation data

FROM

TO:

WHEN:

HOW:

Combatant commands, Services, and agencies

DISA WASHINGTON DC //JNCP//.

1. A new organization requires

identification.

2. Revised organization data, within 30

days of revision.

3. Organization deleted from force

structure.

4. Quarterly by 20th of Mar, Jun, Sep, Dec

WIN terminal, data record, or hand carried.

1-03.7-2 WEAPONS STATUS REPORT

Provides data on nuclear warheads and war reserve

components of nuclear weapons.

FROM

TO:

WHEN :

HOW:

Custodians.

DNA, combatant commands, Services.

DEFCON 4 and 5: Daily by 1200L for the day

before, if changes occurred.

Message.

1-03.7-3 WEAPONS STATUS REPORT-EMERGENCY

Establishes nuclear weapons reporting procedures

during increased readiness.

FROM: Custodians.

TO: DNA, combatant commands, Services.

V-ll
WHEN: When declared by the CJCS: Twice daily by

0500L and 1700L as of 0100L and 1300L,

respectively, for the day before, if

changes occurred.

HOW: Immediate message.

WSR-EXER 1-03.7-3 WEAPONS STATUS REPORT-EXERCISE

Establishes nuclear weapons reporting procedures

during increased readiness in exercises.

FROM: Custodians.

TO: DNA, combatant commands, Services.

WHEN: When declared by the CJCS: Twice daily by

0500L and 1500L as of 0100L and 1300L,

respectively, for prior day, if changes

occurred.

HOW: Immediate message.

v-12
Joint Pub 1-03

CHAPTER VI

REPORT DESCRIPTION FORMAT

1. General. Align all reports in the JRS in the Standard

arrangement shown below.

PUBLICATION NUMBER

CHAPTER NUMBER

REPORT TITLE

SHORT TITLE

(The short title is an acronym formed from the report title)

REPORT IDENTIFICATION SYMBOL

(The report identification symbol is determined from the

publication and chapter number in which the report

appears. For example, "1-03.11-3" would identify

"Communications-Electronics," and the third chapter.)

2. Format- Describe the details of the report thoroughly with

concise entries under each of the paragraph headings numbered

and highlighted below.

1

- Subject and Purease.. Provide a brief description of

the nature and purpose of the report, indicate implementing

authority or reference for the report.

2. Submitted By. Indicate the agencies or organizations

required to submit the report.

3- Submitted To. Indicate the organizations or agencies

to which the report is made, subdivided into action and

information addressees, as required.

4

- When Submitted. Indicate whether reporting is by

exception, as required, or on a regular basis. If the

latter, indicate the exact time of day when applicable.

Indicate any connections of reporting with DEFCON level.

5. How Submitted

a

- Classification. Indicate appropriate

classification and declassification of reports when

they can be determined in advance; otherwise, the

submitting agency may be required to determine the

proper classification and declassification.

b. Transmission. Indicate the primary and alternate

methods of report submission, i.e., DMS(AUTODIN),

telephone, or mail.

c. Precedence. Indicate the desired precedence

according to type of report and urgency of reported

data. This precedence should be determined in

relationship to all other traffic.

VI-1
d- MINIMIZE. State whether the report should be

submitted if MINIMIZE is in effect. If reporting

during MINIMIZE is conditional, state the exact

circumstances under which reports will continue to be

electrically transmitted. Policy concerning MINIMIZE

is contained in Chapter 3, Section VII, ACP 121, US

Supplement 1.

f• Beport Indicator. The J-6 Directorate will assign a

two-character report indicator code to each report to

facilitate automated transmission and processing of the

report. Identifications will be assigned to nonautomated

as well as automated reports in order to provide for

possible future automation.

7. Specific Reportina InstnifH-i^np Provide information

on specific data to be reported, including any special

notes or instructions that may be applicable. Include any

specialized definitions of information elements.

8. B^P^rtJCQlitent. (Optional) Provide data formats and

examples of fixed entries required for automated reports.

?

r

n;"r

ative-type reports, indicate any paragraph headings

or numbers to be used.

9. Sample Report. (Optional) Provide a sample of what an

actual report should look like where deemed useful for

guidance to agencies that will be submitting or receiving

reports. These samples should include complete

identification and body of the report but may omit

addressing information.

VI-2
Joint Pub 1-03

CHAPTER VII

ANNIVERSARY REPORT

(Short Title—ANNREP)

Joint Pub 1-03-7

lm Subject and Purpose. To provide regular inputs from both

preparers and users of all JRS reports in order to aid in the

JRS reports monitor and review process outlined in Chapter III

of this publication. These reports, which supplement JRS

change proposals, will contribute to the following goals:

a. Reduction of information elements contained in JRS

reports.

b. Reduction of information duplication among different

JRS reports.

c. Reduction, when possible, of the total number of

different joint reports.

d. Updating and maintenance of report addressees and

address indicator groups (AIGs).

e. Validation of information requirements and verification

of reporting intervals.

f. Usefulness of information being reported.

2. Submitter! By

a. Commanders of the combatant commands for all JRS

reports for which they are preparers or recipients,

including exercise reports.

b. The Services, for JRS reports for which Service

headquarters are recipients, including exercise reports.

c. Joint Staff directorates and Defense agencies for all

JRS reports for which an element of the directorate or

agency is a user of information provided by the report.

3. Submitted To. C4 Architecture and Integration Division

(J6I), 6000 Joint Staff Pentagon, Washington, D.C. 20318-6000.

4. When Submitted. Submitted by 30 September, with an "as of"

date of 31 August, 1 year before the 5-year anniversary

revision to Joint Pub 1-03, "General Instructions." (See Joint

Pub 1-01.) Negative reports are required.

5. How Submitted

a« Classificati-Qn. As determined by the originator.

VII-1
b

- Method of Transmission Letter or message.

6- Report Indicator. "XY."

1

• Specific Reporting Instruction* Narrative.

8. Report Content. Reviews should address but not be limited

to the following items:

a. Report title, part, and chapter.

b. State whether report content is:

(1) Adequate for stated purpose.

(2) Overly detailed; which specific data should be

eliminated or summarized.

(3) Insufficiently detailed for stated purpose

(propose specific change).

(4) Redundant to another joint or Service report or to

one in an allied reporting system? Which one? Which

report or portion of a report should be eliminated?

c. State whether the report format is appropriate.

(1) If narrative, should the report or a portion of it

be designed for either data record (card image) formats

or for message text formats? Why?

(

V ,F^data forn>atted, but not to DOD standards,

should formats be revised? Why?

*?*." data formatted, should the report or a portion

of it be converted to narrative or to message text

formats? Why?

d. Addressees. Recommend additions or deletions. Review

AIG composition for completeness, unnecessary addressees,

or overlap. Recommend changes that would eliminate receipt

ot the same information from various sources.

e. Precedence. Review for continued applicability. Could

precedence be lowered during major exercises and crisis

situations?

f. Method of Transmission. Can report be sent by mail

rather than by message? During which periods?

g. When Submitted

(1) Is receipt of information timely? is it often

delayed? Why? is report submission time realistic?

Propose and substantiate change.

VII-2
Joint Pub 1-03

inn,,nh7reE

0rt bein9submifcted

too often or not often enough? Propose and substantiate change.

h. Understandable. Are the reporting instructions easilv

diff,Vn??ded bV

he

P

ersonnel having to use tnem? Identi?y difficulties and propose change. y

9

- Sample Rppnrf- None.

10. Genera]

a. All JRS reports will be reviewed, as provided for

above, with no exceptions. F a £or

t>. Combatant commanders are encouraged to conduct

Anniversary Report reviews of their own reposing

structures, Service publications, and Service suDDlementai

instructions to JRS reports. Such reviSS SuJX

significantly contribute to the review of the JRS reports.

on an

h

«as

e

occu?rfnn« *

nd

.

su^ested

improvements to the JRS

this vo?»mo 9 baS1S'

as Pre

scribed in Chapter IV of cms volume, are encouraged.

d. Every input resulting from the Anniversary Rennrf

rlport LA1' B^SSST* * ^ PP'opri.S'SÄ« or

bl staffed anS ~ 2- pf°P°sedchanges to the JRS will then

eltaM^hfr. ?* coordinated according to procedures

established m Chapter IV. Information copies of inputs to

proposeaCS9

resd

"

1U

"* adViSed °

£ the «»position of

VII-3
(INTENTIONALLY BLANK)

VII-4
Joint Pub 1-03

CHAPTER VIII

US MESSAGE TEXT FORMATTING PROGRAM

1. Introduction. The term "message text formatting" refers to

the conversion of military reports to formats that are common

to all US defense organizations and compatible with NATO

reports. The USMTF program improves interoperability by:

a. Producing messages that can be read by humans and

processed by machines.

b. Reducing the time and effort required to draft,

transmit, analyze, interpret, and process messages.

c. Improving information exchange through vocabulary

control.

d. Providing uniform reporting procedures to be used

across the range of military options.

e. Facilitating exchange of information between the US and

allied commands; reducing or eliminating dual reporting by

US units when they operate with allied commands or units or

after their change of operational control to allied nations

or organizations.

f. Providing, through the Joint Pub 6-04 series and Joint

Pub 3-56.24, the management and documentation for these

standards.

2. Responsibilities

a. Overall responsibility for converting JRS reports to

USMTF is vested in the publication or report LA.

b. The J-6 Directorate monitors these conversion efforts

to ensure:

(1) Compliance with the USMTF program.

(2) That US and allied interoperability requirements

are considered and reflected to the greatest possible

extent.

(3) That the conversion effort is coordinated with the

DOD Data Element Standardization Program.

VIII-1
(INTENTIONALLY BLANK)

VIII-2
Joint Pub 1-03

APPENDIX A

INDEXES FOR REPORTING INSTRUCTIONS

1. General. The three JRS indexes listed in the annexes to

this appendix are used to locate reporting instructions

contained in the JRS.

2. Organizational Index. Annex A lists the JRS publication

titles.

3. Short Title Index. Annex B lists the JRS reports by an

acronym or short title, in alphabetical order. It also lists

the report identification (ID) symbol, which shows the

publication and chapter of the JRS where the report description

is located.

4. Report Indicator Code Index. Annex C lists report

indicator codes along with the report title and short title.

Not all reports need report indicator codes, only those using

80-character file formats.

5. Guide to Codes

** Reports Under Staffing

***

TU" win be used only in error messages (data record

type "ZE") associated with TYPREP "P" data records.

**** The J-6 Directorate will assign a report indicator for

the report and include it in the implementing

instructions. This report indicator code will be used

for the purpose of report management.

A-l
(INTENTIONALLY BLANK)

A-2
Joint Pub 1-03

PUB

M CJCS TNST

1-03 3150.01

J-6

APPENDIX A

ANNEX A

ORGANIZATIONAL INDEX

1 ZULE

GENERAL INSTRUCTIONS

1-03.3 3150.02

J3 6

1-03.6 3150.03

J-3

1-03.7 3150.04

DNA/NOSM

1-03.8 3150.05

J-3

1-03.9 3150.06

J-3

1-03.10 3150.07

J-6

STATUS OF RESOURCES AND TRAINING SYSTEM

(SORTS)

EVENT/INCIDENT REPORTS

NUCLEAR WEAPONS REPORTS

SITUATION MONITORING

RECONNAISSANCE

COMMUNICATIONS STATUS

1-03.11 3150.08

J-6 COMMUNICATIONS-ELECTRONICS

1-03.12 3150.09

DI SA

1-03.13 3150.10

DI SA

1-03.14 3150.11

DI SA

1-03.15 3150.28

DIA/J-2

1-03.17 3150.13

J-l

MILITARY INSTALLATION STATUS

Joint Resource Assessment Data Base Report

MILITARY INSTALLATION STATUS

Joint Resource Assessment Data Base

Record Format and Data Field Codes

MILITARY INSTALLATION STATUS

Joint Resource Assessment Data Base

Handbook

INTELLIGENCE

JOINT PERSONNEL REPORTING

1-03.18 3150.14

J-4

LOGISTICS

A-A-l
1-03.19 3150.15 CODEWORD, NICKNAME, AND EXERCISE TERM

J-3 3150.29 REPORT (Formerly GENERAL

USE/MISCELLANEOUS)

1-03.21 3150.16

J-3

1-03.31 3150.26

J-7

1-03.32 3150.27

J-7

JOINT OPERATION PLANNING AND EXECUTION

SYSTEM REPORTING STRUCTURE (JOPESREP)

1-03.22 3150.17 TYPE UNIT EQUIPMENT DETAIL REPORT

1-03.23 3150.18 TRANSPORTATION ASSETS REPORT

J—4

1-03.24 3150.19 CHARACTERISTICS OF TRANSPORTATION

J

"

4

RESOURCES REPORT

1-03.25 3150.20 AERIAL PORTS AND AIR OPERATING BASES

J_3 REPORT

1-03.26 3150.21 PORT CHARACTERISTICS REPORT

u —3

1-03.27 3150.22 CIVIL ENGINEERING FILES

u— 4

1-03.28 3150.23 LOGISTIC FACTORS REPORT

J—4

1-03.29 3150.24 TYPE UNIT CHARACTERISTICS REPORT

1-03.30 3150.25 JOINT AFTER-ACTION REPORT SYSTEM

PREPAREDNESS EVALUATION SYSTEM (PES)

COMBAT SUPPORT AGENCY ASSESSMENT

SYSTEM (CSAAS)

A-A-2
Joint Pub 1-03

SHORT

AAR

ANNREP

APORTSREP

ASSETSREP

BULLETIN

CEDREP

ID SYMBOL

1-03.30-1

1-03-7

1-03.25-1

1-03.23-1

1-03.15-5

1-03.11-1

CEF 1-03.27-1

CEPODA 1-03.11-2

CEPODB 1-03.11-3

CHSTRREP 1-03.24-1

COMSPOT 1-03.10-2

COMSTAT 1-03.10-1

CRAFREP 1-03.18-4

CSADR 1-03.32-2

CSPAR 1-03.31-2

DISUM 1-03.15-3

GEOREQ 1-03.19-1

INTELSITSUM 1-03.15-4

JADREP 1-03.12-1

APPENDIX A

ANNEX B

SHORT TITLE INDEX

REPORT TTTT.F

JOINT AFTER-ACTION REPORTING SYSTEM

ANNIVERSARY REPORTS REVIEW

AERIAL PORTS AND AIR OPERATING BASES

REPORT

TRANSPORTATION ASSETS REPORT

NATIONAL MILITARY JOINT INTELLIGENCE

CENTER BULLETIN

COMMUNICATIONS-ELECTRONICS DEPLOYMENT

REPORT

CIVIL ENGINEERING FILES

COMMUNICATIONS-ELECTRONICS

POST-DEPLOYMENT (A)

COMMUNICATIONS-ELECTRONICS

POST-DEPLOYMENT (B)

CHARACTERISTICS OF TRANSPORTATION

RESOURCES REPORT

COMMUNICATIONS SPOT REPORT

COMMUNICATIONS STATUS REPORT

CIVIL RESERVE AIR FLEET SUMMARY REPORT

COMBAT SUPPORT AGENCY DIRECTOR'S REPORT

CINC'S PREPAREDNESS ASSESSMENT REPORT

DAILY INTELLIGENCE SUMMARY

SPECIFIED GEOLOCATION CODE REQUEST

INTELLIGENCE SITUATION SUMMARY

JOINT RESOURCE ASSESSMENT DATA BASE

REPORT

A-B-l
JCASREP* 1-03.17-2

JOPESREP 1-03.21

LOGFACREP 1-03.28-1

MID 1-03.15-1

MOBREP* 1-03.17-1

MUREP 1-03.18-7

NICKA 1-03.19-4

NUDETSUM 1-03.6-2

NUREP 1-03.7-1

OPREP-1 1-03.8-2

OPREP-2 1-03.8-2

OPREP-3 1-03.6-1

OPREP-4 1-03.8-2

OPREP-5 1-03.8-2

POLCAP 1-03.18-2

PORTSREP 1-03.26-1

RECON-1 1-03.9-3

RECON-2 1-03.9-4

RECON-3 1-03.9-5

RECON-4 1-03.9-6

REPOL 1-03.18-1

SEV 1-03.7-4

SIR 1-03.7-5

SITREP 1-03.8-1

SORTS 1-03.3

JOINT CASUALTY REPORT

JOINT OPERATION PLANNING AND EXECUTION

REPORTING SYSTEM

LOGISTIC FACTORS REPORT

MILITARY INTELLIGENCE DIGEST

MILITARY MANPOWER MOBILIZATION AND

ACCESSION STATUS REPORT

MUNITIONS STATUS REPORT

CODEWORD, NICKNAME, AND EXERCISE TERM

REPORT

SUMMARY OF NUCLEAR DETONATIONS

NUCLEAR WEAPON REPORTS

OPERATION(S) PLANNING REPORT

OPERATION(S) START REPORT

OPERATION(S) EVENT/INCIDENT REPORT

OPERATION(S) STOP/RESULTS REPORT

OPERATION(S) SUMMARY REPORT

BULK PETROLEUM CAPABILITIES REPORT

PORT CHARACTERISTICS REPORT

RECONNAISSANCE NICKNAME LOG REPORT

RECONNAISSANCE TRACK DICTIONARY REPORT

RECONNAISSANCE MISSION SCHEDULE REPORT

RECONNAISSANCE MISSION FOLLOWING REPORT

BULK PETROLEUM CONTINGENCY REPORT

STOCKPILE EMERGENCY VERIFICATION

SEMIANNUAL INVENTORY REPORT

COMMANDER'S SITUATION REPORT

STATUS OF RESOURCES AND TRAINING SYSTEM

REPORT

A-B-2
Joint Pub 1-03

SPIREP

TEDREP

TUCHAREP

WSR

WSR-EMERG

WSR-EXER

1-03.15-2 SPOT INTELLIGENCE REPORT

1-03.22-1 TYPE UNIT EQUIPMENT DETAIL REPORT

1-03.29.1 TYPE UNIT CHARACTERISTICS REPORT

1-03.7-2 WEAPONS STATUS REPORT

1-03.7-3 WEAPONS STATUS REPORT-EMERGENCY

1-03.7-3 WEAPONS STATUS REPORT-EXERCISE

Reports under staffi ng

A-B-3
(INTENTIONALLY BLANK)

A-B-4
Joint Pub 1-03

REPORT

INDICATOR ACRONYM

CODE CODE

BP CEF

CH CHSTRREP

CJ CEDREP

CK CEPODA

CL CEPODB

CR CRAFREP

CT COMSTAT

CX COMSPOT

DI DI SUM

DO DODID

FS SORTSREP

GO GEOREQ

IN OPREP-3

JD JADREP

JT ASSETSREP

LI LOGFACREP

MR MUREP

NB BULLETIN

APPENDIX A

ANNEX C

REPORT INDICATOR CODE INDEX

REPORT TTTT.K

CIVIL ENGINEERING FILES

CHARACTERISTICS OF TRANSPORTATION

RESOURCES REPORT

COMMUNICATIONS-ELECTRONICS DEPLOYMENT

REPORT

COMMUNICATIONS-ELECTRONICS

POST-DEPLOYMENT (A)

COMMUNICATIONS-ELECTRONICS

POST-DEPLOYMENT (B)

CIVIL RESERVE AIR FLEET SUMMARY REPORT

COMMUNICATIONS STATUS REPORT

COMMUNICATIONS SPOT REPORT

DAILY INTELLIGENCE SUMMARY

DOD INTELLIGENCE DIGEST

STATUS OF RESOURCES AND TRAINING REPORT

SPECIFIED GEOLOCATION CODE REQUEST

EVENT/INCIDENT REPORT

JOINT RESOURCE ASSESSMENT DATA BASE

REPORT

TRANSPORTATION ASSETS REPORT

LOGISTIC FACTORS REPORT

MUNITIONS STATUS REPORT

NATIONAL MILITARY JOINT INTELLIGENCE

CENTER BULLETIN

A-C-l
NC NUREP

ND NUDETSUM

NN NICKA

OB APORTSREP

OP OPREP-1

OP OPREP-2

OP OPREP-4

OP OPREP-5

PC PORTSREP

PI INTELSITSUM

PL POLCAP

PO REPOL

RE RECON-1

RE RECON-2

RE RECON-3

RE RECON-4

SP SPIREP

SR SITREP

TQ TEDREP

TU*** TUCHAREP

XY ANNREP

NUCLEAR WEAPON REPORTS

SUMMARY OF NUCLEAR DETONATIONS

CODEWORD, NICKNAME, AND EXERCISE TERM

REPORT

AERIAL PORTS AND AIR OPERATING BASES

REPORT

OPERATION(S) PLANNING REPORT

OPERATION(S) START REPORT

OPERATION(S) STOP/RESULTS REPORT

OPERATION(S) SUMMARY REPORT

PORT CHARACTERISTICS REPORT

INTELLIGENCE SITUATION SUMMARY

BULK PETROLEUM CAPABILITIES REPORT

BULK PETROLEUM CONTINGENCY REPORT

RECONNAISSANCE NICKNAME LOG REPORT

RECONNAISSANCE TRACK DICTIONARY REPORT

RECONNAISSANCE MISSION SCHEDULE REPORT

RECONNAISSANCE MISSION FOLLOWING REPORT

SPOT INTELLIGENCE REPORT

COMMANDER'S SITUATION REPORT

TYPE UNIT EQUIPMENT DETAIL REPORT

TYPE UNIT CHARACTERISTICS REPORT

ANNUAL REPORTS REVIEW

RepprtS NQt Requiring Rfinnrf Tndinafnr PnH.c

AAR JOINT AFTER-ACTION REPORTING SYSTEM

CSADR COMBAT SUPPORT AGENCY DIRECTOR'S REPORT

CSPAR CINC'S PREPAREDNESS ASSESSMENT REPORT

JCASREP JOINT CASUALTY REPORT

A-C-2
Joint Pub 1-03

MOBREP MILITARY MANPOWER MOBILIZATION AND

ACCESSION STATUS REPORT

SEV STOCKPILE EMERGENCY VERIFICATION

SIR SEMIANNUAL INVENTORY REPORT

WSR WEAPONS STATUS REPORT

WSR-EMERG WEAPONS STATUS REPORT-EMERGENCY

WSR-EXER WEAPONS STATUS REPORT-EXERCISE

***

****

"TU" will be used only in error messages (data record

type "ZE") associated with TYPREP "F" records.

The J-6 Directorate will assign a report indicator

for the report and include it in the implementing

instructions. This report indicator code will be

used for the purpose of report management.

A-C-3
(INTENTIONALLY BLANK)

A-C-4
Joint Pub 1-03

APPENDIX B

DESCRIPTIONS OF INFORMATION ELEMENTS

1- Need for Consistency. To ensure minimum burden on report

originators, the information content in all JRS reports should

be identified in a consistent manner. This need for

consistency is reinforced by the fact that many JRS reports are

interrelated in report origination, transmission (common

communications processing), or terminal processing (data base

interactions or command center correlations).

2. Types of Reports Involved. The achievement of consistency

in reporting is complicated by the fact that there are three

basically different types of reports in the JRS:

a. Automated Reports. These are formatted reports that

feed into automated data bases either directly from

communications lines or through batch processing updates.

Examp1e: SORTSREP.

b- Narrative Reports. These are free-text prose reports

intended for command center use and not usually associated

with automated data bases. Example: SPIREP.

c

- Semi-Formatted Reports. These reports are formatted to

the extent that certain information always appears under

the same paragraph or subparagraph headings for ease of

entry into an automated data base—at the same time they

are easily understood by command center personnel.

Examp1e: OPREP-4.

3- Composition of Information in Reports. The term

"information element" is used interchangeably with the term

"information field" as a descriptive name for a discrete amount

of information to be reported. The information element or

field may consist of one information item or a combination of

information items that are usually placed in a logical

unvarying sequence within an information element.

a. Information in Automated Reports. Information items

used in automated systems are usually rigidly coded to

compactly transmit and process the data. In this form,

these items are commonly referred to as data codes, usually

arranged in tables of legal values or code tables. Code

tables used in the Joint Pub 1-03 series will appear in the

individual reporting systems. Standard code tables that

are very large need not be repeated in the various chapters

of a publication within the Joint Pub 1-03 series; rather,

reference may be made in the appropriate instructions to

the source of standard data elements (i.e. code tables in

the appropriate chapter of the Joint Pub 1-03 series; DOD

program; or those in applicable WWMCCS standard support

files). B-l
b. Information m Narrative Rpnnrf. Information items

used in narrative information systems are not usually

placed in any particular sequence. Occasionally, some very

common and clearly understood codes and abbreviations may

be used, for which tables are not necessary.

?: Information in Semi-Formatted Reports. Information

items used in these reports designed for both the automated

and command center environment are not usually coded but

are frequently abbreviated. They are normally arranged in

a logical unvarying way as parts of an information

element. Information elements may be separated by virgules

(/) or spaces in non-USMTF reports from other information

elements contained in the same report. NOTE- This is

system specific. Any codes or abbreviations used must be

easily understood by both humans and machines in order for

these reports to be useful in a dual environment.

4

- Definitions in This ApppnrH-r

rommnn

S

^

e

F°rtS"^ contain information element definitions

t

Cyp^s0nnot0edW

:bovem0re reP°

rtin9 SyStemS inCluding a11 three

m;r*TTPcf°

ll0W

i

ng 3re selected definitions common to two or

Sraatted "' N°

TE: The examPles are n

°t USMTF

(1) Military Pate. The military date will be

expressed as day, month, and year. The date 3 January

- 2LW°^ iS6 reported in narrative as 03 Jan 93 and in

a data field as /0/3/J/A/N/9/3/.

(a) Full PATF.-TTMF. The full DATE-TIME will be

expressed as day, time (GMT 0001 to 2400), month,

and year. The full DATE-TIME would be reported in

narrative as 031215Z Jan 93 and in a data field as

/0/3/1/2/1/5/Z/J/A/N/9/3/.

(J) miiimitsLBäTHIffi. The abbreviated

DATE-TIME consists of the first seven characters

of the full DATE-TIME. The abbreviated DATE-TIME

would be reported in narrative as 031215Z and in a

data field as /0/3/1/2/1/5/Z/.

<

c

> Beqin/Depart/T.annch DATF-TIME (Arfnal nr

Planned). The full or abbreviated DATE-TIME of

the initiation of a ground, sea, or air operation.

<

d

> End/Arrival/CloEiirP DATE-TTMF (Actual or

Planned). The full or abbreviated DATE-TIME of

the termination of a ground, sea, or air operation

phase.

B-2
Joint Pub 1-03

<

e

). Incident/Loss DATE-TTMK. The full DATE-TIME

an incident or loss occurs.

(f) RePort-as-of-DATF-TTMK The full DATE-TIME

representing the cutoff point for the data being

reported.

<9> Base DATE-TTME. The abbreviated DATE-TIME

that a generation, launch, mission plan execution,

etc., was directed for military forces.

<

n

> PATE-TIME Over Tarnpf- The abbreviated

DATE-TIME over a target that a strike flight

employs weapons, a reconnaissance (RECCE) flight

makes observations, a signals intelligence

(SIGINT) flight intercepts a signal, etc.

(2) Elapsed Time. The number of hours and minutes

elapsed since a specified base DATE-TIME reference

Expressed using three numeric characters for hours and

two numeric characters for minutes.

Narrative example: 01216 represents 12 hours and

16 minutes elapsed from a base DATE-TIME.

Data field example: /0/1/2/1/6/

<

a)

Flight Time to Target. Elapsed time from the

launch DATE-TIME to the DATE-TIME over target.

<

b

> Total Flying Time.. Elapsed time from a

launch DATE-TIME to the arrival DATE-TIME of the

first landing.

(3) Geographical Coordinate. pfirnn^r The location

on the earth in degrees, minutes, seconds, and

direction of latitude and longitude expressed using two

numeric characters for degrees, two numeric characters

tor minutes, two numeric characters for seconds, and

one alphabetical character (N or S) for North or South;

three numeric characters for degrees, two numeric

characters for minutes, two numeric characters for

seconds, and one alphabetical character (E or W) for

East or West.

Narrative example: 32° 16' 24" N, 112° 52' 16" E

Data Field example:

/3/2/1/6/2/4/N/1/1/2/5/2/1/6/E/

<

4

> Universal Transverse Mernator (UTivn Coorrli nai-pg

Location on the earth using metric grid coordinates.

Expressed using two numeric and one alphabetical

character for grid zone designation, alphabetical

characters for 100-kilometer square, four numeric

characters to locate vertical grid line to nearest 10

meters.

B-3
Narrative example: 48QXK79008600

Data Field example: /4/8/Q/X/K/7/9/0/0/8/6/0/0/

Normally, UTM coordinates are reported in abbreviated

form omitting the first three characters, i e

/X/K/7/9/0/0/8/6/0/0/.

<

5

> World Area Code (WAC). Rectangular areas of the

world's land masses that are covered by charts

(normally 4° of latitude by 8° longitude). These

charts are sequentially numbered up to four positions

Use is made of the chart numbers when referring to

operations that cover large areas. For chart numbers

less than four positions, supply leading zeros to the

fourth position.

Narrative example for WAC Chart #3: 0003.

Data field example: /0/0/0/3/

(6) Installation Number. Six alphanumeric characters

to represent serially numbered installations located

within an area denoted by a WAC.

T

(7) International Civil AviaHon Organisation (TCArO

location Cojfe. A four-character alphabetical location

code of fixed aeronautical stations worldwide.

(ü}

Geopolitical Area/Water Code. Two alphabetical

characters that represent geopolitical land boundaries

and international water bodies.

(a) Nationality. The geopolitical code is used

to represent national origin of foreign units,

vessels, aircraft, or forces.

(b) Objective area.

(c) Collection area.

(9) Region Code. A two-character alphanumeric code

representing province, state, or region of a particular

country.

<1°> geographic Location Code (GF.m.nr) An

alphabetical character code employed by the Joint Staff

for locations of particular military interest. These

locations are registered with the Joint Staff and

maintained in a file that is cross-referenced to

geographic coordinates and place names.

N0TE: Point Of Departure/Arrival is a GEOLOC code

for the base, or identifiable point, from or to which a

mission or force is planned to depart or arrive. The

point of departure or arrival can be requested in ICAO

code (subparagraph 4b(7)), in GEOLOC, or both.

B-4
Joint Pub 1-03

(H> Major Equipment Type- A data element composed of

a maximum of 10 alphanumeric characters that uniquely

identify an item of major equipment (aircraft,

bridging, communications equipment, fire control

equipment, gun, helicopter, launcher, missile, rocket,

trailer, vehicle, or truck) authorized and/or possessed

by US forces. Examples are:

B-52H

MGM-18A

(12) MalQ_r Equipment Weapons Delivery Cap^hi 1 i fry. A

one-character alphabetic code indicating the nuclear,

conventional, or reconnaissance capability of major

equipment being reported. Examples are:

N Deliver Nuclear Ordnance Only.

R Conduct Sensor Reconnaissance Only.

<

13

) Aircraft/Missile Pnrie A one-character

alphabetic code used to identify aircraft and missiles

being reported. Examples are:

A Strike Aircraft.

M Missile.

R Reconnaissance Aircraft.

(14) Ship Type. A data element composed of a maximum

of five alphabetic characters used to identify types of

ships authorized and/or possessed by the US Navy.

Examples are:

DD Destroyer.

CV Aircraft Carrier.

<f5> Unit Identification Code <mr.\. The UIC is a

six-character alphanumeric code that uniquely

identifies each Active, Reserve, and National Guard

unit of the Armed Forces. Also called UIC.

(16) Force or Task Unit- Ng^e A non-UIC

identification by name of a force, task unit, or ship

associated with the particular data being reported.

Uses up to 12 alphanumeric positions.

<

17

) Unit Iievel Code- A three-position (maximum)

alphabetic code characterizing each organization

according to a stratum, echelon, or point at which

control or authority is concentrated.

(18) Unit Descriptor Cnrte. A one-character

alphanumeric code that indicates the component, general

status, and primary mission for which the organization

was established. Examples are:

B-5
A Active—Combat.

B Planned—Combat.

i

1

?) Number of Major Equipment. Ships, nr Ofhar

Material Destroyed. Three-digit number when used in a

data field.

<20) Number Of Mgjpr Equipment:. Ships. nr pj-hor

Material Pamaqed. Three-digit number when used in a

data field.

Ltll. WY

m

*?gr Pf Mf,ior Equipment. EM pf8, nr r^hrr

Material Wiping pr CaphirPd. Three-digit number when

used in a data field.

(22) Lass/Damage Indicator. A two-position alphabetic

code indicating the type of loss or damage sustained: Examples are: öuouaxueu.

CA Combat Damage—minor.

CB Combat Damage—major.

OA Operational Damage—minor.

OB Operational Damage—major.

CL Combat Loss.

OL Operational Loss.

UL Unknown Loss.

UD Unknown Damage.

inrtlr.a?

?gS Si"**'A two

-character alphabetical code

ro«

1Cf^ng

3

he cause of the loss or damage being reported. Examples are: 8

PE Pilot Error.

RK Rocket Attack.

i^iLJ^^i A si9

nific

arit incident occurring along a

mission route; one causing diversion, abort, or

cancellation of a mission; or one causing certain data

,? reported. This is a two-character alphabetical code. Examples are:

AS Air Abort.

CA Canceled Strike.

(25) Loss Classification. A two-character

alphabetical code that classifies the loss beinq

reported. Examples are:

AC Aircraft.

SA Small Arms.

(26> Number pf Casualties. The number of friendly

personnel killed, wounded, injured, or missing or the

number of enemy personnel captured.

B-6
Joint Pub 1-03

This is a five-digit number when used in a data field.

(27) Type of Personnel. The type of personnel

involved in the casualties being reported. This is a

two-character alphabetical code. Examples are:

AE USA Enlisted.

CP Civilian Personnel/Dependents.

(28) Type of Casualty. The type of casualty being

reported. This is a two-character alphabetical code.

Examples are:

AK USA Killed in Action.

MI USMC Prisoner of War.

(29) Installation. The 38-character alphanumeric

field that provides a descriptive name of the place,

installation, activity, facility, etc.

(30> Functional Category ?r>f\* Each installation is

assigned a five-digit numeric category code. Examples

are:

18352 Freight Terminals.

87561 Military Facilities.

<

31

> Basic EncvcloperHg Number, A 10-character

alphanumeric consisting of WAC and Installation

Number. See subparagraphs 4b(5) and 4b(6) above.

(32) Type Target Objective, A two-character

alphabetical code that represents the type target or

objective planned for attack or actually attacked by

any US or friendly air, naval, missile, or ground

force. Examples are:

AA Surface-to-Surface Missile Site.

AF Airfield.

(33) Results. A two-character alphabetical code

describing the successful, unsuccessful, or unknown

status of launches, strikes, or reconnaissance status

of a sortie, weapon, or designated ground zero (DGZ)

Examples are:

DE Destroyed.

WX Weather.

(

34

> Mission/Operation/Action Function. The planned

or actual uses of the major equipment or type operation

or action of the unit being reported. This is a

two-position alphabetical code. Examples are:

B-7
AE Airborne Early Warning.

CA Close Air Support.

(3^> Deployment Codp. A one-character alphabetical

code that indicates the

deployed. Examples are:

f„f_.„^ 15J

dlcates the means by which a force is being

or

D Self-deploying.

A Airlifted.

S Sealifted.

(36) Mission Numb&r. A code assigned to a specific

mission, using up to seven alphanumeric characters.

(37) Track Number. A code assigned to a specific

track flown by an aircraft, using up to seven

alphanumeric characters.

(

38

> Mission Nickname. Nickname assigned per

operations order, using up to 18 alphabetical

characters.

(39) Operations Plan/Order Number. Operations plan

order number authorizing the mission. Use five

alphanumeric characters for data field reporting.

<

40

> Aircraft Serial Number. A tail number

designating a specific aircraft. Use up to eight

numeric characters. y

(41) Data Record/Li nf» p^io^r.» Number A

s

r

alw^rnni

er f

*

iel

*l- JRS header data record or line is always 001 and continues sequentially for everv data

record or line of data message.

Y

iill»y£t%l ¥ ?rrrl

pP

Indicators. A one-character alphabetic field. For real reports, enter R; for

exercise reports, enter an X.

(

f

3) RePPr

t Identification. An 11-alphanumeric

character field consisting of the 6-character Unit

Identification Code (UIC) of the report originator,

rl^llBCI

reP°rt indicat°r

' and a 3-character numeric report number.

<?4> Data Record TVDP TripntifiraHnn A threecharacter alphanumeric field denoting the data record

type within a report. Examples are:

/H/ / / header.

/E/ / / end.

/A/ / / detail.

/A/0/2/ 2d continuation of detail data record

type A.

B-8
Joint Pub 1-03

/K/N/l/ Navy continuation of detail data

record type K. (Data reported are

responsive to requirements unique to

the Navy.)

(45) Security Classification Coflp. A one-character

alphabetical code representing classification of a

message or a data record or line within a message.

(46) Conventional Ordinance A four-character

alphanumeric code used to report all US conventional

ordnance planned for use, expended, jettisoned, or

returned to base.

(47) Circular Error Probable (C.F.P) . An indicator of

the delivery accuracy of a weapon system. It is the

radius of a circle within which one-half of the

missiles or projectiles are expected to fall. It will

be reported in hundreds of feet using three digits.

Example:

1,000-foot CEP would be reported as "010."

(48) Height of Burst (HOTO . The vertical distance

above the earth's surface or target to the point of

burst. HOB will be reported in hundreds of feet using

three digits. Example:

6,000-foot HOB will be reported as "060."

(49) Carqp. Cargo delivered or that carried in

support of force being deployed. A three-character

numeric code when used in a data field.

(

50

> POD Component Cortes. Combatant commands are

represented by a one-character alphanumeric code and

Services and agencies by one-character alphabetical

code.

Command Code

USCINCCENT x

USACOM 2

USCINCSPACE s

NORAD/USELMNORAD 3

USCINCEUR 4

USCINCPAC 5

USCINCSO 6

USSTRATCOM 8

USCINCTRANS G

USCINCSOC 9

Department of Defense K

US Army A

US Navy N

B-9
US Air Force p

US Marine Corps M

US Coast Guard p

Joint Staff J

(51) Combined Command Codes. A one-character

alphabetical code representing headquarters staffed by

US and allied personnel.

Combined Command Code

SACLANT

CINCHAN

SACEUR

A

B

E

United Nations Command, Korea K

NORAD N

Inter-American Peace Force P

United Nations Truce Supervisory Commission T

<

52

> Unit Of Measure. The standard unit used to

report amounts of various material items. Uses up to

four alphabetic characters. Examples are:

BBLS barrels.

STON short tons.

(53) T_rjms action Code. A one-letter code used to

denote what action is to be taken with data reported

(via automated reports) in a detail data record or

line. See Appendix D.

B-10
Joint Pub 1-03

APPENDIX C

DATA RECORD FORMATS

1

- Communications Header and End-of-Transmission Data Record.

A communications header and an end-of-transmission data record

are required as the first and last data records of every report

submitted by a data terminal or data file (card image)

reports. The formats for these data records are defined in

Joint Army, Navy, and Air Force Publication (JANAP 128).

2

- Security Classification. Exercise, and Special Handlina

Datg Record. Following the communications header, a data

record containing the following instructions will be inserted.

a. Security classification (use a space between each

letter of the words CONFIDENTIAL, SECRET, or TOP SECRET;

use UNCLAS without spaces for unclassified messages);

b. Exercise name (if applicable).

c. Any special handling (or "PASS TO").

3

- Report Header Data Rernrd. The originator will include a

report header with each report submitted. This data record

will be prepared as follows:

Element Namp Position

Data Record Sequence Number 1-3

Security Classification 4

Remarks

Enter 001.

Enter the security

classification of the

report, using standard

single-character alphabetic

code.

Data Record Type

Identification

5

6

Leave blank.

Enter "H" for report header

7-8

Report-as-of-Time

9-10

11-12

13-14

15

16-18

19-20

C-l

Leave blank.

Enter the ZULU as-of-time

of the report as follows:

Day of month (01-31)

Hour (00-24)

Minutes (00-59)

Z to denote ZULU time

Month (Jan-Dec)

Last two digits of the year,
Real Report or

Exercise Indicator

Special Use

Format Indicator

Report Identification

21

22-57

58

59-64

65-66

67-69

Report Identification

70-75

76-77

78-80

For real reports, enter R.

For exercise reports, enter

X.

May be used for data fields

that apply to the detail

data records or lines.

Enter 5 for data terminal

reports. Leave BLANK for

data file reports.

For data terminal reports

enter:

report originator UIC,

report indicator,

report number.

Leave BLANK for data file

reports.

For data file reports,

enter:

report originator UIC,

report indicator,

report number.

Leave BLANK for data

terminal reporting.

cönfcSn H

P

f

a F

r

r

?I

dp

-. *

n

Edition to the transmission control and report identification data records, JRS reports

will be composed of various detail data records that Contain

information required for file creation or update? The Tall

altTrtL1*

pos*tions i"14

* 70-80 are common to aU detail data records and are entered as described below: ae"^

Element Nf»"y°

Record Sequence Number

Position Remarks

1-3

Security Classification

The first detail data

record will be number 002

and each succeeding record

will be incremented by

one. The maximum number of

records allowed in any one

report will be governed by

JANAP 128. This total

includes all types of

records or lines.

Enter the DOD standard single

classification character of

the data in each record.

C-2
Joint Pub 1-03

Transaction Code

Record Type Identification 6-8

Unit Identification Code 9-14

(Unit-oriented reports only)

Detail Data

(Unit-oriented reports)

(Other reports)

Report Identification

15-69

9-69

70-75

76-77

78-80

C-3

A one-letter code to indicate

the nature of the action to be

accomplished when the data

record is processed with the

file. Transaction codes and

rules for their use are

explained in Appendix E.

Enter data record type left

justified. Specific data

record types and their

functions will be determined

for each separate report

type. Three characters are

allowed for data record types

to allow for coding of

subtypes within a specific

data record type. Detail data

records will be labeled

alphabetically, beginning with

the letter "A" (omitting "E,"

"H," "I," »o," "R," and "Z"),

except as indicated below.

Remarks data records normally

will be labeled "Z." After

all remaining alphabetic

characters are exhausted,

detail data records will be

numbered sequentially,

beginning with number 1.

Enter the six-character UIC

when used in unit-oriented

reports as part of the record

identification. For instance,

if USACOM submits a report

concerning one of its

subordinate units, the UIC of

the subordinate unit would be

reflected in positions 9-14;

while USACOM's UIC would be

reflected in positions 70-75.

If UIC is not used, positions

9-14 become part of detail

data record.

Detail data may be

formatted or unformatted,

depending on requirements of

each report type.

Originator's UIC,

report indicator,

report number.
5- Pepprt End Data Record. Following the last detail data

record of each report, the originator will insert a report end

data record prepared as follows:

1-3

Element: Nanu?

Record Sequence Number

Security Classification 4

Transaction Code 5

Record Type Identification 6-8

Position Remarks

Exercise/Operation/Study

Name

Declassification

Instructions

9-35

36-56

Multisection Report

Identification

57-69

Report Identification

70-75

76-77

78-80

Enter the next sequential

number after the one on the

detail data record.

Enter the DOD standard single

classification character code

for the report.

Leave blank.

Enter "E" in position 6 to

identify report end data

record.

If appropriate, enter

exercise, operation, or study

and the nickname; otherwise,

leave blank.

If all data to be submitted

at this time are to be

contained in this numbered

report (or last section),

enter the appropriate

declassification or DOD

5200.1-R.

If all data to be submitted

at this time have NOT been

included in this and preceding

numbered sections, enter the

number of the next section;

e.g., "03 of 06 next."

Otherwise, enter "Last

Section" in this space and

declassification instructions

in positions 36-56.

For data file reports, enter:

Originator's UIC,

report indicator,

report number.

Leave blank for data terminal

reports.

C-4
Joint Pub 1-03

APPENDIX D

TRANSACTION CODES

1. Transaction Standards. This appendix establishes JRS

standard codes and rules for transactions pertaining to

automated reports. Deviations from these standards will be

explained within the body of applicable report instructions.

The transaction code will be carried in position 5 of the

Report Detail Record of the JRS Input Record Format standard.

2. Standard Transaction Codes. The following standard

transaction codes apply to JRS data record inputs:

CODE EXPLANATION

A Addition or creation of new record or logical portion

of a record in a file. Addresses an entire input

record.

C Change of data within a record. Addresses only those

fields or data elements to be changed.

D Deletion of an entire record or logical portion of a

record. Addresses the control fields identifying the

record.

L Change of specific field or data element, as identified

in the control field of a specific report.

R Replaces an entire existing record with the information

reported. (This transaction code will be used only

with selected applications.)

BLANK For narrative comments.

3. Transaction Rules

a. "A" Transactions (Add or Created

Rule 1: Initial submission establishing a new data

record requires an "A" transaction. Data record types

that can establish a new record or logical portion of a

record will be designated in the body of each report

instruction.

Rule 2: If a record has been created, another "A"

transaction with the same control identification cannot

be processed without a preceding "D" transaction.

Normal change transactions can be accomplished with "C"

transaction.

D-l
b

- "C" Transactions frhango)

Rule 1: Changes, corrections, or deletions of data

within a record can be accomplished with a

transaction.

ii r* ••

S

le

-

2:

* t l

D

"

(delete> transaction submission is not required before a "C" transaction.

Rule 3: Only those data fields requiring change or

"U10;

need h

t filled in on a data record. Fields

not affected may be left blank.

5?I?*4:-

In 2rder t0 delete (blank out>a

specific dat field, insert a pound (#) sign in the high-order

(leftmost) position of the field to be deleted.

a

?i?rt«:floe-Cha?

9

2

transaction

may not be used to change lelds designated as Record Control Fields.

Rule

f

«D«ETran^-

Con^°l Field(s) may be changed by a

F?*i^a? I

Ct

£°

n

u

hat ldentifies the Record Control Field(s) to be changed, followed by an "A"

transaction with the new Record Control Field(s).

c

- "P" Transactions fncl0F0}

SJürJ'. i "

D

" transaction permits, with a one-data

n

e

n

nry' deletion of an entire record or logical

portion of a record, as designated in the body of each

reporting instruction. y each

chanofVrl^rranSaCtion is not re«3«ired before a cnange transaction.

fn1« «*„„? T transaction is not used to delete data

a -S- 9n «T«ld°

r da^a element of a record' Either a C or an L" transaction should be used for this

purpose. Lino

FJei?:r

T

r>

a

rr^i{r" rhnpqp nr pelptp a Ppprifir

Ü»1!! J- 2 complete record control and a field label,

as defined m the pertinent report, must be given.

Rule 2: Only one element (field) label can be

addressed per data record.

Rule 3: All data in the field will be changed to

I« "?! as

4.

indicatfd

?

n

the data record. For example,

an L data record with proper control and field labels

followed by blanks will delete (or change to blank) the

contents of a field. '

D-2
Joint Pub 1-03

Rule 4: Consult appropriate reporting instructions

for special applications of this type of transaction.

"R" Transaction (Replace a Record)

Rule 1: The report must contain a complete, current

record associated with an existing primary record

control group.

Rule 2: Complete records cannot be added or deleted.

Rule 3: All fields or groups of fields reported will

replace like-identified fields or groups of fields

existing in the file.

Rule 4: All fields or groups of fields omitted from

the report will cause like-identified fields or groups

of fields existing in the file to be set to blanks. If

file maintenance edit routines require a positive value

in a field or group of fields set to blanks, an error

condition will exist.

Rule 5: If data are reported for a secondary control

field or group of fields and associated data fields

that do not exist in the record, the data will be

entered into the record.

Rule 6: If a secondary control field or group of

fields and associated data fields that exist in the

record are not included in the place transaction, the

secondary record will be deleted.

D-3
(INTENTIONALLY BLANK)

D-4
Joint Pub 1-03

APPENDIX E

USERS EVALUATION REPORT

ON JOINT PUB 1-03

1. Users in the field are highly encouraged to submit

comments on this pub by removing this page and sending it to

JDC. Please fill out the following: users' POC, unit

address, and phone (DSN) number.

2. Content

a. Does the pub provide a conceptual framework for the

topic?

b. Is the information provided

be updated?

accurate? What needs to

c. Is the information provided

it be improved?

useful? If not, how can

d. Is this pub consistent with other joint pubs?

e. Can this pub be better organized for the best

understanding of the doctrine and/or JTTP? How?

3. Writing and Appearance

a. Where does the pub need some revision to make the

writing clear and concise? What words would you use?

b. Are the charts and figures clear and understandable?

How would you revise them? __^_

4. Recommended urgent change(s) (if any)

5. Other

6. Please fold and mail comments to the Joint Doctrine

Center (additional pages may be attached if desired or FAX to

DSN 564-3990 or COMM (804) 444-3990.

E-l
(FOLD)

FROM:

JOINT DOCTRINE CENTER

BLDG R-52

1283 CV TOWWAY STE 100

NORFOLK, VA 23511-2491

(FOLD)

E-2
Joint Pub 1-03

USERS EVALUATION REPORT

ON JOINT PUB 1-03

1. Users in the field are highly encouraged to submit

comments on this pub by removing this page and sending it to

JDC. Please fill out the following: users' POC, unit

address, and phone (DSN) number.

2. Content

a. Does the pub provide a conceptual framework for the

topic? '

b. Is the information provided accurate? What needs to

be updated?

c. Is the information provided useful? If not, how can

it be improved?

d. Is this pub consistent with other joint pubs?

e. Can this pub be better organized for the best

understanding of the doctrine and/or JTTP? How?

3. Writing and Appearance

a. Where does the pub need some revision to make the

writing clear and concise? What words would you use?

b. Are the charts and figures clear and understandable?

How would you revise them?

4. Recommended urgent change(s) (if any)

Other.

6. Please fold and mail comments to the Joint Doctrine

Center (additional pages may be attached if desired) or FAX

to DSN 564-3990 or COMM (804) 444-3990.

E-3
(FOLD)

FROM:

JOINT DOCTRINE CENTER

BLDG R-52

1283 CV TOWWAY STE 100

NORFOLK, VA 23511-2491

(FOLD)

E-4