FAMIS 360 Destination
The FAMIS 360 Destination connector sends Work Orders from the Mapped graph into FAMIS 360, a CMMS commonly used in higher-education and facilities-management environments. It reads existing Work Order context from Mapped, creates or updates the corresponding FAMIS 360 record, and writes the FAMIS 360 Work Order identity back to the same Mapped Work Order.
Use Cases
- Centralized Work Order dispatch: Use Mapped as the hub for Work Orders from multiple systems and route them into FAMIS 360 for execution.
- Round-trip FAMIS 360 workflows: Pair with source connectors so Work Orders can be created in Mapped, enriched with graph context, and then managed in FAMIS 360.
- Controlled migration and replay: Backfill historical Work Orders by date range or by specific IDs during rollout or remediation.
Configuration
Auth Requirements
The connector uses FAMIS 360 username / password authentication.
| Field | Required | Description | Where to Find |
|---|---|---|---|
| Base URL | Yes | Your FAMIS 360 instance URL | Your FAMIS 360 administrator (for example https://your-instance.famis360.com) |
| Username | Yes | Username used to create and update Work Orders in FAMIS 360 | Your FAMIS 360 administrator |
| Password | Yes | Password used to access the FAMIS 360 API | Your FAMIS 360 administrator |
Use credentials with permission to create and update Work Orders.
Building Selection
The place-mapping step is used only to choose which FAMIS 360 buildings are in scope for Work Order synchronization.
| Selection | Required | Notes |
|---|---|---|
| Selected buildings | Yes | Only Work Orders related to these buildings are sent to FAMIS 360 |
Notes
- New Work Orders must be related to a Space that already has a FAMIS 360 space ExternalIdentity.
- Building selection acts as a safety boundary so only approved locations are synchronized.
Work Order Field Mapping
The connector provides field mapping for the main FAMIS 360 Work Order classification fields.
| Mapped Work Order field | FAMIS 360 field |
|---|---|
| Job Priority | Request Priority |
| Sector | Request Type |
| Problem Description | Request Sub Type |
| Job Type | Work Type |
| Job Status | Status (updates only) |
Each mapping supports these behaviors:
| Option | Description |
|---|---|
| Enable / disable mapping | Pass mapped values, or leave the original graph value unmapped |
| Default value | Use a fallback FAMIS 360 value when no explicit mapping is found |
| Undefined-only mode | Apply the default only when a source value has no explicit mapping |
The connector also refreshes FAMIS 360 request-type / request-sub-type and building / request-type relationships so valid combinations can be reviewed before sync.
Advanced Options
Historical Data Backfill
The data backfill lets you re-send or re-sync Work Orders that might have had changes or corrections.
| Mode | Description |
|---|---|
| Date range | Reprocess Work Orders created or updated during a selected time window |
| Specific IDs | Reprocess only the listed Mapped Work Order IDs. This must be the Mapped entity Id for the Work Order(s). |
Backfill uses the same create / update rules as normal polling.
Mapped Concepts
API to Mapped Entities
| FAMIS 360 destination behavior | Mapped entity | Exact type | Notes |
|---|---|---|---|
| Created or updated FAMIS 360 Work Order | WorkOrder | WORK_ORDER | Existing Mapped Work Order remains in place; the connector adds or preserves the FAMIS 360 identity |
| Synced FAMIS 360 identity | ExternalIdentity on identities | N/A | Written as urn:famis360:workorder🆔<id> |
Polling & Syncing Behavior
| Function | Frequency | Description |
|---|---|---|
| Work Order poll | Every 1 minute | Processes new and updated Mapped Work Orders for the selected buildings. On the first run, it looks back 2 hours. |
| Historical backfill | On demand | Replays Work Orders by date range or by specific Work Order IDs |
| Relationship refresh | First poll and on demand | Refreshes request-type, request-sub-type, and building relationship data used by the mapping workflow |
| Deprovision | On connector removal | Clears connector action state |
Syncing Requirements for Work Orders
- A related Space with a FAMIS 360 space identity
- Requestor information from a related person on the Work Order
- The related Space must be located in one of the selected buildings
Sample Code
The below query shows the related Space and identifies for FAMIS 360 Work Orders. Read more about Work Orders.
{
workOrders(filter:{connectedDataSourceId:{eq:"your-connector-Id"}}){
id
name
jobPriority
jobStatus
jobType
summary
dateCreated
mappingKey
identities {
... on ExternalIdentity {
__typename
value
}
}
relatesTo {
...on GenericPlace {
id
name
exactType
mappingKey
identities {
...on ExternalIdentity {
__typename
value
}
}
}
}
}
}