Platform vendors' new BP Management tools focus on SOA infrastructure, operational monitoring, and technical development tools for use only by developers and architects. Many of their visual process diagrams remain proprietary and do not provide a sound basis of collaborative process understanding and revealing requirements, especially for collaboration with less technical analysts who may best understand true business rules and needs. While sharing BPEL as the common standard process execution language, such tools can not transform BPEL into readily understandable and editable BPMN, show "As Is" and "To Be" changes visually, then generate new BPEL. The platform development and operational tools are complementary, but do not provide the process requirements collaboration benefits of eClarus Business Process Modeler.

Business users often use whiteboard diagrams, Visio, or PowerPoint to show processes. While such visualizations are useful during initial requirements brainstorming and capture, they do not provide the clarity, refinement, and precision that is essential for cross-silo, cross-business process definition and process automation. Business Analysts often work with users to capture rough process definitions, then refine them to work with technical staff. Analysts increasingly use BPMN (Business Process Management Notation), the modern open standard designed for precise process expression and automation, particularly for SOA and Web Services. Whether adapting new application software to organization needs, initiating partner interfaces, updating outdated business rules embedded in hard-to-maintain software, or clarifying processes for compliance and governance needs, analysts are finding BPMN is a better way to work.

For more information on how well eClarus Business Process Modeler products bridge the process collaboration gap, see our Products