Working with Shannon. I was showing Shannon my notes from the past week. One of the entries had some notes and my spiritual experience (planning and brainstorming on training the AI agent). See element of time # 12527 in the shop for more details. Going over the power of the plan - reinforce, recruit, and then share it. It feels like a mini parallel to God's master plan. Another part of it deals with helping adilas get ready to go out to the world and be a tool that could be used.

We spent some time going over concepts and showing her what the context window was (concept) and how to help make it function at the appropriate level. She then helped me as we talked about using the CMS tables on adilas university to create and make the global context records. CMS stands for content management systems. All of adilas is basically a giant CMS type application. We will use our media/content database table for those global context pieces to help train the AI agent and our users. It is perfect, it already exists, and has been being used since 2013. We will just repurpose a small portion and use it more heavily from within the adilas university site and corporation.

Switched over to working on the white label section on the fracture (deeper development and system code) build out. We finished up that section. Yeah! After the meeting, I sent Steve a text about using the media/content database table as a CMS system for adilas university and global context stuff. That will be super cool, and it is already done and functional. What a blessing.

Meeting with Greg from the Calder Group. We did some catching up, chatting, and shooting the bull. We then talked about some of the new happenings inside of adilas. Greg wanted to hear a little bit about our story... we had fun going back and forth. Greg did a bunch of accounting in school. We chatted about that and how things have changed and progressed over time. I also briefly talked about some history inside of adilas and how things grew and became to be. I sent him the link for the adilas lite (fracture) master plan. Good meeting.

Working with Shannon. We spent the whole time working on the fracture plan about lessons learned from doing 20+ years of work on this project. Shannon and I were drawing a bunch, going over concepts, and brainstorming on what we want things to look like. After our meeting, I did a little bit of research and read some of the other content that we have been working on. On the lessons learned section, we didn't quite finish up, but this is what we were coming up with... content to this point.

One of our most encouraging lessons is that we are successfully creating an application that we've dreamed up and worked for. It is totally possible. We are systemizing business functions into an integrated platform that other companies have been separating into multiple different applications. We have been doing this on a garage budget, with limited resources, for 20+ years.

We have built up this application by prototyping features and functions to meet various needs. Many of these needs and wants have come directly from client input and requests. To summarize what we mean by prototyping, our process starts by determining a want or a need. Then we do research and brainstorming and figure out the plan. This could include trying to use new techniques or doing things that would further the product along. Where possible, we tend towards permissions, settings, and templates. Then we build it out and let others use it. They beat it up, and we make any revisions that are needed. Once it is being used and our clients are loving it, they often let us know what they want for the next steps. This pattern has occurred over and over again. This prototyping process has allowed us to build out the entire adilas application over the years. The result of this is a robust, revenue producing, and versatile system that is meeting the needs of our clients.

Our approach going forward is to continue following this pattern. If we do receive more funding, we will adjust our approach accordingly. This may include building out a more detailed master plan, using teams, hiring specialists, and other development techniques. If no additional funds are available, we will keep dreaming up new ideas, doing research, experimenting, prototyping, building, and moving on. This is what we do! If you want to see an overarching view of our master plan, please see the value add-on core section.

With 20+ years of experience, there is no way that we could fully put into words all of the lessons learned. However, we have documented the whole process through a section that we call the "developer's notebook". This notebook has been a running log of ideas, concepts, lessons learned, and other notes that we have collected over the years. It has been a great resource for us to refer back to as we continue to build and improve adilas. Just as a sample, if you go to that page and type in the word "fracture", you will see a number of notes and ideas that we have collected over the years that relate to this new buildout. There are over 200+ entries just on that subject alone. If you want to checkout the developer's notebook, you can find it here: Developer's Notebook by month and year or search the developer's notebook by any subject, use this link and associated form.

Working with Shannon. Going over new changes. Looking around in the Nxtlinq backend application (AI agent backend dashboard). It looks like we can edit things and upload documents now. That will be awesome. I haven't played with it yet, but good to see progress. That should help us with training it and helping certain pieces of global context to stick and be available to all users.

Shannon and I then went into our work on the fracture (adilas lite) plan. We were working on the section about lessons learned over time. We are wanting to show that we have listened to clients, done tons of prototyping, and are actively building out the master plan. We have captured tons of this process in the developer's notebook and are excited to really put the whole master plan together and go from there. We truly have experimented and prototyped numerous pieces of what we plan on doing for the whole fracture project. That is super cool.

Working with Shannon. We stated out the session talking about building on what we have and filling in the gaps. We talked about building bridges vs building walls (one lets people in and the other keeps people out).

We talked about API's, sockets, endpoints, and how all these things play and flow together. I was drawing up a storm. We spent a bunch of time looking at some graphics in the teaching gallery and then drawing on top of those graphics. We then flipped over to work on content in the adilas lite and fracture plans. We were working in the API socket section of that page. So many potential benefits and ways to use it. One of my big takeaways was how this could tie-in to the value add-on core model. We, adilas, create the master road map for our product that is called the value add-on core. Adilas is going to build out the main transactional core (level 1 of 5). Any other level could be built out and/or added to with the API. We can't even fathom all of the possibilities. If you want more information about the value add-on core and all of the levels of the master plan, please see that section. Here is a quick overview of the adilas value add-on core model...

Level 1 - Adilas Transactional Data Core

Level 2 - Industry Specific Skins

Level 3 - Custom Code

Level 4 - Business Intelligence (BI)

Level 5 - Enterprise (multi world)

Working with Shannon on content for the adilas university project in the adilas lite master plan. We spent some time on the value of education and then into some information on the proposed video library that we will be creating. Good session.

Working with Shannon on content for the adilas master plan. Finished up the enterprise level content (see below). We then reread the whole value add-on core model page.

Here is the content we came up with for the Enterprise level:

Level five of the value add-on core is what we are calling enterprise, or the enterprise level. Not every client or corporation needs this level of interaction and functionality. That is why this level is the top most level of the value add-on core model. For those who do need it, it becomes the unlimited top end and allows for all kinds of functionality between multiple locations or multiple corporations. Enterprise could be a number of different things, but essentially you start getting into a scenario where you have one master corporation that controls smaller entities. Think Sci-Fi (science fiction), top level control or dominance. You always have the aliens with a master ship that controls all of the sub ships and sub armies attacking the planet. Below we will paint a small picture of how this may look. Once again, this is not required but has huge potential for those who want and need it.

Back to the business Sci-Fi levels... In a world building analogy, imagine a universe level. You have multiple planets, solar systems, clusters, all kinds of things that are interacting together. Normally, most of your transactions that happen inside of adilas are on a single world, or on a single planet type level. That is what we would call a corporation or business entity. In the enterprise realm, you are starting to mix and blend worlds and/or corporations. This is great for all kinds of businesses where you have either franchises, mother/daughter type corporations, vendor/distributor, or entities that are somewhat connected and have either shared financials or shared ownership.

Inside of the enterprise level, we have already defined a number of pieces with data flow going both up and down the chain, big to small or small to big. Data flow is really important and helps with communications and reporting. The real value of that communication channel is too broad for this discussion, but it is essential for enterprise level transactions. You could also add any amount of custom code to create rules, automations, functionality, special relationships, or define any other need for the flow of data. Custom code at this enterprise level is how you fine tune your processes and cater the software application to your business needs.

One of the goals of an enterprise level system is normalization, meaning normalizing or standardizing your data. You can have multiple different businesses, all running on adilas, and they can all use the same terminology and the same type of accounts or landing places for your data. This allows data to flow up and down and in between worlds to help with reporting and business intelligence. It then allows you to pull standardized reports so much easier than pulling individual reports and trying to blend them together with spreadsheets or other methods. Depending on the size of the company, some of this normalization can be very cost intensive and even painful. Sometimes there are even teams setup specifically for the purpose of extracting and normalizing data from multiple software systems. The adilas enterprise level has incredible value and helps to overcome some big pain points for traditional companies. Think business intelligence on an enterprise or universe type level.

Here are some other benefits of the enterprise level:
- Master lists or libraries of data - items, vendors, customers, photo galleries, etc.
- Shared loyalty points and gift cards
- Multi-locational or multi-corporational
- Bulk tools, rules, processes, and scheduled tasks
- Consolidated banking and financials
- Consolidated reporting and business intelligence
- Permission levels and security
- Automated routines and processes
- Options for custom code

Amazing potential in the enterprise level! This is the top most level of the value add-on core. You get to mix, blend, and use any of these sub pieces to create your perfect dream business, track and record your story, ease your pain, and have the necessary pieces to help your business thrive!

Work session with Shannon. Working on the BI (business intelligence) level content. Part of the adilas master plan. We spent time today defining the ETL (extract, transform, and load) process and how that works. We also spent some time on the content for why that is valuable and important. Lastly, we spent some time going over how transactional data begins to break down (too many smaller entries or too big of a time span). Talking about solutions and how we will be helping our clients with the bigger BI master plan.

Small work session with Shannon. We were working on the business intelligence (BI) level of the adilas value add-on core model. That section is kind tricky. Some people think that business intelligence is just graphs and charts. You have to do a lot of boiling things down and refinement and re-refinement in order to get to the real BI level. Going over the process and what it really takes.

