Join the crewMy track

Classes / Systems class / Systems Department

Systems Track: Spacecraft Links and Flight Software Basics · Rank 6 coursework · Module 1 of 3 · about 40 min

Running a network: scheduling and service

A ground network sells time. NASA’s Deep Space Network and Near Space Network serve many missions with a limited set of antennas, so every pass is scheduled and every mission competes for coverage. Commercial ground station services work the same way.

Leading a network means balancing demand: critical events like launches and landings get priority, routine science fills the gaps, and emergencies can bump everyone. Clear rules about priority, published in advance, prevent most arguments.

Service is measured. Teams track how many scheduled passes delivered their data, how fast problems were fixed and how much antenna time was lost to maintenance. These numbers drive budgets and upgrades.

We study how network leaders plan capacity years ahead. New missions, larger data volumes and optical links affect antenna, staffing and budget needs, so the case for resources must be made before demand arrives.

We write the service promise before choosing a metric. Booked antenna minutes, usable contact minutes, received information and delivered application data describe different boundaries. A pass can start on time and still fail its intended delivery. We state whether a count means any reception, a specified volume or a critical event's required evidence. Otherwise a favorable pass-success percentage can conceal a poor result for the actual user.

Worked example, fictional schedule: two ten-minute passes are booked at one useful megabit per second. The first has six usable minutes and the second has none. Delivered volume is 360 megabits, or forty-five decimal megabytes, not the 1,200 megabits implied by multiplying every booked minute by rate. The record separates lost opportunity from delivered volume. We do not label a partial pass complete without a stated success criterion.

Practice, on paper: we create a small demand table with one fictional time-critical event and two flexible transfers. We apply a declared priority rule, reserve finite station time and show what is delayed if an outage occurs. Our self-check includes a recipient-facing delivery metric and an assumption about fallback. This is planning practice, not a claim about NASA's internal scheduling policy or permission to book real network time.

Sources

Module quiz

10 questions, 8 correct to pass. You'll see what you missed and why, and you can retake it.

Next: Space sustainability: debris and end of life →