Skip to main content

Labs & Experimental Features Guide

Labs is MachineMetrics' experimental playground — a collection of beta features, trial dashboards, and advanced tools that are in development or testing. Labs gives you early access to new capabilities before they're generally available.

1. What is Labs?​

Labs contains features that are:

  • Experimental — Still being refined based on user feedback
  • Beta — Functional but may have limitations
  • Trial — Available for testing before full release

Important Disclaimer​

Labs features are experimental and may:

  • Change significantly or be discontinued
  • Have bugs or unexpected behavior
  • Not be fully documented
  • Require additional configuration

Use Labs features with the understanding that they are works in progress. Provide feedback to help shape their development.

2. Accessing Labs​

From the Main Menu​

  1. Click My Apps in the left navigation
  2. Select Labs
  3. Browse available experimental features

Enabling Features​

Some Labs features require activation:

  1. Find the feature in Labs
  2. Click Enable or Try Now
  3. Configure initial settings if prompted
  4. The feature appears in your navigation

3. Available Labs Features​

3.1 OPC UA Tag Explorer​

Browse and discover OPC UA tags from connected machines without writing adapter scripts.

Use Cases:

  • Discover available tags on new machines
  • Verify tag paths for adapter script development
  • Troubleshoot connectivity issues
  • Explore machine capabilities

How to Use:

  1. Go to Labs → OPC UA Tag Explorer
  2. Select a machine with OPC UA connectivity
  3. Browse the tag tree structure
  4. Click tags to see:
    • Current value
    • Data type
    • Full node path
  5. Copy tag paths for use in adapter scripts

Features:

FeatureDescription
Tree NavigationBrowse hierarchical tag structure
SearchFind tags by name or path
Live ValuesSee real-time tag values
ExportExport tag list to CSV

3.2 Value Engineering Tool​

Financial breakdown of machine performance — quantify the cost of downtime, slow cycles, and quality issues.

Use Cases:

  • Calculate cost of unplanned downtime
  • Justify improvement projects with ROI data
  • Identify highest-value optimization opportunities
  • Present financial impact to leadership

How to Use:

  1. Go to Labs → Value Engineering Tool
  2. Configure financial parameters:
    • Hourly machine rate
    • Labor costs
    • Material costs
    • Overhead allocation
  3. Select date range and machines
  4. View financial impact analysis

Metrics Provided:

MetricDescription
Cost of DowntimeDollar value of lost production time
Slow Cycle CostImpact of cycles slower than expected
Quality CostCost of rejected parts
Setup OpportunityValue of reducing setup time
Total OpportunitySum of all improvement opportunities

Example Output:

Machine: CNC Mill 3
Period: Last 30 Days

Downtime Cost:         $12,450
Slow Cycle Cost:       $3,200
Quality Cost:          $1,800
Setup Opportunity:     $2,100
─────────────────────────────
Total Opportunity:     $19,550

3.3 MaintainX Integration Manager​

Configure and manage the MaintainX integration for work order creation and asset synchronization.

Use Cases:

  • Connect MachineMetrics to MaintainX CMMS
  • Map machines to MaintainX assets
  • Configure automatic work order creation
  • Sync machine status with maintenance system

Setup:

  1. Go to Labs → MaintainX Integration Manager
  2. Click Connect MaintainX
  3. Enter MaintainX API credentials
  4. Map MachineMetrics machines to MaintainX assets
  5. Configure automation rules

Configuration Options:

SettingDescription
Asset MappingLink MM machines to MaintainX assets
Auto Work OrdersCreate work orders from alarms or conditions
Status SyncUpdate MaintainX when machine status changes
Meter UpdatesPush runtime hours to MaintainX meters

See the MaintainX Integration Guide for detailed setup instructions.

3.4 Production Order Dashboard (Trial)​

Visual dashboard for tracking production orders and work-in-progress.

Use Cases:

  • Track order progress across machines
  • Monitor WIP levels
  • Identify bottlenecks in order flow
  • View order status at a glance

Features:

FeatureDescription
Order CardsVisual cards showing order status
Progress BarsCompletion percentage by order
Machine AllocationSee which machines are running which orders
Due Date TrackingColor-coded based on delivery risk
Filter & SortFilter by customer, priority, status

How to Access:

  1. Go to Labs → Production Order Dashboard
  2. Click Enable Trial
  3. Dashboard appears in your Dashboards menu

3.5 Utilization Dashboard (Trial)​

Enhanced utilization dashboard with drill-down capabilities and comparative views.

Use Cases:

  • Deep-dive into utilization metrics
  • Compare utilization across machine groups
  • Analyze utilization trends over time
  • Identify underutilized assets

Features:

FeatureDescription
Utilization HeatmapVisual grid of utilization by machine/time
Drill-DownClick to see breakdown by state
ComparisonsSide-by-side machine group comparison
Trend AnalysisHistorical utilization patterns
ExportDownload utilization data

How to Access:

  1. Go to Labs → Utilization Dashboard
  2. Click Enable Trial
  3. Configure default filters and views

3.6 APM Onboarding Tools​

