Sizing ProcessHardware During the implementation of LN ensure you select suitable hardware to avoid problems at a later stage of the project. Undersized hardware that cannot be upgraded, or oversized hardware can stop the implementation due to budget problems. Therefore, you must consider sizing carefully during the implementation. Final sizing A final sizing can only be performed if all implementation aspects are known. In a pre-sales situation, there is often only high level information about the usage of the application. In this case, a pre-sales sizing can be done to have an estimate on hardware costs. Sizing verification A sizing verification can be done after going live with the first implementation. With the sizing verification, all assumptions made during the sizing can be verified. If required, the sizing can be adjusted to better support the following implementations. Stress test Performance problems tend to appear shortly before going live with an implementation. It is advised that you perform a stress test shortly before going live, to verify if the actual performance meets the requirements. This table shows the sizing stages and the tools, and the documents or services supporting them.
Steps 1, 3 and 4 are an iterative process. In a pre-sales phase, an initial sizing can be done to determine hardware costs. In an after-sales phase an more detailed sizing can be developed. Step 6 can be done at multiple implementation stages, such as after going live for each customer location. Refer to solution number 225096 to find the latest information about performance related topics which deserve special attention or are not yet published via the regular documentation. It also provides information about the latest version of the Sizing White Paper. Download the solution number at http://www.infor.com/inforxtreme. Sizing guides, questionnaires, and e-sizing assistance can be found at: http://pbc.infor.com/sizing/ For second line sizing support contact infor.sizing@infor.com
| |||||||||||||||||||||||||||||||