Skip to main content

Assets & Knowledge Hub Guide

Overview​

What are Assets?​

Assets in MachineMetrics are the physical components of your manufacturing system:

  • Machines: CNC machines, mills, lathes, grinders, etc.
  • Edge Devices: Industrial computers that collect data from machines

Asset Management includes:

  • Adding and connecting machines
  • Configuring data collection protocols
  • Managing Edge Devices
  • Monitoring machine health via Diagnostics
  • Correcting part counts
  • Analyzing machine performance via Timeline

What is Knowledge Hub?​

Knowledge Hub is a centralized repository for storing manuals, SOPs, maintenance procedures, and operational documentation.

Key Features:

  • Upload documents (PDFs, DOCX, TXT, etc.)
  • Max AI indexes content for natural-language search
  • Operators and technicians ask questions, get answers with citations
  • Eliminates inconsistent tribal knowledge

Who Uses This:

  • IT Admins: Add and manage machines, configure Edge Devices, upload documents
  • Maintenance Teams: Use Diagnostics to troubleshoot machines, access manuals via Max AI
  • Operators: Access work instructions via Max AI, view machine status
  • Engineers: Analyze machine performance via Timeline, correct part counts

Managing Machines​

What is a Machine in MachineMetrics?​

A Machine is any piece of manufacturing equipment connected to MachineMetrics for data collection.

Examples:

  • CNC mills, lathes, grinders
  • Injection molding machines
  • Laser cutters, waterjet cutters
  • Welding machines
  • CMMs (Coordinate Measuring Machines)

Data Collected:

  • Execution state (active, inactive, disconnected)
  • Cycle times
  • Parts produced
  • Alarms and faults
  • Diagnostic metrics (spindle speed, feedrate, tool number, etc.)

Prerequisites for Adding Machines​

Before adding machines:

  1. Network setup complete:
    • Machines on same network as Edge Device
    • Or direct ethernet connection to Edge Device
    • Machines have static IP addresses (or DHCP reservations)
  2. Data collection protocols enabled on machines:
  3. Edge Device registered and configured:

Adding Machines (Manual)​

Step-by-Step:

  1. Navigate to Assets → Machines
  2. Click "Add Machine" button
  3. Enter machine details:
    • Machine Name: Unique name (e.g., "Mill #3", "Lathe-CNC-104")
    • IP Address: Machine's IP address (without port number)
      • Example: 192.168.1.100 ✅
      • Example: 192.168.1.100:8193 ❌ (do not include port)
    • Edge Device: Select Edge Device this machine connects to
  4. Click "Save"
  5. Machine added to list

Next Step: Scan and connect machine (see below)

[Recommended Image]: Screenshot of Add Machine form

Adding a New Machine Video

[Recommended Image]: Replace with direct video link

Adding Machines (CSV Import)​

When to Use: Bulk adding many machines at once.

Step-by-Step:

  1. Navigate to Assets → Machines
  2. Click "Import Machines" button
  3. Download CSV template (optional)
  4. Prepare CSV file:
    • Required columns: Machine Name, IP Address, Edge Device
    • Optional columns: Machine Group, Model, Serial Number, Location
  5. Upload CSV file
  6. Review preview
  7. Click "Import"
  8. Machines added to list

CSV Example:

Machine Name,IP Address,Edge Device
Mill #3,192.168.1.100,Edge-001
Lathe #5,192.168.1.101,Edge-001
Grinder #2,192.168.1.102,Edge-002

Next Step: Scan and connect machines (see below)

Scanning Machines​

Purpose: Determine network readiness and data collection method.

Step-by-Step:

  1. Navigate to Assets → Machines
  2. Select machine(s) to scan (checkbox)
  3. Click "Scan" button
  4. Scan runs (typically < 1 minute)
  5. Results displayed

Scan Result Statuses:

1. Ready to Connect ✅

  • Machine detected and protocol identified
  • No additional action required
  • Proceed to connecting machine

2. OPC-UA Detected ⚠️

  • OPC-UA server detected
  • Manual configuration required:
    • Security mode/policy
    • Certificate management
    • Browsing server to select data
  • See OPC-UA Connectivity Guide

