Meeting with both Alan and Aspen. I took some notes and Aspen took some notes. After the meeting, I did some more note recording and note digitizing for 6/15/23 and for 6/16/23.

Alan was on with us for the first hour. Here are some of my notes. See attached for all of them.

- Let's build out the MVP for the plan - general fracture or adilas lite planning session - what documents does that mean and/or require?

- Two of the first main things we want to do is define the jelly fish model (business structure) and the value add-on core model. Those two are some known needs of where we are heading.

- We spent quite a bit of time talking about how to break functionality and features up. We want to keep those separate as far as options.

- I showed Alan the presentation gallery and the outline of the business functions. There is quite a bit of work that has already been done there. Great resources.

- Small packages and/or starting points - We could call it whatever - recipes, packages, templates, industry specific skins, presets, etc.

- Alan wanted us to think about tiers and scaling - both vertical and horizontal. I was thinking, what about the Z scale or the depth/layering axis. Just for fun 3D scaling and 3D world building. It might be fun to explore this.

- We talked a little bit about pricing and tier levels. We would like to set breakpoints, ranges, and fees for going over.

- We asked Alan about his vision for adilas lite and fracture - He is really excited about creating a solution that is light weight and very efficient. In his words, he said, How can I get the most power with the least amount of drag? We went on to talk about hiding things that they don't need and getting them to the meat of the operation as quickly as possible. We will do future planning sessions where we look at each section and slim it down to the minimum or minimal requirements.

- This is a side note, but as I have been thinking about minimal pieces, I keep coming back to a concept that we were looking into called standalone declarations (full entries without any other connections and/or supporting documentation). They exist by themselves but they also may be mapped and pointed to the right place. We could sum them up, count them, map them, and keep it super simple. Originally it was going to be something that could be made for financial documents (P&L and the balance sheet)  but technically we could use them in any way. Simple standalone pieces.

- Spend the time and do some market research on what business verticals we could hit and take care of.

- Lots of talk about automation and even automating the setup of new systems. Let people try things out as a free or limited version. We would setup thresholds, limits, ranges, or whatever. We want people to try it out and like it.

- We talked about ice bergs and mountains (perception of how big it is). We also switched and talked about the depth of the water... pretend levels of swimming - Imagine that you are at the beach - you could get your feet wet, do some wading, swimming, snorkeling, or scuba diving. All at the same place, just how deep and serious are you or what are you looking for?

- Once we have a list of things that need to be done and/or worked on, we get to prioritize that list. What do we want to build out and when?

- Alan had the idea of putting our outline information into a database. That way we could just query things (just in time) as needed. That way we could make the lists super small and then allow for it to be expanded at will. Great idea. Simple displays with drill-downs. Almost the presentation gallery for sales, marketing, pricing, features, and education.

- We also want to highlight future plans and what is up and coming. We change things all the time. Make that part of the plan and the part of the presentation. Put it in a database and let our users pull back what information they want and/or need. Self-building templates, feature lists, tiers, and other levels.

Working with Danny, Sean, and Shari O. on the rafting site (demo site). They, especially Danny, were requesting and wanting some kind of SOP's (standard operating procedures) or some kind of a quick start guide. See attached for our notes. New notes are at the bottom. Mostly the session was just checking in and some light communications for today.

One of my observations is we have things all over the place. We have things inside elements of time, in physical notebooks, in emails, on adilas university, on YouTube, in help files, on different google drives, and the list goes on. We have a ton of resources, but they are not yet linked, cataloged, and organized for use. It's too spread out. That would be an awesome project to get all of that together and available to the public. That could be a future fracture type project. Training and education are huge spokes that we need in our wheel. There is a whole other side to this thing and it's on the education and training level.

Totally random, but a fun side note or thought - Think how cool it would be to go through the different system players (all 12), all of the different system business functions (12 of those as well), and the underlying core concepts. That would be awesome. Beginner, intermediate, advanced, and deep dive or backend levels. Show how things act, cause and effect relationships, where they show up for roll call, how things happened historically, how they effectually show up for roll call, and even how they financially affect inventories, banks, P&L's, balance sheets, and other financial relationships. That would be sooooo cool! I would love to work on that project.

I would love to get into the how, why, and what we are doing. The how and why really seem like fun topics. The "what" is pretty normal but allow us to do the other parts of the puzzle or passing the data along the virtual data assembly line. Getting into 3D world building and all kinds of cool stuff. So many things that we want to do and build. We just need help getting to that next level.

I woke up this morning dreaming about adilas and what value it brings to the table. I went downstairs to record a couple of thoughts and ended up staying down there for a quite a bit of time, just recording ideas as they came to me. I then took a small notepad of post-it notes upstairs and kept coming up with different ideas. These could be expanded upon, it was just a quick, record what thoughts are coming to your mind, type of thing. I had all of these little one-liners written on about 9 pages of post-it notes. Kinda funny.

- 20 years of experience

- 250 customers

- Working model

- Trained team

- Data like crazy - tons of it

- Usage patterns

- Able to handle multi-industries (business verticals)

- People use it - daily

- Success stories from some of our clients

- Database model and database schema (what rows, columns, tables, indexes, data types, records, values, etc.)

- Code repository (huge code base)

- 10 full versions with back-ups of each version (over time)

- Documentation (things written, recorded, and organized)

- Commercial product

- Developer's notebook - full story and all that we have learned

