R&D PLANNING CYCLE INSTRUCTIONS

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP85-00024R000400220037-3
• Release Decision: RIPPUB
• Original Classification: C
• Document Page Count: 15
• Document Creation Date: December 20, 2016
• Document Release Date: October 4, 2007
• Sequence Number: 37
• Content Type: REPORT

Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
FY-1985 R&D SCHEDULE
3 August 1982
24 September 1982
1 October 1982
15 November. 1982
22 November 1982
3 January 1983
7 January 1983
30 January 1983
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
CONFLDENTIAL
Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
 Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
! 0
RFD PLANNING CYCLE INSTRUCTIONS
1.0 - Introduction
The RFD 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 RFD solutions proposed.
The instructions have been divided into specific areas as
follows:
Customer Requirements
RFD Solutions
Customer Evaluation
Office Recommendations
2-.0 - Customer Requirements:
The Planning Division of 0/DDSFT will request revalidation
and update as necessary of the RFD 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 RFD 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 - RFD Solutions
The Planning Division will review all problem statements and
designate a Principal Office prior to forwarding the problem
statements to the DDSFT RFD Offices. This designation of
Principal Offices should not inhibit other RFD Offices from
responding to applicable problem statements.
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 2007/10/19: CIA-RDP85-00024R000400220037-3
 Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
The R&D proposals should be in RFD notebook format including
all D&E 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 RFD office is
interested in the problem and wants to be sure that the problem
is fully understood before proceeding.
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.
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.
Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
 Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
0
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.
DFE 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 RFD 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 500 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 2007/10/19: CIA-RDP85-00024R000400220037-3
 Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
DEFISIONS FOR PROGRAM PLAN PAARATION
Program Title
As appropriate to identify the
program activity and/or the problem
statement.
Principal Office Identified with each problem
statement.
Contributing Office Any RD&E Office other than the
Principal Office contributing to the
solution of a problem statement.
Problem Statement Identify by customer, customer number
and title
System or Technology Area_ 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.
Program Objective
Systems Integration
Schedule
Funding
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 tiie funds
reflected in the FY-83 Congressional
Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
 CONFIDENTIAL
Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
0 0
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.
rn\TT;Tn'PXTTT AT
Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
 Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
0
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
RED 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 (1983), 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 RFD Planning notebook and in subsequent
notebooks.
Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
 Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
0 ?XAMPLE
PROGRAM PLAN
I. PROGRAM TITLE:
PRINCIPAL OFFICE:
PROBLEM STATEMENT(S):
II. SYSTEM/TECHNOLOGY AREA: OFFICE FY83 FY84 FY85 FY86
Priority 1. $ $ $ $
Priority 2. $ $ $ $
etc., etc.
TOTAL RECOMMENDED PROGRAM PLAN $ $ $ $
III. 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 2007/10/19: CIA-RDP85-00024R000400220037-3
 Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
?
APPENDIX D
The instructions for development of the System/Technology
Area sheets (proposals) have been modified and are attached.
Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
 CONFIDENTIAL
Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
? ?
(1) PROGRAM
(2) SYSTEM
(3) Office/Project Officer/Telephone Extension
(4)-REQUIREMENT:
(5) CUSTOMER/SCENARIO:
Customer:
Scenario:
(6) DESCRIPTION:
Initial Operational Capability:
Type of Intelligence Product:
(6a) Deliverables/End Products
83:
(6b) 84:
(6c) 85-
(7) FUNDING: 82 83 84 85 86 87 88 89 90
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 2007/10/19: CIA-RDP85-00024R000400220037-3
 Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
? is
SYSTEM/TECHNOLOGY AREA DATA SHEETS
(1) PROGRAM
The Program is the overall descriptor of a grouping of
Systems or Technology Area efforts within an RD&E Sub-Element.
File a separate Program Data Sheet for each Program. Examples of
Programs are:
- Nuclear Weapons Monitoring/Detection
- Audio Surveillance
- Video Surveillance
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 wor 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 RD$E 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 2007/10/19: CIA-RDP85-00024R000400220037-3
 Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
If the RD$E effort is to modify or improve a system, state
the needs and requirements that drive such action. What will be
accomplished with the RD&E 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 DDS&T 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
Name the CUSTOMER organization(s). A customer organization
is one that can validate the requirement for the RD&E effort.
Use the lowest organizational level that is appropriate.
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 RD&E work to be accomplished; e.g., complete
system development, specific system modification or augmentation.
Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
 Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
?
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 RD&E 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? Where are 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 he
obtained from using the resultant RD&E 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 RD&E 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
Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
 Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
?
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:
(1) The extent to which basic technology must be developed
versus system development of integration requirements.
(2) Comparison with the technology used in the currently
operational equipment.
Comparison with the oppositions' target and/or
countermeasures technology.
CONFIDENTIAL
Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
 Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3
Approved For Release 2007/10/19: CIA-RDP85-00024R000400220037-3