Configuration Checklist

Use this checklist when setting up or auditing a machine in MachineMetrics:

• Machine added via Assets → Machines

• For CSV imports, columns are correctly formatted (case sensitive): machineName (required), machineMake, machineModel, serial, year, edgeSerialNumber, ipAddress (all optional except machineName)

• System attempted auto-detection of connection type after Save and Connect

• Any machines labeled Needs connecting have:

  • Data Collection Method manually set
  • Connection address entered
  • Adapter script configured (if needed)

• Machine appears with correct connection status, IP, and collection method

• General Information:

  • Machine name, type, make, model, year, serial set
  • Machine schedule assigned
  • Benchmarking participation decided
  • Notes field updated with setup and context
  • Controller make/model entered

• Production & Operations:

  • Manage jobs in set (ShopPulse vs ERP Driven) per your workflow
  • Record labor as and Schedule jobs as mapped when using MES or preparing for MES
  • Jobs selected by set (Operator vs Program) when ShopPulse is selected; Program path reviewed against APM defaults
  • Optional MES features (first article inspection, shift handover) decided and toggled if needed
  • MES enabled only after mappings are complete and operators notified (enable/disable stops active work on that machine)

• Data Collection:

  • Correct connection type selected (FANUC, MTConnect, OPC UA, etc.)
  • Connection address verified
  • Adapter script configured and working
  • Transforms configured where needed (In → Process → Out)

• Data Mapping:

  • Program items mapped as program
  • Part count items mapped as part count
  • Execution items mapped as execution
  • Important signals not left unmapped
  • Mapping exported/imported if using AI-generated mapping from PLC tags

• Data Rules:

  • Program metric selected for dashboards
  • Select Part Count Metric set to the correct option:
    • Default (part_count) for standard controller counting
    • Haas M30-Counter if experiencing double counts on Haas machines
    • Virtual Part Counter if controller counter is unreliable
    • Production Run for high mix/low volume with manual interventions
    • Manual Counter for manual stations only
  • Verified no double counting (only one counter selected, check Data Mapping)

• Warning and Failure Thresholds:

  • Machine-specific or company default thresholds chosen
  • Status color rules (green/orange/red) aligned with operational expectations

• Tool Monitoring (if licensed):

  • Tool anomaly detection configured
  • Tool thresholds defined

• Integration:

  • ERP and other integrations configured (if applicable)
  • ERP Driven job mode used where shop floor work is owned entirely in the ERP (see Production and Operations)

---