Introduction
The account hierarchy is used to display machines and their data for a specific entity within the hierarchy.
The account hierarchy is the structure we built initially in the Augury system to organize the different assets of an organization, in a way that best reflects that organization and its needs. It was based on a specific set of business needs that no longer represent the majority of our use cases. In addition, once a hierarchy was set up, it was impossible to change.
Consequently, our users needed to find creative solutions that often differ within an organization. This led to inconsistencies in terminology that prevented alignment with other business systems and complexity for users.
Augury’s goal is to better represent the customer’s physical assets. The company and site remain because they represent physical assets, whereas the region and branch have been removed because they are more conceptual and don’t always refer to a physical entity.
The new flexible company structure
Augury has flattened the structure and removed regions, facilities, and branches. The change helps companies organize their data in a way that better follows their organization. It also allows for flexibility if the structure needs revising.
To enable this flattened structure, Augury has taken all the previous regions, facilities and branches and created groups. From now on, under company structure the customer will only see Company, sites, and buildings, and under them the custom groups that were created under that company.
Groups provide a more agile flexible structure in the platform. It is easy to create, edit, and delete them, as well as assign and remove them at any time. They simplify navigation, asset management, and visibility.
Groups can be created at any time, and any asset can be grouped based on its needs. The new structure is more flexible, which solves the problem of rigidity in the previous structure.
New groups are manually created by Augury.
The migration process
As mentioned above, we have taken all the previous regions, facilities, and branches and created groups. From now on, under Company structure you’ll only see Company, sites, and buildings, and under them the custom groups that were created under that company. Note that all facilities will be automatically renamed to “site”.
Augury will work closely with you to make sure we’re consolidating the groups correctly.
Any re-organization of groups after the migration will be done by Augury together with you, the customer.
Effect on user permissions
The flexible company structure also affects how user roles are assigned.
Previously, a user was assigned to a specific part of the fixed hierarchy, a facility for example, and could only access information specific to that facility.
Now, user roles are at the company level, so that permissions can be assigned wherever needed within the company, but only where needed.
For more information, read the User Management article.
Effect on navigation and selection
User roles are now directly linked to the company level so you can easily assign users to the relevant structure or group, and not just be limited to a structure. From now on, customers can assign a user to multiple structures according to the job they perform.
Whether you’re focused on a machine’s health, and IoT device status, or another area of the platform, you can quickly filter and organize data across facilities to suit your needs.
For more information, read the How to Work With Multi-Selector Navigation article.

