ERACS Application Guidance Notes ^{Version 3.12.2 : Feature 8265 29/11/2023}

ERACS Application Guidance Notes. An item labelled "Guidance Notes" has been included in the ERACS "Help" menu and provides access to the following guidance notes...

• Arc Flash Worst-Case Multi-Scenario Results and Labels: describes two tools that are provided with ERACS that will enable comparison of arc flash results from a number of scenarios to determine the worst-case incident energy and subsequently produce labels.
• Database, Network and Library Relationship: describes the relationship between ERACS databases, the networks (single-line diagrams) they contain and the libraries employed by the networks.
• ERACS for Administrators: provides some helpful background information about ERACS.
• Export Single-line Diagram: provides guidance on how to export a single-line diagram in Comma-Separated Values (CSV), eXtensible Markup Language (XML) and Scalable Vector Graphics (SVG) formats.
• PV System Modelling: describes how to provide a simplistic representation of a Photovoltaic (PV) system in ERACS, but could equally be used to represent any renewable.
• Neutral Earthing Transformer Modelling: describes how a neutral earthing transformer can be represented in ERACS.

Arc Flash Multi-Scenario Studies ^{Version 3.12.2 : Feature 8260 29/11/2023}

A document that describes the process of producing a set of arc flash warning labels representing the worst-case incident energies from multiple arc flash studies has been produced. Access to that document and the utilities it refers to have been made available in the following areas of ERACS...

• from a popup menu shown when the main Arc Flash calculation button is pressed and then Tools sub-menu.
• from the main Calculate menu's Arc Flash Risk Assessment and then Tools sub-menus.
• from the main Tools menu's Arc Flash sub-menu.
• from the single-line diagram's context menu (accessed by right-clicking an empty area of the diagram) and then Calculate and Arc Flash Risk Assessment and Tools sub-menus.

Updated Reference Library ^{Version 3.12.2 : Feature 8218 29/11/2023}

Models of Siemens' SENTRON 3WA 3200A air circuit breaker and its corresponding ETU600 LSIG trip unit have been added to the ERACS Reference Library.

Protection and Arc Flash Capability ^{Version 3.12.2 : Feature 8207 29/11/2023}

A facility has been included in Protection Coordination studies that enables you to choose a circuit breaker (or bus section) that should ignore its trip signal. During the protection study, should the chosen circuit breaker (or bus section) receive a trip signal, it will be ignored and the circuit breaker will remain closed, thereby simulating a circuit breaker failure. That facility has been extended to Arc Flash studies too. Should a circuit breaker (or bus section) be associated with an enclosure, it is possible to instruct an Arc Flash study to disable the circuit breaker when an arcing fault is applied to the associated enclosure.

Updated Reference Library ^{Version 3.12.2 : Feature 8084 29/11/2023}

Models representing the overcurrent and earth fault functions of Schneider Electric's PowerLogic P5 relay have been added to the ERACS Reference Library.

Arc Flash Risk Assessment module updated to support NFPA 70E-2024 ^{Version 3.12.2 : Feature 8051 29/11/2023}

The Arc Flash Risk Assessment module has been updated in line with NFPA 70E-2024. It is now possible to set the NFPA 70E Edition study parameter to '2024' in the Arc Flash study setup form. The Arc Flash Notes available in the study setup form, plus the PPE Table and Help file available via the Report window and Detail form, have been updated accordingly. The electric shock approach boundaries have been updated, in line with changes made to the source data defined in Table 130.4(E)(a) of NFPA 70E-2024.

Improved Data State (Scenario) Management ^{Version 3.12.2 : Feature 7843 29/11/2023}

Data State (i.e. scenario) management and support have been improved. It is now possible to perform the following actions in the top-level data state of a family tree of states without the need to save the model as a new network. What that means is that actions performed in the top-level state are reflected into the child states.

1. Add an element to the top-level state and it appears in all child states.
2. Delete an element from the top-level state and it is removed from all child states.
3. Edit operation does not force a new data state to be created if the state has child states.
4. It is not possible to perform the following actions in a child state… add, cut, paste & move.