Enterprise Architecture for

Global Bike Inc.

Group 3
Section D
Methodology
Customer Segments

Value Proposition

Business Objectives

Operating Model

Desired level of Integration and

Standardization

Enterprise Architecture
Value proposition
Vision
Mission
To deliver leading edge bicycles in a prompt and efficient
To create a stable and reliable bicycle retail network.
manner utilizing creative ideas and solutions

Value Proposition

-Provide good experience to customers by providing superior quality products and excellent after-sales network.
Maturity stage of EA
AS-IS : RATIONALIZED Enterprise agility TO- BE : MODULAR
DATA ARCHITECTURE ARCHITECTURE

Redesign process to be independently

Base
1. Standardization deployable Processes could
of data and be made more
processes Dependency
Redesign processes with excessive incoming autonomous and
and outgoing dependencies customer
2. Core process oriented to
integration Process like Order mgmt., Inventory mgmt. enable business
Usability can be clustered for encapsulation
3. Shared product model extension
and customer data using modules
bases Extensibility
Redesign process such that features can be
added without halting the existing process
facilitating
reusability and
strategic agility.
Promoting standardized interfaces and
Utility deploying PIPs like PIP1A, PIP1B, PIP3A##
Operating Model – Unification
Centralized managed database
Most BUs are closely linked with one another
Globally integrated processes in all 5 locations across 2 countries – High Integration
Most processes or functions may be centrally defined by corporate office of GBI –
High Standardization
Customers and suppliers may be local or global
 ENTERPRISE IDEA-TO-MARKET
ARCHITECTURE Stakeholders
1.1 1.2 1.3
(CORE Product Product Product Customers
Design Trials
DIAGRAM) Research
Partners
LINKING TECHNOLOGIES (Dealers &
STACKS WIKI suppliers)
DATA Employees
Partners Inventory
Designers
BUILD-TO-STOCK
Transaction Sales
2.2 2.3 2.4
Production
2.1
Production Quality Inventory 4.1 Support 4.2 Partner
Production 4.3 Repairs
Management Assurance Management (Problem-to-resolution) Support
Planning and returns
Enablement
Product data Customers
Employee
CORPORATE
New Bike SERVICES
Designers Leads
SHAREPOINT Stores
DROPBOX
Customer
Bike parts
service

ORDER-TO-CASH SERVICES & SUPPORT

CRM
SYSTEM
3.1 Marketing 3.2 Sales 3.3 Partner 3.4 Invoice
Management Management Management Management
SOLUTION Products

Authentication

Operation Management System

BLUEPRINT Bikes

Delivery Interaction System (Consuming APIs)

SMS Stores Mobile Apps Web portal

Authorization
Social Media Handheld devices Partner Portals

Application Layer (Exposing APIs)

Production planning and Monitoring System Sales System Accounts System

Security

Access Token Management

IT Operations
Procurement System HR System Product Information System
Customer Information System Social Monitoring System

Customer Feedback System (Web 2.0) Personalisation Engine (Web 3.0)

Customer Activity System
Payment Gateway System Handheld Gateway System (Web 2.0)

IT tools to automate and support

SaAS (Software as a service)
Infrastructure Security

Networks Data centres Servers and Cloud Virtual Machines

Master Database Payment Information

Data Replicas Social Media Information
Scope of Web 2.0, Web 3.0, Social and Shared
Web 2.0 – Provide interactive feedback system and a forum for discussion for Global
Bike Community
Web 3.0 – Create a ML and AI based personalization experience for users who logged
in our system using some profile information.
Social – Provide certain models with a monitoring system which can monitor how
much you ride the bike. Now use Gamification techniques like batches etc. to
motivate riders to compete with others.
Shared – Create some fan clubs inn major cities and allocate some bikes for the clubs.
People can pay some amount and enjoy a ride and park the bike to some other
allocated spaces. This can promote company as well as build a loyal club.
Schema
(Snowflake) Time

• More structured (normalized), less redundancy

Product
Currency • Product
• Less disk space Fact • Category

(Revenue,
Discount,
Cost)

Geography Customer
• Customer
• City
• Sales
• Country
Organization
Dimension tables (1/4)

PRODUCT Product_ID
1
Product_Code
PRTR1000
Product _Desc
Professional Touring Bike-
Black
Product_Cat_ID
1
2 DXTR1000 Deluxe Touring Bike-Black
1
3 DXRD2000 Road Bike Alu SRAM
2

Product_Cat_ID Product _Cat_Code Product_Cat_Desc

1 TOU Touring Bike
2 ROB Roadbike

Primary Key
Foreign Key
Dimension tables (2/4)

TIME
Calendar_ID Day Month Year Date
1 1 1 2007 01012007
2 2 1 2007 02012007
3 3 1 2007 03012007

Primary Key
Foreign Key
Dimension tables (3/4)
CUSTOMER, Customer_ID
17000
Customer_Desc
Cruiser Bikes
City_ID
1
Sales_Org_ID
1
GEOGRAPHY 15000 Bavaria Bikes 2 2
Sales_Org_ID Sales_Org_Code Sales_Org_Desc
1 DNOO XYZ
2 DSOO ABC
City_ID City_Desc Country_ID
1 Hannover 1
2 München 1
Country_ID Country_Code Country_Desc
1 DE Germany

Primary Key
Foreign Key
Dimension tables (4/4)

CURRENCY
Currency_ID Currency_Code Currency_Desc Base_Currency_ID Exch_Rate
1 USD US Dollar 1 1
2 EUR Euro 1 1.5

Primary Key
Foreign Key
 Fact Table
Order_ID Order_Nu Product_ID Calendar_I Customer_I Currency_I Sales_Qty Revenue Discount Cost
mber D D D
1 100001 1 1 1 2 4 10669.84 320.81 6000

Primary Key
Foreign Key
Analytics questions that can be
answered
In which particular time period (week/month/quarter..) or season are the revenues
dipping?
Which SKUs/Product categories should be stopped/promoted in which region(s)?
Forecast revenue, cost, profit across any desired dimension combination
Which sales organization/customer groups to target
Most profitable product categories, considering sufficient sales quantities
Break-even analysis across geographies to formulate region-specific strategies