Adilas Key Contributors:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Recording notes and working on a list of known issues. See top_secret/secure/known_issues.cfm for more information.

For fun, here is a list of some of the items listed on that page. This list originally was started in 2009. Small list of what are known problems. Some of these things are real problems and some are just warnings. Lots of things have changed since then. It may need to be updated, added to, and some of the items removed, that have been patched, fixed, and/or finished.

1. Invoice pmts on account with something different than 0.00 value.


2. Receipt pmts on account with something different than 0.00 value.


3. Reimbursements (rei's) with a bank assigned on the receipt pmt.


4. Invoices with mismatch between main and line items.


5. Deposits with mismatch between main and line items.


6. Receipts with mismatch between main and line items.


7. PO's with mismatch between main and line items.


8. Non verified payments (outstanding deposits and checks).


9. Duplicates ???


10. Dates prior to the corp start date or prior to the bank start date. See bank_balance_helper.cfm page.


11. Dates in the future. see bank_balance_helper.cfm page.


12. Internal invoices that are not marked as paid.


13. Receipt payments that are verified but the main is not verified.


14. Difference between invoices and stock numbers. Created a number of flags to show disconnect.


15. When paying back splits and rei's - what about both (main and subs) being assigned to income statement expense types? This could double things up on the income statement. Defaulted special multi build (rei and splits) to b.s. items for expense types. Still possible problem on original e/r that may get assigned to the balance sheet.


16. Update PO's not tied to a balance sheet item (say a loss account or something).


17. Lien payoff line items on invoice with a 0 cost. The cost and the price should be the same otherwise it puffs up the profit. Did run a report at one time to fix this. Also added code to the cart to match cost and price for lien payoff stuff.


18. PO payments that have the wrong date and thus the po_paid date is wrong. The system was using the current date as the payment date even if the payment was actually made in the past. Small disconnect between actual payment date (e/r payment date and PO paid date).


19. Check auto dates that are actually used in I.S. reports or B.S. reports. Need a way to manually change the auto dates if really being used. Check the unit payments, PO payments, other system made payments. The system seems to be ok, the problem is with dates and being able to either set the date when using or edit the date if defaulted to today's date.


20. Blank expense/receipts (payee_id = 1).


21. Voided items but part of it is still in play or not fully voided. Need to get to a voided list quickly.


22. Denied check requests on payables page.


23. Sales tax problem with work in progress invoices. They don't show up on sales tax reports until they get flipped back to a customer invoice. The problem is that the date (main invoice date - if not moved forward) will not show up on the next month’s tax reports. If this happens, the invoice will fall through the cracks and not be counted for sales tax. Possible option for sales tax, Steve thought that it might be cool to have a point and click interface that we physically pay taxes on certain invoices. That way, they never fall through the cracks and we only pay taxes once we collect the monies. This would also help with a system-maintained b.s. item for accrued sales tax. As an update, Eric was working on a sales tax aggregate project to automate this.


24. Along with sales tax problems, how do we show this on the balance sheet? We need to show collected, paid, and owed values. Once again, Eric has been working on this in his sales tax aggerate project.


25. Payroll has similar problems with regards to what has been paid on, what is still needed, and how do we show this info on the financials.


26. See idea in note book about showing all daily transactions. This is different than a history transaction record. This is what really hit in and out on this day in time according to the system. This is not a known issue but may help with finding issues. Daily monitoring of each account per location, per day, per account or category. This would be awesome.


27. Check for master/slave relationships between date changes. For instance main invoice date compared with invoice line items dates. PO main date with PO line items date.


28. Known issue with PO dates. Do we run off the main PO date or the PO received date? Need to standardize. Leaning towards PO received date.


29. Known issue with location based payables. Both expense/receipts and deposits have the location on the line items not the main. This means that monies could potentially get split between stores which would alter bank balances if only part of the money went in/out of the bank. Known problem here. Solution might be that banks are what they are (full monies in/out) and all sub lines and types are location specific. This could give a false indication as to how much money was available for each location.


30. What about transition invoices that have the main invoice date overlapping the transition (wip/qti) invoice date range. They don't show up anywhere other than on the main invoice homepage which doesn't tie to anything. Added a small fix on view_transition_dates.cfm page. Still need to check for possible mismatches.


31. Disconnect between sold date on units and invoice date. This is a disconnect that is unmonitored and will only show up if pulling a sold report (units) and an invoice report for the same time frame.


32. When backing up the main bank start date, there is a problem with expense payments and deposits that have a date before the main start date and a verified date after the main date. The payment or deposit date is not counted but the verified date is. I had the same problem with Leanna in Poncha and with Drew Middlemiss doing his first bank statement. What a pain. See the bank_balance_helper.cfm report (5/16/09) for small fix. Still a known problem with a starting bank balance not being 0.00.


33. Advanced pmt on invoices (pre-paid). They hit the bank because they were deposited but they also need to show up as a liability to offset the deposit or cash going up. This should be a system maintained item.


34. What about deposit types of other income that are assigned to invoices (double counted)? The default is an invoice hits the p&l and only deposit line items that are under other income and revenue adjustments hit or the p&l.


35. What about bad debt? Do we want to create a system maintained items for this?


36. What about deposits that are made before pmts are posted to invoices. This is not backward compatible.


37. Know disconnect between PO dates. The main PO date is currently used as the main search date. The PO received date is the main b.s. date. We are thinking that the main date may become somewhat of a request date or a age player only. The main date will become the received date with the received flag.


38. If a check request gets approved and assigned to a bank but never written out (bank never sees it), there seems to be a problem. There is also a problem with older check requests and the dates that are set in the background. They are uneditable once the request changes into a normal e/r.


39. Known issue with i.s. (income statement) deposit types. If used, without an invoice, they don't show up on the income statement. They may also be double booked if on an invoice and also recorded as other income or revenue adjustment.


40. What about payments made on a PO before it was received. This could happen with a request PO or a basic PO that has not yet been received.


41. What about inactive (status) on parts and subs. If we have details (activity) but something is inactive, that could cause problems.


42. Levels of inventory - this could deal with parents, subs, and usage details. We may need to check costs, quantities, dates, etc. Sub inventory was added way after 2009 (original date of this report). We may want to spend a whole session just going over sub inventory levels and possible pit falls.


43. Steve, Kelly, Molly, and others have lists of balance sheet challenges and other known issues. Check with them and get their lists.


44. Ecommerce and what plays into the real mix from there - invoices, taxes, costs, prices, discounts, payments, quantities, elements of time, etc. Good questions? Some of this is already figured out, it just needs a little bit of loving.


45. What about aggregates (somewhat new for us and just barely getting rolled out) and making sure things match up. Category (could be whatever), by day, by location - are there update processes that may be ran to keep things up to date. Manual updates, API sockets, watchers and feeders.


46. What about backorders? Steve did a whole section on backorders but I'm not sure if we tied in everything to the balance sheet and P&L. Anyways, may need to circle back around.


47. What about banks that get turned on/off (active/inactive). If we go back in time, we need to know if they were playing.


48. Same is turn with location. If they get turned on/off (active/inactive), we need to know when they were playing. We may need a start and end date and then be able to pull things accordingly, even if the current state or status is inactive.


49. What about cost of goods sold on unlimited or special line items? They should be a $0.00 cost because they are unlimited (like a labor or a service). If a cost is needed, it needs to be allocated through an expense to the COGS section or distributed in a thing called SG&A costs. SG&A (selling, general and administrative expenses - aka accounting for general costs by attributing them to a single unit and thus incorporating the true costs into an item). Basically, you take a normal expense like the electric bill or rent and build it into the individual cost of each unit by unitizing the expenses and virtually spreading a bigger general cost to smaller pieces. Sometimes that type of process (SG&A) is required for certain manufacturing and/or production type products. Basically, they (the IRS) don't allow you to expense off the whole expense (rent, insurance, waste, electric, etc.) as a bulk item. It has to be distributed to each smaller piece. If you do real SG&A, it helps assimilate those costs in smaller percentages and thus passing on a truer look at real costs of goods sold.


50. Anything that is currently marked inactive but may have played a role at some point. This could be locations, banks, part categories, items, vendors, customers, etc. Often, if we make them inactive, they don't get pulled (but maybe we need them at some time in the past).


51. Other special account options such as in-store credits, vendor credits, punch cards, etc. We already have loyalty points and gift cards that use special accounts. Maybe expand on this and allow for custom options or other digital payment accounts or payment solutions.


52. I'd love to map out all of the existing balance sheet and P&L values. Make it more widely known and really put it out there. Right now, it all happens behind the scenes and is kinda like a magic box. I'd love to get it all mapped out and presented to the public. We'll get feedback, refinement, and maybe even some other really good ideas. That's my vote, let's get it all out there in the public eye and public realm.

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

Bryan and I looked at his progress on show/hiding additional contacts out on the web. He is making great progress. We talked about some conditional statements to help with flow and possible lack of settings. Running through different scenarios. Sometimes, all of the possibilities make it extra tough (use cases and scenarios). It is also tough when you are adding onto existing pieces vs creating brand new features. You have to cover water under the bridge, partial old/new settings, no settings, and all new settings. Lots of variables.

After our meeting, we looked into another small project that Bryan is doing for Molly. It involves using a QR code both internally and externally. The real results allow a customer to scan a QR code and go directly to saved testing results. The same QR code, if scanned internally, will simply add an item to the shopping cart. Creative use of QR codes and virtually putting codes within codes. Interesting.

On a meeting with Molly and Bryan. They were going over options, bug fixes, and trouble shooting client needs. We talked about getting our internal tech support system and workers to be more responsive and quick. We also talked about passing some of those upgrades on to our clients for a price. It just takes more money to play at the higher and higher levels. Light talks about other possible up sales.

After the meeting. I got an email and had to setup a new adilas meeting room on GoToMeeting. One of our guys accidently deleted our reoccurring meeting for GoToMeeting. No harm, we just had to setup another room with a new id.

Spencer checked in and we did a light review of the simple cart or simple shopping cart project that he is working on. The cart has been called short and sweet and simple cart. We decided today that we would just call it the simple cart. We reviewed some code and made some plans. I also showed him some cautions and suggestions dealing with his current branch of code and how the actual code sign-off process will go down.

As a side note, Molly joined us right at the start. She and Spencer and I talked about memory management options for carts, sessions, and making sure that double clicks and duplicates didn't happen. I showed them a few of the things that we do on our carts to make sure that duplicates don't happen. They are going to look into their code and review things separately (Molly and Spencer).

7/20/2020: Bryan working with Spencer on Molly's API

Met with Molly and Spencer on a few different projects. We did a little bit on Leafly, checked on a new project to post a date for quantities being updated, and checked on a project for the customer queues and using those queues out in ecommerce land. I took a few notes and tried to help where possible.

Tons of other random projects and what not.

Phone call with Molly and Bryan going over ways to get real-time inventory counts. Including ecommerce, quotes, other secure shopping carts, and getting those details as fast as possible. We briefly talked about some of the things planned for mini conversions and being able to track the real-time quantities in bulk and keeping track of changes without updating everything. This is a big need if a 3rd party is using normal web or API sockets. Lots of calls and requests and not everything is changing all the time. It is becoming an efficiency type issue. They, 3rd parties, keep calling to get updated counts and we have to calculate and report even if nothing is changing. Too heavy of a load on the API sockets.

Small code changes for Danny and pushing up some new branches and custom labels. I also did two new pushes for Bryan on some of his code branches. After that, emails and recording notes. I also had to flip some stuff around on my calendar as most of this was unscheduled and pushed some other projects out of the way.

Jonathan Wells (designer) was on the meeting with Steve and I. He had some questions... the deeper we get, the more we really need to get all the way out to mini conversions. It is becoming more and more plain to see. Our users really want to see their quantities, units of measure, and weight equivalence values. We can fake it right now, but it really needs to go deeper for some of our reporting. Nothing new, we already know about this, we just are seeing the need for mini conversions being pushed forward. It is gaining momentum and steam (warming up and getting hot).

Steve and I looked into the restore quote to cart functionality for Molly. We looked over a number of core pages and also found some custom files. Nothing jumped out at us, everything looked pretty normal. We determined to do some testing with and without the custom code to see if that changed anything. Steve will do that later on based on his time.

The last hour of so was spent with Steve and Brandon going over their business model, going over ideas, and lightly pitching ideas back and forth about adilas as a trust, profit sharing, coop type options, and other business decisions. Trying to figure out the best approach and how we would handle investments, employees, ownership options, etc. Good meeting.

Meeting with Molly to go over some custom gram trackers. She has found a small bug between the restore to cart (quote back into the cart) and the custom gram trackers. We took some notes and will do some research on that. Towards the end of the call, there was a lot of talk about API sockets, WordPress, and Molly's new product that crosses adilas with Woo commerce.

4/15/20: Need a developer like Alan to look at core folders and files with Molly on clients server to make sure all is up to date.

4/21/20: Quoted to Move all 27 Systems to new VPS environment and Upgrade see Quote 1798

Emails

Met with Molly on an RFP for a state proposal. As we got in deeper, Molly was expressing that she has frustration levels on different projects. We are all trying but we are all getting pulled in so many different directions. She gets frustrated because she feels like she has to repeat herself. That is understandable. After a while, Wayne was able to join and he really helped out. Some of the RFP stuff had big huge acronyms and he understood some of that stuff. Huge help to both Molly and I. 

Quick meeting between Molly, Bryan, and myself. Molly had a question on the cross corp invoice to PO settings. The question was dealing with the new part number (items or products) on the incoming side and where to get the part status from. We determined that we would check the item being entered to see if it was a standalone parent item or a sub. We will then flip the new inbound status to match that vs pulling it from the invoice (from or source side). We made some decisions and will default some of the settings and logic.

On the phone with tech support and checking out servers. Steve, Alan, and I got on a GoToMeeting session with Molly to check on some database tables that had been jammed up. We did some repair work and got things going. Long day today. But, on the positive side, we have a great team and that is awesome.

7/22/2020: client interested once again. quoted at $500-$1000.

6/1/2020: Could have possible client interest in this.Waiting to hear back.

3/20/20: Molly's client paid to have subs all (from invoice adv search) added to report list. At the time adilas said they would pay to develop the same report under Inventory. It would use the same logic that was already written. Bryan started this project, Brandon finished. Not sure how far Bryan got for inventory report.

8/14/19: From Brandon's notes:

Working with Bryan on a deep sub inventory report. The thing that makes this one crazy is a mixed bag of sub inventory attribute filters (from across multiple categories). That little piece of multiple categories throws some major variables into the mix.

This is more for me... but we need to go back and do a full mini project to prep the field (general sub inventory area) better on sub inventory. We need to record the sub reference id numbers on the po/invoice line items table (both po's and invoices). We also need to record the main part id's, app type id's (items=11), and the part category id on the custom texts, custom dates, and custom numerics tables. We can use the main_id, app_type_id, and sub_id columns on the custom tables. We need to spend some time going backwards before we can go forwards with any speed. It may be a big mini project but hopefully it would help us as we try to go forward.

4/2/20: Was paid by Molly and completed.

3/10/20: $100/hour. 

9/11/2020:Documentation

 getSubQueueDetails - Web link - printable_web_api_documentation.cfm?id=976

6/30/2020: Moving ahead with this project. Starting with $500 and will most likely go up to $900, then $100/hour after that. 

List of queues, view queue, add to the queue= 3 sockets, possibly more.

3/10/20: 5hrs

3/3/20: Molly really wants to help make adilas e-commerce better. Using word press in the meantime to connect to adilas through API.

3/3/20: Molly willing to fund these api connections.

Molly needs in order to connect to wordpress.

Working with Cory on a possible tax calc bug. It ended up that it wasn't a bug, it just needs to be extended to some other with tax included scenarios. The question was dealing with sales tax calcs and settings from the store/locations, or the customer settings, or the cart settings. We just need to build it out a little deeper to handle the with tax included items if the customer is set to something different (say a tax category of government or something) and the items are set to with tax included. It removes the tax but it doesn't back the price down to what it would be without that tax. Sort of missing a step, but only for a certain scenario.

Towards the end of the meeting, Cory and I talked about getting other key players involved in certain projects. We were primarily talking about Kelly and Molly and other power rep/consultants. We talked about who is going to be the project manager and who would be the consultant on that project. We may need to define certain roles to help things flow better. Some of our projects will be built for our clients and some of our projects will be built for our power rep/consultants. There is a small difference as to who the client is. Somewhat internal or fully external.

We also looked at another project and some small bugs that need to be looked at on the general ledger stuff.

Working with Bryan on a number of small projects. We merged and pushed some code. Part way through the process, he invited Molly on to the meeting. We talked about delayed inventory counting and then some on the fulfillment center homepage and storing RFID tags on quotes. Eventually we had both Eric and Steve on the meeting and chiming in as well. Somewhat of project management by group/committee. The main topic was the time frame between a quote/order and invoice fulfillment. Anyways, we had some good conversations.

Discussing AdilasWPShop (new e-comm solution) formally known as WooAdilas

MVP - minimal viable product/plan

- Competition and how we help get some of the pieces past the finish line

- Platforms and building on top of them - WordPress, WooCommerce, Adilas, etc.

- Online ordering platforms, showing inventory, full ecommerce, drop shipping, ordering and delivery orders

- In-store pick-up or delivery or shipping options

- Tons of talk about deliver options, scheduling, picking date/times, etc.

- Small talk about integrated systems vs trying to mix and blend tons of independent products and trying to marry them together. There is pain in some of those pieces.

- Plug-ins (plugins) and getting things all tied together

- You have backend apps, frontend apps, customer facing things, options, assets, etc. Lots of mixing and blending.

- Pricing options on parents vs subs (parent/child inventory and pricing tiers).

- Using adilas API sockets to populate WooCommerce stuff using custom plugins.

- Certain pieces are pre-built by other vendors. Other things would be nice. And yet other things are already done by adilas as pre-built or custom options. Where do you build? Where do you spend your time/money/resources.

- Molly needs a gram tracker, custom discounts (discount engine), and better integration options. Currently she has to manage multiple applications and have one do one thing and the other do something else. Sometimes both applications do the same thing and you either need to choose and/or pick one or the other (more integration).

- Versioning and who has the latest cookie and how do you distribute that?

- Multiple ways of dealing with tiered pricing inside of adilas. We need to help standardize things there. As we were talking, there are some know issues with some of the ways that we do it internally (smart group buttons, parent attributes, etc.)

- Shipping zones, different fees for different zip codes, etc. WooCommerce has a ton of different pieces.

- Updates, reports, and getting the needed information quickly. This deals with shipping, queues, sub-queues, reports, and even clear out to element of time or somehow track the shipping, delivery, and/or in-store pick-up. We need to link up the delivery aspects and the customer queue.

- Claiming quantity and on-line orders affecting inventory levels and availability - small talks about quotes, transitional invoices, and normal customer invoices.

- There were also talks about state compliance systems and how in-store pick-up vs delivery orders may need to be handled.

- Messaging and using emails, text, queue specific, or different stages (as things happen) messaging. Notifies  and reminders.

- Acknowledgement and approving payments. We may need a setting where they could fill in some verbiage, and toggle on/off settings to show/hide and require/not require those steps and pieces.

- Coupons, promotional codes, referrals, etc.

- People want something that is integrated, fast, flexible, powerful, and easy. They also want it to look awesome!

- Tying in custom messaging into the customer queue, sub queue, and ecommerce orders. The queues are a great start... we just need to tighten up a few pieces and make it go full circle.

- Being able to automatically add in a delivery fee as a line item on the invoice/quote from ecommerce.

5/29/2020: Jonathan has a design worked out.

3/18/2020: Page settings: keep them but allow to collapse. Comes from the invoice sales and profit search page.

Print all option: Print to pdf view= looks like screen shot. Have a section of the mj operations page on the top of each section. You can skip to different sections. Each section needs to have its own total.

See attachment screen shots. a)Customer reports= data (like on mj operations page) then visual. Customer types and Queue Reports. Each exports as its own excel. Split expiring customer or patients column into 30 and 60 days. Then take over column 4 that is currently 60 days and make it queue reports.Add visuals. Switch customer types to be on the left and Customer Queue Report on the right. 

b)Sales Report= data =from inventory quantity/weight report. Use columns: category, quantity, weight, weight sold, running weight, sales price, cost, gross profit, percent. (remove vendor and inventory columns). Then add visual of sales. Want to see grouped by category and weight: ***How many 1/8ths, how many 5pk pre rolls, how many 200 mg edibles?

