Guided tutorial
This tutorial follows the real private console path. It covers local evaluation first, then explains what changes when a deployment owner runs the same workflow on a self-hosted reference instance.
1. Local sign-in
For local evaluation, an administrator starts the app and staff open /admin/local-login. Choosing Start setup opens a private browser session for the Operations Console.
Self-hosted difference: production access starts with a one-time first-admin setup link, then password sign-in at /admin/login. The local sign-in shortcut is for local/demo operation only; SSO/OIDC is future work.
2. Start page
The Start page shows the current product state and the ordered workflow: setup, schedule import, feed URLs, vehicle data, realtime review, issue fixing, maintenance, and authorized sharing preparation.
Self-hosted difference: the same page should reflect deployment-owned public base URLs and server-side service state.
3. Set up agency
Agency Setup keeps profile, public feed metadata, contact, license, schedule, vehicle data, validation, and maintenance ownership in one browser-first checklist.
Self-hosted difference: deployment owners should replace local placeholders with the reference deployment hostname, monitored contact, and owner assignments before sharing URLs.
4. Import a schedule
Use Import Schedule or Schedule Review to load a schedule, confirm required files, review import history, and understand validation guidance before checking public feed URLs.
Self-hosted difference: the deployment owner must decide which source schedule is allowed for the hosted environment.
5. Check feed URLs
Feed Health shows discovery, static GTFS, Vehicle Positions, Trip Updates, and Alerts. Missing or stale rows link back to the next private console action.
Self-hosted difference: public URLs should use the deployment-owned hostname and reverse proxy path.
6. Connect vehicle data
Devices, Telemetry Freshness, Realtime, and Connectors show whether vehicles are sending fresh data and which connector category fits the deployment.
Self-hosted difference: credentials, sidecars, payload mappings, and retention rules stay under deployment-owner control.
7. Review connector options
Connectors shows which adapter shape fits telemetry, prediction, validation, monitoring, or discovery work before any real endpoint, credential, or vendor payload is introduced.
Self-hosted difference: a deployment owner controls sidecars, secrets, payload mapping, and network sends.
8. Review realtime output
Realtime review separates fresh vehicles, stale rows, unmatched vehicles, Vehicle Positions, Trip Updates diagnostics, and Alerts lifecycle status.
Self-hosted difference: production-like checks still need deployment-specific validator and monitoring review.
9. Review readiness
Readiness shows remaining gaps across metadata, schedule, feed health, validators, telemetry, realtime output, maintenance, and future sharing preparation.
Self-hosted difference: readiness should use deployment-owned base URLs and local/reference diagnostics without changing consumer statuses.
10. Maintain the deployment
Maintenance and Help show routine checks, owner responsibilities, backup and restore guidance, validator setup, support summaries, and update planning.
Self-hosted difference: these tasks become routine deployment-owner responsibilities.
These captures are tutorial assets from local/demo UI review. They do not show private agency data, secrets, external portals, consumer submissions, vendor payloads, or proof of production readiness.