MicrosoftDynamicsAX成功案例――美国维.

Microsoft Dynamics® AXTracing Dynamics AX 2009 Role Center KPI’sSummary: This document explains how to trace the data displayed in a Role Center page KPI to its source in the Microsoft Dynamics AX online transaction processing (OLTP) database.Author:Catherine McDade, Support Escalation EngineerDate Published: January, 2010Table of ContentsIntroduction (3)Terminology (4)KPI walkthrough (9)Description of KPI example (9)Step-by-step (9)Appendix A: Useful links (31)IntroductionThe prominent place of key performance indicators (KPIs) in Microsoft Dynamics AX 2009 Role Center pages has prompted questions about where the KPI data is drawn from. This document explains how to trace the data displayed in a KPI to its source in the Microsoft Dynamics AX online transaction processing (OLTP) database.Microsoft Dynamics AX relies on SQL Server Analysis Services (SSAS) for its business intelligence processing. In the following sections, we define terms of importance for SSAS, and then provide an example of how to trace the data for a KPI on a Role Center page.TerminologyKey Performance Indicator (KPI)A Key Performance Indicator is a measurement for gauging business success, or, in other words, ameasure of business metrics against targets. For example, a Sales Amount KPI could show sales from the last quarter and display a green icon if you are at budget, yellow if you are within 5% of budget, and red if you are under 5% of budget.Online Analytical Processing (OLAP)OLAP systems (such as that supported by SSAS) aggregate and store data at various levels across various categories.FactsFacts are predominantly numeric measurements, such as price or quantity, and represent the key business metrics that you want to aggregate and analyze. Facts form the basis of calculations, and you often aggregate them for members of a dimension.DimensionsDimensions form the contexts for the facts, and define the aspects of a business by which the facts are aggregated. For example, Items could be a dimension, while Price and Quantity could be facts of that dimension.Data sourceA data source stores the connection information for an SSAS project and/or database. WithMicrosoft Dynamics AX, the project or OLAP database that you create has a data source that points to your Microsoft Dynamics AX OLTP database.Data source viewA data source view contains the logical model of the schema used by an SSAS database object.Data source views can filter, apply calculations, and create joins on objects in the data source. In the OLAP database that Microsoft Dynamics AX creates, most of the data source views are simply views of a specific table, though some views may include a SQL statement that contains filters, calculations, or joins.MeasuresA measure represents a column that contains quantifiable data, usually numeric, that can beaggregated. A measure is generally mapped to a column in a fact table. An example of a measure would be Sales Amount or Cost of Goods Sold (COGS).CubeCubes store summarized fact and dimension data in structures that are multidimensional (that is, containing more than the two dimensions found in spreadsheets and normal database tables).Dimensions define the structure of the cube, and measures provide the numeric values of interest to an end user.Microsoft Dynamics AX 2009 ships with the following 10 default cubes:∙Accounts Receivable∙Human Resources Management∙General Ledger∙Production∙Project Accounting∙Purchase∙Sales∙Customer Relationship Management∙Expense Management∙Accounts payableMultidimensional Expressions (MDX)MDX is a query language, analogous to Structured Query Language (SQL), that is used to retrieve multidimensional data from a cube.Business Intelligence Development Studio (BIDS)An integrated development environment (IDE) based on Microsoft Visual Studio 2005 or 2008 and used to create and modify business intelligence solutions. This is the tool that you use to view and/or modify your Dynamics AX OLAP project or database.ProjectIn BIDS, a project is a collection of objects that make up your OLAP database. BIDS stores the objects (cubes, dimensions, etc) as files in the file system. It is recommended that you create a project for your OLAP database so that when you are making changes you are not affecting the database until you deploy.Below is a screen shot of BIDS opened to a project, followed by two screen shots that label the various sections of the BIDS environment.Detail view of BIDS, left side:Detail view of BIDS, right side:KPI walkthroughDescription of KPI exampleThis section walks you through an example of how to determine the origin of KPI values. We will use screen shots as needed to illustrate procedures.Scenario: Your CEO views her Role Center and wants to know where the numbers for the Production Cost KPI are coming from.Step-by-step1.In the Microsoft Dynamics AX client, go to the User profiles form (Administration >Setup > User profiles). On the form find and select CEO in the Profile ID column andthen click the View Role Center button.2. For the Production KPIs click the Manage KPIs link.3. Click the edit button on Production cost (the pencil icon). It will tell you that this ispulling from the Production Cube and the Production Cost KPI.4. To look at the KPI open SQL Server Business Intelligence Development Studio (BIDS). Ifyou are running SQL Server 2005, BIDS can be found at Start > All Programs >Microsoft SQL Server 2005 > SQL Server Business Intelligence DevelopmentStudio. If you are running SQL Server 2008, BIDS can be found at Start > All Programs > Microsoft SQL Server 2008 > SQL Server Business Intelligence Development Studio.5. Open your OLAP database (File > Open > Analysis Services Database).6. On the Connect To Database form, select Connect to existing database. Enter thename of the SQL Server Analysis Services Server in the Server field. In the Database field, enter Dynamics AX.Note: By default your OLAP database is named Dynamics AX. If you have applied adifferent name, use that name for Dynamics AX in the step above.7. Open the Production cube in the Solution Explorer section of BIDS. Find ProductionCube, right-click, and select Open.8. Click the KPIs tab.9. In the KPI Organizer, click the Production Cost KPI to open its setup form.10. The Value Expression section tells you what data the KPI is displaying.For this KPI we see that it displays the following:[Measures].[Actual vs. Planned Consumption]“M easures” could be a calculated measure or a measure on the cube structure. It istypically a calculated measure, so click the Calculations tab for the Production cube. 11. On the Calculations tab, find the Script Organizer and click the Actual vs. PlannedConsumption calculation.12.You will see in the Expression section it is doing the following:IF(ISEMPTY([Measures].[Cost of Planned Consumption]) OR [Measures].[Cost of Planned Consumption] = 0,NULL,([Measures].[Cost of Actual Consumption] / [Measures].[Cost of PlannedConsumption]) * 100)13. If we break the above statement down we see that the first part is:[Measures].[Cost of Planned Consumption] OR [Measures].[Cost of Planned Consumption] = 0, NULLWhat this tells us is that if these values return zero we will report null, otherwise we will do the calculation on the next line. First we need to find out if the above statement would return a zero, as shown in the following steps.14.Begin with the first part of the MDX query, [Measures].[Cost of PlannedConsumption]. On the Calculations tab you should see that Cost of PlannedConsumption breaks down to the following:[Measures].[Planned Cost Amount] + [Measures].[Planned Cost Markup]15. The Planned Cost Amount is another calculated measure that does the following:([Measures].[Cost amount], [Production Level].[Level].&[1])16.Cost amount is not a calculated measure, so we go back to the Cube Structure tab andin the Measures pane find CostCalcuation > Cost amount.17. Right-click Cost amount and select Properties.18. Expand Source, then expand Source again. The TableID is PRODCALCTRANS and theColumnID is COSTAMOUNT.19. To verify where the data is pulled from, go to the Solution Explorer and right-clickDynamics AX under Data Source Views. Select Open.20. On the Dynamics AX data source view tab, find PRODCALCTRANS under Tables.21. Right-click PRODCALCTRANS and select Edit Named Query.22.If you didn’t have an Edit Named Query option, it would mean the data was being pulledthe PRODCALCTRANS table using the following select statement:select costamount from prodcalctransHowever, since this is a named query, we need to find where the COSTAMOUNT column is coming from. To do this, look through the column labeled Column, find COSTAMOUNT, and then look at the Table column to see the source table.23.We see that the COSTAMOUNT column is pulling data from the PRODCALCTRANS table.The SQL statement would be:select costamount from prodcalctrans24.Now we need to trace the second part of the calculated measure, which is [ProductionLevel].[Level].&[1]. Find Production level in the Hierarchies tab underDimensions. Expand Production level and then click Edit Production Level.25.The Production Level hierarchy should appear under Production Level. Right click Leveland select Properties.26.In the Properties window, expand NameColumn and then expand Source. The sourceTableID is PRODCALCTRANS_LEVEL and the ColumnID is COLLECTREFLEVEL.27.We now know the data source that OLAP is using, but we want to find out where data isbeing pulled from in the Microsoft Dynamics AX OLTP database. To do this we can open the Dynamics AX option under Data Source Views in Solution Explorer.28.Scroll to PRODCALCTRANS_LEVEL, right-click, and select Edit Named Query29.The SQL statement for this data source is:SELECT DISTINCT COLLECTREFLEVEL FROM PRODCALCTRANS30.We now have enough information to build a SQL statement that would reflect the OLAPquery we saw in step 24 ([Production Level].[Level].&[1]). Adding the level of “1”from the end of the statement yields the SQL statement:select * from prodcalctrans where collectreflevel=1bining SQL statements yields:select sum (costamount) from prodcalctrans where collectreflevel=132.Now return to the second part of the MDX query [Measures].[Planned Cost Markup]from step 14.On the Calculations tab, find Planned Cost Markup. We see that this calculated measure is defined by([Measures].[Cost Markup], [Production Level].[Level].&[1])33.On the Cube Structure tab, navigate to CostCalcuation and then to Cost Markup.34.Right-click and select Properties for Cost Markup.35.In the Properties window, expand Source and then Source again. The displayedTableID is PRODCALCTRANS and the ColumnID is COSTMARKUP.36.Return to the Data Source View and look at PRODCALCTRANS and the Cost Markupcolumn (as in steps 20 through 23). The SQL statement turns out to be:select costmarkup from prodcalctrans37.We already found the SQL for production level.level &1 in steps 24-30. Combiningthat with COSTMARKUP yields:select sum (costmarkup) from prodcalctrans where collectreflevel=138.Now you can take the sum of COSTAMOUNT and COSTMARKUP (using the results fromsteps 31 and 37) where collectionreflevel=1. If that value is zero, then the KPI is null.39.If the value is not zero, then we continue tracing the KPI using the second part of thestatement from step 12:[Measures].[Cost of Actual Consumption] / [Measures].[Cost of Planned Consumption]) * 10040.The Cost of Actual Consumption is a calculated measure that has the followingexpression:[Measures].[Realized Cost Amount] + [Measures].[Realized Cost Adjustment]41.In the first part of the statement, the Realized Cost Amount measure is:([Measures].[Actual cost amount], [Production Level].[Level].&[1])42.Now look up the Actual cost amount measure. To find this measure, go back to theCube Structure tab and find Actual cost amount under CostCalculation.43.If we look at the properties of Actual cost amount we find that the source TableID isPRODCALCTRANS and the ColumnID is REALCOSTAMOUNT.44.This gives us a SQL statement of:select realcostamount from prodcalctransIf we add the production level of 1 (which we already found in steps 24 to 30) the SQL statement for all of step 41 is:select sum (realcostamount) from prodcalctrans where collectreflevel=145.Go back to step 40 and look at the second part of the statement[Measures].[Realized Cost Adjustment]Realized Cost Adjustment is a calculated measure equivalent to:([Measures].[RealCostAdjustment], [Production Level].[Level].&[1])46.The source of RealCostAdjustment can be found by going back to the Cube Structuretab and finding RealCostAdjustment under CostCalculation.47.If we look at the properties of RealCostAdjustment, we find that the source TableID isPRODCALCTRANS and the ColumnID is REALCOSTADJUSTMENT. Adding the production level of 1, we would see a SQL statement such as:select sum(realcostadjustment) from prodcalctrans where collectreflevel=148.To derive Cost of Actual Consumption, we would add the results of steps 44 and 47.49.Next we trace the second part of the statement from step 39:[Measures].[Cost of Planned Consumption]This results in the expression:[Measures].[Planned Cost Amount] + [Measures].[Planned Cost Markup]50.[Measures].[Planned Cost Amount] is a calculated measure equivalent to:([Measures].[Cost amount], [Production Level].[Level].&[1])51.To find [Measures].[Cost amount], go back to the Cube Structure tab and find Costamount under CostCalculation.52.If we look at the properties of Cost amount, we find that the source TableID isPRODCALCTRANS and the ColumnID is COSTAMOUNT. Adding the production level of 1, we would see the SQL statement:select sum (costamount) from prodcalctrans where collectreflevel=153.Return to step 49 for the next part of the statement:[Measures].[Planned Cost Markup]This is a calculated measure equivalent to the expression:([Measures].[Cost Markup], [Production Level].[Level].&[1])54.To trace this measure, go back to the Cube Structure tab and find Cost Markup underCostCalculation.31 TRACING DYNAMICS AX 2009 ROLE CENTER KPI ’S55. If we look at the properties of Cost Markup , we find that the source TableID isPRODCALCTRANS and the ColumnID is COSTMARKUP. Adding the production level of 1,we see the SQL statement:select sum (costmarkup) from prodcalctrans where collectreflevel=156. The results for [Measures].[Cost of Planned Consumption] would be the sum of steps 52and 55.57. Therefore, the results for [Measures].[Cost of Actual Consumption] / [Measures].[Cost ofPlanned Consumption]) * 100 This means we have to divide the results from step 48 bythe results of step 56. Then we take that number and multiply it by 100 to get our actualvs. planned consumption which is what gives us the Production Cost KPI.After following these steps you should now know where the data that makes up the Production Cost figure on the KPI is coming from. You should also have learned how to trace a KPI so that you can determine where any KPI is pulling data from.Appendix A: Useful links∙ Microsoft Dynamics AX 2009 Business Intelligence Cube Reference Guide: /downloads/details.aspx?FamilyId=6A685DF3-912D-4545-B990-CD2283C159FB&displaylang=en∙ Role Center reference for Microsoft Dynamics AX: https:///dynamics/ax/using/ax_rolecenterreference.mspxReferences:∙The information above was taken from SQL Server books online. For more information on SSAS please go to /en-us/library/ms130214.aspx32 TRACING DYNAMICS AX 2009 ROLE CENTER KPI ’SThis document is provided “a s-is.” Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes. © 2009 Microsoft Corporation. All rights reserved.Microsoft Dynamics is a line of integrated, adaptable business management solutions that enables you and your people to make business decisions with greater confidence. Microsoft Dynamics works like and with familiar Microsoft software, automating and streamlining financial, customer relationship and supply chain processes in a way that helps you drive business success.U.S. and Canada Toll Free 1-888-477-7989Worldwide +1-701-281-6500/dynamics。

