Digital Architecture Methodology for Systemic Digital Transformation (Smart Cities are an example)

Digital Architecture
Methodology
for
Systemic
Digital Transformation
(Smart Cities are an example)
Digital Architecture Summit
Nov 19-21, 2019, NY, USA
Dr Alexander Samarin
iCMGworld.com

• Digital transformation practitioner, architect and
methodologist
– from a programmer to a systems architect
– have created production systems which work without me
– systems of various sizes: company, corporate, canton, city,
country, continent, community
• Some of my professional roles
– “cleaning person” (usually in an IT department)
– “peacemaker” (between the IT and business)
– “swiss knife” (for solving any problem)
– “patterns detective” (seeing commonalities in “unique” cases)
– “assembler” (making unique things from commodities)
– “barriers breaker” (there is always a bigger system)
– “scribe and futurist” (AS-IS & TO-BE viewpoints)
© A. Samarin 2019 Digital Architecture Methodology for Systemic Digital Transformation 2
About me

• Digital Transformation (DT) is as daunting task because
scope, depth, speed, risks, gains, etc. are scaled up
• Digital systems are fragile thus must be done carefully
• DT is a flow of changes which are
– Disruptive, risky, complex and unpredictable
– Neither for waterfall
– Nor for agile
• Such a flow of changes requires flawless execution
– What is this next change?
– Why to carry out next change?
– How to carry out next change?
– Who will gain / lose /pay in this next change?
– What will be the changes in the flow of changes?
Digital Transformation is difficult
X
X

• DT never ends; Forbes called DT “lifestyle”
• 70-80% failure rate (with trillions USD)
• Many good recommendations but no “key thread”
• Current approaches to DT are messy
– New key roles (Chief Data Officer, Chief Digital Officer and Chief
Digital Transformation Officer)
– Existing key roles (CIO, CTO, Enterprise Architect)
– Old unresolved problems (where, when and how create and
deliver value to the customers)
– New challenges (e.g. rapid world-wide competition and
technological pressure, fragility of digital solutions and platforms)
• Everyone understands “digital” and “DT” differently
Digital Transformation is expensive

IT community folklore
CDO CDTO
EA
Digital
Transformation

• Context for “digital” Digital as discrete, not analogue,
not physical and not mental
• Meaning of “digital” Related to the presentation of data
by different states or discrete values
• Example – data in digital representation
• Related concepts
– Numbers are the basic concept of mathematics used to quantify,
compare, number objects and parts
– Numerical digits — a sign system to record specific numbers
values
What is digital – context 1

• Context for “digital” The basics of efficient use of
computers – representing objects
• Meaning of “digital” One of many representations of an
object
– physical, analogue, digital, bionic, etc.
• Digital representation is explicit, formal,
machine-readable and machine-executable
• For example of “machine-executable”:
– Using a 3D printer, you can translate a digital view of an object into
its physical view (i.e., print such an object);
– You can visualize an HTML document on a variety of devices
(including a conventional printer)

• Because many representations of the same object may
co-exist then the priority is important
• For a nature-made object, its digital representation is
always secondary
• For a man-made object, its digital representation may be
primary
primary vs secondary
Becoming
digital

What is digital - context 2
Many representations of a house
House design
(digital) v1
Built house
(physical) v1
Built house
(physical) v2
Built house
(digital)
Time
House design
(digital) v2
Implement Monitor Improve
Model Improve
Control
Alerts

• “Digital twin”
– a digital twin is a digital replica of a living or non-living physical
entity
• “Digital footprint” or “digital shadow”
– one's unique set of traceable digital activities, actions,
contributions and communications manifested on the Internet
• “Digital profile”
– a mixture of previous two
• However, in these cases, the digital representation is
secondary thus it is not used efficiently and DT
cannot bring all its benefits
• Let us consider the digital representation as primary one
What is digital - context 2
however, digital is considered secondary

• Context for “digital” Systems made primarily from
objects in digital representation
• Meaning of “digital” Systems are fully symbolic and
technical
• This digital representation is primary
• A change in software leads to changes in a system (for
the better or not)
software-defined “technical” systems

• Digital representation of the traffic (cars, lights, etc.) is
primary
Example
Intelligent Transportation System

Example
Software defined network

Example
Software defined based Smart Grid

• Software Defined Network + Wireless Sensors Network
• SD-WSN is used in water management
Example
SD-WSN

• Is the most difficult IT system!
Modern autonomous car

– see https://bpm.com/blogs/executable-architecture-of-software-defined-enterprises
Software-defined enterprise

Example of a software-define enterprise

