Skip to content

Hardware vs. Software Asset Management Architecture

Scaffold

This MicroSim has been scaffolded from its specification. The interactive implementation has not been built yet.

Run MicroSim in Fullscreen

Specification

The full specification below is extracted from Chapter 2: It Asset Management.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
**Type:** infographic

**Purpose:** Illustrate the parallel yet distinct data flows for hardware and software asset management within an IT management graph

Components to show:
- Top layer: Financial Systems (ERP, procurement, accounts payable)
- Middle layer: IT Management Graph (central)
- Bottom layer: Discovery Sources (network scanners, software metering, cloud APIs)

Left side (Hardware Asset Flow):
- Procurement → Hardware Asset node (with serial number, purchase order, cost)
- Network discovery → Device CI node (with IP, hostname, specifications)
- Relationship: FINANCIALLY_REPRESENTS (Hardware Asset → Device CI)
- Relationship: INSTALLED_IN (Device CI → Physical Location)

Right side (Software Asset Flow):
- Procurement → License Entitlement node (with SKU, quantity, contract)
- Software discovery → Software Instance node (with version, installation path)
- Relationship: CONSUMES_LICENSE (Software Instance → License Entitlement)
- Relationship: DEPLOYED_ON (Software Instance → Hardware/Virtual Host)

Connections between sides:
- Bidirectional relationship: RUNS_ON (Software Instance → Device CI)
- Aggregation query path (shown with dotted line): "Compliance Check" traversal from License Entitlement through all consuming instances

Style: Layered architecture diagram with directional arrows showing data flow and relationship types

Labels:
- "Financial Domain" on procurement systems
- "Operational Domain" on discovery sources
- "IT Management Graph" in center with node type examples
- Relationship labels on all edges

Color scheme:
- Blue for hardware-related elements
- Orange for software-related elements
- Green for the central IT Management Graph
- Purple for cross-domain relationships

Implementation: SVG or draw.io style diagram with clear separation of concerns