Digital product integration for equipment manufacturers
Equipment manufacturers can integrate data connectivity, runtime software and suitable applications into their products. After delivery, customers can use measurements and status records for site analysis, professional computation and everyday work. We supply the relevant products and adaptation support, working with manufacturers on integration scope, shipping configuration and continuing service.
Manufacturers know their equipment and how customers use it. Shipping reusable data definitions, interfaces and runtime capabilities can reduce repeated site setup and make digital functions easier to adopt. Supplying or replacing an edge carrier is one implementation route; the integration choice starts with the applications customers value.
Simulated workflow: recommend, then approve. The operating mode is configured for the task.
First align units and charge/discharge direction, then obtain each site’s permission. A and B enable the status and event application; C remains pending. Data and permissions stay separate.
This example: negative = charging; zero = idle; positive = discharging.
Define units and power-sign convention; retain raw fields
Read-only application; authorize and validate each site separately
Check units, ranges and event meaningsSix samples; check units, ranges and event codes✓
Replay charging, idle and dischargingReplay charging → idle → discharge; no control commands✓
Prepare activation settings for each siteReuse model mapping; prepare separate configurations for sites A/B/C✓
AI drafts; the owner confirms before action.
Enable charge/discharge and event tracking; A/B can view equipment history, C awaits permission
Example feedback recordedA/B reuse the same field mapping while keeping separate data and permissions. C remains pending permission. Replay the same sample set when evaluating later versions.
Space plays/pauses; arrow keys seek.Reduced motion is on. Explore the complete work with the timeline.
Convert equipment fields into application inputs with explicit units and meaning, then replay raw samples. The engineer confirms the mapping; each site authorizes and validates separately. The application is reusable while customer data and operating permission remain separate.
| Time | Charge reading | Power W | Alarm code |
|---|---|---|---|
| 14:00 | 620 | −80000 | 0 |
| 14:05 | 650 | −60000 | 0 |
| 14:10 | 670 | −40000 | 0 |
| 14:15 | 680 | −20000 | 0 |
| 14:20 | 680 | 0 | 0 |
| 14:25 | 660 | 40000 | 0 |
620 ÷ 10 = 62% · −80,000 W ÷ 1,000 = −80 kW
Define units and power-sign convention; retain raw fields
Read-only application; authorize and validate each site separately
A/B reuse the same field mapping while keeping separate data and permissions. C remains pending permission. Replay the same sample set when evaluating later versions.
Reuse the mapping; manage permission and operation per site
Choose an application such as monitoring, energy records, maintenance support or relevant professional computation. Combine the manufacturer’s equipment knowledge with our data and runtime products, defining the functions to retain and the additions to make.
Adapt acquisition interfaces, asset definitions, software and equipment configuration. A temperature record identifies its component and unit; an alarm identifies the equipment state. This lets customer applications use the records correctly. Integrate into new equipment or work alongside existing modules.
Test equipment connections, data computation and the selected application together, addressing configuration, versions and exceptions. After equipment delivery, the selected application processes new records on its configured schedule to support operating analysis and maintenance. The manufacturer, Be Water and delivery teams manage versions, updates and exceptions within their respective product and service responsibilities.
Retain firmware, existing control and the manufacturer’s customer-service interface. Integrate connectivity, runtime software and selected applications around interface and supply requirements. Direct OEM purchasing and connection at an operating site are separate routes; replacing every existing module is unnecessary. Manufacturers can also extend their applications through agreed interfaces and permissions, with supply, licensing and support defined for the product.
Data dictionaries, asset instances, model computation and basic energy management have a historical software and demonstration basis. We select products for the application; the manufacturer contributes equipment engineering knowledge. Joint adaptation turns this foundation into usable digital functions.
Bring an equipment type, interface specifications and the digital function you want customers to gain. Select the first integration application and discuss the prototype, shipping configuration, site connection and continuing support.