Quick Start Guide: From Sensor Installation to First Leak Alert

This guide walks through the practical steps of deploying a pipeline leak detection system — from mounting your first pressure sensor to receiving your first automated alert. Whether you're monitoring a district heating network or an oil pipeline, the workflow follows the same pattern.

Prerequisites

Before starting, ensure you have:

• [ ] Platform account with active subscription (Detect tier or higher)
• [ ] At least 2 pressure sensors per pipeline section
• [ ] LoRaWAN gateway within range of sensor locations
• [ ] Network server configured (ChirpStack or similar)
• [ ] Pipeline data: length, diameter, wall thickness, fluid type

Step 1: Register Your Pipeline

In the platform dashboard, navigate to Pipelines → Add Pipeline and enter:

1. Pipeline name and identifier
2. Physical parameters: length (m), inner diameter (mm), wall thickness (mm)
3. Material: steel, HDPE, cast iron, copper
4. Fluid type: water, oil, gas, heating fluid
5. Operating conditions: nominal pressure (bar), temperature (°C)

The system automatically calculates the expected wave speed using the Korteweg equation. This value calibrates the NPW detection algorithm.

Step 2: Define Pipeline Geometry

For accurate leak localization, the system needs to know where your sensors are relative to pipeline features:

1. Go to Pipeline → Map Editor
2. Draw the pipeline route on the map (click nodes along the path)
3. Mark elevation changes — these affect static pressure readings
4. Note branches, tees, and dead ends (wave reflections)

Step 3: Register and Install Sensors

Hardware Installation

Mount pressure sensors at predetermined locations along the pipeline:

• Mounting: On existing tapping points, drain valves, or dedicated connections
• Orientation: Transmitter above the tapping point (prevents air traps)
• Protection: Weatherproof enclosure rated for outdoor conditions
• Power: Battery (5-10 year life) or solar for remote locations

Platform Registration

For each sensor:

1. Navigate to Sensors → Add Sensor
2. Enter the DevEUI (printed on sensor label or commissioning sheet)
3. Select sensor type (pressure, temperature, flow)
4. Set pipeline assignment and position (distance from pipeline start in meters)
5. Configure alert threshold (recommended: 0.5 bar for heating, 1.0 bar for oil)

Step 4: Verify Data Flow

Once sensors are powered on and registered:

1. Check Dashboard → Real-time view for incoming readings
2. Verify each sensor shows reasonable values (compare with manual gauge if available)
3. Confirm update interval matches configuration (default: 10 seconds)
4. Look for any sensors showing "offline" status — troubleshoot radio connectivity

Troubleshooting Connectivity

If a sensor isn't reporting:

• Verify LoRaWAN gateway is online and within range
• Check DevEUI matches between physical device and platform registration
• Confirm the device activation method (OTAA vs ABP) matches network server config
• Test with sensor closer to gateway to rule out range issues

Step 5: Configure Detection Parameters

Navigate to Pipeline → Detection Settings:

1. Wave speed: Auto-calculated from pipeline parameters; override only if measured in field
2. Detection sensitivity: Start at "Normal" — reduce to "High" only after initial tuning period
3. Minimum event duration: 2 seconds (filters out transient noise)
4. Confirmation window: 30 seconds (time to wait for wave arrival at second sensor)

Recommended Initial Settings

Step 6: Set Up Alerts

Configure notification channels in Settings → Alerts:

1. Dashboard: Always active — shows real-time events on map
2. Email: Add on-call engineer addresses
3. Telegram: Connect bot for instant mobile notifications
4. SMS: Configure for critical-priority events only (cost per message)

Alert Hierarchy

• Critical (confirmed leak): All channels immediately
• Warning (suspected anomaly): Dashboard + Telegram
• Info (sensor offline, battery low): Email daily digest

Step 7: Run a Detection Test

Before relying on the system, validate it detects a controlled event:

1. Coordinate with operations team
2. Open a drain valve briefly (2-3 seconds) at a known location
3. Observe: system should detect the pressure drop within 5-15 seconds
4. Verify: localization should indicate position near the drain valve (±200 m)
5. Document: save the test event for baseline comparison

If the system doesn't detect the test:

• Increase sensitivity
• Check sensor sampling rate (must be ≥10 Hz for NPW)
• Verify wave speed calibration
• Ensure drain valve creates sufficient pressure change (>0.2 bar)

Step 8: Go Live

Once validation passes:

1. Set system to Production mode (enables external notifications)
2. Brief operations team on alert workflow
3. Define response procedures for each alert priority
4. Schedule weekly review of events for first month (tune thresholds)

Ongoing Operations

• Monthly: Review detection log, adjust thresholds if false alarm rate too high/low
• Quarterly: Recalibrate wave speed if temperature changes significantly
• Annually: Sensor battery check, firmware updates, system health audit

*Need help with deployment planning? Our support team provides remote assistance for sensor placement optimization and system commissioning.*