Search The Adilas.biz Developer's Notebook
Time Period:
Daily (enter the day you want to see)
Monthly
Custom Date Range to
Template Filter:
Color Code:
General Text Filter:

(use a plus "+" sign to separate search terms. ex: jack+jill+hill)
Sort Value:
 
Adilas.biz Developer's Notebook Report - All to All - (98)
Photos
Time Id Color Title/Caption Start Date   Notes
No po photos available. Click to view time details.
Shop 10359 Organizing notes and prep work 7/26/2023  

Multiple sessions. Organizing my notes on digital storytelling into blocks. Tallying which core concept each note or sub note was tied to. I've been working on this prep work for a conference talk that I may be giving. I've been on and off this project for a few days now. Here is a link to element of time # 10355 to see all of the notes, scans, brainstorming, and organizing that I was trying to do. Fun little project.

 
Click to view time photos.
Shop 10355 Research on digital storytelling, world building, and concepts of the data assembly line 7/26/2023  

Title: Exploring Digital Storytelling - Benefits of going beyond the data

Description: Everything has a story to tell. What if you could help your data start talking back to you (nicely)? Wouldn't that be awesome! Imagine asking something like this: What's your story? Who created you? Where have you been? Where are you headed? Who are your buddies? Where do you belong? When did you finish? In this session, we will be exploring the 12 core concepts of digital storytelling. We'll discuss real world examples of how using these concepts can bring life, depth, and value to your data, apps, systems, and platforms.

Outline:

Here are the 12 core concepts of digital storytelling:

  1. Capture & Record The Story
  2. Groups, Players, Individuals, & Characters
  3. Relationships
  4. Trouble, Problems, Pain, Needs, & Goals
  5. Decisions & Choices
  6. Consequences (cause & effect)
  7. Accountability
  8. Permissions & Settings
  9. Systems
  10. Vision & Future Developments
  11. Tech, Tools, & Maintenance
  12. Tracking Objects & Data Over Time

Other things that I would like to cover:

  • Systems thinking approach
  • Success isn't a destination, it's a journey!
  • Finding success along the way
  • Everything has a story to tell
  • All the W's - who, what, where, when, why, wHow :) - just being funny!
  • World building
  • Digital assembly line concepts
  • Tying everything into the 12 core concepts of digital storytelling

References:

I've been studying and using some of these concepts for years. See attached for some of my notes. In my notes, I took pages and pages and boiled them down into a smaller list of key points. Each main point is numbered and underlined. For reference, the numbers look like this: #2.8 or #4.5, depending on which document the idea or point comes from. I may refine it further, but this is the rough draft.

Below are the links to the original docs in digital form (no mark-up, no numbers, no underlining on the originals).

Number #1 - Submission to speak at an Adobe ColdFusion conference - link

Numbers #2.0-#2.13 - Text from the business zipper website on the about us page - link

Numbers #3.1-#3.17 - Text from the old adilas.biz website. You may have to scroll down to see the text. - link

Numbers #4.1-#4.51 - Core concept document - taken from the adilas archives - still partially unfinished - link

 
No po photos available. Click to view time details.
Shop 10354 Research 7/24/2023  

Going over the adilas core concepts document. Prep for a talk on digital storytelling.

 
No po photos available. Click to view time details.
Shop 10266 Editing a document on adilas core concepts 6/21/2023  

Digital storytelling - using data and drill-downs - to tell the story. See attached for a multi page document that Shannon and I were working on (a couple of years ago). I was proofreading and doing some editing on it. Not sure why, but I was thinking about this older document and decided to reread and revamp it a bit. See attached for where I'm working at - still under construction.

Communicating with Hamid about meeting next week for lunch.

The document has an analogy of how people use a video recorder to record and duplicate scenarios and actions. As part of the analogy, it relates what adilas does in the digital storytelling to help with full world building. I thought that it was kinda fun. The document goes pretty deep. Spent lots of time rereading, adding and taking away little bits, and doing some proof reading. Only got about half way through it.

As a fun side note, I sent it to a contact, even though it wasn't fully finished. Trying to get the word out.

 
No po photos available. Click to view time details.
Shop 10058 Intern meeting 4/20/2023  

Meeting with Hamid. He was showing me the progress on the business zipper website that he is building (small side project). I gave him the URL for our old site and told him to read the bottom portion that talked about the concepts of the business zipper. Here is the link and some of the text (you have to scroll down to the bottom portion of the page to get to this info).

-------

Older website text

-------

Many people over the years have asked us, what do you guys do? Why do you do that? Where are you trying to go? How long does that take? How can you do such and such and others can't? And what makes you so different? Those are some great questions. The answers vary depending on the time someone is willing to listen. :) This is somewhat of an inside joke, but sometimes we feel like saying "Did you pack a lunch?", meaning it can get pretty deep pretty quick.

To answer plain and simply, we are in the business of tracking people's data. We are a virtual data portal. The word "data" means different things to different people. The word "adilas" also means different things to different people. To some it may be CRM functionality (Customer Relationship Management). To others it might be inventory, sales and POS information (Point Of Sale). To others it might be ERP (Enterprise Resource Planning) or backend office functions. To others; general operations tracking, JIT inventory tracking (Just In Time), manufacturing, online expense tracking, business intelligence (BI), paperless office, document management, a CMS (Content Management System), financial data and reports, paperwork, payroll, timecards, scheduling, etc. Because we say we track "data", we need to be as deep and diverse as the term itself.

Our goal is to help you, as a user or a company, get in, get out, and be happy. Along the way, and depending on what you consider to be data, we try to help show you the whole picture of what is going on. If what we have helps you out, great! If not, that's ok. We enjoy sharing what we have learned. The adilas.biz business platform is a huge integrated tool set that allows you to play in multiple different areas. It is very scaleable and caters to custom settings and different permission levels. Your use of the system, depends on you and your needs.

The words "system" or "platform" denote more than one piece working together in harmony. A full system allows you to do things that others can't do, simply because everything may not be there.

One of our biggest strengths is helping you get your data into the system. Once in, it becomes part of the big picture. Data coming in usually means some form of "operations" or the day-to-day business that happens. We love this and have a strong focus on helping on the operation side of the equation. We try very hard to follow a logical or linear model in helping you to get your data in and out of the system as quickly and easily as possible.

We also offer some great backend office tools and accounting features. If truth be known, the reason we are able to offer you accounting-type features is directly related to how we track your data and help you do your operations. We, at adilas.biz, are actively working on a new and more modern model for accounting as compared to the current, somewhat antiquated, double entry accounting system embraced by most companies. We can run your operations regardless if you use adilas for your accounting needs or not. If you are looking for a traditional credits and debits accounting system, we may not be your product other than for your operational needs. However, if you are willing to try a more modern and nontraditional approach to accounting, you will love what we do and where we are headed. Straight up, it is new and different and we are still pioneering on a daily basis.

Here is a little background on the traditional double entry accounting model that dates back to the fifteenth century (500+ years old). Luca Pacioli, an Italian monk (friar) wrote one of the first math text books called "Summa de Arithmetica". In that book he explained about how the Italian merchants kept track of their sales which we now call "double entry accounting". This guy was a genius and a math wizard for his time. Here is the kicker, this text book came out in 1494. Two years prior to that, Christopher Columbus, in 1492 sailed the ocean blue to show people that the world was round. People were just coming out of the dark ages and entering into the age of the Renaissance. The only way that businesses could track their "data" was in giant notebooks called journals and ledgers. They had large rooms with tons of paper copies and went through different processes of recording, adjusting, and posting their data between the different journals and ledgers. Sound familiar?

Basically, they were trying to track different states and statuses of the data. Some of the processes that they used to track these changes and states of the data were called "debits" (negatives) and "credits" (positives). These debits and credits were added to things called "T Accounts". The different T Accounts made up a bigger thing called the "Chart of Accounts". The Chart of Accounts usually had a numeric value and a name associated with it. This is how they tracked things, on paper and in different notebooks. These Chart of Accounts were then added up and used in financial documents called the "Income Statement" (profit and loss statement or P&L) and the "Balance Sheet". The goal was to make sure that everything got recorded and accounted for. In order to make things balance, they had to do one entry on one side and then a matching entry on the other side of the T Accounts. Thus the term "double entry accounting". This standard has been followed for years and is currently the accepted way to do accounting. As a mater of fact, most computer systems that do some form of accounting, have basically computerized the 500 year old model and added their own little tweaks to the process.

So what makes us so different? Well, we spent the first five years working on operations. The original goal had nothing to do with accounting. The goal was to start tracking inventory and other data. We wanted to be able to quickly view things, pull reports, and even be able to show where that data was or what had happened to it over time. Through a step-by-step approach to solving our own business problems, we stumbled upon a new way of doing accounting. Basically, once we had the operations in place (this is a big key), we just kept asking the question, what happens next? We would then build the system out to that level. As we kept going, the path began to be rolled out and we just kept taking the next logical steps. This process took years and years and was only possible because we kept working at it. Concepts that were only a dream or a wish started to be right in front of us and we simply reached out and grabbed them.

Adilas can virtually track objects and data over time without using the old double entry accounting model. We still simulate some of the pieces of that model, but we do not have any journals, legers, T Accounts, Chart of Accounts, and other standard accounting features that are considered traditional requirements. We don't use the words debit or credit and we try to use as few adjustments as possible. We use technology, good data, flags, dates, checkpoints, approvals, permissions, and business mapping to run things in a linear fashion. Every entry or data object has a life-cycle and we simply track it. We are then able to go back in time and virtually ask the objects or items questions. What's your story? Who created you? Where have you been? Where are you headed? Who are your buddies? Where do you belong? When did you finish? What is your value? And the list goes on. We call it "roll call accounting". At the end of the day, we still produce an Income Statement (profit and loss or P&L) and Balance Sheet. We just arrived there through mapping data and running objects over time.

We are still pioneering and developing steps to the roll call accounting process. We've had a blast creating it and we can't wait to share it with you! Although our accounting system is not completely finished (fully automated to the highest level), we have had many companies happily use it for years. We just keep adding new pieces that make it better and better. Remember, our main goal in providing the adilas.biz system or platform is to help you track your data. Adilas can help you with your operations, accounting, or both. The model is open and flexible.

We invite you to check it out. We would be happy to meet with you in person or give you a live online demo. Give us a call TODAY! Call 719.439.1761 and ask for Steve or email us at sales@adilas.biz.

If you want more information, there is a brief history document of the making of adilas at the bottom of the page. It is a short 6 page read that tells the story of what happened when and who was involved. It has been a wonderful journey thus far and we're still going!

Just for fun, we wanted to list a few of the core concepts if you don't want to read the history document. This is just for fun... :)

When we first started, back in 2001, our original goal was inventory tracking. As things progressed, one of our main goals was to figure out a way to help fill the gap or create a "bridge" between operations and accounting. There seemed to be a very large and visible disconnect between what was happening in the field (operations) and what the final output was (accounting and final numbers). In one of our brainstorming meetings, we came up with the analogy of a "zipper". One side of the zipper was operations and the other side was accounting. Our goal was to start bringing them together one cog at a time, like a zipper being pulled upwards until it came together.

We came up with the theory "track every penny in and track every penny out". With this thought in mind, we started to track each penny from start to finish. What we found was that every transaction had a life-cycle that it went through. We decided to enter the items and data as easily as possible on the operations side and then track it through a number of steps until it found itself finished or completed. Along the way, we started time-stamping each step with a flag and a date. Each flag and date combo became what we called a "checkpoint". As each new flag was added, we would lock the prior steps below that based on permissions.

This process of passing data from checkpoint to checkpoint, based on permissions, is how we track your data. A great analogy of this process is if you imagine what it takes for water to turn into ice. This process doesn't happen all at once, it needs to go through different phases, states, or status levels. As your data passes through these different phases, called checkpoints, we simply help you flag and date the data as it runs over time. Just like the ice analogy, the water droplets are very loose at first "operations" and slowly become crystals, then slush, and finally become completely frozen or ice "final numbers and accounting".

We then use a process called "roll call accounting" to virtually map backwards in time to where the data was at a given date or time. Another synonymous term for roll call accounting is data mapping. The reason we use the term roll call accounting is because that is what we ask the computer to do. Imagine data that is flagged and dated as it goes through certain checkpoints. Pretend that the computer is an army General giving out a roll call or a flag/status report. The computer says, "I need all of the invoices that were not fully paid at such and such a date to step forward". Only these invoices would then be counted - based on flags and dates. You could then use the computer to do the math and give you the totals you need. Each time you want more information, you simply tell the computer what criteria to use for the roll call and eventually it will tell you the story of what is going on.

To sum things up "literally", by keeping track of your normal day-to-day operations, we can get very complex results like aging, histories, usage, reports, final numbers, and accounting. Thus the accounting becomes the date sensitive sum of the details. These values are what make up your "Business Intelligence (BI)" or "Big Data" concepts. It all comes back to managing and tracking your data. Because every piece of the puzzle still exists in the database, you are able to virtually go back in time and see what was where and when it moved out of each checkpoint. If the data is correct, let it flow. If a modification is needed, make the correction, lock it down, and let it keep flowing. The accounting becomes more of a check and stamp of approval rather than entering numbers from different journals or locations. When you put it all together, what do you know... All Data Is Live And Searchable.

 
No po photos available. Click to view time details.
Shop 9576 Working on the rafting demo site 11/15/2022  

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.

 
No po photos available. Click to view time details.
Shop 9085 Signing up to be a possible speaker for a conference 5/31/2022  

I got an email about an Adobe ColdFusion conference coming up in October. As part of the email, they were requesting people who wanted to speak and/or present. I decided to put my name into the mix. I would really like to be able to pitch the concepts of world building and the concepts of the data assembly line. I sent them links to our website and also a link to an adilas origins - core concepts document that Shannon and I worked on at the beginning of the year.

 
No po photos available. Click to view time details.
Shop 8904 What brings value - small list 4/7/2022  

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.

 
No po photos available. Click to view time details.
Shop 8463 Work with Shannon 1/20/2022  

Going over some of the origins doc that we just finished. Talking about adilas core concepts, plans, business plan, heading toward fracture, budgets, and small teams. We also talked about optimizing vs maximizing and pros and cons there. How do you implement change? What is the cost of transitions and switching gears?

Here are our current priorities (just for Shannon and I - where we are heading):
1. Budgets and getting cash flow under control
2. Plans - business plans, investment pitch stacks, and planning out fracture.
3. Back to the adilas core concepts and new content for articles, user guides, or other docs.

 
No po photos available. Click to view time details.
Shop 8495 Adilas Time 1/19/2022  

Both Sean and Danny joined in on the meeting and were checking in this morning. We spent a little bit of time and went over some of the intro to world building stuff that I sent around yesterday evening. This is the small five-page doc that Shannon and I have been working on for the adilas core concepts - origins doc. Anyways, we had some fun discussions about some of the concepts. My goal is to keep introducing some of these pieces, one piece or step at a time. I think that the full-blown concept of world buiding or business world building is too deep for people to get right off the bat. However, as they learn about it, I really think it helps them envision possibilities and creates the "why" for what we are doing.

Eric joined and we went over some progress on the sales tax aggregate project. We have learned some big lessons on this one. Anyways, I think that he and Wayne have had some great meetings and have a good plan in place. One of the things that was happening was cross merging. We had some hidden first round pages and prototypes in place on the master branch. Then as new development would happen, even on a different branch, we would merge in the master code branch to keep it up to date. The problem was, the true older code was on the master branch and so it kept overwriting the new development. Anyways, I think we got it figured out. Lots of cause and effect things. It also brings into light the need for a manual touch vs just letting the code or applications do everything automatically. All part of the learning curve and what it takes to have a master code branch, a dev testing branch, and keeping everything straight and still up to date. Lots of challenges.

One other topic that Eric wanted to bring up was a communication platform called "Discord" and how it may help us connect and interact better. We currently use GoToMeeting for online meetings. We also have a number of folks who will pop out to Zoom sessions or whatever. Eric is going to look deeper into Discord and then give me a small walk-through to see if we want to switch and check things out there for some of our meetings and communication needs.

After everybody left, John and I were talking and going over some of his skills and how diverse they are (backend, servers, IT, graphics, frontend UI stuff, and modern trends and strategies). He also has done some managing and admin level stuff in the past. A good mix.

 
No po photos available. Click to view time details.
Shop 8658 Catch up and clean up 1/18/2022  

General to do list stuff. Checked on a bug, pushed up a new video recording, reread a page that Shannon and I were working on - dealing with the origins of adilas core concepts and how that ties into world building concepts. See attached for a copy of the document.

 
No po photos available. Click to view time details.
Shop 8456 Work with Shannon 1/18/2022  

Overarching concept of world building and finishing up the adilas core concepts - origins document. Shannon and I worked on the conclusion and the first couple of paragraphs to help tie the whole document together. See attached for our finished first draff copy of the document. We may end up adding pictures and such to the document later on. The main goal right now is dealing with the story, the history, the verbage, and the copy.

 
No po photos available. Click to view time details.
Shop 8454 Work with Shannon 1/13/2022  

Work session to work on the conclusion or wrap-up for the adilas core concepts origins document. We've been working on this one for a while now. It is getting really close, we just need to refine a few things and button it up. See attached for our progress on the document.

 
No po photos available. Click to view time details.
Shop 8457 Work with Shannon 1/11/2022  

Hour long work session with Shannon on the adilas core concepts origins document. We had a bunch of extra ideas and text, but we pulled it out and moved it over to another document. We are trying to wrap up this document and create a good lead in towards the other documents that will be needed. This is not done yet, but we are creating some new content. See attached for our progress.

 
No po photos available. Click to view time details.
Shop 8458 Work with Shannon 1/6/2022  

Re-reading the adilas core concepts origins document with Shannon. We were working on the section that talks about why and how we have used world building (concepts and theories) to help us build up what we are doing. We also were moving some teaser type content from one document to another. Basically, some good stuff, but it just didn't fit in the current document, but we didn't want to lose it. Lots of reviewing pass entries, lists, notes, scans, and pulling out small gems. See attached for our progress.

 
No po photos available. Click to view time details.
Shop 8460 Work with Shannon 1/4/2022  

Touching base and catching up after the Christmas holiday break. Shannon and I did a work session on the verbage and copy for the adilas core concepts origins document. We are right in the middle of an explanation of the concepts of world building and how that concept has influenced us, as a company. Fun stuff. It's good to be back working on this content. See attached for where we are at in the process.

 
No po photos available. Click to view time details.
Shop 8459 Work with Shannon 12/16/2021  

Work session with Shannon. We were reviewing some of the verbage and copy for the adilas core concepts documents and coving some origins of how we got introduced to world building. See attached for where we are working. Today we started into the section dealing with how learning about world building has influenced our decisions and direction. Lots of brainstorming today. We'll keep refining it until it fits in with the rest of the story. As I think about it, the concepts of world building are huge in what I do personally and what I'm hoping to help our company do as a whole. It, being introduced to those concepts, was a paradigm shift for me and adilas. Kinda fun to rehash some of that.

 
No po photos available. Click to view time details.
Shop 8462 Work with Shannon 12/14/2021  

Working with Shannon on some verbage and copy for the world building piece inside of the adilas core concepts and origins section. It's not finished yet, but here are some things that we are working on: See attached for the other parts of the story.

So, what is world building? And how does it relate to business software? We would like to answer this in three different ways. First, we would like to answer the question. Next, we would like to explain it a little bit further and give some examples. Lastly, we will try to explain how it has influenced our decisions and direction as a company.

1 - Answering the questions, what is world building and how does it relate to business software?

World building is the process of creating a unique environment for each business entity.

