Volvo case study - download.microsoft.comdownload.microsoft.com/.../290104_Volvo_presentation.pdf · Copyright 2002 Cap Gemini Ernst & Young. ... Technical detailed architecture JSE

Copyright 2002 Cap Gemini Ernst & Young. All rights reserved. Proprietary and Confidential.

Volvo case studyMats Lehrman Cap Gemini Ernst &Young


Agenda

• Background• Business challenge• IT-solution• Key benefits• Best practice • Questions


Client - Volvo

• Volvo Personvagnar AB, Motor- The plant for manufacturing of engines in Skövde, Sweden


Old situation

Base data systems

Source systems

Refine process Destination system


Business issues

• High maintenance cost• Old technology made it hard to find resources• Hard to implement and test changes• Highly depended of IT department• Key person wanted to retire


Business challenges

• Controllers/accountants had to achieve control over the economical rules

• Minimize dependence on IT resources• Act quickly on changes in economical rules• Ability to adapt to future changes• Lower cost for maintenance and operation • Reusable solution for other plants• Make it possible to move from batch to real-time


Business requirements

• Easy to change economical rules that calculate refined data• Cost effective handling of system management and

governance• Minimize need for system development during life cycle. If

possible changes in calculating rules should be possible to configure without system change

• History database able to store 10 year of history data• Transaction database dimensioned to store 1 year plus 3

month of transactional data• Database containing aggregated data (data warehouse)• Reporting and ad-hoc queries


Some metrics

• Number of transactions ~150 000 per week• Number of different transactions ~15• Number of systems involved ~ 10


SAP/R3 ePrisOBSHR

MPS

Maintenance

Salary

Time

Basic Data

Data flow

SAP/R3

Data warehouse

Validate Refine

JSE

Prisma

GUI JSE

Leva-1

AnalysisReports

Interfaces to other systems


Services

Support services

Data services

Import Validate Correct Refine Export

Notify Log Batch Economicrule Master

Authorise Basic data Report Dataanalysis

Historicdata


Products

Internal End-useraccess

Data sourcesUHSSAPR/3

MaintenaceePrisOBS

JSE

BizTalk 2002

SQLServer 2000

MS IE 5.x

MS IIS (web server)

Directoryservice

Transactiondata Basic data BizTalk

databases

Import Validate Refine Export

SQL Server 2000

Crystal Enterprise

txt-files

MPS

txt-files

COM+

Correct

Functoid

Business logic

JSEMaster

Windows 2000/BizTalk 2000/SQL Server

2000Notify

LogBatch

XML

Data access

Fileshare

VCOMDIST

Time report

Historic andaggregated

data

OLAP DTSExtract

Load

ReportDataanalysis

Leva1 Fakir


Architecture benefits

Constrained by the architecture

Integration hub


Key benefits

One application - One flow - One place

Lower costs• Lower costs for application management

• Gained control over economic rules and manuals for controllers/ accountants

• Lower costs at future changes• Euro, Monthly-end Reports, changes in

system portfolio

• Competence on current applications • Mainstream products

More efficient administration• Controllers/accountants have control over

the economical rules

• Higher efficiency in business administration

• No internal controls between applications

• Makes it possible for a common solution for all plants


Best practice

• Design an architecture • Set up interface contracts• Iterative approach• Master data• Design common messages• Testing


High-level project approach

Pre-study Design Construction Test

Perform integration

testSign-off

Migrate to production

Build solution

Test casesUnit test

Content agreementsTechnical

architectureApplication

ArchitecturesCommon UI

Flow analysisUse CasesCommon objects


Questions


END


Technical detailed architectureJSE Server

BizTalk 2002

SQLServer 2000

MS IIS (web server)

Transactiondata

Basicdata

BizTalkdatabases

CorrectJSEMaster

Fileshare

Recive

Channels

Messagingports

Validate

Refine

Export

ImportIn

XSLMappings

OutTransform

COM-componentsto write XMLtransactionsto database

COM-componentsto read XML

documents fromdatabase and post

it to a channel

In OutTransform

In OutTransform

In OutTransform

VCOMDist


The Integrated Architecture Content Framework (IAF)

Business Information

GovernanceSecurity

Contextual

Business Information / Knowledge

InformationSystems

Conceptual

TechnologyInfra-

structure

Logical

Physical


Architecture design

Applications Architecture

Data Architecture

Technology Architecture

Integration Architecture

Systems Management

Governance Applications Development

Security

Service Levels

Functional Requirements

Business Drivers

Use Case ModelInformation

Model

Component Model

IT Drivers & Principles

AS-IS Environment

Strategy


Enterprise Application Integration (EAI) Framework

Management

System Monitoring

Inte

grat

ed D

evel

opm

ent E

nviro

nmen

t

Security

Connectivity

Database Application Mainframe

B2B

Business Process

Workflow

PersistenceDelivery Server Components

Technical Workflow

Transformation

a ca

abc

Message Monitoring

Error Handling

!

Flat File

101110001 e-commerce

partnerXML

<title>CGEYvar oLoaded

= false;


Integration framework

• A process that supports the integration of systems- Driven by business and IT principles and requirements- Build on Integrated Architecture Framework (IAF) methods

- Tools, techniques and guidelines for designing architecture- Focus on service oriented architecture

- Services and their interfaces- Incremental implementation (migration strategy)

• multi-vendor/-technology experience- Focus on interfaces- Many integration technologies

Documents

Volvo case study - download.microsoft.comdownload.microsoft.com/.../290104_Volvo_presentation.pdf · Copyright 2002 Cap Gemini Ernst & Young. ... Technical detailed architecture JSE