390 likes | 815 Views
QualiWare i Vattenfall. Agenda. About Vattenfall Vattenfall Integration Platform Vattenfall Application Portfolio Vattenfall and Enterprise Architecture. Agenda. About Vattenfall Vattenfall Integration Platform Vattenfall Application Portfolio Vattenfall and Enterprise Architecture.
E N D
Agenda • About Vattenfall • Vattenfall Integration Platform • Vattenfall Application Portfolio • Vattenfall and Enterprise Architecture
Agenda • About Vattenfall • Vattenfall Integration Platform • Vattenfall Application Portfolio • Vattenfall and Enterprise Architecture
The Brand Heritage 1909 Founding 1996Swedishderegulation 1910Hydropower (Olidan) 1952Transmission (Harsprånget- Hallsberg) 1969Nuclear Power (Ågesta) 1980More focus on bio / wind 1992Vatten-fall inc. 2006One Vattenfall 1900 1910 1920 1930 1940 1950 1960 1970 1980 1990 2000 1909 2000
Vattenfall in brief • Europe's biggest producer of heat and fifth biggest producer of electricity. • Vision: Being a leading European energy company. • Business today in Sweden, Finland, Denmark, Germany and Poland. • Production, transmission, distribution and trading of electricity. • Production, distribution and trading of heat. • About 33 000 employees. • Parent company Vattenfall AB is owned 100 percent by the Swedish state.
Board of Directors CEO Group Shared Service Group Functions Business Group Vattenfall Nordic Business Group Vattenfall Europe Business Group Vattenfall Poland Generation Mining & Generation Distribution Distribution Transmission Sales Sales Distribution Heat Heat Sales Services Heat Shared Service Centres Organization
Electricity generation (TWh) Electricitysales (TWh) Net sales (EUR billion) Electricité de France (EDF) E.ON RWE Vattenfall Enel Electrabel (Suez) Endesa 610* 224 217 169 126 131 127 581* 367 299 200 156 145 148 51 56 42 14 34 12 18 Largest electricity companies, Europe 2005 *) 2004 figures Sources: Annual reports, Financial statements
Agenda • About Vattenfall • Vattenfall Integration Platform • Vattenfall Application Portfolio • Vattenfall and Enterprise Architecture
Vattenfall and system integrations • In 2004 VBSN got an assignment from CIO Nordic to establish a collective integration center for the Nordic region, Vattenfalls Integrations Center (VIC). • The new integration center got an assignment to establish a new common integration platform (BizTalk/VIP Nordic) that step by step will replace old integration platforms. • In 2005 the governance modelfor IT at Vattenfall Nordic was established, including a council for integrations. • In 2006 the assignment was expanded to supply all integration platforms and germane services.
The integration services consists of several deliverables. Strategy/ Controlling VIP Xxxx VIP Volym VIP Nordic (BizTalk) VIP Xpress (Mercator) VIP Extern (Amtrix/GS) Administration Management Development Services/Delivery Services Delivery components
Environments for • Development • QA • Production • Routines for: • Maintenance (service delivery and support) • Emergency Corrections • Configuration Management • Incident & problem management • Release management • Change management • Business model support • Interface agreements (contract between sender, receiver and integrator) • Statistics generators • Methodologies for • Development (including test and deployment strategies) • Capacity management and tuning • Tools for: • Documentation • Regression and performance test • Missionary and education • Recommendations for application owners and builders • Rules and guidelines for creation of integrations VIC Framework • VIC Framework is mainly assembled for VIP Nordic but can be applied on remaining platforms. • The framework consists of:
Operation methods and processes • VIC operation methods and processes are documented in QLM/Atlas
Static view of Integration – Meta model New Templates
Data Access Points • Belongs to exactly one information system • Describes an information structure • Could be an inbound and/or outbound • A physical data model • Technology • File, API, WEB Service… • Part of adapter
Demo Static view of an Integration
Demo Dynamic view of an Integration
The Biljett Project • 200+ integrations • 8-12 persons involved • 10 QLM • Decision to continuously design and document the integrations in QLM • Decision to only document what could/should be maintained but enforce quality in the documentation • ~ 1 man year for documentation
The Biljett Project – Was it worth it? • No real cost benefit analyze have been performed, but • “No one have questioned the investment in continuous documentation” • “The easy access of accurate documentation was a success factor for the project since some flows was redesigned several times during the project” • Estimate • 20 % of an integration project consists of “searching for documentation” • VIC has nine full time employees working in integration projects • Estimated 0.5 to 1 man year for maintenance of documentation • 9*0.2 – 1 = 0.8 man year
Agenda • About Vattenfall • Vattenfall Integration Platform • Vattenfall Application Portfolio • Vattenfall and Enterprise Architecture
Vattenfall Application portfolio - Characteristics • Documenting 580 systems • Administration • Usage • SLA • Distributed • System owners maintains documentation • QEI • Go live 14/5 2007
Example Example BusinessFunctionArea • InfrastructureManagement • R/3 Classic BusinessFunctionGroup • R/3 ClassicRåcksta • DeviceManagement BusinessFunction • R/3 ClassicRåcksta Test • ReplaceDevice New abstraction levels of existing objects InformationSystem(Abstract) InformationSystem(Data System) InformationSystem(Installation)
Business Functions at Vattenfall • Not what QualiWare usually means with Business Function • Very similar to what many call “services” • 18 Business Function Areas • 68 Business Function Groups • 363 Business Functions • “SAP Business Map for utilities” as a first approach. “Not 100% but good enough”
Agenda • About Vattenfall • Vattenfall Integration Platform • Vattenfall Application Portfolio • Vattenfall and Enterprise Architecture
Demo Defining a system usage
Enterprisefocus Prioritized Project Projects takes of in the existing EA And contributes to the “complete architecture”
Knowledge about dependencies Optimize Enterprise Architecture Planning Business BusinessFunction Data InformationSystem Database