1/10/24 Marisa emailed the following evaluation of needs for Adilas:

To be honest, no, we would not be ready to move over. Adilas has quite a ways to go to be ready for the hospitality industry, especially for campgrounds/parks of our size. I would say if you wanted to look at your biggest competitor it would be RezExpert. That is the only software that we seriously thought about switching to but ultimately decided to stick with what we have due to price. Our only cost at this time using Campground Master is $100/year for any upgrades and customer service. 

Graphical User Interface for Campground owners.  

Link to xd share https://xd.adobe.com/view/5c903c5b-0451-4fca-5613-5ed795812d1e-2aa1/ 

We have had a number of meetings on this project, here are some other resources and meeting notes. Many of the different notes have screenshots to show the development of the project and where it is at and/or going. See below for more details.

Meeting on 10/10/19 - click to see meeting notes and screenshots - research and ideas

Meeting on 10/15/19 - click for notes and screenshots - concept art and mock-ups

Meeting on 10/29/19 - click for notes and screenshots - more mock-ups

Meeting on 10/31/19 - click for notes and screenshots - mock-ups of the revenue and expenses sections

Meeting on 11/7/19 - click for notes and screenshots - first full mock-up - multiple pages and topics

Meeting on 11/12/19 - click for notes and screenshots - full mock-up plus some mobile screenshots

Meeting on 11/19/19 - click for notes and screenshots - mock-ups for mobile

Meeting on 11/21/19 - click for notes and screenshots - more mock-ups for mobile

Meeting on 11/26/19 - click for notes and screenshots and a video of the meeting (virtual tour of the app to date) - full mock-ups and mobile mock-ups

Meeting on 12/3/19 - click for a couple of screenshots - moving from graphic concept into first round of coding.

Meeting on 12/5/19 - click for notes and screenshots - mock-ups from graphics to code

Meeting on 12/10/19 - click for notes and screenshots - more mock-ups from graphics to code

Meeting on 12/12/19 - click for notes and screenshots - code mock-ups - playing with different backgrounds

Meeting on 12/17/19 - click for notes and screenshots - code mock-ups

Meeting on 12/19/19 - click for notes and screenshots - code mock-ups and browser testing

Meeting on 1/23/20 - click for notes and screenshots - starting into the customer side - new website mock-up for WanderWays

Demo video 1/28/20 - click to view demo (youtube) - 3 minute video to showcase the product to date - marketing efforts

Meeting on 2/12/20 - click for notes and screenshots - new website almost done and interactions between designer and backend code writers

Meeting on 2/19/20 - click for notes and screenshots - new color pickers and settings for look and feel

Promo video provided by Marisa on 2/26/20 - youtube video - 3 minute promo

Meeting on 2/26/20 - click for notes and screenshots - working through settings and starting into project management

Meeting on 3/21/20 - click for notes and screenshots - Working on settings, color pickers, site admin, roles & permissions

There was a small break in the project and we had to set it by the side, dealing with funding, and availability. There were a few small meetings and progress, but nothing major to report.

Meeting on 7/22/20 - click for notes - Meeting to get the project back on track and moving forward.

Meeting on 9/2/20 - click for notes and screenshots and a new mock-up - Reporting on the customer frontend pages and application.

Met up with Steve over the morning meeting. We did a little bit of catch-up and talked about a number of things. Lots of moving pieces and many of them are doing well and making progress. We talked about developers, reoccurring invoicing, new graphic work and options, and touched base on white label progress. We briefly looked at banks, payments not yet deposited, receivables, payables, and some verbal budgeting. We would like to increase some of the wages to those who are helping us (dependables).

Wayne joined us and I started working with him. We were having a small server issue with one of the brand new servers (not yet released) that is being setup. It was losing itself on a redirect. We looked into it and Wayne started doing some wire shark and backend connection tests. I built a small testing page and passed it over to him via email. We got far enough that Wayne will take it from there. He is the master when it comes to the server side of things. I'm so grateful for his help.

Dustin, Steve, Josh, Eric, and I were on the morning meeting. Each of the guys checked in and then bailed out to work on their own projects. Eric had a number of questions dealing with showing some of the discount options and data. Discounts are so crazy... We have settings, tax settings, percentages, dollars off, bulk discounts, tiered pricing, customer type discounts, etc. It can get crazy. We are also seeing a need for more documentation out in the API socket land. What do these methods return and how can we get to that quickly.

The power of recipe/builds. Both Cory and Steve were talking about the potential and ways that the recipes could and do help the build process. They were even talking about unitizing some of the costs using certain recipes.

Cory and Steve wanted to see a demo on the rewards and customer loyalty points. We went through things and they made some comments and had a couple of questions. Mostly they were excited to see us get it ready for release.

Working on the project list and refining some requirements on the multi vendor, multi corp, invoice to PO - one of the time consuming pieces is bringing in bulk raw goods. On the subs being transferred in... could we keep the barcodes the same, both on the parent barcodes and the sub barcodes? The other time sucker is relabeling and printing the labels. Some of the clients are using complex labels (bring a sub package in and tie it to different units of measure). They, the client, are using the custom labels with qr_subId_quantity_price (label format) type thing. They really need mini conversion with the ability to do cross-corp barcode labeling. Mini conversions almost gets into the level of grand children and so on.

Steve would love to build out our internal project management stuff. We would like to build out project timelines and showing progress via timelines and check points. Helping our clients see the work that goes into some of these projects. Including funding, time, labor, check points, progress, etc.

Small talks about bulk check printing and using the keyword "bulk" to help the system assign check numbers on the fly. Steve had a number of be careful/got ya's - such as missing checks, printer eating or destroying a check, jumping out of the process, different check types - say 3 on a page vs single check per page (default). It gets deep on the got ya's. Calvin did some work on the bulk check printing project a couple years back.

Crazy sales tax stuff. We were talking about multi tax rates, buying and selling products and services and then being able to tax things based on where they were sold from and where the products were going to end up. Kinda crazy taxing stuff and mixing and blending special taxes. It seems like taxes are already complicated, and it seems to be heading even deeper. Special sales tax rates per zone, per city, per county, per municipality, per entity, per location. Invoicing, transferring products behind the scenes, special taxing, special reporting and the list goes on. Crazy, crazy stuff.

The deeper we go, the more we are seeing the usage of locations and stores and keeping things straight. That could be inventory levels, needs, sales, transfers, taxes, users, permissions, clients, vendors, etc. It get's pretty crazy. Locations are a huge piece of the puzzle.

We were talking about flex grid tie-ins and being able to expose certain things to the public and certain things internally based on show/hide on the web settings and the reflexive side of the flex grid (crisscrossing flex grid tie-ins and relationships). We are seeing a need for this (it already exists but may not be being used) and we may want to employ more of this type of function.

There was also a small discussion about ideas, limits, and setting up priorities. There are so many ideas... sometimes it gets tough to figure out what or where to jump first. Eventually it comes down to priorities and setting those priority levels.

Shannon was on earlier but we were still in a meeting with Cory and Steve. She was working on formatting a document that we were working on. We have another appointment scheduled for later this week.

Eric popped in and had some coding questions. We got him squared away and headed in a good direction.

11/12/19: E2 Solutions is asking for this as their client runs a payroll for 200 employees.

Many clients have asked for this over the years. Most recently Herbo has been interested, and on 8/26/19 C_ - -c (client of Steve in Denver) is also asking. Steve B. asked if perhaps they might want to chip in? Herbo could be asked the same thing perhaps? Steve B also suggested having Calvin work on this?

Years ago $2500 was paid in for this project- wanted 3 checks on one sheet (not one of our options). This would be another project. There can also be a printer printing problem- ie eats check. How to keep the numbers of the checks in order?

9/3/19- Steve has spent 30-40 hours of time. Waiting on metrc to open up the API so we can push wholesale transactions through. 

Talking with Steve about master corporation (aka meta data systems, aggregated data, data warehouse, etc.) ideas. What if we did the master corp thing and then mapped all the pieces where they need to be. We already have a ton of mappings from the normal system into reports and financials. What if we used the same model but just got aggregated sums and totals and recorded them per day per location per category. It could be pretty simple, by using the existing systems and just recording master totals under a master corporation of sorts. The break through today is - use what we have... and then all of the existing code still works without building new tables and new logic.

Working with Eric on some debugging on multi-line variables and custom JSON objects.

Talking with Steve about other budding options and opportunities. We also talked about new servers and how that process is going.

Steve and I met with three people from Herbo this afternoon. Steve had sent them a spreadsheet with some basic numbers and data (system stats). They wanted some clarification on some of the numbers and what the different data points meant. Good conversation. We even jumped on one of the servers and showed them some quick stats, queries, and data counts. We basically, told them, tell us what data points you want and/or need, and we can get them for you (within reason). I have a different page of notes. The file is called "meeting_with_herbo_9_3_19.txt" in the brandon folder.

In a nutshell, the main thing was getting at raw numbers on a global scale (full or system wide) and then also providing similar numbers on a per corporation dashboard of sorts. Their thinking was that some of the numbers, averages, counts, and totals are and/or could be great marketing tools and pieces. They were talking about special landing pages that helped service and/or answer their clients questions and help to provide the comfort and knowledge needed to help the clients feel good about the tools, product, and direction. Basically using stats to help with customer support and buy in. Steve said that he would help them get some of those numbers and values coming more to the surface. He will be working with them directly.

Some of the other questions were dealing with QuickBooks integration, importing and exporting data, digital story telling, good cause and effect, crazy tax issues, dedicated servers, and limited sites for selling limited POS (point of sale) transactions (visually paired down systems using simple carts, invoices, and merchant processing). Good meeting.

