Adilas.biz Developer's Notebook Homepage

Search The Adilas.biz Developer's Notebook
Time Period:	Daily (enter the day you want to see) Monthly Custom Date Range to
Template Filter:
Color Code:
General Text Filter:	(use a plus "+" sign to separate search terms. ex: jack+jill+hill)
Sort Value:

Adilas.biz Developer's Notebook Report - All to All - (311)
Showing 150 of 311 Page 1 of 3 :: Go to page ::
Photos	Time Id	Color	Title/Caption	Start Date	Notes
	Adi 406		Invoices - Take off the contact info captions	7/26/2012	We got a suggestion from Shari O. that maybe we could simplify the salesperson contact info on the bottom of both quotes and invoices. She recommended that we take off the field captions that tells what the data is. For example: Sales Rep: John Doe - maybe just put John Doe. Just an idea...

	AU 1803		Daily Ideas	9/28/2013	Random notes – Woke up 3:30am and couldn’t sleep: - Use graphic mock-ups and layouts. No code is required and a picture tells a thousand words. Super-fast and it creates a model or goal to build towards. - Make graphic flow of different pieces. This could even be simple flow charts. - Use existing pages as default icons. - Get notebooks to my sister and get caught up on what is in the notebooks. - Help Steve push the adilas world to a real usable level. - Maybe think of small trial periods for approved persons. - I need to do more teaching and training. This could be in ColdFusion, adilas, or adilas sales and service. - Check out the operations seminar at USU. What a great resource. - I need to play as a team instead of just doing things all by myself. - Contact my brother and work with him on some of his commercial ideas and what not. - Get creative on funding and money flow. - Figure out new projects, scopes, and budgets. - Go back and review notes from 12/24/12 (December of 2012). Lots of good notes and ideas. - Figure out what is promised as far as tools and features. - Schedule the next training event. - Post the first round of the user guide. - Recruit internally. - Put Shari on task with the user guide. - Adilas university may end up being a non-profit. Until then, go ahead and just run it as it. We can transition later. - Get the database ready to be duplicated. - Finish up tools and features for eCommerce. - Get the content server up and online by end of 4th quarter 2013. - Organized and prepare the next whole level. Take adilas to the platform level. This is us dreaming to a super high level. Reach and stretch a bit. As a note, plan that this next level or model, at some future point, will also break and become a stepping stone. Include: custom css, layout, design, destinations, flow, tables, code, choices, in-line custom code, API options, pre-built templates, pattern after elements of time with build your own types and apply functions as needed. Be able to create your own flow and check points. Think of holding areas, checkpoints, permissions, and flow. We also need to add correct data mapping back to states and status and holding areas. Track the full life cycle of the items and transactions. - You dream it up – we’ll wire it up! - Show flow charts. This could be recommended flow, options, and special circumstances. - Use other people’s money to fund the projects. - We bring experience and vision to the table. - We will build on what we have. - The new platform level may need steps, phases, and different levels. - We at adilas need to follow our own advice and dream it up! - Document it, sketch it out, draw it up, and go to it. - Make visual homepages with icons and sections. - Get the notebook caught up… It takes extra effort to do things twice. Writing and sketching and then rewriting. - We have been planning this upgrade or next level for years. This doesn’t just come out of nowhere. - Think “platform”! Think “world building”! Think “in-line custom code”! - Make things consumable! - Plan the education and training from the get go or right from the start. This can’t be an afterthought. You almost plan it from the beginning and let it lead development. Then it truly becomes marketing. - The project for the developer’s notebook is very important. We have to share and communicate what is going on. This notebook is a huge part of our communication and direction. - Plan it out, seek help, use other people’s money to fund the projects. - Our plan is to share and seek protection out in the open by sharing. We also want to focus on the abundance model. Not only is there enough to go around, this model deals with more than money and business. My sister said the other day, this model also deals with people, skills, ideas, talents, drive, etc. Her saying that really helped my open my mind and think differently. -Start with education and an open API (application programming interface) or open source code. Those are two huge keys that we currently have shadows of but are lacking the full implantation of those features. - In order to get where we are going… You have to have some time in the game. - Education needs to be brought up to the marketing level. -We may end up leap frogging ourselves. That would be kind of fun. - Build to eliminate bottle necks in flow, processes, code, education, marketing, people, and other pivotal points. - We want to get marketing involved from the ground floor level. - On a personal note, I’ve done a number of projects and tried to market after the fact. That process is pretty tough. We need to see the vision and fund the projects with the vision. Self-funding is very difficult. - Plan for mobile and new technology! - Plan for data production and duplication! - Plan for snap-on and bolt-on additional features. It would be super cool if some of the code and features already anticipated external connections. Think application flex grid level. - Depending on our goals… we might need to start a whole new company or at least another arm of the current company. - Talking about new or extending business can be scary. It feels big! But, we’ve done this before and , most likely, we’ll do it again. - What about timing for this? That is still kind of a big unknown. - I am sad now. Sitting here thinking about the size of the project that we are currently in and thinking how big this current proposal is. In order to build, the weight, load, and wealth must be spread out. And then I start thinking... Build on what you have! And, the mode softens. I need to remember that saying. - Use adilas' existing base and experience to market the next level of growth. Again, build on what you have! - As an idea... I know of a company with a dream and they are daily building towards it. Would you like to hear more or become a part of that vision and dream? The company is called "adilas.biz". Come and check it out! - The taboo word is not "break" or "break it". The real taboo word is "eventually". This came from a small conversation during one of the lunch breaks during the Logan September adilas training course. - Choose your flavors (like an ice cream shop). - Pick your tools (like a tool shed or toolbox). - Skin your engine (like a vehicle). - Build your world (like worlds of a solar system). - This might be a fun part of the adilas formula flyer. Maybe replace the results section of the flyer. - Sample sketch of this idea (see photo gallery, sketch includes: Choose your flavor (ice cream treats), Pick your tools (tools for building), Skin your engine (different vehicles), Build your world (different worlds and planets), adilas logo in the middle.

	Shop 1541		Go back through and redefine the system defaults	6/24/2016	We need to circle back around and redefine the system defaults. This could be the tax categories for discounts, corp-wide settings, defaults, pre-sets, etc. It has been years since we were in there. This would really help to make it so that our customers and clients could run faster right out of the gates. We want our system to be as easy to use as possible. Steve, Shannon, & Shari O. would be great people to get involved in this project and redefining session.

	Shop 1805		Working with Russell	9/9/2016	On a Zoom meeting with Russell. He started out by making some proposals about doing a couple rounds on an Affiliate Program of sorts. The interesting twist was using the second salesperson slot on the invoice as a quick fix and almost instant tie-in (just some minor tweaks). We then talked about how we may need both payee/user pieces as well as customer/client pieces. His idea to start on the payee/user side might actually be very helpful in some ways. That might allow for a number of pre-built pieces to be used rather quickly because all existing code is based off of payee/users vs. customer/clients. Eventually, we'll need lots of customer stuff, invoice stuff, parts and general item stuff, promotion codes, special discounts, and even points and redemption type stuff. This could tie into expense/receipts and other special reports. I see the flex grid tie-ins section written all over this particular project as well as other main key players. Russell also proposed that we start into the black box project on the main secure site and allow for themes and templates just like in the ecommerce land. Russell has done a great job in ecommerce and is looking to make similar type moves inside the system for the main secured environment. He really wants to make some mobile ready pages and apps. Good stuff and fun direction. I had to help on a tech support call for about 20+ minutes to help Shari O. of adilas with inter corp settings between physical boxes (clusters and solar systems). We got it all figured out and got her going on her way. After that Russell and I worked on some stock/unit settings for ecommerce. We are trying to make it so that users can modify and setup default photos for sub types, new aliases, and special web descriptions for stock/units. Good meeting.

	Shop 1981		AFB Demo	11/16/2016	On a Zoom session and live demo with Chris Johnnie and Russell Moore going over the new AFB theme. Russell was the primary presenter and did a great job. We walked through the new options and settings and got to look around and play with the new features. Russell did a great job and the people on the Zoom session had a good response to what they were seeing. Lots of potential for what they are doing. Great look and feel with tons of custom options. At the end, we had a good discussion on direction and where things are headed. I enjoyed the demo, tour, and information session. Good stuff. As a side note, Shannon, Shari O., Bryan, Dave Forbis, Chris Johnnie, Russell, and a couple other reps and people were on the session.

	Shop 2070		General & Tech Support	12/5/2016	Tracking down some CSS and session bugs with the new AFB headers and footers. I then was on a phone call with Shari O. doing some tech support for an adilas client. I wrote an email back to Shari O. and some of the folks at Emerald Fields about some tax settings. Trying to help explain some tech support questions, settings, and what not.

	Shop 2047		Adilas Time	12/12/2016	On a GoToMeeting session with Steve. We talked about direction and where we want to head in the coming months. We also looked over the adilas YouTube media/content player, we setup a cannabis specific site (just the folders and rough structure), and we also talked about training events. Steve would like us to strip off the code from the https://data0.adilas.biz/top_secret/community_funded_projects.cfm page and start being able to collect monies to help with daily training events. We also talked about how my dad volunteered to find us venues for our training classes. Shannon got on the call. We talked about some progress on the videos that she, Dave Forbis, Russell, and Chris Johnnie. Shannon showed us the link to the current google drive videos. https://drive.google.com/drive/folders/0B7QkXlJmb-PSeGRMZF9jbG10ZEE We talked about the difference between in-person vs. webinar (web based training). We are seeing the need for the live sessions (they enjoy the connection with the people). Who, where, when? We need to offer the live events, even if they aren't fully attended. Build out the adilas university video library and the user guide. Make it easy to use and help train the trainers there. One of the unknown values is how do you help someone to stay on and keep going. Shannon mentioned Dave Forbis and Shari O. as up and coming helpers for tech support stuff. Also, Nick and Alan (both developers do have some great teaching skills). I could also be more a consultant and trainer type person. One of the major challenged is how fast things change. We shoot a video or write a help file and then things change. How do you keep up? What a good question... We have some great users... that is good and bad. We also don't have any standard certifications and/or train the trainer type stuff. Some of these people have some major skills but might be liabilities on the other hand. What about the adilas marketplace and the adilas university? We may be going too fast for our own good. What would happen if we totally slowed down and sell what we have? We build and build but are somewhat unable to slow down and tell people what we have to offer. What is the master plan? Do we already have it written down but just need to follow it or do we need to redefine it? We are seeing a change in the way that the system flows... We are getting more API socket calls, we are getting shortcuts, we are seeing more black box stuff, more developer specific code. We need to tell Shannon and Shari O. Who is going to do this new training? We may need to recruit who made it to help do the training. Make that part of the process. Slow things down a bit. The developer's notebook is kinda splitting now as well. We have elements of time in adilas university, adilas, and in the adilas shop section. How are we going to bring all of that together. We have things fracturing and splitting all around us. That is part of the game, we need to allow and accept that. How are we going to deal with that? Sustainable pace - slow and steady wins the race. Maybe keep looking at the process and judge the pace and needs accordingly. People have the potential to let you down. The only person we can truly trust is God. We can then give trust to other people. Make him your main stable anchor and then extend to others. If all else fails, then the sure anchor will still hold fast. I would rather be a trusting person and then be betrayed vs. not being a trusting person from the get go. Quote from Shannon who got it from an apostle (lightly tweaked). We are looking for a loyalty and commitment level of sorts. We do have to be picky. It comes down to a balance and a relationship. Take your time and start to build from there. Relationships take time. That is ok, build it everyday. We make the choices and strengthen and exercise those choices everyday.

	Shop 2304		Meeting with the AFB team	2/8/2017	On a GoToMeeting session with the AFB team. We had Steve, Chris, Russell, Brandon, and Shari O. on the call. We started off talking about Chris' needs for sub inventory on the ecommerce level. He is clothing and retail and needs colors and sizes. We talked about some options and recorded some small notes. After that, we talked tons of sales stuff, model stuff, and what is our next move. See the attached set of notes for more info. Great session and we recorded some ideas on packages, sales models, and how we could combine forces in order to increase sales for adilas. In talking about different package sizes and different industries, we did go over a concept of corp-based permissions vs. user-based permissions. If we took things clear out to the corp level, we could virtually hide (smoke and mirrors) or take parts away to simplify the options. As a side note, when dealing with custom... not everything is adding. Sometimes removing things really helps to make the pathway clearer.

	Shop 2311		Meeting with the AFB team	2/15/2017	On a GoToMeeting session with Chris, Russell, Steve, and Shari O. We met and talked about some more sales and marketing options. See the attached notes for more information. Steve and the others keep going after I dropped off. We had a problem with the data 0 server and I had to jump off and do some fire fighting to help a history table that got locked and was issuing out duplicate primary key id numbers. - Idea from Steve, Russell, and Chris - What if we turn some of the existing places of business into real adilas training centers. For example: Say a retail shop that uses adilas - they could charge for training some of the new people to use the system. They, the new clients, then pay to come and learn on site with people who know how to use the system. - What about pitching a pilot program where an existing company that uses adilas becomes a virtual training center of sorts. This could be a great sales tool for the owners and their employees. - This new program is more of a shadow and mentoring model.

	Shop 2478		Adilas Time	4/10/2017	On the daily developer session with Steve and Alan. We started out the meeting catching up from being gone for a week. We then rolled into a session on goals and projects that need some help and lovin'. Here are some of the notes from the session: - Sales and who to call? We need to figure out some phone numbers and make changes within the site. - Who is dealing with custom projects? We spent tons of time on this subject. Alan and I will be making more concrete decisions in a later meeting today. - What is the process? Lots of talk on processes. Assigning projects, getting projects, working on projects, sign-off, etc. - We have a breakdown in communication. We know we are dropping some balls. - Internal projects... >> mini conversions >> sub part categories >> sub queues >> special accounts and loyalty points >> world building and database stuff >> rework sub inventory >> dollar off discount stuff >> other discount settings >> icon menus >> sales and promotion >> pricing tiers >> custom labels >> smart cart stuff >> post-it notes - little to do list stuff >> flex grid stuff - additional settings >> rentals and reservations >> internal repairs - such as duplicate expense/receipts, reoccurring expenses >> adilas API section - documentation and ease of access >> help files and user manuals >> forgot password or password reset >> emailing invoices, quotes, and statements. We need to provide custom email addresses and maybe web versions of the pages (links to a .cfm page vs the PDF versions). >> bitbucket - branches and issues and pull requests >> Code sign-off and general communications. >> training and education >> server management and optimization - We need to focus on the features and benefits that we do have to offer! The list is huge and most of those pieces are fairly stable. They may need some light tweaking but are fairly stable. -------------------------------------------------- Brandon's typical day. On a trail by 6:30 - 8:30 Breakfast/Shower Meetings from 9-5 7-9 am sometimes early morning meetings 9-12 pm adilas meeting -- brainstorming, work session, or putting out small fires -- this session seems to be pretty productive 12-12:30 pm lunch 12:30 - 1 pm call with Calvin - 50% affective 1 - 5 pm with other developers on their projects -- meetings with Russell, code sign-off, planning, reviewing progress, brainstorming, doing actual code, debugging. -- meetings with Bryan, code sign-off, questions, training, helping with projects, guiding him on what is needed. -- meeting with Alan, planning, counsulting, dreaming, code work, documentation stuff. -- meeting with Nick. Planning, education, code sign-off, and working his projects. -- meeting with Shawn. Code sign-off, planning, and finishing projects and fine turning stuff. -- meeting with Dave Forbis and Shannon. Consulting, custom code, quotes, tech support, etc. - If I check email, text, or voicemail... I usually take down the info and make a post-it note... That just gets added to the pile. I've got these things to do on normal basis... - emails - text messages - voice mail - bug fixes - custom projects that are assigned to me - tech support - get calls from Steve, Shari O., Shannon, Developers, and other clients - Pay bills & write checks - Prep for upcoming meetings - server stuff - notes, documentation, and recording stuff - graphics - We tend to loose a lot of time in the transition between projects. - We are going to have Alan help with some scheduled times for code sign-off. During those times, I will be working on my own projects. - Use Craig as the "bucket" guy. Have him fill in where needed. Some backend business management stuff.

	Shop 2743		Adilas Time	6/8/2017	On the morning GoToMeeting with Steve and Shari O. We started out the day looking at the sales tax differences. We talked about a virtual dust pan for catching any rounding errors on tax calcs. Our options might be: - We extend the original percentage spot - where the percentage is held (on the locations). We could go with say a 5 decimal level of accuracy. - We could use a small bucket or dust pan for tax calcs. This could be called the rounding error for the tax calcs. - We could rework the math on the tax calc function (this is the main function that is used over and over again to calc the taxes). Check for possible bad rounding errors. - We could show a flag on the invoice line items reports where a tax is off (say a color or an icon or something - say red...) - We could show the full extended math on the edit invoice line items page... this could include the extended price * the tax % - no rounding - and then the rounded value. - The biggest complaints are on the grand totals per tax category... This is just a sum of the details. We can't really adjust that number... it is just math. We can however get tighter on the individual sums or individual line items. - Drew some graphics on possible disconnects between calculating the taxes based on line items vs. invoice totals. We were talking about the disconnects on line items vs. grand totals. We came up with a number of possible options... - What if we calculated and stored the line item calculations at 5 decimals. We hold what it really is... - On the main invoices - we could add a number of new buckets to the main invoices... the only problem here is how much of a load this is... The ideas is: new buckets like: sub total, taxable total, tax total, all taxes (state, county, city, other 1-5, out of area), and a new one to help with tax calc diffs (rounding error or catch all bucket). - What if we ran things in a paired type solution where we have a total per tax section and the total taxes collected for that total. That way we could show a total and the calculation based off of that. - We will want to run each major report off of these new totals. * new idea - this could be super cool * what if... we did this summing and virtual bucket stuff on a daily basis... that would save tons of storage space. This is what we are hoping to call watchers, feeders, and even standalone declarations. We have been looking at things like this clear since 2010. - As a side note, we could propose a solution that taxed and calculated out to 5 decimals. Then at the very very end we could round it to real numbers. Steve would really like to take this proposal back to the state sales office to show them the problems and possible solution options. - We spent quite a bit of time talking about watchers, feeders, and standalone declarations. We made a number of small drawings and had a great meeting dealing with the vision of these concepts. See attached for some of the drawings. We talked about the 3D calendar and how things could play in if we caught things per day, per location, and per category (these are revenue, cost of goods sold, expenses, assets, liabilities, and equity). We also talked about possible options and how that could even be fed into a virtual video or play-by-play on the full financials of the company and how that plays out over time. Pretty cool futuristic ideas and concepts. - There is more information on these graphics in the media/content section. Additional explanations on watchers, feeders, standalone declarations, and 3D calendars. See attached and the descriptions for more details.

	Shop 2772		Adilas Time	6/15/2017	On the morning GoToMeeting session. Steve and I chatted and talked about options for taxes and such. That seems to be heating up pretty quickly. We did some prep for a meeting with Emerald Fields. Lots of checking and planning on what we could do with the taxes and what not. Lots of changes coming down the pipeline. On taxes, we will be adding custom tax values 6 - 10. We already have custom tax values 1 - 5. Also, we are seeing both part category and customer type playing into taxes and tax calculations. This is a question related to those two filters... On prices and price matrixes, how do those same pieces play in? On our smart group buttons we already allow for a limit based on the customer type. What if we expanded that and allowed it to be a one-to-many? Currently it is only a single customer type filter. I could see that needing to go to a list and be a possible one-to-many relationship and/or filter. Eric popped in part way through and we talked about taxes and calculating things based off of both part category and customer types. We did some drawing and went over some ideas. After Eric left, Steve and finished up doing some prep for the other conference call. We got on a new GoToMeeting session with the guys at Emerald Fields. They had 4-5 and adilas has 3 of us on the call. We had Steve, Shari O., and myself. We did a small presentation on how we could help fix the taxes and such. We pitched going out to 5 decimal places, adding a number of new custom fields, and then cascading the stuff throughout the system. I also pitched the idea of watchers and feeders but they didn't really like it. They didn't have a problem with it, but they couldn't see the bigger picture of what we were trying to do and how it would help them... Anyways, I know they would love it, they just can't see it right now. The meeting went for about an hour and they were pushing on us pretty hard. I was drawing, showing calculations, and trying explain our plan. I think it went well, overall. Sometimes people just want what will fix the issue and how quick can it be done... I think that it is interesting that they are making millions and millions off of using our product, but they are somewhat complaining about an uncontrollable rounding error piece that is like dust and shavings from doing a wood cutting project. Kinda interesting. Anyways, we have a small plan and will be starting into that here very soon. Good stuff.

	Shop 2799		checking into a hack on data 2	6/18/2017	Spent some time working with the server farm on a possible hack of one of the 8 data servers. We got a number of calls yesterday about 404 errors. This is where the server can't find the page that it is requesting (file not found error). Shannon, Shari O., and Steve took care of it and had the server guys reset things. Today, around the same time, we started getting calls from our clients on the same box that it happened again. This time I called the server guys and ordered a full lock down on FTP and RDP to that server. They are going to be changing the usernames and passwords. I went in and fixed the problems that I could see and then manually went folder by folder looking for new modification dates and possible problems. The hacks were simple renaming of key files and folders, nothing major, just enough so that the server couldn't find it. Very interesting. I know that Steve and I will be talking about this more tomorrow and making a plan accordingly. It is no fun to get hacked but maybe it is a blessing and will help us make things more secure and help us to tighten things up.

	Shop 2951		Adilas Time	8/23/2017	Back on the sales tax expansion project. Started working line by line through the main add to cart page. This is the page that gets hit from tons of different angles including, but not limited to, simple searches, advanced searches, page view - per item, advanced add to cart, add special line items, my cart favorite buttons, barcodes, QR codes, sub inventory, convert parent to child, mini conversions, recipe/builds, cart quick searches - mixed sources, start cart, redirects from itself - add to cart, update cart, profit calculator, restore to cart, duplicate to cart, review cart (custom adds after the fact), transfers, internal stock/unit tickets, wholesale carts, black box, and other custom options. Basically, this page is a huge hub and has to be super flexible to be used in all of these different ways. As a fun side note, Steve called and we talked about training and education. Steve and Shari O. just got done with a meeting with a lady who has a masters degree in education and loves to teach. Steve and Shari O. are going to try to help her get started into the teaching and training world of the adilas system and/or the adilas platform. All parties are really excited. Steve called and just wanted to talk and chat about some of the ideas and options. Fun stuff.

	Shop 3240		Adilas Time	12/4/2017	On the morning GoToMeeting session with Calvin and Steve. We spent the first little bit doing some catch-up and talking about new and upcoming pieces and projects. We talked lightly about budgeting and told Calvin to send us a bill for a couple more thousand to keep things going with the sales tax expansion project. After that, Steve had me merge some files for him. Them we all split up and did some clean-up and catch-up stuff. All of us bailed out of the GoToMeeting session and joined Russell on a Zoom session. Russell was showing off the AFB quick employee time clock and the new email settings. There were 9 people on the Zoom session. Some of them were: Calvin, Steve, Danny, Chris Johnnie, Russell, Molly, Shannon, Shari Olin, and myself. Great meeting and I love how well AFB is creating new tools and then making sure that they get noticed, good training, and even some marketing efforts. Good stuff.

	Shop 3264		Russell Moore	12/5/2017	On a Zoom session with Russell. We were going over a new project dealing with a warning and info box on the top header that helps us track who has paid and who has not. This is a project that Steve had requested to help David Berkenkotter and Shari O. with accounts receivable (A/R's). We went over some ideas and I explained a couple needs and wants for the feature. Russell took notes and recorded the session.

	Shop 3250		Adilas Time	12/6/2017	On a GoMerging code, prepping, and planning my next moves. Fixed some tech support things for Shari O. dealing with default expense types for vendors. I then talked with Steve a bit about where we are headed - goals, progression, and such. Paying some bills and on the phone - other random stuff.

	Shop 3278		Adilas Time	12/14/2017	Morning GoToMeeting session. Mostly working by myself. Working on the adilas API socket code for Will. Touched base with Steve, Calvin, and Alan on different projects. As a fun side note, Calvin met with a client and will be proposing a mixed solution between a Window's desktop application using adilas API sockets and normal web-based adilas. That will be pretty cool. In a way, it is using the API sockets more than the normal application and existing flow. A full rewire job done on an external code set but still tapping into the power of the adilas platform. Pretty cool. Towards the end of the session, Mrs. Shari O. got on with Steve and I and we went over how to do assignments to custom paperwork. This uses the "Document Management" section. Shari O. needed to help setup some new clients on other servers to get access to the Texas 130U form and PDF document. Sometimes it is fun to look back and see some of the power and potential that we have built into the system. Tons and tons of dynamics. It just helps us play better in the custom realm.

	Shop 3268		Russell Moore	12/20/2017	Working on a small bug fix for Shari O. for stock/units on data 6. Then on a Zoom session with Russell. We merged in two code branches and uploaded code to the servers. One of them introduced a predictive text search for adding a new customer to a shopping cart.

	Shop 3533		Adilas Time	2/21/2018	- Steve is not afraid of making a change. - Steve was hoping that Russell would catch the vision along our line of vision. - It seems like AFB is looking for a piggyback ride. - The sales of the new tools are already falling on adilas. - If needed, we could play hardball. That is not our goal. - Our plan was to try to stretch out and get more help. - AFB is so strategic that it almost seems like we are not the same team. - Normal 3rd party deals are 70/30 or 80/20, where we keep certain percentages. - Possible options... withdraw the offer - we also need to say stop on all future building. No more meetings, no more free time. What about what already exists? They want a type of a buyout. Time is hard to calculate a cost on. We need to negotiate on what will happen in the future. No more power play... if you want to build something else... feel free, but it will be on your own servers. We put a value on what has been done and then start working toward that value. - If we want to bring time into the negotiations, we could play the game. We have Steve time, Brandon time, Shannon time, Shari O. time, David time, Alan time, etc. We also have system usage from Chris Johnnie that could be brought into the puzzle. - Steve is trying to teach a practical business lesson. Looking at the whole picture. - We could present them with a couple of other options. - We really need to be on the same team. - We have an abundant model. We can get others to fill the positions. - We have a reoccurring revenue model. We are a valid solution for companies and it works. - We need a graphic designer. - Option 2 - Close out AFB and transition into plain Adilas (same team). We figure out the value and then figure out the payback options. This could be monthly revenue percentages and free usage of the system for Chris Johnnie. It could also be some number that gets put on the balance sheet. We may want to explore some of these options. We are offering Russell an awesome reoccurring model. This is a percentage forever. That is the payout. - We need to close down the AFB mine shaft. No more side projects. If they still want to play along those lines... we need to separate them into a valid 3rd party solution. - If we can separate Russell from AFB, we may want to play. If not, we'll go somewhere else. We need somebody who is fully on our team. This is a marriage type relationship. - A couple of questions for Russell - Can he play at the same level as Steve or Brandon - meaning how we work together? Can you compromise (in a good way) and work with the team? Are you willing to talk things out vs just jumping in and pushing forward? We don't want any underhanded strategies going on... We are all on the same team. - We are virtually offering Russell a key spot in this company. Does he want to play? Yes or no. - We are hoping that Russell will see what we have offer and jump on. If it comes down to it, we will pick Alan over Russell due to how easy he is to work with us and jump in and play the game. - We are being pioneers in the business world. We are ok with that. - There are a number of new things coming... new technologies that will take over and take jobs from employees. We are seeing more things being headed into small strategic teams or groups. More things than we can even see now. - There is a hidden cost to managing some of these things. It takes time to make decisions and help mange things. - SSC or Start, Stop, Continue - This is way or method of dealing with things. - If Chris and Russell want to bring in new monies... we need to play in new ways. We need to keep it on a 3rd party level. - Planning the wedding vs planning the marriage. Look out to the future and make plans out further than the current event or meeting. After the meeting with Steve, I called Newtek and got put on hold for almost an hour. While on hold, I was printing checks and running sites and code to check on email settings and options. The guy from Newtek helped me out and we, in theory, got the adilas email problem fixed. As a side note, you should see the adilas payables (monies owed to other parties). This is the cleanest and smallest it has ever looked. Pretty cool.

	Shop 3536		Adilas Time	2/27/2018	Barcode printer trouble shooting with a client. - Problems with the label printers. We have had more problems with the Zebra printers. They Dymo printers seem to work much better. More people are switching over to the Zebra printers due to ratings and quality. The Dymo is considered a lesser of a printer. - We do have a problem with receipt printers but not as much as label printers. - We are hoping that Svend (spelling), a tech, could help us out. - We have issues with operating systems, browsers, hardware, etc. They all need to match up. - We have had a number of complaints about systems being setup wrong. This usually isn't a software issue, but deals with settings and hardware. Maybe the system does have problems due to the number of options. - Shannon and Shari O. have been great on the support side. They are the best. - We briefly talked about possibly moving away from the Flash barcode generator. We could do HTML, CSS, and/or Adobe PDF. - We have seen problems with printing (receipts and labels) due to different browsers. Some times Chrome works better, other times Microsoft Edge or Internet Explorer. - Russell - we are not responsible for the hardware. Maybe we should specify the hardware to use. - When we say a self-serve model, people don't really understand that. What does that mean? - We need to use the Adilas Market (adilas world) to point people to professional 3rd party persons who specialize in hardware. - On the setup or start-up email, we may want to put some info there about integrating with hardware. - There are many people who like the freedom of picking their own hardware. We need to keep that open. We also need to figure out how to service that openness. - Just for an example - We had 6 key players on a multi-hour tech support call today. We really need a master hardware specialist. We just don't have a master and/or 3rd party solution for that yet. We need it pretty soon. - We are seeing quotes going out for 20-60 systems at a time. How are we going to support that? We may really want to get some certification and/or recommendations to outside 3rd party solutions. - There are so many hardware options. A GoToMeeting session is really hard if we are just directing mouse clicks. Sometimes if we are live and onsite, we can fiddle on things at our own leisure vs having someone right there trying to listen and puppet the motions. - Sometimes our reps (our independent consultants) really take a beating. If anything goes wrong, it immediately casts a negative reflection on the main adilas company. - Some of our clients don't have a clue on what they are training... Who's fault is that? We need to make sure that our consultants have the training that they need. - Often it is in the initial setup and/or training where things go off the tracks. That is huge. - We may need to push the adilas market more... this could be for training, setup, consulting, hardware, etc. - Certified or verified consultants. We may even need some different levels. - If a consultant does something wrong, if has a huge effect on us and our progression. - The Adilas University is another big spot where we can help educate and help train our people, users, consultants, setup people, etc. - We have some very complicated needs... We have multiple industries... tons of settings... tons of options... and multiple paths. - We also have some new accounts that are trying to be at the white label level. If they get that big, we want them to be able to help out with the tech support, training, and setup. - Steve - We don't have a contract and people complain a lot, but they often end up staying with us. - We are all independent... We need to have some options and/or contacts or connections. - Maybe a hardware doc that has options and/or even suggestions for 3rd parties that could help. - Steve - Question for our clients... Is it software support or hardware support? It almost goes in different directions. Maybe we should help direct the traffic where it needs to go. Maybe a number for normal support and a number for hardware support. - We all have spent hours and hours at people's places of business helping them get things setup. It would be so helpful if we had a hardware expert who could help. A hardware guy or gal may end up spending hours and hours figuring things out to get it working. - We have tons of past users who are master users and players... it would be so cool to harness some of that knowledge. - Russell's word - dependables - We need more people like that. They just get the job done and help our clients fly and be very happy. - As we get support calls, maybe ask who their consultant is? That may help us know who is doing what and where things may be needed. - We turned over the presentation over to Russell to show us around some ideas for the news and updates page (aka adilas features). Basically, an online list (very visual and easy to navigate) of help files, videos, tips, tricks, and other verbage info. We can load up all kinds of stuff, step-by-steps, tutorials, links, screen shots, images, animated gifs, animations, videos, etc. Basically, make the adilas user manual be a super powerful piece of the puzzle. Make the information more accessible and very visually stimulating. Help our users and reps/consultants get the info and training as quick as possible. - Steve and others have tons of emails with info, tech support, etc. That is a huge untapped resource. This is just a note.

	Shop 3623		Adilas Time	3/28/2018	On the morning meeting with Steve and Russell. We talked with Russell about working for adilas on a more full time basis. We got a number of calls and text messages from Shannon and Shari O. about tax update problems. Off to the races to see what we can fix. Working straight through the day. I canceled most of my other meetings and just focused on cascading the tax rounding error through out the system. Super long day.

	Shop 3705		Error fixing	4/27/2018	Got a call and text message from Shari O. from out in the field. She was trying to setup a client with the new AFB time clock application. It was throwing an error. I went in and fixed and it and re-pushed up files and let Shari O. know about it. The bug took a bit to find and fix. Once we got it, it wasn't too bad. Other emails and tech support calls.

	Shop 3699		3 Day Live Adilas Class	5/29/2018	Live Adilas Class. Logan, UT - Bridgerland ATC, Custom Fit, Room 810 (computer lab). We had 4 live paying clients and a number of internal team members in the class. We had Steve, Shari O., Dustin S., Alan, Bryan, Calvin, Russell, Shawn, Jeremiah, and myself from the core adilas team. Not all of them were there everyday, all the time, but they all came and participated quite a bit of the time. We also had a number of folks join us online in the GoToMeeting sessions. We recorded all of the training except for two main sessions. Here are some links to the videos. video from day 1 - morning session small adilas demo, intro, and core concepts video from day 1 - afternoon session new features, open q&a, and historical stepping stones video from day 2 - morning session POS - point of sale features part 1 video from day 2 - afternoon session POS - point of sale features part 2 - open q&a, and world building in use video from day 3 - morning session CRM - customer relationship management overview video from day 3 - afternoon session exploring ecommerce & custom email settings - BI - business intelligence and big data video from day 4 - morning session tips, tricks, & best practices - small custom consulting session video from day 4 - afternoon session meet the adilas developers, adilas model, and wrap-up /////////////////////////////////////////////////////////////// other notes that I took during the class. 5/29/18 - Drag and drop custom fields - they really like the custom field settings for customers. They would love that to cascade out and filter through the whole system. Point and click, toggle on/off fields, sort, customize verbage & instructions, and be able to effect the display as well. - The need for more one-to-many relationships - Light request for more settings on the main salesperson and other salesperson settings - be able to split the names instead of just one setting. - A custom preset on permissions "copy and/or duplicate" permissions. - Setup a master and then apply those settings. This could be templates and/or master files - a virtual job description. - Floating up and down nav to help minimize the scrolling. - The power of "templates" - elements of time, sub inventory, payee/users, look & feel, etc. - Start by setting up the templates and then assign them as needed - that makes a great starting point. 5/3018 - Alan was doing an exercise - he had everybody list what they could for two minutes on all of the fruits that they could think of. Fun little exercise. After that, he was comparing this to development. We try to hit the fruit that is on your list. Things keep evolving and sometimes you forget things and have to add that in later. - Corp-wide settings and allowing you to set certain verbage stuff. - Bryan Dayton was showing the adilas market (adilas world). We really need to get others into the marketplace. - While Bryan was showing his profile... I was thinking that we need to help him get some better screen shots for his demo graphics. You could tell that they were done with a low end and/or free graphic editor (kinda fuzzy and pixelated). - It helps us to have a flow and/or a clear picture (talking about custom code and custom development). - Small demo on a custom dashboard for Global Design - Steve and Shari O. were talking and doing a demo together. Steve was talking and Shari O. was driving. Later Steve and I did similar things. It really helps to split that load and have a helper. The person talking can focus on what they are saying and the demo person (driver) can draw, highlight things, and show focus areas. It seemed to work out quite well. - Steve and Shari O. started out in a coffee shop and did some quick split cart stuff. They then went into some of the corp-wide settings to show how they were able to do what they were doing. Good flow from normal usage to how it is done based off of settings. - Eventually we need a deep merge (find and replace) on customer records. - Our users would like to be able to compound a discount. For example: double up points, do a 1.5 mark-up, etc. Lots of time based sales and promotions. 5/31/18 - Not many notes from this day... We started out and Steve and I were presenting on sub inventory. See the video links above for more details and info. 6/1/18 - Steve was going over the new cultivation functionality. 4 main levels for the cannabis guys... they need cultivation, production, distribution, and retail. - Some of the these white label options should really build out and use all of the pieces. - Page and function level settings - Interesting topic of hardcoding & concepting vs dynamic code & production - speed, limited scope, and testing. - Being able to lock-down certain pieces, features, and virtually ice things down (ice-down dates). - Also, interesting as we get deeper and deeper into the industry specific code... the verbage, lingo, & the flow are really important. That is what makes it feel like native or custom code or custom software. - Comment from Dustin - We need guide rails, guard rails, settings, templates, and easy configuration options. Help lead the people down the paths that we want them to go. - On the data tables - it sure would be cool if you could sub filter things. It comes down to space, coding, page real estate, and planning. People want more and more custom options - to setup their flow, work space, and environment (requests for deeper and more robust world building options). - On numeric entry fields, show the unit of measure to remove the questions (if applicable). - Making the label options show up and be available from multiple pages and such. - Settings are preset choices & decisions - super important. - On Calvin's tools... Just an idea, but what about dynamic or user input boxes and text fields? This is for text that may be added on the fly. He currently has static text, HTML enabled text fields (allows formatting), and dynamic look-up text (text fields mapped to data or dynamic output). What about user input text boxes? - Making labels and empower the users. - We had a client/participant that recommended that we put a small icon on each page that could be a default homepage and then have a quick link to set it as the default homepage. Great idea. Basically, let them navigate there (to the actual page) and then set it as their homepage if that is what they want. ///////////////////////////////////////////////////// Comments from Bryan - who talked with one of the participants - When starting the class, for someone who is brand new... it might be nice to give a 15-20 intro and general overview. We just started out and jumped right in. Basically, somewhat of a canned explanation of what is adilas and what do you get with this software package. A really simple and organized intro. ///////////////////////////////////////////////////// Notes from Dustin - See attached for full notes General To Do's: Need to Have each page check for the color of the background and adjust the card to be a lighter complimentary color (universal). (4,5) Need to have api key capability for each employee that performs metrc api interaction. Need to set up custom permission setting capabilities so that they can set permissions for multiple employees over time without having to do a redundant process. Themes and standardized user type templates. Make a excel or csv spreadsheet that templates the fields needed for api integration to give to a customer to fill out. Maybe a master list that passes in all of the general fields and passes over unneeded fields based on customer needs. Need a graphical repesentation of the entire seed to sale process with tie-ins to each adilas feature/tool. Need predictive on the search vendor field on the add/edit page. Need to have customer password fields auto-populate wherever needed. (e-commerce) Need to have a set to default button on the nav menu for setting any page as a default homepage. Need to have a toolbar button for page relevent tips and tricks with links to news and updates. Need to update how people reset thier login attempts: lets add a captcha or at least put the copy paste link on the same page. Maybe two step varification would work. When you are switching corps, instead of needing to click on the little box link, make it so that you can click on anywhere on the corp piece. Need to have UOM type indicators on any field that holds wieghts. In most cases this could probably be hard coded. Need to create the ability to check a box that opens all of the subs for inventory search for adding to cart.

	Shop 3908		Adilas Time	7/16/2018	Working through various tech support and email requests. Took some time and got the new data 10 server fully updated and ready for service. Did some backend database work and bridged key adilas persons to the new data 10 server. Let Steve and Shari O. know that the data 10 box was fully live and ready. Worked on merging in code from other developers. I also got some paper work put together to secure the meeting room reservations for the next adilas training in Denver in September of 2018. We were going to be working on in-line discounts with Alan, but it didn't happen.

	Shop 3883		Adilas Time	7/19/2018	On the morning meeting with the guys. We had a number of random emails and tech support requests come in from last night and this morning. We spent most of the morning session brainstorming and talking about options and what we could do to help track things down. We even invited Shari O. and Drea into our meeting and got some of their feedback. They have been helping out with tech support and what not. We determined 3 main things that were problems/issues. They were all dealing with rounding errors, tax rounding, and cart/invoice rounding. The other common thread was a tax category called "with tax included". What that means is we have to back into a known target (certain dollar figure) and then adjust the price and the taxes to perfectly match that target value. That may not see very hard, but it gets crazy tough in the backend. We did test after test, took notes, talked about options, and came up with a light plan. Most of the coding was done by Alan Williams and myself. The others were mostly sounding boards, consultants, and extra sets of eyes. We demoed the cart/invoice rounding and the potential there. We also came up with a plan to help on the line item level and how to control the rounding. Alan had to switch some of the business logic around to make it work. By the time the morning session was over, I felt pretty beat-up and thrashed. In the mean time... more emails and phone calls were coming in asking about updates and timeframes for getting things fixed. At the time, it felt pretty overwhelming with just a small hint of a plan. I'm so grateful for other players who helped shoulder some of the load and responsibility. Good stuff.

	Shop 3927		Brandon will be checking in	8/2/2018	Checked in to see if anybody needs some help. Mostly out of the office all week. Talked with Dustin about some sub filtering of prep queries (working with smaller record sets) and then some form submission and JavaScript stuff. Going through emails and text messages. Talked with Eric and setup some times to work on the loyalty points project. Called and chatted with Shari O. and Steve. Just touching base. Tech support and other random to do list stuff.

	Shop 3952		Adilas Time	8/27/2018	Wayne popped in and we talked about database transfers between servers and how to handle duplicate records. We came up with a plan and he will be moving forward with the plan. Eric and I setup some dedicated times to work on loyalty points and special account tracking. We are planning on 2 hour blocks for the next two weeks, from 1-3 pm, Tuesday, Wednesday, and Thursday. That will be good to get some dedicated times to work on things. ------ different topic ----- These were some other questions that I wrote on a number of post-it notes... we are just trying to get organized and figure out a better plan for handling all of the pieces that are coming in. - There are so many needs - There are so many new requests (new things) - There are quite a few bug requests (old things) - Who does the work? - How do we inform them? - What is the plan? - How can we duplicate ourselves? - How do we create the funnel type approach.... things come in, we record them, we organize them, we distribute them, we work on them, we can check in, get reports and put things to bed - If I add to my to do list... it never gets done - Who can I use and what are my budgets? - How do you prioritize request, projects, and bugs? - Who gets assigned? - What do we want to be? - What are we becoming? - Who are we wearing out? - How do we mange that? - What are our goals? - We need some help - See a need... fill a need - I kept coming back to this... this may be the next step. - Help people manage themselves - I feel like I'm climbing with a dresser on my back - so many pieces, we need to simplify. - What teams (people assets) do we have? How are we going to use that? - I'm running and hiding... - We need some help - Kinda like facing giants - Get the Lord's help - Get some good help - See a need, and then fill that need... make a plan! - Focus on one thing at a time - it is hard to switch and transition. - We may have to keep people at bay while we do things. - Schedule it out and stick to that if possible. ------- meeting with Steve ----- - Departments and who gets what - We sometimes have multiple people looking and checking on the same things. That is not effective and/or efficient. Say an email that is sent to Steve and I, we both look at it and then both respond. This is just one example. - How do things come in? Do they start with support or do they start with a call to a rep or something else? We might need to start catching things and then funneling them around. - There is not a book on "SaaS" Software as a Service. We are kinda faking it as we go. That is for real. Basically a pioneering project. - Maybe talk to Shannon and see if we could get here back. Maybe have her come back in as a different role. We could really use an internal project manager of sorts. Maybe a higher or overall approach. - We may need to use elements of time and create our own support system and/or support tickets. That could be really quick, now that we have some things ready and done. - We would love to have a sorted tick list... What are the top 10 maintenance pieces, top 10 bugs, top 10 new requests, top 10 upcoming projects. Then keep rotating through that. - We love the concept of the data assembly line... What about our new needs... We have done of data, tons of servers, tons of requests, tons of needs... how are we going to track that process and take the actions that are needed. - We might need places where we have ideas, projects, maintenance, bugs, etc. - We often talk about the burning platform... it is amazing as we keep going, the burning platforms get fixed, and then there becomes another burning platform. - Steve and I need a shield to help us filter some of the outside static and/or noise. Once it gets boiled down, we could get a list of things to do and work on. - We feel bad about not being able to get emails, phone calls, and texts. We are just getting too many. We may need a person to help shield us a bit there. - Steve and I have thousands and thousands of emails and thousands and thousands of text messages. It gets too much for one person to handle. - We are in the business of data management, storage, processing, and such. We need to help categorize things and help filter the number of requests that come in. - Filters... We need someone to help us catch things and then basically boil things down into a manageable list. - We need to be able to allocate resources as we see fit. There are always limits on people, talent, time, money, etc. We need to manage our resources. - We have some guys that are top notch... We are seeing Wayne, Alan, Eric, Bryan, Will, Dustin, etc. They are all shining and showing more and more potential. That is exciting. - We also have Shari O., Shannon, Drea, etc. on the tech support and customer care side. - We will be working on a running list and trying to be more effective. - We really want to reach out and have the people run and excel where they have skills and talents. - We are going to be reaching out to and contacting some of our people. We have a great team... if we use that team wisely, that will open up options. - Kinda funny, we use to ask our clients, where is your pain? Let's start there. We'll we have the pain now, so, I guess we start there and work forward. Yee haw!

	Shop 3932		Adilas Time	8/29/2018	Got some reports that the data 1 server was having issues. The two reports were that it was not finishing the invoicing process on any corp and that a person could not edit a user account. I logged in and took a look at what was going on, sure enough, the invoice process was stopping part way through. It took awhile, but we found that the problem was the invoice history table. That table was tied in to both the add and edit invoice processes. Because we had ordered a full server restore, it was replacing tables with older data from a back-up. We also had a couple of people still on the server trying to put in new data. Just the way the tables worked, it created a conflict and was giving us a duplicate record error. The other problem was the main user table. Originally, it looked like it had been hit as part of the server hack. We later found out that it too was trying to sync old data and new data and just needed a little bit of loving. In the meantime, we posted a temporary login page and added notes to it throughout the day as we found out new pieces and made small break throughs. It was pretty stressful on our side of the fence. I know that some of the clients, on their side, were stressing it as well. Throughout the day we 7 or 8 of us here at adilas helping out. We had Calvin helping me on the servers and checking database stuff. Wayne popped in and helped us reset a number of things and do some looking around to see if we could see any other harmful activity. Alan popped in and helped us with fixing the database problems towards the end of the day. None of them were very straight forward. Steve was helping to coordinate who was doing what and testing with fake data to make sure things were flowing through. Shari O. and Drea were doing emails, phone calls, and text messages. I was digging through log files, working with the other guys, and back and forth with the server team in Arizona. Very busy day and it took the whole team to figure out different parts of the puzzle. I'm super grateful for their help. Only the one server was down, but that was pretty crazy. Lots of lessons learned and it was re-restored, released, and pretty heavily tested by around 6 pm. We added a link to the main login page on that server to show a link of what happened and some notes from throughout the day. One of the most stressful things was wondering if the problems were part of the hack job or just circumstances of mixing old and new data from the restore from back-ups. On a positive note, I would say that the biggest lesson for the day was - enjoy the learning process. Sometimes that is fun and sometimes not, but the cool thing is, if you enjoy learning, it will always make you better. Pretty cool. Long day.

	Shop 3959		Adilas Time	9/4/2018	On the morning meeting with the guys. We started out with Wayne asking questions about payee/users and how they can and do criss-cross and how they can cross between corps. We talked about options and why we did what we did. We got in to migrating parts, items, and PO line items. We then has some conversation about splitting up databases, indexing, and other processes that could either optimize the data processing and data retrieval process. Calvin and Alan popped in, they were working on labels on the content server. Alan helped Calvin wrap some of his code in a try and a catch. It was awesome and he was able to push the cfcatch variable. That allowed us to figure out what we needed to do to fix it. Super cool. Steve and Alan - "We break things and then we fix them." Fun little saying. Alan would like to rework the forgot password project. He wants to rework the security and how that process would work. He would like to beef things up a bit and make it more bomb proof. Alan would also like to work with Wayne on breaking code into smaller blocks and working in a more MVC (model view controller) type model. Basically, making baby steps and making things into a more object oriented code base. Alan was talking about encapsulating and modularizing functions, data, and components. Lots of code reuse and minimal duplication. Question - Build new or build on what you have? We are leaning towards refactoring existing code vs re-writing new code. Adilas' goal is build as if for years. We were talking about sub inventory and taking that whole new level and pushing it out into an object oriented model. We also talked about implementing Wayne's testing framework along the way with the new changes. The goal is trying to limit the number of times we are re-writing the same thing. We want to reuse code as much as possible. We talked about strengthening our foundation so that it could handle more weight and also allow for flexibility and fracturing, which will still occur, no mater what we do. Light talks about black box code and who pays to keep it updated. There seems to be two different levels. There are critical updates and non critical (optional) updates. We need to figure out a standard procedure to deal with custom code and black box code. Sometimes, if we have a problem and we are forced to think about it, we can usually come up with a pretty good solution. If we wait too long, we are forced into emergency surgery and sometimes that is not the best approach. We want to be pro-active on our approach and on our development. Steve and I were talking about some hanging projects... One is the invoice due dates and watching for outstanding receivables (David and Shari O. really need this). This was a Russell project that only got half baked. We need to finish it up. The goal there is for us internally, to be able to see what companies owe what and what the dating is. Then once it gets to a certain level, we could prompt for payment and/or be able to shut things off. We also talked about how it takes a whole village to raise the upcoming generation. We are really trying to build the adilas community and adilas family. We have many talented persons who are playing the game along with us.

	Shop 3960		Adilas Time	9/5/2018	Got on the meeting early to work with Steve and Alan. They were looking into some server issues with the data 5 box. Alan was on the box and Steve was browsing through the web. They were running checks and looking at things. Most of the corporations were doing fine, the problem was with one of the bigger ones. It seemed to be at the database level. If a super huge query was being ran, it was clogging up the queue to run other database queries. Alan ended up looking into temp table sizes, heap sizes, and max levels of memory that were available. He made some small modifications and we fully rebooted the server. When it came back up, it seemed to be running much faster. Alan then went to all other servers and adjusted database max levels to match the new settings. In a small way, this is just part of the performance tuning that needs to happen. Basically, you run into a wall, figure it out, and try to expand the corridor. Shari O. popped in and we had to look into a small issue on the data 1 box. Alan was on the box and we had a table that had locked itself. We did some repairs and were able to get the table back up and running. Wayne popped in and had a few questions. Dustin then worked with Alan to get some JavaScript rounding errors taken care of. Alan and I then started to look into the sales tax updates for other tax 6 through other tax 10 (new custom tax fields). This is one of the final steps in the sales tax changes that we were making earlier this year.

	Shop 3961		Adilas Time	9/6/2018	On the morning meeting with Steve and Dustin. We merged in both of their code branches and pushed a few new files up to all servers. Calvin popped in and reported on his local hard drive and getting it recovered... good reminder for all of us to keep doing local back-ups. Alan came on and helped with questions and then he and I went over the Denver training schedule. Alan is doing some performance tuning on some of the servers and some of the most used queries. We talked about getting access to bigger data sets to run the queries against for testing and to see the real costs (against the database) with the bigger data sets. Small plans and talking about indexing certain tables, columns, and combo columns in the database. Called and touched base with Shari O. about the Denver training event. She will be doing a couple of sections and also talking about who is covering food and snacks. She is awesome and wonderful helper.

	Shop 3957		Adilas Training Class in Denver, CO	9/10/2018	Adilas training course in Denver, CO. We will be at the La Quinta Inn and Suites. Englewood Tech Center 9009 E Arapahoe Road, Greenwood Village, CO 80112 Phone: (303) 799-4555 See attached for notes, scans, files, and GoToMeeting recordings (videos) -------------------------------------- Day 1 We did some intros and then got started. Danny Shuford did a demo and did a great job. See attached for some notes. Here are a couple of the highlights from what I took away from it. - Solution for solution minded people - It can be molded to fit your industry - Changes keep happening - Big open view of the whole system - it wasn't made for just one industry - Brief overview of the framework - Based on user permissions and valid logins - All web-based and cloud-based - Features and benefits - focusing on the benefits - CRM - log notes, additional contacts, photos, and other media - We all deal with money, but in the end... we are all dealing with people - Note to me... Danny went into the customer table and doing the custom page settings on the customer fields. This is for things like the name, aliases, sort value, show/hide, etc. We really need to keep pushing that idea and concept forward. People really want that level of control. It just takes a ton of work to cascade that through the full system. - He talked about news and updates - "Our Interface" - what do you want? We don't have a single set interface, we let you choose - Customer queue - Lots of moving parts - Drea - "Adilas is play dough" - Inventory tracking - Reporting and building your own reports - Labels and changes to the requirements - ecommerce - Payroll - Accounts payable and accounts receivable - Print checks - emails - Customize and working with the developers - Security and back-ups - Steve - Showing some hidden gems - Small demo on flex grid Next, I gave a small section on the adilas model - core concepts - and intro to world building. I will upload my outline. I'm also hoping to upload the video as well. I don't have any notes because I was the presenter, but here is my rough outline: - We will be bouncing around - Start with a guy holding tons of stuff - Talk about the needs and how to organize things - Go over different tools... head and mind, paper and pencil, word processing, spreadsheets, databases, software packages, web or hosted solutions - Go over systems and how things start to inter-relate - Cover the 12 main players - Cover the 12 business functions - Cover the 12 main world building concepts - Mix and blend to get the desired results After lunch, Alan Williams did a presentation on highlighting and exploring new features. He started out with a fun group activity and a game of sorts. Minimal communication and we had to figure out a path through a virtual mine (bomb) field. It ended up having forward steps, side steps, back steps, etc. We eventually, as a group, got through the mine field. Really fun exercise and it opened up some conversations. Here are some notes from Alan's presentation: - Little active - mine field - group activity - finding their way - How does this relate to the adilas process? - He then showed some of the steps that we have taken to build the application - Side steps, back steps, and forward steps - Going into advanced add to cart and sub functions - Request from the group - no standalone discounts - Make that a permission and/or a setting. Standalone discounts can and do cause tax problems. Next, Steve Berkenkotter lead an open Q & A section. The first question was asking about any updates with the Metrc (state compliance and tracking system for Colorado). That got pretty deep but exposed some of the challenges that exist between connecting and maintaining dual systems (adilas and Metrc). Here are a few notes: - Questions on Metrc - Some new tables and new limits from Metrc - Auto processors - running nightly stuff to help sync data between systems - API and server to server connections - Challenges that exist - Mixing old and new functionality - Transfers - Sales - Using elements of time to track states, status, phases, and groupings - Getting back at the data - reporting - High level vision - Question from Pat - 280E - new tax and accounting rules - what can we write off as cost of goods? What about unitizing expenses? - Steve - How the IRS is looking at things and expecting things - Steve - loves numbers and how he brings his skills to the table - Work in progress - attributing a value as part of the accounting - The progression of building and breaking - The system is able to store the data (huge piece of the puzzle) - The system may be customized to get the data back out and/or to get the data in (another huge piece of the puzzle) - Template building - A consultant spending time and configuring a system before it is released to the end users - Small questions on CSS and changing certain page colors The last section of the day was a presentation on historical stepping stones - what have we learned and why do we do what we do? I did this presentation so I will add my outline. Once again, we are hoping to get some videos uploaded to this element of time incase someone wants to watch the videos. Here was my outline: - Where did we start? Spreadsheets, static web sites, zip disks and sending inventory around from place to place - Fixing current business problems - Where is your pain? Start there - Letting operations lead - Use the adilas interactive map to help show flow - At some point, accounting will need to follow - Checkpoints and flowing data - Gap between operations and accounting - drawing the gap, horses and carts, and old school T accounts - light history of accounting - How does time play into the mix - Comparing operations and accounting in a static environment - Comparing operations and accounting in a dynamic environment - Progression - drawings of the data assembly line and how it ended up at a 3D data assembly line - 3D world building - x=time, y=resources, z=space or depth - draw out the box or cube - Black boxes & white label options - The whole deal We didn't quite make it all the way through the whole outline, but we covered a good portion of it. Towards the end, we went around the room and got some feedback. Those documents and notes will also be uploaded. The final request from the class was to have adilas allow the "adilas version" spreadsheet to be shared with the world. It was originally created in order to get a bank loan, but Steve said to release it to the world. Great meeting and good energy on day 1. Good stuff. -------------------------------------- Day 2 We spent most of the day working on and going over inventory tracking and point of sale (POS) features. See the attached videos. We also had some great demos from Calvin Chipman on building custom labels and one from Dustin Siegel on some new code and features that help with plant phases and cultivation. Here are a couple of notes from some of their presentations. For a more complete version, you may need to watch some of the videos from day 2. - Calvin and the adilas label wizard - He gave a slide show and then started to interact with the label builder. After he was done, we asked him to show some of the behind the scenes pieces of his label builder. Good stuff. - Vaporware - the product doesn't fully exist (yet) - part concept, part actual, not yet fully functional - User designs the label (step 1) - User selects the label from inside of adilas (step 2) - The label(s) are created and displayed on the fly, based on stored instructions, mappings, and special code. (step 3) - Part of the demo was showing sheet labels with a data merge, labels with barcodes and QR codes, static text, dynamic text (user can interact and change things), data mappings, graphics, etc. Pretty cool. - Small talk about PDF's, Flash, & HTML and CSS - printing options from the web - Our choice is PDF currently - Interacting with printers, browsers, and other hardware pieces - PDF - actual size vs shrink to fit size - Questions about font point size and possible limitations for compliance reasons - We will leave that up to the users, that way we don't have to chase all of the compliance rules and regulations. - We talked about settings and maybe limits that could be stored and looked up on the fly. - Possible template options - Be careful saying a compliant label - A good disclaimer to keep things legal according to the local and/or state requirements - put the liability back on the companies and/or users. - Small story of a company and internal programming wars and war stories - Different places that Calvin has worked. - It may take a hybrid solution of both software and web - Small demo of the actual builder - Calvin is going to be taking that and putting it more into a wizard-type format. Currently, you have to be pretty techy to use it. Round 1 - prototype. Dustin gave a presentation on some new cultivation processes and some dynamic mapping. We had some technology issues, the demo was going slow (Internet) but the concepts were awesome. Imagine going from a manual one-by-one process, to a bulk streamlined process. Huge time saver, plus tons more data points, capturing the whole story clear down to minutes, seconds, locations, phases, etc. Pretty cool. -------------------------------------- Day 3 Busy day today. We got into sub inventory, why we do sub inventory, customer relationships, elements of time, flex grid, ecommerce, custom emails, group mass texting (GMext Pro), and a presentation by Kelly Whyman (super power user from the Denver area). We are going to be posting the videos and the notes from the day. Good sessions. Here are some of the notes that I took while others were presenting. Once again, see the attached media/content files for videos and other digital notes. These are some notes from Shari O.'s presentation on CRM functionality - CRM - The real acronym stands for Customer Relationship Management - Shari O.'s acronym for CRM is - Can't Remember Much - pretty funny - Good data in = good data out - Fill things out completely and make sure you get good data in - The client log and how to use it - Leaving personal footprints in the sand - using the log - Addin gin a user-maintained history... internal communication - Cover you own rear-end - Being business appropriate - have good manners when recording details and data points - Custom emails Drea did a demo on how to show/hide transfer packages inside of the adilas/Metrc inventory pages. Here are some notes from that: - Transfers in and out and how to hide things - Everything in adilas is flexible - This new functionality is only a week old - Talking about manual clean-up and automatic clean-up - doing side-by-side comparisons - Using the data tables and being able to sort and search data - almost on the fly - re-writing the page based on the data. - Some of the new CSS cards, tabs, and such - really look super cool and it seems more intuitive - it also makes it look more modern. - We would love to keep adding new data tables and more options - As we keep going, we may need more clean-up options Calvin game a PowerPoint presentation on GMext Pro - This is his group mass texting solution. He did a great job and I think that people really liked it. Here a few notes that I wrote down. - Pretend like you are a client - Communicating to a large group or large groups (plural) - Pitching GMext Pro - great demo and presentation - Some of the stories of huge companies and how changes have happened and how those big companies weren't able to keep up. WordPerfect and Blockbuster were some of them. Major game changers entered the market and could do things better, faster, and cheaper. People gravitated to those new options. - Technology happens... embrace it and thrive - Mass texting and single text notifications - similarities and differences - Phones and phone numbers - with mass texting, you are basically buying phone numbers so that you can send more texts at a time. Each phone number can only send 1 text per second. So you may need 5, 10, 15, 20, 25 phone numbers to get all of your texts sent out. - Problems with people giving out the wrong phone numbers (bogus numbers or wrong numbers) - that can break your marketing campaigns - too many wrong numbers and you get reported as a spammer. - Ways of opting in and out -------------------------------------- Day 4 Final day of training for this go around. We started out day 4 with a group session on tips, tricks, and best practices. We spent quite a bit of time going over settings, permissions, and parent attributes for items. Steve then did a whole session on the three main parts of the balance sheet (assets, liabilities, and equity). The topic was intro to adilas backend office and functions. Steve took the words backend office and tried to flip it to - let's put the owners in the driver seat vs trying to drive from the back of the plane (pretend they are trying to fly the plane from back in the bathroom with the doors closed). Great session. The afternoon session was talking about BI - Business Intelligence & Big Data. The group talked about databases, data, and how to both get data in and out of the databases. Lots of fun examples. We then has some other Denver power users jump in and do demos on tiered pricing and smart group buttons, and another one on the process of doing a full inventory reconciliation and full inventory count. Great info and good sessions. The final session was supposed to be on the adilas model - vision, future, and wrap-up. We were all too tired, so we just chatted and went over a bunch of the things that we learned from the training session. We got some great notes and tried to clarify a few items, topics, and concepts. Pretty casual ending. Great people, wonderful ideas, excellent participation, and memories made. A great training session. Here are some of the notes that were taken while others were presenting: - Molly presented on parent attributes for items - think of tag or ways to categorize things - On parent attributes - for example: say you have an item but want to show different brand names or characteristics - Say you are selling shoes... You may want Nike, Converse, Adidas, etc. Or running, walking, hiking, trail running, etc. These would be good parent attributes or tags. - Parent attributes are huge for ecommerce searching and creating tags for different items - Russell did a great job on so many different features - we would love him to keep building more features - Easy setup - Building your own little shortcuts - Parent attributes are used for labels, sales, ecommerce, searching, filtering, etc. - Treat parent attributes like a way to build your own database... eight use the flex grid and the custom fields or use parent and sub attributes. - Both parent and sub attributes are unlimited and they have a proper data type such numeric, dates, text, toggles, and drop-down lists. That really helps when putting data in and also when querying the data to get certain results back. - As an idea... what if we build out both parent attributes and sub attributes to all 12 main player groups, inside of adilas. You literally could build your own one-to-many database relationships. The main 12 player groups are deposits, invoices, users, vendors, customers, stock/units, expense/receipts, balance sheet items, elements of time, quotes, PO's, and general inventory items. Currently, parent attributes and sub attributes are only available for parts or general inventory items. Think how cool that would be if we pushed it to the next level... /////////// - Small note from a meeting during one of the breaks... what is the internal adilas funnel to report an error or a bug? Who gets put on that project? We need to figure out our own process and communication funnel. - Bryan and Molly and others... funding some of the consultant projects - what is the short list and then where are things at. Basically, what do we have to work on and what are the priorities of those pieces? - Shannon may be part of this funnel that we are trying to build out ////////// Back to the main training even... The next session was Steve Berkenkotter and Shari Olin - going over financials and adilas backend office functions. Steve pretty much ran with this subject and did an hour long power session on the three main parts of the balance sheet (assets, liabilities, and equity). - CPA homepage interface - Inspecting what we expect - you have got to look at what is being delivered as a final product (actual items and/or tasks or services) - Going back to the beginning - balance sheet homepage - When you get a new system, we setup a default bank and default location - Problem with batching... Say trying to remember 30 days back and/or not getting data and information for a long period of time. It kinda leaves you guessing and/or missing some of the details - Steve - Think of flying a plain... try to be ahead of the plane... where is it going - often pilots try to think 3 tasks ahead of what they are doing - Views of the balance sheet - a trial balance - working and checking mode - Assets, liabilities, and equity - We covered the difference between the income statement (P&L - profit and loss statement) & the balance sheet - Values and tax laws - Depreciation and schedules - Life cycle - length of the life of an object and/or an entity - time and a schedule to lower a value (usage & wear & tear) - The IRS has setup the tax game... They want you to play and even play up to the lines that have been setup - think of a game - play to the line - Where you put things in very important - Small discussion on double entry accounting - history and pros and cons - Skate to where the puck (hockey) will be - The formula is the most important part of it - Passing things like a hot potato... basically moving things along the data assembly line - roll call accounting - A balance sheet is a snap shot in time - Talking about the profit margin and where does that come in to play - Small holes in the ice - things that are either gotcha's or thin ice (not all the way done) - Some of the guys and gals were saying that we need - big dumb animal pictures - super simple instructions - Accounts receivables - Think of that as they have your inventory or they have your endeavor (a promise to pay for something) - basically, they owe you money - You have to know the story - sometimes the numbers tell the story but sometimes the story tells the numbers what they mean - Liabilities and hidden liabilities - be careful there - Hidden costs - Triggers - Payroll and payroll taxes - this is a huge sink hole - Sometimes we can't do things due to the technology - as that opens up, we have more options - Auto processing and calculating needed values in non-peak times that could then be available for other reports - Fall backs, redundancy, auto-syncs, and re-syncs - Turtle up, sometimes the servers will shut down and pull in their legs - kinda like a turtle protecting itself - We need an all encompassing system to help steer the ship - think platform or system - Owners - who holds the liability - Steve - analogy of the tail wagging the dog vs the dog wagging the tail - who is in charge & which way do things flow? - The owner needs someone who is a decision maker and/or gate keeper - What is the game plan and do you have buy in? - The POS (point of sales and inventory tracking part) is only a small part of the puzzle. Very small compared to the whole business realm (world). - Abundant model - you have to imagine a line of people wanting your services and standing in line - next, next, next - The backend - really, this is the pilot's cockpit and/or the driver's seat - Absorption (in take) model & attributing sub costs over time - Dustin - I want "this" (meaning adilas & underlying data) to argue with my boss, not me. - I need a business tool & now I can run faster & better - thank you - Equity - Net Profit - it comes from the P&L - one of the only connections between the income statements (P&L) and the balance sheet. - Investment - how was this company funded and/or formed? - Fracture - just having fun - it keeps doing it (fracturing) on its own... maybe let it keep going and play accordingly - Change "backend office" verbage to the cockpit or balance sheet. Towards the end of the day on day 4, we had a couple of power users show some demos and such. We had Josh do a presentation on my cart favorites and smart group buttons (tiered pricing). Drea made a suggestion that you make the pricing tiers as dummy proof as possible. They even pushed the ending values clear out to show a visual warning to the person using the buttons. The other major request was for this feature (buttons and tiered pricing) was dealing with allowing these buttons to be time sensitive for sales and promotions. We also had Drea go through and show an inventory update and how she does a physical count and then an inventory clean-up. She would pull reports, export data, show/hide columns, add columns, print things out, and have her people go work. Then she showed how the system would take those over and short values and push them through an update PO (internal tool for updating inventory counts). Pretty cool. As we go along, we will need more clean-up tools. Clean-up tools make things look better and help to give users a peace of mind. We also talked about trust issues and how sometimes it is tough to trust and/or trust people. All of that plays into the mix. My final note about the training sessions is that those who played with us, live and online, really had a good time and we all learned a lot. Good times, great food, and wonderful people. Inspiring sessions. If you want more details, check out the media/content pieces (notes, excel docs, scans, and videos for more info).

	Shop 4011		Meeting with Shannon	10/9/2018	Meeting with Shannon - 2 tasks to follow up on - hardware with Svend and picking up existing pieces for the adilas user guide. New notes - She has met with Svend twice and they have another meeting setup for later this week. Their goal is to get Svend's adilas market profile up and have some live content by next week. Once that profile is live, we will let Shari O. and Drea know to help point people who have hardware questions to Svend's market profile. As a second step, we would like to do some more news and updates (tips and tricks) dealing with hardware and then give some credit to Svend and such. Create links back and forth between the adilas market profile and the news and updates. Shannon will reach out to Russell and see if she can get some more advanced training on both news and updates and advanced options for the adilas market stuff. Russell is still the master there. On the user guide stuff, we also went in and found some of the old content that was created for the adilas user guide. I did some light checking on my end with no new results. Shannon did find a number of her files. Shannon will be pushing those pieces up in to the adilas university so that we can get to that info. She has about 20 Word docs that have some beginner user content. We scheduled a meeting for next week, and will stay on task with those two tasks. Just advancing the ball. Also, as a fun note, I gave Shannon some other updates on who is working on what and some other inside adilas news. We are really excited to have Shannon back working with us. It will be awesome.

	Shop 4025		Adilas Time	10/31/2018	Happy Halloween! As a fun side note, both Steve and Josh have Halloween as their anniversaries. They were able to chat and have fun talking about that. Calvin popped in and we got some API stuff working on the adilas content server. He needs that functionality for the new adilas label builder app. Good stuff. Alan, Dustin, Josh, Steve, and I were on the morning meeting. Steve had a couple of questions about some emails that were going around. We pulled in Alan and chatted about some database restructures, re-indexing of records, and full table rebuilds. We then talked briefly about a client that has a bunch of custom code but hasn't really been able to get things going. They are currently not paying their monthly bill and not responding to the David B. and Shari O. We have decided that we need to turn them off as it is costing our company trying to chase their company. If they want it, we can easily re-flip the light switch back on. Wayne jumped in and we did some checking on his database migration code. We logged into the dedicated server and ran a couple reports. All of the data looks good and he will be contacting the client to let them know. This project has been ongoing for about 2 months now. Basically, we migrated about 10 corporations off of one of the shared servers to their own dedicated servers. Well, once we finished and released the new dedicated box, they came back and said, what about this other corporation that we had no notes and/or record of. Because it missed the normal migration process, and the new server was already live and consuming auto id numbers in the database, we couldn't do our normal migration process. Instead, Wayne had to write a new program that allowed for both servers to keep running at full speed and still be able migrate and copy database records across between servers. That may sound easy, but think of all of the auto id number and foreign keys based off of the auto id numbers that could get messed up. This was a very deep project. It looks great and seems good to go. That is awesome. We intend to use this same program (actual software we have to run on the physical servers) to help us migrate other clients off of shared environments and into either other shared servers and/or to their own dedicated boxes. That is a huge break through for us. Good stuff. After that, I jumped in and did some emails and tech support stuff. Towards the end of the meeting, Calvin jumped back in and we made two of his permissions go live for the adilas label builder. We then did some light testing on the live servers. It still needs some lovin, but we had a successful live test between data 0, the content server, and Calvin's adilas label builder app. That is pretty cool. He was going to make a couple changes and then get back with me. Pretty cool and some great progress.

	Adi 1435		Invoice due-date project - also A/R controlled page header	11/6/2018	10/6/22 Videos for the auto email, email report and invoice due date functions. 10/6/22 Page URLs for completed project. Note: These URLs are primarily from the auto email part of this project. The URLs for the email history report, use credit terms and invoice due date project were not included as it would take a significant amount of time to dig up this past information. Large edits 1. public/afb_email_preview_action.cfm 2. public/auto_email.cfm 3. publictop_secret/cfc/Services/EmailService.cfc 4. top_secret/cfc/Daos/EmailDAO.cfc 5. top_secret/secure/classic/email_report_body.cfm 6. top_secret/secure/email_report.cfm 6. top_secret/secure/afb_corp_email_home_action.cfm 6.top_secret/secure/afb_corp_email_home.cfm Small edits 1. Application.cfc 2. public/auto_email.cfm 3. top_secret/cfc/search_15.cfc 4. top_secret/cfc/security_4.cfc 9/29/22 The auto email project was pushed live and tested. It will be used by Shari O for a week or so then the automation will be added to each of the servers by Wayne. The auto email project was completed and pushed to data 0 about a month ago. Several bugs were identified by Bryan and Shari O, but were put on hold as other higher priority projects were being completed. 6/13/22 Met with Brandon to clarify some specifics on the 2.2 plan. 2.2 Email history report (email_history_home) 1. new table (not the same as invoice history) a. new update that creates table I. Look at tables for examples (history and text) II. Email_history table variables – like custom_text table: email_history_id, corp id, payee_id, datetime, app_type_id, main_id, table_name, special flag, history_note (13, 3076, statement). III. Types of special flags: Invoice, quotes, pos, statements, customer, eCommerce, custom, auto due date, multiple invoices. 2. Set up history capture on email a. design email capture (from/to email addresses?, status: success/failure) b. search for pages to put history code on by using adilasuniversity.biz c. add email capture on all pages 3. Create email reports page a. be able to search by: type, time period (day, week etc). I. model after invoice_home_basic.cfm 4. Show email history on invoice history, PO history, quote history, and statement history reports (invoice_history.cfm etc). a. bold line below reports saying “Email History Actions” and then email reports b. ? auto_sent column in email_history. 5. Report on my_history.cfm page a. Tie to invoice app type similar to how statement works. 6. If it goes out manually it also goes into the history. 5/31/22 Met with Brandon and developed plan for part 2. Broke it down into 3 sub-sections 2.1 Add setting (Use Credit Terms) and if selected change due date on Cart 2.1.1 Add "Use Credit Terms" settings to Corp Wide Settings 1. create database update and add tiny int 2. research standard invoice credit terms 3. standardize credit terms on Corp Wide Settings, add_edit_customer.cfm page and Corp Email Settings page 4. Add verbiage to Corp Wide Settings Page 2.2.2 Use Credit Terms to switch out default session due date 1. Working on cart_4.cfc 2. check if "use due date" has been selected in settings 3. get due date session default 4. check if "use credit term" has been selected in settings 5. if "yes" get credit term variable. 6. check if a number exists in it and it is less than 100 7. if "yes" switch out the session default variable 2.2 Check due date and automate email (not planned out yet) 2.3 Email history report (not planned out yet) 5/27/22 Met with Shari O regarding moving forward to add auto email to the Invoice Due Date function: 1. Bug on invoice due date: the due date is showing current date. Is this a normal bug or happening at server update? (1:59). 2. Can we make due date default "Credit Terms" on the Customer (add_edit) page. If Credit Terms is different than due date it will trump. 3. Email template "due date" reads from due date or credit terms. 4. Different (edited template if paid). Reads from due date or credit terms. 5. Auto send out reminders if 5 days from overdue. Adilas is due upon receipt, late fee at 30 days and shut down at 45 days overdue. Alan is making good progress as of August 2019. Brandon and Russell were working on this. It got to a point, and then got dropped. Finishing this up would really help with accounts receivable and cash flow. See branches ram-37 and BWM-33. Steve asked me to work with Shawn on this project. I lightly got Shawn started on the project on 4/10/19. This is an invoice due date project. It is a prep step to get a corp-wide header that could go from server to server to help prompt for overdue payments. Basically, a way to speed up the adilas receivables or A/R accounts. Once the invoice due date feature is in place, we can then figure out the aging of how old an invoice is, regardless of payment history. Once again, this is a prep step for a bigger project, but much needed. Russell and Brandon started the project back in December of 2017. Due to craziness, it got almost finished and then mothballed. We (both Brandon and Russell) picked it back up on 2/23/21. Project turned over to Bryan on 5/17/22. See media/content for a 26-minute video overview of the project.

	Shop 4170		General	11/15/2018	We had a bunch of screen shots that we uploaded for a meeting earlier today. Once they were up, I thought that they had too much info on them. I went in and added some sensor boxes to grey out some of the values (business privacy stuff). I reuploaded the images. I was also on a tech support call with Shari O. We have a client here locally in Utah that will need some in-person training done to get them going. We also chatted about some other internal email functionality options. It looks like we may need to revisit the email functionality sooner than later and expand the reporting, history stuff, and error catching. We may also need to go in and create corp-specific emails and put them in place in order to cut down on the number of returned emails. Basically, this will limit exposure as well as let the client know what is going on with the emails that are sent.

	Shop 4206		Adilas Time	12/5/2018	Merging in code with Dustin and Steve. Meeting with Hamilton from Full Circle at 10 am. They are looking for a January 1, launch date. Josh gave us a small update on where he is at. Customer dash board to show coupons, loyalty points, preferences, and maybe even a self check-in (add to queue). A possible manager's dashboard and tracking throughput and what campaigns are used and ratios for closing those campaigns and coupons. Josh is looking to build out some matrix to help show profit, costs, and other demographics (age, distance from store, etc.). They are looking to add a flag at the corporation level as well as at the customer level on who is playing with Full Circle (who opted in). If both corp and customer levels match up, we can add additional functionality. As part of an advertising campaign, we may just grey out the fields and help prompt the users to sign-up to get the additional functionality. Josh was talking about a virtual batting average per campaign - how many messages were sent out, what was the ROI and usage, etc. This will be more than just a response matrix, it will include prices, costs, profits, usage, etc. A mix of different stats and variables. Josh is also trying to tie-in things with his new discount rules and discount engine. This is a combo of both existing discounts in the system as well as mixing with outbound campaigns. There have been some talks on making a standalone version to capture more market share. Basically, a special functional section for adilas users and another one that is just a standalone, that way it may be used in multiple arenas. Timelines and vision - Josh is going to be breaking things into chunks to help with development and deployment. One of the keys that has been tied in, this past week, was the line item level of or for campaign tracking. That will be a huge key for reports going forward. Question by Hamilton - what options do I have if I wanted to stand up my own box (server and databases)? He was talking about a go to market strategy. What are the entry points? Options (1, 2, 3, or 4)? Two scenarios, existing adilas users (what do they get) and new users, that don't use adilas (but maybe hit at what they could have)? Basically, Hamilton doesn't necessarily want two code bases but we may have to try to direct them to the main adilas system. Make it a double sale. Hamilton was talking about a mini version of the adilas platform (small and cute and limited) and then over time, allowing his outside users to eventually migrate over to adilas over time. We talked about a mountain (show everything) vs a ice berg (limited view but more available)... Josh and Hamilton would like to flip the model and expose a smaller portion that looks awesome but has huge potential as they get deeper. It kinda comes down to the entry point (perception). This conversion is basically talking a mini version of the white label concept with a limited entry point. One of the key pieces is the domain name (it has to be pointed to a single server). We also talked about some dual entry points where we have both adilas domains and full circle domains pointed to the same box. Think of it like doors on a building... did they come in from the front, back, side, or up from the floor below? Piece of cake. It comes back to entry points, preferences, and traffic flow. Hamilton was talking about "dangling" options in front of his clients... virtual up sales of what else if available. If you purchase adilas as a package, it may be harder to up sale the client - they kind of expect the full package. However, if they come in from the Full Circle side, they Full Circle, could sell and/or expose other pieces based on a more modular pick and choose type model. That could be really cool. Once again, showing the full mountain vs just an ice berg with more potential under the surface. There were some light conversations between Steve and Hamilton about data storage and processing - who is hosting what pieces and where does the traffic come from? In a lot of ways, we don't really care where the clients come in the door as long as they come to play. We also talked briefly about Full Circle being able to expose small pieces as they become available (breaking the adilas mountain into modular pieces that are add-on's and virtual up sales). As a side conversation, there was some talks about beefing up the reoccurring billing section (reoccurring invoices) and making it more modular and automated. Billing for our services is a big things for us internally. The easier the process becomes, the less time we have to spend chasing it. That leave more time for other tasks. The tuff part is the technical side, the fun part is the selling of the features - from Hamilton. Hamilton wants to use his existing adilas account and setup reoccurring billing from inside the system for his existing Full Circle invoices. We will have Josh and Shari O. help get Hamilton all setup with the reoccurring billing inside of adilas. Josh was stating some ideas about helping to automate things back and forth between the main adilas accounts and the Full Circle billing parts and pieces.

	Adi 1465		Payroll questions from Shari O. - recording mileage and something else	1/17/2019	Brandon, Shawn and Shari need to get in and work on it.

	Shop 4277		Adilas Time	1/30/2019	Meeting with Steve and Dustin to start off the morning. Dustin had a couple of questions on ways to track some of his internal code changes. We talked strategy for a bit. Steve then had a question on a client's custom label. It was duplicating one of the fields. We dug in and found that it was a sub inventory attribute that was virtually sharing an id number with another sub inventory attribute. It was appearing to duplicate the data due to the numbering of the attributes. Random error. We went in the backend and fixed it. We haven't had any other complaints about that, so we are assuming that somehow both attributes got assigned the same reporting number. As Steve and I were fixing the sub inventory issue, we were talking about sales, customer support, and how we are hoping that these new server configurations are going to help us out. We also talked about getting someone to help Shari O. - she is getting buried and needs someone to help. We also talked about some other ideas to think about while we are breaking up the bus (analogy of getting people off the bus and onto their own motorcycles or cars - aka world building). Here are some of the quick notes: - What about mini options for AWS servers... Currently we have multiple dedicated servers (with fixed number of processors, RAM memory, and fixed hard drives for storage). What if we took those bigger boxes and virtually broke out a new virtual instance for each of our clients. If it could work, it would be almost like a mini virtual dedicated box per client. Just an idea. - Steve would really like to split out users from corporations (allows users to exist as their own entity and also as part of a master list). Then, we could bridge people over and across and allow users to jump between corporations as they get assigned. We currently can do this, within a single box or cluster. It would be awesome if we could do this on a universe or global scale. Any user (has a single account) and could be interconnected and/or have access to any other corporation (world) based on permissions and being bridged over. Think of home planets and bridging people from worlds to worlds. (digital passports and what not) - Currently, we (adilas admin) are the only ones who can bridge users between corporations. If it went out further... we could allow individual parties to allow/invite other users to come in and help with any projects and also set connection durations (how long they could virtually stay). If we empower the users to create those relationships, that takes the load and the liability off of the admin adilas team. Good stuff. - Steve really wants to help out workers and/or dependables - We would really like add some visual upgrades - CSS and settings. As a side note, settings are going to be huge going forward. We are seeing at least four levels of settings - corp (world), group (system players), pages, and user settings. - Steve and I were looking at some stats that Wayne had gathered for us... crazy to see those stats and this is just one month from the data 0 box. We would love to see all of the servers and all of the stats, side-by-side, and compare. That would be crazy. - The deeper we get, the more settings and being able to toggle things on/off (custom setup options) are going to play in. We were even talking about new settings for ecommerce and companies that allow for new customer/client accounts to be setup. What fields do they want to show/hide, what ones are required, what special instructions, what names or aliases, what sort order, etc. Everybody wants crazy deep levels of control on how they set things up. - Steve and I talked about the pros and cons of the black box options... on the one hand, we can configure any page to do whatever we want. On the other hand, if we go black box vs building a new setting, we have to do the same thing over and over again. Sometimes the speed of the black box option actually creates more work later on. The longer route is building a setting, but it then becomes easier to manage that later on, plus less duplicating code.

	Shop 4358		Adilas Time	2/4/2019	It's Monday. Josh, Dustin, Steve, and I were on the morning meeting. Josh checked in and we set up some time to work on merging in his discount engine stuff. We added some new permissions and created a new help file for him to populate. We are hoping to get all of his code rounded up and populated within the next couple of days. Good stuff. Steve's summary from January - Mrs. Shari O. needs some help. We've got that going and Pat will be helping out. We need to make it easy, pretty, and powerful. Steve would like to circle back around and then we need to do some look and feel stuff (make it look pretty). We will keep building out the functionality but we really need it to look nice and appear more simple. If we can get the current model, more spiffy (nice looking), we can really wind some things up. It is a very abundant model. The future of SaaS (software as a service) is customization. People want to start very simple and slick but as they go, they start looking for more functionality and eventually really want it to be their way (custom code and customization). What do people do the most inside our system? We can pull in stats from all of the servers and then look at them (the stats) side by side. We could then have Russell go in and help us with some cool look and feel on the top 10 pages. Once that is done, we could keep drilling in deeper and deeper. Alan popped in and gave us a report. Steve and I were working on different projects. I'm working on checking in code that Will did for a thing called transitional PO's. The new PO type is between an order/request (not tied to inventory) and a live PO (fully tied to inventory and payables). The new transitional PO's allow for pre-payments (assets or pre-payments on inventory) and will be tracked on the balance sheet differently. The project has about 22 pages in it. Just going through and checking out code and adding my own flair to it.

	Shop 4370		Talking with Shari O.	2/5/2019	On the phone talking with Shari O. She called and had a request/question. We got it resolved and then did some talking about the adilas team and how people are coming together. Shari O. is doing a great job and is helping new comers have fun, get connected, and share in tasks and information sharing. I'm super excited and she is doing awesome and creating a fun team dynamic. She gets my vote. Yee haw!

	Shop 4449		Internal tech support	2/28/2019	Tech support for Shari O. and a stock/unit issue. We ended up fixing some code and pushing it up to data 0. It was dealing with URL encoding a passed value. The value they, the client, was trying to pass was causing the button code to break. I also helped Eric on a JavaScript loop question. I showed him a couple of ways of doing it, using existing code and hopefully pointed him in a good direction.

	Shop 4508		General	3/27/2019	Emails, follow-ups, phone calls, and light research on a custom project that is coming up. On a GoToMeeting session with Shawn going over payroll things. He committed some new files on the sdc7 branch. Started to do a code review and code merge. On a tech support call with Shari O. We were looking into some expense/receipts and running things through auto pay outs for splits (making payments on account).

	Shop 4510		General	3/28/2019	Working on some code merges and tax withholding updates from Shawn. Got a call from Shari O. and Dustin and I had to do a quick fix on a page that was pushed up earlier today. Minor tweak, but somewhat urgent.

	Shop 4540		General	4/2/2019	Got on to work with Shawn. He was working on payroll stuff so I ended up on a tech support call with Pat and Shari O. We spent about 1.5 hours working on getting those two, Pat and Shari O., setup and using the adilas label builder wizard that Calvin Chipman created. They got a pretty good taste of what it can do and we did some light playing and training. Lots of potential there. After that, I worked on some other emails and notes.

	Shop 4526		Adilas Time	4/8/2019	It must be Monday... We started out on the morning meeting and only Steve and I were on at first. We chatted about the transition over to the AWS (amazon) stuff. We have a number of questions and aren't really sure which way to turn. Steve needs to provide some of our clients with an answer, can we service them or not, and we need to know how long it will take to get the AWS stuff fully up and running. Lots of unknowns, but some great potential. Part of us wants to return to what we know (older stable ground) and the other part of us wants to keep pushing forward (new and uncharted but promising ground). It creates an emotional battle of sorts. We switched gears and Steve had some questions about a project where he is tying in balance sheet numbers to vendors. As part of his project, he was trying to come up with a switch that we could flip to help us know if a vendor was an inventory (parts or items) vendor or just a normal vendor. As we talked about it, we decided to take it out to an app type level (the 12 main system players). We talked about that and Steve liked that idea. I got him some code to help him get started. It is amazing how much, as we keep going, that the system keeps organizing itself into main player groups and what kind of relationships are needed per system or main player group. Very interesting. Almost like it likes to be organized into groups and related functions. We sure have learned a lot along the way. Alan joined the meeting and we were talking about some of his projects. He is still working on automating some of the reoccurring invoice stuff. We also talked about having Bryan work on the dynamic field names and settings per main player group. That is pretty deep and we may keep it tabled for now. Also, as we were talking about it, we were talking about how an object oriented programming approach may be a better solution for some of these new settings and defaults. Currently, we build and break, build and break (speaking about pulling and accessing settings). It may be nice to keep and hold some of the persistent or permanent settings and features. An object oriented model may be better equipped for that type of transaction. Currently, we look things up just in time. In the future, we may need to catch and hold those settings and maintain them in the user's session (stored in memory) options. Eric popped in and we did some check in and follow-up with his code review on the sub special account tracking project. This project is a sub of the balance sheet and deals with special accounts (mini bank account type objects) like customer loyalty points, gift cards, in-store credit, etc. That project is promised by next Monday. I will be trying to focus on the code sign-off this week. After that, Eric and Steve and I started talking about some of the new look and feel, CSS, and user interface stuff that Eric is wanting to help with. Both Steve and Eric were talking about a virtual "Adilas Cafe" or a global landing spot for the adilas users. This all goes back to separating the users from the main application code. There will still be a tie-in, but we are seeing a bigger need to keep users on the outside as a single entity and then allow them to go in and work or be a part of a corporation. We have many users that have and/or will need access to multiple corporations, and even be able to bridge across physical servers. Currently, our model is based on users per server and then tied to corporations based on active permissions to those corporations. We are seeing a need to break that down even further and have a master or global user id (virtual pool of users) and then allow them to be bridged to different corporations on a more global scale vs just per server (physical box) vs the possibilities of dynamic cloud networks. As we got deeper into the conversation about the potential of the Adilas café type model, we were talking about doing mock-ups, flow charts, etc. Eric had some questions about authentication servers and how that would all roll into the mix. We told him that he would need to get with Wayne to get more details. As we talked, we decided that Eric and Wayne should work together in a mini team type environment. As we explored the options, some of Steve and I's concerns (listed at the top of this entry) started to go away. We ended up somewhat asking Eric to be a project manager type role for this transition project between Newtek and AWS. That little tweak in the plan and how the developers were paired up, made a ton of difference and some of the anxiety started to go away. We need to crate a list of specs for Wayne and what we want the application to do. Plan and play as if for years. We also talked about in-house coordination and communication. That is a huge key and helps all parties involved. Steve was talking about skating to where the puck (pretend we are playing hockey) is going to be. He and Eric were talking about the existing login pages and the corporation chooser page as being the beginning of the adilas café (landing spot or centralized common ground area). Good discussion. We would really like to keep pushing the ball forward and making each system its own entity. This means having a centralized database controlling users and access to different corporations and/or entities and then having the individual entities having their own database or system for just their stuff. Currently, there are a number of tables that are shared between parties. For speed and efficiency, we really need to split things up more. This may also affect how we are able to bill for storage and processing vs a set monthly system fee. Anyways, as the conversation progresses, Steve and Eric were talking about using the choose corporation page as the starting common spot or commons area. Steve was also saying that he would like the users to be able to go to work (assigned or authorized corporations) as well as go play (demo sites, play grounds, or play sites). Basically, anybody could have an adilas account, and then they could either go into a real site (aka work) or a play site (aka play and testing). Fun ideas. One of Eric's and Wayne's first item of business will be to do a virtual inventory check of where things are at on the project and what will still be needed and/or stands in the way. That will be awesome. It really was an mini answer to prayers that we decided to team up Eric and Wayne. It helped us let go and be willing to embrace some of the unknowns. As part of that, we are hoping that having the guys work together in mini teams helps us prioritize what really needs to be done and when. Sometimes, by yourself, it is hard to know what needs attention first, especially if it feels like everything is vying or trying to get the input, attention, and/or priority. Crazy stuff, I'm been there before and will be back again. Steve and I talked about cycling through hardware and how that is just part of the line of work we are in. Later this year, we will need to buy some new laptops and upgrade some of our development environments. One of the breakthroughs for today was the mini team concept. We have Steve and I, Steve and Dustin and Josh, Brandon and Alan, Wayne and Eric, Shari O. and Pat and Drea, etc. There are starting to be all kinds of little teams. That is awesome. Shawn popped in and reported on some payroll updates and changes. We scheduled a time to meet again tomorrow. He is also willing to help me out with some of my projects and such. After that, I spent the rest of the session recording notes and trying to get caught up (as good as I could).

	Shop 4574		Business plan - whiteboarding with Kelly, Brandon, and Steve	4/23/2019	We were going to have a meeting with Kelly and do some online whiteboarding and business planning, but that didn't happen. Instead, Steve and Brandon had a couple hour brainstorming session about their own ideas on a business model and business plan. Super fun brainstorming meeting. - Steve and Brandon were talking about the role of the adilas market, adilas university, and the adilas café. - Steve was talking about ideas... are you buying or selling? What section of the market and/or café do you play in? - Just jump in... see a need, fill a need - we love it - Another piece that we may be missing is marketing and sales type literature and media pieces - We would love to recruit some others to help with the heavy lifting - There are tons of great adilas users out there who have some great skills - It takes time and energy to get things going - the goal is, once it gets going, hopefully it will keep feeding itself. - Steve is having fun tackling the business model - analogy - like a friendly pirate ship. It could be a boat, a ship, a car, a plane, or anything that moves over time. The fun come in as you start asking questions. Are we friendly? Are we mean? How many sails do we put out? What direction are we going (what is our heading)? What kind of crew do you want? How big and how small do you want to be? Etc. Fun stuff. - Sometimes as we write and record these log notes, it may expose some of our underbellies, but we really gain from it in multiple ways. - Steve and I would like to be open to discussions from any parties. We also acknowledge that there is a cost to being open and listening to those ideas. - There seems to be many cycles that interconnect and play as the ball gets kicked down the road. - Zipper analogy of bringing operations and accounting together. We started this a long time ago, we want to keep going but some of the steps are bigger and harder than others to conquer. Problems exists and that helps keep things going. Problems force decisions and hopefully a solution. - Working in teams and pulling through things together - it helps get the ball across the finish line and you build relationships along the way. - A constant mode of refinement - dive and resurface, dive and resurface - build and break, build and break - the concept of maintenance. - Building blocks of teams - forming, storming, norming, performing - where are we at in our team development process? - As we keep coming together as a team, there will be some normalizing and efficiency as we keep going. Good stuff. - Steve is always on the hunt for the better and better ideas. He loves the hunt, in theory and in practice. - Different angles, different views - false summits, operations, accounting, task oriented, dreamers, managers, etc. Like a pie analogy, we need the whole (in the end), and certain people are doing certain pieces (delegating tasks and processes), but hopefully as you bring it all together and it becomes the whole. - The proof is in the pudding - if you have a great idea... let's put it to the test... we don't have a monopoly on all of the good ideas. We want to be open to those around us. Ideas by themselves don't really stand too long... those ideas have to be put into action and start applying those concepts. - You can fund a company through investment, equity, sales, or leveraging debt. We are leaning towards sales and equity. - Talking about models, we are even seeing some morphing models (mixing and blending), client/services, budgets, and strategic customer care projects. Customer tune ups, targeted tech support, and other customer care and retention efforts. - Hoist anchor! Starting to get the ship out of the harbor. - Models - rep model, hub/shop model, 3rd party solutions and white label model - We are seeing a small mix between the basic rep model and the basic hub/shop model. - Russell's word "Dependable" model. A loosely bonded hub/shop type model where the bond is the dependable type and/or dependable people who service other parts of the service model. Basically, they stick around to help pick-up and service the by-products that are created (training, consulting, setup, design work, custom code, tech support, project management, training, and other by-product services). - Being able to clone some of the main core players - Steve, Brandon, Shari O., etc. Small teams forming under some of these key players and creating loose bonds (dependable type bonds). Very interesting. - Talking about sales and white label options, we have no boundaries and no zones - people could consume our product wherever they are - we don't plan on adding any boundaries and/or zones. - Anybody could identify a problem and/or issue - what we really want and need is those who help come up with and are willing to work on solutions. - Steve was saying that the employer/employee relationship is a kin to slavery - it can work, but over time, it has other costs and drains. Steve really wants to keep moving towards the dependable type model - It is very loose but it can and does work - We want to keep helping those around us - if you look at it... we have so many by-products, the by-products completely outweigh our normal products. Very interesting. One of the key pieces is, you have to want to play the game. If you are just coasting, it doesn't work very well. - Finding that balance point - We were talking about the difference between a normal company that has an employer/employee model vs this loose community of dependable - We also talked about how some companies are replacing the traditional model with robots, AI (artificial intelligence), or automated services. Where are those balance points and what makes things tip to one side or the other? One of the core concepts that we have is, our main product creates tons of subs or by-products. We can allow others to pick-up any of those by-products by offering their services (basically an open market type option). - Some of this is just happening and we are figuring it out as we go... We have plans, we try things, we fail sometimes, we go backwards and forwards, we try to listen, we harvest other's ideas, we experiment, we tweak, we refine, we circle back around. That seems to work for us. It is more of the try storming type mentality vs just a plan it and build it type model. - Randomly enough, we keep getting people circling back around after years of talking with them initially (old sales leads). We also have other people who are looking for and needing some of the functionality that we are working on and/or already have. The general public needs keep advancing right along with us. Step by step building process. Keep building towards the full system (fully interconnected pieces) and even full world building levels. - Talking about commissions and outbound monies and such - Steve used the word semi-dependable (not a full dependable, but still part of the whole team). - Finding the glide plane - like an airplane coming in for a landing. - Tag teaming based on abilities - Coach, put me in... I want to play or give me a shot. - People putting in time to help move the ball forward - Steve would like to move the company into a trust at some point. - We are excited that we are moving some things over to deeper and more expanded technologies - tech stuff and server models. - Keep working to get out of the way - There is some magic in having a business plan but it can have limits - we do need some direction but it also helps to have your head up and be looking around. Our current business plan is "we are heading North" or something like "we are heading to the top of the mountain" - we have a direction and a way to go about it, that's about it. Fill in the gaps and cross the bridges as they come up (we know they are out there, but we don't have a full plan in place for every little thing). - What about enjoying the journey? There is some fun in planning out the journey and then responding to cause and effect relationships that happen based on those decisions. That sounds like world building, in a way. The five core concepts of world building are: Characters, relationships, trouble/problems, decisions, and consequences - see this element of time for more information... Web link - time_web_gallery.cfm?corp=371&id=3634 - Some people will like what we do and sadly, we may make some enemies - we want to keep it as an open model - there are tons of options out there. We welcome those who want to play and we'll keep refining and building as we go. We want people who are looking for a solution and are willing to help and invest in their solution. We want to make adilas consumable... what do you want and how can you make it work for you? - Model of being able to charge for different components - it all needs to exist - what if we showed all of the 12 main players and what part of their bill gets charged out and/or applied to what part of the 12 main players? That could be pretty cool. - We may want to open up the adilas ecommerce piece to all of our clients. Currently, they have to pay for the extended ecommerce functionality. - Data - the new currency... people are offering features and functions for free, just so that they can collect data. Very interesting. - Steve would like to help push forward the ideas of the adilas café - a virtual community of users and/or other companies that offer their services - that will be really cool - helping to push the ball along the path using the skills and talents of others (a community of adilas power users and/or outside services). Once again, the by-products are a huge part of the model. - We do need some standardization pieces, but some of our model is the flexible ways you can do it... We need both side of the fence. - We ended by doing a brief look at where we have been and where we are going (historical summary of invoices and client based financials). Good stuff.

	Shop 4616		Adilas Time	5/13/2019	I was gone for a couple of days. Most of the morning meeting was doing some catch up and getting back into the groove. We had a number of different developers pop in and give us updates. We had Dustin, Josh, Alan, Wayne, Eric, and Steve each give some reports. We answered some basic questions and then got to work. Shari O. and Drea were also on the call. They let us know about a tech support issue that needed some loving (small error or bug). I then started to work on that bug. It was dealing with sub inventory attributes and being able to dynamically search by the attributes. The value in question was N11 (meaning the 11th numeric field). The old code had 20 custom text fields, 10 custom date fields, and 10 custom numeric fields. We are expanding it to allow up to 100 custom text fields, 100 custom date fields, and 100 custom numeric fields. That is just a number so that we keep it in check, technically, it could be pushed further, we are just taking smaller steps.

	Shop 4665		Adilas Time	6/6/2019	There were quite a few people on the morning meeting this morning. We had Steve, Dustin, Wayne, Shari O., and myself. We started out and Wayne wanted to get a standard spot to report and handle issues and bugs for the transition to the AWS stuff. We setup an element of time and will be using the sub comments and notes to record any issues and/or bugs. After that, Steve and Dustin wanted to go over the cannabis cultivation homepage and figure out where we could speed things up. See attached for some notes. The main take away from the meeting was user designed, single pagers, let users control the flow of data based on clicks and events, and use AJAX (asynchronous JavaScript and XML) type interfaces. The conversation turned lightly to aggerated data (pre-summed up data) vs transactional data (individual details). We would really love to keep heading more and more in this direction. Shari O. was talking about some communication issues between our clients and the reps that support them. We had an issue last night when we had to turn a client's system off. We had contacted the client and they were over 3 months behind on monthly payments. We shut them off (the companies system) and then crap hit the fan. The client was open 24 hours a day. Anyways, we had a rep that got on the phone and was ripping our tech support people a new one. We had some talks about how we need to use the system to be the bad guy. We have a project planned that will show prompts in the page headers and will let them know that they will be shut off if they get past a certain date. We need to get back to that. If we could get this project done, it would save a lot of headaches. Shari O. was talking about some team work and playing as a team. We have some great people who help and participate and some that don't do much. We have a spectrum of different people all around. This is both funny and sad, but sometimes we really feel like the little red hen - who wants bread? Me, pick me. Ok, who wants to help me plant it? Not me, not me. Ok, who wants to help me harvest this stuff? Not me, not me. Ok, who wants to help me with (fill in the blank)? Not me, not me. Ok, I guess that I'll just do it my self. Suddenly, we get the bread done, and everybody wants it. There is some truth to that. Steve was expressing some concerns that he is getting behind on his email stuff. We had some light talks about what needs to happen there and how best to structure our team. At a certain point, you almost give up and/or can't keep up. The mountain keeps growing and doesn't seem to stop. Back on team building stuff... we are trying to help and train our guys and gals to work as independently as possible. There are constant needs that just keep coming. It gets pretty crazy. Back on the email stuff, maybe we need to use more of a standard like "support@adilas.biz" or "info@adilas.biz" and then let it get filtered out before it hits all of us. Steve really wants us to use technology to play this game. More automation and more ideas and options. Lots of tag team stuff. We are also learning along the way. Lots of new lessons being learned and hopefully applied. Steve was talking about dependables and who is playing with what and who is doing what. We have a very independent model. That is awesome but does have some challenges as well. Steve would like his sales focus to be more on the white label type arena. Alan joined the meeting and gave us an update with USAePay and there EMV chip reading and chip processing. We may end up having to integrate with FirstData as a merchant processing account (more gateways). We currently offer some chip reading options, but it still kinda random and small ball of strings. There is a growing need on the merchant processing and gateway stuff (credit card processing and chip reading technology stuff). This is way out there... but maybe at some point adilas will be their own merchant processing gateway (some sort of internal solution). Alan volunteered for this project (just kidding). Towards the end of the session, Eric jumped on and needed some help with some queries of queries, complex data, and getting some data tables setup for his custom reports. We also scheduled some other time next week to work on sub inventory and API socket documentation stuff.

	Shop 4690		General	6/10/2019	Paying bills, recording expenses, and light email research. We are wanting to allow corporations and companies to be more self-reliant with their own custom adilas.biz email accounts. Shari O. and I will be meeting later today to discuss some options.

	Shop 4679		Working with Shari	6/10/2019	Shari O. and I met up to go over some email options. We currently have about 3 main email addresses that our clients use to send invoices, quotes, statements, etc. As such, if anyone replies to those emails, they get sent back to my inbox (email mappings). Our goal is to create a number of custom email addresses and then allow the customers, clients, and corporations to have their own email addresses. This should save quite a bit of time and should help the customers have better business transactions because I won't be in the middle (as a pass through account). Anyways, that is the goal. We went over some proposed changes inside of adilas and how those values will affect the email settings. We then spent most of the time over in the SmarterMail application going over their settings and options for forwarding emails. We made a good plan and will go from there. Mrs. Shari O. helps Steve and I pick up numerous pieces and does a knockout job. One of the giants of the adilas teams (awesome job).

	Shop 4691		General	6/10/2019	Worked on the admin corp-wide settings to help open things up for custom adilas.biz email addresses. Shari O. has instructions on what is needed there to help set those values up. I was only able to get the admin corp-wide settings page to update. The other page (AFB custom email settings) in question needs some database work before it will be able to updated. Sent a note off to Shari O. with an update. Got a call from Bryan and he wanted to meet for a bit. He got an email from a gun club that uses adilas to file member waivers, sign people in/out, and run their gun club. They are interested in showing community events (calendar and elements of time) to the public on their website. They would also like to do some ecommerce and do some online booking and reservations and being able to sign-up for classes through their website. Great stuff and very possible. Some of those things are already done and some just need a light tweak and we could make it work. Kind of a mix between ecommerce, elements of time, invoicing, quotes, customers, files (media/content), and making it all flow through correctly. Sounds fun. At the end of the session, I was working on a few small changes to a sales flyer for Pat, Shari O., and Drea. The originals are held here: https://data0.adilas.biz/top_secret/adilas_banners.cfm

	Shop 4735		Adilas Time	7/16/2019	Working on migrating around 7,000 customers from one corporation to three other corporations out on data 7 for a company in Florida. Shari O. popped into the meeting and had a question about changing stock/units models and their sub inventory types. After that, Wayne Andersen joined the meeting and had some questions about some of the settings out inside of the shop folder. He is working on the AWS stuff. We went over a few things and talked about progress in the transition between spinning hard metal (normal dedicated servers with actual hard drives) vs the AWS cloud (virtual servers, stacks, and dynamic server assets). Interesting.

	Shop 4737		Adilas Time	7/18/2019	Working with Alan on debugging a cross corp invoice to PO process. The error ended up being in a sub loop and switching between main or parent line items and sub or child line items. Anyways, Alan figured it out and we did some testing and got it all fixed up. I had a client join our meeting and we did some trouble shooting on his Authorize.net merchant processing account. Later, Mrs. Shari O. popped in and had a few questions. Small but productive work session this morning.

	Shop 4863		Server issue	8/21/2019	We got a report that one of the dedicated servers was having problems. We had all hands on deck looking into what was going on. We ended up getting Bryan, Molly, Drea, Alan, Wayne, Steve, Shari O., and I all involved at different times and in different levels. Kind of a freak error. Anyways, we ended up on a GoToMeeting session looking around and trying to get all of our heads together. This may sound crazy, but I'm so excited that we have tons of great help. I used to have to tackle these crazy things all by myself. I'm so grateful for awesome team mates. Good stuff. As a side note, normally it does take this many people to get something figured out. This one had a few contributing factors. Everything started when a single folder got moved on the server, pages couldn't find their other pieces. Then there were some cause and effects that happened from there. We got it all figured out.

	Shop 4876		Work with Steve on project list	8/27/2019	Steve and I had another multiple hour session working on his advanced JavaScript. We got that whole thing done and tested pretty deeply. It was good to take a break and then come back and hit it again while everything was fresh. Both of us feel good about what it does and how it works. Good stuff. Part way through the session, Shari O. came over to Steve's house and chatted with us over the GoToMeeting session. She gave us a report on her health and we had some good laughs. After that, Steve and I looked briefly at our adilas to do list (aka adilas community funded projects). We mostly focused on the priority 1 projects. We then got out a text document and started working through our people (adilas team members) and who was doing what list. We made some notes and talked about a few projects and where things were at. Steve and I will be doing more and more of this to help things keep going and advancing. That is exciting. Spent some time recording some notes and getting caught up for the day. Busy day today.

	Shop 4974		General	9/26/2019	Officially release the data 16 server to Mrs. Shari O. She does all of the new system setups. Went into the server and made a few small changes to some settings and such. Emails out to developers about the new serves data 15 and data 16. Back working on some stats and runner counts for the Bear 100. This year's race will start tomorrow at 6 am. Trying to get a few last minute tweaks to help it be even smoother this year. Good stuff. I got a call from Shari O. and we jumped on a tech support call together. A client was having a small issue with payables and being able to pay multiple expenses with a single check. We went through it and everything seemed to be fine. We voided out the testing expenses, made notes, and Shari O. will call the client back and help them know what to do. We didn't solve any issues, everything worked through the times we tried it and actually ran some test data through.

	Shop 5268		Putting a new server into production	12/4/2019	Wayne released the data 11 server to me earlier today. I went in and updated files, checked settings, and updated some shared database tables and ran some database updates. The data 11 server is now ready to go and I sent an email to Wayne, Alan, Steve, Cory, and Shari O. letting them know that they could start adding clients to that machine.

	Shop 5350		Working with Shawn	12/31/2019	Shawn came over to my house and we did some work on payroll stuff. He was busy working on new state and federal withholdings. I haven't started yet, but will be working on W-2's, 1099's, and other PDF reports for payroll. As a side note, I got a call from Shari O. with an update as well as a call from Russell with an update on where he is at with things. Lots of good stuff happening.

	Shop 6093		Going over payroll with Shari O.	3/5/2020	Shari and I got on the GoToMeeting session and had a brief chat about 2020 federal withholdings and new W-4 changes. We just launched some code the other day and need to circle back around and make sure all is well. There seems to be a problem with one of the withholding calculations.

	Shop 6146		General	3/21/2020	Working on new payroll changes and monitoring servers during a physical server move and relocation being done by Newtek. We will have some servers being both up and down during the day as they move them from one location to the next. Moving day. Steve, Wayne, Shari O., and I were all on the morning meeting and adilas GoToMeeting channel all morning. We all got on at 9 am and have been on all day monitoring and watching the progress of the move. Crazy time. This was pushed on us by the server company (actual server farm) with minimal warning and lead time.

	Shop 6148		Payroll and server monitoring	3/21/2020	More work on the 2020 payroll stuff and watching the servers come up and start working again. On the GoToMeeting session with Steve, Wayne, and I. We were all working on different things and randomly chatting and talking as we either waited or thoughts came to our minds. Group effort. I also know that we had Shari O. and Drea online doing tech support all day as well.

	Shop 6024		Business consulting	3/23/2020	Meeting with Jonathan Johnson from Epic Enterprises. All of met online, due to the corona virus stuff. Steve, Brandon, and Jonathan were on the meeting the whole time. Shari O. was on for a bit but had too much to do. We took a bunch of notes and sent her a copy. The notes are Brandon's computer in a Word document. See attached for a local (on his computer) reference. Good meeting.

	Shop 6211		eXPO: eCommerce push	4/1/2020	Got on with Bryan to look at some code. He was still working on some stuff so I ended up doing some other stuff. I reached out to Wayne and we did some new server testing. I created a small tick list and started checking things on the new server (data 17). Pulled down files from data 0 and pushed some files up to data 17. Helped Bryan with some questions and talked with Shari O. over the phone. More server testing. I fixed a few things and finally ran into an error. I sent a message to Wayne and called it quits for the day.

	Shop 6380		Meeting with Shari O.	5/14/2020	Shari O., Steve, and I were on the meeting for the first little bit. We had some good conversations about where things are headed and likes and dislikes of some of the options that we have. Shari O. has always been a great helper and a core part of the team. Eventually we (Shari and I) went over some email stuff but the first half of this meeting was some great open conversation about direction, team players, and wishes and dreams on how things get structured. Here are few things that I pulled out of the meeting. - How big do we want to be? How flexible or rigid do we want to be? What personnel/staffing would help those dynamics? And where do each of us want to fit into that mix? Great questions. We chatted and did some drawing to illustrate certain points and pieces. - Our current trend is more towards an open model. We just feel more comfortable there. - Shari O. really wants to get some good customer care and proactive helping of our clients. That has been a big goal of hers for years. - We also went over email settings, auto forwarding for our clients, and how best to setup custom email addresses to lessen our loads and make our customers more responsive and productive. Nice meeting with a mix of all kinds of topics. Towards the end, Shannon joined the meeting and was able to chat with Mrs. Shari O. for a bit. That was good.

	Shop 6400		Meeting with Euflora - Expense issue	5/19/2020	Flipping some expenses and re-voiding certain pieces for a client. Talking about our model as far as the main adilas team. We had Shari O. and Steve on with us. We really want to keep building small teams of people vs individual or solo teams. We also need to spread the load and in order to keep building. It is too much for just one person.

	Shop 6362		Projects	5/19/2020	Scanning and recording some notes from a meeting with my daughter Aspen. She helped me out back on 5/7/20 and we took a few pages of handwritten notes. Great meeting. Recording some of those notes. Got on a GoToMeeting with Shari O. The subject was dealing with email accounts, settings, and how to best handle some of those pieces. Here are a couple notes: - Being able to send emails have been around for quite awhile. Here are some of the project rounds as I see them. 1. Can I do it? Yes, it is done and we can send emails for invoices, quotes, statements, and custom. 2. How well does that work? This is where we are at right now. We could really use more histories, logging, error handling, notifications, Wayne's touch, Russell's touch, etc. 3. The third round might be full automation and being able skip adilas all together to get the emails and communications going. - We talked about outsourcing some of the big and small projects and pieces. There are times that we really need more manpower and skills. - There are waves that pass over all of us. If we watch out for each other, we can help de-stress and transfer the load as needed. - Shari O. and I talked about the jelly fish model - dealing with how the adilas model, tasks, and talent pool is constructed. See attached for a rough drawing.

	Shop 6463		Adilas Time	6/8/2020	Catching up from a long weekend. Shari O. was on the meeting and needed some login access to some of the newer servers. I showed her how to flip things per server to help with future logins. Steve and I worked and touched base on a number of projects and direction of where things are headed. After that, Steve and I worked on some of his aggregated banks and cross corp mapping project. We went clear back and talked about the approach and sketched out a plan on paper. We then went into code and started working on things. We had to prep some of his data to help the page work better and be a more accurate test.

	Shop 6467		Adilas Time	6/11/2020	Jumped on the GoToMeeting and Steve and Shari O. were on. A new server got spun up and we migrated the old data 2 box to the new server. They were standing by to help with tech support pieces. Most of the things went pretty smooth. Throughout the morning and into the early afternoon, we had a number of different people join us on the meeting. We had Steve, Shari O., Wayne, Alan, Bryan, and myself. Both Wayne and Alan were brought in to do some of the heavy lifting. Wayne had a really long day. We made a few changes and things calmed down by the afternoon time. Steve and Shari O. were fielding the tech support pieces and then Wayne, Alan, and myself were making the changes that were needed. A great team effort. Good stuff.

	Shop 6440		Projects	6/25/2020	Talking and working with Shari O. over the phone and on a GoToMeeting session. We were dealing with email accounts and email users. From Shari O. - "We are like family and we take care of each other" - meaning the adilas family. Helping Bryan with some questions. I also swapped out the older meet some of the team graphic on the contact us page with a newer graphic that didn't have Dave Forbis and Bryan Dayton's numbers. More generic.

	Shop 6490		Adilas Time	6/29/2020	On the morning meeting with Wayne, Shari O., Steve, and myself. We ended up having Eric and Danny join us later on. The start of the meeting was dealing with new server company settings for Hostek and different tech support pieces. We got Shari O. all setup to help with any tech support pieces. Wayne is really stepping up to help us with code, Git, bit bucket, and code management. We spent most of the meeting going back and forth with Wayne on ideas and what not.

	Shop 6492		Adilas Time	7/1/2020	The morning meeting went long. We had two servers that were being moved. They were data 4 and data 6. The data 4 server had a problem and the databases were slightly switched around. We have a test database and a live/production database. The web server was pointing all new transactions towards the test database and we couldn't see the live data. It was still there, we just couldn't see unless we logged in directly. It took us a bit, but we (mostly Wayne Andersen) got it fixed and headed in the right direction. Calvin called and reported in on some things and projects. He has been helping users with the adilas label builder, doing more gmext (group mass texting) stuff, building new tools, and more mobile development. We chatted for awhile and ended our conversation on CMS (content management systems) and the need to be able to tie-in files and documents to different pieces of the puzzle. As a side note, Calvin built a tool that allowed files and documents (media/content) to be added to certain objects. He said a funny comment, "I have recreated only a small portion of what adilas already does." That was pretty cool. We do a lot and allow media/content, photo galleries, and files to be added to all 12 main application player groups (invoices, deposits, expense/receipts, vendors, users, customers, stock/units, elements of time, quotes, PO's, balance sheet items, and parts/items and general inventory). Switching back to the servers and what not, we really need to take care of Shari O., Drea, and Wayne Andersen. They have all been rock stars in doing tech support and server stuff. They get my vote and appreciation. Long days for all of these guys and gals.

	Shop 6476		Adilas Time	7/13/2020	Eric, Danny, and Shari O. were all on the morning meeting. Each were checking in and had random little questions here and there. We had to flip some user settings for Shari O. and also we went through a corporation email setup. Steve and Danny batted a few questions back and forth. Towards the end of the meeting, Steve joined the meeting.

	Shop 6684		Projects	8/24/2020	Emails. Phone call with Shari O. about Newtek servers. We also talked a bit about the adilas business model and how things are going and developing there. Here are a few of my notes: - You have to suit up and show up at the table - over and over again. You can't just show up once and get your way. - We tend towards a work in progress vs a fully finished and polished piece of art. That seems to be our style. We just keep building and refining. - We really play well with most of the people who are key players. Shari O. was talking about personalities and mixing those together. She is a good mother hen and watches out for her virtual chicks or peeps. Along those same lines, we have a number of key players who are doing great in filling their roles and doing a great job. We would love to see more of the same and keep refining along the way. - Similar fabric yet we have our differences. - We want to worry about the whole client base vs just a smaller selection or portion - think big picture. - Awesome discussion on checks and balances and how those can prevent misuse and dictator type influences. How can we build in some checks and balances into our business model? Cool concept. - Finally, we got into servers, payables, and options. We have servers at Newtek, Hostek, and AWS. We are trying to keep it all tight and straight and don't want to pay for services or products that we are not using. This is turning into a fulltime job, just to keep track of all of the pieces, expenses, and services being offered and paid for.

	Shop 6820		General	8/28/2020	I woke up and had some ideas for paring down a big huge corp-wide settings table. I recorded some of my thoughts on the project for paring down the tables. See this element of time for details (extra comments and notes). After that, I jumped on the GoToMeeting to check on some servers and voicemail that I had. Once I got on, I was able to help with some server migration questions and changes. I was on the main GoToMeeting for a couple of hours. By the time I got ready to leave, there were 10 of the adilas players on the meeting. All helping and virtually cheering Wayne on as he was in the hot seat and we were trying to restore one certain database table. This is kinda funny, but I got a call from Russell letting me know that there was an error. We told him that we knew about it and were working on it. Just for fun, I asked how he knew about it. Apparently, his name and phone number was on the error page. So, some of our users had called him. After a few calls, he logged in and checked it out and tried to get a hold of us. Kinda funny. That error message, that people were getting was an old relic from days gone by, but because a certain database table was missing, it was kicking out this 5 year old error message, that had been completely forgotten about. Kinda funny. Wayne got things fixed, Shari O., Steve, Alan, and tons of others helped. Later on, Eric and I spent time on a Zoom session and over the phone going over some logic for ACV (actual cash value) on customer loyalty points, off balance sheet items, phantom liabilities, and a switch from basing the loyalty points off a pure point value to the ACV value of the points. Pretty deep accounting things, changes, and logic changes. A lot of what we talked about were the auto clean-up routines and reconciliation processes. If you add in cross-corp loyalty points, things get even deeper.

	Shop 6716		Meet with Alan	9/2/2020	Met with Alan and touched base on some of his current projects. After that, we jumped in and chatted about a number of other things including the meeting that we had with Steve and Wayne from earlier this morning. Here are some of my notes: - We really want to split some of the guys into smaller teams to see what that would do. As we do that, we know there there may be more overhead to help those teams keep going, but we are interested to start trying some things. - We talked about making improvements to the project manager type role and filling in more of the requirements and back story before releasing a project to a developer. Ideally, smaller, bite sized pieces vs the whole ball of wax. Lots of talks about defining the role of the project manager (PM). Upfront time and monitoring things along the way. We would love to shoot for mini teams of 2-3 people. - Alan recommended that we see what people want to do based on their input from the survey docs that we sent out a couple of weeks ago. We want as many people to play and participate where they want to. That could be very useful but may take some time to get the right mix and balance. - If we break things into smaller pieces, that helps the confidence and the moral of our team members. - We talked about some of the core team members and what their roles are: Steve, Cory, Brandon, Alan, Wayne, Shari O., etc. - Having a buddy and a back-up plan - Who is the helpers that fit under the main people (sub players with in their own roles and areas)? We need to define those roles and relationships. - Alan highly recommended that we put in some of our own projects into the project queue so that we could reserve those spots. The project queue is already backed up a bit. - We would like to focus on more structured teams and getting deeper into the project management side of things. - There are always opportunity costs of doing more of one thing than another. We need to get in there and start figuring things out. Opportunity costs are what you loose and/or can't do if you do something else. - As part of where we are going, we would like to start using some more agile type sprints and agile development cycles and practices. - What is the next important thing? - We have been defaulting to Steve to be our leader. We all love what he does and no one really wants to pick up that ball (and all that it contains) and really run with it. Sadly, it almost feels like a poison ball (the full on leadership role). - Alan and I poked around the adilas site and looked at some business numbers and stats for a few minutes. - It really feels like a major cross road is before us... make it simpler or go even bigger.

	Shop 6643		Adilas Time	9/15/2020	Some of the guys checked in this morning and then went about their ways working on projects and what not. I was checking banks, payables, and doing odds and ends. Steve checked in for a few minutes. Busy times. I was also building a list of special reports for Shari O. to help monitor client usage, images uploads, and file uploads (media/content) stuff.

	Shop 6701		Projects	9/15/2020	Meetings with Shari O. and Steve. Shari O. joined first and we went over some email questions, email account stuff, and went through a small tick list of questions and things that need to be done and/or looked into. We also spent some time talking about staff and some of the adilas team members. Light report from the field... Steve joins us at 2 pm ish. We chatted with Shari O. for a bit and then just Steve and I worked on finances, budgets, and ideas for how to raise more money and capital. We have a really good thing going, it just keeps taking virtual gas to keep driving the car. This is the constant battle for most small businesses. I guess that we'll need to get creative and come up with something that works for us and fits our style.

	Shop 6952		Work session	10/6/2020	Test and merge new update for the flex attributes from Bryan. Great job. That project is live and being tested by a select group of clients and users. We know it has a lot more that is needed, but it is coming around. Phone call with Shari O. to go over servers, users, and accounts receivable stuff.

	Shop 6895		Projects	10/22/2020	Recording notes and emails. Part way through the session, we were notified that there was a bug and/or problem with stock/units. It ended up being that the stock/units were fine, the problem was the API socket call after the fact that was the problem. We had just put a version of a filtering software called cloud flare on the data 0 box. We were doing some super simple API socket calls and not using https (SSL - secure socket layer). No big deal, it was just a quick update. However, the cloud flare filtering software was blocking anything that was normal http (non secured traffic) and thus the problem. It took us awhile to figure it out and then to make all of the changes. I was on, Cory was on, Shari O. was involved, Wayne was involved, etc. It got pretty deep. We finally got it all figured out and okayed in the end but some rough waters for a bit.

	Shop 7215		General	12/15/2020	Steve and I were going to meet, but we ended up on different projects. I was helping Shari O. and Alan track down a stock/unit bug. We got denied a few times as we were trying different things. Still trying to figure out the new servers and their configuration stuff. We had to do some tech support stuff and emails as well.

	Shop 7216		Talking with Steve	12/15/2020	Steve and got on a meeting with Shari O and were talking about servers and questions that we had. Eventually, it was just Steve and I. We would like to setup some meetings with the server guys to make sure that we are all on the same page. We are automating things more and more, but we also need ways of tweaking things manually. If things get too automated, it makes it so that it is harder to fix in some ways. We need to find a balance point. Once again, more needs for balance and refinement. It is hard to nail this stuff down and it keeps changing. That makes for a dynamic and changing landscape.

	Shop 7126		Adilas Time	12/17/2020	Server meeting with a bunch of the guys. We had Steve, Wayne, Eric, Alan, John, and myself on the meeting. Later on, we were joined by others as well. There are some of my notes. - Some of Steve's top 3 for the year was - 1) servers, 2) customer care, 3) look and feel - On the auto Git updates... we are thinking that once a day may be enough... also doing this off hours. - Idea - kill the rej files, do the merge, check again, if rej files exist - do a hard replace - Wayne and John are working together to cross share knowledge - Eric - question about a build (manual process) vs an auto merge or auto build process - Wayne - the more servers we get, the more time consuming and demanding the processes may be - trying to get to the automated testing levels (becoming a given) - Light talks about file corruption and cascading bad code - We have very interlinked code that is complex and has multiple usage modes - we really need the testing - Some of our issues are singular... meaning they happen once or once in a blue moon - in general, most times thing flow pretty well - There was some talks about different branches, staging servers, testing servers, etc. It still comes down to time and efforts. - Our model gets even deeper, once you add all of the custom stuff per server - The Wayne and John (virtual partnership) is going to get a second pair of eyes on the processes. Getting a different perspective. - We have a Cloud Flare filter and/or blocker. That is good and bad. We are getting timeout issues when certain pages take a long time to load. - Cory and Shari O. popped in and were talking about client needs and wanting to get to their data, even it it takes a long time. - Steve was chiming in and talking about clients and their needs and being able to provide the data and services that they want. - Wayne was talking about other threats that we are facing, including outside threats, hack attempts, and traffic outside of our direct control. - We can't turn off the security to allow for clients to just have full access to their servers. - Wayne was proposing that we look at the long running reports and pages and try to fix those pieces. Steve was then talking about how much time and efforts that would take to fix and modify those pages and reports. - We have some pages that need page specific settings. Currently Cloud Flare (the frontend filter) has server settings but not page level settings for timeouts and such. - Some of our efforts need to be on optimizing code and reports to make them run faster. - Talks about security and firewalls. - Updates on some of the bigger or global projects (big tables and prepping for cluster models). Wayne and Alan were talking about servers, code changes, and getting deployment and testing options. - Emails and talking about mail servers - Trying to work more as a team, communications, updates, and helping each other.

	Shop 7310		Bug fix	1/5/2021	I got a call from Shari O. about a small bug in the older classic version for sub inventory. Both John and I jumped on a GoToMeeting session and made some changes. We pushed up a new file to fix it.

	Shop 7337		project planning	1/12/2021	Working with Shari O. on barcodes. Then working with Bryan on planning to make a plan for the flex attribute reporting project. He is working on doing some prep work to help with project management tasks. Plans for making a plan.

	Shop 7258		Adilas Time	1/13/2021	Working with Spencer, John, and Shari O. on pushing up and testing new Flash conversion stuff. Tons of emails and text messages.

	Shop 7178		Working with Shannon	1/19/2021	We started out our meeting and Shari O. needed some help getting into some of the new servers. We got her taken care of and then jumped into the questionnaire summaries. We finished up the question 18 about marketing and sales strategy and moved on to question 19, dealing with techy stuff and where we are headed. See attached for our progress.

	Shop 7259		Adilas Time	1/27/2021	More testing and printing 1099's for tax year 2020. Shari O. joined John and I for the testing session. We would make changes, push up new files and she would test them with us. Lots of back and forth.

	Shop 7275		Projects	1/28/2021	Meeting with Shari O. to talk about cross corp sales for stock/units. This was a huge blast from the past. We went over corp-wide settings, permissions, wholesale cart builders, etc. Kinda fun. See attached for some special links inside the classic shopping cart that made the cross corp sales possible. After Shari O. and I finished up, Steve joined us and we went over finances, servers, plans, and current payables.

	Shop 7478		Adilas Time	3/17/2021	Steve and I were brainstorming on a list of needed projects that we want to get done. We made a list so that we could show Mike a smaller tick list. We have hundreds of projects, we just wanted to put down some simple one liners, on a spreadsheet. Helping Marissa with some 1099's for her lawn care company. After that, Steve and I did some work on some clean-up logic and talking about the process that was needed. Shari O. popped in and was asking about helping to take care of the adilas family and their personal needs. She is very kind and considerate. The final thing that went on this morning was Shari O. doing some training to help Marissa with transitional invoices and how those work and help in certain scenarios, especially when we get deposits or pre-payment on invoices for work that has not been billed yet.

	Shop 7655		Tech support	3/31/2021	Shari O. joined the meeting and had a tech support question. We ended up modifying some code to help with the issue. Pushed up code to all servers. We also talked about adding in digital signatures and dates for our PDF documents that we populate and/or control through the system. We would love to keep taking things to the next level on the digital docs. Eric called over lunch to talk about his aggregation project for daily sales tax totals per location per day. We talked about the po/invoice line item date and when that changes and how to virtually trigger events based on changes. We were talking about simple strategies as well as deeper update and logic checks for things when they change or get updated. He is making some great progress.

	Shop 7500		Adilas Time	4/5/2021	Nice weekend. There were quite a few guys and gals on the morning meeting this morning. There was an issue over the weekend with special characters in some batch names. We've had problems similar to that before (different section similar issue). Certain key field really struggle if they have special characters. We have to URL encode them, escape them, and even deny the users if they try to use them. Certain fields are fine, but other key text fields really struggle with certain special characters. Some of those special character are things like: ('"%^+=<>#) Eric popped in and had some questions about the new sales tax aggregates. He and Steve were having some good conversations. We were talking about combo balance sheet items with both system maintained and user-maintained parts and pieces. Almost like a buddy BSI type relationship. It is so interesting how we have to mix things. Shari O popped in and asked questions about the data 9 server. We had John reset some database and Adobe ColdFusion servers and it seemed to resolve itself. Welcome to a Monday morning!

	Shop 7581		Weekly Server Meeting	4/13/2021	Server meeting with Wayne and John. We talked about all kinds of things. Shari O and Cory joined us as well. Pretty much just a Q&A session for about an hour. Good meeting. Some of the topics were new servers, old contracts on old servers, FTP, text message marketing rules and regulations, moving and migrating servers, progress reports, and unit testing.

	Shop 7703		Adilas Time	5/3/2021	A few more guys and gals joined the meeting at 9 am. Still working on getting all of the domain name changes populated through the system. Talking with Danny about custom labels. Cory, Shari O., and John and Wayne were on and off the meeting at different times. More database changes to help with the domain name changes. Pretty deep. That was a major change. Wayne popped back in and we added some things to his auto deploy script to manually flush certain variables. Steve and I then looked into some looping logic on some of his custom pages. Busy morning!

	Shop 7809		Small bug fix	5/4/2021	Fixing a small WordPress error on the news and updates page with Shari O. WordPress changes their API socket output and we didn't know. We had to put some code around some of our output.

	Shop 7779		Brandon, Shari Steve Cory conference planning	5/10/2021	Shari O., Cory, and I on a planning meeting for the training event that is coming up. We met using GoToMeeting and going over some planning and Google docs. We talked, did some planning, and then made some assignments.

	Shop 7798		Conference details meeting two	5/13/2021	Shari O., Marisa, Cory, and I met and talked about the upcoming adilas training conference. We went over some topics like pricing, planning, catering, food, budgets, and scheduling. Lots of good stuff.

	Shop 7791		Brandon and Cory projects	5/20/2021	Great meeting. We went over a few projects and follow-ups. Then we switched gears and talked about the upcoming training event and conference. Cory was reporting on what plans she, Kelly, and Marisa have been up to. They are doing a knockout job and getting everything prepped and planned out. I'm excited to see how it goes and turns out. My props go out to Cory, Kelly, and Marisa. Also some props to Mrs. Shari O. behind the scenes.

	Shop 7813		Info graphics for training	5/25/2021	Emails and pushing up some new info graphics to the photo gallery page. Signing up for lodging for the upcoming training event and conference. On the phone with Shari O. going over plans and details for the conference. Talking about flyers, hardware, projectors, power supplies, snacks, meals, handouts, schedules, etc.

	Shop 7944		Group planning for the conference	6/5/2021	Zoom meeting with Danny, Kelly, Cory, Marisa, Sean, and Shari O. to go the last minute details and logistics for the training conference. Brief overview of the training slides that will be used. The ladies did a great job on prepping the content and training materials. Kelly went over some of the slides and the timing that we are shooting for. Great back and forth with lots of input from the different parties and persons.

	Shop 7765		Adilas Conference & Training Event - Salida, CO	6/7/2021	Multi-day conference in Salida, CO - birthplace of adilas.biz! If you spell Salida backwards, you get Adilas - All Data Is Live And Searchable Small Recap: The adilas team meets almost everyday via GoToMeeting and Zoom meetings (virtual online meetings). Having said that, we have not had an in person conference for almost 3 years. Our last major conference was in September of 2018. The live event was much needed. The adilas team met up on Monday evening and did a small meet and greet - ice cream social. We then went over to the hotel and conference center. We setup up systems and did some testing. Crazy, but sad, the hotel was having major Internet problems. We setup some mobile hotspots, but it just wasn't enough. Tuesday morning we started the conference but the Internet was super slow and was dropping the GoToMeeting session, audio, recording, and even basic site browsing was going super slow. We tried using the GoToMeeting options for the first two sessions. After that, we ended up just presenting to those who were on site. There were about 20 individuals there on site. Once we dropped the GoToMeeting piece, the whole attitude of the conference shifted. From my personal opinion, the change was for the better. Much better flavor and things started to flow much better. We had more folks join us live on day two and day three of the conference. Great stuff. Those who were there were treated good and everybody was learning new things. As a huge shoutout, three ladies spent a ton of time on training content, slides, and presentations (including timing, samples, etc.) Marisa got a bunch of shirts for adilas with the little blue dog avatar (ADI). The guys and gals looked great in the adilas shirts. As usual, Mrs. Shari O. took great care of us and had snacks and lunches for us each day. /////////////// See attached for some of my notes... I will also put a few of them there below for searchability. My notes that are attached have a lot more details. I just wanted to capture some of the tweaks and user requests that we picked up from the conference. Not all of my notes are just what needs to be updated (for the record), most of my notes were dealing with what the guys and gals were presenting: - Request - We should not allow new default payments as "show" they should be hidden by default - this is dealing with money types under more options under the corp admin page. - Request - They wanted Venmo as a payment type - Request - Remove the Flash option for my cart favorite buttons - under personal profile - They went through all kinds of setup and settings - being consistent to get things out of the system later on - Request - Adding in a date picker to the add/edit pages in elements of time. It is currently there, but if you have the HTML enabled SummerNote editor, there is a conflict between the two features. They both use a form of jQuery. - Small side note on the presentations - Kelly was doing slides on a PowerPoint, Marisa was driving (clicking through adilas), and Danny was presenting - fun combo and good flow. - Prototyping and then expanding those things - Request - On the customer log notes, try to add in the date pickers and the SummerNote HTML editors (small conflict) - Request - On the balance sheet quick search - be able to pull the balance sheet by that date, using the quick search. That would be pretty cool! - We sure want to get back to a project called "known issues report" - Helping to find things that are known problems or disconnects - Request - On sub inventory templates, it needs to default to active. Currently it defaults to inactive. - Kelly and Steve did a great job showing some down the road cause and effect relationships for categories, inventory controls, and other sections in the inventory controls section. Great little session. - Request - On the advanced part and parent attribute search - They may or may not want some of the inactive parent attributes on that report. In the Farm and Ranch demo site, there were tons of inactive parent attributes that were showing up. Small clean-up. - Use of the word core - parent cores, child cores, etc. - Request - On smart group buttons, the description modifier does not currently change the sub description. It only changes the parent description. It should change the sub as well. - The power of being able to save your own reports - Save time and money, adilas has a solution built-in (talking about ecommerce, but it could be anything) - Request - On ecommerce, change some of the verbage on the photo image sizes - make them square (item pictures and item category pictures), if possible. Say something like 750 (_w) x 750 (_h) vs 750 x 553. Square works better on the web, helps make it all line up correctly. - Request - On ecommerce, the parent attributes on ecommerce show all items with certain tags. We need those counters to filter what was/is really available - For example: Drinks(2) - but when clicked, only 1 (one) showed up. It would be better to show Drinks(1) and then show just that one. That shouldn't be too hard to fix. Maybe just look to see how those item counters and counts are calculated. - Request - On login into ecommerce, it would be so awesome to have a new setting to say - Where can we take you after a valid login? My details, shop home, make a payment, etc. that would be cool! Basically, let the client/users dictate where to send their customers upon a valid login. Right now, they always just go to a single page and then have to click from there where they really want to go. - Request - Build a customer marketing link builder page, this would be a page similar to the add/edit my cart favorite buttons (limited), but thte main feature would build a link, add to cart, set a discount, tract a campaign, add a coupon, auto login, etc. Build whatever link you needed, without knowing all of the techy stuff behind the scenes. Make the links so that they may be used in marketing messages, emails, texts, ect. The person who builds it, enters info into a form and the form (backend logic) builds the correct link for the client. Basically a special marketing or link builder tool. - Request - Add some terms to the glossary such as: Modal, ADI (the blue dog avatar). - Request - Make the "all help files" more flexible and be able to search the descriptions as well. Currently, it only searches titles for the help files. - I can't wait until we can show the daily balance sheet over time - multiple day report running over or off of the aggregated totals - Request - Look into the add new B.S.I. item process - We may need some more flexibility on the account and item groupings. Also, a request was made to allow for setting up the expense types and deposit types right from there as well. Basically, a one-stop shop for balance sheet setups. - The value of education and being able to help set people and users up for success - Understanding logic and cause and effects - Idea - It sure would be cool if due dates could show up on a calendar type view - think of showing all kinds of stuff on a calendar type approach or view - Request - New settings - Expense/receipts and locations on line items. Also, B.S.I. bump up or down values. More settings. - Take time and read the page errors and info stuff - We are trying to help - Slow down just a bit - There is a need for some cash flow and budgeting tools - This would be awesome - Maybe round 2 on the financials - Request - Ice-down dates and being able to "post" on invoices and PO's - Posts only exist on deposits and expense/receipts - Data visualization and customized dashboards - We haven't even scratched the surface yet - It's time! - Request - On the media/content homepage and media/content advanced search pages - It would be nice to output or show the reports in Snow Owl data tables to help with exports and visual displays - Following your interests and be yourself!

	Shop 8232		Internal adilas meeting - part of the June training conference	6/11/2021	On Friday, June 11th, 2021 we had an internal conference day for just the adilas team. We went from sales to internal code to ideas and plans. All over the place. See attached for my notes. Many great things were discusses. Once again, this was an internal team meeting, but we don't mind sharing what we were talking about. :) ////// The attached notes are better formatted, but I wanted to push some of them here for searchability: ////// Group Sales Meeting Marisa, Danny, John, Cory, Sean, Steve, Dustin, Shari O., Dawn, Brendan, Steve (mac), Brandon, Chuck, Alan, Kelly, Bryan - Kelly was saying that there is some public records per states - We may try to pull our own list - Questions... who, what, where, how good, etc. - Maybe look at a sample of 10 - We may need a more focuses approach - What about different industries? - We need to get the name out there - Kelly was pitching a social presence - Do we know anybody who wants to do the social stuff - Word of mouth - Testimonials - Some new video graphics - To the penny, to the gram, every day - What about small streaming commercials – focused and pointed - Kelly recommends that we maybe focus on a slightly larger pool - Dawn – maybe focus on start-ups or that small to medium range - Get them at the beginning – maybe even tradeshows - It is a pain in the but to switch over – pain creates options for change - Focus on services... deployment, oversight, consulting, training, best practices - How can we deploy something easily and repeatable? - It is tough to get some of the people started, but once they get all in, they tend to stay - Kelly has done this over and over again - Using the professional resources that are available - From Kelly – Help get the clients all the way in – full system and platform - Getting the success on the first implementation and then building from there - What about focusing on those who are having trouble and/or are struggling - Dawn loves the support, training, and feel good part of it – duplicate that feeling to others - How quick can we respond – we jump pretty quickly on custom needs, development, training, and support - Get more testimonials from our clients - We have some experience to offer to those who want it - What about pitching best business practices - It's ok to be non-traditional - Being Relevant! - Focus on helping over sales – from Steve (mac) - Simple things that bring the relevant pieces - Social webbing – group effort - Danny, straight up, I don't want to be the social media guy! We have to find the right person and/or persons (small little team) - We are not QuickBooks... what does that mean? Be our own style! - Packaging this platform based on the target audience - Formulating a plan – ease the lift – maybe a monthly meeting with some planning - Influencers and YouTube options - Small info tips... - New age marketing – we have to play to the current market - Big Dumb Animal Pictures – super simple - We have to do a cost analysis to see which one(s) make more sense for us - John, what if we setup our own little social piece (aka maybe the adilas cafe) – we could allow all of our users and power users to pitch and promote – we may need to approve things, but we have tons of very knowledgeable people and users - We are looking for engagement – back and forth – a relationship – maybe get an intern to help handle this - Danny – Switching over to the modal message marketing - How to save the app to your phone - Make the email piece better - Small web tool to help with building special html links to embed promotions, direct add to cart, discounts, campaigns, etc. A simple form to help with the backend tech of those URL's and web links. - Maybe, we need to upgrade our email platform. It is a small holdover from years gone by. - What about the delay on the outbound emails? - Marisa – maybe outsource things as needed - Steve – would like more input on the bulk tools - Better filtering and target marketing - Steve wants to work direct with Dawn and Branden - Matrix and target marketing – even predictive - Maybe a little itty bitty (super small) native app on the different phones – iOS, Android, etc. - Steve wants to get into possible predictive marketing - Steve – looking for great feedback and even ideas and dreams... - Archiving, saving for later, dismissing, etc. We have the data, what do we want to do with it? – Wet clay... - Danny – Going back to past clients - Version 1 vs Version 2 – type attitude - What kind of clients do we want? We may not want certain kind of clients. - We love people who like details and are willing to play - We love people who take things to the fullest level - We love people who just need a small little piece – there is a gap in their current model and they need some help. We can then grow from there. - Do a full comparison of what we offer - Pitch what we do differently – we help deploy and maintain your ERP - White glove approach - Playing with the tools that we have and flipping those into marketing messages - Chuck – maybe check out some groups on Facebook - Blog posts, articles, info snippets, quick videos - Talking with Kelly – how have we helped small businesses become bigger or big business – showing the potential – dreams to reality - The small goals to achieve – steps to get to the next level - Small goals lead to bigger goals – getting some small successes along the way - Clients and expectations – not all money is the same – budgeting and planning – what kind of client do we want - Reoccurring revenue vs one-time revenue - A quote is just one of many pieces that needs to be done - People, skills, and cogs in the wheel - We all care... where would you and your skills fit in best - Seeing the bigger picture - Maybe looking at personalities and figuring out the mixing and blending of our options and resources - Slowing down and taking the time to see where we are at? Virtual time travel – child, youth, adult – as a company - What's the difference between a goal and dream? A plan! - The internal group summary that we did... a great start /////////////////////////////////////// Second session - Servers & Infrastructure - Refining Our Processes - Tech Support & Training - Project Management Steve wants us to show the online label builder - We had some good talk about where we want to go - We pointed to our internal summary report - Steve McNew – helping with the strategic marketing plan, technology road map, timelines to position, plans for action - Scale – can we grow and can we shrink - Conversation between big and small – perspective – big and small (sales, number of team members, lines of code, etc.) - Molly – Is adilas the big guy or the small guy? Think of code (lines of code). We could be considered a big guy if you were looking at code and functionality. - We like being small (ish), but what if we are big already - If we want to grow, that means that we want to get better – grow in a good manner and sustainable manner - The underlying services that support the whole - Be your own style! - Steve McNew – old classmate with Steve Berkenkotter – guest speaker – part of the adilas team to help us get some things more standardized – processes and procedures - Defense contractor for the military – 28 years - Testing, software, management, auditor - He has already called, interviewed, and talked with a number of different team members - He did a 20 page audit and report on what he was seeing - Getting into some testing and processes – he would like to see more of this - Not trying to derail the train – we are trying to polish the Ferrari (spelling – awesome car) - Whitepapers – catering to a higher audience – going beyond stick figures and into technical docs – not everybody will want to read some of these, but there will be some that require it - Steve B – if we try to sell our product to those who can't afford it, it doesn't really work. They have to be able to pay for what we do (really do – billing for our time and efforts) - Fin-tech – financial technology - Using whitepapers as part of our marketing plan - John M – unit testing – confidence of the developer team – currently only Wayne and Alan are doing this (unit testing) - Going to ease into this – refining our testing plan - Version control and when do we update these systems? The older way was wild west... we may want to figure out some specific micro builds. - It would be nice to keep track of the versions and options. - The balance between core and custom development - The application needs some spring cleaning – what is being used, what isn't, what is going slow, etc. – Refactoring - Priorities – customer priorities or our internal priorities – what is the mix and blend of these pieces - We all ware many hats... we may need to define that so that we don't overstretch ourselves - We all use (and can use) the system in different ways – how do we translate that information to our clients, other developers, and other team members (upstream and downstream) - 2 minute videos – no more - Work instructions – even giving it to someone who has never done anything in the system - Danny – Shoutout to Steve and Brandon – we have done great – what is coming next? Resources? - Talks about earn and burn ratios - Prices have to match the services - We are a growing business - Kelly – going from 1.5 to 10 (millions) – that is a huge change - We are competing with companies that are hugely funded... what do we want to do? - There are some real things in our path – there is tons of potential – what do we want to do with it – also, sometimes there is shelf life on potential or advantages - We don't want debt – however, there is a time for debt – cost analysis and being smart about it - Making choices, but also being willing to fail - Marisa – look at our new website - Steve – there are some percentages of adilas that are available – not looking for vulture capital (just being silly – vulture vs venture) - Someone looking to take on some risk but helping us to get to the next level, without taking over the company - Kelly – pitching our vision and business plan – we have to define the vision – Danny seconded the define the vision before looking for the funding – goals, sales, budgeting, maintenance, and getting a business plan. - Adilas Trust option – co-founders - Possible option – Maybe take some of IP (intellectual property) and sell that to a new entity and then restructure those new pieces - Dustin – thoughts on corporate structure – we are all on our own little islands – Ferrari to a tricycle – frontend compared to backend – splitting up those pieces and functions – he wishes that we could be more collaborated. - John – teams and buddy projects – small sub teams – full stack (all levels) vs specific skills or somewhat limited skills – this needs to be part of our plan. - Sean – we already have some small teams that are working on some of these projects – cogs of the wheel – buddy tagging the workflow and processes - John – the adilas docs project – and being able to go to it and also add to it – working on standardizing the pieces – filling in the gaps - Danny – Navy Seals – two is one, and one is none – at least two on a project – two-by-two - Kelly – scale – having a back-up - Danny – accountability back and forth - John – confidence levels - Kelly – what about a succession plan? - John and Dustin – real life buddies and how they help out each other – seeing a different angle or perspective - Marisa – tooooooooo much weight gets put on single persons - Kelly – relieving pressure and helping with scale - Marisa – Cory, Kelly, and Marisa – wonderful training slides, presentation, and delivery for the conference. Awesome job! - Alan – modularize things – able to be reused – code concepts can relate to business functions – one to many relationships – translating knowledge into real life and different scenarios - Chuck – last summer Chuck was on a joint project with he, Russell, and a different John. It worked out awesome – Keep pushing towards that kind of rollout of the project - Molly – thinking and coming up with ideas. Keep it going! ///////////////////////////////////////////// Next Session - Deployment & Oversight - Design & Layout - Internal Core Development - Custom Development - Deployment – where are we going and how can we make this all work – team effort - Shari O. – first touch and setup corp, Sean and Shay first hour or so, Sean helping to coordinate the next steps and pieces - Sean does a great job of reporting back - Report on things, record the notes, get back with us to help us keep pushing - Doing great with testing and prototyping - Kelly – who is on settings, who is on planning, maybe even looking at pre-deployment options - Before Kelly even does a demo, do some consultation – figure some things out without doing any pitching or selling. This is called listening. - What are you looking for, wanting, expecting, hoping for? - Make the demos custom to the pain points or key wants and needs - The prep work is huge to help them be successful - This platform is not a turn on and go type system – there may be pre demo, consulting, custom planning and demo, then custom hand holding to get them going down the road - Picking the point of contact... who is going to own this thing? - Owners, managers, and users - Users want the easy button – Steve calls this the tail wagging the dog vs the dog wagging the tail – what is and how can we get buy in? - Tools are great, but solutions to problems and pain points are even better - Give to get! If you give too much, it can get you into trouble. - What is the cost to fixing things... on the other hand, failing does help with major learning – there has to be a balance - We tend to remember pain – setting people up for success - Often users are looking for a quick switch. This system takes work. Please sell it that way. - Not going to custom too quickly – learning the manual way – then automating it - User buy in – light pain and then helping them learn a better way - Change proposals and scope of work – setting up boundaries - Feature creep – setting that scope of work – cause and effect of what they want and what they give – expectations and timelines - Sometimes I start with NO – interesting - A saying no - sandwich... Yes, I'd like to, no, I can't. Yes, I would love to help do this... - people think that no is a bad word - Having a plan to say yes, vs just saying yes - We like to please people – that is awesome – what does that cost? - Help make the plan to say yes. Maybe, no (first), however we could do this... - Making things repeatable - What are the internal costs to do deployment? - Say $350 for a setup fee – does that cover it? If yes, great. If no, where does that put us? - Maybe on the setup, prep, an activation fee (define this – turning on the lights), setup and deployment fee (range), training, custom code, imports, labels, etc. - We like to cater to everyone – that had bitten us - Actual prices and then use discounts if needed. You can't really ever raise a price after the fact. - Back-up our prices - Use adilas to run adilas!!! This is our communication tool, let's use it. - We are good at the dreaming and software building part of things, we need some major loving on the service side - There is demand! - What pulls at our time - It is time, money, skills, etc. - Kelly – earn has to be more than burn - Flipping the demand to sales or services that could be provided - MVP – minimal viable product, plan, player, etc. - Intangibles ///////////////////////////////////////////////////// Next Session – Show and tell! What are you working on? Calvin – Advanced file and folder finder, resize images, convert images Brandon – harvesting assets from element of time Steve – parent attributes report, items not on a recipe (manufacturing), modal message marketing for customers, log notes for vendors and employees (payee/vendor logs), backorders homepage, mini units, auto add item (quick PO behind the scenes), bulk update on the vendor – master copy paster... :) - Branch 122 – fun Bryan – cfqueryparams – stop SQL XSS (database hacks – cross site scripting) - SQL injection – converting from dynamic queries to secure dynamic queries - Example: Corp_id = #Trim(some form or URL var)# or Corp_id = <cfqueryparam etc, etc,> - this stops the SQL hacks Bryan is also working on eChecks for eXPO, Hypur checkout in the shopping cart (eComm), new API's for delivery (with documentation and samples) John – Payroll project to allow holiday date picking, timecard flags, timecard totals (pre summing the math to go faster and lead towards bulk payroll), new timecard reports showing grouped sums and totals. Page templates and style guide defaults with Chuck – Going from old school tables and links to the newer grid and mobile ready code. Part of the adilas docs project. Build once, use many (effective copy and paste). Basic templates (3 new ones). New information icons and popups (modals). Style guides and usage of those pieces. Servers with Wayne Chuck – Huge new web site!!! Awesome Job!!! Global Design Dashboard, adilas docs, and new presentation gallery (sales tool). Danny – message marketing, custom labels, sales team meetings – hats off to all of us! Keep listening and keep finding solutions. Open table – follow your highest excitement and be yourself! Be happy! Alan – enterprise level catalogs, refactoring code (custom page settings), standardizing code for speed and reliability. Random comments – Cory really liked having access to all of the team members, right here at the conference. Marisa – great to meet everyone – keep floating the boat. Sean – he likes the team. Molly – loved watching and wants to be involved. Chuck – idea of everyone joining slack

	Shop 7909		Steve, Cory, Brandon-Catch up on projects and updates	6/21/2021	Cory and I had a good work session. We were looking over limiting view invoice permissions. It seemed like it wasn't working on the new invoice homepage. We did a little bit of research and reached out to Alan. Next we talked about some bug tracking options and we determined that we would track them under one element of time and then just use sub dates and times to do the actual but tracking. We went over a few scenarios and did some playing around. Our next little work session was talking about costs and revamping our quote spreadsheet. We made a detailed view and changed things around. We also made a super basic view that is quick and dirty. We are hoping to use the quick and dirty one for projects under the $1,000 magic line. We have a number of quick $300-$750 projects that will fit nicely in the basic view. It seems that once a project crosses that magic line of $1,000 - we have to really up the game as far as what is needed, requirements, features, etc. See attached for a copy of the new quote templates (spreadsheet) Shari O. joined the meeting and Cory and Shari O. talked about clients and accounts receivables. Nice little meeting.

	Shop 7927		Projects	7/20/2021	Working with Steve on some string manipulation practice for a process where he was pulling out the recipe/build id number from a bunch of notes and user inputs. Shari O. joined and needed some help with some internal email stuff and getting rid of some old ones and adding Sean and Cory as new email users in our custom internal email programs and app.

	Shop 7880		Work with Shannon	8/3/2021	Multiple different meetings within this time slot. First off, Cory and I spent some time going over projects and making plans after the earlier meeting ended. Lots of reporting in, circling around, and doing follow-up on different topics and projects. Steve and Cory were touching base on production (manufacturing) stuff. At some point we have to turn things over to the people who are doing it (meaning our clients). We can't hold their hand forever. Eventually, the subject got back to deployment and who is doing what. We do want to take care of our clients, but we also can't babysit them every waking hour without charging for that service. Shannon joined the meeting and she and I worked on brainstorming on adilas core concepts. We spent most of our session on permissions and settings and recording ideas, notes, and brainstorming on those fundamental concepts. We often say that adilas is built on a foundation of permissions and settings. That keeps expanding and rolling along as the whole thing unfolds. Very interesting. See attached for our ideas, progress, and notes from our brainstorming session. Shari O. joined the meeting and had some payroll, internal audit questions, and email template questions. She and I went over a small questionnaire and chatted about independent contractors, independent developers, and independent reps/consultants. We then looked at some bank registers and fixing a small error on the save as PDF page for bank registers. Busy couple of hours.

	Shop 8077		Wayne, Brandon John and Cory server meeting	8/5/2021	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.

	Shop 8126		Drew, Brandon and Cory shuttle biz strategy	8/23/2021	Got on a GoToMeeting session with Drew, James, Shari O., Cory, and myself. Drew and James are looking at using Adilas to track and handle all of the business side of a shuttle business for the Monarch Crest Trail. Both are long time friends and we all worked together up at Monarch Ski and Snowboard Area out of Salida, CO. We went over tons of options. I was driving and Drew was mostly asking questions. We did a small dog and pony show, some show and tell, and took some notes. Lots of drawing on the screen and explaining how things need to go and flow for it all to work out. We talked about the ecommerce side (customer portal) or section as well as internal adilas (backend secure options) flow of the data. We talked about customers, profiles, invoices, invoice payments, scheduling, time templates, mapping, and tying all of those pieces together. I think that this will be a fun project and will get elements of time out in ecommerce land. Looking forward to pushing on this project. As a side note, it also includes email and notification options, digital waivers, cancelations, user day tally marks (quota of people that they can take on the shuttles), and eventual check in functionality. It should be pretty fun.

	Shop 7999		Server meeting	8/24/2021	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.

	Shop 7993		Server meeting	8/31/2021	Cory, John, and Shari O. showed up for a server meeting. That didn't really happen. We all ended up doing our own thing while we were waiting. Towards the end, Cory and Shari O. bailed out. We were hoping that Wayne was going to join, but that didn't play out. I was working on some small bug fixes, flipping through the presentation gallery, exploring the different themes, etc. I ended up merging in a pull request for John dealing with the date picker and small verbage changes. John and I talked about full stack developers and characteristics of the full gamut of what we do and have to do. We have to switch between frontend, backend, system admin, content, marketing, sales, HR, project management, graphics, design, etc. All over the place. We ended with some training on expense/receipts and the differences between splits (payments on account) and REI's (reimbursements). The main difference is how they get paid back and where the funds come. There are also some differences on end of the year 1099's and who pays taxes on what. Light training and did some drawing on the screen. Thank goodness for GoToMeeting and the drawing tools (ability to draw right on the screen, change colors, and erase as needed).

	Shop 8147		Adilas Time	9/23/2021	John was reporting on the size of the different database. That was awesome to see. Shari O. joined and needed some small updates and help to setup some new credit card processing accounts. We got her all setup and good to go. Working on the Bear 100 large photo gallery page. Text messages, emails, and other to do list stuff. Pushing up code for Bryan and then back on the Bear 100 mobile first stuff. Working on aid station stuff.

	Shop 8145		Adilas Time	9/27/2021	Shari O. checked in and was asking about server sizes and what servers have space or availability. Database sizes and data counts (how many customers, invoices, deposits, expenses, PO's, users, vendors, elements of time, inventory counts, etc.) per server and per corporation.

	Shop 8148		Adilas Time	9/28/2021	Danny, Sean, Steve, and Shari O. were talking about sales and strategies. Good stuff. While they were doing that I was working on emails and follow-ups. This is from Steve - He said that his mom had a sign in her kitchen saying "If at first you don't succeed, ask your mother." Kinda funny! He was referring to us, both Steve and I, talking with our wives and getting some great advice and direction.

	Shop 8349		General	10/4/2021	Small data fix for Shari O. on un-posting an expense/receipt inside of adilas. Posting is kinda like a final lock-down. There are no tools to un-post something currently. I was asked to check on a data dump for Euflora and added a number of parent attributes to the custom data dump file. Pushed the file up live. I also merged in a file for Dustin, pushed it live, and sent him an email with some suggestions on some of the logic.

	Shop 8292		Adilas Time	10/13/2021	Everybody was scrambling this morning, as the servers were down. It appeared to be a routing issue, upstream from us. We had Marisa, Cory, Sean, John, Shari O., and myself on the meeting. We also had Bryan join for a bit. Steve was texting back and forth, and Wayne joined and gave us more information as well. The whole tech support team was answering emails, text message, and trying to help pass on the information that we had. Great team effort. The sad thing was, we couldn't really control all of the variables. The routing problem was even above the data center or server farm level. We fix code and can tweak a few things, but if the main highway is broken, I don't care how good your vehicle is, it just won't go. A few small lessons learned... We were trying to send out an email blast, but most of our data was on the primary adilas.biz servers and we couldn't get to it. We did have some older exports of our client list, but it was a few months old. We also updated some files, through FTP, but the caches weren't being updated. Interesting. As the time progresses, we kept fielding calls, texts, emails, etc. Wayne and John were doing a great job bouncing around and checking all kinds of different maps, up/down internet sites, and even bouncing to different countries to try to access our sites from different IP addresses and access points. Pretty crazy.

	Shop 8525		Adilas Time	12/13/2021	Steve and Sean were talking strategies and talking about some client needs. We have a number of clients that have a ridiculous number of inventory items. They need help either importing those data pieces or being able to provide us with lists and we then help them get them entered into the system. Shari O. popped in and had a few questions for myself, John, and Steve. She was checking on some of the year end forms, state payroll tax calculations, and other small items. After she was done, a number of other developers popped in and did a quick check-in and small update. We finished before 10 am and all of us jumped off the meeting to work on other projects. Lots of stuff going on.

	Shop 8594		check and push code	12/30/2021	Looking at some code with Bryan for the year end totals and save as PDF option. We made a few changes and then merged and pushed up the code. Shari O. had requested this feature, as she is the one dealing with 1099's and W-2's and other year end totals.

	Shop 8516		Adilas Time	1/5/2022	Small bug fix fest this morning. Wayne, John, and I were talking about bugs, custom validation, special routines, and includes, code aborts, and custom tags. We worked together to fix a small validation bug. Pushed up files and cascaded pieces to all servers. Shari O. joined the meeting and had a small question about some merchant processing and EMV/Chip reader stuff. Looking into some code for her. She will meet with Eric to get some deeper tests, as Eric build the function in question.

	Shop 8638		Projects	1/17/2022	Emails and tech support. Shari O. sent me an email about the forgot password section. I spent some time looking into that and pushed up a small change. I also got an email from Cory about a possible error with a PDF version of the income statement (P&L). Four of us jumped on the GoToMeeting session to see if we could fix it. We had Eric, Cory, John, and I working on things. We tried a number of things, but we decided that we would unroll some of the changes and get with Wayne tomorrow morning on what was merged in a couple of days ago. Lots of the new changes across the board. We were dealing with changes from both Wayne and Eric. Wayne's changes were on the application level and Eric's changes were on the sales tax aggregate level. Anyways, we made a number of changes and fixed a few things but decided to unroll the new changes.

	Shop 8521		Adilas Time	1/18/2022	Midweek sales meeting going on this morning. There were 10 people on the meeting. Marisa, Steve, Alicia, Audrey, Chuck, Danny, John, Sean, Shari O., and I were attending. Marisa was taking notes and she and Danny were swapping out and running the meeting. They launched a newsletter signup that is tied to news and updates. They were talking about leads and demos that they either have, have had, or are scheduled. Sean and Marisa are doing great and handling all of the demos. Shari O. chimed in a few times. They are tracking the deployment and training on the new accounts and new corporations. That is awesome. Once the sales folks left, Steve had some questions for Chuck and John dealing with CSS and page layout. Funny thing, they were trying to fix it and then Chuck went to the adilas docs and pulled some sample code out for Steve to use. What do you know, it fixed the issue. The cool thing was that the answer came straight from the adilas docs. Good job Chuck and John! Towards the end, Chuck and John were talking about options for imbedding custom videos per page. Good little discussion.

	Shop 8613		Steve, Cory, Brandon-Catch up on projects and updates	1/24/2022	Shari O. and Cory joined and were talking to John and I about server costs. I was impressed, they had a multiple page spreadsheet and were trying to really dial in exact costs and even semi associated costs. In the past, we primarily just looked at raw costs, and didn't take into consideration maintenance, monitoring, upgrades, and primum server support for our servers and boxes. Lots of back and forth. I'm excited to see us looking at real costs. We have flown by the seat of our pants for way too many years. We got pretty deep in to costs and what we gain from having Fusion Reactor and server monitors in place. We are being charged by the minute that those servers are being monitored. The costs stack up really quickly. We've quadrupled our costs in the last couple of months. We looked at ways to possibly bring that down or manage it better. John keeps bring up this concept of providing a white-glove type service for our big clients (tons of server monitoring, optimization, and access to reports and even system admin personnel). Anyways, just throwing things around. We were also getting into deep level configuration scripts and how to manage some of our existing servers and assets. One of things that we were talking about was dealing with old corps and inactive accounts (old or dead data) and how to clean some of that stuff up and make it faster and smoother. We talked about monitoring our clients and their storage levels, media/content files, number accounts, amount of data, traffic, and overall usage. We have some that we know that are big and there are others that slide under the radar because they don't call us or complain. We need to help those who want to play and charge accordingly. Some of our clients are so different, based on their habits, usage, and system needs. There was some talk about wiping data and starting fresh for certain sandbox and smaller accounts. We need to load up certain servers with more clients to make it economically feasible to keep certain servers up and running. Basically, manual load balancing and monitoring what clients are on what boxes and how those boxes (servers) are doing (sever health). We have some of the servers that we probably need to kill and get rid of them. The other option is loading them up with more clients and then really using them. We have a project out there that has and keeps circling around. It is called the datasource or world building project. Currently, we have a perfect one-to-one relationship between a data server and a supporting database server. We would like to allow for a single data server (code box) to interact with multiple databases, as needed. Make it more configurable. This datasource project would allow us to do those types of things. This has been referred to as getting our clients off the bus and getting them setup with their own virtual motorcycles (quick and speedy smaller databases). We would love to split some of these things up and make everything faster. Another big project is paring down some of the big corp-wide settings tables. We have two huge ones right now that are over 400+ columns (going across or horizontal). We would like to rebuild this system and stack things vertically (data records per setting - going down vs a single column going across or a unique field per setting). Anyways, this project keeps rearing its ugly head as well. We are starting to work on it (Wayne and John). The last section of the meeting got back to budgets, checking and monitoring usage and traffic, checking CPU's and RAM allocations per server, and adjusting as needed. Along with these budget type questions and topics, we would also like to look at possible up sales and offering other services to our clients. Including targeted or specific offerings to certain clients. Trying to harness more out of our existing clients.

	Shop 8662		Budgeting	1/27/2022	Working on some budgets and prep work for an upcoming meeting with Steve, Cory, Shari O., and I later today. Working spreadsheets on costs and trends.

	Shop 8646		Admin	1/31/2022	Steve, Cory, Shari O., and I on an admin and budget meeting. We were going over roles and who is going to do what. Our current admin team is going to be the four of us. Steve has the final say, but the rest of us have power and authority to help in the roles that we are playing in. See attached for some of our notes.

	Shop 8689		Talking with Eric	2/7/2022	Eric, Steve, and I got on a meeting. We started out by talking about EMV chip technology (retail or cart present merchant processing). Shari O. joined us for a bit to chime in on merchant accounts. Our new need is to have both retail EMV chip processing and online or web-based ecommerce type payments for the same merchants. We can do both, but not really with the same account type. We will be looking into options that allow for both. The goal is to mix the pieces - live retail and online bill pay or ecommerce orders. Shari O. left and just Steve and I were left. We chatted with Eric about options, lines in the water (virtual fishing or other things that might come to pass), accounts receivable (who owes us money), and how we are going to be dealing with paid projects and what not. The goal is to get a better plan and then follow it. We talked about a small shift in our model (bringing things in-house and the cost/value of that decision). See other notes for some ideas and what not. Great discussion.

	Shop 8696		Budget Meeting-Steve, Brandon, Shari, Cory	2/8/2022	Shari O., Cory, and I on a budget meeting. Steve joined us towards the end. Anyways, we started out and looking into doing some budgets per area vs some of the other budgets that were per person. There is a lot of cross-over but it was still good to see things being broken down in both directions (per person and per area or department). Once Steve joined, the meeting changed and ended up flipping more into things that needed to be done, project wise, and sales wise. Lots of moving pieces. We had an agenda but kept being pulled off course. We would circle around and then we got pulled off again. We are not used to being tied to an agenda and we tend to bounce a lot. We'll get better but it can be super frustrating. See attached for some of our other notes.

	Shop 8683		Adilas Time	2/23/2022	Shari O. was checking in and asking about corp-wide settings on the data 16 box. There seemed to be a problem with adding in a new corporation and having the defaults setup correctly. We didn't have time to fix that right then, but we asked Shari O. to send us an email and point us in the right direction. Sean and John also checked in. Once things quieted down, I went to data 16 and started looking around. I ran a number of older database updates. I also pulled up some data on the data 16 box and did some comparing to see where we were missing some defaults and settings.

	Shop 8804		Budget Meeting	3/1/2022	Budget meeting with Shari O., Cory, Steve, and Brandon. We started off talking about some of our A/R's (accounts receivables or money owed to us). We then rolled into sales, commissions, staffing, and talking about internal projects and decisions. There is still a lot that we would like to get done and/or finished. We went over some feedback that we've been getting on some of the new look and feel pages that we've been pushing up to the server for the snow owl theme. We talked about settings and how people want their own custom stuff. We also talked about coming up with some performance matrix and performance monitoring options for some of our guys and gals. We went heavily over budgets and had to make some cuts and trimming stuff. Towards the end of the meeting, we also went over rough timeframes and what we were thinking about for the amount of time some of these tweaks and changes will take to fully go into effect. Brandon has a number of spreadsheets and other notes from the meeting on his local computer. The notes were also sent out via email to all parties. As far as internal projects that were discusses, here is a short list: - Decisions on merchant processing. We have tons of options. We are looking to focus in and even specialize on USAePay for now. - Client facing scheduling - I was tasked with coming up with a plan and reaching out to a couple of clients to see if they have any interest in funding or helping with this project. - Other ones that got briefly touched on were - global or enterprise item catalog, cultivation and harvest stuff, invoice due date, auto collection on A/R's, custom labels, and a possible CSS (cascading style sheets) project to help with global look and feel.

	Shop 8790		Adilas Time	3/8/2022	Tuesday morning sales meeting. Marisa, Steve, Sean, and Chuck were on the meeting. Shari O. joined a little bit later on. They were going over email campaigns and planning some follow-up calls. They are just starting that email campaign for trailer dealers and dealerships. They were going over some planning and logistics. Lots of talk about using the existing adilas tools to help them track touches, contacts, quotes, invoices, and billing for time for deployment and other time-based services. Good stuff. I saw some great communication between different team members and all being on the same page. They will be doing some internal training on elements of time, billing, and what not to make sure that they are good to go. The last topic for the sales meeting was Marisa asking Steve, Shari O., and I about the floorplan application. Originally, we built that section of the site back in the Morning Stat Automotive days. We were reviewing some things and giving Marisa and Sean a general overview. They are going to be setting up some other internal training sessions to fully get their heads around it. After the sales meeting was over, Marisa had some questions for Steve and Sean about custom gram controls and other logistics for a demo later today. We also went over some inventory controls and being able to update inventory counts and inventory management tools (update PO's, delayed scanning, etc.).

	Shop 8796		Adilas Time	3/10/2022	Steve and Sean going over custom labels. I was showing Stee an update on the recipe/build functionality and the JavaScript auto calcs that I was working on. He wants me to keep going on the changes that we are making. John and Steve were going over some servers and making sure that we get things transferred over so that Shari O. can get those servers on auto pay. For some reason, we had one of the database servers get shut down. We got it back up super quickly, but we knew nothing about it until the server company shut it off. Shari O. will handle all of that, going forward. If the server guys order something, we'll just make sure that the server farm bills and sends out invoices to the correct parties. We don't want anything to get lost in the shuffle. Cory had a few questions for Steve and I relating to projects, accounts, and upcoming tasks. As a fun side note, Cory has been drumming up some training and other professional support services (invoices from adilas out to our clients for services provided). That is awesome and we are glad to see that starting to happen more regularly. We really want to be a full, one-stop-shop for all kinds of professional services (training, consulting, design, custom code, deployment, setup, data migration, support, etc.). Shari O. checked in and had some questions on servers, costs, and just catching up. We had to do a small server reset to see if some code would work better. Shari O. was trying to do a deposit from invoice payments, and it was not letting her do what she wanted to. After the server reset, the error was still occurring. We'll have to look deeper on that.

	Shop 8831		Fix	3/10/2022	Paying bills and following up on payments being made. Internal stuff for a loan repayment. Looking into a bug reported by Shari O. and making a deposit. We ended up having to trim or limit (cap) the notes section for deposit line items. The current values were exceeding the limit stored in the database. We did some force trimming and it worked great. I also added in a new corporation to the hardcoded list of enterprise corporations for enterprise corporation list. This small change was for Cory, as she had a client that needed some of the new enterprise and cross-corp functionality.

	Shop 8764		Budget Meeting	3/17/2022	Budget meeting with the adilas admin core team. Steve, Cory, Shari O., and I were there. I was taking notes and we got great input and comments from all parties. We followed up on some old business, then rolled into some new business. We chatted about maintenance, education, looked at budgets (spreadsheet work), and talked about some future and upcoming projects. Brandon has notes and spreadsheets on his local computer. Notes and spreadsheets were also sent out to all parties after the meeting was over. Making progress.

	Shop 8853		Budget Meeting	3/21/2022	Budget meeting for the SBA loan that we were able to get. Looking into sales, commissions, future automation, existing loan payments, and clearing out payables. See spreadsheets on Brandon's computer is more info is needed. Steve, Brandon, Cory, and Shari O. were in attendance at the meeting. Notes and copies of the budget spreadsheets were sent to each person.

	Shop 8845		Payroll Audit	3/22/2022	Steve, Shari O., Cory, and I on an admin meeting to go over an employee/employer audit. Looking into solutions and options to reclassify if needed. Most of our guys and gals work from home, use their own stuff, and control their own schedules. In our books, that is 1099 or sub contractor work. The state of Colorado wants adilas to be setup as a full employer. They do make a case but there are some big holes in it. We are going to be asking our CPA, other professional resources, and maybe even setting up a meeting with the auditor. We spent a lot of time looking at ideas on what we are calling the adilas trust (possible future company or company structure to help make sure that adilas is able to move forward in the future). We went through and did a list of pros and cons and what we want to do with our model and future company structure. Our model has already been changing. Lots of good questions and ideas. There are also a lot of unknown variables. Trying to figure out what path to take. We also talked about options such as: Fight it (appeal it) or just take it and move on. There was some talk about maybe forming an ESOP (employee stock ownership plan) type company. Cory was going to do some research and get back with us.

	Shop 8846		Adilas Trust	3/24/2022	Steve, Shari O., and I working on ideas for the adilas trust. Talking about ideas, options, and plans. I took some other notes and sent them around after the meeting. Steve will be meeting with our CPA on Monday to go over some ideas and options.

	Shop 8795		Adilas Time	3/29/2022	Marisa, Chuck, John, Sean, Steve, Shari O., and I were on the sales meeting. They were talking about their email campaign and making follow-up calls. Steve wants to get a ballpark figure as to how much that email campaign is costing. We would love to get a rough idea on the client acquisition costs for different industries that we serve. Chuck and Marisa were reporting on how they go in and search for contacts, numbers, emails, and build their own lists. Once we do that for a bit, we'd like to try buying a list of contacts and see which one is more effective. Basically, we are stirring the pot and virtually going on a fishing trip. What is out there? During the meeting, the question was brought up about current sales rep type persons. Checking in on different names, people, and who is doing what. Sean had some good info on some of the folks. After the sales meeting, Steve was asking John about some of his projects. Trying to help our guys focus where possible. After that, Steve and Sean were talking about a live system deployment where Sean is going to be going onsite to help with the full setup and deployment. The client has pre-paid for 20 hours of training and will be covering all costs to pay for Sean to be onsite for a couple of days including airfare, lodging, etc. That is awesome! We are really trying to recoup our costs with some of our new clients. On average, it costs us about $2,000 to get a new client on and going on the system. Steve and Sean were going over ideas on text message marketing and some possible marketing options. We are going to be trying to market more and more of our own professional services such as training, setup, data entry, deployment, maintenance, and consulting. We are really excited about that. One of the missing pieces is who is coordinating things and helping to orchestrate the sale and the deployment. Switching gears to merchant processing, we really want to figure out a standard procedure there and help get our clients setup with great rates and excellent service. We have tons of options, but we really want to focus in and offer a standard package. Part of our missing link right now is info from the merchant processors as to what kind of accounts and services are available.

	Shop 8781		Server meeting	3/29/2022	Server meeting with Steve, Wayne, John, Shari O., and myself. We talked about some scheduled maintenance on the data 3 box and database. We then talked about the amount of time it takes to run certain database updates (tons and tons of records). Both Wayne and John are working on a spreadsheet of where the server guys use and spend their time. Our goal is to figure out some of the things that they do and what kind of patterns we can glean from the process. Steve had some questions about being able to merge in corps from different databases into an already existing database. That gets super deep and can cause major issues. We looked into that years ago and ended up bailing out due to it being so intense and id number craziness (mixing and matching and cascading new and old id numbers through a system that is already in use). Tons of possible conflicts. We briefly touched base on existing projects. The server guys have been busy with normal life stuff this past week and didn't get much new stuff done. We checked in on the changes for the corp-wide settings and multiple datasources per server box. John wanted to know about a budget or allowance for server monitoring. We are trying to keep a tighter budget, but some things come and go (ebon flow). We talked about needs and keeping a good balance between what is needed and/or extras that just cost money. Along those line, Steve was asking Wayne and John if he could get some ammunition or good information on one of our clients that is kinda pushing the limits and may need to be upgraded to their own server. We switched modes and Steve was asking both Wayne and John about their thoughts and ideas on our company structure and what they would like to see and/or participate in. We got into a great discussion on what we are calling the adilas trust or multi member LLC, where ownership and percentages are distributed to some of our key players. Great discussion and I took some notes. The last topic of the meeting was trying to stay focused on a single project at a time. Sometimes, if we get too much going, nothing gets done or finished. Staying focused is a big key.

	Shop 8869		Adilas Time	4/4/2022	On the morning meeting, Marisa was showing us some sub inventory issues that need to be smoothed out dealing with sub inventory attributes and template settings. I was doing some emails. A question was brought up about New Mexico state payroll and state withholding. We used to have that state, we just need to circle back around and make sure that everything is updated and good to go. Shari O. and I spent some time going over progress with USAePay and getting information from them. We have both made multiple calls to our contacts at Newtek and haven't really gotten the information that we need yet. Kinda frustrating, we just want info on account types and how to help our clients sign-up for what they need. If we can't the info that we need, we talked about going in a different direction. Both of us will keep trying, for the time being. Switching subjects, Shari O. and I spent quite a bit of time talking about our transition from full 1099's for all of our guys and gals to the multi member LLC (partners and ownership) options. Eventually, we may need a hybrid type solution that allows for owners, 1099 folks, and even employees and W-2 folks. Still trying to figure things out there. As a note, Shari O. is recommending that we slowdown a bit and make sure that we have watched budgets, gotten documentation, and standard procedures in place before we jump too quickly. I showed her the adilas docs section, inside the adilas site, and she had never been there. If we do build out more internal flow and owner type handbooks, that is where it will go. It will be called our standard operating agreement or something to that nature. Shari O. and I talked about budgets, watching and tweaking those budgets, and then making some decisions. Lots of talk about timelines and timeframes for some of the upcoming changes. Good stuff. I'm super glad that she cares and is willing to ask hard questions.

	Shop 8899		Budget Meeting	4/7/2022	Budget meeting with Steve, Shari O., Cory, and I. Most of the meeting was done using spreadsheets and Word document that we have been adding to for the ideas and concepts of the multi member LLC that we are trying to get fully setup. - Steve and I talking about the cost of getting a client on the system. Often, they have huge demands, totally ridiculous. Often, there are even times that they have huge expectations, almost expecting perfectly wrapped, signed, sealed, and delivered products. Steve and I were talking about the expectations and ROI on those clients. - Levels of activation and setting a price tag accordingly. Setting the expectations and assessing their (our clients) needs. Seeing how deep we need to go and what we are dealing with. - As is or are we doing extras? - Steve was reporting on talking with Eric and maybe letting him take a crack at doing sales. Cory has some small development projects for him as well. - Doing a better assessment of what it will take for them (each new client) to be fully on and up and going. It may be a 5-10K dollar rollout vs a $500 activation. - Differentiate between training, setup, deployment, customization, consulting, and tech support. At the end of the meeting, Shari O. and I touched base on ecommerce terms and refund policies. We need to create a general page that covers different privacy policies, refund policies, and other terms and such for ecommerce. We have a client that needs that in place before the merchant processing company will release their merchant account. After that, Cory and I quickly touched base on some other projects that we are working on. I showed her a demo of the copy selected chart of accounts between corporations and we went over the next steps.

	Shop 8876		Adilas Time	4/13/2022	It was Steve's day off today, but he was still in there pushing on things. He was checking in and uploading new custom labels to data 16. After that, he and Dustin were going over some new CSS (display) changes for some of the pages. We helped Dusitn figure out some stuff with the CSS and data table switches. Cory and Shari O. were touching base on some small tech support issues. Eric joined and was reporting in on the driver license scanning project. He is looking into our code and comparing it to a 2D barcode library that he found on git hub. Eric and I ended up talking about other API sockets and functionality. He was saying that he likes to categorize things as - must haves and nice to haves. I thought that it was a fun way of saying needs and wants. Good stuff. Spent the rest of the time working on emails.

	Shop 8917		Budget Meeting	4/14/2022	Meeting with Cory, Steve, and I to go over budgets and corporate structure changes. Shari O. wasn't able to make the first part of the meeting so we recorded it. Brandon has the video footage at his house on his computer. We didn't want to post it as it contains some budget type info. Anyways, we went through the meeting and I was taking some notes, we were drawing and going through some scenarios. Shari O. was able to join us about half way through the meeting. I sent the meeting notes around after we finished. The meeting notes are mostly about the corporate structure changes that we are trying to make. See attached.

	Shop 8946		Working on projects	4/25/2022	Emails and updating an active company and corporation list for Shari O. Switched over to working on some custom code and working on bulk tools for dealing with flex grid tie-ins. Coding and working through things.

	Shop 8928		Budget Meeting	4/26/2022	Admin budget meeting. To start out with, we had all of us on the meeting (Steve, Cory, Shari O., and myself). Steve was having internet issues and ended up dropping off of the meeting. The other three of us kept plowing ahead. After the meeting, I sent notes and budgets to all of the main admin team. I have copies of those files here at my house, if we need them.

	Shop 9002		Meeting with Steve	4/28/2022	Talking with Steve over a GoToMeeting session. We went over and covered a number of topics. We started out talking about merchant processing options. We already have a relationship with USAePay. However, we are also looking at NMI, Stripe, and Elavon. As we get more or new clients, they will have more and more merchant processing needs. Trying to stay ahead of the game. Steve and I were also talking about the different mix of team players that we have. We got into talking about religion, beliefs, controversial topics, cannabis, non-cannabis, developers, sales, and how to balance all of those pieces. Our mix almost creates an interesting culture and a specific need (who else if needed). We don't have very many that can crisscross either based on the beliefs (religion and feelings), which topics that they are assigned to work on, and whether or not they will reach out and talk to people (sales). We have some of our developers that will only work on certain projects (me included) and other ones who don't do sales (they only want to do code). Because the team is so small, it can be a real challenge. There has to be a balance and we are trying to find and maintain that balance. It feels elusive and slippery at times. Steve was saying or relating what we do to an analogy of people sitting around the fire. Everybody likes the fire, but nobody wants to go out and get more firewood. He really wants to push harder on the sales side of things. Basically, it feels like we are a little bit heavy on the developer's side of things. Towards the end, we were talking about the ability to take basic building blocks and stack them into small combo packages to get awesome outcomes. It's not that the smaller pieces are super cool, all by themselves, it is just, when they get stacked together, they really become something cool. Taking the basics and stacking them together. Steve is really trying hard to work on bringing in custom controls and dynamics to all of his projects. That is awesome. Here are some other notes that I took during the meeting. I started out jotting things down on paper, but was getting behind, so I started typing things so that Steve could see where we were and what we had covered. These notes below are from the typed stuff. - People's willingness to play in different industries - cannabis and non-cannabis - Personalities and where they feel comfortable and want to spend their time - development (writing code) and sales (getting out, networking, pitching things, and talking to people) - We may need to cut back dev and push more on sales - Analogy of cutting firewood vs sitting by the fire - Balance and being able to keep going - Have cory focus on clients who want improvements and are willing to make investments - client funded projects - Wasting money on sales meetings and emails campaigns - People who are great at what they do but they can't do all of the things to keep the balance - This ends up being a vacuum or a money pit because we have to pay for all of the one-sided stuff - In cannabis - we can get some of the new accounts, but it is hard to make someone switch - We are up against a lot of money - big money investments - We want to stay as small as possible and stay nimble - Paying someone for sales - somewhat of a headhunter - Steve would like to see 5-10 new systems per month - 3rd party solutions - there is a need there and they do help us float down the river - Maybe looking at pair programming - Talking about trust levels - Shari O. has been the back-up for server resets - Help is only helping if they are helping - we can't hold up a drowning swimmer - We have had some peace and quiet with letting some of our guys/gals go... We need to get back there - On the MMLLC - some of our team is worried about liability - A couple of phases - anybody who wants to stay, needs to jump on the wagon - Minimum is at 1/10th of a percent - Don't worry about all of the details - Get those set who want to and then go forward with the others - Sort of a faith-based venture - just start, if you don't like it, we'll buy it back (talking about the company restructure stuff - buying and selling percentages) - We have enjoyed working with Dustin - Bryan has been a great work horse - Steve would like to check in with industrial supply places and see what we can do there - find a vertical and then service it - Maybe try some email campaigns for some of these smaller verticals - Trying to expose more and more of the system - fewer black boxes and make it available for everyone - Getting to a stable location (lifestyle)

	Shop 8976		Server meeting	5/3/2022	Wayne, Cory, and Shari O. were going over server questions. One of the big topics was the clean-up of the data 0 database and servers. We talked about lists and ways to get a standard list of what is good and what needs to go. Wayne also reported in on his settings project. We told him that we would like Bryan to work with him on getting things tested and getting things finished. Wayne was excited to get another set of eyes on the code and help push the project forward. Cory was asking Wayne about some background syncing between the adilas servers and Metrc (state of Colorado cannabis tracking system). We wanted to make sure that certain background clean-up processes were in place and working as expected. Towards the end of the meeting, Cory and I were speaking with John. He had some questions from our meeting yesterday and we were talking about buy in and owner and percentages stuff. Sometimes communication and expectations are the hardest things to get figured out. We'll keep pushing things forward and figure it out, maybe even on the fly. As a side note, we are all trying to do good. If someone isn't happy with what we are doing, it can deflate us. It's like a kick in the side. It hurts when someone doubts you or questions your capabilities or priorities. Just speaking in general. I for one, feel pretty fragile sometimes. Other times, I can take some pressure and heat. It all depends.

	Shop 9007		To do list items	5/4/2022	Emails, text messages, and other follow-ups. Recording notes. Installing some new tools from Calvin Chipman. He has a new image converter and a file renaming tool. Got those installed and ran some tests. Calvin is the tool guy. He loves making his own little tools to make things go faster and faster. Got on a GoToMeeting session meeting with Shari O. to over our existing options for USAePay and getting re-familiar with the USAePay virtual terminal for credit cards, refunds, batches, and other transaction look-ups. We took a couple of screenshots and will be sending some emails to Newtek tomorrow to help get things going in the right direction. This is just for fun, but earlier today I heard Cory say - "We the bananas from so and so (a client)". It made me laugh. The term "bananas" is what Shari O. uses instead of saying money. I told Shari O. that she is rubbing off on us... :)

	Shop 8965		Adilas Time	5/9/2022	Pretty quite this morning. Shari O., Sean, and John were all checking in. Nothing major. Steve joined and he and Sean were touching base on some prospects and contacts. Steve had some questions on his smart gram controller settings, able to switch, between medical and recreational licenses. After that, Steve and Shari O. were going over pricing and some new accounts.

	Shop 9009		Pushing up some code for Chuck	5/9/2022	On a quick meeting with Chuck. We looked over some code and merged and pushed up some changes. This was on the parts usage page. These were some requests from Kelly and Cory. After that we looked at some of his other projects that he is working on. Small little session. Shari O. jumped on the meeting and just needed a verbal consent for the bank to use a debit card for a foreign transaction for one of our vendors.

	Shop 8952		Budget Meeting	5/12/2022	Admin budget meeting. We had Cory, Shari O., Steve, and I on the meeting. We started out the meeting going over an email that Shari O. had sent with items on accounts receivable, bad debt (uncollectable invoices), expenses, and report on new systems. I was taking notes and we got lots of good back and forth communications and plans. Another key thing that we talked about was the need to get our guys (developers) to enter notes on the projects so that we can track hours and progress. Basically, a way to step up and clean-up some of our internal processes. Notes were sent out after the meeting to all parties.

	Shop 8957		Adilas Time	5/16/2022	Jumping onto the morning meeting. It was just Steve and I to start out with. Steve had a couple of code questions. We then started talking about reseller documents and contracts for USAePay, NMI, and Trinity Payments - all merchant processing stuff. We are considering being a reseller of online merchant accounts. We have had merchant processing built into our system since 2009, we are just now getting to the point that we may want to enter that market space and become a reseller of those services. Steve asked about the bulk flex grid tools and customer facing scheduling stuff that I was doing the bike shuttle company. He volunteered to help build out some settings when I'm ready for that. He would love to go after some clients in that neighborhood. We also talked about using ecommerce, message marketing, and other client portal type tools to really connect with an end-user or client. Good stuff. Steve has lots of ideas. Shari O. joined and we talked about banks, deposits, and bank transfers. After that, Steve and Shari O. were going over servers and where to setup and put new clients. They also went over some quotes and prices. The last thing that went on in the morning meeting was Steve and Sean going over sales and options to help out our reps in the field. They are bringing in contacts and leads, just trying to make sure that we take care of those leads as they come in. Everybody left and I was waiting for my next meeting. Nobody came, so I did some emails and what not. Going through small to do list stuff to get my week started.

	Shop 8974		Adilas Time	5/18/2022	Shari O. jumped on this morning with a few questions. She was setting up a client on an Authorize.net account for merchant processing. We looked at a help file and got her going in a good direction. After that, John checked in and setup a meeting for later today. Shari O. jumped back on a little bit later and had a few more questions. We did some drawings and diagrams and got her all set. She just had some questions on how things work with internal merchant processing vs external or 3rd party solutions and standalone merchant processing. I also did some emails and other small things.

Showing 150 of 311 Page 1 of 3 :: Go to page ::

What's New

Products

Find Us