Document the disturbance before clearing the information from theIED.Only authorized and skilled personnel should analyze possibleerrors and decide on further actions. Otherwise, stored disturbancedata can be lost.6.2.1 Disturbance recording triggering GUID-5569488B-F930-4762-99CE-2863BEFB1947 v8Disturbance recordings are normally triggered by IED applications when theydetect fault events. Disturbance recordings can also be triggered manually orperiodically. The manual trigger generates an instant disturbance report. Use thisfunction to get a snapshot of the monitored signals.6.2.2 Disturbance record analysis GUID-52E4493E-5F8F-44F8-94DE-23A2EBD36AC1 v5The IED collects disturbance records of fault events which are set to trigger thedisturbance recorder. Disturbance data is collected and stored for later viewing andanalysis. The disturbance recorder data can be read and analyzed with PCM600.For more information, see PCM600 documentation.6.2.3 Disturbance reports GUID-4191AAA0-EA7E-4C74-9B8E-EC44FC390919 v3PCM600 can be used for creating reports of disturbance recorder data.For more information, see PCM600 documentation.6.2.4 IED self-supervision GUID-FFF9F2C4-B04B-40BD-A636-8D430DBA69CF v10The IED self-supervision handles internal run-time fault situations. The mainindication of an internal fault is a flashing green Ready LED.Internal faults can be divided to hardware errors, run-time errors in the applicationor operating system and communication errors. Further actions always depend onthe cause of the error.Section 6 1MRK 500 128-UEN BIED operation58 650 series 2.2 IECOperation manual