• Smart cities, smart territories & countries, smart
manufacturing enterprises, smart grids, organisations, etc.
• Such systems
– are usually classified as “socio-technical” or “cyber-physical”
– comprise many various interwoven and interlinked “facets”
(economical, intellectual, biological, ethical, real-time systems,
software-intensive, computational, etc.) – similar to human body
– they are not “system of systems” or “system of ecosystems”
• All such “facets” must be mutually aligned to form the
system (consider the human body)
What’s about sociotechnical systems? (1)

• Why a system? Because only integration is not enough
• SMART CITY: effective integration of physical, digital and
human systems
• Fortunately, for each such facets its digital representation
(primary or secondary) can be built
DIGITAL
PHYSICALHUMAN

• Context for “digital” Dealing with multi-facet systems
• Meaning of “digital” Systems are partially symbolic
(based on the “double mirror” approach)
• Mr Orit Halpern: “computationally and digitally managed
systems”
– However, the whole life cycle must be emphasised
• Digitally coordinated system – system which is
architected, governed, managed and operated based on
the digital presentation of its elements, features and
relationships between them
• Short name “Digital System”; full name “Digitally
Coordinated Repeatable System”
digitally coordinated “socio-tech” systems

• There is a strong demand for sustainable future
– The Club of Rome
– Sustainable Development Goals from the UN
– Everything is requested being smart
• Essential requirements for smart cities
– combining diversity and uniformity
– achieving repeatability and scalability (e.g. 4 500+ cities with
150 000+ citizens need to become smart in a sustainable way)
– addressing complexity
• It is a systemic problem which has to be solved by
(re)building existing systems systemically as digitally
coordinated repeatable systems
Why digitally coordinated systems (1)

• Examples of multi-facet systems to become coordinated
systems
– economy sectors, enterprises, hospitals, universities
– homes, buildings, cities (including town, village, megapolis, etc.)
– territories, countries, unions of countries
– governmental agencies, ministries
• Digital Transformation (DT) of an existing system is
rebuilding it as a digitally coordinated system
• Unofficial definition
– Digital Transformation of any system is a permanent systematic
perestroika this system as a digitally coordinated system
Why digitally coordinated systems (2)

• Digital economy is an economy built as a digital system
• Digital country is a country built as a digital system
• Digital territory is a territory built as a digital system
• Digital enterprise is an enterprise built as a digital system
• Smart city is a city built as a digital system
• Smart building is a building built as a digital system
• Smart home is a dwelling built as a digital system
• Any digital system has to be “smart” because otherwise the
“digit” will not stand as the slightest mistake is a collapse
that spreads quickly with huge damage - well, as with a
house of cards. If you want to build a “smart” system,
today it must be “digital”. There's no other way yet.
Some related concepts

1. A digital element is easy repeatable (cloneable); copy
cost is zero
2. A universal (with rich functionality) digital system which
satisfies many customers is very difficult to create
3. A digital system is a coherent set of digital elements
connected in a digital way, since any system consists of
elements and connections between them
(“assembly” pattern)
Main secret of digital -
easy to create necessary variations (1)
e
d
a
b
c

4. Individual versions of digital systems can be easily
assembled from standard digital repeatable
elements (“Lego” pattern)
d
a
c
e
d
a
c
eda b c

5. Unique digital elements (labelled “1” and “2”) can be
quickly added as needed thus allowing the creation of
all sorts of individual versions of a digital system
(“platform” pattern)
6. If these unique digital elements become popular then
they can be included in the platform for wider distribution
(“software factory” pattern)
1
2
eda b c
PLATFORM
1
2eda b c
PLATFORM

7. When necessary a platform component can be replaced
by another component (labelled “β”) which follows the
same interfaces (“API” pattern)
• Thus, the most efficient and effective way of DT is
– coordinate and complement creating digital repeatable elements
– use methods for assembling digital repeatable systems from
digital repeatable elements
– reuse (e.g. sell, rent, copy) such elements and systems many
times
1
2eda β c
PLATFORM

• A lot of existing elements which constitute and support
such digital repeatable systems must get their digital
representations as well
– rights, currency, shares, laws, contracts, documents, business
processes, horizontal and vertical integration, etc.
• Life cycles of these elements will be (re)built on the
primacy of digital representation of those elements
Go to digital repeatable systems

• Rights on an asset become digital records and managed
by right owners directly
– rights on ownership, usage, etc.
– changes must be recorded in a third-party digital archive (e.g.
blockchain)
– right on a whole asset or part of it
– assets may be digital as well
– also known as “token”
Digital representation of supporting things
Rights (1)

