tuds-installation-prerequisites
Complete these items before you create a SQL Bridge or expect Mission Control features that read Vista SQL data. For the full cross-product view, see the Robonauts Setup Requirements Matrix.
Who should do this
- Team captains and IT admins standing up a new TUDS team.
- Anyone preparing the Windows host that will run SQL Bridge.
Required before setup
-
Windows 10/11 (64-bit) host near SQL Server
The SQL Bridge runs on a Windows machine that can reach your Vista SQL Server. See Windows Host Requirements. -
Outbound HTTPS to tuds.ai
Required for the web app and for the SQL Bridge to validate and operate. See tuds.ai Connectivity. -
Vista SQL Server access from the bridge host
Know the SQL Server host, port, database name, and login. See Vista SQL Access Overview. -
SQL credentials
Create or confirm a SQL login the bridge will use. See Create SQL Account. -
Cloud SQL path (cloud customers only)
TLS Database Endpoint or IPsec VPN must already be available so the bridge host can reach SQL. See Cloud SQL Connectivity. -
Team subscription / entitlement
Captains activate the team plan in Team Billing after users are added. See Team Onboarding for Captains. -
Office public IP
Needed when creating the SQL Bridge in Team Settings → Connectors. -
SQL Bridge package ready to install
You will download the bridge installer and config from TUDS after creating the bridge. See SQL Bridge Customer FAQ.
Not required for TUDS
- Microsoft Excel
- SAP Crystal Reports runtime
- .NET 8 / .NET Framework 4.8 (on end-user browsers)
- Vista client on every user workstation (only the bridge host needs SQL reachability)
Ready checklist
- Bridge host Windows machine identified
- SQL Server host, database, and credentials known
- Cloud TLS/VPN path confirmed (if cloud)
- Office public IP known
- Outbound HTTPS from bridge host confirmed
- Captain can sign in to Mission Control
What to do next
- Getting Started with TUDS
- Team Onboarding for Captains (users → billing → bridge → Vista Configs sync)
- SQL Bridge Troubleshooting if the Wi‑Fi status icon stays unhealthy