Adilas Key Contributors:

Steve Berkenkotter - Main owner and business partner - original ideas, concepts, and training - sales, relationships, dreamer, visionary, custom code, coordinator, builder of the first industry specific skin, and the list goes on. Huge player in the adilas story and timeline. One of the original owners in Moring Star Automotive - where the system came from. There are three known Steve's in the system notes. Most of them are this Steve (99 out of 100 times). He won't admit it, but adilas was his brainchild.

David Berkenkotter - Steve's brother and business partner in Morning Star Automotive. David was a system user and helped us create the adilas quick search. He liked using that feature, the quick search, but it only existed on one page originally. He wanted us to put it on every page. That ended up being in the header. He was also one of the original partners in adilas. Power user in the system. Sadly, he passed away due to cancer.

Shari Olin - Commonly known as "Shari O.". She worked in the accounting department back in the Morning Star days. She has been somewhat of a mother hen to help all of us crazy chickens keep going. She helps with customer support, training, payroll, bill collection, and tons of backend office functions. Major power user. Just being silly, but she can have the mouth of a sailor but the heart of an angel. Part of the adilas admin team and a great friend.

Craig Leitner - Also part of the original Morning Star team. Craig was the automotive floorplan and bank guy. He is a power user in the system and does a lot of bank reconciliation and other tasks. He currently works with Steve and asks as the adilas controller (money flow guy).

Cory Warden - Originally an adilas rep and consultant. Cory become part of the team after being a rep for quite some time. She helps with customer care, client support, project management, and keeping the team on track. She also does all of the news and updates and other training material. Cory does tons of oversight type services for our clients. Power user and part of the admin team.

Sean Carlton - Sean was a manager at a Cannabis dispensary in Colorado that used adilas for years and years until they sold. Steve recruited Sean to help with sales, deployment, and training. Sean brings lots of usage experience. Often, he is one of the helpers if we need to send someone onsite to help with a deployment or training session. Power user.

Brandon Moore - I'm one of the guys that writes most of the developer's notebook entries. Originally, I was hired by Morning Star, the automotive dealership, to help with data entry, accounting, and website stuff. I ended up being one of the main adilas developers and architects. I build content, write code, help other developers and team members, and help with training. Helped start the project back in 2001 under the Morning Star name.

Chris Dunsey - One of the first adilas interns (developers). Helped with a number of projects. Ended up being somewhat of a consultant later on.

Shawn Curtis - Kinda a funny story. He was taking a developer's class at Bridgerland. He knew my brother Russell. He asked to join our developer class and became one of the first interns along with Chris Dunsey. Shawn ended up helping with payroll and other projects. Some of the photo galleries in the system came from Shawn's help. He also worked on the media/content (file upload) pieces. Later on, he did more payroll work and acted as a buddy to Brandon and did some consulting work. We worked together for years and years.

Russell Moore - Russell is my younger brother. Originally, he was added to the group because of his graphic skills. He ended up being a great backend developer and project manager. He has also acted as a trainer and mentor for Brandon along the way. Much of the current system came from projects and efforts that Russell was involved with. He has also been Brandon's AI tutor in recent years. Great help to the system. Huge contribution.

Chris Johnnie - He is an entrepreneur who teamed up with Russell to help create a company called "Adilas For Business" or "AFB". Eventually, both Russell and Chris sold their pieces back to adilas. They were honestly the first ones to really try to run as a white label of adilas. This was back in 2015 and 2016. Chris really helped to push the product to the next level along with Russell's help.

Danny Shuford - Longtime friend of Steve's. Danny helped with some website design, sales, and videos for adilas. He even got into creating custom PDF labels for clients. Light development work.

Marisa Shaw - She is Danny's daughter. Danny brought her to an adilas training event in Denver, CO. Marisa was the star student. She ended up helping with some graphics, flyers, marketing material, teaching, instruction, and planning. Power user. Very helpful.

Shannon Scoffield - Shannon is Brandon and Russell's sister. Her maiden name is Shannon Moore. Huge help and virtual assistant to Brandon. She has helped with training, project management, and content creation. Most of the major content sessions were or have been with Brandon and Shannon working together. When they, Brandon and Shannon, were traveling, Shannon was one of the primary adilas instructors. If she was teaching Brandon was taking notes. If Brandon was teaching, Shannon was taking notes. Power user.

Cheryl Moore - Cheryl is my mom. What an asset. She owns a small business and has owed a few different ones. When we were doing training sessions, she came to every one of them. She asked wonderful questions and was a great supporter. Sometime, I would use her as a test subject - can my mom do this? If yes, we are good. If not, we may need to keep tweaking it. Thanks mom!

Wayne Moore - Wayne is my dad. He was my hiking buddy and more than willing to talk about ideas and concepts on our walks and hikes. He helped out with video stuff and was a great coordinator for making other connections. He worked at Bridgerland (technical college) and helped us get setup with classrooms, computer labs, and other great connections. Huge cheerleader! There is another Wayne, Wayne Andersen, he is a backend developer, systems guy, and database guy.

Wayne Andersen - This Wayne lives in Portugal and helps with all of the backend security, server, and code testing. Major skills, writes code, helps push all of us to new technologies, partially retired but loves to play with tech stuff. If you search for Wayne and it deals with concepts and coordination stuff, that's my dad, Wayne Moore. If you search for Wayne and it sounds like a master backend guy, that's Wayne Andersen.

Alan Williams - One of the lead developer's at adilas.biz. Alan joined us in 2015 and quickly came up through the ranks. Trainer, CTO, team lead, master developer, prototyper, and system architect. Alan has helped with many projects and features over the years. He also helped Brandon with some of the prep work for the adilas lite (fracture) plans and project. Sometimes called "Dr. Alan" by the other developers. Example: This might be a project for Dr. Alan.

Bryan Dayton - Bryan has been one of the most versatile guys on our team. Originally, he joined a development class out of curiosity. He and Brandon live in the same town and know each other from church. Bryan has done more custom code or small system projects than almost any other developer. He also joined the team in 2015. He helps with sales, custom projects, pushing on projects that he thinks will yield a return. Lots of work on the adilas lite and fracture project. Very hard working and versatile.

Dustin Siegel - Developer who helped with numerous cannabis and cultivation type projects. He worked directly under Steve to help with that business vertical. Many of the original pages that Steve built were taken over and remade by Dustin.

Eric Tauer - Developer and custom code guy. Originally, Eric knew Steve and lived in Salida, CO. As a note, adilas is Salida spelled backwards. Eric has a background in database work and data warehousing. Eric has done tons of custom systems for clients. Often, Eric would pioneer certain features or logic, as custom code, and then we would bring those features into the main adilas application.

Garrett Kirschbaum - Adilas intern and then full developer back in 2015. Stressful time of building and expansion. He and others helped run the adilas shop with Brandon's help. Garrett was a great developer and helped us standardize a number of tools and features. He was the first developer to work on sub inventory, back in the day. He also did other projects and helped with some developer management stuff.

Charles or "Chuck" Swann - Charles was an instructor at Bridgerland for web development. He builds custom websites, does amazing mock-ups, prototypes, and is a CSS master (styling a website using code). Chuck worked with Russell to help with redesign work, projects, and vision. Chuck worked fulltime for a number of years and now works and coordinates work done by a small hand-picked design and development team. Anything that needs some design loving gets passed over the Chuck and his small team.

Steve McNew - Friend of Steve Berkenkotter's. This Steve helped prep some whitepaper documents to help with getting adilas standardized and some internal audit type stuff. Mostly white papers and putting things down on paper. He ended up getting hired by the local school district and wasn't able to finish the process, but he got it started. He asked some great questions, and we had some good conversations.

