Hardware that survives a test still needs to work afterward. Subsystem-level functional verification under controlled conditions — checking behaviour, not just structural integrity.
Functional verification runs during environmental testing — your hardware is exercised at hot, cold, and ambient dwells, not just powered on after the test.
A unit can pass a vibration test mechanically and still fail to boot. Functional testing during environmental exposure is how you catch this — before launch, not after.
Functional checks executed at hot and cold dwells — not just at ambient before and after. Catches temperature-dependent failures that would otherwise be invisible.
Hardware exercised through its actual flight interfaces — power profile, command sequence, telemetry. Not a synthetic test mode that bypasses real-world behaviour.
Every off-nominal observation is logged with timestamp and conditions. The test report includes anomaly history — not just pass / fail.
Functional testing has no fixed standard — by design. Scope is defined per your subsystem and your acceptance criteria. We bring the lab discipline; you bring the test sequence.
Functional testing is paired with environmental testing — never standalone. These are the campaigns it most often runs inside.
Tell us your test sequence and your acceptance criteria — we’ll integrate functional verification into the right environmental campaign.
Functional testing means exercising your hardware through its real flight interfaces — power profile, command sequence, telemetry — while it is under environmental stress.
Not “powered on and observed” after the test. Real interfaces, real behaviour, captured live.
A unit can pass a vibration test mechanically and still fail to boot. A board can survive thermal cycling and still produce telemetry corruption at the cold dwell. Temperature-dependent and load-dependent failures are invisible at ambient.
Functional verification during environmental exposure is how you catch them — before launch, not after.
No — by design. Functional scope is defined per your subsystem and your acceptance criteria. We bring the lab discipline (anomaly tracking, timestamped logs, real-time comms); you bring the test sequence and the pass/fail criteria.
Functional always runs inside a thermal, vibration, or TVAC campaign — never standalone.
Every off-nominal observation is logged with timestamp and conditions. The test report includes the full anomaly history — not just pass/fail.
You see what happened, when, and under which environmental load. No surprises at delivery.
Power profiles (bus voltage, transient profiling), command interfaces (CAN, RS-485, SpaceWire, custom), telemetry capture, payload-specific protocols.
Test sequence is agreed in the test plan before execution. Bring your EGSE or use ours — depending on scope.
Yes — and it usually should be. Functional during dwell is part of the campaign price when defined upfront. Adding it after the fact is possible for re-tests but harder to coordinate.
Best practice: define functional criteria during test plan kickoff.
