Smart City IoT Solutions for Parking, Drains, Water and Waste

The ones that come from assets nobody can see: bays that fill, drains that block, overhead tanks that run dry or overflow, bins that overflow, feeders left on in daylight, meters read by hand and toilets cleaned on a round. A battery-powered sensor on each asset reports over the city's own LoRaWAN network, and the ICCC acts on the reading instead of the complaint. Cameras, ANPR and traffic signals are a different class of equipment and are not what this hardware does.

Geomagnetic parking sensors in bays (ParkNode Gen-1); ultrasonic level sensors over drains, tanks and under bin lids (MacRay LUS X1); rain sensors and weather stations on the wards; pressure transducers on the water network; CO₂, NH₃/H₂S odour and sound level sensors; people counters at facility doors; capacitive fuel level sensors on generator tanks; MacSync converters that read existing water and energy meters over Modbus; MacSet controllers that switch lighting feeders and pumps; and LoRaWAN gateways that carry all of it. Every device is listed in the table on this page with its datasheet.

A ParkNode Gen-1 sensor is fixed in each bay, surface or flush mounted. Its three-axis magnetometer detects a vehicle above 98 % of the time and reports arrival and departure within 7 to 10 seconds over LoRaWAN to a gateway on a rooftop or a pole. The network server decodes the event and passes it to the guidance signs, the enforcement app and the ICCC. The X1 variant is rated up to 10 years on its battery and the X2 up to 5, depending on how busy the bay is. The parking page and the comparison page carry the figures.

LoRaWAN is the city's own network: a few gateways per ward, no SIM in any device, no plan per device, and the keys and the data held by the corporation. NB-IoT is the operator's network: coverage, including deep indoors, where the operator provides it, a SIM and a plan in every device, and the operator's terms. Cities that want to own the infrastructure and add departments to it over time choose LoRaWAN; those that will not run gateways and have confirmed NB-IoT coverage choose the operator. Macnman makes LoRaWAN, Wi-Fi and 4G devices.

With LoRaWAN, gateways. A MacLink Gen-2 on a rooftop carries more than 2,000 devices on eight channels, and the only SIM is the one in the gateway's 4G backhaul, if it does not have Ethernet. A thousand parking and bin sensors therefore need a handful of gateway backhauls, not a thousand plans. 4G devices, used for isolated pumping stations, do carry their own SIM.

Yes, and that is the point of owning it. ChirpStack and The Things Stack organise devices into tenants and applications, so the parking cell, the water department and the sanitation wing each see their own devices on the same city-owned gateways, with their own users and their own data feeds into the ICCC. A new department adds devices, not a network.

As a working estimate, one rooftop gateway typically covers 2 to 5 km across a built-up ward, so most wards need one to three, plus an indoor Setu X1 for each basement car park. Dense high-rise and sensors at ground level under cars shorten the range, which is why the pilot includes a coverage check with a sensor at the real mounting point. The gateway and coverage calculator on this site gives a first count from the ward map.

Yes, and the hardware carries it. LoRaWAN in India uses the IN865 plan in the 865 to 867 MHz band, which the Wireless Planning and Coordination wing has delicensed for low-power devices, so the corporation needs no spectrum licence to run its own gateways. Macnman devices are built for IN865 and are WPC compliant; the compliance documents are supplied for the tender file.

Yes. The devices register on any LoRaWAN network server, and the server delivers decoded JSON over MQTT or HTTPS to the ICCC, SCADA or dashboard. Payload decoders are published on GitHub, so the integrator can map the fields before the first device arrives. Commands, such as switching a feeder, go back the same way as downlinks.

Yes. Macnman supplies sensors, converters, controllers and gateways with published payload formats and no mandatory platform. The city's network server and ICCC stay as they are; the MSI connects the MQTT or HTTPS feed.

The corporation owns it. ChirpStack can run on the MacLink gateway, on a server in the corporation's data centre or in a government cloud; the device keys and every reading stay there. Nothing passes through a Macnman account, and there is no subscription in the path.

No. The devices work with any LoRaWAN network server and any broker. A hosted platform is a choice the city or the MSI makes, not a condition of using the hardware.

A datasheet and a user guide for each device, WPC compliance for the IN865 radio, RoHS conformity, payload decoders and integration notes, mounting guides, and a quote by quantity and band. If the tender asks for a document that does not exist yet, we say so rather than improvise.

