Meeting with Wayne and Alan to go over options for database configuration options (code words... datasource project or bus to motorcycle or world building project). Light catch-up. Wayne was going over options for running a base service to figure out the corp and datasource (what database to use). The old datasource is the default.

Talking about efficiency and combining corporations and servers. Going over scenarios. The idea is to make the code and the schema unaware (more open - able to connect to any database). For me, I have a bunch of older notes under clustering, solar systems, and galaxies (all kinds of cross-schema options).

For us, internally, database updates may get more crazy, especially for our developers. Talking about possible load balancing stuff. We were talking about master databases, sub databases, and efficiency questions.

- Wayne was recommending a more company related approach (which businesses are connected or have a relationship) vs corp related (single worlds, all by themselves). Widen it out a bit.

- Wayne's branch... WLA/DynamicDSN

- Alan was talking about a wish list to help update things from one spot (one page or one server) vs logging into each server to run it on each server (current process).

- Wayne already uses a script (test script) to run his database updates. He doesn't like to do things over and over again. He would rather build a script or make a tool to do that.

- Wayne wants Alan and I to help pitch it to Steve and Cory.

- We may need to look at and check the edge cases (on the datasource look-up project). They were talking about some known caching issues.

- Places that we need to check... (list of us, internally)
>> shop folder - there is some session stuff but it is different then the top_secret stuff.
>> web folder - API's - most pass in a corp key that we can figure out a corp id number from.
>> public folder - hardcoded per page or FORM or URL scoped controlled.
>> temp folder - hardcoded per page or FORM or URL scoped controlled.
>> database_updates folder - may need to query (get all known datasources), then loop and do updates per schema. basically, layer and nest things vs just plain doing a single update.
>> check the process to create a new corp - some questions there (we are currently using the main datasource and building tables and inputting values based on our create new corp routines).
>> caching - check the daos, services, and cfc's - make sure we do what we need to here to make this still function correctly.
>> search for corp_id IN (? whatever the list or arguments are) - multi corp queries. Maybe be able to set a temporary master/primary corp id where needed.

Working with Steve on logic for updating and adding parent attribute values in bulk. Steve is working on a few new pages that have some new bulk attribute tools. After that, we flipped over and had to do a small data update for a client on the data 10 server.

Eric joined the meeting and was asking questions about the item catalog and enterprise level systems. He and Alan are working on those pieces. Anyways, he was asking about logic and flow from the main enterprise system out to the transactional corporations. We talked about flow and then got into training and user experiences (UX/UI) and user interfaces. That lead to a discussion about education and even certification for certain aspects of the system. Another option for compliance and good data outcome is a form of oversight or mentoring for our clients. This would be an additional service.

If you keep following the path of the data and the needs. We can see things at the world level (low level), the solar system level (linked corporations or worlds), and on up the chain to the universe level (everybody who plays into the system both directly and indirectly). Eventually things will need to get clear out to the API socket level where anything could talk to anything else. There was even some talk about subscribing to other high level vendor product catalogs. Basically, a way to make the data entry and updates quick and easy.

For fun, we got into some space analogies with universe, clusters, solar systems, worlds, etc. Eric was also using some construction and cooking analogies. Lots of people understand things at that simpler level. Thinking big picture and then being able to pull it back down into the smaller details. Data is king! Having the foresight and vision to see what else if needed and wanted. That's a challenge at times. We were talking about business logic, flow, aggregates, and other data level needs. Our goal is to keep revamping things as we go. Both logic and look and feel. That's about all we can do.

Server meeting between Wayne, John, and I. Going over a number of different topics. We talked about special websites that branch off of the main root or master branch. Ideally, if they are needed, we'll put them under public from now on. We decided that we may make a retired code repo (code repository) for things that are no longer in use or that are old. That was Wayne's idea and I think that it is awesome. I tend to just leave things where they are and work around them. He is trying to streamline things and help to standardize where possible.

Wayne is making big steps on the conversion between Application.cfm and Application.cfc's (overarching application and security structure of the main application pieces). Things are going well and he is ready to push them up to the dev server for testing. That is awesome. That project is a prep step for bigger corp-wide settings projects and simplifying some of the settings. We have two tables that are really big, and both of them hold settings. We need to change the format so that we are prepped for more growth in those areas.

We spent some time talking about the cost of storing content and files off of the main data servers. That is one of the pieces that is holding us up from clustering servers. Anyways, we are looking in to it and starting to chip away at that project as well. The goal would be to get all of the content in one place (photos, images, content, media, files, temp uploads, etc.) That one place may be a variable (change it per corporation or per server box or per cluster) but a special spot where all of the extra files that are not part of the master code branch go. Currently, they are stored on the data boxes in special folders. They, other files, are stored on the content server. This little project came up because we are having to up the storage on the content server. Lots of companies are using it. Eventually, we may have multiple content servers and be able to dynamically assign them. Good stuff.

Some of the other topics for discussion were dealing with the datasource project (smaller databases per corp or per solar system - linked companies). Timezones on the servers and making them all the same. We also spent some time looking into possible cost savings by switching from Adobe ColdFusion to Lucee (free and open source cfml - still ColdFusion but a different engine). If we were to switch, it would save us thousands and thousands year over year. Worth checking out.

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.

Talking about some marketing and ideas. Danny, Sean, and I were on the meeting to begin with. We were talking about the use of the blue dog avatar and where we are trying to go, marketing wise. Lots of good and open conversations. We talked about a few different ideas and just kicked the ball around. John joined and we asked him a little bit about his experience and questions that he has been asked and/or had to explain. Good conversation.

After Sean and Danny left, John and I went over some stuff for the content server. I showed him some old graphics and drawings of our world building concepts and how we were going to structure data servers, content servers, databases, and corporations within those databases. Click here to see some of the other analogies and explanations for universe level, galaxies or galaxy level, clusters, solar systems, worlds, etc.

Server meeting with Wayne. John and Steve were on as well. Mostly we were talking about and making plans for the new website. Chuck, Danny, Marisa, and John have been working on the new site for a couple of months. Well, that is getting ready to launch and so Wayne and I are making plans on how to roll things out and get it fully deployed. As a fun side note, the new site is up in beta mode for some of our guys and gals to test and play around with. That is awesome.

Anyways, I pitched a plan and then we came up with a modified version of that plan. Brandon has some notes on his local computer about some of the plans.

Towards the end of the meeting, we switched gears and talked about the usage on the content server. Eventually, we would like the content server to hold all of the files, images, CSV files, PDF's, Word, Excel, and other media/content files. Currently, the system is setup to hold and store certain files locally (per box or per server) and then all of the bigger media/content pieces up on the content server. We would like to get all of the pieces in one general place. That would help with future projects on clustering servers and what not.

We also talked about breaking up and adding more content servers as needed. This gets into world building, universe level stuff, galaxies, clustering, solar systems, and stacking of servers and technology. See this help file for more info on world building.

Wayne is also pushing hard on some test driven design stuff. He is out pioneering some concepts that he wants us to use in our normal development processes. After that, Steve needed some help with some logic and wanted to get a number of sample files for uploading CSV files to the server. He has a new project that he is working on for a client.

Going over a big spreadsheet with Alan on the splitting up the database (world building) project. We went through things on his spreadsheet line by line and talked about scope, depth, and what each step would take. Some great conversations. We talked about testing, changing things, and cascading new changes. Some of our talks were going clear out to the universe, galaxy, cluster, and solar system levels. See attached for an older drawing of the universe levels.

Eventually we'll get things fully dialed in at those upper levels and we'll get back to world level (corporations) and location level (locations within a world) stuff. We also talked a lot about temporary steps for master corporations and sub corporations within their different solar systems (database stuff and who is connected to what).

Steve and I had a good session talking about options of creating a true solar system level system (using the world build and space analogy). We did some drawings, took a few notes, and looked at some older drawings and graphics. Here is a good reference for some older world building graphics - click here.

- Ice-down dates - We had a good conversation about this. What if we pull a general aggregate for revenue, cost of goods, expenses, assets, liabilities, and equity - then when they pull it, they can then push it. These aggregate totals would be on a per day per location and per category basis. At this point, when they pull these totals, we could allow them (the users) to lock things down on that day (the date could a date back in time, depending on when they pull the data). Basically, each day could virtually get a lock-down or ice-down date. If needed, they could unlock things and then lock them back down. Just ideas and we still need to figure out the particulars, but these were some more ideas from today.

- Parent/child >> in the solar system level - We have had a very good experience talking with people about parent/child relationships and how that plays into the mix dealing with inventory items and other stacked relationships. If you go far enough, eventually it gets out into grandparents, great grandparents, etc. Normal parent/child relationships exist all over the place.

- Solar system >> planets (transactional worlds) and the sun (enterprise or aggregate system). We were talking about what terminology works best for our solar system analogy. The solar system is made up of different worlds that are closely related and somehow interconnected either through the database or through a relationship (parent/child or brother/sister or something like that).

- In inventory, we have vendors & customers (high level), PO's & invoices (medium level), items (small level), parent/child items and relationships (smaller), mini conversions (even smaller or micro)... in the universe analogy we have solar systems, suns (controller world), planets (transactional worlds), locations, groups, individuals, data, etc. Almost everything goes from big to medium to small levels, depending on how things are grouped and/or shown.

- Top level mappings - corps, locations, vendors, part categories, expense types, deposit types, etc.

- Enterprise solutions >> who is your buddy and how is everything setup (structure)? We had some brief talks about how to set this up. For now, we will just hard code things and then introduce variables a little bit later on down the road. Eventually, there may be database records and even one-to-many relationships with what corp type (world style or world type setting), who are the players (buddy list), and which way does the data flow (up, down, bi-directional, etc.). More planning is needed.

See attached for some drawings

It must be Monday. We had a pretty busy morning meeting. Dustin checked in. Alan joined in and reported on some of his projects. He set up some times to meet with Steve. We also talked quite a bit about data tables and creating more aggregated data and pushing the transactional data deeper into the system. That will definitely be an upcoming project. It is gaining momentum and heat. Eric joined in and we chatted about special accounts, new rounds on customer loyalty points, implementing new rules, and other projects that he is interested in. Steve assigned him to two new projects from the community funded projects list.

In between the different reports and sub meetings, I did a code merge for Bryan, uploaded a new video, and recorded some expenses.

Steve and I got into a discussion about world building and enterprise system (consolidated data for multiple corps). We talked about world bulding levels such as: universe, galaxy, cluster, solar system, and clear down into worlds and/or corporations or entities. See attached for an older drawing of how those levels play together.

Steve and I also did a small code session on some of the recipe/build stuff that he is working on. We talked about putting in flow and validation pieces to help him get the desired records and data. Small analogy of building a road and putting in water bars and drains (engineering where you want things to go and flow). The last part of the session was spent going over the internal flow of the adilas API sockets and how those pieces work and flow. Steve is planning on starting in on that and using the internal API to gather and record daily sales data from aggregated or consolidated corporations (worlds). He is getting dangerous in his knowledge and willingness to learn and grow. Super exciting stuff.

Steve, Wayne, and I were talking about serves and direction. We were talking about getting things going with Newtek with the new VPS and clustering options. We are somewhat putting AWS stuff on hold. We have been over there for six plus months and still having some issues and running into small little barriers of sorts. We have had great success with Newtek and want to keep that ball moving forward.

One of the main topics of the day was the data 0 box. It is currently our oldest box and plays a pivotal role. It is somewhat of the gateway for the rest of the system. We are going to be trying to change that and get all of the normal companies that need production level capacity to other servers. Basically, we are going to be splitting up the corporations (worlds or business entities) on that server into a couple of new spots. It should help things go faster and lessen the load on the actual gateway that data 0 plays (as far as a redirect or doorway type application).

Here are some of our other notes. Lots of good chats and talks.

- Lewis and Clark expeditions and mapping things out and figuring out what to do and where to go next. This is part of our explorations that are needed in the digital realm.

- Splitting up databases in to different datasources (where are things pointed) and also the structure of the data. We talked about certain tables that are independent, certain tables that need to stay as shared or master data, and other tables that are for sure corp-specific or based on a per world level. Interesting conversation. Going back to the older world building ideas - cluster database vs solar system databases.

- Wayne was mentioning that he would like to work with Alan on splitting things up between the database and different datasources. That could be really cool. Wayne was also mentioning about using the DAO's (data access objects) and having that be part of splitting up the databases. As a side note, if we create new databases and datasources for each company, we would potentially be duplicating a lot of data. It may be faster, but we need to look at what that extra duplication would cost as far as connections, storage, and even eventual clean-up. In short, moving to the DAO model vs duplicating existing databases.

- We are really trying to move more towards the adilas community funded projects... similar to how the open source software and community operate and flow. If someone really wants something big, they need to make some resources available (time, money, ideas, people, etc.).

- We talked about selling the data storage and processing services. In a way, we could say, our system or software is free, you just pay for the services that you need to support that. Those could be setup, hosting, storage, processing, custom code, marketing, training, consulting, design, etc.

- We briefly talked about owning our own hardware cluster there at Newtek. It was on Steve's list to talk about. Wayne chimed in and recommended that we not go in that direction. He explained that if we stay on Newtek's hardware clusters, they have a reason to keep upgrading and maintaining those clusters. If we ride on top of what they are doing (their products and services) we gain from all of their advancements. If we are on our own, we have to provide all of those upgrades and maintenance pieces. Great point and something to think about. Ideally, if we gain enough, we would be better off riding on top of these other products and services.

- We spent some time talking about the refresh rate and the replacement rage of hardware and who manages that.

- Stress testing on the servers - Finding server level breakpoints and stress and load testing on servers. We pointed Wayne to a number of bigger reports and processes. He will simulate those loads on some test data to see if we can find any stress points, breakpoints, and other info we can gain by load testing things. Wayne would like to work with some of the reps and consultants to find the pain points and going the daily grid and what works and what needs some more loving.

Eric popped in and asked some questions about transitional invoices and how all of that works. We ended up talking about putting those requests into our community funded project list. Steve and I want to help to funnel the users and their requests into our project management options. Steve and I are going to be trying to focus on core vs custom and trying to figure out how maybe the custom could be core with settings (how to make it happen and/or play through).

3D calendar and time management. We are seeing people wanting to get into smaller and smaller time periods just as hours, minutes, seconds. Most of our stuff is currently on the day or single day type environment. 3D calendars deal with years, quarters, months, weeks, days, hours, minutes, and seconds. Our users may even want to determine what their unit of measure (date specific) is... that way they could choose what level they want to play on (days, hours, minutes, etc.).

https://data0.adilas.biz/top_secret/help.cfm?id=479&pwd=core - help file for world building and showing the layering options

https://www.adilascontent.biz/top_secret/images/corp748_EA81FBBDE6/pdf/doc_26325_9F86EF2854.jpg - small drawing on how the upper levels of world building may be configured and such.

Steve and I are seeing our way through the multiple databases per server type option. Those are technically the cluster and solar system levels in the world building pieces.

After Steve and I got done speaking, I jumped back on the special accounts project (rewards, customer loyalty points, gift cards, etc.).

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

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

