VSI GLOBAL // ENTERPRISE ARCHITECTURE

Tablet Fleet

3 min read

Tablet Fleet

Deliverable SYS-005. Structure per cc02-standards/SYSTEM-STANDARD.md. Every component traces to a design basis (NEED/REQ) and to an acceptance criterion.

1. Purpose and Design Basis

1.1 Scope and Objective

The Tablet Fleet (v2) provides a tiered suite of Android tablet workstations for mobile command post monitoring, tactical vehicle navigation, and field deployment of ATAK-CIV (SYS-007).

1.2 Design Basis

This system configures three distinct hardware tiers to optimize cost, display area, and ruggedness based on operator role and environment. It replaces commercial default installations with MDM-managed, hardened profiles.

1.3 Needs

  • NEED-SYS-005-01: Team Leader and operators require common operating picture (COP) interfaces that display tactical maps and team locations.
    • Source: Team Leader (RF)
    • Context: Handsets have small screens; large-format tablet screens are required for vehicular and command post monitoring.
  • NEED-SYS-005-02: Detail operators require tiered ruggedness and form factor devices depending on operational environment and role.
    • Source: Operations Manager (BR)
    • Context: Operators in heavy weather require waterproof rugged frames, while detail planners require lightweight units.

1.4 Requirements

  • REQ-SYS-005-01 (Traceability: NEED-SYS-005-01): Tablets shall support local installation and offline rendering of ATAK-CIV map databases [VR-SYS-005-01].
    • Verification Method: Test (T)
  • REQ-SYS-005-02 (Traceability: NEED-SYS-005-02): Tier 1 tablets shall hold a certified MIL-STD-810H and IP68 rating for deployment in extreme environmental conditions [VR-SYS-005-02].
    • Verification Method: Inspection (I)
  • REQ-SYS-005-03 (Traceability: NEED-SYS-005-01): The tablet operating system shall enforce hardware-backed full-disk encryption with a boot passcode [VR-SYS-005-03].
    • Verification Method: Inspection (I)

2. Architecture As Built

+-------------------------------------------------------------------------+
| SYS-005 Tablet Fleet                                                    |
|                                                                         |
|  [Tier 1: Rugged 8.0"]  <-- Local Map Data --> [ATAK-CIV Client Engine] |
|  [Tier 2: Workstation 14"]                                              |
|  [Tier 3: Basic 10.1"]                                                  |
|                                                                         |
+-------------------------------------------------------------------------+

3. Components and Bill of Materials

ComponentSpecVendor / LinkPriceTierStatusTraceability
Tier 1 TabletSamsung Galaxy Tab Active 5 8.0 SM-X306B 128/6GB 5G ruggedizedAmazon$699.991SELECTEDREQ-SYS-005-02
Tier 2 TabletUrao 14in Android 16, 30GB/256GB, WiFi 6Amazon$239.992SELECTEDREQ-SYS-005-01
Tier 3 Tablet10.1in Android 16 (2026), 24GB/256GB, T606, Widevine L1Amazon$117.603SELECTEDREQ-SYS-005-01

4. Build and Deployment

4.1 Device Initialization

  1. Unbox tablets and complete basic configuration without internet connection to prevent telemetry collection.
  2. Update OS to the latest stable vendor release using localized files.
  3. Install Android Debug Bridge (ADB) on administrative workstation and pair the tablet.

4.2 Application Installation

  1. Sideload ATAK-CIV (SYS-007) and required map plugins.
  2. Load regional map packages (ART-region-package) onto the external storage partition or dedicated data folder.
  3. Configure the local connection profile to sync coordinates over the mesh network (SYS-004).

5. Hardening Baseline

  • OS Hardening: Disable developer mode after configuration; remove pre-installed bloatware and unnecessary packages via ADB; disable location history and Google telemetry interfaces; configure user profile lockouts [REQ-SYS-005-01].
  • Encryption: Enforce full-disk encryption using AES-256; require a minimum 8-character alphanumeric boot password [REQ-SYS-005-03].
  • Network Hardening: Restrict default network connection profiles to prefer WireGuard VPN; configure the firewall to block non-VPN egress traffic.

6. Integration Points

  • Inputs: Requires ART-engagement-order (Provides authorized deployment periods).
  • Produces For: SYS-007 (ATAK client configuration).

7. Acceptance Tests

CriterionMethodExpected ResultReference
REQ-SYS-005-01TestOpen ATAK-CIV on the tablet, load offline map data, and verify coordinates render correctly without internet access.VR-SYS-005-01
REQ-SYS-005-02InspectionVerify that manufacturer certificates confirm MIL-STD-810H and IP68 compliance.VR-SYS-005-02
REQ-SYS-005-03InspectionVerify Android settings confirm that device encryption is active and pin lock is enforced.VR-SYS-005-03

8. Run and Maintenance Handover

  • Storage Procedure: Store tablets inside Faraday shield bags when not active to prevent location tracking.
  • Battery Management: Recharge and cycle tablet batteries every 30 days to prevent degradation.
  • Ownership: Systems Engineer (CS) for security updates; Operations Manager (BR) for inventory custody management.

END OF SYSTEM

Model wiring

Generated from cell frontmatter at publish time.

Graph View

Backlinks