MTO Staffing & Activity — Stakeholder Walkthrough
Welcome. This is a click-through demo of the proposed phase-one Staffing & Activity-Tracking application. It is built for HR, production staffers, supervisors, timekeepers, and IT/reporting observers attending the discovery workshops.
It does not replace the working design pages, the SOWs, or the proposed solution brief — those live in knowledge/wiki/. This demo exists to help everyone in the room see the same picture of what the application would feel like in day-to-day use, before we lock the PRD.
How to use this demo
- Pick a use case below.
- Open its index page to meet the user and read the scenario.
- Click Next at the bottom of each step to walk through the workflow.
- Click Use Case Index in the footer to jump back to the use case's start or Demo Home to return here.
The mockups are drawn in a plain WPF + open-source theme style — they indicate what the built application would look like without assuming any commercial component license. Specific values (employee names, shop orders, product descriptions, dates) are fabricated for illustration. Visual polish will be refined in a downstream UX pass; the goal here is to align on workflow and information, not on theme choices.
Background
- Solution Architecture — how the new application fits with Kronos, Active Directory, SSRS, and the PLP/BI warehouse poll; what the new app owns vs what stays where it is; validation rules; pilot and rollback. Worth reading before the use cases if you want the systems picture first; safe to skip if you'd rather start with the workflow.
Who you'll meet
| Persona | Role | Use cases |
|---|---|---|
| Maria Rivera | Staffing Clerk · Dept 3630 / Line 5 | UC1, UC4, UC5 |
| Kavi Patel | Timekeeper | UC2 |
| Jaspreet Singh | Production Supervisor · Dept 3630 | UC3 |
Use cases
Core workflows
Staffing the line — Maria opens her scope, sees the day's shop orders, assigns employees to a team, watches the app validate against punches in real time, and saves. 5 steps.
Resolving an activity error — Kavi opens the Activity Errors queue, picks a hard fail, reads the punch-vs-activity timeline, applies a correction, and watches the downstream feed clear. 5 steps.
Monitoring the shift — Jaspreet opens the read-only visibility dashboard, reads the KPI tiles, spots a short line, sees that timekeeping is already working it, and hands off to SSRS for forensic detail. 5 steps.
Edge cases
TTS spread job — Maria handles a spread-flagged order: one employee activity is keyed once and allocated across multiple shop orders by shop-order line hours. 4 steps.
Hand-packer units (job 0055) — Maria captures the piece-rate unit count alongside the activity so payroll continuity is preserved. 3 steps.
Where this fits in the bigger picture
- The full proposed solution brief is at Proposed Phase-One Solution For Ryan Review.
- The architecture, workflow, role, and TTS-spread diagrams are at Future-State Solution Diagrams.
- The two-workshop plan is at Stakeholder Workshop Plan - June 2026.
- The system-of-truth boundary, validation rules, and pilot scope are described in the proposed solution brief and the As Is vs To Be page.
What this demo is not
- Not a commitment to a specific visual theme, icon set, or commercial component library — those are downstream UX decisions.
- Not a final PRD — workflows and rules shown here are still subject to workshop validation.
- Not a Kronos/timekeeping replacement — phase one keeps employees, schedules, punches, pay codes, and meal/missing-punch behavior on the existing timekeeping system.