IoT
Systems Design
Campus mission · 4 operations
 Mission dossier · ready
Assignment brief · Campus IoT programme

You are the
systems design team.

Campus operations has a connected-system programme to deliver. Your job is not to pick fashionable technologies: it is to turn operational needs into a design you can explain, defend and revise when the evidence changes.

Enter Mission 01 → No mission work filed yet on this device.
Operating rule: expose the need, assumptions and constraints before defending a technology.
Your role

You own the system-level decisions.

Campus operations sets the outcomes. Field, network and platform teams bring constraints, evidence and incidents. Your responsibility is to turn that information into a connected system that can actually work — and to explain why your design still makes sense when the situation changes.

Your job is not to guess the “best” technology.Start from the need, make assumptions explicit, then defend the architecture that follows.
01Structure the systemTurn needs into components, responsibilities and flows.
02Make design choicesSelect communication and placement strategies from explicit constraints.
03Defend the reasoningSeparate facts, assumptions and engineering decisions.
04Revise when evidence changesTrace what breaks, what survives and what must be redesigned.
Your counterparts

They bring the problem. You own the design.

These four people recur throughout the campus case. They do not reveal the answer: each one changes the evidence your architecture must survive.

AM
AminaCampus operations leadservice outcomes · operating constraints
ST
SamField techniciandevices · environment · incidents
YN
YanisNetwork architectconnectivity · infrastructure · responsibilities
LE
LeilaPlatform engineerapplications · data · interoperability
Your mission dossier

Your decisions follow the system.

Major architecture choices, constraints, assumptions and open issues are filed in one evolving dossier. Later missions can reopen them when new evidence arrives — so a previous choice may have to be defended, revised or dealt with as a consequence.

MISSION DOSSIERNot started

Complete Mission 01 to begin filing structural design decisions.

Your mandate

Four responsibilities. One system.

The missions are successive engineering responsibilities, not four independent chapters.

01Establish the systemTranslate a physical-world need into responsibilities, components, flows and explicit communication requirements.
02Make exchanges workDefine interaction patterns, protocol responsibilities, protocol composition and shared data meaning.
03Place computationDecide what belongs on the device, nearby, at the edge or in the cloud as constraints change.
04Break your own designExpose failure assumptions, challenge dependencies and revise the architecture beyond nominal conditions.
Operations board

Your current mission.

Each operation changes the same campus system. Completed missions remain available as evidence; later missions open as the programme advances.

Mission status
FINAL DEBRIEFYour reusable system design mapMission → architecture → communication → guarantees → revision. Opens as the course-level synthesis after Mission 04.
Final debrief · locked