Creation of program (multiple projects) , and enterprise (one per instance), where sites would be created and risks and issues, along with OLAP/Reporting could auto roll up to a customers alignment.

i.e. The same way projects can have sub projects, but without the embedding of the projects them selves. Designated 'Portfolio' pages would automatically have a different sharepoint site template, allow for high level risks and issues to be managed, and have automated dashboards for showing high level cost and schedule metrics, across a group of projects. The highest level, would then be the enterprise, where all programs, risks, and issues roll up for executive visibility.

If an organization wants to be able to manage their resource capacity with PPM then they should be able to register not project related work and see the impact of this not project related work on their resource capacity. (see attached screenshot)

PPM currently has the so called “administrative” tasks for registering not project related work. But work registered on administrative tasks is not taken into account for the calculation of remaining resource capacity. You would expect that the administrative tasks (Work Type: Working) behave the same as project related work when it comes to resource capacity. But unfortunately they don’t, they behave quite different. It would be very nice if administrative tasks (Work Type: Working) would behave in the same way as project related work when it comes to resource capacity. This work should show up in the capacity report even when it is only planned and users should be able to fill the planned line for this kind of tasks in their timesheet (the is currently possible for administrative tasks and should stay possible) (see attached screenshot).

Project status Active, Complete, Cancelled

When a project is active it show up on project center. When its complete or cancelled, an archive option now let us archive the project in a specific place witch project manager can access for consulting and lessons learned. Its not on project center anymore, and the same happens eith the project site and other data like issues and risks that belongs to the archive project.

When a project is cancelled and it's not 100% yet (example: you cancel a project around 40% complete). You can archive the project with a cancelled report saying what happened and, MOST IMPORTANT, the resources allocated ahead (the last 60%) will be free to next projects allocation from that date.

When a customer implementation requires replicating of PWA data to a SQL Server database it's fairly easy to get the project data by using Integration Services and the e.g. the projects OData feed. This feed contains custom fields and the lookup table values selected on a project, but it's not possible to get further details on the selected lookup table item.

It should be possible to read lookup tables and lookup table items (incl. level, value and description) in an OData service. Further it should also be possible to map a selected lookup table value on a project (or other entities) with the lookup table item in order to get the item description and level.

Example: A lookup table contains a list of product areas where the lt item value field represents the product area name and the lt item description field represents the product area number. The value has been selected on projects. Then in the reporting it's possible to filter projects on product area numbers and integrate with LOB systems by using the item descriptions.

PMs often change 'Start' and 'Finish' dates for tasks accidently which, in turn, applies scheduling constraints to tasks. This often introduces confusion and complexity into a schedule.

Instead I suggest that 'Start' and 'Finish' columns for 'Auto scheduled' tasks be made read only. (if you want to adjust dates, use manually scheduled tasks).

If a PM wants to impose fixed date (my means of a Scheduling Constraint) they could double click on the task and from the advanced tab of the Task Information apply a scheduling constraint from there.

I understand that this is a significant paradigm shift for Project but this is the next step since introducing 'Manually scheduled' tasks (which in my opinion should not be the default within Microsoft project, as this sends new, untrained users down the wrong path to scheduling greatness). If Apple can remove the earphone Jack, Microsoft can do this!