Technical Information

30/72-3780-0 EN
Maestro UX

Archiving

Contents:
1 2
2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.7.1 2.7.2 2.7.3 2.7.4 2.7.5 2.8 2.8.1 2.8.2 2.8.3 2.8.4 2.8.5 2.8.6 2.9 2.9.1 2.9.2

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Operation of the archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Initialization of data carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forced change of write data carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notifying external archive manager of data carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting data carrier index from external archive manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of status of archive devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatic data archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archiving/backup by system dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archiving/backup of the COL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archiving/backup of graphical objects (M1 models) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archiving/backup of BLE data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archiving/backup of Contronic-P data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archiving/backup of recipe configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dearchiving of data by system dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dearchiving of the COL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dearchiving of graphical object data (M1 models) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dearchiving of BLE data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dearchiving of logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dearchiving of Contronic P subsystem data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dearchiving of recipe configuration and result data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dearchiving of applications data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dearchiving of trends. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dearchiving of messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 .7 .8 .8 .8 .9 .9 11 13 13 14 16 16 19 20 20 21 22 23 24 24 24

3
3.1 3.2 3.3 3.4

Configuration of archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configuration of the archive object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of trend archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of message archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of log archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...... ...... ...... ...... 26 29 31 31

4
4.1 4.2 4.3

Archive components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Stations with online archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Station with centralized archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 External archive devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

5
5.1 5.1.1 5.1.2 5.2 5.2.1 5.2.2 5.2.3 5.2.4

Structure and layout of the archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

The online archiv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Layout and function of the online archive for trends . . . . . Layout and function of the online archive for files . . . . . . . External archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Layout and mode of functioning . . . . . . . . . . . . . . . . . . . . Connection of the archive devices. . . . . . . . . . . . . . . . . . . Archive data types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archive/data carrier management . . . . . . . . . . . . . . . . . . . ...... ...... ...... ...... ...... ...... ...... ...... ....... ....... ....... ....... ....... ....... ....... ....... ................... ................... ................... ................... ................... ................... ................... ................... 34 34 35 36 36 36 36 37

5.2.5

Access to the data carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

6 7 8 9

Size monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Evaluation of archived trend data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Archiving in redundancy mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Consistency of the archive - Recovery mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . 44

Page 2

30/72-3780-0 EN

07/1999

1 Introduction
Archiving in Maestro UX is used to save the data and data structures in the system on a secure backup medium for a long period of time. The archived data can be loaded back into the system, for example to carry out subsequent evaluations or to be able to re-establish the last saved status quickly and reliably after a malfunction. A basic distinction is made in the archive data between trend and file histories. Trends are process values of functions collected and archived over time. Sources of trends may be various signal types. Trends can be analyzed with the aid of various applications. It is, for example, possible to display the process values in the curve display, to represent them in the matrix log as value strings, or to pass them on to the control level for more detailed analysis (e.g. characteristic value calculation, lifetimes monitoring). File histories are data stored in the form of files. These are object-related system configuration data (data of the central object list), graphics, data from subsystems, messages, logs (configuration and result data), recipe data (configuration and result data) and data of BLE applications. File histories are used by various functions, such as to represent the message history on the historical message page. A general distinction is made between automatic and user-controlled archiving. Functions for which data can be automatically archived must be configured appropriately. Trends, logs, recipe results and messages are automatically archived. The user-controlled archive data types include Maestro UX configuration data, graphics, data of subsystems (e.g. Contronic P), BLE applications (configuration data and results), and the recipe configuration data. The archive of a Maestro UX system consists of one or more online archives and a centralized archive component. The number of online archives is dictated by the number of workstations in the system. The online archive of a Maestro UX system is scalable, and can be expanded by suitable choice of hardware components (hard disks/number of workstations). There is one centralized archive in a Maestro-UX system. It is responsible for management of the external archive and the external archive devices, and communication with the external archive devices. The external archive devices must be connected to the workstation on which the centralized archive is installed. The external archive comprises an unlimited sequence of external data carriers, and so can be scaled in any way desired. DAT tape drives and magneto-optical drives can be used as external archive devices.

07/1999

30/72-3780-0 EN

Page 3

2 Operation of the archive

The archiving system provides the following services for execution of the archiving tasks: Initialization of data carriers Import of data into the online and external archives Delivery of data from the online and external archives Evaluation of trend histories based on selectable evaluation algorithms Evaluation of file histories based on various criteria Management of data and data carriers

Dialog with the archive is by way of the message page. There all activities, such as archiving and dearchiving of data and actions with the archive devices (insert data carrier, remove data carrier etc.), can be depicted. The additional information on the message always contains the complete name of the data carrier which is to be accessed. The message contains the data carrier reference by way of the data carrier type, the serial number of the type, the archive channel, and the number of archiving and dearchiving jobs waiting for the data carrier type. The general data carrier entrya is: (<data carrier type>|[<ser. no. of data carrier type>]|[<no. of archive channel>])_[<no. of archiving, dearchiving jobs>] Examples: (0|3) (0|3)_4 (0|3|2) Requirements for the data carrier (DC type 0| serial no. 3) Four archiving jobs are waiting for the data carrier (DC type 0 | serial no. 3). A data carrier has been inserted into/removed from the archive device on archive channel 2 (DC type 0 | serial no. 3| archive channel 2). A newly initialized data carrier (-) with no data yet written to it has been inserted into/removed from the archive device (DC type 6 | - | archive channel 1); The serial number is automatically issued for DC type 6 the next time an archiving job is received.

(6|-|1)

Note: When executing actions with the external archive devices it should always be ensured that the correct data carrier is inserted, or that a data carrier is inserted at all. Select "Control Level / Archive" from the menu in the system dialog to move into the Archiving start menu. The system dialog is started by selecting the "wrench" icon from the dialog box. The start menu is shown in Figure 1. The top section is termed the "action window" and is used by all actions which can be executed by the buttons on display (Load, Save, Media Init,...). The action window is initially empty. The bottom section is called the "job window". The job window is used to display all archive jobs. It uses a scrollbar when there are more entries than can be displayed at once due to the size of the window. Any job entered in the list can then be reached by scrolling up and down using the slider. From the system dialog choose: Control Level -> Archive

Page 4

30/72-3780-0 EN

07/1999

Fig. 1: Archiving start menu

Description of fields, Figure 1: Archiving start menu Field A B C D E Return Load Save Media Init Media Import Example of entry Explanation Quit archive dialog and return to system dialog Load archive data Archive and save archiving data Initialize a medium Enter a data carrier in the external archive management table. Function not yet implemented. The entry is made automatically when a Maestro UX data carrier not yet known to the archive is detected in an archive device. Export a data carrier from the management table of the external archive. Function not yet implemented. The export is executed automatically as soon as the maximum number of entries in the management table of an external archive is exceeded. Forced change of medium. In execution of the commande the old medium is disconnected and a new medium of the same data carrier type is entered as the current write data carrier. A new, initialized data carrier of the same data type must have been inserted into the device. Delete all entries in the job window except the active jobs Cancel a selected job. Function not yet implemented. Output of information on the media inserted in the devices 15.01.1997, 11:45:00 COL total Save active User1 Streamer COL Date and start time of the archive job Information text on the job (entered by the user) Type of job to be executed Job status Name of user who executed job Name of archive device used Processed archive data type For display of confi prompts and dialog errors. The button has a dark red background if error messages are waitingn. Select the button to open up the error window and acknowledge the error.

Media Export

Tape change

H I J K L M N O P Q R

Export Cancel job Device Info Time Info text Jobs Status User Device Archive type Error

All actions during ongoing operation which the user can and must execute in connection with the archive are integrated into the system dialog. The functions concerned are: Initialization of data carriers Forced change of write data carriers
30/72-3780-0 EN Page 5

07/1999

Notifying the external archive of data carriers Deleting data carrier index from external archive manager Overview of status of archive devices Archiving/backup of data

The following data types can be archived from the system dialog: BLE application (ARC_BLE_APPL) Graphical objects (ARC_GRAPHICS) Maestro UX objects (ARC_OBJDIR) Contronic P subsystem (ARC_SUBSYSTEM/CP) Recipe confi data (ARC_BATCH/CONFIG)

Dearchiving of data The following data types can be dearchived from the system dialog: BLE application (ARC_BLE_APPL) Graphical objects (ARC_GRAPHICS) Logs (ARC_LOGGING) Maestro UX objects (ARC_OBJDIR) Contronic P subsystem (ARC_SUBSYSTEM/CP) Recipe confi data (ARC_BATCH/CONFIG) Recipe results (ARC_BATC/RESULT)

