Your data. Your rules. Every recommendation cites both.
Like most analytics platforms now, Stratum describes what happened, forecasts what’s coming, and recommends what to do. What sets it apart is the last step: every move is weighed against the leases, covenants, and policies you operate under, and cites the clause it stays within. Here’s how it works, end to end.
Descriptive · Predictive · Prescriptive · Grounded in what binds you
The analytics lifecycle you know, built to end in the move.
Every analytics platform walks the same path: pull the data in, describe what happened, predict what’s coming, and increasingly, suggest what to do. Stratum covers all of it, as a layer on the systems you already run. The difference is what the suggestion is checked against: the permits, leases, and covenants you’re accountable for, read from the documents themselves and cited in every recommendation.
It starts with the data you already collect.
Most of your parking data already exists; it’s just scattered across PARCS, permit systems, LPR and occupancy sensors, finance, and event and academic calendars. Stratum connects to the systems you already run and resolves those feeds into one continuous picture, normalized to the same lots, hours, and rate classes. No rip-and-replace, no new hardware.
Alongside the feeds, Stratum takes in the documents that govern them: leases, bond resolutions, permit policies, union agreements, committee charters. Those are what every recommendation is checked against later. No special formatting needed: a designed master plan PDF, a plain Word file, a spreadsheet export, or a report full of charts all work.
What happened, without the manual assembly.
From those feeds Stratum builds the descriptive layer: occupancy by lot and by hour, dwell and turnover, utilization against what was actually sold, revenue by product and segment. It’s the reporting most teams still rebuild by hand every cycle; here it’s standing, current, and consistent. Table stakes, and the base everything above it stands on.
What’s coming, grounded in your calendar.
The predictive layer projects demand and overflow forward, by lot and by time-of-day. It doesn’t forecast on history alone: it reads what actually moves your demand: an event on the calendar, a shift change, a flight bank, a seasonal swing, a construction closure. A forecast that sees a sold-out event or a Monday-morning peak coming beats one that only knows last month’s counts. Still table stakes, but grounded ones.
This is where Stratum is different.
Reads and forecasts are table stakes now. Here Stratum weighs each move against the documents that bind you and shows the clause it stays within: the reason the platform exists.
A recommendation is a case, not a guess.
Every recommendation starts from one question: what changes, and what does it touch? Stratum weighs the candidate moves against the constraints you actually operate under: a bond covenant, a lease guarantee, a permit policy, a union agreement, a service level you’ve committed to. Each option comes back scored on projected impact and effort, carrying the numbers, the reasoning, and the source: the document and section it stays within. So the one you choose holds up, whether that’s a budget meeting, a board review, or a public hearing. It surfaces moves your team hadn’t lined up, and it never takes the decision: it makes the case, you make the call.
Opening 420 Level 5 spaces at the Economy rate absorbs the overflow without a rate change and keeps shuttle headways at the 10-minute standard in the Ground Transportation Plan. Garage revenue lost on Level 5 is offset by recaptured Economy turn-aways.
Estimated +$611,000/yr in recaptured parking revenue; debt service coverage stays at 1.42x against the 1.25x covenant.
| Scenario | Garage A Peak | Garage B Peak | Rerouted | Lease Reserve |
|---|---|---|---|---|
| No closure (observed) | 91% | 74% | – | Held |
| Close now, no rerouting | 97% | 96% | 0 | At risk |
| Close now, retail to Lot C | 93% | 88% | 1,140/wk | Held |
| Close Jan 6, after holidays | 89% | 84% | 610/wk | Held |
See the move play out before it’s real.
Before you commit, run the move as a scenario. Stratum projects the effect across the things that interact (occupancy, overflow, service levels, and the revenue line) so you see the second- and third-order consequences, not just the first. Close a deck and watch where the overflow lands; move a rate and see the revenue and the access tradeoff together; shift capacity for a peak event and see which lots feel it downstream. Compare two or three approaches side by side, and walk into the decision with the tradeoffs already mapped instead of argued.
Product questions
Dashboards and reports tell you what happened, and Stratum does that too, as its descriptive layer. But it doesn’t stop there: it forecasts what’s coming and, above all, recommends what to do about it, weighed against your real constraints. The dashboard is the floor; the recommendation is the point.
Your account can be live the same day. Upload your governing documents and recent data reports at setup and Stratum processes them automatically, typically within a few days and often sooner, so first recommendations come from what you already have. Live API connections follow, and they’re quicker for vendors Stratum already integrates with. Most teams don’t need IT involved, and there’s no new hardware.
No. Stratum is the advisor, not the actor: it does the analysis, brings back the moves worth making, and shows the reasoning behind each. The decision, and the authority for it, stays with your team. It makes the case; you make the call.
Everyday operational calls and higher-stakes ones: permit allocation against the schedule, rate changes, lot closures and construction phasing, event and move-in plans, enforcement posture, mode-shift tradeoffs: anything where the move touches occupancy, revenue, access, and the obligations you’re accountable for.
No. Stratum is a layer on top of what you already run (PARCS, permits, LPR, financials, calendars), not a replacement. It’s vendor-neutral and works alongside the tools you already trust.
See it run on a decision like yours.
Bring one real decision you’re facing (a rate change, a lot closure, an event plan). We’ll run a representative version through the lifecycle using sample data and show you the move, with the clauses it stays within. No data or system connection needed.