Both. Most Smart Cities Mission work runs through a master system integrator, and we supply the MSI with hardware, documents and engineering support; corporations, SPVs, utilities and parking operators also buy directly for pilots and departmental projects. The partner programme on this site is for integrators who want a standing arrangement.

Yes, and we recommend it. The pilot kit is a gateway with a few parking, level and bin sensors on the city's own network server, with the same hardware the tender will scale. The coverage map, the battery readings and the ICCC feed from the pilot go into the DPR with real figures.

Yes, at feeder level. A MacSet controller in the feeder pillar switches the feeder on a schedule, on a light-level input or from the control room, reports run status and fault inputs, and reads the feeder's energy meter over RS485. It is not a per-lamp dimming controller; where a tender specifies per-lamp control, that is a separate device. Check the tender's controller specification against the MacSet datasheet before quoting it.

A MacRay LUS X1 ultrasonic sensor under the lid measures the distance to the waste, from 3 cm to 450 cm, and reports it over LoRaWAN on a schedule and when a threshold is crossed. The collection plan then goes to the bins above the threshold instead of every bin on the route, and an overflowing bin is known before the complaint. The waste-bin case study on this page describes a deployment.

An ultrasonic sensor mounted above the drain, culvert or nullah reports the water level without touching it; a rain sensor or weather station on the ward reports rainfall intensity alongside it. A blockage shows as a level that rises without rain, and a surge shows as a level that rises with it, and either raises an alert in the control room while a crew can still reach the spot.

Yes, where the meter has an RS485 Modbus port or a pulse output, which most bulk water meters and pumping-station energy meters do. A MacSync LX1 converter polls the registers on a schedule and sends them over LoRaWAN; a 4G version does the same from an isolated pumping station. The meter stays, and the readings land in the billing or SCADA system the utility already runs.

A MacRay LUS X1 above the water in the ESR or the sump reports the level; a MacSet LX1 at the pump switches on a low threshold and off on a high one, with the rule running on the controller so it works through a network drop. Line and hydrant pressure from the pressure transducer show a burst or a closed valve on the same dashboard.

A LoRaWAN odour sensor reads ammonia and hydrogen sulphide inside the toilet block and reports the level on a schedule and when it crosses a threshold, so cleaning is sent to the block that needs it. A people counter at the door adds footfall, and a tank level sensor shows whether there is water. The washroom monitoring article linked on this page explains the set-up.

From the datasheets: the ParkNode Gen-1 X1 is rated up to 10 years and the X2 up to 5, depending on the number of parking events a day; the MacRay LUS X1 is rated about 3 years at hourly reports, about 2 at 15 minutes and about 1 at 5 minutes on its 8 Ah cell. Battery level is sent in every message, so replacement is planned from the dashboard, not discovered on the street. Ask us about end-of-life replacement for each model.

The ParkNode Gen-1 is IP68, rated from −40 °C to +80 °C, and is designed to be driven over; the gateways are IP67; the ultrasonic level sensor has an IP67 transducer for the drain and the bin. The datasheets carry the figures, and the article on parking sensors and vehicle load linked on this page covers the road.

Sensors keep transmitting, and any other gateway in range receives them, which is why ward plans overlap gateways. Controllers keep running their schedules and thresholds locally. Readings that no gateway heard appear as a gap, and the next scheduled reading arrives when the link returns; the ICCC treats a missing heartbeat as an alarm.

Four lines, and the device is only one: the number of points per application, the gateways needed for the wards and the basements, the mounting at each point (flush or surface for bays, brackets for drains and lids), and the integration into the ICCC, which is usually the MSI's scope. Hardware is quoted by quantity and band; send the point list by application and a ward map and we quote the whole deployment.

Yes. Macnman Technologies designs and manufactures its sensors, converters, controllers and gateways in Pune, Maharashtra, with WPC compliance for the IN865 radio, and supports them from the engineering team.

Compare on what the datasheet states rather than on the brochure: detection or measurement figures with their conditions, battery life with the traffic or interval it assumes, the IN865 plan and WPC compliance, the ingress rating, published payload decoders, and where the hardware is designed and supported. Macnman designs and manufactures its parking, level, odour, noise and climate sensors, converters, controllers and gateways in Pune, publishes datasheets and decoders, and the comparison pages on this site set the ParkNode, the level sensor and the gateway beside other makers' published figures with sources.

Yes. As the manufacturer, Macnman adapts firmware, payload formats, enclosures and branding for city platforms, integrators and tender orders. Customisation depends on volume; share the quantity and the change you need and we will say what is possible.