asap roadmap - support - end-user acceptance analysis_ proposal template

©SAP Commercial In Confidence 3 February 2009

BTC Proposal for End-User Acceptance Analysis to <CLIENT>Subtitle

<Date> <Version><Original Author> <Modified by>

BTC Proposal

This box along with the contents is metadata for this template and needs to be deleted while preparing the proposal

Template Document Change History

VERSION DATE AUTHOR REMARKS1.4.1 MAY 11, 2009 FRANK

ROTHENPIELER AND AAKASH JHALANI

FIRST DRAFT OF OCM END USER ACCEPTANCE ANALYSIS

Version A.B.CA= Denotes the version for the basic templateB= Denotes the service category (for now 0=basic, 1=ITAA, 2=CCoE, 3= BPM, 4= OCM)C= Denotes the minor changes version within service category

Legend for the colour coding of text in the template is given below:Green – Geography specific contentRed – Directive/guideline for the actual contentViolet – Optional Grey - ExampleBlack – General content/Static

©SAP Commercial In Confidence 3 February 2009Page 1/18

BTC Proposal

FOREWORD/ CONTRACT CONDITIONS...........................................................................2

1 Introduction....................................................................................................................2

2 SAP’s Understanding of <CLIENT>’s Requirements.....................................................2

3 Project Objectives..........................................................................................................4

4 Project Approach and Deliverables................................................................................4

5 <Client> Cooperative Duties, Assumptions and Limitations...........................................4

6 Logistics.........................................................................................................................5

7 Project Organization......................................................................................................5

8 Project Timeline.............................................................................................................6

9 Effort and Costs.............................................................................................................6

10 Appendix....................................................................................................................6


BTC Proposal

FOREWORD/ CONTRACT CONDITIONSThe contents of this document shall remain the confidential property of SAP and may not be communicated to any other party without the prior written approval of SAP. This document must not be reproduced in whole or in part. It must not be used, other than for evaluation purposes by <CLIENT> except with the prior written consent of SAP and then only on condition that SAP’s and any other copyright notices are included in such reproduction. No information as to the contents or subject matter of this proposal or any part shall be given or communicated in any manner whatsoever to any third party without the prior written consent of SAP.

SAP warrants that to the best of its knowledge those who prepared this response have taken all reasonable care in preparing it and believe its contents to be true as at the date of this document. SAP cannot however warrant the truth of matters outside of its control and accordingly does not warrant the truth of all statements set out in this document to extent that such statements derive from facts and matters supplied by other persons to SAP. The statements in this document are qualified accordingly.

The furnishing of this document is for budgetary purposes only. It is subject to contract and shall not be construed as an offer or as constituting a binding agreement on the part of SAP to enter into any relationship. Any services to be provided by SAP as proposed in this document shall be subject to the standard terms and conditions of SAP for the provision of the relevant services.

This proposal is valid for 30 days from the date of this document.

1 Introduction1.1 Background to the document

As a guide this section provides the background to the document and/or provides the cover letter.

This document explains how SAP Business Transformation Consulting proposes to deliver <Service> to <Client>.

This document has been prepared based on the

RFP dated <Day Month Year>

Information which has been provided by client discussions with SAP in <Month Year>

2 SAP’s Understanding of <CLIENT>’s Requirements2.1 The Current Situation

As a guide this section shows that SAP BTC understands the clients:

Industry and competitive position

The current strategic and business objectives, or larger projects that the client has, which the SAP solution will add value to

The relevant issues ( Project objectives) driving the client to request <Service>


Administrator, 02/16/09,

Geography specific


Project specific


Project specific

BTC Proposal

2.2 SAP’s recommended service description

As a guide this section shows SAP’s description of service as available from material on the portal. This may involve a graphic to enhance the visual presentation. The aim of this section is to provide a high level overview of the service.

2.2.1 Reasons for Applying an Acceptance Analysis

End user acceptance is considered a key indicator of success for any SAP implementation. The success of an SAP project depends on how useful and beneficial end users perceive the new processes and the new systems after go-live.

Therefore, one of the key questions is to identify the causes of different acceptance levels. For example a low perception of the usefulness or usability of an SAP solution could be caused by lack of end user training. Other causes might be cultural differences in information usage as well as the lack of functionality or trust in the information quality provided by the system. Especially establishing standardized processes and systems on regional or global level could lead to the end user’s perception of loosing freedom in selecting or adapting their own tools. A deeper understanding of the causes for different end user acceptance levels is necessary to derive and implement appropriate improvement measures.

