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.

Phone call with Calvin about Emerald Fields, Gmext, and possible Mac version of the bulk FTP uploader tool. We also chatted about some of his other tools. They have been a huge help and we, at adilas, use them every day.

Wayne, John, Cory, and I on a server meeting. We started out with going over some of the new processes for Emerald Fields and their custom roll-up database. Basically, they have showed us certain reports that they use and want to use for some of their analytics. We then build them some custom data extracts to populate new database tables with the correct data (basically a virtual roll-up type model). The roll-up takes daily transactions and pulls some other data (table joins) and logic to store the data in a very usable state. This process is called E.T.L. (extract, transform, and load). Basically, some custom aggregated data just for them. It is setup on a schedule and pulls data from date range and then adds or updates the transformed data as needed. The guys at Emerald Fields are then able to have full access to that custom (non live) database.

Cory had some questions about AWS (amazon web services) and what pieces we are building and using. She, Cory, and the others were also talking about adilas phones and some of the flow and logic there. There is some maintenance that is needed.

The value of maintenance and upkeeping code bases and features. We are striving to be proactive vs just fighting fires that are lit under us. Those things tend to get more of a priority (aka pain or need).

New changes for Emerald Fields and their custom data extract project. Wayne and I were adding some new logic to either add or update, based on the records that are in their reporting system (custom extra database). Just for fun, the new logic looks at the history table, pulls a list of invoice numbers that have been modified in a certain date range and then pulls a special combination and extraction query based on only the invoices that have had changes within the rolling date range. Nothing too major, but some new logic on their custom data extraction process.

Server meeting with Cory, John, Wayne, and Brandon. We talked about a custom data extract for Emerald Fields. They wanted some light tweaks to the data that we are pulling for them. We then switched gears and talked about auto deploy from bit bucket to our production servers. The goal is to deploy from master or update the production boxes with master once a day. The script has been working great until bit bucket made some changes to their defaults. We will get it figured out and set it back up again.

We went over some database group by options and global variables. We will make sure all of the main database servers are setup in the same way and open to allow a looser group by criteria or requests. Cory asked for some follow-up on some of the other projects. Still moving forward there.

At the end, just Cory and I were still on the meeting. We got into talking about subs within permissions and how some of the permissions almost need to break into sub levels, dealing with what functions, views, and options each permission allows. Lots of custom needs and almost crazy levels of micro permissions (sub permissions based on functions within a single permission).

Quite a few of us on the server meeting this morning. I had a small list to go over with Wayne and we started there. My list was:

- The new Emerald Fields server and custom database

- Training for John - that is going great and we are very happy there

- Talking about the developer's server and making it more into a testing environment as needed - a server that is in total flex - lots of great ideas and conversation here

- Corp-wide settings and carving up the bigger tables. We also got into talking about switching between Application.cfm (current) and Application.cfc (where we are headed). Wayne and John are going to be looking deeper and working on this in the next couple of weeks.

- We need access to some Adobe XD files that we put on the content server. They exist, but we can't download them via a direct URL currently.

- More great talks about the testing and developer's server

- We would like to setup a meeting with Russell, Chuck, John, and others to go over Bootstrap 3, 4, and 5 - We would also like to look at options for other data tables that we may want to use. When we do this, we will eventually want to let Dustin, Bryan, Alan, Eric, and Steve know about decisions and direction.

- John reported to Cory on the adilas phones product and progress there

- John went over some of the discount engine stuff and showed us some of his new plans - light question and answer session between John and Cory

Good meeting and making progress. Good stuff.

Quite a few of us on the server meeting today. We had Wayne, John, Steve, Cory, Shari O., and myself. We talked about the transition between Newtek and Hostek and how that is going. We are almost fully transferred over to the Hostek side, as far as servers. We still have a few lingering accounts and servers on the Newtek side. Shari O. has negotiated some hard stop dates on the Newtek side for certain servers and contracts. Light follow-up on dates and being ready for those hard stop dates.

Wayne and I talked about the Emerald Fields custom data extract project. Wayne is almost done with that project. I prepped things and got the queries all tweaked out and the main logic done, then Wayne is going in turning those queries and custom logic into new database tables on a totally different database. That involved some timing, scheduling, and custom looping over some data logic functions. This particular project is not just data, it is full on ETL (extract, transform, and load) type changes to the data. Some of them require multiple queries and logic to mesh and blend the pieces. Making great progress, the final touches should be applied in the next couple of days.