Rights (2)
• Advantages of the Token Container Model (from The
Liechtenstein Blockchain-Act) https://cointelegraph.com/news/liechtensteins-parliament-
unanimously-approves-new-blockchain-act

Rights (3)
Non-fungible token

Rights (4)

• National currency gets its digital representation
– Digital Money of National Bank, e.g. digital-euro, to move it
directly from one owner to another; euro and digital-euro are
mutually exchangeable
– Potential implementations
• Only central bank (e.g. Tunisia https://www.chipin.com/digital-
dinar-tunisia-issues-electronic-central-bank-currency-e-dinar )
• China approach is 2 levels: National Bank and commensal
banks
• Peer-to-peer
• Enterprise shares become security tokens
National money and shares

• Contracts become digital contracts https://improving-bpm-
systems.blogspot.com/2016/07/digital-contract-as-process-enables.html
– Activities during the contract preparation phase:
1. Vendor and Buyer: Engage a “digital”
lawyer via a standard digital contract
2. Vendor: Propose contract
3. Lawyer: Validate contract
4. Buyer: Accept contract
5. Escrow: Seal contract
– Activities during the contract execution phase:
6. Buyer: Transfer money to escrow
7. Lawyer: Announce payment to vendor
8. Vendor: Deliver goods
9. Buyer: Announce acceptance of goods
10.Lawyer: Transfer money to vendor
– Activities during the contract closure phase:
11.Lawyer: Close the contract
Contracts

• Laws become digital
– e.g. GDPR
Digital presentation of supporting things
Laws

• Documents become structured, machine-readable and
machine-processable
• Identification of a person become digital and online
• Business processes become digital processes
• Horizontal and vertical integration is done by inter-
organisational digital processes
Many others (1)

1. Customers
2. Customer’s journey
3. Goods and services
4. Life cycles of goods and services
5. Business models
6. Business processes
7. Business decisions
8. Business partners(or ecosystem)
9. Transactions with partners and customers
10.Technology
11.Information
12.Data
Many others (2)
Magic
of data
as new
oil

• Systemically
– coherent viewpoints, views, descriptive and executable models
• Value-driven
– understand pains and cures
– understand flows of value, their performance and potentials
• Via Human Enterprise Learning Leadership (HELL)
– everyone is an important stakeholder who must learn and act
• Trustworthiness by design
– privacy by design, quality by design, etc.
• With coordination, complementation and copying
– to address next uber-complex challenges with limited talent resources
How to transform a system to the digital one

Smart City makes the world better for
citizens, society, business and government
• Primary beneficiary (citizens and society) - Significant
improvement in living standards; the rapid and effective creation of a
wide range of goods and services based on Digital Economy
• Secondary beneficiary (business) - Ease of doing business (EoDB),
creating new sectors of the economy and entering new markets
• Tertiary beneficiary (government) - Systematic and manageable
implementation of a complex transformation of a city; increasing
predictability and reducing risks associated with a complex
transformation of a city
• One of the Sustainable Development Goals
• 4 500+ cities (with 150 000+ citizens) to become
smart (thus sustainable) in a sustainable way
– i.e. by transforming cities into digital repeatable systems

• Unpredictable and unlimited growth and development
• Each city is different
• All cities have some commonalities
• Digital data and information in huge volumes
• Contradictory demands for security and privacy
• Many diverse stakeholders
• Distributed and decentralised
• Great influence on our society
• Multidisciplinary
• City is a system of various (social, economic, technical,
physical, intellectual, biological, and its mixtures)
interwoven and interdependent systems
Smart City complexity

To implement many similar systems –
use pattern “4 Levels of architecting”
2.Reference
architecture
1.Reference
model
4. Implementation
A2
3. Solution
architecture B
3.Solution
architecture A
4. Implementation
A1
build and test
refine
design and engineer
architect
extract essentials
refine
refine
design and engineer
Problem space Solution space
General needs
- stakeholders
- quality
- system
- domain
architect
extract
align
Reference Architecture is a
template for many Solution
Architectures
City A specific needs
- stakeholders
- quality
City B specific needs
- stakeholders
- quality

Pattern “Reference Architecture”:
a common need for a sustainable solution
Common parts
Unique parts
A A B B T T
Citizens
Society
Business
Government
Citizens
Society
Business
Government
Citizens
Society
Business
Government
Let us
1) Build common understanding
2) Isolate common parts
3) Find how to integrate unique and common parts
4) Develop common parts once and with high quality as a platform
5) Have a version of the common platform at each Smart City
6) Cooperate, complement and copy among Smart Cities
Together Smart Cities will gain a lot in quality, time and money

