NOTES FROM MEETING OF 25 MAY
Document Type:
Collection:
Document Number (FOIA) /ESDN (CREST):
CIA-RDP79B00314A000200060019-4
Release Decision:
RIPPUB
Original Classification:
U
Document Page Count:
2
Document Creation Date:
December 15, 2016
Document Release Date:
April 22, 2004
Sequence Number:
19
Case Number:
Publication Date:
May 26, 1967
Content Type:
NOTES
File:
Attachment | Size |
---|---|
![]() | 83.33 KB |
Body:
Approved For ease 2004/07/07 CIA-RDP79B0031#0200060019-4
Internal Use Only
126 May 1967
.SUBJECT: Notes from Meeting of 25 May
I. In the development of R&D programs in which
various technical components have an interest, areas of
agreement as well as non-agreement need to be surfaced
early, and areas of non-agreement resolved.
2. Major projects tend to be more tangible and may
therefore generally be resolved easier in terms of go/no-go.
3. Leadership by effected technical component heads
to develop a coordinated program when the technical field
lies across organizational boundaries is essential, and
planning of the distribution of the resources which will
be done prior to starting projects could eliminate much
contention and improve efficiency.
4. To further illuminate the broad problem, a-tentative
assumption was posed that ORD effort might be primarily
directed to Research and Exploratory Development, whereas
TSD effort would be directed towards Advanced Development,
Engineering Development and similar work. Thus, ORD would
be working to show feasibility of various devices or
techniques so that T9D could then proceed to develop an
Approved For Release 200f/Qi mC4A 78 9314A000200060019-4
Approved For Foase 2004/07/07: CIA-RDP79B00314W0200060019-4
Internal Use only
appropriate configuration for use, etc., and procure
operational hardware. From this discussion a number of
pros and cons developed, including such questions as:
a. How did ORD get into "competition" with
T$D in the hardware business in the first place?
b. Would this sort.of arrangement drift toward
a single R&D organization?
c. Is pre-planning of the distribution of
effort by the technical chiefs fundamental to this
sort of arrangement?
S. Why aren't we using existing mechanisms?
STAT
Approved For Release 20I,ia(LlMO@P,OP314A000200060019-4