Intelligence Systems Integration and Maintenance Technician

You are the technical authority the 35T section has been working toward becoming. You came out of the best maintainer / integrator bench in Army MI — and the BCT S2, the brigade SSO, and the analyst section chief now treat your read on whether DCGS-A is healthy as the ground truth.

You completed the 353T Warrant Officer Basic Course (WOBC) at the U.S. Army Intelligence Center of Excellence, Fort Huachuca, and arrived at your first warrant billet carrying the technical depth of a senior 35T with the new authority to own technical decisions your NCO career was always supporting. At WO1/CW2 you are typically the primary MI systems warrant in a BCT MICO, a divisional MI battalion, or a named MI brigade — 470th at JBSA-Fort Sam Houston, 500th at Schofield, 501st in Korea, 66th at Wiesbaden, 780th at Fort Eisenhower, or one of the MI groups at Fort Meade. Your daily work is the technical management of the intelligence collection and processing enterprise: DCGS-A node administration and configuration, integration of the all-source production stack with SIGINT, GEOINT, and HUMINT feeds, COMSEC account management under AR 380-40, tactical SIGINT vehicle fielding and integration (Prophet Enhanced, Trojan SPIRIT), and the SCIF physical and IT infrastructure that the analysts depend on and cannot fix themselves. You sign for millions of dollars of MI-specific kit. You also own the workforce: the IAT certification pipeline for your 35T section, the DoDM 8140 workforce management data, and the JQR / OJT sign-off structure that moves junior maintainers from observer to qualified operator. The 35T SGT NCOIC executes; you set the technical standard they execute to.

• 01Administer a DCGS-A node end-to-end — service configuration, query-tier and ingest-tier troubleshooting, database integrity, vendor field-service escalation with a clean repro package — to the Army Intelligence Enterprise standard.
• 02Integrate the MI collection and processing enterprise: correlate DCGS-A ingest parameters with the unit's Priority Intelligence Requirements (PIR) and ensure the system architecture reflects the commander's collection plan under ADP 2-0.
• 03Own the SCIF IT infrastructure — Windows / Red Hat server environment, AD, storage, cross-domain solutions, NIPR/SIPR/JWICS/NSANet segmentation — to ICD 705 and ICD 503 standards from the floor to the ATO.
• 04Run the unit's COMSEC account at the warrant level under AR 380-40 — EKMS / KMI key generation and distribution, LCMS log discipline, two-person integrity, semi-annual inventory defensible to the next echelon up.
• 05Lead the section's DoDM 8140 workforce compliance — IAT-II/III credential tracking, work-role assignments, position coding, and the MOU / manning documents that gate billet access.
• 06Brief the S2 OIC and the BCT S-6 on MI systems technical status — DCGS-A uptime, IAVA compliance posture, COMSEC account status, and residual risk — in language the operational staff can act on.

• —ADP 2-0 — Intelligence (the doctrinal framework that defines what all-source production infrastructure is supposed to enable; every DCGS-A architecture decision you make serves this document).
• —FM 2-0 — Intelligence (the operational reference; read chapter 2 on MI operations and chapter 4 on MI systems before your first BUB).
• —AR 25-2 — Army Cybersecurity; AR 25-1 — Army Information Technology (the policy framework every ATO and STIG baseline you manage is built on).
• —AR 380-40 — Safeguarding and Controlling Communications Security Material; AR 380-5 — Department of the Army Information Security Program.
• —AR 381-10 — US Army Intelligence Activities; AR 381-12 — Threat Awareness and Reporting (TARP); DoDD 5240.01 — DoD Intelligence Activities.
• —DoDM 8140 — Cyberspace Workforce Qualification and Management Program; ICD 503 — IC IT Systems Security Risk Management; ICD 705 — Technical Specifications for Construction and Management of Sensitive Compartmented Information Facilities.

• —WOBC complete at Fort Huachuca; first-unit JQR signed off on the primary DCGS-A and SCIF infrastructure work-roles inside 12 months of arrival.
• —IAT-III credential (CCNP-Security, CASP+, or CISSP on the DoDM 8140 list) current — the 353T billet is typically an IAM-II or IAM-III coded position; arrive with the credential, do not wait for the unit to fund it.
• —DCGS-A node, tactical SIGINT platform, and SCIF IT infrastructure under your signature with zero CAT-1 STIG findings unresolved past the published window.
• —First OER cycle producing a rater narrative with measurable technical outcomes — uptime percentages, IAVA closure rates, soldiers certified, inspections passed — not process descriptions.
• —TS/SCI with CI polygraph where the billet requires it, maintained without a flag; one unauthorized disclosure investigation ends the clearance and the career simultaneously.

