PPMS Interface to MSP

 

Overview

 

Built around a database, PPMS is a high performance multi-project management system which can also be used for rapid and simple planning of individual projects. Where it is desired to use both MS Project and PPMS, the two systems can be integrated with the help of the optional component PPMS-MS Projec tLink.

 

Experience shows that companies make use of various project management systems. To achieve company-wide project management in spite of this often requires that the various systems are integrated or exchange data.

 

In numerous organizations, MS Project is already established for the purpose of generating local date objectives for individual projects. In order to effect uniform date tracking, resource management, cost control or to make cross-project analyses, professional multi-project management systems such as PPMS are used.

 

Your advantages

 

·         Integration and use of existing project management software

·         Use of the respective strengths of MS Project and PPMS

·         Organization-wide planning of dates, resources and costs, including where different project management systems are used

·         Flexible forwarding of project information

 

Notes on the integration

 

PPMS and MS Project are based on different project management philosophies. As a result, when both systems are being used certain restrictions must be observed. The most important differences are:

·         Duration: MS Project permits durations of less than 1 day. Da dies in PPMS die kleinste Einheit ist, muss bei einer Integration die kleinste Dauer der Tag sein.

·         Structure of the tasks in a project: In MS project there can be up to 12 levels, in PPMS there is no restriction.

·         Links to tasks in other projects

·         Multiple links between the tasks

·         Maximum conditions for links

 

Scenarios

 

To permit an exchange of data between PPMS and MS Project, various scenarios can be implemented using PPMS MS Project Link.

 

Scenario 1:

Project data is copied from MS Project to PPMS, to permit the generation of summaries of the dates for projects and tasks, for use by management in monitoring dates and progress. The display takes the form of barcharts, which reflect the hierarchical structure of the projects. There is no need for rescheduling in PPMS.

·         To effect this, the MS Project users export their project data to PPMS. There is no need for any feedback of the data to MS Project.

·         Because PPMS utilizes more comprehensive planning strategies, any replanning may produce different results. The dates calculated by MS Project are retained for comparison purposes.

 

Scenario 2:

The project data is copied from PPMS to MS Project, where it is broken down into sub-projects corresponding to the different execution phases. This procedure is encountered particularly where the projects are complex.

·         For this purpose, the PPMS users export their project data to MS Project. There is no need for any feedback of the data to PPMS.

·         Scenarios 1 and 2 do not permit any cyclic interchange of data. Any changes will be lost when the data is fed back.

 

Scenario 3:

The project data is copied from the operating level in MS Project to the strategic level in PPMS, from where it is fed back to MS Project in order to update the project data there. A cyclic exchange of data takes place until the project comes to an end.  

·         MS Project users and PPMS users can export and make use of the project data.

·         The project data which can be exchanged between MS Project and PPMS comprises the data about the project, tasks, task texts, resource assignments and links. Calendars and resource availabilities are not exchanged.

It is not possible to exchange the project data in its entirety because, although it is possible to adapt PPMS so that all the MS Project fields are supported, MS Project does not support all the fields required for the enhanced functionality of PPMS.