system architecture - edlegiodetail and prioritize new and redesigned business models i1 i2 i3 i4 i5...

System architecture

© Cordial Business Advisers AB

Transformation of business models in four phases

2

Analyze the market and the competitive landscape

Verify & update the strategic intent and the desired market position

Identify and describe the current business model portfolio

Analyze the identified business models and business model portfolio

Define the desired position and strategic goals per business model

A1

A2

A3

A4

A5

Segment customers and understand their needs, behaviors

Define concrete and attractive value propositions

Identify enablers for future business models

Suggest new or redesigned business models

Detail and prioritize new and redesigned business models

I1

I2

I3

I4

I5

Define and prioritize strategic business requirements

Survey existing supporting structures

Determine the required degree of transformation in each structural dimension

Design ideal architecture

Design solution architecture

D2

D3

D4

D5

D1

ANALYSIS INNOVATION DESIGN

Build a change strategy and design its implementation

Organize and mobilize the available organizational resources

Establish structural preconditions for the change

Drive execution of the change.

Reinforce the change to secure sustainable results

R1

R2

R3

R4

R5

REALIZATION


In the design phase we build the detailed structures that will enable realization

Strategic objectives Strategies CSFBusiness environment Business idea Vision

Value proposition CustomerStructure

BUSINESS MODEL(S)

Customer relationshipCompetence

OFFERINGS

Offering guidelines Offerings Services Products

PROCESS INFORMATION CAPABILITY ORGANISATION SYSTEM

Sub systemSub process Sub capability Business objectOrganizational unitUnit plan

System component

Process component Process capability Object groupTeamTeam plan

BUSINESS PLAN

Process activity Activity capability ObjectRole System functionIndividual plan

Capability areaProcess areaOrganizational area System areaCorporate plan

Main processArea of responsibilityBusiness plan System

Capability

GO

VE

RN

AN

CE

MO

DE

L

Foru

mD

ecis

ion

man

date

KPI

BU

SIN

ES

S R

EQ

UIR

EM

EN

TS

Strategic business requirements

Information area

3

BUSINESS STRATEGY


Why analyze systems and system architecture?

•  As-Is system analysis creates conditions for, e.g: •  IT development •  IT risk analysis •  IT complexity analysis •  IT Due Diligence in M & A

4

Make sure we use the valuable information about structures in the business that are embedded in the systems

AND Determine which parts of the current system landscape can

be reused in future solutions

© Cordial Business Advisers AB 5

Systems inventory Systems review

Category definitions Distinguishing: Provides competitive advantage, business strategy Informative / Decision Creates / compile / provide a basis for decisions, analysis, etc.

Efficiency improving: Operational (base / core) application to streamline / support activities, is often used by many users. Infrastructure: Basic infrastructure services

System

Categories

Key findings The core systems are of the types described Distinguishing and Efficiency improving. In the above matrix The core constituent system are marked by a red background.

Sys

tem

1

Sys

tem

2

Sys

tem

3

Sys

tem

4

Sys

tem

5

Sys

tem

6

Sys

tem

7

Sys

tem

8

Sys

tem

9

Sys

tem

10

Sys

tem

11

Sys

tem

12

Sys

tem

13

Sys

tem

14

Sys

tem

15

Sys

tem

16

Sys

tem

17

Sys

tem

18

Sys

tem

19

Sys

tem

20

Sys

tem

21

Sys

tem

22

Sys

tem

23

Sys

tem

24

Sys

tem

25

Sys

tem

26

Sys

tem

27

Sys

tem

28

Sys

tem

29

Sys

tem

30

Sys

tem

31

Sys

tem

32

Sys

tem

33

Sys

tem

34

Sys

tem

35

Distinguishing x x x x x x x x x x x x Informative /

Decision x x x x x x x x x x x x Efficiency improving x x x x x x x x x x x x x x x x x x x x x x x

Infrastructure x x x x x x x x x x x x x

System analysis

Kundvårdshantering!L1! Uthyrning och leverans!

Kundvård!L2! Uthyrning och leveranshantering!L2!

Kund och Partner Interaktion!L1!Konsumetportal!L2! B2B Portal!L2! Underhållsportal!L2!

Master Data Management!L1!Geografi

MDM!L2!

L4!

Kund MDM!

L2!

L4!

Leverantör MDM!

L2!

L4!

ProduktMDM!

L2!

L4!

PartMDM!

L2!

L4!

L4!

Affärsstöd!L1!Talang-

försörjning!L2!

Affärsutveckling!L1!Affärsmodell-

