School IT Cost Simulator

By /

School IT Cost Simulator

ISEF Category: Systems Software

Ready to Turn This Idea Into a Real Project?

This guide was put together with the help of AI research tools to give you a solid starting point. But a competitive science fair project lives in the details: refining your research question, fine-tuning your variables, analyzing your data, and presenting your findings like a seasoned scientist.

For next steps tailored to your interests, skill level, and timeline, work one-on-one with a MehtA+ mentor. Learn more about MehtA+ Science & Engineering Research Mentorship →

Subcategory: Other  ·  Difficulty: Intermediate  ·  Setup: Home Setup  ·  Time: 1 to 2 Months

The Hook

School districts spend real money on software choices that look simple on paper. One platform can seem cheap, until user counts, storage, support, and bandwidth all pile up. You can build a simulator that turns those hidden costs into per-student numbers. That gives you a real decision tool, not just a spreadsheet.

What Is It?

This project is about building a model that estimates the cost of running school software systems. Think of it like a weather forecast, but for budgets. You feed in things like enrollment, staff size, bandwidth needs, and storage use, and the model predicts cost per student for different setups.

The main comparison is self-hosted versus SaaS. Self-hosted means the district runs the system itself, often on its own server or cloud setup. SaaS means Software as a Service, where a company hosts the platform and charges a subscription. Your simulator can compare learning management systems, email, and file storage as one stack, then show how the total changes when one input changes.

A sensitivity analysis dashboard makes the project stronger. Sensitivity analysis asks, which input changes the final answer the most? That helps you find the real cost drivers, like bandwidth, admin labor, or storage growth, instead of guessing.

Why This Is a Good Topic

This is a strong science fair topic because you can test it with public pricing data, school enrollment data, and your own model design. You do not need a wet lab, but you still get real research skills, like building assumptions, comparing alternatives, and checking how sensitive your results are. The project connects to a real problem school districts face every year, and your final product can help people make budget decisions with more clarity.

Research Questions

  • How does enrollment size change the per-student cost difference between self-hosted and SaaS school software stacks?
  • What is the effect of bandwidth growth on total annual cost in a self-hosted school IT model?
  • Does adding storage demand change which option is cheaper for a district, self-hosted or SaaS?
  • To what extent does staff support time alter the break-even point between the two models?
  • Which input, enrollment, bandwidth, storage, or support, has the largest effect on cost per student?
  • How does contract length affect projected savings in a SaaS school software comparison?

Basic Materials

  • Laptop or desktop computer with internet access.
  • Spreadsheet software, such as Google Sheets or Excel.
  • Public pricing pages for LMS, email, and storage services.
  • School district enrollment data from public websites.
  • Basic calculator for checking formulas by hand.
  • Notes document for tracking assumptions and sources.
  • Browser for testing a simple dashboard or prototype.

Advanced Materials

  • Laptop or desktop computer with internet access.
  • Python installed with pandas, numpy, matplotlib, or plotly.
  • Jupyter Notebook or a similar notebook environment.
  • Public cloud pricing pages for compute, storage, and bandwidth.
  • Public school district datasets for enrollment and staffing.
  • Database or CSV files for scenario inputs.
  • Version control software, such as Git, for tracking model changes.
  • Optional web framework, such as Streamlit, for an interactive dashboard.

Software & Tools

  • Google Sheets: Lets you build the first cost model, test formulas, and compare scenarios quickly.
  • Python: Helps you automate sensitivity analysis and run many cost scenarios at once.
  • Jupyter Notebook: Keeps your calculations, graphs, and notes in one place.
  • Plotly: Makes interactive charts that show how inputs change per-student cost.
  • Streamlit: Lets you turn a notebook model into a simple public dashboard.

Experiment Steps

  1. Define the school software stack you want to compare, such as LMS, email, and storage, and decide which costs count in each model.
  2. Gather public pricing and enrollment data, then list every assumption so your model stays transparent.
  3. Build a baseline cost model that converts total annual cost into cost per student for each setup.
  4. Add sensitivity analysis so you can change one input at a time and see which variables drive the result most.
  5. Compare multiple district sizes or usage scenarios to test where the break-even point shifts.
  6. Turn the results into a dashboard or chart set that explains the tradeoffs clearly to a nontechnical reader.

Common Pitfalls

  • Mixing sticker price with real cost, which hides support, migration, and hosting expenses.
  • Comparing self-hosted and SaaS models with different assumptions, which makes the result unfair.
  • Forgetting to normalize by student count, which makes large districts look more expensive only because they are larger.
  • Using outdated pricing pages or old district data, which makes the simulator less credible.
  • Leaving out bandwidth or storage growth, which can flip the cost ranking in bigger districts.

What Makes This Competitive

A stronger version of this project goes beyond a simple spreadsheet. You can test multiple district sizes, compare several software stacks, and show which assumptions actually change the answer. A well-built sensitivity analysis makes your model more convincing because it shows uncertainty, not just one clean result. A published case study or a small validation against real district data would make the work much stronger.

Project Variations

  • Compare urban and rural districts to see how internet bandwidth changes the best software choice.
  • Model only one system, such as email or LMS, and test how costs scale with user growth.
  • Add a reliability angle by comparing cost with downtime risk, admin workload, or vendor lock-in.

Learn More

  • U.S. Department of Education, Common Core of Data: Find public school district enrollment and staffing data for model inputs.
  • NCES Edge: Explore school district profiles and compare enrollment trends by location.
  • USGS Water Science School, but for modeling practice is not relevant here; instead search NOAA or NASA for data analysis examples and dashboard ideas.
  • MIT OpenCourseWare: Search for introductory courses in systems analysis, software engineering, or modeling to study how to structure a simulation.
  • PubMed: Search for review articles on school technology adoption, digital equity, or cost analysis methods if you want background on real-world impacts.
  • INFORMS Journal on Computing: Search the journal for articles on simulation, decision support, and sensitivity analysis methods.
Shopping Cart