SUPPORT TO MILITARY OPERATIONS
Document Type:
Collection:
Document Number (FOIA) /ESDN (CREST):
CIA-RDP81B00401R002300140012-2
Release Decision:
RIPPUB
Original Classification:
S
Document Page Count:
3
Document Creation Date:
December 14, 2016
Document Release Date:
May 19, 2003
Sequence Number:
12
Case Number:
Publication Date:
May 15, 1980
Content Type:
MF
File:
Attachment | Size |
---|---|
![]() | 111.55 KB |
Body:
Approved For Release 2003/0@i lik-RDP81 B00401 R002300140d
IEMORANDIk FOR
(S) NATIONAL RECONNAISSANCE OFFICE
WASHINGTON, D.C.
PERSONAL 15 May 1980
25X1
SUBJEC'`T ' Support to Military Operations
As might be expected, since I became the DNRO I have
been concerning myself with what our posture and relationships
should be with respect to serving operational military needs
via satellite reconnaissance. This issue pervades a
substantial number of institutional relationships which I
have and I have been uneasy about the soundness of the history,
conventional theory, and practices which characterize NRO
.participation in this process. I have, therefore, been holding
fairly extensive dialogue within the Department of Defense to
seek a formula which would provide for a more substantial NRO
role.
In Particular I have been exploring two separate ideas:
First, at the present time, I am charged, on behalf
the Secretary of Defense, to develop, acquire, and operate
25X1 satellite reconnaissance systems solely in response to your
requirements using resources located within the NFIP. Although
there are case-b -case exceptions
it is the rule no e 25X1
25X-exceptions that c aracterize the:NRO. If Defense were to
contemplate a satellite reconnaissance system such as, for
exam le
.
better served if the DNRO were expected to lead such and effort
and I find considerable sympathy for that view.
The second issue has to do with the dissemination
of nrnr1ii---
present De ense practices
_eave a ea ers 1.p o suc an effort straddled between the
Services. i believe both Defense and I t 11'
-+ 1111:1JC1:1 w.Lzn me
processing, reporting and dissemination of SIGINT products
including to the operating commands. Now that we are moving
with E: 1
capabilities, current support to operating forces is more
attracti:-e. However, when one examines the architecture we
25X1
Approved For Releasl '20 - 3106116 A-RDP81 800401 ROO~ OE
NRO review(s)
completed. REVW MAY 2000
CONTROL
SEPIRE
25X1
25X1
25X1
COPIES
PAGES
pproved For Release 2003/06/16 CIA-RDP81 800401 R002300140
SECRET
have and are procuring for this function it is unsettling.
IPGene Tighe has suggested that the DNRO should accept
responsibility at least for defining the system architecture
needed down to the U&S and allied commands and defining the
technical interfaces for the next echelon down.
As of this date, the.results of these discussions are
not very conclusive. The Services and OSD staff agencies
view this with mixed emotion;. most everyone agrees that
something more progressive should be done but are skeptical
of the NRO's "national" associations.
have been delaying discussion with you until I was
clearer about what, if anything, might jell in Defense.
Although--that still isn't happening very fast, there has
been enough internal Defense discussion to make me uneasy
about our lack of dialogue. Therefore, if your time priority
will support an hour on the subject, I think it would be
worthwhile to exchange views for awhile.
Regards,
25X1
CONTROL N
CO?Y OF
Approved For Release 2003/06/16 . - 401 R00230014 --2
25X1
25X1
25X1
25X1
Approved For Release 2003/06/16 : CIA-RDP81 800401 R002300140012-2
Approved For Release 2003/06/16 : CIA-RDP81 800401 R002300140012-2