<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/performance/tt/P000006_sizing_process" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Sizing Process</Title>
		<Keyword ContextSensitive="No"><Level1>
                              Valid for ERP LN FP0, FP1, FP2, FP3
                           </Level1>
		</Keyword>
	</Header>
	<GeneralSection><SectionTitle>Hardware</SectionTitle>
		<Paragraph class="Default">During the implementation of Infor ERP 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.</Paragraph>
		<GeneralSection><SectionTitle>Final sizing</SectionTitle>
			<Paragraph class="Default">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.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>Sizing verification</SectionTitle>
			<Paragraph class="Default">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.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>Stress test</SectionTitle>
			<Paragraph class="Default">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.</Paragraph>
		</GeneralSection>
		<GeneralSection><Paragraph class="Default">The following table shows the sizing stages and the tools, and the documents or services supporting them.</Paragraph>
			<TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated"><TBODY><TR><TD width="76" rowspan="1" colspan="1">
							<GUIRef href="" role="manual">Step</GUIRef>
						</TD>
						<TD width="300" rowspan="1" colspan="1">
							<GUIRef href="" role="manual">Phase</GUIRef>
						</TD>
						<TD width="322" rowspan="1" colspan="1">
							<GUIRef href="" role="manual">Tooling / documentation / service</GUIRef>
						</TD>
						<TD width="313" rowspan="1" colspan="1">
							<GUIRef href="" role="manual">Notes</GUIRef>
						</TD>
					</TR>
					<TR><TD width="76" rowspan="1" colspan="1">1</TD>
						<TD width="300" rowspan="1" colspan="1">Collect key sizing figures from customer</TD>
						<TD width="322" rowspan="1" colspan="1">Configuration and planning questionnaire Configuration and planning questionnaire for upgrades</TD>
						<TD width="313" rowspan="1" colspan="1">For upgrades use information from existing applications</TD>
					</TR>
					<TR><TD width="76" rowspan="1" colspan="1">2</TD>
						<TD width="300" rowspan="1" colspan="1">Optional: customer specific benchmark to determine load of specific functionality</TD>
						<TD width="322" rowspan="1" colspan="1">Customer specific benchmark</TD>
						<TD width="313" rowspan="1" colspan="1">Only for large/complex/business critical customers</TD>
					</TR>
					<TR><TD width="76" rowspan="1" colspan="1">3</TD>
						<TD width="300" rowspan="1" colspan="1">Size the hardware</TD>
						<TD width="322" rowspan="1" colspan="1">Sizing Guide / E-Sizing assistant (web based)</TD>
						<TD width="313" rowspan="1" colspan="1"></TD>
					</TR>
					<TR><TD width="76" rowspan="1" colspan="1">4</TD>
						<TD width="300" rowspan="1" colspan="1">Deliver sizing and deployment information to the customer</TD>
						<TD width="322" rowspan="1" colspan="1">Sizing Template (End 2007) Sizing White Paper (End 2007)</TD>
						<TD width="313" rowspan="1" colspan="1"></TD>
					</TR>
					<TR><TD width="76" rowspan="1" colspan="1">5</TD>
						<TD width="300" rowspan="1" colspan="1">Optional: stress test</TD>
						<TD width="322" rowspan="1" colspan="1">X</TD>
						<TD width="313" rowspan="1" colspan="1">Timely before going live to be able to solve problems</TD>
					</TR>
					<TR><TD width="76" rowspan="1" colspan="1">6</TD>
						<TD width="300" rowspan="1" colspan="1">Optional: do a sizing verification at the customer site to adjust sizing figures</TD>
						<TD width="322" rowspan="1" colspan="1">Sizing verification</TD>
						<TD width="313" rowspan="1" colspan="1">Only for large/complex/business critical customers After going live</TD>
					</TR>
				</TBODY>
			</TABLE>
			<Paragraph class="Default">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.</Paragraph>
			<Paragraph class="Default">Step 6 can be done at multiple implementation stages, such as after going live for each customer location.</Paragraph>
			<Paragraph class="Default">Refer to solution number <GUIRef href="" role="manual">225096</GUIRef> 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: <Link href="http://www.infor365.com" role="wwwlink">http://www.infor365.com</Link>
			</Paragraph>
			<Paragraph class="Default">Sizing guides, questionnaires, and e-sizing assistance can be found at: <Link href="http://pbc.infor.com/sizing/" role="wwwlink">http://pbc.infor.com/sizing/</Link>
			</Paragraph>
			<Paragraph class="Default">For second line sizing support contact <Link href="mailto:infor.sizing@infor.com" role="wwwlink">infor.sizing@infor.com</Link>
			</Paragraph>
		</GeneralSection>
	</GeneralSection>
</ManualTopic>