Tech support, emails, small bug fix, working with Bryan on a tech support email, recording expenses, and reading through notes from the day. Other emails to Wayne about new dedicated servers and other small tech support things.

Both Eric and Wayne checked in on the morning meeting. Eric was confirming some changes that he was working on and reported on some of his findings. Wayne sent me a bunch of information to login and test some of the new dedicated virtual machines at Newtek. We have two of them being commissioned and configured. He stayed on the meeting while I did some initial exploration and logged in via FTP (file transfer protocol) and RDP (remote desktop protocol). Those are the two main ways of connecting into the servers. Even though these are virtual machines, we are hoping to treat them like they are physical boxes spinning on metal drives. All of these new servers are virtual or VPS (virtual private servers). It should be interesting.

In working on sub special accounts (rewards, customer loyalty points, gift cards, in-store credit, etc.). Added some new validation and formatting to the show special account transaction report.

Eric joined the meeting and we touched base on a couple of questions. One of the subjects was dealing with the loyalty points and the program start date. It was already built into the add new points for an invoice method. We decided to add it to all other look-ups. That will help the users keep the loyalty points program hidden until they are really ready to use and show it. That allows for a configuration time before being directly used right out of the box.

Wayne released two new servers today. They are both virtual machines vs older physical boxes. I didn't have time to get to both boxes, but I was trying to virtually kick the tires a bit. Here was my short list:

kick the tires on the servers... to do list
1- browse to the site
2- check the ssl redirect
3- check the database updates
4- rdp into the server
    - cf settings
    - look around
    - click through a few things
    - check for .jar files being installed
5- ftp into the server
6- record login info inside of adilas, let dev team know about new servers
7- update any files within the date modified window
    - 8/22/19 - so anything later than 8/1/19 will need to be pushed back over
8- browse to the site and login... bounce to different pages and check things out
9- check api sockets and connections
10- make sure that the master list stuff is ready to go in the master code branch and on data 0

Anyways, started going through the process.

Bryan and I looked at some code for the advanced invoice sub inventory search and results. We had a complaint from a client that the report was taking a long time. We briefly looked at the code and worked on a plan of attack. Currently, the report is looping and then going out to the database multiple times per loop to fill in missing and/or unknown data. We will be reworking things to do what is called a query of a query. This changes the approach from back and from between the database and the page to back and forth between memory (a cached query in memory) and the page. It should speed things up considerably.

After that, we worked on a small change to the plain footer. That small footer is used by the system when generating a PDF document for a PO, invoice, quote, or financial report. We had to get some white label variables out into that footer through non session (memory) based means. We tested and merged in the new code. We then pushed it out to all servers.

Dustin, Steve, and I were on the morning meeting to start with this morning. Steve and I started talking about servers, models, and how to help configure the adilas model. I gave Steve an update from my working with Wayne yesterday and getting into and exploring the new virtual servers at Newtek. Lots of potential there and we could possibly take things to the next level without jumping from physical servers clear out to AWS. Basically, we are seeing a good middle ground where we gain from both side of the coin using Newtek's virtual serves, stacks, and clusters. We did some light drawing and talked about options. We may want Wayne to help us focus on the Newtek side of things vs going back into the deep, deep waters of AWS land. Good stuff.

Eric popped in and had some questions on session management and when, where, and how to use session values and variables. Mostly best practice stuff. Great questions and you can tell that he is trying to follow those best practices.

Steve and Dustin had to bail off the call around 10 am. They have a multiple hour call/meeting with a CPA in Colorado. Lots of talk about unitization, SGNA costs, cultivation, and production, and tracking everything through the system.

I spent the last hour working through some new settings on the new virtual servers from Newtek.

On a work session with Shannon. When she first came in, we started out with some global updates and letting her know about a few of the current happenings. We spent the first half an hour going over changes in servers and configuration options (virtual servers at Newtek), the adilas café (new layout and design work being done by Jonathan), and other happenings inside of adilas. I have a ton of fun sharing and helping Shannon keep up to date on what is happening. After that, we jumped in on the glossary and did some new entries in the G's and H's.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=4030 - link to the glossary that we are working on

7/20/2020: This still has glitches. Bryan just billed for $330 as of today, and handed project back to Brandon. Brandon has spent 6hrs to date and will most likely spend another 5-6hrs this week.

This project has been a work in progress and is almost complete as of 1/17/20. Still a glitch that has to do with inactive items. Bryan is working away. 

Shannon and I met up with Jonathan. Shannon was mostly just listening in from the background but she chimed in a couple of times. As part of the conversation, both Shannon and Jonathan will be getting together to go over system functionality. The deeper Jonathan gets, he is becoming more able to interpret the training and information that Shannon could provide (virtual tour guide/trainer/consultant). That's exciting.

We started out the meeting and Jonathan gave us a new demo of the progress on the mock-ups for the adilas café. See the link below for a small clickable demo. As a side note, the contents may change if the project gets re-exported for viewing. We talked about some options for saving and archiving different versions. We have some plans and will try a few of them to see what works best. Also, see attached for some screen shots.

https://xd.adobe.com/view/9759489c-676e-48f5-7bd8-d85c6a6b7699-e168/ - graphic and clickable demo (temp link)

The next topic switched to Jonathan's "clean out and organize the garage" project. He has gone all the way through the customer section and is listing page names, topics, functions, links, and what pages connect to what other sections and/or pages and sub pages. Basically, he is mapping out the system and what plays with what and how things work. Very cool. Along with that, we expressed that we want him to keep going in this exploration project and allotted a new budget amount to keep going in that direction. The end goal is to virtually figure out the "adilas family tree" and who (what) is related to who (what), inside the system. Kinda fun.

Did some photo prep on some of the new screenshots that I got from Jonathan Wells (graphic designer). Spent some time recording notes and pushing up files to document the process.

Eric popped in and we had a half an hour session. We talked about some of his projects and worked on some query of queries processes for his current API project. We talked about options of running certain tasks from memory and session vs direct trips to the database. This is kinda funny, but we were talking about looping, grouping, and summing our way through some of the data. It just sounded funny.

On a different note, the topic of a master corporation to help hold the totals and aggregated sums and totals is gaining some momentum. Interesting how we sometimes need to solve things on a simple one-by-one manner, then we do it manually for a while, then we work on automating things, than we start mixing and blending and putting pieces together to create more of a whole or full picture. That seems to be a common process and how things tend to evolve.

Back on it again with Bryan. We are struggling to come up with a fast and efficient way of getting the advanced invoice sub inventory search to go fast enough. It is working but it takes forever (minutes). We spent a bunch of time looking over things and making little tweaks here and there. Still no major speed increases. We may need to go backwards to figure out a faster way to get at the data. Maybe start clear back at the search interface and then go forward from there. This project has a number of sub requirements that make it kinda tough.

Reading over some advanced invoice sub inventory search and report code. Making a plan and working on a new solution. The old solution took to long and was taxing on the database (multiple trips back and forth between database and loop iterations). The new solution will query the database, join certain tables, and then group and filter, group and filter. The end goal is to get to smaller and smaller sub results. Those sub results will then be used to display and provide data back to the user. A series of smaller funnels will help in the grouping and filtering process. The process also includes a scratch list and a clean list. The scratch list will hold all possible pieces based on the sub filtering. We will then loop over the scratch list and populate only unique entries into the clean list. This clean list will then be used to do a query of a query to limit the final results.

Lots of planning and rewriting and restricting code. The main pages being altered are the advanced_sub_invoice_line_search and advanced_sub_invoice_line_results pages. Lots of changes on both the forms (hidden values and visible values) and lots more work on the logic on the results page to show the values.

Worked most of the day on Friday - working on this report. I stated at 7 am and worked most of the day until 8:30 pm. I had a lunch break and went to the city party with my kids for a bit, but most of the day was spent on this report and logic. See elements of time # 4919 in the shop for more details. Lots of testing, rewriting, and some praying. This was pretty deep but somewhat developed into a series of smaller funnels and grouping and filtering to get to smaller and smaller data sets. Minimal trips to the database and then back and forth between memory objects to filter the data. It's not all the way done yet, and it has only been tested locally, but I feel that it has some potential, not just for the current report, but also for a future database feature called real in-line extensions.

The crux deals with a record set and then being able to filter that record set based off of numerous (unlimited) outside filters with somewhat randomly connected data points. The random data points, in this instance called sub inventory attributes, are user controlled fields. These custom fields point to custom tables that are not part of the main database tables. They basically hold the custom data and allow for the full structure to be reconstructed on the fly. We have future plans to use similar custom tables to hold data type specific values for all other areas of the database.

We have a thing called flex grid tie-ins and they now have 30 custom fields. Those fields may be named and used as needed. The main problem deals with a thing called a data type. The different data types are (generally speaking): text values, dates, times, numeric values, decimals, and on/off switches called toggles. We also have custom bulk object for storing JSON objects. Anyways, the data types allow for special things. The older flex grid tie-ins (all 30 of the custom fields) are strings and may hold all kinds of data. However, when being looked up and/or filtered, they are all treated as strings (simple text values). That makes it hard to do things like find something between this and that value, add things up, figure out max and mins, average, etc. A data type is required for that types of action. Anyways, lots of work was spent today on trying to work around those pieces and params. Good stuff.

The only other notes for this entry are some hints: joins, filters, and groups or grouping - doing these things over and over again, helped us get back to the requested and filtered data. Repeat the process as many times as needed. Keep narrowing the players.

Monday morning. Lots of action today. Steve and I were the only ones on the meeting to begin. By the time we were done, we had touched base with Dustin, Alan, Eric, and Josh. By around 11 am, most of the guys had moved on and were working on their own projects.

