Skip to content
TechnoGuru — Think Technology, Think TechnoGuru
Verifiable · ISO 9001:2015 · CEDIA · AVIXA

Audit us before you award.

Government, hospital, hospitality and enterprise procurement teams routinely verify systems-integration practices before signing. This page collects every credential, statutory registration and external profile in one surface — so the audit is a five-minute read rather than a five-email chain.

Statutory registrations

Government-issued IDs.

MSME / Udyam

UDYAM-AS-03-0002628

Registered as TechnoGuru

IEC (Import Export Code)

1409002756

Issued to TechnoGuru

GeM Seller ID

8E12180000480078

Active · Techno Guru

GSTIN — Assam (Guwahati)

18AHTPB2250R2ZS

GSTIN — Nagaland (Dimapur)

13AHTPB2250R2Z2

GSTIN — Tripura (Agartala)

16AHTPB2250R1ZX

Certifications & designations

International standards.

CEDIA Member

CEDIA Member

Custom Electronic Design and Installation Association — residential AV and home-cinema designation. Continuing-education hours logged annually.

Active

AVIXA Member

AVIXA Member

Audiovisual and Integrated Experience Association — commercial AV designation. Founder holds AVIXA AV Technologist Certificate (March 2016).

Active

ISO 9001:2015

Quality Management System. Audited and certified by VRS Certification Services Pvt Ltd. Scope: audio, video, security products and automation.

Mar 2024 → Mar 2027

ISO 10002:2018

Customer Satisfaction & Complaints Handling. Issued by IPQC. Scope: quality management — customer satisfaction; complaints handling in organisations.

Mar 2024 → Mar 2027

HAA Level 1 Calibrator

Home Acoustics Alliance — high-end home-theatre acoustic tuning to HAA standards. Founder-held; March 2016.

K-Array Certified Designer

K-Academy (AVIXA CTS RU Provider) — loudspeaker system design for K-Array Italian premium line-array. December 2025.

Full credential register on /credentials — including individual founder certifications across Harman, Alcatel-Lucent, Rako and others.

Industry memberships

Chambers & trade bodies.

  • ISO 9001:2015

    ISO 9001:2015 Quality Management System

    Internationally-recognised quality-management-system certification, certified by VRS Certification Services Pvt Ltd. Issued March 2024, valid through March 2027.

  • ISO 10002:2018

    ISO 10002:2018 Customer Satisfaction & Complaints Handling

    Customer-satisfaction and complaints-handling certification, issued by IPQC. Issued March 2024, valid through March 2027 — applicable to audio, video, security products and automation.

  • CEDIA

    Custom Electronic Design & Installation Association

    Member since 2020. Global association for residential cinema and home-automation engineering; continuing-education hours logged annually.

  • AVIXA

    Audiovisual and Integrated Experience Association

    TechnoGuru's founder holds the AVIXA AV Technologist Certificate (issued March 2016) — professional audiovisual capability that backs the studio's commercial-AV, auditorium, conference-room and collaboration-space work.

  • Young Indian (YI)

    Young Indians — CII Initiative

    Confederation of Indian Industry's youth wing, contributing to national-level industry conversations.

  • FINER

    Federation of Industry & Commerce of North Eastern Region

    Apex chamber for industry and trade across the eight North-Eastern states; we hold an active membership.

  • BAI

    Builders Association of India

    Patron Member of the Guwahati Centre since 30 January 2016. National-level association of builders and infrastructure contractors; relevant to our turnkey ELV and life-safety engagements.

  • LUB

    Laghu Udyog Bharati

    National chamber for MSME and small-industry advocacy; aligned with our MSME registration.

  • FSAI

    Fire & Security Association of India

    Individual membership of the national non-profit representing the fire-protection, life-safety, security, building-automation, loss-prevention and risk-management domains. Founder is an Individual Member, valid 06/2024 to 06/2027.

External entity profiles

Verifiable elsewhere.