3. Digital I/O T4 or T7 Detected ⚠️

  • LabJack device detected (T4, T7, or U3)
  • Manual adapter script configuration required
  • See Digital I/O Connectivity Guide
  • Takes up to 5 minutes after script configuration before machine starts reporting

4. Manual Configuration Required ⚠️

  • Machine not auto-detected
  • Check:
    • IP address correct?
    • Data collection protocol enabled on machine?
    • Network connectivity (ping machine from Edge Device)?
    • Firewall blocking connection?

5. Scan Failed ❌

  • Network connectivity issue
  • Troubleshooting:
    • Verify IP address
    • Ping machine from Edge Device (Diagnostics → Test Connectivity)
    • Check network cables, switches
    • Verify machine is powered on

Auto-Detected Protocols:

  • MTConnect
  • FANUC FOCAS
  • Citizen M700
  • Haas Next Gen
  • Haas MTConnect
  • Heidenhain

Manual Configuration Protocols:

  • OPC-UA (Bystronic, Siemens, Kepware, Fanuc Robot)
  • Digital I/O (LabJack T4/T7, Sealevel, Advantech)
  • Modbus TCP
  • MQTT

Connecting Machines​

Purpose: Start data collection from machine.

Step-by-Step:

  1. After scanning, machine status shows scan result
  2. If "Ready to Connect", select machine (checkbox)
  3. Click "Connect" button
  4. Connection attempt begins
  5. Wait up to 5 minutes for connection to establish
  6. Machine status updates:
    • Connected ✅ (green): Data flowing
    • Disconnected ❌ (red): No data

Important: Connection can take up to 5 minutes. Be patient.

If Machine Shows "Disconnected":

  • Wait full 5 minutes first
  • Refresh page
  • Check Edge Device status (online?)
  • Check machine status (powered on, data collection enabled?)
  • Review Diagnostics application for errors

Configuring I/O-Enabled Machines​

For Digital I/O Machines (LabJack T4/T7/U3, Sealevel, Advantech):

Requires: Manual adapter script configuration (YAML format)

Example: LabJack Adapter Script

version: 2

registers:
  execution-raw:
    address: 0      # AIN0
    func: 4         # Read Input Registers
    type: uint16

  part-count-raw:
    address: 1      # AIN1
    func: 4
    type: uint16

variables:
  # Convert raw ADC to voltage
  execution-voltage:
    - source: execution-raw / 409.6
  
  part-voltage:
    - source: part-count-raw / 409.6
  
  # Threshold logic
  execution:
    - source: execution-voltage > 1.15
    - off-delay: 10
    - state:
        - ACTIVE: this
        - READY: true
  
  # Part counting
  part-count:
    - source: part-voltage
    - edge: rising
    - threshold: 1.15

data-items:
  - execution
  - part-count

Steps:

  1. Navigate to Assets → Machines → Select Machine
  2. Click "Edit" → "Adapter Script" tab
  3. Paste or write YAML adapter script
  4. Click "Save"
  5. Wait up to 5 minutes for machine to start reporting
  6. Verify data in Diagnostics application

See Also: Digital I/O Connectivity Guide for comprehensive adapter script examples

Managing Edge Devices​

What is an Edge Device?​

Edge Device is an industrial computer that collects data from machines and sends it to MachineMetrics cloud.

Two Types:

1. Standard Edge Device (MachineMetrics-provided)

  • Industrial fanless PC
  • Pre-configured with MachineMetrics software
  • Collects data from up to 50 machines
  • Two ethernet ports (one for internet, one for machines)
  • WiFi capable

2. Virtual Edge (Customer-provided)

  • MachineMetrics software on customer-supplied Windows Server/PC
  • Customer manages hardware
  • Same capabilities as Standard Edge Device

Edge Device Setup (Physical)​

Physical Setup (Standard Edge Device):

What's in the Box:

  • Edge Device (industrial PC)
  • Power supply and cable
  • Ethernet cable
  • Mounting bracket (optional)
  • Quick start guide with QR code

Installation Steps:

  1. Mount or place Edge Device in secure location
    • Near machines
    • Protected from chips, coolant, debris
    • Accessible for troubleshooting
  2. Connect power cable
  3. Connect ethernet cable to Port 1 (internet/corporate network)
  4. Power on Edge Device (press power button)
  5. Wait 2-3 minutes for boot-up

Edge Device Activation (QR Code)​

On-Edge Setup (Recommended):

Prerequisites:

  • Edge Device powered on and connected to internet
  • Mobile device or laptop with camera
  • QR code from quick start guide

Step-by-Step:

  1. Navigate to Assets → Edge Devices
  2. Click "Add Edge Device"
  3. Select "On-Edge Setup"
  4. Scan QR code (from quick start guide or printed on device)
  5. Edge Device activates and appears in list
  6. Configure network settings (see below)
  7. Associate machines with Edge Device

Legacy Bluetooth Setup:

  • Older method (not recommended)
  • Requires Chrome browser (not supported on iOS)
  • More complex than QR code method

Edge Device Network Configuration​

Two Ethernet Ports:

Port 1: Corporate Network/Internet

  • Connects to company network for internet access
  • Sends data to MachineMetrics cloud
  • Configuration options:
    • DHCP (automatic IP): Recommended for most
    • Static IP: If DHCP not available or required by IT

Port 2: Machine Network

  • Connects directly to machines (or to machine network switch)
  • Does not require internet access
  • Configuration options:
    • DHCP: If machines use DHCP
    • Static IP: Must be in same IP range as machines
      • Example: Machines on 192.168.1.x, set Port 2 to 192.168.1.50

WiFi:

  • Available as alternative to Port 1 ethernet
  • Connect to WiFi network via setup interface
  • Requires SSID and password

Configuring Network:

  1. Navigate to Assets → Edge Devices → Select Edge Device
  2. Click "Network Settings"
  3. Port 1 (Internet):
    • Select DHCP or Static IP
    • If Static IP: Enter IP, Subnet, Gateway, DNS
  4. Port 2 (Machines):
    • Select DHCP or Static IP
    • If Static IP: Enter IP in same range as machines
  5. WiFi (optional):
    • Enable WiFi
    • Select SSID
    • Enter password
  6. Click "Save"
  7. Edge Device reboots with new settings (2-3 minutes)

Edge Device Diagnostics​

Monitoring Edge Device Health:

Access: Assets → Edge Devices → Select Edge Device → Diagnostics

Status Indicators:

  • Online (green): Connected to MachineMetrics cloud
  • Offline (red): No connection to cloud

Diagnostic Tools:

1. Refresh Device

  • Forces Edge Device to sync with cloud
  • Use if machine data not updating

2. Reboot Device

  • Remotely reboots Edge Device
  • Use if Edge Device offline or unresponsive
  • Takes 2-3 minutes to reboot

3. Test Connectivity

  • Automatic Ping Test: Pings all machines associated with Edge Device
  • Manual Ping Test: Ping specific IP address
  • Results show:
    • Success (green): Machine reachable
    • Failure (red): Machine not reachable

Use Case: If machine shows "Disconnected", run ping test to verify network connectivity.

Associating Machines with Edge Devices​

Purpose: Tell MachineMetrics which Edge Device collects data from which machines.

Method 1: During Machine Creation

  • When adding machine manually, select Edge Device from dropdown

Method 2: Edit Existing Machine

  1. Navigate to Assets → Machines → Select Machine
  2. Click "Edit"
  3. Change "Edge Device" field
  4. Click "Save"

Important: Each machine must be associated with exactly one Edge Device.

Knowledge Hub​

What is Knowledge Hub?​

Knowledge Hub is a centralized repository for storing manuals, SOPs, maintenance procedures, and operational documentation.

Key Benefits:

  • Eliminates Tribal Knowledge: Standardized, searchable documentation
  • Faster Problem Resolution: Operators and technicians get answers instantly via Max AI
  • Consistent Information: Everyone accesses same up-to-date documents
  • Improved Training: New employees can search for procedures

How It Works:

  1. IT Admins upload documents to Knowledge Hub
  2. MachineMetrics processes and indexes documents
  3. Max AI uses indexed content to answer user questions
  4. Users ask Max AI questions in natural language
  5. Max AI returns answers with citations to source documents

