Why VP Project Management Uses P3M Engine
Larger enterprises with robust program and project management operations have two needs that tend to be in opposition to each other.
· PMO Flexibility - An enterprise may have multiple PMOs and each PMO may run multiple programs. Each PMO and program should have the flexibility to tailor their governance to their specific environment and needs. To accomplish this, each PMO or program typically needs a different instance of PMIS (Program Management Information System) software.
· Enterprise Consistency - It is important to be as consistent as possible across the enterprise so all reporting can roll up to the enterprise and performance comparisons can be made. It is important for PMOs to be able to share information with other PMOs. To accomplish this, you typically place all on a single instance of PMIS software.
You cannot have both. If you provide flexibility, you sacrifice consistency. If you enforce consistency, you give up flexibility. But not anymore. P3M Engine has solved that problem.
P3M Engine enables each client to tailor P3M Engine behavior through a new concept called Layered Configurability. Through Layered Configurability, each layer of your program and project management organization (enterprise, PMO, programs) can configure P3M Engine and their processes as needed and manage the capability of the downstream layer to configure their processes. This will provide the flexibility of tailored governance and processes wanted by each part of the organization while giving each layer the consistency needed to facilitate cross-communication and upward reporting and analytics.
Security and project health configurations are available only at the enterprise level. This will support consistency and communications across the enterprise. The remaining configurations are available at all levels.
Over 120 items are configurable in P3M Engine. Here is a summary look.
Login and password security is configurable at the enterprise level.
Health Rules are configurable at the enterprise level, including:
·Scope
·Schedule
·Cost
·Resources
·Colors
·Issues
·Risks
·Actions
·Decisions
·Status Reporting
Operational and process parameters are configurable at all layers:
·Project
·Work Hierarchy
·Logs
·Change Control
·Reviews
·Communications
·Risks
·Issues
·Resources
·Status Reporting
For more information see http://www.p3mengine.com.










