Skip to content

Guides

Specification requirement → finding a suitable good (spec matching)

Describe a component requirement with technical limit values, have variants from the material catalog rated and adopt the best one as a component.

A technical demand becomes a concrete good whose specifications demonstrably match the requirements.

  1. Create the requirement. In the „Engineering“ tab you create a component requirement. You select a material type. Without a material type, neither specifications nor matching are possible.
  2. Define limit values. Under „Technische Anforderungen“ (Technical requirements) you add a target per specification. Available are the specifications of the material type and its parent types. For numbers there are „=“, „≥“, „≤“ and „zwischen“ (between), for selection lists „=“ and „einer von“ (one of). For text and yes/no there is „=“.
  3. Rate candidates. „Spec-Matching“ lists all variants of the material type and its subtypes. Inactive variants cannot be selected. Each shows how many targets it fulfils, for example „3/4 erfüllt · 1 unbekannt“ (3/4 fulfilled · 1 unknown), and a rate in percent.
  4. Read the matches. At the top are variants that fulfil everything. Then follow variants without a violation but with missing values, then those with violations. The color is green for a full match, red for a violation, otherwise yellow.
  5. Select. For the selected variant, the dialog shows the value and a sign per target: fulfilled, violated or „?“ („kein Wert hinterlegt“, no value recorded). You also enter the „Benötigte Menge“ (Required quantity).
  6. Adopt. After a warning, a technical component replaces the requirement in the same structure folder. It takes over name and description. The requirement is deleted; this is not reversible.
  7. Continue to procurement. On the component, allocation and procurement request follow (see From engineering to order).
Rule Meaning
Unit Comes from the specification of the material type. Both sides use the same one, Aligia does not convert anything.
Limits Limit values are inclusive. A value range must lie entirely within the limits.
Text Must be exactly equal. Text is never converted into a number.
Missing value Counts as „unbekannt“ (unknown), not as a violation. The rate only counts known values.

A technical component with a verified good and quantity, ready for allocation and procurement.

Technical structure · Materials · Procurement