Connected Retail Reference Architecture

•Download as PPT, PDF•

7 likes•7,673 views

Please use the below URL to view recording of this webinar: http://wso2.com/library/webinars/2015/02/connected-retail-reference-architecture/ The key focus areas of this session are An overview of the retail IT landscape What is a connected retail IT architecture How the WSO2 middleware platform enables a connected retail business Connected retail L0 architecture Connected retail L1 architecture with WSO2

February 2015
Connected Retail Reference
Architecture
Software Architect
Kasun
Indrasiri

2
About WSO2
๏ Global enterprise, founded in 2005
by acknowledged leaders in XML,
web services technologies, standards
and open source
๏ Provides only open source platform-as-
a-service for private, public and hybrid
cloud deployments
๏ All WSO2 products are 100% open
source and released under the Apache
License Version 2.0.
๏ Is an Active Member of OASIS, Cloud
Security Alliance, OSGi Alliance, AMQP
Working Group, OpenID Foundation
and W3C.
๏ Driven by Innovation
๏ Launched first open source API
Management solution in 2012
๏ Launched App Factory in 2Q 2013
๏ Launched Enterprise Store and
first open source Mobile solution
in 4Q 2013

About the Presenter
๏ Kasun Indrasiri
๏ Software Architect and Product Lead of WSO2 ESB
4

Agenda
๏ An overview of the retail IT landscape
๏ What is a connected retail IT architecture
๏ How the WSO2 middleware platform enables a
connected retail business
๏ Connected retail L0 architecture
๏ Connected retail L1 architecture
๏ Customer Stories
5

‘Retail’
๏ Selling goods and services to the final consumer.
6 https://www.espatial.com/wp-content/uploads/PicA4.jpg

Types of Retail Businesses
7 Source : http://www.ramganalytics.com/wp-content/uploads/2014/07/Retailers.png

8
An overview of Retail IT
Source : http://www.celerant.com/images/tke_command.gif

9
An overview of Retail IT
Source : http://www.infinityrms.com/assets/img/diagrams/infinity-rms-pos-software-modular-architecture-diagram.gif

๏ Product, Order, Inventory and Supply chain
Management Systems(Legacy or proprietary systems)
๏ Distributed deployments (eg: PoS and main data
center)
๏ Merchandising/Business Intelligence : Market
Analysis, Trends
๏ Proliferation of Devices : Mobile and API enablement
๏ Cloud Services (eg: Paypal)
10
An overview of Retail IT

๏ Building an internally and externally connected retail
business
๏ A competitive and globalized retailed business,
requires to quickly launch products and promotions
and provide enhanced customer experience.
๏ Consistent engagement, seamless shopping,
personalized attention, and memorable interactions.
11
A ‘Connected Retail’

๏ Create rich customer experience (eg: Fast checkouts)
๏ Develop a transparent, collaborative, real-time
supply chain. (optimize the inventory stock)
๏ Offer multichannel data/sales management.
(proliferation of devices)
๏ Price management. (upload price updates seamlessly)
๏ Point-of-sale (POS) transformation. (move away from
p2p model)
12
Challenges in building a Connected Retail
Source : msdn - http://msdn.microsoft.com/en-us/library/bb264584.aspx

Connected Retail Reference Architecture
(L0)
13

Connected Retail Reference Architecture
(L1)
14

๏ Ultra fast Message routing with low latency. (over 6
Billions of transactions)
15
Use Case I – High volume message
routing

๏ Integrating : SAP and Non SAP systems, databases and
message broker
16
Use Case II – Distributed Point of Sale

6
Links
๏ Enabling a Connected Business -
http://wso2.com/landing/enabling-the-connected-business/
๏ Connected Business webinar series -
http://wso2.com/landing/connected-business-webinar-series/
๏ Convert your enterprise to a Connected Business –
http://wso2.com/whitepapers/convert-your-enterprise-to-a-
connected-business/

The ArchiSurance Case Study is a fictitious example developed to illustrate the use of the ArchiMate® modeling language in the context of the TOGAF® framework. The Case Study concerns the insurance company ArchiSurance, which has been formed as the result of a merger of three previously independent companies. The Case Study describes the baseline architecture of the company and then a number of change scenarios. This Case Study is required to be used as an example throughout accredited ArchiMate training courses. However, it is not part of the definition of TOGAF. This work supports The Open Group vision of Boundaryless Information Flow by illustrating the combined use of the TOGAF and ArchiMate standards for consistent representation of architectural information across diverse organizations, systems, and initiatives.

EA foundations (Views, Repository, Artifacts and Metamodel)

Mohamed Zakarya Abdelgawad

