ASSURA β€” Predictive Impact Tool NAV Methodology v1.3 Locked

Predicts NAV impact per MC / Region / Circle from a site-down incident.

← Home
🧾 Single Incident
πŸ“‹ Batch Table (Multiple TT)

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) β–Ύ

RegionCircle
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)

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.