Steve and I were talking about a number of topics. The first one was dealing with a corp-wide setting that was setup way back but never had been fully operational. It was called show_tax_breakdown. After looking for a bit, we determined that it was setup in September of 2012. It has never been used. We did find however that a smaller version of it exists in a corp-wide setting called default_printable_invoice (option # 9 for that setting) on the mini invoice and showing a tax summary as part of the mini invoice (customer receipt). This question and subsequent look-up came from a client email that wanted to turn on the old show tax breakdown setting. It is funny how things keep circling around. Often, we do what we can, and then we know that we will have to circle back around again. We keep building out nubbins where we hope to tie things in later.

While we were looking up some history on the older corp-wide settings, we also talked quite a bit about master corporations, aggregated data, aggregated systems, and being able to move away from transactional data. We still need the transactional data, we just need a way to get to secure summed up and tallied data points. We talked quite a bit about posting, locking, and levels of being able to edit things. The analogy of water freezing into ice was brought up. Some users want us to go directly to ice and make things un-editable. Others require the options to be able to modify and edit data and values. We talked a bit about our data assembly line concept and having different permissions that allow certain levels of access in the flex bubble type model. Very interesting.

We also talked about VPS's (virtual private servers) and some times needing to go back into older environments or models with new features and/or needs. We talked about flagging data, maintaining known and trusted values, scheduled tasks, harnessing user clicks and actions, and even back filling data as needed. There were conversations about single logins, flipping between corporation, showing and maintaining aggregated totals, and validating the integrity of certain data points, sums, totals, counts, and grand totals. We are seeing bigger and bigger needs on first, sales data, and then on inventory tracking. Those seem to be the hot topics for now. Sales data tends to motivate all kinds of other sub functions such as cash flow, inventory levels, tax collection, repayment, etc. The list goes on.

Eric popped in and has a number of question about discount campaigns and how to set them up and track them. We went over ways in corp-wide settings, individual entries, and talked about the discount engine that Josh worked on. There were some talks about deciphering some data and exposing certain fields and values to outside 3rd parties through API socket connections. The users would have to agree to the 3rd party terms and turn thing on, but once completed, all discount information, campaigns, and calculated values and totals would be passed to specific 3rd parties for analysis (only if turned on).

More talks about circling back around and back filling and/or completing certain data values. There are tons of transactions, and certain records hold certain values. We may also need to expose how certain values are calculated, if it is not logical from the data itself. This gets clear into formulas, calculations, order of operations, etc. Discounts play along those lines. You can skip discounts, do standalone or dis-jointed discounts, in-line discounts, percentage discounts, dollars off discounts, mixed discounts, automated discounts, stacked discounts, etc. It gets pretty deep.

While we were talking to Eric about discounts, Josh joined in. We talked with Josh about getting with Cory and working on some concise videos and educational material for showing how to use the automated discount engine. We talked posting videos to help files, updates, and the news and updates page. We are seeing more and more of need to get the correct information out to our users. Basically, a number of things and features exist. However, due to how many there are... some times certain features are not used just because people/users don't know how and/or can't find any training on the subject. Some times they don't even know that certain tools and features exist.

Still talking with Josh, the topic started shifting towards more concise pieces. We have tons of things that are big and somewhat bulky. Those are harder to consume and digest. We need to get into smaller and smaller pieces. Along those lines, Steve chimed in and mentioned almost a marketing type approach. We need to be consistent and have some consistency between the info we are trying to share and how that is presented. We need to help people/users learn, but we also need to be putting our best foot forward. That takes things to a different level and almost adds a marketing level of showing off our stuff. There are pros and cons to that. A pro is it all looks super nice and makes sense. A con is that it requires still, time, resources, and a plan (one or more persons doing the same thing).

As we got deeper into some of the subjects, I kept thinking back to the word "teams" and what teams are we a part of? Certain people or certain teams need to handle certain parts. This really isn't a free for all, it is too complex and requires certain timing, skills, and resources.

After Eric and Josh were done, Steve and I worked with Alan. He helped me on some database query questions and then Steve worked with Alan on a project that both of them are working on for state compliance issues. A couple of other topics for the day were: directing towards teams and who does what. Using news and updates more for training and tech support, GPS tracking and delivery options, and using the right tools for the right job (talking about database and SQL query optimizers - built-in helpers for certain tasks with complex logic and tons of records).

Lots of moving pieces, all over the board. Towards the end of the meeting, I worked on some emails and then recorded a bunch of notes. Things are going so fast... the only way I feel that we can keep up is to record what is happening. We can't solve everything, but hopefully, we circle back around and get a sense and/or flavor of what transpires. Busy times.

Steve has already put quite a bit of time into this code (get details from Steve). This will aid distribution clients in tracking liabilities, ....

Working on pagination and filling in sub attribute values for the sub inventory search results.

Working with Bryan on how to connect to Square as a merchant gateway. This is a new merchant type. We talked about ways to get it coded into adilas as well as getting test accounts and doing some scratch files to play with the new integration and API socket options. Good meeting. We also merged in a little bit of code for Full Circle.

More work on the sub inventory searches and data exports. This has been a very deep report. See attached for some of my notes.

Steve and I talking about projects and priorities. More and more pressure to get organized and get all hands on deck working in the same direction. Right now, we don't have a shortage of able body hands, we are just all over the place. We have guys on this project and that project, we have others on custom work, we have other on core projects, we have others that we don't know where they are at. We really want to keep focusing on the list, and adilas tick list. Along those lines, we setup another meeting with Cory for Thursday to keep going over the list and making adjustments as needed.

From Steve - "Not a lack of work... there may be a lack of organization."

Steve was also quoting my dad, "use technology to help you as you go along."

Anyways, we were talking about how hard it is to control certain timelines and the pull of other projects (almost distractions of sorts). Eric popped in and had a few questions. We setup some time later this week to work on special accounts (rewards, customer loyalty points, gift cards, etc.). Some times budgeting time to work on certain projects, with mixed participation, really helps. Some times if I plan time for me to work on a project by myself, it seems like a softer schedule than if someone else is committed to the same time. A buddy, on some of these projects, really helps.

Working with Josh on his discount engine bug and merging code. We ran into a small problem and had to back out some code. We will re-hit it later today.

Making progress on sub inventory. We ended up altering the scratch list to clean list process. We added in a way to check and stack sub filters and only allow things that have values in all sub filters to be passed on as part of the clean list. This took most of the session today.

Met up with Josh to go over some new discount code. The new code has a feature in it called max uses and deals with the number of times a certain discount may be used. We also did some debugging on his code for add to cart. We looked up some variables and moved some declarations up higher in the code. That seemed to fix the bug that was being shown. The code was merged in and uploaded to all servers.

We merged in a branch of code that Dustin had been working on for a couple of months. Some of the code was already deployed and being tested on certain servers. We had to circle around and get about 4 pages from Steve's branch to make the merge happen. Dustin and Steve have been doing some back and forth ping pong to tag team on certain pages and pieces. About 18 new or modified files were pushed up to all servers.

Paying bills, emails, recording notes, and phone calls.

Working more on the pagination and output for the advanced invoice sub line results report.

6/9/2020: Notes from meeting with Kelly regarding upgrades/fixes to discount engine:

1)Currently for each line item you add through the discount engine, it creates a description in the non printing notes. This can get messy for searches. Possibly make this a permission- do you want this to print? Or, only print once.
2)Most people want to price items more than they want to give discounts. 
3)Needs to work in e-commerce.

Josh will be finishing up phase one of discount engine this week (9/11/19). 

Buy X get Y (a more flexible BOGO). This has been asked for quite a bit by clients. Josh estimates this is a larger scope, as additional fields would need to be added to the database. Estimated time would be 2-4 weeks.

Buy X Get Y
   -  Categories for X
   -  Categories for Y
   -  Parts
   -  Vendors
   -  Time Periods
   -  How many max uses
   -  Make any purchase on Friday, get a free joint

Buy 2 Get 1
Buy 5 Get 2

This is a big project that Steve wants Josh to jump back into in the next week or so. Josh has already done quite a bit of work on this. This will give clients ability to assign drivers to deliveries, see where the drivers are on googlemaps, use EOT for GPS coordinates. You will be able to hover over delivery car and see drivers name. Click on it to get info about driver and delivery. 

Attached are two screenshots- a mockup of a delivery dashboard (chooser) and a map view. 

Spent some time working on code sign-off and review for the special accounts project. This deals with rewards, loyalty points, gift cards, in-store credit, etc. Working on the methods inside the submit cart page. Lots of nested logic and methods calling other methods. Things like look up account types, see if they should/shouldn't use loyalty points, how many are earned per invoice, how many are redeemed (spent) per invoice, balances, rules (point values), etc.

Online GoToMeeting with Molly, Spencer, Bryan, and I. We started out with all of us on the call/meeting. The topic was last modified dates for parent items and sub inventory items. We took some notes and talked about options. See attached for some notes.

After that, Spencer dropped off and just Molly, Bryan, and I were left. We spent some time talking about the re-work on the advanced invoice sub line search and sub inventory results. This is the project that I have been working on for sub inventory and redoing the logic to include funnels, groups, sub filters, scratch lists, and clean lists. Pretty deep. I gave them a run down and said that I'm over 3/4 of the way done. Working on output and export options now. Most of the logic is done.

Once we fined that conversation up, Molly dropped off and just Bryan and I went over some things. We talked about merchant processing with Square and Herbo and other options. I mentioned that if Square is too crazy, we may want to look into Stripe as a new merchant account type. We also went over the last modified dates for parts and subs and added some to do list stuff to get Bryan a small overview to start with.

The last part of the evening was spent recording notes, emails, and light clean-up from the day. Busy times.

