{"id":4723,"date":"2026-08-05T05:30:00","date_gmt":"2026-08-05T05:30:00","guid":{"rendered":"https:\/\/aubrikmc.com\/?p=4723"},"modified":"2026-08-05T05:30:00","modified_gmt":"2026-08-05T05:30:00","slug":"column-boom-acceptance-guide","status":"publish","type":"post","link":"https:\/\/aubrikmc.com\/pt\/blog\/column-boom-acceptance-guide\/","title":{"rendered":"Manipuladores de soldagem (coluna e lan\u00e7a): Guia de 11 pontos"},"content":{"rendered":"

A welding manipulator can look complete on a quotation and still arrive with unanswered questions about load, signals, utilities, guarding, factory tests, and final release. This guide is for the people who must close those questions: fabrication and production engineers, welding coordinators, project managers, maintenance leaders, EHS teams, and procurement staff.<\/p>\n

If you first need the equipment basics, read how column-and-boom manipulators work<\/a>. Here, the job starts later. We’ll turn a production duty into comparable supplier responses and witnessed evidence, without inventing a universal payload, deflection tolerance, safety level, or productivity claim.<\/p>\n

Bottom line:<\/strong> accept the documented condition, not the model label. Freeze the load and interfaces, assign every boundary, witness the promised test, retest installation changes, and close the record set before production release.<\/p>\n

Quick Specs: What the Acceptance File Must Control<\/h2>\n
\"Quick<\/figure>\n\n\n\n\n\n\n\n\n\n
Engineering field<\/th>\nMinimum controlled record<\/th>\nWhy a catalogue is not enough<\/th>\n<\/tr>\n<\/thead>\n
Duty case<\/td>\nWorkpiece, joint path, process, duty pattern<\/td>\nOne machine can serve different jobs<\/td>\n<\/tr>\n
Boom-end load<\/td>\nMass, offset, reach, direction, duration<\/td>\nA maximum value does not identify the tested stack<\/td>\n<\/tr>\n
Interfaces<\/td>\nSignal, protocol, owner, fail response, test<\/td>\n\u201cIncluded\u201d does not assign integration responsibility<\/td>\n<\/tr>\n
Utilities and foundation<\/td>\nApproved supplier sheet and site-readiness record<\/td>\nInstalled conditions are site-specific<\/td>\n<\/tr>\n
FAT and SAT<\/td>\nMethod, values, witness, deviation, disposition<\/td>\nA demonstration is not automatically an acceptance test<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

1. Start With the Acceptance Case, Not the Model Name<\/h2>\n
\"1.<\/figure>\n

Before comparing models, write one duty-case paragraph that fixes the workpiece envelope, joint path, welding process, working reach, installed head package, companion motion, operating pattern, and responsibility split. That paragraph becomes the reference for the quote, drawing review, FAT, SAT, and handover.<\/p>\n

Aubrik’s published column-and-boom specification table<\/a> currently lists four model classes: AM-CB-30 at 3 \u00d7 3 m with a stated 150\u2013500 kg range; AM-CB-40 at 4 \u00d7 4 m and 300\u2013800 kg; AM-CB-50 at 5 \u00d7 5 m and 500\u20131,200 kg; and AM-CB-60 at 6 \u00d7 6 m and 800\u20132,000 kg. The listed motion-speed range is 120\u20133,000 mm\/min. These are first-party catalogue values, not independent proof of an installed condition or a complete statement of every custom size the supplier might quote.<\/p>\n

<\/p>\n

Each model row lists the same 120\u20133,000 mm\/min motion range. Neither the 120 mm\/min endpoint nor the 3,000 mm\/min endpoint proves loaded speed stability at the buyer’s required reach; that needs a controlled test condition and agreed tolerance.<\/p>\n

Published Range vs Acceptance Condition Matrix<\/h3>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Catalogue field<\/th>\nCondition still missing<\/th>\nRequired evidence<\/th>\nLimitation<\/th>\n<\/tr>\n<\/thead>\n
3 \u00d7 3 m model class<\/td>\nRequired vertical and horizontal work envelope<\/td>\nApproved layout and duty case<\/td>\nNominal class is not usable stroke proof<\/td>\n<\/tr>\n
4 \u00d7 4 m model class<\/td>\nTorch access and collision envelope<\/td>\nReach study or drawing review<\/td>\nNo universal clearance applies<\/td>\n<\/tr>\n
5 \u00d7 5 m model class<\/td>\nBase, rail, and installation arrangement<\/td>\nApproved general arrangement<\/td>\nSite structure is project-specific<\/td>\n<\/tr>\n
6 \u00d7 6 m model class<\/td>\nAccess, lifting, and service path<\/td>\nSite-readiness inspection<\/td>\nSize can increase integration demands<\/td>\n<\/tr>\n
150\u2013500 kg stated range<\/td>\nInstalled mass and offset<\/td>\nSigned load-stack schedule<\/td>\nFirst-party published data<\/td>\n<\/tr>\n
300\u2013800 kg stated range<\/td>\nMaximum working reach and direction<\/td>\nConfigured FAT test sheet<\/td>\nNo generic deflection value supplied<\/td>\n<\/tr>\n
500\u20131,200 kg stated range<\/td>\nDynamic cable and hose effects<\/td>\nObserved motion record<\/td>\nRouting changes the installed condition<\/td>\n<\/tr>\n
800\u20132,000 kg stated range<\/td>\nFuture allowance and approval owner<\/td>\nContract load revision<\/td>\nAllowance is not free capacity<\/td>\n<\/tr>\n
120\u20133,000 mm\/min<\/td>\nRequired setpoints, path, and loaded condition<\/td>\nTime\/distance or control trace<\/td>\nPublished range is not speed-stability proof<\/td>\n<\/tr>\n
Welding-process compatibility<\/td>\nExact source, head, services, and sequence<\/td>\nInterface register and function test<\/td>\nNot a welding-procedure qualification<\/td>\n<\/tr>\n
Automatic operation<\/td>\nPermissives, limits, alarms, recovery<\/td>\nCause-and-effect witness record<\/td>\nSafety design remains risk-dependent<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

This is the first rule of the 11-Point Quote-to-Arc Acceptance Chain<\/strong>: a published range starts the conversation; the acceptance case defines what must be proved. Even a heavy-duty label remains incomplete until the quoted condition and evidence are fixed.<\/p>\n

2. Freeze the Real Load Stack at Maximum Working Reach<\/h2>\n
\"2.<\/figure>\n

Boom-end capacity documentation should prove the complete installed load at the agreed working reach and motion condition. It should name every item, its mass and offset, the path and duration of the test, the measurement method, the acceptance value, and the people who approve changes.<\/p>\n

Count more than the weld head. A complete schedule may include a slide, torch, wire feeder, flux equipment, seam tracker, camera, brackets, cable carriers, hoses, and an agreed future allowance. A component mounted away from the boom’s reference point can matter differently from the same mass close to it, so offset belongs beside mass.<\/p>\n

What should boom-end capacity documentation prove before acceptance?<\/h3>\n

It should prove five things: the installed stack is complete; each item’s mass and offset are known; the boom is at the agreed maximum working reach; the motion direction and test duration match the duty case; and the measured result meets a contract value. Documentation should identify the drawing and load-schedule revisions, measurement instrument, setup photographs, raw values, witness, deviation status, and approval signatures. Cable and hose routing should match the intended configuration rather than being tied back for convenience. If any field changes after approval, the responsible parties should assess the change and decide whether a repeat test is needed.<\/p>\n

Use a boom-end load calculator<\/a> to organize the stack, not to replace the supplier’s engineering review. ISO 17662:2025<\/a> supports a disciplined approach to calibration, verification, and validation of welding-variable equipment; it does not provide a universal column-and-boom deflection or speed tolerance.<\/p>\n

<\/p>\n

3. Write the Welding Automation Cell Interface Schedule Before Asking for Quotes<\/h2>\n
\"3.<\/figure>\n

An interface schedule should assign every device, signal, utility, and failure response in the welding system to a named party before bids are compared. For each boundary, record direction, normal state, protocol or hardwired condition, permissive, alarm, loss-of-signal response, test owner, and required evidence.<\/p>\n

This register normally touches the manipulator, power source, weld head, seam tracking, operator controls, extraction, flux recovery where applicable, and companion motion. If a positioner or turning roll is involved, link mechanical and control ownership rather than writing \u201csynchronized\u201d with no definition. Adjacent field experience makes the point: a physical connector isn’t enough when the robot or controller can’t interpret the signal.<\/p>\n

Which control-system interfaces must a welding manipulator RFQ define?<\/h3>\n

Define start\/ready signals, welding-source status, motion permissives, emergency and protective-stop interactions, travel limits, seam-tracker enable and fault states, companion-axis commands, extraction or flux-system status, alarms, reset authority, safe recovery, data retention, and the loss-of-communication response. Name whether each point is hardwired or networked, who supplies each side, and who witnesses its test.<\/p>\n

For companion-equipment fundamentals, see the welding rotators and turning rolls guide<\/a>. Different weld processes need different interfaces; this article doesn’t turn SAW, MIG\/GMAW, TIG, cladding, or pipe welding into one generic process recipe.<\/p>\n

4. Define Factory Readiness and Utility Boundaries<\/h2>\n
\"4.<\/figure>\n

Factory readiness is a dated, owned record, not a sentence saying \u201csite by buyer.\u201d It should identify the approved supply characteristics, protective-conductor boundary, air or process-gas interfaces where used, extraction, floor or rail foundation, anchoring, access envelope, lifting route, network connections, and materials needed for dry runs.<\/p>\n

Don’t copy utility values from another project. Ask the selected supplier to issue a controlled utility and installation sheet, then add the site owner, ready date, inspection method, and SAT evidence for every line. Approved layouts should show operating, guarding, service, and removal space as separate needs.<\/p>\n

IEC 60204-1<\/a> provides relevant electrical-equipment-of-machines scope. In the United States, OSHA 1910.212<\/a> also makes guarding and anchoring real acceptance questions. Neither source supplies your site’s voltage, foundation design, extraction duty, or access geometry.<\/p>\n

<\/p>\n

5. Turn Safety Functions Into Witnessed Tests<\/h2>\n
\"5.<\/figure>\n

A witnessed safety test names the function, initiating condition, expected safe response, reset and restart rule, witness, result, and deviation owner. Its contents should come from the applicable risk assessment and integrated-cell design, not from a generic checklist copied into every project.<\/p>\n

\n

\u201cOne or more methods of machine guarding shall be provided to protect the operator.\u201d<\/p>\n