c) PO Reports: need to figure out how to recreate like invoices. Add the mj operations piece for this. (This example is actually from invoices.) We want to show how many did we purchase? By category and weight.

See visuals by category and weight. Need to group all by category and weight. 

2/10/20: Rewrite to mj operations homepage. Start with phase 1- first report for one corp. Walk first, then run. Have Charles work a few hours to make it look good. Get a better drawing from Molly, drawing over the mj operations page and reworking it. Use fake data. Includes all 5 reports Molly's clients want.

Multiple corps would be phase two.

2/4/20: Reviewed project 1627, 1628, and 1629 with Molly and got a new vision of what her client wants. This is all too much. (referring to the three projects- they won't want another system- what is the purpose? They want one page, one dashboard that is divided into 5 sections. One section has the customer data (new, total) one section has queue data: total time (queue to exit), avg total time, POS- exit time. Both of these have their data points and a graph. Section 3: sales and profit report with category and weight. Also multi or single location, multi or single corp. Daily, weekly, monthly, quarterly, all. Section 4: Purchases/Production- just pulls from PO's- no sales info- only cost. Still category and weight. Section 5: Inventory on Hand= looks to po's and invoices to determine. 

Want to keep it simple- similar to mj operations homepage, but just needs a little more data.

Original idea:1/29/20: Client wants a customer report with total customers and new customers displayed like invoice homepage data. Ability to print and also cross corp multi locations. Steve thinks we can use the invoice template for this and pull customer data instead of invoice data. 

Update: 2/3/20: Adding custom messaging to the queues. When you have delivery, you will have a certain message. We don't need to worry about the verbiage. We put the text field in and they can enter.

1/23/20: From meeting with steve regarding MI needs for e-commerce: See attachment for all notes from client/Molly. Below are Cory's notes on each item.

1)aQueue selection setting- required yes/no. Bryan could bring in queue code that already exists. (quoted at $1,000)

