|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Yellow
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Notes:
|
|
Main list of tools is on element of time # 4029 inside the adilas university site. Web link - time_web_gallery.cfm?corp=371&id=4029 1. Head and mind This is the entry for the level 9 or full world building level... 9. World Building (digital story telling – ultra custom/hybrid level) a. Background: World building is a term that is often used when people create movies, plays, or write books or novels. What these artists or authors do is they try to create a world where you have characters that have relationships, and they make decisions which create consequences, which brings up some sort of a need to overcome something. As these characters interact these consequences become the building blocks of what happens next and it all becomes aimed or focused on fixing some sort of trouble or problem. What we do in a computer system analogy is we allow for those same pieces to be setup and created and for different actions to occur and things are allowed to be reported to other places and so on. It literally becomes digital storytelling. Some people think that they don't want to hear the whole story but they just want the raw, underlying numbers. However if you capture the story as it unfolds over time it becomes such a rich environment to produce greater information. If you are recording your numbers in this manner over time you can see they are carrying with them the why, the when, the how, the who, the what, and other pieces of information and data that build a rich and desirable picture. Capture and record the story. So in essence, just like an artist or author, you are building your world and creating a story. b. Features, Advantages, Benefits: What if you could mix and blend all the other tools into one platform or system. The concept of world building is open to all parties and peoples. As a disclaimer some of the pieces that we add going forward might feel like they are pointed toward Adilas. We are doing that on purpose but please know that we don't have a monopoly and we are not the only ones that participate in world building. But hopefully this can help to present the ideas and things that we have seen as we have encountered problems and needs in growing our own system or world. c. This link is to a document called the Adilas Formula. This is basically a mix of business functions, business players, and concepts that are able to be mixed and blended together to virtually create a world. https://data0.adilas.biz/adilas_formula.pdf d. It is very common for computer systems to have lots of fun acronyms. World building starts combining all of these. For example: Sales, Inventory Tracking CRM (Customer Relationship Management) CMS (Content Management System) Online Expense Tracking Payroll & Timecards Calendar & Scheduling Create Data Relationships Between System Players Backend Office & Accounting Functions Histories & Reports, BI (Business Intelligence) Web Presence & eCommerce Virtual Data Portal (Big Data) Etc. e. Imagine if you were able to create a system where you empower users at the point where things happen, through permissions, and then allow things to track themselves over time in a virtual data assembly line format. f. If you get clear into world building eventually you are going to need to get pretty deep. We see at least a 3D level where you have an x axis, a y axis, and a z axis which allow you to expand in all the different directions. We would make a proposal to keep things simple that x = time (bottom or horizontal axis), y = money or resources (vertical, up & down axis), and z = depth (where you track what we would call space or layering). g. The peace of mind to have everything in one place is amazing! If you have everything centralized, permissioned out, backup options, and secured, it truly can help you rest easier. You are set, you can play that game. And then imagine being able to customize it on top of that! Literally, dream it up! h. Limitations - Some of these limitations are more challenges than limitations but they are absolutely real. -Consolidated data - You have two different sections of data, you have transactional data and aggregated data or summed up/prefigured totals. Consolidated data allows you to go incredibly fast with math and calculations already done. The challenge there is to make sure that you caught everything contributing to that even though things are changing and moving. -Cross corp transactions - Cross corp means world switching. For example Company A sells something to Company B and it would automatically be inserted into the new system. Or Company A does a transaction and it needs to be recorded on Company B's financials. -Dark side, too much info or temptation - This might sound scary but technically if you get so much information, the entire story, it can become a more juicy target. Or there can be a temptation to use that information in ways that it should not be used. -Bigger volume requests - Say you are trying to merge or sync 50,000 customers in a single attempt. That is a lot of data. Or say you are trying to pull reports for 500,000 invoices at one time. How big of a bite or chunk are you taking at one time? -Complex one to many relationships - What if you have four to six levels deep in one to many relationships. If you think that sounds silly let me tell you a little about sub inventory. You have vendors that are connected to items, items are connected to part categories, part categories are connected to sub attributes, sub or child inventory are connected to parent inventory items, and mini conversions are connected to sub inventory or child packages. Did we forget to mention that all of this is location specific. -Pioneering and exploring - Where we are headed there are basically just dreams and ideas, no real road maps exist. It is very common to go down a path only to find out that, that may not be the best path but you don't know that right off the bat. There is a constant need that keeps feeding in and forcing things to keep moving forward but we can't see the end yet. -Things keep going, no stopping - These are often either client demands and/or advances in trend or technology. Once you can do something a certain way usually people want to do it faster, in bulk, less steps, more automated, etc. -Changes in technology - We live in a modern world where things tend to have a one to two year lifespan. Depending on what we are building on some of that stuff changes. For example there was a product called Adobe Flash that used to be the hottest item on the internet but currently all Apple IOS devices do not allow Flash at all. Languages change, protocols change, storage and capacity changes, software versions, hardware options, integration solutions. This might sound kind of silly but we talk about a fracture model how we are building on a changing, fracturing, unstable ground. That is where we live and where we are building. You have to be able to adapt to that. i. Here are some other topics that might be interesting to explore. - Data Fusion - mixing data from multiple sources. - Big data - how much data, where does it come from, how did we get it, how do we analyze it, what trends are we seeing? etc. - Digital currency - like bit coin and other digital currencies - Trends - watching for, discovering, and anticipating trends - Security and privacy - huge topics that have different levels from head to paper to computers to web to bigger... - Independent systems - there are certain things that we don't want to interconnect and/or limit access to. That is an important topic (limiting access and/or limiting outside connections). - Auditability or history or audit trail information - how easy/hard is it to follow the audit trail? This is way deeper than just a one-liner. What was the lifecycle, steps, states, and phases of x (fill in the blank). - AI (artificial intelligence) - What level of AI are we talking about? Simple if statements, cases, switches, states, or fuzzy logic with decision making power. How does this play in and how will it affect things in the future? Small side note, some of this was being talked about back in 2013 (creating this document). It is now 2026 and AI is a huge game changer. - Integration to other platforms - Once something is on the web, do we allow for integration, do we pick strategic integrations, or leave it open for any possible 3rd party integrations? That starts getting into strategy and even ethics. - If you do allow integrations, what about syncing data (making sure that data on side A and side B are the same) and figuring out rules of master/servant type relationships between syncing parties. What about integrity of the data sync or data syncing process. - What do the clients want? If we are avoiding things on purpose, does that get us in trouble? A simple survey of our customers may help shed some light on those topics. What are they wanting, expecting, demanding, and/or wishing for? - Real-time transactions and flow of funds - batching (time delayed - per month, week, day, etc.), I owe you accounts (who owes who and when will it get paid), real-time transactions, real-time payments, allowing vendors, banks, and government agencies real-time access and real-time payments for products and services. Along those lines, who negotiates those terms and deals? This sounds like more permissions and settings on a per corp (per world) type level. - Systems vs standalone applications - sometimes you can gain great advantages by using a system vs a single standalone tool. Having said that, sometimes as you add more players and pieces, there is a virtual drag (resistance and/or friction) that may go along with that. If it works, sweet. If not, you have been creating an anchor of sorts (a drag or something that slows you down). - Other potential issues - general - What are some potential warning signs that we put up... company pride, individual pride, not listening, avoiding certain topics and/or features, seeing and acknowledging hidden threats, on purpose staying a certain size (not reaching our potential), working on a private agenda, and other possible warning signs. - As an additional note, toward the end of a hike (we were actually driving home from our hike), a buddy and I were talking about integrations with other existing software companies and their platforms. The main topic was the accounting giant "QuickBooks" (and other like products) and why we are not trying to integrate with their product(s). It got pretty deep, but my hiking buddy was concerned that we might be missing out by not integrating with QuickBooks and others. I know that some of our clients would like that, but we have on purpose delayed and kicked that can down the road multiple times. Some of it is pride, some is money and cost of doing so, and some deals with challenging tradition. Other reasons deal with being true to what we are learning and exploring (what if we can do it this way or that way vs just following the crowd - love of exploring). - Some other topics along this same line are things like game changers, disruptive influence, progression, and expectations. What we have seen is that sometimes, tradition may be your biggest competitor. If you are interested in world building, here are some graphics that you might enjoy checking out: This link goes to a map, or an overview, of how we implement some of the principles of World Building in the Adilas system. Web link - adilas_system_overview_map.pdf. Or for a zoomed in map click here. Web link - images/help/big_map_layout.gif This is a link that shows a graphical core shot of a world. Imagine actually building a world, what would a core shot look like? What departments and pieces would contribute to your world? Web link - images/help/adilas_gps_layout_big.jpg A four step process to world building. Web link - images/help/adilas_dream_it_up.jpg This is the concept of 3D world building with an explanation of the X, Y, and Z axis. Web link - help.cfm?id=483&pwd=building More explanations on expounding this formula - Results = Mix(Functions, Players, Core Concepts). Web link - help.cfm?id=487&pwd=formula |