Interoperability constraints and approaches

Modelling initiatives are taken up by businesses irrespective of subsequent change implementation. The aim might be to get a central repository of business processes for any future developments or facilitate inspection of processes being employed.

Key business process modelling drivers include:

• Process documentation for knowledge retention and management
• Improvement techniques discovery or trouble area analysis
• Precursor and prerequisite to domain/industry specific product fitment
• Basis for subsequent software build

A mature and expansive establishment will already have a process repository in one form or another. Imagine asking them to start process capture from scratch in a completely new tool set or informing them that the expensive process execution engine or ERP they have purchased isn't able to draw process data from existing setup.

Case for interoperability:

• Companies often have their processes documented in traditional tools like Visio or UML based tools
• An enterprise may use legacy tools to manage their process knowledge or store process data in Database or even use different technology tools like LDAP (Organization models) etc.
• Process data may have been extensively captured in standard documentation formats such as spreadsheets, text documents etc.
• Since a mature process management or process realization environment such as a BPMS, Workflow, Integration, ERP etc., might exist process data may need to be mined from existing setup or extracted from process logs
• Different tools having different strengths are procured and tapping the capabilities of each is required
• Different business areas/departments/geographies use different methods but a global understanding, centralized repository and control is required
• The execution system is vastly different from modelling setup and roundtrip and lifecycle management of processes is disconnected, often tedious or impossible
• A large amount of code exists for facilitating exchange/collaboration between environments used by different business users
• Business users aren't keen on using a new tool as it is complex to work with and cuts into efficiency. Transition is looked on as a difficult task
• Working on modelling, processes is often restricted to office setup. Additional costs arise when office network is inaccessible

-1-

Explore Our Topics

• BPM & Enterprise Architecture
• BPM Standards
• BPM Implementation
• BPM Best Practices
• Continuous Process Improvement
• BPM Governance
• Service Governance

• Business to Business (B2B)
• BPM for Supply Chain
• BPM for Customer Management
• BPM for Financial Services
• BPM for Healthcare & Insurance
• BPM for Government

• Business Activity Monitoring
• Event Processing
• Process Intelligence
• Business Rules Management
• Decision Management
• Operational Intelligence

• Workflow Automation
• BPM & Enterprise 2.0
• BPM & Web 2.0
• BPM & ECM
• Case Management
• Collaboration
• Enterprise Portals
• Social BPM

• BPM & Cloud Integration
• BPM Analysis & Optimization
• Business Process Simulation
• Process Visibility & Monitoring
• Process Orchestration
• Process Discovery
• Process Modeling

Home
Webinars
Blogs
ebizQ Forum
All Topics
Subscriptions
White Papers
Analyst Corner
Follow us on Twitter
Fan us on Facebook

Explore Our Topics

BPM Strategy
BPM Solutions
Event Processing Strategy
Content-Centric & Collaborative BPM
Process-Centric BPM

About Us
Editorial Submissions
Feedback
FAQ
Advertise With Us
Site Map
Privacy Policy
Unsubscribe