In practice this analysis can be a very complex undertaking. Projects are frequently started with precise finance and even precise hardware environments pre-defined. However, this is usually done before the start of project with a thorough understanding of the final system requirement. Sizing hardware is always a challenge. The issue here is that production sized hardware usually needs to be procured even before the project has started. This is usually the case with organizations where Oracle and Oracle EBS is being installed for the first time. There is no prior version of the application, to benchmark against. Number of the hardware vendors provides sizing sheets that can be filled out, and a rough estimate required can be reached.
We're frequently asking to Oracle Support in Service Requests (SRs) to guide on the appropriate hardware specification for an Oracle Applications environment. Some of the areas we should keep in mind are, but not limited to:
• It should not get conflicted as Sizing a mere calculation rather it is a process.
• Sizing is a complex, iterative process and must be treated with care during the implementation.
• Sizing is a major assignment in any Oracle Project
• System sizing and architecture goes a long way in determining the TCO of the software
• It potentially means ability to grow vertically(Module wise) and Horizontally (Data)'
• Customer, hardware vendor and the consulting partner should work together to find the best sizing strategy.
• Your database Size should be based on benchmarks and collective experience of Oracle, H/W vendor and knowledge gained from existing customers.
• Sizing process should not be confused with capacity planning, as both are different parameters.
• Scaling & load balancing requirements can influence the architecture landscape
The reality is that sizing an Oracle Applications environment is a multipart task to carry out before the project start. There are a lot of factors to take into consideration.
• Underestimating the hardware that you need will have performance and budgetary consequences
• Overestimating the hardware you need wastes valuable resources.
• Poor performance of a system when it is rolled out will easily undermine confidence in a project.
• The functionality of the software may be perfectly good but if it is delivered on inappropriately sized hardware it may take time to fix and the integrity of the whole project may be called into question.
I have added below different sources for hardware sizing, including different vendor’s spreadsheets.
A good article of Steven Chan: A Primer on Hardware Sizing for Oracle E-Business Suite
IBM Sizing Questionnaire for Oracle E-Business Suite Applications - New Implementation
A good document of Andrew Rivenes: Sizing Oracle Applications Projects, A Technical Perspective
Different Vendor’s Sizing questionnaires are attached in this post
You can refer below link if you are looking for info on hardware sizing for Oracle Fusion Applications
Hardware Sizing for Oracle Fusion Applications 11g