Industrial-grade AIoT operations products and data services

Standard product sales, plus IoT solutions around application scenes

Built on industrial gateways, expansion modules and an AIoT platform, Tongwei works along two lines — standard products and scene solution services — so equipment makers, integrators and site operators can make scattered equipment, environments and energy sites connectable, diagnosable and maintainable.

01

Standard Products

Standard Products

Without replacing your core equipment or system, we complement it with proven gateways, modules and interfaces for connectivity, acquisition, alarms and remote access.

For equipment makers, control-cabinet builders, low-voltage contractors, system integrators, solution firms and OEM partners. What we sell: SG / BEC gateways, SDS / IOC modules, industry terminals, plus platform accounts and open APIs. Path: standard selection, sample integration, volume supply — with OEM branding and hardware/software customisation (ODM) available.

No in-house development: add connectivity, acquisition, alarms and remote access in weeks

Who it is for

  • Equipment makers
  • Control-cabinet builders
  • Low-voltage contractors
  • System integrators and solution firms
  • OEM partners

Standard capability

  • Multi-protocol access and conversion
  • Offline buffering and local interlock
  • Remote access, alarms and configuration
  • SaaS / on-premise / OEM / API

What you can verify

  • After sample integration, online status and key parameters are acquired.
  • Simulate an outage and confirm local buffering, backfill and edge interlock still work.
  • Simulate a fault and confirm the alarm reaches the named endpoint or the customer's platform.
Open Standard Products

Standard Products

Without replacing your core equipment or system, we complement it with proven gateways, modules and interfaces for connectivity, acquisition, alarms and remote access.

For equipment makers, control-cabinet builders, low-voltage contractors, system integrators, solution firms and OEM partners. What we sell: SG / BEC gateways, SDS / IOC modules, industry terminals, plus platform accounts and open APIs. Path: standard selection, sample integration, volume supply — with OEM branding and hardware/software customisation (ODM) available.

  • Equipment makers
  • Control-cabinet builders
  • Low-voltage contractors
  • System integrators and solution firms
  • OEM partners

No in-house development: add connectivity, acquisition, alarms and remote access in weeks

The problem

What you are dealing with now

Shipped machines go dark, building your own gateway and platform is slow and expensive, and field protocols make it hard to plug into the customer's existing platform.

  • Once shipped, status is invisible; faults arrive as phone calls and on-site visits.
  • Building a gateway and platform in-house is costly and slow, with protocol work repeated.
  • Sites mix brands and protocols, so connecting to the customer's platform is messy.

The difficulty is the data, not the device

Why this is not solved by adding a sensor

Inside the machine you may find a PLC, VFD, proprietary board or private protocol, with point tables in drawings and engineers' heads. For product complement, the customer can take device and edge only and keep their own platform — one protocol stack and data model, not a new integration every time.

Standard capability

What this line includes by default

This is the standard scope. Protocol adaptation, custom development, OEM pages, third-party integrations and advanced reporting are scoped and quoted separately.

Multi-protocol access and conversion

Modbus, RS485/232, SNMP, MQTT, DI/DO, LoRa, 4G, plus meters and third-party APIs.

Offline buffering and local interlock

Buffer locally during outages and backfill on recovery. Critical interlocks run at the edge, not on the cloud.

Remote access, alarms and configuration

Online status, threshold and trend alarms, remote view and configuration — connectivity as a complement to existing machines.

SaaS / on-premise / OEM / API

Deliver under your brand and deployment model. Data returns through MQTT, REST or tcp-json into your own system.

How we work

The path for this line

Standard selection → sample integration → volume supply. OEM branding and ODM customisation available. For product complement, take device and edge only and keep your own platform.

Architecture

How data travels from the field into the loop

  1. 01

    Field machine / control cabinet / meters

  2. 02

    SG-series or BEC-series industrial gateway

  3. 03

    SDS / IOC expansion modules (as needed)

  4. 04

    Platform account, OEM pages or open API

  5. 05

    Customer's own system, or Tongwei Cloud / app

How to verify

What you can check yourself during the pilot

We do not substitute percentage promises for acceptance. Each item below can be checked by you during the PoC, and used to decide whether to widen scope.

  • After sample integration, online status and key parameters are acquired.
  • Simulate an outage and confirm local buffering, backfill and edge interlock still work.
  • Simulate a fault and confirm the alarm reaches the named endpoint or the customer's platform.
  • Check that the agreed OEM pages or API fields are available.

Scope limits for this solution

We do not replace core controllers or field safety systems. Standard products: small batches are in stock; larger quantities are scheduled with you. White-label supply: sample in 10 days, small batch in 20–30 days. Connectivity is assessed from the equipment list, protocol and point table. Scope and lead time for custom development are confirmed per project.

FAQ

What customers ask most during evaluation

Our machines use a proprietary protocol — can you still complement them?

Usually yes, but it must be assessed first. Provide the model, comms interface and protocol document or point table. If the protocol is undocumented, key states can often be obtained via DI/DO, analog inputs or serial traffic analysis. Protocol adaptation is scoped and quoted separately.

Will this replace our controller or our platform?

No. Standard products do not replace your core controller or field safety systems. You can take device and edge only and keep your own platform, or use a Tongwei account, OEM branding or APIs to feed your existing system.

What if no standard product is a good fit?

It can be adjusted for the project. When no standard model fits, Tongwei uses its hardware and software engineering to change the interfaces and companion software — typically to follow a change in function, or to bring cost into an acceptable range. Which interfaces change, and how far, is scoped and scheduled after assessment.

Can the platform be delivered under our brand?

