Command and Control Systems Integrator

You are the ADA battalion's technical nerve center for command and control. The BC's air picture is only as clean as your data links — and you are the warrant officer responsible for making every system in the Integrated Fire Control element talk to every other system without dropping a track.

You completed WOCS at Fort Novosel and the Command and Control Systems Integrator Course at the U.S. Army Air Defense Artillery School at Fort Sill, Oklahoma — the Army's Fires Center of Excellence — and arrived at a PATRIOT firing battery or an ADA battalion headquarters. Day-to-day your job is owning the BMS architecture: FAAD C2 (Forward Area Air Defense Command and Control), the AMDWS (Air and Missile Defense Workstation), Sentinel radar data links, IFF (Identification Friend or Foe) integration, and the digital communications stack that ties launchers, radars, engagement control stations, and higher-echelon AMD headquarters into a common air picture. You troubleshoot data link outages while the battery is in a rotation, you integrate new software baseline upgrades without breaking the live picture, you advise the BC and the S3 on BMS architecture decisions, and you train the 14E and 14G soldiers who operate the consoles you are responsible for keeping online. The unglamorous parts: configuration management of legacy software on hardware that has been fielded since before some of your soldiers were born, COMSEC key management for the link encryption suite, and paperwork explaining to higher-echelon why a system is down that looks operational from the outside.

• 01Configure, integrate, and troubleshoot FAAD C2 — network architecture, message formats, track filtering, alert thresholds — so the BCP air picture matches the engagement picture at the IFC.
• 02Manage the AMDWS baseline across the battery: software version control, cryptographic key loads per AR 380-40, link-parameter verification, and post-outage recovery without a reboot that clears the track history.
• 03Integrate Sentinel radar data (3D track, IFF mode data) into the C2 network and verify track correlation between the radar's own display and the downstream AMDWS — mismatches are your flag, not the operator's.
• 04Brief the BC and the battalion S3 on BMS architecture risk in plain language: which nodes are single-point failures, what the PACE plan looks like if the primary C2 node goes down mid-engagement, and what you need to fix it.
• 05Train 14E TDAs and 14G BMS operators on C2 system fundamentals — not just "press this button" but "here is why the track disappeared and how to recover it without breaking the picture for the other batteries on the net."
• 06Run COMSEC custodian or sub-hand-receipt duties for the link-encryption keying material in the C2 network — AR 380-40 standard, two-person integrity, no blind spots on the destruction-log cycle.

• —FM 3-01 — Army Air and Missile Defense Operations (the doctrinal anchor for what you are protecting and why the C2 architecture exists).
• —ATP 3-01.16 — Air and Missile Defense Planning (C2 architecture in the joint AMD battle — read the link integration chapter before your first battalion-level exercise).
• —ATP 3-01.85 — Patriot Battalion and Battery Operations (the day-to-day operations framework that your C2 integration work supports).
• —ATP 3-01.7 — Air Defense Artillery Brigade Operations (brigade-level AMD picture — the echelon your data links feed).
• —AR 380-40 — Safeguarding and Controlling COMSEC Material; AR 25-1 — Army Information Technology; AR 25-2 — Army Cybersecurity.
• —System technical manuals for FAAD C2, AMDWS, and Sentinel — the doctrine gives you the "why"; the TMs give you the "how on this specific box at 0300."

• —WOBC and Command and Control Systems Integrator Course complete at Fort Sill — the entry credential; you do not sit the TCO chair without it.
• —FAAD C2 / AMDWS system integration certified by the gaining battalion — the unit-level credentialing step that says you can configure the architecture without breaking a live battery.
• —IAT-II baseline (CompTIA Security+ CE) under AR 25-2 / DoDM 8140 — a C2-systems integrator billet is coded, and the brigade S6 or G6 will ask at your in-brief.
• —COMSEC account accountability current at 100% — zero discrepancies on the first AR 380-40 audit after you take the sub-hand-receipt.
• —OER profile from the first WO billet that the senior rater can defend at the warrant promotion board — observable outcomes (data link uptime, BMS integration quality, soldier training events, exercise execution).

