“Financial Calculation” scripting

Agenda:

  • Add an additional week-by-week comparison layout
  • Fill in the Calculation processing layout: Priority 1
    • Company summary (clones)
    • CEC summary (clones)
    • Month-by-month fields (clones)
    • Day of week (clones)
    • Week-by-week fields (standard fields): up to 12: Priority 2
    • Week-by-week fields (clones): up to 12: Priority 2
    • Week-by-week fields (standard fields) 13 to 52: Priority 2
    • Week-by-week fields (clones): 13 to 52: Priority 2
    • Hourly (clones): Priority 2
  • Code: Priority 1
    • Company summary
    • CEC summary
    • Company monthly
    • Company days of week
    • Company weekly (up to 12, and 52): Priority 2
    • Company hourly: Priority 2
  • Hook up buttons and scripting in 3.0 Brain:
    • Move to “Suspense” layout and open find
    • Manually activate (View Numbers)
  • Tighten up design

Merchant A.I. applications

Update Merchant Owner Manual for statistics: Create a narrative for each of the 5 layouts. Add a synopsis paragraph looking at a decision process involving all layouts (tell a story).

  • Summary
  • Month
  • Day of week
  • Weekly: hold
  • Hour: hold

___________________________________________

Programming and thoughts:

  • Assumptions: rework numbers to reflect new compensation numbers
    • 3.0 corporate: .30 / .015
    • Node alliance: .70 / .035
      • Lead CEC / Node organization: .20 / .010
      • Merchant sales rep: .25 / .0125
      • Member referral source (CEC): .25 / .0125
  • Break apart (month, week, day and hour) during the initial Transaction
  • Loop within a loop. Inside loop is the calculations.
    • Loop test – Total to date
  • When calculating components (hourly, weekly, monthly) begin with an “If statement” to segment out only the relevant transactions
  • Incorporate Merchant sales/compensation into the CEC layout:
    • Build in a field in Company database with the CEC number of sales rep (or Lead Node CEC – who will have a 999 type number like in the Employee database)

______________________________________________________________________________

______________________________________________________________________________

Member statistics: month / year / total — 2nd Priority

  • total Member points redeemed
  • average transaction amount per Member
  • number of transactions
  • average points redeemed per transaction (probably not)
  • purchase ‘sub-niche’ (if they can contain some uniformity)
  • narrative notes on Members (include universal keywords that could prompt ‘HELP’ action or update interest information) ~ the Merchants employees are eyes and ears “On the Street”. This can also give subjective insight on the Merchant — much a like an involuntary suggestion box
    • I have a transfer from the Transactions to Relationship database. But it doesn’t aggregate into a central place in Members database. But should it. Current there is an “Intervene” field that could be programmed as a flag sent to someone (e.g. stakeholder or public authorities)
      • Add this into training instructions
      • There could be an archive feature added to the Members database also – but that might be a bit much (privacy issue)