Ex A CDRL DD 1423.doc

CONTRACT DATA REQUIREMENTS LIST

Form Approved

OMB No. 0704-0188

Public reporting burden for this collection of information is estimated to average 440 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate of Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction project (0704-0188), Washington DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO.

All

B. EXHIBIT

A

C. CATEGORY:

TDP _____ TM _____ OTHER ______X_____

D. SYSTEM/ITEM

SNIM

E. CONTRACT/PR NO.

FA4600-08-R-0025

F. CONTRACTOR

TDB

1. DATA ITEM NO.

A001

2. TITLE OF DATA ITEM

Monthly Metrics Report

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

See embedded template

5. CONTRACT REFERENCE

SOW, Paragraph 1.5.2.3

6. REQUIRING OFFICE

DTIC-I

7. DD 250 REQ

NO

Monthly

12. DATE OF FIRST SUBMISSION

30DAC

14.

DISTRIBUTION

8. APP CODE

N/A

N/A

13. DATE OF SUBSEQUENT SUBMISSION

30DAC

a. ADDRESSEE

Draft

b. COPIES

__Final__ Reg Repro

This report shall be submitted electronically on a monthly basis starting 30 days after contract start in accordance with the template embedded herein.

DTIC-I COR

1. DATA ITEM NO.

A002

2. TITLE OF DATA ITEM

Monthly Contract Tracking Report

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

See embedded template

5. CONTRACT REFERENCE

SOW, Paragraph 1.5.2.4

6. REQUIRING OFFICE

DTIC-I

7. DD 250 REQ

NO

Monthly

12. DATE OF FIRST SUBMISSION

30DAC

14.

8. APP CODE

N/A

13. DATE OF SUBSEQUENT SUBMISSION

30DAC

a. ADDRESSEE

Draft

b. COPIES

Reg Repro

1. DATA ITEM NO.

A003

2. TITLE OF DATA ITEM

Weekly Activity Report (WAR)

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

See embedded procedures

5. CONTRACT REFERENCE

SOW, Paragraph 1.5.2.5

6. REQUIRING OFFICE

DTIC-I

7. DD 250 REQ

NO

As Required

12. DATE OF FIRST SUBMISSION

30DAC

14.

8. APP CODE

N/A

13. DATE OF SUBSEQUENT SUBMISSION

Weekly

a. ADDRESSEE

Draft

b. COPIES

Reg Repro

G. PREPARED BY

H. DATE

I. APPROVED BY

J. DATE

Section J Exhibit A, DD Form 1423-2, AUG 96(EF)

PREVIOUS EDITION MAY BE USED.

Page ___1____ of ____1__ Pages _1289118626.doc Standard Operating Procedures for Weekly Activity Reports (WARs) – 1 January 2005

SUBJECT: Standard Operating Procedures for the IAC Weekly Activity Reports (WAR)

I. PURPOSE: To provide guidance for the preparation and submission of the Defense Technical Information Center (DTIC) Information Analysis Center (IAC) Weekly Activity Report (WAR). These procedures will be used to prepare and distribute the mandatory WAR from each IAC to the DTIC IAC Program Management Office (PMO) who will forward to the DTIC Administrator and the Office of the Secretary of Defense (OSD) for further distribution.

II. BACKGROUND: The DTIC IAC WAR is a compilation of information submitted by the IAC Directors, special staff, and IAC Satellite Officers for inclusion in the WAR. The Centers’ WAR details the IACs’ most significant accomplishments. The OSD sponsors require the IAC PMO to have the IACs report information on a regular basis. The IAC PMO requires regular IAC input to the WAR. It is assumed each IAC is providing valuable services and/or products that should be reported once a week. The IAC PMO needs and uses this information to support and defend the program budget and also to exemplify your importance in the National Defense of our Nation.

III.

APPLICATION: This mandatory SOP will be will be applied to all DTIC sponsored DoD IACs effective immediately.

IV. CONSOLIDATION AND PREPARATION OF WAR:

A. Each IAC shall submit a consolidated WAR, which may include input from Deputy Directors, Special Staff Officers, IAC TAT Managers, and Field Activities to the DTIC IAC PMO no later than noon every Tuesday, negatives are required. Electronic submissions (MS Word compatible to DTIC) should be sent to iacwar@dtic.mil and to the assigned IAC Program Management Analyst (PMA).

B. Each WAR submitted is categorized by the DTIC IAC PMO based on appropriateness, sensitivity, and applicability to the DTIC IAC program as a whole. Each IAC is highly encouraged to submit multiple WARs weekly.

C. Items for DTIC and OSD will be categorized based on the following criteria:

· Key IAC Technology News Breakthroughs

· IAC Work on high level Organizations (i.e., Unified Commands, OSD, Presidential

Initiatives, etc.)

· Disaster Assistance (if applicable)

· Press Inquiries

· Grants, Economic Announcements, and Publications (if applicable)

D. Each WAR submission should be self-contained and independent of any prior submission (must stand alone). Include a sentence of content or background, describe the situation/issue, and conclude with who is affected.

Technical Area Tasks (TATs)/Subscription Accounts (SA): If the WAR is TAT related:

· Answer the who, what, and why (tell the story, not just “Support to the Warfighter”)

· Provide the TAT Number and sponsoring organization

· What role the IAC is playing (developed analysis, demonstration or assisted in…)

