Workspace settings
Workspace settings apply to the active workspace. Some pages and actions are limited to workspace administrators; see member roles.
General
Workspace administrators can rename the active workspace on this page.
Members
This page lists every member of your workspace with their role, when they joined the workspace, and when they were last active. You can search members by name or email address and filter the list by role.
Workspace administrators can invite new members, change the roles of existing members, and remove members from the workspace on this page.
Adding and removing members
To invite new members as a workspace administrator, click the Invite button at the top right of the member list. Enter one or more email addresses, separated by commas or spaces or by pressing Enter after each one, or paste a list of addresses. Then select Send invitation. You can invite up to 25 new members per day.
To remove a member, click the delete icon on the right of the member list and confirm in the dialog.
Removing a user from all workspaces does not delete their account. To keep using Tensor Cloud, they need an invitation from an administrator of an existing workspace, or a new workspace created by Tensor support.
Member roles
Workspace administrators can change a member's role with the edit icon on the right of that member. There are two roles:
- Administrators can invite and remove members, change their roles, and manage workspace-level settings such as API keys and integrations.
- Users can use the rest of the platform, including adding, editing, and deleting assets, PPAs, and scenarios, but cannot use administrative functions such as inviting members or changing roles.
Check the member list from time to time to make sure no other administrator has invited someone from outside your organization by mistake.
Tags
On the Tags page you manage the custom labels used to organize assets, files, and events in your workspace. Tags are listed on separate Assets, Files, and Events tabs, each showing how many items use the tag. Each tag has a color, a name, and an optional description. Every workspace member can create, edit, and delete tags, and every tag is available to the whole workspace. Deleting a tag removes it from every item it is attached to.
You can use tags to group assets by project phase, location, ownership, or any other criteria that suit your portfolio. Add them to assets from the asset list or in asset settings, then use them to filter your portfolio.
For more on using tags, see Tags.
Notifications
On this page you choose which notifications Tensor Cloud sends you and where. There are three categories:
- Alerts: urgent events that need immediate action
- Reminders: upcoming events that need attention or action
- Activity: general updates and changes made by others
For each category, choose whether to receive it in your Tensor Cloud inbox, by Email, or both. Notification settings are separate for each workspace.
Stakeholders
Here you manage the stakeholders that appear in various places on Tensor Cloud. Each stakeholder has a name, a contact person, an email address, a phone number, and one of these types:
- Developer
- EPC
- O&M
- Offtaker
- Operator
- BG responsible party
- Owner
Adding a company to this list does not give it access to any information in your account, and does not tell the company that you added it. The list is visible only to members of your workspace and is never shared with other Tensor Cloud customers or third parties.
API keys
API keys authenticate requests to the Tensor Cloud API. On this page, workspace administrators can generate new keys, edit the name and permissions of existing keys, and revoke keys that are no longer needed. For how to use API keys, see the API documentation.
A new key is shown only once, right after you generate it. Save it somewhere safe: you cannot view it again, and if you lose it you have to generate a new key. Revoking a key disables it immediately, and any request made with it is rejected.
Keep your API keys secure, never commit them to source control, and make sure any third party you share them with stores and retrieves them securely. If you think a key has been compromised, revoke it immediately and create a new one.
Each key is granted permissions per resource:
| Resource | Path | Available access |
|---|---|---|
| Assets | /v1/assets | Read |
| Asset actuals | /v1/actuals | Read, Write |
| Generation forecast | /v1/forecasts | Read |
| Price forecast | /v1/price-forecast | Read |
Give each key only the permissions its task needs. For example, a key that only reads asset actuals from Tensor Cloud should be read-only, and only a key that writes actuals back needs write access. This limits the damage if a key is misused.
Integrations
The Integrations page connects your Tensor Cloud workspace to external services and APIs. It lists the OCCTO, TSO data provision system, EPRX, ElecONE, JEPX, and Adincs integrations, each with its connection status. Tensor also sets up a SECOM secure file transfer integration on request. To ask for an integration that is not listed, use Request new integration at the bottom of the page.
OCCTO integration
The OCCTO integration lets you submit generation, sales, and procurement plans to OCCTO through Tensor Cloud.
To connect your workspace to OCCTO, provide:
- Username
- Password
- Certificate
- Certificate password
We recommend creating a dedicated user in your OCCTO account for the Tensor Cloud integration, with the permissions needed to submit plans to OCCTO.
Generation plan updates
There are two options for the contents of your generation plan. By default (Generation plan updated dynamically), the generation plan for your BG is updated whenever new forecasts are available, which can be as often as every 30 minutes. Alternatively (Generation plan always equals sales plan), the generation plan always equals your sales on JEPX.
Sender
Sender information consists of a sender ID and a sender name.
The sender ID is a unique 4-digit identifier that OCCTO assigns to each grid participant. It is often suffixed with a single digit for the grid area and used as a 5-digit "operator code".
The sender name is the grid participant's name as registered with OCCTO. OCCTO does not check its contents.
Submitter
Submitting plans to OCCTO requires a unique submitter ID for each grid area, which is the same as your JEPX customer ID for that grid area. Use Add submitter to register a grid area with its submitter ID and submitter name. Submitter information is used both for OCCTO submissions and for trading on JEPX, so deleting it affects the OCCTO and JEPX plans for that grid area.
Only one submitter ID per grid area is supported. If you need more, contact Tensor through the Get support button.
Plan submission autopilot
When Enable autopilot is on, Tensor Cloud submits the selected OCCTO plans for you. Autopilot covers two plan families, Generation plans (generation-sales plans) and Demand plans (demand-procurement plans), on the same schedule, based on OCCTO's official deadlines:
- 2-day-ahead plan: submitted at 09:30 JST on D−2 (30 minutes before OCCTO's 10:00 deadline)
- Day-ahead plan: submitted at 11:30 JST on D−1 (30 minutes before OCCTO's 12:00 deadline)
- Weekly, monthly, and yearly plans: submitted at 09:00 JST on the calendar day before each published deadline
Each family has its own checkboxes for the five plan types. Only the selected types are submitted automatically, and you submit the rest yourself. This helps when another system already handles part of your submissions: for example, if an external trading integration sends your 2-day-ahead and day-ahead plans to OCCTO, select only the weekly, monthly, and yearly plans here.
Generation plans are submitted for all balancing groups configured with a contract classification number 1, including those with no operational assets. For those, an empty (zero-value) plan is submitted, which meets OCCTO's reporting requirement.
To exclude a balancing group from autopilot, leave its contract classification number 1 unset. Balancing groups without it (typically ones created for testing) are never submitted automatically.
Demand plans are submitted for every internally managed demand balancing group in your workspace, again with an empty (zero-value) plan for balancing groups with no eligible assets. The demand side has no contract classification number, so you cannot exclude a single demand balancing group; the Demand plans checkboxes are the only control. Procured volumes match the JEPX buy bids for batteries that can charge from the grid.
You are notified in the app and by email only when a submission fails. Successful submissions do not trigger notifications; you can see them on the OCCTO submission screens. Balancing groups covered by autopilot do not receive the day-ahead reminder email.
Autopilot submits plans for you, but you remain responsible for OCCTO compliance.
TSO data provision system
The TSO data provision system integration imports preliminary meter data (30-minute generation and usage data) and confirmed meter data directly from your transmission and distribution system operator (TSO), so you do not have to retrieve and upload meter data by hand.
Setting up TSO integration
To enable the TSO data provision system for your workspace, upload these credentials:
- Certificate (the client certificate)
- Certificate password
- Operator code, if you retrieve data from Chubu Electric Power Grid: the 4-character code assigned to your organization at registration, which Chubu uses to build the URL for retrieving meter data
Tensor Cloud then tests the connection to the TSO system endpoint for each area (for example, Kyushu Electric Power Transmission and Distribution Co., Inc.). In the Grid operator connections section you can then control the connection to each of the nine grid operators separately.
Your TSO provides the client certificate, which authenticates your requests to its data provision system.
Automatic data import
Once connected to the TSO system, Tensor Cloud automatically imports preliminary 30-minute generation data for every registered asset in your workspace.
For the import to work, the location ID must be filled in correctly in the asset settings. Tensor Cloud matches imported data to assets by this location ID.
Confirmed meter data
Tensor Cloud can also import confirmed meter data automatically. These are the final figures used for settlement, published monthly by the TSO.
Turn it on for each grid operator with the Confirmed meter data toggle in the TSO integration settings. It needs no extra credentials and uses the client certificate you already uploaded. Some grid operators also require a file password to open their confirmed meter data files; for those, the integration settings ask you for it.
Availability differs by grid operator:
- Hokuriku Electric Power Transmission & Distribution and Shikoku Electric Power Transmission & Distribution do not provide confirmed meter data through the integration.
- For Tohoku Electric Power Network, confirmed meter data comes through the existing connection, with no extra setup.
- Chugoku Electric Power Network requires the File password for its confirmed meter data files.
Confirmed meter data is retrieved weekly, and the first sync runs within a week of turning it on. The Integrations page shows the connection status of each grid operator and when data was last received.
Data availability
Preliminary meter data can only be imported for the past 14 days, including today. The TSO systems set this limit.
The TSO publishes confirmed meter data once a month. With the confirmed meter data import turned on, Tensor Cloud imports it automatically and you no longer need to upload it.
For periods the automatic import does not cover, such as months before you turned it on, you can still upload monthly confirmed meter data with the data upload function. The TSO portal provides this data as "発電者の仕訳後の電力量のお知らせ帳票" (hatsudensha no shiwakego no denryokuryō no oshirase chōhyō, post-accounting electricity notice for generators).
EPRX integration
The EPRX integration lets Tensor Cloud participate in the balancing markets for you.
To connect your workspace to EPRX, upload your TLS client certificate (PKCS#12 file) and enter its password. Tensor Cloud reads the user name, MMS code, and expiry date from the certificate and asks you to confirm them. You also need to provide:
- Operator code: the unique identifier issued by EPRX
- Legal entity name
- Contact phone number and contact email address: these appear on the notification sent to the TSO when a balancing market award is cancelled, so enter a phone number and an inbox that someone monitors
Only workspace administrators can update the credentials, change the operator code, switch auto-offering on or off, or disconnect the integration.
EPRX auto-offering
When Submit offers automatically is on, Tensor Cloud submits balancing market offers to EPRX for the workspace's registered resources on every planning cycle, every day including weekends and holidays. Offers are based on the latest forecasts and Tensor's optimization model. Awarded volumes become a delivery obligation, and failing to deliver carries a penalty.
Switching it off stops new offers from the next planning cycle. Offers already submitted to MMS and volumes already awarded are not affected: Tensor does not withdraw them, so you have to do that in MMS yourself. Generation plan (BP 0431) and baseline submission continue either way.
Auto-offering submits offers for you, but you remain responsible for your participation in the EPRX market.
ElecONE integration
The ElecONE integration allows Tensor Cloud to deliver forecasts and plans for your assets directly to the ElecONE supply-demand management system, without any manual exports or uploads. It is used only when configured for your workspace, which requires alignment with the Tensor Energy technical team. Contact Tensor through the Get support button if you would like to use it.
JEPX integration
The JEPX integration lets Tensor Cloud submit day-ahead spot bids to JEPX for you. Tensor provisions it: Tensor sets up your JEPX Member ID and must activate the integration before you can enable autopilot.
On the JEPX integration page, workspace administrators can:
- Register a Delivery contract code for each grid area you trade in on JEPX. Removing a code stops autopilot submissions for that grid area.
- Turn on Enable autopilot and choose the Grid areas to auto-submit.
For how autopilot bids are generated and submitted, see JEPX automatic trading.
Adincs integration
The Adincs integration sends generation plans for your assets directly to the Adincs supply-demand management system used by your retailer or aggregator. The latest plan for each asset is delivered automatically every hour, with no manual exports or uploads. The integration page shows the endpoint URL and the plant mapping: each plant delivered to Adincs with its inquiry ID.
SECOM secure file transfer
The SECOM integration lets Tensor Cloud deliver files, such as generation plans, securely to your counterparties with SECOM's secure file transfer software 転送くん (Tensō-kun, literally "transfer").
Tensor sets up the SECOM and Adincs integrations for your workspace. To use one of them, contact Tensor through the Get support button.
Operations
The Operations page holds workspace-level settings that affect how Tensor Cloud generates battery optimization schedules for all assets in the workspace.
Imbalance value Operation
The imbalance value is an extra penalty, in JPY/kWh, that the battery optimization engine applies to any imbalance it would cause when it generates charge and discharge schedules. Use it to tune how hard the engine tries to stay on the submitted generation and demand plans. You can enter a value from 0 to 9,999 JPY/kWh.
The imbalance value changes optimization behavior as follows:
- 0 JPY/kWh (default): The engine is free to cause imbalance and uses the day-ahead auction price as a proxy for the imbalance price. This usually maximizes expected wholesale market revenue, but can lead to larger deviations from submitted plans.
- Above 0 JPY/kWh: A penalty is added on top of the day-ahead price proxy, pushing the engine to cause less imbalance. The higher the value, the harder the engine avoids imbalance, possibly at the cost of some wholesale market revenue.
- Very high values (e.g., 1000 JPY/kWh): Imbalance becomes, in effect, a hard constraint. The engine avoids imbalance even when that lowers overall profit.
The imbalance value only affects how the optimization engine plans dispatch. It does not change the actual imbalance prices settled with OCCTO.