How to Use the Essential Launchpad

These are the sites within your organisation and will be for any location-based views and maps Examples: London HQ, New York, Osaka Distribution Centre

The business domains your organisation has. Examples: Finance, Sales

The capabilities the organisation has. This is a key foundation for your enterprise architecture. See the business capability tutorial here for more information. Note you need a single root capability – create a root capability and then make sure you replicate the name in the root capability column. You then associate your level 1 capabilities with the root name as the parent capability Examples: Fund Management, Trade Management

These are the logical business processes. There is no inference as to when they are performed or by which organisation. Examples: manage customer payments, create invoices.

These are used to group business processes, activities or tasks that are variants of each other into a single ‘family’, allowing them to be distinct while at the same time conveying that they are related. Examples: Invoice Processing

The organisations within your enterprise. Where different locations have the same organisational names, e.g. Marketing in London and in Paris, then differentiate them by adding something like Marketing (London), Marketing (Paris). Examples: Marketing, Operations, IT (Milan), IT (Manchester)

Here you map your organisations to the sites you created earlier

Another key foundation for your Enterprise Architecture, the application capabilities you need to support your business. Examples: Accounting Management, Trade Management

Define what services are needed to support each capability. Examples: Resource Management Capability mappped to: Time and Absence Management, Compensation Management, Payroll Management

This is the types of information that are sent between applications Examples: Client Data, Trades, etc.

This is where you build your links between apps and show what data is flowing between them using the data from the Information Exchanged sheet.

Define the users of applications.

The servers in the organisation. Note this can be AWS or Azure, etc. too.

Mapping the applications to the technology nodes.

Mapping processes to the application services which can support them.

Mapping the physical processes to the applications (via application services which do support them).

Mapping the physical processes to the applications (via application services which do support them).

The technology capabilities you require. Note, as this is a fairly standard layer, we provide a pre-populated set of technologies, you should add to, amend or delete these. Again, this is one of the key elements of the Enterprise Architecture for identifying EA opportunities. Examples: Messaging Services, Event Management Services

The technology capabilities you require. Note, as this is a fairly standard layer, we provide a pre-populated set of technologies, you should add to, amend or delete these. Again, this is one of the key elements of the Enterprise Architecture for identifying EA opportunities. Examples: Messaging Services, Event Management Services

A list of technology suppliers – add to, amend or delete these as required Examples: Microsoft, IBM

Capture your products here. We provide a sample set, delete these out if you don’t use/want them. Examples: Apache Tomcat 9

This provides a way of grouping technologies into families, e.g. Oracle Databases Examples: Oracle Products

Associates technologies with those parts of the organisation that use them.

Enables you to map the technologies that applications use. This page is key for the Application Strategic Technology Alignment view and the Technology Build in the Application Summary

Capture your data subjects Examples: Party, Claim, Employee

Capture your Data Objects Examples: Sales Order, Purchase Order

Capture your Data Objects Examples: Sales Order, Purchase Order