Architect

Process architecture is developed in several steps. First step is to develop an overview; identify all processes, triggers, products and customers (could be internal as well as external). The process architecture is key to understand and manage the business development. Even though it is quite granular in the beginning, it will be the common structure for all detailed design that comes later.

A quality information architecture is a central part of our data oriented architecture. From the information architecture we identify database building blocks. We develop an overall business information model (OBIM), and for each part of the OBIM we develop a detailed information model (DBIM). This is an efficient structure to keep control of both the large picture while each part can be detailed. An effective step by step process combined with strict modeling rules, we control granularity and quality.

Existing business applications are an important part of existing, or AS-IS, architecture. An they are an important part of designing the enterprise. When we are designing and constructing the new enterprise, we do that on a “living organism”. Even though we do changes, the business must roll on. So in addition to applications we have projects. Both of them must have their defined places within the enterprise architecture.

We map information against business process; where is it captured and where is it used. We pick processes to be authorised sources for information. Normally there will be a huge potential for information reuse in all enterprises.

There are dependencies between data that you cannot neglect. It is of high importance when you scope development projects, buy applications or when you clean your application portfolio. If you don’t take these into account you will run into trouble with project overrun, unnecessary complexity etc. These dependencies are very stable and relatively easy to find. In an even modest information architecture there are over 100 such dependencies, which is more than humans can control without proper documentation.

Data must be acquired only once and after that reused. Applications will reuse more data than they will have authority to acquire. When you develop one application it is important that data that the application shall reuse already exist. You will have to plan for this to happen. We make a data-ready sequence for development. It is of high importance when you plan for your digital platform.

Projects realise new value propositions for the enterprise. At the same time each project represent a step in developing the future digital platform for the enterprise. In addition, there will be liquidation of applications. Therefore each project must be defined and scoped from the architecture (current and future). The sequence and dependencies between projects are important. When the engineering sequence differ form business prioritsation we must mitigate cleverly.

It is easy to add new applications. But if you have redundancy, complexity and too many applications running, you need to set up a plan for liquidation of applications. That is a challenge in most cases. What happens when an application is removed? You will never reduce complexity, risk and cost without liquidation. But you need to control it. You do that with your architecture models and project definitions. The liquidation plan is an important component for reaching an effective future digital platform.

Data quality is a must in the information society. Data-driven business, AI and digital transformation – you can forget it if it is not based on quality data. Our philosophy is to produce quality data from the source – and keep the quality in the whole life cycle. You have to manage data in the same way as you mange your other resources like personell and finances.

Where are you in terms of digital readiness, are your enterprise prepared for digital transformation. Very few enterprises are today. In the coming decade we will see many businesses be redefined. To be part of that you have to be ready. Well, it takes time to prepare. You need to monitor your progress in preparation.

As an architect you have to play together with leaders, business experts, developers and the whole organisation. The enterprise is constantly evolving. You need a common dashboard to tell the status and progress. In this way you make the architecture work visible. And it helps you to get a grip on the important stuff.