Define which products factory readiness must include
Start with startup goals and critical tasks, or with an already defined product need. Specify whether delivery includes AI Workforce for continuing tasks, Industrial Platform for data and professional applications, or both. Select professional applications individually where appropriate, together with the Industrial Platform services each Be Water application needs. AI Workforce is not required, and suitable existing data and systems can continue to be used. Name the users, output recipients and maintainers; readiness work leads to configured products and operating responsibilities.
Prepare people and systems together
The owner defines operating goals and acceptance; specialists supply the selected methods, engineers and suppliers confirm interfaces, and the owner’s HR team plans hiring and job training. Define any purchased operating-design, rehearsal or product-use-training work separately in scope and fees. The selected delivery identifies product configuration, documentation and handover routes. Receiving users rehearse routine work and an incomplete or exceptional case to expose unresolved staffing, information or support.
Prepare the information each task needs
For industrial tasks, confirm equipment identifiers, process steps, record definitions, units, timing and data quality. Selected applications can use systems already chosen for the factory or provided by the group, with field connections where needed. AI Workforce and customer AI need authorized knowledge, tools, output requirements and escalation conditions. Work, Core and Edge supply the relevant technology; the scope follows the task rather than requiring all components.
Test delivery through real tasks
Have the receiving users run a representative task from input to the agreed output. Test missing data, failed access, handover to a specialist and resumption afterward. The acceptance checklist identifies configured products, individually selected applications, interfaces, operating procedures and the people able to use them. Assess whether staffing and dependencies are ready alongside those deliverables.
Begin operations and review the value
Define data frequency, calculation schedules and event triggers for the selected work. Assign who reviews outputs, approves changes and executes site actions. Retain the task, action and subsequent operating records for outcome review. Where savings or other gains matter, agree the comparison and required operating conditions; successful installation alone does not establish those gains.
Define responsibility for runtime, expertise and site support
Agree the continuing runtime, software updates and support supplied with each product or application. Name the owners of models, interfaces and task configurations. Qualified teams handle established procedures; specialists assess unfamiliar conditions and material changes. Specify site-service coverage separately. When changing AI tools, retain suitable industrial relationships, methods and records, then verify the new calls and results.
Prepare a one-page brief
Describe the project stage, startup goals, staffing and specialist support, selected or group systems, and the tasks or product need to address. Before design or procurement choices are fixed, operating requirements can inform those choices; later, check what is already committed. Begin with non-sensitive information. Confirm selected product releases, available materials, licenses, delivery dates and the scope and fees for planning, rehearsals and training.
A preparation checklist
Your notes stay on this page until you download them; they are not saved or sent beforehand.
General guidance for adoption. It contains no customer data, equipment operating instructions or standard pricing.
Readiness, product delivery and handover Choose products and applications for the task Prepare a discussion brief