the information & data that describes the specific object in the Agile system.
Administrator can create and rename subclasses, and also delete any
subclasses that have not been used by Agile users.
1. User
2. Part, Document 3. ECO, ECR, SCO, etc.
4. Broker, Distributor, Component Mfr., Contract Mfr., and Mfr. Representative
When users create a new object in Agile, they specify one of the Agile-supplied subclasses or a subclass that the administrator has created (or renamed) per your company’s requirements. Subclass names cannot be used more than once within an Agile system. A few classes offer multiple out-of-box
subclasses.
The object type plays a part in user access and permissions. For example, you can restrict a user’s privilege to either the Changes base class, the Change Orders class, or the ECO subclass (or another, user-defined subclass of Change Orders class).
Installed Agile Classes, Base Classes, and
Subclasses
The following two tables list all the possible installed object types in Agile PLM. Classes are
grouped being routable or non-routable, which is discussed further on. Also covered in this section:
à
Discovery and Read Privilegesà
Routable and Non-Routable ObjectsThe following two tables list all the possible installed object types in Agile PLM, grouped by the routable and non-routable distinction. Your company may have purchased server licenses to a subset of this list. A class appears grayed out in the administrator’s list of classes if your company has not purchased its server license.
Base class Class Subclass Description
Routable objects: the means to direct or recommend changes to non-routable objects; these classes have a default workflow for changes to seek approval from other users; objects from these classes can be changed without approval.
Changes Change Orders ECO Directives to change an item; can
advance the revision (“rev”) of an item
Page - 65
Base class Class Subclass Description
Change Requests ECR Requests for a change to an item Deviations Deviation Directives to temporarily substitute
one item for another
Manufacturer Orders MCO Changes to AML data, such as information about manufacturers or manufacturer part numbers Price Change Orders PCO Directives to change a published
price; can advance the revision of a published price
Site Change Orders SCO Changes to BOM and AML information for a specific site Stop Ships Stop Ship Directives to stop shipping/using an
item Substance Declarations Substance
Declaration Seeks compliance information for each substance within the specification
Part Declarations Part Declaration Seeks part-level compliance information and other composition header-level information
(manufacturing parameters) JGP Declarations JGP Declaration Seeks compliance information
(weights) according to the JGP standard
Homogeneous Material
Declarations Homogeneous Material Declaration Seeks complete breakdown of parts on the Bill Of Substances and compliance information at the homogeneous material level Supplier Declarations of
Conformance
Supplier Declaration of Conformance
Seeks compliance with specifications from customers and government agencies
IPC 1752-1 Declarations IPC 1752-1
Declaration A Joint Industry Guide (JIG) material composition declaration for electronic products
Declarations
IPC 1752-2 Declarations IPC 1752-2
Declaration A homogeneous material composition declaration for electronic products
Packages Packages Package Packages of data to share with
partners
Product Service Requests
Problem Reports Problem Report Quality incidents with items or products
Page - 66 Agile Product Lifecycle Management
Base class Class Subclass Description
Non-Conformance Reports
NCR Quality conformance issues with items or products
Activities Program; Phase;
Task Components of project planning in Product Portfolio Management; activities are time-based objects to which resources can be assigned
Programs
Gates Gate Project management milestones in
Product Portfolio Management; gates identify cross-PLM deliverables of the product development process to enable executive reviews of programs
Corrective and Preventive Actions
CAPA Requests for corrective actions and preventive actions
Quality Change Requests
Audits Audit Proactive reviews of business processes
Automated Transfer Orders
ATO Transfer or publication of a product record that is automatically triggered by a workflow
Transfer Orders
Content Transfer
Orders CTO Transfer or publication of a product record that is manually triggered
Base class Class Subclass Description
Non-Routable Objects: objects in these classes are not routed to Agile PLM users with workflows; objects from some of these classes, however, are changed by a user submitting a workflow (from routable classes) for approval from other users.
Customers Customers Customer Clients of the company
Discussions Discussions Discussion Informal, threaded dialogue
File Folders File folders File Folder Objects that include files or URLs; this class includes all file folder objects except historical report file folders
Documents Document Specifications, blueprints,
manufacturing data, and so forth
Items
Parts Part Parts manufactured within the
company, or provided by
manufacturers or suppliers and given internal part numbers
Manufacturers Manufacturers Manufacturer Qualified manufacturers
Manufacturer
Page - 67
Base class Class Subclass Description
Part Groups Part groups Commodity
Part Family
Containers of other parts (items or manufacturer parts) that share the same properties, such as prices, approved supplier lists, and composition.
Note This object was named “Commodities” in previous releases of Agile PLM. Quote Histories Quote History Organizes bid prices from RFQ
responses; cannot be revised by a PCO (see Changes)
Prices
Published Prices Published Price;
Contract Organizes prices of the company’s products; can be revised by a PCO (see Changes)
Standard Reports Administrator Report; Standard Report
The out-of-box reports for
administrators (Administrator Reports) and users (Standard Reports include Products, Sourcing, Quality, Process, Personal, and Global reports) Custom Reports Custom Report Reports created and used within
company
Reports
External Reports External Report Reports created outside Agile PLM
Requests For
Quote Requests for quote RFQ Requests for quote, which are assembled from sourcing projects and sent to suppliers for formal bids
RFQ Responses RFQ responses RFQ Response Bids, that is, responses from suppliers to your company’s RFQs
Sites Sites Site Manufacturing locations within the
company, or closely partnered with the company
Sourcing
Projects Sourcing projects Sourcing Project Work preparatory to creating RFQs and capability for analysis across multiple RFQs
Specifications Specifications Specification Lists of banned substances (or substances of concern) and their threshold values
Substances Substances Substance A single chemical element used in
composition of items, manufacturer parts, and part families
Page - 68 Agile Product Lifecycle Management
Base class Class Subclass Description
Materials Material A compound chemical, a substance consisting of multiple substances Subparts Subpart A subunit of a component
Substance Groups Substance Group A group of multiple substances, with a base substance that is what legislation is interested in, for example, “Lead and Lead Compounds”
Suppliers Suppliers Broker; Distributor;
Component Mfr.; Contract Mfr.; Mfr. Representative
Qualified suppliers of manufacturer parts; used by PCM (which uses the out-of-box subclasses) and PG&C solutions
Users Users User Individuals using the Agile PLM
system
User Groups User groups User Group Groups of people using the Agile PLM system, e.g., departments, teams, site-specific groups
Your Agile administrator may have created or renamed subclasses. The administrator defines new objects by creating subclass objects under each object class. For example, under the Deviations class, you could see new subclasses such as “MechDev,” “SWDev,” and “Part Switch” in addition to the default subclass, Deviation.