Implementation guide

Deployment requirements: what a site needs

A Vikbot system runs on the customer's own site: cameras at the check points, an edge computer on the local network and a link to the orders it checks against. This guide lists what a site needs before go-live and the steps a rollout follows.

At a glance

What does a site need before a Vikbot go-live?

A site needs a mounting position, lighting and power for the cameras at each check point, a place on its local network for the Vikbot-supplied edge computer, the expected quantities from its ERP or WMS (or a spreadsheet), samples of its items for training and staff for a parallel run. Everything runs on-premises and offline, so the checks do not need internet access. Vikbot, an AI warehouse automation company in Chennai, India, checks these points in a site survey and sets the timeline after it.

Cameras
Vikbot AI camera units at check points; existing CCTV for video analytics
Compute
Vikbot-supplied edge computer on the customer's LAN
Internet
Not needed: runs on-premises and offline
Rollout
Site survey, installation, training, parallel run, go-live
Company
Vikbot, a brand of Clofus Innovations Pvt. Ltd., Chennai, India

Requirements checklist

Use this list to prepare for the site survey. Camera models, mounting heights, bandwidth and power ratings depend on the site, so they are confirmed during the survey rather than fixed here.

Cameras

  • A check point for each camera. Vikbot AI camera units go where goods pass in a controlled way: conveyors, dock doors, dispatch points, packing benches and gates.
  • A mounting position and lighting at each point, with a clear view of the items. Height and angle are checked during the site survey.
  • Existing CCTV, where it is used. Video analytics and FleetBot work on the site's existing CCTV cameras.
  • Product-specific setups. PackBot uses two cameras and a scale at the packing bench; ScanBot is a phone app and needs no fixed camera.

Network

  • The customer's local network (LAN) connecting the cameras and the edge computer. Everything runs on-premises and offline.
  • No internet access is needed for the checks themselves.
  • Network capacity per camera is checked during the site survey.

Power

  • Power at each camera point and where the edge computer is placed. Power needs are confirmed during the site survey.

Compute

  • A place for the edge computer. Vikbot supplies the edge computer that runs the AI on site; the customer provides a location for it on the LAN.

System access

  • The expected quantities. Pick lists, invoices or dispatch orders from the ERP or WMS, so each item can be checked against them.
  • SAP, if used. Vikbot connects over SAP APIs (OData, BAPI/RFC); the SAP-side work is agreed per project and done together with the customer's SAP team. See how Vikbot integrates with SAP.
  • No ERP link yet? DockBot can run standalone from a spreadsheet of dispatch orders.

People

  • Item samples of the goods to be checked, so the models can be trained on the customer's own items.
  • Floor staff for the parallel run, working the existing process alongside the new checks.
  • The customer's ERP or SAP team, when an ERP link is part of the project.

Rollout steps

  1. Site survey. The Vikbot team sees how goods are checked today and confirms the check points, mounting, lighting, network and power.
  2. Installation. The cameras and the edge computer are installed on the customer's network.
  3. Model training. The models are trained on the customer's own items.
  4. Parallel run. The new checks run alongside the existing process before anything relies on them.
  5. Go-live. The Vikbot system becomes the check of record.

Typical timeline

Every rollout follows the steps above, but there is no standard duration: the timeline is set after the site survey. One published reference point: PackBot needs about two weeks of use to learn the items and workflow before it becomes the primary control.

For how the checks themselves work, see how camera-based inventory counting works and how QR scanning and dispatch verification work; for other guides, see all implementation guides.

FAQ

Deployment frequently asked questions

What does a site need before a Vikbot system goes live?
A mounting position, lighting and power for the cameras at each check point, a place on the local network for the Vikbot-supplied edge computer, the expected quantities from the ERP or WMS (or a spreadsheet for DockBot), samples of the items for training, and staff for the parallel run. The details are checked during the site survey.
Does Vikbot need internet access or a cloud service?
No. Vikbot systems run on-premises and offline on the customer's network. The AI runs on a Vikbot-supplied edge computer on the customer's LAN, so the checks do not depend on a cloud service.
Can Vikbot use our existing CCTV cameras?
Existing CCTV is used for video analytics and for FleetBot truck and gate tracking. Checks at conveyors, docks, dispatch points and packing benches use Vikbot AI camera units. ScanBot runs as a phone app.
Is an ERP or SAP connection required?
Not to start. DockBot can run standalone from a spreadsheet of dispatch orders. When an ERP is connected, SAP is integrated over SAP APIs (OData, BAPI/RFC), with the SAP-side work done together by the Vikbot team and the customer's SAP team.
How long does a Vikbot deployment take?
Every rollout follows the same steps: site survey, installation, model training on the customer's items, a parallel run and go-live. There is no standard duration: the timeline is set after the site survey.

Plan a site survey

Tell us where goods are checked on your site today, and we will work out the cameras, network and rollout with you.