IWMAC is a cloud-based SCADA platform for managing technical building installations. When a site already uses IWMAC, our platform can read live values and write approved setpoints through the IWMAC Cloud API. This guide lists what you, or your IWMAC contact, need before starting the new-site wizard.

What to request from IWMAC

IWMAC issues API access per customer account. Contact your IWMAC representative and ask them to provide the four items below for this specific site.

1. API credentials (Client ID + Client Key)

Two values tied to your customer account in IWMAC. The Client ID is short and identifies the account; the Client Key is a long secret used to obtain a session token. The same pair can cover several sites, so you normally do not need a new pair per building unless your IWMAC contact prefers it.

2. Plant ID for this site

IWMAC identifies each physical site by a numeric Plant ID (for example 2117 or 3653). You need one Plant ID per building you want to onboard. Ask IWMAC for the Plant ID that matches the address you are setting up.

3. API authorisation for the Plant ID and units

Credentials are not enough on their own. IWMAC must explicitly authorise your Client ID for the Plant ID and the controller units inside that plant. Ask them to enable API access for this Plant ID and confirm which units are included, such as ventilation, heating, or cooling. If a unit is missing here, calls for data points in that unit will return "no access" even when the credentials are valid.

4. Address list export (raw IWMAC CSV)

IWMAC can export an address list with every data point for a plant: sensors, setpoints, status values, and similar signals. This is the raw export from their portal. The platform parses it during upload, so you do not need to clean it up or rename anything. At minimum, the file must contain these columns:

1. unit_id — the controller unit ID (e.g. VV_2515 or 911).
2. unit_name — human-readable controller name (e.g. "Cylon PLS", "Hovedmåler EL").
3. driver_id — the long internal address string IWMAC uses for the point.
4. driver_id_no — the short numeric ID the API uses to reference the point.
5. alias_text — short description of the point, such as "Communication status" or "Supply temperature SP".
6. eng_unit — engineering unit, when defined, such as °C, %, or kW.
7. att — read/write attribute, such as r or rw.

Where each piece goes in the wizard

After you have the four items above, the new-site wizard walks you through the rest. The wizard has eight steps; IWMAC inputs land in five of them. Use this as a map:

1. Step 2 — Integrations & Discovery: choose IWMAC, paste the Client ID and Client Key into a new credential, and enter the Plant ID for this site as a credential override. The IWMAC card also has a "Request Watchdog protection (recommended)" checkbox; leave it ticked unless you have a specific reason not to use the watchdog (it is the safety mechanism described below). When unchecked, Step 7 becomes a no-op — the wizard skips watchdog registration entirely, and the generated config does not include a heartbeat node. Click Verify — the platform requests a token from IWMAC and confirms the credentials and the Plant ID work. A green tick means you can move on.
2. Step 3 — Upload Documents: upload the raw IWMAC address list CSV alongside any HVAC documentation (P&IDs, schematics). The platform parses the CSV during upload, so you do not need to clean it first.
3. Step 4 — Review Detected Items: accept the systems and components the platform extracted from the address list and the documents. No new IWMAC input here.
4. Step 5 — Operational Analysis: the platform uses the IWMAC credential from Step 2 to read a live snapshot from the Plant ID — current setpoints, temperatures, fan modes — and uses it to seed evidence-based defaults instead of generic ones. The snapshot also seeds watchdog fallback values in Step 7. If you skipped IWMAC in Step 2, you can skip this step too.
5. Step 6 — Visual Config Editor: review the generated configuration; no new IWMAC input.
6. Step 7 — Watchdog Setup: see the next section. This step uses the IWMAC credential to register the watchdog endpoints once IWMAC has returned the Endpoints CSV.
7. Step 8 — Deploy & Test: Upload to CMS pushes the configuration; Deploy Secrets writes the IWMAC credential into the cluster so the running pod can authenticate; Deploy Site rolls out the per-site service. The endpoint test panel then lets you confirm reads (and writes, if you control setpoints) work end to end.

The watchdog (writing setpoints safely)

When the platform writes a setpoint to IWMAC, IWMAC's watchdog checks that we keep refreshing it. If our writes stop because of an outage, a network problem, or decommissioning, the watchdog returns the setpoint to a safe fallback value. This prevents the building from staying on the last value we wrote. The watchdog is mandatory for sites where we control setpoints and is set up once, in two parts:

1. Step 7A: the wizard generates a Watchdog Request CSV based on the setpoints the new configuration will write. For each setpoint, confirm the fallback value, often the current BMS value, and add any notes IWMAC needs.
2. Send the Watchdog Request CSV to your IWMAC contact. They configure the watchdog rules on their side.
3. IWMAC sends back a Watchdog Endpoints CSV. It is usually semicolon-separated and contains columns such as driver_id_no;unit_id;alias_text;eng_unit. This maps each setpoint alias to the watchdog driver ID number IWMAC has created.
4. Step 7B: upload the endpoints CSV exactly as IWMAC sent it. The wizard stores the mapping so the running integration knows which addresses to refresh.

A short message to send your IWMAC contact

Use the lines below as a starting point. Replace the bracketed placeholders before sending.

1. We are connecting [site name / address] to a third-party HVAC control platform via the IWMAC Cloud API.
2. Please provide a Client ID and Client Key for our account.
3. Please confirm the Plant ID for this site and enable API authorisation for that Plant ID and all controller units we will be reading from and writing to.
4. Please send the standard address list CSV export for this Plant ID, the one containing unit_id, unit_name, driver_id, driver_id_no, alias_text, eng_unit, and att. Include all units; we will filter on our side.
5. We will follow up with a Watchdog Request CSV. Please be ready to register the watchdog rules and return the corresponding Watchdog Endpoints CSV.

Stuck on something?

If IWMAC needs technical details you do not have, such as token format, API endpoints, or error codes, open the assistant and we will help you draft a reply.