FY 1985 RESEARCH AND DEVELOPMENT PROGRAM

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP85-00809R000200160017-7
• Release Decision: RIPPUB
• Original Classification: C
• Document Page Count: 19
• Document Creation Date: December 21, 2016
• Document Release Date: March 5, 2008
• Sequence Number: 17
• Publication Date: August 3, 1982
• Content Type: MEMO

Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
-DD/aL.Regis,t.rt-
ifs67g,
4
. ,
DF,' RECORD , SHEET'
,..: . ''''''''`'% ...:,-Zt/7.e.i ,.,.O,ta4r;,4:,.',.,n ' ,? 4.'',,V.1111,14!'". -? 4=a3.,,,,,I ,..?0 ._ , 1,, -'.'., UTI 4

SUBJECT
:.,i,I-1`i;;;Viligi,',Y,4'it2g4,1?11Zift4
r-' ' '' ;-. , ?., ,..-.41'...?..,,, -,;,..
' ? -= t'-'4' a ' . - i;;?t,,.F`,',.....V'Agtir' V ':?..-,?N?,'*-...',4.-...';.......7 ..i..' .,, .. k'.-- A,' ,:1-...),.. ir.
Y..: (O phonal) ' .,. 61........:,:vc?-!..:0&-,..T.4;,,q--t40.-., -..,--..-';,'"..,. - ?.-'.'"-''.. li., ''''''
' . " - - : 1985 ',E,. Research and Development ". ,. ' 7r ,.:?, . v., -.10,4'44...
1.1-T4
'' R. V.P. ,r,k. tf .. .=: ,:.%.7'g,a,,..;..11:',.:.sii":T-4.,..,??.:.;'.!!AeX4Y3Sfii'itiejfit04i1:4.:Vi't.t:.;.:'.!=-4.:--le4A7.1;1.4*-"E4,,;FK.... i,;,,'::4074. _. !, ,I, " ... ?,!.L-c?, . . -4...P44...W..! '..?:
a ,..w,, 4-r "!;'1< - g....M'o:t. 4. -,,q41Tale, c.,:z. ,....,.3--,, ?:-?,..4.,.?,,,?..i.,.,,, ..,..!' ......,. ... ,, ? -- .
, .. ..?
71174XTENSIONe-,
_ .

..-
IVF

i.,......
NTh,44.O k.
.M,,,,,,m,', t,,?it.sT..-.,...i...-7?
1.. .,:.,:,,'.I,.F,,,4.',.L,tl,,:R,:..,.,.,
? ? ,.?:.f.-'.
6?c;1_I;?,..,1v4,
,4:
2DATE
E0/DDV
-,, -,4.
.4.r-r.i.t'"i ?
..0-.
,sO.n,,-,:,? ,4 .V...6? .,-g-
7D18 IQ
.P,.,.".r ? , ..

0?
4
-,,...
, Ve.ti.%4..'
98Z
AUG
a'.,--:', r? :'
_-4',
.70:,. (Officer:, designation room ,.. number ......_ .,. .., .
-:;.:::::-.T, ' --',, ' i. . - ,
'IT, .., ,..?1.,13i.:>,,,.t.'r.,,,Z'
'',ii k -4 ''OFFICEir.-S'!.
,
D,G4::,,,..',I,,,,;Vr1::;*A'ti.54
'..'t..;1"'"-W." ? ..4 4 ,..-? ..? ??1.k.'' ?
111...',.'? ' ? ' .,;...". 1:?..:. ..' ' . ?' ' ? ". ? ? ' ' '''' ` ? '
COMMENTS.z.1 (Nuinlier' each comment to show Irani :',. whom ., ..
:building)
? ..,,....:$; '.;,,,.. E., ....j:."'.!.`4:. .. .i.
..,? ?-v- ,,,JPM7- .,:r.., W. - ti..-`., .,..
- - - .. ,
. RECEIVED 4'''
? - ? - - ' INMALS.: 7 ."to
FORWARDED 7, ,,,, . ,, ., -....,-,;.:;:-:', -
wham Draw a line across? column after each comment):
,,'''., ' .....', r-? - '-:- - ' ' , '',', ..,. , :::'!..; - ' ''.,:,.. .,. - '-';,,,"1'..t-i','''' ...!`".'''',. S. ,''''-'? ''''';;',,??.&.. 7
.
- -, ?,,,,,,i .,;.,;',-1,47;4'.,0 ? 1,11-:??'''',;''''''", ,'
'1:.r.i,..'.; .t....i' . 'f:14i14' 5.t..?9?=1,,:.1,-,.r..igte, . - -,-4,.. - . ',, _ ?.
?
1,... ,
, ..
. ? .1 ,
-..--,.A4,
....-....

...,
.. ..
' ;., ,.."? .,1 . '''' - ft,- ..? '4,:. ?'.4.
?.,;
' , ?...
t-.,,
- A ,
k,4,I.

