Skip to content
SmartFACT HelpHandbooksWatch and practise
Handbooks: FactorySpec

How to include a component above a length

Use a starter rule to add a component line that is included only when a length is over a limit.

Review edition · 16 November 2026 · For Author, Reviewer

On this page

Some components are needed only on larger units: a centre support above a width, extra clips on a tall frame. The starter rule Include a component above a length adds a component line that is included only when a length is over your limit.

Use the starter rule

You need the Author role, and the family needs a saved draft that the evaluator accepts, with at least one length input and one component whose Dimension profile is a count only. The rule goes into the draft's next revision. No evaluation uses it until a separate Reviewer approves a release that contains it and activates it, and every result stays an evaluation result.

  1. Open Product families and choose the family in Open a family.
  2. Under Starter rules, find Include a component above a length. It is in Component list. You can also type a word from its title in the search box above the cards.
  3. Fill in the blanks in the card's sentence, "Include … … when … is greater than … mm.":
    • Count: how many each unit over the limit takes, from 1 to 9,999.
    • Component: one of the family's components counted without dimensions, shown by its description and code.
    • Length: one of the family's length inputs.
    • Limit: the length in millimetres, as your product expert gives it. A unit exactly at the limit does not list the component.
  4. Choose Use this rule. The button waits until every blank has a value.

FactorySpec saves the draft's next revision with one new line at the end of Component list, whose Include when compares the length with the limit. It is the same line you would get by choosing Add component line in the engineering model and choosing Save draft. No AI is asked. Above the cards, the page says which starter rule the revision began from.

Save or discard any unsaved change in the engineering model first: the cards wait while the editor has one. If someone saved a newer revision of the draft after you opened the page, the card is refused: reload the page, check what changed, then use the card again.

Where SmartFACT Automation is connected to FactorySpec, you can also arrive here from New requirement there, which offers the cards of the family whose draft changed most recently. Its Use this rule makes nothing: it opens Product families on that family with this card alone and its blanks filled in. Check the blanks, then choose Use this rule on the page. See every starter rule shows all the cards.

Where plain English for conditions is switched on for your site, the card also offers Reword with AI. It adds the same line, then opens Describe a condition in plain English on it, with the card's sentence in Describe when this action should apply. It sends nothing: you change the sentence and choose Draft a condition proposal yourself. Where plain English is not available, the card offers Use this rule alone.

What the rule does

A unit whose length is over the limit lists the component with your count. A unit at or below the limit does not list it, and neither does a unit without that length, where the length is optional. The family's other lines are unchanged.

For Frame assembly FA-300 at Brighouse works, "Include 2 Support clip (CLIP) when Finished external height is greater than 2000 mm" adds two support clips to a frame 2,000.1 mm high and none to a frame exactly 2,000 mm high.

Correct the independent cases

A starter rule saves no case and changes none, because an expected component list is your product expert's to state from the engineering source: FactorySpec never works it out for you. The cases over the limit now expect a component list without the new line, so they no longer pass, and the page says the draft is not ready for independent review. Under Independent cases in the engineering model:

  • add the new line to the expected component list of every valid case over the limit;
  • include one case just over the limit and one exactly at it, so the boundary is checked;
  • give each change an engineering basis that names the source.

Save the draft and read the proof. Where actual and expected differ, settle it from the source, not by copying what the evaluator returns.

Review and activate it

Choose Run cases and request review. The candidate freezes the model, the cases and a bounded comparison with the active release. A Reviewer who did not contribute to the model or its cases checks it and chooses Approve this candidate, then activates the release with a recent second factor. Review a candidate describes the review. A rule from a starter rule is reviewed like any other, and an accepted result remains an evaluation result, not a manufacturing approval.

Change it later

Nothing about a starter rule makes its rule permanent. Change the line's count or limit, or remove the line, and save the change as a new revision. Correct the cases, request review and activate the new release in the same way. Results already accepted keep the release and inputs they were accepted with.

If the card is refused

A refused card saves nothing, and the message says why:

  • "Not done: reload the current draft before making this change." Another author saved the draft after you opened the page.
  • "Not done: this card has changed since the page was read." The draft's inputs or components, or FactorySpec's starter rule, changed. Reload the page and fill the card in again.
  • "Not done: the engineering model already has this rule." A line already includes the same component, in the same count, over the same limit.
  • "Not done: plain English is not available here." You chose Reword with AI after plain English was switched off. Choose Use this rule instead.