SmartFACT Automation guides and demonstrations

Learn SmartFACT Automation tasks, handle common problems and practise with checked demonstrations using sample data.

Read a guide below, or use the help page to ask a general product question. Interactive demonstrations run on desktop and laptop computers. Written instructions work on any device.

Guides and help pages

Describe a LotTrail investigation trigger in plain English

Type an investigation trigger in plain English, answer the AI's question about the missing details, inspect the complete proposed rule and save it deliberately as a draft.

Review the expected results for the rework rule

Check the expected results frozen with the rework investigation policy, including the rework case that runs the forward investigation, before approving them.

Freeze the rework policy with its agreed expected results

Check that the expected results agreed before the rule existed already expect the rework investigation, then freeze the policy so LotTrail proves every one of them.

Prove and submit the rework investigation policy

Run LotTrail's complete check of the frozen rework policy and its reviewed expected results, then submit that exact release for independent review.

Review the rework investigation release

Reopen the submitted policy with its rework-forward rule, read its proof and record an independent decision.

Request changes to LotTrail expected answers

Record a clear review request when you cannot confirm an expected result.

Review LotTrail expected answers

Check profile selection, investigation coverage and review triggers independently before approving the frozen answers.

Enter independent LotTrail expectations

Enter the input and expected review outcome for a coverage gap while retaining the complete expected investigation.

Edit LotTrail with manual controls

Prepare a sixty-minute evidence-age threshold for coverage review.

Prove the LotTrail policy

Recheck the complete frozen policy and prepare an exact release for independent review.

Inspect original LotTrail evidence

Open the saved submission, check its complete file list and inspect the original result alongside its inputs.

Review a submitted LotTrail release

Open the saved submission and record a separate review of the complete policy and its proof.

Describe a CheckStation inspection rule in plain English

Type an inspection rule in plain English, answer the AI's question about the missing details, inspect the complete proposed rule and save it deliberately as a draft.

Review the expected results for newly approved suppliers

Check the expected inspection results for the plan that now holds the newly approved supplier rule, including its bracket width check, before approving them.

Prove and submit the newly approved supplier plan

Freeze the plan with the newly approved supplier rule, run CheckStation's complete proof of every expected result and submit that exact release for independent review.

Review the newly approved supplier release

Reopen the submitted plan with its newly approved supplier rule, read its proof and record an independent decision.

Review the expected inspection results

Check and approve the expected inspection results independently against the approved inspection plan.

Enter independent CheckStation expectations

Review the supplied inspection cases and enter the expected selected checks and refusal behaviour.

Edit CheckStation with manual controls

Require supervisor review for the approved A3 inspection binding.

Prove a CheckStation inspection plan

Prepare the complete inspection plan and verify its expected inspection results.

Review a submitted CheckStation release

Open the saved inspection plan and its original proof, then record your independent decision.

Compose a coordinated release set

Bring together two complete product releases that already have their own independent approvals. This exercise coordinates configuration readiness only. It does not claim that physical work has been completed or that one product has proved an outcome for the other.

Prepare both products and understand the hold

Prepare the new-work hold in each product. Existing committed work keeps its pinned release; fresh work waits for the coordinated opening.

Open a ready coordinated release set

Both native releases are active and retain their own approval. Check all members, then open each product explicitly. This exercise proves configuration readiness, not a physical production outcome.

Recover a missing coordinated reply

A missing reply is uncertainty, not proof of failure. Read the original native receipt and retain its identity before continuing.

Review a coordinated release set

Independently review the relationship between the two already-approved product releases. Approval of the set still does not activate either product.

Describe a SmartFACT Data SKU mapping in plain English

Type a shop SKU mapping in plain English, answer the AI's question about the missing details, inspect the complete proposed SKU table and save it deliberately as a draft.

Review the expected results for the hinge pair mapping

Check the expected results for the spares shop SKU table that now maps the hinge pair, by column name, before approving them.

Prove and submit the hinge pair mapping

Run SmartFACT Data's complete proof of the SKU table with the hinge pair row, read its result and submit that exact table for independent review.

Review the hinge pair mapping release

Reopen the submitted spares shop SKU table with the hinge pair row, read the proof result and record an independent decision.

Request changes to ConfigSheets cases

Use a review request to explain missing coverage without changing the author’s frozen answers yourself.

Review ConfigSheets expected results

Check the matching and no-match answers as a separate reviewer before the author runs the complete check.

Enter the expected unapproved-feed hold

