> 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/customer-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](/customer-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 — energy cap, 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. * **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. ## 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. * 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.myrspoven.com/customer-interfaces/backoffice.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.