中卫大河机床有限责任公司利用Microsoft Dynamics AX改善企业管理、制定市场战略、加快改革发展脚步"通过Microsoft Dynamics AX系统，我们可以更快的做出重大决定，改变了行业格局，对我们来说意义非同一般。

”孙强宁夏中卫大河机床有限责任公司副总经理客户简介宁夏中卫大河机床有限责任公司成立于1965年，坐落于我国西北边陲的宁夏回族自治区中卫市，是我国集珩磨技术研究、开发与制造为一体的主导企业，是设计、制造珩磨机床、立式钻床、数控机床、组合和专用机床的国家大型二类企业，是全国机床工具行业三十二家骨干企业之一，是国内设计、生产珩磨机床最早、技术水平最高、品种最全、产量最大的生产厂家。

该公司的大河珩磨机床研究所，是国家珩磨机床唯一的专业研究机构。

公司产品遍布全国及世界六十多个国家和地区，在国内外市场占有率达到70%，享有极高声誉。

公司非常注重信息化建设，自九十年代以来先后投资购买了CAD、PCCAD、KMCAPP、SolidWorks等专业系统软件。

随着业务及管理数据量的剧增，公司需要建立一个可以实现数据集成、共享、转换的信息平台。

公司采用Microsoft Dynamics AX提供的良好的人机交互界面、科学的采购、生产计划及库存管理等强大的功能，充分利用其易集成、易开发的特点，在采购、库存、物料、计划生产、财务应收应付账款等业务方面实现了信息一体化，确保了企业信息流的完整、准确、及时，不但解决了该公司各部门业务以及管理上的诸多问题，而且为企业制定市场战略决策提供了可靠的数据来源，支持了企业的敏捷制造，提升了企业竞争力。