In order to get a clearer picture of the root causes for such different user behavior SAP provides a practical-proven and empirically founded methodology to evaluate end user acceptance levels and its influencing factors (causes). The acceptance analysis helps customers to identify right measures to realize the full economic benefits of their SAP implementation.

2.2.2 General Objectives of the Acceptance Analysis

The objectives of an end user acceptance diagnosis can be grouped into the following categories:


Knowledgetransfer

Continuousimprovement

Identification of root causes to improve the implementation process

Derive and prioritize and appropriate activities to improve end user acceptance

Ensure continuous improvement process (e.g. measure the impact of follow-up activities)

Ensure knowledge transfer and usage of experiences for subsequent projects (e.g. roll-out projects)

Evaluation

Feedback about the quality and effectiveness of the implementation process (e.g. organizational change management, quality of system, processes and end user support)

Identification of relevant causal structure and influencing factors of end user acceptance

Application of a standardized diagnostic tool to measure acceptance of SAP users

Knowledgetransfer

Continuousimprovement

Identification of root causes to improve the implementation process

Derive and prioritize and appropriate activities to improve end user acceptance

Ensure continuous improvement process (e.g. measure the impact of follow-up activities)

Ensure knowledge transfer and usage of experiences for subsequent projects (e.g. roll-out projects)

Evaluation

Feedback about the quality and effectiveness of the implementation process (e.g. organizational change management, quality of system, processes and end user support)

Identification of relevant causal structure and influencing factors of end user acceptance

Application of a standardized diagnostic tool to measure acceptance of SAP users


Service specific

BTC Proposal

Figure 1: Objectives of End User Acceptance analysis

2.2.3 Full Cycle of Acceptance Analysis

To meet these objectives the acceptance analysis is structured in three phase:

Phase A: Evaluation of status

Objective is to evaluate the status quo after go-live This phase should be conducted 3-6 month after go-live

Phase B: Apply follow-up activities

Objective is to derive appropriate improvement activities – if necessary – on basis of the results The range of improvement activities could be from simple measures to projects

Phase C: Evaluate the impact

Objective is to evaluate the impact of implemented improvement measures after phase A The evaluation of the impact should be conducted 9 to 12 month after go-live

Figure 2: Phases of End User Acceptance Analysis

This proposal is focused on the phase A. Efforts for phase B and C will be part of different proposals according to [customer name]’s needs. In general, the efforts required for the evaluation of the impact in phase C will be significantly reduced due to reuse of results/ documents, e.g. questionnaire.

2.2.4 Partnership

SAP has engaged in a close partnership with the Institute of Industrial and Organizational Psychology (W&O-Institute) at the University of Mannheim. The combination of SAP’s project experience with methodological experience of the W&O-Institute guarantees the highest quality of the acceptance analysis. The advantages of this partnership could be summarized into three categories:


Phase A:Evaluation of status

Phase B:Follow-up activities

Phase C:Evaluation of impact

No What? Who? With whom? By when? Status Comments

1 GLOBAL Awareness workshop: Importance of change management in GLOBAL

Mr. Smith CM-Team May, 26th in process Invitation sent out on May, 12th

2 Increasing level of information about GLOBAL (vision, mission, scope, objectives and plan)

Project Management GLOBAL Project Team asap open Information events should organised by

cluster

3 Make appropriate and sufficient resources available for cluster work Project Management GLOBAL Cluster

Leader asap in process Definition of role profiles required

4 Rework list of decisions (reduce complexity, prioritise decisions, ensure integration)

GLOBAL Cluster Leads Project Management asap in process

5 Define and implement an appropriate business re-engineering methodology PMO Project

Management June open

6 Align all communication activities within GLOBAL project team

PMO CM-Team asap in process Syncronise communication activities with overall project plan

7 … … … … … …

8

9

10

Apply online diagnostic tool

Analyze and report results



Define improvement activities

Implement activities

SAP AG 2007, Framework for Acceptance Analysis / Dr . Oliver Kohnke / 4

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

2007

Activity

Activity

Activity

Activity

Activity

Activity

Activity

Activity

Activity

Activity

Legend: Duration Milestone today

Phase A:Evaluation of status

Phase B:Follow-up activities

Phase C:Evaluation of impact

No What? Who? With whom? By when? Status Comments

