Timeline
The Timeline tab provides a single chronological view of all events related to an asset. It combines system-generated lifecycle milestones with user-created maintenance events into one unified feed, giving you a clear picture of what happened, what's happening now, and what's planned.
Timeline overview
The Timeline displays events in an agenda-style layout, grouped into date-based sections:
- Past — completed events and historical milestones
- In progress — maintenance events currently underway
- Today's schedule — events scheduled for today
- Upcoming — future planned events
Use the Today button in the toolbar to quickly jump to today's events. If there are in-progress events, the button scrolls to those instead.
You can filter the timeline by date range and event type to focus on specific periods or categories of events.
System events
System events are read-only entries automatically generated from your asset's configuration data. They mark key lifecycle milestones and cannot be created, edited, or deleted by users.
System event types include:
- COD (Commercial Operation Date)
- FIT start / FIT end
- FIP start / FIP end
- Battery COD
- Battery warranty end
- Start of operation / End of operation
- Asset status changes (e.g., when Tensor features are enabled or disabled)
Maintenance events
Maintenance events are created by users to record planned or unplanned downtime. They are the primary way to communicate maintenance schedules across your team and to Tensor Cloud's automated systems.
Creating a maintenance event
To create a maintenance event, click the Create maintenance event button at the top of the Timeline tab. You will need to provide:
- Start date and time — when maintenance begins
- End date and time — when maintenance ends (must be after the start time)
- Affected components — select which parts of the asset are affected (e.g., solar array, battery)
- Comment (optional) — add context about the reason for maintenance
Event statuses
Maintenance event statuses are derived automatically from the start and end dates — they are not set manually:
| Status | Condition |
|---|---|
| Scheduled | Start date is in the future |
| In progress | Current time is between start and end dates |
| Completed | End date is in the past |
Editing a maintenance event
You can edit a maintenance event to update its dates, affected components, or add a comment. All changes are tracked transparently in the event change history — there are no silent overwrites.
Deleting a maintenance event
Maintenance events can be deleted when they are no longer relevant. Deleted events are removed from the timeline.
Effect on operations
Maintenance events directly affect Tensor Cloud's automated systems:
- Planner — battery charge and discharge are prevented during maintenance windows
- Infeed forecasts — solar generation forecasts are zeroed out for time slots within maintenance windows
- EPRX and JEPX auto-bidding — bidding behavior is adjusted to account for scheduled downtime
Changes take effect within the next scheduled run, typically within 30 minutes. The UI communicates this scheduling expectation when you create or edit a maintenance event.
Comments
Each event on the timeline supports threaded comments, allowing your team to add context, explanations, or follow-up notes without leaving the activity feed.
You can add a comment when creating or editing a maintenance event, or add comments directly to any event in the timeline. Comments can also be edited after they are posted.
Event change history
All edits to maintenance events are tracked and displayed as log entries in the timeline. When an event is modified, the change history shows:
- What was changed (e.g., start date, end date, affected components)
- The previous and new values
- When the change was made
This ensures full transparency — you can always understand what was planned, what changed, and when.