Mixed-vendor retrofit
Existing Water Bottling System Upgrade
Create a measured mixed-vendor tie-in basis before selecting, connecting or commissioning new equipment.
Decision focus
What must cross this boundary, under which condition, who owns the response, and what evidence closes the interface?
01
Direct Answer
An existing-system upgrade should begin with a verified survey of the installed equipment, drawings, actual operating basis, footprints, utilities, controls, tie-in points, shutdown limits and restart conditions - before a replacement or addition is selected.
02
Position in the System
The upgrade boundary can sit around a blower, filler, labeler, packer, conveyor, treatment transfer or control layer. The task is to connect the new module without treating the existing system as an undocumented black box.
03
Buyer Inputs
- Current equipment list, supplier records, drawings, manuals and available backups.
- Approved bottles, labels, packs and observed operating conditions.
- Measured footprints, elevations, access, tie-in points and shutdown constraints.
- Utility readings and terminal conditions at the proposed connection.
- Controller, I/O, protocol, machine-state, alarm and safety-boundary information.
04
Interface Map
One controlled record for the physical, process, utility, control and evidence boundary.
SystemInterfaceCard
New machine to existing mixed-vendor system
- Upstream system
- Existing or new supplying equipment
- Downstream system
- Existing or new receiving equipment
- Transferred material
- Project-specific water, bottle, label, pack or operating-state information
- Physical connection
- Site-measured tie-in with confirmed geometry, access, boundary and installation constraint
- Required condition
- Compatible product, rate, transfer, utility and operating-state basis confirmed from current evidence
- Utility requirement
- Measured available conditions compared with approved new- and existing-machine requirements
- Control signal
- Mapped existing and new states with defined conversion, fail, stop, reset and restart behavior
- Failure response
- Protect the installed process, isolate the affected tie-in and follow an agreed rollback or recovery plan
- Evidence required
- Survey record, redlined drawings, compatibility matrix, backups, test plan, open-gap list and restart results
05
Main Design Decisions
Survey confidence
Separate verified measurements and current records from nominal, historic or unknown information.
Tie-in boundary
Freeze the mechanical, material, utility, electrical and control demarcation for the new module.
Compatibility method
Compare product, rate, geometry, utilities and state logic explicitly; do not rely on connector or protocol names alone.
Shutdown and restart plan
Sequence installation, backups, dry checks, connected checks and production return around actual operating constraints.
06
Trade-offs to Resolve
Adapt the new machine vs. modify the installed line
Adapting one side may reduce site work, while shifting constraints into the new equipment. Compare access, lifecycle and validation needs.
Retain interfaces vs. replace controls
Reusing documented, stable interfaces can reduce change; replacing obsolete or opaque interfaces may improve supportability but expands validation scope.
07
Common Failure Modes
These are realistic review scenarios, not claims about a completed project.
- Historic drawings are accepted without checking the installed condition.
- Nameplate information is treated as the current sustainable operating basis.
- New controls exchange a nominal signal but do not reproduce the existing stop and recovery behavior.
- The installation plan has no protected backups, staged checks or rollback decision.
08
Required Documents
- Existing equipment and document register with revision/confidence status.
- Site survey, photos, measurements and redlined layout.
- Product-format and actual-operating-basis records.
- Utility readings, electrical drawings, I/O and network information.
- Tie-in, shutdown, backup, test, rollback and restart plan.
09
Questions to Ask Before Quotation
- Which existing records match the installed condition, and what remains unverified?
- What are the measurable mechanical, utility and controls constraints at the tie-in?
- How will existing and new state meanings be reconciled?
- Which staged evidence permits installation, connected testing and production restart?
Project-Specific Confirmation
This page provides a survey and review framework, not a remote compatibility approval. Final scope requires current site measurements, supplier information, controlled backups and an agreed installation/test basis.
11
Related System Pages
Turn the unknowns into a reviewable interface
Review My Existing System
Share the available bottle, output, site, utility and supplier evidence. Open items can remain explicitly marked for confirmation.