CONTRIBUTOR’S GUIDE

In accordance with P.L. 102-190, Section 802, implemented by the Defense Federal Acquisition Regulation Supplement (DFARS) and Guidelines For Contractor Communication of Independent Research and Development (IR&D) Technical Information, July 1992, Updated/Reprinted April 1994, contractors are encouraged to engage in research and development activities of potential interest to the Department of Defense (DoD). DOD Instruction 3204.1, IR&D, 1 Dec 83, implements the public law.

The Defense Technical Information Center (DTIC) plays a vital role in the collection and dissemination of IR&D information by collecting IR&D summaries from industry and putting them in the centralized IR&D database accessible to DOD scientists, engineers, and analysts. By submitting to this database, DOD contractors provide DOD with important information on their IR&D projects, which helps DOD identify potential solutions for DOD needs.

This manual provides specific instructions and establishes uniform data elements for the input of data on contractor IR&D projects to the DOD IR&D database. The data elements in the IR&D database were determined with full cooperation from the Multi-Association Task Group on IR&D. This group is comprised of industry IR&D representatives.

Contributors desiring broad IR&D policy guidance on this subject should write to:

Office of the Secretary of Defense

DDR&E

Room 3E1049, The Pentagon

Washington, DC 20301-3080

B. Introduction

The IR&D data you submit will be distributed to Government Research and Development (R&D) personnel via the Defense RDT&E Online System (DROLS) and SECURE STINET on the Web. The data is made available through a secure Internet site unless your company has explicitly informed DTIC that you do not want your information available in this manner.

All IR&D data submitted to DTIC must be UNCLASSIFIED even though the overall classification of the project may be classified.

C. DTIC Contact Point And Input Address

The following address and telephone number will be used for all communications with DTIC about any aspect of the preparation/input of data for the IR&D Database and/or for interpretation or clarification of input instructions:

Defense Technical Information Center

ATTN: Acquisitions Branch (DTIC-OCA)

C/O Mr. David Hyman

8725 John J. Kingman Road, Suite 0944

FT. Belvoir, VA 22060-6218

Telephone: 703-767-9039

DSN: 427-9039

IR&D Homepage is http://www.dtic.mil/ird

Chapter 2 - Preparation And Submission Of IR&D Project Data

A. Basic Requirements For Submitting IR&D Data Documents

Assignment of Organization Source Codes and Accession Numbers

Each IR&D submission must contain a valid Source Code and Accession number.

a. Source Codes

Each company's IR&D focal point must obtain a unique organization source code (often called corporate source code) for their organization prior to submitting data to DTIC. If your corporation is comprised of several companies or divisions and each perform IR&D, each company or division will require a separate source code.

Additionally, if an organization’s name changes (reorganization, buy-out, takeover, etc.) a new organization source code must be obtained.

Source codes are obtained from the DTIC Acquisitions Branch contact point by calling Mr. David Hyman at 703-767-9039 or email dhyman@dtic.mil. DTIC requires the following information in order to create source codes:

(1) Parent Organization

(2) Performing Organization

(3) Performing Organization Street Address

(4) Performing Organization, City, State, and Zip Code

b. Accession Numbers

DTIC issues a "block’ of accession numbers for each source code. The accession number is the key to identification and storage of IR&D records in the DTIC databases. It is composed of a unique 6-digit serial number preceded by a 2-digit company fiscal year. Therefore, if a company is allocated a block of 6-digit serial numbers, by assignment of a new 2-digit prefix for each new fiscal year, the company perpetuates its block of unique 8-digit numbers for each year's program.

Do not assign duplicate accession numbers. Duplicate numbers will be rejected by our system. It is imperative that each reporting entity stay within their allocated accession number range. If the number of projects reported exceeds the given range, contact DTIC to receive additional numbers.

If your company ownership has changed since the last reporting year, please inform DTIC since a new accession number range, as well as a new organization source code, may be warranted.

c. Correlation between Accession Number and Source Code

During the DTIC input process, the organization source code is compared to the accession number of a project to ensure that the number is within the accession range for the reporting company. If the cross-field check fails, the project report will be rejected by the input program and DTIC-OCA will promptly notify the contributor by telephone.

B. Submission Contents

Each company should submit descriptive project summaries for each IR&D project. Additionally, each company should submit two overview files describing the structure and scope of the companies IR&D program. The overview files consist of an Overview "A" (OVA) file and an Overview "B" (OVB) file.

1. Overviews Files A and B:

The OVA file provides an overall description of a company’s organization structure and the basic IR&D program management. The OVB is optional and provides a listing of project titles and current and prior year funding allocated to each project. A complete description of these files and samples can be found in Appendix A.

2. Project Summaries:

A project is a grouping into which R&D efforts are categorized for purposes of contractor technical management. Each project should be unique as defined by its need and objective. Projects should be technically distinguishable from one another and their descriptions should reflect this uniqueness. For example, when a system study or development effort includes several subsystems, each of which has unique technical problems, separate projects should be established. However, system studies or development efforts which integrate technologies to develop a total system, and assess total system parameters may be presented as a single project.

C. Submission Format/Template

1. Data Template/Input Software

Contractors must prepare IR&D data using the Microsoft Word Template provided by DTIC.