• Planning and prepping files and projects for the new developer. Started to implement a light version or version-ing system. Added light documentation for versions 1-9. See element of time # 873 in adilas and #2777 in the adilas university site.
• Burning copies of files for the new developer. Talking with him to let him know where we are headed and what his current project will be.
• Helping the new developer get set up with a new and updated copy of adilas files. We ran updates, installed databases, and got him lined out on his new project. He will be working on building the new solar systems.
• Working on pagination (next n) stuff for migrating data between servers. Helping the new developer out with code questions and light ColdFusion training.
• Working on new code to transfer zip codes. This was the first, bigger table that needed a multi-step process to make the migration go smoothly. Working with pagination to keep the user in a loop or process until they were done with the migration task at hand. This was a lot of prep work for other tables like invoice, parts, customers, expense/receipts, etc. Fairly simple process to migrate thousands of records at a time.
• Working on the create new solar system page. Breaking up the process into bite sized chunks of data. Working on the tables with letters A to B.
• Finished up the create tables and dummy record inserts for the solar system tables letters A to B.
• Starting on solar system tables for letter C.

• At the table planning out new login procedures, new database tables, flow, and requirements. Good session. Got a few new pages of notes. We are going to use cluster payee id's, home planets for users.
• Emails and tech support stuff. Light brainstorming on using the parts reference field to help with sub grouping and classifications. See further notes for details.
• On the phone with Steve going over new and upcoming projects. We also talked about using project managers to help with bigger projects. The other main subject was developers and how to help them develop from API's or internal, using templates and skins. We are getting more and more people who want to ride on our platform and charge for custom code that fits on top of or inside the normal adilas system.
• Helping an intern with his icon menus and some light code stuff. Sitting at the table doing some planning. Spent quite a bit of time documenting the inter-workings of the system. I know that all of that documentation could be used against us (showing the whole map) but we gain tons from it. I think it is exciting to see all of the pieces come together. Yee haw! Here we go!
• Writing code for new cluster tables. Trying to prep things for clusters and multiple solar systems (new database levels).
• An intern came over and we worked on his customer migration project. Lots of training on the fly and trying to help him understand what is going on. He is doing a good job.
• Documenting adilas database tables and field names. Working in Microsoft word going table by table.

• Emails and posting new default invoice views as corp-wide settings. There are six different views to choose from as the default when a shopping cart is converted to an invoice. The new ones are: 3” format – no line descriptions, 3” format – summary, and 8 ½ x 11 summary.
• Prepping files for an intern for more icon menus. Working on parts and general inventory pages.
• Creating icons for parts and general inventory pages and new buttons and icon menus.
• Emails and tech support stuff.
• New logos for clients.
• Research and tracing the existing login procedure. Tying to get insight as to how the new cluster and solar system login procedure will happen and take place. We need to make some changes due to the new and upcoming database structure.

• Back working on the database copy and deep database surgery. This is also known as the solar system level. This project was started in mid August of this year. Spent the morning checking different computers for files and progress on the database copy. Reread all of my notes in this notebook from 8/12/14 to 9/12/14. Lots of crazy things happening. The notebook review really helped me remember what is going on and where we are headed.
• Touching pages that are part of the big database copy project. Light work on the in-line discount code. Trying to make sure existing code will work going forward.
• Emails and tech support stuff.
• On the phone with a consultant talking about tax settings and mini invoice options and settings. See notes below. Small code changes for him and his client.
• Small tweak to the mini invoice and corp-wide settings to only show the mini invoice with the items and not the descriptions.
• The guy helping with marketing and project management came over to meet with me about marketing ideas and how to get more developers online and in the trenches. Great meeting! Lots of vision and concepts. I showed him some pieces of the new teacher/student interface and we talked some potential.
• An intern came over and we worked on a customer upload from a digital file. Light database work and combing an Excel file.
• Working on database design and layout at the upper cluster (box or domain) level. Making some decisions about cluster corporations and cluster payee/users. Those two are kind of the crux tables.

