• 1. Willsys will monitor the operations of the SAP environment and Report to Customer to take the appropriate actions to address systems issues in SAP systems areas including:
• 2. Monitoring Job logs
• 3. Ensuring all SAP instances are running else report to Customer
• 4. Monitoring Standard SAP housekeeping jobs
• 5. Reporting on Spool and Print within SAP
• 6. Monitoring Tem Se objects, consistency and reorganization
• 7. CCMS alerts
• 8. Trace files
• 9. Job queues
• 10. Update process and terminated updates
• 11. Analysis and deletion of aged locks
• 12. Serious system log messages
• 13. Program terminations (short dumps)
• 14. Research SAP Net database for short dumps, determine relevance to Customer and forward it to super - users.
• 15. Update Locks and table Locks Reporting
• 16. Transactional and qRFC Queue Status

Willsys Basis Team will monitor constantly the growth of File systems and Database as part of the check list. We will monitor the growth of the sys log files, db log files, transport log files ,so that abnormal growth will be identified, and either backed up to a tape, or archived to other destination.

Willsys will develop and implement a proactive program to monitor all systems and operations under its responsibility and report to CUSTOMER when Willsys detects an area of responsibility which is degrading its performance. Upon identification of the root cause Willsys will initiate corrective actions or execute the appropriate escalation procedure. If, in the course of performing the Services, Willsys detects systems performance problems in areas outside the Scope of Work, Willsys will advise Customer Management of such systems problems as soon as possible.

As there is a Solution Manager in the landscape we will use this agent to monitor the system.

We do configure Monitoring Trees and Alert Monitors in CCMS to raise alerts to operators (Consultants) in case of any errors which are cropped up during run time.

Willsys will tune the SAP system with the objective to run the SAP system at optimal performance. Tuning activities will include

• 1. Performance and related tuning
• 2. Workload and buffer analysis
• 3. Profile parameter changes
• 4. SQL Performance Tuning
• 5. Work process allocation and performance (dialog, update, background, and spool)
• 6. Transaction performance
• 7. SAP Logon load balancing

Willsys will manage and maintain the SAP system landscape, which includes the Development, Test and Production Systems. System landscape activities will include

• 1. Client settings and client copies/refresh
• 2. Analysis of transport logs
• 3. Correction of transport errors.
• 4. Carry out system copies from Production system to TST on need basis.
• 5. Perform CTS, including configuration changes as required
• 6. Data Base Administration & Support

Willsys database back-up and recovery activities will include the following:

• 1. Ensuring database backups and archive logs successful completion.
• 2. Schedule Archive Log Backups, Periodically to avoid "archiver stuck" scenario.
Monitor "saparch" file system capacity and initiate/take necessary action.
• 3. Management of Tape library rests with Customer Team.
• 4. Reviewing the backup processes to confirm suitability and timeliness.
• 5. Tapes will be checked for the consistency at least once in the defined backup cycle.
• 6. Willsys recommends weekly full backups (offline/online) with online/incremental backups done nightly according to the schedule approved by Customer Project Management Team.
• 7. Tapes shall be stored offsite.
• 8. Full restore procedures must be demonstrated via actual test once per year.

Willsys will collect data and information concerning the areas it is managing as part of the Services on a periodic basis. Such information will be interpreted, analyzed and reported to Customer Such data collection, performance monitoring, trend analysis and reporting will include recommendations for avoiding performance problems as well as improving performance of the Services.

A report will be prepared at end of every month and presented to Customer management by first week of following month as per your requirements, covering the entire landscape. Willsys will also provide problem management service to minimize the adverse effect of incidents.

• 1. Observations and recommendations for performance improvement.
• 2. List of out-of-hours calls and the resolution
• 3. MIS Reports and Daily Check Lists and Weekly Consolidation Reports
• 4. Weekly reports
• 5. Status reports
• 6. Metrics reporting
• 7. Calls opened, calls closed, average time spent per call by priority, category, functional area
• 8. Monthly Reporting
• 9. Dashboard overview
• 10. Services Level report with trend analysis
• 11. Comparison over last month’s performance
• 12. KB update report
• 13. Mean time to repair report on break fixes by priority/critically/business areas
• 14. Quarterly Reporting
• 15. Consolidated SLA report over last quarter / performance etc.
• 16. Cost overrun analysis on new projects, time utilization chart
• 17. Steering committee report on discussions, minutes and action items