1)b Payment authorization= custom black box could be written by Bryan. Not sure on $ for this.

2) Back to consent check box: part of the black box above steve thinks- but isn't sure. Who else would want someone to have to check a box for consent to pay? Still discussing- no quote yet.

3)Another e-commerce setting related to queue. If using queue (yes) and queue is delivery queue, must hit a minimum dollar amount to be able to check out. Steve said it would be similar to disabling of checkout for having too many grams in the cart. Quoted at $500.

4) Currently can add a flat rate or use shipping matrix. Matrix can be set as 1-300= $10 delivery fee. $301-1000 (or whatever) = delivery fee= 0. This would need to be tied into delivery queue. Currently there is a box next to the shipping matrix that applies to all sales. There could be another box that that when checked applies to this logic:  If you use queue and it is set to delivery, then apply shipping matrix. Quoted at $500.

5)Could turn on signature fields one and two in corpwide settings. Create a setting for capturing enabled data. Customers could sign with finger or stylus or even type in that field.. This would show up after receipt is created. Quoted at $1,000.

6)Another setting in e-commerce, not sure how deep. You would assume it is their first time if the box isn't checked. Conversation stopped here, as Steve thinks liability is too high to control this, and that patients age and consent for data retention should be acknowledged/agreed upon when they become a patient. There could be consent forms that say "if you are going to shop/order online then you must read and sign this form..." get this prepared by attorney and have in each patient profile. Question: does MI say this has to be seen online or can this be achieved ahead of time? Seems more reliable than a pop up that says" Are you 21?" No quote- will need to discuss further if it's a must to have it online per MI regulations. Wasn't clear at this time. Would be custom if we go forward.

7) Setting in e-commerce to not allow to edit profile. Quoted at $500.

1/21/20: Steve wants to tackle this project. He is familiar with Molly's process and can see his way through it.

1/16/20: This is called an ICC- internal cost correction. Needs to work with both subs and parents: See ID #460 and ID#1015.

From Molly on 1/15/20: when someone enters incorrect costs prior to sales .. 

3/4/20: Spoke again with Molly on this important  project. Need a template when packaging to add sub attributes.

1/23/20: Spoke with steve today and he asked to have this assigned to him so he can start working on it.

Spoke with Molly about this project. Needed to be added to the project list.

Second step of this process would be converting each to grams for metrc purposes in the build process.

Meeting with Cory and Molly on different projects. One of the topics was inventory threshholds and a virtual inventory engine. We talked pros and cons and discussed developers and who could do what. We also talked about some cross corp stuff.

Some of the projects are small and quick, but we tend to fall off the wagon by having so many things ready and virtually queued up.

As of 1/6/19, this project has been started by Bryan. He had some downtime and Molly asked him to start. She knows to put these requests through to Cory in the future.

Would add it to normal advanced line item search and super advanced line item search through html, and need to be able to export both as well.