Architecting DT for Smart Cities:
a common understanding of common parts
A A B B T T
Common parts
Unique parts
Standards Development
Organizations (IEC, ISO, ITU,
JTC1, IEEE, …)
Industries
Academic and
research
institutes
IEC SyC Smart Cities WG3
Smart Cities Reference
Architecture (SCRA)
and Smart Cities
Reference Architecture
Methodology (SCRAM)
IEC/TC …
IEC/SyC
ISO/PC
ISO/TC JTC1
Citizens
Society
Business
Government
Citizens
Society
Business
Government
Citizens
Society
Business
Government
Best practices
Best knowledge
Best standards
SCRAM & SCRA
1) all digital solutions are repeatable
2) each city may add its own solutions
under the common methodology, i.e. SCRAM

repeatable solutions for common parts
Common Smart Cities
digital repeatable platform
S2 …S1
S3
A
2
Telecommunication
providers
Industries
Academic and
research institutes
Financial organisations
IT companies (start-
ups, local, global)
City A
S1
S3
City B
S2B1 B3
City T
T1
T3
Common parts
Unique parts
Coordination, complementating and copying of digital
repeatable solutions and systems
SCRA and SCRAM
IEC/TC …
IEC/SyC ISO/PC
ISO/TC JTC1
Standards Development Organizations
(IEC, ISO, ITU, JTC1, IEEE, …)
IEC SyC Smart Cities WG3
Citizens
Society
Business
Government
Citizens
Society
Business
Government
Citizens
Society
Business
Government
Primary market:
City digital transformation
Secondary market:
Platform implementation
Secondary market:
Platform implementation
Primary market:
City digital transformation

investment opportunities
Common Smart Cities
S2 …S1
S3
A
2
City A
S1
S3
City B
S2B1 B3
City T
T1
T3
Common parts
Unique parts
Coordination, complementating and copying of digital
repeatable solutions and systems
SCRA and SCRAM
IEC/TC …
IEC/SyC ISO/PC
ISO/TC JTC1
Citizens
Society
Business
Government
Citizens
Society
Business
Government
Citizens
Society
Business
Government
Institutional
investors
Ordinary
investors and
crowdfunding
Smart Cities FUND
10%
yield
First comers advantage
Platforms acts
an amplifier for
4 500+ cities
City
infrastructure
insurance
companies
Eliminate
negative yield of
several trillion
USD market
Estimations are provided (mid
2019) by company Relex
(www.relex.io) which is
specialised in real estate
crowdfunding

• Many disciplines to be used together
• The whole system life cycle
– conception, development, production, utilization,
support, retirement and destruction
• There is no one single framework
which covers all of these phases
• However, there are many frameworks
which are “monolith” (also known as “silos”)
– ZF, TOGAF, PEAF, POET, FEAF, DoDAF, MoDAF, NAF, RM-ODP,
JTC1/SC7 software engineering standards, CoBIT, ITSM (ITIL), ISO
20000, ISO 27000, ISO 9000, BIZBok, BABok, BPMBoK, PMBok and
many other “disciplines” such as DevOps, Agile, SCRUM, etc.
• Smart Cities Reference Architecture Methodology (SCRAM)
• Smart Cities Reference Architecture (SCRA)
How to describe such architecture?

Geometrical views of buildings are viewed side by
side — as a composition
ISO/IEC/IEEE 42010:2011
architecture description
Views (system-in-focus dependent) are governed by
viewpoints (system-in-focus independent)
Each view comprises one or many models. Any model consists of artefacts (e.g.
applications, servers, products, reports, etc.) and relationships between them.
Models (system-in-focus dependent) are governed by model-kinds (system-in-focus
independent).
Architecture views are often originated by different
people — thus they must be aligned to be used together

All frameworks comprise many model-
kinds

• The SCRAM did the following
1. Decomposed pertinent “monolith” frameworks into smaller pieces
2. Sorted those pieces out
3. Structured those pieces
• SCRAM viewpoints
• SCRAM model-types (or model-kinds)
• SCRAM artefact-types
• SCRAM patterns
• SCRAM viewpoints are containers for SCRAM model-types
• SCRAM model-types link SCRAM model-types and/or
SCRAM artefacts-types
• SCRAM patterns are methods to create an SCRAM model-
type from other SCRAM model-types
SCRAM: Collection of digital viewpoints,
model-types, artefacts-types and patterns

• SCRA models and SCRA artefacts are parts of a system-
of-interest and its architecture description (because they
are digital)
SCRAM: methodology reference model

SCRAM/SCRA: Some models may be generated
from others
View A
Model 1
Model 2
Common techniques,
patterns, guesses, magic, full
traceability, automation, etc.
View B
Model 3
EA gold
mine

