AMS data flow and event logs

Data processing flow

AMS processes availability data through the following stages:

1. Tag and alarm description mapping convert raw data into mapped events
2. Event log generation creates structured event records
3. AMS configuration maps event codes to allocation categories and availability criteria
4. Users edit, reset, preview, and publish event data
5. The system saves changes and tracks delta changes between previous and current states
6. Reports are generated based on published availability data

Types of event logs

AMS manages three types of event logs:

Turbine downtime logs

Turbine breakdown causes alarms that trigger event logs. Event codes mapped to these alarms are categorized as downtime events.

Edited logs

Users can modify and save event logs. These logs are used to review and achieve accuracy.

Noncommunicating logs

Event logs that occur when signals are missing, such as power, wind speed, or alarm code data. These logs indicate periods when the system cannot determine turbine status.

Data backfilling rules

AMS applies the following rules when backfilling data:

• The system recomputes the last 30 days of data when delayed inputs are received
• Only unedited or unsaved data is overwritten during backfilling
• Noncommunicating logs are converted to either Turbine OK status or downtime events based on available data
• Metadata updates apply forward in time, but you can publish based on updated mappings for historical periods