inventory-monitor 10.0.0

Asset Management with semi-auto discovery processes

inventory-monitor

Discover inventory from devices in NetBox

Attachments

• For attachments use https://github.com/Kani999/netbox-attachments

---

classDiagram
    class Contractor {
        +name: str
        +company: str
        +address: str
        +tenant: FK
    }
    
    class Contract {
        +name: str
        +name_internal: str
        +type: str
        +price: decimal
        +signed: date
        +accepted: date
        +invoicing_start: date
        +invoicing_end: date
    }
    
    class Invoice {
        +name: str
        +name_internal: str
        +project: str
        +price: decimal
        +invoicing_start: date
        +invoicing_end: date
    }
    
    class Component {
        +serial: str
        +serial_actual: str
        +partnumber: str
        +asset_number: str
        +project: str
        +vendor: str
        +quantity: int
        +price: decimal
        +warranty_start: date
        +warranty_end: date
    }
    
    class ComponentService {
        +service_start: date
        +service_end: date
        +service_param: str
        +service_price: decimal
        +service_category: str
        +service_category_vendor: str
    }
    
    class Probe {
        +time: datetime
        +device_descriptor: str
        +site_descriptor: str
        +location_descriptor: str
        +part: str
        +name: str
        +serial: str
        +description: str
    }

    Contractor "1" -- "*" Contract: has
    Contract "1" -- "*" Invoice: has
    Contract "1" -- "*" Contract: parent/subcontracts
    Contract "1" -- "*" Component: order_contract
    Contract "1" -- "*" ComponentService: has
    Component "1" -- "*" ComponentService: has
    Component "*" -- "1" Device: belongs to
    Component "*" -- "1" Site: belongs to
    Component "*" -- "1" Location: belongs to
    Component "*" -- "1" InventoryItem: belongs to
    Probe "*" -- "1" Device: belongs to
    Probe "*" -- "1" Site: belongs to
    Probe "*" -- "1" Location: belongs to

---

How the Data Model Works

1. Contractor

   • Represents an external company or individual providing services or components.
   • Associated with multiple contracts (Contract).

2. Contract

   • Represents a business agreement, such as for purchasing components or services.
   • Can have:
     • Multiple invoices (Invoice) for billing.
     • Subcontracts (Contract) for hierarchical contract management.
     • Components (Component) linked to the contract.
     • Services (ComponentService) provided as part of the contract.

3. Invoice

   • Linked to a contract, representing billing details.
   • Contains details about invoicing periods and project-specific billing.

4. Component

   • Represents physical or logical components involved in a project.
   • Includes details like serial number, price, vendor, warranty, and project association.
   • Linked to services (ComponentService) and devices, sites, locations, or inventory items.

5. ComponentService

   • Represents services provided for a component, such as maintenance or subscriptions.
   • Contains details about the service period, parameters, pricing, and service categories.

6. Probe

   • Represents measurements or data collection related to a device, site, or location.
   • Includes descriptors for identifying the context of the probe.

---

Example Data and Relationships

Scenario

• A contractor named TechCorp signs a contract for supplying components and providing maintenance services for a project.
• The project involves purchasing routers and switches from TechCorp, with maintenance services for these components.
• The contract also includes invoicing for specific periods.

---

Data Example

Contractor

• Name: TechCorp
• Company: TechCorp Ltd.
• Address: 123 Main St, TechCity
• Tenant: Default Tenant

Contract

• Name: Network Infrastructure Supply
• Type: Supply and Maintenance
• Price: $100,000
• Signed: 2025-01-01
• Invoicing Start: 2025-01-15
• Invoicing End: 2026-01-15

Invoice

• Name: Invoice #001
• Project: Project Alpha
• Price: $25,000
• Invoicing Start: 2025-01-15
• Invoicing End: 2025-02-15

Component

• Serial: R12345
• Part Number: RT-5000
• Vendor: TechCorp
• Price: $5,000
• Warranty Start: 2025-01-15
• Warranty End: 2028-01-15
• Project: Project Alpha

ComponentService

• Service Start: 2025-01-15
• Service End: 2026-01-15
• Service Param: Annual Maintenance
• Service Price: $1,000
• Service Category: Maintenance
• Service Category Vendor: TechCorp

Probe

• Time: 2025-02-01 10:00:00
• Device Descriptor: RT-5000 Router
• Site Descriptor: Data Center 1
• Location Descriptor: Rack A1
• Part: Router Module
• Name: Temperature Check
• Serial: R12345
• Description: Router temperature measurement.

---

Relationship Example

1. TechCorp is linked to the Network Infrastructure Supply contract.
2. The contract includes:
   • A component (router) with serial number R12345.
   • A service for annual maintenance of the router.
   • An invoice for January 2025 billing.
3. The component is associated with:
   • A site (Data Center 1).
   • A location (Rack A1).
   • A device (RT-5000 Router).
4. A probe captures performance data (temperature) for the router at a specific time.

This structure enables easy tracking of components, contracts, invoices, and services within the NetBox plugin.