diff --git a/content/modules/report_module_activity.png b/content/modules/activities/images/rpt_mod_sessions.png similarity index 100% rename from content/modules/report_module_activity.png rename to content/modules/activities/images/rpt_mod_sessions.png diff --git a/content/modules/rpt_module_staff.png b/content/modules/activities/images/rpt_mod_staff.png similarity index 100% rename from content/modules/rpt_module_staff.png rename to content/modules/activities/images/rpt_mod_staff.png diff --git a/content/modules/activities/iteration.md b/content/modules/activities/iteration.md index 5981e40f295a3f09af31a617549b9ad47033b24a..78f031bcfeaafd1f688c74e05ac7dd69e9be5c9c 100644 --- a/content/modules/activities/iteration.md +++ b/content/modules/activities/iteration.md @@ -51,7 +51,7 @@ Remarks can be used to communicate anything extra to the timetabling team. We us ## Duplicating Iterations -Sometimes, it is neccerary mass-create duplicate iterations (for example, for assessments). You can *right click* on a row to duplicate entries: +Sometimes, it is useful to mass-create duplicate iterations (for example, for assessments). You can *right click* on a row to duplicate entries:  diff --git a/content/modules/activities/staff.md b/content/modules/activities/staff.md index 2ddedca59630d4289ded10d06faeee3e8a54d1ca..b7cccf25236ab19d8a4172fbbe27c40d18d88067 100644 --- a/content/modules/activities/staff.md +++ b/content/modules/activities/staff.md @@ -5,3 +5,13 @@ title: Staff Hours When you have a complex module which lots of activies which have multiple iterations and which run over multiple weeks it can be tricky to keep track of the number of hours being requested for staff. The _staff hours_ view shows the total number of hours across iterations for a staff member. + + + +### Staff Members + +Each staff member is listed one per row, the total hours per activity is shown. If a staff member is attached to multiple iterations, the sum of all hours will be shown in the column. + +### Activities + +Each column represents an activity type. The number of hours attached to each of this activities is shown in each cell. diff --git a/content/modules/activities/weekly.md b/content/modules/activities/weekly.md index eda4bb640b6aec24455f8c3b4ba4259a0ad4f8c0..c886fb7d9bf595652ea9ed01a0325e3cf2abb178 100644 --- a/content/modules/activities/weekly.md +++ b/content/modules/activities/weekly.md @@ -4,7 +4,7 @@ title: Weekly View It's useful to see how this module will look when planned out on a week-by-week basis. The tool features a weekly planning report to show this. -**SCREENSHOT HERE** + ## Weekly Breakdown diff --git a/content/reports/images/report_module_activity.png b/content/reports/images/report_module_activity.png new file mode 100644 index 0000000000000000000000000000000000000000..6aea99c37195e78e8eecc3e77ff206ac372ff2d5 Binary files /dev/null and b/content/reports/images/report_module_activity.png differ diff --git a/content/reports/images/rpt_module_staff.png b/content/reports/images/rpt_module_staff.png new file mode 100644 index 0000000000000000000000000000000000000000..39f5236b5069000d2de865b2d82e6e316d47e2da Binary files /dev/null and b/content/reports/images/rpt_module_staff.png differ diff --git a/content/modules/rpt_space_util.png b/content/reports/images/rpt_space_util.png similarity index 100% rename from content/modules/rpt_space_util.png rename to content/reports/images/rpt_space_util.png diff --git a/content/modules/rpt_staff_usage.png b/content/reports/images/rpt_staff_usage.png similarity index 100% rename from content/modules/rpt_staff_usage.png rename to content/reports/images/rpt_staff_usage.png diff --git a/content/reports/query.md b/content/reports/query.md index 2cd62aa11d44d2590e2398aee45dae49cf848d6b..8bf6a9e916345d56f2dcada56fa46882b94b3137 100644 --- a/content/reports/query.md +++ b/content/reports/query.md @@ -2,5 +2,4 @@ title: Staff Query --- -It can be tricky to keep track of which sessions are running in which week across all modules. This view provides the ability to see which sessions a staff member is attached to (for example, for rebalacing workload). - +It can be tricky to keep track of which sessions are running in which week across all modules. This view provides the ability to see which sessions a staff member is attached to (for example, for rebalancing workload). diff --git a/content/reports/room.md b/content/reports/room.md index a57234ce0f216776c01ed2052145548e683faaab..b1863631d0eca8794d2e381c2c5bddd81c3f102d 100644 --- a/content/reports/room.md +++ b/content/reports/room.md @@ -2,10 +2,18 @@ title: Room Reporting --- -Room availablity can be a common issue during the planning cycle. We need to make sure we are making effective use of the spaces available, and are not requesting too much in one location (making it impossible to schedule). This view lets staff see how much has been allocated as guide to aid planning. +Room availability can be a common issue during the planning cycle. We need to make sure we are making effective use of the spaces available, and are not requesting too much in one location (making it impossible to schedule). This view lets staff see how much has been allocated as guide to aid planning. MPyT also has no knowledge of room capacities -- it treats a room pool as a uniform 'block' of hours. It therefore cannot warn about issues relating to capacities, special requirements, etc... (eg, it can't tell the difference between chapel and exchange lecture theatre), which must be resolved after the fact. It also doesn't know about rooms in multiple pools. Due to this quite simplistic model, this report is (_very_) optimistic regarding maximum room pool capacities. Real world constraints often mean it is not _possible_ to fully schedule a space at the best of times. Please treat this view as **guide only**. We might be able to improve on this in future iterations, but this will never be perfect (we'd have to handle the full timetabling process for it to be 100% accurate!). -**SCREENSHOT HERE** +# Room Report + +The room report can be found in the *reports* menu, it looks like this: + + + +### Total Hours + +As a **guide**, the total hours column shows how many hours have been requested across the study block. Be aware that perfect utilisation of space is often not possible, and shared spaces may already have allocation attached to them (eg, other departments, rooms in multiple pools, or Exeter usage) and this will not be reflected in the tool. diff --git a/content/reports/staff.md b/content/reports/staff.md index 7f24f408a605c5ddea367bdc8d6e6cbd067cd958..0c71fb510b51266168afefd742cfa1dcab1d4507 100644 --- a/content/reports/staff.md +++ b/content/reports/staff.md @@ -6,4 +6,10 @@ Staff workload considerations are an important part of the planning cycle. This The 'staff report' is available in the 'Reports' menu and will show a week-by-week breakdown of the activities attached to a staff member. If you want more detail, you can use the [Staff Query](../query) tool to find which sessions are scheduled in a given week. -**SCREENSHOT HERE** + + +This report shows a week-by-week breakdown of the staff hourage by each study block. The _total hours_ column shows the sum of the hours across all modules and activities. This can be used to identify issues with staff workload and working patterns. This is at the granularity of weeks, so if staff have working pattern constraints this will need to also be taken into consideration. + +## Hours remaining + +As a **guide**, the hours remaining column shows the number of hours allocated vs the workload model hours (assuming an equal split in study block one and two). A positive number assumes there are hours still available, a negative number indicates a possible bias towards this study block.