Scribd
Upload
19 views1 page

H18

Uploaded by

m.k.rameshkumar1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
19 views1 page

H18

Uploaded by

m.k.rameshkumar1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

11/1/24, 7:56 PM Online PDF Translator | Translate PDFs to any language for free

Material protected by licensed copyright to BR Dem Additional Articles at Table 1 (2 of 2)

Information

92 Class of control function(s) — 186 —

93 Maximum number of reset actions within a time period

94 Number of remote reset actions

H.17.1.4.3

For controls declared as class A, requirements 66, 67, 68, 70, 71, and 72 are exempt. For controls
with software classes B or C, information will be provided only to the segments of the software.
Information about non-safety-related segments will be sufficient to demonstrate that the segments
are not related to safety.

N the software sequence will be documented and, along with the operating sequence requirement
of Table 46, will include a description of the control system philosophy, the control flow, the data
flow, and the times. Data related to safety and safety-related segments of the software sequence,
whose malfunction could identify the requirements of 17, 25, 26, and 27. This identification will
include the operating sequence and may, for example, take the form of a fault tree analysis that will
include the errors from Table H.1 that may lead to non-compliance. The software failure analysis of
hardware in Clause H.27.

Examples of other information that may be adequate for inclusion in the documentation required by
footnotes m, n, o, q, r, and s are: Original specification of the software system, for example:
functional specification, including the restart procedure in case of power loss, — module design,
including the description of equipment interfaces, and the description of user interfaces, — detailed
design, including the description of memory usage, identification of programming codes,
comments, and listing of subroutines, — test specification, — installation, use, and/or maintenance
manuals. The programming documentation must be provided in a programming design language
declared by the Manufacturer.

R Within a control, different classes of software may be applied to different control functions.
Examples of control functions that may include software classes A to C are as follows:

Class A — Examples are room thermostats, humidity controls, lighting controls, timers, time
switches.

Class B — An example is a thermal cut-off.

Class C — Examples are automatic burner controls and thermal controls for closed water heater
systems (non-vented).

The measures that must be declared are those chosen by the manufacturer among the
requirements of H.11.12.1.2 to H.11.12.2.4 inclusive.

T This can be expressed as a time after the execution of a specific software segment.

https://smallpdf.com/translate-pdf#r=translate 1/1

You might also like