{"id":3248,"date":"2026-10-25T01:52:15","date_gmt":"2026-10-25T01:52:15","guid":{"rendered":"http:\/\/ritoks.com\/"},"modified":"2026-10-25T01:52:15","modified_gmt":"2026-10-25T01:52:15","slug":"power-quality-event-incident-report","status":"publish","type":"post","link":"https:\/\/ritoks.com\/cs\/power-quality-event-incident-report\/","title":{"rendered":"Power Quality Event Records: What a Useful Incident Report Contains"},"content":{"rendered":"<h2 class=\"wp-block-heading\">Key takeaways<\/h2>\n<ul class=\"wp-block-list\">\n<li>Identify the actual meter, configuration and measurement point before interpreting an event.<\/li>\n<li>Keep event occurrence time separate from collection, notification and operator response times.<\/li>\n<li>Preserve missing duration or waveform data as missing, not as zero or a fabricated reconstruction.<\/li>\n<li>Save the original exports and document any conversion used in the report.<\/li>\n<li>State observations before hypotheses; matching timestamps alone do not establish root cause.<\/li>\n<\/ul>\n<h2 class=\"wp-block-heading\">Define the incident question before collecting screenshots<\/h2>\n<p class=\"wp-block-paragraph\">A report should begin with the question the investigation can answer. Was a disturbance recorded at a particular feeder? Did an equipment stop occur during the same period? Can records from two locations be compared reliably? These questions require different evidence. Naming the question prevents the report from promising an explanation that the instruments cannot support.<\/p>\n<p class=\"wp-block-paragraph\">Record the incident owner, affected equipment and requested review period. Identify who reported the problem and whether the initiating information was an operator statement, controller log or electrical measurement. An operator&#8217;s description is useful context, but it should not be relabeled as a meter observation. Conversely, a recorded voltage event does not demonstrate that every downstream device stopped.<\/p>\n<p class=\"wp-block-paragraph\">Use a short scope statement such as: \u201cReview the available feeder-meter event records alongside the machine&#8217;s documented stop log.\u201d Add the exclusions. If there is no synchronized upstream measurement, the report cannot directly establish the upstream event sequence. If load status is unavailable, the report cannot determine the machine&#8217;s operating condition merely from a meter alarm.<\/p>\n<p class=\"wp-block-paragraph\">The scope also guides the procurement brief. A buyer needing historical event evidence must ask about recording, retrieval and retention, not just displayed electrical quantities. If the instrument cannot produce a requested file, the report should disclose the limitation rather than substitute a graph from unrelated equipment.<\/p>\n<h2 class=\"wp-block-heading\">Build a minimum event evidence record<\/h2>\n<p class=\"wp-block-paragraph\">The minimum record combines event identity, measurement context, event definition and retrievable evidence. Use the table below as an original report-design checklist. It is not a standardized report form or a specification of any particular meter. Each field should point to an actual document, export or accountable observation.<\/p>\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Report component<\/th>\n<th>What to record<\/th>\n<th>Review question<\/th>\n<\/tr>\n<\/thead>\n<tbody><tr>\n<td>Instrument identity<\/td>\n<td>Model, serial number, firmware and ordered functions<\/td>\n<td>Is the record tied to the installed configuration?<\/td>\n<\/tr>\n<tr>\n<td>Measurement location<\/td>\n<td>Feeder, panel reference and channel mapping<\/td>\n<td>What electrical point does the evidence represent?<\/td>\n<\/tr>\n<tr>\n<td>Event definition<\/td>\n<td>Quantity, channel and applicable trigger configuration<\/td>\n<td>What condition caused this record to be created?<\/td>\n<\/tr>\n<tr>\n<td>Timing<\/td>\n<td>Source timestamps, time basis and synchronization status<\/td>\n<td>Can events from different sources be compared?<\/td>\n<\/tr>\n<tr>\n<td>Magnitude and duration<\/td>\n<td>Available values, units and availability flags<\/td>\n<td>Are missing fields visible?<\/td>\n<\/tr>\n<tr>\n<td>Original evidence<\/td>\n<td>File names, export method and storage location<\/td>\n<td>Can another reviewer reopen the source?<\/td>\n<\/tr>\n<tr>\n<td>Operating context<\/td>\n<td>Equipment log references and attributed observations<\/td>\n<td>What was happening outside the meter?<\/td>\n<\/tr>\n<tr>\n<td>Interpretation<\/td>\n<td>Findings, limitations and next evidence needed<\/td>\n<td>Is the conclusion proportional to the evidence?<\/td>\n<\/tr>\n<\/tbody><\/table><\/figure>\n<p class=\"wp-block-paragraph\">Do not fill a blank with an assumed default. The nominal value used by a trigger, the configured threshold and the actual measured minimum answer different questions. A report that mixes them can appear internally consistent while describing no actual event. Keep each value under its own label and retain the source&#8217;s unit convention.<\/p>\n<p class=\"wp-block-paragraph\">Include the applicable configuration revision. A threshold viewed today may not be the threshold active during the incident. If configuration history is unavailable, say that the present setting was observed after the event and historical applicability remains unconfirmed. This qualification is more useful than presenting an unsupported reconstruction.<\/p>\n<figure data-spectra-id=\"spectra-fac8370e-c249-47cc-8872-f3922a7e040f\" class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1400\" height=\"1050\" src=\"https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-body-01.webp\" alt=\"Evidence index lists device, event, time, file and context\" class=\"wp-image-3246\" srcset=\"https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-body-01.webp 1400w, https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-body-01-300x225.webp 300w, https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-body-01-1024x768.webp 1024w, https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-body-01-768x576.webp 768w, https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-body-01-16x12.webp 16w, https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-body-01-600x450.webp 600w\" sizes=\"auto, (max-width: 1400px) 100vw, 1400px\" \/><figcaption class=\"wp-element-caption\">Original report-design checklist; source identities must come from actual records.<\/figcaption><\/figure>\n<h2 class=\"wp-block-heading\">Keep the several clocks separate<\/h2>\n<p class=\"wp-block-paragraph\">An incident can have multiple timestamps: meter occurrence, server receipt, alarm display, email transmission and operator acknowledgment. These are not interchangeable. For each source, identify what its timestamp represents, its time zone or offset, and the documented synchronization arrangement. Record uncertainty where the clock state was not verified.<\/p>\n<p class=\"wp-block-paragraph\">Preserve original timestamps in the evidence archive. If a working timeline converts them to a common time basis, explain the transformation and retain the original field. Do not silently shift records to make them align. A conversion should make comparison easier without concealing the limits of the original timing information.<\/p>\n<p class=\"wp-block-paragraph\">For example, a hypothetical incident may have a meter event and a controller stop entry that appear adjacent after conversion. The report can state that the available records occur in the same reviewed period. It should not state that the meter event caused the stop unless the additional evidence supports that conclusion. Unknown controller-clock drift remains a real limitation.<\/p>\n<p class=\"wp-block-paragraph\">Ask the equipment owner about clock changes, device restarts and communication interruptions during the period. A missing history is not proof that none occurred. Describe the information source: exported configuration, maintenance record or operator recollection. Attribution lets another reviewer decide how much confidence to place in the timeline.<\/p>\n<h2 class=\"wp-block-heading\">Record event start and end without inventing duration<\/h2>\n<p class=\"wp-block-paragraph\">A duration is meaningful only when its definition and supporting timestamps are known. Schneider Electric&#8217;s FA312845 describes a PME case in which duration is calculated from disturbance-start and disturbance-end records. It also describes how a loss of meter control power can leave only the start record. This is a bounded example, not a universal rule for all event monitors (Schneider Electric, 2017).<\/p>\n<p class=\"wp-block-paragraph\">The report-design implication is to retain availability explicitly. \u201cEnd record not available\u201d is different from \u201cevent ended immediately.\u201d A blank field should not become a zero-duration event through spreadsheet formatting. Check the source export and the software&#8217;s documented treatment of incomplete events before drawing a conclusion.<\/p>\n<p class=\"wp-block-paragraph\">If duration is reported by the device, preserve that field along with its documented meaning. If the investigator calculates a duration from valid source timestamps, label it as calculated and identify those timestamps. Do not merge device-reported duration with a manually estimated operating interruption. The machine downtime and electrical event duration may describe different phenomena.<\/p>\n<p class=\"wp-block-paragraph\">A qualified engineer must determine any changes to instrument power or installation. The report should record the existing arrangement and relevant evidence gaps; it should not turn a documentation checklist into an instruction to rewire the meter. Preserve unresolved duration as an open evidence item until reliable information becomes available.<\/p>\n<h2 class=\"wp-block-heading\">Distinguish a waveform from an alarm or trend<\/h2>\n<p class=\"wp-block-paragraph\">A waveform record is not simply a smoother trend chart. In Schneider Electric&#8217;s PM5500 documentation, waveform capture is explicitly limited to the listed PM5650, PM5760 and PM5761 models, and the records use COMTRADE files. Those features cannot be inferred for another meter from its power-quality label (Schneider Electric, n.d.).<\/p>\n<p class=\"wp-block-paragraph\">When a waveform exists, retain the supplied files together with the relevant channel definitions and instrument configuration. A picture of the trace can support discussion, but it is not a replacement for the original record. Identify the tool and any processing used to create a presentation image. Do not draw an illustrative waveform and present it as measured evidence.<\/p>\n<p class=\"wp-block-paragraph\">When no waveform exists, report the available evidence honestly. An event list may still establish a recorded condition under its documented definition. A periodic trend may provide context. Neither should be relabeled as a waveform or assigned a sampling capability absent from the exact model documentation.<\/p>\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Available evidence<\/th>\n<th>Suitable statement<\/th>\n<th>Statement that needs more evidence<\/th>\n<\/tr>\n<\/thead>\n<tbody><tr>\n<td>Event flag with a timestamp<\/td>\n<td>The device recorded this event type at its stated time<\/td>\n<td>The complete electrical waveform is known<\/td>\n<\/tr>\n<tr>\n<td>Numerical trend export<\/td>\n<td>These logged quantities were available over this period<\/td>\n<td>Every short disturbance was captured<\/td>\n<\/tr>\n<tr>\n<td>Original waveform record<\/td>\n<td>These channels were captured under the documented trigger<\/td>\n<td>The disturbance&#8217;s source and responsibility are established<\/td>\n<\/tr>\n<tr>\n<td>Operator statement<\/td>\n<td>This person reported this equipment behavior<\/td>\n<td>The meter independently recorded that behavior<\/td>\n<\/tr>\n<\/tbody><\/table><\/figure>\n<p class=\"wp-block-paragraph\">This separation makes the report useful even when the available data is incomplete. It also reveals which capabilities must be confirmed before the next equipment purchase.<\/p>\n<figure data-spectra-id=\"spectra-e458e6ef-b0b1-4192-87d1-d25f3e4d10ea\" class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1400\" height=\"1050\" src=\"https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-body-02.webp\" alt=\"Separate event condition, trend quantities and waveform channels as distinct evidence types\" class=\"wp-image-3247\" srcset=\"https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-body-02.webp 1400w, https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-body-02-300x225.webp 300w, https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-body-02-1024x768.webp 1024w, https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-body-02-768x576.webp 768w, https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-body-02-16x12.webp 16w, https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-body-02-600x450.webp 600w\" sizes=\"auto, (max-width: 1400px) 100vw, 1400px\" \/><figcaption class=\"wp-element-caption\">Confirm the exact ordered recording functions; an event timestamp does not itself establish root cause.<\/figcaption><\/figure>\n<h2 class=\"wp-block-heading\">Add operating context without converting it into a diagnosis<\/h2>\n<p class=\"wp-block-paragraph\">Request relevant maintenance, switching and equipment records from their owners. Link each statement to its origin and distinguish recorded facts from recollections. A machine restart log, work order and operator note can explain why a period deserves investigation, but they do not automatically explain an electrical disturbance.<\/p>\n<p class=\"wp-block-paragraph\">Keep an observation column separate from a hypothesis column. \u201cThe controller logged a stop\u201d is an observation if the original log is available. \u201cThe feeder disturbance caused the stop\u201d is a hypothesis requiring a defensible relationship between timing, electrical conditions and equipment behavior. This distinction helps prevent an incident report from becoming an unsupported liability statement.<\/p>\n<p class=\"wp-block-paragraph\">Document competing explanations and missing information briefly. The aim is not to list every theoretical failure. Identify only uncertainties that affect the actual question: unreliable time comparison, incomplete event duration, unclear channel scaling or absence of equipment-state information. Assign a responsible person and a requested evidence item to each.<\/p>\n<p class=\"wp-block-paragraph\">When a specialist subsequently provides an interpretation, retain it as a named review with its scope and evidence references. Avoid editing the original records to match the interpretation. A useful archive should allow a later reviewer to separate the measurements, the original report and subsequent conclusions.<\/p>\n<h2 class=\"wp-block-heading\">Specify recording evidence when selecting the meter<\/h2>\n<p class=\"wp-block-paragraph\">The RITOKS <a href=\"https:\/\/ritoks.com\/cs\/products\/accura-3700-panel-power-quality-meters\/\">Accura 3700 panel power-quality meter page<\/a> lists a family with harmonic and event functions, while requiring confirmation of ordered measurement and recording options. It does not establish every event trigger, duration field, waveform option or export format for an ordered unit. Request those exact documents before treating any function as included (RITOKS, n.d.).<\/p>\n<p class=\"wp-block-paragraph\">A practical request should identify the events the project needs to review, the required channels, the retrieval method and the expected operating environment. Ask the supplier to show the matching function table and a representative export from the proposed configuration. A generic brochure or front-panel photograph is not enough to validate the report workflow.<\/p>\n<p class=\"wp-block-paragraph\">Confirm who retrieves records and where they are stored. Decide how the team will preserve configuration information, incomplete records and operating annotations. These are procurement and handover questions, not promises of automated diagnosis. The desired result is a traceable evidence package that the customer&#8217;s engineer can actually review.<\/p>\n<h2 class=\"wp-block-heading\">\u010casto kladen\u00e9 ot\u00e1zky<\/h2>\n<h3 class=\"wp-block-heading\">Is a screenshot sufficient for an incident report?<\/h3>\n<p class=\"wp-block-paragraph\">Usually it is only a presentation aid. Retain the original available export, device identity, channel context and event definition so another reviewer can verify what the screenshot represents.<\/p>\n<h3 class=\"wp-block-heading\">Should missing duration be entered as zero?<\/h3>\n<p class=\"wp-block-paragraph\">No. Preserve its unavailable status and investigate the documented source fields. A zero value and an incomplete record make different claims.<\/p>\n<h3 class=\"wp-block-heading\">Does an event timestamp establish the cause of a machine stop?<\/h3>\n<p class=\"wp-block-paragraph\">No. It can support a timeline, but causation requires suitable electrical and equipment evidence, with clock uncertainty considered.<\/p>\n<h3 class=\"wp-block-heading\">Does a power-quality meter necessarily provide waveforms?<\/h3>\n<p class=\"wp-block-paragraph\">No. Confirm the exact ordered recording function and export capability. Manufacturer examples from a different model family do not prove the proposed unit has that feature.<\/p>\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n<p class=\"wp-block-paragraph\">A useful incident report is an evidence map: identifiable instruments, understandable event definitions, preserved source records, explicit timing limitations and attributable operating context. It should make the next review easier without promising unsupported root cause or responsibility. Specify the required recording and retrieval functions before purchasing the meter, then keep observations and hypotheses separate throughout the investigation.<\/p>\n<h2 class=\"wp-block-heading\">Literatura<\/h2>\n<ol class=\"wp-block-list\">\n<li>Schneider Electric. (2017, April 6). <em>Why can one not see a duration time for a sag event?<\/em> (FA312845; updated January 22, 2026). <a href=\"https:\/\/www.se.com\/ph\/en\/faqs\/FA312845\/\" target=\"_blank\" rel=\"noopener\">Official FAQ<\/a>.<\/li>\n<li>Schneider Electric. (n.d.). <em>Overview of waveform capture<\/em> (PM5500 user manual, HRB1684301-18). <a href=\"https:\/\/productinfo.se.com\/pm5500\/595e2aa946e0fb0001f715da\/PM5500%20user%20manual\/English\/PM5500SeriesUserManualv02_0000044889.ditamap\/$\/C_WaveformRecordingOverview_0000245732\" target=\"_blank\" rel=\"noopener\">Official documentation<\/a>.<\/li>\n<li>RITOKS. (n.d.). <em>Accura 3700 panel power quality meters<\/em>. <a href=\"https:\/\/ritoks.com\/cs\/products\/accura-3700-panel-power-quality-meters\/\">Product-family documentation<\/a>.<\/li>\n<\/ol>","protected":false},"excerpt":{"rendered":"<p>Organize event definitions, source timestamps, duration availability, original files and operating context without assuming waveform capability or root cause.<\/p>","protected":false},"author":1,"featured_media":3245,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ritoks_resource_detail_renderer":"viox","ritoks_resource_product_cat_term_id":88,"footnotes":""},"categories":[68],"tags":[],"class_list":["post-3248","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-electrical-measurement-monitoring"],"acf":[],"spectra_blocks_featured_image_url":{"thumbnail":{"url":"https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-hero-01-150x150.webp","width":150,"height":150},"medium":{"url":"https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-hero-01-300x169.webp","width":300,"height":169},"medium_large":{"url":"https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-hero-01-768x432.webp","width":768,"height":432},"large":{"url":"https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-hero-01-1024x576.webp","width":1024,"height":576},"full":{"url":"https:\/\/ritoks.com\/wp-content\/uploads\/2026\/10\/power-quality-event-incident-report-hero-01.webp","width":1600,"height":900}},"spectra_blocks_author_info":{"display_name":"RITOKS","avatar_url":"https:\/\/secure.gravatar.com\/avatar\/6d7d0fc73468198f994ab13ef6eb6558c53b6ed1ad86364d5165efe8bdf8eb4a?s=96&d=mm&r=g","author_link":"https:\/\/ritoks.com\/cs\/author\/dazzlingwqbgmail-com\/","description":""},"_links":{"self":[{"href":"https:\/\/ritoks.com\/cs\/wp-json\/wp\/v2\/posts\/3248","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ritoks.com\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ritoks.com\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ritoks.com\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ritoks.com\/cs\/wp-json\/wp\/v2\/comments?post=3248"}],"version-history":[{"count":1,"href":"https:\/\/ritoks.com\/cs\/wp-json\/wp\/v2\/posts\/3248\/revisions"}],"predecessor-version":[{"id":3249,"href":"https:\/\/ritoks.com\/cs\/wp-json\/wp\/v2\/posts\/3248\/revisions\/3249"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ritoks.com\/cs\/wp-json\/wp\/v2\/media\/3245"}],"wp:attachment":[{"href":"https:\/\/ritoks.com\/cs\/wp-json\/wp\/v2\/media?parent=3248"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ritoks.com\/cs\/wp-json\/wp\/v2\/categories?post=3248"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ritoks.com\/cs\/wp-json\/wp\/v2\/tags?post=3248"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}