Mt Olive Staffing & Activity — Solution Walkthrough

Prepared by Pruvida for Mt Olive Pickle Company.

This walkthrough presents the proposed phase-one Staffing & Activity-Tracking application as it currently stands in discovery. It is intended for HR, production staffing leads, production supervisors, timekeepers, and IT & reporting stakeholders ahead of the solution-design workshops.

The goal is for everyone in the room to leave with the same picture of how the application would feel in day-to-day use, what it owns, what it deliberately does not own, and which decisions still need stakeholder input — before we lock the PRD.

How to use this walkthrough

1. Pick a use case below.
2. Open its index page to meet the user and read the scenario.
3. Click Next at the bottom of each step to walk through the workflow.
4. Use the Use Case Index link in the footer to jump back to the use case's start, or Demo Home to return here.
5. Click any illustration to open it full-screen at high resolution.

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 at this stage 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

Use cases

Core workflows

1. 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.

2. 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.

3. 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

4. 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.

5. 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 walkthrough is not

• Not a commitment to a specific visual theme, icon set, or commercial component library — those are downstream UX decisions and will be revisited with Mt Olive's IT and design preferences in mind.
• Not a final PRD. Workflows, validation rules, and scope shown here are the current proposed design and remain subject to workshop validation.
• Not a Kronos / timekeeping replacement. Phase one is a staffing and activity-tracking application. Employees, schedules, punches, pay codes, and meal / missing-punch behavior stay on the existing timekeeping system.