User Guide

How to use PlantMaster Pro

Every section of the app, what it is for, and how your team uses it day to day. Written for the people on the floor, not for software people.

Getting started

PlantMaster Pro runs in a web browser. There is nothing to install and no app store download. Open app.hsbfix.org on a phone, tablet or computer and sign in.

Add it to the home screen. On Android Chrome, tap the three dots and choose Add to Home screen. It then opens like a normal app, full screen, with its own icon. Most plants do this on every technician's phone on day one.

The first person to sign up becomes the owner. The owner sets up the plant and invites everyone else. You need a working internet connection; if the signal drops for a moment while you are saving, the entry is held on the phone and sent when the connection returns.

Finding your way around

There are three ways to move around the app, and they all reach the same places.

At the top you will always see your company, your plant and your role, plus an Online indicator. Every screen has a search box that searches only the module you are currently in, and an + Add button to create a new record.

Every dropdown can also be typed into. If the list does not contain what you need — a designation, a category, a unit — just type it. You are never stuck waiting for someone to add an option for you.

Dashboard

Who uses it: everyone, every shift.

The home screen. It shows unread alerts at the top, then six quick tiles — Analytics, Scanner, Daily Logs, Condition Monitoring, Problem Solver and Reports — followed by cards for Assets, Work Orders, Checklists, Maintenance, Spares & Tools, Purchase Orders and Suppliers.

How to use it: start here at the beginning of a shift. Check the alert count, deal with anything urgent, then go to your module.

Assets

Who uses it: maintenance engineer, supervisor.

The register of every machine in the plant — the foundation of everything else. Work orders, maintenance plans, spare parts and manuals all attach to an asset, so it is worth setting up properly.

To add a machine: Assets → + Add → fill in name, code, location, make, model and serial number → Save.

Start with your 20 most critical machines, not all 300. A register that is half finished and accurate beats a complete one nobody trusts.

Work Orders

Who uses it: supervisor raises, technician completes, manager reviews.

A work order is one job on one machine. Something broke, something needs adjusting, something needs checking.

To raise one: Work Orders → + Add → choose the asset, describe the problem, set priority, assign a person → Save.

The technician opens it on their phone, does the job, records what was done and which spares were used, then marks it complete.

Every change is recorded in the Audit Trail with the person and the time. Not to police anyone — so that six months later you can answer "when was this last touched, and by whom?"

Preventive Maintenance

Who uses it: maintenance planner or engineer.

Scheduled work that repeats — weekly, monthly, quarterly, yearly. The app tells you what is due instead of you remembering.

To set one up: Maintenance → + Add → pick the asset, describe the task, choose the frequency, set the next due date → Save.

Checklists

Who uses it: operators and shift technicians.

Repeatable inspection rounds. You build a template once — the list of points to check — and staff complete a run against it each shift or each day.

To use: create the template with its check items, then staff open Checklists, pick it, and tick through on the phone. Each completed run is saved with the time and the person.

Keep a shift round under fifteen items. Long checklists get ticked without looking, which is worse than having none.

Spares & Tools

Who uses it: storekeeper, maintenance engineer.

Two separate registers in one module.

To use: add each spare with its minimum level. When a technician uses a part on a work order, the stock reduces. The low-stock flag is what triggers a purchase request.

Set the minimum to the quantity you need on the shelf to survive the lead time. If a bearing takes three weeks to arrive and you use one a month, a minimum of one is already too late.

Purchase Orders

Who uses it: engineer requests, owner approves, storekeeper receives.

The full purchase cycle, built around Pakistani practice — PKR, NTN and STRN, 18% GST.

  1. Request — someone raises a material request for what is needed.
  2. Purchase order — the request becomes a PO against a supplier. Numbers are generated automatically as PO-2026-0001.
  3. Approvalonly the owner can approve. This is deliberate and cannot be delegated in the app.
  4. Receipt — when goods arrive the storekeeper records what was actually received, and spare stock increases automatically.

Totals, including GST, are calculated for you. Send the PO to a supplier over WhatsApp straight from the app.

Suppliers

Who uses it: procurement, accounts.

Your vendor list with the details Pakistani purchasing actually needs: NTN and STRN, payment terms (default Net 30), currency (default PKR) and contact numbers.

To use: add each supplier once, then select them when raising a PO. Keeping NTN and STRN here means every PO carries the correct tax details without retyping.

Roster & Attendance

Who uses it: shift supervisor, HR.

Five sections in one module:

Handovers are the most undervalued screen in the app. Most repeat failures in a plant come from something the previous shift knew and did not pass on.

QR Scanner

Who uses it: anyone standing at a machine.

Point the phone camera at the QR sticker on a machine and its record opens immediately — history, open work, manuals, spares.

To set up: generate a QR code from each asset record, print it, laminate it, fix it to the machine where it stays clean and reachable.

This is the feature that decides whether a CMMS gets used. Typing a machine code with oily gloves does not happen. Scanning does.

Condition Monitoring

Who uses it: maintenance engineer.

