Available with the ArcGIS Indoors Pro or ArcGIS Indoors Maps extension.
You can add occupant data to an Indoors database and integrate it into floor-aware maps and apps. For example, you can use Indoor Space Planner to manage employee assignments to offices and hotel areas, search for occupants and route to them in Indoor Viewer or Indoors mobile, or enable workspace reservations so that occupants can book meeting rooms and office hotels.
When you run the Create Indoors Database or Upgrade Indoors Database tool, the Occupants feature class is created in the Indoors database. After loading floor plans into a database, you can import occupant information from external systems or tables. Occupant data can be loaded from a geodatabase table, a .csv file, or a Microsoft Excel spreadsheet (.xls or .xlsx file) that contains the required fields.
You can use the Update Occupant Features tool to import the occupant data and spatialize it for search and routing functionality. You can periodically update occupant information, seating assignments, or floor plan updates and add, delete, or modify occupant features.
The Update Occupant Features tool assigns occupants to units by matching the units and occupants from the input table with the units and occupants in the Indoors model. This matching process is based on unique identifiers that are defined in the tool parameters. The tool can update occupant information in the following ways:
- Assign occupants to a unit—When an occupant is assigned to a unit, its assignment type is changed to Office. An occupant feature is also created at the centroid of the unit and the unit's Unit ID and Level ID field values are added to the occupant feature.
- Assign occupants to home offices—You can set a SQL query for the Home Office Identifier parameter to identify home office assignments in the input occupant table. Occupant records returned by the query are assigned to a home office and are not assigned a point geometry. Home offices can also be assigned and managed in Indoor Space Planner.
- Load occupants as unassigned—Occupants can be loaded without being assigned to a space. If the field selected for the Unit Identifier (Input Occupant Table) parameter has a NULL or empty value, the occupant is loaded without an assignment and is not assigned a point geometry.
- Update occupant attributes—To update occupant attributes without updating space assignments in the Occupants feature class, run the tool without including values for the Input Unit Features, Unit Identifier (Input Units Features), and Unit Identifier (Input Occupant Table) parameters. Only fields mapped in the Occupant Attributes Mapping parameter will be updated.
- Update occupant geometry—To update occupant point geometry after creating a floor plan, run the tool without selecting an input for the Input Occupant Table parameter.
Occupant table requirements
The Input Occupant Table must include information that can uniquely identify each occupant and one or more fields that store occupant space assignment information. The Unit Identifier and the Occupant Identifier can be used to associate table records with building space features. Any field that is used to uniquely identify an occupant or unit, such as EMAIL for Occupants or NAME for units, can be used as the primary key field.
The following fields must be present in the source table:
You can optionally include the following fields in the input occupant table to populate them in the target occupants layer. If field values are present for occupant features they are displayed in Space Planner to provide additional information about occupants.
- CONTACT_EXTENSION—The occupant's extension number
- CONTACT_PHONE—The occupant's phone number
- ORG_LEVEL_1—The occupant's first organization level, such as a department. This field is used in Space Planner to support organization area planning.
- ORG_LEVEL_2—The occupant's second organization level, such as a team
- JOB_TITLE—The occupant's job title
- START_DATE—The occupant's start date
- SITE_ID—The occupant's associated site
You can add more fields that contain data related to occupants, such as employee ID number, as needed.
Occupant table fields
The following fields are created in the Occupants feature class and you can load data to them when you run the Update Occupant Features tool. You can create and store more fields in the Occupants feature class using the Add Field tool and load data into them to maintain more information about occupants before you run the Update Occupant Features tool. For example, you can create a field to maintain a secondary phone number or an employee ID number. You can use the Occupant Attributes Mapping parameter to load custom fields in the tool.
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 users will search for him in the app using Scooter Palmer. Use the KNOWNAS field to contain this known name.
Two occupants can have the same known name, but their email addresses should be different. In this situation, Indoors uses the EMAIL field to identify unique occupants. This field must contain a valid email address for each occupant to enable workspace reservations in the Indoors web and mobile apps.
CONTACT_PHONE
In this column, you can store phone numbers where the occupant can be reached directly. More characters or spacing in phone numbers is supported, but it is recommended that you 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 combines 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 the CONTACT_PHONE field and 0 in the CONTACT_EXTENSION field.
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 the CONTACT_EXTENSION field.
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 highest organization level the occupant is assigned to in your organization's hierarchy, such as a department. You can 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 want to filter by. This field is used in Space Planner to support organization area planning.
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 secondary organization level the occupant is assigned to in your organization's hierarchy, such as a team. You can 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 want to filter by.
JOB_TITLE
The Space Planner app includes filters to help users quickly find and assign occupants to spaces. Including this field in the input table and populating it with occupants' job titles allows 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 the input table and populating it with start dates for occupants allows you to filter by start date when assigning occupants to spaces, making it easier to evaluate space requirements by seniority.
SITE_ID
The unique ID of the feature’s associated site is recorded and can be used to identify the site feature in floor-aware maps. A feature can only be related to a single site using the SITE ID field. This field is only populated if you specifically map it using the Occupant Attributes Mapping parameter in the Update Occupant Features tool.
Load occupant data to the Occupants layer
To load occupant data to the Occupants layer in the Indoors model, complete the following steps:
- Prepare the occupant data as a geodatabase table, .csv file, or Microsoft Excel spreadsheet (.xls or .xlsx file).
Ensure that the required fields (KNOWNAS and EMAIL) are included, as well as any other fields you want to include.
- Run the Update Occupants Features tool.
Note:
If you are using Indoor Viewer or the Indoors mobile apps, the layer that contains the occupant data must be named People or Occupants.
The tool updates the input layer for the Target Occupant Features parameter using the table selected for the Input Occupant table parameter. New occupants are added, removed occupants are deleted, and matching occupants have their information updated.
The Update Occupant Features tool updates the ASSIGNMENT_TYPE values for units in the Units feature class that have occupants assigned and unassigned. The ASSIGNMENT_TYPE attribute drives specific features of the Space Planner app. Ensure that the ASSIGNMENT_TYPE value in the Units feature class is set to Office for spaces that are occupied before sharing the data to be used for Space Planner, Indoor Viewer, or Indoors mobile. In future updates of the occupants features, the tool will automatically update the ASSIGNMENT_TYPE value to reflect the latest occupant data.