Why the handover package decides whether a perovskite line ramps on schedule
Perovskite production-line equipment is usually bought at a moment when the schedule is already tight: a pilot line is being scaled, a lab process is being transferred, or a customer has committed to a qualification date. The machines arrive, the installation team arrives, and then the project stalls for reasons nobody planned for — missing drawings, an undocumented recipe, a PLC program nobody outside the vendor can read, spare parts with no order number. That stall is rarely an equipment problem. It is a documentation problem, and it is fixed at contract stage, not at commissioning.
A handover package is the set of documents, files, and records that transfers ownership of the line from the builder to the operator. Done well, it lets your own engineers maintain, adjust, and re-qualify the equipment without calling the vendor. Done badly, it becomes the reason a line sits idle for weeks. The checklist below is written for buyers of perovskite production line equipment, and it applies to coating, laser processing, and line-integration equipment of the kind Shenzhen PowerDe Automation Precision Equipment builds for perovskite solar, OLED, lithium battery, quantum-dot and OPV work.
1. Process and recipe documentation
This is the part first forgotten and most expensive to lose. Ask for a written record of every process parameter the equipment was tuned to during acceptance: coating head speed and gap, substrate temperature, drying or annealing profile, laser power, scan speed and pitch, atmosphere and gas flows, vacuum level, and dwell times. For any recipe that was adjusted to make your trial run pass, require the final values, not the factory default.
- Signed recipe sheets per station, with revision number and the date they were locked.
- The machine-readable recipe files themselves, exported from the HMI or PLC, with the exact naming convention the equipment expects.
- A note on which parameters are safe for an operator to change and which are service-level only.
If your process windows were established on the vendor's trial substrate, request the trial data with it. Without those references, your team later cannot tell whether a drifting result is a process change or an equipment fault.
2. Mechanical, electrical, and control drawings
Request both paper and editable digital files. A PDF of a wiring diagram cannot be revised; a source file can. Insist on as-built versions, not the design-issue set, because every line changes during build and the differences are exactly what your maintenance team will trip over.
- General assembly drawings and exploded views, with part numbers on every replaceable item.
- Pneumatic and vacuum circuit diagrams, plus the pressure and flow settings each circuit was commissioned to.
- Electrical schematics, panel layouts, terminal schedules, and the bill of materials for drives, sensors, and safety devices by manufacturer part number.
- PLC and HMI program source with a commented structure, the alarm list with plain-language causes, and the I/O list.
3. Acceptance evidence from the factory and the site
Your purchase order should name the tests up front, and the handover package should contain their raw records rather than a summary statement. For coating and laser stations, that means coating uniformity and thickness measurements across the substrate, registration and alignment results for laser scribing, and the defect or yield figures from the run you witnessed. For line-level equipment, include cycle-time measurement, continuous-run data, and the alignment or fit tolerances the machine was verified against.
Keep the witness report, the deviation list, and the sign-off that closes it. Where an acceptance item was deferred — a subsystem tested only at site, a interlock verified after commissioning — the package must state that clearly instead of leaving it silent, and name who is responsible for closing it and when.
4. Spare parts, consumables, and service terms
A spare-parts list without order codes is not a spare-parts list. Ask for a two-level list: wear items to keep on site, and long-lead items to source from the vendor with an agreed price and delivery window. Note service life or replacement interval for each wear item — seals, nozzles, blades, lamps or laser sources, filters, vacuum pump oil, gaskets — so your planning is based on running hours rather than guesswork.
- Recommended on-site stock, with quantities tied to your planned output.
- Quoted unit prices and a validity period, plus who pays freight on warranty items.
- Warranty start date, what counts as operator damage, and the response time for remote and on-site support.
5. Software, licences, and machine identity
Software is the newest failure mode in equipment handover. Record the licence status of every control, motion, vision, and measurement package, including whether it is perpetual, machine-bound, or tied to a dongle. Get the current firmware and software versions for controllers, drives, and any PC-based station, together with a full system backup and the restore procedure. Write down which PC is which — IP addresses, computer names, and the software versions running on it.
Ask explicitly about what happens if a licence expires or a controller board fails. The answer belongs in the package, because the moment you need it is exactly when you have no line running.
6. Training, installation, and site readiness
The installation handover should include the site requirement record: power quality and capacity, compressed-air quality and dew point, water, drainage, exhaust and venting, floor loading, and any cleanroom or inert-atmosphere requirement, along with how each was verified. Then the training record: dates, attendees, topics, and the competency that was signed off for operators and for maintenance separately. Maintenance training matters more than operating training, because operating skill is easy to teach again after an absence and maintenance skill is not.
Ask for standard operating and lockout procedures written for your line's languages, and for a fault-tree or troubleshooting guide keyed to the alarm list from item 2.
7. Safety, compliance, and interface records
Include the risk assessment, the declared safety functions with their performance level, guarding and interlock descriptions, laser safety classification and documentation for laser stations, and any certificates or declarations supplied with components. Where the line interfaces with your existing equipment, hand over the interface control document: mechanical, electrical, gas, and data interfaces, plus the communication protocol and message mapping that was agreed. Half of all integration disputes are disagreements about where one machine's responsibility ends.
How to make the vendor actually deliver it
The practical answer is to make the package a contractual deliverable with the same weight as the machine, and to break it into documents you can hold back payment against.
- Name the package contents in the order, item by item, and list the file formats you require.
- Tie one payment milestone to a complete package rather than to machine delivery.
- Review the package as a document set at the same time you perform the factory acceptance, not after shipment.
- Require a named documentation owner on the vendor side, and one on yours.
A line whose documentation is complete can be re-qualified after a process change, moved, or staffed by new engineers. That is the difference between an asset and a dependency. If you are specifying a new line, ask the same documentation questions of every automation supplier you shortlist — including an intelligent cleaning equipment manufacturer that also builds production-line equipment — and expect the answer to be a list, not a promise. Our engineering team at Shenzhen PowerDe Automation Precision Equipment works from build specification through integration and support, and the handover scope is something we are glad to agree in writing before the order is placed.
