11.5 - Adilas Theory on Accounting

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

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

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

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

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

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

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

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

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

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

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