Adilas.biz Developer's Notebook Homepage

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 - (171)
Showing 150 of 171 Page 1 of 2 :: Go to page ::
Photos	Time Id	Color	Title/Caption	Start Date	Notes
	AU 2651		Daily Tasks	10/27/2008	• Checking page code. • Added a new printable report for payments being made. • Went in to meet with Steve for lunch. Talked about updates and where we are going. Also talked about issues and legal stuff. Went over notes from meeting with the attorney. We also talked about an associate and how to best use him on set-ups. 10 miles. • On the phone with my dad going over ideas for his place of work. • Checked out Google docs.

	AU 1529		Daily Tasks	10/30/2009	• Looking over a project that my dad sent to me. • Working on the add/edit process for merchant account settings. • Signing off on new pages. • Started to build interface on cart checkout and payment page. • Working on the actual add secure payment form for collecting credit card data. • Lots of time working on Java Script for that page.

	AU 1569		Daily Tasks	12/9/2009	• Working on the cross-corp sales process. • Added new documentation on the customer side for the developers help page. • Finished up the documentation for the adilas web services side. • On the phone with client’s associate about theirs and adilas’ website design. Swapped some ideas and just talked. Neither of us knew the agenda. We just knew that we were supposed to talk at our client’s request. Kind of funny. I wrote a quick update email back to our client. • One thing that I did learn was I need to get some help if I want to grow. By myself I can only tackle one or two projects at a time. With a small team, I can take on 10 to 20 projects at a time. • More work on the cross-corp sales permission. • Also talked on the phone with Steve about game plan and options. • On the phone with my dad going over site options and trying to get new clients for adilas. We talked a lot about remote demos and using products like Citrix, DimDim, Go to meeting, and other online web meetings.

	AU 2166		Brainstorming Automating Sales Tax, Collected Fees & Other B.S. Items	10/6/2010	Automating Sales Tax and Collected Fees & Other B.S. Items: Questions and concerns: 1. How do I name the output on the balance sheet? How do people want to see it? - Taxes? i. State, county, city, 5 dynamic, out of area, could be 0, 1, 2+ (or infinity) - Collected items? i. Could be 0, 1, 5+ (five is a random # but it could be infinity) 2. With only one location, the scenario above is workable. What would happen if you had 10, 20, 100+ locations? 3. Because it is so dynamic (0 to 100+ it seems to me that we need a 1-many on a per corp or per location level. Just an idea, we may want to start one by default that is only half setup so that is automatically tracks sales tax. On all of the drill-downs, put notes how to complete the process… 4. At one point we were talking about a hybrid balance sheet item…. How might this play in to the mix? I know that I need some sort of item to link up everything on taxes and collected items. What other pieces of the puzzle need help? 5. What if we made some modifications to all existing user-maintained balance sheet items and allowed for them to be hooked-up just like we need for taxed and collected. Hooked-up might mean… where or what are my incoming values, where or what are my outgoing values, and do I need any extra entries (general pointers, declarations, hybrid pieces, special bridges, pads, gaps, extensions, connections, hand holding, filling, extra entries, etc.)? This hook-up would not be required for the items to function. 6. So, what this could mean is that a user-maintained balance sheet item could be a standalone item (no watchers or no extra helpers) and it could functions “as is” right now. This is fully user-maintained and a manual process. However, if you add 1 or more watchers (and/or helper, feeders, participants, extra players) it could become some sort of hybrid. This might help with a known gap between B.S. expense types and B.S. deposit types. This could be cool because some B.S. items only need to watch one thing (an in or out). However an item could be setup to watch for ins, outs, and extra declarations or standalone entries. 7. As long as I’m brainstorming… what about a thing we wanted to call “special callouts” or “accrual callouts”. These are system-maintained items that need to be able to standalone. Say a special A/P for a certain vendor or a certain A/R for a specific customer that you do a lot of business with. These are basically handled just like the other A/R’s (invoice & payments) and other A/P’s (PO’s & payments or e/r’s & payments) but they are not lumped into the group as a whole. Basically, we set a watcher, as alias name, and a grouping for either a vendor or customer. The system runs all the logic and math but the end result is a standalone callout or hybrid system-maintained B.S. item. 8. This might also be a great time to set up a 1-many from vendor to expense type (defaults per vendor). 9. If we do allow hybrid user-maintained and hybrid system-maintained items, what would we call them or is “hybrid” a good word? Maybe two corp-wide settings? 10. A hybrid system-maintained item would be a special callout and would require a name, grouping, and either a vendor id or customer id. If a vendor was chosen, it might need checkboxes for e/r’s and po’s (or select both at the same time). 11. A hybrid user-maintained item would need a host (main) user-maintained balance sheet item. Which has the name, grouping, and math instructions. It also has options to hold subs. It then could have a B.S. deposit type watcher, a B.S. expense type watcher, multi B.S. deposit or expense type watchers (1-many if needed), standalone declarations, or known system feeds or feeders. 12. Just as an idea… a “standalone declaration” would be a generic non-specific item that could cross boundaries and be pointed to I.S. revenue, I.S. cost of goods sold, I.S. expenses, B.S. assets, B.S. liabilities, and B.S. equity. This could definitely get abused and has no backing. The name standalone declarations. On purpose, I may want to make it standout like a sore thumb so that it doesn’t get out of hand. There are reasons for it but it should be the exception not the rule. This is the item that can make the dreaded word “adjustments”. 13. A “system feed” is a certain section, part #, or known area of the system. The reason it would be called a system feed is because no manual entries are made but they are looked up (hence dynamic) from another known part of the system. A good example is sales tax, we know where it lives and should be recorded as a sum per day instead of individual details. The cool thing is one more drill-down and you could be at the detail level. Another good example is part # “collected”. It is assigned on an invoice line item and may need to be further categorized or filtered by description. 14. Histories on the standalone declarations will be very important. They will have their own homepage that can be accessed directly and from the P&L homepage and the balance sheet homepage. 15. After talking to Steve about this idea of standalone declarations, he thought that it might be a good idea to have a tool to link declarations together. For example: say that you are moving something from one account to another, you may want both actions to be linked together. This is not required but may be handy. 16. Before we go automating everything… what about documenting or mapping all system-maintained items out on paper. It might be good to take a small side step and map all of the know flow and what flags are needed to speed up the process. This could also help identify additional holes. 17. If we create a map, maybe we should go back to the underlying logic (where the add/edit and view takes place) and help the system keep track of known issues, dates, date ranges (windows), etc. It would be so nice to be able to search flags and dates instead of the main items, then the line items, and then the payments (sub loops and sub payments). Some of the flags that would help are: (not a full list) - Start, end, pre-main, pending, post or after main, paid, voided, match, complete, verified, posted, reconciled, transition period, etc. - Think of all the options for each piece. What are the possible states and status, both required (solid line) and optional (dotted line)? B.S. and I.S. flags? Basic and advanced? 18. With the mapping, watchers, and flags. The goal is to provide a quick look-up method for where are things at? What else is needed? And are there any potential problems? This mapping helps with the “known issues” report. It will help us present the findings back in reports and/or visual roll call reports. The goal way down the line would be to know where everything is and who is playing, moving, waiting, and in what area? Think overall vision…. - This becomes the full item roll call and where it has been, is, and where it is going… - Time becomes an issue that need to be shown and tracked. This is a constant and can be measured. Amounts and values are also constants. - These graphics don’t really mean anything it is just a concept - (See scan in photo gallery for graphics) 19. A 2D graphic might be awesome for general reference but a 3D graphic might be really cool to show 1-many relationships, subs, look-ups, etc. Just an idea… Think of a 3D model of the adilas database. Even cooler might be what and how are things playing together. Real time cause and effect. See the data relationships be built before your eyes… (interactive model) Okay, this is way out there… back to reality! 20. This is another random idea… Because we are defining all of the system players and how they interact, it would be cool to give them a face and characters (personality). This could be used to teach and educate users about what they do and how they play as tools, entities and as standalone characters. Some of the players may need more than one character to fully show what and how they interact. 21. If we could get it interactive enough, we could help show the users every step of the way what they are doing and how it fits in to the whole picture. Step-by-step – cause and effect, “visual”. 22. When showing graphics do we want to use static images, image maps with links, i-frames (windows), pop-ups, or interactive flash content? Maybe two different versions, one that is friendly to people and one that is friendly to search engines. 23. How do I keep it engaging yet logically simple? This might be a tight balance. Maybe show it very simple at first and allow the user to get more in-depth or technical as needed. Another strategy is to show it simple and then build layer upon layer until you get the full scope. This building idea takes more effort but might help the users see how things fit together better. 24. Just an idea… I’m worried about filling all the gaps and holes. What if we leave some gaps and holes and just show the users where things are at. The game of golf purposely has traps, water, sand, and rough terrain. What about the game of accounting and business? Is the goal to make it smooth or show where things are at? Once again, it might be a balancing act. 25. If I’m tracking something… How do I show something in the middle that has an uncertain start or unknown starting time and/or value? The reason I ask this is, quite often, we are asked to pick-up right in the middle and show a valid finish (numbers and accounting). It is kind of like a river… tons of water has already gone past (both flood and trickle) but I need to track a certain set of drops from point “E” to point “F”. In order to do that, I need some way to show current players and their status. In a way, I either need the supporting details or I need a starting value that plays forward… How do you do that? Does that affect anything down the road? Is there a limit going back? Does a starting value or false floor cause problems in the future? 26. How deep do we want to go? Surface level, a couple layers deep, or the full meal deal down to the dotting of “i’s” and crossing of “t’s”? How do we help people go to the level that they want and/or are comfortable with? How do you present on this level? How do you take yourself out of the mix so that there are no bottle necks and things run efficiently? 27. When a presentation is made (of any kind) how do you let people know it exists? How do you show it in context? How do you categorize the level of the info and presentation? How do you link backwards and forwards in a logical flow? How do you make it simple so that anybody could follow the path? 28. How do you help people get an education? You can’t force it… Do you want to show prerequisites or building blocks? What about requirements before and after? What about an indicator “you are here”? Lots of variables. 29. What is the timeline for a roll out like this? Or do we just start and slowly build as needed? Basically, don’t put any sort of time line on the project and just start it with the idea it will have future growth… 30. So, instead of worrying about timelines and deadlines… Do all that you can now because it will all be needed later on. Map it out, tell the story, and help people follow the path! 31. Make running a business and accounting fun… make is a puzzle… make it a game… make it as easy as possible without losing the need to pay attention or think… 32. As I was starting to map things out (visual flow chart), I thought that we may need a couple different maps… One might have all possible bridges or connections… another one might only show the current transaction and what pieces it plays with. Maybe we could even show a sample transaction and how it plays in. Maybe show the 10 or 20 most common transactions and what happens. 33. What about the element of time? This is a constant and part of the puzzle. A big part of the puzzle… 34. What about a hybrid graphic to help map actions. 2D – who are the players… plus a 2nd or 3rd 2D graphic as to the timeline and or physical relationships… Put them together to show the interactions. (Sketches in photo gallery, page 6) 35. How can I make the application map itself? Every possible roll call situation would need to be documented, scripted, and mapped. If the application could look at what happened (relative connections) it could display a real time map or visual flow chart. 36. If we are talking about smart object and/or transactions. We could also talk about smart reports, known issues, and full on automation of data flow. Along with automation… we will need to provide ways to back things out or correct known issues. Make the charges, record the history, and show a new flow chart or diagram. 37. Some modern software programs have a dashboard or graphical reports about key features. We could either use that feature or provide some sort of virtual drivers chair or cock-out (control seat) with all system controls and reports. 38. Wouldn’t it be cool if you could build virtual pieces or items (potentially 3D objects with relationships) and then drag and drop or physically put the pieces where they go? Basically, all of the tools we have created already would be used to put and build relationships (behind the scenes). The new piece would be on the user-side and would be a virtual environment where you can do your work and put things where you want them (interactive console or work environment)… This is sci-fi theory…! 39. On a different note, there is a known gap or hole if using special line items on incoming PO’s. Three possible solutions exist (right now)… One, we map the special line items to expenses or cost of goods straight from the PO’s and then pay for the entire PO through a B.S. inventory account. Two, we allow for some smart logic when paying for PO’s and help users split the specials off at that point. There are problems with both options as they exist right now. In scenario one, the full value must be deducted at once and it might seem weird to map backwards to the incoming special line items... (Not sure?) It might be better to use expense types). The second option also has a problem because it requires you to eat the whole cost at once and only shows up for roll call when you pay for it. This could be months between when you get it and when you pay for it. The third option is to satisfy the incoming PO with a series of PO payments assigned to the correct accounts. This gets the items booked right away. The catch is that you don’t pay the expense/receipt and turn the PO payable into a split payable (on account) for the vendor. The problem here is that you need to do double work and then have a split to pay off instead of a PO payable. 40. Once we get all of the mapping done. Why not use the map as a navigations tool (right from the homepage)? Show the history homepage report in a graphical manner. If people are stuck, show them what is needed, next, or possible options. Use the graphics to help lead them down the paths that will show them what is needed, or what we (the system) are waiting for. 41. Idea on making the map(s) dynamic. Allow corps to show/hide certain features like floorplan, stock/units, parts, rei’s, statements, rentals and reservations, etc. Maybe also allow them to move the pieces where they want. This could go even deeper if they have a rental fleet or layout of units. You could potentially stack, sort, categorize whatever it is that you have so that it matches your business. You could map your lot, your building layout, your warehouse, your restaurant, your clinic, your rooms, etc. 42. These are a couple of random ideas that I had in another notebook and have in another notebook and have a spiritual side to them. However, I still think they apply to adilas and where we are going… - Procedures (changeable) vs. Doctrine (unchangeable) - “Teach them correct principles and let them govern themselves.” –Joseph Smith - Teach people to think. They will take care of the rest… - Help the people catch the vision… This will drive them… - There is no new silver bullet. We need to use the tools and programs that already exist… - Bring it together… Everybody is playing on the same team! - A solid base supports the whole! 43. People want to see simple grouped reports. I (adilas) have a tendency to show details and expansive reports with every possible options and value. They have great data but they may not be what people are looking for. If I could say just a couple of words “simplify”, “cut to the chase”, “simple grouped with drill-downs to the details (if needed). Just show me the groups, categories, and the number totals. 44. Are we building and spending our time where we (Brandon & Steve - adilas) want or where our clients want? What do our clients want? What have they said? What have they not said but hinted or eluded to? What are we missing? - “If we help enough of them get what they want, we will be able to get what we want.” – Rough quote from President Leo Price (2/8/09) 45. Most of the comments on this page and other pages have been leaning towards a global watcher type system. This is not meant to deflate that idea but what if the flags and watchers and spread throughout the entire application with the tables that already exist (go to the source). The reason for this comment is I’m thinking about upkeep and system resources. The beauty of adilas is the depth and direct link to the underlying details. Maybe think about each main item carrying its own details like baggage. If I put the flags and dates in the right place we can easily pull reports and jump to the correct players. 46. Accounting is not so much the numbers… It is who and what are playing over time. We are dealing with independent objects and how they grow, shrink, live, die, play with, help, support, tie, bind, interact, skip, connect, and other actions. Let each object live and track what it does and make it accountable for its actions… wow, that’s deep! Almost spiritual… 47. Remember the whole picture… This is not just about the accounting. We need to remember that time plays into the operations and daily actions as well. One of the constants is time… Inside of adilas there is the effectual or what shows up for roll call. There is also the historical or who touched what. Both deal with the element of time. What about the financial side? 48. What if we beefed up the flex grid tie-ins… we use them as watchers, feeders, etc. We could set-up dynamic drop-down fields (for any of the 10 flex fields). We could beef up the search options and reports. We could also allow for the roll call or reflexive side of the flex grid to be used. 49. There is a known issue if people/users are using adilas as a cash register. On the one hand, we are recording invoice payments coming in; on the other hand, they (meaning the users) might be taking cash out for expenses (like a petty cash draw). If they (the users) are not going to the deposit and bank level it might be okay but there are some cause and effects that didn’t get recorded. How can you simply help people who want to do that kind of transaction? Here are some options: - They need to record a negative invoice that doesn’t count towards revenue (special line item with a black hole assignment). They also need to record the negative out flow or payment. When they do their deposits, they deposit the negative payments right with the positive payments and it works out okay. - What if they were able to tie to “cash” expense/receipt payments from the amount to deposit? Basically, create some sort of secondary line item that back tied itself to an expense receipt. That would be the negative side of the equation. - What if you had some way to tell the story of where they money went? Allow and create tools to tell the story so that we can account for them, not double things up, and keep the loop tight. That is a challenge! 50. On the global watchers – what if you called it locations, layers, and level. A super mini version of this already exists inside of adilas. It is the location ages and floorplan history for stock/units. Basically, we are looking for who, what, when, where, how much, and how long… 51. Good consulting and education may be better and more important than good programming! 52. What if any object or sub object could be pointed into play or told how to show up for roll call. What if that could be flexible on a per item or sub item basis. Basically, set a standard and default to that. If special, have the tools and permissions in place to let things play where ever you want in the final game or layout. 53. To take this “any object to any place” methodology even further… what if this becomes the watcher or watcher(s). This could be 1-many on dates and status. The roll call then knows where to show up and how and when to play in to the mix. Basically, a default roll call is either assigned or presumed. (Keep the footprint small or inline). Then if needed, only on special cases, allow for the 1-many to happen as “any object to any place”. At that level you’re playing with where and how things show up to play. Full control and full flexibility. Maybe only add a “custom mapping or roll call” if needed… otherwise let it flow naturally. 54. The system would need to track exactly what was happening and be able to show effectually and historically what was, is, and will be where and at what timeframe or in what window. Funny how it comes back to time… 55. Maybe time is the stable element and we organize events and objects inside of the time windows. 56. Space??? Time??? Time space??? That could make a pretty good 3D model. You could even push, pull, move, slide, and shuffle objects to create a sense of virtual time travel (past, present, future) with in the application. Only recorded data would be able to play. You can’t pull something out of nothing. Without getting too deep… the element of space is how you organize items and objects into logical pieces. Catch and hold all of the pieces and then be able to show them back again. This becomes the accounting or story of what happens in your space. 57. Old school accounts want to see the entries that were made. What if you show the database entries that were made and show them how to map back to it? This could be a nice presentation with graphics or just a pen and paper and physically showing where things go and how you can look them back up. Draw out tables, containers, etc. Show them on paper where things are at. Simplify some of the look-ups and keep it to a minimum (don’t be so detailed that it makes it hard to follow). Simple. 58. To make the above simple demonstration even more powerful. Once the entire transaction is mapped out on paper… take them in to adilas and show the same transactions using the system. Compare the map with how the system works. Maybe allow them to choose what they want to see. A decision or linked tutorial. 59. For the record, there are some other known holes and issues: (balance sheet related) - Credits (vendor and customer), payroll settings for all states, payroll reports, accrued payroll, year-end reports and forms, sales tax reports and forms, build and hold recipes, build and build recipes, conversion of a stock/unit into parts inventory, hard core manufacturing, process vs. discrete accounting, depreciation and amortization schedules, schedules and rentals, other items discussed in this brainstorming session (see previous notes and questions). - Some of these already have a work around but they could use either some help and/or documentation/training. 60. Jumping back to 58. It would be really cool if a tutorial had subs. The user could either view the entire thing, just a sub step or chapter, or be able to jump to what they want. Maybe have an outline for each tutorial, sequence, or presentation. If the user is in a hurry, allow them to look at the outline and jump to that section. On a technical note. That may require the player to have an active playing piece and a next up piece that is being downloaded. If the user jumps around, the player would need to shuffle the pieces. Just an idea… but maybe that map or outline could be its own clip or movie that could stay loaded until the user is done with that clip or section. It would also be cook if the player could be smart enough to show related topics and additional clips. 61. In the theory clips… show web basics, how 1-many works in a database, client/server relationships, dynamic searches and filters, history and approach, what are the technologies that are playing and what each does, show how relationships are created, how things interconnect, and what things standalone. In a way, pretend that you were teaching someone new how to build a web based relational database application. I know it sounds like you are giving away the farm but I really feel strongly about helping other people learn and understand what is going on. Think about Steve and I and how we communicated, because we can talk at that “full picture” level, we can keep dreaming and taking the next step. Conditional logic, new settings, 1-many relationships, short cuts, links, loops, where things are currently, where we would like to take it histories and how we can get there. 62. I want to make sure that adilasuniversity.biz is free and open to the public. We may be able to charge for other things like system fees, training, setup, migration, optimization, merchant processing, classes, demo accounts, retail store, upgrades to different service levels, marketing and ads (sponsors), white labeling, etc. Train the upcoming generation! Help them to learn adilas so that is what they want to work in… 63. Once we get everything working, it would be awesome to go back through and hide all irrelevant items or choices. For example hide the bank if only one bank, hide the location if only one location, hide stock # stuff if no stock/unit assignments are made. Clean it up and simplify it. The process is the same; the only difference is hiding steps and making it more user friendly and faster. 64. Going back to the timeline idea… wouldn’t it be cool if you could see your revenue, COGS, gross profit, expenses, and net profit values every day. It would also be cool if your application could show a thumbs up or down (or smile or frown) for in balance yes/no. It would also be cool to show known issues and potential problems. This could almost be called a smart balance or something fun… This would be cool to add to a dashboard of sorts… 65. Add a crumb trail to the application. This would also be cool if you could visually show someone on a map where you are at. You want to know where you are at and where you are going… It would be cool if you could jump or switch places really quickly. Easy… yet flexible menus and jump spots. 66. On a jog with my dad and was thinking about using smaller flash movies inside of a bigger player. If you left the flash environment it would be cool if you could jump back right to where you were. Maybe pass a small string value to an outside request so that it would know to get back. It might also be cool to have certain major functions built in to the main player (adilas dewy decimal, permissions, etc.) and then smaller functions within the smaller flash movies that deal with just their functions. 67. How do you get depth? 1-many relationships, time, volume, layers, chaining, combining processes, pulling from a central location, multiplying, magnifying, compressing, breaking things down into smaller pieces, use over and over, only pull what is really needed, efficient layout and design. Group things, anticipate, lead from step to step, preload, copy, duplicate, and use a template system. Allow the system to grow and be dynamic depending on the user, what they are playing with, and how many are playing with the same items or processes. 68. A pencil works in space. A ball point pen does not. Keep it simple. 69. How about a visual permission map. Just another layer or mapping.

	AU 300		Daily Tasks	11/19/2010	• Went in to town and had a meeting with my dad and his associate at BATC for his company. Went over ideas for their interactive training tool. Good meeting, 30 miles. • Worked on the exact destination action/tasks for my cart favorites. • Worked on the bulk manage section of the my cart favorites. Finished up what I could on the my cart favorites. • Started to work on the photo button assignments. Ended up posting all files online, testing and updating selected help files. • Tested the my cart favorites but did not activate the permission, it still need a little tweaking.

	AU 307		Daily Tasks	11/30/2010	• On the phone with Steve going over the needs for people to view and use multi-media training. We also talked about using the interested company to help fund the project and development costs. • Spent some time brainstorming on adilas university and the multi-media training application. • Wrote an email proposal (light and loose) to my dad and his associate about having adilas.biz be involved in the project for the training application. • Spent some phone time with customers going over the flex grid tie-ins and how to use them to track serial numbers. Sent them a small recap on the phone conversations. • Started working on the new my cart settings for the custom add to cart options. This includes fixed quantities, fixed prices and fixed descriptions. • Added a new logo for a company. Posted colors and logo online. • Full database back-up.

	AU 315		Daily Tasks	12/4/2010	• Went in to BATC to help my dad with the Jim Phillips foam clothing workshop. My dad set up the classroom, the multimedia stuff, live feeds from a camera, video screens and equipment and I was able to help. I also learned a ton of stuff. 30 miles.

	AU 335		Daily Ideas	12/4/2010	-An idea from my dad: Scheduler – “Any” - Any thing – app types and general generic build your own - Any place (loc) dynamic - Any # of events - dynamic - Any length (time) - Any # of participants – dynamic - Any price Jim Phillips – “Systems” -Narrated slide show. -It is a “System” – key word. -Teach the “why” – counter to the fast food mentality – I want it now! -A full system allows you to do things that others can’t do… -Practical – He was talking about heating your home – instead of having tons and tons of firewood, coal and propane… he had a set of foam clothing that cuts to the chase… -Technique and art of doing… -Why do you do it? Because it needs to be done! -Ask the question – what would I do? This helps to develop the why – the why takes time to figure out and develop. -Lab test between static vs. dynamic. Static – there may be other products that perform in this type of environment. Dynamic – real world is very dynamic. You have to plan for it. -Start from the bottom up! -Function vs. fashion – make a choice, this is an attitude. Does it work? Once you get it to work, you can make it look pretty. Pick your options. -Spiritual – attitude – knowledge – stuff (material things) -K = I x E - Information (correct and right) x Experience = Knowledge - Information x Experience = Knowledge. -When you understand the rules you are able to make better decisions. -Knowledge changes attitudes and outlook, this will change the way you do things. -Authority – choice. Responsibility. Accountability – natural flow. -Think dynamic as far as naming conventions. -On the scheduler – add a one to many from location to (rooms, offices, conference rooms, cabins, Kind bed, Queen bed, party room, gym, theater, etc.) a sub location(s). Think one to many… this could be a B&B, office, commercial mini mall, warehouse, etc. One location could have 2 of these, 4 of these and 12 of xyz… you get the idea. -On events, classes, trips, reservations – allow a single customer to sign-up for multiple items, packages, classes, time frames. -The customer could be one to many or one to one or share ticket – multi independent customers. Think about a meal tab that needs to be split between the parties. This may be as simple as multi-payments for a single invoice or ticket. -On both the training and scheduler maybe allow for web services or domain aliases. -Be able to register for classes, courses, tips, events, etc. -On the scheduler – allow it (the training) to be assigned to all of the adilas assets. Why not use the same application for training, visual multi-media presentations for groups, sales, stock units, parts, rentals and reservations, marketing, etc. If it is multi-media, let it go here and play well with all other pieces already in the system. Basically, a 1-many between the system items and the multi-media pieces or from a single multi-media piece out to multiple different items, audiences, etc. -Scheduling – employee time scheduling and shift planning. -what about mixed locations on the same ticket? -Multi-media – allow outside users to log in under a public username and password to submit content for review and formatting. This may require an approval process or an approval/sign off field(s). Only show items that have been approved. -Map touch – maybe color code sections and different departments. Keep the same color code for sub nav and/or reports and/or options. It might also be cool if you are on a page and could open up a visual sub menu. Keep things fast and efficient – this may require a hybrid solution.

	AU 318		Daily Tasks	12/8/2010	• Went out to a company to meet with an associate about the multi-media training application. My dad was there too. We met in his associate’s office and then went out in the plant for a small tour. We ended the day by saying adilas will build it and show a dog or pony show for full buy in on his and his company’s part. 80 miles. • On the phone with Steve going over what we are doing with adilas and the direction we are headed. We talked about needs, wants and the future. Things are going good. • Brainstorming on the multi-media application. Playing with layouts and options.

	AU 320		Daily Tasks	12/10/2010	• Research on W2’s and tax tables. Lots of waiting for the IRS phone system. • On the phone with my dad going over the ideas on the multi-media training tool. Did a quick dimdim session for him to see what I was proposing.

	AU 2181		Brainstorming - Ideas & Concepts for the adilas.biz "Any" Scheduler (Elements of Time)	2/1/2011	1 February 2011 Ideas & Concepts for the adilas.biz “any” scheduler - This section began 2/1/11 & concluded 3/4/11 1. Tie to payroll. Add options for commission gross sales profit. 2. Remember that one of the original ideas in adilas was a series of containers or “Pringle's cans”. Stuff things where they need to go and move things around as needed. 3. The heart is – “Objects and data over time.” 4. We are trying to record and document the “story”. Tell the story: who, what, when, where, how much, how long, why, etc. 5. Map to check points and status as they happen (past, present, and future). 6. Be your own style! And let the users be their own style. 7. Scheduler for personal. 8. Scheduler for customer time cards – tie to invoices and show payment status. 9. Go onsite and ask about schedulers. • Dental, doctor/medical, rentals, car maintenance, manufacturing, classes and courses, golf tee times, hotel/motel, guide services, trips, cleaning companies, services like heating and plumbing, buy here – pay here, CPA/lawyer’s appointments, customer/client billing of time, reservations, salons/beauty, therapy, lessons, events, competitions, mobile persons, vacation time shares, membership, licenses, pre-paid services, etc. 10. What do you call it? 11. How many different pieces does it have? 12. How can you keep it flexible yet simple? 13. I want it to be a time-based scheduler on a flex grid tie-in level. This means all main players can play with built-in functionality. 14. Time… why not call it “Time” or “Element of time” and then let users define if they want customer time cards, rentals, to do lists, mini blogs, appointments, etc. 15. Include anything that could have a timeline on it. 16. Other thing to think about – rentals and buying down units, share and coordinating schedules, unassigned task or job pools, allow others to assign or move to their pile or task-list. 17. Add visible and basic/admin status. See the flex grid tie-ins for more info. This could also be a privacy or mark as private settings. Who else gets to see it? 18. When creating time based element – what about having a point and click interface with show/hide options during the creation process? Options, actions, types, etc. 19. What happens if I pre-define certain types of time elements and allow users to copy/paste and tweak the pre-sets? 20. Maybe I could add options for corp-wide settings and individual settings. 21. This may not be related but what about project management, goals, ideas, tick lists, wish lists, cataloging (events, agendas, video clips, etc.), or documenting ideas and plans. 22. Maybe review the MDI idea center. 23. Blogs, forums, threads, sign offs, comments, sharing and collaboration. 24. Show on web – build a pre-built page to show. This could be a blog, mini blog, update page, or a sales or specials page. 25. Along with show/hide on the web – maybe a show until date. 26. What about a newsletter? Think about an art company’s website I worked with. They also have meetings, shows, and special events. 27. What about an HTML editor of sorts – maybe photos, links, line breaks, tables, div tags (css), lists, horizontal rules, etc. This may have to come later on. 28. Keep it super simple – select time and objects and then click go. 29. Allow the time line to be printed in different formats and outputs. 30. Think about using spreadsheets as a layout form for the scheduling. 31. Some of the users will be doing scheduling either on a phone of mobile device or viewing a schedule from a phone or mobile device. 32. Think about water in a ditch – it always flows in the path of least resistance. Help to channel people and their use of the system so that if flows and is very simple. 33. Allow time elements to be tied together. This could be a single event, a series, a brother/sister or parent/child relationship. Help tell the story! Cause and effect, planned and un-planned, hay and sad, etc. 34. I am not limited to a Flash only interface. I can mix whatever technologies I need to and piggy back on existing technologies. I could use ColdFusion, database stuff, HTML, tables, div tags, css, Java Script, graphics, charts, MS Excel spreadsheets, PDF, etc. 35. Drag and drop is wanted but not required. This may come later as an upgrade or add on. 36. Design it first on paper, create static screen shots, then build the dynamic interface and add the needed interactivity. 37. Hide/show additional details when printing and viewing. This could be page settings, Java Script pop-ups, spreadsheet comments, or Flash status bar rollovers. 38. Random note about Flash – I may need to upgrade to the latest version. I could also stay with my current version for this first round. 39. We need a light package that allows for invoicing, quoting, using a recipe/build for presets, my cart favorites, groups, advanced grids, etc. We need to be able to attach deposits and invoice payments. These items need to flow right in to the normal back end adilas functions. We may need some new flags to help track states and status. I want it to go clear to the balance sheet (only if needed). 40. On the customer time clocks – allow items to be shown as invoiced/not invoiced or no charge. Allow for time sheets to show/hide on invoice. They could be individual and/or summed up. This might tie in to the visibility settings. 41. I want to allow it (time and elements) to be fully connected but they don’t interfere with normal traffic. Maybe another full application on top of the main application. Time goes in both “known” directions. Think 3rd dimension. Multiple pieces may share the same time space but each may have a different life or life cycle. 42. Time needs to be the one (1) and whatever plays in to that space is the many. 43. Allow multiple bookings in a single slot of time. Also don’t force ends to match-up perfectly. Let it flow like water… fully user-maintained… If needed show some extra flags for potential problems, double, triple, quadruple, booking, overlaps, gaps, disconnects, and waiting lists. 44. Allow the users to put and place what they want into the time-based model. 45. Allow users to go back in time (if needed). Basically, time as it is forecasted (future-somewhat unknown), time as it happens (user may be too busy to change something), and time in the past (what did happen or what was perceived). 46. The key to time is let it flow and date/time stamp and the actual history behind the scenes. This will become the audit trail if needed. 47. Like a virtual to do list – If an item gets done, let it stay. If not, allow it to be pushed forward. 48. If I’m using a quote to hold items or reservations – I may end up with multiple quotes (or invoices). It may be cool if you could stack, chain, or combine quotes and invoices. 49. It might be nice if the scheduler had its own photo gallery. It might also be nice if it had access to the reflexive photo galleries (what is it tied to). The main photo galleries are tied to the main objects. The photo gallery for the scheduler will be more of a one-time deal. 50. What if you could search, filter, and print out different Excel spreadsheets dynamically. 51. Think of the Flash timeline – This is a 2-D, layered timeline with actions, labels, spans, fills, blanks, and color-coded items. 52. What if we took that one step further and added a 3-D or cubic level to the time line. Think about the bricks in a building – Each brick represents a block of time; however, as you look closer at the individual bricks you can start seeing the details that make it up. A brick wall can be the entire wall, just a row, just a column, just a small block of bricks (cluster), or clear down to the details of each and every brick. 53. Most timelines are flat and straight. This is random, but what about a cycle, round, cubic, or infinity timeline model. Just a thought. 54. The scheduler might be a series of 1-many relationships. Each time element could have any number of subs. This could be good for details, follow-up, GPS stuff, tie-ins to other pieces, etc. It may need to go to a 3-deep level. Or more… (See #103 for ideas on subs and snap-ons.) 55. Have each corp start over with an id of one (1) and then increment from there. 56. My dad had the idea of the “any” scheduler – (12/4/10) • All dynamic: - Anything – different application types, general, generic, and build your own - Any place – locations and sub locations (maybe even open or custom) - Any # of events - Any length (time) - Any # of participants - Any price or cost 57. The whole thing is a “system”. That becomes a key word. A full system allows you to do things that others can’t do. 58. I want multiple entry points. Use the quick search, use the time element homepage, and be able to add from any unit (just like the flex grid). 59. I think we need to add a new main application type to the flex grid tie-ins. It will be “Element of Time”. Maybe a future one might also be “Standalone Declaration”. This may come later. Maybe even use quote as a future option. 60. Why do you do it? Because it needs to be done! Ask the question – what would I do? This helps developer the why – the why takes time to figure out and develop. 61. Function vs. Fashion – this is an attitude. There is always a choice. Once it works – you can make it look pretty. 62. Add a one to many from locations to sub locations. This could be rooms, offices, conference rooms, cabins, king beds, queen beds, party room, mini mall, warehouse, etc. (Storage units) 63. Allow a single customer to sign-up for multiple items, packages, classes, and time frames. This could eve cross locations. 64. Allow customer to split and share tickets. This could be as simple as multi payments on the same ticket or actually splitting a ticket. Maybe a restore to cart and then some edits. The trick here is being able to keep things tied together, fast and easy, and making sure that the original gets used, cleaned-up, or voided out. 65. Potential problem – Currently invoice and quotes are location specific. We may need to look at this and allow corps to mix and match locations and sub locations on invoices and quotes. 66. Be able to register for classes, courses, trips, events, etc. 67. Employee time scheduling and shift planning. 68. Be able to handle dispatching and service calls. I also have a need to be able to tie-in GPS as part of this. This may be a sub of the time elements. 69. “Apply” what you learn! Do this along the way. Don’t wait to the end. The more you apply it – the more it becomes a part of you. 70. There may be some cross-over to the multi-media player and training application. 71. Recruit help! It is okay not to have all of the answers. The more people that are willing to help, the better it is in the end! 72. I want and need some sort of work, time, or job sheets to help tie activities to invoices and payees (employee/users) to jobs. This needs to tie back to payroll and be available as a dynamically fed option. It would also need its own report from the calculate payroll page. Think about the ski mountain I worked for and how they pay their ski school staff. It could be hourly, teaching time, head counts, referral rates, etc. 73. Contact companies already using adilas to see what they would like in a scheduler application. 74. In order to allow invoices with multiple locations, maybe we will need to switch the (P&L) revenue and COGS sections to invoice line items instead of the main invoice. 75. On quotes – we may need an option that allows for a single quote to be restored to cart or split into different invoices more than once. Currently, once an invoice is created, it locks the quote from being used. This may need to be opened up a bit. Maybe make it a setting on the main quote. 76. We already have the flex grid in place – why don’t we allow options to automatically chain and link things together. Think of this as putting water fountains and sinks around your house or building. You shouldn’t have to go all the way outside to get the water source. 77. What about events and classes. This might be a mix of dates and participants. Depending on how tight the scheduling is, I could see an alternating schedule and/or multiple classes/labs being scheduled back to back. Think of a class at Bridgerland or room at the University. Either way you might need multiple start and end times. How do you keep all of the participants tied to each date and time? Roll call. 78. Some events and classes will be in rented or non-permanent locations. We might want a choice to select from a list of locations and sub locations or enter a temporary or custom location. 79. Spent some time in Staples Office Supply Store in the planner and appointment book section. Think very simple like a day planner, to do list, desk calendar, etc. 80. Allow preset blocks – seconds, minute, ¼ hours (15 minutes), ½ hour, and hours. The user could then see and choose the level without typing anything. It would also be cool to let them see start and stop values. For example: My dad always begins at 6:00 am and ends at 8:00 pm (whatever). If something custom is needed it would also show up. Maybe even have a button for 24 hours (if needed). 81. Time – slots, as many or as much as needed. Items, rooms, persons – as many or as much as needed. 82. We many want the users to choose between simple vs. complex time elements. They also need to be able to show results on different levels. (See #103 for info on subs and snap-ons.) 83. Online reservations and registration will lead right in to online eCommerce. We need to plan for that. Along with that – we also need a way for customers to pay their bills and see history (activity) and outstanding values. Self-service. 84. If people are in a hurry – they may want to schedule an appointment without getting all of the customer info. Allow for a generic party or customer name. This can be replaced later on or just left as is. 85. Adilas already has 2 or 3 storage units. Maybe call and talk with them about wishes. 86. I use sticky-notes or post-it notes all the time. I wonder if adilas could have a small mini blog or quick notes section. 87. Remember this is just a tool. The variable is still people and having them follow through. As an idea – if you tie it to payroll – that helps motivate people and users to play. 88. Be able to choose colors. This is not required. Maybe have a number of pre-sets and then be able to add custom colors if needed. 89. Let the users define preset increments of time – a couple days, 1 week, 2 weeks, a month, etc. Or maybe have a jump field – jump ahead, jump back. Be able to easily come back to the current day. Use a calendar interface to help show layouts and dates. 90. Be able to show other appointments per customer or customer family member by clicking a link or a button to show related or other appointments both in the past and in the future. 91. If a company wants to do rentals or dispatching – allow for pools of items, locations, and users. The system could help you pull from the pools by drag-and-drop or by clicking a check box. Another idea is to have the system remember the main time element as it searches for other pieces to tie to it. (Session scope) Be able to clear the memory if needed. 92. Make this as small and easy as possible – yet as flexible, bit, and complicated as needed. This will be a balancing act. 93. Be able to mark things in/out of play. This could be workers on a crew, service trucks, equipment that is in the shop or being fixed – help coordinate what is going on. 94. Templates of time, start and end time ranges, days of the week that are in play, etc. Be able to set known times and standard occurrences – weekly, meetings, training, lunch breaks, etc. 95. It may be line managers or crew chiefs that are setting up schedules for their employees. Each crew or line may need the flexibility to switch crews, locations, shifts, etc. 96. Be able to schedule a webinar. 97. Allow a buddy system on tasks, ideas, comments, and assignments. 98. Time also deals with the future like goals and forecasting. It could also be used to determine reality vs. planned. I could see a manager setting a goal for each day – then a crew manager entering an actual for each day. That would allow the person(s) to monitor progress and actual output. 99. If you were in manufacturing – you could even schedule production runs, needs, and demands. What about maintenance schedules. 100. It would be pretty cool if the system could help send you reminders . This could be email, screen pop-ups, text messages, etc. As a side note – some scheduling applications use MS Outlook as the platform and then use a MS exchange server as part of the application. Maybe a notification@adilas.biz or reminder@adilas.biz email form or address. 101. Estimates, quotes and job costing. The goal here is to gather up the details and show how they relate to income and costs. This could include supplies, parts, labor, time, overhead, rentals, sub-contractors, project management, fees, etc. It might be nice to have a report that shows what is revenue and what is a cost or expense. The goal is the bottom line or profit margin. Many times, the element of time plays in to these types of jobs. 102. A couple of things to think about – sign off requirements, sign off by who, changing status and how long in each section (aging of changes), assignment changes, aging in the queue and/or running time between phases or status. 103. What I’m seeing develop is a simple time object that can have all sorts of subs or pieces stacked on. Kind of like Legos. The main would hold and carry all of the subs. Each sub section has the functionality built in to it, not the main time element. This allows for known actions to be “snapped on” and they already know how, where, when, and how much to play. Maybe a “time snap-on” or “element snap-on”. Build the functionality in to the subs and options. Maybe just call it and “add-on” or an “add-on component”. 104. Once we go clear to eCommerce – we will need to know what to do (instructions), what to show, and how to show availability and bookings. 105. Each element of time may be tied to a master recipe or template. This will show options, show/hide “snap-ons”, and set requirements. 106. Be able to schedule payments and due dates. This is money coming and going. Think of a bank collecting on a loan or a buy here pay here checking to see if their buyer is on time. This could also be for monies going out. 107. Almost every element or piece inside of adilas is related to time. Is there a way to bring things together without making the user duplicate their efforts? Basically, we have tons of stuff that is already getting assigned to an element of time. I would love for that stuff to show-up and be counted as well. Adilas – All Data Is Live And Searchable. 108. Reoccurring invoices (and expense/receipts and balance sheet items – not done yet) need to show up as an element of time. 109. I’m sitting here thinking about how every piece of the puzzle is tied to an element of time. I’m also thinking about how I could have missed this “Big” of a component of the entire picture. We have been running things for years and only now is it clicking and making more sense. I’m grateful that I’ve had time to soak some of this in. 110. There are six pages of notes in my mini notebook dated back in 8/27/08 under the topic of reoccurring invoices. Here are some highlights and/or ideas: - Inter-corp options, master/sub relationship, be able to turn on/off the master, back tie to units to help buy them down (physically and/or depreciation adjustments), normal operating hours for each unit, only show those hours unless the full 24 hour link is clicked, be able to search for available dates and times, be able to cancel and back things out. - Need in/out stamps for check in/out, booked vs. actual usage, special notes and/or instructions per booking. Think general to specific, average time slot per unit. - What about capacity, # of guests (customers), optimal #, min #, max #. - Productivity reports (booked, used, optional), assignments (requests), mass entry (recipes), different reports that deal with dates, time ranges, capacity ranges, available, booked, etc. - Rate tables for seasonal use, waiting list feature, cleaning status on each unit, package deals, late fees, cleaning fees, other fees. 111. We want to add a sales and promotion section to adilas. Maybe customer reword programs, promotion codes, sales, and seasonal pricing can play in to time. This deals with loyalty programs, points, rations, and marketing campaigns. 112. Marketing and promotion is a huge part of business. Help them start to manage that as well. 113. For drag and drop or selection pools – what if we actually create a second or sub time element for items that are not available. Basically, one pool for active and one pool for inactive or out of play. This may be able to be done by reverse association but I wanted to add it as an option. 114. When going to drag and drop. Use the adilas multi-media player to show and display elements. Include interactions between the left sub and right main panel. 115. At some point we wanted to add specific medical records. The elements of time might be a perfect spot. This would be as a sub or add-on component. 116. What about someone that goes to a resort. Everything goes on a tab and then could be pulled together. It might work cool if you could stack or combine invoices. Another cool thing might be to limit line items by date range and then print or show to your client. 117. Not everything that gets recorded needs to be shown or made printable. What about practice, draft, or concept notes. 118. We need an option to add up to five levels deep for an outline. This outline needs to be able to form in html and automatically in the Flash player (sub nav panel). Be able to edit on a single and/or bulk level. 119. On the outline – maybe use a table with 10 columns. Use two columns for each level. Column 1 (one) would be the Number and/or bullet point. Column 2 (two) would have the title, data, etc. 120. We need to be able to tie assets to outlines and/or subs. This is full content management. Be able to upload and store assets and content for users. We many want this on a different content server. That way it doesn’t impact the main adilas site or traffic. 121. Another function of time is a progress report. This could be added on to a task, to do list, document, idea, project, job costing, students, customer, etc. 122. What I’m seeing is eventually all of this data and content will need to be able to fly around via web services. We want it to get to the level of… “Your data, you cache and retrieve it, we secure it.” Make a super open interface… This could even allow outside developers to tie in to adilas functionality to create a hybrid super solution. 123. “Sphere” – once you are in the data sphere you can virtually go anywhere at any time. Other words or names are ball, global, bubble, orb, orbit, and realm. This concept could make a cool visual for how to get around inside of adilas. The outside layers could continue to expand as needed. 124. Training may fit best as an element of time similar to a document, outline, or idea. The media assets and contents could then be tied to sub elements. 125. Maybe have a show/hide status for items still in edit mode. It might also be cool if you could lock things down at some point and only allow growth or actions to take place on certain pieces. 126. What if we created system-maintained time elements and they became the watchers. Return and report! I’m not saying everything, but what if we wrapped all existing objects and data inside of adilas and allowed them to play or be counted in their own time element. Maybe one element per day with unlimited financial subs. 127. We need to stitch, sew, chain, group and link things together. This could be physical, virtual, or based on a relationship model. The entire system is a series of 1 to many relationships. 128. Originally I was thinking that time had two parts type and function. What I’m seeing is that the type just tells or dictates the functions needed. You can create type by adding function(s). 129. Matter – cannot be created or destroyed – but it may be combined, altered, formed, molded, compressed, etc. Fine matter, course matter, liquid, solid, gas, vapor, plasma, pure, contaminated, etc. Cut it, stack it, bend it, break it, etc. 130. Time – cannot be created or destroyed – this is a give (as far as we know) – what we do with it depends of each person. It could be simple, complex, self, others, persons, places, things, reoccurring, standard, variable, by choice, by dictation, by consequence, by others, etc. 131. Question about the system –maintained time elements – will that blow-up the elements of time table. Maybe we could have a special system-maintained section that mimics the elements of time without adding tons of system-maintained items (non-editable and non-searchable (ish)). In some ways, it might be nice to leave time as user-defined and put the daily watchers in a different table. 132. What if the type of time is the template with all of the defaults and settings assigned. 133. Most email programs have a calendar and appointment application. They may also have a to do list or sticky note section. Some people have apps on their phone. Where adilas comes in is connecting other pieces, built-in functionality, and already in the business platform environment. We win on the scalability and tie-ins to business functions. 134. We may need a special page that helps people know about their options – training eventually, but before that – some sample and guidance… show options. 135. Allow for defaults, presets, and custom values on all entries. This includes date and time selection – auto or custom date/time stamps. 136. Create a master list of functions of time. Duplicate this list and allow users and corporations to modify or create an alias name of the functions. What they do will still be the same but allow for custom naming. 137. Categories are the same way – create defaults and allow them to change the names and values as needed. 138. Categories are tied to functions of time and functions of time are tied to templates or types of time. 139. Certain settings, like back tie to units (or anything else – persons, places, or things) may need settings and options on the individual items that could then play forward. Even though we may want a back tie – It may need to come from the items themself and only play when needed. Another option is to think more globally and create a pool that knows what to do – then when the pool is update, the items already know how to play instead of being on a one-by-one basis. This could even work for sales and promotions. 140. Along the lines above – we may need to add a reverse look-up from the items to the pools so that they know what to do. 141. On the templates (types of time) – allow for the users to either preset hardcoded values or defaults or set the settings to dynamically look-up values like current user, current location, current date, current time, etc. Help wherever possible. 142. On reminders and notifications – push the valves in front of the user on the time homepage and the main homepage. There will also be options to help notify via email or text message. 143. When booking things for a date range – maybe add a transparent sub date/time option to hold each date to help with booking and availability. 144. On categories – instead of just one, what if they could pick and choose – like check boxes or something, maybe tie colors to categories. 145. When showing people how the elements of time work – show them a very basic drawing of the key pieces. (Templates have functions and functions have categories). 146. “A fox that chases two rabbits catches neither.” Focus and get the job done! Then move on. 147. When looking at a single item – show the bookings for three months. This may help to get an idea of usage and availability. 148. Sometimes the prep is more important than the jump. 149. On the templates – It might be nice to add an option to preset sub default titles. Either separate with commas or add a one-to-many relationship. Look at the flex grid titles for ideas. Options may include leave blank, a set value, or a list of values to use. 150. I may need to “dummy” things way down. This is like going hunting with an army, planes, tanks, and ships – when all that is needed is a small gun and some bullets. I know that it is a balancing act, but less might be more. 151. Currently we have a template that controls the elements of time. What if we had some settings that controlled the templates? 152. I can see a market for a scaled down version of adilas – say an adilas express or something like that. - Maybe a home version, a business starter version, an entrepreneur version, a small business, and a medium or large business, maybe an enterprise level. Okay, just took it too far again. 153. In conference on (4/3/11) I heard a talk that was talking about basic needs. The question was posed- will this buy me any bread? Cover the basic needs before we go tweaking to the “nth“ level. Keep it simple! 154. We may need to rate a table per user or per tech. This would automatically tie in to the rate or general amount according to who was assigned and the total time. From Post-it notes: - Group Meetings o Use technology to get the biggest impact - Group Training Sessions - Group Invites/Seminars - Newspaper ads - Flyers - Adilas theory demos - Webinars - Video capture, Dimdim, simple drawings, and power-point slide shows - Use Steve’s house until we grow out of it On customer site: - Easy contact info: o Email form o Phone #’s - Video demo o Overview o Specific tasks or concepts - Maybe a tutorial link or help files - What about showing general pricing and allow credit card payments and sign up - Adilas express - Adilas non-profit - Maybe allow the users to select # or users, # of locations, # of invoices or annual gross sales, send email requesting a quote.

	AU 376		Daily Tasks	2/8/2011	• Tech support, phone calls and emails. • Worked on the multi-media player mock-up. • Sent an email to my dad and another associate of his. • On the phone with a customer going over depreciation and how to record it. • Working on the "any” scheduler application. • Reading old notebook. • On the phone with Steve going over progress and new discoveries. Talked about the element of time and how it is going to play, expand and tie things together. Fun brainstorming session.

	AU 384		Daily Tasks	2/17/2011	• Recording ideas for the training application. • Went in to town to meet with my dad and one of his associates. We had breakfast at BATC and then started talking about the multi-media training tool and where we are at. I explained my personal needs, wants and vision. Both chimed in with ideas and comments. Great session! I took some good notes and we are planning another meeting in a couple of weeks. 30 miles. • Brainstorming on the player and flow for the application. • Watched a couple of videos (online training) at Lynda.com on Audacity and Flash 8.

	AU 451		Daily Tasks	4/19/2011	• New logo and colors for a company. • Working on the multi-corp/multi-location daily/weekly report. • Decided to open it up to single corps and added drill-downs to underlying data. • Finished up report and posted files online. • Sent an email to Steve about the new changes. • Went into BATC (local Technology College) and my dad showed me a demo of some of the new interactive software that he has been playing with. Trying to get ideas for the adilas training application. 20 miles.

	AU 2266		Note - Planning With Purpose & Meeting With My Dad	12/15/2012	Planning with a purpose – do purpose/goal first, then plan - Invoice homepage - Edit line items - Edit main - Printer friendly - Save as pdf - Show/hide menu - Buttons, icons, or links – different categories Places for LTF that I visited: Notes from my Dad: Had a small meeting with my dad at BATC. These are my notes mid December 2012 - Take a few steps back - Make a plan - Show the current tools in the shed - Teach & show - Use the product to show the product - Get ready to expand “as is” – set it up for duplication o Split databases o Add numeric date times - Let people know what we are doing o Share the vision & the future - Work smart - Offer classes – trade out web work for class time - Take yourself out of the pivot point - A time for each scenario - cats blankets or folded paper vs. flat paper - Promises made 7 work to be done - Play as a team

	AU 1011		Daily Tasks	12/18/2012	• On the phone with Steve. We talked about interface and then on to money and what is needed there. We need to either, get more clients, do training, or work for people. If not, I will need to supplement with other work. • Started on personal settings but stopped mid-stream. [This was somewhat of a breaking point for me. What this means is that I have years and years left to make everything happen, we need money, and I felt very trapped. I couldn’t sit there and make another feature. Not that it was hard, I just felt buried and trapped. I spent the rest of the day doing LTF stuff and going into town. Good change of pace.] • Went into Logan to show people the LTF product. Stopped by tons of shops, book stores, and places. Gave demos and gave away lots of copies of the product. Went to Beaver Mountain ski office and talked with the director of the ski school, BATC Bookstore (Bridgerland Applied Technology College), BATC West Campus. my dad’s office, Al’s Sporting Goods, Directive Board Shop, Zummies, The Game Stop, Sports Authority, Seagull Book, Deseret Book, Books of Yesterday, and Oasis Books. Fun and interesting day, 40 miles.

	AU 1029		Daily Ideas	12/19/2012	Random notes, brainstorming, and other ideas….. -What if we taught a class and trained the trainers. I could lead it and then video type it. We could then post it online for other trainers to see. We could even let our customers see it so that they could train their staff or other companies. -On elements of time – allow people to assign a task to a user and then have it show up until it is done or marked off. This is somewhat of a reminder type thing. -On elements of time – add a temp span or color block and id if an end date or time is known. Instead of full color blocks taking up the entire cell, just use a little piece that says, I’m a “blocked in” or “scheduled” piece. -On eCommerce – our first go at it may be only existing customers, web pricing, and only go to the quote or order level. No payments, no inventory, tweaks, etc. -On the orders or quotes (eCommerce) – maybe set the invoice classification to “online order” and then make all normal quotes without the invoice classification (or a default) so we can tell what is what. It would also be cool to be able to sort or pull back data according to the classification. It may be cool to track the classifications as difference windows or date ranges, one-to-many. -Yesterday, 12/18/12, I went in to town to run some errands and spread some love for Learn to Freeride (an interactive CD-ROM that shows freestyle tricks and moves.) As part of my day I went by the technical college where my dad works. I chatted with him for a good half an hour and he pointe me in a good direction. We talked about a bunch of things and here are the cliff notes or shortened version. o Take a few steps back o Make a plan o Show the current tools in the shed o Teach and show o Use the product to show the product o Get ready to expand “as is” o Let people know what we are doing o Work smart o Offer classes, use technology, trade out we work for class time (there at the college) o Take yourself out of the pivot point These may not be his exact words, but this is what I took out of it. -Since then, yesterday, I have added a few more key points that I think need to play in to the mix: o The mix or blend may be what we are looking for. There is a time for each scenario. Order, disorder, speed, slow and steady, work and rest, new and old, etc. o I still need to keep promises made and work to be done. o Play as a team! -Where are we headed? Do I know? Am I okay with that? What would I like to change? I have so many questions and my head is in competition for which emotion to follow. It is kind of weird; I’m at peace yet anxious, scared yet excited, overwhelmed yet driven, doubting yet confident. It is really hard to pin down my thoughts. I can be focused like a laser beam and in no time flat, be as random and spread out as a light hitting a rough, yet reflective surface. I feel in control yet desperately grasping for stability. I keep seeing life lessons being played out before me. I’m part of them, then watching from the outside, then back inside. -Random change of events – one minute I am writing the above message, the next minute Steve calls and we talk for an hour. Then later today, I go on a walk in the snow with my dad and now I am super pumped up and ready to make things happen. -We may end up using the content server as a second adilas data server. Build with major growth in mind. -We need to under promise and over deliver. -Build up the education and self-help sections. Create some points marketing and really put it out there. -Show the vision – make a lot of it public knowledge. -Dream the dream and then live it! -Any outside report – pull the in under the main adilas wing, that way when we expand, they already exist inside the main core or application files. -What if we built things out so adding a new server was as easy as adding a new corporation. Automate database creation, settings, starting values, etc. -Eventually we will need to the ability to talk back and forth between servers and share data via web services. It may be good to start laying that foundation. -We may want to spread things out (servers and services) just to protect ourselves. Think of the saints when they came to Utah, once they got set-up, almost immediately they sent other parties out to settle other areas. That way it was harder for someone to come in and shut everything down. It also created mini bases and strong holds. I’d like to do something similar.

	AU 1040		Daily Tasks	1/7/2013	• Tax withholding tables. Checking for new withholding tables for different states. • On the phone with my dad and his associate talking about a light history and background of the adilas.biz system. • Phone calls and tech support. • Brainstorming and talking with my wife about the connection between teaching, learning, history and mixing and blending ideas and concepts. • Writing and recording ideas.

	AU 1086		Daily Tasks	2/14/2013	• Reviewing the rep flyer document. Sent a copy to my dad and Steve. • On the phone with a client, they had a number of crazy internal trades, deals, pass through items, etc. We walked through each internal deal. As we went through, we used the flex grid to tie the pieces together. • Final editing on the career opportunities flyer.

	AU 1091		Daily Tasks	2/19/2013	-Super early in the morning 2:00am-4:30am Steve and I (Brandon) got the server back online. We woke up and then got ready for day 1 (one) of the first adilas.biz training courses. We met at Bridgerland and set up the class. We had a number of students who participated in the class. We also had a guy who watched via Skype. We went from 9:00am-5:00pm with an hour for lunch. Adilas bought the lunch for the students. My dad videotaped all three days of training. After class we ate dinner at my house and talked and had little light meetings. Steve and I worked on his developer laptop and getting everything installed and up to date. To bed after 12:00am. 30 miles.

	AU 1092		Daily Tasks	2/20/2013	-Day 2 (two) of training. We woke up early and did a few things and then off to class for the day. 9:00am-5:00pm in class. My dad videotaped the whole day. That night after dinner, we had a meeting about what we need to do and where we want to take adilas. My wife participated in this team meeting. 30 miles.

	AU 1093		Daily Tasks	2/21/2013	-Day 3 (three) of training. My dad taped the whole class and we were at it from 9:00am-5:00pm. At the end of the class, I showed my mom specific things that she had questions on. We spent three good days and only touched on 25% of the application. That was an eye opener to quite a few of us. More good stuff to come. 30 miles. The adilas team was planning on leaving sometime on Thursday the 21st of February. However due to snow and weather, they ended up staying until Sunday morning. Those extra days were a blessing to me and my family. We got a lot done and were able to talk about a number of different topics and items.

	AU 1104		Daily Ideas	2/23/2013	-“It’s time for musical chairs… everybody get up and go to the next station.” -S.O. -“Are you prepared to let go of what you need to?” –my dad. -With reps – do’s and don’ts. With paying – do’s and don’ts. -What do we need to setup a corp – process or required pieces. -Adapt and overcome! -Outline and structure the training material – we were a little too open. -Bank account to get ACH services. -Take off the flyer about bringing the lunch. -The servers are the top monster. -(Sketch in notebook with clusters. Content - Data 1, 2, 3, etc. - each corp has its own little area - each corp feeds the outside web services (adilas web services). If content is needed it gets pulled from a content server. (Adilas university)) -Sketches of the cluster model. -1 content server hooked to multiple data servers. -Each data server would have a number of corporations under a specific data server. Kind of like their own little “adilas”. -The model above is for a single cluster. Multiple clusters could be used either together or by themselves, very flexible… -Put the help files on adilas university. -Put the YouTube videos on adilas university. -Put the developer’s notebook on adilas university. -Monitor each cluster and who is on each server. -Growth and “farming” of data servers. -Keep cluster 1 and data 1 very small and make adilas the controlling entity. -Play musical chairs – mix and match – learn other pieces of the puzzle. -Accounts are reviewed on a semi-annual basis. Based on that review, we analyze and will do something with the monthly fees. -Create a web-based company assessment. Fill out as much as you feel comfortable: looking for numbers and values. - # of EIN’s - # of Location(s) - # of Employees - Business type or industry - # of transactions - You get it all…. Help us know which features you are interested in? o Do you have inventory? - How many unique types? o Do you have any serialized inventory or big tick items? o Do you sell labor? o Do you sell time? o Do you sell services? o Do you plan on uploading photos, scans and images? o Do you plan on using the scheduler and elements of time? o Do you plan on using merchant processing? o Do you plan on using eCommerce? (May require additional fees) Still dealing with a web based company assessment… - Other notes on request - Reps or how did you hear about us - Main contact info - Company name - Contact name - Phone - Email - Call to action! -Have the reps use this request from to submit info to us. This would be how they request a new corporation. -Buttons that say “quote me” or “sign me up”. This is a call to action or an action link. -We will be contacting you. -Have and show some testimonials. -Having the adilas team here in Utah at my house was a great blessing and we got a ton done. I’m super thankful for a couple of extra days due to bad flying weather. It was a blessing in disguise!

	AU 2276		Brainstorming - Meeting to Talk About Adilas	2/23/2013	- Accounts are reviewed on a semi-annual basis. Based on that review, we analyze and will do something with the monthly fees. - Web-based company assessment (numbers and values) – fill our as much as you feel comfortable o EIN’s o Location(s) o Employees o Business type or business industry o # of transactions o Which of these features are you interested in • “You get it all” • Do you have? o Inventory types and counts (how many) • Unique items • Serialized • Non-serialized • Labor • Time • Services o Other advanced options: • Images/scans photo uploads • Elements of time • Merchant processing • eCommerce o Other notes or requests o Reps or how did you hear about us o Main contact info o Company name o Contact name o Phone o Email - Have the reps submit info to us. Request a new corporation - Buttons that say “quote me” or “sign me up” (“action link”) - We will be contacting you - Testimonials - It’s time for musical chairs… everybody get up and go to the next station. (Shari) - Are you prepared to let go of what you need to? (my dad) - With reps – do’s and don’ts o Paying do’s and don’ts - What do we need to set up a corp – process or required pieces - Adapt and overcome - Outline and structure the training material… we were a little too open - Bank account to get ACH services - Take off the flyer about bringing the lunch - Global updates o Creates and updates take longer o Reads are faster o In loops (batch transactions) wrap in transactions or rollback recovery options. o The database should be the base model o “Linked in”

	AU 1109		Daily Tasks	3/4/2013	• Getting the new training flyer ready. Created a number of new links with dates and training info. Sent an email to Steve with the new flyer. • On the phone with my dad setting things up for the next training session. Signed up for a new visa card for adilas. • Requesting a quote for 3 new dedicated boxes from Newtek. We want 2 data servers and 1 content server. • New logo for my dad’s work. Created a new corp and added colors and a logo. Set my dad up with a username and password. • Research on elements of time and showing spans.

	AU 1111		Daily Tasks	3/6/2013	• Working on pulling time spans for elements of time. • On the phone with Steve talking about servers, plans, and white labeling. Steve is getting some major pressure from different clients on certain subjects. These pressures are helping us to figure out our game plan. • Went in to town to work with my dad and my sister on go to meeting stuff. We setup cameras, mics, and ran a couple of sessions on GoToMeeting. Good stuff. 20 miles.

	AU 1112		Daily Tasks	3/7/2013	• On the phone with Steve. We talked about increasing the commissions back to reps up to 40% in a tiered structure based on how many clients the rep had and was able to maintain. We also talked about resellers, load balancing, and white labeling options. Good stuff. • Went into town to work with my dad and sister on setting up GoToMeeting and options for setup, filming, and capture of the content. My sister recommended that when we started the meeting (the real one) that we kind of talked briefly about the structure of how things work with go to meeting. Who gets to talk, who gets to show webcams, who gets to chat, etc. We played with remote stations, dual webcams, and audio options. There is some power there. 20 miles. • Called and canceled the old content server. • Checked out some custom files and provided a rough quote on time frames. • New logo for a company. • Reviewing some content from GoToMeeting. • Filling out the annual PCI Compliance questionnaire. • Working on the calendar time spans. It gets pretty deep dealing with what to show and what to hide.

	AU 1128		Daily Tasks	3/26/2013	• Went in to town for day one of adilas training. We set things up and got on to GoToMeeting. My sister helped with GoToMeeting stuff (chat, recording, and controlling audio and web cam settings). That was a huge help. We recorded tons of audio and screen capture stuff throughout the three day session. We did three practice sessions with GoToMeeting but this was our first live or real session. For the actual training we went over and covered the map. We started on the button and went over locations and tax settings, web presence, eCommerce, tools, maintenance, customers, inventory, etc. Basically just jumping around the adilas map and training and touching on different players. Throughout the day we had a number of different people pop in and through the GoToMeeting applications. At the end of the day it took us 2 hours to convert and render the recording. Both my mom and my dad helped with different tasks throughout the day. I’m very grateful for their love and support. My mom was in the training class all day every day other than when she had to pick up a cousin from the airport on Thursday. Great stuff. 20 miles.

	AU 1130		Daily Tasks	3/28/2013	• Went in to town for day three of training. • Quick emails to update people about changes. • Back to training… We got to BATC and a client was already on the call and wanted help with a payroll issue. We got the GoToMeeting session going and hit the ground running. Kind of a crazy start. We got him taken care of and then rolled into some of the new changes and features we added last night. They were default check write banks and options for changing the main payables vendor id on a special live PO. We then did a training session on payroll and time cards or user time clocks. After lunch we did some training on customers, the customer queue, statements, and recording the story and how time and dates play in to every part of the puzzle. We talked a little bit about “types” and “functions” and how these play into the puzzle. The last couple of hours of the training session were quite fun for me. We switched from training and doing to a discussion based format. We talked concepts, vision, future, needs, and ideas. My dad came in and joined my sister and I talking about adilas stuff. A great brainstorming session and we recorded the audio portion of it. We talked about the developer’s notebook, training, education, pricing, and tools. We had fun talking about business tools and what it takes to break certain models. We covered the following: - Pen & paper - Spreadsheets - Databases - Software - Networks and IT stuff - Server databases - Web - API’s (Application Programming Interfaces) & business platforms * Some of the things that break these tools or models – searchability, permissions, volume, dates & times, costs, upgrades & versions, settings, conditional logic, centralized data, options for change. • Back to the training stuff… We ended on a fun discussion and then started another wave of talks after the class and while we were cleaning up. The last topic was on education and even getting adilas or adilas concepts out to the rising generation. This would involve non-profits, grants, teams, and helping to educate people and students. Great stuff. 20 miles.

	AU 1150		Daily Ideas	3/28/2013	-On an education level, maybe think about putting something up on Lynda.com (online training for tons of different applications). -Interns may not be from the college… keep it open and include professionals, teachers, or independents. Thinking of a contact at BATC, that does accounting, consulting and teaches for Bridgerland. They would be a great asset. -Comment from my dad – Permissions are like scrolling a football field, maybe do it by section. -On the developer’s notebook… maybe add all of the brainstorming and ideas by section vs. by date. Get things organized and make it easy to get to. -Add a “change” link to help with flow for changing main tie-ins like vendors and customers. This would help on invoices, expense/receipts, and special live PO’s (mixed vendors). -On the training… schedule it out, ask what people want to learn about in advance, show the new features, create your culture. Maybe do more question and answer sections on a weekly basis. Record everything (within reason).

	AU 1180		Daily Ideas	4/3/2013	-Make a business plan. Include different rounds and steps. Budgets, pro-form, interns and required steps. Also include what we’ve already done. Be positive and share some vision. -Use people that I know who have skills. My sister, contacts at Bridgerland, my sister-in-law, my dad and others. -Plan for cross corp business. Create a cross corp mapping table that allows any corp to crisscross or map to any other corp. This could be a one-to-many from the main corp to his/her outside vendors and/or customers. Sharing customers, sharing parts, sharing stock/units, etc. -As a marketing game… Do a competition between universities and private parties to create a niche product that is able to ride on top of the adilas engine. (Different skins or different functions.) -Sell adilas as the engine! -How will people know what our product can do? What are the core functions, types, and tools? The “how to” is different than the “what is possible”. -Look for and harness people’s potential. It is great to share, build and grow. Help other people be successful! -What functions do we provide and/or offer? Once you know and choose a function, we can then teach you how to use or do those functions. -Pricing… there is or there are tons of variables… which ones are important? Which ones are key indicators? How can we let price be our friend? Reps really struggle with how open the concepts and pricing structure are… We may need a standard or some way to quantify this.

	AU 1154		Daily Tasks	4/4/2013	• Working on numbers and proforma Excel documents. Forecasting and documents dealing with adilas numbers. • Went to Smithfield to set my mom up on adilas. Talked with my mom and dad for a while about concepts and vision of adilas. Did some consulting with my parents on paper and then started going through the setup process. 10 miles. • Went in to Logan to talk with a contact and his accounting buddy. Great meeting and I learned a lot. I got roasted a bit but no harm done. It was fun to express myself. I was very honest and they were very point blank honest. My contact ended up watching and listening and his buddy and I battled balls back and forth. I come out of the meeting knowing what they were looking for and being able to talk about our vision for the future. In a nutshell, I took away the following ideas… adilas is an eBusiness model, we are currently in the cost covering mode, be careful of the innovation model (quick in & quick out), we may end up being acquired by some other company, we are looking for a loan, not for investors at this point. In order to get a loan we need to know what is it for, how much, and what are we willing to give up? We also talked about notes and what are my end goals? Is it a certain amount of passive reoccurring money a month or what? We did go in circles a few times but I felt very good about it and what I’m learning. A couple things that were hotter topics were breaking or changing tradition, changing roles, why would a company want to change from their current system, and what is the scope of the business? I brought up about sharing code and assets and that was met with very negative reactions. Anyway, just some notes. • Research and recording ideas. • Working on recording changes to customer assignments for invoices.

	AU 1186		Daily Ideas	4/11/2013	-All system players (main application types) need a general reference number field. This would allow for any outside alias names or numbers from other outside systems. -On the main… There is usually a lock-down option and/or a lock-down permission of sorts. -Every major player needs: - The main - Line items - Payments - System histories - Flex grid tie-ins - Photos/scans - Custom documents - Other – content or files (assigned per corp) -Vendors, users and payees need a general notes field. -Work on standardizing things -It is okay to still need future development. -My dad and I went on a hike up Smithfield Canyon. We saw hundreds of new improvements. On the way home we were talking about how those improvements will open tons of doors and will more people enjoy that area. We also talked about improvements that we make to adilas and how they will help tons of people. -Maybe make a business plan for MDI and then use that and invest in adilas. -On a hike with my dad we were talking about all of the inter-connected systems in the human body. It works like a machine and all of the systems need to work together to make things happen. I asked my dad to start thinking about doing a human body systems comparison with the adilas concepts and players and how they work in a system. It will be fun! Human Systems vs. Adilas Systems Skeletal (bones) -? Muscular (muscles) -? Nervous (brain & nerves) -? Digestive (stomach & intestines) -? Concepts & Players Respiratory (breathing, lungs & heart) -? Circulatory (lungs, blood, heart, veins) -? Reproductive (make new ones) -? Endocrine (waste) -? -Speaking about interconnected systems – we have often asked, what pieces can we do without? The answer usually comes back as none of them – we need them all or certain people need them all. -I had the thought – what would happen if you tried to take your religion out of your personality? Depending on how inter-connected they were… it could be impossible to separate. Kind of like having a body but not having bones or muscles. They just go together (or should go together). -On some of our help files and pages (normal webpages) it might be nice to make some of them into Adobe PDF documents for easier printing. We have 400+ help files and pages of information. We almost have a mini library… -The deeper we get, the more some of our jobs become organizing and grouping large amounts of data. On this same note… the first step is catching all the data. Once we are catching the data, then the task becomes being able to search, group, and categorize that data. Without being able to quickly and accurately get at the data, it almost becomes like a broken model. -My notebook is exploding… My paper model is starting to break. I’m writing as fast as I can but I have no way to go back and search it. I’m starting to duplicate things, forget things, and it is taking tons of time and then tons more time going backwards. It might be time for elements of time and using adilas (all data is live and searchable) to record and track adilas. -Speaking of breaking models… My notebooks are all on paper and in tons of different spots. I need to centralize the data, categorize it, record it, and document it. I have a lot of important stuff but it is all spread all over the place. -I think I will make a master element of time for each main topic. I will then print out a list of main topics and their id #’s. I will then go through my notebook and hand sew elements of time together using the flex grid. My master thread will hold id’s for all subs. Each sub will hold its own data, images, notes, and details. The mini subs will be standalone by date (historical) and the master thread will be by category according to the thread name. Here is a simple diagram. This will be duplicated over and over again… -(Sketch in notebook of this idea) Flex grid to subs, flex grid tie-ins, sub elements, master thread or by category.) (These (referring to subs) would be subs or the details. They would be standalone entries with their own dates, captions, notes, colors, and photos/scans.) (They would be sewn together using flex grid.)

	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.

	AU 1164		Daily Tasks	4/16/2013	• Went in to town to see a bank associate. We talked for a while and then a rep from Salt Lake City came in. We talked about adilas and where we’ve been and where we are headed. We talked quite a bit about ACH (auto clearing house or automatic debit). We want to be able to use ACH as a payment method for adilas. We also talked about merchant processing and direct deposits. It was a good meeting and I think that he got a good taste of what we are doing and what we are looking for. 20 miles. • Went back in to town to meet with my dad. He wanted me to talk with a lady in the Business Resource Center at BATC. On the way, my dad and I chatted with a number of people. I talked with some contacts about elements of time and time clocks. We, my dad and I then talked with a lady about a car repair facility. We then went over to meet with the lady in the Business Resource Center. We talked about tons of stuff and she had run an art gallery for a while. As we talked, she was virtually reliving memories about what was required to run her business. She really seemed to connect with what we are doing and seemed to enjoy the direction. She gave me some contacts up at the University who deal with entrepreneurs and business mentors. She is part of “SCORE” which is a national organization that helps small businesses. Entrepreneurs may be a perfect match for what we do and what we are offering. We talked with Cindy about presenting and giving classes on what we do. She was very open to the idea. Good stuff. 20 miles. • Lunch meeting with my dad. While at lunch my dad grabbed the manager and had me talk to him. We chatted for half an hour about how to run things over time and help with flow and editing data. We talked a lot about hot interface plays into the puzzle. We also talked about how new and modern processes sometimes need to be new from the start. Tradition can be a huge wall. One of his problems was dealing with three different systems and marrying all the data together. That is so common in businesses today. • Writing and recording hours. Lots of fun stuff today. • New logo for a company.

	AU 1191		Daily Ideas	4/16/2013	-On the API (application programming interface)… I want to control access on a corp level and on a user level. This will end up being almost a sub permission level. Inside of adilas, each section has a permission. On the API level, each function could have a permission level just by allowing access or not. This is not required but could be allowed. Major options for customization and special tweaks. Think permissions on a function by function basis. -Some people who see the need or have felt the pain – know and understand what we are doing! -Interface is huge! We want a standard classic interface and then tons of industry specific interfaces. If those don’t work, build your own through the API. -Yesterday, I was thinking results = functions x players x concepts. -Interface is a huge part of that puzzle. Instead of saying times (like a math function) what if you say mix and blend until you get interface. So, in a way interface is part of the results. -Promotion codes, tracking sales, loyalty points, customer gift cards, etc. All of these are future developments. Some of this starts getting into marketing. -Two possible spots for more love are in marketing and HR (human relationships). Both could use a little dose of lovin’! -On pricing and billing – maybe point out the monthly stats as part of the monthly billing structure. That might help us get an idea of usage and prices. Being able to save as a PDF would also be cool. -The secret is to centralize the data and then record and catch the pieces. If you can do these two things, the rest will be possible. It may not be in the right format (yet) but if you have it, you will be able to use it. -On the content server… We need to make sure and store the bigger files in the database. We want to prevent any direct browsing of the files. If the users want it, they will need to go through the correct channels. -My dad said this today… “These guys haven’t broken any rules per say, but they have broken tradition.” That’s a fun way to put it!

	AU 1193		Daily Ideas	4/18/2013	-Define the goal, objective, or desired outcome. This is the best place to start. Once you know the goal, you can then figure out how to get there. This is a huge piece of the puzzle. -We have a couple people who are masters of different accounting programs. It would be cool if we could hire them to help us with common processes in other programs. For example: In QuickBooks you do this. In adilas you do this. In Peachtree you do this. In adilas you do this. Etc. I’m thinking of other contacts. -Adilas may need a custom solutions department or team. This could be skins, graphics, interface, flow, or even franchises. -On photo galleries. Add small graphic to try to help people get information about uploading photos. Put it on the top of each add/edit photo page. This will help users get the correct settings. -Perspective… what level are you at? What do you want to see? Where would you like to go? I was hiking with my dad and we were way up on the side of a mountain looking down on the valley. Being way up high allowed us to see things differently as compared with being in the middle or at the bottom. The feature we were looking at were the same but depending on our perspective they seemed or appeared different. As I was hiking I just kept thinking about the word perspective and how that applies to tons of different things. -Along with perspective, we have a fun little graphic that my daughter made. It is a busy street scene with cars, roads, buildings, parking lots, etc. Here is the text that we have on graphic… Think of a bird’s eye view looking down on a busy street… Lots and lots of activity… coming… going… turning… doing… staying… becoming… what if you could… (then we had a little picture of a helicopter). Watch from above? Be on the street level? Be inside one of the cars? Actually play back the movie? (then in bold) Well, you can!!! This little graphic deals with levels, perspective, permissions, and even roles and permissions. Kind of fun. -Learning for transfer… Once you learn to drive a car, you can drive a golf cart, a van, a truck, an SUV, etc. The concepts are the same. You may need to make a small changes or tweaks but the concepts are the same. The same thing happens inside of adilas. Once you learn the concepts, you can apply them in any situation. You will also be able to mix and blend concepts. Good stuff!

	AU 1209		Daily Tasks	5/9/2013	• Went out to meet with a contact and do an adilas demo. He tracks restoration jobs and weed control data. These are private and government projects that are doing large restoration projects. He has a home grown system that has four to five main pieces feeding into a large database. He then tries to pull data out of the database and show it to his customer and/or staff. His pain was in the marrying of all the different systems and then trying to pull data back with nominal web background (coding knowledge). I showed him elements of time, dynamic pages and search options, and some code basics. It ended up being more of a consulting meeting vs. an adilas demo but I used adilas as my supporting documentation and real life example of what was possible. Kind of a fun angle for using adilas as a working example of options and theory. 20 miles. • Recording notes and monitoring remote servers. • Working on eCommerce. Implementing new settings for cart options and flow. Started on the add to cart. • Went in to Logan for a couple of meetings. Stopped by the bank and talked with a banker about ACH debit transactions. I then went to Bridgerland to meet with my dad and contact he had been talking to. We had a multi hour training session. It started out with just my dad and a couple. We talked theory, history, and light inventory. Another contact then joined us and we talked questions and answers for quite some time. This contact is a buyer for a sporting good warehouse of sorts. Great meeting and great energy. The couple was really excited. 20 miles.

	AU 1213		Daily Tasks	5/14/2013	• Customer migration for a company out of Texas. Round two. Pulling data off of spreadsheet and importing into live database tables. • Invoiced for a company and tried to charge their card. Came back as do not honor. Small email to let them know what is going on. • Working on eCommerce add to cart. Lots of copying and posting and checking form values. • Working on eCommerce and the add to cart page. • Went into town to do an adilas demo. Put some files in the safe deposit box. Stopped by and chatted with a contact at the Logan bank. Then went to Bridgerland for the adilas demo. There were four people plus my Dad and I. There was a computer tech guy, a couple and another contact. One of them has a small repair shop; he wanted to see quotes, customer, and invoices. The couple just wanted a small overview. Great meeting and it was fun to interact with the people. 20 miles.

	AU 1222		Daily Tasks	5/24/2013	• Went in to Bridgerland to have a meeting with my dad and a guy. He is maintenance guy and teaches for Bridgerland. I did a demo on stock/units and internal costing, outside repairs, and internal invoicing. We talked a lot of theory and I used Steve’s old business and another company to show different options. The highlight for me was talking about tracking data objects over time. I showed both this gentleman and my dad some of the little sketches that I’ve been working on. (5/11 and 5/17 ideas on time and tracking to micro levels). The other highlight was dealing with ideas for tons of different interfaces. We talked about interfaces for maintenance, home food storage, process monitoring, batch codes, etc. I can’t wait to get the program to that level. 20 miles. • Meeting with by brother. He was showing me his music making software and cool things he could do with it. It was quite a visual piece of software. All kinds of buttons, options, sliders, dials, switches, etc. He kept showing me screen after screen and all of them were different. It was a little overwhelming but good to see. It cast a thought about complexity and how relative complexity really is. Another really fun thing with the sound editing software was how it could deal with live input and just by changing settings and filters it could change the sounds in real time. It also mapped things out in layers that could by moved and mapped over time. Most media type software packages have both layers and time lines. Movie editors, Flash, sound editors, etc. Anyway, fun to get some layering and timeline ideas. Great meeting. • Phone calls, emails, tech support, and playing with new POS (Point of Sale) hardware for the upcoming training session for adilas. • On the phone with Steve going over some code questions. Good stuff. • New logo for a company. • On the phone with some new contacts talking about an adilas setup. One of them wants to be an adilas rep and the other is a business consultant that works at the college. Great people. • Domain settings for adilascontent.biz.

	AU 1225		Daily Tasks	5/28/2013	• Finished up the customer migration for a company. • Emails and tech support. • Creating an agenda for day 1 of the training class. • Went into town to teach day 1 of the Logan training class. It took quite a bit of time to set up the class. I had printers, barcode scanners, credit card readers, scanners, etc. Tons of stuff. I only had a few students but it was fun to do and show some different pieces. We talked about world building and how user to corps are setup. I used a graphics program to draw and show relations. I started with Microsoft Paint and then went to Fireworks to be more accurate. It got a little bit deep but it was pretty fun. One of the interesting things that happened was I introduced the “chooser” (choose your interface) and it kind of confused the students. Almost too many options before they really know where they were going. I’ve got to think of way to ease people into the mix of adilas. It is quite big and very dynamic. 20 miles. • Small side note about how the day ended (5/28/13). About 2:30-3:00pm my wife brought my son and daughter to Bridgerland. She had taken my son in today to be checked for diabetes. His blood sugar level was over 700+. A normal level is between 60-100(ish). Anyway, the doctors wanted us (my wife and I) to take my son down to Primary Children’s Hospital in Salt Lake City. So, we cancelled the last couple of hours of the day 1 (one) training course and I went with my wife and son down to Salt Lake. My dad and mom and sister helped shut things down and took my daughter home. My dad helped my give my son a blessing before we left Logan. Pretty crazy day!

	AU 1656		Daily Tasks	6/5/2013	• Prep for meeting with the bank. Quick phone call to Steve. Printing out documents and such. • Went in to town and signed papers for a new bank account. This account will be used for ACH and EFT transactions. That is where we will be doing direct debits (taking money) and direct deposits (pushing money). I also talked with our banker about options for getting an SBA Loan for adilas. Good stuff! • After the bank I took a few June training flyers around to different people. I took some to the Business Resource Center. I then took some to a contact at the BATC Business Department. I chatted with them for a bit. While at Bridgerland, I dropped in to see my dad as well. 20 miles. • Emails and bank stuff. Send them a rough budget for the SBA Loan. • Recording hours and notes. • Working on eCommerce and adding and editing web customer info. • On the phone with Newtek going over issues with the new server. We had a couple of questions and couldn’t get them figured out. We ended up figuring out that a CFX extension for Cold Fusion was an older 32 bit program and didn’t work on the new 64 bit servers. Light research on the cfimage tag. • On the phone with a local Cache Valley company that might be interested in using adilas. • Working on cfimage tag stuff. Made a bunch of changes and uploaded and tested files. Swapped out an older CFX tag or extension for a new way to process images. It seems to be a bit slower but hopefully it will help us do the transition. • Spent a couple of hours updating login files and testing the new server. • On the phone with tech support going over migration stuff and checking files and pages on the server. • Pointed all logins to the new server and did some light testing.

	AU 1685		Daily Tasks	7/2/2013	• On the phone with a client going over ICC’s and what our goals are for Internal Cost Corrections. We went a couple of rounds and talked about math calculations on the fly and pros and cons of different options. • Finalizing things on the old dedicated server. Called and told them to turn it off. Got a full database back-up file from the old server. The current database size is about 4.5 GB. • Emails and tech support. Small invoice line item label change to show a qty. Mapped to the quantity field. • Going through emails. New logo for a play site for a tree cutting service. • Emails, expenses, and installing new printers and scanners. Backing up files. • Went in to town with my brother. His hard drive crashed and we had to go get a new one. We bought the hard drive and then went to Smithfield (his home) to set things up. We had a few system issues and ended up coming up with a temporary solution. My dad was helping my brother and I with the system issues. 20 miles. • Installing and doing our first round of videos through Sorenson Squeeze (video compression).

	AU 1703		Daily Tasks	7/29/2013	• Emails, phone calls, and light tech support. • Reviewing notes from the Colorado training trip. Great notes typed by my sister during the training event. They are now part of the history. Also read her notes from the adilas team meeting in Salida on 7/19/13. Great notes and wonderful recap of ideas, suggestions, and options. • Decided to allow training videos to be sent out via DVD. Burning disks, updating pages, and prepping things to get some of the footage out the door. My dad called and said that he got the digitizer for his camera as well. He also recommended that I at least put a CD label on the DVD’s that have the adilas training. Good call! • Went into Smithfield to work with my brother and sister. My brother and I looked at some video and I got a new file from him. I talked with him about future plans and needs for video clips. I also talked with a contact about using adilas as a rental program. 20 miles.

	AU 1704		Daily Tasks	7/30/2013	• Went in to BATC to work with my dad on some government surplus items that were donated to Bridgerland. They, BATC, are going to be categorizing and selling the surplus items. I was there to help and show them how to use adilas to track and show the items. Very little work was done inside of adilas. Most of the day was getting organized and sorting out the items. Only about an hour of the day as spent inside of adilas. Just enough to show them parts, PO’s, and photo gallery stuff. 30 miles. • Went to Smithfield to work with my sister and brother. Set up a printer for my mom and did some light training. She will be using it for her herbal business and tracking things through adilas. The meeting with my sister and brother was dealing with elements of time and putting the developer’s notebook up on adilas university. We also talked about some marketing stuff and using the Utah State University campus as a venue for training and sponsoring different events. 20 miles. • Went back in to town to work with my dad and others on the BATC surplus items. Minor work was done in adilas but I feel this could be a good project to help show how adilas can help companies with their eCommerce and web presence needs. Good stuff. 30 miles.

	AU 1722		Daily Tasks	8/6/2013	• On the phone with my brother talking about graphics and sales. We are planning to meet tomorrow and go over a plan and do some training. We talked about doing some marketing and even some graphic practice on the developer’s notebook. I’m hoping to use my brother’s skills in graphics, animations, and in sales. He has a natural skill set that lends well with sales. • Back working on some data combing for a client. Lots of manual entries. • Went in to Bridgerland to work with my dad and a contact there. I spent some time working on a customer data files and helping to answer questions about adilas. I also had some light conversations with different people who came in to look at the BATC surplus items. Once everybody left, I ended up talking to this contact about business and how to grow. He is quite a dreamer and has worked with IT (Information Technology) people before. We had a good talk. He made a couple suggestions including contract labor and keeping things on contract labor for as long as possible. He also mentioned project management software and helping to track things. My mind turned to elements of time and tweaking a few things out a bit. We also talked about using other people’s money to grow our business, instead of us funding the projects. Let our customer’s fund projects that they want and then sub those projects out. I (Brandon & Steve) need to get out of the hot spots and dream and manage more. We also need to charge more and cover our costs. Good things are happening, we just need to keep going and be willing to change as needed. Change can be very hard. It can also be needed. • More data combing for a customer data upload. Finished up and uploaded 1,100+ new customers and log files. Sent an email update.

	AU 1728		Daily Tasks	8/13/2013	• Emails and light research on the first data gateway. • More emails. Small fix on the flyers page for outside reps. • Went in to town to meet with my brother. We talked graphics and then did some stuff in Flash. My brother wants to learn and I’m game to help him learn. It will be fun. 30 miles. • Meeting with my dad and one of his associates. We met with a CPA/business consultant about setting up an education based non-profit organization. Good meeting. • I then worked with my dad on setting up a demo for use with the Bear 100 mile race and using adilas to track runners. We took some time and entered in some fake data.

	AU 1756		Daily Ideas	8/21/2013	-I was on a walk with my dad this morning and I got to thinking – my dad is a great recruiter and talent scout. It would be cool to tap into that talent and resource. -A long time ago I worked with a guy who was a master designer and a great artist and computer guy. I was thinking about contacting him and seeing if he had any leads to people we could hire for adilas work and projects. Ben is a master and would be another good resource. -Use the adilas demo sites in training. This will help keep them up to date and make them better play grounds.

	AU 1736		Daily Tasks	8/22/2013	• Tons and tons of brainstorming ideas. Lots of them have to do with the teacher interface we are working on. See other notes and bullets on the next couple of pages. I’ve got 12 little post-it notes full of ideas written or scribbled out on my desk. • Made some phone calls about an upcoming teacher’s meeting next week. • Emails and other phone calls. • Called my brother to talk about some graphic changes we need for the teacher interface. • Emails and recording notes. • Made a to-do list because my desk is exploding with post-it notes. • On the phone with Steve going over different projects and future game plan options. Our game plan is to keep our costs low. We spent almost an hour talking game plan, goals, and ideas. We are going to be openly soliciting help, funds, and ideas from the adilas community. This will push the product forward and will create tons of new jobs. We are seeing a growing need to push elements of time to its full potential. We need it to help communicate with our clients, our users, our developers, and with the community. Good stuff. • Recording notes and trying to get organized. • Phone calls and emails. • Went in to town to meet with my dad, my brother and another contact. This contact is a freelance graphic artist and is going to help adilas with some graphics and basic HTML stuff. We chatted and shared some needs and vision of the future. We looked at her work and talked about some training for my brother. She will help train him in Adobe Illustrator, Adobe Flash, and Adobe Fireworks. She should be coming to the adilas training in a couple of days. 30 miles.

	AU 1757		Daily Ideas	8/22/2013	-Last night and this morning I had a great brainstorming session. The result was tons of post-it notes all over my desk. Some of these notes are in random order but were part of the brainstorming session. -On elements of time – We need a multi filter for elements assigned to a single person (normal) plus any elements that are unassigned or general items. This could be as simple as a list like “1,77” where 1=unassigned, and 77=some user id number. This is a small tweak but it could really help in a shared environment. -We’ve said this before but we need to open up the adilas API (application programming interface) and make it consumable by any other application and/or programming language. We need to be willing to allow things to be more open and available. -I don’t have to know all of the new technologies. Allow others who know the new technologies the ability to use and build as needed. Let them consume or use pieces as they see fit. -We may need to hire out the web design for the main adilas.biz website. It might be good to get some fresh blood and new ideas. -My brother said his friend wanted to see the customer reviews and ratings for adilas. We are working on it. -On standalone flex grid reports. Allow multiple sort options. This could be on custom fields, dates, values, id numbers, etc. -On the standalone flex grid report (and maybe other flex grid reports), add up the columns if possible. If numeric, great, add it up; if not, assume 0 and leave the total blank. -We have had requests to add bulk flex grid tie-ins. This most likely will be custom but very possible. One of our first shots may be for teachers and students and entering grades and assignments. -On elements of time, in the time slot view – add a check for pre (before block) and post (after block) elements of time. Basically, show a count of elements that are outside the visible start and end time block. -On some of the custom interface pieces – we may need to check for certain settings or custom documents. If a corporation doesn’t have those, show a light error and maybe even show a graphic or screen shot of what would happen. This could help teach them and still say a gentle no. -Maybe use quick graphics and proofs to help show what the plans are and what might be coming. Just like when a building is going up, the drawings or plans help to show the vision. We need more of this. Something quick to show the concept. -We may have other pages where we could create some quick graphics to show the concepts and/or mock-ups of what will go there. Treat it like marketing and planning. -Show a standalone flex grid link right by the in-line flex grid report. Currently, the link to the standalone flex grid is up at the top of the page. We may also want to add new flex grid tie-in links where the flex grid in-line reports and shown. Make it friendlier. -Quote from my friend in Colorado – “Get out of the way and let people come in!” -Add a button for the “paperwork” link to pages. If the custom documents exist, let people get to it easier. -On the custom documents page, maybe show buttons and links. Currently only links are used. It could be something like: Button [view/use] – Title and normal link (some custom document name), [view/use] – (some other title name), etc., etc. This may help it be more user friendly. -You dream it up – we’ll wire it up! -The above statement “you dream it up – we’ll wire it up!” This came about while my dad and I were out on a walk. We actually stopped walking and I wrote it down. I’m a pencil and paper guy. My dad had his cell phone and did a voice text message conversion and then tried to send it to me. I won because he didn’t have any signal… kind of funny! -There is more and more new technology being developed. It is very hard to keep up. We are seeing smaller and smaller devices, more and more touch screen, and even hand help projectors and motion sensing technology. We need to let adilas play in those realms. We do this by making it consumable! -We need to add some validation on dual salesperson assignments. Currently, an invoice, a customer, a quote may all be assigned to the same salesperson without any validation on who is the second or other salesperson. We do need to tighten this up. Once we do fix this – we also need to fix older records and existing data. -My dad is a great talent scout, coordinator, and go to guy. He is kind of like the character “sniff” (nose to the air) in the book “Who Moved My Cheese?”. That is awesome! -Things are changing rapidly – we need to plan for that. -I may only be able to document things, but at least they are written down. That may be my contribution! -My dad and I were talking – we know a guy who has a fancy Mustang (car) but he keeps it in an old cargo box. It is a gem (the car) in a box (old cargo trailer). Adilas is kind of like that right now! -On the standalone flex grid reports – Allow a show/hide option for the different columns. There may also be a value for show/hide “auto” which dynamically checks for which fields to show. Currently, the default is “auto”. If we add the other, it just adds to the flexibility of the tool. As a note, the current “auto” setting checks the lengths of the fields and looks for values greater than zero. If yes, it shows the value. -Marketing idea – Let people know about our ideas and tick list. Then allow then (the people and/or users) to help fund the projects. Kind of like a think tank or over a pre-order system. Maybe set a goal as far as people, interest level, or funding dollars. This could be per project. Coordinate these values to a level of “see a need, fill a need!” Good stuff!

	AU 1737		Daily Tasks	8/23/2013	• Reviewing graphics for my brother. Answering emails and light tech support. • More graphic stuff with my brother. • Working on elements of time. Added a new link to the add/edit sub dates and time section. The new link allows you to add a new sub starting right where the last one left off. • Went in to town to work with my dad on tracking runners for the Bear 100 miles race. Making small tweaks to adilas and the sub dates and times feature within elements of time. 30 miles. • Went up to the University and talked with a gentleman in the Business department. We had a good sit down meeting and I tried to tell him what we are looking for as far as interns and help from the college. It takes a little bit of time even for people to understand where we are coming from. I really enjoy talking to people who will listen. One thing that I do too much of is trying to get out everything at once. I get so excited, I just want to tell them everything all at once. • Went back to Bridgerland to work with my dad more on tracking the Bear 100 runners. He is getting the flow down and it is fun to see him using adilas. • Recording notes, checking email, and checking in on different projects. • Went in to Smithfield to help my brother and give an adilas demo. The guy was interested in an inventory tracking system. He wants to do eCommerce, eBay, and merchant processing. Fun little demo. I then got some new video clips from my brother. He’s been working hard!

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

	AU 1742		Daily Tasks	8/29/2013	• Went in to town for day three of the August adilas training. What a great session! We covered some things that we had never covered before. Our goal was banks, deposits, expense/receipts, and back-end accounting stuff. Well, it got pretty deep and we followed a ton of paths from start to finish. It was really fun. We did a whole day of training on the backend of “the story”. Tons of relationships and cause and effects. Great stuff. We covered expense/types, old school vs. new school account, flow on the map, what is automated – what is not, options, variables, objects and data over time, potential problems, known issues, disconnects, and vision for the future. I used my marker and drawing tools more during this training session than any other training session. It was almost to the overboard level. The whole thing deals with flow and cause and effect relations. We had good participation both in class and online. Tiring but awesome! 30 miles. • Working with my dad on his new video and digital video toys. We are hoping to record right to digital vs. tapes and analog technologies. Exciting stuff.

	AU 1764		Daily Tasks	9/2/2013	• Updated a commercial video for a client’s website. Posted new files online. • Reviewing notes and notebook files. Read my sister’s notes from training. • Sent an email to a graphic associate about a new graphic assignment to help create and meet the player groups for adilas. This deals with the 12 main players and how they interact, play and function. This is kind of like introducing groups of people for a movie or book. We are hoping to make it fun and fresh. • Posted a new YouTube video online. • Recording notes from the past couple of days. Brainstorming on ideas for showing people our to-do list. • Went in to Smithfield to work with my dad, and two brothers. My dad and I played with his “direct to edit” video recorder. This takes a standard video camera and skips the old analog tape and goes right to digital storage. This saves time on rendering and digitizing files. We are really excited about this. I met with my brother and got him some money. I met with my other brother and he showed me some ideas he has for some adilas commercials. I’m excited to see what he comes up with. Good things are happening! 20 miles. • Working on a new training flyer for September. • Posted the new training flyers online. Updated the news and update page.

	AU 1769		Daily Ideas	9/4/2013	-On a walk this morning with my dad – We heard some dogs barking but we couldn’t tell where they were coming from. We decided to check it out because something wasn’t right. There were two dogs and they were stuck on a cliff band. Who knows how they got there. We scrambled up and checked it out. The dogs were fine but we didn’t know where the owner was. We looked around, yelled, whistled, etc. Anyway, we helped the dogs get out, called the police, and waited for a call back. It ended up that the dogs had been lost for three days and the owner and the dogs got re-united. We were grateful that the owner wasn’t missing. It is crazy to see how fast our own little world can be flipped into a different scenario. Life is very precious! -We have had requests to turn the customer tax category into a real setting. Currently, it is only a reminder and shows a warning if not used correctly. People are in such a hurry, the little warnings don’t do the job. They just glance right over them. People want things automated and easy!

	AU 1770		Daily Tasks	9/5/2013	• Went into town to meet with the folks about tracking the Bear 100 runners and using adilas to do it. I watched and listened to what they had going on and how they were trying to fix it. They have fixed one of the pieces but also introduced tons of new requirements and variables into the puzzle. My presentation was a simple drawing and then a couple minute presentations of what adilas could do. I was having fun. My dad and two other guys were there. Good meeting. 30 miles. • Emails, phone calls, and tech support. • Working on a new set of pages to help document the current adilas pages. This is the start of the adilas API (Application Programming Interface). Planning out and adding new database tables to hold the documentation pages and information. Added eight new tables. One for the main page of function, one for modified log notes, page comments, page parameters, page results, page sub results, page samples (code), and a history table to record the changes made.

	AU 1797		Daily Ideas	9/12/2013	-“adilas engine” or “adilas core” – Thinking about bolt-on products to the adilas engine or the adilas core. I think either one may work. I kind of like the adilas engine visual best. -I was thinking about getting help on different projects. What if we fully documented specs for the project, included all requirements, brainstorming ideas, wanted flow, and even possible mock-up screen shots. Then posted the projects online and let outside developers bid or see if they are interested in the project and/or the job. Basically, let interested people find us instead of us staffing and finding all the talent and skills. There are pros and cons to this but I wanted to record the option. -One thing that my dad said was… Interns don’t have to come from the University or College. Basically, keep an open mind and look for and find talent wherever you can. -Note on this student’s idea about getting rid of Accountants. He had a thought… what if we could get rid of the job Accountants? We could layout the categories and then plug stuff into the slots on the correct days. Make it real-time and just plug things into a linear spreadsheet of sorts. Anyway, after he got done telling me his idea, I told him that he would love what we do. Instead of using a simple spreadsheet and plugging in the values, we use objects and data and run it over time. His idea is very similar to the financial history report that has not yet been build. Here is a rough sketch of his idea…. … Date 1 Date 2 Date 3 Date 4 Date 5 Date 6 ….. Totals Category 1 100 100 … … … … … 200 Category 2 … 10 … … … … … 10 Category 3 300 … 500 200 … … … 1000 Category 4 … … … 250 … … … 250 Category 5 200 … … … … … … 200 Category 6 … 700 … … … … … 700 ….. … … … … … … … … Totals 600 810 500 450 0 0 … … Imagine time across the top in days. Down the side would be the different financial categories. The numbers would then be plugged in where they needed to be or what happened. So… to take that to the adilas level… Imagine something very similar but the values would be fed in from underlying data and objects that are carrying that data. Each data point would be a drill-down link to the underlying data. The actual dates at the top would be a drill-down to the effectual history report for that day (what shows up for roll call). The categories could be links to details filtered by the categories. Basically, instead of plugging the data into specific spots, the system would map and roll call the data to the spots. The spots (data points) would then become the drill-down links to the underlying details. If more detail is needed, you could have different views of the report and expand sections as needed. If you want even more details, you could click on the objects themselves. This could allow for the full one-to-many relationship, any photos or outside documentation, system histories, and links to other pieces of the puzzle. The whole story right at your fingertips! In a nutshell, this student’s ideas prompted me to write out more of what we were thinking about clear back in January and February of 2011. If you want more info, go the adilasuniversity site and search elements of time for the word “financial”. You’ll get some good results.

	AU 1807		Daily Tasks	10/3/2013	• Uploading new YouTube videos. • Tech support. • Organizing expenses and invoices for interns. Made a couple of calls to interns and contacts. Also called and left a message for a couple other bankers that my dad recommended that I go see. • Went in to town to get some files from one of the interns and ended up talking with 3 different bankers. I spent half an hour to 45 minutes with each banker. I spoke with one of the bankers, a good friend; I then went and talked to the other two bankers. I got tons of good information and each one had similar things to say. It all came down to the fact that adilas is considered software and somewhat of an intangible asset. Even though we have a great product and tons of potential, the banks are required to meet certain requirements in cash flow (capital), collateral, credit score, and character (type of person and/or business). All in all, I had a three hour schooling on the ins and outs of banking and lending. Great information and I really enjoyed it. I was super glad that all three bankers were very nice and listened to my story, needs, wants, and ideas. They each gave me a bunch of feedback and I really appreciate the info. Great use of a day. Good stuff. • Sat down with my wife and discussed what I had learned and what options we have to play with. She doesn’t like to talk about debt or borrowing very much, I can understand that. • Created the October training flyer and posted things online.

	AU 1809		Daily Ideas	10/3/2013	-Idea from my dad… Sell the bank on how we can help small and medium businesses with our software and web application tools. -On elements of time - Be able to duplicate an element of time on a calendar type interface. Use settings and check boxes. Show a month at a time. Be able to advance months as needed. For example: (Sketch – showing ability to select all for each day, Sun-Sat, going down that column; also able to select the whole week going across) Use a calendar and check boxes to duplicate an element of time.

	AU 1818		Daily Tasks	10/14/2013	• Burning a back-up DVD of files and recording hours. • Recording hours and sending emails out about this week’s ColdFusion training course. Sent messages to the interns, other contacts and Steve. Trying to slowly create an internal adilas team of sorts. Once we create a team, we should be able to start harvesting many of the profitable byproducts that adilas create naturally. • On the phone with Steve going over budgets, interns, projects, and forecasting. Good stuff! • After getting off the phone with Steve, I started working on an adilas pricing matrix. This deals with the number of users/employees per location, number of invoices, stock/units, eCommerce, payroll, and other services that are needed. Basically, it is a simple one page worksheet that helps get the ball rolling. It’s not perfect yet, but a good start. • Went in to town to start day one of five for some adilas intern training. Our goal was to go start to finish on what we were calling the adilas YouTube video project. The goal was to create some new tools to help categorize and catalog the hundreds of YouTube training videos that we have. As the day went on, the subject kept expanding from just YouTube to general training to categories files, media, content, etc. Interesting progression. We wrote down our goals, talked, brainstormed, and did some planning. One intern did a great job and helped with the planning session. By the end of the day, we had a rough sketch of the database and tables we wanted to use. Great session. 30 miles. • Cleaning up, rendering videos, and emails. • Met up with some contacts that my mom and dad had set up. He is a small business consultant and entrepreneur and his wife works at Bridgerland, great meeting. We swapped stories and background and then talked adilas concepts for quite a while. They both had good questions and I even ended up writing and drawing out analogies on the white board. Great conversation and meeting. They would like a demo in a couple of weeks. • Emails and making a few tweaks to the adilas pricing matrix.

	AU 1820		Daily Tasks	10/16/2013	• Recording notes from loose pages. • Brainstorming on a new visual way to show flow inside of adilas. It is a cross between a target and a web or spider’s web. It deals with space and organization of data. (See sketches from scans in photo gallery 10/16/13) • Working on the adilas GPS (Global Positioning System) graphic. The sketch on the other page is kind of like a GPS and could be used to show where date is located. A virtual “where am I at” or “where is your data at” type interface. I spent some time on the computer taking the idea to the next level. Very fun! I could totally see this as an interactive touch screen app. • Went in to town for day three of the adilas ColdFusion class. We worked on making a basic template, created and setup the Application.cfm page, and created an error handling page. Great session. As part of the session I showed the interns the new GPS graphic that I was working on. I also showed my dad and we had a good talk about how we could improve it. He had lots of good ideas about way to make it look cool and be interactive. • Working on the Texas 130-U PDF document. Working on the adilas GPS graphic.

	AU 1842		Daily Ideas	10/18/2013	-On the adilas GPS graphic… Put the world building concepts first, then the adilas counterparts, then the GPS interface. Idea by my dad. • Human world building analogy on the left • Next verbage for the different levels • Next the adilas world counter parts to the human world building concepts • Next the adilas GPS interface model -On the content management system…. Harness the power of referencing a path to local files, remote access files (reference the URL), internal network files, or physical files that get uploaded to the servers. -Just an idea for the content management system… what if we could help a user upload their files to an outside storage system. Say: Google drive, Microsoft Sky drive, drop box, Adobe Creative Cloud, YouTube, Photo Bucket, Facebook, etc.? Basically, from adilas to something else. Then hold and store a reference or hyper link to that file or folder or directory structure. In a way use adilas to create a link in table of contents and reference library. We don’t have to store all the files… we may just need to allow for flexibility and then help people organize their stuff wherever it is located – whether it is local, remote, network, or physically on an adilas server. -Use the power of a hyper link to reference data wherever it is stored. They, hyperlinks, help the user jump right to the source.

	AU 1824		Daily Tasks	10/21/2013	• Finished up recording loose pages into this main notebook. • Prep for the Colorado trip. Paying bills, grabbing expense/receipts, gathering check stubs, etc. • Entering expense/receipts and posting files online for the interns. Wrote a big email about the plan this week and next week for the interns and the training that will be available. • Working on the Texas 130-U PDF document. Finished up both the full document (lines, shading, verbage, and form fields) and the data only document (only the form fields – nothing else). Posted the flies online and sent an email out to the trailer dealerships we have in Texas. • Working on the eCommerce payment page. • Driving to Denver – worked on the code while my dad was driving. Total mileage for the whole trip was 1,460.

	AU 1828		Daily Tasks	10/25/2013	• Got a call that the server was down. Got things back up and going. • Responding to emails. Worked on an error when a user had an open timecard from another corporation and he/she was trying to switch corps using a custom navigation page. Posted the new files online. • Went to Salida, Colorado to film a commercial at a client’s store. My dad did the filming and the rest of us helped, watched and had fun. Quote from my dad, “this is more than a store” – meaning how they help disabled adults. Great session! • Responding to different emails.

	AU 3645		To-do's	10/25/2013	Scratch Paper Notes – To-Do’s - Read a contact’s stuff - Server research – hot fixes, ping, and resets - Check on money movement options - Flash interface – start with what you have & know you can always circle back around. Just get it out there. - Roll call page & virtual GPS on adilas - Map it out - Skip training for November & December - Print out notes from training session - Review the developer’s notebook - Follow-up on tech support & emails - expenses - “adilas diversity” – my dad 10/28/13 - Adilas world, adilas university, plan it out and go get it

	AU 1829		Daily Tasks	10/26/2013	• More emails and removing the October training flyers. • Brainstorming session with my dad, my mom, and my sister as we were driving home from the Denver adilas training. We talked needs, ideas, outside help, sharing vs. protection or sharing as a form of protection, flash, graphics, and education and training. We had a good time and it was a great brainstorming session. We are going to build on what we have and use the tools that are already in place. Very positive. Total mileage was 1,460 miles.

	AU 1844		Daily Ideas	10/28/2013	-“Adilas Diversity” – There is strength in diversity. This was a quote from my dad while on a walk this morning. -We had a request to tie a customer address right to Google maps or have some way to auto connect through a hyperlink. -The deeper we get, the more people want to reverse look-up different pieces of the puzzle. Basically, we create a relationship from one thing to another. We then show that relationship. What we are finding is that people want to see the reflexive side of that same relationship. Basically, if a relationship exists they want to go back or forward to follow the relationship. IN a nutshell, they want a roll call page of what is connected to what and can I get there from piece to piece quickly. Very interesting! -Along those same lines – reflexive back and forth compatibility, I was talking to my brother and he wanted to be able to link to a media/content piece (file) and then also have the ability to go from an item to a file and also from a file to an item. Both or any direction(s).

	AU 1831		Daily Tasks	10/29/2013	• Recording notes and uploading YouTube videos. • Recording notes from loose paper. • Working on the media/content project to prep for class today with the interns. • Went in to town to meet with the interns. One intern had done some good homework and shared with the class. He did a great job and it really helped u all out. We talked a little bit about table joins and lists today. 30 miles. • Worked with another guy on table joins and how to do that in SQL. I then worked with my dad a bit on his classes that he wants to offer and show as the BATC Custom Fit classes. • Uploading videos to YouTube. Checking code that an intern did for the media/content project. Wrote an email back to him with suggestions. Good stuff.

	AU 1882		Daily Ideas	11/18/2013	-“Set the table… the Lord will provide.” – Talking with my dad this morning on our walk. He was talking about a mutual friend that used to love the above saying. It shows great faith and good intentions. I’ve also heard it put this way… work as if everything depends on you, and pray as if everything depends on the Lord. It still takes work but it also takes a bunch of faith.

	AU 1904		Daily Tasks	12/19/2013	• On a conference call with some folks from Texas. They had some questions about bank balances, balance sheets, etc. Small training session on those pieces. We also changed some colors and showed them some new tools. Good session. • An intern came over and we had a planning and brainstorming session on how we are going to setup adilas and all of the server and cluster structures. Lots of drawing and sketching of ideas. We also started listing out goals, needs, and known issues. We decided that we would use corp key id’s, allow unique aliases if needed, and make the corporation id’s all come from the master control center. We also determined that users would be help in a master list as well. We would have records on the admin master level, the cluster level, and the world level. Users may also have a local or inter world id and an id that is global or outer world id. Each world will mostly use the inter world id numbers. The more global or outer world id number will only be used to determine cross world or cross cluster relationships. Also, I gave the intern a copy of some of the adilas code for his home machine. I think that will help him get his head around things better for future projects. Safety and security through sharing. • Went in to Bridgerland for the last class session of the year. We had 3 interns there and my sister. My sister taught us for an hour on expense/receipts and how seeing the bigger picture helps us understand the system thinking. As you get the bigger picture, you start looking at cause and effect relationships. As you start seeing cause and effect relationships, you start formulating goals and desired outcomes. Once you have a goal or have an anticipation of what an action does, you have more focus and are able to get to the task at hand. In a way having the goal and knowing how to get the outcome helps you move around the system better. Another interesting concept was dealing with a super flexible interface and then slowly becoming more rigid or linear. Think of driving to school... You could come from any direction until you get to the school. Once you get there, you most likely have to use an existing door to get in. Then once inside, you may have more halls, corners, levels, etc. Once you get to the classroom, you may be limited to one or two doors to actually enter the room. Interesting analogy. This relates to tons of things in life. My sister also used the white board and adilas map as visuals to help with her lesson. Good stuff. We then went into the system and played around with specific goals and cause and effects in mind. After that, all of us boys did a session in ColdFusion on the photo gallery for elements of time. This project is ¾ of the way done but has been sitting on the sidelines since 10/10/13. At the end of class we had each person come up to the whiteboard and map out the flow and pages for elements of time. I would say a page and how it was connected and the guys would draw the pages and flow on the board. I thought it was really fun and good way to visually figure out what was there or part of the tool set. 30 miles. • Emails, giving my dad some files and recording notes in my notebook. It’s been a good day.

	AU 2015		Daily Tasks	2/13/2014	• Phone calls, tech support, and emails. • Went in to Bridgerland to work with an intern on the media and content project. I worked on a mini object builder page to help an intern with the API and web services. Got some customer uploads prepped for the interns. We watched my sister’s first weekly training session on settings and permissions. She went for an hour and really did a great job. I was very impressed. She had done quite a bit of prep in reading, making an outline, a work sheet, and then presenting it. Great job! After lunch, an intern and I had a great session on what a code review or sign-off session was. My favorite part of our session was having both of us up at the whiteboard drawing out processes. We then went into code and did some testing. It was a great session. See other notes for some details. 30 miles. • Went out to my brother’s house to get some video clips. We also talked about options for employment. My brother owes me some back pay hours. He is going to start working some of those off by taking flyers around and participating in training sessions. We also came up with a deal to set a rough budget per training session as far as cost to do video editing. • Went back in to Smithfield to get my brother a check and some flyers. I then went to my parent’s house to take my sister some video clips and pick up a power cord for my laptop. I ended up chatting with my mom and dad about adilas for quite a while. Part of what they like about adilas is that we are helping people get skills and giving chances for individual growth. If truth be told, I really get a kick out of helping people. That is fun! 20 miles. • On the phone with my sister going over her classes that she did today. Good stuff and great start. We also talked about some upcoming projects, options, and vision of where we are going. It sure is fun to dream. We talked quite a bit about some of the future and potential of the elements of time section and how we, adilas, will use that for training, recording, and making assets become available.

	AU 2038		Daily Ideas	2/24/2014	-What if we used JSON objects inside of adilas to store custom settings for different pages. This could be report assignments, report settings, dynamic filters, etc. Think of the old “Mend & Repair” section but use objects to store data and criteria vs. 100’s of different form fields. Let the JSON (java script object notation) object flex up and down as needed. This could allow one single table to hold data for all possible custom settings and custom reports. That could be super powerful! -Along with custom settings, we could even scope or do some internal mapping to FORM’s, URL’s, and variables scopes. Maybe even session and application scopes if needed. -If we used internal objects, we could use a simple table that was tied to specific pages, one or more users, etc. Think user specific reports, corp specific reports, etc. -If a specific report setting was passed into a page, we could go directly to that page, its object (search and filter criteria), and display the results accordingly. That would awesome! We could use this small pass through to allow users to set up their own buttons, links, and drill-down options. Mix custom code and in-line settings to get a super user-specific interface. This could end up being the “my favorites” section of the application. -If you used objects to store settings, you could store as much or as little data as needed. The object would flex up or down as needed. This could even be which fields to show, what order to put them in, and which criteria of filters to use. -We could establish dynamics for dates as well. This would allow for hardcoded dates or mobile and flexible dates or date ranges such as: current date, current week, last week, next week, tomorrow, yesterday, this month, last month, next month, etc. If a flexible date was used or stored, the system could figure out those settings on the fly. That would allow reports to roll or move forward or backwards as needed. Basically, time keeps moving, by allowing the dates to move, the reports are able to keep up without changing the dates all of the time. Think dynamic! -If you use objects to store data… you could potentially use a general database to store the objects and yet get tons done without having a specific field for every little setting. Let the objects carry and hold their own baggage. This is very flexible for unknown or changing pieces however may not be ideal for standard one-to-many relationships. Basically, I’m trying to say, yes, this does exist and is very powerful but may not be the best option for every scenario. Mix and match as needed! That is the key! -I could see objects being used where criteria, mappings, and flexible options are needed. Where things are known or standard, I could see using traditional relationship models being used. -As a note, the application flex grid (business to business flex grid tie-ins) may need mappings and settings stored at an object level. There may be some unknowns or super complicated pieces that could be tied together with objects vs. traditional fields and columns in a database. -If all data is live and searchable, I do see a smaller problem searching objects vs. searching pre-filtered database rows and columns. To the user, they just want to search their data. To the backend developers, that means knowing where things are at and how to get to them. Things will be buried deeper in code vs. on the surface level. -There are some modern terms that we might want to check out. They deal with objects and such. They are: NoSQL, NoJS, JQuery, Ajax, etc. -While on a walk with my dad this morning, we were talking about objects and options. I had the idea and thought that objects may be a way to store in-line custom code and settings. We could provide a front-end interface with options and point and click form controls. We would then roll all of that data up together and store it in a general object. Basically, instead of having a field and table for every option, we could code the options into the object. The database would then be the storage engine and then code could be stored in a generic container. Anyway, I think it could simplify storage needs and account for future growth and options. -Another thought along those lines are dealing with elements of time and holding and storing custom JSON objects as a sub of time. This could be in the sub comments (already able to store HTML and large amounts of text) section if needed. -Another thought was to create objects and send them back and forth to represent physical one-to-many objects inside of adilas. For example: If someone passes in the invoice number of 500, we could put all of the invoice pieces into one return object and then pass that whole object back to the user. We could pass like data, relationships, subs, and even other pieces in a virtual one-to-many relationship or object. Help make the pieces be mobile and consumable. -As an option for group players and custom code options… what if we treated each section similar to elements of time and master time templates. We could figure out the options, settings, and built-on functions for each main player group. We could then save those options as an object. If someone wanted to tweak out the options, they could pull up the main group player options, change what was needed, and then reset or submit the object to be held in the database. -Using objects could even expand the flex grid and add one-to-one or in-line code options right to the main object or player groups. Say you wanted a new field to be stored per invoice. Instead of using the existing flex grid tie-ins to create the new field, what if you went to the main object itself and added a bolt-on piece right to the main object. The upper main object level could then control the sub items and the data storage level. Basically, define the additional field and store them in an object at the root level. Then store the extra data at the individual or data level. Both the group definitions and the individual object pieces would be stored as JSON objects. The system could then interpret the results. -If we got into storing pieces of code and settings as objects, one of the tricky pieces would be showing, placing (location), and formatting the output. Another tricky piece would be validation, search ability, and defaults. Anyway, it does get kind of deep fairly quickly. However, if dynamics are needed, this may be a great option and/or tool.

	AU 2053		Daily Ideas	3/3/2014	-My dad had the idea… change the name of your weekly demos to something like… “Challenging & Breaking Tradition”. We ended up with a title of “Cloud Software Demo – Challenging & Breaking Tradition”. The idea came from my father.

	AU 2045		Daily Tasks	3/5/2014	• Recording notes and working on organizing my notes, pages, and brainstorming papers. • Went in to Bridgerland. My dad drove me in, so, no miles. I worked with an intern on getting in to payroll withholdings for state tax calcs. We found a small state tax setting error for the state of Colorado. An intern spent some time updating his local database with the correct changes. These changes still need to be pushed up to live servers. I also spent some time with another intern working on the adilas API calls and backend application. • Working on updating the Colorado state tax settings. Started to build an update page that updates settings in bulk. Decided to have an intern help and get involved in the pages and update process.

	AU 2046		Daily Tasks	3/6/2014	• Went in to Bridgerland to work with the interns. I worked with an intern on an update page for state tax calcs. I’m trying to get an intern ready to work on payroll, withholdings, and state tax settings. All of the federal stuff is done for this year but we have lots of state withholdings that need to be done. Towards the end of the day, I worked with the other intern on the PayPal gateway integration and sign-off. Technically the PayPal gateway is ready to go once we launch the files. 30 miles. • Went over to the Cache Business Resource Center and setup for our first ever weekly public software demo. Our subject was: Cloud Software Demo – Challenging & Breaking Tradition. It started out okay and we were bouncing around talking about business functions and how, we, at adilas, are handling these functions and processes. We covered online expense tracking, web presence and eCommerce, and then some backend office and Accounting functions. My dad was there and had a couple questions and comments. My sister was also there and helping to take notes, comment, and do the GoToMeeting stuff. We had a number of people online and we were doing great. About half way through the demo a guy that works with robotics poked his head in and participated in the discussion. He basically asked questions for the next whole hour of the demo. It was perfect and he asked some great questions and made great comments. It was really fun. See some of the other notes on some of the stuff that he said. Anyway, it was a great session and I really enjoyed it and learned a ton! Good stuff!

	AU 2051		Daily Tasks	3/13/2014	• Went in to Bridgerland to work with an intern on the media/content project. We worked all morning on the advanced media/content search page and the advanced results page. Adding a “refine your search” option to the page. Another intern came over and brought lunch for the other intern and myself. After lunch, the other intern and I did a whiteboard session on the flow for the adilas API (application programming interface) calls. The whiteboard really helps to visually display the pieces. Another huge help is to have each person with a marker. If the other person can translate the subject into his/her own language, it really helps the subject to stick. • An intern and I ended up on the physical upload section for the media content section. 30 miles. • Went over to the West Campus to do the weekly adilas demo. This is the second weekly demo. We started out with just my sister and myself and an adilas rep online. She had some inventory questions so we started there. We went over PO’s, parts, items, barcodes, and how to track things using the RFID tags and manual packaging options. My mom and my aunt came by and they helped lead the rest of the demo. She had some data tracking questions and we tried to listen and then do some consulting/showing her how to accomplish her goals using adilas. It really helps to have someone with real questions. If we can help them out, it makes our product that much more valuable. We talked about using a mix of tools to get the job done. For my aunt’s job, we ended up going over customers, flex grid, and small elements of time. Great demo and training session. After the session, my sister and I chatted about the future, current development, and goals for where things are headed. I am very grateful for wonderful help from tons of different people. It makes a huge difference. A few of the current helpers are my wife, my sister, my mom and dad, Steve, David, Shari, Craig, the developers, my brothers, and many others. I am also very grateful for tons of help from above. My Heavenly Father hears and answers prayers – time and time again! Very grateful!

	AU 2059		Daily Tasks	3/15/2014	• Emails and tech support. Started working on a new admin feature to help update the max number of the auto increment (auto number) for quotes and invoices. Eventually, we would like to expand this function to all of the main system player groups. • Working on the update auto increment page and function. • On the phone with Steve helping him out with a custom CSV (comma separated values) files that he needs to create. His skills are really improving on the code side. • Went over to my dad’s house to work with him on adilas videos and adilas commercials. We looked at footage, still shots, audio files, and options for voice over. We talked about options for laser focused training clips for adilas. It looks like I’m going to need to get more into the video editing and editing process (eventually). We talked about making adilas consumable. Almost to the pill or capsule level. This deals with laser focused training pieces. Lots of potential and tons of powerful tools. 20 miles. • Recording notes from loose pages and brainstorming on future developments for elements of time. Lots of good ideas for RFID tags and subs of time for packaging.

	AU 2075		Daily Ideas	3/17/2014	-I keep thinking about schools and some of their needs. I think about lunch cards, grades, student tracking, elements of time, document management, training, and other pieces. As a note, the school lunch card idea is the exact same as a gift card or pre-paid card of some type. That would be a great project to tackle here soon. -In our cups and plates model we may want to add a new cup or bucket for assigned or attached elements of time. Maybe make it bucket #10. Currently there are nine others. They are: 1. Main 2. Line Items 3. Payments 4. System History 5. Flex Grid Tie-Ins 6. Special Subs & Relationships 7. Photos & Scans 8. Custom Documents 9. Other Content 10. Elements of time (this would be the new one) -Some people may want a perfectly matched software system to their industry. Think about electricity. It can be used by tons of different industries. The electricity is the same. The way it is used varies drastically. Adilas is kind of like the electricity, everybody gets the whole package. -Worms and cans of worms. Every door you open could potentially be a can of worms. Tons of interdependent pieces. My dad said, “Hold the worms, more fish are coming!” Kind of funny. He has said that they, at their house, have things called “worm wars”. This is where they put a worm into the chicken pen and then watch the young chicks run around and have worm wars. Sometimes we think of cans of worms as bad things. That is not always the case. I loved how he spun the topic of cans of worms into fun and positive pieces. Good stuff! Focus on the positive.

	AU 2066		Daily Tasks	3/24/2014	• Emails. • Working on corp-wide settings for stock/units. Steve needs this for one of his clients. Fixed the new payee settings dealing with notes and default expense types. • Setup a new corporation for a new client in Logan. Light logo work and setup the corporation. This is my sister’s first account. • Emails and tech support. Long email for a company that is doing an industry specific live menu or shopping channel type site. • Went in to town to meet with a contact and my dad. She has done lots of corporate training and HR stuff. She has been a trainer for about 10 years. She would make a great consultant and adilas trainer. 30 miles. • On the phone with my brother going over the plan for video editing and work options. • A developer came over to my house. We got him new files and then spent a couple of hours signing off on his API code for Full Circle.

	AU 2085		Daily Ideas	3/31/2014	-My dad challenged me to go home and watch the Disney music video from Frozen called “Let It Go!”. Good stuff and very inspiring. It is crazy how much our fears keep us bound. So, I’m going to let it go! Game on! Let’s see what we can do! I’m excited for new potential.

	AU 2086		Daily Tasks	4/1/2014	• Added the April training sessions and training seminars to the main adilas website. • Recording notes. • On the phone with Steve talking about different options. We talked about funding, interns, projects, and sales. We are going through a critical point and things are going to be tight. Lots of potential and things lined up in the wings. We need to get more sales or have our clients and future clients help us fund these projects. There is definitely a squeeze right now but we can see the light at the end of the tunnel. • Talking with a developer and going over the new game plan. We talked about pay rates, hours, custom projects, future raises, etc. Our goal is to help supplement his hours with paying customer projects. • On the phone with my mom going over recipes and builds. We also touched on PO’s and invoices and how they play in. She is doing great. • Talking with a developer about new changes to the adilas game plan. Similar talk with this developer as I had with the other about hours, raises, and doing customer funded projects. • Talking with my wife about new changes and plans. • Working on Lynda.com training stuff. Watching videos and looking at stuff my dad has made to help with video highlights for some customer commercials (Highland Vineyard & The Mixing Bowl).

	AU 2087		Daily Tasks	4/2/2014	• Logos for companies. Changed a logo for a client. • Working with a developer on sign-off for the deposit photo gallery. • Small team meeting with myself and two of the developers. More work with a developer to sign-off on the deposit photo gallery. • Adding a help file link to the 3 strikes you’re out login policy. This will help users reset their own login attempts. • Prepping logos and images to send off to my brother. Sent him 3 logos. • New logos for a company. • Went in to Smithfield to work with my dad on customer testimonial videos. Working on final edits for the Highland Vineyard clip. It is a 3 minute promotional video on who they are and how they use the adilas system. The clip is looking really good! 20 miles.

	AU 2102		Daily Tasks	4/21/2014	• Posted our first client spotlight and client testimonial video clip online. The video clip is 3 minutes long and highlights Highland Vineyards out of Colorado. The video was edited by my dad. I also spent quite a bit of time working on permissions and drill-down links of the media/content project. Added the system part category to the sales tax by part category section. • Drove to Denver CO with my sister and one of the developers. Total mileage 1,651.7 miles. • Worked with Shawn on the vendor photo gallery.

	AU 2333		Daily Ideas	5/15/2014	-On the API, we may want to move the IP checks to individual pages. We could then use some of the other fields to even limit or block IP addresses. -API socket/connections: More on the wall socket analogy… what if you had a surge protector graphic… Then show all of the things that could be connected to it. Think of the possibilities…. (Sketches of a wall outlet or a power strip – please see scan in photo gallery) -“Sometimes you have to leave people alone so that they can learn (to learn).” – Rodney Mullen – Adobe Creative Cloud video. -On a similar note – Maybe God wants us to learn how to learn by letting us struggle a bit. He is still there but maybe we have to be left alone (out of his presence) so that we can learn. -My dad wanted me to check out a product called “Citrix Share File.” It is a media and file management system on a large scale. -I think it is interesting that media/content and files are holding more and more weight. I’m almost thinking that they, media/content and files, might end up being the next main player group to go with our other main 12 player groups. Very interesting! -The glove analogy – adilas intern: This relates to in-line custom code and special include files to get at or process custom code. Basically, the glove is the same (virtual page) but what goes inside of it may change. (Sketches – please see scan in photo gallery) – (Glove – same for everybody – page of code. Hand – variables or custom – custom includes to code)

	AU 2311		Daily Tasks	5/16/2014	• Went in to town to meet with a couple of guys from Bridgerland. My dad setup the contacts. The first appointment fell through so I just worked on logos. 30 miles. • Had a demo with a gentleman at Bridgerland Applied Technology College. My dad set it up and we had a great meeting. We went for 2.5 hours non-stop talking about the 12 business functions that we do. We flipped into multiple corporations and showed data, reports, functionality, etc. He had some great questions and I think we answered most of them – at least for this go around. Towards the end of the demo, the main Information Technology Specialist sat in and asked a few questions. We had a lot of fun and I think that both guys really enjoyed the demo. My dad was there for the entire demo. Today was his birthday and he was willing to spend the whole day with me. That is awesome! Thanks dad! • Recording notes and rereading some other notes. Went to a local park and updated my notebook.

	AU 2334		Daily Ideas	5/16/2014	-My dad – “This cloud software can handle 85-90% of any business. Any need, anywhere, any way you need it!” This is how my dad introduced adilas as he was talking to his friends at Bridgerland. It was fun to watch him work. -Digital media/content tied to eCommerce. This seems to be a pretty big need out there. I met a guy today that asked about this kind of tie-in. I’ve had a number of other requests for similar type pieces. eCommerce and media/files. -Function over fashion… That is awesome! At the right time, it will be super fun to add that fun GUI (graphical user interface) level. I’m excited about that! Yee haw!

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

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

	AU 2799		Daily Tasks	8/21/2014	Emails and writing POS (Point of Sale) tech specs. Emails, phone calls, and permission based tech support. Emails to Steve about doing numeric date indexing as a later project. To add it right now might make it hard to manage. There will still be time... Working on database stuff. Went in to Logan for a workshop on intellectual property like trade secrets, trade drivers, patents, trademarks, and copyrights. 30 miles. Went over to Bridgerland to meet with a guy from Garden City, Kansas. He was teaching a class on high level chemical processes for boiler and refrigeration stuff. My dad setup the meeting for us to kick the ball around a bit. Fun meeting. Recording notes in my notebook. I also gave a small adilas demo to the guy from Kansas. He wanted to see our website and product. Gave him a verbal quote of $2,000 for a custom piece and under $200/month. Working on the new database structure.

	AU 2825		Daily Tasks	9/10/2014	Recording notes in my notebook. Posting the new behavior tracking and teacher/student interface pieces online. Small help file graphic tweaks and light testing. Brainstorming notes and ideas of how adilas could really benefit teachers and educators. See notes on other pages. Lots of notes. My mind has been going nuts. On the phone with Steve talking about schools and teachers. Lots of good ideas. More brainstorming on ideas for teachers, educators, and students. Lots of fun, cool, ideas. We could really help these guys and gals out. I really think that we could help there! More brainstorming on schools, teachers, and educators in general. I scanned the five pages of notes and sent them to my dad and to another contact that has been helping with marketing and other aspects of adilas. I would like him to spearhead that little project. Working on help files for the teacher/student interface. Also modified a page to help teachers both add and view (access) data as quick as possible. Helped an intern with installing software on his new laptop. Paying bills and recording expenses.

	AU 2853		Daily Ideas	9/27/2014	BEAR 100 MILE RUN -It is raining outside and I'm sitting here waiting on some aid station workers to bring me drop bags from their aid station. This weekend, I helped my dad as we went aid station to aid station while helping out with the Bear 100 mile race. My dad was the aid station coordinator and took supplies to each of the different stations. It was amazing to see how many people it takes to make something like this happen and work. Under normal conditions, it takes 5-10 people per station. Under crazy weather conditions, it could take even more. My hat goes off to all those who help and make the event go. Some of the volunteers give between 2 hours to 48 hours. Some of the directors and captains give days and days leading up to, during, and then cleaning up from the events. It is amazing. -Because the Bear 100 is a mountain foot race, it has a number of semi complicated pieces. The aid stations each use and have Ham radio operators who help with communications. These guys help to check people (runners) in and out of the aid stations. They talk between the different aid stations and camps. They play a very valuable role in the overall success of the event. -I would love to use elements of time, inside of adilas, to help track the runners and data pieces that are needed. It would be really cool to handle the event, the registration, the data tracking, the event results, the check in/outs, the DNF's (did not finish), the DNS's (did not start), and also the virtual progress (in real time) of the runners. I think it could be a fun project. -We could use barcodes, events, checkpoints, mobile devices, radio data channels, eCommerce, elements of time, invoicing, CRM, etc. We've got lots of pieces, it would just be taking the time to put the package together.

	AU 2783		Brainstorming on 3D Operations and 3D Acconting	10/14/2014	This morning, Tuesday, 10/14/14, Brandon and Wayne Moore were on a morning trail run. The subject was what goes with time? Brandon came up with space and Wayne came up with money. When you put all three pieces together, you can actually get 3D Operations and 3D Accounting. In Wayne's direct words... (written in an email to his friend) "I think you will like his 3-D approach to Operations and Accounting. X = Time, Y = $'s, and Z = Space." Great early morning conversation - done while running and hiking in the mountains of Northern Utah.

	AU 2878		Daily Tasks	10/14/2014	• Emails on new permissions for invoices and limiting invoices to a specific salesperson. Also helping an intern with some css placement for a custom label job. • On the phone with Steve going over direction for the sub inventory and cost controls (packaging) section. The first hour was basically a pitch to head towards round two of elements of time as a virtual wrapper for all main system player groups. We did a GoToMeeting session and were drawing and talking concepts for over an hour. Really fun session. We used the graphics from 10/9/14 as a basis of our discussion. We also used the interactive map and the GPS core layout graphic to show flow and concepts. I had a lot of fun. 3D or three dimensional pieces were brought into the discussion. As a note, the 3D elements are: x=Time, y=Money, and z=Space. (Please see sketch on scan in photo gallery) o X – Time is on the bottom – it keeps running and may be broken down into years, months, weeks, days, hours, minutes, seconds, etc. o Y – Money flows upward or downwards – In business a point or trend that is flowing upwards is often a good thing (not always). Also, we want all monies to be tracked clear to the bank and financial level. Think of cream rising to the top. As a historical note… My dad is the one who came up with money as the y axis. That came from a walk earlier this morning. o Z – Space provided the depth structure of the items as they relate to time and money. Space allows for organizing, stacking, layering, packaging, combining, and separating. There are tons of things or attributes that may be applied to space. o Anyway, back to the telephone meeting, we used the last hour and a half talking about requirements for sub inventory and cost controls. See elements of time #892 in adilas or time #2786 in adilas university (developer’s notebook) for the actual brainstorming document. We spent a lot of time dreaming and talking about subs of subs, extensions, matrix, rules, and assignments, sub attributes, packaging, barcodes, space, etc. Great session. • An intern came over to work on the web/API documentation project. I helped him out a bit and tried to get organized. I started entering subs and elements of time to help us monitor custom code projects. We really need to do this. • Recording custom code projects into adilas – using elements of time.

	AU 2896		Daily Ideas	10/16/2014	-Idea from my dad while we were out walking… “Play at the wall.” – This deals with how we will allow outside developers to interact with adilas code and database. They will virtually play at the wall. This deals with API (application programming interface) sockets. -Other ideas from my dad… Treat the application like an electric wiring or circuit. All of the major wiring is done by the master electrician (programmer in our world). Once it is setup, a normal Joe is able to plug into the wall or power outlet. -When my dad and I were talking about electric circuits and playing at the wall, a couple other topics were: blue print reading or print reading (does the person understand the design or default flow). What standards are used? How does one read or interpret existing logic and wiring? Are there standard procedures or processes? If so, what are they and how can I get to them? -It is very tough to code to moving targets… Help out our future clients and developers by defining existing flow, wiring, output, and even code. -We need to fix the forgot password section. It should run great over our new API sockets. Currently it is built on older technology. Remember the glove analogy by an intern for handling custom code: - Same glove or page name - Any hand could go in the glove – any code could go into the page - I’d like to take this analogy to the next level… What is that level? I have needs to allow custom code, processes, and even custom output… - The glove thing, or whatever we come up with, will be used over and over again… Figure out a good solution! -On custom code includes... maybe define areas or sections and then allow those spots (places in the code) to be changed. This could be full page, navigation, headers, footers, body, sub body, etc. Basically, define the points where we allow custom.

	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.

	AU 2897		Daily Ideas	10/17/2014	Notes from a meeting with a potential client in Salt Lake City: - Extend the discount settings to both secured environments and customer facing eCommerce. Idea came from this potential client. - They (the potential client and his web developer) wanted to use quick css (cascading style sheets) templates to put a wrapper around the adilas backend engine. - Lots of talk about wrappers, skins, and getting things exposed as quick as possible. There was a definite element of speed to market. - They wanted options for both wholesale and retail simultaneously - They had questions about contracts and protection. Most of it was to cover them. - They wanted to know the quickest way to get up to speed. Once again speed to market and shortening learning curves was a big deal to them. - My dad and I talked tons about API sockets and mobile consumption of data (building apps). - We wanted to put my sister on this project. They asked for our best consultant and trainer. My dad and I both thought that my sister was our top pick for skills and availability. - While doing brunch, we had some pancakes on the table. We used the pancakes as a stackable object and then related to elements of time, phases, and even accounting. My dad wanted me to record that pancakes may be a good training image or object. Almost everybody knows what pancakes are and what they can do, be, have, etc. Fun stuff… (please see sketches in photo gallery) - Pancake sketches: Order, Cook, Serve, Top, Eat - Track objects and data over time (time, money, space, 3D elements)

	AU 2882		Daily Tasks	10/18/2014	• Phone call with Steve. Lots of talk about custom projects, new and existing developers, and internal needs. We talked a lot about basecamps and what we need to do to get there. • Emails and light tech support. • On the phone with Steve trying to get his computer up to date with new files, database values, and what not. • Emails, phone calls, and tech support. • Working on in-line discounts and applying a custom discount on each item in bulk. Basically, looping over an existing shopping cart and updating values. • On the phone with my dad… He is recruiting other developers and other connections and contacts. I sent an introduction email to a new client to introduce him to Steve. Sent him some adilas reading as well. More in-line discount code work. Working on the bulk apply discount page. • Putting the advanced backend accounting flyer up online for the training seminar at the end of the month.

	AU 2883		Daily Tasks	10/20/2014	• Working bulk in-line discounts. • Working with an intern on PDF barcodes. Also working with my brother on beginner HTML, tables, and links. • Went into Smithfield to give a demo to a prospective client, a manufacturer for inlaid glass in cement, tiles, and flooring. My dad set up the demo. He went with me. The lady had a number of questions all written up and went right down her list. I was impressed with how organized she was. The things I took away were: o The importance of eCommerce!!! o Templates for eCommerce o Product matrix or attributes – colors, sizes, etc. o A pay portal for customers o Automated credits and credit memos • At the end of the demo, they asked for a demo login. Not that this was the main point, but the deeper we go, the more we see that companies want easy to use, full features, and speed to market type features. Lots of requirements. 20 miles. • Working more with my brother on beginner HTML stuff. More tables, links, and light formatting.

	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!

	AU 2891		Daily Tasks	10/29/2014	• Emails. • Working with an intern and my brother. The intern was working on a custom PDF invoice and my brother was working on an intro to ColdFusion page. He was working with basic math and variables. • Working with my brother on variables. Working on adding two new system permissions. They are for my invoices – limited view per user and a new permission for a discount approver. This is a manager level permission to help with discounts. • Went in to Bridgerland to meet with a graphic designer about billboard and banner sites. Great meeting. We talked concepts and plans for just over an hour. Lots of little sketches about 3D world building, the data assembly line, API sockets and data ports. 30 miles. • Went to Preston, ID, with my dad to go to a meeting for the radio guys that helped with the Bear 100. Took a bunch of notes in my little green notebook. We then went to an ice cream Shoppe and talked about GPS event and race tracking using adilas as a backend engine with a cool and simple GPS app on the front end. Really good stuff and both my dad and I were really excited.

	AU 2892		Daily Tasks	10/30/2014	• New 3D domain names. Email to the graphic designer, my dad, and Steve about digital billboard sites. Purchased these new domain names: 3dassemblyline.com, 3ddataassemblyline.com, playatthewall.com, 3deventtracking.com, and 3dracetracking.com. • On the phone with Steve, an intern, developer, and myself. The first part of the call was talking about sub categories for parts. See notes later on. After the developer left, we did a session on custom labels and showed Steve how to tweak the label settings. An intern then gave Steve a demo on the custom labels and barcodes that he did for a client. After that, Steve and I worked together on in-line discounts. We spent the rest of the time coding and building while doing some teaching. Great session. • Emails and tech support. • On the phone with a marketing contact going over a new custom project dealing with electronic billboards and menu boards. The client wants to interface between his menus and our point of sale system. • Helping an intern with his web/API documentation project. Reworking 2 new banners for Steve. The banners are for a trade show in November. • Finished up the 2 new banner graphics and sent some proofs to Steve. • Reviewing feedback from the advanced accounting training class. A rep sent me a recap of the surveys that were turned in. • New logo for client. • A developer came over and we got his laptop up to speed and all updated. He will be working on the adilas API socket project and wiring up the wall.

	AU 2876		Daily Ideas	11/12/2014	3D Concepts of time, money, and space could also be stated as: timelines, budgets, and scope. Anyway, the terms used don't really matter... It still comes back to tracking objects and data over time. -X=Time, timelines, checkpoints, phases, stations, events, stamps, actions, reactions, cause and effects, histories, ages, aging, flow, milestones, periods, seasons, maturity, term, cycles, ranges, scheduling, dates, etc. -Y=Money, budgets, financials, balances, accountability, accounting, funding, cash flow, trending, profits, losses, assets, liabilities, equity, capital, revenue, cost of goods sold, expenses, forecasting, registers, etc. -Z=Space, scope, depth, levels, layers, stacking, adding and subtracting, multiplying and dividing, wrapping, covering, uncovering, organization, packaging, bundling, processing, locations, sub locations, moving or categorizing, types, subs, details, grouping, spreading, joining, chaos, order, etc. -What about establishing multi-point locations or geographic areas? Think of uni (1), bi (2), tri(3), quad(4), and poly(unlimited) points to determine a certain place, location, perimeter, boundary, or area. My dad and I were talking about GPS tracking and RFID tag tracking this morning on our walk. Anyway, a location or sub location may need to be defined further. At the same point, it might be nice to keep things general unless more points or details are needed. Maybe optional pieces if more is required. This might also deal with multiple naming conventions and an unlimited amount of locations and sub locations. -It might just be me... but everything seems to be going in a sub or small detail level. Most people don't want to stay there very long but they need that level of control. I think that it is interesting how we rolled out round one of elements of time... We have a build your own temple structure (point and click interface), we allow for types, kinds, functions, subs, etc. Each template is independent of any others. The report types are also interesting... We have calendar, time-slot, details, groups, build your own, and even exports to Microsoft Excel. Tons of options. I really think that elements of time is our most progressive system yet. And where we are headed is really fun as well. We want more tie-ins, more transparency, more custom interfaces, more ease of use, more options, and more functions. At the same time... we want simple, intuitive, dumbed down, and still lightning fast speed. It has to be all of these things. That's a pretty tall order... Well, I guess we know what the goal is... Now we just need to do it! Yee Haw! On the phone with a developer from Salida... Small ideas and future to do list: -Make a black box inside the shopping cart. It will be created and cleared just like normal. The custom code or settings (weight calcs, discounts, rules, etc.) will then be fully custom based on needs of the client and the developer. Basically, we will acknowledge that it is there but won't touch it other than creating it and clearing it. (Black box inside the cart) -On page level black boxes... Don't include an abort code. Let the developer leave it out to make the custom code transparent or have them add it to their page which will virtually take over or pass full control and display to their code. -We need a recalc cost method or function... Pass in the current cart structure line items and return totals and cart calculations. -Maybe think about using spreadsheet type documents as simple databases. They are quick and easy to update... however they are not as quick to be searched or as standardized as normal databases. We may need to pick and choose when to use what tools. -We need our own little mini spreadsheet or quick grid tool. Basically an app where you can create your own grid on the fly. We could do simple math, simple formatting, and be able to export out to a real spreadsheet like Microsoft Excel or Google spreadsheets. -Another idea is to allow custom mapping from adilas to a spreadsheet. This could be something like – put the item number in G4 or the price in H4 or the description in I4. Use rows, columns, and the laser focus and place data and hardcoded values as needed. -What if each spreadsheet was just stored as a JSON object verses a real database table. Basically, can make, store, and show a simple grid that the system can use and manipulate almost on the fly... (Sketch in photo gallery – quick grid tool, How many rows? How many columns?) -On all parts look-up’s add all parts and pieces. We need all available fields to show up for roll call. This deals with general inventory items and invoice line items. We are starting to use more and more of the other options.

	AU 2952		Daily Ideas	11/19/2014	-This morning my dad and I were walking on a snow covered trail. We could see lots of different footprints on the trial in the snow. My dad made the analogy that many different people (and animals) use the same trail but each has its own footprint. He related it to adilas and helping to build a virtual trail for businesses to use. Each business leaves its own footprint and many use the trail for different reasons. People use trails and roads because it is easier than bush whacking. -Steve had the idea to charge $17 per training session. That would help us fund that project. -We need to setup adilas eCommerce and online bill pay options for ourselves at adilas. We need to charge for new setups, training, custom code work, consulting, adilas world, and other events. -We also need to circle around and finish up the email and email confirmations section. -We need more options to schedule and take reservations for classes, training, and other events. We, as adilas, need round two of elements of time.

	AU 2941		Daily Tasks	11/20/2014	• Reworking the non-compete and non-disclosure agreement for a developer. He wanted a couple changes to allow him still to be an independent developer and work with other clients. Added verbage to include more flex and known grey areas. • Playing with the cfx_http5 custom tag and Cold Fusion extension. • Working with an intern on a Power Point presentation for our upcoming intro to Cold Fusion class. We were going off of an outline from 9/12/14 (see earlier in this notebook for details). • Went into town to have lunch with my dad and a GPS guy. We ate lunch and talked GPS (Global Positioning System) and GIS (Geographic Information System) stuff. Good meeting. We are working 3D even tracking and using both GPS and GIS data to support the time, money, and special elements of different events. 30 miles. • Working with an intern on Cold Fusion training. We worked on lists and loops. • Small team meeting with an adilas associate and adilas interns. We went over options for new developers and helping to on board new talent and skilled independents. • The associate and an intern broke off to talk about on boarding new developers and the other intern and I worked on code stuff. • Working on emails and going over direction with the adilas associate about project management and using adilas. We set up a meeting for next week to create a process for project management inside of adilas. • On the phone with a developer working on the adilas API stuff. He also showed me a screen sharing software called Teamviewer.com, good intro to the API general format.

	AU 2955		Daily Ideas	11/26/2014	-Small miracle this morning as my dad and I were on our walk/run. The roads were like bullet proof ice this morning. They were snow packed but it was warmer so they were melting. We drove up the canyon and it was so sketchy that we turned around. On the way back, we started to slide off the road towards a steep bank that went down to the river. Anyway, we were about to slid off the road and suddenly we were able to stop. We didn’t know how or why but we were able to stop. That particular corner sloped off the wrong way (downhill) and could have dumped us off the edge. Anyway, once we stopped we said a prayer. My dad then put the Jeep into 4-wheel drive low and we crawled out of the sketchy zone. We ended up drifting sideways down the next hill as well. Super slick. We made it out eventually to plain ground. We then put on some special foot traction devices and went on our run. As part of our run we ended back up the canyon by the hill and corner that almost ate our lunch. With the foot traction stuff we could walk on the icy road. What we found at the scene of our almost crash was pretty cool. We found a small rock that had been dislodged when we went into a skid. The rock had left a small grind path in the ice for over 7 feet. Basically as the wheels locked up the rock was in front or under the back right tire. It’s carve in the ice was the only visual evidence of the skid. As we looked at the scene, we couldn’t help but feel blessed. That little rock being drug under a locked up tire helped stop the vehicle from going over the edge. That same rock, most likely also allowed for the Jeep to get traction when crawling forward to get out of the danger. I am so grateful for a loving God that watches over us and teaches us along the way. I’m grateful for the Rock! (Sketches on scans in photo gallery) -I want to map out each tool as blocks. Break it into tools, sections, subs, and options… Similar to the plates and cup analogy but use blocks and wireframes. Blocks & wireframes: (sketches on scans) • Main items • Line items • Payments • Photos, scans, files, flex grid, etc. • Internal & External API socket options -As a note, a wireframe is a mix of both technical information as well as a visual representation of the data. It is very simple but helps to convey functionality, behavior, and priority of content. See Wikipedia – website wireframe – for more information. -A new personal setting could be what set of my cart favorite buttons to use. That would really help save users a couple of clips. Idea came from the Salida, CO developer. -Showing big picture to smaller sub details. Yesterday, I used simple drawings to talk with different people to show multiple different levels and how we deal with each one. These could be some great teaching analogies. Think big picture… clear down to smallest pieces and sub details! Huge to micro – go as deep as you want! See sketches in photo gallery: • Internet – Worlds • Servers – Locations, States, City • Databases – Highways, Streets, Roads • Tables & Queries – Traffic, buses, cars, motorcycles, etc. • Individual cells, data, and variables – Individual persons, drivers, passengers, pedestrians, etc.

	AU 2960		Daily Tasks	12/3/2014	• New logo for a client. Posted new logo and colors online. • Copying video footage to jump dives. Over 250+ hours of training footage per jump drive. That is awesome. • On the phone with Steve going over new updates and progress. He just got off the phone with a server rep talking about new servers and possible options for custom plans. We also talked about using video in helping to train new developers and new reps. Great resource. • Reviewing some pieces with an intern that he had watched in the training videos. • The intern and I were going line by line through a custom data upload document. As a fun exercise, we did a number of small or mini assignments to work on concepts. We even planned on paper before going to the computer. • Recording notes and burning videos onto jump drives. • Working on hooks, custom code options, and mini black boxes for cart alerts and promotions. Also had a tech support call on internal invoices for stock/units (transferring inventory from parts to a stock/unit). We also talked about shipping options for eCommerce. A client in Texas is the one wanting the shipping options. They recently started up a motor sports aspect and want to sell part online. I told her that we want to play. • On the phone with our client that does GPS tracking and with my dad. We did a GoToMeeting session. He showed us around the GPS world. I took 3 pages of notes. See notes on other page for details. • Working more on the mini black boxes (top & bottom) for the shopping cart. • Finished up the mini black boxes for the view cart page. Added a look-up for custom code and custom document assignments. This puts a button right on the view cart page to help users get to custom code as quick as possible. • Email update to Steve and the CO developer about new cart changes.

	AU 2985		Daily Ideas	12/3/2014	Notes on GPS stuff from a call with a GPS client and my dad: - Check out the company CalAmp - ESN numbers and Unit #’s – key id fields - States, statuses, and switches. These are things like speeding, how fast? Idling, how long? Stopped, how long? Mileage, how far? Driving, fuel usage, PTO usage, etc. - Tons of different sub details. Basically, we need to track dates, times, details, phases, locations, activities, and monies while doing different things that may range from sea to shining sea (long distances). - Landmarks, sub locations, areas, perimeters, boarder, etc. How many points make up a sub location? - Timing, histories, and intervals of actions or events. - Managers may only want to see units assigned to them. Admin may want to see all players. Fleet assignments. - IFTA or International Fuel Tax Agreement – This is huge for truckers and GPS tracking. State to state, sleep time, idle time, working but not driving, etc. - Full dispatch package, routes, estimations, gallons, price per gallon, reports, etc. - Google Earth is a great resources. - Mangers and admin want to see multi screens, quick snapshots, and activity of what is going on. - Tell the story - Leave and/or show bread crumbs – audit trail - Pull reports as needed… - Some of the drivers need access to the last 7 days of data. After that, it needs to be archived. - Most devices are coded by scripts or pulses that are sent to them. - Lots of divisions and sub divisions. Groups, sub groups, and subs of subs. - The phone # on the SIM card (Subscriber Identity Module) is super important. - He said that he used to be the kind of buy here, pay here. He wants back in that arena. - Texting, emails, web, API sockets, etc. – Lots of different communication levels. - Maps and quick visuals – show me, don’t tell me. - Maintenance servers and being able to manually ping the device.

	AU 3736		Brainstorming - GPS & 3D Event Tracking	12/3/2014	Phone call with GoToMeeting session with Barry & my dad (Wayne): - Barry & my dad - GPS & CalAmp - Gpsicu.com - Esa #____ - Vehicle ID - Vehicle name - Vehicle description - Odometer - Trip meter - Speeding: o Speed threshold – ____ MPH - Idle: o Idle Durations - ____ minutes - Stopped: o Stopped Duration: ____ minutes - Mileage: - Switches: o Switch input 1 • Estimated Fuel Usage: ____ gallons per hour o Switch input 2 o Switch input 3 (PTO) – • get to subtract this back out o Switch input 4 - Land Marks o Sub locations o Inter - Histories of the truck - Vehicle id - Name - Last heard (central) - Speed (mph) - Heading (degree) - Battery (volts) - Id 1 – unit # - Id 2 – ESN # - Intervals of action - Timing - Managers look after certain subsets – assigned to certain fleets - IFA – International Fuel A____ (not sure) - Full dispatch, routes, gallons, price per gallon, reports, etc. - Google Earth - Multi-screen – quick snap shot Reports: o Mileage by vehicle o Mileage by date o Places by vehicle o Places by date o Places by place - Tell the story - Bread crumbs… audit trail - Reports as needed… - Last 7 days current, then archive the data - Hours of service templates o Driving, working, stopped, o 4 roles: • Admin • On-service drive time • Working but not driving • Sleeping o Simple time - Pulse – code the device based on what is needed – puls.calamp.com - Lots of divisions and sub division, groups - Config scripts - Phone # of the sims card - Buy here pay here - Texting, email, web, API – different communication levels - Maps - Quick visuals - Manually ping the device - Maintenance server

	AU 2986		Daily Ideas	12/4/2014	-Keep flagging the trail! My dad and I were hiking this morning and we couldn’t find our war (new trail). The only way that we knew where to go was due to some pink flagging that had been tied to trees and branches along the way. Part of my job is to keep flagging this trail that we are on! Yee haw! -Invoices drive the process – Steve Berkenkotter -As things settle… Look into possible software integration through API sockets and gateways. Software can and is very powerful. It also interacts better with hardware than the web. Good stuff! -Keep building towards an open API interface and model. -Keep heading towards both internal custom code options and external custom code options. Make it consumable. Build a full on, open, business platform. -Copy the video files. Send them around. Get more jump drives…

	AU 3004		Daily Tasks	1/7/2015	• On the phone with Steve and a contact going over Washington State API stuff. Steve also wanted some direction on some label stuff. • More phone calls and tech support. On the phone with our Colorado developer going over new and existing needs and what not. • Emails. • Went in to Bridgerland for the first day of actual training. We are going to be doing four days a week with night classes three days a week. Our classes today were dealing with an HTML review and basic intro to ColdFusion. We recorded the classes and sessions using GoToMeeting. After class, we (my dad and an intern) did some rearranging of the classroom. My sister did the night class and did an adilas intro class. 30 miles. • Went by and met with my brother and a developer at their houses. I pitched a commission model for the adilas payroll section to the developer. Nothing was decided, but we are starting to talk about it. That would really help me out tremendously. • Went over to another friend’s house to help him get his laptops setup with ColdFusion. His computers were going slow so we talked and did some light training while we were waiting for the programs to load. We finally got it all working.

	AU 3601		Daily Ideas	2/5/2015	Back on 1/20/15 we were brainstorming on a project called round 2 of elements of time. See entries from that date for details. Anyway, when I was driving home, I started thinking about how we needed elements of time to advance the ball for our balance sheet and financial records. When I got home, I scribbled some small ideas on a post-it note and stuck it on my scanner. I’ve been meaning to record those pieces but have been slammed. Here they are: - Use elements of time behind the scenes to record daily records per categories. No other math other than the daily sums is needed. We will then pull reports based on those daily sums. Watchers and feeders. - The different categories will be updated and maintained as they happen in real time. This includes normal actions such as adds, edits, deletes, voids, etc. This is possible as most pieces are manipulated on a one by one basis. - There are tons of entries in the adilas university site on watchers. Search for the key word watchers. Some of the entries go back to 2008, 2009, and 2010. Things started getting hot in 2010. Lots of planning and mapping sessions were being done. That whole process was the prep and foundation for elements of time – round 1. We just ran out of time to get it all done. See specifically the entries for the month of October 2010. Interactive map, watchers, feeders, roll call, mappings, etc. - On the daily records per categories (watchers and feeders), these would be accounting level subs of time. They could be done daily per location as needed. The subs would only be added as something happens. Keep it small and tight. Simple sums would be sufficient. Relate the subs back to pieces of the financials. Use the P&L (profit and loss or income statement) and the balance sheet as the categories to keep track of. For example: part categories, revenue, cost of goods sold, expense types, deposit types, balance sheet pieces, taxes, receivables, payables, etc. - The goal is daily sums per location per category. The word category is kind of broad but record key pieces per day. These feeders could then be used to support and/or feed other reports including the P&L (profit and loss) and balance sheet. - I really need to get these records (my notebook) out to the public. There is a lot of good stuff here that could benefit the whole human race. The ideas, knowledge, and planning are free. Making it happen… that takes resources. See notes back on 1/24/15 about new custom black boxes for custom code. Today while doing a whiteboard session, we may end up adding other options for custom headers and custom footers. These would be more global type pieces but available if needed. The word global means more system wide vs. per page like most of the other custom code. Standard page inside of adilas – black box custom code options: - Top – full takeover or custom logic - CSS – Global or system wide - Top custom header – Global or system wide - Top mini – under the header - Main body black box - Bottom mini – above the footer - Bottom custom footer – global or system wide Be able to switch out any piece of a page as if it was a Lego building system. The page name would remain the same but the display and logic could be customized with no problems. -To take the black box concept even further… What if each page had options to use a point and click interface to show/hide criteria, custom naming conventions, change display order, and even add or subtract links, navigation, buttons, graphics, and even database fields. The extra database fields might need to be tied to the future project called real in-line extensions. See notes from 10/2/14 through 10/9/14. -I wanted to record a miracle… We’ve been working with new interns for over a month now. They are growing and developing some great skills. We are really excited about that. The scary side to that is how much it costs to get them to a level where they can play the game. Anyway, I was telling my dad and he asked me if I could get a loan or something to help bump these guys over the hump into a producing level. I told him that I didn’t think so… He immediately said – “Let me talk to mom and see if we could get you something.” You have to realize that my parents aren’t rich or well to do. They scrape and pinch like most of us. Anyway, I end up heading home, ran some errands, and finally get home. Later I get a call from my dad and he says – “Come by tomorrow and mom will give you some money.” They are planning on loaning me $5,000 to help bump the interns into a producing level. That will really help and is literally a miracle. I feel very blessed. I told my mom and dad… “I want to be just like you when I grew up.” I love how quick they give, serve, help, and jump in. They are and have been a huge blessing in my life. I’m very grateful!

	AU 3596		Daily Tasks	2/12/2015	• Working on the logic for bulk in-line discounts and discounts on a cart as a whole basis. • Went in to Bridgerland to work with the interns. My first project was to create a small list of projects that needed to be quoted. I then made a list of internal projects. After that a small list of already quoted projects. We will start chipping away at those pieces as we go. There are tons of projects. That is awesome. • An intern and I worked with another intern on signing off on his mini project. They, both the interns, worked on their first dynamic search mixing normal SQL with dynamic ColdFusion if statements mixed together. Powerful stuff. I worked with an intern on some code and data clean-up. He has really been very diligent, I’ve been very impressed. Lots of bouncing between pieces and things and different projects. Worked with interns. An intern and I spent an hour going over permissions and how things are organized behind the scenes. Great day with lots of learning and progress. 30 miles. • Talking with my dad about the new guys and what they are learning. He recommended that I have them work together on different projects. Let them build a good inter relationship. I enjoy talking and chatting with my dad. He has been an awesome cheerleader and example to me. I really appreciate that. • On the phone with Steve. We did an hour long GoToMeeting session to work on his code projects. We worked on custom page settings, black box includes, and cart alerts. Lots of new dynamics. • On the phone with a developer. We talked about the adilas API and different web services. He is a tech guy that loves to see what is hot and upcoming. He recommended that we keep going with JSON stuff but also check out a thing called AngularJS or Angular Java Script. I am grateful to guys who keep their nose to the air and watch for trends. That really helps us all be aware of what is out there and upcoming.

	AU 3746		Daily Tasks	3/12/2015	• Went in to Bridgerland to work with my guys. Started out the day working with an intern to see how his training is going. • I then worked with another developer to help restore his local database. Once we got that going we worked on World Building and splitting apart the main database. • Most of the day was spent with a developer working on looking over code and working together on his new code to copy and transfer full tables between servers using crazy dynamics and API sockets. Pretty intense. The developer came up with the plan. I mostly just helped with debugging and consulting type stuff. 30 miles. • Reading a letter that my dad wrote to a guy who is very good and GIS and GPS about 3D event tracking and plans to head in that direction. My dad is really excited about the 3D event planning and 3D event tracking stuff.

	AU 3770		Daily Ideas	3/24/2015	We have a number of requests to merge customer data. Basically, people end up creating duplicate records. They then want to clean things up. We may need a find and replace or some sort of merge function. This may end up needing some deep changes. Maybe use the find and replace parts section as a pattern. Customer data runs deep and touches multiple tables and sub tables. To help… start with these tables: - Additional customers - All inv - Corporations - Customer contacts - Customer history - Customer log - Customer photos - Customer queue - Customers - Elements of time - Invoices - PO invoice lines X (some number) - Quotes - Statements - Tie in flex grid - Etc. Also remember to change photo names and also check for generics with a main id and an app type id of 8. Check for the CMS media main, tie in flex grid, time sub assignments, and time sub pool assignments. -Along with merging customers and customer records. We have also had requests for merging vendors and payee records. Similar to customers… payees are used in tons of tables. They also have photos, media/content, flex grid, and time assignments. Remember tables that use main id and app type id 9 & 10. Number 9 = vendor/payee & 10 = employee. We may have to check both. A payee adjustment could run very deep. -With our community funded projects, how are we going to handle pledged or promised funds and monies? I think we could just add an internal payment and focus on operations. We could use a user-maintained balance sheet item to temporarily offset values as needed. Maybe I’ll do a pledged amount on GPS & GIS tracking for my dad and mom. I’ll go figure it out. -Idea from Steve… what if we used the existing page hooks right this second. Page hooks, meaning places that we could change the look and feel right now. We have plans to add 8-10 black boxes on every page. We already have 3 virtual black boxes on every page inside the secure side of the adilas application. Let’s use those to start with. This is 3 black boxes per page without any recoding of the site. -What if we used the session scope (after a valid login) and the chooser page to control corporation level settings as well as user level settings. We also have a personal settings page that could be used as needed. This could handle things like headers, footers, css stuff, skins, templates, custom pages, favorites, etc. Using the session scope, the custom header and footer black boxes, and custom settings could be awesome! -Small clean-up note… when editing customer log notes and elements of time (notes and sub comments) and their notes, maybe reconvert HTML break tags back into enter signs. That may help with editing for non HTML users. What this means is, we convert returns and enter signs (from a keyboard) into HTML break tags to help show what was entered. In order not to scare people, maybe un-convert or revert back to simple returns and enter sings for editing. That way the user doesn’t have to know any HTML or web code.

	AU 3757		Daily Tasks	3/25/2015	• On the phone with Steve going over the API socket pieces and what is needed and what is done. • Went in to Bridgerland to work. Spent some time with an intern on database World Building stuff. Helped another intern on some data migration stuff. Got another intern started on some code to help save report settings. If we could save some reports per user and per corporation… that would be awesome! 30 miles. • Conference call with my dad and a guy who specialized in GIS. We talked about apps, services, modems, SMS messages, cell and cellular data packets, and even options for GPS as a service. Great call. My dad and I figured out that GPRS modems were a huge key to the GPS data world. GPRS stand for something like… Global Packet Receiving Model… or something like that. Basically, it is a hub or modem that sends and receives text messages between GPS units, cell phones, and other devices that play in that world. He helped us with some great break-throughs. I was very impressed. See additional notes later on. • Helping interns on their projects. • Conference call with a client. My sister, two developers, and I were on the call. Great call and we had some good discussions on different topics. We talked about PayPal, skinning the shopping cart, distributing costs of goods sold, affiliate programs, email and text message blasts, and referral marketing. We briefly talked about site analytics and point systems. We committed to some deadlines and promised a written proposal of work that would be done. Exciting times. • Worked with an intern on some API socket documentation. I then spent some time with another intern doing customer migration stuff.

	Adi 974		GPS, GIS, & RFID tag tracking - Sub of Time	3/30/2015	First $5,000 paid in by Wayne Moore - Logan, UT. 2/7/15 Second $3,000 paid in by Wayne Moore - Logan, UT. 5/4/15 Third Calvin Chipman did some internal development out to a light demo mode Fourth: Josh Sagert did a google earth simulation tied in to cell phones.

	AU 3781		Daily Ideas	4/2/2015	-I want to create a flavor of “pioneering” & “innovating”. Maybe something like – Pioneering new trails through new terrain or something like that. I want to make it fun. It also needs to be okay if it isn’t done and perfect. Work boot style. -This morning I went hiking with my dad and my son. The trial was faint and somewhat overgrown. We still had a great time. Walking the trails in the morning really helps me out with my mental game. I love it.

	AU 3807		Daily Ideas	4/10/2015	-Keep remembering… By small and simple things… great things are brought to pass. Awesome advice. -The other day at church, I heard a talk by a gentleman. In his talk he was talking about how all we need sometimes is a little traction. He was talking about “Deer trail traction” and how sometimes even the smallest trail is enough to help maintain the elevation that we’ve gained. Anyway, my dad and I were on our morning walk and we were 100% on steep side hills looking for Deer trail traction today. It was amazing how much just something so small could help and even increase your confidence. Great analogy. -Add payee_id’s to user lists for eCommerce and 3rd party settings. Basically, an active username and user id (payee_id) are required to use the eCommerce settings and other API socket or 3rd party solutions. However, the payee id’s are not shown anywhere on the page. This requires us to educate and tell each user where to get those numbers and id’s. It will be easier to just build it into the pages and application. Make it easy and obvious. -On stock/units – we need an option to be able to search by a date in range. It would also be cool to be able to see inventory prior to or between certain date ranges. Kind of like year-end totals for stock/units.

	AU 3821		Daily Tasks	5/1/2015	• Working on the adilas.biz community funded projects. Trying to get something up and online. Sprinting to get the projects posted online and the new ads created and pushed online. Somewhat of a pressure cooker. Created a new page and two new graphic ads to say that the community funded projects were released. One of the ads had a guy’s set of work boots that were randomly tied together and duct taped. This was our starting ad for the community projects. Kind of fun. (duct tape, string, old work boots) • Went into Bridgerland to work with my guys. It felt so good to get the first round of community funded projects at least up and online. • I showed a developer and my dad how to add and subtract from the community list of projects. • I spent quite a bit of time talking with other developers about eCommerce and overall site structure and models. • I also worked with a developer on two different subjects. He is working on a software bridge to work between adilas and a pin debit card reader. His other current project is dealing with GPS coordinates and mapping things out using Google maps. Making lots of progress. • This was our last day at Bridgerland for this round. We have spent the last 4 months there using Bridgerland as our make shift office and group meeting area. What a blessing. I am very grateful for all of the help that I have received. Awesome stuff! 30 miles.

	AU 3861		Daily Tasks	6/2/2015	• More work on signing off on code for splitting up the invoices and invoice payments table. • Recording bills and invoices. • Went into Logan to work with my guys. • Worked with an intern to line out his custom code project for adding a city filter to the advanced customer queue page. • Worked with a developer on his saved settings for stock/units. • My brother showed me a fun trailer and vehicle website that he built. • Went over to Bridgerland to meet with some developers and my dad about GPS and GIS tracking. • Spent about 1.5 hours talking about our goals and dreams for GPS tracking and even tracking. • On the phone with a developer going over ideas for PayPal stuff. • Went over some email settings and flow on being able to send emails to customers using simple settings and a strategic button(s) or subpage. • Spent about an hour on the phone with a developer’s brother. He is a business consultant and has a fun product for strategic project planning. We may be able to integrate with him using API socket connections and other computer to computer type interactions. Lots of options. 30 miles. • Exporting some bigger logos for a custom invoice for a company. • Did some code sign-off on invoices and invoice payments. • Pushing on the sign-off for invoices and invoice payments. Lots of testing and debugging. • Finished up the main core cfc’s. Pulled down all of the custom pages and went through those pages on a page by page basis. Quite the process. Got too tired to finish…

	AU 3867		Daily Tasks	6/9/2015	• Checking on new code for both data 0 and data 1 servers. • Checked custom pages for changes dealing with invoice and invoice payments. • Went in to Logan to work with guys. After our stand-up meeting, I started prepping a file to allow the guys to play with the adilas headers and footers. This includes the CSS (cascading style sheets) for the look and feel of the system. • Basically, we are looking to upgrade and/or give our users options on how the pages look and feel. This will be the start of the header/footer/css competition. • I worked with different people on projects and ended the day talking with the project managers about adilas, the hub model, services, and how to do things to make the hub model or store ideas work. That was fun. We pulled out a laptop and looked right at numbers inside of adilas. We then talked shop and did some projections. • My dad came to visit with me today as well. We talked and chatted for a while about the Bear 100 race and what we could do for them using adilas. My dad then talked with some of the guys and looked and my brother’s graphics. Fun stuff. 30 miles.

	AU 3868		Daily Tasks	6/10/2015	• Emails and viewing a Ted talk by Simon Sinek. See notes above and on other page. • Updating the main login page. Took off a couple of ads. • Fixed an invoice bug and prepped some developer update files for helping developers migrate and update their local systems. • Went into the Logan office. I spent the first couple of hours working with a developer on sales, goals, and vision of how the adilas model works. We spent quite a bit of time drawing things out and going over numbers. • We also had a discussion about a hybrid independent model vs. a full traditional employee model. Good stuff. • I helped to rough out a project for an intern. We even got to start working on it. It deals with grabbing the last known RFID tag numbers for shopping carts that are restored to a cart. • I got another intern helping me do some prep work on the data 3 custom files. He was prepping them for the invoices and invoice payments switch and migration project for data 3. • A developer and I had a great meeting with a client. My dad brought them over to our office and we chatted for a bit. We spent quite a bit of time talking about concepts of the data assembly line and how that works. We also talked about concepts of systems and how to interconnect things together. They want a product demo tomorrow. 30 miles. • Went over to Bridgerland to meet with my dad and the Ham radio guys for the Bear 100 race. My dad and I pitched the adilas concept and tying in everything for GPS, automated data entry and retrieval, and custom searches and special interfaces. Good stuff, great meeting. • Recording notes, paying bills, and emails. • Working on custom files for the data 3 server. • Migrating and splitting all invoices and invoice payments on the data 3 server. Testing new code. This marks the completion of the project to split up invoices and invoice payments on all 4 data servers. Yea!

	AU 3869		Daily Tasks	6/11/2015	• Phone calls and tech support. • Went into Logan to work with my guys. • A developer gave us a demo on where he is at using the google API sockets and GPS data from a trip that he went on. • I worked with an intern on adding a new auto populate RFID tag setting. Lots of training on what is going on. • Some contacts came over and we did a demo for them. These are the guys that came over yesterday that my dad brought over. The demo included vendors, PO’s, items, recipes, builds, quotes, customers, invoices, and expense/receipts. This was about a 2 hour demo with lots of questions. One of the contacts does training and simulation models. He also deals with wind farm hardware systems. He is out of the Provo, UT area. • A developer and I signed off on code for a fulfillment and processing invoice flow and process. Good stuff. We cleaned up some code and pushed files live. • At the end of the day a developer, project manager, and I talked about a percentage back to adilas to help fun new developers as well as project management. We talked about a 10-20% managing fee on a project. That money would go to help with sign-offs, pushing files live, and all billing and follow-up for the projects. Fun but crazy day! 30 miles. • Emails and working with a developer on data import sign-off for some clients. We did a couple of phone calls and even jumped online for half an hour to do a GoToMeeting session.

	AU 3899		Daily Tasks	7/2/2015	• Went in to Logan to work with my guys. I had a 2.5 hour meeting with a developer going over ideas on models and how we could stack and grow this thing. See other page for some model ideas. • I worked with some other developers on mapping out a project to automate expense/receipts and balance sheet items. Lots of training and showing them they why behind the need. • I got on a conference call a developer, a client, and my dad. We went over the progress that we are making in the GPS world and land. Good meeting and the developer was able to get some new information. The GPS landscape is kind of random with hidden little pieces scattered all over. People are holding pieces and not sharing information very easily. Interesting! • The owner of the building where our office is, called me in to chat with me. He wanted to know what we do and what we offer. We had a great discussion and ended up filling up an entire whiteboard with drawings and sketches. We covered: dynamics, systems, player groups, functions, settings & permissions, rep models, server structures, 3D world building concepts, data assembly line concepts, stats, and even possible 3rd party predictive models for stats and other analytics. Great little meeting. • As a fun side note, Dave helped me out twice today by pulling me out of very long meetings. He pulled me out of the meeting with a developer this morning and with the building owner this afternoon. I kind of needed that extra help to pull out of those meetings that just keep going and going. Good meetings, just long… : ) 30 miles.

	Shop 3829		Virtual Post-It Note	10/15/2015	New sites for: Chris Scholle Chris Johnnse Dave Forbis "Foretech Services" Wayne Moore Concept based sign-off procedure-we need to build it. Reread the project management document. Budgets Plans Sign-offs Code review Timelines Client involement Communications Deployment Wrap-up

	Shop 2959		General	10/22/2015	10/22/15 9:00-10:00 On the phone with Steve. We talked about plans, developers, and where we want to focus. We keep coming back to the train track and railroad analogy. We just want to focus on and own the tracks and train. We don't want to own the market, the hotel, the bank, the school, etc. We want to focus on the data, storage, and processing. All of the other services are up for grabs. Also, we want to make sure that we keep an open model for that allows for a Hybrid shop. Search other notes for some ideas on the Hybrid Shop and Hybrid developer models. 10:00-10:30 Writing out bills, checks, and invoices. 11:30-12:30 Tis is more for the record vs. actual time stuff...I went into town to have a meeting with Bryan and Garrett for lunch. I was anticipating a business meeting to talk about the shop or talk about issues or something. When I got there, we met a Pizza Pie Cafe, there was a bunch of the developers there and they had already payed for my plate. We had a fun lunch party instead of a lunch meeting. The people who were at the lunch party were: Garrett, Will, Dave, Russell, Bryan, Nick, Lincoln, and my self. That was really fun. 12:3-3:00 working with Calvin on his bar code project. We also went over a driver license scan and parse (split-up) feature. I then worked with Garrett on some sub inventory logic and how to virtually draw a line in the sand between tracking inventory on a parent item vs. tracking inventory on a sub inventory level. After that, I met with Jared and my dad about tracking scrap items and selling things online. I then worked with Jared to see some of his YouTube video cataloging that he is doing. We talked about direction and returning and reporting on progress. 3:00-4:00 Recording notes, helping developers, trying to get caught up. 4:00-4:15 Working with Russell on some graphic layouts. 4:15-5:30 Emails, tech support, and signing off on code for Adam and his Hypur project. 5:30-7:00 After hour meeting with Dave Forbis to work on some quotes. We had a good session and even talked about some future direction from with the shop. Dave has some been a great internal leader and an awesome sounding board for me. I really appreciate all of his help and efforts. We finished the quotes and started talking about leadership and service. Dave has a ton of knowledge in those areas. 30 miles. 10:15-11:00 Finished up on the quote for Beaver Mountain Ski School. They want an online class registration process and application for their ski and snowboard school. This will be time and service based on eCommerce with elements of time, customers, invoices, and special mapping between classes and part numbers (services). It will also use the flex grid to tie things together.

	Shop 290		Working with my Dad	12/11/2015	Meeting with a new developer. Notes: Met with a guy by the name of Matt. He is going to be working with my dad on his industrial recycling. We met and talked and then I showed Matt some of the vision and where we are going. We had a good conversation about the data assembly line concepts and how to systemize things. He seemed to be pretty sharp and caught on really good.

	Shop 451		Adilas Party	1/14/2016	Come to the adilas party - here at the shop. We'll have some pizzas to share. Bring something to share and we'll go from there. Kids are welcome as well. Notes: We had a great turn out. Dave Forbis did most of the planning for the event. We had Dave and his niece, Will and his wife, Garrett and his wife, Derrick, Alan and his wife and family, Bryan and his wife and family, Calvin and his wife, Shawn and his wife, Daniel and his wife, Chris Johnnie and his wife and kids, my family, my mom and dad, and Shannon stopped by for a bit. We had pizza and potluck goodness! Some of the guys played games (farkle), some watched a movie (national treasure), and some just chatted. Fun event!

	Shop 1097		Meeting with my dad and his team	3/28/2016	Meeting with my dad and his team on how to use adilas to track things through the system. They are getting industrial scrap from big companies and then repurposing and salvaging things as possible. Basically a recycling center for industrial products and pieces. Big whiteboard session to help show flow. We had my dad, Matt, and Jon there to represent my dad's team. Good session.

	Shop 1273		Consulting Meeting With Pepperidge Farm	4/22/2016	Had a consulting and brainstorming meeting with Pepperidge Farm. My dad setup the meeting. He was there and so was a lady by the name of Melissa Vanover from Pepperidge. Melissa is the training coordinator for the new J. Victor Mahoney Training Center located at the Richmond, UT, Pepperidge Farm location. We spent the entire session doing brainstorming and whiteboarding. The subject was a LMS (learning management system) type flow and process. As we would fill up the board with notes, drawings, and concepts my dad would take pictures for the record. We had a great session and covered a number of topics. I really enjoyed helping to facilitate the session and got to help provide some direction. We went for hours and all parties were engaged. That was fun. We even got Melissa up at the board to help with the brainstorming session. Good stuff.

	Shop 962		Adilas world projects	6/28/2016	Looking over code that Russell did. We also planned a time to get together and do a big push on merging Russell's new ecommerce code and settings with the classic version of adilas ecommerce. We are thinking that this coming Friday would be a good day to start on that. We had to cut out a little bit early to help my dad move some stuff clear out in Smithfield.

	Shop 1000		Brandon out of the office all day	7/15/2016	Went on a hike with my Dad and Sister this morning. We went to the top of Flat Top Mountain in Smithfield, UT. It was about a 6.5 hour and 13.5 mile hike. Supper fun and very beautiful. At 2 pm I started doing some emails. At 2:15 - 2:45 pm I was on a zoom session with Russell trying to help him fix a small bug on the Adilas Market (adilas world). We made the change and then pushed up the new code. Russell's stuff is looking really really cool, I'm excited to see how our clients like it and view it. 2:45 - 5:30 pm - Cleaning up shop times, recording notes, and making small fixes. Changed a billing email address for adilas.

	Shop 1766		Working with Shannon	9/8/2016	Shannon came to Bridgerland and we had a small work session. We talked about progression and how to balance new vs. older more stable technologies. We also made a tech support call about a cross-browser issue with sub inventory templates. Some of those things get hard to trouble shoot because of browser differences. After that, Shannon and I went to a retirement party for Wayne Moore (my dad) there at BATC. Good stuff.

	Shop 1012		Brandon out of the office all day	10/7/2016	Went on an extra long hike with my dad this morning. We were doing trail maintenance and flagging a new trail. That was kinda fun. Later in the day I spent some helping Russell with some adilas stuff and printing a copy of the existing elements of time for adilas as a back-up copy.

	Shop 1013		Brandon out of the office all day	10/14/2016	Great day. I did some trail maintenance with my dad, helped moved some things, and small things around the house.

	Shop 1016		Brandon out of the office all day	11/4/2016	Took the day off. Worked up in the mountains on some trail maintenance with my dad. I then got a bunch of things done around the house. I did pay some adilas bills, but that was small(ish).

	Shop 1017		Brandon out of the office all day	11/11/2016	Spent the day up in the mountains unwinding. My dad, a friend, and I spent the whole morning working on a bridge and stream crossing structure. Lots of chopping, sawing, clippings, tying, and building. Super fun day.

	Shop 1018		Brandon out of the office all day	11/18/2016	Went on a hike up Maple Canyon, up in Idaho with my dad and a friend. It was 15-20 degrees outside with about 2-3 inches of snow on the ground. I then went shopping with my wife and little daughter. As a side note, I am amazed at the human spirit and what it can do and what it does. Amazing.

	Shop 2047		Adilas Time	12/12/2016	On a GoToMeeting session with Steve. We talked about direction and where we want to head in the coming months. We also looked over the adilas YouTube media/content player, we setup a cannabis specific site (just the folders and rough structure), and we also talked about training events. Steve would like us to strip off the code from the https://data0.adilas.biz/top_secret/community_funded_projects.cfm page and start being able to collect monies to help with daily training events. We also talked about how my dad volunteered to find us venues for our training classes. Shannon got on the call. We talked about some progress on the videos that she, Dave Forbis, Russell, and Chris Johnnie. Shannon showed us the link to the current google drive videos. https://drive.google.com/drive/folders/0B7QkXlJmb-PSeGRMZF9jbG10ZEE We talked about the difference between in-person vs. webinar (web based training). We are seeing the need for the live sessions (they enjoy the connection with the people). Who, where, when? We need to offer the live events, even if they aren't fully attended. Build out the adilas university video library and the user guide. Make it easy to use and help train the trainers there. One of the unknown values is how do you help someone to stay on and keep going. Shannon mentioned Dave Forbis and Shari O. as up and coming helpers for tech support stuff. Also, Nick and Alan (both developers do have some great teaching skills). I could also be more a consultant and trainer type person. One of the major challenged is how fast things change. We shoot a video or write a help file and then things change. How do you keep up? What a good question... We have some great users... that is good and bad. We also don't have any standard certifications and/or train the trainer type stuff. Some of these people have some major skills but might be liabilities on the other hand. What about the adilas marketplace and the adilas university? We may be going too fast for our own good. What would happen if we totally slowed down and sell what we have? We build and build but are somewhat unable to slow down and tell people what we have to offer. What is the master plan? Do we already have it written down but just need to follow it or do we need to redefine it? We are seeing a change in the way that the system flows... We are getting more API socket calls, we are getting shortcuts, we are seeing more black box stuff, more developer specific code. We need to tell Shannon and Shari O. Who is going to do this new training? We may need to recruit who made it to help do the training. Make that part of the process. Slow things down a bit. The developer's notebook is kinda splitting now as well. We have elements of time in adilas university, adilas, and in the adilas shop section. How are we going to bring all of that together. We have things fracturing and splitting all around us. That is part of the game, we need to allow and accept that. How are we going to deal with that? Sustainable pace - slow and steady wins the race. Maybe keep looking at the process and judge the pace and needs accordingly. People have the potential to let you down. The only person we can truly trust is God. We can then give trust to other people. Make him your main stable anchor and then extend to others. If all else fails, then the sure anchor will still hold fast. I would rather be a trusting person and then be betrayed vs. not being a trusting person from the get go. Quote from Shannon who got it from an apostle (lightly tweaked). We are looking for a loyalty and commitment level of sorts. We do have to be picky. It comes down to a balance and a relationship. Take your time and start to build from there. Relationships take time. That is ok, build it everyday. We make the choices and strengthen and exercise those choices everyday.

	Shop 2727		Demo with Caisson Labs out of Smithfield	9/1/2017	Went into town to meet with my dad and to do a demo for Caisson Labs out of Smithfield, UT. They are a manufacturing company that deals with cell cultures, bio-chemicals, microbiology, media, plant biology, etc. They buy raw products and raw chemicals and then produce and build bio-chemical type products. We met with their team and they had 8-10 key players at the meeting. We first met in a conference room and briefly talked about some different things and they had a number of questions. I then handed them a world building graphic and then worked from the whiteboard to help educate them about some world building concepts and data assembly line concepts. Lots of good conversation and ideas. See attached for a copy of the world building graphic that I was using. I'm not sure if it has been uploaded or not before. After that, we went back in their production area and had a look around. The main owner and a couple of his people talked about their general processes. I took a page of notes and they gave me a copy of their excel spreadsheets (for one product). I also got a number of business cards and some custom labels that they are printing for their products. See attached for the notes and other documents.

	Shop 3050		Adilas Time	10/3/2017	On the morning GoToMeeting with Steve. We were talking about how quickly we could do a patch job for mini conversions. This is just a quick patch, not the real deal. Basically, you could create a new small table. The new table would have an auto id, a corp id, and the stored QR code value (text entry with a max of 50 characters or a varchar field). The QR code values would be in this format: qr_7777_77_7777 where it follows this pattern: "qr_subId_price_weight". The new table would use the auto id as the new barcode value. We were talking about the ^ (carrot sign or symbol). Say something like: ^27 or ^3555. The barcode would be that value. We would need a special page to take off the carrot and then look up the QR code value. It would then translate what was needed and pass it to the normal QR code page that Steve and Danny created. This is a simple way to use a standard barcode (smaller than 15 characters) and have it do the same thing that a 50 character QR code could do. The other things that were important were which pages to add code to help intercept the barcode searches and what pages to put links out to the new barcode generator. Steve took some notes and some screen captures of what we needed to do. Bryan Dayton and Steve will be working on this project. Both have already done some prep work and such. Steve built the original QR code page and Bryan has a small JSON object solution for storing and looking things up. The new patch would be to take that (both Bryan's and Steve's) code and make it into a new small mini table and a couple of pages to get the job done. We also talked about a number of other fun things on the horizon. These are just some small notes to help us remember what we were talking about. - We are excited to be working with Calvin and seeing what kind of fun internal 3rd party pieces we could come up with. We could do a texting service, bulk labels direct from adilas, exports to CSV files, and even getting back into GPS stuff. We talked about a bunch of options and even lessons learned from past projects. - We've got Alan back on with the database project - We've got Wayne working with the new frameworks and model view controllers (MVC's). - Bryan with custom projects - Russell with other projects, design, internal and project management - Nick small black boxes and icon menus - Steve made a comment that we already have a great popsicle. We just need to make it easy by putting it on a stick or on a popsicle stick. The easier we can make it, the better. It needs to have tons of functionality built-in behind the scenes... if we can make it look and feel easy, then we really win big. Keep it simple and easy. - Another comment that Steve made as he was talking. This one came from Kelly Whyman, an adilas consultant. "The sales taxes and tax pieces must be like the nervous system in the body... it goes through everything." We loved that the comparison was to the body and how things work. Wayne Moore (Brandon's dad) has made similar type analogies comparing body system to internal adilas systems. You could make some analogies that way. Think of the skeletal system, the nervous system, the digestive system, the endocrine system, the whatever system... It could be really cool to take it out to that level. - Steve was also saying that the key to keeping things going is delegation and training. We then let each person keep improving their own processes and such. - One other topic was dealing with possible look-n-feel/functionality of a one pager with multiple feeders, tie-ins, and even asynchronous loading and variable visual displays. Think of dashboards, drill-downs, charts, graphics, placeholders, movable pallets, expanding windows, etc. Thinking about future options and where we want things to go. Good session and lots of fun ideas and such.

	Shop 3261		AFB Time	11/28/2017	On a Zoom session with Russell. We merged in some code, talked about some projects. As part of our conversation, Russell gave me some advice on a past project from the Shop era that is still outstanding. Here are a couple of my notes to help me remember what he was saying: - Make a list of what is still needed. - Make a list of what was promised. - In the future, try to go more with estimates vs. a full bid or set price. - Figure out how much it will cost to bring the project all the way to completion. - Reset some budgets and try to stick by them. - Have a meeting with the client. - Figure out where the communication gap was and/or managing expectations. - Rebid or re-estimate if possible. - We may have to do some matching of funds. - We need to educate our clients about feature creep and how that affects timelines, budgets, and expectations. Later on, I was talking to my dad and Steve and they had some ideas as well. These are from my dad and Steve (I talked with both of these guys on 11/29/17 - the day after the initial talk with Russell): - It might be worth the time and money to setup a face to face meeting. - Maybe take Dave, Alan, and Russell. Each of these guys has and/or brings a certain flavor to the table. - Be a peacemaker. - Adilas may need to fund some of the development or I may need to do it myself. - At the same time, it takes money and we may not want to jump in and save someone. - We don't have a crystal ball to see if this company is going to make it or not... there is some risk there. - Using our top developers and guys, there is a cost associated with that including opportunity costs. - If you look at other projects, they have much bigger price tags on them and there is still no guarantee that things will work out perfectly. Steve had tons of examples of big projects that have failed, even with millions of dollars invested. - Even if you paid more money, is it enough to get you to first base? What will it take to get all the way home? These things tend to grow and grow and need tons of maintenance along the way. Usually, it is not just one push and your done. - We need to meet and figure things out. - See elements of time # 3273 for some notes between Brandon, Alan, and Dave Forbis talking about this project. Towards the end of the session, Russell and I spent some time and looked into the AFB employee time clock app and started in on a small code review. We weren't able to finish due to time.

	Shop 3382		Adilas Time	1/11/2018	No adilas work was done. This ended up being a private meeting in Logan with David Ashby and my dad - USFS (US forest service). Talking about options for trail maintenance and volunteer options.

	Shop 4891		Adilas Time	9/10/2019	Steve and I talking about projects and priorities. More and more pressure to get organized and get all hands on deck working in the same direction. Right now, we don't have a shortage of able body hands, we are just all over the place. We have guys on this project and that project, we have others on custom work, we have other on core projects, we have others that we don't know where they are at. We really want to keep focusing on the list, and adilas tick list. Along those lines, we setup another meeting with Cory for Thursday to keep going over the list and making adjustments as needed. From Steve - "Not a lack of work... there may be a lack of organization." Steve was also quoting my dad, "use technology to help you as you go along." Anyways, we were talking about how hard it is to control certain timelines and the pull of other projects (almost distractions of sorts). Eric popped in and had a few questions. We setup some time later this week to work on special accounts (rewards, customer loyalty points, gift cards, etc.). Some times budgeting time to work on certain projects, with mixed participation, really helps. Some times if I plan time for me to work on a project by myself, it seems like a softer schedule than if someone else is committed to the same time. A buddy, on some of these projects, really helps.

	Shop 4896		Adilas Time	9/16/2019	When I got on the morning meeting. Steve and Dustin were talking about their projects and times that they could meet up and work together. They have become a great little team. That makes me really happy. Below are some notes between Steve and I. We were talking about some upcoming meetings with both Russell Moore and Jonathan Wells. Both are designers and graphics guys. - Graphical homepages (graphical mini dashboard per main 12 player groups), custom dashboard with little widgets that could be moved around and configured per user, mix and match pallet (mini windows - movable and dockable) - We would like to look into what it would take to build on a JavaScript framework. There are multiple frameworks out there, what does that mean, what does that look like, and how are the pieces managed between the different systems? Lots of questions. - Projects for Russell - He could work his magic on the corp-wide settings page, 3rd party solutions page, help out Alan with the invoice due date project, and help us get more data tables in place and integrated into the system. - Getting help from Russell on some of the snow owl theme settings for some of the older AFB headers and such. There are a number of knowns spots. One is the adilas community funded project, the snow owl theme settings, the ecommerce settings, the custom email settings. - Looking at resources and what do we want to spend on what and how quickly could those expenditures turn around and produce some results. - We talked about consolidating our ideas and projects, using the adilas community funded projects page, report, and section. We could used it for project management, reports, progress, and a centralized location or hub for developers, clients, reps/consultants, and others. One spot will all of the updates and progress. - There will always be ongoing development, product refinement, and what is coming (future). The system keeps morphing out in front of us. Sometimes that is hard to predict. - Help prepare our users for impact - this is a huge system with tons of branching options and paths. - Keep working with Jonathan on putting together a list of what adilas can do - whitepaper/graphic/map - Getting it all organized - a virtual road map - big dumb animal pictures - this would help so much with sales. - Helping Jonathan get more system training from myself, Shannon, and Steve. The more training that he gets, the more he will be able to start pulling all of the pieces together. We would like to keep him on the education and sales side of the equation. - Permissions homepage and how we simplify that - currently, it is kind of a monster or as my dad says - a football field of permissions. - Mapping out the system functions and what is available. Steve wants a map the adilas world - what do we have and how is it organized - scroll as needed - zoom in/out - etc. Use this as a training and sales tool. - As we were talking about mapping, we jumped into some of the existing adilas maps and navigation interfaces. We talked about the adilas interactive map (vintage around 2010 ish), the GPS core interface (vintage around 2013 ish), and helping to bring that dream to life. On the newest version of the GPS core graphic, we have included some sub navigation dealing with permissions, settings, training, etc. For the record, currently, that graphic is just a small mock-up of what it could be. The real intent was to use that core interface to interact with different app modes. They could be things like data/work mode (what do you have), permissions mode (who gets to play), settings mode (how does it work or function), training mode (what can I do), usage/stats mode (show me what I've got). Anyways, some cool ideas already exist. Maybe help Jonathan keep going in that direction. - Use the map and be able to show what new trails are coming. Steve would also love to tie the upcoming pieces out to the adilas community funded projects to help with eduction, funding resources, progress, and a centralized hub for all of our projects. After our meeting, I spent some going over emails, recording notes, and getting caught up. Today is Monday, back at it again. Part of my process this morning was recording some notes from a couple of meetings we had on Friday. Lots of moving pieces. I'm so grateful for pen and paper and being able to scribble things down quickly and then fill things in later with all of the details. If it weren't for paper and pen, I wouldn't be able to remember enough to fill in the gaps. Great little tools.

	Shop 5209		Consulting	11/13/2019	Went into Smithfield to work with my mom and dad on a business called Moore Repurposing. They basically get donations and then take the items and try to sell them and/or repurpose them. They are going to be using adilas as their backend tracking solution. We spent some time talking about what is needed, how things will work, and some other overarching goals. We then sat down at the table and started writing out a virtual checklist to help them know what to and how each thing tied in to the bigger puzzle. Super fun couple of hours. We made a to do list and then started working through some of the pieces. Lots of our work was done with paper and pencil/pen to start with and then we moved to the computer once we had a plan. Good stuff.

	Shop 5900		Ecommerce training	1/29/2020	Went into Smithfield and helped setup my dad and MaKell for doing PayPal and ecommerce. We did about an hour worth of training.

	Shop 6056		Adilas Time	3/5/2020	On the meeting with Steve and Danny. Going over small items, projects, and new changes. Lots of moving pieces. Steve was showing me a shopping cart demo done by Spencer (outside developer) and how cool it was. Web link - Adilas/Main_GUI.html - demo page for the short and sweet cart Steve was also showing me some of his cross-corp (enterprise level) vendor mapping project. It is looking good. We talked about a few tweaks, but making progress. After Steve left, Wayne joined the meeting. We logged into some of the remote VPS servers and made a few changes. He also helped me with my local box, as it was running slow. While rebooting my local machine, I called and talked with my dad. He has done some grant writing in the past. I briefly talked to him and asked him if he would be willing to help me and play that game again. He said yes and we'll set something up. Fun stuff.

	Shop 7380		Projects	2/2/2021	Meeting with Craig and Steve to go over finances, bills, ideas, and direction. The meeting started out with just Craig and I. We went over a bunch of things and then Steve joined us later on. Craig brought a fun flavor to the meeting. Steve and I have hashed over some of these things so many times, we kinda get jaded or set in our ways. It was nice to have a fresh view and someone who would pose hard or uncomfortable questions. I really enjoyed the meeting. All of the meeting notes are on Brandon's computer. Here is a small portion of them. - We need to find the balance point - not running faster than we are able but still pushing it - We have been spending some monies on certain projects - we really need to get a return. For example: Research on AWS (amazon), R&D for fracture, WanderWays, SEO - Funding options - The main 3 are: sales, borrow, investments - Steve was saying, we have two main choices - steer towards deployment and fully funded projects - sell stuff or pull back and just do what we can - head back into smaller waters - slim down and tighter budgets. As a side note, we even talked about cause and effect if we were to actually gain from a small dip... lose some weight. - Failure to launch - this is a problem if you never get off the launch pad. - Picking our battles - There is need for what we do - Dealing with charging for our services - $65-100/hour - Trying to sell a new car but it keeps having issues - makes it hard to sell - people are willing to pay more for certain products if they are reliable - Fixing the servers - question: do we need more money or what to help make it better. On the positive side, people really use our products and they hit it hard, we really push the servers that we have. It's not like nobody uses it, the opposite is true - people throw everything that they have at them... we still need more. - Maybe stop development - we need to sell things - harder done than said... - try to switch gears - cross training - maybe change the word or phase sales into networking... connecting the dots - get some more hunters out in the field - swap people around - focus on the deployment and setup process - focus on funded projects - on the dev side - Being able to say "STOP" - Learning when to put our foot down - limits and levels - Selling the current 2021 model - Switch who we are targeting - trailer dealers, bowling pro shops, etc. - sell what we have to offer - It's just a $100/hour - managing expectations - sometime people want a perfect number or a nicely wrapped quote or project cost. It's just $100/hour. Otherwise, we lose our shorts. - We get pulled off on tons of outside distractions - external distractions, custom projects, and outside 3rd party solutions - The code is splitting - new school, old school, high tech, low tech, etc. scripts, tags, functions, includes, different styles - Having a real game plan - we really need this - a full plan and then let everybody know about it - Fracture is a real word - a life style - part of where we live and breath - keep heading in that direction. As far as we can see, things will keep fracturing. Plan on it and build accordingly. - Like race car driving - we need a good driver, but maybe not the best driver, especially with an attitude, they may need to go - You can always fill a spot... (even in management) - like a bucket of water, if you put your hand in, then pull it out, it will fill back in - finding that range that fits - There are multiple battles - in front of us - Using a talent scout, like my dad - maybe look around at the college (talent just getting out of school) or for people who have the skills - draft - Find and gather up the low hanging fruit

	Shop 7631		Demo	3/10/2021	Went over to my dad's house and gave a guy a demo of adilas and what we do and can do. It was fun, we ended up talking quite a bit about potential and how this product could be used in so many instances and scenarios. Good meeting.

Showing 150 of 171 Page 1 of 2 :: Go to page ::

What's New

Products

Find Us