Gjennomgang av veiviseren for nytt bygg

Site setup is a guided, step-by-step flow that takes a site from "we just signed the contract" to "the platform is controlling the site's technical systems". To start, open Bygg → Legg til bygg. Which steps you see depends on what the site does, chosen in Step 1, and on the integrations you connect in Step 2; this guide is the map of all of them: what each step does, what you need ready, and where the natural checkpoints are. The setup saves a draft as you go, so you can leave at any point and resume it from the list in Step 1.

Trollmann er AI-en som setter opp dette bygget: den leser dokumentene og dataene dine, spør deg bare om det den ikke finner der, og lager konfigurasjonen.

Før du begynner

Site setup goes fastest when you have everything in hand before you start it. Most slow-downs are not the setup waiting on you — they are you waiting on someone else (your BMS vendor for the address-list CSV, your Niagara supplier for the station connection, your IWMAC contact for the Endpoints CSV in "Watchdog-oppsett"). Gather what you can in advance and the rest of the steps go quickly.

1. A BMS credential per provider you enter yourself (for example IWMAC Client ID + Client Key). You can enter it in "Integrasjoner og kartlegging" now, or skip the provider there and return to that step to add it later; "Utrulling og test" needs it before it can deploy the credential to the site. See the BMS-specific guides for what your vendor calls these and where to find them.
2. Niagara (hosted by us): nothing to gather — we issue the connection, and the setup shows it on a read-only card in Step 2. The owner guide "Niagara: connect your building to us" walks through it.
3. Byggspesifikke overstyringer der SD-anlegget trenger det (for eksempel IWMAC Plant ID for dette bygget).
4. Den rå adresseliste-CSV-en fra hvert SD-anlegg — eksportert av SD-leverandøren eller integratoren, ikke håndredigert.
5. Valgfritt, men svært nyttig: VVS-dokumentasjon for bygget (systemskjemaer, P&ID-er, utstyrslister, navneforklaringer). Veiviseren bruker disse til å identifisere systemer og komponenter i "Gjennomgå funn".
6. Sensorlegitimasjon hvis dere bruker Airthings eller Disruptive Technologies (Client ID + Secret, eller Service Account-nøkkel).

Help is one click away in every step. The "Ask Helper" button at the top of each setup step opens an in-app helper for questions about what you are looking at right now. While it is open, the same button reads "Hide Helper". Use it instead of guessing.

Lokasjonsinformasjon

Before anything else, an organisation must be selected in the sidebar — if none is, Step 1 shows a notice asking you to pick one and Next stays disabled. Then pick a unique site name. It is used in URLs, in the cluster, in our internal logs and — for connections we issue, such as Niagara MQTT — as the permanent identity in the username and the topic folder, so the rules are strict: lowercase letters, digits and hyphens only, 3–40 characters, no dots, starting and ending with a letter or digit. Examples: "narvik-vagle", "office42". Choose it once; it cannot be changed after the site exists. The same screen lists any drafts you started earlier. Pick a draft to resume rather than starting fresh.

Step 1 also asks for the "Tilknytning til dette bygget": how the organisation selected in the sidebar is related to the site. Whoever holds the service agreement for this building decides it; if you do not know yet, ask them before you continue. The options are:

Laster …

Continuing past Step 1 registers the site under that organisation, with the relationship you chose. If the site already exists under another organisation, creation is refused; that site is managed from Organisasjoner instead. Once the site is registered, Step 1 shows the relationship rather than asking for it again, and it is changed from Organisasjoner.

Step 1 also asks what the site does: the site's capabilities. Nothing is pre-selected, and each option is marked "styring" or "kun lesing". Pick an option marked "styring" only if the service agreement for this building includes the platform writing setpoints to the building management system (BMS); if the agreement covers reading only, pick "kun lesing" options. This choice is the site's classification and there is no screen for changing it later, so decide it here.

About drafts: you can have several in flight at once. Drafts are not auto-deleted, so the resume list grows over time — delete the ones you abandoned so the list stays useful. The site name is fixed once you continue past Step 1, because that is when the site is registered (the name is part of URLs and cluster identifiers), so check it before you press Next.

Integrasjoner og kartlegging

For every BMS or sensor system the site uses, add a credential, attach any site-specific overrides such as the Plant ID for IWMAC, and click Verify. For sensor providers such as Airthings and Disruptive Technologies, you also choose which discovered devices belong to this site. When the card of every provider you intend to use shows "Tilkoblet" in green, or for a sensor provider the number of its devices in green once they are found, you are ready for the next step. You can also continue without all credentials in place — discovery and the operational snapshot will be unavailable until you come back and add them, but the rest of the setup will work.

