Core + Edge
Industrial Platform
Industrial foundation · new Be Water version in developmentMakes data from different systems usable in one calculation, and runs specialist models and applications on it.
Product
Put specialist analysis and AI to work in daily operations.
Investigate energy use, diagnose equipment, trace quality problems, and follow the findings through to action. Start with one task, keep the systems that work, add only what is missing.
Industrial Platform and the applications build on an existing industrial foundation; the new Be Water versions are being productised. AI Workforce is in development. Current availability
The full picture
Keep what works. Add what is missing. Decide who acts.
Industrial Platform connects your data and runs the calculations. Applications do the specialist analysis. The result goes to your team, or to AI Workforce if you want AI to follow it up.
Read the picture
Existing systems and data → what is missing → the work to be done
What would you like to do first?
Pick the one task you most want to improve.
Use existing records to look into an energy, equipment or quality problem. Check that the data fits the chosen application, then decide whether your team acts or AI follows up.
Running a factoryYour equipment, systems and data
Records from existing monitoring platforms, databases or equipment interfaces. Suitable models, applications and workflows stay in use.
Industrial data and specialist calculation
Industrial Platform Industrial foundation · new Be Water version in development
Relates records from different systems to the same equipment, process and time, so specialist models can use them; runs the applications.
- Align equipment and data
- Check time, units and quality
- Run models and applications
Specialist applications, with the platform services they need
Applications Existing applications · scope stated per application and site
Analyse energy changes, diagnose equipment, trace quality problems, with calculations and evidence for people or AI to use.
Runs on site, in your private environment or in an agreed cloud. Data and IP
Optional
AI Workforce New product in development
Calls the applications and tools, keeps progress and evidence, follows up what is unfinished.
No AI Workforce: the application result goes straight to people.
Result checked
Records of what was done return to the platform for the next review.
Who handles the result?
No AI Workforce needed
Your team or existing process acts
Use the application directly. Your team arranges the site check and the action, records what was done and checks whether it improved.
Site checks, equipment operation and maintenance stay with the people or systems you name.
Access to data is not permission to change records, work orders or equipment settings.
One energy anomaly, handled three ways
A process illustration: it does not connect to production equipment. Change who handles the result to compare.
Find the problem, with evidence
Application
The application finds an energy anomaly against production conditions, with comparison records and calculation evidence.
Act
Your team
Operations staff arrange the site check and action, and record progress in existing systems.
Check the result
Your team
People record the measures taken and use new data to check how energy use changed.
Products and availability
Which products do you need?
Industrial Platform can be used on its own: connect data, run your own models and applications. Be Water applications come with the platform services they need. AI Workforce is optional, for when AI should organise and carry out the follow-up.
On Industrial Platform
Professional applications
Existing applications · scope stated per application and siteQuality traceability; equipment diagnosis and maintenance; energy analysis and optimisation. Used on their own or called by AI Workforce.
Work · optional
AI Workforce
New product in developmentFollows a defined operating task: gathers information, calls tools and applications, tracks progress and hands over when a person has to decide.
Current availability
| Product | Foundation | Current status |
|---|---|---|
| Industrial Platform | Industrial platform with field practice | New Be Water version being productised; version and delivery scope stated per project |
| Professional applications | Existing applications and project foundations | Available scope stated per application, version and site conditions |
| AI Workforce | Existing workflow and interface foundations | Complete AI task product in development |
| Self-diagnosis and automatic quotation | Existing diagnosis and professional methods | Not open yet |
Core team members previously delivered an industrial data platform and professional applications on industrial sites, at their former organisation. Be Water is turning that technology, those models and that experience into products that are easier to deploy, upgrade and keep using. Project experience
What each product does
Industrial Platform · Make data from different systems usable in one calculation
The same equipment can carry different names, units and recording times in different systems. Industrial Platform relates the records to the real equipment, processes, materials and time, so models and applications can use them together.
Your experts, models, AI and own applications can use these data and calculation services without Be Water applications or AI Workforce. The proposal states which systems are connected, which models are set up, and how they are checked and maintained.
Professional applications · Use specialist models on an operating problem
Applications produce calculations, evidence, operating options or open questions for energy, equipment and quality work. Use the result directly, or let AI call the application and carry on with the task.
They come with the Industrial Platform services they need; an existing platform can keep supplying data. Your team, an existing process or optional AI Workforce handles the follow-up.
AI Workforce · Let AI call tools, carry out the task and follow up
AI Workforce calls applications and tools for the selected work, keeps the progress, evidence and action records, and follows up what is unfinished. Suitable existing tools can be connected.
Set the key steps a person confirms, or let checked and authorised tasks run on their own. Tool permissions, site responsibilities and how to stop and hand over are agreed before adoption. Using an application never requires AI Workforce.
Underneath
Work · Core · Edge
The products run on three layers, shaped like water: Edge is the source on site, Core the riverbed that gives the flow its shape, Work the current, with gates where people decide.
Runs AI Workforce
Keeps a task moving until it is finished or handed to the right person. When a decision, information or a site response is needed, it keeps the progress and coordinates the handover. You see the evidence, the actions taken, open questions and who needs to decide.
Industrial Platform
Records how equipment runs, how process steps connect and how material flows. Every value keeps its unit, time and operating condition. Models share data and exchange results, each traceable to its data, assumptions and model version.
Industrial Platform
Connects equipment, collects and stores operating data, and runs local calculation and applications close to the equipment: planned for validated existing industrial PCs or optional Edge hardware.
Small grains, precise meaning, clear relations
Water can take finer shapes than fixed blocks. Core keeps data in small, well-defined pieces with clear relations, so the same records recombine for quality, equipment and energy work without starting over.
The same grains, arranged as
Existing platforms
Already have an industrial platform?
It keeps collecting and storing data; suitable models, applications and workflows keep working. Nothing is replaced wholesale: we check what you have, then list only what the chosen application still needs.
| The work | What you keep | What gets connected or configured |
|---|---|---|
| Read the data | Equipment connections, historical records, existing models and applications | The systems, equipment, fields and periods to read, connected through interfaces |
| Run the analysis | Data, models and tools that meet the chosen application’s requirements | Equipment names, data meanings, units and time aligned; the required models and runtime services configured |
| Use the result | Existing screens, business systems and site teams receive it | Where results go, what may be written back, and who acts and checks |
The proposal lists each added component, where it runs, interfaces, licences and checks, so you can see why each part is needed. Data use and access
Getting started and costs
How do you start, and what do you pay for?
Start from the problem. Setup, trial and ongoing use are arranged separately, and the quote says what each part includes and whether it is one-off or recurring.
Discuss the first task
You describe the problem. Together we define the result you want, who will use it and what action follows the analysis.
Agree the plan and costs
We review your systems and data with you, then list the products to add, where they run, permissions, responsibilities and one-off or recurring charges.
Trial, check and hand over
After the agreed setup, the actual users check inputs, results and the way of working on representative tasks, then receive configuration, guidance and support.
Use and maintain
Your team receives results or oversees AI in the chosen mode; we maintain products, interfaces and models as agreed. New tasks or sites are agreed when you add them.
Cost parts
Possible parts; the actual scope and charging basis are agreed in the proposal.
| Part | When it is needed | What you get |
|---|---|---|
| First connection and configuration | The application needs your existing systems connected, data prepared or models configured | Working data connections, equipment mappings, model configuration, usage checks, guidance and handover |
| Platform operation and maintenance | Continued use of Industrial Platform data, calculation or application runtime services | Operation, version maintenance and product support for the selected services |
| Professional applications (licence) | Use of a specific analysis, diagnosis or optimisation application | The licence, the agreed calculations and outputs, and maintenance of the related models and application |
| AI Workforce (optional) | AI should call tools, organise the task, act or follow up | Connection of the selected tasks and tools, permission setup, run records and ongoing support |
| Site or specialist services | Installation, site checks, physical actions or specialist judgement are needed | Named services, responsibilities and deliverables, each marked one-off or recurring |
Using Be Water applications is a licence for an agreed scope, not a transfer of source code or proprietary models. Be Water is responsible for its agreed products, adaptation, delivery and support; the proposal names who handles site installation, equipment operation and daily actions.
Data and intellectual property
Your data, processes and models stay yours.
Connecting does not change your rights to data, core processes, recipes or your own models. Before adoption you agree what is read, who can access it, whether data leaves the site and what happens when use stops.
Proposed adoption and delivery checks; configuration and what can be verified are confirmed per product version and plan.
Where a diagnosis can run
Planned for the diagnosis service, which is not open yet.
| Processing choice | Where data is read and computed | What leaves |
|---|---|---|
| Offline files | Selected export files on one machine, with local rules, calculations and models | Nothing: the data stays on that machine |
| Inside your environment | Only the data sources and models you authorise | Only to approved endpoints; hosting and processing region are listed |
| Approved external model | Full records and specialist calculation stay on your side | Only approved content, after you see the provider, content, purpose, region and retention |
The model provider and Be Water are different recipients. Connecting is not consent to training general models.
Questions to settle before adoption
Which data will be read?
- Agree
- Only the equipment, fields and periods the task needs, through read-only interfaces or restricted views. Recipes and private models get their own usage scope.
- Check at handover
- Review the allowed data list and confirm that reads and writes outside it are refused.
Where is the data kept?
- Agree
- List where existing systems, applications, temporary caches, logs and backups live. Choose on site, your private environment or an agreed cloud.
- Check at handover
- Review deployment and data flows: actual connections, outputs and what leaves your environment.
Does anything go to external AI or other services?
- Agree
- Agree what external AI, status reporting, remote support and training may receive, and why. Connecting is not consent to training general models.
- Check at handover
- Review recipients, fields and transfer records. For local computation, disconnect external networks as agreed and show the work still runs.
Who can access the system remotely?
- Agree
- Support access only when needed, for named people, periods, sites and functions. You can revoke it.
- Check at handover
- Review support accounts, permissions and access records; confirm access ends at expiry or revocation.
Do recipes or private models have to be handed over?
- Agree
- Where an existing model interface can return the result, call the interface. Before any files, parameters or recipes are supplied, agree purpose, storage, visibility and licence.
- Check at handover
- Review calls and deployments, and what appears in logs, backups and exports.
What happens when use stops?
- Agree
- Revoke credentials and task access, export the agreed data, configuration, results and records, and define how temporary copies and backups are handled.
- Check at handover
- Confirm reads fail after revocation, inspect readable export samples, and confirm how long remaining copies are kept.
Models, files and results that you and your experts provide follow their own licences for calls, deployment and export.
Tell us about one problem you want to solve.
Which equipment, process or site; the improvement you want; your existing systems and site preparation. No core recipes or private model files are needed for a first conversation.
Discuss an adoption plan