Accounts Receivable Department |
Used in ENOVIA Product Line Management. People
who receive payment for sales orders and then promote sales orders to
the Payment Received state. |
Build Management |
Used in ENOVIA Product Line Management. People
responsible for managing Software Build objects. |
CES_ADMIN |
Administration group for Component Reuse. |
CES_DESIGN_ADMIN |
Design Administration group for Component Reuse. |
Change Boards |
Used in Engineering Central. This is
the parent group of all the change board groups. Members of the change
board are responsible for reviewing ECRs. At least one Change Board must
exist -- the applications are designed around the assumption that there
is generally more than one in a company. Product Lines contain a Change
Board attribute, declaring which change board is responsible for it.
All Change Boards must be child groups of this group. |
Company Name |
Deprecated. The functionality of the Company
Name group has been replaced with the Company Name role. The name of
this group has been changed to Company Name Old (the symbolic name remains
group_CompanyName). Any existing code that uses this group should continue
to work (as long as the code properly referred to the symbolic name and
not the actual name). |
Design Engineering |
Used in ENOVIA Variant Configuration Central. In
Product Option Manager, Design Engineers are responsible for adding engineering-related
rules for a configurable product, including engineering-related compatibility
rules, inclusion rules, rule extensions, and resources. Design Engineers
also create parts, generate the Generic BOM, and review and test the
product structure. |
Distribution Groups |
Used in Engineering Central. Distribution
Group is the parent group of all the Distribution Groups. Members of
Distribution Groups are notified upon the release of an ECO and its related
parts. At least one Distribution Group must be created for the process
to work correctly. |
Documentation |
Used in ENOVIA Product Line Management and ENOVIA Variant Configuration Central. Persons in charge of documenting the software. |
Order Entry |
Used in ENOVIA Variant Configuration Central. People
responsible for validating product configurations (when the system does
not validate automatically) and generating Precise BOMs for product configurations.
Order Entry Clerks also may enter the order into the MRP system and enter
the promised delivery date for a sales order, as assigned by the MRP
system. |
Product Management |
Used in ENOVIA Variant Configuration Central. People
responsible for adding features and options to configurable products,
adding marketing-related compatibility rules, and reviewing and testing
the product structure. |
Production Support |
Used in the ENOVIA Variant Configuration Central. People
responsible for monitoring sales orders as they move through the manufacturing
system. |
Project Originators |
Used in Program Central. Parent is Project
Users. |
Project Users |
Used in Program Central. Parent of Project
Originators. |
Sample Change Board 1, 2, 3 |
Used in Engineering Central. Children
of Change Boards. |
Sample Distribution Group 1, 2, 3, 4 |
Used in Engineering Central. Children
of Distribution Groups. |
Shadow Agent sd |
Hidden role used by all applications. The Shadow Agent group
has ALL permissions. Programs push the context to a member of this group,
the User Agent person, when the program requires access not granted to
most users. For example, in order to ensure that Configurable Product
objects are created using the Create Product wizard, and not the Object/New/Original
dialogs, create access is only allowed by the Shadow Agent group. |
Shipping Department |
Used in ENOVIA Variant Configuration Central. People
responsible for shipping ordered items to customers and promoting sales
orders to the Shipped state. |
Software Change Board |
Used inENOVIA Product Line Management and ENOVIA Variant Configuration Central. People who assess and assign everything involved in the
development of a software product, including specifications, incidents,
features, impact analyses, etc. All Change Boards are part of this group,
including the Change Control Board (CCB). |
Software Engineering |
Used in ENOVIA Product Line Management and ENOVIA Variant Configuration Central. People who write code for the software, perform impact
analyses, and write functional specifications. |
Software Quality Engineering |
Used in Product Line component and ENOVIA Variant Configuration Centrall. People who are involved with the entire quality development
process of the software. |
Software Release Engineering |
Used in ENOVIA Variant Configuration Central. People
responsible for software components, software library, and the integrity
of sequencing the configuration management environment. These people
also create/oversee the development/test of runtime environments and
support both the development and QA environment. They manage the release
of new versions of software to customers. They build release and packing
tools, and develop release policy in conjunction with Quality Assurance,
Development and Program Management. |