Bosch Praesideo 4.0 - Инструкция (Страница 72)

Praesideo 4.0 en | 82
Bosch Security Systems B.V. IUI-PRAESIDEO_4.0 | V1.0 | 2013.01 Installation and User Instructions
14.5 The storage of programs and data (see also
Annex C)
Praesideo is compliant.
14.5.1 All executable code and data necessary to
comply with this European Standard shall be held in
memory that is capable of continuous, unmaintained,
reliable operation for a period of at least 10 years.
All Praesideo programs (executable code and data) are
stored in Flash EEPROM.
14.5.2 For the program, the following requirements shall
apply:
a
the program shall be held in non-volatile memory,
which can only be written to at access level 4, and
Firmware (i.e. the program) can be replaced using the
File Transfer Application. Using the File Transfer
Application requires access level 4.
b it shall be possible to identify the version reference or
references of the program at access level 3. The
version reference or references shall be in
accordance with the documentation of 14.2.1.
The version of the firmware of the units that have an LCD
(access level 3) is visible on the units and on the
firmware upgrade web page (that can be accessed via
the web interface of the network controller). The version
of the network controller software is visible on the
network controller display and the web start page.
Getting access to the web interface of the network
controller requires access level 3.
14.5.3 For site-specific data, including emergency
message(s), the following requirements shall apply:
a
the alteration of site specific data shall only be
possible at access level 3 or 4;
Alteration of site specific data can only be done via the
web pages offered by the web interface of the network
controller (configuration data) and via the File Transfer
Application (message sets). Getting access to the web
interface of the network controller requires access level
3. Using the File Transfer Application requires access
level 4.
b the alteration of site specific data shall not affect the
structure of the program;
Configuration of the Praesideo system is implemented to
be data-driven and is not part of the program executable.
Also transferring message sets to the Praesideo system
is data-driven and is not part of the program executable.
Therefore alteration of the site specific data does not
affect the structure of the program.
c if stored in read-write memory, there shall be a
mechanism which prevents the memory being written
to during normal operation at access level 1 or 2,
such that its contents are protected during a failure in
program execution;
Site specific data is stored in a Flash EEPROM based
file system. The file system is maintained by the
VxWorks Flash file system manager using a dedicated
cyclic Flash-Write program mechanism.
d It shall be possible to either read or interrogate the
site specific data at access level 2 or 3, or the site
specific data shall be given a version reference that
shall be updated when each set of alterations is
carried out.
Site specific data can be viewed and maintained from the
configuration web interface. Using the web interface
requires access level 3.
e If the site specific data has a version reference, it
shall be possible to identify this at access level 2 or
3.
The site specific data of the Praesideo system does not
have a version reference.
14.6 Monitoring of memory contents Praesideo is compliant.
The contents of the memories containing the site specific
data shall be automatically checked at intervals not
exceeding 1 h. The checking device shall signal a
system fault if a corruption of the memory contents is
detected.
The message store is checked every 100 s using
checksum validation. Upon detecting corruption, a fault
is reported indicating a corrupt message store.
The configuration file is checked at intervals not
exceeding 1 h using checksum validation. Upon
detecting corruption, a fault is reported indicating a
corrupt configuration.
Clause / Requirement Compliance Signature