From wiki.ginstr.com
Jump to: navigation, search

Recording the master data

Before you begin to record the master data described in more detail below, you should ensure the following conditions are met:

  • Procurement of the required number of NFC tags for
    • the mobile {{{customerType}}}s (NFC company badge)
    • the {{{dataLevel3}}}s to be serviced and related {{{industry}}} tours
  • Procurement of the pictograms for indicating on the phones
    • the services to be provided for each {{{dataLevel3}}}
    • the potential ‘special incidents’

Providing data by uploading a CSV or Excel file

Importing data

All the master data in the office software can be created by uploading a CSV file or an Excel xlsx file.

Details can be found here.

Create CSV / Excel sample files

To make the processing of existing data in Excel or CSV as easy as possible, we recommend you first export the empty tables as an Excel or CSV file as follows:

  1. Right-click anywhere in the table header
  2. Select the ‘Download data’ option and then download either as an Excel file or a CSV file
  3. Select the other details of the download and download the file
  4. You then receive a file with the correct column headers but which is otherwise empty.

You can find more details on export data here.

You can use these column headers to prepare the existing data for ginstr web. Column headers must not be changed as this would make the data unusable.

Please speak to the ginstr support team in case you need to change the column headers.

In a future version of the application, you will also have the option to customise column headers yourself to suit your needs.

Option to download data to Excel file

Employees table

The ‘Employees’ table is used to manage

  • all of the employees provided with the {{{appName}}}© app for use on a smartphone
  • all of the {{{dataLevel1}}} managers, including their contact details such as their e-mail address and phone number
Example of 'Employees' table

The table contains the following columns (fields marked with an asterisk* are mandatory):

first name*
In this field, enter the employee’s first name
last name*
In this field, enter the employee’s last name
NFC tag id
In this field, enter the tag ID of the employee’s NFC tag (company badge). This tag ID is subsequently used to identify the employee in the Android software.
Alternatively, a custom text string can be written to the NFC tag instead of the NFC tag number (see here for more details)
  • If text content is written to the employee’s NFC tag, this text content must be entered as the NFC tag id instead of the serial number of the NFC tag.
  • If no text content is written to the employee’s NFC tag, the serial number of the NFC tag should be entered as the NFC tag id.
