Question of the Week – DESTINI Profiler and DESTINI Estimator: Why do my variables have weird Units of Measure during takeoff when I open a Profiler Assembly inside Estimator?

Questions of the Week are asked and answered in the Beck Technology Community. Anyone is encouraged to join the community to discover additional tips and tricks.

Why do my variables have weird Units of Measure during takeoff when I open a Profiler Assembly inside Estimator?

This answer is provided by Casey Wilt, implementation specialist, and posted on our community as well as below.

Profiler and Estimator use variables in totally distinct ways.  In formulas intended for use in Profiler, you have access to both Parametric and User-Defined Variables. When you add an assembly in Profiler, there is no “takeoff” window, and the Parametric variables quantities used in the formulas are automatically populated and you can then tweak your UDVs in the “Contributing variables” tab. (Area, Perimeter, etc. – already known and accepted in Profiler).

Estimator, however, has no concept of the parametric variables that Profiler uses. Therefore, if you use a Parametric (Area, Perimeter, etc), it is seen as a pseudo-UDV and assumes the UoM of the line item it is used to quantify. For this reason, I make sure that any variable I use in an Estimator formula is first created in the Variables tab in Data Manager.

In sum, Estimator assemblies and formulas should all use UDVs, and Profiler assemblies and formulas can use both Parametric and UDVs. Still, a Profiler assembly can be opened in Estimator and used just fine, the takeoff window is just slightly “messy”.