Module

In the KScope Asset Registry, a Module represents an external data source or system that provides information about your assets (Elements). It acts as a connector between the Asset Registry and your IT ecosystem — allowing assets to be imported, synchronized, and updated from real-world platforms like AWS, Azure, ServiceNow, or internal systems.

Think of a Module as a data pipeline or integration point that brings asset data into the registry from other systems of record.

---

🧱 Why Modules Matter

Modules are essential for turning the Asset Registry into a dynamic, living system that stays in sync with your broader IT environment. They enable you to:

• Automatically populate the registry with accurate, real-time asset data

• Eliminate manual entry and reduce data drift or inconsistencies

• Track asset provenance — know where each asset came from

• Map data from various systems to a common structure (via Element Types)

• Enable integration-driven updates for continuous asset intelligence

---

🧩 Example: Modules in Use

Let’s say your organization uses AWS for cloud servers and ServiceNow for ITSM and application management. You configure the following Modules:

Module Name	Provides Elements For
AWS	Servers (EC2 instances)
ServiceNow	Applications, Databases

These modules automatically feed asset data into the registry, where each asset is classified under the correct Element Type and assigned to the appropriate Domain.

---

🔍 What a Module Includes

Feature	Explanation
Name / Identifier	A unique name for the data source (e.g., AWS, SNOW_Prod)
Source Type	The system it connects to (e.g., AWS API, CMDB, custom DB)
Linked Elements	All Elements that originated from this source
Mapped Element Types	Helps transform source-specific data into KScope-compliant asset schemas
Optional Sync Rules	Controls how and when data from the Module is updated in the registry

---

🔄 Example: Asset with Module Context

Element: Server_001
Element Type: Server
Module: AWS
Domain: Finance
Attributes:
  - name: Server_001
  - IP: 192.168.1.10
  - location: us-east-1
  - storage_capacity: 500

Here, Server_001 was discovered through the AWS Module, categorized as a Server, and assigned to the Finance Domain. If AWS metadata changes (e.g., IP address), the Module can update the asset automatically.

---

🧭 Where Modules Fit in the Modeling Framework

In the KScope model:

• Each Element belongs to exactly one Module — showing its origin.

• Modules are also tied to TypeFunctions to align asset types with their source systems.

• Data from Modules is translated and normalized using Element Types and Attributes, creating consistency across sources.

---

🛠 When Would I Create or Use Modules?

You work with Modules when you:

• Integrate external tools into the Asset Registry

• Import and transform asset data from systems like AWS, Azure, or ServiceNow

• Define sync frequency or behavior (e.g., pull nightly, ignore deprecated assets)

• Trace asset lineage — useful for auditing or troubleshooting data issues

---

💡 Tips for Managing Modules

• Use clear naming conventions to reflect the system and environment (e.g., AWS_Prod, ServiceNow_EU)

• Monitor for sync failures or data mismatches to ensure asset integrity

• Review mappings regularly to keep up with changes in upstream source schemas

• Consider grouping similar Modules under a TypeFunction (e.g., “Cloud Sources”)

---

✅ Summary

A Module in KScope Asset Registry is the bridge between your source systems and your centralized asset view. It ensures that asset data is always up-to-date, trustworthy, and aligned across your IT and security landscape.

By using Modules effectively, you build a continuously refreshed foundation of truth — essential for security, compliance, and operational excellence.