Overall Duration: 1 year In-Kind ZT: 5000 (Studenliste fuer Meetings) Cash in ZT: 35000 Project-Volume: 49546 Person Months: 5 Includes: 10 days at ZT location in Dornbirn Workpackages: WP1, WP2, WP3 Costs: The costs above are with CDP involvement. Contracts directly with TUM reduce the person months to 4, and the project volume to 35000. Also for direct contracts, the meeting costs for ZT staff (ZT In-Kind) can not be part of the project volume (and is thus 0). TUM goals are: * Testing OUR technology in real-world scenarios (scientific state-of-the art). * Describing the scenario in scientific papers (including the name of ZT). ** i.e.1: research direction: best practice step-by-step introduction of office-process automation office-process automation. ** i.e.2: research direction: conformance checking for office-process automation. ** i.e.3: research direction: auto-generated process dashboards from process models, that automatically adapt to process-changes. All software created as part of our cooperation will be open-source, and will be independent of ZT use-cases or data. Our research goals depend on WP3 (Process Data Analysis), and do not necessarily are immediate results from WPs, or immediately benefit ZT. While some tools created from exploring the research directions will be WP deliverables, others, or refinements of tools, will be available for introduced to ZT cases after the project. In the following we describe the proposed WPs: # WP1: Implementation of a basic idea collection process (Phase 1) for ZT. ############################################################################### Duration: 6 months The implementation consists of 3 stages: Stage 1: Prototype Executable Process, that drives the idea collection ====================================================================== 2 stakeholders: process participants (PA, i.e., the roles from excel), process supervisors. The work is distributed to the correct process participants. A final decision for all idea collections is disseminated among the process participants. Process (meta-)data accrued for each process is saved in a standardized format, ready for processing in standardized data/process analysis tools (e.g., Celonis, Fluxion). The process supervisors can see which instances are currently running, and, should it be necessary, manually trigger the repetition of steps, or even cancel processes altogether. Stage 2: Prototype Deployment ============================= The necessary software is deployed at ZT and integrated into their infrastructure. This includes utilizing internal ZT email and authentication infrastructure, realizing/collecting/defining the proper organization model (units, roles, subjects), and deploying all components to internal virtual computing resources. Stage 3: Prototype Evolution ============================ The prototype should be introduced in multiple stages, each including a wider audience. Initial experience reports will fall into three different groups: * UI problems (i.e., understandability) * Data artefacts missing for potential decisions (i.e., stuff missing from UI) * Process problems (i.e., steps missing, not in correct order, or the overall structure of the process leads to bad results, bottlenecks, or bad decisions). Group 1 and group 2 have to be solved by continuously improving the UI to best suit the requirements of the process participants. Group 3 problems will be typically solved by the process supervisors (see stakeholders Stage 1), who can adapt individual instances of idea collection processes). For each applied solution it has to be reflected, if this is a change that should be integrated into the overall processes, either as a (1) structural change, or (2) as a conditional execution relying on some automatic decision / data artefact. # WP2: Implementation of a 2nd process (idea collection Phase 2, or unrelated) ############################################################################### Duration 6 months. It should follow the same stages as outlined for WP1. It should have a similar magnitude as WP1. # WP3: Process Data Analysis ############################################################################### Duration 3 months. The idea of this WP is to make the data created during process execution available for data analysis, and allow for automatic processing of this data. This includes automatic anonymization of data, as well as a tool-chain that assists in finding potential problems, if processes are newly generated or evolve, which leads to new potentially problematic data artefact. Concrete Benefits: * Automatic statistics for the process execution, complying to data protection regulations * Tool-chain for automating the creation of such statistics. Indirect Benefits: The data can be made available as "open data" (e.g., as part of EU open data initiatives such as zenodo,org), potentially leading to interesting analysis results, thus allowing ZT to gain "free" additional insight for future process improvements. Please also see research directions at the beginning of this document.