Overview
Every Asset in Mobaro has a fixed set of fields that capture the data your team needs to find, identify, and manage equipment over time. This article is the reference for what each field is for, when to use which, and how to request additions to the Mobaro-managed lookup lists for Manufacturer, Model, and Category.
Why this matters: Filling in the right fields, consistently, makes the rest of Mobaro work better. Reports filter on these values; the App displays them; integrations sync from them. Empty or inconsistent fields turn into operational friction — Users searching for an Asset by serial number that wasn't entered, or reports that can't group by Manufacturer because the field was skipped.
Required access: To create or edit Assets and their fields, you must be a Super User or hold a Role with the Locations: Modify permission.
Asset field reference
Every Asset shares the same schema. Only Name is required; everything else is optional but recommended where applicable.
Field | Purpose and notes |
Name (required) | Primary identifier, shown throughout the Mobaro Backend, App, and reports. Free text; Mobaro does not enforce name uniqueness. |
Short name | An alternate, condensed display name. Users of the Mobaro App can toggle between showing the Name or the Short name. Useful when full Asset names are too long to read comfortably on a phone screen. |
Description | Free-text notes about the Asset (model details, version numbers, install date, anything that helps the next person who opens the record). Supports basic formatting — bold, italic, underline, strikethrough, and lists. |
External ID | Your organization's stable identifier from an upstream system (CMMS, asset register, etc.). Use it as the anchor for API sync workflows so you can match Mobaro records to the source of truth. |
Serial | The manufacturer-issued serial number for the physical unit. Free text. Useful for warranty lookups and component tracking when units are swapped. |
Code | An internal asset code that your organization assigns. Free text. Often used for internal naming schemes such as a fleet code or maintenance number. |
Custom Scanner Code | A custom string that generates a scannable QR code in the Asset detail view. Useful for placing physical labels on equipment so operators can scan their phones to open the right Asset. |
Manufacturer | The Asset's manufacturer (e.g., Allen Bradley, Vekoma). Selected from a Mobaro-controlled list — request additions through your CSM or support. |
Model | The specific Model of the Asset. Selected from a Mobaro-controlled list, scoped to a chosen Manufacturer. Requesting a new Model requires telling Mobaro which Manufacturer it belongs to. |
Category | A high-level grouping for the Asset (e.g., a class of equipment). Selected from a Mobaro-controlled list — request additions through your CSM or support. |
Mobaro-controlled fields: Manufacturer, Model, Category
Three of the Asset fields — Manufacturer, Model, and Category — pick from lists that Mobaro maintains centrally rather than letting each organization manage its own values. This keeps the data consistent across customers and protects the integrity of cross-organization reporting, integrations, and any future industry benchmarking.
Heads up: If your organization needs a Manufacturer, Model, or Category that isn't currently in the list, the values are not self-service. To request an addition, reach out to:
Your Customer Success Manager, or
Mobaro will add the value to the global list, after which you can edit your Assets to use the new value.
A note on requesting Models
Models are scoped to a Manufacturer — every Model in the global list belongs to exactly one Manufacturer. When you request a new Model, include the Manufacturer it should be associated with so Mobaro can add it under the right parent. If the Manufacturer isn't in the list yet either, request both at the same time.
Best practice: Before submitting a request, double-check the existing list. Manufacturers are sometimes listed under a parent or corporate brand rather than a sub-brand, so the value you need may already be there under a slightly different name.
Best practices for filling in fields
Pick a naming convention and stick with it
Apply a consistent naming convention for Assets across your organization. A few patterns that scale:
Position-based:
MCC1,MCC2,OCC1— short, scannable, useful when position is meaningful.Function-based:
Drive Motor 1,Brake Module B— readable, useful when there's no fixed numbering.Prefixed by system:
EL-MCC1,EL-Drive Motor 1— useful when you want to filter or search by system without relying on the parent/child hierarchy.
Use External IDs from day one
If your Assets exist in any other system (a CMMS, a maintenance database, a fleet register), copy the upstream identifier into the External ID field. This makes API sync vastly simpler and protects against duplicates if a future re-import happens. See Bulk imports and API access for Assets.
Set a Short name when the Name is long
If the Name runs more than ~15 characters, populate the Short name. App Users will see the shorter version on small screens, while reports and the backend continue to show the full Name.
Capture Serial numbers when they exist
Serial numbers tie a Mobaro Asset to a physical piece of equipment, which matters when components are swapped or warranty claims need to reference the unit that failed. Don't skip this field for major Assets even if it's tedious to gather upfront.
Use Custom Scanner Codes for high-traffic Assets
For Assets that operators interact with frequently — control panels, ride entry signs, queue gates — populate the Custom Scanner Code and print the generated QR code on a label at the equipment. Scanning takes the operator straight to the Asset's record without searching.
Anti-patterns to avoid
Watch out for these habits, which create downstream pain:
Stuffing structured data into the Description field — if a value belongs in Serial, External ID, Code, or Manufacturer, put it there. Description is for narrative notes, not for fields you'll later want to filter or sync on.
Inventing your own values for Manufacturer, Model, or Category — these are Mobaro-controlled lists. Putting "see description" or "TBD" in those slots breaks reporting; leave them blank and request the missing value instead.
Skipping External ID on Assets that exist upstream — every future sync becomes a manual reconciliation exercise. Populate it once at creation and you'll thank yourself later.
Inconsistent capitalization or naming across Assets — "MCC 1" vs "MCC1" vs "Mcc1" all read the same to a human but are distinct strings to a search filter or report.
See also
Creating an Asset — the create flow.
Linking Assets to Locations — how the Location field on each Asset works.
Asset hierarchies and parent/child relationships — for how Parent and Children relationships sit alongside the schema fields covered here.
Asset history and audit trail — for tracking changes to these fields over time.
Bulk imports and API access for Assets — for setting these fields programmatically.
Frequently asked questions
Q: Can I add my own custom fields to an Asset?
A: Not currently. The Asset schema is fixed at the fields documented above. If you have data that doesn't fit any existing field, the most flexible options are the Description (for narrative notes) and the External ID (for upstream identifiers). For other use cases, talk to your CSM about how to model the requirement.
Q: How do I add a new Manufacturer or Model to the dropdown?
A: Manufacturer, Model, and Category are Mobaro-controlled lists. To add a value, contact your CSM or [email protected]. For Models specifically, include the Manufacturer the Model belongs to, since Models are scoped to a Manufacturer.
Q: Why are Manufacturer, Model, and Category controlled by Mobaro?
A: Centralized lists keep the values consistent across customers, which preserves the integrity of cross-organization reporting and integrations. If every customer added their own variants of "Allen Bradley," the data would fragment quickly.
Q: What's the difference between Code and External ID?
A: Code is an internal Mobaro field — typically a fleet or maintenance code your team uses inside the system. External ID is the identifier from an upstream system (CMMS, ERP, asset register) and is the right field to use for API sync. Both are free text, but their intent and usage differ.
Q: How does the Custom Scanner Code generate a QR?
A: When you populate the Custom Scanner Code field, Mobaro generates a QR code in the Asset detail view from that value. Print the QR on a physical label at the equipment, and operators can scan it from the Mobaro App to open the right Asset directly.
Q: Can I bulk-update fields for many Assets at once?
A: Through the API, yes. There is no UI bulk-edit for Asset fields today; bulk changes go through the API as one PUT per Asset. See Bulk imports and API access for Assets.
Q: Can two Assets share the same Code, Serial, or External ID?
A: Mobaro doesn't currently enforce uniqueness on these fields, so technically yes — but it's strongly discouraged, especially for External ID. Treating External ID as unique by convention is what makes API sync workflows reliable.