Modeling the Insurance EnterpriseIver Band

Modeling Big Data with the ArchiMate 3.0 Language

Iver Band

Health care enterprises use big data methods and technologies to gain insights for improving the efficacy, efficiency, and accessibility of their services. Effective big data initiatives require shared understanding among diverse stakeholders of business challenges and the often complex architectures required to address them. Enterprise and solution architects can use the ArchiMate language to build this understanding with compelling visual models. This presentation introduces the ArchiMate 3.0 language, and uses it to explore the US National Institute of Standards and Technology (NIST) Big Data Reference Architecture (NBDRA), and to present a health care case study based on the NBDRA. Participants will learn how to use the ArchiMate 3.0 language, in alignment with the TOGAF framework, to propose, justify and plan big data initiatives, and to guide their successful implementation.

ADM Target Operating Models

Steven Hall

Talk given at the business architecture Master Series in Sydney October 2019. Agility is here to stay. But dig a little deeper and you will see that fundamental strategic, structural and cultural issues exist that often prevent success within large organizations. Some organizations have learnt the hard way when it comes to the missing pieces of the puzzle around organizational agility. I was recently asked by a new-ways-of-working team to help them apply business design to create the target operating model needed to enable structural, operational and strategic agility. Is this the secret sauce that’s been missing in the agility conversations? In this talk I’ll discuss the broader issues around agility when creating the adaptive and fast learning organization. And discuss the "secret sauce" that is missing when it comes to business heuristics and patterns. I will also look at the areas where agility is succeeding and failing and discuss the need for multi-disciplinary architects that can help with the transition across strategic, business and delivery lenses. PS - this is a presentation pack. I dont put everything I talk to into a slide. Some of these slides will therefore lack some context for you. Next time I'll record the talk and you can hopefully catch the story around the slides.

Data Architecture for Solutions.pdf

Alan McSweeney

The data architecture of solutions is frequently not given the attention it deserves or needs. Frequently, too little attention is paid to designing and specifying the data architecture within individual solutions and their constituent components. This is due to the behaviours of both solution architects ad data architects. Solution architecture tends to concern itself with functional, technology and software components of the solution Data architecture tends not to get involved with the data aspects of technology solutions, leaving a data architecture gap. Combined with the gap where data architecture tends not to get involved with the data aspects of technology solutions, there is also frequently a solution architecture data gap. Solution architecture also frequently omits the detail of data aspects of solutions leading to a solution data architecture gap. These gaps result in a data blind spot for the organisation. Data architecture tends to concern itself with post-individual solutions. Data architecture needs to shift left into the domain of solutions and their data and more actively engage with the data dimensions of individual solutions. Data architecture can provide the lead in sealing these data gaps through a shift-left of its scope and activities as well providing standards and common data tooling for solution data architecture The objective of data design for solutions is the same as that for overall solution design: • To capture sufficient information to enable the solution design to be implemented • To unambiguously define the data requirements of the solution and to confirm and agree those requirements with the target solution consumers • To ensure that the implemented solution meets the requirements of the solution consumers and that no deviations have taken place during the solution implementation journey Solution data architecture avoids problems with solution operation and use: • Poor and inconsistent data quality • Poor performance, throughput, response times and scalability • Poorly designed data structures can lead to long data update times leading to long response times, affecting solution usability, loss of productivity and transaction abandonment • Poor reporting and analysis • Poor data integration • Poor solution serviceability and maintainability • Manual workarounds for data integration, data extract for reporting and analysis Data-design-related solution problems frequently become evident and manifest themselves only after the solution goes live. The benefits of solution data architecture are not always evident initially.

Approaches to business architecture

Real IRM

In this presentation Michael Payne debates the merits of placing Business Architecture within an organisation’s Business, IT or Enterprise Architecture departments. He examines some of the options available to organisations starting out with Business Architecture, and touches on Business Architecture engagement models. In addition, Michael provides a sneak peak into the new developments in the Open-BA Framework.

Digital Transformation Strategy and Plan Template

Aurelien Domont, MBA

Business Architecture - Paul Turner

IIBA UK Chapter

Slides from a presentation given by Paul Turner to meetings of IIBA UK on 16 July and 12 August 2014. Much has been written about technical and solution architectures, without due attention being given to how these work together with the Business Architecture. It is easy to believe that those who are involved in business analysis, requirements definition and systems modelling do not need to consider the Business Architecture at all. This could not be further from the truth. This talk explains the rationale behind Business Architecture, what its main components are and why Business Analysts should ensure that they understand it and the influence it is likely to have on their work.

Enterprise Architecture Implementation And The Open Group Architecture Framew...

Alan McSweeney