Record about 30 seconds of a running machine's sound with the phone. The app compares it against that machine's own healthy baseline and flags it when the pattern changes.

  1. Record a baseline while the machine is running normally and you are confident it is healthy.
  2. Record again at regular intervals — weekly works for most plants.
  3. If the sound pattern shifts away from the baseline, you get an alarm.
Be clear about what this is. It is an early-warning aid that tells you to go and look at something. It is not calibrated vibration analysis and not a certified measuring instrument. Use it to prompt an inspection, never to certify that a machine is safe to run.

For a consistent reading: same spot on the machine, same distance, same running condition every time. An inconsistent baseline is worse than no baseline.

AI Problem Solver

Who uses it: technicians and engineers, especially at night.

Describe a fault in plain English or Urdu and get a structured troubleshooting path, grounded in the equipment manuals you have uploaded.

To use: Problem Solver → describe the symptom → it asks clarifying questions → it suggests what to check, in order.

A good description: "Injection moulding machine 4, hydraulic oil temperature reaching 65 degrees after two hours, was 45 last month, no change in cycle time." A weak one: "machine hot".

The AI gives suggestions, not instructions. It can be wrong, and it can be confidently wrong. A competent person must review every recommendation before work is carried out. It never overrides your isolation procedures, permit-to-work system or the manufacturer's instructions.
Its answers are only as good as the manuals you give it. A plant that uploads its manuals gets specific answers with section references; a plant that uploads none gets generic advice.

Manuals & Drawings

Who uses it: everyone; set up by the engineer.

Your equipment documentation in one place, readable on the floor instead of locked in a cupboard in the office.

To use: upload the PDF and link it to its asset. The app indexes the contents so the Problem Solver can quote from it and so you can search inside it.

Upload the manuals for your ten most critical machines first. This is the single highest-value setup task in the whole system, and the one most plants skip.

Analytics & Reports

Who uses it: managers, and anyone facing an audit.

Analytics shows trends — workload, failures, what is consuming your time and money.

Reports generates a document from any of twelve areas: assets, work orders, checklist runs, maintenance plans, spares, tools, support threads, manuals, problem cases, attendance, daily logs and shift handovers.

To use: Reports → choose the module → set a date range → Generate. Preview it, then download as CSV, Excel, Word or PDF.

For an ISO audit, export work orders and maintenance plans for the period as PDF. It is the evidence auditors ask for, and it takes about a minute.

Daily Email Report

Who uses it: plant manager, general manager, owner.

A summary of the day sent by email automatically — work raised and completed, alerts, low stock, attendance.

To use: Daily Email → add the recipients. Management then sees what is happening without logging in or asking anyone.

Alerts

Who uses it: everyone.

Notifications for work assigned to you, approvals waiting, low stock, maintenance due and condition alarms. The unread count sits on the dashboard.

Enable phone notifications when the app asks, so an approval request does not sit unseen for a day.

Audit Trail

Who uses it: owner, manager, auditors.

A record of every change made to plant work — who, what, when. Filter by date, by action type, or search. Export in any of the four formats.

Scope is deliberate: the audit trail records plant work. Platform and database maintenance is not logged, because it is not your operation. Reading a record is not logged either — only changes.

Recovery Bin

Who uses it: owner, manager.

Nothing is deleted immediately. Removed records go to the Recovery Bin and can be restored. After the grace period — 30 days by default — they are permanently erased.

If someone deletes something by mistake, look here first before worrying.

Files

Who uses it: everyone.

Photographs, test certificates, damage pictures and documents, attached to the records they belong to. Use + Upload instead of + Add in this module.

A photo of a failed bearing attached to the work order is worth more than a paragraph describing it.

Team & Invitations

Who uses it: owner.

Invite your team by email and give each person a role:

Company Profile is where your company name, logo and details live. The logo appears on your reports.

Support

Who uses it: anyone.

Two different things, both on the bottom bar. Support is for asking us questions. Complaints is for reporting a problem with the app itself. Both keep the whole conversation on record.

You can also message us on WhatsApp at +92 316 236 4074.

Settings & Profile

Who uses it: owner for settings, everyone for their own profile.

Settings holds theme, data retention periods and plant configuration. Profile is your own details — name, contact, designation, skills, default shift.

Plan on the bottom bar shows your current subscription, user count and storage use.

Your first week

The order matters. This is what works, in the sequence that works.

  1. Day 1 — Company and people. Set up the company profile, invite your team, set roles.
  2. Day 2 — Assets. Add your 20 most critical machines with codes, locations and nameplate photos.
  3. Day 3 — QR codes. Print, laminate and fix a code to each of those machines. Get technicians scanning.
  4. Day 4 — Manuals. Upload documentation for the ten most critical machines. This is what makes the AI useful.
  5. Day 5 — Spares. Enter your fast-moving parts with honest minimum levels.
  6. Day 6 — Live work. Stop using the paper register. Every job goes in as a work order from now on.
  7. Day 7 — Plans and reports. Add your preventive maintenance schedules, switch on the daily email, generate one report.
The hardest part is not the software. It is the fortnight where people are asked to change how they record work. Decide the paper register stops on a specific date and hold that line. Plants that run both systems "for a while" end up with neither.

Want to see it on your own machines?

We will walk you through the app using your plant as the example — no slides, no obligation.