At Weishu, we configure food and beverage production equipment around the final product, raw material, package, site, and operating plan. Hourly capacity alone does not tell us which process route, tank volume, automation level, filling system, utility system, or installation boundary the customer needs.
A clear project brief allows us to prepare a more relevant process flow, equipment list, layout concept, utility basis, and quotation scope. It does not need to be a finished engineering package. The following information is enough for our team to begin a structured technical discussion.
We use this checklist for dairy, yogurt, UHT milk, plant beverage, juice, beverage, water, ice cream, cheese, and milk-powder projects. Not every field applies to every line, so our engineers adapt it to the actual process.
Start with a short project summary:
State whether the project is at concept, budgeting, tender, or purchase stage. A budgetary proposal and a contract-ready quotation require different levels of detail.
If confidentiality is important, agree on how formulations, drawings, and commercial information will be handled before sharing sensitive files.
Create one row for each product or SKU. Include:
You do not need to disclose a complete proprietary formula during the first discussion. We do need enough information to understand whether the product is a low-viscosity milk, a pulpy juice, a cultured dairy product, a plant beverage, a viscous mix, or a powder.
If several products will share equipment, identify the most difficult product for heating, mixing, pumping, filling, and cleaning.
Give more than hourly capacity:
Clarify whether the stated capacity is raw-material intake, process flow, filler output, or finished packed product. These are not interchangeable.
We use this information to state the capacity basis for each major module, identify the likely bottleneck, and explain how batch preparation, continuous processing, filling, and cleaning fit into the daily schedule.
Provide the expected process flow if you already have one. If not, describe the required final product and operating constraints so our team can develop a preliminary flow.
Depending on the project, address:
We do not assume legal process conditions from the equipment name alone. The project brief should state who is responsible for product-process development and validation. If trials are required, we confirm the test material, quantity, success criteria, and ownership of results before testing.
Packaging choices affect the upstream process and plant layout. Include:
When we select a filler, we match its working output to the actual product and package rather than relying only on maximum mechanical speed. We also review format-change time, cleaning requirements, start-up material, and operator staffing.
Supply available utility data:
Provide a site drawing with building dimensions, columns, doors, floor levels, drains, ceiling height, and access routes. We use it to prepare the layout and check equipment access, maintenance space, and installation sequence.
If Weishu is expected to include utility-generation equipment, tell us whether site distribution is also required or will be completed locally.
We define the applicable material and hygienic requirements in the equipment schedule, including:
Certification is not universal across every model or project. We confirm the certification requirement at the start and identify the documentation available for the quoted equipment.
The customer should identify the authority having jurisdiction and confirm local requirements with qualified professionals. We then design the quoted scope around the confirmed project requirements.
Define the desired operating model:
Our automation proposal can include the instrument list, control description, I/O scope, panel boundary, software boundary, and responsibility for field wiring.
Automation should be evaluated by function. Two “fully automatic” proposals may differ significantly in valve routing, recipe control, CIP, reporting, deviation handling, and operator intervention.
State which equipment and circuits require CIP and which items will be cleaned manually.
For the CIP section, we define:
Cleaning programs must be validated for the actual product and plant. We explain the equipment capability, circuits, and design basis, while the processor retains responsibility for approving and validating its sanitation program.
List every project element and assign responsibility. Typical items include:
We use a responsibility matrix with “Weishu,” “customer,” “third party,” or “excluded.” This makes the boundary for equipment, piping, utilities, civil work, installation, and commissioning visible before the contract is finalized.
Battery limits should identify the exact connection points for product, water, steam, cooling, air, drainage, electrical power, data, and packaging.
Depending on the project scope, our document register may include:
Agree on language, file format, review stages, number of revisions, and final handover timing.
Replace “machine works well” with measurable acceptance conditions.
Define:
Performance criteria must match the contract scope and be achievable under agreed raw-material, utility, operator, and site conditions.
Our commercial quotation states:
Compare total project scope, not only equipment price.
After we receive the project information, our team organizes the proposal around the following sections:
We identify the assumptions and exclusions that still require confirmation. If the customer changes a product, package, capacity, utility condition, or project boundary, we update the affected process and commercial sections rather than treating the change as a separate machine only.
We recommend a technical clarification meeting before final commercial confirmation. This allows both sides to resolve the process, capacity, layout, utility, interface, and acceptance questions before production begins.
At minimum, send the product matrix, capacity and schedule, package, site and utilities, desired scope, and target market. Mark unknowns clearly; our team will list the assumptions that must be confirmed.
Yes for preliminary budgeting, if you provide enough product-property information to select a process concept. Final equipment and performance commitments may require formulation details, samples, or trials.
The product route, materials, automation, tank volumes, filler, utilities, piping, installation, documentation, and tests may all differ. Our proposal therefore states the design basis and scope instead of relying on capacity alone.
It is the defined connection boundary between Weishu’s scope and the customer’s or another contractor’s systems. Clear battery limits prevent gaps in piping, wiring, utilities, controls, and responsibilities.
Attach the product matrix, production schedule, package list, site layout, utility data, water analysis where relevant, required standards, scope matrix, and any existing process diagram.
Prepare the information in this checklist and send Weishu your project brief with the available drawings and product data. Our engineering team will use it to prepare a preliminary process flow, major-equipment list, interfaces, and quotation scope. You can also review our existing application scenarios and company capabilities before the technical discussion. Final specifications, process conditions, compliance, tests, and commercial terms are confirmed during engineering and contracting.
EN