• Emails and recording notes from post-it notes.
• Checking out digital files for a client that wants us to upload their data. Wrote an email back to the rep with quotes, prices, and questions.
• On the phone with Steve giving him an update as to where we are at with the database surgery,copy, and duplication process. We also talked about other projects, timing, and direction. Good stuff.
• My sister came over and we did a multi-hour session on defining the database tables. We went table by table and wrote a small blurb or paragraph for each table. What does it do, how is it connected, and what are its uses. Anyway, a great session.
• Writing an update email on the database split and copy project. Asked for another two weeks to get it done. It may even be longer than that. I compared the existing adilas shared environment to a bus. Virtually, adilas has been selling seats on this bus. With the new database and solar system changes adilas will be able to sell individual vehicles and/or motorcycles to our clients. They will have an independent instance or mini adilas engine to run and operate on. That is exciting. Good stuff!

• Emails and tech support. More API socket connection requests
• Going through table by table and checking code for populating the new database structures for both clusters (level 3) and solar systems (level 4). Went through all of the A tables and started in the B's. Finished up the B tables and started into the C's.
• Our client, the school teacher, came over to talk about the adilas teacher/student interface. She needs a behavior tracking system. We will use elements of time and a custom wrapper on it. We talked about options and I made some sketches about what she is looking for.
• More work on the “C” tables. Getting things ready for doing database copies.

• New logos for a client.
• On the phone with a client. We went over tons of different scenarios on the balance sheet. Including distributions, loans, paid in capital, outside funding, etc Good little session.
• Small changes to a client contract. Added new credit hours and posted the changes online. No charge.
• More logo work for a client. Emails and follow-up.
• Jumping back into the full database copy and scripting all of the tables out. Started on the populate process. This pulls data from a master database and pushes new records to a new solar system. Both my sister and my wife were prepping files.
• Reviewing brainstorming notes for the full database copy project. Lots of loose pages with notes clear back from December of 2013 about different levels and pieces that are needed. Good review. A developer was over tonight helping with copying and posting code. Good stuff.

• Working with both my wife and sister on database updates and SQL update statements. More prep work for doing full database copies. Also working on adding database indexes to all sort orders and field status values. This will help when doing database queries.
• Working on database code for new clusters. A cluster is a box, server, or domain level structure. It goes:
  -Level 1 – Universe,
  -Level 2 – Galaxies (linked servers),
  -Level 3 – Clusters (individual servers, boxes, or domains),
  -Level 4 – Solar Systems (databases inside of a cluster or box),
  -Level 5 – Individual Worlds (corporations inside of a database or solar system). The levels go all the way to 10 but we only needed the top 5 for this entry.
• On the phone with Steve going over things. We talked about options for dynamic css (cascading style sheets), 3rd party skins, and interface pieces. We also talked about upcoming projects, progress on the database project, and the use of API socket connections in the near future. We are seeing a large shift towards full API requests and access to backend data pieces.
• Planning, paying bills, and recording notes.
• Making decisions on where to put certain tables that play both at the cluster level and at the solar system level. Did some research on existing table structure and layout. Checking for dependencies between tables for certain joins on tables.

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.

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.

• Moving prepped table creation statements into live code to help create new mini adilas databases. We are calling this, level 4 or creating a new solar system.
• Moving pieces, clean-up, prep, and planning next phases.
• Tech support calls on complicated pricing matrix and mix-n-match selling to get to a standard price. We talked my cart favorites, advanced grids, and then recipe/builds
• More work on the new databases.
• On the phone with Steve talking about pros and cons to the system charges we are making. This is a huge step for us in going to the next level. Some of the benefits are speed, mobility, options, balancing, storage, and even deleting and removing waste. That is awesome.
• New logo for a client out of Salida, CO.

• Prepping more SQL and database files. Finished some of the prep and started into detailed table creation. Going line by line checking defaults, indexes, and formatting. Fine tooth combing.
• Adding fully scripted tables to the create new solar system (level 4 database structure) method.

