oracle finally admits this is a bug as p6 allows you to delete it and think it is not being used.

and what when an unassigned resource works several hours or days on an activity?

at some point it becomes too much. i use the hands down approach of keeping the details on the payroll records, time cards and job unit costing system. these records complement the schedule i use to plan rather than for an over detailed record keeping via the schedule updates.

this is weird, the software shall allow recording work hours different to as planned. similar to work on saturdays, work on overtime can be different as planned. there must be a way to record true actual and keep true plans.

what happens if using time cards the calendar is 8 hr per day, 5 days a week and the resource worked 10 one of the regular day of the week? i suppose it would get it right, then if direct data entry you shall be able to get it right.

how do you filter/organize for calendars used by activities vs calendars used by 世界杯时间比赛时间 when different?

in this case, you would need to create a calendar that allows weekend work and assign it to those activities. then you can progress the weekend dates as actuals.

regards,

idris

reply

regards,

idris

in the beginning of scheduling , i fix the calendar with working as 5days/week & considering other national holidays.
some of the activities are completed at site on weekends and holidays to recover the delay in schedule.
but , while updating the physical progress in system. system not allowing the actual dates , which we already mentioned as holidays.
kindly advice to update the actual dates in system.

regards,
jyothi

full agreement.

michael,
i’m not debating anything from your comment. global calendars were probably meant to be used exactly as you describe. however, in my experience, too many users have access to edit global calendars, and sometimes no knowledge of the kind of impact they are making. if 50 projects are referencing a global calendar, and some inexperienced user changes that calendar to suit his/her needs ignorant of the 50 projects that are now impacted.
it’s not truly an issue of calendar functionality – it’s an issue of user privileges. we recommend you make a project calendar as a copy of a global. then users are free to make changes to the calendar as they need. the database can handle thousands of calendars.
it sounds like you’ve already been bitten by this privilege issue – since you’ve “locked down” your global calendars. that’s definitely an option i recommend as well. but i start with using project calendars as debunking p6 privileges is another huge time killer.

if the global calendar is appropriate for the project, then why would i tell a user to copy it as a project calendar? i tell them to use the global calendar in the project because that is why global calendars were created by primavera in the first place. this gets away from the archaic 15 year old technology of the old betrieve p3.

here is an example using gac’s. i have an automatic interface that posts data to a single gac. i have nine sites where this gac is used. the interface is a write once where if the field is null, it will write the value, but if it already has a value, it ignores the field. this means the schedulers can in fact change the field value and it does not get over written. before we locked down the user from creating a duplicate project activity code, we had over four hundred duplicate codes of the global code. enough of these and you begin to have performance problems.

the global calendar was the same problem. example, we have a default 7×24 global calendar because we are a 7×24 company working around the clock. before we locked down the project calendars, we had hundreds of duplicate 7×24 project calendars. another is the standard 40 hour week calendar. before we locked project calendars down we had hundreds of those duplicate calendars.

so, because the global calendar can be used in any project at any site and we can name them as standards for our business, why in the world would we allow thousands of duplicate calendars in aggregate, when i can have none or very few unique project calendars that do not rise to the level of voting to create a common approved global calendar?

once all the controls are set up via security, you will see significant reduction in duplicate and abandoned codes, calendars, etc. last is to have one of the admins set up in an access db via read only odbc connection a series of queries to guickly determine if a new gloabal code, calenders, etc has been created by looking at the create dates. check once every two weeks. then the ruthless part – create a corporate p6 configuration controls procedure and in it state the rules for adding a new global activity code, udf, calendar, etc. state that the rules are that all site admins must talk and vote on whether to approves a new one. and that if a new code is discovered and that new code was not appoved by all site admins, then it will be deleted when found.

once all of the p6 configuration controls are in place, you will find life is much easier and p6 does not grow uncontrolled and have hundreds of duplicate codes, calendars, udf, eps codes, and all the other areas schedulers love to add the spur of the moment code only to abandon it in a fews weeks.

good question kristen – in enterprise->calendars, highlight a calendar, the click the “used by” button. you’ll get a list of projects that the highlighted cal is linked to. any project names with a “- b1” are baselines. that should do the trick!