英文全文：
http://mediaproducts.gartner.com/reprints/bea/vol1/article2/article2.html
?
?
純粹只玩BPM的廠商繼續(xù)占據(jù)領(lǐng)先位置，但“經(jīng)典”BPMS的應(yīng)用場景已由應(yīng)用基礎(chǔ)設(shè)施變化為模型驅(qū)動(dòng)的、整合的環(huán)境。
?
魔力象限圖：
?
從產(chǎn)品角度，評(píng)估BPM廠商的10項(xiàng)標(biāo)準(zhǔn)。
-
流程執(zhí)行與狀態(tài)管理引擎：
Process execution and state management engine: This orchestrates the sequence of multiple process interaction patterns and maintains the state of process instances, activities and steps among humans and systems based on the metadata and process flow that were modeled. Supporting H2H, H2S and S2S interactions, case management and compensating transactions. -
模型驅(qū)動(dòng)的設(shè)計(jì)和開發(fā)環(huán)境：
Model-driven design/development environment: This is a drag-and-drop modeling environment that includes process wizards, templates and "what you see is what you get" development tools to model and architect all process artifacts, including process design, human interaction, rule interaction, user interface, system interaction and electronic forms. Features such as search, version management, repository partitioning, publish and subscribe services, and check-in/check-out. -
文檔與內(nèi)容管理：
Document and content management: This is document and records management technology that is capable of storing, archiving, indexing, picking and tracking all types of content (for example, structured and unstructured data) inside and outside the context of a process flow. Features include folder management, document and image indexing, management of structured and unstructured data, and document archiving, as well as document security management. -
用戶協(xié)同：
User and group collaboration: These are design time and runtime human teamwork tools. The design time collaboration tools provide development tools for business users and IT to help close the communication gap between the two groups. Runtime tools provide work collaboration facilities so that work teams can drive work to completion faster and can detect, suggest and change system behavior for optimal system performance. This area includes shared work queues, project portals/rooms, role-based development, instant messaging/blogs and community bulletin boards. -
流程組件注冊(cè)與倉庫：
Process component registry/repository: This stores all process definitions, components, models, rules and other process data that can be browsed by humans and called by systems. It supports search, version management, repository partitioning, publish and subscribe services, and check-in/check-out of all software components created and orchestrated at runtime. -
系統(tǒng)管理與維護(hù)：
System management and administration: These tools set up and maintain system and human access, as well as provide monitoring tools to govern the health of running systems. They include role management, security management, system management monitoring, LDAP integration and Active Directory deployment tools. -
業(yè)務(wù)規(guī)則管理：
Business rule management: The ability to abstract and execute business policies and decisions/rules from the underlying application and to enable more-flexible process change. This includes event-based rules, inference-based rules, rule test and debugging, rule simulation/what-if analysis and rule templates. -
在線與離線的仿真與優(yōu)化：
In-line and offline simulation and optimization: These are process simulation and optimization tools that use real-time, historical and estimated data values to detect and suggest process optimization opportunities. Simulation tools should have tight integration with the development environment to enable round-trip engineering. This functional area supports predictive analysis (financial and risk), concurrent process and rule simulation, a simulation repository, optimization algorithms and round-trip engineering. -
流程事件管理：
Business event management, business activity monitoring (BAM) and business intelligence (BI) management: Business monitoring and reporting tools are used for governing and alerting business managers on current and changing business operation behaviors. Features include event listeners, alarms, triggers of online analytical processing/BI reporting, key performance indicator dashboards, graphical process monitoring and process discovery tools. -
系統(tǒng)連接性：
System connectivity: These tools enable system architects to publish and subscribe system services, choreograph service interaction and set up bidirectional connections to various, back-end business applications via prepackaged system connectors, such as Enterprise JavaBeans or SOAP, technical adapters, service support, enterprise service bus, data transformation tools and application adapters.
?
個(gè)人感受：翻閱了這10條技術(shù)標(biāo)準(zhǔn)，一個(gè)產(chǎn)品之所以只能成為工作流(Workflow)，而不是業(yè)務(wù)流程管理(BPM),是因?yàn)楣ぷ髁髦痪邆淞肆鞒虉?zhí)行引擎、模型設(shè)計(jì)等基本工具，而在與流程相復(fù)合的功能，如上面提到的文檔管理、業(yè)務(wù)規(guī)則管理、事件管理/BI/BAM/DashBoard、流程模擬與優(yōu)化以及流程運(yùn)維管理做的不夠深入。
但有意思的是，似乎先進(jìn)的BPM產(chǎn)品所具備的業(yè)務(wù)層次上的BPM能力超越了目前國內(nèi)業(yè)務(wù)應(yīng)用現(xiàn)狀，很多信息化建設(shè)還僅僅處于起步狀態(tài)，這些信息化建設(shè)在初始階段往往只需要一個(gè)工作流引擎即可。
加上本地化因素、市場因素、國外產(chǎn)品難以導(dǎo)入等，造成BPM產(chǎn)品在國內(nèi)曲高和寡（高端應(yīng)用除外！）。
?
?
BEA ALBPM
優(yōu)勢(shì)：- 可以讓業(yè)務(wù)人員參與到IT構(gòu)建中，參與到業(yè)務(wù)流程的全生命周期；
- 開放的標(biāo)準(zhǔn)，較強(qiáng)的H2H,H2S,S2S功能；
- 在將支持業(yè)務(wù)人員參與到流程驅(qū)動(dòng)的解決方案，包含SOA與WEB2.0
- 與Weblogic產(chǎn)品未完全整合，如與Weblogic Integration的整合，包括文檔、管理；
- BPM價(jià)值主要基于產(chǎn)品的創(chuàng)新，可能難于與追求商業(yè)結(jié)果的BPM購買者形成共鳴；
- 僅支持設(shè)計(jì)時(shí)的仿真和優(yōu)化。。？？
IBM
優(yōu)勢(shì)：- 整合所有資源推動(dòng)客戶接受BPM，這些資源包括全球服務(wù)、大學(xué)推廣、業(yè)務(wù)咨詢以及合作伙伴生態(tài)系統(tǒng)；
- 擁有廣泛的、強(qiáng)勢(shì)的BPM-enabling技術(shù)，幫助客戶做大作強(qiáng)SOAs，并達(dá)到BPM級(jí)別；
- 有提供給業(yè)務(wù)人員和分析師的工具Business Modeler、Business Monitor，支持在設(shè)計(jì)、監(jiān)控、分析等階段的流程改進(jìn)；
- 已圍繞SOA構(gòu)建了卓有成效的軟件和IT服務(wù)生態(tài)系統(tǒng)，對(duì)SOA與BPM的市場有很強(qiáng)的預(yù)見性。
- 不只是一個(gè)BPM產(chǎn)品，BPM戰(zhàn)略包括很廣泛的產(chǎn)品線，包括Tivoli、Webshpere、Lotus、FileNet和Rational。參與BPM改進(jìn)生命周期的角色不能形成統(tǒng)一的產(chǎn)品體驗(yàn)；
- 改變已部署執(zhí)行的流程依然需要IT人員支配；
- BPMS產(chǎn)品和專業(yè)服務(wù)不支持business-user-driven，不具備敏捷開發(fā)的特征。
Oracle
優(yōu)勢(shì)：- 用戶可以漸進(jìn)的增強(qiáng)BPM能力，如可從Oracle BPA套件起步，然后增加使用BPEL Process Manager和Oracle BAM；
- Oracle BPA套件和SOA套件使用同一套元數(shù)據(jù)(Process Blueprint)，支持業(yè)務(wù)人員和開發(fā)人員在設(shè)計(jì)時(shí)協(xié)作；在BPA套件設(shè)計(jì)的流程保存為BPMN格式，通過Process Blueprint可轉(zhuǎn)化為BPEL格式；Oracle JDeveloper可以編輯這些模型。這樣可形成閉環(huán)管理，盡管是人工進(jìn)行；
- BPEL Process Manager有很強(qiáng)的人工流程管理功能，如投票、組分配和時(shí)間期限等；
- Oracle事件驅(qū)動(dòng)型的BAM較強(qiáng)，可以可視化的輕松創(chuàng)建內(nèi)置的度量指標(biāo)和儀表盤（盡管需要有很強(qiáng)的數(shù)據(jù)理解能力）
- 由于根據(jù)不同角色而定的的設(shè)計(jì)和開發(fā)環(huán)境，不同角色的業(yè)務(wù)人員和開發(fā)人員的交流將受限。例如，跨角色的模型交流需要從不同的工具中集中版本；
- 總體的用戶體驗(yàn)為傳統(tǒng)的開發(fā)方法論，而不是模型驅(qū)動(dòng)、協(xié)作和敏捷的方法；
- 模擬功能只能使用BPA套件在設(shè)計(jì)階段支持。
Tibco
優(yōu)勢(shì)：- Business Studio2.0是一個(gè)基于Eclipse的統(tǒng)一開發(fā)環(huán)境，支持由業(yè)務(wù)分析師和開發(fā)人員使用。適應(yīng)BPEL2.0標(biāo)準(zhǔn)，支持可重用的流程片段，可通過XSLT和語義驗(yàn)證轉(zhuǎn)換為BPEL；
- iProcess套件使用了事件驅(qū)動(dòng)架構(gòu)，包含一個(gè)強(qiáng)大的、向?qū)降腂AM層，可對(duì)流程進(jìn)行深入的檢視；
- 對(duì)很多標(biāo)準(zhǔn)有很好的支持，包括XSLT\XPDL\BPEL\BPMN等；流程可以保存為XPDL、可以很輕松的從BPMN轉(zhuǎn)換為運(yùn)行時(shí)BPEL，和其他的BPM工具有互操作性，例如IDS Scheer；
- Business Studio設(shè)計(jì)仿真是高度圖形化的。他利用歷史改變數(shù)據(jù)、允許并行的比較設(shè)計(jì)。
- 流程改進(jìn)的整個(gè)周期是不完整的。與SOA的整合、與開發(fā)者的整合尚不完整。因此，完成人工交互流、消息流和服務(wù)編排的開發(fā)過程較復(fù)雜。因?yàn)榻巧碗A段的分離，導(dǎo)致往返工程較困難；
- Tibco產(chǎn)品“久經(jīng)世故”，價(jià)格高昂，不易對(duì)規(guī)模較小或不成熟的組織產(chǎn)生吸引力；
- 對(duì)一些復(fù)雜內(nèi)容交互的流程支持較少，比如說case-management-style的流程。
?
Cordys 從最初定位于應(yīng)用平臺(tái)中間件，目前正擴(kuò)張到BPMS陣營。C3為近期最新發(fā)布的BPMS，在很多方面得到顯著增強(qiáng)，例如BPM建模和執(zhí)行，平臺(tái)與集成支持，安全與治理，還有案例管理。該廠商未包含在此報(bào)告中，是因?yàn)閳?bào)告數(shù)據(jù)搜集時(shí)沒有趕上其最新產(chǎn)品發(fā)布的時(shí)機(jī)。
更多文章、技術(shù)交流、商務(wù)合作、聯(lián)系博主
微信掃碼或搜索：z360901061
微信掃一掃加我為好友
QQ號(hào)聯(lián)系： 360901061
您的支持是博主寫作最大的動(dòng)力，如果您喜歡我的文章，感覺我的文章對(duì)您有幫助，請(qǐng)用微信掃描下面二維碼支持博主2元、5元、10元、20元等您想捐的金額吧，狠狠點(diǎn)擊下面給點(diǎn)支持吧，站長非常感激您！手機(jī)微信長按不能支付解決辦法：請(qǐng)將微信支付二維碼保存到相冊(cè)，切換到微信，然后點(diǎn)擊微信右上角掃一掃功能，選擇支付二維碼完成支付。
【本文對(duì)您有幫助就好】元