2.1 Initialization of data carriers

From the system dialog choose: Control Level -> Archive -> Media-Init -> [selection of archive device] -> [selection of data carrier type] Choose 'Media Init' to open up a window (Figure 2) in which the actions to initialize a data carrier can be executed. Initialization of a data carrier can be started at any time. The archiving function checks whether the initialization is permissible. The following reasons cause an initialization to be refused: The data carrier to be initialized is a current write data carrier There is no data carrier in the selected archive device The data carrier to be initialized is write-protected or defective Another job is occupying the selected archive device Initialization is already active

When archive data are first written to an initialized data carrier, the carrier is assigned a serial number which is marked on the carrier. The complete data carrier ID can be ascertained by way of the Device Info function in the system dialog, and should be marked on the data carrier label (see 'Archive/data carrier management').

Page 6

30/72-3780-0 EN

07/1999

Fig. 2: Initialization of data carriers

Description of fields, Figure 2: Initialization of data carriers Field A B Device Data carrier OK Cancel Example of entry Dev1: Storage medium Type 0 Explanation Display/selection box containing connected archive devices Display/selection box containing the available data carrier types (see 'Archive/data carrier management'); For allocation of data carrier types and data types, refer to 'Configuration of the archive object') Confirm selection and execute action Cancel the action and return to the last menu

C D

The system dialog starts the job and flags it as "active" in the job window. As soon as it is flagged as "finished" in the job window, initialization is complete. If an error has occurred, a detailed description of the error can be displayed in the error window of the dialog box. Also, an operator message is sent which can be viewed on the message page.

2.2 Forced change of write data carriers

From the system dialog choose: Control Level -> Archive -> Tape Change -> [selection of data type] Choose 'Tape Change' to force a change of the current data type-specific write data media. A window opens (Figure 3) in which the data carrier type for which a forced change is to be made can be selected. The new, initialized data carrier must already be inserted in an archive device. In the management table of the external archive an entry is generated flagging the current write data carrier as terminated. The serial number of the relevant data carrier type is increased by one and noted on the new write data carrier with the other identifying data (see 'Archive/data carrier management').

07/1999

30/72-3780-0 EN

Page 7

Fig. 3: Forced change of data carriers

Field description, Figure 3: Forced change of data carriers Field A B C Data carrier OK Cancel Example of entry Storage medium Type 0 Explanation Display/selection box containing the available data carrier types (see 'Archive/data carrier management') Confirm selection and execute action Cancel the action and return to the last menu

2.3 Notifying external archive manager of data carriers

Data carriers are automatically detected when inserted. Manual intervention is not necessary.

2.4 Deleting data carrier index from external archive manager

The export is executed automatically as soon as the maximum number of entries in the management table of the external archive is exceeded (see also 'Configuration of the archive object').

2.5 Overview of status of archive devices

From the system dialog choose: Control Level -> Archive -> Device Info Choose 'Device Info' to open up a window (Figure 4) showing the current status of the connected archive devices. The left-hand column displays the installed devices; the right-hand column the data carriers currently inserted.

Page 8

30/72-3780-0 EN

07/1999

Fig. 4: Device information

Field description, Figure 4: Device information Field A B C D Device Data carrier OK Cancel Example of entry Dev1: hgr93_2013412624/ 6/0 Explanation Display box containing the available archive devices Display box containing the data carriers inserted in the corresponding archive device The button cannot be selected in this dialog box Cancel the action and return to the last menu

2.6 Automatic data archiving

Certain data types are automatically archived, without the user having to do anything. In operation it must merely be ensured that the correct data carrier is inserted. The automatic archive data types include: Trends Messages Operational, matrix and message logs

The archiving of data is defined on configuration of the objects concerned (see 'Configuration of archiving').

2.7 Archiving/backup by system dialog

All write or read jobs relating to user-controlled archive data types are started by the user by way of the system dialog. The user-controlled archive data types include: Maestro UX configuration data Graphical objects Configuration data of the subsystem Configuration and result data of BLE applications Configuration and result data of the recipe.

From the system dialog choose: Control Level -> Archive -> Save Choose 'Save' to open up a window (Figure 5) in which the data type to be archived or saved can be selected. The 'Archiving' button is active by default. Saving data differs from archiving of data in that the user can write data of any data type to a data carrier of any type. The allocation is not checked by the archive software. If an error has occurred in the save operation, the job is canceled and - in contrast to the archiving function - is not automatically repeated. It is the responsibility of the user to check whether the archiving job has been properly completed. Archiving: When the 'Archiving' function is selected the data of the selected type are archived onto the current write data carrier of the assigned data carrier type. Archiving of the data and export to the data carrier are registered by relevant messages on the message page. If the necessary data carrier is not inserted, the user is prompted to insert it with the message "Insert data carrier". The system dialog starts the job and flags it as active in the

07/1999

30/72-3780-0 EN

Page 9

job window. A mark in the job window flagging the job as finished indicates that archiving onto the external data carrier has been executed. If the archiving job could not be executed due to an error (e.g. no data carrier inserted), the job is automatically repeated, by cyclical restarts, until it can be processed. Errors are displayed in the error window of the dialog box. The archiving function also sends operator messages which are then available on the message page. If a data carrier is to be produced with a complete backup of the selected data type, the user should check correct execution of the job. This is indicated by the message "Archiving to DC OK", which contains the information text as an item of additional information. Save: Choose the 'Save' function to write the data of the selected data type to to the data carrier inserted in the selected device. The procedure is the same as the manual archiving procedure. But here the option is available to save data of different types on one medium. The system dialog starts the job and marks it as active in the job window. When it is flagged as finished in the job window, the save operation to the external data carrier is executed. If the save operation has been executed successfully the message "Archiving to DC OK" appears, containing the text entered with the job as additional information. The backup data of the selected type are written to the data carrier inserted in the selected archive device. If no device is inserted in the data carrier, or if another job is active for the device in question, the backup operation is canceled with the error message "Backup not OK". Regardless of the data type and mode of archiving, the generated archive files are always saved first to the online archive on the source station and then exported to a data carrier in the external archive. A distinction must be made in this process between data with and without an implicit reference to a station. Data with an implicit station reference are allocated to a specific workstation in the system. They are present only once in non-redundant systems. When archiving these data the data source must be entered and, when dearchiving, the data destination. Data with implicit station references are: Object-specific COL data Graphical objects (M1 models) Recipe configuration data

For data types with no implicit station reference (e.g. BLE data), the source and destination stations must always be entered when archiving and dearchiving. Data without implicit station references are: BLE data Contronic-P data

The dialog is basically identical for all data types. Choose the data type and mode of saving and confirm with 'OK' to activate a filter in which the search criteria for the archive objects can be entered.

Fig. 5: Archiving and backup

Description of fields, Figure 5: Archiving and backup Field A B Archive type Save Example of entry Graphical objects Explanation Display/selection box containing manually archivable data types When the button is selected the selected data can be archived to any desired data carrier.

Page 10

30/72-3780-0 EN

07/1999

Description of fields, Figure 5: Archiving and backup C D E F Archiving Device OK Cancel When the button is selected the selected data are archived to a data carrier of the assigned data carrier type. Display/selection box containing the connected archive devices Confirm and execute the action Cancel the action and return to the last menu

After confirmation with 'OK' another window (Figure 6) opens up. An information text can be entered in it and saved together with the archive data.

Fig. 6: Info text

Description of fields, Figure 6: Info text Field A Info text Example of entry Explanation Option to enter an information text to be saved together with the archive data. This text is displayed in the archive browser when the data are reimported. Confirm and execute the action Cancel the action and return to the last menu

B C

Save Cancel

2.7.1 Archiving/backup of the COL

From the system dialog choose: Control Level -> Archive -> Save -> Archiving/backup, CSO objects, [selection of archive device] -> [filter, COL browser] -> [Save]

Fig. 7: COL archiving, filter settings

The meanings of the individual fields in the filter settings (Figure 7) are described in detail in the TI 'Configuration - Objects'. The result of the search is displayed in the archive browser (Figure 8).

07/1999

30/72-3780-0 EN

Page 11

Fig. 8: COL archiving, filtered COL data