An NFC tag ID can be assigned to only one employee. If you attempt to assign the same NFC tag ID to more than one employee, an error message is displayed.
employee no.*
In this field, enter the employee’s employee number. An employee number must not be used more than once. Please ensure that you use unique employee numbers.
e-mail
In this field, enter the employee’s e-mail address. This is used for {{{dataLevel1}}} managers who are to be notified by e-mail as soon as an employee triggers an emergency call regarding a {{{dataLevel1}}} allocated to them.
phone
In this field, enter the {{{customerType}}}'s private phone number. This will appear in an e-mail to the {{{dataLevel1}}} manager as soon as an emergency call is triggered by this employee. {{{dataLevel1}}} managers are prompted in the e-mail to call the employee on this phone number.
Attention: Do not use the phone number of the SIM card of the smartphone that is used for the {{{appName}}}© app.
Once you have activated kiosk mode as described here, this smartphone can no longer receive calls.
comments
In this field, you can save any desired comments about each employee.
managers
In this field, you can assign one or more managers to each employee.
The designated manager(s) will receive SOS alerts and information on overdue check-ins for the selected employee.
While you are editing the data set, you are shown a list of all the available employee numbers. Select from the list the unique number(s) of the employee(s) you would like to designate as manager for the selected employee.
assigned tours
This field allows individual tours to be assigned to different employees.
When an employee is logged in they will be instructed to process only the tours assigned to them.
If the field is left empty for an employee, no tours will be assigned to them and the employee account will only be able to [[#Special_incidents_per_{{{dataLevel3}}}|report special incidents or emergency calls]].
track time immediately
The working time for tours selected in this field will be started immediately on tour selection for the specified employee and stopped after logout or selection of another tour.
Tours specified in this field must also be assigned to the employee in the assigned tours column

Customers table

All the customers for whom {{{industry}}} services are provided are entered in the ‘Customers’ table.

Example of 'Customers' table

The table contains the following columns (fields marked with an asterisk* are mandatory):

customer*
enter any name for the customer to be created. A customer name must not be used more than once. Please ensure that you use unique customer names.
customer no.*
enter this customer’s customer number. A customer number must not be used more than once. Please ensure that you use unique customer numbers.
comments
in this field, you can save any desired comments about each customer.

Customers can be either assigned to {{{dataLevel1}}}s, tours or {{{dataLevel3}}}s depending on the structure of your business.
We recommend not to assign employees to different data levels because this can cause unpredictable results of the application.

Public Holidays Categories table

Any number of public holiday categories can be defined in the ‘Public Holidays Categories’ table. A public holiday category is used to consolidate individual public holidays into groups and then allocate these groups to {{{dataLevel1}}}s with identical public holiday regulations.

Example of 'Public Holidays Categories' table

The table consists of two columns, both of which are mandatory:

public holiday category*
in this field, enter a unique name of your choosing for the public holiday category. A name of a public holiday category must not be used more than once. Please ensure that you use unique names.
comments*
in this field you can record any desired comments for each public holiday category.

Public Holidays table

All the public holidays which must be taken into consideration for the various {{{dataLevel1}}}s are entered in the ‘Public Holidays’ table.

Public Holidays are summarised in public holiday categories.

Example of 'Public Holidays' table

The table contains the following columns (fields marked with an asterisk* are mandatory):

public holiday category*
This field refers to the ‘Public Holidays Categories’ table.
While you are editing the data set, you are shown a list of all the public holiday categories created previously. Select from the list the public holiday category you would like to allocate this public holiday to. You can allocate as many public holidays as you like to each public holiday category.
date*
The date of this public holiday must be entered in this field.
comments
In this field you can record any desired comments about each public holiday.
The ‘Public Holidays’ table is linked with the ‘Public Holidays Categories’ table, meaning that, in a workspace containing both tables, selecting one or more categories in the ‘Public Holidays Categories’ table will filter the ‘Public Holidays’ table automatically to show only the public holidays belonging to the selected categories. You can clear this filter by clicking on the
select none
button in the ‘Public Holidays Categories’ table.

You will find more details about linking tables here.

{{{dataLevel1}}}s table

In the ‘{{{dataLevel1}}}s’ table, a customer’s individual {{{dataLevel1}}}s are allocated to the relevant customer.

Example

{{{dataLevel1example}}}

[[File:{{{appName}}}_{{{dataLevel1}}}s_table.png|thumb|722px|none|Example of '{{{dataLevel1}}}s' table]]

The table contains the following columns (fields marked with an asterisk* are mandatory):

customer no.*
The customer number to be specified here refers to the customer number in the ‘Customers’ table.
While editing this value, you are shown a list of all the customers previously recorded in the system. Select from the list the customer to which you would like to allocate this {{{dataLevel1}}} by clicking on it.
{{{dataLevel1}}} name*
In this field, enter a name of your choosing for the {{{dataLevel1}}} to be created.
A {{{dataLevel1}}} name must not be used more than once. Please ensure that you use unique {{{dataLevel1}}} names.
{{{dataLevel1}}} no.*
In this field, enter a number of your choosing for the {{{dataLevel1}}} to be created.
A {{{dataLevel1}}} number must not be used more than once. Please ensure that you use unique {{{dataLevel1}}} numbers.
regional manager*
The value to be specified here refers to the ‘Employees’ table.
While editing this data set a list of all the employees is shown. Select from the list the employee you would like to allocate to this {{{dataLevel1}}} as {{{dataLevel1}}} manager by clicking on his or her employee no..
public holiday category
The public holiday category to be specified here refers to the ‘Public holidays categories’ table.
While editing this data set, a list of all the public holiday categories recorded previously is shown. Select from the list the public holiday category you would like to allocate to this {{{dataLevel1}}} by clicking on it.
comments
in this field, you can record any desired comments about each {{{dataLevel1}}}.

The ‘{{{dataLevel1}}}s’ table is linked with the ‘[[#{{{dataLevel3}}}s_table|{{{dataLevel3}}}s]]’ table and the ‘Customers’ table, meaning that, in a workspace containing these tables

  • selecting one or more customers in the ‘Customers’ table will filter the ‘{{{dataLevel1}}}s’ table and ‘[[#{{{dataLevel3}}}s_table|{{{dataLevel3}}}s]]’ table automatically to show only the {{{dataLevel1}}}s and {{{dataLevel3}}}s belonging to the selected customers.
  • selecting one or more {{{dataLevel1}}}s in the ‘{{{dataLevel1}}}s’ table will filter the ‘[[#{{{dataLevel3}}}s_table|{{{dataLevel3}}}s]]’ table automatically to show only the {{{dataLevel3}}}s belonging to the selected {{{dataLevel1}}}(s).
You can clear these filters by clicking on the
select none
button in the ‘Customers’ table and/or ‘{{{dataLevel1}}}s’ table

You will find more details about linking tables here.

{{{dataLevel3}}}s table

In the ‘{{{dataLevel3}}}s’ table, individual {{{dataLevel3}}}s are allocated to the tours created previously.

[[File:{{{appName}}}_{{{dataLevel3}}}s_table.png|thumb|995px|none|Example of '{{{dataLevel3}}}s' table]]

The table contains the following columns (fields marked with an asterisk* are mandatory):

customer*
The customer number to be specified here refers to the customer number in the ‘Customers’ table.
While editing this value, you are shown a list of all the customer numbers previously recorded in the system. Select from the list the customer to which you would like to allocate this {{{dataLevel1}}} by clicking on it.
{{{dataLevel3}}}*
In this field, you can enter a unique name or number of your choosing for the {{{dataLevel3}}} to be created.
A {{{dataLevel3}}} name or number must not be used more than once. Please ensure that you use unique {{{dataLevel3}}} names or numbers.
NFC tag id*
The tag number of the NFC tag (which subsequently identifies this {{{dataLevel3}}} by scanning the tag with the smartphone software) is entered in this field.
Alternatively, a custom text string can be written to the NFC tag instead of the NFC tag number (see here for more details)
  • If text content is written to the {{{dataLevel3}}}'s NFC tag, this text content must be entered as the NFC tag id instead of the serial number of the NFC tag.
  • If no text content is written to the {{{dataLevel3}}}'s NFC tag, the serial number of the NFC tag should be entered as the NFC tag id.
An NFC tag ID can be assigned to only one {{{dataLevel3}}}. If you attempt to assign the same NFC tag ID to more than one {{{dataLevel3}}}, an error message is displayed.
alerts to regional manager
This field is a checkbox.
If this checkbox is active (true status icon.png), SOS alerts and information on overdue check-ins for the selected {{{dataLevel3}}} will be sent to the regional manager for the respective {{{dataLevel1}}}.
special incidents that might happen for this {{{dataLevel3}}}
The potential special incidents to be defined here refer to the ‘[[#Potential_special_incidents_per_{{{dataLevel3}}} table|Potential Special Incidents per {{{dataLevel3}}}]]’ table.
While editing this field, a list of all the potential special incidents is shown. Select the special incident you would like to allocate to this {{{dataLevel3}}} from the list.
Any number of potential special incidents can be allocated to each {{{dataLevel3}}}.

The ‘{{{dataLevel3}}}s’ table is linked with the ‘[[#{{{dataLevel1}}}s_table|{{{dataLevel1}}}s]]’ table and the ‘Customers’ table, meaning that, in a workspace containing these tables

  • selecting one or more customers in the ‘Customers’ table will filter the ‘[[#{{{dataLevel1}}}s_table|{{{dataLevel1}}}s]]’ table and ‘[[#{{{dataLevel3}}}s_table|{{{dataLevel3}}}s]]’ table automatically to show only the {{{dataLevel1}}}s and {{{dataLevel3}}}s belonging to the selected customers.
  • selecting one or more {{{dataLevel1}}}s in the ‘[[#{{{dataLevel1}}}s_table|{{{dataLevel1}}}s]]’ table will filter the ‘[[#{{{dataLevel3}}}s_table|{{{dataLevel3}}}s]]’ table automatically to show only the {{{dataLevel3}}}s belonging to the selected {{{dataLevel1}}}(s).
You can clear these filters by clicking on the
select none
button in the ‘Customers’ table and/or ‘[[#{{{dataLevel1}}}s_table|{{{dataLevel1}}}s]]’ table

You will find more details about linking tables here.

Potential special incidents per {{{dataLevel3}}} table

The ‘Potential Special Incidents per {{{dataLevel3}}}’ table describes all the potential special incidents per {{{dataLevel3}}} which may occur.

[[File:{{{appName}}}_potential_special_incidents_per_{{{dataLevel3}}}_table.png|800px|thumb|none|Example of 'Potential Special Incidents per {{{dataLevel3}}}' table]]

The table contains the following columns (fields marked with an asterisk* are mandatory):

special incident no.*
In this field, you can specify a unique number of your choosing for the special incident.
A number such as this must not be used more than once. Please ensure that you use unique numbers.
special incident description
In this field, you can save a description of the special incident to be created. This is not transferred to the smartphone. It is used only for orientation purposes in ginstr web.
{{{dataLevel3}}}s for which this special incident might happen
In this field, you define all the {{{dataLevel3}}}s for which the incident to be created may occur.
While editing this data set, a list of all the {{{dataLevel3}}}s is shown. Select from the list the {{{dataLevel3}}}s to which you would like to assign this special incident by clicking on them.
icon*
In this field, you can add an icon, which will subsequently be displayed on a smartphone in the {{{appName}}}© app, to the special incident to be created by clicking on the ‘add pictures’ button.
The ‘Potential Special Incidents per {{{dataLevel3}}}’ table is linked with the ‘[[#{{{dataLevel3}}}s_table|{{{dataLevel3}}}s]]’ table, meaning that, in a workspace containing both tables, selecting one or more {{{dataLevel3}}}s in the ‘[[#{{{dataLevel3}}}s_table|{{{dataLevel3}}}s]]’ table will filter the ‘Potential Special Incidents per {{{dataLevel3}}}’ table automatically to show only the potential special incidents belonging to the selected {{{dataLevel3}}}(s). You can clear this filter by clicking on the
select none
button in the ‘[[#{{{dataLevel3}}}s_table|{{{dataLevel3}}}s]]’ table.

You will find more details about linking tables here.

Tours table

Tours’ allow you to group several {{{dataLevel3}}}s, even those from different {{{dataLevel1}}}s, in to convenient routes. Individual tours must first be defined in the ‘Tours’ table before defining the itinerary of each tour in the Visits per Tour table.

Tours can be allocated to different employees using the Employees table and scheduled to begin at regular dates & times using the Working Windows per Tour table.

Example of 'Tours' table

The ‘Tours’ table contains the following columns (fields marked with an asterisk* are mandatory):

tour name*
In this field, enter a unique name of your choosing for the tour currently being created.
A tour name must not be used more than once. Please ensure that you use unique tour names.
agreed tour working time (decimal hours)*
In this field, enter the tour working time in the decimal hours unit of measurement agreed upon with the customer for the tour currently being created.
One hour is assumed to be 100 units in this case (i.e. 45 minutes = 0.75 hours)
save timestamps for each {{{dataLevel3}}}?
This field contains a checkbox. If this checkbox is active (true status icon.png), the individual times for starting and completing each {{{dataLevel3}}} subsequently allocated to this tour are transmitted individually and displayed in the evaluations.
To allow a post calculation to be performed for each {{{dataLevel3}}}, individual loss-making {{{dataLevel3}}}s can be reliably identified and appropriate counter-measures can be taken.
If this checkbox is not active (false status icon.png), these times are not saved and cannot be restored at a later time either.
maximum deviation in minutes*
In this field, enter the maximum deviation in minutes between the actual duration of the employee’s tour and the value defined in ‘tour working time’.
If this value is exceeded, information is sent to the {{{dataLevel1}}} manager by e-mail.
public holiday category
The public holiday category to be specified here refers to the ‘Public holidays categories’ table.
While editing this data set, a list of all the public holiday categories recorded previously is shown. Select from the list the public holiday category you would like to allocate to each tour by clicking on it.
{{{dataLevel1}}}
The {{{dataLevel1}}} name to be defined here refers to the ‘[[#{{{dataLevel1}}}s table|{{{dataLevel1}}}s]]’ table.
While editing this data set, a list of all the {{{dataLevel1}}}s is shown. Select from the list the {{{dataLevel1}}} to which you would like to allocate this tour.
comments
in this field you can record any comment you like for each tour.

Working Windows per Tour table

The ‘Working Windows per Tour’ table allows you to define regular scheduled start times for tours previously defined in the Tours table.

If a tour should be carried out several times per day at defined times, you can record several rows with the same {{{dataLevel3}}} number in this table.

Example of 'Working Windows per Tour' table

The table contains the following columns (fields marked with an asterisk* are mandatory):

tour name*
The tour name to be defined here refers to the ‘Tours’ table.
While editing this field, a list of all the tours is shown. Select from the list the tour to which you would like to allocate this start time by clicking on it.
ID*
In this field, you can specify a unique ID name or number for each entry.
An ID must not be used more than once. Please ensure that you use unique IDs.
start time*
In this field, you can define the time at which the specified tour is to start on the days specified.
weekday
In this field, you can define the weekdays on which the specified tour has to take place at a particular time.
calendar week no.
If the tour is only required to be scheduled for one or more specific calendar weeks, these can be defined here.
execute on public holiday
This field contains a checkbox. If this checkbox is active (true status icon.png), the selected tour will be scheduled to start at the specified start time on the defined weekdays, irrespective of whether or not the day is designated as a public holiday.
If this checkbox is not active (false status icon.png), the specified start time will not be scheduled for any dates designated as a public holiday.
dates
If the tour is only required to be scheduled on one or more specific dates, these can be defined here.
exclude dates
If the tour is not required to be scheduled on one or more specific dates, these can be defined here.
The ‘Working Windows per Tour’ table is linked with the ‘Tours’ table, meaning that, in a workspace containing both tables, selecting one or more tours in the ‘Tours’ table will filter the ‘Working Windows per Tour’ table automatically to show only the working windows belonging to the selected tour(s). You can clear this filter by clicking on the
select none
button in the ‘Tours’ table.

You will find more details about linking tables here.

Visits per Tour table

The ‘Visits per Tour’ table is used to define the itinerary for each tour. Each visit defined in the ‘Visits per Tour’ has an associated service to be carried out which is defined in the Services per Visit table.

A single tour can include {{{dataLevel3}}}s from different {{{dataLevel1}}}s. {{{dataLevel3}}}s can be visited several times in a single tour if required, and each {{{dataLevel3}}} can be allocated to several different tours.

[[File:{{{appName}}}_visits_per_tour_table.png|thumb|743px|none|Example of 'Visits per Tour' table]]

The table contains the following columns (fields marked with an asterisk* are mandatory):

visit name*
In this field, enter a unique name of your choosing for the visit currently being created.
A visit name must not be used more than once. Please ensure that you use unique visit names.
tour name*
The tour name to be defined here refers to the ‘Tours’ table.
While editing this field, a list of all the tours is shown. Select from the list the tour to which you would like to allocate this visit by clicking on it.
{{{dataLevel3}}}*
The {{{dataLevel3}}} to be defined here refers to the ‘[[#{{{dataLevel3}}}s table|{{{dataLevel3}}}s]]’ table.
While editing this field, you are shown a list of all the {{{dataLevel3}}}s that have already been created. Select the {{{dataLevel3}}} you would like to allocate the current service to from the list.
sequence*
This column is used to define the order in which each {{{dataLevel3}}} is visited within a tour.
The first {{{dataLevel3}}} to be visited should be assigned the number 1, the second should be assigned the number 2 and so on.
It is also possible to use decimal numbers (i.e. 2.5, 2.6) between whole numbers. This can be useful when adding new visits to a pre-existing ‘Visits per Tour’ table' with many entries, avoiding the need to re-number the entire sequence.
preparation time
This column is used to define the time (in minutes) required prior to each visit, taking into account travel time between separate visits.
If no value is entered in this field, the working time for the specified visit will be tracked immediately following completion of the previous visit.
start time
If it is required for an individual visit to start at a specified time, this can be defined here.
If an employee completes the previous visit prior to the defined start time of a subsequent visit, their work will be paused until the next visit can be carried out at the specified start time.
The ‘Visits per Tour’ table is linked with the ‘Tours’ table, meaning that, in a workspace containing both tables, selecting one or more tours in the ‘Tours’ table will filter the ‘Visits per Tour’ table automatically to show only the visits belonging to the selected tour(s). You can clear this filter by clicking on the
select none
button in the ‘Tours’ table.

You will find more details about linking tables here.

Services table

The ‘Services’ table describes all the services that may potentially be carried out for the customers created previously. [[File:{{{appName}}}_services_table.png|thumb|800px|none|Example of 'Services' table]]

The table contains the following columns (fields marked with an asterisk* are mandatory):

service no.*
In this field you can specify a unique service name or number of your choosing for the service to be created.
A service name or number must not be used more than once. Please ensure that you use unique service names or numbers.
service description
In this field you can save a description for the service to be created. This is not transferred to the smartphone. It is used only for orientation purposes in ginstr web.
icon*
by clicking on the ‘+ add picture(s)’ button you can allocate an icon to the service to be created, which will subsequently be displayed on a smartphone in the {{{appName}}}© app.

Services per Visit

The ‘Services per Visit’ table allows you to allocate services previously defined in the Services table to visits previously defined in the Visits per Tour table. It is also possible to define one-off additional services for a particular visit.

Several services can be allocated to the same visit, resulting in multiple service icons displayed to the user on the [[#{{{appName}}}_Android_app|{{{appName}}}© app]] as soon as he/she visits the {{{dataLevel3}}} (scans the NFC tag of the {{{dataLevel3}}}).

[[File:{{{appName}}}_services_per_visit_table.png|thumb|800px|none|Example of 'Services per Visit' table]]

The table contains the following columns (fields marked with an asterisk* are mandatory):

visit*
The visit name to be specified here refers to the ‘Visits per Tour’ table. While you are editing this data set, you are shown a list with all the visits that have already been created.
Select from the list of visit names the visit to which you would like to allocate each service.
service no.
If the required service has previously been defined in the ‘Services’ table, you can select it here. The description and the icon for the service are in this case loaded automatically and allocated to this additional service.
If, on the other hand, a service is to be rendered which is not defined as a regular service, you can describe it in more detail with the following two fields:
description*
Here, enter the description of the service which is to be provided for the {{{dataLevel3}}} defined previously but which is not saved in your services.
infographics*
In this field, you can save the icon to be displayed in the smartphone app for the additional service. To do this, click on the ‘+ add picture(s)’ button within the field.
quantity*
This information is used to specify how often the indicated service is to be performed for the {{{dataLevel3}}} it was allocated to previously.
If the service involves, for example {{{dataLevel3}}} cleaning and the {{{dataLevel3}}} has 4 sections to be cleaned, then ‘4’ is entered in this field.
service value (units / hour)*
The ‘service value’ field specifies how many times the selected service can be provided per hour.
A service value of 60 indicates that the service takes 1 minute to complete.
If the employee were to service e.g. 3 {{{dataLevel3}}}s per hour, in this case the service value would also be 3.
This means:
60 minutes ÷ 3 {{{dataLevel3}}}s = 20 minutes per {{{dataLevel3}}}
20 minutes per {{{dataLevel3}}} × 4 {{{dataLevel3}}}s to be serviced = 80 minutes
In the example provided above, the employee has a time allowance of 80 minutes in total for servicing the four {{{dataLevel3}}}s.
dates
If the service is only required on one or more specific dates, these can be defined here.
The ‘Services per Visit’ table is linked with the ‘Visits per Tour’ table, meaning that, in a workspace containing both tables, selecting one or more visits in the ‘Visits per Tour’ table will filter the ‘Services per Visit’ table automatically to show only the services belonging to the selected visit(s). You can clear this filter by clicking on the
select none
button in the ‘Visits per Tour’ table.

You will find more details about linking tables here.

{{{appName}}}© reports

Below is a description of the tables used to evaluate the work performed and the list of special incidents.

All of these tables are generated automatically based on the data supplied by the smartphone app.

All the reports can be filtered using the search field in the top left-hand corner or sorted by clicking on the column heading.

Ordered Working Times per {{{dataLevel3}}}

This report shows the working time per {{{dataLevel3}}} and compares the scheduled working time and the actual working time. [[File:{{{appName}}}_ordered_working_times_per_{{{dataLevel3}}}.png|thumb|936px|none|Example of 'Ordered Working Times per {{{dataLevel3}}}' report]]

Target Services table

The ‘[[#Ordered_Working_Times_per_{{{dataLevel3}}}|Ordered Working Times per {{{dataLevel3}}}]]’ table is linked with the ‘Target Services’ table, meaning that, in a workspace containing both tables, selecting one or more records in the ‘[[#Ordered_Working_Times_per_{{{dataLevel3}}}|Ordered Working Times per {{{dataLevel3}}}]]’ table will filter the ‘Target Services’ table automatically to show only the services belonging to the selected visit(s). You can clear this filter by clicking on the
select none
button in the ‘[[#Ordered_Working_Times_per_{{{dataLevel3}}}|Ordered Working Times per {{{dataLevel3}}}]]’ table.

You will find more details about linking tables here.

The records of the ‘Target Services’ table are replicated to the ginstr app and as soon as he/she visits the {{{dataLevel3}}} (scans the NFC tag of the {{{dataLevel3}}}), they are shown the list of services which should be rendered during their visit.

Executed and Scheduled Working Time per {{{dataLevel3}}}

This report shows all the working times per {{{dataLevel3}}} for each individual employee in comparison to the agreed working times per {{{dataLevel3}}} in order to highlight potential issues and/or efficiency improvements for individual employees or {{{dataLevel3}}}s.

The report consists of the following columns:

  • tour name
  • {{{dataLevel3}}}
  • {{{dataLevel3}}} NFC tag no.
  • employee no.
  • employee NFC tag id
  • customer no.
  • customer name
  • {{{dataLevel1}}}
  • scheduled {{{dataLevel3}}} preparation start time
  • scheduled working duration at this {{{dataLevel3}}} (decimal minutes)
  • actual working duration at this {{{dataLevel3}}} (decimal minutes)
  • scheduled start time at this {{{dataLevel3}}}
  • actual start time at this {{{dataLevel3}}}
  • scheduled end time at this {{{dataLevel3}}}
  • actual end time at this {{{dataLevel3}}}
  • maximum deviation (minutes)
  • image
  • message
  • video
  • audio
  • time ID
  • visit
  • related date

Data sets created before today's date (shown in blue) are generated automatically and can not edited in retrospect. It is not intended to modify the content of this table manually.


Services Rendered table

The ‘[[#Executed_and_Scheduled_Working_Time_per_{{{dataLevel3}}}|Executed and Scheduled Working Time per {{{dataLevel3}}}]]’ table is linked with the ‘Services Rendered’ table, meaning that, in a workspace containing both tables, selecting one or more records in the ‘[[#Executed_and_Scheduled_Working_Time_per_{{{dataLevel3}}}|Executed and Scheduled Working Time per {{{dataLevel3}}}]]’ table will filter the ‘Services Rendered’ table automatically to show only the services belonging to the selected record(s). You can clear this filter by clicking on the
select none
button in the ‘[[#Executed_and_Scheduled_Working_Time_per_{{{dataLevel3}}}|Executed and Scheduled Working Time per {{{dataLevel3}}}]]’ table.

You will find more details about linking tables here.

The ‘Services Rendered’ table consists of the following columns:

Overdue Employee Check-Ins

This report shows a list of all the cases in which {{{dataLevel3}}} {{{industry}}} was delayed or was not started. If an employee fails to check-in with the app at or before the agreed check-in time, their manager(s) (as defined in the Employees table) will be informed and a record will be automatically generated in the ‘Overdue Employee Check-Ins’ report.

The report consists of the following columns:

  • expected check-in (date and time)
  • last verification (date and time)
  • tour name
  • {{{dataLevel3}}}
  • recipient employee no.
  • recipient e-mail
  • recipient first name
  • recipient last name
The ‘Overdue Employee Check-Ins’ table is linked with the ‘Employees’ table, meaning that, in a workspace containing both tables, selecting one or more employees in the ‘Employees’ table will filter the ‘Overdue Employee Check-Ins’ table automatically to show only the overdue check-ins belonging to the selected employee(s). You can clear this filter by clicking on the
select none
button in the ‘Employees’ table.

You will find more details about linking tables here.

SOS Alarms of Employees

This report shows all the emergency calls made by employees, the {{{dataLevel3}}} the emergency call was made from, and the list of persons who were notified as a result of the relevant emergency call.

The report consists of the following columns:

  • employee no.
  • employee NFC tag
  • employee first name
  • employee last name
  • employee phone
  • recipient employee no.
  • recipient e-mail
  • recipient first name
  • recipient last name
  • tour name
  • {{{dataLevel3}}}
  • date and time of the SOS alarm
The ‘SOS Alarms of Employees’ table is linked with the ‘Employees’ table, meaning that, in a workspace containing both tables, selecting one or more employees in the ‘Employees’ table will filter the ‘SOS Alarms of Employees’ table automatically to show only the SOS alarms belonging to the selected employee(s). You can clear this filter by clicking on the
select none
button in the ‘Employees’ table.

Incidents Reported

This report shows details related to all of the special incidents reported by employees on site.

All the photos of the special incidents recorded using the smartphone camera are also displayed here.

The report consists of the following columns:

  • employee no.
  • employee NFC tag
  • employee first name
  • employee last name
  • {{{dataLevel1}}}
  • tour name
  • {{{dataLevel3}}}
  • incident no.
  • incident description
  • icon
  • date and time of the incident
  • incident images
The ‘Incidents Reported’ table is linked with the ‘Employees’ table, meaning that, in a workspace containing both tables, selecting one or more employees in the ‘Employees’ table will filter the ‘Incidents Reported’ table automatically to show only the incidents reported by the selected employee(s). You can clear this filter by clicking on the
select none
button in the ‘Employees’ table.

Employee Bookings

This report shows a list of all the employee working times per working day. The calculation of working time starts with logging in at the first tour and ends with logging out from the last tour on the same calendar day.

Time for which the employee uses the smartphone app to log breaks is saved as 'break duration' and automatically deducted from the 'working hours'.

The report consists of the following columns:

  • employee no.
  • first name
  • last name
  • work begin timestamp
  • work end timestamp
  • work started in tour
  • work stopped in tour
  • working hours
  • break duration
The ‘Employee Bookings’ table is linked with the ‘Employees’ table, meaning that, in a workspace containing both tables, selecting one or more employees in the ‘Employees’ table will filter the ‘Employee Bookings’ table automatically to show only the bookings belonging by the selected employee(s). You can clear this filter by clicking on the
select none
button in the ‘Employees’ table.

Console

This report contains errors which occurred during hourly background processing of the data. Most of the errors usually relate to the generation of the schedule.

Typical schedule generation errors are:

  • No start NFC tag was found for tour x
  • No end NFC tag was found for tour x
  • Service with number x can't be rendered for {{{dataLevel3}}} x because appropriate icon was not uploaded into ‘Services’ table
  • Render count of service x for {{{dataLevel3}}} y for date ... (...) is more than count of start times for this date: ...


Export data

In some cases, it is desirable to further process data generated using ginstr apps in other programs or Excel. The ‘download data’ feature allows downloading data stored in ginstr tables to your local PC.

To download data from a table or ginstr app, right-click anywhere in the table then select the ‘download data’ option to display the following pop-up window:

download data’ pop-up window


The following options are available to configure the data download:

export format

  • CSV
Files with .csv file extension (Comma-separated values) are commonly used to exchange data between different applications; so in case you would like for example to further process your data in a dispatching or book-keeping software then you can export the data to a .csv file and then import this .csv file into your other software.
  • Excel
This option creates Microsoft Excel compatible files with .xlsx file extension.
Excel 2007 version or newer is required to open such files.
.xlsx files can hold up to 1 million records.

include attachments

  • yes
In case you select this option the data will be downloaded as a .zip file which contains several other files:
  • the .csv or .xlsx file depending on the chosen export format
  • all media files (e.g. .png image files, .wav sound files etc.)
Depending on your operating system and version there are different steps how to extract the individual files contained within the .zip file. If you don´t know how to do this please contact your system administrator.
  • no
  • download of the data of just one table
In this case just the .csv or .xlsx file will be downloaded depending on the chosen export format
  • download of all tables of a ginstr app
In this case the data of all tables of the selected ginstr app will be downloaded packed into one .zip file.

rows filter

  • all rows
This option allows to download all records of a table independent of currently applied filter options.
  • visible rows
ginstr tables provide a multitude of options to filter and sort the content of tables.
In case you have filtered some records to be shown on your screen and you choose this option then only the records currently shown on the screen will be downloaded.
  • table with dependencies
This option allows you to download the selected table together with any related tables connected through pointer and/or assignment datatype.
  • all tables of this ginstr app
In case the table you right-clicked belongs to a ginstr app, then this additional option will be available which allows downloading all tables of the ginstr app in one step.
all tables of this ginstr app’ option displayed in ‘download data’ pop-up window if the selected table belongs to a ginstr app
This feature is sometimes used for local data backup on a customer’s PCs in addition to the automatic backup the ginstr cloud provides by default.
In case of CSV export format, each table will be represented as a separate .csv file. In case of .xlsx export format, each table will be represented as a separate sheet inside one single .xlsx file.

columns filter

  • all columns
This option allows to download all records of a table independent of currently applied column visibility settings.
  • visible columns
ginstr tables provide a multitude of options to filter and sort the content of tables.
In case you have hidden some columns to be shown on your screen and you choose this option then only the columns currently shown on the screen will be downloaded.

language

Most ginstr apps are available in multiple languages. The language selection does not only affect the UI of the apps on the phone but also the table headings. With this option you can select the language in which the headings of the downloaded tables must be stored in the .csv or .xlsx file.
Default value depends on the settings of the user in his ginstr web preferences.

time format

ginstr supports multiple time formats. This option allows defining in which time format the data should be downloaded. This might be relevant for you because the software that will be used to further process the data might have some restrictions in this regards.
Default value depends on the settings of the user in his ginstr web preferences.

date format

ginstr supports multiple date formats. This option allows defining in which date format the data should be downloaded. This might be relevant for you because the software that will be used to further process the data might have some restrictions in this regards.
Default value depends on the settings of the user in his ginstr web preferences.

number format

ginstr supports multiple number formats. This option allows defining in which number format the data should be downloaded. This might be relevant for you because the software that will be used to further processing the data might have some restrictions in this regards.
Default value depends on the settings of the user in his ginstr web preferences.

time zone

ginstr internally stores all data in UTC time zone; this is the universal time which is the same worldwide. Before presenting dates and times on the screen, each timestamp is adopted to the time zone selected by the user in his ginstr web preferences.
This option can be used to override the time zone settings in the ginstr web preferences.
Default value depends on the settings of the user in his ginstr web preferences.
Export into Excel of numbers, dates, times and pointers to these datatypes is done supporting Excel cell formats according to the operating system's 'Region and Language' settings. This means that if a date is exported as "1 January 2016" but Excel is opened on a system with 'Region and Language' format set to German, it will be shown as "1. Januar 2016".


Each table is exported with one additional column: "record created on". The value in this column stores the record creation date which is used for filtering in the case of a large data table.


Access to media files (pictures, videos, audio files, documents) after download

Export without attachments
In this case the URL of the media files will be stored in the .csv or .xlsx file. In case a table cell contains multiple files, then the URLs will be separated with “|” (i.e. http://ginstr.com/image1.jpg|http://ginstr.com/image2.jpg)
These links will be available until the attachments (or the entire row which contained such attachments) are deleted from the ginstr cloud.
Note: ginstr credentials are not required to open these links (i.e. anybody with the link can view the attachments).
Export with attachments
  • Tables that do not belong to a ginstr app:
In this case the .csv / .xlsx file will contain relative links to the appropriate files in the archive folder.
For example pictures/image1.jpg in single table export will mean that this file is placed inside the archive at the following path: /pictures/image1.jpg.
  • Tables belonging to a ginstr app:
In this case pictures/image1.jpg of “customers” table will be stored in the archive at the following path: /customers/pictures/image1.jpg.
As per Export without attachments (above), if a table cell contains multiple files, then the URLs will be separated with “|” (i.e. pictures/image1.jpg|image2.jpg)


Import data

In some cases it is desirable to import data generated using third party programs or to upload data that has previously been exported from the ginstr cloud back to the cloud again. The ‘upload data’ feature allows uploading data stored on your local PC to ginstr tables in the ginstr cloud.

To upload data to a ginstr table or ginstr app, right click anywhere in the table then select the ‘upload data’ option to display the following pop-up window:

upload data’ pop-up window

In order to ensure that the headings of the tables to be uploaded to the ginstr cloud are correct and complete, it is recommended to download the existing table(s), even if they are empty, and to use these downloaded files for editing and subsequent data upload.


The following options are available to configure the data upload:

upload data

  • in this table only
Use this option if you want to upload data for the selected table only.
  • all dependent tables
If you had previously downloaded the selected table together with any related tables connected through pointer and/or assignment datatype and made some changes to these downloaded tables, this option allows you to re-upload all dependent tables in one step.
  • in all tables of this ginstr app
In case the table you right-clicked belongs to a ginstr app which is using multiple tables, then this option will be available; it allows uploading data to all tables of this ginstr app in one step.

include attachments

  • yes
In case you select this option, the data must be uploaded as a .zip file which contains several other files:
  • the .csv or .xlsx file
  • all media files (e.g. png image files, .wav sound files etc.)
Depending on your operating system and version there are different steps how to pack individual files into a .zip file. If you don´t know how to do this please contact your system administrator.
  • no
In this case just the .csv or .xlsx file(s) will be uploaded without attachments. These files must be packed as a .zip file in any case if you are going to upload data, which will go into tables belonging to ginstr apps.

language

Most ginstr apps are available in multiple languages. The language selection not only affects the UI of the apps on the phone but also the headings of the tables in ginstr web.
With this option, you can select the language in which the headings of the table columns to be uploaded have been stored in the .csv or .xlsx file.
This is essential to ensure that the upload routine can assign the content of the various columns in the files to the related columns of the ginstr tables.
Default value depends on the settings of the user in his ginstr web preferences.

time format

ginstr supports multiple time formats. This option defines in which time format the data should be uploaded. This is essential to ensure that the upload routine treats the timestamps in the various columns correctly.
Example: 10:00:00 PM or 22:00:00 - one of these two time formats can be used with the values stored as text.
Default value depends on the settings of the user in his ginstr web preferences.

date format

ginstr supports multiple date formats. This option allows defining in which date format the data is stored. This is essential to ensure that the upload routine treats the dates in the various columns correctly.
Note that two date formats can look similar: dd/mm/yyyy and mm/dd/yyyy, hence 01/02/2016 can be either the 2nd of January 2016 or the 1st of February 2016. This cannot be detected automatically and therefore setting this option carefully is required.
Default value depends on the settings of the user in his ginstr web preferences.

number format

ginstr supports multiple number formats. This option allows defining in which number format the data should be uploaded. This is essential to ensure that the upload routine treats the numbers in the various columns correctly.
Default value depends on the settings of the user in his ginstr web preferences.

time zone

ginstr internally stores all data in UTC time zone; this is the universal time which is the same worldwide. Before presenting dates and times on the screen, each timestamp is adopted to the time zone selected by the user in his ginstr web preferences.
This option can be used to indicate the time zone in which the data contained in the file to be uploaded has been saved.
Default value depends on the settings of the user in his ginstr web preferences.

choose file

This option is used to select the file on the local disk drive which contains the data that should be uploaded to the ginstr cloud.


If the “record created on” column is empty in the file to be uploaded, then the newly uploaded records will have a record creation date from the moment when the data was uploaded. Otherwise the record creation date provided in the imported file will be used.


File names and table names

Excel files
For the upload of Excel files the Excel file names and sheet names are not relevant.
Each Excel sheet must provide in cell A1 the precise name of the table to which the data will be uploaded. This table name must correspond with the language which was selected in the ‘language’ option of the file upload pop-up window.
.csv files
.csv file names must have the following format:
table_name_in_language_of_import.csv (i.e. customers.csv)
Data with references to other tables in the ginstr cloud (not presenting in Excel file) can only be uploaded if the relevant columns with the references have the ‘unique’ attribute set for them. In case of Excel import and both rows present (row to which reference is created and row which has reference) import can be done to non-unique row in case reference is a correct Excel reference.


Please note that the data upload feature does not update records; it just creates new records.

In case of uploading Excel .xlsx files with dates and numbers columns stored in 'text' cell format, these values should have the format which was previously selected in the data upload pop-up window.

If dates and numbers are stored in an Excel file like a number datatype, then the Excel cell format will be used during the data upload and therefore the format specified in the upload dialog will be ignored.

Data upload is limited to max. 100 MB per file to be uploaded.

{{{appName}}} Android app

First steps

Gmail account

An individual Gmail account is required for each device.

It is essential to ensure that each device is assigned its own unique Gmail account.

The use of the same Gmail account on multiple devices is strongly discouraged. Because of Google's security policies, in the case of a Google software update the device will be blocked meaning that each device would have to be updated manually after every Google update.

Downloading the app

The {{{appName}}}© app can be downloaded from the Google Play Store using the following link:

https://play.google.com/store/apps/details?id={{{googlePlayURL}}}

Alternatively, you can read the following QR code with your Android smartphone to start downloading the app:

[[File:QR_{{{appName}}}.png|border|none|100px]]

Installing the software

Ensure that the phone is connected to the Internet via WLAN and, for security reasons, deactivate the mobile connection to the Internet or remove the SIM from the device.

Once you have selected the {{{appName}}}© app in the Google Play Store as described previously, tap the
INSTALL
button:
[[File:GooglePlayStore_Install_{{{appName}}}.png|thumb|220px|none|Google Play Store
INSTALL
button]]


Once the app has been installed, you must ensure that the ‘Auto-update’ option has been activated in the Google Play Store for {{{appName}}}© on every phone!

To activate this feature, please tap the three dots in the top right-hand corner of your screen as soon as the app has been successfully installed on your smartphone.

[[File:GooglePlayStore_Installed_{{{appName}}}.png|thumb|220px|none|Google Play StoreAuto-update’ option]]
Once the ‘Auto-update’ feature has been activated, please do not click on the
OPEN
button. Press your smartphone’s ‘home button’ instead.

You are now shown the selection between your standard menu and the {{{appName}}}© app.

In this window, please select {{{appName}}} and click on the
ALWAYS
button:
[[File:GooglePlayStore_Always_Open_{{{appName}}}.png|thumb|220px|none|Select {{{appName}}} and click on the ‘ALWAYS’ button]]


The app now opens and you can proceed with the next steps.

Downloading app data to the Android smartphone

In the following screen, you are prompted to enter your login credentials for the ginstr web user account. This step, which is only required once per phone, logs the smartphone into your user account with the app. To do this, please enter your login credentials and confirm the entry by tapping the button with the blue tick.

[[File:{{{appName}}}_App_Login.png|thumb|220px|none|{{{appName}}}© login screen]]


Once you have successfully logged in, the smartphone’s database is synchronised with the server’s database:

[[File:{{{appName}}}_App_DataSync.png|thumb|220px|none|Database synchronisation]]

This step can take a few minutes depending on the size of the database.

Once synchronisation has been successfully completed, you can proceed with the next step to activate kiosk mode. Until then the smartphone is blocked.

Activating the kiosk mode

Activating the kiosk mode is optional. The kiosk mode ensures that the smartphone can only be used to perform the features of the {{{appName}}}© app.

To activate kiosk mode, please tap anywhere in the log-in screen shown below until the following context menu appears:

[[File:{{{appName}}}_App_KioskMode_Context_Menu.png|thumb|220px|none|{{{appName}}}© context menu with ‘kiosk mode’ option]]

Now select the ‘kiosk mode’ menu item.

In the following screen, you are now prompted to define a password for kiosk mode. Under no circumstances should this password be made available to your employees.

Enter the password and confirm the entry by tapping the button with the blue tick.

In the following screen, activate the smartphone’s kiosk mode by clicking on the
ACTIVATE
button:
  • [[File:{{{appName}}}_App_KioskMode_Password.png|thumb|220px|none|Password entry screen for activating ‘kiosk mode’]]
  • [[File:{{{appName}}}_App_KioskMode_Activate.png|thumb|220px|none|Device administrator screen for activating ‘kiosk mode’]]

Take note of the password! This is absolutely essential to enable you to exit kiosk mode again.

Logging an employee into the software

If all of the settings have been made successfully, your employees can start using the app.

If kiosk mode is activated, the {{{appName}}}© app opens automatically when the device starts.

If kiosk mode is not activated, the app can be started by tapping on the app icon on the device homescreen or App Drawer

[[File:{{{appName}}}_App_Icon.png|80px|link=]]
Note: if the {{{appName}}} icon is missing from your device's launch screen, use the
create icons on the launch screen
button on the ginstr launcher login screen to re-generate it.

The employee is first prompted to log into the software.

[[File:{{{appName}}}_App_Employee_Login.png|thumb|220px|none|{{{appName}}}© start-up screen]]


To this end, the NFC tag allocated to this employee in the ‘Employees’ table must be touched with the smartphone’s NFC reader. Generally speaking, this should be the company badge.

Alternatively, the employee can also tap and hold anywhere on the screen and select the ‘PIN Code Login’ menu item to log into the app by entering their NFC tag ID.

When the employee has successfully logged into the software, their name will appear on the screen:

[[File:{{{appName}}}_App_Employee_Logged_In.png|thumb|220px|none|Once logged in, the employee name is displayed]]

To get started with the {{{industry}}} work, the employee must select a tour from the drop down selection by tapping on 'Please select tour...' and selecting the name of the tour they wish to begin.

[[File:{{{appName}}}_App_Tour_selection.png|thumb|220px|none|Tapping on 'Please select tour...' displays a list of available tours]]

After selecting a tour from the drop down selection, the employee is shown which {{{dataLevel3}}} they have to service first today:

[[File:{{{appName}}}_App_Region_Active.png|thumb|220px|none|Screen showing next {{{dataLevel3}}} to be serviced by the employee]]

Services per {{{dataLevel3}}}

Now, the employee should go to the {{{dataLevel3}}} and scan the NFC tag installed at this {{{dataLevel3}}}.

By reading the NFC tag of the first {{{dataLevel3}}} to be serviced, the employee is automatically forwarded to the screen below, which shows the employee all the services which have to be rendered for this {{{dataLevel3}}} now with the help of icons.

[[File:{{{appName}}}_App_Services_to_be_rendered.png|thumb|220px|none|Screen showing all the services which have to be rendered for the active {{{dataLevel3}}}]]


Once the {{{industry}}} services to be rendered by the {{{customerType}}} have been performed in full, the employee must confirm this by tapping the button with the blue tick.

Following this confirmation, he is shown the next {{{dataLevel3}}} to be serviced:

[[File:{{{appName}}}_App_Region_Active.png|thumb|220px|none|Screen showing the next {{{dataLevel3}}} to be serviced]]

Special incidents per {{{dataLevel3}}}

The special incidents report is important for the company so that it can draw conclusions with regard to improving work processes, whether there is any potential for increasing {{{customerType}}}s’ efficiency, etc.

Customers may be interested in this information too, in the sense of them being provided with a smooth service.

Furthermore, the special incidents report protects both {{{customerType}}}s and the company from any false accusations and suspicion. Using this information, the {{{dataLevel1}}} manager is capable of responding immediately to any faults which occur during ongoing operation before the situation can potentially escalate.

If an employee would like to report a special incident regarding a {{{dataLevel3}}}, they should click on the yellow exclamation mark in the bottom left-hand corner of the screen. They are then automatically forwarded to a screen with icons illustrating the potential particular incidents allocated to the current {{{dataLevel3}}}.

  • [[File:{{{appName}}}_App_Services_to_be_rendered.png|thumb|220px|none|'Services to be rendered' screen showing yellow exclamation mark button in the bottom left-hand corner]]
  • [[File:{{{appName}}}_App_Special_Incidents.png|thumb|220px|none|'Special incidents per {{{dataLevel3}}}' screen]]

The following icons are shown:

SOS icon
Tapping on the SOS icon triggers an emergency call.
This is automatically forwarded to the responsible {{{dataLevel1}}} manager.
To reassure the employee, a voice message is played informing them that they will be called back immediately.
Camera icon
Tapping on the camera icon allows the employee to take a picture in connection with the special incident. This picture is automatically transmitted to the server.
Other icons
Other icons for potential special incidents are shown if they have previously been assigned to the current {{{dataLevel3}}} in the back-end.
If the employee taps on one of these icons, the {{{dataLevel1}}} manager is informed of the special incident by e-mail and/or SMS.

Logging out

Before the employee can log out of the app on the smartphone, they must log out of the tour. You will find more details about this here.

If the employee is logged out of the tour, they will see a screen where they are prompted to log into a tour.

[[File:{{{appName}}}_App_Employee_Logged_In.png|thumb|220px|none|After logging out of a tour, this screen prompts the employee to log into a tour]]


If the NFC tag which identifies the employee is read in this screen, the employee is logged out of the software and the current time is transmitted to the office software as the ‘end of tour working time’.

Alternatively, the employee can also tap and hold anywhere on the screen and select the ‘PIN Code Logout’ menu item to log out of the app by entering their NFC tag ID.

Logging out of a tour

If the employee has finished their work in one tour or has to stop working in this tour for whatever reason, they can log out by reading the NFC tag that identifies the current tour.

If there are no further {{{dataLevel3}}}s in a tour, nothing is displayed under ‘Next {{{dataLevel3}}}:’.

The employee is also informed of this situation by a notification on the screen as soon as they report that the last {{{dataLevel3}}} to be serviced in a tour is finished.

[[File:{{{appName}}}_App_All_Tasks_Completed.png|thumb|220px|none|Screen displayed when all services per {{{dataLevel3}}} have been rendered]]


If there are {{{dataLevel3}}}s in a tour which are not yet serviced and the employee wants to log out of the current tour by reading the tour’s NFC tag, they are notified of this by a note on the screen that still non-serviced {{{dataLevel3}}}s remain:

[[File:{{{appName}}}_App_Unfinished_Tasks.png|thumb|220px|none|Screen displayed when logging out of a tour with un-serviced {{{dataLevel3}}}s remaining]]


To switch between two tours, the employee must first log out of the current tour they are logged into, after which they can then log into another tour by reading an NFC tag which identifies another tour.

If an employee exits a tour where there are still {{{dataLevel3}}}s due to be serviced, they can return to it at any time.

Processing {{{dataLevel3}}}s in a deviating order

There is always the possibility of an employee logging in to a {{{dataLevel3}}} which either does not have to be serviced at the present time or even today.

If there are currently no services to be rendered for such a {{{dataLevel3}}}, no services are shown on the screen:

[[File:{{{appName}}}_App_All_Tasks_Completed.png|thumb|220px|none|Screen displayed when all services have been rendered for a tour]]


But if one or more instances of {{{industry}}} work are scheduled for the {{{dataLevel3}}} today, they are displayed and the employee can service this {{{dataLevel3}}}.

As soon as the employee marks the {{{dataLevel3}}} as complete, they are shown the {{{dataLevel3}}} they actually had to service, and the smartphone software automatically returns to the scheduled order of {{{dataLevel3}}}s for today.

In this case, the {{{dataLevel3}}} which has already been completed is skipped in the order of {{{dataLevel3}}}s to be processed now.

Several employees in one tour at the same time

It may happen that several employees log into a tour at the same time. To name but one example, this feature is used in the event of several employees acting on an employee’s behalf in a tour e.g. in case the original {{{customerType}}} is unwell.

If several employees are working in one tour at the same time, they are shown the next {{{dataLevel3}}} to be serviced on their phones based on the specified order.

Any {{{dataLevel3}}}s that have already been serviced by another employee are skipped.

Displaying the remaining tour working time

As soon as an employee has logged into a tour, a coloured bar and the remaining tour working time are displayed along the top edge of the screen.

This bar is yellow to begin with and its length is proportional to the scheduled tour working time decimal hours (defined in the ‘Tours’ table)

As the employee spends more working time in the tour, the bar gets progressively shorter and thus indicates the remaining time available for this tour:

[[File:{{{appName}}}_App_Region_Active.png|thumb|220px|none|Remaining working time displayed when logged into a tour]]


If the tour working time has elapsed, the bar is filled with red and shows the same time provided for processing this tour, thereby indicating that the scheduled tour working time is being continuously exceeded:

[[File:{{{appName}}}_App_Region_Working_Time_Remaining.png|thumb|220px|none|Working time indicator bar turns red when the scheduled tour working time is exceeded]]

Offline mode

The application’s entire database is saved locally on the device. This means it is also possible to work with the app during times when there is no Internet connection available.

All the data recorded is saved locally on the phone and the next time an Internet connection is established, synchronisation with the database on the ginstr cloud servers will take place automatically.

Any activities recorded retrospectively using the office software and which could at first not be sent to the smartphone for lack of an Internet connection are not displayed until the Internet connection has been re-established.