Brigade Onboarding · WiFi → TAK → Field → Live Fire

Plan and prepare before the field. A brigade — with or without TAK — can load its roster, MTOE, hand receipts, and readiness into SHIELD/ATLAS, train in classroom mode over WiFi, switch to TAK-enabled rehearsal on the same plan, then deploy to field DDIL and live-fire while continuing to execute the same plan with the same data and the same audit chain. One platform, four phases, no re-platforming between them.

Four Phases · Same Plan, Same Data, Same Audit Chain

PHASE 1 · PLAN

Garrison WiFi · TAK Off

CDR + S-shop · classroom / armory
  • Brigade roster loaded; T/O&E populated against MTOE template
  • Property-book and hand-receipt import; sub-hand-receipts assigned
  • Plan in /joint-ops — MDMP, sync matrix, running estimates
  • Rehearse decisions in /sandbox exercise mode against same data
  • Readiness rollup C-rating + P-rating + S-rating visible in /logistics
TAK state: OFF · /api/tak/status configured:false reachable:false
PHASE 2 · REHEARSE

Garrison WiFi · TAK Enabled

SAME unit · SAME plan · plus TAK clients
  • Set TAK_SERVER_URL + TAK_CLIENT_CERT + TAK_CLIENT_KEY env vars
  • /api/tak/status flips to configured:true reachable:true
  • Rehearsal traffic now flows outbound as CoT to ATAK / WinTAK / iTAK clients
  • Squad leaders see the same COP on their EUDs that the BN TOC sees
  • No re-keying, no re-loading the plan — toggle is environment, not data
TAK state: ON · ENV-GATED · CoT outbound via /api/tak/relay (admin-key gated)
PHASE 3 · MOVE

Field · DDIL Network

FTX / NTC / JRTC / CTC rotation
  • Same PWA installed on EUDs; UI shell + data layers + decision queue are offline-by-design (Service Worker + IndexedDB). Map basemap is operator-pre-cached: OFFLINE TILES panel on /field, /cop, /gps-denied lets the operator pre-cache the world at low zoom (z0–z5, ~6 MB) and any AO at high zoom (z0–z14) into the Service Worker tile cache before deployment — works fully offline within the cached scope. We do not ship a pre-loaded global high-resolution basemap (operator-driven, AO-specific by design).
  • Mesh / BLOS / Iridium gateways for backhaul when available
  • Field cues (/field or /phone) submit photos + GPS pins or anchor+bearing+range projections; EXIF GPS auto-extracts from photos when present
  • Live operator track on /field — TRACK ON/OFF starts watchPosition; phone draws its own breadcrumb trail (last 10 min, up to 200 points, dashed polyline — cyan for GPS fixes, amber for manual / EXIF-photo anchors) and accumulates distance since last anchor. Drift bound is the second number: foot 5%, wheeled 2% of distance walked / driven. REPLOT REQUIRED red banner appears when distance since last anchor exceeds 200m on foot (drift bound ±10m at trigger) or 500m wheeled (drift bound ±10m at trigger) — operator anchors via /pnt-toolkit (sun, Polaris, resection) or a fresh GPS fix, then RESET DRIFT zeros the accumulator. Thresholds match the operator decision interval, not the drift number itself.
  • GPS-denied: /pnt-toolkit gives operators 7 offline PNT methods (sun azimuth NOAA SPA, shadow-stick, Polaris, Southern Cross, two-landmark resection, dead reckoning, magnetic declination); /gps-denied is the jammer-awareness + uncertainty-growth simulator (R-330Zh, Pole-21, Iranian, DPRK profiles) with per-session trajectory + APPLY TERRAIN FIX
  • Peer-locate (/peer-locate) — when a teammate has GPS and you don't, they broadcast their position. AUTO MODE: peers who can see you POST their range-to-you; the page polls every 5 s and auto-solves the moment 3+ observations are within ±60 s of fresh observer beacons. MANUAL BACKUP: you pick 3+ peers and enter your own operator-estimated range to each (eyeball, pace count, map measure, landmark, or rangefinder). Browser solves Gauss-Newton least squares on a local tangent plane, draws a 1σ confidence ellipse (major × minor × orientation, not a circle — geometry-dependent anisotropy) on the map. When fresh peers drop below 3, falls back to dead-reckoning from the last fix using operator-set heading + speed × elapsed × 1.5; snaps back to AUTO the moment a 3rd fresh peer arrives. Honesty: not hardware ranging (web platform exposes no RSSI / time-of-flight / AoA), not authoritative GPS, not encrypted/authenticated — brigade-internal demonstration only.
  • All decisions queued locally; sync to enterprise on reconnection (audit chain preserved)
  • Squad → COCOM data path remains intact; latency is the only variable