1 GLOBAL Awareness workshop: Importance of change management in GLOBAL

Mr. Smith CM-Team May, 26th in process Invitation sent out on May, 12th

2 Increasing level of information about GLOBAL (vision, mission, scope, objectives and plan)

Project Management GLOBAL Project Team asap open Information events should organised by

cluster

3 Make appropriate and sufficient resources available for cluster work Project Management GLOBAL Cluster

Leader asap in process Definition of role profiles required

4 Rework list of decisions (reduce complexity, prioritise decisions, ensure integration)

GLOBAL Cluster Leads Project Management asap in process

5 Define and implement an appropriate business re-engineering methodology PMO Project

Management June open

6 Align all communication activities within GLOBAL project team

PMO CM-Team asap in process Syncronise communication activities with overall project plan

7 … … … … … …

8

9

10





Define improvement activities

Implement activities

SAP AG 2007, Framework for Acceptance Analysis / Dr . Oliver Kohnke / 4

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

2007

Activity

Activity

Activity

Activity

Activity

Activity

Activity

Activity

Activity

Activity

Legend: Duration Milestone today

BTC Proposal

Combination of experience SAP has strong product, solution and implementation know how The W&O-Institute has strong experiences in international employee surveys and is able to host

surveys with large groups of employees (up to several thousands) and has strong capabilities to meet specific requirements of end user surveys (items and scale definition, reports, analysis,…)

Non-disclosure agreement with W&O-Institute (as SAP‘s subcontractor) guarantees confidentiality of customer specific data at any time

Anonymity & Neutrality External hosting of surveys avoids anonymity and neutrality problems perceived by participants Anonymity increases motivation to answer questions in an honest way (higher quality of answers) Anonymity increases participation rate

Analysis & Reports Efficient capabilities to produce customer specific and user friendly result reports Strong capabilities to perform (additional) statistical analysis (e.g. SPSS) Ability to calculate specific indices that are based on SAP’s practical

proven and empirical founded acceptance model

3 Project ObjectivesThis project has the following objectives:

As a guide, this section will contain specific/customized or part solutions of the overall service as described in the SAP service description section.

4 Project Approach and Deliverables4.1 Overview

SAP BTC’s phased <Service> combines our expert knowledge of SAP software and its technical requirements, with experience of how clients gain the value from SAP systems by adopting both deployment and operational best practice.

Our consultants will carry out the evaluation by drawing on SAP’s extensive knowledge-base of completed <Service> projects, and by working collaboratively with your stakeholders to assure that the recommendations of the project accurately reflect your business objectives. This approach assures that <Client> capitalises on SAP’s experience; gains a clear understanding of all feasible technical options and ultimately selects the SAP transformation approach that will generate material and sustainable value.



General


Project specific

BTC Proposal

4.2 Work Packages

The process of the end user acceptance analysis is structured into five steps which are described in the following chapters.

Figure 3: Proceeding with the End User Acceptance Analysis

4.2.1 Step 1 – Set-up of Survey

SAP is providing a practical and empirically proven acceptance model that enables the customer to measure end-user acceptance and its influencing factors. This model helps to acquire feedback regarding the quality and effectiveness of the implementation process as well as identifying causes for different end-user acceptance levels regarding SAP solutions. A standardized and modular diagnostic tool (questionnaire) offers a demand-oriented adaptation to the specific customer situation.

The end-user acceptance survey is based on four principles which guarantee a successful process and will be adhered to:


Set-up Adaptation of the survey

Informationto employees

Execution of survey

Analysis & reporting

Definition of objectives and scope

Prioritizing topics and selection of survey modules

Specification of the evaluation units, e.g. countries

Agreement to principles of the survey, e.g. anonymity

Selection and adaptation ofquestions

If necessary, developmentof additional modules

Pretest execution

Set-up online questionnaire

If necessary, involvement of social stake-holders (e.g. works councils)

Announcing the enquiry to employees and management

Illustrate advantages of participation

Explanation of goals and methodology

Distribution of questionnaires (paper pencil or electronic)

If necessary, additional actions, e.g. establishing a help line

Anonymous statistical analysis

Preparation of the result presentation

Identification of improvement measures

Presentation & publications of results

Plan improvement measures

Realization of measures

Control impact of measures, e.g. repeated survey

Follow-up activities

1 2 3 4 5

Set-up Adaptation of the survey

Informationto employees

Execution of survey