hantering!L2!

L4!

Projekt-hantering!

L2!

L4!

Verksamhetsstyrning!L1!Affärsplanering!L2!

L4!

Business Intelligence!

L2!

Organisations-hantering!

L2! Uthyrningsställe-hantering!

L2!

Finans!L2!

Franchisehantering!L2!

Anställning!L2! Personal! Inköp!Intern-kommunikation!

IT!

Marknadsföring!L2!

Fordonshantering!

Fordonsförsörjning!L2!

Fordons- underhåll!

L2! Fordons-försäljning!

L2! Försäljning!L2!

L4!

The system description is made in three steps and will result in an analysis of systems within the scope


The system description is made in three steps and will result in an analysis of systems within the scope

6




System

Categories


Sys

tem

1

Sys

tem

2

Sys

tem

3

Sys

tem

4

Sys

tem

5

Sys

tem

6

Sys

tem

7

Sys

tem

8

Sys

tem

9

Sys

tem

10

Sys

tem

11

Sys

tem

12

Sys

tem

13

Sys

tem

14

Sys

tem

15

Sys

tem

16

Sys

tem

17

Sys

tem

18

Sys

tem

19

Sys

tem

20

Sys

tem

21

Sys

tem

22

Sys

tem

23

Sys

tem

24

Sys

tem

25

Sys

tem

26

Sys

tem

27

Sys

tem

28

Sys

tem

29

Sys

tem

30

Sys

tem

31

Sys

tem

32

Sys

tem

33

Sys

tem

34

Sys

tem

35




System analysis





MDM!L2!

L4!

Kund MDM!

L2!

L4!

Leverantör MDM!

L2!

L4!

ProduktMDM!

L2!

L4!

PartMDM!

L2!

L4!

L4!


försörjning!L2!


hantering!L2!

L4!

Projekt-hantering!

L2!

L4!


L4!


L2!



L2!

Finans!L2!



IT!

Marknadsföring!L2!

Fordonshantering!





L4!


System inventory in four steps

7

Identify system scope

Identify key individuals

Select data collection method

Collect data


Identify system scope based on capabilities heat-mapping

8

Business governance L1

Business development L1

Customer dialogue L1

Sales and delivery L1

L2 L2 L2 L2

L2 L2 L2 L2

L2 L2 L2 L2

L2 L2 L2

Business support L1 L2 L2 L2 L2

No functionality

Low functionality

Average functionality

Excellent functionality

High priority

Medium priority

Low priority

No priority


Identify inventory key individuals

9

Business

Supplier

IT

System A System B System C

Capability owner

System expert

System

System D

Sales manager

System expert

Lead-developer

Service manager

System expert

System manager

System owner

System expert

Capability owner


Select data collection method

10

System A System B System C System D

© Cordial Business Advisers AB 11

Other examples of questions •  When was the system introduced? •  Where in the lifecycle is the system currently found? •  Which bigger activities are planned for the system and when will they occur? •  Which category of system are we dealing with?

•  Does the system support distinguished processes? •  Does the system contribute to enhanced efficiency? •  Does the system support decisions? •  Is the system a part of the fundamental infrastructure?

Functional breakdown

Integration & information

Collect data based on pre defined questions and selected data collection method


The system description is made in four steps and will result in an analysis of systems within the scope

12




System

Categories


Sys

tem

1

Sys

tem

2

Sys

tem

3

Sys

tem

4

Sys

tem

5

Sys

tem

6

Sys

tem

7

Sys

tem

8

Sys

tem

9

Sys

tem

10

Sys

tem

11

Sys

tem

12

Sys

tem

13

Sys

tem

14

Sys

tem

15

Sys

tem

16

Sys

tem

17

Sys

tem

18

Sys

tem

19

Sys

tem

20

Sys

tem

21

Sys

tem

22

Sys

tem

23

Sys

tem

24

Sys

tem

25

Sys

tem

26

Sys

tem

27

Sys

tem

28

Sys

tem

29

Sys

tem

30

Sys

tem

31

Sys

tem

32

Sys

tem

33

Sys

tem

34

Sys

tem

35




System analysis





MDM!L2!

L4!

Kund MDM!

L2!

L4!

Leverantör MDM!

L2!

L4!

ProduktMDM!

L2!

L4!

PartMDM!

L2!

L4!

L4!


försörjning!L2!


hantering!L2!

L4!

Projekt-hantering!

L2!

L4!


L4!


L2!



L2!

Finans!L2!



IT!

Marknadsföring!L2!