Example: from functions to org. units (1)

• Business concern: How to structure a business unit
• Logic
– Collect functions
– Draw a matrix of mutual relationships between those functions
– The relationships may be like “synergy”
– The relationship may be like “prohibition”, e.g. SoD
– Find clusters in the matrix
Pattern Structure IT Organisation (SITO)

• Prohibition rules
– P1 Separate doing and supervising/controlling – SoD
– P2 Separate architecture/design and implementation – SoD,
specialisation and quality at entry
– P3 Separate implementation and operation – SoD, specialisation
and quality at entry
– P4 Policy vs applying it – legislation vs executive separation
– P5 Specialisation
• Synergy rules
– S1 Close work
– S2 Architecture role to guide
– S3 Synergy between technical and administrative activities
(how you do something may be more important what you do)

• Business concern
– dealing with the project portfolio during evolution of the strategy:
intended, emerging and realised
• Logic
– explicitly linking strategic objectives, initiatives, business
capabilities, IT capabilities, IT tools and projects
– add priorities
Pattern: Strategy To Executable Portfolio
(STEP)

Business
initiatives
(business-specific
demand)
Business
capabilities
(business-
generic
demand)
IT
capabilities
(IT-generic
supply)
Roadmap
programmes
(from AS-IS
to TO-BE)
Business demand IT supply
Business
strategic
objectives
Governance
Maturity improvementRequested maturityBusiness priority
1
2
3
2
2->5
2->4
1->3
1->4
2->4
1->3
2->5
2->4
3->4
4
4
5
3
1
2
3
4
4
1
1
2
3
2
2
4
4
5
3
3->4
1->4
3->5
3->4
2->4
IT tools
(IT-specific
supply)
3
Programme priority
5
4
3
4
4
Dynamic relationships between various
artefacts
Manage
business by
processes
Manage
processes BPM suite

• Implications
– A formal way to discover points of the most leverage
– The decision-making process is explicit and transparent
– A strategy adjustment and validation becomes a routine on-going
activity during its implementation (like functioning of the GPS
navigator)
– Add $$$$$
Implications and example

• Process
• Classifications
• Assembles
• Tensors
• General schemas
SCRAM: Complex dependencies
examples

Natural dependencies of models
Model A Model B
Model u1
Model D Model E
Model u2
Model G
Model A View N … Pattern 1 Pattern 2 …
A model can be in one or many views
Custom models

SCRAM vs SCRA
SCRAM viewpoints
SCRAM is a set of architecting rules SCRA is an architecture of an idealized city
SCRAM model-types
SCRAM artifact-types
SCRA views
SCRA models
SCRA artifacts
govern
govern
govern
in SCRAM
in SCRA

• VALUE viewpoint
• BIG PICTURE viewpoint
• SYSTEM-SOLUTION ENGINEERING viewpoint
• PLATFORM ENGINEERING viewpoint
• PLATFORM COMPONENT ENGINEERING viewpoint
• SOLUTION ENGINEERING viewpoint
• CROSSCUTTING ASPECTS ENGINEERING viewpoint
• CORPORATE viewpoint
• RISK MANAGEMENT viewpoint
• SOFTWARE FACTORY viewpoint
• STANDARDS viewpoint
SCRAM: a set of viewpoints (11) and
model-types (107)
TOGAF
DoDAF
BIZBok
BABok
JTC1/SC7
CoBIT
ITSM, ITIL, ISO 20000
ISO 27000
ISO 9000
BPMBoK
PMIBoK
DevOps
Agile
SCRUM
RM-ODP

• There is a “happy path”
• Actually, it will be “pinball” because if something has been
changed that all connected elements must to be validated
SCRAM: Dependencies between
viewpoints and model-types

SCRAM: VALUE viewpoint

SCRAM: BIG PICTURE viewpoint

SCRAM: SYSTEM-SOLUTION viewpoint

PLATFORM ENGINEERING viewpoint

PLATFORM COMPONENT ENGINEERING
viewpoint

SOLUTION ENGINEERING viewpoint

CROSSCUTTING ASPECTS ENGINEERING
viewpoint

CORPORATE viewpoint

RISK MANAGEMENT viewpoint

SOFTWARE FACTORY viewpoint

STANDARDS viewpoint

And all viewpoints from ZF
(model-types can be in many viewpoints)
Models from
solutions, platform
components and
platforms populate
the cells in ZF

• Stakeholders, their roles and their concerns
SCRA: VALUE view:
stakeholders’ concerns analysis

SCRA: SYSTEM-SOLUTION view:
City capabilities

