Public Demo
You are welcome to explore this solution. Prior to official go-live, you may use it freely — however, your data may be lost in future updates. No guarantees or liability are given. Use at your own discretion.
Intermediate

Match requests to the right resources

Build a working criteria set — including an enum and a numeric threshold — apply it as capabilities, and verify the match.

Published

Outcome

A small, realistic criteria set — one Boolean, one Number with a unit, one Enum — applied as capabilities on spaces and used as requirements on a request, with the match verified both positively (it schedules) and negatively (a wrong resource is rejected).

Before you begin

Step 1 — Define three criteria

Open Settings → Criteria (“Define reusable criteria that can be used as space capabilities or utilization requirements.”). Create, via Add Criterion:

  1. Crane — Data Type: Boolean (true/false). A hall has one or it doesn’t.
  2. Max Load — Data Type: Number (numeric value), Unit kg. A magnitude to compare against.
  3. Power Supply — Data Type: Enum (predefined options) with options 230V and 400V. One of a fixed list.

For each, check Applies to includes spaces, then Create.

Step 2 — Describe your spaces truthfully

For each space (Spaces → Spaces tab → open → Capabilities):

  • Heavy-assembly hall: Crane = true, Max Load = 5000, Power Supply = 400V.
  • Light workshop: Crane = false, Max Load = 500, Power Supply = 230V.

The point of this guide is the difference between the two — matching only matters when resources genuinely differ.

Step 3 — Create a demanding request

Under Requests → New Request:

  • Name: Press installation.
  • Requirements: Crane = true, Max Load ≥ 2000, Power Supply = 400V.
  • Leave the schedule empty; Create Request.

Step 4 — Verify the match, both ways

  1. On Utilization → Spaces, drag Press installation onto the light workshop row. Validation rejects it with named issues — Required capability missing — because the workshop fails all three requirements.
  2. Now drop it on the heavy-assembly hall: it places cleanly and shows Scheduled.
  3. For the automated version: unschedule it, press Auto-schedule unscheduled requests, and confirm the preview proposes only the hall. A model where no space qualifies would come back as No compatible space.

Step 5 — Scale the vocabulary deliberately

What made this work is worth keeping as policy:

  • Add a criterion only when it gates real placements — decoration criteria rot.
  • Boolean and Enum for qualities, Number + Unit for thresholds.
  • Name for the shop floor: conflict messages will quote these names back at planners.
  • Put shared capabilities on groups (all Cleanrooms certified at once) rather than on each member.

Next steps