Schaeffler is a globally acting component supplier for the mechanical engineering and automotive industry employing around 89,000 people. Facing the challenges and opportunities of digitization and transition from combustion engines to fuel-cell and electric vehicles, the business processes and underpinning application landscape and technology use are in an ongoing transition; generating a strong need for Enterprise Architecture. In this blog we outline the nature of EA at Schaeffler and tool support by BiZZdesign’s solution, focusing on architecture modeling quality. Read more
ArchiMate provides a powerful language to visually describe the architecture of an enterprise at different layers – from strategy to implementation. Read more
In previous blogs, we have written about the combination of structure and data to create novel insights into your enterprise, and about how this can support creating a Digital Twin of your organization. To reiterate, a digital twin is a digital representation of a real-world entity or system.
Today, organizations need to move at speed and adapt their business to a volatile environment, while at the same time dealing with many inside and outside stakeholders and influences, ranging from customers and partners in the ecosystem to regulators, competitors, and the uncertain effects of politics (viz. Brexit or the US-China trade war). To be an adaptive enterprise, business architecture is an indispensable discipline. Without an architectural approach to your business, you will quickly get mired in the myriad changes and effects, without a clear path forward.
Much of what we do in the world of enterprise architecture and business process management is based on pre-defined analysis and design techniques, like a game that has a well-defined set of rules and operates within a bounded, predictable universe. You know what the aim of the game is (check-mate your opponent, or reduce the cost of your application landscape, for example) and follow the rules to get the optimal outcome.
In the past I’ve written several blog posts on enterprise architecture in an agile world, most recently together with my colleague Fabian on our tool support for Agile and DevOps, and a bit longer ago on the use of ArchiMate in an agile context. In this blog post, I want to revisit the latter subject and add some newer insights and ideas with SAFe®.
One of the more interesting developments in the tech space taking place right now is the emergence of digital twin technology. For those of you asking What is a digital twin? right now, allow us to elaborate.
In previous blog posts, we have written about various analysis techniques that help you get more value from your models, as well as dashboarding techniques to visualize data in all kinds of ways. These two topics point to a more general theme: the new possibilities you get from enriching your models with various types of external data. We call this Business Intelligence 2.0.
In the two previous installments, we discussed planning and roadmapping in the context of enterprise architecture, and how you can use the concepts of the ArchiMate language to model your roadmaps. We showed how you can model the evolution of your enterprise at coarse-grained level, using concepts such as ArchiMate’s ‘plateau’. In this installment, we will discuss more fine-grained modeling of change in Enterprise Studio. Specifically, we will show you how you can model the lifecycles of individual elements of your architecture. Moreover, our platform supports analysis based on life cycles and the dependencies between elements, for instance, to find conflicts in your transition plans.
A key driver for management in general and enterprise architecture in particular is to get a better grip on the future, on the evolution of your enterprise. A common technique to support this is roadmapping. A roadmap is a strategic plan that shows the main steps or milestones needed to achieve a desired outcome. It articulates the strategic direction of your enterprise and shows the path forward. It helps you identify what is needed and what the main dependencies and priorities are, and serves as a communication instrument to align the organization along a common course of action.
In a previous blog post on the features of our collaboration platform, we have explained how you can support people in working together on architectures and other models via structured workflows. In that post, we looked ahead at future features to support this kind of collaboration. Time to update you on the latest developments!
– Marc Lankhorst, Fabian Aulkemeier
In my recent blog post on stakeholder communication, I described various basic forms of communication about architecture, with diagrams, tables, heatmaps and the like. What I did not touch upon in that post is how you can enrich your architecture (and other) models with additional data and display the results in various dashboards. That is the topic of this post.
Enterprise architecture is often perceived as an abstract, conceptual, and somewhat esoteric discipline practiced by ‘high priests’ who provide guidance with their lofty ‘architecture principles.’ It’s true that architects are often concerned with overarching, cross-cutting concerns that are not always visible to the people ‘in the trenches,’ but this view of enterprise architecture is misguided at best and increasingly misses the mark.
In today’s business landscape, effective transformation is critical for enterprises to stay competitive. By definition, transformation happens over time.
Enterprises (or some subsection thereof) have a current state which needs to change for the better. That change – however small or large – results in a different future state. With the widespread adoption of Agile working practices and DevOps-based continuous delivery, these changes can be very small and very frequent.
-Nick Reed and Bart Molenkamp
Marc Lankhorst, Fabian Aulkemeier
Enterprise architecture, agile software development, and DevOps are sometimes seen as being at odds. We think they can fruitfully collaborate and interface, but how do you do that? How can you align the concepts and processes from these worlds and bridge the cultural gap?
Previously, I have blogged about stakeholder management and showed you some useful techniques to support this important part of enterprise architecture. In this blog post, I want to address different ways to share architecture information with different types of stakeholders involved in changing your enterprise.
Large architectures of big organizations can become quite large and complicated, posing a challenge for the architects developing and maintaining them. In previous discussions, we have addressed a number of techniques for organizing and controlling such large models to keep things manageable. In this installment, we look at the processes and practices you can use to optimize the collaboration between the people working on these architectures.
In the first blog of this series, I explained how important it is to raise your digital change capability to become an adaptive enterprise. I also highlighted the role of effective communication, as well as approaches to categorize and visualize enterprise architecture descriptions based on the TOGAF and ArchiMate standards. In this series, I also included guidance on which approach to select for modeling Architecture and Solution Building Blocks (both are types of logical or physical components). To round out this series, I will end by discussing the connection to Deployed Solutions.