Capítulo 3 Marco teórico
3.5 Criticas y limitaciones del ECM
include the following:
Provide leadership, establish primary C2, and supervise the maintenance of all Sense and Warn Sections.
Integrate the platoon with the TOC or controlling unit.
Integrate any C-RAM networks throughout the OA.
Supervise the maintenance of the platoon’s sense and warn equipment.
Ensure continuous security of the sense and warn sites.
S
ENSE AND WARNS
ECTION3-39. The primary role of the Sense and Warn Section is to provide EW and continuously update the TOC or BDOC cells on sense and warn status at the base, camp, or station and provide IDF input to the S-2 and counter-fire operation section. The section must maintain and operate the FAAD, AMDWS, WAVES, LCMR, and LAN (wireless or fiber), ensuring the operation of the FOB EW links. The following links, voice or digital, must be established when available: RAID, target acquisition sensor suite (TASS), AFATDS, and the UAS common ground station.
3-40. Each section will operate the system and will perform the following:
Interface with the TOC/BDOC or other assigned cells.
Perform operator preventive maintenance checks and services (PMCS) on the following
Ensure power systems are maintained.
Maintain system logs and reports.
Advise the supported unit.
Sense and Warn Section Responsibilities
3-41. The responsibilities of C-RAM personnel are varied. These responsibilities are listed in the following paragraphs.
Sense and Warn C2 Section Sergeant
3-42. The Sense and Warn C2 Section sergeant is the direct supervisor for a Sense and Warn Section. His responsibilities may include the following:
Provide leadership, establish primary C2, and supervise the maintenance of all Sense and Warn Sections.
Integrate Soldiers with the TOC or controlling unit.
Integrate the C-RAM network.
Directly supervise the maintenance of the section’s sense and warn equipment.
Ensure continuous security of the sense and warn site.
Sense and Warn C2 Section Leader
3-43. The Sense and Warn C2 Section leader performs the following:
Provides the commander and subordinate units with RAM information.
Provides information to facilitate SA in order to visualize, describe, and direct the battle as shown in Table 3-2.
Table 3-2. Assess the tactical situation and operations Supporting the Local Operations
Verify the commander’s critical information requirement (CCIR) and actions necessary upon identification of CCIR prior to tracking the battle.
Configure the EW capability for the current operations per the tactical standing operating procedure (TSOP).
Maintain SA and stay abreast of the current tactical situation.
Pass information supporting CCIR to the TOC/BDOC battle captain with a recommendation, as required.
Disseminate key RAM information within the TOC/BDOC, as required.
Brief RAM-related information as part of battle update briefs and shift changes.
Analyze RAM Threat Factors
3-44. The Sense and Warn C2 Section leader conducts the analysis of RAM threat factors, as described in Table 3-3, before proposing the BDOC area of interest and operational environment.
Table 3-3. RAM threat factors Operational Environment
Identify the area of interest.
Analyze RAM threat factors bearing on the operational environment.
Define threat systems bearing on the area of interest.
Analyze Effects of Weather and Terrain
3-45. The Sense and Warn C2 Section leader analyzes the effects of weather and terrain on RAM operations within the OA as described in Table 3-4.
Table 3-4. Environmental effects Weather and Terrain Analysis
Analyze air-related military aspects of the terrain using the observation and fields of fire, cover and concealment; obstacles, key terrain, and potential RAM POO.
Evaluate the effects of terrain on RAM operations.
Analyze the effects of weather on the operational environment.
Describe the operational environment effects on threat and friendly capabilities and broad courses of action (COA).
Evaluate the Threat
3-46. The Sense and Warn C2 Section leader updates the threat doctrinal template; analyzes threat capabilities, strengths, and vulnerabilities; and recommends coverage for high-value assets for the given situation, as Table 3-5 illustrates. Also, see Appendix F.
Table 3-5. Threat analysis Threat Analysis
Identify threat capabilities.
Define the composition of the threat.
Analyze the threat.
Identify how threat capabilities would impact broad COA.
Determine Threat Course of Action
3-47. The Sense and Warn C2 Section leader identifies and evaluates enemy COA, and specifies the most likely threat and most dangerous enemy COA as Table 3-6 shows.
Table 3-6. Enemy COAs Analysis of Enemy COA
Evaluate the threat COA overlays and provide C-RAM input to the S-2 section.
Determine the most likely and most dangerous threat COA.
Evaluate pattern analysis products to determine most likely enemy activity, times, and locations.
Review the situation template and C-RAM support input to the S-2 section.
Support development of critical collection requirements by providing C-RAM input during war gaming.
Conduct Mission Analysis
3-48. The Sense and Warn C2 Section leader analyzes the mission and determines friendly and enemy capabilities, and identifies critical tasks and capabilities pertaining to C-RAM, as shown in Table 3-7.
Table 3-7. Conduct analysis Friendly and Enemy Capabilities
Analyze the base order and relevant annexes received from higher in order to derive initial C-RAM concept of operations.
Provide initial intelligence preparation of the operational environment (IPOE) input for inclusion into the S-2’s overall IPOE estimate.
Identify C-RAM specified, implied, and essential tasks.
Analyze C-RAM assets available for the upcoming operation.
Identify any C-RAM-related constraints and limitations imposed by higher headquarters.
Identify C-RAM critical facts and assumptions.
Identify accident risk hazards and assess the risk level for each hazard.
Recommend C-RAM related information requirements for staff review to become CCIRs, priority intelligence requirements (PIRs), essential elements of friendly information, or friendly force information requirements.
Integrate C-RAM into ISR plan in coordination with S-2.
Brief the C-RAM portion during mission analysis briefings, if required.
Issue a warning order (WARNO) to the unit with the commander’s restated mission.
Plan Intelligence, Surveillance, and Reconnaissance Operations
3-49. The Sense and Warn C2 Section leader provides C-RAM input and assists in the staff development of the ISR plan as shown in Table 3-8.
Table 3-8. Plan ISR ISR Plan Development
Develop initial C-RAM ISR requirements as part of mission analysis.
Review the ISR threat related to ISR production and collection requirements.
Assist the ISR team’s development of an initial ISR plan.
Provide C-RAM scheme of support to ISR plan.
Review and update the ISR plan as necessary.
Develop a C-RAM Concept of Support for Each Course of Action
3-50. The Sense and Warn C2 Section leader assists in the development of COAs, consistent with the commander’s guidance. The Sense and Warn C2 Section leader incorporates C-RAM capabilities into each COA and briefs them as shown in Table 3-9.
Table 3-9. COA support COA Development
Assist the supported unit staff in analyzing relative combat power.
Review initial planning overlays created by the S-2/S-3 sections, and portray the initial array of forces for each COA.
Develop an initial C-RAM scheme of support for each COA.
Provide C-RAM input into the development of the COA statements and sketches.
Brief the C-RAM portion during COA briefing to the commander, as required.
Record C-RAM aspects of each COA in C-RAM running estimates for future planning.
War Game Concept of Support
3-51. The Sense and Warn C2 Section leader participates with the supported unit staff in the military decision-making process (MDMP) and incorporates the commander’s guidance. Additionally, the Sense and Warn C2 Section leader evaluates and reviews each COA from a C-RAM standpoint and develops an initial supporting C-RAM plan for each COA as shown in Table 3-10.
Table 3-10. Concept of support COA Analysis/War Gaming
Verify the S-3’s list of friendly C-RAM forces.
Evaluate C-RAM-related assumptions and evaluate critical events and decision points for appropriate C-RAM input.
Review the COA evaluation criteria, once determined by the XO or S-3.
Provide C-RAM input while participating in the staff war gaming method.
Assist the staff with the development of the synchronization matrix to include key C-RAM events.
Refine initial C-RAM scheme of support plan to incorporate analysis of the COA.
Record results of COA analysis in the C-RAM running estimate for future planning.
Compare Courses of Action
3-52. The Sense and Warn C2 Section leader compares each developed COA, consistent with the evaluation criteria, and identifies the preferred COA from a C-RAM standpoint. He then makes recommendations to the commander, as shown in Table 3-11.
Table 3-11. COA comparisons COA Analysis
Compare COAs using one evaluation criteria category at a time, and by using the decision support matrix.
Identify overall C-RAM advantages and disadvantages of COAs with respect to each other, by analyzing the decision support matrix data.
In the C-RAM running estimate, record C-RAM specific information from COA analysis and COA comparisons.
Identify the COA that has the highest probability of success against the threat, most likely, and most dangerous COA.
Recommend the best COA from an overall C-RAM perspective.
Develop the Running Estimate
3-53. The Sense and Warn C2 Section leader develops the C-RAM running estimate and provides input during the staff planning process. He then posts that information digitally for command, staff, higher, and subordinate access, as shown in Table 3-12.
Table 3-12. Running estimate Running Estimate Development
Develop the “Mission” portion of the C-RAM running estimate.
Develop the “Situation” and “Considerations” portions of the estimate.
Analyze and compare COAs as part of the MDMP with the maneuver staff.
Provide recommendation and conclusions as part of the MDMP with the maneuver staff.
Finalize the C-RAM plan and issue orders to unit.
Prepare an Annex
3-54. The Sense and Warn C2 Section leader completes the plan and prepares the C-RAM Sense and Warn annex to the existing operation order (OPORD). The C-RAM annex will clearly state the C-RAM mission and the commander’s intent, and will fully support the force scheme of maneuver as Table 3-13 illustrates.
Table 3-13. Annex Annex Preparation
Finalize C-RAM Sense and Warn plan based on the commander’s decisions and guidance.
Complete the OPORD.
Synchronize Operations
3-55. The Sense and Warn C2 Section leader synchronizes C-RAM operations to support the scheme of maneuver during all phases of the operation, coordinates with other staff members, and issues orders to ensure synchronization of C-RAM defense as shown in Table 3-14.
Table 3-14. Synchronize Operation Synchronization
Maintain SA of the decisive, shaping, and sustaining operations.
Recommend an order, fragmentary order (FRAGO), or request to higher to implement the commander’s decision based on the CCIR.
Recommend an order or FRAGO to subordinate units to execute a pre-planned decision, respond to a trigger, or conduct staff-to-staff coordination.
Develop recommendations because of unplanned or extraordinary C-RAM battlefield events critical to the current operation and requiring major adjustments to the plan or requests to higher.
Confirm receipt and understanding of all orders, FRAGOs, or requests to higher headquarters (or sender).
Sense and Warn C2 Operator
3-56. The Sense and Warn C2 operator is the direct operator for the Sense and Warn Section. His responsibilities may include the following:
FAAD C2 operator primary C2.
Maintain all sense and warn equipment.
Integrate with the TOC or controlling unit.
Maintain the C-RAM network.
3-57. The EW system operator establishes, integrates, and maintains all of the C-RAM Sense and Warn Section voice and data communications network architecture. The FAAD C2 operator has the job of ensuring the C-RAM section remains 100 percent operational at all times. Table 3-15 describes some of these duties and tasks.
Table 3-15. EW system operator Tasks
Manage the structure and employment of the data for internal C2.
Provide technical guidance on the joint services/task force communications architecture.
Manage unit maintenance and logistics on the AMDWS.
Manage integration and application of software and hardware upgrades.
Emplace LAN.
Manage data connectivity from sensor devices to internal and external sources.
Initialize and perform operator troubleshooting procedures on the LAN.
Perform the following on a UNIX system:
Operator actions.
System administration functions.
Archive functions.
User accounts maintenance.
Network functions.
Actions in an MSDOS environment.
Perform the following on the AMDWS:
Initialize the software.
Map generation.
Enter boundaries.
Create a sensor coverage overlay.
Select overlays.
Perform FO.
Perform EO.
Perform continuous operations.
Operate, troubleshoot faults, and maintain system.
Conduct PMCS.
Manage nonstandard prototypical computers and “off-the-shelf” equipment using an available logistics system.
Manage data and voice coordination networks.
Load crypto keys into enhanced position location reporting system (EPLRS) and SINCGARS radios.
Perform operator PMCS on digital nonsecure voice terminal (DNVT) and digital subscriber voice terminal (DSVT) equipment.
Perform operator PMCS on EPLRS radio set AN/VSQ-2(V)2.
Operate the EPLRS radio set AN/VSQ-2(V)2.
Operate the PLGR.
Integrate the PLGR into C-RAM systems.
Perform march order and emplacement.
Operate secure voice and data using secure telephones (STU III or STE).
Noncommissioned Officers
3-58. The C-RAM Sense and Warn noncommissioned officer (NCO) responsibilities include supervising all section operators in the performance of their duties, emplacement/march order (to include necessary computers and radios), and performing limited troubleshooting to allow for normal operations. The C-RAM Sense and Warn NCOs supervise emplacement of the FAAD, initialization of communications networks, and connectivity of the AMDWS, WAVE, RAID, TASS, AFATDS, and UAS common ground station.
Initialize Software on the AMDWS
3-59. The C-RAM Sense and Warn NCOs initialize the software on the AMDWS, log into the network, and insert the initialization parameters by performing the steps shown in Table 3-16.
Table 3-16. Initialize AMDWS AMDWS Software Initialization
Boot up the AMDWS.
Verify role name and external interface configuration.
Begin process manager.
Configure desktop one on AMDWS with defense planner.
Configure desktop two on AMDWS with common message processor.
Configure desktop three on AMDWS with common tactical picture (CTP).
Configure desktop four on AMDWS with user’s preference, such as Windows NT, Microsoft Office, or SUN Office Tools.
Ensure system is configured to interface with the following: WAVE, RAID, TASS, AFATDS, and UAS common ground station.
Perform AMDWS Map Generation
3-60. The C-RAM Sense and Warn NCOs generate an operational map using the defense planner or joint mapping tool kit (JMTK) software application. NCOs conduct planning or current operations on the AMDWS by performing Table 3-17.
Table 3-17. Map generation Operational Map
Start up the defense planner in the AMDWS.
Generate AMDWS maps from the defense planner or generate AMDWS maps.
Create a new map tab.
Zoom in on the selected map area.
Configure map settings.
Conduct planning or current operations on the AMDWS.
Establish the AMDWS Situational Display
3-61. The C-RAM Sense and Warn NCOs receive air tracks from live or simulated external sources, then open the correct mission in the defense planner and display the current air picture and situational display by performing the steps shown in Table 3-18.
Table 3-18. Situational display Displaying the Situation
Start up the defense planner software application.
Open an existing exercise, mission, and deployment.
Display the current air picture.
Relay the track information to other AMDWS in the network.
Relay the track information to the other systems on the network, WAVE, RAID, TASS, AFATDS, and UAS common ground station.
Integrate the AMDWS into the TOC or BDOC Network
3-62. The C-RAM Sense and Warn NCOs integrate the AMDWS into the TOC LAN and configure the equipment for operation by performing the steps shown in Table 3-19.
Table 3-19. TOC network Network the AMDWS
Verify that the ABCS server maneuver control system workstation is operational.
Verify that the sustainment operations control system is up and operational.
Configure the AMDWS into the LAN.
Perform synchronization with global positioning system time.
Deactivate the network group definition.
Verify LAN configuration settings.
Reactivate the network group definition settings.
Perform node initialization procedures.
Perform external data interface configuration procedures with the following systems: WAVE, RAID, TASS, AFATDS, and UAS common ground station.
Verify air picture is being sent by FAAD.
Perform Dual LAN Interface Procedures on the AMDWS
3-63. The C-RAM Sense and Warn NCOs configure the AMDWS to operate within a dual LAN interface by performing the steps as shown in Table 3-20.
Table 3-20. Dual LAN procedures Dual Networking Procedures
Inspect all LAN connections ensuring connectivity.
Configure the AMDWS to run either single or dual LAN.
Set network group definition; activate network group definition.
Power Up the AMDWS
3-64. The C-RAM Sense and Warn NCOs install the AMDWS on the LAN and configure it to operate as a client in the network architecture by performing Table 3-21.
Table 3-21. Power-up Client Configuration
Conduct initial exterior checks of the high-capacity computer front, rear, and monitor.
Boot up the AMDWS central processing unit (CPU).
Boot up the high-capacity computer to operate as a client.
Log in as user and prepare the system to initialize the AMDWS and CTP-related software.
React to RAM Alerts on the Battlefield Situation Display
3-65. The C-RAM Sense and Warn NCO or FAAD operator read and clear RAM track alerts in the order they are received. This provides the TOC/BDOC battle captain and FOB commander with a constant SA of the IDF picture. Perform the steps in Table 3-22.
Table 3-22. Alerts Displaying Tracks
Select F2 (single track) variable function key (VFK).
Select F1 (track clear) VFK.
Repeat step 2 for each track alert until all track alerts are cleared.
Select F2 (other clear) VFK to clear other alerts, as required.
Select USER SYSTEM TOP VFK to return to top level.
Monitor Early Warning Data
3-66. The C-RAM Sense and Warn Section receives EW data on the FAAD. The EW system operator will monitor and interact with EW data as shown in Table 3-23.
Table 3-23. EW data Early Warning System Operator Actions
Display RAM tracks on the AMDWS. Monitor friendly platforms based on speed, heading, and local airspace management procedures and controls.
Transmit changes in C-RAM equipment status to the battle captain.
The C-RAM EO section will process, evaluate, and disseminate EW over WAVES and evaluate and correlate RAM tracks.
The Sense and Warn NCO will inform the FOB personnel when pending tracks cross an established threshold.
The C-RAM Sense and Warn Section will receive and disseminate information to their platoon CP, report and receive C-RAM status updates.
Generate or Modify Control Measures on the Battlefield Situation Display
3-67. The C-RAM FAAD operator generates or modifies selected control measures to reflect changing conditions, or movement to a new site, by performing the steps in Table 3-24.
Table 3-24. Battlefield display Selecting Control Measures
Press F10 (MESSAGE) VFK.
Press F10 (CONTROL MEASURE) VFK.
Select desired control measures per commander’s guidance.
Enter required parameters at the prompts to generate control measures.
Press USER SYSTEM TOP VFK to return to top level.
Perform AMDWS Overlay Functions Using the Defense Planner
3-68. The C-RAM AMDWS operator displays the correct overlays on the mission map by entering the required information and coordinates, using the defense planner, by performing the steps in Table 3-25.
Table 3-25. Overlay functions Using the Defense Planner
Start up the defense planner in the AMDWS.
Create a new exercise/mission or open an existing exercise/mission.
Create a new sensor/weapon/control measure deployment or modify current deployment.
Save a deployment (overlay) using approved naming convention.
Open an existing deployment (overlay) created in the defense planner.
Send a deployment (overlay) created in the defense planner to another AMDWS.
Retrieve a deployment (overlay) sent from another AMDWS.
Perform AFATDS Data Distribution
3-69. The C-RAM NCOs distribute data to AFATDS by performing the steps in Table 3-26.
3-69. The C-RAM NCOs distribute data to AFATDS by performing the steps in Table 3-26.