--- title: "Choosing a Tactical Satcom Terminal: 7 Questions Every Procurement Team Should Ask" date: "2026-10-28T16:06:05+00:00" url: "https://hiskysat.com/resources/articles/tactical-satcom-terminal-buyers-guide/" description: "A practical buyer's guide for comparing military satellite terminals, from SWaP budget to IP ownership." --- # Choosing a Tactical Satcom Terminal: 7 Questions Every Procurement Team Should Ask [← Blogs & Articles](https://hiskysat.com/resources/?type=articles)Blogs & Articles A practical buyer's guide for comparing military satellite terminals, from SWaP budget to IP ownership. Most tactical satcom terminal datasheets read alike, and that sameness is the first trap in any military satellite terminal evaluation. A phased array, a frequency band, a data rate and a weight say little about how a terminal behaves under jamming, during integration, in a swarm or when an export approval lands on someone’s desk. Those are the moments that decide a program. The seven questions below belong in your RFP before any vendor starts answering, so that every supplier is measured against the same evidence. In my experience, a terminal can look fully compliant on paper, yet real-world integration and operational testing often expose performance gaps the datasheet never shows. ## Mapping the Seven Questions to What Matters Each question maps to a technical dimension and to a piece of proof you can request in writing, or in a proof of concept, to allow the committee to separate what a vendor claims from what it can actually demonstrate. - **SWaP budget.** Tests: weight, peak and standby power, volume. Proof to request: measured figures for the whole terminal. - **LPI/LPD proof.** Tests: low-signature behavior under jamming and detection. Proof to request: test evidence and the spreading approach. - **Orbit flexibility.** Tests: GEO, LEO, Ku and Ka. as demonstrated in the past (Ella-1). - **Network ownership.** Tests: who runs gateways, routing and management. Proof to request: an architecture showing where traffic goes. - **Integration support.** Tests: interfaces, ICDs, platform adaptation. Proof to request: named integrators and interface documents. - **Total cost.** Tests: terminal, hub, NMS, airtime, lifecycle. Proof to request: an itemized model at your volume. - **In-house vs outsourced IP.** Tests: who controls each element of the design. Proof to request: which elements are built in-house. Score every vendor against the same list and file the scores with the evidence behind them. That record is what the committee will rely on when the decision is reviewed later. ## The Seven Questions in Detail ### 1. What is our real SWaP budget? On a loitering munition or a small UAV, size, weight and power decide whether the terminal flies at all. Ask for the weight and dimensions of the complete unit, power draw in standby and in simultaneous transmit and receive, input voltage range, and environmental ratings such as ingress protection and operating temperature. If your integrator wants to embed the terminal, ask whether the modem and RF stages come at card level. A terminal that wins on antenna size and loses on power draw has only moved the problem. ### 2. Can the vendor prove LPI/LPD? Low Probability of Intercept and Low Probability of Detection are easy to print on a brochure, so ask how the signal achieves them. Wide-range frequency spreading, low-signature waveforms and the terminal’s behavior when idle all matter, and each claim should come with test evidence. Then ask whether the terminal depends on GNSS. GPS denial is routine in contested environments, and a terminal that needs navigation data to point its beam inherits a weakness no waveform can hide. **Related reading:** Operating Without GPS: Designing GPS-Independent Satcom for a Jammed, Contested Battlefield ### 3. How flexible is the orbit? A terminal tied to one constellation ties your program to that constellation’s schedule, pricing and policy. Look for Ku and Ka band support, GEO and LEO capability, a satellite-agnostic design and, above all, a demonstrated handover between orbits. **Related reading:** [Why Multi-Orbit Satcom Is the New Resilience Strategy for Military Satellite Networks](https://hiskysat.com/resources/articles/multi-orbit-satcom-resilience-strategy/) ### 4. Who owns the network? Ask where your traffic is routed, which gateways it touches, who operates the network management system and whether that system can run on your premises, including fully air-gapped. In a private network, traffic reaches only your gateways. In a shared network, however good, someone else holds a switch. Ask also whether channels can be split between shared fleet management and dedicated on-demand use, since that is how operations actually run. ### 5. What integration support comes with the terminal? Integration work starts where the datasheet ends. Ask for the interface control documents, the electrical and data interfaces, how platform position, attitude and velocity reach the terminal, and whether the vendor will adapt the antenna or modem to your platform. Ask which integrators have already fielded the terminal, and on which platforms. A vendor that has done the integration before has already met the problems you are about to meet. ### 6. What does total cost really include? Unit price is the cheapest number in the room. Build the model around the whole system, including terminals, HUB, network management, satellite capacity, integration effort, re-certification after any change, sustainment, and the cost of leaving if the vendor or constellation changes its terms. Price it at the volume you plan to field. A terminal that is affordable in tens can become a budget problem in thousands. **Related reading:** The Munitions Math: Why “Low-Cost and Plenty” Is Rewriting the Case for Affordable Satcom ### 7. Who owns the IP, and who built it? A vendor that assembles terminals from outsourced modems, third-party hubs and licensed management software can still pass a first evaluation. The trouble starts when you ask for a change, a fix or an export approval. In-house development of terminal, HUB and network management gives you one support chain and lets the vendor customize at the pace of your program. Ask which elements are built in-house, which are licensed, and who is allowed to modify them. ## What the Evaluation Is Protecting If you sit on the evaluation, you will have to defend the decision afterward, and a choice that looked fine on paper and failed in the field stays with you for years. If you run the integration, the risk arrives sooner. A terminal that misses its weight budget by a few hundred grams, or draws more power than the platform can supply, sends you back to redesign. Both sides face the same quiet threats, namely hidden costs, schedule slips, vendor lock-in and the dependency nobody listed in the RFP. One question I always encourage evaluation teams to ask is: “What evidence can you provide that the terminal will meet these requirements in our actual operating environment, not just under laboratory conditions?” ## Applying the Checklist to HiSKY Here is how HiSKY answers the seven questions. The company develops its Private Satellite Networks end to end, with terminal, HUB and NMS built in-house, so every answer comes from a single supplier. - **SWaP budget:** terminals from 1.4 kg to under 6 kg, drawing under 10 W in standby - **LPI/LPD proof:** integrated LPI/LPD with wide-range frequency spreading, and GPS-independent operation. - **Orbit flexibility:** Ku/Ka band GEO/LEO multi-orbit capability with smooth handover. - **Network ownership:** Private Satellite Networks route traffic only to customer gateways. Space Control NMS runs on premises or fully air-gapped. - **Integration support:** customized integration, platform-specific antenna and modem adaptation, and defense programs delivered with leading system integrators. - **Total cost:** one vendor for terminal, HUB and NMS, engineered for affordable rollout across fleets. - **In-house vs outsourced IP:** terminal, HUB and NMS developed fully in-house. HiSKY has delivered thousands of terminals worldwide, on land, air and maritime platforms. ## Before the First Demo Send the seven-question list to every shortlisted vendor before the first demo and ask for the proof back in writing. The answers that arrive with test reports, interface documents and an itemized cost model at your volume have earned a demo slot. **Talk to HiSKY about your next tactical satcom terminal program** [hiskysat.com](https://hiskysat.com/) | **By the HiSKY Pre-Sales Engineering Team** [← Back to Blogs & Articles](https://hiskysat.com/resources/?type=articles)[Contact HiSKY →](https://hiskysat.com/contact/)