A spec instance is the act of adding a product from a Standards folder into a particular project. Each spec instance copies all the attributes of the specification into the Project. Spec instances always involve product specifications that are linked across multiple projects. In other words, many of the attributes of the spec have already been determined within the Standards folder.
While the basic attributes of each spec instance are determined within the Standards folder, users may also want to “fine-tune” individual spec instances to meet project goals. This is because even among a standardized set of projects, the exact attributes will likely vary from project to project. Typical examples of project-specific fields include Code/Tag, Quantity, and Cost. Project-related Attributes and Nested Project-related specs are also fields that can be added inside a Spec Instance. To eliminate confusion, while working within the project, all Attributes and Nested specs that have been assigned in the Standards spec display as read-only fields.
How do Changes Made to Specs in Standards Affect Spec Instances?
When you’re adding spec instances within a given project, you’ll notice a link symbol next to every spec instance. Clicking here will take you back to the Standards folder that houses the spec. Note that changes made to the corresponding spec in the Standards folder may not always impact the spec instance. This is because at certain times users may wish to differentiate between the spec instances across linked projects, keeping some of them the same while altering others. Read more about why you may want to edit some, but not all, spec instances here: