Contact Us
Tell us about your production line and the process problem you are dealing with, and we will give you a specific feasibility assessment and a pilot recommendation. To help us answer quickly, please include the workstation layout, the cycle time and the process that causes the most trouble today.
To make the first conversation productive, please include these details in your enquiry: the product type and workstation layout, the line cycle time, the process that currently causes the most trouble, and what systems you already run (MES, QMS). With that we can usually tell you straight away whether the case is feasible, instead of going back and forth to confirm basics.
- If you are not yet sure whether your scene is suitable, start with the industry solutions to see whether a case close to your process is already covered.
- Common questions — installing without stopping the line, controlling false alarms, MES integration — are answered in detail in the FAQ.
- For technical detail, start with the Visual AI SOP System.
- For who we are, how we work and where we draw the line, see About Intsoft.
What happens after you send this
There is no telephone sales step in our process. When your enquiry arrives it is read first by an engineer who has worked on site projects, not by someone whose job is to book a meeting. The purpose of that first pass is to work out whether the case is feasible, not to schedule a call.
From enquiry to a verdict, usually in four steps
- A reply within one business day
We first place your case in one of a few categories: the acceptance criterion is unclear, the imaging conditions are insufficient, or it is actually a management problem rather than a technical one. In the last case we usually say so directly and recommend not buying technology.
- Follow-up questions
If the cycle time, the workstation layout or the pass/fail definition is missing, we ask. It normally takes one round of correspondence, not several meetings.
- A feasibility verdict
The answer is usually one of three: yes, yes with preconditions, or not recommended. We explain the reasoning, including anything your side needs to put in place first.
- A site visit where it is needed
Reflections, occlusions and very small movements cannot be judged from photographs. When that is the case we say a site visit is required rather than quoting a confident-sounding number from a description.
What can be judged without a site visit
Many teams assume nothing can be concluded until someone walks the line. In practice part of the picture can be read straight from a description. Separating what can be answered remotely from what genuinely needs a visit removes one unnecessary round of delay.
| Question | Judged remotely? | Why |
|---|---|---|
| Is the acceptance criterion clear? | Yes | If nobody can state what counts as done correctly, no technology can implement it |
| Can a camera physically be mounted? | Mostly | A workstation photo or a short phone video usually settles this |
| Is the lighting and reflection controllable? | Site visit | Reflection depends on material and angle; photographs distort both, a visit shows it immediately |
| Is the cycle time sufficient? | Can be estimated | Given the cycle time and the duration of the action, the decision window is arithmetic |
| What false alarm rate is achievable? | A range only | The final number has to be measured on the pilot workstation with real data |
Data handling and confidentiality
This is the question that comes up first, and it is where many projects stall — the process team wants the system while IT is worried about video leaving the plant. We would rather state the boundary up front than negotiate it after a contract is signed.
- Recognition runs locally at the edge. Production footage does not cross the public internet and is not uploaded to any cloud service.
- By default we retain decision results and the necessary event clips, not continuous video.
- An NDA can be signed before a site visit rather than waiting for the commercial stage.
- Where data has to reach corporate IT or an MES vendor, the scope and the format are written out item by item in the proposal.
Questions about the enquiry itself
About the first conversation
Do you charge for the initial discussion and assessment?
No. The first conversation and the feasibility verdict are pre-sales work. Only when a site visit is required — and it is far away — do we say in advance whether travel costs apply, so you can decide whether to proceed.
Can you give a proposal without visiting the site?
Often, yes. Where the acceptance criterion is clear and the workstation is visible, a photo and a description are usually enough. But with reflections, occlusions or very small movements, any accuracy or false-alarm figure quoted without a site visit is unreliable — and we would rather not quote one.
We do not have a specific workstation in mind yet. Can we still talk?
Yes. More often than not the starting point is a vague symptom — an audit that turned up a missed operation, or rework where part of the cause cannot be identified. Narrowing that into a measurable process target is itself part of the feasibility assessment.