UNLIMITED FREE
ACCESS
TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

CJCSI 6285.01D

MISSION PARTNER ENVIRONMENT INFORMATION SHARING REQUIREMENTS MANAGEMENT PROCESS

inactive, Most Current
Organization: CJCS
Publication Date: 21 August 2017
Status: inactive
Page Count: 32
scope:

Purpose.

This instruction establishes the process for collecting, validating, prioritizing, and overseeing implementation of current Combatant Command's (CCMD) Mission Partner Environment (MPE) operational systems requirements as directed by reference a. The management process described in this instruction serves as a single point of entry for requirements to support modernization, enhancements, and system development efforts for existing programs within the Defense Information System Agency's (DISA) Multinational Information Sharing (MNIS) portfolio. Additionally, these requirements may be used to inform future doctrine, organization, training, materiel, leadership and education, personnel, facilities and policy development and other joint requirements generation processes. New capabilities will be assessed for operational validation and passed to the appropriate organization for sponsorship through the Joint Capabilities Integration and Development System (JCIDS) process. Request for network connections will be in accordance with references p, q, and r and not applicable to this process. Existing MPE information sharing systems and services covered by this instruction are listed in Enclosure D. U.S. Battlefield Information, Collection, and Exploitation Systems (US BICES) and U.S. BICES eXtended (US BICES-X) requirements are addressed in paragraph 4.e. Joint command and control (C2) requirements will follow the procedures outlined in reference k. The MPE requirements management process will evolve over time to keep pace with warfighter needs and technological improvements, and remain aligned to the MPE governance and management processes outlined in reference a and b.

Document History

CJCSI 6285.01D
August 21, 2017
MISSION PARTNER ENVIRONMENT INFORMATION SHARING REQUIREMENTS MANAGEMENT PROCESS
Purpose. This instruction establishes the process for collecting, validating, prioritizing, and overseeing implementation of current Combatant Command's (CCMD) Mission Partner Environment (MPE)...
May 15, 2013
MULTINATIONAL AND OTHER MISSION PARTNER (MNMP) INFORMATION SHARING REQUIREMENTS MANAGEMENT PROCESS
Purpose. This instruction establishes a process to collect, validate, prioritize, and sustain operational requirements for Multinational and other Mission Partner Information Sharing systems as...
December 30, 2010
CHANGE 1 TO CJCS INSTRUCTION 6285.01B
Purpose. This instruction establishes a CJCS requirements management process for sustainment of the MNIS systems: Combined Enterprise Regional Information Exchange System (CENTRIXS), CENTRIXS Cross...
September 13, 2010
MULTINATIONAL INFORMATION SHARING (MNIS) OPERATIONAL SYSTEMS REQUIREMENTS MANAGEMENT PROCESS
Purpose. This instruction establishes a CJCS requirements management process for sustainment of the MNIS systems: Combined Enterprise Regional Information Exchange System (CENTRIXS), CENTRIXS Cross...
May 16, 2008
MULTINATIONAL INFORMATION SHARING (MNIS) OPERATIONAL SYSTEMS REQUIREMENTS MANAGEMENT PROCESS
Purpose. This instruction establishes a CJCS requirements management process for sustainment of the three MNIS systems: Combined Enterprise Regional Information Exchange System (CENTRIXS), Griffin,...

References

Advertisement