{"id":2024,"date":"2026-08-07T02:00:00","date_gmt":"2026-08-07T02:00:00","guid":{"rendered":"https:\/\/cnfuerte.com\/blog\/surge-arrester-discharge-counter-event-records\/"},"modified":"2026-08-07T02:00:00","modified_gmt":"2026-08-07T02:00:00","slug":"surge-arrester-discharge-counter-event-records","status":"publish","type":"post","link":"https:\/\/cnfuerte.com\/fr\/blog\/surge-arrester-discharge-counter-event-records\/","title":{"rendered":"What Should a Surge Arrester Discharge Counter Record?"},"content":{"rendered":"<div class=\"b2b-article\">\n<p style=\"margin:0 0 16px;line-height:1.7\"><strong>A surge arrester discharge counter can provide an event record for maintenance review, but the count should be read with the location, date, associated equipment, installation context, and model information.<\/strong> It helps a buyer organize evidence for a technical discussion; it does not identify a cause or prove the condition of an arrester by itself.<\/p>\n<figure style=\"margin:26px 0;text-align:center\"><img decoding=\"async\" style=\"max-width:640px;width:100%;height:auto;display:block;margin:0 auto;border-radius:8px\" alt=\"FUERTE lightning surge arrester power distribution context for event record review\" src=\"https:\/\/cnfuerte.com\/wp-content\/uploads\/2026\/07\/lightning-surge-arrester-power-distribution.webp\" \/><\/figure>\n<nav class=\"b2b-toc\" style=\"background:#f5f8fa;padding:16px 20px;border-radius:8px;margin:0 0 24px\">\n<h2 id=\"contents\" style=\"margin:42px 0 14px;scroll-margin-top:96px\">Contents<\/h2>\n<ul style=\"margin:0 0 18px 1.2em;line-height:1.7\">\n<li style=\"margin:0 0 8px\"><a href=\"#part-1-treat-the-count-as-an-event-record\">Part 1. Treat the Count as an Event Record<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-2-keep-the-event-context-with-the-number\">Part 2. Keep the Event Context With the Number<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-3-put-the-record-into-a-maintenance-review\">Part 3. Put the Record Into a Maintenance Review<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-4-build-an-inquiry-package-that-can-be-checked\">Part 4. Build an Inquiry Package That Can Be Checked<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-5-use-existing-arrester-guidance-without-duplicating-it\">Part 5. Use Existing Arrester Guidance Without Duplicating It<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-6-route-a-model-specific-fuerte-inquiry\">Part 6. Route a Model-Specific FUERTE Inquiry<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-7-fit-boundaries-for-counter-records\">Part 7. Fit Boundaries for Counter Records<\/a><\/li>\n<\/ul>\n<\/nav>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-1-treat-the-count-as-an-event-record\">Part 1. Treat the Count as an Event Record<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">A counter reading is most useful when it is treated as a record that prompts a review. The record can show that an event was registered, while the surrounding project evidence explains what should be investigated next.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">For a utility or EPC team, the useful first question is not &#8220;what does this number prove?&#8221; It is &#8220;which asset, event window, and installation context belong to this number?&#8221; That distinction keeps a maintenance log from becoming an unsupported diagnosis.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-2-keep-the-event-context-with-the-number\">Part 2. Keep the Event Context With the Number<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Capture a short, repeatable record whenever a counter is reviewed. A buyer can then ask suppliers, maintenance teams, and project engineers to discuss the same facts rather than different recollections.<\/p>\n<table style=\"width:100%;border-collapse:collapse\">\n<thead>\n<tr>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Record field<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Why it belongs in the file<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Do not assume<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Asset location and equipment tag<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Connects the reading to a defined installation<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">That a count identifies the cause<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Review date and event window<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Preserves timing for the maintenance discussion<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">That one period equals another site<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Arrester and counter model identity<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Lets the supplier check the offered configuration<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">That all counters are interchangeable<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Installation notes and associated equipment<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Gives the engineering team context<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">That an installation is approved<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Follow-up observation<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Separates a recorded event from a conclusion<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">That the counter replaces inspection<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p style=\"margin:0 0 16px;line-height:1.7\">This structure is deliberately simple. It avoids invented thresholds and leaves the project team free to apply its own approved maintenance process.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-3-put-the-record-into-a-maintenance-review\">Part 3. Put the Record Into a Maintenance Review<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">An event record has more value when it is reviewed alongside site observations, relevant protection information, and the equipment documentation available to the project team. That is why a counter should sit inside a broader evidence trail rather than become the sole decision point.<\/p>\n<figure style=\"margin:26px 0;text-align:center\"><img decoding=\"async\" style=\"max-width:640px;width:100%;height:auto;display:block;margin:0 auto;border-radius:8px\" alt=\"FUERTE lightning surge arrester manufacturing inspection for maintenance evidence discussion\" src=\"https:\/\/cnfuerte.com\/wp-content\/uploads\/2026\/07\/lightning-surge-arrester-manufacturing-quality-inspection.webp\" \/><\/figure>\n<p style=\"margin:0 0 16px;line-height:1.7\"><strong>Important:<\/strong> Do not use a discharge-counter reading as automatic replacement advice or as proof of an arrester failure. A responsible technical review needs the installation context, the offered model documentation, and the project&#8217;s own maintenance requirements. <a href=\"https:\/\/electra.cigre.org\/\" rel=\"nofollow noopener\" target=\"_blank\">CIGRE Electra<\/a> publishes technical material that can support broader power-system discussions.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Where a buyer needs the wider commercial evidence list, the <a href=\"https:\/\/cnfuerte.com\/fr\/blog\/mv-surge-arrester-rfq-checklist\/\">MV surge arrester RFQ checklist<\/a> is the better companion. For installation-related questions, keep <a href=\"https:\/\/cnfuerte.com\/fr\/blog\/surge-arrester-grounding-rfq-inputs\/\">surge arrester grounding inputs<\/a> separate from the event-record discussion.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-4-build-an-inquiry-package-that-can-be-checked\">Part 4. Build an Inquiry Package That Can Be Checked<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Send the event record with enough identity and context for a supplier to respond responsibly. The request should invite a model-specific review, not force a supplier to guess from a count alone.<\/p>\n<table style=\"width:100%;border-collapse:collapse\">\n<thead>\n<tr>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Buyer should provide<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Purpose of the field<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Supplier response to request<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Counter and arrester model references<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Establish the actual equipment under discussion<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Confirm whether the offered route should be reviewed<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Clear product and installation photographs<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Help identify the installed arrangement<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Flag any information still needed<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Asset role and application context<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Separate line, transformer, or other project use cases<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Keep the response within the application boundary<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Event record with date and location<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Make the maintenance conversation traceable<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Avoid interpreting an isolated number<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Project standards or acceptance requirements<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Identify project-controlled requirements<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">State what must be verified before quotation<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p style=\"margin:0 0 16px;line-height:1.7\">Buyers should also retain the relevant technical documents. The <a href=\"https:\/\/webstore.iec.ch\/\" rel=\"nofollow noopener\" target=\"_blank\">IEC Webstore<\/a> is a useful starting point for locating applicable standards, but a search result or catalogue reference is not a project approval.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-5-use-existing-arrester-guidance-without-duplicating-it\">Part 5. Use Existing Arrester Guidance Without Duplicating It<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">This page owns the event-record question. It should not be stretched into a second article about arrester materials, grounding, or placement. Those subjects have different evidence needs and different buying decisions.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">For overhead placement context, read <a href=\"https:\/\/cnfuerte.com\/fr\/blog\/line-arresters-overhead-distribution-placement\/\">line arresters for overhead distribution<\/a>. For the wider product family, begin with the <a href=\"https:\/\/cnfuerte.com\/fr\/lightning-arrester\/\">FUERTE lightning arrester range<\/a>. Keeping each page focused helps the buyer reach the appropriate document without repeating an entire selection guide.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-6-route-a-model-specific-fuerte-inquiry\">Part 6. Route a Model-Specific FUERTE Inquiry<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Once the event record is organized, a buyer can ask FUERTE to review whether a <a href=\"https:\/\/cnfuerte.com\/fr\/product\/discharge-counter\/\">Discharge Counter<\/a> route is relevant to the supplied project information. Include the counter identity, arrester identity, application, photographs, and the project&#8217;s required documents.<\/p>\n<figure style=\"margin:26px 0;text-align:center\"><img decoding=\"async\" style=\"max-width:640px;width:100%;height:auto;display:block;margin:0 auto;border-radius:8px\" alt=\"FUERTE lightning surge arrester product options for a model-specific counter inquiry\" src=\"https:\/\/cnfuerte.com\/wp-content\/uploads\/2026\/07\/lightning-surge-arrester-oem-product-options.webp\" \/><\/figure>\n<table style=\"width:100%;border-collapse:collapse\">\n<thead>\n<tr>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Inquiry need<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">FUERTE route<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Boundary<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Discuss event-recording hardware<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\"><a href=\"https:\/\/cnfuerte.com\/fr\/product\/discharge-counter\/\">Discharge Counter<\/a><\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Confirm the offered configuration against project inputs<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Identify an arrester route for review<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\"><a href=\"https:\/\/cnfuerte.com\/fr\/product\/yh5w-6-yh10w-6-surge-arrester\/\">YH5W-6 \/ YH10W-6 Surge Arrester<\/a><\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Do not infer compatibility from the blog alone<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Share an RFQ package<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\"><a href=\"https:\/\/cnfuerte.com\/fr\/contact-us\/\">Contact FUERTE<\/a><\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Include model and application details<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p style=\"margin:0 0 16px;line-height:1.7\">Do not recommend a counter when the buyer needs fault diagnosis, a protection study, installation approval, or an unverified replacement decision. Those cases require the appropriate project and engineering review first.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-7-fit-boundaries-for-counter-records\">Part 7. Fit Boundaries for Counter Records<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Use this article to make an event record comparable and discussable. It is not a substitute for inspection, project standards, manufacturer verification, or a conclusion about equipment condition.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"faq\">FAQ<\/h2>\n<h3 style=\"margin:28px 0 12px\">What does a surge arrester discharge counter record?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">It can provide an event record for maintenance review. Keep the reading with the asset identity, date, location, and installation context.<\/p>\n<h3 style=\"margin:28px 0 12px\">Does a count prove that an arrester has failed?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">No. A count by itself is not a diagnosis. The project team should review the associated evidence and model documentation.<\/p>\n<h3 style=\"margin:28px 0 12px\">Should a counter replace visual inspection?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">No. The record can support a review, but it does not replace the inspection and maintenance process required by the project.<\/p>\n<h3 style=\"margin:28px 0 12px\">Which fields should appear in an inquiry?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">Include counter and arrester model references, application context, photographs, event timing, asset location, and required documents.<\/p>\n<h3 style=\"margin:28px 0 12px\">Can all counters be treated as interchangeable?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">No. Ask for a model-specific review rather than assuming that a counter fits every arrester or installation.<\/p>\n<h3 style=\"margin:28px 0 12px\">Is a discharge counter the same as a protection study?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">No. A counter record and a protection study serve different purposes and should not be substituted for one another.<\/p>\n<h3 style=\"margin:28px 0 12px\">Which FUERTE page should a buyer open first?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">Open the Discharge Counter product route after preparing the inquiry fields, then share the package with FUERTE for review.<\/p>\n<h3 style=\"margin:28px 0 12px\">Does this article approve an installation?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">No. Installation and acceptance requirements remain project-specific and must be verified by the responsible parties.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"references\">References<\/h2>\n<ul style=\"margin:0 0 18px 1.2em;line-height:1.7\">\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/webstore.iec.ch\/\" rel=\"nofollow noopener\" target=\"_blank\">IEC Webstore catalogue<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/electra.cigre.org\/\" rel=\"nofollow noopener\" target=\"_blank\">CIGRE Electra technical journal for power-system context<\/a><\/li>\n<\/ul>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>A surge arrester discharge counter can provide an event record for maintenance review, but the count should be read with the location, date, associated equipment, installation context, and model information. It helps a buyer organize evidence for a technical discussion; it does not identify a cause or prove the condition of an arrester by itself. [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":1982,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_gspb_post_css":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-2024","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":7}},"_links":{"self":[{"href":"https:\/\/cnfuerte.com\/fr\/wp-json\/wp\/v2\/posts\/2024","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cnfuerte.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cnfuerte.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cnfuerte.com\/fr\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/cnfuerte.com\/fr\/wp-json\/wp\/v2\/comments?post=2024"}],"version-history":[{"count":0,"href":"https:\/\/cnfuerte.com\/fr\/wp-json\/wp\/v2\/posts\/2024\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cnfuerte.com\/fr\/wp-json\/wp\/v2\/media\/1982"}],"wp:attachment":[{"href":"https:\/\/cnfuerte.com\/fr\/wp-json\/wp\/v2\/media?parent=2024"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cnfuerte.com\/fr\/wp-json\/wp\/v2\/categories?post=2024"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cnfuerte.com\/fr\/wp-json\/wp\/v2\/tags?post=2024"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}