Information Architecture at Nokia - · PDF fileInformation Architecture at Nokia NOKIA...

1 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

NO

KIA

Info

rmat

ion

Arch

itec

ture

Information Architecture at Nokia

SYTYKE presentation

Aija Palomäki / 2-Sept-2005


NO

KIA

Info

rmat

ion

Arch

itec

ture

Contents

Nokia BI Architecture Direction

What is Information Architecture?

UNA, NEIM

Getting started…

Creating Awareness: DM3

NEIM development

EDW for Nokia


NO

KIA

Info

rmat

ion

Arch

itec

ture

What is architecture?• Without bringing external energy in, any system will evolve towards

chaos

• Architecture is external energy that brings order to chaos

• Order is brought about by structures that we may also call the architectures

• Architecture deals with the big picture of • information, • business processes and • applications• technical platforms


NO

KIA

Info

rmat

ion

Arch

itec

ture

Nokia BI Architecture Direction• Business infrastructure architecture spans across all business information,

processes, applications, and technical platforms.

• Its purpose is to increase the agility and productivity of Nokia's business infrastructure.

• It does so by specifying standards and guidelines that shall be applied when solutions are planned, created, and maintained.

• Business infrastructure architecture is based on Nokia's strategic architecture. BI Architecture has five distinct dimensions


NO

KIA

Info

rmat

ion

Arch

itec

ture

Architecture Dimensions


NO

KIA

Info

rmat

ion

Arch

itec

ture

Nokia BI Strategy Nokia BIOperating Model

Nokia BI ArchitectureStrategy

Nokia BI ArchitectureOverview

Nokia BIInformationArchitecture

Nokia BIProcess

Architecture

Nokia BIApplication

Architecture

Program ManagementNOCOP

System EngineeringUNA

Nokia BISecurity

Architecture

Nokia BITechnical

Architecture

Nokia BI ArchitectureOperating Model

Nokia Business Infrastructure Architecture

Architectures areImplemented in

programs-

Tools are NOCOP and UNA!

Architectures areImplemented in

programs-

Tools are NOCOP and UNA!


NO

KIA

Info

rmat

ion

Arch

itec

ture

The Role of BI Architecture

• The role of BI architecture in general is to provide guidelines and principles for the development of the business infrastructure, to satisfy the non-functional requirements derived from the business and operating models.

• These requirements can be divided into different categories, like• Visibility and integrity• Optimization of system economics• Performance and capacity• Availability and continuity• Usability and operability• Flexibility, extendibility, and maintainability• Mobility


NO

KIA

Info

rmat

ion

Arch

itec

ture

Dimensions in Detail• Information Architecture

• The topic of this presentation• Process Architecture

• Nokia Process Architecture is a vehicle for managing the direction and content of Nokia process development.

• Provides enablers for managing current and future processes by providing a big picture of processes and their relationships, thus enabling search and reuse of created process models.

• Application Architecture• Nokia BI Application Architecture defines the high-level role setting of

applications in Nokia business infrastructure. • The purpose of application architecture is to enhance cost efficiency through

optimizing the application portfolio.• IT Security Architecture

• Nokia Information Security Policy gives NBI IT Security a mandate to develop and maintain the management structures, policies, standards and processes to protect the information systems of Nokia in cooperation with Nokia Corporate Security

• Technical Architecture & Technology Management• Provides BI-wide technology management and longer-term visibility on

technology development and future trends in cooperation with other Nokia units

• Proactively supports & coordinates Technical Architecture work & Technology selections in BI


NO

KIA

Info

rmat

ion

Arch

itec

ture

Information architecture

• Information architecture on highest level consist of the enterprise information model, categorization of information to master data and process data, and definitions for metadata.

• This enterprise information model describes main information entities or business objects, their structures and structural relationship to Nokia business and Nokia business infrastructure.

• As such it also defines the terminology used in any other documents.

• For every problem domain there is also a domain model describing in the domain specific language, and usually also in more detail, the information entities in that domain.

• Domain models are refined subsets of the enterprise information model and must comply with it in all aspects.


NO

KIA

Info

rmat

ion

Arch

