Evidence / quality
Haoyue structures technical evidence around the project requirement, the equipment boundary, the test condition, and the acceptance record. The exact scope is confirmed for each project; published product limits are configuration references, not a substitute for project validation.
Buyer principle
Ask every supplier to show the same condition, the same measured channels, and the same acceptance method.
Use the proposal checklist ↗Material, part geometry, process window, atmosphere, pressure or load, utilities, data records, site conditions, and acceptance criteria are recorded before configuration is finalized.
Typical output
Approved technical requirement brief
The chamber, hot zone, tooling, press or gas system, vacuum package, controls, cooling, safety interfaces, and maintenance access are reviewed against the agreed process boundary.
Typical output
Configuration review notes and open-item list
Key assemblies, wiring, seals, sensors, fixtures, and utilities are checked against drawings and the agreed bill of scope before functional testing.
Typical output
Inspection records and deviation register
Vacuum or pressure integrity, temperature response, alarms, interlocks, cooling, and empty-load behavior are checked using a defined method and recorded condition.
Typical output
Test records with conditions and results
FAT scope is agreed around the actual equipment functions, data channels, dummy tooling or test load, documentation, operator walkthrough, and outstanding actions.
Typical output
FAT checklist, data package, and action closure
Site utilities, installation boundaries, training, spare-part context, maintenance access, operating records, and support contacts are prepared for handover.
Typical output
Handover pack and service baseline
These public templates help procurement and engineering teams align test conditions, site inputs, milestones, and handover records. Final values and documents remain project matched.
Acceptance structure covering the requirement baseline, functional checks, recorded conditions, deviations, and sign-off.
Download PDFProject-input sheet for electrical supply, cooling, gases, exhaust, access, safety interfaces, and SAT planning.
Download PDFPlanning list for technical, operating, safety, acceptance, maintenance, and service records.
Download PDFSample documents are planning aids. They are not certificates, signed records, or acceptance results for a specific machine.
Evidence layers
Recipe version, temperature, pressure, vacuum, gas state, load, displacement, current or power, and sampling requirements defined for the project.
Model configuration, usable work zone, tooling envelope, hot-zone material, controls, cooling, utilities, and limits stated as configuration references.
Test method, test condition, inspection points, witness responsibilities, records, deviations, and closure criteria agreed before acceptance.
Equipment identity, maintenance baseline, consumable context, alarm history, documentation language, training scope, and support route prepared for operation.
Related evidence paths
Application evidence
See how material, geometry, process window, and verification items are framed before an equipment discussion.
Technical review
Share your material, process, equipment, site, and acceptance inputs so the open questions can be separated from confirmed facts.
Evidence examples on this page describe a project review framework. They do not certify a specific machine, material result, customer, installation, or regulatory approval. Final documents and test scope depend on the confirmed equipment configuration and contract.
Response timing is confirmed after scope review.