Abby Elkins - Abby is Brandon's daughter. Her maiden name was Abby Moore. Abby, when she was little (10-12 years old) helped with some of the original concept artwork for adilas. Later on, she helped with content for the presentation gallery and then the adilas lite plans (fracture). Currently, she is working graphic artwork for different adilas pages. She's now in her mid 20's and has some awesome art and content skills.

Aspen Moore - Aspen is Abby's younger sister and Brandon's daughter. Aspen helped Brandon with some planning and counseling (mental help). Aspen also did some general business consulting with her dad Brandon.

John Maestas - Developer, backend server guys, and designer. John came to us through Dustin. John was uses as a jack of all trades on the backend and frontend. He did numerous projects, documentation, payroll, and page redesign projects. John was also very help to Brandon in working on the notes and comments on the SWOT analysis document. Many other projects as well. Good vision of the future.

Kiva Berkenkotter - Steve's wife. She helped Steve with various projects and planning sessions. At one point, she was in charge of paying commissions and collecting monthly reoccurring payments. Huge supporter to Steve!

Heather Moore - Heather is Brandon's wife. What a trooper. Cheerleader, support, ideas, and consulting. Huge asset to Brandon (me). Thanks Heather!

Jonathan Wells - Designer and mock-up guy. He helped to map out the system and created a number of deep mock-ups for adilas lite (fracture) projects. Great job catching the vision and putting those pieces into a visual representation. We still refer to his work when talking about fracture (future project for adilas).

Jonathan Johnson - Business consultant from Epic Enterprises. Met with Brandon and Steve in end of 2019 into 2020. Really helped us see some needs and opportunities. Later, helped Brandon with some other consulting when trying to define the fracture plan.

Calvin Chipman - Windows software developer. Calvin also did a bunch of web-based work, database stuff, label printing, and API socket stuff. Calvin was the first developer to use the adilas API's to create a native mobile app for a client. He also built a number of special developer tools used by some of our team to speed things up. He's the tool guy!

Cody Apedaile - Bryan Dayton's cousin, Cody helped with a bunch of JavaScript code and changes. He also spent some time working on the UML diagram for the adilas database. We didn't get things finished, but he was working on a new build your own interface (custom to you) for adilas. We ran out of funding. We want to get back to that project at some point.

Dave Forbis - Dave was the official "high tech gofer". He did a bunch of things. Graphics, project management, brainstorming, planning, sales, and helped with managing developers for the adilas shop. He was another great student. He came to a number of training courses and brought so much to the courses. He was also a big support to Brandon during some rough times.

Josh - There are three Josh's. Josh Wheeler, Brandon's friend and developer. Josh Sagert, developer and adilas user (worked tons on the discount engine), and Josh White, Steve's friend from California. Josh White has brought us a number of bigger leads and bigger players, like franchises, and other higher-end clients. Anything recent is Josh White, from California. He helps with networking, sales, and dreaming of new things.

Suzi Distelberg - Sales, training, and deployment. She also worked with some custom projects and doing step-by-step user guides. She has helped with all kinds of projects and even gone onsite for setups and training. Great asset!

Kelly Whyman - Kelly is Dustin's wife. Kelly was single handedly the best independent sales rep that adilas had. She did training, consulting, and sponsored a number of custom projects. Kelly helped Steve and Brandon with reports, functionality, and other things. She got so good at things, state contracts snagged her up to work at state and multi-state level stuff.

Molly Hennessy - Molly was another independent sales rep and consultant. She had numerous clients and got into doing SOP's (standard operating procedures) and other high-end documentation and training. Molly was an entrepreneur and even started creating some of her own product and services. If you search adilas on google, some of the other results are from Molly. Super creative and a great consultant.

Hamid Karbasi - Developer - He has worked with Brandon doing small websites, training, and small tasks. He currently is a manager at a retail store and brings some managerial type skills to the table. Willing to talk about concepts and how they apply to retail and other environments. He is also lightly helping with some planning for fracture.

Gene Spaulding - Friend, entrepreneur, and businessman. Gene is an old college friend. We had a number of friends in common. He has been a small mentor to me over the years. Way back, before adilas, he helped me get my first business loan for a project that I was working on.

Sharik Peck - Friend, entrepreneur, public speaker, physical therapist, and businessman. Good influence and mentor in ways. Sharik and I used to exercise together back in the day. Many of fun walk, run, and weightlifting session. Learning some conference and training skills from him and his wife. They have done really well pushing their product lines and doing some marketing. Trying to get some ideas.

Bridgerland Technical College - Use to be Bridgerland Applied Technology College. Not a person, but a huge help. This is a local technical college in the Logan, UT, area. Brandon's dad, Wayne, worked there. Tons of assets. They provided classrooms, training options, computers, and even an small incubation spot (starter office space) for the adilas shop during the startup phase. Huge asset!

McCorvey's Pro Shop - Also known as Bowling World. Client that had multiple locations. The started out with around 30 and grew up to the 90+ location level, all using adilas. Long time client.

Emerald Fields - They were the first client that wanted their own fully dedicated box and server. They had multiple locations and requested some custom code, reports, and features.

Beaver Mountain Ski School - Client that we helped them track their ski school (snow sport) lessons. Students, instructors, classes, and schedules. Custom interface dealing with elements of time and flex grid.

Bear 100 - This was the first event or annual event client that we did. They used the system for about a week each year. They had 350+ runners and their families that would be on the site for multiple days straight. It was a 100 mile running race with 13 aid stations and a small social portal for the family and friends to watch their runners. This one was special as it had custom input options to upload CSV files to populate the database vs normal HTML form field entries. Records were sent in batches from remote places to adilas for storage and race progress.

High Valley Bike Shuttle - Online ecommerce and scheduling client. They also have a cafe and small retail store. Fun online scheduling and bulk flex grid projects.

Herbo - Mike Roundtree, owner of Herbo, was the first company to do a small white label of adilas. Mike has been a great asset to Steve and the two of them have worked on projects, plans, and dreams. Herbo also has a custom payment solution that they are trying to market and get rolling. Mike has been a great supporter for years. He is also a certified CPA and that credential helps us and him. We would like to get other CPA's on board as well. Thanks Mike!

Nxtlinq AI - AI assistant. These guys really pushed us to get an AI agent inside of adilas. Tons of development took place and lots of prep stuff. We wanted to do a 3-part plan for integrating AI. 1. Teach it how to navigate using the AI quick search (check - done), 2. Teach it all things adilas. and 3. Teach it how to be clear up at the consultant type level. We only got the first phase done. Lots of other plans and such, but we ran out of funding.

Grok AI - Steve loves using Grok. He has built a number of image generation options inside of adilas. He is also working with Grok to feed it data to help with analytics and AI insight. This is not finished yet, but we may end up using Grok as an AI assistant inside of adilas. We have simple and emerging connections available right now but need to really polish things up before going live with the AI assistant options.

ChatGPT AI - We have started using ChatGPT to help with code, explanations, explore resources, planning, and help with training and flow for people and other AI bots. Currently, Brandon, Steve, Bryan, Alan, Josh, Russell, Chuck, and Wayne are using AI in either ChatGPT chat sessions or some other form of AI. We have some using Copilot, Gemini, Claude, etc. AI is actually helping in many ways. ChatGPT is a big one for use. Anyways, they are earning their place in the adilas key contributors list.

There are so many more that I can't list. Developers, users, power users, reps, consultants, trainers, clients, accountants, friends, family, and even critics. They have all helped out the idea farming process and progression. Good stuff! We couldn't have done this alone. It takes a community to do what we are doing.