This may be somewhat on the side, but I feel like we have to do some teaching and training vs just using buzz words. I feel driven to help with that.

To start out our conversation for today, we re-read the notes from our meeting on 7/1/25. That got us going in the right direction. It is somewhat crazy to see all of the parts and pieces mixing together. All part of the master plan for adilas and what is possible. Good stuff.

Meeting with Shannon and working on content for the adilas value add-on core model. This is somewhat of the master plan and where we are heading. Today we were working on content for defining the core. Here is some of what we came up with... we may still edit some things but it's a start.

New content... - part of the value add-on core

Before defining the current adilas core, we thought that it would be helpful to show what is common or somewhat industry standard as far as matching software to needs.

The current approach that most businesses use is to look around and try to find the best in class pieces of software. Then they try to marry those software pieces together to get a semi-workable system. This commonly ends up being a solution that includes anywhere from 4-10 (or more) different software packages to run their business. Imagine something like this: Best in class inventory tracking, best in class POS (point of sale), best in class ecommerce package, accounting, payroll, timecards, CRM (customer relationship management), project management, scheduling, etc. You get the idea... Does this sound familiar?

This ends up being what is called a "mashup", or mix, of different software packages all trying to be pulled into one workable solution. The pain comes in as each piece dead ends and doesn't fully fit with the other pieces. You end up in somewhat of a time sink as you have to duplicate data or search for data details in or from one software package to the other. Not to mention that you have different accounts, contracts, logins, and are paying for multiple pieces of software.

Inside of adilas, we are demonstrating that it is possible to do all of these critical business functions in a single integrated system. This is what we do at adilas. Imagine being able to do full inventory tracking, fully configurable POS functionality, CRM functionality, scheduling, accounting, payroll, ecommerce, full financials, reporting, exports, and having a virtual paperless office (CMS - content management system). This is just the surface of what is available with adilas, one system, all working together in an integrated solution.

Some of the benefits of having a fully integrated solution are things like: Having everything in one place and it all interconnects (no dead ends). Being able to search and find underlying details of amounts, sums, and counts. Not having to buy all of the other software packages. You are no longer limited to strictly linear processes. You are able to have a virtual three-dimensional (3D) system that allows you to enter data at any level and it will interconnect. Another huge advantage is that you get to use what features you want and don't have to use other features that you don't need. It's all there, if you need or want it.

To describe the adilas transactional core, what already exists, we will start with the word "transactional". This means - details or individual transactions. If you catch every penny in and every penny out, every invoice, every PO, item usage, expenses, deposits, etc., you start getting transactions and data history. This creates multi-relational data stored over time. All of these underlying details and histories become the transactional core. Everyone who uses adilas will need a transactional core. This is what people will purchase as the base model for how they run their business.

If you want more, here is a 50 slide pitch of what we do... have fun... we call this the presentation gallery.

Recording notes from yesterday. Meeting with Shannon to go over text, verbiage, and content on the adilas master plan stuff. Working on talent and personality types. As we are writing these sections, we are trying to shoot for the ideal, show what is current, and then show where we are heading for our future plans.

Meeting with Cody. Going over UML diagrams that he is working on. Talking about efficiency, reuse, pros and cons of copy and paste, pros and cons of duplicating data, and math on the fly or precalculated math. Lots of good topics. Here are some of my notes:

- The importance of refactoring. Keep refining and paring things down. Make it smoother as we go.

- Talking about mini conversions and other options. Mini conversions is a sub of sub inventory (parent/child inventory). For example: Say you have something that gets sold by the case, by the bottle, and by the fluid ounce. You have to be able to go up and down the conversions to show what is really there. True inventory tracking.

- Talking about lots of suggestions and what makes sense to change out and/or leave.

- On the mini conversions, we might be able to hold the conversion id's and the math all on the same table. Help the users setup the conversion charts and/or relationships. Especially if we don't know the conversion factors or ratios (custom conversions or custom units of measure).

- We have had a lot of wild west style development (anything goes). There is a need for specific roles and company structure (adilas jelly fish model - future plans for where we are heading as a company).

- We mix so many different business verticals. That has been a huge blessing but also a small curse (so diverse).

- Cody was pitching that we need a primary role of a database admin type person (specialists per role). Creating the chain of command, down the different roles. Basically, turning the wild west into a more modern city (modern development environment).

- Talking about someone who knows how to work really hard and how to help them to work smarter and use technology.

- Cody wants us looking into growth, in the long run. Talking about a master plan and then breaking things down into more digestible pieces.

- Talking about internal education and structure. We need our team to know what to do and how it (all of the pieces) fits with the bigger picture or the whole.

- Figuring out what we have, suggestions for what to change, and future plans.

- We then got into time sub inventory and parent/child relationships. It gets deep, pretty quickly.

- Growth is hard to manage sometimes.

- Talking about independent developers, light guidance, and working on our own. Reasons for building out the UML diagram. Not just for Cody but for all other developers who will be working on this project.

- Building out the dream. Getting organized (not really official, but pretending that it was official). It will all help in the long run. Risk vs rewards - push/pull in the organization. Unofficially organize ourselves (at least on the development side).

- Link to the interactive map - small visual for how things are organized.

The actual meeting with Hamid was from 4:30 pm to 5:30 pm. I spent the first half an hour doing some prep work. Putting him in the system as a user, assigning permissions, and recording a small video for how to record project timeclocks in adilas shop (just under 4 minutes in length).

During the actual meeting we went over how to add project timecards, different tasks, adding, editing, and looking things up. We built some quick links to help him navigate around quicker. We then talked about Snagit and Camtasia for options for internal and external training. Hamid is going to checkout some tutorials there to see how it works. We briefly talked about some of the billboard sites and options there. The other major topic was dealing with helping to refine some documents and make things more presentable. I gave him a few links to check out and we'll slowly start refining some of the pieces of the plan.

Links that I sent to Hamid

- 10,000 foot view of where we are headed... https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=10377

- More links and research stuff - master plan - https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=10179

After the meeting, I did some clean-up, reviewing some Snagit files, different videos, and uploading the new video for adding subs of time.

Emails and recording notes from older entries. Trying to get caught up. Recording notes from back on 7/11/23 and some of Aspen and I's brain dumping and high level master plan stuff. Then moved on and did notes from 7/17, 7/18, and 7/19.

As a small side note, none of this would be possible (developer notebook entries) if I hadn't scribbled some small post-it notes when it actually happened. On the negative side, it does take a while to transfer that info from pen and paper into digital, but it has great value to me and is worth it. Anyways, this is a small shoutout to the speed of pen and paper as a quick tool (small little scratches). Sometimes I'm presenting or in the middle of a meeting and can't take a digital note or someone will say something and I quickly scribble it down. That's how I roll. Those tools help extend my memory. Good stuff.

All kinds of little things. Emails and reviewing the adilas docs. John had been in there making some changes. Sent an email out about the pivot group meeting tonight to go over ship A and ship B stuff.

Small notes for me - There is a huge value in education alone. If you combine education, training, and maintenance, you have a huge piece of the puzzle. Those pieces will help support the whole. I added in a few research links to our Google doc for master plan research.

Working with Aspen to go over our plan for making the plan. Light review and discussing expectations and where we are going. Started in on adding some research links to part of our plan. Pushed up the new stuff to the google doc that John and I had started.

Here is a light version of where we are heading... (just barely starting - for the record, it looks nicer in the google doc)

Master Adilas Plan or Adilas Master Plan

1. Company Structure - Adilas Jelly Fish Model
2. Product Development - Adilas Value Add-On Core Model
3. Education & Training - Adilas University
4. Community & Outside 3rd Party Solutions - Adilas Marketplace
5. Social & Efficiency Options - Adilas Cafe & Community
6. Deeper Product Development - Adilas Lite - Fracture Project
7. Budgets, Finances, Marketing, & Sales - Other Business Plans

New note added on 8/14/23 - For a pretty good breakdown of these projects - just at a high level, see this element of time 10377 and it's photo gallery.

________________

Table of Contents. To-do

All time id's are inside of adilas

2283 - Main Index

2284 - Jellyfish Model

- Research on the Jellyfish model - link

2285 - Value Add-On Core Model

- Research - link

2286 - Adilas University

- Research - link

2287 - Adilas Marketplace

- Research - link

2288 - Adilas Cafe & Community

- Research - link

2289 - Fracture - Future Project

- Research - link

- Adobe XD mock-ups with options

2290 - Budgets & Finances

2291 - Marketing & Sales

- Adobe XD mock-ups with options

- World Building Concepts and Concepts of the Data Assembly Line - Pitching the concepts

- Research on world building, research on data assembly line

- Presentation Gallery - great start for an outline of what adilas does

2292 - Other Timelines, Plans & Projects

Meeting with John and doing some planning. We were going over themes, ins and outs of how to make a new theme in our existing code, folders, paths, settings, and page level controllers. We talked about some of the new code and R&D that Jonathan Wells did. We are looking for feedback. We may end up offering options and pushing the choices over to the users. Tons of toggle on/off switches for the different features.

People don't want to scroll and they want a minimal number of clicks to make something happen. We talked about getting the information (all kinds) into the database. Minimal on the hardcoded pieces. The whole thing becomes data driven.

I was drawing and talking about different things. We would love to create a master plan. John and I started a small google doc to gather some the of the master plan info so we both could access it.

