In short: The Custom Taxonomy classifies your applications according to your own business language (your Business Capability Map) rather than the Beamy framework alone. You segment the portfolio and analyze redundancies with the terms your organization already uses.
Prerequisites
A custom taxonomy configured on your platform, together with your Beamy team.
Without a custom taxonomy, the Beamy taxonomy remains the reference classification.
Why import your taxonomy
The Beamy taxonomy is the universal framework, maintained by Beamy, that automatically classifies every detected application. Your custom taxonomy reflects your internal functional map (Business Capability Map or any other logic). Both coexist: your manual adjustments are preserved when the mapping is updated.
Importing your taxonomy addresses concrete challenges for your organization:
A common language between IT and business teams: your analyses, filters and campaigns reason according to the breakdown your teams already know. No more mental translation between a generic framework and your reality, and analyses you can present in committee as-is.
Rationalization on the right breakdown: redundancies are detected at the level of your real business capabilities. Two applications grouped under the same generic category may cover two distinct capabilities in your organization: with your taxonomy, you do not rationalize by mistake.
Governance aligned with your responsibilities: your Domain Owners and architects manage functional scopes that match their actual mandate, not an imposed breakdown.
How to create your custom taxonomy
A platform back office is in preparation; for now, the setup is coordinated with Beamy's Service team:
You share the mapping of your Business Capability Map, with a description of each element, or at least of the lowest-level elements of your hierarchy.
Review rounds with the Service team: aligning labels, levels and correspondences with the Beamy taxonomy.
Import on the platform: your taxonomy becomes available across all modules.
The main feature: the key to your analyses
Every application should carry a main feature: the feature that best represents it in your taxonomy. It is much more than a label: a significant number of platform capabilities rely on it.
The Tech dimension is built on the main feature: it is what attaches each application to a functional scope.
The Analysis Scope works on this basis: a Tech scope selects applications through their main feature.
Redundancy analyses and dynamic campaigns also depend on it.
⚠️ An application without a main feature is de facto excluded from these analyses. It does not appear in any Tech sheet, is not selected by any Tech scope and escapes redundancy analyses. Make sure every application in your portfolio carries one.
Managing an application's taxonomy from the Product Sheet
Each application's custom classification is managed directly from its Product Sheet, in the Product Info tab:
Custom features: add or remove the features of your imported taxonomy.
Main feature: choose it among all available features, and change it at any time.
Where to use it
Your custom taxonomy is available across the entire product:
Apps Inventory: columns and filters on the custom taxonomy to segment the portfolio.
Tech sheets: the Tech dimension sheets represent your custom functional scopes.
People sheets: application tables display your classification.
Prioritization Matrix: filter the matrix on your taxonomy to analyze a specific functional scope.
Guidance: create dynamic campaigns targeting a custom main feature.
Automations: trigger rules based on your taxonomy.
Homemade product creation: your internally developed applications are classified in your framework.
Concrete example
Your Business Capability Map distinguishes "Customer Relationship Management" and "After-Sales Service", two capabilities that the Beamy taxonomy groups under "CRM". With the custom taxonomy, your Tech sheets, filters and campaigns reason according to your breakdown: the After-Sales Domain Owner analyzes the redundancies of their exact scope, noise-free.