Meeting with Bryan and Suzi. Dealing with Lucky Puppy stuff (planning and figuring out where we are at). They really want options for docking (virtual copy and paste board for their appointments), drag-and-drop, multiple relationships (owner to pets, pets to rooms, pets to other assistants), popups and rollovers (showing sub details), splitting tips, etc. Suzi showed us some log info under the customer log that she had added. I was really glad that she did that. I had forgotten a few things. She had log notes, screenshots, files, documents, and other stuff. Bryan and I will get together and do some planning and then we will circle back around after the first of the year.

Talking with Bryan - I was asked what are our most popular business functions - these are my top three functions - where I think people like to use our products - POS & inventory tracking, CRM (customer relationship management), and scheduling. Here are some fun links: POS, CRM, and Scheduling.

Switched over to the QuickBooks API stuff. We kept getting an error and didn't know why. We had to make some live edits and then do some live testing. We found some large negative numbers and it looks like the client is maybe using some values and tools in the wrong way (updating inventory counts using huge negative invoices vs using an update inventory count PO - normal way). It sounds like a training issue. We will get with the rep and show him so that the client can do it correctly. Hopefully that will fix the API issue.

Meeting with Bryan. Going over some leads and checking out white label stuff for Herbo. Making some small changes. Trying to figure out which customers we can help and how quickly. There is huge demand.

Jumping in with Bryan to look at some white label info and settings for the Herbo server. Trying to debug some things. Someone had taken over one of the special corporations on the Herbo server. Basically, they just wanted a test site, but they took over one of the special ones (ones that we use to manage each server). That's a no-no. We have code that looks for specific id numbers and such. Anyways, we will reach out and them and get it all figured out and going in a good direction.

Closing elements of time behind the scenes for Cory and Kelly for a demo corp on the Herbo server. Spent some time working on the pub-15 for 2024 - entering withholding table data.

Phone call with Cory to go over plans and logistics. Emails, checking on the Herbo server, texts and emails, and working on a database update for Eric - pulling out a dependency in the code.

We started out in the server meeting talking about an outage we had last week at the hosting level (upstream of us). We talked about what to do about an outage and getting and SOP (standard operating procedure) or process in place for what to do on a disaster recovery type level. Cory was checking on different projects.

Wayne is looking into ColdBox as a ColdFusion framework. We talked quite a bit about his findings and progress. After that, we were figuring out what is next for the data 5 testing server. We've had a few projects that get almost all the way done and then sort of get lost in the sign-off and testing phases. It could be data, time, scenarios, settings, or just not watching it all the way through. That code isn't gone, it's just sort of stalled out or in limbo land. Cory and John were making plans to do some testing on a project.

They were looking at a server and why it is running slow. We need more info from the client as to what they are doing (process or procedures). We really need to know what corp, what page, what time of day, and what process they are doing. Just saying that the server was slow doesn't help us out very much. Once we finished this up, Cory bailed out and left just Wayne and John and I on the meeting to work on my local development environment (docker images, git stuff, and database code).

Both Wayne and John were watching my screen and trying to help me figure out what was going on. We repulled down code, rebuilt images, and did whatever updates we could think about. Tons of command line stuff. I'm not very good at that (hardcore IT and tech stuff). They were very kind to help me for hours and hours. As we worked, we were having some side conversations about different things. Here are some of my notes.

- Aspects, events, announcing (broadcasting states and status), listening for events and announcements, virtual queues, and event handlers.

- We talked about resource collections, private resource collections, and virtual session management options.

- Standards and consistencies across platforms and development environments

- Different modules for security, validation, etc.

- Form validators and bulk issue finding

- The power of mixing rules and assignments

- Virtual flash memory and managing containers for memory objects (just in time memory allocations and storage).

- Thinking in both layers and levels - for almost everything

- Writing less code using a framework

- If we went with a new framework, we would need both training and deeper education.

- We talked about having both commercial products as well as open source products. Mixing the two types together. Some people will buy the commercial product and then contribute to the open source product. Or the other way around - open source to commercial.

- Packages, extensions, modules - making complex decisions

- Looking at clustering options - comparing Lucee and Adobe ColdFusion - including options for clustering and licensing requirements. Adobe ColdFusion is really nice, but you can lose your shorts on the clustering options and prices. It can get painful in the pocketbook (costs).

- If we make some changes, we would have to change our pricing models. If a client or customer wants more dynamic resources, they have to pay for it. The price would based off of usage vs just a fixed or static price.

- We talked about paying for support - both what we offer and what we are requesting from other vendors and web hosts.

- Talking about ways to give back to open source models and projects - help with bug fixes, donations, and keep pushing their product forward. We spent a little bit of time talking about other ways to help businesses and products that we like and want to support. Just conversations at this point but rolling a few things around.

Wayne had to leave (dinner time where he was at) and just John and I kept going. Wayne checked back in a few time but to no avail. We couldn't get my local environment fully back up. Wayne is going to do some testing on his side and we'll hit it again tomorrow. While we were waiting for things to download and install, John and I were talking about computers and different specs. I may need to upgrade my local computer. It's kinda small for what I use it for (spec wise and hardware wise - RAM, motherboard, chips/cores, hard drive, and processor speed).

Sean and Michael were meeting and talking about gift cards, demos, and sales. I was cascading updates and settings to other servers. John jumped in and helped me with the Herbo server and with my local docker image stuff. The Herbo server just needed to be restarted (Adobe ColdFusion services). We kept running into problems with the docker image stuff. Some of it would run great and other parts would fail or not work correctly. Wayne jumped in and helped me out as well. No major success before the server meeting started (the next meeting).

Cory and Steve were going over labels and sub inventory stuff. Mike Roundtree joined in and was asking about Herbo payment solutions and options for demos. I mentioned to him, if needed, we could help him out by using special accounts, inside of adilas. We will check to see what is already built out and then go from there. Anyways, he has some needs and ideas. We'll see where it goes.

Next, Mike was talking with Sean and Steve about ecommerce, multiple locations, using a single system for multiple different tasks, and making plans for a new demo site for somebody in Hawaii. Shari O. will spin up the new site, Sean will help fill things in, Cory will help Sean where needed. Fun to see them all making plans and coordinating. We also pulled in Bryan briefly to talk about the Herbo (eXPO) payment solutions and what has been automated and integrated. The demo is out a few weeks.

Shari O. had some questions on a bulk inventory update that needed to be done for a client. She and I made a plan and she will be kicking me over an email to get it in writing.

Cory and Eric were talking about enterprise level stuff and the new item catalog that they are working on. We then switched over and were talking about a 3rd party API socket connection that has been in place for a couple of years. They had some questions and want us to do some research. We feel like they should pay for it (new maintenance and new development). We looked around in our code repository a bit to see if we could find any changes that happened on our side of the fence.

Wayne joined the meeting and reported on some mandatory Adobe ColdFusion updates (patches) that had to be applied to all production server (security risk stuff). We talked about getting server documentation and helping to transfer that server and backend knowledge to the other developers or whomever might be taking over, once Wayne retires. Wayne has been making some notes and doing some screen recording or screen capture videos.

We then rolled into a discussion on a dedicated testing server. I'll cover more of that in a minute. At the end of the meeting, John was reporting on progress on CSS and look and feel changes. He is working on printable deposits and printable expense/receipts. He is also making some small tweaks to the layouts and where certain dollar figure data is located. Good stuff. Cory and John were talking about plans on the discount engine and making plans.

Going back to the dedicated testing server - We went over a proposal to get a real testing server up and going. We currently have a number of testing bottlenecks. We talked about reverse merging in master code to the working branches, to help keep them up to date. We have had problems when a project takes weeks or months and it has not been kept up with the master code branch. When we go to merge it, sometimes there are huge differences, conflicts, and some of the underlying application structure has changed. That merge process then takes a while to sort out and make sure that everything gets fully tested and verified again. Anyways, it is an issue that we deal with.

