Database Reference
In-Depth Information
While defining the landscape, the strategy should take into consideration if the customer
intends to use Ready-to-Run R/3 system or a Preconfigured System (PCS):
1. Determine and identify Required Systems.
2. Client Deployment Strategy.
3. Release Strategy.
4. Transport System Strategy.
13.2.1.3 Project Kickoff
In ASAP, this task is the first important milestone of the project.
This task signals the formal initiation of the SAP project. The occasion should be graced by
the presence of all the senior management, steering committee members, SAP project managers,
SAP team members, SAP consultants, partner representatives, and the change management team
and members. This is the platform to elaborate the project charter, the implementation strategy,
the project organization, and the overall project plan. It also presents the key roles, requisite skills,
time frames, and responsibilities of the various members of the team. The meeting should espe-
cially emphasize the change management goals and objectives. In the final analysis, it is basically
a forum for get the immediate team motivated and exited about the successful completion of the
SAP project in time and on budget.
This meeting also implies the corporate-wide adaptation of the declared goals and objectives,
defined strategies and plans, and established standards and procedures by not only the members of
the SAP team but also the company as a whole. The kickoff meeting is followed by team standards
meeting to adopt all of the relevant standards as well as wide dissemination of the project-related
details throughout the organization.
13.2.1.4 Infrastructure Requirements Planning
This task targets gathering of company-specific data to define the requirements of the infrastruc-
ture, size and benchmark the hardware and related infrastructure, and procure the hardware keep-
ing in line with the overall time frame of the project:
1. Define Infrastructure Requirements.
2. Benchmark Hardware.
3. Procure Initial Hardware.
4. Order Remote Connection.
It also involves ordering for the remote connection to the nearest SAP servers in that part of the
world. This connection acts as the lifeline for specific services provided by SAP at various stages
of the project like OSS, GoingLive service, and EarlyWatch service, and this lifeline may become
extremely critical at the time of unforeseen problems or emergencies.
