ATP 6-02.61 — Expeditionary Mission Partner Network Operations
ATP 6-02.61 provides guidance for Army operations with mission partners on expeditionary mission partner networks.
- Publication number: ATP 6-02.61
- Title: EXPEDITIONARY MISSION PARTNER NETWORK OPERATIONS
- Date: 12/06/2023
- Proponent: T2COM
- Status: ACTIVE
View ATP 6-02.61 on armypubs.army.mil
It outlines doctrinal techniques for planning and executing Department of Defense information network operations on an expeditionary mission partner network. It covers network management, information dissemination management and content staging, cybersecurity, and integration of the multinational force common operational picture.
Applies to: ATP 6-02.61 applies to the Active Army, Army National Guard/Army National Guard of the United States and United States Army Reserve unless otherwise stated.
Topics covered
- Expeditionary mission partner networks
- Department of Defense information network operations
- Network management
- Information dissemination management and content staging
- Cybersecurity
- Digital common operational picture integration
Questions and answers
What information does a mission partner network exchange?
Working on a common network, these entities exchange information to facilitate command and control.
What communications does a mission partner network support?
MPN provides the supporting capabilities to communicate by secure text, speech, voice, and imagery (still and motion) with all MPN partners, superiors, peers, and subordinates. (paragraph 1-14)
What information can a mission partner network display on the common operational picture?
A MPN enables the receipt and dissemination of essential information to a command post platform for display on the common operational picture (COP). (paragraph 1-9)
Who is responsible for the mission partner network?
The multinational force commander is the network operational authority. This officer is responsible for the network. (paragraph 2-15)
When does network engineering start?
Network engineering starts prior to deployment through a persistent test environment and by using a standardized test plan. (paragraph 2-5)