Description of fields, Figure 8: COL archiving, filtered COL data Field A B C D E F G Return Filter Save Cancel job Init COL Example of entry Explanation Cancel the action and return to the last menu Call up the selection filter for the COL browser Confirm and execute the action Cancel the action and return to the last menu Initialize the COL; This function should not be used. Browser window with display of the selected COL data Job window; For explanation see Fig. 1, fields H-R

All COL data have an implicit station reference. Choose 'Save' to open up another window (Figure 9). This window offers the possibility of entering an information text on the archive data. Choose 'COL Complete' to archive all the functions in the COL. Choose 'Filtered Functions' to archive the objects displayed in the browser. By choosing the 'Selected Functions' button, individual objects displayed in the browser can be selected and selectively archived.

Page 12

30/72-3780-0 EN

07/1999

Fig. 9: Archiving COL objects

Description of fields, Figure 9: Archiving COL objects Field A Info text COL Complete Filtered Functions Selected Functions C D Cancel Save Example of entry Explanation Option to enter an information text to be saved together with the archive data. This text is displayed in the archive browser when the data are reimported. Selection of the COL data to be archived Archiving of the functions displayed in the browser Archiving of selected functions Cancel the action and return to the last menu Confirm and execute the action

2.7.2 Archiving/backup of graphical objects (M1 models)

From the system dialog choose: Control Level -> Archive -> Save -> Archiving/backup, Graphical Objects, [selection of archive device] -> OK All files stored under the path /usr/contronic/appl/DD/Models/M1-Models are compiled into one file and archived. Graphical object data have an implicit station reference. They are available only on the COL station. Choose OK to call up the dialog box (Figure 6) offering the option to enter an information text. This text is displayed in the browser when the data are re-imported.

2.7.3 Archiving/backup of BLE data

From the system dialog choose: Control Level -> Archive -> Save -> Archiving/backup -> BLE Application -> [selection of archive device] > [selection of station] -> Save All data stored under the path /usr/contronic/appl/API/arc on the entered station are compiled into one file and archived. BLE data have no implicit station reference. As a result, the stations must be identified by their names.

07/1999

30/72-3780-0 EN

Page 13

Fig. 10: Archiving of BLE data

Description of fields, Figure 10: Archiving of BLE data Field A B Archive type Info text Example of entry hgr93 Explanation Display/selection box containing the workstations in the system Option to enter an information text to be saved together with the archive data. This text is displayed in the browser when the data are re-imported. Cancel the action and return to the last menu Confirm and execute the action

C D

Cancel Save

2.7.4 Archiving/backup of Contronic-P data

From the system dialog choose: Control Level -> Archive -> Save -> CP Subsystem, Archiving/backup, [selection of archive device] -> [selection of station], [selection of track], [selection of CP files], [selected CP files] -> Save The selected files of the chosen station and track are compiled into one archive file and saved under one of the directories /users/hub/cks/1 ... 4. The subdirectories 1 ... 4 are allocated to the four possible tracks. Contronic P data have no implicit station reference.

Page 14

30/72-3780-0 EN

07/1999

Fig. 11: Archiving, filtered Contronic P data

Description of fields, Figure 11: Archiving, filtered Contronic P data Field A B C D E F G H I J K L M Return Save Delete Workstation Track CP files All CP files Latest CP files Selected CP files Selected CP files Export Single Export All hgz1 1 Example of entry Explanation Cancel the action and return to the last menu Confirm and execute the action Delete the selected files Display/selection box containing the workstations in the system coupled to the Contronic P system External archive channel of a Contronic P system Display/selection box containing all Contronic P files of the selected track on the selected workstation Filter button for selection of all Contronic P files Filter button for selection of the latest versions of the Contronic P files Filter button for manual selection of Contronic P data. The archive data are selected by clicking on them with the left-hand mouse button. Display of all selected Contronic P files. Only the data displayed in this window are archived. When the button is selected single files can be excluded from archiving Choose the button to deselect all selected files Job window; For explanation see Fig.1, fields H-R

07/1999

30/72-3780-0 EN

Page 15

2.7.5 Archiving/backup of recipe configuration data

From the system dialog choose: Control Level -> Archive -> Save -> Batch Confi Data, Archiving/backup, [selection of archive device] -> [selection of recipe], [selection of batch files], [selected batch files] -> Save The chosen files of the selected recipes are compiled into one archive file and saved. Recipe configuration data have an implicit station reference. The complete recipe data archiving and processing procedure is described in the recipe package TI 'SymBatch'.

2.8 Dearchiving of data by system dialog

The following data types can be dearchived by way of the system dialog: Maestro UX objects Graphical objects BLE application Contronic P subsystem Recipe confi data Recipe result data Logs

The search for archived data can be executed either via the management table of the external archive or by direct accessing of an external data carrier (Figure 12). When accessing the management table the search can be narrowed down by specifying the data type and entering time criteria. When accessing the external data carrier the complete index of contents is always displayed. In both cases the search results are displayed in a browser (Figure 13). If there are more than 1000 entries on the data carrier or in the management table of the external archive, the browser can only display a total figure for the data set. In this case the search must be restricted by way of the data type and the period of time. The browser indicates whether the data are still in the online archive, or on which data carrier they are stored. After selecting the required data, the user can insert the relevant data carrier to dearchive the data. If the data are still in the online archive or in the online cache of the external archive, no further action is necessary. One file can be dearchived with one job. Where several files are to be dearchived, the process must be repeated as often as necessary. From the system dialog choose: Control Level -> Archive -> Load -> [selection of archive device/online history], [selection of period], [selection of data type]

Page 16

30/72-3780-0 EN

07/1999

Fig. 12: Dearchiving

Description of fields, Figure 12: Dearchiving Field A B C D E F G H Read device Device Read directory Start time Duration Archive type Cancel OK 23.03.1997 06:48:18.832 720:00:00.000 Logs Dev1 Example of entry Explanation Read the index of the inserted external data carrier Display/selection box containing the available archive devices Read the contents of the management table of the external archive Start time of search period. Input in format dd.mm.yyyy HH:MM:SS.sss Duration of the search period. Input in format DD:HH:MM:SS.sss Display/selection box containing the data types for dearchiving Cancel the action and return to the last menu Confirm and execute the action

07/1999

30/72-3780-0 EN

Page 17

Fig. 13: Dearchiving, browser

Description of fields, Figure 13: Dearchiving, browser Field A B C D Return Load Filter Media Export Example of entry Explanation Return to last menu Dearchiving of the selected file Call up the filter for the archive browser Export a data carrier from the management table of the external archive. Function not yet implemented. The exsport is executed automatically as soon as the maximum number of entries in the management table of the external archive is exceeded. Search result of the archive browser. List of archived data with indication of data type, information text, time of archiving and localization of the archive data Job window; For explanation see Fig.1, fields H-R

The system dialog start the job for dearchiving of the selected file and flags it in the job window as active. When it is flagged as finished in the job window, dearchiving is completed. If an error has occurred, it is displayed in the error window of the dialog box. The archiving function also sends operator messages which are then available on the message page. If the archive data are no longer available online, and the required data carrier is not inserted, the user is prompted to insert the data carrier with the message "Insert data carrier". Only one file can ever be dearchived at once by one dearchiving job. Where several files are to be dearchived, the loading process must be repeated as often as necessary.

Page 18

30/72-3780-0 EN

07/1999

2.8.1 Dearchiving of the COL

The COL can only be loaded from the archive if the standard functions already exist in the COL, because the archiving process always requires the _ARCHIVE object from the COL. This means that when a COL is empty as is only conceivable during commissioning or servicing - the commissioning or service engineer must load the standard functions into the COL beforehand by calling up the script LoadZovSysdat.sh. Then an archived configuration can be loaded into the COL (Figure 14). The data are loaded from the external data carrier onto the archive station and then passed on to the COL workstation.

Fig. 14: Dearchiving COL

Description of fields, Figure 14: Dearchiving Field A Ignore old versions Example of entry Explanation Only the data not yet present in the system are included in the dearchiving operation. If data already exist under the same name, older versions are ignored. Regardless of their date of creation, the current data in the system are replaced by the archived data version. Confirm and execute the action Cancel the action and return to the last menu Archive browser; For explanation see Fig. 13, fields A-E Selected data (COL objects) to be dearchived Job window; for explanation see Fig. 1, fields H-R

B Overwrite current versions with old ones C OK D Cancel E F G

07/1999

30/72-3780-0 EN

Page 19

2.8.2 Dearchiving of graphical object data (M1 models)