SCRA: SYSTEM-SOLUTION view:
Platforms nomenclature

Reference capabilities vs platforms
Citizen

SCRAM: SOLUTION viewpoint:
Linking solution, solution artefacts, platforms
Tools,
APIs,
Patterns
Templates
Instances
Reference application
architecture for solutions
Solution
artefacts
Forms
Information,
documents
Rules
Processes
Roles
Automation
Information,
KPIs, reports,
audit-trails
Events, data
IoT

• CITY VALUE view
• CITY BIG PICTURE view
• CITY SYSTEM-SOLUTION ENGINEERING view
• CITY.UNIVERSAL PLATFORM ENGINEERING view
• …
• CITY.TRANSPORT VALUE view
• CITY.TRANSPORT BIG PICTURE view
• CITY.TRANSPORT SYSTEM-SOLUTION ENGINEERING
view
• …
• CITY.WATER VALUE view
• CITY.WATER BIG PICTURE view
• CITY.WATER SYSTEM-SOLUTION ENGINEERING view© A. Samarin 2019 Digital Architecture Methodology for Systemic Digital Transformation 84
The SCRA applies the SCRAM many times
the whole city and each vertical

• CITY VALUE view
• CITY BIG PICTURE view
• CITY SYSTEM-SOLUTION ENGINEERING view
• CITY CROSSCUTTING ASPECTS ENGINEERING
• CITY CORPORATE view
• CITY RISK MANAGEMENT view
• CITY SOFTWARE FACTORY view
• CITY STANDARDS view
• CITY.ABC SOLUTION ENGINEERING view
• …
• CITY.UNIVERSAL PLATFORM ENGINEERING view
• CITY.UNIVERSAL.ZZZ PLATFORM COMPONENT ENGINEERING view
• CITY.UNIVERSAL.YYY PLATFORM COMPONENT ENGINEERING view
• …
• CITY. URBAN PLATFORM ENGINEERING view
• CITY. URBAN PLATFORM ZZ COMPONENT ENGINEERING view
• CITY. URBAN PLATFORM YY COMPONENT ENGINEERING view
• …
• CITY.WATER VALUE view
• CITY.WATER BIG PICTURE view
• CITY.WATER SYSTEM-SOLUTION ENGINEERING view
• CITY.WATER PLATFORM ENGINEERING view
• CITY.WATER.Z1 PLATFORM SOLUTION ENGINEERING view
• …
SCRA:
Structure (fragment)

• An initial set of types
– event centric
– data-entry centric
– document/content centric
– data and/or information flow centric
– data and/or information visualisation
– IoT-device centric
– mobile centric
– short-running operations (activities-based)
– long-running operations (processes-based)
– any combination
• Each type has its own reference architecture, typical
solution artefacts, tools and techniques
Platform-enabled agile solutions:
typology of solution architectures

Platform-enabled agile solutions:
Solution and its microservices
Synchronous
Asynchronous
Check
History
Review
Loan
Check
Client
Approve
Loan
Prepare
Contract
Reject
Loan
Domain
rules
Census
Unit-of-functionality
Service
Platform
Monolith
Assembly
Link
BPM-suite tool
Finance
Microservice
Decisions tool

1
2
3
4
Security-by-design

The SCRA is a template for Solution
Architectures
Smart Cities Reference Architecture (SCRA) Tailored city Solution Architecture for a particular Smart City
Smart Cities
Implementation
Manual (SCIM)
Smart Cities Reference Architecture Methodology (SCRAM) to enable this

From a problem to the solution
?
Problem
?
?
?
?
?
?
?
?
?
Architectural and technological governance
Architecture & design
Coherent
ecosystem
!
!
!
!
!
!
!
!
!
Common platform
!
Solution
Already
available
Already
available

• Many reference architectures are developed by
ISO, IEC, JTC1, IEEE under different methodologies
What’s about standards?
Active Assisted
Living for people
with disabilities
and the elderly
IoT
Smart Manufacturing
Smart
HomeAAL
Smart Cities
Smart
Energy
Digital Healthcare
BigData & AI…Blockchain
Smart
Building

Common RA stack
implementation
(e.g. IoT RA for Big
Data, IoT RA for SC)
(e.g. IoT RA
“Implemented
systems” as
solution-
architecture and
implementation)
(e.g. IoT RA, SC RA,
Big Data RA, etc.)
42010
mRA generic-RA
is specialisation of
solution-architecture
(no viewpoints, no model-kinds, no views, no models)
(some viewpoints, some model-kinds, some views, some models)
DS-RA
solution-RA
is concretisation of
is concretisation of
DS-RADS-RA
solution-RAsolution-RA solution-architecture
solution-architecture
implementationimplementation
generic-RAgeneric-RA
(e.g. JTC1, EU,
a country, etc.)
(no viewpoints, no model-kinds, no views, no models)
mRA – Meta RA
DS-RA – Domain Specific RA