Business Value Metrics for Data Governance

DATAVERSITY

As data professionals, we recognize and understand the need for data governance, focusing on data quality in particular. We have made progress in this area, as illustrated by the emergence of the Chief Data Officer role in recent years. However, in many organizations, the need for governance is still largely unrecognized, and remains very tough to sell internally. You may need some detailed information and metrics to demonstrate the business value. This session will focus on business justification for establishing a data governance framework, including: Data classification Data quality Business value metrics (KPIs)

Togaf 9 overviewEnterpriseArchitects

Bringing Architecture Thinking to the People - An introduction into the PEOPL...

Craig Martin

The successful implementation of an architecture plan or blueprint is often challenged not in the efficacy of the design elements of the architecture, but in its implementation by people in business operations. Transformation programs will often struggle as a consequence of the failure to consider the issues impacting and the role of people in supporting the target operating state of the architecture once implemented, it is therefore imperative that when architects innovate, model and design to solve business problems, that they equally consider the people dimension. Capability based planning is incomplete unless we address the optimum mix of people, process and tools to drive out the target outcome of that capability. This presentation will look at a case study from within the Australian market in which Business Capability Based Planning was applied to assess people capabilities and organisation preparedness to support a target business model. It will also discuss some of the more effective people levers that can be applied to deliver more impactful and long lasting architectural change.

Building a strong Data Management capability with TOGAF and ArchiMate

Bas van Gils

An Introduction into the design of business using business architecture

Craig Martin

Business Architecture is gaining interest from many non-traditional architecture stakeholders across the enterprise however most remain unclear of its scope and application. This webinar was presented through the Open Group as lead up to the London 2013 Conference on business transformation. It provides an overview of the language, methods and techniques of developing a business architecture and assist architects to demonstrate its relevance to business leaders. It also provides an insight into the method and techniques taught in the "Discovering Business Architecture" course run by Enterprise Architects.

Application RationalizationCarolyn Reid

On business capabilities, functions and application features

Jörgen Dahlberg

Design Science and Solution Architecture

Alan McSweeney

This examines the potential for the application of Design Science principles to the solution design process within solution architecture to improve the rigour and accuracy of solution designs. Design Science is the structured and systematic process for creating designs that resolve problems. It is concerned with the structured process for the acquisition and application of knowledge in relation to the problems to the resolved and the solution knowledge to be applied. The application of Design Science must be a means to an end – better solution quality – and not an end in itself – an incentive for the design function is to become large. Solution architecture requires a (changing) combination of technical, leadership, interpersonal skills, experience, analysis, appropriate creativity, reflection and intuition applied in a structured manner. Knowledge management – problem knowledge and solution knowledge – is at the core of the application of design science principles. Knowledge management requires good management of the solution architecture function.

Solution Architecture Centre Of Excellence

Alan McSweeney

