Timeline

The Timeline tab on the asset view is a chronological log of everything that affects a single asset. It combines automatically generated system events — such as commercial operation dates, decommissioning, and FIT or FIP subsidy periods — with maintenance events that you create yourself. Use the Timeline to see at a glance what has happened, what is in progress right now, and what is coming up for an asset.

Layout

Events are grouped into four sections that you scroll through vertically:

• Past: Events that have already ended
• In progress: Events whose start date has passed but end date has not
• Today: Events that occur on the current day
• Future: Events that have not yet started

The Today button on the action bar jumps the scroll position to the current day, which is useful when an asset has a long history of events. If there are in-progress events, the button scrolls to those instead. The filter panel on the left lets you narrow the view by event type (system or maintenance), affected components, status, and date range.

System events

System events are read-only entries automatically generated from the asset settings. 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)

To change a system event, edit the corresponding field in the asset settings — they cannot be modified directly from the Timeline.

Maintenance events

Maintenance events represent periods during which the asset is temporarily offline for inspection, repair, or other planned work. Unlike system events, maintenance events are created by users and can be freely edited or deleted at any time.

Creating a maintenance event

Click New maintenance at the top right of the Timeline to open the maintenance event dialog. The dialog has the following fields:

• Start: When the maintenance period begins. Date and time are entered with minute precision in JST.
• End: When the maintenance period ends. Must be after the start.
• Affected components: One or more of generation, battery, and consumer, depending on which components your asset has. If your asset only contains a single component, it is selected automatically.
• Note (optional): A free-text comment explaining the maintenance work.

Once saved, the event appears on the Timeline in the appropriate section (Past, In progress, Today, or Future) based on its dates relative to the current time.

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 and deleting maintenance events

Open an existing maintenance event from the Timeline to change its dates, affected components, or note. Each edit is recorded in the event's change history so the team can see who changed what and when. Maintenance events can also be deleted from the same menu.

Effect on asset status

While a maintenance event is in progress (the current time is between its start and end), the asset's status is automatically set to Maintenance, overriding the Operation status. The asset returns to Operation as soon as the event ends. Past and future maintenance events do not affect the current status.

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

note

After creating, editing, or deleting a maintenance event, downstream forecasts and OCCTO plans may take up to 30 minutes to reflect the change.

Comments

Each event on the timeline supports threaded comments, letting you and your team add context, explanations, or follow-up notes directly inside the Timeline. You can add a comment when creating or editing a maintenance event, or add comments directly to any event. 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.