Estimator Dashboard

the estimator dashboard simulates a pad export for your selected scope and produces effort estimates for migrating each call tree — including how much blueprint saves versus manual rewrite and how much work remains to bring migrated code to production ⓘ the estimator supports per call tree view only accessing the estimator dashboard select rpa dashboards and reports from the navigation bar click estimator click change scope in the top right, select your scope, and click ok see using scope and view ⓘ blueprint simulates a pad export to generate estimator metrics calculations are not run automatically by default once a scope is selected, initiate a calculation job to populate stats while a calculation is in progress, estimator stats are unavailable monitor status in jobs see jobs docid\ ggdafdipismxvtx9xlxao for details dashboard controls recalculate estimations — reruns calculations after a blueprint upgrade or after changes to processes in the current scope to ensure estimates reflect the latest mappings refresh — reloads current data in the dashboard adjusting estimation parameters the center of the dashboard compares two effort estimates side by side without blueprint (manual rewrite) on the left and with blueprint (automated conversion) on the right both estimates are driven by parameters you can adjust to match your team's capacity and working speed as you change any parameter, the estimates, the hrs saved and % faster indicators, and the effort breakdown update in real time without blueprint — manual rewrite this panel estimates the effort to rewrite the selected scope by hand, with no blueprint assistance it multiplies the total actions in scope by the rate at which your team can manually recreate them in pad actions/hr — the number of source actions your team can manually rewrite per hour set this to reflect your team's realistic manual rewrite speed for the source platform the resulting manual rewrite total effort is the baseline against which blueprint's savings are measured with blueprint — automated conversion this panel estimates the effort to bring blueprint's migrated pad code to a production ready state it shows the estimated completion effort , along with hrs saved and % faster relative to the manual rewrite baseline team size — select how many people will work on completing the migration ( 1 , 2 , 3 , 5 , or 5+ ) this does not change the total effort in hours; it spreads that effort across the team to produce the estimated calendar time, shown to the right as an approximate number of weeks effort breakdown the effort breakdown divides the remaining post migration work into three categories, each shown with its item count, an adjustable fixes/hr rate, and the resulting effort in hours the donut chart visualizes how the total effort is distributed across the three categories for each category, set fixes/hr to the number of items a team member can resolve per hour effort is calculated as items ÷ fixes/hr todos — items flagged with blueprint todo comments that a user must address to make the bot production ready compiler errors — errors in the generated pad code that must be resolved for the flow to compile selectors — ui selectors that may need attention after migration for selectors, an additional field sets the % needing re spy — the portion of selectors expected to require re spying (re capturing the target element) rather than a simpler fix raising this percentage increases the selector effort enabling automatic calculations in estimator ⚠️ enabling this option will increase import time by default, estimator calculations are not triggered automatically on import to enable automatic calculation on import open settings from the navigation bar expand rpa management select dashboards and reports check automatically calculate estimations on import