The OfficeSpace Destination connector exports occupancy and presence data from the Mapped graph to OfficeSpace Software's presence management system. This destination connector synchronizes real-time occupancy information from sensors, spaces, and zones in Mapped to update presence status in OfficeSpace, enabling workspace management and utilization tracking.

Use Cases

• Real-time Workspace Utilization: Push occupancy sensor data to OfficeSpace to track desk, room, and floor utilization in real-time
• Presence Management: Automatically update presence status across multiple location types (desks, rooms, neighborhoods, floors, sites) based on sensor readings
• Unified Occupancy Reporting: Aggregate occupancy data from multiple sensor types to provide comprehensive presence insights in OfficeSpace

Configuration

Auth Requirements

To connect to OfficeSpace, you need:

• API Key: A valid OfficeSpace API key with permissions to create presence records
• Base URL: Your OfficeSpace instance URL (e.g., https://your-instance.officespacesoftware.com)

The connector validates credentials by attempting a test query to the OfficeSpace GraphQL API during setup.

Building Selection

It's required to select one or more Mapped buildings that contain occupancy data to sync

OfficeSpace Identities

Buildings, Floors, Spaces, and Zones in Mapped must have OfficeSpace external identities in the format: urn:officespace:{type}:id:{id}

• Supported types: site, floor, room, neighborhood, desk

The connector automatically discovers locations with valid OfficeSpace identities when processing occupancy data.

Mapped Concepts

Entities

This connector does not create entities in the Mapped graph. It is a destination connector that reads occupancy data from existing Mapped entities and exports it to OfficeSpace.

Entities Read by This Connector

The connector reads from the following Mapped entities:

• Building: Selected buildings containing occupancy data
• Floor: Floors with OfficeSpace identities
• Space: Spaces with OfficeSpace identities
• Zone: Zones with OfficeSpace identities
• Thing: Sensors and devices with hasLocation relationships to spaces

Points Read by This Connector

Point Type	Data Types	Description
Occupancy_Status	INT, DOUBLE	Binary occupancy status (0/1)
Temporary_Occupancy_Status	INT, DOUBLE	Temporary occupancy indicator
Occupancy_Count_Sensor	INT, DOUBLE	Number of occupants detected
Occupancy_Sensor	INT, DOUBLE	General occupancy sensor reading
PIR_Sensor	INT, DOUBLE	Passive infrared motion detection

The connector uses the latest: true option to retrieve only the most recent value for each point.

Supported Value Types: The connector can extract numeric values from any of the following timeseries value fields:

• float32Value
• float64Value
• int32Value
• int64Value
• uint32Value
• uint64Value

Enumerations

The connector maps Mapped occupancy point types to OfficeSpace presence statuses:

Mapped Point Type	OfficeSpace Status	Description
Occupancy_Status	PRESENCE or NO_PRESENCE	Direct occupancy indication (1 = present, 0 = not present)
Temporary_Occupancy_Status	PRESENCE or NO_PRESENCE	Temporary occupancy indicator
Occupancy_Count_Sensor	PRESENCE or NO_PRESENCE	Presence determined by count > 0
Occupancy_Sensor	PASSIVE_PRESENCE or NO_PRESENCE	Motion/activity-based presence detection
PIR_Sensor	PASSIVE_PRESENCE or NO_PRESENCE	Passive infrared sensor detection

Occupancy Count: For Occupancy_Count_Sensor points, the actual count value is included in the presence data. For other point types, count is set to 1 when present.

Sync Behavior

The connector runs on a 60-second polling interval, continuously:

• Fetching the latest occupancy data for all selected buildings
• Identifying locations with valid OfficeSpace identities
• Transforming occupancy values to OfficeSpace presence status
• Sending presence updates to the OfficeSpace Presence API

Note: Only locations with properly formatted OfficeSpace external identities (urn:officespace:{type}:id:{id}) will receive presence updates.