• Working on a digital file conversion and update. We got a digital text file with barcodes and quantities. We had to load the text file, group it, do the math, look-up products and barcodes, check quantities, and update the system if there was a problem, etc. Got the update pushed to a live server and emailed all parties involved.
• Posting a news and update page with the highlight on the expanded chooser page (choose your custom interface).
• On the phone with Steve doing a quick update and touching base on current projects.
• Prepping SQL (database) stuff for the full solar system copy.
• Got a call from a client. I ran the inventory update for them this morning. Well, they forgot to tell me that it happened a couple days ago, so the update that I did had the wrong numbers. Anyway, we voided out the old update and ran it again with some different dates. Hopefully that fixed everything and corrected the inventory according to a date in the past. Kind of crazy...
• Emails and updates.
• Prepping files for copying the database. I had both my wife and sister working on different copy and paste formatting projects.
• Emails and light tech support.
• Prepping more database files.

• A developer came over to help me with a database migration project. We chatted and did some catch-up on things. I started prepping files and step-by-step plans for the database copy procedure. The developer started on the create new solar system (aka database) page and I started going through each table and defining what we need to copy and what will be added by the system.
• More work on database tables. Going through things table by table. Lots of memories back to past projects. Manual work but kind of fun.

• Emails and updates.
• Updating some help files. Recorded some notes on the help file for the adilas GPS core layout (help id = 479). This includes the list of all 10 levels in the world building concepts. See elements of time id #1914, 1905, & 1969 for other entries on these 10 world building levels. These id numbers are in the adilas university site. I also added some graphics to element of time #2773 for a small visual history of graphics and concepts for the adilas Dream it Up – your data, your world, your way slogan.
• Small tech support fix on a partially voided PO. Part was voided but two line items still had values. Not sure why that happened unless it was multiple users and/or multiple windows being used at the same time.
• Recording notes about doing full database copies. Basically cloning solar systems and inter galactic moving and copying.
• Working on the in-line discount project. It sounds like a discount thing, and it is. However, the real problem behind the scenes is sales tax and keeping things straight that way. Spent quite a bit of time at the table planning out what is needed. Pages of notes and calculations and database planning.
• Started coding new database tables for the in-line discount project.
• Worked on an update script for all existing tables for each corporation to include the in-line discount fields.

• Reading emails and planning out my day. Just got a request to do a full database copy for a client. That will be a huge project.
• Prep, emails, and light code changes for PO's.
• On the phone with Steve going over direction for existing pieces and projects. We talked about some known holes, fixes and how to copy and duplicate the system. We decided that we would do a full and independent copy of the adilas database. This will be a step towards our universe and world building concepts that we are trying to do. As a recap we have level one – universe level, level two – galaxies (linked servers), level three – clusters (independent servers or boxes), and level four – solar systems (databases within a single box or server). This will be our first attempt at the solar system level. That is exciting. For more details on the world building concepts, see clear back in late 2013. Lots of work done on this part of planning back in December of 2013. See entries on 12/20/13 for the first mention of the solar system level. Prior to that it was just called the database level.
• Planning, prep, and research back in my notebooks. It was fun going back to see entries from late last year on world building concepts. This is the next step.
• Creating an invoice and email for the full database copy.
• Emails and schedules for upcoming project and full database copy.
• Reworking the IFTA page that reads the CSV file in. Changed from a load data in file command to a method that reads the file into memory and then loops over it line by line with validation and error handling. Canceled a tech support ticket, random phone calls, and emails. Kind of crazy.
• Working on a simple API connection between adilas and an ATM type of kiosk called Cash 4 Ever.
• On a conference call between Cash 4 Ever developers and myself. They wanted a demo on the eCommerce section and how we could integrate between the two systems. I showed them a simple interface, the shopping cart, eCommerce, mini receipt stuff, quotes, and restore to cart features.
• Phone calls, emails, and paying bills.
• Prep work for the developer for the Armored car stuff – banks, customers, deposits, and flex grid stuff.
• On the phone with the Colorado developer going over IFTA stuff and also an intro to flex grid to help him set things up for the Armored Car Playsite.