Round 2 Presentation — AI Slide Prompt + Speaker Notes

PASTE THIS WHOLE BLOCK INTO YOUR AI SLIDE TOOL (Gamma, etc.) TO GENERATE THE ROUND 2 DECK: Create a 10-minute, 10-slide presentation titled "FluxView: Shell NET–PVAMU Data Visualization — Contribution & Requirement Analysis (Round 2)". Make this feel like a polished product pitch a well-funded startup or a company's innovation team would give investors or executives — NOT a plain academic bullet-point deck. The audience knows nothing about flux towers, agriculture, or environmental science going in. By the final slide they should feel genuinely excited about this project, not just informed that it exists. Audience: our senior design faculty coordinator (Dr. Md Hossain Shuvo) and our Shell industry sponsors (Dr. Kuloyo and Hemshikha), for a Computer Science capstone course. Tone: confident, energetic, non-expert-friendly. VISUAL AND PRODUCTION QUALITY REQUIREMENTS (critical — do not generate a plain bulleted-text deck): - Every slide needs a strong visual: a relevant photo or illustration, an icon set, a map, a diagram, or a chart. Never a slide of plain bullet text with nothing else. - Use consistent icons throughout (rain, thermometer, soil/leaf, trend-line, bell/alert, phone/mobile) instead of repeating words. - Color palette: clean, professional blue/green earth-and-data tones. - Include at least 2 illustrative example charts showing what the dashboard's real-time and historical trend views will look like once built. Label these clearly on the slide as "Illustrative concept — not real Shell data" in a visible caption, since we don't have real measurements plotted yet. Never present mockup numbers as if they are real results. - Include a simple map or diagram showing the PVAMU research farm with its flux towers feeding data into the dashboard. - On the problem slide, use a strong visual "before vs. after" or side-by-side contrast (e.g., a phone showing a normal weather app next to a "???" for farm history) so the gap is obvious at a glance, not just stated in words. - Close on a visually strong, memorable "vision" slide — not a plain "Thank You" text slide. Generate speaker notes under every slide that a nervous first-time presenter could read almost verbatim, matching the timing below, written in plain conversational English (not bullet fragments). Structure exactly as follows: SLIDE 1 — Title slide - Title: "FluxView: A Mobile-Friendly Dashboard for Real-Time and Historical Environmental Monitoring" - Subtitle: "Shell NET–PVAMU Data Visualization Team — Contribution & Requirement Analysis, Round 2" - Team: Raylen Williams (Team Lead), Rory Samuels, Alex Curtis - Course: COMP-4207 Senior Design, Prairie View A&M University - Visual: a strong hero image or illustration evoking farmland + data (e.g., a stylized farm landscape with a subtle data-overlay/grid effect) SLIDE 2 — Project Overview (this slide covers ~2 minutes of talk time) - Team name, leader, and members (restate briefly) - Project title - One-sentence problem statement for a non-expert audience: "PVAMU and Shell collect rich environmental data from 8 flux towers on the research farm — but right now, nobody outside the research team can easily see it, especially not historical trends, on a phone." - Project goal: build a mobile-friendly dashboard showing real-time and historical environmental conditions - Intended users: PVAMU researchers, students, farm staff, and the broader community - Visual: a simple map/diagram of the PVAMU research farm showing flux tower locations SLIDE 3 — The Problem, in Plain Terms - Visual metaphor, shown not just described: side-by-side contrast of "checking today's weather" (a normal, easy phone weather app screen) vs. "checking last week's soil moisture on the farm" (a big question mark / dead end) — make the gap visually obvious in one glance - 3 bullet gaps beneath it: (1) no accessible historical view, (2) flux tower / greenhouse gas data locked in research-only tools, (3) nothing mobile-first or purpose-built for this farm SLIDE 4 — Major Project Contribution (~2 minutes of talk time) - Headline: "We are not inventing new sensors or new science — we are making Shell and PVAMU's existing environmental data usable by non-experts for the first time." - 3 contribution bullets, each with its own icon: 1. Accessible historical trends (not just "today"), on mobile, for this specific farm 2. Threshold-based alerts so out-of-range conditions surface automatically instead of requiring someone to notice 3. A documented, common data API so the Predictive Analytics team (Project 3 in the Shell portfolio) can later plug in forecasts without this team's work blocking on that - Visual comparison table: "Existing tools" (consumer weather apps, FLUXNET portal, Shell's internal tools) vs. "What's missing" vs. "What we're building" — styled like a clean product-comparison table, not a plain grid SLIDE 5 — Requirement Analysis: Must-Have (~1 min of the 3-minute requirements section) - A. Must-have requirements, each with a small icon: - Ingest environmental readings via a documented API, tagged with QA/QC flags - Display current conditions on a dashboard home view - Display historical trend charts over a selectable date range - Fully mobile-responsive layout (this is the core value proposition) SLIDE 6 — Requirement Analysis: Should-Have and Future (~2 min of the 3-minute requirements section) - B. Should-have requirements: - CSV export of displayed data - Configurable alert thresholds with notifications - C. Future/scalable requirements: - Forecast/prediction overlays (integration point with Project 3) - Multi-site comparison as more towers/sensors come online - Automated anomaly detection beyond simple thresholds - Visual: a simple layered/roadmap graphic showing Must-Have -> Should-Have -> Future as building blocks SLIDE 7 — Updated Project Milestones (~1.5 minutes of talk time) - Completed: kickoff and sponsor requirements call (mid-September); existing-work review and gap analysis - Current: this requirements and system specification report + this presentation (due this week) - Remaining: wireframes and data schema design -> ingestion API + database prototype -> dashboard front-end (charts, maps) -> alerting logic + accessibility pass -> integration testing and usability review -> Semester 1 demo and progress report (target: December 2026) - Task assignment (draft — team to confirm): Raylen — architecture, ingestion API, Shell coordination; Rory — database design, data validation/QA logic; Alex — dashboard front-end and visualization - One honest note: team started roughly a week to a week and a half behind the ideal timeline while finalizing the Shell data-transfer process, which the sponsor explicitly said is a normal and acceptable delay - Visual: a horizontal timeline/roadmap graphic, not a text list SLIDE 8 — Expected Final Outcome (~1.5 minutes of talk time) - What the completed system will accomplish: any PVAMU/Shell stakeholder can open the dashboard on a phone or desktop and see current conditions plus at least 12 months of historical trend data for the research farm within seconds, with automatic alerts for threshold exceedances - How success will be demonstrated: a live or recorded demo showing real (or representative) data flowing end-to-end from ingestion into charts, meeting all must-have requirements - What counts as a successful outcome: a credible, working prototype — not production-certified software — that a non-technical user can operate without help, per the capstone program's own scope guidance - Visual: an illustrative mockup of the finished dashboard on a phone screen (current conditions + a trend chart + an alert banner), clearly captioned "Illustrative concept — not real Shell data" SLIDE 9 — References - List: PVAMU-Shell Capstone Project Description (sponsor brief); FLUXNET public data portal; NIST Cybersecurity Framework; NIST AI Risk Management Framework - Note: full citations also included in the team's written report SLIDE 10 — Vision / Thank You / Q&A - Not a plain text slide: a strong closing visual (e.g., the illustrative dashboard mockup again, or a "from data to decisions" graphic) paired with a short, energetic closing line and "Questions?" - Team contact: Raylen Williams (team lead)

