The Aranda Field Service (AFLS) Cloud architecture diagram provides a view of how the product is deployed in the cloud, using the Microsoft Azure platform.
In this modality, the management layer is composed of application servers, services, storage accounts and databases that are deployed in the Aranda cloud, this eliminates the need for its own infrastructure by the customer, who only needs to enter the management layer from the devices assigned to the administrators. monitors and dispatchers who are responsible for setting up and supporting the AFLS website cross-country specialists.
Field specialists must download the mobile application on the devices to perform the management and completion of work orders.
AFLS leverages Azure’s robust infrastructure to optimize the operation of field services with a timely assignment of work orders, improving care response times, having real-time access to specialists’ information.
The Aranda Field Service architecture is an application distributed in the following components:
Aranda Push Gateway Central 
Manage the push notification service, technology that apps use to send messages to users.
Customers 
Person or company that acquires the services configured by a company, for the management of work orders with AFLS. Taking into account the role assigned to the customer, they are allowed to access the Web console or the AssistMe console from the Browser, they can make requests through the available APIs or they can access the mobile console on Android or iOS. Note: The customer must publish the services to the internet.
Database Server 
A server that uses a database application and provides database services to other computer programs or computers, as defined by the client-server model.
Federated Identity (SAML) 
It allows you to delegate user authentication to a third-party provider, improving the user experience in your application.
Firewall 
A security barrier that controls network traffic, allowing or blocking access to a computer network according to predefined rules to prevent unauthorized access and protect against threats.
LDAP Server 
Allows you to store and retrieve information about users, groups, or objects on an active directory server. Note: The server port may vary depending on the client’s configuration.
Mail Server 
It is a server used to receive, send, and manage emails.
Note: The server port may vary depending on the client’s configuration.
Microsoft Azure
A pool of resources where Aranda products and services are hosted in the Azure cloud. Port: It is an interface through which different types of data can be sent and received.
Server
It is a computer that allows you to process information and programs. They are designed to support heavier workloads and/or be always available for users to access their resources, be it software, data, etc. On the server we have the deployment of the AFLS Web console, the AssistMe client console and the AFLS APIs, the installation of the services is also carried out.
Windows Services 
It is a computer program that works in the background. We have four important services:
| Service | Description |
|---|---|
| Aranda AFLS AssignmentEngine Services | The AFLS assignment engine resembles the operation of a neural network, where it has inputs with initial weights which are decisive when choosing the best specialist to attend to a work order. The relationship of the incoming parameters in the mapping engine is: - Execution time for each work order (DmCost) - Position in coordinates (DmDistance) - List of skills required for the service (DmSkill) - Work Order Attention Time Limit (DmSLA) - Distribution of the order of care to support work orders by specialists (DmDistribution) Note: Port 1605 is used |
| Aranda License Windows Services | Administrator and validator of licenses for Aranda applications. There can only be a single licensing service running on the server |
| Aranda Worker Windows Services | Scheduled task executor. Tasks are specific actions that must be performed, some scheduled or at the time of making some AFLS configuration are in table AFW_TASKS (Start with id 34), those that require programming are displayed in the AFW_SCHEDULER table with a specific frequency, execution time of the same, date of last execution and date of next execution. How the process works between Scheduler and Worker: - Scheduler: Schedule and send tasks to the Worker. - Worker: Executes and leaves execution traces in AFW_WORKER_LOG. Note: The Worker has the ability to queue requests since multiple tasks can be sent and executed at the same time. |