Any change that needs to be implemented into production will go through MSDPL change management process and approvals there in.

SLAs are at the heart of Support Provider (SP) relationships. Willsys believes in accountability for meeting Service Level Agreements negotiated as part of the overall contract with its customers.

We will also be able to demonstrate our ability to maintain appropriate SLA levels with other clients and provide periodic reports of results. Basically customers would require that we manage this environment to ensure its availability and support.

For all the above-mentioned requirements the Willsys Team will send out a written email by the Project Manager of delivery. The Delivery Head will then act on the request and fulfill the requirements the satisfaction of all involved.

All the Necessary Down times are documented and performed during Off-Peak hours or during Weekends. This is informed to all the Productive Users well in advance and performed only on approval from the Project Manager. These down times will be aligned with other down times (UPS, Power Maintenance and Hardware etc.)

The SAP Data Migration solution is based on SAP Business Objects Data Services and provides packaged content to the primary data objects required for migration. Expedien has extended the solution with its own methodology aligned to ASAP to provide customers with a clear approach to migration. It provides alignment between the business process functional consultants and the data migration team to ensure that the data being sourced is what is required to support the business processes being designed.

Expedient provides full project delivery support and supplement your existing delivery team with SAP Data Migration expertise to guide and quality check delivery. Expedien can help you in performing business analysis in preparation for the migration. Most legacy data systems tend to have issues such as duplicate records for customer or vendor records across sources. We use systematic and educated approach in resolving these issues and prepare a golden copy of the legacy data to load in your SAP application. We use the following proven process for SAP Data Migration.

• SAP Implementation Services
• SAP UPGRADE Services
• SAP HANA Upgrade and Migration
• SAP OS and DB Migration
• SAP S4HANA Implementation

Service Desk is a Service in Solution Manager in which internal customers, users or reporters create problem messages directly from a transaction. Employees, Business Process Owners or reporters can contact their Service Desk easily in this way. One can organize the internal service desk in several support units.

The processor of the problem in the Service Desk can enter symptoms in an internal solution database, and search for solutions. He can also search for SAP notes in the SAP Service Marketplace. If the processor does not find a problem solution, he can forward the problem message to subsequent support units, or to SAP Support, and monitor the progress of processing in the Service Desk.

Change Request Management enables to manage SAP Solution Manager Projects (maintenance, implementation, template, and upgrade) projects from inception to Go-Live: Starting with change management and project planning, through resource management and cost control, to physical transports of changes from the development environment into the productive environment.

Ongoing software and configuration changes as well as large implementations or ongoing challenges for managing data consistency and secure project control are tracked. Change Request Management as part of SAP Solution Manager integrates Service Desk functionality for managing change requests, and extends project control by integrating project planning with the cprojects application into a transport workflow control.

The processes supported by Change Request Management include urgent corrections for implementing fast and direct changes in the productive environment, and activities for maintenance projects, and implementation, upgrade, or template projects. Cross-system and cross-component changes are supported.

Change Request Management offers the following benefits:

• • Increased maintenance and project efficiency
• • Minimized costs for project management and IT
• • Reduced risk of correction and project failure
• • Shorter correction, implementation, and going-live phase
• • Efficient maintenance of customer developments and implementations

Note: The Complete Project Management using ASAP Methodology is tracked by using predefined SAP Business Scenarios.

It guides you through the procedure for planning and implementing maintenance and for installing enhancement packages. It complies all the necessary information in a procedure and the product to be maintained or installed, the affected systems, and the assigned SAP support packages.

