PARTNERSHIPS · CUSTOMER SERVICES AND ADOPTION
Develop, integrate and deliver with Be Water
Develop applications, contribute licensed methods or models, or integrate our products into equipment and customer services. Research and teaching organizations can collaborate on professional methods, learning materials and application evaluation. Choose the role that fits your work, then agree the result and responsibilities.
Choose the contribution you want to make.
01Service businesses
+
Use selected professional applications within your customer service, or AI Workforce to coordinate recurring work with your existing tools. Industrial Platform supplies the data and calculation foundation where needed. Retain the customer relationship and agreed service responsibilities, while Be Water provides its products and contracted support.
02Equipment manufacturers and integrators
+
Integrate Industrial Platform and selected applications into equipment or an existing platform. Add the required local connectivity and runtime, and choose AI Workforce separately for customer or service-team work. Distribution, software rights and support are arranged around the equipment you deliver.
03Implementation teams
+
Implementation teams may come from the customer, a partner or Be Water. For the selected work, agree the required equipment and system knowledge, access, procedures and acceptance checks. The team connects, configures and verifies supported applications within that scope. For each project, confirm the available product version and implementation materials with us.
Be Water supports its supplied products and contracted work. Method providers address adaptation and unfamiliar professional questions within their agreed scope; site responsibilities remain with the assigned team. At handover, identify the first support contact and escalation routes for configuration, product defects and method applicability.
04Professional contributors and application developers
+
Contribute a method, model or application for use in a defined customer or partner project. Agree inputs, applicable conditions, version, licensed use and the provider responsible for method support. A model may remain in the contributor’s own service and be called through the agreed interfaces; it need not be transferred as source material.
If you want tools for your own expert team, explore Industrial Platform for internal data, calculations and applications. That is a customer adoption route, separate from contributing a capability for others to license. Confirm the relevant product version, interfaces and available materials for either route.
05Research, teaching and industry organizations
+
Collaborate on methods, teaching materials, professional learning or joint application evaluation. Public learning resources and site delivery have distinct purposes and responsibilities.
Contribution rights, usage evidence and compensation To be launched
Your expertise should remain yours to license. You may be concerned about copying or use beyond the agreed scope, understated usage, lost attribution, unclear revenue shares or an open-ended maintenance obligation. These are questions to settle before contributing a model, method or application.
Start with a license that sets out who may use the contribution, where and for what purpose, which changes are allowed, and who maintains it for how long. Agree attribution, compensation and the usage evidence you can inspect and reconcile with settlement. A contribution need not include disclosure of model source code or customer operating data.
We plan to use blockchain for jointly confirmed usage and settlement records, making it harder for any party, including Be Water, to quietly alter a confirmed record. This shared recording capability has not yet launched. It can help you check recorded use and agreed payments; it cannot discover unrecorded calls, prevent every copy, or guarantee payment or a fair agreement.
- 01
Define the contribution and license
Identify the contributor, capability version, applicable conditions, rights holder and method maintainer. Define permitted users and deployments, parameter changes, derivative versions, training use and export. A license may cover routine changes without a new approval for every use or calibration.
- 02
Define the evidence and access
Select the usage measures and record fields needed for the agreed purpose, such as capability version, authorized caller reference, task or run reference and usage quantity. Agree who records and checks them and which fields may leave the deployment. Shared recording is not required of every installation.
- 03
Agree payment and review
Identify who pays whom and whether compensation is based on a license, agreed usage evidence or another project-specific basis. Agree how discrepancies are reviewed. There is no assumed standard rate or share, and no assumption that contributions are free.
| Access question | What the license and project scope define |
|---|---|
| What the contributor can inspect | The agreed usage evidence and level of identification needed to check attribution and compensation; this does not automatically include customer operating records. |
| What the customer can inspect | The capability version, applicable conditions, agreed calculation evidence and charges relevant to its use; this does not automatically disclose proprietary model source material. |
| What is not shared by default | Customer operating data, proprietary methods, source material and other deployments’ records require authorization for the specific disclosure or use. Shared records contain only the selected, authorized information. |
Protection comes from the license, access controls, reliable usage records and agreed review and dispute arrangements working together. Agree who checks discrepancies and how they are resolved, alongside the professional provider’s maintenance scope and Be Water’s product support. Customer and contributor material is not automatically available for general model training.