The data are loaded from the external data carrier onto the archive station and then passed on to the COL workstation (Figure 15). All data in the selected file are loaded under the path /usr/contronic/appl/DD/Models/ARC. The path is only available on the COL station. After dearchiving the data are available for processing by the rearchiving function. After rearchiving the image compilation process must be restarted (see TI 'Rearchiving of Graphical Objects').

Fig. 15: Dearchiving of graphical object data

Description of fields, Figure 15: Dearchiving of graphical object data Field A B C D E Cancel Load Example of entry Explanation Archive browser; for explanation see Fig. 13, fields A-E Selected data (graphical objects) to be dearchived Cancel the action and return to the last menu Load the selected archive data Job window; for explanation see Fig. 1, fields H-R

2.8.3 Dearchiving of BLE data

The data are loaded from the external data carrier onto the archive station and then passed on to the selected workstation (Figure 16). All data in the selected file are loaded under the path /usr/contronic/appl/API/arc. The path is only available on stations on which the BLE API is installed.

Page 20

30/72-3780-0 EN

07/1999

Fig. 16: Dearchiving of BLE-data

Description of fields, Figure 16: Dearchiving of BLE data Field A B C Archive type Cancel Load Example of entry hgz1 Explanation Display/selection box containing the workstations in the system Cancel the action and return to the last menu Confirm and execute the action

2.8.4 Dearchiving of logs

The data are loaded from the external data carrier onto the archive station and then passed on to the workstation from which the dialog box was opened (Figure 17). The result file of the log function is loaded under the path / usr/contronic/appl/PRO/DeArc. Evaluation and processing of the dearchived logs is described in the TI 'Log Processing'.

07/1999

30/72-3780-0 EN

Page 21

Fig. 17: Dearchiving of logs

Description of fields, Figure 17: Dearchiving of logs Field A B C D E Load Cancel Example of entry Explanation Archive browser; for explanation see Fig. 13, fields A-E Selected log to be dearchived Job window; for explanation see Fig. 1, fields H-R Confirm and execute the action Cancel the action and return to the last menu

2.8.5 Dearchiving of Contronic P subsystem data

The data are loaded from the external data carrier onto the archive station and then passed on to the selected workstation (Figure 18). During dearchiving the file is unpacked under the track under which it was packed and archived. The result file is saved to one of the four track directories under the path /users/hub/cks/1 ... 4.

Page 22

30/72-3780-0 EN

07/1999

Fig. 18: Dearchivierung von Contronic P-Daten

Description of fields, Figure 18: Dearchiving of Contronic P data Field A B C D E F Archive type Load Cancel hgz1 Example of entry Explanation Archive browser; for explanation see Fig. 13, fields A-E Selected Contronic P data to be dearchived Job window; for explanation see Fig. 1, fields H-R Display/selection box containing the workstations in the system Confirm and execute the action Cancel the action and return to the last menu

2.8.6 Dearchiving of recipe configuration and result data

The complete recipe data archiving and processing procedure is described in the recipe package TI 'SymBatch'.

07/1999

30/72-3780-0 EN

Page 23

2.9 Dearchiving of applications data

Certain data types cannot be dearchived by way of the system dialog. These data must be dearchived by way of applications. The data types include trends and messages. Trend data can be dearchived by way of the curve display, message data by way of the historical message page. The time which elapses from submission of the archiving inquiry through to delivery of the data in the relevant application depends on the localization of the desired data and on the current overall workload of the system. In the case of trends the archive data are searched for in the following order: 1. Online trend archive 2. Online cache of the external archive on the archive station 3. Management table of the external archive on the archive station For the duration of the search the curve display making the inquiry is blocked. Historical message pages are searched for in the following order: Message database on the central message server Online file archive Online cache of the external archive on the archive station Management table of the external archive on the archive station

For the duration of the search the message page from which the inquiry was started is blocked. If the archive data cannot be delivered within 15 minutes, the inquiry is rejected, and must be repeated as necessary. The following reasons may cause an inquiry to be rejected: Archiving inquiries which cannot be processed within a pre-set time as a result of high system load. In this case no error message is delivered. The inquiry must be repeated as necessary. The required data carrier has not been inserted in the archive device. In this case no error lmessage is delivered. The inquiry must be repeated as necessary when the required data carrier has been inserted. The data carrier is specified in an operator message which appears on the alarm page. An error occurs during accessing of the archive device (e.g. because an archive device is defective). In this case an error message is delivered on the alarm page. The possible causes of error, and the associated remedial action, are described in the TI 'System Error Messages'. An error occurs during accessing of the archive device (e.g. archive station unreachable due to network error). In this case an error message is delivered on the alarm page. The possiblei causes of error, and the associated remedial action, are described in the TI 'System Error Messages'.

2.9.1 Dearchiving of trends

Trends are dearchived by way of the curve display (see TI 'Curve Display'). If there are no more data available online in the history of the required trend, the lmessage "Trend data in external archive" appears in the dialog box and on the alarm page. When the 'ExArc' button in the curve display is selected, the prompt "Insert data carrier" appears on the message page. This prompt specifies the data carrier containing the required data. When it has been inserted into the relevant drive, all further actions (access to the data carrier, import of data into the online archive, display of data in the curve display) are automatically executed. The import operation is executed for all signals in the curve display. The imported data are retained on the archive station. The period for which data are dearchived is directly dependent on the time resolution in the curve display. When represented on a 12-hour scale, archived data are dearchived for at least 12 hours; on a 30-minute scale, for at least 30 minutes. As the trends are stored in files, the archiving function searches for the trend files containing the desired period. All the data in those files are always dearchived. On successful import of the data, the message "Trend data loaded from DC" appears on the message page. Any error which may have occurred is displayed on the message page. Possible causes of error, and the associated remedial action, are described in the TI 'System Error Messages'.

2.9.2 Dearchiving of messages

Messages are dearchived by way of the historical message page. By entering an asterisk (*) before the date and time in the dialog box (e.g. *21.04.1997 10:53:00.000) it is possible to access the archived message history. If a time is entered at which no more online message data exist, the user is prompted by the message "Insert data carrier" to insert the data carrier containing the required data. When it has been inserted into the relevant drive, all further actions (access to the data carrier, import of data into the message database, display of data on the

Page 24

30/72-3780-0 EN

07/1999

message page) are automatically executed. As historical messages are stored in files, the archiving function searches for the file containing the required time. All the messages stored in that file are always dearchived. The number of messages contained in a file is configured in the message database object (STD_MDB). The data are loadeda from the external data carrier onto the archive station and then passed on to the central message server. On successful import of the data, the message "Dearchiving OK" appears on the message page. Any error which may have occurred is likewise displayed on the message page. Possible causes of error, and the associated remedial action, are described in the TI 'Systemh Error Messages'.

07/1999

30/72-3780-0 EN

Page 25

3 Configuration of archiving
To make the archiving function usable for the system, it must be configured in accordance with the system structure. The archiving function must also know which data are to be archived. This information is defined on configuration of the individual objects.

3.1 Configuration of the archive object

In order to make archiving configurable and to deliver internal operating states for all system processes, the archiving function provides an object named _ARCHIVE, summarizing configuration parameters and archiving operating states on the archive station (Figure 19).

Fig. 19: Archiving configuration editor

Description of fields, Figure 19: Archiving configuration editor Field A B C D E F G H I J K Return Delete Save Print object COL browser Object editor Object header Data types Devices Access rights Error Example of entry Explanation Cancel the action and return to the last menu Delete the archive object _ARCHIVE and return to the last menu. The user is not allowed to delete the archive object! Save the current object configuration and return to the last menu Create a printout or an ASCII file containing all selectors belonging to the archive object Activate the COL browser (see also TI 'Configuration - Objects') Activate the object editor for the archive object. Use of the object editor is intended only for service purposes! Activate the menu to set the basic object parameters Activate the menu to allocate data carrier types to the Maestro UX data types Activate the menu to allocate archive devices to the archive channels Activate the menu to define access rights to the archive object For display of confi prompts and dialog errors. The button has a dark red background if error messages are waiting. Select the button to open up the error window and acknowledge the error. Information on the object currently in the configuration editor

Info line

The archive object is called up by way of the system dialog. Most entries relate to the external archive. Key parameters include the RHOST entry (WS name) and the hardware constellation of the respective subsystem (Figure 20). If the RHOST entry is not configured, for example, the system has no way of displaying the status of the archiving processes in the relevant subsystem, or to archive the desired data at all.

Page 26

30/72-3780-0 EN

07/1999

Fig. 20: Archiving configuration editor, object header

