Reference · built on requestConnectorPLC, SCADA & MES

Seeq

Signals, conditions, capsules, scalars, and workbooks from Seeq through its REST API and the SPy Python module.

Request accessPricing ↗

About

Seeq is process analytics software that sits on top of plant historians and other time-series sources. Everything the Seeq web application does goes through the Seeq Server REST API, so any data or analytic visible in Workbench or Organizer can be reached the same way. Seeq derives server SDKs for Python, Java, and C# from that API, and the SPy module adds spy.search, spy.pull, and spy.push for signals, conditions, scalars, asset trees, and workbooks.

Through Fibric, an operator pulls conditions and their capsules on a schedule, watches for new or uncertain capsules, and proposes what follows: a pushed condition, a calculated item, or a task for an engineer. You approve. Each push is made 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 Seeq 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

  • Signals, conditions, and scalars found by spy.search on properties such as Name, Type, and Datasource
  • Signal samples interpolated onto a grid, 15 minutes by default, through spy.pull with start and end
  • Capsules with Capsule Start, Capsule End, and Capsule Is Uncertain for any condition, pulled with shape set to capsules
  • Calculated results by passing a Seeq Formula in the calculation argument of spy.pull
  • Workbooks and worksheets exported through spy.workbooks, and asset trees through spy.assets
  • Scheduled job runs and their state through spy.jobs

Proposed actions

  • Target capability: propose pushing a condition with capsules and capsule properties through spy.push
  • Target capability: propose pushing a calculated signal, condition, or scalar defined by a Seeq Formula
  • Target capability: propose archiving an item through spy.archive
  • Target capability: propose an email to named recipients through spy.notifications

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

What you can build

  • Turn a capsule into a maintenance request

    A condition such as high bearing temperature closes a capsule. The operator pulls the capsule and the signals under it, drafts a work request with the evidence, and waits for your approval.

    With Predictive Maintenance, Inspection Due

  • Watch a golden batch drift

    Deviation conditions are pulled each shift. The operator compares this batch's capsules with the reference profile, lists where they diverge, and proposes a review note in the workbook.

    With Batch Deviation, Cycle Drift

  • Flag capsules still marked uncertain

    Capsule Is Uncertain marks capsules that may change when new data arrives. The operator holds any downstream proposal until the capsule settles and tells you why it waited.

    With Data Freshness

Requirements

  • A Seeq Server URL and a user account, or an Access Key created from that user's profile in Seeq
  • An SDK whose MAJOR version matches the server's API Reference version; R66.14.2 pairs with SDK 66.14.2
  • The x-sq-csrf token on requests when Seeq returns one in headers or cookies
  • Network reach to the Seeq Server; SPy honors HTTP_PROXY and HTTPS_PROXY or an explicit proxy argument
Authentication
A session token from POST /auth/login returned in the x-sq-auth header, obtained with a username, password, and directory, or with an Access Key and its password when Seeq uses OAuth 2 or Windows Authentication.

Limits

  • Session tokens expire after inactivity; the timeout is the user's sessionDuration field
  • Items pushed by spy.push are scoped to one workbook by default; workbook=None makes them global
  • Seeq keeps public functions under a deprecation flag for at least one year; breaking SDK changes raise the MAJOR version
  • The MATLAB SDK is not derived from the REST API and covers only a small subset of functions

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 Seeq ↗

Questions and answers

Is the Seeq REST API documented publicly?
It is documented inside each Seeq Server. Open the Help Center from the hamburger menu and select API Reference; each endpoint shows its response JSON, parameters, and result codes, and can be executed as the current user.
How does Fibric get data out of Seeq?
Through spy.pull with a start and end. Signals return one column each on a grid, 15 minutes by default. Conditions return capsules with Capsule Start and Capsule End. A Seeq Formula in the calculation argument applies a calculation before the data is returned.
Does Fibric write into the plant historian through Seeq?
No. spy.push writes signal samples, capsules, scalars, metadata, and calculated items into Seeq itself. The documentation does not describe writing to an existing external datasource.
Ask about Seeq

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 Seeq 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