Skip to main content
GullySystem
Requirements checklist

What to ask for when choosing software for machine vision companies.

A checklist built from how machine vision companies work, to print or save as a PDF and bring to any supplier meeting.

Share your requirements

What the software should cover

Tick each one that matters to your business.

  • Feasibility study records
  • System bill of materials
  • Image library and model versions
  • Installation and line trial
  • Support tickets by system
  • Retraining and change jobs
  • Service contracts and spares

Roles that need their own access

Who logs in, and what each person may see or change.

  • For application engineers
  • For the assembly bench
  • For vision programmers
  • For support engineers
  • For sales and account managers

Reports to ask for

Ask to see each one with your own sample data.

  • Studies by outcome, defect type and customer
  • Installed systems by camera and lens model
  • Model versions with accuracy results and approver
  • False reject and false accept calls by system
  • Line trial days against the quoted days
  • Spare lamps, lenses and cables against reorder level
  • Contracts due for renewal by month

Systems it may need to connect to

Note which ones you already run.

  • Email
  • Calendar
  • File storage for image sets
  • Accounting export
  • SMS

Questions for any vendor

Put these to every supplier you are comparing.

  • Can a study turn into a project?
  • Does it store training images?
  • How do we know which model is running on a line?
  • Can accuracy results be recorded?
  • Does it run the inspection?
  • Can spares be held by system model?
  • Can customers raise support calls themselves?
  • How do we get a quotation for the software?
  • How long before engineers log studies and systems in it?
  • What should we prepare before the build begins?

Where the work usually breaks today

Circle the ones you recognise. They set the order of the project.

  • Feasibility results are not kept
  • Image sets and models drift apart
  • Hardware variants multiply
  • Support requests arrive without context
  • Pilot work is not billed

Check the difficult cases before choosing software.

Use examples from your own records to test the workflows that matter in your business.

System bill of materials

What changes when a component or quantity is substituted?

Take one entry from “System bill of materials” and change an input in a test copy. Review the resulting material requirement and cost with the person who approves production.

Background reading: ERPNext: bills of materials

Support tickets by system

What happens between reporting a fault and accepting the fix?

For “Support tickets by system”, walk through a fault reported outside normal hours. Agree the first responder, escalation path and evidence needed to close the incident, including what falls outside the support arrangement.

Background reading: ERPNext: support settings

Prefer to talk it through? See the machine vision companies page.