TAK state: ON · DDIL TOLERANT · when configured, CoT is cached at the gateway and drained on link recovery
PHASE 4 · FIGHT

Live Fire · Operational

Real ROE, real safety chain
  • SAME plan that was rehearsed in Phase 2 — no re-platforming
  • ROE gate switches from EXERCISE to LIVE; engagement thresholds re-checked
  • Operator-detection remains decision support; AI never authors ballistic numbers
  • Counter-fire queue (/dod-cop) requires human APPROVE FIRE MISSION click
  • Hash-chain audit log captures every PROPOSE / AUTHORIZE / APPROVE for AAR
TAK state: ON · LIVE · same CoT stream when TAK is env-configured · ROE gate switched in audit chain

Unit Loader · How a Brigade Gets Loaded

Six import paths, all file-based and on-prem. Imports are scriptable for monthly refresh from the system of record. SHIELD/ATLAS does not claim a live API link to GCSS-Army, DRRS-Army, or DTMS — the official workflow is export-from-source-of-record, file-import-into-platform, audit-chain-preserved.

Roster · S-1

Personnel + chain of command

Per-soldier identity (last name, first initial, rank, MOS, unit position). Drives the echelon tree from BDE → BN → CO → PLT → SQD and seeds permissions per role.

CSV: rank,last,first_init,edipi,mos,unit_uic,position
Source: IPPS-A export (Army primary) · MILPDS export (Air Force) · legacy eMILPO supported · manual
MTOE / TO&E · S-3

Modified Table of Organization & Equipment

Authorized strength + authorized equipment per LIN/NSN. Templates available for IBCT, ABCT, SBCT, MEU, CSG, SOTF. Drives the fill-rate readiness math.

XML/CSV: uic,lin,nsn,nomenclature,auth_qty,paragraph_line
Source: FMSWEB MTOE/TDA authoritative source · GCSS-Army export (current) · legacy PBUSE supported
Property Book · S-4

Hand receipts + sub-hand receipts

On-hand qty per LIN, serial-tracked items per individual sub-hand-receipt holder. Reconciles to the MTOE for the fill-rate. Drives equipment-on-hand readiness (S-rating).

CSV: uic,lin,nsn,serial,sub_holder_edipi,nomenclature,condition_code
Source: GCSS-Army Property Book export · paper PBUSE forms
Readiness · S-3 / G-3

P · S · R · T ratings → C-level

Personnel (P), Equipment-on-hand (S), Equipment-readiness (R), Training (T) per unit. Computed from above three imports plus training records. Rolls up brigade C-rating.

XML: uic,p_rating,s_rating,r_rating,t_rating,c_level,as_of
Source: DRRS-Army CDR export · USR · manual G-3 entry
ATAK Data Package

Existing TAK-format unit data

If the unit already operates on ATAK, drop the data package (zip with .pref + CoT XML + KMZ overlays). Platform ingests unit symbols, named areas of interest, control measures, and overlays directly.

.zip containing: manifest.xml, *.cot.xml, *.kml/.kmz, *.pref
Source: existing ATAK Server pull · WinTAK export
Training Records · S-3

DTMS / individual training

Last training event, qualification dates, weapons-qual status, MOS-specific certifications. Feeds the T-rating in DRRS rollup and the per-soldier readiness card.

CSV: edipi,event_code,event_date,qual_status,instructor_edipi
Source: DTMS export · ATRRS pull · manual

Hard Rules · What We Have, What We Do Not Claim

Honesty Disclosures (briefable to a JCS J-3 / J-4)

Related Surfaces · Recommended Sequence

For an Army S-shop walkthrough, work the surfaces in this order:
1. Start here at /brigade-onboarding — load roster + MTOE + property book + readiness, pick TAK posture  →  2. Validate the data path on /unit-demo — spawn a test unit, see it appear across joint partners  →  3. Run device + sensor gate checks on /onboarding — 7-gate engine for EUDs and sensors  →  4. Detail S-4 / G-4 planning on /logistics — supply, fill rates, pacing items.
/onboardingZero-Configuration Tactical Onboarding — 7-gate engine for sensors and devices, runs on the production backend /unit-demoLive unit-spawn demo + multi-unit COP — adds a unit to the hierarchy, watch it appear across joint partners /logisticsS-4 / G-4 supply planning wizard, MTOE rollups, readiness pacing /sandboxExercise mode — same UI, same data, EXERCISE-gated ROE /joint-opsMDMP planning surface — battalion commander's view, three echelons up and down /setup-guideHardware + sensor + sensor-bridge installation
UNCLASSIFIED // FOR OFFICIAL USE ONLY SHIELD/ATLAS · ISS LLC