The actual meeting with Hamid was from 4:30 pm to 5:30 pm. I spent the first half an hour doing some prep work. Putting him in the system as a user, assigning permissions, and recording a small video for how to record project timeclocks in adilas shop (just under 4 minutes in length).

During the actual meeting we went over how to add project timecards, different tasks, adding, editing, and looking things up. We built some quick links to help him navigate around quicker. We then talked about Snagit and Camtasia for options for internal and external training. Hamid is going to checkout some tutorials there to see how it works. We briefly talked about some of the billboard sites and options there. The other major topic was dealing with helping to refine some documents and make things more presentable. I gave him a few links to check out and we'll slowly start refining some of the pieces of the plan.

Links that I sent to Hamid

- 10,000 foot view of where we are headed... https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=10377

- More links and research stuff - master plan - https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=10179

After the meeting, I did some clean-up, reviewing some Snagit files, different videos, and uploading the new video for adding subs of time.

Phone call with Hamid. Touching base and going over some ideas for fracture and adilas lite. We talked about possible networking options with our connections. We also spent quite a bit of time going over some tech stack decisions and talking about needs for adilas lite. We went over three main avenues. 1. Is Planning - business plans, tech documents, etc. 2. Training needs - both internal and external, and 3. More billboard sites - sites that point to adilas. We talked about banking hours and no limits as far as investment opportunities (working hours for future payoffs and percentage ownership options). Nice phone call.

Quick meeting with Alan. We touched base on where we are at and how is doing what. I've been looking at Adobe XD documents from Jonathan Wells and doing XD training tutorials. I've also been digitizing notes and linking things together. Alan is working on a small wireframe for the adilas cafe login. He is also doing some research on modern UI/UX requirements and expectations. We talked about some domain names and also looking at billboard type sites for pointers to the main adilas.biz site.

I'm going to be harvesting Adobe XD videos and mock-ups. Alan is going to be working on features and making a nice list of features. I pointed him to a document that Shannon and I did for the presentation gallery and a backend outline of some of the features. This is not meant for the public (yet) but it will be a good resource.

We looked at the calendar and decided that we would shoot for our next group meeting for adilas lite and fracture to be on 8/30/23 (a couple weeks away from today). Good stuff.

After the meeting, I went and purchased a few domain names to claim our spot. Also did some other small to do list items.

Trip to Logan to meet with Hamid. We met for lunch and talked about fracture and adilas lite. Fun meeting. Here are some of my notes, from the meeting and just driving around.