We publish on third-party platforms so the audit trail does not depend on this site alone. Each profile below is a verifiable record at the listed authority.

Being published: Google Business Profile — Dimapur, Google Business Profile — Agartala, Wikidata, Crunchbase, OpenStreetMap, Bing Places, JustDial, IndiaMART, Sulekha, CEDIA member directory, AVIXA member directory, Houzz Pro — entity records added here as each listing is verified.

Public factsheet for directories and journalists: /factsheet.txt.

Brand and OEM neutrality

Vendor-neutral by design.

Brand selection is project-led. Our compensation is unaffected by which manufacturer we recommend, and we hold no exclusive distribution rights. The list below is how to read what we say about vendor relationships.

Brand authorisation

Letters held on file

Written authorisation letters are held on file for a limited set of vendors and issued to procurement on request — Sony, Samsung, ViewSonic, AERO Digital, K-Array, KGEAR.

Designer / training

Issuer-verified credential

Vendor-issued designer or system-integrator credentials are listed on the credentials page with the issuer, year and scope (CEDIA, AVIXA, HAA, K-Array, Harman AMX, Harman BSS, Rako DALI, Alcatel-Lucent OXO Connect).

Vendor familiarity

Catalogue we work across

We work across ninety-plus manufacturer ecosystems by training and project history. Familiarity is not authorisation — vendor catalogue width does not imply an exclusive or preferred-partner relationship with any specific brand.

Where two brands are equally suitable for a brief, we say so and let the client choose. Where one is decisively right, we recommend it and explain why, in writing.

Project and media governance

What we publish, and what we don’t.

Approximately seventy per cent of our reference work sits behind contractual confidentiality. The discipline below governs what appears on this website and what stays in the project file.

  • Selected, not exhaustive

    The projects on the site are a chosen sequence — different sectors, different scales, different mixes of disciplines — not the full reference list. Walkthroughs of active deployments are arranged for serious enquiries.

  • Written consent before media

    Photographs, drawings and BOQ excerpts are published only where suitable for public display by the client, the architect or the relevant authority. Government, hospital and hospitality work requires named-authority approval.

  • Drawings sanitised before publication

    Single-line diagrams and topology drawings are stripped of building addresses, panel co-ordinates and title-block client data before they appear in public. Camera viewsheds and access-control maps are not published.

  • BOQ excerpts, never prices

    Where we publish a BOQ extract, it shows scope structure and the brand stack — not unit prices, freight, taxes, margins or supplier identities below the manufacturer level.

  • Patient and operational data stripped

    Hospital and clinical photographs are reviewed for patient identifiers and dashboard data before they appear. Industrial photographs do not show process-control diagrams or safety-bypass procedures.

  • Defence-track work stays in the file

    Police modernisation, secretariat security, and similar engagements are not published until written government clearance is on file. Most of this work is referenced in meetings, not on the website.

The protocol is documented internally at docs/PROJECT_MEDIA_UPLOAD_GUIDE.md and reviewed before every published asset. Procurement teams that need access to the unpublished record can request a reference pack at info@technoguru.in.

Tools and calculator safety

Indicative output, not final design.

The engineering tools at /tools are calculators, planners and code-aware checks — useful for early scoping, not for stamping a drawing. The discipline below applies across the toolset.

  • Every tool shows its assumptions

    Inputs assumed, formulas used, standards referenced and what the tool does not do are visible on the page — not buried in a footer.

  • Output is labelled indicative

    Every projection — runtime, AP count, sprinkler zoning, RT60, ROI — is labelled an estimate and bounded by the conditions stated. None of it replaces a site visit or a chartered engineer’s review.

  • Code-aware tools defer to local authority

    The NBC Fire Checker and related code-aware tools quote the National Building Code as a baseline. Local authority having jurisdiction, state amendments and site-specific conditions always govern final compliance.

  • No personal data captured by default

    Calculators run client-side where possible. Where a tool emails its output, the user controls when and to whom. We do not retain calculator inputs as a sales pipeline.

