We are getting more outside vendors (3rd party solutions) trying to sell us block chain (blockchain) type technology. This is both on the inventory tracking side as well as the accounting side. Currently, it sounds good and cool but there are hidden costs and problems.

As a side note, we are also getting more pressure on servers and who has access to control what pieces. We are still bringing things up at AWS and Newtek. Both systems have a different structure. That is a challenge as well.

Another topic is dealing with API sockets and dealing in bulk sending and receiving data back and forth. The other circling topic is the need for customer rewards, loyalty points, and other special account stuff. The deeper we get, the more buried we seem to be. It almost seems perpetual and an ongoing mode of being buried. Thus is life.

On the adilas permissions (we have tons of them), we would really like to help that page with the look and feel as well as a copy user permissions and/or templates. We were also talking about a possible grouping of permissions and even a drill-down type interface for permissions, settings, and how each thing could be layered and/or navigated. The easy answer may be a simple copy a specific user's permissions. That could be the fastest option for helping out with permissions and setting up permissions for other users.

We had a discussion on the transferring of sub inventory and parent inventory. We have some clients that want to mix the locations on PO's, invoices, and quotes. It gets really crazy. They want to virtually skip the transfer step. Steve would like to maybe help them out by creating a new process that allows for bulk transfers. As an alternate option, Steve would like to potentially be a project manager for this project and work with Bryan on a new solution.

Spent some time reading over public records on blockchain. There are some advantages and a number of disadvantages. As of right now, we will continue with what we have going on and working on a digital assembly line. https://en.wikipedia.org/wiki/Blockchain

Jim Dougal (tax atterney in California and works with differnet CPA's) jumped on and had a few questions for Steve. We also had Pat Dolan join us. Pat has been helping out Adilas with sales and customer relationships. We also had Timothy Lyons (lead IT and tech for Herbo) join in the meeting. The subject of the meeting was dealing with pricing, technology, and how to move forward.

1. Price piece - discussion between Jim and Steve

2. 3rd party solution - Herbo ecommerce solution - We want to allow all of the customers access to this option. Having said that, we need a 3rd party solution switch that would allow for an actual switch (on/off).

3. Integrating with Square (payment processing) - They are in the process of finishing up the contract between Herbo and Square. Steve has already talked with Bryan Dayton (adilas developer) for the Square integration.

4. Other - On the server side, we briefly talked about dedicated servers and how we can proceed. We could commission physical dedicated boxes or virtual cloud clusters. Along with that, we talked about custom URL's and/or domain names. There were some questions about when does a company need a dedicated box vs a shared stack or semi-dedicated server model. What are the thresholds and capacity levels? How many transactions are we looking at per company, per server, per group?

Looking forward on AWS (amazon web services)… we get away from a physical dedicated server but it gets into a dedicated stack and/or dedicated cluster. The AWS environment allows for virtual load balancing and then automatically adding and subtracting dynamic power to help with the processing.

There were some conversations about splitting up the bus and getting each company on its own corp-specific database vs a shared database. As we get bigger and bigger, we will need to split things apart to make them faster and more efficient. Having said that, that also increases the need for back-to-back API sockets and data exchange between clients and clients and corporations and corporations. As things grow, we end up seeing lots of cross-corp type connections and functionality.

Tim had a couple questions:

1. Where are we going to host things? We would like to setup a meeting with our current hosting provider. Tim would really like to be in on this conversation. We, from the adilas side, need to get both Wayne and Alan involved in our decisions. As a side note, we have a physical dedicated environment that works and can work in the future. All of the AWS and/or dynamic cloud interfaces are in the process... but we don't have a physical fully working environment.

Steve was talking about once we get things settled, we can still jump up to bigger servers, clusters, and even migrating data and systems to the more robust virtual environment. Lots of options. There may even be some pricing options such as economy level, mid level, and deluxe type levels. Some of that may come back to where are things hosted and what are the environments that get setup.

Tim was talking about umbrellas and having dedicated and shared servers underneath the main umbrellas. Basically, a way to stack the systems. In a way, we simulate a hosting company by sub dividing our IT assets as needed.

- What are the timelines for AWS or Newtek?

- There are some discount options for pre-buying and/or pre-paying for servers.

- There were some talks about charging for hosting as a pass-through type charge. Currently, if our clients are on a shared type environment, we only charge a monthly fee, similar to a ski lift (pay for a seat and the chair is just spinning). However, if we have a dedicated client, we charge a server fee and then the monthly within the dedicated server. Kinda like a private chair lift per server. Adding in some options to help do normal charges and then also help the clients pay for what they are using (being able to track the stats and real usage per client). They were also talking about watching and monitoring each box and getting the best ROI (return on investment) per server. Basically, the standard fee structure that we currently use may need to change to help deal with pass-through and new and upcoming costs.

2. What about code branching? They, Herbo, would like to offer a specific version (branch of code) and then be able to mix and blend and cross merge code as needed. If they develop things, we could merge them in, if we develop things, they could merge them in. They would be separate branches. We would like to have another meeting between Wayne, Alan, Tim, Steve, and others.

- We briefly talked about themes (separate internal sub folders) or are we at an API socket level (external data sharing) where we are just exchanging raw data back and forth. The difference is, it built internally or built externally and just played at the API socket level (play at the wall). If they play that way, external API sockets, they could use AJAX and just push and pull data through the API sockets. If they work on the API socket level, they could code it any way they want with any look and feel and any backend coding languages.

- Steve kept bringing it back to use what exists and what works and we'll go from there.

Emails, phone calls, and follow-ups.

Shannon and I had a work session working on the brainstorming document called tools that we use. We spent most of our session working on the sub comments dealing with world building and taking things to an advanced level. See this element of time for more details and then scroll down toward the bottom to see the entry on world building. https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=4029

Steve and I were on the meeting before Bryan jumped in. As a side note, we need to be able to focus on a project. We keep getting pulled in every direction. We had a great conversation about direction and what we want to do as we try to focus. Super good stuff.

Bryan, Steve, and I had some conversations about allowing or disallowing mixed locations on the PO and invoice lines. We talked about rules on the location level, on the parent line item level, and even on the sub inventory level. As we talked about it... we really need to keep each PO and/or invoice completely specific. Behind the scenes, we need to help them transfer their inventory via bulk transfers to keep all of the pieces correct.

For documentation, each main PO or invoice is tied to a single location. This is way up high on the main or top level.

Each main PO or invoice then can have any number of line items... (line items). Ideally, each of those line items need to be tied to the same location as the main.

If they go to sub inventory (child packages), it gets even deeper. Each line item (parent line item) is tied to a location. All subs under that parent need to be in the same location other wise you get a disconnect.

As we were talking about it... it almost feels like a need for sub locations and being able to move things from one side to the other. Just an idea.

Steve was talking about a similar need on the production side of things (bringing things together to make something new). They, the companies, have inventory all over the place. As they build the new items, we need to transfer things into the correct spot to make the new product. Bryan is on the opposite side, he is bringing things in and wants to send some of this and that to different locations (spreading or distributing products). It all deals with a background transfer step that either needs to be there and/or should be there to help with the virtual paper trail. Steve would love to help speed up the process and build in the auto transfers and help with the moving and/or tracking of the sub locations and sub phases.

As a side note, we ended up using elements of time to help track the changes in the sub location and/or phases. The main PO's and/or invoices really need to hold on to things pretty tight at the location level. That goes all the way to inventory tracking principles.

Getting back to accounting... we really need to simulate what really happens and then be able to track it all the way out. If you add too many short cuts, you end up loosing yourself. We have to track what really happens. Cause and effect. Interesting that time is a major factor in what happens. Digital story telling.

On a super positive side... Bryan is working hard to come up with solutions. He is really pushing on things.

One of our virtues is to keep going day after day. We also keep trying to solve and take the next logical step. We just keep doing this over and over again. That's what we do.

Steve and I were talking about our guys. Dustin is doing great. We are excited to see where he will end up and what we can do to help that process. Steve is really excited about Eric and getting him going on more internal stuff. He has been a great custom developer and a great team player. We keep trying to make a one stop solution. That becomes a challenge. Steve was talking about directing the energy of the guys and putting them into the right spot and best fit.

Some of our 3rd party solutions end up giving us a big black eye. We want the outside help... but it kinda comes at a cost.

Steve was talking about an analogy between an arrow and a target. If we are the bow (our company), what arrows are we going to use and where do we point it.

We then started talking about some of the byproducts that Adilas can and does create. We are seeing needs in oversight, compliance, training, sales, consulting, custom development, etc. Steve was saying that one of the main goals is making your CPA happy (on the accounting side). Oversight could a reoccurring service. Some of the other services are reoccurring but they tend to cycle through different companies. It is reoccurring and a never ending need but it does cycle more.

Make a small goal, then regroup and huddle up and make the next plan. Kind of a return and report type model.

Steve and I would like to offer more guidance and help with system oversight. To fit Steve's analogy, we need to be aiming the arrow instead of being the arrow. We tend to through the rope across the river and then someone else could come back and help carve out the trail a little bit better. Steve and I are kinda like pioneers in some ways. We keep trying to solve the problems that present themselves. Some of these projects may include scouting, research, ideas, demos, prototypes, mock-ups, and eventual plans.

Inspect what we expect.

We started talking about a trail type analogy. We want to build to certain points, some of it is pretty stable and awesome, some of still needs some loving, and some of it still needs to be pioneered and explored. It just keeps going.

We have tons of projects... we need to turn some of those ideas and projects into ice (water, slush, to ice). We need to follow the same analogy as we did for operations and accounting. We have an ideal (straight parallel lines) but in real life, it needs to flex a bit. Once we allow the flex bubbles or flex pods, we then put in some checkpoints. That helps us make sure that things get brought back together. We could then add in permission levels and eventually allow it flow just like a data assembly line for code vs a data assembly line for data, inventory, and financials.

We are seeing that we, internally, need to provide some small goals and checkpoints and then help with the oversight to help them get to the next checkpoint. We are building SaaS (software as a service). Do we really know where that is going? The answer is no, we truly don't know. But we do have a good idea (an ideal or a goal or a direction). That is great and may be good enough for now. This is a paradigm shift for us.

Taking and bringing things back to the trystorming type methodology. We make a plan and then keep trying and trying, knowing that we will have to circle around again and again.

We need a plan (even if it is dusty and/or a little rough). We then take action to get there (small goals and checkpoints). We then look at the results and make the next decision. We allow the flex but still provide some checkpoints. We do tons of mini project management stuff all the time. Maybe keep going with that and keep it going from step to step vs planning the whole voyage. We still need a vision and master plan, but keep it small and turn it into attainable steps. As a side note, if we don't get enough communication between our developers, we may need to shorten up the checkpoints and make it into smaller attainable goals and steps. Checkpoint, direction, checkpoint, direction. That would be awesome.

Such a fun conversation. We got into resource planning and management (y axis) type stuff. We want to softly start reaching out and helping our guys and gals hit their stride. A fox that chases two rabbits catches neither.

We had some more talks on the adilas community funded projects and helping to tie things into the adilas tick list (see attached for an excel file). We would like to use these two things and actually use those documents as part of the project management tools and tool sets. We also talked about pulling in a ranking (priority) and using some of the code that Bryan was working on for voting on and creating an adilas community and what they would like us to do and work on. This will be a little mini project for Steve and I. Let's use what we have and start down this little path. Yee haw!

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.

Bryan is doing some code for a white label company. They wanted to remove the name adilas.biz from some of the help files. We went in and did some coding to allow those help files to be more dynamic. The new code allows us to pass in variables through saved database content such as help files and other white label options.

He also had some questions on advanced sub inventory searches and reports. We rescheduled and will look into this a little bit later on.

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.

Touching base with Alan and Dustin on their weekends, trips, and plans. Great guys and good stuff. It is fun to see all of the guys figuring things out and having fun in the midst of the crazy stuff. I made a few phone calls out to other developers and just trying to circle the wagons a bit. Emails and other to do list stuff. Wayne popped in for a bit as well. We setup an appointment for tomorrow morning.

Around 10:15 am ish, Steve and I were the only ones left on the meeting. Steve had a number of things that need to be taken care of. I was taking notes (good old post-it notes) and we got into a great discussion about servers and what we have and where we are going. We were talking about our current setup with Newtek (physical dedicated boxes and dedicated servers) vs AWS (cloned images and private and shared stacks and clusters). We also talked some about how we could possibly take an interim step and maybe increase the output and throughput over at Newtek. We started drawing and talking about current observations, options, and known bottlenecks. Great stuff and I think that it will help us out when we talk with Newtek about some options. Along with that same discussion, we talked about possible ways of getting people (other companies or corporations) off the bus or giant shared database environment and into their own databases.

After that discussion, we got into reporting, financials, and switching between transactional data and aggregated data reports. That spun us off into a discussion about how to show and display the P&L and balance sheet values directly from the same page or report over time. We have dreamed about this for years now. If you want, look up "movie" in the developer's notebook. Not all entries apply, but some of them totally deal with running the business financials over time in a virtual movie type format. Showing the growth and flex patterns of a company using the aggregated sums, averages, and totals. Pretty cool idea.

As a direct quote from Steve today - "I would love to teach people about accounting from the balance sheet backwards (meaning where the data came from)."

We also talked about switching to more robust servers, software on the servers, and switching between community and enterprise editions on database models and scripting environments. Lots of possible options. We just keep taking the next logical step (lots of little changes).

Increased the timeout on the balance sheet homepage, the P&L, and the history homepage. Light research on making a virtual movie type report and showing financial data using aggregated totals over time. That could be really cool.

Bryan and I got on a work session. We first looked at a bug with an export to CSV. We found the error and it was in a custom include file. The problem was the path and making sure that it was relative to the calling or processing page.

Next, we jumped back in and looked at the sub inventory invoice line items search with all sub attributes being allowed. This may seem super easy but it really has a lot of teeth. We did some conceptual planning, took some notes, and Bryan is going to go try to build it. We will meet back up tomorrow or the next day to see how it turns out. Good progress.

Recording notes and drawing out a small server structure diagram. See elements of time # 4804 for the diagram. Just trying to record the ideas and possibilities.

Touching base with Wayne about AWS and possible cloning and clustering options at Newtek. I showed him the brainstorming doc that Steve and I made yesterday. We also talked briefly about the task code and how we may be able to harness some of that code to help with other automated tasks in the system. Currently, Wayne is looking into some of the image stuff that he had working on AWS. They made some changes (Amazon) and it broke our code. He is working through that and making new changes.

Alan was showing Steve and I some new getters and setters (dynamic database code). Basically, the old code that we use to do and make was start to finish code dealing with a specific task. This new code is very generic but allows for all kinds of dynamic SQL (database code). That is really cool. We also talked about the need for training of our team to use some of these new features. Good stuff.

Just for fun. Light conversations about being a digital nomad (modern day gypsy spirit). Alan is looking into doing some travelling and working for Adilas along the way and chiming in from different areas around the world.

We were talking about parent attributes and sub inventory attributes. We need a way to flatten the data in order to work with labels. Calvin and I were on a Zoom session. We did a lot of drawing and talking about ways to show the human side of things and the computer side of things. We ended up looking at data samples, drawing database schema maps, and brainstorming ideas on how to help flatten and/or standardize sub inventory attributes and other dynamic data driven objects. The tricky part is that sub inventory attributes could be anything... we virtually let our users build their own databases (specific data points that they want to catch and/or track). We then have to allow them to use those values in labels. It gets pretty deep.

Shannon and I met over a Zoom session. Steve and Josh were on the GoToMeeting channel. We did some review and worked on more content for the adilas user guide. We are currently still working on the limitations of world building, under a sub document called tools that we use. We also spent some time talking about our flex bubble type model and how that analogy and/or system plays into real life and plans that we make.

See element of time # 4791 in the shop for more details.
https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=4791

Met with Alan for half an hour going over the existing internal API socket system. We talked about web page id's, API sockets, requirements, and how things are validated. He has a project (invoice due dates and automated watchers for overdue invoices - collecting on a/r's or accounts receivables). He will either be using the existing path way and/or slightly modifying it to work better for future development. Good stuff.