• —Signing a COMSEC risk acceptance memo without personally reading the underlying discrepancy. The memo carries your name and your technical authority; a discrepancy you did not understand is one you cannot defend to the AR 15-6 investigating officer.
• —Configuring DCGS-A to satisfy the analyst's immediate collection request without validating the change against the Army Intelligence Enterprise architecture standards. The next fielding team or the INSCOM inspector will find the deviation and it will be in your OER.
• —Treating the 35T section NCOIC as the technical authority and yourself as the administrator. The warrant officer is the technical decision-maker; the NCOIC executes that decision. Reversing the relationship means the section is being led by an NCO without warrant authority and the formation notices.
• —Letting IAT credentials lapse across the section without escalating to the S2 OIC. DoDM 8140 audit pulls an uncertified soldier off a billet the day it expires; if you were tracking the pipeline you had 30 days of warning — the warrant who is surprised is the warrant who was not watching.
• —Closing a system-outage ticket without a written root-cause analysis and a corrective-action line. The next outage with the same signature will show that you fixed it once and did not institutionalize the fix; that is the entry in the inspector's finding.

The good WO1/CW2 353T is the warrant the brigade S2 OIC names in the BUB slide as "MI systems is solid" — because DCGS-A uptime is green, the IAVA closure rate is above the brigade floor, the COMSEC inventory is clean, and the analysts have not had to call the senior maintainer since this warrant arrived. His section NCOICs are running the floor the way he trained them, his OER has outcomes in it, and the INSCOM inspector asks him to explain the architecture rather than explain the findings.

You are the senior technical authority for all-source intelligence production infrastructure in your formation. At CW5 you are the officer the INSCOM CG, the corps G-2, and the brigade S2 community trusts when the MI system enterprise is the decisive factor and the answer has to be right.

At CW3 through CW5 you are holding the billets that define the 353T community: Senior MI Systems Warrant at a division, corps, or theater MI headquarters; senior technical advisor to an INSCOM command element; 780th MI Brigade at Fort Eisenhower; 706th MI Group at Fort Meade alongside NSA / CSS infrastructure; ARCYBER or USCYBERCOM technical advisory staff; or Army Futures Command in a DCGS-A program-of-record advisory role. Your advisory scope has expanded from one brigade's DCGS-A node to the entire MI collection and processing enterprise at your echelon — integration architecture across all-source, SIGINT, GEOINT, MASINT, and HUMINT feeds; the Authority to Operate (ATO) lifecycle for IC IT systems under ICD 503 and the DoD RMF; the fielding and training integration for new MI systems and sensors as they arrive in the force; and the cross-classification management of the SCIF environments that the enterprise runs inside. You also own the community. The CW5 353T shapes the accession criteria, the WOAC curriculum feedback, the billet structure at echelon, and the career development pathway for CW2s and CW3s below you. At CW4 and CW5 you will brief division and corps commanders on MI system risk in terms they can translate directly to collection posture decisions; the clean technical assessment you deliver to a two-star who has a collection window opening in six hours is the reason this warrant specialty exists. You are also building your post-service positioning deliberately — NSA / CSS, INSCOM civilian workforce, defense contractors supporting the DCGS-A program of record, and the IC IT community at large all recognize this credential set.

• 01Lead the MI systems enterprise architecture review at division or corps level — DCGS-A topology, cross-domain solution integration, network segmentation, redundancy and continuity architecture — and produce the technical assessment the G-2 can brief to the commanding general without a staff package carrying it.
• 02Own the ATO lifecycle for IC IT systems at your echelon: system categorization under CNSSI 1253, NIST SP 800-53 control selection, STIG artifact collection, continuous monitoring architecture, AO brief and acceptance — without a contractor carrying the technical lead.
• 03Integrate new MI system fieldings — sensor platforms, processing upgrades, DCGS-A software increments — into the operational formation without disrupting the analytic line or the SIGINT collection picture, and write the fielding integration plan the program office can carry forward.
• 04Mentor junior 353T warrants (WO1/CW2) through WOBC, their first-unit JQR, and their first OER cycle — with OER support forms that name technical outcomes, not process participation.
• 05Represent the Army MI systems community in joint and IC environments — USCYBERCOM, INSCOM, NSA/CSS technical forums, COCOM J-2 / J-6 integration — and produce assessments the joint force can act on.
• 06Brief the division or corps commander on MI system readiness in the language of collection posture and intelligence production capacity — not uptime percentages, but what the formation can and cannot know tonight based on the systems that are up.

