Assignments

Assignment 1 - Design Ideation

Phoenix Force Design Ideation and Idea Generation Presentation 1

Video
Report
Images and text marked ✦ used AI - cited in Resources.

Goal of the Project

The goal of our project is to develop a modular wildfire response system that improves the early detection and monitoring of hot spots, which are critical in preventing flare-ups and fire spread. Our system combines mobile sensor modules with a base display module, allowing distributed detection of temperature, smoke, carbon monoxide, and other key indicators of fire activity. By using ESP-Mesh networking, multiple mobile units can cover wide areas, relay information to one another, and transmit data back to a central screen where conditions are clearly visualized. This provides firefighters and fire-watch teams with real-time, field-level situational awareness that is often unavailable in remote or high-risk environments. Ultimately, the project supports wildfire suppression by enabling faster responses, reducing blind spots, and ensuring that hot spots are identified before they reignite into larger, more dangerous fires.

Success metrics
  • ≤ 1 s alert latency (lab target)
  • ≥ 99% message delivery over ≥ 100 trials
  • ≥ 95% detection accuracy for chosen condition
  • ≤ 3 actions to complete the core task

Audience of the Project

Our primary audience is frontline wildfire responders, including firefighters, fire-watch volunteers, and emergency management teams. These groups need rugged, easy-to-use technology that functions reliably in harsh outdoor conditions while providing actionable information at a glance. Secondary audiences include researchers and community stakeholders who can use the collected data for environmental monitoring, long-term fire prevention strategies, and public safety education. By tailoring our design for professionals in the field while also making it understandable for broader audiences, our project bridges the gap between advanced sensor technology and practical wildfire response. The ultimate aim is to create a tool that not only aids trained responders in critical situations but also demonstrates to the public the importance of hot spot detection in protecting lives, property, and ecosystems.

Concept Generation

Scrollable list. Click any idea to pin as a pop‑up note.

Sensors & Detection

Temperature, smoke, CO, thermal camera, wildlife detection, lidar.

Power & Energy

Solar backpack, swappable batteries, kinetic/hand‑crank, fuel‑cell.

Comms & Networking

LoRa/ESP‑Mesh, cellular/satellite fallback, SMS relay, repeater mode.

Alerts & Feedback

LED codes, siren + voice, haptic wristband, AR overlays.

Durability & Safety

Fire‑retardant, waterproof, dust/ash‑proof, shock‑absorbing.

Deployment Concepts

Rovers, drones, balloon sensors, wearable modules, mast antenna.

Mapping & Visualization

GPS geotagging, collaborative map, AI spread modeling, overlays.

  • Thermal camera ✦ (hidden hotspots)
  • Smoke sensor
  • Predictive AI fire spread modeling ✦
  • GPS geotagging + collaborative mapping
  • AR heads‑up display in goggles ✦
  • LoRa mesh (no Wi‑Fi/cell required)
  • Satellite uplink fallback
  • Emergency siren + vibration wristband
  • Rugged casing (fire/water/shock)
  • Solar backpack power
  • Swappable batteries
  • Helmet‑integrated thermal display ✦
  • Remote‑controlled rover
  • Hybrid firefighting drone
  • Cloud hotspot archive + real‑time dashboard
Cues

Visual (LED, overlays), auditory (siren/voice), tactile (haptics) for redundancy under stress.

Controls

Large glove‑friendly buttons, one‑button SOS, icon‑first screens, modular clip‑ons.

Durability & Safety

Fire‑retardant, waterproof, dust/ash‑proof, shock‑resistant; comfort via balanced wearables.

Instruction

Quick‑start icons, intuitive color/sound codes, AR guidance, app simulator.

Concept Sketch

Concept sketch with subsystems
A. Sensor Mast (linear actuator)
B. Battery Bay
C. ESP‑Mesh/LoRa Radio
D. Rugged Body
E. Thermal/Smoke/CO Sensors

Product Description

Mobile sensor units with GPS and a raiseable sensor mast form a distributed detection fabric. An ESP‑Mesh backbone relays readings to a rugged base module with multi‑modal alerts and glove‑friendly controls. Roles align to the course structure: networking, HMI, sensing/actuation, and systems integration (power, runtime, terrain navigation).

Appendix

