A four-class criticality model for VLEO satellite electronics
KEY TAKEAWAYS:
- Structuring the system by mission impact enables consistent design trade-offs
- Choosing a mix of COTS and space-grade unlocks performance and costs efficiency
- Mitigating risk at the system level encourages modern design practices and faster iteration
In the first article of this series, we examined the VLEO environment and how radiation, thermal cycling, atomic oxygen and contamination translate into concrete qualification and derating practices for satellite electronics. Building on that foundation, this article shifts focus from physical effects to architecture and business context.
Very low Earth orbit (VLEO) and adjacent low‑altitude LEO bands are attracting interest in three main areas: higher‑resolution Earth observation, low‑latency communications and aerodynamics or propulsion research into drag compensation techniques. To turn those opportunities into sustainable programs, designers need an assurance approach that balances mission risk, cost and time‑to‑market, especially when mixing commercial off‑the‑shelf (COTS) and space‑grade components.
Three examples of VLEO business opportunities
While VLEO launches are a few percent of total LEO launches, Juniper Research forecasts that investment in VLEO satellites will reach $220 billion by 2027, and the number of launches will grow from 16 in 2024 to over 620 by 2030. The applications outlined below could be the main drivers of that growth:
- Operating closer to the Earth’s surface enables finer ground resolution for a given payload and can improve temporal coverage when coupled with agile constellations. That makes VLEO attractive for applications such as high‑detail imaging, change detection and specialized sensing where resolution and signal‑to‑noise are key differentiators. The trade‑off is higher drag and a more aggressive environment, which can shorten design lifetimes and increase replenishment rates. Electronics must therefore support both reliable operation in a harsh regime and manufacturability at constellation scale.
- Many existing “5G from space” and non‑terrestrial network (NTN) initiatives are focused on LEO more broadly, but the same drivers of latency, link budget and terminal cost also make lower orbits interesting for regional systems and technology demonstrators. VLEO can offer very low round‑trip delays and strong link margins for certain architectures, at the expense of more frequent handovers and stricter pointing and power constraints. Payload and platform electronics need to deliver high data throughput and agile beamforming while maintaining robustness under rapid thermal cycling and single‑event activity.
- VLEO is also a natural laboratory for testing materials, shapes and propulsion concepts that manage or even exploit atmospheric drag. Technology demonstration missions in this area often combine novel structures and surfaces with electric propulsion, advanced attitude control and in‑situ measurement payloads. From an electronics standpoint, these missions may tolerate higher risk in experimental subsystems but still demand high assurance in core power, control and communications.
Across all three opportunity areas, the commercial reality is that programs are under pressure to deliver more capability per kilogram and per dollar. That points toward carefully controlled use of automotive and industrial COTS devices alongside space‑grade components, structured by a clear view of functional criticality.
A four‑class criticality model for space electronics
Different agencies use a variety of criticality and assurance classifications for spacecraft electronics. The four‑class scheme presented here is not a formal industry standard, but an example of a consolidated best‑practice framework Avnet might suggest when helping customers architect VLEO and LEO platforms. Its goal is to make the links between functional criticality, parts policy and mitigation strategies as explicit as possible.
A practical classification divides functions into four classes:
- Class A: Loss‑of‑mission or safety‑critical
This category includes attitude and orbit control, primary power management, propulsion systems, separation actuators and safe‑mode communications. Failure in these functions can lead to irreversible loss of the spacecraft or significant safety hazards, for example, if an uncontrolled vehicle threatens other space assets. - Class B: Major mission impact but recoverable
Examples include primary payload data‑handling, high‑rate science or imaging downlinks, rendezvous and inspection sensors that are not required for basic survival, and core timing and data‑distribution networks. Failures here can degrade mission objectives or service quality, but do not immediately jeopardize basic safety or controllability if appropriate fall‑back modes exist. - Class C: Degraded‑mode acceptable
These functions can tolerate reduced performance or temporary loss. Typical examples are secondary sensors, housekeeping data paths, non‑critical computing resources and auxiliary communications. Mission planning assumes that occasional outages or performance degradation in these areas can be managed at system level. - Class D: Experimental or disposable
Class D covers technology‑demonstration payloads and experiments that can be allowed to fail, provided that appropriate containment prevents adverse effects on higher‑class systems. This is where novel devices, aggressive COTS usage and rapid‑iteration hardware are most at home.
Each board and functional block is explicitly assigned to a class, and this assignment is captured in the parts control plan and reliability documentation. For VLEO missions, where the environment can be harsh, but lifetimes may be comparatively short, this structured view of criticality helps teams decide where to invest in space‑grade components and extensive testing, and where mitigated COTS usage is appropriate.
Table 1: System-level partitioning by criticality
| Criticality class | Typical functions | Parts approach | Typical mitigations |
|---|---|---|---|
| Class A | Attitude/orbit control, primary power, propulsion, safe-mode comms | Mostly space-grade/rad-hard | Redundancy, derating, watchdogs, current limiting |
| Class B | Payload data handling, high-rate downlinks, core timing/data networks | Mixed architecture | Error correcting codes, scrubbing, supervisory controllers, fall-back modes |
| Class C | Secondary sensors, housekeeping, auxiliary comms | COTS-dominated | System-level FDIR, mode management, isolation |
| Class D | Experimental payloads, novel sensors, AI accelerators | Aggressive COTS/disposable | Isolation, current-limiting, software disposable, containment |
A four-class criticality model helps satellite designers align component assurance, mitigation strategy and cost with the true mission importance of each subsystem in VLEO and adjacent LEO platforms.
COTS versus space grade components by criticality class
With the four class structure in place, teams can make more consistent decisions about how to blend COTS and space grade parts.
Class A: conservative by design
For Class A functions, space‑grade or radiation‑tolerant devices with documented total ionizing dose (TID) capability and characterized single‑event effect (SEE) behavior remain the baseline. These parts are operated with generous electrical and thermal margins, and redundancy is common. Where no suitable space‑grade equivalent exists and a COTS device is unavoidable, the design incorporates stringent protection and mitigation, including current‑limiting, watchdog‑based recovery and architectural safeguards to prevent a single device from jeopardizing spacecraft survival. Avnet’s role in this space often involves identifying viable space‑oriented components, managing obsolescence risk and coordinating access to specialized screening flows.
Class B: mixed architectures for performance and cost
Class B functions lend themselves to mixed architectures that combine high‑assurance building blocks with higher‑performance COTS devices. A typical pattern pairs a radiation‑tolerant supervisory controller or microcontroller with one or more automotive‑ or industrial‑grade FPGAs or processors that provide high‑throughput data processing. Non‑volatile configuration memory may be radiation‑tolerant, while higher‑density volatile memory is COTS protected by error‑correcting codes (ECC) and scrubbing. The intent is that SEEs in COTS devices can be detected and corrected without propagating unacceptable behavior into Class A subsystems. Here, Avnet can help teams assemble compatible device combinations from its portfolio, interpret available radiation data and structure screening campaigns that focus on the most critical unknowns.
Class C: COTS‑dominated, system‑level mitigation
In Class C, industrial and automotive‑grade COTS components can dominate, provided they satisfy environmental requirements including temperature range, vacuum compatibility and packaging suitability where exposure to atomic oxygen is possible. Failures in Class C are handled primarily at system level through mode management and fault‑detection, isolation and recovery (FDIR) rather than via highly conservative part‑level margins. Designers may accept higher event rates or wear‑out probabilities at device level in exchange for lower cost and greater flexibility, as long as higher‑class functions cannot be compromised. Avnet’s broad COTS line card and experience in automotive reliability can be particularly valuable for constructing robust Class C designs in VLEO.
Class D: sandbox for innovation
Class D hardware is treated as isolated. Minimal screening and derating may be applied, but power feeds are current‑limited, interfaces are galvanically or logically isolated and flight software can disable or ignore the hardware if anomalous behavior is detected. This allows mission teams to fly emerging technologies such as new sensor concepts, AI accelerators or experimental communications payloads without exposing core services to undue risk. For suppliers and startups entering the VLEO market, Class D can be a proving ground that balances in‑flight learning with manageable assurance requirements.
Linking criticality classes to the VLEO business case
VLEO’s combination of relatively modest TID, significant SEE activity, high thermal‑cycle counts and pronounced atomic‑oxygen and contamination effects has direct commercial implications. Designs may experience shorter operational lifetimes than traditional LEO missions, but replenishment and iteration cycles can be faster. Constellations may include a mix of high‑assurance platforms and more experimental units.
In that context, Avnet’s four‑class model helps program teams tailor their electronics strategy to the underlying business case:
- Earth observation missions that hinge on image quality and continuity can concentrate Class A and B assurance on attitude control, primary power and core data paths, while allowing more aggressive COTS use in image processing pipelines and secondary payloads.
- Communications constellations targeting low‑latency services can reserve conservative parts policies for timing, synchronization and core links, while treating edge compute and value‑added services as Class C or D.
- Aerodynamics and drag‑compensation demonstrators can treat propulsion control and safety‑related functions as Class A or B, with new sensors, algorithms and test payloads in Class C and D to enable rapid learning.
Because each class maps to a different mix of parts, screening and derating, procurement and engineering teams gain a common language for balancing risk, performance and cost. That, in turn, supports more predictable program budgeting and clearer communication with customers and stakeholders.
From framework to implementation
The four‑class criticality model is most powerful when combined with the environment‑derived qualification and derating practices described in the first article in this series. Radiation and thermal analyses define the envelopes; the criticality classes determine the required margin and mitigation for each function within those envelopes.
Avnet’s defense and aerospace teams can use this or a similar framework when assisting customers on architecture, component selection and screening strategies for VLEO and LEO platforms. By pairing structured criticality classification with access to both space‑grade and high‑reliability COTS portfolios, it becomes possible to exploit modern terrestrial electronics while still meeting the mission‑reliability expectations of emerging VLEO markets.
Part 1 in this series looks at component selection and design criteria for VLEO satellites.
Related content
VLEO satellites upend space electronics with automotive-grade components
Satellites servicing satellites
Putting 5G in space for the massive IoT
