0 Reference Data (Daily Denum & Hourly Profile) βΎ
You can select multiple files at once (mix of .csv / .zip / .rar), e.g. per-region or per-batch exports. Everything is extracted & parsed in the browser then merged into one index. The tool automatically picks the date with the most complete 24-hour coverage (across all files) as the reference day.
0a Sitemapping (Site β MC β Region β Circle) βΎ
Official master mapping for Site/MC/Region/Circle (columns read: siteid, mc, region, circle_id/circle, site_name). Once loaded, this becomes the primary source for resolving MC/Region/Circle β Circle Mapping (0b) is automatically refilled from here, and the Region guess from hourly data is no longer used. Hourly availability data (panel 0) still needs to be uploaded separately for the Denum numbers β sitemapping only provides the relationship, not the availability figures.
0b Circle Mapping (Region β Circle) βΎ
Region
Circle
Used to automatically resolve Circle from the Region found during parsing/incident entry. If Sitemapping (0a) has been loaded, this table is automatically refilled from it (more accurate); the defaults below are just a manual fallback for Circle KSMP.
1 Input Incident
Paste WhatsApp SPO Notification
Upload Excel Tracker
Paste Incident Notification
2 Parsed Incident (editable)
3 Calculation Result
β
Total Sites (matched)
β
Hours Remaining (until 23:00)
β
LND 2G / hour (sec)
β
LND 4G / hour (sec)
Recovery Urgency (Circle): β
Impact per Hour (average)
Level
2G Impact % / hour
4G Impact % / hour
Cumulative Impact through End of Day 23:00
Level
2G Impact %
4G Impact %
Denum Full Day 2G
Denum Full Day 4G
Impact per Hour = LND(1 hour) Γ· Denum(group, same hour), averaged only over the typical hours (the LND value that occurs most often across the 24-hour reference day) β anomalous hours (e.g. a temporary drop in active cell count) are automatically excluded so they don't drag down the representative rate.
Cumulative Impact = effective N hours (from the start hour through hour 23) Γ average LND per hour across all 24 hours (including anomalies) Γ· Daily Denum, technology-specific β because the real total exposure in a day must account for those anomalies too.
2G and 4G Denum are always taken from their respective technology columns β never mixed.
4 Actual vs Projected NAV per Hour Chart
Download as PNG
Download as JPG
NAV Impact per Hour
Y-axis scale differs per panel β note the drop pattern at MC level vs the dilution effect at Region & Circle.
Actual NAV (reference, no incident)
Projected NAV (if it continues)
Actual = Num(reference, hour h) Γ· Denum(reference, hour h) β normal condition without the incident.
Projected = (Num(reference, hour h) β Denum of the affected site) Γ· Denum(reference, hour h), applied from the hour the incident starts β assuming the site is fully down.
B Batch Table β Multiple TT
Upload an incident tracker (.xlsx/.csv) with one row per TT. Expected columns: Title, TT Number, Occur Time, Circle, Region, MC Cluster, Affected Site List (comma-separated site codes).
Missing MC/Region/Circle are auto-resolved via Sitemapping (0a) from the affected sites. Requires Reference Data (0) to already be loaded.
B2 Batch Results
Click π on any row to open its Actual vs Projected NAV chart.