Analysis & reporting

Definition of objectives and scope

Prioritizing topics and selection of survey modules

Specification of the evaluation units, e.g. countries

Agreement to principles of the survey, e.g. anonymity

Selection and adaptation ofquestions

If necessary, developmentof additional modules

Pretest execution

Set-up online questionnaire

If necessary, involvement of social stake-holders (e.g. works councils)

Announcing the enquiry to employees and management

Illustrate advantages of participation

Explanation of goals and methodology

Distribution of questionnaires (paper pencil or electronic)

If necessary, additional actions, e.g. establishing a help line

Anonymous statistical analysis

Preparation of the result presentation

Identification of improvement measures

Presentation & publications of results

Plan improvement measures

Realization of measures

Control impact of measures, e.g. repeated survey

Follow-up activities

1 2 3 4 5


Service specific

BTC Proposal

Principle Content

Anonymity Participation in the acceptance analysis is anonymous so that the results of the survey cannot be traced back to any individual person. In consequence, analysis on group level (e.g. department) is possible with as little as 5 participants.

Voluntary participation Participation in the acceptance analysis is, of course, voluntary!

Transparency Participants of the acceptance analysis receive the aggregated results of the enquiry in the form of a results presentation.

Practical implications

The aim of the analysis is to point out measures and solution strategies to increase end-user acceptance and to improve report and information usage.

Objective: Setting the basis for the acceptance analysis

Activities: Definition of survey objectives and scope, e.g. evaluation of end user acceptance regarding one end

to end process or one SAP module Prioritize survey topics according to their importance for end-user acceptance, e.g. “Organizational

Change Management”, “Quality of system information”, “Quality of system performance” Define structuring criteria for statistical analysis and reporting, e.g. end-user roles, functional

departments, locations, countries, end-user behavior (e.g. report usage) Specify target groups (e.g. pilot countries/ areas) Agree on survey principles

Results (Documents):

Defined basis for acceptance analysis Defined project plan

Estimated effort:

Step 1 – Set-up Estimated Days

Define survey objectives and prepare acceptance analysis 1

Define and prioritize survey scope 0,5

Define structuring criteria and evaluation units 0,5

4.2.2 Step 2 – Adaptation of Survey Content

The second step focuses on the selection and refinement of detailed questions. The number of questions for each topic should reflect the previous prioritization of the survey topics, e.g. high importance of a topic should require a detailed investigation with 5-8 questions.

Objective: Developing a questionnaire (English) on the basis of SAP’s standard that is adapted to the specific

customer situation (e.g. number of questions per topic according to importance)


BTC Proposal

Ensuring that all relevant influencing and acceptance factors are included in the questionnaire in order to properly utilize the causal acceptance model

Activities: Prepare and conduct a series of workshops in order to

o select questions according to prioritized topics (content) from standard questionnaire o refine detailed questions according to customer specific style and termso if required, develop additional questions according to specific requirements of departments

under survey (max. 5-8 questions) Prepare and conduct a pretest with end-users of the defined target group (three groups of 3-5

persons at one customer location). The pretest helps to improve the quality of the questionnaire (e.g. wording, examples from daily work) and results in higher acceptance

Adapt the questionnaire according to the pretest results Develop a code table for each question (variable names, scaling) necessary for subsequent statistical

analysis.


Questionnaire for sample survey (in English) Table with coding of variables (items)

Estimated effort:

Step 2 – Adaptation of survey content Estimated Days

Select and refine detailed questions 2

Conduct pretest with end-users 2

4.2.3 Step 3 – Information to Employees (Option)

The acceptance survey has to be accompanied by appropriate communication measures. In this step all necessary communication measures will be defined and synchronized with the project plan.

Objective: Create awareness of planned survey amongst management and end-users Increase motivation to participate in the sample survey (high participation rate) Manage expectations of survey participants

Activities: Analyze established communication channels within selected organizational units, e.g. intranet sites,

newsletter, to reach the target groups Define and plan appropriate communication activities to support the survey, e.g.

o Local information packages, e.g. FAQ listo Letter/ email to managerso Letter/ email to target groupo Information on system screeno Incentives for participantso Invitation with link to online surveyo Refresher after one week


BTC Proposal


Communication plan for sample survey

Estimated effort:

Step 3 – Information of employees Estimated Days

Support communication activities during sample survey 2

4.2.4 Step 4 – Execution of Survey

This step contains the preparation and hosting of the online survey with an internet based diagnostic tool. This tool guarantees high availability and performance up to several thousand employees accessing the online questionnaire within a short time frame.

Objectives: Ensure high quality of online questionnaire Ensure high quality end-user access to online survey (availability and performance)

Activities: Set-up questionnaire in online tool Test questionnaire and end user access to internet page Host online survey during data collection phase (2-3 weeks) including administration


Excel sheet and SPSS file with raw data (including text comments)

Estimated effort:

Step 4 – Execution of survey Estimated Days

Set-up questionnaire in online tool 1

Test online questionnaire and end user access 1

Host online survey including administration 2

4.2.5 Step 5 – Analysis & Reporting

This step is the most important one since the raw data of the survey will be statistically analyzed and described in action oriented and comprehensive reports.

Objectives: Describing the quality of the implementation process, system and support Describing the level of end-user acceptance and satisfaction Identification of root causes for different end-user behavior


BTC Proposal

a) Analysis

The analysis of the survey data is the key activity for getting deep insights into the current end-user perception of the implemented SAP solutions and possible causes for different user behavior. All analysis will be performed in a strictly anonymous way.

Activities: Conduct descriptive analysis of survey data according to pre-defined structuring criteria Conduct qualitative analysis of comments according to pre-defined structuring criteria (provide MS-

Excel sheet with filtering function, ensuring anonymity, e.g. eliminate names) Conduct causal analysis on basis of the total sample size using powerful statistical methods (e.g.

structural equation model, regression, variance or correlation analysis)

Optional analysis: Conduct additional descriptive or causal analysis on the basis of a specific data selection,

e.g. within one organizational unit, functional area. Conduct qualitative content analysis that categorizes comments in order to derive key

statements and draw conclusions.

Increase explanatory power (optional):

The combination of survey data with real user data increases the quality and explanatory power of the analysis; therefore it is important to prepare real end-user data accordingly and in parallel to the survey. In order to make this possible the customer should conduct the following activities:

Prepare a separate data file (in MS-Excel) with real end user data on basis of appropriate KPIs, e.g. “report usage”, “no of logons”

These KPIs must be monitored during the data gathering phase for each end user in the target sample (preferably during the complete data gathering phase but at least during one week in order to reduce bias in real usage). An average score for each end user has to be calculated and linked to a user identification that is unique, e.g. email address

This ID should also be used for gathering the survey data as it ensures a correct link between survey data and KPI at an end-user level

As mentioned previously, SAP will ensure anonymity of individual survey data. After the merge of the two data files by SAP any possibility of identifying individuals, e.g. via email address, will be deleted. All data will be aggregated and analyzed on group level with at least five participants.


BTC Proposal

Estimated effort (days):

Step 5 – Analysis Basic1) Option

Conduct descriptive analysis of quantitative data 1 12)

Conduct descriptive analysis of qualitative data 1 13)

Conduct causal analysis 2 24)

1) Analysis will be conducted on basis of total sample size comparing data according to one criterion, e.g. countries2) Estimated effort for each additional analysis according to pre-defined structuring criteria, e.g. locations, functions,

roles3) Real effort for qualitative content analysis (categorization, interpretation) depends highly on actual number of

comments and has to be calculated after data collection phase4) Estimated effort for each additional causal analysis

b) Reporting

Activities

Define the structure of standard result reports Generate standard reports with descriptive survey results (e.g. calculate indices, means, distribution,

qualitative data) according to pre-defined structuring criteria (see example) Prepare a result presentation (synthesis of survey data) with recommendations


Report with descriptive analysis of quantitative data according to one structuring criteria, e.g. report comparing countries, locations, functional units or user roles

Report with descriptive analysis of qualitative data on basis of total sample size (MS-Excel) Report with causal analysis on basis of total sample size

Option 1: Interactive analysis and reporting tool SAP provides an offline tool that allows flexible descriptive analysis and reporting without additional

costs This online tool is based on the total sample size and allows selection of questions and comparisons

according to the pre-defined structuring criteria, e.g. comparing UK and Italy with respect to quality of system performance

Option 2: Additional reports Generate additional standard reports (based on descriptive or causal analysis), e.g. select and

compare specific groups of the survey sample

Option 3: Summary reports Define structure for summary reports for participants Generate summary reports for participants, e.g. report for a selected management or

functional area


BTC Proposal

Estimated effort (days):

Step 5 – Reporting Basic Option

