The bleedingEDGE brain map

_______________________________________________________________________________

System access and security

  • Use a third party access system (if applicable)
  • Front Porch access via web browser
    • Front Porch number
    • Password
  • Resident access via API
    • Phone number
    • Password: FileMaker is deficient for passwords since it doesn’t take into account the entire entry

_____________________________________________

Purchase engagement input at the physical Front Porch

  • API interface working with FileMaker backend (even on employees personal phone)
    • API will be separate from Resident API (but will coincide with Front Porch desktop interface)
    • I have to do some more thinking about this (any downsides)
  • Follow through the flow (including the database set-up)
  • 1st check for Resident status. Kick into Creation of a new Resident/patron.

_____________________________________________

Financial calculations

  • Narrative contents
    • Goals of the calculations: provide marketing consultation base, trigger Melvin nudges to support Front Porches in needed areas (overall sluggish sales, day or time sales assistance)
    • Thoughts on Phase 2 ideas
  • Possibly build out a consultation page in Melvin’s web site

_____________________________________________

Non-purchase engagement input at the physical Front Porch

  • This will probably be a geo-app
    • Sending the nudge to the email will involve an additional code block integrated into the triggers (it’s probably already scripted: “You all come back now”
    • A purchase or previous “You all…” nudge would disengage the nudge
    • Possibly trigger a coop nudge upon leaving (either pushing the sponsor or a different Front Porch)
  • What are the applications for this. It could roll into a geofence (for recording purposes only)

_____________________________________________

Geofencing input (nests)

  • Strategize several possible applications and design corresponding algorithms
  • The input software will grab the ID (phone number) of the Resident

_____________________________________________

Creation of a new Resident/patron

  • Create a new Resident and patron at a Front Porch
  • Create a new Resident at a pop-up (or similar)
  • Create a new Front Porch patron from a current Resident
  • Use existing code. Pay attention to layout pop-ups issue. It may resolve itself when an API is used.

_____________________________________________

Adding a new employee

_____________________________________________

Associate CEC sign-up and dispatching

  • This component includes the application process (reference form and other narrative – wherever it’s at)
  • DON’T KNOW ABOUT THIS: Create a separate blog post with a comments section that will go to each Lead CEC of each Node for approval
  • Melvin uses this nudge campaign as a communication tools for Associate CECs. Add a dedicated campaign layout to be used only by Melvin (that selects all Associate CECs)

_____________________________________________

“A Look in the Window” assessment to Action Point programs

  • Begin with standard Action Point calculation and then adjust Action Point alterations
    • Action Point calculation flow. It’s likely only to be a couple lines of code with long strings of calculations. Follow what I already have.

_____________________________________________

Engagement database development

  • Designate whether the nudges are for email or nest output
  • How much should I pull from the Engagement Database vs. the campaign layout in the Company database
  • These’s an entire strategy behind the purpose of the Engagement Database

_____________________________________________

Front Porch engagement trigger/campaign creation

  • This is already coded (except to adjust for Action Points – I think)
    • Detail the major code block flow.
    • Pull out embedded code blocks that should be laid out separately and accessed that way
  • Random Melvin’s site page (probably no value)

_____________________________________________

Action Point sort for output to daily email file

  • Use current Sort and output scripting
    • Prepare for output files. Create a different file for each time to be sent.
    • Use a select number of output times (determined via pulldown menu selected by Resident)

_____________________________________________

Nudge output via email

  • Prepare files as per vendor specs

_____________________________________________

Geo-app coding (nests)

  • Narrative: build a specific page in Melvin’s site for nests
    • Summarize the piece

_____________________________________________

Real time nudge output via text (geofences)

  • Work with vendor specs

_____________________________________________

Front Porch desktop interface

  • Determine the software/access conduit

_____________________________________________

Mobile app development (API)

  • Resident API (The Rabbit Hole)
  • Determine the front end software that will pull and send input to the back end and and pull calculated returns back end. An app software is really no different than a FileMaker layout.

_____________________________________________

Food.IQ input (Lead CEC or agent)

  • Work with a FileMaker front end where Lead CECs will enter in initial/revised Food.IQ data

_____________________________________________

Food.IQ calculations

  • FileMaker sub-routine
  • Use FileMaker and work from the same methodology as the “Mirror”. In fact the format will be pretty much the same as the Member’s database in FileMaker
  • Calculations will be done within a few long string calculation lines – just like the Member’s assessment

_____________________________________________

AWS integration

  • Filemaker Pro upgrade
  • AWS set up
  • Integration

_______________________________________________________________________________

Notes:

  • If I use FileMaker, I may have to divide the database up into separate ones for each Node (or group of Nodes) to keep the processing at a minimum.
  • Component page outline:
    • Narrative description of segment
      • Start with notes
      • Goals of the segment
      • Include concerns in optional last paragraphs
    • Algorithm description (narrate as much as possible)
      • How I’m going to get done what I want
    • FileMaker code segments (if applicable)
      • Possibly include in Algorithm section
      • List top level code hierarchy (determine when I look at it)
    • Software suggestions
      • Evaluate options and discuss plusses and minuses
    • Cloud (AWS) integration