Name Role Primary Deliverables
Vinny Project Manager / Team Lead Project timeline & coordination; task assignments & follow-ups; meeting agendas/notes; risk & scope management; instructor/stakeholder communication.
Emonie Documentation Lead Report drafting & editing; citation management; submission packaging; Google Drive organization & version control; compliance with course formatting.
Amanda Design & Branding Lead Slide templates and graphics; diagrams/figures; logo and visual assets; UI mockups as needed; visual consistency across deliverables.
Danitza Research Lead Literature & standards review; sensor/comms trade studies; evidence-backed recommendations; source summaries; data collection planning.
Erjan Electronics Lead Circuit design & prototyping; PCB layout and BOM; component selection; firmware integration support; bench bring-up and debugging.
James Test & Validation Lead Test plans & procedures; unit/system testing; data logging & analysis; acceptance criteria; demo readiness checks and issue tracking.
Communication Procedures (Summary)
  • Async default: group text (≤24h response; reactions OK for acks)
  • Sync for blockers: quick call (15–30m) + recap in chat
  • Formal trail: email/Canvas; Vinny as primary point of contact (cc all)
Definition of Done (excerpt)
  • Builds from clean clone; README updated
  • Test(s) executed with logs/clip
  • Wiring/schematic & enclosure notes updated
  • Metrics recorded: latency, delivery, accuracy

Decision Log (Template)

Date:
Topic:
Options Considered:
Criteria & Tradeoffs:
Decision:
Owner:
Revisit If:
        

Communication Channels

Preferred modes for each team member.

Name First Choice Communication Second Choice Communication Third Choice Communication
Vinny Panchal Group Text Phone Call Email / Canvas
Emonie France Group Text Phone Call Email / Canvas
Amanda Pizarro Group Text Phone Call Email / Canvas
Danitza Jimenez Group Text Phone Call Email / Canvas
James Austin Group Text Phone Call Email / Canvas
Erjan Baigenzhin Group Text Phone Call Email / Canvas

Notes: “Group Text” refers to the team chat chosen by the group (iMessage/Text Message/WhatsApp/Discord). Call = direct phone/audio. Email/Canvas for formal or instructor-facing items.

Communication Procedures

  • Async (default): Group text for day-to-day updates, quick questions, and coordination. Response expectation: within 24 hours; reactions are OK for simple acks.
  • Sync (when needed): Phone call for blocking issues, time-sensitive decisions, or pair-debugging. Set a 15-30 min timebox; post a short summary in the group chat afterward.
  • Formal / Records: Email (cc the team) or Canvas for deliverables, instructor questions, and decisions that need a paper trail.
  • Instructor correspondence: Primary point of contact: Vinny (sends/receives), with all members cc’d. Vinny posts a 2–3 line recap + links in the group chat within 12 hours of any instructor reply.
  • Shared files: Google Drive is the source of truth for docs and assets: Team Drive Folder. Naming: EGR314 - Deliverable - vYYMMDD - Owner (e.g., EGR314 - P1 Slides - v250915 - Vinny).
  • Escalation path: 1) ping in group chat → 2) quick call within 24h → 3) escalate to instructor if blocked & deadline risk.

Availability Matrix

Summary of the team’s overall availability based on the survey form.

Member Sun Mon Tue Wed Thu Fri Sat
Vinny x x x x
Emonie x x x x
Amanda x x x x
Danitza x x x x
Erjan x x x x
James x x x x x

Meeting Template

Agenda:
1) Check-in & blockers (5m)
2) Progress since last review (10m)
3) Decisions needed (10m)
4) Next steps & owners (5m)

Notes:
- …
        

Notes & Brainstorms

  • Assumptions: rugged embedded device for wildfire response; glove-friendly screen+buttons; internet-optional comms (ESP-NOW/LoRa); outdoor sun/dust.
  • Key metrics: ≤1 s alert latency; 99% message delivery (n≥100 in lab); >95% detection accuracy for chosen condition; ≤3 actions for core task.
  • Constraints: course timeline, limited budget, safe lab surrogates (no open flame), simple enclosure & power budget.
  • Why this scope: maximizes embedded-systems learning while remaining demo-feasible; clear pass/fail tests.

Team Organization Steps

  • Expectations Charter: response time ≤24h on chat; meetings start on time; escalate blockers after 2 days.
  • Conflict Path: 1:1 → team discussion (15 min timebox) → instructor input if unresolved.
  • Peer Reviews: every PR needs one review; use a 3-item checklist (builds clean, tests noted, docs touched).

Resources

Report PDF

Open or download the submitted PDF.

Presentation Video

Watch on YouTube if the embed is blocked.

AI Image Citation

Any image marked with ✦ used AI in its generation. Websites used: ChatGPT