Overview
Component types can share the same name as long as each has a unique description. This lets your organization use consistent naming conventions across similar component types while still telling them apart by what they describe.
Accessing Component Types
From the navigation, click Settings.
Under Lubrication Routes, click Component Types.
From here you can create, edit, or review component types.
Creating a Component Type with a Duplicate Name
In Settings > Lubrication Routes > Component Types, click Add Component Type (or the equivalent create button).
Enter a Name. If this name is already used by another component type, you must enter a Description that differs from the description on the existing component type with the same name.
Enter a Description that is distinct from any existing component type with the same name.
Save the component type.
If you attempt to save a component type where the name + description combination already exists, you will see a validation error.
Use Cases
Standardized naming across asset categories — A maintenance team uses the component type name "Bearing" across multiple asset classes (motors, pumps, gearboxes). Each can now have its own "Bearing" component type with a distinct description (e.g., "Motor bearing", "Pump bearing", "Gearbox bearing") without needing to use workaround names like "Bearing - Motor."
Shared naming conventions by region or site — Organizations with multiple sites can use the same component type names at each site, differentiated by description, rather than prefixing every name with a site code.
Best Practices
Always add a description when the name is shared. Even though a description is not required, omitting it on a component type with a common name makes it indistinguishable from similarly named types in dropdowns and reports.
Keep descriptions concise and specific. The description should immediately clarify what differentiates this component type from others with the same name — avoid vague descriptions like "Other" or "Misc."
Audit existing component types before adding duplicates. Review your current list to ensure the name + description pair you intend to create does not already exist.
Troubleshooting
Issue: I receive a validation error when saving a component type, even though the name is different from others.
Solution:
The validation now checks the name + description combination, not the name alone.
Check whether another component type already exists with the exact same name and description.
Change the description to make the pair unique, then save again.
Issue: I cannot save a component type with no description, and a component type with the same name already exists.
Solution:
If a component type with the same name and no description already exists, you cannot create a second one with the same name and no description — the blank description counts as part of the pair.
Add a description to differentiate the new component type, or use a different name.
Summary
Component types don't need unique names — the name and description together must be unique. You can use the same name across similar component types and differentiate them by description. When doing so, make sure each description is specific enough to tell them apart.