The ToolWatch CMiC integration is focused on two goals:
To enable personnel to be able to accomplish their job(s) using a single system, whether that system is CMiC or ToolWatch
Enable Job Cost and Billings calculated in ToolWatch to be sent back to CMiC to charge the associated Jobs, Phases, and Equipment
This integration approach assumes that CMiC will be used for accounting and project management, and that ToolWatch is used for inventory.
CMiC | Sync Direction | ToolWatch |
PY Employees | → | Employees |
JC Jobs | → | Cost Centers |
JC Jobs | → | Locations |
JC Phase Codes | → | Cost Codes |
JC Master (Global) Phase Codes | → | Cost Codes |
EM Equipment | → | Items |
For Cost Centers, Locations, and Cost Codes, the Description can be reformatted using a configurable template (combining the source Number, Description, and other tokens) rather than a plain copy of the source Name.
A ToolWatch Employee will be created for every PY TAXEMP in CMiC. The following fields will be mapped:
CMiC PY TAXEMP | ToolWatch Employee | Notes |
EmpOraseq | Employee ID | Behind the scenes, these CMiC and the ToolWatch records are related by their underlying ID fields. These fields are not user-facing, which means that it's not possible for a user to "break the integration" by making a change in the UI of either system. When using the API V1 connection, the employee's UUID (EmpVUuid) is used as the underlying key instead. |
EmpNo | Number |
|
EmpFirstName | First Name |
|
EmpLastName | Last Name |
|
EmpFirstName, EmpLastName | Description | The CMiC EmpFirstName and EmpLastName will be combined to match the ToolWatch Description format of "LastName, FirstName". |
EmpEmailAddress |
| |
EmpPhone | Phone |
|
EmpStatus | Inactive | The integration can be configured to specify which Statuses represent an active Employee. |
A ToolWatch Cost Center will be created for every JC Job in CMiC if the Job is active. If the Job is not active, but it exists in ToolWatch it will be synchronized. If the synchronized Job becomes inactive the ToolWatch Cost Center will become inactive with all associated Cost Codes.
The following fields will be mapped:
CMiC JC Job | ToolWatch Cost Center | Notes |
JobObjectOraseq | Cost Center ID | Behind the scenes, these CMiC and the ToolWatch records are related by their underlying ID fields. These fields are not user-facing, which means that it's not possible for a user to "break the integration" by making a change in the UI of either system. |
JobCode | Number |
|
JobName | Description |
|
Status Code | Inactive | The integration can be configured to specify which Statuses represent an active Job. |
By default, a ToolWatch Location will be created for every JC Job in CMiC if the JC Job is active. If the ToolWatch Location exists and is mapped to the JC Job - it will be synchronized. This is not strictly necessary in order to properly accrue Job Costs and Billing in ToolWatch, and have those charges flow back into CMiC , but it is generally convenient in ToolWatch to be able to assign the assets to the Job when you are going to begin charging the Job for the assets. The Location and Cost Center will be linked in ToolWatch so that by default all assets assigned to the Location are charged to the corresponding CMiC Job.
The following fields will be mapped:
CMiC JC Job | ToolWatch Location | Notes |
JobObjectOraseq | Location ID | Behind the scenes, these CMiC and the ToolWatch records are related by their underlying ID fields. These fields are not user-facing, which means that it's not possible for a user to "break the integration" by making a change in the UI of either system. |
JobCode | Number |
|
JobName | Description |
|
- | Cost Center | The Cost Center associated with this CMiC Job will be set as the Cost Center for this ToolWatch Location. This means that if assets are transferred to this ToolWatch Location, they by default will be charged to the associated ToolWatch Cost Center (CMiC Job), unless the user specifies otherwise. |
Status Code | Inactive | The integration can be configured to specify which Statuses represent an active Location. |
When using an ODBC-based connection, the CMiC job-site address is also synced to the Location - street address, PO box, city, state, and zip map to the Location's Address, Address 2, City, State, and Zip. The Direct API and API V1 connection methods do not populate these address fields.
A ToolWatch Cost Code will be created for every JC Phase Code in CMiC. If a JC Phase Code is associated with a JC Job, and both are synced to ToolWatch as a Cost Code and Cost Center respectively, then the Cost Code will be linked to the Cost Center. Cost Codes will be created if the parent of JC Phase Code (JC Job) is active.
The following fields will be mapped:
CMiC JC Phase Code | ToolWatch Cost Code | Notes |
GjjpObjectOraseq | Cost Code ID | Behind the scenes, these CMiC and the ToolWatch records are related by their underlying ID fields. These fields are not user-facing, which means that it's not possible for a user to "break the integration" by making a change in the UI of either system. |
GjjpCode | Number |
|
GjjpName | Description |
|
GjjpJobCode | Cost Center | The CMiC Job that this Phase Code relates to will be located by looking for the CMiC Job with the matching value for GjjpJobCode. |
Record Status | Inactive | The integration can be configured to specify which Statuses represent an active Phase Code. |
CMiC master (global) phase codes can also be synced directly as ToolWatch Cost Codes, independent of any Job or Cost Center. This is a separate, optional sync (the "Sync Global Cost Codes" setting) and is only available when using the API V1 connection method.
CMiC Master Phase Code | ToolWatch Cost Code | Notes |
Master Phase Code | Number |
|
Master Phase Description | Description |
|
- | Cost Center | Master phase codes are not linked to a Cost Center. |
A ToolWatch Item will be created for every EM Equipment in CMiC. An Item is created the first time the equipment is synced; later changes to that equipment in CMiC are not applied to the existing ToolWatch Item. The following fields will be mapped:
CMiC EM Equipment | ToolWatch Item | Notes |
EmeEqpCode | Item Number | Behind the scenes, these CMiC and the ToolWatch records are related by their underlying ID fields. These fields are not user-facing, which means that it's not possible for a user to "break the integration" by making a change in the UI of either system. |
EmeFastMakeName | Item Manufacturer | A ToolWatch Manufacturer will be created if required. |
EmeEqpclassCode | ToolWatch Master Category Number | A ToolWatch Master Category will be created if required. |
EmeEqpclassName | ToolWatch Master Category Description | A ToolWatch Master Category will be created if required. |
EmeFastCatCode | ToolWatch Item Class Number | A ToolWatch Item Class will be created if required. |
EmeFastCatName | ToolWatch Item Class Description | A ToolWatch Item Class will be created if required. |
EmeDesc | Item Description | A ToolWatch Description will be created if required. |
EmeName | Item Model | A ToolWatch Model will be created if required with Manufacturer, Category, Class and Description above. If CMiC asset information is not present Equipment Name will be used. |
EmeFastModelName | Item Model | A ToolWatch Model will be created if required. See notes above. |
EmeFastModelYear | Item Model Year | A ToolWatch Model will be created if required. |
EmeLegalUniqueIdentifier | ToolWatch Item Serial Number |
|
EmeFastLicNumberCode | Item License Number |
|
EmeFastLicExpDate | Item License Expiration Date |
|