A line can contain excellent paper insertion, winding, coil insertion, forming, lacing and testing machines and still miss its production target. The usual cause is not that every station is technically poor. It is that nobody owned the spaces between them: which part arrives, which material revision runs, how identity travels, how a failed stator exits, what the operator does after a stop, and which evidence closes acceptance.
This is why the cheapest compliant-looking quotation can become the highest-risk project. A short proposal leaves assumptions invisible. One supplier may include transfer, traceability, change tooling, guarding validation and run-at-rate support; another may price only stand-alone automatic cycles. The totals are not comparable until the boundary and evidence are aligned.
Product family, route, boundary, capacity, quality and site constraints.
Process concept, interfaces, safety, data, access and change control.
Representative parts, production-intent materials, tooling and methods.
Integrated performance, quality evidence, faults, recovery and documents.
Installed utilities, site interfaces, ramp-up, training and controlled files.
A stator line is a discrete-manufacturing system, so the standard is not a universal contract template for every project. Its core discipline is still useful: define the applicable specification, the test plan, the parties and the evidence before the test begins.
“One paper inserter, two winders, one inserter, one former and one lacer” sounds precise, but it embeds an untested process architecture. It says nothing about which stators use that route, whether all products share the same datum, which variants need phase-by-phase insertion, or whether terminal work and electrical testing are inside the line boundary.
Begin with a product-family matrix. For each variant, record the stator envelope and mass, slot count, stack, conductor and winding data, insulation materials, lead and terminal arrangement, required route, quality characteristics, forecast mix and expected product life. Highlight the extremes that challenge different stations. The largest stator may govern handling; the highest slot fill may govern insertion; the most delicate liner may govern material trials.
“Complete stator line” can mean a line that starts with a bare core and ends after electrical test, or a smaller system that starts with an insulated core and stops before lead connection. Impregnation, curing, terminal joining, visual inspection, packing, reject analysis and rework may sit inside or outside the quoted scope.
A 20-second automatic cycle does not necessarily mean three accepted stators per minute. Ask what starts and stops the clock. Is loading included? Is the quoted value for the easiest part? Does it include paper-roll replacement, wire replenishment, lacing-thread change, in-process inspection, reject handling or a shared robot? Does the line need two parallel winders because winding is slower than insertion?
The capacity model should show bottleneck cycle by product, parallel-station logic, planned staffing, changeover, planned maintenance, inspection frequency and forecast mix. Separate ideal automatic cycle, demonstrated sustained rate and practical planning capacity. Define whether the acceptance metric is total output, accepted output or first-pass output; otherwise rework can hide a weak process.
Useful test: ask two suppliers to calculate one eight-hour scenario with the same mix, break pattern, replenishment, changeover and quality checks. The assumptions often explain more than the headline seconds.
An easy stator built with hand-selected wire and fresh tools can make almost any demonstration look stable. The real project risk often sits elsewhere: a high-fill variant, short stack, soft liner, difficult lead exit, tolerance extreme, multiple wire, abrasive lamination edge or terminal operation with limited access.
Agree which part challenges which risk. Samples should use released or clearly identified pre-release drawings, production-intent materials and representative upstream conditions. Define sample quantity, material lots, conditioning, incoming inspection, destructive checks, metrology, disposition and who owns the resulting data. A “golden sample” is useful only when its revision and acceptance criteria are controlled.
Integration failures are often ordinary: one carrier blocks the next tool, a stator arrives at the wrong angle, the PLC handshake cannot distinguish “part absent” from “part rejected,” or a station changes recipe while the downstream tester still holds the previous variant. Mechanical, electrical, controls, data and quality interfaces all need named signals and failure behavior.
For every handoff, define the physical datum and orientation, carrier identity, part-status states, recipe authority, buffer capacity, handshake, timeout, reject route, rework rules and recovery after power loss. If a robot or conveyor is supplied by another party, its safe-zone interaction and line-stop behavior belong in the same interface document.
A real changeover may require winding forms, insertion tools, wedges, nests, fingers, lacing programs, vision jobs, test fixtures and carrier inserts. It also requires cleaning, verification and a controlled first-off release. If tools are heavy, delicate or easy to install incorrectly, the labor and risk may dominate the nominal recipe-selection time.
Classify changes as recipe-only, change-part, major tooling or engineering modification. For each class, define target time, staffing, lifting aids, storage, poka-yoke, revision identification and verification. Reserve future capability as an envelope—dimensions, load, I/O, network, floor space and software architecture—not as an unlimited promise that “more variants can be added later.”
A line footprint can fit on the drawing while the project fails around it. Doors may not admit the largest module. Cable trays, exhaust, cooling, compressed air, electrical short-circuit capacity, floor loading or overhead services may be unresolved. Operators may fit, but maintenance staff cannot remove a spindle, pull an insertion tool or open a control cabinet without dismantling adjacent equipment.
Run a joint layout review using installation, operation, replenishment, fault recovery and major-maintenance scenarios. Include incoming and outgoing material routes, wire and paper roll handling, tool carts, quality quarantine, ergonomic reach, lifting points, service clearances, egress and future expansion. Record utility quality—not just nominal connection size—and assign responsibility for measurements before shipment.
A short automatic run proves that the line can cycle under prepared conditions. It does not show sustained output, material replenishment, quality stability, changeover, alarm handling, rejected-part routing, safe intervention, power-loss recovery, data integrity or documentation completeness.
Write the FAT protocol before equipment completion. State prerequisites, sample and material quantities, measurement methods, calibrated instruments, witness roles, duration, acceptable stops, restart rules, data retention and deviation handling. Challenge faults deliberately: missing liner, wrong recipe, blocked transfer, failed test, lost network, full buffer and interrupted cycle. Verify that the line fails safely and preserves part identity and quality status.
Keep a punch list with severity, owner, due date, retest evidence and effect on shipment or acceptance. “To be fixed at site” is a risk decision, not a neutral note. Any open item that could invalidate site installation, safety, product quality or capacity needs an explicit disposition.
| Vague quotation phrase | Acceptance-ready definition | Evidence to request |
|---|---|---|
| “Suitable for your stators” | Named product revisions, size/winding/material envelope, route and exclusions | Product-by-process coverage matrix |
| “Cycle time: 20 s” | Clock boundaries, product, staffing, parallel stations, quality checks and replenishment | Capacity model plus demonstrated run data |
| “Quick changeover” | From last accepted part to first accepted part, with named staff and tools | Witnessed change-and-return protocol |
| “MES ready” | Data owner, tags/objects, protocol, states, timestamps, retention and error recovery | Interface control document and test script |
| “Safety compliant” | Applicable jurisdictions, risk assessment, safety functions and validation scope | Controlled safety file and open-item register |
| “Training included” | Roles, language, hours, materials, competence check and refresher conditions | Attendance, content and practical assessment records |
| “Spare parts included” | Commissioning, critical and consumable spares with quantity and lead time | Part-numbered list, drawings and obsolescence route |
| Question | FAT at supplier | SAT at buyer site |
|---|---|---|
| Primary purpose | Show the built system satisfies the agreed factory-test specification before shipment | Show the installed system works with actual site utilities, interfaces, materials and operating conditions |
| Typical focus | Machine functions, integrated sequence, process quality, rate, faults, recovery and document readiness | Installation, utilities, network/MES, logistics, safety integration, training, ramp and site performance |
| Representative inputs | Agreed production-intent parts, materials, tooling, recipes and test equipment | Released site materials, production personnel, factory systems and normal support functions |
| Cannot substitute for | Unknown site conditions and long-term production capability | Process/design defects that should have been exposed before shipment |
| Completion evidence | Signed protocol, raw data, deviations, punch list and shipment disposition | Signed protocol, closed site issues, backups, training, spares and production-handover record |
The exact sequence can include a factory integration test or site integration test when multiple suppliers or systems must be combined. Names matter less than the test boundary: every requirement should have one verification method, one location, one owner and one retained record.
- Approved product-family and process-route matrix with challenge parts identified.
- Incoming/outgoing conditions and a complete supply/integration responsibility matrix.
- Capacity model using one agreed mix, staffing pattern and loss boundary.
- Site layout, utilities, logistics, maintenance access and installation data.
- Mechanical, controls, data, quality and safety interface-control documents.
- Representative-sample and production-intent material plan for process proof.
- Design-review gates, revision control and commercial change process.
- Risk assessment, applicable-jurisdiction plan and safety validation deliverables.
- FAT/SAT protocols, run-at-rate rules, deviation handling and punch-list closure.
- Lifecycle index covering editable files, backups, licenses, access, spares, training and service.
The safest way to buy a new stator production line is to make assumptions visible before they become changes. Define the product family and route first; then align capacity, interfaces, site conditions, safety, data and lifecycle support around that definition.
A capable supplier should be able to turn those requirements into a reasoned proposal and a testable acceptance plan. The buyer’s job is to preserve the chain of evidence from URS through design review, representative process trials, FAT, SAT and handover. That chain—not the number of machines in the quotation—is what makes the equipment a production line.
What should be included in a stator production line RFQ?
Include the product-family and route matrix, incoming/outgoing condition, winding and insulation data, quality characteristics, required output by mix, automation boundary, site interfaces, changeover classes, safety and data requirements, representative samples, acceptance methods and lifecycle deliverables.
How should practical line capacity be specified?
State the product mix, shift pattern, staffing, parallel stations, loading, quality checks, replenishment, changeover and planned-loss assumptions. Separate ideal automatic cycle from demonstrated sustained rate and accepted production output.
What is the difference between FAT and SAT?
FAT verifies agreed functions and performance at the supplier before shipment. SAT verifies the installed line with the buyer’s utilities, network, factory systems, materials, logistics and personnel. The protocols should be connected, but neither automatically replaces the other.
Which stators should be used for process trials and FAT?
Select parts by risk, not convenience: dimensional extremes, high slot fill, sensitive insulation, difficult leads or terminals, and representative material variation. Map each sample to the process condition and evidence it is intended to challenge.
Should payment be linked to FAT and SAT?
Objective milestones can reduce ambiguity, but payment, title, warranty and remedies are commercial and legal decisions. The technical team should define measurable evidence and open-item severity; procurement and legal teams should convert that evidence into contract terms.
What software and service items should be handed over?
As applicable to the contract: editable automation projects, known-good backups, parameter and recipe baselines, licenses, admin and recovery procedures, data-interface files, drawings, calibrated-tool lists, spares, training records, support contacts and controlled open issues.
