Entities

An entity can be a serialized component, a batch of items, a custom made product, a service task or even an entire purchase order. It is entirely up to the creator what the entity must represent. You can think of the entity as a box where users can add and retrieve information describing the entity itself, its state or physical position.

Generally, entities have three modes; single, batch and order:

• Single: a uniquely identifiable product or service where the quantity is strictly one
• Batch: a uniquely identifiable batch of products or services where the quantity is higher than one
• Order: any combination of singles or batches where each entry is uniquely identifiable. Order entries may have individual Due Dates

Entity identifiers (ID)
Prescience uses identifiers to distinguish between entities within the workspace. You can assign one or more custom identifiers to each entity. This is useful if your products or services already have unique ID's that are a part of your daily routine. Additionally, Prescience assigns a unique ID to each new entity within the workspace, to ensure there is at least one globally unique identifier for each entity (key = workspace + identifier). The mobile application enables users to locate entities using QR-codes, NFC-chips and traditional bar-codes.

Entity due date
The entity "due date" is the key planning parameter to describe when an entity must change state from "in progres" to "completed". If an entity does not have a due date users may suffer from reduced functionality as Prescience cannot trigger risks and alerts. The "new agreed due date" can be used to override the due date for all statistics and alerts.

Entity item number
The entity "item number" is the main reference for information describing the entity. The item number must be unique within the workspace/organization and can be configured to include;

• Descriptive information; item description, item category, etc.
• Dimensional information; weight, height, length, depth, diameter, etc.
• Unlimited custom attributes
• Attachments and files; Bill-of-material, drawings, specifications and instructions

Entity location
The entity location is the main positional reference. Entities can have connections to locations specified by organizations and partners to represent factories, warehouses or storage facilities. With the mobile app it is possible to provide exact location coordinates using the device GPS. Similarly dashboard users can easily associated the entity location with a pin in Google maps.

Creating an entity
Creating an entity should be fast and simple, this is why Prescience can create entities with no information from the user. However, to enable the fundamental functionality we recommend that at least ID and Due Date is specified. Similarly item number and location provides useful information to users. Aside from this Prescience aims to keep the entity creation process as lean as possible, only prompting users where options exist. See guides explaining how to create entities:

• Via App
• On Dashboard
• Through API