- Able to do custom out of the box

- All of the custom code (as an asset)

- Plans for fracture (upcoming and future project)

- Established billing and revenue

- R&D and prototyping

- Graphics, visuals, and other artwork (even sketches)

- Presentation gallery - Full presentation ready gallery for business functions, attributes, key players, and core concepts

- Concepts - these are worth more than our code

- Pioneering paths and ideas

- Over 6.5 million in sales

- Willing to push the limits and try new things

- We know the pit falls, the costs, the good, and the bad - we've been playing in this arena for quite some time

- No one else is doing what we are doing and how we do it. Our approach to bring operations and accounting together is unique.

- Our story is fully recorded

- Reoccurring model and reoccurring revenue

- Support a team of 15-20 individuals and their families

- Thousands of users that use it every day

- Refinement and bug fixes

- We've built and maintained this application - we know what it takes

- We are doing it - following a dream

- Tons of video recordings and trainings

- Knowledge and experience

- Minimal debt

- Generating revenue right now

- Plans and vision for the future

- 40+ servers

- Ok with being who we are right now

- We don't have to have every client - Ok with serving those who like what we do

- Relationships with clients, vendors, 3rd party solutions, users, and team members

- Tons of intangibles

- Ecosystem

- 12 main players, 12 business functions, 12 core concepts

- Data assembly line

- 3D World building concepts

- The concepts are worth more than the code - We are one of millions of possible options vs everybody will go down the main primary path that leads to what we are doing and trying to do. If they (any other company or software system) choose to follow us, they will come down the core paths that we have found and are exploring. These are the core concepts that we are built on. There is tons of room down here (like exploring a giant cavern with tons of off shooting tunnels and shoots).

- We keep taking the next little step and keeping linking things together

- The depth of what we do and what we cover

- High-end software as a service (online SaaS model), we cover anything to do with operations and accounting, we have a standard package and can built out custom on top of that.

Shannon and I spent the session working and formatting the presentation gallery outline. We also tried to add some new images to help break-up the space as well as a small intro into business world building (towards the bottom of the page). See attached.

Here is some text on world building. Just for fun.

Moving Toward Full World Building

If you cut through all of features and bullet points above (pretend you are looking at all of the presentation gallery outline stuff) the end goal and idea is for you to be able to solve any of your business needs. A good portion of what we offer and peddle are hope, vision, potential, and making your dreams become reality. 

This is why we are trying to introduce world building. The concepts of 3D World Building or Business World Building have been in the works for years. Adilas didn't start out with world building as the main goal. It kind of evolved from just taking one step after another, trying to solve our own business needs. 

The goal is not just the operations, accounting, or the data. The goal becomes capturing the story with all of the details and interactions. It is the story that brings the dates, times, numbers, locations, and groups together. 

Mixing all of the pieces together gives the values (data) or players (characters - pretend like it is a game) life or almost a personality. For example: Say all you know is we have $5,000 on 25th of October. That doesn't mean that much if that is all you get. But if you knew that the $5,000 on the 25th of October came from 20 different invoices at a single location that were collected and then deposited by John. That helps tell the story. Say you also had all of the underlying details of what each invoice was holding, what each customer bought or purchased, how much money was paid and how much was still owed... You could see inventory levels, notes, histories, trends, states, statuses, and other important details. Now you are getting a story. That is the goal!

Shannon came on at 11 am, but I was still working on the code merge for Steve. We got started about 11:30 am. The whole session ended up being somewhat of a training exercise about mapping out the system and what progress we have made over the years. My goal was to help Shannon as she was going to be meeting with Jonathan and doing some training for him. After Steve and I's meeting the other day, we would like Jonathan to keep going along the lines that he is working and work on mapping out the pieces.

Going back a long ways, we started out in 2010 (October 2010 ish) doing a mapping project that lead to some major discoveries. We came up with the interactive map and tons of other good needs and ideas for the future. That was literally a springboard into some of our current projects and direction. Here is a link to the interactive map graphic.

https://data0.adilas.biz/top_secret/images/help/big_map_layout.gif - interactive map graphic (2010)

Next we got into what we ended up calling the core layout or GPS core. This is a spiral navigation wheel or a core shot of a world. This graphic started to bring in concepts of world building and almost a space type theme. Here are a couple of links for these graphics.

https://data0.adilas.biz/top_secret/images/help/adilas_gps_layout_big.jpg - GPS core layout map (2013/2014)
https://data0.adilas.biz/top_secret/images/help/adilas_gps_layout_plain.jpg - core only
https://data0.adilas.biz/top_secret/images/help/adilas_gps_layout_world_building.jpg - world building levels only

The next level was dealing with the core interface, deeper world building concepts, with different modes or levels (data mode, work mode, usage/stats, settings, permissions, learning, concepts/theory levels). This one only got to the graphic stage, we really wanted to build it out into an interactive navigation model, but only prototype graphics were created. Here is a link for some of these graphics:

https://data0.adilas.biz/top_secret/images/adilas_gps_core_layout.jpg - GPS core layout with different modes (2015)
https://data0.adilas.biz/top_secret/images/adilas_gps_core_layout_white_label.jpg - GPS core layout - white label (2019)

