{"id":4397,"date":"2026-08-13T07:23:17","date_gmt":"2026-08-13T07:23:17","guid":{"rendered":"https:\/\/zxweldingrobot.com\/?p=4397"},"modified":"2026-08-13T07:23:17","modified_gmt":"2026-08-13T07:23:17","slug":"iso-ts-15066-cobot-welding-safety","status":"publish","type":"post","link":"https:\/\/zxweldingrobot.com\/pt\/blog\/iso-ts-15066-cobot-welding-safety\/","title":{"rendered":"Limites de for\u00e7a ISO\/TS 15066 para soldagem de Cobots: o que o padr\u00e3o realmente exige"},"content":{"rendered":"
\n

Updated:<\/strong> August 13, 2026<\/p>\n

ISO TS 15066 cobot welding safety<\/strong> is not a matter of typing one force number into a robot controller. Defensible welding applications start by identifying every foreseeable contact, classifying the body region and contact type, measuring the applicable force and pressure, and preserving the tested configuration as evidence.<\/p>\n

\nQuick answer<\/strong><\/p>\n

ISO\/TS 15066 provides collaborative-application guidance, including biomechanical limits used for power and force limiting. It does not certify a cobot model, replace the application risk assessment, or control arc radiation, fumes, heat, spatter, electricity, sharp workpieces, or trapping created by the cell.<\/p>\n<\/div>\n

\n\n\n\n\n\n\n\n
Before accepting a contact<\/th>\nEvidence to retain<\/th>\n<\/tr>\n<\/thead>\n
Classify the task and contact<\/td>\nScenario, body region, transient or quasi-static condition, and contact geometry<\/td>\n<\/tr>\n
Select the applicable criteria<\/td>\nStandard edition, project rules, force limit, pressure limit, and assumptions<\/td>\n<\/tr>\n
Test the frozen application<\/td>\nInstrument setup, calibration, raw traces, result, corrective action, and approval<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

What ISO\/TS 15066 Requires, and What It Does Not<\/h2>\n
\"What<\/figure>\n

One common application-risk mistake is treating an industrial standard as a product label. ISO’s catalogue entry for ISO\/TS 15066:2016<\/a> still lists the document as published and current, while its lifecycle stage says it is to be revised. That status does not certify an individual welding cell. <\/p>\n

\n\n\n\n\n\n\n\n\n\n
Document<\/th>\nPractical role in a welding-cobot project<\/th>\nImportant boundary<\/th>\n<\/tr>\n<\/thead>\n
ISO\/TS 15066:2016<\/strong><\/td>\nCollaborative robot-system guidance, including power-and-force-limiting contact criteria<\/td>\nSupplements the broader industrial-robot safety framework; not a cell certificate<\/td>\n<\/tr>\n
ISO 10218-1:2025<\/a><\/strong><\/td>\nRobot-level design and information for integration<\/td>\nRobot conformity does not prove the integrated welding application is safe<\/td>\n<\/tr>\n
ISO 10218-2:2025<\/a><\/strong><\/td>\nApplication and cell integration, commissioning, use, maintenance, and decommissioning<\/td>\nExact adopted editions depend on the project and jurisdiction<\/td>\n<\/tr>\n
ISO\/PAS 5672:2023<\/strong><\/td>\nMethods for measuring and analyzing human-robot contact force and pressure<\/td>\nDoes not identify which hazards or contact scenarios the risk assessment must select<\/td>\n<\/tr>\n
AWS D16.1:2018 and D16.3:2026<\/strong><\/td>\nWelding-specific safety and robotic arc-welding risk-assessment references<\/td>\nUse when applicable to the contract or jurisdiction; do not treat a catalogue summary as the normative text<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
\nStatus check, not a legal conclusion<\/strong><\/p>\n

The 2025 editions of ISO 10218-1<\/a> and ISO 10218-2<\/a> were published in February 2025. Confirm the editions named by the purchaser, risk assessor, local regulator, and conformity route before testing. <\/p>\n<\/div>\n

Within this standards set, the technical specification adds collaborative robot safety guidance while ISO 10218 carries broader safety requirements for industrial robots and their applications. Collaborative operation may also use measures such as a safety-rated monitored stop or speed and separation monitoring; those methods are distinct from power and force limiting, and no cobot safety or safety standard label selects the right method automatically.<\/p>\n

\nTerminology that affects the test<\/strong><\/p>\n

The robot arm, safety functions, end tooling, workpiece, fixture, and human task form one application. That is why industrial-robot application safety cannot be reduced to the arm’s speed and force settings.<\/p>\n<\/div>\n

Normalize RFQ language before choosing a test<\/h3>\n

Specifications often mix robot safety standards, product descriptions, and control-language shorthand. Treat the following phrases as prompts to define scope, edition, evidence, and ownership\u2014not as proof that a requirement applies or that safety compliance has already been established.<\/p>\n

\n\n\n\n\n\n\n\n\n\n
Language found in specifications<\/th>\nQuestion the project must answer<\/th>\n<\/tr>\n<\/thead>\n
\u201crobots and robotic devices,\u201d \u201cindustrial robots and their integration,\u201d \u201ccollaborative robot application,\u201d \u201ccobot cell,\u201d \u201c6-axis articulated robot,\u201d or \u201ccobot payload\u201d<\/td>\nWhich robot, tooling, payload, cell boundary, and human task are actually inside the assessment?<\/td>\n<\/tr>\n
\u201cfunctional safety,\u201d \u201cfunctional safety requirements,\u201d \u201csafety system,\u201d \u201csafety features,\u201d \u201crobot stopping,\u201d or \u201crobot slows or stops\u201d<\/td>\nWhich safety function, operating mode, performance target, validation method, and fault response are required?<\/td>\n<\/tr>\n
\u201csafety enclosures,\u201d \u201csafety laser,\u201d \u201cISO 13855,\u201d or \u201cdistance between the robot and a person\u201d<\/td>\nWhich access or separation hazard is being controlled, and which edition and measured layout support the decision?<\/td>\n<\/tr>\n
\u201cper ISO 12100,\u201d \u201cper ISO 13849-1,\u201d \u201crobot safety standards,\u201d or \u201csafety compliance\u201d<\/td>\nWho confirms applicability, adopted edition, jurisdiction, evidence package, and acceptance authority?<\/td>\n<\/tr>\n
\u201cfour collaborative operation modes,\u201d \u201ccontact with a person,\u201d \u201ccontact between the robot and a person,\u201d \u201cguidance for collaborative robot use,\u201d or \u201cUniversal Robots\u201d<\/td>\nIs the phrase naming an operating method, a contact scenario, generic equipment, or a specific brand\u2014and what application evidence follows from that distinction?<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

7-Node Force-Limit Decision Chain<\/h2>\n
\"7-Node<\/figure>\n

Limits sit at the end of the decision chain, not the beginning. If a team starts with \u201cWhat force number can we enter?\u201d, it has skipped the questions that determine whether contact is acceptable and which criterion applies.<\/p>\n

    \n
  1. Define the human task, including production, loading, teaching, debugging, maintenance, repair, and recalibration.<\/li>\n
  2. Remove avoidable contact by changing the layout, access, fixtures, sequence, or safeguards before trying to justify a contact with a number.<\/li>\n
  3. Identify every moving interface: the arm, torch, wire, cable dress, workpiece, positioner, fixture, and carried part.<\/li>\n
  4. Classify the event by deciding whether the person can recoil from a transient impact or may be trapped in a quasi-static contact.<\/li>\n
  5. Select the body region and geometry because a broad padded surface and a narrow workpiece edge don’t create the same pressure distribution.<\/li>\n
  6. Freeze and reproduce the worst case, recording payload, tool, path, speed, reach, direction, effective mass, fixture, and counter-surface.<\/li>\n
  7. Compare every applicable quantity. Where the selected criteria<\/a> specify force and pressure, both must pass; otherwise redesign the contact or add safeguarding.<\/li>\n<\/ol>\n
    \nTwo-Number Fallacy<\/strong><\/p>\n

    Force and pressure values aren’t universal settings for an entire cell. Each value belongs to a defined contact scenario, body region, contact classification, geometry, test configuration, and edition of the applicable criteria.<\/p>\n<\/div>\n

    Pass-Both Rule for Applicable PFL Contacts<\/h2>\n
    \"Pass-Both<\/figure>\n

    Force describes the overall interaction, while pressure depends heavily on the area and shape over which that force acts. Broad compliant padding can reduce peak pressure without necessarily reducing total force; a narrow torch bracket or workpiece corner can concentrate pressure even when the force reading looks modest.<\/p>\n

    \n

    \u201cAs soon as either the force or the pressure limit is exceeded, the requirements are not fulfilled.\u201d<\/p>\n

    DGUV FB HM-080, guidance for power-and-force-limited robot systems<\/cite>\n<\/p><\/blockquote>\n

    \n\n\n\n\n\n\n\n\n
    Observed result<\/th>\nWhat it proves<\/th>\nDecision<\/th>\n<\/tr>\n<\/thead>\n
    Applicable force passes; pressure fails<\/td>\nEnergy may be controlled, but geometry still concentrates load<\/td>\nNot accepted; change contact shape, padding, clearance, path, or safeguarding<\/td>\n<\/tr>\n
    Pressure passes; applicable force fails<\/td>\nContact is spread out, but total interaction remains excessive<\/td>\nNot accepted; reduce energy, speed, effective mass, or exposure<\/td>\n<\/tr>\n
    Controller force estimate is below a setting<\/td>\nOnly that the controller reported its estimate under that run<\/td>\nInsufficient without scenario-specific contact measurement<\/td>\n<\/tr>\n
    Both applicable quantities pass<\/td>\nTesting confirmed the contact under the frozen conditions<\/td>\nRetain evidence and continue with all other application hazards<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    That qualification matters. NIST’s biomechanical-limits workshop record<\/a> notes that pain onset can be expressed through quantities such as force or normal stress and that impactor shape affects validity. Apply the pass-both rule where the selected PFL criteria set both limits; do not turn it into an unsupported universal statement. <\/p>\n

    \nCopyright and accuracy boundary<\/strong><\/p>\n

    This guide does not reproduce the complete ISO\/TS 15066 Annex A limit table. Select authoritative values from the licensed standard and the editions adopted for the project; avoid generic claims such as \u201c150 N\u201d or \u201c65 N\u201d without the associated body region and contact conditions.<\/p>\n<\/div>\n

    Classify Every Contact With a Contact-Map Test Matrix<\/h2>\n
    \"Classify<\/figure>\n

    Free impacts and trapping events<\/a> aren’t interchangeable. Use this matrix as a planning template, not a prefilled compliance record; replace every row with the application’s real tasks, surfaces, body regions, configurations, criteria, and measurements.<\/p>\n

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    Scenario<\/th>\nLifecycle\/task<\/th>\nContact pair<\/th>\nClass<\/th>\nLikely body region<\/th>\nWorst-case variable<\/th>\nEvidence needed<\/th>\n<\/tr>\n<\/thead>\n
    CM-01<\/td>\nLoading<\/td>\nArm and operator<\/td>\nTransient<\/td>\nHand\/arm<\/td>\nMaximum reachable speed<\/td>\nPeak trace and geometry<\/td>\n<\/tr>\n
    CM-02<\/td>\nLoading<\/td>\nArm and fixture<\/td>\nQuasi-static<\/td>\nHand\/finger<\/td>\nMinimum clearance<\/td>\nForce, pressure, and trapping setup<\/td>\n<\/tr>\n
    CM-03<\/td>\nProduction observation<\/td>\nTorch body and person<\/td>\nTransient<\/td>\nArm\/torso<\/td>\nTool orientation and reach<\/td>\nContact fixture and raw trace<\/td>\n<\/tr>\n
    CM-04<\/td>\nPart removal<\/td>\nHot workpiece and operator<\/td>\nProcess hazard<\/td>\nHand\/arm<\/td>\nPart temperature<\/td>\nThermal control, not a PFL limit<\/td>\n<\/tr>\n
    CM-05<\/td>\nTeaching<\/td>\nArm and fixed structure<\/td>\nQuasi-static<\/td>\nHand\/arm<\/td>\nManual-mode path and speed<\/td>\nMode-specific safeguard record<\/td>\n<\/tr>\n
    CM-06<\/td>\nDebugging<\/td>\nCable dress and person<\/td>\nTransient<\/td>\nUpper body<\/td>\nUnexpected cable sweep<\/td>\nForeseeable-misuse test<\/td>\n<\/tr>\n
    CM-07<\/td>\nTip change<\/td>\nWire\/electrode and hand<\/td>\nSharp-contact hazard<\/td>\nHand\/finger<\/td>\nExposed point and stored energy<\/td>\nElimination or guarding record<\/td>\n<\/tr>\n
    CM-08<\/td>\nMaintenance<\/td>\nAxis and fixture<\/td>\nQuasi-static<\/td>\nHand\/torso<\/td>\nUnexpected motion<\/td>\nEnergy-isolation procedure<\/td>\n<\/tr>\n
    CM-09<\/td>\nRepair<\/td>\nPositioner and technician<\/td>\nCrush\/trap<\/td>\nWhole body<\/td>\nGravity and stored energy<\/td>\nIsolation and blocking method<\/td>\n<\/tr>\n
    CM-10<\/td>\nRecalibration<\/td>\nMoving tool and technician<\/td>\nTransient or quasi-static<\/td>\nTask-specific<\/td>\nTemporary setup<\/td>\nRevised scenario and acceptance result<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
    \nDesign priority<\/strong><\/p>\n

    Don’t normalize foreseeable head or neck contact merely because a table appears to contain a value. Exclude access to severe contacts through layout, clearance, sequencing, interlocks, monitored zones, or other risk controls wherever practicable.<\/p>\n<\/div>\n

    How to Build a Defensible Validation Test<\/h2>\n
    \"How<\/figure>\n

    The contact map defines what a credible test must reproduce: the assessed contact, relevant body response, and worst-case application energy. Controller screenshots can’t show local pressure, trapping geometry, instrument response, or whether the tested program and payload match production.<\/p>\n

      \n
    1. Freeze the bill of configuration.<\/strong> Record the robot, payload, torch, wire, cable dress, workpiece, fixture, positioner, program revision, safety parameters, and cell layout.<\/li>\n
    2. Derive test points from the risk assessment.<\/strong> Convenient points on the arm don’t replace the surfaces a person can actually encounter.<\/li>\n
    3. Select the measurement method.<\/strong> The ISO\/PAS 5672:2023 catalogue<\/a> describes the document’s force-and-pressure test-method scope and device-characteristic scope. <\/li>\n
    4. Match the simulated body response.<\/strong> Document the biofidelic element, contact area, mounting, instrument identity, calibration, and validity for the selected scenario.<\/li>\n
    5. Reproduce the worst case.<\/strong> Test reach, direction, speed, effective mass, stopping behavior, trapping clearance, and counter-surface under the frozen configuration.<\/li>\n
    6. Capture raw evidence.<\/strong> Preserve force and pressure traces, acquisition rate, filtering, repeats, uncertainty, setup photos, and the analysis method.<\/li>\n
    7. Close the loop.<\/strong> If a criterion fails, change the energy, geometry, surface, path, clearance, or safeguarding, then repeat the affected test and approve the final result.<\/li>\n<\/ol>\n

      Nine-record validation handover ledger<\/h3>\n

      A validation result becomes reusable project evidence only when the test record connects the assessed scenario to the approved configuration. The following ledger separates the records needed to reproduce a result from the events that should reopen it.<\/p>\n

      \n\n\n\n\n\n\n\n\n\n\n\n\n\n
      Checkpoint<\/th>\nPass evidence<\/th>\nReopen when<\/th>\n<\/tr>\n<\/thead>\n
      Assessed task<\/td>\nNamed production or non-production activity<\/td>\nA task, access route, or user group changes<\/td>\n<\/tr>\n
      Contact scenario<\/td>\nSurface pair, body region, and trapping condition<\/td>\nGeometry or clearance changes<\/td>\n<\/tr>\n
      Robot setup<\/td>\nRobot, controller, firmware, and safety revision<\/td>\nSoftware, controller, or safety settings change<\/td>\n<\/tr>\n
      End tooling<\/td>\nTorch, adapter, wire, and cable-dress record<\/td>\nTool mass, outline, or routing changes<\/td>\n<\/tr>\n
      Workholding<\/td>\nWorkpiece, fixture, and positioner identification<\/td>\nA part, fixture, or positioner changes<\/td>\n<\/tr>\n
      Motion<\/td>\nProgram, path, speed, reach, and direction<\/td>\nProgramming or production rate changes<\/td>\n<\/tr>\n
      Instrument setup<\/td>\nDevice identity, calibration, mounting, and filter record<\/td>\nInstrument or analysis method changes<\/td>\n<\/tr>\n
      Measured result<\/td>\nRaw traces, repeats, uncertainty, and pass\/fail decision<\/td>\nA repeat is invalid or a criterion changes<\/td>\n<\/tr>\n
      Approval<\/td>\nNamed reviewer, open actions, residual risks, and release date<\/td>\nAn open action or change-control trigger is activated<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
      \nMeasurement note<\/strong><\/p>\n

      DGUV practice guidance discusses a fixed measuring system and at least 1 kHz acquisition for signals up to 100 Hz, with defined filtering. Treat that as attributed practice guidance, not as a fabricated quotation from ISO\/TS 15066, and use the method required by the project’s licensed documents and test plan. <\/p>\n<\/div>\n

      A Passing Contact Test Does Not Make Welding Safe<\/h2>\n
      \"A<\/figure>\n

      Power and force limiting addresses assessed human-robot contact. Beyond that test plan, welding introduces a second hazard layer, so the risk assessment must independently control the arc, fumes, electrical energy, heat, spatter, sharp wire and workpiece edges, fixtures, positioners, cylinders, and stored energy.<\/p>\n

      \n\n\n\n\n\n\n\n\n
      PFL evidence can address<\/th>\nPFL evidence cannot establish<\/th>\nSeparate control examples<\/th>\n<\/tr>\n<\/thead>\n
      Measured impact or clamping contact in an assessed scenario<\/td>\nProtection from arc radiation and optical exposure<\/td>\nArc screens, controlled access, personal protective equipment<\/td>\n<\/tr>\n
      Whether applicable force and pressure criteria passed<\/td>\nControl of welding fumes and manganese<\/td>\nProcess selection, local exhaust ventilation, exposure assessment<\/td>\n<\/tr>\n
      Tested geometry and motion configuration<\/td>\nProtection from hot parts, molten spatter, fire, or electricity<\/td>\nThermal barriers, housekeeping, electrical safeguards, hot-work controls<\/td>\n<\/tr>\n
      Residual contact risks named in the dossier<\/td>\nSafety of untested teaching, repair, or maintenance states<\/td>\nMode-specific procedures, isolation, blocking, supervision, and access controls<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

      OSHA’s Technical Manual on industrial robot systems<\/a> separates system hazards, task states, and lifecycle responsibilities. NIOSH likewise treats welding fume and manganese exposure<\/a> as a process-dependent occupational hazard, not a robot contact limit. <\/p>\n

      \nWelding-specific standards layer<\/strong><\/p>\n

      The AWS D16 committee catalogue<\/a> lists D16.1M\/D16.1:2018 for robotic arc-welding safety and D16.3M\/D16.3:2026 for robotic arc-welding risk assessment. Use applicable AWS documents alongside, not instead of, the robot-application risk assessment and contact validation. <\/p>\n<\/div>\n

      Acceptance Evidence and the Change-Control Tripwire<\/h2>\n
      \"Acceptance<\/figure>\n

      Handover should not reduce the result to \u201cthe cobot is compliant.\u201d A useful Acceptance Dossier shows which application configuration and contact scenarios were assessed, how they were tested, what passed, what residual risks remain, and which changes reopen the assessment.<\/p>\n

      \n
      Risk and configuration<\/strong><\/p>\n