The day when the contract becomes effective is known as the effective date (or contract effective date), which may be different from the execution date. So, what is the effective date of a contract? However, this isn’t necessarily the same day the contract comes into effect. It’s when both parties agree to terms and conditions as the contract outlines. The execution date is the day both parties sign the contract. What is the execution date of a contract? To understand the difference between signing a contract and a contract coming into effect, there are two terms that are important to know: effective date and execution date. It’s a common misconception that a contract becomes valid the day it’s signed. Your thoughts? Please email me with any comments or questions.Have you ever signed a contract and then wondered when the terms of the contract become enforceable? For many of us, the answer to this question is probably “no”. In the screenshot below we can see the time period settings for just one calendar:īy making the hours per day in the time periods for this calendar match the hours per day in the calendar itself then P6 will properly understand what is considered to be a normal work day. These time periods are calendar-specific. Under Enterprise, Calendars, there is an option to specify time periods. “Use assigned calendar to specify the number of work hours for each time period.”Ĭhecking this box is real important because it allows us to use the hours per day in our calendars rather than the global hours per day under Admin Preferences. Note that right under the time periods in the Admin Preferences there is a box with the following phrase: Nevertheless, we are real close to a solution. These are Admin Preferences, and not User Preferences.
![hr dates dont match hr dates dont match](https://www.researchgate.net/publication/330933252/figure/fig4/AS:959304182013965@1605727348991/Workflow-of-the-analytical-strategy-carried-out-for-the-identification-by-untargeted.png)
![hr dates dont match hr dates dont match](https://media.cheggcdn.com/media/862/86225234-a784-4fac-baff-f7e26aa633f8/phps5mZWy.png)
This solves the problem of P6 thinking that anything in excess of 8 hours per day is overtime, but it also changes the settings of every schedule in the database. We can change the time units under Admin Preferences to show 10 hours per day. Under Admin, Admin Preferences, Time Periods, the hours per day, week, month and year can be specified.
![hr dates dont match hr dates dont match](https://static.helpjuice.com/helpjuice_production/uploads/upload/image/3504/direct/1589225191106-2020-05-11_15-25-45.png)
Now, savvy P6 users know that the hours per day can also be modified somewhere other than in the calendars. While this figure can be changed later on, the initial budget will be based on 8 hours per day regardless of the calendar settings. This can be confirmed by adding a labor resource and watching what happens to the budgeted hours. By working 10 hours per day, my crew worked 40 hours in 4 days. Why? Because P6 assigned an imaginary budget of 40 hours to my task based on a normal 8-hour day.
![hr dates dont match hr dates dont match](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/time/edge_time.png)
I assigned this calendar to an activity with a 5-day duration. The work day starts at 7:00 am and ends at 5:00 pm (this allows for no lunch break but my theoretical crew is a bunch of really hard workers!). This results in activity dates not calculating as expected. In the following example, I created a 5-day calendar with 10 hours per work day, Monday through Friday. P6 defaults to 8-hour work days, as we will see in a moment, and interprets anything more than 8 hours as overtime. There is a potential problem, however, when specifying more than 8 hours per day for activities. Most Primavera P6 users are familiar with setting up and modifying calendars.