Some options cannot be combined: a black frame with a clear panel, a slim profile with a heavy glazing option. The starter rule Block two options together adds a blocking condition that stops a unit with both options, and shows your reason.
Use the starter rule
You need the Author role, and the family needs a saved draft that the evaluator accepts, with at least two inputs that have options or a yes-or-no answer. 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.
- Open Product families and choose the family in Open a family.
- Under Starter rules, find Block two options together. It is in Blocking conditions. You can also type a word from its title in the search box above the cards.
- Fill in the blanks in the card's sentence, "Block a unit when … and …, and give the reason: …":
- First option: one option of one of the family's inputs, such as "Frame finish is black", or a yes-or-no answer, such as "Include a panel is yes".
- Second option: one option of a different input. A unit has one value for each input, so two options of the same input are refused.
- Reason: what the supervisor reads when the unit is blocked, up to 300 characters. Say which combination is not made and what to change.
- Choose Use this rule. The button waits until every blank has a value.
FactorySpec saves the draft's next revision with one new row at the end of Blocking conditions. It is the same condition you would get by adding it yourself 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 condition, 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 with both options is blocked before any component list is produced, and shows your reason. FactorySpec never swaps an option to make it fit: someone changes one of them and evaluates the unit again. A unit with only one of the options is not blocked by this condition. Where an option's input applies only to some units, such as a panel type that applies only with a panel, a unit without that input is not blocked either.
For Frame assembly FA-300 at Brighouse works, "Block a unit when Frame finish is black and Panel type is opaque, and give the reason: The black frame takes no opaque panel. Choose clear or remove the panel." blocks a black frame with an opaque panel, and lets through a natural frame with an opaque panel and a black frame without a panel.
Correct the independent cases
A starter rule saves no case and changes none, because an expected result is your product expert's to state from the engineering source: FactorySpec never works it out for you. Under Independent cases in the engineering model:
- add one case with both options, expected to be blocked with this condition's key as its reason;
- add one case with each option alone, expected to be valid with its complete component list;
- correct any existing case that the condition now blocks;
- 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 reason or an option, or remove the condition in Blocking conditions, 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 FactorySpec's starter rule, changed. Reload the page and fill the card in again.
- "Not done: choose options of two different inputs." Both options belong to the same input, so no unit could have both.
- "Not done: the engineering model already has this rule." A blocking condition already blocks the same two options.
- "Not done: plain English is not available here." You chose Reword with AI after plain English was switched off. Choose Use this rule instead.