1. Business & Enterprise Architecture
Emerging Trends
Business & Enterprise Architecture
May 2, 2017
Prepared for itSMF Ottawa PDD - May 2, 2017
Architecting the future closereach.ca

2. Business and Enterprise Architecture
Architecture as-is baseline
Architecture to-be?
EA examples
Where are you on the architecture continuum?
Architecting the future.

3. Enterprise Architecture
… many views and opinions - business
In Europe when you are talking about Enterprise Architecture you are talking to the business – they are the drivers behind EA
… IM/IT is the business enabler
IM/IT architectures are all about structuring thins so that the business meets its objectives
Architecting the future.

4. Architecture baseline
… many views and opinions – IM/IT
Notation?
BPMN – Business Process Modeling Notation
UML – Unified Modeling Language
IDEF, IEF
Architecture Description Language
Framework?
Zachman
TOGAF – The Open Group Architecture Framework, Archimate
Service Oriented Architecture – GSRM,…
FEA - Federal Enterprise Architecture
... MANY more
In North America, 90 percent of the time if you are talking about EA you are talking with IM/IT – the technology guys
Many with an IM/IT background would equate architecture with how you model – the notation
Others view architecture from a framework or method perspective
They are looking at things from the particular point of view that is relevant to them
... Again not necessarily wrong but is that particular view too limiting? Does it prevent us from realizing the full benefit of taking an architectural approach
Architecting the future.

5. Architecture baseline
… architecture describes what we do and how we do it
AND the relationship between these things
Best description or maybe just the simplest for most people – Architecture describes what we do and how we do it
… but is also is the relationships between all of these things
Understanding those connections, the relationships between architecture components is the key to realizing it’s true value as a business and transformation tool. Equally important is also understanding that those pieces or architecture and the relationships between them are not static they are ALWAYS CHANGING – sometimes by things that we do , sometimes by influences outside of our control.
Architecting the future.

6. Architecture baseline
… architecture describes what we do and how we do it
AND the relationship between these things
Caveat: Take architecture only to the level necessary to meet the needs of the business
Best description or maybe just the simplest for most people – Architecture describes what we do and how we do it
… but is also is the relationships between all of these things
Understanding those connections, the relationships between architecture components is the key to realizing it’s true value. Equally important is also understanding that those pieces or architecture and the relationships between them are not static they are ALWAYS CHANGING – sometimes by things that we do , sometimes by influences outside of our control.
Architecting the future.

7. Architecture as-is Looks inside Architecting the future.
Core processes break down to sub processes…
For most people and organizations, architecture is processes or systems or data…. And it inward looking – describing what is within our organizations –
…and are visualized by workflow diagrams
Architecting the future.

8. Architecture as-is Silos of information Business planning
Policy, programs, etc.
Business processes
IM/IT processes
System/components
Data
Networks & infrastructure
Architecture information is in lots of different places in lots of different forms.
Relatively static – more documentation than anything else… and everyone knows what happens to documentation/training – last thing to get done, first thing to get cut
More data at our disposal, incremental technology improvements
Some consolidation of data – datamarts, data warehouses
Some consolidation/integration of applications
Some have adopted better tools but if you ask most people where their architecture content is – its in Word, Excel, PowerPoint, on a shared drive, in someone’s head.
BUT… We are essentially doing things the way that we have been for years.
…. And frankly its not working – projects/initiatives, systems continue to fail with much the same frequency as they have always done
ITS TIME TO UP THE GAME – because things are changing
Architecting the future.

9. Why will architecture change?
Always on
Faster
Wherever
Whenever
Whatever
Highly integrated, ecosystems
Personal user experiences CHANGE business user expectations
Architecture will have to change to remain relevant
Architecting the future.

10. Why will architecture change?
Always on
ERPs
Solutions based on best practices
Integrating systems
Consolidating/sharing data
Changing delivery paradigm: Cloud
Machine learning – real time analysis & decision making: Governance
ERPs deal with the whatever, wherever, whenever for large businesses
ERP vendors are mapping their solutions against APQC’s knowledge base.
APQC is the American Productivity and Quality Center. It is the world’s foremost authority in benchmarking, best practices, process and performance improvement, and knowledge management. Their core expertise is Business Excellence, Financial Management, Human Capital Management, Knowledge Management, and Supply Chain Management
These are all things that are challenging the traditional view of architecture
Architecting the future.

11. How is EA changing? Where EA lives EA’s perspective
Business Management System (ERP integration)
Focus on metrics and analysis
Business planning, transformation and collaboration
Architecting the future.

12. Outside - Inside view Business Ecosystem Architecting the future.
How we view architecture has to change to accommodate this dual view
… we have the inside inward looking views down pretty well (still siloed)
… where we are struggling and the coming challenge is with the outside view and how we integrate it all
Outside of our organization there are things (people, organizations, legislation/policy, technology) that have a massive impact on what we do inside but that we have very little or no control over.
If we are only looking inside we get blindsided and can’t plan and be ready to respond or be ready to react to these outside influences
… if our architecture ends at our organization’s doors without that outward looking view we are in trouble
Architecting the future.

13. Outside - Inside view Business Modeling & Transformation
Architecting the future.

14. Outside - Inside view Customer Journey Map Architecting the future.
Customer journey map is a decomposition of the business ecosystem
Looks at things from a very personal interactive level – from the outside view
Architecting the future.

15. Outside - Inside view Business Outcomes and Metrics
Taking data from external sources and relating it to an organizations strategy, plans and performance.
Architecting the future.

16. Business/Operating Management System
EA lives at the core
EA takes on an operational role
Integrates a wide variety of information (or makes it easy to find/shows relations)
Metrics and analysis
EA informs business planning and organizational transformation
Architecting the future.

17. Business Management System
Architecting the future.

18. Business Management System
Situational Awareness – architecture and real-time performance metrics drive current business decisions and future plans
Architecting the future.

19. Business Management System
Architecting the future.

20. Business Management System
Architecting the future.

21. Business Management System
Architecture drives workflow drives metrics/feedback
Architecting the future.

22. Business Management System
Architecture drives workflow drives metrics/feedback
Architecting the future.

23. Business planning, transformation & collaboration
Architecting the future.

24. Getting from A to B Baby steps work
Senior Management buy-in – you need a sponsor
Choose the right project
Don’t reinvent the wheel
Get started
Collaborate
Don’t get into Framework wars!
Architecting the future.

25. Architecting the future.

26. Thanks. Questions?
Architecting the future.