CHANGE PAGES TO FBIS DOCUMENTS

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP91-01355R000300100005-1
• Release Decision: RIPPUB
• Original Classification: U
• Document Page Count: 100
• Document Creation Date: December 23, 2016
• Document Release Date: August 7, 2013
• Sequence Number: 5
• Publication Date: June 1, 1988
• Content Type: MEMO

es".1?,,
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1 Ta"`
MEMORANDUM FOR: Distribution
THROUGH:
FROM:
SUBJECT:
REFERENCE:
Change Pages to FBIS Documents
ESG Memo dated 8 April 1988
Subject - Results of 7 April 1988 CCB
SES-098-88
1 June 1988
1. The Reference memo reported the CCB approval of CO-RFC-C-001-88,
CO-RFC-C-002-88, HU-RFC-C-004-88, HU-RFC-C-006-88, and HC-RFC-C-001-88, as
modified by the CCB. The SI (SES) was instructed (Reference) to update
the AFS System Specification (MPD-900-001C), the FBISI-1:ICD
MD-900-208), and the FBIS/Agency Classified Systems (MPD-900-207A)
in accordance with the changes produced by these RFCs and provide change
pages to holders of these documents.
STAT
2. The attached change pages to the AFS System Specification are the
current versions of ?the pages affected /and should be inserted into the
document, re lacing the corresponding pages. The other atechments are
the new FBI ICD, and the new version of the FBIS/Agency Classified STAT
Systems ICD.
3. This action completes the formal distribution of the
documentation changes resulting from the 7 April 1988 CCB.
4. For more information or additional copies of the attachments,
please contact
Attachments:
I
Change Pages to the AFS Sy stem Specification (MPD-900-001C)
First issue of the HIS ICD (MPD-900-208)
Revision A of the FBIS/Agency Classified Systems ICD (MPD-900-207A)
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07 : CIA-RDP91-01355R000300100005-1
STAT
STAT
STAT
STAT
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
SUBJECT: Change Pages to FBIS Documents
DS&T/FBIS/ESG/ADD/SES
Distribution:
Original - C/ESG
1 - DC/ESG
1 - CCB Secretariat (ESG/PEO)
1 - C/E&PS
1 - C/OPS
1 - C/DRD
1 - C/WSS
1 - C/PROD
1 - C/AG
1 - SAM/AG,
1 - SAM/PRO
1 - SA/OPS
1 - C/FED
3 - C/HED
1 - C/ADD
1 - DC/ADD
6 - ADD Staff
1 -
1 -
1 -
1 -
1 -
1 -
1 -
1 -
COTR
FBIS/CO
LEC
GE/SES Staff
GE/SES Chrono
GE/SES CCB Chrono
FBIS Registry
Originator
SES-098-88
(1JUN88)
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
STAT
STAT
STAT
11
mpn_onn_nnir Onto 01111flTifTrAMTAM 1^nel
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1 '
CHANGE LOG
TITLE: FESIS SYSTEM SPECIFICATION DOCUMENT MPD-900-001C
REV DATE
PAGES AFFECTED
RFC NO.
2/6/87
2/6/87
2/6/87
6/29/87
11/23/87
11/23/87
11/23/87
11/23/87
11/23/87
3/1/88
4/7/88
vii, 6, 22, 34, 35
vii, 5, 11, 20, 21, 22, 23, 24, 25,
33, 36, 41
vi, viii, 6, 7, 37, 38, 42, 43,
44, 45, 46, 47, 48, 49, 50, 51, 52, 53
24, 26, 27, 28, 29, 30, 31, 32, 33, 34
40
17
21
vi, 21, 23
iv, v, vii, 1, 3, 7, 42, 43,
44, 45, 46, 47, 48, 49, 50, 58
vii, 6, 8, 12, 13, 37, 38, 40, 50
vii, 2, 6, 7, 37, 38, 39, 41, 42,
45, 50
GE-012-86
GE-018-86
GE-019-86
GE-020-86R1
CO-RFC-C-001-87
HU-RFC-C-001-87
HC-RFC-C-001-87
HC-RFC-C-002-87
FS-RFC-C-001-87
C0-RFC-C-002-87
C0-RFC-C-002-88
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
upn_onn_nnir
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
SECTION TITLE
3.3 System Interface Definition
3.3.1 AUTODIN
3.3.2 Telex
3.3.3 Dedicated Line
3.3.4 Wire Service Subscribers
3.3.5 Independent Contractors
3.3.6 P&PD
3.3.7 Agency Classified Communications System
3.3.8 r::17ted Press Agency
3.3.9
3.3.10 rect Dial Up Service
3.4 System Availability/Reliability
3.4.1 Allocation
3.4.2 Lifetime Requirements
3.4.3 Single Point Failure
Mean-Time-To-Restore
3.5 System Maintainability
3.5.1 Fault Isolation
3.5.2 Human Factors
3.5.3 Maintenance
3.5.4 Equipment Packaging
3.5.5 Equipment Checkout
3.5.6 Non-Interruptive Maintenance
3.5.7 Marking and Interchangeability
3.5.8 Accessibility
3.5.9 Fault Detection and Correction
3.5.10 Environmental Conditions
3.5.11 Transportability and Handling
3.5.12 Security
3.5.13 Safety
3.5.14 Operability
3.5.14.1 Degree of Automation
3.5.14.2 Use of Redundancy Features
3.5.15 Design and Construction Practices
3.5.15.1 General
3.5.15.2 Controls
3.5.15.3 Control Panel Identification
3.5.15.4 Metal Parts
3.5.15.5 Workmanship
3.5.15.6 Reliability
iii
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
STAT
MPD-900-001C FATS SPRrTPTCATTON 7 April 1988
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
TBD/TBR/TBS LIST
Paragraph(s) Description
3.2.4.1.1.2.2 The Field Communications Function ... receive
... Telex at 50 to 4800 (TBR) Baud.
3.2.4.1.1.2.5 The Field Communications Function from the
BBC (Interface and Format TBD)
3.2.4.1.1.6 The Field Communications Function ...30 (TBR)
seconds of receipt.
3.2.4.1.2.6.3 The Field Communications Function ... send ...
Telex at 50 to 4800 (TBR) Baud.
3.2.4.1.2.6.6 The Field Communications Function ... to the BBC
(Interface and Format TBD)
3.2.4.1.3.2 The Field Communications Function ...ten (TBR)
mailboxes per entries ...
3.2.4.1.4.2 The Field Communications Function ... collecting
defined (TBD) statistics...
3.2.4.1.4.3 The Field Communications Function ...outgoing
message automatically within 10 (TBR) seconds
...., ....new packages of addresses within 120
(TBR) seconds.
3.2.4.2.6 The Press Agency Collection Function shall be
capable of handling the load of 16 (TBR)
distinct lines.
3.2.4.3.7
3.2.4.5.1
3.3.8
Field Segment ...versions shall be stored for 60
(TBR) days.
The Field Configuration shall support up to 50
(TBR) concurrent users.
Selected Press Agency "TBS"
5.2 Field Locations - Facility Requirements (TBD)
vii
Declassified in Part- Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
mpn_onn_nnir inno
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
rage z.
2.0 APPLICABLE DOCUMENTS
2.1 Compliance Documents
2.1.1 Statement of Work for Automated FBIS System
2.1.2 Automated FBIS System External Interface Control
Documents
MPD-900-200 - FBIS/AUTODIN
MPD-900-201 - FBIS/TELEX
MPD-900-202 - FBIS/Dedicated Line
MPD-900-203 - FBIS/Electronic Subscribers
MPD-900-205 - FBIS/P&PD
MPD-900-206 - FBIS/Independent Contractors
MPD-900-207 - FBIS(Azelcy Classified Systems
MPD-900-208 - FBIS
MPD-900-209 - FBIS/Direct Dial Up Service
2.2 Other Documents
2.2.1 FBIS Automation Requirements
MPD-000-002
2.2.2 FBIS Baseline Description
MPD-000-001
2.2.3 Automated FBIS System Concept of Operations
MPD-900-100
2.2.4 FBIS Editorial Handbook dated January 1986
2.2.5 Facilities Baseline Document
MPD-100-701
2.2.6 Facilities Requirements Document
MPD-100-702
2.2.7 Human Engineering Design Criteria for
Military Systems, Equipment and Facilities
MIL-STD-1472C
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
SITAT
mon [IAA nnin
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R0003b6100005-1
rage 6
3.1.2.4 Composition Function
The Headquarters Classified Segment shall have the capability
to perform automated composition of text and graphics for
"local" hardcopy printing and reproduction by P&PD.
3.1.3 Communications Segment Functional Description
The Communications Segment shall handle all communications and
message traffic as it enters or leaves the Automated FBIS
System. The Communications Segment shall be divided into the
following major functions: Headquarters Unclassified
Communications Function, and Headquarters Classified
Communications Function.
3.1.3.1 Headquarters Unclassified Communications Function
The Headquarters Unclassified Communications Function shall
process unclassified communications and message traffic for
FBIS Headquarters. Headquarters Unclassified Communications
shall:
a) provide automated support to receive, verify, lo
store, and route incoming message traffic from
AUTODIN, Telex, Direct Dial Up Service and Dedicated
Line,
b) provide automated support to retrieve, format, log,
store transmit, and verify outgoing message traffic
viar?MUTODIN, Telex, Direct Dial Up Service and
Dedicated Line,
c) accept Wire Service output from the Headquarters
Unclassified Segment and transmit this data to 32 Wire
Service consumers, with a capability to expand to 128
consumers,
d) accept simultaneous electronic inputs of word
processing documents via modem and commercial dial up
telephone circuits.
3.1.3.2 Headquarters Classified Communications Function
The Headquarters Classified Communications Function shall
process classified communications and message traffic for FBIS
Headquarters. This function shall provide automated support to
receive, verify, log, store, and route incoming message
traffic.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
STAT
STAT
ULM OAA AM,
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R00030010000eT 1
rage I
3.1.4 Field Segment Functional Description
The Field Segment shall provide automated support to handle all
unclassified message traffic, the collection of selected Press
Agencies, the selection, translation, editing, and review of
all items selected for processing, the preparation of messages
for transmittal to headquarters and to lateral consumers, and
bureau database and file maintenance support.
3.1.4.1 Field Communications Function
The Field Communications Function shall handle all unclassified
communications and automated message traffic to and from the
field locations. These functions shall:
a)
provide automated support to receive, verify,
store, and route incoming message traffic fro
INTERNET, Direct Dial Up Service, Telex or Dedicated
Lines, and
b) provide automated support to retrieve, format, log,
sto ansmit, and verify outgoing message traffic
via INTERNET, Direct Dial Up Service, Telex and
Ded cated Lines.
3.1.4.2 Press Agency Collection Function
The Field Segment shall automatically collect, print, and store
selected Press Agency material.
3.1.4.3 Monitor and Editor Processing Function
The Field Segment shall enable monitors to create and store
documents (e.g., summaries, FYI's, or translations of selected
items), and release them to editors for further processing.
The editors shall have the capability to create, access, and
edit files, send files back to monitors, and prepare messages
for transmission.
3.1.4.4 General Support Function
The Field Segment shall provide a generalized capability to
maintain files, and to support preparation of correspondence
and reports.
3.1.4.5 Field Configuration
The Field Segment shall provide workstations, file servers, and
printers that are capable of Local Area Network and Stand-alone
"local" operations.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
STAT
STAT
mon ann nnir / ince,
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
ra6c a,
3.2.3 Communications Segment
The Communications Segment shall consist of the Headquarters
Unclassified Communications Function, and the Headquarters
Classified Communications Function. The functions and
interfaces supported by the Communications Segment are depicted
in Figure 3.2.3-1.
3.2.3.1 Headquarters Unclassified Communications Function
3.2.3.1.1
The Headquarters Unclassified Communications Function shall be
that portion of the Communications Segment that shall handle
unclassified communications. The following paragraphs describe
the requirements for the Headquarters Unclassified
Communications Function.
Field Traffic
The Headquarters Unclassified Communications Fu shall
support two-way communications with bureaus via AUTODIN,
Telex, and Dedicated Line (London only) in accordance with the
respective Interface Control Documents for these interfaces.
Telex shall be used as a backup to and AUTODIN. There
shall be a Dedicated Line between FBIS Headquarters and the
London Bureau to provide backup to AUTODIN for this bureau.
The Headquarters Unclassified Communications Function shall
support two dedicated interfaces to AUTODIN switching centers
at Andrews AFB and Ft. Detrick via standard Telecommunications
Line Controllers and modems within Headquarters Unclassified
Communications (see FBIS/AUTODIN Interface Control Document,
MPD-900-200).
The Headquarters Unclassified Communications Function shall
suDDort a dedicated interface to the
switching center at STAT
via existing connectivity installed betwee STAT
Headquarters, and Reston, Va. Refer to the FBIS :STAT
Interface Control Document, MPD-900-208. 1
STAT
STAT
The Headquarters Unclassified
support a dedicated interface
S&T Units) via Direct Dial Up
and a separate PC workstation
Segment computer.
3.2.3.1.1.1 Incoming Communications
3.2.3.1.1.1.1 Receiving
3.2.3.1.1.1.1.1 AUTODIN
Communications Function shall
from the Field Segment (including
Service, modem, PC workstation,
connected to the Communications
The Headquarters Unclassified Communications Function shall be
capable of automatically receiving an average of 2100 messages
(840,000 words) per 24 hour day, 7 days a week from
AUTODIN. The peak input rate per hour shall be 300 messages
with an average of 133 words per message.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
STAT
MPD-900-00i VUTC COVOTOTPATTAM on
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1 "
rage so
COMMUNICATIONS FUNCTIONS
FICCF HEADQUARTERS CLASSIFIED
HUCF = HEADQUARTERS UNCLASSIFIED
AGENCY
CLASSIFIED
COMMUNICATIONS
AUTODIN
COMMUNICATIONS SEGMENT
LECF
3.2. 3.2
to.
HUGE
3. 2. 3. 1.1.1 1.1
RCA 1 I LEXTRA
DEDICATED LINE
DIRECT DIAL UP
SERVICE
3.2.3.1.1.2.5.1
3. 2. 3. 1.1. 1.1. 1
3.2.3.1.1.2.5.1
3. 2. 3. 1. 1.1. 1.2
2.2. 3.1. 1.2.5.2
HC) CLASS SEG
STAT
3.2. 3..1. 1. 1.1. 3
3.2. 3.1,1. 2.5. 3
3. 2. 3. 1. 1. 1. 1. 4
3.2.3.1.1. .5.4
1-414 tc+
NON-ELECTRICAL
HQ UNCLASS SEG
3. 2. 3.1. 2
I NIIIPENDINT
CONTRACTORS
3. 2. 3. . 1. 1. 7
NOW-ELECTRICAL
DIRECT DIAL UP 32 4, 1. 1.2.6
I SERVICE 3. 2. 4. 1. 2. 6. 7
DEDI CAT EC LINE
3. 2. 4. 1. 2. 6. 3
1E LEX
3.2.4.1.2.6.2
3.2.4.1.1.2.?
of.
3. 2. 4. 1. 1. 2. 2
to
3. 2. 4. 1. 1 2.4
3. 2. 4. 1. 2. 6. 4
AUTODIN
NGL I SH LANG
PRESS
3.2 4. 1. 2. 6. 1
3. 2. 4. 1. 1. 2. 1
3. 2. 4. 2
FIELD SEGMENT
FBIS COMMUNICATIONS SEGMENT IN1 ERFACES
(LOGICAL FLOW)
FIGURE 3. 2. 3-1
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
STAT
mpn-qnn_nnir
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
rage JV
3.2.3.1.1.1.1.2 Telex
The Headquarters Unclassified Communications Function shall be
capable of receiving Telex messages at 1200 baud from the RCA
Global store and forward system TELEXTRA/DATABANK. Incoming
messages shall be stored in the RCA Global DataBank until AFS
software dials the access number for RCA and provides the
proper password.
3.2.3.1.1.1.1.3 Dedicated Line
The Headquarters Unclassified Communications Function shall be
capable of automatically receiving messages from the London
Bureau over the Dedicated Line in accordance with MPD-900-202.
3.2.3.1.1.1.1.4 Direct Dial Up Service
The Headquarters Unclassified Communications Function shall be
capable of receiving messages from the Field Segment and S&T
Units via the Direct Dial Up Service in accordance with
MPD-900-209.
3.2.3.1.1.1.2 Verifying
The Headquarters Unclassified Communications Function shall be
capable of automatically verifying that all messages received
via AUTODIN, the selected Commercial Communications Network and
the Dedicated Line are free of transmission errors; this shall
be accomplished in accordance with AUTODIN Mode I or Mode V
(with commercial communications and Dedicated Line only)
protocol procedures. Detected errors shall be routed to a
communication operator's workstation for resolution.
3.2.3.1.1.1.3 Capitalization
The Headquarters Unclassified Communications Function shall
inspect that part of the input data stream received in 5 level
Baudot and capitalize characters according to the rules stated
in the FBIS Editorial Handbook, Section 14.21, page 124.
3.2.3.1.1.1.4 Logging
The Headquarters Unclassified Communications Function shall
automatically log (softcopy) each incoming message and retain
this log for a period of 30 days.
3.2.3.1.1.1.5 Storing
The Headquarters Unclassified Communications Function shall
have the capability to automatically store each incoming
message on-line for a period of 30 days.
3.2.3.1.1.1.6 Daily Report and Wire Service Function Interface
The Headquarters Unclassified Communications Function shall
forward each received message to the Daily Report and Wire
Service Function.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07 : CIA-RDP91-01355R000300100005-1
unn nnn nnIn C1infIT1/1-/I A Inl.nte
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R0003b6106606:1-3
' rage 4 1
3.2.3.1.1.2.5.2 Telex
The Headquarters Unclassified Communications Function shall be
capable of transmitting outgoing message traffic through the
RCA Global store and forward system TELEXTRA/DATABANK at 1200
baud.
3.2.3.1.1.2.5.3 Dedicated Line
The Headquarters Unclassified Communications Function shall be
capable of transmitting outgoing message traffic via the
Dedicated Line in accordance with MPD-900-202.
3.2.3.1.1.2.5.4 Direct Dial Up Service
The Headquarters Unclassified Communications Function shall be
capable of transmitting outgoing message traffic via the Direct
Dial Up Service in accordance with MPD-900-209.
3.2.3.1.1.2.6 Verifying
The Headquarters Unclassified Communications Function shall
verify that each outgoing message shall have been sent without
format or transmission errors. This shall be accomplished in
accordance with AUTODIN Mode I/V protocols.
3.2.3.1.2 WSS Output
The Headquarters Unclassified Communications Function shall
accept Wire Service output from the Daily Report and Wire
Service Function and transmit this data to the Wire Service
subscribers. The capability shall exist to route the data to
any number or all subscribers based on a routing indicator
added to the text. The capability shall exist to handle the 32
subscribers. The design of this function shall not preclude
expansion to support up to 128 subscribers. The Headquarters
Unclassified Communications Function shall provide backup
circuits in the event of failure of the prime circuits. The
Headquarters Unclassified Communications Function shall provide
a data transmission rate of 1200 baud.
3.2.3.2 Headquarters Classified Communications Function
The Headquarters Classified Communications Function shall be
that portion of the Communications Segment that shall handle
classified message traffic. The Headquarters Classified
Communications Function shall support a classified two-way link
via the Agency Classified Communications System to Agency
Headquarters in accordance with MPD-900-207.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
M14)-900-001C FATS RPRCTOTCATTAN A--11 trios
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
LC6C
3.2.4 Field Segment
3.2.4.1
3.2.4.1.1
3.2.4.1.1.1
The functional elements of the Field Segment are depicted in
Figure 3.2.4-1.
Field Communications Function
Incoming Messages
(Excluding London) This capability shall handle the message
traffic load of 500 messages per operational day.
3.2.4.1.1.2 Receiving
3.2.4.1.1.2.1 The Field Communications Function shall be capable of receiving
all incoming messages in JANAP 128 or ACP 127 formats.
Optional communications flow control shall be provided.
3.2.4.1.1.2.2 The Field Communications Function shall be capable of receiving
all incoming Telex Messages at 50 to 4800 (TBR) baud.
3.2.4.1.1.2.3 The Field Communications Function shall be capable of receiving
all incoming messages and communications via each communication
line in accordance with its defined interface.
3.2.4.1.1.2.4 The Field Communications Function shall be capable of receiving
all incoming messages and communications via the network
using the Communication Instructions Tape Relay cr?o;ledures, ACP
127 format, including US SUPP-1 and via the INTERNET network.
3.2.4.1.1.2.5
3.2.4.1.1.2.6
3.2.4.1.1.3
3.2.4.1.1.4
3.2.4.1.1.5
3.2.4.1.1.6
(London Only) The Field Communications Function shall be
capable of receiving incoming messages and communications from
the BBC (Interface and format TBD).
The Field Communications Function shall be capable of receiving
all incoming messages and communications via Direct Dial Up
Service system and local GFE modems.
The Field Communications Function shall automatically print and
log each incoming message.
The Field Communications Function shall automatically store
each incoming message for a period of 7 days on-line.
The Field Communications Function shall make available each
incoming message to the Incoming Message Support function.
The Field Communications Function shall provide the capability
to automatically alert the communication operator and Slot
Editor of the receipt of Immediate and Flash precedence
messages with both a visual and an audible alert within 30
(TBR) seconds of receipt. Flash notification shall require
manual action to deactivate.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
STAT
mon_onn_nnin
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100605-13
rage 4)
3.2.4.1.2.6.7 The Field Communications Function shall be capable of
transmitting all outgoing messages and communications via
Direct Dial Up Service system and local GFE modems.
3.2.4.1.3
3.2.4.1.3.1
3.2.4.1.3.2
Incoming Message Support
The Field Communications Function shall provide the capability
to receive, process, store and disseminate to the appropriate
addressees within the bureau all message traffic received under
continuous and non-continuous operations including those
associated with scheduled and unscheduled circuit signoffs.
The Field Communications Function shall have the capability to
disseminate incoming message traffic to four precedence
mailboxes and ten (TBR) mailboxes per entries on the PASS
field, or as defined by the user. A designated position shall
have the capability to further disseminate message traffic
manually to 50 (TBR) definable "clipboards".
3.2.4.1.3.3 The Field Communications Function shall provide the local
capability to respond to the creation of new
mailboxes/clipboards and the deletion of mailboxes/clipboards.
3.2.4.1.3.4 The Field Communications Function shall be capable of
collecting defined statistics from the incoming message
traffic.
3.2.4.1.3.5 The Field Communications Function shall be capable of detecting
? the check numbers on Administrative messages and comparing them
with the corresponding table. Non-sequential entries shall be
reported to the operator for resolution.
3.2.4.1.4 Outgoing Message Support
3.2.4.1.4.1
3.2.4.1.4.2
3.2.4.1.4.3
The Field Communications Function shall provide the capability
to process outgoing messages and forward them for transmission
whenever the bureau is open, up to 24 hours a day, 7 days a
week.
The Field Communications Function shall be capable of
collecting defined statistics (TBD) from the outgoing message
traffic.
The Field Communications Function shall provide the capability
to append the appropriate precedence and provide routing
instructions to a document within 10 (TBR) seconds for all
compiled packages of addressees. The system shall also have
the capability to generate routing instructions for new
packages of addressees within 120 (TBR) seconds.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
Linn AAA AA1A Arn.rAm / A--41 1000
' Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
ra6c Jv
3.3 System Interface Definition
The following interfaces shall be supported by the Automated
FBIS System.
3.3.1 AUTODIN
This interface shall be as specified in the FBIS/AUTODIN
Interface Control Document, MPD-900-200.
3.3.2 Telex
This interface shall be as specified in the FBIS/Telex
Interface Control Document, MPD-900-201.
3.3.3 Dedicated Line
This interface shall be as specified in the FBIS/Dedicated Line
Interface Control Document, MPD-900-202.
3.3.4 Wire Service Subscribers
This interface shall be as specified in the FBIS/Electronic
Subscribers Interface Control Document, MPD-900-203.
3.3.5 Independent Contractors
This interface shall be as specified in the FBIS/Independent
Contractors Interface Control Document, MPD-900-206.
3.3.6 P&PD
This interface shall be as specified in the FBIS/P&PD Interface
Control Document, MPD-900-205.
3.3.7 Agency Classified Communications System
This interface shall be as specified in the FBIS/Agency
Classified Systems Interface Control Document, MPD-900-207.
3.3.8 Selected Press Agency
(TBS)
3.3.9
3.3.10 Direct Dial Up Service
This interface shall be as specified in the FBIS/Direct Dial Up
Service Interface Control Document, MPD-900-209.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
STAT
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
(
AFS/AGENCY CLASSIFIED SYSTEMS
INTERFACE CONTROL DOCUMENT
MPD-900-207A
7 April 1988
(1
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
mml_onn_ln/A nvAnn-rnY/In OVVIIIDUV TFIN 7 A___/1 1nng
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
CHANGE LOG
TITLE: FBIS/AGENCY CLASSIFIED SYSTEMS INTERFACE CONTROL DOCUMENT MPD-900-207A
REV
DATE
PAGES AFFECTED
RFC NO.
A
4/7/88
ALL
HC-RFC-C-001-88
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
mon_onn_qn/A ,
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000306100605-t1 3
TABLE OF CONTENTS
SECTION TITLE
1.0 INTRODUCTION
1.1 Functional Interface Description
1.1.1 Cables from MHF to AFS
1.1.2 FBIS Products from AFS to SAFE
1.1.3 Electronic Mail Between AFS and VM/AIM Users
2.0 APPLICABLE DOCUMENTS
2.1 Compliance Documents
2.2 Reference Documents
3.0 INTERFACE REQUIREMENTS
3.1 Physical Layer Description
3.2 Data Link Layer Description
3.3 Message Layer Description
3.3.1 Cables from MHF to AFS
3.3.1.1 Cable File Transmission
3.3.1.2 Cable File Format
3.3.1.3 Cable Types
3.3.2 FBIS Products from AFS to SAFE
3.3.2.1 Product File Transmission
3.3.2.2 Product File Format
3.3.3 Electronic Mail Between AFS and VM./AIM Users
3.4 Data Volume
3.4.1 Cables from MHF to AFS
3.4.2 FBIS Products from AFS to SAFE
3.4.3 Electronic Mail Between AFS and VM/AIM Users
3.5 Redundancy
4.0 INTERFACE VERIFICATION REQUIREMENTS
4.1 Description
4.2 Verification Categories
4.2.1 Inspection
4.2.2 Analysis
4.2.3 Test
4.2.4 Demonstration
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07 : CIA-RDP91-01355R000300100005-1
'mon OAA nn,A n
--
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91:51355R00035oi 00005-1 ?
APPENDIX A
APPENDIX B
APPENDIX C
APPENDIX D
APPENDIX E
APPENDIX F
APPENDIX G
APPENDIX H
TABLE OF CONTENTS (Continued)
CABLE FILE FORMAT
CABLE FORMATS
CABLE EXAMPLES
FILE FORMAT FOR FBIS PRODUCTS
DATA FIELDS FOR FBIS PRODUCTS
EXAMPLE OF ARTICLE IN BRS/SEARCH DATABASE LOAD FORMAT
AFS SYSTEM PREREQUISITES
AGENCY IBM MVS SYSTEM PREREQUISITES
ii
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
mpn_fann_wile nn r a, I ? ny Al.. ,r, ..
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000310100005-1 10
FIGURES
3.1-1
4.1-1
LIST OF FIGURES
TITLE
AFS To Agency Classified Systems Interface
Verification Matrix
iii
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
VOTOJArnmflv nTACCTOTTNI CVOMVUO "'fin _
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1 '
rage i
1.0 INTRODUCTION
This Interface Control Document (ICD) defines the interface between the
Automated FBIS System (AFS) and Agency Classified Systems residing at Agency
Headquarters. These shall include the Agency's Message Handling Facility
(MHF), SAFE and VM/AIM systems.
The interface shall provide a two-way electronic link to support the:
Transmission of cables from MHF to the AFS via an Agency IBM MVS
system, and
Transmission of FBIS Products from the AFS to SAFE via an Agency IBM
MVS system, and
Two-:,c:v transfer of (electronic mail) messages between users of the
AFS ...:stem and users of the VM/AIM electronic mail system via an
Agency IBM MVS system.
This ICD shall address only the interface between the AFS and an Agency IBM
MVS system via a GFE communication link that includes encryption devices and
modems. The interface between the Agency IBM MVS system and the MHF, SAFE and
VM/AIM systems shall be the responsibility of the Sponsor.
The hardwareand software prerequisites for the AFS and Agency IBM MVS
systems.1 that are required to support the interface, are included in Appendices
G and H, respectively.
1.1 Functional Interface Description
1.1.1 Cables from MHF to AFS
MHF shall transmit cables, via an Agency IBM MVS system, to the AFS for
dissemination to AFS users based on user-defined interest profiles resident on
the AFS VAX 8700 computer system. Dissemination of cables to the AFS by MHF
shall b..1 based on previously submitted FBIS-level reading requirements.
1.1.2 FBIS Products from AFS to SAFE
AFS shall transmit certain FBIS products to SAFE via an Agency IBM MVS
system. These products, shall include text-only portions of the JPRS Reports
and TRENDS Reports.
1.1.3 Electronic Mail Between AFS and VM/AIM Users
AFS users shall have the capability to send mail to and receive mail from
VM/AIM users electronically via an Agency IBM MVS system.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
mpo_0nn_qn7A
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIX-15P9-1:61355R0003-06106605171-B
rage -2.
2.0 APPLICABLE DOCUMENTS
2.1 Compliance Documents
2.1.1 Automated FBIS System Specification, MPD-900-001
2.2 Reference Documents
2.2.1 MHF External ICD, November 18, 1985
2.2.2 MHF Draft Specification May 25, 1984
2.2.1 MHF Cable Description Document, November, 1985
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
%inn Ann nn/A "Th.-rine...near flTArryrITun evemvue Trn
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
ragc
3.0 INTERFACE REQUIREMENTS
3.1 Physical Layer Description
The physical interface between the AFS and the Agency IBM MVS system shall
be provided by a DMB32 interface board. The DMB32 is a host-based,
intelligent communications controller that supports eight asynchronous lines,
one synchronous line and one printer port. This interface shall utilize the
synchronous line. The DMB32 shall provide the remote interconnection between
the AFS Classified System VAX 8700 and the Agency IBM MVS system via an
encrypted circuit. Modems, encryption devices and an IBM 370X (at the IBM MVS
end) shall be furnished as GFE. The (GFE) modem (at the AFS end) shall provide
the DMB32 with both the send and receive clocks. The data transmission speed
shall be at least 9600 bits per second over a full-duplex line. The electrical
interface shall be in accordance with EIA RS-232C. The physical interface is
shown in Figure 3.1-1.
' INTERFACE
A
8 3
7 2
0
0
- - >
' INTERFACE '

0
< - - - >
0

< - - - >
3
7
Figure 3.1-1 AFS to Agency Classified Systems Interface
3.2 Data Link Layer Description
The AFS to Agency IBM MVS system interface shall be implemented using the
Soft-Switch MAILbridge Server/DEC package. The interface shall support the
Synchronous Data Link Control (SDLC) protocol at the link level.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
mPn-enn_9n7A _ ?
Declassified in Part -Sanitized CopyApproved for Release 2013/08/07 CIA-RDP91-01355R0003150100005-1
Page 4
IC
3.3 Message Layer Description
3.3.1 Cables from MHF to AFS
3.3.1.1 Cable File Transmission
For each cable to be transmitted to the AFS, MHF shall create an ASCII
file (with no embedded non-printing characters) formed by the concatenation of
the CDS dissemination envelope and the cable text. The file shall then be
transferred from MHF to the AFS via MPS (which shall be resident on the Agency
IBM MVS system). MPS shall create a new file which is formed by appending a
one-up number (described in section 3.3.1.2) to the file received from MHF.
The resultant file shall then be transferred from the Agency IBM MVS system to
the AFS, where it shall be received as a VMSmail message. Each line in this
file shall be terminated with . The TO: line of the mail message shall
include nodename::username where:
nodename = AFSCABLE
username = MHFCABLE
3.3.1.2 Cable File Format
Cables, to be disseminated by MHF to the AFS, shall be included in a file
having the following four sections:
. Section Provided By
MPS header MPS
CDS dissemination envelope header MHF (CDS)
Cable text MHF (CDS)
CDS dissemination envelope ender MHF (CDS)
The MPS header shall be in the following format:
MSGNO nnnnn/mmmmm
nnnnn is a five-digit one-up number which shall be incremented by one for
each cable transmitted to the AFS. The numbering sequence shall run from
00001 to 99999 and then wrap to 00001. Provision shall be made by MPS to
set the one-up number nnnnn to a specific five-digit number agreed to by AFS
and MPS operational personnel (e.g. to reset to 00001 at the first of the
month). Upon request by AFS operational personnel, cables shall be
retransmitted by MPS with the original one-up number. In this case, the
original one-up number shall be included as the sequence mmmmm as shown
above. The format of the cable file is shown in Appendix A. A number
(referred to as the AFS_NUMBER) shall be built from the cable file as
follows:
If the prosign SERIAL: appears in the cable text, the associated
alpha-numeric sequence (up to 12 characters) shall be used. Otherwise, the
message identifier and message reference number, which are included in
the CDS dissemination envelope header, shall be used.
The AFS NUMBER shall be used for logging purposes and also to populate the
AFS NUMBER field of the Message Database.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIATDP9701355R0003.00100005T1
rage
3.3.1.3 Cable Types
The AFS shall be capable of receiving and processing the following five
cable types in the format specified below:
Cable Type
State
Military/Cable
R (DAO)
Cable Format Category
Originating ACP M (Military)
ACP S (State) STAT
ACP M (Military)
ACP M (Military)
DOI-103 Special N (Non-Agency) STAT
Format line usage and formats of the above cable types are described in
Backus Naur Format (BNF) in Appendix B. Examples of each cable type are shown
in Appendix C. Except for military cables, MHF shall assemble multi-take (or
multi-section) cables into a single-take (or single-section) message prior to
transmission to the AFS.
3.3.2 FBIS Products from AFS to SAFE
3.3.2.1 Product File Transmission
A transmit file, which includes the AFS one-up number and the JANAP 128
message (which includes the text file), shall then be transferred from the AFS
to an Agency IBM MVS system as a VMSmail message. Each line in this file shall
be terminated with . The TO: line of the VMSmail message shall include
nodename::username where:
nodename . SAFE
username . SAFE
The maximum size of the text file transmitted shall be 5,000,000 bytes.
Based on.nodename::username, the Agency IBM MVS system will route the file to
the SAFE System for further handling.
3.3.2.2 Product File Format
FBIS products shall be transmitted from the AFS to SAFE as the text of a
JANAP 128 message. Each message shall be included in a transmit file the
format of which is shown in Appendix D. The required message fields are also
indicated in Appendix D. All messages shall be transmitted with a precedence
of routine. FBIS products shall be transmitted as a complete report or as a
series of individual articles. JPRS reports shall be transmitted on an article
by article basis. All other reports shall be transmitted in the same format
that it is stored in the AFS product database, i.e. either as individual
articles or as an entire report. For each article (or report) to be
transmitted to SAFE, the AFS shall create an ASCII file (with no embedded
non-printing characters) which shall be in BRS/Search database load format.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
OTT nnn nn" "."'"n" ^"
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1 3
Page 6
Specifically, the file shall include the data fields described in Appendix E.
Those fields that are mandatory are also indicated in Appendix E. All other
fields may or may not have an entry depending on the content of the report or
article itself. An example of an article in BRS/Search database load format is
shown in Appendix F.
? The AFS shall append a header to each transmitted message. The AFS header
shall be in the following format:
MSGNO nnnnn/mmmmm
nnnnn is a five-digit one-up number which shall be incremented by one for each
message transmitted by the AFS. The numbering sequence shall run from 00001 to
99999 and then wrap to 00001. Provision shall be made by the AFS to set the
one-up number nnnnn to a specific five-digit number agreed to by AFS and MPS
operational personnel (e.g. to reset to 00001 at the first of the month). Upon
request by MPS operational personnel, messages shall be retransmitted by the
AFS with the original one-up number. In this case, the original one-up number
shall be included as the sequence mmmmm as shown above.
3.3.3 Electronic Mail Between AFS and VM/AIM Users
Electronic mail shall be implemented using VMSmail on the AFS and AIM on
the Agency VM system. The AFS user shall be provided with the full
functionality of VMSmail. AFS users shall be able to send mail to and receive
mail from VM/AIM users using appropriate facilities of VMSmail. The VM/AIM
user will be able to send mail to and receive mail from AFS users using
appropriate facilities of AIM. When mail is received by the AFS, the AFS user
shall receive the VMSmail alert:
New mail on node AFSn from vm/aimusername (hh:mm:ss)
The received mail may then be handled by the appropriate VMSmail facility, e.g.
READ, EXTRACT, etc. The TO: line of the VMSmail message shall include
nodename: :username where:
Mail from AFS to VM/AIM -
nodename . AIM
username = AIMusername (8 characters maximum)
Mail from VM/AIM to AFS -
nodename = AFS
username = AFSusername (8 characters maximum)
Note: The 8 character (maximum) AFS username specified by the
VM/AIM user shall be mapped to the 8 character (maximum)
AFS username on the AFS system via the Soft-Switch
MAILbridge server.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
??
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07 : CIA-RDP91-01355R000300100005-1 8
Page 7
3.4 Data Volume
3.4.1 Cables from MHF to AFS
The maximum volume supported by this interface shall be 2400 cables per day
each consisting of an average of 5,000 characters.
3.4.2 FBIS Products from AFS to SAFE
The interface shall support an average of 20 FBIS reports per day
consisting, in total, of a maximum of 12 Megabytes.
3.4.3 Electronic Mail Between AFS and VM/AIM Users
The maximum volume supported by this interface shall be 800 messages per
day each consisting of an average of 2,000 characters.
3.5 Redundancy
Redundant DMB32 communications controllers (one in each of three VAX 8700s)
shall be provided to support switchover in the case of failure of the primary
communications VAX 8700. In the event of failure of the primary VAX 8700,
switchover shall be accomplished as follows:
[1] The encryption device shall be reconnected manually to the
secondary VAX 8700 via an external patch panel (contractor-
supplied),
[2] The communications software shall then be restarted in the
secondary VAX 8700.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
mpn_enn_9n7A PUTC/ArVMPV MACCTATVIN CVemome Tern inn")
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1 '
ragC 0
4.0 INTERFACE VERIFICATION REQUIREMENTS
4.1 Description
All requirements defined in Section 3.0 shall be verified. Verification
shall be accomplished by either Inspection, Analysis, Test, or Demonstration as
defined in 4.2.1 through 4.2.4 below. The Verification Traceability Matrix
(VTM) is shown in figure 4.1-1. Regardless of which category of verification
is exercised, appropriate documentation shall be generated to record the
process or event and any conclusive results.
4.2 Verification Categories
4.2.1 Inspection
Verification of a requirement through inspection shall be accomplished by
examination of a configuration or a functional result, i.e., a physical or
visual review.
4.2.2 Analysis
Verification of a requirement by analysis shall be accomplished by:
a) conducting comparative evaluations, and/or
b) executing numerical or statistical algorithmic calculations.
4.2.3 Test
Verification of a requirement through testing shall be accomplished by
performing trial procedures internal to the development system, and achieving
results which meet or exceed the specification in question. Tests conducted on
specific segments of the design below the "system" level, shall be assessed
against values derived from the system specifications or ICD's. Simulation
software or special hardware may be required to emulate/simulate external
interfaces or data from an internal function. Analysis of test results where
necessary to verify compliance is implied.
4.2.4 Demonstration
Verification of requirements by demonstration shall be accomplished through
the execution of formally documented test procedures which exercise all or part
of the system including operational external interfaces. The verification
shall be deemed satisfactory when the resultant data meets or exceeds the
specifications documented (as pass/fail indicators) in the test procedures.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1 8
Page 9
VERIFICATION MATRIX (TBD)
FUNCTIONAL REQUIREMENTS
N/A
A
T D
3.0 Interface Requirements
3.1 Physical Layer Description
3.2 Data Link Layer Description
3.3.1 Cables from Miff to AFS
3.4.1 Data Volume
3.3.2 FBIS Products from AFS to SAFE
3.4.2 Data Volumes
3.3.3 Electronic Mail between AFS and VM/AIM Users
3.4.3 Data Volume
FIGURE 4.1-1
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
,.- ? ?
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000500100005-1
Page iu
APPENDIX A
CABLE FILE FORMAT
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
mon-Orin_9n7A
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CI"AlnElf'9.1:61355R000300100005-1 ?
rage II
CABLE FILE FORMAT
{start MPS header}
MSGNO nnnnn/mmmmm
{end MPS header}
(start CDS dissemination envelope header)
{CDS line
1}
(CDS line
2)
(CDS line
3)
{CDS line
4}
(CDS line
5}
(CDS line
6)
(CDS line
7)
(CDS line
8)
(CDS line
9)
(CDS line
10)
(end CDS dissemination envelope header)
(cable text)
(start CDS dissemination envelope ender)
{CDS last line)
(end CDS dissemination envelope ender}
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
mtm_ann_In7A
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R00030010000511-8
rage .rz
CDS LINE FORMAT
Line Columns Description
11 2 2 character ID number or blank
3 "/" slash character
4 - 5 2 character ID number or blank
6 "/" slash character
7- 8 2 character ID number or blank
9 Blank
10 - 29 Character string (Field "A") or blanks
30 - 33 Blanks
34 - 46 Classification (Field "B") or blanks
47 - 56 Blanks
57 - 60 "FRP"
61 Blank
62 "1" or blank
63 comma
64 "2"
or blank
65 utm comma
66 "3" or blank
67 comma
68 "4" or blank
69 lin' comma
70 "5" or blank
71 comma
72 "6" or blank
73 11110 comma
74 "7" or blank
75 11,0 comma
76 "8" or blank
77 - 80 Blanks
2 1 - 80 Blanks
3 1 - 56 String of alphanumerics or blank characters
57 - 80 Message Handling Indicator (MHI) - Field "C"
Note: AFS will receive only
STATE
MILITARY
NON-AGENCY
1 - 80 Blanks
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
mpn_onn_9n/A tInTr/Annt0^1.2. ^TA ... n . n . CITCM1/0 Yflr's
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
rage ii
CDS LINE FORMAT
Line
Columns
Description
5
1
- 7
"ACTION:" (Field "D")
8
Blank
9
ACTION Office Unit Symbol (OUS) and AOCN
The action OUS and AOCN in column 9 and continues
for,a maximum of 19 characters
NOTE: for originating traffic this field is used for
CONFIRMATION OUS
23
"INFO:" begins in column 23 or one blank character
after the end of the action OUS field if the action
OUS field extends beyond column 21
29
OUS's (see definition) folloWed by (nnn/p or w)
e.g., (122/w). The OUS's can continue as necessary
up to 600 OUS's. The continuation lines for OUS's
always begin with a blank in column 1.
5- 1
1
Blank
thru
5 - 59
2
- 80
OUS's (If dissemination ends on this line, Field
will also appear).
6
1
- 80
"-" Dash character
7
1
- 80
Blanks
8
1
- 2
Calendar year, e.g., "80" or "TS" if message
classification is Top Secret.
3
Blank
4
- 10
7 character CDS number
11
Alpha suffix or blank
12
- 14
Blanks
15
- 17
Category class precedence trigraph
1St character - Message category (AYIJSMN)
Note: AFS will receive only
S= State
M = Military
N = Non-Agency
2nd character - Classification (TSCEU)
3rd character Precedence (YZOPR)
18
- 35
Blanks
36
- 39
"PAGE"
40
Blank
41
- 43
Page number composed of 3 numeric characters 001-999
44
- 56
Blanks
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
mpn_onn_9n/A OnwriAnnwinv AnTACCTOTOTI CVCMEWV TflM -t
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
Line
Columns
rage ve
CDS LINE FORMAT
Description
8
57
- 59
CDS number prefix "IN", "NC", or blank
60
Blank
61
- 67
7 character CDS number (same as columns 4-10) or
blank
68
Alpha suffix or blank
69
- 80
Blank
9
1
- 30
Blanks or character string
31
- 34
"TOR:"
35
Blank
36
- 41
Date Time Group
42
"Z"
43
Blank
44
- 46
3 character month abbreviation
47
Blank
48
- 49
2 character calendar year
50
- 56
Blanks
57
- 60
4 character cable address designator (ACAD)
[for State the ACAD is 6 characters]
[for DOI and ACP the RI is used here]
61
Blank
62
64
(66)
3, 4 or 5 digit message reference number (MAN)
starting in column 62
[for DOI and ACP the SSN is used here]
65
(67)
- 80
Blanks
10
1
- 80
"-" Dash character,
Last
1
- 14
"END OF MESSAGE" (if last page)
15
- 33
Blanks
34
- 45
Classification
46
- 80
Blanks
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
_
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1 ?
rage 1)
APPENDIX B
CABLE FORMATS
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
mon CiAn In/A
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1 8
Page 16
APPENDIX B.1
FORMAT LINE USAGE
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
mPn-QOO-907A
Declassified in Part - Sanitized Copy Approved
LINE DOI
1
2
3
4 1
4a
vnTefloymov rTACCTVTVI1 cycmymc Tonnno
for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
rage
ACP REMARKS
Point-to-point accountability line
Routing indicator line
1/
line STAT
DE routing indicator
2 Security protect line
Director line
5
Date time group line
6
From line
7
Action addressee line
8
Information addressee line
9
Exempt addressee line
11
3
Break-begin text line
12
Non-Sponsor text lines
13
Break-end text line
14
serial number line
STAT
15
End-of-message (NNNN) line
LEGEND:
- "x" means used and mandatory
- "-" means not used
- Numbers refer to numbered notes listed below that explain
the difference between the use of the particular line
between formats.
NOTES:
1. The constant ZNY is used on this required line, followed by the
prosign MM and the Transmission Control Code (TCC) Trigraph.
2. ZNR UUUUU is used for unclassified messages. Classified messages
consist of WY followed by one space and five 'E's (unclasefto), five
'C's (confidential), five 'S's (secret), or five 'T's (top secret).
In transmissions for foreign nationals the last two (2) characters
will be replaced by the second character of the addressee's Routing
Indicator. For messages with the Message Handling Indicator (MHI) of
SXSXSX, the classification is followed by a slash (/) and five 'B's.
(e.g., TTTTT/BBBBB). This is a required line.
3. The break-begin line consists of only ZEM. This line is required.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
mpri_onn rim
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R0003001 00005-1
rage its
APPENDIX B.2
BACKUS NAUR FORMAT
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
'Ann nnn nnit,
Declassified in Part - Sanitized Copy Approved forRelease 2013/08/07: CIA-RDP91-01355R000300100005-1 8
Page 19
B.2.1 Backus Naur Terms
The following section defines the terms and syntax used in the Backus Naur
form of notation in this paper. This syntax is used to describe the content of
the format lines on terminating/originating messages.
Symbol
Note:
Definition
"is defined as"
"open symbol" adjacent symbols denote concatenation
denotes alternation
replication factor
the underscore denotes required key words.
A recursive operation is denoted as:
::= l
can be the occurrence of one or more times
B.2.2 BNF PRIMITIVES

