AI / ML & Computer Vision
CT Garud CT Flow Builder CT OCR / OCV CT Mikha Anomaly Detection BCFHS Vision Measurement Process Check EOL Inspection All vision →
IoT & Smart Factory
Production-Line Tracking EHS / Safety Tracker OEE & Condition Monitoring Digital Dashboards (DMS) NCMS CPAS All IoT →
AI CCTV Monitoring System For OEMs — Ship Under Your Brand Engineering & Machine Building OMR — Exam & Form Scanning Vaarnaap — Weight Management System Our Work Case Studies Services Industry 4.0 — Where to Start IT & OT — Network & Data About Careers Contact Request an Assessment →
Request an Assessment

/ For IT & Automation Teams

Where This Sits on Your Network

Production wants the defects caught. IT has to be satisfied it is safe to put on the floor. This page is written for the second conversation — what the system touches, what it needs, and what it explicitly does not. Forward it.

Ask a Technical Question → Industry 4.0: Where to Start

It lives on the OT side. The station sits on your line network and signals the PLC. It does not need to reach your corporate network to do its job.

No inbound path exists. There is no port to open, no tunnel to keep up, and no cloud service waiting for a connection from your plant.

Pull the uplink and it keeps running. Inspection does not degrade without internet, because it never depended on it.

/ The Boundary

What It Touches, Either Side of the Line

Vision deployments go wrong when the inspection layer is quietly made dependent on corporate IT. This one is built to stay where the machines are.

Operational technology On the line
Camera & lighting
GigE industrial cameras on the station, over RTSP/ONVIF where it is CCTV. Yours or supplied by us.
Inspection station
An industrial PC or edge endpoint at the line. This is where inference runs.
Line signalling
OK/NG to the PLC over digital I/O, Modbus or OPC-UA. The control layer keeps its own logic — we signal, it decides what to do.
Reject hardware
Diverters, gates or stoppers where the line needs them, wired into the same station.
Information technology What we ask for
Network
A switch port and an IP address on the OT segment. The station can live entirely inside that segment.
Internet
Not required. The system is designed to run air-gapped and keeps inspecting with the uplink pulled.
Accounts
No cloud account, no tenant, no licence server to reach. Nothing to provision on your identity platform.
Optional uplink
Only if you want results in MES, ERP or an existing dashboard — and then it is an outbound push you define.

/ The Useful List

What We Will Not Ask You For

Usually the faster way to answer a security review.

An inbound firewall rule or port-forward
A VPN tunnel kept permanently open
A cloud subscription or vendor tenant
Internet access for the system to function
Domain administrator rights
Agents installed on your other machines
Access to your ERP, file shares or user directory
A standing remote-access session

/ Data

Two Different Questions, Two Different Answers

Vendors tend to blur these. They are not the same thing and your IT team will ask about both.

In production — nothing is transmitted
Once deployed, inspection images, verdicts and models stay on your infrastructure. There is no cloud service they are sent to and no scheduled upload. Results go only where you point them: the PLC, and optionally your own MES, ERP or dashboards.
For training — samples you share, deliberately
Initial model training runs on our hardware, from sample images you send us for that purpose. They are used only for your model, kept confidential, and returned or deleted on request — see the Privacy Policy. If your policy does not allow samples to leave site, tell us early and we will scope around it.

/ Support Access

How Updates Reach a System With No Open Door

You choose which of these applies at your site. Neither requires a connection that stays open.

A
On-site
An engineer applies the update at the station, or it is delivered over your own local network. No remote access path exists at all. This is the default where a site is air-gapped or policy forbids remote sessions.
B
A session you open
Where you prefer remote support, you open a temporary session when you want one and close it afterwards. It is initiated from your side, supervised, and nothing persists between sessions.

Some sites run strictly on-site, others allow a supervised session — it is your call, and it is written into the deployment rather than assumed.

/ Get Started

Send This to Your IT Team

If they come back with questions this page does not answer — segmentation, logging, retention, hardening — send them to us directly. We would rather answer them now than at commissioning.

Ask a Technical Question → See Case Studies