IS0 16484-3:2005 pdf download.Building automation and control systems(BACS)一 Part 3:Functions.
5.3.2.11 Data archiving
Data gathered by the function historical data. described in 5.5.4.3, and other system data can be permanently archived using a data ard’iivWig method, e.g. file server, tape data storage, CD-ROM. For cross-reference see also backup and restore Ii 5.3.2.13.
Performance creria:
1) maximum number, size and types of records managed;
2) if applicable: type of DBMS software and onginal license p.’ovider shall be stated with respect to
copyi’ight laws.
5.3.2.12 Data importiexpod
Data that is intended to be used by a dedicated special system, often a third party or foreign system, shall be made available by the source database. If requWed. Any capability that the data processing device or server station has for Import/export data Is to be clearly specified.
The data format and, e.g.. record type, descnp(ors. texts, delimiter to separate variables are to be specified Performance crifena:
1) import format of data for the data processing device or server station.
2) import format of data for onward transmission to controllersiauton’iation stations:
3) export format of data colected from controllerslautomatlon stations.
5.3.2.13 Backup and restore
At least one complete backup of all software and project specific data shall be given to the responsible user. The way ii which a user can make a full back up and restore of all functions and their configuration data at all relevant levels shall be specified. Backup media to be used shall be specified.
Performance criteria:
Time needed for complete system backup and restoring.
5.3.2.14 Redundancy
Any capability for the use of multiple hardware to automatically overcome the failure of any piece(s) of equipment is to be stated. The requested capability for stand-by operation shall be stated with respect to:
a) power supply;
b) processing unit;
c) mputioutput unit;
d) network interface/access unit and data interface unit:
e) hard disk e.g. RAID level.
Data gathered by the function historical data. described in 5.5.4.3, and other system data can be permanently archived using a data ard’iivWig method, e.g. file server, tape data storage, CD-ROM. For cross-reference see also backup and restore Ii 5.3.2.13.
Performance creria:
1) maximum number, size and types of records managed;
2) if applicable: type of DBMS software and onginal license p.’ovider shall be stated with respect to
copyi’ight laws.
5.3.2.12 Data importiexpod
Data that is intended to be used by a dedicated special system, often a third party or foreign system, shall be made available by the source database. If requWed. Any capability that the data processing device or server station has for Import/export data Is to be clearly specified.
The data format and, e.g.. record type, descnp(ors. texts, delimiter to separate variables are to be specified Performance crifena:
1) import format of data for the data processing device or server station.
2) import format of data for onward transmission to controllersiauton’iation stations:
3) export format of data colected from controllerslautomatlon stations.
5.3.2.13 Backup and restore
At least one complete backup of all software and project specific data shall be given to the responsible user. The way ii which a user can make a full back up and restore of all functions and their configuration data at all relevant levels shall be specified. Backup media to be used shall be specified.
Performance criteria:
Time needed for complete system backup and restoring.
5.3.2.14 Redundancy
Any capability for the use of multiple hardware to automatically overcome the failure of any piece(s) of equipment is to be stated. The requested capability for stand-by operation shall be stated with respect to:
a) power supply;
b) processing unit;
c) mputioutput unit;
d) network interface/access unit and data interface unit:
e) hard disk e.g. RAID level.
