Alphabetic List of Products
Name | Short Description | Main Capability | Sub Capability | ||
AAM/Archimate Management | Define details of changes in time to find out how changes of Knowledge Functions will influence each other | 2 | 8 | Product Lifecycle Management | Product & Service Management |
AAM/Architecture Modeling | Designing Architecture Models, defining PROSA, etc. based on (extended) Archimate | 5 | 4 | Enterprise Architecture | Architecture Concept Development |
AAM/Architecture Modeling Full | Modeling and Managing all Arcitecture components in Archimate 3.0+ | 5 | 5 | Enterprise Architecture | Architecture Continuum Development |
AAM/Capability Design | Modeling Capabilities | 5 | 2 | Enterprise Architecture | Product Lifecycle Management |
AAM/Capability Design | Designing Capabilities in their Product Delivery context, including the Actors, etc. up to Knowledge Functions | 2 | 2 | Product Lifecycle Management | Capability Management |
AAM/Capability Design | designing the Capability according to the Strategy | 1 | 1 | Strategy Modeling | Strategy-to-Capability |
AAM/Capability Management | Managing Capabilities | 5 | 2 | Enterprise Architecture | Product Lifecycle Management |
AAM/Capability Management | Managing and modeling Capabilities | 3 | 3 | Information Management | Knowledge Function Management |
AAM/Capability Management | managing, planning and developing Capabilities; connection to Information Planning | 1 | 1 | Strategy Modeling | Strategy-to-Capability |
AAM/Capability Map | designing the Capability Map; connection to Knowledge Function Modeling | 1 | 1 | Strategy Modeling | Strategy-to-Capability |
AAM/PEA Generation and checking | Generating the PEA based on the delivered components and checking the PEA against the PSA | 5 | 7 | Enterprise Architecture | Optimization of the Design Continuum |
AAM/Principles Derivation | based on the Strategic Principles the Principles of each Architecture Domain are detailed on a high level | 1 | 1 | Strategy Modeling | Strategy-to-Capability |
AAM/PSA Generation | Generating the PSA based on the modeling the Product Service Delivery and the Information Service Delivery | 5 | 6 | Enterprise Architecture | Transition Support |
AAM/PSA Generation | Generating the PSA based on the modeling the Product/Service Delivery and the Information Service | 3 | 4 | Information Management | Change Management |
AAM/PSA Generation | Generating the PSA based on the modeling the Product/Service Delivery and the Information Service Delivery | 3 | 3 | Information Management | Knowledge Function Management |
AAM/PSA Management | Maintaining the PSA | 6 | 1 | Transition Delivery | Requirement Management |
AAM/Service Delivery | Designing the Business Service Delivery Model | 5 | 2 | Enterprise Architecture | Product Lifecycle Management |
AAM/Service Delivery | designing the Business Service Delivery Model | 5 | 1 | Enterprise Architecture | Strategic Dialog |
AAM/Service Delivery | designing the Business Service Delivery Model | 1 | 5 | Strategy Modeling | Business Service Delivery Concept |
AAM/Service Delivery Modeling | Modeling the Service Delivery (Actor to Knowledge Function) incl. attention for Value Creation improvement | 6 | 5 | Transition Delivery | User Interaction Design |
AAM/Service Delivery/Patterns | recognizing Business Service Delivery patterns from initial request (Life Event) to actual results in business and information terms | 1 | 5 | Strategy Modeling | Business Service Delivery Concept |
AAM/Value Creation | Defining Value Creation in the (Conceptual and) Business Object Models | 2 | 2 | Product Lifecycle Management | Capability Management |
AAP/Agile Product Specification | Define adjustments and improvements on the Product and Delivery specifications Register Product Owners, Suppliers and Design teams for Delivery | 5 | 2 | Enterprise Architecture | Product Lifecycle Management |
AAP/Agile Product specification | Define adjustments and improvements on the Product and Delivery specifications Register Product Owners, Suppliers and Design teams for Delivery | 3 | 2 | Information Management | Operational Supplier Management |
AAP/SLA | Defining the Delivery SLAs of new specifications | 3 | 2 | Information Management | Operational Supplier Management |
AAP/Work Order specifications | Define work orders, EPICS, etc. in JIRA/TFS style registrations | 3 | 2 | Information Management | Operational Supplier Management |
ACD/Activity Competence Definition | Defining the necessary competences to use the Knowledge Function | 6 | 6 | Transition Delivery | Activity Competence Definition |
ACM/Competence Management | the collected competence registrations are used to support HRM in different ways. The first one is focusing on training the individuals and teams in learning the new competences, while the second one is focusing on selection of new employees. | 1 | 5 | Strategy Modeling | Competence & Culture Management |
ACM/Competence Matching | Supporting HRM to match employees and activities based on necessary competences | 6 | 6 | Transition Delivery | Activity Competence Definition |
ACM/Core Competence Management | Defining and managing the Core Competences of the organization | 5 | 4 | Enterprise Architecture | Architecture Concept Development |
ACM/Core Competence Management | Defining and managing the Core Competences of the organization | 5 | 2 | Enterprise Architecture | Product Lifecycle Management |
ACS/Competence Support | Supporting HRM to start recruiting and selecting | 6 | 6 | Transition Delivery | Activity Competence Definition |
ACT/Competence Training | Supporting HRM to plan training employees to gain competences | 6 | 6 | Transition Delivery | Activity Competence Definition |
ADM/Delivery Management | Module to register the actual hours spent per profession | 5 | 3 | Enterprise Architecture | Impact of Change Analysis |
AEM/Environment Management | Moving accepted components from one environment (Acceptance) to the other (Operations) | 5 | 7 | Enterprise Architecture | Optimization of the Design Continuum |
AFI/Function details | maintaining Messages as Information Events and Information Results in Interaction Model | 1 | 4 | Strategy Modeling | Knowledge Function Modeling |
AFI/Function Microflow Modeling | Enriching and defining the logical microflow of internal actionable Knowledge Function components | 6 | 7 | Transition Delivery | Knowledge Function Management |
AFM.Function Modeling | maintaining Augmented Knowledge components | 1 | 4 | Strategy Modeling | Knowledge Function Modeling |
AFM/Function Management | Managing Knowledge Functions for all types of functional knowledge | 6 | 7 | Transition Delivery | Knowledge Function Management |
AFM/Function Management | Managing Knowledge Functions for all types of augmented knowledge | 6 | 7 | Transition Delivery | Knowledge Function Management |
AFM/Function Modeling | Managing Function-based (Architectural, Augmented and Actionable) Knowledge Assets | 3 | 3 | Information Management | Knowledge Function Management |
AFM/Function Modeling | maintaining Actionable Knowledge components | 1 | 4 | Strategy Modeling | Knowledge Function Modeling |
AFP/Analysis | Analysis for duplicate solutions including higher risks, probable budget overruns, extra requirements are necessary | 3 | 6 | Information Management | Planning and Control |
AFP/Funnel Planning | Registering and managing all opportunities for improvements, including the consequences and alternatives for Transition Delivery | 3 | 6 | Information Management | Planning and Control |
AFP/Funnel Planning | Registering potential innovations, delivering opportunities for the already developed products, services and innovations in their context of the architecture and design continua, and support the decision making until initiatives become available for Information Planning; here the focus is specifically on integrating new innovation and developments and deciding whether the fit/gap is defined enough to distinguish the necessary Statement of Work to be performed and base a planning on that | # | 6 | Product Lifecycle Management | Fit/Gap Analysis |
AFP/Funnel Planning | Registering potential innovations, delivering opportunities for the already developed products, services and innovations in their context of the architecture and design continua, and support the decision making until initiatives become available for Information Planning; here the focus is on delivering new proposals, including the Value Creation, the Cost/Benefit essentials, etc. | 2 | 7 | Product Lifecycle Management | Product & Service Improvement |
AFP/Funnel Planning | Registering potential innovations, delivering opportunities for the already developed products, services and innovations in their context of the architecture and design continua, and support the decision making until initiatives become available for Information Planning; here the focus is specifically on external innovation and developments | 2 | 5 | Product Lifecycle Management | Product Lifecycle Management |
AFP/Management Support | Delivering reports on changes for the Change Advisory Board, Product Owners, Planners, etc | 3 | 6 | Information Management | Planning and Control |
AFR/Function Requirement | Checking the PROSA requirements for each Knowledge Function of the solution components | 5 | 7 | Enterprise Architecture | Optimization of the Design Continuum |
AFR/Function Requirement | Defining the PROSA requirements for each Knowledge Function of the solution | 5 | 6 | Enterprise Architecture | Transition Support |
AFR/Function Requirement | Defining the information requirements per Knowledge Function based on the Capability Design | 3 | 3 | Information Management | Knowledge Function Management |
AFR/Function Requirement | Maintaining the PROSA requirements for each Knowledge Function of the solution | 6 | 1 | Transition Delivery | Requirement Management |
AMM/Conceptual Object Model | Generating the Conceptual Object model based on the Proposition Model | 5 | 2 | Enterprise Architecture | Product Lifecycle Management |
AMM/Designing the Proposition | Designing the Proposition Model | 5 | 2 | Enterprise Architecture | Product Lifecycle Management |
AMM/Generating KFM | Generating the Knowledge Function Model based on the Proposition Model | 5 | 4 | Enterprise Architecture | Architecture Concept Development |
AMM/Generating KFM | generating the Knowledge Function Model | 1 | 4 | Strategy Modeling | Knowledge Function Modeling |
AMM/Generating KFM | generating the Knowledge Function Model based on (Standardized) Capability Map | 1 | 2 | Strategy Modeling | Proposition Modeling |
AMM/Generating Proposition Apps | generating the maintenance Apps for Proposition components | 1 | 2 | Strategy Modeling | Proposition Modeling |
AMM/Knowledge Function Model | Generating the conceptual KFM based on the Proposition Model | 5 | 2 | Enterprise Architecture | Product Lifecycle Management |
AMM/Proposition Modeling | Modeling the Proposition Model | 5 | 4 | Enterprise Architecture | Architecture Concept Development |
AMM/Proposition Modeling | designing the Proposition Model | 1 | 2 | Strategy Modeling | Proposition Modeling |
AMM/Proposition Support Apps | Generating the maintenance apps for the Proposition components | 5 | 2 | Enterprise Architecture | Product Lifecycle Management |
AOM/Business Modeling | Define the Business Objects at the Logical Level | 3 | 1 | Information Management | Enterprise Data Management |
AOM/Business to Enterprise | mapping objects from Business (Logical model) to Enterprise (Conceptual model) Objects as specializations | 1 | 3 | Strategy Modeling | Conceptual Object Modeling |
AOM/Business to Enterprise | mapping objects from Business (Logical model) to Enterprise (Conceptual model) Objects as specializations | 6 | 2 | Transition Delivery | Data Management |
AOM/Conceptual Mapping | Checking the Business Objects and generalizing/specializing them against Enterprise Objects | 5 | 7 | Enterprise Architecture | Optimization of the Design Continuum |
AOM/Conceptual Modeling | Generating the Conceptual Model based on the Proposition Model and Elaborate | 5 | 4 | Enterprise Architecture | Architecture Concept Development |
AOM/Conceptual Modeling | Designing the Conceptual Object Model | 5 | 2 | Enterprise Architecture | Product Lifecycle Management |
AOM/Conceptual Modeling | Define the Enterprise Objects at the Conceptual level | 3 | 1 | Information Management | Enterprise Data Management |
AOM/Conceptual Modeling | designing the Conceptual Object Model | 1 | 3 | Strategy Modeling | Conceptual Object Modeling |
AOM/Conceptual Modeling | designing the Conceptual Object Model with Enterprise Objects based on the Proposition Model | 6 | 2 | Transition Delivery | Data Management |
AOM/Enterprise-Business Mapping | Map Business Objects as specializations of Enterprise Objects | 3 | 1 | Information Management | Enterprise Data Management |
AOM/Information Mapping | Checking the Business to Data mapping and optimizing the mapping | 5 | 7 | Enterprise Architecture | Optimization of the Design Continuum |
AOM/Object Modeling | Modeling Business Objects, relate them to Enterprise Objects, map them to Data Objects and generate the Information and Data messages | 6 | 7 | Transition Delivery | Knowledge Function Management |
AOM/Physical Modeling | Define the Data Objects at the Physical Level | 3 | 1 | Information Management | Enterprise Data Management |
APM/Main Processes | Managing the complexity of all Processes | 1 | 2 | Strategy Modeling | Proposition Modeling |
APM/Process Activity-Competence Management | during the modeling of Process Activities or Knowledge Functions the necessary competences to optimally fulfill the tasks in an efficient and effective way, become clear and can be registered | 1 | 5 | Strategy Modeling | Competence & Culture Management |
APM/Process Modeling | Modeling the Business Activities related to the Knowledge Functions of the Business Process in which way the process model’s actionable knowledge assets are defined | 3 | 3 | Information Management | Knowledge Function Management |
APM/Process Modeling | modeling the Business Process and storing business Events and business Results in Interaction Model | 1 | 4 | Strategy Modeling | Knowledge Function Modeling |
APM/Process Modeling | Modeling Business Processes based on either of the two modes (BPMN or CMMN) | 6 | 8 | Transition Delivery | Business Process Design |
APM/Process Modeling | Managing Processes for actionable knowledge | 6 | 7 | Transition Delivery | Knowledge Function Management |
APP/Application Portfolio Planner | Defining the initial plans, PIs, budgets, etc for the Business Cases and Value Streams | 2 | 2 | Product Lifecycle Management | Capability Management |
APP/Application Portfolio Planner | Defining the more detailed activities and how they will influence more detailed plans, PS, budgets, etc. for all the forthcoming Business Cases and Value Streams | 2 | 8 | Product Lifecycle Management | Product & Service Management |
APP/PID Generation | Generating the PID based on the PSA | 5 | 6 | Enterprise Architecture | Transition Support |
APP/PID Generation | Generating the PID based on the PSA | 3 | 3 | Information Management | Knowledge Function Management |
APR/PROSA Management | Maintaining details of Principles, Requirements, design Objectives, Standards & Agreements for the solution | 6 | 1 | Transition Delivery | Requirement Management |
APR/PROSA Modeling | Checking the details of the Principles, the Requirements, design Objectives, Standards & Agreements for the solution components | 5 | 7 | Enterprise Architecture | Optimization of the Design Continuum |
APR/PROSA Modeling | Defining the details of Principles, Requirements, design Objectives, Standards & Agreements for the solution | 5 | 6 | Enterprise Architecture | Transition Support |
APR/PROSA Modeling | Defining the details of Principles, Requirements, design Objectives, Standards & Agreements | 3 | 3 | Information Management | Knowledge Function Management |
APR/PROSA Modeling | Defining the details of Principles, Requirements, design Objectives, Standards & Agreements | 3 | 5 | Information Management | Transition Management |
ARA/ Functional Mapping | Mapping applications against Knowledge Functions to distinguish duplications of applications that support business functionalities in which case they are candidates for rationalization | 5 | 8 | Enterprise Architecture | Information Lifecycle Management |
ARA/ Functional Mapping | Mapping applications against Knowledge Functions to distinguish duplications of applications that support business functionalities in which case they are candidates for rationalization | 8 | 1 | Information Lifecycle Management | Rationalization Analysis |
ARA/Analysis Workshop | Delivering information tools and presentations to collectively weigh each application/information system individually and within selected sets of applications from several viewpoints and map them (Performance vs. Significance and Information vs. Knowledge) based on general, financial, contractual, technical, responsibility, usage, and strategy issues as displayed in text, maps, and graphs. Mapping the different applications/information systems grouped per set for their technology vs. Business value and chose the strategies for rationalization (abandon, source code conversion, modernization, migration, etc.). | 5 | 8 | Enterprise Architecture | Information Lifecycle Management |
ARA/Analysis Workshop | Support Workshops to present, discuss, evaluate and assess | 8 | 1 | Information Lifecycle Management | Rationalization Analysis |
ARA/Application Rationalization | Suite with tools for Application Rationalization. For Enterprise Architecture the following tools are relevant: | 5 | 8 | Enterprise Architecture | Information Lifecycle Management |
ARA/Information Planning | Defining the necessity and priority of each strategy for information planning and issuing the results for Information Planning. | 5 | 8 | Enterprise Architecture | Information Lifecycle Management |
ARA/Information Planning | Defining the necessity and priority of each strategy for information planning and issuing the results for Information Planning. | 8 | 1 | Information Lifecycle Management | Rationalization Analysis |
ARA/Suite | Delivering information tools and presentations to collectively weigh each application/information system individually and within selected sets of applications from several viewpoints and map them (Performance vs. Significance and Information vs. Knowledge) based on general, financial, contractual, technical, responsibility, usage, and strategy issues as displayed in text, maps, and graphs. Mapping the different applications/information systems grouped per set for their technology vs. Business value and chose the strategies for rationalization (abandon, source code conversion, modernization, migration, etc.). | 8 | 1 | Information Lifecycle Management | Rationalization Analysis |
ARA/Suite | Suite with tools for Application Rationalization. For Enterprise Architecture the following tools are relevant: | 8 | 1 | Information Lifecycle Management | Technology Stack Assessment |
ARA/Survey Development | Developing surveys for specific stakeholders within the Rationalization context | 5 | 8 | Enterprise Architecture | Information Lifecycle Management |
ARA/Survey Development | Developing surveys for specific stakeholders within the Rationalization context | 8 | 2 | Information Lifecycle Management | Information Lifecycle Management |
ARA/Survey Development | Developing surveys for specific stakeholders within the Rationalization context | 8 | 1 | Information Lifecycle Management | Technology Stack Assessment |
ARA/Value weighing | Weighing the technical and business value, including the risks and criticality for the business with contract managers, financial managers. super users, information managers and technology consultants | 5 | 8 | Enterprise Architecture | Information Lifecycle Management |
ARA/Value weighing | Weighing the technical and business value, including the risks and criticality for the business with contract managers, financial managers. super users, information managers and technology consultants | 8 | 3 | Information Lifecycle Management | Rationalization Analysis |
ARM/business Ruleset Management | Managing Business RuleSets including the sources | 6 | 7 | Transition Delivery | Knowledge Function Management |
ARM/Rule Execution | Simulation of the Business RuleSet execution in a test environment | 6 | 4 | Transition Delivery | Business RuleSet Management |
ARM/Rule Translation | Semi-automatically translating legal texts into Business Rules, including the definition of Facts | 6 | 4 | Transition Delivery | Business RuleSet Management |
ARM/RuleSet Management | Defining the Business RuleSets including sources of rules and regulations (Source, Law, Capability, etc.) | 6 | 4 | Transition Delivery | Business RuleSet Management |
ARM/RuleSet Management | Maintaining and managing different Business RuleSets | 6 | 4 | Transition Delivery | Business RuleSet Management |
ARS/Requirement Specification | Examining, Defining, and Extending Requirements for Requirement Management | 3 | 5 | Information Management | Transition Management |
ARS/Requirement Specification | Defining, Adapting, and Extending Requirements for Functional Testing and Transition Delivery | 3 | 5 | Information Management | Transition Management |
ASA/Strategy Analysis | Work in Progress | 5 | 4 | Enterprise Architecture | Architecture Concept Development |
ASA/Strategy analysis | Strategic choice Analysis based on | 2 | 3 | Product Lifecycle Management | Service Delivery Assessment |
ASA/Strategy analysis | Strategic choice Analysis based on | 2 | 1 | Product Lifecycle Management | Value Creation Assessment |
ASA/Strategy Analysis Assessment | Work in Progress | 5 | 2 | Enterprise Architecture | Product Lifecycle Management |
ASC/Supplier Contract Management | Define Contract Information and Contract Knowledge Functions Register communication and actions with Suppliers per Issue | 3 | 2 | Information Management | Operational Supplier Management |
ASL/Lifecycle Support | Supporting Application Lifecycle Management for Architects by delivering information from the Product and Information Interaction Models, use of Service Types etc. to be able to initiate optimization requests for supply and demand chain cooperation and efficiency improvements | 5 | 8 | Enterprise Architecture | Information Lifecycle Management |
ASM | Strategic choice mapping on the Knowledge Function Model | 1 | 2 | Strategy Modeling | Proposition Modeling |
ASM/Strategic Choice Mapping | Mapping the strategic choices on the Knowledge Function Model | 5 | 4 | Enterprise Architecture | Architecture Concept Development |
ASM/Strategic choice Mapping | Strategic choice mapping on the Knowledge Function Model | 2 | 3 | Product Lifecycle Management | Service Delivery Assessment |
ASM/Strategic choice Mapping | Strategic choice mapping on the Knowledge Function Model | 2 | 1 | Product Lifecycle Management | Value Creation Assessment |
ATS/Competence Support | Supporting Competences for Actor/Role combinations with Process Activities | 5 | 6 | Enterprise Architecture | Transition Support |
ATS/Data Support | Supporting Data Management and Information & Data Service Generation – Also see AOM and ISE | 5 | 6 | Enterprise Architecture | Transition Support |
ATS/Information Service Delivery | Support (pattern recognition and) design of the Information Service Delivery components (Knowledge Functions, Application Functions, Technical Services, etc.) | 5 | 6 | Enterprise Architecture | Transition Support |
ATS/Interaction Support | Supporting modeling EPICs, User Stories, Interaction Design and Presentation Services – Also see ISE | 5 | 6 | Enterprise Architecture | Transition Support |
ATS/Interaction Support | Supporting modeling EPICs, User Stories, Interaction Design and Presentation Services – Also see ISE | 6 | 1 | Transition Delivery | Requirement Management |
ATS/Knowledge Function Support | Supporting Knowledge Function Management – Also see AFM | 5 | 6 | Enterprise Architecture | Transition Support |
ATS/Process and Value Creation | Supporting Value Creation for Process Models | 5 | 6 | Enterprise Architecture | Transition Support |
ATS/Product Service Delivery | Support pattern recognition and design of the Product Service Delivery components (Actor, LifeEvent, Business Service, Contracts, Business Processes, Knowledge Functions, etc.) | 5 | 6 | Enterprise Architecture | Transition Support |
ATS/RuleSet Support | Supporting Business Rule Management – Also see ARM | 5 | 6 | Enterprise Architecture | Transition Support |
ATS/Transition Support | Supporting the Transition during different phases | 5 | 6 | Enterprise Architecture | Transition Support |
ATS/Transition Support | Supporting the Transition during different phases | 6 | 1 | Transition Delivery | Requirement Management |
AUM/EPIC Modeling | Modeling the EPIC based on the Service Delivery | 6 | 5 | Transition Delivery | User Interaction Design |
AUM/Presentation Design | Designing the different User Interactions and Windows | 6 | 5 | Transition Delivery | User Interaction Design |
AUM/Presentation DME | Directly Executing/Testing the User Interaction | 6 | 5 | Transition Delivery | User Interaction Design |
AUM/Presentation Object Modeling | Designing and Defining the Presentation Object per window for the generation of Presentation Services | 6 | 5 | Transition Delivery | User Interaction Design |
AUM/User interaction Modeling | Modeling Presentation Objects, mapping them to Business Objects, generate presentation messages | 6 | 7 | Transition Delivery | Knowledge Function Management |
AUM/User Story Design | Designing the different User Stories per EPIC and Knowledge Function | 6 | 5 | Transition Delivery | User Interaction Design |