////////

We then had a small discussion about pros and cons for getting or having a dedicated testing server. This was all recorded on a google doc, but I'll paste it here for searchability. Here are some of our notes from today:

Group discussion notes

Cory - We’ve tried this before - what would be different this time?

John - No FTP access to the testing server - there are pros and cons to that

Wayne - We need to test one branch at a time

John - He would like to see it (use of the testing server) go in a line (testing schedule or queue) - I’m next, you’re after me, etc.

Wayne - If we need to, we wipe it clean and then start over again. That’s the process and the beauty of it. We test on it, beat it up, and then wipe it clean for the next round.

John - We can get a full copy of a client’s database and then kick the crap out of it. When done, we just flush it. We never mess with live data. We just make a copy and then test and push against that. Much better look (at live data - copied) then our own fake development data.

Wayne - We need a way to turn off outside 3rd party API’s - either mocking it (pretending) or muting it (silent send outs).

Cory - Sometimes we have big issues with Metrc and other outside parties and doing testing that flows into outside 3rd party API sockets and feeds.

Cory - Currently we are using the Herbo server for some testing. We have been having problems with that. What is going on?

Wayne was commenting on the Herbo server - We are mixing branches, there is still FTP access, it is pointed to a non-master branch, and we have certain things that we can’t change for demos or other needs. Basically, we are using a live server, we have live clients on it, and we are trying to test on it. Too many mix and blend variables... Hard to manage.

Wayne - Would like to see some project scheduling - project A on this day, project B on this day, etc. Keep it tight (ish).

Cory - Con of having just Wayne and John having access to the testing servers. The scenario is, if we find an error, we can fix it right away (whoever the developer or testers are) but then we have to contact either John or Wayne to help that new code get pushed up and deployed. That becomes another bottleneck.

Wayne - We could change the timeframe or auto deploy time cycle to make it faster.

Cory - What about data 5? That is an option, but we would have to make a full copy of the database and all of the corp specific files (images, PDF’s, csv files, etc.). We could then order a new hard drive or put those files somewhere on the current hard drive that we could get back to if needed.

John - Talking about paying bills (meaning our clients)… If a client doesn’t pay, we should be able to just shut them off.

Cory - Question - How much does it cost to put things in cold storage? How much does it cost to bring it back up live?

John and Cory - Talking about costs. John was saying that we need to build in this cost ($400-$600 per month) as an operating cost. We are a software company. We kind of need this. Just like being a foundation company and not having access to a cement truck. It creates a problem.

There are ways to lower the cost, if needed. We could lower CPU’s, RAM, etc. We could also spin things up/down as needed.

Wayne - Rough cost to spin up a server is 2+ hours (somewhere in that neighborhood)

Cory - Really liked the video idea of Wayne recording what he does as future training things and visual assets. Good idea. We just need to be careful of who gets those… This is the whole backend access zone stuff. We just need to keep it tight.

John - He has some server docs and would like to get that put into a private repo that only has access to Wayne, Brandon, and John. Small group.

Cory - Figuring out a way to force some of these clients to pay for cold storage and reanimation or redeployment of the servers. It comes down to if you don’t pay your bills, we get full control of what happens. We need to do what we said that we will do. Forcing the hand by making them pay for the backup data.

John - We just need to have our plans and procedures in place. We need something to stand on.

Brandon - We could do some cold storage on the same servers. Either with a different drive or a partitioned area where we could store things. As a group, we were talking about other possible storage options within the same box. We could make copies of ColdFusion files, client files, and SQL data dumps. Put them all out of reach but on the same server. Then if needed, we could restore things as needed.

John and Cory - If we need to reanimate or redeploy - here are the params and timelines and costs - Part of the plan. Some of these values may change in the future as well.

John - If the crap hits the fan… He doesn’t want to be in the spray zone of that fan. We need to protect ourselves.

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.

Helping Steve with some image paths for a 3rd party solution menu system. After that, John was showing us some new pages that he is working on and changing the look and feel. We looked at some custom Expo/Herbo code and layout stuff. At times, we are not sure what certain older pieces of code do and accomplish. Sometimes, just like in life, we have to fake it.

Steve chimed in with some accounting history to help John with some of our terminology. He was talking about the term "Posted" and what that used to mean. In a way, this older term was a way of locking things down and moving data along a virtual data assembly line - old school style. As a side note, it is amazing how much training and education it takes to help our users know what to do and how to do it. That seems to be a never-ending process.

The last topic of the meeting was looking at some of John's new mobile responsive code and page layouts. It is looking good. We are excited to see where it goes.

Eric joined the meeting and was touching base on a number of projects. We chatted about gift cards, enterprise catalog or item catalog, and the inventory snapshot project. Small sales meeting. The guys were reporting on efforts and what not. Lots of follow-ups and different communications. We have the best price for the value. Talking about bigger demos and updates. There are lots of little shops out there that need our help.

Shari O. asking questions about a client setup. Steve was showing some stuff from the Herbo proposals. Light research on using Google Meet (online meetings). We currently use GoToMeeting, just looking around.

Bryan has been making videos about his project, just to document things. Small push to change eXpo payment type to Herbo payment type. Lots of talk about layers on time and availability. Bryan got deeper into reviewing the horizontal time view page for Beaver. We also talked about time buttons (this will be a sub of my cart favorite buttons but to help book and sell time - with an additional calendar tie-in as well as shopping cart functionality). See elements of time #'s 6967, 8004, and 9633 for other ideas on time buttons.

We were playing inside of Microsoft Excel with scenarios and options for web availability and layering.

Steve and I jumped on a meeting. He was showing me a little bit of stuff and we were talking about the demo that he, Mike, and Kelly were on this morning. Kelly had created a really nice outline that had a series of live links on it. Basically, she was logged into a corporation on the Herbo server. She could then split the screen and jump from her outline presentation right into the system without any migration. That allowed her to follow her outline and jump to pages that she wanted to show or demo. Pretty creative and a great way to use web-based software.

On that same note, that kind of presentation and/or demo takes quite a bit of prep work to get it all laid out, prepped, and ready to go. Pretty awesome. Anyways, Steve was going down the outline with me and going over things. As a fun side note, he and the girls (Cory and Kelly) were prepping things and they reminded him of reports that he had forgotten that we had. We have so much stuff that is available and ready to use. Sad but true, we sometimes forget what we even have, there is so much.

Steve's wife came in and he had to go and help her with something else. I flipped over and started to do more transferring of notes and recording notes from the past couple of days. Good stuff and lots going on. Busy time.

Going over custom labels and being able to configure those labels through dynamic settings. Steve's next settings page is going to be for the printable invoices. They started to talk about Metrc (state tracking system). Steve was also reporting on what Mike is doing and what he is pitching and throwing. Mike owns Herbo and eXpo, two different companies that are integrated with adilas as 3rd party solutions and even virtual white labels of the adilas platform. He is pitching adilas as a possible option under some different labels and umbrellas.

The guys got into a subject of adilas phones and what we could offer there. This is a phone tree type software package that adilas acquired a few years back. It has kind of just been sitting there, being used by a small number of clients but not really being pushed. They pulled it up and were looking around the adilas phones section and pages. Getting deeper into the phone tree stuff.

Danny was saying, software is only as good as the setup and the usage of that software. I would agree. We also were talking about some of the salespersons and what they could do and offer. There are some great skills out there.

We started talking about a new shopping cart and being able to switch back and forth between a possible new look and feel and the older more stable versions. Talking about adding more cart settings. Ideas about being able to flip over to toggle switches vs checkboxes. This is a more modern look and feel thing. What we would really like is nice interfaces that have the one-pager type feel where you can do all kinds of things from just one page. It still interacts with the server, session (memory stuff), and database queries, but there is a minimum or no full page refreshes. It all happens on one page (one-pager apps). This is a more modern way of doing web code.