Yes. OEM branding covers name, logo, colours and domain; hardware/software customisation (ODM) is also available. Alternatively use the API only and keep Tongwei UI out of sight. OEM pages, dedicated models and integrations are scoped and quoted separately.

What is the path from selection to volume?

The standard path is selection, sample integration, then volume supply. Timing depends on protocol complexity, point-table size and field conditions, and is committed only after assessment. Samples are chargeable in principle, with credit possible against volume orders.

02

Scene Services

Scene Solution Services

Start from the scene: select hardware, configure the platform, commission on site, and bring field assets into one ledger, alarm and operations loop.

For equipment makers and system integrators who serve these sites. What we sell: scene design, hardware selection, platform configuration and commissioning. Site installation is outside the supply. Energy, equipment rooms, restrooms, building automation and agriculture are sites we have supplied, not a customer list.

Site visible, anomalies known, handling traceable, results verifiable

Who it is for

  • System integrators
  • Equipment makers
  • Control-cabinet builders

Standard capability

  • Scene design and point layout
  • Central monitoring and tiered alarms
  • Work orders, inspection and mobile
  • Reports and open API

What you can verify

  • Finish the scene point design and import the site ledger; verify point counts and owners.
  • Trigger a real anomaly and confirm the alarm reaches the right owner by severity.
  • Run one work order end to end: dispatch, acceptance, field feedback, closure.
Open Scene Solution Services

Scene Solution Services

Start from the scene: select hardware, configure the platform, commission on site, and bring field assets into one ledger, alarm and operations loop.

For equipment makers and system integrators who serve these sites. What we sell: scene design, hardware selection, platform configuration and commissioning. Site installation is outside the supply. Energy, equipment rooms, restrooms, building automation and agriculture are sites we have supplied, not a customer list.

  • System integrators
  • Equipment makers
  • Control-cabinet builders

Site visible, anomalies known, handling traceable, results verifiable

The problem

What you are dealing with now

Many sites, scattered equipment, rounds done by hand; alarms miss the owner and duplicates pile up; work orders, inspection, feedback and monthly reports never line up, so service results cannot be verified.

  • Many sites and scattered assets; rounds are manual, so status and risk cannot be seen in one place.
  • Alarms miss the owner, duplicates pile up, and escalation has no clear owner.
  • Work orders, inspection, feedback and monthly reports sit apart, so results cannot be checked.

The difficulty is the data, not the device

Why this is not solved by adding a sensor

Each site brings different brands, protocols, networks and power, and legacy projects leave disconnected systems and point tables. Scene solution services start with scene and point design, then hardware and platform, so the field lands in one ledger and one rule set — not a new system per scene.

Standard capability

What this line includes by default

This is the standard scope. Protocol adaptation, custom development, OEM pages, third-party integrations and advanced reporting are scoped and quoted separately.

Scene design and point layout

Design the scene and the point list from the actual assets; sites, devices and owners go into one ledger.

Central monitoring and tiered alarms

Multi-site dashboards, online and trend views; alarms tiered, de-duplicated and routed to a named owner.

Work orders, inspection and mobile

Alarm to work order, mobile acceptance, on-site photos and closure — the handling is on record.

Reports and open API

Monthly reports, fault statistics and verifiable service evidence; data and events can also feed the customer's existing platform.

How we work

The path for this line

Diagnosis → single-site pilot → multi-site copy. We supply hardware, platform and commissioning, and do not take the installation contract. Multi-site copy is the typical form of this line: demonstrable, quotable, acceptable, repeatable.

Architecture

How data travels from the field into the loop

  1. 01

    Per-site equipment, meters, sensors, environment and energy assets

  2. 02

    SG / BEC gateway and SDS / IOC modules per site

  3. 03

    AIoT platform: ledger, alarms, work orders, inspection, access

  4. 04

    PC / video wall / app / mini program

  5. 05

    Reports, open API and ongoing service

How to verify

What you can check yourself during the pilot

We do not substitute percentage promises for acceptance. Each item below can be checked by you during the PoC, and used to decide whether to widen scope.

  • Finish the scene point design and import the site ledger; verify point counts and owners.
  • Trigger a real anomaly and confirm the alarm reaches the right owner by severity.
  • Run one work order end to end: dispatch, acceptance, field feedback, closure.
  • Export the operations report and check alarm counts, handling time and open items.

Scope limits for this solution

We do not take the installation contract. We supply hardware, platform and commissioning; site installation and acceptance stay with the integrator or the owner. Protocol, remote-control permissions and acceptance criteria for custom work are confirmed in writing per project.

FAQ

What customers ask most during evaluation

Must Tongwei take the whole project?

No. We can take the whole job or only the design and product complement, with the integrator or owner doing the rest. Protocol and point scope, remote-control permissions, implementation split, acceptance and SLA are confirmed in writing.

We already run another monitoring system — must we replace it?

No. Start with sites and devices not yet covered; bring the existing system into the unified view through APIs or data integration. We recommend a single-site, verifiable pilot before copying to more sites.

Are energy, equipment rooms and restrooms three separate businesses?

No. They are scenes inside scene solution services. What changes is the points and the rules, not a new system. Energy management sits at data acquisition, efficiency analysis and operations — it is not a full EMS and does not do real-time dispatch, production control or safety interlocking.

What if a site has no reliable network?

Gateways support 4G and wired uplinks, buffer data locally during outages and backfill on recovery. Critical interlocks run at the edge and do not depend on cloud connectivity.

Next step

Not sure which line fits?

If you sell equipment or complement a project, start with standard products. If you need a whole site taken through, start with scene solution services. The two lines can combine — the foundation is the same.