Component counting in trays
Compare the observed number with the agreed unit and tray definition.
A project contracted with Adaris
Camera counting for Elche components
Are parts missing from the tray or package? If someone checks by eye today, Adaris can study one component scene in Elche: gather real video, review examples with a person and check whether a count or alert helps before preparing a local Player.
For businesses in Elche · remote work in Spanish
Does this happen in your business?
These examples help you explain what needs to change. Tell us how you work today and we will agree what to build, its cost and how to check it.
Evidence for a preparation issue
Keep a detection, zone or clip to review a gap, overlap or uncertain case.
Computer visionAgree the first step
Start with one specific task.
Agree which part or tray to observe, how one unit is counted and which order-preparation moment matters. Studio reviews images or video, corrects examples and compares results before preparing a local Player for one source. The pilot is quoted and contracted separately, with the test scope in writing.
Explore the full serviceSee the actual product
Prepare with Studio. Run with Player.
Studio prepares and reviews examples, evaluates the model and packages the solution. Player runs video analysis locally. These are captures of our own product, rather than results from customer installations.
What we agree in the proposal
Observable tray and unit
Specify the tray, component or gap to identify and the order-preparation moment that matters. Define valid samples, incomplete trays, overlaps, reflections and cases that should not be counted.
Reviewed examples and comparison
Import representative material, let Studio suggest detections and have a person correct, approve or reject relevant cases. Compare results in included scenes and record sample limits.
Bounded local operation
When appropriate, prepare a Player with the defined count, zone, path, heatmap, rule or evidence. A second line, camera or source needs its own analysis, configuration and package or licence.
How we check the delivery
- Identify the trays, components or gaps included in the approved examples.
- Review which units were detected, missed or excluded from the sample.
- Check that zone and counting rule follow the agreed order-preparation definition.
- Run the local Player with the included source and review the configured evidence or alert.
What to tell us first
- Videos or images of trays and order preparation in normal conditions, including difficult cases.
- What a correct tray means, which unit to count and which issue you want to review.
- Variations in orientation, lighting, material, speed, hands or process occlusions.
- The video source and intended equipment, together with network limitations we should know.
Before requesting a proposal
Can it detect a partly hidden component?
Occlusions can be included in the evaluation when representative examples are supplied. Results are documented for that sample and are not a guarantee for every future condition.
Can it distinguish similar parts?
That depends on visible differences, available material and the agreed rule. Studio helps review and compare examples before deciding whether the distinction is clear enough.
Can it connect to the preparation process?
A local connection with other systems can be assessed as a defined scope. Sensor, PLC or machinery installation is considered separately.
What if the count is not reliable?
We identify misses, incorrect alerts and difficult test scenes. You can narrow the use or request an improvement with new material and an agreed scope.
Describe the step that gets stuck.
We assess fit and agree scope and budget before starting. Your first message can describe the process without sharing customer records.