FAQ
Common questions
Straight answers about how we work, what we deliver and what falls outside our studio model.
Before you write, scan the topics below. If your question is project-specific, the fastest path is a short note through our contact form with part photos and shift length — we can usually tell you whether a discovery visit makes sense.
Is RoboPoint a robo-advisor / robocalling service, a robot store, or fully autonomous robots with guaranteed uptime?
No. We are an AI robotics integration and deployment studio. Robo means physical robotics with AI — not a robo-advisor, robocalls or software-only RPA — and Point means the point of deployment (getting a robot to do real work), not loyalty points. We integrate robots into real operations with functional safety, guarding and trained operators in the loop; nothing is fully autonomous with no humans, and no system is perfectly safe. Deployments are risk-assessed and standards-compliant (for example ISO 10218 / ISO/TS 15066). We do not build autonomous weapons, and we cannot guarantee uptime, throughput or zero defects.
Which industries do you serve?
We focus on discrete manufacturing, food and beverage processing, precision machining and industrial equipment assembly across Canada. Projects typically involve repetitive manipulation, material transport or visual inspection where cycle time and quality data matter. We do not take residential or entertainment robotics commissions.
Do you sell robots directly?
We are integrators, not a volume distributor. We specify hardware that fits your maintenance and spare-parts strategy, assist with procurement and remain vendor-neutral when multiple models meet the spec. Hardware invoices may pass through us for convenience or go direct to the OEM — whichever your finance team prefers.
How long does a typical integration take?
Feasibility studies run two to six weeks. Full cell integrations commonly span three to nine months depending on vision training data volume, safety category and factory access windows. AMR fleet rollouts with multiple buildings add mapping and traffic-validation time. We publish a milestone schedule in the statement of work before kickoff.
What middleware do you standardise on?
New builds default to ROS 2 with documented launch files and CI-friendly packages. Legacy installs may retain proprietary OEM environments when replacement cost is unjustified — we wrap them behind stable interfaces so you can migrate incrementally.
Who owns the source code and models?
Unless otherwise agreed in writing, custom integration code, trained models and documentation created for your project are yours upon final payment. We retain the right to reuse generic libraries and non-client-specific utilities developed internally.
How do you handle functional safety sign-off?
We prepare hazard analyses, validation evidence and as-built diagrams aligned with ISO 10218 / ISO 13849 workflows. Your designated safety officer or external certifier retains statutory sign-off authority. We participate in reviews and remediate findings within scope.
Can you work with our existing PLC and IT standards?
Yes. OPC UA, Ethernet/IP, Modbus and discrete I/O are routine. Network design respects VLAN segmentation, jump-host access and logging policies your IT team defines. We do not insist on cloud connectivity for core control paths.
Do you offer remote support after commissioning?
Hypercare is included for an agreed window after go-live. Extended support retainers are available with defined response times and escalation paths. Emergency on-site visits are billed separately unless covered by an active retainer.
How is personal information handled?
Contact form data is used only to respond to your inquiry and manage the resulting business relationship, in line with PIPEDA and our Privacy Policy. Consent is required before submission and is not pre-selected on the form.
Do you travel outside Kitchener-Waterloo?
Yes. Discovery visits and commissioning support routinely take us across Ontario and to other provinces when scope warrants. Travel is quoted explicitly in the statement of work. Remote FAT and structured video acceptance remain options when site access is constrained.
Still have a question?
Send a message — we read every inquiry that clears our spam filters.
Contact RoboPoint