Description of fields, Figure 20: Archiving configuration editor, object header Field A B CH I WS name Plant area Redundancy status NoReDd hgr93 Example of entry Explanation Start dialog for archive configuration; for explanation see Fig. Abb. 19, fields A-K Name of the workstation installed in the central archive Opportunity to enter various information texts (see also TI 'Configuration - Objects') Entry of parameter for the redundancy mode. Since the external archive is not capable of redundant operation, 'NoRed' must always be entered here. The value is entered automatically and must not be changed.

In the 'Data Types' menu (Figure 21) the data carrier types can be allocated to the non-default data types (see 'Archive/data carrier management').

07/1999

30/72-3780-0 EN

Page 27

Fig. 21: Archiving configuration editor, data types

Description of fields, Figure 21: Archiving configuration editor, data types Field A B Max. entries in DB Data types External devices Buffer time 10000 Example of entry Explanation Start dialog for archive configuration; for explanation see Fig. 19, fields A-K Number of entries in the management table of the external archive. An entry includes a cross-reference to an archive file, the name of the archived function and the archived period. List of data types in the Maestro UX Allocation of data carrier types to the Maestro UX data types. The data carrier type is chosen by selecting a type from the pull-down menu using the mouse. Delay time indicating for how long export data are collected in the online cache of the external archive before being exported. Input in format HH:MM:SS.sss

C D

Trends Data carrier type 0 01:00:00.000

The archive devices are allocated to the archive channels in the 'Devices' menu (Figure 22). A maximum of four archive devices can be connected to the archive station.

Page 28

30/72-3780-0 EN

07/1999

Fig. 22: Archiving configuration editor, archive devices

Description of fields, Figure 22: Archiving configuration editor, archive devices Field A B Archive channels C Archive devices Archive channel 1 DDS streamer with SCSI target ID 3 Example of entry Explanation Start dialog for archive configuration; for explanation see Fig. Abb. 19, fields A-K List of max. configurable archive channels Allocation of the connected archive devices to the archive channels. The archive device is chosen by selecting one of the connected devices from the pull-down menu using the mouse

3.2 Configuration of trend archiving

To enable trend data to be archived automatically, an appropriate entry must be made during configuration of the object concerned (Figure 23). Trend data are archived on the station on which they are recorded. The recording station is specified by the 'RHOST' entry in the object header of the relevant trend. The individual option boxes in the menu are activated with the cursor.

07/1999

30/72-3780-0 EN

Page 29

Fig. 23: Configuration of trend archiving

Description of fields, Figure 23: Configuration of trend archiving Field A B Inscan TRUE Example of entry Explanation Start dialog for archive configuration; for explanation see Fig. 19, fields A-K 'TRUE' signifies that archiving is active for the selected signal. The value cannot be changed explicitly, but only in conjunction with a selector. Selector (subselector) to be archived. When a selector is entered the value in the 'Inscan' field is automatically set to 'TRUE'. In function-oriented subsystems such as Contronic P, the entries for archiving of the individual selectors must be made at this point. In signal-oriented subsystems such as Contronic E, Melody or Freelance 2000, archiving of the individual selectors can be activated by way of the signal allocation dialog 'Signals'. The time constant describes the average time interval after which a signal is archived. This value is required for calculation of the ring memories. It is closely related to the dynamic of the signal and should be adapted to it as far as possible (see 'The online archive'). Input in forrmat HH:MM:SS.sss Minimum time between two successive archiving values. If the values are received more quickly than shown here the interim values are ignored (see 'The Online archive'). Input in format HH:MM:SS.sss Maximum time between two successive archiving values. If no new value meeting the condition of the input filter (mainly time maximum and tolerance band) is received within this time the last archived value is duplicated and archived again. Input in format HH:MM:SS.sss

Selector

VXA

Time constant

00:00:01.000

Time minimum

00:00:01.000

Time maximum

00:10:00.000

Page 30

30/72-3780-0 EN

07/1999

Description of fields, Figure 23: Configuration of trend archiving G Tolerance 0.000000e+00 Tolerance band indicating the percentage by which a value must deviate from the last archived value in order also to be archived. Input as a percentage of the measuring range. Time indicating for how long the chosen selector is to be stored in the online archive. If the volume of data is so low that no archive file could be created, the data are held for longer in the online archive. They are only deleted from the online archive when an archive file has been terminated and the configured period of time has elapsed. With sufficient disk space, the values may very possibly remain in the online cache of the external archive for a long time (see also 'Size monitoring'). Input in format HH:MM:SS.sss Parameter indicating whether the chosen selector is to be transferred to the external archive

Stored online

08:00:00.000

Ext. archive

FALSE

3.3 Configuration of message archiving

To enable messages to be archived automatically, the relevant object STD_MDB must be configured appropriately when the message database is created (see TI 'Messages'). In the object the size of the database and the number of messages to be compiled in an archive file are defined. Archive files created by the message server are automatically passed to the archiving function.

3.4 Configuration of log archiving

To enable logs to be archived, an appropriate entry must be made in the log definition (see TI 'Logs'). Only logs automatically created by the log server can be archived. These are operational, matrix and message logs. If these log types are manually executed, they cannot be archived. Status report logs can only be manually executed, and so are not archivable.

07/1999

30/72-3780-0 EN

Page 31

4 Archive components
4.1 Stations with online archive
Every workstation in a Maestro UX system which is to store data has an online archive. All archive data created in a workstation are stored in the online archive of the station concerned. The data comprise trends and files. The number of trends which can be recorded by a station is limited, for reasons of workloading. The station workload is likewise heavily influenced by the dynamic of the signals. A workstation with an online archive must be designed for adequate performance on the basis of the Maestro UX project design guidelines.

4.2 Station with centralized archive

Within a Maestro UX system any workstation can be defined as the designated archive station. In addition to the software components of the online archive, the components for management of the external archive and the external archive devices, and for communication with the external archive devices are also installed on this station. This workstation is termed the "archive station" in the following. All designated trend and file histories are passed on to the external archive by way of the archive station. The trends and files designated for long-term archiving originate from the online archives of the workstations in the system, including the online archive on the station with the centralized archive. Up to four external archive devices can be connected via a SCSI interface for long-term data storage. Due to the high volume of data, the archive station should have at least 4 gigabytes of available disk capacity. The archive station must be designed to be able to process both the workload generated by the local online archive and the data from the overall system designated for the external archive. It must be designed for adequate performance and memory capacity on the basis of the Maestro UX project design guidelines.

4.3 External archive devices

External archive devices for long-term storage of archive data supported as from Maestro UX version 1.2D are 3.5'' DAT tape drives (DAT: Digital Audio Tape) and magneto-optical drives. A maximum of four external archive devices can be connected. External archive devices must be connected to the station on which the central archive is installed. Due to the physical background conditions, the devices cannot be connected in any desired combination. The permissible combination options are listed on Data Sheet 10/72-4.23. The tape drives support recording formats DDS-1 and DDS-2 (DDS: Digital Data Storage). The storage media for DAT drives are available in different tape lengths: Tape length 60m, 90m with recording format DDS-1 Capacity <= 2 GB (uncompressed) Tape length 120m, 90m with recording format DDS-2 Capacity <= 4 GB (uncompressed)

The standard storage media used for magneto-optical drives are magneto-optical disks with a total capacity of 2.6 GB (double-sided, i.e. 1.3 GB per side). The magneto-optical media are written to with the HP-UX file system, and are treated like an additional hard disk. The archive devices are notified to the archiving function by way of the archive object. When a certain device has been entered, then that device is reserved exclusively for archiving use. If the device is required for other use, it must be explicitly removed from the archive object for the duration of the other use. If more archiving jobs are awaiting processing when the device is removed, the current job being executed is first completed. The remaining jobs are retained in the job queue - provided they are export jobs - until the archive device, including the required data carrier type, is entered again (see Figure 22). Waiting dearchiving jobs which cannot be processed within a timeout period of 15 minutes are rejected. In the case of the DAT tape drives, an ongoing archiving job can be canceled by removing the data carrier. The archiving function flags the job as not properly completed, and retains it in its job queue until the original data carrier is inserted again. The archiving function cyclically addresses the device to check whether the data carrier has been re-inserted.

07/1999

30/72-3780-0 EN

Page 32

In the case of the magneto-optical drives used, it is not possible to remove the data carrier during ongoing archiving. When the job is started the data carrier, that is to say the file system on it, is incorporated into the UNIX file system. The data carrier can not be removed until the archiving job has been completed and the data carrier, or the file system on it, has been removed from the UNIX file system and released.

