Data acquisition
S7 protocol (S7-1200/1500/300/400), Modbus RTU/TCP, OPC UA/DA, MQTT; reconnect on disconnect, backfill, timestamp alignment, and anomaly flagging.
Capability 04 · HMI/SCADA Application Development
The PLC finishes the motions, but the data stays locked in the cabinet
The PLC finishes the motions, but the data stays locked in the cabinet
The HMI/SCADA application should keep a record of "what happened"
In many plants the situation is this: the equipment runs fine, but how much each shift produced, how much was scrapped, why it stopped, and when a parameter drifted — it's all in the shift leader's handwritten notes. The value of an HMI/SCADA application isn't "having a screen" — it's making the data queryable, traceable, and computable.
¥50,000+ (≈US$7,000+)By feature list and I/O point count
8–16 weeksTypical timeline, delivered in two phases
Three technology pathsWPF / Qt / configuration software
Includes opsDeployment scripts, backup, remote upgrade
Choose the path first, then talk price. The same "add an HMI/SCADA application" request has very different costs and fits across three paths: configuration software is fast but limited by the vendor's capabilities; WPF/Qt is flexible but a larger development effort; a hybrid (configuration for the screens, custom code for data and reports) is often the best value. We'll tell you which path fits — not just push custom development.
How to choose among the three paths
| Path | Technology | When it fits |
|---|---|---|
| Configuration software | WinCC / KingView / ForceControl / Ignition | Fast screens and alarms with complete standard functions; limited for complex reports and external integration |
| WPF / Qt custom | .NET 6+ / C++ Qt | Full control over UI and business logic; fits traceability, algorithms, multi-system integration; larger development effort |
| Hybrid | Configuration for screens + services for data | A balance of timeline and cost; reports and interfaces supplemented with custom code |
Delivery scope
Screens & operations
Process screens, equipment status, parameter setting with read-back verification, role-based access, and an audit log (who changed what, when).
Reports
Shift reports, daily/monthly reports, OEE (availability / performance / quality), defect classification, energy consumption; export to Excel / PDF, with scheduled delivery.
Traceability
Look up by batch / serial number: process parameters, inspection data, operator, machine state, alarm history.
Alarms & notifications
Severity-graded alarms, dedup and suppression, WeChat / email / SMS push, and a closed acknowledge-and-handle loop.
Deployment & operations
Industrial-PC deployment package, one-click backup and restore, remote upgrade scripts, offline buffering and resync; source code and deployment docs delivered.
Two-phase delivery: usable first, then more features
- Phase 1 (4–8 weeks): acquisition + screens + basic reports. Get the data right and the interface usable first, then run a two-week trial. By the end you can answer "how much did this shift produce, and how long was it down."
- Phase 2 (4–8 weeks): deeper reports + traceability + external integration. OEE, defect analysis, MES/ERP interfaces, dashboards. Priorities are adjusted based on real Phase 1 usage — many requirements only turn out to be non-priorities once live.
- Acceptance criteria go into the contract: the acquisition point list, refresh cycle, report definitions, concurrency, and data retention are tested item by item. No "looks good" clauses that can't actually be verified.
About source code: custom projects deliver complete source code and deployment docs by default — no encryption, no license lock-in. You can maintain it yourself or hand it to a third party. We renew on delivery quality, not by locking you in.
Frequently asked questions
Can you do just the reports and keep our existing screens?
Yes — this is a very common type of engagement: the site already has configuration screens, but the data was never stored and reports are done by hand. We pull data from the existing PLC or configuration software's historian, build the data layer and reports, and leave the existing screens untouched.
Old equipment has no Ethernet port — only serial or no comms at all. Can you do it?
Serial ports can be read directly or with a converter; for legacy equipment with no comms at all, we capture signals with I/O acquisition modules or added sensors. For these we first deliver an "Acquisition Feasibility Table" showing how each point is captured, at what cost and accuracy.
Where is the data stored? Do we need the cloud?
Local by default: industrial PC + database (SQLite / SQL Server / PostgreSQL), running even when the network is down. The cloud comes in only when you need multi-site roll-up or a mobile dashboard — and even then it only does aggregated display, while control and production data stays local.
Clarifying requirements matters more than a quote
We have an "HMI/SCADA Requirements Self-Check" covering six dimensions to help you pin down what you need: acquisition points, report definitions, traceability granularity, permissions, deployment environment, and acceptance criteria. Just ask.
+86 133 1955 1131