|
|
Process Layout is a graphical overview diagram composed of production or logistics processes based on defined relationships in the Model. It is a starting point for most of the navigation in the platform and for many users it will act as their home page. A platform can have multiple Process Layout diagrams that focus on different areas of a plant.
|
|
|
A scanable code that is system generated for any object in the model. A printed QR code label can be scanned to automatically navigate the user to a specific page in the portal for information about an object.
|
|
|
A quantity kind is a representation of all the properties that can be measured with the same kind (type) of measurement unit. For example, the quantity kind length can be measured using centimeters, inches, yards, miles, etc.
|
|
|
A detailed report on how the Feed Chain determined that materials flowed from material account A to material account B, when the material stops flowing; why it was determined to have stopped flowing by drawing attention to the pieces of equipment that stopped the flow, etc. The reasoning is displayed in the Material Flow Diagram.
|
|
|
Relationships in the Model are used to enhance understanding of the manufacturing process in a few ways: what equipment is involved how materials flow through the equipment, and how other resources or materials ,such as energy, are consumed by the processes. Relationships help create a graphical view of the process. The Process Flow diagrams and Material Flow diagrams illustrate the relationships between equipment instances and material within the plant.
Relationships are built upon semantic triples, also known as triplets or three-part statements. They are a way of representing information in a structured and logical manner. They consist of a subject, predicate, and object, and are used to express relationships between entities and the properties that define them. Storing data in this manner makes creating a graphical representation of the data a natural outcome.
In the platform, standard relationship types are 'Can Feed', 'Can Produce' and 'Can Consume'. These types are provided by the ThinkIQ Base Library.
|
|
|
A subset of data; queried using arguments such as resolution and number of data points. Gateways typically sample all data from a historian, however, ThinkIQ UIs and processes may often query for a smaller sample of the data.
|
|
|
A script created in the IDE that is scheduled using the Script Scheduler and executed by the Script Execution engine.
|
|
|
A daemon that executes the scheduled scripts defined/located in the Script Engine. Executes on the same web host as the customer site.
|
|
|
Executable code that can be written in the Mini IDE. Scripts can leverage existing templates and have several output types such as headless, browser, class and display scripts. The platform supports scripts written in Php, Python and SQL.
|
|
|
Feature that allows per-customer and unique attributes to be defined, calculated and stored / displayed. The calculations can run periodically or upon request, and can be stored back into, for example, a model created by the model editor.
|
