Adilas.biz Developer's Notebook Homepage

[reset this page] . [historical web outline - entries by month] . [adilas community funded projects] . [contact adilas.biz support - email form] . [help]

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 - 2/1/2018 to 2/28/2018 - (67)
Photos	Time Id	Color	Title/Caption	Start Date	Notes
	Shop 3489		Adilas Time	2/1/2018	Started out the morning working on some updates for the 2018 state and federal tax withholdings. Shawn did the code and I reviewed it and ran it on all servers. After that, Alan jumped on the GoToMeeting session and we chatted about the next steps. Alan wants me to do some additional planning to help with the upcoming new session values for phase 3 of the sales tax expansion project. We are still on phase 2, but prepping the field. Some of the other guys popped in and out throughout the session. Eric popped in and we chatted for a bit. Steve was at the bank closing on a refinance loan and then on the GoToMeeting session. Shawn came over to my house and was working on stock/unit database changes for the sales tax project. Alan was on the meeting most of the morning as well. Good stuff.

	Shop 3491		Lunch	2/1/2018

	Shop 3490		Adilas Time	2/1/2018	Phone calls, emails, and working on documentation for the upcoming session scope changes for the sales tax expansion project.

	Shop 3434		Russell Time	2/1/2018	Russell and I got together and worked on the invoice due date project. We are pretty close to being done. We ran into a small problem with the merchant processing stuff on the web/shop or ecommerce checkout. It works live, we just couldn't get it to work locally. We will have to jump into it a little bit deeper. We also chatted about options for helping Russell focus on different projects or have him help with ones that don't have cannabis related backends.

	Shop 3508		server setup notes	2/1/2018	This meeting did not happen. No action taken.

	Shop 3485		Brandon out of the office all day	2/2/2018

	Shop 3496		Adilas Time	2/5/2018	Steve and I joined up on a GoToMeeting session. We then jumped into a conference call with a company. They needed some light custom code to duplicate a single entry into two different fields in the database. We talked with them and then started working on our own projects. After that, I was fixing a bug in a trailer dealer's site and Alan and Steve were working on some API socket connections. On my project, somehow the main part number for the stock/units had been removed. I went in and made a small file to replace the old part number by copying a similar item from a different corporation. Once that was completed, everything else started going through ok. I then did some light tech support stuff, phone calls, emails, and getting ready to switch gears to get back on the sales tax stuff. Most of the rest of the session was spent working on the session scope for the sales tax expansion project. Lots of documentation and making notes. I also helped Steve out with his plant phases project and helping him get clear back to the time template level to get the data that he needs. Lots of good stuff going on.

	Shop 3504		Lunch	2/5/2018

	Shop 3500		Adilas Time	2/5/2018	Emails, doing bills, and reaching out to Shannon about some questions.

	Shop 3519		push server	2/5/2018	On a GoToMeeting session with Bryan. He wanted to get some server updates and notes pushed into master. This is for a master file that he uses to setup a new server. It has a huge multi-point to do list to help him go through the process. After that, we talked about a special barcode checkout process where they, his clients, could validate what was actually shipped and/or packaged to fulfill an order. They are basically looking for a secondary check to make sure that what the client ordered was really packages and given to the client. We also talked briefly about looking into options for menu boards and including sub inventory with that feature. It is amazing how much things keep sub dividing, fracturing, and breaking into smaller and smaller pieces. Our clients want global control of what is going on... in order to give global control, we need to break things down into sub controls of varying levels to give them that ability to control things. See attached for a small graphic that shows the same thing and/or concept.

	Shop 3520		General	2/5/2018	Testing files for the database updates for the sales tax expansion project.

	Shop 3497		Adilas Time	2/6/2018	Working with the guys on the morning GoToMeeting session. Steve showed me a bug with scanning custom barcodes. We then started working on the scan QR code page for custom barcodes and custom QR codes. We did some major clean-up and also added a store/location filter. Steve and Alan were talking about keeping data updated with outside 3rd parties and making a custom database to catch and sync up the grouped data. We then talked briefly about getting everybody off the bus and only adding corp specific tables as needed. There is a lot of coming needs on splitting up the database and doing our world building project. We then did a GPS demo with Wayne Andersen. We are seeing more heat there and things are getting excited in that area. After that, Calvin came on and we talked about some GPS stuff and progress on his other projects. We ended up talking about mobile apps, cell phones, GPS tracking, RFID tag tracking, and options on those fronts.

	Shop 3505		Lunch	2/6/2018

	Shop 3501		Adilas Time	2/6/2018	Looking over changes on the sales tax expansion project. Going through pages on my local system and playing with the new changes. Virtual testing without being super deep in the underlying code.

	Shop 3509		Russell Time	2/6/2018	Working with Russell to get the invoice due date project closer to being uploaded and finished. We did some testing, tried to fix the local merchant processing, and spent quite a bit of time working on a deployment plan. The invoice due date interacts with invoices, quotes, shopping carts, and session scope values. That makes it harder to launch pieces without interrupting existing flow and logic. Kinda like changing a wheel on a car that is moving... :) See attached for our current tick list.

	Shop 3521		Meeting with Calvin	2/6/2018	On an after hours Zoom meeting with Calvin. We setup a few corp-wide settings for Caisson Labs (a client), added logos, watermarks, and then went over the code for the login procedure. Calvin is going to be creating a standalone desktop app for Caisson Labs. He wants to use the desktop app and connect directly to adilas through the API sockets. It should be a fun project.

	Shop 3528		New database updates with Alan	2/6/2018	Alan and I met up and used a GoToMeeting session to push phase 2 of the sales tax expansion project. We merged in some files with master and then uploaded the database updates for all servers. We tag teamed on the uploads and did thousands of click, click, click, wait, click, click wait... :) Two hours of clicking talking and testing. Kinda fun. We chatted about all kinds of random stuff.

	Shop 3498		Adilas Time	2/7/2018	Started out the morning on the GoToMeeting session with Steve. He had some questions on his plant phase stuff. We started into the code and then got some other questions from both Eric and Bryan. We helped both of those guys get going on their way and then went back to the plant phase stuff. We ended up creating a smaller scratch file with minimal information and logic. That helped Steve better where he was going. We then talked some strategy and funding options and budgets. Steve got his refinance home loan and adilas will be able to use some of that money to refinance our own debt and such. It should be really good. We will end up paying a similar amount but will be able to restructure things and consolidate some of the other payables and other business debt. Good stuff. I checked in with Alan and he wants me to work on the ecommerce cart session values for the new sales tax expansion project. This is phase 3 of that project.

	Shop 3506		Lunch	2/7/2018

	Shop 3502		Adilas Time	2/7/2018	Working on the session values for the main ecommerce shopping cart. This is part of a prep step for the sales tax expansion project.

	Shop 3510		Russell Time	2/7/2018	Russell and I met up and started working on the invoice due date project. We used a Zoom session and did some prep work on the session scope variables for the new due date options. We then pushed up some prep code. After that, we started to work on some merge conflicts between what we had coded and what Alan and I have coded for the sales tax expansion project. Both projects use similar files and we have to be sure not to overwrite the other project's code. Little game of who has the last cookie. :)

	Shop 3527		Meeting with Calvin	2/7/2018	On a Zoom meeting with Calvin. We looked into some new adilas API sockets and how to test and debug against them. Calvin is creating a small desktop app that will touch base with the adilas database through API sockets. He is using existing pieces as well as building out other pieces that are needed. We spent most of the time testing, turning things on, going over rules and best practices options, and making sure we know which pieces go where. After that, we talked briefly about GPS data points and how to get those via a simple browser-based function on a computer and/or a smart phone. We also talked about having a counter for data points that were the same. Basically, instead of recording thousands of data points that were the exact same... We would record 1 data point and then increment a counter if the next data point was the same. So, instead of having a thousand records that have the exact same data... we could have 1 record with a counter of 1,000 (showing that it was in the same place for 1,000 touches). Then when we show it (the display)... we could show it however we needed to but technically, we would have all the data that we needed without blowing up the database for things that are parked and/or stationary. Great idea.

	Shop 3499		Adilas Time	2/8/2018	Met up with Steve, Alan, and Eric on the morning GoToMeeting session. Eric needed some help to push up some custom code for a client. I was working on a custom data migration for a client. They had 27,000 customers that needed a phone number moved to a different column. I wrote a small page and did the migration. I then had to work on a custom black box page that would do the same thing on the live server and would keep up with them as they did their daily work. Alan and Steve were working on the API socket connections for Leaf Data - a state traceability program. They were testing code and then making changes. Alan helped Steve get some things migrated and merged into the master branch. At the end of the session, Steve and I were working on a bug fix for voiding PO's with sub inventory. We changed the availability to hidden/closed vs. disabled/open. Hopefully that will help. We had to go into one of the servers and do some bulk updates behind the scenes. As a random note... the more we automate things... the quicker someone who doesn't know what they are doing can really make a mess. The same is true with other things... think about horses and buggies vs. going 80+ miles per hour in a vehicle. If the vehicle goes off the road, the wreck had more potential to be of higher consequences due to the speed. As we automate different things, we encounter new challenges due to the new variables that get exposed and/or introduced. Interesting.

	Shop 3507		Lunch	2/8/2018

	Shop 3503		Adilas Time	2/8/2018	Paying some bills. I then got on a GoToMeeting with Calvin. He is working on his Caisson Labs project. As part of that project, he needs to do a data import for the parts and general inventory items. We looked over the data and made some plans. He needs to go back to them and try to get more data. We got very little data and some of it wasn't very inconsistent. After that, we spent most of the session talking about the technical side of the database relationship between vendors, parts, PO's, PO line items, units of measure, part categories, and sub inventory. We went through different database tables, column and field names, and what ties into what. Good session and I think that it helped Calvin get a better grasp of what the pieces are and how they play. Good meeting.

	Shop 3529		Fulfillment flow	2/8/2018	Met up with Bryan over a GoToMeeting session. He had some questions about the fulfillment homepage and how the flow worked there. Basically, the companies are creating invoices, getting payments, and then processing the orders. We talked about options to help with the lock-down (approval and/or fulfillment) process and how to simulate that feature in a simplified page and/or environment. We went through the process a couple of times and I showed him where he could go to get code snippets and existing logic and functions. We also talked about barcode scanning and how to tie something like that into the process. Good stuff.

	Shop 3486		Brandon out of the office all day	2/9/2018

	Shop 3530		General	2/10/2018	Paying bills and emails.

	Shop 3522		Brandon out of the office	2/12/2018

	Shop 3523		Brandon out of the office	2/13/2018

	Shop 3524		Brandon out of the office	2/14/2018

	Shop 3525		Adilas Time	2/15/2018	Emails, phone calls, text messages, and recording bills.

	Shop 3526		Lunch	2/15/2018

	Shop 3552		General	2/15/2018	Emails, bills, phone calls, and light tech support. Trying to get unburied from a trip.

	Shop 3553		General	2/15/2018	Paying bills and doing things for both the main adilas.biz company and the adilas shop. Phone calls and emails.

	Shop 3487		Brandon out of the office all day	2/16/2018

	Shop 3531		Adilas Time	2/19/2018	Talking with Steve about how to get some of our players more involved and more connected into the adilas family. Doing some light planning. - Maybe make Russell the main designer. We still want to go function over fashion, but we are seeing a bigger need for things to look modern, cool, and quick. - In order to get to where you want to... you have to have some kind of a vision. - The other one that we really need is Alan. - With some of the new monies we are getting... we may want to push some of that out to Russell and Alan. They are both big huge key players. - On the world building project (splitting up the database), we may want to set an amount that we want to spend per month. This is a huge project that we want Alan to work on. - Help our guys by making projects and plans and then letting them go. We basically help them get the vision and game plan and then let them chip away at it and let them run with it. - Steve can fuel the projects (master salesperson). - Most of our guys need to be around the $35 to $50 mark. If you translate that into monthly... you are looking between $3,000 and $6,000 per month. After chatting for awhile, Steve and I went on mute in the GoToMeeting session and pounded out some expenses and such. We are trying to clear a bunch of the adilas payables out and get a good look at where we are. See attached for a light budget worksheet that we were working on and talking about.

	Shop 3538		Lunch	2/19/2018

	Shop 3545		Adilas Time	2/19/2018	Back on the GoToMeeting with Steve. We did a small tweak on his Leaf Data code and output the store/location license number. We then talked a little bit more about budgets and clarified a few things. Steve started working on his stuff and I switched gears and started working on my stuff. I made a couple of phone calls to Alan, Bryan, and Russell. Updated some domain names and changed out some nameserver names. This came from Newtek and they are updating some of their servers and what not. I then switched over to the ecommerce cart and session stuff for the sales tax expansion project. Trying to alphabetize some of the session values for the ecommerce shopping cart and session values. Part way through, Alan Williams came over and I got him a check and we chatted for a bit. Towards the end, I helped Steve merge and push up some of his code. He is really trying hard to play well and keep things being merged into the master code branch. He is doing awesome and we are starting to turn over new leaves. Good stuff.

	Shop 3532		Adilas Time	2/20/2018	On the morning GoToMeeting session with Steve. We started out and paid a number of credit card bills. We paid them off in full. This is a huge step for us. We have had some credit card debt since 2013. Boy, that feels good to get rid of that. Good stuff. Alan and Steve were working on some bugs on Leaf Data pages and I was paying bills and such. We then chatted with Alan about progress on the sales tax expansion project. - Wayne Andersen - Failure is an opportunity. - Wayne Andersen - If the big thing that you are trying to accomplish, can be done in your lifetime... you are thinking too small.

	Shop 3539		Lunch	2/20/2018

	Shop 3546		Adilas Time	2/20/2018	On the afternoon GoToMeeting with Steve and Alan. We are all having problems with our email system and I was doing some checking on that. Light tech support and follow-up. Steve and Alan were working on some bugs and custom error messages. Alan and I went back to work on the sales tax expansion project and working on the session scope changes. I then got a call from Shawn and he and I merged in some code for some payroll changes for some of the states. Kind of a crazy afternoon.

	Shop 3513		Russell Time	2/20/2018	On a Zoom session with Steve and Russell. Our original goal was to talk about upping the percentage for Russell and AFB from 3% of gross sales to 6% of gross sales. This was to help get Russell more onboard and helping us on more internal projects. As we got into things, the whole subject expanded and we got into somewhat of a heated discussion on who owns what, who gets to claim what, and how to make the transition as smooth as possible. I don't know if we meant it or not, but a number of the topics ran deep and had an underlying theme of AFB vs Adilas and how to virtually buyout AFB so that we could all go forward together, as the same team. See the attached graphic for some of the topics of the conversation. These are in no special order, but here are some of the subjects: - We could split the 6% in any way that was needed... 1% for Chris, 5% for Russell, 3% for AFB, 3% for Russell, or any other combo. - Russell wanted to know what our plan was for either an investment or a buyback or payback for pieces and projects that have been completed. - We talked about possible options of putting some of the investment monies on the balance sheet and how that would work. Bascially, AFB would have to invoice Adilas for the sale of certain features and then Adilas would have to have that as a short-term payable or a long-term payable. - We talked about how to possibly treat water under the bridge (real monies and invested time). We also talked about how to treat future projects and investments. - Steve made the comment - This is a long term play. - There was tons of talk about what has been gained by the existing relationship. This took on many forms and talked about physical monies changing hands, training, tools, business benefits, our system and providing services to Chris Johnnie without being paid for those services, and many other topics. - We went over some of the early promises that were made and/or implied by Brandon, back in early 2015. Some of those subjects were: you guys build it, you can keep it. You guys can have free systems and free access to the new tools, and how to we treat Chris? Is he part of the family or is he an outside investor? - We talked about ways that Russell thought that things could be settled. Some of these were different topics, but just listed here for reference: Some kind of a virtual buyback or buyout to help Chris with his investments, Free systems and non-3rd party tools for X number of years (small limits), If new systems come on, what does that mean?, At what point do we reach a virtual payout or buyback?, And maybe setting a limit on the free systems and tools to the existing 5 systems. - We also talked about how much of a monthly service Chris is getting by being able to use the system for free currently. We estimate that he is getting close to $1,000 a month worth of free services. There were a number of other topics, but that is a small recap. The meeting ended still lightly hot and we determined that we would meet again and try to come to a decision. Everybody is running hard and there are some outside variables that were adding to the stress.

	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 3540		Lunch	2/21/2018

	Shop 3547		Adilas Time	2/21/2018	Random bug fixes for payroll and light tech support and emails.

	Shop 3516		Russell Time	2/21/2018	Meeting with Russell and Steve and Chris Johnnie over a Zoom session. We started out with Steve pitching... as we, at adilas plan, we would like to get Russell's input. He could really help. We then each took turns and talked about what we would like to get out of the relationship. Steve talked, Brandon talked, Russell talked, and Chris chimed in. - Who gets what and what are the ownership levels? - Who sales what? Who does the demos? - If we are spending money, where is that going? - Russell thinks that adilas needs to maintain the control. - Lots of fun back and forth conversations. Lots of good comments and no where near as heated as yesterday. - How can we bring it back together and just be adilas? - Steve's idea of making adilas into a living trust where nobody owns adilas. We all just play together. One big organism and virtual family. - Steve was pitching Chris on the fact that eventually, he, Chris, may end up just selling adilas vs chasing tons of outside businesses and outside investments. Kinda fun. - What are the proposal elements from Russell's and Chris's side of the puzzle? From Russell - Chris gets his 5 systems for free for life. Anything he puts in, money wise from here on, will go on the balance sheet. Russell would like some numbers on the balance sheet and some flexibility to work his magic. Russell's balance sheet number is $40,000 (what he expects as a fair price for what he has in the cooker - projects that are already developed). This would be a no interest account and then paying it down $1,000 per quarter or $4,000 a year. - Just for fun... add an "e" on the end of the name - adilas-e. The "e" stands for "eventually". Somewhat of an inside joke. The word eventually has almost become a dirty word... :) - It would be so cool if the system could sell itself and even demo itself. That would be really cool. - Adilas is like a farm for ways for starting new businesses. It has so much to offer, you could go in all kinds of directions. And the system runs deep and can really help businesses go forward. - Russell's word - dependables - and making everything work and play together. - Other things that Russell would like to do are: Marketing, making videos, education, and helping with sales. - On payments going out... We will book the entire amount - say 6% of gross sales - then we will pay it out in smaller amounts. This will help with cash flow. Maybe even give Russell some signed checks and let him print his own checks. Just like printing your own money.

	Shop 3534		Adilas Time	2/22/2018	Joined into the GoToMeeting session. Steve and Russell were working on some tweaks on the current data tables for sales deposits. They wanted some new functionality but the page was having some issues with pagination and JavaScript stuff. They ended up tweaking some JQuery to make the page work and look better. Meanwhile, Alan and I were working on the sales tax expansion project. We were testing and merging files and making some small changes. Towards the end of the meeting, Steve and Russell were going through the system and talking about things that they wanted to change. Everything from simple look and feel to defaults and functionality options. That will be really cool and is exciting.

	Shop 3541		Lunch	2/22/2018

	Shop 3548		Adilas Time	2/22/2018	Emails

	Shop 3554		White label	2/22/2018	Bryan and I got on a GoToMeeting session and worked through a couple of questions. Some of the questions ranged from new session values, white label options, scanning RFID tag numbers (batches and lot numbers), and possibly adding corp-specific action status values for elements of time. These are things like clock-in, clock-out, start, stop, pending, completed, etc. I have wanted to do corp-specific options for quite some time.

	Shop 3488		Brandon out of the office all day	2/23/2018

	Shop 3535		Adilas Time	2/26/2018	Joined up with the guys on the morning meeting. Steve, Russell, Alan, Wayne, Calvin, and I all participated at different times. We started out with Steve and I working on some code. Then Russell came in and we worked with him on some look and feel direction. We want him to focus on the frontend and what we show to the customers and/or potential customers. This deals with new and updates, list of features, and some of the marketing and packaging of the items. Russell pitched a couple of ideas and we listened and then came back to the frontend look and feel stuff. He would love to add some live chat options, email forms, automated settings, and other cool features. He also showed us a cool and simple task management system that he was working on for some training. Alan and I touched base on some projects and then got back to work on what we were doing. Alan is working on both the sales tax expansion project and finishing up some Facebook integration for Campaign Rise. Wayne had some questions on database stuff. Later on, Calvin had some questions on info that he is collecting from Caisson Labs. Lots of good progress for all of the guys and things are moving forward in a good manner. I ended up using the last couple of hours doing emails and tech support. We had to call a couple of clients and go in and checkout some of the code and what not on the data 9 server. Basically, the whole morning was bouncing around and jumping from here to there. It must be Monday. Yee haw.

	Shop 3542		Lunch	2/26/2018

	Shop 3549		Adilas Time	2/26/2018	Prepping and going over code for the sales tax expansion. Uploaded some of the session code and did some testing. Pushed things up to all servers. I still have a few corp-specific files to check and go through.

	Shop 3555		White label	2/26/2018	Met up with Bryan over a GoToMeeting session. We went over some questions and merged in some code and did some session stuff. We talked and worked on some white label stuff and made some decisions. Bryan had one question that I referred him to Steve on, it was dealing with how much a white label could show/hide on the 3rd party solutions page. Basically, if they choose one white label option, this one company wanted to hide some of the other options. I wanted Steve to make that call.

	Shop 3556		Tech support	2/26/2018	Phone calls and tech support. Helping with a barcode printer problem.

	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 3543		Lunch	2/27/2018

	Shop 3550		Adilas Time	2/27/2018	Working with Steve on some code questions. We went through some code that was looping over PO's and updating things. We then worked on some new code to build a special table to help cross validate between adilas and state API compliance systems. This is a new table that Steve and Alan need for a project with Metrc state compliance. Part way through the session, we had to make a quick fix to the barcode generator code. There was a variable conflict.

	Shop 3517		Russell Time	2/27/2018	Russell and I hopped on a Zoom meeting. We mostly worked on the new email options that Russell and the AFB guys built. We added in some custom email users and then Russell loaded in some templates and custom email settings. We merged and pushed up the code and did some light testing online. We also talked about what projects have our priority and focus and jumping into those pieces.

	Shop 3557		General	2/27/2018	Fixed the advanced sub inventory search results pages. They used to show the main sub id number, which is actually the virtual transaction number. I changed it out and showed the sub reference id or main package id number. That should help. I then did some emails and such. It is amazing how much time that takes some times.

	Shop 3537		Adilas Time	2/28/2018	Steve and I were on the morning GoToMeeting session. Russell popped in and sent Steve and I an invoice for transferring all of the AFB (adilas for business) stuff over to the main adilas.biz company. I printed and signed and sent it back. We then talked with Russell about some graphs and charts and ways of getting that stuff going. After that, we had a small brainstorming session on a number of different subjects. See below for a couple of quick notes. - Hook up Russell and Svend to get him into the support team on the hardware side. Basically a hardware consultant. Treat things more like a service vs a retail related business. - We want to separate the system support and the hardware support. - We may want to have Russell and Svend work on getting Svend into the adilas market (adilas world). - Talked about a $1,000 per month as a rough budget for non billable hours at $25/hour (things that he can't bill and/or collect on). We also talked about a 0.5% or a 1% of total revenue as a carrot. - We want to be pro active on the hardware side. - We want a pricing list and list of recommended hardware and turn it into a web page. - The independent model - we help them belong to something - plus they have their own thing on the side. - We find a need and then find the person to see if we can fill that need. - Hire that person (employee model) vs work with that person (independent model) - both ways you get to work with the person, the difference is the angle and the amount of freedom that is expressed. - Find more people who want to belong to something, but may not need to be held on to (have a virtual babysitter that has to watch them). - On the hardware side, we need that person to be flexible and allow for users to choose their own options and hardware. - We are learning as we go... We are seeing that if there is a need and we can find someone to fit that need, they tend to play pretty well. - We were talking about trial periods, starting budgets, possible percentages, and reviews and expectations. - Let people know "what our model is..." that may be the first part of all our training and education - start here and then see how people respond to that model. Basically, here is what we do and how we do it, let's see if you are a good fit and like what we do. Steve was even talking about showing the model before the features, advantages, and benefits. - Russell is starting at the beginning... Let's point him towards explaining and helping us show our model. That might be a great starting point. - It seems like the main goal is constant refinement... that could be code, processes, people, filling needs, and pushing forward. - We talked about the data tables... How do you want this data? What columns to show/hide? What visual display - graphical, charts, data, details, etc. How do you want this data as output? This could be web/HTML, visual eye candy, CSV, Excel, PDF, printable, etc. Pretty crazy. Virtually like a mini report builder of sorts.

	Adi 1434		Icon menus for pages	2/28/2018	Huge project and involves every page in the system. Already spent $50,000.

	Shop 3544		Lunch	2/28/2018

	Shop 3551		Adilas Time	2/28/2018	Working with Steve over a GoToMeeting session. We worked on his Metrc API socket stuff. We built a new table, per corporation that uses that state API socket. We went over some code on new methods, we did some planning, and looked over code and pages already done by Steve. I did some billing, email, and merged in some new icon menu pages from Nick. I had to create a number of small icons or image files to go along with the new pages. Pushed up about 22 new files. Towards the end of the session, Steve got on the phone with Svend (an adilas hardware specialist) and we chatted for a bit. I was mostly working on other projects while Steve and Svend were talking, but Steve was pitching him on the independent adilas model and how he and his team could play a big part in the hardware side of things. Good phone call and they will be touching base early next week to keep things going. The word of the day today was "model" and helping to define and educate people on what that is and how we play the game. Good stuff.

	Shop 3518		Russell Time	2/28/2018	Meeting did not happen today. I ended up just working on other projects. Russell sent me a text saying that he didn't have anything new that he needed help on today.

What's New

Products

Find Us