Organizational Structures

Note:The Organizational Structures section (under the Reporting tab) is displayed only if Flexera Analytics Flexera Analytics (Cognos) has been installed and configured. The user must also have a role with the View Org Structures or View and Manage Org Structures permission.

FlexNet Manager for Engineering Applications supports the creation of organizational structures. Organizational structures enable grouping and sub-grouping of users, projects, and license server hosts in hierarchical order. Organizational structures act as a “rule set” for how to distribute license usage across various areas of your enterprise. You can use organizational structures in reporting, and for license distribution (if you use Investment Planning functionality). See Contract Pools for more information about license distribution.

For example, you can create organizational structures for all of the users in your organization, based on the departments to which they belong. You can create another organizational structure based on the geographical location to which users belong. Both organizational structures can exist in the FlexNet Manager for Engineering Applications system at one time and you can generate reports for either group or for subgroups of these two organizational structures.

Organization structures are made up of nodes that are arranged in a tree structure. There is a single root node at the top of each organizational structure. Leaf nodes (nodes that have no child nodes) for each organizational structure are defined by the type of the structure—for example, each leaf node of a User ID organizational structure corresponds to a user ID. The nodes between the root node and the leaf nodes are known as intermediate nodes. There can be an arbitrary number of intermediate levels in each organizational structure, and multiple intermediate nodes can have the same name, as long as they have different parent nodes. (For example, there could be Engineering nodes beneath each of the Japan, Australia, and Germany nodes.) A leaf-level node could have an intermediate parent node of any level. A leaf node cannot have another leaf-level node as a parent. A leaf-level node cannot have more than one parent node on the same date. Leaf nodes on the same level must be unique. (For example, there cannot be two Smith leaf nodes beneath Germany’s Engineering node.)

You can define user–, project– or host-based organizational structures using the Add Organizational Structure page, or you can define the organizational structures in an XML file and import the file. After creating an organizational structure, you can import organizational-structure data from an LDAP domain.

To view a list of your enterprise’s organizational structures, use the Organizational Structures page.