Knowledge Hub with Max AI

Feature Availability​

Status: Gradual rollout (by invitation)

Prerequisites:

  • MachineMetrics Account
  • Max AI enabled

Access Levels:

  • All Users: Can ask Max AI questions (receive answers from Knowledge Hub)
  • IT Admins: Can upload and manage documents

Requesting Access: Contact your MachineMetrics SDM (Solutions Delivery Manager) or AE (Account Executive).

Uploading Documents​

Supported Formats:

  • PDF
  • DOCX (Microsoft Word)
  • TXT (plain text)
  • MD (Markdown)
  • HTML
  • CSV
  • JSON

Step-by-Step:

  1. Navigate to Assets → Knowledge Hub
  2. Click "Upload" button
  3. Select file(s) from device
    • Single file or multiple files
    • Drag and drop supported
  4. Files upload and processing begins

File Processing States:

  • Uploading: File transferring to cloud
  • Processing: Text extraction, structure normalization, indexing
  • Processed: Ready for Max AI to use
  • Error: Processing failed (check file format, size, corruption)

Processing Time:

  • Small files (< 10 pages): < 1 minute
  • Medium files (10-100 pages): 1-5 minutes
  • Large files (> 100 pages): 5-15 minutes

Document Management (IT Admins)​

Viewing Documents:

  • Navigate to Assets → Knowledge Hub
  • List shows:
    • Document name
    • Upload date
    • Processing status
    • File size

Renaming Documents:

  1. Click document in list
  2. Click "Rename"
  3. Enter new name
  4. Click "Save"

Replacing Documents:

  1. Click document in list
  2. Click "Replace"
  3. Select new file
  4. Document automatically reprocessed

Use Case:

  • Updated version of manual
  • Corrected SOP

Deleting Documents:

  1. Click document in list
  2. Click "Delete"
  3. Confirm deletion
  4. Document removed from Knowledge Hub and Max AI

Reviewing Extracted Text:

  1. Click document in list
  2. View extracted text
  3. Validate accuracy (especially for scanned PDFs)

Using Max AI with Knowledge Hub​

Asking Questions:

Access Max AI:

  • Click Max AI icon (chat bubble) in sidebar
  • Or click Max AI button on any page

Example Questions:

  • "How do I perform first article inspection on Mill #3?"
  • "What are the maintenance steps for way lube system?"
  • "How do I troubleshoot alarm P/S 101?"
  • "What is the setup procedure for Part ABC-123?"

Max AI Response:

  • Answer: Contextual guidance based on Knowledge Hub documents
  • Citations: Links to source documents (which document, which page/section)
  • Follow-up Questions: Suggested related questions

Example Response:

Question: "How do I change tool on Mill #3?"

Answer:
To change a tool on Mill #3:
1. Press Cycle Stop button
2. Open door interlock
3. Press Tool Release button
4. Remove old tool from spindle
5. Insert new tool into spindle
6. Release Tool Release button
7. Close door interlock
8. Press Cycle Start button

Source: Mill #3 Operation Manual, Section 4.2 "Tool Changes"

Related questions:
- What is the torque spec for tool holders?
- How often should tools be changed?

Benefits:

  • Instant access to procedures
  • No searching through 200-page manuals
  • Consistent information for all users

Document Best Practices​

Structuring Documents:

1. Use Clear Section Headings

  • H1, H2, H3 headings in Word/Markdown
  • Example:
    • H1: Setup Procedure
    • H2: Mill #3 Setup
    • H3: Tool Installation

2. Concise Steps

  • Use numbered lists for procedures
  • One action per step
  • Keep steps short (1-2 sentences)

3. Single Topic Per Document

  • Don't combine unrelated topics in one file
  • Example:
    • ✅ "Mill_Setup_Procedure.pdf"
    • ❌ "All_Shop_Procedures.pdf" (split into separate files)

4. Critical Details as Text (Not Screenshots)

  • Max AI can't read text in images
  • Type out specifications, values, settings
  • Use screenshots only for visual reference