Patterns “Levels of architecting”
Common
Reference
Architecture
Stack Implementation A2
Solution
architecture B
Solution
architecture A
Implementation A1
build and test
refine
design and engineer
refine
refine
design and engineer
Problem space Solution space
City A specific needs
- stakeholders
- quality
City B specific needs
- stakeholders
- quality
Reference
Implementation
build and test
refine

• Other initiatives (see www.samarin.biz)
– FinTeсh
– InvestTech
– HealthTech
– EduTech
– UrbaTech
– ….
Smart City is only a integral part of the
bigger picture

• Mission statement: see below
• Vision statement: BRAVE NEW WORLD for HUMANS, ASAP
Mission statement and vision statement

• Geographical scope is recursive
– the whole planet
– continent
– regional group of countries (APEC)
– country
– industry
– enterprise
– territory
– city (as generalisation of town, village, megapolis, etc.)
– building
– home
Problem space (1)
• Activity scope
– economy
– education
– culture
– healthcare
– social

• Citizens
– Significant improvement in living standards and solving issues
which are important for citizens.
• Society
– The rapid and effective creation of a wide range of goods and
services.
• Business
– Ease of doing business (EoDB), creating new sectors of the
economy and entering new markets. Extensive business
involvement and creating conditions for innovations.
• Government
– Systematic and manageable implementation of a complex
transformation of a region. Increasing predictability and reducing
risks associated with a complex transformation.
Beneficiaries and their concerns

• Scalability (geography and activity)
• Common elements must be done once, with good quality
and being repeatable
• Each country or city should be able to carry out its DT at
its own pace (step-by-step)
• Use existing knowledge as much as possible
Solution space constraints

• There is a good example – Development Bank
• Usual services
– knowledge (about sectors and countries)
– experts
– sources of available finance
– coherent ecosystem of partners
– mechanisms for organizing projects
• Let us add services which are specific for digital
– a library of digital repeatable solutions
– bank of ideas for the continuous improvement
– coordination and complementation at scale
Organisation of an DT body (1)

• Central office vs regional offices (vs country offices)
Organisation of an DT body (2)

• Mission statement: Help clients to internalize successful
DT
– Knowing that DT is a new life style, the RC4DT is responsible to
help clients to materialize life style into their corporate culture
• Vision statement: 80% of clients internalise successful
DT in 2-3 years
• Reminder: RC4DT is using, extending and improving the
DT4DT
• The historical analogue of the RC4DT are “Machine-Tractor
Stations” (MTS)at the USSR at 1930 years
Regional Centre for DT (1)

• Essential characteristics
– be able to use and adapt the common methodology and
governance
– be able to architect digital repeatable system for various clients
– be able to conduct development of functioning (but not necessarily
final) digital replicating system
– Operational autonomy of the RC4DT
Regional Centre for DT (2)

The DT coordination group is supported
by the RC4DT

Governance stack

• The RC4DT supports the DT Coordination Group. The
latter is formed from the RC4DT expert team and the local
team; gradually, the first teaches the second.
The RC4DT and the DT coordination
group

Various life-cycles during the DT

• One of the essential parts of the DT4DT are DT initiates
(popular reference solutions for some domains)
• Currently, there are several types of initiatives that differ
in their level of uniqueness:
– applied (more unique)
– sectoral
– universal
– system (more general)
• There are natural dependencies between initiatives - so
more unique ones depend on more general ones.
DT Initiatives (1)

• Each initiative has its own maturity level from 0 (less
complete) to 5 (more complete), as shown below.
– 0 - idea
– 1 - outline
– 2 - reference architecture
– 3 - reference implementation
– 4 - two real implementations
– 5 - optimization on the experience of real implementations
• Less completed initiatives are opportunities for
investing in the DT4DT
• https://docs.google.com/document/d/1T9XoosLWVITMn3VvGlN4V-sVsoWC5aERVKjQF4ffv1Q/edit#heading=h.qt8c1dil0w5q
DT Initiatives (2)

DT Roadmap
https://docs.google.com/document/d/1Dm_3RZfquOxPIhln9rqtVKkgCdKeJfl7G65yh86_xtw/edit#§

