{"id":31417,"date":"2021-11-17t11:15:47","date_gmt":"2021-11-17t16:15:47","guid":{"rendered":"\/\/www.deco-dalles.com\/?p=31417"},"modified":"2021-11-17t11:01:40","modified_gmt":"2021-11-17t16:01:40","slug":"expected-finish-in-primavera-p6-speedy-updates","status":"publish","type":"post","link":"\/\/www.deco-dalles.com\/expected-finish-in-primavera-p6-speedy-updates\/","title":{"rendered":"use expected finish in primavera p6 to speed updates"},"content":{"rendered":"
i’d love to see some stats on the average size of a primavera p6 schedule. i’ve never come across any stats, but based on experience and lots of consulting and web-research, it’s pretty clear that today’s project schedules are the chunky big brother to their slim and compact sibling of 10 or 15 years ago.<\/p>\n
schedules are becoming bloated with data. why?<\/p>\n
really, i think we as a society have become obsessed with data<\/strong><\/a>. in the age of big data, we\u00a0feel we should capture as much as possible and track it.<\/p>\n and i\u00a0agree. except our scheduling software<\/a> has no automation to help us manage big project data.<\/p>\n we’re still visiting each activity one at a time and an hand-entering an accurate status update. i know automation is coming. hopefully soon.<\/span><\/p>\n but for now, i believe in the motto:<\/p>\n “saving clicks & keystrokes saves time”<\/strong><\/p>\n i’m not saying less clicking will help your project finish sooner. it will save you time, less clicking, typing in status data and constantly rescheduling in p6 will save you time to do other more important things, like monitor your critical path<\/a>\u00a0or maybe watching 8-wheeler off-road truck videos<\/a>. whatever’s most important.<\/p>\n one thing we can do to save clicks and keystrokes in primavera p6 while performing status updates, is to use the expected finish date<\/strong>.<\/p>\n <\/p>\n the process of updating an activity with status in primavera p6 typically goes like this (note: i’m leaving out updating 世界杯时间比赛时间
& expenses – just the basics of updating dates and % complete here):<\/p>\n the common\u00a0difficulty is figuring out what value to enter for the remaining duration<\/strong>. because the remaining duration is added to the future data date (the new data date you’ll enter after you’ve done your updating), we won’t know the activity’s new planned finish date until after we schedule.<\/p>\n on top of that, we don’t have visibility into the activity calendar – if you’re trying to input a remaining duration that equates to the activity finishing on a particular date, you’ll need to be aware of non-work days in the calendar; another piece of information that makes using remaining duration difficult and cumbersome.<\/p>\n sometimes it’s nicer to just input a date<\/strong>, rather than the remaining duration.<\/p>\n for example<\/strong>, let’s say for\u00a0activity b<\/strong>, you enter 12 days<\/strong> for remaining duration<\/strong>. to know what 12 day remaining translates to as a planned finish date,<\/strong> you need to add 12 days to the new data date – let’s say it is feb 1st. so feb 1st + 12 days = feb 12th<\/strong>. but, what about calendars<\/strong>? it could be easily be feb 14th or 15th or 16th depending on\u00a0whether there are non-working days<\/strong> in that period on the calendar.<\/p>\n so many p6 users (me included) find that using remaining duration is really a bummer<\/strong>, unless you’re working with a short remaining durations, like 1-5 days. if the remaining duration is small, then the calculation is trivial and doable.<\/p>\n what if there was a better way than having to figure out and record how many days are remaining on an activity?<\/p>\n\n
\n
\n
using expected finish<\/span> in primavera p6<\/h2>\n