Shari O. jumped in and had some payroll questions. We did some quick research, pulled some records, and helped her make some changes. We got it all figured out.

Went into Smithfield to meet with my dad and his friend Harry. We chatted about updates, changes, and plans. I offered to help get them started and/or pay for an adilas power user to help them get started. It may be a great way to help people get going and get started. Basically, assign them a buddy to get them up and going and then they can take over and/or sub it out. After Harry left, I went over some new developments with my dad and lightly was pitching him on our master plan and possible ways of raising funds for adilas projects. That was kinda fun and he was a good listener and was encouraging me to keep pushing on things. We'll see how it all plays out. One of the biggest distractions is time... it takes time to make these plans and then it takes time and funds to make them happen.

One huge advantage of our system is the visibility and transparency of who does what inside the system. If we don't have it, we could easily add it. We currently have tons of histories, log notes, historical data, and data broken into tons of small transactions, all being monitored and recorded in the background. That is awesome.

The sales guys are gearing up to help sell gift cards. Sean and Michael have been pitching some of our existing clients to see if they could help them get started, for some practice runs (doing gift cards and gift card setup).

As part of the sales meeting, Steve asked me if I had any sales ideas. We started getting into a small pitch of where I think things need to go. Basically, a pitch of our pitch (parts of the adilas master plan). Nothing is in stone, but I had been thinking about some ideas and options over the weekend. I pitched the idea of maybe selling some percentages of adilas in order to raise some money. We are shooting for 2 million and basing a budget off of that. As we were talking, Steve was liking what he was hearing, but he also had some hard or tough questions. I wrote a number of these questions down in a Word Doc that I have been working on, but some of them dealt with things like client acquisition costs, life expectancy for clients, what do our clients really like and need (MVP stuff), and how can we roll things out in packages or make the process smoother? How do we get paid back? What are the timelines? What is the ROI (return on investment)? And other great questions. Good discussion.

Eventually, Steve had to bail out and jump on another call/meeting. He wanted to stay but had to go. He told us to keep planning things out. Sean, Michael, and I kept going, talking and laying out the basic pieces of the plan and/or pitch. It's not ready yet, but we want to build and make our own pitch deck (files, assets, and a presentation) for potential investors and co-owners.

As we were talking and drawing things out, Sean said that he heard this from one of our clients - "You (meaning adilas) are sitting on a gold mine." - Renee Grossman - "You just need to finish it!" - Meaning we have a great thing going and being developed. It just needs to be taken to the next level and fully get the i's dotted and the t's crossed. This comment of "You've just got to finish it" inspired some more discussion on helping people catch and believe the vision of what we have and where we are going.

I was giving the analogy of the Death Star from Star Wars and how it was mostly a work in progress but it finished enough to give you the vision of what it could be. I realize that not everybody likes Star Wars, but I liked the analogy. We went through a number of drawings, light sketches and talking about options. I had a fun time, and the guys were chiming in and having fun as well. Basically, I was trying to pitch them on the adilas master plan and recruit their help in building it out further.

Just for fun... I added a small Star Wars graphic that I modified on 3/13/23 to this element of time, just for fun. See attached.

Getting ready to send some documents and starting info over to Steve dealing with the adilas master plan. It's not done, but we are making good progress and I've been gathering tons of info and details and data.

Just for fun, here's another element of time (developer's notebook entry) that deals with what brings value?

Emails and working on the adilas master plan. Spent some time updating the presentation gallery outline document. See attached. The old starting went a little deeper and was kinda rough. Smoothed out the opening and did some light formatting.

Started playing with elements of time and setting up the main pieces for the adilas master plan. Here is a quick breakdown of the time id's.

Master Adilas Plan

All time id's are inside of adilas

2283 - Main Index

2284 - Jellyfish Model

2285 - Value Add-On Core Model

2286 - Adilas University

2287 - Adilas Marketplace

2288 - Adilas Cafe & Community

2289 - Fracture - Future Project

2290 - Budgets & Finances

2291 - Marketing & Sales

2292 - Other Timelines, Plans & Projects

Working on gathering up ideas and data for a master adilas plan. Reading over notes, developer's notebook entries, and coming up with some scratch files to add to the plan. The goal is gather things, then copy and paste from the scratch document into a more organized and formatted official document of sorts. We may end up using the web, so that we can link and refence all kinds of other things. It also becomes searchable which is awesome.

As a side note for me, I'm seeing the adilas jellyfish model as a great starting point for our master plan. It has all of the services and extensions that we want to build out and define (that we can see right now). See attached for an older copy of that graphic.

Cory jumped on to the meeting. We were talking about monies being owed to us and from us to others. Maybe even holding projects for payment before starting. Lots of talks about cash flow and getting the development funded that we are doing. We do a lot, we just don't charge for everything. That is both good and bad. We really need to charge for the services that we provide. We tend to do a ton of stuff for free, but that is costing us big time.

We talked about a menu board project and who was going to do what. We have developers who can handle the backend, but they don't have the frontend or design skills to really make it look nice. We have to mix and blend who is doing what. We also talked about breaking the bigger projects into tons of smaller, more manageable mini projects. They, the clients, were requesting a 4th menu board (already have 3), new settings, auto refresh, and tied to quantity on hand.

The concept of an "MVP" (minimal viable product) and how that fits into the bigger or master plan. Either way, you still have to manage these projects from end to end. 

Towards the end, Cory and I spent some time looking into the timeclock issue with the AFB timecards and timeclock app. We ended up checking different versions of the code, working with the backend actions, and looking over code with Cory. I was coding and narrating and she was watching and asking questions.

Great little session on the look and feel and where we are headed. See attached. Also, here is a small copy of the verbage for the summary we did today.

-- from the attached file under a question about the look and feel and user interface.

Summary: When we started Adilas we decided that we wanted to get functionality done first, followed by look and feel. We know it is time to bring that pretty, modern look and feel into play. Some of these aspects are already being approached and more are on the horizon. 

We have chosen to let the clients lead with their ideas, suggestions, priorities, and funding. This has directed our development and our growth thus far. We recognize that many people would like us to just spend the money and make everything pretty, but then you still may not make the goal or hit the mark, which is continually changing. We feel it is important to keep following the client's lead and this will still be our main approach. 

Having said that, we are definitely planning on extending more services, continuing to evolve and refine the interface, and keep following what is working. This will include getting a master plan in place. Many people have heard us talk about this concept called "fracture" - which is a name for a future project which will be a configurable, dynamic interface that will only turn on whatever pieces you want to see. Fracture will include countless ideas, lessons learned thus far, ways to improve efficiency, and breaking things into smaller modules and pieces. This will include more efficient navigation, dashboards, and user friendly features. 

It's beyond the scope of this summary to fully explain here but this will be incredibly powerful to be able to configure Adilas to whatever level of complexity or simplicity you want. This is like an iceberg mountain analogy. You still have the whole mountain but you only expose what you want to see - just the iceberg portion on top. It can make it feel easier, simpler, and more manageable. 

The current model is composed of numerous, smaller prototypes that have been linked and wired together. Our eventual goal with fracture is to make all of those prototypes have the same look, feel, and flavor. This will be selecting the best of class from over the years and standardizing it across the platform/system.

Even though we are talking about look and feel, taking a team approach, helps us move forward in every aspect of furthering the application and model. People who work together are able to achieve more and that is how we are trending and changing our operations even further. More good stuff to come.

If you type the word "fracture" into the developer's notebook you will begin to see how big our plans and dreams are for what we want to accomplish when we build to this "fracture" plan.

Shannon jumped on from 11 to 12 and we did a work session on prepping a document for an upcoming meeting. It was somewhat of a business planning agenda of sorts. See attached for what we were working on. We know that we need to do some planning and get a more firm or concrete master plan in writing and make that public knowledge, at least within our own company. Right now, the vision resides in heads of a few of the cofounders. We would like to pull that knowledge out and put it in writing and/or make a plan. Once again, see attached for some questions to help get that process started.

Glossary Terms:

A

