IIoT, SCADA & Edge Connectivity worked example
SCADA Migration Workload at 69% fat, sat, validation, and cutover allowance: a worked example
What does the result look like when fat, sat, validation, and cutover allowance reaches 69%? The full calculation is worked below with real intermediate numbers. Use it when an integrator or controls lead is sizing a SCADA migration sprint (legacy SCADA to Ignition, Wonderware, AVEVA, or FactoryTalk View) before quoting the project.
The inputs for this scenario
- Screens or program organization units (POUs) to migrate: 260 screens (unchanged)
- Engineer migration throughput: 1 screens / hr (unchanged)
- FAT, SAT, validation, and cutover allowance: 69 % (raised for this scenario; the documented default is 60)
Working through the calculation
- Applying the documented formula (Base SCADA migration hours = screens or POUs รท engineer rate) to the inputs above produces each figure below.
- At this operating point the engine returns 439 hr for required scada migration hours, the number this scenario is built around.
- At this operating point the engine returns 260 hr for base scada migration hours.
- At this operating point the engine returns 69 % for fat, sat, and cutover allowance.
- At this operating point the engine returns 1 pieces / min for engineer migration rate.
How this compares with the baseline
- Against the tool's baseline example, where fat, sat, validation, and cutover allowance sits at 60% and the headline result is 416 hr, this scenario comes in 5.62% above the baseline at 439 hr.
- A figure at this level is achievable when fat, sat, validation, and cutover allowance is genuinely sustained, not just peaked for a shift. It assumes a uniform per-screen rate; a graphics-heavy mimic with embedded scripting and alarm logic can take 5x a simple status screen, so blend rates or segment the count for mixed estate.
Results at a glance
- Required SCADA migration hours: 439 hr (headline result)
- Base SCADA migration hours: 260 hr
- FAT, SAT, and cutover allowance: 69 %
- Engineer migration rate: 1 pieces / min
Run it with your numbers
- Every input above is editable in the live SCADA Migration Workload calculator, which recalculates instantly and can be shared with the inputs intact.
Last reviewed 2026-05-12.