/ Engineering philosophy

How TechnoGuru approaches the work

These are the published positions the practice applies to every project — not marketing copy, the actual axes of judgement we measure decisions against.

engineering

How TechnoGuru approaches engineering

Every project starts with the building's constraints, not the brand catalogue. Protocols are specified before devices, and the engineering pack is the artefact every other decision is anchored against.

  • · Protocol-first specification — KNX or BACnet decision precedes the controller decision
  • · Engineering pack assembled before the BoQ is published
  • · Cause-and-effect spine documented before commissioning starts
  • · Every spec block cites the clause it answers to, not the standard in the abstract

specification

How systems are specified

Specification is engineering, not procurement. Every clause cites the standard, the protocol or the engineering reason that anchors it; the AHJ and the auditor should both be able to read the pack and recognise the logic.

  • · Clause-level citation — IS 2189 §X, NBC 2016 Part 4 §Y, IEC 62386 §Z
  • · Brand ecosystems specified alongside the protocol they participate in, not as a closed list
  • · Interoperability seams explicitly named in the spec, not assumed
  • · Specification language reviewable by the consulting engineer before BoQ release

lifecycle

How long-term maintainability is considered

Every decision is taken with the day-2,000 building in mind, not just the day-zero handover. Lifecycle considerations are explicit on every engineering pack.

  • · Spares strategy planned at design stage, not at handover
  • · Refresh windows documented for every major subsystem
  • · Vendor-continuity factored into ecosystem selection
  • · Cable colour and labelling conventions documented for future trades

interoperability

Why interoperability matters

Open protocols and documented seams keep buildings integrate-able across vendor changes and product-line shifts. Vendor lock-in is treated as an engineering risk, not a procurement convenience.

  • · BACnet, KNX, DALI, Modbus, ONVIF preferred as backbone protocols
  • · Gateways used only where the engineering case justifies them
  • · Seam-level interoperability documented in the engineering pack
  • · Brand ecosystems chosen for their open-protocol posture, not their proprietary features

documentation

How documentation is treated

Documentation is not a deliverable — it is the engineering pack the building runs on. Every project closes with an updatable engineering record, not a static handover bundle.

  • · Single-line diagrams refreshed at every major change
  • · Cause-and-effect matrices kept live, not frozen at commissioning
  • · Cable schedules and IP plans handed over in editable form
  • · Runbook structured for the FM team's daily reality, not the integrator's mental model

deployment

How deployment is sequenced

Deployment is sequenced by the building's operational rhythm, not by the integrator's convenience. Commissioning is staged to align with the user's reality.

  • · Hospitality deployment staged around brand-readiness windows
  • · Healthcare deployment staged around clinical operational windows
  • · Civic deployment staged around session and ceremony calendars
  • · Residential deployment staged around the family's occupation pattern

maintenance

How maintenance is approached

AMC is an extension of the engineering practice, not a service contract bolted on at handover. Preventive calendars come from the engineering pack; reactive response is the exception, not the rule.

  • · Preventive calendar derived from each system's actual lifecycle profile
  • · Documentation refreshed alongside firmware tracks
  • · Response targets shaped by operational priority, not standard-template tiers
  • · Renewal evaluated on uptime and calendar adherence, not ticket-close-time

governance

How integration accountability is taken

Single-point accountability for integration seams. The FM team runs the building; we own the seams between systems. Vendor coordination is contractual, not ad-hoc.

  • · AMC documents the named seams and assigns ownership
  • · Incident process routes seam-related issues to us
  • · Escalation path published with named responders
  • · Vendor coordination led by us, not handed to the client's FM team

/ Procurement team

Need this in a different format?

We routinely supply credential packs as PDF compendia for government, hospital and enterprise procurement teams — including notarised copies of statutory registrations and ISO certificates. Write to info@technoguru.in with the procurement reference and we will send the pack within two working days.

Trust — Certifications, statutory IDs, GBP and verified profiles | TechnoGuru