In this procedure, we will see how to make adjustments to the automatic needs generated by the system when we include workers in logistic schedules or training.

Image Removed

Image Added

1.2 Após feito o acesso, a seguinte tela aparecerá:

Image Removed

2. Identificar o trajeto utilizado pelo Drake, para gerar as necessidades logísticasOnce logged in, the following screen will be displayed:

Image Added

2 - Identify the path used by Drake to generate logistic needs.

2.1 Realizar filtro para localizar a informações de trajeto. Selecione o trajeto onde a origem seja o nome do trabalhador e clique nele.  Image RemovedFilter to find the path information. Select the path where the origin is the worker's name and click on it.

Image Added

2.2 Após clicar, aparecerá uma janela, contendo o nome e as informações do trajeto do trabalhador escolhido. Verifique as informações importantes como na imagem abaixo:

Image Removed

 2.3 Realize a validação das necessidades nas guias Ida e Volta

Image Removed

 Na aba Ida, se encontra os trechos que serão utilizadosAfter clicking, a window will appear, containing the name and information of the chosen worker's path. Check the important information as in the image below:

Image Added

 2.3 Validate the needs in the tabs Going and Return

Image Added

On the Going tab, you will find the routes that will be used.

2.4 Informações do trecho cadastrado

Para checar ou visualizar os trechos já cadastrados, basta clicar em alguns dos trechos à mostra, e a janela "Manter trecho previsto" surgirá.

Image Removed 

Image Removed

3. Cadastro de trecho

3.1 Para cadastrar um trecho, o usuário deverá acessar a tela de Cadastro > Logística > Trecho. 

Image Removed

3.2 Após isto, a seguinte tela irá aparecer:

Image Removed

3.3 Clique em Incluir para ser redirecionado para a janela de inclusão de trecho.

Image Removed

3.4 O próximo passo é o cadastro do trecho. Defina uma Descrição, o tipo de transporte, Qual a origem, o Destino e a Duração desse trecho.

Image Removed

Os campos devem ser preenchidos conforme o solicitado.

• Descrição: Representação do trecho.
  Exemplo: SDU/SBRJ - Aeroporto Santos Dumont X CGH/SBSP - Aeroporto de Congonhas.

• Tipo: Tipo de transporte que será utilizado.
  Exemplo: Transporte aéreo.

• Subtipo: Detalhamento do tipo de transporte.
  Exemplo: Premium Economy.

• Origem: Ponto inicial do trecho.
  Exemplo: SDU/SBRJ - Aeroporto Santos Dumont

• Destino: Ponto de final do trecho.
  Exemplo: SBSP - Aeroporto de Congonhas.

• Duração: Espaço de tempo previsto para realização do ponto inicial até o ponto final do trecho. É importante que o tempo de estipulado seja coerente, para que o Drake possa calcular os horários em que as necessidades logísticas serão compradas.
  Exemplo: 2 horas.

Obs: Os campos “Qualquer Origem” e “Qualquer Destino” têm uma definição diferenciada.

Image Removed

Registered routes information

To check or view the paths already registered, just click on some of the paths shown, and the "Maintain Route Parts" window will display.

Image Added

• Duration: Utilized when the time travel is different than registered.

• Reverse: When it is necessary to create the same path, with origin and destination in reverse order to set the way back.

• Recalculate duration: If informed, this path duration will be updated when the path duration be changed.

• Change time by other services: Leave this box empty when the need time is fixed, ensuring the transport won’t be changed.

• Generate Logistic: If this path generates logistic.

• Observation: Utilized to include information regarding the path. Example: Flight preferences.

3 - Routes registration

3.1 To register a Route, the user must access the Records > Logistics > Routes.

Image Added

3.2 After doing it, the following screen will appear:

Image Added

3.3 Click Add to be redirected to the route inclusion window.

Image Added

3.4 The next step is to register the routes. Define a Description, the transportation type, What is the origin, Destination and Duration of this route.

Image Added

Fields must be filled in as requested.

• Description: Representation of the route
  Example: SDU/SBRJ - SDU/SBRJ - Santos Dumont Airport X CGH/SBSP - Congonhas Airport.

• Type: Type of transport that will be used.
  Example: Air transportation.

• Subtype: Detail of the type of transport.
  Example: Premium Economy.

• Origin: Starting point of the route.
  Example: SDU/SBRJ - Santos Dumont Airport

• Destination: End point of the route
  Example: SBSP - Congonhas Airport.

• Duração: Expected time for the completion of the starting point to the final point of the route. It is important that the stipulated time is consistent so that Drake can calculate the times when the logistic needs will be purchased. Example: 2 hours.

Note: The fields "Any Origin" and "Any Destination" have a different definition.

• Any Origin: It means that in the proximity of the origin, it does not need to be exactly in the place specified in the origin, it is possible to use the route. If the field is marked, Drake understands that the origin does not have a fixed point and logistics can happen in any origin, within the limit established in the optimizer.
  

• Any Destination: It means that in the proximity of the destination, it does not need to be exactly in the specified location in the destination, it is possible to use the route. If the field is marked, Drake understands that the destination does not have a fixed point and logistics can happen in any origin, within the limit established in the optimizer.