MARCH 2026 · ANONYMISED OPERATIONAL DATA
Excellerate Services SmartPark
Mobility, Behaviour & Revenue Analytics
THEME
Comfort uses warm charcoal and roomier text for long reading.
LAYOUT PREVIEW
PLAYBACK SPEED
Showing — · — (— days)
Analyst view. Every page now adds its detail tables (daily, hourly, lane-level and exclusions). Switch back to Executive for the summary.
Part of March is selected. Totals, averages and charts follow your dates; the median stay, unique plates, repeat share, stay mix and payment-type split are full-month figures and say so where shown.
MODULE 00 · READER’S GUIDE
Every page moves from what happened, to the pattern behind it, to the record you can quote. This guide shows how to read each part, what the colours and marks mean, and where the figures come from.
The Overview tiles are built the same way. Read the label first, then the number, then the line under it.
Entry events 1
—2
— a day on average 3
4Net parking revenue
R—5
After R — validations 6
What is counted. “Events” are barrier transactions; “journeys” are matched entry–exit plate reads.
The total for your site and date selection. It counts up when filters change, then settles on the exact value.
The figure that makes the headline meaningful: an average, a rate or the cohort it was calculated from.
The shape across the selected period, following Group by. The dot marks the highest point.
Money. Orange always marks the number to read first.
Validations are shown beside net revenue so the two are never confused.
Use the View switch at the start of the filter bar; it stays pinned to the top as you scroll. Stop at the level your decision needs.
EXECUTIVE · SUMMARY
What happened, and what needs attention?
You will see
The month in one line, ten KPI tiles, the Replay March player, charts and management insights.
Go here when
You need the position in two minutes.
ANALYST · RECORD
What exactly is behind each figure?
You will see
Everything above plus daily, hourly, revenue, lane and exclusion tables on every page.
Go here when
You are about to quote a number, compare lanes or check a reconciliation.
One question per page. Select a card to open it.
Colours and marks used on every page, all drawn from the Excellerate palette.
Colours
Marks & symbols
Labels that change
Eleven things on the page and how to interpret them. The third column is the common misreading.
| You see | It means | It does not mean |
|---|---|---|
| Entry events | Successful barrier entries recorded | The number of different vehicles or visits |
| Fewer exits than entries | Fewer successful exit transactions were logged | Vehicles still parked, or occupancy |
| Average stay | Mean of plate-matched journeys of 0–24 h | Every visit — unmatched reads are excluded |
| Median “30–60 min” | The band holding the middle journey across both sites | An exact minute value |
| Net revenue | Money collected, per device financial reports | Gross value, or a bank-settled amount |
| Validations | Parking value waived through validation | Revenue received |
| Repeat plates | Plates seen on two or more March days | Verified individuals or loyalty members |
| Net per paid transaction | Net revenue ÷ paid transactions reported by devices | Average spend per vehicle |
| Correlation 0.96 | Daily revenue and entries rise and fall together | That traffic causes revenue |
| Unusual day +18% | 15%+ away from the same weekday’s median in range | An incident or a data error by itself |
| “Valid” as a failure reason | The system’s own reason code for that unsuccessful event | That nothing went wrong |
One anonymised extract drives every figure. Open Sources (top of the dashboard) to see each calculation and download its rows.
What is in the data
Not available, so not shown
THE MONTH IN ONE LINE
Events are barrier transactions, not verified vehicles. Duration uses only matched entry–exit journeys.
Entry events
—
— a day on average
Exit events
—
— per 100 entries
Net parking revenue
R—
After R — validations
Average stay
—min
— matched journeys
Median stay
—
—
Unique plates observedDistinct plates a day
—
Plates with a valid read, MarchDaily average in range; monthly unique needs the full month
Repeat platesReturning share of daily plates
—%
Seen on 2 or more March daysSeen on an earlier March day
Average daily activityAverage weekly activityMonthly activity
—
Entry events a dayEntry events per 7 daysEntry events in March (one month of data)
Average daily revenueAverage weekly revenueMonthly revenue
R—
Net, per calendar dayNet, per 7 daysNet, March total (one month of data)
Peak activity period
—
About — entries in that hour a day
Press play to watch demand and revenue build through the month. Pause or drag along the track to stop on any day. Speed is under Display.
Daily totals.Weekly totals (Monday start); faded bars are part-weeks.One bar for March: the file holds a single month. Entry and exit events (top) and net revenue (bottom) share one timeline. Hover for exact values.
NET REVENUE (R)
Observed findings from this data. Possible explanations are marked as such.
Every day in the selected range, for the selected sites. Mean stay is weighted by matched journeys.
| Day | Entries | Exits | Net (R) | Validations (R) | Matched journeys | Mean stay (min) |
|---|
02 · DEMAND & TRAFFIC INTELLIGENCE
Busiest hour —. Weekend days average — entries against — on weekdays.
Follows Group by. Faded bars are part-weeks cut by the month or your dates. Click a legend item to hide it.
Average events in each hour of a day, for the selected dates.
Average events per day for each weekday.
Darker cells are busier hours. The outlined cell is the peak. Follows Show.
Entry events per day, all selected sites together.
| Day | Rank | Entries | Exits | Net (R) |
|---|
Successful entry, exit and passage events per anonymised lane.
Totals and per-day averages for each hour, selected sites and dates.
| Hour | Entries | Exits | Entries / day | Exits / day |
|---|
03 · VISITOR BEHAVIOUR & PARKING DURATION
—
Average stay
—min
Weighted by matched journeys in range
Median stay
—
—
Matched journeys
—
Entry and exit both read, 0–24 h
Entry events per matched journey
—
Why events ≠ visits
Short under 30 min · Medium 30 min–2 h · Long 2 h+. Full month.
Matched journeys by pass type. Full month.
| Site | Pass type | Journeys | Mean (min) | Median (min) |
|---|
Share of each site's matched journeys per band. Full month.
Observed plates by number of distinct March days seen. Aggregated counts only. Full month.
Share of each period's plates seen on an earlier March day. It starts at zero on 1 March because there is no earlier history.
Plate reads that could not form a valid March journey.
| Site | Plate-read rows | Matched | Missing entry or exit | Outside March | Negative or over 24 h |
|---|
04 · REVENUE & COMMERCIAL INTELLIGENCE
Gross reported value of R — less R — validations leaves R — net revenue.
Net revenue
R—
Collected, per device reports
Validations
R—
— validations · not collected revenue
Average daily net revenue
R—
Per calendar day in range
Net per paid transaction
R—
— paid transactions reported
Cash and card make up net revenue. Follows Group by.
Gross value − validations = net revenue. The check line shows any difference.
Unreconciled difference: R —
Net revenue by channel as reported. Full month.
"Other credit card type" is how the payment devices label most card payments; it is kept as reported.
Each dot is one site-day: entry events (across) against net revenue (up).
—
Selected dates. Ratios are context, not transaction values.
| Site | Net (R) | Gross (R) | Validated % | Net / day (R) | Cash % |
|---|
Revenue by lane or pay station is not available: the financial reports are not linked to lanes.
Follows Group by. Gross − validations = net; cash + card = net.
| Period | Gross (R) | Validations (R) | Net (R) | Cash (R) | Card (R) | Paid transactions |
|---|
05 · OPERATIONAL PERFORMANCE
For every 100 entry events, — exit events were recorded. Unsuccessful attempts: — per 100 entries and — per 100 exits.
Follows Group by. Click a legend item to hide it.
Unsuccessful events by recorded reason. Full month. "Valid" is the system's own reason code.
Unsuccessful per 100 successful events; lanes with 1,000+ successful events.
Days at least 15% above or below the median of the same weekday in the range.
| Date | Site | Measure | Value | Weekday median | Difference |
|---|
—
Selected dates. Median, unique plates and repeat share are full-month figures.
| Site | Entries | Exits | Exits / 100 entries | Failed exits / 100 | Mean stay | Median stay | Repeat plates % |
|---|
Selected sites and dates.
| Lane | Role | Entries | Exits | Passages | Failed entries | Failed exits | Barrier ops | Failed / 100 |
|---|
Full month, from the event log.
| Site | Manual barrier ops | Void entries | Violations | Plate corrections | Lost tickets |
|---|
06 · MANAGEMENT INSIGHTS
Each card pairs an observed finding with a possible explanation, a recommended action and the measure that would show it worked. Findings update with your filters.
Issue → action → result. Everyone who can open this dashboard sees the log; editors add entries.
| Issue | Action | Owner | Status | Result |
|---|
—
This is an offline copy. The live dashboard keeps the shared action log; record actions there.
That wasn't saved. Only editors of this dashboard can add to the log.