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.
Outcome
You build a small, realistic criteria set: one Boolean, one Number with a unit, and one Enum. You apply it as capabilities on stations, and you use it as requirements on a request.
You then check the match in both directions. A correct resource schedules, and a wrong resource is rejected.
Before you begin
- A workspace with a site and at least two spaces. Model your facility sets this up.
- The Editor or Admin role.
- Read How capability matching works. This guide is the practice half of it.
Step 1 — Define three criteria
Open Settings → Criteria: “Define reusable criteria that can be used as space capabilities or utilization requirements.” Select Add Criterion and create these three:
Crane— Data Type: Boolean (true/false). A hall has one, or it does not.Max Load— Data Type: Number (numeric value), with Unitkg. This is a magnitude to compare against.Power Supply— Data Type: Enum (predefined options), with the options230Vand400V. This is one value from a fixed list.
For each criterion, make sure that Applies to includes your station type. Then select Create.
Step 2 — Describe your stations truthfully
For each station, go to Stations, open the station, and open Capabilities:
- Heavy-assembly hall:
Crane= true,Max Load= 5000,Power Supply= 400V. - Light workshop:
Crane= false,Max Load= 500,Power Supply= 230V.
The difference between the two is the point of this guide. Matching only matters when the resources are genuinely different.
Step 3 — Create a demanding request
Go to Requests → New Request:
- Name:
Press installation. - Requirements:
Crane= true,Max Load≥ 2000,Power Supply= 400V. - Leave the schedule empty. Select Create Request.
Step 4 — Check the match, both ways
- On Utilization → Stations, drag
Press installationonto the light workshop row. Validation rejects it and names the issue: Required capability missing. The workshop fails all three requirements. - Now drop it on the heavy-assembly hall. It places cleanly and shows Scheduled.
- For the automated version, unschedule it. Select Auto-schedule unscheduled requests. Check that the preview proposes the hall only. If no station qualified, the preview reports No compatible resource.
Step 5 — Scale the vocabulary deliberately
Keep as policy what made this work:
- Add a criterion only when it gates a real placement. Decorative criteria rot.
- Use Boolean and Enum for qualities. Use Number with a Unit for thresholds.
- Name each criterion for the shop floor. Conflict messages quote these names back at planners.
- Put shared capabilities on groups, so that all Cleanrooms are certified at once. Do not put them on each member.
Next steps
- Templates can pre-bundle these requirements for recurring work. See Speed up intake with request templates.
- When a capability changes under a live schedule, conflicts appear. Find and resolve conflicts shows the loop.