Tablet Command Integration

---

Prerequisites

• Upgrade your FVCAD Server to version 6.9.2.0 (or greater).
• We recommend first upgrading your Test CAD environment before production.

---

Configuration in Flight Vector

1. Go to Settings → 3rd Party Settings → TabletCommand (or search TabletCommand)
2. Enter your unique API Key in the TabletCommand API Key field.
3. Confirm the following default settings (see screenshot below):
   • TabletCommand Host: api.tabletcommand.com
   • TabletCommand Port: 443
   • TabletCommand Secure: On
   • TabletCommand Enabled: Set to On once configured

---

Asset Setup

1. Under Asset Custom Fields, add two new text boxes with the following Save As values:
   • tablet command id
   • radio name
2. Populate these fields for each asset with the values used in Tablet Command.
   • Each value must be unique per asset.

---

Notifications & Manual Actions

• When Flight Vector CAD receives a manual command from Tablet Command, a notification will appear in the Notification window.
• To act on it:
  1. Right-click the notification.
  2. Choose one of the following:
     • Dismiss
     • Dismiss with notes
     • Perform the suggested action
• If dismissed, details are stored in the EventViewItems database table.
• If the command is invalid, the notification will indicate it is unexpected.

---

Command Actions Between Systems

• DIS (Dispatched) → User may assign the asset to an existing request (dropdown menu).
• RES (Responding) → Asset departs automatically from the first waypoint.
• ONS (On Scene) → Asset arrives automatically at the pickup location.
• TRS (Transporting) → Asset departs automatically from the patient pickup.
• ATH (At Hospital) → Asset arrives automatically at the drop-off location.
• OOS (Out of Service) → User selects the OOS reason from the standard dialog.
• INS (In Service) →
  • If out of service for one reason → standard in-service comment/time box opens.
  • If multiple reasons → user selects which reasons are no longer applicable (checkboxes).
• ATP (At Post) → User sets the asset’s last known location (defaults to selected Post, but any location can be chosen).

---

Important Notes

• If fuel and/or risk values are required by settings, Tablet Command actions bypass these checks during departure/arrival.
• The system will warn if these fields are missing before closing the request.
• Users with Required Field Rule Override permissions may bypass these requirements.
• Users without this permission must manually add the values before closure.