John and I asked Wayne about Adobe XD files and the content server not allowing them to be downloaded and/or rendered. I sent an email to Wayne with the URL link and the error message that we were getting. He will look in to it.

After that, we talked about the internal email speed, grey listing, and possibilities of doing our own custom email server and spinning up a server, just for our adilas.biz emails. Currently, we are using Newtek servers and have to use API sockets to send emails from all of the other servers. The last topic of the day was getting Wayne and John hooked up to do more cross training and sharing of knowledge. At the end, Wayne was having fun sharing info about his solar panels and the savings that he is getting, there in Portugal at his house. Kinda fun.

Working on getting projects finished up and off my plate. Working on the custom data extract project for sub inventory for Emerald Fields. This sub inventory extract required some data flip flopping. We pulled a query, pulled a number of other supporting queries, built an array of structures (objects), looped over the data, manipulated and filtered the data, and then pushed the results back into a query object to show and display. Kinda like data gymnastics.

Danny, Sean, and John were on the morning meeting. We checked in and chatted for a bit. Danny and Sean were talking about email templates and using some of the new things that Danny has setup and created. After that, we all went on mute and just started working on our own projects. I went back to finishing up the custom data extraction project for Emerald Fields (a client). The project involves going and flip flopping between different data types to get a complex sub inventory report to pull and be formatted correctly.

Server meeting. Wayne, Cory, John, Steve, Shari O., and I were all on the meeting. Lots of back and forth with small questions from each person/party. Some new directions were given and requests made. Wayne will be ordering some new boxes for a client. We then went around and checked on the status of different projects. We are hoping to get back to the developer's notebook box (developer box) and also making some plans about the Emerald Fields custom data extraction project.

After the server meeting ended, Cory stayed on and was asking some questions on the new payroll changes. We made a small list of bugs and setup another meeting to go over things and add some loving to the new pages. Nothing huge, just some tweaks and refinements.

Working on the sub inventory custom data extract for Emerald Fields.

Working on Emerald Fields and prepping for an email update to the client.

Shannon joined and we started working on the adilas core concepts. We were working on decisions, choices, consequences (cause and effect), and accountability. See attached for where we are working.

Email out to the client with an update on the custom data extract project for Emerald Fields. Other emails.

Quick merge for John on some balance sheet font changes and new social icons for the ecommerce footers.

Cory joined and she and Steve were talking about different parts and pieces. I reported on the Emerald Fields custom data extract project. We talked about a few other projects as well. Lots of good back and forth with questions and replies from both Steve and I. Cory was reporting on some of her news and updates that she has been working on. Some of them (news and updates) get pretty deep as well.

Working on the custom data extracts for Emerald Fields. Advanced customer searches with lots of SQL if statements to flip flop values around to be more human readable.

Back on the Emerald Fields custom data queries and custom data extract project.

Working on the database queries and prep work for the custom data extract for Emerald Fields.

Cory, Steve, and I going over projects. We spent most of our time working on two projects. One was some special data mapping and exports for Emerald Fields and the payment processing project for the bill recycler and coin recycler. I took some extra notes on each project and have them saved on my local computer under folders for each client.

Small side note, some of the our old ways of doing stuff are starting to bite us in the rear. Things like letting our independents or reps do their own marketing, using the adilas name, separate branding, etc. Not the end of the world, but it is making it more difficult to figure out who is building, supporting, and selling what. We are currently in a phase where we are trying to bring more of those pieces (services and hardware) back under the main adilas umbrella. It may take some time, however we are making great progress.

John, Alan, Cory, and I got on a small weekly update. John and Cory were touching base on projects and priorities. After that, Alan and Cory touched base on some projects. Alan is working on sub inventory, tiered pricing, and had a few questions about sales tax on subs and tiered pricing. Good reports from both of them (John and Alan).

After the other guys left, Cory and I spent some time going over projects, code sign-off procedures, next steps, and cause and effect chains if there are errors or issues. We touched base on the paypod project scope and also the custom data push for Emerald Fields and custom database tables that they need.

Both Wayne and John were on the meeting going over server speeds and stats. Wayne was showing some logs and pages. Steve and Wayne were looking at logs and server availability and usage. Some of the clients keep growing and are putting more and more demands on the servers. Looking at pure traffic. They got into comparing usage, stats, CPU's, RAM memory, connections, data bandwidth, for some of the bigger boxes. We decided to upgrade a few of the boxes with more specs and options.