End of Line

A combination of Alpha
Numeric, and Special
characters
Carriage Return
A single blank
A slash (/)
::= 72 or fewer alphanumeric characters, except
when used to refer to one of the standard
message format lines. A line can extend over
multiple 72 character lines.
Line Feed
::= a sequence of
a sequence of
a sequence of
a sequence of
a sequence of
a sequence of
a sequence of
=

AlB!CID!EIFIG!HlI!JIKIL!M!NIO!PIOIR!
SITIUIV!W!X!Y!2!
*141$11!"1:10,1.1./!?!(!)1.-f.V.+!%!&I
112!3!4!5!617!8!9!0!
::= A!BICIMEIFIG!B!I!J!KIL!M!N!0!PIOIR!
S!TIUIV!W!XIM!1!2!3!415!6!7!8!910!
*!#!$!'!"!:10,!.!/!?!(!)!-!@!+12,1&!
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
Declassified in Part -Sanitized Copy Approved for Release 2013/08/07 : CIA-RDP91-01355R000300100005-1
Page 20
APPENDIX 8.3
DOI -100 FORMAT
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
Declassified in Part :-S-an-iied Copy Approved for Release 2013/08/07 : CIA-RDP91-01355R000300100005-1 B
Page 21
B.3.1 D0I-100 FORMAT LINES

