Each worker is modeled as a unary resource. Since the timetable information is of interest, timetable constraints should be explicitly added on these resources. The requirement that every worker has a two day break every five days is stated by setting a breaklist on each resource. In addition, each customer request is characterized by the team which manufactures the requested product and by the date on which the team can start working on that product (we call that date the release date of the request).

This data can be easily translated into new activities and constraints as follows: For each team member a one day activity requiring the corresponding resource is created and all these activities are constrained to start after the release date. In addition, precedence constraints are added between these activities, according to the description of the manufacturing process of the product (in this example we suppose that both types of products impose the same precedences between activities). The solution of the request, the delivery date communicated to the customer, is represented by the end of the last activity in the manufacturing process.