itec

ture

Role: Information Architect• An information architect is

responsible for activities and work products within a specified business and/or functional scope at selected abstraction levels of information architecture, for example:

1. Generic metamodels pertaining to the BI foundation

2. Nokia enterprise information model (NEIM)

3. Solution specific domain information models or conceptual data models

4. Application specific design models or logical data models

5. Database schemas or physical data models

Examples of activities:

• Identify the larger context of the model

• Ensure integrity, coverage, consistency, and fit for purpose

• Maintain mapping between domain models and NEIM, and between domain models and logical data models

• Ensure compliance with UNAsystem engineering methodology

• Develop UNA competence within the scope of the role and Unit


NO

KIA

Info

rmat

ion

Arch

itec

ture

Unified Nokia Approach (UNA)

What is UNA?UNA is a system engineering methodology for bi solution creation focusing on process and domain modeling, requirements development, system architecture definition and design.

UNA uses definitions that are described in Nokia Enterprise Information Model (NEIM).

UNA is a methodology. It describes system engineering activities and related work products.

UNA defines a formal way to process information. This formalization is based on the use of the Unified Modeling Language (UML).

UNA is model driven.

UNA is minimal – it will always require tailoring for a specific problem domain, such as warehousing, eBiz, SAP development.

UNA development has been driven by enterprise architecture function.

UNA is the tool to get the architecture work done in the programs.

UNA was developed 2002-2003 and is now in BI wide deployment phase.


NO

KIA

Info

rmat

ion

Arch

itec

ture

Relationships: process map, activity diagrams and domain model

Solution roadmapping

Solution use

Program change control

Ini tial requi rement processing

Program E-1 decision

Solution deployment roadmap

Approved initial requirements

Advanced care

Deploy

Initial requirement

B2E sel f service and assisted care

B2C self service and ass is ted care

B2B self service and assisted care

New ideas

STP process

Nokia strategic planning

Solution creation portfolio

Business and operat ing model roadm ap

Released: Solution release

Deployed: Solution release

Inc ident

Ini tial requi rement

Approved: Change note

Critical incident

Fix cri tical inc ident

Release creation

Service change control

Maintenance task

Implementation note

Solution roadmap

Change request

Enterprise architecture creation

Enterprise architecture

Change request

Process integration model

Identification of core processes

Capture

Initial requirement can come f rom any party who has rights to input requirements into this process.

New : Init ialRequirement

: InitialRequirement

Categorize & Assign

Assigned : InitialRequirement

Postponed : InitialRequirement

Analy ze initial requirement

Solution roadmap

Global / local

New : ChangeRequest

To program change control

[ In hurry, c lear

business case & exist ing

program ]

[not f easible nor strategic imperat iv e nor any other must-be need OR Requirement not v alid and more inf ormation not giv en OR no business owner]

[ not clearly f easible, or high risks/v olatilitiy ]

Postponed/rejected initial requirement

Handle rejected/postponed initial requirement

Analy zed : InitialRequirement

Reject or Postpone [No]

[Yes]

Postponed : InitialRequirement

Rejected : InitialRequirement

Approv e init ial requirements

Initial requirement ready f or roadmapping and release planning

[ Approve? ] [Y es]

[No]

Approved : InitialRequirement

Solut ion roadmap

Decision MakerAnalyzerDispatcherRecorder : Initial requirement, defect

Updated : Roadmap

Create Feature Roadmap

Business Model and Operating model roadmap

Existing : Solution Portfolio

Only di rectly ReDe related activities and artefacts are described here, especial ly concentrating to "solution roadmap" development

Other services/ solutions roadmaps

Feature list

Periodic or "on demand" start for the process

Approved : InitialRequire...

Existing : Solution Roadmap

Initiate release creation

Program E-1 proposal

Approve Feature Roadmap

Approved : Roadmap

E-1

Program E-1 decision

To Release Creation process