::=ZNY

::=
::=CRCRLF two carriage returns and one line feed.
Line 4 is the ZNY security protect sequence. The constant "ZNY" is
followed by the special intelligence community prosign "MM" and the
transmission control code (TCC) trigraph. Line 4 is never composed of more
than one printer line in length.
8.3.6 Director Line
::=
::=ZKZKDE
::=1

::=CRCRLF two carriage returns and one line feed.
The Director line has the elements necessary to accomplish the switching of
message traffic at communication centers equipped with an automated message
distribution system. The Delivery Distribution Indicators (DDI) are identified
as a line 4 parenthetical remark beginning with the trigraph USE (e.g., USE ABC
DEF CHI). If no DDIs are specified, DSII or SOA will be inserted, the former if
MHI=SERVICE. Line 4a will not exceed one printer line.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07 : CIA-RDP91-01355R000500100005.11
rage L4
B.3.7 Date Time Group Line

::=UNCLAS !
UNCLAS E F T 0 !
CONFIDENTIAL!
SECRET!
TOPSECRET!
::=Optional and appear as specified in original message
4:
::=l
::=SECTION OF
::=Section number of a multi-section message
::=Total Number of Sections
::=FINAL SECTION OF
::=Total Number of Sections
::=CRCRLF
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
'Inn AAA AA?A ? ? -
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R0003-00100005-1 B
Page 28
3.3.14 Text Line Elements (cont'd)
Line 12 elements (a-c) combined will comprise one or more lines. No
component,will be split across printer lines with the exception of CODEWORDS;
however, the words themselves will not be split. Section information will be
included only when the message is longer than one section.
::=
::=CITE
::=ORIGINATOR'S CABLE ADDRESS DESIGNATOR (The originating
. station)

