Editing and saving AMS event logs

Edit event logs in the Availability Management System (AMS) to reallocate event codes, change allocation categories, split event durations, add comments, and publish availability data.

About this task

AMS provides comprehensive editing capabilities for event logs to reallocate event codes, change allocation categories, split event durations, and add comments. You can edit single or bulk entries, and the system tracks all changes through a complete edit history.

Procedure

  1. Edit event codes or allocation categories.
    • To reallocate event codes, select one or more event logs and assign a new root cause event code. Allocation categories do not automatically change when event codes are edited.
    • To reallocate allocation categories, select one or more event logs and choose a new allocation category from the list. New categories automatically populate the list when added to the configuration.
    • To edit noncommunicating logs, select the logs and assign appropriate event codes or allocation categories based on available information.

    Bulk editing supports between 100 and 300 logs per operation. The edit window allows changes for a maximum of 30 days at a time.

  2. Split event durations if needed.

    For events more than 20 minutes (with 10-minute data cadence), you can split the event duration. Each event can be split only one time, and splits are limited to day-level adjustments. Split events are highlighted in blue.

  3. Add comments to event logs.

    You can add comments to individual or bulk event logs to document downtime details or causes of delay. Comments help provide context for availability reports and audit.

  4. Reset edits if needed.

    Use the reset function to undo the last bulk action and return events to their previous state.

  5. Save your edits.

    Unsaved edits are visible for 24 hours only. After saving, edits are highlighted and the count of unpublished logs is displayed. Saved edits persist indefinitely until published. If multiple users edit the same events, the recent version is retained. If you fail to save, the system reverts to the last saved state.

    Only saved events can be published for availability reporting.
  6. Preview availability before publishing.

    Review the availability calculations based on your saved edits to help ensure accuracy before publishing.

  7. Publish the availability data for the selected time period.

    You can publish anytime for any selected time period. The system tracks publishing history with timestamps.

Results

Your edited event logs are saved and published. The system maintains a complete user edit history and tracks changes between previous and current states.

What to do next

You can view the complete edit history and publishing history at any time to audit changes and track availability reports over time.