What is it: Define, draw and narrate the system's standard Processes and store them in a central repository. Deploy them at Project start and then identify and define the distinctive Business Processes that make the client's organization truly unique and competitive. Map out specific steps in this valuable process visually

Why do I need it: Instead of starting from scratch on every Project, get a head start and save hundreds of hours of effort by using your best-in-class system Processes that you have already defined. This also allows you deploy In-Scope processes from the SOW and then flow that into the project so that Team Participants are only occupied with scoped work.

What is it: Define granular Business Process Steps as part of the Business Process. You can then associate to that Step content like Issues, Activities, Requirements, Test Scripts, SOP updates and more.

Why do I need it: Very granular process definition. Associate Process Changes, Activities, Questions, Tests, etc. at this level for exceptional process definition and control.

What is it: Organizational Change Management can be monitored in CCP. You can create, plan and manage changes that may impact specific aspects of the organization like culture, job security, process change, etc. You can create a Storyboard to describe the change and use this content with the Communication Plan functionality to effectively share upcoming change.

Why do I need it: Allows you to be pro-active in addressing organizational change and significantly reduce the risk of users not participating in the project or not adopting the new processes and systems.

What is it: Upload the cient's current SOP documents into CCP. As existing processes are changed, track SOP changes for updates and approval. When SOP's are completed, download the SOP's back into the client's SOP repository on cut-over. As you progress through the project you can use CCP to identify SOP’s that will require updates to ensure that all SOP’s are updated before go-live. Also provides complete traceability back to the Business Requirement.

Why do I need it: Allows for edits, updates and new SOP's during project without touching the client's existing SOP's. Easily manage the progress of SOP updates and approvals while providing a complete audit trail and version history.

What is it: Identify key decisions that need to be made, like should we use Advanced Warehousing or not, and then assign, track and decide the decision.

Why do I need it: Clearly know who decided what and when. Eliminates down-stream miss-communication.

What is it: If you are a Project Manager, simple question for you. Can you provide real time analysis of all questions being asked by the by business that have not yet been answered by your team?

Why do I need it: If the project uses e-mail no one has any idea how many questions have been asked, by who, when or whether the question has been answered. This functionality solves a huge black-hole in most projects.