Define customer specific result report - 1 Generate standard report for quantitative results 11) 12)

Generate standard report for qualitative results 11) 13)

Generate standard report for causal analysis 11) 1

Interactive analysis tool - 5

Prepare result presentation 2 -

Define summary report - 1

Generate summary report - 0,54)

1) Report will be generated on basis of total sample size comparing data according to one criterion, e.g. countries2) Estimated effort for each additional report according to pre-defined structuring criteria, e.g. locations, functions, roles3) Real effort for qualitative content analysis (categorization, interpretation) depends highly on actual number of

comments and has to be calculated after data collection phase4) Estimated effort for each summary report

5 <Client> Cooperative Duties, Assumptions and LimitationsAs a guide, this section should clearly outline any assumptions, pre-requisites and limitations that exist or are likely to be seen before and during the project. Some examples are provided in the working appendix; however these have to be decided by the project manager and will vary on a case to case basis.

5.1 <Client> Cooperative Duties <CLIENT> will appoint a Sponsor for the work.

<CLIENT> will nominate a Co-ordinator for the assignment (if not the Sponsor), who will liaise with the SAP Project Manager.

The Project Manager will develop, with the Coordinator/Sponsor, a schedule for interviews and workshops on-site.

5.2 Assumptions

This section should list the assumptions.

<CLIENT> is responsible for assessing and evaluating the final project deliverable, and will endeavor to provide at least one staff member, of which the SAP BTC project team will report to over the duration of the project

SAP BTC will not be involved in… unless commissioned on a separate scope to do so. Our responsibilities are limited to … as stipulated in this proposal

5.3 Limitations

If any, this section should list the limitations for the project.



Project specific

BTC Proposal

6 Logistics6.1 Venue

The on-site part of the project will be conducted at <location>.

7 Project Organization

One success factor for the acceptance analysis is the establishment of an effective project organization that includes the following roles:

Project Lead Project Enterprise (as sponsor) Head of Change Management responsible for the acceptance analysis Process Owner (depending on process in focus of acceptance analysis) Process Lead (depending on process in focus of acceptance analysis) Power User (depending on process in focus of acceptance analysis) SAP Team Lead responsible for the agreed deliverables SAP experts (involvement depends on specific activities and request)

Both Team Leads will have to agree upon an appropriate status reporting for all activities.

8 Project Timeline8.1 Project Plan

The acceptance analysis for the pilot studies could be completed until calendar week 7 from start. This depends mainly on the alignment process of the questionnaire, availability of resources and the duration of the data collection phase. It is recommended having a data collection phase of at least two weeks.

Phase Basic activity Proposed calendar week (CW)

Step 1 – Set-up Initial workshop/ Kick-off CW 1Step 2 – Adaptation of survey Refinement of content (workshops) CW 2 – CW 23Step 3 – Information of employees

Prepare managers and employees CW 2 – CW 5

Step 4 – Execution of survey Conduct survey CW 4 – CW 5Step 5 – Analysis & reporting Analyze data and prepare results Until CW 7

9 Effort and Costs



Project specifc


Project specific


Project specific


Project specific

BTC Proposal

The following table summarizes the estimated efforts (in days) for each step of the acceptance analysis. The estimated efforts are summarized for basic and optional activities.

Evaluation of status Basic Option

Step 1 – Set-up 2 -

Step 2 – Adaptation of survey content 4 -

Step 3 – Information of employees - 2

Step 4 – Execution of survey 4 -

Step 5 – Analysis and reporting

Descriptive quantitative analysis 1 11)

Descriptive qualitative analysis 1 12)

Causal analysis 2 22)

Standard reports 3 13)

Interactive Analysis Tool - 5

Result presentation 2 -

Summary reporting - 1 + 0,54)

Summary 19 days -1) Estimated effort per additional descriptive quantitative analysis2) Estimated effort per additional causal or qualitative content analysis 3) Estimated effort per additional result report (on basis of quantitative, qualitative or causal analysis)4) Estimated effort per summary report (1 day for report definition and 0.5 per report generation)


BTC Proposal

10 Appendix10.1 Delivery Team [Optional]

As a guide, this section will provide biography for the proposed delivery team.

If you have any suggestions for the proposal template, please contact BTC OCM Community



Project specific

https://portal.wdf.sap.corp/irj/portal?NavigationTarget=navurl://640b5473f367aa9f6d386ae368bd1360