For SD-leverandører som støtter skriving tilbake til anlegget, er Watchdog sikkerhetsmekanismen bak skriving av settpunkter. Om veiviseren har et eget steg for den, avhenger av leverandøren du kobler til: når leverandøren har en Watchdog-funksjon, inneholder veiviseren steget "Watchdog-oppsett", der du setter den opp. Den SD-spesifikke guiden for leverandøren forklarer nøyaktig hva Watchdog gjør.

Some connections are issued by us rather than entered by you — Niagara MQTT is one. Its card is read-only: it shows the broker address, username and topic folders we issued, a "Test MQTT-megler" button and a "Use this connection for this site" checkbox, and there is nothing to type. The owner guide "Niagara: connect your building to us" explains what to do with the card, step by step.

Last opp dokumenter

Upload the technical documentation you have for the site: system schematics, P&IDs, equipment lists, and naming legends. A provider whose card in "Integrasjoner og kartlegging" has its own list upload takes its point list or device list there; add the point lists of the other providers, meaning the raw BMS exports, here. If documents already exist for this site, the setup offers to reuse them instead of re-uploading. The platform indexes everything here and uses it in the next step to identify systems and components.

No documentation at hand? Choose Describe the site instead and describe each technical system in your own words: what it serves, how it is controlled and which sensors it has. The setup assistant asks about what it still needs, and you can finish at any time. When you finish, your description is listed with the documents and used in the next step like them; it counts as this setup's document. A description you leave before finishing is continued the next time you open it in the same setup. Next needs at least one technical document or a finished description, and at least one point list.

Niagara MQTT sites: the point export you uploaded on the Step 2 card counts as the point list and is listed here as well.

Airthings sensors: with an Airthings credential, the setup reads your devices from the API. Without one, upload the device-list export from the Airthings dashboard as a CSV on the Airthings card in "Integrasjoner og kartlegging".

Gjennomgå funn

Trollmann kjører over opplastingene fra "Last opp dokumenter" og foreslår systemene, for eksempel ventilasjonsaggregater, varmesoner og kjølekretser, og komponentene, for eksempel vifter, spjeld, sensorer og ventiler, som finnes i bygget. Jobben din her er å gå gjennom forslagene, godta det som stemmer, og fjerne haken på det som er feil. Bruk søkeboksen til å filtrere og "Tagged only"-bryteren for å fokusere på elementene Trollmann er trygg på. Trollmann kan også stille oppklarende spørsmål mens den kjører. Svar i spørsmålspanelet, så fortsetter den der den stoppet.

The words on this step

You will see a handful of technical words on "Gjennomgå funn". You do not need to master them to continue — the platform fills them in from your documents and the address list — but this is what they mean.

• System: one piece of building equipment with its own job — a ventilation unit, a heating circuit, a cooling circuit.
• Component: one part of a system — a fan, a damper, a valve, a temperature sensor.
• Tag: the short code your building uses to name a component, taken from your drawings and the BMS (for example RT400 for a temperature sensor). A tagged component is one the platform could match to your naming; "Tagged only" shows just those.
• Type: what kind of component it is — sensor, fan, valve, and so on. "Unknown" means the platform has not decided yet; it is not something you have to fill in.
• Datapoint: one live value the BMS can read or write — a measured temperature, a fan speed, a setpoint. Mapping is the link between a component and its datapoint, so that the platform reads the right value and writes to the right place.

What you are asked to do is only this: uncheck any system that does not exist in your building, that you do not want controlled, or that does not yet have full sensor coverage, and any component that does not exist; then answer the questions the Wizard asks in plain words. An unchecked system and its components are left out of this setup, and you can add the system later. Everything else — tags, types, datapoints, mappings — is the platform's work, and the counts on the screen change while it runs. If something looks wrong and you cannot tell why, ask through the "Ask Helper" button or leave a note for us; do not guess at a type or a datapoint.

Save and Next

Next saves your review the same way Save does, then moves on to the next step. Save records your review and stays on "Gjennomgå funn" — use it when you want to keep working here, for example to answer a question or wait for the analysis to finish. If your review cannot be saved, the setup stays on "Gjennomgå funn" and tells you why in plain words; nothing is lost.

Driftsanalyse

