JTAGS Operations Order
This appendix provides a template for a sample JTAGS detachment or section OPORD. It can be modified for exercises or operations. However, much of the information presented may not be required because of the echelon of command and the amount of detail contained in other annexes supporting the plan. To avoid duplication, refer to the basic operation plan and other annexes addressing space support where possible.
Copy ______ of _________ Copies
USARSPACE JOINT TACTICAL GROUND STATION (JTAGS) OPLAN _______
Time Zone Used Throughout the Order: ZULU
Major regional conflict (MRC)-East (E)
CONUS contingency teams (3)
a. Enemy forces. See Annex B (Intelligence) or intelligence estimate, and analysis of area of operations if available.
(1) Terrain. List all critical terrain aspects that would impact operations.
(2) Weather. List all critical weather aspects that would impact operations.
(3) Enemy capability and/or activity.
- List known and template locations and activities of enemy units. Information is normally gathered one level up and two levels down.
- List significant enemy maneuver and functional area capabilities that impact friendly operations.
- State the expected employment of enemy assets based on the most probable enemy course of action.
b. Friendly situation.
(1) Outline the plan of the higher headquarters.
(2) List designation, location, and outline of the plan of higher, adjacent, and other functional area assets that support or would otherwise impact the issuing headquarters or would require coordination, and any other supporting the unit.
c. Attachments and detachments.
(1) List attached Navy operators from Detachment E/Navy Space Command, advance party members other than JTAGS personnel, and other personnel or elements attached or detached only as necessary to clarify task organization.
(2) Highlight changes in task organization that occur during the operation, including effective times or events.
(1) Personnel, equipment, and prescribed load list (PLL) are available from the entire JTAGS Branch for cross-level to support the mission.
(2) For deployment of CONUS contingency teams, all required Navy operators are available to support the mission.
(3) ARSPACE headquarters staff is available to support the mission.
(4) JTAGS support requirements are a priority to the receiving theater.
(5) Airlift or sealift is available for the deployment.
Major regional conflict (MRC)-East, MRC-W and/or the CONUS contingency teams deploy (TBD) to (location) to provide processing and dissemination of tactical ballistic missile cueing, alerting, and early warning in support of (supported CINC).
a. Concept of operations.
(1) JTAGS is the transportable in-theater element of U.S. Space Command's (USSPACECOM) theater event system (TES) and provides theater commanders a continuous 24-hour capability to receive and process in theater, direct downlinked data from defense support program (DSP) sensors in order to disseminate early warning, alerting, and cueing information on tactical ballistic missiles (TBMs) and other tactical events of interest throughout the theater using existing communication networks. JTAGS processes data from up to three DSP satellites to determine launch points, state vectors, and predicted ground impact points for TBMs and ties directly to worldwide and theater communication systems to immediately disseminate this critical information. JTAGS supports all theater missile defense (TMD) operational elements (attack operations, active defense, passive defense, and battle management/command, control, communications, computers, and intelligence (BM/C4I)).
(2) Peacetime/Armistice Operations. One JTAGS detachment headquarters with one section is deployed in Korea (JTAGS-PAC), supporting U.S. Forces Korea (USFK) and Pacific Command (PACOM). One detachment headquarters with one section is deployed in Germany (JTAGS-EUR), supporting European Command (EUCOM) and Central Command (CENTCOM). These forward-deployed JTAGS detachments conduct continuous 24-hour operations in support of their respective theaters and TES. There are two contingency JTAGS sections that train to maintain combat readiness for immediate contingency deployment. The last contingency section is used to support JTAGS individual qualification training. This section can deploy to support a contingency as a secondary mission.
(3) Wartime Operations. In periods of increased tension or active conflict with a chance of tactical ballistic missile activity, two CONUS contingency teams may deploy forward into the theater when requested by the supported CINC and tasked by CINCSPACE. The system(s) currently in theater may remain in place or deploy to another location within theater. Because JTAGS receives data directly from space-based sensors and can use long-haul communications, it is not necessary to actually position a JTAGS within the theater of conflict to provide support. However, the added value of positioning a JTAGS system directly in theater to take advantage of the existing theater communications architecture is critical to assured and rapid dissemination of JTAGS information.
(4) Advance Party. The successful and rapid in-theater reception and integration of JTAGS depends largely on two factors: 1) the maturity of the theater to integrate JTAGS based on a previously conducted advance party site survey, and 2) the successful accomplishment of a current advance party site survey. Either way, the theater must make the reception and integration of JTAGS a priority for successful accomplishment of the JTAGS mission. As soon as a contingency mission appears possible, the JTAGS branch chief will request the theater to authorize an advance party into country and then deploy the advance party. Exact composition of the party will vary depending on previous site survey information and the maturity of the theater's support. Most advance parties will consist of the branch chief and/or a section OIC, communication support contractor, and a DCSLOG logistic representative. Additional members can include a supporting contractor, DCSINT security representative, and other members of the ARSPACE staff depending on theater requirements.
(5) Deployment Sequence.
(a) On notification for deployment, the Army Space Command Center (ARSPCC) or DCSOPS will notify the JTAGS branch chief (or designated representative) who will then activate the JTAGS alert roster and initiate the required n-hour sequence (Appendix 3 (n-Hour Sequence) to Annex C (Operations)). The normal sequence is a 48-hour deployment timeline; however, JTAGS can be prepared to deploy on a 24-hour timeline if required and if airlift is available. The ARSPCC will recall all ARSPACE staff members required to support the deployment.
(b) For deployment of CONUS contingency teams, personnel will recall to support the deployment, regardless of which section is deploying. Additionally, the JTAGS branch chief will notify the Navy Space Command (NAVSPACECOM) JTAGS program officer, NAVSPACECOM Operations Center, or Detachment E of the pending mission and arrange for deployment of Navy operators to Colorado Springs.
(c) JTAGS is capable of deploying by air, land, and sea. However, standard deployment is by air in order to get JTAGS rapidly into theater. The deployment sequence includes the following critical tasks of recalling all personnel, load and march order the deploying section(s), move to the aerial port of embarkation (APOE) and conduct airload operations, fly to the theater aerial port of debarkation (APOD) where the section(s) is met and received by the advance party, offload, stage, march order, road march to the site, emplace, and assume mission.
b. Tasks to subordinate staffs/elements.
(1) Detachment Commanders/Section OICs.
(a) Maintain personnel and equipment to deployment readiness.
(b) Update automated unit equipment list (AUEL).
(c) On alert notification, initiate and supervise required n-hour.
(d) Prepare personnel, vehicles, equipment, and pallets for movement IAW established load plans and directed n-hour sequence.
(e) When CONUS contingency teams are deploying to a theater already supported by a JTAGS detachment, the detachment commander will:
1. Conduct in-theater coordination as directed by the JTAGS branch chief prior to deployment of the JTAGS section.
2. Be prepared to assume command and control of the JTAGS section on arrival.
(2) JTAGS Branch Chief (Director of Operations if Branch Chief is deployed).
(a) On alert notification for deployment of CONUS contingency teams:
1. Initiate the JTAGS alert roster. Monitor recall until all JTAGS personnel are available or accounted for.
2. Alert and coordinate for deployment of Navy operators from Detachment E/NAVSPACE. Receive attachment of Navy operators on their arrival.
3. Brief Commander/ JTAGS-PAC and JTAGS-EUR on the mission and establish any required CONOPS for the mission.
(b) Initiate coordination with required ARSPACE staffs for all n-hour sequence requirements.
(c) Initiate coordination with the theater for mission requirements and advance party deployment.
(d) Establish and deploy the advance party. See Appendix 1 (JTAGS Advance Party Operations) to Annex C (Operations) for detailed information.
(e) Verify time-phased force deployment data (TPFDD) information with the ARSPCC.
(f) Coordinate with USSPACECOM for specific mission requirements including shared early warning (SEW) and first detect/first report (FD/FR) requirements.
(g) Coordinate with the JTAGS Product Office and the supporting contractor for all required contractor logistics support (CLS) to support the deployment and mission.
(h) Maintain and publish the operations plan (OPLAN) and operations order (OPORD) for all contingency missions as directed by the DCSOPS. Provide the base OPLAN/OPORD, Annex C (Operations), Annex J (Command Relationships), and Annex K (Command, Control, and Communications Systems).
(3) Deputy Chief of Staff, Operations (DCSOPS).
(a) On alert notification, initiate recall of JTAGS personnel and essential ARSPACE headquarters personnel to execute the JTAGS deployment.
(b) Brief Command Group and staff on current situation.
(c) Establish and direct a crisis action team (CAT) if required.
(d) Issue OPLANs and OPORDs for all contingency missions. Have the information operations officer provide Annex L (Operations Security) to this OPLAN.
(4) Deputy Chief of Staff, Personnel (DCSPER).
(a) Provide the personnel and medical services portion of Annex D (Logistics) of this OPLAN to the DCSLOG. Assist with other portions as required.
(b) For deployment of CONUS contingency teams:
1. Conduct records review of all deploying personnel to determine level of soldier readiness processing (SRP) and support that is required.
2. Coordinate with logistic support installation for required support to complete SRP of deploying personnel (i.e., medical/dental, legal, finance).
3. Complete all necessary record transactions based on personnel cross-leveling.
4. In coordination with (ICW) JTAGS branch, and the HQ's first sergeant, schedule and conduct the family support group meeting.
5. Coordinate with logistic support installation for chaplain support during deployment operations and for briefings to soldiers and family members as required.
(5) Deputy Chief of Staff, Intelligence (DCSINT).
(a) Brief personnel on any local threat activity as required.
(b) Brief deploying personnel on threat activity (IPB) and security in the theater of operations.
(c) Brief personnel on the environment in the theater of operations (i.e., terrain, weather, etc.) as required.
(d) Brief personnel on subversion and espionage directed against the United States (SAEDA), operations security (OPSEC), signal security (SIGSEC), and essential elements of friendly information (EEFI).
(e) ICW the public affairs officer (PAO), ensure that information released to the public contains no classified or sensitive information.
(f) Be prepared to provide one member for the advance party as required to coordinate security support for the deploying section(s).
(g) Provide Annex B (Intelligence) of the OPLAN to the DCSOPS.
(6) Deputy Chief of Staff, Logistics (DCSLOG).
(a) Determine and report location of APOE/seaport of embarkation (SPOE) and APOD/seaport of debarkation (SPOD) to JTAGS branch chief.
(b) Coordinate transportation requirements for the deployment.
(c) Provide one or more members for the advance party as required to coordinate logistics support for the deploying section(s).
(d) Provide loading assistance and materials to deploying personnel as well as assisting in coordinating/conducting departure airfield control group (DACG) operations.
(e) Coordinate with logistic support installation for pickup of basic load of Class I, meals ready to eat (MREs) for deployment.
(f) Coordinate with logistic support installation for pickup of Class V basic load.
(g) Ensure material handling equipment (MHE) required for packing and loading equipment is available (i.e., forklifts, k-loaders).
(h) For deployment of CONUS contingency teams:
1. Coordinate use of ARSPACE General Services Administration (GSA) and transportation motorpool (TMP) vehicles for transport of personnel to the APOE as required.
2. Coordinate lodging and transportation for Navy operators.
3. Coordinate issue of CTA-50 for deploying personnel, to include Navy operators and contractors.
4. Be prepared to issue/requisition supplies and materials to deploying personnel.
(i) Coordinate with logistic support installation for maintenance contact teams to assist in preparation of vehicles for air loading.
(j) Provide Annex D (Logistics) of this OPLAN to the DCSOPS.
(7) Public Affairs Officer (PAO).
(a) Provide Annex F (Public Affairs) of this OPLAN to the DCSOPS.
(b) For deployment of CONUS contingency teams:
1. Prepare statements for release to the media.
2. Contact local media if and when appropriate.
3. Field all inquiries from media.
4. ICW DCSINT, ensure classified and sensitive information is not released to the media.
5. Provide guidance and brief USARSPACE personnel regarding release of information to the media.
6. Coordinate requirements with local, higher headquarters, and theater PAO officers.
(8) Deputy Chief of Staff, Contracting (DCSCON).
(a) ICW the Deputy Chief of Staff, Resource Management (DCSRM), coordinate with JTAGS Product Office to ensure CLS contract coverage is adequate for the mission requirements including logistics and supporting contractor assistance. Augment if required.
(b) ICW DCSPER, ensure contractors are ready to deploy. Coordinate for contractor visas for the country(ies) of deployment.
(c) ICW the DCSRM, assist the advance party with in-theater procurement requirements.
(d) Provide the contracting and procurement portion of Annex D (Logistics) of this OPLAN to the DCSLOG (if required). Assist with other portions as required.
(9) Deputy Chief of Staff, Information Management (DCSIM) will issue cell phones to the JTAGS OIC and other personnel as directed by the ARSPACE Commander and/or DCSOPS.
c. Coordinating instructions.
(1) This plan is in effect for staff coordination immediately and becomes an OPORD on alert notification.
(2) Commander's critical information requirements (CCIRs).
(a) Priority intelligence requirements (PIRs).
(b) Essential elements of friendly information.
1. ARSPACE standing.
a.What missions/contingencies are being planned?
b.What units have been identified for possible deployment? What is their level of readiness? What are the specifics of their deployment and redeployment (i.e., schedules, routes, modes, destinations, ports, etc.)?
c.What are the capabilities, limitations, and vulnerabilities of USARSPACE (FWD) command, control, communications, computers, and intelligence (C4I) nodes?
d.What personnel actions/activities (i.e., leave, recalls, temporary duties (TDYs), after hour activities at the HQs, and unit mobilizations) indicate changes in the USARSPACE (FWD) readiness posture?
e.What are the single points of failure across the entire communication spectrum that would negatively impact USARSPACE (FWD) mission?
f.What new systems and technologies are being evaluated, fielded, developed, and/or integrated by USARSPACE (FWD), their capabilities, and what resources are required to operate and sustain them?
g.What are the single points of failure for USARSPACE (FWD) supporting infrastructure (i.e., facilities, utilities, personnel, logistic support, resources, equipment, and hardware)?
h.What unclassified technical and operations data (i.e., after action reports, briefings, information papers, financial reports, logistic data, etc.) if compiled may reveal critical sensitive or classified aspects of USARSPACE (FWD) and/or its operations?
i.What are the single points of failure for outsource support (i.e., sole source providers, contractors, key contractor personnel)?
j.Who are the command personnel whose absence would significantly, adversely affect mission accomplishment?
2. Additional JTAGS standing.
a.Specific details about deployment site.
b. Supporting unit during mission.
c. All DSP information.
d. Warning dissemination means and architectures.
e. Additional support equipment.
f. Scheduled and unscheduled down time.
g. All frequencies and codes.
h. Personnel data information.
(c) Friendly force information requirements (FFIRs).
(3) Force protection and risk reduction control measures.
(a) Mission-oriented protective posture (MOPP).
1. All personnel will deploy with complete MOPP equipment including the M40 protective mask with hood and optical inserts (if required), chemical protective overgarment (CPOG)/battle dress overgarment (BDO), overboots, gloves with inserts, one roll M9 detector paper, and one M258A1/M291 decontamination kit either worn or carried in their operational nuclear, chemical, biological (NBC) bag depending on MOPP level.
2. Additionally, all personnel will deploy with one individual chemical equipment (ICE) pack that includes a spare CPOG/BDO, protective mask hood, gloves with inserts, protective mask filter, one roll M9 detector paper, and one M258A1/M291 decontamination kit.
3. The section OIC/NCOIC will pack three (3) nerve agent antidote kits (NAAKs) Mark 1 and one (1) convulsant antidote for nerve agents (CANAs) per each deploying person and issue to each soldier as required by theater. The OIC/NCOIC will also pack and issue nerve agent pretreatment pyridostigmine (NAPP) tablets if available.
4. No MOPP level in effect during the loadup phase of the n-hour sequence. MOPP READY in effect prior to boarding the aircraft or other means of travel away from APOE/SPOE. Theater MOPP level in effect prior to landing at APOD/SPOD.
(b) Operational Exposure Guide (OEG). Theater guidance in effect.
(c) Vehicle recognition signals.
(4) Rules of engagement.
(5) Environmental considerations.
4. SERVICE SUPPORT
See Annex D (Logistics).
5. COMMAND AND SIGNAL
(1) For most contingencies, JTAGS will remain OPCON to ARSPACE and provide general or direct support to the theater. Under some circumstances, CINCSPACE may transfer OPCON to the theater CINC. The exact command relationship of the deploying JTAGS detachments/section(s) to the theater is dependent on the situation and IAW CINCSPACE Force Transfer Decision Tree (see Annex J (Command Relationships)).
(2) Deployment of CONUS contingency teams. The ranking ARSPACE military member of the advance party will command the advance party and the section(s) when it arrives unless a more senior ARSPACE officer arrives with the section. Typically, the JTAGS branch chief or section OIC will be in command of the section(s). If the section(s) is deployed into the EUCOM or PACOM theater, the detachment commander from that theater will be prepared to take command. Succession of command is by rank. When ARSPACE retains OPCON, chain of command will flow from the in-theater commanding officer back to Commander, ARSPACE.
(3) State the location of key functional area leaders.
(4) List command posts and other C2 facilities and their locations.
See Annex K (Command, Control, and Communications Systems).
|Join the GlobalSecurity.org mailing list|