Publish Time: 2026-11-18 Origin: Site
A factory does not truly hand over when the last machine is switched on; it hands over when the people who must run, maintain and audit it have the documents they need. Yet documentation is the most consistently under-specified part of a turnkey agreement, usually reduced to a single line promising manuals, and the gap only becomes visible months later when a line stops and nobody can find the drawing, or a customer audit asks for a record that was never produced. A turnkey PCBA factory documentation package is a defined set of deliverables, each with an owner, a format and a point of handover, and it should be written into the contract rather than assumed. This guide sets out what that package should contain — equipment records, process and quality documents, configuration files, as-built drawings, acceptance evidence, compliance records, training materials and the data files behind traceability — so that a turnkey PCBA factory solution arrives not just as working equipment but as a maintainable, auditable asset.
Documentation is easy to treat as an accessory to the real work of building a factory, but it is a deliverable with its own scope, cost and acceptance criteria, and projects that treat it otherwise pay later. The reason is simple: the plant will outlive the installation team, and every question that arises afterwards — how to calibrate a feeder, what the original line settings were, which standard a process was accepted against — must be answered from records rather than from a phone call to a supplier who has moved on. Defining documentation as a deliverable means naming each item, deciding its format and language, and setting a handover milestone. This is closely related to writing a clear scope of supply, because documents are part of that scope and belong in the same three-zone list of supplied, excluded and buyer-provided items.
The phrase "documentation package" is too broad to be useful until it is broken into categories, each with named contents. At minimum it should cover the machines themselves, the processes configured around them, the building and utility interfaces, the acceptance testing, the training delivered, and the records the factory will generate in operation. Each category contains both static documents, such as manuals and drawings, and dynamic files, such as machine programs and configuration backups, which change as the plant evolves. Defining what the package means at the outset prevents the common situation where a buyer expects a complete operating manual set and a supplier believes a parts catalogue satisfies the promise. Write the categories down and attach a sample list, then the phrase has a shared meaning.
When documents are left vague, they are the first item to be compressed under schedule pressure, because nothing visible breaks if they are late. The cost appears later: a technician cannot find the pneumatic diagram during a fault, a process engineer cannot reproduce the settings that achieved good yield, or an auditor cannot see evidence that acceptance testing was performed. Each of these turns a short interruption into a long one, and collectively they reduce the value of an otherwise well-built plant. Documentation also has commercial consequences — a factory that cannot show its records is harder to certify, harder to insure and harder to sell. Treating the package as a scheduled deliverable with its own acceptance is a small upfront discipline that avoids a long tail of avoidable cost.
Every document in the package needs an owner and a handover point, because a document that nobody is responsible for producing will not appear. A useful way to enforce this is a document register — a single table listing each deliverable, its owner, its format, its due milestone and its acceptance status — which is reviewed at the same meetings as equipment progress. Without such a register, documentation exists only as a clause in a contract and nobody notices it is late until handover week. The register also makes the package auditable in itself, because you can see at a glance which items have been received, which are outstanding and who is chasing them. Treat the register as a live project document from the order date onward rather than a form filled in at the end. For supplier-generated items, state the format, the language and the milestone — for example, manuals before shipment, as-built drawings after installation, acceptance reports at site sign-off. For buyer-generated items, state what the buyer must supply and by when, since the supplier cannot document a utility or a product program without the inputs. Define whether documents are delivered in paper, electronic form or both, and where they will be stored once received. Assigning ownership and timing turns a wish list into a plan that can be tracked, and it makes a late document as visible as a late machine.
The equipment records are the foundation of the package, because they are what the maintenance team will use for the entire life of the machines. These documents must match the machines as actually delivered, not a generic catalogue version, and they must be complete enough to support independent maintenance. Where a line combines several suppliers, require a consolidated set so the team is not left reconciling inconsistent formats. Referencing recognised standards for symbols and documentation practice, such as those published by IPC where relevant, gives a consistent basis without inventing performance claims.
Require a manual for each machine that covers operation, routine maintenance, adjustment and fault finding, written in the language your team uses. A manual that only describes controls but not maintenance intervals or adjustment limits is incomplete, so state the topics it must cover rather than just asking for a manual. Define whether manuals are supplied as editable electronic files, printed volumes, or both, and whether updates are provided for the support period. Where the same machine type appears several times, ask for one master manual plus machine-specific differences rather than duplicate copies. A well-specified manual set is the single most used part of the documentation package over a plant's lifetime.
Require complete drawings that reflect the equipment as built: electrical schematics and wiring diagrams, pneumatic and vacuum schematics, and mechanical assembly or layout drawings. These are essential for fault diagnosis and for any later modification, and generic drawings that differ from the delivered machine are worse than none because they mislead. State the drawing standard and file formats expected, such as editable vector files rather than scanned PDFs alone. Define whether the supplier must provide a schedule of components with part numbers and ratings, which allows the maintenance team to source replacements locally. Where utilities connect to the machine, the drawings should show the connection points and ratings clearly.
Require a spare-parts catalogue that lists each part with a unique identifier, description, quantity recommended and expected lead time, and that distinguishes stocked spares from items that must be ordered. A catalogue that uses only the supplier's internal codes is of limited use if those codes cannot be cross-referenced to standard components, so ask for manufacturer and specification details wherever possible. The consumables list should name every item the line uses regularly, from stencils and feeders to nozzles, cleaning agents and coating materials, with approved alternatives where they exist. This connects directly to the scope of supply checklist, which should already have defined which of these items were included at handover. A clear catalogue and consumables list turn spare-parts management from guesswork into planning.
Modern machines are defined as much by software as by hardware, so the package must include the licences, firmware versions and configuration backups that keep them running. State which licences are perpetual, which are time-limited and what happens when they expire, because a licence that lapses quietly disables a function. Require a configuration backup for each machine — the settings, parameters and offsets that represent the working state at acceptance — stored in a format that can be restored. Define whether the supplier provides firmware updates and for how long. A machine with its original configuration preserved can be recovered after a fault; one without it can take weeks to tune back to the same state.
Equipment documents describe what the machines are; process documents describe how the factory is run. This part of the package turns a collection of machines into a repeatable operation, and it is often the part buyers forget to request. It should capture the agreed process parameters, the inspection criteria, the handling rules and the quality system records that tie them together. The content should reflect the quality gate plan for the plant, so that every gate has a documented method and acceptance basis.
Require a documented process flow that shows every step from goods-in to shipping, including handoffs between SMT, through-hole, cleaning, coating, inspection and packing. Each step should have a work instruction describing the method, the key parameters, the equipment used and the checks required, written so a trained operator can follow it without interpretation. State whether the supplier provides these instructions or only a template for your team to complete, because the difference is significant. Where instructions are product-specific, define which products are covered at handover and who extends them for new ones. A complete set of work instructions is what makes output repeatable across shifts and operators.
Require the process parameters established during commissioning — printer settings, placement programs, reflow profiles, soldering settings, coating parameters and inspection thresholds — recorded in a set of approved set-up sheets. These values represent the proven starting point for each product and are invaluable when a process drifts, because they let the team compare the current state with a known-good one. State the format and whether the sheets are controlled documents subject to change approval. Define whether the supplier provides parameters for all products in the agreed family or only for samples used during acceptance. Where changeover is frequent, a well-organised set of set-up sheets reduces both setup time and variation.
Require the inspection and test specifications used at each quality gate, including the criteria for acceptability and the method for recording results. Where the criteria reference recognised standards, name the standard and the revision, using frameworks such as IPC documents without inventing limits. Define who owns the decisions about acceptability, since a supplier's criterion and a customer's requirement may differ, and the factory needs one authoritative basis. Require the test specifications used during acceptance to be handed over, so the same tests can be repeated later. Complete inspection documentation allows the plant to prove that it builds to the agreed standard, not merely claim it.
If the plant operates under a quality management system, the documentation package should include the records that system requires: calibration logs, equipment qualification records, process validation reports, nonconformance procedures and change-control forms. State which of these the supplier provides and which the buyer maintains, because the boundary is frequently unclear. Define the format for records and how they will be retained and retrieved, since a record that cannot be found is of no use in an audit. Where the project itself involved changes from the agreed design, require a change log showing what changed, why and who approved it. These records form the evidence that the factory is controlled rather than merely equipped.
A factory's documentation must also include the digital files that define what it builds and how it builds it, because these are needed to reproduce a product or reconfigure a line. This area is often overlooked because it sits between the supplier's world and the customer's, and both sides may assume the other owns it. Define each file type, its format and the point of transfer. The files created during the proposal and planning stage should also be reconciled here, so the as-built reality matches what was originally agreed.
Require a consolidated set of board design data — Gerber or ODB++ files, drill data, panel drawings and stack-up information — for each product covered at handover. These files are needed to generate stencils, fixtures, programs and inspection routines, and a line that lacks them cannot be quickly adapted when a product returns. Define the version-control convention, because a board revision change without a corresponding file update causes subtle errors. State whether the supplier needs these files as inputs during commissioning and confirm that they are returned or passed through unchanged. A clean, versioned board-data set is a reusable asset well beyond the initial project.
Require the programs created for each machine — placement programs, inspection routines, coating paths and handling recipes — as editable files with documentation of their structure. A program that exists only inside a machine controller is fragile: a controller failure or a software update can lose it, and a new operator cannot understand it. State the format required and whether the supplier provides a program for every product in the agreed family. Define who is responsible for maintaining programs when new products are introduced, and require a naming convention so files can be found reliably. Program ownership is one of the most important practical questions in a documentation package, because it determines whether the plant can support itself.
Require drawings for every custom fixture, stencil, carrier and tooling item supplied with the project, including dimensions, materials and tolerance information. These items wear out or need duplication, and a drawing is what allows a replacement to be made without reverse engineering. Define whether the drawings are supplied in editable form and whether the supplier grants the right to reproduce the tooling elsewhere. Where a fixture was designed specifically for an odd-form component or a coating mask, its drawing and design rationale should be preserved. A tooling drawing set protects the plant from a single-source dependency on the original supplier. It is worth requiring a short design note alongside each drawing explaining what the fixture achieves and why it was built that way, because a drawing shows geometry but not intent. When a product changes, that intent is what lets an engineer decide whether the old tooling can be adapted or must be replaced. Where the supplier used a standard fixture as a base and modified it, record the base part so a replacement can be sourced independently. These notes are small to produce during commissioning and disproportionately valuable years later, when the people who designed the fixture are no longer available to ask.
A factory changes during installation, and the documents that describe it afterwards must reflect what was actually built rather than what was planned. As-built drawings are the definitive record of where services run and how equipment sits, and they are indispensable for any later modification. This category also covers installation evidence and the interfaces between the supplier's work and the buyer's facilities, which are described from the planning side in the greenfield versus brownfield comparison.
Require a final layout drawing showing the actual position of every machine, conveyor, buffer and access point after installation, not the proposed layout from the quotation. Small shifts made during installation matter when a later machine must be inserted or a material route changed. State the drawing format and whether dimensions are included, since a scaled electronic drawing is far more useful than a schematic sketch. Require the drawing to show clearances and access zones so future changes do not block maintenance paths. An accurate as-built layout is the reference that every subsequent project in the plant will use.
Require drawings showing where power, compressed air, water, exhaust and network connections were actually installed, with ratings and circuit references. A schedule listing each connection point, its capacity and the equipment it serves makes future load checks possible without tracing cables. Define whether the supplier documents only its own scope or the complete utility picture for the plant, and if the latter, who verifies the buyer-provided portions. Require test records for critical supplies, such as air quality or extraction performance, where these were part of acceptance. Utility drawings are the documents most often missing at exactly the moment they are needed — during an expansion.
Require records of the installation itself: delivery and unpacking reports, levelling and alignment records, connection checklists, and sign-offs at each interface between supplier and buyer scope. These records establish that installation was completed correctly and provide evidence if a later fault is traced to an interface. Define the format for sign-offs and who from the buyer's side must approve them. Where installation happened in phases or during shutdown windows, require a record of each phase and its restoration state. Installation records are a small part of the package but disproportionately useful in resolving responsibility questions later.
Acceptance records prove that the factory met its criteria at handover, and they form the baseline against which future performance is judged. They should be complete, signed and easy to retrieve, because a customer audit or an internal investigation will eventually ask for them. This part of the package should mirror the acceptance plan defined earlier and connect to the readiness checklist before installation, which established the conditions under which testing began.
Require the factory acceptance test and site acceptance test reports, listing each test, the method, the result, the criterion and the witnesses. A report that states only passed or failed is inadequate; it should record the measured outcome so a future comparison is possible. Define whether failures and their resolution are documented, since a resolved failure is part of the machine's history and useful to know. State the language and format, and whether electronic signed copies are acceptable. Complete acceptance reports are the strongest evidence that the delivered plant met its agreed specification.
Require a record of commissioning that captures the plant's performance at handover — cycle times, yield figures, changeover times and any other agreed indicators — measured under defined conditions. This baseline is what allows the team to decide later whether a change has degraded performance, rather than relying on memory. State which indicators matter for your operation and require them to be recorded with the conditions under which they were measured. Where the plant is expected to grow, define whether baseline measurements are repeated after each phase. A well-documented baseline turns subjective impressions about performance into measurable facts.
Require calibration certificates for measuring and test equipment, with dates, methods and traceability to recognised standards where applicable. Define the calibration intervals expected and whether the supplier provides a schedule for future recalibration. Where a machine influences product quality — an inspection system or a process controller — its calibration status should be documented and visible. State whether certificates are supplied for items provided by the buyer as well as by the supplier. Calibration records are a routine audit request and a common finding when they are missing, so include them explicitly in the package. Require also a calibration schedule that shows when each instrument is due for recalculation, so the plant can stay current without relying on memory. Where equipment was calibrated by an external laboratory, keep the laboratory's accreditation details with the certificate, since an auditor may ask whether the calibration is traceable. Define how records are stored — a controlled electronic folder with clear naming is usually best — and who is responsible for adding new certificates as instruments are replaced. A calibration system that is maintained continuously is far less work than one reconstructed before an audit.
A factory must be able to demonstrate that it operates safely and within the applicable regulatory framework, and the documents in this category provide that evidence. Requirements vary by market and product, so state which frameworks apply rather than assuming a generic set. Where standards such as those from IPC or joint IPC/JEDEC publications are relevant to acceptability, name them as references without claiming certifications that have not been earned.
Require the declarations and certificates that come with the equipment — conformity declarations, safety certificates and any documents required for import or installation — and define which are originals and which may be copies. State the format and language expected, particularly where local authorities require documents in the national language. Where a machine bears a conformity marking, require the supporting documentation and the basis for the marking. Define who retains the originals and where copies are kept for daily use. A complete certificate set prevents delays at customs, installation and audit.
Require safety documentation covering machine safeguards, interlocks, emergency stops, lockout procedures and any operating restrictions. Define whether the supplier provides a risk assessment for the equipment and whether it covers the integrated line or only individual machines. State the language required for safety labels and warnings, and whether replacement labels are supplied. Where a process involves extraction, chemicals or elevated temperatures, require the relevant handling and protective documents. Safety documentation protects people and reduces liability, and it should be treated as a core part of the package rather than an attachment.
Where the process generates waste streams — cleaning solvents, coating overspray, solder dross or packaging — require documentation describing their handling, storage and disposal according to applicable rules. Define whether the supplier provides specifications for the materials used and safety data sheets for chemicals, and in what language. State who is responsible for local environmental permits and records, since this often falls outside the equipment contract. Where a customer requires evidence of material compliance, define which declarations must be retained and for how long. Environmental records are easy to overlook at handover and expensive to reconstruct later.
Training is only fully delivered when its content is preserved as reusable material and a record exists of who was trained. This part of the package converts a one-time event into a lasting capability, and it should be specified with the same detail as the equipment documents. Tie the training records to the factory's staffing plan, so that the roles requiring training are identified and covered.
Require the training materials used during commissioning — presentations, handouts, exercises and any video recordings — in electronic form and in the language your team uses. Define whether the supplier grants permission to reuse these materials for internal training of new staff, which is often the most valuable aspect of having them. State whether materials cover operation, maintenance, programming and quality, or only a subset. Where practical, ask for short task-based videos of procedures that are hard to describe in text. Reusable training material reduces dependence on the original trainer and keeps knowledge in the plant.
Require a record of who attended each training session, the topics covered, the duration and the trainer, signed or confirmed by both sides. Where competency was assessed, require the assessment results and the criteria used. Define who maintains these records after handover and how they are used when new staff join. Where a train-the-trainer arrangement was agreed, record who was designated as the internal trainer and what they were trained to deliver. Attendance and competency records turn training from a verbal claim into evidence that the team can run the plant.
Require a record of structured knowledge-transfer sessions beyond formal training — for example, walkthroughs of specific faults, process decisions made during commissioning, or supplier explanations of design choices. Define whether these are documented as meeting notes and where they are stored. Require a clear record of post-handover contacts: who to approach for support, the scope of the support period, response expectations and escalation paths. Where the supplier has local representatives, record their details and responsibilities. These records ensure that knowledge does not leave with the installation team when it demobilises.
Configuration backups and machine programs. They exist inside controllers and are easy to omit from a document list, yet without them a controller failure can cost weeks of tuning. Require editable backups and programs for every product in the agreed family as an explicit deliverable.
Electronic form is usually more useful because it can be searched, versioned and copied, but some contexts still require paper or certified originals, such as certificates for authorities. State the format for each document type and where the master copy will be kept. A mixed approach is normal when the requirements are written down.
This should be settled at handover. The supplier creates them during acceptance, but the factory must be able to use, change and control them afterwards. State that the parameters are handed over as controlled documents and define who approves future changes, so the plant is not dependent on the supplier for routine adjustments.
Quotation drawings show the intended layout; as-built drawings show what was actually installed, including every shift made during construction. Only the as-built set is reliable for future work. Require it as a distinct deliverable at the end of installation and check it against the physical plant before acceptance.
Calibration certificates, acceptance reports, inspection specifications, change-control records and training competency records are the most frequently requested. Because audits happen unexpectedly, these should be stored where they can be retrieved quickly and kept current rather than assembled at the last moment.
Before the contract is signed, as part of the scope of supply. A list agreed at the end becomes a negotiation conducted under time pressure, when the supplier has little incentive to add work and the buyer has little leverage. Defining the package early makes it a normal priced part of the project rather than a late request.
content is empty!