Mapper — quick reference¶
A one-page reference for hierarchy building and tag commissioning.
The five-level hierarchy¶
Tasks, NFC tags, schedules all attach at Task Point level.
Naming rules¶
- Consistent —
Line 01notLine 1/Line One. - Short — fits mobile screens.
- Searchable — unique enough that 3 characters narrow results.
Decide once. Stick to it. Resist drift.
Task types and when to use each¶
| Type | Use |
|---|---|
| Lubrication | Grease / oil application |
| Mechanical | Inspection, adjustment, cleaning (default for routine) |
| Electrical | Voltage / current / insulation checks |
| Production | Output / run-hour readings |
| Repair request | Resolving a reported fault |
Component vs asset¶
- Component-level tasks — one definition applies to every asset of that component type. Use when ≥3 similar assets exist.
- Asset-level tasks — one-off / outlier equipment only.
NFC tag workflow¶
- Open task point in mobile app.
- Write NFC tag → hold blank tag against phone.
- Apply physically to the asset.
- Test-scan. Move on.
Tag choice: NTAG213 minimum, enclosed / on-metal for ferrous surfaces. Budget ~$0.50 / tag.
Safety procedures¶
- 3–8 steps per procedure. Specific imperatives ("Verify LOTO on main disconnect").
- Attach only to tasks where risk justifies it.
- Co-author with your safety officer.
Master data checklist¶
Before executing real tasks, confirm these are populated:
- Units
- Thresholds (loose initially; tighten later)
- Products
- Tools
- Repair request types
- Shutdown reasons
Anti-patterns¶
- Building the whole plant before testing. Pilot one site; get feedback; then scale.
- Inconsistent naming. Decide first, stick.
- Generic safety ("check safety is OK"). Be specific or don't bother.
Print on A4 · Smart Maintenance Task Manager