SAFE PDR -- SOME VIEWS

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP84B00049R001700290011-6
• Release Decision: RIPPUB
• Original Classification: C
• Document Page Count: 3
• Document Creation Date: December 20, 2016
• Document Release Date: March 20, 2007
• Sequence Number: 11
• Publication Date: February 3, 1982
• Content Type: MEMO

Approved For Release 2007/03/20.: CIA-RDP84B00049RO01700290011-6
COMPT 82-0132
MEMORANDUM FOR: Deputy Director for Administration /
Deputy Director for Intelligence
FROM
Comptroller
SUBJECT SAFE PDR -- Some Views
1. As the SAFE program is now in a critical stage in its development and
will doubtlessly require additional funding, I attended a day and a half of
the final week of PDR to get some perspective of my own and to demonstrate
Agency interest in the program. I have attempted to summarize my views -- re-
stricted as they are by limited contact with the program -- in this memorandum
for your information. II
2. There is good news and bad news on the program's future. I think we
can get there from here -- in terms of acceptable SAFE performance, but it is
going to cost us more, and the program eou.1d be up to a year late. I see a
strong commitment by the contractor and the project office and conspicuous
areas of good management on both parts. However, a number of the managers and
management systems have been brought on board over the last few months; they
look good, but time will tell for sure.
3. The relationship between the contractor and the program office seems
to be excellent with a very open exchange of information. But I am dis-
appointed that there are fundamental areas of missed communication over
requirements and critical design items. I personally would be much more
comfortable with crisper program direction and more explicit formal agreement
and control over items under discussion.
4. It is clear that the current user language requirement statement is
not adequate and that the "2.5" delivery -- estimated in March 1983 by
= -- will not meet DDI anal st needs. This area must be fixed, but an open
negotiation at this time to find the final solution would,
I believe, be unwise. PDR cannot be completed until this requirement is
established and reflected in system design. The requirement and design must
quickly be modified so they are close enough -- within an easy subsequent fix
of the final solution. Then the contractor ,mn t devote all his present atten-
tion. to implementing the interim solution. lul
5. I am encouraged by the performance estimates being generated by the
TRW simulator. But the project office must devote a lot of work to making
these simulations more realistic. Further, they should go on record with the
user community on the level of performance to be provided by the system. This
can keep the user, the program office, the contractor, and the system on the
F
25X1
25X1
 Approved For Release 2007/03/20: QIA7RDP84B00049R001700290011-6
6. The cognizant "Vice President, and
agree the "2.5" delivery should be a test bed in Headquarters leading to full
Block 1 capability in October 1983. I agree that we should push hard for a
March 1983 delivery, and this is the best we can expect. Even this date may
slip a few months, but the best reasonable outcome seems to be a full Block 1
capability late in 1983 or early in 1984.
0
7. Within a few months, the program office should be able to have a high
confidence estimate of Block 1 schedule. They must develop "can deliver" cost
estimates in the very near future. I have asked the Program Manager for a
high confidence upper bound on these costs within a week or so.
Maurice Lipton
25X1
25X1
 Approved For Release 2007/03/20, -CIA-RDP84B00049ROO1700290011-6
Distribution:
1 - Each addressee
1 - SAFE Program Manager
1 - D/ODP
1 - D/OCR
1 - C/IG
1 - C/AG
1 - Compt
1 - D/Compt
1 - Compt Subj
1 - Compt Reading