MCT Nexus ENGINEERING RESOURCE
How to Specify a Custom Machine
A practical guide to defining the process, interfaces, responsibilities and acceptance criteria for a custom automation machine.
Begin with the required result.
A useful machine requirement describes the production result before prescribing a list of components. What enters the equipment? What operation must be performed? What condition must the product meet when it leaves? These questions give a machine builder a clearer starting point than a request for “a robot and a PLC.”
Separate the problem from the preferred solution. For example, a request to automate loading should explain the part, presentation, required placement and production constraints. A specific handling technology may be appropriate, but that decision should follow a review of the task. MCT Nexus uses this information to discuss custom machine development and the engineering scope needed to establish feasibility.
Describe the part and the process range.
Provide drawings, samples or other controlled product information. Identify dimensions and characteristics that affect handling, locating, processing and inspection. Explain the incoming condition, expected variation and the number of product types. A design based on one ideal sample may not address the full production range.
List the process steps in order, including operator actions and material replenishment. Identify which steps are already proven and which need trials. If the machine uses a specialist process, test instrument or tooling system, state who is responsible for validating that method. The machine builder needs to know which performance assumptions are established and which remain open.
Include the required outgoing condition and reject disposition. A part that cannot proceed may need to be segregated, held for review, reworked or retested. Those paths affect handling, operator access, software and traceability.
Define production expectations with their assumptions.
A cycle-time target is more useful when it identifies the product, operation and loading conditions. Distinguish automatic cycle time from the overall production rate that includes loading, changeover, replenishment, inspection and expected interruptions. Specify how performance will be measured and which conditions will apply during acceptance.
Avoid an unsupported number that combines ideal machine speed with real production expectations. If capacity is critical, describe the required product mix, operating pattern and constraints. The supplier can then identify the engineering questions and trials needed before committing to a result.
Changeover deserves its own requirement. Identify the product changes, tooling changes, recipe selection and verification steps. Define which adjustments an operator may make and which are controlled engineering settings. An automated process that is difficult to change over may not meet the actual production need.
Map the equipment and site interfaces.
The machine will interact with people, utilities and other systems. Document the floor space, access routes, utility supplies, upstream and downstream equipment, and the information exchanged with plant systems. Indicate what is customer-supplied and what belongs in the machine package.
For equipment handshakes, define the information needed: readiness, requests, acknowledgments, completion, faults and the response to unavailable equipment. For data interfaces, identify the system owner and the purpose of each record. If a network, database or production system is controlled by another team, include that team in the review.
Site conditions may influence enclosure selection, instrumentation, cable routing and installation planning. Provide the actual environmental and access requirements rather than expecting the supplier to infer them from an industry label.
Assign engineering and protective-design responsibilities.
A custom machine can involve a machine builder, tooling supplier, process specialist, panel builder, controls engineer and the customer’s plant team. The specification should identify who owns each deliverable and interface. Gaps in ownership often become expensive during build or commissioning.
Identify required customer standards, applicable approvals and the process for reviewing hazards and protective measures. State the expected documentation and validation deliverables. A list of standards by itself does not define the work required to demonstrate that the equipment meets the project requirements.
The control panel, electrical design and PLC/HMI scope should be coordinated with the machine requirements. If a certification or third-party inspection is required, establish the delivery arrangement before purchasing or construction begins.
Write acceptance criteria that can be observed.
Each important requirement should have a planned verification method. State the setup, test material, expected response and evidence that will be recorded. Some checks can be completed before shipment; others need the installed utilities and production interfaces. Make that division explicit.
Include abnormal conditions that matter to operation: missing parts, failed devices, interrupted cycles, invalid recipes and unavailable connected equipment. Define the expected response and recovery path. Testing only the normal cycle leaves important behavior unresolved.
The FAT planning guide explains how to organize this work. The acceptance plan should also establish how exceptions are recorded, who approves them and what must be completed before shipment or production use.
Define the handover before the build starts.
Agree on native software files, drawings, configuration records, manuals, parts information and training. Identify file formats, software versions and third-party licensing responsibilities. A machine that runs during acceptance still needs a maintainable technical package after the supplier leaves.
Discuss installation, commissioning, production support and future changes as separate scope items where appropriate. Travel, site access, utilities, test parts and customer personnel are project dependencies. A clear proposal states what is included and what must be provided by others.
A concise starting package
- Product drawings or samples and the required process steps.
- Product variants, production expectations and changeover requirements.
- Equipment layout, utilities and upstream/downstream interfaces.
- Required quality decisions, records and reject handling.
- Customer standards, protective-design responsibilities and approvals.
- Acceptance conditions, handover deliverables and target schedule.
You do not need every answer before speaking with MCT Nexus. Identify what is known, what is assumed and what still needs engineering work. The next step may be a feasibility review, a concept scope or a defined machine proposal. Use the project inquiry checklist to organize the initial discussion.
Discuss your project with MCT Nexus.
Share the equipment, production requirement and target timing. We will review the scope, interfaces and next steps with your team.