Miller Work Order Processor

Total Work Orders

0

Open Orders

0

Completed Work Orders

0

Emergency

0

Emergencies This Week

0

Recent Work Orders

View all →

Map

Open full map →

Metrics — All Sections

Show charts for:

By Status

By Stage

Actions Taken Lookup

Actions Taken combo:

Upload NYC DOT Work Order

Upload an NYC DOT Work Order PDF or photo to automatically extract and organize the work order information. Drag and drop a file here, or browse to select one. PDF, JPG, PNG, or HEIC.

Browse Files

Batch Update from Scanned PDF

Have a single PDF of many already-completed, hand-marked-up work order pages from the field — or even just one — a photo works too? Upload it here — each page is read by the same AI handwriting reader used for single photos, matched against existing Work Orders / Carry Over records by Work Order #, and queued below for you to review. Nothing is saved to a record automatically — every page needs your explicit approval before its note and suggested Legacy Entry fields are added to the matched record. One page is treated as one work order. No limit on how many pages. A page that's blank, or an exact repeat of one already read before, is skipped/reused automatically at no extra cost. A small batch processes live (progress bar below); a large batch (more than a handful of pages) is submitted as a discounted background batch instead — it typically finishes within about an hour and appears in the queue automatically, no need to keep this tab open. See "Background Batches" below for anything still in flight. Click "Preview (no cost)" first — it checks every page locally (blank pages, exact repeats, and pages that already match a record marked Completed) and reports how many pages would actually need a real, billed AI read, making zero API calls. "Run Extraction" (the real, billed pass) stays disabled until you've previewed the currently-selected file.

Choose Scanned PDF or Photo

Pending Batch Updates

"Approve All Matched" writes the note + Legacy Entry suggestion for every pending page that matched exactly one record AND had no AI read error — the same as clicking Approve on each one by hand. Anything with no match, an ambiguous match, or a read error is left in this list either way.

Showing Work Orders (55), Carry Over (52) and Utility Referrals (54) together — use the toggle above to narrow to one. Export downloads exactly what's filtered and sorted below; the ▾ beside it has the Excel and weekly-submissions versions. For the monthly billing sheet, pick a Closed Month under "More filters". Comparing against DOT's own numbers? Use Weekly DOT Reports in the left nav instead.

Status breakdown

Top ZIP codes

Add a User

Accounts

Emergency Detection

Defect Type values that mean Emergency

Defect Code values that mean Emergency

Keywords in Comments that mean Emergency

Separate multiple values with commas. Matching isn't case-sensitive. Defect Type/Code must match a value exactly; keywords match if they appear anywhere in the Comments text.

Email Ingestion

Which incoming emails should land in the Email Queue for review. At least one sender must be set — otherwise nothing gets pulled in, to avoid accidentally ingesting the whole mailbox.

Only from these sender email addresses

Subject must contain (optional)

Separate multiple values with commas. An email must be from one of the listed senders AND have a PDF attached; if you also list subject text, the subject must contain at least one of those phrases too.

Instant-alert ("Situation Room") subject match

Some senders (e.g. NYC DOT's "Situation Room" mailer) send a text-only heads-up with no PDF attached, ahead of the real work order PDF email a bit later. A no-attachment email from one of the senders above, whose subject contains one of these phrases, fires the emergency alert (SMS/email) immediately — no Defect Type/Code check, treated as urgent on its own. When the real PDF email for the same work order arrives shortly after, it's filed normally with no second alert sent. Leave blank to disable.

Weekly SLO Approved-list report subject match

NYC DOT's weekly digest email carries a "Wkly-SLO-Open3" attachment listing every work order number currently DOT-approved for SLO relief. An email from one of the senders above whose subject contains one of these phrases has that attachment imported automatically, and sets SLO Status to Approved on every work order number it lists (new numbers are created, already-tracked ones backfilled). A work order that drops off a later week's list keeps whatever SLO Status it already had — never cleared. Leave blank to disable.

DOT Contract

Contract Number

Printed on the Monthly Inventory export whenever the export is run without explicitly overriding it. Confirm this against the actual, current NYC DOT contract before relying on it.

Batch Update from Scanned PDF / Photo Auto-update Stage/Status/SLO/Actions Taken from a recognized code. When a scanned page or photo's extracted Repair Disp code is one of the real, known Disposition codes (not an AI confidence guess — the same reference table the Recommended Action card uses), the matched work order's Stage (and Status/SLO when the code confirms one of the 4 known SLO stages) updates immediately, with a note explaining why. The same rule also covers Actions Taken: if the extracted value splits cleanly into recognized 2-letter codes (like "LR"), it's confirmed straight into the Legacy System Entry's Actions Taken field the same way — again, only when every code is a real recognized one, never a numeric confidence guess. Safety-critical Disposition codes (like Voltage On Pole) and codes DOT requires an explanation for (Cannot Repair, No Access, City Equipment Needed, Construction Damage) never auto-apply — those, and the rest of the detailed Legacy System Entry fields for every page, always still wait in the queue for a person to confirm. Off by default. Auto-approve pages that matched a work order and read cleanly. When a scanned page or photo (a) matched exactly one existing Work Order / Carry Over record by its Work Order # AND (b) the AI reported no trouble reading the page, its note and full Legacy Entry suggestion are saved to that record automatically — the same as clicking Approve yourself — and it never shows up in the Pending Batch Updates queue at all. A page with no match, an ambiguous match, or any read error always still waits in the queue for a person, no matter what this is set to. This is separate from the Stage/Status/SLO setting above — that one only moves Stage/Status/SLO for a recognized code; this one writes the notes and Legacy Entry fields too. Off by default.

Miller Work Order Processor

Dashboard

Recent Work Orders

Map

Metrics

Metrics — All Sections

By Status

By Stage

Actions Taken Lookup

Upload Work Order

Upload NYC DOT Work Order

Batch Update from Scanned PDF

Background Batches

Pending Batch Updates

Carry-Over Completion Report

Pending Carry-Over Report Rows

Work Orders

Manage Users

Add a User

Accounts

Settings

Email Queue

Miller Work Order Processor

Dashboard

Recent Work Orders

Map

Metrics

Metrics — All Sections

By Status

By Stage

Actions Taken Lookup

Upload Work Order

Upload NYC DOT Work Order

Batch Update from Scanned PDF

Background Batches

Pending Batch Updates

Carry-Over Completion Report

Pending Carry-Over Report Rows

Work Orders

Manage Users

Add a User

Accounts

Settings

Email Queue

Work Order Already Exists

Delete Work Order?

Edit Actions Taken

Now print the notes

Now print the repair sheet

Now print the repair sheet

Now print the repair sheet

CSV Import Complete

DOT Weekly Report Import Complete