• Actions/Action Page - Often, when you are on the web you interact with a form. This form always submits its data to an action page, where it performs an action. Normally, this is a database action, report filter, or some other logic function that is performed.
• 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 customer invoices that are not paid. Money that is owed to your company. 
• Active - A status that designates data as being in use. This status relates to almost every database record, or at least all main players within adilas. By default, the active items show up on reports and searches. Inactive items must be specifically requested, if needed.
• 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 - This assigns a customer to the main queue (waiting room or waiting list). Often this is used in connection with shopping carts and other service oriented checkout processes.
• Adi - Meet our mascot, Adi! Our blue dog avatar, Adi, is the mascot of Adilas, and encompasses what we are comprised of - a trustworthy, invaluable, and loyal sidekick for your business. She's always ready to help!
• Admin Time Clock - This allows admin users to see all active time cards/hours based on requested parameters. It also gives the 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 - The advanced add to cart function is based on permissions. We sometimes call this the haggle mode feature. You can change prices, quantities, back into things, figure out advanced math, change mark-ups, view profit percentages, apply discounts, etc. Super flexible. Not required, but a very flexible add item to the current shopping cart functionality. Inside the system, it can be accessed by clicking on the double plus (++) link per item.
• Advanced Searches - All main sections or player groups in the system have advanced searches. These searches include far more filter options than a standard search. Often, you can even pick and choose what fields, columns, or values to show. Once the reports are returned, there are save options for viewing these reports later. If you are a quick search user, the keyword adv (short for advanced) can get you to the advanced searches without other actions.
• Age Verification - This is a process of checking the age of a patient, or client, for either viewing and/or purchasing options. If age verification is needed, turn that feature on in the corp-wide settings. This can be for ecommerce (viewing and purchasing) and/or internal processing (check-in, verification, diver license swiping, or other identity checks).
• AI - Artificial Intelligence is tied to a LLM or large language model behind the scenes. Often AI is used to automate tasks, it can use "fuzzy logic" to process natural language and then replace normal speech with computer API calls or functions. Various other options exist as well. This is a growing field, and player, in the computer and web space.
• AI Agent - An AI agent is a special function of normal AI. The agent gets, or is given, access to do certain tasks and/or functions. Often, the agents are trained specifically on a certain task or business function. Inside of adilas.biz, we have an AI agent named "Adi". It has been programmed to help with simple navigation, training, deployment, settings, and even some consulting. The goal is to help it keep learning and adapting so that it will be a master adilas.biz user and consultant.
• AI Context Window - The AI context window is a set number of tokens that make up its available (quick) memory. A good way to think of the context window is like a sliding window that can move over tons of data. It doesn't care about all of the pieces, it is only looking for what matches its context, or what is being requested. Often, the context window tries to stay in the same scope or mode. If needed, the context window could shift, so that it can do other tasks. Another way to think of it is like a Google search. Tons of information out on the web, but the search only brings back what you need. Imagine that happening with AI, but even better and possibly layered.
• AI Image Generator - This is an AI tool that takes normal, written, or typed prompts and then creates an image for you using an AI backend. The system has a number of places that allow for AI image generation. Things like item category images, item photo galleries, etc.
• AI Quick Search - This is a super version of the normal quick search. This interface allows you to jump and do almost anything in the system using a simple form (sometimes called a command line interface). Quick help, prompts, and cheat sheets are available from that page. Imagine a simple Google search type interface for the entire system. Very cool!
• AI Tools - An AI tool is a preset, or preprogrammed function or method. These could be API's, sockets, or special tasks that an AI agent knows how to use. They could also be set URL (web addresses) or form submission functionality pieces. The term tool, or tools, is used to help the AI agent know what options it has to do and/or perform.
• API - An API is an application programming interface. Basically, it's a way for computers to talk to other computers. You can do special tasks, request data, and sync records using API's. Very flexible. Most API's have lots of documentation of what is allowed or required. For security, there are often special keys, tokens, and settings that may be assigned or used. API's also have a master switch that either allows or denies access.
• 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 and when is the payment due. 
• 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. Assets are tracked on the balance sheet. Assets are one of three main categories. There are assets, liabilities, and equity. Inside the system, many of the assets are automatically tracked or called system-maintained balance sheet items. These are things like bank balances, petty cash, inventory levels, and accounts receivable. We also offer options for other assets to be tracked on the balance sheet through user-maintained balance sheet items (not automated by system). These may be monies that you loaned out, vendor credits, etc.
• Assign to Cart - This is a button on the customer log page (customer profile page) or some other customer report. By clicking this link/button, it will add the current customer to the shopping cart.
• Authorize.net - An available merchant processing gateway. Provides integration for internal shopping cart, online bill pay (clients paying after the fact), and ecommerce solutions.
• Ctrl-A - This is a keyboard shortcut on windows for selecting all the content in a certain area. This is control plus the A key.

B

• Balance Sheet Item - A user-maintained account that stores data on the balance sheet. Your company may create any number of these user-maintained balance sheet items. As a note, there are many automated tasks that the system will monitor and track for you as well. Those are called system-maintained balance sheet items. A user-maintained balance sheet item (BSI) may be an asset, liability, or an equity account. Without going super deep, each balance sheet item gets created, gets a starting value, and then it may be connected to any number of other transactions that either bring its value up or down, depending on what is happening. These are used for financial records on the balance sheet report.
• Bank Reconciliation - This is a process of matching what the system says (deposits and expenses) to what the bank says. Most deposits and expenses have a number of dates. These dates are the creation date (you know about it), the verified date (when the bank knows about it), and a posting date (when it becomes locked down). Most bank reconciliation reports deal with the verified date. Things may be verified one-by-one or there are some bulk tools and processes.
• Banks - Inside the system, a bank is a virtual account where you can track monies going in or out. At least one is required if you want to do deposits or expenses. An unlimited number of banks may be created. Some companies also use banks to help track credit cards and other cash tracking accounts.
• Barcode - A barcode is a series of lines and spaces that make up a unique value. They are often used to help speed up the sales process. Inside the system, barcode values may be added to numerous items including inventory items, special POS buttons, discounts, flex grid tie-ins, and all sorts of other id's or numbers. There are fields to record barcodes, or you may create your own. Inside the system, we allow for numbers 0-9, all alpha characters, and even some special characters. There are also a number of barcode generators and label makers built into the system.
• Basic Live PO - There are multiple types of PO's or purchase orders. A basic live PO deals with vendor specific items that are present or available for sale. Without going super deep, there are other PO types such as special PO's, update PO's, build PO's, request PO's, and others. The name basic live PO may be changed in the corp-wide settings (see section C).
• BI or Business Intelligence - This is the process of gathering up smaller pieces of data and being able to show trends, totals, sums, averages, counts, maxes, mins, stats, and other telling data. Business intelligence is often used by companies to show quick values and even tell digital stories over time. Often BI uses lots of reports, exports, and other graphical representations of the data to help the user easily see what is going on.
• Big Data - Think mixing everything... Big data refers to collecting large sets of data that can then be analyzed to reveal trends, patterns, and relationships. These data sets are often too large and varied to be handled by traditional data processing systems. They require more specialized systems to organize and compute the information gathered so it can be better utilized in business decision making.
• Bit Map Image - This is similar to a JPEG, PNG, 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 - We use this term to talk about custom code or page level take-overs. These page take-overs allow customer specific functionality as requested. Basically, a black box is one or more insertion points where we can make a change. We do a lot of custom coding for our clients. This is part of the technology that allows for that to take place.
• Browser - Browsers are how all web-based content is shown. There are multiple browsers and some of them are based on your operating system or preference. These are things like Google Chrome, Microsoft Edge, Safari, Opera, Firefox, etc.
• BSI - An acronym short for Balance Sheet Items. It may also be shown as B.S.I. See balance sheet item definition for more information. There are system-maintained and user-maintained balance sheet items. Most of the BSI's deal with the user-maintained items. Think of a miniature account for various things. Some of these could be things such as loans, individual or company investments, large assets like buildings, vehicles, machinery, etc.
• Build & Hold - This term is used inside the recipe/build section. It is used on the raw goods side. The build and hold process uses raw goods and eventually creates an outcome or other product. Technically, we use other terms such as ingredients, outcomes, etc. This build and hold process is usually a preparatory step and those products may be used farther down the manufacturing line, or to be sold independently.
• Build & Sell - This is another term used inside the recipe/build section. The build and sell process is used on the invoice side. Often the build and sell process may be used for quick, just in time, preformatted groups, or kits. Basically, you put together the recipe (what you want to sell as a group) and then you build it, or add multiple things to the shopping cart as needed.
• Build PO - This is one of the PO or purchase order types. This is used to take raw goods and combine them into one or more new items or pieces. There are multiple PO types such as live PO's, request PO's, update PO's, and build PO's. This may sound like the recipe/build section, but it is different. This is the actual PO or inventory tool that helps with the inventory tracking. A recipe may be used but it is not required. Either way, you are taking some form of an item, or multiple items, and making them into something else.
• Bulk - The word bulk means more than one thing in the system. In general, it means doing more than one thing at a time. This could be bulk adding items, bulk editing or updating line items, bulk verifying, bulk clean-up processes, etc. It could also mean bulk printing of labels, invoices, bulk uploads, and the list keeps going.
• Bulk Add - This is a term used to denote adding one or more items to things like PO's, shopping carts, deposits, etc. Basically, you do a search, and then you can interact with one or more of the items that are showing from your search. Usually, the process looks for either a valid quantity or checkmark, then once the add button is clicked, only those values will show up on the correct page as new line items.
• Bulk Edit - This term is used to modify, update, or edit line items. Usually line items are found on invoices, quotes, purchase orders, expense receipts, deposits, etc. Bulk edit will take you to a special page where multiple changes may be made at once. Upon submitting the form, all changes are stored in the shopping cart (memory) or database.
• Bulk Transfer - This term deals with transfer invoices and moving things around. Most transfer invoices take place through the shopping cart and special bulk tools. Imagine things in a warehouse and then moving them just in time, on a schedule, or for an event. The bulk transfer is very handy and helps save some time. There are also some bulk transfers that happen if you are doing cultivation, harvesting, or other plan related activities. Those bulk transfers happen on special PO's.
• Bulk Verify - This is a term that we use on deposits and expense receipts to help keep bank balances up to date. Usually, most financial documents have multiple dates. There is the creation date (you know about it), the verify date (the bank knows about it), and the post or lock-down date. 
• 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

