MachineMetrics Glossary
Version 1.0 | Last Updated: January 30, 2026
This glossary defines key terminology used across the MachineMetrics platform, organized by functional area.
π Legacy Terminology Notesβ
Important: If you're familiar with older MachineMetrics terminology, review this table first. These terms have been updated or deprecated.
| Legacy Term | Modern Term | Notes |
|---|---|---|
| Job | Work Order Operation | "Job" still appears in some UI elements but refers to Work Order Operation |
| Activity Set | Production Run | Production Run is the preferred term for a collection of activities |
| Job Run | Production Run | Same concept, updated terminology |
| Job Dispatch | Start Job / Start Production Run | Action of beginning work on an operation |
| Monitors | Workflows | Renamed for clarity |
π Work Order Managementβ
Work Orderβ
A manufacturing order from an ERP system specifying what to produce, quantity required, and due date. Also called "Production Order" or "Shop Order" depending on the ERP system. Contains one or more operations that define the routing.
Work Order Operationβ
An individual manufacturing step within a work order routing. Represents specific work to be performed on a specific machine or work center. This is the modern term replacing the legacy "Job" terminology throughout the platform.
Contains:
- Operation sequence number
- Part operation reference
- Resource/work center assignment
- Quantity to produce
- Setup time standard
- Cycle time standard
- Due date
Part Operationβ
A step in a part routing defining how a part is manufactured. ERP master data specifying operation sequence, work center/resource, standard setup time, standard cycle time, tooling requirements, and instructions.
Routingβ
The sequence of part operations required to manufacture a part from raw material to finished goods.
Resourceβ
An ERP work center mapped to MachineMetrics machines. Represents where work can be performed.
Production Runβ
The period during which a machine is actively working on a specific work order operation. Begins when an operator starts a job (ShopPulse-Driven) or when a labor ticket is created (ERP-Driven). Tracks all production activity, parts produced, time elapsed, and operator assignments for that operation.
Labor Ticketβ
A record of work performed by an operator on a specific work order operation. Contains operator identification, work order and operation, start/end timestamps, parts produced (good and rejected), activity type (setup/production), and time duration. Created in ShopPulse (ShopPulse-Driven mode) or ERP (ERP-Driven mode).
π Job Tracking Modesβ
ShopPulse-Driven Modeβ
Job tracking mode where MachineMetrics is the primary operator interface. Operators use ShopPulse dashboard to clock in/out, select and start jobs, choose activity types, and submit labor tickets. MachineMetrics writes labor tickets back to ERP (bi-directional sync). Provides real-time job tracking from operator actions with no ERP terminal required for job management.
ERP-Driven Modeβ
Job tracking mode where operators continue using their existing ERP process. Operators use ERP terminals to clock in/out of jobs, and ERP creates labor tickets. MachineMetrics reads labor tickets from ERP (read-only) and provides a visibility overlay on the shop floor. Sync delay is based on configured interval (typically 5-15 minutes). ShopPulse remains available for viewing status and categorizing downtime.
Comparison: ShopPulse-Driven vs ERP-Drivenβ
| Feature | ERP-Driven | ShopPulse-Driven |
|---|---|---|
| Job Start/Stop Location | ERP system | ShopPulse dashboard |
| Labor Ticket Source | ERP system | MachineMetrics |
| Data Sync Direction | ERP β MM (read-only) | Bi-directional |
| Clock In/Out | ERP or not tracked | MachineMetrics |
| Part/Scrap Reporting | Entered in ERP | Entered in ShopPulse |
β Activityβ
An individual, consecutive block of time that is "tagged" with an Activity type. Activities on a machine cannot overlap. Activities are associated with one another and other data models through a Production Run.
Activity Modeβ
The base level aspect of an Activity. These are wholly created, maintained and controlled by MachineMetrics and are not editable by customers. Activity Mode contains the rules and details that represent any implications of the Activity to other pieces of data, metrics and other relevant elements.
Productionβ
The active manufacturing phase where parts are being produced. Tracks parts produced vs parts goal, cycle time performance, expected vs actual output, and time remaining to complete job.
Setupβ
The process of preparing a machine to run a new part (or job). Setups vary greatly by company type and machine. Tracks setup time vs expected setup time, parts produced during setup, setup progress and completion status. Can be paused (excludes pause time from duration) and transitions to Production when marked "Complete."
Job Shop Setup: A job shop typically runs a large variety of part numbers which often requires a full setup on a machine prior to running a new part. This process can be a multi-stage process that involves "tearing down" the previous setup, prepping the machine for the new part, dry running a program, running a setup part, and inspecting the part.
Production Shop Setup: A production shop with a lower number of part numbers will often have dedicated machines for specific families of parts. This greatly reduces setup times and allows the changeover process to be highly optimized (SMED - Single Minute Exchange of Dies).
Reworkβ
Correction of defective parts. A customer-configurable activity type for tracking time spent on rework operations.
Maintenanceβ
Machine repair or preventive maintenance activities tracked as part of production run context.
Activity Typeβ
Allows customers to contextualize Activities in custom ways. These are added, edited and created by customers. Activities are set to a single Activity Mode and given a unique name (for example Setup: Change Tool vs. Setup: First Piece Inspection).
Activity Selectionβ
The process where an operator specifies activity type when starting a production run. Can be done via on-screen button selection, scannable QR codes (digital), physical barcode cards (laminated station setup), or skipped entirely in "Production-Only Mode" for quick-changeover environments.
Activity Mode Configurationβ
Configuration determining how activities are tracked. Options include Production-Only Mode (simplified, no activity selection required) or Full Activity Tracking (granular activity type selection).
Production-Only Modeβ
Simplified job tracking configuration where activity selection is skipped. Operators start jobs directly into production without choosing activity types. Ideal for high-volume, quick-changeover environments.
π Schedule Intelligenceβ
MachineMetrics' modern approach to production schedulingβone that continuously adapts to real-time shop floor conditions. Unlike traditional static schedules that become outdated as soon as production begins, Schedule Intelligence integrates live machine data and ERP work order information to dynamically prioritize and adjust job schedules.
Key Capabilitiesβ
- Live completion estimates β Based on actual cycle times, not just standards
- At-risk job identification β Highlights jobs that may miss delivery dates
- Capacity utilization visibility β Shows 7-day capacity outlook
- Drag-and-drop scheduling β Planners can manually adjust priorities
- Operator visibility β Schedule changes appear instantly in ShopPulse
ETTC (Estimated Time To Complete)β
Using real-time machine or manual station data, the system calculates when a job is expected to complete. Combines historical machine performance with current conditions to provide accurate completion estimates that update with every machine cycle.
At-Risk Indicatorβ
Visual flag on scheduled operations that may miss their delivery dates based on current production pace and remaining work. Enables proactive intervention before deadlines are missed.
Capacity Utilizationβ
Percentage of available machine capacity scheduled for a given time period. The 7-day capacity utilization metric shows how much of your available capacity is committed to scheduled work.
Auto-Schedulingβ
Optional algorithms for optimizing job sequencing based on work order due dates, machine capabilities, and production constraints.
π€ Max AIβ
MachineMetrics' AI-powered digital workforce for the shop floor. Max AI agents work 24/7 to execute what your ERP plans, handle what your ERP can't see, and feed back what your ERP needs to know. Built on real-time machine data, production analytics, and self-learning anomaly detection technology.
Max AI Agentsβ
| Agent | Status | Description |
|---|---|---|
| Continuous Improvement Agent | β Available | For CI leaders, supervisors, and engineers. Instant analyst for downtime trends, machine performance, missed targets. Generates reports, suggests dashboards, surfaces anomalies. |
| Operator Assistant Agent | π Q1 2026 | For machine operators. Recommends next machine, provides setup instructions, flags alarms with resolution steps, highlights urgent tasks. |
| Supervisor Agent | π Planned | Real-time issue surfacing, root cause suggestions, and task routing for production supervisors. |
| Planner Agent | π Planned | Dynamic plan-vs-reality analysis with schedule optimization recommendations. |
| Scheduler Assistant | π Planned | Optimizes production schedules in real-time based on machine capacity, tooling availability, and priorities. |
Knowledge Hub (KHub)β
β Available
Centralized, searchable repository of tribal knowledgeβsetup procedures, troubleshooting guides, customer-specific requirements. Self-building "manufacturing Wikipedia" from operator interactions and document uploads. Foundation for all Max AI features.
Includes:
- Controller documentation library (1000+ PDFs)
- Alarm code databases with resolution procedures
- Setup and programming guides
- Customer-specific tribal knowledge
Alarm Resolution Assistantβ
π Coming Q1 2026
AI-powered feature that detects alarm triggers and immediately surfaces relevant Knowledge Hub articles. Analyzes alarm context (machine state, recent activity, similar past events) and generates step-by-step troubleshooting guides customized to the current situation. Includes operator feedback loop to improve recommendations over time.
Shift Handoverβ
β Available
AI-assisted shift transition feature. Outgoing operators complete a 5-minute intelligent debrief capturing both data and context. Incoming operators receive personalized briefings showing machine status, required actions, and job priorities with full context.
π§ Tool Managementβ
Tool Life Monitoring (TLM)β
Dashboard feature tracking tool usage counts against preset limits. Pulls data directly from CNC controls via Fanuc Macro B variables, P-Codes, OPC-UA, or MTConnect. Displays tool count vs preset, time remaining, usage percentage, and historical trends. This is counter-based trackingβno AI/ML involved.
Tool Anomaly Detection (TAD)β
AI-powered feature detecting abnormal tool behavior during cutting operations. Analyzes spindle load patterns at high frequency (1000 Hz sampling) for real-time deviations from learned baseline.
Capabilities include:
- Learns normal patterns in few cycles
- Detects breakage, chipping, wear
- Optional feed hold on anomaly detection
- Works with Fanuc FOCAS controllers
Key Distinction: TLM tracks usage counts (how much tool has been used), TAD detects anomalies (how tool is performing).
Tool Change Eventβ
Captured record when operators change tools, including time, tool number, reason, and next tool life reset. Builds predictive models for tool life analytics and enables future proactive tool change alerts.
β Quality Managementβ
First Article Inspection (FAI)β
Quality verification process for the first part produced in a new job or after setup. In MachineMetrics, operators can submit FAI requests directly in ShopPulse with real-time status tracking (Submitted β In Inspection β Approved/Rejected). Automatic notification to QA inspector with part details and measurement requirements.
Rejectβ
Any part that is intentionally excluded from the count of Good Parts due to quality issues.
Reject Reasonβ
The classification assigned to rejected parts explaining why they failed quality requirements. Configured per organization with categories like "Dimension Out of Spec," "Poor Material," "Cosmetic," etc.
Scrapβ
Rejected parts that cannot be reworked and must be discarded. Distinguished from non-conforming parts which may be reworked or used with deviation approval.
Non-Conformingβ
Product that does not fulfill its specified requirements but may be dispositioned for rework, use-as-is, or return to vendor rather than scrapped.
In-Process Inspectionβ
Periodic quality checks during production runs for long-running jobs. Operators are prompted to measure critical dimensions at specified intervals. The system can detect dimensional drift and recommend corrections.
Good Partsβ
Parts that pass quality inspection and are counted toward production output.
Quality (OEE Component)β
The percentage of parts produced that meet quality standards. Formula: (Good Parts / Total Parts) Γ 100. Measures the impact of defects and rework on overall equipment effectiveness.
π OEE & Production Analyticsβ
OEE (Overall Equipment Effectiveness)β
Industry-standard metric measuring manufacturing productivity efficiency. Calculated as:
OEE = Availability Γ Performance Γ Quality
OEE provides a single percentage that represents how effectively manufacturing equipment is being utilized. A score of 100% means you are manufacturing only good parts (Quality), as fast as possible (Performance), with no downtime (Availability).
OEE Components Summaryβ
| Component | What It Measures | Formula |
|---|---|---|
| Availability | Impact of downtime on production | Scheduled Time In-Cycle Γ· Scheduled Time Γ 100 |
| Performance | Whether machine runs at expected speed | Ideal Part Time Γ· (Scheduled Time In-Cycle Γ· Scheduled Parts) Γ 100 |
| Quality | Percentage of good parts produced | (Good Parts / Total Parts) Γ 100 |
Availabilityβ
The ratio of time the machine was producing to the time it was scheduled to produce. Measures the impact of downtime on production.
Performanceβ
Ratio of actual production speed to ideal speed. Measures whether the machine is running at expected speed. Also called "Performance Efficiency."
Qualityβ
Percentage of parts produced that meet quality standards.
OOE (Overall Operations Effectiveness)β
Takes unscheduled time into account, looking at Total Operations Time as the maximum. Provides a more realistic gauge of performance during time that machines could have been running but weren't because there was no scheduled work.
Formula: (OEE Γ Scheduled Time) Γ· Non-Optional Time
Non-Optional Timeβ
The total time a machine is available for production, excluding optional shift periods (nights, weekends, holidays) when the facility is not normally operating. Used as the denominator in OOE calculations.
TEEP (Total Effective Equipment Performance)β
Extended OEE metric including all calendar time (24/7), not just scheduled production time. Measures theoretical maximum equipment utilization. Useful for manufacturers attempting to maximize utilization regardless of shift schedules.
Utilizationβ
The percentage of total time that a machine is in-cycle. Differs from Availability by using total time rather than scheduled time.
Formula: (In-Cycle Time / Total Time) Γ 100
In-Cycle Timeβ
Time when machine is actively running production cycles (spindle engaged, cutting, processing). Excludes downtime, idle time, and non-productive periods.
Ideal Cycle Timeβ
Expected time to produce one part based on engineering standards or ERP cycle time data. Used as the baseline for performance calculations. Also called "Expected Cycle Time" or "Standard Cycle Time."
Actual Cycle Timeβ
Measured time from machine data for completed cycles. Tracked as Current Cycle (in progress), Last Cycle (L1), Average of Last 3 (LAvg), and Overall Average.
Parts Goalβ
Performance metric showing progress toward expected quantity. Displays as a visual wheel indicatorβGreen (on pace or ahead), Yellow (slightly behind), Red (significantly behind).
Formula: (Actual Parts / Expected Parts based on elapsed time and cycle time) Γ 100
Scheduled Timeβ
Any time where parts are intended to be made. Parts are not intended to be made during the planned portion of setup or when a job isn't scheduled to run.
π΄ Downtimeβ
Any time in which a machine's execution state equals inactive.
Downtime Eventβ
A single, continuous instance of downtime with a start time and end time.
Downtime Categoryβ
The classification given to contextualize the reason behind an individual Downtime Event. Organized in a hierarchical structure with primary categories (Machine, Job, Operator, General, Other) and drill-down subcategories.
Downtime Classificationβ
The process of assigning root cause categories to downtime events. Can be:
- Automatic β via Downtime Rules based on machine signals
- Manual β operator categorization via ShopPulse
- Hybrid β automatic with operator override capability
Downtime Rulesβ
Automated classification logic based on machine signals including alarm-based triggers, state-based triggers, and alarm-message triggers. Configurable with strict mode options (start/end/both).
Planned Downtimeβ
Any downtime that was planned or expected (such as lunch breaks, scheduled maintenance, meetings). Can be scheduled in advance to exclude from OEE calculations.
Unplanned Downtimeβ
Any unexpected downtime that was not planned. Requires categorization and root cause analysis.
Split Downtimeβ
The act of splitting a currently running, categorized Downtime Event into a new, separate event when the root cause changes mid-event.
Downtime Paretoβ
Analysis widget showing highest-impact downtime categories by frequency and duration. Updates in real-time to help target improvement efforts.
π± Manual Stationsβ
MachineMetrics capability for scheduling and tracking work on non-connected assetsβlike assembly benches, inspection stations, kitting areas, and manual machinesβwhere machine data isn't available.
Why It Mattersβ
Brings visibility to areas that often make up 30β60% of production but were previously out of reach. These stations are now part of MachineMetrics' scheduling, tracking, and analytics workflows.
Capabilitiesβ
- Digital job tracking for manual processes
- Labor ticketing for accurate performance and costing analysis
- ERP integration with bi-directional sync
- Automated workflows for material calls and notifications
- Unified UX across automated and manual operations
π Connectivity & Integrationβ
Edge Deviceβ
IoT-enabled hardware collecting machine data and transmitting to MachineMetrics cloud. Serves as the communication bridge between machines and the platform.
| Type | Description |
|---|---|
| Physical Edge | Ethernet/wireless connectivity with I/O terminals |
| Virtual Edge | VMware/Hyper-V software deployment |
Note: Contact MachineMetrics for current edge device model specifications.
Communication Protocolsβ
| Protocol | Description |
|---|---|
| MTConnect | Open-source manufacturing protocol for CNC machine data exchange. Standardized XML-based communication widely supported across modern CNC equipment. |
| FOCAS | Proprietary Fanuc protocol for accessing CNC controller data. Enables high-frequency data collection, macro variable reading, alarm data access, tool life data, and program information. |
| OPC-UA | Industrial automation protocol for secure, reliable data exchange. Platform-independent and supports complex data structures. |
| Modbus | Serial communication protocol for industrial devices. Supported for PLC and sensor connectivity. |
| EtherNet/IP | Industrial Ethernet protocol commonly used with Allen-Bradley PLCs and robotics. |
| IO-Link | Sensor-level communication standard. MachineMetrics supports via IO-Link connector for condition monitoring sensors. |
I/O Connectivityβ
Legacy machine connection using digital/analog signals via edge device terminals. For machines without modern communication protocols.
π ERP Integrationβ
ERP Connectorβ
Integration framework enabling bi-directional data exchange between MachineMetrics and ERP systems. Syncs work orders and operations, part operations and routings, resources (work centers), labor tickets, personnel records, and reason codes.
Supported ERP Systemsβ
| ERP System | Integration Type | Sync Modes |
|---|---|---|
| Infor Visual | REST API | ShopPulse-Driven, ERP-Driven |
| Epicor Kinetic | REST API or CSV | ShopPulse-Driven, ERP-Driven |
| Epicor 10.x | ODBC or CSV | ERP-Driven |
| JobBOSSΒ² | REST API | ShopPulse-Driven |
| JobBOSS Classic | ODBC | ShopPulse-Driven, ERP-Driven |
| Infor XA | ODBC | ShopPulse-Driven |
| Infor Syteline | ODBC | ShopPulse-Driven |
| ECI ProfitKey | ODBC | ShopPulse-Driven |
| Sage X3 | REST API | ShopPulse-Driven, ERP-Driven |
Coming in 2026: Dynamics 365, PLEX, ProShop, GlobalShop
Note: Additional ERP systems may be supported via custom solutions or middleware. Contact support@machinemetrics.com for assistance.
ERP Data Studioβ
Administrative interface for managing ERP data within MachineMetrics. Provides:
- View all imported ERP entities
- Resource mapping (ERP work centers β MM machines)
- Personnel assignment
- Reason code alignment
- Labor ticket management (create/edit/delete)
- CRUD operations on ERP data
Access restricted to IT Administrators.
π Barcode Scanningβ
Barcode Scanningβ
Input method for job tracking using handheld scanners (USB or Bluetooth). Supports job traveler scanning, activity selection via QR codes, order-agnostic two-barcode scanning (work order + operation in any sequence), and scan-to-start/scan-to-complete workflows.
Job Travelerβ
Physical document accompanying a work order containing barcoded identifiers. May include a single combined barcode (work order + operation) or separate barcodes. Scanned to initiate job tracking in ShopPulse.
Activity Barcode Cardsβ
Laminated physical cards with barcodes for activity types (Production, Setup, Rework, Maintenance). Mounted near operator tablets for "no-touch" scanning workflow. Dynamically generated based on customer-configured activity types.
π Reporting & Automationβ
Scheduled Reportsβ
Feature enabling automated delivery of reports and dashboards via email. Supports immediate or scheduled delivery, flexible scheduling options (daily, weekly, monthly), multiple recipients, PDF attachment option, and custom messaging.
Custom Report Builderβ
Native report builder allowing users to design custom reports, save, export to Excel, and print directly from the browser without third-party business intelligence tools.
Custom Dashboard Builderβ
Native dashboard builder allowing users to include custom reports, KPI charts, and trends directly in the browser.
Automations & Workflowsβ
User-configured profiles that activate when trigger conditions are met on selected machines. Previously known as "Monitors." Supports email, text, and webhook automation to alert users and integrate with business systems (CMMS, Excel, MS Teams, etc.).
Workflow Triggerβ
The specific condition that acts as the trigger for a Workflow (downtime threshold, alarm condition, performance deviation, etc.).
Workflow Actionβ
A specific action that fires when a Workflow's trigger condition is met (notification, webhook, escalation).
π₯ Customersβ
Customer Typesβ
| Type | Description |
|---|---|
| High Mix Low Volume | A company that produces many different types of parts but does not produce them in high volumes. Typically requires frequent setups and benefits most from job tracking and schedule intelligence. |
| Utilization-Focused | A company that primarily tracks machine utilization without detailed parts counting or job tracking. |
| Job Shop | A type of manufacturing process in which small batches of a variety of custom products are made. Most products require a unique set-up and sequencing of process steps. |
πΊ Data Mappingβ
Data-Itemβ
An item (used in an individual Machine's Data Mapping) that represents and defines a piece of data captured from a Machine in a format useable by MachineMetrics. Data Items are further defined (into type, subtype, component and component-type) through the process of "mapping."
Adapterβ
On The Edge Device: A piece of software running on an Edge Device used to extract information about a machine, typically by communicating with the machine's Controller. The Adapter sends this information to the SHDR Pusher software, also residing on the Edge Device, which passes it to the MM Cloud.
On The MM Cloud: A mapping which takes specific machines' data value labels and transforms them into a common format which the data ingestion pipeline can understand and use for analytics.
The Configuration Fileβ
The YAML or JSON file used to manually define Data-Items (creates/edits/transforms inputs and outputs to/from The Data Mapping).
The Automapperβ
MachineMetrics software that automatically maps data-items to their type/subtype and component/component type based on previous mappings.
π€ Machinesβ
General Termsβ
| Term | Definition |
|---|---|
| Alarm | An error code generated directly from an individual machine's controller. Can trigger automated downtime classification and workflows. |
| Axis | (1) A direction of motion (linear or rotary) that a machine offers and can be independently controlled by a machining program (G-code). (2) The subsystem of a machine that implements axis motion. |
| CNC (Computer Numerical Control) | Machine tools controlled by programmed commands encoded on a storage medium, as opposed to manually controlled machines. |
| Controller | The computer system that controls the machine's operations, interprets programs, and manages all machine functions. |
| Cycle | The interval in which a machine starts and finishes processing a part. |
| Cycle Time | The time it takes to complete a single cycle, typically measured "Start to Start"βthe starting point of one product's processing until the start of the next product's processing in the same machine. |
| DNC (Distributed Numerical Control) | CNC industry term for transferring programs to (and from) CNC machines over a network connection, as opposed to manually entering programs or loading from USB. |
| Execution State | Machine operational status. MachineMetrics uses two states: active = Machine is running/in-cycle; inactive = All other states (idle, stopped, alarm). |
| Feed Override | Adjustable setting on machine that controls feed rate (IPM) of the machine's axes. Usually 0-150%. |
| Machine Group | A logical grouping of machines for organizational and reporting purposes. |
| Program | The G-code program that runs on the machine and tells it how to perform operations. Also called Part Program, CNC Program, or Machining Program. |
| Override | Adjustable setting on machine that controls speed/feed of a tool or axis. Usually 0-150%. |
Machine Typesβ
| Type | Description |
|---|---|
| Grinder | Machine tool used for grinding, an abrasive machining process. |
| Horizontal Mill | Milling machine where the spindle axis is oriented horizontally. |
| Vertical Mill | Milling machine where the spindle axis is oriented vertically. |
| Lathe | Machine tool that rotates the workpiece about an axis of rotation to perform various operations. |
| Swiss CNC | A type of lathe designed for small, precision parts with a sliding headstock and guide bushing. |
| Stamp/Press | Machine used for stamping or forming sheet metal. |
π₯ Pages & Dashboardsβ
Dashboardβ
A unique view of company machines displayed as tiles with various options for views and data points.
| Dashboard | Description |
|---|---|
| Current Shift Dashboard | Displays current activities and details in tile view. |
| Performance Dashboard | Displays historical view of performance in card view. |
| Timelines Dashboard | Displays historical view of execution in timeline view. |
Production Order Dashboardβ
Real-time shop floor visibility interface showing machine status cards with color-coded states, active work order details, production counters, operation progress, scheduled operations queue, and machine utilization metrics.
ShopPulseβ
The operator-facing dashboard and tablet interface. Provides job selection, activity tracking, downtime categorization, part counting, and access to Max AI assistance.
Diagnosticsβ
All the data being received on an individual Machine. Shows raw data values and can be used for troubleshooting connectivity issues.
π Metricsβ
| Metric | Description | Formula |
|---|---|---|
| Performance | Compares actual production rate to ideal rate based on expected part time. | Ideal Part Time Γ· (Scheduled Time In-Cycle Γ· Scheduled Parts) |
| Availability | The ratio of time the machine was producing to the time it was scheduled to produce. | Scheduled Time In-Cycle Γ· Scheduled Time |
| MTBF (Mean Time Between Failures) | Average time between machine breakdowns. Calculated from historical downtime data to assess machine reliability. | β |
| MTTR (Mean Time To Repair) | Average time to restore a machine to operation after a failure. Key metric for maintenance effectiveness. | β |
π· Operator Dashboardβ
Last Fewβ
Display showing the cycle times of the most recent completed cycles for quick performance reference.
Parts Goal Wheelβ
Visual indicator showing progress toward expected production quantity with color coding (green/yellow/red).
Operator Runβ
A historical record of a single Operator being contiguously logged in to MachineMetrics (resets by default on Shift Change).
π° Shiftβ
Company-specific divisions of time used to contextualize data that happens within those periods.
| Term | Definition |
|---|---|
| Current Shift | The active shift at the current moment in time. |
| Previous Shift | The shift immediately preceding the Current Shift. |
| Shift Change | The transition point between one shift ending and another beginning. |
| Optional Shift | A shift period (like nights or weekends) that is excluded from OOE calculations when the facility is not normally operating. |
π€ Machine Statusβ
| Status | Indicator | Description |
|---|---|---|
| Active | π’ | Machine is actively processing parts. Execution = active, no alarms present, not in Setup activity. |
| Idle | π΅ | Machine is functioning properly but is not processing parts. Execution = inactive, no alarms present. |
| Fault | π΄ | Machine is not processing parts because of an error condition. At least one alarm of high severity is currently present. |
| Setup | π‘ | Machine is in Setup activity mode. Not technically a "status" but rather a UI representation of the Setup Activity Mode. |
| Not Reporting | βͺ | Machine is not currently reporting data to MachineMetrics. Either off or data connection is not working. |
| Never Reported | βͺ | Machine has never reported data to MachineMetrics. |
| Unavailable | βͺ | The adapter is reporting data, but the Machine on the other end is either off or otherwise not connected. |
π¨ Value Systemsβ
Alarmsβ
| Type | Description |
|---|---|
| Fault | A critical alarm requiring immediate attention that typically stops machine operation. |
| Warning | A non-critical alarm that indicates a potential issue but doesn't stop operation. |
Machine Performance Indicatorsβ
The background color of the performance section changes based on how the machine is performing against goals:
| Indicator | Color | Description |
|---|---|---|
| Goal | π’ | Machine is operating at or above the performance goal for the current shift. |
| Warning | π | Machine is operating below the performance goal but above the failure threshold. May not meet the performance goal. |
| Failure | π΄ | Machine is operating below the performance goal and below the warning threshold. Most likely will not meet its performance goal. |
| No Job | βͺ | No work order operation has been assigned/started for the shift. Used in Parts Goal and OEE views. |
Questions or Additions?β
This glossary is maintained by the Product team. For questions or suggested additions, contact product@machinemetrics.com.