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 - (852)
Showing 150 of 852 Page 1 of 6 :: Go to page ::
Photos	Time Id	Color	Title/Caption	Start Date	Notes
	AU 2430		Daily Ideas	2/22/2008	Meeting with Steve on 2/22/08 - When doing a quote – allow for a trade-in without actually stocking it in – year, make, model and trade value - Make sure taxes are figured correctly - Might need totals in a table similar to allinv_final_numbers Customer server-side write-up system: adilas - All Data Is Live And Searchable - Inventory - A/R - A/P - Payroll - Income/balance All Data Is Live And Searchable – ADILAS Questions: - Who, what, where, when, how? - Who are we? o Steve & Brandon, LLC, entrepreneurs, business owners, online application developers, custom write-up system developers, online solution providers - What is it? o One stop shop for all of your operations and accounting needs. We offer a system where you can empower your people in the field, where the actual action is taking place, to do the work (operations) that provides the number for accounting and financials. o Empower the end users and then check it along the way o Enter it once. If it is okay – let it flow through. If it needs correcting, change it and then let it flow through. o No limits, track your inventory in two different ways • Specific units – recorded and tracked on a one by one basis • General units – recorded and tracked as general inventory o Tie it all together o Take things all the way through the process and only enter it once. o Imagine: you can stock in inventory, record payables, track inventory and aging, photo galleries, quote, sell, invoice, age receivables, deposit money, verify bank statements, show income statement, etc. o Imaging: scan bill/statement, create check request, record payables, do employee/vendor reimbursements, print checks, age payables, verify bank statements, show income statements, etc. o Run full payroll functions • Hourly – digital time clock • Hourly plus overtime • Hourly plus commission • Commission only • Salary • Salary plus commission o Track PO’s, Inventory, Payables, Expense/Receipts, Reimbursements, Quotes, Invoices, Deposits, Bank Statements, Financials o By appointment only – we provide an adilas rep to help set you up and handle any training needs o Month to month – no contract o Multi-location and multi corp o Unlimited vendors, customers, payees, employees, locations, inventory items o Enter once – use multiple – one to many relationships o Custom write-up with customization available per corp o Security stuff o Build your own reports o Flexible search interface o Custom look & feel o Permission based (flexible & multi leveled) o Real-time virtual accounting , double entry accounting o Compare to online banking o Remote access – see your numbers while you are on the road

	AU 3563		2010	1/1/2010	YEARLY ACCOMPLISHMENTS 2010 Steve, This is a list of things that happened and accomplishments made during the 2010 year on adilas. It was a great year with tons of great stuff. If you need more detail, just let me know. I have everything documented down to the date. January 2010: • Brandon and Andy created their first video tutorial. It never got published but it was a 4 minute video on using the adilas shopping cart. • Small face lift to the main adilas.biz site. Added the cloud background. • Created a number of new flyers. Added options for dynamic name and contact info. • Lots of brainstorming on marketing, what do we do, and how can we get it out to the people? • Came up with a new slogan: Your date, you cache & retrieve it, we secure it. • Prep and research for the dewy decimal system. • Encoded sensitive database fields for storage. Examples: bank accounts, routing numbers, customer and employee SSN’s, driver license numbers, EIN’s, and usernames. Passwords were already encoded prior to this. • Added a forgot password helper page. February 2010: • Added a multiplier for the recipe/build prep page. • Added the add as advanced PO line item page. This page allowed for mini conversion calculations during the add line item process. • Added new PDF forms. 1 for Texas and 2 for Colorado (paperwork). • Posted the first round of the dewy decimal stuff online. Hundreds of files were updated. • Small fix on internal transfer invoices. Added current costs to items. March 2010: • Added units of measure to parts, PO’s, invoices, and quotes. • Activated corp-wide settings: show bin numbers, show unit of measure, and show line item numbers. • Steve loaned some money to adilas. Thanks! • Added a sort order option to PO and invoice line items. Included a bulk sort page for changing multiple sort values at a single time. • Added code to help automate bad debt payments. • Added the profit and discount calculator. Linked up the profit and discount calculator with the loan payment calculator. • Brandon and Andy worked on some marketing ideas. • Added a tools and features list to the main adilas.biz homepage. Also a small scrolling flash movie with the features. Most of the ideas came from Brandon and Andy’s marketing sessions. April 2010: • Added special line item settings to the corp-wide settings. Over 100+ fields. Things like: Labor, Supplies, Other, Collected, Fee, Dealer Handling, Discount, Freight, etc. • Added a merchant processing prep step to help speed up the transactions. We were experiencing long wait times (every once in a while). • Added a grouped customer log report. • Added the profit percentage to the global parts mark-up tool. • Added a price helper field to the add/edit number page. Local java script to help with profit margins, mark-ups, and pricing. • Added a price switch to trailer and toppers. They were always a mark-up value and we added options to choose between a list price and the mark-up value that was calculated on the fly from the basis. • Applied the stock/unit price switch to all stock/units and made it part of the global stock/unit mark-up tool. May 2010: • Created the mini invoice or 3” customer receipt. • Added the last 4 of the credit card numbers to the payment notes for reference. • Tons of time working onsite at an adilas client’s. Great ideas and training ground. • Added the barcode generator. Added page tie-ins and posted a free barcode generator on the main adilas.biz homepage. • Added a recalc taxes switch for invoices with multiple locations. This is an after the fact deal and allowed for items to be pulled from one location and then flipped to another location. The taxes would be recalculated and invoice values changed. • Added the financial flow calculator and worksheet. June 2010: • Spent more onsite time at a client’s (on and off throughout the entire month of June). • Added a new tax category called “With Tax Included”. This helps back into a bottom dollar value. • Added a discount calculation option right from the profit and discount calculator page. • Added a printer friendly link to the printable PO page. Took off all of the extra navigation and quick search info. • Lots of new corp-wide settings. Added the barcode quick cart, quick cash checkout, number of payments on checkout, customer web settings, show/hide prices, web return address, and barcode label sizes. • Changed all of the disabled/helper fields to a light blue color with black text. The old way was a white field with a light grey text value. The new fields stand out and are easier to read. • Added the PO quantity to the add/edit parts page. This is really handy when adding new parts from within the PO line items mode. • Added the apply quick discount to the edit cart line items page. • Added the auto calculate change due setting. Recorded the info and helped show the actual change due. July 2010: • Brandon and family moved from Salida, CO to the Logan, UT area. Salida was the birth place of adilas.biz application. Spell Salida backwards… you get adilas. (2001-2010 9 years) • Added tons of new details to the grouped daily/weekly reports. Showed tons of new break-downs and details with drill-down links to underlying data. • Added a corp-wide setting to help limit and/or open up location specific inventory tracking. • Major push to activate all existing corp-wide settings. Didn’t actually complete until August 2010. • Added the key word “All” to all of the quick searches. August 2010: • Combined a push on all of the corp-wide settings. • Added external customer PO #’s to invoices and quotes. • Finished up the basic corp-wide settings. In all, updated and changed over 700+ files in all. Files were from the main adilas.biz site, secure backend, data components, web/customer files, etc. • Did some page clean-up and added some CSS (style sheet) changes to every page in the site (while checking for corp-wide settings). Tightened up the overall look and feel of the application (minor changes to the eye but helped to standardize code and flow). • Added new drill-down links to the history homepage report. • Created the mini version of the daily/weekly report (3” format). September 2010: • Added a corp-wide setting for specific unit names. • Added a new global find and replace part number feature or tool. • Added the first round of the advanced add to cart section or page. • Added a gateway connection to the Merchant One online credit card gateway. This was the second merchant processing option for adilas customers. • Added a test page for all merchant processing accounts. • Did a full rework on the USAePay gateway code and merchant processing code. This rework eliminated the random slow connections and made the entire system seem like it was working as fast as lightning. USAePay was the original merchant gateway added to the adilas.biz system (11/2009). October 2010: • Tons of brainstorming and documenting ideas and concepts. Worked on mapping out system players and processes on paper. • Created an interactive map of the adilas business platform. Map is just in concept stage and was drawings and graphics. Used a “building” layout to show players, concepts, and virtual departments. The building metaphor has rooms, sections, hallways, doors, and shows relative connections of the pieces (strategically placed items to show flow and relationships). • Presented the map concept during a whiteboard session in Salida. • Added all special line items, as their own group, to the history homepage as drill-down links. • Lots of brainstorming on the scheduler application and the element of “time”. • Ordered a new dedicated server for adilas.biz. • Switched to ColdFusion 9 as our scripting environment. • Tweaked the code that deals with changing part numbers. New code will help to cascade changes to the appropriate other tables. Much cleaner and hug time saver. • Went to live on the new dedicated server. Saw major increase in uptime and speeds. • Put up the first round of the adilasuniversity.biz site. Small graphic with some links and some verbage. November 2010 • Added some new filters on the update inventory counts pages. They were a barcode filter and a vendor quick switch field. • We have over 100+ domain names pointed to the adilasuniversity.biz site. This is mostly for future marketing and domain real-estate protection. • Added a link right from the default photo (thumbnail) to the add/edit photo page. Idea came from a guy named Logan out of Denver, CO. • Added a total or bottom dollar value to the advanced add to cart page. • Full rework on the advanced add to cart section. Included tax calcs, back calcs to quantity and prices, discounts, mark=ups, etc. • Added the part category as a filter on the main part number search. • Added the my cart favorites section. This is a user-maintained dynamic button section that allows for searching of parts, recipe/builds, adding items to cart, displaying advanced add to cart options, and custom setting (quantity, price, and description). • Brainstorming on adilas university and a multi-media training tool. December 2010: • Added a special my cart favorites search part number interface. • Posted an out of business note on the Morning Star Automotive website. The turning of an era! Thank you Morning Star! You got us where we are today! (site will be left up as a demo site) • Added buttons to create new items (deposits, carts, invoices, quotes, PO’s, expense/receipts, BSI, etc.) • Added show/hide toggle buttons to show/hide the main search criteria for reports. • Added the “Any” name option for customers and vendors. • Reworked the customer payment history report. Allowed custom settings to be applied and the ability to hide the deposit info. Basically, a printable customer payment history report. • Added a checkbox to help keep the search criteria open if needed (got a little too aggressive on the show/hide options). • Condensed the PO location/contact info for printable PO’s. • Working on a graphic version for the interactive business platform map. Really excited about the future!

	AU 192		Daily Ideas	6/16/2010	IDEAS FOR SCHOOL - Dynamic – multi people contribute – approval process – standard upload checklists. - Tied together – Help files/related videos - Short – 30 seconds ideal, 2 min max - 30 seconds length on …. Topic - Wrapper and watermark - Em-bed code? - Train the trainers? - Text script for search engines - Ratings/levels – permissions colors - Comments – monitored - # views? - Searchable/categorized – i.e. invoices/PO’s/ER’s/etc. - Topic - category - sub category - details - Keep is simple stupid! - Standardized beginning (ending?) - Training notes - Video/screen capture/audio/animations - Theory – sign on , clock in/out – time, carts, parts - Application – PO’s, invoices, barcodes, inventory - Manage - Incorporate - Layout navigation/orientation – introduction to topics - Widen the bottle neck! - Crunching video on fly? - Software – wink, snag-it, video editing, DimDim - Compression - Bottlenecks – where are they and how to open it? - Audience: Business owner, employees, accountants. Managers, casual browser, shopper, consultants, attorneys, reps - Competition: investors, “I.T.” people – web service, education system – teachers, students (business/accounting classes) - Advertising: target markets – smaller businesses - Fear – Brandon “isn’t ready” for mass market - Short term goals: page for training videos, always looking for ways to widen bottleneck(s) Ability to Morph - Web basics - Log in/out - Password and profile - Clock in/out – view hours - Quick Search - Basic navigation within adilas - Main homepage – sub homepage – task or reports - Keyboard short cuts - Inventory coming in: stock/units, parts and general items, customer parts or services - Location and tax settings - Corp-wide settings - Users and permissions - Banks and check write settings - Vendors - Customers - Payroll - PO’s – all different types – naming? - Invoices – all different types - Quotes - Expense/Receipts - Deposits - Barcodes and barcode scanners - Calculators: finance, profit and discount, financial flow - Accounts Receivable - Accounts Payable - P & L - Balance sheet - Photo and document management - Customer log - Histories - Search inventory: stock/units, parts - Advanced search techniques - Using multiple windows - Using dual screens - Merchant processing - Pre-built customer web pages - Flex grid - Reoccurring billing - Admin time clock - Global mark-up tools - Point of sale - Sales taxes - Customizing interface – naming, colors, logo, etc. Concise – Video help files - 1 – opening browser window - 1 – back and forward - 2 – Ctrl + F – find, edit/find - 1 – links, drop down menus - 1 – address bar - 1 – status bar - 1 – favorites - 1 – super back button - 1 – F11 – full screen - 1 – tabs – windows – alt + tab - 2 – buttons - 1 – min, max, restore - 2 – cut, copy, paste - 2 – print - 2 – Print Screen/Screen capture - Group all keyboard - 2 – title bar - 2 – tab and shift tab – form nav. – toggle

	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 3564		2010	12/31/2010	YEARLY ACCOMPLISHMENTS 2010 Steve, This is a list of things that happened and accomplishments made during the 2010 year on adilas. It was a great year with tons of great stuff. If you need more detail, just let me know. I have everything documented down to the date. January 2010: • Brandon and Andy created their first video tutorial. It never got published but it was a 4 minute video on using the adilas shopping cart. • Small face lift to the main adilas.biz site. Added the cloud background. • Created a number of new flyers. Added options for dynamic name and contact info. • Lots of brainstorming on marketing, what do we do, and how can we get it out to the people? • Came up with a new slogan: Your date, you cache & retrieve it, we secure it. • Prep and research for the dewy decimal system. • Encoded sensitive database fields for storage. Examples: bank accounts, routing numbers, customer and employee SSN’s, driver license numbers, EIN’s, and usernames. Passwords were already encoded prior to this. • Added a forgot password helper page. February 2010: • Added a multiplier for the recipe/build prep page. • Added the add as advanced PO line item page. This page allowed for mini conversion calculations during the add line item process. • Added new PDF forms. 1 for Texas and 2 for Colorado (paperwork). • Posted the first round of the dewy decimal stuff online. Hundreds of files were updated. • Small fix on internal transfer invoices. Added current costs to items. March 2010: • Added units of measure to parts, PO’s, invoices, and quotes. • Activated corp-wide settings: show bin numbers, show unit of measure, and show line item numbers. • Steve loaned some money to adilas. Thanks! • Added a sort order option to PO and invoice line items. Included a bulk sort page for changing multiple sort values at a single time. • Added code to help automate bad debt payments. • Added the profit and discount calculator. Linked up the profit and discount calculator with the loan payment calculator. • Brandon and Andy worked on some marketing ideas. • Added a tools and features list to the main adilas.biz homepage. Also a small scrolling flash movie with the features. Most of the ideas came from Brandon and Andy’s marketing sessions. April 2010: • Added special line item settings to the corp-wide settings. Over 100+ fields. Things like: Labor, Supplies, Other, Collected, Fee, Dealer Handling, Discount, Freight, etc. • Added a merchant processing prep step to help speed up the transactions. We were experiencing long wait times (every once in a while). • Added a grouped customer log report. • Added the profit percentage to the global parts mark-up tool. • Added a price helper field to the add/edit number page. Local java script to help with profit margins, mark-ups, and pricing. • Added a price switch to trailer and toppers. They were always a mark-up value and we added options to choose between a list price and the mark-up value that was calculated on the fly from the basis. • Applied the stock/unit price switch to all stock/units and made it part of the global stock/unit mark-up tool. May 2010: • Created the mini invoice or 3” customer receipt. • Added the last 4 of the credit card numbers to the payment notes for reference. • Tons of time working onsite at an adilas client’s. Great ideas and training ground. • Added the barcode generator. Added page tie-ins and posted a free barcode generator on the main adilas.biz homepage. • Added a recalc taxes switch for invoices with multiple locations. This is an after the fact deal and allowed for items to be pulled from one location and then flipped to another location. The taxes would be recalculated and invoice values changed. • Added the financial flow calculator and worksheet. June 2010: • Spent more onsite time at a client’s (on and off throughout the entire month of June). • Added a new tax category called “With Tax Included”. This helps back into a bottom dollar value. • Added a discount calculation option right from the profit and discount calculator page. • Added a printer friendly link to the printable PO page. Took off all of the extra navigation and quick search info. • Lots of new corp-wide settings. Added the barcode quick cart, quick cash checkout, number of payments on checkout, customer web settings, show/hide prices, web return address, and barcode label sizes. • Changed all of the disabled/helper fields to a light blue color with black text. The old way was a white field with a light grey text value. The new fields stand out and are easier to read. • Added the PO quantity to the add/edit parts page. This is really handy when adding new parts from within the PO line items mode. • Added the apply quick discount to the edit cart line items page. • Added the auto calculate change due setting. Recorded the info and helped show the actual change due. July 2010: • Brandon and family moved from Salida, CO to the Logan, UT area. Salida was the birth place of adilas.biz application. Spell Salida backwards… you get adilas. (2001-2010 9 years) • Added tons of new details to the grouped daily/weekly reports. Showed tons of new break-downs and details with drill-down links to underlying data. • Added a corp-wide setting to help limit and/or open up location specific inventory tracking. • Major push to activate all existing corp-wide settings. Didn’t actually complete until August 2010. • Added the key word “All” to all of the quick searches. August 2010: • Combined a push on all of the corp-wide settings. • Added external customer PO #’s to invoices and quotes. • Finished up the basic corp-wide settings. In all, updated and changed over 700+ files in all. Files were from the main adilas.biz site, secure backend, data components, web/customer files, etc. • Did some page clean-up and added some CSS (style sheet) changes to every page in the site (while checking for corp-wide settings). Tightened up the overall look and feel of the application (minor changes to the eye but helped to standardize code and flow). • Added new drill-down links to the history homepage report. • Created the mini version of the daily/weekly report (3” format). September 2010: • Added a corp-wide setting for specific unit names. • Added a new global find and replace part number feature or tool. • Added the first round of the advanced add to cart section or page. • Added a gateway connection to the Merchant One online credit card gateway. This was the second merchant processing option for adilas customers. • Added a test page for all merchant processing accounts. • Did a full rework on the USAePay gateway code and merchant processing code. This rework eliminated the random slow connections and made the entire system seem like it was working as fast as lightning. USAePay was the original merchant gateway added to the adilas.biz system (11/2009). October 2010: • Tons of brainstorming and documenting ideas and concepts. Worked on mapping out system players and processes on paper. • Created an interactive map of the adilas business platform. Map is just in concept stage and was drawings and graphics. Used a “building” layout to show players, concepts, and virtual departments. The building metaphor has rooms, sections, hallways, doors, and shows relative connections of the pieces (strategically placed items to show flow and relationships). • Presented the map concept during a whiteboard session in Salida. • Added all special line items, as their own group, to the history homepage as drill-down links. • Lots of brainstorming on the scheduler application and the element of “time”. • Ordered a new dedicated server for adilas.biz. • Switched to ColdFusion 9 as our scripting environment. • Tweaked the code that deals with changing part numbers. New code will help to cascade changes to the appropriate other tables. Much cleaner and hug time saver. • Went to live on the new dedicated server. Saw major increase in uptime and speeds. • Put up the first round of the adilasuniversity.biz site. Small graphic with some links and some verbage. November 2010 • Added some new filters on the update inventory counts pages. They were a barcode filter and a vendor quick switch field. • We have over 100+ domain names pointed to the adilasuniversity.biz site. This is mostly for future marketing and domain real-estate protection. • Added a link right from the default photo (thumbnail) to the add/edit photo page. Idea came from a guy named Logan out of Denver, CO. • Added a total or bottom dollar value to the advanced add to cart page. • Full rework on the advanced add to cart section. Included tax calcs, back calcs to quantity and prices, discounts, mark=ups, etc. • Added the part category as a filter on the main part number search. • Added the my cart favorites section. This is a user-maintained dynamic button section that allows for searching of parts, recipe/builds, adding items to cart, displaying advanced add to cart options, and custom setting (quantity, price, and description). • Brainstorming on adilas university and a multi-media training tool. December 2010: • Added a special my cart favorites search part number interface. • Posted an out of business note on the Morning Star Automotive website. The turning of an era! Thank you Morning Star! You got us where we are today! (site will be left up as a demo site) • Added buttons to create new items (deposits, carts, invoices, quotes, PO’s, expense/receipts, BSI, etc.) • Added show/hide toggle buttons to show/hide the main search criteria for reports. • Added the “Any” name option for customers and vendors. • Reworked the customer payment history report. Allowed custom settings to be applied and the ability to hide the deposit info. Basically, a printable customer payment history report. • Added a checkbox to help keep the search criteria open if needed (got a little too aggressive on the show/hide options). • Condensed the PO location/contact info for printable PO’s. • Working on a graphic version for the interactive business platform map. Really excited about the future!

	AU 2182		Brainstorming Types of Time - Elements of Time	2/5/2011	Types of Time - (any of these things could have the word “my” appended to it) - (my) to do list, tasks, assignments - (my) mini blog, sticky notes, or my quick notes - (my) appointments, calendar, schedule (simple), day planner, specials, sales, planning - Simple – above. Complex – below. - (my) time sheet, work sheet, payroll log (ties to payroll and maybe invoices, po’s, and expenses, may be tied to customers - (my) customer time clock, work order, customer time sheet (tied to customers and/or invoices) - (My) ideas, wants and needs, discussions, forums, sharing, collaboration, threads, blogs (one or more people, sign-offs, comments, building…) - Seasonal, peak, non-peak, holiday, specials, promotion (tied to look-up with fee schedules or price to date ratios) - (my) updates, newsletters, projects, documents, meetings, agendas, shows, special events (main with sub sections) - Rentals, reservations, dispatching, advanced scheduling, service calls - Rewards programs, sales and promotion, loyalty programs, points, marketing - Events, classes, roll call, webinars, events, registration, trips, courses - Estimates, quotes, job costing - Manufacturing, production, forecast models, goals - Employee, technicians, doctors, teachers, guides, crews, managers, one or many (scheduling people – simple to detailed) - Reoccurring events, templates, or set schedules - Payments coming in or going out - Waiting lists - Tick lists, project management, cataloging - Queues, pools, job pools, unassigned, pick list - Maybe subsets of persons, places, things, combinations, or custom Categories - Rentals & reservations - Lists & tasks - Notes & documentation - Schedules & appointments - Time Logs - Collaboration & sharing - Documents & projects - Events & meetings - Dispatching - Persons o Employee/user o Customer o Vendor/payee o Salesperson - Classes & courses - Estimates & quotes - Registration - Manufacturing & production - Goals & forecasts Rough overview of the MDI Idea Center: - Add an item (document), choose a client from list, select a project (dynamic according to client), choose a document type (see below), title, notes, budgeted hours, priority, sign-off required, sign-off by who, hide/show document (still in edit mode). - Able to search any projects, any clients, etc. Quick and advanced search options. - Only the correct person could do the sign-off. It would then show up for roll call. Very simple: a check box and a notes field. - Anybody could add a comment to any document. All of the person (user) date and time stamps happen behind the scenes. Very simple: a notes field. - Application had an auto response (send an email to Brandon) built-in. It would let me know if an item was added, a comment, and/or a sign-off happened, pretty cool. - It also had an email form built in. - The notes and comments allowed for html to help in the presentation. Any outside files had to be uploaded separately through FTP. - It also had options to finish the document. This included finish notes, actual hours, priority, and lock-down options. - There was a built-in 5-level deep outline option using div tags. - Document types (drop-down list): ideas, add-ons, progress reports, change requests, bags, phone calls, meetings and verbal, email documentation, other, proposals, contracts, project scope and overview, project schedules, “workflow, roles, and responsibilities”, phases and milestones, creative document, technical document, requirements and specifications, other main documents.

	Adi 13		Look & Feel - My quick buttons & links (favorites)	6/3/2011	See element of time # 412 for more info. It would be really cool if we could marry the my cart favorite buttons with the old mend and repair (build your own report) settings. The new buttons would then show up as standalone buttons and/or in the interactive map layout. Another idea is have a full list of every possible link in the system and then allow the users to pull up the links, name them, save them, and categorize them. The initial interface would be broken down into application types and then broken down into subs from there. Another idea is to have a link on each page (say like in the heading) that allows that page to be pulled in automatically to the favorites. Kinda like a bookmark or favorite inside a browser. If that page needs criteria, it would then prompt for any criteria. That way, the users would know where they were at before creating the favorite or link to that page or section. New idea added on 9/25/12 by Brandon - What if we just did a big one-to-many and allowed any existing report in the system to be saved (the settings). The main values would be a report id (dynamic key field), the report name, the page name (destination page), who it was assigned to, and a status field. Other values may be public/private or something like that. The many part would be the report id (tie-in value to the main report), a variable name (setting name), a value (setting value), and a status. We would then be able to pull the reports and then set the correct criteria or just run the reports and look-up the saved settings or values on the fly. This would be really cool... Instead of making a whole big brand new super report, we could just harness all of the existing reports and result pages. All we would have to do is pass a special saved report id number and then have the report pages look-up the values and play accordingly. That would be a huge time saver (not having to re-create this huge super report structure). Along those same ideas... We may need to add special date presets or hardcoded date keywords. We could then dynamically figure out those dates by having a global function that could interpret the keywords. This could be things like: today, yesterday, tomorrow, thisweek, lastweek, nextweek, thismonth, lastmonth, nextmonth, ytd, or a special value called "prompt" which would allow you to enter the custom date range on the fly. This whole system could be saved per user, shared between users (like public cart favorites), and dealt with in a controlled manner. As a side note, we may want some global functions or global responder pages that know what to do and then pass the data to the correct sub pages or sub reports. Just some ideas.

	Adi 15		Taxes - sales tax & collected fees	6/3/2011	Note added on 7/19/12 by Brandon - Sales Tax - we need to start on the location homepage. We need to assign real vendors, real expense/types, and real user-maintained balance sheet items. The key is the locations... that is tied to the tax settings, that is how it is recorded and collected (on invoices), that is how it will be paid out, etc. A good resource is Jeff McCorvey who has 30 locations with 8 different states and tons of smaller entities that need to be paid and tracked. Small idea on the sales tax re-work... What if we added two more levels. The top level would be a quick - to the point - group for the date range. The next level down would be a breakdown by day, the last level would be the detail level. If a fourth level was needed, it could be level 3 as a invoice group and then level 4 as all of the details for that invoice (advanced invoice line item search). Just some ideas. The other thing that I want to do is take out the invoice total (with taxes). I just want to show the amounts that need taxes and the taxes. Don't worry about the amounts plus taxes (full invoice totals). New note added on 9/10/12 by Brandon - We just spent a whole week doing a rework on the sales tax page. We still need to automate flow between invoices and balance sheet item and balance sheet items and expenses but we did do a bunch of prep work and created the 4-level deep reporting system described above. Those files are up and online as of 9/8/12.

	Adi 16		B.S.I. - Balance sheet rework (round 4)	6/3/2011	We need to circle back around and work on automating sales tax, collected fees, standalone declarations, watchers, feeders, hybrid callouts, etc. This is quite in depth and is what we would be calling round 4 of the balance sheet. As a note, on 7/4/13 we had another request from Kelly Whyman to add some sort of off the record type entry that a CPA makes. This would allow the owner or manager to see things as they really are and/or see things as they become adjusted according to specific entries. Kelly was requesting this show/hide option that could be turned on/off as needed. I (Brandon) replied to the email and mentioned the "standalone declarations" that are planned for adilas. Here is some info from the email. Kelly, Great ideas! We love it! Now if only we could find some time... :) I'm not sure if I've ever mentioned this before but have you ever heard of a thing called a "standalone declaration". This is a future adilas project that I think could help you out. A standalone declaration will be a physical entry that is mapped to a specific spot within the financials (income statement and/or balance sheet). It will be called a standalone declaration because it just exists or was created (kinda pulled out of the air if you will). It doesn't really have any backing or supporting documents other than it was an entry that was required or requested by a CPA. We are going to call these entries a standalone declaration to help them stand out or be their own little sub set. In order to help with the show/hide options, we could add a special show/hide flag or we could add an option for "real" or "taxes only". Another thing that we could do is allow the dates to be very general. Most of the dates inside of adilas are a physical date such as 7/4/13. However, if we needed to, we could allow for things like: In 2013 or in July or 2013 without going clear to the exact or physical date value. Anyways, just some ideas and food for thought. Enjoy your day and keep the ideas coming. Even if we can't jump on them yet, we can at least record them. That is at least a start in the right direction. Thanks, Brandon Moore 435.258.5504 (home/office) brandon@adilas.biz :: www.adilas.biz "all data is live and searchable" ----- Original Message ----- From: Kelly Whyman To: Brandon Moore - adilas.biz ; Stephen Berkenkotter Sent: Thursday, July 04, 2013 1:40 PM Subject: HUGE SUGGESTION - The need for an additional day on the Balance Sheet or Option for Adjustments to be seen or hidden Gentlemen - Happy July 4th, with it being independence day, I have a huge request for the Adilas System. Is it possible to add a day or some time of sub section to the system that allows adjustments to the P&L/Balance Sheet to be shown or hidden. So many CPAs adjust clients books and it takes away from the ability to see the business as it was prior to adjustments. Originally Steve had mentioned an extra day of the year. I would like to suggest you allow the adjusting entry mechanism (Invoice, Deposit, Expense, Balance Sheet Detail) to have the ability to be active or inactive when viewing P&L or Balance Sheet. Is this possible? It would be something that no other system is capable of doing. Best, Kelly

	Adi 23		Time & Web - Online reservations	6/3/2011	See element of time # 427 for some ideas about rentals and reservations. Also, as a note, Brandon has a ton of brainstorming sheets that cover these topics in depth. It would be a good idea to review those documents when actually doing this project.

	Adi 31		Training - Map out entire system	6/3/2011	When getting to a detailed level about what the system does... Go through the code and note all forks, decisions, assumptions, and normal flow logic. Put those values in to normal English and dummy things down a bit... :) This concept of mapping out the system started back in Sept./Oct. 2010, and let to the development of the interactive map concept. I have a number of loose pages with brainstorming ideas on the system mapping sections... see Brandon's adilas brainstorming folders. Also, here are some other random notes that I made in my notebook. These notes were part of a picture that was drawn in my notebook. The picture was of a globe or data sphere... Here are some of the notes... Not bound by walls, virtually jump to any place at any time, if you ever get lost... return to the main homepage or main hub, the quick search is like a little vehicle or transport pod to multiple parts of the system, it (the quick search) follows you to every page. Think interconnected levels, orbs, stations, functions, processes, jump points, cores, short-cuts, stages, key points or flag, full life cycles, waiting rooms, staging zones, traffic patterns, etc. Show permission levels and how they interact or overlay the data and life cycle of the objects and data. This is the adilas "data sphere" model. Learn how to play the game... relate the model to the game of golf with fairways, greens, roughs, sand traps, lakes, bunkers, etc. Help the users visually see where they are and where their data is (good to go or in the sand trap).

	Adi 255		Report - Template/Dashboard for all corps	1/4/2012	Steve would like us to create a dashboard, template, or custom combo. Let the users decide what they want to see and use. Maybe setup some generic settings according to job type... global templates. This may be somewhat tied in with a concept called my favorite buttons and links. See elements of time #13 and # 412 for more details. They are not totally related but may end up being part of the same features and/or options. Basically, ways to customize the system per user or per industry. As a side note, Steve and Brandon worked on a mini version for the MMJ industry. It is contained in the custom code section under the file name: mmj_operations.cfm

	Adi 20		Training & Interface - Interactive business platform map/touch	7/31/2012	The interactive map/touch concept was first put on paper on 10/11/10 and has been in the works and on our minds for almost two years. Tons of thoughts and ideas have been added to a seven page document that has ideas and concepts dealing with the map/touch interface. The entire seven page document has been uploaded to the history B.S.I. gallery until the project goes live. Ideally, it will be an interactive player of sorts that will act as front-end interface for users to navigate and get familiar with the system. There is a graphic version (non-interactive) up online from the main switchboard page and from an upcoming concepts page. There is also a special help file that was created to help give some reason and logic for why pieces were placed where they were... Tons of thought has gone in to this project and we can't wait to get it fully going... Good stuff. Part of an email sent to Steve on 10/29/12 by Brandon. (see below - at this poit the interactive map was still a concept and had not gone past the graphic or mock-up stage.) What if... you allowed a company to design their own interface and then we just overlay links on top of their graphic. We then show a custom graphic (custom gui) and then we just point it to different things (links). That is the exact same thing we are doing with the current interactive map layout. The only difference is, we made the interactive map as compared with a client making it. Imagine a set format for the graphic (certain size)... They could then use their words, their buttons, their look and feel, and their graphics. They could make it as simple or as decked-out as they wanted. We could even sell that option as an extra service... We then help them add functionality to their own graphical interface. Each corporation could be completely different and customizable. It could have buttons, links to pre-built searches, quick options, outside links, etc. All it would be is a graphic that gets some custom mapping overlaid on top of it... just like our current interactive map on the bottom of the main switchboard page (just a graphic with links overlaid for functionality). A corp specific image map or custom GUI interface. Additional thoughts... What if you took this even further and allowed (or helped) users create a custom flash movie to add interactivity, animation, roll-overs, drag-n-drop, or special menus or sub menus. The goal is not to re-create the whole thing, just add a visual layer to the already existing toolsets. In a way, a virtual landing or homepage for the companies that met their needs.

	Adi 464		PO's - Corp-wide setting for PO note	8/1/2012	Craig would like to not have to add a note to a PO. Response by Brandon - Maybe he could just put his initials or something. Our goal is to help tell the story. Those notes are part of that process. It only requires three characters.

	Adi 468		PO's - Adjust PO Type on Dupe	8/1/2012	Craig would like to be able to adjust the PO type on duplication. Response by Brandon - This could get pretty tricky as some PO types have special settings dealing with vendor match-ups and whether or not to allow request quantities. The original goal is to copy or duplicate. Once the new one exists, the person is able to use the normal process if something needs to be switched.

	Adi 469		PO's - External Invoice # Field	8/1/2012	Craig would like to be able to add many invoice numbers to the external invoice field. Currently he can only add 3-4. Would like it widen to hold many more. I mentioned Flex Grid but I do know clients that have multi invoices they receive on one PO. Response by Brandon - Maybe if tons of invoice numbers are needed, they could put something like "see notes" and then use the notes field to list up to 255 characters. The external invoice field only has a value of 50 characters. If it gets lengthened, every PO would need to carry that extra field length weight which is unnecessary. Just have them point to the notes and use that.

	Adi 470		Invoices & Printing - Browser Override	8/1/2012	Invoices & Printing - Browser Override John would like to over ride the browser print function so he only has to click print once. I was talking to Michael about the same thing and he suggested we also alow the system to defaut to a printer drawer and maybe drive two printers at the same time. Response by Brandon - Printing from the web gets tricky... In order to control printer settings, you have to use java-script or something that is client side. This could get pretty funky as every setup (printer to computer) may be different. Currently, the system does not have any way of recording or talking to specific hardware on the client side. The browser itself is very neutral and plays with what it finds. I'm not sure we want to get into specific hardware settings. It could lead to a perceived liability of us not being able to talk to a specific device. That could be a can of worms... I'd shy away if at all possible...

	Adi 501		B.S.I - Balance Sheet on a minute or second level	8/29/2012	This is just a concept right now but may become a piece of the puzzle later on... We are seeing a potential need for showing things happening on a minute by minute level or even down to the second by second level. This may not be the actual balance sheet (actual report), but it might help in figuring out what was going on and what happened or what should have happened. Crazy how it come back to time... it's kinda like we've been looking over the underlying pieces, only to find that the missing piece is time (what we considered a given). Interesting... This may not fit here, but back in fall of 2010, we had the idea of running all of the pieces of the puzzle through a movie-type interface and show it as things changed. You could run the movie forward, backwards, just let it play, pause, go in closer, etc. Fully interactive with the data that happens over time. That thought spurred a number of ideas including the interactive map, ideas about elements of time, an interactive player, and ideas about 3D operations and accounting. For more info, check out Brandon's notebook from August 2010 to to December 2010. Packed full of ideas all relating to objects and data over time.

	Adi 524		Quick Search - Default Cursor	9/12/2012	From Bill in Pagosa Springs - When you click on a radio button or select a drop down, have the cursor return to the search field. Finished on 9/14/12. Added some code to both the main homepage and the quick search in the header bar. Brandon

	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 1139		Daily Ideas	3/14/2013	Artist & Writers Fest – USU -Brandon Mull – Author of Fablehaven – - Dream it up in your head and then do it - Use the real world as a model - Spend lots of time daydreaming - Details and memories provide additional insight - World building – create a new environment or world - Think through how the world would work and what would happen. Example: Say a good fiction writer might talk about a concept of an automobile. A great fiction writer goes clear to the traffic jam level of this concept. o Take things to a new level and what happens in their society or culture. How do you deal with cause and effects? - What new abilities does this bring to the picture? - Brandon interacted with the audience quite well… lots of questions and responses. Story based. He was talking about concepts of world building. Think through the realities of the world you are building. - Characters, details, physical description, use of words, how they think, what do they do, personality, learn about past, base off of real people, what they choose, stay true to that, relationships, interactions between players. - Five key pieces to a story and/or world building: characters & relationships & trouble & decisions & consequences. - Imagination can take you places. - Sometimes no’s help create who you are – a great teacher! Reading session – Writer’s & Artist Fest - I want to accomplish my dreams – so that is what I’ll do – young author. - Limitless! o Creativity, motivation, capacity of the heart, challenges.

	AU 1129		Daily Tasks	3/27/2013	• On the phone with Steve. We went over a few things about training and client needs. We talked briefly about job costing and different ways to use some of the adilas tools. Eventually we will need to make both makes and models into a dynamic corp-wide setting (what to call them). • Went into town for day two of training. We had more participants with GoToMeeting and had a great session. On a fun note, we started the day talking about “world building” – a concept that fantasy and sci-fi writers use to help their readers learn and understand the rules and options in these other worlds. We then started talking about the adilas world and what goes on there. We lightly talked about five features that Brandon Mull – author of “Fablehaven” used in a seminar. They are: characters, relationships, problem and/or trouble, choices and decisions, and finally consequences. Great session. Lots of interaction through GoToMeeting. There were three clients that chimed in a good deal. There were others but those three were active and asked tons of questions. 20 miles. • During training we found and got a couple of new requests. Spent some time making some quick fixes. Linked up the default check writing bank to the add new expense/receipt page and the add new expense/receipt payment page. Also changed the flow on the Special Live PO’s and how the main vendor/payee gets changed. The old way used a dynamic drop-down list to change the PO vendor (basically setting the payables vendor). The downside was that in order for vendor to show up, they needed to have at least one PO and one item or part in the system. These requirements helped to limit the list but added some complexity to the process. The other change we made was to switch the drop-down list to a straight id number field. This makes it easy to switch but requires a vendor/payee id look-up. Posted files online.

	AU 1242		Daily Ideas	5/27/2013	-Ideas for a flyer… “World Building”. I had the idea to do a flyer about the concept of world building and telling the story. This could include a number of concepts and how they help to “tell the story”. Include: characters, relationships, trouble, decisions, consequences (From the author: Brandon Mull) -Along with the world Building flyer… Add an analogy between the human world and the adilas world. This might need a little help! Human World vs. Adilas World Universe - Adilas admin Worlds/locations - Corporations/locations Populations/Groups - System Players Individuals/Objects - Main Objects Data Level - Data Level -World building and telling the story: universe, world, locations, populations/groups, individuals, data. Do a flyer that talks about world building and telling the story. Include adilas core concepts. (This whole flyer is the why)

	AU 2135		Adilas 3 Day Training Notes - Denver	7/16/2013	General Notes for Adilas Training in Denver Day 1 - Tues. July 16th - Focus: sales and inventory Steve - demo/overview: -Mainly covering sales - shopping cart, interfaces, -Cool demo and overview with serialized and stock units -Think it up, and then let adilas try to follow your flow IDEA: Steve mentioned that it would be neat to get someone on a demo... or maybe we could even film them and put it online.... but get a user that uses a touchscreen (like those that have a touch screen/computer flat together, it tilts) they can just go to town on their touch screen IDEA: Maybe this is kind of like what Brandon & I talked about when we visited the Mixing Bowl... but that would be really neat to do some high quality filming on locations to see how various users use adilas... like mormon.org type thing... that would really be so neat and could be a great asset for marketing... just a quality little video demo with really users -Recipes - Build & hold/Build & sell Cannot overemphasize how important setup is! SETUP is critical - that makes users happy, satisfied and that can create more successful adilas users. IDEA: Would it be worthwhile to have a special training for reps and consultants to specifically help them be effective with setups? Helping consultants so they can help their clients. -Ability to archive - Standard Operating Procedures (SOP) right onto their site, so that the company can have its specific guidelines for use - that is really neat Adilas - REAL TIME, anytime and can be SO incredibly effective and help your client to be successful when you give them the correct tools (setup), and help them to use it successfully - No lag time with understanding what is going on with your business, you can know everyday Dream it up - and you can make it happen! It is what YOU WANT! That is one of the greatest features for users! -Adilas Project - Steve called it - I'd never heard them mention that term but I liked it. Adilas is trying to help business owners accomplish their goals and be successful. -Just getting clients/users going... you can start them with a little bit and add more pieces as they are ready for more, wanting to incorporate more. You can fill in the backend later. Just get them using the system on a daily basis and then you can incorporate other aspects as you go. -The most important thing is to know what your client wants, needs, what are their goals? Then set them up in a way that they can accomplish that and understand how to be successful. Mirror the physical in the virtual. (What they do with their hands - do in adilas.) Back with Brandon: -Planning out what you want on paper - very useful tool -Setting up a consulting business -How many worlds = corporations (EINs, entities)? Locations - various locations under the same corporation or entity -Print help file on the main page when you set someone up so that you can get them back in should they log themselves out... -I think a great thing Brandon did is having them walk them through functions - when something was missed, or just general practice and repetition -Rep: get all the info you can independently before you start - like tax settings, etc., etc. Then anything they need you can go through with them... but get what you can before the sit down setup. IDEA: connect a video link to the permissions and settings area so that people could watch a brief blurb instead of reading the info to the side if desired - idea from Russell Back from lunch: -A brief history of adilas - started from a question of how long has adilas been sold -It is so interesting how much your goal really does affect what we do in training or how we use or work with adilas tools - -So many ways to play the game or get what you need/want - i.e. they were talking about duplicating the PO's for generic items to switch locations... so many great tools -People LOVE the Quick Search when they see how it can be used -When people see what adilas can do, they LOVE it! It's just getting them to be able to see, understand, and use adilas successfully. -You can start from SO many different places. When you have parts you can start your cart from there, you can quick search start, you can start with customers, etc., etc. -Remember to use your browser tools and assets -Be consistent in adding your items with everything (customers, part numbers, just keep it the same - all lower case or first letter of word capped, etc. -People love seeing the possibilities - they love seeing the speed, they love seeing things that make their work faster, easier, more efficient - all of the tracking, accountability barcodes, reporting - history, quick buttons, my cart favorites etc., etc., etc. -My cart favorite buttons - pretty snazzy stuff

	AU 2136		Adilas 3 Day Training Notes - Denver	7/17/2013	DAY 2 - JULY 17th: Idea for focus - CRM, eCommerce, Flex-grid, Elements of time Review/demo with Steve -Going over PO creation, getting inventory in -Can use reference number to help select specific groups, for closeout items or etc. -Verify & lock PO's - is really a communication tool between off site receiving & another site for accounting - allows to verify that things have been received.... -Much easier to just get the little swiper or key it into adilas so that all of your data is there & tracked. Much easier than having a separate card swiping system which you have to record approval numbers back from the batch, etc., etc. Much easier if it is all contained in adilas. Adilas also can connect all of the info from the swipe - the approval number has a drill down with all of the details and you can even void a transaction in adilas if it's within that business day and the batch hasn't been settled -Covering credit card transactions - people really want to be able to use this function for demos -"This is an eBusiness buffet, have fun!" - Brandon Back training with Brandon **Training, education, education, training! Obviously that is why we are even in Denver but there is such a need for it! We have a lot of exciting things coming and it will be so exciting to get the user guide up and going with interactive videos and education from the conceptual level through tech level IDEA: (apparently already recorded) but have a template for inputting new employees, to help save on time -Customer Tax ID# - a great field to just modify to what you need (for Russ with family history, maybe this is their Reference tag) -Customers: a fun little demonstration with Danny & Santiago -Customers throughout the morning -Training & questions on customers (CRM) -Elements of time - often the question is presented - can you get it to prompt you? Push technology -Fits into round 2 of elements of time -IDEA: It would be cool in the follow ups or whatever... is to have the dates on the mini calendar as a link that automatically populates field - way too much work for right now - automated will come in the future. COOL - Something I did not know, but is a cool little thing. You can add links in the adilas logs... there is an automatic link if you fill in the web address for the customer... but also by html compatible log notes... which for Russ's question for family history essentially means every log note you make - say for referencing census reports, death records, etc., etc. - you can add html text to create a hyperlink in your log note, so you could reference right to that sight... that is pretty snazzy (with family history, I don't know how reliable the site sources are, or if you need a scan or pic from it???) It is going to be so fantastic and incredibly powerful to have the "create your own buttons" for what you do or look at or need to get to fast, etc. or being able to write custom code for your specific purposes. Really neat stuff! -When you know where things are stored and you know your methodology it is amazing how easy and the capacity you have to pull that information. -Copy and paste emails to the log, then you have all of the information and the entire story that has occurred... as much as you put in, you can get back -Additional contacts is a great place to add subs or things like "Ship To", "Shipping Address" or whatever you need -I love that adilas is created to be not limiting - - so many applications don't let you do certain things or don't allow certain things because for various reasons they limit it to a specific scope or don't realize other capabilities -Cool sounding function on elements of time where you could track sub dates and time under a project... then you could track your final amount of time or so forth and invoice for it or know how long a project took you -Elements of time - you can add up your time and billing if you'd like - for it to auto-calculate and help you with some of those things enter them as mains. Sub dates and times can be good for tracking a project but it does not auto calculate your time but maybe if you don't have a specific hourly rate and just want to decide on a total when you're done or something, that might be a good way to go with subs. Depends on what you want - just like with all of adilas... what is your goal? Then let’s choose the best route to achieve that. -Pre-set your calendar view in the settings area - you can put it in calendar view, time slot, showing what you want, etc., etc., etc. Of course from the home page, you can swap to differing views. Lots of cool stuff. I need to get more up to speed on elements of time and flex grid REQUEST/IDEA: Clients have been asking for a connection between customer log notes and elements of time. Basically asking to put a follow-up on the calendar, etc., etc. Brandon mentioned that might fit well with a setting. Maybe an element of time....? Brought up in class by Steve. -I think it is instructive how we work through step by step and problem solve many times. So working through turning on a permission and then adding the setting when it doesn't show up and just adjusting things so that users know that there are ways to fix things or get back to what we wanted or my goal was. -eCommerce overview - super neat stuff coming with this... -I think it is cool that people working on the eCommerce are already getting their own exposure to adilas... :) - also an unanticipated aspect I had not thought of is building customer profiles. -Returns - 'think negative invoice' - but be careful with that, it is not a blanket statement... because what if you have something returned that you can't use again or etc., etc., etc. -Sometimes it is so amazing to me, that you click a few settings or permission buttons and your entire look, feel, capability can change entirely... same product, which we know but sometimes I still find it astounding because it is SO different from any other product, amazing! Whoa! So much cool future development! All sorts of fantastic stuff coming! - Marketing, business aspects, tools, promos, etc., etc., etc. *IDEA: Track who is logging in to eCommerce. Possibly somehow route it to the Queue??? Maybe flag it somewhere else??? (May possibly be in the code already???) -Been down digging tons of tunnels and kind of wondering why no one else is down here but they are trying to spread the word and invite others down to dig down here. And there will be many more to come! -Currently - adilas is a business tool. Future - adilas as a business and marketing tool. -Brief overview of flex grid -Flex grid: essentially creating and stacking your own customizable database on top of what adilas already has. (Create your own database) -User maintained history aspect: essentially any note you want to create, or any info you want to log that isn't already tracked, user maintained notes, etc. -Custom fields: so many possibilities here! What do you want to track, how many categories, sub categories, etc....?

	AU 2137		Adilas 3 Day Training Notes - Denver	7/18/2013	DAY 3 - JULY 18th - Focus on deposits, banks, expenses, etc. -Started off with a question from online which led us back into flex grid -Back into flex grid... (Transparent & non-transparent flex grid options) -The only caution for flex grid is plan it out so you don't have to re-do all of your work and so that you can have the pieces you need where you want ^I need to learn more about flex grid and elements of time -I love the problem solving aspect of setup and consulting.... understanding their issues, concerns, needs, goals and helping choose the best tools to fit that goal or an acceptable solution for their concerns -It is so neat that the flex grid is its own customizable database on top of the application. -You can even barcode flex grid if you would like - a company uses this because they have different pricing for many of their customers on the same parts We need testimonials and experiences from customers - people see the value in that, it had been mentioned by multiple class members -Stock units seem really neat - we saw a little bit with a company that had done a lot of internal invoicing with stock units - really amazing how much they tracked everything.... construction management and job costing to the n-th level -Once you have all of this data, you can do SO many things. Plan ahead, know what you need for future projects, have everything tracked to the finest detail... huge potential, everywhere! -Brandon did a little show & tell of how some different company's use adilas - people LOVE this! This seems to give people an understanding to the point where they finally grasp some of the possibilities of adilas. It is interesting to hear their reactions, because we have been working in adilas now for 2 days and they have been really excited but people love seeing how this is really used in business and they start seeing an even bigger picture. A good little wow show, they really capture just how much this tracks and how easy it makes people's lives in business and how great of a business tool adilas is. ....... Now we just need to get some "commercial", "testimonials" from so many of these customers that are using adilas. -Adilas really increased the re-sale value when you have such a detailed customer base and detailed books and you really increase the value by showing what the company is that is being sold. IDEA: A rep training - which was already mentioned above but what if it was largely rep led and instructed - specifically for reps and how to setup clients, but also all that adilas does -Protection by sharing - and the users and those in the class were expressing their appreciation of that and also feedback on how smart or a good route that is -Security question - password & profile help page. Talking about all the upfront adilas does to keep things safe Users get super frustrated when they are set up and feel like they have been left alone. If you can make a good setup and initial training, that is critical, but there is a definite need for consultants and training - no question obviously, why we're here again and why adilas university is forth coming. You will definitely have some people that will get in and figure it out and make things work and you definitely have other people who will need more hand holding. Also known - just figuring out how to address that again and help users to be successful! That should be the focus of the rep/consultant - help your users/clients to be successful. -Is accounting even needed if nothing is happening? Great way to ask that - let operations lead. Put the horse before the cart. -Zipper analogy - a great starting point - because merging operations with accounting will change the ways businesses can function and can change the face of what will occur in business accounting and tracking.... Brandon wanted me to record that Joe was talking about this but more of a comment than an idea. Maybe an idea as an approach??? -Reps/consulting/instruction note: we really need to be able to help people understand principles, flow, some basics and where to go for help (help file, tech support, adilas university, etc.) about how adilas functions.... because when people understand flow and more principles, then hopefully they can be more prepared to go in and figure out how to make things work for them. -Interactive map: operations on the bottom and as things flow through the bottom section, then thing begin to rise to the top (a little cream scenario), when you have good operations, things will be cascading to the top - your accounting aspects -I'm really impressed with Brandon's teaching: sometimes it gets really challenging to cover basics, flow, and possibilities when you have such varying levels of users and also users or clients who really want their "problem" questions answered... anyhow, it definitely takes a balance and I am grateful for Brandon's patience and teaching and all such things. -Accounting comes with the natural flow of accounting -It is important to understand that there are many ways around the track. Different ways work for different people, industries and preferences - and help other to work in the way that they need... Roxanne: demoing expense/receipt - Good to remind people when setting up and the interface looks intimidating. That assets are any monies coming in, liabilities are any monies going out. With that PO's are tied to inventory, what you are paying and bringing in for inventory. Expense/receipts are any other money out for whatever....... -She also copies and pastes a lot of her little notes into all the different sections, b/c different ones show up in different reports -P&L - Profit and Loss, I.S. - Income Statement, B.S. - Balance Sheet -Roxanne was saying: Get in there and get working - if you make mistakes, not a problem, it can be cleaned up but be unafraid to get in there and just use it. There are ways to clean up, to move on, just get going and try to do the best we can. -Reimbursements - when creating that expense receipts for a reimbursement, you are putting in what they paid - so "no bank assigned", then when you go to pay him that will essentially create a new expense/receipt to satisfy that one or many if there are many to reimburse Always work out of your payables, you're always cleaning up your payables. For what you owe, look at your payables, work from there. Look at what to pay from there, and then you have it broken down to your PO's, your REI's, and your Splits. -The "not yet" verified link on PO expenses you are paying on - if you click on that link it will take you right to the verify page and then right back to your payables homepage - instead of going back and doing the process over and over and over, you can do it all there nice and fast. Wahoo! Thanks Roxanne, that was a great demo! Back with Brandon leading - but a lot of group comments and input, wrapping up the training scenarios, etc. -Great comment by Joe as we were talking about future clients - Every situation you walk into you need to assess the client, not only what they need, but what is their interest and desire - are they ready to soak up adilas like a sponge.... or are they no, no we have QuickBooks/PeachTree/whatever... then you just throw them a bone and then another bone, etc., etc. Then Brandon was discussing that you really can walk someone step by step. You can start with some aspect of the application and once they get that then you can introduce another aspect. What do you want??? The byproducts that adilas creates is worth way more than the monthly payment for the application People believe in adilas and the way adilas functions. They love how adilas cares about their customers and reps, they appreciate how adilas is not stingy with all of their code or training, they love it for the incredible business tool it is - that it tracks everything and does almost anything they want and that you can tie everything together and tell the whole story, they love that adilas is offering training for free right now, that adilas actually takes their ideas for improvement and incorporates that. Those things make people believe in adilas and people are selling and promoting adilas because they love the product and they believe in adilas' philosophy. -Things are automatically mapping just as you are operating. -"People do things different ways, and so does adilas." -comment from Roxanne as we were discussing how important it is to set people up right from the beginning or in a way that works for them and their preference -Also a note, a consultant was discussing that they doesn't know everything but you don't want a client to know that or feel like you don't know what you're doing. So they focus on another problem or area of training for that time, express that you can focus on the question next time or after getting these things settled, work with something that you know, - then they’ll figure out the answer for the next time. That was their trade style. *But of course another style - which others mentioned, is: I don't know the answer to that question but I know where I can get the answer and I will get it for you. That is how I like to play as well. Be completely up front and honest and transparent but I am willing to work for the answers and get them to you. You can still be confident about the system and your abilities without knowing the answer to everything. Just be up front and professional and get the answers you need or find creative solutions for their problems. The answers are there. -Here is the system, there are some rules involved but you can play like crazy with whatever you want! -History has such great power, records the rest of your story. -Traditional accounting - I need to close up my month, what happened this month. Adilas - what happened today, at any time, and at any time throughout the day. All sorts of data - run all levels over time! -You can use any aspect of adilas.... or all aspects of adilas. What do they want? Or if you hit the brick wall of tradition, offer something they don't have... then they can slowly work into things later if they want, or if not, no problem. You can sell adilas just for their pain! -Because you are not forced to play in one specific way it opens things up exponentially. That is why adilas can service all sorts of clients, industries, etc., etc. -People love that adilas supports the small business owners and truly works to support clients and does not kowtow to huge corporate companies. -And still growing.... :) -A great selling point for customers is also the idea sharing - if a client has a need, adilas often has a tool that can help, and if adilas doesn't have it you can submit your suggestions or they can build you the custom function or maybe there can be a piggyback development -Put notes in everywhere in adilas - use the notes to the max, tell the story Notes for graphic ideas: -Adilas Engine with different bodies/skins - multiple ways to show how customizable, various ways to interface -World building graphics - -Items travelling through the pipes: PO's - transformation - invoice -Steve's symbolism about an ant colony all participating to build adilas

	AU 1699		Daily Tasks	7/19/2013	• Made a new training flyer for August. Added links to adilas university to different pages. Updated training pages. Posted files online. • Went in to Salida for a team meeting. We had quite a few people come and participate. We had Shari, David, Steve, Craig, Brandon, my brother, my sister, Shari’s son, another associate, a previous employee and her husband. Anyway, a good group of us. We talked about sales, marketing and support. The deeper we got, the more all three topics kind of morphed together into the “needs” of adilas. If you don’t have sales, you can’t fund education and support. If you don’t have education and support, you can’t do mass marketing and sales. It was interesting to see our whole group go in circles over and over again. Steve also expressed a lot of concern about monies and having enough to make things happen as they need to. Shari and I expressed to Steve multiple times that he was not alone. You could really feel his weight and stress level. Steve seemed to be at almost a breaking point. I was in the same breaking point about 6-8 months ago. Overwhelmed, spread thin and more than we can handle alone. We tried to emphasize “team” and that he is not alone. Anyway, the meeting ended and no new ideas or direction was presented other than stick to the current plan, work as a team, and time will tell the story. Great meeting.

	AU 2138		Adilas Team Meeting Notes	7/19/2013	ADILAS TEAM MEETING NOTES - JULY 19th FOCUS TOPICS: Marketing, Sales, Support MARKETING: -Commercials on youtube.com - how they use adilas, talking about how they love it, what they do with adilas, what they love about us. Show what it can do, for lots of other people. This is what it does.... how someone uses it and what they think about the product. -Target people with previous knowledge of business & technology - or at least try to have them as reps, so they have an understanding of business concepts and can understand adilas. Get actual reps that can go out and be representatives for adilas with the knowledge and skills to be successful as a rep. -Adilas has all of the CRM, Inventory management, Employees & payrolls, finances & accounting, ----- would like to also include and improve on marketing for adilas and also to help users with marketing -Little business seminars - live events - they let me show you what this is, instead of just come to training. Seeing the possibilities and what adilas can do.... show the product and then training, reps, etc. can be setup later when we the clients are in place. LIVE infomercials. -Business Resource Center: a source for a lot of entrepreneurs - allow demos & presentations of business related aspects... getting the product out there -Increasing our education and support - get education higher than the function, so that people and marketing can move that forward and advance the growth of function -Go after the people that want to be on the system - you can tell who those people are because of how they interact. If they get someone specifically on the ball that can get completely trained and then is responsible for training everyone else in the company and takes care of everything, they are the ones that really succeed and really take off. Steve's analogy of the really tough sales with bad credit, so you can work with, work with, work with but at the end of the day, they are still the toughest sales. Go for those who have the budget and the structure that they are already ready to move forward. -If you can get someone who already knows what's going on, they can take off with that. Then you are not teaching them every little thing instead you have them understanding at least of business and so forth. -Laser focused training on adilas university so that you could link people to those videos and have small focus. -At the end of the day - it really takes someone who catches the vision and who wants to learn. -Adilas is a piece of clay but most people want a cup. So somehow we have to get them to see the excellent flexibility..... or maybe you just need people that recognize that an adaptable piece of clay is better than a cup. -Companies need to see the possibilities but you may also need to build the piece that they want or their dream business model and train them in how to use it. Maybe you'll have to play both worlds or both sides of the coin.... or maybe you will want to focus on one for now. -Steve knows the system well enough that he can go to a company and can really assess if the company can use adilas. And IF they are willing participant, you can really go places. -We have to figure out how to market our product to those who are willing participants. You have to fire customers in a market as well, just like employees or those who aren't willing to go anywhere. -A link on boxes with reps or something and those need help with various aspects - they could click a box and then a rep that has expertise in that area could help them or something like that -Small & medium sized businesses - that is the current focus -For some of the people - if you can't get to the trough and eat by yourself then maybe this is not the pasture for you. -The ones who want something for nothing are not the people that are the kind of accounts you want. Maybe if we don't babysit them so much we can have them help themselves... so then we need to have the training in there, videos so that they can go there, figure it out themselves and get going -Social media - if you could find a way to harness that, you could do hugely powerful things there -Sub homepages: with a graphical interface that talks about the functions for that page and pushes essentially the technology and the training right in front of them - that could be rocking! Or in a side bar with help videos, side bars, graphical interfaces.... just one thing to keep in mind is that some people really like it right now how it is, so do you want to change up how they like to get in and work? Or do you just combine it somehow with what you have now? -More and more the need is coming to be able to customize their application. To make it how they want it, what they want to see, or being able to create their own, they can pick and choose it how they want... -More user-friendly - perception wise - we have to keep the elephant, we just have to make it bite size -Use our advantages where we have them. So some of those are how nimble and flexible adilas still is. It is not so constrained, so instead of a little to go box, adilas is an eBuffet. -Find a rep that has a vision to put in a little adilas training center in a major metropolitan area. Potentially customers would fly others in for little training or what not... -We need more people on sales - how? Because the majority of the reps do consulting and setup.... but we need a sales force to really get adilas out there. -Call centers - if they would want to take the product -Sales forces - could you get sales teams in major metropolitan areas - could you use college students - could you spend a day at career and job fairs, get people on sales on commission, and then you could also get a setup team which is paid hourly or whatever -You have such a prime target area with college students because they are so hungry to get working and get out into a market -But we do need to close the gap between education and functionality -Maybe they need Brandon focusing more on development and we may need to get someone else that is there teaching -Maybe I need to meet some movers and shaker friends and get them going into the sales aspect.... -College job/career fairs -Let's get the support up there - let's make it accessible, easy, clean, organized, focused --- so that we can continue to snowball and get more and more people involved and as all of that happens, it will continue to build and snowball, snowball -eCommerce will be a huge opportunity - because to have a web presence to sell, it is about 8-20,000 to get that web presence and this is a much less expensive and excellent option -Plant analogy - the process of time is important in this process, as the plant grows -Joe's comment: You mean that I only have to sell them on one page/piece of adilas for them to sneak around the brick wall of tradition? -What is your pain? We have something that can help you with that? Think of how great a product you have for such a service - that is powerful for a potential sales person... they could sell any aspect for any businesses need. That kind of product gives a sales individual incredible confidence if they can understand that and catch the vision. -Have someone creating visual interfaces (custom wrappers) and putting them over the adilas engine They need people out selling adilas -So maybe you don't want to spend time training customers but maybe you want to spend your time training reps -Just keep going - things are growing and progressing but we need some amount of structure and support to really take it to the next level. -So maybe this is way, way future - but I know Brandon had talked about getting this into business schools and getting students to train and do assignments on that - but then what if you were to be a presence in that school at a job/career fair and they already recognize the name, they are already familiar with the product and they know it's potential - then all of the sudden you have this potentially massive sales, setup and user force -What does adilas do? - - - Basically anything you want! -Should we raise the bar a little bit and go after bigger companies???? People that will either figure it out themselves or are willing to pay for the -Brandon kept saying - we have a plan in place, let's keep advancing the ball and accelerating and just keep going. -We have a hosted solution - that is the time for that - so let's see what we can do with that -Do info blasts at colleges - 2 hour demo or in the business department - get out to people that can potentially go out and do your sales for you -Do info blasts with reps -We need to change the packaging of adilas - if you can dress it up it will potentially sell itself -We almost need a power statement for adilas - an adilas in 30 seconds -It is ripe! It is ready to get out. -Maybe it would be cool to create a cool college type poster - so it does inventory, tracking, accounting, grad school tracking, CRM, - but also research tracking, project tracking, family history, etc., etc., etc. -We NEED to get sales people! -Have Santiago go to the business college, go the University -Who are my sales buddies???? -Get a sales team leader - have them recruit and create a sales team -Also do I now other coders, developers, graphics, marketing people....???? -Steve mentioned that he has never gotten to the point where he has had more sales than we have been able to handle at this point -WE NEED SALES PEOPLE! -It's different from other sales as well, because you need those people with sales mentality but they also need to know the product -Brandon - it's coming, it's coming, it's coming.... -There are a lot of people ready to help but we need some people that are ready to go out and sale -Internet marketers - possibly a great sales force? -We need people that can network and get things going, advancing the ball more and more and more and more.... -As it continues to progress and expand, you will eventually touch those people who will want to create those sales forces, who want to take it farther. -If we do end up shifting the burning platform - no problem. We would all rather find bookkeeping people, they are great to find and you can get them almost anywhere, especially at the rates we could pay if we could get more product sold! -We have got to find a way to sell more product!!!! -We need to be able to support the support crew... it will get there... it's coming, it's coming.... -I enjoy problem solving things like this - so what part can I play to help -Shari -expressing that she realized she is part of adilas and she wants to help it grow... she wants to help lighten loads and figure out what can be done -We are here to support Steve - he needs help there. -We're seeing to the future - the compensation will come, it will come. -We might eventually need a tech support person that could handle all the tech support at some point - almost like a lot of these other services offer 24/7 support. Maybe though when you get enough clients, you can The key question for today: How do we find and create a good sales force? -Or maybe we won't want a tech support but have it fielded for someone that has an expertise in that field - like the adilas world/mall idea - get someone who is professional in that area - they can handle the support for that question - that will be the most effective and a shared method. But also if you have the support, education, and training in place -Sales will come, let's keep pushing on sales - but let's keep bringing up the support so that when we go to sale, we can have a huge infrastructure to support the sales that will come -Maybe we need to change focus and work on support - maybe I need to focus with Brandon on the user guide, wait on the developer's notebook and move forward on training accessible to helping reps, users and everyone get up and going. -If we could get those training videos up and going and have that support there - then maybe we can be ready to blast ahead and move forward and put in a huge structural piece for the sales to move forward -We could possibly get some of these trainings and adilas university up in a month or so - profiles back up on the world - something like a $50 profile -Adilas world - this deals with this above - Brandon saying that we could build that before next month's training - even if on a $500 budget -The railroad project - an example from Brandon about the LDS temple being built and the prophet discussing that they had to take a break and take time to help build the railroad and there was some resistance but once the railroad is done they could transport so much faster and were able to -We've got to figure out a way to sale what we have - and it is ready to sell right now! -It's ready, it's ready, we can keep supporting - so maybe the focus does need to change toward sales - because you HAVE to have some amount of revenue to move forward -Shari - if we build it, they will come. But we do need to help it grow & someday we'll have the big bag of candy & though it's not there right now, it will come -Shari is really helping coordinate, reach out, organize and helping to grow -It's here, it's built, it will come, we need the flow, we need to support each other and we need to move forward as well! -Keep moving forward! -Steve is there to look out for everyone, he wants to make sure every person is taken care of and he is concerned about that. Then we have to figure out what to do to support Steve. -Are you prepared to let go of what you need to? ----- That is a powerful question! We need to get schools on board with this - especially the universities -we need to get this involved at the University level - we need students on adilas as the wave of the future for operations tracking and accounting - if you got some school accounts you could potentially have some of your biggest paying customers and then you are creating an instructed user base, a sales base, a consultant base and you are basically priming the next generation to use adilas and be successful -We need to get adilas into the education system at every level - and interesting thought - if we are so concerned about getting our education up to the level we want - why don't we utilize any aspect we can that every educational system has to offer -We need WAY more people at trainings each month if we are going to continue to do them. Maybe we need smaller fliers to pass out individually, maybe we need free ads posted, maybe we need fliers up in prime locations - like the University - like the school of business - we need to do our part to bring people to come because. We should have at least 20 people at each class and hopefully the majority of them are new and potential clients *Why can't adilas right now, raise every customers base price, by some percentage, and every new client that comes in, put them in the new pricing tier It's already so much cheaper - maybe too cheap - people understand that rates go up typically by percentages every year. You guys have to know that you are worth it!!!! Automatically updates - you are not re-selling every few year. This product is not what people have originally had and just express that we have to increase the rates to match the product being given. -Make sure you ask people for what your worth and as you are worth more - you should be asking for more -You guys have to grow with how you are growing, you have got to cover your costs as well - we have to cover what we are offering you right now Raise the pricing structure a blanket amount and then if you have other customers that have been longtime customers give them a preferred customer discount (like a blanket 10% and maybe long-time preferred customers at 5%???) Adilas has been growing and expanding as have the costs associated with that. The prices may need to reflect that. -They want to get to the place where they can charge for usage rates but we are not quite there yet. -Adilas needs its own eCommerce - set prices for rates - create pricing tiers that you can follow and -Want to turn in adilas to a hosting company - the product is free but you will pay for what you do with adilas as the hosting company. -The what about(s)....? And the how come(s).....? Are what bury Steve and Brandon so if there is a way to relieve the pressure -If you can get people who will consume it themselves - STUDENTS - prime target, they already know how to use these, they like to explore, they just fly on this and they can consume it and pass it on and just go to town on all of this stuff The future of adilas is as bright as potentially anything could be - but maybe we just need the fuel to get there -Look at what the competition is giving and at what price to help create your pricing structure Does it need to move right now to the modular focus and so that they could get pricing in place - so that they are paying for usage - modular mode - a natural price increase time.... so some could snip off some pricing and others could add to it for holding their pdf docs and what not - so people are willing to pay to access that in the modular unit -Potential for investors???? -There are a lot of challenges with this particular business - so much there - but it's a little different beast so how do you handle those challenges -We need to get some canned demos and some canned commercials -We need companies that have someone who can be the ones writing SOP (Standard Operating Procedures) and move forward on that -You can charge in many different ways. By usage seems like it would be the best - but you could charge by "room", like the kitchen, or the garage, or.... *You could get a change in the price right now when you set people up with eCommerce you change adjust their prices right there. And all those clients who are not going to use eCommerce, let them know you are going to have a blanket increase of 10% or whatever This is something that could be done right now! ** -Let's get the younger generation involved as much as we can - they are primed to work in a system like this *Great meeting - lots of input

	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 1739		Daily Tasks	8/26/2013	• Small update about where we are heading using students, interns, and such. Posted the update online in the news and update page. • Emails and light tech support. • Recording notes about World Building concepts. Sent a small email to Brandon Mull (author) about using his five main points for a good story. They are: characters, relationships, trouble, decisions, and consequences. • Working on elements of time for recording the Bear 100 race with all of its people and racers. Small code tweaks. • Posted files and updated the update page about students and interns.

	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 2143		Adilas 3 Day Training Notes - Logan	8/27/2013	ADILAS LOGAN TRAINING - AUGUST 27-29 Day 1 - August 27th -Began with stock/serialized units. Class member’s husband is in the car dealership industry, so showing a little bit of that to start off the adilas training. -There are some really neat things you can do with serialized stock units and inventory.... lots of neat functionality... I can only imagine how incredibly helpful this would be for people in this industry to use adilas.... there is so much functionality with adilas, it is crazy! Now we just need to figure out the best ways for other people to see that and start using it - sales! -Adilas does custom documentation - so they can do any documenting that you need, the forms can be populated with all of your data in adilas - SO many powerful tools! -Stock units actually have huge pieces within the puzzle that they can hold and connect to. **IDEA: What if we started doing something like a weekly demo. Maybe pick a time slot on a Friday or a time slot that changes weekly, 1-2 hours and Brandon or Steve or someone could do the demo. It could be open at a location nearby or even through GoToMeeting as well. We just need way more people at these trainings... we need people here so maybe if we could invite just tons of people to demos... we could get some greater interest. We need to get the word out. People only really come to adilas trainings if they use adilas, so we need a quick enough exposure that they are interested in talking more. Because most people cannot dedicate anything like the kind of time that our trainings are set for but they could probably squeeze out an hour for a demo & questions and answer session to see if they are even interested. We could pass out flyers with some catchy info and the times. Papa could record it and maybe from some of those sessions, we could get some little demo videos that people could distribute or users/sales people/anyone could use to do a special little video presentation demo of adilas. So maybe we need a super snazzy 1/4 sheet flyer and we need to get spreading the word abroad. People have to know about adilas and get some exposure to it or they can never use it. Even if we try to use the huge asset of the customer base already using adilas. If you could set up the demos, users could invite their friends to get on and watch or they could access some of the videos we create. Especially if we could get even a super great 10-15 min demo/overview of adilas and get it out to your users. They can show that and give personal experiences... but basically give them some more tools to help them market adilas for you, as well as incentivizing this process in some way. You might get some power users that realize that they really like sharing adilas and they could get some good stuff going.... Just some thoughts. Maybe we could even do short demos for each of the main "categories" or ways to use adilas... like a quick demo for CRM, POS, Inventory tracking, Backend accounting, etc., etc., etc. Maybe it would be cool to even do some little videos like we watched with Brandon Mull.... just short with him explaining important points and concepts.... like a "What isn't adilas?" video.... or some adilas overview videos Maybe papa needs to come with us to Colorado this next go around and film some demos, film some power users, film some commercials, get some goods on all of this great stuff we have going on. He and the mama could join us. -Stock units - you are able to add multiple subs and can track so many other related fields - a lot more info. Once you set things up on operations - they start cascading themselves throughout the system... behind the scenes, it is already showing up in other places... we are feeding accounting automatically just by doing operations. -As you do your day to day transactions - accounting follows those actions -I think it is really constructive to the learning process, when we go back in and fix problems... or we didn't have what we needed for a specific goal, so that we can go back and work through the process of putting it in -All Data Is Live And Searchable - it is amazing how quickly the system can recover data, even year’s back, that is such a valuable asset! **Chart out the normal flow of the business, understand their needs, etc. Then you can go in and help cater the best adilas fit. -We setup going through a wedding planning/catering service type business - it was really good, we got to practice with various elements including parts/inventory, PO's, recipes, elements of time -Adilas really comes alive for people when they finally relate it to themselves, or problems they have had in their own industry/business, or when they finally understand how helpful it is for their needs, it somehow seems to open so much more after that as to how helpful this could be for everyone. Dream it up, plan it out, make it happen! -What you have in your adilas right now is available on eCommerce right now - that really is pretty amazing. Incredibly quick and cost effective and you have that functionality right now! Captions on the pictures especially (and searchable texts) are great to add because they can be found by search engines, etc. They show up on your descriptions on eCommerce. So when you learn how to play, there is so much you can do! And SO amazing that it tracks directly to your adilas and all of your inventory, real time, live data. AMAZING!!! -A good practice would be to check the history homepage every day when you pop into adilas. It would tell you things that you have ready like reoccurring invoices, or possibly elements of time you have scheduled, or target dates for things to sell, etc. -Great tools so you can adapt your web pricing and what you want to show or hide or if there is something that you would like to be priced differently for one or the other.

	AU 2144		Adilas 3 Day Training Notes - Logan	8/28/2013	Day 2 - August 28 -Today we are trying to focus on elements of time, customers, and flex grid type applications. -Telling the story adds validation and may be more important than just a list of numbers. If you have the back-up story, that gives validity to your numbers and your flow. The story is SO important. -Cause and effect - perpetuation, cascading effects, etc. -Systems: everything affects/effects everything else. Interconnectedness, how characters interact, play and associate with each other. -You want to categorize and detail things out so that you can know where money is coming and going from your P&L - so much better to have that on the invoicing side - because that shows such greater details. And you don't want to double play/book, you don't want to show the same things from invoices and deposits on your P&L - so defer those to invoices if possible b/c there is much greater detail. And it cuts down your time on the deposit side, so you don't have to try to detail it all out there - it is already on the invoice side, yeah, happy day! Law of Deference - deferring to the player that can hold the most detail &/or be the most effective for your business processes. -With interest that accrues - a good way to go might be to just make another quick invoice with interest expenses - it would be good to have that as an "item" if that happens often in your business. -Good teaching view when Brandon made the invoice really tiny and circled to show what part was the main, the line items and the payments... that was helpful, b/c not everyone knows that. -Tell the whole story... adilas and you are documenting everything going on... tell the story with all the details. -System history - pretty cool stuff! -Good read: "Who Moved My Cheese?" We should do a little adilas overview - like some of the things Brandon was talking about how things are changing SO much and how we need to change along with that and how adilas has. I think it is really instructive to discuss some of the history and some of the tradition that holds things back or causes some tensions, etc., etc..... Another really good description/instruction with the discussion of the more rigid traditional accounting idea w/adjustments, etc. vs. objects and data over time, with checkpoints/doors, holding places, advancing things letting it flex, pulling it back in - allows for time to occur as it does with this model. It would be great to get some graphical representations of these. -Tell the story, that is what everyone wants/needs and it is meant to do. **WHOA! I feel like I have this realization every time I am in a training that adilas has SO much more potential than I even realize, than anyone in these trainings even realize! Amazing potential with eCommerce and web presence... that you could expose whatever you wanted them to see if you have adilas customize it. That is amazing, so you could have them schedule themselves online, then you could prep inventory if you needed, or you could have them satisfy their own accounts online and pay their payments, etc. Such an incredible asset! Allows you to make smart money decisions, time decisions, and a predictive approach to your inventory and so forth. A good example here is mom's herb business and being able to see what people want and then you can make sure to have it when it comes. Super sweet stuff! *You dream it up, adilas wires it up! "Dream it up, we'll wire it up!" -There is NO business that won't love and eat up that model!!! Huge, huge, huge!!! -On the tick list - to get a generated email or confirmation order, etc. Adilas is trying to shift to a just in time model as well, allowing their clients/customers to pay for the future development. Adilas World - a mall for professionals - SO cool, what a great asset for customers and for professionals on adilas world. Already in concept - super cool stuff on the way. "What doesn't adilas do?" IDEA: Adilas needs to become a just in time venue as well - just in time development as people are paying for that development and so forth, etc. You can skin adilas not only just with a fun or custom interface but you can cut out all the unnecessary steps and speed up the process super-fast - linking it straight to your pieces with no problem. *Incredibly powerful engine with adilas - now custom look, feel and flow! Neat! -Cool little teaser interface - with the school data tracking --- API: Application Programming Interface -Flex grid - a front end programmer/user created database - wow, powerful! We all loved the little school interface - I think it is so powerful, even though a lot of us can imagine how you could have different interfaces, it is SO powerful to see it! And it is so fun to explore, or see where some of the little "buttons" go, and to see how fast and efficient it is for their uses. -If you want to record the data, you can record the data. You can copy and paste full emails into the log notes, you can put what you want in there. -What is your goal? What are you trying/wanting to accomplish? These are critical questions to answer to help direct your flow, setup, etc. **IDEA: from Tanya, maybe create a flow chart or rubric of sorts to help ascertain what a client needs. Maybe it's too dynamic to have a chart but maybe you could come up with something generic to help reps/consultants ask the right questions to help them get the best use out of adilas. Or really it could even be accessible to users, then they can self-assess what they want and then maybe have a direction to head - education/training. Future: giving users the ability to be their own front end programmers. In-line customer work - future development. -Adilas is currently a bare bones model - which is great because that means you can dress it up basically any way you want. Powered by the adilas engine you can dress it up as you like it. -Can skin eCommerce with one of just a couple easy pages - skin it on the top side however you want to present it. Big giant buttons, easy, appealing interface, so many cool things. WOW! *Adilas has all of the data and lots of power - do you want it to look pretty & custom? Great - get a designer. Get a developer, get things how you want them. -Just like with other things - people don't know, what they don't know - adilas. There is SO much that is possible! UNLIMITED POSSIBILITIES!!! -Web people will understand how to pass data and variables to different places. -"Never let a crisis go to waste" – was said satirically today in reference to a quote from the past, but that truly is a valuable point. We hopefully don't let crises go to waste in our life - hopefully we change or adapt or flex or jump, shift whatever, so we don't get squished, so that we are better prepared for the future. Sometimes we try to do all we can to avoid a crisis in our life but they are a powerful means of change and can be positive in so many ways if we respond. Like Pres. Uchtdorf says that it is not our adversity but how we respond to it that creates our story or our destiny.

	AU 2145		Adilas 3 Day Training Notes - Logan	8/29/2013	Day 3 - August 29 -Today we are mainly trying to focus on the back-end accounting functions -Money coming out of your bank - expenses - from various things like A/P, inventory, users, vendors, rei's, splits(A/P), etc. Which then shows up on your P&L and then also affects your balance sheet. -Money coming into your bank - deposits - from invoices, A/R, -Ideally - it is great to categorize your stuff before you get into adilas - set up your cans first thing, then it can really help to track things - like right here with expenses - what are our expense category and then if you have that all set up, you can stuff thing in the correct category -A lot of things are tracking automatically to the P&L and the B.S. but if you want it tracked out at a finer level you could set up more categories or something but again remember the Law of Deference - deferring to someone with more information for example deferring to the PO vs. the expense one line description. System maintained vs. user maintained balance sheet items - system tracks it or you need to add it. (User maintained B.S. item - like the company truck, a loan, things that adilas doesn't know what they are going to do. Other things they already map/track - system maintained) Line it out in word or on paper - once you set it up and have a flow and goals it is amazing how much easier and focused it makes things -System maintained example - once a PO comes in with inventory your B.S. automatically increases with assets - it flows there, but also the A/P flows in there to your balance sheet so they are automatically flowing through. ----Financial flow calculator and worksheet - just an educational/instructive tool - does not save in the database, just a tool -The Income Statement (P&L) feeds the balance sheet with net profit - that is fed automatically from adilas - the connection between the two -Telling your story accurately and detailed creates your accounting ???'s for class - Requests for class questions - what happens to my sales tax - how and where does that effect things/end up? What happens with shipping? ---- Brandon did a great job covering sales tax. Freight - business preference and flow - out of gross profit or net profit, COGS vs. Expenses -6 accounting categories - Revenue, COGS, Expenses, Assets, Liabilities, Equity -They can automate things that are pretty standard, structured or a more rigid process.... but the minute people have great variability in the way they function, then you have to leave that more open and more maintained on the user level. It is still gathered and in its holding tank - to wherever it has advanced to and then you can go and advance it along the line as you need and are ready. -End of the month, you are going to have to manual/physical entry your sales tax - there are just too many variables to automate it... so you know you're going to spend a little time doing that. But all of the data is there and gathered and it is still probably at least 75% there and you just have to wrap it together and put it where you need it. Real data on real time - not having to make all these adjustments -Old school accounting - deals with numbers; adilas accounting - deals with the story. -Balance sheet - a point in time (a single date, a snap shot in time) .... -P&L/Income statement - more of an accrual and over time, what is happening through the year and how it is continuing, rolls over your fiscal year as your profit and loss statement (the pulse). P&L feeds the balance sheet with its net profit - to the balance sheet. -Trying to teach cause and effect relationships. I cannot even believe how much easier it is tracking your accounting from the operations side... it helps you understand SO much more of what is actually happening! -Full record/transaction of everything that happens! *Possible new setting - talking with Cheryl... about getting a potential setting to distribute the cost of freight across however many items you have so that it can be added back into the cost of your items so that you can cover that cost and attribute it this way within your inventory. Probably not a high priority - right now mom just has some extra prep work to do on the PO side to figure out how much she needs to add to her items to make sure she is marking things up enough. -What tool do I need for the current job? Adilas balances day by day by day.... traditionally a lot of accounting settings balance at the end of the month and often times there are huge disconnects that are really difficult to account for or making multiple adjustments. There seems to be a huge disconnect when accountants are looking for pennies in certain scenarios and have everything detailed out and then they can get to the end of the month and not account for some huge amount and then they just make an adjustment. That is a huge disconnect!!!! Adilas - all in one, operations will lead and we will feed accounting according to what operations are and do. Adilas - incredible operations tracking that can take it to the accounting level. Not required but available. -If you play with adilas on the fairways and the greens (the way things automatically track through) they are making all these little connections for you. -A really great question about Gift Cards really illustrated the point to me again that understanding the story and how things flow really helps to know where you need to track or put something or what the next step is. So we need to add a user-maintained balance sheet item for our gift cards here - we needed to hold it as a liability. *So cool that adilas will be moving to a model where they can ask - okay, who would like this? Who wants to help fund the creation of this project? -Gift Card tracking (lunch card tracking) - future development for adilas to track it out to the detailed level where it is automated and tracked to the balance sheet -Pre-paid items: you have to hold that as a liability at least until you have expirations or what not.... -Future of adilas - load balancing -Wanting to take adilas out to the serious balance sheet level? A/R, A/P - automated. Inventory & banks also automated and they are the 2 biggest keys you need to get in line to head to the Balance sheet level. Get the stuff that feeds in automatically going and feeding in and then you are ready to take it to that level. Record the story! Record everything that you do! Record everything that you do physically and then if you need to do a little tiny bit of connecting, no problem. -The heart of adilas - objects and data over time - this tells the story -Great little analogy I like that Brandon made about the horse leading the cart - which we talk about over and over as being the most ideal way to get things done, really it is to move forward with any efficiency.... but the funny analogy he said was that when you have things set up in the right way, with the horse leading the cart, every once in a while the horse is going to poop and you have to do a little clean up. Over 75% of the accounting is already done just by leading with operations but every little bit there is some clean up - so there you can use your balance sheet and some other tools to clean up a little. It's just part of the game, but SO much easier at the point, to just scoop up a little poop, or do just a little bit of clean up and everything else is just rolling along and moving forward with ease and efficiency and we are prepared to scoop up any little items that we need. :)

	AU 3653		Brainstorming: New Server Structure	12/20/2013	Brainstorming with an intern on new server structures: - New databases get corp id – they don’t generate them they get assigned - Master controller – Mother ship o Cluster Controller – Master Corp id’s • World Controller – Master User id’s - Corp key id – set a default to 3 alpha-numeric. But let them change it. Alias must be unique - On vendors & payees – we need to allow vendors & payees at will. However the payee id. - Inter world id #s & outer world id #s – just for users Master Controller – Universe Level Master Corporations: - Corp id - Corp name - Corp key id - Corp key id alias - Cluster id - Corp status - Corp admin - Corp address 1, 2 - City - State - Zip - Phone - Web address - Corp email Master corporation history: - Corp history id - Corp history date - Corp history change Cluster Controller: Domain on server level - Cluster corporation - Same as master table - Minus to increments on corp id - Minus cluster id - Plus data source id Master User: - User id - User first name - User last name - Corp id - Status Master User Corp: - Id - Corp id - User id - Status User request: - User id - Corp key id - Status Cluster datasource: - Id - Datasource name - Notes - Start date - End date - Status Cluster user: - Same as master user - User login id Master Clusters: - Cluster id - Cluster name - Cluster alias - Domain - Cluster notes - Cluster start date - End data - Status - Cluster version User History: Master User Corp History: Cluster User Corp: Table to hold login records. World Controller – database level – if more than one world per database it becomes a virtual solar system. Corporation: - Corp key id - New column - Alias disable auto increment on corp id Payee: - User id World Controller Continued… - Where can people switch worlds (modify) (as well as login page) - Change datasource id - Change payee id - Record who accesses which corps - Super user login o Web services o User info o Reporting service Master Controller: (cont) Webservices: - New corp - Update corp - New user - Update user - Password change - Request access to world - Accept/deny request - User request applications - Help file access - Retrieve update - Record update Application: - Modify structure – see records - Run reports Clusters Controller: (cont) - Reporting web services System to move or extract someone to a new location Brandon & intern – Brainstorming on table design for universe and cluster level tables and database stuff. (See scans in photo gallery)

	AU 2132		Adilas 3 Day Training Notes - Denver	1/28/2014	JANUARY 2014 DENVER ADILAS TRAINING - JANUARY 28-30th DAY 1 - JANUARY 28th -Brandon was going over the newer graphic he has made, I think he calls it the adilas GPS graphic, but there has been a lot of thought into the order of that as well. Again like the map, things that are related are close to each other, or other related items are across, etc., etc. A great learning tool and it was a good way to start. -PO's - an inventory tracking tool - getting anything into the system, even internally creating product, etc. Demo/Intro with Kate: -Great comment: she said wherever you are you can always start at the top and work your way down and you are bound to figure out what you want or what you need to do. -Control - instead of a right click, choose new tab... good way to quickly open a new tab -What page are you on? - You always know exactly where you are at. -What is the goal? Plan it out... then you can walk through the system *IDEA: The ability to save barcode settings.... so much of what people are wanting for many aspects though - and adilas is working on many of these... basically people want to be able to do what they do/want and save those settings for their purposes. IDEA: We may need to clarify this idea with someone who understood exactly what was said - but I think what I basically got was - they want a way to be able to track/calculate how many grams the patient ends up walking out with. Associated with the product, so that they can track how many grams add up as they add products to the shopping cart, so that they can make sure the person does not walk out with more grams/ounces then they are allowed to. **IDEA: with packages... package ID numbers and once you sell it, it can go.... Brandon seemed to understand what was meant by these ideas... one of the class participants was talking about this. Cleaner way to move through inventory, to pre-package and back stock & only see what is currently out in your inventory so you can work through that. -There is a definite importance and need for people to understand practices or what tools to even use to accomplish various processes and tasks.... granted there are many ways to do lots of things... but there are some "BEST Practices" -Returns: Think negative invoices -Departments: set up tax settings, relationships between department and users.

	AU 2133		Adilas 3 Day Training Notes - Denver	1/29/2014	DAY 2 - JANUARY 29th -Steve was talking about some good practices and was expressing that with employees, limit their permissions, such as - don't let them see the cost in the cart - because they could change that. He expressed that he even likes to run with that off, since he has the ability to turn it on & off, then he can make sure he doesn't inadvertently change the cost. If he needs to, he can go back in and turn it on again. -It is important to understand the permissions and know how to use them! -I like how Steve kind of works his way down or through the page just teaching and discussing what things are or what they do... very helpful, great for teaching. -Once things are in the system.... its RELATIONSHIPS, RELATIONSHIPS, RELATIONSHIPS.... assign, attach, connect, sell, buy, pay, receive, RELATIONSHIPS... -Are we able to save "Favorites" buttons yet? *IDEA: Adjusting the tax category as a drop down, so that you could adjust things as needed for tax categories with pre-assigned values. But Steve was expressing some of the difficulties of tracking this potentially??? Some brainstorming still needs to occur on how to deal with different tax settings for specific items or categories. -Enter once - use many! - This can help your life tremendously... they will use some of these same principles and concepts that adilas runs on, (even think eCommerce for one instance), to help solve these problems they are trying to manage with everything changing in this industry. -PO - Purchase Order or Production Order - for this industry and their plants, they use a lot of this as Production Orders -It really is AMAZING that the adilas application is truly a model that is a huge toolset to let you run your business however you want - your flavor!!! So many other models are so rigid. Adilas is huge! But I also see how that can be a little intimidating for people with adilas. Because it is a giant sandbox and you can jump, hop, go here, go there, stop mid-process, come back, etc.... That IS huge flexibility!... But different for people to understand how to use, it takes a different approach. We know this, but it is still interesting to see it over and over again. -How valuable to be able to take people's ideas - because they know what they want to happen - and be able to help them make that happen for their system, for their industry. -You can do some powerful stuff with flex grid for sure - something new that I hadn't thought of. Brandon was saying you can filter your flex grid data, export it to Excel and then do all sorts of math calculations with them to help you adjust what you are doing... that is a great thing, good stuff. -Neat futuristic - application flex grid tie-ins - such cool stuff coming IDEA: Steve was expressing some good ideas from Randy about scanning the tags from the top of an order down and then copying & pasting things and changing one function. I really didn't get entirely what was being said b/c it was pretty quick but seemed very understood by those in the industry. Anyhow some ideas about RFID tracking.... IDEA: Again, some huge possibilities and help with packages and tracking through packages.... IDEA: A quick search option for the RFID tag - search in invoice line items, PO line items and the actual part - return with variance, how much you have received when it began and where it is at now, or where it has gone. **IDEA: On Elements of Time - is there a way you can categorize things per location or per user group - so who gets to see what.... almost like pre-filters if you will for locations or user groups etc.

	AU 2131		Adilas Team Meeting Notes	1/31/2014	ADILAS TEAM MEETING - JANUARY 2014 (Steve, David, Craig, Shari, Brandon, Shannon) -Taxes for MMJ - put it in the parts section, or on the location homepage - basically being able to change -More one to many - on the categories -Those 2 pieces together - multi-leveled categories (also important for eCommerce) + the tax category (so the ability to set the taxes per category) -Packages - RFID -Split Cart -Custom Labels -Ice Down Date - pop-up calendar, maybe these two would go well together since we are already touching every page -Content server -Financial history page - this will be a great asset for the future. Probably a lower priority currently but this will be a really neat feature. -More validation on different pages - the example was of a B.S. item on an e/r - but more things are coming with the balance sheet -A search sort by column.... but maybe that could come later -Bringing in things this year to enhance some of the smaller feature or functionality of adilas.... -Button links that open and expand - like on the printable invoice, allows for more space and it can open up -What if you were able to save setting on reports? -Bring the Report Builder back - save your settings on reports -Expand out the "Chooser" - Exposing all approved customer interfaces - approve all of the generic customer interfaces and then you can put the custom ones in their own special place -Some of these need to be industry specific - to approve for everyone.... For example - there are a lot of custom pages for MMJ and it would be really nice to be able to know what needs to be assigned for anyone in that industry -Steve's making a Splash Homepage for MMJ, sounds great! Basically they get in and can decide whether they want to go from the Splash page - this can be in the chooser -Expand the GPS graphic - it would be really neat to expand the new GPS graphic and make that into a really neat interface and homepage and then taking it to the next level - the graphical interface currently would be the main or home.... but then expand, so when you get into a sub homepage then you have about 3 sections... Section for the sub homepage, then little graphical buttons for all of these and your next steps... so what you can do from that homepage... and then what you can do with the data and having a special input link so you could type in the ID number for the item and then click on the graphical link you want - i.e. the main for that object, the line items for that object, etc., etc. -Graphical display or something that we can continually use to show: Tips, news and info -User guide: Tips, tricks, helpful info..... -Prep the consultants - so that you can turn on those 2 main permissions and then let them go to it and set up those companies... that would be fantastic and help take the load off of Brandon and Steve so much -Expose eCommerce - we could add validation, so if you don't have certain pieces it won't let you move forward.... let the system be the bad guy, work it through validation **Empower the users - that is really what so many of these ideas are about -Allow people to setup their own Merchant Processing - all of these things would be so great - it empowers the users and takes work off of adilas -Allow them to setup their own logos... set up standards for what they need to have or if you don't know how to do a logo you could have a link that they could feed that to Russell or other developers that could work that, bill them directly, and create quite a few logos for them (Steve talked about this really cool idea that he heard from a gentleman about what he did to get his logo online - logos.com or something, but a really neat idea) -3rd party settings: Adilas World NEEDS to come into play - so many skills and so many people that are ready and willing to help with things happening in adilas.... people want to play -Developer's Notebook - get our back story -Adilas University: Get the Help Files up there, SOP's, User Guide, Videos -Training: multi-day mini sessions -Categorize our videos, rate them, get them ready to be consumed easily *API, API, API - that is where it is headed, that is where we need to go - MAKE ADILAS CONSUMABLE!!! -Generating revenue: Set up your parameters & standards or maybe you do want to keep if flexible - but your setup and optimization fees, activation fees, etc...... -Having an adilas team that can pick up so many of these pieces that people are willing to pay for... pick up the money and projects from those that are around -The byproducts are worth far more money than the actual code - training, consulting, custom pieces, ..... -Training - where do we want to go with this???? -Feb & March - Logan. April - ???? - Shari even offers one on one training at the training meetings that she does not charge for... good ideas, good stuff, such a great place for networking!!!! -Mini training sessions - and charge for the mini sessions, topic specific possibly??? Or really super flexible, whatever you want to do with it Adilas World - networking capabilities, Our need is in trained people - there are so many clients and potential clients out there - but we NEED trained people - once you build that up, though there is the initial investing, then they turn around and can produce so much more -Who can I grab and train? We can get people busy doing work in so many ways. -Setting up mini sessions - let someone set it up and go with it Adilas eCommerce up and going - then you can start showing some of these pieces and start charging for some things -Having a team that can help pick up the money - $$ - Custom pieces - having someone pick up what is already out there -Custom pages - they are getting what they want, they are happy and those are some solid customers, -Steve's charging $100 per client for setup right now... or if it's tiny $50 - very cool stuff -Custom servers -custom boxes - we will be having clients that will want this, it is coming -Hosting - this if following a similar model to how we even have been setup on servers, do you want your own environment, shared, semi-shared, etc., etc. -We are excited where things are going and we will just keep moving forward! :) -We need to help people feel like they can succeed once they get in adilas... we want to empower the users... but we don't want to make them feel like they are alone in this big forest. Good stuff coming! -Trained people are going to make money - we need to help them get the skills. -Interesting - it's often not when people are slow that they want to get all their stuff together, but it's often when they are busy and they feel like, yes, I need help, I need to get organized, I need to get things together. -Certificate of training - makes them feel like they have value. -Steve would also like to work into doing some workshops in some big cities, maybe do some consulting, networking, that could be some great work -Possibly Texas for April training - that could be a really neat opportunity -Work some mini sessions in Denver. That could be huge! Charge for the mini sessions, you have so many potential workers or people teaching. -Shari, was also expressing that you could do an 8 hour session or something....then it was inputted that you can break it up with some flex time, but then you can say from here to here we are covering this (i.e. 9-11 E/R's, 12-2 B.S., 3-5 ???? whatever you want).... maybe give yourself an hour in-between the sessions so that they can network and you can move on to your next training on time... etc. That could be a great setup -Or schedule some time and create sectioned mini sections so that you can have focused classes that they can pay for. Great stuff! Charge $25 a class. -Chatting about someone in Texas that could set us up with something - a venue, etc., etc. *Mini sessions in Denver - because Denver could use a training session every month for sure - take care of the user base in Colorado, keep things going here -Longer training elsewhere -All sorts of stuff - have specific topics, or even industry specific topics, you could have a rep/consultant only class -With the mini sessions - if we set it up for a focused topic and ask people to pay, then we do not stray from that either, that is where the focus needs to be -Trying to get more people to the Logan trainings.

	Adi 838		Packages and Conversions	2/1/2014	Steve and Brandon had a brainstorming session on Saturday night. We talked about taxes per part category. World building levels and tons and tons on parts, conversions, and packages.

	AU 2036		Daily Ideas	2/19/2014	Brainstorming notes between Brandon and an intern dealing with the adilas API: Notes from a brainstorming session on the adilas API (application programming interface). Brandon and an intern went through the code on the first round and then had a discussion about ways to improve things and help to standardize processes. - We would like to offer 3 data exchange formats. They would be JSON (java script object notation), WDDX (web distributed data exchange) and eventually standard XML (extensible mark-up language). - All API calls will be funneled through a single page called adilas_api_calls.cfm. - Currently we have both FORM fields and objects that get passed in. Our plan is to move towards objects. - As we transition from basic FORM field submission, we will need to alter the flow and order of things. - Eventually we would love for the process to be mostly database driven vs. customer code or special include files… Ideally we might need a mix. We could use the database for standard operations and then use the database plus custom includes for any custom work. Think about a fully automated way of getting a mix of both worlds. - We need to build out the documentation and the database for the API. Help people! - Setup a searchable sub section of the API. It would also be cool if we could categorize and even visually display API functions and methods. Use the adilas interactive map of the GPS (global positioning system) core interface to help organize and display options. - As part of the API, we would like to setup a 3 step testing environment to help with testing. Think of a virtual playground of sorts. The 3 steps would be: o Prep it – a form that allows preset options and input. o Convert it – this would format the data and show what the request would look like. And the… o Run it – show the results and what that would look like. - As a side note, it could be fun to allow both test and live data to be submitted. It might be cool if the developers could really see things in action and then mimic those actions in their own projects. - On a permissions and settings level, we want to help our users, clients, customer, and outside developers. Basically, the system will have to have a number of options to help it be dynamic and flexible. - To list a few of the options, we talked about: users, corporation (worlds), windows and doors (access), usage, limits, passwords, and security issues. We even talked about certain things that would not be allowed – rules of the game. - We determined that we need controls on the universe level, the world level (corporations), and on the who (users), what (permission and methods), when (optional times and dates), and where (IP addresses and domains) levels. - While talking about security, the intern mentioned about checking the existing list of black listed IP addresses and deny access to those without even checking the data. - Every method or API call would need a password. - We want to be able to track usage and history of who, what, when, where these API calls are used. As a note, the history may need to be added somewhere towards the top of a call or just before it gets returned. - Make sure and run the API over full SSL (secure socket layer).

	AU 3671		Tech - Adilas API	2/19/2014	Adilas API - JSON & WDDX & (XML – later on) - Adilas api calls – cfm - Currently we have both FORM & objects (required change) - Change the order of things - Love it be database driven (later on) vs. custom code or includes… o We might need a mix. Db for standard operations and db plus custom includes for custom work - Doc & DB – built up and detailed out - Setup a searchable sub section of the API - Categorize the documents and pages and methods - Testing or playground environment - 3 step environment: o Prep it o Crunch it (request would look like) o Results (response would look like) - Users, corps, windows, doors, usage, limits, passwords, access, and security issues – not accessible (special) to outside users o Universe level o World level o Who - users, what – permissions & methods, when – ?, where – ip addresses, domains, etc. - Check existing black listed IP addresses - Method password for every call - Who accesses these API calls – history towards the top checks - Run over SSL Brandon & an intern working on the adilas API: - 100+ permissions - $500-1,000 methods - Linker – users; Linker – methods 1. Prep it! – just from fields 2. Convert it! – show it form & cfdump (Full Circle) 3. Run it! – form & cfdump; ½ FORM, ½ objects

	AU 3676		Brainstorming - Conversions & Packaging	3/4/2014	Brandon and an intern brainstorming on conversions and packaging: (Please see sketches on scan in photo gallery) - Units of measure - Link id - Line items - VIN - Cost per - Date/time column - Parts – track - Unit - App var name - id Packages Brainstorming & Whiteboard Session: (Please see sketches & whiteboard planning on scan in photo gallery) - Conversions – unlimited - Packaging – limited - PO – main, lines, pmts - Po invoice line items o Parts o UofM - Invoice – main, lines, pmts

	AU 3681		Brainstorming - Adilas Business Functions/Features	3/20/2014	This is a brainstorming document that was done from 3/20/14 to 3/27/14. It covers all 12 of the major business functions that adilas provides. The goal here is to focus more on the “sizzle” vs. the steak. The brainstorming was done by Brandon, Shannon, Dave, Cheryl, & others. Goal/Objective: Show & tell all 12 Business Functions/Features – here is what this can do. Brief definition – this is what this is. - What functionality – per business features – what, what, what – show me WHAT it can do. WHAT features does it have…. - From start to finish – follow this path all the way through – start to finish & review it 1. Sales, Inventory Tracking, & POS (Point of Sale): - Serialized inventory - Consignment inventory - Hide/show line items (hidden line items) - Advanced add to cart items - Barcoding - Package tracking - RFID Tracking - Custom labels - Paperwork – custom - Content Management - Photos/Images - Shopping carts - Duplicating - Vendor specific items - Generic items - Service items - Tiered pricing structure - Interface options - Dynamic cart interface - Quote – save as - Discounts - Contract pricing – using flex grid - Adjustable invoice styles - My Cart Favorites – Buttons - Recipe/Builds - Adjustable tax settings - Multiple customers per invoice/quote - Mixed tickets - eCommerce – Point of Sale options - Merchant Processing – credit cards - Customer queue - Item usages - Flex Grid - Transfers between locations - Update inventory count options – shrinkage/loss - Returns/refunds/exchanges - Tie directly to customer PO’s – dynamic fields - Custom search options - Sell anything! - Editable after the fact - Record notes – printable & non-printing - Searchable notes – searchable data 2. CRM (Customer Relationship Management) - Unlimited logs - Unlimited follow-ups - Calendar - Appointments - Bill for time - Track special data – customize your database - Additional contacts - Custom data fields - Paperwork - Photos/scans/images - Content Management - Export to Excel - Email/text message - Tie to specific sales associates - Current receivables – past history - Backend eCommerce login - Pay portals - Statements - Apply payments - Purchase history / statistics - Link to any other application piece - Custom search options - Trending & marketing 3. CMS (Content Management System) - Photos, scans, images - Reference any file – local, remote, physical upload - Unlimited & searchable reference library - Documentation - Custom documents - Paperwork - Contracts - Custom mappings - Direct to eCommerce - Your data, your system, your world, your way! - ??? – Something more… - Custom search options - Virtual World Building - Look & feel - What do you want? We’ll serve it up! - Mix & blend - Point & click interface 4. Online Expense Tracking - Reimbursements - Expense accounts - Payments on account - Payables - Access from anywhere - Enter data from anywhere - Print checks from anywhere - Bank reconciliation - Automatically cascades to P&L - Check requests - Check printing - Multiple payments - Documentation - Split between location - Aging, due dates - Dynamic reporting - Exporting to Excel - Bulk verify - Unlimited banks - Payroll - Custom search options - Photos, scans - Digital filing - Paperless office - Automated…. ??? - ACH & EFT’s – wiring money 5. Payroll & Timecards - Digital time clock – clock in/out - Admin time cards - Admin time clocks - Commissions - Salary - Overtime - Split deals - Hourly - Year to date summaries - Unlimited departments - Auto calculate federal & state withholdings - Summary reports - View/print my pay stubs - Bulk timecard options - Check writing - 1099’s - W-2’s - Automatic annual updates - Custom search options - HR management - Needed piece for every business – employees are used in other pieces of the puzzle – common denominator – wrap that up and present that well – potentially, on our side, take a day and create a few custom interfaces (that you could even flip to a mobile app) and just have this as an entrance (or get your foot in the door piece) - Compensation - Holiday pay/hours - Vacation pay/hours - Sick pay 6. Calendar & Scheduling - ANYTHING - How do you use time? - Appointments - Calendaring - Scheduling - Reservations - To-do lists - Projects – track subs and totals for projects - Servicing - Project management - Pools - Rentals - Dispatching - Bill for time - Reminders - Follow-ups - Notices - Dynamic naming - Create & name your own time templates - Scans, photos, images - Content uploads - 4 different report types/view: calendar, time slot, groups, & details - Advance searching - Add subs - Tie to customer, vendors, locations - Queue things to be invoiced - Project status – what needs to be done or what status is it at - Color code - Unlimited notes, entries, sub dates & times - Block out time spans - Packaging - GPS tracking - RFID tag tracking - Customer checkpoints - Document processes over time, with time - Customer facing calendar - Registration - Adding time to invoices & quotes - The underlying concept – ALL things run over time 7. Create Data Relationships Between System Players - Natural relationships - System maintained relationships - User maintained relationships - Special relationships – connections - Flex Grid Tie Ins - Custom fields - Customizable databases - Unlimited notes - Unlimited connections - Customizable reports - Relationship builder - Virtual buddy system - Process & flow relationships - Roll call – anytime o Who o What o When o Where o How many o How much o Who else – other connections o Why - Systems thinking - Cause & effects - Telling the story - Records all processes - Histories – system recorded histories – when/who did this? - User recorded histories - Linking within system groups - Core concepts - Accountability - World Building – creating realistic & logical relationships - Objects – objects & data over time - Multiple access points – multiple entry points - Visual organization & structure in data relationships 8. Backend Office & Accounting Functions - Automated Balance Sheet - Automated Profit & Loss Statement - User maintained Balance Sheet flexibility - Automates 75%+ of your financials - Live feedback - Live financial report for any data – even historical - Searchable - Editable - Build in audit trail - Tells the story - Tax reports - Automated cause & effects - Banks - Inventories - Receivables - Payables - Floorplan - Checkbooks - Check-writing - Payroll - Commissions - Withholdings – taxes - Shrinkage, loss - Documentation - Photos, scans - Content - Forms – standard forms - 1099’s, W-2’s - Operation led & accounting automated – horse before the cart - Simulate traditional accounting using modern technology - Business mapping data over time & data relationships - Entries are objects & portions of information progress/flow forward - HR management 9. Histories & Reports - ALL Data Is Live And Searchable (& retrievable) - Data in – data out - Usages - Histories o Financial o Effectual o Historical - System history for every action - Quick search - Advanced searches - Exports to Excel - Save as pdf - Print reports - Dynamic filtering & searching - Wild card searches - Drill-down to multiple layers of data - Any data in – is retrievable! - Build your own reports - Date sensitive reports - Pre-set criteria - Custom reports - Search & retrieve ALL data! - Know the data source – where is that information stored - Just in time reporting – live, flexible reports - Retrieve information for marketing, HR, sales, inventories, financials, trending, usages 10. BI (Business Intelligence) - Def: The pulse – what is happening in your business, who/what is involved, how does this play, they want to know the story – all of this is done with data, using data to tell the story, analytics, what does this mean, interpreting, marketing, trending, etc. - Provide the History & Reports * - Usage - Interfaces – dashboard level - Return & report - Track usage, data, interactions, history, etc.: o Customers o Invoices o Stock/Units o Items/Parts, Inventory o Deposits o Expense/Receipts o PO’s o Vendors o Employees/Users o Quotes o Elements of Time o Balance Sheet Items - Relational data interactions - Dynamic data levels – unlimited – one to many to many relationships - Thank you adilas for making our lives easier! - Spend time analyzing & tracking data instead of building - Cutting edge – fastest browsers, new technology - Graphs, charts, visual representation for data - Data projections - Anytime roll call – return & report - Cascading, flexible, dynamic - Just in time – reports, history, recall, financials – what do I want to look at right now - Cloud based – centralized data – access anytime, anywhere - World Building: o Universe level o Galaxies o Clusters o Solar System o World o Location o Groups o Individuals o Data o Run All Levels Over Time - B2B or business to business interactions - Technology advances – memory, storage, processing power - Playing to where things are going - Future vision – anticipating, trending - The tools to reach future vision - Adaptability - Make appropriate changes according to your data - The data & reports to make your business decisions – research, marketing, trends, etc. - Affordable - Enterprise toolset for small to medium businesses - Cutting edge system for the right price - Grows with your company – reflects your - Time efficiency * - Quick access & accountability for business functions - Business stimulating ideas - Project management – managing business - Entrepreneurial idea type system vs. more rigid/fixed systems - Multi-accessible, editable, adaptable flow vs. linear, rigid flow - A living tool 11. Web Presence & eCommerce - Online elements of time & calendaring options – scheduling, appointments, rentals, reservations, class seats, projects, timelines, check-off processes, etc., etc. (not exposed yet) - Online quotes/orders - eCommerce – cart to payment to shipping functionality - Continual updates & releases - Adjustable settings & eCommerce options - PayPal - Multiple Merchant Gateways – Authorize.net, Maxx Merchants, Merchant One, USAePay, First Data - Shipping API’s - Merchant Gateway API’s - Marketing/messaging API’s - Promotion codes - Special web pricing - Marketing – sales - Futuristically… smart menu – that helps track & calculate time according to the tasks you choose - Downloadable products – E-products - Customer login options - View user history, view your quotes, your invoices, your accounts - Online bill pay - Assign monthly rates for varying levels of customer use - Specify features for different customer types - What do you want your site to do? Dream it up! We’ll wire it up! - Full integration with your adilas system - Real time inventory counts & tracking - Free canned version with adilas subscription – custom upgrade to whatever level you want to play - Photo management - Descriptions - Categorization - Settings - Customizable look & feel - Connect the adilas engine to your already functioning website - Educate your users – CMS - Custom contract, disclaimers, agreements, paperwork - Link to external sources, upload additional content - Videos - Connect with social media – Facebook, twitter, LinkedIn, Pinterest, etc. - The entire adilas engine - Interconnected - Free - Ready to go - eCommerce ready to go POS system - affordable eCommerce packages - Show/hide things on the web instantly from within your adilas: locations, items, stock/units, contact information, etc. - Permissioned & protected inside adilas – then eCommerce – separate but fully integrated customer facing side - SEO automatically functioning: photo management, descriptions, your content (maximize for your company’s name) – to incredible levels - Contact us links - Future: mix & blend eBay & adilas & other big markets - Phone, call-in, mail order, - for web presence - Emailing invoices - Direct logins - Customer pay portals - Touch screen eCommerce – drag & drop - Multi functionality - Recipe/building 12. Virtual Data Portal (Big Data) - Archive data - The entire adilas package - Data sphere – data world - ANY data, ALL data - All file types - POS, eCommerce, scheduling, expense tracking, all of the 12 business functions here in one nifty little package - All Data Is Live And Searchable - Manageable data - Affordable data system - User friendly system - E-Business buffet – what do you want??? - Your business, your way! - World Building Concepts: - Cache, secure & retrieve data - Cross-company data sharing: vendor to supplier, or vice versa, to retailer, to … - Fun - Understand relationships – cause & effect - Systems thinking – systems working - Collect data as it’s happening – filter as needed, retrieve as desired - Searches data, crunches data - Data in bulk - Customer reports, returns - Unlimited data – mess volumes - Dream it up! - Work with the whole or filter down to smaller sections - Start to finish on processes - Plan it out – accomplish it in the system - Centralize the data - Follow the entire process through the data - View the entire history - Tell the story - Visualize it your way – graphs, tables, charts, rows & columns - Educate on big data – make it less intimidating - Making big data consumable - Normal operations create the big data – the sum of your normal operations create the whole – your big data - Creates all the connections & links from normal flow - Making informed decisions – make the best decision by having the best data - Making choices based on actual data - The whole, complete, inter-connected package - Build your world, create your interactions, populate your world, create your own processes, view any piece at any time - ADILAS – ALL Data Is Live And Searchable - It comes line upon line, piece by piece – normal operations –big data - The adilas formula is: Results = Mix(Functions, Players, & Concepts) - Tech, tools, & maintenance - Needs – trouble motivates action

	AU 2007		Daily Ideas - Brainstorming on universe level	3/27/2014	Brandon and Dave brainstorming over lunch on day 3 of the adilas training session for March 2014. We talked about levels, diagrams, and future to do list of upcoming projects.

	Adi 859		Mock-Up for Adilas World	5/13/2014	This element of time contains a mock-up of the adilas world site. The attached PDF is from a phone call between Brandon and Steve about options for the adilas world site. View the PDF document for the mock-up.

	Adi 860		Custom Code - Lush Lighting & New Age	5/13/2014	Lush Lighting wants Pay Pal as a payment. Matt 574.250.6633 New Age in Edgewater (Jeremy) 512.420.7550 wants a solution to clocking in and out at midnight. Please quote. - On 5/13/14 Brandon called Jeremy and told him about the magic switch to help timecards roll over past midnight. The secret is the "work shift" on the payee to department section. If you flip the shift to "grave", it will automatically roll over the timecards from day to day. This functionality is only available for the graveyard shift.

	Adi 891		Custom code for A Touch of Style out of Texas	7/16/2014	This is a multi-part project. It basically has three pieces. 1. We needed to add photos and images to the invoices and quotes. Daniel Swainston has already completed that. 2. We needed to add in-line discounts to both invoices and quotes. Brandon is currently working on that. This is a big internal project. 3. Lee, the owner, needs a custom invoice made. See the documents (media/content) for an overview. We are waiting on the custom invoice until Brandon gets the in-line discount piece done. The custom invoice is set at $200. This is the piece that is still available.

	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.

	Adi 890		Limit quantity sold to amount on hand - don't allow negative quantities	9/4/2014	Carmen Foley, an adilas rep, has authorized us to build in some code for checking for negative quantities on parts and general inventory items. Basically, she wants the system to be the bad guy and not let her salespersons sell into the negative. There is already some similar code on the ecommerce side that basically checks for a quantity on hand and then virtually denies the person the right to use the current product (shows out of stock and all add to cart features are disabled). This means we would hide or disable add to cart functions inside the main adilas system. This project also needs some help with other more advanced features and other possible access points. The other access points are things like barcodes, advanced add to cart, my cart favorite buttons, and maybe even recipes. Don't be too scared, basically, our job is to stop the users from selling into the negative. We can do this by checking quantities and then disabling buttons and text fields where users interact with the system. We want to stop the horses from getting out of the barn. This job is basically putting locks on different access points. This setting will need to be on a corp-wide setting level. Talk to Brandon for more details. Also, this setting was promised back in late September but has been put on the back burner based on how in-depth it is and how swamped Brandon is. Brandon will most likely need to help whomever chooses to do this project as it goes pretty deep. If it goes over the $200 budget, adilas will pick up the rest of the tab and pay $15/hour over the $200 budget.

	AU 3713		Brainstorming - Database Copy & Solar System Notes	9/17/2014	- Do we want to go to int(11) or stay at int(10)? - All normal dates need to be indexed - When adding a new corporation (world) we need to decide if the new world is part of an existing solar system or a standalone new solar system. We have to make a decision… - Once we have the corporation (world) setup in either a new or existing solar system, we can then copy from old world to new world or just let them (the corporation) start from scratch Database Copy & Solar System Stuff: - I am seeing a need for a cluster controller database and a blank master solar system database that will help populate and feed all other solar systems. Basically, we need a controller and a template to copy. - Once the new copy is made, the system will leave the blank template alone. The blank solar system template will only be used when creating a new solar system. No one will actually interact with that database except for admin during scripted updates. - Once we have a good cluster controller database and a blank solar system template database, we need to put copies on all servers. Those will end up becoming templates for all other pieces. o Data 0 o Data 1 o Data 2 o Archive & storage - The goal is to be able to create a new standalone solar system before we worry about copying from the bus (existing shared environment) to the new motorcycle or vehicle. - The copy process is very important but I want to stop selling tickets on the bus so that I can drain the pond. We have to stop the inflow in order to get things cleaned up. I learned that from an old farmer! : ) - Part of the project is documentation. Take the time to get it done and do things right. This includes the Microsoft Word document with table names & descriptions. - On the solar system copy and migrate part. Break things down by letter of each table A-Z. If a letter doesn’t have any tables, still show it, just disable that option. That way, we could always enable it later on if needed. Changes to Make: - Payee table – solar system level o Add a new column o Cluster payee id o Int(10) for the old bus – new, old, documented - Payee login history table – solar system level o Corp id o Cluster payee id o Int(10) for the old bus – new, old, documented Small Check List: - Check application scope vars - Login 1 corp - Login multi corp - Exceed logins - Logout - Look-up username & corps - Switch crop - Record login history - Any payee to any corp - Adding a new user - Editing a user - Admin user edit and reset – cascade down to sub databases - View login history – make corp specific allow for unknowns - Add new corp (standalone) - Add new corp (already existing – solar system) Other notes: - If a user switches corporations (worlds) we need to catch those actions. This will be recorded on the payee login history table. In order to do this, the choose corporation page will have to play a bigger role in the system. It will have to log someone out virtually and re log them in to the new corporation. This will create a foot print of who went where and for how long. If the user logs out, they also get that recorded. Basically, this table will end up being the world the world switching table and history. Any corp that gets visited will be logged – this includes ever brief window shopping. - The store/locations will need to be moved to the session scope. Currently they are recorded in the application scope. The other options is stay with the application scope and put a cluster level list of locations together. Either way. New Cluster Level Tables: Cluster Payee Table: - Cluster payee id - Payee id - Payee type id - Payee first name - Payee last name - Payee status - Payee username - Payee password - Home planet corp id o Create o Select o Insert o Update o Documented - As a special note… reserve the first 100 cluster payee id’s - We may need some customer code to populate Brandon’s & Steve’s id numbers – mini admin function Cluster payee to corp to permissions table: - Payee corp permission id - Corp id - Payee id - Cluster payee id - Payee permission id - Payee corp permission status o Create o Select o Insert o Update o Documented - On any payee to any corp… update both the cluster level and the solar system and world levels Users: - They must exist in a home planet (corp) - At that point, they will be assigned a cluster payee id - That new cluster id will then be recorded at the solar system level to help with a backward look-up - Usernames & passwords will only be able to be changed from the home planet - Payee admin will use the cluster payee table as it’s source - If a home planet is changed - It needs to be recorded on the cluster level - If a payee gets bridged between planes, he or she keeps the home planet id. They virtually become a guest or visitor at that point. Cluster store location table: - Cluster store id - Store id - Corp id - Store initials - Store name - Store status - Store percentage o Create o Select o Insert o Update o Documented - This new cluster store location table will help us keep track of all locations per box or domain - We will use application variables to hold and store all locations for quick look-up Things to do… - Put a new mini method on the top of each CFC page. This will help do a look-up on the corp id and the solar system datasource. Name each method according to the page name. For example: o Cart cfc o “Cluster look up cart” o Amin 1 cfc o “Cluster look up admin 1” - Check every datasource = “___” to make sure it is pointing to the correct solar system, cluster, or correct database - Every method (function within a cfc) needs a call to the look-up function to help dynamically flip the datasource name - We need to check every instance of “applicaton.” ____ or “#application.” - Make sure and record all changes in modified logs and files to upload lists Application Scope Values & Variables: - Main DSN = “ “ fill in the blank - Test & live indicators – from the general table - Cfc paths – “top secret cfc – xyz” - Script path – “top secret secure” - http address – “http://www.adilas.biz” - https address – “https://www.adilas.biz” - Main root folder – “/” - Root folder – top secret - Pdf path – www.adilas.biz top secret pdf - Back up webservice address – (old) – adilaswebservices.biz inventory web components adilas - Use webservice root path – (old) – adilaswebserices.biz inventory - Use content server address – www.adilascontent.biz - Content root folder – top secret - Allow corporation creation – “yes” or “no” - Master SSL web address – “https://data0.adilas.biz/” - Master normal web address – “http://www.adilas.biz” - App mode = “test” or “live” - Qry system defaults = CSS colors & stuff from corp 1 - Qry adilas defaults = CSS colors & stuff from adilas corp - Qry store locations = corp id, store initials, store name, store id, store status, store percentage - Qry time card reasons = qry condition types, qry money types - This one might need some help with new solar systems

	Adi 884		Custom Code - New Age - Expanded P&L	10/4/2014	Hi Steve, Hope you are well. I left you a vm on Thursday regarding New Age & the reporting they are wanting. I was wondering if its possible to get a report for the P/L that can include all details of every account. It would be a very lengthy report but Dallas said they are willing to pay for it. Also, I've been sick so I haven't called the attorney but I will call her on Monday. Thanks & have a good weekend! Kath --- Contacted Dallas at New Age. They would like for all of the sub details to be entered into the reports. Quoted him at $500. Got approval the same day. Set the due date to 10/31/14. May have to ask for an extension as we don't have the in-line discount section done yet. Note added by Brandon on 10/29/14. Contact info for Dallas at New Age Medical. Phone: 303-233-1322 and newagemedicaldallas@gmail.com

	Adi 886		Custom Code - Dacono Meds	10/4/2014	Hi Stephen, Well, Brandon is very busy and hasn't had time to address the label issue. But I can't even print the first one, I talked with him and he was unable to assist me in getting it to print. Is there any other center using Adilas, that is also using a Zebra LP 2824 Label Printer that could give me some help in getting this running. Right now I am hand writing all of the labels for each container as they are sold. Labor intensive and not very professional looking, but the only option I have at the moment. Thank you, Karen Nab Dacono Meds

	Adi 892		Brainstorming notes from Steve and Brandon on sub inventory & cost controls (packaging)	10/14/2014	See attached for brainstorming notes and ideas on sub inventory & cost controls (packaging).

	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 2786		Brainstorming between Brandon and Steve on sub inventory & cost controls (packaging)	10/14/2014	Brandon and Steve had a 3-hour GoToMeeting session talking about next phases of the project and where we are headed. These are some of the notes from part of the conversation. The notes cover sub inventory & cost controls, units of measure, pricing matrix options, attributes, extensions, and wrapping things together using space, time, and money.

	AU 3719		Brainstorming - Sub Inventory & Cost Controls	10/14/2014	Brainstorming meeting between Brandon & Steve on 10/14/14: as a note this file was modified 10/22/14 - Sub inventory & cost controls (packaging) – sub of time – another function - Play in bulk or play in individuals – let the users decide - Limits (quantity limits) – yes limits or no limits (unlimited) - Attributes – the ability to have additional options, fields, settings, etc. - Pools – pre-defined rules to help with conversions o 1/8 oz = x g o ¼ oz = x g - Units of measurement for the package… unchangeable - Sub inventory items with special values… (for example) o Labor – mommy objects • Sub labor – child options - Price – variable prices and variable quantity to price levels - Barcode – we can use a unique number and it will pop up the package details - Package of packages (mini price and quantity matrix for or per the package) – copy and paste from other rules or matrix… think one-to-many - Currently we have a 1 to 1 on price and unit of measurement – we need to extend that… - Controlled groups – each package is individual - Pre-packaging - Scales and integrating with scales - Pricing matrix per item… without smart group buttons. This could be on a group level or on an individual item level. - Think subs and subs of subs – attributes (individual – micro level) - Be able to package, re-package, and re-package again. Unlimited number of layers or wrappers (how are we applying space) - By default a perfect 1 to 1 on price, quantity, cost, description, unit of measure o If they want, they could connect to a pre-defined matrix • Prices, start/end qty’s, descriptions, and unit of measure • Sub packaging to get to that level - On pricing we need price per, and total prices… just like smart group buttons - Borrow the logic of the smart groups without forcing things to the button level - Attributes – Allow them! – Empower the users! Both ways in and out (adding fields and subtracting fields). o Colors, descriptions, sizes, weights, o Sub matrix of other options… o Flex grid at any level… think any attribute - Packages are very defined… packages may not be as big, but think of a lot full of cars and trucks. Each one is very unique and we need to record that data. The uniqueness, good or bad, may also affect the cost and price (money or the y scale) - Part categories and sub categories of categories – stack as needed - Real In-Line Extensions – we need them – see notes from 10/2/14 - Go as deep as we need - Think of attributes on a per item basis…. Shoes, balls, t-shirts, sizes, colors, etc. The categories need to be main… The attributes need to be on the sub category or sub level. - Pattern after the makes and models section (any attribute and make it searchable). Do this on a group level or an individual level. - The goal is bulk or generic to specific or individual. Use the stock/units as a model. They are serialized units… tons of micro details that may be assigned and applied per item or per package… - Searching space… pretty vase and broad - All of the pieces play in this same realm – all 12 main players, sub line items, payments, sub tables, attributes, and any other sub functionality. Make it even more of a system.

	Adi 889		New Limited Invoice Permission	10/14/2014	This is a custom code job for a new system wide permission. The client has employees (sales reps) that need to be able to look at invoices but only invoices that they have made. We have similar code for my quote vs. the general all quotes permission (all salespersons). The invoice permission will get a little bit tricky in that the permission needs to be cascaded out to all invoice sub reports as well. The goal of this new permission is to allow the user (sales rep) the full invoicing options and power but limit them to what other invoices may be seen. Ideally, if they have this permission we will automatically switch things in the background to limit reports to their name in the salesperson columns (2 columns - main and other salesperson). Along with that, we also need to limit access to an invoice if they (the current user) is not the main salesperson or the other salesperson. Basically, we pull the data, check the permissions, and then if needed we also check to make sure that they have access to view and/or add/edit details. Finished by Brandon Moore on 4/7/15.

	Adi 897		Custom code - Setting for Quotes	10/21/2014	Setting for quotes that will allow the salesperson to be the user id that restores the quote. As a note, a new corp-wide setting was added to the ecommerce settings to allow this to happen. The new setting was added as part of the in-line discount process. In-line discounts took over for about 3-4 months and the new setting was never pushed all the way through. Talk to Brandon for more details. This should be fairly quick once we get a developer on it.

	AU 3721		Brainstorming - Sub Inventory & Cost Controls	10/21/2014	Notes form a phone call between Brandon & Steve on 10/21/14: Recorded on a Word Doc for Sub Inventory & Cost Controls used for Brainstorming - Go to the very beginning. Where does it start? - On multi RFID & serial #’s o Standard – XYZ-7 o Auto increment from 003 to 7000 - Stock/Units – tons of 1-many - Attributes – tons of 1-many - Auto packages – LIFO or FIFO o Order of selling or think a vending machine – next, next, next - Setting – how do they want to play over rides – possible - Possible group invoices o Real details…. Behind the scenes o Show in bulk (to the customer) according to the price and description - Track in details but show in bulk

	Adi 895		Brainstorming session between Steve and Brandon	10/22/2014	See attached for brainstorming documents dealing with sub inventory and cost controls (packaging), recipe/builds (extending functionality), 3D world building (creating the whole system), etc.

	AU 2904		Daily Ideas	10/25/2014	On the API socket pages… I would like to provide samples in different languages on how to connect...: - ColdFusion - ASP.net - PHP - Ruby - Java - C++ - Java Script -Maybe have a super simple method that outputs a person’s name or does some simple math. Kind of a “Hello world” method, just for testing. Help people get connected. -A developer came over and we worked on the adilas API socket project. We are calling it “wiring up the wall”. Here are some graphics that we used to explain the process: hard coded pages and database queries. This is a one-time plug-in. We don’t want that. That is a one-to-one ratio and can’t be reused unless you copy and paste. Then if changes are needed, you have to update every page. -Internal use of API socket connections (API socket calls – good – use many, database) OR External use of API sockets, ports, gateways, etc. (“wire up the wall”) More drawings on how the API works… Brandon and a developer: This is the developers’ project of wiring up the wall with different ports and sockets. Many sketches – please see scans in photo galleries - External clients: laptop, phone or mobile, tablet, desktop - Normal Internal structure: internal API socket, adilas database - Other programs, apps, pages, etc. - Custom or 3rd party solutions Connection Process – Plugging in: 1. Knock, knock, who is there? 2. What do you want? Which method or function? 3. Pass in requirements. 4. Make the connection. 5. We pass back the results. - 500+ options Internal data ports and sockets

	Adi 901		New adilas banners	10/31/2014	Here are two new adilas banners that will be printed and used at the upcoming trade show. Banner 1 - PDF - 11MB - https://data0.adilas.biz/public/adilas_banner.pdf Banner 2 - PDF - 12MB - https://data0.adilas.biz/public/adilas_banner_2.pdf The banner design was originally created by Steve using CSS (cascading style sheets) and graphics. We then had to convert the ideas to Adobe Photoshop in order to get the resolution high enough. Brandon did the Photoshop work and pushed the files up online. A lady by the name of Katrina Skinner helped with some of the data points and verbage. Banner 2 includes information and data about 3D World Building as well as other key concepts such as: assembly line for data, custom data engine, custom dashboards, and real-time data portal.

	AU 2788		New Banners for the Las Vegas trade show	10/31/2014	Here are two new adilas banners that will be printed and used at the upcoming trade show in Las Vegas. Banner 1 - PDF - 11MB - https://data0.adilas.biz/public/adilas_banner.pdf Banner 2 - PDF - 12MB - https://data0.adilas.biz/public/adilas_banner_2.pdf The banner design was originally created by Steve using CSS (cascading style sheets) and graphics. We then had to convert the ideas to Adobe Photoshop in order to get the resolution high enough. Brandon did the Photoshop work and pushed the files up online. A lady by the name of Katrina Skinner helped with some of the data points and verbage. Banner 2 includes information and data about 3D World Building as well as other key concepts such as: assembly line for data, custom data engine, custom dashboards, and real-time data portal.

	AU 2950		Daily Ideas	11/13/2014	-I went to a large multi-stake Priesthood training meeting tonight. Very good training. The whole thing was on the meaning of the Sacrament and how we, personally, can remember Him, meaning Jesus Christ. I loved how they used principles of learn, act, share – over and over. Very effective way of teaching. It encourages participation and interaction. It also has deeper levels of learning because you end up learning from multiple sources, including directly from the Spirit or the Holy Ghost. On boarding new interns & developers: Ideas between an adilas intern and Brandon dealing with bringing on new adilas developers: 1. See notes from 9/12/14 for requirements for new adilas interns. Lots of good stuff there. 2. Looking for skilled independents (contract labor) 3. Start them out at $10 per hour. Keep them at this until they are ready to move up 4. Require 30 hours of training. That would be 15 hours of Cold Fusion, 10 hours of adilas training, and 5 hours working with Brandon or other adilas developer/trainer on projects. 5. We would pay $300 for the training. That works out to $10 per hour for training. 6. On budgeting … We can budget $300 for Cold Fusion (code) training. $200 for adilas training and $300 to pay the new developers. Our goal is to get the new persons trained for $800 or less. The $300 & $200 for training would go to the instructors or trainers. The other $300 would go directly to the new developer. This way we try to cover all parties. 7. Our goal for the new developers would be to get them to the $35-$50 per hour rate. At that point their skills will be enough to help them do whatever they want to do. 8. The whole project is just in time. Just in time projects, just in time funding, just in time skill sets. 9. Dream dreams! Follow those dreams!

	AU 3729		Brainstorming - On-Boarding Interns	11/13/2014	Working with an intern on developing a program to help new developers come on board – See 9/12/14 for requirements On Boarding: - Skilled independents - $10 per hour - 30 hours training o 15 CF – back to instructors o 10 adilas o 5 project or with Brandon o $300 pay them o $300 CF teacher o $200 adilas teacher - Once on board as independent, keep at $10 for the first month - Just in time - My goal with skills to $35-50 - How to pay back - Dreams! Planning numbers & budgets

	AU 2951		Daily Ideas	11/14/2014	Code Sign-Off Process: 10. Sign-off on code and add small version control per page. Talking with an adilas intern. 11. I would like to work with developers on their machines and sign-off on things locally. 12. Once a page has been signed off locally, the developer will upload pages into the top secret/need sign offs folder. This will keep it out of production until it gets a final gate keeper review. 13. The gate keeper (Brandon for now) will pull down the files that need a sign-off. The gate keeper will then test and make sure that things are good to go to production. 14. Once put in production, new code will be put up online in the released or normal top secret folders. All developers will go to the FTP server to get the latest files that have been released. We had a request to help manage max & minimum inventory levels across companies. That sounds like application flex grid or real in-line extensions. These projects are gaining momentum and heat. New Developers: 15. Meeting with an adilas associate and talking about a company that can help or who would manage the process of bringing people on board and bringing them up to speed. Both reps and consultants as well as developers. We are focusing on the developers right now. 16. Film and record all of the training pieces and put them up on adilas university. 17. Have a test and/or certification level to help with skill sign offs. Maybe use flex grid tie-ins or elements of time to accomplish this. 18. Do things once and then use over and over again. 19. Make the first video as a 5 minute overview. Keep it brief. 20. Anybody new needs to go through the process. 21. Use the code segment – can act as an evaluation process of sorts. Basically, do we want to spend the money on their education? In other words, a trial period of sorts. 22. Plan some 2 hour session in December & November – monthly & weekly training sessions. 23. -Generally schedule out time frames for each subject. o Topic: • Bullet points • Requirements • Options • Visual aids • Time frame 24. Double the bang for the buck… show code sample and concepts and how they relate to adilas. Put the concepts into action at the source. 25. Use all of the different teaching methods and learning styles. Audio, visual, actual, hands on, etc. 26. There will be quite a lot of time in both pre & post production stuff. 27. API – Play at the wall! This is where we could support the largest number of code developers. 28. Do a small 1-2 hour seminar for interested developers – Look for people who are interested. Pull from a bigger pool! 29. Start the first seminar with hand-picked folks who want to play. 30. Use the seminars and meetings as a screening process for qualified people. Help them get the skills to pay the bills. Share, share, share! 31. Try storming – Be willing to circle back around. 32. It is ok to break models. We do it all the time. BE sensitive about his but don’t fear. Take more counsel from your faith, hopes, and dreams than from your fears. Let faith win! 33. When teaching a code class, it might be cool to have a way for class participants to submit and run code. Maybe use elements of time and sub comments. Maybe each person has their own main element and then uses the sub comments for assignments.

	AU 3730		Brainstorming - On-Boarding Interns & Code Sign-Off Process	11/14/2014	- 30 hrs - $300 o 15 CF Code - $20/hr = $300 o 10 adilas - $20 hr = $200 o 5 actual project – hands on o $800 - New 10-20 new clients - $2,000 per month - New custom jobs - $5,000-$10,000 per month - Company who manages (Facilitator) – on boards process & bring them up to speed - Film and record all of the pieces adilas university - Have a test and cert base to accomplish the sign-offs - Do it once – use many - First video is the overview – 5 mins (brief) - Anybody new needs to go through the process - Code evaluation process o Do we want to speed the money on their education - Plan 2 hour sessions in December - Generally schedule out timeframes for each subject – (Liks – 10 min) o Bullet points that need to be addressed and/or covered o Options o Visual aids - Double the process by showing these concepts in action inside of adilas - Auto, visual, hands on or actual - There will be some pre & post production stuff - API – Play at the Wall! - Small 1 hour seminar for developers – look for people who are interested (pool of people) - Start the end of November - Use the meeting as a screening process for qualified people - Try storming - Okay with breaking models - David.forbis@adilas.biz – Project Management - What if we had a way for class participants to submit code for running and/or checking? Maybe use elements of time & sub comments Talking with an intern about flow & code sign-off process: (Please see sketches on scan in photo gallery) 1. Sign-off locally 2. Upload all to need sign offs 3. Pull down from need sign offs 4. Brandon is the gatekeeper (right now) 5. Once actually released they will go into production & updated on the MDI server 6. Max & min on inventories

	AU 3731		Sketches - API Socket Connections	11/15/2014	Brandon & a developer talking about API Socket Connections: (Please see sketches on scans in photo gallery) - Pages – “.cfm” - CF - Components – “.cfc” - Adilas API Demo - Security cfc - Page – adilas api calls cfm - Special include - JSON - Black box o Web api o Adilas demo cfm o “.cfm” external use - Adilas API Calls / External API: o Check permission o Get web inventory o Adilas API demo - Return info in – JSON – CF – general validation – CF include, their request – custom validation 1., 2., 3., 4. Call .cfm

	AU 3000		Daily Tasks	1/2/2015	• Prep work on files to help with in-line discounts. Checking shopping cart stuff, eCommerce code, and adding stock/units. • Huge late night push between Brandon & Steve to get new code launched for in-line discounts, campaign tracking, new payroll withholding tables, new label mapping options, new settings, etc. We had to update and shutdown multiple servers and then bring them back up and online with new code. Major process. Steve and I did the whole session using GoToMeeting. Thank goodness for candy and chips (snacks)… Late night. As a small note, we have a couple of known issues that will be fixed in the next couple of days. They are all noted on a separate page.

	Adi 917		Custom code - Deeper Client Search	1/15/2015	Jan 8 (7 days ago) to dgrier, David, Brandon Hey Don! How about if I add a search field to your gun club homepage? I'd say $100 would pay a developer to knock that out for you. Thanks, Stephen Berkenkotter 719.439.1761 steve@adilas.biz :: www.adilas.biz "all data is live and searchable" The information in this e-mail and any attachment is client privileged and confidential. If you have received this e-mail in error, please notify the sender immediately. From: "Donald S. Grier" Sent: Thursday, January 08, 2015 12:06 PM To: davidb@adilas.biz Subject: RE: new adilas updates Hi David. Thanks for the update. One question. When we search our members, we can only pull up the individual member listed on the main portion of the account. We have family memberships where there are additional people that are part of a family membership (sometimes with the same last name, sometimes not). Is there any way that Brandon can add that when we search any name, Adilias will search all the members and the additional people on a membership? We could really use this feature. An example for me is below: If you searched “Grier” you would find me, but none of my family members on my account: Additional Contact/Address Info [add an additional contact/address] Contact Type 1: Wife First Name 1: Elizabeth Last Name 1: Grier Address 1: City 1: Prescott State 1: AZ Zip 1: 86305 Cell Phone 1: 928-420-3457 Show On Every Invoice 1: No Contact Type 2: Son First Name 2: Ethan Last Name 2: Frank Show On Every Invoice 2: No Contact Type 3: Son First Name 3: Aidan Last Name 3: Frank Show On Every Invoice 3: No Contact Type 4: Son First Name 4: Shane Last Name 4: Grier Show On Every Invoice 4: No So if I searched Aidan Frank, Adilias would not show him at all and would require that we add a new customer or our staff will tell the person they are not a member. Finally, we cannot delete an inactive customer or double entry. Sometimes, an employee does not find a customer and then re-inputs the information. We would like to delete the inactive account entirely, but cannot do that. Is that possible as well? Thanks, Don Donald S. Grier Prescott Gun Club 1200 Iron Springs Road Prescott, Arizona 86305 Telephone: 928-717-2218 Website: www.prescottgunclub.com

	Adi 920		Custom code - Email Invoice	1/19/2015	From: "Jason Robillard" Sent: Thursday, January 08, 2015 11:36 AM To: davidb@adilas.biz Cc: "mark@greenfrogg.com" Subject: Re: fw: new adilas updates Great features buit dont really apply to our company. What has been promised to us for over a year now is an invoicing email feature without having to save each invoice as a pdf. I understand that that we are the small dog on the block but why make the promise then? Hope you are having a great year. Finally launched new code and email invoices and quotes feature on 9/5/15. This update note was added by Brandon Moore.

	Adi 963		Custom code - Drivers License	3/17/2015	Notes on completed project. Project - Add a new drivers_license field to the customer table - blum - emerald green Steps 1.Add the field to the database a. Name = drivers_license b. Data Type = varchar c. Size = 100 d. Defult = null 2. We need to script that change ... this allows us to update all the other systems. a. Brandon do and show 3. We start at the add process. a. Add a new field to add_edit_customer.cfm 4. We need to cascade that field all the way out to the action field. add_edit_ customer_action.cfm a. Add validation b. Add to the add method c. Add to the update or edit method d. Unknown - Search other methods to see if we need to add to other methods. also search for INSERT INTO customers (" also check eCommerce land .... adds, edits, validations and actions. 5. We need the drivers license to the customer_log.cfm 6. We need the same field (showing it or outputting it) on the customer gallery, customer history 7. We need to add it to the quick search - search_action.cfm or is it the customer_search_action.cfm a. Tying it underneath the normal customer search field for quick searches i. this is just another or clause 8. We need to add the field to the advanced_customer_search.cfm 9. We need to add the same field to the output or search results page - advanced_customer_search_results.cfm - cfcSearch13? a. WE also need to make sure that we pass the correct values to all other including refine search, pagination (next page of n) as well as exports to excel 10. We need to check other places where customer gets exported to excel 11. Get a sign-off on new code changes 12. Clean-up we need to modify help files and push all new code to all servers. a. Pages to upload data0 - x data1 - x data2 - x update_20150126.cfm - 0x 1x 2x assets.cfc - 0x 1x 2x search_13.cfc - 0x 1x 2x search.cfc - 0x 1x 2x add_edit_customer.cfm - 0x 1x 2x add_edit_customer_action.cfm - 0x 1x 2x 3 customer_log.cfm - 0x 1x 2x customer_gallery.cfm - 0x 1x 2x customer_history.cfm - 0x 1x 2x advanced_customer_search.cfm - 0x 1x 2x advanced_customer_search_results.cfm - 0x 1x 2x custom/full_customer_list.cfm 0x 1x 2x 13. Bill for the project - 400

	Adi 1000		Duplicate Or Copy Elements of Time	3/30/2015	Completed by Brandon Moore in 2018

	Adi 1003		Map Out & Document Full Adilas Database - Make The Database Layout Available To Outside Developers	3/30/2015	Brandon and Shannon have documented tons of tables in word docs and notepad docs. Not publicly available. Currently in backend pieces.

	Adi 1005		Adilas University - Videos, Training, Tutorials, Shortcuts, & User Guide	3/30/2015	Brandon and Shannon are currently working on this. We have a number of videos out there, hundreds of hours of training that raw. Every week this is being touched on for a couple of hours.

	Adi 1013		Reoccurring Elements of Time	3/30/2015	Completed by Brandon Moore 2018

	Adi 1014		Inventory Alerts - Max & Min Thresholds - Quantity & Order Monitoring	3/30/2015	4/16/2020: With all of the current need for e-commerce, the need for buffers on the item level has come in to play and is wanted. In order to beef up needs to be location specific. Buffers do exist in e-commerce. There is a category based buffer in the shopping cart (two of them). The one in the shopping cart can be configured on a per category level and even on a per item level. Super high level- needs to be on a per item/per location basis. ////// new notes on 1/6/2020 - Meeting with Brandon, Steve, and Cory - Steve wants to get this inventory engine built into a reordering system. There is more than just mins and maxes, we have to deal with sales, quantities, how fast/slow things move, lead times, things that need to be sold, restocked, and even never stocked again. Lots of ideas of algorithms and building in logic to these pieces. - We would like to create a good game plan (what are we going to build and how will it benefit our users) and get it funded. - Steve also wants to get Alan and other developers involved. - As a sales happens, we will start hitting a special weighted function (algorithm) that helps us see what a sale means. The weighted portion of the puzzle would help us know what is moving, what is effective, and other virtual marketing and sales matrix options. Getting the real meanings bubbling up to the surface. Kinda like a performance level or batting average (sports analogy). - There were some talks about building out ways to catch this weighted value and what steps would come after that (refinement of that process). - There is a still a human element that needs to play into the mix. There is also a maintenance level to keep these things (numbers, values, and settings) updated. - In order to really to this correctly, we a really need to build it out on a per location basis. Winter boots sell much better in the North than they do in the desert. - To do reorders, you almost need a way to pour over sales reports and past order forms in order to get an idea of what is needed.

	Adi 1020		Expand Payroll Options - Bulk Pay, Bulk Reports, Different Commission Structures, All States, Forms	4/3/2015	10/7: 33.63 John is helping with this: Shawn and Brandon are payroll guys. Shawn has upped the number of states. 10-12 states currently. Year end forms Currently one at a time for payroll. Can pull multiple time cards per department.

	AU 3806		Daily Ideas	4/8/2015	-On the “verbage” special line item… Take off the $1.00 price value. Change it to a zero. An even better option is to allow the users to change the prices on the corp-wide settings page. -Along with changes to special line items… It would be cool if we could allow users to create their own custom special line items (parts or unlimited items). This could be additional labor rates, fees, discounts, etc. They can already do this, but they have to create their own unlimited items through a setup PO. -I was reading an email and really liked the phrase “Managed Solutions”. I would like to start using that term more often. -When showing the black box concept, show multiple pages to get the concept across. Pretend that the dots are possible black boxes per page. (See sketch in photo gallery) Brainstorming notes between Brandon and adilas interns & developers: - We are going to call this section – my saved favorites. It may also be known by my favorites, saved report settings, and just favorites. - An intern really liked the split screen idea for showing the saved favorites. - Split screen idea for my saved favorites: saved favorites (left side bar), actual reports based off of the saved favorites (right side – majority of screen) - It might be cool to add in a type, categories, app types, etc. Basically a way to organize the my favorites or saved favorites. - We want to be able to rename, delete, and edit the favorites. We also want to be able to copy and duplicate them as well.

	AU 3782		Brainstorming about the need to mix elements of time, sub functions, and 3D world building concepts	4/21/2015	These are some whiteboard brainstorming pictures of a brainstorming session between Brandon Moore and Calvin Chipman. We were talking about how relationships, inside of adilas, are created and/or manufactured. The subject covered was dealing with how we want to help to virtually adopt different players and player groups inside of adilas to the sub functions of elements of time and space. The subject was somewhat on the topic of data glue. We covered main application types (system player groups), main id numbers (how they connect), and what natural options and relationships already exist. We figured that at the most basic level, we could use the following fields to connect any piece to any other piece. Corp Id or World Id Number App Type Id (2=Deposit, 3=Invoice, 4=PO, 5=Expense/Receipt, 6=Balance Sheet Item, 7=Stock/Unit, 8=Customer, 9=Vendor/Payee, 10=Employee, 11=Part, 12=Element of Time, 13=Quote) Main Id - What is the corresponding main id number to create the main id and app type id combo? These combos deal at the data level for the data item. For example: App type 2 and deposit number 50. That makes a specific named deposit. Or app type 3 and invoice number 700. That creates an invoice entity or individual. Or app type 11 and part id number 1000. This would be how the system would talk to and/or communicate with a part number or item (general inventory item). Sub Id - Optional. This would be a sub id number if we need to connect to a sub. If not, it would be left at 0. Table Name - This would be a string or text value that would help us know what table we were talking about. This helps us possibly connect an unlimited number of subs or sub tables. The other fun thing about this brainstorming session was the fact that we listed out a number of the subs of each player group as well as listed out some of the sub functions of time. The sub functions of time are still somewhat new and a budding subject inside of adilas. This brainstorming session also mixed a little bit of 3D world building with sub functions of time, permissions, settings, photos and scans, locations (stacked model), and with media/content (files). By the time we were done, we were talking about a thing called the application flex grid (connecting different worlds or software applications together) and real in-line extensions (possible ways of extending any table or column in the entire database). Good session.

	AU 3816		Daily Ideas	4/22/2015	Notes from a discussion between Brandon, a developer, and the project manager: - Training is so important. A company that believes in training is awesome. Even a draw to outside parties and talent. - Training and maintenance may be more important than a new feature. - The lack of training is like not having the feature at all. Either you don’t know about it and/or you don’t know how to use it. - Believe in training and education. That helps, lifts, and inspires people. At least, that is the goal or concept. - Seek outside funding for the black box project.

	Shop 136		Bryan	10/26/2015	Talking about the issues that arose from the Adilas Shop Monday morning meeting. Notes - We did a lot of brainstorming and used up the whiteboard numerous times. We are talking about ownership of the shop, dividends, and future options for the shop. Basically, adilas has a need to get internal projects done to make a virtual bullet train (fast and smooth project). In order to get there, we need to build some of the internal pieces out (adilas engine). We talked about setting a future date and seeing what we can kick back to the shop to help it float and succeed. We also talked about the adilas shop helping out with the tick list that is contained in the "developer's notebook" that Brandon has kept.

	Shop 139		Steve and Brandon	10/26/2015	Bryan meets with Brandon and Steve. Notes - We worked on saving PDF's for the Prescott Gun Club. After checking a number of things... We ended up changing an https to an http (without the s). It seemed to work out fine.

	Shop 141		Brandon w/ Nick Safe Harbor	10/27/2015	Skipped - due to other fires.

	Shop 148		Brandon/Calvin - CSV bug	10/27/2015	We looked at the bug and Calvin was able to change it on 2 pages very easily. Basically, we just check for a 0 record count and show an error if 0.

	Shop 3831		Virtual Post-It Note	10/28/2015	SHOP Will Nick Brandon Jake Daniel Bryan Garrett Adam Calvin Makay James Derrick Chris Scholle Chris Dunsey Shawn Curtis Russell Shannon Dave Alan Jonnathan Lincoln Louisa Wayne Jared Chris Jhonnie Steve Daniels

	Shop 152		William Bates GPS Project	10/29/2015	Meeting to recap the progress of the GPS interface project and start incorporating Calvin's Gps Routing work. Invited: Calvin Chipman Daniel Swainston Brandon Moore Jake Vaughn Dave Forbis Notes - We met and went over things. Daniel did the demo on his machine and all the rest of us watched and chimed in as needed. We determined that we would use locations for the trucks instead of the general person field (just text). We also went over some other small changes and other tweaks that are needed. The guys are doing great and we set a tentative completion date of 11/9/15. We have a joint meeting with Calvin Chipman tomorrow to talk about the actual GPS portion of the project.

	Shop 164		Working with Nick & Bryan on Safe Harbor	11/2/2015	We skipped this meeting completely. I ended up on a phone call with Steve for almost 3 hours and then we had to take care of transferring ownership of the Adilas Shop back to adilas.biz as a company transfer between Brandon, Bryan, and Garrett.

	Shop 174		API Hypur- BRANDON NOT IN THE OFFICE	11/5/2015	Brandon is unavailable to meet because he is doing coding needs. Notes: I ended up doing a 3 hour blast on this stuff. We added in some new code, did some testing, and spent over an hour on the phone with Ignacio from Hypur on the phone. Good session and by the time we were done, we had a working API socket connection between adilas and the Hypur invoice collector API.

	Shop 179		Working WIth G to push code live.	11/6/2015	:) Notes: Garrett ended up pushing up the code by him self. He pushed some new changes up to data 3 because it was Friday afternoon. We didn't want to bring the whole system down on Friday afternoon/evening. Busy time. We did end up with some errors and finally got them all fixed after a 2.5 hour session on Saturday morning. The errors were on sub inventory, bulk labels, printable quotes, and restoring quotes to cart. Garrett and Brandon worked together on Saturday to get the errors all taken care of.

	Shop 180		Meet with Altra	11/6/2015	Brandon and Dave went to Icon Health & Fitness (in Logan) to meet with the Altra Running Shoes department at Icon. We met with a couple of guys by the name of John and Chett from the sales division of the Altra section. We did a small demo and they wanted to see what was available by way of an EDI (electronic data interchange) or API socket type interfaces. Basically, they wanted to stay with their older system but push data to us to get at reports and other custom sales matrix and stats. Their current system did sales and provided lots of data but was not very flexible on the reports and building custom options. Interesting meeting.

	Shop 2941		General	11/25/2015	6:15-6:30 Recording notes from yesterday from memory and from post-it notes. 6:30-9:00 Working on some changes to the Hypur API for the invoice collector. Made a number of changes and got on a phone call with Ignacio from Hypur to test and push things. Small GoToMeeting session over code. 10:15-5:45 Went into Logan to work with my guys. I had meetings with Nick Vaughn, Alan Williams, and Bryan Dayton today. Pretty quite and we got a lot done. Nick and I did a good two hour sessions on the third party error logs. We tightened up the page, added a new admin permission, looped ober things to help archive data, and added addition search options and functionality. We are thinking to use the new error log tool to track employees who clear shopping carts as well as other error logs. After that, I worked with Alan for over 3 hours on shipping settings for eCommerce. We were working on fixed notes, flat rates per item, and other shipping settings. I worked with Bryan on a custom invoice job for a company called A Touch of Style. They provided us an Excel based invoice and we had to convert ti into a web based invoice. Daniel was in today as well but working on his own projects. Quiet but busy day, 30 miles. 9:00-10:00 Online recording note inside of elements of time for the Adilas Shop. Clearing out the Brandon Time entries and appointments.

	Shop 2942		General	11/27/2015	7:00-8:00 Responding to texts and email. Going through elements of time and cleaning up the Brandon Time entries in the Adilas Time Shop site. 9:00-3:00 Went out to Lewiston to work with Calvin on his label Wizard product. The first hour and a half we just chatted and talked about projects, options and needs. We then got into the label wizard. We wrote down some specs, got YouTube video links and got some graphics coming back from Russell. I worked on YouTube media/content pieces and a new ad for Calvin. He worked on other projects and helped give me direction and feedback. Great day. I also got to know some more things about Calvin and some of his background. The day was busy but casual at the same time. 20 miles. 5:00-5:30 More work on Calvin's label wizard ad for the main login page.

	Shop 2731		General	12/18/2015	12/18/15 -6:15-9:15 See E of T #324 in the shop-Alan-Html me cart favorites button. -10:00-12:30 See E of T #304 in the shop-Daniel-horizontal time slot report. -1:00-1:30 Russel and I had a small meeting while eating lunch. We basically talked about direction and vision. We both like to dream big...It's the getting it done that is the hard part. -1:30-3:00 Cleaning up the shop. Sweeping floors and meeting with Russell on some up coming projects such as the Adilas university site, the Adilas market site, and the Adilas world site. All of these projects and up and coming in the near future. -3:00-4:15-Catching up on notes and notebook stuff. Cleaned out a number of time entries for the last couple of days. Basically, I go to the favorites page, click on Brandon Time (a time template name) and clean up the older entries. I record notes about happenings and progress that is made. Recording things is a big part of my job. -5:00-5:45-Light clean-up on corp-wide settings for the shop. I also updated an invoice from the Beaver Mountain to note the trade details for Beaver Mountain. -5:45-6:30-Recording notes from loose pages and post-it notes into my main notebook.

	Shop 347		Brandon Gone All Friday	1/1/2016	January, February, March Brandon will not be in the office on Fridays Great day on the hill... Very tired after new years, but good snow and good turns. Yee Ha!

	Shop 348		Brandon Gone All Friday	1/8/2016	Great day on the hill. Taught a mountain adventure class with Allie.

	Shop 349		Brandon Gone All Friday	1/15/2016	Great day on the hill. I taught a 2-hour mountain adventure class. We worked on jumps and riding powder. I met up with Daniel in the afternoon and we took a number of runs together.

	Shop 430		Clean-up	1/19/2016	Emails, clean-up, and tech support. Cleaned up a number of elements of time in the Brandon Time section. Trying to keep up on notes and comments. Also recorded a number of ideas and things to do. Small work with Dave on some quotes and direction.

	Shop 350		Brandon Gone All Friday	1/22/2016	Great day on the hill. Taught 3 lessons. One was a mountain adventure class with 5 younger kids. We did some jumps, powder, and introduction to trees and traverse trails. The other two classes were week 1 of the college classes. I have a high level freestyle class at 12:30 and then an intermediate freeride class at 2:30.

	Shop 351		Brandon Gone All Friday	1/29/2016	Great day on the hill... Taught a clinic on intro to moguls for the instructors. This was a simple clinic using pressure and pivot to stall out and gain some time. I then taught the mountain adventure class with Allie (another instructor). This was the last class of 4 for our mountain adventure class. They are smaller kids (7-13 years) but really fun. We worked on ollies and riding powder and trees. I then did both of my college classes in the afternoon. Good snow and lots of fun in the trees. The last college class we did a little bit about spins and light rotation.

	Shop 527		Brandon Coding Time	2/3/2016	Emails, gathering up some help files for Alan on elements of time, recording notes on sub details and special flags/tags for elements of time. I then worked with Alan and Daniel on some planning for the horizontal view for the Beaver Mountain project. We went up to the board and spent a good hour going over our plan, what we know, what we want, and how to get there. Alan did a great job and was very beneficial in the planning and understanding of the logic. Both of use were tag teaming and trying to help Daniel catch the vision and where and how to get the project done. Good stuff.

	Shop 352		Brandon Gone All Friday	2/5/2016	Good day up on the hill. We did a two hour powder clinic and rode together as a group in the morning. I then did an hour of work and recorded notes in my notebook. I then did the two college classes in the afternoon. Good snow and good times.

	Shop 667		Meeting with Todd Williams	2/9/2016	Russell Moore, Brandon Moore, David Forbis Mountain Valley Machine, Inc twilliams@mvminc.biz Work 435-563-3632 Gave Todd Williams a demo on multiple different levels. We were bouncing between corps and looking at both inside (internal) and outside (ecommerce) stuff. I showed him some project management options and time tracking for projects. We also looked at some quick sales reports, ecommerce, and CSS (look and feel). After our demo, we stepped into a side room and had a discussion about a possible business option and idea. The main goal would be to include different resources and bring people together. Basically provide a hub or place where a group of people could get together and allocate monies and/or resources to a new project, physical product, digital product, a concept, or an idea. We talked about pulling in attorneys, CPA's, data folk, machinist, production people, sales people, marketing, designers, bankers/lenders, etc. to create a pooled environment where we could all work together. Basically, adilas would be the backend business tracking software piece and help to allocate budgets, timelines, track resources, ownership, and help in the business tracking process. So, those who invest or allocate resources (skills, trades, time, monies, talents, ideas, etc.) would be partial owners of the new products. Basically, because a product, concept, or idea isn't much more than a plan at first, it isn't worth a ton until it starts going from water, slush, to ice. Basically, we want to create an environment where we push new ideas forward and help to build people, places, and things. After Todd left, I batted around some ideas with Russell, Dave Forbis, and Bryan Dayton. We chatted about options to help do some of the following: These are all kinda loose and just ideas at this stage... - Single product market and/or mall type concept - Imagine a mini version of eBay or Amazon for different products and services - A market place where small businesses could get together and collaborate on ideas, projects, and actual products. - We could allow for online shopping and ecommerce through a preset venue - and adilas hub model shopping place. - We could help with setup, data storage, data mapping, invoicing, digital payments, and moving monies around. We would own the merchant account and then re-distribute the funds to the parties involved. - It might even be really cool to re-distribute the funds based off of percentages of ownership. This idea came from Keats Horstmann from Safe Harbor Alliance. I could see it being pretty cool. Think about almost instant re-distribution of funds. - We would need to handle shipping, customer service, fulfillment, and other shopping related needs. - As we allocate resources, we could track time, monies, ideas, raw goods, and other resources that get allocated to the projects and products. - If a company ends up selling or moving on, hopefully they will have a loyalty to the adilas platform and continue using the database service. - In a way, this project is a mix of community funded projects, the adilas world, the adilas market, the developer's notebook, and a social hub for sharing resources and such. Anyways, some good ideas have been floating around. Todd asked me to let it simmer and add thoughts as they come up. He would like to get a small team together to see what we could come up with. I offered the adilas shop as a place to meet and do some whiteboarding on the concepts and ideas. See the sub comments for more ideas as they come in... little mini forum of sorts.

	Shop 528		Brandon Coding Time	2/10/2016	Recording notes and ideas about a number of things. Lots of fun stuff going on. Emails and prep stuff. I then started working on the add limited flex grid page for Beaver Mountain.

	Shop 353		Brandon Gone All Friday	2/12/2016	Good day on the hill. Got there early in hopes to talk to Debbie about the progress that we are making on the Beaver Mountain project. She was pretty busy. Not much happened. I got some runs in and then helped with the school. After that, I did a couple of hours of adilas work while sitting in the lodge. I then taught my two college classes in the afternoon.

	Shop 529		Brandon Coding Time	2/17/2016	Working on the add limited flex grid page. This is a special add page that interacts with almost 500 settings to show/hide fields and values as needed. Basically, the goal is to help the add mode for adding new pieces of flex grid. By default, the add/edit flex grid page has tons of fields (40+). That can be intimidating for users. The new add page, allows you to preset which or what fields to show. So, you can only show 4 fields, 6 fields, etc. vs. all 40+ fields. Anyways, almost done with that page.

	Shop 354		Brandon Gone All Friday	2/19/2016	Good day on the hill. I taught a morning learn to turn lesson for a labor and delivery nurse. I then taught my two afternoon college classes. Our last run of the day we went off the backside of Beaver down to spring road. We got into some unknown territory and I thought that we had missed the spring road connection back to the front side of the mountain. Anyways, we made it back but it was a little bit stressful. Good day!

	Shop 790		We need to get an ecommerce document ready for outside developers	2/23/2016	Here is an email that I sent to an outside developer who wanted to know about the adilas API socket connections. I think we need to build a small page or section to help them know what to do and how to get started. Help them "Play at the wall". Taylor, Hello and good afternoon! I wanted to reach out to you and see if I could point you in a good direction for integrating with Adilas. There are tons of pieces that are pre-built and totally done. We have a free pre-built web presence and ecommerce option. This option is completely controlled from inside of Adilas and allows for settings, uploading photos, setting web prices, full cart checkout, pre-ordering, client login, etc. We also allow developers (like you) to interact with some of the URL and FORM if they need a little bit more control. https://data0.adilas.biz/shop/developer_help.cfm We also allow outside developers to interact and virtually take over some of the standard code in a black box type scenario. We also do custom carts internally for clients who want help. Here is a small link to a custom shopping cart. https://data0.adilas.biz/top_secret/ecommerce.cfm - basic info about ecommerce https://data2.adilas.biz/shop/search_web_inventory.cfm?corpKeyId=Saf%2D0594 – actual custom shopping cart page We also have a small API that allows for raw data transfer. The API has not been fully tested at this point. We do have some people using it, but it kinda a pioneering project if you know what I mean. Basically, we had some of our beginner developers on the project and then had to pull them off for other projects. We haven’t been able to fully circle back and kick all of the code. Here is a link to that section. Once again, it is kinda there and kinda not. https://data0.adilas.biz/api https://data0.adilas.biz/top_secret/help.cfm?id=464&pwd=api https://data0.adilas.biz/web/api_samples.cfm Anyways, I hope that helps. If you want to get into things a little bit deeper. We do have some developers that would be willing to help you out for $25/hour to help with method call, getting started, etc. Anyways, just offering that as well if you wanted. Thanks Taylor and enjoy your day! Brandon Moore 435.258.5504 (home/office) support@adilas.biz :: www.adilas.biz "all data is live and searchable"

	Shop 530		Brandon Coding Time	2/24/2016	Emails and clean-up. Working on the Beaver project and going over code for the horizontal time view. Lots of commenting and testing new code.

	Shop 355		Brandon Gone All Friday	2/26/2016	Good day on the hill. I had about an hour of freeriding time, I taught a Jr. High lesson, gave a half an hour demo to Camiel and Travis on the new adilas Beaver project, and then taught both college classes. Good day.

	Shop 856		Recording notes and updating schedule	2/27/2016	Recording notes and cleaning up the Brandon time elements of time for my schedule. I'm trying to keep up with what is going on using adilas as the source.

	Shop 531		Brandon Coding Time	3/2/2016	Emails and recording notes. Worked with Bryan on the data 4 server. Tech support call with Newtek on domain stuff. Going over required updates for the data 4 server. Also met with Chris Scholle about rent and the adilas app.

	Shop 356		Brandon Gone All Friday	3/4/2016	Good day on the hill. I got to go freeride for the first hour. I then came in and worked with Camiell and Debbie for an hour on adilas and some of the new features and settings. After that, I got ready and taught my last two college classes for this year. We had a great time and the lessons flew by. Good stuff.

	Shop 532		Brandon Coding Time	3/9/2016	Working on a new page to help show what database tables and record counts exist for each corporation. This report will be used to help with the data migration process. This is a prep step for the upcoming world building project. The goal is to get everybody off the buss (shared database environment) and get each company or group of companies using their own database. I also helped out Shawn and Bryan with different little questions on their projects. Shawn is doing payroll functions and Bryan was working on servers and doing a custom data import project for a client.

	Shop 357		Brandon Gone All Friday	3/11/2016	Good day on the hill. Got ready and helped with a school in the morning. After that, I went and did some riding with both Cody and Adam. We were just messing around on the little beaver trails and lift. Good stuff. After lunch, Cody and I went and did a backside run off of second peak. Super fun run. We then ran another shuttle and did a second one. Adam and Karlie went with us on this one. The snow was even better than the first one. Super fun and good times. I really enjoyed it. Sometimes it is fun to remember why you do what you do.

	Shop 533		Brandon Coding Time	3/16/2016	Worked from 7 am to 1:30 pm with Bryan. We did a couple different projects. The first one was dealing with the invoice migration for A Touch of Style. We had a group discussion with Russell, Bryan, and I about the state of things. I went off about how many different things we are expected to do and how it is so hard to balance everything. I was kinda venting and gratefully both Bryan and Russell listened and helped me through it. Bryan and I then worked on the adilas API sockets and trying to get things up and running there. We recorded some videos and prepped and cleaned up a number of things. It felt good to get things cleaned up a bit more and make things tighter. Some of the pressures that exist are from things (code or sections of code) not being fully done or completed. We have a lot of things flapping in the wind. That adds stress because they are not done and people want to use them. Anyways, good session.

	Shop 358		Brandon Gone All Friday	3/18/2016	Good day on the hill. I spent the morning freeriding powder and playing with another instructor on a run called jump hill. It is a giant roller type jump. I helped with some carnival stuff and did some balloons. I also did some more freeriding with Cody. We did a Spring road run and a lone pine run. Good stuff. At the end of the day, I rode with Josh & Jen Wheeler for a couple of runs. They are good friends from High School and College. Good times.

	Shop 534		Brandon Coding Time	3/23/2016	Emails, clean-up, and doing catch-up stuff. Started to work on the custom wire job for Green Star Doctors. They wanted a feature where when an invoice is paid, a renewal date is cascaded into the future by 11 months.

	Shop 652		Adilas World	3/24/2016	Canceled - Brandon and Heather were at the hospital having their little baby girl.

	Shop 701		Calvin Chipman	3/24/2016	Canceled - Brandon and Heather were at the hospital having their little baby girl.

	Shop 1086		russell	3/24/2016	Canceled - Brandon and Heather were at the hospital having their little baby girl.

	Shop 1075		Adilas World/ Adilas for Business	3/24/2016	We're getting close, so let's look at where I am so far and see what needs to be tightened up. Canceled - Brandon and Heather were at the hospital having their little baby girl.

	Shop 359		Brandon Gone All Friday	3/25/2016	Canceled - Brandon and Heather were at the hospital having their little baby girl.

	Shop 535		Brandon Coding Time	3/30/2016	Talking with Dave Forbis and getting caught up. Dave just got back from a trip back East today. We did some light training on expenses. Working with Bryan on server stuff. Helping Will with some questions on sub inventory and his BioTack API stuff.

	Adi 1276		Dollars Off for In-Line Discount	3/31/2016	Currently add discounts that deal with dollars off get ran on a separate line item. We have had requests to get this function to work on a per line item basis. Bryan, Alan and Brandon completed this project 2018

	Shop 985		Brandon out of the office all day	4/1/2016	Went up to Beaver Mountain. Ended up giving an hour long training session to the Cammeil and Debbie. They gave me a small list of requests. Most of them dealt with navigation and removing un-needed fields from the add/edit page on the flex grid. That seems to be a common request. Basically, people love the functionality, but it looks or feels complicated. They want it to be a more simple type interface. Part way through the day, I spoke with Travis Seeholzer about adilas and what we can offer to Beaver Mountain. I had a great day on the hill and got in a lot of just fun freeriding. I ended up spending all afternoon riding with students that I had in my college classes. Good day.

	Shop 1204		Hypur - Team Meeting	4/13/2016	Team meeting for the Hypur project. We will go over the projects and make the assignments. Looking for the following attendees: Dave Forbis, Brandon Moore, Shawn Curtis, Bryan Dayton, Alan Williams, Nick Vaughn, and Will Hudson. Notes: Dave ran the meeting. He had a bunch of topics on the whiteboard (wall). He had a small agenda, the projects were listed out, a few small details per project, a light time budget, and assignments. Dave did an awesome job. I loved it. Shawn did quite a bit of talking and did great in the role of lead developer. All of the guys seemed to be excited and the meeting went very well. I did some light training on team building and helped wrap things up and make connections. My favorite part of the meeting was watching both Dave and Shawn run with things. They did great. I'm really excited to see how this project turns out. This is a step into a bigger playing field. Good stuff.

	Shop 987		Brandon out of the office all day	4/15/2016	Worked from home.

	Shop 1025		Brandon - Working on own projects	4/20/2016	Emails and tech support stuff.

	Shop 988		Brandon out of the office all day	4/22/2016	Went in and had a full day. See other entries for more details.

	Shop 1026		Brandon - Working on own projects	4/27/2016	Working from home. Emails, writing checks, and light tech support.

	Shop 1027		Brandon - Working on own projects	5/4/2016	Emails, project management, and helping the guys get settled into their projects. Working with Nick on the Hypur project C and E pieces. Basically, it is getting and setting JSON objects and passing them to the task queue. Working with Bryan on some of his last minute fixed for the Hypur project A stuff. More emails and tech support. Small phone calls and trying to get things all going in a good direction.

	Shop 990		Brandon out of the office all day	5/6/2016	Shawn came up to my house. We were going over the Hypur project and doing some planning and documentation stuff. We went through projects A and B together. We then took a break and I worked on other emails and tech support stuff. After that, we got Alan on the line and went over project D - the task queue. We did a GoToMeeting session and brainstormed on what was still needed. Productive work session between myself, Shawn, and Alan. Hopefully the first of many like this.

	Shop 1144		Working on Hypur projects	5/9/2016	All day working on Hypur projects. The first part of the day was spent with Brandon and Alan working on the main invoice post for new invoices. We were converting from SOAP/XML to JSON. Lots of testing and going back and forth. We were on the phone multiple times with Hypur. The last half of the day was spent with Bryan working on the flow for the payment refund API method calls and page flow. Lots of reworking and light testing.

	Shop 991		Brandon out of the office all day	5/13/2016	Working from home. Tons of random stuff. Emails, quotes, Hypur code sign-off, a conference call with Hypur, tech support, phone calls with other developers, a product demo, and other random things. Busy day.

	Shop 1029		Brandon - Working on own projects	5/18/2016	Emails, tech support, and small bug fixes. I had to login and get current tax tables from data 0 and push them out to data 4. Somehow we were missing something. That seemed to fix the payroll problem on data 4. I then worked on the Full Circle customer API stuff and added a sub query to help with a last purchase date. The original code came from Seth Johnson from Full Circle. I tested and posted new files online. I then did some vendor merging for J&J Trailers and J&J Motorsports. Other emails and tech support stuff.

	Shop 992		Brandon out of the office all day	5/20/2016	Worked from home. Bryan came over and we worked on two different projects. We spent quite a bit of time going over his API socket project for Jane. It was dealing with searching out part numbers and inventory items. The new changes were dealing with being able to search system special line items (unlimited items). Lots of code review and work. As we were working, we got a number of phone calls from Jane about other API's and tech support type stuff. We then prepped for conference call with Hypur. We got on the call and started to show the work and changes. It went ok, but we ran into a couple of questions and bugs. After the conference call, we got on the phone with Alan and went over what was said and new requests for the application. With Alan, Bryan and I talked about the two main projects we are on. We went over the Hypur stuff, new requests, and direction. We then jumped right into the Jane project and talked about API socket stuff. The last half of the afternoon was spent with Bryan and I working on the main addCustomer API socket. The method already exists inside the secured environment, but had not been exposed to the outside public. It has over 40+ arguments. We went over ways of simplifying, defaulting, and dynamically allowing options to be added and/or left off. With that being the case, we spent a ton of time working on defaults, looking things up, and helping to standardize the process. Throughout the afternoon, we had a number of other contacts from the developers at Jane that needed help with getting to the API's, turning things on, and testing connections. When you mix all of these things together, the day was very busy and kinda crazy.

	Shop 1030		Brandon - Working on own projects	5/25/2016	Emails, tech support calls for developers, and reading through documentation that was created for Hypur and the new changes that we have been working on. Alan did the documentation and it has screen shots, info, verbage, and explains a number of the features. It looks great. We reviewed it and sent it on to Hypur. I also got on a tech support call (GoToMeeting session) with Tiffany from JaneFour20. We were logged into the live data 3 server and running some raw database queries. I then put together some screen shots and sent them out to the Jane Team. Light help around the shop. Different small questions here and there from the developers. I also approved Bryan's first mini internal bid to do an adilas API socket clean-up project. He did quite a bit of research on the pages and put together a nice spreadsheet of the info and estimates of costs and time for each piece. I was impressed.

	Shop 993		Brandon out of the office all day	5/27/2016	On a phone call and GoToMeeting session with Steve to go over how to pass data from adilas to outside parties. We built some small test pages and did lots of testing. The session went really well until we ran into a problem on how ColdFusion sends JSON values to the other 3rd party servers. We spent the last half of the session doing research and trying different things. Lots of testing of something that should be quite simple. It seems that ColdFusion is flipping some things behind the scenes and making it difficult.

	Shop 1031		Brandon - Working on own projects	6/1/2016	Recording notes and getting caught up on back time entries in the adilas shop site. For some reason, I feel driven to record parts of the story. Russell was here today and nobody else was, so, we worked on some new ecommerce settings as well.

	Shop 1385		General	6/1/2016	Emails, tech support, and documenting some brainstorming done by Russell and Brandon.

	Shop 994		Brandon out of the office all day	6/3/2016	Tech support, phone calls, and emails. On the phone with Steve for almost an hour catching up on current projects, positioning, and where we are headed. We talked about a number of upcoming projects and where current projects are at as well. Busy times.

	Shop 1032		Brandon - Working on own projects	6/8/2016	Quoting session with Dave and Shannon. Lots of different quotes. Many of them needed additional research before actually putting numbers to things. That is ok. We also did a whiteboard session to talk about payees, permissions, and taking the permissions out to the location level. Along the way, we talked about various quotes, projects, and who is going to follow-up on what. We also did some light tech support questions to help Shannon with some of the questions that have been asked to her.

	Shop 1478		Making changes to the data 1 server	6/8/2016	Working on changes to the data 1 server. Fixed a couple files dealing with the customer queue. Sent a number of text messages back and forth between Brandon, Shannon, and Steve. On a GoToMeeting session with Steve looking at servers, queries, code, and talking about options. We made some changes and even purged some really old data from the queue (all records prior to 2015). We did make a back-up if we ever needed that data again. We also logged into the other servers and looked around to make sure things were ok. Crazy evening!

	Shop 995		Brandon out of the office all day	6/10/2016	On a 3 hour GoToMeeting session with Steve. We worked on a number of Steve's projects. He is working on the sub inventory stuff and update PO data for his Colorado Metrc homepage. That page helps our clients pass adilas data to the state compliance sites to help sync up the different sites. We also went over a number of new code pieces and made a bunch of changes. We chased some bugs down and fixed a couple of other pages that he had issues on. Good work session. We also had a good brainstorming session on packages and part/item conversions and units of measure. Here are a couple of small notes that went along with our session. - We may want a couple of new fields on a per part or item basis. This would include fields to hold the normal sales quantity and an alternate unit of measure. Currently Steve is doing this or something like this by hijacking the weight field and the bin number or catalog page field. This is a way to do some smoke and mirrors and setup a one-to-one relationship for the items. In normal English, this means we need a show quantity, a show unit of measure, a real quantity, and a real unit of measure. For example: Say I wanted to sell 1 package which actually was 16 ounces. So, the show values would be the 1 package while the real values would be the 16 ounces. Hopefully that makes sense. Like I said, Steve already has a couple of companies doing this but hijacking other existing fields to make it happen. - I would love to see conversions be part of a one-to-many relationship vs. a one-to-one relationship. - Maybe think about the part categories or going up a level or so. We would love to do something along the lines of rules and assignments, similar to the my cart favorite - smart group buttons. These rules and assignments would be for both pricing matrixes and conversions. - Help things be a factor of one. For example: 1 something equals x of this unit of measure. 1 something else equals y of this unit of measure. Keep things consistent. - Use the template structures from part categories and sub categories. Be able to go up the chain to reduce the maintenance on the rules and assignments. - Think inheritance or be able to break out and create your own values if needed (a child could lean on a parents rules and assignments or a child could make their own rules and assignments depending on needs). - Think tiered pricing, tiered conversions, etc. Both will end up using some kind of rules and assignments of some kind. - We have some other brainstorming on this same subject for sub inventory stuff. See attached for a multi page document of some of our brainstorming for the sub inventory and cost controls stuff. Some of these subjects get pretty deep.

	Shop 1033		Brandon - Working on own projects	6/15/2016	Added Alaska as a new time zone to all servers. Changed the Jane API to a query with a sub query vs. multiple queries with loops and lists. Tested code with Bryan and found a problem with the special characters in the product descriptions and how the URL encoding of JSON objects was being done. Started working on a 12 month payment history for a loan application.

	Shop 996		Brandon out of the office all day	6/17/2016	Working from home. On a GoToMeeting session with Steve. We were on for about 2.5 hours. We worked on some outbound API stuff for Steve and some state compliance systems. We also worked on some custom cart settings, gram tracking, dynamic math, and output that shows comparisons. I had a phone call with Calvin and we went over some more plans on changing up the sub inventory stuff. This will change the role and current flavor of sub inventory. I also spoke on the phone with Will about API's, projects, and how we need to get some of the documentation done and going along. The morning had a few different sessions. Kinda bouncing here and there.

	Shop 1471		Brandon out of office	6/20/2016	Brandon was out of the office helping a local boy scout troop with the pioneering (ropes, pulley's, and lashing stuff).

	Shop 1034		Brandon - Working on own projects	6/22/2016	Started the morning off with a bunch of emails, tech support stuff, making some screen shots and graphics, and some debugging. I was bouncing between the Hypur and the Jane projects. Both projects are needing a little bit of attention. This is kinda funny, but we are changing things on our side and Jane is asking what is going on? Hypur is changing things on their side and we are asking what is going on? I heard this from somewhere but we each get to eat each others virtual dog food (what we are serving out). Kinda interesting. Started working on some sub inventory standardization stuff for a couple of known issues. Concept - who is prepping for who? It's a game of sorts. I had the thought today, who is prepping for who? Are other people prepping for me or am I prepping for them? Does it matter who does what (for example: job titles and job descriptions)? We need to get things done, that does matter, but does it matter what side of the fence we are on (serving or receiving)? We may need to get things prepped for us and we may need to prep things for others. We are all on the same team. Interesting concept. I like it. The concept has a service flair to it.

Showing 150 of 852 Page 1 of 6 :: Go to page ::

What's New

Products

Find Us