KVARSince 1988

Instruments built to your specification, under your name.

Embedded design, firmware, enclosure and manufacture — for companies that need a product built properly and cannot justify an electronics team to do it.

What we do for OEM customers

Some customers come to us because no instrument exists that does what they need. Others have a product and no in-house electronics capability to build it. In both cases we can take it from specification through design, firmware, enclosure and volume manufacture — and it ships under your brand, not ours.

The capability, plainly stated

  • Embedded hardware design: schematic, PCB layout, analogue front ends, power, industrial I/O.
  • Firmware: microcontroller and ARM platforms, RTOS, and industrial protocols including Modbus, Profinet and BACnet.
  • Connectivity: RS-232, RS-485, Ethernet, Wi-Fi and cloud.
  • Enclosure and panel: mechanical design, membrane and display integration, IP rating.
  • EMS manufacturing: PCB and SMT assembly, box build, functional and burn-in testing at Mahim, prototype to volume.
  • Engagement models: build-to-print, design-and-build (ODM), or white-label.
  • Sustaining: we keep the drawings. Boards we built over a decade ago are still supportable.

Why a thirty-eight-year track record matters here

Our own history is largely a sequence of things that did not exist and had to be made. India’s first almanac-based street light timers for BEST. An indigenous PCM link tester for the Department of Telecom, which won the G.S. Parkhe Award. End-of-line vehicle testing for Mahindra, Ashok Leyland and Fiat when importing it proved prohibitive. The Route Data Preparation System behind Indian Railways’ country-wide GPS mapping.

That is the work an OEM customer is buying: a team that has repeatedly built the instrument nobody was selling. Read the full history.

How an engagement usually starts

With an NDA and a conversation about what the product has to do, not what it should contain. We will tell you if an existing product in our range or anyone else’s already solves it, because a custom development you did not need is bad for both of us.

Common questions

What volumes do you take on?

From low-volume specialist instruments to steady production runs. We are an MSME manufacturer, not a mass-market contract house, which suits products where design quality and long-term support matter more than the lowest unit cost at very high volume.

Who owns the design?

That is agreed in writing at the outset, before design work starts. Arrangements vary and we have no fixed position we insist on.

Will you sign an NDA first?

Yes. For most OEM conversations we would prefer to.

What if we only need the firmware, or only the manufacturing?

That is fine. Not every customer wants the whole chain, and we are happy to take a defined part of it.

Tell us what the product has to do.

Start under NDA