The other thing that we have always wanted to do was use and show some graphical homepages. Basically, have some kind of primary navigation that is really easy to use. As the users leave the primary dashboard and/or navigation, have them land on a graphical homepage of sorts. Each of these sub homepages would be a landing spot for the subject and/or topic at hand. For example: invoice homepage, deposit homepage, expense/receipt homepage, inventory homepage, customer homepage, etc. There are even smaller and more specific homepages that are sub to some of these bigger homepages. They could use some fun graphical interfaces as well. We still want to do this, we just haven't had the time. Here is a link on some of the research and ideas on the graphical homepages.

https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=graphical%20home - research on graphical homepages out in the developer's notebook

The next level is trying to get the whole system or platform into a deeper 3D world building level and using the concepts of the data assembly lines. That would be really cool. Here are a couple of other links that play along those lines:

https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=3d%20world%20building - research on 3D world building
https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=data%20assembly%20line - research on the concept of a data assembly line

Here are some other fun graphics - just concepts:

https://data0.adilas.biz/top_secret/images/help/tools_magic_square.jpg - magic square - invoices, PO's, deposits, and expenses
https://data0.adilas.biz/top_secret/images/help/adilas_3d_world_building.gif - concepts of 3D world building
https://data0.adilas.biz/top_secret/images/help/adilas_dream_it_up.jpg - 4 step - dream it up process
https://data0.adilas.biz/top_secret/images/help/adilas_dream_it_up_white_label.gif - 4 step - dream it up process - white label
https://data0.adilas.biz/top_secret/images/help/location_model_landscape.gif - What you get with adilas - map overview
https://data0.adilas.biz/top_secret/images/help/adilas_map_layout_all_business_functions.jpg - business functions overview using the map layout
https://data0.adilas.biz/top_secret/images/help/adilas_gps_layout_all_business_functions.jpg - business functions overview using the core layouthttps://data0.adilas.biz/top_secret/images/help/adilas_core_map_combos_all_business_functions.jpg
- business functions overview using both corp and map layouts

All Business functions: - all business functions - shown in the core - show on the map - show using both core and map

1. Sales, Inventory Tracking, & POS (Point of Sale) - core - map - combo



2. CRM (Customer Relationship Management) - core - map - combo



3. CMS (Content Management System) - core - photo galleries - map - combo



4. Online Expense Tracking - core - map - combo



5. Payroll & Timecards - core - map - combo



6. Calendar & Scheduling - core - map - combo



7. Create Data Relationships Between System Players - core - map - combo



8. Backend Office & Accounting Functions - core - map - combo



9. Histories & Reports - core - map - combo



10. BI (Business Intelligence) - core - map - combo



11. Web Presence & eCommerce - core - map - combo



12. Virtual Data Portal (Big Data) - core - map - combo

11.7 - Old School Accounting vs. New School Accounting

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

OLD SCHOOL ACCOUNTING

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

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

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

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

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

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

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

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

NEW SCHOOL ACCOUTING

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

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

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

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

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

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

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

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

-The other analogy is the data assembly line

-WORKING, CONCPETS, IDEAS:

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

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

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

-Horse & cart analogy

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

4:17 PM

Brandon Moore

/// notes from the adilas history bio

- corps, locations, users, permissions

- web-based

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

- Internet came into play mid 90's

- gathering information into a centeral location

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

- start with your pain points

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

- letting operations lead

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

- pain - load and stress

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

- permissions and opening and closing virtual windows

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

- one-to-many relationship model

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

4:17 PM

Brandon Moore

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

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

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

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

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

-Ideas/Concepts from History Bio Article:

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

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

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

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

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

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

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

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

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

At some point, we want to circle back around and rebuild a bunch of the pieces and how they act and interact. We would like to call this new rebuild "fracture" or something to that effect. Anyways, here are some brainstorming ideas on the fracture pieces that we would like to sew together. No specific order:

- object oriented approach (objects and data over time)

- use teams and different talent pools

- ice berg vs mountain type analogy (what is being exposed and what are the perceptions - visual exposure)

- settings and different setting levels (corp, group, page, user)

- subs... of sub (everything is fracturing into smaller and smaller pieces) - plan for it and embrace it

- API socket connections and external work flow options

- database scaling (corp-specific databases or corp-specific database tables)

- real in-line database extensions (add/edit/remove database fields and help them flow through the whole system)

- 3D world building - keep going and building out these ideas and concepts - one step at a time

- data assembly line(s) - concepts of tracking phases, grouping, sub locations, allowing flex and checkpoints, permissions, mapping to financials, etc.

- using time or elements of time as a base level and then mix, blend, and share sub functionality and tracking options (more objects and data over time stuff)

- funding and making sure we can fund the planning, design, and development of our game plan

- help files, videos, and SOP (standard operating procedures) - standard and custom

- black box and ways to customize the pages, verbage, logic, and process flow

- summarized data (aggregated data) vs transactional data (all the steps and transactions) - we need both - watchers, feeders, and triggers

- following and dreaming the dream - it may sound way out there... but following that dream is huge

- make a visual plan

- include general testing, unit testing, validation (local and serer-side), and standardizing requirements

- version control and deployment

- going back and doing research and review of older notes - tons of mini gold nuggets to harvest from doing this over the years (make sure and harvest some of our own ideas)

- use of sub homepages and graphical hubs of sort - also use graphics, charts, graphs, and other elements

- summed up data with drill-downs or searches available (basic or advanced) - approach all most everything from a summed up version into a more expansive (expanded) view and/or format

- be able to export any data to CSV, Excel, PDF, and general web format

