Basic Concepts of OrigoTracker Sequi
1. Basic Concept
Before using OrigoTracker Sequi to perform data acquisition, you need to understand the following concepts
| Concept | Description |
|---|---|
| Module | A module refers to the processing stages a product goes through during its generation, which you can think of as workshops. For example, if a product needs to be processed first in Module A (Workshop A) and then in Module B (Workshop B) to become a complete product, then A and B are modules. |
| Production Line | Production lines under a module (workshop). For example, if there are three press machines in a molding workshop performing the same production steps, then each of these three press machine constitutes a separate production line. |
| Production Process | The complete production process of a product refers to the sequence of production modules (workshops) that the product must pass through as it transforms from raw materials into a finished item. These modules, arranged in order, form the product’s manufacturing workflow. For example, if Product A requires processing first in Module (Workshop) A and then in Module (Workshop) B to become a complete product, its production process is defined as A → B. |
| Product Type | Model number of a product |
| Product Unique Code | The product unique code, such as serial number or batch number, generated during the product manufacturing process， is similar to an ID card number. It should be uniquely identifiable. Please note: in OrigoTracker Sequi, the system defaults to including batch number information in the product code, while the entire product code itself is a unique identifier. |
| Equipment Type | Equipment type is related to PLC protocols. For example: among 10 equipment, there are 8 press machines and 2 ovens. Out of the 8 press machines, 3 of them use PLCs with Protocol A, while the others use Protocol B. Both ovens use PLCs with Protocol A. Therefore, Equipment Types are: Press with Protocol A, Press with Protocol B, and Oven with Protocol A. |
| Equipment Instance | An equipment instance represents an individual physical equipment, used by the system to locate the specific equipment when collecting data from it. |
| OPC-UA Connection | A connection based on OPCUA protocol，can be used for the communication with KEP Server |
| Tag | It is an alias for a PLC address. For example, the PLC address DB2.0 is used to store real-time pressure data. We can assign an alias to this address, such as "Pressure," to make it easier for users to remember. The term "Pressure" is a tag in this example. |
| KEP Server | A software developed by PTC，which is used to retrieve data from PLC |
| Automatic Retrieval of KEP Server Tags | By leveraging the KepServer API, a single click retrieves pre-configured tag information directly from KepServer, eliminating redundant manual tag definitions and reducing repetitive work. |
| Simple Connector | It is a subsystem for managing PLC tags and performing data acquisition/monitoring. It supports multiple PLC protocols and allows PLC tag configuration, display, and testing on a single page. |