Campus access and cloud service responsibilities

Steps

Screens captured against IoT Ideator e0d4b9ccf661cd6c20a3efa24bab86c9ea7c9e30 on 2026-09-06; the tool may have moved on — the text steps are the contract.

1. 1 Step 1

   Do

   In the Working View canvas, select the Wi-Fi Module and inspect its access hop to AWS IoT Core.

   You will see

   Physical placement shows a 45 m hop against the mission’s 30 m teaching limit, leaving a 15 m deficit.

   Why it matters

   The chapter identifies network limits as part of cloud service use. A provider’s service boundary does not establish that your access path works.

2. 2 Step 2

   Do

   In the Site canvas, replace Wi-Fi with nearby NB-IoT, linking ESP32–NB-IoT by Data/UART and NB-IoT–AWS IoT Core by Data/NB-IoT.

   You will see

   Removing the old link breaks the route check. With UART within 15 m, the connected NB-IoT and restored-route checks pass.

   Why it matters

   A service model describes which layers the provider manages. Changing the access link repairs a different boundary: the device’s route to that service.

3. 3 Step 3

   Do

   In the Working View canvas, select the Fog Computing Node and inspect its connected alternative to AWS IoT Core.

   You will see

   The fog node remains connected beside the managed option. The drawn routes do not establish field connectivity or sensor accuracy.

   Why it matters

   The chapter’s traditional column leaves every stack layer with the customer. Comparing that boundary with a managed service exposes which operating work remains yours.

4. 4 Step 4

   Do

   In the Day panel, read Operating cost / day and compare it with the mission’s $1 daily limit.

   You will see

   The recorded model shows $0.0015/day for broker and transport. That estimate excludes wider labour and outage costs.

   Why it matters

   The chapter separates buying infrastructure from managing the layers above it. A transport estimate cannot represent all the work retained by the customer.

5. 5 Step 5

   Do

   In the Day panel, expand Service models and compare the 365-day totals and responsibility rows.

   You will see

   The recorded totals are $5,787.07 self-hosted and $2,190.59 managed. Both exclude migration, and the managed option retains shared responsibilities.

   Why it matters

   PaaS delegates infrastructure management while leaving application control with the customer. Reading responsibility rows beside costs makes the purchased boundary explicit.

6. 6 Step 6

   Do

   In the Scenarios panel, enter the managed total, build/run/patch/support owners, retained fog duty, shifted core duty, and shared access failure.

   You will see

   All four mission checkpoints pass and Reflect unlocks after the required entries. Saved explanations remain learner claims about the catalogue design.

   Why it matters

   Provider-managed services still leave governance, configuration, and verification duties with the customer. Naming the remaining owner prevents a service label from hiding that work.