• CartPointe - An available merchant processing gateway. Provides integration for internal shopping cart, online bill pay (clients paying after the fact), and ecommerce solutions.
• Cart - Where items are placed in order to make a purchase (see also Shopping Cart). The shopping cart is available for both internal POS transactions and external ecommerce transactions. Both carts have multiple sub tasks, features, and tons of functionality.
• Cash - This term deals with some sort of money or bills. Inside the system, cash is a money type (similar to check, credit card, etc.). The term may be used on the inbound side from customers and clients. It may also be used on the outbound side for vendors and payees as a form of payment. Without getting super detailed, there are also some accounting terms that deal with cash and actual cash value.
• Cash Counter - This is a special page inside the system that allows you to put in figures and it helps you count the total cash. For example: I have 103 $20 bills, 37 $10 bills, 56 $5 dollar bills, 17 $1's, etc. This would give you the total value of the cash. It also works for coin or cents.
• Chart Of Accounts - This is a traditional accounting term, meaning a way to organize different parts of the financials. Often, traditionally, they have a number assigned to them that help them show up in the correct spot for the P&L, income statement, and balance sheet. Think of them like named containers for data and records. Often inside of the system, we use the terms expense types, deposit types, and balance sheet types to mean or reference chart of accounts. Without going into too much detail, adilas.biz uses technology and relational databases to simulate what traditional chart of accounts did (paper/pen or 2D model). Tracking objects and data over time to help them show up in the correct financial documents.
• Check - This is one of the many money types used inside of the system. This could be used on inbound or outbound transactions.
• Check Requests - A check request is a potential precursor to an expense. It is similar to how a quote and an invoice are related, a quote is a potential precursor to an invoice. A check request does not count toward financials while it is in the request state. It requires an approval, and once it is approved, then it can become an actual expense and will be booked on the financials. 
• Child - Connected to a parent item (parent inventory) which carries the name, the main item id, and some basic information. The child item is unique and may carry more specialized information (see also Sub Inventory). The term child is somewhat of a shortcut for talking about that parent/child item relationship.
• Chooser - This is a page with 40+ choices of other pages that may be set as your default homepage (starting place within the system). It is called the chooser because the user "chooses" which one is most suitable to their needs. Once chosen, that page becomes the new homepage. Switch as often as you like based on your tasks or your style.
• Classic - An interface that shows all potential functions in the system. Not geared toward any particular tasks or industry. There is also a thing called the classic cart - one of the original internal shopping carts. For the most part, classic means original, or an oldy but goody.
• Clear Cart - Wipes out all actions related to the active shopping cart. This action must be performed to log out of the system, or to start a new cart.
• Clock In/Out - This is a way for users to track their hourly work. There are multiple levels within the timeclock application, including admin, managers, and payee/user levels. The users must be assigned to a department and have the correct permissions turned on to clock in/out. These hourly records may be used by themselves or advanced into the payroll side of the system.
• Closed - This usually means some sort of ending or removing of certain things inside the system. We often use the term of inactive status if dealing with removing or hiding certain things. There is also some direct usage of the term closed, dealing with sub inventory. Once a sub/child item is at quantity 0, it can be closed.
• Clover - An available merchant processing gateway. Provides integration for internal shopping cart, online bill pay (clients paying after the fact), and ecommerce solutions.
• Corp Id - The identifying number associated with every corporation. It is assigned upon activation. This value is basically your "world" number. It is used in numerous places within the system, including external resources such as ecommerce.
• Corp Key or Alias - This is a special way to denote a corporation without just using the id number. A corp key is a combination of three letters of the corporation name, a dash, and then a numeric corp id number (it may be padded with 0's, if needed). Pretend that a company's name was
  "Playground" and the corp id was 53, the corp key may look like this "Pla-0053".  You could also use an alias such as "Playground" or "ILikeToPlay", but that needs to be set inside the database for storage and usage. The corp key is used on login, API access, and in all ecommerce transactions.
• Corp-Wide Settings - These are settings that help control the flavor, tone, and verbiage of all parts of the system. This includes things like, what to call your entity, locations, customers, general inventory items, and so much more. There are hundreds of these settings. This is how you make the system talk and speak your language. This is also where numerous defaults and show/hide options are set. Imagine a whole smorgasbord of options and you only choose just what you want or need. That helps make the system custom for you and your industry. There are settings for invoices, PO's, vendors, taxes, discounts, defaults, and almost every other main subject or topic within the system.
• 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 - A shopping cart that is not assigned to a customer. Used in sales situations where the customer does not need to be tracked or assigned. No loyalty points are accumulated for these types of sales. These sales should not be put on account, because the customer/client is unknown. Often it is for high volume, quick cash, or a quick credit card transaction.
• Create - This is another word for adding or making something new in the system. For speed, if using the quick search, you just need the keyword new. For example: new cart, new invoice, new po, new expense, new deposit, new customer, etc. Super power tip... If you want, the keywords new, create, or add also work when using the AI quick search - add time, add deposit, create vendor, etc.
• Cross Corp Invoice to PO - A special function that must be added by a system administrator. There may be fees associated with this functionality (cross corp stuff). Once assigned, it allows one corporation to send inventory via an invoice (outbound inventory) to the other corporation. These two corporations must be on the same server. Once the receiving corporation gets the information, it will automatically turn the invoice into a PO (inbound inventory). Both corps must agree to connect. This example shows flow from one corporation to another, if multiple corporations exist, and need this functionality, they may also be assigned and setup. If advanced options are needed, please ask a representative to tell you about enterprise level functionality.
• 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 number of settings that affect the CSS.  
• CSV - A CSV stands for a "Comma Separated Values" file. This file format is simple text that uses commas to separate values into tabular data or rows and columns without having all of the lines. It is great for exporting data from one system to another. This is also a common format if data from another system is needed for import inside the system. Within the system, based on permissions, there are options to both import and export CSV files, in certain areas.
• Ctrl - This is the shortened version, or how it is written, for the windows control key. It is often used in a combination for showing keyboard shortcuts. Example: Ctrl-C, Ctrl-V, etc.
• Ctrl-A - This is a keyboard shortcut on windows for selecting all the content in a certain area. This is control plus the A key.
• Ctrl-C - This is a keyboard shortcut on windows for copying a certain selection and putting it on the clipboard for future use. To paste something, use Ctrl-V. These two are often used in combination.
• Ctrl-N - This is a keyboard shortcut on windows for creating a new window 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-T - This will get you a new tab within your current browser.
• 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. Its brother command is Ctrl-Z or undo.
• Ctrl-Z - This is a keyboard shortcut on windows for undoing a previous action. Its brother command is Ctrl-Y or redo.  
• Ctrl-+ - This is a keyboard shortcut on windows for zooming in (make it bigger) on the webpage or browser. This is the control key and the plus sign (+). 
• Ctrl-- - This is a keyboard shortcut on windows for zooming out (make it smaller) on a webpage or browser. This is the control key and the minus sign (-).
• Cultivation - This is general term that some industries use when dealing with plants and herbs. Cultivation usually means tracking and monitoring the entire process from planting, cloning, growing, and other phases, clear out to harvesting and production.
• 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. It is also generally used to say, we could add that into the system, 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 those 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 a line, or a queue, so that they are seen in a first come, first serve order. Multiple queues can be used to designate customers as VIP, Pickup, etc.
• Customers - The people, or companies, you sell items or services to. There are settings inside the system to allow you to name your customers as you see fit. Examples: clients, members, students, patients, buyers, VIP's, guests, etc.

D

• Dashboard - A dashboard is a special interface that shows quick access buttons, charts, graphs, and stats. They come in all kinds of varieties but basically speed up commonly used functionality. Usually, there is some representation of the underlying data in some sort of summary, count, total, or other aggregated function. Often, users like to use dashboards to speed up processes and/or control their layout and space (what they like to see and/or use).
• Data - This is a generic term for digital information. It could mean all kinds of things. This system is a real-time data portal where you can cache, send, upload, and archive your data.
• Data Table - Inside of web pages, tables are often used to help with layouts. A data table is a special kind of table used for reports. It has special functionality like special exports, local searching, sorting table columns, and a thing called pagination (next or previous page). Great for showing and interacting with tables of data or tabulated data (reports with rows and columns).
• Database - This is a background storage engine that holds all of the data. A database contains numerous 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 the 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 information from session memory into the database where it is stored.
• 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 lots 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. If you want, you can even have a custom dashboard or default homepage made. See the Chooser for more information.
• 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.
• Delete - This is the act of making something go away. Inside of adilas, most delete actions or remove actions occur by changing what is called a status from active to inactive. This is how you hide/show or use/don't use certain items. All main player items and their subs have status fields inside of adilas. Once you get into a multi-relational database, you don't really want to do real deletes and start making holes all over you data. Inside of adilas, most things are deleted by changing a status value.
• Delivery - This usually means that an invoice or order needs to be delivered by a driver or carrier. If your company uses delivery options, they may be setup in the settings. If not, no delivery options will show up. Some delivery options include vehicles, sales staff, travel routes, estimated times, etc. Delivery is also sometimes used by or from external entities that need to pick up products and then make those deliveries.
• 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. 
• Direct Deposit - This is when a company sends or wires money directly to someone's bank account. This could be for payroll, commissions, or bill payments.
• 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. 
• Due Date - This is used on invoices, statements, expenses, and other key documents. A due date is when something is due. In business, usually that means a payment is due. Inside the system, there are various fields and search options for due dates. If you or your company use due dates for your customer/clients, they may be setup in the corp-wide settings. Once setup, they will be available in the cart, quotes, and invoice sections.
• 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). Sadly, flash was discontinued by most major browser. We really liked it for multiple parts of the system.
• 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. Sadly, this interface no longer exists due to browsers no longer supporting flash interfaces.
• 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 standalone sales 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. Sadly, these flash buttons have been replaced with normal web buttons, due to browser support.
• Flex Attribute - This is a custom field or fields that allow you to setup custom naming and data types for special fields. Flex attributes are somewhat like a database extension. Meaning, if you need a field or value tracked that doesn't exist, you simply create it. Those values are then searchable, and you are able to track that extra or special data (flags, tags, custom data, and other options).
• 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. This may be setup in a one-to-many relationship and allows for interconnecting different pieces within the system. Admin settings allow for limited fields to show up for simple add/edit processes. Very flexible and help with custom data tracking and reports.
• 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.
• Fracture - This is a code name for a future buildout of the adilas.biz application. It involves all kind of toggle on/off settings, aliases, deeper code structure, and ability to customize anything. The term fracture came as we started seeing main components and pieces start sub diving into subs or fractures. There are whole pages about what this means - future buildout and master plans - also called adilas lite - https://data0.adilas.biz/lite/
• Fulfillment - This is the act of finishing or fulfilling an order or invoice. Fulfillment is a step in the process. Within the system, there are special settings and pages to help with this functionality. Often, once something has been fulfilled, it gets stamped or approved and then passed on to the next stage or phase.
• 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.
• Gift Cards or Gift Certificates - Gift cards deal with selling a future I owe you to a customer or client. The value is held on the side until it is redeemed or used. Gift cards and gift certificates are part of the section called special accounts. This section deals with loyalty points, gift cards, vendor credits, in-store credits, and other miniature tracking accounts. Once turned on, this functionality is available at no charge from within the POS system. Your company is in charge of the actual cards (if using a physical card), but the tracking and usage of the system is built in.
• 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. 
• Global Context - This is a term that often refers to AI or artificial intelligence. The global context is a term that deals with the overarching what, when, who, why, and how type values. Global context helps the AI figure out what goes where. Lots of moving pieces, but basically content to keep it aligned with the current or programmed tasks or functions.
• Go Mode - This is a special keyword to help the system use the most possible navigation options. There is a feature inside of adilas called the quick search. It exits on every page in the system. If you use the quick search, you can jump and bounce to any other part of the system. If you type in the keywords "go mode" into the quick search, it will take you to a special page that is programmed to show you almost every possible option in the system. Some people like to select this page as their main homepage from the chooser. It's that fast... Go mode is for let's go! Super powerful search page.
• 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

