18. Match the Vehicle
Parking · Intelligence Studio
Route electric cars to charging bays and large vehicles to large bays.
Scenario
The lot has standard spaces, charging bays for electric cars, and wide bays for large vehicles.
Problem statement
Vehicles with specific requirements are entering your lot.
Electric vehicles need charging bays, while large trucks need wide spaces. Assigning an electric car to a standard space or a large truck to a small spot causes a category violation!
Order your rules from specific vehicle requirements (carElectric, carLarge) down to the general standard vehicle fallback.
The starter controller routes everything to standard parking. Place specific rules above that fallback: 1. WHEN hasExitRequest -> DO release-vehicle 2. WHEN carElectric -> DO park-charging 3. WHEN carLarge -> DO park-large 4. WHEN hasWaitingVehicle -> DO park-standard
What this teaches
Match specific resource requirements before applying general fallbacks.
Active controller
Apply & Run executes only the selected controller.
How a rule works
A rule has two parts:
WHEN <something is true> → DO <this action>
- WHEN is a question about what is happening right now. For example: "Is it raining?" or "Is there a wall ahead?"
- DO is what happens when the answer is yes.
- The simulation runs one step at a time.
- On each step, the rules are checked from top to bottom.
- The first rule that is true wins. The rules below it are skipped for that step.
- To change which rule wins, move it up or down the list.
- If no rule is true, nothing happens on that step.
- Some actions have more than one step, like "turn right, then move". You build these in the Functions tab.
- Once a multi-step action starts, it finishes all its steps before the rules are checked again. It only stops early if the next step is not safe.
See an example
Two rules for deciding about an umbrella:
1 WHEN isRaining → take an umbrella 2 WHEN always → leave the umbrella at home
- It is raining. Rule 1 is true, so you take an umbrella. Rule 2 is skipped.
- It is sunny. Rule 1 is false, so rule 2 is checked next. Rule 2 is always true, so you leave the umbrella at home.
- Order matters. If rule 2 were on top, it would be true every day, and you would never take an umbrella.
Rule folders
Categorise cards without changing their global execution order.
ParkFlow operations
Entrance → allocation controller → parking → authorized exit
Entrance queue
Allocation controller
Classifying car-01
Standard compact vehicle
Exit checkpoint · 0
No exit request
Checkpoint monitoring parked cars
Task progress & pass contractThe exact requirements used to judge this visible run⌄
- Serve every vehiclenot run
reached && allVehiclesServed - No category violationsnot run
allVehiclesServed && violations == 0 - Average entry and exit wait no more than two ticksbonusnot run
allVehiclesServed && averageWait <= 2 && averageExitWait <= 2
Parking penalty audit
Entrance wait
0.00
Exit wait
0.00
Hard violations
0.00
Preferences
0.00
Abandonment
0.00
Rerouting
0.00
Congestion
0.00
Active queues
1.00
No parking allocation violation has been recorded.
Press Apply & Run to load your brain and start the simulation.