Scaling a Water Meter Monitoring System for 50+ Units: NE101 + NG4500 Architecture

When Does LTE Stop Making Sense at Scale?

When you deploy 5–10 NE101 cameras on individual LTE Cat.1 SIM cards, the architecture is simple: each camera connects independently to cellular, uploads images to an MQTT broker, and your OCR pipeline processes reads on a server. For scattered remote sites, this remains the right approach.

At 50+ meters concentrated on one building, campus, or industrial facility, the economics and operational complexity change. With IoT SIM pricing at $1–3 per device per month, 100 units adds $1,200–$3,600/year in recurring connectivity costs. Managing 100 APN configurations, SIM renewals, and independent reconnect cycles becomes a maintenance burden. If images must stay entirely on-premises for compliance or privacy reasons, routing through cellular may also be architecturally undesirable.

At this point, centralized OCR on an NG4500 is a strong production architecture. NE101 cameras can reach the same NeoMind host over local WiFi/HaLow or over LTE Cat.1 when a secure network route is available. Local radio links remove per-camera SIM costs and can keep image traffic on-site; LTE remains useful when the meters are spread across a plant or beyond local radio coverage. The NG4500 aggregates images, runs OCR, and delivers readings to SCADA or BMS in either case.

System Architecture

In large-scale deployments, image capture and OCR inference are handled separately. NE101 units capture and transmit images at each meter, while NeoMind on the NG4500 processes OCR centrally. A PC or other suitable Linux host can run NeoMind for evaluation; for a 50-camera production rollout, the NG4500 is our recommended central host. This reduces per-device cost, simplifies maintenance, and keeps AI workloads off battery-powered field devices.

The architecture consists of three layers:
1. Capture nodes: NE101 cameras installed at each water meter to capture images on schedule or by event.
2. Network path: NE101 uses WiFi or WiFi HaLow to an AP/gateway, then LAN/Ethernet to the NeoMind host; or Cat.1 over the carrier network to a reachable host.
3. Centralized edge inference: NeoMind on NG4500 runs OCR and sends structured readings to your monitoring platform.

Local Connectivity Options:
WiFi HaLow is well suited to basement meters and longer links when an AP can reach the installed cameras. WiFi works when existing coverage reaches the meter locations. In both cases, Ethernet is the AP/gateway’s LAN backhaul to the NeoMind host, not an NE101 interface. For geographically dispersed meters, LTE Cat.1 cameras can upload through the carrier network to the same centralized host, provided its MQTT endpoint is reachable.

Choosing the Right NG4500 Model:
For scheduled meter-image OCR, NG4510 (Orin Nano 4GB, 20 TOPS) is an entry point for a lighter fleet, while NG4511 (Orin Nano 8GB, 40 TOPS) gives a 50-camera rollout more memory and processing headroom. CamThink’s engineering sizing for a standard NG4521 (Orin NX 16GB, 100 TOPS; 157 TOPS in SUPER mode) is 100 NE101 cameras for scheduled meter captures. Beyond that, size from capture frequency, peak upload bursts, OCR model mix, and storage needs rather than camera count alone.

Recommended Hardware for a 50-Unit Pilot

A representative hardware stack for deploying 50 NE101 cameras with a centralized gateway architecture. Scale the NE101 count to your site requirements and choose connectivity based on existing infrastructure.

NE101 Variant Selection

NG4500 Sizing

Choosing the Right NG4500 for Your Deployment

*The 30–50 and 50-camera figures are planning scenarios; the NG4521 100-camera figure is CamThink’s engineering baseline for scheduled meter captures. Peak uploads, OCR latency, model mix, and retention drive final sizing.

Cost Comparison: Local WiFi/HaLow vs Individual LTE

The example below compares 100 NE101 cameras over three years. Both network paths use a central NG4500 for NeoMind OCR; the inputs are $2 per LTE SIM per month, $120–180 per year for host electricity, and the hardware ranges shown in the table. Installation, maintenance, taxes, and existing network costs are outside this comparison.

3-Year Cost Comparison

Operational Comparison

With the inputs above, the local WiFi/HaLow path is already cheaper by the end of Year 1. Lower SIM rates or new AP installation shift the crossover.
WiFi is most cost-effective where coverage already exists; HaLow is useful when its measured link reaches meters that standard WiFi cannot. A 50-camera fleet can still use LTE Cat.1 with central NG4500 OCR when local radio coverage is impractical.

Deployment Workflow

Deploying 50-300+ cameras requires planning but doesn’t have to be complex. The workflow below separates preparation, installation, gateway setup, and validation into distinct phases. Each phase is designed to scale efficiently: batch device preparation reduces on-site time, bulk configuration accelerates setup, and early validation prevents costly rework.

MQTT Payload and OCR Integration

