system:inmation is made up of objects (classes) that each perform functions within the system. The table below lists the available objects and their description, for more information for each individual object click on the respective link.
|Action items are used to carry out actions when other objects trigger certain events.
|Advanced trend class.
|X-Axis for an Advanced Trend Pen.
|Y-Axis for an Advanced Trend Pen.
|Generates A&E events from numerical data.
|Use alias items to expose items from the I/O Model with a different name.
|Area of a plant.
|An asset is a durable good which can only be partially consumed or input as a factor of production (like a cement mixer) which can only be partially used up in production.
|Publishes S88 batch production records of its parent equipment object.
|Definition of the Batch Equipment Phases.
|Definition of the Batch Equipment Steps.
|Definition of the Batch Operation.
|Real time batch tracker. The object reads and converts an arbitrary number of object values and transforms the data into a S88-compliant data structure which can be obtained in form of a JSON document.
|Control object for the BatchTracker backfill operation.
|Allows users and external systems to access the entire system address space, which may consist of multiple Core and Cache services.
|The inmation Cache Server works as an auto-prioritizing in-memory buffer for historical data (raw time series, aggregates, events etc.). Cache Servers are indirectly accessed through Broker Servers, when user requests are executed.
|A graphical representation of data, in which the data is represented by symbols, such as bars in a bar chart, lines in a line chart, or slices in a pie chart.
|Inserts text based data into a cloud storage system.
|A connector holds all necessary information for the communication with his underlaying endpoints.
|Each core can have individual parameter settings like host name, ip-address or location.
|An instance of a core service running on a host.
|User-defined data store for Big Table data.
|A userdefined data store for selected events.
|The userdefined data store for files.
|User-defined data store for Batch Production Records.
|A custom data store containing numerical time series history of particular items of the system.
|A custom data store v2 containing numerical time series history of particular items of the system.
|Catches SQL events raised by other objects and delegates the execution to a DatabaseSink object.
|Manages the infrastructure of DBDispatcher and DBSink objects in a system in order to route SQL commands from source to sink.
|Executes SQL commands against an external RDBMS.
|Distributed Control System.
|Data Document (Complex Data).
|Can be used to organize meshed data objects in a certain hierarchical structure.
|Group data store objects together.
|Represents a distinct data source or server, which supplies an interface supported by the system.
|View lua instances.
|Events and Conditions are organized within one or more process areas. An area is a grouping of plant equipment configured by the user, typically according to areas od operator responsibility.
|Pointer to an array of vendor specific event attributes returned for this event notification.
|Standard and Vendor-specific event category codes, define groupings of events supported by an OPC Event server. Example: Process Event, System Event, Batch Event.
|The name of the condition related to the event notification. Conditions may be single state or multi-state. An alarm is merely a special case of a condition.
|similar to IONode.
|The source of the event notification can be used to determine the related Item.
|Represents a configured and optionally filtered event stream connected to an external event source.
|The name of the current sub-condition for multi-state conditions, for a single-state condition the subcondition is equal to the condition name.
|There are 3 types of events: Simple, condition-related, tracking-related. A simple event is for example a device failure. A condition-related events are associated with OPCConditions and represent transitions into or out of the states represented by OPCConditions and OPCSubconditions, i.e. a tag transitioning into an alarm condition and a HI-alarm sub-condition . Tracking-related events represent occurences which involve the interaction of an OPC Client with a target object within the OPC Event Server, i.e. A setpoint change.
|Represents a configured event tracker connected to an external event source.
|Controls feedback for external writes based on separate objects.
|Allows to monitor and read file based data in cases where the dropzone functionality is not sufficient.
|The file sink receives the files from file source and stores them into the configured storage.
|The file source processes the files from disk folder and transfers to the configured File Sink object.
|Can be used to organize objects in a certain hierarchical structure.
|Generic Items can be used for Simulation, Script-based data generation and more.
|A generic KPI object, which is automatically populated to the Web-based KPI displays.
|A persistent event buffer for data of particular items of the system, with support for custom script.
|A persistent time-series buffer for data of particular items of the system, with support for custom script.
|Supplies configuration and execution of system health monitoring.
|Manages the infrastructure of HistoryTransporter and HistorySink objects in a system in order to route historical time-series data from source to sink.
|Does a one-shot export of history data into a file.
|Inserts historical time-series data into an external Historian system.
|History transport via subscription-based protocols.
|Backfills missed events.
|Processes real-time events.
|This object should be created once in the Core in order to monitor an arbitrary number of Histrory Transfer Controller objects. It supervises the status of all involved Connectors, Datasources and Transporters. It also maintains the KPI Dashboard organisation for history transfers.
|Controls a set of History Transporter objects in browse-process fashion.
|Configuration object for Bucketed extension for History Transport Manager.
|Allows to fetch large chunks of external history.
|The Data Holder Item allows for storage of real-time data. It can be set by external OPC Clients.
|Recurring ITLog analysis, provides KPI structure and data based on acquired raw data.
|This object delivers some table properties in order to configure locations, out-of-band computer names, KPI defaults etc.
|Can be used to organize ITLog objects in a certain hierarchical structure.
|This class catches all internal generated alarms and events which are raised by AlarmGenerator objects.
|A named element acquired from an item-oriented system like an OPC UA server, or created by dropzone text imports or SQL scripts.
|Represents a group of I/O Nodes and I/O Items.
|The IO-node is a folder-type object, usually refering to a node in an external systems namespace.
|A property of an I/O-Item.
|A bookmark for Visual KPI.
|Dashboard for VisualKPI.
|Object to embed external content via URL.
|Container object which is used to organize KPI's, Charts, Tables and other groups. Groups can be nested to whatever required depth.
|Create VKPI table KPIs.
|Widget of VisualKPI dashboard.
|Holds a link to any other item with a dynamic value property.
|A representation of groupings of material definitions for a definite purpose such as manufacturing operations definition, scheduling, capability and performance. Example: Sweetener, with members of fructose, syrup and sugar.
|Properties of a material definition shall be defined as material definition properties. A material definition shall be further characterized through zero or more material definition properties.Example: density, pH factor or material strength.
|A representation of goods with similar name characteristics for the purpose of manufacturing operations definition, scheduling, capability and performance shall be shown as a material definition. Example city water, hydrochloric acid and grade B alum.
|Properties of a material definition shall be defined as material definition properties. A material definition shall be further characterized through zero or more material definition properties. Example: density, pH factor, material strength.
|A representation of a uniquely identified specific amount of material, either countable or weighable shall be named as a material lot. A material lot describes the planned or actual quantity or amount of material available, its current state, etc.
|Each material can have unique values for zero or more material lot properties, such as a specific pH value for the specific lot of material, or a specific density for the lot of material.
|A material lot may be stored in separately identifiable quantities. Each separately identifiable quantity of the same lot shall be presented as a sublot. All sublots are part of the same lot, so they have the same properties.
|A representation of the results from the execution of a quality assurance test shall be presented as a material test result. A material test result records the results from a material test for a specific material lot or material sublot.
|A representation of a material test shall be shown as a material test specification.
|Allows to configure a complete set of Master Data, required to establish the message communication between a distinct PAS-X instance, system ID and set of Basic Functions with respect to a selected set of control systems and/or devices.
|Configuration of a MessageBroker Message.
|Processes messages according to the MessageBroker configuration.
|A OPC UA TCP server instance.
|A OPC UA TCP server endpoint.
|The Parameter allows to store real-time data and historize it. It is like a Variable, but offers some additional properties, like Limits and engineering units.
|Can be used to organize meshed performance data objects in a certain hierarchical structure.
|An industrial process plant that manufactures goods or processes materials.
|A network of two or more connected plants in the immediate vicinity.
|Redundant Items are used to provide redundancy based on multiple data sources.
|This object provides for a logical event stream; consisting of multiple A&E streams supplying the same data.
|A group of services providing redundancy to the parent component.
|An inmation Relay Server can be used to bridge networks. The Relay would connect one to many connector servers over one distinct network adapter while supplying the server access port on another network interface.
|Allows to group remote service components together.
|Object to save report designs to file.
|The Report Item can use source data in form of a JSON document and render it visually according to 1 or multiple templates, which have been created with the Report Designer.
|Filter branch for rules.
|Logical grouping of Work Centers.
|Typically a collection of sensors, actuators and associated process equipment that, from the point of view of control, is operated as a single entity.
|Top-level equipment which contains Sites.
|A functional group of equipment that can carry out a finity number of specific minor processing activities.
|Properties of equipment shall be listed as equipment properties. An equipment shall have zero or more equipment properties.
|A collection of associated Control Models and / or Equipment Models.
|Equipment which performs a continuous process.
|Equipment used in batch production which contains Units.
|Equipment used in repetitive or discrete production.
|Equipment used in continuous production.
|Normaly a location based equipment level which contains Areas.
|Storage location like silos, bins and racks.
|Storage like silo parks and warehouses.
|Equipment which creates one part of the product.
|Generic equipment on Work Center level.
|Generic equipment on Work Unit level.
|Scheduler class for time-based scheduling.
|This class collects the scripts events below its hierarchical position.
|Entity which controls the connection between Lua Executing Objects and targeted system objects.
|Groups multiple Script Profiles.
|Any code executing in the objects below in the tree will have the security identity of the perimeter object, which can be used to specify security permissions.
|inmation Server services distribute data according to the OPC standard.
|Represents a property of an event type.
|A container object of event types exposed in this server.
|Represents the type of events forwarded from the core service to the server service which were originated in an external system or in a different component.
|A container object of types exposed in this server.
|Production site or operation level.
|Show and design Reports that use realtime, historical or namespace data.
|Used to store different types of credential.
|Group object to contain credentials objects.
|Multiple systems can serve as logical grouping elements for different business branches or production units.
|The not scheduled time is all time the equipment is not being used or touched for operation, maintenance, cleaning etc. Example: The equipment is not scheduled during weekends. See also: https://www.oeeindustrystandard.org/v2011/definition/definition-of-time/not-scheduled/.
|Calculates the OEE aggregation values in the corresponding branch of the ISA95 model.
|Auxiliary object of the OEE Aggregator, which performs individual OEE Aggregation scope calculations.
|OEE Availability Index.
|The object holds the detail configuration required to specify the individual monitoring strategy for a single production equipment.
|The object acts as a table container for equipment failures, which is also supposed to be the interface for operation support, e.g. for manual edits and corrections using WebStudio.
|TPM OEE Generic Index.
|OEE Performance Index.
|The tracking table to record all relevant information about the production batch in terms of TPM/OEE analytics. The main purpose is to provide results by automatic monitoring, but the table can also be used as a manual interface for modifications or manual insertions.
|OEE Quality Index.
|This object is created automatically by TPM OEE Equipment Monitor and is used to recalculate real-time OEE metrics after user changes.
|TPM OEE Time Value.
|The object contains a particular shift configuration for a certain production area. This can be an S95-area or an entire site as examples. It is notable that the OEE Monitoring will take the shift configuration into account which is positioned hierarchicaly at the nearest position in respect to the Equipment Monitor.
|The object holds the site configuration for TPM, e.g. the timezone settings.
|Stop Reason Configuration.
|During the operations time, the equipment is taken out of operation (un-scheduled). Reasons to un-schedule the equipment could be: - the product is not needed (over-capacity); - it is not allowed to run (due to Governmental regulations or contracts); - ‘Force Majeur’ (catastrophe’s outside of the company); - the equipment is ‘handed over’ to another party (e.g. R&D). See also: https://www.oeeindustrystandard.org/v2011/definition/definition-of-time/unscheduled-time/.
|Year configuration to calculate and provide TPM KPIs.
|Object to hold table data.
|Filter branch for Template Nodes.
|Supplies concise information about the time zone and daylight savings status.
|“Represents an Event Attribute Type in OPC UA namespace.
|Represents an Event Type in OPC UA namespace.
|Represents the OPC UA Server’s Server node.
|Represents a Type in OPC UA namespace.
|The Variable allows for storage of real-time data.
|Can be used to organize variable objects in a certain hierarchical structure.
|Active Directory Federation Service integration configuration.
|Web API Server Service Component.