Reference · built on requestConnectorPLC, SCADA & MES

MachineMetrics

Machine states, alarms, downtime annotations, and production rollups from MachineMetrics through its GraphQL and REST APIs.

Request accessPricing ↗

About

MachineMetrics is machine monitoring for discrete manufacturing. Its edge software sends machine data, states such as execution and alarms, part counts, and quantities like load and feed rate, to the MachineMetrics cloud, where it is immutable. An operational layer adds production runs, operator runs, downtime annotations, rejects, and work schedule events. The GraphQL API at https://api.machinemetrics.com/graphql reads all of it; the REST API returns production and quality rollups and accepts jobs and schedule events.

Through Fibric, an operator watches machines in downtime and their open annotations, reads utilization and downtime rollups, and proposes a job import or a work schedule event. You approve. Each write is sent once and leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from MachineMetrics and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Machines with currentStates such as MasterExecution and currentAlarms with startAt, nativeCode, label, and description
  • Downtime annotations with annotationType, startAt, and endAt, filterable to those still open
  • Production rollups such as utilizationRate for a startDay to endDay window through POST /reports/production
  • Rejects grouped by reason, machine, shift, or operation through the Quality report endpoints
  • Scheduled time for a machine during a time window
  • Work schedule event definitions and their assignments

Proposed actions

  • Target capability: propose importing jobs from a file through POST /jobs/import
  • Target capability: propose a work schedule event definition through POST /work-schedules/events and its assignments

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Categorize a downtime that nobody annotated

    Machines whose annotations have no endAt are read every few minutes with their alarms and execution state. The operator drafts a downtime reason for the supervisor and files the alarm codes it saw.

    With Line Downtime, OEE Loss

  • Watch scrap climb on one operation

    Quality rollups by operation are read each shift. When rejects for one operation rise against its recent pattern, the operator proposes a review and lists the reject reasons behind it.

    With Scrap Rate, Quality Hold

  • Load tomorrow's jobs from the ERP

    Jobs due next shift are drafted into the import file format. The operator shows you the list before calling POST /jobs/import, and the receipt records which jobs were created.

    With Backlog Priority, Changeover Plan

Requirements

  • A MachineMetrics company account and an API Key created for that company with the scopes each endpoint lists
  • The reporting scope for GraphQL queries and the Production Reporting endpoints; write endpoints need other scopes
  • A separate key per integration, as MachineMetrics recommends, so rate limiting on one does not affect another
Authentication
An API Key created at app.machinemetrics.com under Settings, API Keys, sent as a Bearer token in the Authorization header; keys carry scopes, and GraphQL queries need only the reporting scope.

Limits

  • GraphQL is read-only and limited to 1000 requests per minute per company
  • Queries are bounded to a depth of 5 and 5 nodes, and must finish within 10 seconds
  • A key found to be abused may be disabled temporarily or permanently
  • Machine data is immutable once ingested; only the operational layer can be changed

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request MachineMetrics ↗

Questions and answers

Can Fibric change data in MachineMetrics through GraphQL?
No. The GraphQL API is read-only. Writes go through REST endpoints such as POST /jobs/import and the work schedule event endpoints, each requiring its own API Key scope.
What limits apply to GraphQL queries?
A sliding-window rate limit of 1000 requests per minute per company, a depth limit of 5, a node limit of 5, and a time limit of 10 seconds per operation. A request that exceeds any one of them is denied.
Does MachineMetrics send webhooks?
Yes, through workflows configured in MachineMetrics. Webhooks send data to other web applications, for example alerts to Microsoft Teams or Slack, or a CMMS. Example payloads are documented on the developer site.
Ask about MachineMetrics

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with MachineMetrics through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy