Sub inventory and cost controls (packaging) and/or parent/child inventory was started in 2014/2015. The first round was released in December of 2015. Since then, it has gone through a number of tweaks, changes, and sub rounds. There have been millions and millions of child inventory packages over the years since its release. The round 3 project is a rework to make sub inventory and cost controls even more stable and easier to user.

The round 3 project contains the following sub projects:

- Formal Planning – Multiple Converging Projects
- Sub Part Categories & Category Inheritance
- Mini Conversions
- Logic & Output Changes
- Parent/Child Rules & Settings
- Pricing Matrixes & Tiered Pricing
- Simple Sizes & Colors
- Recipe/Builds & Sub Inventory
- Discount Rules & Other Discount Options
- Subs In eCommerce Land
- Custom Labels & QR Codes
- Using Elements of Time To Track Subs
- Sales, Coupons, Campaigns, & Promotions
- Loyalty Points & Special Tracking Accounts

// past funding for earlier rounds

$10,000 paid in by Calvin Chipman of Chipman Software, Inc. Amount was paid in by a loan to adilas, and we have decided to apply it to the packaging project. - Logan, UT. 5/18/15. As an update, the loan has been fully paid back as of 3/26/16.

$10,000 paid in by Adilas.biz to help push the project along.

Working with Bryan on 8/14/19 - took a couple of notes on ways to help speed up the process. See element of time # 4848 in the shop for more details.
https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=4848 - small background mini project that is needed to help us go faster and smoother.

Sales, Promotion codes, coupons, campaign tracking, & referral tracking - sales & marketing options

- We have added in a discount engine and have done tons of work on standalone discounts, in-line discounts, and campaign tracking.

On the morning meeting with Steve and Russell. They were going over the news and updates section. Lots of talk on where to store the filters and sub features - at the corp level, at the admin level, and even at the employee/user level. The filters and settings will help us display the correct feeds and news and updates back to the users. They also talked a bunch about pushing 3rd parties over to the adilas marketplace. The eventual goal is to get all 3rd party solutions to have an active adilas market account and profile before we add them to the adilas 3rd party solutions page. Kinda force them over there before we do any outside advertising for them.

Fun little one linear from Kelly Whyman - "If you touch, you track."

On elements of time, Steve is wanting to setup internal templates and being able to fully control them and/or lock them down. Basically, a way of making a normal template but not allowing the users to change and/or manipulate things. Basically, we create it and let them use it, but we don't allow direct editing of certain pieces (maybe only certain things or limited options). Steve was mentioning a virtual ice-down on some of the settings and features that are turned on/off. This is not an ice-down date, but it is a form of ice-down but icing down settings, features, and functionality.

Some of the custom settings are almost becoming their own database tables and we have to make sure that things are setup correctly.

At 10 am to 1:15 pm, Eric popped in and we worked more on the loyalty points and gift cart stuff. We went into media/content and looked at all entries under "loyalty" and got some good ideas. That spun us off on some side tangents. We also talked quite a bit today about how things will be tracked, showed, and how things will be held on the balance sheet. One of the good breakthroughs today was an idea of how we could tie in these new special tracking accounts to existing balance sheet items. See attached for a small screen shot.

The uploaded image is a normal BSI (balance sheet item). It shows a main and normal subs. We then talked about how we could add additional options such as: main_account_types (#1), account_type_rules (#1.5), special_accounts (#2), and special_account_transactions (#3). We also talked about some of the stacking order under the main balance sheet items and how that would play out.

We recorded a number of new notes and even did some light scenarios using small drawings and such. Towards the end, we talked with Steve about the accounting side of both gift cards and loyalty points. Gift cards need to be tracked on an invoice, the part number needs to not be recorded on the P&L (revenue) but needs to be deferred to the balance sheet. We also have gift cards as a form of payment. We talked about some of the invoice payments that might need to be tied into make that happen. We also talked about how loyalty points and coupons are basically future discounts of sorts. Those values don't really show up on the balance sheet, but do need numbers below the surface. A discount could be in-line and/or standalone. Both the loyalty points and coupons reduce revenue and need to be treated like special trackable discounts or price adjusters (variable of price). See other attached document for more details and notes.

In early working on the new payroll changes that Shawn submitted. This is dealing with county based withholdings and new state calculations for Indiana.

Steve is seeing the 3rd party solutions page extending into a virtual permissions for those outside solutions to get access to any of the 12 main players. We need to show what is available and allow for what windows and doors are open. This is really common for some of the clients that are dealing with oversight or overseeing certain pieces (virtual auditing and such). We need to keep our clients data safe but also need to allow the different parties to allow or dis-allow between themselves. Maybe the secret is allowing the clients to build their own relationships between the possible different solutions and/or outside parties.

At some point, we may need some kind of history of who is opening and closing the API socket windows and doors. That may help later on if we need to figure out who is changing what.

Eric will be popping in around 10 am to talk about loyalty points and gift cards.

Meeting with Anthony Harrington about loyalty points and gift cards. Eric, Steve, and Brandon were on the meeting with him.

- There are tons of daily discounts. It gets crazy in order to manage all of those things.

- There are a number of steps that need to be done in order (on carts and checkout process). One of the things that they would like us to do is - dumb things down and make it more simplified.

- They would love to have preset discounts, sales, and promotions. Also, a lot of the different discounts are based on a day of the week and/or a specific time.

- Eric has done a number of these custom discount and pricing engines. Eric was saying that some of the discounts are not created equal... bogo (buy one get one) vs auto calculating all similar items and then repricing based off of quantity (just as an example).

- Some discounts and promotions will be standard (hoping to catch 80% or more). There may be others that are just plain custom. Those still needs to stay on that level, meaning we may still need the option for custom code.

- Anthony would love to help push the development forward in such a way that the users (adilas clients) could use the system to tweak the system. If they, our clients, need to call a developer all the time, that gets crazy and very expensive. The solution needs to be out to sales and promotions and virtual campaigns. Eric and I have also talked about allowing discount rules and such.

- Anthony has some price grouping and some needs there. Similar to smart group buttons and tiered pricing structures. He would love the cart to be able to keep track of those pricing tiers and virtual groups. He would like the ability to move and manage pricing structures based on groups (even a subset of part/item categories).

- Lots of needs for time based discounts such as happy hour, certain deals, etc. It would be super cool if we could setup all of these rotating discounts and the cart is able to apply those on the fly and as needed. Basically, we need an automated pricing engine.

- Some of these discount rules may need to be built and held in a coupon, sales, and promotions type system.

- Eric was talking bigger volume shops vs the mom and pop shops. They all want that kind of feature but it comes down to cost. If we could build it into the system, it would benefit all parties.

- Eric would like to see a printed list of what kind of discounts they offer. That would help us in the background make sure we can build out the rules that would be needed.

- Anthony would like to know a cost and timeframe. Eric was talking about phases and options for deployment and development. Then Eric talked about building out the standard features, all-a-cart features, and then also being able to customize things if needed.

- They would really like the pricing tiers to work similar to the smart group buttons without having to tie them into a button. Basically, behind the scenes, they have rules (what to do) and assignments (who can play). That is the same basic model that is still needed, just not tied to a button. This may end up being part of the pricing engine. The cool thing would be rules that could also be tied into time and time-based promotions. The higher level (meaning the top level or group level) of pricing really helps with speed to market and ease of use.

- Steve was saying that sometimes it takes years to get a stable picture of what is really needed. That is a huge key.

- Sharing knowledge and helping others be able to run and go forward. Anthony has some great operational experience... we would really love to tap into that. A huge knowledge base of experience. Another huge asset is perspective and vision. Those are both huge assets.

- There is a huge training need. Some people will use what we have but they may not even know we have it. That comes back to ease of use and education.

- Molly popped in - what comes first, the pricing engine or the coupons and sales?

- There are a few main pieces to help everything play in and work together. We are seeing sales and promotions, pricing engines (cart logic), custom labels, sub inventory, mini conversions, discount rules, tiered pricing models, customer loyalty points, gift cards, coupons, etc. They all play together and have similar pieces that need to be coordinated. We know we need all of these pieces, the trick will be what comes first? And how do we pull things together?

- As a side note... when setting up pricing groups, we may need to pull in parent attributes to help us create good groups and grouping.

- Small complaint on packaging and sub packaging, when they add a new one (sub), they have to re-enter the price (every time). They would love it to be tied to a pricing group. They also want to make sure that we keep them in a good process path. They would love the new subs to pull in the price from the group pricing vs setting it every time. They do want to be able to change it if needed, but they would love it that price auto pulled itself into a preset pricing group. This is a big priority to help make it easy and more standard.

- Mini conversions are really needed here soon. The deeper we go, the more we are needing that ability. What they are calling (our clients) packaging is really mini conversions of sorts. There are a number of clients that are doing internal manufacturing inside their systems. We need to help them out with that. Also, when the customers buy things, they want to be able to search for one item (not 50 million), and then be able to buy and sell those items in different sizes, packages, and conversion pieces. In the frontend, they want it really simple. In the backend, we need to mix and blend and cross-tie things in and maintain the correct relationships. That is really huge.

- The more we help to automate things, the less chances for user error.

Emails, paying bills, and on a Zoom session with Calvin. He showed me a new demo of where he is and we chatted and talked about the next steps. He is making good progress.

Talking to Steve about buttons, barcodes, labels, coupons, etc. They are all ways to get things into the cart and/or affecting pricing and discounts. That is an interesting point.

Steve has really helped me delegate more. He is good at it and even encourages me to do the same. Sometimes it is just an idea or a suggestion, and other times, he may help nudge the boat in the right direction and then it makes it easier for me to do what I need to do to advance the ball. Good teamwork stuff.

Spent most of the afternoon doing tech support, emails, recording notes, and talking to Shawn about new payroll changes. Shawn and I got his system all up to date and new files pulled down. I called and chatted with Steve (see a couple small notes above) and then did the other things. Busy day.

On the morning meeting with Steve and Russell. They were talking about how Bridgerland could help with outside development and doing smaller projects. Part of the puzzle is how we empower our users. It is so important to empower our users at the level that they need (go to the source). That is a huge core concept.

Taking the email options out to the bulk level and also allowing users to make the email come from their own servers.

As the guys were talking, I was doing some research on the old adilas website. Lots of good PDF files, help files, graphics, and flyers. Here is the old website link: https://data0.adilas.biz/old_index.cfm

Eric wants to talk about coupons and loyalty points. We talked about a guy named Chris Johnnie and some prior planning that may have been done by Russell and Chris. We are trying to pull things together and make everything happen.

From Eric - It is so expensive to keep stopping and starting - we lose tons in the transitions. We need to focus and stay on track.

Eric was expressing some concerns about sub inventory on the production side of things. Steve chimed in and was talking about how some people don't even know what else is possible and already built. The trail is faint and many people have been gone in different directions. We need to define the best path and then help educate others to play the game.

Manufacturing is a whole new level - You have raw goods being made into finished goods. Lots of internal flipping and tweaking. You need bill of materials, sub assemblies, recipes, other tracking needs, etc. We talked briefly about parent inventory and sub or child inventory. Some of the big needs come when they have sub assemblies and use semi raw goods and then push it into another finished good or product. You have to be at the sub level in order to really track that information. It gets into sub locations and sub phases and all kinds of other subs. In the background, we are seeing the _Z coordinate (depth and stacking) coming more in to play.

We are having a number of clients that are fighting against change. Some of the subjects are the way the one-to-many relationships are setup and what the individual people think should be the best option. Some of the questions are things like - one PO with multiple line items or one PO per one line item. Which one holds the location and how do you move things around. They want to group things but also be able to move things independently. They need both... basically, I'm part of this group but I also play over here and here. Very interesting.

This is a side note, but we end up spending so much time managing our customers because they all want to chime in and say what they feel is the best. Custom is awesome but it can also get us in trouble. Custom is really easy on existing and established pieces. One of the main problems is when we get into uncharted territory, people have all kinds of ideas and what things would work best. Once the trail is set and people are using it, they tend to go with what is already there unless we make it too hard. When the trail is not fully established, it turns into the wild west (anything goes) really quickly.

Once people get what they want, they tend to want to get to it quicker. They also want more. This could be more options, more control, more access, more of almost everything. They basically get addicted to data and ease of use.

Steve was doing a demo on sub phases, sub groups, and sub locations. Lots of using elements of time and special flags and tags to track all of the details.

One thing that will help people is showing them how to get back to their details and data. We (developers and power users) know things well enough that we pop through screens, skip steps, and go really fast. A new user is watching and they just get lost. So many moving pieces. It hasn't been smoothed out and/or standardized yet to really make it manageable and easy to understand. We either need to slow down and/or make the path more direct and discernible. Make it obvious and straight forward.

A note for us... We can use these subs to hold the sub details and sub data. We need to show things in very general levels and make it look simple unless the user wants to get clear down to the lower detail level. Think of the world building graphics that have universe level, world level, location level, group level, individual level, and the underlying data level. We need to allow the users to navigate at whatever level they feel most comfortable. We need all of the deep, deep, sub data, but that may be too much detail for some people and/or users.

There will be a greater and greater needs for mini conversions and how that effects things. Steve has already done quite a bit of work on the custom/build_complex_labels.cfm page. We need to use that as a great starting place. Lots of moving pieces. It goes like this... You have to have a parent item. Parents have subs or children. Those children then get broken down into smaller pieces and sub packaged. That is mini conversions.

We keep pioneering small little projects and getting some testers and people who keep pushing on things. Adilas is literally a giant testing environment and a virtual idea farm. We keep planting and harvesting ideas. They just keep coming.

Going back to manufacturing - there are tons of batches, sub batches, lots, and even reprocessing and repackaging pieces. We need to keep defining the road and helping the people who will be coming down the road later on. Kinda like Eric was saying... We need to focus and get pieces done and standardized - we get pulled in so many different directions. We lose a ton in the transition and switchover between projects. It gets very expensive and takes a ton of time and energy. In manufacturing, they often will set up an assembly line for a certain run... They then run that product until it is done. If they had to switch lines (assembly lines) every couple of hours, they would have tons of down time. Maybe we need to do similar type things. Make a plan and then work your plan.

The other gem is using the people who know it... get the reps and the clients together that know what is going on.

Flow - We can link all kinds of stuff together. That is a whole other level. If we can get the job done and get the person to the correct next step, we can help them keep moving forward. It comes down to flow and planning. Steve wants Dustin to help with some of that flow. Steve's words... "we need to train the system". That helps the whole thing go better. Dustin's words were... "the system almost needs rails". They then talked about wizards, steps, and showing a logic path and where they are on that legend or helping them know what is next and where things are at. Walk them through it. This could be crumb trails, legends, wizards, etc. Good stuff.

Working on adilas ecommerce pieces and training details.

Morning meeting. Steve was working on code. I was updating adilas ecommerce stuff. Russell came on and reported on some of his projects.

Information from Russell and Chris Johnnie about coupons, loyalty points, and gift cards.

- Gift cards - be able to get a random number and put it onto a card. The random number makes it harder for someone to use another card (security issues). He needs to be able to scan it and see what is on the card. He also needs a spot to scan the card and have it use that as a payment option. It needs to go full circle. They need to be able look things up, add to it, take away from it, and view levels. Both tied to a customer and not tied to a customer (generic card). Be able to use this in both the normal secure cart and the ecommerce cart. Easy to load card.

- Punch cards - every cart that is $15 or more is eligible. If the cart is a counter sale, they could be prompted to sign-up if they want. Once they are in, the points would automatically accumulate based off of the rules. Once they get to a certain level, say 15 points, they get $10 off of the purchase. They want it really automated and almost a non-thinker type process. They want a quick interface to allow for the sign-up process.Just to recap Notification when a customer is eligible, notification when a customer has points they can redeem. Customers can choose how much they want to pull out. They must pull out blocks of points at a time. For example they have to pull out 15 Points to get $10 off. They cannot pull 10 points and get $7.50 off.

- Coupons - add, edit, copy, delete (permanent hide status), details - coupon code, coupon text or description, quantity, status, type ($'s off or % off), usage (unlimited, limited amount, unlimited no additional discount, limited amount no additional discount) , customer limit, specific item or part id, status (blocked or open or deleted), minimum value to activate, etc. See Russell's page afb_coupons_rules_logic_settings.cfm - branch ram-42. See the link below for the spreadsheet planning.

https://docs.google.com/spreadsheets/d/1ANHIdJx6zbV4BM_pZ1biOTmK-SJrKwLUoxuHYMA7BJM/edit#gid=0

10 - 1 with Eric - planning out the loyalty points and special accounts.

Estimated amount Chris is willing to contribute

Gift Cards

$3500-$5000

Puch Card

$1500-$3000

Cupons

$1500-$3000

We talked quite a bit about using the builders and logic (part of the UI) as the master options. The builders might be things like locations, part categories, customer types, and even the item or part id level. Lots of field names and lists to  help us make and generate the rules.

We do have a more complicated issue when we do cross-corp loyalty points. These cross-corp things struggle with pre-calculated totals and such.

We talked about migration paths and getting existing customers into the basic loyalty points as well as getting new customer using our basic adilas loyalty points.

User communities - who wants to join up and put a list of priorities together. We then work and prioritize these features and get them in place as soon as possible.

As part of the conversation, I gave Eric permission to run with the basic loyalty points. He will get a plan ready and then re-present it back to me before going into the coding stage. Good stuff and trying to remove as many obstacles as possible.

Meeting with Chris - rough budgets - Gift cards (3,500 - 5,000), coupons (1,500 - 3,000), loyalty points, rewards, and virtual punch cards (1,500 - 3,000)

Chris wanted to make sure we got his other details from Russell. Chris is looking for timeframes. We went over what Russell passed over to us on element of time # 3742.

Steve jumped on and started talking monies and strategy for repayment. Possible white label options - going forward. Chris has been a great asset and contributor for years now. The goal is to get the developers funded and pushing on the projects with minimal side tracks (focused). We are looking at $2,000 this month and then $2,000 next month. That would be a great start. Whatever Chris throws over, we'll put it on the balance sheet and then pay it back out at $1,000 per month. Steve will enter things in and then send Chris a screen shot of what was booked.

Different topic - competing with Air B&B - booking timeshares, rentals, reservations, etc. All kinds of people put up their properties and then let it get scheduled out, paid for, and reserved. This seems to be the new way people are booking their vacations and travel. Basically, people have the items (camper trailers, cabins, houses, apartments, condos, etc.) and are willing to rent them and let others use them.

Affiliate programs and referral programs - more extended options - it could go all kinds of ways and get pretty deep. This could also tie into coupons, discounts, campaigns, and even rentals and reservations. Steve and Chris were talking about taking Air B&B type concepts and mixing that with affiliate programs and referral programs.

Checking in on the morning meeting. I have been out of the office most of the week. Steve and I chatted this morning about the need for new independent developers and getting people into the mix and into the family. There is a real need there. We then merged in some code from his branches and pushed up files to all servers.

Looking over ideas for loyalty points. Lots of good info on element of time # 3778 in the adilas shop.

What is a liability? What are the differences between real and phantom values? We need the values recorded for both real and phantom, the difference is how firm and/or fixed the liability is. Steve mentioned a term called a "shadow account" (that exists, but may not be fully tangible). We also talked about how it is the actual company that is creating these phantom and/or shadow type liabilities. That kinda changes things... it is the company creating their own liability based off of a point system to encourage customer loyalty.

There seems to be two main part of the puzzle. How many points (ins and outs) and what is the value of those points? Lots of balance sheet transactions.

Simple to more complex transactions... simple gift cards or simple gift certificates, basic loyalty points, punch cards, in-store credits, coupons. As a fun side note, some of these transactions are subs of the balance sheet. Kinda like sub inventory but on the balance sheet side. Maybe we need to think about how the transaction takes place. Is there already cash on hand (paid in advance)? or is it just lowering the total owed, like a form of a discount? Who pays for what? What about coupons that a manufacture pays for or pays a part of?

On the main balance sheet items, we may need another switch to help us know if this is a main account and/or a sub account. We may also need to know if the asset, liability, and/or equity account is real or phantom (shadow). This is kinda fun, but we are seeing a fracture that is needed in order to record the balance sheet items. Everything is breaking into sub accounts.

Going back to discounts and special discounts... do we apply the discount to the cart/invoice on a whole or do we have to re-distribute that discount back through the system?

On a different note, we had a request from a client to be able to permission and/or fully turn off standalone discounts. Also, we are seeing that taxes make the discounts more complicated. We have options to do both in-line discounts and/or standalone discounts. Things get really fuzzy as you try to tax, especially with excise taxes and taxing things at the different levels (per item category, per customer type, per inventory type, etc.).

We had a great talk about "bad debt" payments. Don't worry about the words (verbage), think about the concept. That helps to satisfy the invoice (monies owed to us), the taxes are fully correct,  but it is then showed as an adjustment to revenue (rewards, coupons, loyalty points, etc.) on the income statement. Both coupons and loyalty points are similar. It is the internal company basically saying "I'm going to cover that part of the invoice". We claim that that invoice and/or ticket is x dollars and has y amounts of tax. We then cover the invoice by real monies and/or monies that mean something, but no real money changed hands. Look deeper in this. The main difference is the verbage between bad debt vs rewards or loyalty points.

Maybe we should add some new standard payment types such as: Rewards, Loyalty Points, Coupon, In-Store Credit, Gift Card/Gift Certificate, etc.

We are seeing the need for a good mix of user-maintained pieces, system-maintained pieces, and possibly some mixed-maintained pieces (user and system). We are seeing this in the watchers, feeders, standalone declarations, time templates, settings, etc. We need to let them play where they can and need to, but also make sure they have the tools and pieces to get the job done, even if we control the pieces behind the scenes.

Eric would like to check in on loyalty points around 11 am for a couple of hours. He texted me and said that he was unable to meet today due to some things that came up. So, in the meantime, Steve and I had a great discussion and made some good breakthroughs. Good stuff.

Spent some time working on an outline for the adilas user guide. I added about 30 bullet points in the meet the players section. That area had about 50 key topics. I have expanded it to just over 80 topics. I will be releasing them once they are a little bit tighter. Some of the things that were added were topics and subjects such as: API sockets, barcodes, QR codes, black box page technology, check writing, coupons & sales campaigns, email settings, gift cards, GPS & RFID tag tracking, marketing, media/content, merchant processing, mini conversions, sub inventory, third party solutions, etc. I'm excited to work with Shannon and get some verbage and documentation on those subjects.

Meeting with Hamilton with Full Cricle IM (interactive media). Hamilton was doing the small demo. Basically, he is going to be working with adilas and integrating his marketing product with adilas. Josh Sagert is going to be doing some work to help with that integration.

- new clients today (new customer/client start dates)

- check-ins today (customer/client queue)

- reminders (small messages to help people know different things - emails and text messages)

- coupons and broadcasts (sales and promotions)

- opt in/out to the loyalty points via a mobile number (quick text verification)

- internal inboxes

- scheduling texts and emails and reminders

- keywords (flagging and tagging different client records)

- auto watching for rewards earned and sending reminders and texts based on certain sales rules

- preferences and products that match certain clients and their profile

- Multi-numbers (virtual phone numbers) to handle more traffic and number of texts being sent

- API keys and storing client connection data

Good discussion between Josh and Hamilton about discounts, campaigns, and how to tie things together. They talked about goals and ways of figuring out the target marketing pieces using the technologies. They also talked about dashboards and showing what was sent out and what was returned (ROI). In Hamilton's words, he wants to reduce the sales friction. By combining things (adilas and Full Circle IM) it could and will be a great combo. All the pieces in the same database, that helps create a system and allows for major options.

They also were talking about integrating out to ecommerce and tracking click through's (general or generic interest) and also retention results (resulted in a full purchase). Tracking leads, campaigns, and effectiveness. They really want to focus on the end user's and how well and easy they can use it.

Talking about possible options of how to sign in - enter the number by the user or by the person doing the check in process. There are also options to text in and then use that as part of the check-in process. Basically, talking about checks and balances and making sure that they knew who was who.

Merging in code with Dustin and Steve.

Meeting with Hamilton from Full Circle at 10 am. They are looking for a January 1, launch date. Josh gave us a small update on where he is at. Customer dash board to show coupons, loyalty points, preferences, and maybe even a self check-in (add to queue). A possible manager's dashboard and tracking throughput and what campaigns are used and ratios for closing those campaigns and coupons. Josh is looking to build out some matrix to help show profit, costs, and other demographics (age, distance from store, etc.).

They are looking to add a flag at the corporation level as well as at the customer level on who is playing with Full Circle (who opted in). If both corp and customer levels match up, we can add additional functionality. As part of an advertising campaign, we may just grey out the fields and help prompt the users to sign-up to get the additional functionality.

Josh was talking about a virtual batting average per campaign - how many messages were sent out, what was the ROI and usage, etc. This will be more than just a response matrix, it will include prices, costs, profits, usage, etc. A mix of different stats and variables. Josh is also trying to tie-in things with his new discount rules and discount engine. This is a combo of both existing discounts in the system as well as mixing with outbound campaigns.

There have been some talks on making a standalone version to capture more market share. Basically, a special functional section for adilas users and another one that is just a standalone, that way it may be used in multiple arenas.

Timelines and vision - Josh is going to be breaking things into chunks to help with development and deployment. One of the keys that has been tied in, this past week, was the line item level of or for campaign tracking. That will be a huge key for reports going forward.

Question by Hamilton - what options do I have if I wanted to stand up my own box (server and databases)? He was talking about a go to market strategy. What are the entry points? Options (1, 2, 3, or 4)? Two scenarios, existing adilas users (what do they get) and new users, that don't use adilas (but maybe hit at what they could have)? Basically, Hamilton doesn't necessarily want two code bases but we may have to try to direct them to the main adilas system. Make it a double sale. Hamilton was talking about a mini version of the adilas platform (small and cute and limited) and then over time, allowing his outside users to eventually migrate over to adilas over time.

We talked about a mountain (show everything) vs a ice berg (limited view but more available)... Josh and Hamilton would like to flip the model and expose a smaller portion that looks awesome but has huge potential as they get deeper. It kinda comes down to the entry point (perception). This conversion is basically talking a mini version of the white label concept with a limited entry point. One of the key pieces is the domain name (it has to be pointed to a single server). We also talked about some dual entry points where we have both adilas domains and full circle domains pointed to the same box. Think of it like doors on a building... did they come in from the front, back, side, or up from the floor below? Piece of cake. It comes back to entry points, preferences, and traffic flow.

Hamilton was talking about "dangling" options in front of his clients... virtual up sales of what else if available. If you purchase adilas as a package, it may be harder to up sale the client - they kind of expect the full package. However, if they come in from the Full Circle side, they Full Circle, could sell and/or expose other pieces based on a more modular pick and choose type model. That could be really cool. Once again, showing the full mountain vs just an ice berg with more potential under the surface.

There were some light conversations between Steve and Hamilton about data storage and processing - who is hosting what pieces and where does the traffic come from? In a lot of ways, we don't really care where the clients come in the door as long as they come to play. We also talked briefly about Full Circle being able to expose small pieces as they become available (breaking the adilas mountain into modular pieces that are add-on's and virtual up sales).

As a side conversation, there was some talks about beefing up the reoccurring billing section (reoccurring invoices) and making it more modular and automated. Billing for our services is a big things for us internally. The easier the process becomes, the less time we have to spend chasing it. That leave more time for other tasks. The tuff part is the technical side, the fun part is the selling of the features - from Hamilton. Hamilton wants to use his existing adilas account and setup reoccurring billing from inside the system for his existing Full Circle invoices. We will have Josh and Shari O. help get Hamilton all setup with the reoccurring billing inside of adilas. Josh was stating some ideas about helping to automate things back and forth between the main adilas accounts and the Full Circle billing parts and pieces.

4.15 - Coupons & Sales Campaigns

-This gets into marketing and how you sell your products. We have some plans to build some engines that will allow you to start creating, automating, and monitoring these sales campaign activities. We are currently building in this area on tools that will allow you to manage and interact more with your marketing endeavors.

-You can currently track a sales campaign based on discounts that are given. You can also search and create reports based on that. It is not tied in directly to coupons at this point.  

-Eventually Adilas would like to be able to handle internal coupons directly through the system. It currently can track sales campaigns that are tied to discounts. There are some existing 3^rd party providers who do some sales campaigns and some coupons.

-Eventually this will also deal with marketing campaigns via text messaging and email blasting. 

Adilas is what we call a "business platform". What that means is there are tons of tools, functions, permissions, settings, and processes to help you run your business. This guide or manual will take you on a step by step journey in exploring and explaining some of the functions and tools that are available to you and your company. Not every tool or function will be used and that's ok. We want you to match the right tools with the right job. Some of the goals in providing this manual are helping you learn the system, apply the concepts in your own specific manner, help you track all your operational and accounting data, and help make you even more successful than you currently are! Let's get started!

Basic Outline - Feel Free to Jump to a Specific Section or Area
 
1 - Understanding The Basics
1.1 - What is adilas?
1.2 - How Does It Work?
1.3 - Enter Once - Use Many
1.4 - Database Basics
1.5 - Web Basics
1.6 - Standard Page Elements
1.7 - Navigation Tips & Tricks
1.8 - Vocabulary
1.9 - Adilas Theory

2 - Logins, Passwords & Permissions
2.1 - Main Website Features
2.2 - Username & Password
2.3 - Creating An Adilas Bookmark or Favorite
2.4 - User Permissions

3 - General System Settings
3.1 - Main Corporation Info & Settings
3.2 - Locations
3.3 - Sales Tax Settings
3.4 - Payroll Tax Settings
3.5 - Departments (tied to payroll)
3.6 - Assigning Employees to Departments
3.7 - Timecards (clock in/out)
3.8 - Master Time Templates (calendar & scheduling)
3.9 - Flex Grid Tie-Ins (custom data fields)

4 - Meet The Players
4.1 - General Overview
4.2 - Admin
4.3 - API Sockets & Communications (application programming interface - send & receive data remotely)
4.4 - A/P - Accounts Payable (vendor waiting room)
4.5 - A/R - Accounts Receivable (customer waiting room)
4.6 - Attributes (parent & child inventory flags and tags)
4.7 - Balance Sheet
4.8 - Banks
4.9 - Barcodes & QR Codes
4.10 - Black Box Page Technology (custom code options)
4.11 - Check Requests (sub type of the normal expense/receipts)
4.12 - Check Writing
4.13 - Chooser (custom interface chooser)
4.14 - Corporations (worlds)
4.15 - Coupons & Sales Campaigns
4.16 - Customers/Clients
4.17 - Customer Logs
4.18 - Customer Queue (check in/out)
4.19 - Data Imports & Exports
4.20 - Departments
4.21 - Deposits (monies coming in)
4.22 - Discounts & Discount Rules
4.23 - Display Options & Interface Choices
4.24 - eCommerce & Web Presence
4.25 - Elements of Time (calendar & scheduling)
4.26 - Email Settings
4.27 - Employee/Users
4.28 - Expense/Receipts (monies going out)
4.29 - Exports - MS Excel/CSV/PDF
4.30 - Flex Grid Tie-Ins
4.31 - Floorplan
4.32 - Gift Cards, Rewards, & Loyalty Points
4.33 - GPS & RFID Tag Tracking
4.34 - History & Reports
4.35 - Ideas & Sharing
4.36 - Interface Options, Dashboards & Choices
4.37 - Invoices
4.38 - Labels & Custom Paperwork
4.39 - Locations & Tax Settings
4.40 - Look & Feel (custom colors & navigation)
4.41 - Manufacturing (changing or modifying inventory)
4.42 - Marketing
4.43 - Media/Content/Files (physical file uploads and referencing)
4.44 - Merchant Processing - Credit Cards & Financial Solutions
4.45 - Mini Conversions (buying, selling, & tracking inventory - units of measure)
4.46 - My Cart Favorite Buttons
4.47 - My Stuff (personal settings & options)
4.48 - Objects & Data Over Time (theory & concepts)
4.49 - Orders
4.50 - P&L - Income Statement
4.51 - Parts/Items (general inventory pool)
4.52 - Payroll, Commissions, & Time Clocks
4.53 - Permissions
4.54 - Photos & Scans
4.55 - Purchase Orders (PO's)
4.56 - Quick Search
4.57 - Quotes
4.58 - Recipe/Builds
4.59 - Reimbursements (REI's)
4.60 - Reoccurring & Automated Options
4.61 - Sales & Promotions (see coupons & sales campaigns)
4.62 - Saved Reports (custom report favorites)
4.63 - Settings - Corp-Wide
4.64 - Settings - Group Level
4.65 - Settings - Page Level
4.66 - Settings - Personal
4.67 - Shopping Cart
4.68 - Special Line Items (system parts)
4.69 - Splits (payments made on account)
4.70 - Statements
4.71 - Stock/Units (serialized inventory)
4.72 - Sub Inventory (parent/child inventory)
4.73 - Support
4.74 - Texts, Emails, Reminders, & Communications
4.75 - Third Party Solutions
4.76 - Tiered Pricing & Pricing Engine
4.77 - Timecards (digital clock in/out)
4.78 - Tools & Maintenance

5 - Customers (in depth)
5.1 - Customer Settings (general)
5.2 - Customer Types
5.3 - Customer Logs
5.4 - Customer Additional Contacts
5.5 - Customers to Invoices & Quotes
5.6 - Customer To Elements of Time (scheduling)
5.7 - Customer Photos & Scans

6 - Inventory (in depth)
6.1 - General Inventory vs. Serialized Inventory
6.2 - Parts, Services, & General Inventories
6.3 - Vendor/Payees
6.4 - Part Categories
6.5 - Use PO's to Add Inventory
6.6 - Updating Inventory Counts
6.7 - Light Manufacturing
6.8 - Recipe/Builds
6.9 - Stock/Units (serialized inventory)
6.10 - Makes
6.11 - Models

7 - Sales (in depth)
7.1 - Shopping Cart
7.2 - Advanced Add To Cart
7.3 - My Cart Favorites & Smart Group Buttons
7.4 - Quotes
7.5 - Invoices
7.6 - Invoice Payments
7.7 - Transitional Invoices
7.8 - Reoccurring Invoices
7.9 - Discounts, Returns, Trades, & Refunds
7.10 - Statements
7.11 - Sales & Profit Reports
7.12 - Sales Tax Reports
7.13 - Merchant Processing (credit card payments)
7.14 - Transfer Invoices

8 - Deposits (monies coming in)
8.1 - Banks
8.2 - Deposits
8.3 - Deposit Types
8.4 - Deposits on Merchandise
8.5 - Depositing Invoice Payments
8.6 - Bank Transfers (deposit side)
8.7 - Special Deposits (balance sheet)

9 - Expenses (monies going out)
9.1 - Payables Homepage
9.2 - Expense/Receipts
9.3 - Expense Types
9.4 - Check Requests
9.5 - Reimbursements
9.6 - Splits or Payments On Account
9.7 - Pay Stubs (payroll and withholdings)
9.8 - Payroll Tax Liability
9.9 - Sales Tax Liability
9.10 - Special Payments - Credit Cards
9.11 - Bank Transfers (expense side)
9.12 - Special Expenses (balance sheet)
9.13 - Printing Checks
9.14 - Advanced Concepts & Usages

10 - Reports & Searching
10.1 - Report & Search Basics
10.2 - Adilas Quick Search
10.3 - Basic Application Type Searches
10.4 - Advanced Application Type Searches
10.5 - History Homepage
10.6 - Sales & Profit Reports
10.7 - P&L - Income Statement
10.8 - All Advanced Searches & Exports
10.9 - View Custom Code & Reports

11 - Financials & Accounting
11.1 - Bank Reconciliation
11.2 - P&L - Income Statement (logic and flow)
11.3 - Balance Sheet (logic and flow)
11.4 - User-Maintained Balance Sheet Items
11.5 - Adilas Theory on Accounting
11.6 - Roll Call Accounting Principles
11.7 - Old School Accounting vs. New School Accounting
11.8 - Vision for the Future

12 - Other Tools & Features
12.1 - Bridging Users Between Corporations
12.2 - Site Look & Feel (colors and logo)
12.3 - Corp-Wide Settings
12.4 - Training & Support
12.5 - Barcode & Label Generator
12.6 - Profit & Discount Calculator
12.7 - Finance Loan Calculator
12.8 - Financial Flow Calculator
12.9 - Global Parts Find & Replace
12.10 - Global Parts Mark-Up
12.11 - Global Stock/Unit Mark-Up
12.12 - Admin Time Clock
12.13 - Update Inventory Counts
12.14 - Managers Checkbook
12.15 - Wholesale - Cart Builder
12.16 - Cross-Corp Sales
12.17 - Custom Forms & Documents
12.18 - Custom Code & Reports
12.19 - Building Master Time Templates
12.20 - My Cart Favorite Buttons
12.21 - Smart Group Buttons (tiered pricing)
12.22 - Become an Adilas Rep

4.61 - Sales & Promotions (see coupons & sales campaigns)

-This deals with selling your inventory - whether it is live where the customer comes in, they order online, or they somehow respond to an ad.

-This is part of your marketing arm. Most of these transactions will take place on quotes, invoices, and online eCommerce.  

-A lot of the current tools deal with being able to set and control discounts and record which campaigns they are tied with.

-There are ways of doing discounts that are manual, in-line, automatic, pre-set buttons, etc. There are also reports to help you view and see these discounts that have been given.

-One of the big tools is something called the discount engine. This allows for discounts based on vendors, part categories, specific dates and times, you can exclude or include certain items, etc. After being setup these discounts occur automatically.

-Additional marketing and discount ideas are still in the works. 

Writing some new content with Shannon. We worked on topics like the chooser (selecting the interface(s) to use and set as your default homepage), coupons and sales campaigns, sales and promotions (getting a little bit into marketing stuff).

After Dustin and I got done debugging some comparisons between settings and sub inventory attributes, Wayne and Eric popped into the meeting. Wayne was just checking in and letting Steve know that more progress was being made in the AWS land stuff. Eric then had some questions about a 3rd party API socket project that he was working on for a company called Spring Big.

Basically, if a company turned on this 3rd party solution, it would share and pass both customer data and invoice data over to Spring Big. I'm not sure of all of the details, but it seems that they did some marketing and offered some coupons and/or campaign type offerings (don't quote me on that - just going by impression). Anyways, Eric and I were looking into new custom code and debugging some of the API calls and internal methods. He has a pretty deep wrapper function that have a number of other sub routines and sub API socket calls. We spent over an hour looking and testing things. We found our bug and fixed the issue. Towards the end of our session, he was checking API socket calls, pushing data, updating data, and finalizing transactions. Great progress.

At the end of the work session, Eric left and Steve and I started working on some of his projects. We spent about an hour looking into his (Steve's) and Dustin's cultivation code and the phases tab (changing plant phases section or sub section of the main cultivation homepage). We did some debugging, added some page and query filters, and commented out some older code. We tested both locally and push things up live. We have a client that is pushing the limits of what we can get the system to do without timing out. We also spent some time talking about ways of changing the existing page structure, carving the code and output into smaller pieces, and using more AJAX (asynchronous JavaScript and XML) type technologies for breaking pages into smaller chunks of data. Lots of potential there.

11.3 - Balance Sheet (logic and flow)

-The balance sheet is a financial document that is very commonly used for high level financials, I.e. banks loans, investors, taxes, etc. The balance sheet has 3 main categories that the details get divided into. They are assets, liability, and equity accounts. Sometimes people will use the acronym “ALE” to quickly remember those 3 categories.

-Assets are things that you own. Monies in the bank, inventory on hand, and other things that have a significant value that you need to track. It could also include monies owed to you for good and services previously invoices (accounts receivables). There are chapters and chapters of all the things that could possibly be assets, this is just a quick list for an idea.

-Liabilities are things that you still owe or may owe on. This could be things like loans, taxes, coupons, loyalty points, gift cards that you have already collected on, accounts payable, bills that are still due, etc. Once again this is just a short list to give a general idea.

-Equity or owner’s equity is more of earnings over time, investments, your net profit that comes from your P&L, distributions, all kinds of long term holding accounts. Equity usually derives some sort of value that has accumulated over time.

-The balance sheet is a "Snap Shot" in time and only applies to a single day. Basically, it is a roll call of who was where and what happened at that exact time (according to the system).

-Both the income statement (P&L or profit and loss statement) and the balance sheet usually end up being quite in-depth in real life and may contain multiple layers in order to tell the real story of what is going on or what has been done.

-The P&L is a time based report of buying and selling and basic operating expenses. By time based we mean that there is a date range associated with it. It could be a day, a week, a month, a quarter, a fiscal year, etc.

-The connection between the two is what is called the "Net Profit" or "Bottom Line". This value is first figured on the P&L and then passed to the equity portion of the balance sheet. The ending date range on the P&L is the balance sheet look-back date or balance sheet date.

-One of the hardest things for people to figure out is what goes on the income statement and what goes one the balance sheet. There are chapters and chapters that cover the in and outs of both reports. For basic purposes, the P&L is the day to day buying and selling of items and services. It also includes basic expenses that are required to run your business. The balance sheet deals more with who owes who, and how things get classified or grouped. Do we own it (or trying to own it), these are the assets. Do we owe for it (or trying to pay for it), these are the liabilities. The last piece of the puzzle is the equity or distribution of wealth (who are the players and what is their piece of the pie).

Bryan joined the GoToMeeting with Steve and I. We were talking about coupons and how that would work and what it would look like. Here is a link to some research on coupons. We were talking about standalone discounts, in-line discounts, percentages, dollars off, free products, buy on get one (bogo), etc.

Bryan and Steve were also talking about advancing the menu board options and helping to make it more and more available. Bryan built a menu board, years back for a client. We may need to revamp that and/or give it a face lift and then go from there. Steve really wants to make it, the menu boards, part of the product and free to all users. We did the same thing with the basic web presence and the paid version of ecommerce. We are trying to make all of these pieces just part of the whole product that we offer.

There were some talks about pushing the menu boards and ecommerce further and further and even helping those two pieces come together better. The more we can keep focusing on building out our product, it just helps the core to be better and more stable. We have to walk this interesting balance between custom work and core work. In a way, we need both. They feed off of each other.

Lots of talks about project management and getting seed monies in place before we jump on these projects.

Meeting with Jonathan to go over some progress. We haven't met in a few weeks due to holidays and what not. The meeting went well. Jonathan and I were on the whole meeting. Steve joined us in the middle for a part of it. Here are a few of the things that we did and covered:

- Review of the education mode - see the screenshots. The education mode allows a user to turn on/off additional helps, tips, help files, verbiage, videos, graphics, etc. The user can turn things on/off to keep the interface more clean and streamlined. If they need more help, it is available at the touch of a button. Side note, added this link to a small video on the education mode on 8/14/23.

- Review of the invoice interface with some fake data. Jonathan is working on showing mock-up data and how it may look and flow, as the user interacts with the system.

- Talking about style guides and standards - design systems - This is how we will end up standardizing the look and feel over multiple pages, components, reports, and features.

- Components and using consistent assets (visual and code resources). Both in the design and in the code - design/code once, use many.

- Talking about mobile development and more needs for mobile ready pages.

- We also talked about the placement of certain eye candy pieces such as graphs, charts, and other stats. Leaning towards the reports pages and/or section.

- We briefly talked about Jonathan's research on fracture and breaking up the system into smaller pieces. Being able to have the mountain of tools and options (features and benefits - current adilas system) but only showing what is needed (turned on/off and properly configured) and streamlined per industry and per company within that industry (making custom software easy). Basically, the ice-burg model. As we got into this, we ended up talking about the core product (the main adilas platform) and how we could allow for industry specific interfaces and settings to play over the top of the skeletal type model.

- The skeletal type model deals with the underlying systems... imagine a person with just a skeleton structure. You could then put normal clothes on that skeleton structure. Pretend this is core adilas (plain jane vanilla). Then you could dress that person with industry specific clothing to get all types of different outputs. Every industry has a different look and feel, verbiage, style, flow, etc. That is like putting on specific clothing on the skeletal system.

- Towards the end, Jonathan and I were talking about the shopping cart and how that part of the system really needs some loving. So many pieces converge on the shopping cart and point of sale interface (POS). It is pretty awesome. Here is a small help file on the shopping cart - click here. We talked about some of the known pieces that converge inside of the cart such as smart cart logic, customer loyalty points, tiered pricing structures, discounts and discount engine stuff, inventory tracking, sub inventory, mini conversions, labeling, coupons, payment solutions, sales and promotions, etc. Once it hits the cart, it gets put into the database and starts its life cycle. We talked about how the shopping cart and things that flow into it and out of it are kinda like the heart of the application.

We weren't quite finished with our other meeting, so Bryan had to wait for a bit. As we were wrapping up, Bryan and Steve talked and chatted about some project details and direction. Once I got back, we pushed up some code. Looked at some other code and talked about a coupon and promotion code project. The deeper we got, it, the project, got deeper and deeper with multiple unknowns. Lots of questions about settings, guesses, assumptions, needs, wants, and bell and whistles. We could see what the client wants but there are questions that come up. Do we do it core or custom? Do we allow for settings or just be bold and do the minimum? What about taxes? What about settings? What about financials and tracking things all the way through the processes? It got deep.

We looked at in-line discounts, standalone discounts, payment options, coupons, promotion codes, automation, cash values, and tons of other things. Some of the projects have teeth and need to be looked at from multiple angles. One of the biggest was taxes and how to satisfy the sales tax questions (charge for it, don't charge for it, back it out, try to match it up, etc.). Standalone discounts can get complicated due to taxes and trying to keep things straight. I ended up giving Bryan a bunch of questions to take back and talk with his client about and see what they wanted. As part of that, if it was going to be full custom, we weren't going to chip in on anything. If it was going to be more of a core and standard thing, we would be willing to chip in on the development planning and cost portion of the puzzle.

Towards the end, we had a good conversation, between Alan, Bryan, and myself about how our current model really encourages custom code development and it almost penalizes the developers for making things internal to the core. Especially if they do most of their work outside of the core anyways. They take a cut in pay (potentially - internal rates vs external rates), the projects get bigger (more requirements), and they then have to answer to one of us (internal adilas control persons). Kinda interesting. Anyways, as we go along, part of job will be figuring out how to help and handle custom code and scope creep and project creep. Bryan will be a good resource as he spends most of this time and efforts in the custom project world.

Bryan and Steve were on the morning meeting. They were talking about a project to allow promotion codes to be entered as part of ecommerce. We went over a bunch of different options. We talked about in-line discounts, standalone discounts, campaigns, payments, taxes, settings, and a bunch of other topics that revolved around the coupons and promotion codes. Adilas offered to pay for half of the development. See attached for some super quick notes.

Discussing AdilasWPShop (new e-comm solution) formally known as WooAdilas

MVP - minimal viable product/plan

- Competition and how we help get some of the pieces past the finish line

- Platforms and building on top of them - WordPress, WooCommerce, Adilas, etc.

- Online ordering platforms, showing inventory, full ecommerce, drop shipping, ordering and delivery orders

- In-store pick-up or delivery or shipping options

- Tons of talk about deliver options, scheduling, picking date/times, etc.

- Small talk about integrated systems vs trying to mix and blend tons of independent products and trying to marry them together. There is pain in some of those pieces.

- Plug-ins (plugins) and getting things all tied together

- You have backend apps, frontend apps, customer facing things, options, assets, etc. Lots of mixing and blending.

- Pricing options on parents vs subs (parent/child inventory and pricing tiers).

- Using adilas API sockets to populate WooCommerce stuff using custom plugins.

- Certain pieces are pre-built by other vendors. Other things would be nice. And yet other things are already done by adilas as pre-built or custom options. Where do you build? Where do you spend your time/money/resources.

- Molly needs a gram tracker, custom discounts (discount engine), and better integration options. Currently she has to manage multiple applications and have one do one thing and the other do something else. Sometimes both applications do the same thing and you either need to choose and/or pick one or the other (more integration).

- Versioning and who has the latest cookie and how do you distribute that?

- Multiple ways of dealing with tiered pricing inside of adilas. We need to help standardize things there. As we were talking, there are some know issues with some of the ways that we do it internally (smart group buttons, parent attributes, etc.)

- Shipping zones, different fees for different zip codes, etc. WooCommerce has a ton of different pieces.

- Updates, reports, and getting the needed information quickly. This deals with shipping, queues, sub-queues, reports, and even clear out to element of time or somehow track the shipping, delivery, and/or in-store pick-up. We need to link up the delivery aspects and the customer queue.

- Claiming quantity and on-line orders affecting inventory levels and availability - small talks about quotes, transitional invoices, and normal customer invoices.

- There were also talks about state compliance systems and how in-store pick-up vs delivery orders may need to be handled.

- Messaging and using emails, text, queue specific, or different stages (as things happen) messaging. Notifies  and reminders.

- Acknowledgement and approving payments. We may need a setting where they could fill in some verbiage, and toggle on/off settings to show/hide and require/not require those steps and pieces.

- Coupons, promotional codes, referrals, etc.

- People want something that is integrated, fast, flexible, powerful, and easy. They also want it to look awesome!

- Tying in custom messaging into the customer queue, sub queue, and ecommerce orders. The queues are a great start... we just need to tighten up a few pieces and make it go full circle.

- Being able to automatically add in a delivery fee as a line item on the invoice/quote from ecommerce.

- Talking about custom code, internal development, project mangement, consulting, and pushing things forward.

- Bringing as much as we can into the core.

- Trying to add a new layer of flexibility and professionalism to the projects that we are rolling out.

- We are trying to help the clients see more of what we are doing.

- Trying to get to a more proactive approach vs a defensive or reactive mode or approach.

- We are looking to gather in all of the good ideas and then roll out the projects accordingly.

- If we use adilas as the source, we could use the people and talents around us to get the best possible projects and features.

- Black box and fully custom code. That is still needed. Where possible we want bring things back into the core and use settings or whatever to help all ships rise with the tide.

- Cautions - between who is driving what projects and where are things headed. We want to make sure that we are all headed in the same direction.

- Bug fixes and helping in the tech support areas and what not.

- Sometimes we are so busy, we skip over some of the other good ideas and things that could really help.

- Constant changing - code changes, languages change, businesses change, expectations change, etc. We have to be able to keep rolling and changing as things happen or we see things trending towards different solutions and options.

- Building to settings and permissions vs hardcoded - make it data fed vs strict line by line or manual changes.

- One of the hallmarks of what we do is let our clients help direct us where we want to go by offering a customizable solution.

- Where do you see yourself? Once we learn things, we tend to have a big tick list of ideas or things that we want to build. Looking long-term, do we stay were we are at or do we keep moving. Means vs ends.

- Meeting with Bryan to dial in the phase 2 option for coupons and promotion codes. We want to get a full plan together for the phase 2 options.

- Talking about sanitizing the content that gets shown on the web and available to the general public. We talked about multiple elements of time, show/hide settings on the web, and using flex grid tie-ins.

Most of the morning meeting was spent today talking about balance sheet rules and regulations. New mandates have come out dealing with customer loyalty points and how things need to be tracked and shown. Steve and Eric were talking about options, next steps, and how we want to handle things. Some of their discussion was centered around the topic of off sheet balance sheet items (things that are not part of the normal balance sheet math or ALE - assets, liabilities, and equity). The off sheet or off balance sheet item would show up below the main math and basically be a reminder type item. Some of these things are hard to really put a finger on due to redemption rates, redemption follow through, and other phantom type issues. Coupons and other things are similar. You start getting into the phantom realm of accounting and perceived liability.

The morning meeting started out normally and then sort of morphed into a multi hour long meeting with no real stop or start between the different topics and sections. We started out and Sean was checking in and lightly going over some of the BioTrack API socket questions. We got into a discussion on promises made and client and user expectations and how deep we want to go into those areas. Some of our clients expect an easy button for every possible wish or desire. It just doesn't work like that. Yet those expectations are real and valid based on user requirements and user demands. That puts tons of pressure on us as a software system. There just is no physical way to make it do everything, for every person.

Wayne joined the meeting and the conversation moved over to slow queries, database indexes, record counts, volume of data, and all kinds of other topics. We spent some major time going over potential problems with our flexible "LIKE" searches on the parts homepage (flexible wildcard searches across multiple database fields and columns). We need the flexibility, and we have trained our people to rely on that, but because it is so open, it is causing issues when put under a huge data load (not thousands but millions or multiple millions of records). We can handle quite a bit with no problem. When you really overload it, it starts groaning and squeaking under intense pressure. Technically, that is called scale.

The amount of data that some of our clients are generating and recording is causing a volume or scale issue. We got into deep logic and how we could speed things up if we were able to use indexes, exact searches, and get rid of huge list look-ups (using the SQL IN clause) or super flexible text searches using like commands (SQL LIKE clauses with wildcards). Basically, when doing some of these functions, the databases skip the indexes and end up looping over millions and millions of records. We spent some time talking about a number of possible solutions.

We had a break where Wayne had to go pick up his kid from school. In the meantime, John and I were talking about some of his projects. He was showing me a bunch of stuff that he has on a Jira board for the discount engine. I was kinda getting overwhelmed and depressed. So much stuff to do and manage. Sometimes it feels like it is all over the place and it never ends.

Wayne got back and we flipped back over to database queries possible options to help speed things up and handle a huge scale or a huge load of data. We talked about a combo type approach where we have to include tweaks to the database, code changes, UI and UX (user interface and user experience) changes, and other backend management changes. It may end up being a combo type package or approach to fix some of these problems.

That topic and discussion lead us to talk about prior or earlier decisions that were made years ago. We talked about why certain things were decided upon and implemented. It is very interesting and the story keeps rolling out in front of us. What we have now is a combination of history, situations, decisions, and even future wants and needs. It all mixes together and makes a complex solution. Some of the why and what we did is super important.

Having said that, things keep changing and morphing. We talked about building things for a non-static environment. Dealing with scale (up or down). That lead us to possible daily or real time mini aggregates on quantities and other key points and factors. Basically, ways of summarizing data and getting to more of a business intelligence type level - quick counts, sums, totals, averages, mins, maxes, etc.

Talking about the aggregation processes lead to talks about database triggers, update routines, scheduling, clean-ups, automation, manual checks and overrides, and the list goes on. Along the way, we kept talking about how important the inventory pipeline and tracking the ins and outs is so critical to these values, stats, and numbers. Steve joined us and we got into update functions, methods, table row locking, more manual updates, and reconciliation options to make sure all is well. You basically need the transactions (what happens and when - this is the details or the historical record). You also need the sums or totals (these are the running or current aggregates). These two pieces, transactions and aggregates play different roles.

As part of our discussion, we were looking at one-to-many database table and column relationships and how things are handled currently. It gets deep quickly. We then started talking about breaking shared tables into corp-specific tables and building smaller corp-specific aggregation type tables. This lead us to a small discussion on sizes of tables and when ones are already broken down into corp-specific tables and which ones may be up for review.

On the mini aggregate tables (quick sums, counts, and totals) we could go different ways. Do we want a historical record of the aggregates or do we just want to keep current (now) sums, counts, and totals? If you add historical, you start adding dates and get new records every day (assuming things are changing) or if you skip the dates, then there are less records, things may be quicker for the current but could take longer if going back in time. Maybe both... one to hold the historical aggregates over time and one to hold the quick and dirty (real-time current look or roll call report).

The deeper we got, the more that settings and database options came into play. We have a future project called fracture in the planning. We need to be able to have and use settings on what our users and corporations (worlds) want to see and use. We have tons of data and tons of records. Okay, great, what do you, as a user or end user, want to see, show, display, sort, etc.? How does that need to be organized? It goes deep and gets into advanced settings, display options, and being able to save layout and configuration options per person, per page, per corporation. That all needs to be included in the fracture stuff, along with the other transactional and mini aggregate database options listed on this page.

Once you know where you want to go... You can get there (hopefully). If you plan on being the only one to get there, the trail doesn't have to be very good. If you plan on repeating the journey, the trail needs to be even better. If you want a bunch of people and/or companies to complete the journey, you will need a road, not a trail. All part of the process.

Going back to tables, we talked about two big corp-specific tables in the system that will need a buddy mini aggregate table (or more). The big transactional tables are the po/invoice line items and the time sub inventory tables. Those two tables (that are already corp-specific) will need helper tables to keep track of both transactional aggregates per date (semi historical summaries) and also current non-historical mini aggregates for the quick and current view (no dates). Another way of putting this is making location specific pre math calculations vs having to go and re-sum things up or count things based on complex look-ups. You virtually do the known math per item, per package, and per location before it is needed. Then those numbers and values are quickly ready and available as mini aggregates. If you need more details or the blow by blow, you just go back to the transactional tables or records (different tables).

Some of our current pain is in the sales and POS (point of sale) systems such as carts and inventory tracking. We can do it, but if it gets into hundreds of thousands or millions upon millions of records, you run into the scale factor and issues.

Just for our notes, a couple key pieces are corporations and locations. If everybody just had a single location, some of this would be really easy. If you have more than one location, the solution needs to scale and keep track of mini aggregates based off of corporation and locations. That is a huge key that often gets overlooked. Plan for multiple (unlimited) locations. Here are some possible columns that may be needed for some of these mini aggregate tables for mini aggregate quantities - auto id, corp id, store id, part id, sub reference id (sub id), part count, and maybe a date if doing historical.

Switching subjects again, we need to charge more to clients for harder tasks and functions. I had a friend that was talking about software. He said, you tend to get two different types. You get cheap software or custom software. Hardly ever do you get cheap custom software. Custom does cost time and money. That is the way it is.

After Wayne left, Steve and I stayed on for a bit to go over some other things. We talked about gift cards, coupons, and other upcoming projects. I showed him a PO rounding demo and what I have done so far. The next question was... how deep are we going to dive per subject? Lots of options.

Cory and I going over a list of questions. About halfway through, Steve and Chuck joined us. I think that they were going to meet and work on some look and feel, but Cory and I were on the meeting. Anyways, the question got brought up about doing down payments on stock/units and how to book that and keep everything straight. The real answer is using transitional invoices. Having said that, we went round and round talking about possible options. Towards the end, Chuck was saying that when we redo our fracture stuff, we may need to make it part of the system that a prepaid invoice, deposit on merchandise, in-store credit, and other things be put in place and education and training made available.

For the record, here is how you would do it right now... using a transitional invoice.

1. Stock in the item, even if you don't have it in stock. If it is in stock, use that item. Anything that is unknown, just make a note of that. For example: a serial number or VIN number - maybe use the customer's phone number or email address.
2. Go to the stock/unit and go through the invoice/sale process. Make sure and set it to a transitional invoice (that wording is dynamic - layaway, prepaid, etc.).
3. Do the sale for the full amount and then take the amount that is either pre-paid or deposited. That will start the journey of the stock/unit and the payments received. All of these transactions will auto flow over to the balance sheet (already built-in) if using a transitional invoice.
4. Keep the invoice in the transitional state until it comes in, gets delivered, or whatever. If needed, additional payments (deposits on merchandise) may be made along the journey.
5. When ready, flip the transition invoice over to a real customer invoice and finish out the rest of the info. Once flipped, it will show up for sales taxes, on the P&L, accounts receivable (if money is still owed), and will count against inventory values. Prior to that, the whole thing is held on the balance sheet as the work in progress, pre-paid invoice, layaway, deposit on merchandise, etc. (dynamic naming).

Anyways, the takeaway is for fracture, we really want to have a way to show our people how to do certain tasks (searchable education mode). We also want to have some of the special account stuff like in-store credit, vendor credits, gift certificates, coupons, punch cards, etc. all done and part of the system. Those features may be built-in prior but need to be there. As a note, a lot of those will be sub sections of what we call special accounts, just like the current loyalty points stuff.

Meeting with Steve and Cory to go over projects. We talked about a couple of projects for Eric. We talked about gift cards, other special account projects (in-store credit, vendor credits, punch cards, coupons, and gift certificates or gift cards). Another one is the mini aggregate project to handle inventory quantities per location. The other possible project for Eric is getting back to the enterprise item catalog project. All of those have value and would be great add-on's.

The next major subject was projects that Alan is either working on and could work on. He is one of our top developers and is in demand, because he can do so many things. One of the projects that Cory really wants him to work on is the transition invoices out in ecommerce land. They already exits out there, they just need a little bit of loving. He could also help Steve out with some BioTrack production stuff.

Lots of talk about other developers and what they are working on. It is a challenge to coordinate projects and developers. Lots of moving pieces. We also talked briefly about some projects for Bryan. We are still trying to help our clients transition from billing in the old independent way to dealing with Adilas as a team or an entity.

Another subject that came up was the number of hours spent in a training and tech support with our clients. It takes a lot of time and effort. One of the benefits is that we learn a lot along the way. The more we help our clients, the more we learn, and can adapt the tools and features that we have to get the desired outcome. Along those lines, sometimes we (internally) need to be reminded of certain processes and tools that exist that we may not remember or are new to us. For example, all of Steve's new backorder stuff that he developed and managing quotes, orders, PO's, and backorders.

Cory was kinda putting her virtual foot down on certain projects. We are trying to retain our clients but sometimes they get out of line. We talked about preventative maintenance type stuff with our existing clients and helping them along the way. We, as a company, are offering more and more internal service offerings. We used to sub it all out to outside independent sub-contractors. We are trying to make those same offerings, but do it all internally now and helping out in new ways. It makes for a better product and better retention.

Talking with Sean about making a tighter game plan for credit card payments and which merchant account types we will allow and support. Currently, we are super open which is nice, but it also introduces too many variables. We have done integrations with a number of different companies and vendors, but not all. It gets really tricky when new hardware is introduced and chip or EMV requirements are needed. Anyways, we'll work on refining our options and how we approach custom solutions.

Eric joined the meeting and had a few questions. He let me know that there was a problem with the Herbo server (most likely a test branch of code). We also chatted briefly about some other MVP special account options that we would like to get to. We talked about in-store credit, round two on gift cards, coupons, and promotion codes. We also mentioned that we may need to do a full review of what we call our standard merchant processing setup and credit card payment options.

Emails, reviewing some videos on a time formatting bug/complaint on employee timecards. We used to leave it very open and allowed users to enter times as they see fit (for example: 5 pm, 5:30 pm, or 5:30:00 pm). The new time pickers require a certain format and some of our clients have been complaining about the requirements. We had time-pickers for hours and minutes, as well as one that required hours, minutes, and seconds. Basically, they want it back open where they can just quickly slam in a time vs having to comply with specific formats.

Sean, Shari O., Michael, John, and I were on the morning meeting. We all checked in and said what we were working on. After that, we all either left or went on mute and worked in the background. Shari O. had to take a tech support call and Sean was waiting to chat with her once she was finished. John had some flex grid tie-in questions. I was doing some research on MVP's and past data that we had recorded for what we wanted in some of our MVP (minimal viable product) stuff.

Here is a short MVP list that I'm thinking about - for the record, we already have some of this, we just need to refine it and make it watertight:

- Special accounts and in-store credit - We already have loyalty points, and round 1 for gift cards. Eventually, we would like to do in-store credit, vendor credits, punch cards, and other ones. The next biggest need is for the in-store credit stuff (in my opinion).

- Round 2 on gift cards - We've been gathering ideas and wants and needs

- Coupons and promotion codes - clear out and through ecommerce and internal shopping carts

- Take Calvin's adilas label builder to the next level - we've already done some planning and prep work there

- Standardize the merchant processing options - We have like 9 different integrations. Here's my next goal, pick one, make sure it flows from start to finish and is super simple. I want to do normal sales, pre-auths, captures, tips, refunds, voids, and reoccurring payments, etc. We have to be able to do manual key (like ecommerce mode), swipe, chip/EMV, and tap to pay hardware integrations. I want to do and offer all of the merchant processing functions. I was thinking that we could do a big push and try to get all hooked up with Datacap and then let them handle all of the different hardware pieces and different merchant gateways. That's my thoughts right now.

- Revamp the internal shopping cart, my cart favorite buttons, and general look and feel. I would love to head towards the fracture project - we have a bunch of R&D on where we want to go with that.

There are tons of other things on my list, but that is my quick MVP list for right now.

Steve wanted me to meet with a guy by the name of Pete - he's a techy guy and a developer.

Met with Pete over Google Meet. He was showing me what he has done and what not. He was interested in adilas and the variety of what we are in and doing (not just a single business vertical). He gave me a good rundown on what he does, where he has worked, and some lessons learned. I really enjoyed our visit. Here are some of my notes - kinda random:

- Different ways of networking - one thing leading to the next, to the next, to the next. Some of the processes and needs are the same, but the people that make those connections are what really changes.

- Pete likes to get into a smaller organization and then really accelerate certain parts or pieces of that organization.

- He has done a lot of managing of teams and different leadership positions at different companies.

- He is interested in supply chain management and all of the pieces that touch that sector.

- On average, he seems like he likes to be with a company for 1.5 to 2 years. That's not bad, that just seems to be his turn rate.

- When possible, he likes to virtually steer the ship. He'll jump in and do SOP's, technology, decisions, and training. He's ok with bouncing around.

- If needed, it's ok to pull back and go into "maintenance mode".

- Introspection and looking inside yourself. Where does he want to end up and/or do? Great questions. It is management, software, hardware, training, or a mix?

- We talked a lot about professional services - Basically business needs and byproducts. This could be things like CPA's, Attornies, Designers, Developers, etc. Kinda like what we want to do for the adilas marketplace.

- We got into some code, backend, frontend solutions. We talked about nocode (no code) and lowcode (low code) solutions. He showed me a little bit of Bubble (bubble.io) and what they were doing. Just for fun, he said that he got a team to roll out a quick demo in about two weeks. It was just a demo, but a quick thing to show to investors and key players.

- Using API sockets and endpoints to do all of the main data play and heavy lifting.

- It's ok to strategically take a pause or a break.

- We talked about marketing and matching products and potential clients (users or customers). The difference between throwing a wide net or a more focused net (fishing analogy). Ways of creating your own mini marketplace.

- Pete showed me a cool, 20 question, walkthrough, to get a new service provider all setup with a professional service offering. Nice looking sequence and small decision tree based on the users input. It was setup like a little chat bot of sorts. Basically, a small Q&A with simple decisions, lists, choices, and in the end, it helped get you all setup. Pretty cool.

- Light talks about Geo fencing, Google places API, and other small wizard type interfaces. When you put it all together, you end up with a bigger wired-up mash-up with different pieces, libraries, and such. It looked pretty good.

- He was using some special discounts and coupons to help with billing stuff.

- Lots of byproducts - not the main products, but things or needs that get generated from the main product that become new products and services. Lots of byproducts.

- Everything was responsive web layout ready. He showed me lots of screens with simulation of what it would look like on different size screens. That was kind of cool.

- Pete showed me some of his rating systems and even pulling ratings from other outside services to create an overall rating for the professionals and their services.

- We went over some role based and team based permissions.

- Airtable - basically, a sharable spreadsheet through API sockets - simple database of sorts

- We went over some options for dynamic page content, drag and drop organization, and how that plays into the mix. He had a nice looking interface. This led us into more Bubble.io stuff. Imagine a map of clickable elements with light logic, nav, and flow built in. That is what it looked like.

- We got into some discussions on UI/UX pieces (user interface and user experience stuff). Lots of different libraries.

- Talking about change. Pete said a couple of times - I'm an agent of change management, not just change. The change management piece was important and where he likes to be.

- We talked about a few different analogies and ways to look at both companies and what they offer. An analogy of a triangle, you could look at the top, the middle, or the base (bottom). You could also look straight on (like a path or hallway) or you could look at the same thing from the side (see the beginning from the end or from the outside). Fun conversation about angles and how to look at things and analyze what you are looking at.

- We talked about the user feedback loop, what they want, what they are willing to pay for, what they expect, what they need, and even the phycology behind some of that (those choices or decisions). This conversation lead into a light talk about interactive education, helping people who are getting stuck, and figuring out why they are either getting stuck, frustrated, or losing interest. Lots of interesting ideas.

- Letting customers drive the next steps - by their feedback.

- Changing in the proper way and at the proper time - proper change management.

Good discusion. After the meeting, I got a prompt from Otter.ai to see the transcript (voice to text) or transcription. I popped in and read a few things. I didn't read it all, but that was interesting. I had never played with that before. Great meeting. We ended up and I told Pete that I would talk with Steve and we'll go from there. Good stuff.

Great two-day conference. Took tons and tons of notes. See attached.

So, Sharik Peck, owner and founder of Rezzimax allowed me to come watch he and his team put the conference on. I brought my mother, who loves that kind of learning and content. Those people (the participants) were her kind of people. That was fun to watch all of them interact. I ended up loving it as well. I learned a ton, tried out the products, and even contributed a bit to the conference (questions and comments). My main goal was watching what they were doing, how they interacted with the conference participants, and observe little tips and tricks that I could pick up and use when I do some training events and conferences. Good stuff!

Here are some of my notes. Once again, this was more of me observing and picking out tiny tidbits of information vs taking notes on what they were really doing and talking about. I hope that makes sense.

- The Dream - telling a small story. Dreaming and then trying to put the dream into reality. Just the motion of following a dream led to a whole other set of ideas, situations, experiments, and achievements. Basically, the whole journey that ensued and is still going. All from following or attempting to follow a dream.

- One of the main goals was sharing knowledge and getting manuals and resources out to their users. One of their biggest problems was - How can we replicate "Sharik" (fill in the name of whomever is a major key player or awesome influencer)? Sometimes, to start with, lots of the main knowledge and/or know how resides in a few key players. We have to get that information out, virtually duplicate that person, and let others help run with it.

- They spent some time, right at the first, trying to get the conference attendees to help pass the word along. They did a whole section on the affiliate program that they are using. This could be done through referral links, commission structures, affiliate program website, training, certification, and specific tracking of coupons.

- They used some guest speakers to help spread the word. They also have done some research, written articles, and gotten things published, in order to get the word out. Some of that takes times and networking. Along with that, it is always good to bounce ideas off others in your field. Collaboration and idea farming.

- "Form follows function" - they kept saying that

- Small pieces of world building - I saw interconnected system, relationships, finding and fixing problems, addressing pain and disfunction, and seeing how those interrelated pieces worked together to almost create a world. This is an older entry dealing with some world building concepts.

- The smallest change in a system can play through and create new problems and new solutions. Trying to get a good balance - along the way.

- Straightening out disharmonies

- Helping people help themselves - teaching them coping and learning skills

- Deprogramming - things that run in natural or normal habits that may be unwanted or causing problems and issues. Deprogramming, in a way, means undoing or rerouting paths and avenues.

- Lots of experimenting and being okay with that - nothing happens by magic.

- Practice and hands on training - they were giving additional instruction during the practice session. The instructors were miced (had microphones attached to them) as they were walking around and helping others with the practice session. Everybody was able to gain from the instruction and feedback given to individuals.

- Durning the presentation, they would bounce out to a well formatted video to help encourage the participants to go to their YouTube channel for more information.

- Talking about alignment and getting things in-tune or aligned - This was tied into a foundation and going back to the basics. This included basic knowledge and basic techniques. The alignment seemed to be a key factor.

- Focus your mind on what you are grateful for... One of the best sources of change.

- Over the years, Sharik has gone onsite and helped out many people - where they are (to their place, their home, or their business). That seemed to be a reoccurring theme.

- Look where you want to go - If you do, you'll have a better change of getting there.

- Victim or Advocate - Question - I make things happen or things happen to me?

- Thinking about thinking - an active approach

- They used their tagline over and over again. It was - "Tune out pain and tune into life!"

- He, Sharik, tries to surround himself with people who have lots of skills, knowledge, and talents.

- They had products and samples that they gave out and let people use, try, and experiment with.

- Their packaging was very professional looking. Nice glossy info sheets, nice visuals, everything looked very professional.

- Matching frequencies - we don't want to stay out of sync very long. We tend to want to match what we are hearing and/or feeling.

- Great interactions between the instructors and the conference attendees.

- Consistency and creating good habits.

- Don't be afraid to try something new. Learning over time and recognizing patterns.

- There were a few different times that Sharik would talk about the process of inventing - He would wake up, write things down, react to things as they keep coming (from any source), and keep moving forward based on where he was and where he wanted to go. I loved the stories.

- Quite a few user stories (from the participants) and testimonials. You could tell that everybody liked the products and the procedures (protocols).

- Lots and lots of great hands-on practice sessions. He even had a number of people (assistants) who could help him out, there at the conference.

- They kept referring back to their website for videos, information, manuals, products, etc.

- They had a new product that got introduced at the conference. You could tell that a lot of time, energy, money, planning, and excitement were part of the new product release. They introduced their mini's or mini version of their calibrated vibration tuner. It was pretty cool! Everyone there got one to play with and experiment with it. Lots of ideas and scenarios started to play out. The participants were expressing ideas and possible solutions, almost imediately. That was really fun to watch.

- Feedback was requested and very welcome.

- Sharik has been doing some public speaking at different events for quite some time. Great way to get the message out there.

- Loved the light flexibility in their agenda. They switched things up on the training as needed. If you were a person who fully expected perfect clockwork, you would have been disappointed. If you were ok with some flexibility, they you were spot on. They still kept it moving but there were definitely some custom alterations on the fly. I really enjoyed it.

- Recipes - basic steps to get a certain outcome or output. They called them "rezzipes" for Rezzimax but they were virtually recipes - simple steps to get certain results.

- Harvesting ideas from others - giving credit where due.

- Lots of personal stories, details, knowledge, hints, tips, and experiences. That made it fun.

- They kept showing success stories - it almost made you want to be one of the success stories. Almost a level of marketing without actually marketing. That was cool!

- They ended the first day pretty casually and soft - they didn't teach clear to the end. Sort of a soft ending on day one. Light interactions, hands-on experimenting, networking, etc. Quite a few people hung out and chatted, asked questions, and had some great interactions.

-------------

Day 2

- Small suggestion from my mom - A bag with your logo on it. We got lots of goodies and new toys. My mom recommended that a bag would be nice. It would be reusable, helpful, and people could see your logo and name as the people carry their stuff.

- Sharik started the day off by asking for feedback.

- He had a few people that could only be there part of the day. He was willing to change his agenda to help accommodate some of the people who needed to leave early. Those people wanted to cover a specific topic. That showed great flexibility and a personal touch.

- He, Sharik, made some fun and great introductions to those who were helping him out. His fun introduction added credibility to the presenters and/or helpers. Whatever their role was.

- They showed a new mobile app to go along with their new minis (calibrated vibration tuners). Super small demo. Talking about upcoming changes. The users wanted to be able to read/write new hardware names (be able to name the devices - in English vs multi-digit serial numbers). They wanted ways to name the device, assign them to a room, or attach a type to the device. Basically, ways to flag and tag things so that they could organize their environments. It was all about organizing their flow.

- They (the users) wanted to be able to turn things on and off remotely. Using technology to help their clients and patients sleep better.

- They also wanted full control to program multi devices with plans, modes, times, timers, and custom options.

- The end users wanted to know timelines, they were really excited to get using it.

- Currently, they are using Bluetooth to connect. They want to be able to do all functions, remotely, including ways to control all of the micro functions, timers, wake-up, go to sleep, modes, cycles, etc. Ideally, they would love it if they could program something remotely and then the device could go pick up that information from a central server or central location. Basically, a web app of sorts. Going beyond Bluetooth.

- Users wanted to know about updates, notifications, communications, and how to provide feedback.

- Not only feedback but also recommendations and feature requests.

- Sharik was asked a question and jumped back into a small history of where they came from. The electric toothbrush story. That was part of the start of the whole dream. In his dream, he was told, "Vibration will heal the human nervous system. Go figure it out!". Through experimentation, they went through over 800+ electric toothbrushes. This is a side note, but I've known Sharik for years. At one point, he was experimenting with handheld sanders (from a hardware store). The toothbrushes were too little and small and the handheld sanders were too big or too powerful. They ended up with their own tuners that allow for calibrated vibration (speed, intensity, and frequencies) and even waves and patterns. All part of the invention process. Kinda fun.

- It was fun to see journeys come full circle

- Back to the minis and the new app - the users wanted to know protocols - who to talk to, what to send in, how to communicate, etc.

- Sharik invited the developer to show the new app. All of this feedback was being thrown at him while he was presenting. They were recording it and others were taking notes. There was no way for the developer to actually take all of the notes for the requests, ideas, and suggestions as he was presenting. It really helped to have other helping to either record or jot down the notes.

- Just for fun - Sharik said about the programmer - "A programmer on a mission!"

- Note about the media guys who were helping - they had two guys recording the conference. One was the primary tech guy. The other was more promotional and marketing. They were capturing testimonials along the way. They miced (used microphones) all of the speakers. If someone else made a comment, they tried to resay it or recap over the microphone. Sharik was also recommending that the attendees get with the media guys to get their stories and/or testimonials. Pretty cool setup.

- Jumping back into the conference and some of the topics. Lots of time spent on "Trauma" - aka problems, issues, and pain. Without pain or needs, no solution is needed. Once trouble or a problem exists, a solution or answer is needed or wanted.

- Pornography, drugs, alcohol, PTSD, life events, etc. All forms of trauma or issues. Some of these things are taken in by the eyes, ears, hands, mouth, touch, feel, or other ways. Eventually, they get into us and/or affect us in some way or another.

- Teaching the law of opposites - joy and misery, happiness and sadness, inhale and exhale, push and pull, etc. Being ok with being uncomfortable. Pairing these opposites and finding patterns. Back to trauma - front door and back door approach. There is always a way in, look around and be creative.

- Let it go! Exposing yourself and being vulnerable. "IT" will come later. It meaning, what you are looking for. Sometimes you just need a catalyst for change. Replacing negative with positive (thought).

- Standing next to the event, not in it (trauma and events). Can you remove yourself from it and virtually watch it play out, what can you learn, do, observe, as you look at it from a different angle. If you only look at things from a single vantage point, you may be limited as to what options are available.

- Going almost empty and then rebuilding and replenishing.

- Trauma has attachments - it could be other traumas or connections with other events or situations. Usually, it is not just a single thing... there are relationships and multiple interconnected pieces.

- Forgiveness and understanding. Forgiveness doesn't make it right. It does have power to help you. At some point, you may need to ask, how is this all done? Where does that lead you?

- Having a safe place to recover and seek healing.

- The ability to connect to the music within you.

- Saying prayers - for self and for others - looking beyond yourself.

- Sharik was sharing his story and tons and tons of other experiences. It makes it real.

- Triggers

- Learning lessons and then passing on those lessons learned. Experiences just happen!

- At one point, they went over a number of FAQ's (frequently asked questions). They had a preset list and it made it easy to just jump through them and/or skip around as needed.

- Different people do things in different ways - that's ok and even encouraged...

- Great discussions and awesome feedback and ideas from the participants. There was enough flexibility in the presentation to allow for that.

- Inspiration and being open to new ideas. Sometimes it takes time to come to an understanding.

- Freely give, freely share - keep it open.

- Each participant comes from a completely different place. Acknowledging the pioneers in the room. Go explore. Learn from your experiences. If you are experimenting, try it on yourself first - controlled experimenting. Fun discussion.

- Mixing and combining techniques and skills.

- Finding out what nature does and either using it (nature or natural ways) or trying to simulate it. Helping to integrate those type of techniques and processes.

- There are tons of other things that can be added into the mix. Take what we have and what we offer and then add to it and even enhance it. Build off of a stable base.

- Back to a topic in the main presentation - deep questions and sequences - Am I safe? Once you feel safe or relatively safe, you can open up and/or work from there. Interesting.

- Making time to care for ourselves.

- Stick to the basics - back to recipes.

- This is from my mom - She can hear the main presenters but can't hear anybody else (other people who asked questions or chimed in). That bothered her a bit. She knew that I was taking notes on my observations and leaned over and asked me to write that down. That can be hard to fix and tends to fall on the presenter to restate the questions and comments. Just noting that was requested (restate what is being said by others).

- Pathways - things that are used over and over. What works for you? Use that and then build and go from there. Along those same lines - think about strategies and figuring out how to duplicate or predict certain outcomes and behaviors.

- Light humor lubes the discussion and/or topics being taught or discussed.

- Gathering information - connecting the dots - even over time. Be patient! Along the way, seek for opportunities and find alternate paths or pathways.

- Sove a problem, then move on to the next... the deeper you look, it will become a map of the environment. That's pretty cool!

- Going back to basics - the goal is the big picture.

- Repetitive processes - that's how we learn.

- More videos and referring the participants to subscribe to the YouTube channels (plural).

- Lots of techniques, tips, and tricks.

- They were talking about self-healing... at times more advanced help is needed - meaning surgery or other advanced help. That is okay! Start with self-healing and go from there. There is a point that we need other people and their skills and knowledge.

- Talking about pain - if you take it all away, sometimes you do something stupid - keep it real - without any pain, you can push things too hard. Pain can be a great teacher. Knowing your limits.

- In their videos... there was a lot of consistency - well done. Some of them felt repetitive but yet different.

- Sharik's wife kept helping them, whoever was presenting, with reminders and helping them if they forgot something.

- Giving service - helping and doing good

- Public speaking and facing fears

- They were talking about sharing energy and sharing energies (plural)

- The feet are great messengers to the brain

- Simple steps - set timing - set steps - make it repeatable

- Watching friendships and relationships being made from the conference attendees - fun to watch

- People cheerleading each other and supporting each other

- Good laughter and fun times

- Emotions tied to injury - making new paths to the brain

- Putting all of the pieces together - creating a system and using other systems that already exist

- This was big for me... what have we found... letting people know... passing on that knowledge

- Just noticing - some of the attendees were standing, going up, getting closer, taking pictures of slides, videoing, recording, and taking notes - internal thinking

- People want to learn - some great questions and follow-ups

- Telling the brain "the map"

- Being developed on the fly... people testing things on the fly. They were putting ideas into play on the fly (meaning the attendees and the presenters). This was especially true as they were playing with tuners and techniques.

- Alignments - keep coming back to simple alignment concepts

- Improvements and seeking improvements

- Major participation - he called someone up to the front, let them do it, and he was commenting and lightly direction what was being done. Very hands on.

- Watching for reactions - seeing through their behavior

- Things working together

- Talking about sensitivity and visiting or building up those areas over time.

- Following protocols - set steps to follow to get certain results

- Translating ideas and concepts to different applications

- Personal stories and tying them into parts of the bigger or main story

- Helping to solve problems - daily

- Constant message of gratitude - being grateful

- Good resources - that helps to bring back that knowledge quickly

- Sensitive individuals - start where or wherever they are at - helping them quickly get back to recovery

- If it takes time - take that time

- When they are ready... there is always a timing that goes along with healing

- Question - Are you trying to solve things or just make things better or easier? There is a difference.

- Thanking others

- Explaining why we do the same things over and over again - finding those patterns and reasons

- For me, I loved the stories and how much Sharik and others had helped others, all around the world, making a difference.

- If you do some pain... Make sure you put a smile on their face before they leave.

- Some of the participants want a way to share and pass on advanced tips and techniques. They talked about a Facebook group(s) and making them public or private, depending.

- Wanting to stay connected

- Mindfulness and being focused - going there on purpose

- Self regulating

- A tool to help - not the end all solution

- Primitive reflexes - a return to a pattern - there are both good and bad primitive reflexes - ways to help overcome ones that are unwanted

- Light it up (an area of the body or a pathway to the brain) - the brain loves information - food for the brain

- Asking others to help us get the word out - work of mouth

- Technique - cross grain or crossing - going across the midline and then back again.

- Transforming and transferring energy

- Test it as you treat

- Work on the weak side

- Working through barriers

- Accelerating processes

- Isn't that cool (both ! and ?) - statement and question

- Combos

- Tests

- X is tied to Y, is tied into Z, is tied into... Everything is interconnected.

- Reviewing, even at the risk of sounding like a broken record.

- Spent some time going through scenarios (different changes or alterations based on the circumstances)

- Integrating both sides - of the body or of your environment

- Keep working on things that need help - wake it up - then integrate it

- Mirror therapy

- Don't put limits on what people can do - the mind and body are amazing