物联网平台与连接系统套件

IOTS 物联网平台

锐益 IOTS 平台：面向设备接入、生命周期管理与跨应用数据共享的统一物联网底座。

平台物联网

连接一台设备并不是难点，两台也不难。而来自多家供应商、使用不同协议、分布在不同工厂、固件版本各异的两百台设备——从这时起，它就不再是一次性项目，而是一项需要长期维护的工作。

锐益智能 IOTS 物联网平台是整套 IoT 套件赖以运行的基础。它登记设备，以设备自身支持的协议进行连接，为每台设备维护一份覆盖调试、配置、固件、健康状态直至退役全过程的档案，并将这些数据提供给上层应用。

关键不在连接本身，而在于上层应用——数字孪生、远程监控、能源、维护——读取的是同一份设备档案，而非各自另建。一次连接、处处复用，这正是套件与一堆独立工具的区别。

连接一台设备很容易，让它始终保持准确、最新且账实相符才是真正的功课。

多协议网关每台设备一份档案全生命周期，不止连接套件内共享

它是什么

The connection layer. Devices, gateways, controllers and PLCs are connected over the protocols they already use — Modbus, OPC UA, MQTT and others present on site — rather than through a driver written again for each project.
One record per device. Identity, location, model, firmware, configuration, credentials, owner and history sit in one place, not in a spreadsheet that was last edited last year.
Lifecycle, not just onboarding. Commissioning, configuration, firmware and parameter changes, health, and decommissioning are all stages of the same record.
A model the applications share. Points, units, states and events are modelled once, so the twin, the monitoring and the reporting read the same thing and mean the same thing.
A gateway for what cannot speak for itself. 设备自身无法上报时，由边缘网关桥接。到达平台的数据，已经符合平台模型。
Security handled in one place. Identity, credentials and certificates are issued and rotated centrally rather than being managed device by device.

当下的阻碍是什么

每种新设备类型都是一次新的集成开发，同样的工作要重复一遍又一遍。

协议解析、点表与数据模型按项目各写一遍。第二种设备类型的成本几乎与第一种相同。同一设备被每个需要它的应用各自接入一次。三个应用、三套集成、三处可能不一致的机会。换供应商意味着重写集成。这就是设备替换总被推迟的原因。连接代码成了没人敢碰的东西。因为它能跑，而没人说得清它为什么能跑。

设备清单存放在别处。装了什么大家心里有数，却不在任何系统中。

现场实际有什么记在一张表格里。最后更新时间是产线安装那天。固件版本、参数设置、哪个凭证发给了谁，没有任何可查询的记录。只能靠问，或靠现场去看。设备挪了位置或换了主人，记录不会跟着走。台账与现场从此各自漂移。一次审计或盘点就意味着派人去数。因为没有可对照的台账。

Connected is not the same as healthy. 连接在，数据是否真的在流动是另一回事。

没有任何标记指出某台设备已停止上报。数据可以断掉数天而无人察觉。没人关注哪些设备在上报、上报频率多高、最后一个值何时到达。没有任何地方能看到这些。网关掉线与设备掉线看起来一样。于是电话打给了错误的人。数据质量没有标记。缺失、冻结与跳变的值与正常值无法区分。

每个应用都自建一套数据管道，一个平台就这样变成了三个系统。

数字孪生接一套、监控接一套、能耗应用再接一套。各按各的方式。同一设备在每个系统里名字不同。交叉对照全靠手工。改一张点表意味着改三处。而它们迟早不同步。结果被当作一个平台售卖，却以多个系统运转。因为它本来就不是一体的。

它管理什么

五个阶段，全部写入同一条记录。设备接入并不算完成；退役之后历史仍可查，才算完成。

阶段	平台做什么
投运	登记身份、位置、型号与归属，并签发凭证
配置	设置参数与点表，记录每次下发的版本
运行	监视连接健康度与数据质量，记录状态与事件
更新	下发固件与配置变更，批次与回滚均有记录
退役	将设备停用，吊销凭证，保留其历史

平台能做什么取决于设备开放了什么。支持标准协议、能自主发布数据的设备接入很直接；不支持的设备则需要网关，可读取的内容也仅限于该设备开放的部分。平台不会凭空制造设备不产生的数据，也不会取代控制系统——它只在现场授予的权限内从控制系统读取数据。

您将获得

应用场景

这些场景的差异在于涉及多少种设备类型，以及已有多少设备资产在运行。

场景	平台通常承载
多供应商工厂	多协议、多代际的设备纳入同一份设备台账
多站点集团	统一的设备登记与描述方式，在各厂一致执行
存量改造	既有设备经网关接入，而非更换
设备制造商与 OEM	设备出厂即带身份，为调试与售后连接
公用设施与基础设施	分布式资产——泵站、变电站、管线——现场无人值守

核心能力

按功能分组。平台上的应用从这些能力读取数据，而非各自直连设备。

Capability	What it means
Multi-protocol connectivity	Connect over the industrial protocols already in use on site — Modbus, OPC UA, MQTT and others.
Edge gateway support	Bring in devices that cannot speak for themselves, through gateways at the edge.
Device registration	Register identity, model, location, owner and commissioning date for each unit.
Point and data modelling	Define points, units, states and events once, and reuse that definition everywhere.
Commissioning record	Keep what was done when a device was brought into service.
Configuration management	Apply parameters and point lists, and record every version that was applied.
Firmware management	Roll out firmware changes in batches, with what was applied and what can be rolled back recorded.
Change history	Record what changed, when, and who changed it, across configuration and firmware.
Connection health	Show which devices are reporting, how often, and when the last value arrived.
Data quality marking	Mark values as missing, frozen or out of pattern rather than passing them through as good data.
Gateway and device distinction	Tell a gateway going offline from a device going offline, so the right person is called.
Time-series storage	保存设备上报的数值，保存期限按现场留存策略设定。
Events and alerts	Raise what devices report as events, in a form the applications above can use.
Interfaces for applications above	Serve the same device record to digital twin, remote monitoring, energy and maintenance.
Write-back where authorised	Send configuration and parameters down to devices, within the access the site grants.
Identity and credentials	Issue and rotate device identity and certificates from one place.
Role-based access	Control who may register, configure, update and retire devices, and log what they did.
部署方式选择	Run in the cloud, on site, or split between the two — usually decided by where operational data may go.
Integration	Connect to maintenance, asset registers and the applications that consume the data.

工作原理

Register. The device is registered: identity, model, location, owner, commissioning date.
Connect. It is connected directly over its own protocol, or through an edge gateway where it cannot publish alone.
Model. 设备的点位、单位、状态与事件只定义一次，且遵循平台模型。
Operate. Connection health and data quality are watched, and what it reports is recorded.
Serve. The device record is served upward, so twin, monitoring, energy and maintenance all read the same one.
Maintain and retire. 配置与固件变更全程记录；退役时吊销凭证、保留历史。

部署、集成与边界

Where it runs. In the cloud, on site, or split between the two. Where operational data is allowed to be processed and stored usually decides the split.
What it feeds. Digital twin, remote monitoring, energy management and maintenance read from the same device record rather than integrating separately.
What it does not replace. It does not replace the control system or the logic running in it. It reads from those systems, within the access the site grants.
What depends on the device. 可读取的内容以设备开放的能力为限。老设备可能只提供状态和少量数值，新设备能给的更多。平台能取到什么就报什么，取不到的如实标记。
What is local. 网络分区、远程访问策略、数据驻留与留存取决于辖区和现场。配置据此设定；这些决策不由平台做出。