Draft
5/196/10/2004July
2004
OP-34--Fund Support for Selected Quality of Life
ActivitiesJMIP/TIARA
Intelligence
Projects
–
-
Documents
|
|
Org
|
DocType |
A. General:
The
purpose
of this
Program Data
Requirements
(PDR)DR format is to identify
“documents”
that
are
collected in support of the
Integrated
Program
and Budget review
(IPBR)/BES
and/or the Congressional
Justification Book (CJB)
(transmittal
memorandums,
introductions,
forewards,
project
graphics and
security
classification
guides).
This
PDR provides the vehicle to identify the list of documents
required
by OUSD(I)
and
centralizes
collection and storage of documents
which
support
JMIP/TIARA resources and
narratives.
B.
Requirements:
1.
JMIP Program Managers
and TIARA Services will submit the following documents via SNaP for their
respective areas of
responsibility. Documents are
required
for the President’s Budget to support the publication of the JMIP/TIARA
CJB. Submission of these documents
is optional for the
POMIPBR/BES
submission:
a.
JMIP
(Volume
II) and TIARA
(Volume
III)
Introductions
b.
Graphics for each
project
c.
Validation
memorandum
2.
DGIAP
office
will submit the Volume II Foreward for
DGIAP
for the President’s Budget Submission/CJB
publication.
3.
Each
submitting organization will submit a memorandum or security classification
guide which addresses the resource and narrative data submitted to OUSD(I)
for JMIP and TIARA. Document
must be coordinated with appropriate security office prior to
submission and
requires a one star General Officer level or higher
signature.
Required with each
submission.
CA.
Instructions:
1.
To
submit
documents:
1.
1.
21.
Instructions
for
Completing
1.
Volume
2
and
3
Introductions,
Graphics,
Certification;
1.
JMIP
Program Managers and TIARA Services will submit the following documents via
SNaP for their respective areas of
responsibility. Volume II and III Introductions, Graphics, and Validation
Memorandum.
1.
DGIAP
Office will submit the Volume II Foreward for DGIAP via
SNaP.
1.
1.
To submit the
Introductions, Graphics and
Foreward:
a.
Click the
Volume II
Forward:
JMIP
Program Managers and TIARA Services will submit the
Introduction
and Graphics
for
their respective areas of responsibility
by
selecting
“Enter
Data”
button
on the
SNapP
menu.
b.
Then
sSelect
“JMIP/TIARA
DocumentsJMIP/TIARA
Documents”
and press “Submit
File”.
c.
In the Documents
window, select
the title of the document
from the
“Title” field
and then use
“Browse”
button to
locate the file on the local server.
The user may also type in the path and
file
name in the
“File”
field.
When the “Submit”
button has been pressed, the file will be copied to the
SNapP
server. The user may view the file
by
clicking on
the title of the
document
to be
viewedin
the lower part of the
screen.pasting
the information into designated SNap
menu. Select “Other Docs
and make a selection from the pull-down
menu. Type or paste the text/graphic
as appropriate.
Refer to the
“Definitions” section for further
clarification.
1.
Refer
to the “Definitions” section for further
clarification.
1.
1.
2.
The Resource
Summary section of Volume I is
not required for the Integrated Program Budget Review
submission.
1.
The
Validation
Memorandum will be submitted
by clicking the “Other Docs” button and following instructions
in
paragraph
c
above.
2.
3. Documents
submitted
will be either
a graphic or a Microsoft Word
document (see
Definitions below for
clarification).
3. Instructions for Completing Volume 1 Resource
Summary: The FY 06/07 Volume I – Resource Summary, Volume II
and
III
baseline is preloaded to SNaP for development of the FY 06
CJB. Volume I, Resource Summary
is prepared by the Services for TIARA and by the PMs for
JMIP. Each TIARA Service and JMIP PM updates this data in SNap
to reflect information for FY 06/07 President’s
Budget. The information you supply constitutes the Volume I, Resource
Summary.
“Other
Docs”:
B.
Definitions
1.
Table of
Contents
--
OUSD(I)
generates the Table of Contents.
It will reflect the various sections, the appropriate page numbers,
and
inividualindividual
projects.
2.
Foreword--: The Foreword consists of a brief statement describing
the goal(s) of the DGIAP program manager’s JMIP activities. It also
describes the objectives of the CJB submission, its organization, and its
relationship to other books and program justifications.
The Foreword file format
must be Microsoft Word.
3.
Introduction
--:
The Introduction is a
narrative that addresses trends, direction, accomplishments, and contributions
of TIARA or JMIP activities to defense
intelligence. Avoid organizational
and management ‘boilerplate’
information. Program managers
should orient the Introduction to the program and focus on the value added
of their management activities.
The
ForewordIntroduction file format must be Microsoft
Word.
64.
Graphic:
--: Each project must include a graphic. The previous
year’s graphics are used unless changes to the project necessitate a
change in the graphic.
New
graphics must meet the specifications listed below or they will be returned
to the appropriate Service/Agency
representatives. Returned graphics
include an explanation of how the graphic does not meet the
specification. The Service/Agency
must resubmit a graphic that repairs the stated problem(s) by the required
deadline. All submitted graphics must meet these
specifications:
1.
Provide a photograph, artist’s rendering or a
schematic.
2.
The graphic must enhance the description of the
program. When project sensitivity
precludes using a descriptive graphic, submit the appropriate Service or
Agency seal.
3.
As a general rule of thumb, keep originals clean and simple, and
use large print.
4.
The graphic may be in color, black and white line art, or continuous
tone, but MUST be printable in black and white.
5.
The graphic may use a maximum of 256 colors (fewer colors is acceptable
since it is printed in black and white).
6.
The graphic must be sized and proportioned to
5”x7”.
7.
The graphic file size cannot be greater than
500KB (it is
preferred that the graphic file size be less than 250KB).
1.
The graphic file format must
be
either.
1.
GIF
(Graphic Interchange Format
(*.GIF)),
orbe
8.
JPEG
(Joint Photographic Experts Group File Interchange Format
(*.JPG)).
1.
9.
Suggestions
for creating your graphics so they meet the
specifications:
a.
Use a graphics product to create/modify your graphic to meet the
above specifications. Using PowerPoint typically does not produce a graphic
that meets the specifications.
b.
Print
your graphic on a black and white printer (such as a laser printer) to ensure
its quality in black and white.
c.
Use a graphics program to specify 256 colors (or
less). Minimizing the number
of colors make your file smaller.
d.
Most graphics programs provide a grid that allow you to easily crop
and/or resize your graphic to 5” x 7”.
e.
When
saving your graphic, use the
“File”
–
“Save As”
option.. Check that the file type chosen is
either
GIF or
JPEG,
and that the
file extension
is
either .gif or
.jpg.
Validation
Memo:
Each organization submitting
resource
and CJB narrative
data
is required
to notify OUSD(I)
that the submission is complete, accurate and consistent with all other budget
related information submitted to
OSD.
This notification
must be documented
by a memorandum validating the content and resource accuracy of the FY 06/07
resource and CJB submission. The
memorandum requires the JMIP
Program
Manager
or a one star General Officer level or higher certification
signature.
5.
Organization--:
The
agency responsible
for submitting applicable documents for inclusion in Volume II and
III (Closed
List):
Army
CIFA
ODASD(CN)
DIA
Navy
NGA
NSA
OUSD(I)
USAF
USMC
USSOCOM
6.
Document
Type--:
(Closed
List)
This is
a closed list that will be modified by OUSD (I) upon approval of
changes.
The
types
of documents
that Organizations
must
submit: (Closed
List):
Organization |
Document
Type |
Army |
Graphic for ACS
Graphic
for ARL
Graphic
for ASAS
Graphic
for CHIMS
Graphic
for CST
Graphic
for
D_RSTA
Graphic for
DFLP
Graphic for
FCS
Graphic for
FMA&E
Graphic for
GIST
Graphic
for
GRCS
Graphic for
IFS
Graphic for
IMETS
Graphic for
ISS
Graphic for
JSTARS
Graphic
for
JTAGS
Graphic for
JTC_SIL
Graphic for
JTT
Graphic for
MG
Graphic for
NGI
Graphic for
PROPHET
Graphic for
RI
Graphic for
RT-TI
Graphic for
STUAV
Graphic for
TCF
Graphic for
TCSA
Graphic
for
TENCAP_CB
Graphic for
TENCAP_PSS
Graphic for
TES
Graphic for
TROJAN
Validation
Memo for
Army
Security
Document
for Army
JMIP and
TIARA |
CIFA |
Graphic
for
CIAI
Graphic for
CIIP
Graphic for
CIMS
Graphic for
JCAG
Graphic
for
RTP
Vol
Validation
Memo for
DJCIP
Security
Document for
CIFA and
DJCIP |
DASD(CN) |
Graphic
for
CN_AIS
Graphic for
CN_IAS
Graphic
for
CN_IT
Graphic for
CN_PN
Graphic for
CN_SA
Graphic for
CN_SC&P
Graphic for
CN_SOS
Graphic for
CN_US
Validation
Memo for
DICP
Security
Document for
DICP |
DIA |
Graphic
for
FL
Graphic for
ICE
Graphic for
ISCOP
Graphic for
ISHDBT
Graphic for
JDISS
Graphic for
JPPR
Graphic for
JRIP
Graphic for
JTF-GTMO
Graphic for
MASINT
Graphic for
TS
Vol II DGIAP
Forward
Vol
Vol
Validation
Memo for
DITP
Security
Document for
DIA and
DITP |
NAVY |
Graphic
for
ADS
Graphic for
BAMS
Graphic
for
BEARTRAP
Graphic for
CDS
Graphic for
CJR
Graphic for
CST
Graphic for
CW
Graphic for
DFLP
Graphic for
EP-3E_ARIES_II
Graphic for
FA-18_RC
Graphic for
FSS
Graphic for
FTI_DPL
Graphic for
GCCS-M
Graphic
for
GIST
Graphic for
ISS
Graphic for
IW-EXPLOIT
Graphic for
JTAGS
Graphic for
JTT
Graphic for
MIS
Graphic for
NAVSPASUR
Graphic for
NCIRF
Graphic for
SHARP
Graphic for
SPA
Graphic for
SSEP
Graphic
for
SURTASS
Graphic for
TCS
Graphic for
TENCAP
Graphic for
TIS
Graphic for
UAVCOP
Graphic
for
VTUAV
Vol
Vol
III
Validation
Memo for
Navy
Security
Document for
Navy JMIP and
TIARA |
NGA |
Graphic
for
A&DS
Graphic for
AA
Graphic for
AMS
Graphic for
AP
Graphic for
ARCH
Graphic for
ARD
Graphic for
BSA
Graphic
for
BT
Graphic for
CI
Graphic for
DAI
Graphic for
DFAS_SPT
Graphic for
EE
Graphic for
EO
Graphic for
ERM
Graphic for
ES
Graphic for
FEA
Graphic for
FIAAI
Graphic for
FS
Graphic for
FWS
Graphic for
GIADO
Graphic for
HI
Graphic for
HR
Graphic for
IA
Graphic
for
IDS
Graphic for
INST
Graphic for
JMTK
Graphic for
MRP
Graphic for
MS
Graphic for
NDI
Graphic for
NSGI_ESE
Graphic for
OPS
Graphic for
OS
Graphic for
PINSS
Graphic for
PS
Graphic for
PURCH
Graphic for
RRS
Graphic for
SBR
Graphic for
SEC
Graphic for
SI
Graphic
for
SS
Graphic for
STOM
Graphic for
TACTD
Graphic for
TD
Graphic for
TI
Graphic for
TN
Graphic for
TSA
Vol
Validation
Memo for
DGP
Security
Document for
NGA and
DGP |
NSA |
Graphic
for
ACS
Graphic
for
ANPRD-13
Graphic for
AOCO
Graphic for
ARL
Graphic for
ASSI
Graphic for
ATI
Graphic for
BGPHES
Graphic for
CDS
Graphic for
CEMO
Graphic for
CHALS-X
Graphic for
COMPVER
Graphic for
GRCS
Graphic for
JTACSIG
Graphic for
JTWS
Graphic for
MEWSS_PIP
Graphic for
NTIOS
Graphic for
PH
Graphic
for
PROFORMA
Graphic for
PROPHET
Graphic for
RBM
Graphic for
RREP
Graphic for
SCSSI
Graphic for
SIGEXP
Graphic for
SPECSIGEXP
Graphic for
STA
Graphic for
SWTOOLS
Graphic for
TCAC
Graphic for
TERPES
Graphic for
TPCS-MPC
Graphic for
TSP
Graphic for
TST
Validation
Memo for
DCP
Security
Document for
NSA and
DCP |
OUSD(I) |
Graphic
for
ASAP
Graphic for
CENTRIXS
Graphic for
DHIP1
Graphic for
DHIP2
Graphic for
DHIS
Graphic for
DKT
Graphic for
FMA&E
Graphic for
HCS
Graphic for
HF
Graphic for
IBS
Graphic
for
INTEL_MGT
Graphic for
ISIO
Graphic for
JET
Graphic for
STS
Graphic for
TECH_DEV
Graphic for
TTP
Vol
Vol
Validation
Memo for
DHIP
Validation
Memo for
DISTP
Security Document for
OSD,
DHIP and
DISTP |
USAF |
Graphic
for
ARGUS
Graphic for
ATS
Graphic for
CAIS
Graphic for
CCICA
Graphic for
CDL
Graphic for
CST
Graphic for
DCGS
Graphic for
DFLP
Graphic
for
DSP
Graphic for
GH
Graphic for
GIST
Graphic for
IAD
Graphic for
IE
Graphic for
IMA
Graphic for
ISS
Graphic for
JTT
Graphic for
MAIS
Graphic for
NUDET
Graphic for
P_MAE_UAV
Graphic
for
PODREC
Graphic for
RC-135
Graphic for
SAISA
Graphic for
SBIRS_H
Graphic for
SBR
Graphic for
SS
Graphic for
TCP_RG
Graphic for
TENCAP
Graphic for
TIP
Graphic for
U-2
Validation
Memo for
USAF
Security
Document for
USAF JMIP and
TIARA |
USMC |
Graphic
for
CDS
Graphic for
CESAS
Graphic for
CH
Graphic for
COBRA
Graphic
for
CST
Graphic for
DFLP
Graphic for
GCCS-I3
Graphic for
GIST
Graphic for
IAS
Graphic for
ISR
Graphic for
ISS
Graphic for
JSC
Graphic for
JTT
Graphic for
MANPACK_SIDS
Graphic for
MC_RIP
Graphic
for
MEWSS_PIP
Graphic for
PIONEER
Graphic for
RREP
Graphic for
SURSS
Graphic for
TACPHOTO
Graphic
for
TCAC
Graphic for
TEG
Graphic for
TENCAP
Graphic for
TERPES
Graphic for
TIS
Graphic for
TPC
Graphic for
TPCS-MPC
Graphic for
TRSS
Graphic for
TS_LITE
Graphic for
TSCM
Validation
Memo for
USMC
Security
Document for
USMC JMIP and
TIARA |
USSOCOM |
Graphic
for
CAPS
Graphic for
ISP
Graphic for
ISS
Graphic for
JTWS
Graphic
for
MMATT
Graphic for
NF
Graphic for
NSS
Graphic for
OPUS
Graphic
for
SOCRATES
Graphic for
SOFIFS
Graphic for
SOJICC
Graphic for
SOTVS
Graphic for
TACLAN
Validation
Memo for
SOCOM
Security
Document for
SOCOM JMIP and
TIARA |
Instructions:
1)
Previously, this data has been collected by OUSD(I) through a separate
data call.
OUSD(I)
will request dual reporting for the minimum number of submissions possible,
until migration to SNaP collection has been proven successful. Migrating
the collection of JMIP and TIARA to SNaP will provide increased visibility
to both the submitters and OSD
staff.
2) The purpose of this PDR
format is to collect JMIP/TIARA documents
needed
to
review
JMIP and TIARA resources and to
publisch the
Budget Congressional Justification Book (Vol I, II and
III).
3)
Documents will be either a graphic or word
document.
4)
Specific instructions for graphics areas
follows: Each project must include
a graphic. The previous
year’s graphics are used unless changes
to the project necessitate a change in the
graphic. New graphics must meet the specifications listed
below or they will be returned to the appropriate Service/Agency
representatives. Returned graphics
include an explanation of how the graphic does not meet the
specification. The Service/Agency
must resubmit a graphic that repairs the stated problem(s) by the required
deadline. All submitted graphics must meet these
specifications:
a.
Provide a photograph, artist’s rendering or a
schematic.
b.
The graphic must enhance the description of the
program. When project sensitivity
precludes using a descriptive graphic, submit the appropriate Service or
Agency
seal.
c.As
a general rule of thumb, keep originals clean and simple, and use large
print.
c.The
graphic may be in color, black and white line art, or continuous tone, but
MUST be printable in black and
white.
e.
The graphic may use a maximum of 256 colors (fewer colors is acceptable
since it is printed in black and
white).
f.
The graphic must be sized and proportioned to
5”x7”.
g.
The graphic file size cannot be greater than 500KB(it is preferred
that the graphic file size be less than
250KB).
h.
The graphic file format must be
either.
(1) GIF (Graphic
Interchange Format (*.GIF)),
or
(2)
JPEG (Joint Photographic Experts Group File Interchange Format
(*.JPG)).
i.
Suggestions
for creating your graphics so they meet the
specifications:
(1)
Use a graphics product to create/modify your graphic to meet the above
specifications. Using PowerPoint typically does not produce a graphic that
meets the
specifications.
(2)
Print your graphic on a black and white printer (such as a laser printer)
to ensure its quality in black and
white.
(3)
Use a graphics program to specify 256 colors (or
less). Minimizing the number of colors make your file
smaller.
(4)
Most graphics programs provide a grid that allow you to easily crop
and/or resize your graphic to 5” x
7”.
(5)
When saving your graphic, use the “File” – “Save
As” option.. Check that
the file type chosen is either GIF or JPEG, and the file extension is either
.gif or
.jpg.
Definitions:
Org:
(Closed
List.) Organizations
responsible for submitting applicable documents for inclusion in the BCJ
Book (Vol I, II and
III).
Army
CIFA
DASD(CN)
DIA
Navy
NGA
OUSD(I0
USAF
USMC
USSOCOM
DocType: (Closed List.)
Specific documents types used to construct the BCJ
Book.
Data Matrix: Org to DocType
Relationship
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Business
Rules:
N/A
Subject Matter Experts:
Questions regarding this
data requirement should be directed to POC Diane McGibbon, OUSD(I) Pentagon
1A875, Com 703-692-5330 email
address Diane.McGibbon@osd.mil or POC Alternate Phyllis Axtell, OUSD(I)
703-692-5186 email address
Phyllis.Axtell@osd.mil
or via the SIRS
button on the SNaP web site:
https://snap.pae.osd.smil.mil
(select
functional issue).
Technical
Issues:
If you are having
difficulty with the data collection
system—SNaP, contact the SNaP administrators via the SIRS button on
the SNaP web site:
https://snap.pae.osd.smil.mil or call
703-604-6349.
Business
Rules:
N/A
Subject
Matter Experts:
Questions
regarding this data requirement should be directed to
POC and
POCAlternate.
Technical
Issues:
If
you are having
difficulty
with
the data collection system—SNaP, contact the SNaP administrators via
the SIRS button on the SNaP web site:
https://snap.pae.osd.mil or call (703)
604-6349.