Create and edit hierarchy¶
Build asset hierarchies on the mobile app — typically during on-site mapping sessions where having the equipment in front of you helps you model it accurately.
Required role
Mapper.
Overview¶
The web portal is the comfortable place to build a hierarchy at a desk with a CSV import in hand. The mobile app is for the other half of mapping: on-site, standing next to the equipment, with a phone to write NFC tags immediately, and a camera to capture reference photos as you go.
The same five-level model applies: Production Site → Line → Section → Asset → Task Point. Anything you create on mobile appears on the web portal after the next sync.
When to use mobile vs web¶
| Situation | App |
|---|---|
| Entering 200 assets from an existing spreadsheet | Web (CSV import) |
| Walking a new production line and modelling it as you go | Mobile |
| Creating a task point and writing its NFC tag in one motion | Mobile (web can't write tags) |
| Bulk rename or reorder | Web |
| Taking reference photos during mapping | Mobile (camera in-app) |
| Inviting a new technician | Web (user management isn't available on mobile) |
Prerequisites¶
- You have the Mapper role.
- You're physically at the site (optional but the whole point of mobile mapping).
- Enough blank NFC tags in your pocket for the task points you plan to create today (if tagging).
Open the hierarchy for editing¶
Menu → Hierarchy. See Browsing the hierarchy for navigation basics.
To add to the tree:
- Tap the + button visible at each level.
- Or open a parent node and tap Add child in its detail screen.
Create a Production Site¶
- From the top of the hierarchy, tap + New site.
- Fill in:
- Name — short, unique.
- Timezone — often pre-populates to your company default.
- Address — optional.
- Save.
Sites are usually created once at installation time. You rarely create new ones after that.
Create a Line¶
- Open a Production Site.
- Tap + New line.
- Fill in name and order.
- Save.
Create a Section¶
- Open a Line.
- Tap + New section.
- Fill in name.
- Save.
Sections are optional. If a line is simple, skip straight to creating Assets under the Line.
Create an Asset¶
- Open a Section (or Line).
- Tap + New asset.
- Fill in:
- Name — asset code or equipment tag.
- Component type — link to the existing component catalogue. This brings the component's default tasks onto the new asset. See Components (web portal).
- Photo — optional; take a reference shot on the spot.
- Save.
Create a Task Point¶
- Open an Asset.
- Tap + New task point.
- Fill in:
- Name — specific ("Main bearing grease point" not "grease point").
- Description — optional, useful for odd-location points.
- Position indicator — optional ("north side", "lower drive shaft").
- Photo — optional reference photo.
- Save.
Write a tag immediately¶
After saving a task point, the app offers Write NFC tag as the next action. If you have a blank tag on you:
- Tap Write NFC tag.
- Hold the blank tag against the phone.
- Confirm the write.
- Physically apply the tag.
- Test-scan.
See Writing NFC tags.
Edit an existing node¶
- Open the node.
- Tap the edit (pencil) icon.
- Change what you need to.
- Save.
Edits propagate to everyone on the next sync.
Delete a node¶
- Open the node.
- Three-dot menu → Delete.
- The app warns you about children and dependencies (tasks, NFC tags).
- Confirm.
Deletion cascades
Deleting a parent deletes all its children. Use sparingly. Deactivation (via the web portal) is usually safer.
Reorder¶
- Open the parent.
- Enter reorder mode via the three-dot menu → Reorder.
- Drag children up or down.
- Save.
Order affects the display order on all apps.
Offline creation¶
All of this works offline:
- Create, edit, reorder, delete.
- Changes queue in the outbox.
- Upload automatically on next sync.
Written NFC tags also work offline — the tag is physically written, and the registration syncs later.
If two mappers are editing the same hierarchy offline and submit conflicting changes, server-side conflict resolution applies (server wins for the same node; non-conflicting additions from both users all apply).
Common mapping patterns¶
Greenfield line¶
- Create the Line.
- Create its Sections (if any).
- Walk down the line. At each asset:
- Create the Asset with component type linked.
- Create each Task Point.
- Write the NFC tag for each Task Point.
- Take reference photos.
- Back at the desk, review on the web portal. Tidy anything that didn't translate well.
Brownfield cleanup¶
- Walk the plant with the existing hierarchy open in the Browser.
- Where an asset doesn't exist in the system but exists in reality, create it from mobile.
- Where the system has something that no longer exists physically, make a note to deactivate it on the web portal later.
- Reconcile on the web portal after the walk.
Adding a single task point¶
- Menu → Hierarchy → drill to the asset.
- Tap + New task point.
- Fill in, save, write tag.
Total: under a minute.
What you can't do on mobile¶
- CSV import / export — web portal only.
- Webmapping visual editor — web portal only.
- User management — web portal only.
- Master data editing — web portal only (but you can reference it here).
Things to watch for¶
Name consistently
The convention you picked at the start of mapping should be followed in the field. Sporadic divergence ("Line-01" vs "Line 1" vs "Line One") makes search hurt later.
Take photos even if you think you won't need them
Storage is cheap; re-visits are expensive. One reference photo per asset when you map it saves many trips later.
Creating hierarchy doesn't trigger schedules
A new task point with a component-inherited task doesn't auto-schedule. Scheduling happens separately on the web portal. See Scheduling (web portal).
Troubleshooting¶
| Problem | Fix |
|---|---|
| + button is missing | You're not signed in as a Mapper |
| Component type dropdown is empty | Components haven't been created yet; do so on the web portal |
| NFC write fails right after creating the task point | Hold longer; try a fresh tag; see NFC is not working |
| New asset not showing to technicians | Force sync on their device, or wait for the next cycle |
Related topics¶
- Asset hierarchy (web portal) — same data on the web side.
- Browsing the hierarchy — navigation.
- Writing NFC tags — the natural follow-up to creating a task point.
- Components (web portal) — the catalogue that task points reference.
- Mapper handbook