Application Scenarios
Match the buyer’s field first. Platform capability to the site; users just use it.
Lingdian does not sell by industry buzzwords. We map to what keeps you up at night. Four field stories show up again and again in real delivery.
Match first: four fields
1. Plant under control
Lines and utilities already run; protocols and shifts are messy. You need more than a device list:
- Organize devices, dashboards, and alarms by project; duty watches trends and exceptions.
- Rules turn detect into act — e.g. low supply pressure auto-stops surplus machines.
- Cloud or on-prem by site network; same layering, no rewrite.
Less: Excel per shift, phone-only incidents. More: data in daily ops; linkage you can accept.
2. Campus ledger
Connect is only the start. Parks fight assets, care plans, consumables, and jobs that won’t finish on a phone.
Ledger · care · consumables · alarms share one control plane; type trees, warranty, attachments; mini-program scan jobs.
Less: paper ledgers and WeChat dispatch. More: operate after connect; close loops on phone.
3. OEM white-label
Makers need “online” as a repeatable pack, not a software team per customer.
Protocol plugins for own HW + children; product templates; private admin; Phase-1 4C2G can start.
Less: rewrite backends per customer. More: white-label pack; focus on hardware.
4. Integrator less on-site
Messy protocols, short windows, expensive residency. Demos don’t help if remote cannot explain.
Dual-track logs (raw + normalized); AI answers common faults with device/log context; people arrive only at critical nodes.
Less: all-night capture, living in the plant. More: short acceptance; reuse the base next site.
How industries fall onto these four
| Your field | Typical gear | Usually maps to |
|---|---|---|
| Energy / power | Meters, switchgear, storage, PV | Plant + remote clarity |
| Industrial lines | Gateways, PLCs, sensors | Plant (linkage) |
| Parks / buildings | HVAC, meters, lighting | Campus ledger |
| Device brands | Own units + children | OEM white-label |
| Agri / environment | Weather, irrigation | Plant (policy) + less residency |
| Env / warning | Gas, water, smoke | Less residency (alarm reach) |
No encyclopedia of industries. Match a story, then read features and architecture.
How one site actually runs
For “brownfield into ops” — not a generic six-step slogan:
- Connect — MQTT/Modbus/gateway/plugins; AI generate when tables are readable, else load a plugin.
- Semantics — thing-model words; align standard parameters.
- See — dashboards/SCADA + dual-track; duty sees state, triage sees raw.
- Act — alarms + rules (detect→action), not just a red badge.
- Operate — ledger/care on the same plane; MES via forward/Open API.
- Stay trustworthy — definitions hold; upgrades don’t smash access; next site reuses the base.
Each step maps to the three yardsticks: first-pass · remote clarity · data you dare use.
Deploy to your field
| Mode | When | How Lingdian holds it |
|---|---|---|
| Private | Intranet, boundary, gov/enterprise | Start 4C2G; same no-skip rules when scaling |
| Cloud / hosted | Fast go-live, unified ops | Same boundaries on cloud; cloud or on-prem per project |
Details: Architecture.
Don’t force-fit
- No devices, pure business site → not the main path.
- Only want the longest protocol list → not our pitch.
- Deep custom industry UI/flows → separate custom services.