Satellite Communications for Engineers Training Course

A practical grounding in Satcom for engineers who didn’t come up through the space industry.

Overview

Satellite links are turning up in places they never used to. Remote sites that were once happily isolated now need connectivity. Maritime, energy, rail, utilities, broadcast, defence, emergency services and industrial operators are all buying satellite capacity – and increasingly, so are organisations who simply want a diverse path when the fibre gets cut.

The engineers asked to specify, integrate, troubleshoot or depend on those links are usually not satellite specialists. They’re network engineers, control and instrumentation engineers, RF engineers from terrestrial backgrounds, systems engineers and technical managers who now own a satellite dependency they didn’t design.

Satellite Communications for Engineers closes that gap. It’s a vendor-neutral course that explains how Satcom actually works, what it can and can’t do, and how it behaves when it’s wired into a wider system. No orbital mechanics derivations, no marketing. Just the working knowledge you need to make good decisions and ask suppliers the right questions.

Who this course is for

This course is written for practising engineers coming from other industries — people with a solid engineering foundation who need to get up to speed on satellite quickly and accurately.

It suits you if you:

• Are specifying, procuring or reviewing a satellite service and want to evaluate the claims being made
• Have inherited a satellite link as part of a network, control system or resilience plan
• Design systems that will be deployed somewhere terrestrial connectivity doesn’t reach
• Need to troubleshoot performance problems where the satellite hop is the prime suspect
• Are responsible for continuity, resilience or risk and need to understand where satellite dependencies actually sit
• Work alongside satellite specialists and want to hold your end of the conversation

Assumed background: general engineering competence and basic familiarity with networking or RF concepts. No prior satellite experience required. The maths is kept to what’s genuinely useful — you’ll leave able to read a link budget and understand what each term is doing, not able to derive one from first principles.

What you’ll be able to do afterwards

By the end of the course you will be able to:

• Explain the practical differences between GEO, MEO and LEO systems, and choose sensibly between them for a given application
• Identify every major component in a Satcom system and describe what it does and how it fails
• Read and interpret coverage maps, beam plans and service specifications critically
• Predict the latency behaviour of a link and anticipate how applications and protocols will react to it
• Recognise where satellite and terrestrial systems interact — and where those interfaces cause problems
• Map your organisation’s real dependencies on satellite and satellite-derived services, including timing and positioning
• Set realistic expectations with stakeholders about availability, throughput, contention and weather
• Ask suppliers the questions that separate a genuine service description from a brochure

Course content

1. Satellite communications fundamentals

The foundation everything else rests on. What a satellite link physically is, and why it behaves the way it does.

• Orbits, altitude and why orbit choice drives almost every other characteristic
• The frequency bands in use — L, S, C, X, Ku, Ka and the move into Q/V — and what each is good and bad at
• Free-space path loss, EIRP, G/T and the anatomy of a link budget, explained in plain terms
• Modulation and coding: DVB-S2X, MODCODs, adaptive coding and modulation, and why your throughput changes with the weather
• Bandwidth, symbol rate and spectral efficiency — where the megabits actually come from
• Multiple access schemes and how capacity gets shared between users
• The vocabulary: transponder, bent pipe, uplink and downlink, carrier, footprint, contention

2. GEO, MEO and LEO systems

The single most consequential decision in Satcom, and the trade-offs behind it.

• GEO at approximately 35,786 km: fixed pointing, huge coverage from a single spacecraft, mature ecosystem, and roughly a quarter of a second of one-way delay
• MEO in the intermediate orbits: a middle ground on latency and coverage, with tracking requirements and a smaller constellation
• LEO at a few hundred to a couple of thousand kilometres: low latency and high throughput, at the cost of large constellations, constant handover and a fast-moving commercial landscape
• Constellation design: how many satellites you need, and why, for a given coverage guarantee
• Polar and high-latitude coverage — where GEO stops being an option at all
• Highly elliptical and non-standard orbits, and where they’re used
• Antenna and terminal implications: fixed dish versus tracking versus electronically steered flat panel
• How the three tiers are increasingly used together rather than as competitors

3. Satcom architecture and system components

An end-to-end walk through a working system, so you know what every box does before you have to specify or troubleshoot one.

• Space segment: platform versus payload, transponders, bent-pipe versus regenerative and on-board processing, spacecraft power and lifetime
• Ground segment: gateways and teleports, hub equipment, network operations, TT&C, and the terrestrial backhaul behind the dish
• User segment: VSAT terminals, block up-converters and low-noise blocks, modems, antenna types and sizing, installation and pointing realities
• Control and management: network management systems, bandwidth allocation, service assurance and monitoring
• High-throughput satellites, multi-beam architectures, frequency reuse and beam hopping
• Where the interfaces and demarcation points sit – and who owns which fault
• What “software-defined” and “flexible payload” mean in practice for a buyer

