Skip to content

Scenario · Quarry · CommissioningScenario · Commissioning

The new M-sand unit is installed. Why hasn’t it made a tonne?

The last time Alpha1 added a machine at its quarry, it stood finished for five weeks. The electricity board had not fitted a meter, the supplier had not sent an engineer, and every update said “still waiting for them”. Nobody inside owned the chase.

TaskMIS task 1012-0013, Power for the M-sand unit: electricity board meter and load increase: Quarry, M-sand unit, raised by Vikram Iyer on 12 Oct, waiting for Electricity board — meter fitting date for 6 days; assigned to Vikram Iyer, In Progress, High priority, due 24 Oct in 4 days, waiting since 14 Oct, request Self, Very High business impact, nobody copied; what done looks like: load increase applied for in September, done = new meter fitted and power on to the unit. The record: raised on 12 Oct at 10:20; In Progress at 11:00; 13 Oct, fee paid at the section office, they will give a date for the meter; now waiting for the meter fitting date, 14 Oct. Shown on Tuesday 20 Oct at 9:30 AM
Task 1012-0013 on Tuesday 20 Oct, 9:30 AM · Alpha1 demo workspace, sample data
See the new unit’s start-up in TaskMIS

Illustrative scenario. Alpha1 is a fictional company. Not a customer story.

Meet Alpha1 — a fictional construction contractor in Chennai, with its own ready-mix plant and quarry.

  • Vikram IyerVikram · Plant & quarry
  • Leo ThomasLeo · Purchase
  • Rohan PillaiRohan · MD · Admin

What went wrong

Everyone was waiting. Nobody was chasing.

  1. Installer“Unit ready. Power and start-up pending.”
  2. Electricity boardFee paid. A date for the meter “will be given”.
  3. SupplierAn engineer “next week”, every week.
  4. Ready-mix plantKeeps buying the sand it planned to make.

One wait. Three costs.

  • A paid-for machine stands stillThe unit is bought and installed, and the sand is still bought in.
  • Outsiders set the paceWith no date to hold them to, the board and the supplier fit the job in last.
  • The MD hears it lastEach update sounds like progress, so nobody asks for help while there is time.

The same start-up in TaskMIS

Same outsiders. Every wait has an owner and a date.

  1. 01 PlanMon 12 Oct
  2. 02 Step inTue 20 Oct
  3. 03 Power20 – 22 Oct
  4. 04 StartFri 30 Oct

Mon 12 Oct · PlanMon 12 Oct, 10:00 – 10:45 AM · Four tasks before the first tonne

What stands between the unit and its first run, as tasks.

Rohan Pillai, the MD, raises the start-up for Vikram Iyer, who runs the ready-mix plant and the quarry: first trial run by 26 October. Vikram writes down what it depends on, each with one owner and a date: the electricity board’s new meter by 24 October (his own), the supplier’s engineer by 24 October (Leo Thomas in purchase) and the wash-water pond by 21 October.

4 tasks · 2 owners · due 21 – 26 Oct

Tasks filtered to the Quarry department, Monday 12 Oct at 10:45 AM: 4 of 13 active tasks, all Quarry, M-sand unit. 1012-0015 Settling pond for the wash water: lining and pump, Vikram Iyer, Medium, Not Started, due 21 Oct; 1012-0014 Supplier’s service engineer for the start-up and trial run, Leo Thomas, High, Not Started, due 24 Oct; 1012-0013 Power for the M-sand unit: electricity board meter and load increase, Vikram Iyer, High, Not Started, due 24 Oct; 1012-0012 Start up the new M-sand unit: first trial run, Vikram Iyer, High, In Progress, due 26 Oct
Tasks → Department: Quarry, Monday 10:45 AM

Tue 20 Oct · Step inTue 20 Oct, 9:30 AM · Two waits reach the MD while there is time

Waiting six days with four to go: the Dashboard sends it to the MD.

Vikram paid the board’s fee on 13 October and marked the meter as waiting the next day; Leo asked the supplier for an engineer on the 13th. By Tuesday the waits are six and seven days old, with both due on Saturday. A task due within a week and waiting three days or more is at risk, and a High-priority task at risk goes to the MD.

2 at risk · waiting 6 and 7 days · escalate to the MD

Dashboard filtered to Quarry, Tuesday 20 Oct at 9:30 AM, Management intervention list, 2 tasks requiring intervention. 1012-0013 Power for the M-sand unit: electricity board meter and load increase, High priority, Very High impact, owner Vikram Iyer, Quarry, due 24 Oct, At risk: due in 4 days · waiting for Electricity board — meter fitting date 6 days, escalate to MD. 1012-0014 Supplier’s service engineer for the start-up and trial run, High priority, High impact, owner Leo Thomas, Quarry, due 24 Oct, At risk: due in 4 days · waiting for Supplier — engineer’s dates 7 days, escalate to MD. Rule: MD when overdue 8+ days, the date has moved 3+ times, or a High-priority task is at risk
Dashboard → Management intervention list, filtered to Quarry

