MAINTENANCE WINDOWS,
DONE RIGHT.
MaintWindow manages the full lifecycle of your biannual Shutdown / Startup Procedures document — from event creation and developer assignment through to PDF/DOCX export and email delivery. Every sent document is immutably archived as the institutional record.
EVERY UPCOMING WINDOW AT A GLANCE.
The dashboard surfaces all upcoming maintenance events and your five most recent sent documents. A single button triggers the Kronos-driven auto-create logic — no manual date entry needed. Events progress through a clear status pipeline from creation to permanent archive.
- Upcoming events sorted by date with status badges
- Recent document history with sent-on timestamps
- One-click Auto-Create for March 1 and June 1 events
- Status pipeline: pending → assigned → previewed → sent → archived
ASSIGN THE RIGHT PERSON TO EVERY TASK.
Each maintenance event generates a set of task items from the template library. Assign one or more developers to each item with a role — owner, validator, lead_shutdown, or lead_startup. Assignments are saved immediately and locked once the document is sent.
- Task items rendered in phase order (Shutdown A–F, Startup A–C)
- Multiple assignees per task with distinct roles
- Validation steps highlighted with amber badge
- Modal-based assignment — no page navigation required
- Full read-only lock once document is sent
ONE CLICK FROM PREVIEW TO SENT.
Preview the finished document in-browser before exporting. Download a PDF via WeasyPrint or a DOCX via python-docx — both rendered from the same single Jinja partial, so there is no drift between formats. When ready, email the PDF attachment to the distribution list and lock the event permanently.
- HTML preview rendered in the browser before export
- PDF download via WeasyPrint
- DOCX download via python-docx
- Single template source — PDF and DOCX are always identical
- Email sends PDF attachment to configurable distribution list
- Event locked permanently after send — immutable institutional record
Event Created
Kronos auto-creates the event 30 days before March 1 or June 1. Can also be triggered manually from the dashboard. Status: pending.
Developers Assigned
A procedure lead opens the event detail page and assigns developers to each task item using the assignment modal. Status: assigned.
Document Previewed
Clicking Preview renders the document in the browser. This sets the event status to previewed and lets the team review before sending.
PDF / DOCX Exported (optional)
Download a PDF or DOCX at any stage before sending. The same _preview_partial.html template drives all three output formats.
Email Sent — Event Locked
Email & Lock sends the PDF to all active distribution recipients and permanently locks the event. The HTML snapshot is stored. Status: sent → archived. No further edits possible.
STRUCTURED. AUTOMATED. IMMUTABLE.
Manage every maintenance window from creation through delivery — with a permanent institutional record after each send.
Sign In to Enter →Premier app — requires MelTuc account