Spent hours and hours working on the display output for the advanced invoice sub inventory search results. Some of the time was formatting and some of the time was testing with some live data. The corporation that I was testing the pages on was huge. Here are some rough stats:

46,026 records for a 30 day period.
The spreadsheet amounted to 108 MB (that is huge for spread sheet)
It took 11:37 minutes for the system to build the spreadsheet
Excel couldn't even over the 108 MB file. I waited almost 20 minutes and it still couldn't open it.
They have 74 sub attribute filters. When grouped by attribute name, it comes to 40 sub attributes (grouped)
A different stat - for 35,074 records (slightly different search), that was 2,365 unique packages

Anyways, here is what I found. The web view, with pagination, ran pretty fast. The export to Excel was as slow and big as cold honey. We need to provide more general stats, totals, groupings, and different report types. We need to show the stats - such as total quantity, total package count, total item count, totals on cost, quantity, and price. Lots of quick info vs 46,000 records. Nobody wants to look through that much data. I think that they are more interested in groups, totals, and other stats.

When I came in this morning, Steve and Eric were talking about numerous custom reports and spreadsheet exports for certain companies. The bigger they are, the more complex some of their needs are and/or become. Tons of custom data, and even cross corp and multi corp consolidated data. They were talking about ways to make the list of corps and locations more data driven vs just code driven (we have to update the code to include the new corps and new locations - manually and then upload code again). As they were talking, I was just listening and hearing that some needs exist out there... some of those needs are: help with data entry (standardizing data entry), data clean-up (maintenance), education (specific training), better communication on needs (we are somewhat guessing what they need), data driven logic (recording lists in a database vs hardcoded on the different reports). There were also lots of new discussions about creating lists of who is connected with other corps and how to create a one-to-many list that could be data driven vs hardcoded. We talked database lists, tie-ins, page includes (just lists and variables) that get pulled into multiple reports, etc. Interesting discussion.

Lots of topics going out to grouping, filtering, exports, using data tables (being able to sub sort by column and do exports directly from reports).

Going over projects, priorities, and budgets for projects. Cory and Steve were on the meeting. We went over a few of the new projects and put some numbers to them. We also talked about and got updates on some of the ones that are in progress. We all wish we had more time, but all things considered, we are making good progress.

There were also some talks about news and updates, education, help, refining, circling back around and doing new phases and rounds on older projects, vision of the future, and working in teams. Good stuff. We talked about removing the name Adilas from some of our documentation and training materials. That is in preparation for white label companies using the same assets without having to revamp everything. We already have some projects that deal with changing out graphics and help files. We may also need some other projects that help clean-up educational assets.

More and more needs to work on user interfaces and helping our clients be able to filter and find the needles in the haystack. We have tons of great data, but sometimes it takes a little while and/or master users to get it out of the system. We need to simplify that process. All in all making good progress. As a side note, sometimes it really helps to get things released early (even potentially pre-mature) and then let people start beating on them and helping us refine the concepts and processes. I often get stuck on the mentality of get it done and do it right and then release it... that works well if I have enough time. If not, it never gets done and thus not ever getting pounded on and/or played with. We have to walk a fine line there, as there are certain things that never should be prematurely released, and other things that should be and/or no harm in getting it out there. Quite the balancing act at times.

On with Cory earlier today. She made a small comment about removing the word "Adilas" in the glossary of terms. She recommended that we use other more generic terms. We came up with terms such as system, platform, application, app, database, software, or any combo of these terms.

https://data0.adilas.biz/players_object_lesson.pdf - pulled up some older documentation for some terms. This deals with how the system is stacked and organized.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=4030 - system software glossary - worked on letters L, M, and N's today.

These pages could use a new do! 

Spring 2020: Jonathan Wells did a work up. See attached video. Waiting for funding of half. Tracking this in project #1627. leans heavily on requests of molly's client.

This page is ugly!! Drea has been asking Steve to fix this page for awhile. 

Dustin has started working on a hub- includes testing, licensing, other operational details. Calling it an oversight hub.

Working with Steve on a project that he is working on with the adilas community funded projects. Also helped Calvin on a Zoom session get some new local data setup for working with sub inventory and sub attributes for his label builder app.

Back working on the special accounts project. It was getting pretty deep and I was having a hard time focusing. I ended up bailing out. I'll circle back around.

Bryan and I met up and touched base on his progress on the Square merchant processing stuff. He is building out test transactions and playing the Square API sockets via a testing account. Great progress and we just went over a few small details and questions. I also gave him a small review of what I was learning on the advanced invoice sub inventory search and some new direction there as well. Good stuff.

Emails, tech support, and recording notes and such.

Great meeting with Jonathan. Dustin was on the entire time. We also had Steve for the first half an hour. Here a few notes from the meeting.

- Jonathan is working on mapping things out and getting them organized by colors and by main players.

- Our users can't consume the massive amount of options and functionality.

- The system is somewhat of a labyrinth or giant puzzle. You could literally click and click and virtually connect everything together. That is both good and bad, in some ways.

- Jonathan really wants to help us simplify things.

- Currently, he is somewhat taking inventory - listing out links, sub homepages, navigation, processes, etc.

