Skip to content

Using the App

This document describes common use-cases and scenarios for this App.

General Usage

Nautobot TRAX is typically used to plan and track mission communications paths, then tie those paths back to actual inventory and RF assignments.

Use-cases and common workflows

  1. Mission planning Create mission plans with deployment details and operational status.

  2. Frequency assignment Build mission frequency sets with TX/RX pairings, transport metadata, and optional satellite/provider links.

  3. Transport path design Define mission transport options across SATCOM and circuit workflows, assigning devices and supporting references.

  4. Operation rollup Group multiple mission plans under a single operation for execution tracking.

Missions with multiple kits

A Mission Plan has one Deployed Kit and any number of Supporting Kits, all linked to Nautobot tenants. The deployed kit must not also be selected as a supporting kit. Supporting kit memberships can be shared across missions; the existing one-mission-per-deployed-kit restriction is unchanged.

Select supporting kits on the Mission Plan create/edit form. The mission detail and list views show their tenant links, and the list can be filtered by supporting kit. The REST API accepts supporting_kits as a list of tenant IDs; an empty list clears the membership. To retrieve expanded tenant names, request ?exclude_m2m=false&depth=1.

RAMP's Deploy Kit saves these memberships before queuing Edge Sync, then passes the same deployed/supporting kit selection to the job. Enterprise mission prefill includes supporting kits and stages any tenants not yet present on the edge until the operator submits the form. Changing the selection replaces mission membership; it does not delete previously synced inventory.

Install the updated TRAX package and apply migration 0008_missionplan_supporting_kits on each participating Nautobot instance before using this workflow. Existing deployed-kit links are preserved. Previously selected supporting kits were only job inputs and must be selected again to persist them on an existing mission.

Screenshots

Representative screenshots are available in the App Overview.