• —Applying a new FAAD C2 software baseline in the field without a validated rollback procedure documented and briefed to the battery. When the picture goes dark the BC is not interested in the release notes.
• —Signing COMSEC material in or out without physically verifying the serial number and quantity. The first AR 380-40 audit finds the gap — the warrant signs the relief paperwork.
• —Trying to own the picture instead of enabling the TDA's ownership of it. The 140A who pulls track calls from the warrant seat is doing the 14E's job and forgetting his own; when the C2 node fails the BC needs the integrator, not a second TDA.
• —Briefing the BC that a data link is "probably fine" without a documented diagnostic. "Probably fine" gets soldiers fired in a real-world engagement when the link was actually degraded.
• —Letting IAT certification lapse because "this is an ADA unit, not a cyber unit." The DoDM 8140 audit does not care that your unit fires missiles — the billet is coded and you are the one not current.

The good WO1 or CW2 is the one the BC calls by name in the BUB when the brigade's fire control officer asks why this battery's air picture is the cleanest in the formation — because the data links are architectured right, the software baselines are managed, and the 14E operators know exactly what the displays are telling them because the warrant explained it. He has Sec+ current, his COMSEC account is 100%, and the senior rater's OER bullet already names the specific exercise where the C2 architecture he built held up when the battalion's other two nets went down.

You are the C2 and BMS technical authority the AAMDC commander and the combatant-command AMD cell lean on when the architecture for the theater air defense picture has to be right the first time. At this rank you are shaping the network, advising the staffs that brief generals, and mentoring the junior warrants who are learning the seat you have been sitting for a decade.

At CW3 and above you hold billets at the battalion S3 section as the senior C2 integrator, at the ADA brigade or 10th AAMDC / 32nd AAMDC staff, at TRADOC / Fort Sill as a schoolhouse instructor or proponency officer for the 140A program, or at a COCOM AMD cell (CENTCOM, EUCOM, INDOPACOM) where the theater air picture has to integrate Army PATRIOT/THAAD, Navy Aegis, Air Force and allied networks into a common operating picture under Joint STARS / Link-16 architecture. You write the C2 architecture for multi-battery and multi-system integration exercises, you chair the technical review board when a new BMS software baseline arrives from the program office, you advise the AAMDC commander on network risk in terms the general-officer commander acts on, and you brief the joint staff cell on AMD C2 interoperability gaps before the next major exercise. You mentor WO1 and CW2 integrators through the technical competencies they will not learn in the schoolhouse — the field-expedient configuration workarounds that keep a battery's picture alive when the textbook solution takes 45 minutes the engagement doesn't have. You also own your own career math: the post-Army defense contractor space (Raytheon, Northrop Grumman, Lockheed Martin, Boeing) hires CW3-CW5 140As aggressively because the FAAD C2 / AMDWS / BMS architecture integration skill set is directly translatable to program office engineering and system integration roles, and the defense contractor pipeline is open if you start positioning during your last 3-4 years of service.

• 01Architect a multi-battery, multi-system C2 network — PATRIOT plus THAAD if the task force includes both, Link-16 integration where the JTIDS architecture is available, Sentinel plus LTAMDS radar track correlation — and brief the AAMDC commander on network risk in plain general-officer language.
• 02Chair a BMS software baseline technical review — evaluate the release notes, the known problem reports, the compatibility with existing link architecture, and make a recommendation to the battalion or brigade that is actionable, not academic.
• 03Lead AMD C2 interoperability planning with joint and allied partners — Army PATRIOT/THAAD integrated with Navy CEC / Aegis, Air Force GCCA, and partner-nation SHORAD systems — and document the link-parameter agreements that the operators will execute.
• 04Mentor CW2 and WO1 integrators on the technical decision-making under field conditions: when to reload a baseline, when to switch to the backup C2 node, how to rebuild the air picture after a COMSEC fail without breaking the engagement timeline.
• 05Brief the battalion or brigade command team on long-term C2 architecture risk — fielding timelines for IBCS (Integrated Battle Command System), the implications for the current FAAD C2 architecture, and how to manage the transition without a degraded air picture during the crossover window.
• 06Position for and execute the post-Army career transition — defense industry, program office technical advisor, government contractor supporting PEO Missiles & Space or the AMD CoE at Fort Sill — beginning the networking and credentialing work 3-4 years before retirement.