Often software tends to be built for one industry specifically. If you only have one industry, the whole package is built to support that business model, or world, and there is no need to diversify it. But what if the software package allowed you to diversify it to all kinds of business models and verticals. This allows you to customize the environment to meet your needs.

As you setup and create this unique environment you end up answering a number of questions. Some of these questions could be where are you located at? Does your business deal with time, products, services? Who are your customers? What do you call them? Members, clients, patients, students, etc. Basically, you are determining what you want your world to be like and what you want it to do. The Adilas system is flexible and able to handle all kind of choices and decisions. As you mix these together this is what creates the customized landing area for your data. As soon as you can start seeing that every single business is technically a different world - it starts making more sense.

2 - Explaining world building further and giving some analogies.

The author who introduced us to the concept of "World Building" was Brandon Mull, a New York Times bestselling author. He was giving a presentation for young writers and artists at a university and one of the co-founders and his children happened to attend the seminar. In his presentation on world building, he stressed 5 key components. They are characters, relationships, trouble, decisions, and consequences.

To further explain this concept here is a small analogy, or example, he gave as part of his presentation. A good science fiction author may come up with the concept of a flying car. But a really good science fiction author thinks at the level of world building. What are the causes and effects that occur with having a flying car? What is the technology that allows that? What are the traffic laws? What things keep it in check? What happens if there is a traffic jam? A wreck? How are they powered? How are they stored? How are they fixed? What are their speeds, capabilities? Are they armed? Etc., etc., etc.

Think of your favorite movie or book. What different things make up the environment that makes it unique and special? Some of the best books and movies are those that are able to create an environment that is so rich it almost feels like a real place you can be transported to and participate in.

These same concepts apply to the Adilas application. Imagine one of the richest environments you will ever use, ready to run standard out of the box, or customize it to meet your business needs. Think of custom naming conventions, toggle options on and off, settings, permissions, tons of tools and business functions at your disposal. The ability of the Adilas system to adapt to any business world is incredible! That is what Adilas has been created for.

To start your mind thinking along the lines of world building, here is a little exercise. Consider answering some of the following questions whether you are creating a world for storytelling, or creating a world for your business entity:

General World Building Questions

- Where is your world located?

- What special features does your world have?

- What does your world have an abundance of?

- What does it have a lack of?

- Who is on your world? Different civilizations? Friends? Enemies?

- How diversified are the civilizations, areas, or locations?

- What are the reasons they are separated or diversified?

- Who are the characters and the groups?

- How will they interact with each other?

- What kind of things are they trying to overcome or accomplish?

Okay, now let's transition into business world building questions:

- What do you call your business?

- What type of business do you have?

- Where is your business located?

- What is your company size? Mom and pop, small, medium, large, enterprise, custom?

- What do you call the people who work for you and work with you? Salesperson, staff, associate, team member, or whatever you may call them.

- Are you doing things alone or as part of a team, department, etc.?

- How many different locations do you have? What do you call those? Locations, stores, clinics, departments, jobs, facilities, or other?

- Who are the people that buy your services or products? Clients, customers, members, patients, students, etc.

- Do you sell labor, time, services, subscriptions, perishables, non-perishables, little items, big items, bulk items, serialized items, or custom?

- How do you distribute what you are selling? In-person, online, call-in, internal manufacturing, wholesale, delivery, etc.

- What are your pain points or challenges?

- Do you have certain processes or a special flow in your business world?

- Do you already have certain pieces in place and need another software to fill in the gaps? Do you need the whole package? Are you required to use certain software or applications?

- Do you have state, government, or industry requirements?

- Do you have paperwork, documents, forms, scans, contracts, or other files to capture and record?

- Thinking of data and reporting needs. What do you want? What do you need? What key data points are you interested in?

- What are some of your goals? Financial, physical, personal, etc.

Still working on content below this, but having fun... :)

 
No po photos available. Click to view time details.
Shop 8251 Work with Shannon 12/2/2021  

Work session between Shannon and I going over more changes and content for the adilas core concepts and the intro to world building document that we are working on. Fun work and brainstorming session. We talked more about the MVP model and options to getting things to the "sufficient" level. See an earlier entry from today to see some other comments on MVP models. See the attached document for our progress from today.

 
No po photos available. Click to view time details.
Shop 8242 Work with Shannon 11/30/2021  

Shannon and I were working on the adilas core concepts and intro to world building document. We added in some new analogies and verbage today. See attached. Making progress.

 
No po photos available. Click to view time details.
Shop 8245 Work with Shannon 11/18/2021  

Shannon and I had a good work session on the adilas core concepts and introducing the world building concepts that we got from Brandon Mull, a New Your Times bestselling author. Funny story, we actually got the concepts of world building from a presentation that Brandon Mull gave to middle school writers and artists in the Logan, UT area. Here are my notes, back in 2013, from that event. Fun memories. See attached for where we are at on our progress.

Emails, follow-ups, and calling the bank. Other little to do list stuff.

 
No po photos available. Click to view time details.
Shop 8255 Work with Shannon 11/16/2021  

Good work session with Shannon. We were refining the adilas core concepts origins project. Coming up with verbage and copy for introducing the concept of world building. See attached for our progress.

 
No po photos available. Click to view time details.
Shop 8248 Work with Shannon 11/11/2021  

Working with Shannon on editing some new verbage and storyline content for the adilas core concepts origins document. See attached. Working on the part where we were introduced to the concept of "world building" and business world building. Trying to show the tie-ins between the concept of world building and how that relates to custom business software. Good work session. Making progress.

 
No po photos available. Click to view time details.
Shop 8244 Work with Shannon 11/4/2021  

Working on content and verbage for an article we are writing (Shannon and I) dealing with the origins of the adilas core concepts. See attached for where we are at. Shannon and I were exploring on where, why, and how some of those core concepts came to life. We weren't planning on getting into all of this stuff like super deep custom business software and theory, but... The core concepts sort of just fell into our laps. We just picked them up and mixed them together... We didn't come up with them, but we sure have been grateful for them. The results are the lessons that we have learned and where we are trying to go and head.

Gratefully, the core concepts have been one of our best guiding lights and we are very vested in them. He/She who masters the concepts, masters much. They are kind of guiding us along this path and journey. I personally love learning and really enjoy talking about, teaching, and brainstorming on the different topics and subjects. I've been in and through many of these situations, scenarios, concepts, and topics. I've lived it, to some extent. I'm still learning, but loving it. I love talking about world building concepts, 3D data assembly lines ideas and ways to implement things. I've also really enjoyed brainstorming on other 3D business world building ideas. Shannon and I were talking universe level, galaxy level, cluster level, solar system level, word level, locations, groups, individuals, data, and running all of these different levels over time. So many different levels.

Fun stuff like 3D data levels (x=time, y=resources and money, and y=space and depth (layering, stacking, details, relationships, etc.). Good stuff.

As part of our research today, we were talking about more world building stuff and how all of that (those concepts) came to be. Once again, we didn't come up with them, but we for sure will help be a spokesman for the subject and topic. We love it! We were discussing the idea of learning and then protecting things through sharing of intellectual property (IP) stuff. That feels like one of our roles. We learn it, then we share it. If we just keep it to ourselves, no one else will gain from it. We really want to share and protect these pieces. Here is an article (developer's notebook entry) on intellectual property and ways of sharing to protect things. I feel driven to help educate, demonstrate, and protect some of the main core concepts and ideas that we, adilas, are founded upon. It give me purpose to try to play a role with these things. Good stuff.

 
No po photos available. Click to view time details.
Shop 8246 Work with Shannon 11/2/2021  

Work session with Shannon on the adilas origins story and how to help introduce concepts for the adilas core concepts origins document. We are currently working on showing how the process of trying to teach the system to others has opened up our vision and helped us to start boiling things down to make it more standard and manageable. Everything that we do and have done has come through a need and series of cause and effect decisions. Fun to see it unfold and see what key choices and consequences have driven us through this entire process.

 
No po photos available. Click to view time details.
Shop 8252 Work with Shannon 10/28/2021  

Work session with Shannon. Going over some of the origins story for the adilas core concepts. We worked through a number of paragraphs and started into a small intro to world building. See attached for where we are working.

 
No po photos available. Click to view time details.
Shop 8250 Work with Shannon 10/26/2021  

Work session with Shannon - going over some ideas and concepts for the origins papers - how did we come up with and/or discover the adilas core concepts. See attached for where we are working. As part of our conversation today, we were talking about chipping away at things, like an arrowhead, one chip at a time. Sometimes, that is the best we can do.

Towards the end, we were doing a little bit of research and I found a number of fun developer notebook entries from clear back to 2010. Here are a couple of them that we were briefly looking over.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=2774 - protecting the core concepts by sharing

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=3681 - huge brainstorming session (from a training event) dealing with the core concepts

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=2279 - brainstorming on core concepts

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=2278 - some analogies about concepts

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=3627 - trying to draw and illustrate some of the concepts

Anyways, a fun session and making progress. One little chip at a time (arrowhead analogy).

 
No po photos available. Click to view time details.
Shop 8257 Work with Shannon 10/21/2021  

Shannon and I had a work session on the adilas core concept origins overview document. See attached for where we are at on this little project. Just for fun, and I don't know if it will happen, but I think it would be cool to write a book and help tell the world this adilas origins story. I would love to include the discovery process and journey of how we came up with these adilas core concepts. This wasn't a list of things we started out doing or thinking about. It really was a discovery process and now, almost 20 years later, we can actually put it in writing as far as what we learned, are still learning, and even hope to learn. No one could come up with this on their own. Not to mention the countless prayers, ideas, inspiration, suggestions, requests, requirements, etc. It, the whole adilas project (whole adilas enchilada) is a conglomeration of ideas, concepts, dreams, exploring, and giving it a go (try-storming - like brainstorming but with action and experiments and learning planned into the mix). What a journey!

 
No po photos available. Click to view time details.
Shop 8243 Work with Shannon 10/19/2021  

Work session with Shannon on some new content for an origins outline and overview for adilas core concepts. Lots of discovery and community involvement to get us where we are at today. See attached for where we are working. Trying to cast a light flavor and hint towards the fable or folk story of "stone soup" and how through sharing, more was accomplished and enjoyed.

 
No po photos available. Click to view time details.
Shop 8240 Work with Shannon 10/14/2021  

Small little work session on the origins of the adilas core concepts. We had a multi-page document of ideas and where we wanted to go. We went through things and cleaned it up and made a really small list of topics for the origins doc. We don't have a lot to show for it today, but we did a lot of cleaning and started into the flavor of what we are trying to do. I also want to go on record that I think that is little project will be fun and has tons of value, if to no one else, it is super valuable to me.

 
No po photos available. Click to view time details.
Shop 8241 Work with Shannon 10/7/2021  

Shannon and I met and finished reading some of the older verbage and origin story (adilas history and overview) from element of time 8089. We were trying to figure out what to help write in the adilas core concepts - origins document. We don't have anything set in stone yet, but doing some planning and brainstorming. See attached for our current progress.

 
No po photos available. Click to view time details.
Shop 8089 Work with Shannon 9/28/2021  

Shannon and I were working on adilas core concepts. We started out and did a small review of the Bear 100 from last week and what we are learning and hoping to do in the future. Kinda fun. We then started in on the primary adilas core concepts. The first one is dealing with capturing and recording the story (digital storytelling). That may seem super simple, but that is a huge part of what we are doing. Our goal, is to go over these core concepts and make a small standalone document for each of the main core concepts. There are 12 main core concepts that we are pitching and hoping will get traction and weight. They are:

Adilas Core Concepts

Why & how does it work? Virtual world building...

1. Capture & Record The Story
2. Groups, Players, Individuals, & Characters
3. Relationships
4. Trouble, Problems, Needs, & Goals
5. Decisions & Choices
6. Consequences (Cause & Effects)
7. Accountability
8. Permissions & Settings
9. Systems
10. Vision & Future Developments
11. Tech, Tools, & Maintenance
12. Objects & Data Over Time

We decided that we may end up doing a preface or lead in before we just jump into the core concepts. In doing so, we were looking at some existing verbage and seeing if we could use it. The existing verbage is already in story and paragraph type form. Just seeing what we can come up with. See attached for what we are working on. Also, I added some sub notes and comments to cover some of the other verbage that we are looking at. All of this verbage is from our older website and some PDF flyers.

 
No po photos available. Click to view time details.
Shop 8092 Work with Shannon 9/21/2021  

Shannon and I met and talked about where we are headed next. We currently don't have any major fires that are blazing, so we looked at our tick list (click to view our current tick list) to figure out what to work on next. It took us a while to figure out which way to jump, but we decided to finish up the new content for adilas core concepts. Along those lines, we took our bigger document (almost 20 pages) and made 12 new files and dumped the raw brainstorming data for each core concept into its own file. We will be going through all 12 of the core concepts and refining things down and making each file able to stand on its own. That's where we are heading.

 
No po photos available. Click to view time details.
Shop 8093 Work with Shannon 9/14/2021  

Working with Shannon. We spent the first little bit going over some highlights of what is going on in different areas. We talked about the presentation gallery, the new facelift for the Bear 100 mobile app, and some other happenings.

We had a conversation about the "stone soup" analogy - bring what you've got and through it in the pot, we are making stone soup. The meaning here, is that, if we are playing stone soup, you can't be as picky as say a high end restaurant. We are looking for progress and refining things as we go. If we had all of the talent and funding in the world, we would play completely differently. Currently, we have to play the stone soup game (more of a community effort or just in time type project) vs other well funded traditional methods and approaches.

Shannon and I talked about changing directions. We were going to be working on refining the adilas core concepts for the presentation gallery (verbage and copy), but they already finished the presentation gallery, so maybe we will jump over there and read through things and try to help there. We would really like that to go live and to be able to be used for teaching, training, and helping new clients and prospects get the idea of where we are headed.

See attached for list of adilas core concepts that we were working on. It's not finished, but a great start. We may try to get back to that later on. For now, we are moving on to the next little fire.

 
Click to view time photos.
Shop 8095 Work with Shannon 9/2/2021  

Work session with Shannon on the analogy and crossover between a video recorder and the adilas recorder or business recorder (the adilas application). Just for fun, I thought that I would attach some of the verbage and copy that we are working on. We are still refining things, but here is what Shannon and I are working on. See attached for more info (still in raw format).

Adilas Core Concepts

Why and how does it work? Every company becomes its own world - virtual world building. What does your world look like?

The 12 Main concepts we are going to cover: 

1. Capture & Record The Story
2. Groups, Players, Individuals, & Characters
3. Relationships
4. Trouble, Problems, Needs, & Goals
5. Decisions & Choices
6. Consequences (Cause & Effects)
7. Accountability
8. Permissions & Settings
9. Systems
10. Vision & Future Developments
11. Tech, Tools, & Maintenance
12. Objects & Data Over Time (Tracking Full Life Cycles)

Small Overview

Concepts 1-6: Elements of digital storytelling - characters, relationships, decisions, consequences, etc. 

Concepts 7-12: Tools and concepts we use to allow, and capture, people's stories playing out on the web/cloud environment. 

Game Changers And The Value Of The Story

We have started realizing that Adilas has created a digital way of recording the story. Similar to what the video camera did in sharing widely with people what was possible; we have started realizing we have created a way to capture and record all of the pieces and relationships in the business environment. Imagine the movie of your business. What would that look like?

From a book called, "The Rise of Superman: Decoding the Science of Ultimate Human Performance" by Steven Kotler, one of his topics was dealing with the role of the video recorder. Before the video recorder so many people did not even know certain things were achievable. Once it was recordable, it could become repeatable. People could share that, study it, run it back and forth, and really get into the details. This allowed others to see what was possible, which produced bench marks and standards that caused people to keep growing and pushing the limits. 

As we were thinking about the ability to record and share content, we thought of some other advancements that have taken place in our lifetime. Video recorders used to be very expensive, now people have them almost everywhere. They are on phones, go-pros, and can be small and hand-held. These video recorders have become very portable, low cost, and widely accessible.  They have become a widely used tool for how people document things.

Another neat thing about a video recorder is that you can jump around the video - pause, record, rewind, go forward, slow it down, etc. On the Adilas side, as you work with the system, everything gets recorded as well. This allows you to have all of your data at your fingertips. You can see the current, real-time rolling data or you can access any data in the past. 

In the business world, there are so many things happening, interacting, and a whole digital story that is unfolding. There are different players and relationships. Resources are going up and down. Things are interacting and being time stamped, tracked, and organized. 

What if you could watch all of these interactions and this story unfold from a bird's eye, high level view? What if you could be on the ground where things are really happening, seeing the causes, effects, and relationships play out? What if you needed more details and you could physically get inside of that piece and see the details and logic? This is ADILAS!

People want to see things tracked the whole way through. Once they understand and see the potential and possibilities of what we are doing with Adilas - they just want more.  What if the Adilas recorder becomes a game changer for capturing your business story? Think of the doors that you could unlock if you had a fully integrated system that works and flows together - the possibilities are unlimited. 

Before you think that this is just a dream - you need to check out Adilas. We have a viable, working solution that does all of this right now! This is a game changer. We will continually be building and expanding on the application but these features are available to use right now! Go, do, build, play, and let's start making those dreams happen together!

 
No po photos available. Click to view time details.
Shop 7877 Work with Shannon 8/31/2021  

Going over the new presentation gallery (test and play mode) that Chuck put up online. Playing with things and going over scenarios with Shannon on how we are planning on using this new tool. Can't wait for it to be all finished and available to the public. Good stuff.

We spent the rest of the session going over adilas core concepts and refining verbage and content. See attached for where we are at.

 
No po photos available. Click to view time details.
Shop 7872 Work with Shannon 8/26/2021  

Work session with Shannon on adilas core concepts and playing more with the idea of comparing Adilas to a video recorder. We are calling it the video recorder analogy. See attached.

Ideas die if unspoken or kept in a dark room, they (ideas) need light (exposing them and talking about them). I was mentioning to Shannon that I've been telling the guys some brief analogies to see how they take them and how they handle things. I have learned a ton by sharing and watching them (reading between the lines) on their take or feedback. Interesting stuff.

Good work session today, re-reading, refining, and trying to get the point(s) across. Still very much in the raw and rough stage, but coming!

 
No po photos available. Click to view time details.
Shop 8133 Recording notes 8/20/2021  

Reading up on adilas core concepts. "He or she who masters the concepts, stands to gain by owning more than just code." - Brandon Moore

Recording notes from the past couple of days. It is fun to go back and relive and reread what goes on day by day. It just keeps going and unfolding. It is also fun to watch for trends, patterns, and breakthroughs. That makes it fun!

 
No po photos available. Click to view time details.
Shop 7882 Work with Shannon 8/19/2021  

Great little session with Shannon. We jumped right in and started reviewing some of what we wrote and added to the adilas core concepts on Tuesday (8/17/21). We reformatted a lot of the verbage and text and really focused on the analogy of the video recorder and how much of a game changer it was to the whole world. We were drawing a parallel to Adilas and the way that the Adilas recorder (for business) works and how you can gain some of the same benefits by harnessing those pieces. We are still working on it, and it's still a little rough, but it is coming.

Think of the angles that we take, the stories and relationships that we capture. We can roll time backwards (that is huge) and forward. We can play at the present, we can allow updates in the past and then let those cause and effect consequences to roll forward, etc. The whole Adilas system is a giant business recorder and translates raw numbers into virtual and digital storytelling. It is pretty cool! You can only do this, if you have a full system that goes end to end. If not, you only get a snapshot or just a portion of the whole. The deeper the system, the more full coverage you get (no dead ends but a full system).