5. Descriptive File Names

  • Include machine, process, or topic in filename
  • Examples:
    • GX-400_Setup_Guide.pdf
    • Lathe-5_Maintenance_Procedure.pdf
    • Part_ABC-123_Work_Instructions.pdf

Organization:

1. Consistent Naming Conventions

  • Use same format for all documents
  • Example: [Machine]_[Topic]_[Version].pdf

2. Keep Documents Focused and Concise

  • 5-20 pages optimal
  • Split large manuals into smaller topic-specific files
  • Example:
    • Instead of "Mill #3 Complete Manual.pdf" (200 pages)
    • Split into:
      • "Mill_3_Setup_Guide.pdf"
      • "Mill_3_Operation_Guide.pdf"
      • "Mill_3_Maintenance_Guide.pdf"
      • "Mill_3_Troubleshooting_Guide.pdf"

3. Replace Outdated Documents

  • Don't keep old versions in Knowledge Hub
  • Replace with updated version (use "Replace" feature)

4. Organize by Machine, Process, or Operation

  • Group related documents
  • Use consistent naming for easy identification

Formatting to Avoid:

1. Scanned Images

  • Low-quality OCR extraction
  • Use digital PDFs or Word documents

2. Deeply Nested Formatting

  • Max AI may lose context
  • Keep structure simple (H1 → H2 → H3, max 3 levels)

3. Multi-Topic Documents

  • Hard for Max AI to isolate relevant section
  • Split into separate files

4. Overly Complex Tables

  • Simple tables okay (2-5 columns, < 20 rows)
  • Complex tables may not extract correctly
  • Consider using text lists instead

Limitations​

Text in Images:

  • Max AI cannot read text embedded in images
  • Images replaced with placeholders during processing
  • Not searchable

OCR Quality:

  • Scanned PDFs require OCR (Optical Character Recognition)
  • Quality varies based on:
    • Original scan resolution
    • Font clarity
    • Image contrast
  • For best results: Use digital PDFs (not scanned)

Complex Tables and Diagrams:

  • May not extract correctly
  • Consider providing information in text format as well

Diagnostics Application​

What is Diagnostics?​

Diagnostics provides live view of diagnostic metrics from machines.

Purpose:

  • Troubleshoot machine issues
  • Verify machine connectivity
  • Monitor real-time values (spindle speed, feedrate, tool number, etc.)
  • Export metric changes over time

Access:

  • Current Shift Dashboard → Click machine → Diagnostics tab
  • Machines Page → Select machine → Diagnostics button
  • Machine Overview Page → Diagnostics tab

[Recommended Image]: Screenshot of Diagnostics Application interface

Diagnostics Interface​

Live Data Updates:

  • Metrics update in real-time (every few seconds)
  • Shows current value for each metric

Color-Coded Status Icons:

  • Green: Normal (metric value expected)
  • Yellow: Warning (metric value abnormal but not critical)
  • Red: Fault (metric value indicates problem)

Diagnostics Status Icons

Common Diagnostic Metrics:

  • Execution: Active, Ready, Interrupted, Stopped
  • Spindle Speed: Current RPM
  • Feedrate: Current feedrate (mm/min or in/min)
  • Feedrate Override: Percentage (0-200%)
  • Spindle Override: Percentage (0-200%)
  • Tool Number: Current tool in spindle
  • Program: Active program number/name
  • Block: Current program block
  • Alarm Code: Current alarm (if any)
  • Alarm Message: Alarm description
  • Mode: Machine mode (auto, manual, MDI, etc.)
  • Door Status: Open or Closed
  • Chuck Status: Open or Closed
  • And more (varies by machine and connectivity protocol)

Using Diagnostics for Troubleshooting​

Common Troubleshooting Scenarios:

Scenario 1: Machine shows "Disconnected"

  1. Open Diagnostics for machine
  2. Check if any metrics are updating
  3. If no data: Network connectivity issue (check Edge Device, IP address, cables)
  4. If some data: Partial connectivity (check protocol configuration)

Scenario 2: Machine in-cycle but not counting parts

  1. Open Diagnostics
  2. Find part count signal (or execution state)
  3. Watch signal as machine runs
  4. If signal not changing: Check adapter script or machine configuration