::=MESSAGE REFERENCE NUMBER (A four- to six-digit number
that provides both the accounting for messages and a
reference key.)
::=Space
::=CRCRLF
Line 12 elements (d-f) always start a new line and will not be over one
line in length.
tt.
4: ::=Message Text
::=CRCRLF or other specified by originator
::=hexadecimal end-of-text representation.
Line 12 elements (g-h) are the actual text of the message land the
end-of-text character. The ETX character will appear before the authentication
information. The text EOL functions will be as specified in the originating
message format.
B.3.I5 Station Identification Confirmation Line
::=
::=I
::=The prosign C followed by plain language corrections
::=Four numerics preceded by a pound sign
! ::=CRCRLF(8) two carriage returns and eight line feeds !
CRCRLF two carriage returns and one line feed.
The end-of-message validation line verifies that the SSN from line 3 and
the one on line 14 agree. Service messages use a single line feed.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07 : CIA-RDP91-01355R000300100005-1
UAA AAA-
nn,..
Declassified in Part - Sanitized Copy Approved forRelease 2013/08/07: CIA-RDP91-01355R000300100605-1 B
Page 29
B.3.16 End-of-Message Line

::=NNNN
Line 15 is the End-Of-Message sequence and is never more than one printer
line in length.
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
Ann
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R0003-06106605-13
rage iu .
APPENDIX 8.4
ACP FORMAT
Declassified in Part - Sanitized Copy Approved for Release 2013/08/07: CIA-RDP91-01355R000300100005-1
mpn_onn_9n7A
Declassified in Part - Sanitized CopyApproveirior Release 2013/08/07: CIA-RDP91-01355R000360100005-1 8
Page 31
B.4.1 ACP Format Lines
::=
::=
::=
::=
::=
::=
::=
::=
::=
::=
::=
::=
::=
::=