All Collections
Manage Locations
Locations vs. Parent Assets
Locations vs. Parent Assets

Should You Make a New Location or Parent Asset? Here's What to Know

Rachel Link avatar
Written by Rachel Link
Updated over a week ago

Overview

We often get asked the difference between locations and parent assets, and when to use each.

This article provides helpful tips to determine if you should create a new location or a parent asset.

Table of Contents

Locations vs. Parent Assets

Locations are used to limit user access.

In order for a user to perform work in Limble, they need to be assigned a role. Roles are location-based, so a user can only perform work at a location where they are assigned a role. This is how locations divide responsibilities and limit user access.

Parent assets are used to organize assets.

Parent assets are used within an asset hierarchy. An asset hierarchy is a group of assets organized with a parent asset at the top and child assets beneath; kind of like a family tree.

Much like a family tree, parent assets can have child assets, and child assets can also be parent assets; so you can create multiple parent-child relationships within an asset hierarchy to be as broad or detailed as you need.

Parent assets do not limit users from being able to perform work on your assets.

If you’re still not sure whether to create a new location or a parent asset, ask yourself some of these questions:

  • Do I need to limit access so only a specific set of users can perform work on a group of assets? If the answer is “yes,” then you should create a new location.

  • Do I need a unique work request portal for this group of assets? If the answer is “yes,” then you should create a new location.

  • Do I want to organize my assets in Limble by building or floor and allow everyone on my team access to those places? If the answer is “yes,” then those buildings or floors should be created as parent assets, not as new locations.

Remember: locations divide user access; parent assets organize your equipment.

Example: Big L Manufacturing

Here's an example of how locations and parent assets function in Limble.

Big L Manufacturing has two plants: one in Colorado, and one in Wyoming. Robert is a technician at the Colorado plant, while David is a technician at the Wyoming plant.

Both the Colorado and Wyoming plants have a Building 1 and Building 2.

Each building has an HVAC unit and a security system.

In Colorado, Robert needs access to both buildings and all of the equipment in the buildings.

David needs access to both buildings and the equipment at the Wyoming plant.

Even though Building 1 and Building 2 may be separate physical locations in real life, the technicians are responsible for maintaining the equipment in both buildings at their respective plants.

To give both technicians the access they need, we would take the following steps:

  1. Create two locations, "Colorado Plant" and "Wyoming Plant."

  2. Assign Robert the Technician role at "Colorado Plant, and David the Technician role at "Wyoming Plant."

  3. At each plant, create "Building 1" and "Building 2" as parent assets.

  4. Then, create the HVAC units and security systems as child assets at each building.

Now, each technician will have the access they need (creating locations) while the equipment is neatly organized (using parent assets.)

Watch the Video Tutorial

Skip ahead to chapter 2 of this video to hear more about locations vs. parent assets!

Related Articles

Still don’t see what you’re looking for? Check out our YouTube channel for more tips and tricks! You can also reach out to us anytime at support@limblecmms.com.

Did this answer your question?