2 Replies Latest reply: Jun 7, 2012 10:37 AM by Segal RSS

    LIO

    938167
      Hi,

      We are looking at using the system to generate ingredient lists and had the following questions:

      •     Due to the modularity of our system is LIO going to work for us? From what we have seen where we have two formulation ingredient outputs feeding a formulation, the LIO statement only declares ingredients one level below and does not declare the ingredients in the lower level formulations.

      •     Where a group is declared it is not declaring the additive number ie the description in the ingredient breakdown is not flowing in. Is this something that needs to be set up?

      •     Citric acid is not declared because it doesn’t have a quantity against it in the formulation. Can we set a rule to incorporate this in the listing?

      •     We are also having trouble understanding the differences between alias, disclosure, groupings and how we set restrictions. Is there an e-recording or information you could recommend to help us. We think we will need assistance setting this up properly and wondering the best way to go about it.

      Thanks.
        • 1. Re: LIO
          SDelzell
          Question: Due to the modularity of our system is LIO going to work for us? From what we have seen where we have two formulation ingredient outputs feeding a formulation, the LIO statement only declares ingredients one level below and does not declare the ingredients in the lower level formulations.


          Answer: Let's walk through how LIO interacts with a hierarchy of specifications...

          - If you point LIO to a given material it will show the material's %breakdown or combined ingredient statement. You can choose between the two options by right clicking on the material.

          - If you identify both the material and the formula on the summary tab then you will see the composition of the various inputs to the formula. Again by right clicking you can choose to use the %breakdown or combined ingredient statement.

          - If any of the input materials to the formula are formula outputs then you can right click on the item and select the next level formula using context. If there are more than one formula that can create the material you must choose one. You can repeat this process until you are at the lowest level of detail.

          --------------------------------------------------------------------------------------------------------------------------------------------------

          Question: Where a group is declared it is not declaring the additive number ie the description in the ingredient breakdown is not flowing in. Is this something that needs to be set up?


          Answer: If you need information from the description to be presented I believe your only option is to use the combined ingredient statement. Another option would be to use the component catalog and define additional declarations. When you are in LIO declarations can be used to alias a composition value.

          --------------------------------------------------------------------------------------------------------------------------------------------------

          Question: Citric acid is not declared because it doesn’t have a quantity against it in the formulation. Can we set a rule to incorporate this in the listing?


          Answer: LIO requires the component target value to be greater than 0%. This requires the input material to have a value greater than zero.

          --------------------------------------------------------------------------------------------------------------------------------------------------

          Question: We are also having trouble understanding the differences between alias, disclosure, groupings and how we set restrictions. Is there an e-recording or information you could recommend to help us. We think we will need assistance setting this up properly and wondering the best way to go about it.


          Answer: We are currently working on a recording for this item. We shared some of the material at user group. That being said let me quickly describe the items mentioned...

          - Component Catalog Alias: A means to standardize naming for components within %breakdowns. As an example:

          Term: SALT
          Alias: TABLE SALT
          Alias: COMMON SALT
          Alias: ROCK-SALT

          If the component catalog values are used to describe the %breakdown items the formula will roll up the values to the term.

          - Component Catalog Group: Allows you to automatically group components using the same term (trem or alias).

          - Component Catalog Disclosure: If terms or alias are found for a given component catalog item the Disclosure values are available for labeling. Therefore salt could be labeled as "SEL" in Canada. The disclosure value would be "SEL" and the restriction would be "Canada".
          • 2. Re: LIO
            Segal
            Please let us know if you have any more LIO questions.
            Thanks.