By Jeffrey McDaniel on Feb 05, 2013
The following blog is around the P6 Extended schema and covers some general topics related to settings that affect the P6 Extended schema services. Because the P6 Extended schema is the data source for P6 Analytics understanding how it works and it's settings are important to having a successful P6 Analytics implementation. The Extended schema applies for all P6 Reporting Database versions 2.2 and higher and P6 Analytics 1.2 and higher. If the data is not in the Extended schema it will not end up in P6 Analytics.
What causes a project to get published?
- Automatic publishing
Projects are automatically published when a user right clicks on project in P6 and choose publish now. Next time the project service runs this project will
be added to the queue. Some operations could cause an internal update of fields on the project level that cause the same affect and force the project into the queue on the next project service run.
- Crossing threshold '# of changes exceeded'
- Crossing threshold 'time since last publication exceeds' and has had a change since last threshold period
Where are the threshold counts being tracked?
- Based on the threshold settings when crossing a certain number of changes the project is added to the queue to be published.These changes are calculated from changes on activities in the project, wbs level for the project, resource assignments on the project, and relationships on the activities. Changes in these areas will be added up in an internal table in the PMDB until it crosses the threshold of changes or the threshold of time has been crossed for projects with changes. At either of those times the project is added to the queue for calculation.
What needs to occur for a new project to make it into P6 Analytics?
- The project must be created, enable publication set. The project must be published. After project has been successfully published the Security global service must be run to calculate security on the project. Naturally over the course of a day the global services are run and this process is taken care of, but if you need the new project immediately you must run this Security global service after publishing the project. When you have confirmed all these processes have occurred run the StarETL. At this point the project should be in the Star database and available for the P6 Analytics application in OBI.