Ometa Event 24-04-2012

1. OmetaEvent 24-04-2012 Case management and SharePoint 2010

2. 10 yearsactive in ECM concepts • Microsoft competence in ECM • Active in Belgium, Netherlands, Germany, Luxembourg, France • Deliver ECM services • DeliverSharePoint Solutions • Who is Ometa?

3. Large customer base • Integration solutionswith SAP, , Axapta, BaaN, Infor LN, Movex, Mapics, ... • Lot of extranet/intranet projects • Advanced tools for case management • Who is Ometa ?

4. Many large Customers • Many have integration with ERP/CRM/ Custom build applications • Involved in design of Intranet/Extranet concepts • Allusing the Ometa integrator Framework • Perform Content Analysis • Deliver SharePoint Solutions due to Standarisation of Concepts • Our customers

5. Agenda

6. Case management Ometa– Luc Deleu Luc.deleu@ometa.net

7. Definition of Case Management • A case in a dynamic case management application follows an unknown path through different states — where rules, tasks and calendars will change based on system events, system controls and the need to meet specific goals. The Forrester Wave™: Dynamic Case Management, by Craig Le Clair and Derek Miers for Business Process Professionals

8. Keywords • Case Management (CM) provides information in context • "Untamed Processes“ • An unknown path through different states • People-driven processes

9. Process Management vs Case Management(BPM) (CM) • Process centric • Repetitive • Structured processes • Data Centric • Dynamic • Unstructured processes • Both involve data, processes, roles, communication, integration and analytics

10. Cases management exceeds process elements • Often more users and roles defined in the case management system • Mostly more data elements defined in the case management system • Not all cases result in processes (ERP, CRM, HR)

11. States and state transition • A state transition in a case canbetriggeredby a human or a system control Event Security Model Change (Groups, Permission levels,...) Alters the state transition possibilities • Sample : • Investigation in progress • Control positive • Calculation in progress Business Rules applied (Orchestration) State AB State AA Case xxx Triggers State BA Alter with associations of Business Entities State CA Creation of ‘bots’ (messages) Alter the context Adaptive/Dynamic (DCM)

12. Samples of states • Opportunity • Request, business case, quote, contract, managed contract, reviewed, legal injunction, end of contract, on hold • Project • Intake(PIT), Preparation, Evaluation, execution, post calculation, finalized, archived • Products • R&D, Commercial evaluation, Quality, in production, Warranty, EOL • HR files • ... • Asset management • .... • Claim • ..... • Investigation • ...

13. Roles, Content, Lifecycle Aannemers Meerwerk Natraject Voortraject Vergunning Oplevering Uitvoeringscoord India MdwVergunning MPA Engineer Senior Engineer Backoffice ERP (Project – Finance) TAN Coordinator

14. Adaptive or Dynamic Case management • Adaptive or Dynamic Case management • Case should be routed through the organisation dependent of its ‘state’ • Only those users should have access to the case dependent of its ‘state’ • Only related ERP and CRM data should become visible dependent of its ‘state’ • Only those ‘state’ transitions should be allowed dependent of current state and business rules

15. Not linked to one system • Typical – Lifecycle overrules application states • Samples • NPI – if product is in engineering, often not in ERP • NCI – customer need to be validated, often not in ERP • Project intake – often project number not assigned • ...

16. Customer Portal Product Portal Purchase Portal Project Portal Integrator Framework Setup (Loose Coupling) Repository Objects Customer Products Purchase Orders Sales Orders Projects Profile SAP user SAP HR SAP Sales AX user Baan user Movex user ODBC User Method SAP SharePoint Dynamic AX Baan ERP Oracle ODBC Movex RFC call BC Call StdPrg System link Web Srvs SAP v4 SAP v5 SAP v6 AX 2009 AX R4 Baan IV Baan ERP Baan LN LawsonMovex M3 Mapics

17. Bringing information elements together • Define your information elements Systems Data elements

18. Movie – object elements

19. State Transitions – result in Actions • Dependencies • Actions • Roles

20. Definingstatesfor a Case

21. State – often dashboards

22. Sample of dashboards

23. Possibleto have multiple flows • Main flow (mainlifecycle) • Sub flow (sub lifecycles) • Dependencies are possiblebetweenflows • SOD betweensublifecycles

24. The Lifecycle of a case A Lifecycle of a workflow is a predefined path of states. The selection might have dependencies on other states of other active Lifecycles Main-flow A Case xxx State AC State AD State AB State AA Sub-flow B State AD State BC State BD State BA State BB Sub-flow C State CC State CB State CA State CD

25. State of a Case Event State AC State AD State AB State AA Case xxx State BB State BA State BA State CC State CA State CA State CD New state of the case defines possible next stepsNot all state combinations are allowed

26. Multiple flows Investigation Request for compensation Only if a control flow is set to state ‘control negative’ Main workflow for case compensation A new control flow can be started if all existing control flows are in state ‘control finalized’ Control positive Control finalized Request for Control Possible Sub-flows Controlin progress Control Control negative Request for Calucation Calculationpending Result Possible Sub-flows Calculation Compensation can be assigned if a Calculation flow is in state ‘Result’ Assigned compensation Revision End of Case Main workflow for case

27. Other projects • Digital projects • Service portals • Contract management • Quality control • Customer portal

28. Thankyou • Feedback form • Next event • Dossierbeheer in SharePoint • Efteling Golf Park 26-04-2012 • Nextel - Ometa : Integratie Lyncand SharePoint • Universiteit Antwerpen - 31 mei 2012