Understanding Implementation Projects

Implementation projects comprise PeopleSoft product suites or business processes and their underlying products and features that you have chosen through the Manage Implementation Projects pages.

Regardless of whether you choose to make your implementation projects selections from a business process or a product perspective, Setup Manager displays the supporting data to the feature level. Only installed products and their related business processes are displayed on the page for selection.

You begin by selecting an implementation method—either by business process or by product—that influences how the underlying features are presented to you. The strategy of selecting an implementation method is determined by the way in which you've structured your implementation project team or your implementation project. For example, consider whether you are replacing or improving a specific business process such as Order to Cash, or planning to implement specific PeopleSoft modules. You and your implementation team need to assess your company's needs and choose the implementation method accordingly.

From the Product Summary page or the Business Process Summary page, you can see your feature selections displayed relative to the products or business processes that they support. For example, if you are implementing a group of PeopleSoft product suites or products, you can check the Business Process Summary page to see what business processes you are supporting based on your feature selections. At that point, you might determine that you have a business process partially implemented, which might influence whether you elect to implement the entire business process using Setup Manager.

After you select the products and business processes for the implementation projects, save it with a unique name.

Multiple Projects

You might want to generate more than one implementation project to support various implementation scenarios. For example, to perform a phased implementation, you can create a implementation project for each implementation phase. Or, you might also want to create different implementation projects to investigate the effect of selecting a particular set of features. You can also create different implementation projects to support different teams working concurrently on different functional areas. For example, you might have a team working on modules such as General Ledger and Accounts Payable while another team works on Order Management and Billing.

In summary, you can create multiple implementation projects that reflect different implementation scenarios. For example, you can create implementation projects that are specific to different phases of an implementation, or you might want to examine the effect of implementing different combinations of products and business processes.