|
2 | 2 | Activity, |
3 | 3 | BarChart3, |
4 | 4 | Boxes, |
5 | | - Building2, |
6 | 5 | CheckCircle2, |
7 | 6 | CloudCog, |
8 | 7 | Cpu, |
@@ -196,34 +195,82 @@ export const homepageContent = { |
196 | 195 | ], |
197 | 196 | }, |
198 | 197 | solutions: { |
199 | | - eyebrow: "Solutions", |
200 | | - title: "Show the suite by business scenario, not only by technology", |
| 198 | + eyebrow: "Industry cases", |
| 199 | + title: "Real IoT industry cases", |
201 | 200 | subtitle: |
202 | | - "The homepage now speaks to the buying contexts seen on industrial IoT, infrastructure, and enterprise SaaS websites.", |
| 201 | + "Reference cases from connected vehicles, renewable energy, robot fleets, and factory edge collection show how Halia, FluxMQ, and FCP fit into production systems.", |
203 | 202 | items: [ |
204 | 203 | { |
205 | | - title: "Smart manufacturing", |
| 204 | + title: "Connected vehicle data platform", |
| 205 | + caseLabel: "Large automotive group · vehicle telemetry and control", |
| 206 | + scenario: |
| 207 | + "Vehicle terminals continuously report periodic, event, and statistical data. Regional and national data centers need stable access, validation, routing, and service integration.", |
206 | 208 | description: |
207 | | - "Collect PLC and equipment data, publish events, and monitor factory-side message flows.", |
208 | | - icon: Factory, |
| 209 | + "FluxMQ acts as the vehicle access gateway, carrying GB/T32960, JT/T808, MQTT, HTTP, and private TCP/UDP traffic into TSP services, data platforms, and control APIs.", |
| 210 | + flow: ["T-BOX / IVI", "FluxMQ cluster", "Rule engine", "Kafka / API", "TSP services"], |
| 211 | + metrics: ["100K-class vehicle concurrency", "Million-level message architecture", "Offline message + API command delivery"], |
| 212 | + outcomes: [ |
| 213 | + "Unified vehicle admission and data forwarding", |
| 214 | + "Low-latency two-way communication for app control", |
| 215 | + "Safer integration with certification, ACL, and service APIs", |
| 216 | + ], |
| 217 | + products: ["FluxMQ", "FCP"], |
| 218 | + visual: "/solution-animations/vehicle-data.svg", |
| 219 | + icon: Gauge, |
209 | 220 | }, |
210 | 221 | { |
211 | | - title: "Energy and utilities", |
| 222 | + title: "Renewable energy operations", |
| 223 | + caseLabel: "Distributed photovoltaic and energy assets", |
| 224 | + scenario: |
| 225 | + "Remote stations are widely distributed, operating conditions are harsh, and generation, device status, alarms, and forecasts need to be visible without increasing field work.", |
212 | 226 | description: |
213 | | - "Connect remote stations, keep device telemetry flowing, and centralize cluster operations.", |
| 227 | + "FluxMQ uses clustered access, TLS authentication, per-device topics, and Kafka bridging to keep telemetry flowing into monitoring, diagnosis, and forecasting systems.", |
| 228 | + flow: ["PV devices", "TLS access", "FluxMQ cluster", "Kafka bridge", "Monitoring / forecast"], |
| 229 | + metrics: ["2M+ connected devices", "7-node production cluster", "Per-device topic model"], |
| 230 | + outcomes: [ |
| 231 | + "Remote monitoring and diagnosis across stations", |
| 232 | + "High-throughput persistence without data backlog", |
| 233 | + "Lower on-site inspection and operating cost", |
| 234 | + ], |
| 235 | + products: ["FluxMQ", "FCP"], |
| 236 | + visual: "/solution-animations/energy-station.svg", |
214 | 237 | icon: Zap, |
215 | 238 | }, |
216 | 239 | { |
217 | | - title: "Connected equipment", |
| 240 | + title: "Robot and smart equipment fleets", |
| 241 | + caseLabel: "Garden robots and export-oriented equipment", |
| 242 | + scenario: |
| 243 | + "Robot products combine sensors, cameras, voice, text, and private protocols. Edge rules and cloud analytics must work together across markets and networks.", |
218 | 244 | description: |
219 | | - "Bridge device fleets into applications with MQTT, HTTP, Kafka, and time-series storage.", |
220 | | - icon: Gauge, |
| 245 | + "Halia normalizes edge inputs, NodeMQ handles local messaging, and FluxMQ carries fleet data to Kafka, big data, and business systems for real-time and offline analysis.", |
| 246 | + flow: ["Sensors / camera", "Halia", "NodeMQ", "FluxMQ", "Kafka / big data"], |
| 247 | + metrics: ["Edge stream processing", "Private protocol access", "Real-time + offline data paths"], |
| 248 | + outcomes: [ |
| 249 | + "Clear separation between edge collection and cloud services", |
| 250 | + "Flexible data rules for robot scenarios", |
| 251 | + "A reusable cloud-edge pattern for smart hardware fleets", |
| 252 | + ], |
| 253 | + products: ["Halia", "NodeMQ", "FluxMQ"], |
| 254 | + visual: "/solution-animations/robot-fleet.svg", |
| 255 | + icon: Cpu, |
221 | 256 | }, |
222 | 257 | { |
223 | | - title: "Multi-tenant platforms", |
| 258 | + title: "Digital factory edge collection", |
| 259 | + caseLabel: "Industrial equipment, PLC, CNC, and SCADA integration", |
| 260 | + scenario: |
| 261 | + "Factory systems need to collect equipment data, filter invalid payloads, transform point models, and deliver clean streams to platforms, storage, and applications.", |
224 | 262 | description: |
225 | | - "Use projects, applications, licenses, proxy access, and audit trails for customer isolation.", |
226 | | - icon: Building2, |
| 263 | + "Halia connects industrial protocols and runs edge rules, FluxMQ delivers MQTT data streams, and FCP keeps clusters, access, alerts, and audit trails manageable.", |
| 264 | + flow: ["PLC / CNC", "Halia rules", "FluxMQ", "FCP", "SCADA / analytics"], |
| 265 | + metrics: ["Modbus / OPC UA / IEC104", "Edge filtering and calculation", "MQTT / HTTP / Kafka delivery"], |
| 266 | + outcomes: [ |
| 267 | + "Reduced cloud bandwidth and storage pressure", |
| 268 | + "Faster protocol onboarding across sites", |
| 269 | + "Operational visibility for rules, connections, and alarms", |
| 270 | + ], |
| 271 | + products: ["Halia", "FluxMQ", "FCP"], |
| 272 | + visual: "/solution-animations/factory-edge.svg", |
| 273 | + icon: Factory, |
227 | 274 | }, |
228 | 275 | ], |
229 | 276 | }, |
@@ -401,30 +448,82 @@ export const homepageContent = { |
401 | 448 | ], |
402 | 449 | }, |
403 | 450 | solutions: { |
404 | | - eyebrow: "解决方案", |
405 | | - title: "用业务场景讲清产品价值,而不只展示技术点", |
| 451 | + eyebrow: "行业案例", |
| 452 | + title: "真实物联网行业案例", |
406 | 453 | subtitle: |
407 | | - "新版首页参考工业物联网、基础设施与企业 SaaS 官网的表达方式,把产品放进真实采购与落地语境。", |
| 454 | + "结合车联网、新能源、智能机器人与数字化工厂案例,把 Halia、FluxMQ、FCP 放进真实的接入链路、运维模型和业务结果里。", |
408 | 455 | items: [ |
409 | 456 | { |
410 | | - title: "智能制造", |
411 | | - description: "采集 PLC 与设备数据,发布事件,并监控工厂侧消息链路。", |
412 | | - icon: Factory, |
| 457 | + title: "智能网联汽车数据平台", |
| 458 | + caseLabel: "华中大型车企 · 新能源数据采集与车控链路", |
| 459 | + scenario: |
| 460 | + "车端持续上报周期数据、事件数据与统计数据,平台需要同时对接企业、属地和国家数据中心,并保障车辆准入、监管和业务应用的稳定接入。", |
| 461 | + description: |
| 462 | + "FluxMQ 承担车辆接入网关,承载 GB/T32960、JT/T808、MQTT、HTTP 与私有 TCP/UDP 流量,将车端数据送入 TSP、数据平台与车控 API。", |
| 463 | + flow: ["T-BOX / 车机", "FluxMQ 集群", "规则引擎", "Kafka / API", "TSP 业务"], |
| 464 | + metrics: ["10 万级车辆并发接入", "百万级消息吞吐架构", "离线消息 + API 指令下发"], |
| 465 | + outcomes: [ |
| 466 | + "统一车辆准入、监管数据转发与业务数据分发", |
| 467 | + "支持 App 远程控车的低时延双向通信", |
| 468 | + "通过认证、ACL 与服务 API 降低系统集成风险", |
| 469 | + ], |
| 470 | + products: ["FluxMQ", "FCP"], |
| 471 | + visual: "/solution-animations/vehicle-data.svg", |
| 472 | + icon: Gauge, |
413 | 473 | }, |
414 | 474 | { |
415 | | - title: "能源与公用事业", |
416 | | - description: "接入远程站点,保持设备遥测持续流转,并集中管理集群。", |
| 475 | + title: "新能源场站远程运营", |
| 476 | + caseLabel: "分布式光伏与新能源资产监控", |
| 477 | + scenario: |
| 478 | + "新能源设备分布离散、位置偏远、环境复杂,企业需要实时掌握发电、状态、告警、诊断与预测信息,减少现场巡检压力。", |
| 479 | + description: |
| 480 | + "FluxMQ 通过集群接入、TLS 安全认证、一设备一 Topic 与 Kafka 桥接,把设备遥测稳定送入监控、诊断、预测和存储系统。", |
| 481 | + flow: ["光伏 / 逆变器", "TLS 接入", "FluxMQ 集群", "Kafka 桥接", "监控 / 预测"], |
| 482 | + metrics: ["200 万+设备连接", "7 节点生产集群", "一设备一 Topic 模型"], |
| 483 | + outcomes: [ |
| 484 | + "实现跨场站远程监控与远程诊断", |
| 485 | + "高吞吐持久化,桥接数据不积压", |
| 486 | + "降低现场运营、排障和巡检成本", |
| 487 | + ], |
| 488 | + products: ["FluxMQ", "FCP"], |
| 489 | + visual: "/solution-animations/energy-station.svg", |
417 | 490 | icon: Zap, |
418 | 491 | }, |
419 | 492 | { |
420 | | - title: "联网设备平台", |
421 | | - description: "通过 MQTT、HTTP、Kafka 与时序存储,把设备群接入业务应用。", |
422 | | - icon: Gauge, |
| 493 | + title: "智能机器人与出海设备", |
| 494 | + caseLabel: "园林机器人、智能硬件与海外业务链路", |
| 495 | + scenario: |
| 496 | + "机器人设备同时包含传感器、摄像头、语音、文本和私有协议数据,需要边缘规则、云端消息和离线分析协同工作。", |
| 497 | + description: |
| 498 | + "Halia 负责边缘输入规范化,NodeMQ 承载本地消息,FluxMQ 将设备数据送入 Kafka、大数据和业务系统,形成实时与离线并行的数据链路。", |
| 499 | + flow: ["传感器 / 摄像头", "Halia", "NodeMQ", "FluxMQ", "Kafka / 大数据"], |
| 500 | + metrics: ["边缘流式处理", "私有协议接入", "实时 + 离线数据通路"], |
| 501 | + outcomes: [ |
| 502 | + "边端采集与云端业务解耦", |
| 503 | + "按机器人场景灵活下发和调整数据规则", |
| 504 | + "形成可复用的智能硬件云边一体架构", |
| 505 | + ], |
| 506 | + products: ["Halia", "NodeMQ", "FluxMQ"], |
| 507 | + visual: "/solution-animations/robot-fleet.svg", |
| 508 | + icon: Cpu, |
423 | 509 | }, |
424 | 510 | { |
425 | | - title: "多租户 IoT 平台", |
426 | | - description: "用项目、应用、License、代理访问与审计能力实现客户隔离。", |
427 | | - icon: Building2, |
| 511 | + title: "数字化工厂边缘采集", |
| 512 | + caseLabel: "PLC、CNC、SCADA 与工业现场数据接入", |
| 513 | + scenario: |
| 514 | + "工厂需要接入多类设备协议,过滤无效数据,转换点位模型,并把干净的数据流交付给平台、存储、可视化和分析应用。", |
| 515 | + description: |
| 516 | + "Halia 接入工业协议并执行边缘规则,FluxMQ 承载 MQTT 数据流转,FCP 统一管理集群、访问、告警与审计。", |
| 517 | + flow: ["PLC / CNC", "Halia 规则", "FluxMQ", "FCP", "SCADA / 分析"], |
| 518 | + metrics: ["Modbus / OPC UA / IEC104", "边缘过滤与计算", "MQTT / HTTP / Kafka 输出"], |
| 519 | + outcomes: [ |
| 520 | + "降低云端带宽、存储和计算压力", |
| 521 | + "让多站点协议接入更快复用", |
| 522 | + "统一观察规则、连接、告警和审计事件", |
| 523 | + ], |
| 524 | + products: ["Halia", "FluxMQ", "FCP"], |
| 525 | + visual: "/solution-animations/factory-edge.svg", |
| 526 | + icon: Factory, |
428 | 527 | }, |
429 | 528 | ], |
430 | 529 | }, |
|
0 commit comments