Steve is excited to get John helping out with some new look and feel stuff and pages. I too am excited to get John going on some GUI (graphical user interfaces) and UI/UX stuff (user interfaces and user experience). Here we go, just need the funding and the green light.

Group session with Cory and Eric, going over gift card logic and testing. We were talking about testing and Eric made the comment - the coder doesn't do the testing... you need someone else to test it. That is really good advice for us. We have been so small, we would play all of the roles, design it, code it, test it, and deploy it. As we are able, we should start sharing the load and getting other views on the code, logic, and flow.

While Eric and Cory were testing scenarios, I was fixing some logic and going through the submit cart page. Small logic tweaks to accommodate the new flow for multi-error messages without a hard stop or hard abort in the code. If one or more things errored out, the rest of the submit cart process would try to finish and then show any errors at the end. I pushed up my changes and Eric will add to them.

Both Cory and Steve were on the meeting. Cory was going over things with me and Steve would chime in when asked about certain projects. He was working on custom label stuff behind the scenes. We were talking about numerous projects. Coordinating flow on the Herbo server for what is up for testing and when that code (branch) would be available and being tracked. As a fun side note, some of the bigger projects that have been out for a while are getting done. It's creating a small traffic jam for testing and deployment.

Cory has a new project for an anti-permission (negative permission). This will be a permission that only allows the adding of a new invoice. No bulk look-ups, reports, or edit capabilities. Talking about pros, cons, and details of that permission project. It will be on my development ticket in a couple of days.

Thumbs up to Cory, she is doing great and coordinating projects between Steve and I and who is going to do what. That is much needed sometimes. More talk about settings and permissions. We also talked about prepping for possible rollback while or after testing, if we needed to. Basically, being ready in case we had to rollback code quickly. This is not something that we do all the time, but it depends on the project and what it touches and/or affects.

New week. Sean joined the meeting and we were just touching base on happenings over the weekend. Steve joined the meeting and the three of us were doing a little bit of catch-up. Steve has been working on the gram controllers over the weekend. Small report there. We talked about how we are constantly rewriting our software, daily tweaks and modifications. Good stuff.

Steve showed Sean and I a huge PDF proposal that he and Mike from Herbo and Eco Science have been writing up and getting ready for a possible big contract. The Herbo pitch uses adilas as the backend accounting and frontend POS (point of sale) system. Interesting mix and Mike is really pushing on things.

As we were talking about pitches and sales, Steve and Sean were rolling over ideas of selling or pitching smaller pieces and doing some local marketing on certain parts of the system. Sometimes we pitch the whole thing and that is so big it scares people away. We do tons of little things, we just join them all together to make up the whole system or platform. Depending on the situation, we may need to only expose smaller pieces at a time.

Everybody else left and John and I were doing some back merging of the master code branch into his local code branch. We were manually comparing old and new files. Trying to keep things updated.

