{"id":5578,"date":"2026-11-20T06:02:58","date_gmt":"2026-11-19T22:02:58","guid":{"rendered":"https:\/\/www.corvelanmag.com\/?p=5578"},"modified":"2026-10-30T13:47:53","modified_gmt":"2026-10-30T05:47:53","slug":"tramp-metal-incident-log","status":"publish","type":"post","link":"https:\/\/www.corvelanmag.com\/fr\/tramp-metal-incident-log\/","title":{"rendered":"Utiliser un registre des incidents li\u00e9s aux m\u00e9taux ind\u00e9sirables pour identifier les sources de contamination en amont"},"content":{"rendered":"\n<style>\n.corvelan-incident{color:#252b31;font-family:inherit;font-size:17px;line-height:1.75;overflow-wrap:break-word}\n.corvelan-incident .article-section,.corvelan-incident .article-intro,.corvelan-incident .article-nav{box-sizing:border-box;margin:0 0 24px;padding:22px;background:#fff;border:1px solid #d6dadd;border-top:4px solid #39434b;border-radius:16px}\n.corvelan-incident h2{font-size:30px;line-height:1.3;margin:0 0 18px;color:#18212b;scroll-margin-top:110px}\n.corvelan-incident h3{font-size:24px;line-height:1.3;margin:26px 0 12px;color:#18212b}\n.corvelan-incident p{margin:0 0 16px}\n.corvelan-incident p:last-child{margin-bottom:0}\n.corvelan-incident ul,.corvelan-incident ol{padding-left:24px;margin:12px 0 20px}\n.corvelan-incident li{margin-bottom:9px}\n.corvelan-incident a{color:#253f50;text-decoration:underline;text-underline-offset:3px}\n.corvelan-incident a:focus-visible{outline:3px solid #253f50;outline-offset:4px}\n.corvelan-incident .article-nav{background:#f4f5f6;border-top-width:1px}\n.corvelan-incident .article-nav ol{margin-bottom:0}\n.corvelan-incident .article-media{display:block;float:none;clear:both;margin:20px 0}\n.corvelan-incident .article-media img{display:block;float:none;max-width:100%;height:auto;margin-inline:auto}\n.corvelan-incident .table-scroll{overflow-x:auto;margin:20px 0;-webkit-overflow-scrolling:touch}\n.corvelan-incident table{border-collapse:collapse;width:100%;min-width:640px;font-size:inherit;line-height:1.6}\n.corvelan-incident th,.corvelan-incident td{padding:13px 14px;text-align:left;vertical-align:top;border:1px solid #d6dadd}\n.corvelan-incident thead th{background:#edf0f2;color:#18212b}\n.corvelan-incident tbody th{font-weight:600}\n.corvelan-incident tbody tr:nth-child(even){background:#f7f8f9}\n.corvelan-incident section{scroll-margin-top:110px}\n@media(max-width:768px){\n.corvelan-incident{font-size:16px}\n.corvelan-incident .article-section,.corvelan-incident .article-intro,.corvelan-incident .article-nav{padding:18px;margin-bottom:18px;border-radius:12px}\n.corvelan-incident .article-section{border-top-width:3px}\n.corvelan-incident h2{font-size:24px}\n.corvelan-incident h3{font-size:20px}\n.corvelan-incident th,.corvelan-incident td{padding:11px 12px}\n}\n<\/style>\n<article class=\"corvelan-incident\">\n<div class=\"article-intro\">\n<p><strong>A tramp metal incident log helps you find upstream contamination sources by linking each confirmed event to the material being fed, the equipment it passed through, and the metal recovered.<\/strong> Record alarms, physical findings and operating conditions separately. Then use repeated patterns to choose an inspection point and use physical evidence to test the suspected cause.<\/p>\n<p>Tramp metal is unwanted metal carried with your process material. Removing one piece protects the next machine; recording where it came from helps prevent the next incident. A shared spreadsheet, paper register or maintenance system can do this job if operators use the same event rules.<\/p>\n<\/div>\n<nav class=\"article-nav\" aria-label=\"Article contents\"><strong>In this guide<\/strong><ol><li><a href=\"#count-incidents\">What should count as one tramp metal incident?<\/a><\/li><li><a href=\"#log-fields\">What should a useful incident log record?<\/a><\/li><li><a href=\"#trace-material\">How do you trace an alarm back to the material source?<\/a><\/li><li><a href=\"#compare-patterns\">Which patterns deserve an upstream inspection first?<\/a><\/li><li><a href=\"#verify-source\">How do you turn a pattern into a supported cause?<\/a><\/li><li><a href=\"#act-on-findings\">What should change after the investigation?<\/a><\/li><li><a href=\"#incident-log-faq\">Tramp metal incident log FAQs<\/a><\/li><\/ol><\/nav>\n<section class=\"article-section\" id=\"count-incidents\">\n<h2>What should count as one tramp metal incident?<\/h2>\n<div class=\"article-media\"><img loading=\"lazy\" src=\"https:\/\/www.corvelanmag.com\/wp-content\/uploads\/2026\/10\/corvelan-conveyor-metal-target-reference-20261030-v1.webp\" alt=\"Metal objects beneath a detector frame on a conveyor belt\" width=\"1200\" height=\"900\" loading=\"lazy\" decoding=\"async\" style=\"display:block;max-width:100%;height:auto;object-fit:contain;\"><\/div>\n<p><strong>Count one incident for a linked contamination occurrence, and keep the number of alarms and recovered pieces in separate fields.<\/strong> Give the incident a unique ID so repeat trips, photographs and maintenance work stay connected.<\/p>\n<p>Suppose the belt trips three times while a crew searches for one bolt. If the same uncleared material caused all three trips, record one incident, three alarms and one recovered piece. If a later load brings another bolt, open a new incident. If the connection is uncertain, keep the records separate and mark the link as suspected.<\/p>\n<ul>\n<li><strong>Confirmed metal:<\/strong> metal was recovered from the affected material or another documented inspection confirmed its presence.<\/li>\n<li><strong>Unresolved alarm:<\/strong> the detector operated, but no metal was recovered and the cause is still open.<\/li>\n<li><strong>Confirmed non-contamination trip:<\/strong> an investigation traced the signal to a belt splice, nearby moving steel or another identified condition.<\/li>\n<li><strong>Planned test:<\/strong> a controlled detector check, recorded separately from production contamination.<\/li>\n<\/ul>\n<p>Do not label every unsuccessful search a false alarm. Small metal can remain hidden in the load, while a repeating belt-related signal can create many trips without new contamination. Keep the original alarm record and update its classification when evidence arrives.<\/p>\n<\/section>\n<section class=\"article-section\" id=\"log-fields\">\n<h2>What should a useful incident log record?<\/h2>\n\n<p><strong>Record enough information to reconnect the alarm with its material source, upstream equipment and physical findings.<\/strong> Put observed facts in one field and the suspected source in another. \u201cCurved steel fragment, 28 mm long\u201d is an observation; \u201cprobably a liner\u201d is a lead to investigate.<\/p>\n<p>Use the following fields as a practical starting form. Operators can enter the immediate facts, while maintenance adds the equipment findings and closes the action.<\/p>\n<div class=\"table-scroll\"><table><thead><tr><th scope=\"col\">Field<\/th><th scope=\"col\">Where the information comes from<\/th><th scope=\"col\">What to enter<\/th><\/tr><\/thead><tbody>\n<tr><th scope=\"row\">Event ID and status<\/th><td>Shared incident register<\/td><td>Unique ID, confirmed\/unresolved\/test classification, related event IDs.<\/td><\/tr>\n<tr><th scope=\"row\">Time and detection point<\/th><td>Operator observation and controller history, if available<\/td><td>Alarm time, clock used, detector\/conveyor ID, shift and reporter. Keep stop and recovery times separate.<\/td><\/tr>\n<tr><th scope=\"row\">Material source<\/th><td>Delivery ticket, loader record, batch sheet or stockpile record<\/td><td>Supplier, delivery\/lot, stockpile or hopper, material type, blend and rework source.<\/td><\/tr>\n<tr><th scope=\"row\">Path through the plant<\/th><td>Line layout and active feed records<\/td><td>Feed route, transfers, screens, crushers or other equipment upstream of this detector.<\/td><\/tr>\n<tr><th scope=\"row\">Operating condition<\/th><td>Production record and detector setup<\/td><td>Belt speed, material depth, throughput when known, moisture change, settings\/program reference and recent test result.<\/td><\/tr>\n<tr><th scope=\"row\">Recovered metal<\/th><td>Retained object and photographs<\/td><td>Bag ID, piece count, dimensions, mass if useful, shape, markings and observed magnetic response. Leave unknown alloy as unknown.<\/td><\/tr>\n<tr><th scope=\"row\">Recent changes<\/th><td>Maintenance work orders and shift handover<\/td><td>Work order, equipment ID, repair time, changed wear parts, belt repairs or material changes.<\/td><\/tr>\n<tr><th scope=\"row\">Response and impact<\/th><td>Operator and maintenance records<\/td><td>Material isolated, metal removed, downtime, restart authorization and any damage found.<\/td><\/tr>\n<tr><th scope=\"row\">Investigation and follow-up<\/th><td>Assigned action owner<\/td><td>Suspected source, evidence needed, action\/due date, repair reference and follow-up result.<\/td><\/tr>\n<\/tbody><\/table><\/div>\n<p>Keep a second, short production record for <strong>all running periods, including those with no incident<\/strong>. Record the source, route, time window and tonnes processed. Without those normal runs, the incident register cannot show whether one source had more contamination or simply supplied more material.<\/p>\n<h3>How should you preserve recovered metal?<\/h3>\n<p><strong>Keep each event\u2019s recovered pieces in a labeled container and photograph them with a scale before their surfaces are changed.<\/strong> Include an overall view and close views of fracture faces, holes, threads or stamped marks. Link the image filenames and container ID to the event.<\/p>\n<p><strong>Before retrieving metal or inspecting guarded equipment, isolate hazardous energy and control stored energy under the site\u2019s lockout procedure.<\/strong> A stopped belt can still move or release trapped material. OSHA\u2019s <a href=\"https:\/\/www.osha.gov\/control-hazardous-energy\" rel=\"nofollow noopener\" target=\"_blank\">hazardous-energy overview<\/a> explains this risk during servicing and clearing work.<\/p>\n<p>Keep pieces from different events separate. Do not grind or discard a fragment before maintenance has compared its shape and dimensions with suspect parts. An authorized, controlled magnetic-response check can help sort pieces, but attraction alone does not identify an alloy or prove which machine shed it.<\/p>\n<\/section>\n<section class=\"article-section\" id=\"trace-material\">\n<h2>How do you trace an alarm back to the material source?<\/h2>\n<p><strong>Work backward from the detector\u2019s alarm time through the actual material path, allowing for travel time, storage and mixing.<\/strong> Match the event to the material that reached the detector, rather than the delivery or loader movement occurring at that same minute.<\/p>\n<p>First compare the detector, production and maintenance clocks. Record any offset and keep the original timestamps. A clock mismatch can make a clean supplier change look like the start of contamination.<\/p>\n<h3>A direct conveyor: work back from the detector time<\/h3>\n<p>For a straight-through conveyor running at constant speed, material travel time is belt-path distance divided by belt speed. Use the distance along the belt from the feed point to the detector, not the straight-line distance across the plant.<\/p>\n<p>For example, assume a feed point is <strong>90 m upstream<\/strong> and the belt runs at <strong>1.5 m\/s<\/strong> without stops. Travel time is 90 \u00f7 1.5 = <strong>60 seconds<\/strong>. An alarm at 10:16:00 points you toward material fed around 10:15:00, after clock offsets are corrected.<\/p>\n<p>If the belt stopped or changed speed, use the recorded movements during that interval. An average speed across the whole shift can assign the event to the wrong feed load. Add the uncertainty to the source window rather than forcing an exact timestamp.<\/p>\n<h3>Hoppers, blends and recirculation need a time window<\/h3>\n<p>A hopper can hold material from several deliveries, and its discharge may mix old and new material. Use fill\/discharge records and observed residence-time information to list the possible sources. Keep the source marked \u201cmixed\u201d or \u201cunresolved\u201d when the records do not separate them.<\/p>\n<p>Map recirculation and return conveyors as well. A piece sent back through the process can trigger another detector or return to the same one. Link those records with the original event where the material path and timing support the connection.<\/p>\n<p>Then narrow the inspection area: which machines and transfer points did the affected material pass after its last documented control point? Include any return stream that joins between that point and the detector. A prior clean check is useful evidence only for the material and detection conditions it actually covered.<\/p>\n<\/section>\n<section class=\"article-section\" id=\"compare-patterns\">\n<h2>Which patterns deserve an upstream inspection first?<\/h2>\n<p><strong>Prioritize patterns that combine a repeatable metal feature with a shared material source, equipment path or recent change.<\/strong> Compare the amount of material processed before deciding which source has the higher incident rate.<\/p>\n<p>For comparable bulk-material runs, use:<\/p>\n<p><strong>Confirmed incidents per 1,000 tonnes = confirmed independent incidents \u00f7 tonnes processed \u00d7 1,000.<\/strong><\/p>\n<p>Keep repeat alarms from the same uncleared event out of the numerator. The denominator must cover the same source, route and time period as those incidents. Count recovered pieces separately when a single incident contains several fragments.<\/p>\n<p>Consider this example with unchanged detector settings and comparable material depth, speed and target checks:<\/p>\n<div class=\"table-scroll\"><table><thead><tr><th scope=\"col\">Feed source<\/th><th scope=\"col\">Confirmed incidents<\/th><th scope=\"col\">Tonnes processed<\/th><th scope=\"col\">Incidents per 1,000 tonnes<\/th><\/tr><\/thead><tbody>\n<tr><th scope=\"row\">Stockpile A<\/th><td>8<\/td><td>8,000 t<\/td><td>1.0<\/td><\/tr>\n<tr><th scope=\"row\">Stockpile B<\/th><td>4<\/td><td>1,000 t<\/td><td>4.0<\/td><\/tr>\n<\/tbody><\/table><\/div>\n<p>A has more incidents in total, but B has four times the observed rate. <strong>Inspect B\u2019s receiving and handling path first<\/strong>, including any equipment used only for B. The next question is whether the metal arrived in that feed or was introduced along that path. These counts set an investigation priority; the physical comparison comes next.<\/p>\n<p>METTLER TOLEDO\u2019s <a href=\"https:\/\/www.mt.com\/gb\/en\/home\/library\/know-how\/product-inspection\/PI-Guides\/metal-detection-guide\/metal-detection-wiki.html\" rel=\"nofollow noopener\" target=\"_blank\">metal detection guide, under Data Analysis and Program Improvement<\/a>, describes using product, shift, test and alarm patterns to target corrective action. For bulk conveyors, adding processed tonnage makes unequal production runs easier to compare.<\/p>\n<div class=\"table-scroll\"><table><thead><tr><th scope=\"col\">Pattern in the log<\/th><th scope=\"col\">First investigation<\/th><th scope=\"col\">Evidence that separates the causes<\/th><\/tr><\/thead><tbody>\n<tr><th scope=\"row\">Similar fragments on one equipment path, across different suppliers<\/th><td>Wear parts, screens and fasteners on that path<\/td><td>Missing material, matching dimensions or fracture features, inspection and work-order history.<\/td><\/tr>\n<tr><th scope=\"row\">Events follow one delivery or stockpile across different paths<\/th><td>Incoming feed and shared handling before the paths split<\/td><td>Retained feed samples, loading records, source photos and metal recovered before downstream equipment.<\/td><\/tr>\n<tr><th scope=\"row\">Events begin after a repair<\/th><td>The repaired equipment and cleanup area<\/td><td>Repair location, removed-part records, missing tools\/fasteners and fragments matching the work.<\/td><\/tr>\n<tr><th scope=\"row\">Trips repeat at one belt position, with no recovered metal<\/th><td>Belt splice, repair fasteners and nearby moving metal<\/td><td>Event timing against belt position and an authorized detector\/conveyor inspection.<\/td><\/tr>\n<\/tbody><\/table><\/div>\n<p>In a spreadsheet, filter out planned tests, group confirmed incidents by source and route, then join their totals to the production-tonnage record. Keep unresolved alarms in a separate view. Review shift differences alongside source, tonnage and operating condition so the busier crew is not mistaken for the cause.<\/p>\n<p>If sensitivity, test method, belt construction or material conditions changed, mark the change and split the comparison there. Better detection can increase recorded finds even while the physical contamination source stays the same.<\/p>\n<\/section>\n<section class=\"article-section\" id=\"verify-source\">\n<h2>How do you turn a pattern into a supported cause?<\/h2>\n<p><strong>Use the pattern to choose an inspection, then connect the recovered metal to a reachable source and check what happens after correction.<\/strong> A supplier name or maintenance date appearing beside several incidents is a starting lead.<\/p>\n<ol>\n<li><strong>Describe the suspected mechanism.<\/strong> Write a specific explanation, such as \u201cthe screen may be shedding wire into this conveyor,\u201d rather than \u201cpoor maintenance.\u201d List another plausible source, such as wire already in the incoming feed.<\/li>\n<li><strong>Compare the physical evidence.<\/strong> Match fragment dimensions, wire diameter, hole spacing, markings or fracture edges with candidate parts. Compare photographs and retained pieces with the equipment in an isolated, safe condition. Color or magnetic attraction alone is too broad for a source match.<\/li>\n<li><strong>Check the material path and timing.<\/strong> The candidate part must have a route into the affected material upstream of the detection point. Match the suspected loss to the work order, inspection history and feed-arrival window.<\/li>\n<li><strong>Correct the identified problem.<\/strong> Replace or secure the damaged part, remove repair debris, change a contaminated handling practice or address the incoming source. Keep the repair finding and removed part linked to the event ID.<\/li>\n<li><strong>Follow comparable production after the change.<\/strong> Record tonnes, source, route, metal features, detector settings and successful target checks. Compare the same fragment category before and after the action, alongside all confirmed incidents and unresolved alarms.<\/li>\n<\/ol>\n<p>For example, imagine several curved fragments share a thickness and hole pattern with an upstream chute liner. An isolated inspection finds a missing section in that liner, and the fragments fit its broken edge. That gives a much stronger source connection than \u201call events happened on night shift.\u201d If later fragments have a different shape, investigate that group separately rather than assigning every future event to the repaired liner.<\/p>\n<p>Large tramp metal can also break into smaller fragments during crushing or milling. METTLER TOLEDO\u2019s <a href=\"https:\/\/www.mt.com\/mt_ext_files\/Editorial\/Generic\/5\/PI-Safeline-Metal-Detection-Guide_Editorial-Generic_1190206474429_files\/MetalDetectionGuide_Preview_1190206474429.pdf\" rel=\"nofollow noopener\" target=\"_blank\">Metal Detection Guide preview, sections 1.1 and 1.3<\/a>, identifies raw materials, maintenance and in-plant processing among contamination sources. Include all three when the recovered pieces do not match the first suspect.<\/p>\n<p><strong>Do not wait for a trend review when a fragment suggests an active equipment failure or another immediate hazard.<\/strong> Contain the affected material and have the equipment assessed before restart. A log supports the response; it does not replace the line\u2019s stop, isolation or product-disposition procedure.<\/p>\n<p>Use clear investigation states: <strong>suspected source<\/strong>, <strong>source supported by physical findings<\/strong>, and <strong>action checked during follow-up<\/strong>. Record what moved the case from one state to the next. With no further events, also record how much comparable material actually ran; a quiet hour after a low-frequency problem gives little follow-up evidence.<\/p>\n<p>If the same fragment returns after a repair, revisit the source match, look for another component of the same design, and examine material held in bins or return loops before the repair. Keep the investigation open until the new finding has an explanation.<\/p>\n<\/section>\n<section class=\"article-section\" id=\"act-on-findings\">\n<h2>What should change after the investigation?<\/h2>\n<p><strong>Turn each supported finding into a named action, a changed control and a follow-up record.<\/strong> Fix the source where possible, and keep detection and removal working while the change is checked.<\/p>\n<p>A wear-related finding may lead to a revised part-inspection task. Repair debris may call for better tool\/fastener accounting and cleanup before startup. Incoming contamination may require a documented discussion with the supplier or a change at receiving. Repeated carryback may require changes to the return-material handling path.<\/p>\n<p>For bulk-conveyor protection, our <a href=\"https:\/\/www.corvelanmag.com\/products\/ljt-a-conveyor-metal-detector\/\">LJT-A conveyor metal detector<\/a> and <a href=\"https:\/\/www.corvelanmag.com\/products\/ljt-e-conveyor-metal-detector\/\">LJT-E conveyor metal detector<\/a> are relevant starting points when unwanted metal threatens downstream machinery. Match the detector and required line response to the target metal, belt construction, material depth, speed and installation. Keep the incident register as a separate plant record unless logging and data interfaces are explicitly included in the supplied control scope.<\/p>\n<p>A useful <strong>tramp metal incident log<\/strong> ends with evidence and an action: what was recovered, which source was supported, what changed, and what comparable production showed afterward. Keep unresolved cases visible and carry their evidence into the next review.<\/p>\n<p>For a conveyor application review, paste a short incident summary into the message on our <a href=\"https:\/\/www.corvelanmag.com\/contact-us\/\">Contact Us page<\/a>. Include the material, recovered-metal dimensions, belt width, speed, normal and maximum material depth, and the alarm\/stop action you need. Those details connect the recurring problem to the detector selection and installation questions.<\/p>\n<\/section>\n<section class=\"article-section faq\" id=\"incident-log-faq\">\n<h2>Tramp metal incident log FAQs<\/h2>\n<h3>What should we record when no metal is found?<\/h3>\n<p><strong>Keep the event as an unresolved alarm and record the search result, affected material and operating condition.<\/strong> Preserve the original time and any repeated trips. If a later inspection identifies a splice, loose structure or electrical issue, update the cause and classification while keeping the original observations.<\/p>\n<h3>Should the same metal passing two detectors create two incidents?<\/h3>\n<p><strong>Keep a detection-point record at each detector and link both to one parent incident when the timing, material path and physical evidence support the connection.<\/strong> Count it once in a plant-level independent-incident total. Count each detector\u2019s response separately when reviewing that detector\u2019s activity. Leave uncertain links marked as suspected.<\/p>\n<h3>Can we compare sources without a belt scale?<\/h3>\n<p><strong>Use a reliable alternative quantity record, or compare operating hours only within similar material and loading conditions.<\/strong> Weighbridge totals or batch weights may supply tonnes if they match the actual route and period. If only hours are known, label the result \u201cincidents per running hour\u201d; do not convert hours to tonnes using a guessed throughput. Collect the missing quantity data before comparing unequal loads by tonnage.<\/p>\n<h3>Is one large fragment more urgent than many small pieces?<\/h3>\n<p><strong>Set urgency from the hazard and evidence of failure, rather than event count alone.<\/strong> One broken wear part may threaten a crusher immediately. Repeated fine fragments may indicate ongoing wear or contamination affecting product quality. Record dimensions, shape, the protected equipment and any damage so maintenance and operations can set the response.<\/p>\n<h3>How long should we keep the log and recovered pieces?<\/h3>\n<p><strong>Set retention around your plant\u2019s traceability requirements, maintenance cycle and the time needed to check recurrence.<\/strong> Keep open-case evidence available until the investigation and follow-up are complete. Link archived photos, work orders and any retained samples so a later event can be compared. Add applicable customer or regulatory retention requirements to the site procedure.<\/p>\n<\/section>\n<\/article>\n<script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What should we record when no metal is found?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Keep the event as an unresolved alarm and record the search result, affected material and operating condition. Preserve the original time and any repeated trips. If a later inspection identifies a splice, loose structure or electrical issue, update the cause and classification while keeping the original observations.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Should the same metal passing two detectors create two incidents?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Keep a detection-point record at each detector and link both to one parent incident when the timing, material path and physical evidence support the connection. Count it once in a plant-level independent-incident total. Count each detector\u2019s response separately when reviewing that detector\u2019s activity. Leave uncertain links marked as suspected.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Can we compare sources without a belt scale?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Use a reliable alternative quantity record, or compare operating hours only within similar material and loading conditions. Weighbridge totals or batch weights may supply tonnes if they match the actual route and period. If only hours are known, label the result \u201cincidents per running hour\u201d; do not convert hours to tonnes using a guessed throughput. Collect the missing quantity data before comparing unequal loads by tonnage.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Is one large fragment more urgent than many small pieces?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Set urgency from the hazard and evidence of failure, rather than event count alone. One broken wear part may threaten a crusher immediately. Repeated fine fragments may indicate ongoing wear or contamination affecting product quality. Record dimensions, shape, the protected equipment and any damage so maintenance and operations can set the response.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How long should we keep the log and recovered pieces?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Set retention around your plant\u2019s traceability requirements, maintenance cycle and the time needed to check recurrence. Keep open-case evidence available until the investigation and follow-up are complete. Link archived photos, work orders and any retained samples so a later event can be compared. Add applicable customer or regulatory retention requirements to the site procedure.\"\n      }\n    }\n  ]\n}\n<\/script>\n","protected":false},"excerpt":{"rendered":"<p>A tramp metal incident log helps you find upstream contamination sources by linking each confirmed event to the material being fed, the equipment it passed through, and the metal recovered. Record alarms, physical findings and operating conditions separately. Then use repeated patterns to choose an inspection point and use physical evidence to test the suspected [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":5624,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5578","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.corvelanmag.com\/fr\/wp-json\/wp\/v2\/posts\/5578","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.corvelanmag.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.corvelanmag.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.corvelanmag.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.corvelanmag.com\/fr\/wp-json\/wp\/v2\/comments?post=5578"}],"version-history":[{"count":1,"href":"https:\/\/www.corvelanmag.com\/fr\/wp-json\/wp\/v2\/posts\/5578\/revisions"}],"predecessor-version":[{"id":5635,"href":"https:\/\/www.corvelanmag.com\/fr\/wp-json\/wp\/v2\/posts\/5578\/revisions\/5635"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.corvelanmag.com\/fr\/wp-json\/wp\/v2\/media\/5624"}],"wp:attachment":[{"href":"https:\/\/www.corvelanmag.com\/fr\/wp-json\/wp\/v2\/media?parent=5578"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.corvelanmag.com\/fr\/wp-json\/wp\/v2\/categories?post=5578"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.corvelanmag.com\/fr\/wp-json\/wp\/v2\/tags?post=5578"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}