CORE: If the WAR is CORE related:

· Identify Technical Inquiry, SA, training, etc.

Foreign Visitors/Travel: When reporting on foreign visitors/travel, include who authorized the visit/travel (TAT Requesting Activity, Core from IAC PMO through proper channels, etc.)

E. All IACs, including IAC field office personnel who prepare and submit WARs, must use the submission standard shown below. Periodically, the DTIC IAC PMO will update the standard and the latest revision will follow. Ensure that all personnel in your organizations have a copy of the standard for their use in preparing WAR entries.

V.

DTIC IAC PROGRAM WAR SUBMISSION STANDARD:

A.

THE WRITER’S RESPONSIBILITY

1. WRITE AND EDIT FOR YOUR AUDIENCE - Science & Technology Community including the Director of Defense Research & Engineering. Write to tell the story, results, and implications. Produce condensed and meaningful information; concisely stated facts are best. Anticipate questions (e.g., completion dates, completed solutions to challenges). See paragraph D above.

2. WRITE ABOUT THIS WEEK'S (Wednesday to Thursday)

ACCOMPLISHMENTS ONLY. Write about accomplishments that have occurred during the reporting period.

3. KEEP YOUR ENTRIES FACTUAL AND TO THE POINT. USE PLAIN ENGLISH. Limit entries to 20 lines were possible. Entries containing acronyms may be longer given the requirement to spell out acronyms when first referenced.

4. USE THE CORRECT ENTRY FORMAT - TITLE, TEXT, AND POC

a. Title. Bold, all capitals, catch interest (e.g., NETWORK DEPLOYMENT FOR SOCOM) and end with a period. Do not use your IAC NAME in the title, spell out IAC name in Text.

b. Text. One continuous block of text as described in this submission standard with one space between sentences, no carriage returns. Do not underline text.

c. POCs: Name/Organization/Telephone Number/email.

IAC PMA: Mr./Ms./A. Example/DTIC-AI/703-767-XXXX/…..@dtic.mil

IAC POC: Mr./Ms./Dr. A. Example/IAC/703-XXX-XXXX/….@iac.mil…..

Note that the examples are separated by slashes and there is no period at the end of the POC identification.

d. LEFT JUSTIFY ENTRIES. Self-Explanatory.

e. USE THE TIMES NEW ROMAN 12-POINT FONT (Agency Standard).

f. USE DATES IF AVAILABLE. Use the day and three-letter initial capital month indicator only (e.g., 3 Jan 02). If the date you cite is outside the current calendar year, use the day, three-character month, and four characters for year (e.g., 3 Jan 2000).

g. USE TITLES, NOT NAMES. Use titles such as OUSD(S&T), AFRL, and

JFCOM (J2). Do not use names since people move on and titles generally remain the same.

h. USE EASILY RECOGNIZED ACRONYMS – S&T, STI, SIPRNET, NIPRNET, INFOSEC, IBM, GTE, GE. Do not assume that higher-level officials will recognize acronyms you use regularly. Spell out acronyms if they are application specific, could be confused with another acronym, or not a matter of common knowledge.

i. DO NOT TRY TO RESOLVE AN ISSUE OR LEVEL PRAISE WITH THE WAR. The WAR should never be used as a mechanism to communicate challenges or opinions; these items should be communicated via your IAC PMA.

Similarly, do not level praise in your WAR entries. Detail dollar savings, cost avoidance, time saved, etc., but remember that a solid accomplishment is more impressive than saying someone was very happy with what you did.

j. IN GENERAL, when you write about meetings and briefings, write about significance, results, and implications, NOT OCCURRENCES.

_1289120467.xls

SNIM

1 FA4600-09-D-XXXX 09-0014/0001 0001 Example of title of task to completed for this effort DTIC DD-MMM-YYYY DD-MMM-YYYY $ 1,000,000.00 $ 100,000.00 $ 35,000.00 35% $ 65,000.00 $ 10,000.00 1% $ 5,000.00 5% Ahead TS/SCI Open 55.0 2.0 1 0 1 0 0

2 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

3 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

4 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

5 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

6 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

7 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

8 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

9 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

10 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

11 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

12 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

13 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

14 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

15 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

16 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

17 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

18 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

19 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

20 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

21 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

22 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

23 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

24 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

25 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

26 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

27 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

28 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

29 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

30 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

31 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

32 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

33 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

34 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

35 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

36 $ - 0 $ - 0 $ - 0 0% $ - 0 $ - 0 0% $ - 0 0% * * 0 0 0 0 0

GRAND TOTALS: $ 1,000,000.00 $ 100,000.00 $ 35,000.00 $ 65,000.00 $ 10,000.00 1% $ 5,000.00 5% 55.0 1 0 1 0 0

Total Orders

Total Open Orders 1

Total Closed Orders 0

Total Orders On Schedule 0

Total Orders Ahead of Schedule 1

Total Orders Behind Schedule 0

&CSNIM MONTHLY CONTRACT TRACKING REPORT

CONTRACTOR: _____________&R&D

&RCDRL-A002

Sheet2

Sheet3

_1289117439.xls Month 1

DTIC Information Analysis Center - SNIM IDIQ Monthly Metrics

Month 2

DTIC Information Analysis Center - SNIM IDIQ Monthly Metrics

Month 3

DTIC Information Analysis Center - SNIM IDIQ Monthly Metrics