Documentation
Describe your organisation’s business capabilities, processes and applications, then connect planned changes to architecture decisions with ArchiLU.
Enterprise architecture
What is enterprise architecture?
How strategy, capabilities, processes and systems connect. The differences between enterprise architecture, Business Architecture and application portfolio management, explained through a business request.
Read the introductionYour architecture questions
Choose the question you need to answer to find the information involved and each team’s work in ArchiLU.
How do strategic priorities lead to specific changes?
Objectives, affected capabilities and investment decisions.
How do you describe business capabilities and processes?
Value streams, activities, responsibilities and supporting applications.
Which applications and data depend on each other?
A shared repository for tracing relationships and assessing the impact of change.
How do you assess a request before starting a project?
Business need, affected architecture, assessment and recorded decisions.
Which applications should you retain, change or retire?
Business use, costs, risks and application portfolio decisions.
How do you find the reasons behind an architecture decision?
The assessment reviewed, decision owner, conditions and history.
Explore a business need
Leadership and industries
Applications and repository
- Application Architecture Guide: Understanding and Mapping Application Architecture
- Application Portfolio Management and Rationalization: Where to Start
- Who keeps the architecture repository up to date?
- Application dependencies, end of support and renewals
- Move an Excel inventory into an architecture repository
- Connect your CMDB and existing tools to enterprise architecture
Requests and decisions
Processes, capabilities and costs
AI, risk and audit
- MCP for enterprise architecture and ADD preparation
- Governing AI agent access to architecture data
- The ICT Third-Party and Outsourcing Register: Keeping It Current from the Architecture
- Architecture Governance for DORA and NIS2: Decisions, Inventories and Dependencies
- IT Cost and Supplier Risk: Contracts, Applications and Critical Functions
- Prepare architecture documents and decisions for an IT audit
Understand and choose ArchiLU
All documentation
49 documents
IT Cost and Supplier Risk: Contracts, Applications and Critical Functions
Finance tracks contracts and their cost; the risk function tracks ICT providers. Both views concern the same applications. A shared repository connects these objects and shows the costs, end dates and dependencies to review.
Read the documentNIS2 and Enterprise Architecture: Documenting Systems, Dependencies and Suppliers
NIS2 requires risk-management measures, attention to the supply chain and notification of significant incidents. This work assumes that an entity knows its systems and their dependencies. The architecture repository holds that documentation; it is not a certificate of compliance.
Read the documentCSSF and Enterprise Architecture: Documenting ICT, Outsourcing and Resilience
Banks, PFS, investment firms and fund players document their ICT, outsourcing and operational resilience. These files rest on the same foundation: capabilities, applications, data flows and the third parties behind them. The architecture repository keeps that foundation current.
Read the documentThe ICT Third-Party and Outsourcing Register: Keeping It Current from the Architecture
An ICT third-party register is useful only if it stays accurate and can be queried. Kept in a spreadsheet, it drifts as soon as an application or a provider changes. In ArchiLU, the DORA register of information is produced from the chain of functions, applications, providers and contracts; the entity remains responsible for its completeness.
Read the documentArchiLU and Avolution ABACUS: Comparing Two Enterprise Architecture Tools
Avolution presents ABACUS as an architecture tool that automates assessments and builds roadmaps. ArchiLU links each architecture object to its owner and to the decisions that concern it.
Read the documentArchiLU and OrbusInfinity: Comparing Two Enterprise Architecture Tools
Orbus Software presents OrbusInfinity with a diagram editor in the browser, a Visio add-in, publication to SharePoint and Power BI dashboards. ArchiLU links architecture objects to their owners, to decisions and to the DORA chain.
Read the documentSAP LeanIX and Ardoq: Comparing Two Approaches to Enterprise Architecture
SAP LeanIX organises its offer around application portfolio management and additional modules. Ardoq describes a platform built on a graph and fed by integrations. The choice depends on the intended use, the people who contribute and the data to connect.
Read the documentAvolution ABACUS Alternatives: Selection Criteria
An alternative to ABACUS is chosen on use, contributors, hosting and the cost of migration. This guide sets out what Avolution highlights, the questions to ask before a change and the profile ArchiLU is designed for.
Read the documentOrbusInfinity Alternatives: Selection Criteria
According to its vendor, OrbusInfinity is a SaaS platform with a diagram editor in the browser, a Visio add-in, publication to SharePoint and Power BI dashboards. An alternative should be judged on your environment, data hosting, the people who contribute and the migration of your models.
Read the documentBizzdesign Alternatives: Selection Criteria
Bizzdesign now brings together the products of Bizzdesign, MEGA and Alfabet. An alternative should be judged on what your team actually uses, on hosting and on the migration of your models.
Read the documentMCP for enterprise architecture and ADD preparation
An assistant can follow dependencies in the architecture model and prepare an ADD. The useful checks concern its sources, its permissions and the treatment of the proposed changes.
Read the documentGoverning AI agent access to architecture data
An assistant may read a model, prepare an ADD or propose a change. Each operation needs a defined authority, an accountable person and an observable result.
Read the documentArchitecture context, source systems and data freshness
A CMDB, a contract register and an architecture model can describe the same application differently. Assign authority to each fact, reconcile the differences and keep the evidence behind the relationships.
Read the documentEnterprise Architecture for the PMO and Transformation Office
A transformation office follows several initiatives at once. Enterprise architecture places them on the capability map, makes their dependencies visible and keeps the decisions that changed the plan.
Read the documentArchiLU or SAP LeanIX: Criteria for Comparing
SAP LeanIX has been part of SAP since November 2023; ArchiLU is published in Luxembourg by MIP-IT SARL. Both maintain an architecture repository. The comparison rests on your uses, your contributors and your hosting constraints.
Read the documentArchiLU or Ardoq: Criteria for Comparing
Ardoq builds architecture on a graph with a configurable metamodel; ArchiLU starts from a predefined model that follows ArchiMate. The comparison rests on the team that will maintain the model, the decisions to record and the hosting you expect.
Read the documentArchiLU or MEGA HOPEX: Criteria for Comparing
HOPEX, developed by MEGA International, has been part of Bizzdesign since 2024 and is now called Bizzdesign Hopex. ArchiLU is published in Luxembourg. The comparison starts from the uses you hold in Hopex, GRC included.
Read the documentA Sovereign European Alternative for Enterprise Architecture: What to Check
Several enterprise architecture vendors have changed owners since 2023. For a European buyer, sovereignty is checked point by point: hosting location, operator, subprocessors, data exit and the use of AI.
Read the documentArchiLU or Bizzdesign: Criteria for Comparing
Bizzdesign, a Dutch vendor, brings together Horizzon, Hopex, Alfabet and Unify and reports more than 2,000 enterprise customers. ArchiLU is published in Luxembourg. The comparison concerns the product in the suite that meets your need.
Read the documentApplication Portfolio Management and Rationalization: Where to Start
Application portfolio management starts with an inventory kept by owners. Rationalization then decides, application by application, what to keep, evolve or retire.
Read the documentArchitecture Governance for DORA and NIS2: Decisions, Inventories and Dependencies
DORA and NIS2 require an entity to know its functions, its ICT assets and their dependencies, and to show who decides. Architecture governance produces this documentation. The competent authority and auditors then assess compliance.
Read the documentTOGAF Explained: The ADM, Domains and How to Use It
TOGAF is The Open Group’s enterprise architecture standard. Its method, the ADM, leads from vision to delivered change; a team keeps the phases that serve its decision.
Read the documentArchiMate Explained: Domains, Elements and Version 4
ArchiMate is the enterprise architecture notation published by The Open Group. Version 4, published on 27 April 2026, speaks of domains where version 3.2 spoke of layers.
Read the documentZachman Framework Explained: The 6x6 Classification Schema
John Zachman published his framework in 1987 in the IBM Systems Journal. Its grid classifies the descriptions of an enterprise; it does not say how to produce them.
Read the documentFEAF Explained: The US Federal Enterprise Architecture
FEAF version 2, dated 29 January 2013, gives US federal agencies a common vocabulary to describe and compare their investments.
Read the documentBIAN Explained: The Banking Industry Reference Model
BIAN provides reference descriptions for banking services. Using them starts with a comparison against your activities, applications and their owners.
Read the documentBusiness Capability Mapping: Levels, Applications and Value Streams
A capability map describes what the organisation is able to do. It supports decisions when each capability has its owner, its applications and its place in the value streams.
Read the documentEnterprise Architecture for Healthcare: A Practical Guide
A healthcare organisation runs electronic health records, laboratory, imaging, pharmacy, scheduling and billing side by side. Architecture describes these applications, their exchanges and their owners before any change.
Read the documentWhat is Data Architecture?
Data architecture describes the sources, storage, flows and rules of an organisation’s data. TOGAF covers it in Phase C; ArchiMate represents it with passive elements in several domains.
Read the documentApplication Architecture Guide: Understanding and Mapping Application Architecture
Application architecture describes an organisation’s applications, what they do, how they exchange and who is accountable for them. A useful map starts from the current state and names the owner of each application, interface and flow.
Read the documentTechnology Architecture Explained: Definition, Components and ArchiMate
Technology architecture describes what applications run on: compute, network, storage, middleware, security and observability. It sets standards and follows the lifecycle of technologies.
Read the documentChoosing an Enterprise Architecture Tool: Criteria, Free Options and What to Test
An architecture tool is chosen for the decisions it must support and the people who will keep it current. Three demonstration tests show who answers for the data, how a decision is made and what an AI assistant can do.
Read the documentBest Enterprise Architecture Tools: Comparison and Selection Criteria
No ranking holds for every organisation. Tools differ in their model, licensing basis, hosting and connection to the rest of the IT landscape; a trial on your data settles a shortlist.
Read the documentLeanIX Alternative: What Should a Small EA Team Check Before Switching?
Changing architecture tools means knowing what you keep: objects, relationships, owners, history and integrations. A small team then compares alternatives on those items and on the workload each one demands.
Read the documentArdoq Alternatives: How to Choose an Enterprise Architecture Platform
Ardoq organises architecture as a data graph with a configurable metamodel. An alternative is compared on modelling approach, contributors, decision governance and the effort of keeping data current.
Read the documentEnterprise Architecture for Banks: BIAN, DORA and Where to Start
A bank starts with its capabilities, its applications and their owners. BIAN serves as a reference for comparison; the DORA chain then connects critical or important functions to ICT third-party providers and contracts.
Read the documentEnterprise Architecture for Insurance: ACORD, DORA and Solvency II
An insurer describes its underwriting, policies and claims with their applications and owners. ACORD provides reference models; DORA and Solvency II require knowing the critical functions and their providers.
Read the documentEnterprise Architecture for the Public Sector: Frameworks, Interoperability and the Case of Luxembourg
A public body describes the services it delivers, the capabilities producing them and the applications shared between organisations. TOGAF, FEAF, Zachman and NORA provide reference points; in Luxembourg, the national interoperability framework sets its own.
Read the documentCapability mapping step by step
Ten steps to move from a list of capabilities to a map linked to applications, owners and transformation decisions.
Read the documentData Architecture vs Information Architecture: What’s the Difference?
Data architecture describes the structure, storage and movement of data between systems. Information architecture organises content, navigation and search for users.
Read the documentAPI Governance for Enterprise Architecture
An API nobody tracks changes without its consumers knowing. Governance starts with the catalogue: the owner, consumers, lifecycle and security rules of each API.
Read the documentCloud-Native Enterprise Architecture: Principles and Governance
Cloud native describes an automated, repeatable way to build and deploy workloads. Enterprise architecture sets the platform standards and tracks what each application uses.
Read the documentArchitecture Review Board: Submission and Decision
In ArchiLU, the Board examines a submitted assessment, assigns questions to owners and keeps the decision with its reasoning. An outline specifies what to prepare.
Read the documentHOPEX Alternatives: Choosing an Enterprise Architecture Platform
Choosing an alternative to HOPEX depends first on the architecture practice to support: governance, transformation or collected data. The uses held in HOPEX today then set the points to check.
Read the documentArchitecture Principles: Definition and Examples
A shared customer record decision becomes a reuse principle. An online lending request carries that rule and its reasoning into its assessment.
Read the documentBusiness Architecture vs Enterprise Architecture: What’s the Difference?
Business architecture describes what the business must be able to do and how it is organised. Enterprise architecture includes it and describes how applications, data and technology support it.
Read the documentEnterprise Architecture Roadmap: From Current State to Target
The roadmap describes the move from the current state to the target: the gaps, the work packages, their order and their due dates. It changes with decisions and with confirmed delivery.
Read the documentEnterprise Architect: Role and Responsibilities
The enterprise architect connects strategy, capabilities, applications and technology. They prepare choices with the teams; authorised bodies decide.
Read the documentWhat is enterprise architecture?
Enterprise architecture describes an organisation’s capabilities, processes, applications, data and technology, together with their relationships. Teams use it to plan changes and examine their consequences before making a decision.
Read the document
