Understanding metadata in Helix IPLM

Helix IPLM enables the collection, display, and search of rich sets of metadata associated with IP, Library, and IP Version objects (as well as many others). Metadata can be leveraged to display data sheets on IPs, simulation, verification, and requirements data, licensing, process and similar information to track and explain the IP.

Attaching metadata in Helix IPLM

Helix IPLM provides a number of frameworks for attaching meaningful metadata to IPs, IP Versions, Libraries, Saved queries, and a number of other objects. Attaching attributes, widgets, properties, and property sets to IPs and their releases enriches the value of the design states captured in Helix IPLM releases. We can both recreate these design states by accessing releases, and understand the releases themselves, for instance what is the performance of the design at this release, which bugs are associated with it, from whom should I request access for my project, etc. Helix IPLM provides a platform for attaching the metadata needed to understand the design, and the interfaces required to capture that information automatically without additional user effort.

Helix IPLM supports both structured (pre-defined and administrator created) metadata in the form of Properties and Property sets, and more ad-hoc user generated data in the form of Attributes and Widgets. Properties are used to extend the built in Helix IPLM data model in a consistent way that supports centralized control and maintenance. Attributes and Widgets are more free-form and used to store data on objects to support automation flows, and to display graphical data on IPLM Web.

See Helix IPLM metadata for more information.

Properties and property sets

Properties are admin created, IP owner managed key/value pairs that are grouped into property sets. property sets are then associated to particular IPs. The properties in the applied property sets extend the IP data model to include additional data fields that should be tracked for that type of IP. IP configuration options, process information, Identifiers, workflow state, requirements, verification information, and licensing information are examples of values that might be tracked as properties.

IP properties can be displayed in IP Catalog listings on PiCLI and IPLM Web and are available from the API.

The Helix IPLM query language can be used to search for IPs based on their Properties and their values.

More information on configuring Properties and Property Sets can be found on the Properties page. Information on setting Property values on particular IPs can be found on the IP, IPV, and IP Line Metadata page.

Attributes

Attributes are also key/value pairs, but differ from properties in that they don't have to be pre-defined by an admin before they can be used, always have a text type data value, and are attached directly to Helix IPLM objects rather than being first collected in a set (as with a property set). This makes attributes a more ad-hoc method of attaching metadata to Helix IPLM objects. Attributes can be saved to and retrieved from objects as needed, providing a convenient way to store data needed to understand or characterize the object. Examples of data that might be stored as an Attribute include characterization data, data needed to support customer flows, links to external data, graphs, documentation fragments, and more.

Attributes as widgets

Specially formatted attributes will be displayed in IPLM Web as graphical widgets. A variety of Widgets are supported by Helix IPLM, including tables, text, bar, pie, and line graphs, images, iframes, links, collapsible trees, and many others. These widgets can be used to create data-sheets on IPLM Web pages for IPs,  IPVs, Libraries, and Saved queries. More details for configuring and displaying Widgets is available in Widgets.

Example Widgets in IPLM Web are shown below:

Labels

Labels are used to categorize and filter IPs in the catalog from IPLM Web and PiCLI. Labels are admin defined strings that users can attached to specific IPs and Libraries. Process, foundry, IP Category, Design Type (amplifier, cpu, etc), and Business Unit are all potential categories that might be implemented with Labels. Selecting multiple labels will filter the catalog by all the Labels selected. More information on Labels is found on the Labels page.

Label definitions also include a color value which is displayed in IPLM Web.