Vietnamese teams commissioning a sensor acquisition gateway can separate costs into acquisition, protocol mapping, offline buffering, platform integration, deployment verification and external resources. Link each item to inputs, deliverables and pass criteria before comparing totals. Device counts or protocol names alone do not define the full workload.
Beijing Winge Technology Co., Ltd., operating as Winge, provides embedded, communications and device integration development services. This is a method for requesting project quotes; scope, source code rights, prices and schedules are agreed in project documents.
Separate sampling, reporting and storage
Provide device models, firmware, quantities, channels or points per device, signal units, wiring and protocol documents. Specify sensor sampling, gateway polling and reporting intervals and platform retention rules separately, including batching, aggregation and timestamp sources.
For an initial buffer estimate, multiply stored records per second by stored bytes per record and maximum offline seconds, then allow for indexes, logs, retries and a safety margin. Use actual serialized record sizes. This estimate does not validate usable capacity, write endurance or replay performance.
Six work packages and cost inputs
This table defines quotation and acceptance scope, rather than fixed prices. State whether a charge is included elsewhere to avoid counting it twice.
| Work package | Cost inputs | Possible deliverables and acceptance |
|---|---|---|
| Acquisition and drivers | Device and channel counts, interfaces, intervals, time source and invalid-value rules | Drivers, field dictionary and sampling logs; compare raw and engineering values, units and time |
| Protocols and mapping | Protocol revision, point list, byte order, read/write rights, frames and error rules | Conversion software and mapping configuration; test normal fields, timeouts and error responses |
| Offline buffering | Record rate, record size, offline duration, capacity and full-buffer policy | Queue and configuration; reconcile replay, duplicates, loss and power recovery by sequence number |
| Platform integration | Platform version, topics or API, authentication, data model and test account | Integration module and configuration; trace device readings to records actually stored by the platform |
| Deployment and verification | Gateway count, operating system, network, permissions, site window and test cases | Deployment or build instructions, version inventory, fault tests and recovery records |
| External resources and maintenance | Samples, hardware, cloud resources, SIMs, licenses, site support and maintenance term | Identify provider, quantity, duration and cost responsibility; list new requirements as changes |
Accept the record chain and assess changes
An initial phase can cover an input review, interface and data-flow diagrams, cost boundaries, a capacity estimate and draft acceptance cases. Implementation can then deliver the agreed firmware or services, configuration, interface documentation, build and deployment instructions, and test records.
Use one device and software revision to connect raw readings, gateway records, transmitted messages and stored platform results. Test device disconnection, network loss, authentication failure, a full buffer and power recovery. Agree test duration, tolerances and recovery criteria first. Successful message transmission does not establish platform persistence or measurement accuracy.
When adding devices, increasing sampling rates or changing protocols or platforms, identify reusable work and new bottlenecks before pricing adaptation, capacity, deployment and regression tests separately. Control writes, remote upgrades and site safety functions need their own permissions and cases; read-only acquisition quotes do not include them by default.
Handover and deployment for Vietnam projects
Before a Vietnam project starts, agree Vietnamese or English interface and documentation scope, working time zone, timestamp format and units. Name site equipment and platform owners and confirm sample handover, remote access windows and deployment location. Currency, taxes, logistics, applicable compliance work and site support require project-specific checks; the target country does not establish fixed rules or a local team.
Common questions
Can sensor counts alone support a fixed total?
No. Models, channels, intervals, protocols, buffer targets, platform and deployment inputs are also needed. If information is incomplete, input review and a critical-path prototype can be quoted first.
What remains to be accepted after MQTT reporting works?
Check platform fields and actual stored results, then test outages, duplicates, a full buffer and power recovery. Protocol transmission and business-data completeness are separate checks.
Does doubling the sampling rate double the cost?
It cannot be inferred proportionally. Check device-bus, processing, storage and network loads and whether reports are aggregated. Price reusable development, expansion and new testing separately.
Related services and inquiries
Multi-sensor acquisition terminal development (Chinese) covers acquisition inputs and channel checks; Modbus-to-MQTT gateway development (Chinese) covers device-to-platform mapping.
Offline buffering and replay development (Chinese) covers capacity and fault boundaries; the company profile (Chinese) identifies the company and project delivery model.
Use the project inquiry form (Chinese) to provide device and point lists, intervals, protocol documents, buffer targets and platform information, so initial scope and acceptance methods can be agreed.
Online
Phone
WeChat
Top