IPLM glossary

Concept	Description
Alias	An alias is a user generated string that is attached to a particular release of an IP (IPV). Once attached the alias can be used to refer to the IPV in place of its release number. Example aliases might include 'GOLD', 'READY_FOR_RELEASE', etc. See IP Aliases for more information.
Attributes	Ad-hoc metadata key value pairs that can be directly applied to Perforce IPLM objects without pre-definition. Used to store information to support design flows on Perforce IPLM objects. If formatted correctly, they will be displayed as Widgets on IPLM Web. See Attributes for more information.
CIPB	Component and IP BOM (CIPB), equivalent term to the IP Hierarchy. See IP Hierarchy for more information.
IP	IPs are the foundational unit of design management in Perforce IPLM. IPs are design abstraction objects that centralize metadata, design, permission, and externally derived data in one place. IPs are reusable and fully traceable through Perforce IPLM. IPs capture releases (IP Versions or IPVs) that represent immutable design states. Workspaces can be built from IP Hierarchies, and new IP releases can be created from Workspaces or directly edited on the Perforce IPLM server. See IP Management for more information.
IP FQN	An IP FQN (Fully Qualified Name) has four components: LIB : Library Name IP : IP Name VERSION : Version or Release (defaults to LATEST) LINE : IP Line (defaults to TRUNK) A full IP identifier is constructed as follows: <LIB>.<IP>@<VERSION>.<LINE> See Listing IPs in the Catalog for more information on IP naming.
IP Hierarchy	Hierarchically related IPVs that constitute a design. See IP Hierarchy for more information.
IPV	IPVs are IP Versions, or releases of an IP. IPVs are immutable records of the captured design state, including design files and metadata. IPVs are versioned with sequential numbered releases. See IP Versions (Releases) for more information.
Events	Perforce IPLM can publish every event that happens across all objects in the platform. Users and groups can subscribe to events and events can be sent to event consumers for email alerts, data aggregation, etc. See Events for more information.
Group	A group is a set of users and/or other groups that can be granted access to Perforce IPLM design objects. See Permissions Management for more information.
Hooks (Client Side)	Attachment points in the IP Lifecycle for automation. Used for automatically running verification and simulations and capturing results back onto Perforce IPLM objects as metadata. See Workspace Automation for more information.
Hooks (Server Side)	Hook scripts associated with server side events (adding new IPs, editing IPs, alias locking, etc). Used to enforce business logic in Perforce IPLM development flows. See Server Side Hooks for more information.
Label	A label is a way to classify IPs and Libraries and may be used to aid filtering and search in PiCLI and IPLM Web. See Labels for more information.
Library	A Library is a collection of IPs, where each IP belongs to one Library. See Library Management for more information.
Line	Lines are lines of development on IP objects. Each line has its own series of releases. The default line is TRUNK. See IP Lines (Branches) for more information.
Permissions	Perforce IPLM Permissions control access to Perforce IPLM objects at the Library, IP, and Line levels. See Permissions Management for more information.
IPLM Cache	IPLM Cache is a IP caching server that manages a central disk location populated with IPVs. IPVs in IPLM Cache can be quickly linked to user workspaces, which speeds workspace load and reduces disk space usage. IPLM Cache servers are typically deployed one (or more) per site. See IP Caching for more information.
Private Resource	An IP resource that will only be populated into the workspace if its direct parent IPV is the top level IPV in the workspace. Private Resources are used in the Build IP Delivery Flow. See IP Hierarchy for more information.
Project	A Project is a top-level IP. Note that this is context dependent. One user may be working on the ADC and for them that is the project. But the ADC might also be a resource used by another IP. See IP Hierarchy for more information.
Project Property	Project Properties are used to configure Perforce IPLM Workspaces. They control IP location in the workspace, group permissions, conflict resolution, and cache mode configurations. See Workspace Configuration for more information.
Property	Properties are typed, pre-defined key value pairs that can be added to IPs and IPVs to extend the Perforce IPLM data model. Properties are used to track custom data about IPs, examples include process info, licensing requirements, lifecycle stage, etc. Properties are grouped into Property Sets and attached to IPs. See Properties for more information.
Property Set	A Property Set is a group of Properties attached to a particular IP/IPV. Once a Property is created it should be added to a Property Set which in turn should be attached to an IP/IPV. There is a "global" Property Set that is by default assigned to all IP/IPVs in the system. See Properties for more information.
Query	A Perforce IPLM query language expression used to search for objects in Perforce IPLM. See Perforce IPLM query language for more information.
Release	A release results in a new IP Version (IPV) and occurs when a material change happens to the meta-data or design files of an IP. Adding a new IPV resource, changing an IP's design files, and modifying project properties all result in a new release (version) of an IP being generated. See IP Versions (Releases) for more information.
Resource	A resource is a child IPV attached to another IPV through the 'resources' field. The IP Hierarchy is build through resource references set on the parent IPV. See IP Hierarchy for more information.
Saved query	A Perforce IPLM query language expression that has be saved (and possibly shared) for future use. Can be created and used on PiCLI or IPLM Web. See Saved queries for more information
Snapshot	Snapshots capture a workspace state to the Perforce IPLM server which can be recreated and shared for the purpose of verification, debug, hotfix, or support facilitation. Snapshots are associated with a particular IPV. See Capturing the Workspace State with Snapshots for more information.
Traceability	Perforce IPLM objects are fully traceable through the Perforce IPLM platform. See Tracing IP Usage on the Server, Listing Workspaces, and Perforce IPLM query language for more information.
User	A Perforce IPLM user that can be granted access to Perforce IPLM design objects.
Widgets	Specially formatted Attributes that will display graphical metadata on IPLM Web. Graphs, images, iframes, tables, and text displays are example Widgets. See Widgets for more information.
Workspace	Workspaces are created from Perforce IPLM releases (IPVs). They consist of design data corresponding to Perforce IPLM releases populated to disk location. See Workspaces for more information.