Defining Working Hour Constraints for Machine Scheduling in Google OR-Tools

[KR Prasath]

Hello everyone,

I'm currently working on a project using Google OR-Tools for machine scheduling, and I need help defining a constraint related to working hours for machines. Specifically, I want to ensure that tasks are scheduled within the working hours of a machine and account for cases where a task might span across multiple working days.

Here's the scenario:

Machine working hours are from 8 am to 5 pm.
Let's say I have a task that starts at 4 pm and has a duration of 2 hours.
I want to ensure that 1 hour of this task is completed on the same day (between 4 pm and 5 pm) and the remaining 1 hour is completed on the following day, starting at 8 am and ending at 9 am, before starting the next task.
Could someone guide me on how to define this constraint using Google OR-Tools? I'm particularly interested in how to handle tasks that span across working days and ensure that they are correctly scheduled within the machine's working hours.

Any help or suggestions would be greatly appreciated! Thank you

[KR Prasath]

.

[Alberto Manzini]

Consider time only on machines working times and then postprocess results.

[KR Prasath]

Yes I found an answer but I need that to convert into c#. https://github.com/google/or-tools/blob/master/ortools/sat/samples/scheduling_with_calendar_sample_sat.py