Modelling capabilities and processes

Approved candidates form the model of record. You shape it on the Capability and Process tabs of Phase 1.

The capability canvas

The capability hierarchy, as a canvas you can edit:

• Add, rename, re-parent, or retire capabilities.
• Business capabilities are anchored to the APQC Process Classification Framework — an open industry taxonomy — so the structure stays comparable from one engagement to the next. The anchor is advisory: it informs reviewers, it never auto-classifies or blocks an approval.
• The Hierarchy, Heat map, Current vs target, and App density views are different lenses on the same model.

Maturity scoring

On the Scoring sub-tab, the AI proposes a maturity score for each capability (and each process), with a short rationale drawn from the framing, the gap register, and peer elements in the same engagement.

The AI never writes a score. Every suggestion is reviewed and applied by a consultant. If a score is later locked, changing it needs an unlock request that a platform administrator grants.

Processes

The Process tab holds business processes. You can:

• Import process models from BPMN, Visio, or draw.io uploads (as candidates).
• Draw or refine a process flow in the built-in BPMN editor (/engagements/{id}/process/{processId}/model/as_is).
• Regenerate a flow from an uploaded diagram image and critique the result.

How the model is structured

You don’t need the internal detail to use eavantage, but two things are worth knowing:

• The model spans layers — business, application, data, motivation, implementation, technology, finance — and your permissions are set per layer (see Roles).
• Every element and relationship has a type, defined by your deployment’s metamodel — the shipped ontology by default, or your firm’s own reshaped and extended version if a Platform Administrator or Engagement Lead has configured one. Either way, the editor only offers valid types and valid connections for whichever rulebook is in effect.