Special-Purpose Machine Manufacturing: Evidence-Gated Procurement

When a Thai factory commissions a custom special-purpose machine, price and cycle time are only part of the purchase. The buyer also needs a controlled chain of evidence covering requirement interpretation, interfaces with existing equipment, safety validation, software and backup handover, FAT and SAT acceptance, and every change made after acceptance. This guide shows how to compare special-purpose machine manufacturers and procure a machine that the factory can operate, recover and modify without inheriting undocumented risk.

Special-purpose machine manufacturing buys repeatable production capability

A special-purpose machine is designed or integrated for a particular product, process, inspection, transfer or assembly task. A system may still behave like a custom-machine project even when it uses standard robots and modules, because its fixtures, sequence, controls, safeguarding and factory connections are unique.

An order that says only “one automatic assembly machine” does not define repeatable capability. The parties must agree on the workpiece, pass criteria, capacity, changeover, abnormal conditions, operator duties, data, maintenance, training, safety and handover. The procurement deliverable therefore has three inseparable parts:

• the machine, fixtures, controls and software that perform the required work;
• test records, risk work, drawings and configuration evidence showing that the requirements were met; and
• a handover baseline that permits recovery and controlled change after a failure, new variant or personnel transition.

This framing exposes what a low special-purpose machine quotation excludes and whether a prospective manufacturer understands the complete project boundary.

Build the special-purpose machine specification from a URS

A User Requirements Specification, or URS, states what must be achieved and under which conditions. It should not prematurely dictate every design detail. When the buyer defines the product, process, operating conditions and acceptance first, suppliers can propose better technical solutions and identify uncertainties before pricing.

Practical URS and RFQ checklist

A capacity statement such as “units per minute” needs a defined measurement window, product variant, yield treatment, test duration and exclusions. Otherwise quotation and acceptance use different measures. Standards references require the same discipline: identify the applicable scope and edition, required deliverables and responsible assessor instead of listing a standard name without context.

Classify requirements before requesting a quote

Mark each requirement as mandatory, supplier-alternative allowed, optional price, information only or out of scope. Give every requirement a unique identifier and retain that identifier in the design specification, review minutes, FAT, SAT and handover register.

For example, “URS-DATA-014: store serial number, result, timestamp and recipe revision for every completed unit” allows a supplier to ask about storage, communications, retention, retry, time synchronization and failure behavior. It also enables a two-stage test: simulated server communication at FAT and connection to the production MES at SAT.

Interface control closes the gaps between manufacturers and the factory

Custom-machine delays frequently arise at boundaries: who provides the electrical feeder, the workpiece orientation, the stop handshake with an existing conveyor, or the final MES tags? Record these decisions in an Interface Control Document or interface matrix rather than relying on meeting memory.

Add a named owner, due date, input, output, revision and open issue to every important line. Labels such as “customer supply” or “by others” do not establish completion criteria. Responsibility can be transferred only when both sides understand the boundary evidence.

Where standardized machine information is useful, OPC UA for Machinery Part 1 provides common models for identification, components, states, operation modes, counters, monitoring and notifications. It does not make OPC UA mandatory for every custom machine. If selected, specify the profile, tags, certificates, time behavior and failure response in a way the plant can maintain.

Compare special-purpose machine quotations on one deliverable boundary

The lowest total can simply be the offer with the broadest exclusions. A comparison should cover compliance, assumptions, exclusions, buyer supplies, options, schedule gates, payment, acceptance, warranty, documentation, software rights and site work. Return the same clarification list to every bidder and require material answers to appear in a revised quotation.

Manufacturer comparison criteria

Weighted scoring is useful but should not override gate conditions. A mandatory nonconformity, missing owner for safety validation, or software package that cannot be restored may not be offset by a low price. The objective is not to claim every intellectual-property right. It is to secure the use, recovery and modification rights required for business continuity. Source escrow or release conditions may suit a buyer that uses a long-term support model.

An illustrative downtime-impact model

The following is a buyer-created illustrative assumption, not a market benchmark or standard machine cost. Assume good output of 600 units per hour, contribution margin of THB 18 per unit, four hours of downtime, and THB 35,000 for external recovery and revalidation. The impact of one event is:

600 units/hour × THB 18/unit × 4 hours + THB 35,000 = THB 78,200

THB 78,200 is neither a typical downtime cost nor a probability-adjusted expected loss. A real buyer should use its own output, margin, buffers, alternative production, quarantine needs and recovery duration. The formula simply makes backup restoration tests, diagnostics, spares and response time visible as procurement items instead of accessories.

