Platform
DICT Justifications
DICT Region VIII lists the sites its monitoring saw down each day and asks for a cause and an action plan for every one. This page gives every listed day one of seven reasons, in set wording, from our tickets, crew reports, schedules, hourly data, weather and holidays.
What it is
Main → DICT Justifications (superadmin, admin and NOC operators; it was called DICT escalation until November 2026). You upload the escalation sheet DICT emails us each day; every listed day gets an answer, and once a week the week is answered, checked and exported back to DICT. Four tabs: Dashboard (charts week by week, and the agent's model and cost), This week (where the week stands, what is left for a person, every site), History (every earlier week, each opening the same way) and Upload.
Per site, not per day
What DICT expects, and when
- Each daily report covers noon to noon (PH time) and lists every AP DICT's NMS v2 saw down.
- For every listed site we owe a cause of downtime and an action plan.
- DICT builds its monthly report from them, so the reply is due by month-end — every day of the month answered. We only answer what DICT listed; downtime we saw that DICT did not list is not raised.
Each week, step by step
| Step | What you do | What the page does |
|---|---|---|
| Upload (every day) | On the Upload tab, drop DICT's workbook as it came from the email — the page shows what the file should look like. The whole month's file is fine. | Reads it in your browser and shows each day in it (new, or already uploaded) and any site code that isn't ours — match it to our site there and later uploads remember. Then keeps our three projects (250 R8, 458 E. Samar, 73 Huawei), stores each site per day, and fills them in. A newer copy later updates DICT's side and keeps every answer already written. |
| Answer last week (Monday) | On This week, press Answer last week. It works on Mondays once all seven of last week's sheets are in; a missing day locks it and says which. Superadmins can press it any day. | Every night the rules give each listed day one of the seven reasons (next section). The button has the justification agent write each site's own answer for that Monday to Sunday where the reason was only weekend, after hours, broken equipment or manual shutdown (see Written for the site). Keep the page open while it runs. Never overwrites anything written by hand — unless it contains a phrase that never goes in the sheet (see Wording). |
| Check what's left | On This week (or the week in History), Left for a person lists days with no answer and sites the agent couldn't write for. Open any site with View to see what each day was given, change a day by hand, or have AI re-check the site. | Saves each change with your name and the time. |
| Export the week | Press Export this week and send the file to DICT. The week shows as sent, with who and when. | One tab per day in DICT's layout, one row per AP, cause and action plan filled in; a summary tab first. Refuses while any row contains a phrase that never goes in the sheet, and warns you if a site still has an unanswered day. |
A day DICT sent no sheet for shows red in the week's seven boxes, and keeps the button locked. Upload it, then press Answer — the agent answers only what it hasn't written yet.
How “Justified” is decided
A day DICT's NMS v2 can't see (every listed AP marked UNMONITORED) and a day covered by a signed beneficiary acknowledgement keep those answers. Every other listed day gets the first of these seven reasons that fits:
| Order | Reason | When |
|---|---|---|
| 1 | Holiday | A national, Region VIII, provincial or town non-working holiday where the site is, on DICT's day or the day before (DICT's window runs noon to noon). Only holidays set by proclamation, RA or EO count. |
| 2 | Site under renovation | A ticket, ticket comment or crew visit report says the building is being renovated or rebuilt (in English, Tagalog or Waray). |
| 3 | Weather | The site is tagged Solar/battery, Island or Boat access in Site conditions, and its town had 30 mm of rain or more, or a storm signal, that day or the day before (a solar site also the day before that, to recharge). A ticket closed as rain or storm counts for any site. Weather comes from the nightly weather job. |
| 4 | Weekend shutdown | DICT's day is a Saturday or Sunday. |
| 5 | After hours | The site went dark outside its hours: its saved schedule, or 8 AM–5 PM on weekdays when it has none (sites marked 24/7 too). Up to 2 hours before closing counts. |
| 6 | Broken equipment | A ticket closed as hardware failure, an installer's can't-fix reason, a crew report or a resolution says something broke or was replaced. A guess on a ticket (“check if the APs are damaged”) is not enough. |
| 7 | Manual shutdown | None of the above. |
One reason per outage
Wording
Wording, beside Upload sheet, lists the seven reasons with the cause and action plan each one writes. Admins can change a reason's sentences; the change applies from the next nightly fill. A sentence may use the blanks shown under it — {holiday}, {town}, {weather}, {effect} — filled in for each site.
Phrases that never go in the sheet
Reading a site (View)
Every row has View. It opens the site — whether its APs are up right now, where it is and its Site conditions — with an AI review on top and three tabs:
- Each day — one card per outage: the reason, the cause and action plan DICT reads, and why it got that reason (the holiday, the crew report, the rain, the time it went dark). Write by hand changes every day of the outage at once; Every day in detail has DICT's times and the ticket for each day.
- Hour by hour — the last 30 days, one row per date, one square per hour. Green: all APs on. Amber: some on. Dark: off. Hollow: no reading (our collector missed that hour — not an outage). A DICT tag marks the days DICT listed.
- Tickets & notes — the site's tickets with their stage, every comment, installer can't-fix reason and crew visit around the dates, its town's rain day by day, and its holidays.
Changing a day by hand
In View, the pencil on a day lets you write its cause and action plan yourself. What you write is kept by every later fill — unless it contains one of the phrases above. If a site's reason is wrong because its data is (a missing schedule, Site conditions not tagged, a renovation nobody wrote down), fix that on the site or the ticket — the nightly fill picks it up the next morning.
Written for the site
The seven reasons can only say “weekend”, “after hours”, “broken equipment” or “manual shutdown” about most days. When Answer last week is pressed on a Monday, the justification agent rewrites those days with what that site actually does: its hour-by-hour pattern over the last 30 days with the counts (“dark from 5 PM on 17 of the last 20 weekdays”), its earlier tickets and crew visits (“our team restored the site on 8 Oct”), visits planned for it, notices and weather. Days with a power notice, a letter, a holiday, renovation, weather proof, a signed acknowledgement or words written by hand are never touched.
It never writes that a site was down through our fault: nothing about data running out, distance, boat access or faulty equipment. Where it is ours, it says there is an issue at the site and a visit is scheduled. Its words are checked against that list before they are saved; an answer that fails twice is left for a person and listed under the week's Left for a person. A site with no readings and nothing on file is listed too.
In View, Review this site drafts the same answers for one site and shows only the days it would change; nothing is saved until you press Save. Both cost a little from the shared AI budget (AI Center → Usage, under dict-justify-agent).
The Dashboard shows which model writes the answers, what each costs per site and per week, the last run and the spend this month. Admins can switch the model there; it applies from the next run. One call covers all of a site's days, so a week of about 350 sites costs about $1 on Haiku 5.5.
Who’s doing what
Under History: per person, how many uploads, fill-ins, answers and exports they did and when they were last active, and the latest 50 actions (“Wrote: …”, “Accepted AI draft: …”, “Changed the wording for …”). Every answer keeps what it said before and after, so a change can always be traced to a person.
What it does not do
- It does not send anything to DICT — the export is sent by a person.
- It does not raise tickets. A site that needs one is raised from the helpdesk as usual.
- It does not answer downtime DICT did not list, and it does not change DICT's side of the sheet (their times and statuses are kept as they sent them).