DTIC may attempt to process other formats, but in most cases this cannot be accomplished. Please notify DTIC-OCA as early as possible if you do not intend to use Microsoft Word. DTIC will need ample time to coordinate these efforts with you to resolve data processing problems encountered as DTIC processes the data. DTIC cannot guarantee that graphical data in these documents will appear on SECURE STINET as displayed in the originating software package.

2. IR&D Project Description Structure

An IR&D project description will be divided into two parts. The first part will contain the bibliographic information or short text fields for the project in a data block format and the second part will contain the narrative description. Detailed descriptions of the IR&D Data Elements are provided in Chapter 3.

a. Data Block Information

The bibliographic information will reside in a data block structure at the beginning of the document. See Data Element Descriptions in Chapter 3 for the data block format that should be followed. To facilitate data input of this information, DTIC has included with this guide a Microsoft Word form template. This template allows input of data elements in a sequential manner and has built-in data edit routines. Additional copies of these templates with user instructions can be obtained from DTIC-OCA by calling (703) 767-9039 or by writing to the DTIC contact address provided in Chapter 1, Section C.

The only portion of the template that can be modified is the IR&D data disclaimer that is displayed at the top of the data block. This information is not extracted from the document, as it is not a data element. Notwithstanding, it is recommended that you use the identical wording shown in the disclaimer located on the sample template. If desired, the disclaimer message can also be placed into a document header or footer to ensure that the message is printed on each page when users of the document print out the information.

Also, please do not exclude data blocks in the template even if there is no data to be reported. Similarly, no additional data element blocks should be added even if you had reported on those fields in previous reporting sessions (i.e., prior years). The data elements shown in the sample template in Page 16 are all that is required and are all that will be accepted into the system.

In short, any deviation from the structure and content of the sample template shown in Data Element Descriptions forces DTIC to manually extract data which causes considerable processing delays.

b. Narrative Description

The project narrative description should begin after the data block. This description is divided into the Keywords, Need, Objectives, Approach, and Progress sections. Please do not move or delete any section headers.

