Nine environments, nine different dominant constraints. This is the index to every industry page we publish — what actually changes between an airport concourse, a hostel block, a guest floor, a ward, a racking aisle, a shop floor, a plant, a civic building and a village, and which part of the design has to move first. Immunity Networks & Technologies designs and manufactures the wireless, switching, optics and control layers behind those environments as an Indian OEM, with hardware built at our Sanand GIDC facility in Gujarat and engineering run from our Powai, Mumbai head office.
A network specification is usually settled by a single constraint long before the others get a hearing. Everything downstream follows from it.
In an airport concourse the deciding factor is the number of unfamiliar devices that arrive together and expect to be online within seconds. In a hospital it is the wall between clinical systems and everything else. In a warehouse it is what steel racking does to a signal on the night shift when the pick rate is at its highest. Access point count, mounting method, switch port budget, VLAN plan, portal design and the cable route all follow from that one decision. Get the deciding constraint wrong and the rest of the build becomes a well-executed answer to the wrong question — which is the expensive kind of mistake, because it is only visible once the venue is occupied.
That is why this page is organised as a catalogue of constraints rather than a list of logos. Each industry page below leads with the thing that is genuinely different about that environment, and treats the rest — the parts that are common to all enterprise wireless work in India — as the supporting layer it actually is. If you are searching for vertical networking solutions in India and finding the same paragraph reprinted under nine headings, this catalogue is deliberately written the other way round.
The second reason for the structure is practical. Most of the people who read this page are not buying for one venue type. A hospitality group runs banquets and back-office. A university runs lecture theatres, hostels and an outdoor quad, and increasingly a small clinic. An industrial group runs a plant, a warehouse and a corporate office on the same WAN. A system integrator bidding a venue tender may be asked to price all of it in a single bill of materials. Reading across the verticals is therefore the normal case, not the exception, and the comparison further down this page exists so that you can see at a glance where two environments genuinely diverge and where they can share a design pattern and a management plane.
Third, there is a hardware consequence. Indoor high-ceiling spaces, per-room coverage, racking aisles and open outdoor spans are four different mounting and antenna problems, and they are answered by different members of the same product family rather than by one universal access point. The product catalogue and the solutions catalogue sit alongside this page for that reason: this page tells you which environment you are in, those pages tell you what gets installed in it. We do not publish coverage figures, device counts or deployment sizes on a web page, because they come from a survey; ask us to confirm current specifications in writing for the specific model you are evaluating.
Each tile leads with the constraint that decides the design. Follow the link for the full treatment of that environment.
Terminals, concourses and forecourts. The population changes completely every few hours, the building is one enormous open volume with very little to attenuate a signal, and passenger traffic must never share a broadcast domain with airline, ground-handling or tenant systems. Capacity is designed by concurrent devices in gate and queue areas, not by floor area.
Universities, colleges and schools, including hostels, lecture theatres and outdoor quads. Hostel blocks concentrate several always-on personal devices per occupant into small rooms with hard walls, and the whole estate swings between an empty vacation and a full term, an examination window or an admission season. Seasonal surge is the planning unit.
Guest floors, banquet halls, restaurants and the back of house. Coverage is judged one room at a time by a guest who will write about it, so per-room signal and per-room capacity matter more than corridor averages. Onboarding is expected to recognise the guest from the property management system rather than ask for a form.
Wards, outpatient departments, diagnostics, theatres and visitor areas. The deciding constraint is isolation: clinical applications, connected medical devices, staff mobility and attendant or visitor access belong on separate policy domains with no routed path between them. Coverage must also hold at bedside and in shielded rooms, not merely in the corridor.
Racking aisles, dock doors, cold stores and outdoor yards. Metal racking and dense stock turn a shed into a set of long reflective corridors whose radio behaviour changes as the stock profile changes. Handheld scanners must roam along an aisle without dropping a session, and the yard needs the same continuity outdoors.
Store floors, stockrooms, checkout lanes and multi-site chains. The constraint that governs the build is separation of payment and point-of-sale traffic from customer Wi-Fi and from back-office systems, repeated identically across every store so that a new site can be brought up from a template rather than designed again from scratch.
Plant floors, fabrication sheds, utilities and stores. Motors, drives, welding, induction heating and heavy moving metal make the radio environment change with the production schedule, and operational technology must be separated from the ordinary IT estate as a matter of structure rather than as an access-list edited later.
Civic offices, departmental buildings, public counters and citizen-facing facilities. Here the deciding constraint is not radio at all: it is procurement. Tender wording, local-content expectations, per-model approval evidence, documented logging and an auditable handover shape what can be quoted before anyone discusses coverage.
Villages, panchayat premises, common service points and roadside locations. Distance and power are the constraints. Coverage is delivered outdoors over open spans with weather, dust and temperature to survive, backhaul is whatever is genuinely available at that location, and mains supply cannot be assumed to be continuous.
The same seven priorities exist in every project. What changes from venue to venue is which one is allowed to set the specification.
The chart below is the reason this catalogue exists. Read it across a row and you have the shape of a project: where the survey effort goes, which layer of the stack carries the risk, and which questions a tender will keep coming back to. Read it down a column and you can see which venues can genuinely share a design pattern. A retail chain and a hospital, for example, look nothing alike on the shop floor but share an almost identical requirement for hard traffic separation; a warehouse and a plant share a difficult radio environment and diverge sharply on onboarding, because a scanner does not read a splash page.
Two rows deserve a word of caution. Government scores highest on procurement evidence not because the radio design is trivial but because a public-sector project can be lost or won on documentation alone, and the network design is frequently the least contested part of the file. Rural scores highest on power and backhaul for the opposite reason: the wireless is comparatively straightforward, and the project succeeds or fails on whether the site stays energised and connected through the year. In both cases the effort is real, it simply does not sit where a wireless engineer would instinctively look for it.
The short version of each industry page, and why one venue’s answer cannot simply be copied into another.
An airport terminal concentrates a very large number of unfamiliar devices into gate hold rooms, security queues and immigration halls for short, predictable windows, and does it inside a building made largely of glass, steel and open volume. Because there is so little to attenuate a signal, cells overlap more than the designer intended and clients hold on to distant access points instead of roaming cleanly. Capacity therefore has to be designed by concurrent devices and traffic segregation planned as a structural property of the network, which is the substance of our airport Wi-Fi solutions page. Passenger traffic, airline and airport operational systems and each retail or lounge tenant sit on distinct VLAN sets, and the passenger domain has no routed path into the operational one.
Rural connectivity is the same public-access problem with every assumption reversed. Instead of thousands of devices in one hall you have modest numbers spread over open ground, so the design question becomes outdoor reach across spans that have no cable route, on mounting positions exposed to sun, dust, rain and temperature swings. Backhaul is whatever genuinely exists at that location rather than whatever the design would prefer, and mains power cannot be assumed to be continuous through the day. Our rural connectivity page deals with outdoor-first design, power budgeting and the public-access authentication that usually accompanies it. Government projects sit between the two: civic buildings are ordinary indoor spaces, but the government and public sector page is mostly about procurement, because the tender defines what may be offered before the site is ever visited.
Education, hospitality and healthcare are all buildings people occupy for long periods, and all three are judged room by room rather than in aggregate — but for three different reasons. On a campus, the hostel block is the hard part: a small room with hard walls, several always-on personal devices per occupant, and an evening peak that has nothing in common with the daytime lecture-theatre peak. Add the seasonal swing between vacation, term, examinations and admissions and you have a network that must be provisioned for a surge it experiences only a few weeks a year. Outdoor quads, sports areas and inter-block links then extend the same estate into the open. That combination is the subject of our campus wireless page.
A hotel has a similar per-room geometry and a completely different service expectation. The guest judges coverage in one room, on one device, in the first five minutes, and expects to be recognised rather than interrogated — which is why property management system integration, room-number-and-name onboarding, banquet capacity that appears and disappears with the event calendar, and clean separation between guest traffic and hotel operations are the substance of our hotel Wi-Fi solutions page. A hospital keeps the per-room coverage requirement and replaces the commercial constraint with a clinical one. Clinical applications, connected medical devices, staff mobility and attendant or visitor access belong on separate policy domains, and the isolation between them has to be enforced structurally rather than by a rule someone can later relax. Bedside coverage, shielded rooms and equipment-dense areas make the radio design unforgiving as well. Our hospital Wi-Fi solutions page works through that separation in detail.
A warehouse is a radio problem before it is anything else. Steel racking and dense stock turn a shed into a set of long reflective corridors, and the behaviour of those corridors changes as the stock profile changes, which means a design validated against a half-empty building can disappoint against a full one. Handheld scanners and vehicle-mounted terminals have to roam the length of an aisle without dropping a session, dock doors and cold stores each behave differently again, and the yard outside needs the same continuity from outdoor hardware. Our warehouse Wi-Fi solutions page covers aisle-oriented placement, mounting height, cold store and dock considerations and yard coverage as one continuous problem.
Retail shares the multi-site discipline and swaps the dominant constraint. Payment and point-of-sale traffic must be separated from customer Wi-Fi and from back-office systems, and that separation has to be identical in every store so that a new site is brought up from a template rather than redesigned. Customer Wi-Fi then carries its own onboarding and its own policy, and store teams need something they can operate without an engineer on site. That is the ground covered by our retail Wi-Fi solutions page. Manufacturing takes the warehouse radio problem and adds an industrial one: motors, drives, welding, induction equipment and heavy moving metal change the environment with the production schedule, and operational technology has to be separated from the ordinary IT estate as a structural decision, agreed with the people who own the plant, rather than as an access list edited afterwards. Our manufacturing plant Wi-Fi page addresses interference, enclosure and mounting choices in production areas and the OT boundary.
Read together, the pattern is straightforward. Density-led venues need capacity design and roaming discipline. Isolation-led venues need a VLAN and policy structure that a future administrator cannot casually undo. Radio-led venues need survey work that reflects the building when it is full and working rather than when it is empty. Reach-led venues need outdoor hardware, honest power budgeting and a backhaul plan. Document-led venues need evidence, in writing, per model. Almost every real project is a blend of two or three of these, and the blend is what the first conversation is for.
Nine environments do not need nine product families. They need one family, selected and mounted according to what the building actually is.
The indoor and outdoor access point family behind every environment on this page. Model choice follows the survey rather than the other way round, and we will confirm current specifications in writing for the specific model proposed.
Indoor coverage for concourses, lecture theatres, guest floors, wards, store floors and offices, with mounting options for the soffits, gantries and columns that these buildings actually offer.
Forecourts, yards, quads, perimeters, village sites and roadside locations, rated for the weather, dust and temperature range those positions genuinely see rather than the range a datasheet photograph implies.
L2 and L3 switching that powers access points over PoE and enforces the VLAN separation between guest, clinical, payment, operational and tenant domains in hardware rather than as a policy that can be edited away.
Captive portal, authentication, session policy and logging for guest, passenger, student, patient-attendant and public-access networks, including the branded onboarding that hospitality and aviation both depend on.
One AIOps console across sites, so a multi-site chain, a multi-block campus or a group with a plant, a warehouse and an office is operated from a single management plane instead of one console per venue type.
Between those layers sit the ordinary but decisive details: fibre and optics between blocks, risers and remote buildings; PoE budgeting that reflects the access points actually chosen; and enclosures and mounts appropriate to a plant, a yard or a public concourse. The full range is set out in the products catalogue, while the design patterns those products serve — campus wireless, switching and routing, network security, captive portal and public Wi-Fi — are described in the solutions catalogue. If your estate spans several of the environments on this page, they can share one management plane rather than becoming several vendor relationships.
Whatever the venue, the questions a serious Indian buyer asks are broadly the same. They are worth asking us as well.
Indian buyers increasingly require MTCTE, TEC and WPC approvals to be demonstrated per model rather than per brand, and the right approach is to ask for written confirmation covering the exact SKUs in the bill of materials rather than accepting a statement about a product family. Ask us for that, ask every other bidder for it, and attach the responses to the tender file. Our certifications page is the place to begin that conversation. The same discipline applies to performance: do not accept coverage figures, device counts or throughput claims from a web page, ours included. Ask for current specifications in writing for the specific model, against the specific site, after a survey.
Public Wi-Fi carries its own framework questions, and two facts about our position are frequently confused, so we state them plainly. With BSNL, Immunity is a Public Wi-Fi Partner. Separately, under PM-WANI, Immunity is a certified PDO Aggregator (PDOA). These are two distinct roles under two distinct arrangements, and we are not a PDO. Our PM-WANI page sets out what each role means and what it does and does not allow, which is the right starting point if your tender documentation asks about framework participation. Institutional venues — transport hubs, hospitals, campuses and civic buildings — are increasingly expected to consider interoperable public authentication alongside their own portal, and it is easier to allow for that at design time than to retrofit it later.
Being the manufacturer changes the shape of a project in ways that matter mostly after the invoice. Engineering change requests, firmware questions, mounting variations and warranty escalations are answered in India rather than routed through an overseas principal, and hardware is built at our Sanand GIDC facility in Gujarat with engineering and support run from Powai, Mumbai — which is also what most Make-in-India and local-content clauses are actually testing for. For integrators, that is the basis of our partner programme: design support, a clean bill of materials and someone who will answer a clarification question inside the tender clock. Anonymised deployment write-ups across several of these environments are collected in case studies, and datasheets sit in downloads. They are deliberately written without identifying the venue or the operator, and they describe approach, sequencing and what we would do differently rather than headline numbers.
Describe the building, the people in it, the systems that must stay apart and where coverage disappoints today. Our engineers will come back with a design approach, a zone-by-zone plan and datasheets, and will confirm current model specifications in writing.
Most real sites do not. A mixed-use development, a township, a stadium, a transport depot or a corporate headquarters with a manufacturing annexe will borrow constraints from two or three of the environments on this page. That is precisely why the catalogue is organised by constraint rather than by sector name: identify the constraint that dominates your building and the nearest industry page will be broadly right, then tell us where it diverges. The first conversation exists to settle exactly that.
One family, selected differently. Indoor high-ceiling spaces, per-room coverage, racking aisles and open outdoor spans are four different mounting and antenna problems answered by different members of the NetWave Lotus Alpha range, powered by the same NetForce switching and managed from the same NetCloud Central console. What changes between venues is model choice, mounting method, access point placement density and policy design, not the vendor or the management plane.
Because those numbers only mean something against a specific building and a specific model, and a figure quoted out of that context tends to be repeated into a tender where it becomes a commitment nobody surveyed. We will give you numbers — after a site survey, in writing, tied to the exact models in the bill of materials. Ask us to confirm current specifications in writing for the specific model you are evaluating, and treat any vendor unwilling to do that with appropriate caution.
Separation is carried as distinct VLAN sets in NetForce switching with policy applied at the NetGuard controller, so the boundary between guest, clinical, payment, operational or tenant domains is a structural property of the network rather than a rule sitting on top of a flat design. It can of course be reconfigured by an administrator with the right rights — nothing is immutable — but it cannot be dissolved by accident, and the design documentation records what was agreed and why.
Ask for MTCTE, TEC and WPC approval status confirmed in writing per model, covering the exact SKUs quoted, rather than a brand-level or family-level statement. Ask for it from every bidder including us, and keep the responses in the tender file. Indian buyers are asking for this more often, and a per-model answer is the only kind that survives scrutiny at evaluation. Our certifications page is the right starting point for that request.
No, Immunity is not a PDO. Under PM-WANI, Immunity is a certified PDO Aggregator, or PDOA. Separately, and under a different arrangement, Immunity is a Public Wi-Fi Partner with BSNL. The two roles are distinct and should not be treated as interchangeable in tender documentation. Our PM-WANI page explains the difference and what each role permits.