Shift comparison and trends for the selected date / month.
Gare Palma Sector-III · Raigarh, Chhattisgarh
GP3 Opencast Coal Mine
Owned by CSPGCL and run by Adani. Coal from GP3 is dedicated to CSPGCL's 2×500 MW Marwa thermal power station.
Rated capacity 5 MTPAOutput ~4 Mt/yrCoal since 2019
🏛️
Owner
CSPGCL
Chhattisgarh State Power Generation Co. Ltd — won the block in the March 2015 coal-block re-auction.
⛏️
Mine developer & operator
Adani
Adani develops and runs the mine for CSPGCL — one of its coal mines in Chhattisgarh. Production started in 2019.
⚡
Where the coal goes
Marwa TPS · 2×500 MW
Dedicated to CSPGCL's Atal Bihari Vajpayee Thermal Power Station, Marwa (Janjgir-Champa).
📈
Production vs 5 MTPA rated
2022
3.58 Mt
2023
~4.0 Mt
2024
3.99 Mt
Mine facts from public sources (CSPGCL, Adani Enterprises, Global Energy Monitor); production figures are approximate.
Shift comparison — selected date
Shift
Incharge
Coal trips
Coal ton
Loaders
Tippers
OB trips
OB Cu.M
Excavators
Dumpers
Trends
📊 How to read the charts: Choose at the top — Day-wise (month) shows one bar / point for each day of the month (dates along the bottom axis); Shift-wise (date) shows shifts A, B and C separately for the selected date. Hover or tap any bar / point to see the exact value. Click a name in the legend to hide or show that line.
Production report
No production data yet — please fill the Production report (date + shift) and Save.
No production data yet — please fill the Production report and Save.
🟧 Coal production chart: tonnes of coal produced per day / shift — the taller the bar, the higher the production. 🟦 OB removal chart: overburden removed (Cu.M) per day / shift.
No production data yet — please fill the Production report and Save.
🚚 Trips chart: number of trips for coal and OB side by side. If trips go up but tonnage does not, the load per trip is low — worth checking.
Overall lead
No overall lead data yet — please fill the Overall lead page (manual & FMS km) and Save.
📏 Overall lead = haul distance (km) from the loading point to the dump / stockyard. The Manual and FMS lines should stay close together; a large gap means the FMS or manual entry should be checked.
Running fleet
No running fleet data yet — please tick the running machines on the Running fleet page and Save.
🚜 Running fleet: number of machines working per day / shift — Loaders and Tippers (coal), Excavators and Dumpers (OB). A drop in the count usually means breakdowns or idle machines.
Running fleet report
Quick fleet-running check at shift start — mark who's running and send it, before full production numbers are ready.
Saved running fleet records
Date
Shift
Loaders
Tippers
Excavators
Dumpers
Noted by
Production report
Shift-level totals only — one record per date + shift. Not a trip log.
Pick date and shift first. If a record already exists for that date + shift, it loads automatically so you can update it.
Saved shift production records
Date
Shift
Incharge
Coal trips
Coal ton
Coal WB (trips / t)
Coal FMS (trips / t)
OB trips
OB Cu.M
OB Manual (trips / Cu.M)
OB FMS (trips / Cu.M)
Overall lead report
Quick shift-level lead summary — one manual and one FMS figure each for Coal and OB, used for the dashboard lead graph.
Saved overall lead records
Date
Shift
Coal manual
Coal FMS
OB manual
OB FMS
Noted by
Breakdown / workshop
Log the breakdown when it starts. When repair is done, click Edit on the same row and fill the end date / time — the record stays one row with its total downtime.
Saved breakdown records
Date
Shift
Vehicle
Start
End
Downtime
Reason
Status
Workshop
Notes
No-communication equipment
Vehicles that have lost FMS signal.
Saved no-comm records
Date
Shift
Vehicle
Time lost
Location
Remarks
Additional work/SLA
Any work carried out during a shift — not limited to breakdown or no-comm follow-up.
Saved additional work/SLA records
Date
Shift
Vehicle
Work description
Reported by
Shift report
Everything for one shift — production, running fleet, lead, breakdown (and additional work/SLA, when logged) — ready to export or share.
Daily report
One date, or any date-to-date range.
Monthly report
A whole month, or any date-to-date range.
Admin login
Authorised users only.
FMS Portal
Adani FMS (Amnex) portal — live fleet & trip data.
Send a completed shift report to your client and seniors on WhatsApp and Email in one go, through an server automation.
This dashboard runs entirely in your browser, so it can't send WhatsApp or Email itself. Point it at a Webhook URL — that one workflow can branch to a WhatsApp node and an Email node in parallel.
Quick setup
In your automation server, create a workflow and add a Webhook node (Method: POST). Copy its Production URL into the field below.
After the webhook, add two branches: a WhatsApp Business Cloud node (or an HTTP Request node to Twilio's WhatsApp API), and a Send Email node (Gmail / SMTP / Outlook).
The webhook sends { date, shifts, message, messageHtml, recipients }. Use message (plain text) for WhatsApp, and messageHtml (line breaks as <br>) for the email body if your Email node is set to HTML — otherwise use message there too.
If the email comes through blank: click "Listen for test event" on the Webhook node, then hit "Send test message" below — the server will show the exact incoming JSON. Most often the fields sit one level deeper, under body (e.g. {{$json.body.message}} instead of {{$json.message}}) — check the panel and fix the expression in your Email/WhatsApp node to match.
Every Send button also posts subject, dateFrom, dateTo, section and attachments — a list of { fileName, mimeType, base64 } (the Excel and the PDF of that section). In your automation server, split attachments, use a Convert to File node (“Move Base64 String to File”) and attach the binary in the Email node; use subject as the email subject.
Password-reset emails use the same webhook with purpose: "admin-password-reset" and only the admin email in recipients (no phone) — make sure the workflow skips WhatsApp when phone is empty.
Team sends (the Send to team buttons and Admin panel → Team members) use the same webhook with audience: "team" and only team members in recipients; client sends have audience: "client". Branch on audience in server if the team should get a different template or sender.
Loop over recipients (each has label, phone, email) so every number/address gets the message. Activate the workflow, then re-test.
Recipients
Label
WhatsApp
Email
Leave WhatsApp or Email blank if a recipient only needs one channel. Numbers/emails go to your webhook with each report — your automation workflow decides who actually gets messaged.
Recent send log
Time
Status
Note
Logged in as admin
Company API (auto-import)
Pull shift production / trips / lead from your company's system — shift-wise, once per shift, kept as a fixed snapshot you can edit here.
How the timing works: data is collected per shift, 1.5 hours after the shift ends. The browser can't run on a timer by itself, so the scheduled pull runs in the automation server (a cron job reads the settings below, calls your company API, and sends the data here). Once a shift's data is imported it is not re-pulled — it stays as saved and remains editable on the Production / Overall lead / Running fleet pages.
Company portal (open & read)
Captcha & login are done by you on the portal. Your ID / password are stored only in this browser (never inside the file you share). The browser can't solve the captcha, so open the portal, log in yourself, then read / download there — or bring data in via Import / n8n.
In your automation server, call the company API, map its fields into this shape, then either POST it to a Supabase table or paste it here. lead and fleet are optional. Only the fields present are imported; the rest can be filled in by hand later.
Import log
Time
Date
Shift
Result
Logged in as admin
Team
Our own team, roster and attendance — admin-only. The list is separate from the client recipients in WhatsApp & Email.
Add a team member
Our team
Name
Role
WhatsApp
Email
Send a message to the team (WhatsApp + Email)
Recent team sends
Time
Status
Note
Monthly roster
Click a cell to cycle the shift: blank → A → B → C → Off → Leave → blank. Then press Save roster. (Each click is also saved automatically as a backup.) Add members in the Members tab first.
ABCOffLeaveNot set
Attendance
Actual shift is pre-filled from the roster. If someone worked a different shift than their roster, change it here — it is recorded as a coverage / swap. Mark Absent or Leave as needed.
Member
Role
Rostered
Actual shift
Status
Note
Coverage / swaps this month
Date
Member
Rostered
Actual
Status
Note
Logged in as admin
Master data
Add a vehicle when new equipment arrives at the mine, or remove one that's gone — every form and dropdown updates immediately. Historical records already saved keep referencing the old vehicle number.