This is an extract from the book An Introduction to Solution Architecture (https://www.amazon.com/dp/1797567616) that discusses the topic of a Solution Architecture Centre Of Excellence. The solution architecture function should aspire to be a Solution Architecture Centre Of Excellence (SACOE). This is concerned with developing a mature function that is highly-skilled at solution architecture and design and provides solution and consulting leadership to the organisation. Developing an SACOE requires vision and resources of both the solution architecture function and information technology management. The solution architecture function has the capability to develop both the business insight and solution and technology expertise to act as the business/technology authority and be the bridge between the business and technology domains of the organisation.

Introduction to business architecture

Aniekan Okono

Practical Enterprise Architecture - Introducing CSVLOD EA Model

Ashraf Fouad

EDGY introduction webinar

Intersection Group

Watch the video: https://www.youtube.com/watch?v=AV_U3fJjNXE Designers, architects and analysts habitually produce maps and visualizations. EDGY is designed to be a visual language to create mappings and visualisations as perspectives on an enterprise model. Instead of just producing more and more isolated artefacts, we create individual mappings as representations of an integrated semantic model. Here are a few questions you should ask when designing better enterprises: - What is your enterprise all about? What is its story? Who are the people behind it? What is their motivation? This is the identity of the enterprise; what it stands for and the reason for its existence. - What will you actually provide to people? What are offering? How is what you offer going to change people’s lives? This is the experience the enterprise aims to create for customers and others. - What do you need to realise that? What are the parts that make it work? How are those parts related? What can you achieve with them? This is the architecture that holds the enterprise together. In the past, these questions have been treated separately by specialist functions and disciplines, leading to incoherent, siloed, underperforming enterprises. Elements like a sound strategy, a well performing operating model, or a winning product design are simply impossible to get right if there is no coherence in the way people working to create the enterprise (its cocreators) answer these questions.  These universal facets of identity, experience and architecture apply to all enterprises: large companies, start-ups, public institutions, ... . They provide useful lenses to understand why an enterprise exists, what it is supposed to deliver to whom, and how all of this is supposed to work.  EDGY, a graphical language for collaborative enterprise design, is complementary to more specific visual languages such as ArchiMate or UML but covers a broader range of view angles needed to create better enterprises.

Process Oriented Architecture

Alan McSweeney

This describes the concept of a Process Oriented Architecture. A Process Oriented Architecture is a way of linking process areas to actual (desired) interactions – customer (external interacting party) service journeys through the organisation. It allows two views of any process to be maintained and operated: 1. External view – that experienced by user 2. Internal view – that worked on by the organisational competency An organisation will interact will multiple external parties. Each external party will have a number of interaction paths or journeys. These journeys are the routes of experience of external parties. These routes of experience need to be mapped (as) seamlessly (as possible) to internal organisational operational process competency groupings. The interaction paths or journeys represent the Straight Through Processing that the customer (external party) wants to experience. The complexity of internal organisational operational process competency groupings needs to be masked from the customer (external party). Process Oriented Architecture is a key enabler of successful digital transformation.

Retail Reference ArchitectureMongoDB

Retail 2.0 Strategy - Perfect Store PDFNigel Tebbutt 奈杰尔泰巴德

What's hot

Togaf 9.1 ADM summary

Marco Bakker

The need for Business design to underpin strategic and operational agility

Craig Martin

Data Architecture for Solutions.pdf

Alan McSweeney

Approaches to business architecture

Real IRM

Digital Transformation Strategy and Plan Template

Aurelien Domont, MBA

Business Architecture - Paul Turner

IIBA UK Chapter

Enterprise Architecture Implementation And The Open Group Architecture Framew...

Alan McSweeney

Business Value Metrics for Data Governance

DATAVERSITY

Togaf 9 overviewEnterpriseArchitects

Bringing Architecture Thinking to the People - An introduction into the PEOPL...

Craig Martin

Building a strong Data Management capability with TOGAF and ArchiMate

Bas van Gils

An Introduction into the design of business using business architecture

Craig Martin

Application RationalizationCarolyn Reid

On business capabilities, functions and application features

Jörgen Dahlberg

Design Science and Solution Architecture

Alan McSweeney

Solution Architecture Centre Of Excellence

Alan McSweeney

Introduction to business architecture

Aniekan Okono

Practical Enterprise Architecture - Introducing CSVLOD EA Model

Ashraf Fouad

EDGY introduction webinar

Intersection Group

Process Oriented Architecture

Alan McSweeney

What's hot (20)

Togaf 9.1 ADM summary

The need for Business design to underpin strategic and operational agility

Data Architecture for Solutions.pdf

Approaches to business architecture

Digital Transformation Strategy and Plan Template

Business Architecture - Paul Turner

Enterprise Architecture Implementation And The Open Group Architecture Framew...

Business Value Metrics for Data Governance

Togaf 9 overview

Bringing Architecture Thinking to the People - An introduction into the PEOPL...

Building a strong Data Management capability with TOGAF and ArchiMate

An Introduction into the design of business using business architecture

Application Rationalization

On business capabilities, functions and application features

Design Science and Solution Architecture

Solution Architecture Centre Of Excellence

Introduction to business architecture

Practical Enterprise Architecture - Introducing CSVLOD EA Model

EDGY introduction webinar

Process Oriented Architecture

Viewers also liked

Retail Reference ArchitectureMongoDB

Retail 2.0 Strategy - Perfect Store PDFNigel Tebbutt 奈杰尔泰巴德

Retail Reference Architecture Part 2: Real-Time, Geo Distributed Inventory

MongoDB

During this session we will cover the best practices for implementing a real-time inventory with MongoDB. This includes properly model quantities and stores to avoid large numbers of documents being indexed, how to efficiently use geo-indexing to find the closest store with a specific item available and how to run aggregation to gather interesting inventory stats. We will also cover operational considerations, like how to make inventory queries and updates from anywhere be low-latency and resilient to network partitions via tag-aware sharding.

Oracle Retail

Rasheed Abdul

Modern Architectures: Building a Sustainable Roadmap

Salesforce Developers

Oracle retail financial integration 13.2.6

Federman Hoyos

Retail Reference Architecture Part 3: Scalable Insight Component Providing Us...

MongoDB

During this session we will cover the best practices for implementing the insight component with MongoDB. This includes efficiently ingesting and managing a large volume of user activity logs, such as clickstreams, views, likes and sales. We'll dive into how you can derive user statistics, product maps and trends using different analytics tools like the aggregation framework, map/reduce or the Hadoop connector. We will also cover operational considerations, including low-latency data ingestion and seamless aggregation queries.

Oracle Retail - Insight Driven Retailing

Blue Events

Design and Instantiation of Reference Architecture for Pluggable Service Plat...

Mohammad Anggasta Paramartha

Importance of retailingjonessoda35

High Volume Web API Management with the WSO2 ESB

Paul Fremantle

Strategic and Inclusive Enterprise Architecture Apr 2011 v 1.1rahmanmokhtar

OLED

Farzan Dehbashi

The executive Guide to CRM architechture

Pivotal CRM

How salesforce.com Uses Hadoop Webinar

Salesforce Developers

Hadoop is the technology of choice for processing large data sets. At salesforce.com, we service internal and product big data use cases using a combination of Hadoop, Java MapReduce, Pig, Force.com, and machine learning algorithms. In this webinar, you will learn about an internal use case and a product use case: :: Product Metrics: Internally, we measure feature usage using a combination of Hadoop, Pig, and the Force.com platform (Custom Objects and Analytics). :: Community-Based Recommendations: In Chatter, our most successful people and file recommendations are built on a collaborative filtering algorithm that is implemented on Hadoop using Java MapReduce.

Erp billing crm ecommerce gestionale pos sito webERP - Billing & CRM

Requirements Hierarchy - A Journey through the Requirements Lifecycle

Marie Halsey

How do you get from “We need something different” to detailed requirements? What do requirements look like as they evolve through the phases of the requirements lifecycle? What are the deliverables in each phase? This presentation discusses three phases of requirements definition – Scope, High Level Requirements and Detailed Requirements. The components of the deliverables in each phase are described, examples of the evolution of requirements through the lifecycle phases are presented, and guidelines for each deliverable are provided. Learning Objectives: • Understand the components of the three levels of requirements – Scope, High Level Requirements and Detailed Requirements. • Understand the evolution of requirements through each level. • Guidelines for each level of requirement

Business architecture in perspective v2.1John Bernhard

Retail depolyment architectureVENUS TELE-LINKS

James hall ch 3

David Julian

Viewers also liked (20)

Retail Reference Architecture

Retail 2.0 Strategy - Perfect Store PDF

Retail Reference Architecture Part 2: Real-Time, Geo Distributed Inventory

Oracle Retail

Modern Architectures: Building a Sustainable Roadmap

Oracle retail financial integration 13.2.6

Retail Reference Architecture Part 3: Scalable Insight Component Providing Us...

Oracle Retail - Insight Driven Retailing

Design and Instantiation of Reference Architecture for Pluggable Service Plat...

Importance of retailing

High Volume Web API Management with the WSO2 ESB

Strategic and Inclusive Enterprise Architecture Apr 2011 v 1.1

OLED

The executive Guide to CRM architechture

How salesforce.com Uses Hadoop Webinar

Erp billing crm ecommerce gestionale pos sito web

Requirements Hierarchy - A Journey through the Requirements Lifecycle

Business architecture in perspective v2.1

Retail depolyment architecture

James hall ch 3

Similar to Connected Retail Reference Architecture

Combining WSO2 API Manager with WSO2 BAM for billing in the energy industryWSO2

Webinar combining WSO2 API Manager with WSO2 BAM for billing in the energy in...

Yenlo

With the help of the WSO2 API Manager, companies are able to reduce their time-to-market dramatically. This webinar demonstrates how a large energy company uses the WSO2 API Manager to do just that. The API manager is used to unlock existing back-end services quickly, so new business initiatives get connected to the main sources of data and information in a uniform way. At a service level, it will also provide the right authentication and authorization. Besides discussing the WSO2 API Manager, this webinar also covers the way AWS cloud website hosting is used to decrease the time-to-market and the service usage for billing purposes in combination with WSO2 Business Activity Monitor (WSO2 BAM). Subjects covered Usage of the API manager (in general) Usage of Puppet scripts for automatic deployment AWS for cloud website hosting Combining WSO2 API Manager with WSO2 BAM for billing Usage of WSO2 Identity Server for central identity management Watch this webinar about WSO2 BAM and WSO2 API Manager here: http://www.yenlo.com/en/web-combining-wso2-api-manager-with-wso2-bam

API Management within a Microservice Architecture

Connected Retail Reference Architecture

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to Connected Retail Reference Architecture

Similar to Connected Retail Reference Architecture (20)

More from WSO2

More from WSO2 (20)

Recently uploaded

Recently uploaded (20)

Connected Retail Reference Architecture