• Half Baked - This is when a product or feature is mostly done and/or partially done. Haft baked means it still needs a little bit of loving to make it perfect. Sometimes features are released in a beta or trial version. We call that half baked or half-baked.
• 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. 
• Harvest - Part of the plant cultivation cycle. This is when you take a part or all of a plant and turn it into something. If you company does this type of process, there are special tools inside of the system to help with the harvest process.
• 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 - A status that designates data as being out of use. Inactive means remove, hide, or don't use. Inside the system, a status of inactive is how you virtually delete things. When inactive, data will not show up in searches and reports by default. A 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.
• Knox Report - Special sales report for invoices and payments made. It has the ability to show quick stats, counts, and other math totals. You can also run comparisons on different date ranges if wanted. The original report, and all of the columns and/or numbers, were requested by an operations manager named Phillip Knox, out of Canada. Thus the name. It's really just an awesome sales report.
• KPI or Key Performance Indicators - These are a set of values (totals, counts, averages, sums, etc.) that are used to determine how things (people, processes, or campaigns) are doing. Some of these KPI's are used on reports, dashboards, and in other areas. Basically, someone setups up a rule and and benchmark goal. Then things are evaluated based on those key performance indicators.
• Kush Cart - This is a version of the internal shopping cart. The three main versions are the classic cart, the Kush cart, and the mini scan cart.

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.
• Label Builder - Special application and/or functionality to help with custom labels. Inside the system, there are various label builders. Some are very basic (auto linked from specific pages to the label generator) and other allow for all kinds of drawing, graphics, dynamic text, colors, rotation, barcodes, QR codes, custom naming, saving, etc. Multiple versions, based on needs.
• 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.
• Loyalty Points - This is the process of assigning points and values (dollars) to a customer or client who purchases from you. These loyalty points can have ratios (how many points for how many dollars spent), date rules, redemption rules, etc. Inside the system, you have to turn it on, but the system will automate this process for you (checkout, accumulation, redemption, etc.). The bigger section is called special accounts and deals with things like loyalty points, gift cards, vendor credits, in-store credits, etc. The use of loyalty points, in the system if built-in, once turned on at no extra charge.
• 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

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

N

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

O

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

P

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

Q

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

R

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

S

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

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

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!

On 6/27/19, Brandon and Shannon were working on some content for the adilas user's guide. As part of that, they went over a PDF document that was created back in 2011. See attached for the full document. Below is the basic text from the PDF flyer. This is the virtual road map of what happened and why... fun story!

SUBJECT: Start-Up History of the "adilas.biz" Business Platform Quick Overview

Adilas, LLC was officially created in January of 2008. The original partners were Stephen Berkenkotter, Brandon Moore, and a corporation called Morning Star Automotive, Inc. The Morning Star Corporation has since been dissolved (2010) in order to more fully focus on the adilas platform. The actual project began in 2001 as a custom write-up system for Morning Star. Originally, the application was created for the used vehicle and trailer dealership industry.

In 2006, the application went through some major changes when Stephen (Steve) came up with the concepts for adilas. At that point, it started to change from servicing just the dealership industry into a more general or open business model. By the end of 2008 adilas was servicing a number of new clients (besides dealerships) with the following business types: self storage, modular homes, construction, manufacturing, professional services, and retail. As of 2011, adilas has added other businesses such as: virtual finance companies, real estate companies, transportation, GPS tracking, computer services, alternative healthcare providers, fasteners (nuts and bolts), catering, consulting, personal accounts, home-based businesses, etc.

The application or platform is set up for future growth and is very scaleable. It is currently geared towards small to medium-sized businesses. The application is in a constant state of improvement. This includes adding and upgrading features and tools, building reports, and automating existing functionality. Each new tool and/or feature is developed and tested locally before being deployed to live servers. All new tools and features are assigned to a permission on a per user and per corporation basis. This makes it so that only persons and/or businesses that need the new tools turn them on and use them. All unassigned permissions and features are dynamically hidden until assigned. The existing core of the application has been developed and tested over a number of years and is currently on its seventh full version.

The adilas platform is web-based and set up on a series of commercially hosted environments with state of the art data centers and 24/7 support techs that monitor all servers and databases. The application is completely "cloud" based and only requires a computer or a device that can access the Internet. All application pages and web service calls are done over a secure socket layer (SSL) with many other security features in place. Daily back-ups are done from within the hosted environments. Current adilas clients may export their own data and save local back-up files at any time. Adilas also performs its own weekly back-ups and then securely stores files offsite. For more information about adilas, please visit - www.adilas.biz

Going back to the beginning…

Morning Star Automotive, Inc., one of the original partners in adilas, was founded in 1989 by Stephen Berkenkotter and his brother David Berkenkotter. It was a used vehicle and trailer dealership. Over the years, they did well over $100,000,000+ (hundred million) in sales. By 2001, Steve and David had been in business for about 12 years and had 5-6 locations in Colorado. Things were going well and they were quite successful. They were managing their used vehicle and new trailer inventories on a spreadsheet that Steve had created. All of their accounting was done on a separate software system called Peachtree Accounting. All sales were done on hand written tickets and then given to the accounting office for data entry. The accounting department entered all sales and inventory items into the PeachTree Software after the fact. The outlying store locations would save all paperwork and invoices and then send a weekly batch via FedEx or UPS to the accounting department. Morning Star's primary headquarters and accounting office was located in Salida, a small mountain town in central Colorado.

Brandon Moore, another original adilas partner, had just graduated from Utah State University in Logan, UT, in December of 2000. He moved with his small family to Salida, CO in the summer of 2001. He originally moved to Salida to be a professional raft guide and kayak instructor on the Arkansas River that ran through the Salida area. As the summer progressed, work was slim and Brandon was scrambling to make ends meet and to keep he and his family afloat. He found a job listing in the newspaper doing data entry work for Morning Star in August of 2001. Brandon interviewed with Steve and his head accounting person for the data entry job. They offered him the job and he offered to help build the Morning Star website.

Brandon had graduated with a BA in Business Information Systems with an emphasis in Office System Management. Prior to that, Brandon had created a couple of small websites in college and worked as a computer instructor for a local technical college. The accounting staff began using Brandon to do data entry work for the parts department.

