項(xiàng)目起步內(nèi)培

1、議程集成項(xiàng)目的實(shí)施風(fēng)險(xiǎn)與對(duì)策概述集成項(xiàng)目的實(shí)施方法論1集成項(xiàng)目實(shí)施的風(fēng)險(xiǎn)（1）管理風(fēng)險(xiǎn)業(yè)務(wù)需求在分析階段還不確定，拖延分析時(shí)間,更糟糕的是在整個(gè)工程階段還在不斷更改需求；多單位合作關(guān)系,沒(méi)有明確的分工和責(zé)任劃分; 應(yīng)用開(kāi)發(fā)團(tuán)隊(duì)、系統(tǒng)集成團(tuán)隊(duì)的建議和企業(yè)各部們之間欠配合;難以平衡業(yè)務(wù)集成需要和對(duì)短期績(jī)效的追求；過(guò)渡計(jì)劃啟動(dòng)過(guò)遲；缺乏整體EAI/BPI戰(zhàn)略和計(jì)劃, 沒(méi)有高層推動(dòng)和領(lǐng)導(dǎo)，資源和效率都得不到保障。應(yīng)用系統(tǒng)項(xiàng)目實(shí)施的拖延影響到EAI/BPI的進(jìn)度；2集成項(xiàng)目實(shí)施的風(fēng)險(xiǎn)應(yīng)對(duì)（1）管理風(fēng)險(xiǎn)的對(duì)策業(yè)務(wù)需求在分析階段還不確定，拖延分析時(shí)間,更糟糕的是在整個(gè)工程階段還在不斷更改需求；必須確認(rèn)業(yè)務(wù)需

2、要達(dá)到的目的,以業(yè)務(wù)部門的需求緩急，心理準(zhǔn)備程度來(lái)安排業(yè)務(wù)整合項(xiàng)目的優(yōu)先次序，并對(duì)其有深入透徹和完整精確的需求理解分析，并獲得業(yè)務(wù)部門的共識(shí)，業(yè)務(wù)部門對(duì)共識(shí)做出承諾. 3集成項(xiàng)目實(shí)施的風(fēng)險(xiǎn)應(yīng)對(duì)（2）管理風(fēng)險(xiǎn)的對(duì)策多單位合作關(guān)系,沒(méi)有明確的分工和責(zé)任劃分; 明確各單位在整個(gè)項(xiàng)目中的角色, 不同角色具有不同的權(quán)利和責(zé)任. 清晰確定各單位之間的接口. 組織結(jié)構(gòu)先行, 具有組織就具有生命力.應(yīng)用開(kāi)發(fā)團(tuán)隊(duì)、系統(tǒng)集成團(tuán)隊(duì)的建議和企業(yè)各部們之間欠配合;組建項(xiàng)目管理團(tuán)隊(duì), 統(tǒng)一協(xié)調(diào)，培養(yǎng)相互尊重的過(guò)程文化和伙伴合作關(guān)系是項(xiàng)目成功的關(guān)鍵。項(xiàng)目成功是共同的成功, 失敗是共同的失敗.4集成項(xiàng)目實(shí)施的風(fēng)險(xiǎn)應(yīng)對(duì)（3）管

3、理風(fēng)險(xiǎn)的對(duì)策難以平衡業(yè)務(wù)集成需要和對(duì)短期績(jī)效的追求規(guī)劃好工程的規(guī)模和實(shí)施順序，從而迅速地獲得最大程度的商業(yè)回報(bào) .過(guò)渡計(jì)劃啟動(dòng)過(guò)遲；過(guò)程伊始就把新舊系統(tǒng)過(guò)渡提到議事日程;在分析，設(shè)計(jì)階段要充分考慮解決方案的可移植性。在系統(tǒng)測(cè)試階段前必須制定新舊系統(tǒng)過(guò)渡方案，充分考慮新舊系統(tǒng)的差別，評(píng)估新舊系統(tǒng)移植的風(fēng)險(xiǎn)，制定新舊系統(tǒng)切割步驟。在系統(tǒng)測(cè)試階段，做過(guò)渡測(cè)試，仿真，做過(guò)渡試點(diǎn);在上線前對(duì)作業(yè)人員作充分培訓(xùn)，由專職機(jī)構(gòu)，有效協(xié)調(diào)過(guò)渡計(jì)劃和作業(yè)。 5集成項(xiàng)目實(shí)施的風(fēng)險(xiǎn)應(yīng)對(duì)（4）管理風(fēng)險(xiǎn)的對(duì)策缺乏整體EAI/BPI戰(zhàn)略和計(jì)劃高層領(lǐng)導(dǎo)推進(jìn)非常關(guān)鍵。EAI/BPI項(xiàng)目會(huì)觸發(fā)一些困難的問(wèn)題，而承擔(dān)責(zé)任的這位高級(jí)