It performs the automatic calculations and it determines the files for maintenance in the system landscape, or components for installing the enhancements package and supports the automatic download of automatically calculated files that are needed for product maintenance in the designated system. It gives you the opportunity to administer a central registry for files downloaded using the Maintenance Optimizer. When manually selecting product maintenance files, it guides you directly to the corresponding download area of the SAP Software Distribution Center for the product that you want to maintain. It approves the items in the Download Basket of the SAP Software Distribution Center. It also gives an overview of all open and completed product maintenance processes.

It provides a report function so that you can search for and display all product maintenance processes in your SAP Solution Manager.

The Service Data Control Centre supports the preparation and delivery of SAP service sessions, such as Going Live and SAP Early Watch Alert.

The tool is intended primarily for SAP service engineers performing SAP service sessions, as well as for system administrators and other qualified customer employees working in their own SAP Solution Manager systems.

The SAP Early Watch Alert is a diagnosis which monitors solutions in SAP and non-SAP systems in the SAP Solution Manager. The system processes the downloaded data. You can display the report as an HTML document. You can also create the report as an MS Word document. You can use the documents as status reports. You can analyze and avoid potential problems with these reports.

It is the interface between your IT department and the person responsible for a business process.

It provides analyses across the systems and business processes in your solution landscape.

You can thus react quickly to risks, and continually improve your IT service.

• 1. A Service Level Agreement is defined between you and an IT organization. It covers Your IT service quality requirements, for example performance and security and unambiguous and measurable service targets and communication structures
• 2. You schedule Service Level Reports based on the Service Level Agreement. You create Service Level Report types. Service Level Report types are templates for Service Level Reports. The Service Level Report types specify the contents and scope of the Service Level Report.
• 3. You specify the scope of the Service Level Reporting, e.g.: which business processes and which systems in your solution are analyzed/ which checks and alert thresholds you require and how the information is presented in the reports
• 4. The system creates the relevant Service Level Report sessions, which you can process, to change details or add further information and the Service Level Report is sent to the persons responsible.

The system monitoring monitors the systems in your solution landscape, in real time.The system monitoring is based on the SAP CCMS monitoring concept or an EWA Based.

System Monitoring Provides the List of values that are overflown beyond the threshold values

The central system administration manages tasks for the systems in your solution, centrally. The preconfigured view of your tasks, and the logical collection of the administration tasks help you to handle open tasks.

The system generates component-specific administration tasks, depending on the SAP system type.

It is used to Set-up tasks for the systems in your solution, Perform tasks, Create task logs, Monitor task plans and Monitor task status

The business process monitoring monitors all business-process-specific processes. You can identify and solve problems at an early stage.

You want to determine which processes and functions, e.g. background processing, important transactions or logs, are to be monitored.

To ensure quick processing of errors, you can specify detailed procedures for:

• 1. Business Process Monitoring
• 2. Error handling
• 3. Contact persons
• 4. Escalation paths

In today’s distributed, multi-technology customer solutions with multi-channel access through diverse devices and client applications, analyzing the root cause of an incident requires a systematic top-down approach. This approach must be guided by tools that help customers to do this as efficiently as possible, following SAP best practices.

The goal of Root Cause Analysis is to identify and provide: an immediate corrective action (workaround) to restore service operations as quickly as possible with minimal disruption to end users by isolating the area of concern and a complete solution to the issue at hand

Root Cause Analysis tools are designed to work towards reducing the number of resources in each step of the resolution process and the Root Cause Analysis infrastructure is open to the integration of new SAP technologies, applications and third-party software.

Willsys would be using standard SAP Methodology SAP Homogenous/Heterogeneous System copy The phases during the migration are as mentioned below:

• 1. Plan: In this phase planning for the Migration will happen and all the necessary components required for the Upgrade including software and hardware would be identified
• 2. Build: In this phase actual execution will happen on the system and SAP Migration would be performed and built to defined Hardware.
• 3. Run: The system would be stabilized and day-to-day activities would come into normal operations from this phase.

Setup System Environment

---