See attached for where we are working. It's still kinda rough, but making progress.

 
No po photos available. Click to view time details.
Shop 8072 Meeting with Chuck 8/18/2021  

Chuck and I started out talking about payables and cash flow stuff. After that we switched over the to the sales and presentation gallery project. Chuck showed me some of the progress that he is working on. One new change is that he has implemented some +'s and -'s (plus signs and minus signs) to help with mini drop-downs for sub or extra verbage. It is looking good and he is making progress. He also reported that he is almost all the way done with the background images and having the different themes stick and play through the entire presentation gallery.

We talked about some new verbage and content for the adilas core concepts. Marisa has been feeding Chuck some new verbage and content. I pointed him to the latest Word document that Shannon and I were working on for new verbage and content for the adilas core concepts. He pulled the document up and we went over some of it briefly. I touched base with him on some of the brainstorming that Shannon and I were doing just yesterday.

Chuck was showing me some training that he is working on and some email campaigns and automation processes that he is researching and playing with. Chuck was talking about using lead magnets (slowly leading the, our clients, to the goal) and using things that we can help them with vs just plain buy our product type marketing. Interesting direction. Also, as you look at marketing, if we can show a need, fill that need, and offer to help ease some kind of trouble or pain, that is very effective. How can we help you? Let us show you how we can!

Along with the email campaigns and automation processes, we talked about controlling splitting paths, following user actions and/or non-actions, and building the automation processes and campaigns based on where the client is in the process.

We then changed directions and talked about bookings and online reservations. We have a client that will need some of these pieces here in the next few months. We talked about some of the new time settings and going over more adilas core concepts and virtual game changers. Both of these pieces are dealing with where we are heading in our world building and digital storytelling processes. I find it interesting that time and elements of time is going to be at the heart of some of these new changes and advancements.

 
No po photos available. Click to view time details.
Shop 7890 Work with Shannon 8/17/2021  

Great little work session between Shannon and I on adilas core concepts. We spent some time looking into concepts of accountability, histories, and how those things interact with permissions, settings, and cause and effect type consequences. We also got into some discussions on flow state, game changers, and virtual data addictions (need and almost a lust for data and what that provides). We were just brainstorming, but we had a great session and made some personal breakthroughs and connections. Great little meeting. See attached for our current thoughts (rough and raw) on the matter.

 
Click to view time photos.
Shop 7887 Work with Shannon 8/12/2021  

Work session between Shannon and I. Brainstorming on adilas core concepts. See attached for where we were working (word doc). Also, we were basing some of our discussion and efforts off of an older adilas formula flyer that shows business functions, application players, and adilas core concepts.

By way of a break through today, we decided that the adilas core concepts have two main categories and underlying groupings. Here are the 12 core concepts:

1. Capture & Record The Story
2. Groups, Players, Individuals, & Characters
3. Relationships
4. Trouble, Problems, Needs, & Goals
5. Decisions & Choices
6. Consequences (Cause & Effects)
7. Accountability
8. Permissions & Settings
9. Systems
10. Vision & Future Developments
11. Tech, Tools, & Maintenance
12. Objects & Data Over Time

The two main categories are: 1 - Elements of digital storytelling (numbers 1-6) and 2 -  How we adapt the digital environment (cloud/web) to track and record that story that is playing out (numbers 7-12). This is new for us and we were excited to see that there was a new classification within the adilas core concepts.

Like anything else, it is still kinda in flux and we don't know exactly what we have and what to do, but we are trying to refine things and boil things down. This is part of creating new content and verbage for the adilas system. Fun! We had a good session. Once again, if you want to see our raw notes, see the attached word document.

Also, we were thinking that number 1 (capture & record the story) was actually kinda like the end result - what we are aiming for or trying to get to.

We also felt like number 12 (objects & data over time) was actually how we enable the flow of the story to take place. The wording may be slightly different, but those are the concepts. Lots of interweaving pieces and give and take that goes on. Part of a living, breathing, system. Welcome to adilas!

At the end of the session, I did merge in some new code for Dustin as well.

 
No po photos available. Click to view time details.
Shop 7874 Work with Shannon 8/10/2021  

Work session with Shannon. We were back on the adilas core concept documents and recording some new ideas and brainstorming on maintenance concepts. Good session. The docs are still kinda raw, but we started to get in there to figure out how to refine them. Ideally we'd like to boil things down into a presentable format that is easy to read and understand. Both documents are currently unpolished, but coming along. See attached.

 
No po photos available. Click to view time details.
Shop 7876 Work with Shannon 8/5/2021  

Work session with Shannon. Brainstorming on adilas core concepts. We were working on ideas for systems, vision and future developments, tech, tools, and maintenance. We also did some light work on brainstorming on running objects and data over time. See attached for our progress. The document is still kinda rough, but at least we are catching ideas and concepts.

 
No po photos available. Click to view time details.
Shop 7880 Work with Shannon 8/3/2021  

Multiple different meetings within this time slot. First off, Cory and I spent some time going over projects and making plans after the earlier meeting ended. Lots of reporting in, circling around, and doing follow-up on different topics and projects. Steve and Cory were touching base on production (manufacturing) stuff.

At some point we have to turn things over to the people who are doing it (meaning our clients). We can't hold their hand forever. Eventually, the subject got back to deployment and who is doing what. We do want to take care of our clients, but we also can't babysit them every waking hour without charging for that service.

Shannon joined the meeting and she and I worked on brainstorming on adilas core concepts. We spent most of our session on permissions and settings and recording ideas, notes, and brainstorming on those fundamental concepts. We often say that adilas is built on a foundation of permissions and settings. That keeps expanding and rolling along as the whole thing unfolds. Very interesting. See attached for our ideas, progress, and notes from our brainstorming session.

Shari O. joined the meeting and had some payroll, internal audit questions, and email template questions. She and I went over a small questionnaire and chatted about independent contractors, independent developers, and independent reps/consultants. We then looked at some bank registers and fixing a small error on the save as PDF page for bank registers. Busy couple of hours.

 
No po photos available. Click to view time details.
Shop 7875 Work with Shannon 7/29/2021  

Working on Emerald Fields and prepping for an email update to the client.

Shannon joined and we started working on the adilas core concepts. We were working on decisions, choices, consequences (cause and effect), and accountability. See attached for where we are working.

Email out to the client with an update on the custom data extract project for Emerald Fields. Other emails.

 
No po photos available. Click to view time details.
Shop 7940 Meeting with Chuck 7/28/2021  

Working with Chuck. Both Steve and Sean were on the meeting as well. We were talking about the presentation gallery and getting some feedback. Lots of good back and forth on the layout, navigation, and what not. I sent Chuck some content for the adilas core concepts that Shannon and I have been working on. Sean was giving some feedback from his angle as well.

Towards the end of the meeting, it was just Chuck and I still on the meeting. We touched base on some of the new settings for elements of time and talking about online bookings and campgrounds. Trying to switch some of our focus. I also did some light training on reimbursements with Chuck.

 
No po photos available. Click to view time details.
Shop 7885 Work with Shannon 7/27/2021  

Brainstorming on core concepts. Why do we do what we do? Lots of world building pieces and what do we gain from that. Working on sections for relationships, trouble, problems, needs and goals. See attached for where we are at in the process.

 
No po photos available. Click to view time details.
Shop 7883 Work with Shannon 7/22/2021  

Shannon and I working on adilas core concepts and brainstorming on content. See uploaded or attached document for more info.

 
No po photos available. Click to view time details.
Shop 7884 Work with Shannon 7/20/2021  

Working with Shannon on priorities. We were brainstorming on a number of places that need some loving. Here is what we came up with:

1. New verbage and content for the adilas core concepts - Chuck needs these for the presentation gallery project (sales tool)

2. Business plan

3. Info graphics - More research and harvesting existing pieces - Pushing out new entries on the photo galleries and teaching tools

4. User guide - We were working on the alternate route for doing financials. We would like to get back to this.

See attached for what we got done on brainstorming on the adilas core concepts. We are just starting, more to come later.

 
No po photos available. Click to view time details.
Shop 7869 Meeting with Chuck 6/30/2021  

Weekly meeting with Chuck. We have missed a few due to vacations and the training conference. It has been about three weeks since our last check-in meeting. Chuck and I chatted about a bunch of different things. He is looking to grow his Swann Haven business a bit more. He is trying to do more booking and reservation type websites and such for clients using WordPress plugins. We chatted about the game of chasing funds and getting paid from clients.

Chuck has added in a bunch of new changes to the adilas docs project. He has added in sales and logging SOP's (standard operating procedures), new developer training modules for bootstrap and dynamic grid systems, and tons of other code snippets and templates. Looking good.

We then switched to the sales and presentation gallery. He is making progress and things are looking good there. This is more of a slide type interface that allows you to jump wherever you need to. The pages or slides are pretty simple and they allow for talking points. This is more for a sales rep or salesperson to engage and cater a demo or meeting with a client vs a client going through things on their own.

Along the lines of the presentation gallery, Chuck has asked for some more content on the system players and the core concepts. I told him that Shannon and I would try to work on some of that stuff for him.

We ended up talking about sales and networking opportunities and just getting out and talking with people. Towards the end of the meeting, we started working on a file merge and push up to the master branch for his new changes for the adilas docs project. Great meeting!

 
Click to view time photos.
Shop 7763 Meeting with Steve McNew 5/24/2021  

Meeting with Steve McNew - consultant and software engineer who is helping us refine, define, and standardize our processes and procedures.

He is working on some adilas docs and whitepapers - structure and design behind what we are building.

We started out our meeting with me reporting to Steve McNew (steve mac) about harvesting graphics, creating training curriculum, and refining some of our processes. All of those are things that we are trying to nail down and get ready before the upcoming training conference in the middle of June. Steve then asked about some of our refinements that we are making and also asked if we could quantify (counts, status, ratios) any of our claims. He is trying to get me to think about taking what we do (normally) and being able to repurpose those same tasks as marketing messages.

Here is an example of taking the normal and making it into a marketing message: I told Steve that we moved and migrated some domain names and servers. Tons of code changes and database reference changes (hundreds of thousands of path and pointer changes). With that project, we created a new database, field/column level, find and replace tool. I explained it that way, how I just wrote it. Steve said, you could take that same thing (find and replace tool) and say something like - Able to handle end of life transitions in a fast and effective manner. His way sounded a lot cooler than mine...

Steve showed me some of the white papers that he is working on. See attached for a small screenshot. He is starting to take our old images, graphics, and core concepts and mixing them with other technical documents. Our goal is to slowly step towards a more refined stack, role, and define what tools and techniques we use to get there. We talked about promoting and highlighting some of our proof of concept pieces, end-of-life tools and transitions, cost-benefit analysis, etc. Basically, using what we already do and adding to it to bring it up to par (a higher level, whatever that may be). This means using our concept drawings and analogies and putting more technical terms and drawings to make it seem more professional.

We went over some other topics such as document templates, risk management, and connecting the dots. We have a ton of content and do a lot of good things already. We just need to bring them out more and fully connect all of the dots. Along this way, I was amazed at how I could say something and Steve would rephrase it as a virtual marketing message. I would explain something and he would take the same thing and flip it so that it sounded cool. Sometimes with just the slightest word, phrase, or verbage change. Almost a virtual positive spin on things... like lemons to lemon-aid type flip/flop. Lots of opportunities.

Towards the end of the meeting, Steve showed me some quick and dirty drawings (simple boxes, flow charts, arrows, and text labels). He wants to help us capture the how and the why. That is awesome. Exposing the layers and looking at things from different perspectives on what we are doing and how things flow together. That sounds exciting. Great meeting.

Here is a link to an online drawing app that Steve recommended.

 
No po photos available. Click to view time details.
Shop 7634 Work with Shannon 5/6/2021  

Super awesome meeting between Shannon, Marisa, and I. We were going over some of the existing concepts for the info graphics, presentation gallery, and digital story telling options. I was on a roll and having a blast trying to convey some of the concepts and what not. I was having fun. The core concepts that adilas is built on are way more valuable than the code that we used to build it. I really want to help promote and protect those core concepts. I feel it my duty and I love it! I had a blast in this meeting.

Just for fun... I will include the chat log from this meeting. Part way through, Marisa's audio (being able to speak and us hear it) went out. So we had to use the chat feature. We were passing along URL's (web addresses) and other good thoughts and ideas. See attached for the copy of the chat logs. Kinda fun!

 
No po photos available. Click to view time details.
Shop 5961 Working with Shannon 3/12/2020  

Shannon and I were working on some new content today for the reporting business function as part of the presentation gallery project. See attached for the new brainstorming. You may need to scroll way down to see it. Our goal is to outline and present all 12 application players, all 12 business functions, and all of the core concepts that we are built on. Pretty deep dive into what we have to offer. Still under construction and in progress but coming.

Here are a few other things that we are working on and/or talked about today:

- The value of time and setting a value on our time and the time of others

- Teaching people how to treat you or treat us (as a company). It is amazing how we act and interact actually trains people what to expect, what to look forward to, and what they can get away with. Almost the rules of engagement or rules of interaction between parties.

- Growing up, line by line, precept by precept. It's a process and aren't we glad for that process.

 
No po photos available. Click to view time details.
Shop 6001 Meeting with Steve 2/20/2020  

Steve and I were going to be meeting with Kelly, but she ended up getting delayed while traveling and security in the airport. We ended up having our own little meeting. Good stuff. Here are a few of the notes from what we were talking about:

- Businesses need all of the deep functionality, they just want it as hidden as possible. Smooth and pretty just feels better, even if it does do as much.

- What if we keep flipping our model? What we mean here is... as a client or a rep keeps asking for more and more, what if we help direct them in such a way that we can get it done? This could be done by meeting with them, planning out what needs to be changed, offering solutions, listening, and taking down notes. Lots of possible options and then we gain from the source vs being pushed away from the source.

- Steve and I talked about the concepts that we are built on vs the code we are built on. Straight up, the concepts that we have built on are 100 times more valuable than the code that we have built on. Our code set is 1 of 1,000's of possible solutions. However, the main core concepts, those will need to be used every single time that someone does what we are doing. Even though you can touch some of the concepts, there is huge value there.

- We were talking about ways to get funding and the down sides to that. We talked about getting overextended and having huge amounts of debt. That is no fun either. Other talks about possible funding sources such as: grants, selling our services, getting partners, investors, loans, venture capital, donations, and leveraging other assets.

- MVP - minimal viable plan (the p could be plan, product, etc.) - I like the plan option for what we are doing and working on.

- What about the adilas marketplace (adilas world)? Lots of options out there as well.

- Everything that we see is fracturing into smaller and smaller pieces. Development process, permissions, settings, servers, API sockets, single tools vs bulk tools, tracking needs, etc. Fracture is the key word. Kinda like "Legos". We may need some blue ones, red ones, and some yellow ones. It just keeps going and breaking down into smaller and smaller pieces.

- Business management and who will take care of what

- Pain and virtual bleeding sometimes help to drive us towards change

- Somewhat of an open source type model

- What is our direction and our pace? Pick a direction and then let it grow. In some ways, it feels like we pick a direction and then plant the seeds, then in a day or so, we dig it up to see how it is doing. I think we need to pick a direction and let it grow a bit.

- Our model has always been slow and steady...

- We are only able to move forward as we get funding - we get funding from...
>> Reoccurring revenue
>> One time services
>> Seed money
>> Donations and other sources

- We are stable currently

- 3 things...
>> Look at what we have - deep, deep
>> We are building daily - progression
>> We help you by bringing value - multiple ways
-->> Low cost for what you want
-->> You are able to move the system in the way that you want it - allow custom

- Maybe make it known what we are spending on new functionality and R&D

- This is who we are... we are who we are and we plan on maintaining that

- We need to take things with a grain of salt

- Our current direction is directing projects over to one main source (Cory) and then diving things out from there - a director of development operations - Steve and I have decided that we will let this play out for awhile before making a major change or shift.

- Walls and helping to sterilizing things - getting some separation

- Like an essay - tell them what you are going to tell them (prep), then tell them (main content), and tell them what you told them (conclusion)

- You can do that? or You can do that! - We love it!

- We have a team that helps and supports us... that is huge

- We, as a company, need to have our clients get in line. Sometimes we give preferences and special treatment. We need to help standardize things.

- As a skill, we have people saying that they are proficient in adilas as a skill set. Pretty cool.

- Constant development and pushing the ball forward. We are building and refining every day. Keep it going!

 
Click to view time photos.
Shop 5196 Meeting with Chuck 11/14/2019  

We started to build out a visual tile board based on the adilas formula flyer. Here is a link to the older flyer...

https://data0.adilas.biz/adilas_formula.pdf - adilas formula flyer

We had a small discussion about world building and how it sometimes confuses people - almost too bold and too abstract. We talked about ways of softening that. For example: Say the different stores in a mini mall or different departments in a big organization. In a way, those smaller pieces or entities are building their own world.

What if we approached it by saying... currently you need a POS, an ecommerce package, a CRM, an ERP system, accounting, etc. Inside of adilas we allow you to pull those things all together under one umbrella. This becomes the virtual universe for that company. Show them how we can pull all of these things into one system. We are also really flexible, configurable, and nimble.

Results is one of the main four topics (results, business functions, application players, & core concepts). The results (what you are looking for) are huge. This side plays more on the emotions and wants of our users.

Link to a fun Ted Talk by Simon Sinek - https://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action?language=en

Here are a few notes from the Ted talk:

- Why - Share the why

- The golden circle - 3 levels - innermost level Why, middle level How, outer level What

- Help people learn from and be driven (of their own free will) from the inside out (why, how, what)

- People buy why you do it, not what you do

- Attraction of people - people who believe what you believe

- Driven by a cause - willing to put in and work with blood, sweat, and tears

- Prove what you believe by why you do it

- Helping to take and push a cause further - Once again, because they want to...

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

Going back to the sales document that we were working on (notes from above), Chuck sent me an updated link. Click below to see the Adobe XD layout. Pretty cool.

https://xd.adobe.com/view/e01cc5b5-caa2-4b84-4727-58b1b2ea764e-962d/

 
No po photos available. Click to view time details.
Shop 4671 Research 6/3/2019  

More research on core concepts. We need good code to help support our cause. However, the real value lies in the underlying concepts. I'd really like to keep pushing on that part of the puzzle. Our code (actually what the system does) could be one of thousands of possible options. The underlying core concepts are the stable foundation on which to build on or build off of. Good stuff.

 
No po photos available. Click to view time details.
Shop 4670 General 6/3/2019  

Working on my local coding environment. Installing and configuring new code editing programs. While programs were installing and uninstalling, I was doing some reading on adilas core concepts, out in the developers notebook, searching between 1/1/13 and 21/31/13. Lots of work on core concepts during that time period.

https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=core%20concept

 
No po photos available. Click to view time details.
Shop 4527 Adilas Time 4/24/2019  

Nobody was on the morning meeting today, so I spent some time going over some older notes and goals. Super fun and I could get lost out in that realm for quite some time. Here were a few of the places that I spent some time today.

I re-read and lightly edited notes from Steve and I's brainstorming and business plan meeting last night - https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=4574

Research from the developer's notebook on core concepts - https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=core%20concepts - I then did a local web browser search for the words "core concepts" and read the entries accordingly. Spent quite a bit of time here.

I would love to re-pick-up on this brainstorming doc - clear back from 2014 (part of an adilas training class with Shannon, Cheryl, Dave Forbis, and my self) - tons of cool ideas and concepts. https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=3681

Other core concepts that we have learned over the years - https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=1190