• —FM 3-01 — Army Air and Missile Defense Operations (the doctrinal foundation you are now contributing to, not just executing from).
• —ATP 3-01.16 — Air and Missile Defense Planning (C2 architecture and link integration chapters — at CW3+ you are the one briefing the staff on these chapters, not reading them for the first time).
• —JP 3-01 — Countering Air and Missile Threats (the joint doctrinal framework for theater-level AMD C2 — relevant at AAMDC and COCOM staff billets).
• —JP 6-0 — Joint Communications System (the joint C2 architecture doctrine behind Link-16, JREAP, and the joint interoperability framework your AMD network integrates with).
• —DA PAM 600-3 — Officer Professional Development (Warrant Officer career development framework — the CW3-CW5 chapter is your professional roadmap, not background reading).
• —PEO Missiles & Space program documentation and Army Capabilities Integration Center (ARCIC) AMD modernization roadmap publications — the non-classified versions are available and are the honest source on IBCS fielding timelines.

• —Warrant Officer Advanced Course (WOAC) complete — the career-gate for CW3 and the institutional credential that opens the senior technical billet slate.
• —IAM-II or IAM-III credential track (CISSP, CASP+) progressing — at AAMDC and COCOM staff billets the billet codes often require IAM-II or III; the CW3 who has Sec+ and nothing else is not competitive for those assignments.
• —Multi-battery, multi-system C2 integration exercise executed as the lead technical integrator — with a documented architecture package and a clean post-exercise AAR that the AAMDC uses as the template for the next rotation.
• —Mentor output: at least one WO1/CW2 mentored through the C2 systems integrator certification process per duty station — the senior warrant community measures this, and it is in your OER.
• —CW5: Technical Warrant Officer certification (Army Warrant Officer Cohort) and institutional recognition as the senior 140A subject-matter expert at echelon — the CW5 who cannot brief the IBCS transition risk to a two-star has not been doing the job.

• —Treating a COCOM or AAMDC staff billet as a desk job where the fieldcraft expires. The CW4 who cannot sit down at the AMDWS and configure a FAAD C2 link from scratch has handed the junior warrants proof that rank is the only thing separating you from the problem.
• —Over-promising on a BMS baseline compatibility assessment without actually running the integration test in a non-operational environment first. When the baseline breaks the live picture during a rotation the CW4 is the one who recommended the upgrade timeline.
• —Mentoring junior warrants on "how we did it at my last unit" without checking whether the software version, the local SOP, or the theater OPORD has changed. The 140A technical chain is only as good as the documentation that survives a PCS.
• —Treating the IBCS transition as something to brief, not something to prepare for. The fielding timeline is real; the CW4 who is still architecting around FAAD C2 the year IBCS arrives at his battalion is the one the BC does not trust with the migration plan.
• —Skipping the defense contractor pipeline conversation because "I have four more years." The senior 140A who starts the Raytheon / Northrop Grumman / program-office relationship at 18 months before retirement is the one who takes a cut in pay. The one who started at 36 months is the one who picks his offer.

The good CW3 or CW4 is the 140A the AAMDC operations officer calls when the theater air picture has a correlation problem nobody can explain — because this warrant has architectured C2 networks at battery, battalion, and multi-system level, knows exactly which link parameter causes that symptom, and can walk the room through the fix without a PowerPoint deck. His junior warrants are certified and independent; his architecture documentation survives his PCS; and the brigade command team can brief the IBCS transition risk at the next quarterly training brief using the analysis he produced. At CW5, the senior 140A is the technical authority the AMD CoE schoolhouse names when the 140A course curriculum needs updating and the program office needs a credible voice on what soldiers in the field actually need from the next baseline release.