Working on year end 1099 stuff. Lots of form building and testing layout and spacing.

Met with Caisson Labs and did some planning. They are doing year end inventory stuff right now. They are in an interesting place. They have an old system that needs some loving and a new system that still needs to be setup. They are going to be counting inventories and getting us new data to put in place in the new system. Steve joined the meeting and will help them learn some of the core production features inside of adilas. That should really help them. Steve was talking to them about location specific items, vendor specific items, and homogenous inventory items. Lots of moving pieces and options.

They are currently using a custom hybrid app from Calvin Chipman and MyEasySoftware. It combines custom software and web based API sockets back to adilas. They love some of the pieces, but there are some challenges. They want to keep using pieces of the custom app and normal core web pieces as well. We are working with them to help get everything moving in a smooth way.

Three of the pieces on the custom app are working really well. They use those pieces every day. They are the Packaging Log, the Label Printing, and the Shipping tabs. See screenshots for a reference.

Steve and I met as part of the morning meeting. I can tell that Steve has a lot on his plate. He is running from fire to fire. Some of that may be year end stuff and pressure and some of it may just be busy times. Danny checked in and said hi. After Steve left, I jumped back on the year end stuff for 1099's and W-2's. I also had a couple of phone calls, emails, tech support stuff, some developers checked in, and other random stuff.

As a side note, Russell sent me this link. It has some great UX and UI quotes. 
https://uxplanet.org/16-quotes-you-need-to-read-as-ux-designer-e47f982e312c

UX and UI mean user experience and user interface - how does your product act and interact with a user?

Meeting between Chuck and Brandon. Steve joined us part way through. We were talking about current tasks and direction.

- Not really learning ColdFusion right now but more on helping to get the snow owl theme to the rest of adilas.

- Pages that Russell and Chuck are working on - classic homepage, payee permission home, add/edit user permissions, mange corp info, corp-wide settings and defaults

- We have purchased the project theme (bootstrap CSS theme). All of those resources are available and online. We were looking at more of the options that come with the preset theme that is already being used.

- The look and feel is so important and really helps to sell the system.

- We may need a way to prompt our users to upgrade to the newer look and feel. This was an idea by Chuck to help us prompt the users to upgrade. If they do upgrade, maybe we could help them by flipping some switches and even changing some of the settings. Make it easy to switch.

- Tying in the new classic homepage design to a user setting. We may need a toggle to switch between the new and old style and also some image controls. Chuck was saying maybe even a picture of the day. We also talked about picture categories and maybe letting them choose.

- Looking at different online resources - get those from Chuck - He had a number of sites that offer free and awesome images and pictures.

- We talked about different levels of control. Do we allow it at a per corp level, then a per user level? Etc. If we bring something forward, we will quickly get requests for more control and more options.

- We are thinking of trying it on a few of our other homepages. We have like 5-10 homepage that this could work on. Talking about a fun changing background image.

- Flipping over to the campground project, we talked about sub dividing it into small pieces and who is going to do what. We may kick some of it over to Marisa to let us know what is the most needed pieces. Trying to shorten the development cycle and get it out to be used quicker.

- For our next meeting - lets get 5 categories of photos (space, mountains, general scenery, ocean, animals), 10 photos per category, figure out the main icons, vertical tabs in the bootstrap theme.

See attached for some screenshots. Some of the screenshots are dealing with possible mock-ups and internal pages and options.

Talking with Calvin and Jacob from the IT Dream Team. Steve joined us part way through the meeting.

- What is the dream?

- Who has access to Calvin and what would that look like and/or cost? Currently, Calvin may be approached by clients, reps, consultants, adilas tech support, and other adilas developers. This may need to be defined more.

- Problem and incident management. Also, change management and future development. We may need to look at some standards such as ITIL (information technology infrastructure library). Great starting point for setting up best practices.

- Communication breakdowns and having too many middle men - adds to loss of communication.

- Helping all of our clients take advantage of new changes.

- Building processes to help standardize things.

- Products that are on our future tick list - text messaging (big and small, group and individual), auto processing (transactional data to aggregated data), label building, and other API socket tools.

- IT Dream Team would like to help us get a strategy of where we are going. Basically an IT partner or part of team on an ongoing basis. An outsource CTO (chief technical officer) type role

- Vertical design and keeping the user involved

- Challenges of just in time project management, just in time funding, just in time bug fixes, just in time development, etc.

- What trends are we seeing and needing? Along those lines, where are we headed and what else if needed? Even to the fact of reoccurring services (IT, servers, developers, management, software, consulting).

- There tends to be a few type of programming - maintenance, bug fixes, and enhancements (new things that need to happen). There is also operational vs emergency needs. If we can be proactive, we could eliminate lots of the emergency type levels. Making a plan and then working that plan.

- We have an independent model... which also allows us to have work (jobs) for you guys as well. There could be a lot of back and forth sharing between clients, projects, and needs.

- Steve was talking about how our end goal, for our model, is helping to bring together operations and accounting (the zipper analogy). Steve was also talking about helping the users really want our product to the point that they need it. The system becomes one of their favorite and most used tools.

- There are tons of other sales type options - we can dream it up and then put together a plan. We would love to play together in different ways. Let's figure it out.

- Knowledge management - key players that have the correct knowledge pieces of the puzzle.

- There was lots of talks about oversight, helping, managing, and even finding the correct solutions on the accounting side of things.

- There were talks about setting up a marketplace that service the adilas clients and markets. It come back to our planning for the adilas café type model. Here is a link to some of our research on the adilas café.

- We were talking about outsourcing some of the babysitting pieces to different CPA firms. Lots of options and vision - huge potential.

- How do we move this thing out to the next level? Let's get some proposals going.

- We have two main things that we could look at. One deals with the development side of things (building and maintaining things) as well as a possible relationship in the revenue sharing and bigger picture.

there were two of these so I chose the other id for allocating hours

Charles, please add your ideas and concepts here :)

We are using https://ajax.googleapis.com for some code, here is a warning I get for this.

1859.02

top_secret/secure/payee_permission_home.cfm?sec=51

/top_secret/secure/setup_new_employee.cfm

top_secret/secure/corp_administrator_home.cfm

When creating a new deposit and selecting the line items, the checkbox and JavaScript functionality that totals the deposit line items is broken.

On going updates to Security on the VPS environment 

On going Server Monitoring and Updating

4/2/20: Did a proposal- never heard back.

2/25/20: Received flow chart from client. Set meeting to review chart for comprehension on 2/27/20.

2/11/20: Moving forward...Physical vs digital inventory discrepancy in adilas. Goal is to create a scanning mechanism to scan a barcode and track inventory from sales rep to partners.

1/21/20: Client is thinking about it and will get back to us

From 710:

1) Sales rep creates transition invoice with items to hold product so no one else can sell. Get order from dispensary. Confirm order. Will click on email but instead of sending to dispensary send to the team (logistics, inventory and fulfillment.) They email the Logistics team once that invoice has been confirmed.

*Activate setting that currently exists to add QR code to the bottom of the invoice.

* It might help to assign SKUs cold or warm in inventory.

2) Inventory pulls the order and hands it off to Fulfilment. 

*Would be amazing to have a way to scan check out SKUs from inventory to fulfilment, but this isn’t needed for this exercise. Just an idea we like.

3) Fulfilment prints out the invoice to box up the order to get it ready for delivery. 100 items but only two delivery boxes. Fulfilment puts the items in either warm boxes or cold boxes. (freezer vs fridge)

Details: There could be 1 sku in 3 different boxes or 3 skus in 1 box. There can be multiple cold or warm boxes. Depends on the size of the order and the amount of cold vs. warm products on the invoice.

