Context Item
A context item is a record of an event in your process. It captures what happened at a specific moment or over a period of time, whether that is a process deviation, a production stage, a maintenance activity, or any other event worth recording.
Every context item belongs to a type, which determines its structure: the fields it carries, an optional workflow it follows, and how it appears in the interface. It is linked to a single component (a tag, asset, or attribute) that anchors it to the right place in your data.
A context item can originate in multiple ways: created manually by a user as a result of an analysis in TrendMiner or a direct observation, generated automatically by a monitor, or synced in from an external system.
Instant context items and context item events
A context item always relates to either a single point in time or a period with a start and an end.
Type | Description |
|---|---|
Instant context item | A single point in time. No duration. |
Context item event | A time range with a start and an end. Can have intermediate states if a workflow is configured for the type. |
An instant context item captures an event that occurs at a single point in time. It has no duration.
A context item event captures an event that unfolds over time. It has a start and an end. If the type has a workflow configured, the item can move through a series of states between start and end.
Open context items
A context item event without a completed end state is considered open.
Open items remain visible in ContextHub and on the chart. This can happen in several situations: the event is still ongoing, a monitor has detected a condition that has not yet resolved, or the item was synced in from an external system that does not always provide a closing date.
Context item structure
A context item is built from several configurable building blocks. Its type determines which fields are available and whether a workflow applies. Fields capture structured metadata. Comments, attachments, approvals, and an audit trail can be added depending on the configuration of the type.
Every context item contains the following core elements:
Element | Description |
|---|---|
Short key | A unique identifier generated automatically when the item is created. It is used to reference the item in the interface, in search, and via the API. It cannot be set or changed by users. |
Type | The context item type the item belongs to. The type determines which fields are available, whether a workflow governs the lifecycle, and how the item appears in the interface. |
Component | The tag, asset, or attribute the item is linked to. A context item is always linked to exactly one component, which anchors it to the relevant part of your process data. |
Events | The timestamped records of each workflow state transition on a context item event. Each event marks the point in time at which the item entered a particular state, such as Started, In Progress, or Completed. An instant context item has a single event with no state. A context item event always has at least a start event and an end event, with optional intermediate events for each state defined in the workflow. |
Description | A free-text field for recording observations, context, or any relevant information about the event. |
Keywords | One or more user-defined labels that can be added to an item to support search and filtering. Keywords are not typed and can be freely chosen. |
Created by | The user who created the item. Recorded automatically and not editable. For items created by a monitor or synced from an external system, the creator reflects the system origin rather than a named user. |
Comments | Free-text notes added by users after the item is created. Available on all context items. Listed in chronological order in the detail panel. |
Attachments | Files linked to the context item, such as reports, photos, or supporting documents. Available on all context items. Maximum file size is 20 MB per file. |
Approvals | Formal sign-offs added by users to confirm they have reviewed the item. Multiple users can each add their own approval. All approvals are removed when the item is edited. It is optional and must be enabled on the context item type by an admin. |
Audit trail | An immutable log of all changes made to the item, recording what changed, who made the change, and when. Accessible via the API. It is optional and must be enabled on the context item type by an admin. |
Spot | The spot, also known as a bubble, is a small circular icon found on a trendline (context item spot) that flags a context type. |
Note
Dates in TrendMiner are represented in UTC with the option to include timezone information in alignment with ISO 8601.
Context items can be created in multiple ways: manually by a user, automatically by a monitor, synced in from an external system, or imported from a CSV file. This page covers manual creation and the editing and deleting of context items. For bulk import and sync, see the dedicated pages.
To create or edit a context item, you need write permission on the context item type. To delete a context item, you need delete permission or must be the owner of the item.
Manual context items are created by a user based on a direct observation or as the result of an analysis in TrendMiner.
When creating a context item, you choose the type, the component it is linked to, and the time it covers. The type determines which fields are available and whether a workflow applies. If the type has a workflow, the item is a context item event and you set a start and end time, each linked to a workflow state.
If the type has no workflow, you choose between an instant context item at a single point in time or a context item event with a start and end.
Click Add context item.
In the Gantt chart, you can also right-click on a selected period and select Add context item. The start and end time are pre-filled based on your selection.
Select the component (tag, asset, or attribute) to link the item to. Components that are active in your current view are suggested by default.
Select a type.
The available fields and workflow are determined by the type you select.
Set the date and time.
For items with a workflow, set a time for the start state. Optionally add times for intermediate states and the end state. If you do not set an end state, the item is created as open.
For items without a workflow, set a single point in time for an instant context item, or set a start and end for a context item event.
Fill in the available fields.
Fields marked as required must be filled in before you can save. Fields marked as read-only can be filled in during creation but cannot be changed afterwards.
Click Save.
In TrendHub, select a point or a period and right-click on the chart. In the menu that appears, select Add context item.
The time is pre-filled based on your selection and can be adjusted if needed.
Select the component (tag, asset, or attribute) to link the item to.
Components that are active in your current view are suggested by default.
Select a type.
The available fields and workflow are determined by the type you select.
Set the date and time if needed. The time is pre-filled from your chart selection.
For items with a workflow, set a time for the start state. Optionally add times for intermediate states and the end state. If you do not set an end state, the item is created as open.
For items without a workflow, set a single point in time for an instant context item, or set a start and end for a context item event.
Fill in the available fields
Fields marked as required must be filled in before you can save. Fields marked as read-only can be filled in during creation but cannot be changed afterwards.
Click Save.
In TrendHub, search results can be saved directly as context items. For more information, see the TrendHub documentation on saving search results as context items.
Context items can be edited from ContextHub or from TrendHub. Open the detail panel of the item and click Edit. Make your changes and click Save.
Editing a context item removes all existing approvals on that item. If the item has an audit trail enabled, the change is recorded.
A context item can be deleted by its owner or by a user with delete permission on the type. Open the detail panel of the item, click the options menu, and select Delete. Deletion is permanent and cannot be undone.
If the item has an audit trail, the trail is deleted along with the item.
For deleting multiple items at once, see the bulk delete section.
Context items can be imported in bulk from a CSV file. This is useful for ingesting historical or ad-hoc data from external platforms such as logbook applications, OEE tools, LIMS systems, or spreadsheets. The types and workflows used in the import must already be configured in ContextHub before importing.
For the full import procedure and CSV file requirements, see the dedicated import page.
A monitor can be configured to automatically create a context item whenever a condition is detected. The type, component, and default field values are set in the monitor configuration. When the monitor triggers, a context item is created without any manual action. Fields left blank in the monitor configuration can be filled in manually afterwards by opening the item.
For more information on setting up monitors, see the monitoring documentation.