Asset view

The asset view opens when you click an asset's name in the asset list, or Details for an asset on the asset map. It shows the information for a single asset, organized into tabs for Timeline, Project, Simulation, Operations, Data coverage, and Files. The Simulation tab is shown only for assets with a solar or battery component.

The header shows the asset name and status, an Edit button that opens the asset settings (keyboard shortcut: E), and a menu with Add to PPA, Copy, and Delete. For assets that combine solar with a battery or load, the menu also offers Change asset plan. When you open an asset from the asset list, previous and next buttons in the header step through the assets in the list.

Timeline

The Timeline tab is a chronological log of everything that affects the asset. It combines automatically generated system events (such as commercial operation dates, end of operation, PPA terms, and FIT or FIP subsidy periods) with events that you record yourself, such as maintenance, incidents, and construction work. It shows what has happened, what is in progress now, and what is coming up.

Layout

Events are grouped into four sections that you scroll through vertically. Each section can be collapsed:

• Past: Events that have already ended
• Ongoing: Events whose status is In progress
• Today: Scheduled events that start on the current day
• Upcoming: 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 ongoing events, the button scrolls to those instead. The filter panel on the left lets you narrow the view by affected equipment, event category, status, entry method, tags, 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, deleted, or commented on by users.

System event types include:

• Grid interconnection
• COD and end of operation for each solar, battery, hydro, biomass, and load component
• Project end of life
• PPA start / PPA end
• FIT start / FIT end
• FIP start / FIP end
• Start of operation / End of operation (the start and end dates of the Balancing and trading feature)

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

Anomaly events

Anomaly events are available when enabled for your workspace; contact Tensor to enable them. Tensor Cloud checks the generation data of each asset every 30 minutes and adds an event of type Anomaly to the Timeline when it detects one of these problems:

• No generation: The plant reports zero output in daylight, when it should be producing. Curtailment in the grid area is taken into account.
• No data: Generation data that used to arrive regularly has stopped arriving.
• Out of range: A measured value is negative, or higher than the site AC capacity allows.
• Low output: Over the past weeks, the plant's best half-hour of output has stayed far below that of comparable plants.

Each anomaly event carries an Auto detected label and shows when the problem started. Once the data shows the problem is over, Tensor Cloud closes the event and sets its end time. Like system events, anomaly events are read-only: you cannot edit, delete, or comment on them. They also have no operational impact, so they do not change the asset status. To show or hide them, use the Anomaly option of the event type filter or the Auto detected option of the entry method filter.

Detection starts when the feature is enabled and does not add events for problems from before that.

Events

Events record anything that happens to the asset that you want on file, such as inspections, repairs, outages, or grid connection work. Unlike system events, events are created by users and can be edited or deleted at any time. Each event has one of the following types: Maintenance, Incident, Aggregation contract, Construction, Grid connection application, Grid connection test, or Other.

Creating an event

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

• Event title: Up to 200 characters. Titles of earlier events on the asset are suggested as you type.
• Event type: One of the types listed above.
• Operational impact: Turn this on when the event takes equipment out of service, then choose the affected equipment: one or more of Generation, Battery, and Load, depending on which components your asset has. At least one is required while the toggle is on.
• Related tags: Tags from the workspace's event tag library. You can create a new tag directly from the picker.
• Start date: When the event begins, in JST.
• End date (optional): Turn this on to set when the event ends. It must be after the start.
• Details: A description of the event, which becomes the first comment in its thread. Supports basic Markdown, @mentions, and file attachments. Attached files also appear on the asset's Files tab.
• Participants (optional): Workspace members involved in the event or who should stay informed. Participants are notified of event updates. The creator and anyone @mentioned are added automatically.

The Operational impact and End date toggles start from defaults that depend on the event type: both are on for Maintenance, Operational impact is on for Incident, End date is on for Construction, and both are off for the other types. You can change either before saving.

Once saved, the event appears on the Timeline in the appropriate section (Past, Ongoing, Today, or Upcoming).

Event statuses

Events have one of three statuses:

Status	Condition
Scheduled	Start date is in the future
In progress	Start date has passed and the event has not been completed
Completed	End date has passed, or the event was marked as completed

Statuses change automatically: an event becomes In progress at its start date and Completed at its end date. An event without an end date stays In progress until you mark it as completed.

Editing and deleting events

Open the actions menu on an event and choose Edit to change any of its fields. When editing, the Details field becomes a Comment field: text you enter there is posted as a new comment instead of replacing the original details. Each edit is recorded in the event's change history so the team can see who changed what and when.

The same menu offers Mark as completed for an event that is in progress, Mark as In progress for a completed event, and Delete. Deleting an event asks you to confirm with a checkbox, cannot be undone, and also removes the event's attachments from the asset's Files tab.