• —ADP 2-0 — Intelligence; FM 2-0 — Intelligence (the doctrinal framework that defines what every architecture decision you make is supposed to enable).
• —AR 25-2 — Army Cybersecurity; AR 25-1 — Army Information Technology; AR 380-5 — Information Security; AR 380-40 — COMSEC Material.
• —AR 381-10 — US Army Intelligence Activities; AR 381-12 — TARP; DoDD 5240.01 — DoD Intelligence Activities; EO 12333.
• —ICD 503 — IC IT Systems Security Risk Management; ICD 705 — SCIF Technical Specifications; DoDI 8510.01 — Risk Management Framework for DoD Information Technology.
• —NIST SP 800-53 (current revision) — Security and Privacy Controls for Information Systems; CNSSI 1253 — Security Categorization and Control Selection for National Security Systems.
• —DoDM 8140 — Cyberspace Workforce Qualification; DA PAM 600-3 — Officer Professional Development (Warrant Officer career management); JP 2-0 — Joint Intelligence (the joint doctrinal context the senior 353T operates inside at corps and above).

• —IAM-III credential (CISSP or equivalent under DoDM 8140) current and continuously renewed — the senior 353T who lets the IAM-III lapse has voluntarily uncredentialed himself from the technical standard the entire community is built on.
• —Warrant Officer Advanced Course (WOAC) and Warrant Officer Staff Course (WOSC) complete; WOSSC for CW5 candidates — the PME gates the selection board looks at alongside the technical record.
• —ATO accepted and actively monitored for IC IT systems under your signature — the senior 353T who has never carried an ATO to completion has a gap the INSCOM and ARCYBER inspection teams will find.
• —Junior warrant development record: at least two WO1/CW2 353Ts billet-qualified and technically competent under your direct mentorship, with OER narratives that name outcomes and not just participation.
• —Post-service positioning built deliberately: the CW5 353T's technical record — IAM-III, ATO experience, INSCOM / NSA-CSS exposure, joint billet — maps to GS-14/GS-15 IC civilian positions or cleared defense contractor technical staff at compensation levels that require documented positioning, not last-minute resume building.

• —Briefing the division or corps commander on MI system readiness with a reconciled picture that understates what the subordinate 353T or 35T section actually found. The two-star who makes a collection decision based on an optimistic system-health brief is carrying risk the senior warrant manufactured.
• —Allowing a new DCGS-A software increment or sensor integration to go live in the operational formation without a written integration plan, a rollback procedure, and a validation test against the analytic workflow. The increment that breaks the collection picture at 2300 before an operation is the warrant's professional signature if there was no integration control.
• —Treating the junior warrant development function as a calendar obligation rather than the primary technical obligation of the senior seat. A CW4 or CW5 who does not produce technically competent junior warrants is shrinking the community, not leading it.
• —Confusing the 353T technical advisory role with programmatic authority over the DCGS-A program of record. Army Futures Command, INSCOM G-6, and the PM MI Systems office own the program decisions; the 353T advises from the operational formation's position. The CW5 who mistakes advisory influence for programmatic ownership breaks the relationships the community depends on.
• —Deferring post-service positioning until the retirement packet is in processing. The IC civilian and cleared-contractor markets the CW5 353T is positioned for require three to five years of deliberate credential maintenance, billet documentation, and professional network building — starting that process at eighteen months out is already late.

The good CW4/CW5 353T is the warrant the corps G-2 calls by name when the MI system enterprise is the factor limiting the collection picture — because when this warrant says the DCGS-A architecture will support the targeting cycle tonight or will not, the G-2 carries that into the commander's update without a qualifier. The junior warrants and 35T section chiefs in the formation describe him as the officer who made their technical careers possible: pushed them into the WOAC packet when they were not sure they were ready, wrote OER support forms with outcomes instead of adjectives, sponsored the stretch billet nominations that built the record. When this warrant retires, the INSCOM or 706th MI Group technical advisory function does not collapse because the institutional knowledge was documented, handed over, and the two CW2s he developed are already running the floor.