Page 33

30/72-3780-0 EN

07/1999

5 Structure and layout of the archive

The Maestro UX archive comprises the two components: online archive and external archive. Histories are created for data of various types. In processing of the archive data a distinction is made between trends and file histories. File histories are always stored in the online archive and in the external archive. Trends, on the other hand, are held only in the online archive, and are only transferred to the external archive when explicitly configured to be transferred. For export to the external archive the data are first transferred to the archive station, and from there passed to the external data carrier. As long as disk capacity permits, the exported data are retained in the online cache of the external archive. Trends and files in the online archive and in the online cache of the external archive can be accessed directly, because they are still present on the hard disk. Trends or files stored in the external archive are only present on the external storage media, if they have been removed from the online cache of the external archive. To access those data the user must first insert the relevant medium into an archive device and copy the required data back onto the hard disk of the archive station. Trend data are re-imported by means of the curve display (see TI 'Trend Displays in Maestro UX'); files are re-imported by means of the archive browser. Depending on data type, the imported data are held centrally on the archive station or are passed on to the relevant destination station. Files in the online cache of the external archive can be addressed by way of the archive browser. Special features are the messages which are collected in the centralized message database (MDB). Messages are archived in the form of files. In configuration of the message archiving function (object STD_MDB, see TI 'Messages') parameters are set defining the number of entries into the message database and the number of messages which are to be compiled into a file. If the number of messages stored in the MDB exceeds the configured value, the oldest messages are compiled into a file, exported to the external archive, and then deleted from the MDB.

5.1 The online archiv

Every workstation in a Maestro UX system which archives data has an online archive. Only data created on the workstation itself are archived in the online archive of a station. The data are, firstly, trends recorded on the station and, secondly, the files created by various applications on the station and passed to the archiving function. A separate history is created for each trend. The size of the history is configurable, and is defined separately for each individual trend. The totality of trend files of all trends recorded on the station, plus the archived files, comprises the online archive of the station.

5.1.1 Layout and function of the online archive for trends

The function of the online archive for trend data is to store and manage trends recorded on a Maestro UX station, over a configured period of time. For each trend, it consists of a buffer area in the RAM and several time-sorted archive files. Sources of trends may be various signal types. Analog signals Binary signals Counter signals Times Durations ASCII signals Packed binary signals

Note: The ASCII and packed binary signal types cannot currently be archived. If a function is designated for archiving, criteria must be defined for the function to enable the archiving system to decide whether a value is to be stored or not (see Figure 23). Based on those parameters, the archiving system then orders the updating service to deliver the next current value and assesses whether the value is recorded. In normal mode the current values are written to the RAM buffer, and then to the archive files as soon as the RAM buffer overflows. The RAM buffer is dimensioned to enable it to store the incoming values for a few minutes.

07/1999

30/72-3780-0 EN

Page 34

The defining parameter for this is the time constant 'Z Minimum' (see Figure 23). With a memory requirement of 32 bytes per value and an update cycle of 1 second, the RAM buffer is able to take approximately 140 values (140 x 32 bytes => approx. 4.3 KB memory requirement for one signal). A reduction of 'Z Minimum' to 100 ms thus means a memory requirement increased by a factor of 10. To prevent the process environment and the load generated by the archiving from becoming too large, the following restriction is made for safety reasons: If 'Z Minimum' is selected so low that a signal requires RAM for more than 1000 values, the memory space is automatically defined as the space required for 1000 values. As a result the period over which a signal can be buffered in the RAM is reduced. The reservation of memory for 1000 values is subject to the condition that not more than 1500 signals are acquired on one workstation. If the number of signals is exceeded, the maximum available RAM requirement per signal, dependent on the number of signals, is reduced in stages. When the data are entered in the archive files the signal values are compressed by means of a virtually zero-loss process. Normally in this process, when two successive values are received only the difference (value, status, time) to the preceding value is stored. A complete value is stored on the basis of specific change criteria and in a cyclical rhythm. The average disk space requirement, using the compression algorithms, is approx. 5 bytes per measured value. However, this value depends on the dynamic of the acquired signal. The calculations were based on a rate of change of 1 value per second. The compression error which can be achieved with this method is < 0.005 per thousand. All archive files are distributed evenly over a directory structure reserved for the archive, based on an internal software name key. The size of the terminated archive files depends on the 'time constant' parameter set in the configuration dialog (see Figure 23). The 'time constant' parameter determines the average time interval between two measured values being archived, and logically should be adapted to the dynamic of the respective signal. According to various system situations, the size of the created archive files may fluctuate between 75 KB (minimum) and 500 KB (maximum). Archive files intended for the external archive are normally 500 KB in size. The number of archive files relating to one trend depends on the 'Stored online' parameter set in the configuration dialog, and on the remaining available hard disk space. If the existing history exceeds the specified value, or if the available hard disk space falls below a specific reserve, the oldest archives are automatically deleted, unless they are designated for the external archive and have not yet been able to be exported to it. If the transfer to the archive station fails due to an error, the online archive prevents data being lost. If the archive station is reachable again after a certain period of time, the data are transferred from the online archive to the archive station, according to the failure duration, and if possible are exported directly onto the external medium. The system then returns to normal operating mode. The data are available to applications requesting them (e.g. the curve display) for as long as they are in the online archive. If the data have already been exported and are no longer in the online archive, the inquiry is passed on to the archive station which manages the external archive. The archive station then initiates all activities necessary to reinstate the data online.

5.1.2 Layout and function of the online archive for files

The function of the online archive for files is to store and manage files created on a Maestro UX station. It consists of files which are created by various functions, such as the logging or recipe functions. Due to its varying data contents, the online archive for file histories is divided into several sub-archives. A station only ever contains the files created by the applications running on the station in question. Data type Recipe data Data of BLE applications Archived message history Archived M1 models Archived log files COL data Data from the Contronic P subsystem Description All archive data of the recipe processing function (configuration and result data) All archive data from the BLE applications All data archived by the message DB Data display configuration data All log files for archiving (configuration and result data) Partial or complete maps of the COL All data generated via Conlink from Contronic P

Page 35

30/72-3780-0 EN

07/1999

From the point of view of archiving, the contents of the individual files are irrelevant. As a result, the methods of handling all data are identical. File histories are always stored permanently, and so are always exported to the external archive. A maximum of 20 files are held online for each data type. If there are more than 20 files of a specific data type, the oldest files are automatically deleted, unless they have not yet been able to be exported to the external archive. If the transfer to the archive station fails due to an error, the online archive prevents data being lost. If the archive station is reachable again after a certain period of time, the data are transferred from the online archive to the archive station, according to the failure duration, and if possible are exported directly onto the external medium. The system then returns to normal operating mode. The files are available to applications requesting them (e.g. message history) for as long as they are in the online archive. If the files have already been exported and are no longer in the online archive, the inquiry is passed to the archive station and so on to the external archive. The archive station then initiates all activities necessary to reinstate the files online.

5.2 External archive

The external archive of a Maestro UX system is the totality of all data carriers generated by the archiving function. As from Maestro UX version 1.2D, DAT streamers and magneto-optical drives are supported as external storage devices. Up to four archive devices can be used simultaneously.

5.2.1 Layout and mode of functioning

The management software for the external archive must only be installed on one workstation in the system. This is the archive station. In addition to the software components of the online archive, the components for management of the external archive and the external archive devices, and for communication with the external archive devices are also installed. All files to be exported from the online archives of the stations throughout the system into the external archive must first be transferred to the archive station. If the files of a sending station were successfully transferred, an entry appropriate to the data concerned is made in the management table of the external archive. The files sent to the archive station are compiled in the online cache of the external archive. The archive station then transfers the files from the online cache into the external archive; that is, it writes the data to the designated data carrier. If the export was successful, the online archives on the sending stations are notified and the files are released for deletion. If the export could not be executed, no acknowledgment is given and the files are not released for deletion. In this case the user must immediately ascertain what is blocking the data export and take the appropriate action to avoid consequential problems (see 'Size monitoring'). The files remain in the online cache of the external archive as long as the hard disk capacity is not used up.

5.2.2 Connection of the archive devices

The archive devices are connected to the SCSI bus on the archive station. The hardware addresses are set by means of switches, according to the system configuration. The numbers 0-4 are provided as SCSI addresses. The DlL switches are usually located on the rear of the device. The hardware-set addresses must match the SCSI addresses set in the archiving configuration dialog. From the five connection options a maximum of four channels can be selected.