4、管理人員就可以及時(shí)處斷 。企業(yè)建立管理小組, 必須制定企業(yè)EAI/BPI從啟動(dòng)到上線維護(hù)的長(zhǎng)期戰(zhàn)略和計(jì)劃，了解和指導(dǎo)EAI/BPI項(xiàng)目進(jìn)程，規(guī)劃公司的未來(lái)。 應(yīng)用系統(tǒng)項(xiàng)目實(shí)施的拖延影響到EAI/BPI的進(jìn)度多個(gè)項(xiàng)目并行，項(xiàng)目之間相互關(guān)聯(lián)和依賴，涉及到多個(gè)業(yè)務(wù)領(lǐng)域和部門，并需要采用多種技術(shù)手段。 建議:采用分步分階段策略,降低管理復(fù)雜度和技術(shù)難度.6集成項(xiàng)目實(shí)施的風(fēng)險(xiǎn)（2）技術(shù)風(fēng)險(xiǎn):實(shí)施團(tuán)隊(duì)缺乏技術(shù)支撐；缺乏可行的EAI/BPI實(shí)施技巧；集成系統(tǒng)上的再集成；沒(méi)有充分發(fā)揮全新的集成信息的威力，對(duì)新系統(tǒng)不太適應(yīng)7集成項(xiàng)目實(shí)施的風(fēng)險(xiǎn)應(yīng)對(duì)（5）技術(shù)風(fēng)險(xiǎn)的對(duì)策實(shí)施團(tuán)隊(duì)缺乏技術(shù)支撐要有技術(shù)保障方案和措施。不

5、嗇使用EAI技術(shù)專才，并訓(xùn)練自己的技術(shù)人員。保證企業(yè)內(nèi)部的業(yè)務(wù)尖子的參與。缺乏可行的EAI/BPI實(shí)施技巧 必須有一個(gè)適合業(yè)務(wù)流程開(kāi)發(fā)特點(diǎn)的，容易掌握的，EAI/BPI實(shí)施技巧為項(xiàng)目指導(dǎo)。一個(gè)有效的管理小組來(lái)客戶化，制定實(shí)施指導(dǎo)規(guī)范，推行實(shí)施技巧。建議對(duì)實(shí)施每個(gè)環(huán)節(jié)都給出指導(dǎo)意見(jiàn).8集成項(xiàng)目實(shí)施的風(fēng)險(xiǎn)應(yīng)對(duì)（6）技術(shù)風(fēng)險(xiǎn)的對(duì)策集成系統(tǒng)上的再集成在選擇平臺(tái)時(shí)，公司應(yīng)該首先考慮兼容性其架構(gòu)整體性，平臺(tái)的開(kāi)發(fā)要保證構(gòu)架整體性，運(yùn)行優(yōu)化必須始終是一個(gè)開(kāi)發(fā)過(guò)程的衡量指標(biāo)。 建議:選擇可靠的, 開(kāi)放的, 靈活的, 可適應(yīng)環(huán)境變化的集成基礎(chǔ)平臺(tái).沒(méi)有充分發(fā)揮全新的集成信息的威力，對(duì)新系統(tǒng)不太適應(yīng)EAI/BPI

6、項(xiàng)目30%的挑戰(zhàn)來(lái)自技術(shù)層面，而剩余的70%則來(lái)自人員和流程。全新的EAI/BPI技術(shù)會(huì)影響許多人員，他們需要培訓(xùn)以掌握新的業(yè)務(wù)流程和操作工具。企業(yè)必須通過(guò)詳細(xì)計(jì)劃、試點(diǎn)試用、內(nèi)部教育和風(fēng)險(xiǎn)分析等一系列手段，來(lái)減少這種情況發(fā)生的可能性.企業(yè)必須充分認(rèn)識(shí)到項(xiàng)目上線最初的這段適應(yīng)期的存在，如果執(zhí)行得當(dāng)，那么這種負(fù)效果可以減低到最小，而且在最短的時(shí)間內(nèi)消除。 9議程集成項(xiàng)目的實(shí)施風(fēng)險(xiǎn)與對(duì)策概述Vitria集成項(xiàng)目的實(shí)施方法論Vitria B2B成功案例海外推項(xiàng)目推動(dòng)的建議風(fēng)險(xiǎn)與對(duì)策機(jī)制的預(yù)先建立三方公認(rèn)的項(xiàng)目開(kāi)展原則明確第一階段目標(biāo)10Implementation ApproachProject S