- Model out each section, similar to the virtual obstacle course we are playing with (see # 10294). It may also be fun to model it out via the plates and cups model (small way of teaching one-to-many relationships for objects).

- Focus on one part or piece at a time. If you don't focus in, it, the whole fracture project, seems way too big and massive.

- If we get lost, we could always focus on mapping out the existing core. That is a "known" and needs to be done.

- We still want to do the rest of the billboard sites (other or outside sites that lead people to the main adilas.biz platform).

- We could offer preset packages for adilas lite. We could also offer an a la carte type option, where they can mix, blend, and pick and choose what they want or don't want.

- Hamid would like to play along with us on building out the dream. He has a number of ideas that he could throw into the mix. Eventually, he would like to transition over to more technical job. Future plans. Once again, great lunch meeting.

Final sign-off for a promotional website done by Hamid. We looked at code and I printed him out a check. We chatted for a bit and he handed me over the code for the business zipper website that he was working on. I'll look over it a little bit better and then get it pushed up to a live server to be an actual site. This promotional site was going to be kinda like a billboard that talks about a certain topic and then points the users or visitors to the main adilas.biz website. We are calling them billboard sites, a form of light advertising.

Meeting with Hamid (adilas intern) to go over his progress. He is almost done with the billboard site for the "Business Zipper" site. A billboard is basically a site that points people to another place (like to adilas.biz from the business zipper site). Anyways, he had a lot more content this time and it's looking good. This is just a fun starter project. We chatted and made some plans to get the full version up and live. I'll wait until he hands me off the files and then we go from there to review it, push it up, and have it go live. Making progress.

Touching base with Hamid, an adilas intern. He is starting to code his website project for the business zipper site. It's still pretty basic but a fun first little site. He's been putting in a little bit of time each day, working on things. This new site will end up being a form of a billboard type site - a separate smaller site that promotes a bigger site (the main adilas.biz site).

Meeting with Hamid Karbasi, new adilas intern. He will be building a small web site on the topic of the "business zipper" and how we came up with that analogy. Hamid was referred to us by Russell Moore. They had worked together as student and teacher at Bridgerland, in the web development department. Anyways, we got on a Zoom meeting and started going over things. We did a small get to know you session. We then switched over to a small about us and where we came from orientation. I did a light intro into adilas.

We then talked about a small assignment to build a billboard site for the business zipper domain (businesszipper.com). As of right now (3/1/23) it is pointed to the main adilas.biz website. Our goal is to create a new mini site or billboard site (think of a billboard or sign as you are driving down the road that pointed you to something else). In Hamid's words, "all roads lead to adilas". I thought that was good and fun.

We have a number of other domains that we may work on in the future. All of them will be billboard sites or mini sites that point to adilas.biz or a feature or concept within the adilas network/family. We made a small plan and then I gave Hamid a number of resources, info, links, and such. We will get back together in the next couple of weeks to see how things are going.

The morning started out with a rougher start than usual, even for a Monday. We had two servers that were acting up. It ended up that some of the domain names (older ones) that used to play part of the mix had expired. Some of our clients were still relying on those older domain names to push and transfer them over to the newer domain names (web browser and web traffic stuff). We had to work with tech support (internal) and get them all lined out.

Wayne joined the meeting and we went over some plans and server stuff. Eventually we got into some discussions about extra domain names and what we want to do with that or those things. We also talked briefly about some marketing, SEO (search engine optimization), and billboard sites (other domains that point back to the main adilas.biz site). Good conversations. I wrote down a few to do list items in my other notes.

On a GoToMeeting session with Dave Forbis. We spent the first little while and talked about ideas for the billboard sites. See element of time # 4108 for more info. We went over Dave's ideas for the sales (quick interest catchers), principles (why), and the features (what). He wanted me to pick 3 from each category. We talked about things and made some decisions.

We then switched gears and talked about Campaign Rise (custom wire job project). They still need some automation and also some training. Dave asked some great questions and I tried to answer them to the best of my knowledge. Dave is willing to help us go get funding and monies for certain projects. We talked about how Steve used to do that and did an awesome job. Currently, he is doing more development work and working on the backend engine vs out front doing sales and talking with clients. We may need to help switch that around. Steve was able to single handed fund and keep the entire adilas shop going. He is really good at that kind of stuff.

One of the places that Dave wants to help out is with automating the reoccurring invoices. They already exist and auto queue themselves up, they just don't auto run themselves. We talked about adding a new setting per reoccurring that allows for manual process (default) or auto create process. We also talked about how the actual money part of that is whole other project and deals with three separate systems (adilas, credit card gateways, and bank or finance institutions). We have to mix and blend all of the pieces.

Light research on some of the ideas that Dave Forbis was pushing up dealing with billboard sites and marketing ideas. I then spent the rest of the block updating server settings and security stuff. Email updates to a few key people.

This will hold the brainstorming for what Brandon Moore coined "billboards". They are essentially websites that have a video, information, image, etc. that redirect to the Adilas main site.  

On the morning meeting with Josh and Alan. We went over a few new changes from yesterday. Alan reported on his work with Bryan and making a new black box database table (custom table - specific just for that client). Alan and I talked about some naming conventions and how all new black box database tables will have "bb_" to start the table name. For example: bb_53_some_table_name.

We spent a little bit of time going over some new needs for quantity and weight multipliers. Alan and I decided to add two new fields to get things into real numeric values. Currently, some of the people are using some of the existing fields, but those fields are strings or varchars (text based) fields vs real numeric fields. Alan will be making some changes. We know that this project will have two phases. The first one will be to add the new fields and then match-up what ever values we can. The other part of this is going through hundreds of other reports and top cart mini's (gram counters) and Metrc API reporting (state tracking stuff) and flipping the older text based logic into real numeric values and real math. We will be using a value of 1 in the numeric weight field as a default. 1 times anything is the same number. If they want to change that ratio, they will at least have a spot (numeric field) where to do it.

I then started to work on the sales tax project and bringing up all of the black box code to match the master code files (checking for new changes on the custom tax fields 6-10 and other dynamic naming). As a side note... Custom is awesome, but there is a flip side to that... It takes quite a bit of maintenance to keep things up to date if you are changing core pieces.

I spent some time reviewing some notes and info that Dave Forbis gathered up dealing with Stripe (online merchant processing and credit card gateway). See element of time # 4095 for some notes and links. After that, I got on a call with Dave and we went over a few things. We have four different topics that we will be looking into next. They are:

1. Reviewing some older things (tons of white boarding and graphics that were done by Dave from a couple years back) - The goal here is to circle through and pick-up anything that still has merit.

2. Start working on some billboard type sites. These are small websites that have a smaller focus and virtually point people and users to the bigger adilas application. These are things like world building, data assembly line stuff, new school accounting, 3D models for world building and digital story telling. Dave and I were also talking about some concepts that adilas is built upon that are either core and/or we've pushed pretty far. Dave was saying that we could create mini Ted Talk type videos and/or graphics. Get people thinking and talking. Use those pieces to point things back to adilas and what we are doing. Some great marketing ideas.

3. Currently, the adilas platform has a very high concentration of MMJ or Cannabis related industries. Maybe get a list of other kinds of companies that are using the system and show some of the diversity with how and what they are using in the adilas platform model.

4. Dave would like a list of the different domain names that we have and where we would like to focus on building small billboard type sites. I will get this together and send it to him. In a way, we are lightly playing the digital real estate game and trying to setup small little claims. Those claims have two fold purposes... One, they will become virtual billboard sites pointing to adilas and the core concepts that we are built on. Two, they will provide prior art - which makes it so that others can't copyright, trademark, and/or patent - intellectual property stuff. It basically strengthens and protects the main core of what we are trying to do. Good stuff.

Steve and I met this morning and had a good meeting. It was just the two of us. So, we ended up talking shop and strategy. We talked about some of our internal pain points and how we could get someone to help us out with those things. One of the pain points was with merchant processing solutions. We have coded to a number of Internet gateways, and that is working fine.

We have two major needs on the merchant processing level...

1. Is on the chip reader side. We have two gateways that we have coded to, but it takes a person to get people setup and going on that (light babysitting). Those solutions require both web API socket stuff and software installed on a computer. If the company updates their software, we have to recertify and no one wants to pay for that. So far, those solutions have been somewhat of a headache.

2. We need a simple Internet solution where a new merchant could be approved very easily and then they are off to the races. Currently, the Authorize.net's and USAePay (our top two gateways) have pretty deep prerequisites that the merchants have to go through in order to be setup and qualify. As they grow and mature, they may need to go to a bigger processor, but we need a really simple solution to get people started fairly quickly. We are thinking that Stripe might be the best option and/or looking deeper into PayPal or something like that. I personally am leaning more towards Stripe.

We also talked about some other internal needs and who we could put on what projects. Some of the other needs are things like:

- User guides

- How to's

- News and updates (this is biggie for us)

- Billboard sites (world building, roll call accounting, data assembly line, and others)

- Tons of other mini projects that come up

- Build out the full Adilas API sockets and the underlying documentation to make that happen. That is a huge piece of the puzzle.

We would really like to have some focused project management on both internal projects and client projects.

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

11:00 to 12:00 pm - Meeting with Global Design and Assembly - orders and backorders

- Not duplicating orders when something gets back ordered. They would love to enter things once and have it flow through.

- They would like a definitive answer of prices and timelines to make that happen.

- They import products and the resell those items. Lots of shipping and fulfilling of orders.

- They would like to go more paperless in the backend office (what is needed, what is ready, what has been shipped, etc.) - Currently, they are doing a lot of paper back and forth. They would like to eliminate the paper model.

- Steve, talking about a transitional PO (similar to a transitional invoice - between a quote and an invoice). This would be used for the on order/not quite inventory yet but maybe we are already making payments, etc. Steve was saying that Will Hudson (adilas developer) was going to be working on the transitional PO project. Basically, a work in progress type PO... it isn't fully valid inventory yet, but it is becoming more and more solid values.

- Jason, I think you guys would have a lot of clients who would like for a more automated backorder process.

- Steve, was talking about the existing manual process of duplicating the original PO and only pushing the backordered items forward. You don't have to build it from scratch, but you duplicate and keep pushing the ball forward. The other side to this, is you only pay for what you really get and have.

- Jason, would really like that process to happen (like magic) so that the whole story is still there but it flows through the whole system.

- Example: Say we ordered 500, you only got 300. What comes next? Do you have a small box that says, move 200 to backorder (aka a new PO) or what other options might be there.

- Small talks about ice-down dates

- On a technical side... how you do you keep cost of goods, inventory, accounts payable, and what is received and what is not received? Some of the questions go clear out to the balance sheet and how to track things.

- Just in time ordering and smaller draws... Say they need 500 total, but only want 100 now and another 100 by next week and then rest when possible. Just in time issues and some tracking nightmares.

- Technically, we may need another couple fields where we could put desired amount, shipped amounts, and backordered amounts.

- There is more of a need for time based ordering - just as, I need this on this date, and that on this other date... Basically, tying things into more of a time or schedule based environment.

- On the just in time... If someone wants 500 and you only have 200, how do you put it on the order? Do you put the whole 500 on there (this would drop your inventory by -200) or do you just do the 200, out the door, and then put the other 300 on another PO/invoice. Basically items still needed to be bought, purchased, and/or shipped.

- Warehousing and stocking shelves - excess inventory and back stock

- ecommerce type scenarios where orders are processed and managed as part of a supply chain scenario.

- Steve, was talking about companies that are proactively pulling sales from the other companies and then keeping a supply chain up and ready based on max/min re-ordering options. Once they (the other company) gets to certain level, a new order is always processed.

- here is a link for some of the older back order or backorder brainstorming from the developer's notebook.

https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=back%20order%2Bbackorder

- Steve, was talking about the new plant move and harvesting options that they are building out. It used to be one manual process at a time. Now, they can click a button and move, kill, phase, or group hundreds and hundreds of plants at a time. The whole things was custom built and automated through elements of time, PO's, and parent/child inventory. Totally a new automated process.

- Jason, we only want what really happens to be recorded, but we don't want to lose the other details of the story.

- Brandi, we already have some custom code that helps us see what we have on hand, what has been placed on new orders, and what is still needed (don't have that yet)

- Brandi, we currently have to make a sales order, fulfill it to the level that is true, and then duplicate it and redo what is still needed. This is the current manual process. She would really love to automate that manual process and take out the possible human error (either multiple clicks and/or info that was forgotten).

- Backorders play on both sides of the fence... inbound items and outbound items... Both sides need a standard and automated flow process.

- Steve, was recommending that we see their existing processes and then make a plan.

- Brandon, we somewhat proposed a system that uses a request quantity (what is wanted), actual quantity (real values), and still needed values (backorders and/or wish list). We talked about having and showing all the fields and allowing JavaScript to help do the math, show/hide checkboxes to help automate the duplication process and pushing the virtual backorder and/or wish list forward. We would then keep chaining and flex gridding those pieces together. Basically, the same things that they are doing manually right now, but we speed it up and help to automate it.

- Steve, he loves clients who ask - Can we move this tree? I keep having to walk around it. While other clients just quietly walk around the tree every day. Sometimes those clients who ask the questions really help us move the ball forward.

- Steve, software and application are constantly changing.

- Jason, really likes to look at "scale". Can I do this? Can I do this for x number? Can I double or triple that and still be ok? Can I multiple by n (unknown number)? It all comes to scale.

- Jason, they have really used tons and tons of flex grid... It is now getting to the level where it is getting to be somewhat of a nightmare, due to the number of custom fields and where it is stored.

- Jason, process sequencing - what data (total) do we need to catch and then push to where it goes. First catch the data. Then we can display it, however we want to.

- Jason, he likes farming (talking about idea farming). But, he really like to harvest (seeing it through).

- Jason, will send up some docs on what they want done. We (adilas) will then help plan it out and get them some quotes and what not.

- Dream it up, and we'll help you wire it up.

Talking with Russell. We talked about some small billboard sites and pointing people to adilas and the adilas community. We talked about SEO (search engine optimization) and using existing verbage to help lead them to what we have and what we offer. For example: Things like CRM (customer relationship management), POS (point of sale system), ERP (enterprise resource planning), CMS (content management system), etc. Point all of those things to where it is going... We are leaning towards 3D world building, data assembly line stuff, new school accounting, and other concepts.

From our talks yesterday, these are some other projects that Russell thought would be cool. They are: a cool mobile app, more with time clocks, time - reservations and rentals, and other mobile ready pieces.

Alan hopped on and we went over progress on the in-line dollars off discount project. Alan is making great progress and we talked about a couple questions that he had. We also lightly touched base on the reoccurring invoicing and reoccurring merchant processing pieces that he is working on for Campaign Rise. Good reports.

Most of the session was spent working on the sales tax calculator page and showing the test calculations and output math.

Chatted on the phone with Calvin going over API socket connection for his desktop application. Also did some light planning for the upcoming live adilas training session. Here are a couple of random notes... no special order at this point.

- Sell the sizzle...

- Think GEO tourism for selling the venue and location of Logan, UT. 1.5 hours North of Salt Lake, hiking, fishing, history, USU campus, shopping, mountains, rivers, valley, Bear Lake, etc. 10 minutes from Logan, you could be in the mountains.

- Guest speakers - concepts, vision, processes, procedures, etc.

- Highlight new features, new updates, and upcoming projects. Think of things like Campaign Rise (social media and custom wire job for elements of time), Beaver Mountain Ski Area and Ski School, Steve's campground stuff, Plant phases and cultivation stuff, Russell's new custom email stuff, ecommerce, WordPress integration, white label stuff, sales tax changes, new discount options, etc.

- Show what has happened, what is happening, and what will be coming down the pipeline. Maybe show a timeline with some key points and historical stepping stones.

- World building concepts and how different clients are problem solving with adilas as their worlds change and progress. Try to focus on 3D world building and the concepts of the data assembly line. Show how some of that stuff is already playing out.

- Different topic, but I would really like to get some sites out there like billboards pointing back to adilas and what we are doing. These are all of the main concepts such as 3D world building, data assembly line, creating a system, API sockets and playing at the wall, etc. These might be great projects for Russell to give his developers who are going through the program at Bridgerland. Good stuff.