Grottarossa:Why?
-
Upload
maurizio-farina -
Category
Technology
-
view
1.080 -
download
0
description
Transcript of Grottarossa:Why?
GROTTAROSSAOpen Source Case Management Framework
ROMA, Novembre 2011
Page 2
Agenda
About us
Scope
History
Grottarossa– Open Source assessment
– The product
Purpose
Page 3
About us!
4 different people with a common passion
Maurizio Farina
Owner Adaptive Software S.r.l.
Marco Sabatini
Software Engineer Alfresco & j2EE Specialist
Marco Di Domenico
Sharepoint, K2 & .NET Specialist
Marco Trischitta
Software Engineer & Case360, Activiti specialist
Page 4
Agenda
About us
Scope
History
Grottarossa– Open Source assessment
– The product
Purpose
Page 5
Scope
We will cover the following concepts:
BPM (Business Process Management)
– … a business process comprises a "series or network of value-added activities, performed by their relevant roles or collaborators, to purposefully achieve the common business goal." These processes are critical to any organization, as they can generate revenue and often represent a significant proportion of costs (Wikipedia)
DM (Document Management)
– … used to track and store electronic documents and/or images of paper documents. It is usually also capable of keeping track of the different versions created by different users (history tracking) (Wikipedia)
ACM (Advanced Case Management)
– … When speaking of advanced case management (ACM), we are referring to the coordination of a service request like financial, health, legal, citizen, or human resources on behalf of a subject such as a customer, citizen, or employee. There are key services required in order to have an ACM-based solution. These services include: content management service, business process management service, business rules management service, analytics service, business monitoring service, collaboration service, document capturing service, integration service, document generation service, user interface, and a case design service. (Wikipedia)
Page 6
Agenda
About us
Scope
History
Grottarossa– Open Source assessment
– The product
Purpose
Page 7
History
2004 – 2007: Scenario Framework (BPM System)
2009 – 2011: Case360 (Case Management System)
2012: Grottarossa?
How Grottarossa
idea was born.
Page 8
Scenario Framework - Why? Business Process Modelling
Page 9
Scenario Framework – Why? – Solution Development
Modella Pubblica Esegui
Verifica
Page 10
Scenario Framework: Needs
Business Process modelling
Continue improving (Process & Documents)
Customer Quality Document as “front-end”
Document repository
Role profiling
Legacy System integration
Page 11
Scenario Framework – a Manufatoring/Quality BPMS
Main Components:
Workflow Engine using a XPDL 1.0 dialects
“Visio-like” modeler using a “close” BPMN notations
WEB portal (worklist handler, user and role administration, infopath integration).
Custom Document Management
Page 12
Scenario Framework – Modeler
All Visio 2003/2007 features
Visio is „The Modeler“
Page 13
Scenario Framework – Workflow Engine
The workflow API provides methods to access the process instances, involved the implementation of the instance, tax and legal attributes, query the DB process instance
Application Manager provides two-way communication for application-level integration of other IT systems
Event Manager is the service for the management of events reported during the design of models that enable interprocess communication and synchronization
Idioma is the engine that interprets the script provides the logic to model and act on the attributes of the process
Process Model Database
Process instance Database
XML
DBMS
IDIOMAscript
language
CRITERIAcore engine
PA
NO
RA
MA
Da
taB
as
e M
an
ag
er
Wo
rkF
low
AP
IAPPLICATION
Manager
XML
EVENTManager
Page 14
Scenario Framework - Web Portal
WEB Server
WorkList Handler
Admin panel
Client side
Customer Module
Process report
Scenario application
library
Admin panel is used for administrative functions and configuration services
Reports to set up a reporting process on data from advanced process control (key performance indicators, etc.)
WorkListHandler gives users a view of the activities dispatches from the server during the execution of process instances.
The application scenario of library services are core application code made available in the library, to be achieved or realized by the customer to provide functionality specific to the activities of automated processes
The service url dispatcher that transparently conveys the advanced user request worklistHandler through to areas of the application solution
urldispatcher
Sc
en
ari
o i
ne
rop
era
bil
ity
Scenario modules
Page 15
IT Integration Layer
Application manager
.NET JAVA Win32
SCENARIO SERVER FRAMWORK
IT SYSTEMS
XML WorkFlowRelevant data
PanoramaDatabase Manager
Application Manager provides application-level integration platforms. NET, Java and Win32 through the following channels :
– Socket
– SOAP
Through the XML server scenario framework shares with existing IT systems relevant data for the process
Page 16
Scenario Framework: Conclusions
Ad hoc Document management is not comparable vs. actual document management (both commercial and open source)
Activities, processes, events scheduling is not complete.
Resources management is poorly implemented.
Process format is far from standard XPDL
Data persistence, represented in the documents, is to be implemented with the encoding of special libraries
Portal is not ECM based solution
the idea of a BPM System built from scratch failed!!!
Page 17
• Document 1• Document 2• ...• ...• Document n
• Document 1• Document 2• ...• ...• Document n
• Document 1• Document 2• ...• ...• Document n
• Document 1• Document 2• ...• ...• Document n
• Actvitiy 1• Activity 2• Activity 3• ..• ...• Activity n
Process Process Process Process
Other needs: Case360
Documents
Activity
Process
• Actvitiy 1• Activity 2• Activity 3• ..• ...• Activity n
• Actvitiy 1• Activity 2• Activity 3• ..• ...• Activity n
• Actvitiy 1• Activity 2• Activity 3• ..• ...• Activity n
Process is
not a customer
target
Process is no longer the target: Case Management
Page 18
Case360: CaseFolder
CaseFolder is the target
Page 19
Case Management Components
PPG/2008/00xx
Page 20
Case Management System: Not a “Simple Stuff”
Workflow Management: Management of the processes in "Tobe" model Interaction between users and groups or the management of the
collaboration between the various actors involved in the process and the systems involved
Document management capabilities that creation, routing of complex documents and their storage
Monitoring of the activities performed by different users / roles and events that occur in various processes (BAM)
User Management and Administration: Creating users and roles with their privileges.
Traceability: Storing all the changes that are needed on processes, activities and data
Scheduling: Scheduling activities (such as running processes), defining the time criteria
User Interface using modular plug-in. Legacy systems integration
Page 21
Case Management: conclusion
BPM is not enough
Case Folder is cool!!!
Case Management is close to customer’s “point of view”
Case Management works well for many “application domains”
The modeling phase is underestimated
Everything is a
CaseFolder!!!
Page 22
What to do?
Page 23
Agenda
About us
Scope
History
Grottarossa– Open Source assessment
– The product
Purpose
Page 24
BPM Systems list
1. Appian Enterprise 5 Business Process Management2. Suite3. Avantis4. aXway: Process Manager 5. BizAgi6. BOC Information Systems: ADONIS7. Borland® Together® Products: Together Architect® 2006 and
Together 8. Casewise: Corporate Modeler9. Cordys: Studio10.Fuego: Fuego 5™ (BEA)11.Elixer Intelligent Software: eliXir BPMN-MDA Framework12.EMC: EMC Documentation Process Suite13.Embarcadero Technologies: EA/Studio14.Fujitsu: Interstage Business Process Manager 7.115.Graham Technology: GT-X16.Global 360: Business Optimization Server - Process
Sketchpad17.HandySoft Global Corp: BizFlow® BPM18.IDS-Scheer: Aris19.Corel: iGrafx20.Hyland: OnBase21.IBM: WBI Modeler22.ILOG: JViews23.Intalio: n³ Designer24.Intellior AG: AENEIS25.ITpearls: Process Modeler for Visio
26. Kaisha-Tec: ActiveModeler Avantage27. Lanner: Witness28. Lombardi Software: TeamWorks™ 529. M1 Global: BPI Studio30. Mega International: Mega Suite31. Metastorm: Metastorm BPM™ Suite32. No Magic: MagicDraw UML 10.033. Orbus Software: iServer34. Pegasystems: BPMSuite35. Seagull Software: LegaSuite BPM36. Software AG: Enterprise Business Process Manager
(EBPM)37. Popkin: System Architect™38. Proforma: ProVision™39. Santeon: XIP BPM Platform40. Savvion: Process Asset Management41. Select Business Solutions: Select Component Factory42. Skelta: Skelta BPM.NET 200643. Soyatec: eBPMN Designer44. Sparx Systems: Enterprise Architect 6.545. Staffware: Process Suite46. Sun Microsystems: Studio Enterprise Edition47. Sybase: PowerDesigner® 1248. Tibco: Business Studio49. Troux™: Metis 3.6 Enterprise Architecture Suite50. Visual Paradigm: Visual Architect
Page 25
Case Management Systems
The Forrester Wave™: Dynamic Case Management, Q1 2011
In Forrester's 57-criteria evaluation of dynamic case management (DCM) vendors,
Pegasystems, IBM, EMC, Appian, Singularity, and Global 360 led with the most
dynamic, visionary platforms. Pegasystems excelled with strong capability in all process areas
particularly service requests — supported by a sophisticated rules engine that automates case
progression. IBM's strong content management capabilities and strategic positioning lifted it
into the Leader category. EMC demonstrated powerful DCM capabilities focused on its
traditionally strong content management offering. Appian shone with its emphasis on
collaboration supported by the new Appian Tempo interface. Singularity demonstrated a long-
term commitment to and vision of DCM, underpinned by strong support for complex timelines
and skills management. Global 360 completed the Leaders group with its user-centric,
persona-based interface, complimented by automation and event management capabilities.
Strong Performers included Pallas Athena, Sword Ciboodle, and Cordys — all offering
Robust platforms that provide innovation in different DCM areas. ActionBase ranks as a
Contender, filling the gap between email chaos and process-centric DCM.
Page 26
BPMS: Make the CaseFolder, Workflows, Documents...?
Workflow Management
RecordManagement
Document Management
Content Management
• Liferay (ECM)
• Alfresco (DM)
• Activiti (WFM)
• .....
• .....
IDEA
Let‘s try to integrate several open source tools to make ACM system
Open Source assessment
Page 27
Case Management (.NET Microsoft)
Microsoft Workflow Foundation ( dal 2005)
Sharepoint
Integrato
Page 28
Case Management (java stack free)
jBPM
Integrato
Alfresco with jbpm now with activiti
Page 29
Open Source: conclusions
PROs:• BPMS• Document Management• Record Management
CONs:• Case Management• Process Designer• Data Designer• Cloud & Mobile Environment
Grottarossa!!!
Page 30
Agenda
About us
Scope
History
Grottarossa– Open Source assessment
– The product
Purpose
Page 31
Software Development
Configuration
Analisys
Software Development
Analisys
Configuration
Grottarossa: Development
Page 32
Services
Products
Grottarossa: Point of view
Page 33
Case FoldersProcesses
Documents
Records
Fields
Grottarossa: Entities
Page 34
Front End
Grottarossa Modeler
Grottarossa
ModelerProcesses, Fields, CaseFolder….
ModelerUsers, Roles, Organizations,
User Interface….
Model (xm
l)
Model (xml)
Web 2.0
Mobile
Grottarossa Web
Page 35
Grottarossa: n-tiers architecture
Back-End
Low – LevelAdministrator
Middle-Ware Front-End: Component
InterfacesCaseManagement
WorkflowManagementDocumentManagement
UserManagementLayoutManagement
High-LevelAdministrator
Users
NativeMobile
Component
Web Component
Integration System Console
AdminConsole
Grottarossa Driver“OTS” Products
Enterprise Service BUS – Queue Manager system
QUEUE Project & Procedures - Request
QUEUE Project & Procedures - Response
External System
Web Mobile
Component
Page 36
Flash – Modeler Assessment
Page 37
Flash – Form Designer Assessment
Page 38
Silverlight Modeler Assessment
Page 39
Flash Eclipse plug-in
Action Script coding
Mac OSX, Win, Mac, Ux
All Mobile devices
Silverlight Visual Studio
.NET languages
Win and Mac OSX
Only Windows devices (maybe)
Modeler conclusions
Page 40
Vaadin – User Front End
Page 41
Grottarossa: RoadMap
Recycling what we have
Improving the Back End
Developing the Designer
Integrating open source libraries/products
Page 42
Grottarossa: actors
A good opportunity for
• University: Grottarossa is the methodology
• Contributors: Grottarossa training, certification
• Partners: Grottarossa does what customer asks
Page 43 Page 43
Grottarossa is the place where the idea was born.
From wikipedia (http://it.wikipedia.org/wiki/Grottarossa)
Grottarossa was crossed by the Via Veientana come off the Via Cassia and connected Rome with Veio. The route of this road is now almost completely engulfed by urbanization of the areas of the Tomb of Nerone and the same Grottarossa. One of the few vestiges of the road (which like the other outside the walls was accompanied by burial) is the tomb of Veio, the funeral of the first imperial age structure of considerable size which is in a state of semi-abandonment, in the park called “Parco Papaccio”.
At the modern hospital of St. Andrew see two of Etruscan tombs in the nearby street “Quarto Annunziata”.
The area takes its name from the caves dug into the red tuff, found near the homonymous street Grottarossa and where, presumably, lived in the prehistoric hominids (probably Neanderthals or Homo sapiens).Another path near the intersection of “via di Grottarossa” with “via Flaminia” seems to take its name from a kind of tufa (“via di Quarto Peperino”), as well as Saxa Rubra (red stones).
Why name Grottarossa?
Page 44 Page 44
Scenario Framework
• https://sites.google.com/site/scenarioframework/
• http://scenarioframework.codeplex.com/
Global360 (now OpenText)
• http://www.global360.com/
Grottarossa
• http://www.grottarossa.org/
• http://code.google.com/p/grottarossa/
Resources
Page 45
Contact Details
Maurizio Farina ([email protected])Marco Sabatini ([email protected])
Marco Trischitta ([email protected])Marco Di Domenico ([email protected])
SponsorsAdaptive Software (www.adapso.com)
Page 46
Thank you for your attention!
Any Questions?
Page 47
Back up slides
Page 48 48
5. Pre-manifattura – Attività e tempi Foiano
Chiusura contratti
Anno 1 Anno 2
gen-apr mag giu lug ago set ott nov dic gen feb mar apr mag giu lug ago set ott nov dic
Ricevimento e pagamento del tabacco sciolto
Stoccaggio
Spedizione colli
Assistenza tecnicaai produttori (~180)
Raccolta e curadel tabacco
• Valutazione/perizia del tabacco• Pagamento (100% alla consegna)• Selezione e definizione lotti
qualitativi:– qualità alta (fascia)– qualità media (filler)– qualità bassa (scarti)
Semina etrapianto
Coltivazione tabacco
Lavorazione
• Alle manifatture: Tabacco per filler e tabacco per fascia (stock di sicurezza)
• In Sri-Lanka (tramite Lucca): tabacco per fascia
• Prosciugamento• Predisposizione colli
Page 49
negative argument 1 negative argument 2 negative argument 3 negative argument 4 negative argument 5
negative argument 1 negative argument 2 negative argument 3 negative argument 4 negative argument 5
positive argument 1 positive argument 2 positive argument 3 positive argument 4 positive argument 5
positive argument 1 positive argument 2 positive argument 3 positive argument 4 positive argument 5
Comparison
NegativeNegativePositivePositive
1SCENE
Advantages and disadvantages with two textboxes ANIMATED
IDEA
Use text boxes for a clear and structured confrontation of do’s and don’t’s
NegativeNegativePositivePositive
Page 50
BusinessTransformation
ChangeManagement
OrganizationDevelopment
Business ProcessDevelopment
CustomerRelationshipManagement
All phrases can be replaced with your
own text.All phrases can be replaced with your own text.
All phrases can be replaced with your own text.
All phrases can be replaced with your own text.
For PowerPoint 97-2010