Supply approved as false and declare the complete held response independently. Keep the Boolean value and full explanation, then retain the case for the ordered review set.

Maintain feed sources and columns

Map the approved orders to the original customer and standard kit tables. Keep the source key, option types and exact column names together.

Edit the ordered feed selection rule

Inspect the complete approved-source rule and change its priority. Keep the unavailable-source hold and the original mapping intact.

Prove the complete approved order feed

Prepare the exact saved approved order feed, run the independently supplied answers and submit the passing native release for a separate review.

Prove a ConfigSheets selection

Prepare the whole saved selection, run its independent expected results and submit the exact passing release for review.

Inspect original ConfigSheets evidence

Open a saved check and inspect its retained results and inputs without rerunning it or changing the release.

Review a submitted ConfigSheets release

Open the saved selection and its original proof, then record an independent decision about that exact release.

Edit a whole-tab selection in the form

When plain English authoring is unavailable, use the complete selection form. Keep exact same-row conditions and approved read connections while naming the planning selection.

Enter an independent shop quantity answer

Change a supplied order to four quarter-packs and enter the independently calculated result of 1.00. The order and complete expected lines are saved together in a new mapping draft.

Maintain a shop SKU mapping

Use an approved SKU table and status effects in a complete mapping revision. Saving the mapping does not poll the shop or move stock.

Prove the complete shop mapping

Prepare the exact saved shop mapping, run the independently supplied answers and submit the passing native release for a separate review.

Correct an incomplete table change

See an incomplete explanation refused, supply the actual business reason, then save the checked rows. A refusal is not a saved change.

Enter an independent same-row table answer

Choose a customer code and a leading-zero pack code that occur on one row. Declare the expected match independently before the software checks it.

Maintain exact customer table values

Enter customer pack instructions as typed rows. Preserve a leading-zero text code and an explicit null, then save a new revision for checking.

Prove the complete customer table

Prepare the exact saved customer table, run the independently supplied answers and submit the passing native release for a separate review.

Recover an uncertain Data table save

A reply can be lost after the product saves the new revision. Keep the original request and check its outcome before trying another change.

Set an observation age limit

Prepare a five-minute limit for an explicitly registered Data observation contract. The original observation time and completeness scope come from the producer, not from an AI proposal.

Check original-time boundaries

Check independently supplied outcomes at 299, 300 and 301 seconds, plus a withdrawn observation. These cases use producer metadata retained before this lesson.

Investigate an incorrect expectation

Read a real failed proof where an expected age was entered incorrectly. Resolve the requirement and case data before seeking approval.

Bind a reviewed policy to Data

Bind the reviewed five-minute policy to an exact registered source in a saved Data selection. Preserve the complete selected native document.

Recover an interrupted binding upload

Recover an interrupted private upload by checking the original request. The native source has stored the file part even though the reply was lost.

Respect a withdrawn policy review

See a genuine refusal after the definition approval has been withdrawn. Read the review history rather than trying to bypass it.

Independently approve an observation policy

James Whitaker reviews the exact definition and cases prepared by Sarah Hughes. Definition approval stays separate from Data publication.

Withdraw an observation-policy approval

Withdraw a definition when its agreed source meaning changes. Existing locally approved releases stay pinned; future bindings need a valid review.

Describe a FactorySpec constraint in plain English

Type a product configuration rule in plain English, answer the AI's question about the details it needs, inspect the complete proposed constraint, save it deliberately as a draft and request the native engineering review.

Review the expected results for the panel constraint

Check the independently worked FA-300 cases, including the black frame with a clear panel, for the expert-approved model that now holds the panel constraint, before approving them.

Prove and submit the FA-300 release with the panel constraint

Select the expert-approved FA-300 release with the panel constraint, verify every expected result in FactorySpec and submit that exact selection for independent review.

Review the FA-300 release with the panel constraint

Reopen the submitted selection, check the panel constraint and its proof, and record an independent decision.

Review FactorySpec expected results

Use the visible practice workspace to review a model already approved by a separate expert in FactorySpec. This lesson does not establish production engineering readiness. Check the independently supplied dimensions and bill of materials before approving them.

Enter independent FactorySpec answers

In the practice workspace, enter the expected status and drawing basis for the complete frame calculation. Expected BOM values come from the engineer’s independent calculation.

Edit FactorySpec configuration in the form

In the practice workspace, label an existing engineering calculation from its drawing. Keep its expression and units unchanged; expert approval remains separate.

Prove and submit a FactorySpec release

