Schedrix™ Allergen Matrix works out each item's allergens from its production BOM (bill of materials, i.e. the recipe), through every level, for a named person to confirm. The app only reads your items, recipes and production orders. It never changes them, including each item's own allergen list. It works within your HACCP plan, not in place of it: your site's own specification and processes decide.
For anything this page doesn't answer, email support@capability-systems.com.
What you need
- Business Central Premium, for its manufacturing features: items with production BOMs.
- One item attribute that holds each item's allergens, on components and finished items alike.
- For Allergen Changeovers, released production orders. With routings, it shows them by work or machine centre.
Set up
Search for Allergen Matrix Setup. Until an allergen attribute is chosen, the app's pages offer to open it.
Choose the allergen attribute
In Allergen Attribute ID, choose the item attribute that holds allergens. Each item's value is either the allergens, separated by commas, such as "milk, eggs, sesame", or "none" for an item with no allergens. A blank value counts as not known, which isn't the same as "none".
Allergens match ignoring capitals, spaces and hyphens, so "Tree nuts" and "tree-nuts" are the same. Different words don't match: "milk" and "dairy" are two allergens.
If you chose an allergen attribute in Schedrix Production Sequencing 1.0, upgrading Schedrix copies it here, unless one is chosen here already.
Give people permission sets
| Permission set | What it lets them do |
|---|---|
| Allergen Matrix User (SRX AM User) | See every page of the app, read only. |
| Allergen Matrix Confirm (SRX AM Confirm) | Everything a user can, plus Confirm. |
| Allergen Matrix Admin (SRX AM Admin) | Everything a user can, plus Allergen Matrix Setup. It doesn't include Confirm. |
Give Allergen Matrix Confirm only to the people your site trusts to confirm allergen lists. Who Can Confirm Allergens, on the setup page, lists the people and groups who hold Allergen Matrix Confirm, SUPER or SUPER (DATA).
Group orders into lines
Group Orders into Lines By sets how Allergen Changeovers groups released production orders: Automatic, Work or Machine Center, Location, or All Orders Together. Automatic groups by centre when any released production order has a routing, otherwise by location; Grouped By shows what it works out today.
Under Work and Machine Centers Shown as Lines, list the centres that are your lines. With none listed, every centre with operations on released production orders is a line. Add Centers in Use fills the list; then remove the ones that aren't lines.
Read the matrix
Search for Allergen Matrix, or open it from the item list. Allergens run across the top, 20 at a time: use Previous Set and Next Set for the others. Each cell says From BOM, or On item only (entered on the item, but not from the recipe).
A blank cell never means the item is free from the allergen. Where an item's allergens aren't known yet or can't be worked out, the row shows only what is known so far, and Status says why.
Filter by Item Filter, Item Category Filter, Allergen Filter, or Show: All items, Confirmed or Not checked. Export to Excel writes the items shown, with the date and filters at the top.
| Status | What it means |
|---|---|
| Missing from item | The recipe gives an allergen that isn't entered on the item. |
| All on item | Every allergen from the recipe is entered on the item. |
| Not known yet | A component in the recipe has no allergens entered. |
| No production BOM | The item has no recipe. |
| BOM not in use | Neither the BOM nor a version of it is certified and active on the date, or it has no lines valid then. |
| BOM contains itself | The recipe includes itself through its sub-recipes. |
| BOM too large | The recipe has more than 5,000 lines across its levels. |
Checked says Not checked, or Confirmed for the date the confirmed list was worked out for.
Trace an allergen
- Allergens from BOMs, from the matrix, the item card or the item list, puts each item's Current Allergens next to From BOM, On Item Only and Missing From Item. If an item's own list should change, change its attribute yourself: the app never writes it.
- Show Sources lists the component each allergen comes from, and the sub-assemblies and phantom BOMs (recipes that are only part of another recipe) it comes through.
- Allergen Where-Used lists every item an allergen reaches, with the path. Open it from the matrix to look up the allergen in its Allergen field, or from an item card to start from that component.
The matrix, Allergens from BOMs and Allergen Where-Used read recipes for the date in BOMs On, as a production order would. It starts at Business Central's work date (normally today); enter a later date to see a recipe change before it starts.
Fix a list at source
The app keeps no allergen list of its own. Each item's allergens come from its recipe's components and from what is entered on the item, so when a list is wrong, fix it where it comes from, in Business Central:
- An allergen in a supplier's specification that isn't on the component yet: enter it in the component's allergen attribute. Every item whose recipe uses the component then shows it.
- A recipe that is wrong, such as a component missing or no longer used: correct the production BOM, or certify a new version of it.
- An allergen no recipe can give, such as cross-contact on a shared line: enter it in the item's own allergen attribute. The matrix shows it as On item only. It isn't part of the list a named person confirms, which is the allergens from the recipe.
A change to the recipe or a component's allergens that alters a confirmed list sends the item back to Not checked.
Confirm a list
You need Allergen Matrix Confirm.
- On Allergens from BOMs, set BOMs On to the date you are checking, and select the items.
- Check each list against your site's own specification.
- Choose Confirm. The app asks first, then keeps your name, the time and the date.
If the list changes later, through the recipe or a component's allergens, the item goes back to Not checked. It stays Not checked, even if the list changes back, until someone confirms it again. Confirmation History shows each confirmation, and when the list was first found changed, with the allergens added and removed. That row keeps the user ID of whoever's page found the change, who may be any reader.
Allergen Changeovers
Search for Allergen Changeovers, or open it from Released Production Orders. It shows each line's orders for a week, Monday to Sunday, in start order. Use Previous Week, Next Week or Week Starting to move.
It counts each order that follows one carrying an allergen it doesn't have, and shows the count on each line. The first order shown is compared with the last one before it on the line, and the Note names it. Each order's allergens come from its own components on Business Central's work date, then any on its item only, which the Note names. Checked says Confirmed for a date only when its components' allergens match the item's confirmed list.
The counts are for planning. Your site's own specification and processes decide what happens between two orders.
Common questions
Not known yet. A component has no allergen value. Enter its allergens, or "none". Show Sources lists it as Component without allergens.
BOM not in use. Certify the production BOM, or a version of it active on the BOMs On date, and check it has lines valid on that date.
BOM contains itself. The Note shows the loop, such as "P1 > P2 > P1". Correct the BOM.
BOM too large. The app doesn't work out recipes of more than 5,000 lines across their levels. Email support if you need this raised.
Orders Without Routing isn't 0. Business Central records which centre an order runs on only in its routing, so these orders are on no line. Give them routings, or group by Location.
A changeover says Not known. One order's allergens can't be worked out. Its Note says why.
Someone with Confirm isn't in Who Can Confirm Allergens. They hold it inside a permission set of your own, which the list doesn't show.
Allergen Where-Used is slow from a component. When Business Central's own where-used can't be used, the app reads each recipe itself, which takes longer.
Your data
The privacy policy says what the app keeps and what Business Central sends us.