Associated Platforms Architecture in Urbantz – URBANTZ | SUPPORT

Info This article overviews the architecture of Associated Platforms and its main characteristics.

Terminology:

Owner: The platform creating the tasks.
Carrier: Platforms that can receive tasks from the Owner and are responsible for executing them.

The Associated Platforms Architecture in Urbantz:

Main characteristics:

The Owner and the Carriers are platforms that work together and all use the same application: Platform portal.

In this case, Carrier Platforms are associated with the Owner Platform.

The owner can work with multiple carriers. To do so, the Owner can set some rules to associate tasks with other platforms. This operation is optional and the carrier can be changed at any moment as long as the task is not in a round.

The Owner can create rounds and assign them to Carriers. The Carrier can configure the fleet of drivers to assign to the rounds received from the Owner.

Another possibility is that the carrier creates the rounds. As the tasks are assigned to the hub of the owner, the current requirement is that all the tasks of the round belong to the same owner.


Announcement	It is done in the Platform portal and the tasks can be associated with another platform or not.
Re-allocation of tasks	it is possible to change the carrier as long as the task is not in a round
Hubs	The hubs are created in the Owner
Notifications	They need to be configured only in the Owner
Branding	It needs to be configured in the Owner Platform
Webhooks	Webhooks can be configured in the Owner and the Carrier.
Optimization	The Owner can decide to create rounds or let the carrier do it
Fleet and rounds	The Owner can have a fleet and perform rounds.
New features	All the new features developed in Urbantz are available for both Owner and Carrier, but structured data is not shared (labels, failure reasons, etc...)
Carrier rounds	The Carrier can have rounds for only one Owner (in the mid-term it will be possible to mix)
Task configuration	The Owner can configure all the tasks properties of the task.
Time slots	The Owner can create scheduling flows, define time slots, and schedule tasks. Carriers can't create time slots.

Important Considerations:

- All platforms use the same application (Platform portal) in this architecture.

- The Owner has more control over task properties and time slots compared to the Sender Platform architecture.- This architecture allows for more flexibility in task assignment and management between Owner and Carriers.

This architecture is well-suited for organizations that need closer integration and shared functionality between Owner and Carrier platforms while maintaining the ability to work with multiple carriers.

Urbantz analyzes each customer's unique requirements to recommend the most suitable architecture type for their specific business needs.