VARAHIEDGE · NIRDESH

The screen that stopped taking taps

A touchscreen only reads a bare, dry fingertip. A shop floor rarely has one spare. Nirdesh was built for the hand that is already busy.

9 September 2026 · Varahi Technologies · Bhugaon, Pune

The tablet went up on the machine cell with real ceremony — a rugged case, a mount welded to the frame, a step-by-step app loaded with the maintenance procedures. For the first few weeks people used it.

Then the coolant got onto the glass. Then the oil from a bearing job. A technician in nitrile gloves presses the screen and nothing happens. He presses harder, wipes the glass on his sleeve, tries again. It takes three of these before someone writes it up: the tablet doesn't work anymore.

Nothing broke. A touchscreen reads a fingertip by the small electrical charge it carries against bare skin. A gloved hand doesn't carry that charge. Neither does a wet one, or an oily one. The tablet was never faulty — it simply needed a hand that a shop floor almost never has spare.

Why we build it this way

The obvious fix is a better screen: a glove-mode setting, a stylus on a lanyard, a case rated for the wash-down. We looked at that road and turned back, because it treats the hand as the thing that needs fixing. On a shop floor the hand is doing the actual job — holding a part, gripping a spanner, inside a panel up to the wrist. That isn't a lapse in procedure. That is what the job looks like.

An interface that only works on a clean, bare fingertip was built for the office it was designed in, not the floor it gets sent to. It will keep failing there no matter how rugged the case gets, because the failure was never really about the case.

The floor is wet, oily and gloved by design. An instruction that needs a bare fingertip to reach someone is asking them to stop the job first.

So Nirdesh doesn't ask for a fingertip at all. Sound reaches through a glove and through a face shield, to hands that are occupied with something else entirely. That isn't a concession to a rough environment. It is the one channel that was never going to need the hand back.

How it works, roughly

Nirdesh reads:

It answers by voice, one step at a time, and waits before moving to the next one — the pace of a person telling you what to do next, not a page to scroll past. Ask it to repeat a step, or what a term means, and it answers in kind. Say a step doesn't match what's in front of you, and that gets recorded against the step, for whoever asks about that unit next.

Nobody has to put a part down, peel off a glove, or find a clean patch of skin to press. A year of that is fewer reports that the tablet doesn't work, because there was never a screen in the way to begin with — and a manual that keeps up with the floor because the floor could always talk back to it. What to do with a correction that keeps recurring is still a person's call, on the OEM's engineering team, and what happened on any one machine stays with that machine, in the customer's building.

Nirdesh · drag to turn
The same procedure tree as the other Nirdesh posts, but every link here carries sound, not a tap — there is no touch surface anywhere in the drawing. The orange node is the same as always: the person on the floor, not the model, deciding whether a correction is real.

Nirdesh is the second of three engineering aids under VarahiEdge. VEDA reasons about a fault from the machine's own signals, and VCAD turns a description into a manufacturable part. All three run on the same on-premise box, inside the building where the machines actually are.

Read about VarahiEdge