Soon after starting to work in the accounting department, the company website became part of Brandon's main job. He began gathering information on inventory levels and items for sale. With so many locations and inventory items being sold on a constant basis, it became almost impossible to keep up with the changes. To make matters worse, the company was constantly transferring a large floppy disk (100 MB zip disk) from store to store to make sure that each location had updated information. The process took about two weeks to make a full circle and then it would go around again. Each time a store would get the disk; they would update their files, add any new items, and send it via FedEx or UPS to the next location. This was a never ending loop with time being one of the biggest variables. Talk about a money pit and literally chasing your tail…

The first step in changing this process was to create a centralized location for the data. One of the sales managers in the Salida office would keep the inventory file relatively up to date by making phone calls and trying to record the data. Every couple of days, Brandon would post the file online with a date to let the other managers know how current the file was. Having the data centrally located sped up the time frame from a two week cycle to just a day or two and totally cut out the next day FexEx charges. Even with these changes, work and efforts were being duplicated. Different salespersons were selling items without others knowing about it and new web page files were being made for items that had already been sold. It became very frustrating as a salesperson would have a good deal on the table just to find out that the item was already committed and/or sold. Deals also went the other way. A customer would ask for something and according to the spreadsheet, it didn't exist, even if it was physically available at another location. Eventually, the need was great enough to drive both Steve and Brandon to come up with a plan to create a dynamic web driven application to track the main big ticket items called stock/units (vehicles, trailers, and toppers).

Brandon went back to Utah on a family vacation and was able to take a dynamic webpage class from the technical college where he previously worked. After the class, he returned to Salida and began working on his very first database web driven mini-application. Its only functions were to track the stock/units (big ticket items), stock items in/out, and mark them as sold (basic inventory tracking). Once completed, the timeline for doing a transaction went from the two days between updates to each salesperson making real-time connections and totally eliminating the old spreadsheet of inventory items. At that point, a number of concepts that are built into adilas started to form. These concepts are enter once, use many, and empower the users at the point of action.

Once the first mini-application was complete, Brandon terminated his full-time employment with Morning Star and became a sub contractor and independent web developer. He started working from home and started his own web-based business and began seeking new clients. Morning Star was still one of his biggest clients, but he no longer worked full-time for them.

As things progressed, more and more options, tools, and features were added to the system. It wasn't long before the operations side (sales) was walking circles around the accounting department. Communications improved, sales went up, and the sales staff loved their new tools. Meanwhile, the accounting department was getting buried and management was looking to add new locations because of improved sales.

Because of the load and stress, the accounting department began to ask for reports with specific dates, data, and totals. Prior to that point, the accounting department had had nothing to do with the inventory tracking system other than the fact that they could login and look at individual stock/units and their histories. A very distinct line was in place and operations could not touch and/or see any of the accounting pieces or functions. Each department only dealt with or played in their department and minimal crossover took place.

As the accounting department slowly began to ask for more and more reports, new tools and new features, the two departments slowly began to interact better. Communications, procedures, and flow started to develop. The commonality became the system. As a matter of fact, they even made the system be the "bad guy" to help spell out the rules and say "No" when needed. If management didn't like what the sales staff was doing, they had Brandon open and close virtual doors to accommodate the correct flow process. More and more permissions where developed to accommodate needs on both sides of the transaction. Real time problems and solutions were beginning to be addressed as they happened.

The operational interface began to lightly feed the accounting department certain values and date sensitive reports. Managers and operations folks began to see numbers and reporting that they had never seen before. A cause and effect cycle began to emerge. This may not seem very big, but it was the start of a huge paradigm shift for the entire company. Managers began watching expenses and taking pride in running a tight store and location. Inventory levels were being tracked, purchases made accordingly and accounting was getting their numbers. Things were starting to flow more smoothly. 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.

The next phase of growth was changing from one corporation into multiple corporations. As the dealership grew, they took on different businesses and acquired others. Steve went to Brandon and asked for the exact same web application for some of his other companies. Each new system needed to be independent so as not to mix numbers and items between corporations. All that needed to be changed were names, locations, tax settings, colors, logos, permissions, and a few other minor tweaks. After adding a number of independent systems, Brandon told Steve that it was getting too hard to keep up with all of the different systems. A single update or change had to be tested in multiple places in order to make sure that it worked with all systems. Users were getting multiple logins to be able to work in different corporations (no cross over existed between the systems). An additional load was added because certain users needed certain functionality in one corporation but not in the other corporations. The current system permissions and roles began to morph into user-specific custom code and began to split the application. More functionality was added but upkeep and maintenance became much harder.

Brandon proposed that they pull back and try to put everything under one roof and build with growth and expansion in mind. This new system could include: multiple permissions that could be assigned to different users by corporation, any number of different corporations, unlimited locations within a corporation, and each corporation could have their own settings and virtual sandbox to play in. To top that off, a bridge or interface could be built to allow a user to switch or cross over between corporations without having to login under that corporation. The entire system would be built on a one-to-many relationship model. Steve liked these ideas and began to think on a more global scale. All of the existing systems continued with minimal enhancements for a number of months.

At this time, Brandon was very involved in a business he had started to teach people how to do snowboarding freestyle tricks and moves through an interactive CD-ROM. Most of his time was devoted to building his own business. He was spending very little time working for Morning Star other than minor special requests. Brandon was looking to have someone take over the work he had been doing for Morning Star as their web developer.

Morning Star needed help with Brandon heading out the door so they hired a new computer guy. Brandon agreed to stay on long enough to train the new guy until he could take over. This required Brandon to dive back into what was going on at Morning Star. About this same time, Steve was dreaming up the concept of creating a "super system" – a web application that could track all of the data for different businesses. He could see the potential of selling this web application as a service to businesses with a reoccurring revenue stream. Steve grabbed the bull by the horns and set up several meetings with Brandon and the new computer guy to share his dream and vision.

It was Steve's idea to begin pulling the operation side and accounting side together like the cogs of a zipper being zipped up until each piece fit in perfectly with the other pieces. Some of the functionality was already in place in a very loose sort of way. Steve had many business ventures (besides his dealerships) in real estate, transportation, small investments, etc. Steve was also in the process of finishing his degree with a dual major in business management and accounting from the University of Phoenix out of Denver. Because of his business knowledge, his entrepreneurial spirit, and experience, he knew that a large gap existed between operations and accounting.

He could envision a way that as he did his day-to-day tasks (operations) that they would automatically show up for roll call on the accounting side of the application. Data would be entered once and then passed along until all of its activity was complete. He wanted to track every penny from start to finish. He also came up with the theory of entering pieces on the operations side and then slowly having them become more firm values, solid dates, and eventually final numbers. He used the analogy of water droplets forming into ice crystals. The droplets start fairly loose (sales) and slowly become crystals, then slush, and then finally becoming completely frozen or iced down. This final output would end up being the actual accounting for the organization. Basically, this was the start of tracking a transaction from beginning to end through its life-cycle. Each key date or status change was flagged and dated and all prior steps were locked down according to user permissions. This became a running history of the objects and data as they moved over time.

About this time, Brandon had a small business loan or note that required a significant payment and funds were tight between trying to push his own products and make the note payment. He began to supplement his normal income by helping to train the new guy and diving in on Steve's idea of this business accounting and operations system (accopps). Within a year, the new part-time computer guy had some family problems and was unable to continue. By this point, Brandon had caught the vision from Steve and both were working almost full time on the project.

All of the existing online systems for the other corporations continued with minimal new enhancements as Steve and Brandon developed a brand new system from the ground up. The new system required a major rework and was purposely built with growth and expansion in mind. Every single page was built from scratch to incorporate the new fields and settings. Scripting and database platforms were changed, servers were added, and the goal began to move toward an open business model instead of just a dealership industry business model. Each new development step opened the vision even further. Ideas and concepts that weren't even possible began to become a reality as the process continued. Cogs of the zipper were slowly coming together from the bottom up.

It wasn't long and the new "Morning Star System" was created. All existing companies migrated from older standalone web applications and started to use the new system. Additional companies and corporations were added under the "Morning Star System" name. No marketing was done and all of the new companies were referrals from current system users. Brandon and Steve were working hard to come up with the next steps and still trying to figure out how to keep pulling the zipper cogs closer and closer together. There were no road maps for doing this. They were truly pioneering ideas and concepts with only a vision, brainstorming, and trystorming (planned experiments) to guide them. The deeper they got, the more they started to see that other companies had the same problems and frustrations that they had already worked through. New companies were ready to pay even though the entire application was not yet finished. A definite "need" was forming.

Steve and Brandon knew that the new system would need a name and would need to become its own company and entity. Over a lunch meeting in Salida, Steve proposed the name of "adilas" which is actually the name Salida spelled backwards. Up to that point, the entire application had been created there in the small mountain town of Salida, CO. The name stuck and an acronym was developed – "all data is live and searchable". As time went on and as each new development step was added to the system, the more this acronym became a living part of the application.

Adilas, LLC was officially created in January of 2008 with the first paying customers in June of that year. Shortly after that, the first paying international customers were added. All in all, there were close to 20 corporations using adilas before it even became an actual entity. All of these companies, from the various industries, had asked to be a part of the process. They were all using the service free of charge up to that point. Each company helped tremendously by providing feedback and ideas that were incorporated into the development process.