客户状况公司管理层清楚地意识到要提升企业竞争力，提高市场反映能力，就必须加强企业的信息化建设，尽快解决所有出现的问题。

于是管理层提出了为各生产环节的管理建立一个可以实现数据集成、共享、转换的信息平台的想法，并提出了信息化工程的总体目标：既通过一体化集成解决方案，在统一架构、统一BOM、统一数据库的前提下，两年内实现各业务系统集成，并保证信息流的完整、准确、及时，实现支持企业敏捷制造的目标。

微软公司案例1（第3章）与戴尔公司不同，微软公司选择的是差异化竞争战略。

微软公司成立于1975年，成立之初年收入只有2万美元。

1985年微软公司发行股票并上市交易，其后迅速发展成为全世界科技含量最高、发展速度最快的IT公司，至2006会计年度其销售收入高达442.82亿美元。

近年来微软公司的销售收入和净利润如表4-11所示。

微软公司如此惊人的业绩表现是得益于宽松的行业竞争环境吗?答案是否定的。

软件行业的竞争是十分激烈的，在操作系统上，Linux从全球范围内展开了对微软的合纵连横之势，逐步压缩着微软的空间；在浏览器上，火狐蓬勃兴起，严重威胁微软浏览器的市场份额；在搜索市场，Google高高在上，雅虎呼风唤雨，微软的MSN相形见绌；在即时通讯领域，也有美国在线和雅虎压阵，虽然微软宣布将和雅虎实现即时通讯互联互通，然而IBM已经先行一步与Google、雅虎和美国在线展开合作，微软被排除在外；此外，微软与甲骨文在通用软件领域的竞争由来已久，SAP的加入，使得微软的市场份额又面临着被吞噬的巨大压力；而在英特网接入领域，微软面临着美国在线和索尼的竞争。

那么在如此激烈的行业竞争下，微软为何能够取得飞速的发展?而且根据预测，微软的业绩增长势头还将得以维继，2007会计年度的预计销售收入将达495亿至505亿美元。

究其原因，微软的迅速发展与其成功地实施差异化战略是密切相关的。

微软的差异化战略体现在以下几个方面：⒈致力于技术创新，维护软件行业的领导地位。

技术创新是微软成长的基石。

对于软件企业而言，谁能够掌握更多的核心技术和行业标准，谁就能在产品研发和市场推广上占据先机。

为了保障微软能够掌握最为前沿的技术，微软不仅十分强调与学术研究界的联系，还十分注重自身的基础性研究工作。

微软早在1986年就做到了将新聘雇员的1/4．分配去做研究开发工作，并于1991年、1997年和1998年分别成立了美国硅谷研究院、欧洲剑桥研究院和亚洲研究院。

crm系统的成功案例CRM系统（客户关系管理系统）是一种通过整合和管理客户信息、实现销售预测和客户服务等功能的信息系统。

它可以帮助企业更好地了解客户需求、提高销售效率、增强客户满意度，从而提升企业的竞争力和盈利能力。

以下是一些成功的CRM系统案例。

1. Salesforce CRM：Salesforce是全球最大的CRM解决方案提供商之一，其CRM系统被广泛应用于各行各业。