4. Coverage and performance trade-offs

Reading a service offering for what it is, rather than what the datasheet implies.

• Interpreting footprint and EIRP contours, and what beam edge really means for your site
• Spot beams versus wide beams: capacity density against coverage area
• Elevation angle, look angle, obstruction and skew – why the same service performs differently 200 km away
• Rain fade and atmospheric effects by band, availability targets, and what “99.5% availability” actually buys you
• Antenna size, terminal power and cost as trade-off levers
• Contention, oversubscription, committed information rate versus best effort, and fair-use policies
• Throughput versus availability versus cost: choosing which one to sacrifice
• Interference, adjacent satellite interference and the discipline of correct pointing

5. Latency and operational implications

The topic that catches out more engineers than any other – because the link “works” and the application still doesn’t.

• Where the delay comes from: propagation, processing, acquisition, queuing and the terrestrial tail
• Round-trip time by orbit class, and what each range rules in or out
• Why TCP performs badly over long-delay links, and what performance-enhancing proxies do about it
• The interaction between encryption, VPNs and acceleration — and why turning on the VPN halved your throughput
• Voice, video and interactive applications: what’s tolerable and what isn’t
• Real-time control, SCADA, telemetry and remote operation over satellite
• Cloud and SaaS applications over a satellite link: chatty protocols and their consequences
• Jitter and variability, not just average delay
• Designing applications and expectations around the delay rather than fighting it

6. Links between satellite and terrestrial systems

Satellite is rarely an island. This is where most real-world integration problems live.

• Satellite backhaul for cellular and remote networks
• Hybrid and multi-path architectures: SD-WAN, path selection, failover and load sharing across satellite and terrestrial
• Getting failover right – detection, thresholds, flapping, and the failover that never actually fired
• IP over satellite: addressing, routing, MTU, fragmentation and quality of service
• Non-terrestrial networks in 3GPP standards, and direct-to-device services
• Interfacing with enterprise networks, security zones and firewalls
• Timing and synchronisation, and satellite’s role in distributing it
• Where terrestrial assumptions silently break once a satellite hop is in the path

7. Resilience and dependency awareness

The strategic layer. Understanding what you actually depend on – including the dependencies you didn’t know you had.

• Mapping satellite dependencies across an organisation, including indirect ones
• The GNSS question: positioning, navigation and timing as a critical hidden dependency, and the consequences of losing it
• Interference, jamming and spoofing: what’s realistic, how it presents, and how it’s detected
• Single points of failure – gateways, teleports, single satellites, single providers, single landing points
• Space weather, orbital congestion, debris and end-of-life considerations
• Supply chain, licensing, landing rights and regulatory constraints on where you can operate
• Diversity strategies that genuinely help versus those that only look like diversity
• Building resilience cases and contingency plans that survive contact with a real outage

8. Practical Satcom limitations and expectations

An honest closing session on what Satcom will and won’t do for you.

• What satellite is genuinely good at, and where it’s the wrong answer
• Realistic throughput, cost per gigabyte and the commercial models you’ll encounter
• Site realities: power, mounting, environment, line of sight, maintenance access, spares
• Installation, commissioning, type approval and regulatory hurdles
• Service level agreements: what’s actually guaranteed and what’s carefully worded
• Common failure modes and a structured approach to first-line diagnosis
• Managing stakeholder expectations, especially where “satellite internet” is assumed to work like fibre
• Where the industry is heading, and how to make decisions that don’t age badly

How it’s delivered

The course is delivered as an instructor-led programme and can be adapted to the audience and time available. Typical formats:

• One-day overview — the essentials, aimed at mixed technical teams
• Two-day course — the full syllabus with worked examples, exercises and discussion time
• Tailored in-house delivery — reweighted towards your sector, systems and use cases, using your own architectures as examples

Available on-site at your premises, at a venue, or delivered live online. Participants receive course notes, reference material and a set of practical checklists for evaluating satellite services.

Why this course

Vendor-neutral. No preferred supplier, no product pitch. The aim is that you can evaluate any provider’s offering on its merits.

Built for engineers from other disciplines. The material starts from what you already know and bridges into satellite, rather than assuming a background you don’t have.

Focused on what’s operationally useful. Emphasis on trade-offs, failure modes, integration and realistic expectations — the things that determine whether a satellite deployment succeeds.

Current. The Satcom landscape has changed more in the last decade than in the previous three. The course reflects the systems being deployed now, not the ones in the textbooks.

Enquire about this course

Get in touch to discuss dates, tailoring the syllabus to your sector, or in-house delivery for your team.

Contact / Book a conversation

Course outline is indicative and can be adjusted to suit your team’s background and objectives.