Question

高分&追分！生产管理或ERP的英文文献，最好有中文翻译！

高分&追分！生产管理或ERP的英文文献（或文章），最好有中文翻译！英文字符8000~12000。

答案如果符合要求，有追分！

Answer 1

我的有译文的！！！我会私下发给你，因为这是我的毕业论文，怕同学的和我重复。。。
我的是到图书馆借书之后文字识别的，相信翻译的没问题。

我第一次回答问题，一定要把分数给我啊！我也要加分！

The Adaptability for Production Change of Team
团队的生产变革适应能力

Ⅰ.Get lost in the fog of change——Paint a picture of what is happening
The manager of a team has an unique perspective . He or she has a wider view of the organization than team members have . The manager also is closer to information from higher levels in the organization . This extensive vantage point plays a critical role in changing times .
一、在变革的迷雾中丧失方向——把现状勾勒出来
团队的经理人拥有一个独特的视角。对于组织，他比其团队成员看得更广，也更易接团织组近来自组织更高层的信息。这个更宽广的视野在变革中扮演了很重要的角色。

Answer 2

http://www.sogou.com/sohu?query=%C9%FA%B2%FA%B9%DC%C0%ED%D7%CA%C1%CF&num=10&pid=01001400&duppid=1&insite=

Answer 3

Management problems
Integrated project team planning
Managed communications across many people
A formal decision-making process
An integrated test plan and managed test process
Applying lessons learned from earlier implementations to later implementations
User problems
Technical problems
ERPComplexity造成的问题二
Management problems
User problems
People obstacles, 62%
Business process issues, 16%
Information technology (technical issues), 12%
Technical problems
ERPComplexity造成的问题三
Management problems
User problems
Technical problems
Nonrobust and incomplete ERP packages
Complex and undefined ERP-to-legacy-system interfaces
Middleware technology bugs
Poor custom code
Poor system performance
ERP Intractable的原因[3]
Reliability
Big-bang seduction
Overeager customization
Cultural hurdle
ERP 的Hidden Costs [3]
Training
Transition
Prolonged schedule
Sparing the best
Delayed ROI (Return on Investment)
Model-Based Architecting and Software Engineering[3]
Success model
Technological vs. comprehensive
Product model
Monolithic vs. Unitized
Process model
Big-bang vs. incremental
Model of Risk Factors[2]
External Business Context
Organization Context
IS Context
Enterprise System Project
Model of Risk Factors in ES Implementation [2]
FoxMeyer vs. Dow Corning之一[2]
FoxMeyer vs. Dow Corning之二[2]
FoxMeyer vs. Dow Corning差异[2]
Organizational culture
Dow Corning has an open culture- communications
FoxMeyer less open - forced by a contract with UHC in 90 days
Use of Consultants
FoxMeyer-Andersen
Dow Corning - no consultant, but ask for SAP's help
Project leadership
FoxMeyer- no steering committee nor strong PM
Dow Corning- VP + planning committee
Model-based analysis
FoxMeyer's reaction to Environment Change
Down Corning's ability to withstand environmental change
Project Resolution by Type [4]
Type I Successful 16.2%
Completed on time and within budget
All required functions and features initially specified
Type 2 Challenged 52.7%
Completed and operational
Suffered budget overruns and/or program slips
Offered fewer functions and features than originally specified
Type 3 Impaired 31.1%
Cancelled or abandoned at some point of the life cycle
IS Failure by Lyytinen and Hirschheim [4]
Correspondence failure
objective
Process Failure
Budget and time schedule
Interaction Failure
User usage, attitudes and satisfaction
Expectation Failure
Meet the stakeholders' requirements, expectations or values.
其它高失败率的IS导入
资料仓储系统(Wixom and Watson, 2002)
1/2到2/3 是失败的
客户关系管理系统(Payton and Zahay, 2003)
50%-70%是失败的
供应链管理系统(Elmuti, 2002)
仅2%厂商认为自己的SCM是世界级的
参考文献
Krasner, H. (2000). Ensuring E-Business Success by Learning from ERP Failure, IEEE IT Pro, January/February, pp. 22-27.
Scott, J. E. and Vessey, I (2002). Managing Risks in Enterprise Systems Implementations, Communications of the ACM, Vol. 45, No. 4, pp. 74-81.
Vogt, C. (2002). Intractable ERP: A Comprehensive Analysis of Failed Enterprise-Resource-Planning Projects, Software Engineering Notes, Vol. 27, No. 2, pp. 62-68.
Yeo, K. T. (2002). Critical Failure Factors in Information System Projects, International Journal of Project Management, Vol. 20, pp. 241-246.
参考文献-ERP
Krasner, H. (2000). Ensuring E-Business Success by Learning from ERP Failure, IEEE IT Pro, January/February, pp. 22-27.
Scott, J. E. and Vessey, I (2002). Managing Risks in Enterprise Systems Implementations, Communications of the ACM, Vol. 45, No. 4, pp. 74-81.
Vogt, C. (2002). Intractable ERP: A Comprehensive Analysis of Failed Enterprise-Resource-Planning Projects, Software Engineering Notes, Vol. 27, No. 2, pp. 62-68.
Yeo, K. T. (2002). Critical Failure Factors in Information System Projects, International Journal of Project Management, Vol. 20, pp. 241-246.
参考文献-Others
Wixom, B. H. and Watson, H. J. (2001), An empirical investigation of the factors affecting data warehousing success, MIS Quarterly; 25(1), pp. 17-41.
Payton, F. C. and Zahay, D. (2003), Understanding Why Marketing Does not Use the Corporate Data Warehouse for CRM Applications, Journal of Database Management; 10(4), pp. 315-326.
Elmuti, D. (2002), The perceived impact of supply chain management on organizational effectiveness, Journal of Supply Chain Management; 38(3), pp. 49-57.