Product – AIM web

An web-based platform providing an agile-architecture approach to delivering IT project portfolios  

Overview

Upload OpenExchange (.xml) and Archi (.archimate) models to have a more open and transparent way to develop Enterprise, Program, and Project Architectures.

Manage your Architecture portfolio at scale

Create stories based on your Architecture models to explain architectures to your team and Enterprise

Use Architecture prefab components to speed up and standardise Architecture development

Share Architecture models with your assurance teams (regulatory, legal, cybersecurity, architecture governance) to reduce the time and cost of assurance and governance.

Installing

AIM web is a progressive web app. Go to https://aim-01.web.app to sign up. This product is in beta, and has a free trial period and then a minimal fee to support cloud hosting costs.

Screenshots

An easy to use platform to support the Plan/Design Architecture phase

The AIM web app provides an easy to use way to manage the Plan/Design phase for Architecture content.

AIM can store Project Architecture models, as well as Component models.

Component models, or ‘prefabs’ are those reusable IT building blocks that help speed up IT project delivery.

This ability to manage and share Architecture models is fundamental to better collaboration across the Enterprise.

AIM is not an Architecture design tool. You can upload any Archi (.archimate) or Open Exchange (.xml) model file to AIM.  

Create model-based stories to explain your Architecture at scale

Once a model file has been imported into AIM web, project team members with different expertise on differt aspects of the solution can create their own animated stories to explain an aspect of the Architecture.

This means that multiple domain experts can each equally contribute into the overall project Architecture.

  • Billing SMEs might create a story to explain how billing/invoicing works
  • Infrastructure SMEs might create a story  to explain what integration services are being used for the project
  • The Lead Architect might create a story to explain Key Decisions for the Project
  • A Security Architect might create a story to explain security controls for a project, in preparation for CyberSecurity/InfoSec assurance.

Outside of Project uses for Stories, there are also important Stories to develop at the Enterprise level:

  • An Enterprise Architect might create a story to explain the Enterprise value chain and Strategic IT goals

Without the ability for multiple team members to create stories, your project teams must use a less agile and open approach that typically involves 1 author updating a document that is difficult to find, access, and contribute into.

Works on your phone

AIM web is a mobile-first progressive web app, so looks good on your phone, tablet, or larger display. This lets you can carry the Enterprise around in your pocket, and have the information you need at any time to support faster and higher quality IT project delivery.

Create better scope, time, and cost estimates

Architects often do a great job of defining a target state but can often leave details out when explaining how the target architecture is going to be delivered.

AIM web can extract the work packages and deliverables from your model into a hierarchical view to make it easy to see how the project team are planning to deliver.

The WBS typically represents the direct costs, and then need to be combined with indirect costs in collaboration with a project manager.

Conduct better Architecture Assurance across the Project Portfolio

In any IT delivery program, it is desirable to have an efficient way to assure and support development of Architecture content.

Some typical assurance questions are:

  • How is the architecture development progressing?
  • Are all of the expected views being created?
  • Does the Architecture help achieve Strategic IT Goals?

By adopting some standard views in your Enterprise, your EAs can use AIM to easily review project architectures and therefore support more projects.

This results in governance outcomes being better achieved through earlier and more continuous assurance, versus when the project is brought through Governance (which is often too late).  

Improved understanding of Architecture models

In order for stakeholders to critique a model they must first understand it.

AIM web makes it easy to navigate through a model to understand views, and how various elements are used. This lets you understand the overall model better, and see all of the ways that an element is used across multiple views.

In this example below we can see a JSON over HTTP element is used in 2 views, as shown by the teal highlighting in the thumbnail views. The thumbnails can then be selected to open that view.

The full ArchiMate set of symbols

All of your models faithfully rendered using sharp SVG symbols.

Product – AIM modeller

A game-engine based Windows desktop tool to create and validate rich Enterprise Operating Model designs

Overview

Create business operating model simulations to build clarity and consensus on large scale information lifecycles across your Enterprise.

Create animates stories to explain how the operating model works

Build working business scenario simulations that process real data through the operating model to validate the high level design of data payloads, and how information is stored and retrieved.

Overlay project portfolios to plan IT strategic investment    

Installing

AIM modeller is a windows executable. See Downloads

A new version of this will be released early in 2022 with Node based tech demo.

Contact support@architectureinmotion.com.au  in the meantime.

Screenshots

Create Operating Model designs to clarify who does what

In the development of Enterprise, Program and Project Architectures, it can often be challenging to in the first instance clarify responsibilities between parties, whether those parties are your internal business units, partners, suppliers, or customers.

Given that usually the overwhelming majority of business outcomes are tied to the streamlined flow of information, it is important to explicitly define what information exchanges and lifecycle management is required at a high level, before attempting to define how that design will be realized.

The first step in Operating Model design is defining the business functions (cubes), domains (green squares), and information exchanges (connectors between cubes) to occur, as well as stores of information (cylinders)

Communicate your Operating Model through animated stories

Once your basic operating model is created, you can then create animated stories to show how information is created, consumed, and exchanged for a given business scenario. This is typically best done at a high level rather than detailed business process level.

Color-coded business domains

As part of being able to communicate your operating model to others, you can use color-coding to indicate different business domains, for example, Ordering, Shipping, Finance, Sales.

Simulate real information flows

While it is useful to have a declarative version of your Operating Model, it is additionally useful to validate the model by simulating the flow of real data through it,

AIM modeller allows you to use scripting to process real data through the operating model design, in order to establish how information payloads need to be structured. For example, when we say an ‘Order’ is submitted, what are the main elements of it’s payload, and have we verified that it contains the main information building blocks that the receiver expects?

Visual model filtering

As part of building better understanding of your Enterprise’s Operating Model, you can create shaders to colour-code and filter out sections of the model based on model attributes 

Heatmapping

You can also easily heatmap your model based on adding numeric model attributes, which might represent current IT OPEX cost, risk, strategic priority, project investment and so on. AIM modeller can then use an initial colour range that you provide to heatmap your model