FY 80-84 COMMUNICATIONS REQUIREMENTS

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP82T00285R000100160030-5
• Release Decision: RIPPUB
• Original Classification: K
• Document Page Count: 4
• Document Creation Date: December 12, 2016
• Document Release Date: February 20, 2002
• Sequence Number: 30
• Publication Date: December 22, 1977
• Content Type: MF

^n ed For Relea002/06/14: CIA-RDP82T00285R000 60 30-
.22 December 1977
-
o~A
MEMORANDUM FOR: Director, CIA Operations Center
Director of Centeral Reference
Director of Economic Research
Director of Geographic and Cartographic Research
,-b- Director of Imagery Analysisv
Director of Regional & Political Analysis
Director of Scientific Intelligence
Director of Strategic Research
Director of Weapons Intelligence
Chief, Current Reporting Group
Chief, Publications & Presentations Group
Special Assistant-NIO Support
FROM . : NFAC Plans and Programs Staff =
SUBJECT : FY 80-84 Communications Requirements
y
1. As part of the FY 80 planning cycle, the Office of Communica-
tions has begun pulling together Agency-wide communications requirements
for FY 80 through 84. In order to prepare a consolidated NFAC re-
quirements package, submissions from NFAC components should be forwarded
to the Plans and Programs Staff by 10 January 1978.
2. The early date for submission of FY 80 requirements has been
mandated by the Office of the Comptroller to ensure that all Directorate
and Center requirements are addressed in OC programs in the most cost
effective manner. It is the intent of OC to combine similar require-
ments from all parts of the Agency where possible, in order to lessen
or negate the impact of individual programs which are riot approved.
From NFAC's point of view, it is important that FY 80 requirements
be identified now so that they can be included in the FY 80 OC budget.
NFAC funds will have to support any requirements that arise after the
OC budget is put together.
Approved For Release 2002/06/14: CIA-RDP82T00285R000100160030-5
 Approved For Relea2002/06/14: CIA-RDP82T00285R0000160030-5
STATINTL
3. The Office of Communications is prepared to offer assistance TINTL
in preparing these early submissions and has designated
the OC Staff
Operations Division Plans Branch (OC-O/SOD/PB -1 1
as the focal point for new requirements. Furthermore- at s request
the undersigned has been identified NFAC Plans ,TP iINTL
Programs Staff to act as coordinator of communications
requirements.
4. Attached for your assistance are two handouts from OC that may
assist you in putting together an adequate submission. STATINTL
Distribution:
one ea. addressee
1 NFAC Plans & Programs Staff file
_ 1 - NFAC Plans & Programs Chrono
Approved For Release 2002/06/14: CIA-RDP82T00285R000100160030-5
 Approved For Release002/06/14: CIA-RDP82T00285R000IW160030-5
ILLEGIB
a. Expansion of service at existing locations,
with location identification, including calling areas/
components to which calls are to be made.
b. Provision of service to new locations, with
location identification, including calling areas/
components to which calls are to be made.
c. Security level required,.
SPECIFIC SERVICES REQUIREMENTS:
1. SECURE VOICE
2. DATA SERVICE
a. The number and locations of termination points
at which information is to be received or transmitted.
b. Identification of the user's equipment, if any,
installed or specified at the termination point.
c. Identification of major system to be accessed.
d. Projected volume of use.
e. Type of data to be transferred, e.g., graphics,
semi-narrative, etc.
Approved For Release 2002/06/14: CIA-RDP82T00285R000100160030-5
 Approved For Releae,z002/06/14: CIA-RDP82T00285R0001'G0160030-5
COMMUNICATIONS REQUIREMENTS DEFINITION
A communications service is identified as an end-to-end
capability which provides for the transfer of information
electronically between a sender and a receiver. Requirements
for such services should be specified in terms of a problem
to be solved, without specifying the solution. In this
regard, there are certain basic elements required in the
requirement statement:
1) A brief description of the mission need to be met.
2) Identification of the locations between which
the user expects to transfer the information.
3) Traffic statistics.
4) Specification of the level of service required,
It should be noted that the user has the sole responsibility
for the content of the information to be passed, while the
supplier assumes the responsibility for the planning,
engineering, operation, maintenance and for the acceptance,
transmission and delivery of the information.
Approved For Release 2002/06/14: CIA-RDP82T00285R000100160030-5