DE19532927A1 - Documentation of fault data in power generation plant - Google Patents

Abstract

The documentation system receives inputs 1 entered via a server 2. The server controls the protocols and graphical plots of data 3 that are then stored in buffer memory 4 in a directory form. When the cycle documentation is complete the archiving process commences 6 and the files are entered into disc memory, e.g. optical discs 8. The files are accessed for processing with the aid of a user terminal 9 that allows menu 10,11 selections to be made using a mouse. Servers 12,13 access the memory and files are called 14 for output.

Description

The invention relates to a method for documenta tion of faults (fault sequence documentation) of the process in a power plant.

The fault sequence documentation (StAD) in a fault sequence Documentation archive (StAD archive) fulfills the requirement, Stö Processes in a power plant, in particular in a nuclear power plant, document and about life archive the duration of the power plant. This is the fault process documentation usually in paper form (protocols, Plots). These papers were placed in filing halls stores. There is the possibility of a subsequent Generation of fault sequence documentation from archived Data. However, this is very time consuming since each compo Individuals of the fault sequence documentation are activated individually that must. There is also an overview of when which faults process documentation was triggered, does not exist, So far, no general realization of this possibility has been found my acceptance by operators and / or authorities.

The invention is therefore based on the object, a suitable Process for documenting process malfunctions running, d. H. a suitable fault sequence documentation give.

This object is achieved by a Stö Process documentation (protocols, plots) by a supplier number of signals relevant for an accident analysis triggers, the state of the Signals is registered, and where signal sequences and / or Value changes within a the trigger time closing configurable observation period be drawn.  

In this case, a fault sequence log can be created based on an event nisses (excitation signal) a message status log, a ver history report and optionally several plots produce. Since the excitation signal is the event a logical connection are theoretically infinite Many stimulating signals possible.

The message status log describes the status of a Selection of binary values at the time of the fault, possibly also at a configurable time before or after the fault at the time. The past report log then the message history of a binary value selection for a period before or after the time of the fault (binary pre and post history). The signal range for that Message status and the past message log is up to 18 signal-related (up to 64 binary values) or area-related message groups (any number Binary values).

The plots for each fault sequence log describe the time Chen course of up to eight each in an analog value group summarized analog values (analog pre-story and post-story te). In addition, the time course of the triggering signal, as well as the course of others, in one Binary value group summarized binary values documented. Of the value range of the X-axis valid for the time course is the same time range as for the message sequence prototype coll.

By defining a log type, the time window to be considered by the fault flow log with the variables "start of the previous history", "end of the post history" and "start time of the message status log relative to the time of the fault" is defined. The scope of a fault log includes analog value groups with the associated binary value groups for describing the plots, message groups for describing the message status log, message groups for describing the past message log and the configuration of locked fault logs. Under a locked fault sequence protocol is to be understood as follows: B. 10 and 15 are excited, but in this operating case Be only the fault log 15 of interest. The fault sequence log 10 is thus locked or suppressed as a function of the fault sequence log 15 . According to this definition, up to 100 different fault sequence logs are permitted.

Under the triggering event for a fault sequence prototype koll is always to be understood as a change in the binary value, whereby each binary value can stimulate a fault log. Several signal changes can be prototyped by a signal change be stimulated.

You can also have several fault logs at the same time be excited. A suggestion of the same fault sequence pro tokolls during the course of post history is under presses. Does one occur during the course of the after story Suggestion of a locked fault log, so who which generates the plots for these fault sequence logs. Each fault sequence log can also be operated be stimulated. The logs and plots are made after Expiration of the observation period issued.

An embodiment of the invention is based on a Drawing explained in more detail. It shows:

Fig. 1 shows a time axis with an observation period and lying in a tripping mentation Störungsablaufdo, and

Fig. 2 shows a schematic diagram of the archiving and analysis of a fault process documentation.

Fig. 1 shows a fault sequence documentation observation period t _b , which results from the trigger time t₀ and a configurable pre / post history t _g .

For the long-term storage of fault sequence documents tations (StAD), these are stored on separate data carriers, e.g. B. archived on optical disks such as MOD, WORM or CD-ROM. All components of a fault sequence documentation (StAD) (Logs, plots) are under an identification criterion rium filed.

For this, a start signal 1 for a city to city to a server 2 as shown in FIG. 2 passed. The StAD server 2 controls the structure of the protocols and plots. The logs and plots are printed out on printer 3 . In parallel to the output on the printers 3 , the logs and plots are temporarily stored in files 4 . The files 4 of a StAD are summarized in a directory.

Once the StAD has been completely prepared, archiving 5 is started. An archive server 6 is given information for identifying the StAD, from which the accountant for an archive is built. The files of the StAD are stored under an identification StAD number and a trigger time. The composite StAD archive is forwarded at 7 to a juke box as archive 8 for storage on optical disks, or stored directly on an optical disk in a single drive. In the Juke Box 8, it is archived in a StAD trail, ie only StAD are archived on an optical disk, with no mixing with other data.

For StAD evaluation, this is selected at 9 via a user interface. After specifying a time range and a StAD number, the bookkeeping of the archived StAD is displayed in a StAD overview 10 . In this, e.g. B. with a click of the mouse on the desired StAD, the desired StAD for a StAD edition 11 can be selected. The abbreviation KKS (power plant identification system for all power plant components) denotes a StAD, which is selected via the corresponding KKS.

The associated component logs or plots are displayed for the selected STAD. The mouse or each sub-component required for output is also selected with a mouse click. The output activation is forwarded to an operating server 12 , which stimulates the retrieval of the StAD data from the archive (juke box) 8 and the output of the or each StAD part component. An evaluation server 13 communicates with the juke box 8 or an individual drive and requests the selected STAD from the STAD trail. The read StAD is split at 14 into its subcomponents, which are stored in separate files.

The evaluation server 13 organizes, via an output server 15, the output of the or each selected sub-component to a printer, a plotter and / or a viewing device, or the transfer to an external application.

The advantages of StAD archiving are in particular in that fault sequence documentation for a very long time period (months) on a data carrier (optical disk) can be archived. The space required for the documents administration is drastically reduced. In addition, the StAD archives can be checked as a closed unit. Except that is the output of the StAD and its components at all times possible as original, whereby the archived StAD much faster than the subsequent preparation of the StAD is.

The targeted archiving of the StAD makes it possible to Suppress online edition of the StAD on printing devices (paperless control room), and only print out the StAD if necessary. All components of a StAD are common  Identification feature addressable. The book also shows maintain the StAD archive, when which StAD was triggered has been.

Claims (1)

Process for documenting faults in the process flow in a power plant, in that a fault sequence documentation (StAD) is triggered by a number of signals relevant for a fault analysis,
wherein the state of the signals is registered for the triggering time (t₀), and
whereby signal follow and / or value changes are recorded within a configurable observation period (t _b ) including the triggering time (t₀).