Servers can only go so far. If we can streamline the code, it helps way more than just adding new CPU's and more server memory (RAM). That also takes time though. We may have to come up with a balance.

Switching to Emerald Fields and their custom data dumps. They have tons of data but not knowing all of the data relationships. Too much data and they want us to help minimize those technical and almost back-end level needs. Steve and Cory met with Josh on 7/8 and discussed what he needs. As we talked about it, we came up with some thoughts. See below:

- Lots of our API sockets deal with simple data calls and showing that data. The Emerald Fields API sockets are more of deeper look into the database as a whole vs just simple pointed API sockets.

- We need to plan, quote it, break it into pieces, and then follow-up on the smaller pieces. Sometime, too big of a bite is harmful.

- Wayne said - it is like they need a custom report, but instead of giving them a finished report, we are building them new database customer report tables - where they can then pull and filter data from a more raw type source. Interesting view. We build custom reports all the time. This one just happens to be a custom view or custom dataset, in database mode or version, vs a normal custom report.

We met up and talked about invoices, invoice line items, tables, joins, and data connections. Pretty deep conversation at a techy level. They are going to do some testing on smaller datasets to make sure that they are getting the raw data that they need. Once we validate that, we will go to the next step. As a back-up, they may need us to produce some custom exports and data dumps to help load their outside remote database (extra database for analytics). Working through the process.

As part of the meeting, we did some explaining, drawing, training, and light mapping. I sent them copies of two of the existing methods that we use calculate invoice line totals and sales and profit reports. Hopefully, that will help.

Wayne, Steve, and I jumped on a meeting with Emerald Fields. There was two guys on from Emeralds Fields with us. They are looking to get some of their data out to a separate database to run their own analytics on that data (not hurting the production database). This process is already somewhat underway, this was just a meeting to work out some further details and plans. Somewhat of a question and answer session. See attached for some notes.

3/8/21: Per meeting today.

Multiple people on the meeting. I took a bunch of notes. They are on my local drive. They are called "emerald_fields_meeting.txt". Here are a few quick highlights:

- They are wanting to get into their own data warehousing - they will be mixing data from adilas and other vendors all under one roof for faster reports and analytics

- Everyone is heading into BI - Business Intelligence type levels - quick fast totals, counts, sums, and averages

- Lots of talk about outside 3rd parties and pros and cons of some of those services

- Emerald Fields does an awesome job and has some really tight business process - virtual poster child levels

- Steve was proposing some consultation from one of our adilas developers

- Push and pull type technologies

- Special discounts with limits and automating processes and custom discount engines

- Looking to the future and building new tools and features as needed

- Steve was pitching them some of the new things that are done and/or coming off the press - he's a good salesman and can pitch a vision

Spring Big Meeting

Online team meeting to cover security, adilas API sockets, black box code, and upcoming white label options. We started out with a number of reports by the different guys.

/////////////////// here are some of the quick reports by the developers:

- Eric - Fixing custom carts and working on the pricing engines. Lots of custom one-off's. Working on loyalty points and special tracking accounts.

- Russell - News and updates - new API socket feeds and such. WordPress site and other look and feel things.

- Wayne - Refactoring code, testing based design, and underlying framework. QuickBooks integration stuff - imports and exports. As a side note, Bryan has had many customers asking about similar type features. Wayne is also working on other database stuff and migration.

- Bryan - White label stuff for outside parties. Tons of custom projects.

- Calvin - Hybrid API to Windows desktop app. Custom PDF labels and printing.

- Alan - Helping Steve with Metrc API stuff. Working on tons of tax and in-line discounts. Helping Brandon with other projects.

- Danny - Generating sales - Props to the developers who are creating the functionality. He pitches the idea that the developers are accessible. Custom labels.

- Shawn - Helping with payroll, federal withholdings, state withholdings, and county level withholdings.

- Brandon - Helping the developers and doing small projects. Merging code and maintenance stuff.

- Steve - Grateful for the help with the Metrc API stuff. Working on phases and sub locations. Steering the ship. New approval levels on other state traceability systems.

//////////////////// meeting notes:

- Talking about the Adilas API and system - dealing with security. Facebook was brought before the senate due to a breach. They allowed an outside company to come in and develop an app for Facebook (basically a 3rd party solution). The problem was... what does that outside service actually do and have access to? The app ended up doing some internal data mining and then sold that data.

- We want our users to be successful - we want to enable them but we also need to protect them.

