Equipment Inventory AI Agent

Agent Description:

The Equipment Inventory AI Agentfunctions as a hybrid monitoring system that cross‑references static asset database records with live IoT telemetry to track and manage high‑value manufacturing equipment.

Purpose and Components
  • Purpose: It streamlines the auditing process by continuously mapping real-time floor data against authorized operational baselines, ensuring equipment is in its correct zone and functioning within safe maintenance limits.

    This agent enables users to automate checks and receive intelligent notifications on items such as:

    • Real-time physical location of tagged equipment

    • Active operating hours versus maximum allowed hours

    • Misplaced asset alerts and retrieval instructions

    • Preventative maintenance work order drafts

  • Components:

    • Live Telemetry Scanner: Pulls real-time physical location and active hours via a GET request to the factory floor API.

    • Database Extractor: Parses authorized baseline rules (zone and max hours) from SQL records.

    • Inventory Auditor: Evaluates the unified asset profile to assign status tags such as NOMINAL, MISPLACED, or MAINTENANCE_DUE.

    • Routing Decision Gate: Directs the data flow based on the assigned status tag to trigger the appropriate response.

    • Loss Prevention Notifier: Generates recovery alerts for equipment found outside its authorized zone.

Supported Capabilities
  • Telemetry Scanning: Uses a GET request to scan the factory floor and pull real-time location and active hours.
  • Database Extraction: Parses a raw SQLite text dump to extract authorized baseline rules (zone and max hours) for each asset.
  • Compliance Auditing: Evaluates the unified asset profile to assign operational status tags (NOMINAL, MISPLACED, or MAINTENANCE_DUE).
  • Intelligent Routing: Isolates the status tag to dictate whether the data triggers a security alert or a maintenance ticket.
  • Automated Dispatching: Generates urgent recovery alerts for lost items or drafts preventative work orders for machinery nearing limits.
LLM Used

  • OPENAI GPT_4O_MINI

    Note: To learn more about the LLM and to modify its behavior, refer to the Configuring LLM settings section.

Sub-Agents

1. Live Telemetry Scanner

  • Role:Floor API Tracker

  • Scope:Uses a GET request to scan the factory floor and pull the real-time physical location and active hours of all tagged equipment.

  • Description:Receives an incoming JSON payload, targets the telemetry_data array, and extracts asset_id, current_zone, and operating_hours. It outputs a clean list of dictionaries for downstream processing.

  • LLM Used: Default (Inherits from parent agent).

2. Database Extractor

  • Role:SQLite Data Mapper

  • Scope:Parses a raw SQLite text dump to extract the authorized baseline rules for each piece of equipment.

  • Description: Scans a .sql file for the equipment_master_list data block. It cross-references live telemetry with these SQL records to extract the Authorized_Zone and Max_Hours, appending them to the live asset's dictionary to create a complete profile.

  • LLM Used: Default (Inherits from parent agent).

3. Inventory Auditor

  • Role:Compliance Checker

  • Scope:Evaluates the unified asset profile to assign a specific operational status tag.

  • Description: Compares current_zone to Authorized_Zone to tag items as "MISPLACED". If properly located, it subtracts operating hours from max hours to tag items ≤ 10.0 hours away from limits as "MAINTENANCE_DUE". Discards "NOMINAL" items and passes anomalous data forward.

  • LLM Used: Default (Inherits from parent agent).

4. Routing Decision Gate

  • Role: Variable Extractor

  • Scope:Isolates the status_tag variable to dictate which edge the data travels down.

  • Description:Receives the filtered list of anomalous assets, extracts the status_tag, and passes the tag alongside the payload to the appropriate outgoing edge for final processing.

  • LLM Used: Default (Inherits from parent agent).

5. Loss Prevention Notifier

  • Role: Security Dispatcher

  • Scope:Generates an urgent recovery alert for high-value equipment found outside its authorized zone.

  • Description:Formats an urgent message stating the asset_id and comparing the Expected Location vs. Current Location. It instructs the floor supervisor to dispatch a runner for immediate retrieval.

  • LLM Used: Default (Inherits from parent agent).

6. Maintenance Scheduler

  • Role:Preventative Planner

  • Scope:Drafts a work order ticket for machinery approaching its maximum operating hours to prevent mid-shift failure.

  • Description:Formats a maintenance request providing usage metrics (Current Hours vs. Max Limit) and recommends scheduling a technician during the next shift change.

  • LLM Used: Default (Inherits from parent agent).

Tools Used:

  • Request – Get: To query the internet/API and pull the live telemetry JSON containing asset locations and active hours.

  • SQL Database toolkit: To parse the raw SQLite database script URL and extract the master list of authorized zones and max operating limits.
Note: For details on modifying the Tools, refer Tools Library section.

Configuration Steps

How to Connect Custom Telemetry and Databases:

  1. Click on the Live Telemetry Scanner sub-agent to configure the live data feed.

  2. Under the Actions tab, update the requests_get tool URL with your active factory API endpoint.

  3. Click on the Database Extractor sub-agent to configure your static records.

  4. Under the Actions tab, update the sqldatabasetoolkit tool with your specific sqlite_script_url.

  5. Save and test the connection to ensure proper data merging.

Agent Workflow Behavior Summary

  1. Input: The user submits a query requesting the status of specific or all active machinery.

  2. Live Telemetry Scanner: Fetches and extracts current physical locations and operating hours from the live JSON API.

  3. Database Extractor: Cross-references the live data with the SQLite database to attach Authorized_Zone and Max_Hours limits to each asset.

  4. Inventory Auditor: Calculates compliance (zone matches and remaining hour limits) and assigns a status_tag (MISPLACED, MAINTENANCE_DUE, or NOMINAL).

  5. Routing Decision Gate: Reads the tag and filters out NOMINAL items.

    • Routes to Loss Prevention Notifier if tag is MISPLACED.

    • Routes to Maintenance Scheduler if tag is MAINTENANCE_DUE.

  6. Output: The agent returns targeted alerts or drafted work orders based on the anomaly found.

Sample Questions:

  • Query the system for the current status of FLT-064. Check their authorized zones and max hours in the database, and tell me if either of them needs attention.

  • Check the live operating hours of all active machinery. Cross-reference this with the SQL database limits and draft preventative work orders for anything within 10 hours of breaking down.

  • Are there any misplaced assets or machines requiring immediate maintenance right now?