When a plant team says it needs a production line for automotive displays, the purchase request usually arrives as one sentence and a budget. What comes back from the equipment supplier is a machine that works—except for three details nobody wrote down. Fixing those details after installation costs far more than describing them on paper ever would. Documenting requirements well is not paperwork for its own sake; it is how you move cost and risk decisions from the commissioning week to the quotation week, where changes are still cheap.
This guide covers what engineering teams should put in writing before a automated production line is quoted, and which items to freeze before the design review. It is written for process engineers, equipment buyers, and project leads who have to hand a supplier something an engineering team can build from.
Why display lines fail on undocumented assumptions
Automotive display assembly sits between consumer electronics and automotive components, and both sides bring their own difficulty. The optical and bonding steps demand cleanroom handling, alignment accuracy, and bubble control, in line with the expectations described on our semiconductor process equipment pages. The automotive side adds traceability, a long parts life, and customer audits that ask for the same evidence years after acceptance. Lines rarely fail on the visible machine. They fail where a requirement was assumed: a cycle time measured at one station instead of the slowest station, a size range that only fits the prototype, or a record nobody was required to keep.
Before you write requirements, settle the product definition
Every downstream number depends on what the line actually assembles. Record these first, because they cannot be changed later without reopening the design:
- Product family: instrument cluster, central multimedia display, HUD, rear-seat or mirror display
- Display technology and stack: LCD or OLED, whether a touch layer or cover glass is bonded, hard-to-hard or soft-to-hard
- Panel size range: minimum and maximum diagonal, plus thickness at both extremes
- Geometry: flat, gently curved, or a three-dimensional formed surface
- Material set: OCA or OCR adhesive, cover glass or PMMA, polarizer, backlight unit, bezel or housing
- Programme horizon: model years covered, expected annual volume, and the changeover plan between variants
Size ranges deserve particular care. A line built around today's 10-inch cluster will not accept a 15-inch centre console without new fixtures, new handling arms, and often a revised vision field. If the customer has hinted at a larger derivative, document the upper bound now, even at the cost of a bigger footprint.
The six requirement areas to write down
1. Process and quality targets
Write each process step in the sequence it will run, from feeding through final inspection. For every step, name the parameter that decides quality: the alignment accuracy for bonding, the temperature and dwell window for a hot-press cycle, the pressure and time window for debubbling, the vacuum level and pressure ramp for vacuum bonding. Specify what is measured on the finished unit—bond shift, bubbles and pit size limits, foreign matter, dead pixels—and where the measurement is taken.
For each parameter, state the acceptable window, who is allowed to change it, and how a change is approved. A supplier that receives "bonding temperature 60 °C, window plus or minus 5 °C, change requires written approval" builds recipe handling into the control software. A supplier who receives "60 °C" does not.
2. Throughput and line balance
State the required output per shift and per hour, at the product mix you actually expect. Then state how you will measure it during acceptance. Cycle time quoted for one bonding station is not line throughput; the line delivers what the slowest station and the changeover time allow. Ask the supplier to show the line balance sheet—the cycle time of each station, the buffer between stations, and the station that limits output—before agreeing to the number.
3. Available time and maintenance
Record planned and unplanned downtime separately, with the target availability you expect over an acceptance window of days, not hours. Add preventive maintenance intervals and the expected consumables list. Specify which spare parts must arrive with the line and what lead time applies afterwards. A maintenance window that is never documented becomes a production stop that nobody planned for.
4. Traceability and records
Automotive customers audit records years after acceptance. Document, before the design freeze: whether each unit carries a unique identity, which process values must be logged per unit, the retention period for those records, the export format, and the interface to your MES or host system. State the alarm log requirements too—if you need to reconstruct a machine state after a complaint, the log has to exist and it has to be readable. Where the line joins an existing system, list the data fields, not just the name of the interface.
5. Facility, utilities, and cleanroom conditions
Equipment arrives into a building with limits. Document the floor area and door dimensions, floor load capacity, compressed-air supply and dew point, electrical supply, vacuum and exhaust availability, and the cleanroom classification for each zone. Temperature and humidity ranges matter to adhesive processes, and foreign-matter limits decide whether handling stays enclosed or opens to the operator. Note the water quality where a process uses it. Anything you leave out here becomes a facility project later.
6. Personnel, safety, and operation
State who will run the line and at what skill level, how many operators are assumed per shift, and which languages the interface and manuals must support. Add the safety requirements that apply at your site, including guarding, interlocks, and lock-out expectations. Specify training content and the depth of the operating and maintenance documentation. A line that only the supplier's commissioning engineer can operate is a line you cannot run.
A practical document set
None of this needs a heavy framework, but it does need separation. Keep three documents distinct so that changes stay visible:
- User Requirement Specification (URS): what the line must do, in measurable terms, written by you
- Design specification: how the supplier proposes to do it, written by them against your numbered requirements
- Acceptance protocol: how each numbered requirement is proven, and what evidence counts
Number every requirement. A number that appears in the URS, the design response, the risk review, and the acceptance evidence is a requirement somebody can confirm. An unnumbered paragraph in a meeting minute is not.
Version control and change handling
Requirements move. What matters is that a change is visible. Give the document set a revision history that records who changed what, when, and why. Put an explicit freeze date on the design, and state what happens to requirements raised after that date: they enter a change list with a cost and schedule impact, rather than being absorbed quietly. Keep a single open-points list, reviewed at a fixed rhythm, and do not close an item on a verbal answer. If your line will handle more than one product variant, record which requirements apply to which variant—variant-specific requirements left in general text are the ones that go unverified.
Sign-off and acceptance evidence
Close the loop before the line ships, not after it arrives. Define a factory acceptance stage and a site acceptance stage, each with the conditions it is run under: which product variant, how many consecutive hours, which measurements, and what sample size. Record the pass criteria next to the requirement they prove. Name the people who sign each stage. Acceptance evidence that is dated and attached to a requirement number protects both sides in a dispute; evidence that is a signed sheet without measurements protects neither.
Common gaps, and the cheapest way to close them
The same gaps recur across display assembly projects. Cycle time is agreed per station rather than per line. The size range is written from the sample panel. The bonding recipe is stated as a target value with no window and no ownership. Traceability is described as "MES integration" with no field list. Maintenance intervals are assumed to be whatever the supplier's manual says afterwards. Changeover between variants is not defined at all. Each of these is a one-paragraph fix while the line is still a drawing, and each is a schedule problem once steel has been cut.
What to review before you send the enquiry
Ask someone who did not write the document to read it against three questions. Can a supplier build from this without a clarifying call? Is every requirement measurable, so a disagreement becomes a measurement rather than an argument? And does the acceptance evidence trace back to each numbered requirement? Where the answer is no, the gap belongs in the document—not in the commissioning schedule. Shenzhen PowerDe Automation Precision Equipment works with engineering teams on integrated engineering team services and equipment customization, and our hardware testing work covers validation of process equipment before handover. If you want an outside read on a draft specification, our contact page lists the engineering enquiry route.