- Small switch in the sales focus. The older model was one-by-one and dealing with reps and consultants. We are seeing more of a switch to bigger companies that virtually take over the sales force and are wanting to sell our product more as a white label type application. Lots of mixing and blending of products and services. They are allowed to provide all of the supporting services that support our product.

- Ideas from the group about security:

- Russell said, bold it or make it red and let them know what they are exposing (meaning the API sockets). Allow the agreements between the parties... we are part of it, but we let them create the relationships between themselves.

- Steve said, we don't want to make our users work harder... to turn things on, but we do want to make sure that the clients know what they are getting in to. Example of what happened with back in 2015 with Hypur and Emerald Fields (two of our clients). Basically, the 3rd party solution (Hypur) got turned on and then it kept growing (what Hypur was doing and/or requiring) and eventually was trying to get at more sensitive sales and inventory level stuff. Eventually the client was super upset due to the lack of disclosure of what was going on and what was open/available to the outside party.

- We are seeing that most of these 3rd parties and white label people tend to expand what they are asking for. Bryan is seeing that more and more auditing type levels are wanted by these 3rd parties. We have also had a number of questions about different server levels and certifications. Our clients want to make sure that their data is safe and secure.

- Russell brought up the point and the difference between a couple of if statements on a page vs a full on white label type solution. We need to develop and standardize that white label type path. They need to pay for it and also be able to help maintain it (meaning the white label company). Taking things clear out to a white label theme (actual files and folders). White labeling is basically bulk black boxing but you can still use any of the classic pieces. We drew some small diagrams and talked about possible options.

- Shawn chimed in and started talking about building a city. Basically, kinda like urban sprawl or older parts of a bigger city - no plan, no alleys, buildings touch other buildings, and not a well planned layout.

- We need to stay on top of things. Keeping code and the database structure up to date. If we do this... it will help us be more efficient and save us time.

- Eric chimed in and said "process" is the solution vs simple communication only. Basically, as we are growing, we need to get to a more standardized process of development. We have a huge landscape to consider. Lots of moving pieces. Ultimately we need to adopt a process oriented approach. Wayne agrees. Different levels within software development. From critical and saving lives to making sure that we have solid code and pieces. It gets into speed and flexibility against slow and more stable type processes. Maturity in software development is sometimes measured in how well you implement internal processes. Eric thinks this is the next step we need to take as a company.

- Danny has been threatened... :) He was talking about levels that people rely on our solution and how all of that plays in and such.

- Small little analogy of the little red hen... everybody wants it but they may or may not want to participate. In real life, things cost money and take time to get done.

- From Brandon - Let's make this thing what we want it to be!

- Any core elements need to be merged into the master branch. This is required.

- Steve was saying... be on the lookout for companies and what they are wanting. That could help us know how to play with them... Maybe look deeper than the current project. We really need to protect our client's data. He was talking about the adilas market (adilas world) and also the 3rd party solutions page. We need to point outside parties to come through the main monitored pathways. We need to keep those sections updated and let the clients know what is being opened/exposed. Very important.

- The value of oversight and/or having someone to help watch them and help them out. This seems to be new trend. If that is the case, we need to make sure that they know what is going on and what is opened and what is closed (talking about data).

- Brandon will write up some super basic pieces of what our current rules and processes are.

- Alan pitched the idea... Local, live, and then into production - talking about a testing server that will be coming this year.

We ended the meeting and allowed people to jump off the meeting. We basically said we would be doing this again (meaning a team meeting) and would get them some info and instructions.

/////////////////////// after the meeting

- Alan and Steve were talking about breaking up code into logical pieces and making the road map more object oriented. Basically, organizing the use and flow of data - making the map for others to follow. Currently, we are just using Brandon's memory to help guide people to the right spot. We need a better road map that others can follow.

- They got into some technical conversations about threads, processes, RAM memory, read/write times, etc.

- Part of our process needs to be setting up and monitoring the servers (actual eyes and reports or dashboards). We need more information, stats, what pages are being used, what processes are running, and what data is being accessed and how often?

- We talked about caching, traffic, threads, database transactions, data mining, and changing from transactional data to more of an aggregated type model (summing up things and organizing things for reporting features). We need to keep allowing day to day operations but also need to optimize things for reports, exports, and other bulk reporting features.

- Alan and Steve were talking about the challenges of using outside API's and syncing up data between systems. Lots of options, but also lots of moving pieces.

- On the API sockets... We need to provide good samples of how to call things and also good response type data. It is really nice if we can format things as well. It just makes it easier for our guys and also outside developers.