20 – 22 Oct · PowerTue 20 – Thu 22 Oct · One visit and one call, both on the record

The MD’s visit goes on the task, where everyone can read it.

That afternoon Rohan meets the assistant engineer at the board’s section office and writes the outcome on the task: the meter will be fitted on Thursday 22 October. On Wednesday he calls the supplier’s regional manager, and the engineer is booked for 28 – 29 October. On the 22nd the meter is fitted and the power goes on.

The record of task 1012-0013, 9 entries: Vikram Iyer raised this task on 12 Oct at 10:20, assigned to Vikram Iyer, target date 24 Oct, High priority, Very High impact; Status: Not Started → In Progress, 12 Oct, 11:00; Vikram Iyer on 13 Oct at 16:00: Fee paid at the section office. They will give a date for the meter; Now waiting for: Electricity board — meter fitting date, 14 Oct, 10:00; Rohan Pillai on 20 Oct at 17:40: Met the assistant engineer at the section office. Meter fitting confirmed for Thu 22 Oct; No longer waiting — unblocked, 22 Oct, 15:00; Vikram Iyer on 22 Oct at 15:18: Meter fitted and the load increased. Power on to the unit; Status: In Progress → Completed, 15:20; Completed, delivered 22 Oct
The power task’s record · append-only, no user can edit

Fri 30 Oct · StartFri 30 Oct, 4:00 PM · The first trial run

The first run, four days after the first date, with the reason on record.

With the power on, Vikram moves the start-up from 26 to 30 October, giving the engineer’s dates as the reason. The engineer signs off the start-up checks on the 29th, and on the 30th the unit runs four hours at full feed. Rohan’s completion mail shows one date change and the task closed on the new date.

Completion mail to Rohan Pillai: Vikram Iyer completed your task, Start up the new M-sand unit: first trial run. Completed on Fri 30 Oct 2026; target date Fri 30 Oct 2026 — on time; date moved 1 time; reminders sent 2; done by Vikram Iyer; task #1012-0012; the team admin can reopen it with a reason
Completion mail to Rohan, Friday 30 Oct

Completion mail to Rohan

Try it on the next thing you are waiting for.

Free for up to 6 members. No credit card required.

Join TaskMIS Today

The difference

Same outsiders. A different October.

DateWaitingIn TaskMIS
12 OctMonWaitingUnit installed. “Power and start-up pending.”In TaskMISFour tasks, two owners, due 21 – 26 Oct
14 OctWedWaitingThe board will “give a date”.In TaskMISWaiting for the board, since 14 Oct
20 OctTueWaitingStill waiting. Nobody has told the MD.In TaskMISTwo waits at risk; sent to the MD
22 OctThuWaitingThe meter is still a phone call away.In TaskMISMeter fitted; power on
30 OctFriWaitingThe plant keeps buying sand.In TaskMISFirst trial run doneRunning

The board and the supplier kept their own pace either way. The difference is that every wait had an owner, and the MD saw it while there was still time.

What could change

Three outcomes for Alpha1

Waits stop looking like progress.

A task waiting on someone shows who and since when, so “still waiting” has a number of days.

FeatureWaiting for · Updates on the task

The MD steps in on day six, not week six.

A High-priority wait that threatens its date goes on the intervention list for the MD.

FeatureAt risk, before it is late · Who should step in

The next installation starts from this record.

Who was chased, when and with what result stays on each task.

FeatureA record no user can edit · Completion mail to the raiser

Possible outcomes in a fictional scenario, not measured customer results.

Used in this scenario

  • One owner on every task
  • A target date is required
  • Waiting for
  • Updates on the task
  • At risk, before it is late
  • Who should step in
  • Management dashboard
  • A reason for every date change
  • A record no user can edit
  • Completion mail to the raiser
See every feature on the Product page →

For the owner

Four answers before a new machine stands idle

  • What is the new unit waiting for, and since when?

    Answered in: Tasks · Waiting on someone
  • Which waits threaten this week’s dates?

    Answered in: Dashboard · At risk
  • Which of them need the MD, not the owner?

    Answered in: Dashboard · Management intervention list
  • Why did the start-up move, and by how much?

    Answered in: The task’s record

Start this week

Start with the machine that isn’t running yet

  1. Write down everything its start-up depends on, one task each, with one owner and a date.
  2. When a task waits on an outsider, mark it as waiting, with who.
  3. On Monday, filter the Dashboard to that department and start with the intervention list.

Questions

Quick answers

Can the electricity board or the supplier see the task?

No. Only your team works in TaskMIS. The owner records what the outsider promised, and the wait shows on the task.

Does TaskMIS chase the supplier for us?

No. TaskMIS mails your own team: the owner, the person who raised the task and the people copied. The call to the supplier is still made by a person; TaskMIS shows who should make it, and when.

Is this a commissioning system?

No. TaskMIS tracks the follow-up: who owns each step, by when, and what it is waiting for. Keep your drawings, checklists and test records where they are today.

Bring clarity and accountability to your team.

Join TaskMIS Today

Free for up to 6 members. No credit card required.