7、tructureOur implementation approach consists of five project stages:Initiate Communicate project goals, methodology and team structure, establish project charter, and determine business requirements.Analyze Bridge the gap, if any, between customer requirements and Vitria Cleanorder capabilities, as

8、well as defining business processes and interfaces.Design/Build Functional and technical development and realization of the systems architecture and configurationIntegrate Rigorous testing and in preparation for the deployment.Deploy Successfully executed implementation and operations support.Each s

9、tage is defined in terms of key tasks, deliverables, tools and techniques and customer benefits 11Implementation Approach Implementation PlanInitiateAnalyzeDesign/Build Integrate DeployDana ParallelTestProject Weeks 1 2 3 4 5 6 7 8 9 10 11 12Initiate Establish project charter Confirm/identify requir

10、ements Set up the technical environmentAnalyze Use case analysis Connectivity and mapping analysis Test plan developmentDesign/Build System design Data transformation/mapping System implementationIntegrate Test preparation Test execution Test acceptanceDeploy Procedure/script preparation System depl

11、oyment12Implementation Approach Implementation - InitiateKey TasksDeliverablesTools and TechniquesBenefits Confirm the project scope Define roles and responsibilities Create project work plan and staffing plan Create communication plan Define high-level requirements Setup the technical environment D

12、etailed project work plan Project approach orientation Skill matrix of Fast Forward team High-level business/user and system/performance requirementsChange management procedure Project/deliverable standards and templates Project management toolkit including: Estimating tools Work plans and status re

13、ports Issue resolution protocol VIP methodology Upfront buy-in and agreement to project structure, expectations and approach Confirm scope and requirements early in the project Early setup of the technical environmentThe initiate stage focuses on communicating the project goals, methodology, and tea

14、m structure, establishing project charter and determining business requirements.InitiateAnalyzeDesign/BuildIntegrateDeploy13Implementation Approach Implementation AnalyzeKey TasksDeliverablesTools and TechniquesBenefitsAnalyze business processes (incl. exceptions) Analyze data validation requirement

15、s Analyze application connectivity requirements Analyze data transformation requirements Analyze reporting and audit information Develop and document use cases Develop test strategy and test plan Requirements specification document Sequence diagrams/collaboration models Data models fit/gap analysis

16、summary Interface specifications Documentation of system requirements Test strategy and test plan checklist Enterprise production checklist Fit/gap analysis tools Pre built process baseline models Pre Built Mapping Guides Test plan / execution checklist Early identification of risks and issues Exten

17、sive hands-on business owner/user participation fosters system ownershipPre built baseline reduces overall implementation timeframe.The analyze stage focuses on bridging the gap, if any, between customer requirements and the BusinessWare capabilities, as well as defining business processes and inter

18、faces.InitiateAnalyzeDesign/BuildIntegrateDeploy14 Unit-tested components (process models, connectors, reports, etc.) Data transformation maps (5) Testing environment checklist Design specification documentProject suggested standards documentSystem ready for integration testing (BPM, EDI Documents,

19、Transformations, Error Handling, Audit Control, Configuration).Implementation Approach Implementation Design/BuildKey TasksDeliverablesTools and TechniquesBenefits Load and configure process models and channel architecture Load and configure connection models and system reports Configure trading par

20、tner relationship Create data transformation maps Document system design specifications Unit test all componentsInitiateAnalyze Pre-built process modelsLogical Mapping guidesBusinessWare Tools and Best Practice Methods Incremental UML based (VIP) methods Shorter development cycle resulting from pre-

21、built baseline processing models.Extensive domain expertise Knowledge transfer with customer involvementDesign/BuildThe design/build stage focuses on the functional and technical development and realization of the systems architecture and configuration.IntegrateDeploy15Implementation Approach Implem

22、entation IntegrateKey TasksDeliverablesTools and TechniquesBenefits Develop test objectives and test plan Develop test cases and generate test data Setup the test environment Conduct system and integration testing Prepare the deployment environmentInitiateAnalyze Test checklist, test cases and sampl

23、e test data System and integration test results Deployment plan and readiness checklistSupport through testing Test plan template documents Stress & load test planner Test data samples Deployment readiness checklist Continued transfer of knowledge through user/operator participation in testing proce

24、ssThoroughly tested application provides solid foundation for deploymentConfirmation that system is ready to accept/send valid documentsDesign/BuildIntegrateDeployThe integrate stage focuses on rigorous testing and in preparing for the deployment.16Implementation Approach Implementation DeployKey TasksDeliverablesTools and TechniquesBenefits Identify operations procedures Develop operations support scripts Review the operations procedures and scripts with the application support staff Monitor performance and tune accordinglyInitiateAnalyze Operati