2 Replies Latest reply: Oct 26, 2009 9:51 PM by 714929 RSS

    Minimizing confusion w/ different data dates for subprojects in P3?

    726923
      A vendor has decided to schedule his project using subprojects, and claims that it is acceptable practice to use different data dates in each subproject. Each subproject has a different project start date, so the start dates for activities without predecessors are set by the subproject start date. I believe the use of different data dates in each subproject leads to confusion and potential errors when the subprojects are viewed in entirety (i.e., view the whole project group). I'm hoping the vendor will see it my way, but if not, what practices should we insist on to prevent confusion and errors?
        • 1. Re: Minimizing confusion w/ different data dates for subprojects in P3?
          728280
          they could have thenm all in one schedule and use early start constraints to hold the start of the subcontracts to their respective start dates
          • 2. Re: Minimizing confusion w/ different data dates for subprojects in P3?
            714929
            I'm doubtful that P3 would allow differing data dates in each sub-project, once viewed as one master project. Have your Vendor try it and see if it's even feasible. Your vendor's position may be a self-correcting problem once he tries and fails to put differing data dates into one project.

            Your data dates are really the date that your schedule is updated. My current contract ( for example ) requires schedule updates submitted on the 25th of each month. I imagine your vendor is going to be updating all of his sub-projects at the same time each billing cycle. Does this give you the contractual tool you need to insist on the same data date for each sub-project?

            Each sub-project can have a different start date ( either as-builted, constrained, or otherwise) but the data date should always be the date of the update.