例如，美国电信巨头AT&T使用Salesforce CRM来管理客户信息、提高销售效率和加强客户服务。

2. Zoho CRM：Zoho是一家提供云端CRM系统的公司，其CRM 系统被许多中小型企业采用。

例如，印度电商巨头Flipkart使用Zoho CRM来管理客户关系、跟踪销售机会和提供个性化的客户服务。

3. Microsoft Dynamics 365：微软的Dynamics 365是一款集成了CRM和ERP功能的综合性商业解决方案。

例如，德国汽车制造商宝马使用Microsoft Dynamics 365来管理全球范围内的销售渠道和客户关系。

4. HubSpot CRM：HubSpot提供的免费CRM系统受到了许多创业公司的喜爱。

例如，美国电动汽车制造商特斯拉使用HubSpot CRM来跟踪潜在客户、管理销售流程和提供个性化的客户体验。

5. Oracle CRM：甲骨文公司提供的CRM系统在全球范围内得到广泛应用。

例如，中国电商巨头阿里巴巴使用Oracle CRM来管理海量的客户信息、优化销售流程和提供个性化的营销活动。

6. SAP CRM：SAP是全球领先的企业管理软件提供商，其CRM系统在许多大型企业中使用。

例如，美国跨国制造商3M公司使用SAP CRM来集中管理全球客户信息、提高销售效率和加强客户服务。

7. SugarCRM：SugarCRM是一款开源的CRM系统，被许多中小型企业和非营利组织使用。

例如，联合国儿童基金会使用SugarCRM来管理全球范围内的捐赠者信息、跟踪项目进展和提供个性化的服务。

微软推出Microsoft Dynamics AX 2009
谢世诚
【期刊名称】《中国信息界-e制造》
【年(卷),期】2009(000)003
【摘要】@@ 意想不到的优惠价格、秉承微软易于使用的特性、非常容易定制开发、满足行业特别需求,是MicrosoftDynamics AX 2009的四大优势.2月25日,微软MBS事业部大中华区总经理孙志伟在Microsoft Dynamics AX 2009中文版在中国上市新闻发布会上对记者说.
【总页数】1页(P79)
【作者】谢世诚
【作者单位】
【正文语种】中文
【相关文献】
1.微软推出Microsoft Dynamics AX2009 [J], 无
2.Microsoft Dynamics AX 2009中文版应运而生 [J], 张华
3.Microsoft Dynamics AX2009中文版上市微软提升ERP用户工作效率 [J],
4.微软及合作伙伴放言Microsoft Dynamics AX创新价值 24个月内收回ERP实施投资 [J], 谢世诚
5.全新角色，Microsoft Dynamics AX 2009助力企业效率全面提升 [J], 邓纯雅因版权原因，仅展示原文概要，查看原文内容请购买。

数字化转型的跨国企业案例分享数字化转型是当今企业发展的趋势之一，许多跨国企业也积极参与其中，通过数字技术的应用来提升效率和创造价值。

本文将分享几个成功的跨国企业案例，剖析他们在数字化转型中的策略和经验。

首先，我们来看一家在云计算和人工智能方面取得显著成果的跨国企业——微软。

作为全球知名的科技巨头，微软早在数字化转型的初期就开始布局，并且一直保持着领先地位。

微软以其云计算平台Azure和办公软件套件Office 365为核心，通过将软件和服务从传统的本地部署转向云端，帮助企业实现更高的效率和灵活性。

此外，微软还在人工智能领域取得了突破，为企业提供了智能化的解决方案。

这些举措使得微软能够帮助企业实现数字化转型，并在竞争激烈的市场中保持竞争优势。

接下来让我们关注一下零售行业的跨国巨头沃尔玛。

随着电子商务的兴起和消费者需求的变化，沃尔玛积极加强和拓展其数字化能力。

通过建立完善的电子商务平台和物流体系，沃尔玛实现了线上线下的全面融合。

消费者可以通过沃尔玛的电子商务平台随时随地购物，并选择自己最方便的方式进行商品的交付。

此外，沃尔玛还利用大数据技术对消费者的购买行为进行分析，为其个性化推荐产品，提升购物体验。

这些数字化转型的举措使得沃尔玛能够更好地满足消费者需求，并在竞争激烈的零售市场中保持领先地位。

除了科技和零售行业，制造业也在数字化转型中发挥着重要作用。

举个例子，德国汽车制造商宝马集团通过数字化技术实现了智能制造。

他们在生产过程中引入了工业物联网和人工智能技术，实现了生产线的高度自动化和智能化。

