Tier Structures Use Cases

Use Case 1

• Let's assume that I run a staffing company and I would like a nice structured way to maintain all personal data that I have on each of my staff members, as well as being able to list whom their bosses are as well as their personal details.

  Here the Tier Structures Module can be very useful as it can give a very clear organisational structure overview. I would thus configure my profile to start with Tier 1 being mangers, I will give them label,value pairs along the lines of First Name, Last Name and Cell Number.

  I will then create another tier, Tier 2 that will contain all of the waiters, each one of these waiters will also contain label,value pairs that are the same as the managers, ie First Name, Last Name and Cell Number.

  That way I now have all personal details of the individuals stored for me (so that I can reference it later) and I have the different levels that my staff members are on.

Use Case 2

• Let's assume that I run a transport company and I want to create a structure that will ensure that I know which regions/provinces certain buses are in, which routes they are on and some other relevant information.

  Here the Tier Structures Module would work extremely well. I would configure the profile so that on Tier 1 we would have the different areas that my company covers, I would add in the label,value pairs, the Area Manager, Area Code and Staff Number - Area specific.

  I would then create a Tier 2 that would contain each and every route according to the area that they are a part of, in the label,value pairs I would put in Route distance, Avg number of Customers and Avg Route Time.

  I would then create a Tier 3 in which I would have all of the bus IDs, in the label,value pairs I would store Driver ID, Bus ID and Registration Number. Once I have configured all of that, I will have a very simple way to access any and all areas, routes and buses within one structure that I can call upon.

Use Case 3

• Let's assume that I run a firm that handles invoices and receipts. I could use a Tier Structures profile to add different tiers to my organisation to help add structure.

  I would configure the profile so that Tier 1 would be customers, in label,value pairs I would add Customer Name, Customer ID and Customer Email.

  I would then configure Tier 2 to Invoices and Receipts (these two are both on the same level, one is not higher than the other, however customers are higher than both), in the label,value pairs I would add Invoice ID, Invoice Amount and Invoice For (for Invoices) as well as Receipt ID, Receipt Amount and Receipt For (for Receipts).

  Once I have configured all of that, I have a very easy view of all of my customers as well as what receipts and invoices they have linked to them.

👍

Food for thought

These use cases/examples are here to show you how the Tier Structures Module can be used within real world scenarios as well as to explain the different elements that exist within the Module.