Niagara: connect your building to us

You own or manage a building with a Niagara (Tridium) system, and a supplier looks after it. You will do three things yourself — add the site in site setup, forward one message and two files to your supplier, and check one screen — and you will wait on us twice: we issue the connection, and we do the final deployment. Your supplier does the technical work.

Niagara with a broker you host (not offered)

Words you will meet

• Station — the Niagara computer in your building that your supplier configures. It is the thing that connects to us.
• Connection sheet — one page we send once, with the address, username and password for your building. The password on it is shown once and is never sent again.
• Certificate file (mqtt-ca.crt) — a small file that lets the station trust our connection point. It goes into the station, not onto your PC.
• Point — one value the station can send: a temperature, a fan speed, a setpoint. The point list is your supplier's list of them.
• Site setup — the guided flow in this app under Bygg → "Legg til bygg". It creates the site and, at the end, the configuration we deploy.

Before you start

1. You are signed in and an organisation is selected in the sidebar. If none is, "Lokasjonsinformasjon" shows a notice asking you to pick one from the sidebar before creating a site.
2. You have your supplier's contact — the person who configures the Niagara station.
3. You have at least one PDF that describes the ventilation systems in the building: a system schematic, a P&ID or an equipment list. "Last opp dokumenter" needs one.
4. You have decided one thing: should we only watch the building, or also adjust setpoints later? The answer goes into Step 1 and decides what we ask your supplier for.

Step A

Add the site in site setup

1. Go to Bygg and press "Legg til bygg".
2. In "Lokasjonsinformasjon", choose a short name for the site — lowercase letters, digits and hyphens only, 3–40 characters, no dots. This name becomes the permanent identity in the connection we issue (the username and the topic folder are derived from it), so choose it once.
3. Step 1 also asks for the "Tilknytning til dette bygget": how your organisation is related to the site. Whoever holds the service agreement for this building decides it.
4. Step 1 also asks what the site does. Nothing is pre-selected: pick an option marked "styring" only if you intend us to adjust setpoints later; otherwise pick "kun lesing" options. There is no screen for changing this later, so decide now. Your choice decides whether the message we generate for your supplier asks for writable setpoints.
5. Press Next. In "Integrasjoner og kartlegging", find the Niagara card. The page header talks about entering credentials and verifying — for Niagara there is nothing to type; the card is read-only and shows what we issued.
6. What you should see on the card: the pill "Utstedt"; the rows "Megleradresse", "Brukernavn", "Topic-område", "Utstyret publiserer til" and "Utstyret leser fra", each with a "Kopier" button; and a "TLS" badge.
7. Stop here. Do not press "Test MQTT-megler" yet — nothing is connected.

Step B

What you receive from us

1. The connection sheet: the address and port, the username, the password, and notes on the client id and keepalive.
2. The certificate file mqtt-ca.crt, which we send you together with the sheet.
3. A link to the technical page for your supplier — the next link on this page.

Niagara: technical setup for your supplier

Keep the password safe

Step C

Send this to your supplier

There are two messages. The first — below — tells your supplier how to connect; send it now, so the connection can be built while we read your documents. The second — the list of exactly which systems, components, measurements and setpoints we want the station to send — is generated by the app for your site once site setup has read your documents and confirmed the systems ("Gjennomgå funn"). It appears on the same card in "Integrasjoner og kartlegging"; send it when it appears. Nothing on that list is typed by you.

Copy the message, replace every [bracket] with the value from your Step 2 card (use the "Kopier" buttons), and send it. Send the connection sheet and the certificate file separately, on a secure channel.

Emne: [Byggnavn] — koble Niagara-stasjonen vår til den nye ventilasjonsplattformen vår

Hei [kontaktperson hos leverandøren],

Vi kobler [Byggnavn] til en plattform som leser ventilasjonsdataene våre og senere kan komme til å justere settpunkter. MQTT-megleren ligger hos plattformen; Niagara-stasjonen vår kobler seg UT til den over en kryptert forbindelse. Vi trenger ikke å åpne noe i brannmuren vår.

Alt du trenger, står på denne siden: [lenke til «Niagara: teknisk oppsett for leverandøren din»]. Kort fortalt:
- Adresse og port: [Megleradresse fra kortet mitt].
- Brukernavn: [Brukernavn fra kortet mitt]. Passordet og sertifikatfilen (mqtt-ca.crt) kommer separat over en sikker kanal — si hvilken kanal du foretrekker.
- Sertifikatfilen skal inn i stasjonens User Trust Store (ikke Key Store). Importer den filen, ikke sertifikatet stasjonen får presentert når den kobler seg til første gang — siden forklarer hvorfor.
- Punktene publiseres under [«Utstyret publiserer til» på kortet mitt]; hvis vi noen gang styrer noe, leser stasjonen under [«Utstyret leser fra» på kortet mitt].