The DOD IR&D contributors homepage (http://www.dtic.mil/ird) provides a sample project document prepared by the Air Force. This document provides insight in how your project descriptions are matched against Air Force requirement documents.

Graphical data can be included in this section. While the inclusion of IR&D data with graphics in the native word processing format will simplify the contractor input process and provides added information value for the users of the data, data storage becomes a constraint.

3. File Names for IR&D Documents

IR&D project description must be contained in a separate document file. Graphical data should be embedded in the document and not as separate files. An IR&D document file must be saved/named with the unique eight character "Accession Number" assigned to the project. Do not save the file under anything but the accession number for windows-based software, the default three character file extension (.doc) used by the word processor should be used to complete the file name. For example, a project plan assigned the accession number 98999999 (FY year/6 digit source code) that was created in Microsoft Word for Windows would be named 98999999.doc.

Please do not send saved template files.

Chapter 3 - Data Element Descriptions and Project Sample

The IR&D Microsoft Word template will facilitate entry of data required in the IR&D data block as defined in this Contributor’s Guided. There are two options available with this template.

Option 1 (default): Microsoft Word Template macros are enabled (turned on), drop-down lists and data validations are available.

Option 2: Microsoft Word Template macros are disabled (turn off).

Special considerations:

No error checking.

Must manually enter correct numerical subject categories and Subcategories, not text descriptions.

Refer to your version MS Word Help about turning off macros.

1. Project Title

Enter the unclassified, descriptive title of the project. This title should refer to a specific system, a technology, or a general area of application of the study or effort.

2. Project Number

Enter a specific project number for each project described. Generally, this number should be preserved throughout the life of the project. If the project changes in category and/or objective, a new project should be established. For the project number in the company/division overview, enter the contractor identification plus "OVA" for part 1 and the contractor identification plus "OVB" for part 2. Overview descriptions are described in detail in Appendix A.

3. Record Accession Number

It is composed of a unique 6-digit serial number preceded by the last 2digits of company fiscal year designation. Each reporting entity has been assigned a range of valid accession numbers. The entry is validated against the organization source code field to prevent an error in processing an accession number that might inadvertently address another company's record. Any document, which does not meet the cross-field check, will be rejected by the input program and the contributor will be promptly notified.

4. Technical Plan Fiscal Year

Enter the 4 digits of the contractor's current fiscal year covered by the Project Description. The last 2 digits will equate to the first two digits of the Record Accession Number.

5. Report Date

Enter the date that the Project Description was submitted in YYMMDD format (e.g., 19970110 for January 10, 1997.)

6. Project Start Date

Enter the date on which work on the project started for continuing or completed projects, and the "will start" date for new projects. Enter dates in YYYYMM format (e.g., 199203 for March 1992).

7. Project Expenditures - Prior Year

Enter in US Dollar currency, to the nearest thousand ($K), the funds expended on the project during the prior year including OVB (i.e., $12,000 = 12). Do not use decimal places, commas, or place a "K" after your data. Enter 0 in this field for OVA.

8. Project Expenditures - Current Year

Enter in US Dollar currency, to the nearest thousand ($K), the estimated dollars to be expended on the project during the current year. (i.e., $12,000 = 12). Do not use decimal places, commas, or place a "K" after your data. Enter 0 in this field for OV A.

9. Organization Name, Address, City, State

Contractors should enter this information to avoid problems that may arise if data in the organization source code is missing or entered incorrectly. Do not include the zip code in this field. Name changes usually require that a new source code and a new accession number range be assigned for input to be accepted.

10. Organization Zip Code

Enter the organization zip code in the format XXXXX-XXXX.

Examples: 12345 or 99999-9876

11. Organization Source Code

Enter the 6-digit organization source code as assigned by DTIC.

12. Organization's IR&D Focal Point

Enter the name of the company official responsible for the organizations’ IR&D technical plan. The format is: Last name, comma, space, first name, space, middle initial. Use only one focal point per source code.

Example: Doe, John J.

13. Organization’s Focal Point's Phone Number

Enter the telephone number of the organization’s IR&D focal point. The Format is: 3-digit area code, 3-digit exchange, and the 4-digit number separated by dashes. This may be followed by an extension number.

Example: 203-585-4399-X234

14. Project Manager/Principal Investigator

Enter the name of the technical point of contact for additional information about the project. The format is: Last name, comma, space, first name, space, and middle initial.

Example: Clark, Henry P.

15. Project Manager Phone Number

Enter the telephone number of the Project Manager/Principal Investigator. The format is: 3-digit area code, 3-digit exchange, and the 4-digit number separated by dashes. This may be followed by an extension number.

Example: 203-585-6700-X123

16. Subject Categories and Subcategories

Option 1 (default): Use drop-down lists.

Option 2: Manually enter at least one or no more than three subject categories and subcategories listed in Appendix B. Codes must be entered exactly as shown in Appendix B especially the placement of periods. Enter codes in first, second, and third order of importance and align vertically within the field block one entry per line. Do not enter more than three subject categories codes or insert commas, colons, or semicolons.

Correct Format

Incorrect Format

1.3.1
1.3.1, 5.3:2.2

5.3

2.2

17. Work Category

Enter one of the following single-letter codes (only codes acceptable) to identify the category of the work. An entry in this field is required including OVA and OVB. See definitions below.

"A" - Applied Research

"B" - Basic Research

"D" - Development

"S" - Systems and other Concept Development Studies

"A" - Applied Research - that effort which (1) Normally follows basic research, but may not be several from the related basic research. (2) Attempts to determine and exploit the potential of scientific discoveries or improvements in technology, materials, processes, methods, devices, or techniques. (3) Attempts to advance the state-of-the-art. Applied research does not include efforts whose principal aim is design, development, or test of specific items or services to be considered for sale. These efforts are within the definition of the term "development" defined in this subsection.

"B" - Basic Research - That research which is directed toward increase of knowledge in science. The primary aim of basic research is a fuller knowledge or understanding of the subject under study, rather than any practical application thereof.

"D" - Development - the systematic use, under whatever name, of scientific and technical knowledge in the design, development, test, or evaluation of a potential new product or service (or of an improvement in an existing product or service) for the purpose of meeting specific performance requirements or objectives. Development includes the functions of design engineering, prototyping, and engineering testing. Development excludes: (1) Subcontracted technical effort which is for the sole purpose of developing an additional source for an existing product. (2) Development effort for manufacturing or production materials, systems, processes, methods, equipment, tools, and techniques not intended for sale.

"S" - Systems and other Concept Development Studies - means analyses and study efforts either related to specific IR&D efforts or directed toward identifying desirable new systems, equipment/ components, or modifications/improvements to existing systems, equipment, or components.

18. Project Sensitivity

Enter "UNCL" if the project effort is unclassified or enter "CLAS" if it is classified including OVA and OVB files. No other terms are allowed.

19. NARRATIVE (Fill in each section as required. Please do not move or delete any section headers)

20. KEYWORDS (no comma, colon, or semicolon on this line)

Provide project-related keywords. KEYWORDS are a single term or short phases (2 or 3 words max) that are used to describe and identify IR&D projects in the IR&D database. The keywords serve the user or searchers to promptly locate the most relevant IR&D projects. IR&D database contributors determine what KEYWORDS they want to use to highlight their IR&D projects. Although keywords are not mandatory entry, most projects have between five and eight and represent the most common method used to query the IR&D database. The choice of effective keywords is crucial in retrieving the particular project during a database search, and hence often can determine the return on investment to the submitting organization. KEYWORDS can also be taken from DTIC Thesaurus. There are no format or font restrictions for KEYWORDS on the IR&D template. The only requirement is that listed KEYWORDS are separated by commas under the KEYWORDS heading of the Narrative section of the IR&D template.

Correct Format

Incorrect Format

KEYWORDS KEYWORDS: Narrative on same line

A single word or phrase, another single word or phrase, another single word or phrase KEYWORDS; Narrative on same line

21. NEED (no comma, colon, or semicolon on this line)

This is a statement describing the void that the project’s product will fill or the reason for the project. Describe the technical problem, deficiency, or business opportunity being addressed. When known, cite the relationship of the project to specific Government requirements or objectives.

22. OBJECTIVE (no comma, colon, semicolon, or any other text on this line)

Briefly state the goal of the project in terms of the results that it is intended to produce. Identify technical objectives along with their specific parameters and quantification. If the project is to continue for several years, indicate the overall objective or goal of the project and then state the specific objectives for the current year’s work. Include in this section a schedule indicating when significant project milestones are expected to be achieved. (Leave this section blank for completed or terminated projects.)

23. APPROACH (no comma, colon, or semicolon on this line)

Provide an explanation of how the investigator plans to achieve the project objective. Briefly describe the overall project plan and the tasks to be performed during the current year. State the methods and techniques to be used, important materials, equipment, or testing involved, and why the selected approach is judged to be the most appropriate way to achieve the objective. Give brief recognition to other approaches and corollary matters to aid in understanding the merits of the selected approach. Explain any unique manner in which resources are planned to be expended, including any significant project expenditures other than labor costs. (Leave this section blank for completed or terminated projects.)

24. PROGRESS (no comma, colon, or semicolon on this line)

Describe results briefly and to the point. Provide a crisp synopsis of the accomplishments of the project during the last year, explaining what the objectives of the project actually were and how they were met. Provide technical detail sufficient to show significance of the results. Unique and unexpected findings should be stated. (Leave this section blank for new projects that were not active during the prior year.)

25. Project Sample

INDEPENDENT RESEARCH AND DEVELOPMENT PROJECT DATA

(INFORMATION IN THIS BLOCK MUST BE UNCLASSIFIED)

Information in this block is furnished by the company in confidence with the claims that: (a) it falls within the exception under subsection (b)(4) of 5 U.S.C. 552, and (b) it is subject to 18 U.S.C. 1905. The information contained herein is furnished for the sole purpose of identifying the subject program, and the DOD shall except as required by the resolution of litigation or the direction of preemptive authority (e.g., The President, Congress, Justice Department) preclude disclosure to other than duly authorized Government Personnel. Any authorized reproduction or disclosure of the information contained herein, in whole or in part, shall include this notice.

(For Help, press F1 while cursor is on field or see Chapter 3 of the IR&D Database Contributors Guide for definition of each element.)

PROJECT TITLE

INSERT PROJECT TITLE

PROJECT NUMBER

01AA-00

ACCESSION NUMBER

01333333

Current Year and Accession Number

TECH PLAN FY

2001

Current year

REPORT DATE

010101

PROJECT START DATE

199801

PRIOR YEAR $K

300

CURRENT YEAR $K

100

ORGANIZATION NAME, ADDRESS, CITY, STATE

ABC Industries, XYZ Division, 13 Elm Street New York, NY

ZIP CODE

10036-9956

ORG. SOURCE CODE

123456

6 DIGIT NUMBER

ORGANIZATION’S FOCAL POINT NAME

Smith, John

TELEPHONE: (212)555-5555

EMAIL: jsmith@abcind.com

PROJECT MANAGER/PRINCIPAL INVESTIGATOR

Doe, Jane

TELEPHONE: (212)555-6666

EMAIL: jdoe@abcind.com

SUBJECT CATEGORIES AND SUBCATEGORIES
(To indicate subject categories and subcategories related to your project, choose a selection from the top drop down, then the next dropdown will fill with subcategories.)

WORK CATEGORY

D-Development

PROJECT SENSITIVITY

UNCL

Most Applicable

1-Aviation Technology

3-Aircraft

1-Helicopters

2^nd Choice

17-Navigation, Detection and Countermeasures

7-Navigation and Guidance

3-Air Navigation and Guidance

3^rd Choice

1-Aviation Technology

2-Military Aircraft Operations

0-All

NARRATIVE (Fill in each section as required. Please do not move or delete any section headers.)

KEYWORDS

Begin keywords

NEED

Begin Need Narrative

OBJECTIVE

Begin Object narrative, schedule may also be included

APPROACH

Begin Approach Narrative

PROGRESS

Begin Progress narrative

Save as word file with a .DOC extension. Do not send template files.

Chapter 4 - Media Preparation and Transmittal of Data

A. Media Preparation

The preferred media for submitting IR&D Documents to DTIC is floppy diskettes, Zip disks, or CD-ROM. However, for contractors who submit a large number of documents, it may be possible for DTIC to accept data on 9 track tape, 8 mm Exabyte Tape, or 4mm Digital Audio Tape (DAT) and Zip Drive cartridges. Please contact DTIC to determine the feasibility of using one of these alternate media types.

1. DOS Floppy Diskettes

Use 3-1/2" (High or Low Density) diskettes for use with standard IBM-compatible personal computer systems. Format diskettes using DOS versions 3.2 or higher.

2. Macintosh Floppy Diskettes

Use 3-1/2" high or low density diskettes.

3. Use of Data Compression Software

If you desire to use data compression software to fit more IR&D data documents on a physical diskette, please make sure you include the decompression software on the diskette with instructions on how to decompress if the resulting compressed file is not a self-extracting file.

4. External Diskette Labeling

Affix a diskette label showing the following information:

(a) A notice of "Unclassified Proprietary" Information.

(b) Name and Source Code of the contributing organization.

(c) Date that the diskette was created.

(d) Count of the number of documents on the diskette.

(e) For a batch of diskettes, mark the total numbers of disks in the

batch, i.e. first diskette in a batch of 4 disks should read "1 of 4."

B. Transmittal Check Sheet

Contributors to the database should include the transmittal check sheet (Appendix D) with each submission. This check sheet will help to remind you of other details DTIC needs to process your data submission.

C. FEEDBACK FROM DTIC

DTIC will telephone if there are any processing problems with your data. If you have any question or need help with filing out the templates, please contact IR&D Program Manager as provided in Chapter 1, Section C.

Contributors are encouraged to send updates of their IR&D projects summaries to DTIC throughout the year. When submitting these updates, please indicate that they are replacements of the initial project summaries.

Appendix A - Overview Descriptions

In order to provide some of the overall contractor information previously presented in the introductory portions of the technical plan, an Overview description, in two parts, should be submitted. The first part of this description referred to as "OVA" summarizes the overall non-financial business aspects of the company/division and its IR&D program. The second part of the overview description referred to as "OVB" provides an overall financial summary of the company/division IR&D program.

Each part is submitted as a separate document. The narrative portion of OVA and OVB differs from the narrative portion for an individual project description in the fact that the information is contained in one section instead of being broken down into four sections.

Please note that the following data elements in the data block template that deal with project specific data should remain blank fields in both the OVA and OVB data block templates: Project Start Date, Project Manager/Principal Investigator, Telephone, Subject Categories and subcategories.

Overview A

The data block portion of OVA will be used to identify the company/division, contractor focal point, telephone number, etc. The project title will be "Overview (Company, Division)." The project number will be the contractor identification plus "OVA". A unique Accession Number must be provided. A "0" (zero) dollar value will be used in the expenditures blocks in the OVA.

The narrative section of OVA summarizes the overall company/division, its products, customers, and how the contractor’s IR&D program is managed. If the unit is part of a larger organization, the relationship should be shown here.

Overview B (OPTIONAL)

The information in the data block portion for this part will be identical to the information in the data block portion for the "OVA" except for the project number (that will consist of the contractor identification and a unique Accession Number. Note that the project title for this document will be the same as the title for "OVA." If possible, please provide total company expenditures in US Dollar currency, to the nearest thousand ($K), for both prior and current year expenditure data element fields. No comma or periods in the blocks.

In the "OVB" narrative section, list the following information for all projects in a column format: Project Number, Project Title, Prior and Current Year Expenditures. Please total the two expenditure year columns. (If necessary, to meet the March 15 submittal cutoff date, best estimates of financial data may be used.) This listing will be used to provide pointers to the individual project descriptions that comprise a company/division plan.

Sample - OVA

INDEPENDENT RESEARCH AND DEVELOPMENT PROJECT DATA

(INFORMATION IN THIS BLOCK MUST BE UNCLASSIFIED)

(For Help, press F1 while cursor is on field or see Chapter 3 of the IR&D Database Contributors Guide for definition of each element.)

PROJECT TITLE

INSERT PROJECT TITLE

PROJECT NUMBER

OVA

ACCESSION NUMBER

01333333

Current year and Accession Number

TECH PLAN FY

2001

Current year

REPORT DATE

010101

PROJECT START DATE

LEAVE BLANK

PRIOR YEAR $K

INSERT ZERO

CURRENT YEAR $K

INSERT ZERO

ORGANIZATION NAME, ADDRESS, CITY, STATE

ABC Industries, XYZ Division, 13 Elm Street New York, NY

ZIP CODE

10036-9956

ORG. SOURCE CODE

123456

6 DIGIT NUMBER

ORGANIZATION’S FOCAL POINT NAME

Smith, John

TELEPHONE: (212)555-5555

EMAIL: jsmith@abcind.com

PROJECT MANAGER/PRINCIPAL INVESTIGATOR

Doe, Jane

TELEPHONE: (212)555-6666

EMAIL: jdoe@abcind.com

WORK CATEGORY
D-Development

PROJECT SENSITIVITY

UNCL

Most Applicable

LEAVE BLANK

2^nd Choice

LEAVE BLANK

3^rd Choice

LEAVE BLANK

NARRATIVE (Fill in each section as required. Please do not move or delete any section headers.)

KEYWORDS

LEAVE BLANK

NEED

Begin your narrative on the line below "Need" and discuss the structure of companies IR&D program.

The narrative section of Overview A (OVA) summarizes the overall company/division, its products/ customers, and how the contractor’s IR&D program is managed. If the unit is part of a larger organization, the relationship should be shown here.

Any charts, diagrams and graphics should be imbedded in the narrative. Do not save graphics as separate files.

OBJECTIVE

LEAVE BLANK

APPROACH

LEAVE BLANK

PROGRESS

LEAVE BLANK

Save as word file with a .DOC extension. Do not send template files.

Sample - OVB (OPTIONAL)

INDEPENDENT RESEARCH AND DEVELOPMENT PROJECT DATA

(INFORMATION IN THIS BLOCK MUST BE UNCLASSIFIED)

(For Help, press F1 while cursor is on field or see Chapter 3 of the IR&D Database Contributors Guide for definition of each element.)

PROJECT TITLE

INSERT PROJECT TITLE

PROJECT NUMBER

OVB

ACCESSION NUMBER

01333333

Current Year & Accession Number

TECH PLAN FY

2001

Current year

REPORT DATE

010101

PROJECT START DATE

LEAVE BLANK

PRIOR YEAR $K

5000

CURRENT YEAR $K

5000

ORGANIZATION NAME, ADDRESS, CITY, STATE

ABC Industries, XYZ Division, 13 Elm Street New York, NY

ZIP CODE

10036-9956

ORG. SOURCE CODE

123456

6 DIGIT NUMBER

ORGANIZATION’S FOCAL POINT NAME

Smith, John

TELEPHONE: (212)555-5555

EMAIL: jsmith@abcind.com

PROJECT MANAGER/PRINCIPAL INVESTIGATOR

Doe, Jane

TELEPHONE: (212)555-5555

EMAIL: jsmith@abcind.com

WORK CATEGORY
D-Development

PROJECT SENSITIVITY

UNCL

Most Applicable

LEAVE BLANK

2^nd Choice

LEAVE BLANK

3^rd Choice

LEAVE BLANK

NARRATIVE (Fill in each section as required. Please do not move or delete any section headers.)

KEYWORDS

LEAVE BLANK

NEED

Project Number	Project Title	Current YR $	Prior Yr $
AA-01	Project ABC	500	400
BB-03	Project XYZ	135	0
CC-01	Project JJJ	90	110
		725	510

OBJECTIVE

LEAVE BLANK

APPROACH

LEAVE BLANK

PROGRESS

LEAVE BLANK

Save as word file with a .DOC extension. Do not send template files.

Appendix B - Subject Categories and Subcategories

0 None of the above

1 Aviation Technology

1.1 Aerodynamics

1.2 Military Aircraft Operations

1.3 Aircraft

1.3.1 Helicopters

1.3.2 Bombers

1.3.3 Attack and Fighter Aircraft

1.3.4 Patrol and Reconnaissance Aircraft

1.3.5 Transport Aircraft

1.3.6 Training Aircraft

1.3.7 V/STOL

1.3.8 Gliders and Parachutes

1.3.9 Civilian Aircraft

1.3.10 Pilotless Aircraft

1.3.11 Lighter-than-Air Aircraft

1.3.12 Research and Experimental Aircraft

1.4 Flight Control and Instrumentation

1.5 Terminal Flight Facilities

1.6 Commercial and General Aviation

2 Agriculture

2.1 Agricultural Chemistry

2.2 Agricultural Economics

2.3 Agricultural Engineering

2.4 Agronomy, Horticulture and Aquiculture

2.5 Animal Husbandry and Veterinary Medicine

2.6 Forestry

3 Astronomy and Astrophysics

3.1 Astronomy

3.2 Astrophysics

3.3 Celestial Mechanics

~~4 Atmospheric Science~~ - NOT USED

~~4.1 Atmospheric Physics~~

~~4.2 Meteorology~~

5 Behavioral and Social Sciences

5.1 Administration and Management

5.2 Information Science

5.3 Economics and Cost Analysis

5.4 Government and Political Science

5.5 Sociology and Law

5.6 Humanities and History

5.7 Linguistics

5.8 Psychology

5.9 Personnel Management and Labor Relations

6 Biological and Medical Sciences

6.1 Biochemistry

6.2 Genetic Engineering and Molecular Biology

6.3 Biology

6.4 Anatomy and Physiology

6.5 Medicine and Medical Research

6.6 Ecology

6.7 Radiobiology

6.8 Food, Food Service and Nutrition

6.9 Hygiene and Sanitation

6.10 Stress Physiology

6.11 Toxicology

6.12 Medical Facilities, Equipment and Supplies

6.13 Microbiology

6.14 Weapons Effects (Biological)

6.15 Pharmacology

7 Chemistry

7.1 Industrial Chemistry and Chemical Processing

7.2 Inorganic Chemistry

7.3 Organic Chemistry

7.4 Physical Chemistry

7.5 Radiation and Nuclear Chemistry

7.6 Polymer Chemistry

8 Earth Sciences and Oceanography

8.1 Biological Oceanography

8.2 Cartography and Aerial Photography

8.3 Physical and Dynamic Oceanography

8.4 Geomagnetism

8.5 Geodesy

8.6 Geography

8.7 Geology, Geochemistry and Mineralogy

8.8 Hydrology, Limnology, and Potamology

8.9 Mining Engineering

8.10 Soil Mechanics

8.11 Seismology

8.12 Snow, Ice and Permafrost

9 Electrotechnology and Fluidics

9.1 Electrical and Electronic Equipment

9.2 Fluidics and Fluerics

9.3 Lasers and Masers

9.4 Line, Surface and Bulk Acoustic Wave Devices

9.5 Electrooptical and Optoelectronic Devices

9.6 Acoustooptic and Optoacoustic Devices

9.7 Electromagnetic Shielding

10 Power Production and Energy Conversion (Nonpropulsive)

10.1 Non-Electrical Energy Conversion

10.2 Electric Power Production and Distribution

10.3 Electrochemical Energy Storage

10.4 Energy Storage

11 Materials

11.1 Adhesives, Seals and Binders

11.2 Ceramics, Refractories and Glass

11.2.1 Refractory Fibers

11.3 Coatings, Colorants and Finishes

11.4 Laminates and Composite Materials

11.5 Textiles

11.6 Metallurgy and Metallography

11.6.1 Properties of Metals and Alloys

11.6.2 Fabrication Metallurgy

11.7 Miscellaneous Materials

11.8 Lubricants and Hydraulic Fluids

11.9 Plastics

11.10 Elastomers and Rubber

11.11 Solvents, Cleaners and Abrasives

11.12 Wood, Paper and Related Forestry Products

12 Mathematical and Computer Sciences

12.1 Numerical Mathematics

12.2 Theoretical Mathematics

12.3 Statistics and Probability

12.4 Operations Research

12.5 Computer Programming and Software

12.6 Computer Hardware

12.7 Computer Systems

12.8 Computer Systems Management and Standards

12.9 Cybernetics

13 Mechanical, Industrial, Civil and Marine Engineering

13.1 Air Conditioning, Heating, Lighting and Ventilating

13.2 Civil Engineering

13.3 Construction Equipment, Materials and Supplies

13.4 Containers and Packaging

13.5 Couplers, Fasteners and Joints

13.6 Surface Transportation and Equipment

13.6.1 Surface Effect Vehicles and Amphibious Vehicles

13.7 Hydraulic and Pneumatic Equipment

13.8 Manufacturing and Industrial Engineering and Control of Production Systems

13.9 Machinery and Tools

13.10 Marine Engineering

13.10.1 Submarine Engineering

13.11 Pumps, Filters, Pipes, Tubing, Fittings and Valves

13.12 Safety Engineering

13.13 Structural Engineering and Building Technology

14 Test Equipment, Research Facilities and Reprography

14.1 Holography

14.2 Test Facilities, Equipment and Methods

14.3 Recording and Playback Devices

14.4 Photography

14.5 Printing and Graphic Arts

15 Military Sciences

15.1 Military Forces and Organizations

15.2 Civil Defense

15.3 Defense Systems

15.3.1 Antimissile Defense Systems

15.3.2 Antiaircraft Defense Systems

15.3.3 Antisatellite Defense Systems

15.4 Military Intelligence

15.5 Logistics, Military Facilities and Supplies

15.6 Military Operations, Strategy and Tactics

15.6.1 Naval Surface Warfare

15.6.2 Undersea and Antisubmarine Warfare

15.6.3 Chemical, Biological and Radiological Warfare

15.6.4 Nuclear Warfare

15.6.5 Space Warfare

15.6.6 Land Mine Warfare

15.6.7 Unconventional Warfare

16 Guided Missile Technology

16.1 Guided Missile Launching and Basing Support

16.2 Guided Missile Trajectories, Accuracy and Ballistics

16.2.1 Guided Missile Dynamics Configurations and Control Surfaces

16.3 Guided Missile Warheads and Fuzes

16.4 Guided Missiles

16.4.1 Air- and Space-Launched Guided Missiles

16.4.2 Surface-Launched Guided Missiles

16.4.3 Underwater-Launched Guided Missiles

16.5 Guided Missile Reentry Vehicles

17 Navigation, Detection and Countermeasures

17.1 Acoustic Detection and Detectors

17.2 Non-Acoustic and Non-Magnetic Submarine Detection

17.3 Direction Finding

17.4 Countermeasures

17.4.1 Radio Countermeasures

17.4.2 Acoustic Countermeasures

17.4.3 Radar Countermeasures

17.4.4 Optical Countermeasures

17.5 Optical Detection and Detectors

17.5.1 Infrared Detection and Detectors

17.5.2 Ultraviolet Detection and Detectors

17.6 Magnetic and Electric Field Detection and Detectors

17.7 Navigation and Guidance

17.7.1 Land and Riverine Navigation and Guidance

17.7.2 Underwater and Marine Navigation and Guidance

17.7.3 Air Navigation and Guidance

17.7.4 Space Navigation and Guidance

17.8 Miscellaneous Detection and Detectors

17.9 Active and Passive Radar Detection and Equipment

17.10 Seismic Detection and Detectors

17.11 Target Direction, Range and Position Finding

18 Nuclear Science and Technology

18.1 Fusion Devices (Thermonuclear)

18.2 Isotopes

18.3 Nuclear Explosions and Devices (Non-Military)

18.4 Nuclear Instrumentation

18.5 Nuclear Power Plants and Fission Reactor Engineering

18.5.1 Nuclear Fission Reactors (Power)

18.5.2 Nuclear Fission Reactors (Non-Power)

18.6 Nuclear Radiation Shielding, Protection and Safety

18.7 Radioactivity Radioactive Wastes and Fission Products

18.8 SNAP (Systems for Nuclear Auxiliary Power) Technology

18.9 Fission Reactor Physics

18.10 Fission Reactor Materials

19 Ordnance

19.1 Ammunition and Explosives

19.1.1 Pyrotechnics

19.2 Aerial Bombs

19.3 Combat Vehicles

19.4 Armor

19.5 Fire Control and Bombing Systems

19.6 Guns

19.7 Rockets

19.8 Underwater Ordnance

19.8.1 Torpedoes

19.9 Explosions

19.10 Ballistics

19.11 Nuclear Weapons

19.12 Directed Energy Weapons

19.13 Guided Munitions

20 Physics

20.1 Acoustics

20.2 Crystallography

20.3 Electricity and Magnetism

20.4 Fluid Mechanics

20.5 Atomic and Molecular Physics and Spectroscopy

20.6 Optics

20.6.1 Fiber Optics and Integrated Optics

20.7 Particle Accelerators

20.8 Nuclear Physics and Elementary Particle Physics

20.9 Plasma Physics and Magnetohydrodynamics

20.10 Quantum Theory and Relativity

20.11 Mechanics

20.12 Solid State Physics

20.13 Thermodynamics

20.14 Radiofrequency Wave Propagation

20.15 Electromagnetic Pulses

21 Propulsion, Engines and Fuels

21.1 Air Breathing Engines (Unconventional)

21.2 Combustion and Ignition

21.3 Electric and Ion Propulsion

21.4 Fuels

21.5 Jet and Gas Turbine Engines

21.6 Nuclear Propulsion

21.7 Reciprocating and Rotating Engines

21.8 Rocket Engines

21.8.1 Liquid Propellant Rocket Engines

21.8.2 Solid Propellant Rocket Engines

21.9 Rocket Propellants

21.9.1 Liquid Rocket Propellants

21.9.2 Solid Rocket Propellants

22 Space Technology

22.1 Astronautics

22.2 Unmanned Spacecraft

22.3 Spacecraft Trajectories and Reentry

22.4 Ground Support Systems and Facilities for Space Vehicles

22.5 Manned Spacecraft

23 Biotechnology

23.1 Biomedical Instrumentation and Bioengineering

23.2 Human Factors Engineering and Man Machine Systems

23.3 Bionics

23.4 Protective Equipment

23.5 Life Support Systems

23.6 Escape, Rescue and Survival

24 Environmental Pollution and Control

24.1 Air Pollution and Control

24.2 Noise Pollution and Control

24.3 Solid Wastes Pollution Control

24.4 Water Pollution and Control

24.5 Pesticides Pollution and Control

24.6 Radiation Pollution and Control

24.7 Environmental Health and Safety

25 Communications

25.1 Telemetry

25.2 Radio Communications

25.3 Non-Radio Communications

25.4 Voice Communications

25.5 Command, Control and Communications Systems

Appendix C - Lessons Learned

The purpose of this list is to identify some common lessons learned that have been accumulated. We ask that you, the contributors, review this list prior to submitting your IR&D data to DTIC to help improve the overall processing time and delivery of your data to DOD users. We also encourage you to share your lessons learned with the contributor community by submitting them to IR&D program manager.

Wrong source code, accession number, or Tech Plan FY.

Do not put dashes into accession numbers. The correct construction of an accession number is FYXXXXXX where FY represents the last 2 digits of the Fiscal Year of the IR&D submission and XXXXXX represents the accession number of the IR&D project.

Do not divide any parts of an IR&D projects summary over multiple documents. Every part of an IR&D project summary should be contained within one document for submission to DTIC.

Save IR&D projects summaries for submission to DTIC as Word. doc’s named as the accession number of the IR&D project summary. In other words, IR&D project summary 01123456 should be submitted to DTIC as 01123456.doc on whatever media the submitter uses.

Web addresses in IR&D project summaries should be constructed as if "live" for ease of use by IR&D database users. In other words, include the http:// with any Web addresses to which IR&D submitters want IR&D database users to be directed.

Please identify the .docs (by accession number) that represent the submitters OVA and OVB (if applicable) files.

Please update the organization focal point and phone number when changes occur.

Do not put more than three Subject categories and/or subcategories codes in the blocks. Please put each subject category on separate lines within each block.

Make sure to have valid Subject categories and/or subcategories codes and all period(s) in the correct place(s).

Do not leave the Category Block and the Project Sensitivity Block blank. This block must be filled in for all files including OVA and OVB files.

Do not modify section headers in narrative.

Appendix D - Transmittal Check Sheet

DTIC requests that all IR&D contributors complete this Transmittal Check Sheet and attach it to your annual IR&D data submission. When completed, the Check Sheet will contain information DTIC needs to process your IR&D Technical Plan data in an expeditious manner. We appreciate your cooperation and will do everything we can to get your technology plan into the hands of scientists and engineers interested in your organization’s research and development.

[ ] Organization Name: _______________________________________________

Point of Contact: __________________________________________________

Complete Address: _______________________________________________

_______________________________________________
city_______________state_________ zip code __________
Telephone Number: _________________________________

Email address: _____________________________________

[ ] Organization Source Code(s): _________________________

[ ] Accession Number Range(s):_____________ to ___________

[ ] Technical Plan Fiscal Year: _________ (4 digits)

(first two digits of Accession Number. Example: 98123456)

[ ] File Names and Accession Number of the Overview Files Submitted to DTIC:

OVA - __________________ OVB - ______________________

[ ] Total Number of Disks (including OVA & OVB) you are sending to DTIC:

__________________

Total Number of Projects on Disks: __________

[ ] Version of Microsoft Word Used: ____________________________

PC or Macintosh platform: ________________________

Name and Phone Number of Person DTIC can call if we encounter problems

processing your data: __________________________________________

[ ] Did you use the DTIC Template and saved as a word (.doc) file?

Yes_____

[ ] Does your Subject categories and subcategories numbers match exactly

those code numbers shown in the Contributor’s Guide including each period?

Yes____

[ ] Are your files name correctly?

Correct Format	Incorrect Format
KEYWORDS	KEYWORDS: Narrative on same line
A single word or phrase, another single word or phrase, another single word or phrase	KEYWORDS; Narrative on same line