Automated Assembly Line RFQ Checklist: What Buyers Should Specify?

When I review an automated assembly line RFQ from an engineering perspective at KH Group, I start with the result the buyer needs. What products must the line handle? How much good output is required? What evidence will show that the equipment is ready? Those answers give an engineering team a useful basis for quotation.

You do not need every design detail before contacting an automation supplier. You do need to distinguish confirmed requirements from open questions. In this guide, I explain how I would organize that information into a practical RFQ package, with a downloadable Excel template for your project team.

What Should an Automated Assembly Line RFQ Accomplish?

Define requirements before equipment

I would treat the RFQ as a shared engineering baseline. Specify the product, output, quality limits, floor-space constraints, and required operating conditions. Let the supplier propose the station layout, feeding concept, and equipment configuration unless your factory has mandatory standards. The buyer owns the requirement; the supplier must explain how the proposed solution meets it.

Make supplier quotations comparable

Two quotations can look similar while covering different work. One may include part feeding, MES integration, and commissioning, while another assumes the buyer supplies them. Ask each supplier to respond against the same requirement IDs and return a consolidated assumption and exclusion list. This makes a lower price easier to interpret and helps prevent scope gaps from appearing after purchase.

What Product Information Should Buyers Provide?

Supply controlled drawings and usable CAD files

Attach 2D drawings and 3D CAD models with part numbers and revision identifiers. The drawings should show materials, dimensions, tolerances, surface requirements, and assembly interfaces. Identify which document takes precedence if the CAD model and drawing differ. Mark any dimensions or surfaces that must not be used for locating, clamping, gripping, or inspection.

Describe the real production range

A nominal CAD model does not describe all the variation an automated line must handle. Include material stiffness, coatings, oil, burrs, color changes, and cosmetic variation where they affect the process. List current variants and identify future models as either a defined design envelope or an open requirement. Ask the supplier to confirm which combinations are included in the quotation.

Provide representative and boundary samples

A single carefully selected sample can hide the hardest feeding or inspection conditions. Provide production samples from the expected range, including accepted parts, known defects, and boundary conditions. Label them so both teams understand the intended classification. Agree sample quantities, delivery dates, and any destructive testing before the supplier builds a trial fixture or inspection study.

What Production Volume and Cycle-Time Requirements Should Be Specified?

Start with demand and available time

I would ask for annual demand, daily or shift demand, working days, shifts per day, and gross shift duration. Then separate breaks, planned maintenance, cleaning, and changeover losses from available production time. Include product mix and typical batch sizes because they affect both output and replenishment. State future capacity needs separately from the initial acceptance requirement.

For example, 420 net production minutes and a demand of 840 good units per day give a takt time of 30 seconds per good unit. This is a demand benchmark, not proof that a machine with a nominal 30-second cycle will meet the target. Unplanned stops and rejected output can reduce good production. See how to calculate takt time and line capacity before fixing the performance requirement.

Separate target cycle time from guaranteed output

Ask suppliers to show station cycle times, the bottleneck, parallel operations, and assumptions about uptime and quality. Distinguish a best-case dry cycle from sustained production with actual parts and operators. The acceptance commitment should state good output under defined test conditions. If a supplier proposes an availability factor, ask how it is calculated and which stops it excludes.

Define how capacity will be expanded if demand grows. Options may include extra tooling, parallel stations, another shift, or a later line extension. Ask the supplier to identify space, controls, utility, and investment implications. Do not treat a possible future upgrade as included capacity unless the quotation explicitly commits to it.

What Process Scope Should the RFQ Define?

Map automated work, manual work, and part presentation

Provide the current assembly sequence and identify the intended start and end of the new line. Mark automated steps, manual loading, replenishment, inspection, and rework. For each part, describe whether it arrives in bulk, trays, pallets, reels, magazines, or on an upstream conveyor. Feeding a randomly oriented part can require a very different solution from picking the same part from a controlled tray.

Assign responsibility at each interface

Define conveyor handoff positions, part orientation, buffer capacity, ready/busy signals, and full or blocked conditions. State who supplies interface hardware and who writes and validates the communication logic. Include reject segregation and what happens when downstream equipment cannot accept a part. Every boundary needs an owner, an input condition, an output condition, and a test.

Relate the scope to the product application

The right process boundary depends on what the line must assemble and verify. A controller, server, appliance, and laptop can have very different handling and testing needs. Use the following KH Group assembly-line pages as starting points for a scope discussion. The RFQ should still define the actual product, process, and acceptance requirements.