Use the visible practice workspace to review a model already approved by a separate expert in FactorySpec. This lesson does not establish production engineering readiness. Check the whole engineering release selection and submit its exact evidence for independent review.

Request changes to a FactorySpec release

Stay in the visible practice workspace. Reopen the original submission and request a clear correction instead of approving a requirement that is not yet settled.

Review a submitted FactorySpec release

Use the visible practice workspace to review a model already approved by a separate expert in FactorySpec. This lesson does not establish production engineering readiness. Reopen the original submission and make an independent decision.

Check an interrupted FactorySpec save

Check an interrupted FactorySpec save by reading its original outcome. Keep an uncertain reply separate from a failed change, and do not repeat the save. Work in the practice workspace, with engineering approval kept separate.

Understand a result that did not pass

Find the mismatching answer without copying the result into the expectation merely to make the check pass.

Describe a KitProof rule in plain English

Open the spare fuses rule for the control box kit, type the change in plain English, check the complete proposed rule and save it deliberately as a draft.

Review the expected kits for the spare fuses rule

Check the expected kits for the configuration that now adds three spare fuses to 24 V boxes with spares, before approving them independently.

Prove and submit the spare fuses configuration

Freeze the configuration with the changed spare fuses rule, verify every expected kit in KitProof and submit that exact release for independent review.

Review the spare fuses release

Open the submitted configuration, check the changed spare fuses rule, its expected kits and the proof, and record an independent decision.

Review the expected kits

Check and approve the expected results independently.

Edit a KitProof rule with manual controls

Use source-owned controls when Plain English assistance is unavailable, then save a complete private draft change.

Use a reviewed shared definition in KitProof

Map every input explicitly, review the exact version and save through the owning product’s normal private draft change.

Prove a KitProof rule

Prepare the complete rule and verify the expected kits.

Review a submitted KitProof release

Open the saved kit configuration and its original proof, then record your independent decision.

Check an interrupted KitProof draft save

Keep an uncertain save separate from a failure, then read its original outcome without repeating the change.

Describe a LabelRules rule in plain English

Type a label rule in plain English, answer the AI’s question about its priority, inspect the complete proposed rule and save it deliberately as a draft.

Review the expected results for ACME label copies

Check the expected label decisions for the release that now gives ACME two copies of each ordered unit, before approving them independently.

Check and freeze the ACME label copies release

Check the five saved label examples for acme-two-copies, freeze the release and prepare its expected results for independent review.

Verify the ACME label copies release

Run the complete verification of the frozen release with acme-two-copies and read the proof result.

Review the ACME label copies release

Open the submitted release, check the ACME two-copy rule and its proof, and record an independent decision.

Submit the ACME label copies release

Load the reviewer’s proof for the release with acme-two-copies, then assemble and submit that exact release.

Review and verify the frozen label release

James checks the complete expected label decisions independently, then runs the candidate’s original software verification. Sarah prepared the rules and expected answers.

Check and freeze complete label rules

Check independently supplied label decisions, inspect the software result and freeze the complete release for separate review. These checks do not print a label.

Enter independent LabelRules answers

Enter independently expected label decisions and their business basis before running the rules. Keep the complete answers for all five required situations.

Edit LabelRules configuration in the form

Change an existing label rule using its complete form when AI authoring is unavailable. This saves a draft and sends nothing to a printer.

Request changes to a LabelRules release

Reopen the original submission and request a clear correction instead of approving a requirement that is not yet settled.

Review a submitted LabelRules release

Open the release submitted by Sarah and record James’s independent review of the complete label rules, expected decisions and original proof.

Check an interrupted LabelRules save

Check an interrupted LabelRules save by reading its original outcome. Keep an uncertain reply separate from a failed change, and do not repeat the save.

Submit the verified LabelRules release

After James has checked the independent expected answers and run the complete candidate verification, Sarah returns as the author to assemble and submit the exact release proposal.

Rename a label template in plain English

Describe a template change in plain English, check every proposed value and save the proposal deliberately as a draft.

Review frozen template expectations

James checks the complete expected label decisions independently. Sarah prepared the template and retained its inherited expectations.

Freeze a complete label template

Keep the inherited business expectations with the complete template, freeze its exact native target, then prepare the frozen cases for independent review.

Edit a complete label template

Change the template name and exact preview sample while retaining the complete approved layout. Saving this draft does not approve or print a label.

Verify the complete frozen template

After independent case review, run the original native verification of the entire frozen template and inherited business decisions.

Review the submitted template release

