On the Nektar platform, a task is a record that collects data for a specific action or event. Every task is linked to a specific asset.
Users create task definitions to define the type of information task records will collect. Because task definitions are easy to customize, the structure of a task can closely match your existing processes and functions.
Example of the link between tasks and assets
A construction site operates a vehicle yard with a bulk storage fuel tank. The fuel tank is registered as an asset on the Nektar platform. Each time a fuel supplier fills the tank, a yard worker records a new task against that asset. In addition to recording task data (e.g. date and time, supply company, the volume of fuel, etc.), the completed task can dynamically update an asset element that displays the fuel volume in the tank (if a system user enabled that dynamic connection in the task definition).
Task data include:
A task name and description.
An operation (a tool to group similar task definitions).
Individual task elements organized into sections.
The user who recorded the task.
The date and time a task was recorded.
Location data to display in maps or GIS systems.