您需要多少人来支持sap项目

1、附件三：您需要多少人来支持SAP项目？众所周知，实施R/3 费用很高，但是长期支持费用有多少？请用下文中 Gartner的 "rules of thumb"来算一下，如果采用SAP系统你需要多少人来支持？与您原来估算的差距有多大？同高昂的长期支持费用相比，初期实施费用根本算不了什么！原文：" Managing Enterprise Applications: From Packages To Productivity ", Gartner Group Europe Symposium proceedings, Cannes, France, Novemb

2、er 2-5, 1998, Fred Magee主题：企业管理软件运用：从软件包到生产力的转化Gartner集团欧洲区会议记录。地点：法国戛纳时间：1998 年11月2号到 5号。To develop a rough estimate for the size of an ERP implementation staff, use five person months per concurrent user and normalize based on estimated project length.基于标准的项目实施周期和每并发用户需五人月来粗略估计 ERP实施的所需人工规模。SAP Im

3、plementation Staff % By RoleRolesAvg %Range %ESP Avg %When UsedTraining-Methodology31-1220Technical Architecture71-2747Gap Analysis30-1428Module Configuration6140-8224Interfaces70-3542Custom Extensions50-2138Data Conversion60-1841Testing/QA84-1922任 务行业平均占总人行业范围的平均天的比例 %使用中培训-方法论31-1220技术体系71-2747差异分

4、析30-1428总体设置6140-8224接口70-3542客户化50-2138数据转换60-1841质量测试84-1922Total Staff Size "Coarse" Rule of Thumb : 5 Person-Months per Concurrent UserSource: Gartner Measurement Selected Benchmark DataNote : ESP = Enterprise Service Providers, eg Big Six's and large SI's依“ Rule of Thumb ”规则粗略

5、估算出人员规模：每并发用户所需五人月。资料来源： Gartner 集团的测量基准数据。备注： ESP 为企业服务提供商。例如国际六大咨询服务商。There is no "correct" size for an ERP implementation team, there are simply too many variables involved. However, having said that some data is better than none. Using twelve selected Gartner Measurement SAP benchmarks

6、, the variability in staffing quickly becomes apparent. Core implementation team sizes ranged from 24 to 161 with implementation elapsed times ranging from10 to 48 months. No obvious meaningful correlation was present in the data, e.g.number of modules, number of instances, degree of customizationor

7、 number of interfaces. However, looking back at the implementation usingoperational concurrent users as a metric, a correlation was found. A"coarse" rule of thumb is 5 person months per concurrent user. Estimationsof project duration and concurrent users would lead to an overall estimatefo

8、r staff size. A rough approximation for concurrent users would be 1:6named users.对于一个ERP 系统实施团队的大小而言，没有标准答案，因为在实际情况中涉及太多不定因素。有人说有数据总比没有的好。引用十二组Gartner 公司的测量SAP 实施基准数据为例，基中人员配备可变因素变得明显。根据SAP 以往项目实施时间的情况看，其核心实施队伍规模一般从24 人到 161 人，实施时间范围从10 个月到 48 个月。在数据中没有反映明显意义的相关性，例如产品的模块数、方案实例数、客户化程度或接口等。但是，运用并发用户的测

9、量标准来回顾项目的实施，就可以发现它们的相关性。单凭此经验粗略估算，每并发用户需五人月，估计项目持续的时间和并发用户有可以估计项目组的大小规模，一个粗略的近似数是：每并发用户：命名用户=1 ：6For the 8 staff roles measured, the data indicates a wide range of usage,with configuration dominating share of staff. Approximately half the casesused ESP for certain roles and when they did the average

10、s indicatedsignificant portions of work being outsourced. (.)Staffing sizes vary widely by organization, but can be correlated to two keyparameters, concurrent users and the industry standard Unix metric例如以 8 个人员任务为基准，数据显示了一个很大的以配置来控制人员分配的使用范围，约近一半案例使用了 ESP 任务，当外包重要的工作部分时，他们使用所显视的平均数人员规模配置的变化受组织影响，但

11、与并发用户和相关工业应用标准的两个关键参数有关联。SPECmark92 benchmark.以 SPECmark92为基准SAP Support Staff EFT MetricsSAP 支持人员， EFT 标准ApplicationAvgRangeProcess Owners191-57Super Users20-10Programmers82-22IS Support40-15InfrastructureAvgRangeOperations61-18Tech Services91-28Help Desk10-8Network10-3应 用平均数控制者19超级用户2程序员8技术支持4基础应用

12、平均数操作6技术服务9桌面帮助1网络1Rules Of Thumb :- Application Support EFT/100 Concurrent Users : Average = 8, Range = 4 - 18- Infrastructure Support EFT/1000 SPECmark92 : Average = 3.5, Range = 2 - 6单凭经验的规则：-应用软件支持 - 基础软件支持EFT/100 并发用户数。平均EFT/1000 SPECmark92=8，范围 =4 18平均 =3.5，范围 =2-5Application support covers st

13、aff that deal with user issues regarding applications, e.g. minor enhancements, bug fixes, report writing and questions regarding application functionality. Many companies draw from the same pool of SAP-skilled resources for both implementation and support.应用软件支持工作人员能处理有关软件应用用户问题，例如：初级入门、错误修复。 。、报告的

14、编写和应用软件功能问题的反映。许多公司从 SAP 熟练的经验中获得实施和支持方面的帮助。Infrastructure staffing includes technical services personnel such as the Basis support team, systems programmers, capacity planners and performance experts. Also included are operations staff such as console operators, job schedulers and tape operators. W

15、e see no great difference in infrastructure staffing between SAP implementations and other client/server environments when we look at common metrics such as support headcount per unit of capacity.基础应用人员有技术服务人员，例如技术支持小组、系统程序员、生产量计划员、执行专家等。同时亦包括相关操作人员，例如控制台操作员，工作日程计划员、数据备份员。当我们回顾其共同机制、标准如每容量单位的支持人员时，我

16、们发现在 SAP 实施和其他客户 /服务环境之间的基本应用人员并没太多的不同。Two rules of thumb emerge from the selected benchmark data. Total EFT forapplication support is correlated to concurrent users, similar to what wasdone earlier for implementation. Infrastructure support is better correlatedto server capacity since this measures

17、 infrastructure size. The relevantSPECint numbers are drawn from the Unix industry standard SPECmark92benchmark.单凭经验的两个规则出现于被选基准数据中， 。EFT 应用支持是与并发用户相关联，类似于早期为实施所做的东西。 基础支持与服务器容量之间的关系更密切， 因为服务器容量可以测量支持队伍的规模。相关的 SPECint 数据从工业生产标准基准数据中抽取。Variance in infrastructure costs among SAP users is over 3 to 1.

18、(For thetwelve SAP installations, monthly costs per 1,000 dialog steps : range from25 to 90 USD).在 SAP 的用户之间的基本费用差异是SAP每一千个对话点每月的成本）。基础设施成本里的变化是3 1倍以上。用户包含基础结构成本（对SAP 十二安装产品，SAP12 每 1,000对话的每月的成本：从 25 90 USD 的范围。The hardware costs here include lease, maintenance and depreciation for all servers. Software includes SAP, DBMS and related software, with purchase costs depreciated over three years. Staff costs are salaries and benefitsfor the infrastructure staff. Most SAP shops have mirrored their production database capacity