I inherited a project template which buffers YEARS on with end of the project tasks, and for the life of me, I can’t seem to figure out where this buffer is coming from (project starts in 1984 (first task started a month ago), and ends in 2034 (last task ends in 3 months).
I’d prefer to not have to rebuild this template -especially not if this may happen again as we use this template for quarterly projects and has over 100 tasks across a half dozen teams.
I’ve verified all predecessors, resources and lag days from all tasks. I even removed all resources and moved the project date a month to see if it would recalculate the start/end date of the project. No luck. All tasks -except the first task are auto scheduled.
Related
Description
While importing the XML in MS Project then the start and finish dates get changed.
Please find the dates in XML
Start and end date in XML
Please find the MS output
MS Project output
Get the XML file from here https://github.com/VigneshRameshh/GanttIssue
Help me to find the reason behind this?
Thanks in advance,
Vignesh Ramesh.
There are several factors that are affecting this.
The calendar that is applied to the project in the XML is the project's "Standard" calendar. This calendar only has 8 hour working days Monday-Friday, starting at 8:00 and ending at 17:00.
The amount of minutes of working time per day is set to 480, which is 8 hours
The task is Auto Scheduled, not manually scheduled (the value would be 1 if it was manually scheduled).
Given those parameters, MS Project cannot have the start of the task begin at 10/22/21 00:00 and finish on 10/23/21 00:00. Because the task is Auto scheduled, it must follow the Project's calendar and hours per day requirements. Therefore MS Project will start the task at the earliest point on 10/22/21 (8:00) and follow the 1 day duration applied to it, which will cause it to end on 10/22/21 17:00.
Note - it is not recommended to have tasks set to be Manually Scheduled. You want your tasks to be set to be Auto Scheduled.
The app works fine locally and is basically just for plotting data - very little to no math/processing is going on. The Shiny input fields just filter a data.frame by date and a handful of other attributes like location, observation type, etc. -- for daily numerical values originating in .csv that go back to Oct '16 that amount to a seemingly manageable ~0.25 gb. The default begin and end dates for the filtering are both in April '19, and the online app filters (by filter()) and plots that about month of data correctly on start up, and works fine looking back several days or weeks too.
However, if I extend the start date back by multiple months or years (say for example 10/15/16 to now instead of just the past month), the io version pretty abruptly yields "disconnected from the server". It seems I need to relax a setting or devote more resources to something else, but just a guess.. any ideas?
If feeling extremely helpful or curious - here's the working app in one ~40 mb zipped folder along with the app.r, and all the data, and the libraries used specified in libs.r
timeseries app
in summary the app works fine locally, but only for short time series ranges in io. The full data set goes back to 2004 for ~2gb. Ideally I'd like to find a way to have all those years queryable from the io app with decent app performance.
I have a Control-M job that runs every 20 min. Everything works great during that day's run. The issue is when we auto-order the next days jobs. If the current day's jobs are running we get 2 copies of the jobs running at the same time.
Is there a way to not start the new job if the previous day's job is executing?
The job starts every 20 minutes, but how long does it run? Set the end window for "submit between" time a few minutes before the new day build.
Let's say your new day builds at 0400. Since the job is intended to run every 20 minutes, you can have it run as late as 0340. Set the "to" time in Activity Window to 0340 and the job won't autosubmit after that time. The new day will build at 0400 and the new version of the job will start then - 20 minutes after the previous start.
You can also add a control resource to the job to prevent two of them from running at the same time. I don't know another way to do it. That's not a can of worms I'd open unless the activity period settings just won't work the way you want them to.
If you're referring to last day's job execution bleeding into current day, causing resource contention, your best bet (as Rob pointed out) is to define a resource with max count of 1 to be required by the job, so next day job instance cannot start until prev day job completes and release the resource. Alternatively you can have the job post a Condition for order date + 1, and have order date condition also be an In condition for the job.
I have a project completed in MS Project but I made an error on the start date. How do I change the start date to another date so that all other dates automatically change? I tried just changing the start date but the other dates will not change?
Have you specified Predecessor links between the individual Tasks? If so, you can simply change the Start of the first Task and all the others will move. If not add Predecessor links between the tasks - even if they're just to set them all to the same Start (e.g. if you want the Task in Row 4 to start at the same time as the one in Row 3, enter 3SS in Predecessors for Row 4). Then change the Start of the first Task; the rest will move and the Project Start will also be automatically updated.
If your tasks are all "automatically scheduled" then moving one task to a later date should automatically move the others. If your tasks are "manually scheduled" then they won't automatically adjust. Switch all tasks to "automatically scheduled" and it should fix it! ^-^
All the best!
Matthew
We're currently using MS Project for an exercise relating to an exam paper. We have to plan out the writing of this paper as a project and report to our lector once a week. This week we're ahead of schedule and and have completed a few tasks that arent planned untill next week. The problem is that when creating a report for earned Value, BCWP for these task is the cost of the hours used, not the hours budgetted for the work.
For instance:
We completed a task that was supposed to be started and completed monday and was baselined at 12 hours, yet we completed it in 8 hours today (thursday). The cost is set at 100$ per hour.
How I see it, the values for this task should be BCWS=0, BCWP=1200 and ACWP=800 yet for some reason it does not recognize the BCWP and ACWP when showing the EV-report. They both show up as 0. I cant change the task to having been performed today either. Can anyone tell me what went wrong?