Hi Larry,
Definitely opening the Published version from the Server and it is pulling in the correct status date. However i ran a test with the project scheduler to update a specific line in the sub-project (working version).
When I open the published program master file the updated working file info came across..
My understanding was that the Reporting Data store (published) is completely separate from the working files and that the publish function moves a copy of the working files to the reporting database and SharePoint interface.
Feeling confused and thats a good effort as I’ve been working in PWA on large programs for a long time as Senior PM and Program master Scheduler….
Richard
Couple of points for consideration.
1. I have 7 integrated (hard Linked) sub-projects in the Program. Total line count across the program is approx 15k lines
2. I have enterprise level outline codes to group the critical path activities cross projects within the program so that I can open up the master and subprojects and Run a high level gantt view. (design,build,Unit Test, System Test, SIT UAT OAT, Training, DATA load, Environment Prep, Go- live etc)
3. the Sub-projects all update working schedule through COB Wednesday nights. I open Program schedule (Master and subs) on Thursday to review impacts to program timeline and then Publish the program to the portfolio. I then run all time line and exception reports Thursday afternoon and Friday morning.
This week one the project schedulers jumped into a “working” schedule early Friday morning and made changes to the sub-project. When i re-ran a report from the published schedule to change gantt bar colour (blame the boss) I identified a significant slip to the timeline dates.
This highlighted that the Program master schedule (published to PWA) is loading information from the Working schedule (non-published).
I’ve never come across this pollution of the published schedule with info from the working schedules.
We use the PWA Test server for scenario analysis and What Ifs.
We use the deliverable functionality of Server and hyperlinks to Change requests and Sharepoint based Risks and Issues and document repositories.
