SoilSensing Layer
- MEMS high-precision sensing
- RS485 bus / AutoID addressing
- Segmented assembly / LoRa wireless
Data Acquisition & Monitoring Cloud
The nerve center of every SoilCreate monitoring system: a self-developed acquisition gateway series and the SoilCreate Monitoring Cloud connect field sensors to dashboards, alerts and AI analytics — one continuous, fully owned data chain.
SoilCreate MONITORING CLOUD · SCDA-DG-01 · SCSE-VW01
Acquisition gateway series
Edge devices that never lose a reading
Three self-developed gateways cover wired buses, long-range wireless and vibrating-wire sensors. Data is filtered and checked at the edge, buffered locally during network loss, and pushed to the cloud the moment connectivity returns.
- ✓Edge computing + filtering
Anomalies are identified and flagged right at the front end, before upload.
- ✓Breakpoint-resume + event-triggered reporting
On-board storage rides out network loss; rapid changes trigger accelerated reporting.
- ✓Hardened for the field
Solar power sized for 7 days of overcast with 30% reserve, lightning-protected enclosures, remote OTA upgrades.
SCDA-DG-01
Wired Data Logger
RS485 bus input with AutoID auto-addressing, 4G uplink, and 16 GB on-board storage for breakpoint-resume on network loss.
SCDA-DG-01-LORA
LoRa Base Station
1 km+ transmission range with ad-hoc mesh networking and 4G/MQTT uplink — cable-free coverage for remote, dispersed sites.
SCSE-VW01
VW Acquisition Module
16 channels with intelligent frequency-sweep, compatible with vibrating-wire sensors from multiple vendors. 8-ch (SCSE-VW01-8) and 4-ch (SCSE-VW01-4) variants available.
16 GB
On-Board Storage
Store-and-forward keeps data safe through network loss.
1 km+
LoRa Range
Ad-hoc mesh networking, no cabling required.
16 ch
VW Channels / Module
Intelligent frequency-sweep, multi-vendor compatible.
IP65
Field Enclosure
Lightning protection with <10 Ω grounding, −40 to 70 °C.
Edge layer
Inside the Edge Layer: Six Function Blocks
Field-service statistics show that most edge failures trace to power, lightning protection and APN/SIM configuration — not the sensors. That is why every SoilCreate edge device is engineered around six clearly separated function blocks.
The six function blocks of a SoilCreate edge device and the power / main-control / comms relay: power management and the sensor interfaces feed the main-control SoC, which hands data to local storage and the communication module — all housed in the protective enclosure.
Main Control SoC
ARM Cortex-A / RISC-V running Linux or an RTOS, executing edge algorithms — filtering, checking and anomaly flagging before upload.
Sensor Interfaces
Vibrating-wire frequency-sweep, 4–20 mA, RS-485, CAN and SDI-12 — one box aggregates mixed sensor fleets.
Communication Module
4G/5G, NB-IoT, WiFi, LoRa — plus BeiDou short message for sites with no public network at all.
Power Management
Solar MPPT charging with lithium or lead-acid batteries, and DC-DC rails at 5/12/24 V for the sensor bus.
Local Storage
SD / eMMC buffering rides out network loss; data resumes to the cloud from the breakpoint once connectivity returns.
Protective Enclosure
IP65/IP67 housings rated −40 to 70 °C, with surge protection rated 8/20 µs · 20 kA against lightning.
Field Deployment Checklist
- 1Size the solar power with a safety factor
Panel wattage ÷ site average daily sunshine × 0.5 safety factor must exceed the device's average daily consumption — a rule calibrated on rainy-season field data. Even a 10% shortfall can mean an outage after sustained overcast.
- 2APN configured at the factory
On site, only the SIM card is swapped — eliminating the most common cause of "phantom" 4G failures: a mistyped APN.
- 3Lightning grounding under 10 Ω
Earth resistance below 10 Ω, with the lightning rod at least 3 m from the device. Substandard grounding is the leading cause of strike damage.
- 4OTA upgrades proven in the lab first
Every remote firmware rollout is validated in the lab before being pushed to cold, remote or hard-to-reach stations.
Technology
Cloud-Edge-Device, Fully Self-Developed
Five layers, one proprietary system — from MEMS sensing to neural-network safety assessment.
Acquisition Layer
- Smart gateway / VW acquisition
- Edge computing + filtering
- Breakpoint-resume / event-triggered reporting
Network Layer
- 4G/5G/NB-IoT all-carrier
- MQTT / TCP / HTTP
- LoRa ad-hoc networking
Cloud Layer
- Microservices architecture
- GIS/BIM 3D visualization
- Tiered alerts / multi-project management
AI Layer
- Neural-network safety assessment
- Kalman / sidereal-day filtering
- Machine-vision defect recognition
FULL-CHAIN PROPRIETARY IP | NO BLACK-BOX DEPENDENCE | FULL DATA SOVEREIGNTY
SoilCreate Monitoring Cloud
Six Core Capabilities, One Platform
Built on a microservices architecture, the SoilCreate Monitoring Cloud turns raw sensor streams into decisions — with full audit trails: every threshold change is version-logged and every alarm leaves a trigger record.
Real-Time Monitoring
Second-level data refresh across all measurement points, with live curves, cloud maps and period statistics.
Intelligent Tiered Early Warning
Configurable graded alert levels pushed by SMS and app, with version-logged thresholds and trigger logs for every alarm.
GIS/BIM 3D Visualization
Measurement points placed on design drawings, GIS maps and BIM models — see the structure, not just the numbers.
Multi-Project Management
Tiered role-based permissions let owner, contractor and supervisor accounts work on the same platform in parallel.
Open REST API
Standard RESTful + MQTT interfaces integrate with your existing GIS, BIM, OA and regulatory supervision platforms — no vendor lock-in.
AI Analytics Engine
Neural-network models deliver trend forecasting and decision support on top of live monitoring data.
Architecture & governance
Three Layers, Clear Permission Boundaries
The platform follows the standard three-layer IoT architecture: a device layer of sensors, an edge layer handling acquisition, protocol conversion, buffering and edge AI, and a cloud layer that splits into access (MQTT / HTTP / device shadow), data (time-series + relational + object storage), algorithm (rules + anomaly detection) and application (dashboards, mobile, government access, API) tiers.
| Module | Purpose | Permission boundary |
|---|---|---|
| Control indicators (alarm thresholds) | Graded alarm threshold configuration | Writable by owner + supervising engineer only; every change version-logged |
| Project overview / cloud map | Project info, progress, measurement points on design drawings | Readable by owner, contractor and supervision |
| Daily reports | Daily monitoring summaries | Writable by the supervising engineer |
| Data summary / comparison / period statistics | Multi-dimensional queries; contractor vs. third-party comparison flags deviations >10% in red | Readable by all parties |
| Project management (staff) | Staff categories and accounts | Writable by the owner only |
| Automation management | Device status and remote upgrades | Writable by SoilCreate O&M only |
Four Audit Trails, Traceable Reviews
Beyond the version-logged thresholds and alarm trigger records noted above, account changes leave approval records (applicant, approver, permissions before and after), and every API call leaves an audit log (caller, time, endpoint, parameters). Together these four audit trails make any post-event review traceable to a person and a timestamp.
API Access in Five Steps
Integration over standard RESTful API + MQTT follows a fixed flow: requirements → interface documentation from pre-sales → customer development → joint testing → go-live. The platform already interfaces with government regulatory platforms — meeting mandates such as Shanghai's 2024 rule that automated monitoring data be transmitted directly to the supervision platform.
AI layer
AI That Works on Engineering Data
Three production AI capabilities sit on top of the cloud platform, turning monitoring data into early, defensible safety judgments.
Neural-Network Safety Assessment
Models trained on monitoring data assess structural safety state and forecast deformation trends before thresholds are reached.
Kalman / Sidereal-Day Filtering
Advanced denoising for GNSS time series strips multipath and orbital noise to expose true millimeter-level displacement.
Machine-Vision Defect Recognition
Computer-vision models recognize surface defects such as cracking, complementing sensor data with visual evidence.
FAQ
Frequently Asked Questions
What happens to the data when the network drops?
Nothing is lost. The edge device buffers readings to local storage (16 GB on the SCDA-DG-01) and resumes the upload from the breakpoint the moment connectivity returns. If readings change rapidly during the outage, event-triggered reporting raises the sampling and reporting frequency automatically.
Can our existing GIS / BIM / OA systems pull data from the platform?
Yes — over standard RESTful API + MQTT. The onboarding flow is: state the requirement, receive the interface documentation from pre-sales, develop the integration, run joint testing, then go live. Every API call leaves an audit log recording the caller, time, endpoint and parameters.
Who is allowed to change alarm thresholds?
Only owner and supervising-engineer roles can write to the control-indicator module. Every change is version-logged with the value before, the value after, the person and the time — so a later review can always establish who changed what, and when.
Can owner, contractor and supervisor all use the platform at once?
Yes. Multi-party accounts work in parallel under tiered role-based permissions: all parties read the project overview, cloud maps and data summaries, while write access is bounded per module — staff management for the owner, daily reports for the supervising engineer, device management for SoilCreate O&M. Account changes leave approval records.
A gateway drops offline right after commissioning. What is the usual cause?
The two most common causes are an APN configuration error and an unpaid SIM — check both by logging into the controller. SoilCreate devices ship with the APN pre-configured at the factory so only the SIM is swapped on site. Severe data latency usually points to weak 4G signal; switch to a LoRa or NB-IoT backup link.
How is the field cabinet protected against lightning and power failure?
Grounding resistance is kept below 10 Ω with the lightning rod at least 3 m from the device, and the enclosure carries 8/20 µs · 20 kA surge protection. Solar systems are sized for 7 days of overcast plus a 30% reserve; on a low-voltage alarm, clean the panels and check the battery — batteries are replaced every 3 years.
Downloads & Resources
Related Cases
Related Solutions
Make an enquiry
Submit your request without leaving the page. Price negotiation stays off the public catalog.
Contact: sales@soilcreate.com · WhatsApp: +86 15356046033