Scenario 3: Feedrate override always at 50%

  1. Open Diagnostics
  2. View Feedrate Override metric
  3. Confirm value is actually 50%
  4. Check with operator (intentional or stuck?)

Scenario 4: Alarm appears but unknown

  1. Open Diagnostics
  2. View Alarm Code and Alarm Message
  3. Search alarm code in machine manual
  4. Or ask Max AI (if manual in Knowledge Hub)

Exporting Diagnostic Data​

Purpose: Export metric changes over time for deeper analysis.

Export Format: CSV file

What's Exported:

  • Only metric changes (not static values)
  • Timestamp of change
  • Metric name (key)
  • New value
  • Duration metric stayed at that value

CSV Columns:

  • start: Start timestamp
  • end: End timestamp
  • duration (ms): Duration in milliseconds
  • key: Metric name
  • value: Metric value
  • nativecode: Native alarm code (if applicable)
  • nativeseverity: Alarm severity (if applicable)
  • qualifier: Additional context
  • message: Alarm message (if applicable)
  • type: Metric type
  • subtype: Metric subtype

Step-by-Step:

  1. Open Diagnostics for machine
  2. Select Date Range (max 1 week recommended)
  3. Click "Export" button
  4. Email sent with download link
  5. Download CSV file
  6. Open in Excel or Google Sheets

Export Email

Excel Formatting Note:

  • Date/time columns may display as numbers
  • Format as date/time: Select columns → Format Cells → Custom → yyyy-mm-dd hh:mm:ss

Excel Formatting

Excel Format Dialog

Export Considerations:

  • Max 1 week of data recommended (larger exports may time out)
  • Only changes exported (reduces file size)
  • Static values (e.g., machine model) not included

Part Corrections​

What are Part Corrections?​

Part Corrections allow you to adjust part counts for machines when inaccuracies occur.

Common Scenarios:

  • Operator manually produced parts without machine signal (dry run, manual operations)
  • Machine signal missed parts (connectivity issue)
  • Operator over-counted or under-counted parts
  • Parts produced during maintenance or setup (not tracked automatically)

Access: Machines Page → Select Machine → Parts Tab → "Manage Parts" button

Adding Part Corrections​

Step-by-Step:

  1. Navigate to Machines Page
  2. Select machine
  3. Click Parts tab
  4. Click "Manage Parts" button
  5. Click "Add Correction"
  6. Enter correction details:
    • Count: Number of parts to add or subtract
      • Positive number (e.g., +10): Add 10 parts
      • Negative number (e.g., -5): Subtract 5 parts
    • Time: When correction applies (timestamp)
    • Message: Reason for correction (optional but recommended)
  7. Click "Save"

Part Corrections GIF

Example:

Count: +25
Time: 2026-01-27 10:30 AM
Message: "Operator manually produced 25 parts during machine diagnostics. Not counted automatically."

Editing Part Corrections​

Step-by-Step:

  1. Navigate to Machines Page → Parts tab → "Manage Parts"
  2. Find correction in list
  3. Click "Edit" (pencil icon)
  4. Modify count, time, or message
  5. Click "Save"

Deleting Part Corrections​

Step-by-Step:

  1. Navigate to Machines Page → Parts tab → "Manage Parts"
  2. Find correction in list
  3. Click "Delete" (trash icon)
  4. Confirm deletion
  5. Correction removed

Use Case:

  • Correction was a mistake (e.g., entered wrong count)
  • Duplicate correction

Managing Rejected Parts​

From Part Corrections Interface:

  • Can also adjust rejected parts
  • Same interface as part corrections
  • See Quality Tracking for details

Filtering Part Corrections​

Date Range Filter:

  • Select date range to view corrections for specific period
  • Useful for auditing or reviewing historical corrections

Timeline Application​

What is Timeline?​

Timeline provides visual, interactive view of machine operating status over time.

Purpose:

  • Analyze downtime patterns
  • Review production runs
  • Identify alarms and their timing
  • Examine part production and cycle times
  • Categorize downtime events

Access:

  • Machines Page → Select machine → Timeline button
  • Current Shift Dashboard → Click machine → Timeline tab
  • Machines List → Click machine → Timeline

