Watchlist
A component family is identified as potentially relevant to New Space based on function, availability, grade, package, market use, or customer interest.
Radiation test pipeline visibility for New Space components.
The Orbital Veritas Test Pipeline gives New Space teams and semiconductor manufacturers a structured view of components moving through nomination, review, radiation test planning, independent characterization, assessment, and date-code surveillance.
The pipeline helps customers see what is already being evaluated, what evidence is becoming available, and where shared testing can reduce duplicated effort across the ecosystem.
Radiation testing is often duplicated, fragmented, and expensive.
New Space teams frequently evaluate similar COTS, industrial, and automotive-grade semiconductor components in isolation. One company may fund a campaign while another tests a functionally equivalent component months later.
The challenge is not only cost. Teams often do not know which parts are being reviewed, tested, planned, supported by manufacturers, or affected by date-code and lifecycle changes.
which components are nominated
which components are under technical review
which test campaigns are planned
which campaigns are active
which tests are completed
which evidence packages are available
which components may require further testing
which parts are suitable for date-code monitoring
A structured path from interest to evidence.
The Test Pipeline tracks components through a defined assurance workflow, from early market interest to completed testing, assessment, and recurring surveillance.
Each pipeline state helps teams understand what has been reviewed, what is being tested, and what evidence is ready for engineering and mission assurance use.
Nominated
A component is submitted by a customer, subsystem supplier, manufacturer, test partner, or Orbital Veritas analyst for deeper review.
Under review
Technical relevance, lifecycle status, package options, public evidence, manufacturer transparency, and radiation concerns are reviewed.
Planned campaign
Test objectives, sample requirements, effects, lab selection, funding route, and expected deliverables are scoped.
Active testing
The component is undergoing radiation characterization under defined conditions through a qualified test partner or laboratory.
Report preparation
Results are reviewed, structured, interpreted, and converted into evidence packages for engineering and mission assurance use.
Assessed
Available test evidence has been interpreted against defined use cases, mission classes, and risk factors.
Monitored
The component enters recurring date-code, lot, lifecycle, or PCN surveillance where justified by demand and risk.
Preferred or restricted
Evidence may support preferred use as a starting point, or restrict a component due to radiation, lifecycle, availability, package, or evidence concerns.
Multiple routes into usable evidence.
Campaign models depend on demand, funding, technical risk, manufacturer participation, and whether evidence has value for one mission or the wider ecosystem.
The pipeline can support customer-sponsored, pooled, manufacturer-sponsored, internally initiated, and date-code surveillance campaigns without changing the independence of the assessment.
Customer-sponsored
A New Space company or subsystem supplier funds testing for components already selected or under consideration in a programme.
Pooled campaign
Multiple companies share the cost of testing a common component or function category to reduce duplicated effort.
Manufacturer-sponsored
A semiconductor manufacturer sponsors independent characterization of selected automotive or industrial components.
Internal research
Orbital Veritas initiates tests for high-demand component categories where shared evidence has clear ecosystem value.
Date-code surveillance
Selected components enter recurring surveillance when lots, process changes, or PCNs may affect evidence relevance.
Radiation effects tracked by component risk.
Different component types require different evidence. The pipeline avoids applying the same test logic to every part and instead focuses coverage on the effects that matter for the component class.
A completed campaign should not only generate raw data. It should produce structured evidence engineers can review, reuse, and defend across design reviews, supplier discussions, and mission assurance gates.
Pipeline status is evidence-based, not sponsorship-based. Sponsored components are not automatically preferred, and commercially attractive components may still require further testing or restriction.
Executive technical summary
Tested part and package information
Date-code or lot context
Sample size and test facility
Test conditions
Radiation effects covered
Observed failure modes
Parametric results
Limitations and caveats
Recommended next action
Mission interpretation notes
Linked PPL status update
Built for teams that need evidence before decisions harden.
Customers, subsystem suppliers, mission teams, manufacturers, and test laboratories can use the pipeline to shape test roadmaps and turn repeated demand into shared evidence.
Participation routes make it easier to nominate components, express interest, join pooled campaigns, sponsor mission-specific tests, access evidence, or request interpretation.
Nominate a component
Submit a part number, component family, or function category for review.
Express interest
Signal demand for a component already in the pipeline.
Join pooled testing
Share campaign costs with other companies evaluating similar components.
Sponsor a test
Fund a campaign tied to a mission, subsystem, or design review.
Request evidence access
Purchase available reports, summaries, or date-code evidence packages.
Request interpretation
Ask Orbital Veritas to interpret evidence against a specific mission profile.