# Partnership and delivery guide Agree how products, specialist contributions and delivery roles serve customers, with clear usage rights and continuing responsibilities. ## Choose a partnership and define its customer outcome For customer delivery, identify the buyer, users, required work and selected products or applications. Equipment manufacturers may integrate Industrial Platform capabilities. Service teams may use Industrial Platform or specialist applications within their services and add AI Workforce where ongoing task coordination is needed. Specialists may contribute a licensed application. For teaching or research, define the audience, authorized materials and useful output before choosing any products. Agree each activity’s deliverables and acceptance separately. ## Prepare methods, teaching materials and research for public use Define what the intended audience should be able to do, what existing courses, examples or methods already cover, and what each participant will add. Ask people who did not create the materials to work through them, including error cases and limits of applicability. Agree publication, attribution, licensing and maintenance. Treat commercial procurement, site deployment and ongoing product support as separate customer delivery work. ## Equipment and integration partners Manufacturers can integrate Industrial Platform field connections, professional applications and runtime into equipment. Integrators connect the selected capabilities to customer systems or customer AI. Agree supported interfaces, versions, deployment, licensing and joint acceptance tests. Define a reusable configuration and the owners of product updates, equipment support and site adaptation. AI Workforce is an optional choice for the service team. ## Model and application partners: rights and rewards — To be launched Before contributing a model or application, agree permitted users, deployments and purposes, attribution, compensation, and who maintains it for how long. Specify the usage evidence you can inspect and reconcile with settlement, along with review and dispute arrangements. Planned shared records can support this agreement; they have not yet launched. Read the partnership guidance for contributor protection, the role and limits of blockchain, and what remains private. ## Implementation and service partners A customer, partner or Be Water implementation team can install, connect, configure and verify the selected applications. Agree the skills, access, procedures and acceptance checks required for that work. Specialists adapt methods or assess unfamiliar conditions within their agreed professional scope. At handover, identify the first support contact and how configuration issues, product defects and method-applicability questions reach their respective providers. Site-service coverage, response and support periods are agreed separately; competence and authority to act remain distinct. ## Separate product, application and service commitments Be Water is responsible for its supplied products and contracted delivery, adaptation and support; partners provide the applications, integration or services assigned to them. Agree the buyer, licenses, outputs, initial fees and ongoing runtime or support for each part. Specialist methods may have their own licenses and maintenance provider. Compensation follows the contribution’s actual terms: there is no default commission, fee, revenue share or margin, and no assumption that the contribution is free. ## Hand over operating work and support For customer projects, hand over the agreed configuration, interfaces, models, applications and task procedures. Have the receiving team complete routine work and handle an exception using the defined support route. Assign product updates, method maintenance, configuration and site work to the appropriate providers. State what can be retained, modified or exported when use or support ends; exports include only material allowed by its license. Reuse accepted components only within the new site’s conditions and permitted scope. ## Evaluate the partnership against its intended output For customer projects, have the receiving team use the products in routine work and check tasks, versions, acceptance criteria and support. For public materials, ask people who did not create them to work through the task, checking explanations, applicability and any steps they cannot reproduce. Reuse effective content in later partnerships, with new scope and maintenance agreed separately. ## Preparation checklist - [ ] Partnership type: customer delivery, public materials or use by your own team - [ ] Buyer, users, operating task or public audience - [ ] Product and individually selected applications - [ ] Contributors, versions, permitted use and usage evidence - [ ] Integration, specialist adaptation and site-service responsibilities - [ ] Delivery acceptance or independent use of the materials - [ ] Initial commercial scope, contributor rewards and continuing support - [Contributions, usage rights and rewards](https://bewater.ai/en/partners/#capability-rights) - [Product delivery and continuing responsibility](https://bewater.ai/en/product/#delivery-scope) - [Institutional partnerships and public materials](https://bewater.ai/en/partners/knowledge/) Be Water · Adoption guide · 2026-10-14. General guidance, without customer data, equipment operating instructions or standard pricing.