This may sound old... but there was a ton of work done on fleshing out the adilas core concepts in 2013. If you want, you could go to the developer's notebook and do a search for core concepts and filter the date range to 1/1/13 to 12/31/13 and get some great ideas. I ran out of time, I would have loved to have done more.

 
Click to view time photos.
Shop 4574 Business plan - whiteboarding with Kelly, Brandon, and Steve 4/23/2019  

We were going to have a meeting with Kelly and do some online whiteboarding and business planning, but that didn't happen. Instead, Steve and Brandon had a couple hour brainstorming session about their own ideas on a business model and business plan. Super fun brainstorming meeting.

- Steve and Brandon were talking about the role of the adilas market, adilas university, and the adilas café.

- Steve was talking about ideas... are you buying or selling? What section of the market and/or café do you play in?

- Just jump in... see a need, fill a need - we love it

- Another piece that we may be missing is marketing and sales type literature and media pieces

- We would love to recruit some others to help with the heavy lifting - There are tons of great adilas users out there who have some great skills

- It takes time and energy to get things going - the goal is, once it gets going, hopefully it will keep feeding itself.

- Steve is having fun tackling the business model - analogy - like a friendly pirate ship. It could be a boat, a ship, a car, a plane, or anything that moves over time. The fun come in as you start asking questions. Are we friendly? Are we mean? How many sails do we put out? What direction are we going (what is our heading)? What kind of crew do you want? How big and how small do you want to be? Etc. Fun stuff.

- Sometimes as we write and record these log notes, it may expose some of our underbellies, but we really gain from it in multiple ways.

- Steve and I would like to be open to discussions from any parties. We also acknowledge that there is a cost to being open and listening to those ideas.

- There seems to be many cycles that interconnect and play as the ball gets kicked down the road.

- Zipper analogy of bringing operations and accounting together. We started this a long time ago, we want to keep going but some of the steps are bigger and harder than others to conquer. Problems exists and that helps keep things going. Problems force decisions and hopefully a solution.

- Working in teams and pulling through things together - it helps get the ball across the finish line and you build relationships along the way.

- A constant mode of refinement - dive and resurface, dive and resurface - build and break, build and break - the concept of maintenance.

- Building blocks of teams - forming, storming, norming, performing - where are we at in our team development process?

- As we keep coming together as a team, there will be some normalizing and efficiency as we keep going. Good stuff.

- Steve is always on the hunt for the better and better ideas. He loves the hunt, in theory and in practice.

- Different angles, different views - false summits, operations, accounting, task oriented, dreamers, managers, etc. Like a pie analogy, we need the whole (in the end), and certain people are doing certain pieces (delegating tasks and processes), but hopefully as you bring it all together and it becomes the whole.

- The proof is in the pudding - if you have a great idea... let's put it to the test... we don't have a monopoly on all of the good ideas. We want to be open to those around us. Ideas by themselves don't really stand too long... those ideas have to be put into action and start applying those concepts.

- You can fund a company through investment, equity, sales, or leveraging debt. We are leaning towards sales and equity.

- Talking about models, we are even seeing some morphing models (mixing and blending), client/services, budgets, and strategic customer care projects. Customer tune ups, targeted tech support, and other customer care and retention efforts.

- Hoist anchor! Starting to get the ship out of the harbor.

- Models - rep model, hub/shop model, 3rd party solutions and white label model - We are seeing a small mix between the basic rep model and the basic hub/shop model. - Russell's word "Dependable" model. A loosely bonded hub/shop type model where the bond is the dependable type and/or dependable people who service other parts of the service model. Basically, they stick around to help pick-up and service the by-products that are created (training, consulting, setup, design work, custom code, tech support, project management, training, and other by-product services).

- Being able to clone some of the main core players - Steve, Brandon, Shari O., etc. Small teams forming under some of these key players and creating loose bonds (dependable type bonds). Very interesting.

- Talking about sales and white label options, we have no boundaries and no zones - people could consume our product wherever they are - we don't plan on adding any boundaries and/or zones.

- Anybody could identify a problem and/or issue - what we really want and need is those who help come up with and are willing to work on solutions.

- Steve was saying that the employer/employee relationship is a kin to slavery - it can work, but over time, it has other costs and drains. Steve really wants to keep moving towards the dependable type model - It is very loose but it can and does work - We want to keep helping those around us - if you look at it... we have so many by-products, the by-products completely outweigh our normal products. Very interesting. One of the key pieces is, you have to want to play the game. If you are just coasting, it doesn't work very well.

- Finding that balance point - We were talking about the difference between a normal company that has an employer/employee model vs this loose community of dependable - We also talked about how some companies are replacing the traditional model with robots, AI (artificial intelligence), or automated services. Where are those balance points and what makes things tip to one side or the other? One of the core concepts that we have is, our main product creates tons of subs or by-products. We can allow others to pick-up any of those by-products by offering their services (basically an open market type option).

- Some of this is just happening and we are figuring it out as we go... We have plans, we try things, we fail sometimes, we go backwards and forwards, we try to listen, we harvest other's ideas, we experiment, we tweak, we refine, we circle back around. That seems to work for us. It is more of the try storming type mentality vs just a plan it and build it type model.

- Randomly enough, we keep getting people circling back around after years of talking with them initially (old sales leads). We also have other people who are looking for and needing some of the functionality that we are working on and/or already have. The general public needs keep advancing right along with us. Step by step building process. Keep building towards the full system (fully interconnected pieces) and even full world building levels.

- Talking about commissions and outbound monies and such - Steve used the word semi-dependable (not a full dependable, but still part of the whole team).

- Finding the glide plane - like an airplane coming in for a landing.

- Tag teaming based on abilities - Coach, put me in... I want to play or give me a shot.

- People putting in time to help move the ball forward - Steve would like to move the company into a trust at some point.

- We are excited that we are moving some things over to deeper and more expanded technologies - tech stuff and server models.

- Keep working to get out of the way

- There is some magic in having a business plan but it can have limits - we do need some direction but it also helps to have your head up and be looking around. Our current business plan is "we are heading North" or something like "we are heading to the top of the mountain" - we have a direction and a way to go about it, that's about it. Fill in the gaps and cross the bridges as they come up (we know they are out there, but we don't have a full plan in place for every little thing).

- What about enjoying the journey? There is some fun in planning out the journey and then responding to cause and effect relationships that happen based on those decisions. That sounds like world building, in a way. The five core concepts of world building are: Characters, relationships, trouble/problems, decisions, and consequences - see this element of time for more information... https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=3634

- Some people will like what we do and sadly, we may make some enemies - we want to keep it as an open model - there are tons of options out there. We welcome those who want to play and we'll keep refining and building as we go. We want people who are looking for a solution and are willing to help and invest in their solution. We want to make adilas consumable... what do you want and how can you make it work for you?

- Model of being able to charge for different components - it all needs to exist - what if we showed all of the 12 main players and what part of their bill gets charged out and/or applied to what part of the 12 main players? That could be pretty cool.

- We may want to open up the adilas ecommerce piece to all of our clients. Currently, they have to pay for the extended ecommerce functionality.

- Data - the new currency... people are offering features and functions for free, just so that they can collect data. Very interesting.

- Steve would like to help push forward the ideas of the adilas café - a virtual community of users and/or other companies that offer their services - that will be really cool - helping to push the ball along the path using the skills and talents of others (a community of adilas power users and/or outside services). Once again, the by-products are a huge part of the model.

- We do need some standardization pieces, but some of our model is the flexible ways you can do it... We need both side of the fence.

- We ended by doing a brief look at where we have been and where we are going (historical summary of invoices and client based financials). Good stuff.

 
No po photos available. Click to view time details.
Shop 4394 Meeting with Shannon 2/19/2019  

We are trying to boil things down for a sales flyer. We are wanting to work more on the core concepts and build a why and what are we trying to do flyer.

 
No po photos available. Click to view time details.
Shop 4029 Adilas Time 10/11/2018  

On the morning meeting with Josh and Alan. We went over a few new changes from yesterday. Alan reported on his work with Bryan and making a new black box database table (custom table - specific just for that client). Alan and I talked about some naming conventions and how all new black box database tables will have "bb_" to start the table name. For example: bb_53_some_table_name.

We spent a little bit of time going over some new needs for quantity and weight multipliers. Alan and I decided to add two new fields to get things into real numeric values. Currently, some of the people are using some of the existing fields, but those fields are strings or varchars (text based) fields vs real numeric fields. Alan will be making some changes. We know that this project will have two phases. The first one will be to add the new fields and then match-up what ever values we can. The other part of this is going through hundreds of other reports and top cart mini's (gram counters) and Metrc API reporting (state tracking stuff) and flipping the older text based logic into real numeric values and real math. We will be using a value of 1 in the numeric weight field as a default. 1 times anything is the same number. If they want to change that ratio, they will at least have a spot (numeric field) where to do it.

I then started to work on the sales tax project and bringing up all of the black box code to match the master code files (checking for new changes on the custom tax fields 6-10 and other dynamic naming). As a side note... Custom is awesome, but there is a flip side to that... It takes quite a bit of maintenance to keep things up to date if you are changing core pieces.

I spent some time reviewing some notes and info that Dave Forbis gathered up dealing with Stripe (online merchant processing and credit card gateway). See element of time # 4095 for some notes and links. After that, I got on a call with Dave and we went over a few things. We have four different topics that we will be looking into next. They are:

1. Reviewing some older things (tons of white boarding and graphics that were done by Dave from a couple years back) - The goal here is to circle through and pick-up anything that still has merit.

2. Start working on some billboard type sites. These are small websites that have a smaller focus and virtually point people and users to the bigger adilas application. These are things like world building, data assembly line stuff, new school accounting, 3D models for world building and digital story telling. Dave and I were also talking about some concepts that adilas is built upon that are either core and/or we've pushed pretty far. Dave was saying that we could create mini Ted Talk type videos and/or graphics. Get people thinking and talking. Use those pieces to point things back to adilas and what we are doing. Some great marketing ideas.

3. Currently, the adilas platform has a very high concentration of MMJ or Cannabis related industries. Maybe get a list of other kinds of companies that are using the system and show some of the diversity with how and what they are using in the adilas platform model.

4. Dave would like a list of the different domain names that we have and where we would like to focus on building small billboard type sites. I will get this together and send it to him. In a way, we are lightly playing the digital real estate game and trying to setup small little claims. Those claims have two fold purposes... One, they will become virtual billboard sites pointing to adilas and the core concepts that we are built on. Two, they will provide prior art - which makes it so that others can't copyright, trademark, and/or patent - intellectual property stuff. It basically strengthens and protects the main core of what we are trying to do. Good stuff.

 
Click to view time photos.
Shop 3957 Adilas Training Class in Denver, CO 9/10/2018   Adilas training course in Denver, CO. We will be at the La Quinta Inn and Suites. Englewood Tech Center

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

 
No po photos available. Click to view time details.
Shop 4002 General 9/6/2018  

Tech support, emails, and more core concepts reviewing for the training event. I also have to present on the historical stepping stones and what we've learned over the years. That will be a fun subject. Good stuff.

 
No po photos available. Click to view time details.
Shop 3964 Adilas Time 9/6/2018  

Studying up on some core concepts and basics on world building. I have to present at the upcoming Denver training event.

Going over graphics on the teaching and training tools as a refresher. See https://data0.adilas.biz/adilas_for_business/photo_gallery_full.cfm

 
No po photos available. Click to view time details.
Shop 3891 Adilas Time 7/10/2018  

Steve, Dustin, and I were all on the morning meeting. I was working on the developer's notebook pages and project. Currently working on a page that shows web ready (public entries) elements of time in a grid type breakdown by month and year. The goal is to help web spiders and other web crawlers to be able to get to the elements of time and then index and archive the content easier. This is a big part of the developer's notebook project.

Our underlying goal is somewhat of an attempt to help publish and publicize some of the core concepts that adilas.biz is build on. Going way back, we went to a workshop on intellectual property and how to patent, copyright, trademark, etc.  As part of that, they said that if there was prior art or prior work, you couldn't do the patents, copyrights, and trademark stuff. So, in a way, we are trying to make some of the core concepts become part of the public knowledge bank. We are basically trying to make it so that the core concepts are unable to be patented or trademarked. We need them to be open and available for all entities.

Wayne popped in and he showed us some server monitor stuff using a Nagios server. We setup some server monitors for all known servers.

 
No po photos available. Click to view time details.
Shop 3787 Adilas Time 6/26/2018  

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.

 
No po photos available. Click to view time details.
Shop 3854 Adilas Time 6/14/2018  

Tried looking for a sub inventory error. Unable to find it and/or duplicate the error. Started working on the developer's notebook page. Trying to get some of that data out and on the web. This is the way we can help protect the main core concepts that the adilas platform is built on. Good stuff.

 
Click to view time photos.
Shop 3699 3 Day Live Adilas Class 5/29/2018  

Live Adilas Class. Logan, UT - Bridgerland ATC, Custom Fit, Room 810 (computer lab). We had 4 live paying clients and a number of internal team members in the class. We had Steve, Shari O., Dustin S., Alan, Bryan, Calvin, Russell, Shawn, Jeremiah, and myself from the core adilas team. Not all of them were there everyday, all the time, but they all came and participated quite a bit of the time. We also had a number of folks join us online in the GoToMeeting sessions. We recorded all of the training except for two main sessions.

Here are some links to the videos.

video from day 1 - morning session
small adilas demo, intro, and core concepts

video from day 1 - afternoon session
new features, open q&a, and historical stepping stones

video from day 2 - morning session
POS - point of sale features part 1

video from day 2 - afternoon session
POS - point of sale features part 2 - open q&a, and world building in use

video from day 3 - morning session
CRM - customer relationship management overview

video from day 3 - afternoon session
exploring ecommerce & custom email settings - BI - business intelligence and big data

video from day 4 - morning session
tips, tricks, & best practices - small custom consulting session

video from day 4 - afternoon session
meet the adilas developers, adilas model, and wrap-up

///////////////////////////////////////////////////////////////
other notes that I took during the class.
5/29/18
- Drag and drop custom fields - they really like the custom field settings for customers. They would love that to cascade out and filter through the whole system. Point and click, toggle on/off fields, sort, customize verbage & instructions, and be able to effect the display as well.

- The need for more one-to-many relationships

- Light request for more settings on the main salesperson and other salesperson settings - be able to split the names instead of just one setting.

- A custom preset on permissions "copy and/or duplicate" permissions.

- Setup a master and then apply those settings. This could be templates and/or master files - a virtual job description.

- Floating up and down nav to help minimize the scrolling.

- The power of "templates" - elements of time, sub inventory, payee/users, look & feel, etc.

- Start by setting up the templates and then assign them as needed - that makes a great starting point.

5/3018
- Alan was doing an exercise - he had everybody list what they could for two minutes on all of the fruits that they could think of. Fun little exercise. After that, he was comparing this to development. We try to hit the fruit that is on your list. Things keep evolving and sometimes you forget things and have to add that in later.

-  Corp-wide settings and allowing you to set certain verbage stuff.

- Bryan Dayton was showing the adilas market (adilas world). We really need to get others into the marketplace.

- While Bryan was showing his profile... I was thinking that we need to help him get some better screen shots for his demo graphics. You could tell that they were done with a low end and/or free graphic editor (kinda fuzzy and pixelated).

- It helps us to have a flow and/or a clear picture (talking about custom code and custom development).

- Small demo on a custom dashboard for Global Design

- Steve and Shari O. were talking and doing a demo together. Steve was talking and Shari O. was driving. Later Steve and I did similar things. It really helps to split that load and have a helper. The person talking can focus on what they are saying and the demo person (driver) can draw, highlight things, and show focus areas. It seemed to work out quite well.

- Steve and Shari O. started out in a coffee shop and did some quick split cart stuff. They then went into some of the corp-wide settings to show how they were able to do what they were doing. Good flow from normal usage to how it is done based off of settings.

- Eventually we need a deep merge (find and replace) on customer records.

- Our users would like to be able to compound a discount. For example: double up points, do a 1.5 mark-up, etc. Lots of time based sales and promotions.

5/31/18
- Not many notes from this day... We started out and Steve and I were presenting on sub inventory. See the video links above for more details and info.

6/1/18
- Steve was going over the new cultivation functionality. 4 main levels for the cannabis guys... they need cultivation, production, distribution, and retail.

- Some of the these white label options should really build out and use all of the pieces.

- Page and function level settings

- Interesting topic of hardcoding & concepting vs dynamic code & production - speed, limited scope, and testing.

- Being able to lock-down certain pieces, features, and virtually ice things down (ice-down dates).

- Also, interesting as we get deeper and deeper into the industry specific code... the verbage, lingo, & the flow are really important. That is what makes it feel like native or custom code or custom software.

- Comment from Dustin - We need guide rails, guard rails, settings, templates, and easy configuration options. Help lead the people down the paths that we want them to go.

- On the data tables - it sure would be cool if you could sub filter things. It comes down to space, coding, page real estate, and planning. People want more and more custom options - to setup their flow, work space, and environment (requests for deeper and more robust world building options).

- On numeric entry fields, show the unit of measure to remove the questions (if applicable).

- Making the label options show up and be available from multiple pages and such.

- Settings are preset choices & decisions - super important.

- On Calvin's tools... Just an idea, but what about dynamic or user input boxes and text fields? This is for text that may be added on the fly. He currently has static text, HTML enabled text fields (allows formatting), and dynamic look-up text (text fields mapped to data or dynamic output). What about user input text boxes?

- Making labels and empower the users.

- We had a client/participant that recommended that we put a small icon on each page that could be a default homepage and then have a quick link to set it as the default homepage. Great idea. Basically, let them navigate there (to the actual page) and then set it as their homepage if that is what they want.

/////////////////////////////////////////////////////
Comments from Bryan - who talked with one of the participants

- When starting the class, for someone who is brand new... it might be nice to give a 15-20 intro and general overview. We just started out and jumped right in. Basically, somewhat of a canned explanation of what is adilas and what do you get with this software package. A really simple and organized intro.

/////////////////////////////////////////////////////
Notes from Dustin - See attached for full notes

General To Do's:

Need to Have each page check for the color of the background and adjust the card to be a lighter complimentary color (universal). (4,5)

Need to have api key capability for each employee that performs metrc api interaction.

Need to set up custom permission setting capabilities so that they can set permissions for multiple employees over time without having to do a redundant process. Themes and standardized user type templates.

Make a excel or csv spreadsheet that templates the fields needed for api integration to give to a customer to fill out. Maybe a master list that passes in all of the general fields and passes over unneeded fields based on customer needs.

Need a graphical repesentation of the entire seed to sale process with tie-ins to each adilas feature/tool.

Need predictive on the search vendor field on the add/edit page.

Need to have customer password fields auto-populate wherever needed. (e-commerce)

Need to have a set to default button on the nav menu for setting any page as a default homepage.

Need to have a toolbar button for page relevent tips and tricks with links to news and updates.

Need to update how people reset thier login attempts: lets add a captcha or at least put the copy paste link on the same page. Maybe two step varification would work.

When you are switching corps, instead of needing to click on the little box link, make it so that you can click on anywhere on the corp piece.

Need to have UOM type indicators on any field that holds wieghts. In most cases this could probably be hard coded.

Need to create the ability to check a box that opens all of the subs for inventory search for adding to cart.

 
No po photos available. Click to view time details.
Shop 3734 Adilas Time 5/8/2018  

On the morning meeting with Steve and Russell. They were talking about how Bridgerland could help with outside development and doing smaller projects. Part of the puzzle is how we empower our users. It is so important to empower our users at the level that they need (go to the source). That is a huge core concept.

Taking the email options out to the bulk level and also allowing users to make the email come from their own servers.

