Enterprise Architecture testimonial May 9 th, 2018

Transcription

1 Enterprise Architecture testimonial May 9 th, 2018

2 Alain De Preter Career Summary Expertise Summary Education YPTO (Railroad) - BE Brussels Airlines - BE Deutsche Bank UK Deutsche Bank BE Microsoft/Unisys Alliance USA Unisys - BE Comedia BE Ariane II - BE SWIFT - BE Borland USA CPU2I - FR UCB - BE Enabling Language Engineering Method Engineering Tool Engineering Modeling Coach Applying Enterprise & Solution Architecture Analysis, Design & Implementation IT Engineer LinkedIn url 2

3 Alain Garsoux Career Summary Enterprise NMBS/SNCB IT (Ypto) Enterprise ING Solution ING BE, Finance & Risk. Team ING BE Portfolio ING BE, Finance & Risk Business ING BE Project NV Account Cognos Inside Merant Inside Sales, Progress Software. Expertise Summary Enterprise Architect. Special attention to some value chains : IT, FMD, Finance & Risk, Procurement, Safety & Security, Station. People Coaching Business Intelligence Business Process LinkedIn url Education/ Certification Commercial Ingeneer (UCL - IAG) TOGAF 9 certified 3

4

5 Belgium Railways 2016* Millions Income % Total balance Investments BE travelers Int l travelers BE travelers km Int l travelers km BE trains km On Time Satisfaction Seats Stations Employees Women Hiring * Source : annual report 2016

6 7 Ypto is a subsidiary of BE railways. It delivers IT services. 100 %

7

8 SOL Service Organization Landscape SOL - EA - Enterprise Architecture FB - Enterprise Architecture Rem: Architecture Board - Architecture organisation Architecture Validation Management Enterprise Architects Resource Management Architecture Community Management Governance of Standard, Rules & Guidelines. Governance Business Architecture Data Architecture Application Architecture Infrastructure Architecture Security & Regulatory Architecture. Architecture Knowledge Management. Repository Management. Roadmapping Roadmap by domain Architecture Profession Development. Today, The service Solution Design is not a service delivered by the EA organisation. Architecture Governance Develop a training catalog with HR EA - Enterprise Architecture 9

9

10 11 Our IT burning platform For sure, we have to reduce the IT TCO, right now! We expect a reduction of the IT budget in the coming years. We must increase our IT productivity. We must close 2 data centers by

11 Outsourcing is the selected solution to transform the SNCB business of IT. There is an ongoing request for proposal to select an IT partner. 12 Scope of the outsourcing Period of 5 years (This is summary view!) 12

12

13 What is enterprise architecture (EA)? Gartner Definition: Enterprise architecture is a discipline for proactively and holistically leading enterprise responses to disruptive forces by identifying and analysing the execution of change toward desired business vision and outcomes. This way Alain De Preter - All rights reserved - Tous droits réservés

14 Key questions to be answered by EA, in order to lead to the right decisions Where are we today? Where do we want to be in the future? This way How shall we get there? Alain De Preter - All rights reserved - Tous droits réservés 15

15 AS IS STEPS TO-BE Topics Business Application Portfolio Application Technology Portfolio Some specific questions What are the enterprise business functions and what is there status? Which ones are differentiators? Which ones are externalized? How are we organized (organizations, processes)? What applications do we have in our portfolio? Which ones are the most critical, most expensive, less reliable...? Which application use obsolete technologies? What business functions does this application support? What processes does it support? What information does it consumes and provides? How does it interact with other applications? What technologies is it using? What is its lifecycle status? Who are contact points? Does it handle private information? What technologies do we have in our portfolio? Topics Rationale Impact Architecture Solution Some specific questions What goals do we want to achieve with this specific programmes/project? What are the target capabilities? Which enterprise and domain specific goals will this capabilities realize? What is the impact of this required change in terms of processes, applications and technologies? What could be the target solution in terms of processes, information, applications, technologies and sequence of changes? What are the alternative solutions? Which one would EA recommend? Are projects compliant with approved recommendations? Some specific questions Reality check Why do we exist (our mission)? What is our business model? What is our vision statement? Which goals do we want to achieve? Which capabilities do we need to develop? What is the plan for delivering these capabilities? How does this plan translates to programs and projects? Alain De Preter - All rights reserved - Tous droits réservés 16

16 How shall we answer all these questions? We need an architecture framework that we will use to create architecture views. These diagrams, charts and reports will provide the answers to our questions Alain De Preter - All rights reserved - Tous droits réservés 17

17 Sample view answering some questions 18

