Attribute Basics

Attributes can be used for all types of information you want to save on a part or subpart.  Examples are capacity calculation, machine assignments, dimensions, special generated texts, etc.  Attributes are defined and assigned to parts in CORE - Setup - Products - Parts using the Attributes tab.

Types of Attributes

• Local - Only available to the selected part's BOM.   If this selected part is a child part in a subassembly, the local attribute will be retained wherever the subassembly is used throughout the BOM.  If the selected part is added in another area of the BOM, the local attribute will not be present.
• Global - Exists in all instances of the component within the entire BOM.  A global attribute’s scope exists everywhere that part is used.  
• System - System attributes are those are available to all parts.  They are defined on the System tab within the Attributes tab and can be assigned to any part from the System tab.

Example of Use

• If you have a System attribute named ABC, you can assign it to multiple parts.  Be aware than any changes to ABC affect all parts that have ABC assigned.  That is why if you try to delete ABC, you get the popup dialog asking you to confirm.  System attributes are edited on the System tab within Part Setup - Attributes.  
• If you have a Global attribute WEIGHT assigned to part XYZ, you can have another Global attribute named WEIGHT assigned to part ABC, and the code can be different between the two WEIGHTs.  However, note that everywhere part XYZ occurs (in any ordered part), it will use the WEIGHT attribute associated with XYZ.  
  • So, if you have a double hung window with part XYZ and a slider window with part XYZ, changing WEIGHT's code while editing the double hung means you are also changing WEIGHT's code on the slider window.  Deleting WEIGHT from part XYZ in the double hung will also delete WEIGHT from XYZ in the slider window.  
    • If you need to do something special in WEIGHT for the double hung, but not the slider, you will need an IF statement checking to see if the current part is the double hung part number, and then add the special code within that IF statement.  
• If you have a Local attribute ABC assigned to part XYZ that is below the part IG in the bill of material, you can have another local attribute named ABC assigned to part XYZ that is below the part MONO in the bill of material, and the code can be different between the two ABCs. 

In summary, it is easier to maintain attribute code with System and Global attributes, and best used if the logic is shared between multiple windows, mono glass parts, etc.  If you put shared logic in a Local attribute, when the logic changes you must change it in every single Local attribute with that logic.

Attribute Variable Types

• Number – Attribute is a constant identified by the value entered into the numeric entry box.  The numeric entry can be a whole number, decimal or exponential (ex 10e4).
• String – Attribute is a constant identified by the value entered into alphanumeric entry box.
• Expression – Attribute value is determined by a basic calculation.  The calculation is y = mx + b, where y = return value, m = multiplier, x = attribute, and b = addition.
  • P – Parent (attribute on the part at the level above in the BOM)
  • S – Sibling (attribute on the same part in the BOM)
  • R – Root (attribute on the part at the top level of the BOM, most commonly the orderable part)
• Include – Attribute value will be determined by the option code selected from the drop-down.  The return value is either true or false if the option is selected in 'Order Entry', true, else false.
• Script – Attribute value is determined by a script.  This script is written within the ‘Visual Basic’ script engine that is embedded into FeneVision. 

Tips

• One of the most common mistakes is not understanding the scope of System, Global and Local attributes.
  • If you change a System attribute on the System tab, you are changing it everywhere it is used in the BOM. 
  • If you change a Global attribute on a certain part, you are changing it everywhere that part is used in the BOM, even on a different ordered part.  
  • If you change a Local attribute on a part within a subassembly, you are changing it for that part everywhere that subassembly is used.  
  • The above statements also apply to delete!
• Location – Location specific attributes appear bold in the attribute grid.  System attributes can be assigned to one or more locations with each location containing a different version of that attribute.  When attributes are then evaluated, the location specific version of that attribute that matches the manufacturing location of the part will be evaluated. 

• If an attribute that is added has the same name as an existing system attribute, the following prompt will appear.  Choosing ‘No’ will allow the user to add a new name for the attribute.  Choosing ‘Yes’ will add the system version of the attribute.  However, if a location is specified in the ‘Location’ drop down and a location specific version of that attribute exists, that version of that attribute will be added to the part when ‘Yes’ is chosen.

  

• Deleting an Attribute - If a user attempts to delete a Global or System attribute from the Parts tab where multiple instances of that part contain that attribute, the following message will appear warning the user of the number of other items that will be affected if this attribute is deleted.

  

• Substitute Parts - Users should take caution when modifying attributes copied from the substitute part.  If changes are made to attributes on a part that is a substitute part for other parts, the changes (including additions and deletions) will not cascade to other parts.  When a change is made, the user is prompted that additional configuration may have to be made to the other parts.
• Attributes and their part assignments exist in the Attributes table of the FVMaster database.

Common Attributes