FIELD CREW — by Robustel

Why Connect?

Rubi’s Smart Business Park Adventures · PARK · Season 1: How Things Connect · Episode 01. At the fictional Rovelwyn Business Park, a leaking pipe leads Rubi and the crew to test what makes an alert useful.

Maya, Leo, Morgan and Rubi stand together at Rovelwyn Business Park, with their names and roles. — Page 1 of 8 · Meet the crew

Morgan finds a leaking pipe after a dry inspection, and the crew asks when the leak began. — Page 2 of 8 · A leak between inspections

After the repair, Morgan, Maya and Rubi discuss detecting water between routine checks. — Page 3 of 8 · Looking beyond routine checks

Rubi proposes a test alert, Morgan agrees to receive it, and Maya configures Sensor 07. — Page 4 of 8 · Agreeing on a test alert

Leo wets a probe during a controlled test; an R1520LG forwards the event and a local app displays a water alert. — Page 5 of 8 · The first controlled test

The crew traces Sensor 07 to Building A’s basement and adds that location to the test alert. — Page 6 of 8 · Adding the missing location

Morgan acknowledges a second alert naming Building A’s basement, then Rubi joins him. — Page 7 of 8 · An alert Morgan can act on

Field Notes defines IoT and IIoT and outlines an alert with an event, location, responsible person and on-site check. — Page 8 of 8 · Field Notes — why connect?

Text version

Page 1 — Meet the crew

FIELD CREW
MEET THE TEAM
HOW THINGS CONNECT
Meet the crew.
Engineers. An AI partner. A better-connected site.
Maya
Solutions Engineer
Turns needs into a plan.
Leo
Field Engineer
Makes it work on site.
Morgan
Facilities Manager
Keeps the park running.
Rubi
Field AI Companion
Finds answers. Checks with you.
Meet the crew · Rovelwyn Business Park

Page 2 — A leak between inspections

FIELD CREW
01 · Why Connect?
It was dry at nine. Now it’s leaking.
But when did it start? The log can’t tell us.
INSPECTION LOG
09:00 · DRY
10:20 a.m.
Why Connect? · 01

Page 3 — Looking beyond routine checks

FIELD CREW
How Things Connect · 02/06
How do we catch a leak between checks?
Right now, we only find out when someone checks.
A sensor could detect water and alert you.
After the repair
INSPECTION LOG
09:00 · DRY 10:20 · WATER
Why Connect? · 02

Page 4 — Agreeing on a test alert

FIELD CREW
How Things Connect · 03/06
Let’s test it. Can we send you the alert?
Sure. I’ll watch for it in operations.
I’ll set up the test alert.
SENSOR SETUP
Sensor 07 Alerts to: Morgan Test 01
Why Connect? · 03

Page 5 — The first controlled test

FIELD CREW
How Things Connect · 04/06
Ready, Morgan? Here we go.
Next day · Controlled test
1 · PROBE DETECTS WATER
TEST 01
2 · R1520LG FORWARDS EVENT
TEST 01
3 · LOCAL APP SHOWS ALERT
TEST 01 · RECEIVED
Sensor 07
Water detected
Why Connect? · 04

Page 6 — Adding the missing location

FIELD CREW
How Things Connect · 05/06
Got it. But the location’s missing.
Building A, basement. Let’s add it to the alert.
Done. Leo, try again?
TEST 01
Sensor 07
Water detected
SOURCE · SENSOR REGISTER
07 → Building A · Basement
SENSOR 07 A · B
Why Connect? · 05

Page 7 — An alert Morgan can act on

FIELD CREW
How Things Connect · 06/06
Leo · radio: On it. One more drop.
Got it. Building A, basement. I’m on my way.
I’ll come with you.
TEST 02 · WATER DETECTED
Building A · Basement
Assigned to: Morgan
✓ ACKNOWLEDGED
Next: Same Plug. Same Language?

Page 8 — Field Notes — why connect?

FIELD NOTES
S1 / E01 · BONUS
FIELD CREW — by Robustel
Why connect?
IoT
Physical devices sense or act and exchange data over networks, so systems and people can use it.
IIoT
IoT applied to industrial operations, where reliability, integration and maintenance matter.
A useful alert
Detect water
Send the event
Show location + contact
Confirm & check on site
What happened? Where? Who will check?
This pilot runs locally. Cloud services are optional.
How Things Connect · Field Notes

Back to FIELD CREW