Fordonshantering!





L4!


System

L2

System

L2

External system

L2

System

L2

External system

L2

System

L2

Create an overall map of systems in scope and show how they are related

13

The purpose of the system map is to describe the co-operation and coordination between systems within the scope on a high level

1 Product information 2 Customer information 3 Payments and invoice foundation 4 Invoices

1

2

3

4


Describe system functionality to enable analysis of current system support

14

SystemL2

SubsystemL3

System componentL4

SubsystemL3

SubsystemL3

System componentL4

System componentL4

System componentL4

System componentL4

System componentL4

The purpose of the system breakdown model is to describe the ingoing components that constitute the system and their functionality


SystemL2

System

L2

SubsystemL3

SubsystemL3

SubsystemL3

SubsystemL3

System

L2

Choose level of detail based on the situation. In general, the system (L2) and its components (L3) can be assumed as standard level whereas the level for system function (L4) is optional.

Describe system integrations in detail to understand consequences of changes in the system landscape

15

channel

MessageSubsystem

L3

Subsystem

The purpose of the model is to describe the system integration in detail, what subsystems and functionality that are used, eventual integration platforms and technique/protocol that are used

channel

Message

channel

Message

channel

Message


Identify which information the system handles

16

System XL2

System YL2

System ZL2

Vehicle SalesL4

ReservationL4

Vehicle MaintenanceL4

PersonnelL4

HRSL2

OrganizationL4

Read Read Read Own + Create Uppdates

The purpose of the system-information matrix is to describe what information the system handles and how, e.g. what information the system needs to read in order to be able create its information

System

Information


Identify which capabilities the system supports

17

CRM-systemL2

Inventory SystemL2

HR-systemL2

Order HandlingL2

SalesL2

Inventory Management

L2Personnel

Management

L2

Order systemL2

The purpose of the system-capability matrix is to describe which capabilities the system supports, which makes a good basis for the continuing analysis of how well the systems support the capabilities needed

by the business.

System

Capability

þ

þ

þ

þ


The system description is made in four steps and will result in an analysis of systems within the scope

18




System

Categories


Sys

tem

1

Sys

tem

2

Sys

tem

3

Sys

tem

4

Sys

tem

5

Sys

tem

6

Sys

tem

7

Sys

tem

8

Sys

tem

9

Sys

tem

10

Sys

tem

11

Sys

tem

12

Sys

tem

13

Sys

tem

14

Sys

tem

15

Sys

tem

16

Sys

tem

17

Sys

tem

18

Sys

tem

19

Sys

tem

20

Sys

tem

21

Sys

tem

22

Sys

tem

23

Sys

tem

24

Sys

tem

25

Sys

tem

26

Sys

tem

27

Sys

tem

28

Sys

tem

29

Sys

tem

30

Sys

tem

31

Sys

tem

32

Sys

tem

33

Sys

tem

34

Sys

tem

35




System analysis





MDM!L2!

L4!

Kund MDM!

L2!

L4!

Leverantör MDM!

L2!

L4!

ProduktMDM!

L2!

L4!

PartMDM!

L2!

L4!

L4!


försörjning!L2!


hantering!L2!

L4!

Projekt-hantering!

L2!

L4!


L4!


L2!



L2!

Finans!L2!



IT!

Marknadsföring!L2!

Fordonshantering!





L4!


Analysis of how well the systems support the capabilities

19

Capability L1

Capability L1

Capability L1

Capability L1

Capability L1

Capability

Capability Capability Capability Capability Capability

Capability Capability Capability Capability Capability

Capability Capability Capability

Capability Capability




Capability





Capability

Capability Capability Capability Capability Capability Capability Capability


Plan for IT development

20

Valu

e

IT Vision

As-Is

Solution architecture 1

Solution architecture 2

Legacy systems

Legacy systems + System x

Legacy systems + System x, y

Legacy systems + System x, y, z


System analysis provides input for understanding the As-Is system architecture

21

•  How well do the system support the

capabilities?

•  Is there reduncancy between systems regarding functionality and information?

•  Where in the life-cyle is the system?

•  Operation and management costs?

•  What should be reused in future solutions?

•  What functionality is available in the system?

•  What capabilities are supported by the

system?

•  What information is handled?

•  What other systems interact with the system in scope?

•  How do the interfaces / integrations look like?

•  Competence, Licenses and Support contracts?

System analysis regarding….. …provides a basis for understanding

system architecture - edlegiodetail and prioritize new and redesigned business models i1 i2 i3 i4 i5...

Documents