军衔: 三等兵
财产:
经验:
魅力:
来自: 上海市
鉴定: 本功能已经被关闭
发帖: 14篇
注册: 2001-11-26

--------------------------------------------------------------------------------


大家一直在讨论项目的管理，或如何管理项目，如何使项目顺利达到项目的最终目的。
但我不知道大家在项目管理的过程中，是使用什么工具或手段来管理项目的，是否都在使用MSPJ/P3/Excel或其他工具（我曾经测试过邦用P2及同济大学的工程项目管理工具）。

不知大家是否有这样的困惑：我的MSPJ的项目计划和P3的项目计划无法共享，也无法被其他的项目经理使用，他在使用邦用P2。

另外我经常听到有人要开发项目管理系统，或针对一个大型的项目开发适合本项目的姓名管理系统，那么下面的信息就非常重要了，

基于项目管理系统的XML标准已经在规范过程中了，目的使对于项目的所有元信息[如：Task,Budget,Resource,ACWP, BCWP等]范化，使得项目信息对于所有的项目经理，不管使用何种项目管理工具都能识别。

[欢迎大家来讨论项目管理系统的XML规范]：下面一一贴出。

The Standard
The PMXML standard is a data definition for project management systems. The PMXML Consortium maintains the standard. PMXML was originally created by Pacific Edge Software Inc. in 2000 and published at BizTalk.Org. Meanwhile other vendors (i.e., Primavera Systems, Welcom, eProject.com, Great Plains, PlanView ...) joined the initiative.

PMXML could be an important step for the PM industry, following initiatives in other industries to provide integration mechanisms on application-level. Project mannagement systems that are PMXML-enabled allow to distribute data easily inside organizations and between different organizations and their respective management systems. The standard can help vendors, who don't have to implement so many different import/export filters, and it can help the users, who can transfer PM data to other systems (e.g., HR, ERP) or share it with partners more easily.

A standard that allows easy sharing and transfer of project management data could help to bring project management out of its relative isolation in comparison to the line management. PSA applications are trying to do this for enterprises, but a standard that could be implemented by most PM systems, especially the smaller ones, could improve the situation on a much greater basis. This would help with the integration of project management into the broader business context in a more and more project-oriented world.

So what is there? Compared with other integration standards PMXML is in an early stage of development. Created in 2000, Pacific Edge Software just published the second version in March 2002. Publicly available are just the XML schema definitions, as an XSD file or as a commented HTML file.

From an outsiders point of view the PMXML standard currently seems to be a pure data definition. Messaging or relations to other standards, especially to the broader integration standards, like ebXML, that could help to embed the project management activities into the broader business processes between organizations, are not publicly available.

In short: PMXML is defined and built-in into some systems, at least at Pacific Edge Software and Primavera Systems, but there is not much information about its details, the goals and timelines for its further development. So, if you need an integration standard like PMXML for portfolio management in your own organization, or as a mechanism to share information between partners, ask your vendors about their support for such standards and keep an eye on the further developement of PMXML.

The Standard
The PMXML standard is a data definition for project management systems. The PMXML Consortium maintains the standard. PMXML was originally created by Pacific Edge Software Inc. in 2000 and published at BizTalk.Org. Meanwhile other vendors (i.e., Primavera Systems, Welcom, eProject.com, Great Plains, PlanView ...) joined the initiative.

PMXML could be an important step for the PM industry, following initiatives in other industries to provide integration mechanisms on application-level. Project mannagement systems that are PMXML-enabled allow to distribute data easily inside organizations and between different organizations and their respective management systems. The standard can help vendors, who don't have to implement so many different import/export filters, and it can help the users, who can transfer PM data to other systems (e.g., HR, ERP) or share it with partners more easily.

A standard that allows easy sharing and transfer of project management data could help to bring project management out of its relative isolation in comparison to the line management. PSA applications are trying to do this for enterprises, but a standard that could be implemented by most PM systems, especially the smaller ones, could improve the situation on a much greater basis. This would help with the integration of project management into the broader business context in a more and more project-oriented world.

So what is there? Compared with other integration standards PMXML is in an early stage of development. Created in 2000, Pacific Edge Software just published the second version in March 2002. Publicly available are just the XML schema definitions, as an XSD file or as a commented HTML file.

From an outsiders point of view the PMXML standard currently seems to be a pure data definition. Messaging or relations to other standards, especially to the broader integration standards, like ebXML, that could help to embed the project management activities into the broader business processes between organizations, are not publicly available.

In short: PMXML is defined and built-in into some systems, at least at Pacific Edge Software and Primavera Systems, but there is not much information about its details, the goals and timelines for its further development. So, if you need an integration standard like PMXML for portfolio management in your own organization, or as a mechanism to share information between partners, ask your vendors about their support for such standards and keep an eye on the further developement of PMXML.

The Data Definition
The PMXML data definition, version 2, contains definitions for four major project management data types and some minor ones. The four major data types are: project, resource, task, and assignment. The definition starts with a ProjectManagementSchema as a root element. It contains

InstanceData, a collection of user- and application-specific data;
PoolResources, a collection of resource definitions;
Projects, a collection of project definitions.
Figure 1. ProjectManagementSchema

The InstanceData element is collection application-specific data that helps to interpret the project management data. It contains fields such as user ID and name, application name and version, and used schema version.

PoolResources is a collection of resource objects. These resource objects define material or working resources. They contain:

Name and address data
Cost data (rates, overtime cost...)
Availability data
Plan and baseline data
Actuals
Metrics (ACWP, BCWP...) and variances
Customization and extension data
Defined currency units are US Dollar, Deutsche Mark, Yen, Euro, British Pound, and Swiss Franc. See Resource Definition for a complete resource definition.

Projects is a collection of project objects. A project comprises:

General data (name, company, status date...)
Definitions for calculations (hours per day, days per month...)
Plan and baseline data
Actuals
Metrics (ACWP, BCWP...) and variances
Customization and extension data
Resources (actually two collections, one for all resources, one for al local resources)
Tasks
Assignments
See Project Definition for a complete project definition.

The remaining two major types, task (see Task Definition) and assignment (see Assignment Definition), are structured similarly. Besides the usual groups for plan, baseline, actual data etc. the task definition contains attributes to define a milestone, a summary task and completion status. The assignment repeats also the plan, baseline etc. data group and adds the IDs for the task and its assigned resources.

Note that many attributes in the mentioned definitions are optional. So the actual processing may need to know which application saved the data and why it omitted or added certain data fields.