First hour — Mapper

A 60-minute quick start. You'll sign in, tour the key pages, and configure one production site to anchor the rest of your setup work.

What you need before you start

• An account with the Mapper role.
• Access to the browser-based web portal.
• Access to the mobile app for NFC tag writing (optional this hour).
• Rough knowledge of the physical plant: sites, lines, assets.

0–10 min — Sign in and orient

1. Open https://portal.<your-installation>.sm-tm.app.
2. Sign in.
3. Note the sidebar sections: Main (Dashboard / Mapping / NFC Tags / Remarks / Products & Tools), Task Planning, Feedback Management, Report, Configuration.
4. Click Mapping — you land on the Web Mapping page with production-site cards. This is your home base.

Detail: Navigating the portal.

10–25 min — Decide your naming convention

Before you create anything, decide how you'll name nodes. You only get this right once per installation.

• Production Sites — short, stable. "Bandung Plant", "Medan Plant". Not "Main Factory" (ambiguous).
• Lines — numbered or sequenced. "Weaving Line 03" beats "Line Three". Pad with zeros.
• Sections — zone-based: "Operator side", "Drive side", "Section A".
• Assets — equipment tag or serial: "Loom L-314". Not "that pump near the door".
• Task Points — specific location: "Main bearing grease point", not "grease point".

Write the rules down. You'll thank yourself when you have 500 assets.

25–45 min — Create your first production site end-to-end

Do the whole tree for one pilot site. This validates your convention before you scale.

1. Mapping → Add Production Site. Name it, save.
2. Open the site → Add Line. Name it, save.
3. Open the line → optionally Add Section.
4. Open the section (or line) → Add Asset. If a matching component exists in Components, link it; the component's default tasks come with the asset.
5. Open the asset → Add Task Point for each inspection / lubrication point.
6. Optionally write an NFC tag to each task point using the mobile app.

Detail: Mapping · Writing NFC tags.

45–55 min — Check the supporting data

Your hierarchy plugs into existing reference data. Confirm these are set up:

• Components — the reusable equipment types your assets link to.
• Asset Setup → Units — the measurement units your tasks will use (°C, bar, l, etc.).
• Asset Setup → Thresholds — min/max ranges for numeric fields.
• Safety Standards — the acknowledgement checklists that gate risky tasks.

If any of these are empty or wrong, talk to the Admin — they typically set these up first, but mappers often end up owning the content.

55–60 min — Plan your next sessions

A mapper's job is multi-week, not one-hour. Set realistic expectations:

• Week 1: pilot one site (what you just did). Get feedback from a technician.
• Weeks 2–4: scale to other sites. Import via CSV where possible — see Mapping › Bulk import.
• Month 2+: iterate on task definitions as technicians report friction.

Bookmark the Mapper handbook for reference.

Top 3 mapper pitfalls

1. Building the whole plant before testing. Pilot one site; get feedback; then scale.
2. Inconsistent naming. Decide the convention first, stick to it, resist drift.
3. Safety procedures too generic. "Check safety" is theatre. Specific steps are safety.

Welcome.