- smaller mini functions - getters and setters - for miniature database access and updates

- use sub flags, tags, and other similar features - lots of ideas about sub phases, sub groups, sub locations, sub flags, sub tags, sub progress, etc. Lots of prior documentation on elements of time and subs of time, including how to virtually adopt functionality between main player groups (invoices, deposits, expense/receipts, PO's, customers, parts/items, stock/units, vendors, employee/users, quotes, elements of time, balance sheet items, etc.)

- custom look and feel - able to match moving trends

- responsive (able to change size and layout based on device or screen size) - mobile development

- sales - how are we going to market and/or sell our products and services - how are we going to set things up for correct billing and tracking (usage, storage, bandwidth, queries, connections, data, files, images, etc.)

- communications, push/pull notifications, automated things, queues and scheduling tasks, bulk and individual communications

- good project management

- sub permissions - almost down to the function type level (as needed)

- dynamic verbage, custom layout(s), dynamic link builder (favorites), and simple look and feel

If you are looking for other ideas for the fracture account stuff. See this URL or web address: https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=fracture

Keep following up on graphical sales flyer, custom emails, and adilas market.

Shannon and I started re-watching the video of Kelly Whyman doing a presentation from the Denver training event. See this element of time and look for the afternoon video on day 3 - the actual start time of the Kelly portion of the video is at 2:33:19 (ish) - https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=3957

- One of the first things that she does is get the physical process that really happen and then she breaks those values into a work flow and defines who is going to do what?

- Setting and maintaining the expectations. Owners and operators are different. If things are too complicated, they, the users, stop putting things in.

- There are those who are good at frontend, backend, and maintenance. Different skills, talents, and interest levels.

- Shannon and I talked about "getting an investment approach" where the clients see what other successful people do. This was talking about other skills such as training, setup, maintenance, consulting, overseeing, etc. Ongoing help and other services.

- The setup and initial portion of the client's implementation is very important. They may need some ongoing oversight and/or help. How am I going to support you to get to your goals. Ongoing relationships.

- Try to operate out of the box first and then customize from there. Sometimes they jump too early on the custom bandwagon. Everybody loves the idea of custom but it can be a two edge sword. There might be a difference between small customization vs full or huge customization.

- Are you really ready to take on adilas? Is this the right system for you? You have to really want this (data feeding game). We talked about can's and should's... cost/time analysis.

- Maybe a way we can differentiate ourselves is based on concepts. We love talking about 3D world building, systems, interconnected data relationships, digital story telling, permissions & settings, and objects and data over time. There is an older PDF flyer that has a fun math equation of :: "Results = Mix(Functions, Players, Concepts)". See this older flyer for more info: https://data0.adilas.biz/adilas_formula.pdf - Good stuff.

- Sell the sizzle

Anyways, Shannon and I only made it part way through the video from Kelly. We had some good talks and we have some homework to keep watching and taking notes. We will touch base again next week on Tuesday.

While I was looking through some older papers, I saw this graphic. I'm not sure if it was ever pushed up online. It has a date of 1/11/17 and deals with adilas world building concepts. These are things like: 1. Adilas Universe Level (all adilas systems), 2. Galaxy Level (linked servers), 3. Cluster Level (individual boxes & servers), 4. Solar System Level (databases inside of the boxes or clusters), 5. World Level (corporations and/or companies inside of a database), 6. Location Level (sub areas within a corporation or company), 7. Group Level (any of the 12 main system player groups), 8. Individual Level (actual players or individual items within a group), 9. Data Level (how and where things are stored and what relationships exist between the pieces), 10. Run all levels over time (foundation concepts of time, space, and money (resources) that make up 3D world building).

The attached image is of the first few levels (universe, galaxy, cluster, solar system, world).

9009 E Arapahoe Road, Greenwood Village, CO 80112
Phone: (303) 799-4555

See attached for notes, scans, files, and GoToMeeting recordings (videos)

--------------------------------------

Day 1

We did some intros and then got started. Danny Shuford did a demo and did a great job. See attached for some notes. Here are a couple of the highlights from what I took away from it.

- Solution for solution minded people

- It can be molded to fit your industry

- Changes keep happening

- Big open view of the whole system - it wasn't made for just one industry

- Brief overview of the framework

- Based on user permissions and valid logins

- All web-based and cloud-based

- Features and benefits - focusing on the benefits

- CRM - log notes, additional contacts, photos, and other media

- We all deal with money, but in the end... we are all dealing with people

- Note to me... Danny went into the customer table and doing the custom page settings on the customer fields. This is for things like the name, aliases, sort value, show/hide, etc. We really need to keep pushing that idea and concept forward. People really want that level of control. It just takes a ton of work to cascade that through the full system.

- He talked about news and updates

- "Our Interface" - what do you want? We don't have a single set interface, we let you choose

- Customer queue

- Lots of moving parts

- Drea - "Adilas is play dough"

- Inventory tracking

- Reporting and building your own reports

- Labels and changes to the requirements

- ecommerce

- Payroll

- Accounts payable and accounts receivable

- Print checks

- emails

- Customize and working with the developers

- Security and back-ups

- Steve - Showing some hidden gems

- Small demo on flex grid

Next, I gave a small section on the adilas model - core concepts - and intro to world building. I will upload my outline. I'm also hoping to upload the video as well. I don't have any notes because I was the presenter, but here is my rough outline:

- We will be bouncing around

- Start with a guy holding tons of stuff

- Talk about the needs and how to organize things

- Go over different tools... head and mind, paper and pencil, word processing, spreadsheets, databases, software packages, web or hosted solutions

- Go over systems and how things start to inter-relate

- Cover the 12 main players

- Cover the 12 business functions

- Cover the 12 main world building concepts

- Mix and blend to get the desired results

After lunch, Alan Williams did a presentation on highlighting and exploring new features. He started out with a fun group activity and a game of sorts. Minimal communication and we had to figure out a path through a virtual mine (bomb) field. It ended up having forward steps, side steps, back steps, etc. We eventually, as a group, got through the mine field. Really fun exercise and it opened up some conversations. Here are some notes from Alan's presentation:

- Little active - mine field - group activity - finding their way

- How does this relate to the adilas process?

- He then showed some of the steps that we have taken to build the application

- Side steps, back steps, and forward steps

- Going into advanced add to cart and sub functions

- Request from the group - no standalone discounts - Make that a permission and/or a setting. Standalone discounts can and do cause tax problems.

Next, Steve Berkenkotter lead an open Q & A section. The first question was asking about any updates with the Metrc (state compliance and tracking system for Colorado). That got pretty deep but exposed some of the challenges that exist between connecting and maintaining dual systems (adilas and Metrc). Here are a few notes:

- Questions on Metrc

- Some new tables and new limits from Metrc

- Auto processors - running nightly stuff to help sync data between systems

- API and server to server connections

- Challenges that exist

- Mixing old and new functionality

- Transfers

- Sales

- Using elements of time to track states, status, phases, and groupings

- Getting back at the data - reporting

- High level vision

- Question from Pat - 280E - new tax and accounting rules - what can we write off as cost of goods? What about unitizing expenses?

- Steve - How the IRS is looking at things and expecting things

- Steve - loves numbers and how he brings his skills to the table

- Work in progress - attributing a value as part of the accounting

- The progression of building and breaking

- The system is able to store the data (huge piece of the puzzle)

- The system may be customized to get the data back out and/or to get the data in (another huge piece of the puzzle)

- Template building

- A consultant spending time and configuring a system before it is released to the end users

- Small questions on CSS and changing certain page colors

The last section of the day was a presentation on historical stepping stones - what have we learned and why do we do what we do? I did this presentation so I will add my outline. Once again, we are hoping to get some videos uploaded to this element of time incase someone wants to watch the videos. Here was my outline:

- Where did we start? Spreadsheets, static web sites, zip disks and sending inventory around from place to place

- Fixing current business problems

- Where is your pain? Start there

- Letting operations lead - Use the adilas interactive map to help show flow

- At some point, accounting will need to follow

- Checkpoints and flowing data

- Gap between operations and accounting - drawing the gap, horses and carts, and old school T accounts - light history of accounting

- How does time play into the mix

- Comparing operations and accounting in a static environment

- Comparing operations and accounting in a dynamic environment

- Progression - drawings of the data assembly line and how it ended up at a 3D data assembly line

- 3D world building - x=time, y=resources, z=space or depth - draw out the box or cube

- Black boxes & white label options

- The whole deal

We didn't quite make it all the way through the whole outline, but we covered a good portion of it. Towards the end, we went around the room and got some feedback. Those documents and notes will also be uploaded. The final request from the class was to have adilas allow the "adilas version" spreadsheet to be shared with the world. It was originally created in order to get a bank loan, but Steve said to release it to the world. Great meeting and good energy on day 1. Good stuff.

--------------------------------------

Day 2

We spent most of the day working on and going over inventory tracking and point of sale (POS) features. See the attached videos. We also had some great demos from Calvin Chipman on building custom labels and one from Dustin Siegel on some new code and features that help with plant phases and cultivation. Here are a couple of notes from some of their presentations. For a more complete version, you may need to watch some of the videos from day 2.

- Calvin and the adilas label wizard - He gave a slide show and then started to interact with the label builder. After he was done, we asked him to show some of the behind the scenes pieces of his label builder. Good stuff.

- Vaporware - the product doesn't fully exist (yet) - part concept, part actual, not yet fully functional

- User designs the label (step 1)

- User selects the label from inside of adilas (step 2)

- The label(s) are created and displayed on the fly, based on stored instructions, mappings, and special code. (step 3)

- Part of the demo was showing sheet labels with a data merge, labels with barcodes and QR codes, static text, dynamic text (user can interact and change things), data mappings, graphics, etc. Pretty cool.

- Small talk about PDF's, Flash, & HTML and CSS - printing options from the web - Our choice is PDF currently

- Interacting with printers, browsers, and other hardware pieces

- PDF - actual size vs shrink to fit size

- Questions about font point size and possible limitations for compliance reasons - We will leave that up to the users, that way we don't have to chase all of the compliance rules and regulations.

- We talked about settings and maybe limits that could be stored and looked up on the fly.

- Possible template options

- Be careful saying a compliant label

- A good disclaimer to keep things legal according to the local and/or state requirements - put the liability back on the companies and/or users.

- Small story of a company and internal programming wars and war stories - Different places that Calvin has worked.

- It may take a hybrid solution of both software and web

- Small demo of the actual builder - Calvin is going to be taking that and putting it more into a wizard-type format. Currently, you have to be pretty techy to use it. Round 1 - prototype.

Dustin gave a presentation on some new cultivation processes and some dynamic mapping. We had some technology issues, the demo was going slow (Internet) but the concepts were awesome. Imagine going from a manual one-by-one process, to a bulk streamlined process. Huge time saver, plus tons more data points, capturing the whole story clear down to minutes, seconds, locations, phases, etc. Pretty cool.

--------------------------------------

Day 3

Busy day today. We got into sub inventory, why we do sub inventory, customer relationships, elements of time, flex grid, ecommerce, custom emails, group mass texting (GMext Pro), and a presentation by Kelly Whyman (super power user from the Denver area). We are going to be posting the videos and the notes from the day. Good sessions. Here are some of the notes that I took while others were presenting. Once again, see the attached media/content files for videos and other digital notes.

These are some notes from Shari O.'s presentation on CRM functionality

- CRM - The real acronym stands for Customer Relationship Management - Shari O.'s acronym for CRM is - Can't Remember Much - pretty funny

- Good data in = good data out - Fill things out completely and make sure you get good data in

- The client log and how to use it

- Leaving personal footprints in the sand - using the log

- Addin gin a user-maintained history... internal communication

- Cover you own rear-end

- Being business appropriate - have good manners when recording details and data points

- Custom emails

Drea did a demo on how to show/hide transfer packages inside of the adilas/Metrc inventory pages. Here are some notes from that:

- Transfers in and out and how to hide things

- Everything in adilas is flexible

- This new functionality is only a week old

- Talking about manual clean-up and automatic clean-up - doing side-by-side comparisons

- Using the data tables and being able to sort and search data - almost on the fly - re-writing the page based on the data.

- Some of the new CSS cards, tabs, and such - really look super cool and it seems more intuitive - it also makes it look more modern.

- We would love to keep adding new data tables and more options

- As we keep going, we may need more clean-up options

Calvin game a PowerPoint presentation on GMext Pro - This is his group mass texting solution. He did a great job and I think that people really liked it. Here a few notes that I wrote down.

- Pretend like you are a client

- Communicating to a large group or large groups (plural)

- Pitching GMext Pro - great demo and presentation

- Some of the stories of huge companies and how changes have happened and how those big companies weren't able to keep up. WordPerfect and Blockbuster were some of them. Major game changers entered the market and could do things better, faster, and cheaper. People gravitated to those new options.

- Technology happens... embrace it and thrive

- Mass texting and single text notifications - similarities and differences

- Phones and phone numbers - with mass texting, you are basically buying phone numbers so that you can send more texts at a time. Each phone number can only send 1 text per second. So you may need 5, 10, 15, 20, 25 phone numbers to get all of your texts sent out.

- Problems with people giving out the wrong phone numbers (bogus numbers or wrong numbers) - that can break your marketing campaigns - too many wrong numbers and you get reported as a spammer.

- Ways of opting in and out

--------------------------------------

Day 4

Final day of training for this go around. We started out day 4 with a group session on tips, tricks, and best practices. We spent quite a bit of time going over settings, permissions, and parent attributes for items. Steve then did a whole session on the three main parts of the balance sheet (assets, liabilities, and equity). The topic was intro to adilas backend office and functions. Steve took the words backend office and tried to flip it to - let's put the owners in the driver seat vs trying to drive from the back of the plane (pretend they are trying to fly the plane from back in the bathroom with the doors closed). Great session.

The afternoon session was talking about BI - Business Intelligence & Big Data. The group talked about databases, data, and how to both get data in and out of the databases. Lots of fun examples. We then has some other Denver power users jump in and do demos on tiered pricing and smart group buttons, and another one on the process of doing a full inventory reconciliation and full inventory count. Great info and good sessions.

The final session was supposed to be on the adilas model - vision, future, and wrap-up. We were all too tired, so we just chatted and went over a bunch of the things that we learned from the training session. We got some great notes and tried to clarify a few items, topics, and concepts. Pretty casual ending. Great people, wonderful ideas, excellent participation, and memories made. A great training session. Here are some of the notes that were taken while others were presenting:

- Molly presented on parent attributes for items - think of tag or ways to categorize things

- On parent attributes - for example: say you have an item but want to show different brand names or characteristics - Say you are selling shoes... You may want Nike, Converse, Adidas, etc. Or running, walking, hiking, trail running, etc. These would be good parent attributes or tags.

- Parent attributes are huge for ecommerce searching and creating tags for different items

- Russell did a great job on so many different features - we would love him to keep building more features

- Easy setup

- Building your own little shortcuts

- Parent attributes are used for labels, sales, ecommerce, searching, filtering, etc.

- Treat parent attributes like a way to build your own database... eight use the flex grid and the custom fields or use parent and sub attributes.

- Both parent and sub attributes are unlimited and they have a proper data type such numeric, dates, text, toggles, and drop-down lists. That really helps when putting data in and also when querying the data to get certain results back.

- As an idea... what if we build out both parent attributes and sub attributes to all 12 main player groups, inside of adilas. You literally could build your own one-to-many database relationships. The main 12 player groups are deposits, invoices, users, vendors, customers, stock/units, expense/receipts, balance sheet items, elements of time, quotes, PO's, and general inventory items. Currently, parent attributes and sub attributes are only available for parts or general inventory items. Think how cool that would be if we pushed it to the next level...

///////////

- Small note from a meeting during one of the breaks... what is the internal adilas funnel to report an error or a bug? Who gets put on that project? We need to figure out our own process and communication funnel.

- Bryan and Molly and others... funding some of the consultant projects - what is the short list and then where are things at. Basically, what do we have to work on and what are the priorities of those pieces?

- Shannon may be part of this funnel that we are trying to build out

//////////

Back to the main training even... The next session was Steve Berkenkotter and Shari Olin - going over financials and adilas backend office functions. Steve pretty much ran with this subject and did an hour long power session on the three main parts of the balance sheet (assets, liabilities, and equity).

- CPA homepage interface

- Inspecting what we expect - you have got to look at what is being delivered as a final product (actual items and/or tasks or services)

- Going back to the beginning - balance sheet homepage

- When you get a new system, we setup a default bank and default location

- Problem with batching... Say trying to remember 30 days back and/or not getting data and information for a long period of time. It kinda leaves you guessing and/or missing some of the details

- Steve - Think of flying a plain... try to be ahead of the plane... where is it going - often pilots try to think 3 tasks ahead of what they are doing

- Views of the balance sheet - a trial balance - working and checking mode

- Assets, liabilities, and equity

- We covered the difference between the income statement (P&L - profit and loss statement) & the balance sheet

- Values and tax laws

- Depreciation and schedules

- Life cycle - length of the life of an object and/or an entity - time and a schedule to lower a value (usage & wear & tear)

- The IRS has setup the tax game... They want you to play and even play up to the lines that have been setup - think of a game - play to the line

- Where you put things in very important

- Small discussion on double entry accounting - history and pros and cons

- Skate to where the puck (hockey) will be

- The formula is the most important part of it

- Passing things like a hot potato... basically moving things along the data assembly line - roll call accounting

- A balance sheet is a snap shot in time

- Talking about the profit margin and where does that come in to play

- Small holes in the ice - things that are either gotcha's or thin ice (not all the way done)

- Some of the guys and gals were saying that we need - big dumb animal pictures - super simple instructions

- Accounts receivables - Think of that as they have your inventory or they have your endeavor (a promise to pay for something) - basically, they owe you money

- You have to know the story - sometimes the numbers tell the story but sometimes the story tells the numbers what they mean

- Liabilities and hidden liabilities - be careful there

- Hidden costs

- Triggers

- Payroll and payroll taxes - this is a huge sink hole

- Sometimes we can't do things due to the technology - as that opens up, we have more options

- Auto processing and calculating needed values in non-peak times that could then be available for other reports

- Fall backs, redundancy, auto-syncs, and re-syncs

- Turtle up, sometimes the servers will shut down and pull in their legs - kinda like a turtle protecting itself

- We need an all encompassing system to help steer the ship - think platform or system

- Owners - who holds the liability

- Steve - analogy of the tail wagging the dog vs the dog wagging the tail - who is in charge & which way do things flow?

- The owner needs someone who is a decision maker and/or gate keeper

- What is the game plan and do you have buy in?

- The POS (point of sales and inventory tracking part) is only a small part of the puzzle. Very small compared to the whole business realm (world).

- Abundant model - you have to imagine a line of people wanting your services and standing in line - next, next, next

- The backend - really, this is the pilot's cockpit and/or the driver's seat

- Absorption (in take) model & attributing sub costs over time

- Dustin - I want "this" (meaning adilas & underlying data) to argue with my boss, not me.

- I need a business tool & now I can run faster & better - thank you

- Equity

- Net Profit - it comes from the P&L - one of the only connections between the income statements (P&L) and the balance sheet.

- Investment - how was this company funded and/or formed?

- Fracture - just having fun - it keeps doing it (fracturing) on its own... maybe let it keep going and play accordingly

- Change "backend office" verbage to the cockpit or balance sheet.

Towards the end of the day on day 4, we had a couple of power users show some demos and such. We had Josh do a presentation on my cart favorites and smart group buttons (tiered pricing). Drea made a suggestion that you make the pricing tiers as dummy proof as possible. They even pushed the ending values clear out to show a visual warning to the person using the buttons. The other major request was for this feature (buttons and tiered pricing) was dealing with allowing these buttons to be time sensitive for sales and promotions.

We also had Drea go through and show an inventory update and how she does a physical count and then an inventory clean-up. She would pull reports, export data, show/hide columns, add columns, print things out, and have her people go work. Then she showed how the system would take those over and short values and push them through an update PO (internal tool for updating inventory counts). Pretty cool. As we go along, we will need more clean-up tools.  Clean-up tools make things look better and help to give users a peace of mind. We also talked about trust issues and how sometimes it is tough to trust and/or trust people. All of that plays into the mix.

My final note about the training sessions is that those who played with us, live and online, really had a good time and we all learned a lot. Good times, great food, and wonderful people. Inspiring sessions. If you want more details, check out the media/content pieces (notes, excel docs, scans, and videos for more info).

On the morning meeting with Steve and Dustin. I spent some time getting back into the developer's notebook project. We are trying to get some our brainstorming and info out to the world so that we can protect things like business or 3D world building, business or 3D data assembly line concepts, and other core adilas concepts and pieces. There will eventually be tons of different options, as far as code and application features go, but we really want to protect and help educate the general public about the core concepts and pieces that we are built upon. That is a huge part of the goal.

Helping Dustin get some custom labels going and helping to populate them. We had to fix a number of small coding issues. Good learning session.

Talking with Russell. We talked about some small billboard sites and pointing people to adilas and the adilas community. We talked about SEO (search engine optimization) and using existing verbage to help lead them to what we have and what we offer. For example: Things like CRM (customer relationship management), POS (point of sale system), ERP (enterprise resource planning), CMS (content management system), etc. Point all of those things to where it is going... We are leaning towards 3D world building, data assembly line stuff, new school accounting, and other concepts.

From our talks yesterday, these are some other projects that Russell thought would be cool. They are: a cool mobile app, more with time clocks, time - reservations and rentals, and other mobile ready pieces.

Alan hopped on and we went over progress on the in-line dollars off discount project. Alan is making great progress and we talked about a couple questions that he had. We also lightly touched base on the reoccurring invoicing and reoccurring merchant processing pieces that he is working on for Campaign Rise. Good reports.

Most of the session was spent working on the sales tax calculator page and showing the test calculations and output math.

Chatted on the phone with Calvin going over API socket connection for his desktop application. Also did some light planning for the upcoming live adilas training session. Here are a couple of random notes... no special order at this point.

- Sell the sizzle...

- Think GEO tourism for selling the venue and location of Logan, UT. 1.5 hours North of Salt Lake, hiking, fishing, history, USU campus, shopping, mountains, rivers, valley, Bear Lake, etc. 10 minutes from Logan, you could be in the mountains.

- Guest speakers - concepts, vision, processes, procedures, etc.

- Highlight new features, new updates, and upcoming projects. Think of things like Campaign Rise (social media and custom wire job for elements of time), Beaver Mountain Ski Area and Ski School, Steve's campground stuff, Plant phases and cultivation stuff, Russell's new custom email stuff, ecommerce, WordPress integration, white label stuff, sales tax changes, new discount options, etc.

- Show what has happened, what is happening, and what will be coming down the pipeline. Maybe show a timeline with some key points and historical stepping stones.

- World building concepts and how different clients are problem solving with adilas as their worlds change and progress. Try to focus on 3D world building and the concepts of the data assembly line. Show how some of that stuff is already playing out.

- Different topic, but I would really like to get some sites out there like billboards pointing back to adilas and what we are doing. These are all of the main concepts such as 3D world building, data assembly line, creating a system, API sockets and playing at the wall, etc. These might be great projects for Russell to give his developers who are going through the program at Bridgerland. Good stuff.

Talking with Russell over the morning meeting. He was showing me around the new news and updates pages. Lots of new tools and features and ways to showcase features, benefits, advantages, support items, and topics of interest. Good stuff. Russell is also putting a really nice flavor to the new graphics and such. He is taking things to a much higher level. That is awesome.

Russell and I had a pretty good conversation about the direction that we want to take. We both talked and expressed that we want to keep adilas as a general tool that could be used by all kinds of businesses and individuals. We talked about an analogy of a tree with roots and branches. Our goal is to keep things balanced. I asked Russell to help steer us in that direction. I gave him a thumbs up and the verbal go ahead.

As a side note, our developer's notebooks and meeting notes have a virtual gold mine of information, ideas, lessons learned, and vision for the future. We need to slow down enough to tap into that resource. It is huge and covers almost 20 years of experience.

Alan popped in and we chatted for a bit. We went over some our upcoming plans and how we are going to tie things together. Basically, we'll keep pushing on in-line dollar off discounts, other discount rules, and then finish up the sales tax piece. We will then roll into options to expand the my cart favorite buttons and turn that portion into the pricing engine or the foundation of the pricing engine. That will naturally tie into sales and promotions and such. We'll have Eric working on loyalty points and gift cards and special tracking accounts. In the mean time, we'll circle back around and help with sub inventory and mini conversions. Ideally we'll also have Calvin working on the foundation of the label builder pieces. Once we get all of those pieces in and stabilized, that should really help.

Alan would also like permission to setup a testing server environment. We talked about using the adilas content server as that environment. Good stuff. We need to test and be confident that things will work in live scenarios, especially with the new database changes and world building stuff that is coming up.

As we were talking, Alan would like to build in some testing and more active object oriented stuff. This means more session based stuff, classes, objects, functions, getters, setters, etc. Piecing things together and combining like code into families and related code sets. Alan and I also talked about how we really want to tie in to time and elements of time as part of the object oriented model. We went out to the developer photo gallery (old drawings and graphics from the developer's notebook) and talked about how huge the time element is to the whole project. We also lightly talked about 3D world building and concepts of the data assembly line. Good conversation.

Spent the rest of the session paying bills, recording notes, and doing emails and tech support stuff.

• Corp Id or World Id Number
• App Type Id (2=Deposit, 3=Invoice, 4=PO, 5=Expense/Receipt, 6=Balance Sheet Item, 7=Stock/Unit, 8=Customer, 9=Vendor/Payee, 10=Employee, 11=Part, 12=Element of Time, 13=Quote)
• Main Id - What is the corresponding main id number to create the main id and app type id combo? These combos deal at the data level for the data item. For example: App type 2 and deposit number 50. That makes a specific named deposit. Or app type 3 and invoice number 700. That creates an invoice entity or individual. Or app type 11 and part id number 1000. This would be how the system would talk to and/or communicate with a part number or item (general inventory item).
• Sub Id - Optional. This would be a sub id number if we need to connect to a sub. If not, it would be left at 0.
• Table Name - This would be a string or text value that would help us know what table we were talking about. This helps us possibly connect an unlimited number of subs or sub tables.