Scenario:
A new employee is hired and needs to be registered in the system.
Action:
User enters employee code, name, personal details, and joins information in Employee Master.
Outcome:
Employee record is created and stored in the system.
Scenario:
Employee works from a specific plant, office, or branch.
Action:
User assigns the employee to a location or branch.
Outcome:
Employee is available only for transactions related to that location.
Scenario:
Employee belongs to production, maintenance, HR, or admin department.
Action:
User maps department, designation, and role to the employee.
Outcome:
Department‑wise reporting and responsibility tracking is enabled.
Scenario:
Employee shift, employment type, and status need to be defined.
Action:
User enters shift, employment type (permanent/contract), joining date, and status.
Outcome:
Employee is correctly linked to shifts, attendance, and MES activities.
Scenario:
Employee details are required for attendance, production entry, and reports.
Action:
System fetches employee data from Employee Master during transactions.
Outcome:
Accurate employee‑wise attendance, productivity, and reporting.