This document establishes policy and assigns responsibilities for the Joint Reserve Intelligence Program (JRIP) and joint reserve intelligence centers (JRICs). It reissues and renumbers a prior instruction to plan, implement, execute, and integrate JRIP activities throughout the Department of Defense. It assigns the Under Secretary of Defense for Intelligence and the Director of the Defense Intelligence Agency primary oversight and management responsibilities for JRIP.
The Guidelines on the Incident Response System (IRS) are issued by the
National Disaster Management Authority (NDMA) under Section 6 of the
DM Act, 2005 for effective, efficient and comprehensive management of
disasters in India. The vision is to minimize loss of life and property by
strengthening and standardising the disaster response mechanism in the
country.
Though India has been successfully managing disasters in the past,
there are still a number of shortcomings which need to be addressed. The
response today has to be far more comprehensive, effective, swift and well
planned based on a well conceived response mechanism.
Realisation of certain shortcomings in our response system and a desire
to address the critical gaps led the Government of India (GoI) to look at
the world’s best practices. The GoI found that the system evolved for firefighting
in California is very comprehensive and thus decided to adopt
Incident Command System (ICS).
In view of the provisions of the DM Act, 2005, NDMA felt that authoritative
Guidelines on the subject, with necessary modifications to suit the Indian
administrative setup, were essential. To meet this need, a core group of
experts was constituted and four regional consultation workshops were
conducted. It was ensured that representatives of the State Governments
and MHA participate and their views given due consideration. Training
Institutes like the LBSNAA, NIDM and various RTIs / ATIs along with National
core trainers also participated. The adaptation of ICS by other countries
was also examined. The draft prepared was again sent to all States, UTs and
their final comments were obtained and incorporated. A comprehensive set
of Guidelines has thus been prepared and is called the Incident Response
System (IRS)
The Guidelines on the Incident Response System (IRS) are issued by the
National Disaster Management Authority (NDMA) under Section 6 of the
DM Act, 2005 for effective, efficient and comprehensive management of
disasters in India. The vision is to minimize loss of life and property by
strengthening and standardising the disaster response mechanism in the
country.
Though India has been successfully managing disasters in the past,
there are still a number of shortcomings which need to be addressed. The
response today has to be far more comprehensive, effective, swift and well
planned based on a well conceived response mechanism.
Realisation of certain shortcomings in our response system and a desire
to address the critical gaps led the Government of India (GoI) to look at
the world’s best practices. The GoI found that the system evolved for firefighting
in California is very comprehensive and thus decided to adopt
Incident Command System (ICS).
In view of the provisions of the DM Act, 2005, NDMA felt that authoritative
Guidelines on the subject, with necessary modifications to suit the Indian
administrative setup, were essential. To meet this need, a core group of
experts was constituted and four regional consultation workshops were
conducted. It was ensured that representatives of the State Governments
and MHA participate and their views given due consideration. Training
Institutes like the LBSNAA, NIDM and various RTIs / ATIs along with National
core trainers also participated. The adaptation of ICS by other countries
was also examined. The draft prepared was again sent to all States, UTs and
their final comments were obtained and incorporated. A comprehensive set
of Guidelines has thus been prepared and is called the Incident Response
System (IRS)
Department of Defense Instruction 5143_DUSD Intelligence 24Oct14Tom "Blad" Lindblad
Reissues DoD Directive (DoDD) 5143.01 (Reference (a)) to update the responsibilities and functions, relationships, and authorities of the USD(I), pursuant to the authority vested in the Secretary of Defense (SecDef) by sections 113 and 137 of Title 10, United States Code (U.S.C.) (Reference (b)), and in accordance with section 3001 et seq. of Title 50, U.S.C. (Reference (c)), as well as Public Law 108-458 (Reference (d)), Executive Order (E.O.) 12333 (Reference (e)), and E.O. 13470 (Reference (f)).
Department of Defense INSTRUCTION NUMBER 5000.02 Jan.docxsimonithomas47935
Department of Defense
INSTRUCTION
NUMBER 5000.02
January 7, 2015
USD(AT&L)
SUBJECT: Operation of the Defense Acquisition System
References: See References
1. PURPOSE. This instruction:
a. In accordance with the authority in DoD Directive 5000.01 (Reference (a)), reissues the
interim DoD Instruction 5000.02 (Reference (b)) to update established policy for the
management of all acquisition programs in accordance with Reference (a), the guidelines of
Office of Management and Budget Circular A-11 (Reference (c)), and References (d) through
(ce).
b. Authorizes Milestone Decision Authorities (MDAs) to tailor the regulatory requirements
and acquisition procedures in this instruction to more efficiently achieve program objectives,
consistent with statutory requirements and Reference (a).
2. APPLICABILITY. This instruction applies to OSD, the Military Departments, the Office of
the Chairman of the Joint Chiefs of Staff and the Joint Staff, the Combatant Commands, the
Office of the Inspector General of the Department of Defense, the Defense Agencies, the DoD
Field Activities, and all other organizational entities within the DoD (referred to collectively in
this instruction as the “DoD Components”).
3. POLICY. The overarching management principles and mandatory policies that govern the
Defense Acquisition System are described in Reference (a). This instruction provides the
detailed procedures that guide the operation of the system.
4. RESPONSIBILITIES
a. Defense Acquisition Executive (DAE). The DAE is the Under Secretary of Defense for
Acquisition, Technology, and Logistics (USD(AT&L)). The DAE will act as the MDA for
Major Defense Acquisition Programs (MDAPs) and Major Automated Information System
(MAIS) programs. In accordance with Table 1 in Enclosure 1 of this instruction, the DAE may
DoDI 5000.02, January 7, 2015
2
delegate authority to act as the MDA to the head of a DoD Component, who may further
delegate the authority to the Component Acquisition Executive (CAE). The DAE may also
delegate MDA authority to another OSD official as the DAE considers appropriate.
b. MDA. The MDA will establish procedures for assigned programs using this instruction
as guidance. MDAs should limit mandatory procedures applicable to all assigned programs so as
to not exceed the requirements for MDAPs or MAIS programs and other acquisition programs
governed by this instruction or DoD Directive 5000.01 (Reference (a)). MDAs should tailor
regulatory procedures in the document consistent with sound business practice and the risks
associated with the product being acquired.
c. Heads of the DoD Components. The DoD Component Head will implement the
procedures in this instruction and Reference (a). Component-required procedures will not
exceed those specified in this instruction. When necessary, waivers or requests for exceptions to
the provisions of this instructio.
Department of Defense Instruction 5143_DUSD Intelligence 24Oct14Tom "Blad" Lindblad
Reissues DoD Directive (DoDD) 5143.01 (Reference (a)) to update the responsibilities and functions, relationships, and authorities of the USD(I), pursuant to the authority vested in the Secretary of Defense (SecDef) by sections 113 and 137 of Title 10, United States Code (U.S.C.) (Reference (b)), and in accordance with section 3001 et seq. of Title 50, U.S.C. (Reference (c)), as well as Public Law 108-458 (Reference (d)), Executive Order (E.O.) 12333 (Reference (e)), and E.O. 13470 (Reference (f)).
Department of Defense INSTRUCTION NUMBER 5000.02 Jan.docxsimonithomas47935
Department of Defense
INSTRUCTION
NUMBER 5000.02
January 7, 2015
USD(AT&L)
SUBJECT: Operation of the Defense Acquisition System
References: See References
1. PURPOSE. This instruction:
a. In accordance with the authority in DoD Directive 5000.01 (Reference (a)), reissues the
interim DoD Instruction 5000.02 (Reference (b)) to update established policy for the
management of all acquisition programs in accordance with Reference (a), the guidelines of
Office of Management and Budget Circular A-11 (Reference (c)), and References (d) through
(ce).
b. Authorizes Milestone Decision Authorities (MDAs) to tailor the regulatory requirements
and acquisition procedures in this instruction to more efficiently achieve program objectives,
consistent with statutory requirements and Reference (a).
2. APPLICABILITY. This instruction applies to OSD, the Military Departments, the Office of
the Chairman of the Joint Chiefs of Staff and the Joint Staff, the Combatant Commands, the
Office of the Inspector General of the Department of Defense, the Defense Agencies, the DoD
Field Activities, and all other organizational entities within the DoD (referred to collectively in
this instruction as the “DoD Components”).
3. POLICY. The overarching management principles and mandatory policies that govern the
Defense Acquisition System are described in Reference (a). This instruction provides the
detailed procedures that guide the operation of the system.
4. RESPONSIBILITIES
a. Defense Acquisition Executive (DAE). The DAE is the Under Secretary of Defense for
Acquisition, Technology, and Logistics (USD(AT&L)). The DAE will act as the MDA for
Major Defense Acquisition Programs (MDAPs) and Major Automated Information System
(MAIS) programs. In accordance with Table 1 in Enclosure 1 of this instruction, the DAE may
DoDI 5000.02, January 7, 2015
2
delegate authority to act as the MDA to the head of a DoD Component, who may further
delegate the authority to the Component Acquisition Executive (CAE). The DAE may also
delegate MDA authority to another OSD official as the DAE considers appropriate.
b. MDA. The MDA will establish procedures for assigned programs using this instruction
as guidance. MDAs should limit mandatory procedures applicable to all assigned programs so as
to not exceed the requirements for MDAPs or MAIS programs and other acquisition programs
governed by this instruction or DoD Directive 5000.01 (Reference (a)). MDAs should tailor
regulatory procedures in the document consistent with sound business practice and the risks
associated with the product being acquired.
c. Heads of the DoD Components. The DoD Component Head will implement the
procedures in this instruction and Reference (a). Component-required procedures will not
exceed those specified in this instruction. When necessary, waivers or requests for exceptions to
the provisions of this instructio.
Chapter IIJP 5-0CSAs, and applicable DOD agencies for preparatJinElias52
Chapter II
JP 5-0
CSAs, and applicable DOD agencies for preparation of plans based on current military capabilities. It implements the planning guidance provided in the GEF and the joint planning activities and products that accomplish that guidance. In addition to communicating to the CCMDs’ specific planning guidance necessary for planning, the JSCP operationalizes the strategic vision described in the NMS and nests with the strategic direction delineated by the NSS, DSR, and the DOD’s planning and resourcing guidance provided in the GEF. The JSCP also provides integrated planning guidance and direction for planners.
The JSCP is described in detail in CJCSI 3110.01, (U) 2015 Joint Strategic Capabilities Plan (JSCP).
e. GFMIG. The GFMIG documents force planning and execution guidance and show assignment of forces in support of the UCP. GFM aligns force assignment, apportionment, and allocation methodologies in support of the DSR and GEF, joint force availability requirements, and joint force assessments. It provides comprehensive insights into the global availability of US military resources and provides senior decision makers a process to quickly and accurately assess the impact and risk of proposed changes in force assignment, apportionment, and allocation. JS prepares the document for SecDef approval, with the Joint Staff J-8 [Director for Force Structure, Resource, and Assessment] overseeing the assignment and apportionment of forces and the Joint Staff J-3 [Operations Directorate] overseeing the allocation of forces. It is updated every two years and approved by SecDef. The GFMIG informs planners of the processes for distributing forces globally. It provides SecDef direction to the Secretaries of the Military Departments for assigning forces to CCDRs in order to accomplish their assigned missions, specifies the allocation process that provides access to forces and capabilities when assigned mission requirements exceed the capacity and/or capability of the assigned and currently allocated forces, includes apportionment guidance to facilitate planning, and informs the joint force structure and capability assessment processes. The assignment tables in the GFMIG and Forces for Unified Commands Memorandum serve as the record of force assignments. SecDef’s decision to allocate forces is ordered in the Global Force Management Allocation Plan (GFMAP).
See Appendix E, “Global Force Management,” for additional information and descriptions.
9. Combatant Commanders
a. Planning Organization. At the CCMD level, a joint planning group (JPG), operational planning group, or operational planning team (OPT) is typically established to direct planning efforts across the command, including implementation of plans and orders.
b. Strategic Estimate. The CCDR and staff, with input from subordinate commands and supporting commands and agencies, prepare a strategic estimate by analyzing and describing the political, military, economic, social, information, and i ...
US Navy Instruction Confirms Retirement of Nuclear Tomahawk Cruise MissileDaniel Ross
Although the U.S. Navy has yet to make a formal announcement that the nuclear Tomahawk land-attack cruise missile (TLAM/N) has been retired, a new updated navy instruction shows that the weapon is gone.
The evidence comes not in the form of an explicit statement, but from what has been deleted from the U.S. Navy’s instruction Department of the Navy Nuclear Weapons Responsibilities and Authorities (SECNAVINST 8120.1A).
While the previous version of the instruction from 2010 included a whole sub-section describing TLAM/N responsibilities, the new version published on February 15, 2013, contains no mentioning of the TLAM/N at all and the previous sub-section has been deleted.
1. Department of Defense
INSTRUCTION
NUMBER 3325.11
June 26, 2015
USD(I)
SUBJECT: Management of the Joint Reserve Intelligence Program (JRIP)
References: See Enclosure 1
1. PURPOSE. This instruction, in accordance with the authority in DoD Directive (DoDD)
5143.01 (Reference (a)):
a. Reissues and renumbers DoD Instruction (DoDI) 3305.8 (Reference (b)) to establish
policy and assign responsibilities for the JRIP and joint reserve intelligence centers (JRICs).
b. Incorporates and cancels DoDI 3305.07 (Reference (c)).
c. Plans, implements, executes, and integrates the JRIP and associated activities throughout
the DoD in accordance with DoDD 5105.21 (Reference (d)), DoDI 3300.05 (Reference (e)), and
DoDD 1200.17 (Reference (f)).
2. APPLICABILITY. This instruction applies to:
a. OSD, the Military Departments, including their Reserve Components (RCs) addressed in
paragraphs 2b and 2c, the Office of the Chairman of the Joint Chiefs of Staff (CJCS) and the
Joint Staff, the Combatant Commands (CCMDs), the Office of the Inspector General of the
Department of Defense, the Defense Agencies, the DoD Field Activities, and all other
organizational entities within the DoD (referred to collectively in this instruction as the “DoD
Components”).
b. The National Guard Bureau and National Guard intelligence personnel performing
operational support pursuant to sections 12301, 12302, 12304 and 12310 of Title 10, United
States Code (U.S.C.) (Reference (g)); or in accordance with section 502 of Title 32, U.S.C.
(Reference (h)) authority.
c. The Army Reserve, Navy Reserve, Air Force Reserve, Marine Corps Reserve, and United
States Coast Guard Reserve when the Coast Guard is operating as a Service of the Department of
the Navy.
2. DoDI 3325.11, June 26, 2015
2
3. POLICY. It is DoD policy that:
a. JRIP promotes and supports RC intelligence mobilization readiness, operational training,
and operational support requirements.
b. JRIP integrates, engages, and enables Reserve Military Intelligence (RMI) capabilities in
the Total Force to satisfy DoD intelligence requirements.
c. JRIP-associated facilities and information technology (IT) at JRICs or other JRIP-
associated locations are shared-use capabilities primarily for RMI training and operational
support requirements.
d. JRICs constitute a critical asset for reachback, distributed operations, and continuity of
operations (COOP) to support defense intelligence and DoD warfighter requirements across the
range of military operations. The use of JRICs is prioritized and deconflicted as needed.
e. JRICs are leveraged for DoD full-time use, COOP requirements, and appropriately-
cleared non-DoD interagency partners on a not-to-interfere basis with RMI activities.
f. JRIC capabilities will be incorporated into future service, joint, and allied intelligence
architectures, as appropriate.
4. RESPONSIBILITIES. See Enclosure 2.
5. RELEASABILITY. Cleared for public release. This instruction is available on the Internet
from the DoD Issuances Website at http://www.dtic.mil/whs/directives.
6. EFFECTIVE DATE. This instruction is effective June 26, 2015.
Marcel J. Lettre
Acting Under Secretary of Defense for
Intelligence
Enclosures
1. References
2. Responsibilities
Glossary
3. DoDI 3325.11, June 26, 2015
CONTENTS3
TABLE OF CONTENTS
ENCLOSURE 1: REFERENCES...................................................................................................4
ENCLOSURE 2: RESPONSIBILITIES.........................................................................................5
UNDER SECRETARY OF DEFENSE FOR INTELLIGENCE (USD(I))...............................5
DIRECTOR, DEFENSE INTELLIGENCE AGENCY (DIA)..................................................5
UNDER SECRETARY OF DEFENSE FOR PERSONNEL AND READINESS
(USD(P&R)) ........................................................................................................................7
ASSISTANT SECRETARY OF DEFENSE FOR RESERVE AFFAIRS (ASD(RA))............7
DEPARTMENT OF DEFENSE SENIOR INTELLIGENCE OVERSIGHT OFFICIAL (DoD
SIOO)...................................................................................................................................7
DoD COMPONENT HEADS....................................................................................................8
SECRETARIES OF THE MILITARY DEPARTMENTS........................................................9
CJCS ........................................................................................................................................10
GLOSSARY ..................................................................................................................................12
PART I: ABBREVIATIONS AND ACRONYMS ................................................................12
PART II: DEFINITIONS........................................................................................................13
4. DoDI 3325.11, June 26, 2015
ENCLOSURE 14
ENCLOSURE 1
REFERENCES
(a) DoD Directive 5143.01, “Under Secretary of Defense for Intelligence (USD(I)),”
October 24, 2014, as amended
(b) DoD Instruction 3305.8, “Management and Administration of the Joint Reserve
Intelligence Program (JRIP),” April 11, 2001, (hereby cancelled)
(c) DoD Instruction 3305.07, “Joint Reserve Intelligence Program (JRIP),” March 27, 2007,
(hereby canceled)
(d) DoD Directive 5105.21, “Defense Intelligence Agency (DIA),” March 18, 2008
(e) DoD Instruction 3300.05, “Reserve Component Intelligence Enterprise (RCIE)
Management,” July 17, 2013
(f) DoD Directive 1200.17, “Managing the Reserve Components as an Operational Force,”
October 29, 2008
(g) Title 10, United States Code
(h) Title 32, United States Code
(i) DoD Directive 5205.12, “Military Intelligence Program (MIP),” November 14, 2008
(j) DoD Directive 5142.01, “Assistant Secretary of Defense (Legislative Affairs)
(ASD(LA)),” September 15, 2006
(k) Executive Order 12333 “United States Intelligence Activities,” as amended
(l) DoD Directive 5240.01, “DoD Intelligence Activities,” August 27, 2007, as amended
(m) Joint Publication 1-02, “Department of Defense Dictionary of Military and Associated
Terms,” current edition
5. DoDI 3325.11, June 26, 2015
ENCLOSURE 25
ENCLOSURE 2
RESPONSIBILITIES
1. UNDER SECRETARY OF DEFENSE FOR INTELLIGENCE (USD(I)). The USD(I):
a. Serves as the principal advisor to the Secretary and Deputy Secretary of Defense on JRIP
matters.
b. Establishes overall policy and provides guidance, strategy, planning, oversight, and
resource advocacy.
c. Guides the integration of RMI efforts pertaining to intelligence mission development,
resourcing, tasking, and mission management.
d. Assesses the effectiveness of JRIP, JRIC operations, and the use of JRICs in support of
DoD intelligence and other operational requirements.
e. Oversees JRIP issues in the Military Intelligence Program (MIP) and National Intelligence
Program (NIP), in accordance with DoDD 5205.12 (Reference (i)).
f. Consults with the Assistant Secretary of Defense for Legislative Affairs as necessary to
ensure JRIP policies are in accordance with the DoD legislative program and strategy in
accordance with DoDD 5142.01 (Reference (j)).
2. DIRECTOR, DEFENSE INTELLIGENCE AGENCY (DIA). Under the authority, direction,
and control of the USD(I), in addition to the responsibilities in section 6 of this enclosure, in
accordance with Reference (d), and as the JRIP Program Manager (PM), the Director, DIA:
a. Establishes and sustains a JRIP Program Management Office (PMO) to manage JRIP and
JRIP-related planning, implementation, execution, administrative resourcing, integration,
financial, and logistical support, and full-time staffing requirements in accordance with
Reference (e).
b. Oversees the daily management of JRICs and JRIP IT.
(1) Addresses competing JRIP-associated facility, IT, mission support, and resource
requirements.
(2) Provides final approval authority on the designation of customer status to those
entities requesting access and use of JRICs.
(3) Designates, establishes, supports, and disestablishes JRIC sites with the concurrence
of the USD(I) and the Service component-hosted JRIC site.
6. DoDI 3325.11, June 26, 2015
ENCLOSURE 26
c. Provides JRIP implementing guidance to the DoD Components to ensure RMI programs
are coordinated and interoperable with JRIP.
(1) Coordinates inputs from DoD Components to ensure submissions are prioritized and
processed through a requirements system as appropriate.
(2) Ensures sub-unified command JRIP requirements are included in CCMD requirement
submissions.
d. Administers Defense Intelligence Enterprise requirements processes (e.g., Community
Online Intelligence System for End Users and Managers) to engage RMI elements with
validated, prioritized operational requirements.
e. Plans, programs, and executes resourcing for JRIP requirements and JRIC support of RMI
integration activities throughout the Defense Intelligence Enterprise in response to validated
requirements.
(1) Provides input to the USD(I) for MIP and NIP JRIP and JRIC requirements for the
planning, programming, and budgeting processes.
(2) Prioritizes and executes MIP and NIP funding, and leverages other resourcing.
(3) Coordinates the distribution of prioritized funds for reimbursement to the Services’
Reserve and National Guard pay and allowance accounts.
(4) Supports the USD(I) in defending JRIP requirements.
f. Resources, maintains, upgrades, expands, and if necessary, removes JRIP associated IT
communications, bandwidth, and other intelligence infrastructure installed at sites that are
accessible to RMI elements.
(1) Designs, implements, and resources a dynamic Intelligence Community (IC) network
and communications architecture responsive to DoD Component JRIP IT requirements.
(2) Maintains common JRIP IT capabilities, infrastructure, and connectivity at JRICs and
other JRIP-associated locations.
(3) Integrates JRIP IT systems, platforms, capabilities, connectivity, services and
management to common IT standards, as part of the larger defense enterprise.
(4) Coordinates with DoD Components to ensure operating compliance and
interoperability with IT systems that are shared with or co-located at JRICs.
(5) Coordinates with JRIC site owners to ensure a mutually supportive site
communications and systems plan is developed, agreed to by all parties, accredited, monitored
7. DoDI 3325.11, June 26, 2015
ENCLOSURE 27
and followed to accommodate JRIP and non-JRIP systems and infrastructure, and their access
and use.
g. Coordinates with and advises Service components, CCMDs, combat support agencies
(CSAs), and interagency partners on their participation in the JRIP and at JRICs.
h. Provides assistance with securing planning, programming, budgeting, and execution
actions.
i. Develops and executes memorandums of agreements (MOAs), memorandums of
understanding (MOUs), co-utilization agreements (CUAs) and, as necessary, inter-service
support agreements (ISSAs).
(1) Enters into MOAs with the Service components that specify roles, responsibilities,
and relationships for participation in JRIP and Service component hosting of designated JRICs or
other JRIP-associated capabilities.
(2) Provides implementing guidance and direction for JRIC use and site management.
(3) Oversees and ensures formal authorization of JRIC full-time use, COOP
requirements, or non-DoD users specifying a not-to-interfere basis with RMI activities.
j. Coordinates RMI mission requirements with the requisite DoD Components.
k. Keeps the USD(I) informed of the overall effectiveness of JRIP in support of
congressional inquires
3. UNDER SECRETARY OF DEFENSE FOR PERSONNEL AND READINESS
(USD(P&R)). The USD(P&R) coordinates changes in RC personnel-related policies and
programs with the USD(I) so that critical operational intelligence support missions to JRIP are
not impacted or limiting efficiencies throughout the Reserve Component Intelligence Enterprise
(RCIE) as part of the Total Force.
4. ASSISTANT SECRETARY OF DEFENSE FOR RESERVE AFFAIRS (ASD(RA)). Under
the authority, direction and control of the USD(P&R) and in addition to the responsibilities in
section 6, the ASD(RA) reviews, evaluates, and maintains oversight of the Services’ RCs
supported by the JRIP to ensure policies, plans, programs, and actions support Total Force
objectives.
5. DEPARTMENT OF DEFENSE SENIOR INTELLIGENCE OVERSIGHT OFFICIAL (DoD
SIOO). In accordance with Executive Order 12333 (Reference (k)) and DoDD 5240.01
(Reference (l)), the DoD SIOO provides independent oversight of all JRIP and JRIC-related
intelligence, intelligence-related activities, and counterintelligence activities.
8. DoDI 3325.11, June 26, 2015
ENCLOSURE 28
6. DoD COMPONENT HEADS. The DoD Component heads:
a. Integrate assigned or aligned RMI elements as part of the Total Force into JRIP and JRIC
capabilities to satisfy readiness, operational training, and operational support requirements.
b. Make the best use of JRIP and JRICs for reachback and other distributed training and
operational requirements.
c. Identify appropriate missions and engage RMI elements, in any duty status, for
operational requirements that can be performed at JRICs.
d. Assess the potential of and leverage JRICs to host Active Component (AC) full-time use
or COOP activities, as practicable, that satisfy validated intelligence requirements on a not-to-
interfere basis with RMI requirements.
e. Coordinate with the JRIP PM and the JRIC site owner to deconflict JRIC use with RMI
requirements and formalize appropriate, supportable relationships.
f. Provide mission management and oversight of their respective assigned or aligned RMI
and AC elements conducting operational training or operational support at JRICs or JRIP-
associated activities.
g. Engage JRIP-associated RMI elements through validated intelligence requirements
processes.
h. Leverage requirements processes to optimize and account for RMI operational support.
i. Coordinate with JRIP PM to identify prioritized JRIC IT requirements and MIP and NIP
operational support funding requirements to satisfy validated intelligence requirements, in
accordance with JRIP PM guidance.
j. Provide, support, maintain, and uninstall, when applicable, DoD Component-owned IT,
communications, bandwidth, applications, and other IT capabilities co-located at JRICs.
Coordinate IT requirements and actions with the JRIP PM.
k. Enter into MOAs, CUAs, and ISSAs with JRIP PM, as needed, which specify roles and
responsibilities for the co-location or integration of DoD Component IT system capabilities at
JRICs or JRIP-associated locations.
l. Provide implementing guidance to integrate DoD Component IT system capabilities into
JRIP-associated IT architecture, when practicable.
m. Enter into MOAs, CUAs, and ISSAs with the respective Service component JRIC host
and JRIP PM, as needed to:
9. DoDI 3325.11, June 26, 2015
ENCLOSURE 29
(1) Specify roles and responsibilities for RMI use of Service component-hosted JRICs or
JRIP-associated locations.
(2) Support AC full-time use or COOP requirements.
n. Provide yearly, or as needed, updates on DoD Component assigned or aligned RMI
capabilities, operations, and requirements that impact JRICs and JRIP-associated activities,
according to the Office of the Under Secretary of Defense for Intelligence (OUSD(I)), JRIP PM,
Service component, or ASD(RA) requirements.
7. SECRETARIES OF THE MILITARY DEPARTMENTS. In addition to the responsibilities
in section 6 of this enclosure, the Secretaries of the Military Departments:
a. Designate a senior official, (O-5/GG-14 or above), to attend JRIP meetings, boards, and
other forums to coordinate on JRIP-associated requirements and resourcing.
b. Coordinate internal Military Department issues that impact JRIP.
c. Provide full-time staff at all Service component-hosted JRICs sufficient to maintain full
operability of JRIC. Review staffing requirements annually and adjusts funding as needed.
d. Provide JRIP implementing guidance and direction to their respective Service components
and leverages JRIP and JRIC capabilities.
e. Ensure additional intelligence training is provided to accomplish JRIP-supported
intelligence missions as appropriate.
f. Address requirements to designate, establish, adjust, or disestablish Service component-
hosted sites as JRICs; conducts Service component manpower demographic data analysis, to
identify potential RMI requirements and inform JRIC growth consideration or expanded JRIP IT.
g. Operate and maintain designated Service component-hosted JRICs and JRIP-associated
capabilities to meet validated intelligence requirements for readiness training, full-time use,
COOP, crisis, and ongoing operational requirements.
(1) Provide adequate space, supporting staff, access, Service component IT and network
architecture, funding, and general base operations support (BASOPS) for Service component-
hosted JRICs on a non-reimbursable basis.
(a) Provide shared, reciprocal access to JRICs and JRIP-associated locations for RMI
activities of all Military Departments.
(b) Coordinate with JRIP Program Management Office and JRIC site user(s) to
address specific BASOPS requirements and funding responsibilities consistent with MOA
guidelines.
10. DoDI 3325.11, June 26, 2015
ENCLOSURE 210
(2) Plan, program, and execute resourcing for JRIC-associated infrastructure and facility
requirements.
(3) Provide and maintain responsibility for Service component IT networks, systems,
applications, communications security, and communications co-located at JRICs or operated in a
shared-infrastructure environment.
(a) Develop and implement mutually supportive JRIC site communications and
systems plans to accommodate JRIP and non-JRIP IT capabilities and architecture; ensures
system access to satisfy readiness training and operational requirements.
(b) Provide implementing guidance to integrate Service component IT capabilities
into JRIP IT architecture, wherever possible.
(4) Submit JRIC IT requirements to JRIP PM for Service component-associated
readiness training or operational support at designated JRICs for resourcing.
(5) Enable and support appropriately-cleared non-DoD interagency partners on a not-to-
interfere basis with RMI activities and DoD requirements, with the approval of the JRIP PM.
h. Enter into MOAs with the JRIP PM to specify roles, responsibilities, and relationships for
participation in JRIP and Service component hosting of designated JRICs or other JRIP-
associated capabilities.
i. Enter into MOAs, MOUs, CUAs, or ISSAs with requesting JRIC customer commands or
entities that specify roles and responsibilities for their use of Service component-hosted JRICs.
j. Provide yearly, or as needed, updates to JRIP PM and the OUSD(I) on Service component
RMI capabilities, operations, and requirements that impact JRICs and JRIP-associated activities.
8. CJCS. In addition to the responsibilities in section 6 of this enclosure, the CJCS:
a. Supports and facilitates the integration of RMI into Service component, CCMD, and sub-
unified command intelligence requirements.
(1) Encourages and enables RMI operational training activities in all RC duty status’ that
contribute to and optimize operational support to meet validated intelligence requirements.
(2) Coordinates RMI-access to DoD facilities, where appropriate, to support JRIC or
JRIP-associated activities; supports requests to other federal and DoD interagency partner
facilities for similar RMI support requirements.
11. DoDI 3325.11, June 26, 2015
ENCLOSURE 211
b. Develops and implements procedures to prioritize and resolve crisis-related conflicting or
competing customer requirements for JRIC and JRIP resources that result from crises, surge,
COOP, or other ongoing operational requirements.
c. Addresses JRIP PM prioritization recommendations in coordination with the OUSD(I)
d. Directs Service components and CCMDs to identify suitable missions and develop JRIC
IT, JRIC infrastructure, and JRIP resourcing requirements to engage RMI and JRIP reachback-
associated capabilities; ensures coordination with the USD(I) and the Service(s) to address those
requirements.
e. Facilitates coordination between the USD(I) and Combatant Commanders to staff and
complete all RMI-related CJCS orders, directives, and requests for forces that impact JRICs or
JRIP matters.
f. Includes JRICs and JRIP-related activities in joint exercises and joint experimentation
projects.
12. DoDI 3325.11, June 26, 2015
GLOSSARY12
GLOSSARY
PART I. ABBREVIATIONS AND ACRONYMS
AC Active Component
ASD(RA) Assistant Secretary of Defense for Reserve Affairs
BASOPS base operations support
CJCS Chairman of the Joint Chiefs of Staff
CCMD Combatant Command
COOP continuity of operations
CUA co-utilization agreements
CSA combat support agency
DIA Defense Intelligence Agency
DoD SIOO
DoDD
Department of Defense Senior Intelligence Oversight Official
DoD Directive
DoDI DoD Instruction
IC Intelligence Community
IT information technology
ISSA inter-service support agreement
JRIC joint reserve intelligence center
JRIP Joint Reserve Intelligence Program
MIP Military Intelligence Program
MOA memorandum of agreement
MOU memorandum of understanding
NIP National Intelligence Program
OUSD(I) Office of the Under Secretary of Defense for Intelligence
PM program manager
13. DoDI 3325.11, June 26, 2015
GLOSSARY13
RC Reserve Component
RCIE Reserve Component Intelligence Enterprise
RMI Reserve Military Intelligence
U.S.C. United States Code
USD(I) Under Secretary of Defense for Intelligence
USD(P&R) Under Secretary of Defense for Personnel and Readiness
PART II. DEFINITIONS
Unless otherwise noted, these terms and their definitions are for the purpose of this instruction.
BASOPS. Functions necessary to support, operate, and maintain JRIC and JRIP associated
facilities in order to sustain mission capability, ensure quality of life, and fund personnel and
infrastructure support. Each Service maintains their own support activities criteria, however,
common support functions include, but are not limited to: custodial services, pest management,
refuse collection and disposal services, fire prevention and protection, guard and security
services, utilities operation and maintenance (i.e., electric plants, heating plants, water plants,
sewage plants and air conditioning), office equipment maintenance and repair, natural resource
services, advertising and public relations, and transportation management services.
COOP. Defined in Joint Publication 1-02 (Reference (m)).
Defense Intelligence Enterprise. Defined in Reference (a).
distributed operations. The process of conducting operations from independent or
interdependent nodes in a teaming manner. Some operational planning or decision-making may
occur from outside the joint area of operations. The goal of a distributed operation is to support
the operational commander in the field; it is not a method of command from the rear.
JRIC. An intelligence production and training capability enabling RMI forces to meet Service
component, CCMD, CSA, and IC training, readiness and operational requirements. JRICs are
generally located within a Service component-owned, managed, and maintained (Active,
Reserve, or Guard) sensitive compartmented information facility and surrounding collateral and
unclassified areas and use JRIP associated IT infrastructure and connectivity.
JRIP. A DoD program supporting mobilization readiness and operational requirements for
intelligence collection, processing, analysis, production, and dissemination by utilizing RMI
forces to the fullest extent possible. The JRIP enables RMI capabilities to support DoD
intelligence requirements.
operational support. Defined in Reference (e).
14. DoDI 3325.11, June 26, 2015
GLOSSARY14
operational training. Defined in Reference (e).
RC. Defined in Reference (e).
RCIE. Defined in Reference (e).
reachback. Defined in Reference (m).
RMI. Defined in Reference (e).
shared-use. JRIC and other JRIP associated facilities available for RMI use (units, elements and
individual drilling personnel) to all Military Services on an equal basis for RC readiness,
sustainment, training, and operational support activities.
Total Force. Defined in Reference (e).