[Recommended Image]: Screenshot of Timeline Application with multiple graphs

Timeline Graphs​

Five Graph Types:

1. Execution Graph

  • Shows Utilization % over time
  • Color-coded:
    • Green: Active (in-cycle)
    • Yellow: Inactive (idle)
    • Red: Disconnected

2. Downtime Graph

  • Shows categorized and uncategorized downtime events
  • Color-coded by downtime category
  • Hover to see details (duration, category, message)

3. Production Graph

  • Shows active operations over time
  • Each bar = one production run
  • Hover to see operation details (name, parts produced, duration)

4. Alarms Graph

  • Shows faults and events over time
  • Each marker = one alarm
  • Hover to see alarm code and message

5. Parts Graph

  • Shows cycle time and aggregated rollup
  • Part production rate over time
  • Hover to see parts per hour

6. Programs Graph

  • Shows active programs and subprograms
  • Each bar = one program execution
  • Hover to see program name/number

Customization:

  • Add/Remove Graphs: Click "Add Graph" or "X" to remove
  • Reorder Graphs: Drag and drop to reorder
  • Saved View: Preferences saved per user profile (applies to all machines)

Date Range Picker:

  • Select date range (max 7 days)
  • Presets: Today, Yesterday, Last 7 Days
  • Custom range: Select start and end dates

Panning:

  • Left Arrow: Pan left (50% of current view)
  • Right Arrow: Pan right (50% of current view)
  • Click and drag timeline to pan

Zooming:

  • Manual Zoom Controls: + and - buttons
  • Click and Drag to Zoom: Click and drag horizontally on timeline
  • Scroll Wheel: Zoom in/out (if supported by browser)

Managing Downtime in Timeline​

Categorizing Downtime:

  1. Click yellow (Inactive) segment on Execution Graph
  2. Downtime detail panel opens
  3. Select downtime category
  4. (Optional) Add note
  5. Click "Save"
  6. Segment updates with category and color

Timeline Categorize

Editing Downtime:

  1. Click downtime segment (any color)
  2. Detail panel opens
  3. Click "Edit"
  4. Change category or message
  5. Click "Save"

Splitting Downtime:

  1. Click downtime segment
  2. Click "Split"
  3. Select split time (timestamp within event)
  4. Event split into two events
  5. Categorize each separately

Use Case:

  • Long downtime with multiple causes (e.g., first 30 min = waiting for material, next 20 min = setup)

Merging Downtime:

  1. Select multiple adjacent downtime segments (Shift+Click or Ctrl+Click)
  2. Click "Merge"
  3. Events merged into one
  4. Categorize merged event

Use Case:

  • Multiple short stops with same cause (combine for easier analysis)

Timeline Best Practices​

1. Review Timeline Daily

  • Quick visual of what happened during shift
  • Identify downtime patterns

2. Use Timeline for Downtime Categorization

  • Visual context (what happened before/after downtime?)
  • Faster than categorizing from list

3. Zoom In for Details

  • Zoom in to specific time period
  • See exact timing of events
  • Example: Zoom to shift changeover to analyze delay

4. Compare Multiple Machines

  • Open Timeline for multiple machines side-by-side
  • Identify common patterns (e.g., all machines down at same time = facility issue)

5. Export Timeline Data

  • Use Diagnostics Export for deeper analysis
  • CSV data for Excel pivot tables, charts

Best Practices​

Asset Management Best Practices​

1. Use Descriptive Machine Names

  • Include machine type, number, or location
  • Examples:
    • ✅ "Mill #3 - Shop Floor A"
    • ✅ "Lathe-CNC-104"
    • ❌ "Machine 1"
    • ❌ "CNC"