Design review prepares evidence; it is not just drawing approval

Use a requirement traceability matrix to show which design element satisfies every requirement and which test will prove it. Open matters need not be hidden. A project can proceed when each open item has an owner, deadline, impact and controlled interim assumption.

Typical gates include concept, basic design, detailed design, authorization to build, software freeze, FAT readiness and release to ship. Define deliverables and approvers at each gate. Approval means a conscious decision to proceed with identified residual issues; it does not mean that all risk disappeared. Changes after a gate must be evaluated for cost, schedule, safety, quality and retesting.

For safety, ISO 12100:2010 gives a methodology for identifying hazards, estimating and evaluating risk, and reducing risk over relevant machine life-cycle phases. ISO currently lists the 2010 edition as current while noting that a draft is expected to replace it in coming months. The draft must not be presented as a published standard.

ISO 13849-1:2023 provides methodology, requirements and guidance for designing and integrating safety-related parts of control systems, including software. It does not prescribe the safety functions or required performance level for a particular application, and it does not itself provide cybersecurity measures. Competent parties must derive and validate safety functions and PLr from the machine-specific risk assessment and applicable requirements.

For machine electrical equipment, IEC 60204-1:2016+A1:2021 may be an appropriate contract or design reference where applicable. A generic article cannot conclude that every Thai custom-machine project is legally required to be certified to it. Confirm applicability for the factory, machine, contract, customer and authority concerned.

FAT and SAT should answer different questions

Factory Acceptance Testing normally occurs at the supplier before shipment. Site Acceptance Testing occurs after installation in the real plant. They should not be the same checklist performed in two locations. FAT should find everything that can be corrected before shipping; SAT should prove integration conditions available only at the destination.

Record prerequisites, input, expected result, observed result, tolerance, evidence and decision-maker. A deviation needs severity, containment, permanent correction, retest scope and conditions for shipment or operation. Conditional acceptance with an open punch list should name the owner, deadline, payment hold and consequence of non-completion.

Before FAT, the buyer should review the procedure and secure samples, instruments, simulated signals and witnesses. Before SAT, confirm installation, utilities, network, adjacent equipment, materials, operators and quality approvals. This separates preparation delay from machine failure without leaving preparation ownership ambiguous.

The handover package creates a recoverable baseline

SAT is the start of operations, not the end of responsibility. Handover content should support restoration, training, spare procurement, audit and future change. Every file should match the machine actually installed: the as-built state.

Handover items to consider

• as-built mechanical, electrical, pneumatic, fixture, network, I/O and bill-of-material drawings;
• source and environment information for PLC, HMI, robot, vision, drives, safety, and PC applications;
• settings, recipes, user accounts, certificates, device configurations and firmware revisions;
• full backups, restore instructions, required tools, target-hardware conditions and tested restoration evidence;
• licenses for software, libraries, fonts, operating systems, runtimes and hardware keys;
• risk assessment, safety requirements, design basis, verification and validation records;
• manuals and training records for operation, changeover, cleaning, inspection, diagnosis and lockout;
• recommended and initial spares, consumables, criticality, source, lead time and alternatives;
• FAT/SAT procedures, results, deviations, corrections, approvals and traceability matrix; and
• open issues, warranty, support contacts, remote-support rules, history and document register.

Do not use “program ownership” as a catch-all. Address copyright, use, copying, backup, disaster recovery, modification, third-party maintenance, multi-site reuse, generic libraries and confidential information separately. Standard supplier libraries can be distinguished from buyer-specific sequences and recipes. Source files alone are useless if the development environment, compiler revision, license or passwords are missing. Conversely, continuity may be achieved through escrow and release conditions without taking unnecessary supplier intellectual property.

A backup is accepted when it can be restored under defined conditions, not merely when a file exists. Demonstrate restoration at FAT or SAT, check I/O, safety, communications, recipes and history after recovery, and record how to return to the approved baseline. Give each package a revision, creation time, target machine, approval status and hash, plus a controlled repository and access owner.

Include spares and obsolescence in the original quotation

Custom machines may run for years while PLCs, industrial PCs, cameras, drives, sensors, operating systems and libraries are revised or discontinued. Without a bill of materials at quotation stage, the buyer cannot compare the future recoverability of two architectures. Assess critical parts for single-point failure, safety and quality impact, availability, substitutions, configuration effort and revalidation.

A spare-parts register should include manufacturer, model, revision, compatibility, storage, inventory interval, warranty, replacement recommendation and substitute-approval process. “Equivalent permitted” is insufficient when response time, accuracy, communications, material compatibility or software behavior may change. Route substitutions through change control and update drawings, risk work and tests according to impact.

Contract the OT-security and remote-access boundary

Remote supplier support can reduce recovery time, but unmanaged routers, shared passwords, permanent accounts and undocumented modifications introduce risk. NIST SP 800-82 Rev.3 explains that OT cybersecurity must consider performance, reliability and safety. Use it as guidance for structuring requirements, not as a substitute for Thai law.

The RFQ should address asset inventory, network zones, ports and directions, individual accounts, least privilege, possible multifactor authentication, approved connection windows, session records, logs, malware controls, patch approach, backup, recovery and incident contact. Even an air-gapped plant needs rules for service laptops, removable media, introduced software and vendor accounts.

Review safety and cybersecurity interactions. Network isolation, expired certificates, disabled accounts, patches and time drift can affect machine availability, diagnostics, records and systems around safety functions. A generic article cannot select the correct functions or controls for a real machine; machine-specific assessment and accountable approval remain necessary.

Treat Thailand BOI eligibility as a separate, verified scenario

The current Thailand BOI Smart and Sustainable Industry page states that the minimum efficiency-enhancement investment is THB 1 million, excluding land and working capital. Qualifying existing projects may receive a three-year corporate income tax exemption capped at 50% of qualifying efficiency-improvement or business-upgrade investment, excluding land and working capital.

The cap becomes 100% only when machinery linked to or supporting Thailand’s domestic automation industry accounts for at least 30% of the total value of machinery, automation and robotics used or upgraded. Implementation must finish within three years of the promotion-certificate issuance. Application, approval, implementation and tax realization are distinct. Buying a custom machine does not automatically create eligibility; confirm the project, domestic-industry link, value calculation, timing and evidence directly with BOI.

Do not discount the base business case by an assumed incentive. Instead, retain quotation breakdowns, supply information, payment, installation and acceptance evidence that could support an application. Select the technical solution for production, safety, quality and maintainability, then assess the incentive as a separate scenario after its conditions are confirmed.

Manage every post-SAT change against the accepted baseline

After SAT, factories adjust sensors, alarms, recipes, cycle logic, parts, networks and software. A small change can affect quality decisions, safety distance, stopping behavior, data integrity or warranty. When verbal edits are not reflected in drawings, source and backups, the factory loses the definition of “correct” at the next failure.

A change request should record the reason, affected object, current state, proposal, urgency and requester. Review the effects on production, quality, safety, maintenance, IT/OT and contract obligations, plus tests, training, documents and rollback. Implement only after approval in a controlled environment, perform defined regression tests, and release a versioned package. If it fails, return to the approved baseline.

Emergency restoration may compress the procedure, but it must not erase the record. Capture who changed what, when and why, and what was checked. Complete the formal risk review and documentation after stable operation returns. A change closes only when testing, approval, as-built updates, backups, training and communication are complete.

Define the buyer team and contract gates before execution

Even a capable special-purpose machine manufacturer cannot stabilize requirements and acceptance when decision ownership on the buyer side is unclear. Production should own capability and workability, quality should own measurement and decisions, maintenance should own diagnostics and recovery, EHS should own risk and plant rules, IT/OT should own networks and accounts, and purchasing or legal should own contract terms and rights. Requiring everyone to approve everything causes delay, so define who prepares, reviews, approves and receives information for each requirement area. The final decision-maker must be able to resolve conflicting departmental needs by comparing cost, schedule and operational effects without compromising safety or quality.

Define entry readiness and exit completion for each gate instead of measuring governance by meeting count. Entry to a design review could require the current URS, open-item list, layout, proposed I/O, risk-assessment progress and test strategy. Exit should record approved, conditionally approved and rejected matters, the next deliverable, owner and due date. Link decisions and the exact revision reviewed to the document register so an obsolete attachment cannot later circulate as the controlling version.

Connect payment milestones to verifiable deliverables, not just calendar dates. A project may use contract, design approval, FAT acceptance, shipment, SAT acceptance and final-document receipt as stages, but the evidence and exception route at each stage must be explicit. If conditional FAT permits shipment, agree the correction deadline, retest location, allocation of additional cost and condition for releasing retained payment. This is not a penalty mechanism. It keeps known problems visible until they are closed at the appropriate location.