通过数据采集和分析，宝马能够及时监测和调整生产过程，提高效率和质量，并且减少资源的浪费。

此外，宝马还积极探索智能驾驶和新能源汽车技术，为未来汽车行业的发展奠定基础。

这个案例展示了宝马在数字化转型中的成功经验，同时也体现了制造业在数字化转型中的巨大潜力。

总结起来，数字化转型对于跨国企业来说是一个迫切的任务。

通过应用云计算、人工智能、大数据等技术，企业可以提升效率、降低成本，并创造新的商业模式。

精益生产成功案例精益生产是一种管理理念和方法，旨在通过消除浪费，提高生产效率和品质，实现持续的改进和提升。

下面我们将介绍一些精益生产的成功案例。

1.丰田生产系统（TPS）：丰田汽车公司是精益生产的开创者。

TPS主要关注生产过程中的浪费和瑕疵，并通过“Just-in-Time”（即时生产）和“Jidoka”（自动停工）的原则，实现了高效的生产和优质的产品。

TPS的成功在于其对员工参与和持续改进的鼓励，以及对质量问题的立即回应。

2.通用电气：通用电气公司采用精益生产理念，优化了其生产流程和供应链管理。

通过分析和优化整个生产过程中的活动和环节，通用电气成功地减少了废品、库存和停工时间。

精益生产的应用帮助通用电气实现了高效生产和投资回报，同时提高了产品质量和客户满意度。

3.美国电子零件制造公司（AMEC）：AMEC是一家为全球电子制造企业提供电子零件生产和组装服务的公司。

AMEC采用了精益生产的原则，在生产流程中消除了多余的步骤和浪费。

该公司通过提高生产效率和质量，降低成本和交货时间，有效提升了其竞争力。

AMEC还鼓励员工积极参与，提供培训和奖励机制，以促进持续改进和创新。

4.日本曙光灯泡公司：日本曙光灯泡公司是一家生产灯泡和光源产品的公司。

该公司采用精益生产的原则，通过持续改进和创新，实现了生产效率的提高和成本的降低。

曙光灯泡公司注重员工的培训和参与，鼓励他们提出改进建议，并将其纳入生产流程中，以实现更好的效果。

通过精益生产的应用，曙光灯泡公司成功地提高了生产效率和产品质量，同时降低了生产成本。

5.伊顿公司：伊顿公司是一家全球性的动力管理企业，采用精益生产的原则优化了其生产和供应链管理。

伊顿通过减少库存、提高生产效率和质量，实现了较高的客户满意度和市场份额。

该公司还通过精益思维培养了员工的持续改进意识和能力，并鼓励他们参与决策和问题解决过程。

以上是一些成功应用精益生产的案例，这些企业通过消除浪费、提高效率和质量，实现了更高水平的竞争力和持续的发展。

关键成功因素法案例3个关键成功因素法(key success factors， KSF)是信息系统开发规划方法之一，由1970年由哈佛大学教授William Zani提出。

以下是店铺为大家整理的关于关键成功因素法案例，欢迎阅读!关键成功因素法案例1：“只买对的，不买贵的”，一句广告词，代表了目前社会群众的商品购买意识，随着时代的发展，电脑像家电一样正在走进千家万户，如何既能满足自己的功能要求，又能省钱地买下一台电脑成为大众关心的话题。

从系统的观点，以关键成功因素法为手段，描述电脑选购的过程，以期给用户一个公式化流程解决电脑选购问题。

一、关键成功因素法关键成功因素法(Critical Success Factors，CSF)于1970年由哈佛大学教授william Zani提出，它是信息系统规划重要方法之一，其含义是以关键因素为依据来确定系统信息需求的一种管理信息系统总体规划的方法，即在现行系统中，总存在着多个变量影响系统目标的实现，其中若干个因素是关键的和主要的(即成功变量)，通过对关键成功因素的识别，找出实现目标所需的关键信息集合，从而确定系统开发的优先次序。

关键成功因素法按如下四个步骤进行：系统目标的分解和识别、所有成功因素识别、关键成功因素识别和确定关键成功因素的性能指标或评估标准。

识别关键成功因素，就是要识别联系于系统目标的主要数据、处理逻辑及其关系。

在选购电脑方面，按照关键成功因素法的四个步骤，我们首先应该定义目标，即弄清楚采买这台电脑是干什么用的，这些用途可能包括办公、学习、娱乐和特殊用途;其次我们要将方方面面的需求转化为成功因素，即用成功因素来描述用户的需求;第三步就是确定关键成功因素，成功购买电脑的关键因素当然是用最少的钱买到最高性能的机器，除此之外，我们还要考虑信息技术的发展规律，在满足性能要求的前提下，机器的档次如何确定;最后一步，就是识别关键成功因素的性能指标或评估标准，即用什么技术指标和标准来衡量关键成功因素，并据此生成数据字典，即产生购买电脑的一些具体数据，用于采买的实施。

