Renaming PDM to Asset lifecycle management

Signed-off-by: Vineeth Kalluru <[email protected]>

Author: vikalluru

industries/predictive_maintenance_agent/.cursor.rules.md renamed to industries/asset_lifecycle_management_agent/.cursor.rules.md

@@ -1,6 +1,6 @@
 # Installation Guide
 
-This guide explains how to install the Predictive Maintenance Agent with different database and vector store options.
+This guide explains how to install the Asset Lifecycle Management Agent with different database and vector store options.
 
 ## Base Installation
 
@@ -186,7 +186,7 @@ sudo apt-get install unixodbc unixodbc-dev
 After installation, see:
 - **Configuration Guide:** `configs/README.md` - How to configure vector stores and databases
 - **Examples:** `config_examples.yaml` - Sample configurations
-- **Getting Started:** Run the predictive maintenance workflow
+- **Getting Started:** Run the Asset Lifecycle Management workflow
 
 ## Support
 

industries/predictive_maintenance_agent/.gitignore renamed to industries/asset_lifecycle_management_agent/.gitignore

@@ -0,0 +1,350 @@
+# MCP-Based Tool Proposal for Asset Lifecycle Management Agent
+
+## Overview
+
+This document proposes the integration of additional MCP (Model Context Protocol) servers to expand the Asset Lifecycle Management Agent's capabilities beyond the current focus on Operation & Maintenance phase, covering other critical phases of the asset lifecycle.
+
+## Current Implementation Status
+
+The current Asset Lifecycle Management Agent primarily focuses on the **Operation & Maintenance** phase with the following tools:
+- SQL Retriever Tool (for asset data retrieval)
+- RUL Prediction Tool (XGBoost-based remaining useful life prediction)
+- Anomaly Detection Tool (MOMENT time-series model)
+- Plotting/Visualization Tools
+
+## Proposed MCP Server Integration
+
+### 1. **Filesystem MCP Server** (For Planning & Acquisition Phase)
+
+**Purpose:** Document Management and Asset Specification Analysis
+
+**Capabilities:**
+- Read and analyze asset specification documents (PDFs, Word docs, spreadsheets)
+- Extract key technical requirements from vendor documentation
+- Compare specification sheets across multiple vendors
+- Track procurement documentation and compliance certificates
+
+**Use Cases:**
+- "Compare the technical specifications of three turbofan engine vendors based on their datasheets"
+- "Extract the warranty terms from the procurement contract for Engine Unit 42"
+- "List all compliance certificates available for the recently acquired assets"
+
+**Implementation:**
+```yaml
+mcp_servers:
+  filesystem:
+    command: "npx"
+    args:
+      - "-y"
+      - "@modelcontextprotocol/server-filesystem"
+      - "/path/to/asset_docs"
+      - "/path/to/procurement"
+      - "/path/to/specifications"
+```
+
+**Integration Benefits:**
+- Enables document-based decision making during asset acquisition
+- Provides access to historical procurement data for cost analysis
+- Facilitates vendor comparison and selection processes
+
+---
+
+### 2. **SQLite/Database MCP Server** (For Asset Registry & Configuration Management)
+
+**Purpose:** Centralized Asset Configuration and Deployment Tracking
+
+**Capabilities:**
+- Maintain a comprehensive asset registry with deployment history
+- Track configuration changes across asset lifecycle
+- Store commissioning checklists and validation results
+- Maintain asset relationships and dependencies
+
+**Use Cases:**
+- "Show the complete deployment history of Engine Unit 24 including configuration changes"
+- "List all assets commissioned in Q1 2024 along with their validation status"
+- "Identify all dependent systems for the main cooling unit before decommissioning"
+
+**Implementation:**
+```yaml
+mcp_servers:
+  asset_registry:
+    command: "npx"
+    args:
+      - "-y"
+      - "@modelcontextprotocol/server-sqlite"
+      - "/path/to/asset_registry.db"
+```
+
+**Schema Extensions:**
+```sql
+-- Asset Configuration Database
+CREATE TABLE asset_registry (
+    asset_id TEXT PRIMARY KEY,
+    asset_type TEXT,
+    acquisition_date DATE,
+    commissioning_date DATE,
+    current_location TEXT,
+    operational_status TEXT,
+    decommission_date DATE
+);
+
+CREATE TABLE configuration_history (
+    config_id INTEGER PRIMARY KEY,
+    asset_id TEXT,
+    change_date TIMESTAMP,
+    change_type TEXT,
+    configuration_details JSON,
+    changed_by TEXT,
+    FOREIGN KEY (asset_id) REFERENCES asset_registry(asset_id)
+);
+
+CREATE TABLE commissioning_records (
+    record_id INTEGER PRIMARY KEY,
+    asset_id TEXT,
+    commissioning_date DATE,
+    checklist_completed BOOLEAN,
+    validation_status TEXT,
+    commissioned_by TEXT,
+    notes TEXT,
+    FOREIGN KEY (asset_id) REFERENCES asset_registry(asset_id)
+);
+```
+
+**Integration Benefits:**
+- Provides complete asset lifecycle visibility from acquisition to disposal
+- Enables tracking of configuration drift and change management
+- Supports commissioning validation and compliance tracking
+
+---
+
+### 3. **Google Calendar/Scheduling MCP Server** (For Maintenance Planning & Optimization)
+
+**Purpose:** Proactive Maintenance Scheduling and Resource Optimization
+
+**Capabilities:**
+- Schedule preventive maintenance based on RUL predictions
+- Coordinate maintenance windows with operational requirements
+- Track maintenance history and resource allocation
+- Manage upgrade schedules and optimization initiatives
+
+**Use Cases:**
+- "Schedule preventive maintenance for all engines with RUL below 500 cycles in the next 30 days"
+- "Find an available maintenance window for Engine Unit 78 avoiding peak operational periods"
+- "Show the maintenance calendar for all critical assets in Q2 2024"
+
+**Implementation:**
+```yaml
+mcp_servers:
+  maintenance_calendar:
+    command: "npx"
+    args:
+      - "-y"
+      - "@modelcontextprotocol/server-google-calendar"
+    env:
+      GOOGLE_CALENDAR_ID: "[email protected]"
+      GOOGLE_APPLICATION_CREDENTIALS: "/path/to/credentials.json"
+```
+
+**Integration Benefits:**
+- Bridges Asset Lifecycle Management insights (especially predictive maintenance) with actionable scheduling
+- Optimizes maintenance resource utilization
+- Reduces unplanned downtime through proactive scheduling
+
+---
+
+### 4. **GitHub/Version Control MCP Server** (For Configuration Management & Documentation)
+
+**Purpose:** Technical Documentation and Configuration Version Control
+
+**Capabilities:**
+- Maintain versioned technical documentation
+- Track changes to operational procedures and maintenance protocols
+- Manage upgrade plans and implementation documentation
+- Collaborate on troubleshooting guides and knowledge base
+
+**Use Cases:**
+- "Retrieve the latest maintenance procedure document for turbofan inspections"
+- "Show the changelog for the anomaly detection threshold configuration"
+- "Create a pull request for the updated decommissioning checklist"
+
+**Implementation:**
+```yaml
+mcp_servers:
+  documentation:
+    command: "npx"
+    args:
+      - "-y"
+      - "@modelcontextprotocol/server-github"
+    env:
+      GITHUB_PERSONAL_ACCESS_TOKEN: "${GITHUB_TOKEN}"
+      GITHUB_REPOSITORY: "company/asset-documentation"
+```
+
+**Integration Benefits:**
+- Ensures documentation stays synchronized with actual practices
+- Provides audit trail for procedural changes
+- Enables collaborative knowledge management
+
+---
+
+### 5. **REST API MCP Server** (For CMMS/EAM System Integration)
+
+**Purpose:** Integration with Enterprise Asset Management Systems
+
+**Capabilities:**
+- Create and update work orders in CMMS (IBM Maximo, SAP PM, Fiix)
+- Retrieve asset performance metrics from EAM systems
+- Synchronize maintenance records bidirectionally
+- Trigger workflows in enterprise systems based on agent insights
+
+**Use Cases:**
+- "Create a work order in Maximo for urgent maintenance on Engine 42 with RUL below 100 cycles"
+- "Retrieve the last 5 maintenance work orders for Engine Unit 24 from the CMMS"
+- "Update the asset status in SAP PM based on the latest anomaly detection results"
+
+**Implementation:**
+```yaml
+mcp_servers:
+  cmms_integration:
+    command: "python"
+    args:
+      - "-m"
+      - "mcp_server_rest_api"
+      - "--config"
+      - "/path/to/cmms_api_config.json"
+```
+
+**API Configuration Example:**
+```json
+{
+  "base_url": "https://maximo.company.com/api",
+  "auth": {
+    "type": "oauth2",
+    "credentials_path": "/path/to/oauth_creds.json"
+  },
+  "endpoints": {
+    "work_orders": "/workorders",
+    "assets": "/assets",
+    "maintenance_records": "/maintenance"
+  }
+}
+```
+
+**Integration Benefits:**
+- Creates closed-loop integration between AI insights and enterprise systems
+- Eliminates manual data entry and reduces errors
+- Enables enterprise-wide asset visibility and coordination
+
+---
+
+### 6. **Time Series Database MCP Server** (For Performance Benchmarking & Optimization)
+
+**Purpose:** Long-term Performance Trending and Optimization Analysis
+
+**Capabilities:**
+- Store and query historical performance metrics
+- Compare asset performance across similar units
+- Identify degradation patterns for upgrade prioritization
+- Support Total Cost of Ownership (TCO) analysis
+
+**Use Cases:**
+- "Compare the performance efficiency of Engine Units 10-20 over the past 3 years"
+- "Identify assets with decreasing efficiency trends that are candidates for upgrade"
+- "Calculate the TCO for Engine Unit 42 from acquisition to present"
+
+**Implementation:**
+```yaml
+mcp_servers:
+  performance_db:
+    command: "python"
+    args:
+      - "-m"
+      - "mcp_server_timeseries"
+      - "--db-type"
+      - "influxdb"
+      - "--connection-string"
+      - "${INFLUXDB_URL}"
+```
+
+**Integration Benefits:**
+- Enables data-driven upgrade and replacement decisions
+- Supports ROI analysis for optimization initiatives
+- Facilitates fleet-wide performance benchmarking
+
+---
+
+## Implementation Priority
+
+### Phase 1: Foundation (Immediate - 1-2 months)
+1. **SQLite/Asset Registry Server** - Core infrastructure for tracking full lifecycle
+2. **REST API/CMMS Server** - Enterprise integration for actionable insights
+
+### Phase 2: Enhanced Capabilities (3-4 months)
+3. **Filesystem Server** - Document management for procurement and specs
+4. **Calendar/Scheduling Server** - Proactive maintenance planning
+
+### Phase 3: Advanced Features (5-6 months)
+5. **GitHub/Documentation Server** - Knowledge management and collaboration
+6. **Time Series Database Server** - Performance analytics and optimization
+
+---
+
+## Expected Benefits
+
+### Comprehensive ALM Coverage
+- **Planning & Acquisition**: Document analysis, vendor comparison, specification extraction
+- **Deployment & Commissioning**: Configuration tracking, validation recording, checklist management
+- **Operation & Maintenance**: Already covered + enhanced with scheduling and CMMS integration
+- **Upgrades & Optimization**: Performance trending, TCO analysis, ROI calculations
+- **Decommissioning & Disposal**: Asset retirement workflows, documentation archival
+
+### Operational Improvements
+- **Reduced Manual Effort**: 40-50% reduction in manual data entry and document handling
+- **Faster Decision Making**: Real-time access to cross-system data and insights
+- **Improved Compliance**: Automated audit trails and documentation management
+- **Cost Optimization**: Data-driven decisions on maintenance timing, upgrades, and replacements
+
+### Technical Advantages
+- **Modular Architecture**: MCP servers can be added incrementally without workflow disruption
+- **Enterprise Integration**: Seamless connection to existing enterprise systems
+- **Scalability**: Easy to extend to additional asset types and locations
+- **Maintainability**: Standard MCP protocol reduces custom integration complexity
+
+---
+
+## Recommended Next Steps
+
+1. **Evaluate and Select**: Prioritize 2-3 MCP servers based on immediate business needs
+2. **Pilot Implementation**: Deploy selected servers in a test environment
+3. **Integration Development**: Create NAT workflow tools that leverage the new MCP servers
+4. **User Testing**: Validate functionality with real-world use cases
+5. **Production Rollout**: Deploy to production with monitoring and support
+6. **Iterate**: Add additional MCP servers based on lessons learned and user feedback
+
+---
+
+## Technical Considerations
+
+### Security
+- Implement proper authentication and authorization for all MCP servers
+- Use encrypted connections for sensitive data
+- Implement audit logging for compliance requirements
+
+### Performance
+- Monitor MCP server response times
+- Implement caching where appropriate
+- Consider data partitioning for large-scale deployments
+
+### Maintenance
+- Establish monitoring and alerting for MCP server health
+- Document configuration and troubleshooting procedures
+- Plan for version upgrades and compatibility testing
+
+---
+
+## Conclusion
+
+Integrating these MCP servers will transform the current Operation & Maintenance-focused agent into a truly comprehensive Asset Lifecycle Management solution. The modular nature of MCP allows for incremental adoption, enabling the organization to realize benefits quickly while building toward the complete vision.
+
+The proposed tools address critical gaps across all ALM phases, from initial procurement through final decommissioning, creating a unified, AI-powered platform for holistic asset management.
+