ground-systems

Size ground networks for space missions using orbit, data volume, and downlink rate.

17|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/devideamax/aerospace-team --skill ground-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ground-systems
Source: https://github.com/devideamax/aerospace-team/tree/main/skills/ground-systems
Command: npx skills add https://github.com/devideamax/aerospace-team --skill ground-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expert ground segment and mission operations engineering — ground station network sizing, pass planning and contact analysis, CCSDS TT&C protocols, data processing pipelines, and MOC architecture. Use when sizing ground networks, calculating contact windows, estimating daily data volume, designing operations concepts, or selecting between DSN/ESTRACK/KSAT/commercial providers. Trigger with "ground station", "pass planning", "contact window", "mission operations", "telemetry", "telecommand", "DSN", "ESTRACK", "KSAT", "data downlink", "MOC design", "CCSDS".

Core Features & Use Cases

  • Ground station network sizing and pass-planning for multiple orbital regimes.
  • Pass geometry analysis, contact planning, and data-volume estimation for operations.
  • CCSDS TM/TC integration, data pipelines, and MOC architecture design for end-to-end mission support.
  • Evaluate provider options (DSN/ESTRACK/KSAT/commercial) and design robust ops concepts for LEOP through nominal operations.

Quick Start

Provide orbit, data volume, and downlink rate to size and optimize a ground network.

Frequently Asked Questions about ground-systems

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I size a ground station network for a specific space mission orbit?

To size a ground station network, provide the mission orbit parameters, expected data volume, and downlink rate. The system calculates station coverage, contact windows, and pass planning margins to determine the required single- or multi-station configuration for your space mission.

What is the best way to calculate contact windows and daily data volume for mission operations?

Calculating contact windows and daily data volume requires analyzing pass geometry against the spacecraft orbit. By inputting downlink rates and orbital parameters, the system estimates contact windows and daily data throughput to ensure mission operations meet data latency requirements.

Can I use CCSDS protocols for telemetry and telecommand integration in my MOC architecture?

Yes, CCSDS protocols are fully supported for telemetry and telecommand integration. The system enforces CCSDS TT&C protocol usage during ground network sizing and MOC architecture design to ensure compliant data pipelines and end-to-end mission operations center functionality.

Does this support comparing DSN, ESTRACK, and KSAT commercial providers for LEOP and nominal operations?

Yes, it supports evaluating provider options including DSN, ESTRACK, KSAT, and commercial alternatives. It assesses ground station network coverage and contact windows to optimize provider selection across Launch and Early Orbit Phase (LEOP) through nominal operations.

How do I design data processing pipelines for a multi-station ground segment configuration?

Designing data processing pipelines for a multi-station ground segment involves mapping telemetry downlink rates against station coverage. The system evaluates contact windows and data throughput margins to architect robust pipelines spanning single or multiple ground stations.

Why do I need to consider downlink rate when planning pass geometry for a space mission?

Considering downlink rate during pass planning is critical to match data volume with available contact windows. The system uses downlink rate and orbital pass geometry to calculate throughput margins, ensuring the ground segment meets mission data latency and volume requirements.