12/16/19: Currently when you pull an advanced invoice search, it gives you the option to specify a category, or you can leave it as all. But the data doesn't pull into the report. The tax category pulls into the report. Many clients would like to see the category as a column in the report. 

This would be core and simple to do.

4/6/20: See attached image for report look. Will pull from inventory engine and inventory #;sf. The report will pull from the thresholds set in the inventory engine (no changes to Josh's code) and only those items that are below the set threshold will show. Ex. if item is set to 20, and it has 20 in stock= won't show. If item has 19 then will show in report. The report will show the on hand quantity for the item (parent and subs) Same example, this item would show 19 as quantity.

1/21/20: Waiting to hear back from Molly's client on what direction they want to go.

1/7/20: Spoke with Josh about this and also Molly. Josh thinks he can do something that won't be super complicated if we use his existing threshold "engine." Clients would add min in his engine. We could direct it to a different page so clients wouldn't have to access from shopping cart. It would make it location specific due to the fact that it is connected to the cart location (I believe). He could do a simple report that pulled that data and if clients had different threshold settings per location the report could pull both.

Molly really wants to do something simple, but maybe a step above what Josh has, although the multiple thresholds for different locations hadn't originally occurred to her as something her client might want. We need to discuss further.

12/16/19: Currently exists in the shopping cart. Called Inventory Engine. Dealing with thresholds. Currently not tied to locations- only categories and items. If you have multiple locations it can get messed up. Not in inventory report itself.

Molly's vision includes another field in item itself. So when you set up the item, you put in a threshold quantity. Dashboard would show all items below their threshold grouped by category, vendor, item, and live quantity.

Brandon proposes a separate table- master setting for tracking thresholds- turn on if yes or no. No= leave it. Yes, allow for extra piece. Automatically set it up. Show the locations if they have them.

adilas will match funds if built as core.

12/12/19: I have a client who is requesting something related to adilas project referenced below. Specifically, they are requesting a dashboard, that shows inventory items (at any current time) that are below an item level qty threshold. 

Molly and Spencer were talking about phase 2 in their woo-commerce project. It is a cross between woo-commerce and a backend adilas API socket integration (codenamed wooAdilas project alias). They were talking about some of the newer Adilas features such as customer loyalty points, discount engine stuff, gram tracking, tiered pricing models, etc.

They would like to get their hands on more of the backend database information on some of these newer topics. We talked about possible custom API sockets, new public facing API sockets, or even passing virtual cart data back and forth. As the discussion progressed, we even came up with an idea of a database storage record called a cloud cart that we process and fill in the data and then pass that back to the user through the API socket connections. Just an idea.

At the end of the meeting, we talked about another project and which developer would be the best fit. Molly is doing great and headed in the right direction. She has been interfacing with the different developers very well. That is awesome. She gets my vote. Good stuff.

Cory and Josh were talking about the number of clicks, settings, and being able to show/hide certain fields. The two hot points were the shopping cart and the PO (purchase orders) page. Basically, getting items into the system and then being able to sell out those items quickly. We are leaning towards some shopping cart settings and also breaking down the needs into smaller steps as we know that some of the pieces may end up being really big.

We talked about sketching things out on paper/pencil and then moving things into a graphic mock-up, coding and then wiring things up.

We showed both Josh and Cory some of the new graphic mock-ups that are being done by both Jonathan and Chuck. We looked at some of their ideas and mock-ups to talk about options, layouts, and configuration options. We talked about showing them, meaning our clients, some of the mock-ups and graphics of where we are heading, that would be way better than having them design things from the ground up.

Managing customer expectations. That is always a challenge. As we were getting deeper and deeper, we are seeing more and more needs/wants of being able to configure and customize their own settings and such.

One of the projects that we talked about was dealing with updates and helping to let our clients know about certain updates before they get rolled out, especially if the updates may have consequences and/or possible issues. Some of the high traffic areas are carts, invoices, and state compliance stuff. We talked about delaying some of the updates instead of just pushing up new code.

Josh recommended a update log that could be searched and even have a small blame section - who coded it. Hopefully blame is the wrong word, but we all know what that means.

Maybe a different section, like the developer's notebook, where we could publish some of the updates and make announcements. We also talked about scheduling the code pushes and making sure that we aren't running faster than we are able.

Molly joined us towards the end of the meeting and had some great comments. Good stuff.

4/20: 27.44

from 4/14: 30

Up to 3/1: 26.48

from 11/19 through 1/1/2022: 112.4

11/18: 15.56

11/17/21: 17.5

10/21: 12.08

10/18: 38.04

10/5/21: 27.07

John is working on this:

2/25/21: Notes from today's meeting with KW and SM. Also from another eot that I just found today.

1) Choosing the hour is available for the everyday option. When you choose a day or a range of days, you should have the everyday functions of adding time frames. Multiple per day would be great ie 9am-10am, 10pm-11pm (Happy hours- only Monday through Friday)

2) Settings that allow the discount engine to connect to e-commerce!! 

3) Possibly the discount happens in the cart and not when added to the cart. (In ecomm only adding one item at a time) This will help with the buy x get y. *We did determine that the limit of how many line items can  receive the discount happens in the cart, so it seems there is already coding there for this.
Minimum =needs to pull from the cart info and not from when scanned.

4) Adding functionality that allows for multiple categories and multiple items. Currently, if you choose one category you can assign specific items. If you choose multiple categories you do not have the option to assign specific items.

5) A snow owl pop up so you can sort the vendor list or item list as they are super long. Would be great if the vendor list only included inventory vendors, and even better only vendors who are associated with the categories or items. 

6) Not imperative but an add or edit or submit button at the top would be helpful.

7) Not imperative but would be nice to show in an item if it is linked to any discount engine items. Similar to how it shows that an item is connected to a smart button. Could go right there next to the smart buttons.

**There seems to be a weird scenario, where if you have the wrong vendors populated in the list for the item that you choose to discount, when you add that item to the cart it doesn't recognize the discount. Kind of goes back to limiting the vendor list.

Adding other notes: Everything on this date was quoted at $5000.

6/9/2020: Notes from meeting with Kelly regarding upgrades/fixes to discount engine:

1)Currently for each line item you add through the discount engine, it creates a description in the non printing notes. This can get messy for searches. Possibly make this a permission- do you want this to print? Or, only print once.
2)Most people want to price items more than they want to give discounts. 
3)Needs to work in e-commerce.

Josh will be finishing up phase one of discount engine this week (9/11/19). 

Buy X get Y (a more flexible BOGO). This has been asked for quite a bit by clients. Josh estimates this is a larger scope, as additional fields would need to be added to the database. Estimated time would be 2-4 weeks.

Buy X Get Y
   -  Categories for X
   -  Categories for Y
   -  Parts
   -  Vendors
   -  Time Periods
   -  How many max uses
   -  Make any purchase on Friday, get a free joint

Buy 2 Get 1
Buy 5 Get 2

3/13/20: Molly specific requests: Updates requested, including improvement for: Tiered Pricing, Buy x Get Y. Corrections for Buy X, Get X: not just Line QTY Requirements but Add Total QTY requirements so this works for people who scan. 

11/25/19: Not sure how high on the priority list this is. Putting it down in the list for now.

One client experiences that the discount engine takes quite a while to load (I haven't see this, but Drea did see it on this clients system). Wants to add buy x get y.

Interested in having boxes next to the days of the week so you could run a special Mon, Wed and Fri. 

Have the vendor list after the categories, and if you only choose one category, choose the vendor, and only have that vendors items populate in the list.

Can you exclude specific items from the discount, the way you can include specific items?

Discounting based on key words.

Molly and Bryan joined the meeting. We introduced them to Chuck (designer) and showed them some of the new things. After Chuck left, we looked at the cross corp invoice to PO functionality. There were just a couple of tweaks that were needed. After we figured out what was needed, Molly left and Bryan and I added some code and then pushed files to all servers. We are making progress.

Steve, Danny, Eric, Alan, and myself were on the morning meeting. Danny had questions about how to be more productive in keeping project notes, searching for things, and getting to the project details quicker. We mentioned that he could build his own top payee links (custom button) or write the id number down and then be able to go from there. We also briefly talked about having a super flexible quick search option for expanded time search. Something that would search elements of time and be able to search the mains (normal titles and notes), the sub dates and times, the sub comments and notes, the sub flags and tags, and other pieces. That would be really cool. Maybe a time-all search or something like that.

Eric and Steve were talking about new rules for the customer loyalty points and adding in some new rules. Eric is getting close on that stuff. They spent some time talking about discount rules and other advancements dealing with the special accounts and the customer loyalty points stuff. We are making progress there.

Steve and I were talking about an upcoming demo and some of the needs and direction of where we are wanting to go. Steve offered to fly out and help with setup and what not if needed. We went over a few items and talked some strategy.

After that Alan and Steve were working on some Metrc packaging stuff.

Bryan and Molly jumped on and we looked at a small bug in the cross corp invoice to PO code. We jumped on live servers and looked at database records and tried to find out what we were able based on simple searches and changes. We then tried to implement the new changes. Bryan is going to put up some small changes and we'll do more testing and go from there.

From Molly email 10/26/19: Making those phases dynamic (except for maybe with state connected databases) would allow someone to customize their phases a little more. A lot of my cannabis clients have propagation, veg1 and veg2 phases before flower. (Or they don’t want to call it propagation).. Maybe some people don’t want the harvest “phase”.. I think making the phases more flexible would help long term. I’ve tried adding phases to the templates once or twice but as I recall it doesn’t work properly when I do.

From Molly email 10/26/19: Even more of a priority, the problem I have right now is that I can’t connect clone batches to harvest batches.. this clouds the transparency of a plants complete record. I would like to figure out how to connect the plant and harvest elements of time...maybe via flex? 

1/21/20: More loyalty points functions needed. Brandon said he was aware of these:

1) Add a blue level permission for setting up and managing loyalty points program so that a manager can use it without accessing the balance sheet.

2) Automate voiding of loyalty points when invoice/sale is voided.

3)"Depositing loyalty points" This is on the radar- to map the payments not yet deposited to COGS so that owners can see what the loyalty points are costing them. Currently can leave undeposited or do a workaround and deposit with an offsetting deposit line to reduce revenue (other revenue-not from sales).

10/28/19: Both Molly and Cory have clients who would like to be able to limit loyalty points to customer types ie members, guests, etc.

Another client also wondered how to delete or edit points once allocated.= Brandon said you can make one negative transaction to offset the points accrued.

& Gift Cards

Going over loyalty points. See email for GoToMeeting id.

Molly and I met for about an hour, we went over some of the math on the customer loyalty points and how things are working. We made a small list of recommendations and small things to check and/or make easier. We also spent some time talking about sub inventory and getting new reports, new API sockets, and making that section tighter. We also talked briefly about developers and team management practices. Great meeting.

Working with Bryan on the new code to monitor and track edits and changes to parent items and products as well as sub inventory or child items and packages. This was a custom project commissioned by Molly, an adilas rep. We spent some time making a plan, doing some final checks, uploading database script files, and going to each server to run the updates for both global parts and items and corp specific sub inventory tables.

Working on the code review for the last modified dates for parent items and sub inventory items. Bryan has almost 50 pages that are being affected due to the new last modified date code. That includes a new API socket to pull data based on the modified date range. We didn't push the new code. There was one page (the database update) that still needed a little bit more work. Bryan has a plan and we will meet again tomorrow to push things up live. Due to the database update, we will need to push it up in phases.

Working on the special accounts project. Added in some logic to watch for rules that are set to inactive (don't use or don't play). I also got contacted by Molly and had to jump on a quick cart fix for the inventory threshold engine stuff. Made the changes and push the new files up and online.

Spring 2020: Jonathan Wells did a work up. See attached video. Waiting for funding of half. Tracking this in project #1627. leans heavily on requests of molly's client.

This page is ugly!! Drea has been asking Steve to fix this page for awhile. 

Dustin has started working on a hub- includes testing, licensing, other operational details. Calling it an oversight hub.

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

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

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

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

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.

Talking about delayed counters and working on phase 2 of that project. Molly, Cory, and Brandon were on the call.

Known needs:
- we need to be able to include subs
- we need to be able to scan subs - currently only scans parent subs
- we also need to be able scan and hold (scan every unit in a bin) and then have that count for you
- multiple locations and being able to scan and hold - not really real adilas locations - kinda like sub locations within the same location
- be able to ultimate review before submitting for processing
- on the review, you could see who scanned what

// ideas

- Maybe a new button that allows for multiple scans (scan to count) - Once it comes up, maybe a spreadsheet like column with multiple lines

- On the review and commit page, be able to search and filter by item and by person and by notes.

- You also need a way to remove and/or combine certain pieces. Kind of a fully functional master overview.

- They would like to see some new quantities such as total amount scanned, system count (on hand), and an open field for the real quantity. Maybe even show them the math before we actually do it, meaning another quantity called math adjustment quantity (non adjustable >> just a math calc).

- On the review page, they wanted a little bit more info without over doing it.

- We may need to change the database model and move from JSON text to real database entries. This would help with searches, show/hide stuff, and better ways to clear and/or delete things out of the process.

- Molly was talking about the importance of date filters and date/time stamps

- They don't want to see all of the sub information (too much). They would like to rework the normal update PO process. (update_inventory_count.cfm page). They would like to have all of the subs open by default, take off all of the extra sub info and sub inventory attributes. Keep it simple and easy. They like how simple the delayed inventory counter looks but even that one needs some new fields.

- Some of the people use this process every day. Many of them use it at least monthly. They really want it work on a Wearhouse type model. Lots of scans and less clicks. They want more of a barcode based model.

- There was some discussion on how to display the review and submit page. Some of the comments were grouped by parent item and then broken down by person who did the scans. They were talking about having a total summary line per item and then some sub details that could be showed if needed (collapsible like the show subs option for sub inventory).

- There was some talk about storing multiple steps in the session scope. Basically another way of delaying the inventory counting. Currently we submit each page... the question was raised about submitting multiple pages and then having a final review to do the real submit process.

- As a side note, the action page for the delayed count process aborts and shows a dump. We need to help and clean that up.

Web link - time_web_gallery.cfm?corp=22&id=1485 - community funded project for this piece.

See attached for a link to the video recording of the GoToMeeting session.

Multi-vendor cross corp invoie to PO. We had Bryan, Molly, Cory, Brandon, Alan, and Steve on the call.

Currently we can do cross corp invoices to PO's. The hiccup seems to be with multiple vendors and making sure that the mapping is correct.

Molly logged in and showed us some examples. The goal is to be able to move inventory between systems without creating or setting up the items on the new system. Basically, they want to grab the info from the system and then use that info as quick as possible. The main source is the outbound invoice. It contains, potentially multiple items from multiple vendors.

Mapping on the main vendor (at the corp level). This is where the main invoice comes in at.

Then mapping on a per line item level. Each line item needs to be mapped to a different vendor based on what the invoice has. They want the line items to default to the same vendor name as the source invoice line. There is already a custom map option. The new functionality just includes a possible vendor switch as part of the mapping. They are looking to get a vendor drop-down on a per line item level. Currently, there is only a drop-down that allows you to select the item category. They still want the mappings... to help speed things up, but they want a vendor assignment to be part of the new mapping process.

If the vendor doesn't exist, be able to add it in on the fly and set the vendor type to inventory.

There is a new vendor based flag called the default vendor type (created by Steve but not fully cascaded through the system). They want to be able to use those flags to show up as a possible vendor option, vs just checking to see what vendors do have real items. They would like the vendor list to either look-up existing items or be flagged as an inventory vendor. Another possible option is show all vendors or do a perfect vendor name match.

They are using this cross corp functionality to setup new systems. They basically have a master corporation, that already exists, and then they just start transferring and selling back and forth and the items get pulled from master corps to the new corps.

An idea was submitted by Steve to go into the existing systems and flip vendors and vendor flags as a background task to make sure that the new feature is fully used. We may also want to add some code to help flip that switch as a vendor is added and then used on a PO.

There were some discussions on conditioning the application to help protect the companies. Sometimes the deeper we get, the more we actually have to code in some protection and safety measures.

See attached for a video recording of the meeting.

As of 3/23/2020: You can scan a sub barcode and automatically count it as one, then keep scanning. Then it will tell you how many you have at the end. Or you can scan the sub barcode and tell it you have x quantity.

**What doesn't work is the "update using selected quantity totals"- this creates the update PO- but it doesn't work for subs yet. We need to have a setting to disable the button if the corp is using subs so they don't create a mess. Not sure if we will fix this button or not- it automatically makes the PO, but would like a review first. (see below)

Molly thinks her client would pay for the next step, which is having a combo of the review page with the update inventory counts page- so you can see how much inventory you actually have, before you submit "update quantity." Essentially a web version of the excel report. Would be great to have it sorted by scanned or not scanned- if in snow owl could sort. You wouldn't have to go through and do the update, but you could make changes if needed.

Want to have a note field per line item after description (instead of just notes at the top of the PO)

As of 3/3/20: Still working on this project- things keep breaking...

9/9/19: Molly working with client on their specific needs. Attached some drawings today.

Need to start phase two. Brandon built a custom upload piece for a client that takes a csv file with a scan and a quantity with spreadsheet. Two columns: barcode and quantity. 

8/13/19: Spoke with Molly at length. Need ability to scan sub barcodes/ids as well. Currently can't submit 0 as a quantity. Also can't add quantity if existing quantity is 0. 

Ability to have multiple stations performing delayed scan count at the same time to facilitate end of day inventory. Already track payee, which is great. 

One idea for organizing data on the screen: On delayed inventory counter review & commit page (Web link - inventory_counter_review.cfm)

Have one line item similar to a parent- total quantity scanned, then under it, each line item or sub scan which would refer to each station/payee who was scanning inventory. 

Then total quantity on hand and total quantity scanned/counted, so that you could compare/review before committing to the numbers. There would be an open field next to the total quantity scanned so you could add another in, and then you could update using selected quantity scanned totals. 

8/12/19: Clients would like to scan every package (with same barcode) and have adilas keep a tally of how many and report that at the end for the final submission. So there would still be the review and commit page, where, after scanning barcode ~1234 50 times you could see that, and then click update using selected quantity totals. This would help cut down on human error.

10/7/19: Bryan has started working on this. Met with customer last week to confirm they like the direction Bryan will be taking this in. They contributed $2,000 to the project.

8/19: Molly, Brandon, Steve, Cory and Bryan met to work out the details. Brandon took note and recorded meeting.

Bryan has been working on this functionality. Molly, Brandon, Steve, Cory and Bryan need to get together on this.

8/13/19: Brainstormed with Molly. Choose a special live/mixed vendor PO to facilitate this process?

Should be able to associate vendor with item in the cart from originating corp, even though the item isn't on the invoice (all items are associated with vendors).

Perhaps in order to show up on a drop down list in the Special PO, must have item under the vendor in the receiving system and the original system exactly the same. 

This will be highly useful to Distribution companies.

Bryan and I had a good work session. We were working on sub inventory searches and results for invoices. Currently, the code allows for searching of sub inventory by a single part/item category. That keeps all of the sub attributes lined up and programmatically readable. The new challenge is allowing sub inventory searches on any and all categories at the same time. This has a number of challenges.

