I have a few crew work groups where the same person is the default user for them as they are the supervisor of both groups. The mobiledbgeneration cron job is reporting errors on any of these multi crew work groups where the same default user is present. What is the best way to set this up? Does each person group really need a different default user?

ERROR:
Crontask instance ID: MobileDbGeneration.HVAC-STEAM;
Template user: USER;
Template user insert site: SITE1;
Person groups associated: HVAC, STEAM;

Warning: The template user is present in more than one Person Group and marked as Default User.

Based on the formatted error, you're on MAS 9.1. For the vast majority of customers, you do NOT want to use the person group flow in 9.1. IE you want a user to generate the preload database that is not a default on any person group. Then use the new cron task parameter for configuring the site(s), language(s), etc. you want the preload database to generate for. Maximo Mobile will change the user's default insert site and language and process them all from that cron task instance, sort of like the PMWOGEN process where MAXADMIN (or another account) can be used to generate work orders for many different sites.

When this is used and a user logs in, Maximo Mobile looks for a preload database for the site & language of the user. There is no need to have a person group that you maintain for the mobile database.

When you use the person group flow (which was the only option available in 9.0 and earlier), it uses the user's existing default insert site, language, etc. to generate a database. If this is tied to a real user and that user can change their default insert site, you may have completely random sets of data based on when the preload database is generated. IE Monday you could have data for BEDFORD site and Tuesday you could have data for NASHUA site because the user changed their default insert site. If you have 100 sites, you need at least 100 person groups, 100 cron task instances, and 100 users. And assuming the person group has people with different insert sites, you likely will have users with the wrong data. Another problem, but the least of the issues in my opinion, is you store the same database multiple times which is why you're given the warning. IE there's an entry in the MOBILEDB table for each person group that user is a default on even though the data being stored will be identical since it's the same site, language, etc. 

The reason the person group feature still exists in 9.1 is if you had lookup data that you wanted to be different inside the same site (IE our storeroom clerks in BEDFORD should see X data but our technicians in BEDFORD should see Y data), you would need to use the person group approach. But lookup data for most customers can be shared across everyone inside the same site. It's typically the transactional data (Work Orders, SRs, count books, etc.) that varies between users inside the same site. 

I have a few crew work groups where the same person is the default user for them as they are the supervisor of both groups. The mobiledbgeneration cron job is reporting errors on any of these multi crew work groups where the same default user is present. What is the best way to set this up? Does each person group really need a different default user?

ERROR:
Crontask instance ID: MobileDbGeneration.HVAC-STEAM;
Template user: USER;
Template user insert site: SITE1;
Person groups associated: HVAC, STEAM;

Warning: The template user is present in more than one Person Group and marked as Default User.

Currently we are on 9.0.7 and only have the one site. Users are not allowed to change any of that info. I am a little confused by some of this. I think what I am looking at is the up front building of the mobile DB correct? The users accessing and downloading that DB isn't the issue for me.  It is erroring out when building the mobile DB due to the user running the cron being in multiple person groups. 

Is the answer to have a separate user for each mobile DB person group cron instance that isn't the default user for the person group? I am just looking for a write up on the recommended way to configure this I guess. 

Based on the formatted error, you're on MAS 9.1. For the vast majority of customers, you do NOT want to use the person group flow in 9.1. IE you want a user to generate the preload database that is not a default on any person group. Then use the new cron task parameter for configuring the site(s), language(s), etc. you want the preload database to generate for. Maximo Mobile will change the user's default insert site and language and process them all from that cron task instance, sort of like the PMWOGEN process where MAXADMIN (or another account) can be used to generate work orders for many different sites.

When this is used and a user logs in, Maximo Mobile looks for a preload database for the site & language of the user. There is no need to have a person group that you maintain for the mobile database.

When you use the person group flow (which was the only option available in 9.0 and earlier), it uses the user's existing default insert site, language, etc. to generate a database. If this is tied to a real user and that user can change their default insert site, you may have completely random sets of data based on when the preload database is generated. IE Monday you could have data for BEDFORD site and Tuesday you could have data for NASHUA site because the user changed their default insert site. If you have 100 sites, you need at least 100 person groups, 100 cron task instances, and 100 users. And assuming the person group has people with different insert sites, you likely will have users with the wrong data. Another problem, but the least of the issues in my opinion, is you store the same database multiple times which is why you're given the warning. IE there's an entry in the MOBILEDB table for each person group that user is a default on even though the data being stored will be identical since it's the same site, language, etc. 

The reason the person group feature still exists in 9.1 is if you had lookup data that you wanted to be different inside the same site (IE our storeroom clerks in BEDFORD should see X data but our technicians in BEDFORD should see Y data), you would need to use the person group approach. But lookup data for most customers can be shared across everyone inside the same site. It's typically the transactional data (Work Orders, SRs, count books, etc.) that varies between users inside the same site. 

I have a few crew work groups where the same person is the default user for them as they are the supervisor of both groups. The mobiledbgeneration cron job is reporting errors on any of these multi crew work groups where the same default user is present. What is the best way to set this up? Does each person group really need a different default user?

ERROR:
Crontask instance ID: MobileDbGeneration.HVAC-STEAM;
Template user: USER;
Template user insert site: SITE1;
Person groups associated: HVAC, STEAM;

Warning: The template user is present in more than one Person Group and marked as Default User.