Tools to help configure Automatic Production Matching (APM) for new machines.

Use Cases:

  • Configure APM for new machine connections
  • Test program header parsing
  • Validate operation matching rules
  • Troubleshoot APM issues

Tools Included:

ToolDescription
Program Header AnalyzerView and parse program headers in real-time
Match Rule TesterTest regex patterns against sample data
Operation Mapping WizardStep-by-step APM configuration
Diagnostic ViewerSee APM decisions and matches

How to Use:

  1. Go to Labs → APM Onboarding Tools
  2. Select the machine to configure
  3. Use the Program Header Analyzer to view incoming data
  4. Configure matching rules using the wizard
  5. Test rules against historical data
  6. Apply configuration

3.7 Day by Hour Dashboard​

Visualize production performance broken down by hour of the day.

Use Cases:

  • Identify hourly patterns in performance
  • Optimize shift start/end procedures
  • Find time-based issues (lunch, breaks, shift changes)
  • Compare hourly performance across days

Features:

FeatureDescription
Hourly GridPerformance metrics by hour
Day ComparisonCompare same hours across different days
Metric SelectionView utilization, OEE, parts, downtime
Pattern DetectionHighlights recurring patterns

How to Access:

  1. Go to Labs → Day by Hour Dashboard
  2. Click Enable
  3. Configure default metrics and date range

3.8 Automatic Document Viewer (Beta)​

Automatically display work instructions and setup documents on Operator Dashboards based on job context.

Use Cases:

  • Show setup procedures when operations start
  • Display quality inspection instructions
  • Provide troubleshooting guides for alarms
  • Deliver just-in-time training

Requirements:

  • Knowledge Hub must be configured
  • Documents must be uploaded and tagged
  • Rules must be configured in Knowledge Hub

Setup:

  1. Go to Labs → Automatic Document Viewer
  2. Click Enable
  3. Configure delivery rules in Knowledge Hub
  4. Test on Operator Dashboard

See the Knowledge Hub Guide for detailed configuration.

3.9 Auto Reject Rules​

Automatically map reject data items from your machines to specific reject reasons, eliminating manual reject categorization and enabling real-time quality tracking.

Use Cases:

  • Automatically categorize rejects based on machine signals
  • Track quality issues without operator input
  • Link machine reject counters to specific defect categories
  • Enable automatic reject tracking for high-speed production

How It Works:

Auto Reject Rules creates a mapping between:

  1. Data items from your machine (configured as reject/part count types)
  2. Reject reasons defined in System Settings

When the machine increments a reject data item, MachineMetrics automatically records a reject with the mapped reason.

Prerequisites:

Before configuring Auto Reject Rules, you must:

  1. Configure Reject Reasons in System Settings:

    • Go to Settings → System Settings → Reject Reasons
    • Create reject reason categories (e.g., "Wrinkles", "Ribbon Length", "Slit Width")
    • These reasons appear as mapping options in Auto Reject Rules

  2. Configure Machine Data Items:

    • Machine must have data items configured for reject tracking
    • Data items must be mapped as reject counters in Machine Settings
    • Can be from direct machine connection or adapter scripts (using declare-keys)

Example Adapter Script for Reject Tracking:

For MTConnect/PLC data with reject codes:

version: 2

# Pull reject data from parent adapter
declare-keys:
  - part_quality_status
  - reject_code

# Create auto-reject variable
variables:
  auto-reject:
    - source: part_quality_status
    - expression: this == "REJECT"
    - count

# Output for Auto Reject Rules mapping
data-items:
  - auto-reject

Setup:

  1. Go to Labs → Auto Reject Rules
  2. Click Enable if not already active
  3. You'll see the Part reject mapper table with columns:
    • MACHINE: Select the machine
    • DATA ITEM: Select the reject data item (from machine data mapping)
    • REASON: Select the reject reason (from System Settings)

Configuration Example:

MachineData ItemReason
Packaging AutomationFlexy-System-BadPartsSlitting | CNS13_Wrinkles - Slitting
Slitting Automation 1Bad-PartsSlitting | NS-RL_NC Slitting Ribbon Length
Slitting Automation 2Bad-PartsSlitting | NS-SC_NC Slitting - Splice Config
Slitting Automation 3Bad-PartsSlitting | NS-SW_NC Slitting - Slit Width

How to Configure:

  1. Add Mapping Row:

    • Click "+" or "Add" to create a new mapping

  2. Select Machine:

    • Choose the machine from the dropdown
    • Only machines with reject data items appear

  3. Select Data Item:

    • Choose the data item that represents the reject counter
    • Only data items configured as reject/part counts appear
    • These come from Machine Settings → Data Mapping

  4. Select Reject Reason:

    • Choose the appropriate reject reason
    • Only reasons configured in System Settings appear
    • Reasons can include categories (e.g., "Slitting | Wrinkles")

  5. Save:

    • Click Save at the bottom of the page
    • Mappings take effect immediately

What Happens:

Once configured:

  1. Machine increments the reject data item (e.g., Bad-Parts goes from 5 → 6)
  2. MachineMetrics detects the increment
  3. System automatically creates a reject event with the mapped reason
  4. Reject appears in quality reports with the correct categorization
  5. No operator input required

Benefits:

BenefitDescription
Automatic TrackingRejects recorded without operator intervention
Real-Time Quality DataImmediate visibility into quality issues
Accurate CategorizationMachine signals map directly to defect types
High-Speed CompatibleWorks for fast production lines where manual entry isn't feasible
Consistent DataEliminates operator variability in reject categorization

Workflow Integration:

[Machine detects defect]
        ↓
[Increments reject data item]
        ↓
[Auto Reject Rules detects change]
        ↓
[Maps to configured reject reason]
        ↓
[Creates reject event in MachineMetrics]
        ↓
[Appears in Quality Reports]

Troubleshooting:

IssueSolution
Data item not appearingVerify data item is mapped as reject count in Machine Settings → Data Mapping
Reject reason not appearingCreate reject reason in Settings → System Settings → Reject Reasons
Rejects not recordingCheck machine connectivity and data item values in Machine Timeline
Wrong reason mappingEdit the mapping in Auto Reject Rules and save

Advanced Configuration:

For complex scenarios with multiple reject types from one machine:

  1. Use Adapter Scripts:

    • Create separate declare-keys for each reject type
    • Use variables to categorize rejects based on codes
    • Output multiple reject data items

  2. Multiple Mappings:

    • One machine can have multiple data items
    • Each data item maps to a different reject reason
    • Example: wrinkle_count → "Wrinkles", length_errors → "Ribbon Length"

Example Multi-Reject Adapter Script:

version: 2

# Pull multiple reject signals
declare-keys:
  - reject_code
  - part_quality_status

# Create separate reject counters per defect type
variables:
  wrinkle_rejects:
    - source: reject_code == "WRINKLE" and part_quality_status == "REJECT"
    - count
  
  length_rejects:
    - source: reject_code == "LENGTH" and part_quality_status == "REJECT"
    - count
  
  width_rejects:
    - source: reject_code == "WIDTH" and part_quality_status == "REJECT"
    - count

# Output all reject types
data-items:
  - wrinkle_rejects
  - length_rejects
  - width_rejects

Then map each in Auto Reject Rules:

  • wrinkle_rejects → "Wrinkles"
  • length_rejects → "Ribbon Length"
  • width_rejects → "Slit Width"

Important Notes:

  • Do NOT contact support for Auto Reject Rules configuration — all configuration is self-service through Labs
  • Ensure reject reasons exist in System Settings BEFORE configuring mappings
  • Data items must be properly mapped in Machine Settings for them to appear
  • Changes take effect immediately upon saving
  • Review Quality Reports to verify rejects are being captured correctly

4. Requesting New Features​

Submit Feature Requests​

  1. Go to Labs → Feature Requests
  2. Click Submit Request
  3. Describe the feature you'd like to see
  4. Explain your use case
  5. Submit for review

Vote on Existing Requests​

  1. Browse submitted feature requests
  2. Vote for features you'd find valuable
  3. Add comments with your use case

5. Providing Feedback​

Labs features improve based on user feedback.

How to Provide Feedback​

In-App:

  1. Use the Feedback button within Labs features
  2. Describe your experience
  3. Report bugs or issues
  4. Suggest improvements

Support:

  • Contact MachineMetrics Support with detailed feedback
  • Include screenshots and specific examples

What to Include​

InformationWhy It Helps
Steps to reproduceHelps engineers find issues
Expected vs. actual behaviorClarifies the problem
ScreenshotsVisual evidence of issues
Browser/device infoIdentifies compatibility issues
Use case descriptionHelps prioritize improvements

6. Labs FAQ​

Are Labs features free?​

Most Labs features are included in your subscription. Some advanced features may require additional licensing — check with your account manager.

Will Labs features become permanent?​

Successful Labs features typically graduate to general availability. Some features may be discontinued based on usage and feedback.

Can I use Labs features in production?​

Labs features are functional but may have limitations. Use them in production with caution and have fallback processes in place.

How do I report a bug?​

Use the in-app Feedback button or contact Support. Include detailed reproduction steps and screenshots.

Can I request access to specific Labs features?​

Yes, contact your account manager or Support to request access to specific Labs features.

7. Current Labs Status​

FeatureStatusNotes
OPC UA Tag ExplorerAvailableGenerally stable
Value Engineering ToolAvailableFinancial analysis
MaintainX Integration ManagerAvailableRequires MaintainX account
Production Order DashboardTrialERP integration recommended
Utilization DashboardTrialEnhanced analytics
APM Onboarding ToolsAvailableFor new machine setup
Day by Hour DashboardAvailableHourly analysis
Automatic Document ViewerBetaRequires Knowledge Hub
Auto Reject RulesAvailableMaps machine reject data to quality reasons

Getting Help​

  • In-App: Use the Feedback button within Labs features
  • Support Portal: Visit the MachineMetrics Support Portal
  • Account Manager: Contact for feature access requests