Most IIoT projects take 6 to 12 months. Requirements gathering. Proof of concept. Integration planning. Pilot. Rollout. By the time you see live data, you have spent six figures and half a year.
We do it in 7 days. Not because we cut corners — because we scoped the problem correctly. Machine monitoring does not require ERP integration, PLC programming, or a committee. It requires sensors, an edge computer, and a cloud connection. That is a one-week job, and here is exactly how it works.
Why Most IIoT Projects Take 6-12 Months
The typical IIoT deployment timeline looks like this: 2 months of vendor evaluation, 1 month of contract negotiation, 2 months of requirements gathering, 1 month of pilot planning, 2 months of pilot execution, 1 month of evaluation, 2 months of rollout.
This makes sense for a $500,000 SCADA system or a full MES implementation. It makes zero sense for machine monitoring. The reason it still happens is that most IIoT vendors sell platforms, not solutions. They sell you the tools and leave you to figure out the implementation.
Our approach is different: we ship preconfigured hardware, we handle the cloud setup, and we use cellular connectivity that bypasses your IT network entirely. The result is a 7-day timeline from purchase order to live dashboard.
The 7-Day Timeline
Days 1-2: Hardware Ships
When you sign up, we configure your hardware kit before it ships. The edge compute box is pre-loaded with your site configuration: your company name, your machine names, your alert thresholds (starting with ISO 10816 defaults). The cellular gateway has its SIM activated and tested. The vibration sensors are paired to the gateway.
This is not generic hardware with a setup wizard. By the time the box arrives at your dock, it already knows who you are and what machines it is monitoring.
Day 3: On-Site Installation (4 Hours)
Installation is a 4-hour job for a single technician. Here is what happens:
- Mount sensors — Magnetic mount on the spindle housing of each machine. No drilling, no tapping, no permanent modification. Takes 5 minutes per machine.
- Place edge compute box — The small fanless computer sits on a shelf or mounts to a wall near the machines. Needs one 110V outlet. That is it.
- Power on the cellular gateway — The gateway creates its own WiFi network for the sensors and connects to the internet via cellular. No connection to your company network required.
- Verify data flow — Within 15 minutes of power-on, the sensors report to the edge computer, the edge computer publishes to the cloud broker, and data appears in the dashboard. We verify this live on-site before the technician leaves.
No IT involvement. No firewall rules. No VPN configuration. The cellular gateway creates a completely independent network path from your sensors to the cloud. This is deliberate: we do not touch your production network because we do not need to.
Days 4-5: Data Flows, Baselines Established
For the first 48 hours, the system collects data in baseline mode. It learns the normal vibration profile of each machine: what the spindle vibration looks like at different speeds, what the idle baseline is, what the typical cutting signature looks like.
During this period, you can already see live data in your dashboard. Vibration readings update in near real-time. Machine utilization is calculated from spindle on/off state. OEE starts accumulating as soon as you mark the first production run.
Our system runs ISO 10816 thresholds from minute one, so critical alerts (Zone C and D) will fire immediately if a machine is in bad shape. But the fine-tuned alerts — the ones that catch gradual degradation — need baseline data to calibrate.
Days 6-7: Alert Thresholds Tuned, Dashboard Live
On day 6, we review the baseline data with you (remote video call, 30 minutes). We look at each machine's vibration profile, confirm the baseline is representative, and set custom warning thresholds based on your actual equipment — not just ISO defaults.
By day 7, your system is fully operational:
- Real-time dashboard with OEE, vibration, and utilization
- Alert thresholds tuned to your specific machines
- Notification routing configured (email, SMS, or both)
- Historical trend data from the past 5 days already visible
- Shift patterns configured to match your schedule
Data flowing in 7 days or your money back. That is the guarantee.
What Ships in the Kit
| Component | Purpose | Details |
|---|
| Edge Compute Box | Local data processing | Fanless x86 mini-PC, pre-configured with data pipeline software. Runs on 110V, no moving parts, industrial temp rated. |
| Vibration Sensors | Machine health monitoring | One per machine. Wireless (LoRaWAN), battery-powered (5+ year life), magnetic mount. Tri-axis accelerometer, 10-1000 Hz. |
| LoRaWAN Gateway | Sensor data collection | Collects data from all vibration sensors. Industrial rated, wall mountable. Range covers a typical shop floor. |
| Cellular Gateway | Internet connectivity | 5G/LTE cellular router. Creates a dedicated WiFi network for the edge compute box. No connection to your IT network. |
| Ethernet Switch | Local wired backbone | 8-port industrial switch connects edge compute, gateway, and LoRaWAN gateway via Cat6. |
| Cabling Kit | Wiring | Pre-cut Cat6 cables, power strips, mounting hardware, cable management. Everything you need, nothing you do not. |
See the full hardware spec
Our device library has detailed specifications for every component in the monitoring kit, including datasheets and mounting guides.
Browse the device library →The Technology Stack (Simplified)
You do not need to understand the technology stack to use the system. But if you are the kind of shop owner who wants to know how things work, here is the chain:
- Sensors read vibration acceleration on each machine and transmit wirelessly via LoRaWAN to the gateway.
- Gateway receives sensor data and forwards it to the edge compute box over the local network.
- Edge compute processes the raw data locally: calculates RMS velocity, applies ISO 10816 classification, packages the data in Sparkplug B format, and publishes it to the cloud MQTT broker.
- Cloud broker receives the data and routes it to the time-series database (for history) and the web application (for live display).
- Your dashboard displays real-time machine status, historical trends, OEE calculations, alerts, and AI-generated recommendations.
The edge compute box is the key differentiator. It processes data locally so that only meaningful, structured data leaves your facility. Raw accelerometer readings stay local. What goes to the cloud is classified, contextualized, and ready to display.
Why Sparkplug B Matters
We use Sparkplug B as our data protocol because it was built for exactly this use case. When a sensor comes online, it announces itself with a “birth certificate” that describes what it measures and how to interpret its data. When it disconnects, the broker announces a “death certificate” so you know immediately that a sensor dropped off.
This means auto-discovery works out of the box. Plug in a new sensor, and it appears in your dashboard within minutes. No manual configuration, no database entries, no ticket to IT. The protocol handles it.
What Happens After Day 7
Day 7 is when the system goes live. It is not when the value stops growing.
- 24 hours of data — AI-generated recommendations start appearing. The system identifies machines running below their potential and suggests specific improvements.
- 1 week of data — Trend analysis becomes meaningful. You can see which machines have rising vibration, which are consistently underutilized, and where your biggest OEE gaps are.
- 1 month of data — Baseline comparison is solid. Anomaly detection is calibrated. The system knows what “normal” looks like for each machine and can flag deviations with confidence.
- 3 months of data — Predictive patterns emerge. Seasonal trends, tooling wear curves, shift-to-shift performance differences. This is where the data starts telling you things you did not know to ask about.
Get your custom deployment spec
Tell us about your machines, your shop layout, and your goals. Our downtime calculator shows you exactly what unplanned downtime costs your facility — including sensor placement, network topology, and alert configuration.
See what downtime is costing you →What It Costs
Transparency matters. Here is the pricing:
- $2,499 one-time Machine Health Assessment — covers site survey, hardware configuration, installation, and training
- $119 per machine per month — includes sensors, cloud infrastructure, dashboard, alerts, and AI recommendations
- 5 machines: $599/mo — the most common starting point for job shops
- 15 machines: $1,799/mo — same flat rate for larger operations
12-month agreement with month-6 exit ramp. No hidden fees. No per-user charges. The 7-day guarantee means if data is not flowing by day 7, we refund the setup fee. The 90-day ROI guarantee means if the monitoring does not pay for itself in the first quarter, we refund up to 3 months of subscription fees.
The Bottom Line
Seven days. That is the distance between not knowing what your machines are doing and having a live dashboard that tells you everything. No IT project. No committee. No 6-month pilot that produces a report recommending a longer pilot.
Pre-configured hardware. Cellular connectivity. Live data in a week. That is the entire pitch.