top - download
⟦8591c985c⟧ Wang Wps File
Length: 50740 (0xc634)
Types: Wang Wps File
Notes: CPS/SYS/001 - issue II
Names: »0173A «
Derivation
└─⟦cf42e5d4d⟧ Bits:30005818 8" Wang WCS floppy, CR 0016A
└─ ⟦this⟧ »0173A «
WangText
…0e……07……0d……0d……86…1
…02…
…02…
…02…
CPS/210/SYS/0001
800919
CAMPS SYSTEM
REQUIREMENTS
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 SCOPE ........................................
1-1
2 APPLICABLE DOCUMENTS .........................
2-3a
2.1 APPLICABLE DOCUMENTS .....................
2
2.2 REFERENCE DOCUMENTS ......................
3
2.3 TERMS ....................................
3
3 REQUIREMENTS .................................
4-348
3.1 SYSTEM DEFINITION ........................
7
3.1.1 General Description ....................
8
3.1.1.1 Connectivity of a CAMPS Site .......
8
3.1.1.2 Logical Addressing Scheme ..........
14
3.1.1.3 Functional Capabilities ............
20
3.1.2 Message Flow .........................
30
3.2 FUNCTIONAL REQUIREMENTS ..................
39
3.2.1 Outgoing Messages ....................
42
3.2.1.1 Message Types and their Flow
through the CAMPS System .........
42
3.2.1.2 Operational Messages ............
47
3.2.1.3 Service Message ..................
61
3.2.1.4 Entry of Complete Messages .......
64
3.2.1.5 ACP 127 Conversion ...............
65
3.2.1.6 Transmission .....................
77
3.2.2 Incoming Messages ....................
82
3.2.2.1 Message Reception Procedures .....
82
3.2.2.2 ACP 127 Analysis .................
85
3.2.2.3 Message Distribution .............
92
3.2.2.4 Procedures Related to Receipt
of Flash Messages ................
97
3.2.3 Terminal Functions and
Characteristics ......................
98
3.2.3.1 Equipment and Functions
allocatable to a Terminal
Position .........................
100
3.2.3.2 Terminal Access Control ..........
104
3.2.3.3 Functional Capabilities of
Terminal Procedures ..............
107
3.2.3.4 Precedence and Queueing ..........
115
3.2.3.5 Terminal Modes ...................
119
3.2.3.6 Status Information Available
from Terminal Positions ..........
125
3.2.3.7 Presentation of Information at
Terminal Positions ...............
127
3.2.4 Supervisory Function .................
133
3.2.4.1 Supervisor Functions .............
138
3.2.4.2 Message Service ..................
156
3.2.4.3 Message Distribution Control .....
161
3.2.4.4 Reports ..........................
165
3.2.4.5 Engineering Functions ............
169
3.2.5 Logging ..............................
172
3.2.5.1 Categories of Transactions to
be Logged ........................
174
3.2.5.2 Logging Events ...................
174
3.2.5.3 Storage of Log Records ...........
175
3.2.5.4 Print of Log Records .............
175
3.2.5.5 Tracing (Computer Analysis)
of Log Information ...............
175
3.2.5.6 Definition of Specific Log
Records ..........................
176
3.2.6 Statistical Requirements .............
185
3.2.6.1 Statistical Data on Messages .....
186
3.2.6.2 Storage Occupancy ................
188
3.2.6.3 Channel availability and
Occupancy ........................
188
3.2.6.4 Message Distribution .............
188
3.2.6.5 Use of Message Formats ...........
189
3.2.7 Storage and Retrieval ................
191
3.2.7.1 Message Storage and Retrieval ....
193
3.2.7.2 Storage and Retrieval of
Non-Message traffic ..............
196
3.2.8 Start-up and Error Handling ..........
197
3.2.8.1 On-line and Off-line CAMPS Site
Software Packages ................
198
3.2.8.2 Initialization ...................
200
3.2.8.3 Error Handling ...................
200
3.2.8.4 Recovery Situations ..............
202
3.2.8.5 Degraded availability
Configuration ....................
204
3.3 EXTERNAL INTERFACES ......................
206
3.4 CHARACTERISTICS ..........................
207
3.4.1 Performance Characteristics ..........
209
3.4.1.1 Message Traffic Characteristics ..
209
3.4.1.2 Message Traffic Throughput .......
211
3.4.1.3 Message Storage Characteristics ..
216
3.4.1.4 Storage of Non-Message Traffic ...
217
3.4.1.5 Storage of Tables etc. ...........
218
3.4.1.6 Timing Requirements ..............
220
3.4.1.7 Connectivity .....................
223
3.4.1.8 Expandability ....................
227
3.4.1.9 Interface Capabilities ...........
227
3.4.1.10 Specific Equipment
Characteristics ..................
230
3.4.2 Physical Characteristics .............
235
3.4.2.1 Size, Weight, Power Consumption
and Heat Dissipation .............
236
3.4.2.2 Power Input ......................
238
3.4.3 Environmental Conditions .............
239
3.4.3.1 Temperatur and Humidity ..........
240
3.4.3.2 Dust, Fumes ......................
241
3.4.4 Availability and Maintainability .....
242
3.4.4.1 General ..........................
243
3.4.4.2 Reliability Characteristics ......
243
3.4.4.3 Availability Calculation .........
244
3.4.4.4 Availability and Reliability
Performance requirements .........
245
3.4.4.5 Equipment Redundancy .............
248
3.4.4.6 Specific Equipment availability
Requirements .....................
249
3.4.4.7 Terms ............................
249
…02……02……02…3.4.5 Security.............................. 252
…02……02……02……02…3.4.5.1 Communication and Electrical
Requirements......................
253
…02……02……02……02…3.4.5.2 Control of Record Output.......... 259
…02……02……02……02…3.4.5.3 Accountability of Transaction..... 260
…02……02……02……02…3.4.5.4 Supervisory Security Monitoring... 260
…02……02……02……02…3.4.5.5 Terminal Access Control........... 260
…02……02……02……02…3.4.5.6 Security Classification and
Special Handling..................
260
…02……02……02……02…3.4.5.7 System Design Requirements........ 261
3.5 DESIGN AND CONSTRUCTION REQUIREMENTS .....
263
3.5.1 General ..............................
265
3.5.1.1 Equipment Produced by CR .........
265
3.5.1.2 Equipment Produced by
Subcontractors ...................
265
3.5.1.3 Products From Other Suppliers ....
266
3.5.2 Special Requirements for the CAMPS
System ...............................
266
3.5.2.1 Environmental Testing ............
266
3.5.2.2 Utility Outlet Sockets ...........
267
3.5.2.3 Materials ........................
267
3.5.2.4 Interchangeability ...............
267
3.5.2.5 Bench Handling ...................
268
3.5.2.6 Cover Plates .....................
268
3.5.2.7 Cabling and Fittings .............
268
3.5.2.8 Flux and Soldering ...............
269
3.5.2.9 Ventilation and Cooling ..........
269
3.5.2.10 Electromagnetic Compatibility ....
270
3.5.2.11 Test and Repair ..................
270
3.5.2.12 Consumable Parts .................
271
3.5.2.13 Safety ...........................
271
3.5.2.14 Nameplates and Product Marking ...
274
3.5.2.15 Controls .........................
274
3.5.2.16 Acoustic Noise ...................
274
3.5.11 Software Engineering Requirements ...
276
3.5.11.1 System Principles ...............
276
3.5.11.2 System Software .................
278
3.5.11.3 Application Software ............
279
3.5.11.4 Software Maintenance and
Modification ....................
282
3.5.11.5 Support Software ................
283
3.5.11.6 Software Integrity ..............
286
…02……02…3.6 DOCUMENTATION REQUIREMENTS................ 287
…02……02……02…3.6.1 General............................... 289
…02……02……02…3.6.2 Format and Publication Criteria....... 289
…02……02……02……02…3.6.2.1 Paper............................. 289
…02……02……02……02…3.6.2.2 Binding........................... 290
…02……02……02……02…3.6.2.3 Numbering......................... 290
…02……02……02……02…3.6.2.4 Preface........................... 291
…02……02……02……02…3.6.2.5 Printing and Type................. 292
…02……02……02……02…3.6.2.6 Language.......................... 293
…02……02……02……02…3.6.2.7 Security Classification........... 293
…02……02……02……02…3.6.2.8 Photographs, Illustrations
and Drawings......................
293
…02……02……02……02…3.6.2.9 Amendments........................ 294
…02……02……02……02…3.6.2.10 Levels of Maintenance............. 294
…02……02……02……02…3.6.2.11 Use of References................. 294
…02……02……02…3.6.3 Approval and Delivery................. 294
…02……02……02…3.6.4 Equipment Handbooks................... 296
…02……02……02……02…3.6.4.1 CR produced Equipment............. 296
…02……02……02……02…3.6.4.2 OEM Equipment..................... 299
…02……02……02…3.6.5 Maintenance Handbook ................. 299
3.6.5.1 Preventive Maintenance ...........
300
3.6.5.2 Corrective Maintenance ...........
301
3.6.5.3 Associated Documentation .........
301
…02……02……02…3.6.6 As-Built Documents.................... 301
3.6.6.1 Civil Works Requirements .........
302
3.6.6.2 As-To-Be-Built and As-Built
Documentation ....................
302
…02……02……02…3.6.7 Inventory............................. 303
…02……02……02……02…3.6.7.1 General........................... 304
…02……02……02……02…3.6.7.2 Property Inventory................ 304
…02……02……02……02…3.6.7.3 Final Inventory (optional)........ 305
…02……02……02…3.6.8 Factory and Acceptance Test
Documentation.........................
305
…02……02……02……02…3.6.8.1 General........................... 306
…02……02……02……02…3.6.8.2 Prototype Test Documents.......... 306
…02……02……02……02…3.6.8.3 Factory Acceptance Test Documents.
…02……02……02……02…3.6.8.4 Site Provisional Acceptance
Document (SPA)....................
307
…02……02……02……02…3.6.8.5 Test Procedures................... 307
…02……02……02……02…3.6.8.6 Test Results Forms................ 307
…02……02……02……02…3.6.8.7 Approval and Delivery............. 308
…02……02……02…3.6.9 Software Documentation................ 308
…02……02……02……02…3.6.9.1 General........................... 308
…02……02……02……02…3.6.9.2 Documentation Structure........... 308
…02……02……02……02…3.6.9.3 System Design Specification ...... 309
…02……02……02……02…3.6.9.4 Subsystem Specification .......... 310
3.6.9.5 Package Specification ............
311
3.6.9.6 Data Base Design Document ........
311
…02……02……02…3.6.10 Field Modification Documents......... 311
…02……02……02……02…3.6.10.1 General.......................... 311
…02……02……02……02…3.6.10.2 Delivery......................... 312
3.7 LOGISTIC REQUIREMENTS ....................
313
3.7.1 Transportation and Installation ......
316
3.7.1.1 Transportation ...................
316
3.7.1.2 Installation .....................
318
3.7.2 Maintenance and Support ..............
322
3.7.2.1 Maintenance Plan .................
322
3.7.2.2 Reporting System .................
322
3.7.2.3 Software Maintenance Support .....
322
3.7.2.4 Tools and Test Equipment .........
323
3.7.2.5 Calibration ......................
325
3.7.2.6 Field Support ....................
325
3.7.3 Spares and Codification ..............
326
3.7.3.1 Supply of Parts ..................
326
3.7.3.2 NATO Codification ................
330
…02……02……02…3.7.4 Training ............................. 331
…02……02……02……02…3.7.4.1 General Requirements ............. 331
…02……02……02……02…3.7.4.2 Training Program Plan ............ 334
…02……02……02……02…3.7.4.3 Technical Training ............... 336
…02……02……02……02…3.7.4.4 Operator Training ................ 340
…02……02……02……02…3.7.4.5 On-The-Job Training .............. 341
…02……02……02……02…3.7.4.6 Software Maintenance Course
(Optional) .......................
342
…02……02……02……02…3.7.4.7 Training of Customers Resident
Site Technicians .................
343
…02……02……02……02…3.7.4.8 Depot Level Training (Optional)... 344
…02……02……02…Annex A to section 3.7.4. Training .......... 345
3.8 PRECEDENCE ...............................
348
4. QUALITY ASSURANCE PROVISION .................
349-362
4.1 TEST AND VERIFICATION METHODS ............
350
4.2 VERIFICATIONS ............................
350
4.2.1 Hardware Verification ................
351
4.2.1.1 Prototype Verification ...........
351
4.2.1.2 Preproduction Verification .......
352
4.2.1.3 Production Verification ..........
352
4.2.1.4 DSMT (Prototype) System
Verification .....................
352
4.2.1.5 Factory Acceptance Verification ..
352
4.2.1.6 COMSEC In Plant Verification .....
352
4.2.1.7 Availability Verification ........
353
4.2.2 Software Verification ................
359a
4.2.2.1 Software Development
Verification .....................
359a
4.2.2.2 In Plant Software Verification ...
360
4.2.2.3 Software Functional
Verification .....................
361
4.2.2.4 Software Operational
Verification .....................
361
4.2.3 System Verification ..................
362
4.2.3.1 COMSEC On-Site Verification ......
362
4.2.3.2 Site Provisional Acceptance
(SPA) ............................
362
1̲ ̲ ̲S̲C̲O̲P̲E̲
This specification establishes the functional, performance,
availability, external physical design, connectivity,
testing and verification requirements for CAMPS (Computer
Aided Message Processing Systems).
The document consists of the following four chapters.
Chapter 1, SCOPE, which introduces the document.
Chapter 2, APPLICABLE DOCUMENTS, which contains the
list of documents constituting the requirements baseline.
Chapter 3, REQUIREMENTS, which defines the functional,
performance and design requirements for CAMPS.
Chapter 4, VERIFICATION, which denotes the responsibility
for verification, the verification methods, the extent
of verification at each delivery milestone and the
associated verification documentation.
2̲ ̲ ̲A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲ ̲A̲N̲D̲ ̲T̲E̲R̲M̲S̲
2.1 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
The following documents are applicable to the CAMPS
System Requirements Specification.
a)* NGTS-40, Issue 2, January 75,
Environmental Test Methods.
b)* NGTS-45, Issue 2, January 75,
General Manufacturing Requirements.
c)* NGTS-50, Issue 2, January 75,
Design, Construction and Installation
criteria for electrical and electronic
material.
d) Contract Document.
Contract No. CE 80-9009-INF
e) User Procedures and Associated
Formats CPS/230/ICD/0001
f) Supervisor Commands and Procedures
CPS/230/ICD/0002
g) ACP127 NATO Supp. 3 Procedures
CPS/230/ICD/0003
h) NICSTARE
CPS/230/ICD/0004
i) ACE CCIS, SCARS II
CPS/230/ICD/0005
j) TRC, Point-to-point Connection
CPS/230/ICD/0006
k) AMSG 719B
l) STANAG 6001
m) AMSG 720A
n) AMSG 293D
NATO CRYPTOGRAPHIC INSTRUCTIONS, January 1977
o) MIL-HDBK-217C
MILITARY STANDARDIZATION HANDBOOK, 9 APRIL 1979
* Only sections of these standards are applicable,
as
specified in section 3.5.
2.2 T̲E̲R̲M̲S̲
a) User - means within this document an operator
who has been allocated one or more of the
following functional capabilities:
preparation, reception and/or release.
b) Supervisor - means t̲h̲e̲ supervisor and the supervisor
assistants who are allocated to the message
distribution control function and/or the
message service function.
c) Initialization - brings the system from cold start
into operational use.
d) Recovery - reestablishes continuity in memory and
file contents.
e) Restart - reestablishes the dynamic behaviour of
the
system based upon recovered data.
f) Start up - includes all aspects of initialization,
recovery and restart.
3̲ ̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
The following chapter will exhaustively specify the
requirements to the CAMPS system as derived from the
CAMPS IFB. The specification will emphasize on the
external requirements to the CAMPS system, i.e. all
the functional capabilities and the connectivities,
the performance and the availability requirements.
The System Requirements Specification will not, however,
give a specification of the internal design-related
requirements. These requirements will be precisely
defined during the system design phases.
The specification of the CAMPS requirements have been
organized in:
a) A System Definition section 3.1 that provides an
overview of the system in terms of connectivity,
addressing principles, functional capabilities
and message identification within CAMPS.
b) Functional requirements (section 3.2.) specifies
all functions applicable to CAMPS.
c) External interfaces requirements (section 3.3)
specifies all the functional requirements related
to the CAMPS-TARE, -TRC, -SCARS II and -ACE CCIS
interfaces.
d) System characteristics are contained in section
3.4. The characteristic areas are:
1) Performance characteristics specified in section
3.4.1.
2) Physical and environmental characteristics
specified in section 3.4.2 and 3.4.3.
3) Availability and maintainability characteristics
addressed in section 3.4.4.
4) All security characteristics described in section
3.4.5.
e) Design and construction requirements are specified
in section 3.5.
f) Documentation requirements are defined in section
3.6.
g) Logistic requirements are specified in section
3.7.
h) Verification requirements are addressed in section
4.
T̲A̲B̲L̲E̲ ̲o̲f̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
S̲e̲c̲t̲i̲o̲n̲ ̲3̲.̲1̲
3.1 SYSTEM DEFINITION ..........................
3.1.1 General Description ....................
3.1.1.1 Connectivity of a CAMPS site .........
3.1.1.2 Logical Addressing Scheme ............
3.1.1.3 Functional Capabilities ............
3.1.1.3.1 Handling of Messages .............
3.1.1.3.2 System Supervision ...............
3.1.1.3.3 Storage and Retrieval ............
3.1.1.3.4 Logging ..........................
3.1.1.3.5 Statistics .......................
3.1.1.3.6 Security .........................
3.1.2 Message Flow ...........................
3.1.2.1 Message Preparation ..............
3.1.2.2 Incoming Message .................
3.1 S̲Y̲S̲T̲E̲M̲ ̲D̲E̲F̲I̲N̲I̲T̲I̲O̲N̲
a) This section is intended to give an overview of
a CAMPS site.
b) The CAMPS site is first looked at from a s̲t̲a̲t̲i̲c̲
̲p̲o̲i̲n̲t̲ ̲o̲f̲ ̲v̲i̲e̲w̲ describing:
1) the connectivity of the system and the protocols
used for transfer of messages.
2) the logical addressing scheme used throughout
CAMPS to route outgoing message and distribute
incoming messages.
3) the functional capabilities given to the users
of message preparations terminals and supervisory
terminals, and the functional capabilities
of the system itself.
c) The CAMPS site is thereafter looked at from a d̲y̲n̲a̲m̲i̲c̲
̲p̲o̲i̲n̲t̲ ̲o̲f̲ ̲v̲i̲e̲w̲ where we follow a message through
the system from preparation to transmittal and
from reception to final distribution of the message.
This part will emphasize on how the message is
identified throughout its life in the system, and
how and when the message and the associated transactions
are logged and stored in files.
d) As an overview section 3.1 and its subsections
do not present any specific detailed systems requirements,
neither quantitative nor functional. The section
does, however describe the baseline for the design
with respect to equipment at terminal positions,
logical addressing and identification, logging
and storage of messages.
3.1.1 G̲e̲n̲e̲r̲a̲l̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
3.1.1.1 C̲o̲n̲n̲e̲c̲t̲i̲v̲i̲t̲y̲ ̲o̲f̲ ̲a̲ ̲C̲A̲M̲P̲S̲ ̲s̲i̲t̲e̲
As a Message Handling system each CAMPS site shall
interconnect with a number of external ADP systems
through communication lines and with a number of Terminal
Positions (ref. section 3.1.1.1 h and 3.4.1.7). The
following defines the CAMPS connectivity:
a) T̲A̲R̲E̲ ̲c̲o̲n̲n̲e̲c̲t̲i̲o̲n̲
CAMPS shall connect to one or more TARE systems
through
e̲i̲t̲h̲e̲r̲ a direct link to a colocated TARE
o̲r̲ a Crypto/modem communication link to
a Remote TARE.
The i̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲p̲r̲o̲t̲o̲c̲o̲l̲s̲ used are
1) V24/V28 electrical interface
2) EDC Link Access Protocol
3) ACP127 Transmission Control Protocol.
CAMPS shall have a w̲i̲r̲e̲d̲ ̲c̲a̲p̲a̲c̲i̲t̲y̲ to handle up
to 6 TARE communication lines. It shall have Line
Termination Units, L̲T̲U̲-̲c̲a̲p̲a̲c̲i̲t̲y̲,̲ ̲to handle 2 or
4 lines depending on the individual sites (equipped
capacity).
Line speeds are for
- colocated TARES: 2400 bits/sec.
- Remote TARES: 600 bits/sec.
b) L̲o̲w̲ ̲S̲p̲e̲e̲d̲ ̲C̲o̲m̲m̲u̲n̲i̲c̲a̲t̲i̲o̲n̲ ̲L̲i̲n̲e̲s̲
CAMPS shall provide a number of low speed interfaces
to be used for connection of SHAPE supplied TRC's
Point-to point connections, teleprinters, paper
tape readers, paper tape punchers and low speed
cryptoes.
The interface is a standard interface common for
all lines and transparent to the type of device
attached characterised by the following:
1) Electrical interface - low level signal interface
(6-0-6 V and less than 1 mA) terminated at
the intermediate distribution frame. The interface
will contain common ground and data signal
lines.
2) Transmission speed, up to 600 Baud.
3) Transmission type - asynchronous ITA2 or ITA5
alphabet.
4) If an attached crypto device looses synchronization
and consequently transmits random garble to
CAMPS, then CAMPS shall be able to recognize
this and notify the supervisor in accordance
with ACP127. Transient errors in the text
part of data messages and the encrypted part
of an encrypted message will, however, not
be detected.
5) Crypto start-up and synchronization is manually.
6) Transmission format and operational procedures
are described in CPS/210/ICD/0004, CPS/210/ICD/0005
and CPS/210/ICD/0006.
c) C̲C̲I̲S̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲o̲n̲
CAMPS shall interconnect to one CCIS system colocated
with the CAMPS main computer system.
The interface p̲r̲o̲t̲o̲c̲o̲l̲s̲ are still under discussion
but the current baseline is
1) V24/V28 Electrical Interface
2) Modified X25 level 2 LAP for Link Access Protocol
3) Not yet specified.
Line speed is 9.6 kbits/sec.
The CCIS connection shall be equipped to fulfil
the availability and reliability requirements as
stated in this SRS.
d) S̲C̲A̲R̲S̲ ̲I̲I̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲o̲n̲
CAMPS shall interconnect to one SCARS II system
colocated with the CAMPS main computer system.
The i̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲p̲r̲o̲t̲o̲c̲o̲l̲s̲ shall be identical to the
CCIS protocols.
Line speed is 9.6 kbits/sec.
The SCARS II connection shall be equipped to fulfil
the availability and reliability requirements as
stated in this SRS.
e) O̲p̲t̲i̲c̲a̲l̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲ ̲R̲e̲a̲d̲e̲r̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲o̲n̲
CAMPS shall interconnect with an optical character
Reader of the type ECRM 5300 auto Reader for input
of message with release authorization.
The interface p̲r̲o̲t̲o̲c̲o̲l̲s̲ are:
- V24/V28 electrical
interface
- Refer sec. 3.4.1.9 link control
- Refer sect. 3.2.1.4.1 Document format
and operational
procedures.
Line speed is 2400 bits/sec.
f) P̲a̲p̲e̲r̲t̲a̲p̲e̲ ̲R̲e̲a̲d̲e̲r̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲o̲n̲
CAMPS shall interconnect to one papertape reader
for input of complete ACP127 message with release
authorization.
The interface p̲r̲o̲t̲o̲c̲o̲l̲s̲ are
- V24/V28 electrical interface
- ACP127 document format.
Line speed is 1200 bits/sec
g) P̲a̲p̲e̲r̲t̲a̲p̲e̲ ̲P̲u̲n̲c̲h̲e̲r̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲o̲n̲
CAMPS shall interconnect to one papertape puncher
for output of messages.
The interface p̲r̲o̲t̲o̲c̲o̲l̲s̲ are:
- V24/V28 electrical interface
- Async.
h) T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲s̲
CAMPS shall interconnect to four types of Terminal
Positions. The detailed interface requirements
are given in 3.4.1.7.
T̲y̲p̲e̲ ̲1̲ is equipped with
- one VDU and attached keyboard (KB)
- one medium speed printer (Receive Only Printer
- ROP).
T̲y̲p̲e̲ ̲2̲ is equipped with
- One VDU and attached keyboard.
T̲y̲p̲e̲ ̲3̲ is equipped with
- One low speed teleprinter with keyboard.
T̲y̲p̲e̲ ̲4̲ is supervisor position equipped with
- one VDU and keyboard
- one or two medium speed receive only printers.
The V̲D̲U̲'̲s̲ are characterized by
1) Wired capacities for typical large site: 32
2) Wired capacities for typical small site 20
3) LTU capacity (equipped) for typical
large site: 26
4) LTU capacity (equipped) for typical
small site: 17
5) Transmission speed: 1200 and 2400 bits/sec.
Only 1200 bps will be used during testing
The m̲e̲d̲i̲u̲m̲ ̲s̲p̲e̲e̲d̲ ̲p̲r̲i̲n̲t̲e̲r̲s̲ are characterized by
1) Wired capacity for typical large site: 16
2) - - - - small site: 12
3) LTU capacity - - large site: 8
4) - - - - small site: 7
5) Transmission speed: 600/1200 bits/sec.
The physical connectivity of a CAMPS is depicted
in figure 3.1-1.
figure 3.1.1
3.1.1.2 L̲o̲g̲i̲c̲a̲l̲ ̲A̲d̲d̲r̲e̲s̲s̲i̲n̲g̲ ̲S̲c̲h̲e̲m̲e̲
Routing of messages from one CAMPS site through the
available networks to another CAMPS site and distribution
of messages and comments to terminals are handled by
a standard NATO addressing scheme.
This section describes the main logic of the addressing
method.
This scheme makes use of three levels of addressing
(refer to figures 3.1-2 and 3.1-3 A and B).
a) The first level is the logical identification of
the e̲x̲t̲e̲r̲n̲a̲l̲ ̲c̲h̲a̲n̲n̲e̲l̲s̲ and T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲s̲ where
- each external channel or communication path
to TARE's, TRC's, Point-to-point connections,
CCIS and SCARS II is identified by a unique
three character C̲h̲a̲n̲n̲e̲l̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲, and
- each Terminal Position is addressed as a whole
by a unique T̲e̲r̲m̲i̲n̲a̲l̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲ ̲(̲T̲D̲)̲ (Defined
in 3.2.3.1..C1).
b) The second level is the logical identification
of the military S̲t̲a̲f̲f̲ ̲C̲e̲l̲l̲s̲ that eventually shall
receive the messages. Each staff cell is uniquely
identified by a three character S̲t̲a̲f̲f̲ ̲C̲e̲l̲l̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲
̲(̲S̲C̲D̲)̲.̲ The Staff Cell is the smallest addressable
unit in the system. Each staff cell is assigned
to one and only one Terminal Position, and up to
five staff cells may be assigned to the same Terminal
Position. The CAMPS Supervisor controls the original
assignment and any subsequent reassignments.
The operators of the system that represents the
staff cells are not identified in the addressing
scheme.
The operators are, however, identified with an
operator ID and associated password to enable secure
sign-in and audit trail of logs. The operators
are assigned to terminal positions so that an operator
can sign-in at one and only one terminal position.
Up to 15 operators can be assigned to one terminal
position, with a total of 400 operators per CAMPS
site.
c) The third level is the formal addressing of m̲e̲s̲s̲a̲g̲e̲s̲
transmitted and received by a CAMPS site. The CAMPS
system as a whole contains too many staff cells
to use that unit as a formal address. The address
of a message is based on
1) a set of Plain Language Action Addresses, ACTION
PLA's.
2) a set of INFO PLA's.
3) a set of Subject Indicator Codes (SIC's) describing
the type of unit within a PLA that shall receive
the message, and whether it is an exercise
message or a message requiring special handling.
4) the PLA representing the originating office.
5) a set of Routing Indicators (RI's) where each
RI identifies a network.
d) The a̲d̲d̲r̲e̲s̲s̲i̲n̲g̲ ̲l̲o̲g̲i̲c̲ is shown in figure 3.1-3A
and B and is in short that the d̲r̲a̲f̲t̲e̲r̲ or originator
of a message inserts ACTION and INFO address information
in the message in form of PLA's and SIC's. The
system itself inserts the originator PLA. The drafter
may insert the PLA's either as:
1) full text PLA's
2) a PLA reference numbers with a one-to-one connection
with the PLA's (PLA-REF).
3) AIG's (Address Indicator Group) where each
AIG is a set of ACTION and INFO PLA's.
4) The originator, further, enters the staff cell
designators (SCD's) for all the staff cells
that shall receive a copy locally, i.e. at
the originating CAMPS site.
The s̲y̲s̲t̲e̲m̲ ̲c̲o̲n̲v̲e̲r̲t̲s̲ the PLA's and/or AIG's into
Routing Indicators (RI's) using a stored list of
PLA-to-RI's. Each PLA may point to up to 3 different
routing indicators and the system looks for the
first RI that has an open channel that satisfies
the security requirements. The RI's, the SIC's
and the originator is then stored in the ACP127
message for onward transmission. The message is
then routed to the relevant channels via the stored
RI-to-Channel Designator relationship.
If the system does not find an open channel that
meets the security requirements then the message
is sent to a Message Service Position for alternate
routing as described in section 3.2.1.6.1.
The message is thereafter d̲i̲s̲t̲r̲i̲b̲u̲t̲e̲d̲ ̲l̲o̲c̲a̲l̲l̲y̲ within
the originating CAMPS by using the SCD's (refer
to above).
e) A C̲A̲M̲P̲S̲ ̲s̲i̲t̲e̲ will receive messages that are
1) intended for local users of the CAMPS
2) intended for CCIS or SCARS II
3) intended for a TRC or point-to-point connection
attached to the CAMPS site
4) intended for relay in accordance with the relay
instruction in Format line 4 of the ACP 127
format.
f) The distribution of the message with a CAMPS site
is based on the PLA's or AIG's in format line 7
and 8 of the ACP 127 formatted message. As shown
in fig. 3.1-3B each PLA represent a headquarter
and will point to a unique list of SIC's specific
to that PLA. Each SIC in the list again points
to a Standard Distribution List that identifies
the ACTION and INFO staff cells to whom the message
shall be distributed.
If the SIC identifies an exercise message then
the distribution will be based on a special Exercise
Standard Distribution List.
figure 3.1-2
figure 3.1-3A
figure 3.1-3B
3.1.1.3 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The functional capabilities of the CAMPS system are
divided into:
a) Handling of Message
b) System Supervision
c) Storage and Retrieval
d) Logging
e) Statistics
f) Security
3.1.1.3.1 H̲a̲n̲d̲l̲i̲n̲g̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
a) O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲
1) The facilities provided for assistance in message
preparation are based on an interactive question
and answer procedure. Entries made by the operators
are validated before acceptance by CAMPS. A
tabular overview of the functional capabilities
are given at the end of this subsection.
2) The aid offered for i̲n̲i̲t̲i̲a̲l̲ ̲p̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ of
messages includes assistance in generation
of the message header in plain language or
use of a preformatted header as specified in
section 3.2.1.2.1.1. After generation of the
message header, the operator may optionally
initiate the message preparation of the message
text part using a set of stored preformatted
texts, or enter the text in free format.
3) An essential part of the message preparation
is the c̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲ of messages. This function
is supported with facilities for distribution
of messages under preparation to staff cells
nominated by the message originator.
4) M̲e̲s̲s̲a̲g̲e̲ ̲E̲d̲i̲t̲i̲n̲g̲ may take place at any time
until the message is sent for releaser's approval.
5) C̲o̲m̲m̲e̲n̲t̲s̲ ̲may be submitted by any staff cell
as a normal comment or as an answer to a coordination.
The comments may be transmitted to the message
originator or to any other staff cell.
6) When message preparation is completed, the
message will be transmitted to a designated
message r̲e̲l̲e̲a̲s̲e̲ position. The decision (approval
or rejection) of the releasing authority is
signalled to the message originating terminal.
7) Message preparation session may be s̲u̲s̲p̲e̲n̲d̲e̲d̲
at any point prior to release authorization.
Suspension may be by command from the originator
or automatically if a high precedence message
has to be delivered to the message originator's
position. A suspended message preparation session
may be resumed from the point where it was
suspended.
8) In addition to the CAMPS message preparation
positions, the system also accepts complete
messages input from paper tape readers, from
OCR's, from colocated SCARS II equipment, or
colocated CCIS equipment.
9) When a message has been released to the telegraph
network the format is automatically translated
to ACP-127 format. Plain language addressees
are used to determine Routing Indicators. For
addressees which cannot be automatically translated
the appropriate section of the message will
be displayed at a supervisory position to allow
the routing indicator to be entered manually.
10) Copies of messages released to the telegraph
network will be locally distributed. The local
distribution is based on the staff cell designators
entered during message preparation. Copies
of outgoing messages will contain the statement
"outgoing message" to make it distinct from
incoming messages.
b) I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
1) The system r̲e̲c̲e̲i̲v̲e̲s̲ and s̲t̲o̲r̲e̲s̲ incoming messages
from the TARE network, and relay centers. Messages
are received in the ACP-127 format using the
alphabets ITA2 or 5.
2) The messages are v̲a̲l̲i̲d̲a̲t̲e̲d̲ for ACP-127 format
accuracy, message serial number and security
for the circuit. Any discrepancies are reported
to the supervisor.
3) The system determines the headquarters being
addressed (through the PLA's) and performs
a l̲o̲c̲a̲l̲ ̲d̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲of the message based on
the assocaited standard distribution lists
for all the SICs included in the message.
1 skema uden nummer
1 skema uden nummer
3.1.1.3.2 S̲y̲s̲t̲e̲m̲ ̲S̲u̲p̲e̲r̲v̲i̲s̲i̲o̲n̲
a) CAMPS shall provide a number of Terminal Positions
for Supervisory Control, Message Handling Assistance
and Status and Alarm Monitoring.
b) The supervisory functions are divided into four
destinct groups as shown on figure 3.1-4.
c) Group 1 Supervisory functions can be assigned to
one Terminal Position at a time only. No
other functions other than those listed
in Group 1,2, and 3 can be assigned at
the same time. The functions include
1) functional reconfiguration
2) control and update of system tables
3) Printout of Reports
4) Printout of Logs
5) Printout of Status Information.
d) Group 2 Message Distribution Control functions
may be assigned to one or more Terminal
Positions. Messages with special handling
and messages where the system is unable
to automatically determine routing and/or
distribution are queued to all terminal
positions having these functions assigned.
The functions provide interactive facilities
to review messages and to insert or update
distribution information.
e) Group 3 Message Service functions may be assigned
to one or more Terminal Positions. When
operators during message preparation require
assistance then their messages will be
queued to all terminal positions having
these functions assigned. The functions
provide interactive facilities to review
messages, correct messages, enter routing
indicators and change routing.
f) Group 4 Engineering functions are assigned permanently
to a dedicated Software Maintenance Position.
The function includes Initialization, Restart,
Software Maintenance, and Hardware Reconfiguration.
figure 3.1-4
3.1.1.3.3 S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲
a) CAMPS provides functional capabilities for on-line
storage of all incoming and outgoing messages in
a short term storage (up to a few days depending
on traffic and assigned disc space). After that
the messages will be kept for a period of 30 days
on off-line disc volumes (long term storage).
b) It will be possible to retrieve messages from the
short term storage within 4 seconds.
c) The maximum time for retrieval of messages from
the long term storage will be 4 minutes from the
time that the disc volume is loaded.
3.1.1.3.4 L̲o̲g̲g̲i̲n̲g̲
All transactions between the CAMPS system and the external
channels, the users of the Terminal Positions and the
Supervisors are uniquely identified and logged. The
logging takes place at initiation of the transaction
with recording of transaction type, operator or channel
identification and Date Time Group. A number of transactions
also require a log recording at termination. See section
3.2.5.
3.1.1.3.5 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
a) Statistical information on i̲n̲c̲o̲m̲i̲n̲g̲ ̲a̲n̲d̲ ̲o̲u̲t̲g̲o̲i̲n̲g̲
̲m̲e̲s̲s̲a̲g̲e̲s̲ is measured and compiled on a per channel
basis. The system records totals for hourly, daily,
weekly, and monthly periods. The statistical information
include: total number of messages by precedence
level, number of messages by security classification
category, number of messages by special handling
category.
b) A special statistic is compiled for m̲e̲s̲s̲a̲g̲e̲s̲ ̲r̲e̲j̲e̲c̲t̲e̲d̲
for manual editing including: total number of rejected
messages, transmission identifications, routing
indicator of station or origin, time of receipt,
time(s) of retry, reason(s) for rejection.
c) Statistics for m̲e̲s̲s̲a̲g̲e̲ ̲d̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲are maintained.
The statistics are compiled for distribution of
incoming and distribution of outgoing messages
separately and on a per recipient basis. The statistic
includes: Number of messages delivered, maximum
and average length, number of messages by security
classification category, number of messages by
special handling category, number of messages by
precedence level. Further for distributed messages
the average and maximum number of terminals included
in the distribution is recorded as well as the
number of messages which required supervisory assistance.
d) For measuring of s̲y̲s̲t̲e̲m̲ ̲p̲e̲r̲f̲o̲r̲m̲a̲n̲c̲e̲ the c̲h̲a̲n̲n̲e̲l̲
a̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲ and occupancy is measured for each
channel on an hourly, daily and monthly basis.
e) Statistics on the u̲s̲e̲ ̲o̲f̲ ̲m̲e̲s̲s̲a̲g̲e̲ ̲f̲o̲r̲m̲a̲t̲s̲ is compiled
for each terminal on an hourly, daily, weekly and
monthly basis and is maintained for the current
and previous day and current week.
f) The statistical requirements are described in depth
in section 3.2.6.1.1b
3.1.1.3.6 S̲e̲c̲u̲r̲i̲t̲y̲
a) The security requirements have two aspects: enforcement
of security procedures and monitoring of security.
This section will give an overview of the security
aspects. Details are given in section 3.4.5.
b) Enforcement of security procedures consists of
access control at user terminals and communication
lines, and control of output.
c) The a̲c̲c̲e̲s̲s̲ ̲c̲o̲n̲t̲r̲o̲l̲ is achieved by having a unique
identification of each user of the system and a
specification of the functions accessible to the
User.
d) The identification is based on unique passwords
which initially are allocated by the supervisor.
Passwords may only be changed by the supervisor.
e) Associated with the password information above
the access rights of the user is stored in the
system:
1) the functions accessible to the user.
- 2) the highest classification to which he has
access.
f) Access rights can only be inspected and changed
by the supervisor.
g) Terminals are uniquely identified in the system.
For each terminal the following information is
stored
1) The functions allocated to the terminal
2) Highest classification of data displayable
at the terminal.
3) Special handling categories displayable.
h) To utilize a terminal the user must first insert
a key in a physical locking mechanism to set the
terminal in on state. The operator then enters
his password for validation by the system. If
the password is correct it identifie the user and
his access rights. These access rights are compared
with the functional capabilities and the security
classification assigned to the terminal. The user
at the terminal is then given only the functional
capabilities that matches and the lower of the
two classifications (his own or that of the terminal).
i) O̲u̲t̲p̲u̲t̲ ̲c̲o̲n̲t̲r̲o̲l̲ is concerned with security enforcement
on data leaving the system, that is, data presented
at VDU terminals, data printed at printers, data
output via paper tape punches, data transmitted
via communications lines and data stored on removable
disk volumes.
j) Classified data are never displayed or printed
at unattended terminals, and, before transmitting
data of security classification higher than a preset
value to a terminal, the operator is warned and
interrogated if the environment is cleared for
the message. Under no circumstances is the system
allowed to output a message of a security classification
higher than what the output device and user are
authorized to receive.
k) M̲o̲n̲i̲t̲o̲r̲i̲n̲g̲ ̲o̲f̲ ̲s̲e̲c̲u̲r̲i̲t̲y̲ is composed of reporting
security violation attempts detected by the security
control procedures, and of logging of all transactions
in CAMPS.
l) Security violation checks are built into most interactive
terminal procedures and the system will report
to the supervision when these interactive procedures
are being misused.
m) Unintended m̲i̲s̲u̲s̲e̲ ̲o̲f̲ ̲t̲h̲e̲ ̲s̲o̲f̲t̲w̲a̲r̲e̲ ̲of the CAMPS
System is prevented by means of the CR developed
DAMOS security kernel and the secure DAMOS File
system.
3.1.2 M̲e̲s̲s̲a̲g̲e̲ ̲F̲l̲o̲w̲
a) This section will illustrate the flow of a message
through a CAMPS from preparation to transmittal
and from reception to distribution. The description
will emphasize on how the message is identified
throughout the preparation and distribution processes,
when it is stored and which retrieval keys are
used, and when and how it is logged.
b) The flow description is given by means of an example,
figure 3.1-5 to 3.1-7.
The example operates with 3 Terminal Positions,
a number of staff cells and a number of operators
as follows:
c) T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲ ̲1̲:
1) Terminal Designator LOT
2) Associated Staff Cells LOA,LOB,LOC
(SCD's)
3) Operator at TP1 AAA
d) T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲ ̲2̲:̲
1) Terminal Designator RET
2) Ass. SCD's REA,
REB
3) Operator at TP2 BBB
e) T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲ ̲3̲:̲
1) Terminal Designator INT
2) Ass. SCD's INA,INB,INC
IND
3) Operator at TP3 CCC
f) O̲u̲t̲g̲o̲i̲n̲g̲ external channel designator: CHO
g) I̲n̲c̲o̲m̲i̲n̲g̲ - - - : CHI
h) The i̲n̲t̲e̲r̲a̲c̲t̲i̲v̲e̲ ̲f̲o̲r̲m̲a̲t̲s̲ A,B,G1,G2,C1,D,E1 are used
in the example. The first line in all formats are
the transaction identifier showing e.g.: LOT018
241432 Z AUG. 80.
LOT: the Terminal Designator for the terminal
in use.
018: a transaction sequence number.
241432: the date time group (D,Hr,Min).
Z: time zone suffix
AUG: the month.
80: the year.
3.1.2.1 M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲
a) Step 1 An operator at Terminal Position 1 (TP1)
with Terminal Designator LOT drafts a
message using Initial Preparation, Format
A, and asks for coordination with Terminal
Designator INT or, optionally, staff cell
INA.
1) Transaction ID = LOT007 241208 ZAUG80
2) Message is stored in Historical Data Base HDB,
and retrievable under key = Transaction ID.
(excl. year = 80). The term HDB is used throughout
this section and identifies the file in which
the incoming and outgoing messages are stored
(i.e. the on-line and off-line message file).
3) Transaction is logged both when the transaction
is initiated and terminated.
b) Step 2 The message is presented to Terminal Position
3 with Terminal Designator INT. Reference
is made to the original message number
= step 1 - transaction id.
1) Transaction ID = INT056 241241Z AUG80.
2) No message is stored.
3) Transaction is logged at initiation and termination.
c) Step 3 The operator at Terminal Position 3 with
Terminal Designator INT prepares a comment
to the drafter of the message at TP1.
The Action addressee (under ACT) is entered
as the Terminal Designator for TP1 or optionally
as an SDC.
1) Transaction ID = INT057 241246 ZAUG80.
2) The comment is stored with retrieval key =
INT057 241246Z AUG.
3) Transaction is logged at initiation and termination.
d) Step 4 The comment is presented at Terminal Position
1. Reference is made to the original comment
number = step 3-transaction ID.
1) Transaction ID LOT014 241250Z AUG80.
2) No message stored
3) Transaction is logged when queued for presentation.
e) Step 5 The message is edited first time at Terminal
Position 1. Retrieval of the message for
editing is made by reference to the first
part of the transaction Id of the transaction
where the message was initially prepared
= LOT007.
1) Transaction ID LOT018 241432ZAUG80
2) No message stored in HDB. Edited version is
stored in a message preparation file.
3) Transaction is logged both at initiation and
termination of the transaction.
f) Step 6 The message is edited the second (and last)
time at Terminal Position 1. The retrieval
key is this time part of the transaction
id for the transaction where it was last
edited, i.e. LOT018. The operator now
asks for a release of the message at the
end of this editing procedure.
1) Transaction ID = LOT030 241756ZAUG80.
2) The message is stored in HDB under key = Above
transaction ID LOT030 241756Z AUG.
3) Transaction is logged at initiation and termination.
h) Step 7 The message is presented to the associated
release position at terminal position 2
with Terminal Designator RET. (Each message
preparation terminal has one associated
release position. The CAMPS site can have
many release positions as the supervisor
can assign release authority to all terminal
position). If release is granted the message
will receive a new identification:
RXYYY 0056 2361811, where
RXYYY Release position code (RI).
0056 a release serial number unique for
the
236,18,11 Time of release granted in Julian
Date
Hr, Min.
1) Transaction ID=RET077 241806 Z AUG80
2) The new message identification code (excl.
year = 80) will be added as a retrieval key
to the message stored in the HDB during step
6
3) Transaction is logged at termination.
4) The transaction ID = RET077 241806 Z AUG80
is unique for the message and follows that
message even during subsequent retransmissions.
At transmission a channel ID is added to the
message in format line 1 as described below
in step 8.
i) Step 8 The converted message is transmitted to
external channel CHO with ID in message
header equal to transaction ID.
1) Transaction ID = CHO 111
2) No message is stored
3) Transaction logged when message is transmitted
4) Concurrent with the transmittal to external
channel CHO, a local copy of the message is
sent to staff cell INA in format E1 (ref. Fig.
3.1-5 initial preparation).
3.1.2.2 I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲
a) Step 9 The message in ACP 127 format is received
from external channel CHI. The message
header has a message ID = CHI 223. Where
CHI is the channel ID and 223 is a sequence
number used for continuity check.
1) transaction ID = CHI 223 241615Z AUG80
2) where the Date Time Group represents time of
reception.
3) No message is stored in HDB.
4) Transaction is logged at message reception.
b) Step 10 The system converts the message to CAMPS
Distribution format E1.
1) No transaction ID
2) The converted message is stored in HDB with
retrieval key = step 9 transaction ID i.e,
CHI 223 241615 Z AUG80.
c) Step 11 The message is presented to the address
with staff cell designator INA located
at Terminal Position 3 with Terminal Designator
INT.
1) Transaction ID = INT088 241733ZAUG80.
2) The above transaction ID is added as a new
retrieval key to the messages stored in the
HDB during step 10.
3) Transaction is logged when the message was
planned for presentation.
figure 3.1-5
figure 3.1-6
figure 3.1-7
