Introduction

Higher mathematics often sounds remote, but its ideas become powerful tools when used to model real systems around us — from traffic near Bryansk’s railway hub to the forests that edge the Desna. This article uses clear language, simple demonstrations you can do with a spreadsheet or free software, and memorable analogies to make system modeling both useful and fun for people in Bryansk.

What is system modeling? A short, friendly definition

A model is a simplified, mathematical picture of a real system. It captures the most important features so we can ask “what if?” and test scenarios without experimenting on the real world. Think of a model as a map: not the territory, but a tool that helps you navigate.

Core mathematical ideas (in plain language)

— Linear algebra: arrays of numbers (matrices) that summarize many relationships at once — like a table of train arrivals and platform occupancies.
— Differential/difference equations: rules for how things change over time — temperature cooling, infections spreading.
— Probability and statistics: tools to handle uncertainty and learn parameters from noisy measurements.
— Dynamical systems and chaos: how simple rules can lead to steady patterns or wild, unpredictable behavior.
— Optimization and control: choosing the best actions under constraints — e.g., timing traffic lights.

Five practical demonstrations (doable with Excel, LibreOffice Calc, or simple Python)

Each demonstration is described with: aim → tool → steps → what you’ll learn.

1) Traffic queue at a Bryansk grade crossing (simple queueing model)
— Aim: Estimate average wait time for cars at a busy crossing near the railway station.
— Tool: Spreadsheet (or Python).
— Steps:
1. Count arrivals per minute during peak hour (or use a rough estimate, e.g., 20 cars/min).
2. Measure service rate: how many cars clear during a green phase (e.g., 30 cars in 60 s).
3. Use a simple queueing formula (M/M/1 as a start): average queue length ≈ ρ / (1 − ρ), where ρ = arrival_rate / service_rate.
4. Simulate in a spreadsheet by recording arrivals each minute and allowing service up to capacity.
— What you’ll learn: How small changes in service (longer green phase) or arrival rate (a diverted bus) affect delays.

2) SIR epidemic model for a small school (discrete-time, spreadsheet)
— Aim: See how an infection might spread in a classroom and how vaccination or isolation changes the outcome.
— Tool: Spreadsheet.
— Model (discrete steps, daily):
— S_{t+1} = S_t − beta * S_t * I_t / N
— I_{t+1} = I_t + beta * S_t * I_t / N − gamma * I_t
— R_{t+1} = R_t + gamma * I_t
— Steps:
1. Set N = class size (e.g., 25). Set initial I_0 = 1, S_0 = 24, R_0 = 0.
2. Choose beta (infection rate) and gamma (recovery rate). Example: beta = 0.6, gamma = 0.2.
3. Iterate day by day in the spreadsheet for 30 days and plot I_t.
4. Try reducing beta (better masks/distancing) or moving some S to R (vaccination) and compare peak infections.
— What you’ll learn: Nonlinear growth, peak load timing, and the power of small interventions.

3) Cellular automaton for a simple forest-fire model (applies to Bryansk’s woods)
— Aim: Explore how fires spread through a patch of forest and how firebreaks help.
— Tool: Spreadsheet with grid cells or a simple Python script.
— Rules (probabilistic):
— Each cell: empty, tree, or burning.
— A burning tree becomes empty next step.
— A tree catches fire if a neighbor is burning, with probability p (wind, dryness).
— New lightning ignitions occur with small probability f.
— Steps:
1. Build a 30×30 grid in the spreadsheet, fill with “tree” or “empty.”
2. Add one burning cell to start.
3. For each step, compute next state using neighbor checks and random numbers (spread probability p ~ 0.3 for dry