Når stasjonen er tilkoblet, vil jeg gjerne at du sender meg dette:
1. Stasjonens egen eksport av MQTT-punktlisten (Niagara Workbench: punkttabellen til MQTT-enheten, eksportert som CSV). Alle formater går fint — plattformen tilpasser seg; du trenger ikke å skrive inn noe på nytt.
2. Én linje om hvordan punktene sendes: ved endring, eller med et fast intervall (og hvor ofte).
3. Om noe på stasjonen kan avvise eller overstyre et settpunkt (har bare betydning hvis vi senere styrer noe).
4. Valgfritt: den offentlige IP-adressen stasjonen kobler seg opp fra.
5. Valgfritt: om denne Niagara-versjonen stoler på vanlige offentlige sertifikatutstedere uten at noe må importeres.

Hvis stasjonen ikke vil koble seg til, fortell meg hva den melder og omtrent når du prøvde — plattformteamet leser loggen på sin side, og den viser om det stoppet på sertifikatet, passordet eller rettighetene.

Takk, [navnet ditt]

1. Send the sheet and the certificate file on the secure channel you agreed with your supplier.
2. Expect your supplier to schedule a session for the station. Nothing is needed from you until they say it is connected.
3. The answers to the numbered questions in the message come back to you. Keep them — Step D says where each one goes.

Information we must be precise about:

• The site id exactly as issued (the topic prefix).
• The broker address, the port, the certificate file and the login — from the connection sheet only.
• Your supplier's export of the point list — with the Type column filled for every row and Local Point filled for every point that publishes.
• Which points are writable, agreed with you; for each, the two topics and the Local Point Slot your supplier used.
• The units and precision (facets) per numeric point, so limits and setpoints are interpreted in the right unit.

Step D

What comes back, and how to check it worked

1. When your supplier says the station is connected: open Bygg → "Legg til bygg", pick the site from the draft list in "Lokasjonsinformasjon", go to "Integrasjoner og kartlegging" and press "Test MQTT-megler" on the Niagara card.
2. What you should see, line 1: "Ekstern tilgang" — "TLS og pålogging OK". The encrypted connection and the login work from the outside.
3. Line 2: "Utstyret" — "… topics publiserer under …" with a number: the station is talking. "Ingenting publiseres under … ennå" means the door works but no point has been sent yet — see the note below.
4. Save the point export your supplier sent, press "Last opp CSV" on the same card and choose the file. What you should see: "Lastet opp". If it says "Opplasting feilet" followed by a dash and a reason, copy the text after the dash and send it to us.
5. Tick "Bruk denne tilkoblingen for dette bygget". This is the one click that records the connection for the building. If the app answers that this site has no issued credential, we have not issued it yet — ask us.
6. Your supplier's answer to "how points are sent" (question 2 in the message): send it to us together with the export.

A setpoint we send counts as accepted only when the station reports the same value back on its own reading of that point. Your supplier seeing the value arrive is reception, not application.

Step E

Finish site setup

1. In "Last opp dokumenter", upload the PDF or PDFs. The point list you uploaded in "Integrasjoner og kartlegging" is already listed here.
2. In "Gjennomgå funn", review the systems and components it found and untick anything that is not in this building. The CSV validation box should be marked OK. Press "Lagre" and wait until the run completes; answer the questions it asks about the building, then go on.
3. In "Driftsanalyse", press "Hopp over — bruk standardverdier". This step reads live values from IWMAC systems only.
4. In "Konfigurasjonseditor", review what was generated. You are not expected to change anything you are unsure about.
5. In "Utrulling og test", tell us you have reached this step; we do the deployment for a site whose connection is issued by us.

If something goes wrong

• The card says "Ikke utstedt ennå — kontakt oss; vi utsteder påloggingen for dette bygget." → us. Send us the site name.
• Your supplier reports a certificate or TLS error → your supplier. The wrong file was imported, or it went into the Key Store; the technical page explains the re-import. A new password will not help.
• Login refused → check the username against the card. A lost password → we issue a new one.
• "Ekstern tilgang" OK, but still "Ingenting publiseres under … ennå" long after your supplier says it is connected → your supplier: are the points built and enabled?
• "Ekstern tilgang" shows "Avvist" → us. Send us the code shown next to it.
• Some points never show up → a value that never changes is sent only when it changes. Ask your supplier to publish each point once.
• It worked for weeks, then stopped → the station trusts our server certificate instead of the certificate file. Same fix as the certificate error above.
• A short outage of some minutes → usually maintenance on our side; the station reconnects by itself.
• Someone suggests turning off certificate checking on the station → no. Over the internet that would let a third party read the login and send setpoints.
• In "Last opp dokumenter", "Next" is greyed out → it needs at least one PDF and the point list.

What to expect over time

The address the station connects to may change one day. An address change is one field for your supplier to change; it does not by itself change the username, the password or the certificate file. Our server certificate renews on a schedule that a correctly set-up station never notices, because the station trusts the certificate file, not the server certificate. The certificate file itself is valid for 10 years.

Niagara: technical setup for your supplier

Etter idriftsettelse