Each NE101 publishes its image payload over WiFi, WiFi HaLow, or 4G LTE Cat.1; the radio path changes, but NeoMind still receives the image at its MQTT endpoint. WiFi and HaLow reach the host through an AP/gateway and LAN/Ethernet backhaul. Cat.1 cameras can be spread across the plant and upload through the carrier network to the same reachable host. NeoMind decodes the image, runs OCR on the NG4500, and delivers structured readings to monitoring systems through the configured OpenAPI, Data Push, or Webhook integration.

{
  "ts": 1740640441620,
  "values": {
    "devName":     "NE101-WM-045",       // Configurable device name
    "devMac":      "D8:3B:DA:4D:10:2C",
    "battery":     84,                  // Battery % — monitor for replacement planning
    "snapType":    "Scheduled",          // Scheduled | Button | PIR | Alarm
    "localtime":   "2026-04-22 06:00:00",
    "imageSize":   74371,               // bytes
    "image":       "data:image/jpeg;base64,..."
  }
}

{
  "device_id":   "ne101-wm-045",
  "site":        "building-b-level2",
  "meter_id":    "WM-045",
  "timestamp":   "2026-04-22T06:00:05Z",
  "ocr_value":   "01027.8",
  "unit":        "m3",
  "battery_pct": 84,
  "source_topic": "meters/building-b/wm-045"
}

For lightweight OCR models running on the NG4510, inference is typically sub-second per image. End-to-end latency depends on model complexity, queue depth, and the selected Jetson Orin variant.

Fleet Operations at Scale

Managing 50-300+ cameras requires operational processes beyond simple installation. NeoMind provides the management layer, but long-term success depends on disciplined maintenance workflows. Key operational areas include:

Battery Replacement Planning

At 3+ years battery life (10 captures/day in WiFi mode), replacement is infrequent but predictable. For 100+ deployments, schedule replacements proactively rather than reactively. Use NeoMind alerts at 20% battery remaining, then plan bulk replacement events within a 3–6 month window to reduce site visits.

Automated Alerting Strategy

Use tiered alerts to avoid alarm fatigue while catching issues early:
Critical — immediate action required
device offline >24h, battery < 10%, OCR confidence below threshold
Warning — maintenance planning
Battery <20%, device offline >12h, image quality degradation
Informational — trend monitoring
Monthly battery reports, read success trends, anomaly detection

OTA Firmware Updates at Scale

Treat firmware changes as a staged fleet operation. The standard NE101 upgrade path is the device Web UI; projects with a remote OTA integration can use the same release sequence:
1. update 5–10 devices first
2. monitor captures, uploads, and battery behaviour for 24–48 hours
3. continue by site or device group after validation
For mission-critical deployments, retain the prior firmware and a recovery procedure.

Device Grouping and Access Control

For deployments across multiple buildings or sites, organize devices by building, floor, meter type, or deployment phase. This simplifies monitoring by making it easier to isolate issues and view relevant metrics without filtering through hundreds of devices.
Grouping also enables granular access control, so maintenance teams only see and manage the devices relevant to their assigned location or responsibility.

Storage and Retention Planning

At 4–6 reads/day with ~50–100KB images, a 100-device deployment generates roughly 7–22GB/year of raw images. Allow additional space for metadata, indexes, temporary files, and backups; longer retention periods increase storage requirements.
A common strategy is to retain raw images locally for 6–12 months, then archive or delete older data automatically based on compliance or audit requirements. NeoMind can automate retention and cleanup policies at scale.

Backup and Disaster Recovery

For production deployments, back up NeoMind configuration regularly, including device registration, automation rules, and dashboard layouts. Store backups externally or on a network location, and document the restore process so recovery is fast in the event of failure. For redundancy-critical sites, consider a warm-standby NG4500 with replicated configuration to minimize downtime.

When Not to Deploy a New HaLow Network

A new HaLow AP network is most useful for concentrated deployments where standard WiFi cannot reach the meters. The central NG4500 OCR host can also receive from LTE Cat.1 or existing WiFi. Consider those paths when:

Geographically Scattered Meters
If meters are spread across a wide area — such as rural water meters across 50 km² service area — one local WiFi or HaLow AP may not cover them. Per-device LTE Cat.1 can still bring images to a centralized NG4500 over the carrier network; the host does not need to sit within radio range of every camera.

Small Deployments (<20 units)
For smaller deployments on one site, a new HaLow AP may not pay back against existing LTE or WiFi coverage, especially for short-term projects. NeoMind still needs a host for OCR; a PC or Linux machine can serve an evaluation before selecting the production NG4500.

Existing WiFi Already Covers the Site
If your site already has reliable WiFi at all meter locations, a WiFi-based gateway architecture is often more cost-effective than deploying new WiFi HaLow infrastructure. Use HaLow only when range, walls, or interference prevent standard WiFi coverage.

Frequently Asked Questions