Prove it works before a batch.
We test the prototype, fix what would break in production, and hand you the records and files a batch is built from.
Who this is for
A working prototype that has to be proven before a batch, whether we built it with you or you built it yourself.
Typical starting points
- A working prototype
- Design files for a prototype you built
- Pilot units that need checking before a larger run
What Anvol does
- Power-on, function and communication tests
- Structural checks
- First-article inspection
- Design-for-manufacturing fixes
- Quality records and test videos
- An issue log, kept open until every item is closed
- Production files
Deliverables
- Test checklist
- Test report
- Test videos
- Production files
- Closed issue log
Typical inputs
- The prototype or its files
- How you expect it to be used
- The targets it has to meet, if you have them
Timeline and cost drivers
- Timeline
- Set in the written scope. Open issues are fixed and retested before a batch starts.
- Cost depends on
- How many functions need testing, test time, and whether a test fixture is needed.
What is excluded
- Certification testing (FCC/CE). It is done by a test lab and quoted separately when a product needs it.
- Anything outside the written scope. Major scope changes are re-quoted, with a new timeline, before work continues.
Related cases
Questions
No. Certification testing is done by a test lab, outside our standard scope, and quoted separately when a product needs it. None of our three priced builds went through FCC or CE.
Yes. Before a run we agree with you how each unit is tested and recorded; every unit is tested before it is packed, against the targets from the sample rounds.
They go in the issue log, and the log stays open until every item is closed. Testing →