As the guys were talking, I was doing some research on the old adilas website. Lots of good PDF files, help files, graphics, and flyers. Here is the old website link: https://data0.adilas.biz/old_index.cfm

Eric wants to talk about coupons and loyalty points. We talked about a guy named Chris Johnnie and some prior planning that may have been done by Russell and Chris. We are trying to pull things together and make everything happen.

From Eric - It is so expensive to keep stopping and starting - we lose tons in the transitions. We need to focus and stay on track.

Eric was expressing some concerns about sub inventory on the production side of things. Steve chimed in and was talking about how some people don't even know what else is possible and already built. The trail is faint and many people have been gone in different directions. We need to define the best path and then help educate others to play the game.

Manufacturing is a whole new level - You have raw goods being made into finished goods. Lots of internal flipping and tweaking. You need bill of materials, sub assemblies, recipes, other tracking needs, etc. We talked briefly about parent inventory and sub or child inventory. Some of the big needs come when they have sub assemblies and use semi raw goods and then push it into another finished good or product. You have to be at the sub level in order to really track that information. It gets into sub locations and sub phases and all kinds of other subs. In the background, we are seeing the _Z coordinate (depth and stacking) coming more in to play.

We are having a number of clients that are fighting against change. Some of the subjects are the way the one-to-many relationships are setup and what the individual people think should be the best option. Some of the questions are things like - one PO with multiple line items or one PO per one line item. Which one holds the location and how do you move things around. They want to group things but also be able to move things independently. They need both... basically, I'm part of this group but I also play over here and here. Very interesting.

This is a side note, but we end up spending so much time managing our customers because they all want to chime in and say what they feel is the best. Custom is awesome but it can also get us in trouble. Custom is really easy on existing and established pieces. One of the main problems is when we get into uncharted territory, people have all kinds of ideas and what things would work best. Once the trail is set and people are using it, they tend to go with what is already there unless we make it too hard. When the trail is not fully established, it turns into the wild west (anything goes) really quickly.

Once people get what they want, they tend to want to get to it quicker. They also want more. This could be more options, more control, more access, more of almost everything. They basically get addicted to data and ease of use.

Steve was doing a demo on sub phases, sub groups, and sub locations. Lots of using elements of time and special flags and tags to track all of the details.

One thing that will help people is showing them how to get back to their details and data. We (developers and power users) know things well enough that we pop through screens, skip steps, and go really fast. A new user is watching and they just get lost. So many moving pieces. It hasn't been smoothed out and/or standardized yet to really make it manageable and easy to understand. We either need to slow down and/or make the path more direct and discernible. Make it obvious and straight forward.

A note for us... We can use these subs to hold the sub details and sub data. We need to show things in very general levels and make it look simple unless the user wants to get clear down to the lower detail level. Think of the world building graphics that have universe level, world level, location level, group level, individual level, and the underlying data level. We need to allow the users to navigate at whatever level they feel most comfortable. We need all of the deep, deep, sub data, but that may be too much detail for some people and/or users.

There will be a greater and greater needs for mini conversions and how that effects things. Steve has already done quite a bit of work on the custom/build_complex_labels.cfm page. We need to use that as a great starting place. Lots of moving pieces. It goes like this... You have to have a parent item. Parents have subs or children. Those children then get broken down into smaller pieces and sub packaged. That is mini conversions.

We keep pioneering small little projects and getting some testers and people who keep pushing on things. Adilas is literally a giant testing environment and a virtual idea farm. We keep planting and harvesting ideas. They just keep coming.

Going back to manufacturing - there are tons of batches, sub batches, lots, and even reprocessing and repackaging pieces. We need to keep defining the road and helping the people who will be coming down the road later on. Kinda like Eric was saying... We need to focus and get pieces done and standardized - we get pulled in so many different directions. We lose a ton in the transition and switchover between projects. It gets very expensive and takes a ton of time and energy. In manufacturing, they often will set up an assembly line for a certain run... They then run that product until it is done. If they had to switch lines (assembly lines) every couple of hours, they would have tons of down time. Maybe we need to do similar type things. Make a plan and then work your plan.

The other gem is using the people who know it... get the reps and the clients together that know what is going on.

Flow - We can link all kinds of stuff together. That is a whole other level. If we can get the job done and get the person to the correct next step, we can help them keep moving forward. It comes down to flow and planning. Steve wants Dustin to help with some of that flow. Steve's words... "we need to train the system". That helps the whole thing go better. Dustin's words were... "the system almost needs rails". They then talked about wizards, steps, and showing a logic path and where they are on that legend or helping them know what is next and where things are at. Walk them through it. This could be crumb trails, legends, wizards, etc. Good stuff.

 
No po photos available. Click to view time details.
Shop 2728 General 12/16/2015   12/16/15
4:30-5:15 Recording notes from yesterday.
5:15-6:00 Browsing photos for Adilas concepts, designs, and issues on the Adilas for business web site. This is the project that Russell and I have been working on. Lots of good ideas and concepts. Light brainstorming on how to educate and market the Adilas tool set. The idea is to focus on the business function that we provide. Basically, it all goes back to the Adilas formula 101-Mix (functions,players, concepts) to get Results. That includes the 12 business functions, the 12 main player groups, and the 12 core concepts.
6:45-8:00 Paying bills and cleaning up my schedule in the Adilas shop elements of time. Emails and other cleanup.
9:00-10:30 Went into Logan to work. Met with Alan and we started into a code sign-off process for my cart favorite buttons and being able to switch between Flash (normal) and HTML buttons. This is needed for users who use Apple products such as: I pods, I pads, and I Phones, some of these are Apple products don't natively support Adobe Flash widgets. Anyways, partway through the process, we got a call from Hypur and they needed some help testing their API. So we helped them out for a good half an hour. WE then got back to our stuff. Crazy morning. 30 Miles.
10:30-12:00 Meeting with Daniel, Shannon and Dave Forbis about Beaver Mountain. Daniel and I laid out our plan and I got input from both Dave and Shannon. We also talked about starter packages and easy setup packages. Some of our conversation ended up going in the direction of what should we charge for setup, training, and consulting. We had a good talk and I lightly pitched the ideas of the hub model to both Dave and Shannon. Fun meeting.
12:00-6:15 See elements of time for other happenings on 12/16/15
-Steve Sub Inventory
-Nick - Adilas World Project
-Garrett - sub inventory reports
-Bryan - Server and other consulting
 
Click to view time photos.
AU 3812 Daily Ideas 4/16/2015   -I’ve got a number of projects and proposals right in front of me. How can I help those projects go forward and be able to scoop up the low hanging fruit in front of me? I think that I need to slow down and pick things up. Sometimes going slow takes more time but can really help!
-Sketches of how elements of time play into all pieces and parts. Concepting with a developer.

See sketches on scans in photo gallery:
- 12 main player groups like customers, invoices, parts, users, vendors, etc.
- Subs or sub functions of time. All main players could use and/or talk to any of the sub functions of time.
- 12 main players with their own natural subs or features.
- Subs or sub functions of time.
- The above model started getting into other natural connections and subs of the main player groups.
- I still kind of like the oval and spiral or radial model. Just trying to figure out the best option to help people understand.
- 3 main points for joining items to the family of elements of time are:
1. Life span
2. Checkpoints
3. Data assembly line
- What if part of the core contained the following elements…
1. Permissions
2. Settings
3. Functions of time & space
4. Media/content & files
5. Relationships
6. Concepts & principles
7. Other key factors & players
8. What is needed to tell, record, & play the story out?
- At the core of world building – you have a number of core concepts and principles. They are the core. Without the core concepts and principles, the whole thing fails. Help it grow by supporting the core!
- The very heart of the matter deals with a number of interrelated and compound concepts. That is where the model gains strength.
- Help other people know about this core concepts, principles, and interrelated pieces. The “why” many take a while to teach, show, and develop. It is worth it!
 
Click to view time photos.
AU 2984 Daily Ideas 12/2/2014   - My brother found a good ColdFusion training clip on the GoToMeeting recordings from 11/13/13. It starts about 35 minutes into the video. It deals with variables, lists, arrays, and structures. Good building blocks.
-A new corp-wide setting might be – what is the default custom homepage per corporation. This would also be cool if we could assign a homepage as we create a new user. Thinking about admin level assignment options.
-A great corp-wide setting (as well as a user setting) might be – what default list of my cart favorite buttons to use? Currently, the user has to choose from a list each time they login.
-Teach at their level! An intern and I were talking about how we trained our first couple interns vs. our second and third sets of interns. We definitely start slower and try to build on core concepts and mini projects vs. big and custom projects right out of the blocks.
-Draw out the possible black boxes (custom code options) for the view cart page. All dotted areas are virtual black boxes.
Sketch in photo gallery scan:
Split Cart & Main Cart:
- Mini black box in the split cart
- Mini black box for cart alerts – top section
- Mini black box for cart alerts and custom code – bottom
- Main cart black box. This allows for custom code to be ran as transparent (no visual) or full cart take over. This is full custom look, feel, flow, colors, graphics, layout, etc. Full on!

-Small note on video clips. I burned 8 DVD’s worth of video clips today. There was over 200+ hours of adilas training and over 50+ hours of ColdFusion training. Man I really want to get that training out to the world. On a side note… I also bought 10 x 32 GB flash drives for just about $10 a piece. 8 DVD’s at 4.7 GB a piece or 1, 32 GB, flash drive. I vote on the flash drive!
-We are going to give all of our developers a new 32 GB flash drive with close to 250 to 300 hours of training on a single mini drive. That’s a ton. I can’t wait to get it all organized and cataloged. That will be awesome!
 
Click to view time photos.
AU 2888 Daily Tasks 10/25/2014   • Working on help files and prep for a meeting with a developer. Made some small needed changes to help files with documentation about login resets. Trying to make things more dynamic.
• The developer came over and we worked on getting him started with the API socket or API parts (connections). We are going to call his project “wiring up the wall” so that we can let any outside party or parties “play at the wall.” The phrase “play at the wall” was mentioned by my dad as we were on a morning walk. We’ve used that phrase a number of times since then when trying to explain API socket connections (virtual data ports) to different people. See notes on other page for graphics that the developer and I drew to describe the process or concepts of play at the wall.
• Working on help files for API socket connections or data ports. Lots of reading and writing. Trying to explain the process using analogies.
• Writing up a help file to help explain 3D world building and business world building concepts. Included: x=time, y=money, and z=space levels and dimensions. Also included all 12 main adilas core concepts. I can’t wait to put graphics with the new help files. Help to both tell and show the story. That is the goal!
 
Click to view time photos.
AU 2881 Daily Tasks 10/17/2014   • Paying bills.
• Working on the Denver training flyer for the end of October. The course was called new system updates and advanced backend office and accounting. Reformatted the flyer and added the 3D world building graphic on it. Sent it to Steve for approval.
• Purchased a number of new domains. They are: 3DWorldBuilding.com, BusinessZipper.com, NewSchoolAccounting.com, RollCallAccounting.com, BusinessWorldBuilding.com, AdilasUniverse.com, and AdilasUniverse.biz. I’m really excited about some of those domain names!

• Went with my dad down to Salt Lake City to meet with a potential client. They are an emergency preparedness company that wanted to see what we could do for them. On the drive down, I browsed their website using my dad’s hotspot while my dad drove. Once we got there, we met them at Village Inn for brunch. I used the interactive map graphic and the adilas GPS core graphic to explain core concepts. A gentleman and his web developer were at the meeting. They both had great questions and kept me hopping. I barely got to eat my meal. After the brunch they wanted a live demo. We then went to the web developer’s house to play with adilas. They kept throwing out questions and I would respond. They (combined) basically drove the demo by throwing question after question. Great session. As we were driving away, we got a call from him with some other questions. He had some excellent questions and you could tell that he was a very sharp cookie. 200 miles.
 
Click to view time photos.
AU 2870 Daily Ideas 10/11/2014   -Using in-line extensions will give us the flexibility of Microsoft Excel with the power of a relational database and cloud based infrastructure. That will be awesome.
-The key pieces are:
1. Centralize the data
2. Be able to collect and store the data
3. How to interact with the data
3.1. Interface
3.2. Flow & Processes
3.3. Analytics & Reporting
3.4. BI (Business Intelligence) & Big Data

Space & Time Brainstorming:

-Brainstorming on project phases and sub locations... Theses are subs of elements of time (and space). These pieces position or arrange how and where and what is happening or has happened or will happen. I think that we need to keep them subs or functions of time and space. However, I also think that we need to record the current state or status on the main. This allows it to be searched and referenced quicker.
-We already store the action status value on the main elements of time table. These sub locations or projects phases would be the same way. We would hold an unlimited list of sub locations or project phases on or in the sub tables... but we would also make the current sub location or current project phase be part of the main element of time.
-I'm really excited to see “space” or organization of time start playing into the mix. This is exciting!
-If we are talking about subs showing up on the main individual data items or data objects, there are other pieces that want to be counted or accounted for. For example: Say a person was adding sub dates and times (virtual timecards) to a project. It sure would be nice if the total amount of time (sum of the subs) could show up on the main. All of the details are still held in the subs, but the current value becomes part of main. This is also true for things like action status logs, sub dates and times, project phases, sub locations, etc.

-Elements of time and space need to be a foundational wrapper for all functionality for adilas. We already do this in a very light way. Invoices are assigned to locations and dated; PO's are assigned to locations and dates; deposits and expense/receipts are assigned to a date and one or more locations at a time. Inventory is tracked per location and by date (sometimes multiple dates). Almost everything we do has a component of space (locations and layering) and time (dates and date/time stamps). We already play this game... What if we just take it to the next level and allow the users to virtually wrap the system, the groups, and the individuals in both time and space? That would be awesome!
-Time and space is ok (still works) but space and time sounds better. What about elements of space and time?

-What if we add the word “space” into all of our pieces of documentation, literature, notes, quick search, etc. It may be made fun of at first but I think it could gain some ground especially if we start teaching and using those concepts together.
-On the quick search – I would like options to search time or elements of time. I would also like a quick search option for space and time or elements of space and time. The space and time options could search much more and find all instances of things in both main and sub tables and database fields. If you searched space and time it could be the global adilas or all adilas searchable.
-Locations and dates are a general way of saying space and time. We already knew that dates and times were important but we didn't know how deep locations or layering pieces would be (organizing your data). We've got to include space... It adds to and increases what dates and time can do by itself... It is a compound concept that needs both space and time!

Think of our little assembly line graphic for our world building concepts... (Please see sketch on scan in photo gallery):
-Space is how we organize over time
-Pretend that the dots are checkpoints or key phases (dates/times)
-Pretend that the top line is operations and the bottom line is accounting
-Time goes both directions
-Pretend that the vertical lines show permissions or access levels. Who gets to play at what level?
-Pretend that the pods are areas or sub locations or departments (space)
-In between checkpoints we have to allow some flex in the model