Microsoft Dynamics AXMicrosoftProduct availability, localization, and translation guideMicrosoft Dynamics AXT able of contents03 Availability 04 Languages06 Country localizations08 Overview of availability and languages 10 Localization and translation overview 11 Channel partner-created solutionsProduct availability, localization, and translation guideMicrosoft Dynamics AXAvailabilityMicrosoft Dynamics AX is localized, translated, and supported by Microsoft and made generally available in the countries † listed below. To learn more about supported versions of Microsoft Dy-namics AX localized and/or translated by Microsoft, refer to the product availability tables below. In addition to country-specific localizations and/or translations that Microsoft creates, our chan-nel partners may make partner-created localizations and/or trans-lations of Microsoft Dynamics AX available in countries where Mi-crosoft does not provide a localized or translated version. See the Localization and translation overview below for more information on partner-created solutions.LanguagesTranslation is the process of adapting soft-ware or documentation to meet languagerequirements for a particular country. For any given language, Microsoft may translatesome, all, or none of the user interface (UI) and documentation for Microsoft DynamicsAX. Contact your channel partner or the lo-cal Microsoft office for more information.MicrosoftLanguages Countries Arabic‡ Saudi Arabia Chinese (Simplified) China CzechCzech Republic Danish DenmarkDutchBelgium, Netherlands EnglishAustralia, Canada, India, Ireland, Malaysia, NewZealand, Singapore, South Africa, UK, US Estonian Estonia Finnish FinlandFrenchBelgium, Canada, France, Switzerland GermanAustria, Germany, Switzerland Hungarian Hungary Icelandic IcelandItalianItaly, Switzerland Japanese Japan Latvian Latvia Lithuanian LithuaniaNorwegian Bokmål Norway Polish Poland Portuguese Brazil Russian Russia Spanish Mexico, Spain Swedish Sweden Thai Thailand Turkey Turkishtranslated into the languages listed below at the time of General Availability.*‡Will be shipped in an updateCountry localizationsLocalization is the process of adaptingsoftware to meet country-specific laws or regulations.Microsoftincludes specific localizationsfor these countries.Country localizations included at GeneralAvailability date*Australia, Canada, Denmark, France, Germany, Iceland, Ireland, Japan, Malaysia, Mexico, NewZealand, Singapore, South Africa, The Neth-erlands, United Kingdom, and United StatesCountry localizations included in later updates*Austria, Belgium, Brazil, China, Czech Re-public, Estonia, Finland, Hungary, Italy, Lat-via, Lithuania, Norway, Poland, Saudi Arabia,Spain, Sweden, Switzerland, and ThailandCountry localizations included in the second update*India and RussiaMicrosoft Dynamics AXLocalization and translation overviewOrganizations doing business in a par-ticular country must comply with coun-try-specific laws, regulations, and com-mon business practices to handle their daily business transactions and opera-tions and meet their legal obligations for activities conducted in the country. Microsoft recognizes that non-adher-ence to these laws and regulations can lead to severe consequences for an or-ganization doing business in that coun-try.As an enterprise resource planning (ERP) solution, Microsoft Dynamics AX helps organizations manage their vari-ous business processes through its ex-tensible architecture. Microsoft extends the business process functionality of its Microsoft Dynamics AX by developing specific commercial requirements, lan-guage, and non-vertical, national, or international functionality to address specific tax, accounting, or financialreporting requirements for countrieswhere Microsoft makes Microsoft Dy-namics AX generally available.Laws and regulations vary by country.While Microsoft Dynamics AX “out-of-the-box” is localized and/or translatedto address specific laws and/or regula-tions for particular countries, it is notsupported in terms of localizations,translations, or technical support in allcountries. Features or functionalitiesthat are available in a particular coun-try may not be available in all countries.Microsoft Dynamics AX also does notsupport all statutory or regulatory re-quirements in a specific country, espe-cially those specific for states, provinc-es, municipalities, or certain industriesand verticals.Rather, we look to our channel partners,who are an important part of our globalstrategy, to deliver Microsoft DynamicsAX solutions that help customers meettheir compliance obligations. Channelpartners may adapt the Microsoft Dy-namics AX to:• Supplement Microsoft Dynamics AX bydeveloping functionality to meet spe-cific laws or regulations that are notcovered by features Microsoft provides”out-of-the-box” (e.g., regulations thatare unique to states, provinces, cities,or municipalities in a particular coun-try); or• Create their own localizations and/ortranslations for countries where Mic-rosoft does not offer a localized and/or translated version of Microsoft Dy-namics AX.Partner-created solutions are owned,implemented, maintained, and ser-viced by, or on behalf of, the originatingchannel partner.MicrosoftMicrosoft Dynamics AXMicrosoft Dynamics AXNotes1. Microsoft Dynamics AX may be available in this country as a partner-created solution at a future date. Contact your local Microsoft office for more information. In Turkey, Microsoft Dynamics AX 2012 is available through the Microsoft Dynamics Turkey Partners Alliance. Contact the local Microsoft office in Turkey for more information.2. Contact local Microsoft offices in Thailand for information on Microsoft Dynamics channel partners that have their own product certification from the Thailand Revenue Department and for the software house ID number and the sequence number. These numbers are required for each customer installation in a live operating envi-ronment to meet the certification requirements of the Thailand Revenue Department.3. Contact Microsoft’s offices in Thailand to apply for a customer sequence number. This number is required for each customer installation in a live operating environment to meet the certification requirements of the Thailand Revenue Department.4. The mainstream support date for Microsoft Dynamics AX 2009 has been extended to April 10, 2018. Custom-ers who remain current on the Microsoft Dynamics Enhancement Plan will continue to receive all of the valued benefits of the Enhancement Plan, including regulatory updates and hotfixes, with the following two exclusions: (1) Support for Microsoft Dynamics AX 2009 Brazil point of sale functionality according to the PAF-ECF “ATO COTEPE/ICMS N° 6” of 14-Apil-2008 (updated by “ATO COTEPE/ICMS 51” of 29-November-2011); (2) Support for Brazil Fiscal book reporting through the integration between Microsoft Dynamics AX 2009 and the fiscal book solution licensed from SoftTeam. Customers that want to continue on SoftTeam’s Fiscal Books solution must contact Sonda do Brasil S.A. and negotiate support directly. For additional details, please visit the Support Lifecycle Policy website by clicking here.5. Additional online services are hosted by Microsoft and additional charges may apply for these services. See- for more information.6. For information about Fiscal printer integration and EFT availability for Microsoft Dynamics AX 2012, please access the “Brazil Localization Scope Document” at https:///customersource/Global/AX/ learning/documentation/white-papers/ax2012r2_scopeofbrazilianlocalization0519.7. Microsoft Dynamics AX is available with language support only. Microsoft does not offer a localized version for this country.8. Retail localization for Microsoft Dynamics AX for Malaysia, Sweden, Poland, Czech Republic, Hungary, Latvia, Lithuania, Estonia and Brazil will be available in later updates.9. MPOS for Win8 is not localized for Sweden, Russia and Brazil. Online Store is not localized for Russia and Brazil. Retail Essentials for Microsoft Dynamics AX 2012 R3 are available only through Retail Realm. Please *********************************@.*General Availability for the next version of Microsoft Dynamics AX is expected during Q1 of CY2016. The of-fering will be updated on a regular cadence and the dates will be announced in advance through the normal Microsoft channels. If you deploy Microsoft Dynamics AX in a country where Microsoft has not made a local-ization available you will need to re-implement the software, at your expense, if and when Microsoft makes a localization for that country available.Notice and disclaimerThis content is provided for information purposes only and is subject to changewithout notice. It is provided “as is” and is not warranted to be error-free. This in-formation is not intended to constitute tax, accounting, legal or other professionaladvice or to be used as a substitute for specific advice from your channel partneror a licensed professional. You should not act (or refrain from acting) based oninformation in this document without obtaining professional advice about yourparticular facts and circumstances. Microsoft does not make any representation,warranty (express, implied or otherwise) or assurance about the performance orsuitability of any localized and/or translated version of Microsoft Dynamics AXused outside the country in which Microsoft makes that software generally avail-able, including implied warranties of merchantability or fitness for a particular pur-pose. Although Microsoft may refer to its channel partners as “partners”, they areindependent entities. There is no partnership, joint venture, agency or franchiserelationship or fiduciary duty between Microsoft and its channel partners. Channelpartners are solely responsible for any configurations, customizations, localiza-tions and/or translations they create or implement on behalf of customers, in-cluding any support or other service they provide to customers for such solutions.Microsoft does not warrant or guarantee partner-created solutions and disclaimsany and all liability arising out of any partner-created solution and/ or service† Use of the word country is for convenience only and is not intended to imply sover-eignty for any disputed territory that may be mentioned herein.Click here to visit the MicrosoftDynamics MarketplaceChannel partner-created solutionsFor additional information about part-ner-created solutions in your country,please contact your Microsoft channelpartner or local Microsoft office, orutilize the Microsoft Dynamics Market-place to identify channel partner solu-tions that might be available in yourcountry.© 2016 Microsoft Corporation. All rights reserved. This document is provided "as-is." Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Some examples are for illustration only and are fictitious. No real association is intended or inferred.This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.All dates, features, and descriptions specified are preliminary, are based on current expectations, and are subject to change at any time without notice.Microsoft Dynamics AXMicrosoft Dynamics AXMicrosoft。