Component identity
Manufacturer, part family, package, grade, category, technology, and spacecraft function block.
Choose your preferred language to continue.
The Orbital Veritas PPL Database gives engineering teams a structured way to discover, compare, and assess COTS, industrial, and automotive-grade semiconductor components for orbital applications.
Each component is organized by function, technology, evidence status, lifecycle signal, radiation assessment maturity, and mission relevance so teams can move faster without losing technical discipline.
Datasheets, PCNs, distributor information, public test reports, manufacturer notes, and internal assessments are usually spread across different systems and teams. The PPL Database creates a curated component intelligence layer, not a generic parts catalogue.
It groups technical, commercial, lifecycle, and radiation-relevance information into one structured starting point. The database helps teams identify credible candidates, reduce duplicated research, prioritize radiation testing, and prepare more defensible component decisions for New Space missions.
Has this component family been reviewed before?
What radiation, lifecycle, and supply-chain evidence exists?
Is the component nominated, tested, assessed, monitored, preferred, or restricted?
Does the package, process, lot, or date code create additional risk?
What evidence is still missing before the part can be defended for a mission?
Is this component a credible candidate, or should it be substituted?
Each PPL record gives teams a structured view of the component's current evidence position and recommended next action.
Manufacturer, part family, package, grade, category, technology, and spacecraft function block.
PPL status, pipeline state, public and private evidence, radiation coverage, lot context, and confidence level.
TID, SEE, SEL, SEU/SET, displacement damage relevance, sensitivity notes, and recommended test priority.
Lifecycle state, PCN activity, manufacturer support, sourcing considerations, package availability, and substitutes.
Mission classes, orbit considerations, shielding assumptions, subsystem criticality, mitigations, and next action.
The PPL Database shows maturity without overclaiming qualification. A preferred status is a strong starting point for defined use cases, not a blanket approval for every mission. Status levels make clear whether a component is only identified, actively evaluated, or already characterized.
Records show whether a component is in test planning, monitored by date code, preferred for defined cases, or restricted by known concerns. They connect directly to available evidence packages so teams can move from discovery to report review without rebuilding the data trail from scratch.
Radiation test summaries
Full evidence reports
Date-code reports
Test campaign notes
Mission interpretation memos
Lifecycle or PCN notes
Manufacturer participation statements
Recommended substitutions
The database supports real engineering workflows from early selection to supplier review, radiation test planning, design reviews, and manufacturer-sponsored evaluation programmes.
Identify candidate components before a design becomes locked.
Compare component families across evidence level, lifecycle status, package type, and test maturity.
Support review discussions with structured evidence and clear status classifications.
Find components that lack sufficient evidence and should enter future test campaigns.
Check whether supplier-selected components are known, tested, monitored, or restricted.
Help semiconductor manufacturers understand which product families may be credible New Space candidates.
The first PPL categories focus on components that appear repeatedly across many spacecraft subsystems, creating stronger opportunities for shared test economics and recurring evidence reuse.