Effect on asset status

While an event with operational impact is in progress, the asset's status is automatically set to Maintenance, overriding the Operation status. The asset returns to Operation as soon as the event ends or is marked as completed. Events without operational impact, and past or future events, do not affect the current status.

Effect on operations

Events with operational impact directly affect Tensor Cloud's automated systems. An event without operational impact is recorded on the Timeline only.

• Planner: battery charge and discharge are prevented during the event
• Infeed forecasts: solar generation forecasts are zeroed out for time slots within the event
• EPRX and JEPX auto-bidding: bidding behavior is adjusted to account for scheduled downtime

note

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

Comments

Each event has a comment thread where your team can add context and follow-up notes. Click Show history on an event to open its thread. Comments support basic Markdown, @mentions, and file attachments, up to 5,000 characters. You can edit or delete your own comments after they are posted. System events have no comment thread.

Event change history

All edits to events are tracked and displayed as log entries in the event's thread. When an event is modified, the change history shows:

• Who made the change
• What was changed (e.g., title, type, status, start time, end time, operational impact, affected equipment, tags, participants)
• The previous and new values
• When the change was made

Project

The Project tab shows the full configuration of the asset as a set of cards, allowing you to review every input to the asset simulation without entering edit mode. A side navigation on the left groups the cards into Basics, Project, Components, and Financials, and lets you jump directly to each card. Cards showing editable settings have an Edit button that takes you straight to the corresponding section of the asset settings.

Overview card

The Overview card combines site information with the connections of the asset on Tensor Cloud.

The site information side shows the grid area, the location name and coordinates, a link to the hazard map provided by Disaportal for assessing disaster risks around your asset, and the subsidy scheme. Clicking the coordinates opens the asset location on Google Maps in a new browser tab. An interactive map window displays a marker at the asset's position; you can switch between satellite and regular map views and maximize the map.

The Tensor connection side lists the SPV, PPA, generation and demand balancing groups, and scenario associated with the asset.

General card

This card shows site information: the location name, coordinates, grid area, land area, and altitude. It also lists which components (solar, battery, load, hydro, biomass) are enabled, including any scheduled activation or deactivation dates, and which Tensor Cloud features (balancing and trading, asset management) are active for the asset.

Simulation card

This card shows the scenario assigned to the asset and the generation model used for simulations, either the Tensor model or a custom generation profile.

Operation card

This card lists the identifiers used in supply and demand operations: the location ID, supply location ID, grid code, and contract classification number 2.

Metadata card

This card shows the metadata registered for the asset, including developer, EPC company, O&M provider, operator, owner, METI IDs, NFC ID, and metering day, along with any custom metadata fields.

Tags card

This card shows all tags assigned to the asset.

Grid card

This card shows the grid interconnection details of the asset: the grid interconnection date and the site AC capacity. For assets with a DC-coupled battery, it also shows the site inverter capacity and site inverter efficiency.

Solar card

For assets with a solar component, this card shows the DC capacity, the AC capacity and solar inverter efficiency (except when the battery is DC-coupled, where the site inverter values on the Grid card apply instead), the configuration (tilt and azimuth), the full set of loss settings, and lifecycle dates (COD and end of life).

Battery card

For assets with a battery component, this card shows the technical specifications (energy and power capacity, roundtrip efficiency, maximum cycles, and, for assets that also have solar, AC or DC coupling), operational settings (state of charge limits, cycle cost, and grid charging), degradation, and lifecycle dates.

Load card

For assets with a load component, this card shows the load profile (minimum, maximum, and average load) and lifecycle dates. Load is currently not considered in simulation results.

Hydro and biomass cards

For assets with a hydro or biomass component, the Hydro or Biomass card shows the lifecycle dates (COD and end of life) and the AC capacity.

CAPEX card

This card shows an itemized list of all CAPEX payments registered in the asset settings, with the description, account, and amount of each. Amounts entered relative to a capacity (for example per kWp of solar DC capacity) are shown as a rate with their unit.

OPEX card

This card shows an itemized list of all OPEX items, with the name, account, frequency (one-time or recurring), and amount of each.

Revenue card

This card summarizes all revenue sources configured for the asset: the subsidy scheme (FIT, FIP, or FIT to FIP, with rates and start date; a FIP rate that changes over time is shown as a stepped chart), market participation (day-ahead market, frequency control reserve, and JEPX NFC non-FIT), and other revenue settings: the linked PPA and the environmental value bilateral agreement.

In workspaces where aggregation contracts are enabled, the other revenue settings also list each aggregation contract that covers the asset, with a link to the contract and the period the asset is under contract. If no contract covers the asset, the row reads No aggregation contract. To change the period, edit the contract.