18 19 YPTO (SNCB s IT) decided to create its Architecture Framework Key aims Architecture Modeling + IT Portfolio Management Integrate architecture catalogs, attributes, descriptions Modeling productivity and consistency Share enterprise visibility and traceability Ease planning and communication Decision to adopt TOGAF, Archimate, BPMN, UML, IT4IT & SAFe 19

19 ArchiMate, BPMN, TOGAF, IT4IT, SAFe All are great and very useful but Not integrated Not actionable as a whole (disconnected sets) Redundant semantics & terms (Data Object, Role, Process ) Not embedded in our way of working YPTO s conclusion Adopting each and every standard is not ideal Need a single integrated company standard to bring productivity and consistency SNCB decided to go for a single integrated framework that is inspired by market standards and to embed it into the business of IT 20 20

20 Building a framework inspired by market standards TOGAF, SAFe, ArchiMate, BPMN, UML Filter, adapt, integrate, extend standards Normalize semantics Tailor to customer needs Reference Systems Semantics Automation By Nature Reference Framework with Integrated Language Architecture Framework being embedded Alain De Preter - All rights reserved - Tous droits réservés 21

21 What is this architecture framework? Roles, Skills Modeling, IT Portfolio & Planning, CMDB, Document Management Performers People Tools & Repositories Competitive Advantage perform Knowledge & control Process Methods Guidelines & Techniques use / produce communicate TO-BE Capabilities Example: Documents Business Context AS-IS Capabilities Content Deliverables Artefacts Building Blocks Meta data Example: Language Example: Application Landscape Example: Applications, Processes Time & Value Roadmap Alain De Preter - All rights reserved - Tous droits réservés 22

22 A metamodel defines the different types of model element and relationship Modeling Language Definition Alain De Preter - All rights reserved - Tous droits réservés 23

23 To support change activities, we need to further organize the architecture content Define and organize the types of view (viewpoints) Integrate architecture views in project deliverables Document the IT organisation & roles Define the model repository structure This requires much communication and collaboration. Integration in change deliverables is time consuming. It requires some management attention. 24

24 Architecture Content is Structured Following Perspectives An architecture perspective is similar to an IAF aspect area Business Process Funcction Organization Information Summarize Process Funcction Organization Business is supported by applications Applications are supported by technology Detail Summarize Detail Summarize Detail Role1 Role1 Activity Application Application Component Technology Node Application Technology Service Activity Data Store System Software Aware of the business context Unaware of the business context Summarize Detail Data Object Entity1 Representation Information is used and produced by Business and Applications Alain De Preter - All rights reserved - Tous droits réservés 25

25 Perspectives Vision Business Domain-specific Goals DSG Strategic or Tactical Requirements & Planning RnP Directives & Demands Informal Business Scope PROJECT Viewpoints Enterprise Architecture created a set of pre-defined Click on any viewpoint to see its description types of view to support change activities. Processes Activities Roles responsible to deliver the views Roles Strategist Business Area Lead Subject Matter Expert Enterprise Architect Solution Architect IBS PRO ACT Functional Landscape FUL Information Information Information Storage INF IST Application Informal IT Scope IIS APL FAL Application Landscape Functional Application Landscape AFU Application Functions AIA Application Interactions Application Interaction Details AID Viewpoints influence other viewpoints Technology A pre-defined viewpoint Application Deployment APD CON IND Connectivity Instance Deployment Technology Usage TUS Alain De Preter - All rights reserved - Tous droits réservés 26

26 Each type of architecture view uses specific types of element and connector Elements & Connectors Some come from standards Some were adapted Some are proprietary We use verbs instead of nouns to indicate the meaning of the connector s directions Alain De Preter - All rights reserved - Tous droits réservés 27

27 Sample Functional Application Landscape View 28 EA Team site FA - Strategy to Portfolio (S2P) JIRA SDEdit FB - Enterprise Architecture FB - Demand Portfolio FB - IT Investment Portfolio Archi Sparx Enterprise Architect FB - Policy OTRS V2 FB - Service Portfolio Control Desk Excel This requires a specification of the language and the motivation FB - Proposal for such viewpoint

28 Prescriptive language for Functional Application Landscape views Functional Block A Functional Block is a level 3 business function that belongs to some functional area. The granularity and scope of a Functional Block is defined by identifying some homogenous set of information that the Functional Block is mastering a group of activities that fulfill the purpose of the functional block, that belong to some processes of same nature and that produce and use the information mastered by that Functional Block A business function is a behavior element that groups behavior based on a chosen set of criteria e.g. required business resources and/or skills, competencies, knowledge, etc. Inspired by Archimate Application An application Is a self-contained unit of functionality as perceived by end-users Can be clearly mapped to some functional blocks Has its own specific set of application attribute values Is used by and billable to one or several Organizations Is owned by a single Organization Can be part of an Application Platform or an Application Group Encapsulates Applications Components and Application Interfaces Can exist at one or many specific points in time called "plateaus". Possible plateaus are AS-IS, TRANSITION and TO-BE. The name of an application component should preferably be a noun. A Realization relationship indicates which concrete entities ( how ) realize which abstract entities ( what ). The realization relationship is used in a business operational sense (e.g., a role realizes a swim-lane of activities), but also in an IT context (e.g., an application realizes a functional block). Inspired by UML & Archimate Alain De Preter - All rights reserved - Tous droits réservés 29

