Planning for floods — Technical https://thesis.uya.no/proposals/plan-for-the-unexpected/#technical-track BACHELOR Final result: A planning prototype and a list of workflow improvements. Task: Build a flood-response planning screen using a fixed nearest-feasible assignment rule. Data: 20 flood scenarios; seeds 1–20 (planned) 10×10 grid, 20 incidents, 5 teams, 10 blocked edges; close 5 more edges at minute 120 of a 4-hour exercise. Include arrival, priority and service duration. Requires: Recruit preparedness staff or experienced volunteers and a scenario reviewer; report the actual participant roles. Method: Use the synthetic roads, requests and crews; test reachability and capacity, then run coordinator walkthroughs. Plan 4 participant sessions. STEPS Build and test 1. Read the starting sources and choose one established implementation method. 2. Write the requirements, data fields, system diagram and test cases. 3. Prepare 20 flood scenarios; seeds 1–20. Make the answer key and pass criteria before testing. 4. Build a working version of a planning prototype and a list of workflow improvements. 5. Run function, integration and failure-case tests. Record each result. 6. Run the practical evaluation and list the changes the system still needs. MASTER Final result: Scenario generator, planning map and paired comparison. Research question: Investigate whether priority-constrained allocation remains useful after a road closure. Compare fair priority-nearest and constrained matching on identical events; analyse feasible coverage before travel and how coordinators interpret replanning. Research result: Design knowledge about priority preservation and explainable replanning under disruption. STEPS Design, build and test (DSR) 1. Read the newest papers and list the closest existing systems. 2. Write down the versions, fields, data split, case assignment, random seeds and correct answers for 20 flood scenarios; seeds 1–20. 3. Draw the user workflow, data model and system architecture. List the requirements and pass criteria. 4. Build a working version of scenario generator, planning map and paired comparison. 5. Test every function, connection and failure case. Save the failed tests as well as the passed tests. 6. Compare the system with the named alternative. Then run the user task or decision task in the assignment. 7. Report the measured result, the failed cases and the design lessons another team can reuse. CURRENT PROJECT LITERATURE A web-based decision support framework for optimizing road network accessibility and emergency facility allocation during flooding (2024, peer-reviewed): https://doi.org/10.1007/s44212-024-00040-0 Shows a current flood-routing decision-support artifact and stakeholder-facing web implementation. Assessment and Improvement of Emergency Rescue Service Accessibility under Urban Waterlogging Disasters (2024, peer-reviewed): https://doi.org/10.3390/w16050693 Provides current accessibility measures and disruption scenarios for emergency allocation. IS THEORY STARTING POINTS Vessey & Galletta (1991) — Cognitive Fit: https://pubsonline.informs.org/doi/10.1287/isre.2.1.63 Test whether a representation helps one kind of task more than another. Wang & Strong (1996) — Beyond Accuracy: https://www.tandfonline.com/doi/abs/10.1080/07421222.1996.11518099 Distinguish accuracy, completeness, representation and fitness for the task. Search Scopus or Web of Science and ACM Digital Library using the topic query, then follow citations to the thesis start date. Record searches and compare methods, data, findings and limitations in literature-matrix.csv. Use that review to confirm or revise the gap and choose a current comparator. The linked papers are starting points. PILOT QUESTION How do allocation recommendations and changing road information affect preparedness decisions? EXAMPLE TOOLS Python, NetworkX, OR-Tools, Streamlit Equivalent tools are fine. FIRST THREE ACTIONS 1. Generate one connected road grid and check reachability after removing blocked edges. 2. Write one feasible manual allocation, then implement first-come-first-served with the same travel constraints. 3. Replay seed 1 with the planned closure and validate response-time calculations before comparing planners. LITERATURE SEARCH emergency resource allocation decision support uncertainty DATA 20 flood scenarios; seeds 1–20 (planned) 10×10 grid, 20 incidents, 5 teams, 10 blocked edges; close 5 more edges at minute 120 of a 4-hour exercise. Include arrival, priority and service duration. HOW TO TEST IT Replay identical revealed events; count unserved incidents by priority, response time and reroutes. Six preparedness-experienced participants revise 4 non-overlapping cases across modes; record correction time, omissions and override reasons. FINAL RESULT Scenario generator, planning map and paired comparison. ACCESS OR PEOPLE Recruit preparedness staff or experienced volunteers and a scenario reviewer; report the actual participant roles. TEMPLATES https://thesis.uya.no/starters/plan-for-the-unexpected/technical/data-plan.csv https://thesis.uya.no/starters/plan-for-the-unexpected/technical/evaluation.csv https://thesis.uya.no/starters/plan-for-the-unexpected/technical/literature-matrix.csv Use participant codes instead of names or email addresses.