When pricing a specification change, separate material difference from redesign, committed components, software modification, renewed risk review, document revision, FAT or SAT retest and site-schedule effects. Rate cards or a defined calculation method in the original quotation can shorten negotiation after award. A supplier design improvement that meets the requirement equally or better without changing boundaries or acceptance may use a simplified change route. In either case, do not incorporate it into the build before approval.

Language is also part of handover quality. A Thai factory may conduct design discussions in English or Japanese and train operators and maintainers in Thai. The RFQ should define which documents are delivered in which language, whether the source or translation controls, HMI and alarm language, a terminology list, and how later revisions are translated. Do not rely on translation alone for safety-critical meaning. Use common drawing references, part numbers, signal names and test IDs so teams can reconcile the same object across languages.

When checking manufacturer experience, look beyond photographs of completed machines. Ask for experience managing boundaries similar to the current project, such as installation requiring shutdown of an existing line, handshake across equipment from several suppliers, live MES integration, safety-related control, local training and long-term service. Confidentiality may prevent disclosure of customer names or drawings, but the supplier can still explain its division of responsibility, gates, evidence and problem-solving method. Specificity helps the buyer judge whether that management approach can be repeated.

A practical procurement-to-acceptance roadmap

1. Record the process purpose, workpieces, capability, quality and operating constraints in a URS.
2. Assign requirement IDs and acceptance methods; distinguish mandatory, optional, information and excluded items.
3. Use an interface matrix for machine, building, adjacent equipment, data, safety, cyber and document boundaries.
4. Compare manufacturers with the same RFQ and response format; incorporate exceptions and assumptions in revised offers.
5. Trace requirements through design, risk work, build and test evidence at controlled gates.
6. Use FAT to resolve what can be verified before shipment and manage every deviation and retest.
7. Use SAT for site integration with real materials, people, utilities, systems and surrounding risks.
8. Handover as-built documents, source, backups, licenses, spares and training as a recoverable baseline.
9. Route every post-SAT modification through change control.

For projects that include robots, our guide to choosing a robot system integrator in Thailand helps define integration responsibility. The broader schedule and governance risks are covered in automation project failure risks in Thailand.

Conclusion: procure a custom machine through evidence gates

Sound special-purpose machine manufacturing starts with acceptance conditions, not a purchase-order description. A URS defines the intended outcome, interface control assigns boundary ownership, design and risk reviews prepare proof, FAT and SAT remove different uncertainties, and handover establishes a recoverable baseline. Controlled post-SAT changes preserve that evidence even when people or suppliers change.

If you are comparing special-purpose machine manufacturers or defining a URS, RFQ, FAT/SAT plan or MES interface, you can contact TOMAS TECH while the project is still at the planning stage. We can review the available documents and help structure the questions that must be resolved before commitment.

Frequently asked questions about special-purpose machines

What is a special-purpose machine?

It is a machine designed or integrated for a defined product, process, inspection, transfer or assembly. Even with standard robots and modules, unique fixtures, controls, safeguarding and data integration justify custom-project governance. The procurement should include evidence and a recoverable handover package, not just hardware.

How should special-purpose machine quotations be compared?

Give bidders the same URS, boundary matrix, acceptance conditions and response format. Normalize compliance, exceptions, assumptions, exclusions, options, site work, documents, software rights and support. Treat mandatory gaps and missing safety or recovery ownership as gates that price scoring cannot automatically offset.

What should FAT and SAT prove?

FAT should prove machine-level function, capability, quality, fault recovery, safety, simulated interfaces and draft handover before shipment. SAT should prove operation with real materials, people, utilities, adjacent equipment and production systems. Both need prerequisites, expected and observed results, tolerances, deviations, evidence and accountable approval.

Who owns the programs and backups?

The project contract decides. Separate copyright from the rights to use, copy, back up, recover, modify and engage third-party support. Include environment versions, licenses, credentials, restore instructions and a demonstrated restoration. The objective is reliable continuity, not an undefined claim to “all source code.”

How should changes after acceptance be handled?

Store the accepted SAT state as the baseline. Use a recorded request, impact review, approval, controlled implementation, regression testing, versioned release and documentation update. Define rollback before the change and scale retesting to the possible effects on safety, quality, data and warranty.

Primary references

• ISO 12100:2010 — Safety of machinery, risk assessment and risk reduction
• ISO 13849-1:2023 — Safety-related parts of control systems
• IEC 60204-1:2016+A1:2021 — Electrical equipment of machines
• NIST SP 800-82 Rev.3 — Guide to Operational Technology Security
• OPC UA for Machinery Part 1 v1.04.1
• Thailand BOI — Smart and Sustainable Industry