Project pre-qualification
Describe the industrial problem before choosing the solution.
This page is for technical needs: production automation, intralogistics, agri-food sorting, vision, packaging, retrofit, machine safety, controls, industrial software or Europe–Asia sourcing.
First scoping
Questions we will ask anyway.
Click a question to see the level of information that helps. You do not need to have every answer.
Which operation is currently limiting performance?
Identify the workstation, equipment or process step, and the main symptom: throughput, waiting, defects, rework, operator strain or downtime.
Answer in the form ↓What needs to be improved or made safer?
Describe the expected result in practical terms: parts/minute, fewer defects, removal of a manual task, secured access, better traceability or less downtime.
Define the target ↓Which equipment and interfaces already exist?
Machine, PLC, HMI, camera, conveyor, sensors, network, product format or software interfaces: even a partial list avoids wrong assumptions.
List the existing setup ↓How much production downtime is acceptable?
A few hours, a weekend, several days or only during a planned shutdown: this constraint has a direct impact on retrofit architecture and offline preparation.
Specify constraints ↓What investment range is realistic?
An order of magnitude is enough. It helps distinguish a quick win, a targeted retrofit or a more structural project without wasting time on an unrealistic scope.
Frame the budget ↓How will the result be accepted and measured?
Target throughput, reject rate, availability, changeover time, compliance, ergonomics or FAT/SAT criteria should be made visible early.
Define acceptance criteria ↓No specification yet?
A photo, the problem and the current throughput are enough to start.
Many SMEs contact us before they have a complete specification. A first discussion can start from three simple inputs.
The workstation, line, flow or equipment concerned.
Lost time, errors, ergonomics, defects, downtime or lack of capacity.
Even an order of magnitude helps scope the solution level.
Before the first discussion
A few simple inputs can save a lot of time.
Nothing is mandatory. The goal is simply to start from field facts rather than commercial assumptions.
General view, problem area, cabinet or interfaces when relevant.
Even an order of magnitude helps distinguish a process issue from an equipment issue.
PLC, drive, vision system, robot, conveyor or main machine when known.
A few concrete examples are often more useful than a long presentation.
Layout, electrical drawing, manual or specification excerpt, even if incomplete.
Send drawings, photos or specifications to contact@syntaver.com.