• The Digital Transformation maturity matrix is an
assessment of the speed on the DT roadmap.
• Higher level - higher speed. Adding one level increases
the speed in 2-3 times. Cost is reducing. Quality is
increasing.
• If the speed at maturity level=1 is 1 then the speed at
maturity level=4 is approx. 16. (2.5**3)
• Why the speed of DT is very important?
Because in the digital world the winner takes all.
• The RC4DT provides maturity level=4.
DT Maturity matrix
https://docs.google.com/document/d/1R8RRy2pOvopszFl_8XOshR1ckLowp613okM8rQIy09I/edit#

• EA is able to
– solve very complex problems at the scale of SDG
– establish a common and efficient set of its tools
– organise concurrent work, coordination, complementarity and reuse
(i.e. achieve repeatability)
– produce digital models, make machine-executable enterprises
– define DT, drive DT and adjust DT as necessary
• EA is a versatile tool, good investment, strong
multiplier of investments and a basis for Digital
Architecture Methodology
• EA maps systems into sets of artefacts and models
and tell you what is missing
• Welcome to the wonderful digital world!
Conclusion

Is EA useful for Digital Transformation?

• E-mail: alexandre.samarine@gmail.com
• Mobile: +41 76 573 40 61
Questions?

• Elimination of many existing natural and artificial barriers
– No distance, as the movement of digital objects does not require
aircraft, trucks, wagons and barges.
– The speed of light services that will be available at all times,
everywhere and for everyone.
– No language barriers, because automatic translation will also
translate cultural and social differences.
– Machine-executable laws, rules and contracts that will allow digital
contracts to be concluded quickly, reliably, legally and, practically,
with anyone. Cm. https://egov-tm.blogspot.com/2017/08/blog-
post_5.html
– State barriers?
Forecast: drivers (1)

• Better security and privacy
– Full traceability of information flows without disrupting personal
"space."
– Digital archives with fully reliable information (thanks to
blockchain technology).
– Providing information security will become an architectural
activity.
– The architecture of digital repeatable systems will become an
applied science.

• World economy productivity
– Programmable businesses that are digitally configured.
– Idempotency of digital objects (i.e. technically, the digital product
is easily replicated, 1 = 1 + 1), which will lead to the industrial
creation of unique digital solutions from a set of standard and
specific digital components.
– The world will become
• Cheaper
• Faster
• Better
• More legal
• More integrated
• More innovative

• Electronic document management
• Man will be the sole master of his information
• It will be known where the ears grow at fake news
• The transfer of property rights will be simplified
• Agriculture
• Industry
• Competitors for services and jobs from all over the world
• Health
• Caring for the elderly
Forecast: changes (1)

• Legislation
• Public administration
• Increased citizen participation in the country
• Finance
• Transition from Digital Economy to Digital Country
• A significant part of the current IT will be an accurate
activity
• Platforms will lose their charm
•

• A lot of humans needs will be removed from
economy

• Change: How you do it is more important than what you do
• Systemically
– coherent viewpoints, views, descriptive and executable models
• Value-driven
– understand flows of value, their performance and potentials
• Via Human Enterprise Learning Leadership (HELL)
– everyone is an important stakeholder who must learn and act
• Trustworthiness by design
– privacy by design
• With coordination, complementation and copying
– to address next uber-complex challenges with limited resources
How to transform your system to a
digital repeatable system

• https://egov-tm.blogspot.com/2018/12/blog-post.html
Example: 100 India Smart Cities

• Digital space is a collection of interacting digital systems
that interact with them with other actors that provide
their systems and infrastructure
• Digital environment <of a digital system> is many
systems that are not part of this digital system, but with
which this digital system can interact
• Digital ecosystem is an ecosystem made up of digital
systems
• Digital security is the security of a digital system
More related concepts (1)

• Digital industry is an industry built as an ecosystem of
digital enterprises and systems
• Digital infrastructure <of a digital system> is a
infrastructure of the digital system
• Digital platform is a coherent set of digital services for a
particular purpose
• Digital sector of the economy is the production of
technical and software products and services in a digital
representation
– Examples: software, digital content.
More related concepts (2)

• Never ever argue about a concept in isolation
– always consider context
– employ your concept system
REMEMBER

• E-mail: alexandre.samarine@gmail.com
• Mobile: +41 76 573 40 61
Questions?

Digital Architecture Methodology for Systemic Digital Transformation (Smart Cities are an example)

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Digital Architecture Methodology for Systemic Digital Transformation (Smart Cities are an example)

Similar to Digital Architecture Methodology for Systemic Digital Transformation (Smart Cities are an example) (20)

More from Alexander SAMARIN

More from Alexander SAMARIN (20)

Recently uploaded

Recently uploaded (20)

Digital Architecture Methodology for Systemic Digital Transformation (Smart Cities are an example)

Editor's Notes