5.2.3 Archive data types

To prevent archive data from different applications being intermixed on one data carrier, up to 16 data carrier types (DTyp 0 to 15) can be defined. The data carrier types can be assigned archive data of specific applications. Archive data of different types can, however, be intermixed on one data carrier, according to configuration. The various archive data types are assigned so-called sub-archive names in the archive, which become visible when browsing through the Maestro UX user interface. Each archive data type can be assigned a delay time (VZ) indicating for how long export data are collected in the online cache of the external archive before being exported to

07/1999

30/72-3780-0 EN

Page 36

the external data carrier. This mechanism is applied only when the relevant data carrier is not inserted. Otherwise the data are transferred directly into the external archive. If the required data carrier is not inserted, the user is prompted to insert it at the end of the delay time. The following defaults are set for the various archive data types with regard to data type and delay time: Archive data types Trends Messages Graphic Logs Maestro UX objects Subsystem BLE applications Recipe Sub-archive name Trend history (ARC_Trends) Message history (ARC_EVENTS) Graphics confi data (ARC_GRAPHICS) Logs (ARC_LOGGINGS) Maestro UX configuration data (ARC_OBJDIR) Configuration data of the subsystem, e.g. Contronic P (ARC_SUBSYSTEM) Data of the BLE applications (ARC_BLE_APPL) Recipe data (ARC_BATCH) DTyp DTyp 0 DTyp 4 DTyp 8 DTyp 4 DTyp 8 DTyp 8 DTyp 8 DTyp 4 VZ 1h 8h 0h 8h 0h 0h 0h 8h

5.2.4 Archive/data carrier management

Before a data carrier can be used by the archiving function, it must be initialized. During initialization it is assigned the system ID and one of the 16 data carrier types. To be able to identify the data carrier unambiguously in the system, an additional component is added to the ID the first time it is used. The complete identification code then comprises: the system ID, which in turn consists of three elements: <name of Maestro UX system>@<name of archive station>_<hardware ID of archive station> the data carrier type (number from 0 to 15) a serial number (beginning at 1) referred to the archive data type

Example: The system name is "Kunde31", the archive station name is "ArcWS" and its hardware ID is 33445566; the data carrier type is 0 (this means, if the default has not been changed, the data carrier contains trends) and the serial number is 9. The data carrier ID is then: Kunde31@ArcWS_33445566|0|9 The archiving function generates a string of data carriers for each data carrier type, numbered beginning at 1. The data carrier with the highest number is the current write data carrier. The archiving function writes archive data as standard to the current write data carrier of the corresponding data carrier type. New data carriers as well as data carriers already containing archive data - provided they are not current data carriers - can be initialized. If the data carrier already contained archive data, any cross-references on the carrier are removed from the management system of the external archive. An attempt to initialize a current write data carrier is rejected with an error message. The user is informed of successful completion of initialization by a message containing the data carrier ID. The archiving system requests initialization of a data carrier if a specific archive data type (or a combination of archive data types to be stored together on one data carrier) has not yet been archived, or if the current data carrier is full and terminated. The data carrier type is only assigned the next serial number when the old data carrier is terminated and the first data packet is being written to the new data carrier. This new carrier then becomes the current write data carrier for the type in question. A data carrier may be terminated on the basis of one of the following events: The data carrier is full The maximum permissible number of 1000 files (DAT tapes) or 10000 files (MOs) on the data carrier has been reached. Data can no longer be written to the data carrier due to an error.

Page 37

30/72-3780-0 EN

07/1999

By a "Forced data carrier change" command the user causes a switch to the next data carrier. In the system dialog this is done by choosing "Change Medium".

Important: The user must make sure that the data carrier ID notified in the message is noted on the data carrier label, to ensure that data carriers can be located. To locate the archived data on the data carrier, a management table is created on the data carrier for the external archive, containing a detailed listing of which archive file is stored on which data carrier. This management table is designed as a ring memory. Its size is currently pre-set to 10000 entries. It can be modified by configuration dialog by way of the system object _ARCHIVE (see 'Configuration of the archive object').

5.2.5 Access to the data carriers

All write and read jobs to the external archive are collected in a job queue and additionally logged as non-acknowledgable incoming messages on the alarm page. The user is prompted to insert the required data carrier. As soon as the data carrier is inserted in the archive device the archiving system works through all the jobs designated for it. An outgoing message is sent which can be acknowledged by the user on the alarm page. Maestro UX provides the following services for accessing a data carrier: Write archive data:

The archiving function generates a string of data carriers for each data carrier type, numbered beginning at 1. The data carrier of a type with the highest number, which is not terminated, is the current write medium. The archiving system always writes archive data to the current medium of the relevant data carrier type. Read archive data:

Based on the entries in the management table, the archiving system knows all the data carriers it has generated and knows which archive data are stored on which data carriers. When data no longer present online are accessed the archiving function delivers an operator message to prompt the user to insert the necessary data carrier. Data carriers for which a cross-reference no longer exists in the management table are made known again when inserted into the archive device; that is, the index of the data carrier is re-entered in the management table. Enter data carrier:

Data carriers or non-system data carriers (data carriers from another Maestro UX system) for which cross-references no longer exist in the management table are automatically made known to the system when inserted into the archive device; that is, the index of the data carrier is entered in the management table. Initialize data carrier:

The initialization prepares the data carrier for archiving of the Maestro UX data. The data carrier is assigned one of the 16 data carrier types. As well as this assignment, the system ID is also noted on the data carrier. The data carrier type is only assigned the next serial number when the old data carrier is terminated and the first data pakket is being written to the new data carrier.

07/1999

30/72-3780-0 EN

Page 38

6 Size monitoring
The archiving processes manage the total actual consumption of disk space according to the total capacity of the hard disks. The online archives for the trend and file archives, and the external archive, monitor the consumed disk space on the hard disk on which their data are located independently of each other. Various delete operations are activated depending on the fullness of the hard disks. But as a matter of principle, archive data designated for the external archive which have not yet been able to be exported to it are never deleted. The table below outlines the response to pre-defined levels of fullness: Remaining capacity of hard disk Reserve > 175 MB Trend archive File archive External archive

Normal mode, Message with priority 8, outgoing: 'Disk space reserve for archive OK' Normal mode,

Normal mode, Message with priority 8, outgoing: 'Disk space reserve for archive OK' Message with priority 8, incoming: 'Archive detects disk overflow' File archive deletes already exported data from the online archive until the 225MB reserve is reinstated Message with priority 4, incoming: 'Archive detects disk overflow' Continued deletion of already exported data New archiving operations are rejected Message with priority 1, incoming: 'Archive detects disk overflow' Continued deletion of already exported data New exports are no longer accepted

Normal mode, Message with priority 8, outgoing: 'Disk space reserve for archive OK' Message with priority 8, incoming: 'Archive detects disk overflow' The external archive deletes already exported data from the online cache until the 225MB reserve is reinstated Message with priority 4, incoming: 'Archive detects disk overflow' Continued deletion of already exported data from the online cache of the external archive Message with priority 1, incoming: 'Archive detects disk overflow' Continued deletion of already exported data New exports are no longer accepted

125 MB < Reserve <= 175MB

Message with priority 8, incoming: 'Archive detects disk overflow'

68MB < Reserve <= 125MB

Message with priority 4, incoming: 'Archive detects disk overflow' Trend archive deletes already exported data from the online archive until the 225MB reserve is reinstated Message with priority 1, incoming: 'Archive detects disk overflow' Continued deletion of already exported data Continued archiving of trends is stopped

Reserve < 68MB

Page 39

30/72-3780-0 EN

07/1999

7 Evaluation of archived trend data

The data recorded by the subsystem are passed to Maestro UX for display and archiving. For each trend to be archived input criteria must be configured, explicitly indicating the conditions under which the asynchronously received values are written to the archive. The configuration of the filter should be adapted to the dynamic of the respective signal. Pressure and flow signals, for example, generally change quickly, and should be acquired with the appropriate accuracy. Temperatures and levels, on the other hand, change relatively slowly, and can be configured with correspondingly higher tolerances and archiving cycles. When low tolerances and short archiving cycles are set, the received values are mapped very precisely into the archive, involving a large volume of data for processing. Setting a broad tolerance and a long archiving cycle produces a small volume of data . But the received signal is mapped less precisely into the archive. When the values have passed the input filter they are written to the archive using a virtually zero-loss compression method. The archived trend data can be redisplayed and evaluated on-screen using various applications, such as the curve display. For this, the application passes to the archive management the required trend selection criteria, such as: the selector name the start and end of the display period the desired resolution (number of values) y-tolerance (the y-tolerance indicates the percentage by which the signal values in two successive resolution intervals must differ so as not to be compiled into one value) the evaluation algorithm