For example, we’ll label an order that takes 5 Boxes (3 warm, 2 cold): 1/5W, 2/5W, 3/5W, 4/5C, 5/5C. Or a two box order (1 warm, 1 cold), 1/2W, 2/2C.

4) Fulfillment scans the QR code on the invoice to pull it up. Now the cold box(es) and warm box(es) each need their own barcode assigned to the master invoice.  Need to know 1 of 5 cold boxes (how many of each kind). 

For Example, on Invoice 4125 (QR Code 1) that has 5 Boxes (3 warm, 2 cold)::

• 4125.1.5W (QR Code 1A)
• 4125.2.5W (QR Code 1B)
• 4125.3.5W (QR Code 1C)
• 4125.4.5C (QR Code 1D)
• 4125.5.5C (QR Code 1E)

5)  Once the barcodes are assigned to the boxes, each time they are scanned it will check them in or out of their next destination.

*It’s crucial that each time they’re checked in or out it only works if all boxes on the invoice are scanned. So it needs to notify whoever is moving the boxes that this invoice is missing a box.  

a) Check-in to invoice

b) Check out of facility ** There would sometimes be a variable where the boxes would skip from stage b to stage e so there would need to be a way to enter or set the course or itinerary for the boxes in step 4.

c) Check in to layover (for the socal orders)May sit for a couple of days here

d) Check out of layover

e) Check in to sales location ***This check in would be the final stage and it would convert transition invoice to customer invoice

Phases that things go through along with communication that goes along with that. Check boxes- where is this advancing along its way. Only way to pull from inventory is using the transitional invoice. 

Sales rep- processor-fulfillment- are all phases. 

Many different products, always changing. Small batch with lots of variety. 

Some accounts are getting 2 orders a week. Some less active. Send out a menu twice a week.

Another phase at some time: Items shouldn't be active until they are ready to ship

Are 10 packs ever broken up- NO.

Might be individual products and samples available as needed.

How could they use internal builds to package up to the next level. 

Add invoice grouping as a possible solution

Is there a way to print out two QR codes associated with invoice. Tells us what is in the boxes and also track the movement of the boxes- check in check out?

There is some labeling where certain phases need to generate a label. Almost a sub phase. 

Use flex grid to tie to an element of time to the invoice. 

Flow chart: Zack will create one. 

As of 6/20/20: AW has invoiced 13,319.75. Doesn't include SRB or BWM time.

4/16/2020: Update from Alan- page originally create was too heavy and slow- too many metrc users. Had to return to square 1 and lighten the load. There was only one table per server= too slow!
New plan: not as much data. Different statuses/stages: not sent, sent, errro=update and auto resubmit in the pm, we think it worked but no confirmation id, final-id=synced.
All tables are built to switch between status/states.

Alan said 10-15 hours: All that is left on this project is showing on the page what state/status the invoice is in, and auto resyncing the ones that need it. Also need to make sure the "E" exclude is in place so that only customer invoices with tags show on the page. 

Alan will do a generic page and pass off to Brandon.

As of 3/2/20: Should be pushed live this week

Updates to the dispensary homepage and how the sync happens with respect to the Metrc ID

Emails and other to list stuff.

Talking with Russell over the phone. We had a great conversation.

- Concept for fracture - Being able to remove any of the extra pieces. This goes clear down to the permission level. If they, our customers, only want invoicing and time management. That's all that they see. Even on the permission side of things. They only see what they have turned on. That may require us to stack and group the permissions better. It goes clear down to the ice berg vs the mountain model. We have to be able to remove all of the pieces otherwise the user still sees the mountain even though we are trying to just show an ice berg.

- The other really important thing for fracture is smaller getters and setters. This allows us to add/edit things in a very modular manner. If you want to change something, you can just change it. If you want to add something, you can just do it. This could help out with API sockets, quick calls, and even web components. Back to the old adage, build it once and use it many.

- We lose so much in our transition times - switching between projects. It is very costly both physically and mentally. It is real.

- Working models - if you look really close, we have a number of great working models and proof of concept stuff. There is some real value there. Keep building on that keep working to bring all of those working models and proof of concept pieces more into fruition.

- Empower the users - you can make it happen - we can help you build your dreams. A big part of what we peddle (sell) is potential and hope.

- We spent some time talking about the concept of elements of time. We have build in so many pieces that it becomes a virtual mountain. Russell was talking about a Leatherman (multi tool) vs a simple knife, a simple screwdriver, etc. We really want to help the users. Sometimes they want the big multi tool and sometime they just like the simple knife. We may need both.

- Because of the load, we are able to gain some traction.

- Talking about database pieces and options. There are multiple different models. You have file share databases, server databases, relational databases, document databases (objects and JSON storage), transactional data, aggregated data, object data, etc. You gain if you can mix and blend and get best of the different worlds - connections, storing, searching/filtering, and reporting.

- Helping other people to succeed. That is a huge piece of the puzzle.

- Creating the ecosystem that feeds the people who provide the byproduct services that are needed and wanted.

- Futuristically speaking - There may be some new business needs. This could be adding new departments underneath of adilas or it could be completely new companies (mother/daughter type companies). Thinking of things within the concept of the adilas café - we know that we will eventually need a company for the adilas market, adilas university, core adilas, tons of other options for the other products and services that are needed.

- As we get more into project management, some of our project managers may need some stacking underneath them. For example, Steve may have some projects that he pushed off to some other project manager(s) underneath himself to manage some of those projects. Organizational stacking (who reports to who and how is that organized).

Working on year end 1099 and W-2 forms.

Talking with Steve about different meetings we had over the weekend. We talked about direction and what Russell wants to do and possible options there. Good stuff.

Towards the end of the session, Wayne jumped in and worked with us on some server stuff. We were talking about server hardening (making them harder to hack and/or take down), testing, HTML frames (possible ways people hack sites by displaying web pages within other web pages), and running things on http and https protocols (SSL - secure socket layer stuff).

Back working on some end of the year forms and layouts.

Working on year end 1099's.

2/3/20: Danny emailed with Pete and is waiting to hear back from Pete.

Gun store wants to simplify serialized sales process. Steve sees this as settings and wants to line Danny out once reviewed with Brandon.

Brandon drew out how steps now include 1-10 but could be limited (with checked boxes or unchecked) so fewer steps were needed.

See doc folder for png files that show what he wants.

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.

Currently you need to log in to metrc and click "Create Test Sample" and then go back to adilas and do the same.It would be helpful to be able to click on a button after the harvest process that "Create Metrc Test Sample" or something. Then it would do it as well in metrc. 

Colorado changed Medical Marijuana Gram Control rules. Steve has been working on updating and building out this in depth gram control and is close to finishing as of 1/6/20.

Talking about new projects and who is doing what. We also talked about watching our costs and being able to get these new projects started. How much of the project is required before we get started? Sometime that is hard to know or fully qualify.

We were talking about a number of different projects. Delayed inventory counting, inventory engine, thresholds, location specific maxes and mins, reordering logic and options, and settings for sales (selling stock/units and bigger ticket items). We talked about some settings for the sales process and then allowing those steps and/or processes to be shown/hidden and even configured. As an example, say they didn't want to do any trade-ins and didn't want any warranties - or something like that. Turn the process into a set of configurable settings.

There was also some talks about how we could figure out how we can help our customers build out their own custom code base. Lots of talks about controlled testing environments, outside developers, project management, and other services (including head hunting and getting people in place). These services are for the other clients, because of that, they really need to help us fund the pieces to get those pieces going and in place.

There may be other opportunities to offer some of our services to outside parties. That could be custom code, project management, consulting, leg work, etc. We may even end up offering some of the core adilas players as options to help others. That could be a cool angle as well.

Bryan often operates based on who is knocking at his door (squeaky wheel). Steve and I were chatting with him for a bit. We were talking about subbing out some of the core adilas developers to help some of our clients with custom code and project management. We worked through some tweaks for a company and then pushed up the files.

Eric joined the GoToMeeting and had a question about some code. We worked through it and got him back going.

After that, I did emails and got back on to year end forms like 1099's and W-2's. I got the 1099's done and pushed them up to all servers.

Working on a custom data import for a client. Combing over data from a couple of spreadsheets.

Steve and I were on the meeting together. We went over the data import and talked about some next steps and how to keep the client involved in the process. Some great ideas. We then worked on some of his custom code and trying to figure out what happens where and what else is needed. Pretty deep looping and checking on a gram tracker. It deals with settings, carts, items, sub inventory, sub inventory attributes, multipliers, etc. Deep water.

Alan, Josh, and I were on the team training meeting. We had quite a few ask for the video recording to watch it later. We spent the whole session dealing with backend databases and some technical stuff about database storage, indexing, primary keys, foreign keys, and other database engine topics.

After the training session, Alan and I chatted for a bit about where we are going with the training and also where we are going with some of the upcoming projects. Alan would like to see some of our team get specialized assignments and he would like to help manage the team better (project management). We briefly looked at the camp adilas project and how we can take that to the next steps or next phases of development. Awesome new project that could use some of the new techniques that we are learning about.

Working on a data import for a client.

Had Alan on the meeting with Chuck and I today. We wanted to get him in on the projects and getting a high level awareness of what is going on. We started out with the camp adilas project and where that is in the development cycle. Chuck did a demo for Alan and they went back and forth with ideas and questions. Both guys are excited to work together on the different projects.

After that, we rolled into a session talking about some snow owl theme (current look and feel inside the system) changes and where that could go. We looked at some mock-ups for the classic homepage and then then into user permissions and profiles. See the screenshots for some of the new ideas. Still in concept mode but definitely coming. We are thinking of putting a facelift on a number of the high usage pages or places where it looks older or more outdated. We are trying to change up the user experience and make it better and better.

We talked about user profiles, permissions, and allowing templates and presets. We talked about having tabs, vertical tabs, accordion displays (ways to show/hide additional data), floating submit buttons, putting help files and summaries under the gear icon on the side of the page, stash and go with a sock drawer type concept, and even changing the page flow to help the users. Currently, they do an action and may end up on a different page or on a success message. They then have to navigate away to another place or do some other action. Good page flow will really help.

A couple of other topics were mixing tasks and skills to get a job/project done vs a full stack developer (able to go from top to bottom or point a to point z - the whole thing). We may need to help some of our developers get really good at certain tasks to help with efficiency and productivity. We also talked about light messages and helping to lightly push our users towards the newer look and feel and/or new functionality options. We know that we have to be careful there, but we will make some attempts when ready.

After the meeting, Alan and I talked briefly about some of our developers and where we are headed and who could help in what regard.

New note added on 1/8/20 - Danny Shuford contacted me and asked that we make the view only permissions easier to get to. I showed him some of the concepts of where we are going with user profiles and permissions and said that I would add a note to this element of time. The original idea came from Kelly Whyman and Danny brought it to us. Great idea. That may require some special code just because the view only permissions are not standalone permissions. They require the main permission and then the view only permission to limit the options.

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

Finishing up tax v-5 project

Alan and I touched base on the tax v-5 project. I was busy with some other things, so he worked on it. I recorded a bunch of notes, emails, and back on data import stuff.

- 4 things that they offer - technical support, strategy (all kinds), architectural design (all kinds of managed services),  and outsourced CTO (chief technical officer)

- They are good at programming, collaboration, networking, VOIP (voice over IP), integration platforms, and other technical things.

- Steve asked about costs for coding, fixes, and future development. Jacob was talking about strategy vs an hourly rate. Trying to turn it more towards the results of what is accomplished vs a straight hourly fee. They would like to help solve the problems and look toward the future as possible white labels.

- Adilas is on the edge of a growth spurt - we need some help keeping things going - help dealing with growing pains.

- Offer from the IT Dream Team - help us out with our current needs (coding, bug fixes, and even new development), they would like to commit a day a week to helping us out. Say 5-10 hours (it may flex). They would like to be at $300/hour or $6,500/month. There are also some options that we could explore dealing with revenue sharing.

- We want someone to virtually come in and help with certain parts of the process.

- We just want to be the software piece that deal with hosting, processing, data storage, etc. All of the other pieces are up in the air. There are huge needs in setup, training, onboarding, consulting, custom code, support, etc.

- They, ITDT, are already tied in with a few partner setup type scenarios. We are looking for people who want to be a white label supplier for or of our product.

- Our, adilas's, biggest needs are on the development side and also on building out the bigger picture and/or dream.

- Steve was proposing that the sweet spot is outside the system marketing the virtual byproducts on or around the other services that could play into things.

- We fit into the gap between the do it yourselfers and the really big players like SAP and Oracle.

- We allow custom code and we don't cost a fraction of the big dogs. Our biggest competition is tradition. We do compete with other companies but most of the other companies sell pieces, modules, or components. We sell a full system.

- We offer shared servers, semi-dedicated servers, private servers, clusters, etc. From small mom and pops to bigger enterprises. Lots of variables.

- Talking about the value of our time - stepping up to the bar and paying for that value of time, effort, and direction.

- There needs to be a shift in the direction that adilas is going so that we could get the value out of what we are all doing. We are somewhat in a tricky spot... we either need to keep growing naturally or we need to go bigger. The middle ground is a dangerous spot to be.

- We are really trying to get white label companies to run with the potential of running and supporting an industry or business vertical.

- Steve would like to get another pitch from Calvin on what would be possible.

- If we do need to go in different directions, what about the existing pieces? Is there a way to get that code or do we setup an agreement to keep things going on a reoccurring model?

Steve and I got on the phone and chatted for 45 minutes after the meeting with Calvin and Jacob from the IT Dream Team. We were talking about business decisions and what path and/or direction we want and need to take. Good conversation. There are lots of options out there. Our plan it to keep going and try to keep things small, tight, and growing naturally. We have some good direction and some great people who are helping us and playing the game. We are going to keep following that path.

The conversation was fun and we jumped from subject to subject. Those are always fun conversations. Steve is super hard worker and we are surrounded by lots of great people. The sky is the limit.

Working on the data import for a client. Combing and filtering data on an Excel spreadsheet.

Emails and paying bills.

On the morning meeting. Pretty quite. Answering emails, paying bills, and texting back and forth with developers. Danny popped in for a bit and had a couple small questions. They were dealing with the new view only permissions (six new permissions) and making it easier to click those options. I recorded some notes on the time id # 5463.

- This is another idea dealing with permissions. We may need to flag and tag the permissions so that we could show them differently. Currently, they are setup based off of the layout of the classic homepage (system search, system basics, system assets, system liabilities, system time and requests, system reports, system maintenance, and system management). It may be really nice if we could put flags on certain permissions such as invoices, POS (point of sale), deposits, customers, view only, etc. Tag and flag them so that we could pull related permissions into smaller groups to help with grouping and clustering of the permissions.

- Along those same lines... we need to add flags and tags on navigation options, permissions, and settings. That will help us organize and sub organize the permissions, settings, and navigation options. For example: All settings that deal with invoices, all permissions that deal with invoices, all navigation options that deal with invoices. Get them all grouped together, using flags and tags. We could then allow for those values to be searched through the quick search. See the concept art work from Jonathan Wells dealing with the new adilas navigation system. This same concept may be extended to pages, help files, videos, tutorials, etc. Basically flag and tag everything so that a single word search will bring up all possible options (mini search engine within the system). See attached for small concept idea on adding specific flags and tags to the items (permissions, settings, help files, nav, etc.).

- Brief talk about application modes and how that works. This deals with how the system is broken down into the 12 main players or 12 main application players (think of the core layout). The modes work in a similar way. By default, the mode is the "data mode" or information mode. That means what is stored or organized per main player group. For example: All invoice information or data can be found under the invoice button or invoice category. In the data mode, you can get to the data for that main player group.

- If you switch the mode to say: "permissions mode", you would get all of the permissions that are related to that main player group. For our example: Say the invoice button or invoice category. You would get all of the invoice permission. You could do the same thing for settings and other main topics. Basically, you choose the mode and then select the player group. You then only get stuff that is related to that player group.

- The main application modes are: data mode, permissions mode, training mode, settings mode, usage and stats mode, tech/concept mode

- The 12 main application players (main player groups) are: customers, invoices, quotes, items, stock/units, elements of time, employee/users, vendors, PO's, expense/receipts, deposits, and balance sheet items. A couple other main  groups are things like banks, flex grid tie-ins, locations, corporations, media/content, and the list goes on. The primary 12 are listed first.

- The magic comes where you are able to click on a mode (data, permissions, settings, training, etc.) and then select one of the main player groups (invoices, customers, items, vendors, etc.). You are then able to see what plays into that section or group. Mixing the application modes and the player groups, allows for all kinds of combos.

- The concepts above are built from picking the mode first and then the application player group (example: data mode >> lets work with invoices). What if you were able to go the other way (example: work with invoices >> show me the permissions or show me the settings). It may be cool to go back and forth between the ways of interacting with the underlying pieces. As a side note, we do the same thing in a shopping cart (how we create quotes and invoices inside the system). It does matter if you start with the items or you start with the customer, as long as you get both pieces before you checkout, you are golden. Non-linear and information and relationships flow in multiple directions.

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

- Talking about the camp adilas project

-- 1 person doing Ajax calls (Josh) - hardcoded data is passed back and forth - no real connections to the backend (kinda middle ground), 2-3 people doing the backend wire-ups (Brandon, Eric, Dustin) - deeper or core developers - maybe one to do database connections and the other doing the service layer (wiring), plus the designer (Chuck).

-- We will make a basic concept page that has some different parts and pieces. We will then assign that concept page out to the different developers. The concept page is just so that we can get some ideas and virtual mini library assets.

-- On the concept page, we want to get a full sign-off on that page before we let the other guys advance. That is checkpoint of sorts. The concept page will be somewhat of a group type project just to make sure that everybody knows what is going on. Walk through it with them, then let them drive, give feedback as needed.

-- Set a standard for the new stuff.

-- On the Ajax calls - we are thinking about pulling back actual HTML vs just data - that way we could just replace certain pieces without having to worry about mixing HTML with data.

-- Brandon and Alan will work together on the project management side of things.

-- Have meetings with each role to get them pointed in the right direction.

-- We want to write out test cases as well.

-- We will be creating a new folder for the new camp adilas project stuff. This includes js, css, html, ajax, and code.

-- We will work with Wayne to help with domain pointers and internal mapping.

Weekly meeting with Brandon

Eric joined the meeting and had a few questions. He is working on a custom project for a 3rd party solution that deals with custom loyalty points. We talked about some options and how to handle some of the custom code, API socket calls, payments options, and how to clean things up for the next shopping cart. I just helped by being a sounding board, pointing him to some existing code and options, and talking through some logic. Good stuff.

Update these permissions so the functionality is core adilas.

156.	Paid Custom Interface - Bubble Interface Home:			This permission allows for the bubble custom interface to be turned on. This is a paid interface. The cost is $50/interface to turn it on. If custom code and/or tweaks are needed, those changes will be billed out at $35/hour by the designer/developer. The original designer of this interface was Russell Moore. 435-760-1389 (cell)	Id=143
157.	Paid Custom Interface - Structured Circle Home:			This permission allows for the structured circle custom interface to be turned on. This is a paid interface. The cost is $50/interface to turn it on. If custom code and/or tweaks are needed, those changes will be billed out at $35/hour by the designer/developer. The original designer of this interface was Russell Moore. 435-760-1389 (cell)	Id=144
158.	Paid - Adilas For Business - eCommerce Package:			Paid access to the Adilas for Business ecommerce packages. This permission is a required for the special AFB templates to run correctly. Only one assigned permission per corporation is needed. Contact Russell Moore. 435-760-1389 (cell) or visit www.adilasforbusiness.com for more details and info.	Id=158
159.	Paid - Adilas For Business - Employee Time Clock:			Paid access to the Adilas for Business quick employee time clock application. This permission is required for the special AFB apps to run correctly. Only one assigned permission per corporation is needed. Contact Russell Moore. 435-760-1389 (cell) or visit www.adilasforbusiness.com for more details and info.	Id=161

Josh and I met up and pushed up some new code for the driver license scans and being able to populate data into the add/edit customer records. After that, I did some email stuff and got back with Calvin and Jacob from the IT Dream Team. We are trying to setup a consistent monthly effort to keep pushing things forward. That's exciting.

Alan and I touch base on the tax v-5 project but ended up working on other projects. I helped Eric out with a couple of questions. After that I spent the rest of the time working on new tax year 2019 W-2's and getting them ready for the system.

Finishing up tax v-5 project

Bryan and I pushed up some new code and some custom reports. We then spent the rest of the session talking about ways to virtually extend the functionality for clients. We went over some of the existing pieces such as black box code, flex grid tie-ins, parent attributes, sub attributes, web page settings (JSON or object storage), and then we settled on real in-line database extensions.

We did a lot of drawing and talked about how we could virtually extend any table without hurting any other corporation (super light and non intrusive). This concept allows us to virtually use the custom tables (custom_numeric, custom_text, custom_dates, custom_json) and create new add-on columns for almost any database table. I showed Bryan how easy it was and we even when through some mock-ups (text and drawings based on scenarios). The nice things about these custom tables is that the data could be a specific data type (a real number, a real date, a real string/characters, or a JSON object). Plus the tables are much smaller than normal flex grid tie-in records.

Here is some older research on custom extensions, real in-line database extensions, and custom columns on a per table basis. Aka - the big brother of the flex grid tie-ins.
https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?sort=asc&q=in%2Dline%20database%2Bdatabase%20extension

Finished up the year end stuff for 2019 W-2's. Pushed files up and did some testing.

Working with Steve on his custom projects. One of the main ones we were working on was his complex gram control logic for different states. Lots of logic, loops, conditions, etc. We also worked on a new report that showed all payee/users and their permissions. A client needed this report to show their investors and board of directors. Kinda random. 

Training meeting with Wayne. We had Wayne, Alan, Josh, and Brandon on the meeting.

- We talked about testing concepts. Lots of injecting and mocking things up. Simulator type stuff.

- Discussions on caching, session stuff, web components, efficiencies, and custom tags.

See attached for the video recording.

A few more items that need to be prioritized/quoted for clients.

Cory and I spent some time looking over custom projects and making plans. We decided, if it (the project) is big, we'll need to give the person a quote for the quote. Sometimes it just takes time and we have to cover that. Some projects are really quick and we can just suck that cost up internally. Other projects, it takes hours just to plan it out. Basically, if the project is big, we may need to give them a quote for making a quote, just to be fair and to do the real quote justice.

We did some training on elements of time and how that tool allows for data to be tracked over time. We got into light training about data assembly lines and how to set that kind of stuff up and use the existing tools.

We also did some training on doing corp roll ups (aggregated systems or enterprise systems). We looked at ideas for multiple corporations, a controller entity, and how to move financial data between those corporations. All of it is manual entry right now, but totally possible. Eventually, the goal would be to automate the whole thing and make it super easy and real time.

The other topic that we talked about and did some training was stacked accounts receivable. This is when more than one party is attached to an invoice. Say for example, a controller corporation (mother corp) has a number of daughter corporations. The daughter corporations extend credit to one another but the main mother or controller corporation needs to pay the actual bill. We talked about one-to-many relationships between invoices, customers, and even sub or secondary customers. All of these pieces already exist, we just needed to do some training to show Cory how it all works. Super fun meeting with a mix of planning and training. Good stuff.

Chuck, Alan, and Brandon were on the meeting.

- Brief overview of projects.

- We reviewed the camp adils project with Alan and made some small plans. Alan is going to help project manage that wire-up job (the main project).

- We also went over a number of mock-ups for the user permissions page and helping the older classic version get updated into the snow owl look and feel. See attached screenshots for details.

Alan and I spent some time talking about treating some of our projects differently. We have spent a lot of time working and helping some of our guys become full stack developers. Full stack means you can go from start to finish and do everything in between (plan it, code it, test it, deploy it, etc. - full stack). As we move forward, we may end up helping some of our developers specialize a little bit more. That will help us speed up the training and get them productive in a quicker manner. It may also allow us to better spend our one-on-one time with those developers as they need help and guidance. That's our plan for right now.

Finishing up tax v-5 project

Steve, Danny, and Dustin were on the morning meeting. I joined later on due to a dentist appointment. Steve was helping the guys with their different projects.

Calvin and I got on a phone call together. We are sending Calvin off to work on the adilas label builder and the hosted or web version of that product. The current product is a hybrid product and has a Windows software portion as well as a web version and/or portion. The new adilas label builder will be completely web-based. Calvin and I also touched base on a few things and talked about direction and vision. I approved him sending in some hours for emergency tech support that hadn't been submitted. For a while, we were somewhat between some talks and negations on how to handle billing and support requests. Calvin is working hard with a partner to create a new company called the IT Dream Team. Most of his time has been spent there. We are excited to get some dedicated time to finish up and work on some of the adilas projects. Good stuff.

Eric and I jumped on a GoToMeeting session. We chatted about some questions and then did some prep work on how some of the math and accounting is going to work for loyalty points and point redemption stuff. Most of the session was back and forth and a little bit of going through scenarios and light training. The other part to our conversation was dealing with how to track that same stuff (loyalty points) but through 3rd party vendors and outside sources. Interesting.

All updates to standard labels

Steve, Eric, and I joined the meeting and went over some scenarios and talked about some deep financial flow questions about bad debt, customer loyalty points, gift cards, etc. I jumped out at 1:30 to meet with a business consultant. Steve and Eric kept talking about deep financial flow and options for another hour plus.

Jonathan from Epic Enterprises came over to my house to meet with us. We started out listening to Steve and Eric over the GoToMeeting session. After a little bit, I started to explain some things to Jonathan. We went on mute but had the meeting with Steve and Eric going on in the background. Every once in awhile we would catch something and it would send us off on a tangent and/or direction change. We were waiting for Steve to join us.

Once Steve joined us, we had a good multi-hour meeting with Jonathan, Steve, and myself. Here are some of my notes.

- We talked about analogies between showing a whole mountain vs just an ice berg (how much do you show and/or reveal - it deals with perceptions of how much there is and how much needs to be learned).

-  We talked briefly about the need for the adilas café and a good starting place for our users to come in and be a part of the community. Some of the people come to work, play, learn, buy or sell their own product and services, and participate in the adilas community. We went over some concepts, graphics, and needs in that area.

- I pitched to Jonathan that we have at least 3 businesses that need to be funded, staffed, and managed. We have the main adilas system, the adilas marketplace (others who are buying and selling their services and products to help support the system), and adilas university (education and training).

- We talked about some progress from one server and being able to share logins (one login allowed access to multiple corporations, based off of permissions and assignments). We also talked about how that model still exists but gets tougher as we keep adding other independent servers. Currently, we can share logins on a per server basis. We can't do a single login and allow that user to access multiple servers. The logins are specific to each server right now. As a side note, not everybody needs to be bridged between servers, but certain users work in tons of different systems and on multiple different servers.

- Jonathan recommended a movie called "The Pentagon Wars" - dealing with scope creep. Basically a project that should have been fairly simple turns into 17 years of development and $14 billion to create it. A comical stab at the mismanagement of government spending and scope creep.

- We as humans, are designed to push too far. We tend to go to extremes.

- Making the system more human like... anthropomorphism

- People tend to be either: stable/reliable (45%), warrior/artisans (27%), idealist/humanist (14%), analytical (10%), other (4%) - all rough figures or ish

- Business is a projection of/from psychology.

- Going from order to chaos, order to chaos, and so forth - cycle that has been repeated over and over again in all ages.

- Suggestion - On the invoice homepage and the graphs... maybe add a projection line on the invoice homepage graphs. Show a forecast and/or projection. This could also be done with an average based on number of days. This came up due to the fact that the existing graphs take month over month data and create a graph. Well, if you have just started a new month... you only have a small number of days worth of data vs a whole month worth of data. Sometimes it makes the graph look like it is trending down sharply when in reality, things are actually doing pretty good. Visual helper.

- Talking with Steve and Jonathan - light intro and talking about their respective backgrounds and interests.

- Jonathan wants to help us improve our company.

- Consultants tend to do one of the following actions:  diagnose, analyze, and/or provide feedback. - Sometimes in that order or 3 step process.

- SaaS (software as a service) is a crazy business model.

- Question (dealing with approach) - How do you sneak up on the elephant? Talks about approaches and why's.

- A consultant informs and convinces. A consultant sees from the outside.

- A few things that Jonathan sees right now, without getting super deep: overdiversification, scope creep, scope seep, lack of structure, possible lack of leadership.

- We don't really like to babysit.

- We are trying to work on our to do list or our tick list.

- People have different skills - putting the people in the right place.

- From Steve, sometimes the environment changes how we act and interact with it - it is not just personalities and traits.

- We haven't spent much on selling and marketing.

- We would like to focus on the adilas café approach.

- From Jonathan, book recommendations - "Good To Great", "Rocket Fuel", and "The Go-Giver"

- Building a company is different than running a company.

- By helping our people better focus, that could help us be more productive.

- Steve would like to involve as many good people as possible - He is ok with not knowing everything.

- Steve wants to keep an independent model and/or have multiple cofounders.

- At some point, you will hit the borders of certain things unless you comply with certain principles.

- So many moving pieces - that makes it tough to both see and figure out the roll out and the plan.

- We may need a plan for who will run the business - we like to create it (dreamers and doers).

- Where does one start? Jonathan wants to start with the minds of the owners.

- We just build things... we don't even stop to try to sell them. We love the building process.

- Steve seems to be the creative type and the organizer type.

- Mixing and blending the persons and personalities - we need all of the players.

- We are trying to create a community.

- Analogy of the bee hive... well, if we have a hive, we may need a queen bee, a tree, and some flowers - we need all of the pieces.

- Steve loves to recruit talent and skills.

- Business philosophy and playing the game.

- Jonathan sees, as far as what we offer: stacked valuable services upon other valuable services.

/////////////////// challenges for Steve and I

1. Use more of Jonathan's time
2. Take a personality test from 16 personalities - Try it in different moods, happy, sad, tired, stressed, etc.
3. Trying to align to business principles
4. Steve and I, discuss some of our known disfunctions - see other notes - search for the key word rejecting

Bryan joined the GoToMeeting but our other meeting ran over. We rescheduled this code push for Tuesday.

Steve, Russell, and I met to talk about some business options. Russell has been working on some prototype code that he wanted to pitch to Steve and I. The new code is really cool, but not all the way finished. We talked about a number of the concepts and they will be great additions and could be the base for some of the fracture stuff that we are planning. Here are some of my notes.

- Russell really wants to take what we have and restructure it into a more cohesive core. We build and build and stack and stack. Some of what Russell wants to do is take all of that, and re-make it in such a way that it becomes more mobile and modular. Same type functions, just change the backend core pieces to work better in the future. See attached for a small diagram (drawing) to help illustrate the concept.

- Russell really wants to fix and patch the current ship as well as start building a new and faster ship on the side. Enlarge our fleet, in a way.

- We build and break, build and break. That's how we keep learning and growing.

- We want the adilas core to be 80% of what people need and use all the time. The other percentage will be industry specific code and custom code per corporation and/or business.

- At some point, we bump up against a few tougher obstacles such as volume (quantity of records or quantity of choices) and up against evolving tech. Those two things seem to be a common thread.

- Lots of talk about using web components. This is where we make a small mini widget and then use it over and over again. The little widget holds the code and the logic, we just pass data to it and it knows what to do. Some places where we want to do web components or something like that are: Movable pieces to set up your own flow or virtual data assembly line (think of the cards on a Trello board). Media/content libraries - be able to upload items and then use for multiple places vs just uploading the same thing over and over. We also want to add drag-n-drop functionality and our own version of the data tables. Russell has more info and ideas. There are things that will end up playing in the fracture interface.

- We talked about the value of being in the know and having experience to go along with that. Huge key.

- One-to-many and using shared libraries and media/content galleries and libraries. We already have some of that (media/content remote references) but we want to make it more visual and spread it out more across the system.

- Building and using some tech and pieces from other companies like WordPress and Trello (cards, boards, and that type of interface). WordPress is a pretty deep CMS (content management system). Lots of good ideas. We'll end up with our own flavor of sorts.

- We want to keep making the tool better, prettier, faster, and more powerful. In Russell's words - Easy, Pretty, Powerful.

- As a side note, I wanted to record a saying that Russell said back in 2016. "Adilas is a great companion software package for any business." (4/13/16)

Steve and Danny were on the meeting this morning. After they figured out their stuff, Steve had a couple of requests for me. He and I are planning to meet up with Wayne Andersen when he comes to visit family here in the states. Wayne currently lives in Portugal, over by Spain. We have met with him tons of times but never officially met, in person.

Wayne ended up joining the meeting and reported on some VPS's (virtual private servers) and where things are at with that. We have a client that wants his own VPS to run his own data analyst against. Wayne is setting those pieces in place. Basically, we have to have a private environment, access to archived data (non live data), and then any other access to the server as needed.

Wayne also reported on a server to server migration project that we have him working on. 

Alan lead the team training today. We did a light review and then jumped into more database logic and topics. We spent quite a bit of time discussing database data types and basic select queries. We had Brandon, Alan, Danny, Josh, and Wayne on the meeting.

See attached for the chat log as well as the video recording.

Recording notes from other projects and other meetings.

Met with Eric to go over the spring big loyalty points and how to show the redemption value on the P&L (income statement). We got into code and looked around and made a plan. There are about 5-6 pages that need to be tweaked. This same thing will end up needing to be done for internal adilas customer loyalty points. We haven't finished the financial side of things for the customer loyalty points yet. Coming soon.

Alan and I touched base on projects and Alan showed me some of his new unit testing. We talked about a few projects and then did some work on our own. I ended up doing emails and recording notes. Alan kept working on a Metrc project (state tracking system stuff).

Work on Invoice due date project

Bryan and I got together and pushed two different projects. One was dealing with some new white label changes (verbiage, variables, graphics, etc.). The other one was dealing with showing the part or item category in the advanced invoice line items reports. Both sets of code were merged in and pushed up to live servers.

Got on the meeting with Drea from adilas tech support. She had a client that had reported a few small issues. We went through the different issues. One was dealing with corp-wide settings (easy fix), another was dealing with pulling too many records at a single time (training and filtering), and the other one needed a small code tweak to allow a report with sales by zip code to allow more than 50 zip codes to be shown at once. We fixed the code and pushed up new files to all servers.

After that, I spent the rest of the session working on emails and checking on the data 4 server. A database password had expired and we couldn't make the server connect to the database. Wayne ended up fixing that for us.

Meeting with Chuck. Alan joined us and Wayne joined part way through. We started out by going over new corp admin mock-ups, talking with Alan about projects and files, and then looping around and introducing Wayne to Chuck and vice versa. Wayne has been working in and on computers since 1979 (long time). Towards the end, we had Chuck show Wayne some of what he is doing on the camp adilas project. Nice meeting. See attached for a couple of screenshots.

- Both Chuck and Wayne have worked on the hardware and networking side of the IT world - As a funny side note, they don't like the pressure of "It's always the server guys fault" - Pretty common for IT guys. They get the blame. They don't get remembered when it runs correctly, they just get the blame when it has a hiccup or an issue.

Weekly meeting with Brandon and Chuck

Weekly meeting with Brandon

Alan and I touched base on direction. We then jumped off the meeting and worked on our own projects. I was doing emails and recording notes. Alan was working on a Metrc project (state tracking system stuff). We will do a joint work session later today.

1/15/20: "The underage being hilighted in orange is a wonderful feature. Is there a way we can code in that same feature but for expired ID’s in red?" from customer in California. Would like a quote and willing to pay if reasonable!

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

Updated the global_parent_core_updates.cfm

Added a new button called Parent Weight Update and associated functionality 

Eric and I met and talked over the phone. Later on we got on a GoToMeeting session. Both times were dealing with the math for how to track customer loyalty points. We were having fun going through different scenarios.

Alan and I spent some time working on the tax-v5 sales tax project. I was merging in files and Alan was working on black box (custom code) pieces.

Work on Invoice due date project

Bryan and I met to talk about refunds. Those get kinda funky as each corporation may have different steps, fees, requirements, and processes. We talked about some of the possible variables and looked at some situations and scenarios. We did some negative invoices, talked about validation, and even setup a refund recipe to help automate a couple fees that the client wanted. I think it helped to talk through things. Lots of human variables in a refund, partial refund, exchange, or applying in-store credit.

Emails, tech support, and recording notes.

On the morning meeting. Dustin checked in. After that, Wayne joined and had a few questions and we chatted about a number of server things. He showed me a simple mirror option for MySQL databases called the federated engine, it just needs a source and it kinda updates it self (almost like a live mirror). We talked about server stuff, database stuff, VPS's, options, and some domain name stuff (records and pointers). Lots of good information. I'm so glad that Wayne knows what he is doing and does a great job with that stuff. It helps me out by him knowing what he is doing.

We didn't do a team training today. I spent most of the session working on pointing a number of domain names to the main adilas.biz server. We purchased these domain names years ago, they have just been sitting there. I'm trying to at least point them to a valid website.

We touched base over the phone. Making progress.

I had a tech support call with a client. They (two of them) joined the call and we went over some processes. For some reason, one of the companies on the data 2 server is having problems with duplicating expense/receipts and then the payables are acting funny. This company has numerous accounts on that server. Only one of the companies is having problems. I promised to go in and look for custom code, possible bad data, and look over the duplicate expense/receipt page to make sure that all is well.

1/10/20: Steve and Cory looked at code and couldn't determine what was missing.

1/16/20: Cory met with Brandon and explained "add/edit balance item body cfm lines 374-404. He explained that it is deeper than just looking at that code. There are most likely several things that need to be fixed. We need to make sure the fields are open. Something could have been disconnected or covered when the flex grid was expanded but need to dig deeper.

Small fix- a developer needs to go into code on receivables homepage, in the body and flip the word "businesses" with "customer type" currently businesses is hard wired in for some reason, and showing up in the type field.

Fixed by Brandon on 1/16/20.

Cory and I went over some new items that are being added to the adilas tick list (community funded projects). We talked about a few, took some notes, made some assignments, and talked about costs for each new project. We are making progress, even though it feels slow sometimes.

Small work session. I fixed a small page for Cory (receivables homepage) and then switched over the to tax v5 branch for sales tax changes. This branch of code is from quite awhile back. It deals with customer tax fields 6-10 and dynamic naming for city, state, and county tax fields per location. The v5 means version 5. This will still take awhile to finish, but we already have 4 mini projects live and in use. This fifth one should help to finish things up.

Alan joined the meeting and was working on the tax v5 branch as well. After talking for a bit, we both went on mute and did our own work session.

Work on Invoice due date project

Helping Dustin with some JavaScript questions. Working on domain name records.

11/10/20: There were glitches and now they have been fixed.

There is a menu board that was developed by Bryan Dayton for a client. Current clients would benefit from this function, and Cory has a particular client who is interested in using it. Is there still a monthly fee?

Work on sprucing it up.

Steve was leading out on the morning meeting today. Both Dustin and Danny checked in briefly. After they were done, Steve and I spent over an hour chatting and talking about direction and options. We had an assignment from a business consultant to talk about a some disfunctions (places that need work). We spent some time and worked on one area. The disfunction area was rejecting structure. There are about five areas that we will end up looking into.

See attached for some notes. The main take away was we need to keep going and doing what we are doing. We would love to focus more on the adilas café ideas and concepts as well as opening up the market to allow our power users to help staff that part of the puzzle (buying and selling services - part of the adilas marketplace). The other topic that we talked about was employees and employers. Steve really likes the idea of the dependables and keeping a small core team of independents that can run and manage themselves.

Gather Testimonials, then design, code and launch.

Paying bills, emails,  recording notes, and other small projects. Spent some time working on the duplicate expense/receipt page. Looking over old code and making a few changes.

Steve, Danny, and Dustin were on the morning meeting when I joined. They each reported and then bailed out. That is pretty common. After that, Steve had a few questions. We went over some of his plans for the transactional data to enterprise data roll-ups and some of his plans. He is right on target and seems to have a good plan for that project or multitude of projects. Good stuff.

Alan sent me a text and said that he had the flu. No training today.

I spent the time working on the duplicate expense/receipt project.

Shannon and I met up to work more on the outline for the sales and presentation gallery. See attached for the current working outline. Today we spent some time on the expense tracking section.

Towards the end of our meeting, I got a call from Wayne dealing with an SSL (secure socket layer) for the data 7 server. He tried to walk me through some things and then we got on a GoToMeeting session. It kept giving us an error that needed more time to work through. We ended up calling Newtek, the server farm, and having them help us out. Wayne was calling from the airport (heading on a trip) and didn't have all of his stuff with him. On a good note, because he wasn't at his home, the servers were denying him from getting access. That is good, but it wasn't good at the same time. That means that the firewall rules are working but it also meant that we had to call for help to get a new SSL installed and renewed. Kinda funny.

1/21/20 from Steve:

email from client:1/20/20

Meeting to review the view and functionality of the Dispensary Homepage, new transactional features.'

Kelly would like to review prior to launching

We met and talked about a number of projects.

- There were some requests on the customer loyalty program stuff. They want a new permission, be able to handle voids, and also fully map and finish the backend accounting.

- Lots of talks about the ICC's (internal cost corrections) and getting that project going. Research on ICC's.

- Menu boards - take our existing pieces and push it to the next level.

- Talking about project costs vs helping with seed money and getting things started.

- We need to build a tool to help migrate customers, similar to part numbers or items. This is one system to another system on the same server. We already have a migration report for general inventory items. We will just build one for customers between corps.

Bryan joined the GoToMeeting with Steve and I. We were talking about coupons and how that would work and what it would look like. Here is a link to some research on coupons. We were talking about standalone discounts, in-line discounts, percentages, dollars off, free products, buy on get one (bogo), etc.

Bryan and Steve were also talking about advancing the menu board options and helping to make it more and more available. Bryan built a menu board, years back for a client. We may need to revamp that and/or give it a face lift and then go from there. Steve really wants to make it, the menu boards, part of the product and free to all users. We did the same thing with the basic web presence and the paid version of ecommerce. We are trying to make all of these pieces just part of the whole product that we offer.

There were some talks about pushing the menu boards and ecommerce further and further and even helping those two pieces come together better. The more we can keep focusing on building out our product, it just helps the core to be better and more stable. We have to walk this interesting balance between custom work and core work. In a way, we need both. They feed off of each other.

Lots of talks about project management and getting seed monies in place before we jump on these projects.

Work on Invoice due date project

Working on the duplicate expense/receipt project.

I got a call from a client and they were going through balance sheet and year end stuff. We ended up on a GoToMeeting session and looking at what they had going on.

Note for me, I saw an ad about Square and a free online store. I wanted to go in and check it out to see what they are doing and offering. This is more for me. Click to see.

Working on the duplicate expense/receipt code. Lots of loops and validation stuff.

Weekly meeting with Chuck

Met with Chuck over a GoToMeeting session. We covered three main things in our meeting today. The first thing we looked at was the Wander Ways website and the mock-ups for the sales arm of the camp adilas project. See the screenshot for an update. Nice looking site and Chuck will be working with Marisa and Danny on prices, verbiage, photos, and content. Exciting.

We also went over some new mock-ups on the adilas corp-wide settings and corp administrator homepage. We talked about some options and also decided that a nice banner image would really help that page out.

The last thing that we did was go over some code for the camp adilas internal tools and project. This project is in the coding phase and looking good. Chuck is using some of his new JavaScript skills to help wire things up a bit. Still in the transition between code mock-up (CSS and HTML) and backend wiring (making it real and come to life). Great report and making progress.

Weekly meeting with Brandon

1/4/21: 8 hours by JM
2/3/20: Brandon can knock this out in the next few months. No big rush at this point since forms have already been generated for 2019 taxes. Will keep it at the top to put on Brandon's schedule this spring. 

1/22/20: 

 I have a customer who is generating W-2’s in Adilas. The EIN pre-populates in the W2 from the Add/Edit Corporation page but that page has no spot for the State Employer Id needed on the W2. Is there a place to enter the state employer id number so it doesn’t have to be added manually on each W2? 

Work on Invoice due date project

Worked with Bryan on a number of different projects. We did some cart custom PDF labels, document management, and then on to QR codes and other PDF labels. After our meeting, I did some tech support stuff and emails.

Working on the duplicate expense/receipt code. Lots of new work on the action page. It didn't have some of the new stuff like tying things into elements of time or tying things into balance sheet items. Working through the code.

Steve and I had a good session talking about options of creating a true solar system level system (using the world build and space analogy). We did some drawings, took a few notes, and looked at some older drawings and graphics. Here is a good reference for some older world building graphics - click here.

- Ice-down dates - We had a good conversation about this. What if we pull a general aggregate for revenue, cost of goods, expenses, assets, liabilities, and equity - then when they pull it, they can then push it. These aggregate totals would be on a per day per location and per category basis. At this point, when they pull these totals, we could allow them (the users) to lock things down on that day (the date could a date back in time, depending on when they pull the data). Basically, each day could virtually get a lock-down or ice-down date. If needed, they could unlock things and then lock them back down. Just ideas and we still need to figure out the particulars, but these were some more ideas from today.

- Parent/child >> in the solar system level - We have had a very good experience talking with people about parent/child relationships and how that plays into the mix dealing with inventory items and other stacked relationships. If you go far enough, eventually it gets out into grandparents, great grandparents, etc. Normal parent/child relationships exist all over the place.

- Solar system >> planets (transactional worlds) and the sun (enterprise or aggregate system). We were talking about what terminology works best for our solar system analogy. The solar system is made up of different worlds that are closely related and somehow interconnected either through the database or through a relationship (parent/child or brother/sister or something like that).

- In inventory, we have vendors & customers (high level), PO's & invoices (medium level), items (small level), parent/child items and relationships (smaller), mini conversions (even smaller or micro)... in the universe analogy we have solar systems, suns (controller world), planets (transactional worlds), locations, groups, individuals, data, etc. Almost everything goes from big to medium to small levels, depending on how things are grouped and/or shown.

- Top level mappings - corps, locations, vendors, part categories, expense types, deposit types, etc.

- Enterprise solutions >> who is your buddy and how is everything setup (structure)? We had some brief talks about how to set this up. For now, we will just hard code things and then introduce variables a little bit later on down the road. Eventually, there may be database records and even one-to-many relationships with what corp type (world style or world type setting), who are the players (buddy list), and which way does the data flow (up, down, bi-directional, etc.). More planning is needed.

See attached for some drawings

Working with Shannon. We spent some time and went over some of the main happenings and how the different projects are tying together. Both from the graphical user interface side (UI/UX - user interface or user experience), the layouts, the code, and then mixing and blending all of those pieces together. Super fun. I showed Shannon some of the screenshots from Chuck and projects that he is working on. We also talked about internal adilas and some of the page layout and flow changes that are coming internally.

After that, we spent some time brainstorming on payroll options and what pieces we wanted for our presentation gallery under the payroll stuff. All kinds of fun things like time clocks, user/employee options, vendor options, reporting, forms and paperwork, commissions, project time tracking, customer time tracking, check writing, automatic updates on forms and tax look-up tables, etc. Fun stuff.

1. 3/3/20: RFID tag in quote is complete as of today. Still need RFID tag number to print on print ticket.

   Queue is complete.

   
   

   Add a cancel/remove button to the fulfillment homepage- just like the one on the queue page (https://data0.adilas.biz/top_secret/secure/customer_queue.cfm?timeCode=43894.3680208)

   
   

   Display RFID Tag on Fulfillment Home Page for QUOTES. This requires adilas to allow users to save RFID tags to a quote. (I would also suggest displaying the RFID on the print ticket). I have heard the argument against why someone wouldn’t want to save the rfid to a quote but I have many company’s that want to.

   
   

   This piece required a new column, back fill, new code, then restore cart piece and some logic. Then it catches up to natural flow. This is $1500.

   
   

2. Associate the orders that are on the Fulfillment home page with the QUEUE they were originally assigned to. One person will manage fulfillment home page for “in store queue” while someone else may manage the “delivery queue”. You should be able to see all or select just one.

   
   

   Once they turn on their sub queues, we can connect it and add the settings in the fulfillment page.$1,000

   
   

   

   

As of 10/29: Another $500 roughly.
As of 9/22/2020, 2119.25 billed. Danny has completed but there is a snag with the particular pdfs that Scott has. Waiting to see what happens next.

7/27/2020: First part complete as of today. Waiting for Brandon to push live? Danny starting on second part. To date, $1,000 billed.

5/28/2020: Client paid- in the queue

4/2/20: Waiting on green light...

2/13/20: Client is interested in moving forward.

2/3/20: Images to subs was quoted at $2,000. Then once this is done, Danny could do "label" for $500-$1,000. Sent email to client today, waiting to hear back.

Attach PDF's to subs and merge the pdf's to print all together. CMS media content

1/23/20: "We are being required to print Certificate of Analysis for each batch that we transport for each client.  The BCC is requiring physical copies to be transported with the manifest and physical goods.  We are currently printing each COA manually by each line item on the invoice.  I was thinking that Adilas may be able to help us with associating COA’s to Sub Items as PDF’s, then combining these into one PDF that can be printed."

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.

e-commerce
production homepage

Meeting with Jonathan to go over some progress. We haven't met in a few weeks due to holidays and what not. The meeting went well. Jonathan and I were on the whole meeting. Steve joined us in the middle for a part of it. Here are a few of the things that we did and covered:

- Review of the education mode - see the screenshots. The education mode allows a user to turn on/off additional helps, tips, help files, verbiage, videos, graphics, etc. The user can turn things on/off to keep the interface more clean and streamlined. If they need more help, it is available at the touch of a button. Side note, added this link to a small video on the education mode on 8/14/23.

- Review of the invoice interface with some fake data. Jonathan is working on showing mock-up data and how it may look and flow, as the user interacts with the system.

- Talking about style guides and standards - design systems - This is how we will end up standardizing the look and feel over multiple pages, components, reports, and features.

- Components and using consistent assets (visual and code resources). Both in the design and in the code - design/code once, use many.

- Talking about mobile development and more needs for mobile ready pages.

- We also talked about the placement of certain eye candy pieces such as graphs, charts, and other stats. Leaning towards the reports pages and/or section.

- We briefly talked about Jonathan's research on fracture and breaking up the system into smaller pieces. Being able to have the mountain of tools and options (features and benefits - current adilas system) but only showing what is needed (turned on/off and properly configured) and streamlined per industry and per company within that industry (making custom software easy). Basically, the ice-burg model. As we got into this, we ended up talking about the core product (the main adilas platform) and how we could allow for industry specific interfaces and settings to play over the top of the skeletal type model.

- The skeletal type model deals with the underlying systems... imagine a person with just a skeleton structure. You could then put normal clothes on that skeleton structure. Pretend this is core adilas (plain jane vanilla). Then you could dress that person with industry specific clothing to get all types of different outputs. Every industry has a different look and feel, verbiage, style, flow, etc. That is like putting on specific clothing on the skeletal system.

- Towards the end, Jonathan and I were talking about the shopping cart and how that part of the system really needs some loving. So many pieces converge on the shopping cart and point of sale interface (POS). It is pretty awesome. Here is a small help file on the shopping cart - click here. We talked about some of the known pieces that converge inside of the cart such as smart cart logic, customer loyalty points, tiered pricing structures, discounts and discount engine stuff, inventory tracking, sub inventory, mini conversions, labeling, coupons, payment solutions, sales and promotions, etc. Once it hits the cart, it gets put into the database and starts its life cycle. We talked about how the shopping cart and things that flow into it and out of it are kinda like the heart of the application.

Meeting with an outside developer who is setting up a custom VPS with some data for a company to run his own analytics. This developer was hired by the company to run some other reports and such through his own environment. Our job is to supply the VPS with a copy of the live data so that the developer has a working model and environment that he can play with. Awesome idea and concept.

Anyways, we went over some database stuff, mappings, key fields, data relationships, and how things tie in together. We did some drawings and other tech talk stuff. As a fun side note, it would be really cool if we have some of this same stuff (what makes it tick) really documented out so that other developers (ours and outside developers) could tap in and play. That would be super cool. Future project. As an idea, maybe a tech mode (similar to the education mode or data mode or permission mode) for the fracture stuff. In tech mode, we could get into the nitty gritty details of how things flow, connections, data relationships, decision trees, conditions and conditional logic, switches, validation, keys, etc. Super techy stuff. The tech mode would talk to the developers, programmers, and/or the curious persons who want to see the backend logic and design.

Recording notes and adding documentation to the different entries and elements of time. Lots of fun screenshots in the past couple of days. Here are some fun entries:

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=22&id=1532 - WanderWays - camp adilas project

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=5530 - WanderWays website prototype project

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=5864 - internal adilas mock-ups - fracture project