Dismounted · Ranges · Command posts

Stand up a TAK server, instrument the weapon, review the day.

The server is normally the part that costs weeks to stand up and somebody who knows Linux to maintain it. Ours runs in minutes with full administrator access. VICE weapon sensors report through ATAK, the server keeps the record, and MARS replays it for the debrief.

A single operator on a mountain ridge
Plate 1 Dismounted, the client side is one Android device running ATAK. The clients are free and the standard is open; the part you buy from us is the server behind them and the record it keeps.
1.0
Scope

Where a cycle loses time

Three places a training cycle or a deployment gives time away. Each one is a thing we sell against, and each is stated below with what actually replaces it.

1.1

Standing up the server

A certificate authority, TLS, data packages, user provisioning and a Linux box somebody has to own for as long as the unit uses it. That is the week you get back: an EOTAK Server is hosted and patched by us, and you get full administrator access to it from the first minute.

1.2

Instrumenting the weapon

VICE modules report shots and weapon pose from the weapon itself. The sensing is onboard: there is no external sensor, nothing bolted to the outside, and no change to how the weapon is carried or cleared. Reporting is over Bluetooth to ATAK; see 2.0.

1.3

Reconstructing what happened

The debrief usually starts from memory and a whiteboard. MARS replays the day from the record the server already kept, so it starts from the track instead. It runs afterwards, not during.2

2.0
Reporting path

The reporting path

Three nodes, in this order and no other. The weapon sensor talks over Bluetooth to the Braveheart ATAK plugin inside ATAK; ATAK writes the Cursor on Target message and talks to your EOTAK Server; the server holds the record. MARS reads that record afterwards.

Figure 1: the reporting path A weapon sensor on the weapon reports over Bluetooth to ATAK on the end-user device, which sends a Cursor on Target message to the EOTAK Server. The server holds the record, and MARS reads that record after the fact. REPORTING PATH FIG. 1 WEAPON SENSOR VICE Glock Module, Core or URS ON THE WEAPON BLUETOOTH SHOTS · POSE ATAK Braveheart ATAK plugin ANDROID, ON THE DEVICE CURSOR ON TARGET EOTAK SERVER Hosted, patched, full administrator access IT HOLDS THE RECORD AFTER THE FACT MARS After-action replay
Fig. 1 Weapon sensor → ATAK → EOTAK Server. The plugin sits inside the ATAK hop rather than beside it, so the chain is three nodes long. MARS is drawn on a dashed line because it reads the record afterwards; it is not a hop.
What is not on this path

EOTAK Stack is not a link in the chain. It pairs with a module directly over Bluetooth and shows that module’s live readout (firmware version, battery, shot count, and roll, pitch and yaw as they move) and it pushes firmware over the same connection. Stack talks to the module in front of you; it is not the reporting path. ATAK is what puts the event on everyone else’s map.

3.0
Components

What you actually run

Four things, and only one of them is proprietary to us.

3.1  Server
A managed TAK server, hosted, patched and monitored by us, with full administrator access for you. Your certificate authority, your users, your data packages. DigitalOcean, or AWS GovCloud where the work requires it.
3.2  Clients
ATAK on Android. TAK is an open standard and the clients are free, so nothing about the picture on the device is ours to charge for or to lock. EOTAK Stack sits alongside it for plugins, map packages and sensor firmware, on Android and iOS.
3.3  Sensors
Three VICE weapon modules: pistol backstrap, AR grip and Picatinny rail. Each reports shot detection and weapon pose from onboard motion analysis. Full comparison in 4.0.
3.4  Replay
MARS, included on every plan. Playback at 1×, 5×, 10×, 20× and 30×; 14 basemaps, none of which need an account; measurement in six units; export to PDF, CSV, KML and GPX so the record leaves with the unit.
4.0
Sensor data

Weapon sensors, compared3

The three VICE modules differ in where they mount and what they weigh. What they report, and the path they report it on, is the same for all three.

Specification VICE Glock Module VICE Core VICE URS
PlatformGLOCK Gen5 backstrapMagpul® MOE and K2 grips, standard ARMIL-STD-1913 (Picatinny) rail
MountInto the backstrapInside the gripQuick-detach throw-lever
ReportsShots · pose · holster draw and re-holsterShots · pose · aim down sightsShots · pose · aim down sights
Weight0.43 oz (12.19 g)0.40 oz2.47 oz (70 g)
Battery100 mAh350 mAh350 mAh
ChargingUSB, in place on the firearmUSB, in place on the firearmUSB
FirmwareEOTAK Stack over BluetoothEOTAK Stack over BluetoothEOTAK Stack over Bluetooth
ModelVICE-G3FVICE-COREVICE-URS
Price$299.99$299.99$299.99
Full pageVICE Glock Module →VICE Core →VICE URS →
Scroll the table sideways on a narrow screen
5.0
Hosting

Hosting and posture

Three statements, each with the authority named. Nothing here is an adjective doing load-bearing work, and the sentences are kept separate on purpose. Collapsing them would be a claim we cannot make.

5.1

The substrate is authorized

Servers can run in AWS GovCloud: isolated US regions, operated by US persons, FedRAMP High authorized, with a DISA provisional authorization at IL5. That authorization is held by AWS.

5.2

Our service is aligned, not authorized

We engineer GovCloud deployments against the IL4 control set. We do not hold our own ATO, and a provisional authorization on the infrastructure is not one.

5.3

Your ATO is yours to issue

At IL4 and above a mission owner grants the authorization for the system. Reciprocity from the substrate is a discount on that work, not a substitute for it.

5.4

Ask before you assume

If you need a specific authorization, tell us and we will answer in writing about where we actually are. On a page with no logos on it, that is the only proof worth offering.

6.0
Pricing

Published pricing4

Nobody else in this category publishes a number. Ours is on the site, in a table, where you can put it in a budget line without asking anyone for a demo first. There is one plan, priced per user, per year, and the rate falls as the seat count rises. The rows below are a sample; every threshold is on the full rate card.

Seats Effective rate Annual total Unit
5$162.00$810.00Per user, per year
25$92.40$2,310.00Per user, per year
10$120.00$1,200.00Per user, per year
50$90.00$4,500.00Per user, per year
More than 50By quote, contact sales
Compliance$10,800.00Per server, per year, see 5.0
MARS is included at every seat count · no setup fee
7.0
Notes

Notes

The qualifications that belong with the statements above, kept where they can be read rather than buried in them.

  1. 1

    ATAK is Android only. That is Team Awareness Kit’s constraint, not ours, and every ATAK plugin inherits it, including the Braveheart ATAK plugin. Our own applications are cross-platform: EOTAK Stack and EOTAK Beacon are both Android and iOS.

  2. 2

    MARS is after-action review. It replays a record the server has already written, and it is not a live tracking product.

  3. 3

    VICE hardware is quoted, not sold from this page. Availability and lead time come back with the quote. Full specifications, wireless details and box contents are on each sensor’s own page.

  4. 4

    Seats are charged in graduated bands: the seats inside each band pay that band’s rate, and the totals are added together. The effective rate in the table is the resulting total divided by the seat count, not a single band’s rate, so a seat count between two thresholds lands between two rates. There is no setup fee, and MARS is included at every seat count. The compliance addon is flat per server and is never multiplied by seats.

End of document

Stand one up and run it.

Managed TAK servers priced per user, per year, with MARS at every seat count. If the answer you need is a compliance answer, ask for it in writing and you will get one.

EOTECH® · Clarksville, TN · +1 (931) 266-0888