Open Sarah’s original complete template submission, inspect its retained evidence and record James’s independent decision.

Check an interrupted template save

The save reply is deliberately interrupted in this lesson. Read the original outcome without repeating the save, then continue only after the product confirms it.

Describe an OrderRun rule in plain English

Type an order rule in plain English, answer the AI's question about the details it needs, inspect the complete proposed rule and save it deliberately as a draft.

Review the expected results for the purchase-order hold

Check the expected results for the policy that now holds BENCHCO orders without a purchase-order reference, before approving them independently.

Declare the expected hold for an order without a purchase order

Declare that the BENCHCO order without a purchase-order reference is now held by name, using the rule saved from the plain-English proposal, before the policy is proved.

Prove and submit the purchase-order hold policy

Freeze the policy with the purchase-order hold, verify every expected result in OrderRun and submit that exact release for independent review.

Review the purchase-order hold release

Open the submitted policy, check the purchase-order hold, its expected results and the proof, and record an independent decision.

Review the expected routing results

Check and approve the expected routing results independently against the approved order routing policy.

Enter independent OrderRun expectations

Enter expected order priority and blocked-customer behaviour using the complete native case form.

Edit OrderRun with manual controls

Set the default order priority to urgent when no routing rule provides another value.

Prove the OrderRun policy

Prepare the complete order routing policy and verify its expected routing results.

Review a submitted OrderRun release

Open the saved order routing policy and its original proof, then record your independent decision.

Describe a ParcelOffice preset rule in plain English

Type a preset rule in plain English, answer the AI’s question about missing details, inspect the complete proposed rule and save it deliberately as a draft.

Review the expected results for Blinds in long boxes

Check the independently supplied preset results for the Assisted policy that now includes Blinds in long boxes, before approving them.

Prove and submit the Blinds in long boxes policy

Read the native proof for the Assisted policy with Blinds in long boxes and submit that exact release for independent review.

Review the Blinds in long boxes release

Reopen the submitted Assisted policy, check the Blinds in long boxes rule and its proof, and record an independent decision.

Review ParcelOffice expected results

Review a guided despatch policy before it is used. Automatic mode has its own expert approval and station checks in ParcelOffice. Check the independently supplied packing and service choices before approving them.

Enter independent ParcelOffice answers

Enter the independently approved packing profile for the accessories order. Save the source case before freezing a candidate for review.

Edit ParcelOffice configuration in the form

Rename an existing packing rule using its complete form. Keep its approved profile and condition together for later checking.

Prove and submit a ParcelOffice release

Review a guided despatch policy before it is used. Automatic mode has its own expert approval and station checks in ParcelOffice. Check the whole guided despatch policy and submit its exact evidence for independent review.

Request changes to a ParcelOffice release

Reopen the original submission and request a clear correction instead of approving a requirement that is not yet settled.

Review a submitted ParcelOffice release

Review a guided despatch policy before it is used. Automatic mode has its own expert approval and station checks in ParcelOffice. Reopen the original submission and make an independent decision.

Check an interrupted ParcelOffice save

Check an interrupted ParcelOffice save by reading its original outcome. Keep an uncertain reply separate from a failed change, and do not repeat the save.

Read the saved working plan

Read the original requirement and questions as a separate reviewer without changing the plan.

Keep questions visible in a working plan

Retain the whole requirement and save precise questions before selecting product changes.

Review PrintStation expected results

The two people in this lesson each have PrintStation Owner access. They author and review separately in Automation. These are office controls for the unattended client, not printing from a phone. Check the independently supplied routing and hold results before approving them.

Enter independent PrintStation answers

Enter the independently expected transport outcome for unknown printer output. Keep the full route and hold cases, and leave physical printing unconfirmed.

Edit PrintStation configuration in the form

As a PrintStation Owner, prepare a transport policy on desktop using approved sources, media and printers. A prepared route does not prove physical printing.

Prove and submit a PrintStation release

The two people in this lesson each have PrintStation Owner access. They author and review separately in Automation. These are office controls for the unattended client, not printing from a phone. Check the whole printer-route policy and submit its exact evidence for independent review.

Request changes to a PrintStation release

The independent reviewer also needs native PrintStation Owner access. Reopen the original submission and request a clear correction instead of approving a requirement that is not yet settled.

Review a submitted PrintStation release

The two people in this lesson each have PrintStation Owner access. They author and review separately in Automation. These are office controls for the unattended client, not printing from a phone. Reopen the original submission and make an independent decision.