Supply Chain Lab

Data boundary · release 2026.07

Privacy & research status

The deployed Lab is configured for routine teaching only. Research/reflection collection is off; a separate optional anonymous quality pulse stores activity-level aggregates.

Teaching-only mode active
Important: this technical configuration does not grant an ethics exemption and is not a substitute for an RMIT determination. Aggregate routine quality feedback may support reflective teaching and a promotion narrative subject to university policy; do not treat it as SoTL research data or publish classroom responses as research without the appropriate determination.

Identity in the activities

  • Activities ask for no login or identity: each class device receives a random Learner-XXXXXX alias derived from a browser-session token.
  • No activity asks for a name, Student ID or email address.
  • The random alias cannot reveal identity and expires with the session data.

QA aggregates at write

  • The optional pulse requests one 1–5 rating, pre-set choices and an optional short comment.
  • Ratings and choices immediately become activity totals; no response row is created.
  • Comments enter one unlinked pool after common identifiers are redacted.

Writing stays local

  • Reflection, evidence and rubric drafts remain in the student’s browser storage.
  • No reflection/evidence request is sent to the server.
  • Students can export or clear their local notes.

Short-lived operations

  • Only live class coordination, score and simulation state are stored.
  • Every participant item carries a 24-hour expiry timestamp.
  • The application excludes expired records without waiting for AWS physical deletion.

Lab requests

  • Problem reports and game suggestions can be submitted anonymously.
  • Name and email address are optional and used only when the sender requests follow-up. Student IDs and sensitive information are not requested.
  • Requests, workflow status and internal notes are visible only in the instructor request tracker and expire after 730 days.

Exact data boundary

What the live deployment does and does not receive.

Swipe the table sideways to read every column.

AreaServer receivesServer does not receivePurpose / availability
Access gateSigned page/class token and secure authentication cookie.No student account or RMIT login.Restrict access to the correct activity and session.
Live classSession code, internal random alias, activity page, score/metric and timestamps.No name, nickname, Student ID, email address, RMIT login, profile token or written reflection.Projector leaderboard and instructor control; participant rows become inaccessible within 24 hours.
CapstoneRandom alias, selected team role and team decision values.No supplied identity or demographic information.Coordinate the shared simulation; operational state becomes inaccessible within 24 hours.
Learning notesNothing.Reflection, evidence, rubric and notebook export.Stored only by the browser on the student’s device until they clear it.
Teaching QA pulseActivity-level rating/choice totals and an unlinked pool of optional comments.No name, Student ID, email, learner alias, class session, game code, grade or response timestamp.Routine teaching improvement and aggregate promotion evidence; rolling 730-day expiry. Skip sends nothing.
Lab requestsRole, current page, report or suggestion, submission time and workflow status. Name and email are optional.No required identity, Student ID, class result, learner alias or local notebook content.Operational maintenance and redesign planning; instructor-only review queue with a 730-day expiry.
AnalyticsAggregate page counts, action counts, date and UTC hour. A random browser token is hashed for approximate daily unique counts and the temporary hash expires within three days.No name, email, IP address, precise location, advertising ID, fingerprint, camera, microphone or third-party tracking pixel.Routine service improvement and operational monitoring; aggregate counters expire after 400 days.

Instructor rules for this mode

  • Do not ask students to disclose their alias.
  • Do not map aliases or QA totals to attendance or grades.
  • Do not combine QA exports with identified records.
  • Describe the pulse as perceived helpfulness, not proof of causal learning gain.

Residual boundary

A student could voluntarily type personal information into an optional comment. The interface warns against this and the server removes common emails, links, student numbers and phone-like numbers before storage, but free-text redaction cannot be guaranteed. Instructors should not request identifying text. AWS physical deletion after a TTL can be asynchronous.