Skip to content

Fluke eMaint Integration

Connect your Fluke eMaint CMMS (Computerized Maintenance Management System) to Querri and analyze work orders, assets, maintenance schedules, and technician performance using natural language queries.

Fluke eMaint is a cloud-based Computerized Maintenance Management System (CMMS) that helps organizations manage maintenance operations, track assets, schedule preventive maintenance, and optimize technician workflows.

Use cases:

  • Work order tracking and management
  • Asset lifecycle management
  • Preventive maintenance scheduling
  • Equipment performance analysis
  • Technician productivity monitoring
  • Maintenance cost tracking

Fluke eMaint uses API key authentication for direct, secure access to your CMMS data.

Before connecting, ensure you have:

  • An active Fluke eMaint account
  • API access enabled (contact Fluke support if not available)
  • A valid API key with appropriate permissions
  • Your eMaint instance base URL
  • Network access to the Fluke eMaint API

To obtain your API key:

  1. Log in to your Fluke eMaint instance
  2. Navigate to Settings or Administration
  3. Look for API or Integrations section
  4. Generate a new API key or copy your existing key
  5. Save the API key securely (you’ll need it for the connection)

Note: API key availability and location may vary depending on your eMaint plan and version. Contact Fluke support if you cannot find the API settings.

  1. Go to Settings → Connectors (/settings/connectors)
  2. Find Fluke eMaint in the Business Applications category
  3. Click Connect
  4. Enter your connection details:
    • Display Name: A custom name for this connection (e.g., “Production CMMS”)
    • API Key: Your Fluke eMaint API key
    • Base URL: Your eMaint instance URL (e.g., https://your-company.emaint.com)
  5. Click Test Connection to verify credentials
  6. Click Save when the test succeeds
  7. The connector is now active

Connection verification:

  • Successful connection shows a green checkmark
  • Failed connections display an error message with details
  • Verify your API key and base URL if connection fails

Once connected, you can query:

Work Orders:

  • Open, in-progress, and completed work orders
  • Work order priorities and status
  • Assigned technicians
  • Due dates and completion dates
  • Work order descriptions and notes
  • Time tracking and labor hours

Assets and Equipment:

  • Asset inventory and details
  • Equipment specifications
  • Asset locations and hierarchies
  • Asset criticality ratings
  • Equipment history
  • Warranty information

Maintenance Schedules:

  • Preventive maintenance (PM) schedules
  • PM compliance rates
  • Upcoming maintenance tasks
  • Overdue maintenance items
  • Maintenance frequency and intervals

Technician Data:

  • Technician assignments
  • Work order completion rates
  • Response times
  • Labor hours and productivity
  • Workload distribution

Performance Metrics:

  • Mean Time Between Failures (MTBF)
  • Mean Time To Repair (MTTR)
  • Equipment uptime/downtime
  • Maintenance costs
  • Work order backlog

Once connected, query your CMMS data naturally:

Status and tracking:

"Show all open work orders"
"How many work orders were completed this week?"
"List high-priority work orders"
"What work orders are overdue?"

Assignment and workload:

"Show work orders assigned to John Smith"
"Which technicians have the most open work orders?"
"List unassigned work orders"
"What's the average work order completion time?"

Analysis:

"Compare work orders this month vs last month"
"Show work order trends over the last 6 months"
"What types of work orders are most common?"
"Calculate work order completion rate by technician"

Inventory and details:

"List all assets in Building A"
"Show critical assets that need maintenance"
"What equipment is located in the production area?"
"Find assets with expired warranties"

Performance:

"Which assets have the most work orders?"
"Show equipment with highest downtime"
"What's the failure rate by asset type?"
"List assets with poor performance metrics"

Maintenance history:

"Show maintenance history for asset XYZ"
"When was the last PM performed on this equipment?"
"What repairs have been done on Asset 123?"

Schedule management:

"Show upcoming preventive maintenance tasks"
"What PMs are due this week?"
"List overdue preventive maintenance"
"How many PMs were completed on time last month?"

Compliance:

"What's our PM compliance rate?"
"Show assets with missed PMs"
"Calculate PM schedule adherence by asset type"

Productivity:

"Show work orders completed by each technician this month"
"What's the average response time by technician?"
"Who has the best work order completion rate?"
"Compare technician productivity"

Workload:

"Show current workload per technician"
"Which technicians are over capacity?"
"List technicians with available capacity"
"What's the total maintenance cost this quarter?"
"Show maintenance costs by asset category"
"Compare planned vs actual maintenance costs"
"What are the most expensive assets to maintain?"
  • Use date filters: Filter by recent date ranges for faster queries
    • “Show work orders from the last 30 days” (good)
    • “Show all work orders ever” (slow)
  • Be specific: Target specific work order types, assets, or locations
  • Filter by status: Narrow results to specific statuses (open, completed, etc.)
  • Limit large datasets: Use “top 10” or “show sample” for exploratory queries
  • Protect API keys: Never share your API key publicly
  • Read-only access: Use API keys with minimum required permissions
  • Regular rotation: Rotate API keys periodically per security policy
  • IP whitelisting: Configure your firewall to allow only Querri’s IP (18.189.33.77)
  • Monitor access: Review API usage logs in your eMaint instance
  • Consistent naming: Use standardized asset and location naming
  • Complete data: Ensure work orders have all required fields populated
  • Regular updates: Keep work order statuses and asset information current
  • Clean data: Remove duplicate or obsolete records
  • Track metrics: Regularly query KPIs like MTBF, MTTR, and PM compliance
  • Identify trends: Look for patterns in failures and maintenance needs
  • Optimize schedules: Use data to adjust PM frequencies
  • Resource allocation: Balance technician workloads based on data

Problem: Connection test fails with authentication error.

Solution:

  • Verify your API key is correct (copy it again from eMaint)
  • Ensure API key hasn’t expired or been revoked
  • Check that API access is enabled for your account
  • Confirm your base URL is correct (include https://)
  • Contact Fluke support to verify API key permissions

Problem: Connected successfully but cannot query data.

Solution:

  • Verify your API key has read permissions for the requested data
  • Check if your eMaint account has access to the data
  • Some data may be restricted based on user role
  • Contact your eMaint administrator to verify permissions

Problem: Queries return no results or incomplete data.

Solution:

  • Verify the data exists in your eMaint instance
  • Check if you have permission to view that data type
  • Ensure work orders/assets haven’t been archived or deleted
  • Try broadening your query filters (remove date restrictions)
  • Check if data is in a different status than expected

Problem: Queries take a long time to complete.

Solution:

  • Add date filters to reduce data volume
  • Filter by specific locations or asset types
  • Avoid querying entire work order history
  • eMaint API may have rate limits causing delays
  • Large result sets take longer to process

Problem: Queries fail with “rate limit exceeded” error.

Solution:

  • Wait a few minutes before retrying
  • Reduce query frequency
  • Contact Fluke support for information about your API limits
  • Consider upgrading your eMaint plan for higher limits

If you have multiple Fluke eMaint instances, you can connect each one separately:

  1. Add a new Fluke eMaint connector
  2. Use a different API key for each instance
  3. Give each instance a descriptive name

Example:

Fluke eMaint - Production Facility
Fluke eMaint - Distribution Center
Fluke eMaint - Corporate Campus

Reference them in queries:

"Compare work order volumes between Production Facility and Distribution Center"

If your eMaint instance has custom fields:

  • They should be accessible through Querri
  • Reference them by their field names
  • Ask about custom field values in queries

Example:

"Show work orders where custom field 'Priority Level' is High"

Combine eMaint data with other connected sources:

"Join work order costs from eMaint with budget data from QuickBooks"
"Compare equipment downtime from eMaint with production metrics from PostgreSQL"
"Merge asset data from eMaint with inventory from Google Sheets"

After querying eMaint data:

  • Download results as CSV for Excel analysis
  • Export to Google Sheets for collaboration
  • Save as JSON for further processing
  • Create PDF reports

Build custom maintenance reports:

  • Recurring maintenance summaries
  • Asset performance dashboards
  • Technician productivity reports
  • Cost analysis by department or location

Use Querri to access maintenance records for:

  • Regulatory compliance audits
  • Safety inspections
  • Equipment certification requirements
  • Warranty verification

Query audit information:

"Show work order history for Asset 456"
"When was the last inspection performed?"
"List all maintenance activities in Q1 for compliance"

Use Querri to identify:

  • Assets approaching failure
  • Overdue maintenance items
  • Equipment with recurring issues
  • Technician capacity constraints

Query historical data to:

  • Predict equipment failures
  • Optimize PM schedules
  • Forecast maintenance costs
  • Plan resource needs
  • Fluke eMaint documentation: fluke.com/emaint
  • Contact Fluke support for API documentation
  • eMaint user guides and training materials

To remove Querri’s access:

In Querri:

  1. Go to Settings → Connectors
  2. Find your Fluke eMaint connection
  3. Click Disconnect or Remove
  4. Confirm the disconnection

In Fluke eMaint:

  • Optionally revoke or delete the API key in your eMaint settings
  • This prevents any future access even if someone has the key

Note: Disconnecting immediately removes the API key from Querri and stops all data access.