This article covers common questions that new users to Seeq often have when learning about the system.
If you still have questions after reading this article, please contact Seeq at email@example.com for more information and/or clarification.
Seeq employs a three-tier architecture comprised of a browser-based (HTML5) application, application server middle tier and a NoSQL database and search engine. Data source(s) such as process historians and other manufacturing systems are connected via Seeq's Agent/Connector system.
You do not have to manage any of these tiers yourself. Seeq Server is self-contained and does not require, for example, Microsoft Internet Information Server (IIS) or Microsoft SQL Server to be installed and managed.
Our requirements, and more information about how Seeq is installed/deployed, are detailed in the Installing Seeq article in our knowledgebase.
Seeq supports most popular historian data sources, OPC-HDA, SQL databases and CSV files. You can learn more about them in the Connector Setup and Configuration article in our knowledgebase.
Seeq installs in about 5 minutes and has no significant pre-install configuration requirements. Once installed, Seeq automatically detects and connects to the default PI System you have on your system (all other connections are configured manually).
Upon initial connection, Seeq indexes all tags in those data sources. The indexing step takes about 20 minutes per 100,000 tags. When connected to a typical mid-size historian, Seeq can be fully operational in about 20 minutes.
Indexes are stored in Seeq's internal database. Seeq handles all management details of the database for users.
All Seeq content is stored in the Seeq internal database. Seeq handles all management details of this database.
Seeq can utilize its internal database for user authentication or it can connect to Microsoft ActiveDirectory or any other LDAP-compatible enterprise directory.
No customer data, such as historian data, asset names, or Seeq search results, are outside your network. The reasons why Seeq will transmit other information over the internet are listed below. For all of these, any transmitted data is anonymized and you have complete control over this via the Launch Seeq dialog.
Seeq Server will check for updates periodically to notify you if an update is available. You can choose whether or not to update.
Through an interactive process you can push log files to Seeq to help address a problem.
Seeq, at your option, sends usage telemetry for research purposes. We use this to improve Seeq and would appreciate your participation in this valuable feedback mechanism. If you wish to withdraw participation, check out this article.
Seeq uses subscription-based licenses that are locked to the machine where the server resides.
Seeq SaaS allows us to provide both best-in-class security, but we can take full advantage of the reliability and scalability features that cloud computing provide. This article discusses these opportunities in more detail.
While it’s true that support for Seeq on Microsoft Windows servers is ending after feature release R58, the capabilities of Seeq will only increase as we adopt our Cloud Native architecture.