i..-0,'
O.,.
,,--- :,, s--.
?
`4
..
,r'? t-"5 .3-4

4,
4,1;47
3'.,,,r4..)-7 ;it.w,..: -- t.:: g.,
-,....,
,, ...?
' Rr 4 ,?. ,
-.. ,
,,,r" -
,
--ti s,r.: -...
. ,-.
4-
,
.
: g . v
-,'-'
?h,.- 1 :.
'
. :F1": ..t,
,. ,. ' '
4 = ' ..,1
s`
,...+ v.. :.,
..?..
4.
, ,
...1:
' -
. 4- i
li
t ',..4 .,...i ? ' '
i .7. '
...
4 = -, ' ,,,,.. .,... '' ''' -
...?., ,..t1 :?:, ,
; , ,
4A'
--',7.45*,...',, ' - -,
i?,- --, ,% ''''
'; , -,,.... ,i,
. '
7; ,;;.,
'''' ?-
tt...'::?,2'..t. ,,t
, _ >--',., 4
',':. ? -:i, 1,
,r,
41: t? ?
:
.
?
, 'Fi ' .:,'4, 7' ''. '' :::" . ,
? ,
4 , , ?
'T. ' '
,...
'":
' ''''' ';-.
7. i..
,,?
.,-
,..:4'''"?

, .
.
7 _
i , .
' '?'.. ' ?.: , .f.i..-t
. ..
' ,..1%,-,
.,,.
',.._.*,4.
1.i,.IVI
VA '
k
?.
. :r. 8. ,c: ;-..- ?-? ., , , ,:,..-...:-.,:.?,,Y,,
...
' ?,-1:- ,, .. , .,,
" ?
.. :-.-:'
:!. ..J:
,,
,
t
....
. ..!...,,.. - ?? ?
' -- ..- ..,-..., . T'.':??:.--:*:"' ,:, 4...,,, ' ,, ' ....,.: : ' ' t. ?, .
??: T.,' '
.+,?-?
.
,
.?
? .i
.
.... .
19. ' ?. ..
?-'''..:it.1,-,(:',.
. .
??
, , ..
,- .11 ,,
, ,
. , ...',
' , :,:f'
. ?.. ? ,
.?::..-',-.4..,t,
..
,t' -4, .--- . , ' !,....,-
: '
%
:. . . . .? ? :: s , .,.. ? - ... .., .?.
? ' ,:,,,. . -,;?,.: , , ...,,,
, ? , -, - ?., ,.. --. . ir,
? ,- , ,
-i. , v- ' . ?-, ".,_ ?
,,,,?,,,,,,I,-,.,'...; ',......?.;:'
,:-..,;.,.1.;,...,,,,s ,,......,
..,..,,,,..,::::: .? .
::-..V,2`,'-'7.'
-:,,-7..i-,,,s;....,1.,t,.., -,,,:,
- . ,,,,:?,..,,,?',',,,:,,.,i
.4,,
.,..,... ?;..,...... ._ ,.,..,,-,,
,.`.:,'.'....p-.'..-.;.;?,..:-.,'",
,:'..',%]..- ... .?- .?',7:.:':.:-.,'
. -:/,-, .
" .
'; '.? 1 3....?:.",;:, ?:,-:",",i,,V;:: , . , '.? i .
L ` .: ';''St
,
? `i...,:,
,..4., 4. .. -.?.? .. .,, 'i,- r- ?-' "
. .1" '
i. 17: ,
f .3 , -.i
'', ... "'.%
`,-..r. i' Nn't;
' "' 7.:
'F.4j,.;,..7 ..?....f.,t.'Sf

., . -..,
'.:P'.:''',":',4.'
. .
.A,",
?,'; ' ' ''' - .4. - .3 ... . -.
. _ ,
. , ,.. , ? ? r ??
`.:,
..
!
? , ...
,
. ...
. : . . .. ?. ?.
,...,
..,
' , .. . . . ?, 1" 1 ,
- ?>?,.., ? .
s .7. -. ,--. ,-,-- ..-
s_
,-
' ''...' ' i''-
. ,..-
;',
.
.k t,
...,:o ._
-... .. .. . . . . .
.,Forim:-, 61
' .1-79
AV'f
AT4.
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
IDD/A Registry
l
1 42-.206-2
C-O-N-F-I -D-E-N-T-I-A-L
MEMORANDUM FOR: Director of Communications
Director of Data Processing
Director of Finance
Director of Information Services
Director of Logistics
Director of Medical Services
Director of Security
Director of Training and Education
FROM:
SUBJECT:
Executive Officer to the DDA
FY 1985 Research and Development Program
1. Attached is the DDS&T call for FY 1985 Research and Development
(R&D) requirements which requests that Directorate submissions be made to
the ST by 24 September 1982. The requested content and format of your
submission are nearly identical to those used last year.
2. The Directorate of Administration will again be using the
members of the R&D Panel (currently composed of OC, ODP, and OS representa-
tives) to develop an initial priority ranking. In order to develop a
consolidated Directorate program, we will need your individual Office
submissions by 10 Svtelabal...12.82.
3. As with last year, we ask that in addition to the information
requested by the ST, you include a note which indicates whether this
is a new or an ongoing requirement.
4. If you have any questions on this matter, please contact
Management Staff,
Attachment
C-O-N-F-I-D-E-N-T-I-A-L
0L2
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
'Z 1.?
1/4.1 ?) ()
-25X1
25X1
25X1
25X1
25X1
25X1
25X1
225X1
IHmi:rnrATTTAT
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
MEMORANDUM FOR:
DDS&T-3450-82
3 AUG 1982
Chief, CRES/DDI
Chief, Technical Control/PCS/DDO
DDA Plans Officer
Executive Officer,
FBIS
FROM:
25X1
Division, PRS/DDS&T
unier, rianning
SUBJECT:
FY-1985 R&D Planning Cycle
1. The FY-1984 R&D Planning Cycle has been completed and
the RDE included within the FY-1984 program addresses the
leading priorities of all customers. In order to implement a
successful FY-1985 program, we must begin the R&D Planning Cycle
now by asking that you reevaluate your requirements and
priorities with appropriate updates/deletions or new
requirements.
2. The schedule for FY-1985 (attached) reflects the later
submission dates associated with CPB. Also attached is a current
list of contacts for Directorate customers, DDS&T R&D Offices and
the 0/DDS&T Planning Division.
3. The first scheduled date is 24 September 1982 for
submission of prioritized customer requirements. At any time
during this Planning Cycle please call me or members of my staff
if we can be of assistance.
Attachments:
As stated
25X1
? rnm-pTn-pmTTar
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
3 August 1982
24 September 1982
1 October 1982
15 November, 1982
22 November 1982
-3 January 1983
7 January 1983
30 January 1983
FY-1985 R&D SCHEDULE
Requirements Call
Customer Requirements to PRS
Customer Requirements to Offices
R&D Proposals to PRS
R&D Proposals to Customers
Customer Rankings and Comments to PRS
Customer Rankings to Office
Office Priorities and Needed Proposal
Revisions to PRS
CONFIDENTIAL
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
4W11111./.1,11/1X-VM,
s)
R&D PLANNING CYCLE INSTRUCTIONS
1.0 - Introduction
The R&D Planning procedures for 1985 are similar to those of
last year but with renewed emphasis on coordinating the schedule
of events while continuing to both reduce the quantity and
improve the quality of requirements and R&D solutions proposed.
The instructions have been divided into specific areas as
follows:
Customer Requirements
R&D Solutions
Customer Evaluation
Office Recommendations
2.0 - Customer Requirements:
The Planning Division of 0/DDS&T will request revalidation
and update as necessary of the R&D problem statements from our
customer organizations (currently DDO, DDA, DDI, and FBIS).
These should, insofar as possible, address relatively broad
classes of problems rather than specific techniques so as to
allow some latitude in identifying solutions and avoid
unnecessary proliferation of paperwork. Since the results of
many R&D programs may lie at least five years in the future, the
types of problems submitted should be forward looking in nature
and prioritized by each customer to reflect their relative
importance.
3.0 - R&D Solutions
The Planning Division will review all problem statements and
designate a Principal Office prior to forwarding the problem
statements to the DDS&T R&D Offices. This designation of
Principal Offices should not inhibit other R&D Offices from
responding to applicable problem statements.
3.1
The Principal Office or a Contributing Office will formulate
a Program Plan (Appendix B and Appendix C) for one or a group of
Problem Statements. It is up to the Office to aggregate problem
statements that are amenable to a single program plan of attack.
CONFIDENTIAL
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
The R&D proposals should be in R&D notebook format including
all DU efforts for the Execution Year (FY-1983), Budget Year
(FY-1984), and Program Year (FY-1985). Technology developments
will be included only for the Execution Year. (See Appendix D).
Office forwards four copies of the Program Plans and
system/technology sheets to the Chief, Planning Division in R&D
notebook format.
During the period when the R&D offices are considering the
customer's problem statements and formulating proposals it is the
R&D offices' responsibility to establish a dialogue with the
customer to verify proper understanding of the problem and its
scope as well as to let the customer know that the R&D office is
interested in the problem and wants to be sure that the problem
is fully understood before proceeding.
3.2
No specific provisions have been made above for R&D
proposals for which there is no problem statement. However, if a
limited number of such proposals warrant special attention a
program plan should be prepared for each group of proposals that
jointly attack a problem. Unsolicited proposals, if any, that do
not lend themselves to integration into a program plan should be
grouped by customer organization under a cover sheet for that
customer organization. The cover sheet should state that the
attachments are unsolicited proposals for that customer and list
the proposal names and FY-1985 funding request.
3.3
System/Technology area sheets (see Appendix D) will be
developed for each R&D solution proposed by both Principal
Offices and Contributing Offices. If the proposed D&E solution
is an ongoing effort, list the funding profile for the two
preceeding years plus the Program Year and four out-years with
funding increments, if appropriate. For D&E efforts ongoing in
one or both of the preceeding years but for which no program year
funding is requested, include the current write up in the
applicable Program Plan. Technology Development efforts
specifically identified for the Execution Year should be included
in the Program Plan. Technology Development funding will be a
separate and distinct line item in the program call formulation
and is not subject to customer evaluation at this time.
4.0 - Customer Evaluation
The Planning Division will review and forward the Program
Plans with their attached proposals to each R&D customer
organization in accordance with the attached schedule.
2
CONFIDENTIAL
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
CONFIDENTIAL
As in the past, the customer organizations will be requested
to provide a 1 to n ranking of each proposal received. Customer
queries are encouraged and we invite your fullest cooperation in
responding to questions, requests for additional information or
clarification during all phases of Program formulation. The
customer rankings will then be forwarded to each R&D office to
assist you in formulating your own Office priorities.
Once the customers have ranked their portion of the R&D
program it is inappropriate for proposals to be combined. For
example, a highly ranked proposal at low dollar value cannot
later be combined with a lower ranked related proposal at a high
dollar value. Make sure your proposed solutions, if inseparable
as elements of the attack on the problem, are written up as one
system/technology area (one proposal) when first submitted.
D&E solutions proposed to the customer must remain as D&E
line items throughout the Program Call formulation. Withdrawing
highly ranked D&E solutions or recategorizing them to the
Technology Development line item distorts the customer
evaluation.
D&E solutions may be withdrawn for cause during the Office
Recommendation portion of the cycle described below.
5.0 - Office Recommendation
After receipt of the customer rankings, the next step in
preparation of the R&D program is the development of a 1 to n
ranking of all R&D systems generated by each Office.
If substantive changes to previously submitted systems are
necessary to accommodate customer suggestions and comments or to
more clearly reflect your program, system and program sheets
should be updated, coordinated with customer, and forwarded to
the Planning Division along with the rankings by the scheduled
date. These changes may encompass narrative, financial data and
the addition of new systems.
If a solution ranked in the top 50% of a given customer
ranking is withdrawn the reason for the withdrawal should be
forwarded to the Planning Division with the above described
information.
CONFIDENTIAL
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
I SIN 14 I-111-W T riff I
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
(
DEFINITIONS FOR PROGRAM PLAN PREPARATION
Program Title
Principal Office
Contributing Office
Problem Statement
System or Technology Area
Program Objective
Systems Integration
Schedule
Funding
As appropriate to identify the
program activity and/or the problem
statement.
Identified with each problem
statement.
Any RDE Office other than the .
Principal Office contributing to the
solution of a problem statement.
Identify by customer, customer number
and title
List the proposed systems or
technology efforts that contribute to
the solution of the problem
statement. Show the priority of
these systems as determined by the
Office. Remember, list only the
dollar value attributed to the
system/technology area that pertains
to this problem statement or
aggregated group of problem
statements.
Describe the overall intelligence or
operational purpose of the program.
The objective may go beyond what the
systems and/or technology area
efforts under the program will
accomplish. Include a justification
of outyear planning wedge funding.
State how the individual efforts
relate to each other and how each
contributes to the solution of the
problem. Indicate the minimum
funding required for a significant
contribution to the solution of the
problem.
Display the program schedule on a
one-page graphic showing the
execution span of each proposal with
key events.
Show the financial accounting number
(FAN) associated with the R&D
contract funds. Show the funds
reflected in the FY-83 Congressional
CONFIDENTIAL
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
LON 1' 1 DEN T IAL
and your proposed FY-84 Congressional
submission. If more than one FAN is
involved, repeat for each FAN.
Proposed efforts for FY-85 will
include only the amount of dollars
supported by the system/technology
sheet directly applicable to the
problem statement or aggregated group
of problem statements.
2
Approved For Release 200870-3/05T-CCAWE5P85-00809R000200160017-7
? Approved For Release 2008/63705 : CIA-RDP85-00809R000200160017-7
PROGRAM PLAN
A Program Plan is an integrated overview presenting the
problem statement and the R&D system proposals to satisfy the
problem. It ties together the individual System Technology Area
proposals which are in R&D notebook format.
A single Program Plan will be prepared encompassing all the
R&D solutions proposed against a problem statement or group of
problem statements by an office.
All Program Plans and supporting system/technology sheets
will be on 8 1/2" x 11" paper and typed utilizing a 10-pitch
element or daisy wheel printer.
Program Plans will include all funded efforts for the two
years preceeding this Planning/Program year; i.e., the Execution
Year (1985), the Budget Year (1984) as well as the Program Year
(1985). The Execution Year (and only that year) must include
specific ORD Technology Development Projects. No Technology
Development efforts or out-year projections of them in the Budget
or Program Years are to be included.
Program Plans will include only the amount of dollars
supported by the system/technology sheet directly applicable to
the problem statement or aggregated group of problem
statements. (See Appendix D)
As Program Plans are formulated, every effort should be made
to ascertain that system/technology titles are not repeated and
that the titles used are meaningful in order to avoid title
changes later in the planning cycle.
The Program Plan format will be used for the program sheet
format in the FY-1982 R&D Planning notebook and in subsequent
notebooks.
CONFIDENTIAL
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
CONFIDVNTTAL
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
PROGRAM PLAN
I. PROGRAM TITLE:
PRINCIPAL OFFICE:
PROBLEM STATEMENT(S):
EXAMPLE
II. SYSTEM/TECHNOLOGY AREA: OFFICE FY83 FY84 FY85 FY86
Priority 1. $ $ $ $
Priority 2. $ $ S.-- $ .
etc., etc.
TOTAL RECOMMENDED PROGRAM PLAN
PROGRAM OBJECTIVE: (Space as Required)
.IV. SYSTEMS INTEGRATION: (Space as Required)
V. FUNDING 83 84 85 86 87 ,88 89
FAN
FY83 Congressional
FY84 Congressional
Operating Amount
VI. SCHEDULE (Separate one-page graphic)
CONFIDENTIAL
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
..aW11.1.11/14/111/XXL
APPENDIX D
The instructions for development of the System/Technology
Area sheets (proposals) have been modified and are attached.
CONFIDENTIAL
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
CONFIDENTIAL
(1) PROGRAM
(2) SYSTEM
(3) Office/Project Officer/Telephone Extension
(4) REQUIREMENT:
(5) CUSTOMER/SCENARIO:
(6) DESCRIPTION:
Source:
Customer:
Scenario:
Initial Operational Capability:
Type of Intelligence Product:
(6a) Deliverables/End Products
83:
(6b) 84:
(6c) 85:
82 83 84 85 86 87 88 89 90
(7) FUNDING:
Contract (FAN)
FY-83 Congressional
FY-84 Congressional
. FY-85 Proposed
Operating Amount
(8) SYSTEM JUSTIFICATION:
Date Originated
Revised
Date
FY-85 PROGRAM CALL NOTEBOOK FORMAT
SYSTEM SHEET
CONFIDENTIAL
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
SYSTEM/TECHNOLOGY AREA DATA SHEETS
(1) PROGRAM
The Program is the overall descriptor of a grouping of
Systems or Technology Area efforts within an RDE Sub-Element.
File a separate Program Data Sheet for each Program. Examples of
Programs are:
- Nuclear Weapons Monitoring/Detection
- Audio Surveillance
- Video Surveillance
(2) SYSTEM or TECHNOLOGY AREA Efforts:
A short, unique, meaningful title should be associated with
each SYSTEM or TECHNOLOGY AREA effort. Where such information is
restricted to special bigot-list access, a separate (addition)
sanitized version of the forms, including sterile version of
otherwise-sensitive information, should be provided. Exploratory
development work, and all work not associated with an actual or
planned system, should be identified as TECHNOLOGY; in such cases
TECHNOLOGY should be the last word in the title. For SYSTEMS,
the word SYSTEM should be the last word in the title. For
activities that are not SYSTEM nor TECHNOLOGY-AREA efforts such
as work orders and service contracts or groups thereof, the words
SYSTEM or TECHNOLOGY-AREA should not be used in the title. Also,
state the classification of the title.
(3) OFFICE/PROJECT OFFICER/TELEPHONE EXTENSION
Show your Office, the Project Officer's name for this system
or technology area effort, and his telephone number.
(4) REQUIREMENT
Define the purpose(s) of your system or technology area or
equivalent efforts. What intelligence or operational objective
will be met by employing the product of the proposed R&D
effort? To what degree and how will this effort contribute to
the solution of the requirement? Be specific. State in detail
what problems we face and how the RDE effort will overcome the
problem.
The first few sentences should summarize the requirement, be
classified at not higher than the SECRET level and be set off by
brackets.
For each System or Technology effort the material on its
data sheet should convey the importance of performing the effort
and the reasons for that importance.
CONFIDENTIAL
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
J.J.J.L.LN111"1.14
If the RDU effort is to modify or improve a system, state
the needs and requirements that drive such action. What will be
accomplished with the RDE results that cannot be accomplished at
all or as well without it?
Greater care should be taken to make clear how the proposed
system/technology effort will help and to use a few key words
from the problem statement against which the solution is being
proposed.
SOURCE:
State the specific written requirement, identify the
requiring Office or DDO Area Division. List not only the
customer and problem statement number, but also the title and, if
the solution applies to only a particular subset, so identify.
Also indicate the DDSU guidance (Problem Statement Tab Number)
that this effort responds to, if appropriate. Identification of
the source of the requirement is not a substitute for a precis of
the requirement. (Describe the current requirement for that
Program's existence.) In the case of directed exploratory
development, in addition to showing that the work is "directed"
and designating the office that directed it, the operational,
intelligence or other requirement or need that lies behind the
directed work should also be stated both by reference and precis.
(5) CUSTOMER/SCENARIO
CUSTOMER:
Name the CUSTOMER organization(s). A customer organization
is one that can validate the requirement for the RDE effort.
Use the lowest organizational level that is appropriate.
SCENARIO:
Discuss the specifics of the operational use
concept/scenario. For System falling under Sub-Elements 1
through 10 (Technical Collection), identify name/location of
specific operational target(s) against which the system will be
deployed. Specify the method of deployment of the system (human,
machine, animal). State the status of agreements for the user(s)
to employ the subject system.
(6) DESCRIPTION:
For a System, define the technical characteristics of the
System. Include pertinent numbers such as resolution, .
sensitivity, power requiremnts, environmental constraints, and
overall size. For all Systems requiring power sources
(integrated or separate) for their operation/implementation,
describe the salient technical characteristics of the power
source. State the RDE work to be accomplished; e.g., complete
system development, specific system modification or augmentation.
CONFIDENTIAL
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
CONFIDENTIAL
Follow-on and previous efforts should be included. The
nature of such efforts and their relationships to the current
year's effort should be shown explicitly. The first few
sentences should summarize the description, be classified at not
higher than the SECRET level and be set off by brackets.
INITIAL OPERATIONAL CAPABILITY (IOC):
List the date when the RDE product can first be employed
productively. For exploratory work, state when the results will
be available for subsequent-phase exploitation. When do you hope
to achieve what level of capability? Whereyare you now? Do not
generalize with a phrase such as "continuing update."
TYPE OF INTELLIGENCE PRODUCT:
Identify the nature of the expected system product to be
obtained from using the resultant RDE product (e.g., a tape
recording, a picture, a thermal plot).
(6A)
Indicate the expected results to be obtained during the
preceding and program year; i.e., what hardware, test results,
reports, computer programs, etc., will be delivered on what
dates? State how the results will aid in satisfying the
system/technology area requirements.
(6B)
Same as above, except state the results to be obtained
during the budget year.
(6C)
Same as above, except state the results to be obtained
during the congressional year.
(7) FUNDING
Indicate the financial accounting number (FAN) associated
with the RDE contract funds (SOC 2530). The FY-83/84
Congressional figures are for reference only and the proposed
numbers do not have to be the same. Incremental funding required
by a given activity within a system/technology area must be
identified. These increments must be on all copies of the
system/technology area sheets. Thus, if you are proposing a
solution that applies to two or more unaggregated problems,
provide the breakout of resources against each problem.
(8) SYSTEM JUSTIFICATION
If this is a new system, provide additional background
information to aid in supporting your proposed activities. This
CONFIDENTIAL
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
? ? ?
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
information should be complementary to the information provided
in other sections. As a minimum include a technology assessment
of the proposed project. The technology assessment should
address such topics as:
The extent to which basic technology must be developed
versus system development of integration requirements.
Comparison with the technology used in the currently
operational equipment.
Comparison with the oppositions' target and/or
countermeasures technology.
CONFIDENTIAL
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
25X1
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7
GUIDELINES FOR R&D PROPOSALS
1. Office and Problem Number - This designator will be used
throughout the process of working with DDS&T to identify
individual problems.
2. Title - Brief statement of the subject of the requirement.
3. Policy Basis - Statement of justification for the importance
of the problem. The DCID priority should be included if
applicable.
4. Expected Benefits - Statement of the value or contribution
to the office of solving the problem.
5. Customer - Designate the division, branch, telephone number
and name of the point-of-contact who could supply additional
information on the requirement to project officers in DDS&T.
6. Problem Description - This section should contain clear
statements of the problem to be solved.,
7. Background for Support Activities - A short discussion for
DDS&T on the backgrounds of the work to be done is highly
desirable.
8. Time Requirement - Is the solution to the problem needed
now, is it a long-range problem, or both?
9. References - Include any references that would be beneficial
for the SET project officer to read to obtain further infor-
mation on the problems to be solved.
10. Ranking - The importance of each problem relative to all
the other problems submitted by the office should be defined.
If the ranking number is identical to the problem number,
it should be so stated.
Approved For Release 2008/03/05: CIA-RDP85-00809R000200160017-7