Goal of ArchiPulse

[ChristianVerhoeven]

Hi,

We are looking for a more centeralized way within our organisation to model and store Archimate diagrams and views. Right now it seems to not be possible to model inside ArchiPulse but use an external tool and import it.

Is there going to be a modelling option in the near future? Or is this not part of he goals set for ArchiPulse?

With Kind Regards,
Chris

[victorsoriadrp]

Hi Chris,

Great question — this touches directly on where ArchiPulse is heading.

At the moment, ArchiPulse is not a full modelling tool like Archi, and today the primary workflow is still to import models created externally.

That said, adding editing capabilities is definitely part of the near-term direction.

Current focus

Right now, ArchiPulse focuses on providing a centralized and queryable data layer for ArchiMate models. The idea is to make models easier to store, analyze, enrich, and govern once they are imported.

Editing capabilities (near term)

Instead of jumping directly into a full graphical editor, the approach is to introduce incremental, structural editing capabilities, such as:

• creating and updating elements
• managing relationships (create/remove/update)
• editing properties and metadata
• maintaining model consistency (IDs, references, etc.)

This enables model maintenance and evolution directly in ArchiPulse, even without a diagram-first interface.

Governance and collaboration

One of the key motivations behind this approach is to support organizational governance over models, which is harder to achieve with file-based tools alone.

With authentication already in place, ArchiPulse can support:

• controlled access to models
• roles and permissions
• (next) approval workflows for incoming changes (e.g. imports or integrations)
• traceability of who changed what

Versioning and snapshots

ArchiPulse also supports saving snapshots of the model, providing a foundation for:

• versioning
• change tracking
• comparing model states over time

This enables auditability and opens the door to more advanced capabilities like semantic diff.

Model-driven views (in progress)

In addition to supporting ArchiMate views, there is ongoing work on automatic, model-driven views.

The idea is to generate diagrams dynamically based on filters and selections (for example by layer, relationships, or specific elements), allowing users to:

• explore the model visually without manually creating diagrams
• derive insights from existing data
• reduce the effort of maintaining multiple static views

About graphical modelling

A full graphical editor (views, layout, canvas, etc.) is something I’m interested in exploring, but it’s a significantly larger effort and not the immediate priority.

The current focus is to first ensure that the data model is solid, import/export (OEF round-trip) is reliable, and core editing and governance capabilities are in place.

Long-term direction

Longer term, the goal is for ArchiPulse to become a platform where models can be:

• stored
• queried
• enriched
• governed
• progressively edited through APIs and lightweight interfaces

If you have specific needs around modelling, governance, or visualization, I’d really value that input — it would help shape the roadmap and priorities.

Thanks again for the question.

[ChristianVerhoeven]

Hi Victor,

Thank you for the comprehensive answer! Then we are going to use it and wait for the features to be released so we can eventually move away from local modelers.