Skip to content

Mapper handbook

Everything a mapper needs to know to build and maintain the data model that powers Smart Maintenance Task Manager.

This handbook is for the Mapper role

If you're not sure what role you have, open your profile in the web portal (avatar → Profile) or ask your Admin.

What you'll do with the platform

As a mapper, you're the authoring layer of the whole platform. Every asset that gets inspected, every task that gets executed, and every NFC tag that a technician scans — you put those in place first. Nothing else works until the hierarchy and tasks are defined.

Your main responsibilities:

  • Build the asset hierarchy — Production Sites, Lines, Sections, Assets, Task Points.
  • Define tasks and link them to the right task points.
  • Write NFC tags on physical equipment so technicians can scan them.
  • Configure components (pumps, motors, drills) and their options (units, thresholds, text types).
  • Maintain safety procedures — the acknowledgement steps that gate certain tasks.
  • Maintain master data — units, products, tools that your tasks reference.
  • Manage users inside your company (this is often shared with Admins).

Your primary app

Mappers split their time between two apps:

App When you use it
Web portal Bulk editing, CSV imports, long editing sessions at a desk, reviewing structures across the whole site.
Mobile app Any time you need to write NFC tags (mobile-only), on-site edits where having the equipment in front of you helps, adding photos while you're at the asset.

The asset hierarchy (the mental model)

The entire platform hangs off a five-level tree:

Production Site
 └─ Line
     └─ Section
         └─ Asset
             └─ Task Point

Every task is attached to a Task Point. Every NFC tag points to a Task Point. Every scheduled inspection operates on a Task Point. If you don't model the task point, none of it happens.

Rules of thumb:

  • A Production Site is a physical building, factory, or plant.
  • A Line is a production line inside the site — the natural split when work is organised by product flow.
  • A Section is a subdivision within a line (drive side, motor side, left bank, right bank). Use sections when one line has obviously distinct zones.
  • An Asset is a piece of equipment: pump P-302, motor M-14, compressor C-1.
  • A Task Point is the specific spot on the asset where work happens: grease point 3, bearing housing, temperature probe. One asset typically has many task points.

Plan the tree before you build it. It's much harder to restructure later than to get it right the first time.

Your first week as mapper

1. Learn the plant before you touch the system

Walk the site. Make notes. Take photos. Ask the maintenance team how they already think about their equipment — if they've been working there for years, their mental model is probably close to what the platform should reflect.

2. Decide the naming convention

Pick a convention and stick to it:

  • Consistent — Line 01, Line 02 (not Line 1, Line Two, Production Line B).
  • Short — names appear on mobile screens where space is tight.
  • Searchable — unique enough that search narrows quickly.

Renaming later is cheap but re-training your team isn't.

3. Build one Production Site end-to-end

Pick one site and model it completely — site, all its lines, a representative sample of sections, assets, task points. Get feedback from a supervisor and a technician. Adjust. Then copy the pattern to the other sites.

4. Write the first ten NFC tags

