A2 — Restore the Relay

How to participate#

In person is the preferred route. Use the campus teaching pack in the facilitated session, with the supplied apparatus or paper models and two distinct sending and receiving responsibilities. Keep your station sheets, predictions, revisions, receiver acknowledgements and explanation. These form the practical record; an additional browser run is not required.

Online, if you cannot attend: use the equivalent activity and control instructions below. The 3D environment supports the same reasoning, rehearsals and evidence requirements. Both routes use this brief’s deliverables and rubric. Label measured, paper-model and simulated results accurately.

Online control guide: restore a relay as a pair#

Your task: use your circuit-diagnosis evidence to verify the supplied relay, justify its archive and permission, and send a precise acknowledged handoff. This combines Weeks 5–8. Share one browser or screen and rotate control; there is no networked multiplayer.

1. Inspect the alternate worked example if useful. Divide the information: the sending student controls Systems/Investigator; the receiving student controls Coordinator. Each owns facts the other must request.
2. Open a new Baseline trial and inspect the mission console. Bring the sender’s Lab 5 diagnostic trace showing how a chosen test distinguished plausible faults. In this compact trial, Power bay offers one combined Measure supply and fuse test, a replacement and a switch. Predict what that test can establish, retain its original result before changing the fuse, then verify the load. The compact check alone does not demonstrate independent test selection.
3. The sender compares the current signed source and copy records in Control room, then derives permission expectations from the mandate. Select and test a supported copy and policy edit. The receiver asks what each check establishes, including its limits.
4. The receiver inspects their acceptance card in Archive. Communicate the item, destination, condition and exact read-back code to the sender. Confirm the verified profile before submitting Send structured handoff. A vague acknowledgement or a stale code fails the receiving condition.
5. At Dispatch, transmit only after the required evidence is complete. Collect the acknowledgement, check the receiving terminal and deliver it. Finish and export the trial; preserve the checkpoint.
6. Swap responsibilities and run Conflicting archive, or the published maintenance-hold case with its changed handoff. The source or acceptance requirement has changed; the old answer is insufficient. Retain both records and explain which messages prevented a wrong transmission.
7. Keep the full permission audit and changed-card communication evidence from Labs 7–8. Assemble the joint explanation and individual contribution statements after playing.

The role cards stay accessible for solo practice. In paired assessment, give each person their card and exchange the necessary information aloud or in an accessible text channel; do not simply let one person operate both roles without documenting it.

You are finished when: you have a completed relay record, a preserved checkpoint and revision, evidence of role rotation, and the full submission bundle. The compact trial does not replace the lab records that demonstrate all nine policy checks and read-back under changed conditions.

Playing in fullscreen: choose Fullscreen mission. Use its Mission & controls panel for the journal, role and area switches, and equipment. Scroll over the scene to zoom; click and drag to turn with the cursor free. Press X to lock it for mouse-look and X again (or Tab) to free it for scrolling and choosing options. Esc or Exit fullscreen returns to the page. The joint written account comes after playing.

The brief#

In pairs, restore a fictional recovery relay. The sending role holds equipment/source evidence; the receiving role holds the acceptance conditions and current acknowledgement code. Rotate roles so each person explains the diagnostic evidence and performs communication. The compact relay checks application; the linked Lab 5 trace demonstrates independent diagnosis.

The relay challenge combines the Week 5 circuit, Week 6 archive comparison, Week 7 permission matrix and Week 8 explicit handoff. Earlier observation and spatial skills help you inspect the system. Use the campus trial pack for a tabletop equivalent.

Checkpoint and final deadline#

Checkpoint: 23 April 2027, 17:00 Canberra time. Preserve your initial circuit diagnosis, source comparison and repaired permission matrix. Record which role performed each check. This checkpoint is formative and does not create an additional assessment weight.

Final: 30 April 2027, 17:00 Canberra time. Complete the coordinated handoff and changed-condition response. Preserve both the initial checkpoint and final record.

What you hand over#

Where each submission item comes from#

Assemble one labelled bundle using the assessment template. One export can support several rows; identify the relevant actions or sections.

The practical evidence and your explanation together form the submission. Keep the original checkpoint and revised files separately so the change can be followed.

The changed situation#

Choose the published maintenance hold or amended archive reference as a revision case. Preserve the old decision, state the new authority and change only the affected expectations. For your changed handoff evidence, complete Lab 8’s Transfer challenge using its published destination, quantity and code, then document the read-back and acknowledgement. Name the revision case and the handoff case in your account so each record is clear.

A justified change of archive copy is stronger than repeating a once-correct selection after the reference changes. Denying all permissions is not a useful repair when legitimate read and certification work must continue.

How to work as a pair#

Use one shared browser state with rotating control, or divide role packs and communicate through a shared screen. There is no live multiplayer server. The selected role label identifies the action source but is not proof of a person’s identity; your contribution account supplies that context.

A partner’s absence does not erase completed individual work. Preserve it and follow the published contribution policy. Feedback is scheduled within seven days to inform the final team mission.

Criterion-specific performance standards#

Diagnosis — 30%#

• Outstanding: Isolates the circuit and policy faults using discriminating checks and verifies the resulting system.
• Competent: Diagnoses the main faults and provides broadly sound checks.
• Developing: A working state is reached but key causes or checks are missing.
• Insufficient: No supported diagnosis or unresolved contradiction with the supplied rules.

Evidence — 20%#

• Outstanding: Uses source identity, completeness and the current signed reference; limits are explicit.
• Competent: Selects relevant records and supports the main conclusion.
• Developing: Relies on labels or timestamps without checking their authority.
• Insufficient: No usable source comparison or unsupported evidence claims.

Coordination — 25%#

• Outstanding: Both roles contribute, rotate and use precise instructions with documented read-back.
• Competent: Responsibilities and handoffs are clear with minor gaps.
• Developing: One role dominates or communication assumptions remain unresolved.
• Insufficient: No credible paired coordination or contribution evidence.

Adaptation — 15%#

• Outstanding: Explains and tests the changed mandate or handoff while preserving the earlier state.
• Competent: Makes a justified revision with some testing.
• Developing: Changes the answer without explaining the affected requirement.
• Insufficient: Ignores the changed condition or overwrites the only original record.

Traceability — 10%#

• Outstanding: The joint account reconstructs actions, roles, versions and assistance without ambiguity.
• Competent: Most decisions and contributions can be followed.
• Developing: Missing role labels or version links make important work difficult to assess.
• Insufficient: Unusable record or unclear authorship.

Format, export and access#

Use the downloadable template, retain editable source and export a readable record. The website provides downloads and local practice; it does not submit to an institutional system. The browser and campus routes assess the same concepts and problem-solving outcomes. Neither automatically certifies physical dexterity.

All due times use 17:00 Canberra time on the published date. Policies and support explain attribution, accessible alternatives, contribution disputes, saving and extensions.