Start with what must be achieved on a shift, which decisions need professional judgment and what the site team must do. Map each task to the required information, application, responsible role and handover.
NEW FACTORIES · DESIGN, COMMISSIONING AND STARTUP
Prepare for day-one factory operations
Prepare the people, data and applications your factory will need from its first shift. Carry the responsibilities, specialist methods and records established during construction into daily operations.
YOUR FIRST STEP
From startup preparation to daily operations
Industrial Platform · Industrial foundation · New Be Water release in development
AI Workforce · New product in development
Start with your project stage, target startup date, equipment or design information and critical operating tasks. Together we can define the first delivery and what suppliers and the receiving team need to prepare.
For a first project, confirm the available product version, demonstration or evaluation materials, delivery scope, usage rights and timetable with us.
Prepare the people and information behind each task
Translate that map into supplier interface requirements, role coverage, procurement inputs and training needs. Workflows use the selected applications and systems already chosen for the factory or provided by the group. Equipment identifiers, process steps and operating records give the data and professional methods a common context.
Trained teams carry out established procedures. Specialists adapt methods and judge unfamiliar conditions. The owner and its HR, engineering and supplier teams prepare staffing and job training.
Make today’s decisions ready for the years ahead
Equipment and systems are selected before production begins. Roles and training are often settled at the same time. These choices shape how easily the factory can use current expertise and adopt better AI later.
Define the work first: what must be achieved each shift, which decisions need professional judgment, what the site team must do, and what software and AI can handle. This connects staffing and technical investment to the same operating goals.
Prepare and rehearse before operating records exist
Before design or procurement choices are fixed, operating tasks can inform supplier interfaces, role requirements and selected systems. If procurement or construction is already underway, start by checking those commitments and identify which gaps can still be addressed.
During commissioning, rehearse the selected tasks with design or sample data, then check them against actual equipment, records and permissions.
After startup, review completed work, operating outcomes and support effort. Extend to additional processes or sites when the results justify it, reusing the suitable configuration and methods.
What the operating team receives
Agree which product configuration, applications, connected records, permissions, instructions and support contacts the initial delivery will include. Test acceptance through complete tasks with the receiving team, including missing information and cases that require specialist judgment.
| Work to prepare and run | Who uses what | How it is used and checked |
|---|---|---|
| Prepare procurement and the first operating team | The owner, engineering team and operating leads use design files, equipment lists and the startup plan. | Define critical tasks, role coverage and supplier interfaces. Where included in scope, use design or sample data to rehearse representative work before operating history exists. |
| Check energy and production records each shift | Shift teams use a selected energy application and, where chosen, AI Workforce for missing-data requests and follow-up. | Map equipment identifiers, process steps and records to matching units and periods. The receiving team rehearses normal and missing-data cases using the agreed configuration and instructions. |
| Compare production and supply arrangements | Production and utility leads use the selected model or application and its defined inputs. | Compare feasible and infeasible candidates, check unresolved site conditions and agree where results go. Authorized people or systems execute within the selected operating mode. |
| Handle unfamiliar conditions and conflicting records | Site staff and the agreed specialist use the sources, completed checks and open questions assembled for the task. | Agree the support provider, scope and handover route. Check when users may continue, when further judgment is needed and whether the required support is in place for startup. |
| Add AI or applications later | Maintainers use the equipment and process definitions, method versions and records included in the agreed scope. | Check compatibility, permitted reuse and access before adding new calls. Confirm which configuration or records can be retained or exported; planned portability features are subject to the selected release. |
Make implementation repeatable and expertise available
Qualified teams can connect systems, configure supported applications and carry out checks from established designs and acceptance criteria. The team may come from Be Water, a partner or the customer. Agree competence, access and acceptance responsibilities for the selected work.
Specialists define or adapt methods and assess cases that established procedures do not cover. They can contribute remotely or on site where that support is arranged. The delivery scope distinguishes product support, professional methods and site execution.
| Area to assign | Responsibility to agree |
|---|---|
| Be Water products and contracted work | Be Water is responsible for its supplied products and the delivery, adaptation, updates and support included in its agreement. |
| Implementation | A qualified customer, partner or Be Water team carries out the selected connections, configuration and checks. Define the interfaces with the owner’s engineering, automation and equipment suppliers. |
| Site decisions and actions | The owner assigns appropriately qualified and authorized people or approved systems to confirm site conditions and perform operating actions. |
| People and supplier readiness | The owner coordinates HR, operating leads and relevant design, construction and equipment suppliers. Define any purchased operating-design, rehearsal or training contribution. |
| Professional methods | Identify who maintains each selected model or method, assesses changes in applicability and provides specialist support. Method maintenance is separate from Be Water software support. |
Put the first applications to work
Initial applications can address quality traceability, equipment condition, energy analysis or other agreed operating tasks. They use the relevant professional methods and shared operating data, with clear destinations for results and actions.
Explore the illustrated workflow
Check readiness through completed tasks
Before startup, the receiving team should be able to use the configured applications, explain their results and handle exceptions. After startup, assess operating outcomes, user effort and support requirements together, then decide where to extend the approach.
Agree delivery fees and support after startup
Recurring checks and applications use new operating records. The selected product and method support keeps its agreed scope usable as equipment, settings or operating procedures change. Define who reviews affected calculations and workflows and which changes can proceed within existing authority.
Agree initial scope and fees for the selected software, applications, configuration, integration and acceptance. Operating-design or startup-planning work, rehearsals and product-use training can be included where selected; the owner’s recruitment and job training are scoped separately with their providers. Ongoing terms define software rights, runtime or hosting, updates and support. Additional applications, sites, method adaptation and site work require their own agreed scope.
Built on industrial practice
The team’s previous work includes quality systems, equipment diagnostics, cross-process energy coordination and multi-site operating management. These projects provide methods and software experience for the new factory’s chosen applications.
Explore an illustrated operating task
Interactive work example · simulated records
Trial a human–AI operating task before production starts
Simulated workflow: recommend, then approve. The operating mode is configured for the task.
Decision and resultExample review result
312 → 288 kWh · 12.0 t
After feed preparation is revised, this example uses 288 rather than 312kWh for the same 12t output; waiting falls from 8 to 2 minutes. The engineer reviews these simulated results.
Electricity intensity in two matched-output trials
kWh/tExample recordsMatched referenceAfter review
The axis shows elapsed time within each trial; both produce 12t.
Calculated output312 kWh ÷ 12.0 t = 26.0 kWh/t
L-02 meter scope; same trial batch; Crew records mark feed waiting
The 23kWh/t trial reference is predefined in this example
AI work in this example3 / 3
Read trial and crew recordsRead trial batch T-06 and crew records✓
Compare electricity use with waiting periods10:10 and 10:15 exceed reference; read idle-wait events✓
Draft the crew check taskDraft a crew check task, requiring engineer approval✓
Human + AI taskSimulated review complete
First commissioning run: examine low-load energy use
Operating preparationEngineer review · crew trial training
Data preparationMeter · batch · waiting events
Together they support this trial taskHuman reviewCommissioning engineer
AI drafts; the authorized reviewer confirms before action.
Work order
Engineer approves preparing feed before starting this stage; the crew trials the revised handover
Example feedback recordedFollow-up records26.0 → 24.0 kWh/t
After the revised handover, the simulated matched-load trial records 288kWh / 12t = 24kWh/t and waiting falls from 8 to 2 minutes. The engineer reviews this illustrated comparison.
First task trial complete; engineer confirms continued use0:41
Space plays/pauses; arrow keys seek.Reduced motion is on. Explore the complete work with the timeline.
Read all records, calculations and review notes
Before production, select one task with reviewable inputs, calculations and responsibilities. AI reads records, runs the calculation and drafts a check; the engineer approves, the crew acts and reviews the next trial.
| Time | kWh | t | Crew event |
|---|---|---|---|
| 10:00 | 42 | 2.0 | — |
| 10:05 | 48 | 2.0 | — |
| 10:10 | 66 | 2.0 | Feed waiting |
| 10:15 | 62 | 2.0 | Feed waiting |
| 10:20 | 50 | 2.0 | — |
| 10:25 | 44 | 2.0 | — |
Decision and result
312 kWh ÷ 12.0 t = 26.0 kWh/t
L-02 meter scope; same trial batch; Crew records mark feed waiting
The 23kWh/t trial reference is predefined in this example
Follow-up records
After the revised handover, the simulated matched-load trial records 288kWh / 12t = 24kWh/t and waiting falls from 8 to 2 minutes. The engineer reviews this illustrated comparison.
First task trial complete; engineer confirms continued use
Tell us what must work on the first day
Describe the construction stage, the team and systems being prepared, and the operating tasks that matter at startup. We can discuss a coordinated approach or a specific product requirement.