-Lately I've been toying with the idea of a wrapper or a way to combine core concepts. I want them (core concepts) to interact and play together. I've been headed towards a wrapper of time (see entries from 5/22/14 and 6/3/14 in adilas university – developer's notebook). Anyway, my new direction is a wrapper or foundation of both space and time. You've got to have them both.
-The bottom level (number 10) of the world building concepts currently says... Run all levels over “Time”. I think it needs to read – Run all levels through “Space” and “Time”. The word “through” may be a good general term for a wrapper, media, medium, or channel. We'll try that and see how it goes.
 
Click to view time photos.
Adi 866 Intellectual Property Workshop 8/21/2014   Brandon Moore, Wayne Moore, Cheryl Moore, Shannon Moore, and Dave Forbis attended a workshop on intellectual property in Logan, UT. The workshop was put on by the Small Business Development Center, Cooperative Extension of USU. The presenters were a law firm that dealt with patents, trademarks, copyrights, etc. See attached for my notes.

What I got out of the workshop was basic information, timelines, ball park figures, and what is required. My favorite part of the workshop was dealing with how patents, trademarks, and copyrights can be denied and/or rejected.

This might sound random, but I think that our goal is not to secure a patent on every little feature. Our goal is to defend patents being put on to core concepts. We need the model to be open and free. If not, it will swing power potentially in the wrong direction. So, in a nutshell, by us talking about things, publishing things, teaching, instructing, and building with openness in mind, we are helping to keep the patents out of the core of the ideas and concepts. Let people patent smaller pieces of the puzzle, that is no problem. However, we need to protect and educate people on the core of what we are doing.

I have said this in private before, but I would bet that the core concepts that adilas.biz is built on are 100 times more valuable than the code that we have written over the years. There could be thousands of possible code angles on these same concepts. That is well and fine and a known fact. The important piece is protecting the core concepts and principles of what we are doing. We kinda fell into this... this wasn't our original goal. However, I do feel that we have some super important things that we are developing such as:
  1. 12 Main Application Player Groups - Customers, invoices, quotes, vendors, PO's, items or parts, stock/units, deposits, expense/receipts, employee/users, user-maintained balance sheet items, and elements of time.
  2. We have photo galleries for each of the 12 main application player groups. Each gallery can hold 100 images per item or individual in the group.
  3. We also have a full blown content management and digital file catalog and/or archive system for each of the 12 main application player groups. We also go further and allow files and documents to be stored and cataloged at the system level (as a whole), at the group level (by any of the 12 main application player groups), or by individuals within the different groups.
  4. Another huge piece that we are doing is business world building concepts. This includes all 10 levels that we currently know about. They are: 1. Universe Level (the internet and all adilas pieces), 2. Galaxy Level (linked servers - both data and content servers), 3. Cluster Level (individual boxes, domains, or servers), 4. Solar Systems (databases within a cluster - could be one or more per box), 5. World Level (corporations, entities, and companies within a single solar system or database), 6. Location Level (stores, departments, or physical or virtual sub dividers of a corporation or business), 7. Group Level (see the main 12 application player groups listed above), 8. Individual Level (items, objects, and entities inside of a group. for example: customer 111, invoice 345, deposit 222, po 474, etc.), 9. Data Level (how and where are things stored in the database? what relationships exists? what is the story?, 10. Run all levels over "Time" (time is the current bottom level structure that we play in, on, and through. this same statement could be re-written as objects and data wrapped in time)
  5. Operation lead accounting over time. Our use of time and how it plays into the whole story of what is going on. It allows for characters, relationships, overcoming trouble or problems, decisions and choices, cause and effect consequences, accountability, etc. That is where you get the whole story or being able to capture the pieces of the story. In short, we call it roll-call accounting. The system is able to go backwards and forwards over time to tell what the relationships were, are, and may be. This helps show how things were/are connected or accounted for over time. It is awesome!
  6. We have taken a traditional model or business model and created a fully integrated system. You no longer have to have 4-10 different pieces of software to run your business. You can use the full adilas.biz system or platform to run your business. You have access to all of the pieces, any time, under one roof. It works because it is a system.
  7. We have built the entire foundation on two main concepts. They are: permissions & settings. You can do almost anything with those two pieces. Permissions are who has access and what can they do? Settings are the how, when, how much, how many, and what to call it. This could also include show/hide, open/close, limit, defaults, etc. Settings and permissions may be applied on multiple levels. Technically, a person could add both permissions and settings on all 10 business world building concepts listed above (universe, galaxy, cluster, solar system, world, location, group, individual, data, and wrapped in time). That is a huge piece of the puzzle.
  8. One last thing that really needs to be there is the ability to be flexible. No two things are the same. People and businesses want access to features, functions, data, and processes from different angles and in different ways. This means that you have to 1. Be able to catch the data. 2. Can you get at the data that you caught? This also includes options for editing or changing the data. 3. Can you show it back to the user in the way that they want it? This goes out to custom levels and deals with interface, API socket connections, webservices, feeds, imports, exports, data trafficking, flow, controls, etc. What are you looking for? What is your goal? This is the results and/or interface of the application.

Anyways, those are some of the pieces that I see that we are doing and developing that could potentially be patented and/or copyrighted. They are listed here to start the process.
 
Click to view time photos.
AU 2774 Intellectual Property Workshop 8/21/2014   Brandon Moore, Wayne Moore, Cheryl Moore, Shannon Moore, and Dave Forbis attended a workshop on intellectual property in Logan, UT. The workshop was put on by the Small Business Development Center, Cooperative Extension of USU. The presenters were a law firm that dealt with patents, trademarks, copyrights, etc. See attached for my notes.

What I got out of the workshop was basic information, timelines, ball park figures, and what is required. My favorite part of the workshop was dealing with how patents, trademarks, and copyrights can be denied and/or rejected.

This might sound random, but I think that our goal is not to secure a patent on every little feature. Our goal is to defend patents being put on to core concepts. We need the model to be open and free. If not, it will swing power potentially in the wrong direction. So, in a nutshell, by us talking about things, publishing things, teaching, instructing, and building with openness in mind, we are helping to keep the patents out of the core ideas and concepts. Let people patent smaller pieces of the puzzle, that is no problem. However, we need to protect and educate people on the core of what we are doing.

I have said this in private before, but I would bet that the core concepts that adilas.biz is built on are 100 times more valuable than the code that we have written over the years. There could be thousands of possible code angles on these same concepts. That is well and fine and a known fact. The important piece is protecting the core concepts and principles of what we are doing. We kinda fell into this... this wasn't our original goal. However, I do feel that we have some super important things that we are developing such as:
  1. 12 Main Application Player Groups - Customers, invoices, quotes, vendors, PO's, items or parts, stock/units, deposits, expense/receipts, employee/users, user-maintained balance sheet items, and elements of time.
  2. We have photo galleries for each of the 12 main application player groups. Each gallery can hold 100 images per item or individual in the group.
  3. We also have a full blown content management and digital file catalog and/or archive system for each of the 12 main application player groups. We also go further and allow files and documents to be stored and cataloged at the system level (as a whole), at the group level (by any of the 12 main application player groups), or by individuals within the different groups.
  4. Another huge piece that we are doing is business world building concepts. This includes all 10 levels that we currently know about. They are: 1. Universe Level (the internet and all adilas pieces), 2. Galaxy Level (linked servers - both data and content servers), 3. Cluster Level (individual boxes, domains, or servers), 4. Solar Systems (databases within a cluster - could be one or more per box), 5. World Level (corporations, entities, and companies within a single solar system or database), 6. Location Level (stores, departments, or physical or virtual sub dividers of a corporation or business), 7. Group Level (see the main 12 application player groups listed above), 8. Individual Level (items, objects, and entities inside of a group. for example: customer 111, invoice 345, deposit 222, po 474, etc.), 9. Data Level (how and where are things stored in the database? what relationships exists? what is the story?, 10. Run all levels over "Time" (time is the current bottom level structure that we play in, on, and through, this same statement could be re-written as objects and data wrapped in time)
  5. Operation led accounting over time. Our use of time and how it plays into the whole story of what is going on. It allows for characters, relationships, overcoming trouble or problems, decisions and choices, cause and effect consequences, accountability, etc. That is where you get the whole story or being able to capture the pieces of the story. In short, we call it roll-call accounting. The system is able to go backwards and forwards over time to tell what the relationships were, are, and may be. This helps show how things were/are connected or accounted for over time. It is awesome!
  6. We have taken a traditional model or business model and created a fully integrated system. You no longer have to have 4-10 different pieces of software to run your business. You can use the full adilas.biz system or platform to run your business. You have access to all of the pieces, any time, under one roof. It works because it is a system.
  7. We have built the entire foundation on two main concepts. They are: permissions & settings. You can do almost anything with those two pieces. Permissions are who has access and what can they do? Settings are the how, when, how much, how many, and what to call it. This could also include show/hide, open/close, limit, defaults, etc. Settings and permissions may be applied on multiple levels. Technically, a person could add both permissions and settings on all 10 business world building concepts listed above (universe, galaxy, cluster, solar system, world, location, group, individual, data, and wrapped in time). That is a huge piece of the puzzle.
  8. One last thing that really needs to be there is the ability to be flexible. No two things are the same. People and businesses want access to features, functions, data, and processes from different angles and in different ways. This means that you have to 1. Be able to catch the data. 2. Can you get at the data that you caught? This also includes options for editing or changing the data. 3. Can you show it back to the user in the way that they want it? This goes out to custom levels and deals with interface, API socket connections, webservices, feeds, imports, exports, data trafficking, flow, controls, etc. What are you looking for? What is your goal? This is the results and/or interface of the application.

Anyway, those are some of the pieces that I see that we are doing and developing that could potentially be patented and/or copyrighted. They are listed here to start the process.
 
Click to view time photos.
AU 2872 August 2014 Monthly Recap 8/1/2014   The majority of time this month was spent on a huge database copy project. This is a really exciting project for adilas as it will allow greater flexibility and options for clients. This project included hours and hours spent prepping tables for copy, creating new database structures, planning, scripting database table levels, and more. With the ability to copy, move, and start new databases, it will be like the difference of allowing clients to have their seat on the bus (current shared model) or have their own motorcycle or agile vehicle (future individual model). Allowing clients to work in their own adilas environment, instead of a shared environment, will greatly increase the speed and agility of their adilas.

Other exciting new projects were started this month such as, working with a cash kiosk system to provide integration for users between adilas and cash kiosks. Adilas now has an expanded chooser section with over 20 new options available to all users. Initial tables and code for the in-line discount project were started as well as a custom behavior tracking project for a school.

After attending a copyright and patent workshop we continue to feel an ever-increasing need to get more information out about the core concepts which adilas has been built on and functions by. We want these core concepts and ideas to be freely known, available, and used by people all throughout the business world. For more information on this entry specifically, please see element of time #2774 here in adilas university.

*We hope you are enjoying the adilas developer's notebook! Please utilize and explore the vast search capabilities of adilas to find more information throughout the developer's notebook. For further questions, or help, please feel free to contact us at: support@adilas.biz.
 
Click to view time photos.
AU 3681 Brainstorming - Adilas Business Functions/Features 3/20/2014   This is a brainstorming document that was done from 3/20/14 to 3/27/14. It covers all 12 of the major business functions that adilas provides. The goal here is to focus more on the “sizzle” vs. the steak. The brainstorming was done by Brandon, Shannon, Dave, Cheryl, & others.

Goal/Objective: Show & tell all 12 Business Functions/Features – here is what this can do. Brief definition – this is what this is.
- What functionality – per business features – what, what, what – show me WHAT it can do. WHAT features does it have….
- From start to finish – follow this path all the way through – start to finish & review it

1. Sales, Inventory Tracking, & POS (Point of Sale):
- Serialized inventory
- Consignment inventory
- Hide/show line items (hidden line items)
- Advanced add to cart items
- Barcoding
- Package tracking
- RFID Tracking
- Custom labels
- Paperwork – custom
- Content Management
- Photos/Images
- Shopping carts
- Duplicating
- Vendor specific items
- Generic items
- Service items
- Tiered pricing structure
- Interface options
- Dynamic cart interface
- Quote – save as
- Discounts
- Contract pricing – using flex grid
- Adjustable invoice styles
- My Cart Favorites – Buttons
- Recipe/Builds
- Adjustable tax settings
- Multiple customers per invoice/quote
- Mixed tickets
- eCommerce – Point of Sale options
- Merchant Processing – credit cards
- Customer queue
- Item usages
- Flex Grid
- Transfers between locations
- Update inventory count options – shrinkage/loss
- Returns/refunds/exchanges
- Tie directly to customer PO’s – dynamic fields
- Custom search options
- Sell anything!
- Editable after the fact
- Record notes – printable & non-printing
- Searchable notes – searchable data

2. CRM (Customer Relationship Management)
- Unlimited logs
- Unlimited follow-ups
- Calendar
- Appointments
- Bill for time
- Track special data – customize your database
- Additional contacts
- Custom data fields
- Paperwork
- Photos/scans/images
- Content Management
- Export to Excel
- Email/text message
- Tie to specific sales associates
- Current receivables – past history
- Backend eCommerce login
- Pay portals
- Statements
- Apply payments
- Purchase history / statistics
- Link to any other application piece
- Custom search options
- Trending & marketing

3. CMS (Content Management System)
- Photos, scans, images
- Reference any file – local, remote, physical upload
- Unlimited & searchable reference library
- Documentation
- Custom documents
- Paperwork
- Contracts
- Custom mappings
- Direct to eCommerce
- Your data, your system, your world, your way!
- ??? – Something more…
- Custom search options
- Virtual World Building
- Look & feel
- What do you want? We’ll serve it up!
- Mix & blend
- Point & click interface

4. Online Expense Tracking
- Reimbursements
- Expense accounts
- Payments on account
- Payables
- Access from anywhere
- Enter data from anywhere
- Print checks from anywhere
- Bank reconciliation
- Automatically cascades to P&L
- Check requests
- Check printing
- Multiple payments
- Documentation
- Split between location
- Aging, due dates
- Dynamic reporting
- Exporting to Excel
- Bulk verify
- Unlimited banks
- Payroll
- Custom search options
- Photos, scans
- Digital filing
- Paperless office
- Automated…. ???
- ACH & EFT’s – wiring money

5. Payroll & Timecards
- Digital time clock – clock in/out
- Admin time cards
- Admin time clocks
- Commissions
- Salary
- Overtime
- Split deals
- Hourly
- Year to date summaries
- Unlimited departments
- Auto calculate federal & state withholdings
- Summary reports
- View/print my pay stubs
- Bulk timecard options
- Check writing
- 1099’s
- W-2’s
- Automatic annual updates
- Custom search options
- HR management
- Needed piece for every business – employees are used in other pieces of the puzzle – common denominator – wrap that up and present that well – potentially, on our side, take a day and create a few custom interfaces (that you could even flip to a mobile app) and just have this as an entrance (or get your foot in the door piece)
- Compensation
- Holiday pay/hours
- Vacation pay/hours
- Sick pay

6. Calendar & Scheduling
- ANYTHING
- How do you use time?
- Appointments
- Calendaring
- Scheduling
- Reservations
- To-do lists
- Projects – track subs and totals for projects
- Servicing
- Project management
- Pools
- Rentals
- Dispatching
- Bill for time
- Reminders
- Follow-ups
- Notices
- Dynamic naming
- Create & name your own time templates
- Scans, photos, images
- Content uploads
- 4 different report types/view: calendar, time slot, groups, & details
- Advance searching
- Add subs
- Tie to customer, vendors, locations
- Queue things to be invoiced
- Project status – what needs to be done or what status is it at
- Color code
- Unlimited notes, entries, sub dates & times
- Block out time spans
- Packaging
- GPS tracking
- RFID tag tracking
- Customer checkpoints
- Document processes over time, with time
- Customer facing calendar
- Registration
- Adding time to invoices & quotes
- The underlying concept – ALL things run over time

7. Create Data Relationships Between System Players
- Natural relationships
- System maintained relationships
- User maintained relationships
- Special relationships – connections
- Flex Grid Tie Ins
- Custom fields
- Customizable databases
- Unlimited notes
- Unlimited connections
- Customizable reports
- Relationship builder
- Virtual buddy system
- Process & flow relationships
- Roll call – anytime
o Who
o What
o When
o Where
o How many
o How much
o Who else – other connections
o Why
- Systems thinking
- Cause & effects
- Telling the story
- Records all processes
- Histories – system recorded histories – when/who did this?
- User recorded histories
- Linking within system groups
- Core concepts
- Accountability
- World Building – creating realistic & logical relationships
- Objects – objects & data over time
- Multiple access points – multiple entry points
- Visual organization & structure in data relationships

8. Backend Office & Accounting Functions
- Automated Balance Sheet
- Automated Profit & Loss Statement
- User maintained Balance Sheet flexibility
- Automates 75%+ of your financials
- Live feedback
- Live financial report for any data – even historical
- Searchable
- Editable
- Build in audit trail
- Tells the story
- Tax reports
- Automated cause & effects
- Banks
- Inventories
- Receivables
- Payables
- Floorplan
- Checkbooks
- Check-writing
- Payroll
- Commissions
- Withholdings – taxes
- Shrinkage, loss
- Documentation
- Photos, scans
- Content
- Forms – standard forms
- 1099’s, W-2’s
- Operation led & accounting automated – horse before the cart
- Simulate traditional accounting using modern technology
- Business mapping data over time & data relationships
- Entries are objects & portions of information progress/flow forward
- HR management

9. Histories & Reports
- ALL Data Is Live And Searchable (& retrievable)
- Data in – data out
- Usages
- Histories
o Financial
o Effectual
o Historical
- System history for every action
- Quick search
- Advanced searches
- Exports to Excel
- Save as pdf
- Print reports
- Dynamic filtering & searching
- Wild card searches
- Drill-down to multiple layers of data
- Any data in – is retrievable!
- Build your own reports
- Date sensitive reports
- Pre-set criteria
- Custom reports
- Search & retrieve ALL data!
- Know the data source – where is that information stored
- Just in time reporting – live, flexible reports
- Retrieve information for marketing, HR, sales, inventories, financials, trending, usages

10. BI (Business Intelligence)
- Def: The pulse – what is happening in your business, who/what is involved, how does this play, they want to know the story – all of this is done with data, using data to tell the story, analytics, what does this mean, interpreting, marketing, trending, etc.
- Provide the History & Reports ***
- Usage
- Interfaces – dashboard level
- Return & report
- Track usage, data, interactions, history, etc.:
o Customers
o Invoices
o Stock/Units
o Items/Parts, Inventory
o Deposits
o Expense/Receipts
o PO’s
o Vendors
o Employees/Users
o Quotes
o Elements of Time
o Balance Sheet Items
- Relational data interactions
- Dynamic data levels – unlimited – one to many to many relationships
- Thank you adilas for making our lives easier!
- Spend time analyzing & tracking data instead of building
- Cutting edge – fastest browsers, new technology
- Graphs, charts, visual representation for data
- Data projections
- Anytime roll call – return & report
- Cascading, flexible, dynamic
- Just in time – reports, history, recall, financials – what do I want to look at right now
- Cloud based – centralized data – access anytime, anywhere
- World Building:
o Universe level
o Galaxies
o Clusters
o Solar System
o World
o Location
o Groups
o Individuals
o Data
o Run All Levels Over Time
- B2B or business to business interactions
- Technology advances – memory, storage, processing power
- Playing to where things are going
- Future vision – anticipating, trending
- The tools to reach future vision
- Adaptability
- Make appropriate changes according to your data
- The data & reports to make your business decisions – research, marketing, trends, etc.
- Affordable
- Enterprise toolset for small to medium businesses
- Cutting edge system for the right price
- Grows with your company – reflects your
- Time efficiency ***
- Quick access & accountability for business functions
- Business stimulating ideas
- Project management – managing business
- Entrepreneurial idea type system vs. more rigid/fixed systems
- Multi-accessible, editable, adaptable flow vs. linear, rigid flow
- A living tool

11. Web Presence & eCommerce
- Online elements of time & calendaring options – scheduling, appointments, rentals, reservations, class seats, projects, timelines, check-off processes, etc., etc. (not exposed yet)
- Online quotes/orders
- eCommerce – cart to payment to shipping functionality
- Continual updates & releases
- Adjustable settings & eCommerce options
- PayPal
- Multiple Merchant Gateways – Authorize.net, Maxx Merchants, Merchant One, USAePay, First Data
- Shipping API’s
- Merchant Gateway API’s
- Marketing/messaging API’s
- Promotion codes
- Special web pricing
- Marketing – sales
- Futuristically… smart menu – that helps track & calculate time according to the tasks you choose
- Downloadable products – E-products
- Customer login options
- View user history, view your quotes, your invoices, your accounts
- Online bill pay
- Assign monthly rates for varying levels of customer use
- Specify features for different customer types
- What do you want your site to do? Dream it up! We’ll wire it up!
- Full integration with your adilas system
- Real time inventory counts & tracking
- Free canned version with adilas subscription – custom upgrade to whatever level you want to play
- Photo management
- Descriptions
- Categorization
- Settings
- Customizable look & feel
- Connect the adilas engine to your already functioning website
- Educate your users – CMS
- Custom contract, disclaimers, agreements, paperwork
- Link to external sources, upload additional content
- Videos
- Connect with social media – Facebook, twitter, LinkedIn, Pinterest, etc.
- The entire adilas engine
- Interconnected
- Free
- Ready to go
- eCommerce ready to go POS system
- affordable eCommerce packages
- Show/hide things on the web instantly from within your adilas: locations, items, stock/units, contact information, etc.
- Permissioned & protected inside adilas – then eCommerce – separate but fully integrated customer facing side
- SEO automatically functioning: photo management, descriptions, your content (maximize for your company’s name) – to incredible levels
- Contact us links
- Future: mix & blend eBay & adilas & other big markets
- Phone, call-in, mail order, - for web presence
- Emailing invoices
- Direct logins
- Customer pay portals
- Touch screen eCommerce – drag & drop
- Multi functionality
- Recipe/building

12. Virtual Data Portal (Big Data)
- Archive data
- The entire adilas package
- Data sphere – data world
- ANY data, ALL data
- All file types
- POS, eCommerce, scheduling, expense tracking, all of the 12 business functions here in one nifty little package
- All Data Is Live And Searchable
- Manageable data
- Affordable data system
- User friendly system
- E-Business buffet – what do you want???
- Your business, your way!
- World Building Concepts:
- Cache, secure & retrieve data
- Cross-company data sharing: vendor to supplier, or vice versa, to retailer, to …
- Fun
- Understand relationships – cause & effect
- Systems thinking – systems working
- Collect data as it’s happening – filter as needed, retrieve as desired
- Searches data, crunches data
- Data in bulk
- Customer reports, returns
- Unlimited data – mess volumes
- Dream it up!
- Work with the whole or filter down to smaller sections
- Start to finish on processes
- Plan it out – accomplish it in the system
- Centralize the data
- Follow the entire process through the data
- View the entire history
- Tell the story
- Visualize it your way – graphs, tables, charts, rows & columns
- Educate on big data – make it less intimidating
- Making big data consumable
- Normal operations create the big data – the sum of your normal operations create the whole – your big data
- Creates all the connections & links from normal flow
- Making informed decisions – make the best decision by having the best data
- Making choices based on actual data
- The whole, complete, inter-connected package
- Build your world, create your interactions, populate your world, create your own processes, view any piece at any time
- ADILAS – ALL Data Is Live And Searchable
- It comes line upon line, piece by piece – normal operations –big data
- The adilas formula is: Results = Mix(Functions, Players, & Concepts)
- Tech, tools, & maintenance
- Needs – trouble motivates action
 
Click to view time photos.
AU 2052 Daily Ideas 3/1/2014   -Adilas flex zone timeline drawing (Sketch of flex zones or virtual waiting rooms, with checkpoints and permissions, and time going in either direction.) (See scan in photo gallery)
-Life has to have some flex zones or small waiting rooms.
-There may be things that are unfinished – that’s okay, they will stay in the flex zones until they are ready. When ready, they may be advanced to the next stage.
-There will be time – just keep going.
-Instead of just one timeline (like the graphic or drawing above), there are multiple time lines working together. Time, itself, has many one-to-many relationships. They all play into the bigger whole but are made up of tiny little individual pieces and parts, kind of interesting.
-We have a client that is looking for EDI (Electronic Data Interchange) pieces and functions. Steve has done a little bit of research and we’ll only start heading in that direction if needed. EDI is basically a way for one or more computers to talk to each other.

Notes from a phone call with Steve on 3/1/14.

- Let our developers build their own clientele. Our reps already do this on their own.
- Our current top three priorities are:
o Package stuff,
o Split Cart functions (interface),
o API (application programming interface) & 3rd party plug-ins.

- Custom documents are a good profit center for adilas. This could include:
o Documents
o EDI – Electronic Data Interchange
o Outside Feeds
o Internal Feeds
o Loyalty Points
o Customer Gift Cards
o Labels
o Barcodes
o RFID
o Reoccurring push/pull actions
- Maybe think about bulking up or beefing up the custom pipes or custom documents area.

- Use the barcode generator (if possible) for some of the custom pieces. If needs be, we could always create a new barcode generator or custom label app if we needed something more robust.
- Packaging and subs of part numbers or subs of item numbers.
- The deeper we get, the more elements of time appear to be connected to everything else in the system.
- Packages and conversions are almost one in the same. One is limited or quantified and the other is open ended or unlimited.
- Should we make a whole new item type??? A mix between a stock/unit and a general part? What about backward compatibility (people wanting to go backwards)???
- Steve kept using the phrase “occurrence of…” or “instance of…” when talking about tracking packages. Virtual usage.
- The naming has to be dynamic… Just like in elements of time.
- Batch, packages, reports
- Maybe store dynamic parameters (actual JSON objects) inside of the subs for time called sub comments. These fields are big, they accept HTML, and they are already a sub of time.

- Maybe use time for packaging and expiration dates as if it was manufacturing. Think both retail and manufacturing of packages, lots, batches, etc.
- On part categories… what if we allowed categories to be stacked inside and/or on top of other categories. Allow it to go as deep as it needs to go.
- If we let simple objects connect to each other and to themselves, how do you go back up the chain? I am talking about showing the relationships. Instead of simple nested part categories… what if it were people connected to other people (say like genealogy). The person exists as a single object, they could then be connected to other people or other objects to create a relationship. The relationship then helps to define how they interact and any dependencies or other independent states that exist. It basically starts forming the story as the objects and data move or interact over time.
- Make the teaching graphics available, to all users, that we use when doing adilas demos and training sessions. Add a muffin tin, add the dream it up, and add a cup and plate model with an underlying platter or bigger tray. Think stacking objects.
- Teach base level core concepts like operations and accounting.
- We are going to need a sales and setup team inside of adilas. Help them sell what we have!
- Our best sales people are involved in the setup process.
- Create a small setup team using existing persons.
- Do weekly demo meeting to help get awareness up.

- On packaging… what about packages of packages or deep one-to-many relationships?
- Packaging may need its own barcode. This could be something simple or it could be cryptic for a main time id, something in the middle, and then a sub of time. Just trying to get ideas.
- On elements of time… We have the “anything” sub – pools and subs. We need to get that ready for use.
- Packages may contain more than one item. Possible mixed items.
- The mother is “time” – then anything that gets applied will be the sub.
- Moving items from a “shelf” to a “package” or subset. Think about moving pieces into other pieces. Basically, it is all mini manufacturing or internal builds.
- Show the usage over time.
- Elements of time… this becomes the master.
- “Any” scheduler – everything needs to be tied to elements of time.
- Push out the developer’s notebook – stake our claim on some of these emerging ideas – do it in a fashion that helps build and share. Remember, “The rising tide raises all boats.” I think the real quote says “ships” but I like boats better. Ships seem so big. Anyway, help raise the tide!
- Work smarter, not harder.
- Allow all or “any” of the pieces inside of adilas to be plugged into time or into an element of time.

- The different report types are:
o Calendar
o Time slot
o Grouped
o Details
o Advanced (pick & choose)
o Subs and stats
o Export to Excel
o Time Line Horizontal (new)
o Time Line Vertical (new)
o Other Formats (new & futuristic)

- What if we used Cold Fusion to dump and display objects inline using a cf dump tag. This may have a place, especially in the API documentation and testing zone.
- We would like to set up a number of adilas training centers. This could be a great business for us and/or other interested parties.
- Prep for a demo meeting.
- Use Bridgerland as our first adilas training center. It is a great fit and is already in use.
- Pass out flyers for the free demo. Maybe pay a team member $10/hour to pass out flyers.
- We are shooting for 50 new clients.
- Do the weekly demos on Thursday night from 6-8pm.
- Use BATC (Bridgerland) or the Business Resource Center for the software demos.
- Maybe show a calendar on the main login page. Have drill-downs to different details, photos, links, and other content.
- Have the same calendar show-up on the adilas training page. Start using elements of time.
- Get adilas university up and live with help files, developer’s notebook, and training and videos.
 
Click to view time photos.
AU 3675 Planning - Packaging & To-Do's 3/1/2014   Packaging & To-Do’s:
- Check the credit cards and make sure things could clear
- Let our developers build their own clientele
- Split cart
- Package stuff
- API & 3rd party
- EDI – Electronic Data Interchange
o Push or pull or catch
o Application flex grid stuff
o Two computers talking to each other
- Custom documents are a profit center for us
o “Custom” – Beef up pipes or bulk up that area
o Documents
o EDI – Electronic Data Interchange
o Feeds
o Loyalty Points
o Custom Gift Cards
o Labels
o Barcodes
o RFID
o Reoccurring Push/Pull Actions
- Barcode generator – maybe allow custom to go through it or have a whole other flash app that can take custom

Packaging…:
- Elements of time – sub of everything
- Package thing & conversion thing are one in the same
- New item type???
o Backward compatible
Process:
- New item
- Track quantity
- “Occurrence of”…
o Sub of the items that exist
- Naming has to be dynamic… elements of time
- Usage or occurrence of… both quantitative and unlimited
- Batch, packages, reports
- Dynamic parameters (JSON objects) stored inside of the sub comments of time
- Use time for packaging as if it was manufacturing
- Retail and manufacturing of packages
- On subs and sub part categories… what if we allowed categories to be stacked inside and on top of other categories. Allow it to go as deep as it needs to go.
- If we let simple objects connect to each other and to themselves, how do we go back up the chain? Show the relationships. Instead of part categories… what if it were people connected to other people (genealogy). The person exists as a single object, they could then connect to other people or other objects to create a relationship. The relationship then helps to define how they interact and the dependencies or independencies that exist. It basically starts forming the story or the objects and data move or interact over time.
- Get graphics available to all users – training sessions
o Add muffin tin
o Add Dream it up!
- Teach base level core concepts like operations and accounting
- Sales & setup team
o Sell what we have!
o Sales people need to be involved in the setup process
o $35
o Create a small team
o Weekly demo meetings (2 hours)
Packaging… Continued:
- Packages of packages
- One-to-many relationships
- Own unique barcode for the package
o Main time id, something in the middle, sub of time
- Time – “anything” – parts & such
- Conversions = unlimited & packages = limited or quantified
- Packages may contain more than one item
- The mother is “time” then anything that gets applied will be the sub
- Moving items from a “shelf” to a “package” on subset. Think moving pieces into other pieces. Basically, it is all mini manufacturing or internal builds.
- Show the usage over time
- Elements of time… this becomes the master
- “Any” scheduler
- Everything needs to be tied to elements of time
- Push out the developer’s notebook – stake our claim on some of these emerging ideas – do it in a fashion that helps build and share. The rising tide raises all boats (ships). (I like boats better, ships seem so big.)
- Work smarter, not harder
- Allow all or “any” of the pieces inside of adilas to be plugged into time or into an element of time.
- The different report types are:
o Calendar
o Time slot
o Grouped
o Details
o Advanced (pick and choose)
o Subs and stats
o Time line horizontal (new)
o Time line vertical (new)
o Export to Excel
o Other formats (future & now)
- What if we used ColdFusion to dump and display objects inline using cfdump tags.
To-Do:
- Adilas training centers
- Prep for a demo meeting
- Bridgerland as our first adilas training center
- Pass out flyers for free demo
- My brother
- $10 per hour to pass out flyers
- 50 new clients
- 6-8pm on Thurs.
- Business resource center for demo
- Call intern
Classes: (adilas training)
- 6th: 12 – elements of time & 2 – flex grid
- 13th: 12 – Inventory & 2- Sales
- 20th: 12 – recipe/builds & 2 = expense/receipt
- Basic Sales & Inventory
- Recipe/Build Class
- Flex Grid
- New Features
- Elements of Time
- Expense/Receipts
- Payroll
- Show a calendar on the main login page. Have drill downs to details, photos, links, and other content.
- Have the same calendar show-up on the adilas training page.
- Get adilas university, live with help files, developer’s notebook, etc.

Packaging & Tracking – Goals:
- Track – Lots, S/N, Package, etc.
- Custom naming
- Chain of custody
- Ease of use
- Deal w/bulk track individual
- Conversions (1st)
- Packaging
- 1-many-many-1-many-many
Goals & Conversions:
- Trade by lowest
- Common factor
- Beware of rounding
- Standard vs. non-standard
- 2 tables:
o Units of Measure
o Linker – UofM x:y, UofM
 
Click to view time photos.
AU 3634 Brainstorming: On the Adilas Team & Adilas Application 12/31/2013   Scan: Notes from a meeting – Thoughts on an adilas team
- Don’t lose the entrepreneurial spirit. That’s a gem! Dream it up and go get it!
- Sometimes we may be missing a huge key piece of the puzzle.
o Maybe a huge piece we are missing is the custom code work and consulting sections. We are allowing tons of outside reps & consultants make tons of money on our product. We may need our own little team that could capitalize on those pieces.
o What are our inputs & outputs?
o Where are our needs?
o How can we solve those needs?
o We need to help pick up what people want.
- Keep building toward the dream. Spend time on where it needs to go.
- Keep doing good and keep serving. Sometimes service pays more than hard money. Story about a guy buying a pack of cigarettes from a lady who was trying to quit. That little act of service was still in force 40+ years later. Great story.
- Going back to the pieces we are missing. There are tons of jobs and projects. Let’s internalize them and allow other people’s money to help fund those projects. Why couldn’t adilas have a team that does sales, consulting, and custom implementation. That may be the next phase of growth.
- On a different note, we really need to help map out the system. A virtual adilas “you are here” or a flow chart of what goes on. An adilas GPS system or sorts.


Scan: Edits & Notes to the Results = Mix(Functions, Players, Concepts) Flyer
(Please see scan in photo gallery)
Get results by applying business functions, application players, and core concepts. Here is a quick look at what we bring to the table to help you run your business.

Results = Mix(Functions, Players, Concepts)

It would be so cool to make a flyer for each one of these things. Not just a flyer per section but a flyer per line 1-12 on all 4 sections.

Results: (Turn this into questions & statements. Who, what, when, how, where, why?)
What are you looking for? What is the goal or outcome?
1. Get Something for Your Pain
2. Make More Money
3. Custom Interface & Graphical Look/Feel
4. Flow & Processes (Logical, Smooth)
5. Tracking Numbers & Data Values
6. Tie-in Paperwork & Documentation
7. Archive & Storage of data
8. Search-ability – All Data Is Live And Searchable
9. Ease of Use
10. Custom Business Solutions
11. Other Goals & Output
12. You Name It… Dream it up, we’ll wire it up! Dynamic & Adaptable – Your e-Business buffet!

Application Players:
What tools are you going to use?
1. Customers
2. Invoices
3. Quotes
4. Vendors
5. PO’s (Purchase Orders)
6. Parts (General Inventory Items)
7. Stock/Units (Serialized Inventory)
8. Deposits
9. Expense/Receipts
10. Employee/Users
11. User-Maintained Balance Sheet Items
12. Elements of Time (Calendar & Scheduling)

Business Functions:
What do you want? How will you reach your goals?
1. Sales, Inventory Tracking, & POS (Point of Sale)
2. CRM (Customer Relationship Management)
3. CMS (Content Management System)
4. Online Expense Tracking
5. Payroll & Timecards
6. Calendar & Scheduling
7. Create Data Relationships Between System Players
8. Backend Office & Accounting Functions
9. Histories & Reports
10. BI (Business Intelligence)
11. Web Presence & eCommerce
12. Virtual Data Portal (Big Data)

Core Concepts:
Why & how does it work? Virtual world building…
1. Capture & Record the Story
2. Groups, Characters, Players, & Individuals
3. Relationships
4. Trouble, Problems, Needs, & Goals
5. Decisions & Choices
6. Consequences (Cause & Effects)
7. Accountability
8. Permissions & Settings
9. Systems Thinking
10. Vision & Future Developments
11. Tech, Tools, & Maintenance
12. Objects & Data Over Time

Each corporation inside of adilas is its own little fenced in area or world… where only assigned users for that corporation may play and/or participate. Corp-wide settings allow for variations and custom usage of the adilas platform.


Scan: Adilas Results Flyer
Updated Adilas Results Flyer
(Please see scan in photo gallery)
Free Weekly Demos


Scan: Sketch – One to Many Relationships, Mixing & Blending
Sketch – One to Many Relationships, Mixing & Blending
(Please see scan in photo gallery)


Scan: Adilas.biz eBusiness Seminar Brainstorming
Adilas.biz eBusiness Seminar Brainstorming
Adilas.biz eBusiness Seminar flyer:
- Business functions
- More white space
- Less wordy
- More marketing


• Sales, Inventory Tracking, & Point of Sale
• CRM (Customer Relationship Management)
• Payroll, Timecards, & Online Expense Tracking
• Calendar & Scheduling
• Backend Office & Accounting Functions
 
Click to view time photos.
AU 1872 Daily Tasks 11/29/2013   • One of the interns and my sister came over to work on the adilas user guide. We started out brainstorming at the table. I had the intern talk about disruptive innovation vs. sustaining innovation. We then talked about byproducts that adilas creates. We talked about selling services and the need for adilas world (virtually selling people and their skills). We then printed out some graphics of the interactive map, the adilas GPS core, and the cups and plate analogy. We also printed out outlines for the adilas user guide – steps to success. We went over 30+ topics and had light brainstorming on core concepts and pieces. The list was taken from section 4 of the user guide. Great session and good progress.
• Emails.
• Went over to my brother’s house. He gave me 43 new videos. He has been working really hard lately. Great stuff. I now have almost all of the October adilas training cut and edited. That is awesome! 30 miles.
• Spot checking and uploading new videos to YouTube.
 
Click to view time photos.
AU 1782 Daily Tasks 9/19/2013   • Emails and tech support. Got a call from a client about the new Texas 130-U application form.
• Adding an option for Steve to be able to upload to the public folder on adilas.
• Prep for interviews. Emails and getting things lined up and ready.
• Went in to town to conduct some interviews for adilas interns. I picked up my sister and we went in together. On the way we were talking about tools and what they do and what they require. We then started talking about models and how to break models and tools. That was fun. We even talked about how to break our (adilas) current model. We talked about where it needs to go and how to get there. We got to the University and met our first appointment. She was from India, what a sharp cookie! Both my sister and I were blown away and she seemed to be just beaming with potential. She had done some research, she had good questions for us, she presented herself very well, and both my sister and I were smiling the whole time that we talked. Great interview. For our next interview it was another lady and she had smaller skills and lacked confidence. My sister and I then had a brainstorming session waiting for our next appointment. We were talking about how to introduce our system players and groups. We talked about introductions, abilities, What does it do?, Who are its friends?, How does it interact?, What are its weaknesses?, Limitations?, and Shortcomings? We talked about usage and frequency. As we got deeper and deeper into the analogy my sister had the idea of going clear up to the “world” level. We talked about an analogy of going to an ice cream shop and virtually choosing your flavor. Very diverse and no good or bad choices – just different flavors. We also talked about basic intros and then branching according to flavors. Great brainstorming session.
We then drove to Bridgerland and met with a lady. She was at the last adilas training session. All three of us continued the brainstorming that my sister and I were doing up on campus. We ended up with ideas that the business functions that adilas does or ways to use the system are like our menu options – what do you want? The groups of application types (players) are the pieces we mix and blend to get you the results you are looking for. As we mix and blend system players we can give the desired business function or outcome. We had a good time. As far as the core concepts and theory, those pieces are the supporting roles or foundation that create the malt shop itself. They are ever present and support the functions and players. After our meeting we setup this associate with her own little adilas account. 30 miles.
• On the phone with my brother trying to figure out options for video editing. I got an email from Steve and David about cost and what we are getting for that cost. Good stuff. We may need to alter our current flow, but good stuff.
 
No po photos available. Click to view time details.
AU 1768 Daily Ideas 9/3/2013   -“Data in detail” – Quote by my father on 9/3/13 while on a morning walk. He said that one of the things that make adilas unique is – “Data in detail.” Another one from him is, “Not all data is created equal.” – February 2013 training session.
-The receive invoice page needs some pagination. It also needs a paid date to be shown. This is an older page that has not had much action for quite some time.
-We talked about doing a “get to know you” flyer for the groups and system player groups. I also think we need to do similar type flyers for the functions and core concepts. We need to let people know what we are doing!
-A future project might be to document what each page inside of adilas does and what page params it allows and/or requires.
-On the adilas API (application programming interface), we need to check for an SSL connection. If not, we need to prompt. If any decoding is needed, we need to decode or encode values as needed. This needs to be done on the application level. Not at the user level.
-When showing the tech level of the API or adilas university – Go by function not by page. Show the concepts or how the different methods work and function, not necessarily how our pages work and flow. Show the users what is available to them through the API. If needed, show main page flow. This should help the end user understand what is going on.
 
Click to view time photos.
AU 1760 Daily Ideas 8/26/2013   -Recording notes about world building concepts. Saturday night into Sunday morning, I woke up due to a dream that I was having. I was fasting for help and trying to figure out how to best keep the balance between work, family, church, and personal. These notes may need to be adjusted slightly, I was scribbling on post-it notes as fast as I could.
-3D printers – I was thinking about how a 3D printer takes an AutoCAD or technical drawing converts the document into a physical item by outputting ply plastics in the shape of the object. It is able to go in multiple directions such as sideways, up and down, and back and forth. Pretty cool! (Another idea – what about a number of robot arms all working together to build something.)
-What if you put a bunch of 3D printers together all building the same output or project. I was thinking of relating these multiple 3D printers to the main 12 groups or system players inside the system. Imagine a number of 3D printers for customers, invoices, quotes, vendors, PO”s (purchase orders), users, stock/units, parts, elements of time, expanse/receipts, deposits, and user-maintained balance sheet items; Imagine these 3D printers working in tandem or working together as different things related together (called tie-in or relationships).
-Use this concept of multiple 3D printers to help show world building concepts.
-Blocking or rough layouts. Most projects start out with a general plan. As things develop, more and more details will be added. Say for example you wanted to “rough in” or “block” a car. It might look something like this (notebook sketch) – very loose and only represents a light form or blocking…
-As more details are added or carved out, the more the “blocked out” item becomes what it needs to be. This is a process and maybe even a progression. For example: The blocked car could become: (sketch of a car progressing from a blocky outline to a more refined and then detailed and accessorized car). Almost like a Cub Scout pine wood derby car being made.
-Think multiple systems playing together over time.
-Each with their own functions and/or jobs.
-Eventually it tells the story as you run it over time.
-2 key components of “blocking” are: Catch and hold the data in a central location. Once you have those two things (the data and it is centralized) you could detail them out.
-Include the adilas core concepts. They are:
1. Characters
2. Relationships
3. Trouble, Problems, Needs, and Goals
4. Decisions and Choices
5. Consequences (Cause and Effects)
6. Accountability
7. Objects and Data Over Time
8. Permissions and Settings
9. Systems
10. Vision and Future Developments
11. Tech, Tools, and Maintenance
12. The Story
-By applying these concepts, you only limit yourself to what you can dream up or how deep or far off is your vision… keep it positive. Think potential!
-Circle back around to goals, planning, output, and needs. These could even by dynamic and/or changing… sometimes that may be scary… but sometime that is what is needed.
-The 5 story building concepts from Brandon Mull, author of “Fablehaven”, “Beyonders”, and “The Candy Shop Wars”. www.brandonmull.com/site/video-bestbook.html The main 5 are: characters, relationships, trouble, decisions, and consequences. I’d like to relate those to world building concepts for businesses.
-What’s your story or what’s your world?
-Spell it out without getting too wordy. Say 2-5 pages.
-This concept “world building” is one of the things that makes adilas unique as its own system.
-If you don’t want to play at this level, that’s okay.
-These concepts are pioneering the future of business and how systems will track things.
-Ours is a first generation, stable product. Eventually it will get leaped or leap frogged by a next generation product. We may even leap frog ourselves. This is just the nature of progression. It is part of the game.
-Our goal is to share and take a small crack at “Tradition”.
-This is a modern-day pioneering!
-Solicit help and ideas – from different sources.
-Dream it up – we’ll wire it up!
-Balance is one of the goals. Pull it back to the goals.
-King Benjamin, in the book of Mosiah, has some great advice about balance. See Mosiah 1-5 in the Book of Mormon.
-Apply it if you know it!
-Define the terms and concepts of world building – lightly. These are the 12 main core adilas concepts.
-A different approach – may need to be taught differently! That is okay!
-My dad’s ideas on transitioning and progress… “Moving Forward” and “Project Next”.
 
Click to view time photos.
AU 1242 Daily Ideas 5/27/2013   -Ideas for a flyer… “World Building”. I had the idea to do a flyer about the concept of world building and telling the story. This could include a number of concepts and how they help to “tell the story”. Include: characters, relationships, trouble, decisions, consequences (From the author: Brandon Mull)
-Along with the world Building flyer… Add an analogy between the human world and the adilas world. This might need a little help!
Human World vs. Adilas World
Universe - Adilas admin
Worlds/locations - Corporations/locations
Populations/Groups - System Players
Individuals/Objects - Main Objects
Data Level - Data Level
-World building and telling the story: universe, world, locations, populations/groups, individuals, data. Do a flyer that talks about world building and telling the story. Include adilas core concepts. (This whole flyer is the why)
 
Click to view time photos.
AU 1178 Daily Tasks 4/30/2013   • On the phone with an associate and replying to emails.
• Setting up a digital capture system to start working with the first adilas training course. We have 16 video tapes from February of 2013.
• Recording notes from the Colorado trip. Going over meeting notes with my wife and reviewing footage from the first adilas class back in February of 2013.
• On the phone with someone from the LDS Church. I sent him an email with adilas information. I got his number from my brother.
• New logo for two companies.
• Making a small movie using Windows Movie Maker.
• Uploaded the movie to YouTube. It is a 20 minute introduction to adilas and who the key players are.
• Working on a second core concept video for adilas.
• Added a second concept video to YouTube.
• Updated pages and posted new links on the homepage.
• I also added the new videos to the news and updates page.
 
Click to view time photos.
AU 1166 Daily Tasks 4/18/2013   • Light tech support.
• Then on the phone and using GoToMeeting with Steve about his custom code pages he is working on. He is learning tons and doing great. A fun side note is he is using our internal API to create his custom files. The more he uses our own API, the more he sees how that can be used by other outside developers.
• Brainstorming, tech support, and working on the introduction to adilas.biz flyer. Added a new formula that talks about what we do. It is: Results = Mix (Functions, Players, Concepts) I then listed 12 results, 12 functions, 12 players and 12 core concepts.
• Working on two different flyers. One is a simple introduction to adilas. The other deals with the concepts and formula for adilas key pieces. Lots of small tweaks and having my wife read over parts.
 
Click to view time photos.
AU 1163 Daily Tasks 4/15/2013   • Brainstorming and working on narrowing down main core concepts and theories for adilas. Come up with 12 core concepts, 12 main players, and 12 business functions.
• Organizing functions, players, and concepts. The server had some troubles and we had a reset.
• On the phone with a bank associate talking about Business products.
• On the phone with my dad and a contact from USU printing. I will be doing a demo with him the first part of May.
• Writing down ideas and concepts.
• Adding a news and update page.
 
Click to view time photos.
AU 1190 Daily Ideas 4/15/2013   -Similar to the mix and blend comment above… I think that I will start using this phrase…
- “Get results by applying business functions, application players, and core concepts.”
-In short – Results, Functions, Players, and Concepts.
From 4/9/13 to 4/15/13 I had an explosion of ideas and concepts. I was trying to boil hundreds of concepts down into smaller categories. I ended up with these 12 core concepts. Many of these top level concepts have tons of subs.
1. Players
2. Relationships
3. Problems, Needs and Goals
4. Decisions & Choices
5. Cause & Effects
6. Accountability Core Concepts
7. Objects & Data Over Time
8. Systems
9. Permissions & Settings
10. Vision & Future Developments
11. Tech, Tools, & Maintenance
12. The Story
These are some other thoughts that haven’t made it in to my notebook. Most of them come from 4/9 to 4/15.
- Inputs & outputs – “you get what you give!” Normally you hear “you get out of it what you put in to it.” What if you shortened that saying to… “you get what you give!” That changes its meaning incredibly.
- Weakest link affects the whole.
- Confidence
- It takes work
- Think logically – what happened in real life and how would I do that in a virtual world?
- Flag & date
- If correct, let it flow~
- Checkpoints
- Computers are dumb, powerful, but dumb. You have to tell it what to do.
- Everybody uses the system differently.
- World building and telling the story.
- It may be overkill at times but it helps track the story, even if it gets complicated.
- You tell the story, we then help you map backwards to show where things were at.
- Push vs. Pull – give automatically or wait until asked.
- Concept buffet – tons of topics.
- You find what you are looking for.
- eBusiness Model
- All elements work together, interacting and influencing one another.
- Objects are defined by relationships.
- Be willing to change. If we replace bad habits with good ones, it can dramatically improve or reinforce the change. That is good!
- Focus on and teach people! The actual subject is secondary. That is hard to remember sometimes.
- It is okay to testify of truth wherever it is found!
- What is adilas? A complete package. It is way more than just a “sales & inventory tracking system.” You get everything!
- Confidence – feeling good about yourself and what you have done. And knowing and/or believing you can do it.
- Everything starts with your goal. What do you want to do? What do you need? Once we know that, we then look or think about the tools to get the job done.
- Say you go to the grocery store. You have tons of options. If you know what you want, you just go there. If you don’t know what you want, you start walking aisles. Inside of adilas, it is the same way, if you know what you want (you have a goal) you just go there. If not, you may feel stuck or may get frustrated.
- Portability – ability to move or change.
- Industry specific – skins and interface.
- Construction… you could build anything with a saw, a drill, a hammer, and a screw driver. If you know how to use them and what they do. Think – goal, tools, and then how to apply the tools or concepts.
- I love the word “apply” or “applied”. That means putting things to action.
- My son was reading the word “turnkey” and he turned it into “turkey” (gobble, gobble). He then said adilas was a wild turkey chase. You go all over the place like chasing a wild turkey. I thought it was kind of funny!
- What you do physically every day… we capture that in a virtual environment. The system is like a physical extension of physical actions.
- Our people need to be willing to try and love to learn.
- We have an engine.
- Stick to the fundamentals… do it over and over, stack and stack and stack.
- We are pushing towards a self-service model.
- Use GoToMeeting and do weekly training sessions. This could start adilas university with very little money. Maybe getting up to 2 classes a day, 5 days a week.
- Along with that, it may be good to pay a rep or someone to teach a class. Say $40 per session or $50 per session. 2 hours.
- We want to use a new landing page for notes, updates, news, and upcoming training events. This page would pop up when a user logs in each day. Maybe set a session variable and if 0, show the page. If 1, let them bounce around as needed.
- The main adilas.biz and adilasuniversity.biz site both need some loving.
 
Click to view time photos.
AU 2281 Brainstorming - Adilas Functions, Players & Concepts 4/15/2013   - Pushing towards a self-service model
- GoToMeeting – weekly training session
- Pay for training sessions
- New page when you login – training & updates
- Adilasuniversity.biz – 2 classes a day, 5 days a week
- New front end for the main website
Adilas…..
- Core concepts
- Application players
- Business functions
- Results
“Get results by applying business functions, application players, and core concepts.”
Business Functions (Results & Outcomes) what do you want?
1. Sales, Inventory Tracking, and POS (Point Of Sale)
2. CRM (Customer Relationship Management)
3. CMS (Content Management System)
4. Online Expense Tracking
5. Payroll & Timecards
6. Calendar & Scheduling
7. Create Data Relationships Between System Players
8. Backend Office and Accounting Functions
9. Histories and Reports
10. BI (Business Intelligence)
11. Web Presence and eCommerce
12. Virtual Data Portal (Big Data)
Application Players (tools to use) – What are you going to use?
1. Customers
2. Invoices
3. Quotes
4. Vendors
5. PO’s (Purchase Orders)
6. Parts (General Inventory Items)
7. Stock/Units (Serialized Inventory)
8. Deposits
9. Expense/Receipts
10. Employee/Users
11. User-maintained Balance Sheet Items
12. Elements of Time (calendar and scheduling)
Core Concepts – (why & how) – (why & how does it work?)
1. Players
2. Relationships
3. Problems, Needs, and Goals
4. Decisions and Choices
5. Cause and Effects
6. Accountability
7. Objects and Data Over Time
8. Systems
9. Permissions and Settings
10. Vision and Future Developments
11. Tech, Tools, and Maintenance
12. The Story
 
Click to view time photos.
AU 1160 Daily Tasks 4/11/2013   • Writing new concept idea and brainstorming on a concept buffet or tons of different concepts.
• On the phone with Steve. We used GoToMeeting and I helped him with some custom code and dashboards he is making for clients. His skills are improving and he is doing awesome.
• Phone calls, tech support, and sending some pages to Steve to help with permissions.
• On the phone with a client doing some training for getting inventory into the system. Editing invoices and applying payments.
• Tech support.
• Working on a list of core concepts inside of adilas. Lots of brainstorming and writing. Light brainstorming on using elements of time to help with my notebook and recording history and/or even family history.
 
Click to view time photos.
AU 1159 Daily Tasks 4/10/2013   • Prep for a meeting with my sister. We met and talked about “protecting ourselves by sharing!” Basically we had a meeting about what we need to do to get adilas concepts out to the public. We went in circles but ended up deciding that we need to teach and focus on concepts. If we help people learn and understand concepts the rest (processes, interface, etc.) will be much easier for them to get and understand. We also talked about different ways to show and tell about these concepts. We came up with histories and stories about concepts or animated timelines to show how things developed. One focuses on the concepts and how they came to be and the other focuses on general “see a need, fill a need” process that has happened over time. Some awesome stuff. See later on for meeting notes.
• Went to Smithfield and went by the bank. Talked with a bank associate about some business banking stuff. Including ACH (auto clearing house) payments, SBA (small business administration) loans, and general banking stuff. He wants me to contact him next week. 10 miles.
• Brainstorming and talking with my wife about options and where we are headed. We went over a light business plan and my wife agreed to help me write the actual business plan. Great meeting and I think it helped her catch the vision of where we are going.
• Emails and tech support.
• On the phone with Steve talking about concepts, loans, and business plan stuff. We just need to get it out there.
• Bank stuff and brainstorming on concepts and ideas.
• Recording hours and notes from a meeting with my sister yesterday. Since that meeting my mind has been going nuts over concepts and players and how they interact.
• Brainstorming on the core concepts inside of adilas. Reading and writing down ideas.
• Steve called and had some questions about code stuff. We also talked about concepts. Steve said that adilas virtually catches everything we do physically. Basically, we either do it and then record it or we record it and then do it. We talked about the engine and who our users are. We also talked about fundamentals and doing them over and over again. Concepts about concepts.

• Tech support and emails.
• Recording notes.
 
Click to view time photos.
AU 2279 Brainstorming - Adilas Concepts 4/10/2013   What are the main concepts of adilas? This was just a small exercise… there are tons more…
o Players:
- Empowering the user
- Data
- Basic building blocks
- Permissions and settings
- Physical extension of actions into a virtual world
- Friends and buddies
- Functions and tools
- Characters
- Story
- Same thing over and over again
o Problems, Needs, and Goals:
- Next logical steps
- Development
- Data
- Change
- Functions
- Goals
- Pain
- Needs, trouble or problems
o Consequences and actions:
- Game of business
- Cause and effects
- Data
o Time:
- Objects and data over time
- Data
- Roll call
- Searching
- Change
- Underlying and kind of subtle
o Relationships:
- One-to-many
- Data
- Culture
- Fundamentals, do things over and over, stack and stack
- Mix and blend
- Friends and buddies
- Repetition
o Decisions and choices
- Game of business
- Cause and effect
- Data
o Accountability:
- Data
- Searching or searchable
- History
- Track everything
- Virtual recorder or video
- Capture real life actions in virtual reality
o Systems:
- Centralizing data
- The “whole”
- Systems thinking
- Data
- Scalability
- Engine
- Web-based
- How you use it & what you do – create what you look like
- Human body
- Server based
- Concept buffet
- Developer’s notebook and sharing
o Vision and future developments:
- Next logical step
- Data
- Dreaming
- Change
- Platform
- Concept and buffet
- Developer’s notebook and sharing
o Tools and Maintenance:
- Data
- Paper, spreadsheets, databases, software, IT and notebooks, servers, web applications, platforms and API’s
- Breaking models and tools
• This causes problems
- Searching
- Maintenance
o The Story:
- Going to the source
- History
- Data
- Data mapping
- Features, advantages, benefits
- Players, relationships, trouble, choices, consequences
- Time
- Data portal
- World building
- Virtual copy of real life
- Hand stitch or sew it together
o Functions:
- Data

Other Notes:
- Inputs & outputs – you get what you give
- Weakest link affects the whole
- Confidence
- It takes work
- Think logically – what happened in real life and how would I do that in a virtual world
- Flag & date
- If correct, let it flow
- Checkpoints
- Computers are dumb, powerful, but dumb, you have to tell it what to do
- Everybody uses the system differently
- World building and telling the story
- It may be over kill at times but it helps track the story, even if it gets complicated.
- You tell the story, we then help you map backwards to show where things were at.
- Push vs. pull – give automatically or ask for
- Concept buffet –tons of topics
- You find what you are looking for
- Different notes from talking with Steve about adilas, direction, and core concepts:
o What you do physically everyday…. We capture that is a virtual environment
o Whatever you do physically… you have to record it
o Physical extension of physical actions – physical to virtual
o Willing to try and love of learning
o Engine
o Features, advantages, and benefits
o Fundamentals, do over and over, stack and stack
- Pyramid Diagram #1 (starting at the top and moving to the base in this order)
o Permissions
o Settings
o Functions
o Types
o Friends
- Pyramid Diagram #2 (starting at the top and moving to the base in this order)
o Functions
o Types
o Settings
o Permissions
o Concepts
 
Click to view time photos.
AU 1184 Daily Ideas 4/9/2013   Recap of meeting with my sister to talk about training and direction: Developer’s notebook
-Protect ourselves by sharing!
-Concepts inside of adilas are 10x (times) greater than the code.
-Visually display the concepts (photos, animations, video, etc.)
- Provide the history and story
o Nested to details
- Brainstorming notes
- Developer’s notebook
- Actual ideas and working pieces
o (Sketch in notebook of brick wall – foundation piece being things like: time, permissions, settings; the next level: data, empower users, etc., etc.)
-Concept based learning
- Each concept needs a story
-Abundance Model – “enough to go around” – sharing
-Tie or connect through feelings or feeling a part of the story.
-“See a need, fill a need” (movie – Robots) – This is a “base”
- As a need is filled it creates a new something or something new
-What about an interactive timeline
-Concept Buffet
-Animated Timeline or story
-The movie “Up” – see entry from 1/5/13 to 1/8/13
-We’d like to show the development of these concepts in two ways. –By Concept –By Timeline
-Teach the “why”
-When recording data (actual pieces) we will need two or more pieces… what concept or subject (players) and what timeframe.
-Figure out the core concepts – we started out with about 20, then decided to go to 10, and then the list kept growing and growing. Kind of started going in circles. I took the assignment to come up with the master list of concepts and sub concepts.
-For the record, here are a few things we scribbled down:
- Centralizing data
- Going to the source
- Empowering the user
- Permissions and settings
- Objects and data over time
- One-to-many relationships
- “See a need, fill a need” – “base” or foundation
- Next logical step – development
- Systems thinking
- Games (rules, players, goals, challenges) game of business
- Data
- adilas – all data is live and searchable
- Dynamics
- Relationships
-Other core concepts that we were listing out:
- Education and sharing
- Types and functions (“why” or building blocks)
- Roll call – what is your story – return and report
- Record the story – the story may be more important than the numbers
- Scalability
- Custom
- Dreaming
- Players
- Culture, vocabulary, change
- Put things to rest “life cycle”
- Mix & blend (we mix concepts and players to create flow, processes, and interface)
- Catch the pieces
- Data mapping
- Peace of mind
- Point the picture – vision of the future
- Open entry, open exit (no contracts, pick & choose, only use certain pieces, etc.)
 
Click to view time photos.
AU 2278 Brainstorming - Developer's Notebook 4/9/2013   Meeting with my sister going over what we want to do with the developer’s notebook:
(Other sketches & diagrams can be found on the scan in the photo gallery)
- Protect ourselves by sharing!
- Concepts – 10x greater than the code
- Core concepts
- “Visual” or video concepts
o History & story
o Nested to details
o Brainstorming
- Driving a car... we learn concepts like right turns, left turns, parking, passing, etc. Then we can go anywhere… even to places that we don’t know or haven’t been.
- Concept based learning
o Each concept needs a story
- Feel the story
- Abundance model – “enough to go around”
- “See a need, fill a need.” – Robots movie.
o Creates something new
- “Base”
- Interactive timeline
- Concept buffet
- Animated timeline or story – The movie “Up” – see entry from 1/5/13
- Two different ways – by concept or by timeline
- Teach the why
- When recording data (actual pieces_ we will need two pieces… what concept or subject and what timeframe
- Figure out the core concepts – 20(ish) – (subs or subs of nesting)
- Let’s do 10 – everything is somewhat built on this kind of model – (plate & cups sketch: with the main (plate) and cups (line items, payments, system history, flex grid, other content, custom docs, photos, etc.)
o Centralizing data
o Going to the source
o Empowering the user
o Permissions and settings
o Objects and data over time
o One-to-many relationships
o See a need, fill a need – “base” foundation
o Next logical step – development
o Systems thinking
o Games
o Data
o Adilas – all dad is live and searchable
o Dynamics
o Relationships
o Education and sharing
o Types and function (why)
o Roll call
o Scalability
o Custom
o Dreaming
o What is your story – “record the story”
o Communication
o Players
o Culture, vocabulary & change
o Put things to rest “life cycle”
o Mix & blend
o Catch the pieces
o Data mapping
o Peace of mind
o Paint the picture – vision of the future
o Open entry, open exit (no contracts, pick & choose, only use certain pieces, etc.
- This is how we track and manage data…. We Mix Concepts & Players
- We are almost coming full circle instead of us dictating flow, processes, and interface – we want people to mix and blend concepts and players to make their own flow, processes, and interface