IRAC
Document Type:
Collection:
Document Number (FOIA) /ESDN (CREST):
CIA-RDP80M01133A000200010006-0
Release Decision:
RIPPUB
Original Classification:
K
Document Page Count:
2
Document Creation Date:
December 12, 2016
Document Release Date:
December 18, 2001
Sequence Number:
6
Case Number:
Publication Date:
June 11, 1975
Content Type:
MF
File:
Attachment | Size |
---|---|
![]() | 99.24 KB |
Body:
Approved For Release 2002/01/15 CIA-RDP80MOl133A00020001
DCI/IC 1592-75
11 June 1975
MEMORANDUM FOR; MPRRD Staff
SUBJECT IRAC
it I thought it would be useful to convey to you the
DCI s reaction to our recent efforts concerning the role
of IRAC. General Wilson, Danny and I met with the Director
on 9 June after he had a chance to review the package which
was assembled last week (I have his copy if any of you
would like to see his reaction to particulars).
2. Overall the DCI seems to share our concern about
IRAC, In particular, he agreed that he will be getting more
pressure in the future to demonstrate its utility while,.at
the same time, would not be very much more successful by
trying to move it into the "program development" cycle than
he had been. He therefore agreed that the "middle-of-the-
road" approach we recommended seemed logical.
3. He did not agree that IRAC should function as a
result of his tasking the members. He observed that IRAC
should function vis-a-vis ICS, much in the same way that
USIB functions with respect to the NIOs (i.e., he looks to
the NIO to task the community for a study, not to a USIB
member). He did feel that we ought not forget that IRAC
must look back as well as forward, i.e,, that it has an
"audit" role. And, the primary tool for this is the KEP.
4, He then indicated those study-efforts he felt IRAC
might appropriately sponsor, using ICS as the catalyst;
ALTERNATE Management, organization,
budget arrangements
SEA DRAWDOWN
R&D FUNDING STRATEGY
? new analytical methodologies
security compartmentation.
7
Approved For Release 2002/01/15 : CIA-RDP80MOl133A000200010006-0.
Approved For Release 2002/01/15: CIA-RDP80M01133AO00200010006-0
We noted that, even though we had included it in our
package, we wondered whether this was a subject appropriate
to IRAC; it seemed more logical for USIB concern. The
DCI's reaction was "maybe IRAC can come up with some good
ideas." We then suggested it as a topic of mutual USIB/IRAC
interest.
S. We then drew the DCI's attention to the 'FY 77
issues list, making a special point that we were not advocat-
ing tabling the list at IRAC, but rather that we were taking
this opportunity to run it by him as the list we would be
working from in representing his concerns in the program
development cycle. He agreed.
6. The DCI thanked us for an imaginative job addressing
what he felt was a real problem,
7. As a post-script, the DCI asked General Wilson at
pre--USIB on Tuesday whether he ought to unveil the "new look"
for IRAC at the USIB meeting. General Wilson advised that
it might be premature to prompt a full-scale USIB discussion
before IRAC had met,-but it might be worth mentioning briefly
as something IRAC would be discussing.
8. Having created some momentum, it is important that
we follow through and insure that the DCI's guidance be
reflected in what we prepare for his use at IRAC on 19 June.
The discussion on this item ought to prove very interesting.
Unless the IRAC turns the concept around (an unlikely event)
I think we'll be spending much more of our time catalyzing
studies and preparing DCI resource memoranda which, if
signed, will represent his guidance to the community.
cc; Gen. Wilson
1 - JWB! Chrono - - .
Distribution:
1 D/DCI/IC
1 - AD/DCI/IC
1 USIB/IRAC
1 IC/REG
V to ea. mbr MPRRD
. _ 1. Reading file
Approved For Release 2002/01/15 CIA-RDP80M01133A000200010006-0