Put real tags on real equipment. Have a technician test-scan. Adjust tag placement (NFC antennas don't love metal — sometimes you need a plastic spacer) and confirm the right asset opens.

5. Seed safety procedures and master data

Pull your existing safety standards. Create procedures for the classes of work your technicians do. Seed the units and products you've already standardised on.

6. Open the first tasks to real work

Hand off to a supervisor, who assigns them to technicians. Watch what happens. Iterate.

Building the asset hierarchy

See Asset hierarchy (web portal) for the step-by-step. The quick summary:

  1. Mapping in the sidebar.
  2. Create a Production Site → open it → create Lines → open each → create Sections → Assets → Task Points.
  3. Bulk-import with CSV if you already have an asset register elsewhere.
  4. Drag to reorder.
  1. Open Hierarchy from the menu.
  2. Tap the + button at the level you're at.
  3. Fill in the form. Save.
  4. For task points, optionally write an NFC tag immediately after saving.

Creating tasks

A task is a definition of work to perform at a task point. Tasks are typed (lubrication / maintenance / electrical / production / repair) — see Task types.

To create a task:

  1. Navigate to the task point in the hierarchy.
  2. Click Add task.
  3. Pick the task type.
  4. Configure the form fields the technician will see — numeric fields, dropdowns, photo requirements, thresholds.
  5. (Optional) Link a safety procedure.
  6. (Optional) Attach a recurring schedule.
  7. Save.

You can define a task once and let the schedule generate instances automatically. You don't create a new task every day — you create it once and let the platform multiply it over time.

Reusing tasks across similar assets

If a section has twenty similar pumps that all need the same weekly lubrication:

  • Don't create twenty separate tasks by hand.
  • Use the Apply to siblings option after creating the first task, or duplicate via CSV import.

Writing NFC tags

NFC is the fastest way for a technician to open the right task point. The workflow:

  1. In the mobile app, open the task point you want to link.
  2. Tap Write NFC tag.
  3. Hold a blank NFC tag against the phone's NFC antenna.
  4. The app writes NFC_TASKPOINT_<id> to the tag.
  5. Physically apply the tag to the asset.
  6. Test-scan to verify.

Which tags to buy

NTAG213 or better. Durable enclosed versions for industrial environments — plain stickers don't survive grease, steam, or wash-down.

NFC on metal

Metal surfaces detune NFC antennas. Use tags labelled "NFC on-metal" for equipment with ferrous housings, or attach a ~2mm plastic spacer between tag and metal.

For more, see Writing NFC tags.

Components

A component is a reusable equipment-type definition: "centrifugal pump", "vertical mill spindle", "V-belt drive". You define the component once (with its options: unit, type, text_type), then link assets to it. Tasks attach to components so that when you create an asset from that component, the task set comes with it.

Use components when:

  • Several assets share the same maintenance profile (one definition applies to many assets).
  • You want to standardise task fields across similar equipment.

Components live in Components → Tree on the web portal. See Components (web portal).

Safety procedures

Any task that has safety implications should have a safety procedure attached. When the technician starts the task, the procedure blocks the form until each measure is acknowledged.

A good safety procedure:

  • Has numbered, specific steps ("Verify lock-out tag on main disconnect", not "Check electrical is safe").
  • Is short enough to actually read (3–8 measures, not 40).
  • Uses consistent verbs ("Verify", "Confirm", "Don") so acknowledgements feel distinct.

See Safety procedures (web portal).

Master data

The tables your tasks reference:

  • Units — measurement units (bar, psi, °C, litres, hours) and their conversion factors.
  • Products — lubrication and consumable products your team uses.
  • Tools — the tool registry (wrench sizes, special fixtures).
  • Thresholds — min/max acceptable values (pump discharge pressure, bearing temperature).
  • Repair request types — the dropdown of failure categories.
  • Shutdown reasons — the dropdown of shutdown causes.

Admins have permission to edit these, but as mapper you often own them in practice. See Master data (web portal).

What you can do that other roles can't

  • Create / edit / delete anything in the hierarchy.
  • Create / edit / delete tasks, components, schedules, safety procedures.
  • Write NFC tags (mobile app only).
  • Create hierarchy from the mobile app (supervisors and admins can view but not create on mobile).

For a full matrix, see Permissions matrix.

What you can't do

  • Approve or reject completed tasks (that's Supervisor / Admin).
  • Change company-wide settings (Admin only).
  • Manage companies or switch tenants (PegotecUser only).

Day-to-day rhythm

A mature mapper mostly maintains, not builds. A typical week:

  • Respond to requests for new task points or tasks (when production adds equipment).
  • Rename / reorganise as the plant's structure evolves.
  • Replace damaged NFC tags.
  • Adjust thresholds based on historical measurement data.
  • Review the NFC skip report — high skip counts often mean a tag needs repositioning.
  • Coordinate with supervisors on scheduling changes.

Troubleshooting

Common issues and where to fix them:

Problem See
NFC tag scans but no task point opens Check the tag was written correctly — NFC is not working
Deleted an asset but tasks still show Orphaned tasks linger briefly — refresh, or check the audit log
CSV import fails Check headers match exactly, UTF-8 encoding — File formats
Can't sign in I can't log in