Cory and Wayne were going over data 16 server issues. It seems to be quieting down but we have little hiccups here and there. Wayne reported on the new corp-wide settings and corporation model object stuff that he and Alan are working on (DAO's and services). It is getting pretty close, and we expect to get some new code tested, pushed up, and fully deployed by end of the week, or first part of next week. When it is ready, we will launch it on the Herbo server for doing some live testing. We went over a couple of other server related projects. Small updates and reports.

After the server meeting, Cory and I briefly looked at the bank drill-down bug that Kelly had reported. We decided to make a small change. After that we talked about a client's need for some maintenance on a merchant account type that we are not really wanting to support. We will look into it but may or may not commit to doing the maintenance. Currently, we only have one client on that particular service and it may cost of a couple of thousand to do the upgrades. We'll have to see. We will commit to getting a guy in there to check it out but we will wait until we hear back from them before taking the bigger commitment step and repairing everything. This wasn't our fault, the vendor of the merchant processing code made changes and thus are forcing us to make upgrades and do unscheduled maintenance, on our dime. Not very fun. We'll check it out.

Doing emails and looking over things. Steve and Sean were on the GoToMeeting touching base. Eric popped in and we pushed up some code on the Herbo server for Sean to do some testing on the barcode and 2D driver license scans. Sean and Eric went back and forth with different tests. As part of the testing, we were getting random errors from the scans, barcodes, and mag stripe swipes. We were getting different results by scanning the same card. Sometimes dealing with hardware has its own little quarks and issues. We were also having some browser issues. We end up deciding that Eric would purchase some new hardware and we would test it from there.  We were just getting inconsistent results using the existing hardware. That makes it really hard to debug and program accordingly. Not sure what was going on.

Eric and I pushing up some code for semi-live testing on the Herbo server. We then rolled into a discussion on the mini aggregate project for inventory quantities. We were drawing and going over ideas and options. Eric was talking about the difference between snapshots (current view of something without dates) vs normal aggregates with dates and possible roll-ups. Great conversation. We spent some time talking about flow, options, timing, and how the project would come together.

We have been calling this project the mini aggregate project, but it may end up being called the inventory snapshot project. It all deals with the quantities per location and how we are going to track it. Our final solution may end up with a process table that gets a new record when a new data or inventory snapshot is finished. We will then use the current snapshot linked with a well indexed (daily or just today's data) query of the live data transactions. That will give us the inventory quantities per location that we are looking for. It will save tons of time as the system won't have to historically go back over time to get the previous quantities.

Lots of talk about the process tables and basically waking up a built-in process. Have it check the process table and then do the requested action. When done, it makes a record in the process table and then goes back to sleep. Automated tasks and scheduled task stuff.

At the end of the meeting, John and I looked at his site and worked on setting up special top header level links and icons for his account.

Working with Bryan on a code review and clean-up on the invoice due date project. Code sign-off and live testing on the Herbo server. Small tweaks along the way.

Steve and Sean talking about other connections (people) and different networking angles. Steve would really like to see if we could find some adilas power users that are looking for some work. Marisa joined and they started talking more sales and marketing. As a side note, both Sean and Marisa are doing a great job with deployment. Steve would like them to circle back around and help make sure that our other clients are being taken care of (reselling or re-pitching our older clients - reengaging them).

They were talking about news and updates and helping to get the word out and about. They were talking about getting some of the new flyers in a standard spot and making those available to any of our guys/gals who need them. Marisa has been revamping some of the flyers recently. The goal is to help our clients stay up to date and also inform new or potential clients of what we are doing and what we offer.

Those who were on the meeting, we touched base on other projects. I was reviewing a number of documents and looking at a website for a possible merchant processing vendor. I have a meeting later today with a guy from USAePay and NMI. The guy also represents a company called Trinity Payments that actually does the merchant processing. The other two companies are called gateways.

Towards the end of the meeting, Eric jumped on and we pushed up some code to the Herbo server. He needed to push up a file for some live testing.

Emails and reviewing a slide presentation that was sent over by the Herbo guys.

Making tons of cart notes, help file links, and testing the developer testing server on some new validation routines that Wayne was adding to the application.

2/14/23 uploaded the following files to data 1 and created a video.

basic_logo_header.cfm, show_printable_invoice.cfm, plain_logo_header.cfm, black_and_white_printable_invoice.cfm, black_and_white_printable_invoice_body.cfm, mini_invoice_body.cfm, print_limited_invoices_body.cfm, print_simple_invoices_body, print_sumary_invoices_body.cfm, mini_invoice.cfm, print_limited_invoices.cfm, print_simple_invoices.cfm, print_summary_invoices.cfm, printable_invoice.cfm, settings_printable_invoices.cfm, settings_printable_invoices_body.cfm.

12/15/22 money type eXPO to Herbo.  Created update_20221214.cfm and edited update_home.cfm.

11/21/22 1. Show-hide category overrule in show on web & 2. default vender type when adding po.  Edited the following pages: adilasWeb.cfc & add_edit_parts_body.cfm

11/1/22 completed adding hours column to grouped view of time home body (video).  Edited the following pages: time_home_body.cfm & requests_2.cfc

10/28/22 completed auto calculate time dropdown function on add_edit_time.cfm page (video). Edited the following pages.

add_edit_time_body.cfm

add_edit_time_action.cfm

10/27/22 completed Domain Name Replacement project.  A record of the pages changed is in the photo/scans and a link is here.

10/27/22 completed PayPal project.  View video of setup and function here. Edited the following pages:

corp_admin_settings_body.cfm

ecommerce_home.cfm

payment_gateways.cfm

payment_gateways_action.cfm

10/25/22 checked and pushed sub inventory default to active, add 2nd vendor dropdown to duplicate expense page and added currency switch to digitech code.  Made changes on the following pages:

duplicate_expense_receipt.cfm

duplicate_expense_receipt_action.cfm

sub_inventory_templates.cfm

sub_inventory_templates_action.cfm

digitech_payment.cfm

4/22/21: Catch all for misc code issues

Great little meeting between Cory, Steve, and I to go over plans, projects, and priorities. Cory and I started out and then Steve joined us. He was traveling and so he was on the phone and Cory and I were on the GoToMeeting session. The goal was to create a small master list of projects that Mike with Herbo might be interested in. The benefit of that is that we, as the adilas team, get a chance to see what is still needed and what is coming down the pipeline. Progress is made daily, but sometimes it may seem slow if viewed from the outside.

I was writing and recording the notes (on a google doc spreadsheet) and Cory and Steve were commenting and adding their insight and input. We added some notes, moved things around, set priorities, etc. Good session.

As a small side note, progress doesn't always involve getting things all the way done... lots of progress happens along the way. We also spent some time talking about resources, developers, and who can do what. Just because you know what needs to be done, doesn't mean that you can just do it. You still have to balance the resources that are available. That gets tricky sometimes.

This was going to be a special meeting for a specific project but it ended up being an extension of the general touch base on quotes, projects, and plans. Here are few things that I pulled out of the meeting (not necessarily part of any one project, but more overview of subjects).

- Both up and down traffic for enterprise systems. At one time, we were mostly focusing on smaller systems rolling up into a bigger oversight or holding type company. What we are seeing is that the clients really want both directions - roll up, and cascade down (two-way traffic).

- Some of these enterprise type setups will be a cross between a permission and a setting. Who gets to do what and what direction or instructions are needed to make the data flow either up hill or cascade down hill? Interesting.

- Looking at both aggregate systems and transactional systems

- The watchers, feeders, and triggers may come in to play as data (things) rolls up or down, depending on task and flow. The watchers, feeders, and triggers may even become part of the communication process and how and where to track things that are going on.

- We are starting to see the next steps... from transactions up to aggregate and from master back to transactional systems. We don't know everything yet, but patterns are starting to emerge and become more clear. That is awesome. Once we fully understand them, we can then document them and build them.

- Steve was talking about starting at a master vendor list level and then letting those vendors be available in the smaller or sub systems.

- We also talked about master lists for items, photos, part categories, sub inventory templates, etc. Think on three main levels... global (anybody could use), enterprise or master level (top level for a multi-level structure), or the individual corporation or world level.

- Smart software and creating master global lists for known vendors, items, categories, photos, customer types, custom units of measure, time templates, etc. The list keeps going...

- Lots of additional services - that is awesome, but we need to be able to charge for that and/or those services. We just can't do all of them for free. They are a cause and effect type service but also need to be a value add-on service that comes with a price.

- There was some talk about bringing in some of our developers closer to have more control over output and processes. Trying to get away from the wild west type mentality.

- Having Steve help more with project management. That could and is huge. He can and is able to point people in a good direction. He has done that for years. Originally, this was his brain child (meaning adilas as a company).

- On some of the projects, we may increase some of the project bids to help include new settings. That seems to be where everything is going and/or heading. Permissions and settings.

Tim with Herbo met with Steve, Cory, and I to go over his vision of an fully automated enterprise type system. We met and talked, drew pictures, took notes, and chatted about scenarios, requirements, and flow of goods and services as compared with the flow of money, funds, and financials. Lots of top down controls and bottom up mirrors, mapping, and roll call type situations.

Here are some other small notes:

- Holding companies, nesting corporations and locations going down, trickle down effect, rolling up effect.

- Id's becoming standardized through mappings. Helping to automate parts and processes.

- Attaching additional intel, info, or instructions to certain key transactions that start and/or process other steps of the transaction. For example: A new PO is brought in, a sub routine (recipe/build or assembly) is done on the items and then automatically distributed out to sub companies with instructions on how to pay either the holding company or direct to the vendor. All of this done through a single screen where the product is brought in through the master holding company and then distributed to the sub or affiliate corporations. Think of it as a process that gets started and the rest of the process is defined and setup by the info added to the starting piece in that process.

- How the holding company (higher level company or summary or aggregated company) could process things, cascade info down, get values passed back up, and controlling flow of monies, accounts receivables, accounts payables, bank balances, etc. Full control top down or bottom up. Plus, be able to stack the model as needed. It got pretty deep.

- We went over a number of scenarios and talked through flow and possible processes. Just talking and chatting at this point. Build on what we have. We already have PO's tied to vendors, tied to items, tied to locations... what if we could also tell it to distribute those items to other companies and those transactions could be run based on info in the first corporation. Instructions on how to account for things, how to pay for things, or how to differ payments or liabilities. Pretty flexible but with clear instruction on how the transaction or family of transactions needs to work. I like the word family transactions... multiple, with varied yet specific outcomes. Kinda fun.

See attached for one of the drawings that we were doing and talking about.

Meeting to discuss a couple of Herbo projects and funding a developer search and retention.

Meeting with Brandon and Steve to talk about business plans and options.

- We talked about our independent model. Both pros and cons. This is for both developers, designers, and our rep/consultants.

- We are looking for people who want to be part of this model. We really want to focus on those who want to play the game with us.

- Running at max output levels and how to work on efficiency stuff.

- Making those hard decisions. That gets really hard.

- On training... is that really helping right now? In some ways yes, and in some ways no.

- Using the community funded projects to help manage flow of expectations and funding.

- Selling what we have and getting people started at that level. More things could come in later on.

- Seed money and how does all of that work out? We are still trying to figure that out.

- We really need to get some of our guys down to one project and help them get focused and stay focused. That gets really tough.

- We have so many projects... we almost get lost.

- Getting our guys to be responsible and accountable for what they are working on.

- We are spending monies on all kinds of things... which ones are really valuable? There has to be a balance point.

- Sometime it takes a hot plate or major pressure to make you want to change (burning platforms).

- How long does it take to get a new developer? There is a big lead up and a long transition period.

- What if we restructure things a little bit? What would that look like and where would we turn?

- What about a proposal and some planning to get to the hub type model?

- We want to have a small team. We know that we need help. How do we structure that? We love the idea of independents, dependables, and even cofounders. We know at some point we may need to get some employees (keeping it small) but we want to keep it at a manageable level.

- What if we had companies hire their own developers? We help with the project management and meet with them to keep them going and what not. We could really gain there without getting super overwhelmed. As new code comes in, we could virtually cherry pick and harness the work and efforts of other developers. Some of the big companies may really benefit from having their own developers.

- We sub stuff out to Newtek (the server farm). What if we allowed some of the development stuff to be subbed out and virtually use their own developers?

- Play at the wall - this was an API socket dream. Any outside developer could play and code against the virtual wall.

- We may need to step back and help mange the flow vs coding all of the pieces. These other companies could really benefit from what we have to offer. How can we help them get over their pain and get past the next level.

- How do we bill for our time? Talking about Steve and I. Currently, we work for adilas and adilas pays us. If we work for the clients, they really should pay us for our time.

- Question that was asked by the business consultant... What is your exit strategy? What are you doing to get there? Are you looking to get a pay off, reoccurring revenue, a retirement plan, etc., etc. Good questions.

- There is a difference between core development and custom development.

- Talking about developers... What if we figure out their rate (the developer) and then add on to it (for our time) and we then help them charge for it and we then pay out and also make a little bit. Normal add on services.

- Steve was saying - we need to say no more free lunch. We have a viable solution. If you want more, you need to bring your checkbook.

- What about charging for our time? Meetings with Brandon? Meetings with Steve? Meetings with Alan? Meetings with Russell? etc.

- Steve and I really love the dreaming process.

- If we could charge more for the custom development, that would help.

- Sometimes we keep beating our head against the wall until it hurts. At that point, you start looking for options and how to relieve and/or get rid of that pain.

- Making a switch... instead of the business running us we need to start running our business. Steve loves the idea of using technology to run our business and solve our problems. That is awesome.

- Selling our services (custom code, design, and project management) and not just our software.

- Charging for productive hours. This could be for our time, code sign-off, project management, custom code, etc.

- What if we went to more of a controlled open source type model? Going beyond software as a service (SaaS) model and getting into a virtual open source model that is tied into the underlying SaaS model. What does that combo look like or what do you call it?

- We haven't had a project that we couldn't handle yet... Sometimes it takes a lot of time and requires a number of different steps, we've been able to see the steps and then setting up a plan to get there. It takes time, money, talent, and the plan.

- Steve and I want to get out of the middle of the volcano (analogy that we were talking about). There are lots of fertile valleys all around us.

- These companies want to succeed. They really don't want to build out the whole software solution. They just want it to work.

- Making a scalable model. We even talked about a new virtual testing environment for these companies.

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

Talk about the automated cross corp stuff and aggregated totals being pushed between corps (herbo project - see email).

We need to talk about our plans with the product lab.

On a GoToMeeting session with Cory and Tim from Herbo. There was also another lady on the call, Jennifer. They have a project that deals with an auto roll-up between mother/daughter corporations. Somewhat of an aggregated system or enterprise system of sorts. The holding company needs and/or wants certain cross corp actions to be automated between the different systems. There is also another major piece that deals with reporting some of those same numbers and values back to the holding corporation (mother system).

Most of the meeting was going over ideas and making a small plan. As part of the plan, Cory was going to go over things screen by screen and pass them over to me. See attached for all of the scans and my notes. I worked on my notes on 12/12/19.

Looking at some small bugs with the cross corp invoice to PO functionality.

Met up with Bryan on a couple of projects. Some of the questions were quick and some we actually looked at some code and made plans. Mostly a general work session.

This idea came up when trying to figure out how to make the sg&a flow easier for Herbo. This is a great way to help with that flow, as you could duplicate, and then switch out parts that weren't relevant.

Code review with Bryan. He is working on a project to add in last modified date/time flags to both parent and sub inventory. He is also creating a new method that outside parties may call through the adilas API sockets and get inventory changes based on the last modified date flag. This allows us to only pass data that has been changed to limit needs to sync up all records when only a few things are actually changing. Less of a load in the sync process.

Herbo potential client (Bob T) wanted the liability numbers to be added together in the report. He also wanted Herbo to create a 941 and 940 report.

Need a $2,000 contribution to start this project

Herbo potential client is interested in this- Meredith asked what it would entail to get this. They would pass this expense on to client.
Quarterly Contribution Return & Report of Wages) - California DE 9 Form. ... Each quarter, California employers are required to complete a Quarterly Contribution Return and Report of Wages (DE 9). It is used to reconcile California payroll tax payments and the total subject wages reported for the quarter. This form is similar to 941 & 940, although it required by State of California.

shari answered....
I would say yes, this would more than likely be a "Custom Code" Report that could possibly be built - I would need to once again, reach out to the Developers for this as well.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Bryan and I met up and worked on a few code changes for the complex label builder. This page simulates a pre-set option for mini conversion. No real conversion take place, but it kicks out barcode and QR code labels that make it look like a mini conversion took place. The page allows for a single product batch to be split into smaller pieces. The magic behind this page is that it only splits things for the labels, it technically doesn't really split it, but according to the labels, it is split up. Anyways a few small changes.

We also talked briefly about a new merchant processing gateway and interfacing with Square as the gateway merchant processing option.

Meeting with Bryan to push up some new code on the invoice sub inventory reports and exports. We made some changes, did some testing, and then did some more testing and light tweaking. Eventually, Bryan found a small error that fixed the issue. It was one misplaced if statement. Funny how small things can effect the whole. New code has been pushed up and tested. All is well.

Jim Dougal (tax atterney in California and works with differnet CPA's) jumped on and had a few questions for Steve. We also had Pat Dolan join us. Pat has been helping out Adilas with sales and customer relationships. We also had Timothy Lyons (lead IT and tech for Herbo) join in the meeting. The subject of the meeting was dealing with pricing, technology, and how to move forward.

1. Price piece - discussion between Jim and Steve

2. 3rd party solution - Herbo ecommerce solution - We want to allow all of the customers access to this option. Having said that, we need a 3rd party solution switch that would allow for an actual switch (on/off).

3. Integrating with Square (payment processing) - They are in the process of finishing up the contract between Herbo and Square. Steve has already talked with Bryan Dayton (adilas developer) for the Square integration.

4. Other - On the server side, we briefly talked about dedicated servers and how we can proceed. We could commission physical dedicated boxes or virtual cloud clusters. Along with that, we talked about custom URL's and/or domain names. There were some questions about when does a company need a dedicated box vs a shared stack or semi-dedicated server model. What are the thresholds and capacity levels? How many transactions are we looking at per company, per server, per group?

Looking forward on AWS (amazon web services)… we get away from a physical dedicated server but it gets into a dedicated stack and/or dedicated cluster. The AWS environment allows for virtual load balancing and then automatically adding and subtracting dynamic power to help with the processing.

There were some conversations about splitting up the bus and getting each company on its own corp-specific database vs a shared database. As we get bigger and bigger, we will need to split things apart to make them faster and more efficient. Having said that, that also increases the need for back-to-back API sockets and data exchange between clients and clients and corporations and corporations. As things grow, we end up seeing lots of cross-corp type connections and functionality.

Tim had a couple questions:

1. Where are we going to host things? We would like to setup a meeting with our current hosting provider. Tim would really like to be in on this conversation. We, from the adilas side, need to get both Wayne and Alan involved in our decisions. As a side note, we have a physical dedicated environment that works and can work in the future. All of the AWS and/or dynamic cloud interfaces are in the process... but we don't have a physical fully working environment.

Steve was talking about once we get things settled, we can still jump up to bigger servers, clusters, and even migrating data and systems to the more robust virtual environment. Lots of options. There may even be some pricing options such as economy level, mid level, and deluxe type levels. Some of that may come back to where are things hosted and what are the environments that get setup.

Tim was talking about umbrellas and having dedicated and shared servers underneath the main umbrellas. Basically, a way to stack the systems. In a way, we simulate a hosting company by sub dividing our IT assets as needed.

- What are the timelines for AWS or Newtek?

- There are some discount options for pre-buying and/or pre-paying for servers.

- There were some talks about charging for hosting as a pass-through type charge. Currently, if our clients are on a shared type environment, we only charge a monthly fee, similar to a ski lift (pay for a seat and the chair is just spinning). However, if we have a dedicated client, we charge a server fee and then the monthly within the dedicated server. Kinda like a private chair lift per server. Adding in some options to help do normal charges and then also help the clients pay for what they are using (being able to track the stats and real usage per client). They were also talking about watching and monitoring each box and getting the best ROI (return on investment) per server. Basically, the standard fee structure that we currently use may need to change to help deal with pass-through and new and upcoming costs.

2. What about code branching? They, Herbo, would like to offer a specific version (branch of code) and then be able to mix and blend and cross merge code as needed. If they develop things, we could merge them in, if we develop things, they could merge them in. They would be separate branches. We would like to have another meeting between Wayne, Alan, Tim, Steve, and others.

- We briefly talked about themes (separate internal sub folders) or are we at an API socket level (external data sharing) where we are just exchanging raw data back and forth. The difference is, it built internally or built externally and just played at the API socket level (play at the wall). If they play that way, external API sockets, they could use AJAX and just push and pull data through the API sockets. If they work on the API socket level, they could code it any way they want with any look and feel and any backend coding languages.

- Steve kept bringing it back to use what exists and what works and we'll go from there.

Working with Bryan to get some new code pushed up to all servers and light code review.

Bryan was working on replacing certain images and dynamic banners for white labeling pages. We ended up getting into some deeper CSS stuff and forcing the changes through the CSS and taking certain pieces and making it become in-line CSS vs a CSS include file. After that, I helped with some other tech support things.

Pushed and merged in some code with Bryan. We did some session clean-up from some temp session variables that were set yesterday. He had some questions about QR codes and we also spent some time going over merchant processing and how and what we do (on our side) to help our clients get setup.

This is just a note for the developers. We allow a corporation to use an alias corp key to login for a certain company and/or corporation. Currently, out in the API socket land, we only allow the older corp key value, which is three letters of the corporation name, a dash, and the corporation id number. Example: Pla-0053 or Mor-0003 or Cor-0263.

The aliases are much more human readable. These could be values such as: demo, herbo, adilas, expo, 710Labs, etc.

It would be nice if the API sockets could handle both versions. That shouldn't take too long, but it may really help.

Meeting with Bryan. We did some merging in of some white label variable changes. That will help as we go forward. We talked about online reservations and possibly splitting a bill/ticket with a client who would like that functionality. I would love to add that to our offerings. We also did some light debugging on some QR codes and stuff for some custom labels. Good session.

Working with Bryan to push up some new white label code for Herbo. Lots of variables and switching out names and contact info. Bryan is doing a great job. I recommended that he go in and change some variable names to help them be more  human readable. Currently, they were things like whiteLabelVariable2, whiteLabelVariable3, etc. vs a real well defined variable like whiteLabelEmailAddress or whiteLabelBusinessName, etc. Good stuff. Progress is being made.

Helped Bryan get a few new files merged in and uploaded. We had to fix a couple of merge conflicts, but that process went pretty smooth. We pushed up new files and Bryan did some testing.

Tim Lyons from Herbo was online with Steve and I. His goal in meeting with us to get to a working process. He was talking about sub assemblies (recipe/builds) and then building and mixing a number of those pieces. He would like to add the operational costs as he goes through the process.

Steve was talking about how adilas tracks all of the internal production stuff. He is really working hard on the production stuff. Just like cultivation, he is out pioneering pieces, and then he will turn it over to someone else to really tweak it out. Fun process.

Steve showed a small demo on his existing production home page. He was doing parent/child inventory tracking, extractions, internal build, RFID tags, unique batches, subs, sub attributes, etc. He was talking about elements of time, time based reporting, phases, sub locations, etc. It got into alerts, lots of time based reports, stages, phases, steps, etc. It got into concepts and tools and what is pre-programmed and what could be configured. Steve was talking about transfer invoices, external reference, combining quantities, and all kinds of good stuff. His demo was using his local environment. Lots of talking back and forth. Good conversation.

We were showing 5 decimals of accuracy, distributing cost of goods sold, pulling and pushing quantities, etc. Steve was bouncing between parents, child inventory, elements of time, PO's, category level options, etc. It got into parent attributes, aggregated recipe/builds, processes, SGA costs, distributed accounting, distribution models, trucks, product transfers, chain of custody, detailed tracking, GPS, Google maps, custom stuff, and all kinds of crazy details.

One of the next steps is going to be setting up parent inventory items and then figuring out the flow process.

Towards the end, Steve had to leave. Tim and I jumped into some other corporations and looked around at real data. We looked at corp-specific flow, a corporation with a number of sub locations and sub entities, and some of the automated reporting that is available for both cross-corp or internal reporting. We also looked at usage reports, quick sales reports, switching between different corps, and using the quick search to get around.

Bryan and I pushed and merged in some code for Herbo and Dutchie - 3rd party solutions. We also started looking into a quote line item search. Bryan took an advanced invoice line item method and was trying to adapt it for quote line items. They are very similar, but it has a few other tweaks that make it unique.

I met with Bryan and we went over 3 different projects. They were dealing with how to treat the Herbo whitelabel  stuff, options for filtering sub inventory attributes, and Full Circle API socket integration and some strategy on that project.

Meeting with Mike Rountree, Jim Dougal, Tim Lyons, Gannon, Steve Berkenkotter, and Brandon Moore - Team Herbo

- Looking at options to help do a white label and see what market share they could get to and/or grab

- From seed (starting) clear out to general ledger (full backend/frontend accounting and financials)

- Working with Cory as an adilas rep/consultant

- There are three different things that need to be implemented together

- They have clients in the CBD category - raw material providers, internal manufacturing, packing, distributing, retail, lots of supply chain things, marketing and sales

- They have a distribution category

- They have a retail category

- How do we scope a project? You start on paper. You make a plan, you know the tools that exists, you see what matches, what doesn't, where do you start, and what are the priorities? It comes back to a plan. This could be a flow chart, diagrams, whitepapers, other documentation. It really helps if you have someone who knows Adilas and what tools are available and what tools can flex and change by default. That really helps.

- Some of the tools are different corporations (different worlds), multiple locations within your worlds, what key players (12 main players) play into that model, etc. Steve was also talking about parent/child inventory relationships. Lots of mixing and blending between the things.

- Builds, transfers, phases, locations, sub locations, etc.

- White labeling allows for custom pages and custom code - We have white label theme levels (multi or group level) as well as custom black box code (per corporation or per world). We can customize almost anything. This includes show, hide, look and feel, logic, toggle switches, flow process, requirements, validation, reporting, ect. We use the phrase you dream it up, we'll help you wire it up.

- Cory is great consultant that really knows Adilas. At some point, you will need someone on your teams that really plays the other part of the puzzle. You have to know the client and the solution. Then you mix them together to get results.

- Bring up questions... they aren't good or bad, they are just questions. Get them out there and then see what is needed (easy, medium, more complex)

- Herbo will create some diagrams of what they need and how they want things to play (processes) - Here is the world and here is how the players need to interact

- Training and content - Who owns what, who builds what, who does what? Also, what about passing training and content back and forth? Adilas is willing to provide any thing that we have through database exports, Excel, CSV, XML, JSON.

- Tim had some great questions on the backend stack and server climate. We recommended that he get with Wayne Andersen to get all of the details. Tim has a vast knowledge of backend operations and servers.

- Herbo will be working on some flow charts, processes, etc. They will have a virtual meeting of the minds and making any plans that are possible.

- On the Adilas side, Steve will be working with Cory to help with any deeper consulting info. Steve is a master planner and knows the system front to back and what is possible.