For bygg med tilkoblet SD-anlegg leser plattformen nåværende tilstand: faktiske settpunkter, gjeldende temperaturer og viftemoduser. Den bruker øyeblikksbildet til å lage målebaserte standardverdier i stedet for generiske. For nyinstallasjoner som ikke er koblet opp ennå, kan du hoppe over dette steget og bruke standardverdier; du kan komme tilbake senere og kjøre det på nytt. Øyeblikksbildet danner også grunnlaget for reserveverdiene for Watchdog i "Watchdog-oppsett", så det er verdt å kjøre hvis SD-anlegget er tilgjengelig. This is currently wired for IWMAC; if no IWMAC credential was selected in Step 2 — a Niagara MQTT site, for example — the step says so: press "Hopp over — bruk standardverdier" and go on.

Konfigurasjonseditor

Plattformen gjør systemene og komponentene du godtok i "Gjennomgå funn" om til et utkast til styringskonfigurasjon. I "Konfigurasjonseditor" går du gjennom og finjusterer utkastet: gå gjennom hvert system, åpne en komponent for å inspisere datapunktkandidatene plattformen plukket fra adresseliste-CSV-en, juster tildelingen hvis den valgte feil punkt, og bekreft styringstypen for hvert system. Lagring her genererer forhåndsvisningen av konfigurasjonen som de neste stegene ruller ut.

Watchdog-oppsett

Watchdog er sikkerhetsmekanismen bak skriving av settpunkter: når plattformen skriver en verdi til SD-anlegget, må SD-siden ha en reserveverdi slik at anlegget ikke blir stående på den siste verdien vi skrev hvis tjenesten vår stopper. Om du faktisk må gjøre noe i "Watchdog-oppsett", avhenger av hvilket SD-anlegg du har koblet til.

1. IWMAC: "Watchdog-oppsett" leder deg gjennom overleveringen — last ned Watchdog Request-CSV-en, send den til IWMAC-kontakten, og last opp Endpoints-CSV-en de sender tilbake. Det er denne runden som ofte tar dager; sett av kalendertid til den.
2. Niagara-only sites (no IWMAC credential): "Watchdog-oppsett" has nothing to configure. Whether the station reverts a setpoint on its own if our writes stop is something your supplier tells us — it is one of the questions in the owner guide's supplier message. Click Next.

Se den SD-spesifikke guiden for leverandøren din for hva leverandøren forventer på hver side, og for den grundigere forklaringen av hvorfor Watchdog er viktig.

Utrulling og test

Above the buttons, a readiness list shows what deploying this site depends on: whether you have uploaded the configuration in this setup session and, when your setup includes those steps, the analysis of your documents and data and the watchdog protection from the watchdog step. Each item says Ready, Outstanding or Needs attention in plain words. Upload to CMS waits while the analysis is still running or waiting for an answer, and stays off if the analysis stopped with an error or stopped without finishing (start it again from the review step); if the analysis has not run for this setup, you can still upload the configuration you generated. Deploy Site becomes available once the configuration is uploaded and every other item is Ready. Only watchdog protection may stay Outstanding — you can deploy without it, but setpoints are then not protected. If you change the configuration after uploading it, upload it again. Use "Check again" after you have gone back and changed something.

Then there are three actions, in order: Upload to CMS pushes the generated configuration into the platform for validation; Deploy Secrets writes the credentials you entered in Step 2 into the cluster so the live pods can authenticate against the BMS and sensor APIs; Deploy Site rolls out the per-site service. After deployment, the endpoint test panel is available so you can confirm that reads and writes work end to end before you leave site setup. Read each action's status before pressing the next button.

Sites whose only connection is issued by us (Niagara MQTT): the platform team completes the deployment. Tell us when you have reached "Utrulling og test", and you are done here.

Hvis noe går galt

Almost everything in site setup is recoverable before deploy. The setup saves a draft after each step, so closing the tab does not lose progress. To change an answer, go back to the step where you gave it and change it there, then re-run what depends on it — for example, change which devices belong to the site in Step 2 and re-run the analysis in "Last opp dokumenter". Until you press Deploy Site in "Utrulling og test", nothing in the cluster has been changed; the site only becomes "real" once that succeeds.

If you started a draft you no longer want, delete it from the resume list in Step 1. Before the site is registered, Step 1 also offers "Forkast disse svarene" to clear what you entered there. If a deployed site needs to come down, that is a separate operation outside site setup — open the assistant and we will take it from there.