The bleedingEDGE brain map

bleedingEDGE activity summary:

Include notes for each of the components, including access to current algorithm, code (FileMaker script name(s)) and software to be used. Create a flow diagram connecting everything – including operation in in the cloud AWS. See IcePanel.

Create separate Rabbit Hole posts for each component

  • Narrative description of segment
    • Start with notes
    • Goals of the segment
    • Include concerns in optional last paragraphs
  • Algorithm (narrate as much as possible)
    • How I’m going to get done whatI want
  • FileMaker code segments (if applicable)
    • Possibly include in Algorithm section
    • Summaries only
    • Link to specific pages
  • Software suggestions
    • Evaluate options and discuss plusses and minuses
  • Cloud (AWS) integration

_______________________________________________________________________________

Create a mobile app

  • Determine the front end software that will pull send input to the back end and and pull calculated returns back. An app software is really no different than a FileMaker layout.

_____________________________________________

Purchase engagement input at the physical Front Porch

  • App software interface working with FileMaker backend
  • Follow through the flow (including the database set-up)
  • 1st check for Resident status. Kick into “Creation of a new Resident – purchase” if no record exists
  • Design a standalone interface to be used by the employee (review the current FileMaker interface)

_____________________________________________

Non-purchase engagement input at the physical Front Porch

  • This will probably be a geo-app
  • What are the applications for this. It could roll into a geofence (for recording purposes only)

_____________________________________________

Geofencing input

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

_____________________________________________

Creation of a new Resident to Melvin’s Neighborhood (via purchase at Front Porch)

  • Takes input from Merchant engagement and sends it to FileMaker backend for processing
  • Pretty cut and dry. Work off the purchase process.

_____________________________________________

Creation of a new Front Porch patron at their location (including employee reference)

  • This component is a subset of the “Purchase engagement at the Front Porch”
  • Takes input from Merchant engagement and sends it to FileMaker backend for processing

_____________________________________________

Creation of a new Resident to Melvin’s Neighborhood independent of a Front Porch

  • Pop-ups, NGOs, schools (including fundraising efforts)
  • Create an interface only with an automatic “0” purchase – otherwise should be same as the merchant purchase interface

_____________________________________________

Associate CEC sign-up

  • This component includes the application process (reference form and other narrative – wherever it’s at)
  •  Create a separate blog post with a comments section that will go to each Lead CEC of each Node

_____________________________________________

“Window” assessment to Action Point programs

  • FileMaker sub-routine
  • Include the 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.

_____________________________________________

Front Porch engagement trigger/campaign creation

  • FileMaker sub-routine
  • This is already coded (except to adjust for Action Points – I think)

_____________________________________________

Geo-app coding

  • FileMaker sub-routine

_____________________________________________

Action Point sort and output to daily email file

  • FileMaker sub-routine
  • Follow the same methodology as the BE programming, except of the introduction of Action Points
  • Include text file sort/output also

_____________________________________________

Nudge output via text

  • FileMaker sub-routine
  • Call Bob

_____________________________________________

Nudge output via email

  • FileMaker sub-routine
  • Call Bob

_____________________________________________

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

_______________________________________________________________________________

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.