The integration between Benchmark and Workbench is done with a flat file exported from a Benchmark project and can be imported either into a Workbench Job’s Budget or a Workbench Quote Costsheet.
The key for this integration is the data mapping for Workbench Activity Codes and Workbench Work Centre Codes.
Benchmark currently derives the Workbench Activity Code from a configurable setting:
Directly from Resource Code, or
A mapping using the Resource Category
The most commonly used method is the Resource Code as Activity Code, and this is the one that will be explained below.
For the import to be successfull
Benchmark Project Resource Code must match Workbench Activity code
Benchmark Project Resource Cost Code must match Workbench Work Centre Code
Importing the file generated by Benchmark
The csv file generated by Benchmark can be imported into a Job’s Budget. Things to consider:
Budget mus be cerated first
Budget’s input must be At Revenue & Cost Element (not At Cost Element, nor At Activity, Work Centre), which has Revenue lines and cost lines under each Revenue line. The Revenue lines are Benchmark Project Items, and the Cost lines are the Benchmark Resources.
Import stored procedure is Benchmark Budget Import.
Create remove any lines that ave a Line Rate = 0.
Tips to troubleshoot errors:
If you get an error and a line number, only leave the line that causes the error and try to import.
Technical details about the Resource data mapping between Benchmark and Workbench
A key rule used in this export file from Benchmark to Workbench relates to how Resources are classified and “mapped” between the two systems. The following Table explains this mapping and is provided for your information: