Expand the reporting database (ODATA)
Expand the reporting database to include key schedule data (e.g. predecessors, etc). These data are not readily accessible with PWA and could be used to create user-authored schedule audits.
-tracking the number of cross-project predecessors in an indirect measure of organizational collaboration, would help to market the value of PWA
-identifying schedules with complex predecessors (e.g. SF) and lead/lag is useful to building more robust project schedules
Trutz-Sebastian Stephani commented
We require also the resource cost rate table information per resource (timephased) as well as the assigned cost rate table on the assignment level (non-timephased).