Consumer multitasker v0.5

docs/support/docs/HOBL_Scenarios.md

@@ -21,6 +21,41 @@ Collect various system logs.
 
 Nonfuctional.  Needs to be updated for new architecture.
 
+## consumer_multitasker
+
+Use the HOBL UI to run the `ConsumerMultitasker_v0.5` workload. The scenario name exposed in the UI is `consumer_multitasker`.
+
+### Prerequisite: Enable diagnostic data
+
+To enable PerfMetrics collection, turn on diagnostic data on the DUT:
+
+1. Open PowerPoint.
+2. Open the **File** tab.
+3. Select **Account** in the lower-left section.
+4. Select **Manage Settings**.
+5. Check **Send Diagnostic Data**.
+6. Select **OK**.
+7. Close PowerPoint.
+
+### Run the workload
+
+1. Open the HOBL UI and create a new job.
+2. Add the `consumer_multitasker` scenario and configure it as follows:
+
+	| Setting | Value |
+	| --- | --- |
+	| Enabled | Yes |
+	| Tools | `perf_utc` (performance data), `power_light` (power data), `run_report` (results rollup) |
+	| Parameters | `enterprise_collab:perf_run=1`<br>`perf_utc:cm=1` |
+
+3. Submit the job. The HOBL UI automatically adds and runs the required prep scenarios before the measured workload.
+
+Results are written under the `result_dir` configured in the selected device profile. Each iteration produces:
+
+* PerfMetrics in `consumer_multitasker_<iteration>_PerfMetrics.csv`.
+* Power metrics in `consumer_multitasker_<iteration>_power_light_summary.csv`.
+
+The `power_light` tool requires the DUT to have a supported Maxim chipset. If the DUT does not have a supported Maxim chipset, use the battery rundown method to measure power instead.
 ## iperf3
 
 Runs iperf3 network throughput tests against a remote server while measuring power.