29 Motivation for creating Functional Application Landscape views Functional Domain1 Functional Area1 Functional Block1 Functional Block2 Functional Area2 Functional Domain2 Application 1 Application 2 This answers the following questions When used as enterprise-wide viewpoint Which applications support which functional blocks? When used as project-specific viewpoint Which applications are/will automate the functional blocks inside the scope of this project? Alain De Preter - All rights reserved - Tous droits réservés 30

30 Sample Application Interaction Details View Sparx Enterprise Architect Sparx Model Repository Web Site Sparx Keystore License Service Sparx License Token Sparx EA Fat Client Sparx Robots Sparx Web Pages File Storage HTML Publication Robot Sparx Shared Folder Architecture Data Publication Robot Architecture Data Acquisition Robot Sparx Shared Repository Repository Backup Generation Robot Model Validation Robot Alain De Preter - All rights reserved - Tous droits réservés 31

31 Sample Application Deployment View Sparx Application Server ADS Sparx Model Repository Web Site Sparx Keystore License Service Sparx EA Fat Client Sparx Robots Sparx Shared Repository Sparx Web Pages File Storage Sparx Shared Folder PRD (HA) 5 users PRD (HA) 50 users Sparx Application Server (Server) Muizen DC Sparx Database Server Internet Information Services Windows Server SQL Server Alain De Preter - All rights reserved - Tous droits réservés 32

32 Work Products Catalogs & Viewpoints Visible Enterprise Catalogs Vision Business Information Application Technology Corporate Vision Domain-Specific Vision Principles Standards Business Functions Services Organizations Processes Roles Individuals Locations Access Points Information Objects Contracts Application Functions Application as a Service Applications Shared Data Stores Interface Protocols Technology as a Service System Software Node Types Logical Nodes (Shared) Node Instances Communication Networks Visible Enterprise Viewpoints Project-specific Project Viewpoints Architecture Management Viewpoint + Standard HTML, Excel & Word reports published daily on intranet Alain De Preter - All rights reserved - Tous droits réservés 33

33 Several approaches are used to manage complexity in the architecture repository Architecture Repository Integrated Enterprise Landscape view formalize Integrated Enterprise Model Architecture perspectives (seen earlier) Architecture levels of details Architecture plateaus (managing time) Project vs Integrated Architecture Content Model repository structure Alain De Preter - All rights reserved - Tous droits réservés 34

34 Security Architecture plateaus describe the subsequent states (AS-IS, TRANSITION, TO-BE) of the operational platform. Envisioned evolution Integrated Architecture Vision To-be (standard apps & tech.) Transition As-is Information Business Application Technology Alain De Preter - All rights reserved - Tous droits réservés 35

35 Security Project architecture describes changes to the platform. Architecture changes are controlled by governance structures re-use integrate Project Architecture of a Change Integrated Architecture Vision Business Application Technology To-be (standard apps & tech.) Transition As-is Information Stage 2 Stage 1 As-is G o v e r n a n c e Governance structures Alain De Preter - All rights reserved - Tous droits réservés 36

36 Architecture building blocks are organized following a prescribed tree structure of folders and building blocks Modular Integrated Traceable Changes Architecture Information Governed AS-IS Transition Scalable TO-BE Shared Alain De Preter - All rights reserved - Tous droits réservés 37

37 38 Summary Enterprise Architecture helps senior management taking decisions with the light on. EA influences decisions about People, Process and Technology. EA is based on frameworks and prescriptive languages. It covers context, business, information, application, technology, security and governance. For a short term jump start, adopt market standards. Scaling for the longer term requires integration of multiple standards. Standards need to be adapted in order to be integrated. EA is not about timing, it is about the sequence. Timing is a question of resources and budget. Those are constraints for Enterprise Architecture. EA specifies the sequence of future investments in terms of target capabilities and standards. EA facilitates management decisions about which standards to select. EA influences and constrains projects in order to deliver some desired end state. And if EA recommendations are not followed, EA adapts the roadmap and informs about the technical debts. The creation of an Enterprise Architecture team takes several years. It starts by managing the as is documentation, collaboration on the ongoing requests for change and then managing the change by defining its content (the solution). Enterprise Architects never work alone. It is collaborative work requiring a great deal of soft skills.

38 ? 39