←
Build the decisionSaved automatically
Hard · Grade 1025. Production Parking Orchestrator

Coordinate mixed parking traffic, incident recoveries, and gate turnover across multi-zone facilities.

Scenario

The facility chooses an exact bay inside your selected category; your control system manages service order, category, waiting, and exits.

Problem statement

You are Principal Infrastructure Architect for ParkFlow!

Your system controls an enterprise multi-zone airport parking platform. Arrivals, departures, charging outages, lane congestion, gate failures, and reservation cancellations occur simultaneously across multiple zones.

Design a durable real-time orchestrator: enforce safety invariants, protect driver patience, manage back-pressure, and pass 10 adversarial test scenarios!

Structure your rules in distinct layers: 1. Hard Safety: Check category availability (`reservedAvailable`, `accessibleAvailable`, `largeAvailable`, `standardAvailable`) before allocating. 2. Service & Fairness: Authorize exit releases to recover capacity and prevent arrival queue abandonment. 3. Rerouting & Optimization: Fall back to safe alternatives when primary bays close.

What this teaches

Engineer an enterprise facility orchestrator with back-pressure handling, fairness, and incident recovery.

Evaluation contract

  • State safety and correctness: 30%
  • Completion, fairness, and customer service: 25%
  • Failure recovery and back-pressure: 25%
  • Efficiency and long-running stability: 20%
Scroll down to build and test your solution.

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.

No rules yet. Nothing will happen until you add at least one rule.