REQUEST FOR PROPOSAL FOR THE BASELINE IMAGERY ADP-T STUDY

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP83M00171R000600030001-8
• Release Decision: RIPPUB
• Original Classification: T
• Document Page Count: 36
• Document Creation Date: December 12, 2016
• Document Release Date: May 17, 2002
• Sequence Number: 1
• Publication Date: May 9, 1979
• Content Type: MF

Approved For 40 easlZ002TU8PT~CIA-RDP83M0017 00600030001-8
9 May 1979
MEMORANDUM FOR:
25X1 A Deputy to the DCI for Resource Management
25X1 A Chiet, Administrative Staff, RMS
FROM:
25X1A
SUBJECT:
Director, Information Resources Office
Request for Proposal for the Baseline
Imagery ADP-T Study
1. Request to undertake the contract-efforts described in the attached
Request for Proposal dated 30 April 1979. This request is for contractor
support to develop and specify the impact of mid-1980 imagery collection
systems upon the present ADP-T s stems. It is planned that this study will
be similar in nature to data flow study which is in progress. The
methodology used in the study will be employed in this study. The
costs of the contractor a s reflected in this Request for Proposal should
not exceed period of eight months.
25X1
2. The initial phase of this Imagery ADP-T Study will be performed
by the IRO Staff which should add a significant amount of data in time to
support the FY 1981 program and budget reviews. The study contract could
require the contractor to make trips to various commands to collect data.
Attachment: a/s
WARNING NOTICE
INTELLIGENCE SOURCES
AND METHODS INVOLVED
Approved For Release 2(TC6f 8&[C4 DP83M
1746,-79 25X1A
Copy 2, Series ^ 25
I 25X1A
 Approved For ease 200/2 I, (83M001700600030001-8
SUBJECT: Request for Proposal for the Baseline
Imagery ADP-T Study
25X1A
Depu o e or Resource Management
Deputy to the DCI for Resource Management Date
0 746-79 25X1 A
Approved For Releasel
25X1A
HANDLE- VIA
OMINT
CONTROL; SYSTEMS JOI LY
i&EG HEII-RDP83M00171 R000600030001-8
 TOP SE~;RET
;Approved For4ease 2002/08/21 CIA-RDP83M00174P00600030001-8
SUBJECT: Request for Proposal for the Baseline
Imagery ADP-T Study
Distribution:
Copy 1 - Addressee
2 - AS/Finance
3 - RMS Registry
4 - IRO Subject
5 - IRO Chrono
Copy 1 - D/IRO (Series
Copy 2 - DD/IRO (Serie
DCI/RMS/IROA (4 May 79)
25X1A
[1746-79 25X1A
HANDLE' VTW Omx,', 25X1 A
Approved For ReleaTdg0 ff IA-RDP83 TAbk0M0dON.Y
 TCP SECFUiT
Approved Foreease 2002/08/21 : CIA-RDP83M00174P00600030001-8
Imagery ADP-T Study
Request or Proposal (RFP)
30 April 1979
1. Introduction:
The Information Resources Office (IRO) of the staff of the Deputy to the
DCI for Resource Management (D/DCI/RM) is soliciting proposals to assist the
IRO in the investigation, analysis, and reporting of the data flow of
information associated with the collection, processing, production, dis-
semination, and exploitation of imagery information. The selected contractor
will work with and assist IRO in developing the baseline of information and
reporting of future ADP-T (automated data processing-telecommunications)
resources as a result of new and planned imagery systems which will be
operational in the mid-1980's. This data will encompass the overhead subset
of the PHOTINT activities of the U.S. Intelligence Community. It is planned
that this contract will be awarded on or about 1 July 1979, and will continue
to 1 March 1980. The level of effort required is expected to be two (2)
qualified individuals, with appropriate administrative support throughout the
duration of the contract.
2. Background and Rationale:
As a result of FY 1980 budget decisions, money has been approved for
the development of new or modified imagery satellites which will become
operational in 1984. These satellites will generate additional requirements
for ADP-T in the 1984 time frame which will require the enhancement and/or
expansion of present facilities. This study is required to:
a. Quantify the resource impact of these changes.
b. Assure that resource needs are identified and adequate
justification for resources exists.
c. Identify the long-range impact of the 1984 imagery mix.
A schematic diagram of the ADP-T systems employed by the present imagery
complex is found in Figure 1. Many of those systems are large and complex.
Several existing systems are in transitional stages of modifications. Figure 2
lists the present and planned collection systems, Tasking and Requirements and
Exploitation ADP Systems, and the Telecommunications Systems. It will be
the contractor's task initially to analyze the baseline information relating
to each of these systems and to develop and analyze the impact of each of
the collection systems upon each of these ADP-T systems.
25X
25)1
1746-79 25X1 A
achment to Copy
(Series
Approved For ReleaseT2OP2/ 0 Ell-RDP83M00171 R00~6~t~~~3~O~1 J> ~"T`'Y 25X1 A
 TOP SECRET
Approved For0ease 2002/08/21 : CIA-RDP83M00174P00600030001-8
In order to standardize the baseline collected data, a format has been
developed by IRO and is found in Appendix A of this RFP. Although the
concept of this format is standard, the contractor can request modifications
or additions to be made with prior approval of IRO.
3. Plan of Work:
The total study is organized as follows:
Phase I - Baseline configurations and current capabilities
- Collection system changes that impact the ADP-T baseline
- Review planning for FY 80-84; both technical changes
and cost impacts
- Target Completion Date--June 15, 1979
- Phase I to be completed by IRO Staff
Phase II - Analysis of cost and planning data to meet objectives
- Development of initial resource plan
- Target Completion Date--October 1, 1979
- Phase II to be completed by IRO and contractor personnel
Phase III - Complete details of imagery data flow
- Revision of imagery ADP-T resource plan
- Target Completion Datp--March 1, 1980
- Phase III to be completed by IRO and contractor personnel
4. Contractor Tasks:
The contractor will support this study by:
Collection of data for analysis and analysis of the data regarding
ADP-T systems used to support imagery as described in the phase
tasks below:
Phase II - The contractor will be required to meet with all
organizations listed in Figure 2 to collect data flow informa-
tion. The data flow information should include descriptions
of the contents of system inputs and outputs, frequency of the
data, interfaces to other systems and factors contributing to
changes in information flow. Costing information should be
derived to determine the impact of the new collection systems.
Data analysis will be performed to develop a baseline document
which will include the nodes and information processing data
flow represented by the organizations found in Figure 2. The
documentation resulting from this phase will represent the
total imagery data flow. The contents of this document will
cover the requirements, collections, collection processing,
intermediate and centralized processing, and specific pro-
duction phases of the data flow.
25X1A
r -~ OMINT
T r J E. T CONTROL SYSTEMS JOINTLY.
Approved For Release 2008/21 : CIA-RDP83M00171 R00060 1-8 25X1 A
1746-79
 Approved ForSease 200248! ''f'~i3P60017900600030001-8
Phase III - This phase will be directed. toward a comprehensive
description of the imagery data flow in the FY 80-84 time period
from the perspective of (1) data flow through all processes, from
collection through production to consumers; (2) capabilities and
shortcomings of all ADP-T involved in those processes; and (3)
interdependencies and interactions among multiple entities. Based
upon the results of this study and analysis thereof, the contractor
shall make suggestions for the revision of the imagery ADP-T
plan, as appropriate.
5. Reports:
Generate periodic reports as follows:
a. Monthly status reports - In addition to financial contract
status reports which are supplied to the contracting officer
monthly, the contractor will also supply a monthly report,
of a page or two in length, to IRO summarizing the previous
month's activity, meetings, etc., and planned activities and
contacts for the next month.
b. At the conclusion of Phase II, the contractor shall submit a
preliminary draft report of the results of this phase. Because
of the security classification of this material, the contractor
may submit an original document for reproduction, limited to
printing, by the sponsor. Oral presentation material of the
findings of this phase are also required at this time.
c. At the conclusion of Phase III, the contractor shall submit
a final report of the results of both Phases II and III. Oral
presentation material of the findings and recommendations of
this study are also required at this time. Document printing
procedures described above may be used.
6. Contractor Bid Requirements:
In response to this RFP, responsive contractors should submit a
written proposal which will be segmented and prioritized: (1) to address
a representative subset of the total overhead imagery activities; and (2)
to approach the study in a prioritized fashion so as to optimize available
contractor resources. Each of the above two phases where contractor
participation is required is separable. Both phases will be awarded to
a single contractor. Work on Phase III may not be continued bases upon the
availability of data collected and analyzed in Phase II. The contractor
should be prepared to submit two cost proposals, if they are different,
for his personnel working in his offices and at the CHB by phase.
0
1746-79 25X1A
TOP SECRET COMINT 25X1A
Approved For Release 2002/08/21 : CIA-RD o TLY
 ? Approved Fc eleaselAgUJJ l&la-RDP83M0010000600030001-8
7. RFP Schedule:
Issue of RFP - May 14, 1979
Receipt of Proposals - June 11, 1979
Contract Award - June 27, 1979
Start of Work - July 2, 1979
The above dates represent major RFP milestones. All questions relating
to this RFP should be submitted in writing. All answers to questions asked
will be distributed in writing to all prospective qualified contractors.
8.
Phase Schedules:
Completion of Phase II -
Completion of Phase III -
October 1, 1979
March 1, 1980
9.
Hardware Exclusion:
The successful contractor awarded this contract will be prohibited from
submitting bids for hardware for imagery systems studied under this contract
for a period of five (5) years from the award of this contract.
10. Software Exclusion:
The successful contractor awarded this contract will be prohibited from
submitting a proposal as a prime contractor, or as a team member of another
contracting team, for software development for imagery systems studied under
this contract for a period of five (5) years from the award of this contract.
The successful contractor may, however, contract to a prime contractor for.
software development tasks after a prime contractor has been awarded an
imagery software development contract.
746-79 25X1A
1-1ANn- F- vne 25X1 A
COMINT
CONTROL SYSTEMS JOINTLY
Approved For Relea TOOIIA~ IA-RDP83M00171R000600030001-8
 Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
Next 3 Page(s) In Document Exempt
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 -Approved Foo lease 2002/08/21 CIA-RDP83M001_0 000600030001-8
Imagery ADP-T Study
Data Call
Information Resources Office
Resource Management Staff
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
25X1A
 ? ?Approved Folease 2002/08/21 : CIA-RDP83M001 000600030001-8
L.ontents
Page
1.0 Automatic Data Processing and Data Base Resources . . . 1
1.1 Reporting Definitions . . . . . . . . . . . . . . . . . 1
1.1.1 Hardware Systems . . . . . . . . . . . . . . . . .. . . . 1
1.1.2 Software Systems . . . . . . . . . . . . . . . . . . . 3
1.1.3 Organization of Reporting Data . . . . . . . . . . . . . 4
1.2.0 Reporting Format . . . . . . . . . . . . . . . . . . . . 5
1.2.1 Cross Reference . . . . . . . . . . . . . . . . . . ? . 7
1.2.2 Administration. . . . . . . . . . . . . . . . . . . . 9
1.2.3 Operational Information . . ... . . . . . . . . . . 9
1.2.4 Data Flow . . . . . . . . . . . . . . . . . . . . . . . 9
1.2.5 Hardware Configuration . . . . . . . . . . . . . . . . . 10
1.2.6 Support Software . . . . . . . . . . . . . . . . . . . . 10
1.2.7 Application Software . . . . . . . . . . . . . . . . . . 12
1.2.8 [Product Data Bases] 14
[ ]-same description . . . . . . . .
1.2.9 [Support Data Bases] 14
1.2.10 Utilization . . . . . . . . . . . . . . . . . . . . . 14
2.0. Telecommunications Resources . . . . . . . . . . . . . . 14
2.1 Reporting Definitions . . . . . . . . . . . . . . . . . 14
2.2 Reporting Format . . . . . . . . . . . . . . . . . . . . 14
3.0 Glossary . . . . . . . . . . . . . . . . . . . . . . . . 15
Appendix A: Example of Format . . . . . . . . . . . . . . 17
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 -Approved Fo*lease 2002/08/21 : CIA-RDP83M001p 000600030001-8
Imagery ADP-T Study - Resource Summary
The information required for the imagery study includes a resource
baseline of installed and operating ADP-T systems. This Data Call re-
presents the requests for the collection of this information. The Data
Call is divided into the following sections:
1.0 Automatic Data Processing and Data Base Resources -
definitions and format requirements for reporting
automatic data processing and data base resources.
2.0 Telecommunications Resources - definitions and format
requirements for reporting telecommunications resources.
3.0 Glossary - glossary of acronyms used in an agency's sub-
4.0 Example of Format - an example of the format of the de-
sired information.
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 ?Approved Fo*lease 2002/08/21 : CIA-RDP83M001p 000600030001-8
1.0 Automatic Data Processing and Data Base Resources
1.1 Reporting Definitions-The information required for this phase
of the imagery ADP study would include ADP resources which support
the flow of data. The information desired is primarily organized
by the major intelligence community agencies. The ADP systems would
be documented by the agency that "owns" the system (i.e. the agency
for which the system was purchased, designed and developed: the
agency that is the primary user of the system). The ADP and Data
Base resources should be addressed within a specific organization
and its component suborganizations.
1.1.1 Hardware Systems-An ADP system can range in size from a single
small CPU with a minimum of peripherals to multiple large-scale
CPUs joined for a specific purpose and connected to a wide range
of peripheral devices. Each ADP system within the intelligence com-
munity is described as one of the following four basic types:
1. General Purpose Information System
2. Communications Support Information System
3. Administrative Support Information System
4. Dedicated Support Information System
The General Purpose Information System are those technical and
application support systems within an agency's ADP organization and
on which any element of the organization may compete for resources.
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 -Approved Fo*lease 2002/08/21 : CIA-RDP83M001p000600030001-8
The Communications Support Information Systems are those systems
dedicated to information receipt, forwarding and routing. They provide
terminals for data flow into and out of a facility. Those systems
which provide data routing or switching within a facility are also
included in this category.
The Administrative Support Information Systems category is provid-
ed,for those general purpose systems which support the'administrative
rather than technical applications. An example might be a system de-
dicated to payroll, personnel, or inventory management.
The Dedicated Support Information Systems category will include
any ADP systems which are wholly owned by a specific organization with-.
in an agency. The organization cited is normally responsible for devel-
opment, support and resource allocation of these systems, although pro-
curement is often performed by another organization. These systems
range in magnitude from large scale computing systems to small, very
specialized analysis support systems.
There is another category of ADP system which is included in this
summary of systems within the context of the above categories. This
system is sometimes known as a "project" and is a name given to those
portions of existing (and perhaps new) ADP systems which become com-
ponents of a project to support a specific function. These projects
will be documented as separate systems with references to the component
systems as appropriate. The component systems description will also
contain a reference to any "projects" in which the system participates.
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 ?Approved FoSlease 2002/08/21 : CIA-RDP83M001 000600030001-8
The description of a specific APP resource will include two
diagrams; one to show the flow of data through each resource and the
other to present a functional hardware configuration diagram for each
resource. These diagrams represent the flow of data for all nodes
supported by a resource. Interfacing nodes and ADP resources will
be indicated. (In a later phase of this Imagery ADP-T Study, periodi-
city of information and volume of data will be requested.) The ADP
resource will be presented as a transfer node and the specifics
of information handling by the resource will be described under
the appropriate support and application software package descriptions.
The appropriate application software packages and data bases acronyms
will be indicated on the ADP resource diagram.
Each hardware configuration diagram should identify the basic CPU
type and hookup. The number and type of peripherals should be identi-
fied where possible. If peripherals are located remotely from the
agency owning the ADP resource, this information should be presented.
1.1.2 Software Systems-Data bases are described within the context
of the ADP system on which they are generated or maintained. Three
types of data bases are included in this report:
1. Product Data Bases - Those functional sets of data which
are controlled and distributed throughout the intelligence
community in either computer readable form or hard copy.
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 ?Approved Fo*lease 2002/08/21 : CIA-RDP83M0017 000600030001-8
2. Support Data Bases - Those functional sets of data which
support the activities of a given node or agency, requiring
inputs from other agencies or nodes, and generally are not
under community-wide control.
3. Process-Unique Data Bases - Those that are used within an
ADP process. These are characterized by inputs and outputs
all internal to the ADP system of which they are part. Any
large software system has multiple data bases ("files") of
this type. In this report, elements in this category will
be discussed in the software description, but these data
bases will not be singled out as either "product" or
"support", and detailed data base descriptions (other than
necessary to describe the process) should not be included.
Product data bases will be noted within the context of the generating
system and within the context of any using system. Where appropriate,
information will be provided to indicate how the product data base
is tailored to support individual users. Data sources will be pro-
vided for all data bases described. Where multiple data bases are
maintained as a part of a data system, each functional part will be
described within the context of products or support data base and the
data system will be identified.
1.1.3 Organization of Reporting Data-The ADP system data information
desired in each subsection should be augmented by textual information
and organized as follows:
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 ?Approved For lease 2002/08/21 : CIA-RDP83M001 000600030001-8
1. Cross Reference to phase of intelligence flow, user
organizations, etc.
2. Administrative Information on financial data, software
languages and data storage capability.
3. Operational Information for the ADP system.
4. Data Flow through the ADP system.
5. Hardware Configuration.
6. Support Software information.
7. Applications Software information.
8. Product Data Base information.
9. Support Data Base information.
10. Utilization data on the ADP resource.
1.2.0 Reporting Format-The following illustrates the desired format
of the reporting data from each agency. An example of an agency's
completed format is found in Appendix A.
1.2.1 Cross Reference-This section for an ADP system is somewhat
standardized. The Cross Reference for any ADP system will include:
a. Phase of Flow:
b. Development Organization:
c. User Organizations:
d. Application Software:
e. Communication System(s):
f. Data Networks(s):
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 .Approved For* lease 2002/08/21 : CIA-RDP83M0017WO0600030001-8
g. Interfaced Computer(s)
h. Point of Contact:
ADP systems which are a component of larger projects will have an field
for "components of:" and the description of the project will replace
"Interfaced Computers" with "Component Systems." (See example format
in Appendix A.)
o The Phase of Flow cross reference is to identify which one
or more of the phases of information handling (i.e., collec-
tion, processing, etc.) is supported by this resource. The
reporter should try to be as specific as possible.
o Development Organization should be the single organization
which has total (or primary) responsibility for making the,
system work. I .
o User Organization should include all users.
Application Software should include the acronym for all the
software packages that are developed for this ADP Resource.
o Communications System should include the acronym for those
communications which are directly connected to the computer
or connected via a computer to computer line from that computer
which is the local terminus of a communications system.
o Data Networks should include the acronym for all data networks
accessible by users of this ADP resource.
o Interfaced Computers should contain the acronym for all ADP
resources which communicate directly with this resource.
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 .Approved Forlease 2002/08/21 : CIA-RDP83M0017SP00600030001-8
o Point of Contact should identify the organizational title, and
office symbol and telephone number for obtaining additional
information on this ADP resource.
o Component of should contain the acronym for all ADP projects
which utilize a portion of this ADP resource.
o Component Systems. should contain the acronyms for all ADP
systems, a portion which ADP comprise this project. This
information. will be used by the reader to obtain detailed
information on the component systems.
NOTE: Either the Component of or Component Systems line will
be included, as appropriate.
1.2.2 Administrative-The Administr-ative Information Section for
an ADP system is also rather standardized. The Administrative Information
Section will include:
a. Financial Data - (See Below)
b. IOC - Date of Initial Operational Capability
c. Upgrade/Replace - (See Below)
d. Software Size - (See Below)
e. Data Base Size: (See Below)
f. Software Languages: (See Below)
o Financial Data should include the initial ADP system and instal-
lation costs, present yearly hardware maintanance cost, and
present yearly software maintenance cost. Future upgrade/replace
costs found in the following subsection should be indicated here.
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 -Approved For lease 2002/08/21 : CIA-RDP83M0017000600030001-8
o Upgrade/Replace should provide data for all upgrades between
IOC and the present. It should also contain a brief paragraph
on the purpose and effect of each upgrade. For future planned
improvements, the proposed date for operational capability
of the change should be provided to explain the purpose
and projected effect of the upgrade. When an ADP system
is phased out of service the date of phase outkshould be
documented and a reference should be provided'o the system,
if any, which is replacing the information, handling support
functions of the system being phased out.
o Software Size data should be clearly documented in appropriate
sizing units, whether specified in instructions (executable +
data + non executable + comments or any combination of the above),
bytes, or words in a program library. These sjzes should be re-
latable to the various support and application software packages
described in detail in later subsection of this Resource des-
cription.
Data Base Size information should be in the bytes of storage.
Where possible it should be relatable to the product and sup-
port data bases with an "OTHER" category for the local and work-
ing data bases.
o Software Languages information should list those languages in
which the various support and application software instruction
sets were generated. Where possible the language should be as-
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 -Approved Forleease 2002/08/21 : CIA-RDP83M0017WO0600030001-8
sociated with the software package(s). Where there are many
variations of a language, such as FORTRAN, the specific variant
shall be provided.
1.2.3 Operational Information-The Operational Information shall
include an overview in a free form narrative, of the purpose
of the resource and the operational modes (batch, real-time, etc.)
which provide the support.
1.2.4 Data Flow-The Data Flow description through the ADP system
should be keyed to the data flow diagram provided. This data flow
text. should not be so complete as to describe the functions performed
by the application software. At this point the appropriate software
packages should be mentioned but the detail should be left for later
paragraphs.
1.2.5 Hardware Configuration-The Hardware Configuration description
should include functional equipment diagrams (not detailed installation
wiring diagrams) for the operational ADP resource and any developmental
or test configurations which may support it. For ADP projects that
are supported by portions of one or more ADP systems, a component
diagram should be included, with specific hardware configurations
of the individual resources being provided in the separate, individual
system descriptions.
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 -Approved Foreease 2002/08/21 : CIA-RDP83MOO17 006OOO3OOO1-8
1.2.6 Support Software-The Support Software shall contain, at a minimum,
a list of operating systems, data base managaement system(s), terminal
support subsystem(s) and other utility software packages available to
users of this ADP resource. Where the information is available, a
brief paragraph might be included for each support software package
to identify whether it was a standard or special package, the developer
of the package, and a brief statement on the capabilities of the package.
1.2.7 Applications Software-The Applications Software subsection
shall contain a different description for each executable, software
package that supports information handling on this ADP resource.
This is to be a functional description of how these programs (which
for the most part should remain nameless) are used to handle the
incoming data and transform it to the resulting output product.
This is not to be a description of software programs, routines,
and subroutines which contain sets of instructions and generally
operate on a small portion of the incoming data.
Each Application Software package description shall be a separate
numbered paragraph and shall contain: a) Cross Reference and b)
Functional Description. The Cross Reference is standard'and shall in-
clude the following:
(a) Phase of Flow:
(b) Responsible Organization:
(c) User Organization:
(d) ADP System:
Approved For Release 2002/08/21 : CIA-RDP83MOO171R000600036001-8
 -Approved Fo*ease 2002/08/21 : CIA-RDP83M0017700600030001-8
(e) Product Data Base(s):
(f) Support Data Base(s):
(g) Point.of Contact:
o The Phase of Flow should identify which of the information
handling phases is supported by this applications software
package.
o The Responsible Organization should reference the organiza-
tion that has primary responsibility for implementing and
maintaining the application software.
o The User Organizations should include a list of all users.
o The ADP System line should contain the acronym for the
resource on which this software is hosted.
o The Product Data Base line should contain the acronym(s) of any
data bases built as a result of the execution of this software
from which copies or products (hard copy) are generated for
distribution throughout-the intelligence community.
o The Support Data Base line should contain the acronym(s)
of any data bases built from any data received from sources
external to the agency or facility which contain the ADP
Resources which support the application software.
o The Point of Contact should identify the organizational title,
office symbol and telephone number for obtaining additional
information on this application software package.
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 ?Approved Forolease 2002/08/21 : CIA-RDP83M0017SP00600030001-8
1.2.8 Product Data Bases-See 1.2.9, Support Data Bases.
1.2.9 Support Data Bases-The content of the description for both
the Product and Support data bases is the same. They are separated
to distinguish among their respective support roles and to group
and highlight the community's product data bases. Each product or
support data base description shall be a separate numbered subsection
of subsection 8 or 9, as appropriate. Each descriptions will contain
the following paragraphs:
(a) Cross Reference
(b) Functional Description
(c) Physical Description
(d) Security
( 'E
(e) Data Sources
The Cross Reference Section is standardized and shall contain:
(a) Phase of Flow:
(b) Responsible Organization:
(c) User Organizations:
(d) ADP System:
(e) Application Software:
(f) Point of Contact:
o The Phase of Flow should identify at which phase of the
information handling process this data base is generated.
o The Responsible Organization for a product data base is that
organization which maintains configuration and content con-
trol over the data base. The responsible organization for a
12
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 Approved For Rele
i
71 R000600030001-8
support data base is that organization responsible for in-
suring incoming data is included in the data base in a timely
fashion.
o The ADP System shall be the acronym of the system which hosts
the data base as it is described here.
o Application Software shall contain the list of acronyms of the
application software packages hosted on this ADP system that
generate or use this data base.
o Point of Contact should identify the organizational title and
office symbol, and telephone number to be contacted for obtaining
additional information on this data base.
The Functional Description should describe the contents of the data
base in a manner that would be meaningful to personnel who are not ADP
oriented. A functional description of record contents should be included
where possible (this should not be a layout of data fields within the
record).
The Physical Description should contain information on logical and
physical record sizes, the number of logical records in the data base
and the volume of storage media allocated to the data base. Where pos-
sible information concerning the storage media (e.g., disk or tape) should
be included.
Security should include the level(s) of classification of the data
base. Where more than one level is maintained all should be identified.
Data Sources should identify those nodes or agencies, outside the
agency controlling the data base that provide the information which be-
come the data contents.
Approved For Release 200
 Approved Foolease 2002/08/21 : CIA-RDP83M0017 000600030001-8
1.2.10 Utilization-The Utilization data should identify what percent
of the ADP resource is used for a specific intelligence data flow.
If the information is readily available, the percent of utilization
by the various user organizations is meaningful. Shift utilization
should also be provided for each ADP resources.
2.0 Telecommunications Resources
2.1 Reporting Definitions-The major telecommunications systems sup-
porting the flow of intelligence and intelligence information among
the various information handling phases. shall be described here.
Both existing and planned communications systems will be included
in the Baseline. There are basically two types of communications
systems to be documented herein. The large general subscriber systems,
such as AUTODIN; and the special-purpose systems which Support a
particular element or information processing phase. These special systems
generally use the facilities and resources of the general subscriber
systems. They may use special protocols and dedicated circuits
within the general systems.
2.2 Reporting Format-For each communications system included, the
ing is the minimal information needed:
(a) System Owner
(b) System User(s)
(c) Transmission Rate(s)
(d) Terminal Devices
(e) Bandwidth/allowable data rate
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 -Approved Fololease 2002/08/21 : CIA-RDP83M0017 D00600030001-8
(f) Transmission Media and Techniques
(g) System Responsiveness
Additional information to be included, if available, might be:
Current Operational Status
Planned Improvement/Replacement
Network Diagram
Utilization
Cost at IOC
Cost for each Improvement/Replacement
This is not to be a detailed description of any telecommunications
System, but rather an overview of the capabilities and capacity of
the system.
3.0 GLOSSARY
This glossary is intended to include all acronyms of data flow nodes
and ADP and communication systems used in the reported data. It should
also include all known aliases for any of these acronyms. In addition
the Glossary should contain the acronyms for all organizations identified
and any acronyms generally used to define system or unit equipment
characteristics.
For a baseline of this eventual size, the Glossary is a significant
section, thus a decision has been made not to include the acronyms of
data sets files, and programs internal to a particular ADP process.
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 Approved Fooolease 2002/08/21 : CIA-RDP83M0010 000600030001-8
These are files that are used to communicate between various segments
of computer software packages and are transparent to any source or con-
sumer beyond the data flow node which is supported by that particular
.software package. While it may be necessary to use these acronyms
to describe adequately the flow of data through an ADP system or
applications software package, the use should be localized so no
i
major inconvenience will be perpetrated by not includiig these
acronyms in this Glossary.
Where an acronym is expanded in the Glossary the association with
a data flow node, Intelligence Community organization or ADP resource
should be provided as appropriate.
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 -Approved FoSlease 2002/08/21 : CIA-RDP83M001 000600030001-8
APPENDIX A
SECTION 4 - EXAMPLE OF FORMAT
N.N.N RESOURCE Name (Acronym)
N.N.N.1 Cross. Reference
a. Phase of Flow:
b. Development Organization:
c. User Organization:
d. Application Software:
e. Communications Systems:
f. Data Networks:
Interfaced Computers:] Optional according to type of
[ or g. Component of:
[ or g. Component Systems:
h. Point of Contact:
-resource being described.
N.N.N.2 Administrative Information
a. Financial Data:
b. IOC:
c. Upgrade/Replace:
d. Software Size:
e. Data Base Size:
f. Software Languages
N.N.N.3 RESOURCE Operations
N.N.N.4 RESOURCE Data Flow
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 ?Approved Fololease 2002/08/21 : CIA-RDP83M00170000600030001-8
N.N.N.5 RESOURCE Hardware Confi uration
N.N.N.6 RESOURCE Support Software
N.NMN.7 RESOURCE Application Software
N.N.N.7.n Specific Application Software Packages Name (Acronym)
a. Cross Reference
Phase of Flow:
Responsible Organization:
User Organizations:
ADP System:
Produuct Data Bases
Support Data Bases:
Point of Contact:
b. Functional Description
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 ? ?Approved For lease 2002/08/21 :CIA-RDP83M00100600030001-8
N.N.N.8 RESOURCE Product Data Bases
N.N.N.8.n Specific Product Data Base Name (Acronym)
a. Cross Reference
Phase of Flow:
Responsible Organization:
User Organizations:
ADP System:
Applicatiion Software:
Point of Contact:
b. Functional Description
c. Physical Description
d. Security
e. Data Sources
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 Approved Fooolease 2002/08/21 : CIA-RDP83M001000600030001-8
N.N.N.9 RESOURCE Support Data Bases
N.N.N.9.n Specific Support Data Base Name (Acronym)
a. Cross Reference
Phase of Flow:
Responsible Organization:
User Organizations:
ADP System:
Application Software:
Point of Contact:
b. Functional Description:
c. Physical Description:
d. Security:
e. Data Sources:
N.N.N.IO Resource Utilization
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 Show Number
and t ocalron
of Remote
Show Number
and Lora oo
if Remote
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
Terminal
Type A
Terminal
Type 8
Main Process." C0&. a,.on
- - - - - - - - - - - - - - t
CPU A
(pU e
Communeca!,on Inrerlace Suoooet Remote Job Support
t' t
CPU 0 CPU E
Comm System A
t
I I
I I I
. 1 I I
1 1
Generic Hardware Configuration Diagram
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
Shorn Number
of Diet
M-bytes of
Storage
 Input
Oata Flow
Ned" A
Input Odsae
Oar. Flow
Nods
Generic
Node
Soec,fc
Node 0
Generic
Node
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
List of
ADDlication
Software
Package,
Number of Records
Periodicity Magnetic CUiRecord/Taoe
M
Update Periodicity
and Vo:ume in Byte,
- Malcr Product
And Support Data Bases
TL Svst?m i
File Name A
No. Lo7?caf Records
No. Bytes of S:Dray
OM-
Oats Bases
Hardcopy
or Msq
Number c1t/Tap!
Generic ADP Resource Data Flow Diagram
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
7% XX TNT
50% VY TNT
25% ZZ INT
18% Other
Destination
Node
In terlxinq
Computer
`0
 Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
Component 6
Generic Component Configuration Diagram
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 `Approved Folwease 2002/08/21 : CIA-RDP83M00174V00600030001-8
Q
-aXS-
MAGNETIC V.rC UtUIT OR OrrLIIlE STORAGE
CARD/CARD RCADCR
CO?UICCTlIIG COt!'UTCR (WITI(IU FACILITY)
OR CPU OR SWIIC11
OIILINE STOflRGC OR COF',PUTCR READASLE
FOPJUIT
NNID CARRY OR F'J!IUAL IItTCRVENTIOuI
SOFT COPY OR DISPLAY CONSOLE
DATA ENTRY OR TTY OR KEYBOARD
DATA FLOW
FEEDBACK
PATll CONNECTOR
11
LEGEND FOR DATA FLOWS AND HARDWARE
CONFIGURATION CHARTS
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
 25X1 Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8
Approved For Release 2002/08/21 : CIA-RDP83M00171R000600030001-8