The archive management searches through the archive files on the basis of the specified criteria, decompresses the values it finds, and prepares them using the selected evaluation algorithm so that they can be processed directly by the application. Using a specific evaluation algorithm, a specific view of the archived data is thus produced. In this way, a value string with non-equidistant time intervals is mapped into a value string with equidistant time intervals. The evaluation algorithms are not applied to ASCII, binary and packed binary type signals. The following evaluation algorithms are available: First value: The "first value" method delivers the value at the beginning of the resolution interval. If there are no values in the display or resolution interval as a result of the non-equidistant original archive data, the archive management searches back until a value is found. This value is then replicated according to the resolution in the display interval. fn(x) = x(T1); k=T1, ... ,Tm fn(x) T1 Tn m n Maximum: The "Maximum" method delivers the maximum value from the resolution interval. If there are no values in the display or resolution interval as a result of the non-equidistant original archive data, the archive management searches back until a value is found. This value is then replicated according to the resolution in the display interval. First value in n-th resolution interval Start of resolution interval End of resolution interval Number of values in resolution interval n-th resolution interval

07/1999

30/72-3780-0 EN

Page 40

Calculation formula: fn(x) = max(x(k)); k=T1,...,Tm fn(x) T1 Tn m n Minimum: The "Minimum" method delivers the minimum value from the resolution interval. If there are no values in the display or resolution interval as a result of the non-equidistant original archive data, the archive management searches back until a value is found. This value is then replicated according to the resolution in the display interval. Calculation formula: fn(x) = min(x(k)); k=T1, ... ,Tm fn(x) T1 Tn m n Mean value: The "Mean value" method delivers the mean value from the resolution interval. If there are no values in the display or resolution interval as a result of the non-equidistant original archive data, the archive management searches back until a value is found. This value is then replicated according to the resolution in the display interval. Calculation formula: fn(x) = [sum(x(k))]/m; k=T1, ... ,Tm fn(x) T1 Tn m n Tendenz (1 - 5): The "Trend" method delivers the trend behavior of the signal in the resolution interval. The individual trends (1 5) are differentiated by a scaling factor. If there are no values in the display or resolution interval as a result of the non-equidistant original archive data, the archive management searches back until a value is found. This value is then replicated according to the resolution in the display interval. Mean value in n-th resolution interval Start of resolution interval End of resolution interval Number of values in resolution interval n-th resolution interval Minimum in n-th resolution interval Start of resolution interval End of resolution interval Number of values in resolution interval n-th resolution interval Maximum in n-th resolution interval Start of resolution interval End of resolution interval Number of values in resolution interval n-th resolution interval

Page 41

30/72-3780-0 EN

07/1999

Calculation formula: fn(xk) = fn-1(xk) + ([sum(x(k))]/n - fn-1(xk))/y; if (fn-1(xk) > fn-1(xk)) then

fn(xk) = max(x(k)) else fn(xk) = min(x(k)); k=T1, ... ,Tm sum()/n fn-1(xk) fn(xk) T1 Tn n m y Mean value in n-th resolution interval Trend in (n-1)-th resolution interval Trend in n-th resolution interval Start of resolution interval End of resolution interval n-th resolution interval Number of values in resolution interval Factor (T1: 1; T2: 2; T3: 4 T4; 8 T5: 16)

07/1999

30/72-3780-0 EN

Page 42

8 Archiving in redundancy mode

The redundancy in Maestro UX is based on 1:1 station redundancy (see TI 'Redundancy'). In normal trouble-free operation the active and passive workstations of a redundancy pair have equal rights. In this, a redundant software environment means that applications and/or objects which are capable of redundant operation always operate in redundant mode on redundant workstations. When a workstation is in redundant mode, the online archiving also operates in redundant mode. This means both the online trend archive and the online file archive are present in redundant form on both stations. The external archive is non-redundant (the redundancy status in the object header entry must always be set to 'NoRed'), because all archive data for export are held in the online archive until they are written to an external backup data carrier. If the archiving in a Maestro UX system is to be executed as redundant, in project design precisely those stations which acquire the data for which redundancy is desired must be executed as redundant. With Contronic P as the underlying automation system, the trend and message archiving systems are automatically the Maestro UX workstations which have a direct link to the CKS. With other subsystems such as Melody, Freelance or Contronic E, the station which is to acquire the data can be freely selected by choosing the RHOST entry in the object header (see Figure 20) of the relevant functions. In this way, the recording of trends required as redundant can be freely allocated to a redundant station. Applications which store their results in files generally create those files on the station on which they themselves are run. If such data are archived in redundant mode, a distinction must be made between the following cases: The application itself is capable of redundant operation The application is not capable of redundant operation

If the application itself is capable of redundant operation, the generated data are automatically present in redundant form if the application runs in a redundant environment. If the application is not capable of redundant operation, but its data are to be held in redundant storage, the application must be installed in a redundant environment. The archiving software will redundantly archive all the data it receives, including the data from the application not capable of redundant operation. If the Maestro UX software is restarted on a redundant station on which an error has occurred, on restart a system correction is performed between the active and the passive stations (see TI 'Redundancy'). Since in the course of archiving most data must be corrected - an operation which can take up to 14 hours with a total storage capacity of 5 KB - the archive is corrected as the last system component. The trend archive is processed first, and then the file archive. The correction is performed in such a way that only data for the periods not overlapping on both stations are transferred from the active to the passive station. The bases for correction are the management tables of the online archives for trends and for files. Data on the passive station not present or no longer present on the active station are also deleted by the passive station in the course of the correction.

Page 43

30/72-3780-0 EN

07/1999

9 Consistency of the archive - Recovery mechanisms

In trouble-free operation the archiving software safeguards the consistency of the archive data by specifying the sequence of processing and rectifying any errors. All data are stored in the form of files in a pre-defined directory structure. Three management tables exist to manage the archive data: A management table for trends in the online archive A management table for files in the online archive A management table for data of the external archive

The contents of these management tables consist of cross-references to the archive files. The consistency check ensures, firstly, that the management tables and archive files themselves are consistent and, secondly, that the references in the management tables to the stored archive data are also consistent. If a malfunction (e.g. hardware defect, software crash) causes a workstation to crash, data in the Unix file system may be damaged or lost. This particularly affects data accessed by write operations shortly before the crash. As a result of the buffer mechanisms of Unix, the probability is then high that the changed data had not be written to disk when the crash occurred. By its recovery mechanisms Unix ensures that an operational file system is available on boot-up. The loss of other data is accepted as the price. As a result the status of the user data in the file system, in particular of the data changed prior to the crash, cannot be predicted. For Maestro UX this may mean that a) data may be missing or inconsistent b) Maestro UX processes may crash when they have to work with data which no longer have the expected structure following a malfunction To safeguard the integrity of the archive data in such cases, a so-called 'logical recover' operation is executed when the system is rebooted. This procedure determines whether the consistency of the archive data present is safeguarded. Trend archives of which the consistency cannot be guaranteed are deleted. This ensures that Maestro UX processes which need to access the archive will not crash when the system is rebooted. The check takes around 0.5s per file (7200 files per hour). Assuming an average of 1.5 files per trend, 4800 trends can be checked in one hour. To do so, the following steps are executed in sequence: Regeneration of the trend management table from the remaining trend files Consistency check of the trend files in the online archive; inconsistent files are deleted Regeneration of the file management table from the remaining files Consistency check of the files in the online archive Check that the management software of the external archive was terminated properly. If it was not, the existing management table of the external archive is deleted and a new, empty management table is created. If no online backup of the management table is found, the table remains empty; otherwise the backup is loaded

Handling of the system in conjunction with recovery mechanisms, and their mode of functioning, is described in the TI 'System Administration'.

Hartmann & Braun

Industriestrae 28 65729 Eschborn Tel. (06196) 800-0 Fax (06196) 800-11 19 Subject to technical changes Hseler Platz 2 42567 Heiligenhaus Tel. (0 20 56) 12- 0 Fax (0 20 56) 12- 56 79

ABB Automation Products

Kohlstrae 4 32425 Minden Tel. (05 71) 830- 0 Fax (05 71) 830- 11 05 Printed in the Fed. Rep. of Germany 30/72-3780-0 EN 07/1999 ABB