2. Maintain Accurate Machine Information

  • Keep IP addresses up to date
  • Update machine groups when reorganizing shop
  • Archive decommissioned machines (don't delete)

3. Document Network Configuration

  • Maintain list of machine IP addresses
  • Document Edge Device network settings
  • Update documentation when changes occur

4. Monitor Edge Device Health

  • Check Edge Device status weekly
  • Address "Offline" status immediately
  • Run connectivity tests if issues arise

5. Regular Diagnostics Review

  • Spot-check Diagnostics daily
  • Verify metrics are updating
  • Investigate disconnected machines promptly

Knowledge Hub Best Practices​

1. Organize Documents by Topic

  • Use consistent naming conventions
  • Group related documents
  • Example structure:
    • Setup Procedures/
    • Maintenance Procedures/
    • Troubleshooting Guides/
    • Work Instructions/

2. Keep Documents Current

  • Replace outdated documents (use "Replace" feature)
  • Don't keep multiple versions in Knowledge Hub
  • Version control in document name (e.g., "v2.1")

3. Use Digital PDFs (Not Scanned)

  • Digital PDFs extract more accurately
  • If must scan: High resolution (300+ DPI), clear text

4. Break Large Manuals into Smaller Files

  • 5-20 pages optimal
  • One topic per file
  • Faster processing, better Max AI results

5. Train Users on Max AI

  • Show operators how to ask questions
  • Demonstrate with common scenarios
  • Encourage use over searching paper manuals

Part Corrections Best Practices​

1. Add Message for Every Correction

  • Explain why correction is needed
  • Provides audit trail

2. Review Corrections Regularly

  • Weekly or monthly audit
  • Identify patterns (frequent corrections = machine issue?)

3. Train Operators on When to Request Corrections

  • Operators should report missed parts immediately
  • Don't wait until end of shift

Timeline Best Practices​

1. Use Timeline for Shift Handoff

  • Outgoing shift reviews Timeline with incoming shift
  • Visual summary of what happened

2. Categorize Downtime in Timeline

  • Visual context helps accuracy
  • See what happened before/after event

3. Zoom to Problem Areas

  • Identify specific time periods with issues
  • Analyze root cause

4. Save Custom Graph Views

  • Configure graphs for your workflow
  • Saved automatically per user

Getting Help​

Common Questions​

"Machine won't connect"

  • Check scan results (Ready to Connect?)
  • Verify IP address correct
  • Run ping test from Edge Device (Diagnostics → Test Connectivity)
  • Check machine data collection protocol enabled
  • Wait full 5 minutes after clicking "Connect"

"Edge Device showing offline"

  • Check power (is Edge Device powered on?)
  • Check network connection (ethernet cable plugged in?)
  • Reboot Edge Device (Assets → Edge Devices → Select → Reboot)
  • Contact support if still offline after reboot

"Knowledge Hub document not processing"

  • Check file format (supported formats: PDF, DOCX, TXT, MD, HTML, CSV, JSON)
  • Check file size (very large files may take longer)
  • Verify file not corrupted (try opening on computer)
  • Contact support if error persists

"Max AI not finding information in documents"

  • Verify document processed successfully (status = "Processed")
  • Check document quality (digital PDF vs. scanned)
  • Rephrase question (try different wording)
  • Verify information actually in document (review document in Knowledge Hub)

"Part corrections not showing in reports"

  • Refresh page
  • Check date range (is correction within selected date range?)
  • Verify correction saved successfully (review in Manage Parts)

"Timeline showing incorrect downtime"

  • Check machine execution state (is signal accurate?)
  • Review adapter script configuration (if I/O machine)
  • Verify scheduled time configuration

Before Contacting Support​

Gather Information:

  • Machine name(s) affected
  • Edge Device name (if applicable)
  • Screenshot of issue
  • Steps to reproduce
  • When issue started (recent change?)

Try These Steps:

  1. Refresh page (F5 or Cmd+R)
  2. Check machine connectivity (ping test)
  3. Check Edge Device status (online?)
  4. Reboot Edge Device (if offline)
  5. Review Diagnostics for errors

Contact Support​

MachineMetrics Support:

  • Email: support@machinemetrics.com
  • Include:
    • Machine name(s)
    • Edge Device name (if applicable)
    • Screenshot of issue
    • Expected behavior vs. actual behavior
    • Steps to reproduce

For Training:

  • Request asset management training
  • Ask about Knowledge Hub best practices
  • Schedule Max AI user training

Next Steps:

Questions? Contact support@machinemetrics.com