Available for an ArcGIS organization licensed with the Indoors extension.
Once you load floorplans to the ArcGIS Indoors geodatabase, you can manually load occupant data.
Databases of occupants—for example, employees, residents, or faculty—typically come from external systems or tables. These must be converted to points to support searching and routing in the Indoors apps. Occupant data can be loaded from a geodatabase table, a CSV file, or a Microsoft Excel spreadsheet (XLS or XLSX).
You can use the Generate Occupant Features tool to import the occupant data and spatialize it for search and routing functionality.
Note:
The source table must include a primary key field that can be used to associate table records with building space features. In the Indoors model, the UNIT_ID can be used as the primary key.
In addition to a primary key field, four required fields must be present in the source table:
- KNOWNAS—The occupant's name
- EMAIL—The occupant's email address
- CONTACT_PHONE—The occupant's phone number
- CONTACT_EXTENSION—The occupant's extension number
- ORG_LEVEL_1—The occupant's team
- ORG_LEVEL_2—The occupant's department
- JOB_TITLE—The occupant's job title
- START_DATE—The occupant's start date
In addition to these required fields, more fields containing data related to occupants, such as employee number, can be added as needed.
Refer to the following sections for more information on the required fields.
KNOWNAS
An occupant can be known by a name other than their first name, and is more likely to be searched for in the app by their known name.
For example, if an occupant whose first name is Anthony and whose last name is Palmer goes by Scooter, most people will search for him in the app using Scooter Palmer. The KNOWNAS field would contain this known name.
Two occupants may have the same known name, but their email addresses should be different. In this situation, Indoors will use the EMAIL field to identify unique occupants.
CONTACT_PHONE
You can store phone numbers in this column where the occupant can be reached directly. Additional characters or spacing in phone num
bers is supported, but it is recommended to store phone numbers as a set of digits. International calling codes can be included.
For example, +19097932853 is recommended instead of +1 (909) 793 2853 or +1 909-793-2853.
CONTACT_EXTENSION
Depending on the telephone system in your organization, there may be an interactive voice response (IVR) configured with specific codes assigned to different departments and extension numbers set up that need to be dialed to reach an occupant. Indoors supports this type of setup and will combine the two numbers when initiating a phone call from ArcGIS Indoors for iOS or ArcGIS Indoors for Android.
For example, if the IVR code to reach the receptionist is 0, store 9097932853 in CONTACT_PHONE and 0 in CONTACT_EXTENSION.
Tip:
If more than one extension code is needed to reach an occupant, separate the values using a comma.
For example, if the IVR code for a department is 5 and the extension number is 1234, store the number as 5,1234 in CONTACT_EXTENSION.
ORG_LEVEL_1
The Space Planner app includes filters to help users quickly find and assign occupants to spaces. By default, this field represents the Department the occupant is assigned to within your organization's hierarchy. You may modify the meaning of this attribute by altering the field's alias in the output feature class to represent the level of the organization you wish to filter by. This field is always intended to represent the primary organization to what has been defined in the ORG_LEVEL_2 field.
ORG_LEVEL_2
The Space Planner app includes filters to help users quickly find and assign occupants to spaces. By default, this field represents the Team the occupant is assigned to within your organization's hierarchy. You may modify the meaning of this attribute by altering the field's alias in the output feature class to represent the level of the organization you wish to filter by. This field is always intended to represent a secondary organization to what has been defined in the ORG_LEVEL_1 field.
JOB_TITLE
The Space Planner app includes filters to help users quickly find and assign occupants to spaces. Including this field in your input table and populating job title for occupants to be loaded will allow you to filter by job title when assigning occupants to spaces making it easier to evaluate space requirements by role or position.
START_DATE
The Space Planner app includes filters to help users quickly find and assign occupants to spaces. Including this field in your input table and populating start date for occupants to be loaded will allow users of the Space Planner app to filter by start date when assigning occupants to spaces making it easier to evaluate space requirements by seniority.
The Generate Occupant Features tool updates the ASSIGNMENT_TYPE values for those spaces in the Units feature class that now have an assigned occupant. The ASSIGNMENT_TYPE attribute drives specific features of the Space Planner app. Ensure that the value of this attribute is set to Office for spaces occupied by individuals for the best performance.