Serial	Activity	Support Scope	Customer SCOPE
1	Install Operating System Win X86_64	Assist verbally and Remotely	System Admin has to Install from Onsite
2	File System Setup As per SAP Recommendations	Assist verbally and Remotely	System Admin has to setup from Onsite
3	Order SAP Software	Assist verbally or send message to SAP	-------
4	Download SAP Software from SAP Market Place	Complete Scope	-------
5	Enable the Network and Provide Remote Access	Assist verbally and Remotely	System Admin has to enable the Remote connectivity, IP Address setup, add to Domain and allow in Firewall(if any)
6	Provide IP Addresses	Assist verbally and Remotely	System Admin has to provide IP Addresses
7	Install Database	Install the SQL Server and Software and patches	Copying the SQl Server Software along with patches
8	Install SQL Server Patches	Install SQL Patches	Copying Software SQL patches
9	Setup the Environment	Support Partner sets the Environment	Provide access to SAP
10	Copy the SAP Software	-------	Copy the Software from CD or Download Area to Servers.
11	Install the SAP ERP System on Development System with X-86 Environment	Install the SAP System	Allow the blocks to install on the specified ports.
12	Perform the Post Installation Actions	Apply License STMS	------
13	Install GUI	Install 740 GUI	------
14	Checking the Sanity, High Availability and Network and Adding Entries to Presentation Servers	Complete Scope	Presentation Servers has to be modified by Customer System Admin and check the connectivity.
15	Provide Access to End Users for testing	Support Network Issues and remote connectivity	-------
16	Perform Backup	Support Network Issues and remote connectivity	-------

---

Serial Number	Name of the Activity	No of Days
	Install, configure and setup sap router of Solution Manager	7 Days
1	SAP ECC 6.0 Upgrade EHP6.0(Mock 1)	15 Days
2	Planning the Upgrade
3	Documentation of the upgrade
4	Preparation for the Upgrade
5	Backup of Production Database
6	DB Refresh on Quality/sandbox System
7	Connect to Market Place through Solution Manager
8	Configure Maintenance Optimizer
9	Add the Software Downloads (Generate XML File)
10	Download the Software
11	Execute Prepare
12	Upgrade Execution
13	Communication with SAP to Resolve Runtime Issues
14	Handling SPDD and SPAU Objects
15	Testing the Upgrade
	Export the Database and import the Database(Unicode)
	Post Upgrade steps
16	SAP ECC 6.0 Upgrade EHP6.0(Mock 2)	10 Days
17	Backup of Production Database
18	DB Refresh on Quality System
19	Connect to Market Place through Solution Manager
20	Configure Maintenance Optimizer
21	Add the Software Downloads
22	Generate XML Stack File
23	Execute Prepare
24	Upgrade Execution
25	Communication with SAP to Resolve Runtime Issues
26	Handling SPDD and SPAU Objects
27	Testing the Upgrade
	Export the Database and import the Database
28	SAP ECC 6.0 Upgrade EHP6.0(DEV)	10 Days
29	Backup of Development Database
30	Execute Prepare
31	Connect to Market Place through Solution Manager
32	Configure Maintenance Optimizer
33	Add the Software Downloads
34	Generate XML Stack File
35	Upgrade Execution
36	Communication with SAP to Resolve Runtime Issues
37	Handling SPDD and SPAU Objects
38	Generate Change Requests
39	Testing the Upgrade
	Export the Database and import the Database
	Post Upgrade
40	SAP ECC 6.0 Upgrade EHP6.0(PRD)	3 Days
41	Backup of Development Database
42	Execute Prepare
43	Connect to Market Place through Solution Manager
44	Configure Maintenance Optimizer
45	Add the Software Downloads
46	Generate XML Stack File
47	Upgrade Execution
48	Handling SPDD and SPAU Objects
49	Generate Change Requests
50	Testing the Upgrade
	Export the Database and import the Database (Unicode
	Post Upgrade steps

Note: The Above line Items provided in the above table has to be iterated as many times ( at least 2 times) as possible until the final miles stones are arrived for scheduling down time.

The Functional Team and Technical Team has to verify and certify the Systems before carrying out the Final Migration

Same Approach will be followed for Solution Manager and BI-BO Systems

Disaster Recovery Server will be set up from the Copy of Production Upgrade