> For the complete documentation index, see [llms.txt](https://docs.myrspoven.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.myrspoven.com/other-interfaces/backoffice.md).

# BackOffice

BackOffice is Myrspoven's internal configuration and monitoring tool. Operations staff use it to register signals, set the bounds within which myCoreAI operates, and manage the processes that drive data collection and control. Customers work in [myPortal](https://docs.myrspoven.com/other-interfaces/myportal.md); integration partners have self-service access to BackOffice for onboarding and configuration tasks.

## Scope

* **Building onboarding.** Registers signals from the Building Management System (BMS) integration, sets optimizer bounds and comfort bounds, and configures the writable setpoints myCoreAI will steer.
* **Feature configuration.** Enables and tunes myCoreAI add-ons per building: myLoadshift and comfort-driven adaptive min/max limits.
* **Process management.** Creates and toggles the recurring processes behind data collection and control: BMS reads, weather reads, optimizer runs, and setpoint writes.
* **Sensor placement.** Places room sensors on the building's floor-plan blueprints and links each one to its room temperature, CO₂ and humidity signals. Sensors can be placed one by one or imported in bulk from a placement file (.xlsx or .csv) supplied by the sensor provider; each imported row is reviewed before it is applied. If the file covers several properties, only the rows of the building's own property are imported. Each floor's sensors go to the blueprint with the same floor number, and a different blueprint can be chosen per floor when the file numbers its floors differently from the drawings. When an import links a room temperature or CO₂ signal to a sensor, it also enables that signal for myCoreAI.
* **Curves and transformations.** Supply curves define the operating envelope available to myCoreAI; transformation tables link related signals — for example, a supply-air temperature reading with its corresponding setpoint.
* **Support diagnosis.** Used by Myrspoven staff to inspect a building's configuration and recent optimizer runs when a case is raised.

## Add room sensors

This configuration is restricted to Myrspoven staff and integration partners with self-service BackOffice accounts. Customers request room-sensor placement through their Myrspoven representative.

Before placement, ensure these items are available:

* The target building.
* A floor-plan blueprint for the applicable floor.
* Registered source room-sensor signals available for linking.

### Individual placement

1. Use BackOffice's sensor-placement workflow for the target building.
2. Add the room sensor and link its available room-temperature, CO₂, and humidity signals.
3. Select the intended floor-plan blueprint.
4. Save or apply the placement.
5. Verify that the sensor appears in the myPortal blueprint view.

Not every device supplies all three measurements. Link the signals available from that device.

### Bulk import

1. Obtain the `.xlsx` or `.csv` placement file from the sensor provider.
2. Import it through the sensor-placement workflow.
3. Review every proposed row before applying it.
4. Import only rows for the target property.
5. Map each floor to its matching blueprint. Choose a different blueprint when file and drawing floor numbers differ.
6. Apply the reviewed import.

Linking a room-temperature or CO₂ signal through the import enables that signal for myCoreAI. Placed sensors appear in the myPortal blueprint view.

Equipment and observable creation, source-signal registration, platform-specific mapping, workflow navigation, and placement-file schemas depend on the account and integration. Authorized partners use the onboarding material assigned by their Myrspoven contact. Customers contact their Myrspoven representative.

## Customer-visible effects

Most BackOffice activity is invisible from the outside. A subset of changes surfaces in myPortal:

* Updated comfort bounds or optimizer bounds appear in the relevant myPortal views once applied.
* Newly added signals or meters show up in reporting and component views.
* Newly placed room sensors appear in the myPortal blueprint view.
* Feature toggles — enabling myLoadshift, for instance — reveal the corresponding myPortal section.

Configuration changes are requested through the Myrspoven representative; customers do not action them directly.

## Integration partners

Partner-specific onboarding steps — discovery file, transformation table, supply curves, read-process activation — are covered in the onboarding material shared by the Myrspoven contact. They sit outside the public documentation because the workflow depends on the BMS vendor and integration method.

## Access

Access is restricted to Myrspoven staff and integration partners with self-service accounts.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.myrspoven.com/other-interfaces/backoffice.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
