IIoT, SCADA & Edge Connectivity calculator

Tag Mapping Workload Calculator

Estimate hours to map and validate plant tags. Enter the tag count being mapped (PLC to SCADA, OPC UA to MES, or legacy SCADA to new platform), the engineer mapping rate (tags per minute including type, scaling, and naming), and an allowance for PLC review, naming standardization, and end-to-end tag test. The calculator returns base hours and the loaded total.

What this calculator does

  • Estimate the engineering hours to map and validate plant tags between PLCs, SCADA, OPC UA, historian, and MES from the tag count being mapped, the engineer mapping rate (tags mapped per minute), and an allowance for PLC review, naming standardization, and tag testing.
  • Use it when an integrator or controls engineer is sizing the labor to migrate or expose a block of tags during a SCADA modernization, MES rollout, or unified namespace project.
  • It returns the engineering hours to map and validate a block of plant tags from PLC through SCADA, OPC UA, historian, or MES.

Formula used

  • Base tag mapping hours = tags to map ÷ (mapping rate × 60)
  • Required tag mapping hours = base hours × (1 + allowance)

Inputs explained

  • Tags to map and validate: Use the tag count being mapped between PLC, SCADA, OPC UA, historian, or MES (do not double-count if a tag is mapped through several layers; size each leg separately).
  • Engineer mapping rate: Use the integrator mapping rate (typical 1 to 5 tags per minute on clean PLC code, 0.2 to 1 on messy or undocumented PLC code).
  • PLC review, naming, and end-to-end test allowance: Add the share of mapping time spent reviewing PLC code, applying the naming standard (ISA-95, plant naming), and running end-to-end tag tests with operations.

How to use the result

  • Use it during SCADA modernization scoping, before issuing the integrator RFP, or when sizing a unified namespace or MES integration sprint.
  • It is a labor estimate. It does not size cutover risk; pair with the SCADA migration workload calculator and a cutover plan.

Common questions

  • Why use tags per minute instead of tags per hour? A per-minute rate keeps the math intuitive across small and large blocks. Multiply by 60 inside the formula to get tags per hour.
  • What rate is realistic on a brownfield PLC? Brownfield PLCs with messy types and missing comments usually slow mapping to 0.5 to 1 tag per minute. Greenfield PLCs with structured tags and clean Add-On Instructions support 3 to 5 tags per minute.
  • Why include a separate naming allowance? ISA-95 or plant naming standardization is real engineering work. Without an allowance, integrators consistently underestimate by 30 to 50 percent.
  • How do I model parallel engineers? Run the calculator at full hours and divide by parallel engineer count to get calendar duration. The hours number is what gets billed.

Last reviewed 2026-05-12.