NoahFace is widely deployed in large organizations with many thousands of users and hundreds of work sites.

This Tech Note explains how to optimize your configuration in these large environments.

‍

iPad Synchronization

The NoahFace App automatically detects when you make changes to your configuration or user lists, and synchronizes these changes to each iPad.

There are a number of configuration settings that impact the time taken for each of these synchronizations, which are explained below.

Access Rules

The time taken for each iPad synchronization has an almost linear relationship with the number of users being synchronized to it.

If you have multiple sites and employees only work at one or a small number of sites, it is therefore critical that you configure your Access Rules to minimise the number of employees synchronized to each Access Point.

For example, if you have 1000 employees in New York, 2000 employees in Miami, and 3000 employees in Los Angeles, you don't want to be synchronizing 6000 workers to each site.

This is covered in detail in the Tech Note Multi-Site Deployments.

Biometric Storage

If you are using facial recognition and you store biometrics in the Cloud, they will be pulled to each iPad as part of the synchronization process.

You can therefore minimize the time taken by each synchronization by only storing biometrics locally on each iPad.

The Biometric Storage setting can be updated on your Access Point Type as follows:

Profile Pictures

User profile pictures are pulled to each iPad as part of the synchronization process.

You can therefore minimize the time taken by each synchronisation by making use of avatars instead of photos for profile pictures.

To enforce the use of avatars, you can set the pictures configuration option to "avatars" in your Access Point Type as follows:

‍

Clocking In/Out

There are a number of configuration settings that impact the time taken for employees to clock in and out using the NoahFace App, which are explained below.

Facial Recognition and User Identification

Facial recognition is unquestionably the fastest and most convenient method of identifying employees.

However, the time taken to identify employees using facial recognition will increase as the number of users synchronized to each iPad increases.

So while there is no hard limit on the number of users that can use facial recognition on a single iPad, we recommend:

• You configure your Access Rules to minimise the number of employees synchronized to each iPad. This is especially important if you have multiple sites, as detailed in the Tech Note Multi-Site Deployments.
• If you need to have a large number of employees (ie: over 2000) sharing a single iPad (and cannot configure your Access Rules or adjust your work practices to reduce this number), you should consider other forms of identification (eg: passcodes, employee numbers, access cards, etc). To learn more, see the Tech Note An Overview of User Identification.

Clocking Modes and Status Sharing

The Clock In/Out screen in the NoahFace App has many modes of operation as detailed in the Tech Note Clock In/Out Modes.

If you need employees to be able to clock in using one iPad and clock out using another iPad, then there are two major choices:

• Use "Manual Mode" (or variations) so that both options (ie: Clock In AND Clock Out) are always available.
• Use "Auto Mode" (or variations) so that when a person presents at the iPad the NoahFace App will reach out to the Cloud to determine their clocking status, and only the appropriate clocking option (ie: Clock In OR Clock Out) will be made available.

To learn more about these options, see the Tech Note Clocking In/Out Using Multiple iPads.

The performance of "Manual Mode" (and variations) is vastly better than the performance of "Auto Mode" (and variations), so from a purely performance perspective, it is recommended to use "Manual Mode" (and variations) wherever possible.

If you have some sites that have multiple iPads (where you want to use status sharing) and other sites that have only one iPad (where you don't need status sharing), then you should setup two different Access Point Types and assign them as appropriate

‍

‍

‍

‍

‍

‍