FireTPM is Innovative

Reduced Data Volume and High Performance Architecture​​

Over 99% reduction in data volume and data querying / processing time

 

Weekly Volume Plans (Columns vs Rows)

• Challenge: It takes a lot of data storage and a lot of query time to retrieve weekly volume records.

• Solution: Store all weekly volumes records for a planning year as fields on a single record.

• Benefit:

  • 98% data volume reduction

  • 99+% data querying/processing reduction

​

Volume Plan Granularity (Monthly vs Weekly)

• Challenge: Regional Account Managers want to plan at the Monthly level whereas Key Account Managers need to plan at the Weekly level.

• Solution: Enable planning at both  levels of Time hierarchy so that each Account Manager can plan at the level they need/want.

• Benefit:

  • 75% data volume reduction

  • 75% data querying/processing reduction

  • Reduced data entry requirements  and improved end user experience

​

Promotion Structure (SubAccounts vs Planning Accounts)

• Challenge: A single Wholesaler, RSM can create a Channel Promotion for 100 or more small C-Store retailers, which creates a lot of data.

• Solution: Have SubAccount Promotion headers reference the parent promotion details rather than copying all details to children Promotions.

• Benefit:

  • 90% data volume reduction

  • 90% data querying/processing reduction

  • Ability to handle modern and traditional trade markets in a single instance 

​

Product Hierarchy (PPG’s vs SKU’s)

• Challenge: Entire Promoted Product Groups (5+ SKU’s) are usually promoted together, but sometimes only a SKU, forcing the entire system to be at the SKU level.

• Solution: Enable dynamic PPG definitions to  prevent unnecessary blow down of Account Plans and Promotions to SKU level.

• Benefit:

  • 80% data volume reduction

  • 80% data querying/processing reduction

  • Reduced data entry requirements  and improved end user experience

 

Formula Fields (1:M vs M:M)

• Challenge: Entire Promoted Product Groups (5+ SKU’s) are usually promoted together, but sometimes only a SKU, forcing the entire system to be at the SKU level.

• Solution: Enable dynamic PPG definitions to  prevent unnecessary blow down of Account Plans and Promotions to SKU level.

• Benefit:

  • 80% data volume reduction

  • 80% data querying/processing reduction

  • Reduced data entry requirements  and improved end user experience