I got on a call with Drea from tech support and she had a number of questions about barcodes and settings inside of adilas. I assured her that beyond creating and generating the barcode, the other settings are on a printer driver, scanner setting, or a browser setting. We don't have any of those pieces in our system. We also briefly went over options between Adobe Flash barcodes and Calvin's PDF labels and sheet labels, using the adilas label builder app.

Grabbed some older notebook sketches and put them together into a single image and uploaded them to element of time # 4791, here in the shop. The combined image is a quick break-down of the data assembly line analogy and model.

Paying bills, recording notes, and following up on a possible project between Cory and Shannon dealing with a custom adilas glossary of terms. Spent the rest of the time back on the special accounts project (rewards, customer loyalty points, gift cards, and other special accounts).

We merged in a couple of code branches. After the first two, we ran into an Internet issue and Bryan had to drop off the call. We finished up over the phone. We did not finish the third code merge. It will have to wait until another day.

Pretty quite morning. Dustin was on for a little bit. He is working on harvest and cultivation functionality. We chatted for a bit and then worked on our own projects. I did emails and stuff like that.

Met up with Shannon for another session on the tools that we use document. It still needs some editing, but it has most of the content now. We spent most of our time today working on limitations and other future topics that need to be considered if doing world building (bottom of the page in the sub comments). See this link for the full document. We have added to this doc for a couple of weeks, here and there. The original was started way back in 2013 and 2014. Long time coming.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=4029

Chuck and I had a meeting to go over some progress. Chuck is a new frontend developer and is going to be helping us with graphics, layout, WordPress stuff, and other frontend development. Today, we reviewed what he has been learning and got him setup on his own new system. We set him up as an Adilas user, bridged him to Adilas, created a new world for him called Swan Haven, LLC. and setup him up in that corporation.

We did some light training and I helped him invoice me and setup some time tracking pieces in elements of time for his projects. I gave him some new assignments and he will be checking in towards the end of next week. Good start.

This was some text from an email about barcodes and how they work inside of adilas. It has some good links and info:

Hey guys,
This is Brandon. Just chiming in on this topic. The main Adilas barcode generator is Adobe Flash based. There are no Adilas settings for what label printer, what label scanner, or what brand a client may use. That was on purpose. Eventually, it comes down to the individual drivers, hardware settings, and browser settings. Adilas does not control any of that.

Here are a couple of help files with some good information about barcodes:
https://data0.adilas.biz/top_secret/help.cfm?id=361&pwd=barcode – barcode generator
https://data0.adilas.biz/top_secret/help.cfm?id=362&pwd=tech – tech info on barcodes
https://data0.adilas.biz/top_secret/help.cfm?id=413&pwd=cart – how adilas scans and uses barcodes

Another option that exists now, thanks to Calvin, is the adilas label builder app. This plays with Adobe PDF (Acrobat) technology. The new adilas label builder requires a little bit more technical knowledge on the setup, but it is available. I would recommend that we possibly go that route. If they don't have anyone who wants to play, I would be willing to work with the client. I'm not a master, but I've seen numerous demos and have played with the product before. The new app allows for labels from invoices, customers, PO's, and inventory items. It can do individual labels, custom labels, and all kinds of sheet labels.

Calvin is currently working on sub inventory items, sub inventory attributes, and flex grid connections. That will be really cool.

Here is a link to more information about the adilas label builder app.
https://data0.adilas.biz/MyEasySoftware/adilas_label_builder_app.cfm

If push comes to shove… I'll be their label tech. I'm a $100/hour but happy to help. Anyways, just chiming in. Thanks guys and gals and have a great day.

Brandon Moore
435.258.5504 (home/office)
435.881.1536 (cell)
brandon@adilas.biz :: www.adilas.biz
"all data is live and searchable"

We did two new branches and got them all merged in and uploaded to all servers. Bryan also kicked off some graphics my way that need small tweaks to help with white label display stuff (taking off the adilas logo and what not). We talked about another tech support question from a client and how to interpret smart group buttons and tiered pricing structures. We ended up going and looking up some documentation from the web/API socket documentation. Bryan will get back with the client and make sure that they understand what is needed and how to interpret those values.

Added some new graphics and took off the adilas logo to help with white label options. Nothing major, just removed some logos.

Steve, Dustin, and I were on the morning meeting. Steve had a couple of query questions and we briefly looked at some code. We talked about an upcoming Adobe ColdFusion conference that we will be going to and a couple of other light topics. Mostly we touched base and then worked on our own projects.

Emails and research on the Adobe ColdFusion conference in October. Spent quite a bit of time reading over the possible workshop topics and seeing which ones looked interesting. There should be some great information. We have four of us planning to go to the conference in a couple of months.

https://cfsummit.adobeevents.com/sessions/

Had a quick 15 minute meeting with Eric. We touched base on a couple of different things. He is headed out to California here soon, so his projects will be coming in from abroad. After that, I did some checks and paid some bills.

Bryan and I were meeting about white label options. We have a client that wants to offer 3 separate or different 3rd party solutions. One would be for the main white label opt in/out, an outside 3rd party ecommerce solution, and a custom 3rd party payments solution. Then, our clients, could sign-up for none, all three, or any combo of the 3rd party solutions.

We also spent some time and talked about the system setup process and who does what and how that rolls out. We also covered some specifics on setting up ecommerce pieces, API sockets, and how to effectively use internal themes and folders for code and custom code options.

On the call with the Newtek guys. We had a guy by the name of Dan and Will from Newtek. We had myself, Steve, and Wayne on the call from the adilas side. We covered a bunch of topics and they will be getting us a new quote with a new structure and format. Here are a few of the topics that we chatted about. No specific order:

Config, templates, older servers and older software (upgrades needed), newer servers and software are available, being able to stand up instances, take snap shots, fault tolerances and rollovers, HA (high availability), load balancing, clustering, proxy servers, scaling out vs scaling up, number of database connections, etc.

After the call, I spoke with both Steve and Wayne on different phone calls and just touched base with them. Good calls.

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.

Meeting with Steve, Dustin, and Alan. We all touched base and bounced some questions off one another. I started working on a bug fix for the shopping cart. After that, Cory popped in and worked with Steve and I on the adilas tick list (upcoming and current projects - aka the to do list). We spent a couple of hours inside of adilas adding notes, updating priorities, and crossing things off our list. We setup another meeting for tomorrow. Trying to get organized on the project tick lists.

https://data0.adilas.biz/top_secret/community_funded_projects.cfm

Working on a small bug fix of doubling up some output tags in some of the page headers and page top files (black box stuff).

Bryan and I met up and talked about possible ways of getting and showing discounts. See attached for our scratch page. As part of our conversation, we ended up going out to the server and looking up certain values in the database to see what options were being used. We looked up automated discounts, customer types, individual customers, parts/items and their settings, tax categories, parent attributes, sub attributes, smart group buttons (tiered pricing), different manual and standalone discounts, corporation settings, custom cart logic, menu boards, and black box code. Lots of options.

Emails, tech support, and working on the output header bug.

On the morning meeting with Steve and Alan. Steve had some JavaScript questions for a custom page that he is working on. We talked through a few things and got him going. Alan and I were talking about some other projects and small bug fixes.

Around 10 am, Cory Warden popped in and her and I worked more on the adilas community funded projects. We were setting budgets, ranking and setting priorities, adding notes, and trying to get that section more organized. We are thinking that one more good session should get us caught up for now. Always more to come, but we are making progress.

https://data0.adilas.biz/top_secret/community_funded_projects.cfm

Shannon and Cory and I spent an hour or so working on some glossary definitions. At first, we were just randomly recording words and phrases that we use in the adilas world. Our eventual goal is to make it more polished and allow people to use it as a normal glossary of terms.

Here is the link to what we have now:
https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=4030

4/21/20: Adding CanPay for client - Completed on 5/9/20 srb

8/26: Request for Square as payment type for CBD.

8/14/19: Request for MTrack as payment type. Client has started using a new debit card and wants a payment that denotes the name of the card.

Brandon handles this. Pushes to data0 and copies to the rest of the servers. 

Request for these two payment types on 8/12/19. Have heard of other requests in the past. 

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 (https://data0.adilas.biz/top_secret/custom/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.

Sucker company wanted to scan individuals on invoice, but grouped invoice line items. Per part number= 1 line. All data still held and recorded. Items were grouped by the parent.

You would choose the invoice view- ie mini, summary, etc. Could be called grouped output in corp wide settings.

In this situation, they want to scan each item to add to the shopping cart, and they want it to "bundle" all of the packages into one line item per barcode, instead of itemizing 50 lines, for example.

Stripe is a great merchant processor with minimal requirements for setting up a new account. No prior business info is required. They charge a percentage of the transaction and that is it. No monthly fees or anything like that. This is a great starter gateway and way to accept credit card payments.

If the business is more established, they may want to checkout out things like USAePay or Authorize.net or other merchant gateways. Stripe is a great entry level merchant processor and gateway.

Glossary Terms:

A

• Actions/Action page - Often when you are on the web you have a form and it always submits its data to an action page, where it performs an action. 
• Accounts Payable - All bills, invoices, PO's and reimbursements that are due to be paid. Money that is owed to others from your company. 
• Accounts Receivable - All invoices that are not paid. Money that is owed to your company. 
• Active - Status that designates data as being in use. This status relates to customers, vendors, and items. When active, data will show up in search and list by default.
• Add - This is a general term which usually means create, multiply, or add on to. Common things could be add a customer, add an invoice - basically this means create a new one or apply an additional one. 
• Add to Queue - Link that assigns current customer to a list or "queue" which is a step before the shopping cart.
• Admin Time Clock - Allows user to see all active time cards/hours based on requested parameters. Also gives ability to edit the time cards. 
• Adobe/PDF - See PDF. This is a product made by Adobe which requires a reader. PDF stands for Portable Document Format which  is a format that can be read across browsers. 
• Advanced Add to Cart - Make changes to the item already added to the cart- price, cost, quantity, and tax category. Add discounts. *Special feature: put in unknown quantity, but known price to have the system determine how much you can sell based on dollars a customer has to spend.
• Advanced Searches - Access data based on specific parameters in all areas of database: customer, vendor, parts, elements of time, invoices, expense receipts, po's,
• API - application programming interface- a set of functions and procedures allowing the creation of applications that access the features or data of an operating system, application, or other service. Allows our software to connect to other software through a "door" that we can elect to open or keep closed.
• A/P's - See Accounts Payable. A/P's is an acronym for Accounts Payable which is an accounting term for who do I owe. 
• A/R's - See Accounts Receivable. A/R's is an acronym for Accounts Receivable which is an accounting term for who owes me money and how can I collect it.
• Assets - Any resources owned by the business. Tracked on the balance sheet through user-maintained balance sheet items (not automated by system).
• Assign to Cart - Action taken to add a customer to a shopping cart. Link is seen to the right of the customer information from the customer homepage.
• Ctrl A - This is a keyboard shortcut on windows for selecting all the content in a certain area.

B

• Balance Sheet Item - A user-maintained account that stores data on the balance sheet. 
• Bank Reconciliation - Matching deposits and expenses in database to monthly bank statement. Must verify all transactions by date for these transactions to appear on the reconciliation page. 
• Banks - Virtual representations of banks or credit cards. May also be used to represent a location for tracking cash sales.
• Barcode - Made up of 15 spaces that may contain letters, numbers or symbols. Used to track inventory and speed up the sales process.
• Basic Live PO - Used to create inventory or inventory items in database. Name is dynamic and may be changed in the corp-wide settings (see section C).
• Bit Map Image - This is similar to a JPEG or a GIF image. Technically a bitmap means little tiny blocks of color that are organized in an image format to show a picture of some kind. The other kind of image is what is called a vector which has smooth mathematical lines that creates its visual appearance. 
• Black Box - Custom coded takeover of a page in the database. Gives customer specific functionality requested. Also makes page static to other system-wide updates so can create limitations in the long run.
• Browser - This is the tool for viewing web based content. There are multiple different browsers and some of them are based on your operating system or preference. Browsers are how all things are shown over the web. 
• BSI - Acronym short for Balance Sheet Items it may also be shown as B.S.I. These balance sheet items are what are called user-maintained items and is a miniature account for various things. Some of these things could be where you account for things such as loans, individual or company investments, large assets like buildings, vehicles, or machinery. 
• Build & Sell - This is a term used with a function called Recipe/Build. The build and sell is a quick, just in time, preformatted group or kit. So if there are multiple things that are sold together you can create this kit or grouping that you can use just in time on an invoice when you are selling these items.  
• Build & Hold - This term is used with Recipe/Builds as well but this term is used on the raw goods side. So a build and hold uses raw goods, meaning taking them from inventory, called ingredients. And produces outcomes or other products to be used farther down the manufacturing line or to be sold independently. 
• Bulk (in general - edit, verify, etc.) - The word bulk means more than one. In the system it is often used such as bulk edit meaning I am going to edit multiple lines at one. Or bulk verify meaning I am going to verify multiple things at one time. There is also bulk labels, bulk printing, etc. We are dealing with multiples of things. 
• Bulk Verify - Used to verify multiple deposits or expense receipts at one time. 
• Bump Value Up - The term bump just means move in a direction. Some systems would say debit or credit. We just say bump meaning which direction of flow is it going. Bump up means you are somehow increasing a value or total.  
• Bump Value Down - The term bump just means move in a direction. Some systems would say debit or credit. We just say bump meaning which direction of flow is it going. Bump down means you are decreasing a value or total. 

C

• Cart - Where items are placed in order to make a purchase (see also Shopping Cart).
• Check - One of many methods of payment, usually flowing out of a bank.
• Check Requests - A check request is a form of an expense receipt which is almost a question. Can I spend this money? It is similar to how a quote and an invoice are related, a quote is a potential precursor to an invoice. This is the same for check requests and expenses. A check request is a potential precursor to an expense. It does not count toward financials at this point. It requires an approval and once it is approved then it can become an actual expense and be booked on the financials. 
• Child - Refers to items in the database that can be sold. Connected to a parent item (parent inventory) which carries the name and some information. The child item is unique and can carry much more unique information (see also Sub Inventory).
• Chooser - Home page interfaces. 40+ choices plus custom options available. Called chooser because the user "chooses" which one is most suitable to their needs.
• Classic - Interface that shows all potential functions in the system. Not geared toward any particular tasks or industry.
• Clear Cart - Wipes out all actions related to the active shopping cart. Must perform this action in order to log out of the system, or to start a new cart.
• Clock in/out - Tracks users hourly work. Requires user to be assigned to a department.
• Closed - Potential status of a sub or child item. Once a sub/child item is at quantity 0, it can be closed. 
• Corp ID - Identifying number associated with every corp. Assigned upon activation.
• Corp Key or Alias - A corp key is a combination of three letters of the corporation name, a dash, and then a numeric corp id number. For example pla-0053. Pretend that this company's name was Playground and the Corp Id was 53, this could be it's corp key. The alias is like a username for the corp instead of the technical three digit plus numeric. An example for this one could be something like testing or playground. 
• Corp-wide Settings - Admin level settings that affect the database on a corp wide level. Options for setting system wide naming conventions, tax settings, discounts, etc.
• Corporation - This is a virtual world inside of a system. Corporation is also synonymous with entity, business, company, etc. Usually a corporation can have locations and different things within it but it is usually a tax entity. Often in the system you will see us use the word corp as a shortened form of corporation or business entity. 
• Counter Sale - Shopping cart that is not assigned to a customer. Used in sales situations where the customer is unknown and does not need to be.
• Create - This is another word for adding or making something new. For example create a new my cart favorite button or create new invoice link. 
• Cross Corp Invoice to PO - Special function that must be added by a system administrator (fees associated with this function) that allows one corp on the same server as another corp, to send inventory via an invoice. Both corps must agree to connect, then one makes an invoice, and the other turns that invoice automatically into a PO.
• CSS - This is an acronym for a web look and feel tool called a Cascading Style Sheet. The css of a site dictates colors, roll overs, margins, spacing, font, and other look and feel pieces. Inside of the system/platform we allow you to change a lot of these.  
• CSV - Comma Separated Values is a simple file format used to store tabular data, such as a spreadsheet or database. Files in the csv format can be imported to and exported from programs that store data in tables.
• Ctrl A - This is a keyboard shortcut on windows for selecting all the content in a certain area.
• Ctrl C - This is a keyboard shortcut on windows for copying a certain selection and putting it on the clipboard for future use. Ctrl V is used to paste.
• Ctrl N - This is a keyboard shortcut on windows for creating a new tab in your browser window. Often you can do the same thing by right clicking a tab and clicking new or duplicate, etc. 
• Ctrl P - This is a keyboard shortcut on windows for printing a certain page.
• Ctrl V - This is a keyboard shortcut on windows for pasting a certain selection held in memory. Either Ctrl C or Ctrl X are the ways of copying something to memory. 
• Ctrl X - This is a keyboard shortcut on windows for cutting a certain selection and putting it on the clipboard for future use. Ctrl V is used to paste.
• Ctrl Y - This is a keyboard shortcut on windows for redoing something that has been undone. It's brother command is Ctrl Z or undo.
• Ctrl Z - This is a keyboard shortcut on windows for undoing a previous action. It's brother command is Ctrl Y or redo.  
• Ctrl + - This is a keyboard shortcut on windows for zooming in on the webpage or browser. This is control plus sign (+). 
• Ctrl - - This is a keyboard shortcut on windows for zooming out on a webpage or browser. This is control minus sign (-).
• Custom - This is a broad term and can be used in many different ways. Often we use custom to refer to custom code, custom look and feel, custom flow, or custom processes. Also we use it generally to say we could add that in but it would be custom, meaning it would be specific to your needs and wants and go through a process of design and development to meet your needs. 
• Custom Logic - This is part of custom code but the term custom logic usually resides more toward the top of the page. It is like the brain for the page. This is how we control what is happening or could happen on a single page. You may often hear us say, "We could black box that." Meaning we could add code and logic at an insertion point to make the page perform custom actions, logic, flow, or other code related options. 
• Customer Queue - Customers waiting to make purchases can be placed in line or a queue so that they are seen in a first come first served order. Multiple queues can be used to designate customers as VIP, Pickup, etc.
• Customers - The people or companies you sell items or services to.

D

• Database - This is a background storage engine that holds all of the data tables, rows, and columns. The database engine that we use is called a MySQL server. This database server is very robust and can handle millions and millions of records, queries, and actions at a single time. Technically the database is that storage engine but sometimes we generally refer to it when discussing data or the storage area. For example, when a cart is fully submitted it transfers from session memory into the database.
• Default Homepages - Every user gets to set their default homepage. This is where you land, or are taken to, when you click your logo or home link. Think of this as your virtual starting spot or home base. The reason it says homepages is there are hundreds of choices that you could set as your default. As a side note you can also switch at any point to facilitate the task at hand. The original goal of this was like a person with a shed in their back yard. If they are paining they want painting stuff from the shed, if they are doing yard work you want yard work from the shed. Depending on the task at hand you may want easier access to options and/or tools. If you want you can even have a custom dashboard or default homepage made. 
• Default Settings - The system has a base of permissions and settings. This is how things interact and are used. A default setting means where it was set originally without any interaction or where that setting has currently been set to. Often these default setting will be changed based on needs, wants, or dictations from administration or higher authority. Settings come on a corporation level, a player group level, a page level, and even on a user level. 
• Delayed Inventory Counter - Used to count parent inventory by scanning barcode and entering quantity.
• Departments - Used to organize employees. Allows employees to utilize the clock in/out function (see above).
• Deposits - A total amount of money that flows into a bank.
• Deposit Types - Chart of accounts for deposits. System comes with several options and the user creates the rest.
• Dewy Decimal System - This was a funny name used as a code name/alias for a project to take functionality from 2 decimal points to 5 decimal points. Sorry librarians, no pun intended. ;) This was just taking numeric quantities, costs, and prices to multiple decimals of accuracy. 
• Disabled - One of the three statuses that refers to items and their ability to be sold or not sold. In this case, when an item is disabled, it is part of inventory but is unable to be sold (on lock down until enabled).
• Discount Calculator - Feature in the shopping cart that allows salesperson to discount items by dollar amount or percentage. Discounts can be by line item or added to the shopping cart as a whole.
• Discount Engine - Used to create reoccurring discounts. Settings determine if discounts are by category or item, and if by day, date, or time.
• DPI (Dots Per Inch) - This deals with image resolution both on screen and for printing. If you are printing something you want your DPI higher. If you are just viewing it on screen usually 72 DPI is enough for your eye to catch on the screen versus images for print are usually printed at at least 300-600 DPI. 
• Drill-Downs - This is a term for navigating through layers. An example might be you doing a customer search and it returned a number of customers. Then you would drill-down on the associated link to see their details, or drill-down to see their history, or drill-down to see other information, etc. 
• Duplicate Invoice to New Cart - Allows user to take an existing invoice and create a new shopping cart that is exactly the same as the original. Great for repeat sales in certain industries.

E

• E-Commerce - This is any sort of online web presence where you sell your goods and services over the internet. The software has both free and paid versions of ECommerce that are fully integrated and built in for our clients. Some of the cool features that you can harness are mobile ready, bill pay - where customers can come in and pay some of their bills, photo gallery, expanded descriptions, technical specs, automated emailing, and tons of custom display options.
• Edit - Function associated with all aspects of database- customers, vendors, items, banks, e/rs, deposits, invoices, etc. 
• Edit Line Items - Makes changes to the line items (second section) that have been added to a PO, deposit, invoice or E/R. 
• Edit Main - Makes changes to the main section (first section) of a PO, deposit, invoice, or E/R.
• Edit Payments - Makes changes to the payment section (third section) of an E/R or invoice.
• Elements of Time - May be defined by your business. Giant toolset that can be customized to meet your needs. Customer time clock, an appointment book, a scheduler of sorts, a dispatching solution, a payroll timesheet for employees, a mini blog, a general reminder system, etc. You name it, you set it up, and then you get to use it over and over again. You can search it, display it, add to it, create new templates, invoice time, quote time, and generally work with almost anything that has a time element associated with it.
• Employees - An employee is technically someone who works for a company. Inside of the system employee is a term that is used for persons who use the system and have permissions inside the system. Employees may have time cards, payroll, permissions, settings; they can also be used on expense/receipts and PO's and in these instances can be used virtually like a vendor. They also populate the salesperson list. 
• Equity - Equity is a section on the balance sheet which means some sort of long-term value. You can have different things like owner equity, paid in equity, investments, worth and distribution of wealth.
• EOT's - See Elements of Time. EOT is an acronym for Elements of Time. Another term is Time. When you search for time you are searching for an Element of Time. Technically you can have unlimited number of templates which are like cookie cutters. And then you can make an unlimited amount of cookies from those cookie cutters. It can go very deep.  
• ER's - Expense Receipt- these words used together mean any total amount of money that flows out of a bank.
• Expense Types - Chart of accounts for expenses. System comes with several options and the user creates the rest.

F

• Favorites - There are two primary ways that we use the word favorites in the system. One is a list of saved reports called your favorites. Another one is actually where favorites is a shortened term for My Favorite Buttons which are graphical point of sale buttons. 
• Flash - Flash is a shortened term for an Adobe Flash player. Flash has been used on the internet since early times. It could as simple as animations, special buttons, rich interfaces, etc. The software application uses Flash for navigation screens, check writing, barcode generating, and my cart favorite buttons (customer point of sale buttons). 
• Flash Bubble Interfaces -  There are three Flash interfaces that were designed my Russell Moore that may be used as default navigation homepages. They have special features such as rollovers, sliding menus, and drop downs. 
• Flash Buttons - Once again these are a shortened term for the my cart favorite buttons. Custom point of sale buttons setup by companies. These can be named, organized, colored, nest them, group them, preset settings, setup special pricing parameters, etc. These are often used as a standalone sale buttons or in the split cart view. Split cart has one screen of buttons and the other screen shows the cart so that you can see what has been added to the cart. 
• Flex Grid - Allows a user to custom code up to 30 fields per each main section. In short, flex grid allows the user to add additional tie ins, database fields and notes.
• Footers - A footer is anything that happens on the bottom of the page that is consistently there. Usually such things as navigation, branding, logos, copyrights, or other consistent notifications. 
• Form/Submit Form -  Anytime that a user can interact with a website is usually in a form. The software application has tons of web forms. Without getting super detailed you can have text fields, number fields, drop downs, text areas, radial groups, list boxes, check boxes, toggle switches, buttons, and other form features. The submit part of a form is when it actually gets sent back to the server and some sort of action takes place such as a search, an add, an update, a commit, a continue, etc. 
• Functions - This is a general term that could be used for what is your business function meaning process or flow. It could mean a logic decision behind the scenes - pass this variable to the function and you will get this result. It could also just generally mean how do things function meaning how do things work, how does it interact. Another term that we use sometimes is if you are dealing with API sockets (Application Programming Interface), we will often talk about the socket as if you are calling a certain function. 

G

• Gallery - A gallery is usually a collection of things most often photos, media/content, files, some sort of digital content. All of the 12 main players have their own galleries. Most galleries are tied to individual items within the groups. 
• General Tie-in - This could be one of two things. It could be talking about a thing called a flex grid tie-in which would be additional data related to the main item. Another reason we use general tie-in is if we don't know where the connection is going to go it can be tied to all sorts of things. Basically the tie-in means a relationship and general means you will need to categorize it.  
• GIF Image - A GIF image is a graphic and is considered to be in the Bitmap family. They have somewhat of a limitation on colors but they can still go up into the hundreds (like 256 colors). Some other really good benefits is they can have a transparent background and they can contain small animations.
• Global - This is a general term. We use it in a couple different ways. One would be a global variable meaning it is available for all. We have global settings which are generic across the whole system or a starting point. Then dealing with a world-building concept - global means within a world what is the style, attributes, presets, etc. for that world. All of these uses indicate broader or more general terms. 
• GPS - Global Positioning System. Basically inside of the software application, GPS can mean a physical location like an actual GPS or sometimes it is used as a term for a virtual locator of where I am in this world or in the system. Indicating a location, such as I am in invoices or deposits, etc. A cousin to GPS is something called an RFID tag. Both of them use some sort of X, Y, and Z coordinates but the main difference is that GPS is over a broader spectrum and RFID is in the confines of some smaller geo-fence but you can still tell where things are moving and can track things in spatial ways. 
• Gram Counter - Control added to the shopping cart for the cannabis industry that helps salesperson stay compliant in how much cannabis they sell to a customer. Multiple varieties exist based on requirements of the state of operation.

H

• Hardware - Technically this is computer peripheral type term. It usually means something that physically exists or something you physically connect to a computer. There is a physical aspect to it. You can see it, touch it, connect to it, it can contain it's own programs and software, etc. Some common pieces are laptops, desktops, monitor, disc drive, scanners, printers, and so on. Almost anything that has a physical component and an electronic piece that can be associated with a computer is called hardware.  
• Hash - The word hash has a number of different meanings. Usually inside of a computer system a hash means a small encrypted value that may be de-crypted or decoded by the computer. A way to make something non-human readable but still decipherable to a computer with the correct codes to unwind it. A general term for hash is a mix of things that gives you a new item or output at the end. 
• Headers - These are usually at the top of the page and have a reoccurring look, feel, theme, navigation, search options, menus, etc. It is basically a way of standardizing multiple pages to look similar - you can use or create a header. 
• History - History inside of the software application takes on numerous different flavors. History could be just what happens over time. It could also be user interactions, cause and effect cycles, check points, etc. The history is also a shortened word for the audit trail, the log files, and the decision trees within the system. Most histories inside of the system are unalterable - they are caught and monitored behind the scenes as actions take place. History inside of the software application can take on a couple different forms - effectual, historical, financial. These are all aspects of history but they all have a little bit of their own flavor. 
• Homepages - This is a web term for a starting spot or a spot that has like pieces. What we do is allow everyone to start with their own homepage or starting area. This allows them to navigate the system or have quicker access for the features they use. The other use of the term homepage in the system is for each of the 12 main players. All of these 12 main players have their own homepage or main hub for the features associated with that player. Such as invoice homepage, PO homepage, expense/receipt homepage, etc. Sometimes these are called sub homepages. 
• Hover - Action used to view links in the database. At the top of every page user can 'hover' over the main links to access myriad other pages in the database.
• HTML Buttons - There are two different terms for HTML buttons. Any form inside of the system technically has an HTML button to help it submit or do any other process. The other use of the term HTML buttons deals with my cart favorites and this is a comparison between Flash buttons or HTML buttons - meaning how the buttons are generated. 

I

• Ice Down - This is a term for basically permission based locking. This goes back to an analogy we use with liquid water turning more solidly into ice. As data in the system becomes more firm or set it virtually gets iced down. 
• Inactive - Status that designates data as being out of use. This status relates to customers, vendors, and items. When inactive, data will not show up in search and list by default. User must specifically request to view inactive data.
• Interactive Map - This is a graphic that shows a lot of the key elements inside of the system. A number of different departments, homepages, areas that have their own tools, etc. It is one of the standard navigation homepages. It is also used often for training when we are trying to show flow between the different areas or departments. The help file for that page goes into major details as to why things are organized on the map the way they are. 
• Internal Build PO - This type of PO is used internally to take raw goods and combine them to create something new (kitting, packages, groups, mini manufacturing, etc.). For example, say you wanted to make a cake, the raw goods might be flour, sugar, eggs, butter, etc. The internal build PO would subtract the raw goods from inventory (negative quantities) and create a new product called cake or cookies (positive quantities). This PO type has it's own permission and is very powerful.This same PO type is used by the system when using the internal recipe/build process. The recipes are basically a pre-set group of ingredients, parts, items, and/or outputs. These recipes are called "build and hold" recipes. The internal build PO may also be used when taking a certain part, painting it, heating it, cutting it, chopping it, combining it, or somehow changing it into some other part (any type of mini manufacturing). This PO type, internal build, is how you physically control your inventory counts. Similar to the update PO, this PO is not vendor specific and does require a special permission to use this PO type.
• Internal Repair - This deals with a stock/unit. Basically it makes an internal serialized item become a customer and you can use anything from your shop or store and attribute it or apply it to that specific stock/unit. 
• Invoice - Use to record a sale of any item or service to a customer.

J

• JPEG Image - A format for compressing image files. Every form in the database has a storage space for jpegs that can be accessed from the photo/scan button.
• Jump - This could be a couple different things. Often we will use the word jump to indicate some sort of motion or movement. This could be let's jump into this or jump to this place on the page or somewhere else in the application. Sometimes we use the same phrase when we talk about using the quick search inside of the system to navigate somewhere. So while this is an action term indicating movement and navigation it can also refer to times when you skip multiple steps by clicking or jumping somewhere. 
• Junk - This could refer to email, junk email. It could also refer to doing something which you are going to get rid of. Or it could be if you are putting garbage into the system, you are going to get garbage back out. This refers to putting bad data in the system - junk, garbage. 
• Just in Time - An acronym for this is JIT. This was originally developed in manufacturing and operational warehouses. Now it has been modified and is used in all kinds of things such as just in time inventory management, just in time bill pay, just in time project management, just in time communications, and so on. Instead of planning and preparing everything out to the nines sometimes you can do it just in time which saves both time and money and is an efficiency factor.  

K

• Keep - This is usually some sort of an action where you are maintaining or keeping something for later use. It could also involve something that you do continuously - for instance keep clicking on this, keep drilling down, keep refreshing, keep checking back, etc. Saying either save that or continue on that path. 
• Kill - This is a general term usually meaning to delete, destroy, make inactive, hide, etc. It is a general term that means to get rid of something. Other times you might talk about if it is going to kill the system meaning too heavy of a load, too intense, too many sub details, etc. 
• Knock knock - Who's there? It could be a joke but actually we use it in computer speaking when we are trying to gain access to API sockets. You play knock knock with the server. The server responds who are you? What do you want? Then you have to respond that those questions/requests. It is kind of a back and forth protocol. 

L

• Labels - Can be printed via browser settings from multiple locations in the database. Item labels can be used to add items to the shopping cart, item labels can be printed from within the shopping cart for certain industries, labels can be printed for plants from the cultivation homepage.
• Liabilities - Financial obligations of a company. Tracked on the balance sheet.
• Line Items - "Meat and potatoes of a form." Can be inventory items on a PO, expenses on an expense receipt, and invoice sales on a deposit.
• Link - A link could be an actual web link where you go from page to page. These are often used in navigation or drill-downs. A link could also be things that get connected or tied in. Such as an invoice might be linked with a customer or an item is linked with a PO. Another definition for link is an item within a chain of a process. What are the links that it needs to go through?
• Locations - Way to sort inventory, allocate sales tax rates, organize operations in the database. Completely dynamic.
• Lock - A lock usually means that something becomes more secure. It could be locking people out, locking things down, it could be advancing something so that people with lower permissions cannot access or see it. Another example could be a system being put or going on lock down - like the system or a database table. A lock is used to inhibit access. 
• Logout - Function that allows a user to leave the database. Once logged out, another user can log in from that computer. Note.. logging out does not clock out the user.
• Logs - Associated with customers/clients. Area where notes may be kept for historical reference.
• Look and Feel - Basically this deals with what you see. Your interface colors, your color choices, your navigation buttons, your interface layout design, your defaults, your style, etc. The software system allows for all kinds of dynamic colors, fonts, watermarks, graphics, logos, and styling to help with your look and feel. 
• Look Back Date - Usually this means that we are going back in time to look at data or content. Very common for inventory levels, sales, and balance sheet items.
• LPI (Lines Per Inch) - This is a printing term that deals with resolution. Another common one for this is DPI which is dots per inch. Often computer screens and printers deal with DPI where LPI is for professional print shops. 

M

• Main - The software application uses the term main in multiple different ways. It could be main homepage, main navigation, main or core logic. The word main might also refer to sub homepages such as main customer homepage, main invoice homepage, main deposit homepage. Going deeper the word main could also mean the starting of the object. Anything that can hold subs is a main. For instance the main invoice details or main element of time. We end up adding sub details, such as line items and payments, to a main bucket, item, or container. It is very common within the application to see the words edit main. This deals with going directly to edit the details required to start or initiate a new object within the system. 
• Make/Model - This is tied to serialized or stock/unit inventory. The make is usually similar to a brand name. Then the model is usually some sort of a sub division within that, that has some known attributes or pieces. In the system we allow you to define the makes/models and the underlying presets that go along with those. These are set up into one to many relationships where one make can have an unlimited number of models.  
• Manager's Time Clock - This is a permission/section that allows a user to oversee time clock records for departments that have been assigned to that manager. Time clocks have three different levels. You have the user level which is easy to add but you cannot edit anything. Then manager's time clock which allows you to add and edit but only at a certain level. Then admin time clock that allows for corporation wide adds, edits, and reports. 
• Mark-up - This usually deals with a pricing model where you take a value and you multiple it by a cost to arrive at a new price. Depending on if you are doing widget (small, bulk) type inventory or serialized (stock/unit) inventory there may be multiple levels of mark-up. Another way that mark-up is used is sometimes on coding language. A mark-up language is where certain things have tags, attributes, and parameters. 
• Media Content - Technically media/content is any kind of file, which could be spreadsheets, text documents, PDFs, graphics, photos, scans, audio files, video files, etc. that may be added to the system. Inside of the application we allow media/content to be added to any of the 12 main items, any of the 12 main player groups, or just generically to the system as a whole. Basically this is your paperless office function. 
• Merchant Processing - This is a general term used to talk about credit card transactions, authorizations, and processing. The system acts as the client side or software piece. It sends transactions over to a gateway which authorizes, confirms, and holds secure data. The merchant part of it deals with converting that data into real monies that will get pushed into the company's bank account.
• Mini Conversions - A conversion is where something gets converted into something else. Usually it deals with units of measure. For example gallons of water, liters of water, cups of water, drops of water, etc. The reason we use the word mini conversions is that we are trying to track a semblance of what is happening instead of a full conversion that might be unalterable. These mini conversions are simulating the breakdown or conversion into smaller or bigger groupings. 
• Mobile - This could mean mobile as in on a mobile device where the sizing or layout changes based on screen size. It could also mean the ability to carry, transport, or move around. It may also mean the ability to transfer pieces between things - the data can become mobile. The ability of the data to transfer between places such as to different corps, other software, different places in the application, etc. Often you might here the words mobile app or mobile ready - that usually means a software system that runs natively on android or iOS devices. 
• Money Types - Options for making and receiving payments.
• Money Type Settings - List that shows all existing options for making and receiving payments. Boxes may be selected or deselected to customize payment options based on form (Invoice, Shopping Cart, Deposit, Expense)
• More Options - Button provides access to links that are associated with the page in use. At the top of most pages.
• My Cart Favorites - Custom preset buttons that determine how items assigned to those buttons are sold.
• My Settings - This deals with access to user level settings within the software application. This could be anything from password and profile information to default cart types, expense types, Flash buttons, etc.

N

• Ctrl N - This is a keyboard shortcut on windows for creating a new tab in your browser window. Often you can do the same thing by right clicking a tab and clicking new or duplicate, etc. 
• News & Updates - Updates and how to's are posted here to alert users of new functionality within the system.
• Normal Parts/Items - The word "parts" is used to mean any item that is tracked as a group (including labor and services). It is also important to note that the words "parts" and "part number" are editable on a per corporation basis from the corp-wide settings. Specific items are called units or stock numbers (serialized units) and are handled through a different section (usually bigger ticket items). Sometimes the word normal parts applies itself to how things are tracked meaning tracking things in and out. 

O

• One to Many - This is a database concept and usually deals with some main element that may have subs, children, add-ons, additions, or some unlimited number of connections. Some examples could be one customer has multiple invoices or each invoice has multiple line items. We use the concept of one to many to talk way beyond just database things but that is where it came from. 
• One to One - This is also a database concept and usually what it means is a direct relationship. It's the opposite of a one to many. Often a one to one indicates a switch, a toggle, an additional value that may be conditional, an option of being turned on or invoked. 
• Online Bill Pay - This is where a customer would actually get a button, a link, or an email where they could go pay for a statement online using a credit card. 
• Open/Opened - This is a common term that we use to talk about being engaged, active, selected, etc. An example might be open this package, meaning make it active or current. Or open the invoice homepage, meaning go to that page and open it. Or you may hear someone say tell me what tabs you have opened, meaning what do you have showing. 

P

• Ctrl P - This is a keyboard shortcut on windows for printing a certain page.
• Packages - This is used in a number of different ways. Often it deals with batches for sub inventory. Sometimes they are called packages or child packages where you get into parent or child relationship. Packages could get into shipping. Packages could also be used for a certain set of features. For example if you were in a certain industry and wanted to buy the extended package that would be a set of extended features. Sometimes it is also used in the recipe/build area if you are creating certain recipes to create a package, or a kit, or some sort of group. 
• Page Settings - These deal with what happens on a single page. As a note there are corporation or world-level settings. There are group level settings such as invoices or PO settings. There are individual settings, there are also these page settings which deal with just how certain pages act, interact, show/hide, react, etc. 
• Parent - This usually refers to inventory and kind of a parent-child relationship. The parent is usually the main element or place holder. We then refer to the parent as the main item and the subsequent children are those related to that parent.  
• Parent Attributes - These are optional but these are classifications and categories that can be associated with different inventory items. These are ways to group and flag your inventories. This can help with sales and filtering of items/products. These are unlimited and often help in categorizing or searching or sub-filtering pieces together. As an example, say you bought outdoor equipment from a wholesaler but you really wanted to make sure that things were known for their brand. Not necessarily the vendor you purchased them from but the brand. This could be one example of a parent attribute but there are unlimited possibilities. 
• Parent Inventory - Inventory items. May be sold as is (status active) or may be set up not to be sold (allow subs only) but to act as name holders for sub inventory (see sub inventory). May also be set to inactive if no longer needed for sales.
• Parts - Items or services that are sold. The name 'part' can be changed to reflect the 'widget' inventory and or services. 
• Part Category/Categories - Organizes items into a subset. Technically a part category helps in searches, in your reports, and on your financials. It also helps if you are going to be setting up any sub inventory attributes. Most of your sales reports are done by category at the top level and then by item. 
• Parts Homepage - Main inventory homepage. May search for inventory by vendor, category, or item. Printable views also accessed from this homepage, as well as a multitude of advanced searches.
• Patient - System default is customer- patient is an example of a choice for renaming 
• Payee - Refers to individual or business being paid, either vendor or employee.
• Payments Not Yet Deposited - As invoices are created, payments are applied. This verbiage stands for the state of these payments. They are 'waiting' to be included on a deposit.
• PDF-Portable Document Format - a file format that is used to share data. Many pages in the system may be exported to PDF through the click of a button.
• Permissions - Over 100 rules that allow or block access to functions within the database. 
• PNG Image - Portable Network Graphic- type of image file that is accepted for upload under the Media/Content link located on most forms in the database.
• PO's - This abbreviation stands for both Purchase Order, used to receive inventory and Production Order, used to record and track light manufactured items.
• Post - A post has a couple different things that it could be. One, any time a form is submitted it is called a post in technical terms. A post in accounting usually means let's lock it down and make it tight, also meaning lock it down from lower permission users. A post could also mean when you take smaller details and combine them into a summed entry, this entry can also be called a post. If you are talking about fences, it's the big tall thing. :)
• Printable - View of data that is condensed in order to print more succinctly. Editing is unavailable in the printable view.

Q

• Quick Search - This function appears on each page and allows one to quickly search for any element.
• Quote - The step prior to creating an invoice. Can be skipped if desired or created and turned into an invoice.
• QR Code - A two dimensional barcode that holds more data than a one dimensional barcode. 
  
  

R

• Raster Image - This is also sometimes called a bitmap image. Usually what this means is that there are little blocks of color to make the image. If it is blown up to big it can become pixelated. For example, people who work in PhotoShop deal with raster images all the time. The opposite of a raster image is what is called a vector image, which deals with smooth mathematical lines, arcs, and curves. Vector images scale very well because they are mathematically based. 
• Recipe/Builds - Method of selling items grouped together into a 'kit' or 'recipe'. Pulls inventory onto the invoice in set quantities.
• Refresh Queue - A queue is basically a digital line. This could be used for projects, people waiting, people who need to be served, etc. Refreshing the queue typically just means what is the current status or order of these people or things waiting. Some of the pages actually have settings so that the queue will refresh itself at an interval the company has selected. 
• REI's - This is short for a reimbursement. A reimbursement is money that was paid out of a person's pocket that needs to be paid back directly to that person. These are very common in the expense/receipt side of the application. Fro example, say I was out and bought a new broom and wanted to have the company reimburse me for buying the broom. On a technical side reimbursements in the system must be paid back in full. There is something called a split in the system that you can chip away at an expense and make payments to it but a reimbursement must be paid in full. There are tools in the systems to combine or pay reimbursements in bulk. 
• Reoccurring Elements of Time - Often you will have things that you want to reoccur over and over again such as company meetings, a set/reoccurring due date, even a person's schedule - things that happen over and over again. Inside the system you have to create one primary element of time that exists by itself, then you can tell it to reoccur or choose how to reoccurs. The master needs to be created first and then you can duplicate that master to create the further elements for reoccurring. 
• Reoccurring Expense Receipts - This is some sort of a bill or expense that happens over and over again. This is very common for rent, insurance, draws, auto-transfers from banks, etc. You set up the master and then you can tell it when to duplicate itself and advance it's dates for creating the additional expense/receipts. 
• Reoccurring Invoices - This is charging a customer over and over again in some kind of a reoccurring subscription, or repetitive purchases, etc. Once a single invoice is setup it could be set to reoccurring if there is some sort of constant, regular billing. If the invoice amount changes you may not want to go this route. This is best used for the same items/services and amount reoccurring on a regular interval. Once again you have to have a master invoice and then it knows what to copy. This section inside of the system can do it both automatically and as a manual reminder in case things need to change. 
• Request PO - This PO type is used for ordering, requesting, or getting quotes from vendors. This PO type records all of the main PO info without taking it to the next step (receiving). The PO request may easily be turned into a "Basic Live" PO by switching the PO type. When this happens, the request will hold all of it's original info and becomes received (actual or live). At this point, it will function just as a basic live PO would (inventory counts and payables). This PO type is vendor specific. See corp-wide settings for custom naming.
• Responsive - This has a couple of general meanings. One of the most modern ones is called a responsive webpage, meaning it sizes well for different devices. The layout will change depending on the size of the screen, that is called responsive. Another use of the word responsive is talking about clients getting back with you, vendors, or even the server - such as the server is not responsive meaning that it is not responding to requests presently which could mean it may be asleep or dead for a bit.
• Restore to Cart - This means you are taking something, usually a quote, and putting it back into the flexible shopping cart mode where you can add, edit, change, and use the bulk tools in the shopping cart. As a note, restore to cart is from quotes but there is also an option to duplicate to cart which is taking a completed invoice and restoring it to the cart. 
• Results - This is also a general term. It could mean a goal - what are you desired results. It could mean results of a query - what came back from a search. It could also deal with testing results for something such as new code. Results are also trying to find what you are looking for. What do you get out of this thing that you are looking for. 
• RFID - Radio frequency i.d.- Used in the cannabis industry to track all inventory and plants. Unique number associated with inventory items.
• Rounding - Rounding deals with the level of accuracy, usually with number. This could be decimals to decimals or decimals to integers. It is also important to know that the deeper you split something apart there might be virtual saw dust or shavings which is referred to as rounding error - trying to get it split apart or broken down as close as you can. Rounding is often used in taxes, discounts, and eventually needs to be equated into money if you are dealing with dollars and cents. Sometimes inside of the system we allow things to be flexible up to 5 decimal points - the term we use for this in the application is the dewy decimal system - this is not related to libraries.   

S

• Sales Tax Settings - All settings are dynamic and can be entered on the location homepage. 
• Server (what server are you on?) - All corps are assigned a server that houses all their data. Server number is visible in URL ie. https://data4.adilas.biz
• Settings - Settings are usually some sort of user preferences or default values to help a page or a function configure itself. Inside of the system there are four main types of settings. We have corporation or world level settings. We have group or system player settings - for example invoices, parts, customers, etc. We also have what are called page settings which deal with a specific page function, flow, or process. The lastly we also have a thing called individual or user settings - this is where an individual or user gets to set some preferences such as default types, navigation, other presets and defaults. 
• Shopping Cart - Where sales happen in the database (see also Cart).  The shopping cart is how you sell your stuff. It is the interface between your customers and the entire rest of the system. The shopping cart eventually helps you to create your invoices and quotes. It is literally tied to almost everything in the system. If you took out this piece of the puzzle, not much would be happening. This is the "interface" piece.
• Show/Hide Search Criteria - This is usually a button or a link that helps you collapse or expand search forms. Often pages or reports needs user inputs or filters but showing that right off the bat takes up valuable real estate on the page. So the show/hide search criteria allows you to expand or collapse that when you need to interact with the input, filter, and searching section.  
• Smart Group - Basically, a smart group button is a my cart favorite button that contains all of the functionality of the normal cart favorite buttons plus it allows for pre-set pricing structures (quantities, weights, and prices) to be assigned or connected to one or more inventory items. Smart group buttons allow for both assignments (who gets to play) and rules (how things interact or play) to be set up.
• Snow Owl - This is a look and feel theme or motif. Snow Owl is a series of header, footers, options, settings, and styling for the pages. Originally developed by Russell Moore in 2017. Additional changes have been made. This theme currently has the most modern features, access to tools, functions, settings, and more. Sometimes we talk about Snow Owl in a general sense but this encompasses hundreds of settings, features, and options that are part of running Snow Owl. 
• Software - This is a term meaning any kind of code or program that is installed on a machine. Often software deals with licenses, updates, versioning, etc. Some of it's family members are hardware, firmware, freeware, shareware, and even sometimes vaporware. Even though the system is a web application it is sometimes generically called software. 
• Special Line Items - These deal with the hardcoded part numbers or "special line items" that are used within the application. Many of them have special uses and special code that is built in to the main application. These are things such as labor, fee, discount, verbage, other, shipping, trade-ins, and more. Basically these are special parts or items that can be attached to an invoice or PO and some of them even have special treatment on how they are tracked financially on the P&L and Balance Sheet.  
• Special Live PO - PO used to bring in inventory from multiple vendors. This PO type allows the main vendor to be set as the payable (who will get paid), and the line items may contain bulk, generic, or non-vendor specific items. These PO types are used by companies that buy the same item from multiple vendors and don't want certain items to be tracked on a per vendor basis. The items become a bulk or general usage item and are usually maintained under a special internal vendor. 
• Special Parts - This can be two different things, it can refer to unlimited items that don't track quantity such as labor or services, or it can refer to the special built-in application items.
• Special Request - This is the request side of the special live PO's. Very similar to a basic request except it allows multi and mixed vendors. See description of special live PO's above for more info. Once received, all special request PO's will need to be flipped over to the special live PO status in order to show up and become real or live. 
• Specific - Specific basically limits the scope. We use it as a general term and it could mean specific in reference to talking about a specific item or a specific relationship. We also use it when referring to things like corp specific, vendor specific, location specific, user specific etc. Once again it takes that general topic and narrows it down to that scope. 
• Split Cart - Feature that allows user to view shopping cart and my cart favorite buttons on the same screen simultaneously (see M for My cart favorite).
• Split/Splits - This has a number of different features associated with the word splits. This could be split payments - which is typically dealing with multiple locations where you may have to split or divide payments. A general term called splits in the system is a term used for payments that are on account. This is used when you need to pay a vendor and you may owe a larger sum than you can pay right then. You can attribute whatever monies you would like to that vendor's account and it will pay off or satisfy those expenses. Sometimes split can refer to split screen functionality that diverges or splits. If you are dividing revenue sharing you might create some sort of a split. 
• Start New Cart - Function that allows user to begin a sale.
• Statements - a time stamped report or "snapshot" of who owes you what.
• Stock/Unit Cust - A restricted view of serialized inventory. The view is 'customer' friendly, hence the name 'Cust.'
• Stock/Unit Full - A full view of serialized inventory. Includes cost and other info that should be hidden from customers.
• Students - Technically a student is a person who learns. There is a corp wide setting that you can use for your customers and if you happen to be engaged with people who are called students you may change your customer name to student. This can also deal with people who are learning from your media files or procedures. 
• Sub Attributes - Unique information associated with a sub inventory item. This information is driven by sub inventory templates that are created based on the tracking needs of the business (see sub attribute templates).
• Sub Attribute Templates - Templates that carry the unique data assigned to sub inventory items. These are assigned by the business based on tracking needs.
• Sub Inventory - Items in the database that can be sold. Connected to a parent item (parent inventory) which carries the name and some information. Sub inventory is unique and can carry much more unique information (see also Child).
• Switch Corp - If a business has more than one corp they can switch between them without logging out.
• System Assets - Contains all company assets. Deposits, Accounts Receivable, Invoices etc.
• System Basics - Basic permissions and links to preform calculations.
• System Liabilities - Contains all company liabilities. In general all payables that your company owes.
• System-Maintained BSI - Item on the balance sheet that are automatically generated and updated by the database.
• System Maintenance - Section that contains homepages that allow the user to maintain different functions.
• System Management - High security level that allows the user to maintain corpwide settings and user permissions.
• System Reports - General reports to help you know and understand the company finances, inventory levels and historical data.
• System Time & Requests - Inter company calendar. Used to schedule any 'element of time.'

T

• T terms connected in the sub notes below - click to view whole document

U

• U terms connected in the sub notes below - click to view whole document

V

• V terms connected in the sub notes below - click to view whole document

W

• W terms connected in the sub notes below - click to view whole document

X

• X terms connected in the sub notes below - click to view whole document

Y

• Y terms connected in the sub notes below - click to view whole document

Z

• Z terms connected in the sub notes below - click to view whole document

Paying bills, phone calls, and emails. Back working on the output bug and doubling up output values.

Bryan and I got on a Zoom session and worked on a dynamic sub inventory report. Last time we had talked about taking over the numbering system and passing in hidden counters behind the scenes. This was going to help us be more dynamic and even allow us to group like sub attribute names (from different item categories). He had gotten that done and it was looking great. We then rolled into the output and/or search results. We were getting results but it was pulling in more data and values then was needed. We spent most of the session talking about how to show/hide columns dynamically.

As a side note, we do tons of this on the flex grid tie-in reports and output. The flex grid table has over 70 data columns but sometimes we only show 4 or 5 columns based on data that is stored. We end up converting all output to numeric lengths, blanks are a 0 length, and valid data is converted into a length or number. We then watch for columns that have a positive length (sum up the column lengths). With the correct logic in place, we can virtually show/hide all of the other columns until they have valid data in them. Anyways, we were working on similar type dynamics for sub inventory attributes and whether or not to show/hide certain columns in the output report.

Merged in the new code to fix the double output bug. This was dealing with some Adobe ColdFusion code called a "cfoutput" tag. We had a couple of spots that were nested and/or doubled up. Fixed a bunch of files and repushed the files to all servers. I finished out the evening by sending some emails around and following up on things.

On the morning meeting. Pretty quite today. I did emails, follow-ups, and light prep on one of the current projects that we are working on.

Cory and I were on a meeting for a couple of hours. Lots of back and forth conversation about projects and pieces. We finished up our first round through the adilas tick list and adilas community funded projects. This was meeting number 3 for a total of 6-7 hours of going through projects and what was what. Currently, there are about 100 projects with an estimated budget of $2,500,000 (ish) and around $500,000 already contributed by Adilas and other outside parties. Pretty cool and fun.

Here is a link to the current adilas community funded projects:
https://data0.adilas.biz/top_secret/community_funded_projects.cfm

This is just for fun... I was looking through some really old graphics and I found one that was used at the starting of when we originally released the adilas community funded projects in early 2015. See attached for a funny blast back to the past. When we launched this, I literally felt like the guy with the worn out shoes, barely making it across the finish line. We are now sitting 4 years later and actually making progress on some of the projects. Kinda fun.

The snow owl menus have a number of hard coded values. change the ones that need the dynamics so that they reflect the corp-wide settings. Such as parts home, customer home, location home. As a side note, there are both on canvas and off canvas menus (lots of drop-down menus). Both need to be updated.

Spent a couple of hours back working on the special accounts project (rewards, customer loyalty points, gift cards, in-store credit, etc.).

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.

It currently works... but the way around the park is up the slide, around the merry-go-round, and past the swings. There isn't a straight line right now. We could use some loving there.

Steve and Dustin were on the meeting this morning. They were going over the need to keep picking up the virtual dust... (imagine an analogy of cutting boards and logs - eventually you end up with chips and saw dust after the main cuts have been made). We are pretty good at grabbing and dealing with the main transactions and main processes. We are seeing tons of sub, optional, or secondary processes starting to show up. Basically, how do we/they clean-up and deal with the smaller pieces and chips (virtual dust)? Interesting discussions. Everything keeps breaking down into deeper and deeper subs. Things are virtually fracturing into smaller and smaller details and sub routines.

Steve and I were talking about project management and helping to keep our guys and gals on track. We were also talking about core adilas projects, custom projects, and who is able to do and handle what. Lots of moving pieces. Steve and I are going to try to steer things a little bit better from the inside. We are wanting to use Cory as somewhat of a gate to help us get projects into the project queue. As a different analogy, image that we are all in the same boat. All of us are pulling and pushing pretty hard, but we are not fully organized and pulling and pushing in the same direction.

We briefly talked about an implementation bill to our clients for custom work. This could include things like planning, oversite, and implementation. This is just an idea right now, but we are spending tons of our time on custom projects and we don't get any value from them. We need to start charging for our time on the adilas side of things.

Shannon and I were recapping and working on organizing the online glossary. Shannon was doing most the work. I was just there as support.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=4030

Helping Shawn get his local environment updated and up to speed. Touching base and briefly talking about other upcoming projects and options.

Code review and working on the special accounts project (rewards, customer loyalty points, gift cards, etc.). Working in the view cart and add cart payment pages and sections.

On the morning meeting with Steve and Alan. Steve is working on some projects that deal a lot with JavaScript and sub calculating things on the fly. We went over his current position and where he still wants and needs to take it. Both Alan and I were chiming in and giving him some ideas and pointing him in a good direction.

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.

Emails, uploading videos, and general clean-up.

There is a setting that needs to allow for this. Also a permission. Show/don't show cost.

Or, we build as a black box for their company. With settings, could be global. 

top_secret/secure/bulk_edit_cart.cfm

8/19/19: email from Tarmac Cultivation: "Can you help us get the COST field and EXTENDED COST field built into the [Bulk Edit Items] tab within the invoice page? We need to transfer our cost of goods onto the COST that we’re charging our dispensaries prior to distributing product. The current process is cumbersome and this will help lighten the load big time (as opposed to deep diving on each individual line item)

We have a production facility as well as a Retail facility that function within the same corporation. When we produce products, they are packed into a retail package and carry a Retail Sales Price. The sale price needs to be marked up in order for our Retail store to be able to scan and sell products, and the cost information needs to be available for us to see and pass on to our other stores. 

Let me know what the cost is – happy to smooth things to make it go faster..."

8/19/19: Added to the project list per Steve to track completion and funding.

New API Document Link

https://api.licensee.fl.biotr.ac/documentation/index.html

8/19/19: Will has completed the Leafly integration.

In progress: JM-10.05

1/7/2021: Assigned to JohnM/ completed 2/3/21

https://data0.adilas.biz/top_secret/secure/advanced_receipt_search_results.cfm

12/15/20: latest request: 

11/5/2020:

https://data0.adilas.biz/top_secret/secure/super_invoice_line_results.cfm

 https://data0.adilas.biz/top_secret/secure/advanced_parts_search.cfm?part=all 

https://data0.adilas.biz/top_secret/secure/check_search.cfm?fromDate=all&toDate=all&checkNum=all

needs data table

10/27/20: New page assigned to John M:https://data0.adilas.biz/top_secret/secure/search_queue.cfm: 6hrs-$150+$100 for Brandon=$250

10/8/2020: Eric and Brandon wanted to add this one:

secure/corp_special_account_tranactions_home.cfm

4/2/20: Added this per kelly:

https://data1.adilas.biz/top_secret/secure/admin_time_clock.cfm (this might not be improved with a data table)

3/17/20: Jon H went through cannabis site and made this list of pages that need snow owl/data tables/export abilities.

https://data0.adilas.biz/top_secret/secure/advanced_sub_po_line_results.cfm

These three are on Renee's list:

https://data0.adilas.biz/top_secret/secure/receivable_home.cfm - this is already conditioned.

https://data0.adilas.biz/top_secret/secure/part_usage_history.cfm = assigned to Jon H on 4/23/20. Needs some tweaks to launch.

Completed: third_party_error_log.cfm

https://data0.adilas.biz/top_secret/secure/parts_home.cfm

https://data0.adilas.biz/top_secret/secure/advanced_parts_search.cfm

https://data0.adilas.biz/top_secret/secure/balance_sheet_parts_categories.cfm?useDate=3%2F14%2F20

https://data0.adilas.biz/top_secret/secure/advanced_invoice_search_results.cfm

https://data0.adilas.biz/top_secret/secure/balance_sheet_home.cfm

https://data0.adilas.biz/top_secret/secure/advanced_time_search_results.cfm

https://data0.adilas.biz/top_secret/secure/advanced_time_sub_results.cfm

https://data0.adilas.biz/top_secret/secure/advanced_receipt_search_results.cfm

https://data0.adilas.biz/top_secret/secure/advanced_receipt_line_results.cfm

https://data0.adilas.biz/top_secret/secure/advanced_receipt_payment_results.cfm

https://data0.adilas.biz/top_secret/secure/flex_grid_search_results.cfm

https://data0.adilas.biz/top_secret/secure/search_receipt_payee_results.cfm

https://data0.adilas.biz/top_secret/secure/invoice_sales_profit_report.cfm

https://data0.adilas.biz/top_secret/secure/super_invoice_line_results.cfm

(I did this one already. Not sure if I need to fix something on the code to make work or if it was never uploaded)

https://data0.adilas.biz/top_secret/secure/advanced_invoice_line_results.cfm

**Customer Homepage (this was completed- see project 1652).
Location Homepage?
Parts Homepage
Payables Homepage

https://data0.adilas.biz/top_secret/custom/mmj_operations.cfm - (hundreds of links that lead to tables). Not sure how to go about this page and associated links.

7/9/20 - added by Brandon.
https://data0.adilas.biz/top_secret/secure/invoice_home_basic.cfm - as a note, this one has double pagination. That seems to be a problem that needs to be cleaned up for all tables with data tables (snow owl vs classic and different pagination) - fixed on 7/11/20. I also wanted to leave this note in case we need to do the same things for other pages.

Not a big deal. Would add a new column show/hide/active list. Separate into show or hidden. Show disabled banks. Change criteria.

Currently, you can't make banks inactive, or it will throw you out of balance. It would be helpful to hide banks that are no longer being used or considered active. Perhaps there is a third status choice for banks: active, inactive, disabled (which would make them not show up on the list but they wouldn't technically be active for balancing purposes)?

Met up with Shawn. We got caught up and went over some billing stuff. We then spent most of the session going over future projects. I'm going to have Shawn help me prep the field and do some prep work on the round 3 of sub inventory. We are going to go in and back fill some data on certain tables and such. It should really help speed things up.

Met with Bryan about a sub inventory export and general report. We have been working on this one for a couple sessions now. Really good news... it is getting super close. At our last meeting, it was looking weak. We made a to do list and a list of requirements. Bryan came back on this session and was able to virtually click all of the boxes. A huge success. We spent most of the meeting going over flow and then following variables around. When we started the session, I had a number of questions. I got most of my questions answered and Bryan really stepped up on this project. He took the to do list and really made it happen. Prior to this, It literally was kinda dying but now it has a chance. Still pretty deep, but at least possible now. Great job Bryan. Wahoo.

On a technical side, the new reports pass dynamic hidden values across, you can refine your search, the values get pulled out, used as filters, and looked up. He has it only showing lines that match and also only showing attribute columns that match and have data. That is a multiple dynamic hide/show based off of both rows and columns. That takes quite a bit of code to make that happen.

Spent some time working with Dustin and Steve on some mixed JavaScript. This is where you have dynamic database driven variables, lists, and arrays. You then build it in so that your JavaScript (client-side code) can talk and deal with your server-side Adobe ColdFusion code. I like to call it mixed code. It can get pretty deep sometimes.

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.

https://data0.adilas.biz/top_secret/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.

Emails, follow-ups, and working with Steve and Dustin on their JavaScript. We were on a Zoom meeting and Steve was coding while Dustin and I were helping him out. Lots of testing and walking things forward one line or phrase at a time. Good stuff.

**We decided to add this setting for a client at no charge. If they want to proceed with more limitations, then they will need to pay.

Limiting permission to hide invoice homepage. New permission- Don't show invoice homepage.

fyi id#141- permission is supposed to limit view to only their own data but user can see invoice totals.

Client would like to limit view of this page- no view at all. It would be a permission that could be selected to have access to the invoice homepage or to deny access(unchecked) to the invoice homepage. The salesperson would still be able to do all necessary functions in the cart with the other invoice permissions that currently exist (give discounts etc).

If we see that an inventory item is connected to a vendor we flag it.

Steve spoke about this in our 8/19/19 meeting regarding vendors who should be included on a special po drop down list. This would automatically check the box for vendors who are included already on PO's with inventory items. Currently you need to check this box manually. Something to consider down the road. This flag is essential for the Special PO.

3/9/20: This is new movement by client who is willing to make something happen. Invoiced them today. #291440 is their client number. Waiting for their feedback and then will meet with Spencer again.(last meeting had to be cancelled last minute)

2/25/20: This has a lot of movement right now with one client who is willing to help fund this. Spencer has looked into this. ajax is remote baby calls to the server. 

We have had a few requests to make a more streamlined shopping cart. They are thinking a one-pager. This would include options for searching, adding, editing, discounting, and cart payments all on the same page.

Working with Shawn to back fill some sub inventory data and data migration. Part of the meeting was spent getting Shawn some dummy data. I then did some research on copying database tables and how best to do things like that. Emails and uploading videos from earlier meetings.

Bryan and I had another session on the sub inventory export report with all categories (advanced invoice sub search). This is a really deep report. We merged in code, pushed it up live, and did some testing. In the live testing, we found a small bug and tracked it down and got it fixed. Kind of a long session, but making progress. We still need to do similar things for the PO side of the data.

Dustin and I were the only ones on the morning meeting. We spent the whole time working through some deep triple looping JavaScript for a page he and Steve are working on. We made a ton of progress and pushed the ball further down the road.

Cory and I spent an hour working on the adilas community funded project list. We had about 10 new projects that we added some small notes, budget info, and set the priorities. We will keep trying to stay up with this and keep it current.

Shannon and I did some more work on the adilas glossary. See this link for more info:

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=4030

4/29: This is a little more info: confirmed just like money type settings page. Only it would be simpler.

1)Review project, web page id, cascade to every other server. create a new page, everywhere there is a drop down for unit of measurement shown, need to fix. Code sign off.

Currently a user can add units of measurement and edit the ones they add. There have been a few requests to hide the units of measurement that aren't being used. I imagine this as similar to select money types, and perhaps it is housed on that page as well? Then users could keep just the uofm's that are relevant to their industry. There would be a page with boxes that could be checked or unchecked.

Or, another option could be more similar to categories, since the add/edit unit of measurement page resembles that one: https://data0.adilas.biz/top_secret/secure/add_edit_unit_of_measurement.cfm?mode=add&id=new

You could actually click next to the uofm and make inactive and then it wouldn't show up on the drop down list when creating a new item/editing an existing item.

Need to take a look internally. Will potentially tie to admin permissions. User needs options to pull data but perhaps not everything.

From Shari: "I think that Adilas needs to "grey" out that option:    Printable Holiday Patron (Customer/Client) List  if this particular User or any User for that matter doesn't have "Admin" Permissions in conjunction with Holiday Patron (Customer/Client)……...or maybe Adilas needs to make the "Printable Customer List" an even HIGHER Level Permission - maybe "Corp Admin", to ensure the confidentiality for not only Adilas but the Clients as well...…"

This might tie into mini conversions.  Selling each but assigning weighted value. Deeper than it seems.

Currently the parent 'cost' and the sub cost can be different. 

But they must share the same unit of measure, however mini conversions would allow each sub to be broken down into different UoM's 

This is mini conversions. srb

This client uses minimal parent items ie Blue Dream is the parent item for bulk, 1g shake, pre roll, 3.5, 7g. and 28 g. So 6 items. They designate the weights through sub attributes. This keeps minimal parent items and works well. Except, when they bring the items in- because they package them at one place, then bring them in. So, instead of being able to create one line item for Blue Dream with 6 subs underneath to represent the various weights, they have to bring in another line item for each weight, since the cost of each weight is different, and the cost must be identical to that of the parent.

Met with Chuck over a GoToMeeting session. Chuck is working on some dashboards for the campground industry. He is a graphics guy and we are trying a new approach. First we are doing some graphic mock-ups and then moving into dummy data with HTML and CSS (normal web interactions). Once we get it that far, we will move to full on backend development to make it come to life. Just playing with options. Good meeting. Currently, we are just passing the initial static graphic phase.

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.

Meeting with Bryan to push up some new code on the invoice sub inventory reports and exports. We made some changes, did some testing, and then did some more testing and light tweaking. Eventually, Bryan found a small error that fixed the issue. It was one misplaced if statement. Funny how small things can effect the whole. New code has been pushed up and tested. All is well.

Interesting conversation between Josh and Steve. The topic was dealing with project management and how quickly our developers can be highjacked by custom requests. Steve was recommending that we try to capture all of the custom requests out in the adilas community funded projects vs just having the clients go directly to the developers. There are pros and cons to that... If they go directly to the developer, they (our clients) get things quicker, but it has a hidden cost (called distraction and/or highjacking of resources). If they go through a channel, it has some different pros and cons. One, we could mix and blend and figure out project management, allowocations, budgets, and priorities. We could even match funds and do other things. On the flip side, sometimes, if it gets mixed in with all of the other projects, it may not get done quite as quickly. Pros and cons and each side. It is amazing how it comes back to a balance type dance.

Steve and I had some great conversations about our guys, our process, and where we want it to go. Another topic was dealing with returning and reporting and checking in. Sometimes we have huge projects and we don't get any communication for weeks on end. We are going to try to implement more regular communications. That should help everybody know what is what and where things are at. Funny how it goes back to forming, storming, norming, and performing (team building skills).

Eric joined the meeting and we setup some big blocks of time to work on the special accounts project next week. That is for customer loyalty points, rewards, gift cards, in-store credit, and other special payment or special accounts.

Shannon and I did a session on the adilas glossary verbage. We were working on rough descriptions and terms for A through D. See this link for the full glossary.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=4030

Shawn wasn't able to make it. So, I ended up doing some review on the adilas café project and re-reading a number of past entries that dealt with that project. Trying to formulate a plan and get a new adilas designer (graphics guy) up to speed on that project. I also had Eric pop into the GoToMeeting session and asked a couple of questions. Mostly a research session.

I merged in some code for Will and did some email follow-ups on questions dealing with the adilas label builder. Sent some emails out to Calvin with some questions.

Bryan and I met up and worked on a few code changes for the complex label builder. This page simulates a pre-set option for mini conversion. No real conversion take place, but it kicks out barcode and QR code labels that make it look like a mini conversion took place. The page allows for a single product batch to be split into smaller pieces. The magic behind this page is that it only splits things for the labels, it technically doesn't really split it, but according to the labels, it is split up. Anyways a few small changes.

We also talked briefly about a new merchant processing gateway and interfacing with Square as the gateway merchant processing option.

Had a great meeting with Jonathan. He reported on some of his findings. He met with Shannon and got a light tour and then did some additional research. We talked about some of his initial thoughts and feelings. He said that it was kinda overwhelming. Pretty normal. Once he got into it and kinda started to understand that you could virtually move around and look at things from different angles, it started to make more sense. We spent an hour and talked about three main concepts. We talked about the adilas café (new entry point for adilas users), the ice berg analogy (reskinning based on industry-specific needs and wants), and other adilas concepts (photo gallery of ideas). Good conversation and good ideas already starting to flow. I loved it. My goal was to transfer some vision and let him start exploring and playing around.

These are some outside links and pages that we went to for background.

A link to some of our plans for the adilas café - https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=adilas%20caf 

I'd like to get Jonathan started on working on the mock-ups for the adilas café and/or the adilas world and/or the adilas marketplace. They are all somewhat tied together. Future home and hub for the adilas community. We want people to come here to work, play, shop, sell their skills and their goods, and participate in different ways.

https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=ice%20berg - notes and research on the ice berg analogy of reskinning the adilas engine

https://data0.adilas.biz/adilas_for_business/photo_gallery_full.cfm - small concept photo gallery of core adilas concepts and direction

Recording notes, cleaning things up, and talking with developers on the phone about needed changes.

Steve can knock this out in the next week or so. (as of 9/3/19)

Per Steve- In order to make this list easier to sort and search.

Theme shows if your logged into the system.

Having challenges showing the snow owl theme. The top.cfm needs to be conditioned so 

if not logged in the theme will show.

Bryan had a question and needed some code merged in. When I joined the meeting, Steve was on there. We chatted for a bit and then he needed some help with some deep and dynamic JavaScript and custom math calculations. We worked on that and then I helped Bryan out for a little while. After we were done, Steve and I chatted and talked about some of our projects and direction. He has got a lot of neat things going. Lots of good things are happening. We are also seeing lots of great talent that we could tap into. That is huge.

Monday morning getting things up and going. Alan checked in on the morning meeting. He is working on 3 different projects right now. One deals with an invoice permission and limiting report data. Another deals with the invoice due date and header notification and billing project. The other one is a special sync with Metrc (state tracking system) and helping to show better and deeper details on synced data.

Wayne sent a few different emails dealing with new SSL's and new dedicated servers. The rest of the session was spent doing emails and light follow-up on other pieces and projects.

Steve texted me and said he was going to the computer store to get some thermal compound to work on his laptop.

Back working on the special accounts project. Eric and I have multiple blocks of time set aside to work on this project this week. We should get some good traction and progress. Steve and I connected and we worked on some of his JavaScript functions as well. We also touched base on a couple of other projects. He and I are going to be tag teaming on project list to get the projects assigned and on track. Good stuff.

Spent some good time working on the special accounts project. Got into some deep code on the add cart payment page (new JavaScript code) and more checks and calculations on the submit cart page. Making progress.

Eric, Steve, and I were on the morning meeting. Eric needed some code signed off. He also had some other questions. Steve was working on his own projects and I was working on my stuff. Lots of emails and what not. After awhile, Steve and I were chatting about progress and where things were headed. We talked about how certain companies really want some hand holding to help them make the jump and transition. We talked about some our efforts in that area.

As a funny side note, we were talking about how some people go through phases. The analogy of learning to snowboard was brought up. The first couple of days and first couple of times can be brutal. We talked getting people through the "this sucks" phase and how to help them keep stepping up. In snowboarding, if they get through the this sucks phase, they end up at the "this is pretty cool" phase. Then real progression can build from there. Sometimes software or software as a service (SaaS) is similar. There seems to be different phases that people need to go through in order to really catch on and buy in or see the possibilities and the vision.

Josh joined the meeting around 10 am. He is working on some consolidated big data reports for a client. This is a multiple corporation report with two years of rolling sales data on a single report. The report has show/hide and slide out type drawers with the data grouped per corporation per month per category. As Josh was showing Steve and I the report... we kept thinking about getting away from transactional data and getting more into data warehousing and aggregated data (pre summed up data per day, per location, per category). That would really help speed things up.

We looked at some other ways of speeding up the reports and even spent some time talking about master corporations and how a master corporation (world) could actually hold the consolidated data on a per location, per day, per category level. There might be some cool options there.

After that, Josh and I spent a good hour debugging one of the reports. We weren't getting very good error messages, so we had to keep moving a break point from top to bottom until we found the errors. Sometimes the debugging process is short and sweet and sometimes it takes hours to get to the bottom of the problem.

Shannon popped on and started working on formatting documents and past elements of time (adilas university stuff). She was waiting around for me, but I was still helping Josh with the debugging. We ended up chatting for a bit and then making sure that we have another appointment later this week. This session kinda got all used up but more good stuff to come.

11 - Financials & Accounting

-These are your numbers. As much as possible we let operations run and do their stuff and then we report back to accounting what happened. The numbers themselves are important but the story behind those numbers is potentially more important. For example $500 in a certain account does not mean anything unless you say it came from sales.

-Some programs focus on the numbers but one of our main goals is trying to zip up the difference between operations and accounting. The way we do that is using the system. It turns into a virtual data assembly line. We add data and if it is good data it flows through the system from check point to check point and builds your accounting and financial pieces.

-There is always a cause and effect relationship. Nothing just appears. Once again we go back to catching the story and then showing how that story unfolds as it goes forward and fills its own life cycle. 

11.1 - Bank Reconciliation

-You have monies going both in and out of a bank. Usually you know about it before the bank does. Outbound money is usually in some sort of expense or outbound payment. Inbound money usually comes from deposits, sales, investments, getting money from somewhere. 

-You record all of these transactions as they happen in the system - you pay a bill, you have a sales transaction - and that is its starting date, that starts an objects life cycle.

-The bank reconciliation portion of this is when does the bank recognize this transaction. When does the bank account for monies going in or out, being added or subtracted to the account.

-There are all kinds of times when there is a discrepancy when something actually happened and when the bank records it as happening. Some examples are you write a check, put it in the mail, and it takes a few days for the check to be cashed and monies to be withdrawn from your account. You make a deposit over the weekend and it sits through the weekend and a holiday until it is deposited into your account and the bank adds that. Someone purchases something using a credit card and those monies get combined with other credit card monies and those get batched and processed together and may take a couple of days to process with a fee reduction.

-There are all kinds of disconnects so bank reconciliation is putting a second date on the transactions so you can say when the transaction actually started or was implemented and the date that it actually becomes live in the bank.

-Often for bank reconciliation you will need both Adilas and your online banking or a printed bank statement in front of you so that you can match pieces up. If you are planning on going clear to a balance sheet level make sure that you have reconciled your bank before you ever try to balance your balance sheet. If you are going to balance your balance sheet the two pieces you want to ensure you have done before you start that are your bank reconciliation and your inventory reconciliation. Essentially making sure you have tracked things well and the needed information has been verified and accounted for.

11.2 - P&L - Income Statement (logic and flow)

-P&L stands for Profit & Loss Statement, it can also be called an Income Statement, it can also be referred to sometimes as the bottom line.

 -The Income Statement is fully automated. We pull reports from all of the known areas in the system that have the necessary numbers.

 -This particular report is time based so it usually has some sort of window of time - whether that is a day, a week, month, a fiscal year. Some sort of time range is associated with this report.

-There are 5 main sections of this report. They are Revenue, Cost of Goods Sold (COGS), Gross Profit, Expenses, and Net Profit. Three of those are actually areas that you can attribute values to, the other two are just math (gross profit and net profit).

 -The revenue portion usually includes invoice sales, labor, outsides monies not tied to invoices, commissions, refunds, sometimes there are also adjustments to revenue such as bad debt, credit card fees, etc.

 -This is the basic search form for generating an income statement or profit and loss statement (P&L). The actual report (results) will show up on a different printer friendly page. Use your back button to go back and forth between search criteria and results to get the amount of detail you need. You will need to re-submit the search form or refresh the results to get the actual values.

The only required fields are the to and from date range. The rest of the fields are optional or set to a system default. If you need more control over your reports, use the advanced link at the top of the page.

One of the most important search form values is the "Report Type" field (bottom most field). This is where you tell the results page how much detail to return. There are four different levels of detail the results page can display. Each one is progressively more expanded and categorized.

Below is a basic overview of the break-down of possible sections on the income statement (P&L) and how things are grouped. Each corporation and location are different. This is a general overview and may or may not reflect what you see on your income statement. Please understand that the income statement is a very dynamic report and is setup to only show sections that fit your search criteria.

The P&L is broken up into 5 main parts. They are:

Revenue (income or sales)
COGS (cost of goods sold)
Gross Profit (revenue minus cogs)
Expenses (money spent to do business)
Net Profit (gross profit minus expenses)

Here is a more detailed break-down of what each section contains.

Revenue

Invoice Sales - This is a sub section of revenue and is taken from invoices entered into the system. This section has a number of sub elements, taken from the invoice line items, that help provide a picture of what was invoiced or sold. All sub elements are grouped according to what we call inventory types. It starts with invoice sales that include specific units (stock numbers), then invoices with general inventory (parts), then invoices with system parts or special line items (labor, supplies, etc.). It is possible for a single invoice to show up (just the individual line items) in each section without creating a double booking. Basically, it is grouped invoice line items that show up for roll call.

Normal Deposit - This is a sub section of revenue and will show all deposit line items that have the deposit type of normal deposit and don't have an invoice number tied to it. Invoices carry more information than deposits and are encouraged (see above). Most of this information, if applicable, will be shown in the invoice sales section above. This section, if present, is a deposit catch-all and will show only items that are deposited but not tied to a specific invoice. This section should only be used for deposit line items that have somehow fallen through the cracks and are not shown above in the invoice section.

Other Revenue - This is a sub section of revenue and will only include special deposit line items that are assigned to a deposit type of other revenue (not from sales). This is the correct way to show revenue that is not tied to an invoice. Warning: It is possible that this deposit type may be double booked. The way to check, if present, is to drill-down and look for items that have an active invoice number tie-in. If yes, it is possible that the item is double booked (shown in the invoice section and in the other revenue section). If the line items do not have an invoice tie-in, you should be okay. Once again, this is the correct place to show other revenue that got deposited but is not on an invoice.

Revenue Adjustment - This is a sub section of revenue and deals with adjustments to invoice sales, bad debt, and certain deposit line items. If you do trade-ins, they will show up here as adjustments (ACV - allowance). ACV stands for actual cash value. If you want to write off "bad debt", all you need to do is satisfy the correct invoice with a payment and assign it to a money type of "bad debt". Once that is done, the invoice will be removed from the accounts receivable section (A/R's) and it will show up here in the revenue adjustments (just the bad debt portion). There is also a possible section that deals with special deposit line items that are assigned to the deposit type of revenue adjustments. These are things like credit card fees, etc.

COGS

COGS (Cost Of Goods Sold taken from invoice line items) - This section will follow a similar format to the invoice sales section described above. The top part, if present, will show the costs of the invoice line items from specific units (stock numbers), general inventory (parts), and system parts or special line items (labor, supplies, etc.).

Depending on corp-wide settings, it is possible to have certain special line items (system parts or hard-coded values) show up as a negative cost of good sold. This is somewhat rare, but an option from the corp-wide settings page. This might be things like freight or shipping charges.

COGS (special expense type category) - There is also a sub section for special expense types that are pointed to the COGS section. Most normal expense types (expense/receipt line items) show up under the main expense section (below gross profit). However, the system allows for expense types to be pointed up here in the COGS section if needed. Basically, this is a way to increase the COGS before gross profit is calculated. Somewhat of an advanced option.

Gross Profit

Gross Profit - Revenue (plus or minus any adjustments) minus COGS. This is calculated for you.

Expenses

Expenses - These are normal expenses that are taken out after gross profit is figured. Almost all expenses, values, and categories come from expense/receipt line items and the associated expense types that are assigned. The one exception to that rule is if your corporation sets up special roll call/handling for special line items (done through corp-wide settings). These are hard-coded parts and by default are assigned to the revenue portion of the P&L. Without making a big deal about it, these are invoice line items that get special treatment and have been told to show up under expenses as a negative expense (somewhat of an advanced setting). Most corporations will get their expenses directly from the expense/receipt line items.

Net Profit

Net Profit - Gross Profit minus Expenses. This value is calculated for you. This value is also passed on to the balance sheet as part of the equity account. This is how the income statement or P&L play into the actual balance sheet.

Estimated Taxes & Depreciation - Optional line item that shows taxes and depreciation. Set at 45% of net. Once this is taken out, a new adjusted net will be shown.

 -https://data0.adilas.biz/top_secret/help.cfm?id=192&pwd=income

11.3 - Balance Sheet (logic and flow)

-The balance sheet is a financial document that is very commonly used for high level financials, I.e. banks loans, investors, taxes, etc. The balance sheet has 3 main categories that the details get divided into. They are assets, liability, and equity accounts. Sometimes people will use the acronym “ALE” to quickly remember those 3 categories.

-Assets are things that you own. Monies in the bank, inventory on hand, and other things that have a significant value that you need to track. It could also include monies owed to you for good and services previously invoices (accounts receivables). There are chapters and chapters of all the things that could possibly be assets, this is just a quick list for an idea.

-Liabilities are things that you still owe or may owe on. This could be things like loans, taxes, coupons, loyalty points, gift cards that you have already collected on, accounts payable, bills that are still due, etc. Once again this is just a short list to give a general idea.

-Equity or owner’s equity is more of earnings over time, investments, your net profit that comes from your P&L, distributions, all kinds of long term holding accounts. Equity usually derives some sort of value that has accumulated over time.

-The balance sheet is a "Snap Shot" in time and only applies to a single day. Basically, it is a roll call of who was where and what happened at that exact time (according to the system).

-Both the income statement (P&L or profit and loss statement) and the balance sheet usually end up being quite in-depth in real life and may contain multiple layers in order to tell the real story of what is going on or what has been done.

-The P&L is a time based report of buying and selling and basic operating expenses. By time based we mean that there is a date range associated with it. It could be a day, a week, a month, a quarter, a fiscal year, etc.

-The connection between the two is what is called the "Net Profit" or "Bottom Line". This value is first figured on the P&L and then passed to the equity portion of the balance sheet. The ending date range on the P&L is the balance sheet look-back date or balance sheet date.

-One of the hardest things for people to figure out is what goes on the income statement and what goes one the balance sheet. There are chapters and chapters that cover the in and outs of both reports. For basic purposes, the P&L is the day to day buying and selling of items and services. It also includes basic expenses that are required to run your business. The balance sheet deals more with who owes who, and how things get classified or grouped. Do we own it (or trying to own it), these are the assets. Do we owe for it (or trying to pay for it), these are the liabilities. The last piece of the puzzle is the equity or distribution of wealth (who are the players and what is their piece of the pie).

11.4 - User-Maintained Balance Sheet Items

-Balance sheet items come in a couple different flavors. You can have both system maintained and user maintained balance sheet items.

-You can have a system maintained balance sheet item. These are things that we can get to and track from the system. For instance running bank account balances, accounts receivable, accounts payable, on hand inventory levels, net profit. We know how all of these show up and we can gather these from the system and automate them onto the balance sheet.

-A user-maintained balance sheet item is something special that the corporation/entity needs to track but the system does not track it automatically. Thus, it is called "user-maintained" and means that all values, subs, line items, and calculations are the responsibility of the users (you and your team). User maintained balance sheet item could be any of the categories or types that are found within a balance sheet - assets, liability, or equity. 

-As far as what the user maintained balance sheet item records as its value there are three possible values to use for user-maintained items. They are the assigned item value, the running value (starting amount plus sum of the line items), and the difference (assigned value minus running).

-These user maintained balance sheet items are special and have a number of options including photo management, sub line items (tie-ins to deposits, invoices, PO's, expense/receipts, and other user-maintained balance sheet items), special math calculations, and their own details page. 

11.5 - Adilas Theory on Accounting

-Before we go into this next section it is worth expressing that there are multiple different views on this accounting piece. As different as religion and politics are, some people have similar opinions and beliefs on how accounting should be done. We are not trying to start a fight or offend anyone and we value all of the different avenues.

 -Basically we feel like accounting is the end result of cause and effect relationships and how they show up. So our goal is to gather information and data as it starts and let it flow if the data is okay. If a change is needed, we make the change, record a checkpoint or make the correction, and then let that data flow. So accounting really does become a sum of the details. In life, most things do not just appear. There is a story or a reason.

-When we first started building Adilas we saw that there was a known gap between what is called “Operations”(day to day activities) and “Accounting” (the financials and final numbers). One of the analogies that Steve Berkenkotter came up with was a zipper where you have operations on one side and accounting on the other side. “Our goal was to bring operations and accounting together one cog at a time, like a zipper being pulled upwards until it comes together.”

-As we got into it and had been exploring we found that you often need to let operations lead, that is a huge key. Already some people might be saying no, stop this is the wrong direction for accounting but this is a critical key in how we approach the topic. Using another analogy, imagine a horse and a cart. Which one needs to come first? The horse, to pull the cart. Your horse is operations and your accounting is the cart. Natural consequences of a users action present the next logical step. This is known as accounting or accountability. Let operations lead and the accounting will automatically follow.

 -For those who are really worried that is a bad idea, accounting can still have the reigns and reign things in the horse/cart analogy. But in the end the cart has to go where the horse goes if they are connected to it and really want true accounting.

-Without going into details it may be important to say that accounting would not have anything to account for if there were not daily operations occurring in one way or another. Once again we feel that accounting is the sum of the details.

 -Another analogy on how we track things is similar to a process of water turning into ice. The water droplets are very loose at first (like operations), and slowly become crystals, then slush, and finally becoming completely frozen or ice (final numbers or accounting). Throughout the process we flag and date key check points of the life-cycle or steps in the process. This becomes a built-in history of what was going on at any given point in time.

 -Imagine the concept of a data assembly line. You basically run all actions and activities through both space and time while monitoring resources to get a 3D model of where things are really at. Digital story telling.

https://data0.adilas.biz/top_secret/help.cfm?id=496&pwd=assembly

-The 3D model contains 3 dimensions, the x axis is time (horizontal), the y axis is monies & resources (vertical), and the z axis is space or depth (how deep are you going within that).  

https://data0.adilas.biz/top_secret/help.cfm?id=483&pwd=building

11.6 - Roll Call Accounting Principles

-Roll Call Accounting is the ability to track objects and data over time using a series of dates and flags. Imagine the web server or computer asking the objects and data to return and report. What's your story? Who created you? Where have you been? Where are you headed? Who are your buddies? Where do you belong? When did you finish? etc, etc, etc. Virtually require each piece of data to hold its own luggage.

-The concept of a roll call is what you learn back in kindergarten/first grade when the teacher is asking, “Where is Johnny?” or “Is so & so here?”. So basically what we do is track the life cycle of data. All data has a life-cycle and goes through different processes in that life-cycle. The roll call comes into play by asking the data questions such as where the data was at a given time, where it is now, who touched it or performed certain actions, etc.

-There are 3 main groups of history tracked in Adilas: Effectual – what shows up for roll call (where is an object at, with date & time stamps), Historical – who touched what (actions/histories), & Financial – what & where does this show up on the financials.

-We have determined that there are 12 main players in the system. Some of the roll call is talking to those individual players or groups and asking them questions based off of the state or status they are in, what point in their life-cycle they are at, where they need to go next, etc. That might sound random to keep it that broad, but each individual player performs certain tasks. Many of those tasks can be mapped directly back to the financials such as sales, quantity - inventory tracking, expenses, COGS, payroll, taxes, etc. Everything has a date/time stamp along with what phase or step it is in. We simply map to that. That is roll call accounting.

-Here is a small example. Let’s say a customer comes in and wants to buy something. Before the sale happens your product is in inventory and no monies are owed by that person. Once the sale is complete we now have a reduction in inventory, we have new sales money that either needs to be deposited or is still owed based on payments made. We have a tax liability, we have COGS, and we know a profit that was made. All of those pieces can be mapped back to physical spots on the P&L or balance sheet. The important part is progressing that data through the data assembly process where you are flagging, dating, stamping, etc. The data if it’s ran through the assembly line process actually allows us to do the roll call accounting.

-A huge part of the roll call accounting piece deals with allowing your data to flex. Disclaimer: certain accounting people may start freaking out at this point but if you don’t allow your data to flex or go into virtual waiting spots while the data is waiting for some of its other pieces you have to do all sorts of adjustments to keep everything picture perfect. Our concept is that things often flex. We hold them in that flex state until they can pass that next checkpoint which is where they are flagged, stamped, and then can get passed on to the next step.

-Some people say, “Okay I see how that can happen once”, meaning a flex point,  but what we see is that it happens over and over and over again. This is why we treat it like the data assembly line. Some data might go through 3, 4, or multiple steps until it has completed its entire life-cycle. But if there is any data that has an issue or has a need to allow for time to pass before completing its life-cycle it needs to stay in that flex zone until it is ready to be advanced. This could be waiting for another process to happen to the data, another person to perform a certain task with the data, waiting for something to happen physically before the data can be advanced, etc. There are endless scenarios that cause this circumstance where the data needs to flex or get held in a waiting area of sorts before it is ready to progress down the data assembly line.

-The link below is an entry from 2014 where we were expanding our vision of how we have seen things start rolling in this roll call/data assembly line type concept. The entry shows a number of small drawings as well as information. If you are interested in this concept it might be a fun read for you. https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=2894

-Here is some additional content on roll call accounting.

https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=roll%20call

11.7 - Old School Accounting vs. New School Accounting

-Similar to a movie that says the views and opinions expressed here are those of the authors and creators and do not necessarily reflect traditional views on accounting. We acknowledge that this could be a very controversial topic and do not mean to make any sort of inference or offense. Having said that we are trying to stir the pot a little and challenge tradition.

OLD SCHOOL ACCOUNTING

-Old school accounting, or traditional accounting, or double entry accounting, are some terms that are used to talk about classic ways of keeping books. Books meaning a company’s financials. Interestingly enough, originally things really were kept in books or notebooks. These are often referred to as journals and ledgers.  

-By way of a little history a couple of very important events happened. The father of accounting is a guy by the name of Luca Pacioli. He was an Italian monk that lived at the same period of time as Leonardo DaVinci. He is credited as the father of accounting due to a textbook he published called, "Summa de Arithmetica" (the summation of arithmetic). Here is the kicker, this book was published in 1494. To put this date in perspective, Columbus sailed the ocean blue in 1492. Many of the modern day accounting systems have just digitized and sped up these 500+ year old concepts. This is potentially why we would call it old school accounting. 

-Going way back, before computers, company’s would keep track of their records on paper. The word “paper trail”goes back to this method of accounting. In order to keep things separated and organized they put things into accounts or T-accounts. A T-account was almost like a miniature bank balance which you could add to it or take away from it so that you could know the balance in that account. These pluses and minuses are called credits and debits. Normally a credit is a plus and a debit is a minus, there are some exceptions.  

-These processes may be different per company but this is a general overview. A company would have something that they wanted to track. Often this was something that was either important to the company or something the government said they had to track due to taxes. Where they would start is to create a list of categories that they called a chart of accounts. Each category or piece that they were going to track got a number. These numbers have all sorts of levels and specific categories that have been defined over time. There are certain numbers for cash, accounts receivable, accounts payable, long-term loans, etc.

-A journal entry was a debit or credit to one of these chart of accounts. This is where your T-account comes in, meaning credits on one side of the T and debits on the other. These journal entries are the small transactions or day by day activity. The sum of these journal entries would then be passed on to a more stable spot called a ledger. Back in the day, depending on the time period between things, the journal entries would be kept daily or as often as they could. When the time period came that they wanted to get the totals, they then summed up those totals and put them into the ledgers. This helped them save space and kept the ledgers clean so that they weren’t showing all the daily ups and downs and fluidity of business. Often these final posts to the ledger were done weekly, monthly , quarterly, annually, or some other period of time. This is where the word post comes into accounting - moving from a general journal to a ledger - aka summing things up and stamping it into the more final record.

-As part of the journal entry system businesses would do what is called double entry, meaning if something happened it may have effected more than one account. Technically this is how they were tracking cause and effects. For example if I got some new monies from a sale I would have to record those monies coming in and the other side of that would be that I got to deposit that money and my bank account increased. Some of these double entries can get very deep.

-To help businesses keep track of their financials there have been some helpful documents or reports created that we still use today. These reports helped them to know the vitality of the business. These are things like cash flow statement, income statement (P&L or Profit & Loss), balance sheet, etc. These documents are wonderful tools that were created. Most business owners will recognize these names as standard financial documents. Business owners use these documents to get business loans, submit taxes, track business operations, buy and sell businesses, make business decisions, receive other financial reports/requests, etc.   

-There are a number of other things that are associated with old school accounting or traditional double entry accounting. There are chapters upon chapters and textbooks upon textbooks that go over all of the ins and outs of double entry accounting. In general, most of the existing accounting software packages literally emulate the same 500+ year old accounting concepts and flow. They use the same names, the same flow, same mentality, it is just digitized and has some technology enhancements that help it to go faster but it is based on the traditional accounting practices. We may address some of these traditional accounting aspects further as we discuss new school accounting.

NEW SCHOOL ACCOUTING

-New school accounting, roll call accounting, time stamp accounting, tracking objects and data over time, data assembly line, world building, these are all some terms that could be used for modern and/or progressive ways of tracking your data and doing your books. As a note, some of the terms and concepts that exist in old school accounting will be mimicked or copied in new school accounting but some of the names have been changed. This is really important because if you keep some of the traditional names, people expect it to follow the same process as the traditional method does.  

-In old school accounting we added a history section that showed sort of where things came from. Before we jump into new school accounting we feel like it is important that you have an idea where some of these things came from before we start right into ideas and concepts. Right up front we didn’t set out to make a new accounting system. Our business problems were all on the operations, day to day tracking, side of the equation. If you would like a story type format here is a great document below that tells the unfolding of what happened with Adilas.

https://data0.adilas.biz/adilas_history_bio.pdf - (Tons of fun concepts as they developed. This document shows lots of the problems we encountered as a business and how our solutions evolved into the Adilas system.)

-As humans we love to use tools because they help us accomplish our tasks more efficiently. In old school accounting some of the tools used at its roots go clear back to paper and pencil, which are some great tools. Each tool has pros and cons and at some point if the task keeps evolving it can break the efficiency of the tool being used. (If you are interested in seeing a fun document exploring tools and where they excel and break click here.) 

-All data actually has a life cycle, meaning it gets started or created and ends and/or finishes. Usually that means that there is some sort of time frame between these different phases or stages in how data fulfills it’s life-cycle. In our quest for tracking things we started on the operations side. We really wanted to see where every penny went from beginning to end. The missing pieces for our business were on the operations side of tracking inventories, selling inventories, counting inventories, building new things, etc., etc. Basically we needed to get more details on what was happening in the day to day transactions and activities. Step 1 is catch the data at the source.

-As you try to catch data at, or from, the source you have to have tools in the hands of those who are doing it to allow them to capture the data. This can be a problem due to technologies, permissions, or trust issues between departments and employees. As part of this discussion we need to acknowledge that there is a known gap between operations and accounting. Operations, or sometimes the sales department, tries to make things happen to make the deals go. Sometimes accounting doesn’t like all of the decisions made by the operations department and/or doesn’t want to give all of the control for decisions to the operations department. This is where permissions come in. A permission is basically a thumbs up or a thumbs down on being able to add, edit, delete, modify, and so on to all kinds of elements. 

-At this point we want to introduce a few analogies. One of them deals with this life cycle of data. What we want to introduce is the idea of water becoming more solid or the process of water freezing into ice. At first when the water is very flexible this is like the sales - things are still happening and moving, deals might still be in process and negotiation, promises may be being made potentially on both sides of the equation. As the deals solidifies it is almost like that liquid water starts becoming snow or slush. At this point we now have fixed numbers, maybe we have monies, a transaction could have been completed, or we need to further build or fulfill something.  As the time goes on those values, numbers, monies, product transactions, and data become more firm and stable like ice. They become fixed and a piece of the history. We call this analogy the water, snow, to ice analogy. 

-The next analogy we want to introduce is a cart and a horse analogy. We propose that the horse is the thing that is moving things along which is your operation or sales side of the equation. If you don't sell anything you don't have anything to account for.  WORKING....

-The other analogy is the data assembly line

-WORKING, CONCPETS, IDEAS:

-Comparison between operations and accounting with static, parallel, perfect lines - everything is perfectly static.

-How we actually need flex bubbles and periods of time/waiting, etc.

-Difference between operations and accounting and the gap between those. Batches, things get batched, missing time, lack of communication, non-centralized data,

-Horse & cart analogy

-3D data assembly line and 3D world building models

4:17 PM

Brandon Moore

/// notes from the adilas history bio

- corps, locations, users, permissions

- web-based

- tools >> head, paper/pencil, computer tools, software, database, web solutions

- Internet came into play mid 90's

- gathering information into a centeral location

- limiting duplicate work - collecting data and allowing it to flow (start a process)

- start with your pain points

- enter once, use many, and empower the users at the point of action

- letting operations lead

- with the right tools, productivity increased and sales increased, and that drove the need for better accounting

- pain - load and stress

- zipper analogy and using the system as the common element (even the bad guy - saying no)

- permissions and opening and closing virtual windows

- solving problems and then going to the next logical step - keep solving bigger and bigger problems (cogs of the zipper)

- one-to-many relationship model

- dreaming up a super system (what if we could do this... or that... or maybe both...)

4:17 PM

Brandon Moore

- maybe grab the paragraph about no road maps and we were just going off of ideas, concepts, and needs... shannon liked that section.

- we are still doing the same things today as we were back then. where is the pain and how can we possibly fix that (more zipper cogs coming together).

-From here maybe start looking at the post-it note list and see if we can transition into some of those other pieces. We’d like to describe that there is gap, horse/cart, time, batching - and just how this gap keeps getting wider and wider with the real time effects of these things, using computers and technology to create logic that can perform these accounting operations (conversation with Brandon & Steve --- WORKING….  

-IDEAS: We are going to start defining terms, concepts, start typing up pieces and ideas and we will probably need to come back and sew it all together, smooth things out, and make transitions.

-Another Note: On 6/25/19 as Brandon and Steve were talking Steve was saying how old school accounting used to have post after post and entries and different journal entires - lots of time and inputs, whereas roll call accounting can use technology to create logic and teach the computer to look for certain patterns and use logic to map to what is actually happening. Because it uses the logic and mapping, it can do that process over and over again and allows the data to flow more on its own, it just tracks where everything is at and puts numbers where they need to go. Computers are really good at doing repetitive tasks.

-Ideas/Concepts from History Bio Article:

These concepts are enter once, use many, and empower the users at the point of action.

The entire development process was as follows: 1. Find a specific need 2. Figure out what pieces came from where 3. Take a step in that direction by releasing a new tool, feature, or report. The natural consequence of the user actions would then present the next logical step and management would be able to see where they wanted to go. In a way, the horse began leading the cart instead of the other way around.

-If you would like some additional research from the developer’s notebook on new school accounting look here.  https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=new%20school

-Some entries from the developer’s notebook on Christopher Columbus and Lucas Pacioli. Christopher Columbus - 1492 sailed the ocean blue. Luca Pacioli - the father of accounting - in 1494 published a work on the double-entry system of book-keeping and accounting called "Summa de Arithmetica".

https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=columbus%2Bpacioli

-This is a 6 page document that has a publish date of 2011 and deals with the start of the Adilas system. It discusses where Adilas came from and how we even started on this journey. Lots of fun concepts of roll call accounting and tracking objects and data over time.

https://data0.adilas.biz/adilas_history_bio.pdf

-The link below is a photo gallery but has some interesting accounting concepts to check out especially in the second picture.

https://data0.adilas.biz/adilas_for_business/photo_gallery_full.cfm 

11.8 - Vision for the Future 

BRANDON’S POST-IT NOTES

-Some of these are terms and some are concepts:

-Debits & Credits, Chart of Accounts, T-Accounts, journals, ledgers, reconciliation, posting, adjustments, batching, Carts/Horses

-Time, gaps, batching, delayed reporting, super detailed (searching for pennies) - but plugging huge numbers, adjustments, power and control, process of discovery, changing names, user report requests, hand written tickets, separate systems, double and triple manual entry, shipping and batching, different locations and departments, cycle time, centralized location for the data, real time connections from the source, enter once - use many, empower the users at the point of action, catching the details on the operations side, communications, problems (stress and load), specific dates, data and totals, minimal cross over, the commonality becomes the system, make the system the bad guy, open and close virtual doors, permissions, real time problems and solutions, operations feeding accounting, seeing both sides, cause and effect cycles, next logical steps, maintenance and upkeep, one to many relationships, cogs of a zipper, the gap, taking data from day to day tasks and having them show up for roll call or the accounting side, tracking life cycles, tracking every penny from start to end, water droplets forming into ice crystals, key dates and status changes are flagged, permissions locks, objects and data over time, the forming need, providing feedback and ideas, find a hole or problem and try to fix it, community effort, training, opening doors and options, changes over time, legacy changes and dealing with old code and legacy code, advancing needs, advancing technology, unfolding needs, learn as you go, can’t stop operations and make changes and then say go, expanding user requests, details and histories, drunk on data,

-WORKING

-Notes from reading:

Steve and I were working on some complex JavaScript and doing some testing and debugging. This particular script had a mix of dynamic data, lists, arrays, objects, and mixing both Adobe ColdFusion (backend data) and frontend JavaScript. To make it more complex, there were three modes that the page could be in... They were single item, category of items (plural items per category), and recipe/builds (plural items from a preset recipe). Lots of variables. Anyways, we got it going really good and making tons of progress on it. We got stumped and decided to break for lunch.

Eric and I were supposed to be working on special accounts (rewards and customer loyalty points) from 1 to 3 pm. We ended up getting denied due to time. We started this session at 2 pm and then went for an hour. We did get some code merged in that Eric was working on for a 3rd party solution API socket call. We will hit the special accounts project again tomorrow. We had time planned each day this week to push on that project. It didn't happen today due to other random tasks and such.

Steve and I had another multiple hour session working on his advanced JavaScript. We got that whole thing done and tested pretty deeply. It was good to take a break and then come back and hit it again while everything was fresh. Both of us feel good about what it does and how it works. Good stuff.

Part way through the session, Shari O. came over to Steve's house and chatted with us over the GoToMeeting session. She gave us a report on her health and we had some good laughs. After that, Steve and I looked briefly at our adilas to do list (aka adilas community funded projects). We mostly focused on the priority 1 projects. We then got out a text document and started working through our people (adilas team members) and who was doing what list. We made some notes and talked about a few projects and where things were at. Steve and I will be doing more and more of this to help things keep going and advancing. That is exciting.

Spent some time recording some notes and getting caught up for the day. Busy day today.

Pretty quiet morning meeting. Dustin checked in and gave me a report on what he was working on. Eric checked in with a question or two. I merged in some code for Will. Wayne is conditioning some new servers and we had a few emails back and forth. I did more emails, paid bills, and got signed up for some classes at the Adobe ColdFusion user conference in October. Light research on some of the topics that will be covered.

Working on the view cart, printable cart, review cart, and submit cart pages for special accounts (rewards and custom loyalty point stuff).

Bryan jumped on and had a couple of questions about some custom drop-down menus. We looked at them and flipped some sort values and that should help them. One of the drop-down menus was connected and/or coupled with a prior query. We separated it and made it its own entity. That fixed the problem with that one. Other small tweaks.

Working with Calvin on a custom database project for data 9. He issued me 6 new MySQL Editor licenses to use on different servers. The MySQL Editor is a custom database program (database tool) that Calvin created for us here at Adilas. It is lightening fast and simplified. The project that he is working on involves a client wanting more raw access to the database vs going through the established channels in the Adilas.biz system. This is a dedicated box and the raw data is going to be a view only access type app. All changes will need to go through existing and established channels. It is interesting how much people want access to their data and also want to run certain queries to pick out trends, stats, and other details. Kinda cool. Data is becoming a new kind of currency.

Back working on the special accounts project.

On the morning meeting with the guys. I got on late. They (Steve and Dustin) were talking about some recent hiking trips into the high country. After that, Eric popped in and needed some code merged in and pushed up to all servers. We got that done and then Steve, Eric, and I started talking about the special accounts and how close we are on the first round. The first round should be up and live by the end of next week. Here are some of our notes, related to that topic.

- The value of the loyalty points - do we calculate at the time of earning or at the time of redemption? Those values may be different.

- What about showing them (special accounts) on invoices or after the fact? Settings and configuration options.

- What about going back in time and trying to figure out dollar/point ratios and values... going backwards gets a little bit tricky. History, financials, and audit trail stuff.

- Histories and drill-downs to activity on these special accounts (big need). Maybe being able to search (quick search style) on special accounts. How do we get to the underlying details quickly? What is the story behind the numbers.

- We are seeing more and more possible settings and configurations for each section and/or type.

- Steve was talking about ecommerce. That may end up being another avenue for some of these special account types (say gift cards, earning loyalty points, etc.).

- We are seeing lots of other needs for these payment type solutions and tracking these sub special account totals, histories, and/or transactions. We are also seeing a mix between both internal (adilas) solutions and external (3rd party payment solutions) accounts of different types. All of them need the special account type mentality and/or flow (mini bank accounts that could be added to and/or subtracted from).

- We are seeing so many different point of sale systems (different POS's and POS competition) out there. We are hoping that some of these outside companies will decide to integrate with us and then help push our product forward. Choose your solution and then invest in that solution. Play the piggy back type scenario.

- One-off's vs core functions and features

- Light talks about barriers to entry and barriers to exiting. The deeper they get (meaning our clients or outside 3rd parties), the more they have virtually bought into the meat of the product and it makes it harder to leave (barriers to exit).

- Steve is seeing a trend where clients are wanting a single solution that does what they need and is highly configurable. We are trying to be that type of solution.

- Beta testing and allowing certain users and clients to jump in on things before a bigger release. We need people to push on things before it goes completely live and full speed.

- Possible problem with bulk loyalty points. We have tons of old custom points vs new automated points. We may need a small bulk migration tool or something like that... this may also be a special custom page that looks at existing logic and then adds new transactions (into the sub special accounts tables) to get the starting balances in place.

Work session with Shannon on the online adilas glossary of terms. We were working on E, F, and G items today.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=4030 - click to see the progress of the glossary

This is somewhat of a clean-up project for older stock/units (serialized inventory). We used to push stock/unit and parts (general items) out to the old Morning Star server for ecommerce and basic web presents. All of the new servers are able to handle this customer web traffic directly from their own servers vs pushing the data out to an outside server. This project would be a code clean-up and virtually stopping the transfer of limited data out to the old web presence site. This is a legacy issue and could be cleaned up internally without much problem.

Limited data is being passed to reconstruct the main data. Known areas are: corporations, basic user info (salesperson names and phone numbers), locations, part categories, makes, models, stock/units, parts and general inventory.

Search for "cfinvoke webservice" or "useBackUpWebServiceAddress" in the code to find pages that did this limited data transfer.

Also, on a side note, we are being charged for this older server. If we remove all data calls to this server, we could get rid of it. That could save almost $1,000 a year.

There may be a few phone calls to some of the older clients to let them know that they have to change their web sites and links out to the older data. Light customer care and clean-up.

12/23/20 - The code clean-up portion of this project was finished today by Brandon. We still need to turn off the domain name and close that account.

Working on code sign-off for the submit cart page and the customer loyalty points and special account stuff.

Bryan joined the meeting and had a few questions. One was about a new money type called "credit card" - basically a generic for all types of credit cards (visa, mastercard, American express, discover, etc.). We talked about how easy it is to add the money type and then how much work it would be to make it flow through the whole system. We estimated a little bit over 10 hours for the project.

We also talked about Full Circle and how to help re-do some of the settings and permissions.

Later on, Calvin called and updated me on some developments with dedicated clients and their want to get at underlying data and the databases on their boxes.

Steve, Jonathan, and I were on a meeting. The meeting topic was the adilas café and some ideas around that subject.

- Where operations and accounting meet

- Launch adilas (aka go to work) - maybe show the top couple corps that they frequent

- Play in a demo site

- Get some training

- Hire a consultant

- Advertise my services

- Advertise my products

- Join our community

- Vote for next features

- See what's in the pipe

- Show stats - personal and over arching (full adilas community)

- Steve would like to keep adilas all lowercase (just for branding)

- The ultimate sophistication is simplicity - DaVinci

- We are looking for a style (the new look and feel)

- Talking about snow owl theme settings, logos, watermarks, and basic styles - talking about customization and even customization with some elements of control (not too much power, but enough). Templates and being able to help people make decisions quickly and keep some virtual rails on the platform.

- Jonathan wants to learn more about the software (web platform) and how our customers are using our product.

- Helping our users and clients interact better - create a single entry environment

- Ratings, communities, money transfers, commerce, skills, and exposing hidden treasures that already exist

- Power users becoming mentors

- Being able to both add and subtract from the visual of what is showing

- MVP (minimum viable product) - the smallest usable piece and then build from there

- Single login, give you access to the adilas café. Maybe show the last corps, top 3 or top 10 corps, etc.

- Maybe bring in the adilas doggie as part of what is available

- Looking for patterns and how people use the product

- Older link to some top level training - https://data0.adilas.biz/training/

- The cart and the shopping cart are the main heart of the application. So many transactions and cause and effect relationships get pumped through there. A vital piece of the puzzle.

There are a number of screenshots attached for some visuals of what we were talking about. Good meeting.

Clean-up, recording notes, emails, and recording expenses and bills.