Reference · built on requestConnectorPLC, SCADA & MES

Sight Machine

Machine cycles, downtimes, parts, line data, and KPIs from Sight Machine through its Python SDK, Dashboard API, and ODBC access.

Request accessPricing ↗

About

Sight Machine is a manufacturing data platform. FactoryTX collects machine and enterprise data at the edge and sends it to a tenant at <tenant>.sightmachine.io, where it is modeled as machine types, machines, cycles, parts, downtimes, lines, and KPIs such as OEE, availability, and quality. Sight Machine documents three ways to read it back: the sightmachine-sdk Python client, a Dashboard API, and ODBC access to a PostgreSQL database.

Through Fibric, an operator reads cycles, downtimes, and KPI series for chosen machines on a schedule and raises what it finds: a downtime reason that keeps recurring, a KPI drifting from its own baseline, or a machine that has gone quiet. It proposes a note, a ticket, or a work order in an adjacent system. This connector reads only.

This is a reference listing. It documents what Fibric would read from Sight Machine 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

  • Machine types, machines, their fields, and lines through get_machine_types, get_machines, get_machine_schema, and get_lines
  • Cycle records per machine through get_cycles, filtered by Start Time and End Time and by any tag with __in, __gte, or __exists
  • Downtime events with Machine, Start Time, End Time, Duration, Shift, Downtime Reason, Downtime Category, and Downtime Type through get_downtimes
  • Part records through get_parts and get_part_schema
  • KPIs such as quality, oee, and availability through get_kpis, get_kpis_for_asset, and get_kpi_data_viz
  • Line data spanning the machines of a line through get_line_data and get_line_data_lineviz
  • Dashboard widget values through GET {environment_name}.sightmachine.io/v1/obj/dashboard/{dashboard_id}/full_values

Proposed actions

Read-only. Actions need a separate connector.

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

What you can build

  • Rank downtime reasons per shift

    get_downtimes runs for each machine on a line, grouped by Downtime Reason and Shift. The operator drafts a shift summary of the longest stops and proposes a note for the supervisor.

    With Line Downtime

  • Catch OEE drift before the weekly review

    get_kpi_data_viz returns oee, availability, and quality per machine over time. The operator flags machines below their own trailing baseline and attaches the series it read.

    With OEE Loss, KPI Drift

  • Turn a repeating fault into a work order

    The same Downtime Reason recurring on one machine becomes a proposed work order in your maintenance system, with the cycle and downtime rows as evidence.

    With Predictive Maintenance

  • Watch a dashboard number without a browser

    A Single Value widget with background loading is read through full_values. When the value leaves its expected range, the operator proposes a notice to the people who own it.

    With Anomaly Notice

Requirements

  • A Sight Machine tenant at <tenant>.sightmachine.io and an API Key and Secret from the Security section of a User Profile
  • For the Dashboard API, widgets set to background loading; only Data Visualization and Single Value widgets are supported
  • For ODBC access, a PostgreSQL client reaching port 5432, database tenant_storage, schema sightmachine
  • For the SDK path, Python with smsdk installed from the sightmachine-sdk GitHub repository
Authentication
An API Key and Secret created on your User Profile page, sent as the X-SM-API-Key-Id and X-SM-API-Secret headers, passed to the SDK's apikey login, or used as the ODBC username and password.

Limits

  • The public documentation shows no write endpoint; this listing is read-only and proposes actions in adjacent systems
  • SDK queries default to 5000 rows and the first 50 fields; Sight Machine warns that values over 5000 may lead to timeouts
  • Full API documentation is in-product at {environment}.sightmachine.io/#/api-docs after an API Key exists, not on the public docs site
  • The production ODBC schema can change as workspaces are published; each deployed workspace has its own schema named workspace_ plus its ID

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 Sight Machine ↗

Questions and answers

How does authentication work?
Create an API Key on your User Profile page under Security; Sight Machine returns a key and a secret. Send them as X-SM-API-Key-Id and X-SM-API-Secret headers, pass them to cli.login('apikey', secret_id=..., key_id=...) in the SDK, or use them as username and password over ODBC.
Can Fibric write to Sight Machine?
No. The documented paths, SDK, Dashboard API, and ODBC, retrieve data. FactoryTX pushes data into Sight Machine from edge sources but is not a write API for applications. Operators using this connector propose actions in other connected systems.
What does a downtime record contain?
By default get_downtimes returns Machine, Start Time, End Time, Duration, Shift, Downtime Reason, Downtime Category, and Downtime Type for one machine. In the Downtimes application, active stops update their Duration and End Time every 10 to 20 seconds.
Ask about Sight Machine

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 Sight Machine 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