Automobile VCU Controller Automatic Assembly Line AI Server Automatic Assembly Line Household Appliance Automated Assembly Line Laptop Automated Assembly Line

What Quality Requirements Should Buyers Define?

Translate quality expectations into measurable characteristics

Writing "automatic inspection required" leaves too much open. List each critical-to-quality characteristic, its tolerance or acceptance limit, and the defect it is intended to detect. Specify the reference method and any gauge correlation or measurement system analysis needed. The supplier should explain how the inspection method works with the expected material and surface variation.

Define inspection errors and reject handling

Where relevant, agree limits for false accepts and false rejects, together with the sample size and test method. Explain whether a rejected part must be diverted, marked, locked in a fixture, or held for review. Define rework permissions and whether retesting may replace an earlier result. Keep serial-level records where the project requires them, with clear retention and retrieval rules.

What Product Changeover Requirements Should Be Included?

Define what the changeover clock includes

List the variants, expected changeover frequency, and maximum acceptable changeover time. State whether the measurement runs from the last good part of one model to the first accepted part of the next. Include tooling removal, adjustment, recipe selection, trial pieces, and verification where applicable. Specify the staffing level and tools permitted during the timed test.

Include tooling, recipes, and error-proofing

Ask which fixtures, nests, grippers, guides, and inspection settings change between models. Confirm storage, identification, and spare tooling requirements. Require a method to detect the wrong tooling, part, or recipe before production continues. A fast mechanical changeover is not enough if the line can restart with an incorrect configuration.

What Controls and Electrical Standards Should Be Specified?

Share mandatory factory standards

Provide approved PLC, HMI, electrical component, robot, and servo standards where they apply. Separate mandatory requirements from preferences so suppliers can propose sensible alternatives. Include operator languages, alarm history, device naming, and maintenance access expectations. Ask for an architecture drawing and equipment list that identify any proposed departures from the plant standard.

Resolve software ownership and remote access

Program backups and editable source code are not necessarily the same deliverable. Define the required PLC, HMI, robot, vision, and recipe files, together with passwords, access rights, and software licenses. Identify subscriptions, renewal costs, cloud dependencies, and any restrictions on buyer modifications. Remote support should use an agreed access method with authorization, logging, and a clear process for ending access.

What Data and Traceability Requirements Should Be Included?

Specify the record and the interface

Define who creates the product serial number and how the line checks duplicates or unreadable codes. List process values, test limits, results, timestamps, and revision information that must be stored. For MES or ERP integration, identify the protocol, message structure, test environment, and responsible team on each side. Ask the supplier to return a sample record and a proposed interface specification.

Plan for faults, access, and recovery

Explain what the line should do when the network fails or the host system rejects a message. Define local buffering, resend behavior, duplicate prevention, and production permissions during an outage. Specify retention periods, backup ownership, and recovery tests. User roles and audit trails should identify who can change recipes, limits, or production records.

What Factory and Utility Information Does the Supplier Need?

Provide an installation-ready site brief

Share the usable floor area, ceiling height, columns, aisles, access doors, and maintenance clearances. Show material flow, operators, forklifts, incoming parts, finished goods, and rejects. Include floor-loading limits, rigging restrictions, and the route from the unloading point to the final location. A layout that fits the production area may still be difficult to bring through the building.

Define utility conditions at the connection point

State electrical voltage, phase, frequency, and available capacity. For compressed air, include pressure, quality, and available flow. Add vacuum, extraction, cooling, gases, or process fluids where required. Describe temperature, humidity, cleanliness, ESD, noise, or vibration constraints, and ask the supplier to identify the utility demand and connection locations.

What Safety and Regulatory Requirements Should Be Included?

Identify applicable requirements and responsibilities

The RFQ should identify the destination market, applicable regulations, selected standards and editions, and customer specifications. Assign responsibility for risk assessment, protective measures, safety validation, and required documentation. A robot application, for example, needs consideration of the integrated cell and its interactions with the surrounding line. Do not assume that one component's documentation covers the complete assembly system.

Define the safety deliverables

Ask for the proposed safety concept, access arrangement, interlock behavior, and maintenance provisions. List the assessment reports, validation records, instructions, and other conformity documents required for the project. Agree how residual risks and operator tasks will be reviewed. The responsible project specialists should confirm the applicable requirements before design approval.

What FAT and SAT Acceptance Criteria Should Be Defined?

Agree acceptance while preparing the RFQ

Factory Acceptance Testing, or FAT, checks the equipment at the supplier's facility against an agreed protocol. Site Acceptance Testing, or SAT, checks the installed system under the agreed site conditions. I would define both before the order because they determine what the performance promise means. Waiting until the equipment is built makes gaps in output, quality, or responsibility harder to resolve.

Fix the cycle-time and production-run conditions

State product mix, sample condition, operators, replenishment method, warm-up, test duration, and minimum quantity. Define when timing starts, how good units are counted, and how stops or rejects affect the result. Record whether the run must be continuous and which interruptions invalidate or restart it. A short demonstration of a fast cycle does not establish sustained good output.

Test variants, quality, faults, and changeover

List the variants and boundary samples to be included, plus any justified sampling approach. Agree yield limits, defect challenges, measurement checks, and evidence to retain. Include safe fault-recovery tests, such as missing parts or communication loss, under an approved test procedure. Verify changeover with the defined tools, operator skill, and timing boundaries.

Define open-item, shipment, and retest rules

Classify open items and distinguish release blockers from items that may be accepted under explicit conditions. Record an owner, due date, required evidence, and retest responsibility for every action. Any conditional shipment should follow the agreed contract and buyer approval process. The FAT report should show what was tested, what passed, and what remains open.

Allocate SAT responsibilities before delivery

Specify site readiness, available utilities, production materials, buyer staffing, and upstream or downstream integration. Define which FAT checks must be repeated after transport and installation. State how site-caused delays, changed inputs, and failed acceptance tests will be handled. Link final acceptance to documented results rather than a general statement that the machine is running.

What Documentation and Training Should the Supplier Deliver?

Make the handover package explicit

List mechanical drawings, layouts, electrical and pneumatic schematics, parts lists, and manuals. Define editable formats as well as readable copies, required languages, and as-built revision status. Include PLC, HMI, robot, vision, safety configuration, and recipe backups where applicable. Agree a restore demonstration if it is needed to prove that maintenance can recover the system.

Match training and spares to the operating team

Specify operator, technician, and engineer training separately where their tasks differ. Define the duration, location, language, materials, and practical exercises. Ask for recommended spare and wear parts with quantities, part numbers, lead times, and prices. Clarify which parts are supplied with the machine and which are recommendations for the buyer to purchase later.

What Commercial Terms Should Buyers Clarify Before Comparing Quotes?

Compare the delivered scope

Require a clear breakdown of equipment, tooling, software, installation, commissioning, training, and spare parts. State who provides samples, utilities, lifting equipment, consumables, and site labor. Confirm travel, lodging, freight, and site expenses rather than assuming they are covered. Mark each major item as Included, Excluded, Optional, Buyer-Supplied, Assumed, or TBD.

Tie commercial milestones to defined events

Clarify warranty duration, its starting event, coverage, response arrangements, and exclusions. Define payment milestones using deliverables such as design approval, FAT, shipment, or SAT. Require a change-order process that records scope, cost, timing, and approval before additional work starts. Confirm quotation validity and dependencies that could change the delivery schedule.

How Should Buyers Compare Multiple Automation Quotations?

I would normalize the technical scope before ranking the quotations. Put each supplier's response beside the same buyer requirement and link it to supporting evidence. A theoretical output figure should not be compared directly with a guaranteed good-output rate under a defined production test. For broader evaluation considerations, see this guide to automation supplier selection.

Request clarification where a cell is blank or the response changes the requirement. Add optional items and buyer-supplied work to the cost comparison so the totals reflect a common scope. If you use a weighted score, agree the weights before evaluation and keep essential acceptance conditions separate. A high overall score should not hide a critical requirement that a supplier cannot meet.

What Should Buyers Include in the Final RFQ Checklist?

Before release, I would ask engineering, production, quality, maintenance, IT, and purchasing to review the same package. Keep drawing revisions and RFQ revisions consistent across all attachments. Separate unresolved information from confirmed requirements and give each open item an owner. This makes supplier questions easier to answer without creating different baselines for different bidders.

A complete RFQ does not need to predict every detail of the final machine. It needs to make the important requirements visible, assign responsibility, and define how results will be checked. From an engineering standpoint, that is what turns separate quotations into a useful basis for an automation investment decision.