1.2.3 Post physical installation UAT

Once the terminal is physically installed and a Service Line has been created in the Orbius Portal, complete the following UAT procedure before signing off the site.

Step 1: Create the Service Line in the Orbius Portal

If you have not already done so, create a Service Line and assign the terminal. See Article 2.3 — How to Create a Service Line. The terminal cannot transmit or receive data until a data subscription is allocated.

'Create New Service Line' Form 

Step 2: Reboot the terminal via the Portal

1.    Log in to portal.orbius.com and navigate to the Service Line

2.    In the Devices section, click Reboot

3.    Wait 3–5 minutes for the terminal to come back online

4.    Confirm the telemetry graphs show the terminal is active again

Overview of Device section in the 'Service Line Details' page

Step 3: Verify internet connectivity

1.    Connect a laptop or test device directly to the Starlink UT Ethernet port using a standard Ethernet cable

2.    Confirm you receive an IP address in the 192.168.100.x range

3.    Open a browser and run a speed test (e.g., fast.com or speedtest.net)

Expected throughput values under clear sky:

Terminal	Expected download	Expected upload
Starlink Mini	~100–200 Mbps	~20–40 Mbps
Starlink Enterprise	~100–200 Mbps	~20–40 Mbps
Starlink Performance Gen 2 (former Flat High Performance)	~150–250 Mbps	~30–50 Mbps
Starlink Performance Gen 3	~200 Mbps or higher	~40–80 Mbps

📌  Note: Actual speeds vary depending on environmental factors, network load, and satellite visibility. These benchmarks apply under clear sky at low network congestion.

 

Step 4: Validate telemetry KPIs in the Portal

In the Orbius Portal, check the telemetry panel for the Service Line. Use the time selector to view the last 15–30 minutes of data.

KPI	Target at UAT	Investigate if...	Fail action
Downlink throughput	≥100 Mbps (Mini) / ≥250 Mbps (Performance Gen 3)	<50 Mbps consistently	Check obstruction, reboot terminal, check cable speed negotiation
Latency	30–60 ms	Consistently >100 ms	Persistent high latency may indicate satellite link issue — escalate to L2 if reboot doesn't resolve
Ping drop rate	0–1%	>3% sustained	>3% indicates connectivity instability — check obstruction, cable, reboot
Signal quality (SNR)	≥80%	<80%	<80% typically means obstruction — re-check app obstruction score
Obstruction percentage	<0.2%	>0.2%	>0.2% reposition antenna. Target 0.0%

• Related Articles

• 1.2.2 Hardware installation guide

  This article covers the hardware installation process for all Starlink terminals in the Orbius portfolio. Follow the model-specific Starlink setup guide for physical mounting instructions. Before you begin Confirm all pre-requisites in Article 1.1 ...

• 1.1.1 Installation Pre-Requisites Checklist

  ⚠️ Important: Do not schedule an installation visit until every item in this checklist is confirmed. Skipping this step is the single most common cause of failed deployments. 1. Commercial and access pre-requisites • Signed agreement with Orbius, ...

• 1.2.4 UAT Troubleshooting - Common Failure Scenarios and Fixes

  If the terminal fails UAT, work through the following failure categories in order before escalating to Orbius (L2 support). Category Likely issue Diagnostic Fix A. No IP address DHCP not assigned by Starlink UT Run ipconfig/ifconfig — if 169.x.x.x ...

• 1.1.2 How to Conduct a Site Survey: Step-by-Step Guide

  A site survey must be completed and signed off before any hardware is installed. The Starlink App must be used on-site to validate antenna placement, there is no acceptable alternative for obstruction validation. Step 1: Site identification Record ...

• 1.2.1 Starlink Terminal Portfolio Overview

  Orbius, as a Starlink Authorized Reseller, offers the following Starlink terminal models. Select the appropriate model based on use case, deployment type, and performance requirements. Terminal Best for Key characteristics Starlink Mini Temporary ...