9. EAM Community Meeting, Bern, Wolfgang Wortmann, Enterprise IT Architect Carl Zeiss AG

Transcription

1 Digitalisierung messbar machen: EAM KPIs bei der Carl Zeiss AG 9. EAM Community Meeting, Bern, Wolfgang Wortmann, Enterprise IT Architect Carl Zeiss AG

2 Financial Highlights 2014/ billion euros revenue 369 million euros earnings (EBIT) 25,000 employees (worldwide) As per 30 September

3 Financial Highlights 2014/ patent applications % million euros invested in research and development (10% of revenue) of employees (worldwide) in research and development Stichtag: 30. September

4 Represented Worldwide Around 25 research and development sites Headquarters Oberkochen (southwest Germany) Over 50 sales and service sites Around 30 production sites Just under 25,000 employees Represented in over 40 countries 4

5 Segments 2014/15 Semiconductor Manufacturing Technology 893 million euros revenue 2,800 employees Research & Quality Technology billion euros revenue 5,900 employees Medical Technology billion euros revenue 4,100 employees Vision Care / Consumer Optics billion euros revenue 9,100 employees As per 30 September 2015: *The values deviate from the published figures of Carl Zeiss Meditec AG as a result of different consolidation models. 5

6 Motivation: EAM and Complexity KPIs Business and IT complexity grow overtime if not managed and measurement eases management! Rutz Ulrich (2012): IT Complexity Commerzbank. Presentation at EAMKON Conference, Stuttgart, April

7 Why measuring IT complexity? Results of the Complexity of Application Landscapes: Measures, Models, Management (CALM3) working group Schneider, Alexander W.; Matthes, Florian (2014): Unternehmensarchitekturgestütztes Controlling zur Beherrschung der IT-Komplexität. In: Zeitschrift für Controlling 26 (12), S

8 Project scope: IT complexity indicators for Zeiss Goal: Develop indicators for application landscape complexity Duration: June to August 2015 Team members: Alexander Schneider (TUM), Wolfgang Wortmann (CZ) Current situation Goals regarding the IT landscape have been set Suitable indicators for progress tracking are not established Iteraplan includes most of required architectural information Approach Metric identification Metric assessment Metric implementation Metric development 8

9 EA complexity indicators selected for Zeiss Selected from industry and literature Number of applications Number of users per application Number of interfaces per application Customization level Number of technical components per application Degree of deviation from standard OS Degree of deviation from standard DBMS Heterogeneity of OS Heterogeneity of DBMS Adolescence of technical components Developed for Zeiss Degree of target landscape compliance Degree of core investment Degree of redundant-free digitization Total: 13 indicators selected for Zeiss 9

10 Adolescence of technical components 10

11 Degree of core investments 11

12 Degree of redundancy-free digitization 12

13 Degree of redundancy-free digitization Example 13

14 Trend analysis Project results: Initial snap-shot analysis Assessment of current EA based on Iteraplan data Initial recommendations for action can be derived Trend would be even more expressive Long-term goal: Trend analysis Currently no historic data in Iteraplan due to its capabilities Requires separate storage of historic snap-shot EA data Regular complexity assessment / indicator calculation (e.g. quarterly) Additional visualizations of indicator trends 14

15 Implementation Iteraplan Graphics Reactor Graphics Reactor Data collection: Iteraplan Metric definition: XSLT script implemented by Iteratec Reporting: Automated generation of an Excel sheet containing all metric results Implementing a new metric: Implemented by Iteratec via XSLT Analyzing time series: Implemented by Iteratec, if required. Can also be done manually 15

16 Implementation Iteraplan data sources / maintenance concept Relationship (M) Maintained by EAM Relationship (M) Maintained by Application Owner Graphics Reactor PPM Tool (A) Ø Life Time Ø Stage gate Ø Project size Relationship (M) Maintained by EAM OS / DB data versions (M) v Maintained by EAM Ø Manufacturer Ø Lifecycle data: Ø Availability Ø Extended Support start Ø Extended Support end License Management Tool (A) Ø (Virtual) Server Ø Installed OS / DB versions Relationship (M) Maintained by Application Owner / Operations Team (A) (Semi) Automated interface (M) Manual Maintenance 16

17 17