Shift Logic Conversion in VB.NET
Budget: ₹600 – ₹1,500 INR
I have an in-house VB.NET application backed by SQL Server 2008 R2 that currently schedules four 6-hour shifts per day. Operational changes now require three 8-hour shifts instead.
The change touches two main areas:
• Business logic – all routines that build the daily roster, assign staff and calculate shift boundaries work off the 4 × 6 model.
• Database structure – several tables store fixed shift identifiers, start / end times, and downstream references that assume four records per day.
Because the scheduling and allocation algorithms drive time-sensitive workflows, any adjustment must keep existing calculation accuracy intact. The user interface itself can stay as is; only back-end logic and schema need attention.
What I need delivered
1. Updated VB.NET code that:
• Replaces hard-coded 6-hour intervals with a configurable shift length setting (default 8 hours, 3 per day).
• Preserves current scheduling features such as staff auto-assignment, overlap handling and validation checks.
2. SQL scripts to:
• Modify or migrate the shift definition tables to support the new pattern.
• Update related constraints, stored procedures or views so reports and exports still balance.
3. A brief migration guide outlining steps to deploy the change to production and roll back if required.
Acceptance criteria
• A test dataset processed through the new logic shows three correct, non-overlapping 8-hour shifts totaling 24 hours.
• All existing scheduling screens load without error and reflect the new shift boundaries.
• No regression in performance or data integrity when running on SQL Server 2008 R2.
All development must stay within the current tech stack (VB.NET, .NET Framework as presently used, and SQL Server 2008 R2). Source control access and sample data will be provided once the approach is agreed.
The change touches two main areas:
• Business logic – all routines that build the daily roster, assign staff and calculate shift boundaries work off the 4 × 6 model.
• Database structure – several tables store fixed shift identifiers, start / end times, and downstream references that assume four records per day.
Because the scheduling and allocation algorithms drive time-sensitive workflows, any adjustment must keep existing calculation accuracy intact. The user interface itself can stay as is; only back-end logic and schema need attention.
What I need delivered
1. Updated VB.NET code that:
• Replaces hard-coded 6-hour intervals with a configurable shift length setting (default 8 hours, 3 per day).
• Preserves current scheduling features such as staff auto-assignment, overlap handling and validation checks.
2. SQL scripts to:
• Modify or migrate the shift definition tables to support the new pattern.
• Update related constraints, stored procedures or views so reports and exports still balance.
3. A brief migration guide outlining steps to deploy the change to production and roll back if required.
Acceptance criteria
• A test dataset processed through the new logic shows three correct, non-overlapping 8-hour shifts totaling 24 hours.
• All existing scheduling screens load without error and reflect the new shift boundaries.
• No regression in performance or data integrity when running on SQL Server 2008 R2.
All development must stay within the current tech stack (VB.NET, .NET Framework as presently used, and SQL Server 2008 R2). Source control access and sample data will be provided once the approach is agreed.