Aliquot’s layered hierarchy is designed to give users flexibility in managing customer accounts. Whether you're setting up a single location or a complex organization with multiple sites, this structure helps administrators:
Customize account setups
Filter reports by location
Control user access to specific data
Navigating to Site Management:
Hover over "Site Management"
Click on the level of access or layer you want to view or manage
You can also filter the organization to narrow down the view based on your current needs.
Hierarchy Structure:
Aliquot allows users to filter the organization at any level of the hierarchy. This is especially useful for narrowing down data views and managing access.
How filtering works:
When you filter by a high-level entity (like a Customer), you will see everything beneath that level, including all associated Facilities, Buildings, and Systems.
This ensures that users can focus on relevant data without needing to manually go through each layer.
Example:
If you filter by a Customer, you'll automatically see:
All Facilities under that customer
All Buildings within those Facilites
All Systems and their associated test data
1. Client
1. Client
The Client layer is where you can manage your organization, or different divisions of your organization.
Best Practice: We suggest only having one client if the organization does not contain multiple divisions that require different configurations within the software.
Note: Any user that is not a 'Global User' will only see their assigned Client in the organization. Under "My Organization" Client Users will not have permission to edit the Client layer.
2. Customer
2. Customer
The customer layer can be populated by a specific customer name or a specific region of a customer. The address and phone would be best listed as the headquarters of your customer. There are toggles to label a customer as a prospect and options to specify if the customer is active or not.
Best Practice: Going forward, it is important to consider your management policy for creating new customers. Doing so can help ensure that your process keeps duplicate customers from being created (e.g., Having customer additions go through multiple stages of approval before the addition is finalized).
3. Facility
3. Facility
The Facility layer allows specification of the individual location of a customer's buildings and systems. In this layer, details like address, contact info, and even units of measurement can be specified.
Example: A comparison for the facility layer can be made to a company like Hilton Hotels. Their company operates on a large scale and in many different regions (e.g., Philadelphia Hilton, NYC Hilton). The facilities layer can be used to categorize these regions into individual locations.
4. Building
4. Building
The building layer can be used to categorize and segment different operating addresses based upon a specific city or geographic location.
Example: Given the previous example, if Philadelphia Hilton were selected as the facility, that region's different operating locations would populate the building layer.
5. System
5. System
The System layer is each of the areas within a building that require testing. Reports all reside at the system layer and can be broken down by competent. This layer is also where all test data is stored for reports.
Example: A cooling system has multiple components (raw water, chill loop, cooling tower, etc.) The system layer allows configuration of reports to show components and their associated tests without unnecessary data being pulled from other systems.