The feedback and suggestions from their clients became one of adilas' biggest assets (and still is today). The size and depth of the live test bed was another huge asset that they harnessed virtually for free. It would be nearly impossible for a small company to pay for a test bed of that magnitude. It would have cost millions in research, development, and staff salaries alone. Similar to the cream rising to the top analogy, the ideas and suggestions began paving the way to new features and functions. Over the years, hundreds and hundreds of people have chimed in and made a contribution in one way or another. When asked, Brandon said that "Even our most adamant critics have helped formulate our direction and plans. We are very grateful to one and all. The more holes they would find and point out, the more we just keep trying to fix the problems. It has been awesome!" People from all different walks of life from CPA's, attorneys, bankers, accountants, owners, managers, salespersons, data entry folks, entrepreneurs, and friends have all added their suggestions, ideas, and feedback. Literally hundreds of thousands of hours and millions of dollars have been put into this project. In a way it has become somewhat of a community effort or project.

In seven short years, from 2001 to 2008, adilas went from a mini custom write-up system to a multilevel business platform that is capable of bridging the gap between operations and accounting. The adilas guys have continued to pioneer the way and haven't stopped building. They are working on a master plan that includes a new way of doing accounting called "roll call accounting". This deals with tracking objects and data over time. Operations lead the way and the system is set up to catch and show cause and effect relationships of what was done and how the pieces are tied together. Along the way, each step is dated, flagged, and recorded. The entire story is being captured, mapped, and laid out for users to see. The "roll call" then happens when the user asks the objects and data where they were at any given point in time. The objects and data then virtually respond or report back to the user.

Clients currently use the system to track inventory, manage customers, showcase their products on the web, sell their items and services in an online point of sale system, run retail store fronts, pay bills, track receivables and payables, do their entire backend accounting processes, do payroll, scan and file documents (paperless office), schedule calendar events, run their business, and much more. New features and tools are released almost weekly and the system is gaining momentum and direction. A future training ground called Adilas University (adilasuniversity.biz) is in the works. This will be a dedicated place for training, video tutorials, step-by-step instruction, newsletters, upcoming events, new feature releases, along with a number of other different topics.

The entire application development process is fully paid for and has been through a number of full working releases. It has had hundreds and hundreds of people from different businesses pushing it to see what and where it will go. The story is still unfolding at an incredible rate. The adilas team is still adding new things every couple of days. With each new release, the vision opens up new doors and more options emerge. When asked, Brandon said, "You should see our tick list of where we want to go with this. I can see better training, faster reports, more automation, new custom settings, user defined preferences, and a more visual-type interface. I'm pretty excited about it!" So, it continues… as long as their users keep asking for the next logical step, they will keep building it better and better! The future looks very bright!

For more information about adilas, please visit - www.adilas.biz - If you would like to learn more about adilas, the system, the tools, the theory, the people, please get a hold of them for a free live demo. They welcome questions and love ideas! Contact them at: sales@adilas.biz or 719.439.1761 and ask for Steve.

--- additional contact info: support@adilas.biz - tech support line: 719.966.7102

--- as a fun side note... this document (text above) was created in 2011. Tons of new chapters have been added since then. Today's date is 6/27/19. And so it continues...

Meeting with Mike Rountree, Jim Dougal, Tim Lyons, Gannon, Steve Berkenkotter, and Brandon Moore - Team Herbo

- Looking at options to help do a white label and see what market share they could get to and/or grab

- From seed (starting) clear out to general ledger (full backend/frontend accounting and financials)

- Working with Cory as an adilas rep/consultant

- There are three different things that need to be implemented together

- They have clients in the CBD category - raw material providers, internal manufacturing, packing, distributing, retail, lots of supply chain things, marketing and sales

- They have a distribution category

- They have a retail category

- How do we scope a project? You start on paper. You make a plan, you know the tools that exists, you see what matches, what doesn't, where do you start, and what are the priorities? It comes back to a plan. This could be a flow chart, diagrams, whitepapers, other documentation. It really helps if you have someone who knows Adilas and what tools are available and what tools can flex and change by default. That really helps.

- Some of the tools are different corporations (different worlds), multiple locations within your worlds, what key players (12 main players) play into that model, etc. Steve was also talking about parent/child inventory relationships. Lots of mixing and blending between the things.

- Builds, transfers, phases, locations, sub locations, etc.

- White labeling allows for custom pages and custom code - We have white label theme levels (multi or group level) as well as custom black box code (per corporation or per world). We can customize almost anything. This includes show, hide, look and feel, logic, toggle switches, flow process, requirements, validation, reporting, ect. We use the phrase you dream it up, we'll help you wire it up.

- Cory is great consultant that really knows Adilas. At some point, you will need someone on your teams that really plays the other part of the puzzle. You have to know the client and the solution. Then you mix them together to get results.

- Bring up questions... they aren't good or bad, they are just questions. Get them out there and then see what is needed (easy, medium, more complex)

- Herbo will create some diagrams of what they need and how they want things to play (processes) - Here is the world and here is how the players need to interact

- Training and content - Who owns what, who builds what, who does what? Also, what about passing training and content back and forth? Adilas is willing to provide any thing that we have through database exports, Excel, CSV, XML, JSON.

- Tim had some great questions on the backend stack and server climate. We recommended that he get with Wayne Andersen to get all of the details. Tim has a vast knowledge of backend operations and servers.

- Herbo will be working on some flow charts, processes, etc. They will have a virtual meeting of the minds and making any plans that are possible.

- On the Adilas side, Steve will be working with Cory to help with any deeper consulting info. Steve is a master planner and knows the system front to back and what is possible.

Working with Steve on some JavaScript to help with a new production build (internal builds) page. Lots of dynamic notation. Steve has been working on main flow and carving out some basic pages. He is then pushing things off to Dustin to help shine it up and make it look pretty. Steve wires it up (round 1.0) and then Dustin takes it to the next level (2.0). Good plan.

Eric popped in and had some questions on how to assign his sub special account tracking things to customers, payee/users, etc. After that, he and Steve were talking about future and upcoming projects. Steve was asking Eric about his backend skill sets vs his frontend design skills. We even got into some project management talks as well as backend database architecture. Eric has quite a few skills that are very marketable. We also talked about internal core projects as well as outside custom projects. Good conversation.

Steve and I were talking, briefly, about our direction for the future and near future. Good stuff. Our goal is to keep working on the system, building new pieces, refining some of the older things, putting a new coat of paint on the application (look and feel stuff), and figuring out the master plan of where we want to go. We have so many ideas out in the developer's notebook area... it would be so cool to gather all of that up and really make a plan.

The master plan could include things such as: database structure stuff (world building), graphical homepages, server structure stuff (universe level), fracture account ideas (things that we have learned and ways to break things into smaller and smaller pieces and settings), API socket access points, custom look and feel stuff, 4 different setting levels (corp/world, player/group, page/section, user settings), as well as additional rounds on balance sheet, elements of time, and subs of subs. This could also include all kinds of system stuff such as watchers, feeders, triggers and other ideas that are out there. That would be really fun, a huge project, but really fun.

Need to take tri-storming approach. Taking smaller steps toward larger vision. More success with taking smaller steps instead of the A-Z approach.

https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=fracture this is the future to do list

Currently, the adilas.biz master plan is held in the minds of a few of its founders. It has never been fully funded and written out. We think that would be a great project and could help our existing users, current clients, and even future clients. It would also possibly allow us to get more funding if there was a firm and written plan of what is needed, in the works, and where we are headed.

As of right now, the only written business plan is very general - such as: "We are heading North" (meaning up :))

On the morning GoToMeeting with Russell, Eric, and Steve. Eric and Russell were talking about tons of ideas on loyalty points and gift cards. Both guys have clients who have offered monies to push this project forwards. We are going to be trying to bring them both together to get the bigger master plan recorded and planned out. We will then build towards that and release things in phases to get it up and functional as soon as possible. See attached for a Word Doc that had a number of concepts and specs for the loyalty points and special account tracking stuff.

For the record... Steve said that yesterday he was able to help out Calvin - The grasshopper helped the master. Steve wanted to get that recorded. It was dealing with PO's, subs, and recording things in bulk backend processes.

Also for the record... Steve is saying that he is hearing Russell say "us" more than "you guys". We are happy to have him more and more on the team.

On the theme... We may want a bulk update to help flip users over more easily.

On news and updates... Steve was recommending that we build some standards for what is showed and what is displayed. Russell was saying, let the people write and build them and then let Russell virtually approve and get them up live. We are trying to go more to a template type scenario where we can virtually plug and play. What is it? What does it do? How do I use it? Videos, written instructions, screen shots, etc. Help make it as smooth as possible. Russell also wants all of the key players to help populate some of the features, updates, and help files. It will be a great team effort as it keeps going forward.

On barcodes and populating PDF labels with barcodes, we (Bryan and Brandon) did a job the other day that we had to crop (make the barcode height smaller). That way, we could put smaller barcodes on labels.

We talked about seeing adilas at the 10,000 feet level. Basically, what is the short elevator pitch? Steve and I were talking with Russell about how to present our model, what we do, how we do it, and why we do it?

Two good virtues - Being able to stand for something but still being open enough to listen. If you aren't open to change... how can you ever affect or make changes happen.

Labels are really heating up... We can do custom but we may need to build it so that individuals can do their own things and manage things as needed. We need to empower the users to build and create and store their own labels.