Simulation

The Simulation tab shows the results of asset simulations. It is available only for assets with a solar or battery component. Simulations run automatically whenever you change the asset, its PPA, or its scenario, and every run is stored as a version that you can name, revisit, and compare against the current configuration of the asset. See the asset simulations reference for a full description of simulation versions, the configuration comparison, and each results section.

Operations

The Operations tab shows the operational data recorded for the asset. This page describes the Asset performance card; the tab also has other cards. For assets with a hydro or biomass component, the Hydro generation or Biomass generation chart plots the site meter reading against the generation plan.

Asset performance card

For assets with a solar component, the Asset performance card shows three metrics: Performance ratio (PR), Availability, and Energy ratio. Each has a KPI tile showing its mean over the visible date range, and the chart below plots the daily values (performance ratio as bars, availability and energy ratio as lines). They compare what the asset generated with the sunlight available to it, and answer two separate questions: was the plant producing, and how well did it convert the available irradiance while it was producing?

note

These metrics are measured from operational data. They are not the same as the availability loss assumption you configure on the asset, or the solar performance ratio produced by a simulation, both of which are modeled rather than observed.

How the metrics are calculated

All three metrics are built from the same two 30-minute series, whose timestamps mark the start of each interval.

The first is measured generation, normalized by the installed DC capacity of the solar arrays:

$$P_{actual} = \frac{E \times 2 \times 1000}{C_{dc}}$$

$E$ is the measured energy of the 30-minute slot in kWh. Multiplying by two converts energy to average power over the slot, multiplying by 1,000 converts kW to W, and dividing by the DC capacity $C_{dc}$ in kW gives watts produced per kW of installed capacity. $C_{dc}$ is the summed DC capacity of every solar array on the asset.

The second is global tilted irradiance $G$ in W/m², the irradiance arriving on the plane of the modules. It is modeled from historical weather data at the coordinates of the asset, using the tilt and azimuth of the asset's first solar array, and resampled to the same 30-minute grid. That weather data comes from the historical weather datasets the platform uses for past weather.

Normalizing by DC capacity makes the two series comparable. Modules are rated at standard test conditions of 1,000 W/m², so a perfect array under 1,000 W/m² would produce exactly 1,000 W per kW installed. Dividing output by irradiance therefore yields a dimensionless number that is 1 for a hypothetically lossless plant and, in practice, sits well below it.

Assets with multiple arrays

Output is normalized by the summed capacity of every array, but irradiance is modeled from the orientation of the first array alone. On an asset whose arrays sit at different tilts or face different directions, the full installed capacity is therefore being compared against a single plane of incidence, and all three metrics are biased as a result. How far, and in which direction, depends on how much the remaining arrays differ from the first.

Performance ratio

The performance ratio is total normalized output divided by total irradiance, counting only the slots that were available (see Availability below):

$$PR = \frac{\sum_{available} P_{actual}}{\sum_{available} G}$$

Because unavailable slots are excluded, the performance ratio measures conversion quality: how well the plant turns sunlight into electricity when it is producing. Only slots below the 5% bar are excluded, though, so partial derates and curtailment above that bar still weigh on this figure.

Availability

Availability is evaluated per 30-minute slot. A slot counts as available when either condition holds:

$$P_{actual} \geq 0.05 \times G \qquad \text{or} \qquad G < 20\ \mathrm{W/m^2}$$

The first condition asks whether the plant produced at least 5% of what the irradiance would suggest. This is a deliberately low bar, so that only a genuine outage or near-total loss of output trips it, not a bad day. The second exempts slots with almost no sunlight: at night and around dawn and dusk there is nothing to convert, and without this exemption every night would register as an outage.

The daily and monthly figures are the share of slots that were available, so 98% availability over a day means 98% of that day's slots met one of the two conditions.

Availability is not uptime

Because every night-time slot satisfies the second condition unconditionally, a monthly availability figure includes every night in the month and will sit well above what an operator would call uptime. And because the first condition asks only for 5% of expected output, a plant limping along at 6% of expectation all day still scores 100% available. Availability answers whether the plant was producing at all, not whether it was producing well. Read this metric together with the performance ratio.

Energy ratio

The energy ratio uses the same formula as the performance ratio, but over all slots, available or not:

$$ER = \frac{\sum_{all} P_{actual}}{\sum_{all} G}$$

Because it includes the periods when the plant was down, it captures total delivered energy relative to total available irradiance.

Both ratios are clipped to a range of 0 to 1. The clip is silent, so a value that would exceed 1, usually a sign of incorrect capacity metadata or of the multi-array caveat above, appears as a flat 1.0 rather than as an anomaly.

