USIB COMMITTEE STRUCTURE AND COMUNITY REORGANIZATION

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP86M00612R000200020087-6
• Release Decision: RIPPUB
• Original Classification: S
• Document Page Count: 8
• Document Creation Date: December 15, 2016
• Document Release Date: May 18, 2004
• Sequence Number: 87
• Publication Date: January 6, 1972
• Content Type: MF

Approved For Release 2004/06/15 5686M00612R04VU 00020087-6
25X1'
MEMORANDUM T'O.R: Chairman,
Q .N
SUS1JECTt
Reorgan iaation
1. The Prooldent'a memorandum of 5 November, directing
certain organizational and management changes in the intelligence com-
munity, placed particular ornphanie on the Director of Central Intelligence's
res
on
ibilit
p
s
y in the whole field of renourcos. This includes the drawing
up of a consolidated intelligence program budget, which carries with it
the need to evaluate intelligence programs, to identify important resource
issues and to make the adjuotmente and trade-offs necessary to come up
with as cost-effective a combination as possible. There are a number
of avenue a which will have to be purLiued to got the information we will
,need. But it is clear that the USII3 committee structure represents a
body of information and expertise in these areas on which I'll need to
,draw on a continuing basis. Some of 'you will, of course, be more involved
then othe
b
t I
rs,
u
wanted to alert you all to this need and to got you
txfnU
in
t i
g ou
t.
Chairman,
Chairman,
Chairman,
Chairman,
Chairman,
Chairman,
COMIREX
CCPC
EIC
GP~IAIC
JAEIC
SIC. .
SIGINT Committee
USlB Committee Structure and Community
g
n
t ff
li r e a your lull cooperation, in what to going to' be a
taxtn
i
2. To got this process under way
7I3ronBon T
d
,
weea
y will be contacts
Ing fciit individually in the immediate future and I would appreciate your
ivin him a
d hi
g rerpondt+
Mlity for all of
cc: DDI
DDP
DDS&T
'Richard Helyds
Chairman -
?droved For Release 2004/06/15: CIA-RDP86M00612R000200D'20087-6_
redseeoa 1 - DCI 1 - NIPE/ subject
1 ? USIB Sect 1 .. ER [[ ccCI~ ~hjEC Ecctudcd tr.a o~rcmat-c,
JL ,1 NIPE/chrono
Oo.n rt..-? ?,~
NIPE:BTweedy:dm(4 Jan 72) '+'
 SEG SET
Approved For ReI 2004/06/15: CIA-RDP86M00612RO 0020087-6
SECTION IV
Data Requirements of the DCI/IC/Comptroller
The DCI/IC/Comptroller has certain formal commitments/tasks
which require resource and performance data. They are:
Preparation of issue papers.
Preparation of the National Intelligence
Program Memorandum.
-- Preparation of the DCI's presentation to
Congress in defense of the Community budgets.
-- Support to the IRAC.
Much of the data required will be obtained through partici-
pation in the program and budget review and decision processes of
departments and agencies. At various times during the cycle (e.g.,
Cc.G
for the draft NIPM, final NIPM, and for the Congressional presentation),
and on other unscheduled occasions, the DCI/IC/Comptroller will
require the formal submission of resource and performance data. The
requirements discussed in this Section apply to these formal sub-
missions. The discussion also assumes full participation by the
DCI/IC/Comptroller's Staff in the program and budget reviews
discussed in Section III, above.
Note: For the most part, Defense is used as the example of
data and other system requirements. Where this is done, it is
assumed that the procedures in other agencies are consistent with
31
Approved For Release 2004/06/15a~~Z; 86M00612R000200020087-6
 MEET
Approved For ReIe~ 2004/06/15: CIA-RDP86M00612R0G00020087-6
those of the more extensive Defense system and can thereby be
accommodated within the requirements and procedures discussed
here.
A. General Characteristics of DCI IC Comptroller Data
-'Tcquirenients"
1. The data must be official.* The data provided the DCI/IC/
Comptroller should be the same as that used for internal management
purposes and supported by the accounts of the respective agency.
2. The data should provide adequate crosswalks between the
programming and budgeting of resources, and the actual use that
is made of the resources (the financial accounts structure).
3. Fund and manpower data must be available on request at
budget unit level even though it may not have to be submitted on
a routine basis.
4. Data must be available for past years as well as for future
years to permit analysis and presentation of trend information.
D. Specific Data Required
5. The primary requirement of the DCI/IC/Comptroller is for a
system, or access to a data system, that will support cross-
organization and cross-program compilation and review of resource
data (manpower and funds). It is important to note in this context
that this paper addresses data requirements and general system
* Official data is defined as data that is used by the department/
agency in its own programming, budgeting, and accounts system.
Approved For Release 2004/06/15D 86M00612R000200020087-6
19f. e I
 SECRET
Aft Approved For Rel6wk 2004/06/15: CIA-RDP86M00612R00020087-6
requirements; it does not choose a specific system, such as CIRIS,
to meet these needs because the DCI/IC/Comptroller requirements
represent only part of the data requirements of the DCI/IC Staff.
The requirement is for the ability to arrange and display official
resource data of intelligence agencies and activities according to
the following:
a. By organization (department; agency; service;
directorate; bureau). _
b. By Program (CCP; GRIP; Special Air Force; DSAP;
CLAP; INRP; etc.).
c. By Program Element (within CCP; GDIP; CIAP; etc.).
d. By Function (Category/Mission; Subcategory/Function;
Element/Sensor).
e. By Appropriation (Mil Pers; O&M; Procurement;
RDT&E; Military Construction).
6. It will be necessary to be able to display the following
types of resource data in all of the above arrays:
a. Funds (TOA)
b. Manpower
(1) Military
Officer Personnel
Enlisted Personnel
(2) Civilian
U.S. Direct Hire (ceiling/staff positions)
Ceiling/Staff positions
Contract positions
33
Approved For Release 2004/06/ ;i-DP86M00612R000200020087-6
 SECRET
Approved For Rose 2004/06/15 : CIA-RDP86M00612R0200020087-6
Foreign Direct 111 re
Contract
Foreign Indirect Hire
Locals/Indigenous
Note: The foregoing is not additive to the CIRIS data call but
represents only that part of the call needed by the DCI/IC/Comptroller.
The needs of other DCI/IC groups are reflected in the overall CIRIS
call.
34
Approved For Release 2004/06/15 : tt f ~ tt I P,86M00612R000200020087-6
tii'L `.AJ?Fr
 SECRET
Approved For Re a 2004/06/15: CIA-RDP86M00612R 00020087-6
C. Data Availability
7. The minimal requirement of the DCI/IC/Comptroller is for.
an official update of program decisions and resource data at least
twice annually!
a. In August,
(1) For the budget year (FY 1974): SecDef decision
on the COIP review (the PDMs) and reclamas. The data
is required as basic input to the preparation of the
draft NIPM.
(2) For the current year (FY 1973): The President's
budget before Congress. This will continue to be the
base year for explaining changes.
(3) For the past year (FY 1972): Actual obligations.
The base year for current trends.
b. In January,
(1) For the budget year (FY 1974): The President?s
budget submitted to Congress. These will be the levels
the DCI will address in his defense of the Community
program before Congress.
(2) For the current year (FY 1973): The Congressional
appropriation. This will be the base year for explaining
change in the DCI speech.
(3) For the past year (FY 1972): Actual obligations.
35.
Approved For Release 2004/06/15 'cl ~JkFPNM00612RO00200020087-6
 Approved For ReI 2004/06/15: CIA, 6t1100612R00020087-6
8. An updating of the data base may be required, for example,
if there is an out-of-cycle "decrement" exercise. Other data,
both program and resource, will be required as part of studies or
reviews of specific activities or issues.
9. It is critical that the above updatings of the complete
data base be accomplished as early in August and January as possible
because of the DCI/IC/Comptroller's tight schedules for producing
the draft NIPM and the DCI's Congressional speech. It is also
essential that these data be available to the DCI/IC/Comptroller
in his work area in order to expedite analysis and use of the data
in preparing the above outputs. Otherwise, the data need not all
be located here physically; nor must it be under DCI/IC/Comptroller
control.
10. Preferably, the data systems and data bases of the Defense
Department, CIA, and State Department can be tapped as needed for
the data this staff requires. An attractive alternative that ought
to be explored is the development of an on-line resources data
base in each Agency (with the possible exception of State where
the smallness of the data base may not Justify the expense of a
sophisticated system) with a data link and console in the DCI/IC
Staff.
11. It would be more desirable for the DCI/IC/Comptroller to
use systems established for, and operated by, intelligence managers
for their own management purposes, recognizing of course that the
36
Approved For Release 2004/06/15:.'A 4EP86MOO612ROO0200020087-6
 Amok Approved For Rele 2004/06/15 : 4-
M00612R000020087-6
DCI
will not require on a routine basis data to the same level of
detail as intelligence managers. The data would thereby be identical
to what they are using for their own purposes, would get updated as
frequently as their own is updated, and there would be a better
chance that we would all be using the same numbers. The fact is
that Defense and CIA managers already have or are working on
management information systems of the type that might satisfy much
of our requirement. In any case, the suggested approach for
acquiring required data is for the DCI/IC/Comptroller to identify
his detailed data needs (above) to Defense so that Defense can then
determine how it can best meet our requirements.
37
Approved For Release 2004/06/15 : CIA-RDP86M00612R000200020087-6