- Meaning of a location or who owns what - originally, he was thinking about each link and/or navigation as being owed by one player group or another. As he got deeper and deeper, he started to think of some of these pages and sections like locations and multiple ways to get and/or point to that location. Instead of it being owned by a certain party (invoices, depostis, PO's, customers, etc.) it was more of a shared asset and multiple parties used the same resources, just maybe in different ways.

- He is making a spreadsheet or flat storage of page names - resource list - what is available?

- Currently, inside the system, if you click on a certain link, you get all of the rest of the sub luggage that goes along with those sections. He would really like to help limit the amount of extra stuff (even if it belongs) and keeping the navigation on a more digestible level.

- There were a number of comments about the availability to bounce and jump from place to place. That is cool if you know what you are doing. If not, you could get lost really quickly. As a fun side note, I was telling Jonathan that we grew up like this (able to bounce), using navigation that is non linear, non conventional, and allows for jumping from place to place.

- Steve brought up permissions and how that actually affects the navigation both display and show/hiding of different links. Jonathan didn't know that certain greyed out links were tied to permissions and/or that certain navigation options either show/hide themselves based off of permissions.

- Steve was also really excited to keep Jonathan on the project of mapping and/or listing out all of the options that are available. You could almost see Steve sales side coming through as he was talking to Jonathan about the possibilities, if we had everything all mapped out, organized, and listed in an approachable format. Tons of potential there.

- We talked about training wheels, guide rails, and other ways to help new users out inside of the system.

- A quote directly from Jonathan - "Streamlining to me, is removing the complexity."

- We talked about prototypes, direct market tests, and doing other things to figure out more information about what is needed, wanted, and most used features. This also includes where people got lost, what they don't use, and what they don't know. Both side of the fence.

- There were some talks about the currency of data and valuable that is. We talked about the benefit of gaining and organizing that data into smaller chunks, analytics, stats, etc.

- The deeper we get, the more you have to adopt a "system thinking" mentality. It becomes possible, because you are in a system vs standalone mini pieces of the puzzle.

- Jonathan was encouraged to keep looking for reoccurring patterns and helping to expose those pieces. We also talked about if we could show how things fit together, and how those reoccurring patterns play in, it would help with education and getting users oriented faster.

Towards the end of the session, I was showing Jonathan a couple of models dealing with how we organize the system. I showed him the simple plates and cups model and how we tend to track all of the main pieces in a similar format. We had some good training and went into a live system and looked up expense/receipts, invoices, deposits, PO's, etc. We did some training on natural connections, flex grid tie-ins, and how each player group has similar ways of tracking and recording those pieces that make it up. Just for fun, we pulled up a small mini graphic of the plates and cups model, and then drew lines from what we had and/or saw to what that would look like in the plates and cup model. It is hard to write about it, but it works better as a show me exercise where we flip screens, check stats, and then show how that looks in the model. We also briefly talked about how a dresser with drawers type model could do the same thing.

See attached for some screen shots and other pieces.

On the phone and then a Zoom session with Calvin going over needs, direction, and mappings for sub inventory. He got a bunch of new tests data and we were hooking it up and going over things.

When I got on the morning meeting. Steve and Dustin were talking about their projects and times that they could meet up and work together. They have become a great little team. That makes me really happy. Below are some notes between Steve and I. We were talking about some upcoming meetings with both Russell Moore and Jonathan Wells. Both are designers and graphics guys.

- Graphical homepages (graphical mini dashboard per main 12 player groups), custom dashboard with little widgets that could be moved around and configured per user, mix and match pallet (mini windows - movable and dockable)

- We would like to look into what it would take to build on a JavaScript framework. There are multiple frameworks out there, what does that mean, what does that look like, and how are the pieces managed between the different systems? Lots of questions.

- Projects for Russell - He could work his magic on the corp-wide settings page, 3rd party solutions page, help out Alan with the invoice due date project, and help us get more data tables in place and integrated into the system.

- Getting help from Russell on some of the snow owl theme settings for some of the older AFB headers and such. There are a number of knowns spots. One is the adilas community funded project, the snow owl theme settings, the ecommerce settings, the custom email settings.

- Looking at resources and what do we want to spend on what and how quickly could those expenditures turn around and produce some results.

- We talked about consolidating our ideas and projects, using the adilas community funded projects page, report, and section. We could used it for project management, reports, progress, and a centralized location or hub for developers, clients, reps/consultants, and others. One spot will all of the updates and progress.

- There will always be ongoing development, product refinement, and what is coming (future). The system keeps morphing out in front of us. Sometimes that is hard to predict.

- Help prepare our users for impact - this is a huge system with tons of branching options and paths.

- Keep working with Jonathan on putting together a list of what adilas can do - whitepaper/graphic/map - Getting it all organized - a virtual road map - big dumb animal pictures - this would help so much with sales.

- Helping Jonathan get more system training from myself, Shannon, and Steve. The more training that he gets, the more he will be able to start pulling all of the pieces together. We would like to keep him on the education and sales side of the equation.

- Permissions homepage and how we simplify that - currently, it is kind of a monster or as my dad says - a football field of permissions.

- Mapping out the system functions and what is available. Steve wants a map the adilas world - what do we have and how is it organized - scroll as needed - zoom in/out - etc. Use this as a training and sales tool.

- As we were talking about mapping, we jumped into some of the existing adilas maps and navigation interfaces. We talked about the adilas interactive map (vintage around 2010 ish), the GPS core interface (vintage around 2013 ish), and helping to bring that dream to life. On the newest version of the GPS core graphic, we have included some sub navigation dealing with permissions, settings, training, etc. For the record, currently, that graphic is just a small mock-up of what it could be. The real intent was to use that core interface to interact with different app modes. They could be things like data/work mode (what do you have), permissions mode (who gets to play), settings mode (how does it work or function), training mode (what can I do), usage/stats mode (show me what I've got). Anyways, some cool ideas already exist. Maybe help Jonathan keep going in that direction.

- Use the map and be able to show what new trails are coming. Steve would also love to tie the upcoming pieces out to the adilas community funded projects to help with eduction, funding resources, progress, and a centralized hub for all of our projects.

After our meeting, I spent some going over emails, recording notes, and getting caught up. Today is Monday, back at it again. Part of my process this morning was recording some notes from a couple of meetings we had on Friday. Lots of moving pieces. I'm so grateful for pen and paper and being able to scribble things down quickly and then fill things in later with all of the details. If it weren't for paper and pen, I wouldn't be able to remember enough to fill in the gaps. Great little tools.

9/16/19: Need to research on our side what coding has been completed already? We may have some code completed already for a Verifone.
We will need a model number as well for Cory to add.

Working with Next Paradigm to bring an enterprise solution to the SMB market using Verifone terminals with First Data merchant accounts. Not for cannabis or cbd markets.

Alan has been working on this.

Meeting between Russell Moore, Steve, and Brandon.

- From Steve - "Russell, we have missed you".

- Russell - Drawn back to the dream

- Like a beehive, everybody gets to play and the combined effort makes a difference

- All core adilas projects are going through our new gateway. Cory Warden is the gatekeeper for those projects.

- We have some snow owl CSS questions for Russell. We need the master back in the mix.

- Timeline views and other modern look and feel (flavor of the sites). These are things that we want to get back to.

- We want to focus on the Snow Owl Theme and get it all stabilized.

- Russell and Steve have had multiple conversations on the widget, app, pallet type interface - mix and blend different widgets and mini apps to help the users get their "space" setup. This is somewhat of a custom mini dashboard concept with lots of options and configurability.

Russell - wanted to pitch some ideas and things towards the adilas fracture project (future adilas project and plan). Making it a true core with an expandable platform type interface.

We started out in Postman (PHP based - API socket tool) and using Russell's auto generated API documentation - Tools with custom extensions for functionality, API sockets, classes, and view models. Core pieces all get add, edit, and view options for the data. Frameworks and then building on top of those. Russell was talking about core, custom core, themes, custom code, etc. These are ways that he could build on and virtually extend the core tool without hurting the main core logic.

Some of the concepts were dealing with the pallet type view (multi mini windows or widgets). They were talking about how to use tons of mini widgets, apps, views, and even third party tools - all mixed together in one app. We started talking beyond screen, and screen size, and going more to a canvas type view. A canvas is a layout design that may be bigger than a screen. They would like to be able to navigate to different sections, zoom in/out, call something into focus, and the background pieces would connect with both internal and external API sockets. Once the data structure is known, the building out of things becomes very quick. The goal is to create a robust back end engine that could be built out and modified on the frontend very quickly. Getting back to cores (internal core) and plug-ins or add-on's.

Both frontend and backend developer widgets and backend components - Russell was proposing a table component (just like the data tables, but more robust and configurable). Components are able to worry about their size vs screen size. Basically, you could make the components smart (know its own parameters). As you start mixing different components, make each one smart enough to mix and interface with other widgets without being overwritten and/or altered. Tons of self-contained mini apps all working together.

I was asking Russell about some of things that he is working on. One of them was what he was calling "Headless CMS (content management systems)" - All API socket connections but no real structure. Virtually a brain without a face. The face becomes the view model. We talked about how adilas uses a similar concept called "play at the wall" type concepts - All API socket connections without having a required view of that data. Russell was getting back to classes and specific tools and object oriented programming. If we use a tool too much (say elements of time), it can make the water muddy. That is both good and bad. In some ways, it makes it very flexible. In other ways, it may actually get abused because it may be used in so many different ways.

Lots of separation between database, views, logic, uses, tools, and data. Some of the new pieces (on the view model) could be scrolled, slid, collapsed, expanded, shrinks, etc. Kinda like the old Adobe Flash Rich Interface Environments but without the Flash wrapper. Beautiful interfaces with just in time data, fun navigation, built-in validation, etc.

At some point, we would love to allow our uses to use what pieces and features that they want and then working on charging based on what they are really using. Maybe thinking of being out on the AWS stuff for this. Still just ideas and concepts.

We also talked about running with two ships vs just one (different applications) - see screenshots (build on both apps and eventually have two separate products). Ideally, the new ship (say adilas fracture) would end up being a more powerful tool and a full remake of the original adilas model. Little by little, chipping away at the new system and new structure.

Quick Zoom session with Calvin. We went over some queries for sub inventory and had a small discussion about how to do it and best practices. Small little meeting.

Recording notes, following up on things, and light clean-up. Recording expenses and doing emails.

Steve - "All roads are leading toward aggregated data totals."

There were a number of different developers on the morning meeting. Steve and Dustin were talking and touching base. Alan joined and worked with Steve for a bit. He also reported on some of his current projects. After that Eric joined and had some questions about corp specific invoice tables. Lots of moving pieces and making progress.

We merged in a branch of code for Steve. He has been putting tons and tons of files up. He does all of the custom gram controller files (black box stuff), logos (done by someone else but pushed to master by Steve), watermarks, and his normal code pieces and pages. He added close to 50 files this round. Other small tweaks and such.

Shannon came on at 11 am, but I was still working on the code merge for Steve. We got started about 11:30 am. The whole session ended up being somewhat of a training exercise about mapping out the system and what progress we have made over the years. My goal was to help Shannon as she was going to be meeting with Jonathan and doing some training for him. After Steve and I's meeting the other day, we would like Jonathan to keep going along the lines that he is working and work on mapping out the pieces.

Going back a long ways, we started out in 2010 (October 2010 ish) doing a mapping project that lead to some major discoveries. We came up with the interactive map and tons of other good needs and ideas for the future. That was literally a springboard into some of our current projects and direction. Here is a link to the interactive map graphic.

https://data0.adilas.biz/top_secret/images/help/big_map_layout.gif - interactive map graphic (2010)

Next we got into what we ended up calling the core layout or GPS core. This is a spiral navigation wheel or a core shot of a world. This graphic started to bring in concepts of world building and almost a space type theme. Here are a couple of links for these graphics.

https://data0.adilas.biz/top_secret/images/help/adilas_gps_layout_big.jpg - GPS core layout map (2013/2014)
https://data0.adilas.biz/top_secret/images/help/adilas_gps_layout_plain.jpg - core only
https://data0.adilas.biz/top_secret/images/help/adilas_gps_layout_world_building.jpg - world building levels only

The next level was dealing with the core interface, deeper world building concepts, with different modes or levels (data mode, work mode, usage/stats, settings, permissions, learning, concepts/theory levels). This one only got to the graphic stage, we really wanted to build it out into an interactive navigation model, but only prototype graphics were created. Here is a link for some of these graphics:

https://data0.adilas.biz/top_secret/images/adilas_gps_core_layout.jpg - GPS core layout with different modes (2015)
https://data0.adilas.biz/top_secret/images/adilas_gps_core_layout_white_label.jpg - GPS core layout - white label (2019)

The other thing that we have always wanted to do was use and show some graphical homepages. Basically, have some kind of primary navigation that is really easy to use. As the users leave the primary dashboard and/or navigation, have them land on a graphical homepage of sorts. Each of these sub homepages would be a landing spot for the subject and/or topic at hand. For example: invoice homepage, deposit homepage, expense/receipt homepage, inventory homepage, customer homepage, etc. There are even smaller and more specific homepages that are sub to some of these bigger homepages. They could use some fun graphical interfaces as well. We still want to do this, we just haven't had the time. Here is a link on some of the research and ideas on the graphical homepages.

https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=graphical%20home - research on graphical homepages out in the developer's notebook

The next level is trying to get the whole system or platform into a deeper 3D world building level and using the concepts of the data assembly lines. That would be really cool. Here are a couple of other links that play along those lines:

https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=3d%20world%20building - research on 3D world building
https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=data%20assembly%20line - research on the concept of a data assembly line

Here are some other fun graphics - just concepts:

https://data0.adilas.biz/top_secret/images/help/tools_magic_square.jpg - magic square - invoices, PO's, deposits, and expenses
https://data0.adilas.biz/top_secret/images/help/adilas_3d_world_building.gif - concepts of 3D world building
https://data0.adilas.biz/top_secret/images/help/adilas_dream_it_up.jpg - 4 step - dream it up process
https://data0.adilas.biz/top_secret/images/help/adilas_dream_it_up_white_label.gif - 4 step - dream it up process - white label
https://data0.adilas.biz/top_secret/images/help/location_model_landscape.gif - What you get with adilas - map overview
https://data0.adilas.biz/top_secret/images/help/adilas_map_layout_all_business_functions.jpg - business functions overview using the map layout
https://data0.adilas.biz/top_secret/images/help/adilas_gps_layout_all_business_functions.jpg - business functions overview using the core layouthttps://data0.adilas.biz/top_secret/images/help/adilas_core_map_combos_all_business_functions.jpg
- business functions overview using both corp and map layouts

All Business functions: - all business functions - shown in the core - show on the map - show using both core and map

1. Sales, Inventory Tracking, & POS (Point of Sale) - core - map - combo



2. CRM (Customer Relationship Management) - core - map - combo



3. CMS (Content Management System) - core - photo galleries - map - combo



4. Online Expense Tracking - core - map - combo



5. Payroll & Timecards - core - map - combo



6. Calendar & Scheduling - core - map - combo



7. Create Data Relationships Between System Players - core - map - combo



8. Backend Office & Accounting Functions - core - map - combo



9. Histories & Reports - core - map - combo



10. BI (Business Intelligence) - core - map - combo



11. Web Presence & eCommerce - core - map - combo



12. Virtual Data Portal (Big Data) - core - map - combo

Inside the CFC's (ColdFusion components) we use a variable scope called arguments or local scope variables. There are a number of places that try to interact with the session scope and the application scope. It would be in our best interest, especially for taking the CFC's and their methods out the API socket land, to get rid of the session and application references. They would be more stable if they used the application or local scope variables vs those other memory scoped variables. This was added while doing some testing... We couldn't use the methods as standalone pieces, it kept saying that those session and application scope variables were undefined.

They work if being used internally from a page within the protected directories (folders), but they fail when used by themselves or used outside of the secured environment. That may sound good, but it makes it so that they wont work via the adilas API sockets route. This needs to be addresses and fixed before it gets too far out there.

We either need to fix it on the CFC's or we need to pass in the correct values from the different pages so that it hits the arguments scope. There may be other fixes, but this project has a number of files that will need to be updated, fixed, and tested.

Note added on 9/18/19 by Brandon - see the top_secret/cfc/special_accounts.cfc page and look for the function called "localGetPathToCFCs". That may be possible option to help with this problem.

Steve and Cory were speaking of this in the context of SG&A's. Say a company is unitizing and they want to add their rent to their "inventory" every month and then pay it. Rent is $6500 every month so we could make it a reoccurring PO, so it would be ready to add to a recipe.

Client requested sales tax breakdown for pdf- currently it exists only on mini invoice. Instead of just adding it to the pdf,  Josh can activate the other settings that can be accessed in the corp-wide settings.

Josh and Brandon completed the planning stage meeting.

Did a special accounts demo for Hamilton from Full Circle (customer loyalty points). Worked on code for the project and tried to fix the issue of session and application scope variables being inside of the CFC's (ColdFusion components). Also did a code merge for Eric and a 3rd party solution API socket that he has been working on.

Worked with Bryan on his project to integrate with Square merchant processing. We were working on the API socket calls and processing our own unique id numbers and random numbers. We went over some sample code and made some plans.

Merged in some code for Eric. Uploaded and launched some videos from Jonathan dealing with mock-ups for the adilas café and system mapping project - clean-out the garage. Emails and other clean-up.

Just Dustin and I on the morning meeting to start with. I spent most of the session recording notes and doing research on system mapping and direction for the future.

Part way through, Wayne joined the meeting and gave me a small report. Here are a few notes from that discussion.

Wayne - looking into generating an auto renewal of SSL certificates. Data 6 has this tech installed - small test run.

We talked about the old dedicated servers, new VPS servers (virtual servers), and AWS (full virtual stacks).

Wayne was stating that he was kinda frustrated with the service level at Newtek on this last go around. We were in a waiting pattern for over a week without anything or any communication. This was our first round of VPS serves with Newtek. It ended up being days and days that we normally don't have to deal with. Wayne is wondering if something is changing and/or slipping there at Newtek. Lots of frustrations and delays.

We want to make sure that we have multiple options, going forward. We currently have a lot of servers out there and we are kinda feeling like we have all of our eggs in one basket. We would like to expand that presence.

There were some other talks about config files and how some of the config files are seaming to revert back to defaults vs staying at a higher tweaked out level. This is mostly dealing with the database config files. Wayne is setting up a file level monitor to help track that down.

After Wayne left, I kept working on my projects. Towards the end of the session, I got a call from Calvin. We switched over to a Zoom session and he showed me what he was working on with his adilas label builder and pulling in sub inventory and sub inventory attributes. It gets pretty deep. I liked what I saw and gave Calvin some feedback. He is quite busy right now and we talked about some options and priorities.

Spent the entire afternoon working on the sub special accounts project (sub of the balance sheet). This will be used for customer rewards, loyalty points, gift cards, in-store credit, etc. Lots of good break throughs today. We added a fix for using application scope variables in the cfc's (ColdFusion components - backend logic pieces), tested the submit cart page, and we added in the account rule that dealt with show/hide the loyalty points on the invoice (customer receipt). We also showed totals on the customer log file with a valid drill-down to see the details. We are making progress. I also added some new notes to the main scratch file for the project. See attached. Good session.

See some of the attached media/content pieces for an overview and preview of a new feature called special accounts. This is for things like rewards, customer loyalty points, gift cards, in-store credit, punch cards, etc.

Thanks for choosing adilas.biz!

Steve had some questions on using existing tables for custom or special needs within the system. We ended up talking about possible black box database tables - format "bb_53_some_table_name" - where "bb_" deals with a prefix, basically saying black box or custom database table, then the corp id, and then the custom table name.

Steve is leaning towards the verbiage of "enterprise systems" vs "master corporations". This deals with using a new system (world or corporation) and housing aggregated totals in that world or system (consolidated data for multiple corps). Anyways, Steve is starting to use the terms enterprise system to meant that holding container.

Getting into aggregated totals and auto processes. We talked for quite a while about either building just in time tools that populate the aggregated totals and/or building something on the serves that runs some kind of automated process, say like a scheduled task that either runs once a day or multiple times a day, depending.

Alan jumped on and we talked about observers and subscribers - another way of saying watchers and feeders and triggers. Basically, he is wanting to get objects, per server, being stored per server (almost a mini cache of sorts), and then keying off of changes (events or triggers). Minimal effort on updates. Set the updates and then do a push type approach if anything changes. Often we just use the pull type technology (go get the data every time). Using a push type method we may change the flow and then the things are only updated when a real change or updates occurs. Other than that, it continues using the stored data, until changed by the push.

We then chatted about the invoice due date project and showing warnings for late or outstanding invoices. We talked about showing things on a top or admin type level, showing color coded warnings, no totals, with links back to data 0 and online bill pay options. Help them be aware and then just get it paid, don't rub the values or dollar amounts in their face.

Cory jumped on the meeting and had some questions about the video for the preview for the special accounts and customer loyalty points. We went over a few of the questions and made a couple more notes for us to look at. We then started talking about some other topics and projects. One of the topics was how tight to tighten things down and/or give the user the power to control things at the source. It got into all kinds of scenarios and cases (what about this, what about that, etc.). It also goes clear out to settings, permissions, and checkpoints. You kinda need to have the flexibility at some point and then be able to tighten things down and/or have it pass through a valid checkpoint. It keeps coming back to the concepts of the data assembly line flow and process. Basically, little linked flex bubbles with checkpoints, permissions, sub pieces or layering (depth), and then track it all over time based on the flex bubbles and virtual phases.

Steve and Cory were talking about running mini manufacturing over time and even getting into different phases and WIP (work in progress) type interface. It all comes back to time and tracking what happens over time. That gets into subs - sub phases, sub locations, sub grouping, etc. They were talking about pros and cons of using recipes and doing all kinds of internal builds.

After that, Steve, Cory, and I went over a bunch of our projects and did some updates and setting budgets and priorities. We are going to keep pushing on this every week. We currently have all of our projects in a section called adilas community funded projects. It is still a work in progress, but we are making progress and trying to setup a good work flow.

Shannon and I worked on adding some new graphics and links to an entry from earlier this week. It shows all kinds of graphics, links, research, and history on where we have been and/or are going with mapping out the system and trying to figure out a way to simplify the appearance and navigation of the system. There are a lot of moving pieces in the engine. Some of that we want to hide and keep being the scenes, some we want to fully expose and let people play with the features and tools. Good stuff.

Here is the link to the page with all of the links and graphics:

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=4933

See attached for a new graphic that shows all of the adilas business functions laid out over the GPS core layout graphic. It ends up looking like a number of pie charts, but it really shows the pieces that help and create the different business functions.

Steve has this mapped out already. This will allow you to do the first half of an internal build (input) and wait until you have your quantity for your output.

This will use elements of time.  Helpful for extraction.

Added some new graphics to the help file for the interactive map. These are a small cluster of graphics that I use for teaching and training. See this link for more info. The images are listed below the interactive map graphic.

https://data0.adilas.biz/top_secret/help.cfm?id=393&pwd=map - help file for the interactive map

I fixed the master corporation list page (an admin page) so that we could point corporations to the correct servers without having to choose from a drop-down. This allows us to use all kinds of different domain names and sub domain names. This will be very important as we move more and more into the virtual realm.

See attached for a new graphic that I put together to show some of what we offer inside of adilas. It is a combination of graphics that we made for our ecommerce site and allowing people to pay for a new site through ecommerce and online payments.

View adilas easy system setup with ecommerce - from our online store

Josh and I got together over a GoToMeeting session. He is working on an inventory engine that will warn you when certain items and/or item categories get to a low or possibly low level. His new code goes clear out the item level. The old code just went to the category level. We did some light debugging and just touched base. Pretty casual meeting. I did let him know that Steve has some new projects for him. He was excited about that.

Working on some new graphics to show business functions overlaid on the adilas interactive map. Nothing really to show yet, just playing around with ideas and concepts. Emails and other small to do list stuff. 

Paying bills, invoicing and doing a deposit, recording notes and going back and rereading entries from earlier this week. I got a demo from Calvin on the new sub inventory stuff on his custom PDF labels, using the adilas label builder. Pretty cool.

I also spent a couple of hours writing some answers to a security questionnaire that was presented to us. I have included a copy of my answers. Hopefully they are honest and thorough enough for the task at hand. See attached for a copy of the security document.

https://www.newtekwebhosting.com/our-infrastructure/ - server infrastructure at Newtek hosting - adilas security

https://www.newtekwebhosting.com/disaster-recovery-solutions/ - disaster recovery at Newtek hosting - adilas security

Added some more security info to elements of time # 4978 - dealing with security documents and screenshots.

Calvin had me cascade some new database tables and settings to all of the servers. After that, I tried running the new label builder. Calvin and I ended up on a Zoom session and spending some time together and working through some small bugs. That took up most of the afternoon.

Emails, small bug fixes with Calvin, installing new software updates, Bear 100 stuff, and server resets.

Monday morning. We had Josh, Steve, Eric, Alan, and I all on the morning meeting. Dustin popped in/out really quickly as well but most of the guys were just reporting on where they are at and setting up other meeting times.

Steve is really excited to get things planned out and moving. Over the weekend, he had some talks and discussions with a client about setting up an analytical corporation and allowing the user/person to dive in deeper on some of the data (analytics and even deep surgery - without touching the master systems). We would have to set up a few different things, but basically a full system (aka just hosting a server or basic web hosting) for the client and then allowing them access to anything that they want (FTP, RDP, API sockets, auto processing of data back and forth, etc.). Interesting conversation. The other really interesting thing is the question, what is the value of data and being able to interpret that data? It is huge. Data and its interpretation are definitely a form of currency to some of these companies.

In between the different meetings, I was working on putting some outlines and drawing some boxes and lines on top of the adilas interactive map. The goal here is to display the different pieces and how the 12 main business functions play with the different sections that we have shown. Here are the 12 main business functions and each one will be a link to the newest image.

1. Sales, Inventory Tracking, & POS (Point of Sale) - shown on the map
2. CRM (Customer Relationship Management) - shown on the map
3. CMS (Content Management System) - shown on the map
4. Online Expense Tracking - shown on the map
5. Payroll & Timecards - shown on the map
6. Calendar & Scheduling - shown on the map
7. Create Data Relationships Between System Players - shown on the map
8. Backend Office & Accounting Functions - shown on the map
9. Histories & Reports - shown on the map
10. BI (Business Intelligence) - shown on the map
11. Web Presence & eCommerce - shown on the map
12. Virtual Data Portal (Big Data) - shown on the map

Eric and I jumped on a branch and tested some of the custom 3rd party API sockets that Eric was building. We did some local testing, some find and replace, and talked about processes and procedures. Good work session.

2/17/20: Code has a bug or needs to be fixed. Need to narrow down where issue in the code lies. Currently when you pull gl deposits to export to excel, it just runs the report again. Won't pull gl expenses at all. This was on data2- it worked in steve's local environment but not here.

From Mike on 9/21: I updated Steve on need for full G/L for all accounts and to be able to query it for an entire 12 month period.   In any IRS or State audit we would need to be able to produce a G/L.  As we begin targeting large accounting groups the g/l report will be an expected output of the system.

10/09/19 updated the query to show YTD from Month chosen

Used CreateDate DatePart

From Mike 

We are compartmentalizing the various G/L sections and kind of reminds me of accounting back in the day

You had a Bank G/L , a A/R , A/P GL , Income Ledger, etc. and ultimately the accountants had to tie it all together.

So we now have

Entire Bank G/L Section

Expense G/L Section   

That just leaves us with the below needed ledgers which could be run independently and be labeled as additional Ledgers :

Inventory Accts  --- Probably 1 report since Big

Other Current Assets /Fixed Assets /Other Assets – Probably could combine into one report

Income Accts  - 1 report since larger query

Other Income / Expense  Accts  ( “Below The Line” items on Income Statement so should be small report )

Other Current Liabilities /Long Term Liabilities – Probably could combine into one report

Equity Accounts  - ( If you remove the Net Income Line from this report the Query should be small )  - ultimately you could get G/L data for entire income statement in various pieces above which would mitigate pulling that line item in the Equity Ledger Report, thus keeping it a small query

Under This Structure we would want all General Ledger Accounts to be one of  the below “Types” to then allow us to run the independent ledgers

Bank

A/R

Inventory Acct ( Includes Raw Materials / WIP )

Other Current Asset

Fixed Asset

Other Asset

Other Current Liability

Long Term Liability

Equity Acct

Income Acct

Costs of Goods Sold Acct

Expense Acct

Other Income / Expense Acct

Working on new graphics. Spent the whole session building out adilas GPS core graphics, adilas interactive map graphics, and combo (both core and map) graphics.

Met with Bryan and we covered some different topics. We went over some Square (merchant processing) questions, CSS changes (white label look and feel), and then checking on progress on the sub inventory searches. Good meeting and mostly just getting squared away and getting traction and direction.

More graphic work on the adilas GPS core, adilas interactive map, and combo graphics (both core and map combos). See attached for a number of smaller graphics.

Met up with the Bear 100 folks. There were 4 of them on the meeting. We went over a number of custom buttons and interface pieces. They had a small to list for me. I have attached my notes. Mostly, they just need ways of seeing things quicker (stats at a glance). Should be easy enough.

Downloading runner lists for the Bear 100. Prepped and combed the data to make sure I had good data. I will be importing new data tomorrow into adilas.

Prepping and uploading 333 new runners for the Bear 100. They will be using the adilas system this weekend for a 36 hour, 100 mile race across Northern Utah and Idaho.

Steve was talking about getting a designer to help us with the Bear 100. He would like to take it out to Google maps, GPS, mobile friendly, and even allow for people to use our site to do sign-ups and other pieces. We could have the site tied out to ecommerce and allow for tons of other options. That could be fun.

Eric came into the meeting and had a couple of questions about customizing the invoice and quote process. We talked about parent inventory, sub inventory, parent attributes, flex grid tie-ins, and even black box custom tables. We also talked about adding in some blank or generic flex fields in the quote line items and the invoice line items. They want some custom fields per line item. Steve was saying, don't tell me what you want... show me. That way we know what tool to use and where to put it into play. Steve was also talking about maybe going up steam and setting those moving variables up higher on the customer level. In a way, the over arching question was I want to extend the existing options and functions per invoice and quote line item. We then have to help, how do we figure that out and what solution could we use to solve that problem? Good stuff.

This doesn't play in quite yet, but at some point we would love to get into real in-line database extensions. That is somewhat of the bigger brother to the flex grid tie-ins. Being able to add and subtract data points and data fields per section. As a side note, we have tons of companies that virtually commandeer (take over - like a pirate ship) any field that they can to get the job and/or task at hand done or finished. Kinda interesting.

Steve wants to get more information, from the source. He would like to get a real world scenario and then make a plan from there. Not just a quick band-aid, he wants to help develop the solution. What are the processes, what are the needs, what already exists, and what else is still needed? It keeps getting deeper and deeper (4 and 5 levels deep).

There was an analogy of a "part changer" - think of mechanic that just swaps out part after part in order to fix something. We really need the mechanic that gets in there and looks at the problem and then makes a decision. From Steve - It's not how fast you go, it's how well you go fast - older Porche commercial.

///////////////////////////////////

Switching gears, we started talking with Wayne about servers.

We were talking about virtual machines, physical servers, load balancing, and the difference between hardware problems and software problems. We were talking about clusters and getting redundancy and depth of options. If we stay with Newtek, we need to build in some of our own pieces. If we go more with AWS, we get to just use some the existing pieces. There is a trade off - AWS has more options but it also a deeper pool. Newtek is not as deep, but in some ways easier. We were also talking about rollover, fail safe modes, mirrors, etc.

We spent quite a bit of time talking about the Adobe ColdFusion engine and how we could potentially configure cluster type environment. When you get out of a single machine environment, what do you do with the database. On a single machine (server or dedicated box), it is simple. On a cluster, you have to keep things moved and/or separated. We would love to break some of the system down into their own databases. The idea here is making each database corporation specific vs server (whole box) specific. We have talked about this for years (since 2012 ish) and have called it world building and other project names. We really want to do this, but we also know that we have tons of code changes that are needed. We could separate out the shared tables in the existing database schema but we would have to do it table by table. As a side note, we have already done this very process for invoices, invoice payments, po/invoice line items, customer queues, sub inventory, etc.

One solution would be to create a corporation specific datasource (pointer to a specific database) and then help that get migrated and pushed around. We also talked about loading in objects per user that has all of their corporation specific settings and values. Eventually, we will still need to break out the payee/users so that we have a master list and then allow them to be merged and virtually bridged to any corporation and even any system. We still have all kinds of exceptions, such as be in corp x but pretend like you are in corp y (look and feel and settings). It gets kinda crazy.

The subject started to switch to more and more object oriented programming, storing values in session objects, and other objects that are server based. We also talked about database server clustering and moving all databases (per corporation) to a dedicated database cluster that only served up data and content. Lots of possible configurations and options. Both Alan and Wayne were talking about cross-schema queries and all kinds of advanced things. As another side to this equation, we are seeing more and more of a need for aggregated totals, auto processing, daily task management, etc. All of these things play into the mix. We are seeing certain tables that are great as shared tables and other tables that really need to be independent and corporation specific.

As we move forward, even towards a fracture type model, we will need to separate databases, logic, move more towards object oriented programming, API socket calls, etc. Just for fun, Wayne and Alan were talking about different levels and using bigger teams - backend guys, database guys, middleware guys, frontend and UI (user interface) guys, etc. We aren't that big.

Steve's idea... Alan, Steve, Dustin, and Brandon are all going to be at a convention. Let's use that time to do some planning and take it to the next level. That's a great idea.

Shannon and I had a work session working on the system glossary. We were working on O's, P's, Q's, and R's.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=4030 - online glossary of terms

We also talked about some of the new graphics and things that are happening around the system. Just for fun, things change all the time. I told Shannon that we used to use this saying "Everyday is Christmas" - meaning lots of new things everyday. She said that was a funny line and keeping it positive vs being just fully overwhelmed because everything really does change so much. Anyways, sort of funny, in a way.

Eric popped in and asked some questions about transitional invoices and how all of that works. We ended up talking about putting those requests into our community funded project list. Steve and I want to help to funnel the users and their requests into our project management options. Steve and I are going to be trying to focus on core vs custom and trying to figure out how maybe the custom could be core with settings (how to make it happen and/or play through).

3D calendar and time management. We are seeing people wanting to get into smaller and smaller time periods just as hours, minutes, seconds. Most of our stuff is currently on the day or single day type environment. 3D calendars deal with years, quarters, months, weeks, days, hours, minutes, and seconds. Our users may even want to determine what their unit of measure (date specific) is... that way they could choose what level they want to play on (days, hours, minutes, etc.).

https://data0.adilas.biz/top_secret/help.cfm?id=479&pwd=core - help file for world building and showing the layering options

https://www.adilascontent.biz/top_secret/images/corp748_EA81FBBDE6/pdf/doc_26325_9F86EF2854.jpg - small drawing on how the upper levels of world building may be configured and such.

Steve and I are seeing our way through the multiple databases per server type option. Those are technically the cluster and solar system levels in the world building pieces.

After Steve and I got done speaking, I jumped back on the special accounts project (rewards, customer loyalty points, gift cards, etc.).

Met with Josh and pushed up some new code for what he is calling an inventory engine. Basically, it is a warning and threshold system for part/item categories and on a per item level. Once the system can tell the item is within the threshold (summing up total quantity on hand minus the current cart quantity), it will show yellow, orange, and red warnings, depending on how close the levels are to the set thresholds. In a way, it should help companies that use it to get their reordering done in a timely manner. Most of the session was spent on that subject. There was some light talk about some other custom reports and settings, but mostly on the inventory threshold engine.

Working on the special accounts project. Added in some logic to watch for rules that are set to inactive (don't use or don't play). I also got contacted by Molly and had to jump on a quick cart fix for the inventory threshold engine stuff. Made the changes and push the new files up and online.

Just Dustin and I on the morning meeting. I had a couple of phone calls and emails, but pretty quite today. I spent most of my time working on some runner stats and Bear 100 mile race totals and stats. Some of the Bear 100 data team wanted more counts per aid station. This weekend will be the Bear 100 mile race. They have used adilas since 2015 for their race tracking. They have 13 aid stations over the 100 mile course. We catch the runner data out in the field and in the mountains and then use HAM radios and CSV files to pump the data into adilas for a somewhat of a live tracking while the race occurs. Family members can add notes and comments and upload photos while watching the progress of their runner. Kinda fun and fully custom but a creative use of elements of time.

Worked on adding help files for the special account project. Going through some of the pages and doing light clean-up.

Working with Bryan on a couple of his projects. We did some CSS stuff, checked out some logic, and went back and forth on some questions. One of his projects is adding in a last modified date/time stamp on both parent items and child inventory items and packages. We have histories, but we need that last modified date to help with API sockets and syncing up data between multiple non-native systems (API stuff). He keeps getting better and better at what he is doing. On a different topic, Bryan has customized a small section of elements of time and is doing his own project management and flow. No one else has his stuff, but that is how he is running his projects. It is fun to see him tweaking out the application to fit his needs.

Met with Jonathan over a GoToMeeting session. We jumped right in and got to work on where we are at, on mapping out the system. Jonathan likes to call it cleaning out the garage. We went over some of new graphics that I pushed up and online. See element of time # 4933 for details. Next we talked about how we got to the 12 main players and how that lead to the 12 main business functions. Jonathan is getting his head around the 12 main players, but still has some questions about how everything works together in the business functions. He would really like to know more about the flow and processes that take place.

As Jonathan asked questions, we drew some sketches and used some of the new combo graphics (core and map images) to help show flow and processes. As we got going in deeper, we ended up drawing the magic square or main 4 square (a grid of 4 squares - one for invoices, one for PO's, one for deposits, and one for expenses - those 4 tools then affect the bank balances and the inventory levels). After the meeting, I created a better graphic, so that I didn't have to draw it by hand every time. See attached for some new graphics.

After that we talked about how awesome it would be to show some scenarios and then animate it using the different graphics, cores, maps, sections, and pieces. We briefly went out to some of the old Flash training that Russell did and looked around. Once there, we clicked on the Flash training and let it play through a number of things. Use this link to get to that older training page. It may take a little bit to load, but it is worth it.

Our next topic was the adilas formula. By itself, it doesn't look like much, but if you can get your head around it, the concept takes on a deeper meaning. Here are a couple of links to the adilas formula flyer and help files.

https://data0.adilas.biz/adilas_formula.pdf - one page pdf flyer on the adilas formula
https://data0.adilas.biz/top_secret/help.cfm?id=487&pwd=formula - help file on some of the concepts inside of the adilas formula

Jonathan had me go take a quick look at an outside site called zoho. He thought that maybe we were kinda like them, in that we have multiple different products that work together in an integrated system. We didn't spend much time there, but I thought that I would at least include it in my notes. There are a number of other products out there that offer different suites of products and services. Another one is DOMO and another is NetSuite and probably tons and tons more. Just put them here for the record. It seems that everybody is somewhat headed in that same general direction.

Anyways, we got back to training and talked briefly about how our entire build up came from needs in the operations and then eventually opened the door into the financial and accounting world. Basically, by following cause and effect relationships and then developing the next logical step, we have built out an awesome product. No one knows about us yet, but we have great potential. Jonathan and I talked about getting to know the system deeper and deeper. We used the words "prepping" for what is coming and what talents and skills we would be pushing and throwing at it in the near future. We ended the meeting by talking about line by line, progression, and versions. Sometimes it takes time to build up the base. See attached for an older Microsoft Excel doc that was used, back in the day, when we were trying to get a bank loan. That isn't important, but the contents of the Excel file have some fun info and stats.

After the meeting, I spent a ton of time making new graphics, recording notes, and pulling some of the pieces together. It was kinda fun.

Working on help files for the Bear 100 and also working through runner count logic and who is still out running vs who is did not finish and who has finished. Checking lots of records to figure out rolling counts and stats.

Working on some Bear 100 stats and logic. I had to go clear out to paper and scribble some ideas down and filter it down from there.

Once the morning meeting started up, Steve and I were talking about the new servers and getting the developers over and pushing on those new servers. We also talked about getting some of the new graphics and training material out to our users and reps. I spent most of the rest of the session updating data 15 and data 16 servers with some new files.

Shannon and I had a work session on the online glossary. We were working on R's and S's.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=4030 - online glossary

Officially release the data 16 server to Mrs. Shari O. She does all of the new system setups. Went into the server and made a few small changes to some settings and such. Emails out to developers about the new serves data 15 and data 16.

Back working on some stats and runner counts for the Bear 100. This year's race will start tomorrow at 6 am. Trying to get a few last minute tweaks to help it be even smoother this year. Good stuff.

I got a call from Shari O. and we jumped on a tech support call together. A client was having a small issue with payables and being able to pay multiple expenses with a single check. We went through it and everything seemed to be fine. We voided out the testing expenses, made notes, and Shari O. will call the client back and help them know what to do. We didn't solve any issues, everything worked through the times we tried it and actually ran some test data through.

Helping with the Bear 100. Went into town to help with the pre-race meeting and picking up drop bags. The Bear 100 guys use adilas to track all of their runners through the different aid stations.

Working on the new code changes for the Bear 100. Adding stats and totals to the full race view. The new totals show up at the bottom of each column in the full race report. Late night.

Working on the runner stats and counts. Pushed up the first version to help the radio folks (people who run the data portion of the Bear 100 mile race). It isn't all done, but it is at least workable. Super early morning. Went to bed last night at 1 am and back at it again at 4 am. Pretty tired.

Went up the canyon to help with the Richards Hollow aid station. While up there, I worked in my car and out of a camp chair on the new runner counts and stats page. This is a page that just shows each aid station and what the specs and/or stats are for each aid station. This deals with things like how many runners are still out, who has dropped, who didn't start, who has finished, and who is still out running - for every aid station. Lots of logic and going over complicated data sets.

Finished up the new runner counts and stats page. Also built out some links back and forth between the full race view and the runner stats and counts pages. Along with that, we built a new page that highlights runners that are part of certain statuses - like still out running per aid station. The new page has some special formatting to help the users do and find what they are looking for in an easy way. Long day already. Glad to get this part done.

All research, design on new UI development for core adilas.

Tons of emails, paying bills, and prepping files for a merge that is coming up. Lots of little things. Later today, Alan and I will be headed to Las Vegas for an Adobe ColdFusion conference.

Headed to Las Vegas with Alan for a ColdFusion conference.