[ Don't approve ]

[ E-1 Approval ]

Decision MakerSolution Management

Assigned : ChangeRequest

Analyze Impact and Plan Implementation

Analyzed : ChangeRequest

Capture and Assign Incoming CRs

Val id CR?[Yes]

[No]

Closed

New : ChangeRequest

Analyzed : ChangeRequest

Rejected : ChangeRequest

Decide on Implementation

To Release Creation process

Approved : ChangeRequest

Rejected : ChangeRequest

Decision MakerDispatcherProject Team

Process models

Contact

Non-functional Requirement

Funct iona lReq uirement

ServiceRequest

Feedback

CustomerSupportIssue

can initiate

initiates if targeting existing baseline

Issue (abstract)

Incident

ChangeDetection

Roadmap

ImplementationNote

Project/ Program

Release

Is Sche du led i n

1

0..n

1

0..n

ChangeNote 1..n1..n 1..n1..n

1

0..n

1

0..n

Feature

1..n1..n

Implemented In

Initia lRequi reme nt ChangeRe quest0..n1..n 0..n1..n

Purified requirement

0..n0..nBel ongs to

1..n

0..n

1..n

0..n

0..n

1..n

0..n

1..n

Is Speci fied In

Item

0..n

1..n

0..n

1..n

1..n

1..n

1..n

1..n

1..n

0..1

Domain model

Identification of information entities

Process definitions


NO

KIA

Info

rmat

ion

Arch

itec

ture

UNA work products and NOCOP milestones

E2 E3 E4E1E0 E5E-1

ProjectStudy

Process & Concept

Development

SolutionDevelopment

FinalPreparation

HandoverProjectPlanning

Solution Concept:• Organization• Stakeholder analysis• User profiles• User scenarios• Process integration

model

Solution concept:• Process models• Domain model• Glossary• Feature List

Feature specification:• Feature description• Functional requirements• Nonfunctional requirements• Relations to other features

ICT system architecture and design

• ICT system description• Relevant parts of CIM

describing ICT System's component's communication with adjacent ICT systems as well as its main components and their communication.

ICT system architecture and design

• Component integration model• System case model• Non-functional requirements• Logical data model• System technical design

Feature specification• System cases• Changes to existing documents

Component design• Component description• System case model at CIM level

2• Nonfunctional requirements• Features• Component analysis model• Component design model• Test plan

System test plan• Integration plan• Test environment specification

User acceptance test planSystem release

• Software on a medium• Database conversion

programs• Installation guide• Administration guide• Maintenance and

operations guide• Open issues• Change notes and

implementation notesSystem release• Software on a medium• System test report• User manual• Open issues• Change notes and

implementation notes

System release• User acceptance test

report• Open issues• Change notes and

implementation notes


NO

KIA

Info

rmat

ion

Arch

itec

ture

How to use UNA in practice?

Methodology

Activities Methods & Templates

Work products

Read how UNA Methodology defines

Create Glossary activity

Conduct UNA activity:Create Glossary

You have created UNA work product:

Glossary

For detailed instructions, studythe relevant UNA material anduse the UNA Glossary Template

Example: ‘Create Glossary’


NO

KIA

Info

rmat

ion

Arch

itec

ture

NEIM• Nokia Enterprise Information Model

(NEIM) gives common structure, terminology and reusable domain models for integrated application development.

• NEIM also contains logical data models• NEIM captures domain knowledge

and states it precisely using UML class diagrams and textual descriptions

• NEIM is divided into product, party, process, accounting and transaction domain models, which are highly integrated.

• NEIM models are generic. They provide enterprise wide definitions to data.


NO

KIA

Info

rmat

ion

Arch

itec

ture

Example: Definition of order(Extracted from NEIM)

OrderItem

- quantity- unitPrice- estimatedDeliveryDate- shippingInstructions- comment- description

Status

- dateTime

Contact

- description

Party

Feature Product

Order

- orderDate- entryDate- orderId

A note on OCL - READ!!!

Constraint onProduct

Constraint onFeature

0..*

1

Stereotype <<Role>>

0..*

1

Stereotype <<Role>>

0..*

1..*

Stereotype <<Role>>

0..*

0..*

Stereotype <<Role>>

{ordered}

1

1..*

Related0..*

0..*

1 1..*{ordered}

0..*1

1

1..*


NO

KIA

Info

rmat

ion

Arch

itec

ture

Getting Started (2003)….• There were no guidelines of how to utilize NEIM in

• Domain modeling• Normalizing the domain model• Defining the logical data model• Defining the physical data model

• No end-to-end description of how to produce the information intensive artifacts of UNA

• Efforts to utilize NEIM have been difficult and diverse

• Feedback from reviews quite negative


NO

KIA

Info

rmat

ion

Arch

itec

ture

Feedback from NEIM Reviews• “Stakeholders may not be interested in the whole picture, only the area of their own.

Bring up concrete cases, where things have gone wrong or business requirements are not met due to dispersed systems or functional silos.”

• “The full package as a realistic package without being defracmented and chaotic.”• “The model is too complicated and not concrete enough. At least there should be lot

of examples how to use it. UNA is partly duplicating what we already have in NOCOP and since UNA is smaller than NOCOP projects start to use it and ignore NOCOP”

• “Too high and theoretical;- Do not bring clear business benefits;- Do not enhance working practices and make efficient and cost effective processes;- deployment takes too much time i.e need to use 2 or more system.”

• “Dusting on shelves!”• “I do not think that the message is clear and that the adoption rate will be very low.

There is no global buy-in.”• “Need more day to day usage examples and need a full picture of how it all ties

together and need to be implemented on a value basis and not just because it is there.”

• “Somewhat theoretical approaches in methods (too, UML centric) to get good byingamong current Nokia NBI Stuff.;Tools: no tools, yet agreed!”


NO

KIA

Info

rmat

ion

Arch

itec

ture

Some Next Steps• Create awareness & sense of urgency!

• Develop NEIM further• More practical• Buy ready-made specifications, tailor for Nokia• Available in a central repository, intranet (Popkin/Telelogic SA tool)• Including logical data model (in UML)• Applying MDA thinking in NEIM: transformations• More and more guidelines• Training, training, training

• Enterprise Data Warehouse program for Nokia started

• New master data management initiatives• Company data

• Data quality and structure assesments• Tool purchased (Ascential)• Pilots

• Recruitments


NO

KIA

Info

rmat

ion

Arch

itec

ture

Creating Awareness….


NO

KIA

Info

rmat

ion

Arch

itec

ture

Data Program Coordination

Enterprise Data Integration

Data Stewardship

Data Development

Data Support Operations

Initial (I)

Repeatable (II)

Defined (III)

Managed (IV

)

Optim

izing (V)

Data Management Maturity Measurement (DM3)

• Defined industry standard

• Attempt to determine data management's "state of the practice"

• Applying CMM process assessment to data management


NO

KIA

Info

rmat

ion

Arch

itec

ture

SEI CMM Capability Maturity Model Levels


NO

KIA

Info

rmat

ion

Arch

itec

ture

Enterprise Data Management


NO

KIA

Info

rmat

ion

Arch

itec

ture

Enterprise Data Management Template


NO

KIA

Info

rmat

ion

Arch

itec

ture

Development, Support, Use


NO

KIA

Info

rmat

ion

Arch

itec

ture

Data Stewardship


NO

KIA

Info

rmat

ion

Arch

itec

ture

Coordination, Integration


NO

KIA

Info

rmat

ion

Arch

itec

ture

Nokia DM3 Executive Summary• There exists extensive data management experience in the organization

(Delivery Solutions) while there are sometimes challenges communication this experience and making it maximally accessible

• There are special challenges with the Data Program Coordination and and the Data Stewardship functions

• Data management need to address the silo structure of the organization that present social as well as technical challenges

• There are numerous signs of current and planned improvements to data management capabilities


NO

KIA

Info

rmat

ion

Arch

itec

ture

Developing NEIM Further

MDA,

UDM


NO

KIA

Info

rmat

ion

Arch

itec

ture

Purchase a Commercial Data Model

• UDM = Universal Data Models• Published as two books and as a commercial

ERWin Repository• Note that plain UDM models are in ER (Entity

Relationship) notation and not conceptual but logical data models, I.e. they contain quite a bit relational database platform specific details

• Nokia BI has purchased the repository and converted the specifications into UML plus stored them in the SA/MoRe Tool as a reference model

• A set of the UDM models have been integrated into NEIM and conceptualized – i.e. the abstraction level has been risen

• Nokia Subject Matter Experts have reviewed the NEIM UDM models and their compatibility with Nokia business


NO

KIA

Info

rmat

ion

Arch

itec

ture

Data related modeling

Domain Domain Domain Domain ModelModelModelModel

Logical Logical Logical Logical Data Data Data Data ModelModelModelModel

Physical Physical Physical Physical Data Data Data Data ModelModelModelModel

Data Data Data Data Definition Definition Definition Definition LanguageLanguageLanguageLanguage, , , , DDLDDLDDLDDL

NOKIA Information Architecture

NEIM

Communication, Business Knowledge Implementation


NO

KIA

Info

rmat

ion

Arch

itec

ture

Model Driven Architectures, MDA

http://www.omg.org/mda/


NO

KIA

Info

rmat

ion

Arch

itec

ture

A RDBMS DependentRDBMS Dependent

Platform IndependentBusiness Knowledge

MDA at Nokia



Physical Physical Physical Physical Data Data Data Data ModelModelModelModelPhysical Physical Physical Physical Data Data Data Data ModelModelModelModel



Manual Transformation

Automated & Manual Transformation

Domain Domain Domain Domain ModelModelModelModelDomain Domain Domain Domain ModelModelModelModel

Automated & ManualTransformation

NEIM contains also the transformation rules = Design patterns


NO

KIA

Info

rmat

ion

Arch

itec

ture

What are Design Patterns• Data modeling Design Patterns are reusable structures that can be

applied across business data based of our core NEIM Meta Model and NEIM General

• The target is to provide a list of patterns that can be applied to NEIM LDM. We can measure the success of this by seeing the consistent style of the NEIM LDM models and seeing that consistent style being reflected in the models that domain modelers create to support their specific data needs.


NO

KIA

Info

rmat

ion

Arch

itec

ture

Example: Aggregation,Association and Hierarchy Pattern

Class

NEIM General

NEIM LDMEntity

Association

Entity

Entity Association TypeDescribes

Source Destination

0..1 0..1

0..10..*

0..*0..*

Constrains0..1 0..*

An association can be described as “A connection of persons, things, or ideas by some common factor; union”. This means that the data items have some common attribute or feature that associates the data items with each other. For example all people with a blood type of O negative.

Rule Logic

An aggregation can be described as a total considered with reference to its constituent parts; a gross amount: “An empire is the aggregate of many states under one common head” (Edmund Burke). The important point is that we are not just associating data items together, but we are also associating those data items to another data item that describes, relates and groups those other data items together.

Class

<<aggregation>>

Class

<<hierarchy>>

Hierarchy can be described as “An organization with few items, or one item, at the top and with several items below each top item. An inverted tree Structure. Examples in computing include a directory hierarchy where each directory may contain files or other directories; a hierarchical network (see hierarchical routing), a class hierarchy in object-oriented programming.” Or more commonly “a series of ordered groupings of people or things within a system.”


NO

KIA

Info

rmat

ion

Arch

itec

ture

Example of Key Constraint Pattern (many to many)

•<<PK>>orderItemCode

•<<UK>><<FK>> orderCode

•<<UK>>orderItemId

•<<UK>> revisionCode

•orderItemDetails

•<<PK>>orderShipmentCode

•<<UK>><<FK>>orderItemCode

•<<UK>><<FK>> shipmentItemCode

•oderShipmentDetail

OrderItem

OrderShipment

0..1

0..*

Constrains

•<<PK>>shipmentItemCode

•<<UK>><<FK>>shipmentCode

•<<UK>> shipmentItemId

•shipmentItemdetails

ShipmentItem

0..1

0..*

Constrains

•<<PK>>orderCode

•<<UK>>orderId

•<<UK<<revisionCode

•orderDetails

Order

•<<PK>>shipmentCode

•<<UK>>shipmentId

•shipmentDetails

Shipment1..1

0..*

Constrains

1..1

0..*

Constrains

Many to Many


NO

KIA

Info

rmat

ion

Arch

itec

ture

Nokia Enterprise Data Warehouse Nokia Enterprise Data Warehouse Nokia Enterprise Data Warehouse Nokia Enterprise Data Warehouse ----Pallas ProgramPallas ProgramPallas ProgramPallas Program

Communications Kit

Version 2.0

13 June 2005


NO

KIA

Info

rmat

ion

Arch

itec

ture

Main Objectives1. Enable new business management capabilities by sharing information

across functions, processes and extended enterprise

2. Shorten lead time for new information driven business applications

3. Improve cost efficiency in business reporting

4. Off-load business reporting from transaction systems

5. Create and deploy Enterprise Data Warehouse (EDW ) platform


NO

KIA

Info

rmat

ion

Arch

itec

ture

Enterprise Data Warehouse Platform

• EDW platform will be built to last more than ten years with no end of the life cycle.

• EDW stores only data which is originated in other systems using systemto system interfaces as input devices.

• Data is not archived, which enables e.g. trend analysis performance over long periods of times.

• Release cycle time is short, preferably weeks instead of traditional months.

• EDW platforms are based on Massive Parallel Processing computer technology to guarantee adequate response times for user inquiries.


NO

KIA

Info

rmat

ion

Arch

itec

ture

Nokia Business Reporting –Current State

• Due to our process oriented organization…• Partially same data is stored in many separate data marts causing

extra cost.• All data marts are not created within the scope of BI services and

applications.• R/3 is loaded unnecessarily since same data is extracted multiple

times.• Long lead times to meet new reporting needs due to expensive and

time consuming integrations and overlapping work


NO

KIA

Info

rmat

ion

Arch

itec

ture

Nokia Business Reporting –Target State

Supplierportal

Customerportal

Serviceportal

Consumerportal

Publicportal

R&Dportal

Value NetworkApplications

Transaction

ERP

Project

PRM

Change

RDCM

Transaction

DSPProcessApplications

Installation

IBM

Interaction

CRM

Product

PDM

Party

CDM

HumanResource

WDM

Site &Location

FDM

Content

CM

Metadata

MDMaster DataApplications

Onedataloadfromeach

sourcesystem

Reportingapp #1

Reportingapp #2

Reportingapp #3

Reportingapp #4

Reportingapp #…

Reportingapp #N

ODS

SAP BW

EDW


NO

KIA

Info

rmat

ion

Arch

itec

ture

The 3-Dimensional Scope

Consolidate local data marts

(Excel, Access, Oracle/BO…)

Off-load reporting from

R/3 (transfer, re-design,

combine)

New decision support

functionality

Measure: Value

statements

Measure: Use cost savings

Measure: CPU load savings ->

postponed investments

Rel 1.Rel X.


NO

KIA

Info

rmat

ion

Arch

itec

ture

Scope1. R/3 usage will be more efficient

• R3 reports will no longer work as interfaces to data marts• Disintegrated applications which produce overlapping information

for daily business operations will be decreased.

2. Data marts consolidation• Local data marts will be replaced by central processing• Data extracting and transfering will be automated• The needed transaction data and refined information can be defined

by understanding the need and content of original reports.

3. New decision support functionality• Decision making options gained by daily access to up to date

information• Current information will be enriched with more details• Planning and execution information will be integrated seamlessly

and automatically.


NO

KIA

Info

rmat

ion

Arch

itec

ture

Conclusion – Our Experience Is That• Do not give the impression architecture creation is an academic exercise

– it is the lethal kiss!

• Enterprise Information Model – buy it!

• Enterprise definitions need to be approved by large audiences – do avoid the analysis paralysis

• Pilot and help out as much as possible – you will need success stories

• Do not implement a police function – be rather the facilitator, enabler

• Implementing architectures always costs more than fast track solutions -> justify the need properly


NO

KIA

Info

rmat

ion

Arch

itec

ture

Questions, Comments?

Information Architecture at Nokia - · PDF fileInformation Architecture at Nokia NOKIA...

Documents

Transcript of Information Architecture at Nokia - · PDF fileInformation Architecture at Nokia NOKIA...