IT Strategy資訊科技策略

When an organization evaluates several Enterprise Application (EA) Vendors and zeros in on a suite, they will begin to notice that all the elements of their firm’s ‘value chain’ cannot be mapped to the business process modules provided by that EA. What it mean is that the EA Suite cannot be used ‘as is’ for every module like CRM, ERP, SCM or SRM etc. to support the firm’s business structure. That is a good sign, because if the EA is used without customization (but only with some configuration) to support every functional organizations then it clearly indicates that the firm does not have a competitive advantage compared to its competitors. It is impossible for an EA vendor to build every possible variations of business organization’s value chain even though the vendors sell it with that promise. Think of it this way, if you can use a generic EA with some configuration to map to your business processes then any organization with the right resources will be able to duplicate your effort and thus eroding your firm’s ‘economic moat’. Granted that some of the modules like SCM, ERP or HR can be your non core activities and these modules can be used with no customization. But for your core activities, EA should not be used ‘out of the box’. As mentioned in my blog 當一個組織的評估幾個企業應用（ ea ）條廠商和零點，在一個套間，他們將開始看到的所有要素，他們堅定的 ' 價值鏈'不能映射到業務流程模塊所提供的電針是什麼它的意思是說，環境評估套件不能用'是 ' ，為每一個模塊一樣，客戶關係管理，企業資源規劃，供應鏈管理或開關磁阻電機等，以支持該公司的業務結構，這是一個好兆頭，因為如果環境是沒有用的定制（但僅限於某些配置） ，以支持每一個功能性組織，那麼它清楚地表明，公司並不具有競爭優勢相比，其競爭對手，這是不可能的，為廣告商建立各種可能的變化，企業組織的價值鏈，甚至雖然廠商賣掉它與這個諾言。想到這個問題，因為這樣，如果你可以使用一個通用的環境評估與一些配置，以圖你的業務流程，那麼，任何組織與適當的資源將能重複你的努力，從而削弱了貴公司的' S '的經濟護城河' 。理所當然地認為某些模塊如供應鏈管理， ERP或人力資源可以成為你的非核心活動和這些模塊，可用於無個性，但對自己的核心活動，環境評估不應當被用來'出來的盒子' 。正如我在博客 Enterprise Application Implementation Strategy 企業應用系統的實施策略 there are 2 ways to tackle automating core competency using EA 有2種方式處理自動化的核心競爭力，用環境評估

Customizing Enterprise Application 定制的企業應用

Pros: 利弊：

• Consolidated Solution : Both non core and core business processes will be on a same platform simplifying the portfolio of software applications. 綜合解決方案 ：非核心和核心業務流程，將放在同一個平台上，簡化投資組合的軟件應用領域。
• Homogenized Development team : Since all the application is on a single EA platform, the IT department can have a homogenized development team. No need to get different resource with differing skill sets. 勻漿開發團隊 ：由於所有的應用是一個單一的環境平台， IT部門可以有一個攪勻開發團隊。無需得到不同的資源具有不同的技能組合。

Cons: 兩種意見：

• Expensive : Need to hire and train highly specialized resources. It is also very slow to build, test and deploy a customized solution thus making the solution expensive. 昂貴 ：需要僱用和培訓高度專門化的資源，它也很慢，以構建，測試和部署一個定制的解決方案，從而使解決方案昂貴。
• Spotty Vendor Support : Usually the vendors do not encourage firms to customize their EA application. But at the same time they do recognize that the customers will walk away if no customization is provided. So EA vendors have a bad reputation of providing good support. 參差不齊的供應商支持 ：通常廠商不鼓勵企業定制自己的應用環境，但在同一時間內，他們承認說，客戶將步行路程，如果沒有個性化的服務。環境，使廠商有一個壞的聲譽，提供良好的支持。
• Handcuffing to a version : Once the software is customized, upgrading to a newer version becomes near impossible because all the customization will be lost. Sooner or later the vendor will start pressurizing to upgrade because of their cost of supporting old version become very high 手銬的一個版本 ：一旦軟件定制，提升到一個新的版本幾乎是不可能的，因為所有的定制都將丟失。遲早廠商將開始施壓，以提升，因為其成本的支持舊版本變得非常高

Getting handcuffed to the current version of EA software is by far the major reason why customizing EA is not a great idea in the long run . 越來越被銬，以現有版本的環境評估軟件是目前主要的原因定制環境，是不是一個好主意，在長遠而言 。

Writing an integrated internal software system : 寫作是一個綜合性的內部軟件系統 ：

Pros: 利弊：

• Decoupled Solution : The core business processes are segregated from the EA. The system can be updated and enhanced several times independent of EA application. 解耦解決方案 ：核心業務流程被分隔開，從環境，該系統可以得到更新和提高數倍獨立的環境評估申請。 That way, the development cycle of internal software system will be decoupled with that of EA development cycle which is notoriously slow. 這樣一來，開發週期的內部軟件系統將解耦與EA的開發週期，這是眾所周知的緩慢。
• Leverage existing capability of IT Department : Writing an internal application can take advantage of existing capability of the IT department. If the current IT department is good in developing .NET applications, then this customized application can be on that platform. 利用現有的能力， IT部門 ：寫作是一個內部應用系統，可以利用現有的能力， IT部門的，如果目前的IT部門是好的，在發展中的網絡應用，那麼這個定制的應用，可以在此平台上。

Cons: 兩種意見：

• Integration Issues : EA applications do not have a good support for integrating external systems. Although, most of them are beginning to use SOA (Service Oriented Architecture) framework to support integration of external application. 一體化問題 ：環境評估的申請沒有一個良好的支持，為集成外部系統，雖然，他們大多數也開始採用SOA （服務導向架構）框架，以支持一體化的外部應用。

As vendors recognize that they will not be able to force every firm to use plain vanilla business process they will begin to support seamless integration with external applications. The second option will become the only way the corporations can automate their core competencies. 由於廠商意識到，他們將不能夠迫使每一個堅定的使用明碼香草業務流程，他們將開始支持無縫集成與外部應用程序。第二個選擇，將成為唯一方式，企業可以實現自動化的核心能力。

Every organization has gotten to this cross road by trial and error implementing a sound EA Strategy.  I don’t think every vendor is speaking in unison as to how to tackle the issue of automating the core competency for that organization. 每個組織都得到了，以這種跨道路試驗和誤差實行無害環境的策略，我不認為每一個廠商都在談步調一致至於如何解決這個問題的自動化的核心競爭力，為這一組織。 The organizations that have tried both the above mentioned ways to automate their core competency have been frustrated by the complexity of the implementation. 該組織曾試圖均採取上述方法，以自動化的核心競爭力，一直在阻撓我們的複雜性實施。 As integration technology changes, and as delivery model adapts we will see continued frustration in the implementation of EA Strategy. 由於集成技術的變化，並作為交付模式適應化修改，我們將看到持續沮喪，在執行環境戰略。

Popularity: 62% [人氣： 62 ％ [ ? ？ ] ]

Tags:標籤： Enterprise Application Strategy企業應用策略 , ， IT Strategy資訊科技策略 , ， Business Strategy商業策略 , ， IT Management IT管理

No Comments yet »沒有評論»