Your product, to market.

Institutes in series, slots in-house, reports scattered. Arc runs the campaign through to evidence.

Book campaign

Campaign · 8 weeks3 institutes in parallel

Week 1Plan, sequence, slots booked
Weeks 2–73 institutes in parallel · logistics by Arc
Week 8One report · OEM release
Sequential14+ weeks · reports scattered

Excerpt · demo data

Context

How Arc differs from test planning

Test planning is the software: spec to a defensible plan. Arc is the campaign: overview, parallel institutes, logistics, one report. Both share the same coverage logic. Accredited test houses run the tests. The certificate comes from the partner, not from Cevelar.

Calendar time follows the longest track, not the sum of every single test. That is why parallel, not sequential. The starting point remains a clean plan: validation planning.

Three institutes. Three reports.

Today

FlowOne institute after another
LogisticsSlots and shipping in your team
EvidenceSeparate reports, trace rebuilt

With Arc

FlowAccredited partners in parallel
LogisticsDUT chain run by Arc
EvidenceOne report for OEM and market

Evidence in hand. Product on its way.

Accredited institutes in parallel, organized logistics, one consolidated report. You move into release and market access without running the campaign yourselves.

From spec to evidence.

What is required, which institutes are running, where the DUT is, what the report says. One campaign, one status.

Overview Required tests from spec and standard, visible before anyone books.
Plan Gaps marked, sequence defensible. The same coverage logic as test planning.
Testing Accredited partners run the tests. Arc steers slots, scope, and acceptance.
Logistics DUT, shipping, slot chain: organized. You see status without running the chain yourselves.
Report One evidence pack: test report, traceability, certification status.

You hand us the campaign.

Institutes, slots, and shipping sit with Arc. Spec, DUT, and market goal stay with you.

With you

Spec and target standard
DUT and delivery window
OEM or market release as the goal

Arc takes over

Required-test overview and test plan
Accredited institutes, slots, shipping
Report, trace, certification status

Plan or campaign.

Test planning

RoleSoftware · spec → test plan
OutputCoverage, gaps, sequence
ForTeams that book themselves

Arc

RoleCampaign · spec → evidence
OutputTesting, logistics, report
ForPrograms that need to reach market

Just the plan? The software.

Test planning remains the engineering OS: spec in, test plan out. Arc sits on top once institutes, logistics, and evidence need to run with it.

Software demo

Short answers.

What does Arc solve for us?

Arc runs the campaign: required-test overview, test plan, institutes in parallel, logistics, and one consolidated evidence pack. You hold the report for OEM release and market access, without chasing slots and shipping yourself.

Who issues the certification?

Accredited test houses and notified bodies run the tests and formal evidence. Arc plans, books, handles logistics, and consolidates the report. The certificate comes from the partner.

How does the campaign get faster?

Arc books several accredited institutes at once. Calendar time follows the longest track, not the sum of every individual test.

Do specs and IP stay confidential?

Yes. Specs and derived artifacts stay under your control. Processing is EU-hosted in Frankfurt. Cevelar does not train public models on your specs. Partner institutes receive only what the booked test requires.

How is Arc different from Cevelar test planning?

Test planning is the software: spec to defensible test plan. Arc is the campaign: overview, plan, parallel execution through partners, logistics, and evidence. Both share the same coverage logic.

How do I start?

Book a time in the calendar. We align spec, target standard, and DUT. Then Arc books institutes and slots.

Book the campaign.

Pick a time. Align scope and DUT. Institutes start.