For example: Each category could potentially have the same sub attribute name (the id's are different but the names are the same). All sub attributes are setup on a per category basis. The different categories could potentially assign different data types to the different sub attributes. The known data types are numbers, text entries, and dates. All of that data is stored in different tables based on the data types. Say that each item category has a sub attribute called "Batch Number". If I have 5 categories with batch number as an attribute, they don't want to see 5 different filters, they want to see one filter (a grouping) of that sub attribute. This gets into a deeper problem of pulling the data back out because technically, the data is stored based off of id numbers and column numbers (order within a category). All of those could be different. It becomes a mixed bag.

Anyways, this was our challenge today. We had a good work session and made a list of to do items to help guide us along the way.

Meeting with Columbia Care. We had Molly, Guy, Megan, Steve, and myself on the call. The topic was - ways to improve the tech support and communication.

Talking about advancements in technology, beefing up servers and capacity, and other options.

They would like a way to get immediate support from Adilas. Guy was pushing, somewhat, on helping us to get to the next level. He had some great ideas and seems to be a server expert (monitoring and reporting on server problems). We, at Adilas, need to get Wayne more involved on the monitoring level. One of Guy's main object was to look at the source and/or problem vs just rebooting the server. He said that he is willing to work with us on getting a better reporting and analysis system in place. All of these advancements will help all of our clients.

Towards the end of the call, we committed to get with Wayne on some additional monitoring and also sent them a tech support cheat sheet with phone numbers, emails, and light reset/reboot instructions.

Kinda of random day so far today. On the phone with an adilas developer going over some changes. Small bug fix for adding new parent items from a PO. On the phone with Molly, an adilas rep, going over needs and tech support stuff. Paying bills and other light tech support things.

Had a 45 minute meeting with a front end designer named Jonathan Wells. He is very talented at graphics, moving animations, and UX/UI (user interfaces, user experience and design). Super cool meeting. His portfolio is: https://designjwells.myportfolio.com/

Bryan and I worked on some new logic for some sub inventory searches and exports. Some of it was some training on complex data sets (arrays of structures, and arrays, with sub arrays, etc.).

Steve, Dustin, Wayne, and I were on the morning meeting. Wayne was working with the guys on some of the changes out in the AWS land stuff. Once I came on this morning, Steve and Dustin jumped off to work on a separate project. Wayne and I talked about some logo and image changes and then some update queries. After that, I did a local database back-up and got ready to uninstall and reinstall some database servers.

Bryan, Molly, and Eric joined the meeting. They were talking a lot about 3rd party solutions and who pays for what. We also talked about some needs for sub inventory. We need API sockets, documentation, more integration models, etc. We even started talking about 3rd party solutions and diverse plug-ins and how to best help that model out. Not all solutions are worthy of spending the time to fully integrate. We want to enjoy working with these other companies.

Molly is looking to expand the searchability and export options for sub inventory. They have done some foot work and worked on a custom export for sub inventory. They would love to bring some of that more into the core process. Currently, a lot of the filtering is done from the parent level down to the subs. We are seeing a need for being able to filter from the subs up to the parents (reverse filtering). We briefly talked about adilas and that we will be doing a new adilas funded round on sub inventory. Currently, we have done 3 full rounds on the sub inventory section. We will be bringing in Alan Williams to help with this project. Before we jump, we are looking for a proposal and/or a plan for going forward.

The conversation started going towards... what is coming up next both with adilas and in general. The landscape keeps changing. What are the priority on the different projects that are coming down the pipeline? Molly was expressing some of her priorities and where the needs are.

Pagination vs grouping - Going back to sub inventory... We need exports and searches on parts, items, sub inventory, parent attributes, sub attributes, etc. To sum it up, we need better reporting on sub inventory and everything that it touches.

Towards the end of the meeting, Steve and Dustin were working on some custom reports and I was working on new install stuff for my local environment.

Bryan and I jumped on a GoToMeeting session. He got his cross corp mapping code ready for code review. We spent the first part of the session going over changes and doing light clean-up. Once we got things merged in, we then invited Molly on to help us look things over. Almost immediately, we ran into a new request to provide a corporation to vendor cross corp mapping. This new project already does a number of cross corp mappings from items in one corporation to items inside another corporation. It was kinda funny that almost immediately we needed another cross corp mapping.

One of our goals deals with the application flex grid (interconnecting or mapping anything between corporations or even between systems or software platforms). This is kinda still a dream, but we are making progress and seeing more and more needs for this kind of thing, function, and/or tool set.

Molly and I met for about an hour to talk about options and possibilities for ICC's or internal cost corrections. She started out saying that she has worked with a number of clients and sometimes it takes up to 20-30 hours to do some clean-up (depending on the size of the client and how long its been since the last cleaning). As a side note, we see bigger problems with normal parent inventory due to the last known cost that is held at the parent item level.

Sub inventory is much tighter and works pretty good. The only known problem with sub inventory deals with some rounding error problems over time. Basically, by the time you split up certain known costs over and over again, clear down to 5 levels of decimal accuracy, there becomes a small rounding error for certain items. It is just math but it still ends up looking like a problem.

The catch 22 is on what it takes to look things up and fix them. On parent inventory, Molly goes and looks at the usage per item. She can then fix things fairly quick. On subs, there are much less problems (originally), but sub inventory is even harder to clean-up due to closed packages, parent item settings and status, and some of the math.

The main goal is to get the cost of goods perfect and/or help the user get to a perfect level. Ideally we would like to build out a new core tool called ICC's or internal cost corrections.

Molly would really like it to follow a FIFO (first in first out) type model for costing. This would require us to be able to go all the way back in time and see what came in and at what cost. It would then try to reconcile itself based on how many have been sold and at what value. For example: if we start out with a 100 at $0.45 per, ideally, we would sell the first 100 items for that $0.45 cost. It gets complicated as things change over time, we don't fully sell out of a specific quantity based on cost, or a person buys multiple things from different cost levels. We have also had problems with users just going in and randomly changing item costs.

- At some point, we need to make an adjustment and/or update to the COGS (cost of goods sold).

- Molly was talking quite a bit about the in/out extended cost. We had some discussion based on FIFO vs last known cost.

- Molly and I were trying to figure out basic rules - only grab items that have an in/out extended cost that is not zero and a quantity that is not zero (don't worry about items that match perfectly or have zeros). If an item has a quantity (+ or -) - we need to look at it. We may need to work backwards to get our numbers.

- We also had some discussion about are we trying to get super detailed (matching PO's with invoices with costs) or be more general and just get the grand totals correct per item? Good discussion. We left off with Molly going to reach out to Eric to see if he has more time to meet and work on a tool/report to help fix things. I am supposed to think about options and come up with some ideas. Lots of moving pieces.

Up early trying to figure out a sub inventory search and/or sub barcode search error. We had a bug reported and I watched an online meeting recording between Molly and Steve where they were going over the error and what was causing it. The error seems to be a disconnect between the sub inventory id (transaction id) and the sub reference number (how packages get related together). Anyways, I spent a couple of hour and tried to crank out some changes. I pushed them up and tested them and everything worked for me.

As a side note, the guys had to reverse the changes later in the day (I was out of the office). The new code fixed some things but made other things worse. One of the new things was dealing with Items being scanned and then coming into the shopping cart at a $0 value. It wouldn't happen all the time, but enough that they reversed the changes. We'll hit it again and test it deeper and more thoroughly. Alan was the one who helped reverse the changes out.

Talking with Molly about adjustments to the inventory values (current inventory) as well as cost of goods sold (items already out the door). Some new questions coming up with sub inventory and how the details are being spread into smaller and smaller pieces. We would like to look at a quick calculator type tool to help out with problems and/or adjustments. How could we use an update PO to help adjust costs diffs? Does it belong on an update PO or some other tool? Great questions.

I put a couple of links out for her through chat to help with research on ICC (internal cost corrections)

https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=ICC - research on ICC's

https://data0.adilas.biz/top_secret/community_funded_projects.cfm?projects=1015 - rough quote

She showed me her current process. She started out by going to the grouped inventory page.

- The grouped inventory page is where they (our clients) then to see the cost problems - quantity of 0 with an existing cost

- She is pulling every usage page (per item) and going page by page to see if she could find the problems and/or issues.

- Per location, current quantity times the current cost should equal the in/out extended total - see screen shot

- She adds a positive and a negative (no change in quantity overall) but we need to alter the cost diffs.

- If we could check if the current cost times the current quantity matches, then great. If different, show a flag and allow the change/update.

- She would really like to have a tool that allows for a recalc of the extended costs (both on the inventory side and the cost of goods sold - both sides of the fence).

We reviewed some videos between Molly and Bryan. It was dealing with some flex grid tie-in search results. We ended up finding some hardcoded values in one of the exports to MS Excel. Changing that back to dynamic values should fix that one. The other one was dealing with sub barcode scans. The problem was multiple packages having the same sub barcode and the code not worrying about the location, just the package.

Pushed up some code to help with the servers.

Small GoToMeeting session with Molly. We looked at a small API socket connection question. They were really close. Just missing a who did it id number (transaction processed by id). Once they got that, they were good.

We also briefly talked about the possibility of setting up some hooks to help with a 3rd party solution and an API socket feed out from Adilas to woocommerce and back from woocommerce back to adilas (syncing up products and quantities). Molly and Spencer may be looking into that option and building a new 3rd party solution to help bridge that gap (building and selling a woocommerce plug-in for adilas clients). Good meeting.

On a meeting with Bryan. He showed me his progress on the unique sub barcode project. We also got Molly, an adilas rep and consultant on the call with us. We answered some questions and made a small tick list of 4 new items. Bryan and I then started working through the items. We got 2 of the 4 items done and setup a time to meet again tomorrow. After that, we spent a little bit of time talking about some new 2nd or additional vendor info on PO's. Bryan has a client that needs some tweaks and we talked about some new settings to help control those pieces. If we don't go the setting route, it would be multiple black box pages per corp (already looking at 10+ corps that need that feature). We are leaning towards new PO settings.

Random notes from the day. Brian Stewart is a friend and 30+ year computer guy and programmer. He works for a different company but we go walking and hiking together in the mornings. We talk business and code while we walk. Here are a couple of gems from today.

- There is a difference between working in your business or working on your business - Brian Stewart on a morning hike.

- Create systems... Instead of setting pass/fail goals... create a small system and then start playing the game. Success is playing the game and working the system. The results will usually end up following. - Brian Stewart on a morning hike.

- Brian and I spent quite a bit of time talking about good cop, bad cop, and helping to setup the community and environment that you want for your company. A lot of the discussion was dealing with finding that balance point between speed, function, stability, and beauty. Not everybody has the same personality and/or skill sets. Lots of mixing and blending. Some of the conversation was how to mix senior developers and junior developers and to help them play well together. Sometimes that mixing becomes an issue and also a who gets credit for what and who gets paid for what. Sometimes a tough mix.

On the morning meeting with Steve, Dustin, Alan, and Josh. We started out and got things going. Dustin is going on a trip soon and was reporting about some areas in the North East that he will be visiting. Sounds fun. Here are some other things that happened on the meeting.

- Helping Dustin with some FORM logic. He has a ton of form field data that needs to be dynamic, grouped, and passed over to an action page and still be able to maintain its complex data format and maintain its special groupings. We went through a number of scenarios and he took a number of screen shots. We talked strategy and I showed him some similar code that is used for duplicating PO's and passing dynamic data from page to page.

- Talking with Alan about the idea of on purpose allowing the view of the pages to fracture and be more controllable. We did a small graphic (drawing) and talked about how we have known form field values. We also have a known database table that could hold the data field settings such as show/hide, defaults, data types, special instructions, sort values, field name aliases, etc. We then talked about how we could potentially use ColdFusion custom tags to hold the logic to dynamically populate and/or build the HTML (web format) pages based on the custom tags. The custom tags are a combo between a function and an include. Anyways, we had a good discussion on that. Alan was saying that this plays in perfectly to the MVC (model view controller) type scenario that we would like to use. See attached for a small drawing.

- We had two other outside parties come into the meeting. We had Molly (an adilas consultant) and a guy by the name of Ryan McCorvey (a user for McCorvey's Pro Shop - Bowling). They both had similar requests. They have different pages and reports (or functions) that are hitting time outs. Both companies have tons of data and Alan and I were taking notes and looking for possible bottlenecks and either slow queries and/or slow database tables. They could do the same reports and actions with small amounts of data, the system just choked and/or timed out when trying to process too much data. Kinda like getting a huge mouth full and not being able to chew and/or swallow. Anyways, we worked with both individuals and took some notes. Alan started looking into some research on what causes those table level slow-downs and what not.

- As we get into bigger and bigger datasets, we have to play well with scalability, indexing, and being able to play the big data game. Interesting how things keep progressing.

On a work session with Bryan. We started out talking about code and getting new pieces and features up and being used quicker. There seems to be a big bottleneck with me as the primary code sign-off guy. I just get pulled in so many other directions. If something is more pressing, the other projects just sit on the shelf. We talked about styles and how best to help push things forward.

After that, we spent the rest of the session working on a plan for the unique sub barcode for sub inventory. This is a prep step for the cross-corp labeling that some of our clients want to do. Bryan was asking questions and recording videos and I was navigating, drawing, typing, and trying to help explain the project scope and what pages and pieces need to be touched. I don't have the videos, but Bryan made a number of small clips using his small capture tool. At this point, we have a small lightly sketched out plan. He will push things forward and ask questions along the way as needed.

At the very end, we talked about some other custom projects and how those are funded and/or pushed through the system. We also talked about a small project that had to be reworked and who pays for that. We had some good discussions and seem to be on the same page. Good meeting and we're making progress.

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).

Homepage for Cannabis Production

This homepage will provide views of current inventory, and allow all inventory to be processed and packages as desired.

All functionality currently exists however this page would speed up the process by completing the internal builds on the fly.

Bryan and Molly jumped in and had a number of questions about both labels and mini conversions. Both of those topics are heating up and gaining more traction. As a side note, we are seeing more and more pressure from the outside state tracking entities. We are also seeing the need of for more cross-corp and/or internal mappings to help certain data fields (for example - sub inventory attributes) keep passing them along. Huge need for internal manufacturing, parent/child inventory, sub inventory, sub attributes, parent attributes, labels, and going clear out to mini conversions. All of this is fully connected and all of the pieces need to be there.

We are also seeing possible needs that will track the main quantity and main unit of measurement. We also need the mini conversion quantity and mini conversion quantity to be recorded. See the attached screen shot that shows both the main and the mini conversion values to both be recorded.

Brainstorming with Bryan. They wanted to use a barcode to prep and fill the smart groups - under my cart favorites. Bryan and I went through a funnel drill and identified requirements, inbound values, possible tools, and then what we could do to finish things up. Good practice session.

We switched subjects and talked about sub phases, sub locations, and pulling stats and reports from the data. Basically, what were my yields and such? The deeper we looked, his client wasn't using anything in the elements of time section. Bryan is going to check with Steve and see where he would recommend that he go and/or direct the client to use a different function or process.

Brainstorming with Russell and Alan about the upcoming training event.

- news and updates, snow owl theme (look and feel and custom links), ecommerce, email, time clocks, other projects

- sub inventory training

- lots of emphasis on what is new and how that works and changes.

- reflexive flex grid, 2nd vendors, review what has happened over the years (maybe even research and setup a time line), future projects

- stay on task

- give industry specific training and maybe schedule things for a different training session or breakout sessions.

- open learning time... specific time to just practice with reps and consultants

- planned and special breakout sessions. So, for example, from 1-3 pm classes taught on this and that in this room and that in this other room, etc.

- as we host cooler and cooler events... we really have to charge and be professional. Make it really cool.

- try to shoot for 4 days. the 3rd day is mostly hands-on training

- 9-10:15, 10:30-12, 12-1, 1-2:30, 2:45-3:45, 4-5 sessions.

- make each day specific to the task at hand

- best practices

- Roxanne - training on financials. Lots of others who may be able to play.

- Having a pizza party with the crew - being able to hang out

- day 1, here is what is new with adilas. Maybe here is what is coming. Make it exciting.

- day 2 and 3, more specific training - POS (point of sale) and CRM (customer relationship management) stuff.

- day 4, hands-on training, one-on-one training, group training, open sessions, and industry specific training

- thinking about skipping the financial side of things for this first training

- we teach in general and then point them to the specific consultants to get industry specific info and advice.

- Get some of the power reps and have them be ready and available to help. Maybe even allow the reps to charge extra for custom time.

- Have someone who is watching for comments online and also taking notes. Someone to help with chat

- We could use one-person Zoom sessions to answer specific questions

- Try to get both Kelly and Molly out here to the training session. It may be $500 to $1,000 per super rep. Let them know that they could extend their stay and charge for individual consulting and other outside meetings. Or we split the fees with them for day 4. Day 4 could also be their thing and let them charge what they want. We could cover their plane tickets.

- Shooting for between 20 - 50 participants.

- Try to keep things industry specific between breaks and on day 4 group sessions.

- Run the payment through ecommerce. Setup online seats and live seats (limit the quantity).

- Run the new classes through the news and updates page.

- Come up with some numbers and budgets

- Document management options - After the session, I was answering some questions about custom forms, custom documents, and custom procedures. I was answering by telling about state manifests, transfer docs, state title work, and even the vacation rental and timeshare company that has a one page form in Adilas and it creates and saves multiple contracts and agreements and records them for clients. We also have gun clubs and such that sign waivers and then assign the signed waivers to the correct client record. Good stuff.

- This wasn't part of the session, but other notes on the training event from post-it notes and my mini notebook. Dated 4/27/18... Black box, presenters choice, Q&A, business topics, meet the developers, participant presentations, demos, industry specific, what is possible with _____ (fill in the blank), and interactive & hands on sessions. Other ideas might be direct video feeds, group games & hands on activities, watch a developer work - say a black box take over or something like that, reports from the field, exploring the database, white labels, dedicated servers, timed challenges, speed and shortcuts, custom wire jobs - show & tell.

In early working on the new payroll changes that Shawn submitted. This is dealing with county based withholdings and new state calculations for Indiana.

Steve is seeing the 3rd party solutions page extending into a virtual permissions for those outside solutions to get access to any of the 12 main players. We need to show what is available and allow for what windows and doors are open. This is really common for some of the clients that are dealing with oversight or overseeing certain pieces (virtual auditing and such). We need to keep our clients data safe but also need to allow the different parties to allow or dis-allow between themselves. Maybe the secret is allowing the clients to build their own relationships between the possible different solutions and/or outside parties.

At some point, we may need some kind of history of who is opening and closing the API socket windows and doors. That may help later on if we need to figure out who is changing what.

Eric will be popping in around 10 am to talk about loyalty points and gift cards.

Meeting with Anthony Harrington about loyalty points and gift cards. Eric, Steve, and Brandon were on the meeting with him.

- There are tons of daily discounts. It gets crazy in order to manage all of those things.

- There are a number of steps that need to be done in order (on carts and checkout process). One of the things that they would like us to do is - dumb things down and make it more simplified.

- They would love to have preset discounts, sales, and promotions. Also, a lot of the different discounts are based on a day of the week and/or a specific time.

- Eric has done a number of these custom discount and pricing engines. Eric was saying that some of the discounts are not created equal... bogo (buy one get one) vs auto calculating all similar items and then repricing based off of quantity (just as an example).

- Some discounts and promotions will be standard (hoping to catch 80% or more). There may be others that are just plain custom. Those still needs to stay on that level, meaning we may still need the option for custom code.

- Anthony would love to help push the development forward in such a way that the users (adilas clients) could use the system to tweak the system. If they, our clients, need to call a developer all the time, that gets crazy and very expensive. The solution needs to be out to sales and promotions and virtual campaigns. Eric and I have also talked about allowing discount rules and such.

- Anthony has some price grouping and some needs there. Similar to smart group buttons and tiered pricing structures. He would love the cart to be able to keep track of those pricing tiers and virtual groups. He would like the ability to move and manage pricing structures based on groups (even a subset of part/item categories).

- Lots of needs for time based discounts such as happy hour, certain deals, etc. It would be super cool if we could setup all of these rotating discounts and the cart is able to apply those on the fly and as needed. Basically, we need an automated pricing engine.

- Some of these discount rules may need to be built and held in a coupon, sales, and promotions type system.

- Eric was talking bigger volume shops vs the mom and pop shops. They all want that kind of feature but it comes down to cost. If we could build it into the system, it would benefit all parties.

- Eric would like to see a printed list of what kind of discounts they offer. That would help us in the background make sure we can build out the rules that would be needed.

- Anthony would like to know a cost and timeframe. Eric was talking about phases and options for deployment and development. Then Eric talked about building out the standard features, all-a-cart features, and then also being able to customize things if needed.

- They would really like the pricing tiers to work similar to the smart group buttons without having to tie them into a button. Basically, behind the scenes, they have rules (what to do) and assignments (who can play). That is the same basic model that is still needed, just not tied to a button. This may end up being part of the pricing engine. The cool thing would be rules that could also be tied into time and time-based promotions. The higher level (meaning the top level or group level) of pricing really helps with speed to market and ease of use.

- Steve was saying that sometimes it takes years to get a stable picture of what is really needed. That is a huge key.

- Sharing knowledge and helping others be able to run and go forward. Anthony has some great operational experience... we would really love to tap into that. A huge knowledge base of experience. Another huge asset is perspective and vision. Those are both huge assets.

- There is a huge training need. Some people will use what we have but they may not even know we have it. That comes back to ease of use and education.

- Molly popped in - what comes first, the pricing engine or the coupons and sales?

- There are a few main pieces to help everything play in and work together. We are seeing sales and promotions, pricing engines (cart logic), custom labels, sub inventory, mini conversions, discount rules, tiered pricing models, customer loyalty points, gift cards, coupons, etc. They all play together and have similar pieces that need to be coordinated. We know we need all of these pieces, the trick will be what comes first? And how do we pull things together?

- As a side note... when setting up pricing groups, we may need to pull in parent attributes to help us create good groups and grouping.

- Small complaint on packaging and sub packaging, when they add a new one (sub), they have to re-enter the price (every time). They would love it to be tied to a pricing group. They also want to make sure that we keep them in a good process path. They would love the new subs to pull in the price from the group pricing vs setting it every time. They do want to be able to change it if needed, but they would love it that price auto pulled itself into a preset pricing group. This is a big priority to help make it easy and more standard.

- Mini conversions are really needed here soon. The deeper we go, the more we are needing that ability. What they are calling (our clients) packaging is really mini conversions of sorts. There are a number of clients that are doing internal manufacturing inside their systems. We need to help them out with that. Also, when the customers buy things, they want to be able to search for one item (not 50 million), and then be able to buy and sell those items in different sizes, packages, and conversion pieces. In the frontend, they want it really simple. In the backend, we need to mix and blend and cross-tie things in and maintain the correct relationships. That is really huge.

- The more we help to automate things, the less chances for user error.