Embed Size (px)
Citation preview
Welcome to theFITMAN Specific Enabler Webinar on
Collaborative Business Process Management16th June 2015
Mauro Isaja – [email protected] Iranzo – [email protected]
Introduction
• The FITMAN "Collaborative Business Process Management" Specific Enabler (CBPM) is a platform for the semantically-enhanced design and execution of Business Processes in complex or distributed organizations
• Targeted at the Virtual Factory manufacturing domain or at Large Enterprises
• Entirely web-based: no software to be installed locally by users, access from anywhere
• Based on the “Light Semantic Composition” Generic Enabler from ATOS Spain (COMPEL)
2
Feature highlights
• Model a business process by composing existing services within a graphical, standard based development environment
• Select existing web services from a catalogue to match process tasks, using semantics (i.e., annotations) in the scope of a reference ontology
• Bind process tasks to web services, to automate their execution at runtime
• Assign responsibility for human tasks to specific users and/or roles
• Run your business processes on the platform, interactwith human tasks through a web UI, monitor and manage your process instances
• Seamless integration with corporate IT environment
3
Benefits
• The development of business process in a formal notation requires multi-disciplinary teams, to share the domain-specific and ICT knowledge required to implement them.
• CBPM simplifies this collaboration:
– Allows a clear separation of concerns
– Applies user profiling
– Provides user-friendly tools
– It is universally accessible
4
Technologies
• Base software assets– Liferay Portal Server [www.liferay.com]
– Activiti BPM Platform [www.activiti.org]
– Sesame2 Ontology Server [www.openrdf.org]
– Jasig Central Authentication Service [www.jasig.org/cas]
• Leveraged open standards– Business Process Model and Notation (BPMN) 2.0
[www.omg.org/spec/BPMN/2.0]
– Resource Description Framework (RDF)
[www.w3.org/RDF]
5
Architectural overview
6
Web Portal
Federated SSO
Persistence Layer
COMPEL GECollaborationWeb Tools
Wiki
Foru
m
Do
c Mgm
t
Semantic KBBPM DBWeb Portal DB
LDAP
Active Directory
Corporate Users
Portal Users
Provisioning
7
• As a Virtual Machine image
– KVM version: deploy on any 64bit Linux system ftp://repo.nimbus-ware.com/fitman-bpm-qcow2.zip
– VirtualBox version: deploy on any Linux, Windows, MacOS system
ftp://repo.nimbus-ware.com/fitman-bpm-vdi.zip
• As a service (SaaS)
– Single, shared instance as an experimentation playground (coming soon)
Terms and conditions
8
• Within the scope of the FI-PPP Programme– Free use of the software for members till the end
of the Programme
– FITMAN provides free support to members till the end of the Programme
• Out of FI-PPP Programme scope– All software assets are free and Open Source
– COMPEL is licensed by ATOS under GPL v3 terms
– Non-COMPEL components have various OS licensing terms, but GPL v3 still applies to the overall product
COMPEL GE Presentation
Multidisciplinary teams (gap)• Roles
• Business Analystsvs
• Service Integrators
• Disperse Knowledge• Domain specific business
processes and conceptualisations vs
• SOA-based technologies: WS*, WSDL, UDDI, SOAP, XML/XSD, JAX-WS APIs, etc
COMPEL Motivation
Technical limitations• Discoverability/Advertising
• Very limited uptake of IoS• Obsolete service registries (UDDI)
• Incorporating new trends in SoC/IoS: ROA, REST, Mashups, etc.
• BPM vs SOA composition languages• BPMN vs BPEL
• Standard graphical notation
• Technology and tooling complexity
COMPEL BPM limitations
Scaling to the Web of Services (IoS)Web 2.0 Crowd-sourcingAssisted (automated) BPM at design and run time
• Automating discovery:• Exact vs approximate
matchmaking• Automating work and data
flow• Dynamic runtime
• Late binding, re-binding, self* capabilities (healing, compensation, etc)
COMPEL Challenges
• COMPEL is an open and multiplatform solution to design business processes (BPMN, BPEL) by aggregation of SOA based services.
• Processes are designed by business analysts. The processes and their tasks are defined using their domain vocabulary (process semantics).
• For each task, Light Semantic Composition suggests the most matching services as far as description is concerned and the user makes his choice.
• The services are located in a centralisedrepository where providers register and describe them semantically
13
COMPEL The solution
• Coarse-grain light semantics for
– Task description, Process description, requirements, preferences, context
• Domain ontology based annotations
• Exact and approximate dynamic discovery
• Semi-automatic late binding
• Automated data flow generation and executable BPMN generation
• Registry for process annotations and service descriptions
• Execution of the business process (through GUI & REST API)
14
COMPEL The editor
15
COMPEL GE Demo
