Glossary

AAA (A3) is the Authentication & Authorization Service provided by OS1 Platform.

An address is a set of human-readable information used for identifying a place like a building, apartment, facility, warehouse, etc.

A web/mobile software that allows an authenticated user to interact with business processes/services by performing actions on backend resources. The app consists of App UI and/or App Backend Service.

The process of confirming the identity of a User.

The process of confirming the permissions granted to a User for taking action on App/OS1 Platform resources.

Clients are the business entities on the platform responsible for originating orders.

The person sending a shipment to be delivered to a consignee.

A container is a physical component with a unique ID. It is the smallest entity unit to represent a shipment.

The Core APIs form the most basic set of libraries and APIs that allow anyone to build business-specific apps on top of them.

The services that are available as a part of the OS1 Platform (For example - Participant Service, Secure Data Service, Container Service, Workflow Service, Dispatch Service, etc.).

Custody is an implicit mechanism to keep a ledger of what inventory (physical objects) are in the custody of an operator for a given dispatch.

A consignee is someone waiting somewhere for goods or services.

One of three main dimensions (the others being length and width) for an object. Height is measured from the base of an object to the top.

One of three main dimensions for a shipment (the others being width and height.) Length is typically the longest dimension and is measured from one end of the shipment to the other.

The horizontal distance between the edges of a package or other packaging or object. In contrast, height is the measure of the vertical distance from the bottom of the object to the top.

Dispatch is a manifestation of the intent to move an operator/service provider from or to a location or multiple locations in order to perform a unit of action called to task or a set of tasks.

An internal or external individual who can assign operators and vehicles to deliver a set of packages.

An event is an individual action performed on the entity object either by a user, app, or system. It is an immutable record of a fact that happened during the lifecycle of the entity object. An event may or may not cause the system to change the state of the entity object.

An event code is a unique alphanumeric code given to an event. Each event code represents a unique event. A particular Event Code can be associated with only one type of entity.

The event sourcing component is an event-based framework to ensure every change to the state of an application is captured in an event object, and that these event objects are themselves stored in the sequence they were applied for the same lifetime as the application state itself.

An execution task is the smallest atomic task that is performed by an operator. The execution task will have a binary outcome, i.e., it can either succeed or fail. Note that an ET can’t be canceled; only the ET workflow or objective can be canceled.

An expected path is a route for the movement of the participant/shipment for fulfilling an order.

The person performing a delivery.

A dispatch represents movement and is the generic construct for representing the movement of resources. The generic dispatcher is a set of instructions created in the form of tasks that will be fulfilled by an operator using the generic field app. What makes it generic is that the dispatcher is purely instructions-driven and is not tied to any leg of delivery (last mile, first mile, etc); nor does it have any particular understanding of the task.

The sequence of workflows to be executed for completing a single leg of the expected path of an order (point to point).

Last-mile delivery is the movement of goods from a transportation hub to their final delivery destination, whether a residential or commercial address.

A freight shipment that does not meet the specifications required for a Full Truckload (TL) shipment. LTL shipments are typically aggregated with other movements to maximize trailer utilization.

An address with corresponding geographical coordinates. Each Service has one or more locations to be visited in order. Example: Pickup location/Delivery location/Return location.

One or more execution tasks to be performed as a workflow for a Container or set of Containers at a given location. Eg: Pick, Drop, KYC, Installation, etc.

Onboards resources (users, vehicles, devices, facilities) and use them to complete a task.

An order is a set of instructions from the originator to complete a task/set of tasks. These tasks can be executed by one or more service providers as per the contract. \n\nA task can be physical or digital in nature. If we are performing the moving of a shipment from a consignor to a consignee then it’s a physical task. Whereas, verifying an address is a digital task.

The smallest unit is tracked in the lifecycle of a shipment. Has both a human and machine-readable label and resolves to a know package ID in the platform.

A Participant is an organization or individual connected to the platform for the purpose of performing any activity on the platform and is governed by the platform rules.

Permission represents a named action allowed on a resource.

A user attribute (designation, department, etc.) and/or environment (mobile, web, time, etc.) based rule that defines whether a Role can be dynamically granted or denied to a user.

There can be more than one reason which can trigger an event. Reason Code is a unique alphanumeric code given to a reason that triggers an event. It provides additional information/context about the event that has occurred.

A resource represents an entity and the possible actions on the entity through the REST API.

A named set of permissions that can be granted to enable a user or app/service to perform a set of actions in an app.

A shipment is a set of one or more containers to be moved from a consignor (originator of the order) to a consignee (terminal point of order).

The state defines the current status/behavior of an entity object. An object entity undergoes various transitions of states as events are raised on them. States are devoid of any data/information related to the events that were raised on the entity object. At any given point in time, an entity object can be in only one state.

Templatization implements a concept where certain attributes take default predefined values based on a category and subcategory defined during participant type creation or updated on the participant type whenever a requirement for it arises.

A Tenant represents a group of users that have access to a specified set of resources. It is a type of Participant on the OS1 Platform that can create and govern custom usage of their Platform instance for their participants by configuring workflows and business models.

Anyone who uses apps to take actions on Platform entities.

A namespace for a set of users grouped together by a common attribute or purpose.