Most wireless vibration projects do not stall on the sensors. They stall on the planning around them: unclear asset lists, gateways placed after the fact, mounting spots picked on the day, and no agreed test for what counts as commissioned. Rolling out 100 sensors in a single working week is realistic only when the site survey, parts staging, and acceptance criteria are finished before the first sensor leaves its box. This guide sets out a five-day method covering mounting, gateway placement, and commissioning for commercial facilities, and shows how Oxmaint maintenance software keeps assets, work orders, and inspection records tied to every sensor you install.
Wireless Vibration Sensor Deployment: 100 Sensors in a Week
Chillers, pumps, fans, and cooling tower drives can be on continuous watch within five working days when preparation, mounting, gateways, and commissioning follow one plan. Wireless removes the cabling; it does not remove the need for a method.
Why wireless changes the rollout math
Wired monitoring spends most of its schedule on construction. Wireless moves that effort into planning, mounting, and network checks, which are easier to compress but easier to skip.
| Factor | Wired monitoring | Wireless monitoring | Rollout implication |
|---|---|---|---|
| Cabling and conduit | Cable runs, trays, and conduit to every point | None to the sensor; power comes from a battery or harvester | Time goes into mounting and network, not construction |
| Disruption | Contractor access, ceiling work, and permits | Short technician visits to each machine | Plan around tenant hours and permit to work rules |
| Scaling | Every added point needs another run | Add points by mounting and joining the network | Phase the rollout by building zone |
| Signal path | Fixed and predictable | Depends on radio conditions, gateway position, and backhaul | Survey the radio environment before mounting |
| Ongoing upkeep | Cable damage and connector faults | Batteries, mounts, and gateway health | Sensor health needs its own maintenance tasks |
Week zero: the preparation that makes a week possible
A 100-sensor week is won before Monday. Rank assets first, so the crew always works on the points that matter most if time runs short.
Week zero checklist
- Walk the site with a sitemap and mark every target machine, plant room, and rooftop area.
- Confirm each asset has a unique ID and tag in the asset register, so sensors map to records on day one.
- Stage hardware in kits by area: sensors, mounts, adhesive or studs, tags, and spare batteries.
- Confirm backhaul options with IT, whether Wi-Fi, cellular, or ethernet, and obtain any approvals.
- Book permits, escorts, and access windows for plant rooms, roofs, and tenant floors.
- Confirm which machines will be running during mounting, since a baseline needs normal operation.
The five-day deployment plan
Each day has a purpose and an exit test. Do not start the next day until the previous day's sensors are reporting.
Prove the network, then mount the pilot
- Install gateways and confirm backhaul before any sensor is activated.
- Mount about ten sensors on easy Tier 1 assets nearest each gateway.
- Check signal strength, data intervals, and platform mapping end to end.
- Fix the mounting standard and photo format everyone will use.
Central plant
- Cover chillers, boilers, and primary pumps with two crews working in parallel.
- Activate sensors in order of distance from the gateway, nearest first.
- Capture a baseline on each machine under normal load.
Air handling and fan systems
- Work floor by floor or plant room by plant room to limit travel time.
- Add a second gateway where steel, concrete, or distance weakens the signal.
- Review data availability at the end of the day and correct weak links.
Rooftop, tower, and secondary systems
- Take weather and roof access rules into account and keep this day flexible.
- Protect sensors and mounts from water and direct sun where the vendor requires it.
- Mount Tier 2 assets only after Tier 1 coverage is confirmed live.
Close gaps and run acceptance
- Revisit machines missed due to access or shutdowns.
- Run the acceptance checklist on every sensor and record exceptions.
- Hand over alarm settings, asset mappings, and sensor health tasks to the maintenance team.
Mounting: where signal quality is won or lost
A sensor on a loose, painted, or thin surface reads the mount rather than the machine. Choose the method by machine criticality and by how permanent the install needs to be.
| Method | Signal quality | Install effort | Best use | Watch for |
|---|---|---|---|---|
| Stud mount | Best frequency response | Highest; drilling and tapping the housing | Critical machines with permanent monitoring | Drilling approval and correct torque |
| Adhesive or epoxy | Very good when the surface is prepared | Moderate; no drilling, but cure time applies | Most Tier 1 and Tier 2 assets | Paint, oil, and dust on the surface |
| Magnet mount | Lowest of the three | Lowest; fast and removable | Pilots, temporary checks, clean flat ferrous surfaces | Loosening over time; place the magnet gently, never let it slap down |
Placement rules that hold across vendors
- Mount as close to the bearing load zone as the housing allows, on a rigid, solid path to the bearing.
- Avoid fan shrouds, thin covers, guards, and flexible panels that add their own resonance.
- Prepare the surface: remove loose paint and grease, and use the flat area the vendor specifies.
- Keep orientation uniform across the site, including axis marking and cable position, so trends compare cleanly.
- Follow vendor torque values and thread-locking guidance, and photograph every mounted sensor.
Gateways and network: the part that decides data quality
Sensors only help when their readings arrive. Treat the path from sensor to platform as four links, and know what breaks each one.
Gateway planning rules
- Install and verify the gateway before activating sensors, then power sensors on starting with those nearest to it.
- Gateway capacity varies by product, with vendor guides ranging from tens of sensors up to very large networks. Use your vendor's figure and leave margin.
- Plan gateways by area and line of sight, not just by total sensor count.
- Test signal at the planned mounting position before committing to a final gateway location.
- Give each gateway reliable power and record its location and network details in the asset register.
The crew math behind 100 sensors in a week
The target is simple arithmetic once Day 1 and Day 5 are reserved for network proof and acceptance. These are planning assumptions, not guarantees.
- That leaves roughly 35 to 40 minutes per point across a shift, including travel, surface prep, mounting, tagging, and photos.
- Machines with difficult access, hot surfaces, or tenant restrictions will take longer, so mix easy and hard points each day.
- Stage parts by area so crews never wait for adhesive, batteries, or tags.
Commissioning: what "installed" must mean
A sensor on a machine is not a working sensor. Use one acceptance test for every point, and do not count a sensor until it passes.
Common rollout failures and what prevents them
Most failed deployments repeat the same handful of mistakes. Each one has a fix that costs little if done in week zero.
- Gateways placed after sensors are mountedSurvey radio conditions and install gateways on Day 1.
- Inconsistent asset names across the platform and recordsAgree one asset ID format and map sensors to it during mounting.
- Magnet mounts used everywhere for speedUse stud or adhesive on critical assets and keep magnets for pilots.
- Alarms left at factory defaultsTune thresholds against the baseline within the first weeks.
- Alerts that nobody ownsDefine who reviews alerts and how they become inspection or work orders.
- No upkeep plan for batteries, mounts, or gatewaysCreate recurring sensor health tasks before the crew leaves.
Plan the rollout around your own asset list
Bring your plant rooms, rooftops, and critical machines into one asset hierarchy before the sensors arrive, so every point lands on a record with history.
From first alert to closed work order
The sensor platform detects change. The maintenance system decides who acts, with what parts, and records what was found.
After the week: the first 30 days
Commissioning ends the install. Stabilizing the program takes a few more weeks of attention.
Week 2
- Review data availability for every sensor and fix weak signals.
- Replace magnet mounts on critical assets where needed.
- Correct asset mapping errors found by the maintenance team.
Weeks 3 and 4
- Tune alarm levels using real operating variation.
- Review each alert and note whether inspection confirmed a fault.
- Start the recurring sensor health tasks.
Month 2 onward
- Plan the next wave of assets from Tier 2 and Tier 3.
- Link confirmed findings to repair records and spare parts usage.
- Adjust route-based inspections where continuous data already covers the point.
KPIs that show the rollout is working
Track deployment quality first, then program results. Both matter, and neither replaces the other.
Commissioned versus planned
Sensors that passed acceptance divided by sensors in the planData availability
Readings received divided by readings expected, per sensor and per gatewayTime to commission
Average crew minutes per point, from arrival to passed acceptanceAlerts confirmed by inspection
Alerts where a technician found a real fault divided by total alertsAlert-to-work-order time
Hours from alert to a raised and assigned work orderSensor health task compliance
Battery, mount, and gateway checks completed on time divided by checks dueWireless vibration sensor deployment FAQs
How many gateways do 100 sensors need?
It depends on the vendor's per-gateway limit and on building layout, because steel and concrete affect range. Plan by area and keep spare capacity.
Can a small crew really do this in five days?
Yes, if surveys, kits, permits, and asset IDs are ready beforehand. Without that preparation, the time disappears into searching and rework. Book a demo to plan your own schedule.
Which mounting method should I choose?
Stud mounting gives the best response, adhesive is a practical default, and magnets suit pilots and temporary checks. Follow your sensor vendor's guidance.
When should I set alarm thresholds?
Enter starting levels at commissioning, then tune them against the baseline and real operating variation over the following weeks.
How does Oxmaint fit into a sensor program?
It manages the assets, work orders, inspections, and spares around the sensors, plus recurring sensor health tasks. Create an account to set up your asset hierarchy.
Turn sensor alerts into planned maintenance
Give your facility team one place for assets, inspections, work orders, and sensor upkeep, so every alert has an owner and every repair leaves a record.
