Performance Impact — Work Zone Key Derivation via Message Scenarios and Work Zone Key Volume

Summary:

In our FFS implementation, the same ZIP code belongs to multiple departments across different Business Functions. FFS does not allow the same Work Zone Key in different Work Zones. Using ZIP code alone as the Work Zone Key causes routing conflicts — FFS cannot identify the correct technician pool fo

Solution Designed

We created a custom activity property called business_department which is populated via FFS Message Scenarios triggered on Activity Create. The Work Zone Key is then derived as:

Work Zone Key = ZIP Code + business_department
e.g. 78006 + GASPC = 78006GASPC

We have two approaches depending on ZIP coverage:

Approach A — Each department gets its own unique business_department code → More message scenarios, more workzones and more work zone keys