Type Function

In the KScope Asset Registry, a TypeFunction is a high-level categorization mechanism used to group related Element Types. It helps you organize different types of assets based on their purpose, behavior, or role within your IT environment.

Think of a TypeFunction as a category label or folder for Element Types that serve a similar function — like grouping “Server,” “Application,” and “Database” under broader classifications such as “Infrastructure” or “Software.”

---

🧱 Why TypeFunctions Matter

TypeFunctions make your asset model more organized, navigable, and extensible by:

• Grouping Element Types by business function (e.g., Compute, Storage, Software)

• Supporting a modular, scalable data model

• Improving clarity when browsing, filtering, or querying asset types

• Allowing consistent treatment of related asset types in rules, policies, or visualizations

• Helping integrations (Modules) map incoming data to the right categories

---

🧩 Example: Using TypeFunctions

Let’s say you have the following Element Types:

Element Type	Represents
Server	A virtual or physical compute asset
Application	A business or infrastructure software
Database	A structured data storage system

You might organize these into the following TypeFunctions:

TypeFunction	Groups These Element Types
Infrastructure	Server
Software	Application, Database

This makes it easier to manage all “Infrastructure” assets as a group, apply rules to all “Software” elements, or display them as logical categories in the UI.

---

🔍 Key Characteristics of a TypeFunction

Feature	Explanation
Logical Category	Groups similar Element Types based on business function
Many-to-One Mapping	A TypeFunction can include many Element Types, but each Element Type belongs to one TypeFunction
Used in UI & Integrations	Helps structure user interfaces and data mappings consistently

---

🔄 Example: Full TypeFunction Mapping

TypeFunction: Infrastructure
Includes Element Types:
  - Server

TypeFunction: Software
Includes Element Types:
  - Application
  - Database

This means that when you look at all “Software” assets, you’re viewing both Applications and Databases together — helpful for reporting, tagging, or managing them as a group.

---

🧭 Where TypeFunctions Fit in the Modeling Framework

In the KScope data model:

• Element Types belong to a TypeFunction

• Modules can be linked to TypeFunctions to scope integrations

• UI groupings, dashboards, and reports often use TypeFunctions to organize information logically

---

🛠 When Would I Create or Use a TypeFunction?

Use TypeFunctions when you:

• Introduce new Element Types and need to classify them

• Want to organize the model for clarity and reusability

• Need to apply behavior or policies to a group of Element Types (e.g., compliance checks for all “Infrastructure”)

• Are mapping Modules that bring in different categories of assets (e.g., cloud vs. software systems)

---

💡 Tips for Managing TypeFunctions

• Keep TypeFunctions broad and logical — they’re not meant to be overly granular

• Align them with functional areas in your organization (e.g., Compute, Network, Security)

• Use them to streamline navigation and automation inside the Asset Registry

• Avoid overlapping purposes — each Element Type should clearly fit into one TypeFunction

---

✅ Summary

A TypeFunction in KScope Asset Registry is a smart grouping mechanism that helps you categorize and manage different types of assets by their function or role in your organization.

By using TypeFunctions effectively, you create a cleaner, more intuitive asset structure that simplifies management, enhances consistency, and supports better automation across the platform.