• Slide 1 (Title, a few seconds): "Good [morning/afternoon]. We're the Shell NET–PVAMU Data Visualization team — I'm Raylen Williams, the team lead, and this is Rory Samuels and Alex Curtis. Today we're presenting our contribution and requirement analysis for FluxView, our environmental data dashboard project."
• Slide 2 (Project Overview, 2:00): "Here's the situation in plain terms: PVAMU and Shell have been collecting real environmental data from eight flux towers on the research farm since 2023 — things like rainfall, humidity, soil moisture, and greenhouse gas measurements. That's genuinely valuable data. But right now, almost nobody outside the research team can actually see it. Our goal is to build a mobile-friendly dashboard that lets researchers, students, farm staff, and the community check current and historical environmental conditions the same way you'd check a weather app — except this data doesn't exist anywhere else in an accessible form today."
• Slide 3 (The Problem, ~30 sec, folds into Slide 2's time): "Think about it this way: checking today's weather is trivial — any app does it. But checking what the soil moisture was on this farm last week? Right now that's basically impossible unless you contact the research team directly. That's the gap we're closing."
• Slide 4 (Major Contribution, 2:00): "We want to be upfront: we're not building new sensors or new environmental science. Shell and PVAMU already have the data and the expertise. What's missing is accessibility. So our contribution is threefold. First, we're making historical trends — not just today's snapshot — available on mobile for the first time. Second, we're adding threshold-based alerts, so if a reading goes out of range, the system surfaces that automatically instead of requiring someone to notice it buried in a chart. And third, we're building this with a documented API and common data schema from day one, specifically so the Predictive Analytics team in the Shell portfolio can plug forecasting into our dashboard later without our work being a bottleneck for them."
• Slide 5 (Must-Have Requirements, 1:00): "We prioritized our requirements into three tiers. Must-have — the things that make this project functional at all — are: ingesting readings through a documented API with quality flags attached, showing current conditions on a home view, showing historical trends over a date range the user picks, and making all of that fully usable on a phone, since mobile access is really the whole point of this project."
• Slide 6 (Should-Have and Future, 2:00): "Should-have requirements — important, but the system is still useful without them on day one — are CSV export of the data, and configurable alert thresholds with notifications. Future and scalable requirements, things we're deliberately not building yet, include forecast overlays once the Predictive Analytics team's models are ready, comparing multiple monitoring sites if more towers come online, and more sophisticated anomaly detection beyond a simple threshold check."
• Slide 7 (Updated Milestones, 1:30): "Here's where we stand. We've completed our kickoff and requirements call with our Shell sponsors, and our existing-work review and gap analysis. Right now, this week, we're finishing our requirements and system specification report and this presentation. Ahead of us: wireframes and data schema design, then a working ingestion API and database prototype, then the dashboard front end with charts and maps, then alerting logic and an accessibility pass, then integration testing, aiming for a working Semester 1 demo in December. On task assignment: I'm leading architecture and the ingestion API and coordinating with Shell, Rory is owning database design and data validation, and Alex is owning the dashboard front end. One honest note — we started a bit behind our ideal schedule while we finalized how Shell will transfer us data access, but our sponsor was clear that a week or two of delay here is completely normal and expected."
• Slide 8 (Expected Final Outcome, 1:30): "By the end of this project, anyone at PVAMU or Shell should be able to open FluxView on their phone and see current conditions plus at least a year of historical trends for the research farm, loading in a few seconds, with automatic alerts if something crosses a threshold. We'll demonstrate success with a live or recorded demo showing real data flowing from ingestion all the way into the charts a user sees. And to be clear about scope: we're aiming for a credible, working prototype that a non-technical person can use without help — not a production-certified monitoring system. That matches exactly what the capstone program asked us to build."
• Slide 9 (References, ~15 sec): "Our full references are listed here and in our written report — including the PVAMU-Shell project brief, the FLUXNET data portal, and the NIST frameworks we're using to guide our security and AI-documentation practices."
• Slide 10 (Vision / Thank You / Q&A, closing): "Picture this: any farmer, student, or researcher pulls out their phone, opens FluxView, and instantly sees exactly what's happening on this farm right now — and how it's changed over the past year — without ever having to ask us for it. That's what we're building. Thank you — we'd love to take any questions."
• Timing check: 2 + 2 + 3 + 1.5 + 1.5 = 10 minutes exactly. Slides 5-6 (the requirements section) are the part most likely to run long in rehearsal — practice those twice.
• Task split and the "week behind" line above are our best draft based on what we know as of Sept 22 — confirm with Rory and Alex before presenting them as fact.