top - download
⟦0361f5024⟧ Wang Wps File
Length: 41726 (0xa2fe)
Types: Wang Wps File
Notes: CPS/SYS/001 issue II
Names: »0174A «
Derivation
└─⟦cf42e5d4d⟧ Bits:30005818 8" Wang WCS floppy, CR 0016A
└─ ⟦this⟧ »0174A «
WangText
…02…CPS/210/SYS/0001
…02…800919…02……02…
CAMPS SYSTEM REQUIREMENTS
…02……02…CAMPS
3.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
The following section will exhaustively specify the
functional requirements to CAMPS.
Section 3.2.1 and 3.2.2 defines all functional capabilities
related to processing of outgoing and incoming messages
respectively. The sequence in which the functional
capabilities are presented are as they appear during
message processing.
Section 3.2.3 specifies all functional capabilities
related to terminals and the associated equipment.
The section has been structured in such a way, that
it presents the functional capabilities seen from a
user's point of view.
Section 3.2.4 defines all required capabilities for
supervisory control commands, message service, message
distribution control, system status and alarm, engineering
functions and software maintenance.
The Section is not presented from an operational point
of view, but more in terms of functional capabilities.
Section 3.2.5 specifies the events for which log entries
shall be made and the information associated with the
log entries.
Section 3.2.6 defines the required statistical reports
related to channel traffic and transactions at terminals.
Section 3.2.7 specifies storage and retrieval requirements
of incoming and outgoing messages.
Section 3.2.8 defines the requirements related to initialization
error detection and recovery.
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
S̲e̲c̲t̲i̲o̲n̲ ̲3̲.̲2̲.̲1
…02……02……02…3.2.1 Outgoing Messages.....................
…02……02……02……02…3.2.1.1. Message types and their flow through the CAMPS
System.........
…02……02……02……02…3.2.1.2 Operational Messages..............
…02……02……02……02……02…3.2.1.2.1 Message Preparation...........
…02……02……02……02……02……02…3.2.1.2.1.1 Initial Message
Preparation...............
…02……02……02……02……02……02…3.2.1.2.1.2 Message Editing...........
…02……02……02……02……02……02…3.2.1.2.1.3 Message Merge.............
…02……02……02……02……02……02…3.2.1.2.1.4 Message Coordination......
…02……02……02……02……02…3.2.1.2.2 Comments......................
…02……02……02……02……02……02…3.2.1.2.2.1 Initial Comment
Preparation...............
…02……02……02……02……02……02…3.2.1.2.2.2 Comment Editing...........
…02……02……02……02……02……02…3.2.1.2.2.3 Comment Presentation......
…02……02……02……02……02…3.2.1.2.3 Message Release...............
…02……02……02……02……02…3.2.1.2.4 Local Distribution............
…02……02……02……02…3.2.1.3 Service Messages..................
…02……02……02……02……02…3.2.1.3.1 Preparation...................
…02……02……02……02……02……02…3.2.1.3.1.1 Initial Preparation.......
…02……02……02……02……02……02…3.2.1.3.1.2 Editing...................
…02……02……02……02…3.2.1.4 Entry of complete messages........
…02……02……02……02……02…3.2.1.4.1 Entry from OCR................
…02……02……02……02……02…3.2.1.4.2 Entry from PTR................
…02……02……02……02…3.2.1.5 ACP127 Conversion.................
…02……02……02……02……02…3.2.1.5.1 Conversion of Operational
Messages with Plain text......
…02……02……02……02……02…3.2.1.5.2 Conversion of Service
Messages......................
…02……02……02……02……02…3.2.1.5.3 Conversion of Complete
Messages......................
…02……02……02……02…3.2.1.6 Transmission......................
…02……02……02……02……02…3.2.1.6.1 Channel selection and
identification................
…02……02……02……02……02…3.2.1.6.2 Procedures related to
premature termination of a
transmission..................
…02……02……02……02……02…3.2.1.6.3 Procedures related to the ZEN
prosigns......................
…02……02……02……02……02…3.2.1.6.4 Procedures related to
FLASH receipt.................
3.2.1 O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
a) This section describes the processing of outgoing
messages by CAMPS from the initial preparation
through all the stages until transmission .
b) The section is organized as follows:
c) Section 3.2.1.1 identifies the different types
of messages which the CAMPS system shall be able
to process and gives for each type an outline of
their functional flow through the system.
d) Section 3.2.1.2 describes how operational messages
are prepared by users, procedures associated with
their release and outlines the local distribution
required for outgoing operational messages.
e) Section 3.2.1.3 deals with service messages and
how they are prepared by the supervisor.
f) Section 3.2.1.4 describes how complete messages
are entered into the system and the involved system
processing.
g) Section 3.2.1.5 describes for each message type
the ACP127 conversion. All outgoing messages shall
be converted into the relevant ACP127 format before
transmission.
h) The processing of converted messages related to
transmission is described in section 3.2.1.6.
3.2.1.1 M̲e̲s̲s̲a̲g̲e̲ ̲t̲y̲p̲e̲s̲ ̲a̲n̲d̲ ̲t̲h̲e̲i̲r̲ ̲f̲l̲o̲w̲ ̲t̲h̲r̲o̲u̲g̲h̲ ̲t̲h̲e̲ ̲C̲A̲M̲P̲S̲ ̲s̲y̲s̲t̲e̲m̲
Messages are constituted of two parts, the message
header and the message text.
a) M̲e̲s̲s̲a̲g̲e̲ ̲H̲e̲a̲d̲e̲r̲. The message header contains the
information which is necessary for the automatic
processing of the message from its origination
to its destination(s). During creation of the message
header under supervision of CAMPS each entry shall
be validated with respect to syntax. Validation
of the semantic shall be performed to a certain
extent too.
b) M̲e̲s̲s̲a̲g̲e̲ ̲T̲e̲x̲t̲.̲ The message text contains no information
necessary for the automatic processing of the message
by CAMPS. Message text is treated as though it
is in free format by CAMPS. The only validation
being performed (no validation for data messages
and messages with encrypted text) is that text
lines do not exceed 69 characters.
c) The following three message types shall be recognized
by the CAMPS system:
- operational messages
- service messages
- data messages
1) O̲p̲e̲r̲a̲t̲i̲o̲n̲a̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲. This type is the one
which may be originated or received by common
users of the CAMPS. Two types shall exist:
- operational messages with plain text
- operational messages with encrypted text
2) S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲. Service messages are generated/handled
either automatically by CAMPS or by the supervisor.
The message text contains control information
of the message exchange between the CAMPS sites.
Two types shall exist:
- Service messages
- Abbreviated service messages
3) D̲a̲t̲a̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲. The message text differs from
the other message types in the following way:
the message text comprises a datastream which
may or may not include End of Line Function.
d) The formal presentation of a message depends on
the stage of processing. Messages distributed
to or received from external circuits are in ACP
127 format. Messages inside a CAMPS system are
in internal formats.
e) Messages for transmission may at the originating
CAMPS be entered either as complete messages, i.e.
in ACP 127 format without format line 1, in OCR
input format, or by means of interactive procedures.
f) F̲l̲o̲w̲ ̲o̲f̲ ̲o̲u̲t̲g̲o̲i̲n̲g̲ ̲m̲e̲s̲s̲a̲g̲e̲s̲
The processing of outgoing messages and how messages
are being entered depends on the message type.
This dependency is shown in fig. 3.2.1.1-1 and
fig. 3.2.1.1-2.
Fig. 3.2.1.1-1
Fig.3.2.1.1-2
3.2.1.2 O̲p̲e̲r̲a̲t̲i̲o̲n̲a̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
a) The system shall support the functions for outgoing
messages listed below
1) Message preparation
2) Message release
3) Local distribution of outgoing messages
4) ACP 127 conversion
5) Transmission of outgoing messages
b) Further, the following support functions described
elsewhere within this document shall be supported
by the CAMPS
1) Storage and retrieval functions
2 Logging and reporting functions
3) Supervisory functions
4) Terminal handling functions
Fig. 3.2.1.2-1 illustrates the processing of operational
messages.
c) This section contains a description of how operational
messages with plain text shall be prepared by users
and further describes the processing of the message
performed by the system from preparation through
release and local distribution until the stage
where the ACP127 conversion takes place.
Fig. 3.2.1.2-1
3.2.1.2.1 M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
a) Message preparation shall be supported by the following
procedures (ref. CPS/230/ICD/0001)
1) Initial message preparation
2) Message editing
3) Message merging
4) Message coordination
3.2.1.2.1.1 I̲n̲i̲t̲i̲a̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
Command: PMA
Associated formats: A, C2, M
Initial message preparation shall be performed by means
of interactive procedures.
Initial message preparation consists of the following
steps:
- Preparation of message header
- Preparation of message text
- Correction of header and/or text
- Clean copy of message
- Sending the message to coordination or to release
terminal for release or defer it for later editing.
3.2.1.2.1.1.1 P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲H̲e̲a̲d̲e̲r̲
a) Two options shall exist for preparation of the
message header:
1) Interactive header creation
2) Selection of a predefined header.
b) I̲n̲t̲e̲r̲a̲c̲t̲i̲v̲e̲ ̲H̲e̲a̲d̲e̲r̲ ̲C̲r̲e̲a̲t̲i̲o̲n̲
Interactive header creation involves separate input
by the drafter of each parameter and subsequent
parameter validation performed by the system.
The parameters are listed below:
1) S̲e̲c̲u̲r̲i̲t̲y̲ ̲C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Parameter is mandatory.
2) S̲p̲e̲c̲i̲a̲l̲ ̲C̲a̲t̲e̲g̲o̲r̲y̲ ̲W̲a̲r̲n̲i̲n̲g̲s
Parameter is optional
3) P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲L̲e̲v̲e̲l̲,̲ ̲A̲c̲t̲i̲o̲n̲ ̲A̲d̲d̲r̲e̲s̲s̲e̲e̲(̲s̲)̲
4) P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲l̲e̲v̲e̲l̲,̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲A̲d̲d̲r̲e̲s̲s̲e̲e̲(̲s̲
Parameter is mandatory.
The precedence level for information addressees
may not be higher than the one specified for
action addressees. This shall be checked by
the system.
When precedence specified for action addressee(s)
is of type FLASH or IMMEDIATE and the precedence
for info addressee(s) is lower the procedure
in section 3.2.1.5.1a shall apply.
5) A̲c̲t̲i̲o̲n̲ ̲A̲d̲d̲r̲e̲s̲s̲e̲e̲(̲s̲)̲
Parameter(s) are optional.
The parameters entered may be of the following
types
- PLA, i.e. Plain Language Address
- Reference Number (each PLA has o̲n̲e̲ associated
ref. number)
- AIG, Action Indicator Group (numerical
id.)
- Address Group (Each AIG has o̲n̲e̲ associated
Address Group, alpha - id.)
- "X" PLA.
The system shall carry out a validation of
the parameters entered. If a PLA is not in
the system address tables, this fact shall
be displayed to the user, who may (after proper
validation) then insert the PLA again preceeded
by an "X". The message will then be queued
for message service where the PLA is considered
for manual insertion of routing information.
6) I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲A̲d̲d̲r̲e̲s̲s̲e̲e̲(̲s̲)̲
Parameter(s) are optional.
The parameters entered may be of the following
types:
- PLA
- Reference Number
- AIG
- Address Group
- "X" PLA
"Either one ACTION or one INFO PLA is mandatory".
7) E̲x̲e̲m̲p̲t̲e̲d̲ ̲A̲d̲d̲r̲e̲s̲s̲e̲e̲(̲s̲)̲
Parameter(s) are optional.
The parameters entered may be of the following
types:
PLA or
Reference number
The exempted addressees shall be deleted from
the specified AIG(s) by the system
8) S̲u̲b̲j̲e̲c̲t̲ ̲I̲n̲d̲i̲c̲a̲t̲o̲r̲ ̲C̲o̲d̲e̲s̲ (SIC)
Parameter(s) are (at least one) mandatory
9) C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲,̲ ̲S̲t̲a̲f̲f̲ ̲C̲e̲l̲l̲(̲s̲)̲
Parameters are optional.
SCD's (staff cell designators) to which the
message shall be sent for coordination.
10) O̲p̲e̲r̲a̲t̲i̲n̲g̲ ̲S̲i̲g̲n̲a̲l̲s̲
Parameters are optional max. 10 for automatic
insertion, otherwise rejection to message servicing
11) I̲n̲t̲e̲r̲n̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲I̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲s̲
Parameters are optional.
c) S̲e̲l̲e̲c̲t̲i̲o̲n̲ ̲o̲f̲ ̲P̲r̲e̲d̲e̲f̲i̲n̲e̲d̲ ̲H̲e̲a̲d̲e̲r̲
When a predefined header is requested by the drafter
of the message, he is first prompted for coordinating
staff cells, thereafter the predefined header chosen
will be displayed , i.e. all information as described
in a1) above.
3.2.1.2.1.1.2 P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲T̲e̲x̲t̲
a) Two options shall exist for preparation of the
message text:
1) Entering of message text in free format
2) Entering of message text interactively according
to stored format information.
b) F̲r̲e̲e̲ ̲F̲o̲r̲m̲a̲t̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲T̲e̲x̲t̲
The text is entered by the drafter in free format,
and no validation shall be supported by the system.
c) P̲r̲e̲f̲o̲r̲m̲a̲t̲t̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲T̲e̲x̲t̲
The text is entered by the drafter under supervision
of the system, prompting the drafter for parameters
in accordance with the predefined text format (M1-
Mn) selected by the drafter and performing syntax
validation of entered values as far as type (numerical
or alphabetic) and numbers are concerned.
3.2.1.2.1.1.3 C̲o̲r̲r̲e̲c̲t̲i̲o̲n̲ ̲o̲f̲ ̲H̲e̲a̲d̲e̲r̲ ̲a̲n̲d̲/̲o̲r̲ ̲T̲e̲x̲t̲
Correction procedures for correction of header
and text shall be supported by the system as an
optional part of initial message preparation (ref.
CPS/230/ICD/0001).
3.2.1.2.1.1.4 C̲l̲e̲a̲n̲ ̲C̲o̲p̲y̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲
After correction procedures has been invoked during
the initial message preparation the drafter will
be prompted if he wants a clean copy. This will
be presented to him in format C2.
3.2.1.2.1.1.5 L̲o̲c̲a̲l̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
The system shall prompt the drafter for insertion
of staff cell designator to indicate local information
distribution which shall take place after release.
Selection of Local Distribution is optional.
3.2.1.2.1.1.6 C̲o̲o̲r̲d̲i̲n̲a̲t̲e̲/̲R̲e̲l̲e̲a̲s̲e̲/̲D̲e̲f̲e̲r̲
The system will after correction has ended, prompt
the drafter for an answer to the following questions.
- Coordination?
- Release?
If coordination is specified the message will be
sent for coordination and the initial message preparation
procedure terminated.
If coordination is not specified the drafter is
prompted with the question "Release?" If Release
is specified the message will be sent to the releasing
officer requesting release and the initial message
preparation procedure terminated.
If Release is not specified the message will be
deferred and be available for subsequent editing.
3.2.1.2.1.2 M̲e̲s̲s̲a̲g̲e̲ ̲E̲d̲i̲t̲i̲n̲g̲
a) Command: EM
Associated formats: C1, C2
b) Message Editing shall be possible only from the
terminal position at which the initial message
preparation took place.
c) Message Editing shall apply to all messages under
preparation i.e. until message release.
d) Message editing shall be performed under supervision
of the system by means of interactive procedures.
e) The message which the operator wishes to edit
shall be identified to the system by means of the
Terminal designator and serial number.
f) The system shall respond to a request for message
editing as follows:
1) Message available. Message editing procedure
shall be commenced.
2) Message available, but initial preparation
of message terminated by the suspend function
(ref.3.2.3.1 b) or preempted. The user shall
be informed and the initial message preparation
commenced from the point where it was interrupted.
3) Message not available, i.e. non existent, released,
awaiting release or not available from this
terminal position. The user shall be informed
accordingly.
g) The message editing shall consist of the following
steps (details given in CPS/ICD/0001):
1) Specification or change of local info-distribution
2) Specification of staff cells for coordination.
3) Clean copy of message.
4) Correction of header and/or text
5) Sending the message to coordination or to release
or defer it for later editing.
h) The last two steps are as specified for initial
message preparation.
i) S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲s̲t̲a̲f̲f̲ ̲c̲e̲l̲l̲s̲ ̲f̲o̲r̲ ̲c̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲.̲
The system shall display the staff cells specified
for coordination during initial message preparation.
The operator shall then be allowed to exempt those
staff cells for which coordination shall not take
place.
j) C̲l̲e̲a̲n̲ ̲c̲o̲p̲y̲ ̲o̲f̲ ̲m̲e̲s̲s̲a̲g̲e̲ ̲(̲r̲e̲f̲e̲r̲ ̲t̲o̲ ̲C̲P̲S̲/̲I̲C̲D̲/̲0̲0̲0̲1̲)
If a clean copy of the message is requested by
the operator, the system shall initiate a security
interrogation if the classification of the message
so requires. Once a clean copy has been presented
to the operator no security interrogation shall
take place on subsequent requests for clean copies.
3.2.1.2.1.3 M̲e̲s̲s̲a̲g̲e̲ ̲M̲e̲r̲g̲e̲
a) Command: MM
Associated format: O
b) Message merge shall apply only to messages prepared
at the terminal position from which the message
merge is requested of the same message.
c) Message merge shall be performed under supervision
of the system by means of interactive procedures.
d) Message merge shall have the capability to merge
two messages as follows:
1) The first message specified will be retrieved
and used in its entirety.
2) For the second message specified (if any) the
text part shall be extracted and concatenated
the text part of the first message.
e) Messages prepared by means of message merge shall
be available for message editing (format C1).
3.2.1.2.1.4 M̲e̲s̲s̲a̲g̲e̲ ̲C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲
a) Asssociated formats: A, C1, B
b) Message coordination may be requested during initial
message preparation or message editing.
c) When message coordination is requested a copy of
the message shall be sent to the specified staff
cells within the CAMPS site. At the destination
the message shall be presented in format B. When
the second or later version of the same message,
due to subsequent requests for coordination, is
presented to a staff cell this shall be indicated
in the display by the word "REPEAT"!
d) Requests for message coordination (messages with
classification higher than NATO UNCLASSIFIED) with
staff cells associated with terminals at which
no users are signed in or at which users/terminals
do not have the required clearance at the time
of the coordination request shall be ignored by
the system. The message drafter shall be informed
by the system that the addressee was not reached.
e) Remarks to messages received at a terminal position
for coordination may be sent to the message drafter
via CAMPS by means of the comment procedures.
3.2.1.2.2 C̲o̲m̲m̲e̲n̲t̲s̲
a) CAMPS shall support the preparation and distribution
of comments within a CAMPS site.
b) Comments may be used for internal exchange of information
or for sending answers to coordination requests.
c) The following procedures shall be supported by
the system with respect to comments.
1) Initial comment preparation
2) Comment editing
3) Comment presentation
3.2.1.2.2.1 I̲n̲i̲t̲i̲a̲l̲ ̲C̲o̲m̲m̲e̲n̲t̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
a) Command: CM1
Associated format: G1
b) Initial comment preparation shall be performed
by means of interactive procedures.
c) initial comment preparation shall involve specification
of the following parameters which except for the
text are validated with respect to syntax by the
system.
1) S̲e̲c̲u̲r̲i̲t̲y̲ ̲C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Parameter is mandatory
2) S̲p̲e̲c̲i̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
Parameter is optional
3) P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲l̲e̲v̲e̲l̲
Parameter is mandatory.
4) A̲c̲t̲i̲o̲n̲ ̲S̲C̲D̲(̲s̲)̲
Parameter is optional
Staff cell designator(s) for "ACTION"
5) I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲S̲C̲D̲(̲s̲)̲
Parameter is optional
Staff cell designator(s) for information.
The system shall check that at least one SCD
either Action or Information is entered.
6) T̲e̲x̲t̲: text in free format.
d) After specification of the parameter the system
shall support:
1) C̲l̲e̲a̲n̲ ̲c̲o̲p̲i̲e̲s̲.̲ Only if requested. The clean
copy is constituted by a simple listing of
the entered parameters.
2) C̲o̲r̲r̲e̲c̲t̲i̲o̲n̲s̲. Correction procedures as described
under initial message preparation shall be
supported upon request.
3) S̲e̲n̲d̲/̲D̲e̲f̲e̲r̲.̲ If requested by the operator the
comment shall be sent to the designated staff
cells, otherwise the comment shall be deferred
and available for later comment editing. Comments
which have been sent shall not be retained
by the system.
3.2.1.2.2.2 C̲o̲m̲m̲e̲n̲t̲ ̲E̲d̲i̲t̲i̲n̲g̲
a) Command: EC
Associated format: G3
Comment editing shall be possible only from the
terminal position at which initial comment preparation
took place.
b) Comment Editing shall apply to comments under preparation,
i.e. not sent to the designated staff cells.
c) Comment Editing shall be performed under supervision
of the system by means of interactive procedures.
d) The comment to which the operator wishes to apply
the comment editing shall be identified to the
system by means of the terminal designator and
serial number.
e) The system shall respond to a request for comment
editing as follows:
1) Comment available. Comment editing shall be
commenced.
2) Comment available, but initial comment preparation
was terminated by the suspend function or preemption.
The user shall be informed and initial comment
preparation shall be commenced from the point
where it was interrupted.
3) Comment not available, i.e. non existent, not
available from this terminal position. The
user shall be informed accordingly.
f) The comment editing shall support:
1) Clean copy of comment
2) Correction procedures
3) Send/defer as for initial comment preparation,
except that upon a request for a clean copy
of the comment the system shall initiate a
security interrogation if the classification
of the comment so requires. Once a clean copy
has been presented to the operator no security
interrogation shall take place on subsequent
request for clean copies of the same message.
3.2.1.2.2.3 C̲o̲m̲m̲e̲n̲t̲ ̲P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
a) Associated format: G2
b) When sending of a comment is requested, it shall
be presented at the destination in format G2.
c) Request for presentation of comments of classification
higher than NATO UNCLASSIFIED sent to staff cells
associated with terminals at which no users are
signed on or the users/terminals do not have the
required clearance at the time of the send request
shall be ignored by the system.
3.2.1.2.3 M̲e̲s̲s̲a̲g̲e̲ ̲R̲e̲l̲e̲a̲s̲e̲
a) When requested by the drafter (via format A, C1)
the message shall be sent to the release position
to which the drafter's terminal position is associated.
b) The release officer at the release position shall
decide whether the message shall be released or
not. This shall be supported by the system by means
of the message release procedure.
c) The message release procedure consist of the following
steps:
1) Presentation of message for which release is
requested
2) Prompting the release officer for a release
decision
3) Entering of release officer's comment
d) P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲m̲e̲s̲s̲a̲g̲e̲
The presentation of the message shall be in accordance
with format D.
e) R̲e̲l̲e̲a̲s̲e̲ ̲d̲e̲c̲i̲s̲i̲o̲n̲
Authorization for release is given by the release
officer when he enters his personal password. The
released message shall be assigned a serial release
number together with the time of release. The message
shall then be accepted by the system for local
distribution and ACP127 Conversion.
Rejection of release may be of two types DEF or
NO, and is further detailed in the release officer's
comment.
f) R̲e̲l̲e̲a̲s̲e̲ ̲o̲f̲f̲i̲c̲e̲r̲'̲s̲ ̲c̲o̲m̲m̲e̲n̲t̲
The release officer has the option to comment on
his decision on release. If the decision for release
was DEF. This indicates that the release officer
wants the message to be resubmitted at a later
time without any changes. The release officer may
specify the time for resubmissison here, as it
is the responsibility of the message drafter to
resubmit the message.
The message drafter shall be informed of the release
decision and the associated comment (if any) by
means of the notification of release procedure
(format F).
3.2.1.2.4 L̲o̲c̲a̲l̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲.̲
a) Local distribution of outgoing messages shall apply
to messages which have been released.
Local distribution shall be based on staff cell
Designators entered during preparation.
c) Local copies of outgoing messages shall be presented
in format E2 (refer to CPS/ICD/0001) at the receiving
terminal positions.
3.2.1.3 S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲.̲
a) The system shall assist the supervisor in preparation
of service messages.
b) Procedures which may be accessed by the supervisor
are detailed in ref. CPS/230/ICD/0002.
3.2.1.3.1…02…P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
a) Service Message Preparation shall be supported
by the following procedures.
1) Initial Preparation.
2) Editing.
b) The supervisor shall be able to request an ACP
127 conversion and the following transmission for
service messages prepared.
3.2.1.3.1.1 I̲n̲i̲t̲i̲a̲l̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
a) Initial preparation shall be performed under supervision
of the system by means of interactive procedures.
b) Initial preparation shall involve specification
of the following parameters, which, except for
the text parameter, shall be validated with respect
to syntax by the system.
1) S̲e̲c̲u̲r̲i̲t̲y̲ ̲C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The parameter is mandatory.
2) S̲p̲e̲c̲i̲a̲l̲ ̲C̲a̲t̲e̲g̲o̲r̲y̲ ̲W̲a̲r̲n̲i̲n̲g̲
The parameter is optional.
3) P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲
The parameter is mandatory.
4) O̲p̲e̲r̲a̲t̲i̲n̲g̲ ̲S̲i̲g̲n̲a̲l̲s̲
5) A̲d̲d̲r̲e̲s̲s̲e̲e̲s̲
Parameter is mandatory. PLA's (or associated
Reference number) and/or AIG's (or associated
Address Groups) shall be specified.
6) T̲e̲x̲t̲
c) The supervisor shall specify:
1) type of conversion, i.e. abbreviated service
message or not.
2) if conversion shall be applied. If not the
service message shall be available for editing.
3.2.1.3.1.2 E̲d̲i̲t̲i̲n̲g̲
a) Editing shall be possible only from the terminal
position where initial preparation took place.
b) Editing shall apply to all service messages under
preparation, i.e. when no conversion has yet been
requested.
c) Editing shall be performed by means of interactive
procedures.
d) The service message to which the supervisor wishes
to apply editing shall be identified to the system
by means of the terminal designator and serial
number.
e) The system shall respond to a request for editing
as follows:
1) Message available. Editing shall be commenced.
2) Message available, but initial preparation
was terminated by the suspend function or preemption.
The supervisor shall be notified, an initial
preparation shall be recommenced from the point
where it was interrupted.
3) Message not available, i.e. non existent, awaiting
conversion or converted.
f) The editing shall support
1) correction procedures .
2) conversion/defer (as for initial preparation).
3.2.1.4…02…E̲n̲t̲r̲y̲ ̲o̲f̲ ̲C̲o̲m̲p̲l̲e̲t̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲.̲
a) Entry of complete messages shall be accepted by
the system.
Complete messages may be entered as follows:
1) from Paper Tape Reader (PTR)
2) from Optical Character Reader (OCR)
b) The system shall support supervisor control of
complete message entry.
3.2.1.4.1 E̲n̲t̲r̲y̲ ̲f̲r̲o̲m̲ ̲O̲C̲R̲
a) Messages shall be entered in a format which is
described below (b). All information necessary
for the conversion to ACP 127 format shall be available
except for the following parameters
1) Channel designator and associated serial number
2) Release serial number and time of release
(For details on conversion refer to section 3.2.1.5).
b) F̲o̲r̲m̲a̲t̲ ̲o̲f̲ ̲D̲a̲t̲a̲ ̲E̲n̲t̲e̲r̲e̲d̲ ̲f̲r̲o̲m̲ ̲O̲C̲R̲
TBD
3.2.1.4.2 E̲n̲t̲r̲y̲ ̲f̲r̲o̲m̲ ̲P̲T̲R̲
a) Messages shall be entered in ACP 127 format with
the following exception.
1) Format line 1 shall be inserted by CAMPS of
transmission.
2) Release serial number and time of release shall
be present, but will be replaced at conversion
(For details on conversion refer to section
3.2.1.5).
3.2.1.5…02…A̲C̲P̲ ̲1̲2̲7̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲.̲
The conversion of outgoing messages to ACP 127 format
shall be type dependent as shown in figure 3.2.1.1-1.
The different ACP 127 formats are explained in detail
in CPS/230/ICD/0003.
This ICD also contains details about outgoing message
conversion for operational messages with plain text
and service messages.
Figure 3.2.1.5-1 provides in a short form the details
of conversion for all types. Operational messages
with encrypted text and data messages are entered as
complete messages and shall except for certain checks
and replacements not be subject to conversion processing.
Refer to section 3.2.1.5.3 for details.
In case of operational messages with plain text and
service messages certain parameters for conversion
are not directly available. Refer to section 3.2.1.5.1
and 3.2.1.5.2 for details.
3.2.1.5.1…02…C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲o̲f̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲a̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲w̲i̲t̲h̲ ̲P̲l̲a̲i̲n̲ ̲T̲e̲x̲t̲.̲
The functional dependencies applicable at conversion
shall correspond to figure 3.2.1.5-2.
a) P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲ ̲s̲p̲e̲c̲i̲f̲i̲e̲d̲ ̲a̲t̲ ̲p̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲.̲
1) Parameters specified during preparation shall
be inserted directly as specified in figure
3.2.1.5-1 and CPS/230/ICD/0003.
2) Address parameters shall furthermore result
in selection of routing indicator(s), refer
to section 3.2.1.5.1b.
3) When precedence specified for action addressee(s)
is of type FLASH or IMMEDIATE and the precedence
for info addressee(s) is lower a separate messages
shall be made for each addressee.
4) The originator designation shall depend on
the release position (refer to fig. 3.2.1.5-4).
5) Contents of format line 12C shall be in accordance
with exercise SIC's inserted during preparation.
3.2.1.5-1
3.2.1.5-1
3.2.1.5-2
3.2.1.5-3
3.2.1.5-4
b) S̲e̲l̲e̲c̲t̲i̲o̲n̲ ̲o̲f̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲I̲n̲d̲i̲c̲a̲t̲o̲r̲s̲
1) Routing indicators shall be selected on basis
of PLA's as described in section 3.2.1.6.1
2) The applicable set of PLA's shall be derived
as follows (refer to fig. 3.2.1.5-3)
- to each Address Group is found the associated
AIG
- to each Reference Number is found the associated
PLA.
- PLA's are extracted from AIG's
- EXEMPT specified PLA's shall not be included.
- ZEN specified PLA's shall not be considered
(the supervisor may specify the sequence
"ZEN(Sp)" shall be inserted in format line
7 & 8 of ACP 127 format on transmission
as associated with specific addressee(s).
Messages containing s̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲s̲p̲e̲c̲i̲f̲i̲e̲d̲
"ZEN PLA's" shall be printed out at a position
specified by the supervisor).
3) PLA's preceeded by an "X" at preparation have
no routing indicators associated by the system:
After final conversion the message shall be
queued for routing indicator assignment.
c) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲l̲e̲d̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲.̲
ACP127 conversion shall further depend on supervisory
control via system tables.
1) Decision on conversion alternatives for all
messages converted at a CAMPS site is defined
in 3.2.4.1.1.3(b).
2) Decision on operating signals (format line
4) as depending on message precedence FLASH:
ZGC when no receipt wanted (refer to section
3.2.1.6).
d) H̲a̲n̲d̲l̲i̲n̲g̲ ̲o̲f̲ ̲L̲o̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲.̲
G̲e̲n̲e̲r̲a̲l̲. Messages prepared on the system for transmission
shall be divided into "pages" of 20 lines if their
length exceed 20 counting from the "format line
5" of the ACP 127 format.
Those messages which exceed five "pages" in length
shall be divided into transmission sections.
1) R̲e̲l̲a̲t̲e̲d̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲.̲ The first page shall consist
of Format lines 1,2,3 and 4 and the succeeding
20 lines.
2) All other pages of the message shall consist
of not more than 20 lines.
3) From the second page onwards each page shall
be identified by the page number, the routing
indicator of the station of origin and the
station serial number in that order. When
the message text is transmitted in plain language
the security classification, the abbreviation
UNCLAS, or the word CLEAR shall also be included
as part of the page identification of second
and succeeding pages. Page identification
shall appear on a separate line, and shall
not be included in the line count as in b.
above.
4) Machine functions used between pages shall
be 2 CR and 4 LF.
5) The number of pages of message text in any
transmission shall not exceed five, a page
consisting of part heading and part text shall
not count as a textual page.
6) Messages which exceed five pages of message
text shall be divided into transmission sections
as follows:
The classification format line 12a and the
SIC format line 12b shall be repeated for each
section. Also, each section shall include
all format lines mandatory for that format.
At a convenient point on the last permissible
page of a transmission section, the originator
shall separate the text (if not, the text is
separated at the end of line).
Each section shall be numbered, and the section
number shall be inserted in plain language
after the Exercise indicator (if used) on
line 12c. For example, when a message is divided
into two sections, the first section shall
be identified as SECTION 1 of 2, and the second
section as FINAL SECTION OF 2.
7) Each section shall bear a separate station
serial number, but the same date-time group
and filing time shall be used on all sections.
e) S̲t̲o̲r̲a̲g̲e̲. Before issuing a message for the transmission
procedures (refer to section 3.2.1.6) the message
segments shall be stored. The segments shall be
stored separately.
3.2.1.5.2…02…C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲o̲f̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲.̲
The functional dependencies applicable to conversion
shall correspond to figure 3.2.1.5-2.
Detailed conversion information is given in fig. 3.2.1.5-1.
a) P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲ ̲s̲p̲e̲c̲i̲f̲i̲e̲d̲ ̲a̲t̲ ̲p̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲.̲ Parameters
specified during preparation shall be inserted
directly as specified in fig. 3.2.1.5-1.
b) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲y̲ ̲C̲o̲n̲t̲r̲o̲l̲.̲ Section 3.2.1.5.1 c) shall
apply.
c) H̲a̲n̲d̲l̲i̲n̲g̲ ̲o̲f̲ ̲L̲o̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲.̲ The provisions of section
3.2.1.5.1 d) shall apply to standard service messages
only.
d) S̲t̲o̲r̲a̲g̲e̲.̲ The provisions of section 3.2.1.5.1 e)
shall apply.
3.2.1.5.3…02…C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲o̲f̲ ̲C̲o̲m̲p̲l̲e̲t̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲.̲
Messages entered under the provision of section 3.2.1.4
as complete, shall be processed as follows:
a) Release serial number and time of release (format
line 3 and 5) shall be replaced with the time of
entry for "conversion" and the next serial No.
in a dedicated series.
b) Routing indicators of format line 2 shall be validated.
In case of a non successful validation the message
shall be queued for routing indicator assignment.
c) Channel designator and serial number shall be replaced
as part of the transmission procedures (refer to
section 3.2.1.6 below).
d) Encrypted messages shall after above conversion
be routed to message servicing for validation of
group count in format line 10 (refer to section
3.2.4.2).
3.2.1.6 T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲
Following ACP 127 conversion as described in section
3.2.1.5 messages shall be subject to transmission procedures.
3.2.1.6.1 C̲h̲a̲n̲n̲e̲l̲ ̲S̲e̲l̲e̲c̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) Where more than one output route is available,
the routing of outgoing messages shall be performed
according to routing tables associating specific
routing indicators with each output route. Separate
transmissions will be made on each output route
concerned.
b) For each transmission of an outgoing message, only
the routing indicators pertinent to that transmission
shall be present in "format line 2" on the ACP
127 format.
c) The maximum amount of routing indicators per channel
shall be as specified by the supervisor to max.
200.
d) Where necessary separate transmissions shall be
made to include all RI's.
e) A table shall exist to indicate for each PLA selected
as in section 3.2.1.5.1.c. The RI to be selected
in order of priority. Max. 3 Routing Indicators
shall exist at a given time.
f) Each RI shall be associated to one external channel.
If the channel is not authorised to carry messages
of the assigned security classification and/or
special warning category the next RI in order of
priority shall be selected. If no channel is found
with proper classification/special category assignment
a security report shall be generated. No transmission
shall take place for the message for that channel,
but it shall be queued to a position specified
by the supervisor.
g) If a channel is found which is authorised but not
available, the next routing indicator in order
of priority shall be selected and the associated
channel analysed for authorization. If no channel
is found although authorization is given, a warning
report shall be generated. No transmission shall
take place for the message for that channel it
shall be queued for message service (RI assignment
including insertion of Instruction in FL4 of ACP
127 format).
h) As a result of Routing Indicator and channel selection
separate messages may be transmitted via different
channels corresponding to one prepared message
(Max. 4). Each of these messages shall contain
all PLA's in format lines 7,8, and 9 of format
ACP 127, however, PLA's reached via other channels
(other routing indicators) shall for each separate
transmission be indicated by "ZEN/PLA" in format
lines 7 and 8 of ACP 127.
i) As decided by the supervisor (section 3.2.4.1.1.3)
finally converted messages may be sent directly
by CAMPS or routed to a Paper Tape Punch.
Output of PTP shall be max. 4 messages according
to the series of RI's associated to the channels
selected.
j) To each outgoing channel shall be assigned a unique
channel designator, security classification and/or
special handling category. To each message shall
be assigned, as the last step before transmission,
a channel serial No. equal to the serial No. of
the last transmitted message plus one.
k) The supervisor shall have facilities for resetting
the serial number.
l) The channel designation and serial number are together
called the transmission identification.
m) Transmission identification shall be inserted in
format line 1 before transmission.
n) The supervisor shall be able to specify the channel
designator for each channel and he shall be able
to reset the sequence of channel serial number
to 001/0001. He shall be able to select whether
3 digits or 4 digits be used and whether the sequence
is reset at 24,00 hours to 001/0001 or reset only
by wrap around/i.e. 001 after 999 and 0001 after
9999). The supervisor shall also be able to update
security classification and special handling categories.
3.2.1.6.2 P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲ ̲R̲e̲l̲a̲t̲e̲d̲ ̲t̲o̲ ̲P̲r̲e̲m̲a̲t̲u̲r̲e̲ ̲T̲e̲r̲m̲i̲n̲a̲t̲i̲o̲n̲ ̲o̲f̲
̲a̲ ̲T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲.̲
a) When during transmission preemption procedures
are invoked in accordance with precedence rules
the interrupted messages shall be terminated automatically
by the sequence
b) 2 carriage returns, line feed, letter shift, 2XC,
space, ZXC, 2 carriage returns, 8 line feeds, NNNN,
12 letter shifts
c) The CAMPS shall automatically retransmit the preempted
message.
3.2.1.6.3 P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲ ̲R̲e̲l̲a̲t̲e̲d̲ ̲t̲o̲ ̲t̲h̲e̲ ̲Z̲E̲N̲ ̲P̲r̲o̲s̲i̲g̲n̲s̲.̲
Refer to sections 3.2.1.5.1b and 3.2.1.6.1
3.2.1.6.4 P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲ ̲r̲e̲l̲a̲t̲e̲d̲ ̲t̲o̲ ̲F̲L̲A̲S̲H̲ ̲R̲e̲c̲e̲i̲p̲t̲.̲
a) For each transmission of an outgoing message with
precedence FLASH the system shall receive a receipt
message from the recipient stations in the format
of a service message as specified below. The receipt
message may be of either precedence FLASH or IMMEDIATE.
b) If the originating CAMPS does not require a receipt
message, it shall be possible for the supervisor
to direct the insertion of the operating signal
"ZGC" in the appropriate position of format line
4 through flagging for each release series whether
ZGC to be inserted or not.
c) If a receipt message is requested and it is not
received within ten minutes from the end of an
outgoing transmission of the precedence FLASH message,
a warning report shall be generated.
d) It shall be possible for the supervisor to vary
the time period involved from 2 minutes to 20 minutes
in increments of 2 minutes.
e) Format for FLASH message receipt is an abbreviated
service message of IMMEDIATE precedence with text
line containing the following sequence:
R (Space) Z (space) Station & Channel designation
of FLASH message transaction station (figure shift)
Serial Number.
