{"id":2316,"date":"2026-10-08T18:21:07","date_gmt":"2026-10-08T10:21:07","guid":{"rendered":"https:\/\/www.zishengelectric.com\/?p=2316"},"modified":"2026-10-08T18:21:10","modified_gmt":"2026-10-08T10:21:10","slug":"substation-hmi-mimic-acceptance-epc","status":"publish","type":"post","link":"https:\/\/www.zishengelectric.com\/ru\/substation-hmi-mimic-acceptance-epc.html","title":{"rendered":"Substation HMI Mimic Acceptance for EPC Handover: Equipment Labels, Status Quality and Display Evidence"},"content":{"rendered":"

Substation HMI mimic acceptance checks whether the operator’s graphical view represents the installed equipment, its actual indications and the quality of the underlying information. A neat single-line screen can still contain a wrong bay label, a reversed status or a value that looks current after communications have failed. Those errors need to be found before the screen becomes part of routine operation.<\/p>\n\n\n\n

For EPC handover, the useful outcome is a traceable set of display checks tied to the approved drawings and signal list. This guide focuses on the mimic and its information behavior. It does not provide switching instructions or replace separate protection, interlocking and command-path acceptance.<\/p>\n\n\n\n

Give substation HMI mimic acceptance a controlled baseline<\/h2>\n\n\n\n

Collect the approved single-line diagram, equipment-tag register, signal list, display conventions and HMI screen schedule. Identify the revisions implemented by the integrator. A screenshot cannot be accepted against an informal drawing that differs from the installed station. The first check is whether the display, design documents and physical equipment describe the same arrangement.<\/p>\n\n\n\n

Define the screens included in the package: station overview, bay details, transformer overview, auxiliary systems and any related alarm or measurement views. Record navigation between them. The owner should be able to move from a general indication to the correct equipment detail without relying on an integrator’s explanation of hidden naming conventions.<\/p>\n\n\n\n

SEL’s SCADA and HMI service description<\/a> identifies communication status, power-system data and alarm management as distinct HMI functions. That distinction helps frame acceptance: a correct diagram is only one part of the operator interface, and each associated information function needs a defined scope.<\/p>\n\n\n\n

Keep display approval separate from operational permission<\/h3>\n\n\n\n

An accepted mimic is not permission to energize equipment or operate a breaker. The project must retain its approved commissioning and operating controls. During display verification, use authorized simulation or test methods and make the test boundary explicit. Do not click a live command merely to see whether a symbol changes.<\/p>\n\n\n\n

\"Topology
Match the screen to approved equipment identities and the installed electrical arrangement.<\/figcaption><\/figure>\n\n\n\n

Reconcile topology and equipment labels first<\/h2>\n\n\n\n

Compare the screen with the approved electrical arrangement. Check bus sections, transformer connections, feeder names and equipment identifiers. Verify that the arrangement is understandable at the normal workstation scale. A correct signal attached to the wrong bay symbol can be more misleading than a visibly missing signal.<\/p>\n\n\n\n

Use physical equipment tags as the common reference. Where the HMI uses a short label, document how it relates to the full asset identifier. Confirm that duplicated names are resolved across voltage levels and station areas. Operators should not need to infer which transformer is meant from the position of a small icon.<\/p>\n\n\n\n

Review screen variants and operating configurations included in the scope. A display copied from another project may retain an unused bus connection, spare feeder label or obsolete device. Remove or clearly identify items according to the approved design. An apparently harmless leftover symbol can mislead later troubleshooting.<\/p>\n\n\n\n

Define every status symbol and its data source<\/h2>\n\n\n\n

Create a display-point map connecting each dynamic object to its source signal, address or tag, displayed text, symbol behavior and applicable quality information. The technical implementation may vary by system, but the acceptance record should expose the relationship clearly enough for a reviewer to trace it.<\/p>\n\n\n\n

For switching-device indications, include the states required by the approved design. These may involve open, closed, intermediate, discrepant or invalid conditions, depending on the device and signal arrangement. Do not invent a universal truth table. Obtain the approved interpretation of the actual inputs and verify that the HMI follows it.<\/p>\n\n\n\n

Color alone should not carry the entire meaning. Apply the owner’s approved combination of labels, symbols, legends and other cues so that different conditions remain distinguishable. Test the result at the actual display size, including common navigation views. A legend hidden on a separate engineering screen may not help an operator interpret an unexpected indication.<\/p>\n\n\n\n

Distinguish indication from command feedback<\/h3>\n\n\n\n

A command request, a command acknowledgement and a device-position indication are different events. If the HMI displays them, document which information drives each part of the screen. A successful request should not be presented as proof that the physical device reached the intended position. Command-path verification remains a separate, controlled activity.<\/p>\n\n\n\n

\"Device
A command acknowledgement does not by itself prove the physical device position.<\/figcaption><\/figure>\n\n\n\n

Use a display acceptance matrix<\/h2>\n\n\n\n
Display claim<\/th>Verification evidence<\/th>Typical discrepancy<\/th><\/tr><\/thead>
Correct equipment identity<\/td>Screen object matched to approved tag and drawing<\/td>Copied label points to another bay<\/td><\/tr>
Correct state indication<\/td>Authorized source stimulus and observed symbol state<\/td>Open and closed interpretation reversed<\/td><\/tr>
Trustworthy data quality<\/td>Approved invalid or stale-data case and visible response<\/td>Old value remains apparently healthy<\/td><\/tr>
Correct measurements<\/td>Source quantity, units, scaling and sign checked<\/td>Wrong multiplier or power-flow convention<\/td><\/tr>
Usable navigation<\/td>Overview, detail and alarm destinations checked<\/td>Link opens a similar but incorrect bay<\/td><\/tr>
Controlled final version<\/td>Accepted screen build and configuration index<\/td>Site runs a different revision from the test record<\/td><\/tr><\/tbody><\/table>\n\n\n\n

Record the actual result for each checked object or agreed group. If a representative sample is accepted, explain why it represents the remaining objects and identify the untested coverage. Copying a successful result across all bays can conceal a single mapping error introduced during configuration.<\/p>\n\n\n\n

Verify measurement meaning as well as the displayed number<\/h2>\n\n\n\n

Check the units, scaling, decimal presentation and sign convention of each relevant measurement. The source and screen should agree about whether a quantity is phase-related, line-related, total, instantaneous or accumulated. A plausible number is weak evidence when its meaning is unclear.<\/p>\n\n\n\n

Power-flow direction deserves particular attention at transformer and bus interfaces. Use the project’s agreed reference direction, and make labels consistent between the overview, detailed screen and exported data. Review how negative values are displayed where they are valid. Do not force an expected positive value by changing a sign without engineering approval.<\/p>\n\n\n\n

For transformer accessories, verify tap position, temperature names and any calculated or selected values in the agreed scope. Distinguish a direct measurement from a calculated value or a maximum selected from several channels. The label should tell the operator what is being displayed without promising information that the source does not provide.<\/p>\n\n\n\n

Set the update and stale-data expectations explicitly<\/h3>\n\n\n\n

The acceptance plan should define the required display behavior when updates stop or data become invalid. Numerical response criteria must come from the approved system requirements. A generic expectation such as fast enough is difficult to test, while an arbitrary delay copied from another project may be inappropriate for the installed architecture.<\/p>\n\n\n\n

Check degraded information and recovery<\/h2>\n\n\n\n

Normal operation is only one display condition. Agree controlled cases for unavailable source data, a communication interruption or another relevant quality change. Observe the affected object and any operator notification. The display should behave according to the approved design and should not silently present old information as a fresh, valid state.<\/p>\n\n\n\n

Keep the test boundary clear. Simulating a quality flag at the HMI input proves that display response; it does not demonstrate the whole path from a field device through every gateway. If the project requires end-to-end verification, the test method must cover that wider path under its authorized procedure.<\/p>\n\n\n\n

Also verify restoration. Record whether the correct source values return, the quality indication clears appropriately and associated notifications behave as specified. An integrator’s temporary test value must not remain active after the session. Preserve the final accepted configuration and the record confirming removal of test conditions.<\/p>\n\n\n\n

\"Normal
Verify that unavailable information is recognizable and that the accepted state is restored.<\/figcaption><\/figure>\n\n\n\n

Review navigation and operator interpretation<\/h2>\n\n\n\n

Walk through common information tasks with the owner’s operations representative: identify a transformer, open its detail view, find the associated alarm and return to the station overview. This is a usability check, not an operating drill involving live commands. Record confusing labels or navigation destinations while they are still easy to correct.<\/p>\n\n\n\n

Check whether alarms and symbols use consistent equipment names. Where a detail window shows information from several devices, identify the source of each group. Avoid screens that imply a single healthy state when one contributing source is unavailable. Any summary status needs an approved definition and a traceable relationship to its inputs.<\/p>\n\n\n\n

SEL’s Diagram Builder overview<\/a> describes configurable power-system objects and alarm-screen tools. Such software capabilities do not guarantee the correctness of a particular project screen. The integrator still needs to demonstrate the chosen object behavior, mapping and presentation in the delivered configuration.<\/p>\n\n\n\n

Control corrections and repeat the affected checks<\/h2>\n\n\n\n

Give each discrepancy a screen reference, equipment tag, expected behavior, actual behavior and supporting evidence. This makes it possible to distinguish a display-label correction from a source-mapping or logic change. Different changes can affect different parts of the system and need different review and retest scopes.<\/p>\n\n\n\n

When a shared template is corrected, identify every screen that uses it. A fix for one bay may alter several others. Conversely, a local correction may leave the same defect elsewhere. The integrator should state the change scope, and the acceptance authority should agree what must be verified again before closure.<\/p>\n\n\n\n

Freeze the final screen build, signal configuration and relevant software versions in the handover index. Retain readable exports or screenshots where useful, together with the controlled backup location. Do not place credentials in ordinary test records. The owner’s access process should manage secrets separately from the engineering evidence.<\/p>\n\n\n\n

Use one deliberately awkward display case<\/h3>\n\n\n\n

Before closing the review, choose a case that is easy to misinterpret: two similarly named bays, a negative power value, or an unavailable source with a retained last value. The case should come from the actual design and be applied through an authorized test method. Ask the operations representative to explain what the screen means without prompting from the integrator.<\/p>\n\n\n\n

If the explanation differs from the approved meaning, investigate the label, legend, navigation and data-quality presentation. The problem may be interpretation rather than a faulty source signal. Record the agreed correction and verify it at the workstation scale used in service. A display that looks clear on an engineering laptop may be less clear on the installed screen.<\/p>\n\n\n\n

Retain this check as part of the acceptance record rather than treating it as informal training. It gives the owner evidence that the delivered presentation supports the intended task, while leaving operational decisions within the approved operating procedures.<\/p>\n\n\n\n

Connect mimic acceptance with the wider EPC dossier<\/h2>\n\n\n\n

The transformer SCADA point-to-point test guide<\/a> addresses source-to-destination signal identity. Mimic acceptance adds the operator-facing interpretation of those signals. Keep the records linked so that the reviewer can distinguish a correctly delivered point from a correctly presented meaning.<\/p>\n\n\n\n

The custom engineering interface review<\/a> can coordinate transformer accessory information with the control-system package. Equipment discussions may reference the 110 kV\u2013115 kV power transformer<\/a> and 10 kV distribution transformer<\/a>. HMI functions belong to the agreed project scope and are not automatic features of every transformer offer.<\/p>\n\n\n\n

What should be handed to operations?<\/h3>\n\n\n\n

Provide the accepted screen index, display conventions, source-point map, checked-state records, measurement definitions, discrepancy closures and final configuration references. Include the limitations of any representative testing and the remaining actions accepted by the owner. Training should use the delivered screens and actual equipment names.<\/p>\n\n\n\n

What information is needed for an interface review?<\/h3>\n\n\n\n

Send the single-line diagram, equipment tags, signal list, HMI screen schedule, owner display conventions and commissioning boundaries. Identify the transformer accessory data and control-system parties involved. Substation HMI mimic acceptance is complete when the operator can identify the correct equipment, understand the displayed state and recognize untrustworthy information. Zisheng Electric can review the transformer-side signal scope as part of the agreed EPC package.<\/p>","protected":false},"excerpt":{"rendered":"

An EPC acceptance guide for matching HMI mimic diagrams to installed equipment, verifying displayed states and measurements, and recognizing unavailable information.<\/p>","protected":false},"author":1,"featured_media":2317,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"themepark_post_bcolor":"#f5f5f5","themepark_post_width":"1022px","themepark_post_img":"","themepark_post_img_po":"left","themepark_post_img_re":false,"themepark_post_img_cover":false,"themepark_post_img_fixed":false,"themepark_post_hide_title":false,"themepark_post_main_b":"","themepark_post_main_p":100,"themepark_paddingblock":false,"footnotes":""},"categories":[4],"tags":[290,397,399,207],"class_list":["post-2316","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-epc-handover","tag-hmi-acceptance","tag-scada-data-quality","tag-substation-commissioning"],"metadata":{"_edit_lock":["1791478694:1"],"_thumbnail_id":["2317"],"_edit_last":["1"],"themepark_seo_title":["Substation HMI Mimic Acceptance | EPC Display Checks"],"themepark_seo_description":["Plan substation HMI mimic acceptance with equipment labels, status interpretation, measurement meaning, data-quality checks and controlled handover records."],"themepark_seo_keyword":["substation HMI mimic acceptance, HMI display verification, substation mimic diagram, SCADA data quality, EPC handover evidence"],"catce":["sidebar-widgets4"],"views":["60"]},"medium_url":"https:\/\/www.zishengelectric.com\/wp-content\/uploads\/2026\/10\/c-hmi-featured-300x169.png","thumbnail_url":"https:\/\/www.zishengelectric.com\/wp-content\/uploads\/2026\/10\/c-hmi-featured-150x150.png","full_url":"https:\/\/www.zishengelectric.com\/wp-content\/uploads\/2026\/10\/c-hmi-featured.png","_links":{"self":[{"href":"https:\/\/www.zishengelectric.com\/ru\/wp-json\/wp\/v2\/posts\/2316","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.zishengelectric.com\/ru\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.zishengelectric.com\/ru\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.zishengelectric.com\/ru\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.zishengelectric.com\/ru\/wp-json\/wp\/v2\/comments?post=2316"}],"version-history":[{"count":1,"href":"https:\/\/www.zishengelectric.com\/ru\/wp-json\/wp\/v2\/posts\/2316\/revisions"}],"predecessor-version":[{"id":2321,"href":"https:\/\/www.zishengelectric.com\/ru\/wp-json\/wp\/v2\/posts\/2316\/revisions\/2321"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.zishengelectric.com\/ru\/wp-json\/wp\/v2\/media\/2317"}],"wp:attachment":[{"href":"https:\/\/www.zishengelectric.com\/ru\/wp-json\/wp\/v2\/media?parent=2316"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.zishengelectric.com\/ru\/wp-json\/wp\/v2\/categories?post=2316"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.zishengelectric.com\/ru\/wp-json\/wp\/v2\/tags?post=2316"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}