Reading the three metrics together

In practice the energy ratio sits at or below the performance ratio, and the gap between them is the production lost in the slots that counted as unavailable. Comparing the three metrics tells you where to look:

Pattern	Interpretation
High performance ratio, low availability	The plant converts well but stopped producing for part of the period. Check the Timeline for maintenance events and the monitoring feed for outages.
High availability, low performance ratio	The plant produced throughout but underperformed. Curtailment is a common cause in Japan and does not show up in availability, since a curtailed slot usually still clears the 5% bar. Other typical causes are soiling, shading, module degradation, and inverter issues.
Wide gap between performance ratio and energy ratio	A large share of the period's potential energy was lost in unavailable slots rather than to conversion losses.
Either ratio pinned at exactly 1.0	Almost certainly a data problem rather than a perfect plant. Check the registered DC capacity and array orientation.

For the two ratios, monthly values are not the average of the daily values. The monthly numerator and denominator are re-summed across the whole month and then divided, which weights each day by its irradiance. A bright day therefore counts more towards the monthly figure than an overcast one, which is what you want when judging how much energy was actually captured. Monthly availability is not weighted this way: it is simply the share of the month's slots that were available. The KPI tiles on the card are a plain mean of the daily values in the visible range, without irradiance weighting.

Data requirements and limitations

These apply to all three metrics.

• Availability is computed at 30-minute, daily and monthly resolution. The performance ratio and energy ratio exist at daily and monthly resolution only.
• The metrics require a solar component with a DC capacity greater than zero, on an asset past its commercial operation date. Assets without solar arrays, or with no capacity registered, do not produce these metrics.
• Measured output comes from the solar monitoring reading. For assets with no battery, metered export is loaded alongside it and takes precedence where both exist; assets with a battery use the monitoring reading only, since a battery's meter nets charging against discharging and is no longer a generation reading. Metered export is net of on-site consumption, so an asset with a significant auxiliary load reads low.
• The most recent days are not shown: weather data takes about three days to arrive, so the series ends three to four days before the current date. The card shows the last calculated date.
• Slots with no measured reading at all are excluded from the calculation rather than counted as downtime. A genuine zero recorded in daylight does count as unavailable, but a slot where no reading arrived is dropped entirely. A gap in the monitoring feed therefore does not lower availability; it shrinks the sample the metrics are computed from, and a day with only a few hours of data can still report 100% availability. Check the Data coverage tab to confirm how complete the underlying data is before reading anything into a figure.

Data coverage

The Data coverage tab shows how complete the actual generation and load data of the asset is, so you can find gaps in its history.

What data coverage shows

The tab shows:

• Coverage percentages for each data source
• A heatmap of daily coverage across the year
• Detailed measurements for a selected day
• Summary statistics for overall completeness

Data sources

Coverage is tracked for three sources.

Meter confirmed

Official meter readings from the utility. They are the most accurate source and are used for billing and official reporting.

Meter preliminary

Meter readings from the utility before final confirmation. They arrive earlier than confirmed readings and are generally accurate, but may still be revised.

Monitoring system

Real-time data from on-site monitoring equipment, used for operational monitoring and performance analysis.

Controls and filters

Year selector

Choose a year with the year picker, or step between years with the arrow buttons. Coverage is calculated for the full calendar year.

Data source filter

Switch between Generation (solar generation data) and Load (consumption data) to see the coverage of each.

Upload menu

Use the Upload data menu to upload Meter data (official utility meter readings) or Monitoring data (monitoring system measurements) and fill gaps in coverage.

Visual components

Coverage heatmap

The heatmap shows each day's coverage percentage as color intensity, with darker colors for higher coverage:

• Dark = 100%
• Medium = <100%
• Light = 0%
• Neutral gray = future slots

Click a day to see its measurements. Future dates are marked and cannot be selected.

Coverage summary

This section, titled Actuals data coverage since COD, shows the total coverage percentage across all sources from COD to the current date, a progress bar for each source, and the total number of available time slots for the selected period.

Daily measurements chart

When you select a day on the heatmap, this chart shows that day's measurements from each data source side by side, so you can compare them and spot data quality problems.

Understanding coverage metrics

Coverage percentage

Coverage percentage is (days with data) / (total available days) × 100. At 100%, data is available for every day in the period.

Available slots

The total number of days in the selected period, counting only days after the asset's COD.

Data uploads

To upload data that improves coverage, see Data uploads.

Files

The Files tab is where you upload, organize, preview, and download the documents associated with an asset: technical specifications, contracts, photos, and grid-connection paperwork. See the Files reference for details on tagging, filtering and grouping, and inline preview.