Configuring Data Sync
This allows you to link the D4H products, Operations Center (Incident Management & Alerting), Personnel & Training, and Incident Reporting; to enable data exchange between them. Once connected, you can sync personnel and Group data between Personnel & Training and Operations Center, and push key data from Incident Management into Incident Reporting (for incidents) or Personnel & Training (for exercises/events) when an incident channel is shut down.
🔑 ACCESS LEVEL REQUIRED: Account Owner
⚠️ ATTENTION: Both D4H Operations Center and Team Manager platforms must be residing in the same region in order for the synchronization to be successful. If your account is not residing in the same region, please drop us a request to help@d4h.com to migrate your account to the correct server and we will then share the next steps.
- Before getting started, ensure your Operations Center and Team Manager accounts are connected. If you do not see a Team Manager URL under Integrations, the connection has not yet been set up. Your team’s administrator can contact the Help Desk to request this and should include both account URLs.
- Next, go to the Admin Area
- Expand Integrations
- Click on Team Manager
ℹ️ NOTE: If you have D4H Personnel & Training in Team Manager and Operations Center, please ensure you follow all the two-way data synchronization steps shown below 1 – 18.
However, if you only have Incident Reporting in Team Manager and Operations Center, you will only need to follow the one-way data synchronization steps 1 – 4 & 14 – 18.
Two-way data synchronization
Two-way data synchronization (required if you have Personnel & Training in both Team Manager and Operations Center) enables syncing of Groups and Personnel/Members by following steps 1–4 and 5–18 below:
Sync Groups (Two-way)
- Select Setup under Groups
⚠️ ATTENTION: Resolve any conflicts Requiring action between the accounts and make sure that the results of the data reconciliation matches your expectations. If a group is matched on both systems, the name can be synchronized, otherwise it will be created on the other system. If there are conflicts, you will need to manually resolve them (e.g. Update Groups in Team Manager to match what is in Operations Center or visa versa) and then select Reload before proceeding.
- Once 2-way sync is ready, select Enable sync
- Proceed with assigning the Group to each personnel
- Resync as needed after making updates in Team Manager
Sync Personnel (Two-way)
- Make sure the Personnel template is updated first if you want to import additional details from the Personnel & Training member profile custom fields
- Select Setup under Personnel / members
- Select the dropdown and choose the Team Manager field equivalent to sync with Operations Center
⚠️ ATTENTION: Resolve any conflicts Requiring action between the accounts and make sure that the results of the data reconciliation matches your expectations. If a member/personnel exists on both systems, the name can be synchronized, otherwise it will be created on the other system.
- Once 2-way sync is ready, select Enable sync
- Proceed with granting access to the synced member/personnel in the appropriate account, as needed
One-way data synchronization
One-way data synchronization (required if you only have Incident Reporting in Team Manager and Operations Center) allows incidents to be exported from Operations Center to Team Manager by following steps 1–4 and 14–18 only:
- Check the option “Export incidents to Incident Reporting”
- Click Setup
- Define how the Situation fields in Operations Center map to Team Manager incidents, exercises, or events.
- Click next
- When you see the message “You are now ready to switch to the new Incident Reporting setup”, click Enable Sync
⚠️ ATTENTION: Resolve any errors Requiring action to proceed. Create any necessary custom fields in Team Manager to properly map the Incident Manager summary report fields.
After Setup: Important Rules to Keep Sync Working
Once synchronization is enabled, there are a few field mapping and formatting rules that must be followed to avoid errors.
See Data Synchronization: Common Errors & Field Mapping Rules article for full details