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 - (988)
Showing 150 of 988 Page 1 of 7 :: Go to page ::
Photos	Time Id	Color	Title/Caption	Start Date	Notes
	AU 3375		Daily Ideas	3/2/2006	Goals: - Smooth - Efficient - Less is more - Dynamic - Generic yet specific - Reports - Small learning curve - Reports - Small learning curve - Convention able - Quick and dirty - Reliable numbers - Secure - Empower the person - Fast - Low bandwidth - Code reuse - Expandable - Organized - Printing - Low click number - Standard - Local validation - Live - Limited access - Modular/self-contained - Easy to maintain - User friendly - Multi browser windows - Global settings - Good work flow - Helpful - Cutting edge - Out of the box - Mixing technologies - Authorized - Flexible - Page settings - Visual appeal - Skin-able - Low cost - Updateable - Simple - Fun - Scalable - Merge (accounting & operations) zipper MSAI Tables: please see scan in photo gallery Inventory & Operations: please see scan in photo gallery

	AU 3493		Daily Ideas	9/11/2006	Stock Migration Steps: 1. Drill down to stock – check for valid stock # 2. Check last 8 vin (if numeric abort) no edits allowed o Check for customer id o Check zip code & first & last name 3. Check location 4. Check purchased by id (need to match up old and new id’s) 5. Check make and inventory type 6. Check model 7. Check salesperson o Check other salesperson 8. Check zip code & first & last name (move to after step 2) o Check for zero – show add customer form o 1 or multiple – choose or add new – prepopulate info 9. Check old and new title account (check actual text value – force to lower case)

	AU 3096		Daily Ideas	4/28/2007	PO’s?: Is there any other way to stock in inventory? What is it and how does it work? Adjustment PO’s? - Likes: - Dislikes: - Wishes: be able to search by external invoice number (not just PO #) Parts?: Parts to vendors? Hard coded parts? Validation on qty on hand? Searches and look-up? History? - Likes: like the parts list feature liked the parts search with details - Dislikes: - Wishes: go up to three decimal points. Create a service category that holds items like shop supplies, freight, labor, and basically don’t validate against an inventory qty Invoices?: Modes – customer, counter, internal, transfer? Crossing over to sell anything out of the system? Assigning invoices to a certain person (labor)? More than one salesperson? - Likes: - Dislikes: unable to edit internal tickets - Wishes: on choosing a vendor be able to type in the number instead of scrolling. Keep parts and units separate. Tracking and seeing other things in store (add-on buys). Would like to see history. Need a save as you go option. Need start date and a pick-up on transaction date. Allow multiple people to touch the tickets, basically show who created and who added the line items. - Internal tickets: problem adding a ticket to items marked sold instead of status sold. Maybe check for payroll status and paid commission. Taxes?: per line item or off of total? - Likes: - Dislikes: have to set it every time - Wishes: have the store pre-selected and pull in tax for that store. Allow them to switch if necessary. Currently almost a penny low, get better rounding. Go to a third decimal point on rounding. Payment Types?: will allow for multiple types and split payments. - Likes: - Dislikes: - Wishes: Reports?: Which ones do they use? Are they fast or slow? What do they want or need to see? - Likes: like the profit per line - Dislikes: don’t show qty and rate – just show extended values - Wishes: Vendors?: - Likes: - Dislikes: not alphabetical - Wishes: make vendors specific to store location. Be able to search for parts without a vendor. Other notes: - Run tickets like an e-commerce app. Keep everything in session vars until they commit. Allow things to change, parts to back out, and vendor look-ups by alpha or numeric. - Save quotes for shopping quotes - Credit apps and financing - Warranties - Physical street address and phone numbers on the invoices - Charges and accounts receivable - Terms - Show difference between amount due and invoice total - Transfers between corps, stores, etc. - Sell from one location to other locations - Shipping - Save partial tickets for specific users - Payables and receivables - Automate deposits from invoices - Deposit on units and showing to other users that someone is on that unit. – Possible 2nd deal. - Automate credit card transactions – possibly integrate automatic swiper - When printing out paperwork make sure and add the verbage and warranty - On each invoice – track how much, what did we get, and how much was actually deposited – somewhat of a mini accounts receivable per invoice - On floorplan accounts. We need to track a history for past payables. This is a huge piece that has been missing and is required for the Balance Sheet. - Add notes to voided items – deposits and receipts - 4 trade ins and 4 tax categories

	AU 3216		Daily Ideas	8/24/2007	Notes: - Store specific o D&H – unit specific o Collected shipping – unit specific & type specific - Need to lock the D&H down - Need a second title/registration name and add verbage – must be typed in exactly how… - Need a general type “other” or customers - Add in cell phone Step 2 and on sell unit - Up special line items to 5 - On step 5 add GAP Insurance - Continue the checkout process - Tie cart items and unit sales process to get until the final step - On vehicles validate numeric odometer reading - Back tie all cart main pieces - If invoice gets backed out – make sure units get put back into stock, etc.

	AU 3341		Daily Ideas	12/15/2007	Notes: - FORM - URL - Database - Error pages - Check for problems with already stored data - Java script - Java sc - Vb script - Src = i frame - - - - - - - - On click - * . * non numeric on either side - URL Encoded Formats - Force to lower case - % 3C = < - % 3E = > - % 3F = ? - % 2A = * - % 2F = / forward slash - % 5C = back slash - ( ) - ) ; - Eval ( - Evaluate Other Notes: - Corp specific vendors - Employee/payee new permission for multicorp - Options – Don’t allow password changes for employees from different corps - Other possible security measures - Need a small description for what the system is and does

	AU 2528		Daily Ideas	6/2/2008	-Drop vendor down 10px -Amount – 10px -Tie a vendor account (auto fill) -Record as printed -My number converter -Convert dollars to string values -Get check write values – zero main, zero payment -Get print status – data in, main zero, receipt type, verified, posted, payment zero, check amount, check type, money type, bank, already printed, inactive payment, needs printing, non-numeric check -Record bank check settings

	AU 2685		Daily Ideas	11/11/2008	-On paying splits – check for 1 checked item and send to edit or add payment. -Change all of the web service methods to be generic and able to handle adds or edits regardless of modes.

	AU 2686		Daily Ideas	11/13/2008	-Create a bank registry report – default to 30 days and add pagination to each page. -Status link per page (on the edit line items page) show what is needed, pending or missing -Deposit photo gallery -Change to part id # instead of vendor and part number -Mass verify on deposits and receipts – add date and show 25 per page -Check splits that have been verified – showing up on verified bank statements. -Add a check box to help put things “on account” on the add_edit_receipt page. -Add a name to the my hours page. -Split or add a new verified and flag to the e/r payments. This will also require a logic change on verify banks and posting final numbers. Check main verify page and every other method that verifies e/r’s. Add new options to payment search. -Change the web inventory link on web_application_prep.cfm page. -Print status stuff to check/payment search -Add vendor/customer names to advanced line and payment searching -Add a numeric check value to receipt payments -Do a major check on mark as payable, receipt paid, splits, rei’s, PO’s, check reqs, normal, negative #’s, subs, etc. Problems with negatives in the past. -Charts – see with your eyes – add some visual candy!

	AU 2687		Daily Ideas	11/17/2008	-On receive multiple invoices – add money type as a search criteria. -Change the lock permission to basic around the board -Create the automate invoice section. Reoccurring invoices and payments. -Create the history look-up section “activity per corp” -Add anchor tags to the permissions page -Balance sheet items and balance sheet report -Report and form builder -Payroll IRA calcs – no federal but full ss and medicare -On verify bank reports. Allow a check range (numeric) and show only deposits or expenses. -On reports – convert day, month, year look-ups to text entries. -Check the math on the payables page under splits when dates are used. Is shows all payments not just satisfying pmts. Doubles the “split” pmts. -At some point, it might be nice to record verify bank history; include date/time and person.

	AU 2673		Daily Tasks	11/18/2008	• Fixing a payroll calc for simple IRA’s. They require a pretax deduction but not a full deduction. They are federal exempt but require full social security and Medicare. Made changes and posted files. • Working on the new verify receipt payment fields and converting to real numeric check numbers.

	AU 3561		2009	1/1/2009	YEARLY ACCOMPLISHMENTS 2009 Steve, This is a list of things that happened and accomplishments made during the 2009 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 2009: • Lots of balance sheet work. Payables, floorplan, inventory, receivables, and look-back reports. • Added the user-maintained balance sheet photo gallery. • Added the part number usage report. • Posted the balance sheet files online. This was round 2 and the first balance sheet available to general users. Round 1 was back in 2008, very limited, with known holes. • Added options to format the balance sheet in to a traditional format for printing. • Added state income tax settings for Arkansas. February 2009: • Allowed invoice notes (printable and internal) to be searchable. • Added pagination (next photo) on the big photos in the gallery. • Added the reoccurring invoice section. • Added the printer friendly invoice (capable of showing multi invoices with an address that would fit in a windowed envelope). March 2009: • Added the work in progress invoice setting. • Added reports for outstanding deposits and outstanding payments (checks). • Added reports and switches for cash accounts (running off of verified dates) and accrual accounts (running off of basic dates). • Added the limited invoice format (no costs and only for work in progress). • Rework of the entire work in progress section. Originally, we didn’t know that they couldn’t show up like normal invoices. Made major changes to balance sheet, income statement, couldn’t show on receivables, and couldn’t show on sales tax reports. Somewhat of a surprise! • Fixed a date problem with PO payments and stock/unit payments. Original date was when recorded not what date the expense was holding. Small disconnect. • Added a mid-year change to federal tax tables (part of a stimulus package). April 2009: • Added barcoded and RFID tag fields to the parts table. • Added the recipe/build section. • Added hidden line items to PO’s, quotes, and invoices. • Added the invoice profit per line report. • Created a search and add invoice line items section for invoices that had already been created (no longer in cart mode). • Permission rework for parts, sales, and being able to not see costs. • Added the “save as…” feature for quotes. • Added admin work in progress permissions. • Added a grouped salesperson report to the daily/weekly report. May 2009: • Added the customer type. • Added the customer additional contacts and customer log entries. Tons of CRM (customer relationship management) options. • Added the customer settings to the shopping cart and checkout process (if invoice is tied to customer). • Added the bank helper report (deals with dates prior to bank starting dates). • Added the advanced customer search. This is a build your own customer report page. • Held the first public adilas.biz seminar at Steve’s house. We had 10 people there. Great meeting. • Added code to help verify expense/receipts. There was a problem with payments getting verified and the main would still be outstanding (or vice-versa). Tied the two together (if a 1 to 1 relationship existed). This deals with reconciling banks. • Fixed a rounding error problem with PO and invoice line items. • Allowed the quick search type to follow you from page to page. Once selected, it would stay selected until changed. June 2009: • Created documentation for web/customer inventory pages via web services. • Added the corp stats report (pre-cursor to the history homepage report). • Added the flex grid tie-in application. This is an application that rides on top of the main application and is used to help tie things together and record additional information. Very dynamic and very flexible. • Added the next day link on the balance sheet homepage. July 2009: • Added the history homepage permission and report. Lots of work on drill-downs and sub reports. This is the corp stats report with more filters and options on a per corp basis. • Added an image/scan drill-down report. • Brainstorming and research on multi decimal points (dewy decimal). • Added first round of crop-wide settings. There were only 5-6 to start with. They were physical year, parts mark-up, default tax category (parts and customers) and ice-down date (disabled). • Major change on how inventory values were determined. Old way was to use the current part number cost times the quantity on hand. The current cost was a variable and could be changed. That reflected itself forward and made a moving target for the total inventory value (a single price change could change everything). The new way is to use the actual costs recorded in the database (as they happened). This removed the current cost variable and allowed exact drill-downs to underlying data. Big break through on tracking inventory. • Added the paid dates and paid flags for invoices and expense/receipts. This helped tighten things up in accounts receivables and accounts payables look-ups and look-backs. August 2009: • Added two new hard-coded parts to the system. They are “Fee” and “Collected”. • Added a search option for adding PO line items. The old way was you had to know the exact part number and cost in order to add a line item. The new way allows you to search the system for the info. • Added the PO requests. These are non-payables, not counted as inventory, and not yet live. They may be turned in to live PO’s later. • Added the option to change the vendor/payee id number on expense/receipts. • Added new options to the web/customer inventory pages (still dealing with units). Options included next photo on big photos (pagination) and medium thumbnails. • Added some rounding on all stock/unit prices (that were calculated on the fly). This was both internal and for web/customers. • Set all the web/customer inventory items that had been sold to a hidden price value and showing the word “Sold” instead of a price. September 2009: • Added 25 new corp-wide settings. Most were set to inactive but added as future placeholders. Slowly started adding them and activating them as time allowed. Setup the main corp-wide settings page. • Changed work in progress invoice name to a transition invoice name. • Added the bank check/deposit register as an optimization project. • Added the vendor of “All” to the printable parts list report. • Added the “parts” to the online web pages for web/customers. Activated web specific corp-wide settings. • Added flex grid tie-ins to the output for different invoices modes (printer friendly, limited format, and save as PDF). • Opened up the limited invoice format to all invoice types. Formally, it was only open to work in progress or transition invoices. • Changed names on the main switchboard page. For example: The permission name and menu option used to be called “basic add/edit deposits”. This was changed to “deposit homepage”. Tons of other name changes to help standardize the naming convention and layout. October 2009: • Added save as PDF for PO’s. • Added the PDF document management section. This deals with pulling database info and placing it on a pre-defined PDF form or document. • Launched the first PDF form – Texas 130-U. This was an optimization project and the first dynamic PDF form (custom paperwork). • Added other PDF forms. Most were start to finish in about 2 hours. • Added some java script calculations on the cart checkout page to show change due. Calculations were made and shown but no physical data was ever recorded. November 2009: • Took off all of the built-in subs to stock/units. For example: gallery fee, web/computer fee, etc. • Allowed negative parts quantities to flow through to the balance sheet. Prior releases only allowed positive inventory counts to flow to the balance sheet. • Added merchant processing. This is the ability to take secure credit card payments, process sales, run transactions, view transactions details, and void transactions if needed. • Processed first credit card transaction through adilas.biz on 11/7/09. • Created the merchant processing flyer and demo payment page. • Added extended prices, costs, and profit to all recipe/builds. • Added the cart profit per line report. • Added a new silver “Specialty” permission color. • Allowed the main PO vendor id to be changed. Also added what we called “Special” PO’s. These are non-vendor specific PO’s and they allow for generic or homogenous parts like steel, wood, water, flour, etc. (items that may be purchased from multiple vendors yet are considered the same basic thing or sold out of a general pool). • Small patch/fix to the P&L for deposit types that are not attached to an invoice. December 2009: • Loan from Steve to adilas to keep it going. • Added the wholesale cart builder permission and function. This allowed multi stock/units on a single invoice with a point and click interface. Max of 50 per invoice. • Disabled the checkout buttons and options from inside the cart mode if the cart was in quote mode. • Added the cross-corp sales permission. This is taking the wholesale cart builder and allowing a sale from one corp to another corp. Basically, sell from one and stock in unit in the other corp. Tie it all together. • Tightened up the transition invoice dates and added a graphic to show what we called the “magic window” (transition period). • Added options to add more than one customer and/or customer contacts to a shopping cart. • Added a reoccurring invoice flag to the customer log and customer search results. • Added a default salesperson per customer. • Added two new time periods to the reoccurring invoices. They were quarterly and semi-annually. • Added 2010 tax tables and settings.

	AU 2368		Brainstorming - Displaying Flex Grid	6/5/2009	Questions about displaying flex grid: 1. Once the database has been searched and records are ready for display… then what? How do I make the results and report as small as I can and still show the fields that have data? There are close to 30 fields that are available, I would really like the reports to show between 5 & 15 fields. 2. Options: a. Start with the query results b. Somehow I need to get the length and value (numeric) for the different fields. c. I then need to figure out which fields to show. d. Maybe I could convert all values to numbers (use the length on strings) and then add them up (sums). Then do a check for sums at great than 0. If yes, add the values to an array. We would then be able to lip over the array and query.

	AU 2375		Brainstorming - Questions & Ideas for Multiple Decimal Places	7/9/2009	Questions & Ideas for Multiple Decimal Places: 1. Currently (as of 7/9/09) all numbers that allow decimal places are forced to two decimals. We have a need for companies to be able to track factions of items and also fraction of pennies per item (both cost and price related). We also have a need to track weights and fractional weights extended to multi decimal points. 2. A couple of known issues: a. Database Storage: - Currently all decimals are set to (9, 2) where nine is the max digits and two is the decimal places. (9,999,999.99 – 9 total digits, 2 decimal places) - I don’t want to expand all tables and fields. The default is two decimal places and should work for 95% of our users. - I’m thinking that a separate table might be in order. I would like to keep everything else as small as possible especially since this (multi decimals) is not the default. b. Output and formatting: - Currently al output is formatted to two decimal places. What would it look like with some formatted to 2,3,4,5,6… places. I would think that it would look funny or inconsistent. - How would I control the formatting? One of the problems would be lining up the decimal point for adding. - It might require a dynamic mask value to be generated and then assigned during page output. - If I have to do different math, it might slow the pages down. This could include page queries and drill-down options. - How do I control permissions and options? - What about rounding error? c. Where do these values (multi and extended multi) need to show up? - When entering parts on a PO - When adding or editing a part number in the database - When using parts in the shopping cart - Quotes - Invoices - Printable invoices - Pdf’s - Profit per line - Recipes d. How do these changes effect the financials? - I.S. i. Revenue ii. COGS - B.S. i. Inventory counts & values ii. Payables & amounts iii. Indirectly – net profit 3. Possible ways to control the use of multi decimals: a. Corp-wide settings b. User maintained (open) allow user to set detail level – default to 2 c. Dynamic (limited open) watch from the background 4. On weight output, I think a var char (25) field would be best. That way the user could put the value in lbs., oz., grams, or mixed. It could be left blank, straight numeric, or any alpha-numeric combo. Multi decimal samples: (Please see scan in photo gallery)

	AU 1476		Daily Ideas	8/26/2009	-It might be nice to add a section where the different corps can search their billing and payments (invoices and quotes from adilas to them). -Inventory type – specific units (vehicle), sub types – large, medium, small, seasons (truck), Make – Storage units, building # (Ford), Model – XX x YY(large), WW x PP (med), BB x CC (small), (F-150) Flex grid tie-in for units: - Customer id - Contract start date - Contract end date - First name - Last name - Business name Sort stock units by: - Stock numeric - First-stock alpha (5) - Different locations: For occupies & available -Receivables/late invoices – search by age -Statement links and printer friendly statements -Pre-payments as a system maintained balance sheet item -Show available units on web site. -Reoccurring quarterly (new time period) -Deposit photo gallery -Reoccurring for bills and vendors -Checkbook register -Receivables – report age search (type in days) -Add last payment and age on receivables -Add customer links to receivable page. Name=edit link, log=log -Show a printed flag on invoices -Change the last date on reoccurring invoice -On customers, add a flag to show if they are set up on reoccurring or not. Billing status. -See customers from an advanced search – general overview where are they at when were they invoiced, when was the last payment, what is still owed, etc. -Look at options to move towards email billing - Possible pdf and attach on the fly - Possible send links with invoice number, date, amt, and age -Need a flag from reoccurring invoices back to customer reports and vice versa. Maybe also the frequency. -Search options for customer and vendor: - biz name, - last name, - first name, - corp-wide setting -Customer photo gallery -Defaults on statements - Payment terms - Printable statement notes - Make these dynamic and call pre-sets or standard verbage -See loose paper for additional notes

	AU 1540		Daily Tasks	11/10/2009	• Went in to town to check with a contact, they told me a soft no. • I then went to the office and ended up meeting with Steve and brainstorming on a number of projects. We talked about new permissions for part quantity tracking, adding a sale price option to trailers and toppers. Showing the difference between mark-up vs. profit percentage. We also talked about creating a non-vendor specific PO and allowing part numbers to be general or homogenous (bulk/generic) and what that would take. 10 miles. • Working on help files.

	AU 3562		2009	12/31/2009	YEARLY ACCOMPLISHMENTS 2009 Steve, This is a list of things that happened and accomplishments made during the 2009 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 2009: • Lots of balance sheet work. Payables, floorplan, inventory, receivables, and look-back reports. • Added the user-maintained balance sheet photo gallery. • Added the part number usage report. • Posted the balance sheet files online. This was round 2 and the first balance sheet available to general users. Round 1 was back in 2008, very limited, with known holes. • Added options to format the balance sheet in to a traditional format for printing. • Added state income tax settings for Arkansas. February 2009: • Allowed invoice notes (printable and internal) to be searchable. • Added pagination (next photo) on the big photos in the gallery. • Added the reoccurring invoice section. • Added the printer friendly invoice (capable of showing multi invoices with an address that would fit in a windowed envelope). March 2009: • Added the work in progress invoice setting. • Added reports for outstanding deposits and outstanding payments (checks). • Added reports and switches for cash accounts (running off of verified dates) and accrual accounts (running off of basic dates). • Added the limited invoice format (no costs and only for work in progress). • Rework of the entire work in progress section. Originally, we didn’t know that they couldn’t show up like normal invoices. Made major changes to balance sheet, income statement, couldn’t show on receivables, and couldn’t show on sales tax reports. Somewhat of a surprise! • Fixed a date problem with PO payments and stock/unit payments. Original date was when recorded not what date the expense was holding. Small disconnect. • Added a mid-year change to federal tax tables (part of a stimulus package). April 2009: • Added barcoded and RFID tag fields to the parts table. • Added the recipe/build section. • Added hidden line items to PO’s, quotes, and invoices. • Added the invoice profit per line report. • Created a search and add invoice line items section for invoices that had already been created (no longer in cart mode). • Permission rework for parts, sales, and being able to not see costs. • Added the “save as…” feature for quotes. • Added admin work in progress permissions. • Added a grouped salesperson report to the daily/weekly report. May 2009: • Added the customer type. • Added the customer additional contacts and customer log entries. Tons of CRM (customer relationship management) options. • Added the customer settings to the shopping cart and checkout process (if invoice is tied to customer). • Added the bank helper report (deals with dates prior to bank starting dates). • Added the advanced customer search. This is a build your own customer report page. • Held the first public adilas.biz seminar at Steve’s house. We had 10 people there. Great meeting. • Added code to help verify expense/receipts. There was a problem with payments getting verified and the main would still be outstanding (or vice-versa). Tied the two together (if a 1 to 1 relationship existed). This deals with reconciling banks. • Fixed a rounding error problem with PO and invoice line items. • Allowed the quick search type to follow you from page to page. Once selected, it would stay selected until changed. June 2009: • Created documentation for web/customer inventory pages via web services. • Added the corp stats report (pre-cursor to the history homepage report). • Added the flex grid tie-in application. This is an application that rides on top of the main application and is used to help tie things together and record additional information. Very dynamic and very flexible. • Added the next day link on the balance sheet homepage. July 2009: • Added the history homepage permission and report. Lots of work on drill-downs and sub reports. This is the corp stats report with more filters and options on a per corp basis. • Added an image/scan drill-down report. • Brainstorming and research on multi decimal points (dewy decimal). • Added first round of crop-wide settings. There were only 5-6 to start with. They were physical year, parts mark-up, default tax category (parts and customers) and ice-down date (disabled). • Major change on how inventory values were determined. Old way was to use the current part number cost times the quantity on hand. The current cost was a variable and could be changed. That reflected itself forward and made a moving target for the total inventory value (a single price change could change everything). The new way is to use the actual costs recorded in the database (as they happened). This removed the current cost variable and allowed exact drill-downs to underlying data. Big break through on tracking inventory. • Added the paid dates and paid flags for invoices and expense/receipts. This helped tighten things up in accounts receivables and accounts payables look-ups and look-backs. August 2009: • Added two new hard-coded parts to the system. They are “Fee” and “Collected”. • Added a search option for adding PO line items. The old way was you had to know the exact part number and cost in order to add a line item. The new way allows you to search the system for the info. • Added the PO requests. These are non-payables, not counted as inventory, and not yet live. They may be turned in to live PO’s later. • Added the option to change the vendor/payee id number on expense/receipts. • Added new options to the web/customer inventory pages (still dealing with units). Options included next photo on big photos (pagination) and medium thumbnails. • Added some rounding on all stock/unit prices (that were calculated on the fly). This was both internal and for web/customers. • Set all the web/customer inventory items that had been sold to a hidden price value and showing the word “Sold” instead of a price. September 2009: • Added 25 new corp-wide settings. Most were set to inactive but added as future placeholders. Slowly started adding them and activating them as time allowed. Setup the main corp-wide settings page. • Changed work in progress invoice name to a transition invoice name. • Added the bank check/deposit register as an optimization project. • Added the vendor of “All” to the printable parts list report. • Added the “parts” to the online web pages for web/customers. Activated web specific corp-wide settings. • Added flex grid tie-ins to the output for different invoices modes (printer friendly, limited format, and save as PDF). • Opened up the limited invoice format to all invoice types. Formally, it was only open to work in progress or transition invoices. • Changed names on the main switchboard page. For example: The permission name and menu option used to be called “basic add/edit deposits”. This was changed to “deposit homepage”. Tons of other name changes to help standardize the naming convention and layout. October 2009: • Added save as PDF for PO’s. • Added the PDF document management section. This deals with pulling database info and placing it on a pre-defined PDF form or document. • Launched the first PDF form – Texas 130-U. This was an optimization project and the first dynamic PDF form (custom paperwork). • Added other PDF forms. Most were start to finish in about 2 hours. • Added some java script calculations on the cart checkout page to show change due. Calculations were made and shown but no physical data was ever recorded. November 2009: • Took off all of the built-in subs to stock/units. For example: gallery fee, web/computer fee, etc. • Allowed negative parts quantities to flow through to the balance sheet. Prior releases only allowed positive inventory counts to flow to the balance sheet. • Added merchant processing. This is the ability to take secure credit card payments, process sales, run transactions, view transactions details, and void transactions if needed. • Processed first credit card transaction through adilas.biz on 11/7/09. • Created the merchant processing flyer and demo payment page. • Added extended prices, costs, and profit to all recipe/builds. • Added the cart profit per line report. • Added a new silver “Specialty” permission color. • Allowed the main PO vendor id to be changed. Also added what we called “Special” PO’s. These are non-vendor specific PO’s and they allow for generic or homogenous parts like steel, wood, water, flour, etc. (items that may be purchased from multiple vendors yet are considered the same basic thing or sold out of a general pool). • Small patch/fix to the P&L for deposit types that are not attached to an invoice. December 2009: • Loan from Steve to adilas to keep it going. • Added the wholesale cart builder permission and function. This allowed multi stock/units on a single invoice with a point and click interface. Max of 50 per invoice. • Disabled the checkout buttons and options from inside the cart mode if the cart was in quote mode. • Added the cross-corp sales permission. This is taking the wholesale cart builder and allowing a sale from one corp to another corp. Basically, sell from one and stock in unit in the other corp. Tie it all together. • Tightened up the transition invoice dates and added a graphic to show what we called the “magic window” (transition period). • Added options to add more than one customer and/or customer contacts to a shopping cart. • Added a reoccurring invoice flag to the customer log and customer search results. • Added a default salesperson per customer. • Added two new time periods to the reoccurring invoices. They were quarterly and semi-annually. • Added 2010 tax tables and settings.

	AU 2163		Brainstorming Drawing Barcodes 128-B in Flash	5/6/2010	Drawing barcodes 128-B in Flash: 1. We need to be able to handle up to 25 characters 2. Need to be able to handle dynamic content 3. Printable from the web to specific sizes and specs 4. Variable length and sizes of output 5. Needs to be readable and correct for 128-B standards Known: - 128 characters, each has 11 positions, sizes and spaces are 1,2,3,4, I have a list of black/white (bars & spaces) codes in “bbwwbbwbbbw” format for each character. - 128-B requires a start character, the value to encode, a check digit, and a stop character. The start and stop characters are standard but the check digit is a variable and will be one of the 128 characters. - The system needs to be able to calculate and draw (render) on the fly. - Most labels will be printed out using thermal transfer to sticker or label paper. - With the 11 positions… I’m assuming that each character only gets 11 and the next one will start on 12 as the first new character. I will need to verify this. - The check digit uses a special formula and then a special division valve. The actual results are not in the main division but in the remainder (left over value). This value then gets converted into a barcode symbol as well. - Flash is capable of drawing bars to exact specs. A loop that gets proper specs could be used to create content on the fly. Flash is also capable of duplicating a master line or bar on the fly. Positioning and printing are both very precise within flash. Technical Ideas: - Because each character has a specific pattern. It would be ideal to get the value to decode, split it into an array with each letter or character in each index, do the math calc to figure the check digit and then process the output with correct instructions and spacing. - Sketches, variables, etc. – See scan in photo gallery - The above example uses a factor of 1. What if I need to shorten things up and used a factor or 0.5, 0.25, 0.01 (etc.). - Working with zero kind of messes things up for basic math. - Here is how the start & end value can be figured: - You need: o See scan in photo gallery o Start with these values already set o To get to the next – do this - Say you have an array with the following values. o See scan in photo gallery - Two dimensional array, index 0=value, index 1=numeric look-up value o See scan in photo gallery - You would also need a look-up array that had instructions or code to make instructions. o See scan in photo gallery - Instructions would need to be: o Start x card = _________ o Bar length = __________ o Start x card = _________ o Bar length = __________ o Start x card = _________ o Bar length = __________

	AU 145		Daily Ideas	5/28/2010	More brainstorming for adilas mini P&L/balance sheet flow chart calculator: - See a couple pages back for more info - look around 3/20/ date range. - I want a web app that uses Java Script to do local calcs. - It only uses ColdFusion if converting and saving as a pdf. - Needs to be designed so that it is super simple. - Needs about 5 editable fields per section. All math is automated and done as you leave each field. - Net profit needs to automatically flow over to the B.S. under equity. - Quick calcs on both top and bottom. - Show tie between Net on P&C and Net on B.S. - All math is done with the tab key: once done – post a generic version online for free. The whole goal of this mini app is training and flow. Nothing is recorded in the database. Think quick and temporary.

	AU 156		Daily Tasks	6/12/2010	• Small tweak for a company website. Took off the American Express logo for the shopping cart. • Working on corp-wide settings. Changed the customer log field size from 255 characters to 65,000 characters. • Worked on the quick cash checkout process. • Uploading and testing files.

	AU 243		Daily Ideas	9/11/2010	-May need to add a security patch so that any outside form cannot submit to adilas. The user is required to login but that doesn’t stop homemade form submission. -Need a global show/hide parts on the web feature. This would only flip the show on web status. See the global mark-up for fast code. -Random idea on parts – I may need to create a set of pages to help people combine parts and make homogeneous or generic items. This will replace all other parts in PO’s and Invoices (line items) and will make those items go inactive. This may also require a PO type flip. -You should be able to look at any day in time and see the overall picture of who is at what check point. In order to do that, we need to really decide what the checkpoints are and map it. -Provide a digital, visual, interactive flow chart of how the system works. Main players, sub players, systems and sub systems. Think of the human body: Body as a whole, body parts, smaller parts, underlying systems, cause and effect relationships, clear down to cells. Map it out, show it and explain it!

	AU 235		Daily Tasks	9/22/2010	• On the phone with Steve going over things. Gave him a quick update on new permission and where we are headed. • Turned on some permissions for some customers for the advanced add to cart permission. Sent them an email with a brief explanation of the features. • On the phone with a customer going over how to make generic quotes. • Added new help files for new permission. • Started working on merchant processing pages to connect to the Merchant One payment gateway.

	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 2167		Brainstorming Who are the adilas players & how do they interact?	10/7/2010	Who are the players and how do they interact? No specific order… Corporation: - Scope: One of the biggest entities. The only bigger is a user or employee (this is because they can have more than one corp). - Operations: they are the box, bowl, or sandbox for all activities - Accounting: this is the end goal… where are we and how are we doing? o Corp start date o Inventory types o Number of decimals o Special line items o P&L physical year o Ice-down date - Buddies: tied to everything User/Employee: - Scope: the biggest entity yet the smallest and does all of the smaller transactions. This might be like a hallway around the different rooms. - Operations: they use the system on a daily basis, more than one may be required for certain tasks - Accounting: all entry is started on a base level. It is then passed on to the next station, state, or status. o Year-end W-2 and 1099 o Payroll o Expenses o Reimbursements - Buddies: tied to everything, they do the work… Flex grid tie-ins: - Scope: second under a corporation. They can tie together any sub piece in a 1-many relationship. This is a second level or virtual air level that flows over the main corp. This level does not compete with underlying data. It helps tie thing together. - Operations: this helps tell the story and creates links and relations, user-maintained - Accounting: no direct accounting ties but has or may contain supporting details - Buddies: could be anybody – built by the users and not required, very flexible Locations: - Scope: this is a sub of a corporation. On the simplest level the corp and the loc are generally the same thing. If more locations are needed, this is like adding additions, sub sets, and wings to a building. This could also be shown by different floors or levels. - Operations: this gets ties to almost every transaction inside the system. If only one location, it is somewhat redundant and un-needed. However, as soon as there is more than one, this helps separate and tell the story. Certain locations have certain jobs and functions. - Accounting: used everywhere. This is like thread holding everything together. o Start date o End date (not yet) o Status o Petty cash o Tax settings - Buddies: Tied to: o Deposits o Invoices o Quotes o PO’s o Expense/receipts o Balance sheet items o Stock units o Taxes o Floorplan o Income statement (P&L) o Balance sheet o Time o Flex grid Banks: - Scope: outside entity where money is stored, at least one is required. No limit (infinite) as to how many may play into the mix. - Operations: get money and make deposits, need money, write checks and pay for things - Accounting: the bank is one of the first entity on the balance sheet o Starting balance o Starting date o Ending date (not yet) o Status o Book dates (deposit and expense dates) o Verified dates o Reconciled dates o Posted dates - Buddies: o Deposits and expense/receipt payments o Balance sheet o P&L income statement Income Statement or P&L (Profit and Loss Statement) – Report - Scope: This is not a physical entity and is a report. It gathers up revenue or income, costs of goods sold, and business expenses. This is one of the primary financial documents. This report has a dynamic relationship with many different parts of the application. - Operations: All of the reports (giving of data) to the income statement that are done as tools are used throughout the system. This report is somewhat like the pulse or heart beat for the corporation. The income statement looks at a date range for one or more location. This report is flexible and may be altered to find or look-up specific trends or totals. - Accounting: This is the first stop for most day to day transactions. Certain pieces live and die here on the income statement. Eventually, the net profit is passed on the balance sheet report as net profit in the equity portion of the balance sheet. This report (P&L) runs a series of complicated math formulas according to what it finds from the system. By saying complicated, this doesn’t mean hard, it means in depth filtering and searching. - Buddies: Different parts of the P&L: o Revenue: • Invoice line items grouped by inventory type (default) item sale prices • Normal deposit line items that are not already tied to invoices above • Other revenue or non-sales revenue from deposits • Revenue adjustments like trade-ins, bad debt, and credit card fees o COGS: • Costs of invoice line items grouped by inventory types (default) • Certain special line items with a COGS setting (corp-wide setting) • Special expense type category assigned to COGS. Expense/receipt line items. o Gross Profit: • Revenue (plus or minus any adjustments) minus COGS o Expenses: • Expense/receipt line items and the associated expense types o Net Profit: • Gross profit minus • Expenses Balance Sheet (report): - Scope: This is not a physical entity and is a report. It is a snapshot in time and shows if everything is accounted for. The word balance comes from a mathematical equation. Assets = Liabilities and Equity. This is the catch all report for your corporation. - Operations: Most users are affecting the balance sheet everyday they make and run transactions. This could be adding and subtracting inventory, selling and stocking things in, buying and paying for things, and even working for the corporation. Most users don’t see their actions as balance sheet transactions but they are. There is a cause and effect relationship with every transaction in the system. One of the biggest pieces of the adilas system is the fact that users are doing their day to day jobs and slowly feeding the balance sheet without even knowing that they are playing a key role. Enter once and let it flow if it is correct. - Accounting: Most users think of the balance sheet as the accounting side of the business. Actually, the balance sheet is just a report of where the transactions are and what is still needed to fully show what is, has, or will happen. It is a snapshot in time of where things are at. The accountant or accounting persons use this report to check and make sure things are categorized correctly and properly recorded. o Grouping o Name o In date o Declared value o Starting date o Starting amount o Ending date (not yet) o Status o Mathematical function to use: • Assigned value • Difference • Running total o Line items or subs - Buddies: connected to almost every other entity and all of their subs or different levels. This is the report that shows “Where am I?” and “Have I been recorded and counted?” Tied to: o Corps o Users o Locations o Bank o Income statement (net profit) – (other report) o User-maintained B.S. items o System-maintained B.S. items – (virtual container) o Vendors o Customers o Stock/units o General inventory (parts) o Special line items (unlimited parts) o PO’s o Expense/Receipts o Invoices o Deposits o Accounts receivables (a/r’s) – byproducts of payments made and still owed o Accounts payables (a/p’s) – byproducts of payments made and still owed o Payroll and time cards o Accrual accounts or accrued monies that are collected and passed on or are due to the corporation o Floorplans o Check requests o Taxes and collected fees User-maintained balance sheet items: - Scope: These entities only exist on the balance sheet. They are used as place holders for things that need additional information or are not automatically recorded by normal system usage. They can be set up with names, numbers, grouping, descriptions, mathematical functions, sub entries and/or transactions. They are capable of being placed on either of the three balance sheet categories (assets, liabilities, or equity). Often these items have a special or less frequent time associated with them. This could be weekly, monthly, quarterly, annually, or at random (as needed) intervals. - Operations: These are special holding spots for special actions that are taken. These items are not changed behind the scenes and require a physical action or transaction to take place. Thus the name user-maintained balance sheet items. Quite often these items have admin permissions and deal with potentially longer time periods (as compared with normal day to day activities). - Accounting: The accounting side of these items is the manual portion of the cause and effect relationship. Currently this other half of the cause and effect relationship is not fully automated. However, where we are taking it will help automate the other side of the equation. Our proposal will include e/r and deposit type watchers, system feeds, and possible standalone declarations of values and times. Currently there is a known disconnect between the cause and effect relationship. - Buddies: Most common buddies include deposits and expense/receipts. However, they may also hold hands with invoices, PO’s, other user-maintained balance sheet items, and standalone entries or declarations. Specific, yet flexible in nature. Vendor/Payees: - Scope: These could be internal or external entities. Vendor/payees are the "who" do we owe or who did we buy from? They could be individuals and/or businesses. They mostly deal with either getting inventory from them or paying them money. - Operations: All PO’s and expense/receipts must have at least one vendor. Specific stock numbers and general inventory items (parts) also have a vendor of sorts. The vendor/payee is somewhat behind the scenes but still plays an active role in looking things up in the system. Vendor/payees create associations (relationships) with other parts of the puzzle. - Accounting: One of the main functions of a vendor/payee is who do we owe for what? It is really important if payment is not made in full at the time the transaction happens. If the payment doesn’t match the total due a byproduct is created and tracked. This is called an accounts payable or A/P’s. Vendors/payees are used on checks and other forms of payment. The payment byproduct is tracked on the balance sheet as a liability (we owe someone for a product or a service). Vendors/payees are also useful when checking histories and seeing how much money went to them over time. - Buddies: Tied to: o PO’s o Parts o Invoice –tied but not shown o Quotes – tied but not shown o Expense/receipts o Check request o Payroll and time cards o Stock/units (loose tie) o Account payable (a/p’s) o Reimbursements o Recipe/builds (ingredients) o Floorplan o Time o Flex grid Customers: The word “customer” is editable inside of the system to whatever you may need. (Corp-wide setting) - Scope: These could be internal and external. Usually this is the party (individual and/or business) that receives a product and/or service. Most customers reside on the sales and quoting side of the equation. There are some exceptions to this rule and they come in to effect when they (customers) become a vendor/payee and we pay them money. Unlike a PO and expense/receipt that requires a vendor/payee, certain invoices and quotes do not require a specific customer. These are called cash tickets or counter sales. Basically, the transaction happens and is of a fast or temporary nature. This allows the products to flow out without associating who purchased or got the products and/or services. This kind of a transaction assumes full payment at the time of the transaction. - Operations: These are used on invoices, quotes, and shopping carts. They, like vendor/payees are somewhat behind the scenes but play an active role in transferring ownership of a product and/or service. Customers create an association of what was give and/or purchased. Customers are very important if the entire transaction is pending or incomplete at the time it takes place. This allows the users to look up the customer and finish the transaction at a future time. There is also an entire section that allows a user to record contacts and log entries about the relationship and how it is developing. This log portion has nothing to do with using customers as part of accounting. It is there to help tell the story. - Accounting: Accounting uses the customer to track how much has been paid and how much (if any) is still owed for the product and/or service. If the payments received do not match the amount owed, a byproduct is created and tracked. This byproduct is called accounts receivable or A/R’s. If an overpayment is created. The byproduct becomes a credit or amount owed back to the customer. - Buddies: o Shopping carts (creating a quote or a sale) o Quotes – are just declarations of projected costs and prices for a particular product and/or service. These quotes do not affect inventory and are non-committal back to the customer. o Invoices and transitional invoices. These are committal back to the customer. o Statements – are just reports to show activity on accounts and money both paid and still outstanding. Basically dead end snapshots in time to help with getting funds due. o User-maintained customer logs. These are notes about the customer relationship and may include follow-up actions and date. o Time and elements of time o Time-based billing Stock/Units – Serialized inventory items: - Scope: These are your bigger ticket items and are usually inventory items that are tracked by themselves (on a one by one basis). These are generally serialized inventory items and may have a need to carry additional baggage (outside repairs, internal tickets, adjustments, shopping and miscellaneous, etc.) Some of these items carry a thing called phantom cost such as pac, interest, slush fund monies, system fees, etc. There is a perceived a value and an actual physical value. These are inventory items. The little brother of the stock/unit is the parts and general inventory section. These are grouped or smaller (mass quantity) items. - Operations: The operations side will stock these items in, fix and update descriptions and details, apply additional parts and pieces to the units, and eventually show and try to sell the items. Salespersons consider these items as their inventory. - Accounting: As an item is entered, it automatically creates a payable (who do I owe for this?). As the users assign outside repairs and internal tickets (grabbing parts and labor and applying it to the unit) to the stock/unit, its value will increase accordingly. Once it is sold, it allows pieces of its baggage to flow over to the income statement and balance sheet. A sale will lower inventory levels, give revenue and cost of goods sold, it may also include other pieces like sales tax, special collected fees, assigned processing fees, trade-in (new inventory and revenue adjustments), and possible Lien payoffs on trades. These are only some of the values that flow over to the P&L and balance sheet. Fairly in depth inventory items. - Buddies: Tied to: o Vendors o Inventory (current and sold) o Accounts payable o Locations o Income statement (P&L) once sold o Balance sheet as inventory, payables, taxes, and collected fees o Possible floorplan actions o Expense/receipts either as payment for units or as outside repairs o Customers once sold o Parts and general inventory if added as an internal ticket o Quotes o Invoices o Deposit line items – coming from invoices o Taxes o Collected fees o Fees o Trade-ins & Lien payoffs o Payroll commissions Parts & general inventory: (The words “part” & “part number” are editable inside the system to whatever you may need. - Scope: Theses are physical and/or virtual containers, parts, items, products, services, etc. A “part” is anything that is tracked as a group and/or may be bought or sold. Parts are vendors specific (even if using a generic item) and are used on PO’s, quotes, and invoices. Depending on your corporation, a part number may be a physical quantifiable (countable) item that is on a shelf or in a box. Other corporations sell services or intangible objects. Both are considered “parts’. This is what we call your general inventory. The big brother to the parts department is called the stock number section or stock/units. These are bigger ticket items or serialized units. - Operations: Parts are created by bringing them in on a PO (purchase order). Once they are created, they can be searched, looked-up, referenced, re-used, counted, quoted, and sold. This process is usually somewhat cyclical and depends on the business. In general, the PO holds the quantity and cost coming in and the invoice holds the quantity, cost, and price going out. When you add up the ins and outs, you get an inventory count. If the item is setup as a service or virtual container, the quantity is set to unlimited and you are able to sell without ever replacing (PO actions). Each part number can have barcodes, descriptions, costs, and prices. Without getting to technical, the actual part number is just a container and space holder that can be used to get (PO) items or sell (invoice) items. The PO’s and invoices do the work. The part number is just the reference or piece that allows the flow to happen. - Accounting: As items are brought in through PO line items two things happen. One, inventory is created (assuming a positive in quantity). Two, a payable is created (how are you going to pay for these items?) As items are sold a number of other effects show up. One, the inventory count goes down (assuming a positive out quantity – this is normal). Two, we now have revenue (sales price or extended price) that goes to the income statement or P&L. Three, we also have the cost or extended cost of the items. This is sent to the COGS (cost of goods sold) section of the P&L. Four, we now have potential taxes that have been collected. To recap, items coming in create inventory and payables. Items going out create inventory deductions, revenue, c=COGS, and taxes that are collected. - Buddies: Tied to: o Vendors o PO line items o Inventory (in & out) o Quote line items o Invoice line items o Taxes o Recipes/build ingredients o Locations (inventory) o Income statement P&L o Balance sheet o Sales and profit reports o Payroll commissions Special line items: (Unlimited hard-coded special part number or items) - Scope: The term “Special Line Items” is used to describe hardcoded part numbers that are automatically added and controlled by the system. Each one has an unlimited quantity and is un-editable to system users. The adilas application has special code and functions for these items. There are some advanced settings inside the corp-wide settings page to control hide/show values, tax categories, payroll, and financial roll call properties. These special line items are the 3rd inventory type allowed on PO’s, quotes, and invoices. The other two types are stock/units (serialized units) and parts and general inventory. Some of the special line items are: Collected, Dealer Handling, Fee, Discount, Freight, Labor, Lien Payoff, Other, Rental, Shipping, Shop Supplies, Sublet, Supplies, Trade-In, Unit, Verbage/Info, and Warranty. F & I. - Operations: In general, theses special line items may be used on any page or section that allows a part number to be used. This includes PO line items, recipe/build ingredients, shopping cart line items, quote line items, and invoice line items. Using special line items can save time and allows special pre-built system functionality to take place. Each corporation is different and has specific tasks and goals for their system usage. Because each special line item is so different, maybe a special section to explain each item what it can and should do. Also, what special code is included if used as stated. This might be more effective than examples or general statements. (See farther on for some of the details…) - Accounting: In general, these special line items have a $0 cost (may be changed if needed on a one-by-one basis.) They can however hold a quantity, price or revenue value. The system treats special line items on a different level. Special line items may be taxed or non-taxed items. Special line items may be included or excluded in payroll commissions and reports. Certain special line items have a closed or limited scope and only properly track through the system if used as states. For instance certain special line items never hit the P&L and only play on the balance sheet. Another use for special line items is purposely use them to get a job done (on the operations side) and creating somewhat of a flag or disconnect (known problem or issue) that will require additional help or action later. Please see the special usage for each line items for more details. - Buddies: Tied to: o Internal system vendors o PO line items o Not eve tied to inventory (by default) o Quote line items o Invoice line items o Taxes o Collected fees o Other fees o Recipe/build ingredients o Income statement – P&L o Balance sheet o Sales and profit reports o Payroll commissions - Note: May need to add “Gift Certificate” to the list. - Also: It might be nice to go deeper and explain special code for each special line item. This might help with the overall picture of what is happening and what is going on behind the scenes? Small subset to talk about specific roles of the “Special Line Items: or hard coded system parts: - Item Name: Details & Information (format) - Collected: o The “Collected” part number is designed for use with monies, fees, or special taxes that are collected by the corporation for some other entity. Basically, you collect it and then pass it on to some other government entity or business. They may or may not give you any compensation for collecting the stated values. The “Collected” special line item will not show up on the income statement, it has no payroll settings, and may be taxed if needed. You can also hide/show the value through the corp-wide settings, if your corporation doesn’t use it. This part number is one of four special parts that can be prebuilt and defined to go on any stock/unit sale. See the add/edit location page for details. If you would like help showing this item on the balance sheet as a feeder, click here for information and examples (link to another page with info). - Dealer Handling Fee: o The “Dealer Handling Fee” par number is designed for use is selling stock/units. This special line item is one of the four special items that may be pre-built and defined for the stock/unit sales process. See the add/edit location page for details. Other corp-wide settings include: show/hide, tax settings, payroll settings, and roll call handling. The default roll call is to the revenue portion of the income statement. - Discount: o The “Discount: part number is primarily used on invoices and quotes. Most often the value is negative indicting a reduction in price or value. There are a number of pre-built pages that allow quick discounts to be calculated and applied from the shopping cart mode. Calculations include dollars off or by a calculated percentage. Discounts are not part of payroll and have a roll call of revenue. You are allowed to hide/show and change the tax category in the corp-wide settings. - Fee: o The “Fee” part number may be used for any fee that is applied to invoices and quotes. Fees are usually associated with revenue. If you are collecting a fee for another entity or government agency. We recommend that you use the special part number “Collected” instead of “Fee”. Use the “Fee” part number for things you get to keep. This part number is also one of the four special parts that may be pre-built and defined for stock/unit sales. See the add/edit location page for more details. All of the corp-wide settings are available for this part number (show/hide, tax category, payroll, and roll call handling). - Freight: o The “Freight” part number may be used on incoming PO’s and outgoing quotes and invoices. No special code is in place for this special line item. All of the corp-wide settings are available for this part number (show/hide, tax category, payroll, and roll-call handling.) Note: If used on incoming PO as a special line item, we recommend that you break it out into a separate line item when paying for the PO... - Labor: o The “Labor” part number is a great generic place holder for any type of labor. Even though there is no hard coded special code for labor, the system does treat this part number as special. There are a number of special reports that just deal with this special line item. By default it has its own payroll setting. There is also an option for paying a special labor commission if needed. See the department to user pages for details. Labor is generally not taxed, but may be taxed if needed. All other corp-wide settings apply (show/hide, tax category, payroll, and roll call handling). - Post-it Notes: Potential problem on the sales tax report page dealing with what part #’s to include and exclude in the parts section. This deals with special line items like “Other” and “Discount”, etc. Currently a “Lien Payoff” does not create a new payable automatically. - Lien Payoff: o The “Lien Payoff” part number is usually a subset of the “Trade-In” special line item. If lien is when monies are owed on a unit or item and this amount must be paid off in order to get a clear title or right to resale the item. Adilas allows a lien payoff to be shown and recorded on a stock/unit sale but technically a lien is a type of payable. Currently, the part number does not automatically create a new payable. This function is a user-maintained function. The part number “Lien Payoff” will not show up on the P&L and has no payroll settings. It can be shown or hidden and set to any tax category from the corp-wide settings. - Other: o Part number “Other”! You may actually hear or end up using this exact phrase. Part number other is one of the most flexible special line items or part numbers. It is considered by some as a blessing and a curse depending on how you use it. On the positive side, you can use it as a place holder for anything in the system. It allows you to quote products and services that you don’t have and sell and you can virtually sell anything that you run across using this part number. It is a great tool for sales or people who deal with customer and clients because it helps you get your quotes and invoices out the door very quickly (even if there are some unknowns or questions). On the other side of the fence, however (cause & effect), you are dumping transactions into a must fix later or more research is required to make it right container. One of the biggest problems is that no cost of goods sold is recorded. This is a key part of gross profit on the P&L and eventually flows clear to the balance sheet. Another possible problem is that if you sell something using part number “Other” the real item may stay in your inventory count, causing overstating of your inventory counts and values, which can also affect the balance sheet. You basically just doubled the problems by trying to be fast or just being lazy. Once again, part number “Other” is both a blessing and a curse. Use it is you need too but just be aware that you might be creating more work for somebody else. This part number, by default has a P&L roll call handling of “Unassigned (black hole)”. This doesn’t mean that it disappears, but it does mean that it gets put into a special container that has an unwritten name of “help me fix this transaction.” If the price is set to $0, the roll call of black hole is great and won’t cause any problems. Once you start assigning monies or values to this part number you may want to consider a roll call handling of revenue instead of black hole. Part number “Other” is not taxed by default but may be taxed if needed. All of the corp-wide settings may be applied to this special line item (show/hide, tax, category, payroll settings, and roll call handling). - Rental: - Post-it Note: Special line items that can be pre-set for stock/unit sales: Dealer Handling Fee, Shipping, Collected, Fee/ Trade-In & Lien Payoff from quote to cart

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

	AU 3565		2011	1/1/2011	YEARLY ACCOMPLISHMENTS 2011 Steve, This is a list of things that happened and accomplishments made during the 2011 year on adilas. It was a great year with tons of new and awesome stuff. More and more still to come… If you need additional details, just let me know. I have everything documented down to the date. January 2011: • New tax tables for 2011 (federal & state). • PCI Compliance Renewal. • Added Authorize.net as a new merchant gateway (merchant processing). • Added the running daily bank balance (per transaction) to the check register. • Added a part number “group” option to the invoice line items search page. Added a switch between groups and details. • Created a similar group and detail toggle switch for PO line items (incoming parts and quantities). • Made a conscience switch to get out of the retail hardware side of business (card readers, receipt printers, barcode scanners, etc.) and focus more on the reoccurring services that we provide. • Added an alpha name search to the quick search options for invoices, quotes, expense/receipts, PO’s, and checks. This allows a search for all results for a given customer name or vendor/payee right from the quick search. • Moved the force payment checkbox on the verify PO page to one step deeper. • Added more links and flow to help with looking up vendor/payees and their current payables. • New corp-wide settings for show/hide tax categories on invoices and quote and a default credit card transaction mode for the merchant processing page (retail swiped, manual keyed, or both). • Created the accomplishments lists for 2009 & 2010. Posted scans online to the adilas history balance sheet item (special archive photo gallery). • Added dynamic drop-down options to the flex grid tie-in titles and custom field names. February 2011: • Started working on the adilas “any” scheduler. This name was later changed to “Elements of Time”. • Tons of notes, ideas, research, concepting, and brainstorming on elements of time. • Went around (onsite) to 10 different businesses to get ideas about how they deal with, tracked, and used time. Filled out prepared questionnaire to gather data. Compiled data into notes and ideas for elements of time. • Added quick search options for main id numbers, included parts, customers, and vendor/payees. • Worked on graphic mock-up for the interactive map and the multimedia training application (player). These are future concepts for adilas university and the main adilas.biz interactive navigation interface. • Added an auto calculate switch (checkbox) to the advanced add to cart page. That allowed us to do more than one calculation at a time before the local math was done. This allowed for things like: unknown weights (quantity), sealed items (USB digital scales), backing in to a fixed total price, and using a tax category of “with tax included”. With the new switch, all of these calculations could be done at once instead of one calculation at a time. • Added options to pass pre-set values from my cart favorite buttons to the advanced add to cart page (options 5 under use exact part number button type). • Created three different bio’s or history documents about adilas. They are the business bi, the education bio, and the brief history of adilas.biz. • Elements of time began to split in to two different sub types. They were types of time (ended up being master time templates) and functions of time (ended up being subs or add-ons of time). March 2011: • Added the CHARGE Anywhere gateway (merchant processing). • Changed the main adilas.biz homepage. Added a search by date field and changed the stats to “daily” stats as compared to the overall “total” stats. • Working on basic database design and layout for elements of time. • Added corp-wide setting and permissions for cross-corp billing. • Added three new fields to the customer statements. They are for the invoice age, the paid status, and the payment types. • Ordered a new content server. • Created a custom CSV file for Dealer Car Search. The export builds itself and sends itself every day at a given time. Includes stock number details, descriptions, prices, and available photos of the stock/units. • Added my cart favorite “group” buttons and a thing we called the advanced grid or add multi grid. Basically a grid that has advanced add to cart features for multiple products at one time. The groups allowed for stacking (depth) of standard my cart favorite buttons. April 2011: • Working on elements of time. Added tons of new pages. Pages included add/edit master time templates, add/edit basic elements of time, basic time search, the working with time page (generic edit mode), printable time page, and time history page. • Decided that each corporation should have their own PO and invoice line items table. Major rework on logic and flow. Split the main table in to corp-specific mini tables. This change affected close to 100 different pages. • Created a multi-corp – multi-location – daily/weekly sales report. Able to pull data by corp, by location, by date, by part category all at one time. One of the first cross-corp reports to come out of adilas. May 2011: • Added the advanced time search (build your own report interface for time) and the advanced results pages. • Added ability to assign time to specific customers, employees, vendors, and locations. Also allowed options to assign to generic persons or places (any – even if not in the system). • Created a bid and proposal for the State of Colorado for the MMJ industry tracking program. • Started working on the sub functions or add-ons of time. They were the action status logs, sub dates and times, and sub comments and notes. • Added a “view only” options (permission) for the my cart favorite buttons. This allowed for one user to set the buttons and then others (maybe not as technical savvy) to use their buttons as their own. This also allowed for a virtual master list of buttons for a single corporation. June 2011: • Constant tweaks to the elements of time section. New settings, new defaults, and new options. • Added a description option to the barcode generator application. Able to switch between a barcode value or a description value (text). • Added a contact (email) adilas support page from any of the application help files. • Kiva and Steve came up with some “short cuts to adilas”. A PDF document for users to get started. • Launched the first round of the interactive map concept. The concept was still a graphic (not yet interactive) but did have a number of links overlaid on the graphic to help with temporary navigation options. • Added a sneak peek graphic to the main switchboard page. The underlying page listed current and upcoming projects that are planned and scheduled. Kind of a small insight to where we are headed or a view of the master plan. • Documented all of the “quick search” options, values, and keyword searches. Put all documentation into its own help files. Added links from different pages to the help file with the documentation. • Added elements of time and reoccurring invoices (reminders) to the main history homepage report. • Added the customer type to the shopping cart. • Increased the number of custom fields on the flex grid tie-ins. Went from 10 custom fields to 15. • Added two new major players to the flex grid tie-ins. They were elements of time and quotes. This brought the total main application types to 12. The flex grid is now a 12 x 12 x 15 matrix as compared with the old 10 x 10 x 10 matrix. • Reworked the flex grid tie-in search results. Made it more human readable to the end user. The old way only had the main application type initials and an id number (example: cust 10001). The new way still shows all of the info but also has a human readable column next to the id number of the tie-in info (example: cust 10001 – Fred Flinstone). July 2011: • Added the flex grid tie-in info to the add/edit customer page. Before it was only shown on the customer log page. • Added a custom shipping CSV file. Custom document tied on a per invoice basis and assigned through the custom document management system. • Kiva took over the reoccurring invoices, credit card payments, and adilas billing functions. • Added a “refine your search” option for elements of time (advanced time search and results). • Added a “grouped” elements of time to customer report to help with billing and assigned times and invoice/quote status values. • Added options to convert one or more elements of time to the shopping cart. This is part of the customer billing options. • Added new corp-wide settings for the customer tax id name, the location license number, and the printable disclaimer text (unlimited text length for invoices and quotes). • Converted all normal customer logs (notes and follow-up notes) to HTML compatible. This allows for things like line breaks, links, and other formatting. • Added an option to search the customer tax id (dynamic name) from the customer quick search. Many of our clients are using a barcode scanner or card reader to search for their customers. August 2011: • Finished up the time to cart process (customer billing). Pretty in depth processing and lots of cross tying between time, quotes, and invoices. All the users have to do is point and click. • Added a couple of MMED forms for the State of Colorado. We added one for the monthly primary center patient list (form 1010) and one for the daily patient sales report (form 1100). • Added an IP address field to the user login/logout actions. This helps a manager know where the users are logging in/out from. September 2011: • Created a generic customer export to Microsoft Excel that included basic customer info plus any flex grid tie-in fields. • Added subs of time to the time to cart process. Other tweaks to help the flow between time and invoices and quotes. • Added an IP address field to the employee clock in/out (timecard) application. Timecards are tied to payroll, so, this helps managers know where the clock in/outs took place. • Created advanced search options for subs of time (add-on functions of time). They include searches for action status logs, sub dates and times, and sub comments and notes. • Added the MAXX payment gateway (merchant processing). • Steve went to a big Trailer Dealer Convention in Texas. Came back with a number of leads and new ideas. • Added a temporary patch for sales tax on the balance sheet. • Added a customer type filter to the my cart favorite buttons. Not required but filters buttons once a customer is assigned to the shopping cart. Helps with different pricing for members vs. non-members. • Major work on visual reports for elements of time. The main time homepage is capable of showing a calendar view (up to 365 days at a time), a dynamic time slot view (daily detail view with any increment of time and a start/stop range), a grouped report, and the normal time details (organized list) reports. • Publicly released elements of time. Round one of three (other future releases will come later on). October 2011: • Added a new quick search option right from the top of the view cart page. This allows for parts searches and barcode scans right from the view cart page. • Added four new customer date fields (main start, main end, period start, and period end). Each new field also has a corp-wide setting attached to help with custom naming options. The period end date has special code to help watch for passed or expired values (shows up in red). • Added a number of new corp-wide settings for elements of time. This deals primarily with what the user sees when they first come to the time homepage. Default settings include things like: time period (date range to show), report type, calendar block size, time slot start/stop range, time slot block size, and show/hide extra stats and subs. • Added a basic export to Microsoft Excel for invoice sales data. • Added a new customer queue application to help track “who is next” for customers and waiting rooms. Virtually a check in/out monitoring process. • Updated the custom document settings for the Texas 130-U (new version). Also added a data only version to help with the facto form printing for title applications. • Added options to change prices and button status on the bulk sort page for my cart favorites. November 2011: • Small tweak on the balance sheet. Showed the difference between the total tax and the possible out of balance value. • Added the user history report (historical history) to the main history homepage. Includes 20+ system-maintained user history sections (actions recorded behind the scenes for system events). • Added a better “change due” call out on the mini 3” invoice format. • Added a new permission called “my history” and connected it to a filtered portion of the main user history report. • Created a new “grouped” customer invoice report. Ability to sort by customer, invoice count, and total invoice sales (sums). • Expanded export options (to excel) for invoices (total of 5 different reports). Added a “refine your search” options to all advanced searches for invoices. December 2011: • Added links to the barcode generator to and from stock/units and for customers. • New customer exports to MS Excel. Including the advanced (build your own report) search, customer logs, and additional contacts. Tied to all exports to the advanced permission for customers. • Added a “refine your search” option to the advanced customer search results. Added an export to Excel for part numbers and quantities. Also tied this export to the advanced permission for parts. • Added a new permission to help with quick retail sales (counter sales or non-customer tickets). Also sped up the customer to cart assignments. • Added an options to hide the main cart info for non-customer counter sales in the view cart page. • Added a new corp-wide setting to use or skip the review cart page (final step in the cart process before converting the cart to an invoice). • Updated all tax tables for the tax year of 2012. • Small change to the balance sheet homepage. Pre-selected the checkboxes for show assets, liabilities, and equity sections. Yee Haw! More to come in 2012!

	AU 3630		No Dates: Buying & Selling - Invoices, Shopping Carts, Parts, PO's, Stock/Units	1/1/2011	Scan 54 & 55 – Invoices – Payments – Deposit Line Items Invoices – Payments – Deposit Line Items Known Issues: 1. Need a received checkbox on each payment 2. Need a date received on each payment 3. Need to know what deposit the payment was on a. Old data may not have link to payment and/or invoice 4. Deposits are very loose right now a. Still need ability to be loose b. Need to tighten up sales or field deposits c. Must require an invoice or payment to deposit 5. On invoices – link back to deposits and show flag if payments have been deposited 6. Receivables will be run off of payments not yet received and invoice not masked “all monies”. This is a double check in ways. 7. What about invoice that are marked “all monies” but don’t have all the payment, mismatch on numbers, or still has outstanding payment. Maybe a special search or flag. 8. Along the way (A/R path) need to record progress – invoice, deposited, verified, posted. 9. Need to deal with other possible deposits such as: a. Deposit or special order; Deposit on existing inventory, Refunds (taxes, purchases, inventory), credit (discounts or pay early), shareholders, loans, donations, sales (assets, inventory, services) 10. What about different deposits. Say you get $25 for an invoice but then bought something out of petty cash for more than you had and had to borrow from the cash drawer? 11. Do we need to track by invoice and deposit or payment id and deposit line item id? Both – main numbers for humans and id numbers for computers. 12. Add customer’s name on deposit line items. Scan 61 & 62 – Invoices, Shopping Carts, PO’s Invoices, Shopping Carts, PO’s: - Go to page automatically - Java script jump menus - Skip the “go” button - Special – limited o Corp-wide setting for invoice limited format - Edit invoice line items & PO line items o Not updating the main corp-wide setting - Back Orders – Dup Invoice o Auto – see split invoice – also PO’s - Sigs – per packing slip or amt invoice o Corp-wide o Quotes o Normal invoice o Limited format o Mini version - Ability to price multi items by customers purchases (last) o Maybe have a custom pricing permission o Ended up doing the advanced add to cart o This could also open up the price field on parts homepage item (1-many from parts to customers) and view parts pages. Also advanced search results page. o Corp-wide setting o Open price field before adding line - Left & Right on remove – shopping cart vs. invoices – may need to standardize - External PO #: do you need a PO # on your invoices o Make it very visible and part of the flow o Customer PO’s on invoice o Standing out – corp-wide setting o Pull it out in the middle o Have a corp-wide setting for the verbage of what to call it. Have another one to hide/show the option o Needs to go to quotes as well - PO’s need 4 dates o Start o Ordered (optional) o Ship o Received o Bill or pay (due date) - Corp-wide setting for show/hide on tax category on printable invoices - Corp-wide setting – special notes per line item on invoices and PO’s o Similar to a line item and a new line item for verbage - Surgery on an invoice – be able to split invoice o Invoice quick edit or invoice master edit o “invoice” based Shopping Cart o Old qty o New qty o Original – new back order or split o Next or forward o Corp-wide setting - On 1-many between parts and customer and parts and vendors o Select cust o Show everything that tied to cust o Sort by most activity o Show (might need to adjust layout and fields) • Qty on hand • Our part • Their part • Qty to add • Current price • Last price (non-editable) • Cost (non-editable) • Contract price • Profit per line that gets figured on the fly o If customer is set in cart, check for 1-many to parts. If yes, show special link to all items - Maybe add a permission that allows open adding to carts, quotes, and invoices. This would open up fields like price, qty, description, and tax category all at once. Advanced add to cart. - Ordered, promised, and qty on hand. Quick report – what do I have where? Scan 70 – Outstanding PO’s Outstanding PO’s – grab current and past ones - Select – sum po amt - From PO’s - Where core = o PO paid = 0 o PO date <= use date o Grab list o See if any payments have been made o Grab a list of PO’s to exclude o See if any other PO’s have been paid on after the use date that aren’t in the exclude list. Scan 71 – Stock/Units Stock/Units: - 1 = vin - 2 = stock year - 3 = make name - 4 = sub inventory type - 5 = model - 6 = miles - 14 = title and registration o Cust address o Cust city, state, zip o Cust county - 15 = owners name o Owner’s address o Owner’s city, state, zip - 15a = gda - 18 = seller name o Miles 2 - 20 = trade year o Trade make o Trade vin o Additional trades (yes/no) - 21 = sale price o Less trade o Fair market o Taxable amount o Tax o Late tax o State tax o Amount of tax due - 21g = tax paid to state - 22 = salesperson name o Salesperson date - 23 = customer name o Customer date Pre-check semi Trailer type semi Scan 87 – Invoices Invoices with all info – sale, price, etc. Parts – we already what we are selling, we may or may not have that item assigned to our store. Customer gives us a down payment in order to complete the invoice we have to have it in inventory. This POS’s a problem – (ops, arc) Incoming money: - Deposit on – special order - Deposit on existing “inventory” - Refunds – Taxes, amounts, purchased, inventory returned - Credit – on accounts we pay early or for doing so – like sales tax - Shareholder – investments - Loans – from banks - Donations – if your non-profit or sponsorship - Sales – Assets or lnv or Services Who I am? Where I am? What I want? – Great way to think about it. Scan 91 – Invoices Invoice – Salida (create) - Invoice - A/R – can do deposit from this page - Deposit Home - Payroll Scan 106 – Buying & Selling Processes Selling/Offering: - Product or service - Quote - Invoice o Revenue Statement o Contract to sell - Payment received o Mini loop that may occur - Deposit - Posted (done) Buying/Wanting: - Product or Service - Expense Quote Thing o “order” – Expense Request – (contract to buy on pay) • PO • Payroll • Inventory • Bill/statement • Reoccurring • Reimbursement - Receipt - Payments Made o Mini loop that may occur - Withdrawal - Posted (done) Scan 134 – -New permission for consulting “monitor quantities” on parts -Add a saleprice option for trailers and toppers. Also add description counters Reverse mark-up options – they got to enter what they want or make • Mark-up vs. • Profit percentage -Maybe make this a corp-wide permission and educate them on the difference between the two – maybe some java script to help with calcs and reverse calcs. -Parts begin homozanus like milk, water, steel, wood, bolts, pile of things -Quantitative ye non vendor specific – bulk, generic, pile, general, transparent, group, school, pack, case, lot, special -Non-vendor specific PO’s: -Special PO – special selected, vendors, mixed vendors, bulk or grouped items -On the search for general PO’s – make them choose a vendor and then display matching parts. Scan 135 – Questions & Answers Questions & Answers Continued: 3. Continued - Send a price & availability Quote - Send part # & description. o This may be a generic “here is what I want” request o You may or may not want the vendor part numbers on it - Get quotes back from vendors - Compare numbers and create multi PO’s if necessary (different vendors) o This includes comparing locations of where the products are - Gather in the products o This could be pick-up o Wait for shipping o Whatever - (Morning meeting – communicate what needs to be done) - Sales of the day (what is needed – date range) o Order # o Quick list o Qty ordered (their order) o Qty on hand o Qty on order (our incoming order qty) Scan 136 – Parts Your Part: Ref Num: Vendor: Main PO: - Line Items o Parts Notes: - Start an invoice from a specific customer - Multi-decimal - PDF or PO’s - Hide line items on PO’s - Sort line item on invoice & PO’s - Order – Request PO - Multi-part ref. chart - Add a part reference – special line item part - Corp Settings for special line items - Own little world on special line items – this includes show/hide and the ability to add custom unlimited parts Scan 139 – Drop downs – st verbage for 30, 60, etc. Lookout – late fees Searchable “invoice” field to see who we need to print and mail invoice – currently have to type text into name field. Email options – flex grid: - Occupancy date - Vacate date – able to enter advance date Edit statement to fit in envelope. Why printable, printer friendly, then print (3 clicks to get an invoice) – multipoint Last payment made date (not date of invoice it was applied to) Recurring & frequency fields (searchable) Balance due Have following fields that we can select from customer list (or somewhere). Need to see entire customer list – which would allow us to check everyone that has a unit without having to go into different parts of the system, figure out if missing someone because they prepay or pay quarterly etc. Would also allow us to catch anyone that doesn’t have billing set, vacated, etc. Recurring or invoice Customer – be able to select phone, email etc. to show Customer status Last Invoice Date Last date invoice, last payment made Balance due Occupancy date Vacate date Follow up date? /Log Above with searchable timeframes, eg Anyone with only current – less than 30 days 30+ days 60+ days Ability to invoice and/or create statement Is there a way to attach that to email. Currently if hit email in customer contact info, it does open email to that customer, but how to attach invoice/statement without saving as a pdf first. Discount applied? On going 3 mo – get 4th for whatever time frame expires Poss – set up each unit as an inventory item – tie to customer? Scan 140 – Units, Customers Units, Customer (Sketches – Please see scan in photo gallery) Scan 151 – Recipe/Builds Recipe/Builds: - 1 = dummy - 2 = build & sell - 3 = build & hold - 4 = build & build PO Types: - 1 = dummy - 2 = basic live - 3 = update - 4 = internal build - 5 = basic request - 6 = special request - 7 = special live Deposit Line Items – - Also check the remove line item code - Check the void code - Line in_out o 1 = neg or ingredient o 0 = output or final product Rework on recipes & builds: - Add in extra verbage to show what is what PO side, invoice side, mini manufacturing, just in time manufacturing - Be able to pass a valid PO number to and through the page flow, even during editing and building - Make sure that costs flow through correctly and may be added to the outcome value correctly - What about total costs, profits, and prices? - Make sure that the duplicator or multiplier field works - What about adding an item (part number) during the process - A PO must be started first, then checked for a valid build PO (PO type id = 4) - What about hidden line items on build and hold PO’s and recipes? - Be able to duplicate a PO including switching locations and PO types. - On the build prep – check for and output value - Is it too strict… just internal builds and only if an output value is used or should we open it up…??? Scan 156 – Advanced Add to Cart Advanced Add to Cart: - Price helper – price helper - Tax category – tax 1 (tax category id) edit page – hidden - Quantity – qty 1 (line quantity) edit page - Cost per – cost 1 & cost helper - Mark up – markup value & markup helper - Price per – price 1 (item price – edit page) & price 1 helper - Use Special Total – price total & price total helper o User price total 1 (Unknown price per) & use price total 1 helper o Use price total 2 (Unknown quantity) & use price total 2 helper - Discount – apply discount – apply discount type o Index 0 = value 1 = % o Index 1 = value 2 = $ off o Discount helper - When the check boxes are used… clean all fields and store the used and checked values in the helper set the focus to the discount field Scan 158 – Printable Items List To do: Add the customer type on the queue page Printable Items List: - FORM main sort by – sort - FORM quantity filter - FORM quantity filter match – quantity filter o 0 = exact o 1 = greater than > o 2 = less than < o 3 = not equal to <> o Check the show on web settings

	AU 365		Daily Ideas	1/11/2011	-Turn the adilas interactive map into the main multimedia player. Allow the left and right hand sides to be controlled. Add a little bit on the bottom and slide the left hand side over a bit. Make it 750 x 450 with a frame set below the main player. -On the player – be able to choose options like video, slide show, h-scroll, v-scroll (maybe spell them out), audio, web link, animation, step-by-step. Each section or sub-section could have their own button options. You could also call for a button on the fly though a function. -On the top left have a home/reset button that allows the application to be reset. This can be controlled through the URL string and stored in a database. Basically, I want the player to be as generic and flexible as possible. -Make all of the buttons show/hide by calling functions. This will help the player be able to respond to any event or need. Make sure and publish the functions and even provide code for flash developers. Make it easy. What do people need? - A way to organize their data - Be able to retrieve their data - Be able to store and archive data - Data could be anything: numbers, dates, text, time codes, serial numbers, inventory, recipes, events, photos, documents, pdf’s, paperwork, movies, slides, video, animation, charts, lists, etc. - Be able to track things - Be able to sell things - Be able to show things - I need something custom that is easy and fits my needs - All in one place…. - ADILAS – All Data Is Live And Searchable -I’m asked to do similar things over and over again. Can you build me an application that does this? This? Or this? How much will it cost and how long will it take? - What do people need?

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

	AU 397		Daily Ideas	2/9/2011	On post-it note in notebook: • Financial history look-up • User history look-up by payee id and location • Full site map of the adilas.biz system. My Quick links • Email sales and support page. • Beef up flex grid searches and dynamic drop-down titles and options. • Payroll feeders on balance sheet items. • Time conditional logic – only date, no time, just a single day (choices). • Might sound weird – no dates – but able to show up for roll call – on specific numeric days (not dates). Like accrued payroll… • Standalone declarations From mini-notebook: • Add a flag to help people know if a transaction is system maintained or user maintained. • Make the system return and report. • “Teach them correct principles and let them govern themselves.” –Joseph Smith • Help the people catch the vision – this will drive them. • Everybody is playing on the same team - bring things together. • A solid base supports the whole. -Need pagination on sales tax report. -Ease the load on the server. Reports are either too big or take too long to run. I want it to run as smooth as possible. -Maybe add a flag per line item for possible tax problems. This would help the accounting staff find the possible problems quicker. -Once we start in to Flash – I can see navigation, sub modules, shopping carts, schedulers, training, etc. starting to play in the same base player. It might be cool if there were options for classic html and interactive or flash.

	AU 2184		Brainstorming Types & Functions of Time - Elements of Time	2/15/2011	Simplify – Types and Functions of Time 1. There are 50 to 100 known types of time. Many are very similar, only what you call it needs to change. Almost like groups or families. Like values. 2. There are 50 to 100 known functions (needs) for time elements to play with. 3. Most people want things that are pre-set and ready to function out of the box. Other people want to be able to customize things. 4. If things are too hard to do, set-up, or maintain… you lost functionality because people are inherently lazy. K.I.S.S. 5. What is a standard? How do I play to that? 6. It needs to be as simple as possible. 7. What if we created basic templates (types and functions) and then allowed the user to apply a template to each time element. 8. What if every element of time was as simple as an id number, a corp, and a template id number. All other pieces would be subs according to the template (directions and requirements). At least one sub would be required but the element could have more than one. 9. What if the types were something like: personal (my), person(s), place(s), thing(s), combination, custom. 10. What if the functions were something like: date only, date/time, …. Infinity 11. Why am I scared to commit… I see that it is big; I see that people want to be able to call it this and that. I want to tie it all together, and part of me wants to keep it all under the same roof “elements of time”. 12. Is my pride getting in the way? Even this page… am I getting too worried about what people will think (later on)? What is the hang-up? 13. I’m feeling a lot of stress… I have needs to finish up balance sheet, do a training application, build the scheduler, map out the entire system, build new reports, etc. 14. What happened? I’ve always had tons to do… why the huge swarm of things in the last couple of months? Why am I so limited? Everything feels big… Everything feels complicated… It seems like everything is so interconnected… I know that is good and bad… 15. I’m thinking that the process needs to go like this… scheduling, balance sheet, and training. I would love to put training first but I also know that some major changes are coming down the pipeline. 16. Things are changing so fast… It is hard for me to keep up with things. I can’t imagine being a user and trying to deal with all of the changes. 17. Maybe keep making the changes and then go back and start training people how to do it properly. (Once changes have been made) 18. Apply what you learn along the way. The more you do the more it sticks and becomes a part of you. 19. Who is counting time anyway… I’m not trying to break some record or something. I am trying to make progress and I’m okay with a step at a time. Only run as fast as you are able. From a gridded outline for brainstorming “elements of time”; Needs – rows – 1,2,3… & Types of Time – columns – A, B, C… NEEDS - rows 1. Basics, quick name or title, corp, id, template, creator id, sub type 2. Date (day only, single, multi, range, reoccurring) 3. Category & sub category sort 4. Time (time only, n/a, single, multi, range, special rounded, reoccurring) 5. Total time 6. Notes & credits (real, practice, draft, concept – 255 or big) 7. Payroll 8. Privacy, show/hide, web, visible, permissions 9. Assignment(s) & changes (one or many), change log 10. Reminder(s) & notification(s) - sending messages and pushing reminders to main homepage 11. Photos & media – subs, choices, ftp, decisions, stitching, content… video, stills, graphs, maps, audio, html, pdf, word, etc. 12. Comments 13. Invoice tie-ins – details or summed up (invoice types), (invoiced, not invoiced, no charge), recipe tie-in (one to many) 14. Quick tie-ins (build or pull from multi chain as needed) 15. Financial & general amount – standalone declarations, able to add back up to the main (revenue, costs, value) 16. Sign-offs & by who? – maybe a 1-many (review, outside players – sharing) 17. Rate tables & look-ups – seasonal, promotion, sales 18. Expiration dates &/or show until dates – due or target dates 19. Booked vs. actual usage, planned vs. reality 20. GPS subs 21. Sub pool(s) – what kind in/out of play 22. Reoccurring (master/share, template, blocks, average unit, standards, slot, values) 23. Flex fields (names & types) 24. Tie-ins (flex grid, what else) what about tying together subs and media, sewing, stitching, links, groups 25. Customer (1 or many) look back, relationships to other tie-ins, roll call, participants, general or generic 26. Vendor/payee (1 or many) 27. Histories & usage logs – start, stop, # of times 28. Sub times or sub time frames – due dates, aging & queues (relationships) 29. Follow-up & details –progress reports 30. Finished/starting settings or completion – starting, prerequisites, requirements, test & evaluation 31. Rewards & promotions 32. Medical records 33. Capacity, min, max, optional 34. Deadlines, timelines, phases, grace periods, due dates, outlines, content, details 35. Status changes – edit mode, dynamic status lock down 36. eCommerce 37. Inter corp – security, settings (general, per corp, per user, IP address) 38. Back tie to units – this may be on the unit or a pool that the unit is assigned to 39. Cancel/back-out/void (see status), (make sure and cascade to subs) 40. Check in/out (start/stop, actual/rough) 41. Mass entry – recipes, packages, deals 42. Priority & rating 43. Reports & searching needs – capacity, conflicts, testing, history, usage, availability, booked, open/closed 44. Waiting list 45. Cleaning status 46. Fees (late, cleaning, other) 47. Person(s) – customer, vendor, payee, user, salesperson, N/A, party, unassigned, crews, lines, shifts 48. Place(s) – subs, temp, variable, multi, unassigned 49. Thing(s) – storage, units, parts, general or generic, assets, money, supplies, labor, overhead, shipping, sub-contractors, game 50. Dynamics – (fun & extras, names, titles, needs, html, multi-step, memory, colors, increments, webservices) Types of time – columns A. Lists, tasks, assignments B. Notes & reminders, progress reports C. Basic, scheduling & appointments D. Time sheets, time logs E. Sharing & collaboration F. Sales & promotion marketing G. Meetings & events, classes H. Projects, updates & newsletters I. Resorts & tabs J. Reservations K. Dispatching L. Registration M. Job costing, estimates, quotes & invoices N. Maintenance, manufacturing & production O. People, employees, techs, doctors, teachers, crews P. Invoices, e/r’s, bs: reoccurring or system-maintained Q. Goals & forecasting, (production, sales, general) R. Rentals, storage S. Places, rooms, locations, subs, main, #’s T. Things, stock/units, parts, general, pools U. Payments in/out, date due, deadlines & grace periods

	AU 2185		Brainstorming - Ideas & Concepts for the Multi-media Training Tool	2/16/2011	Ideas & concepts for the multi-media training tool 1. Make a template for learning and distributing knowledge. 2. Knowledge = Information (correct & right information) x Experience or K= I x E 3. Add a crumb trail to help the users know where they are at… 4. Secure multi-media player. Be multi-media I mean graphics, buttons, links, text, searchable, printable, audio(mp3), video, mapping, motion, PDF, web, controllable, code once – use many, dynamic templates, database fed, permissions, history, usage, forums, feedback, charts, pod casts, dynamic outlines, decision trees within presentation, still images, automated output, etc. 5. Be able to mix and match what the player can do… 6. The end goal is to automate as much as possible. We may have to take some steps to get to that stage. 7. Usage permissions – General public (no login required), all users per corp (requires a valid login), only specific users may view (1-many from training to users). 8. Usage histories – Every time a user views a clip – we record a history note behind the scenes. Random idea – maybe show the users which ones they have seen and when. Maybe even a started and completed flag. 9. If a valid login is required, how can we help the users know if their time limit is up and/or getting close. Maybe run a check against the login table and then prompt them to keep the session alive by searching or refreshing their login history page. 10. On usage histories – it may be cool if you could require certain training modules before allowing a user to use a specific part of the application. This could get out of control but may help educate people before you just turn them loose. 11. The usage history would also need some special reports to help managers and trainers know what is being viewed and what might need a touch-up or revisit. 12. As long as we are doing training… what about testing and evaluations? Why not include a testing module. Not required at all unless you want it. We provide the database, question templates, etc. We also provide the correcting reports to managers. 13. What about a valid login plus an IP address – additional security? Just an idea. Maybe a white list of IP addresses. This may come later if needed. Another idea is require the IP addresses on the login not the media. 14. Training could be as simple as a narrated slideshow or as complicated as a branching interactive video with different sub sections. Because it is a multi-media player – you could even mix and match presentation types in a single player. 15. Ask the question – what would I do? 16. Maybe allow for web services or domain name aliases… 17. Allow outside users to login under a public username and password to submit content for review and formatting. This may require an approval process or an approval/sign off field(s). Only show items that have been approved. 18. Be able to categorize training. This also includes sort options. 19. Keep things fast and efficient – this may require a hybrid solution… 20. We might need to use frames – standard adilas header, player window, extra content to print or add/edit something, standard footer a. This could help with branding, searchable and printable text, etc. b. This might need to be three or four windows within a single master window – you might need to scroll the whole page as a unit. You may also need to scroll the extra content window. It is possible to also use an I-frame instead of a normal frame. 21. One of the goals is to lessen the number of clicks… leave menus open, show indicators, simulate a back-type button, etc. Make it a good experience. This also includes a play all of next clip. 22. Allow the user to determine what buttons to show… this would be done during the set-up phase of the media clip. Different buttons might be play, pause, stop, rewind, fast forward, full speed, ¾ speed, ½ speed, ¼ speed, loop, back to start, step forward, step back, volume, mute, scroll up, scroll down, scroll right, scroll left, zoom in/out. 23. “Apply” what you learn! Do this along the way… don’t wait to the end. The more you apply it, the more it becomes a part of you. 24. Be able to choose options like video, slide show, horizontal scroll (h-scroll), vertical scroll (v-scroll), audio, web link(s), animation, step-by-step, etc. Each section or sub section could have their own button options. You could also show/hide and call any button from a function call on the fly. 25. Make the player as generic as possible. It also needs to be as flexible as possible. It should be able to respond to any event or need. In order to do this, all functions will need to be available and published (written & documented). We may even need to provide flash code samples. Make it easy, I don’t want to be the bottle neck… open it up for other developers. 26. If a change is made in the process, maybe have a piece at the end that shows additions or modifications. That way you don’t have to totally redo the entire clip. 27. Another idea is to break the pieces into smaller pieces so that it would be easy to cut and paste or fill in changes or gaps. Think “bite size” pieces. 28. Allow backgrounds and text colors to be modified. Maybe even think about variable (dynamic) symbols and buttons (icons). Make everything transparent to help show custom background colors. 29. Another option is to allow dynamic player buttons, use .swf files, and allow the player to be fully customized. Even allow a custom loader to be used. 30. The smaller more modular pieces, the better. This will help with branching logic, videos within videos, smaller downloads, and snap-on components and functionality. 31. Remember the non-flash users. This could be html or .mov files. 32. Push vs. Pull technology. Allow the user options to show related clips or possible next steps. 33. Once we start in to flash… I can see navigation, sub modules, shopping carts, schedulers, training, etc. Starting to play in the same base player. It might be cool if there were optional choices or options for classic html or interactive Flash. 34. I want options for QuickTime, mp3 audio, html step-by-steps, & Flash. I want to service all of our clients and their learning styles. 35. Training may fit best as an element of time similar to a document, outline, or idea. The media assets and contents could then be tied to subs. Think of an interactive outline that has subs and dynamic content. That outline becomes the training as it is organized and then sent to a player to allow the user to interact with it. 36. What about tests, quizzes, and evaluations being tied to education and training pieces? This is not required but might be a cool option. 37. Allow the doors to be opened to recruit or enlist help… This could be flow, concepts, media, content, suggestions, needs, etc. The goal would be to provide a clear and logical path with built-in checkpoints and checks. This is a way to duplicate yourself and share the load. 38. Dealing with content, media, and/or other assets… What about having a place for credits… This is the who behind the pieces… This could help to motivate people to play and even drive business to them as individuals. 39. Random idea – Inside of LTF we have a music selection (jukebox or iPod). It might be fun to allow others to be able to change music or have some fun and control of different tunes and/or moods. This doesn’t have to be tied just to music. It could be for music, background sounds, different levels and takes, tracks, different teachers and/or instructors, additional commentary, etc. Sound and music are a big part of learning and defining who people are and what they enjoy and/or feel comfortable with. 40. Instruction could also be a form of meditation or visualizing certain steps and/or events. Think of some calm backgrounds with someone talking or taking you on a mental journey. 41. What about custom help files or standard operating procedures? Because each page has a help file id, we could technically allow a user to tie in their own procedures dynamically so that their users would see or have access to the correct help files or custom help files. This could be HTML, pdf, audio, video, graphics, or other…. (added 12/14/12)

	AU 2196		Brainstorming Elements of Time - Needs & Form Layout	4/5/2011	Needs for the element of time: - Home page (nav, add new, search form, results, maybe grouped results - Add/edit templates – admin - Add/edit main element of time - Add/edit subs - Advanced search (main and subs) - Advanced search results (main and subs) - Printable - PDF (save as) - Photos - Payroll - Billing or adding to cart (invoice, quote, recipes, my cart favorites, single and multi) - Quick search (numeric, date, new, home, last, all, alpha) - Flex grid stuff - Bulk sort subs… see the work with time page - Void or back out - Admin only or private - Quick drill downs (smart links) - Apply session var (hold to use later) - Initializing templates and setting up items by default - Changing templates (editing the main) - Work with time – work sheet or work area edit line items type page – void, edit; allow for quick status changes, color changes, notes, single assignments, etc., links, bulk sorts, etc., almost like a shopping cart for time When adding the main… allow step by step, allow a preset template, allow a preset date or time, allow a tie-in to a session element of time. If tying to a customer (in add mode) (or edit mode) allow for a search to be conducted or a customer right from the add mode. Figure out a good flow process. Ideas for a time search: - Report Type: Details, Calendar, Time going down, Time going across - Template Filters: All, (drop down menu options) - Created By: All, (drop down menu options) (include inactive users) - Basic Assigned To: All, (drop down menu options) - Time Period: o Daily: (enter the day you want to see) o Weekly: (presets) o Monthly: (month & year drop down menu) o Custom Date Range: _____ to _____

	Adi 7		Web - Full eCommerce	6/3/2011	Here are a number of ideas related to eCommerce... no specific order... just dumping... - Small time eCommerce is where we want to go with this thing (adilas). People will pay the monthly fee just so that they can sell things. - We have created a fun thing in the buttons and what they can do (my cart favorites)... What if we allowed a similar thing with eCommerce. - A customer sign-in could be the customer id number and the email associated for that customer. The customer id would be able to look up the corp id. - I want to have a customer bill pay section where they can pay their bills, look at their payables, print invoices, and histories. Maybe even their own statements with limited functionality. - One big challenge might be shipping and handling... They are separate but somewhat linked. We need free, set, dynamic, and variable options. - I will be building a cart on one server and then passing the whole cart to another server for payment and committing to the database. That could get a little bit tricky and making sure that both sites (send and receive) get updated correctly. - What about inventory levels and selling items that don't exist? How do we handle back orders? - What about custom or web service options... Do we want to use XML, ColdFusion web services, basic HTML, etc? We want to make it portable, yet flexible. We will provide a cookie cutter or pre-built cart and allow for custom options. - Building custom carts could be a great side gig and money maker for me and/or another development company. That may be a great spot for interns and college folk. Create the tools and then open up the road. - We may need some mass or bulk update tools to help with shopping cart stuff. Sales, hide/show, active/inactive, my cart favorites, etc. Special reports. - Make the process as easy as possible. Many of our clients will be in the under 10 items pool. We may have others who are in the 100-10,000+ item pool. Think small to big... - Add photo upload options for part categories, buttons, and promotional banners. The more we can put at our user's finger tips, the better! - Allow a customer to create and save their own quote. - What about merging customer info... We already have them on file but they get entered or created again. - There will need to be corp-wide settings setup and maintained just for the shopping cart... What location, what invoice type, what user (generic), what customer type, what taxes, what promotions, etc. - A flash shopping cart may also be a fun option. Kinda extra. - Emails and promotions, etc. - Quick reports and notifications. Email about new sales. - Ask customers and clients what they want. - We may need a page that has or shows specials. Key off of the web price settings. Maybe have a section for special web prices, best prices, etc. - The price setting per item will either allow a sale or not. - What about quantities on hand? How do we monitor that? Do we check the real site or do we just do it and sort things out later (like back order, credits, refunds, etc.). For the record, it is easier to check first and deny at the door rather than ask someone to leave that is already in and committed. - Our goal is to provide the service... however, wherever possible we should also help our users learn and use good practices. - Keep it ultra simple - show a crumb trail (where you are at and where you are going). - Use email and/or text messages. - Have special reports for web sales. - Treat all sales as either customer sales or transition invoices. - I want to provide some simple buttons that allow a customer to create basic things like a quote, restore to cart, save as... (new quote), statements, pay a bill, real cart checkout, check on outstanding invoices. - Allow custom HTML to be assigned to parts and stock/units. This could be links to movies, tables with rates, calendar graphics, virtual tours, sub navigation, additional verbage, headers, footers, special notes, etc. Think anything custom. It could be added before or after an item - or even both. It could be a one-to-many relationship between the custom sections and the items. We need to allow for sorting, spacing, etc. Basically, a mini snippet or wrapper. Other ideas... links to like products, promotions, ratings, testimonials, availability, reminders, colors, sizes, options, recommendations, waivers, forms, checklists, rosters, syllabus, course work, coupons for local businesses, updates, closures, etc. - Maybe pass back data in XML format instead of letting ColdFusion generate the data. This would make our methods more usable to other developers. Maybe a step further down the line would be to pass a param (coldfusion or xml) to the web services and then let the user decide how they want to deal with the results. If xml, convert and send back. If coldfusion, just process as normal. The XML could be a standalone function that takes a ColdFusion structure and creates the XML notes and pieces. Think reuse... - On the stock/unit photo galleries... we need the captions to show up like they do on the parts galleries. - eCommerce may also include custom pdf documents or other special paperwork or forms (pdf, word, excel, other). - On the corp-wide settings... Maybe have options for show only (default), quote only, or full eCommerce. Maybe instead of a choice (one or the other), maybe create a list of options and let the users select what they want people to do. This list may be extended to customer login, bill pay, reservations, statements, etc. Think options... To help with outside code (additional web services or custom eCommerce web sites), pass all incoming data through a verifier or validator or sorts. If the incoming data is missing one or more pieces, either ask for it or use a default value. That way all of the main code can run as needed. This allows us to update things (normal flow and values) and still allow for possible older outside code to function correctly.

	Adi 12		Photos - Secure images & use a content server	6/3/2011	Random notes about the content server... - On the current thumbnails, take off the height attribute and re-do all thumbnails. This allows for square, portrait, and landscape images. - Maybe allow for other content to be saved... Create special images and icons for word docs, excel files, adobe pdf, and other generic files. Images would have their own icon (mini thumbnail) and other docs would use these custom graphics. - Set an upload size limit. Say like 2 MB and then let them upload whatever they want... We might need to be careful with things like web code, java-script, sql, etc. - What about virus protection? What do we do about that? Does that really matter? How would it affect us? What are the other possible threats? I do have a full sheet of notes that are dated 3/21/11 in my file at home with about 20 ideas and feature requirements.

	AU 628		Daily Ideas	10/5/2011	New request from Steve: -Customer: 4 new date fields with corp-wide settings. (Active date range) Start date, end date; start period date, end period date (expiration date – membership expiration date range). On ending period date – add a notification if passed, don’t allow a new cart – maybe some rules of engagement and notification or full lockdown. -Preload the start dates according to history. -Pull flex grid MMR #’s to customer tax id’s. -Pull the terms (dates) and add to expiration date fields. -Add a new generic search field to search an item, put it close to the add item button. -Take off Java Script for top quick search focus. -Need a flag to show who has been started in the cart. -Queuing a customer – in memory not in the database. 2 hour limit – when invoiced kick out or after 2 hours check-in/out – queue by time in, be able to flush. -On the queue – track from check-in to invoice time – that might be good to see how much time passes between these states. -Be able to start cart or start time for persons in queue. -On the customer dates – they also need to show up on the following pages and reports: customer log, add/edit, history, gallery, normal search, advanced search, export to MS Excel, MMED custom forms, shopping cart, invoices, quotes, PDF’s, cart payment, etc.

	AU 3566		2011	12/31/2011	YEARLY ACCOMPLISHMENTS 2011 Steve, This is a list of things that happened and accomplishments made during the 2011 year on adilas. It was a great year with tons of new and awesome stuff. More and more still to come… If you need additional details, just let me know. I have everything documented down to the date. January 2011: • New tax tables for 2011 (federal & state). • PCI Compliance Renewal. • Added Authorize.net as a new merchant gateway (merchant processing). • Added the running daily bank balance (per transaction) to the check register. • Added a part number “group” option to the invoice line items search page. Added a switch between groups and details. • Created a similar group and detail toggle switch for PO line items (incoming parts and quantities). • Made a conscience switch to get out of the retail hardware side of business (card readers, receipt printers, barcode scanners, etc.) and focus more on the reoccurring services that we provide. • Added an alpha name search to the quick search options for invoices, quotes, expense/receipts, PO’s, and checks. This allows a search for all results for a given customer name or vendor/payee right from the quick search. • Moved the force payment checkbox on the verify PO page to one step deeper. • Added more links and flow to help with looking up vendor/payees and their current payables. • New corp-wide settings for show/hide tax categories on invoices and quote and a default credit card transaction mode for the merchant processing page (retail swiped, manual keyed, or both). • Created the accomplishments lists for 2009 & 2010. Posted scans online to the adilas history balance sheet item (special archive photo gallery). • Added dynamic drop-down options to the flex grid tie-in titles and custom field names. February 2011: • Started working on the adilas “any” scheduler. This name was later changed to “Elements of Time”. • Tons of notes, ideas, research, concepting, and brainstorming on elements of time. • Went around (onsite) to 10 different businesses to get ideas about how they deal with, tracked, and used time. Filled out prepared questionnaire to gather data. Compiled data into notes and ideas for elements of time. • Added quick search options for main id numbers, included parts, customers, and vendor/payees. • Worked on graphic mock-up for the interactive map and the multimedia training application (player). These are future concepts for adilas university and the main adilas.biz interactive navigation interface. • Added an auto calculate switch (checkbox) to the advanced add to cart page. That allowed us to do more than one calculation at a time before the local math was done. This allowed for things like: unknown weights (quantity), sealed items (USB digital scales), backing in to a fixed total price, and using a tax category of “with tax included”. With the new switch, all of these calculations could be done at once instead of one calculation at a time. • Added options to pass pre-set values from my cart favorite buttons to the advanced add to cart page (options 5 under use exact part number button type). • Created three different bio’s or history documents about adilas. They are the business bi, the education bio, and the brief history of adilas.biz. • Elements of time began to split in to two different sub types. They were types of time (ended up being master time templates) and functions of time (ended up being subs or add-ons of time). March 2011: • Added the CHARGE Anywhere gateway (merchant processing). • Changed the main adilas.biz homepage. Added a search by date field and changed the stats to “daily” stats as compared to the overall “total” stats. • Working on basic database design and layout for elements of time. • Added corp-wide setting and permissions for cross-corp billing. • Added three new fields to the customer statements. They are for the invoice age, the paid status, and the payment types. • Ordered a new content server. • Created a custom CSV file for Dealer Car Search. The export builds itself and sends itself every day at a given time. Includes stock number details, descriptions, prices, and available photos of the stock/units. • Added my cart favorite “group” buttons and a thing we called the advanced grid or add multi grid. Basically a grid that has advanced add to cart features for multiple products at one time. The groups allowed for stacking (depth) of standard my cart favorite buttons. April 2011: • Working on elements of time. Added tons of new pages. Pages included add/edit master time templates, add/edit basic elements of time, basic time search, the working with time page (generic edit mode), printable time page, and time history page. • Decided that each corporation should have their own PO and invoice line items table. Major rework on logic and flow. Split the main table in to corp-specific mini tables. This change affected close to 100 different pages. • Created a multi-corp – multi-location – daily/weekly sales report. Able to pull data by corp, by location, by date, by part category all at one time. One of the first cross-corp reports to come out of adilas. May 2011: • Added the advanced time search (build your own report interface for time) and the advanced results pages. • Added ability to assign time to specific customers, employees, vendors, and locations. Also allowed options to assign to generic persons or places (any – even if not in the system). • Created a bid and proposal for the State of Colorado for the MMJ industry tracking program. • Started working on the sub functions or add-ons of time. They were the action status logs, sub dates and times, and sub comments and notes. • Added a “view only” options (permission) for the my cart favorite buttons. This allowed for one user to set the buttons and then others (maybe not as technical savvy) to use their buttons as their own. This also allowed for a virtual master list of buttons for a single corporation. June 2011: • Constant tweaks to the elements of time section. New settings, new defaults, and new options. • Added a description option to the barcode generator application. Able to switch between a barcode value or a description value (text). • Added a contact (email) adilas support page from any of the application help files. • Kiva and Steve came up with some “short cuts to adilas”. A PDF document for users to get started. • Launched the first round of the interactive map concept. The concept was still a graphic (not yet interactive) but did have a number of links overlaid on the graphic to help with temporary navigation options. • Added a sneak peek graphic to the main switchboard page. The underlying page listed current and upcoming projects that are planned and scheduled. Kind of a small insight to where we are headed or a view of the master plan. • Documented all of the “quick search” options, values, and keyword searches. Put all documentation into its own help files. Added links from different pages to the help file with the documentation. • Added elements of time and reoccurring invoices (reminders) to the main history homepage report. • Added the customer type to the shopping cart. • Increased the number of custom fields on the flex grid tie-ins. Went from 10 custom fields to 15. • Added two new major players to the flex grid tie-ins. They were elements of time and quotes. This brought the total main application types to 12. The flex grid is now a 12 x 12 x 15 matrix as compared with the old 10 x 10 x 10 matrix. • Reworked the flex grid tie-in search results. Made it more human readable to the end user. The old way only had the main application type initials and an id number (example: cust 10001). The new way still shows all of the info but also has a human readable column next to the id number of the tie-in info (example: cust 10001 – Fred Flinstone). July 2011: • Added the flex grid tie-in info to the add/edit customer page. Before it was only shown on the customer log page. • Added a custom shipping CSV file. Custom document tied on a per invoice basis and assigned through the custom document management system. • Kiva took over the reoccurring invoices, credit card payments, and adilas billing functions. • Added a “refine your search” option for elements of time (advanced time search and results). • Added a “grouped” elements of time to customer report to help with billing and assigned times and invoice/quote status values. • Added options to convert one or more elements of time to the shopping cart. This is part of the customer billing options. • Added new corp-wide settings for the customer tax id name, the location license number, and the printable disclaimer text (unlimited text length for invoices and quotes). • Converted all normal customer logs (notes and follow-up notes) to HTML compatible. This allows for things like line breaks, links, and other formatting. • Added an option to search the customer tax id (dynamic name) from the customer quick search. Many of our clients are using a barcode scanner or card reader to search for their customers. August 2011: • Finished up the time to cart process (customer billing). Pretty in depth processing and lots of cross tying between time, quotes, and invoices. All the users have to do is point and click. • Added a couple of MMED forms for the State of Colorado. We added one for the monthly primary center patient list (form 1010) and one for the daily patient sales report (form 1100). • Added an IP address field to the user login/logout actions. This helps a manager know where the users are logging in/out from. September 2011: • Created a generic customer export to Microsoft Excel that included basic customer info plus any flex grid tie-in fields. • Added subs of time to the time to cart process. Other tweaks to help the flow between time and invoices and quotes. • Added an IP address field to the employee clock in/out (timecard) application. Timecards are tied to payroll, so, this helps managers know where the clock in/outs took place. • Created advanced search options for subs of time (add-on functions of time). They include searches for action status logs, sub dates and times, and sub comments and notes. • Added the MAXX payment gateway (merchant processing). • Steve went to a big Trailer Dealer Convention in Texas. Came back with a number of leads and new ideas. • Added a temporary patch for sales tax on the balance sheet. • Added a customer type filter to the my cart favorite buttons. Not required but filters buttons once a customer is assigned to the shopping cart. Helps with different pricing for members vs. non-members. • Major work on visual reports for elements of time. The main time homepage is capable of showing a calendar view (up to 365 days at a time), a dynamic time slot view (daily detail view with any increment of time and a start/stop range), a grouped report, and the normal time details (organized list) reports. • Publicly released elements of time. Round one of three (other future releases will come later on). October 2011: • Added a new quick search option right from the top of the view cart page. This allows for parts searches and barcode scans right from the view cart page. • Added four new customer date fields (main start, main end, period start, and period end). Each new field also has a corp-wide setting attached to help with custom naming options. The period end date has special code to help watch for passed or expired values (shows up in red). • Added a number of new corp-wide settings for elements of time. This deals primarily with what the user sees when they first come to the time homepage. Default settings include things like: time period (date range to show), report type, calendar block size, time slot start/stop range, time slot block size, and show/hide extra stats and subs. • Added a basic export to Microsoft Excel for invoice sales data. • Added a new customer queue application to help track “who is next” for customers and waiting rooms. Virtually a check in/out monitoring process. • Updated the custom document settings for the Texas 130-U (new version). Also added a data only version to help with the facto form printing for title applications. • Added options to change prices and button status on the bulk sort page for my cart favorites. November 2011: • Small tweak on the balance sheet. Showed the difference between the total tax and the possible out of balance value. • Added the user history report (historical history) to the main history homepage. Includes 20+ system-maintained user history sections (actions recorded behind the scenes for system events). • Added a better “change due” call out on the mini 3” invoice format. • Added a new permission called “my history” and connected it to a filtered portion of the main user history report. • Created a new “grouped” customer invoice report. Ability to sort by customer, invoice count, and total invoice sales (sums). • Expanded export options (to excel) for invoices (total of 5 different reports). Added a “refine your search” options to all advanced searches for invoices. December 2011: • Added links to the barcode generator to and from stock/units and for customers. • New customer exports to MS Excel. Including the advanced (build your own report) search, customer logs, and additional contacts. Tied to all exports to the advanced permission for customers. • Added a “refine your search” option to the advanced customer search results. Added an export to Excel for part numbers and quantities. Also tied this export to the advanced permission for parts. • Added a new permission to help with quick retail sales (counter sales or non-customer tickets). Also sped up the customer to cart assignments. • Added an options to hide the main cart info for non-customer counter sales in the view cart page. • Added a new corp-wide setting to use or skip the review cart page (final step in the cart process before converting the cart to an invoice). • Updated all tax tables for the tax year of 2012. • Small change to the balance sheet homepage. Pre-selected the checkboxes for show assets, liabilities, and equity sections. Yee Haw! More to come in 2012!

	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

	AU 759		Daily Ideas	3/26/2012	-We need to provide updates on what we are working on and what is new. -We need a payables rework – we need to break things into 0-30, 30-60, 60-90, 90-180, 180-360, and over 360 for aging. -We need a section for sales and promotions that are tied to time, dates and even small segments of time. -Lots of requests to be able to change the thumbnail images. Also take off the force on the height. -We are also getting more requests for MS Excel, MS Word, PDF, jpg, etc. People want to store different kinds of content. -We are getting more and more requests for the custom report builder functionality. The old form of this was called “mend and repair” in the old system. -On the flex grid – we need the ability to set specific data types per field. These are things like text, date, numeric, Boolean, etc. That way we could do calculations, ranges, etc. Things that you can’t do with text fields directly. Just an idea, we could run data through a conversion type function (force apples to apples) and then do some sorting or filtering. We could also create and use temp tables if it got to that point (convert, filter, report, destroy the temp). This could be done over and over or we could figure out a more permanent solution. My goal as the developer would be to make the solution be as light as possible so that every record didn’t have to carry a huge extra data burden (tons of unused fields, flags and indexes). Keep it light and quick.

	Adi 440		Flex Grid - Set data types on custom fields	7/27/2012	We need the ability to set specific data types per custom fields in the flex grid tie-ins. These are things like text, dates, numeric, decimals, boolean (yes/no), etc. That way we could do calculations, search date ranges, do aging, hold real money values, etc. Currently all custom fields are stored in text fields which do not allow certain functions. Just an idea... We could run data through a conversion type function (force apples to apples) and then do some sorting or filtering. We could also create and use temp tables if it got to that point (convert, filter, report, and then destroy the temp table). This could be done over and over or we could figure out a more permanent solution. My goal as the developer would be to make the solution be as light as possible so that every record didn't have to carry a huge extra data burden (potentially tons of unused fields, flags, and indexes). Keep it light and quick... :)

	AU 988		Daily Ideas	11/1/2012	-We need the reflexive side of the flex grid and the roll call page. Whit is connected to what and how does it play. -We need a report that shows activity and summaries (full database): who does what? How many? Values? Where are people doing things per corp as well? -On database tables – we need to add indexes to the dates. We may also want to convert dates to numeric values (just a thought). -On time – people really want to see blocks (visual) of time. We are catching all the data, the system needs to be smart enough to show an appointment from 2-4pm (the whole block filled in). The same is true with multi-dates like, all day Monday or Tuesday-Thursday for a conference.

	AU 2264		Brainstorming Outline for the Main adilas.biz Homepage & What It Is We Do	12/7/2012	E.D.G.E – Explain, demonstrate, guide, enable – Boy Scouts of America Outline for the main adilas.biz homepage and what is it that we do: Build on common ground… you win more bees with honey than salt. - Very simple… we help people track data - Data means different things to different people - Help you see the whole picture - “System” is a key word - Start with operations - A full system allows you to do things that others can’t do…. - Cause & effect will create accounting - Small review of where traditional accounting came from - We do things differently now - Accounting needs to follow the changes in trends - One huge key is “time” - Here is what we want to do about it - Invite people to participate & help - Why do you do it? Because it needs to be done! - Ask the question… what would I do? This helps develop the why. The why takes time and is counter to the fast food mentality of I want it now! - Add an audio version to the website… read it for the people

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

	AU 1030		Daily Ideas	12/22/2012	-On payroll and time clocks – we’ve had a request to help log or clock a person in/out if they work past midnight. Basically the code checks for specific dates and doesn’t let anything cross over the magic midnight line. We may need to automate the roll over. -Our biggest competition is “tradition” and what people consider “normal”. -If we end up sharing code, with the public, we may need to strip off some of the security stuff to keep our code safe. This could include the decoders and the decoder key. There may be some other pieces that don’t get included. -Match the right tool to the right job. -Consulting is key! -Good education and maintenance might be better than a great feature. -Adilas may not be the right fit for every business. -Teach database logic and relations. Teach one-to-many, one-to-one, and one-to-many-to-many. Teach them how to create objects. Symbols for these relationships are: normal 1-many, 1-1, 1-many-many -Features, advantages, and benefits! -Make a power-point slide show. Use bullets, graphics, and minimal transitions. -Be willing to share the road way and even provide a map to what we have learned. -We do the same basic things over and over again. We use the main homepages as a hub or starting point. We then jump to sub stations or sub homepages. We use basic searches, advanced searches, reports, permissions, settings, histories, add and edit processes and tons of 1-many relationships over and over again. -Once you learn our flavor and methods, it helps you to figure out the other pieces. -Review and help teach the history of double entry accounting. -Make sure and use my son’s graphic (drawing) of a boat sailing off the world. (Columbus 1492) -Old school accounting – paper copies and transferring from place to place or book to book. (Journals and ledgers) -I think that I could use my son’s skill in talking and negotiating – he is amazing at it! -My son loves to go driving with me. I control the pedals. Once we are in a safe location, I let him have fun and play around. Care is taken to only let him play in certain, safe situations. -Our product is a service. It falls somewhere between millions for custom write ups and $200-$600 far off the shelf products at Wal-Mart or Best Buy -Our service is software as a service or “saas”. A cloud based data portal. Your data, you cache and retrieve it, we secure it. -Centralized data – it all starts here. -Some of the other solutions are $6,000,000 for a license and $1,500,000 for implementations. -Plenty of room, enough to share the knowledge. -We are actively experimenting, exploring and pioneering. -Lots of sci-fi analogies: flying, transporting, mother ship, clones, time-travel, virtual reality. -Examples of a flat file vs. a 3D object with multiple entry points. It would be fun to show a comparison between the two. -I end up borrowing thoughts, sayings and ideas from lots of other places. This is called learning for transfer. -At some time we will need to add features for waste removal. -Pattern after nature or existing models and objects. -Help people connect the dots, help them see how things are inter-connected. -Different personalities and styles are great. Diversity is great! -Lots of life lessons. -Teach about relations and relationships. -Multiple entry points. -Elements of control – relate to what I do and how I feel sometimes. -Different needs and personalities are great and needed. Let the system and permissions be the bad guy. This may help to create a commonality between skills and personalities. -Often tying things to pay makes a huge difference. Sometimes this helps to get compliance. Money speaks… -Change can be tough – sometimes it helps to have a burning platform. Imaging an off-shore oil platform; most people won’t jump if you tell them to. However, if the platform is on fire, they will jump on their own. -We use a thing called “try-storming”. This is brainstorming and then implementing, knowing that we might have to come back around. This creates a very dynamic pioneering process. -Plan it out, take a stab at it, and be willing to come back around. There may be multiple rounds or trials. Time plays a part in this type of development. -We need to let people see our tick list. This may help them see the vision or even look forward to future projects. -We need to put a lid on it! We need to temporarily limit the development and focus on training and education! -Sell the current system “as is”! -Give the analogy of going down a rabbit hole; lots of options, tunnels, exploring, depth. -We only have created one of thousands of possible solutions. We have taken some broad strokes on some main pieces. There is literally tons of room for niche or industry specific applications. (Kind of like tunnels off the main rabbit hole.) -We really shine with multi locations and tracking details. That usually means that we need a detail oriented person somewhere in the organization. Old adage of, garbage in equals garbage out. -How do you learn and/or apply knowledge. Is it like a drop at a time (a drip system) or do you do flood irrigating. Little by little is a great way to go. This could be knowledge, information, tasks, settings, permissions. -Give your clients homework assignments and then return and report. -We are based on a foundation of permissions and settings. -You can or will be able to build your own interface. What do you want? What do you need? -Elements of time – use tasks and reminders for employees. Assign something and then have it show-up until completed or finished. -We use multi check and balances to create happy and sad objects. We even use happy faces and sad faces. We might need more of this. -We need to train the trainers. -On database dates, I would like to store numeric dates. This includes dates, times, date/time stamp and days. The ‘days’ is a new twist. Store Sunday –Saturday as a number. This will allow for reports, what happens on Fridays? -Just like LTF we need to show common mistakes and ways to fix things. -LTF used a great model of get the skills, learn the moves, go ride. Each of those sections was broken up into smaller pieces such as pre-requisite sites, exercises, beginner, intermediate, common mistakes, freeride, and next steps. -This is not a product you buy off the shelf. It is in a constant state of change. Possible lifetime work in progress. It may never be done. That’s why we are getting things out there; we don’t know what is going to happen. -3D accounting – running things through times to virtually build structure, texture and depth. -If we get lots of money, maybe buy back some of the domain names we had to let go, protect that piece. They kind of tell a story of where we are going. -Help other people look good. -Train the competition. -Ours is one of many possible solutions, lots of options. -We, as a company, know and are okay with the fact that at some point we will be leap frogged. It is just part of the game. -Simplicity through simple steps. Complexity through simple steps. -Solicit God’s help through prayer. Then be thankful for the help. Acknowledge His hand! -One of our greatest assets is the ideas and suggestions that we get from other people. This could be our users, reps, business owners, clients and other people. -We truly have become a community effort. -Help people see and compare the amount of work it takes to do real double entry and possible holes that can and may happen. This could be fat fingers, forgot, transposed, misplaced, time issues, not done in a timely fashion, gaps, holes and human error. -Get multiple eyes on the same data. Enter once, use many. If correct (the data) let it flow. Use the analogy of water droplets turning to ice: water (loose), slush, crystals, ice. Approve and pass it on. -It is very hard to jump to the end without a base or the small steps it takes to get there. Maybe even do an object lesson. Get a starting place, pick a goal, then figure out a plan. Make it real and attainable. No magic, no jet packs, no speeders, no flying crafts – unless that is part of the plan. It is okay to dream, we just need to remember how much time, money or energy things take. -Plan, Pace, Perform, Review – get a base, take small steps, you’ll get there. -Tell the story – it is amazing what that solves. -Take the time to do things right. Put it to bed, tuck it in, turn off the lights, let it rest. Once it is done, move on, next! -I love the word “again” - like a little child going down a slide – “again”. Keep it positive. -Draw a line in the sand – help bring things forward. This is how you start in the middle. -Isaiah the prophet (Old Testament) - sometimes hard to understand. He talked about the past, present, and the future sometimes without a transition. -Driving a car, you have to take drivers Ed, you have to be a certain age, you get a permit, you practice, you take a test, and then later on, you may get tested again. -Getting a little bit here and a little bit there – organic and smooth (at least in theory). -Data mapping is like a GPS tracking system for data. Kind of like tracking an UPS of FedEx package. Every check point is recorded and documented. If needed, you could virtually go back in time. This is tracking data items (packages) over time. -Do exercises – build 1-many relationships. Teach people the concept, enable them! -Many people want things all at once – maybe use the analogy of a rough circle rolling until it becomes a smooth and polished circle. This is a process that takes time. -Simple drawings – make them available without tons of words, then be able to point and explain. I’d like to refer to them at will. Maybe even make each one the size of a page 8 ½ x 11 or 11 x 8 ½. -Figure out – what is your goal or your client’s goal? How quick do you want to get there? Are you willing to take a step-by-step approach or do you want to make a single leap? -There is a great story in the Bible about sharing and giving. It deals with Elisha the prophet (2 Kings 7). There is a great famine in the land and the people of Israel are under siege from the Syrian army. Four leprous guys are outside the main city and decide, if we stay we die, if we go into the city we will die. Let’s go see if the Syrians have any food. If they kill us, we die anyway, so let’s go check it out. They found the whole camp empty of people but loaded with stuff. They take some of the stuff and hide it. Eventually they decide to tell the people. The people are saved from both the famine and the ward. Kind of a fun story about sharing and giving away information. -Little tid-bits go a long way. -Adilas (the data portal section) will starve without data and input.

	AU 1043		Daily Tasks	1/10/2013	• On the phone with a client talking about generic inventory items and the find and replace functions. • New logo for a company. • Tech support and emails. • Bank work. • On the phone with Steve going over new accounts and ideas for the training course. • Answering emails and writing how-to's for depreciation expenses and creating generic inventory items. Long emails. • Went into town to help with the Thursday Beaver Mountain ski and snowboard classes. Did an LTF demo and gave out product. Also went over to the instructional technology department at USU and gave out product and did a demo. 20 miles.

	AU 1048		Daily Tasks	1/16/2013	• Changed how a numeric recipe search works. Instead of going to the printable recipe/build, it will go right to the build prep for that recipe. • Sent an update email out to Steve with info about the keyword “auto” and all of the new buttons and tweaks to the recipe/build section. • Adding a part status filter to the printable parts list report. Also added the part status as a filter for the update inventory count section. • Working on the update inventory count section. Posted the files online and updated the help files. • Populating 1099’s with live data. • Small demo and training for my sister.

	AU 1133		Daily Ideas	3/2/2013	-Inline custom code – use adilas as is… with options to tweak and show things or do things (custom) in the fly. Think of the title of this note… inline custom code. After flow, change layouts, shortcut steps, etc. -Once we open up the outside “API” or web services… allow a company to lock things down or expose only certain pieces. Think “settings & permissions.” -It may be time to pull out the promotion code stuff. As part of that… it may be col if when a user lands on the promotion code homepage, they have a way to see and track results of certain promotion codes or marketing avenues. -Lately I’ve been thinking more about pushing elements of time and doing a couple week blitz to take it to round 2 (two). This would include showing spans, running off of numeric data, and adding more subs of time. The subs of time provide the extra functions. The one I really want is the any person, place, or thing sub. This deals with rentals, reservations, dispatching, etc. It could also be used for classes, registration and multi assignments. -Another thing that is rising to the surface is the “roll call” page for each item. Another is the calendar overlay of data. -Known issues page and date problem report. These are big helper pages. -Get the important stuff done first and then jump on these other projects that are rising to the top.

	AU 1143		Daily Ideas	3/19/2013	Questions about using interns: 1. What is the general process? - Start with a budget. - Offer a premier internship… - Leverage to new business options. - Sell yourself as the best. - USU is your friend and they want to be exploited. - The more you praise somebody… the harder they work. 2. What is required? Time, money, paperwork, contracts, etc. - Manage things with price. - Let price be your friend. - The University wants to be sold. 3. Who do I contact? How do I go about that? - Go up to USU. Talk to a specific contact. Go to the HR department. - Ask to come and speak to different departments. - Go with BIS students… you could always teach programming. 4. How did you get so many at a time? Where did you start? - Bid half of what you need or expect on the first go around. - Go simple and learn as you go. - The cash cow – bring in money…. - Layout the basics – training. 5. What where some things that you did that you thought were successful? 6. What were some things that you did that you wish you could do over and/or change? 7. What was the interview process? - Skill and heart. - Great attitude. 8. What kind of time did it take on your part to put things together? 9. Was anybody assigned to help you? 10. What was your favorite part about using interns? Why? 11. Recommendations…. - We didn’t get to all of the questions. - Protection through giving. o He asked me how I was protecting myself. My answer was – through giving… I’m okay with that! -Career Aggie, usu.edu/career -I was walking past some landscape architect drawings… tons of details and great concepts. Why not do the same thing for adilas… Let somebody design the layout and flow for what they want and need. We already have the dynamic interface capabilities, why not let them tweak it out. Let’s get some artists. -Adilas by itself is a bare bones interface…. Allow each corporation to customize their own skin or GUI (graphical user interface). USU – Info blast or Information Session – recruiting event – Target Stores was the presenter -Power point slide show – simple – bulleted – branded. -Why do you love your job? Come to work and love your job. -How is the company doing… Growing… -What is the business structure… this is this and that is that, etc. -What are we looking for? What will you be doing? -The interview process. -Managers vs. Leaders – looking for leaders. -Little tag lines as branding. -Star method – situation, task, action, result. -They had someone who had already done the internship. -Fast, fun, and friendly. -The discussion was fun and engaging. -Where will you be in three year, five years… -See if you are a good fit? Check it out. -Recruiting – selling yourself, your ideas, your products, your vision… Recruit and seek help! ___________________________________________________________ -What if you missed business data mapping with inline custom code… Instead of just altering a process… what if your process was dynamically mapped to your reports and even your accounting. You virtually get to create the process, the flow, and the mapping for accounting or other key points or indicators. Make the whole thing be dynamic. What is the story? What are the key check points or states, and what are the cause and effect relationships or mapping? If you don’t like our default process or mapping… no problem… do it your way! -What if we had a mini date/time clock application that could virtually be a cross between the following pieces… - A digital time clock (ins and outs) - A date or date range with pre-defined flags. - The power of the flex grid but smaller… maybe or maybe not. -What if we added more to the flex grid and let it play into the custom flow, flags, and time clock level? What if we added a section to the flex grid that could be mapped to and would hold a value as a state, status, or checkpoint? -Let the flex grid hold and/or become a bigger player. Use it in doing custom mappings, custom flow, etc. We would need another date field, sometime fields, and some numeric fields. -One known issue is data types… the flex gird uses a lot of text based fields… What if we could dynamically “type” or “cast” certain fields to be certain data types. For example: strings, numeric, dates, decimals, etc. Interesting. -A mix between: tools, functions, data, settings, and permissions. What do you want? What do you need? How do you want to do it? What are the steps? -make your own model… -We just sell Legos… what you build or do with them is up to you… We sell potential! -On the flex grid… we could add more fields like dates, times, numeric, and then allow users to turn them on/off just like time templates. If they aren’t used, they are attached but hidden. If they are used, then they play as part of the game. -If you are controlling the mapping of the data… you may need to record the logic and SQL (math & formula) for your custom mapping. Something to think about. -What if the entire adilas application was all done by code in the database. Instead of using rigid files… what if each corp virtually created their own files based on instructions from within the system. -At some point, some company will want full SQL access to their data… that way they could do or run multiple pieces with custom data and calculations. -Random note and idea – I think it would be fun to write a book about my different worlds. I have reality with home and family, and I have this fantasy or sci-fi world of adilas with smoke and mirrors, data objects, relationships, and full of ideals and dreams. It might make a fun book at some future point.

	AU 1195		Daily Ideas	4/20/2013	-Thinking about “roll call”… I don’t even know if this is possible, but would happen if you had one table just for roll call? This would be what flag, what date, what checkpoint, what status? This is just an idea but if we had everything in one place, it sure would make reporting easier. Currently we have all of the pieces (mostly) but they are all continued in-line or on tons of different tables. -This idea is somewhat related to some topics back in October and November of 2010. We have tons of brainstorming on watchers, feeders, standalone declarations, etc. A global “roll call” table may end up being part of those options. -In a nut shell – things happen every day (changing, turning, staying, coming, going, becoming, etc.) Our goal is where is it at (the objects and/or data) when the day closes? Almost like a “snapshot” or daily summary. If more details are needed, we could always go back and check on the objects history. -The one (or more) problems with this deal with changes and going back in time. This is especially true if one value is related to another value. You end up getting a cause and effect chain of events. -One way to solve this is to put each corporation on its own mini adilas and then look-up all of details, dates, and flags on the fly. We could speed things up by using numeric dates, smaller tables, and using global watchers that help things stay contained. We have a thing called the “ice down” date. That could help us lock things down and then don’t allow any changes. If a change is needed, we could back up the ice down date and then record changes. That date could be a backward compatible border or boundary of sorts. Basically, a no one goes past here unless the ice down date is backed up. -Another thought keeps playing through my head… what if you still kept – all data is live and searchable – but added a lock or sorts. You still want all of the data but you also don’t want everything to be flexible all the time. Maybe once you lock it down, no one gets to touch, unless the lock down (ice down) date gets pushed back. Everything is still there and plays a part but it prevents tampering and changing once it gets perfectly locked down. -Maybe think about formulas in a spreadsheet… But be able to lock them down…

	AU 1199		Daily Ideas	4/25/2013	My sister took a bunch of notes. These are some of her notes: - Permissions/settings – finite (a few) main things, click on it (small list) and then expand your options. Instead of having things all together, break it up into sections. - Page settings – personalized - almost like a print preview setting. Be able to check or click something and have it interactively show up or show what it does. - Knowing/understanding settings and permissions. Not just how to use it but what does it do. - Email & text message blasts through adilas. Something free and/or connect to an outside service. - Access to print barcodes… they would like to print groups, sheets, or be able to get at them quicker. - Loyalty punch card, gift certificates, reward points, and other marketing options. - People really want quick, user friendly, efficient flow and effective tools. - A control or view to see who is logged in. - Interaction is the best part for digesting the info. - Be able to sort parts or quantity per vendor. This would help with ordering. - It would be nice to show ways or how things expire. This deals with inventory and expiration dates. - Some of the companies would like to use QR (quick reference) codes. These are 2D barcodes that can store more info than a standard font based barcode. - People would like to send invoices by clicking a button. - Through eCommerce, allow people to agree to text and email blasts. - Percentage discount calculator on incoming PO’s. Basically, allocate a certain percentage across the board. Currently this is a manual calculation. - Reflexive side of the flex grid. - Add a new permission for super admin photo management. - Specific industry training or specialized info and feedback. - Notifiers - Capture and allow digital signatures inside of adilas. - Be able to control custom data types. How do you want custom data fields to play? Text, numeric, Boolean, date, etc. - Art on consignment idea for interfaces. Our rep mentioned tattoo artists and how they market their art work. If you want this, go see so and so. - We had a request for a couple of old reports to be brought back. They are: Best sellers report and Build your own report (mend & repair). - Export to CSV (comma separated values) files for all data inside of adilas. - “Open communication” – conversation at the end of the day with adilas team members and a rep. - We are trying to take our shared database model into smaller individual pieces. We still want to allow multi and sub corporations. We may not want to break our current model. There is still some huge value in what we have going on. It still may be important to have everything play under the same roof. - We may need an html (plain web) version for my cart favorites. Currently, they only use Flash technology. - When teaching sales & invoicing… Make sure and include discounts, returns, trades, and refunds. These are all very important. - On the steps to success (user guide/outline) – Talk about settings and permissions per category. Also, group the help files under the different sub sections. - Similar to the US Forest Service – Land of Many Uses – adilas is a land of many uses.

	AU 1234		Daily Ideas	5/11/2013	-I woke up at 4:00 am dreaming about how data was organized over time. It felt like something was missing from my dream but I wanted to record what I scribbled on some post-it notes before going back to bed. When I say “calendar”, I was thinking dates and times in general. Not specifically a calendar application. Anyways, I was trying to organize the different pieces into a calendar type format. This was clear at the players and sub players level. In other words, clear at the database table level. Imaging 200+ (two hundred plus) tables with data, objects, and relations all playing in time to complete the whole. Here are some of my notes… -It starts with objects and data overtime - This helps tell the story or the history o As this happens “relationships” are created and formed. * This is the who, what, where, when, how long, how much, how many, etc. (aka details) o The blocks of time then sub divide into smaller pieces. For example: Days, hours, minutes, and seconds. * These time blocks then divide into the 200+ tables were data is stored. This is how relationships are formed in a digital world. * They can be grouped by day (default) or by smaller blocks if needed. (Small diagram: in notebook) (This is where the objects, data and relationships go or end up. This tiny square is where you could have your 200+ database tables that hold the data.) Notes from a dream about organizing data over time. (Continued) -Anyways, I was seeing the database tables holding data clear down at the second level. This is kind of deep but it felt like the best spot for it. Prior to this dream, I’ve always envisioned the database at the day or daily level. However, it feels like it needs to go even deeper. Basically, at the day level, there are too many variables (too big of a time span). If you took it clear down to the seconds you could always go back up and sum things up by the minute, hour, day, month, year, etc. -If you take things clear down to the second level, without freaking out or overwhelming, your users, you get? - This produces the story, the history, and the ability to track objects and data over time. - Time becomes the constant piece to ride on. - It comes back to – all data is live and searchable. - This also allows for groups, edits, changes, flex, corrections, etc. - It allows us to convert data (virtual water) water-slush-snow-ice. - This also creates the “life cycle” -It circles back to tracking objects and data over time. -Enter once; use it over and over again. -If the data is correct, let it flow! -If a change is needed, make the change, lock it down, and let it flow! -All data is live and searchable. -I keep thinking that it would be cool if we could run reports off of archived values. However, every time I go there, I can see a problem if anything changes in the past. It has a cause and effect relationship going forward. It basically makes it so that you can’t rely on the archived values. Maybe the secret is to start with the just in time calculation and help speed up the database processing and indexing. -Numeric dates could help out a ton. You could index the main integer part and then store the decimal part as a separate value. The integer part is the day; the decimal part is the hours, minutes, and seconds. -The default group would be on the day or integer level. If the user needed to go deeper they could get into the decimal part. It would still exist but the default would be on the day or integer level. -Either way, if using a numeric date value, make sure to separate it into two different fields. Index the integer and just store the decimal part. If no decimal is needed, just use 0 (zero). -I had some fun ideas about adilas university the other day. It was kind of a cross between adilas and LTF and using a non-linear Flash type interface. I also thought about simple HTML Frames, sub menus, etc. -Some diagrams in the notebook: -each link from the simple page would load in a new menu on the frame set. -a click from the frame-set menu would put a video into the player. -Another idea was an app of sorts that uses the screen area to show everything. Unlike LTF that had a skin and a player, this little app would be just a player and then skin itself on top of the player section. Basically a way to conserve space. This would be nice for mobile stuff. (Player with a small wrapper) (Player with a menu)

	AU 1240		Daily Ideas	5/20/2013	-I would love to add the key word “auto” to the parts department. This would auto create a part number by using the id number. -The keyword “auto” could also be used on the barcode fields for flex grid, my cart favorite buttons, and recipes. Maybe add a small tag to help us know what it is. Example: f19976 (flex grid #9976) of FAV 320 (cart favorite button #320) or RB14 (recipe/build 14). -It may also be cool if a part number could be set as a one-time usage. Basically, once used it removes itself from the active pile. There may be pros and cons to this. -If we did use a one-time usage option on parts. It might be nice to show “sold” instead of out of stock on the web or eCommerce site. -It may be worth our time to look into a cross between a big ticket stock/unit and a part number. We may need something in between. Tracked one on one but entered and sold in bulk. Some sort of hybrid item. -If we did a hybrid item, it could be entered into the part department with an auto part numbers and then the reference number acting like a generic part number. That way we could search by either. This could also be part of the onetime usage flag. -So to recap, assuming that all of this was done. Say you sold tons of items and they are very similar yet unique. They are not quite a stock/unit and not quite a part that goes into a bin or bucket. What it we used the parts department, had the system create a unique part number, used the reference field as a generic part number (same for tons of items) and then used “auto” for the barcode value. This would create unique items with the same or similar reference numbers. So, it I wanted all of my “bronze bear sculptures” I could search the reference number for “bear” or the barcode to get a specific item. I could then use a flag to flag the item so that it could only be used one. Thus, using the key word “auto” and a one-time usage flag, we could technically show tons of items that are similar yet unique. They each could be used once, have their own photos, prices, descriptions, and unique part numbers. We could even automate clean-up functions that once they get sold, they show the sold status. -I could see a usage for this in consignment shops, hand crafted items, or custom build shops. Each item is unique and needs to be treated by itself, yet sold in bulk. Each item also needs to be tracked coming in, while in inventory, only sold once, and then paid for or whatever the final process is. If the user doesn’t want to make them all individuals, they could just run it as a normal part that gets put on the shelf or into a bin or bucket. -From Post-it note: auto part numbers and auto one time usage options – basically, when used, they inactivate themselves. -At some point, we may need some bulk management tools for parts. Hide/show, web status, price changes (already done) and other bulk options. -Idea for in-line custom code… what if you could go in and detail out functionality according to types, functions, locations, and pre-filtered searches. Basically, I only want you to see this and this. You will never see this and this, and I only want you to be able to interact with this and this. This could be functions: add, edit, search, verify, lock, etc. This could be by types: only these time templates, only these PO types, only these invoice types, only these customer types, only these expense types. This could also be pre-set or filtered reports. For example: I only get to see sales from this location. I only get to see expenses from this bank or this vendor or this expense type. These are all options and criteria of sorts. Wouldn’t it be cool if we could allow companies the option to control these pieces using in-line custom code. I think this would be awesome. -Some of the ideas for in-line custom code are also part of the personal settings that may be applied per page. What if we married the two together. Personal settings could be updated and changed by a user. In-line custom code could be set by an administrator and could over rule or update personal settings. Basically, the user has control unless a setting is set by an admin and then set to a locked status. If an admin person makes a setting and doesn’t lock it down, that just becomes a default and the user could go in and change things as needed. Once something gets set and locked down by admin, it becomes un-editable by the user. It would only be editable by an admin level user. This could be two birds with one stone. AS a side note… some of the settings may be used as a one-to-many depending on the page and what it does. Interesting twist on personal settings. -It sure would be nice to have the main system player’s home pages in a graphical format. Show the options, flow, permissions, settings, in-line custom code, special reports, and training specific to the task at hand. Be it: invoice homepage, parts homepage, deposit homepage, vendors homepage, etc. -I’m starting to see a big need for the customer gift cards, in-store credit and loyalty points. Also being able to re-load, add, subtract, use, etc.

	AU 1247		Daily Ideas	6/1/2013	-“Empower the people!” -We may end up storing dates and times as integers using a modified format for both dates and times. - Modified dates could be stored yyyymmdd as numbers - Modified times could be stored hhmmss as numbers. -Dates and times already, convert to numeric values, however, they are not very human readable. If we modified and forced the numeric format, it would make the data easier to read and to search. -It may be as easy as a date/time mask and just remove the slashes and dashes. For example: 6/3/13 could be stored as 20130603 which is modified format of 2013/06/03 (yyyymmdd). Time could be the same thing. Just use military time. For example 1:30 pm could be stored as 133000 (hhmmss) which would be 13:30:00. Anyway, just some ideas. -If we do this, we will index the dates and then use them to search by.

	AU 1680		Daily Ideas	6/20/2013	-On the eCommerce section or pages – It may actually be beneficial to remove keywords and descriptions (meta tags) from certain pages. Keep it simple and clean vs. generic and non-applicable. Just an idea.

	AU 1672		Daily Tasks	6/26/2013	• Emails and tech support. • Second day of the Logan training class. We spent a lot of time on PO’s, generic inventory, services, part categories, etc. Good stuff. All participants took turns at the main computer. Lots and lots of hands on learning. Towards the end of the day, I had fun doing a demo on objects and using plates, cups, and trays. 20 miles.

	AU 2290		Adilas.biz Training Course Video Descriptions	7/4/2013	Adilas.biz Training Course: Video 3: - Small demo, photo galleries, permission and how ti effects the classic homepage, chooser, introduce the interactive map, basic navigation, how things are connected basic overview, setting your own interface of homepage. Video 4: - Dynamic templates, adilas.biz was designed to ride on top of browsers. Small shopping cart demo, Video 5: - Demo A/P waiting room, splits, adding documentation of PO or Purchase Orders, paying off PO’s in bulk, cause & effect relationships, drill-down Video 6: - Demo general inventory pool, parts and products, corp-wide settings, adding a part category, adding parts and inventory, add/edit parts, showing how items and objects show up for roll call, selling items in stock, small recipe/build demo (build & sell) Video 7: - How the shopping cart is held in the browser’s session. Hide and show line items. How to build a PO. Building PO’s, edit main, Request vs. live PO’s, PO types, incoming inventory tool, help files for every page Video 8: - Real time costing on inventory, payables, who owes who money and tracking things on the balance sheet. Changing from a request PO to a live PO. Difference between vendor specific inventory vs. generic or homogeneous inventory. Let operations lead and accounting will follow. Freight, use the PO as a tool. Light accounting logic dealing with inventory tracking. Video 9: - Overview of concepts covered, interactive map, objects and data over time, audit trail, permissions and settings, easy search-ability, bring everything together, traditional double entry accounting basic history, we track data and connect pieces together. Video 10: - Building a basic expense/receipt

	AU 1696		Daily Tasks	7/16/2013	• Went in to day one of the Denver Training event for adilas. We met at the Moose Lodge; the building was a multipurpose room (where we did the training) and a bar/diner/pool hall. It looked a little random but ended up working out just fine. We set up the class room and added a bunch of tables and chairs. David ended up bringing a large movie screen, which really helped. There were a couple of new people that came to the training. We had 3-4 online over GoToMeeting and we had about 10 in the live class room. The day started with Steve giving a basic sales demo. It was fun to watch him do that. We then spent most of the day talking about corp-wide settings, sales, quotes, invoice, etc. We covered services, generic products, vendor specific items, and PO’s. Great class. We used the world building graphics quite a bit and tried to relate back and forth between the graphics and what concepts and/or levels we were playing at.

	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 1718		Daily Tasks	8/1/2013	• Recording notes form conversation with a rep from yesterday. See previous day. • Checking images and writing an email to a contact at BATC about uploading photos and images. • Light tech support. • Research and email updates about a report request to allow all products to be matched up with a vendor even if they (the vendors) are different. This might sound weird but currently all vendor searches try to match the vendor to the PO line items. However, we have a need to search by the main PO vendor and then get any line item that matches the main vendor regardless of the vendor assignment on the line items. This is a complication dealing with generic inventories or mixed vendor inventories. • Working on the advanced PO search and adding a new main vendor search option.

	AU 1746		Daily Ideas	8/2/2013	-Adilas has become somewhat of a community effort and/or community project. I would love to keep it that way. Maybe the community and our users could help us take things to the next level. -On the permission to lock down customer to reps – we know that ideally it would work best as a one-to-many relationship but we are thinking of doing a miniature version to start with. This will be a more rigid permission. That will solve some things temporarily until we can circle down and around again. -As a side note to the customers to salesperson (reps) permission – On the one-to-many, it would be cool if we could set up limits, permission, and even do both (limits and access) based on states, customer types, zip codes, cities, etc. That would be really cool. -Also as another note on the customers to salesperson permission – It gets deep pretty quickly. What about customers tied to invoices, stock/units, elements of time, quotes, statements, etc. What about those relationships? Are they limited or open based on settings in this permission? -As soon as we can, we need to do the following: - Open up the API (application programming interface) - Add the content server (separate content from data for load balancing) - Make the system more modular and independent (tons of mini adilas’) - Finish up eCommerce (it is close but it needs a bit more) - Round two (2) of elements of time - Roll call page for all main players - Reflexive side of the flex grid -Maybe put all adilas.biz help files on adilasuniversity.biz site. I’m assuming that eventually there will be tons of different domains that serve up adilas content. It might be nice to have a standard place for all main adilas help files. -The flex grid is super cool and very flexible – However, we are seeing a need for in-line fields that may be used for parts, invoices, customers, vendors, etc. Almost a custom field level for all of the main 12 system players or groups. The thing that would make it cool is if you could name it, set the data type, set rules and defaults, and then be able to search by these fields according to data types (dates, numeric, decimals, text, and binary). The search ability by data type is super important. -In a nutshell here is what is going on. People are getting creative and recording their data wherever they can right now. They, the companies, then export the data into MS Excel and then use the data to represent different things. It would be nice to help them out. The problem comes in to play as each company is unique and may have different needs. We could add some custom fields but then it makes the whole system a little heavier. This would be a case where we would add static fields in order to increase dynamic usage. I see the need, but I’m not sure we are ready to jump yet in that direction. The ideal would be to allow for unlimited dynamics and allow for those changes to happen and flow within the bounds of the system. This is custom, yet in-line, and fully allowed; that could get kind of tricky. -Another piece to the custom and in-line code is getting each corporation or world by itself. That makes the custom fields weigh less because they only apply to certain worlds and/or corporations. The trick there is updates and changes. If everything is custom – how do you update pages and features. It kind of comes back to in-line custom code. Basically, we know it needs to be custom so, plan for custom right off the bat. -All of this talk about in-line custom code makes me think of settings and permissions on an almost page level. This could be clear to the – use this field, call it this, require this, search by this, and have it show up here and here and here. Basically, this is the default outline, layout, and pre-set settings. If you want something different… you need to play at this upper admin “tech” level. Then you could do custom right out of the box. We aren’t there yet… but I can see it down the road in the future. -Two huge keys are: 1. Centralize the data 2. Catch the data -If you can get to that level – the rest is all possible. Those are the two things I see as paramount! -The deeper we go, the more we see things headed to “world building” and “virtual world building”. -Sometimes I get so excited recording notes and ideas that it is hard to pull back and do the work. Maybe I could become a professional daydreamer! -This is kind of silly – we say that our biggest competition is “tradition”. We also say that eventually we will be used to train our competition. What if we end up training people how to overcome tradition? Anyway, I thought that is was kind of funny. -The assembly line really helped out businesses. Things were done overtime and then passed on to the next step of the assembly line. Adilas does the same exact thing with your business data. Things are done over time and then passed on to the next step. Pretty cool! -I’d like to make a graphic and show how businesses use different assembly lines. It would then be fun to show how adilas uses similar processes to link and connect data together. -This is an old analogy we used to use for showing flow (graphics/sketches for each): operations and accounting - both perfectly in line – static. Operations and accounting – different things happen over time but they come back together – dynamic. The new analogy may look something like this – once again relating back to an assembly line – type analogy: operations and accounting – different things happen over time but they come back together in order to pass the checkpoints. Or another analogy that fits this flow is a bottle of data flowing down the river. As it flows (through a virtual assembly line) it passes certain checkpoints. My daughter even drew me a graphic for this. Some of the key elements are: 1. Enter once 2. Use over and over 3. Run it over time 4. Checkpoints help maintain flow 5. Checkpoints may be permissioned if needed 6. Track the entire life cycle.

	AU 1733		Daily Tasks	8/19/2013	• Product upload for a company. Ran into a problem with the part numbers being too general or generic. They were note unique and the data file had a number of duplicates. • On the phone with Steve going over different ideas and going over questions and current projects. We talked about interns, projects and transitioning into a different system of charging for custom stuff. • Creating a number of custom pdf’s for some contacts down in Colorado at adilasdata.com. Sent the custom pdf’s to one of them that attended our last Denver training session. • Reviewing an email from my brother about Ted talks at ted.com. Some fun stuff there. • Prepping files to create a cross venture with an email and text messaging company called Full Circle Interactive Media. I sent them some sample data and a sample API method call. The email also included some other security specs and ideas. • Working on a custom project for a teacher and tracking her students using customer’s and flex grid as core curriculum data points. • New logo and wiring up custom homepage and interface options. Using my brother’s custom graphic as an image map for the teachers. Wiring up the graphic and overlaying buttons for the teacher interface. Fun and good stuff. Small tweaks to underlying pages to pass correct variables. • More wiring up the graphic. I’ve been making lots of underlying page changes to allow things to be detailed out.

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

	AU 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 2141		Adilas 3 Day Training Notes - Denver	10/24/2013	Day 3: Oct. 24 -Think of adilas like a game... cause & effect, cause & effect... -P&L - runs over time; B.S. - snapshot in time; main players on the P&L - Revenue, COGS, Expenses -Revenue: more so what you are going to be taxed on... from Mick - the transfer of goods or services at a price.... so invoices (an investment would go on the balance sheet but it would not be inputted on the P&L -Henry Ford and the assembly line --- adilas ---- Adilas - a new tradition. -Adilas - so user friendly, so accessible --- and the connectivity is INVALUABLE! -Peachtree, QuickBooks. (Traditional accounting systems) are numeric or alpha-numeric systems.... whereas adilas is more an alpha system... much easier for the user. Also a traditional accounting system is a T-account or flat... whereas adilas is a multi-dimensional, mobile system... also units of measurement already built in to the system... incredibly enjoyable -Paul said this a cool way... with all of these worlds are stories so often they invite us into their world or for the story we experience things in "their" world, come into my world. But with adilas, it is... "What is YOUR world?"... Because we are here to help you create your world. How do you want to play? How can we help to build your world and help it to function? -System Assets: think monies you are bringing in, monies in; System Liabilities: monies, monies going out -Reiterate some of the small things when setting up... because often people get overwhelmed just b/c it's all new and you forget how and where or for instance things coming in... all need to come in on a PO for example... -Funny, but true, Roxanne says anyone that has done shopping online can do sales in adilas.... they might need some training and guidance for other functionality like adding in inventory, or doing accounting... but for sales, it is very logical and user friendly The edit ability of adilas is a huge asset or benefit of using the system! Whatever you do outside of the system... do inside the system! -With verifying deposits and expenses... if they have been verified but they are wrong, you can back it up and actually un-verify it, then you can add/remove items... then you can go back and get things correct and you can verify it... a good way to back up if you made that mistake.... -Check your homepages so that you can see what you've been doing... sometimes people add so fast or use the back button and end up adding a whole bunch... so it is good to monitor and care for things.... Best practice: add things only once... then edit, edit, edit, whatever you need.... if you tried to add it, you might just need to search for it or figure out where to find it. -Verifying things... is such a great way to basically check done... to say yes, this is correct; I authorize that to move forward...... (On a PO, the specific verify date is not as important as the Expenses and Deposit verify dates... that is very important on those last ones) Idea/want to have: the ability to divide payments on expenses... or on paying off PO's with partial payments (divide payments like applying payments for our customers) -Creating actual objects allows for multi-dimensional relationships... it simulates and/or tracks what really happens in the world... with time, relationships, story, etc. Don't be afraid to start playing... even just start with what you can start with... you can circle back around and edit if needs be, or teach the next step at the next time, etc. *IDEA: from Uri, asking if we had thought about QR codes/swift codes for sending direct transfers, especially for those that are sending huge amounts of money to people IDEA: Quick exports to Excel... any page, any data... again from Uri -You are able to pull all sorts of data and reports from adilas... but you do have to know where to find it.... -adilas and others will sometimes trick out the system just a bit & put in a $0 expense to track their monthly bank statements.... so that they can have a holding place, attached to their vendor and then upload all the photos for their bank statement... so that they can document that along the way as well ***IDEA: a box on expenses that you can say how much you would like to pay, as noted earlier... that way it can help you calculate and do the math... -Splits allow for partial payments... but reimbursements do not allow for partials... so if you have a unique situation, you may need to play accordingly -I personally need to have a better understanding of items like equity, capital, user-maintained balance sheet items (the running, assigned, etc. what are the differences in those options, what does it mean?), (Learn what feeds automatically and what needs to be manually entered... and what situations), P&L statements, payroll, payroll taxes --- really just how a lot of the accounting works.... liabilities - loans, company distributions, assets... (So many places to get to this information... many great resources for understanding these processes... Shari had specifically been talking about payroll) -Other content bucket: local - is it on my C drive, F, my docs, etc., etc., etc. Remote - your YouTube account, google drive, sky drive, etc., etc. for both of these no costs just referencing to these files. Physical: pushed up to adilas servers and retrievable from adilas servers... that one they will have to charge for because of the space and potential file size.... but this is going to be SO neat! Really, the possibilities are SO immense. What kind of content do you use, what do you want?!

	AU 1865		Daily Tasks	11/21/2013	• Got an email from a client. They just added six new locations and needed some merchant settings applied to the new locations. That is exciting! That brings them up to 44 locations. That is awesome! • Add a new logo for a client, my brother did the graphic. • Reviewing an online eCommerce video that we put up on YouTube. • Rereading code for eCommerce. Signing off on code. Working on a more generic customer sign on. The old way was pretty tightly tied to a valid shopping cart. The new way will be a little bit looser to allow both existing customers and new customer s to access backend options. Security will still be tight for customer actions, just the gathering of information will be relaxed slightly. • Went in to Bridgerland to work with the interns. I did a small eCommerce demo showing actual invoice creation and payment stuff. That is a new feature. My sister then did a demo on the flex grid and how to use it. We spent an hour and 3 interns had a blast playing with different pieces of the puzzle. Great session. After that, we worked on the advanced search page for the media/content application. Another lady helping with some projects came by and we showed her our progress. 30 miles. • Talking with this lady about the “dream it up” graphic. That little graphic says a lot about what we are trying to do. We also talked about a possible project that she would like to do for her current boss and how they train substitute teachers. We then talked quite a bit about custom interfaces and how the word “interface” also or almost deals with the word “space” or “work space” or “flow”. That was a really fun conversation. She gave me a disk of files and I got her paid up. • Recording notes on time and space and how interface plays into the space part of the puzzle. Cleaning up computer stuff and heading home. • Went to Smithfield to work with my sister and brother. I got 11 new videos from my brother and we talked about getting him a new laptop so that he could work from home. I then worked with my sister on what we wanted from the adilas user guide. We talked about using her own words, Steve’s stuff, and my help files to come up with a rough outline for the user guide. • Uploading new video clips to YouTube. Light file management and pushing up the new files.

	AU 1898		Daily Tasks	12/12/2013	• Checking out new servers. Ordered three new servers. Talked with the sales rep, reviewed quotes, and went ahead with it. Exciting! One new media/content server and two new data servers. Also ordered 5 new domain names for future data servers. Emails and tech support. • Went in to Bridgerland to work with the interns. Brainstorming with interns on server layout stuff. Lots of drawings on the whiteboard. We talked lots of concepts. Talked about objects and data over time and how to speed up processes. We talked about splitting databases, indexing numeric dates and times, and cloud structures and virtual load balancing. We need to plan for media/content servers, data servers, databases (clusters), and then corporations with in the databases. Light research and talk about existing cloud structures and how they handle similar pieces. Still leaning towards our own manual load balancing and cluster models. 30 miles. • My sister came to Bridgerland and taught us a great class on concepts of mixing and blending and making objects. We started out talking about PO’s (purchase orders) and what they need to take or allow. No specific order, just brainstorming and listing pieces. We then talked about chocolate chip cookies and what it takes to make those. We talked about timing, processes, and even checkpoints. We then talked options and how adilas allows for mixing and blending and tons of options. Great comparison between the two things. We then took it a little farther and started talking about options, choices, and flow for invoices and shopping carts. Tons of cool cross over ideas. The whole session or class was a whiteboard discussion of sorts. Good stuff. At the end we talked about allowing users and companies the option of organizing processes and space to be more efficient. This could be more in-line custom code, new settings, sub classifications, or custom processes and /or virtual checkpoints. We talked business mapping and using an application flex grid. Great session and good participation. • Recording notes on what happened today. Exciting stuff! • Emails.

	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 1958		Daily Ideas	1/13/2014	-The flex grid tie-ins are very helpful to record extra data. This is an idea that will help and expand upon those already existing options… What if we, on purpose, added extra fields, to the main application types or system player groups? For example: Deposits, Invoices, Expense/Receipts, PO’s, Parts, Customers, etc. What if we added extra flex fields to both main and line item tables? - Main flex text fields from 1-5 or 1-10 or 1-N - Main flex numeric fields, 1-N - Main flex data fields, 1-N - Line flex text fields, 1-N - Line flex numeric fields, 1-N - Line flex data fields, 1-N -The text fields would be up to 255 characters (default 100, 150, or 255). The numeric field would be signed (+ or -) with two decimals. If we built them in a way that they could be turned on/off at will, that would be cool. It would also be cool to be able to name them, search by them, and even allow for custom output options. This would take some work, but build in the flex text fields as part of the main application. As a note, let the database control the application through settings, permissions, and assignments. I know this is a lot, but think master templates, point and click assignments, and sort of base things off of elements of time and master time templates. -Vendors and users need a log page. We are seeing a need to be able to log vendor and user stuff just like what we do with customers. This includes, log notes, follow-ups, additional contacts, etc. Basically CRM (Customer Relation Management) stuff for vendors and users. That would be really cool! -When adding time to cart… Maybe stick to hours instead of converting to days. I guess it depends on what you are billing for but hours seems to be the best option. This issue came up as we added just over 24 hours of billable time to the cart. Instead of showing 24 hours and a decimal portion, it showed 1.02 days.

	AU 1949		Daily Tasks	1/28/2014	• Went to the first day of adilas training. We held it in Denver, CO., at the Moose Lodge. We set up tons of tables and chairs, set up computers, printers, scanners, etc. We had 20+ people at the live class and another 10-15 online through GoToMeeting. We did some introductions and then started in on the training course. We had a number of clients that were from the MMJ industry and the training definitely had that flavor. As part of the training one of the ladies who is going to help consult for adilas helped answer tons of questions. She did some adilas training and also some MITS training. MITS is a site that requires the MMJ industry to record certain state required fields. It takes tons of work for the users to record the data in both places. She did a great job and many of the users were very thankful. Another thing that we covered a lot was generic items, special PO’s, and global find and replace functions. We got some great ideas and really enjoyed helping the people. Great class and good participation.

	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.

	AU 2033		Daily Ideas	2/13/2014	-An intern and I talked about the check-off or sign-off process for code. We determined about levels… (Little sketch on notebook page – see scans in photo gallery) Scratch (testing & development) – Sign-off (line by line, try to break it, check everything, details) – Approval – Use or Deploy to the full adilas system During the sign-off phase… We need to: - Check structure and layout - Spacing, tabs, aesthetics - Comments, documentation, hints, and tips - Code and verifying logic (try to break it) - Spelling, output, results - Check for useless arms (like a T-rex) The intern then boiled that down into: - Backend, coders, & maintenance – (nerds & techs) - Runtime & execution – (computers and servers) - Frontend & users & output – (users & people) & (Web & API – (unknown usages)) -Use elements of time for classes and training. We could use the calendar, the notes, the types or colors, the photo gallery, and soon the media/content section. The other content could be agendas, links to video recordings, and any other handouts or documents that are used. It will be cool to put and keep everything all together. -This is an idea that I had years and years ago but I’d like to record it again in part… I would love to use adilas as the backbone tracking software for a multi-person, multi-company challenge that has different people or groups try to build new hybrid engines that use 10-12 different forms of energy. Basically, set the rules of the challenge, set-up a prize for the winners, and then use adilas to track the whole process from start to finish. This would be all the inventory, expenses, draws, deposits, elements of time, events, photos, scans, documents, etc. Part of the game would be that they, the participants, would have to use adilas and report their progress and findings to the world through updates and documentation. Run the contest for a year and even help cover the different teams through video, TV, or something to help document the process. One huge key is that all of the findings and ideas would become public knowledge. Help push the ball forward. There are hybrid engines or energy sources out there already… what if we brought them all together into a multi-hybrid system. The contest would be on the toy or smaller level. Once we work out details and ideas, we could then take those ideas to different bigger industries. See other notebooks for other ideas. -My sister did some great training on permissions and settings. She made a small Word document with the ideas all laid out. Maybe think of ways to break the permissions and settings into smaller subjects, topics, and categories. If we could take it to a visual level, that would be awesome. Maybe think about the adilas map or the GPS core layout graphic as the visual top level layout. As a note, the first part of March 2014 we started to change our approach… Permissions and settings are tools to help with custom usage and custom functionality. Maybe focus more on the outcome vs. the tools. -As we get deeper and deeper… Maybe start using elements of time as our own social media venue. It could be like combining Twitter, Facebook, and LinkedIn all in one. This involves people (vendors, users, customers), logs, photos, scans, media, other content, events, dates, notes, sharing, etc. In a way, that is kind of our plan with adilas world, adilas university, and adilas in general. Adilas = All Data Is Live And Searchable! -Along with the idea above about using adilas as a social media venue… what if we could also combine other pieces of the puzzle such as links to their personal websites, calendar events, eCommerce, history of interactions and transactions, etc. Bring things together. This could be frontend, backend, sales, support, availability, resources, options, etc. When you start talking systems or system thinking, you really start bringing things together. -Think about the movie “Up” from Disney & Pixar. Maybe do a virtual commercial to help tell the story of what is going on and growth that has occurred. There is a fun section in the movie “Up” where it shows a story and no words are used for 5-10 minutes. In a quick way, you get familiar with the story and the characters. I would love to do that to help users understand that adilas has grown up from a baby to an adult and is still growing. If they, the users or investors, understand the history, it will help them see the vision and potential of the future. We could use this to help sell or pitch ideas, recruit help, raise awareness, and even solicit funds to help fund projects. I love the concept of using history and cause and effects to tell an unfolding story. -As a side note, my brother did a historical recap of Bible stories and events and brought them forward into current events. He did this as a number of us were sitting around a picnic table during a family BBQ. I was totally captivated by the story and seeing how one thing created the next and the next and the next. The deeper you get, the more you could see how the cause and effect consequences both made the story and even helped feed the next steps. Very interesting. This brother is a master story teller and loves mixing history with current events. Great skill to have! -Tools are created by people to help them do a job. Some tools are designed for both good and bad. Some tools are very generic and may be used for both good and/or bad. Imagine a hammer, a saw, and a drill. These same generic tools could build a church, a school, a house, or something for business. These same tools that build for good, are also used for destruction, war, weapons, and vice/sin. These tools aren’t bad… It comes back to the agency of the person that uses the tool and what they intend… Adilas is a generic tool. I hate to say this, but it may end up being used for various different outcomes. The tool is generic. The usage depends on the users.

	AU 2034		Daily Ideas	2/15/2014	Notes from a phone call with Steve on 2/15/14: - On funding, we are looking for a loan. We are trying to steer away from investors and looking for a possible loan. Maybe offer 10% to 12% on interest. - We could also allow our clients (top paying or longest clients) to pre-pay with a discount applied. We may want to limit this to clients that have a year or more time with adilas. Maybe 10% for 6 months pre-payment. 20% for 1 year pre-payment. 25% for 2 years. 30% for 3 or more years. Kind of like a season pass for a ski resort. They (the ski resort) get more capital up front and the lifts (servers) are going to be running anyway. Notes on packaging or packages (sub of the parts section). - Maybe add a 3rd item type. Other two are serialized items (stock/units) and general items (parts). The 3rd item type might be a sub or baby of a momma (either stock/units or general items). - Keep the naming conventions as dynamic as possible. - Maybe change “parts” to “items” at the top most level. This is clear up at the top level or 12 main system player groups. - What if this 3rd item type was able to handle outside services, job costing, packages, subs of the main, etc.? That would be super cool. - Conversions could be part of this sub or 3rd item type. - There may already exist some ideas and notes on “mini units”. This is an older idea but may have some ideas for what we are trying to do. Mix between stock/units and parts. - Package control – helping, watching, and monitoring. - Stock/units mixing with packages or element of time to get RFID tag tracking, job costing, and subs of subs. - Lots of new 1-many relationships. - Round two of elements of time deals with payroll options, rentals, reservations, job costing, clear to the any person, place, or thing level. This could be to a dispatching level on elements of time. As a note, there are tons of notes on what we wanted for round two of elements of time – check out old notebooks and brainstorming pages. Look in early 2011 for details. - Track the “time” related to packaging. - The 3rd item type may be done by taking an existing item and creating a one-to-many relationship from it to a new group or package. -We are heading toward generic corp-wide settings. We could then bulk change these settings based on different industries. What is your industry? Can we help you setup some common features, settings, and interface options that are used by people in your industry? Help our users get the most out of the system by using settings and permissions. -Steve and I were working on building some new corp-wide settings… As we went through the process, we came up with a few key points to help us get started. They are: start with ideas and needs. Then do some planning. Then make new database changes. Go to the source of where things start. Build the settings, then actions and updates, and then cascade the new settings as needed. Finish up with sign-off and deployment of new features.

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

	AU 3673		Brainstorming - Parts & General Inventory	2/26/2014	Brainstorming on parts, items, and general inventory items. Done on day 2 of the February 2014 adilas training session. 2/26/14 Inventory: Goals, Features, Advantages, Benefits, Pros/Cons, Known/Unknown, Shortcomings What do we know? - PO’s – inventory comes in on PO’s - Vendor specific inventory – perfectly tied to that vendor, its own special… - *Generic inventory* - purchasing product from multiple vendors but selling it out as the same product or at one price, (if it’s going in a bin, same shelf, mixing, etc., run it as generic) - Different types of PO’s – 6 - In inventory, on order - Unit of Measurements – lowest common denominator – what are you selling it out at - Include/Do not include shipping in COGS - 5 decimal levels of accuracy – not required, but available - Cause & effects – payables, affecting inventories - Get it in – PO/inventory side – then we will pick it up on the Payables side – who do we owe? - Barcoding - RFID tags – Radio Frequency Identifier (higher cost) - Packaging - Potential backorders - Pre-ordering - Pay before receiving product - Shipping - Freight – different on financials than inventory pieces - Mini-manufacturing – making new products, buying in bulk – selling in singles - How am I selling my products out? - eCommerce - Open up brand new markets - Allow online bill paying - Recipes – bulk, group, kit, pre-set, flex… - Multiple pricing structures – tiered pricing structure (i.e. same item w/different pricing) - Interface for selling advanced add to cart, buttons, ??? - Services - Unlimited items - Migrating – find & replace, combining items - Data imports - Global mark-ups - Sales - Discounts - Promotions - Customer loyalty - Merchant processing - Gift cards - Planning – faster, consistency Shortcomings/Pains: - When to order? - Loss/shrinkages/damages/returns - Potential volume of inventory – can be really challenging to manage - Tradition, legacy, how it has been done - How will I enter everything into the system? - Lots of work getting inventory in… - Pro/con: Taxes - Education/training - Pro/con: Planning - Expiration dates Brainstorming on stock/units: Flavor of stock/units What do we know? - Serialized - Big ticket items - Individual Needs/Level – needs some love – what happens to THIS item - One by one - Vehicles - Trailers - RV’s - Campers - Planes - Boats - Buildings - Hotel/Rentals/etc. - Homes - Motor sports – motorcycles, sleds, rhinos, 4-wheelers, etc. - Firearms - Jewelry - *Jobs* - Job costing - Can contain subs - Can be sold - Sub buckets - Job histories - Can be tied to locations – tracked to different locations – mobility - 5 deep level categorizations: o Inventory type o Sub inventory type o Make o Model o Physical unit (with additional subs) - Sales tool – with some “haggle” ability built in – cost variables - 100 photos per stock unit - Manager’s checkbook – slush fund - Fictitious costing - Somewhat fixed items - Mixed items: almost between serialized & non-serialized items - Not a standalone item on invoices - Wholesale & manufacturing of stock/units - Stock units that product other stock/units – (manufacturing, harvesting) - Very powerful, very diverse, very functional - Documentation – media content, unlimited documentation, not just photos – add the design specs, the paperwork, contracts, etc. - Rentals – (stock/units to elements of time) - Reservations - Needing to attribute subs to individual pieces - Details – main What is possible? Features: Advantages: Benefits: Shortcomings: - They are big - Require a lot of data if you really want to play the game - Time intensive to sell – paperwork, financing, trade-ins, contracts, - Human error – to help with this, making things editable & tracking histories - Search multiple buckets – to get your data back out (pro/con) - Economic downturns – big ticket inventory can become very difficult - Education/training to be able to work with complicated/detailed items – associated permissions - High entry cost to serialized units - With more stock/units – potentially requires more people/space – money, employees, security - Taxes and random settings - Paperwork

	Adi 846		Expense Favorites	3/7/2014	Working on favorite expenses for the trucking industry and thought that adilas needs expense favorites that we could park on the search_receipt_payee.cfm See the American Trucking play site homepage. custom_trucking_home.cfm I'm thinking of an image tag that when clicked will push the vendor id and the chart of accounts id to the add_edit_receipt.cfm This way we could also use these buttons anywhere such as a custom interface for payables, or any page (in the future) a client desires.

	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 2130		Adilas Team Meeting Notes	4/25/2014	APRIL ADILAS TEAM MEETING NOTES: Friday April 25th -Do we need to reach out near the end of the year to help clients be reconciled and in balance? That may be something we need to think of, so we don't have panic mode from anyone at the end of the year. -We need some sort of setup help, education and training for all new clients. Setup and training - set people up for success. -Hands on time with clients to help them get up and running. -We need to come up with some specific training for .... -Industry specific training sessions??? -Would it be beneficial to have a place to setup and have people there - an open forum type setting to help clients. -Or do we need to offer custom classes and charge per seat? -Adilas training store - adilas training center - even like a little space in a shopping mall, you could even have hardware, POS system plugins etc., and have the opportunity to teach classes, have one on one, consult, etc., etc. -We also may need to put up a list of things we recommend to plug and play with - to help filter some of the questions -Our current model is that we are kind of trying to do 3 jobs - consulting, training, and sales.... everyone doing all of the jobs -But maybe our new model needs to be something more like: consultants, sales, and training all as different jobs/aspects -Project management for custom code and future projects - moving to some sort of an approval process -Washington DC Payroll taxes - we need up next - already funded - project going to a developer who has already been working on payroll taxes -Industry specific custom interfaces - there is a need for that within industries - we still want that flexibility and ability to create a generic option to use throughout that industry.... but it would be great to make custom interfaces and custom code projects per client - because that is where the need really is -API interfaces - having clients fund the projects - maybe even a standard customization per industry and then the option for custom interface, custom anything per client - that they pay for -Developer's Queue - put it in the system, they can even self attribute themselves there, funding from the clients, approval process, submissions, etc. -Custom training - -Internal projects (which we internally prioritize, etc.), industry specific projects, custom projects per client specifically -Adilas World - an internal project we may need very soon -Custom interfaces, etc - Craig had a great analogy - he was saying you buy a car from a manufacturer - core adilas - what we do. But it is like taking your car to a custom car shop and getting custom wheels, custom paint, custom etc., etc. The client is still paying monthly payments to the manufacturer (adilas) but they are also paying money for their custom pieces (developers). -Adilas fee for adilas world - subscription for adilas world -Users group - crowd sourcing funding, participate in the users group for the development of new features which the user group prioritizes. But you could also have them fund it, or it could dictate when you have enough people that are willing to pitch in to that project and when you finally have the funding there. Then that project can start being worked on. -What do we need to help adilas clients succeed? -What do we need to do to map it out? To help them understand and accomplish what they need? -Consultants - hourly + commission -Sales - need a bird dog fee + a piece of the commission -Training - right now is free - it needs to be part of the product - it has to hold hands for it to work -Training Center - fund a client training center from a certain amount of the monthly fees for the client center - basically a new expense for adilas to help pay for the training that needs to happen (a certain % from clients in that area) -If they pay for the product they get the training - training center - this is probably better for training all around - it is hard to train someone at their place of business. The training is free but they are still responsible for getting themselves down to the training center - but it is there for them to access for their training -Training for that town or area - someone that could pick that up for that area -Certifications for our training - to an adilas standard - but get someone that can help setup that training center -We need to come up with some kind of a model that works in these metropolitan areas for clients to get in and get the training they need and be able to accomplish that -At some point we may even get to where we have a center manager that adilas pays -Advertising -Enterprise tools for pennies -It would be great if we could dial in on some of these distinctions between sales, consulting, and training, etc. -Because our prices are so affordable - it creates a barrier to entry for others - so how can we help get these people trained and supported so that they are successful? -Incentivize clients bringing on other clients and sales, or potentially a season pass approach, 10% off when you pay for your year up front, etc. -Hosting & processing fees - so basing all of the pricing off of hosting, storage, etc. So really basing it on user use. -We win with volume -Funding future projects - is it time to draw a line in the sand? And projects from here on out, do they get funded? -We need packaging/batching - and probably very quickly -Price tag & pledge for upcoming pieces - that way the users/clients can really help dictate what they want by what they are willing to pay for -Also show the customers what the whole price tag really is for that - but then say we will lift off after "this" amount, that way they also see how much input and development really is involved, and they may be more willing to help and input pieces to contribute to the process -Packaging, Batching & Package Control, Conversions, Actual Costing/Pricing - these are all part of that packaging piece -Queue - Content server up in the next week, then Adilas World & with Adilas World bate the first project with a $5,000 price tag for packaging - that is the order/plan for the next couple weeks -To do list: Content Server Adilas World Packaging - batching, conversion, actual pricing, quick search, Discounts -Adilas stores - training centers - if we can get the right person in some of these training centers - someone who can see the vision -Additional training - free training -If we could get to the point where some of these training centers are funded - that would be so fantastic, really helpful -A lot could happen if we could get some training centers up and running -Categorizing training that we already have done - categorizing and summarizing for easy use of the training videos -Adilas University could be the leader for these training centers - training the trainers -Hey I want to be the adilas university of - Chicago, Denver -What if we even sold the adilas university as a franchise??? -You get it, you run it, but you must meet our certifications and our standards, you pay to get this setup, maybe you can get funded again from client base in that area -Setup with a consultant/training - like Shari that can really help them get up and running correctly -When a new person comes on - see if there is an offsite place we can meet or someone that can take care of your business so that you can meet them elsewhere so you can get some focused time on adilas -Even a day can just help get the clients started and going in the right direction -Start off with the right principles and practices -Take the time to set things up the right way and get them into a position where they have the ability to run and move forward -Setup/consultants, but we also want to have bookkeepers or someone that we could pass some of these clients off to, so they can help run some of these things for clients. That way key players can unload some of their plates.

	AU 2330		Daily Ideas	5/9/2014	-We had a request to help transfer my cart favorites between users. So, what happened was, someone setup all of the my cart favorite buttons. That person doesn’t work there anymore and now the owners want to transfer ownership of the existing buttons to someone else. Interesting twist. -As a note on my favorite buttons… Maybe allow them to be generic or unassigned. This would allow anybody with permissions to update or edit the unassigned buttons. This would allow for generic corporation buttons vs. just “my” cart favorites that are only tied to one specific user.

	AU 3700		Brainstorming & Tech - Elements of Time	8/1/2014	Adilas Versions: - 12 years of progress - 8th version - Info graphics per year – 2001-2014 (See scan in photo gallery for sketches) Versions: 1. Inventory tracking system – Locations, employee/users, and stock/units (serialized inventory) – big ticket items 2. 3. 4. 5. 6. 7. 8. World Building -Base Camp -Anchors Versions: - Description/Features - Time 1. Version 1: 2001-2002 (?) - Inventory Tracking - Stock/Units or Serialized Inventory - Multiple Locations - Employee/Users - Role Based Permissions - Digital time clock 2. Version 2: 2002-2003 (?) - Full & General Inventory - Parts Department – General Items - Basic Inventory Point of Sale - Vendors, Purchase Orders (PO’s), parts, items, services, quotes, tax settings, invoices, and customers 3. Version 3: 2004-2006 - Payroll Reports, Commission Reports, & Withholdings - Stock Units - Floorplan app - Photo Management for Stock/Units - Web Presence for Stock/Units 4. Version 4: 2006-2007 – Full Rewrite - Full Rewrite with a New Base of Permissions & Settings - Changed from MS Access databases to MySQL server database - Banks, Expenses, Check Write System, Deposits - Invoice Rewrite to Open to Both Stock/Units, Parts, & Services 5. Version 5: 2007-2009 - Accounts Payable - Accounts Receivable - P&L – Income Statement - Balance Sheet - Officially Started Up Adilas (6/2008) 6. Version 6: 2009 - Merchant processing for credit cards - Recipe/Builds - Introduced corp-wide settings (custom naming conventions) - Web presence for parts & general inventories - CRM functionality & customer logs - Flex grid tie ins - Customer paperwork & PDF’s - Reoccurring invoices 7. Version 7: 2010 - Major work on corp-wide settings - Security settings tightened - Lots of new POS (Point of Sale) features such as o Barcode printing o Receipt printer invoices o Inventory ordering process o Dewy decimal – up to 5 levels of decimal accuracy o My cart favorite buttons – custom o Units of measure o Sales & profit reports o Advanced add to cart 8. Version 8: 2011-2012 - Elements of time – Calendaring & Scheduling - System designing & layout pieces and how they all worked together - Interactive map layout - More work on my cart favorites and other POS functions - System refinement - Customer queue - Smart groups and tiered pricing structure - Enhanced barcode search capacity - Duplicate PO - Choose interface options - New custom homepages 9. Version 9: 2013-2014 - Custom code & custom interfaces - Industry specific tweaks & charges - Built-in eCommerce and full web presence - Tons of new settings & permissions - Tons of training both online and live classes - Introduced World Building concepts - Lots of new flyers and graphics - Hired college interns to help with custom code projects - Over 100+ hours of training captured and edited - Lots of new YouTube videos - More icons & buttons - Added additional photo galleries for all 12 main system player groups - Migrated to multiple servers and further defined world building levels and definitions - Added full media/content (file management stuff for PDF, spreadsheets, word processing, graphics, images, video, and audio files - API sockets - 3rd party vendors - Custom code Update note: this was lightly recorded into the database on 9/20/14. See elements of time #873 in adilas or #2777 in the adilas university site. Recorded on 9/20/14. Elements of Time Homepage Params FORM – URL – Defaults - Action status id o Action status • 1 - Assigned to id o Assigned to • Normal id = x + 0 = all, 1 = unassigned, 1,id = unassigned plus me - Block size o Block size o C-W • “ “ - Color value o Color value • “all” - Created by id o Created by id • 1 - Customer filter o Customer • “All” - Daily date, FORM time period = 1 o Lots of if statements to refigure FORM o Me period = 1 • “ “ - From date o From date • “ “ - General title o Title • “All” - Monthly date – 1-12, FORM time period = 3 o If blank set to current • “ “ - Monthly year – FORM time period = 3 o If blank set to current • “ “ - Quick jump date • “ “ - Quick jump frequency • “ “ - Quick jump value • “ “ - Report type o Group o Calendar o Details o Time slot o Type – required if going URL o C-W • “ “ - Show group subs o 1 = show o 0 = hide o Show subs o C-W • “ “ - Show logs o Yes = show o No = hide o Show logs o Run extra cfc • “yes” - Time block end o Sample – “5:00 pm” o To time o C-W • “ “ - Time block frequency id o 2 = sec o 3 = min o 4 = hours o Block frequency o C-W • “ “ - Time block size o Block frequency size o C-W • “ “ - Time block start o Sample “8:00 am” o From time o C-W • “ “ - Time period o 1 = daily o 2 = weekly o 3 = monthly o 4 = custom o Defaults are 1 & 4 o C-W • “ “ - Time template id o 1 = all numeric o Template • 1 - To date o Used with from date o To date o FROM time period = 4 • “ “ - Weekly dates o Filled if blank o “start date, end date” • “ “ Time #2773

	AU 2811		Daily Ideas	8/20/2014	-Idea from my sister: As we start making adilas more and more a self-serve model, include the reps and consultants as the next level of automation and permissions. Let them get in and setup things. It is already headed in that direction, help feed things that way. -Maybe allow a request from a cluster to the upper galaxy and universe levels. That might be a cool option. Think of going up and down the chain of command. -On this new database copy project... Level 4 database or create new solar system project... Maybe use the analogy of a bus (older shared table structure) as compared with a motorcycle (newer, smaller, quicker table structure). Another one might be a raft vs. a kayak or a space ship vs. a smaller speeder or something. We are hoping that it will make that big of a difference. That would be cool! -”Teach them correct principles and let them govern themselves.” -Joseph Smith. Great council and advice. -We had a request to record shopping cart history. This is virtual memory. I can see a need for start, stop, save, create invoice (checkout), or clear. All other actions get into a micro management issue. It has got to come back to good principles... -When ready, we need to index main dates to numeric values. We also need to push date/time stamps out to hours, minutes, and seconds. Once we start to index that, it will be awesome! As a note, look-up numeric dates on adilas university for more info including numeric day of the week values.

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

	AU 2816		Notes from an Intellectual Property Workshop	8/21/2014	INTELLECTUAL PROPERTY WORKSHOP Conference on Patents, Copyrights, and Trademarks -Creative act of the mind Copyrights: www.copyright.gov -Literary, musical, and artistic works -Physical, it has a life span, only covers the expression of the idea – not the idea Trade Secrets: -Formulas, practices, processes, designs, instruments, patters, or compilations of information – Have to have controls in place to keep it a secret Trade Dress: -Visual appearance of a product, its packaging, retail environment -Aesthetics - Look and feel Patents: www.uspto.gov -The concept, inventions, designs, plant, functional -Termed or time based – 20 years from date of filing -Utility and design – utility means useful -”Fair use” doctrine – make sure and site your sources. Trademarks & Service Marks: -Symbols, words, phrases -Be careful – if it becomes a generic term it could be over -Make sure and search first -Cost benefits and cost of protecting your intellectual property -Be proactive and do training on intellectual property -Patents – use a professional to help you -Patents – usually take between 3-5 years to be fully done Patents & rejected patents: -Prior art -Already printed publication -In public use -On sale or for sale -Or otherwise available to the public -Obvious or too general -These are things that we could do to protect future patents on stuff we are doing Trademarks: -Possible problems with consumer confusion – too close to another existing trademark -Instead of trying to help everyone... We need to focus in on our customers that are using our system. Keep them good and happy. Other customers will come. Focus on what we've got! -If you want to get something fixed... Have the person who built it use it for awhile. It will most likely get fixed pretty quickly. Kind of funny! Nobody likes to use something that is broken or hard. If the builder can see those issues, they will most likely fix it!

	AU 3712		Planning - Pages for Building New Corps/Worlds	9/16/2014	From a Post-it Note: (9/16/14) - Universe - Galaxy - Cluster - Solar System - World - Payees - Usernames could be unique - Solar System payee status Planning out pages for building new corps, worlds, solar systems, and clusters: Tracking the current login process: Top secret index cfm: Corp key id (passed or entered) – alias or traditional XYZ-0014: - If on the master cluster check the master corporation list - Else check the corporations table Top secret login action cfm: - Currently only username and password are pass in o Payee and time zone check - Check the number of corps o Single payee id number check o Corp & permission check o Looking for one or more matching corporations - If single corp assignment o Do another payee to corp to permission check o Grab quick search options o Grab corp and tax category settings - If single corp assignment o Grab all personal settings including default homepage o Set session vars - If multi corp assignment o Set generic session vars & send to the corp chooser page - Record the login history for the user Extra Page: - Top secret look up corp key cfm o Username look up o Payee check o Corp & permission check o Currently assumes a single payee id but possible multi match on corps and permissions

	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

	AU 2849		Daily Ideas	9/18/2014	-We had another request to allow the smart group buttons (tiered pricing) to be generic within their group. Say someone wanted to sell 1 for $6 or 3 for $15. The users want to be able to mix and blend between all assigned items within the group. Currently to get the 3 for $15 deal, you have to get 3 of that item. What they want is 3 for $15 with lots of choices to make up the 3. Basically, the price is fixed and the quantity fixed within the group. Anyway, we've had a couple of requests for this type of tiered pricing structure to be implemented. -We also got a request to expand the number of search results on the parts homepage. It was at 50, they want 100 at a time. -We had a request to date range in memory for the admin time clock report. Apparently, the user was doing some repetitive task over and over and had to keep resetting the date range. -On label and receipt printers, add some more details to the help files about paper types, paper sizes, and browser page margins. One of the main secrets is the browser page setup and margins. -The other request we had today was barcodes and graphics on custom PDF stickers and labels. People want to get at the data in the system and put it on different sized stickers and labels. It would be cool if they could map to any data, set sizes and positions, etc. It would also be cool if they could see all of their sticker and label layouts, templates, and designs from one spot. Let them save as many different options as they want. The other really important piece is the database point and click interface. Maybe use JSON objects to store settings and mappings. That way it could be more dynamic.

	Adi 873		Start of the adilas version control system	9/20/2014	As part of the world building project and database copy we are adding some light version controls. This is a list of the prior versions of adilas before the database copy and split. Version 0 - Prior to 2001 Paper tickets, handwritten invoices, numerous spreadsheets, paper timecards per employee, Peachtree Accounting Software, mailing a zip disk from location to location to update inventory. This is where we started from. Version 1 - 2001 to 2002 Web based inventory tracking, stock/units or serialized inventory, multiple locations, employee/users, role based permissions, digital time clocks and timecards. Custom write up system for Morning Star Automotive out of Salida, Colorado. Version 2 - 2002 to 2003 Full parts and general inventory department, basic inventory point of sale, vendors, purchase orders (PO's), parts, items, services, quotes, tax settings, invoices, and customers. Version 3 - 2004 to 2006 Payroll reports & withholdings, commission reports, stock/unit floorplan app, photo management for stock/units, web presence to show stock/units to the public. Version 4 - 2006 to 2007 Full system rewrite, base of permissions & settings. Changed from MS Access database to MySQL Server database. Added banks, expenses, check write system, deposits, & opened up invoices to handle both stock/units and general inventory items and services. Version 5 - 2007 to 2009 Lots of new accounting features. Accounts payable, accounts receivable, P&L (profit & loss) or income statement, first rounds of the balance sheet. Adilas, LLC officially started in June of 2008. Adilas - all data is live and searchable. Version 6 - 2009 Merchant processing - credit cards, recipe/builds, introduced corp-wide settings (custom naming conventions), web presence for parts & general inventories, CRM functionality for customers, flex grid tie-ins, custom paperwork, and reoccurring invoices. Version 7 - 2010 - Part 1 Major work on corp-wide settings, security settings tightened, & lots of new POS (point of sale) features. New features: barcode printing, mini receipt printing, my cart favorite buttons, units of measure, sales & profit reports, & advanced add to cart. Version 7 - 2010 - Part 2 Major rework on inventory ordering processes and system. Allowed for generic mix vendor PO's vs. strict vendor specific PO's. Added a feature codenamed the "adilas dewy decimal" - up to 5 levels of decimal accuracy for costs, quantities, and prices. Version 8 - 2011 to 2012 - Part 1 Added elements of time, calendar, and scheduling. More work on my cart favorite buttons. Added smart groups & tiered pricing structure. Enhanced barcode search capacity. Added duplicate PO, choose interface options, and new custom homepages. Version 8 - 2011 to 2012 - Part Major effort to define how the system interacts and plays together. Lots of work on concepts (underlying core of the system). Added the interactive map layout and touch screen button interfaces. Also added the customer queue (virtual waiting room). Version 9 - 2013 to 2014 - Part 1 New custom code & custom interfaces, industry specific tweaks & changes. Built-in ecommerce & full web presence. Tons of new settings and permissions. Tons of training, both online and live classes. Introduced world building concepts. Version 9 - 2013 to 2014 - Part 2 Hired college interns to help with custom code projects. Over 100+ hours of training captured and edited. New videos put on YouTube. Started adding buttons and icons to pages. Added additional photo galleries for all 12 main system player groups. Version 9 - 2013 to 2014 - Part 3 Defined world building levels & definitions. Migrated to multiple dedicated servers. Added full media/content uploads for all 12 main player groups (file management stuff). API socket connections, custom code, and integration with 3rd party vendors.

	AU 2777		Start of the adilas version control system	9/20/2014	As part of the world building project and database copy we are adding some light version controls. This is a list of the prior versions of adilas before the database copy and split. Version 0 - Prior to 2001 Paper tickets, handwritten invoices, numerous spreadsheets, paper timecards per employee, Peachtree Accounting Software, mailing a zip disk from location to location to update inventory. This is where we started from. Version 1 - 2001 to 2002 Web based inventory tracking, stock/units or serialized inventory, multiple locations, employee/users, role based permissions, digital time clocks and timecards. Custom write up system for Morning Star Automotive out of Salida, Colorado. Version 2 - 2002 to 2003 Full parts and general inventory department, basic inventory point of sale, vendors, purchase orders (PO's), parts, items, services, quotes, tax settings, invoices, and customers. Version 3 - 2004 to 2006 Payroll reports & withholdings, commission reports, stock/unit floorplan app, photo management for stock/units, web presence to show stock/units to the public. Version 4 - 2006 to 2007 Full system rewrite, base of permissions & settings. Changed from MS Access database to MySQL Server database. Added banks, expenses, check write system, deposits, & opened up invoices to handle both stock/units and general inventory items and services. Version 5 - 2007 to 2009 Lots of new accounting features. Accounts payable, accounts receivable, P&L (profit & loss) or income statement, first rounds of the balance sheet. Adilas, LLC officially started in June of 2008. Adilas - all data is live and searchable. Version 6 - 2009 Merchant processing - credit cards, recipe/builds, introduced corp-wide settings (custom naming conventions), web presence for parts & general inventories, CRM functionality for customers, flex grid tie-ins, custom paperwork, and reoccurring invoices. Version 7 - 2010 - Part 1 Major work on corp-wide settings, security settings tightened, & lots of new POS (point of sale) features. New features: barcode printing, mini receipt printing, my cart favorite buttons, units of measure, sales & profit reports, & advanced add to cart. Version 7 - 2010 - Part 2 Major rework on inventory ordering processes and system. Allowed for generic mix vendor PO's vs. strict vendor specific PO's. Added a feature codenamed the "adilas dewy decimal" - up to 5 levels of decimal accuracy for costs, quantities, and prices. Version 8 - 2011 to 2012 - Part 1 Added elements of time, calendar, and scheduling. More work on my cart favorite buttons. Added smart groups & tiered pricing structure. Enhanced barcode search capacity. Added duplicate PO, choose interface options, and new custom homepages. Version 8 - 2011 to 2012 - Part Major effort to define how the system interacts and plays together. Lots of work on concepts (underlying core of the system). Added the interactive map layout and touch screen button interfaces. Also added the customer queue (virtual waiting room). Version 9 - 2013 to 2014 - Part 1 New custom code & custom interfaces, industry specific tweaks & changes. Built-in ecommerce & full web presence. Tons of new settings and permissions. Tons of training, both online and live classes. Introduced world building concepts. Version 9 - 2013 to 2014 - Part 2 Hired college interns to help with custom code projects. Over 100+ hours of training captured and edited. New videos put on YouTube. Started adding buttons and icons to pages. Added additional photo galleries for all 12 main system player groups. Version 9 - 2013 to 2014 - Part 3 Defined world building levels & definitions. Migrated to multiple dedicated servers. Added full media/content uploads for all 12 main player groups (file management stuff). API socket connections, custom code, and integration with 3rd party vendors.

	AU 3715		Tech - Database Project & Solar System Tables	9/20/2014	Planning stuff with a developer to help with the big database project: - Nondisclosure - Files & database - Documentation – pdf file - Prep – his project will be creating the new solar systems - Burn special copy – give it to developer - Help him get setup with a working copy with all up dates - Pattern after the create new cluster section - Creates & dummy inserts – prepped text files - Build on what you have - Work as if for years - Maybe add a version to the general table - Put the updates together and add the version # - It is okay to look-up versions on hand written paper for now - 5 step creation process for new solar systems. This is just for the database creation and dummy inserts: Maybe More: - A – B - C - D – H - I – N - P - Q – S - T - U – Z Maybe More: 1. Universe 2. Galaxy (linked servers) 3. Cluster (box or domain) 4. Solar system (database) 5. World 6. 7. 8. 9. 10. List of Solar System Level Tables – A-B: Column Headings: - Table name - Create - Select - Insert - Dummy - Populate - Update - Disconnected Table Name: 1. Additional customer types 2. Additional customers 3. Adjustment POS 4. Allinv 5. Allinv ages 6. Allinv asset types 7. Allinv final numbers 8. Allinv floorplan 9. Allinv history 10. Allinv internet status 11. Allinv payments 12. Allinv status 13. Allinv sub types 14. Allinv subs 15. App types 16. Balance sheet history 17. Balance sheet items 18. Balance sheet photos 19. Balance sheet subs 20. Bank check specs 21. Banks Key Indexes for the Main allinv Table: - Stock id - Status - Title account id - Model id - Store id - Purchase by type id - Sales invoice number - Corp id - Allinv asset type id - Purchase by id - Salesperson id - Stock - Other salesperson id - Payroll status id - Internet status - Stock paid - Floorplan id - Floorplan paid - Web price setting id - Date in - Date sold - Date floored - Pay period from - Pay period to - Pay date - Date paid commission - Stock paid date - Floorplan paid date - First stock - Month sold - Year sold - Show on web - External alternate id - Customer id List of Solar System Level Tables C: Columns: - Table name - Create - Select - Insert - Dummy - Populate - Update - Document Table Name: 1. Chart favorite categories 2. Chart of account type 3. Chart of accounts 4. Check request types 5. Check types 6. CMS media file types 7. CMS media history 8. CMS media history 9. CMS media references 10. Colors 11. Common features 12. Condition types 13. Contact types 14. Corp to inventory types 15. Corporations 16. Country 17. Customer contacts 18. Customer credit types 19. Customer history 20. Customer log 21. Customer photos 22. Customer queue 23. Customer queue types 24. Customer types 25. Customers Key Indexes for the Main Customer Table: - Customer id - Corp id - Customer type id - Credit type id - Tax category id - Customer status - Salesperson id 1 - Customer start date - Customer end date - Period start date - Period end date - Customer birth date - Use end date - Use period start - User period end - Use customer birth date - Salesperson id 2 - External alternate id - Customer birth numeric - Opt out text - Opt out email - Last date modified

	AU 2865		Daily Ideas	10/2/2014	Myself and an associate were talking in the car, going down and back to Orem. These are a few things we learned and were talking about today: -Seeking and bringing “truth” to what you are doing. Truth tends to radiate light and is recognizable when seen and spoken. If we base our actions, words, and presentations on truth, others will see and recognize those things. Sometimes that can be like hunting for gems in the rough. -Compound concepts – This was a topic that he was talking about. I loved the idea of compound or multiple concepts working together. The reason he was talking about “compound” was certain concepts have inter-relationships between pieces. If you take them apart, they fail or don't work. However, if you use them in combination, they flourish, prosper, and grow. We talked about tons of things both spiritual, gospel, and business. Lots of fun things here. -Be considerate of other people's time. In a way, how you treat their time or interact with people has some underlying tones about your love or care for that person. Granted, that may not be a perfect model, but it was fun to think about time as a gift. Then how we respect that gift of time and how that can relate back to love. This was a fun compound concept – time and love. -Just for fun, here were a couple other topics we had fun with... Compound Concepts – The God Head (The Father, the Son, and the Holy Ghost), Faith, hope, and charity; revelations, obedience, and intelligence; Tasks, goals, and dreams (the big picture), relationships, between things (objects and data) over time – how does time play into relationships? We also talked tons about inter-dependencies inside of the business world, systems, adilas, etc. Fun topics! The key was going back to the idea of a compound concept.... by itself, it needed something else. Together or in combination, it grew, thrived, and flourished. Pretty cool! -Different Business models: Separated Model vs Systemized Model We are seeing more and more need for the following – notes from an on-site setup – no specific order: 1. External alternate id numbers to link between different systems – see possible notes on application flex grid, normal flex grid, and more in-line database fields and options. Search adilas university – developer's notebook entries. 2. Certain line item tables even need external alternate id's. This is true for PO line items, invoice line items, quote line items, expense/receipt line items, and even deposit line items. [External alternate id's for line items] 2.1. Quick note – flex grid tie-ins only tie to main groups. Currently nothing exists for line items that need subs or special data fields. 2.2. We had an instance today (during the setup) that we needed potentially more fields per line items. We were transferring items from area to area (locations) and needed to record lot numbers, external PO numbers, and packaging slip numbers all on the same transfer invoice. These pieces of data related to the line items not the main invoice. 2.3. Some of the external alternate id's come from other systems, but need to be tracked as things happen and take place. Here is an example: Say we got in multiple batches (lots) of product for different PO's. We then want to move the pieces that have been okayed for production but the different pieces come from different external PO's, each with different batch or lot numbers. Right now, I only have one field that can hold an external id number such as an RFID tag number or a batch number. I don't have enough fields to also record external PO numbers per line item. (Think chain of custody or chaining things together to show a relationship or an ongoing relationship...) 2.4. Being able to add both one-to-one and one-to-many relationships to line items would be cool. We are already planning this as part of the sub inventory and cost controls (packaging) feature that is coming up. Our plan is to use a sub of elements of time to hold the sub inventory pieces. What other options are available? Think simple to more complex or dynamic. 2.5. It might be possible to expand the existing flex grid to allow for dynamic connections between main player groups and their line items. We could do this by adding a new column called special_line_id. This would be a temporary patch. However, this would cause us to rethink naming conventions, flex grid titles, and even queries on existing flex grid pieces. 2.6. As long as we are talking about the flex grid and flex grid tie-ins, what about special data types. Currently,the flex grid can extend and connect pieces in the system. We can name different fields and set up light properties such as open entry, drop-down menus, or both open entry and a drop-down. What about dates, date/time stamps, numbers, decimals, and bigger text fields? Currently, all flex grid fields are text based and can only hold up to 100 characters for both titles (alias names and actual data columns. The flex grid tie-in system is awesome, but it may be time for a custom system or custom upgrade option. This doesn't mean the flex grid will go away, but it may mean that a new dynamic system may be needed. Something even bigger or more robust that can be configured and setup as needed. I'd like to make the new feature as light, flexible, and dynamic as possible. Instead of a preset and coded database – existing flex grid tie-in system – what if we allowed each corporation to build extensions. 2.7. Real extensions – Currently, the flex grid tie-in system allows for new data points to be virtually added to a single individual player inside of a player group. The records are added independent of the main individual record. We also show the flex grid tie-in records in a separate spot on the associated sub pages. What if, we allowed new fields to be actual extensions of the main and/or line databases? I'm talking about new fields that appear to be in-line or fully connected at the hip with the original tables, entries, and queries. For example: Say I wanted a packaging slip number, an external customer PO number, and an expiration date to be assigned on every invoice. I only have a couple fields that are built-in to the invoices table. I would have to use flex grid (after the fact) to tie things together. What if I could set up any number of new data fields, assign them a name, sort order (where and how they show up), a real data type (date, time, numeric, decimal, text, etc.), and even have them show up as in-line options? That would be so cool! When I do my invoice, I would literally see those fields as options on the view cart page, edit main invoice page, printable invoice page, etc. The extensions could then be shown back to the user in-line or in-place. (Real In-line Extensions) 2.7.1. Quick note on these extensions.... we also need a field that helps us know instructions, relationships, required/not required, defaults, ranges, and expectations. If these fields are really going to play, we need them to be more rigid as far as what goes in them as opposed to an open entry text field that doesn't have any rules. 2.7.2. If we use real in-line extensions, we could also show and use them as part of the normal query and/or search filters or search criteria. Extension means an extension (dynamic one to one relationship). These values will be held in a special table, but will be treated as if they are part of the original table. This includes searching and filtering data. If a user is looking for a specific value, we could check the extensions and then use the results to filter the main core or existing tables. If no extensions are being searched or filtered, we could reverse the process by searching the main table and then filtering the extensions table base on the results of the main search. Extensions means an extension... 2.7.3. Real In-line extensions could be used on both the main group levels and the line item levels. That would be really cool! This could solve a number of custom field requests at almost any level. 2.7.4. What other tables besides main groups and line items? What about payments? What about subs of time? What about extensions of the flex grid tie-ins table? What about extensions of photos or media/content tables? What about extensions for time cards, payroll, etc. If we are talking about table extensions.... where do we draw the lines? Or do we draw lines? This could be a great way to extend any table... I know that means more code all around the site, but think of the potential. 2.7.5. Table extensions would have to be corporation or world specific but could technically be applied to almost any other main or sub table. This would allow us to keep the core engine virtually the same but it would allow types and functions to be applied like legos to any part of the system. That could be really cool and would make our product super flexible. 2.7.6. I see at least two new tables that are needed. They are the extension names and settings and the extension data points. The names and settings will hold all assignments, names, instructions, data types, defaults, rules, etc. The actual extension data point table will hold a number of pre-configured fields that just hold the data. In a nutshell, the actual extension data points table will be a plain white (vanilla) container. It will be general fields that can hold specific data. It will be the names and settings table that will help the general data points table know what to do. There may be some other supporting tables that go along with this, but these two main tables will be the core of the real in-line extensions. 2.7.6.1. Tech specs for the extension names and settings table: (General 1st round planning): please see scans in photo gallery for details 2.7.6.2. Tech specs for the extension data point table: please see the scans in photo gallery for details 3. Front-end and backend programmers – we are seeing a bigger need for tools for both front-end programmers (point and click interfaces and settings) and backend programmers (people who build the features and pages). The backend programmers are the hard core adilas developers that work in code all of the time. The front-end developers are the reps and consultants who help end users and companies to set up their corporations or worlds. Front-end programmers use existing tools to configure and tweak permissions and/or settings to get the desired outcome. We are seeing a need for both types of programmers. More and more tools are going to be developed for the front-end programmers. This seems to be the current trend. 4. While on the on-site setup, we were asked about moving product between bins and pallet docs (sub locations). Basically, in a warehouse type scenario moving inventory within a defined area. For most retail facilities we use the normal bin # field for the items. There is a need for tracking things on a sub level within a certain bigger area. Currently that option doesn't really exist. This could be a sub of time and I think a good fit there. It may also require the role call page to be built. What are my connections? I think that a flex grid solution could also be used on the transfer invoices after the fact. This entry has been all over the place but I do think that we have a couple of options. 5. Possible combo pack between the normal flex grid tie-ins and the future proposed application flex grid tie-in application. What if we used the real in-line extensions (see item 2 in this list) and extended the flex grid with in-line extensions. That could be pretty cool. That could be the best of both worlds in a fully customize-able level. That could be the application flex grid. Capable of connecting even outside systems together with special mapping, etc. Lots of options. 6. We had a request to be able to track hours worked (labor hours) per job or per Customer PO. This seems like a job for elements of time. It sure would be cool if we could attach sub time elements to any object without having to go to the main elements of time section. Here is one way it can work... A main element of time could connect to a single individual data object, and that could create a link to time. Then the subs could be added at will from the individual data object (a PO, an invoice, a customer, a stock/unit, etc.) This could be done very easily. Just add a new template setting called individual data connection. We could then use sub dates and time very easily. Basically, add an app_type_id and main_id field just like media/content and there you have the needed relationship between time and the single data object or player. It could be that easy. That would be super cool. 7. We really need round two of elements of time. It has so much potential. 7.1. Prepped but unfinished subs or functions of time: Additional Sign-Off's – Subs Additional GPS or RFID Tag Tracking – Subs Additional Payroll/Time Sheets – Subs Additional Notification/Reminders – Subs Additional Tie-In's/Assignments/Pools (“any” person, place, or thing) 7.2. See this URL for help and definitions of proposed pieces of the elements of time section: - https://data0.adilas.biz/top_secret/help.cfm?id=391&pwd=sub. This whole page talks about subs or functions of time 8. We are seeing more and more needs to be able to copy existing pieces in the system. This could be recipe/builds, users and permission settings, and even transfer invoices between locations. Each of these sections need their own features but basically people want to set things up once and then copy and paste or be able to see the next one up quicker or make almost an exact duplicate with only minor tweaks. Here are some other pieces that would be cool if we could copy them... 8.1. Be able to copy expense/receipts 8.2. Be able to copy balance sheet items 8.3. Part or items 8.4. Stock/units 8.5. Be able to copy users and permissions 8.6. Be able to copy locations and tax settings 8.7. Be able to copy Recipe/Builds 8.8. Be able to copy elements of time 8.9. Be able to copy smart group rules and assignments 9. Be able to point and click and create your own invoice and quote templates. Imagine an invoice template that you could set what to show/use, what to hide, what order to show things in, and what placement for the different pieces. Be able to turn features on, off, name the templates, and other options. As a note, elements of time already use custom templates – unlimited with point and click options to name the types of time and control the subs or functions of time. It already exists, just not for invoices yet. 10. We had a request to be able to speed up transfers and be able to carry over batches, lots, and RFID tag numbers. People want things tracked in detail but they also want speed. -Side note: This session has been more of a brainstorming session than just recording the notes from the setup... I got home late and just scribbled some quick notes on a post-it note. It is now 10/4/14 (two days later) and I'm trying to record the notes in my notebook. It's the little tiny note on my post-it note that is sending me off on this brainstorming session. I am so grateful for tiny little notes and the ability to write things down. Without that, we would skip and forget a lot of stuff. Anyway, just a small side note.

	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.

	AU 2902		Daily Ideas	10/23/2014	-We had a request to be able to save advanced customer search options for custom reports. We are going to get more and more of these types of request. Users want to cut steps and save settings and search criteria. We already have the tools… we just need to implement them. -Quote from a developer – “The lines contain the data.” Basically, let the line items (the details) contain and hold the data. This will help later on with look-ups and reports. On sub dividing pieces into smaller sections… The goal is to add granular level controls. Having said that, it would also be very nice if we had pre-built bigger sections if we want to run fast or want to run in bulk. Think of bread as an example…. (please see sketches in photo gallery) - Loaf – (large or bulk) general - Slice – (medium) some control - Cubes or sections – (small) fine level control - Mixed or different options – (variable) -It sure would be nice if we could control things at whatever level we needed it to be. That would be awesome! -The best solution is a mixed or variable option that fits your needs. Granular control is awesome but sometimes you need quick, bulk, grouped, or even generic. Think pre-set pieces, tools, and output.

	AU 2906		Daily Ideas	10/30/2014	Notes from a phone call between Steve, a developer, an intern, and myself: - We need to allow sub categories for parts. This could be called Nth level categories where N (letter N) is the variable. These categories need to create a self-identity or virtual stacking order. - It would be nice to add a photo per part or item category. This could really help with eCommerce and visual navigation. - Weights are going to be coming more into play. - We may need to create a cart or shopping cart alert system. - Small graphic to explain the difference between backend programmers and frontend programmers. (Please see sketch in photo gallery) - Clients – our users; API, Permissions, Settings – consultants, reps, and frontend programmers; ColdFusion, Code, Database, Java Script, SQL, … Backend – backend adilas developers, interns, techs, etc. - Pages – nuts and bolts - Subs… That seems to be the new direction. Subs deal with stacking, layering, categorizing, wrapping, and other spatial (space) elements. - Conversion - Little black boxes on the shopping cart page. - User defined rules and assignments. - True generics and homogeneous products - Units of measure or units of measurement. - We need a mini blog of what’s new, new updates, and upcoming features. - We talked about class and training attendance at our advanced accounting class (30+ people). We need more training. - We also talked about controlling and managing our time lines. That is a tough subject. - Custom labels - Backend developers – (write and develop the settings, permissions, and API sockets) vs. Frontend developers – (setup, use, and interact with settings, permissions, and API socket calls and connections) Small graphics while talking to an intern about filling in the subs or sub pieces of the puzzle…: (Please see sketches in photo gallery) - Start here – fill in the subs – key pieces or main general structure – goal - We got a very good base level structure built and ready - The next phase is filling in the sub pieces of the puzzle - 2D spreadsheet or table (rows & columns) - 3D model – Time (x), Money (y), Space (z) - Pretend this is a bridge – main supports, subs, “zipper it” – one cog at a time

	AU 3725		Brainstorming - Call with Steve & Developers	10/30/2014	Conference call with Steve & 2 Developers: - Sub categories for parts - N level categories - Self-identity - Photos on part categories - Cart alert - Weights - Subs – it is the new direction – special elements - Weights - Conversions - Little black box on the shopping cart stuff - User-defined: rules & assignments - True generics and homogenous products - Units of measurement - Mini blog of what’s new o New updates - 30+ people in the advanced accounting class - Do logos - Controlling and managing out timelines - Custom labels

	Adi 908		Client/Server Model & ColdFusion Structures & Scopes	11/24/2014	This is a simple drawing of two different pieces that we use to help developers understand the servers and what they do. Part 1 - Client/Server Model This section helps show the flow of what happens as an outside client makes a web call or page request. The diagram shows clients (laptops, desktops, tablets, phones) connecting or requesting something from a normal web server through HTML (hyper text markup language). If the web server can handle it, the web server returns the request. This is called static HTML or a basic web site. If the normal web server does not know what to do, for example a ColdFusion page request, the web server hands it (the request) off to the ColdFusion server. Basically it is a please help me, I don't know what to do with this... The ColdFusion server than plays with all of its options and assets and returns the results in normal web language (html). The ColdFusion server is kinda like the brains of the process. It is very flexible and can deal with variables, conditional logic (if statements), loops, multiple sets of data coming from different sources, and even database and API connections. Very powerful. If the ColdFusion server needs database information or records, it uses an internal API (application programming interface) to get the data back to the ColdFusion server. This is the wall outlet looking piece of the diagram. ColdFusion (the brain) then talks to the database through a language called SQL or structured query language (database talk). The database responds and sends the information back to the internal API and then back to ColdFusion. The trip between ColdFusion, the internal API, and the database all happen very fast and possibly multiple times per page request. Think of those three pieces (ColdFusion, internal API, and the database) as the three musketeers. They work very well together. Most of the work in the system is done by bouncing between those three players. By the time everything is done, ColdFusion converts the values into normal web or HTML and sends it back to the normal web server that sends it back to the client. All of these connections are done in super fast, lighting quick phases so that it appears that only a single page was requested, processed, and returned. In reality, there are multiple different servers working in combination, each doing their own job, to make the whole. If you take any part of it out, the process would fail. Another fun part of the model deals with how an external API socket connection might take place. We, at adilas, allow access to backend database pieces based on settings and permissions set inside of the main secured environment. The external API is represented by the surge protector type piece that has sockets, data ports, and plug-ins. This section takes a standard piece or request and sends it to the internal API (wall socket in our diagram). The connection is made in a non native format like JSON (java script object notation) or XML (extensible markup language). This allows various 3rd party players or 3rd party solution providers to play with functions, data, and pieces of the adilas.biz business platform. Basically, they (the 3rd party players) are able to code in their native environments (other programming languages) and then request, pass, or pull data from our servers (logic and databases) using external API socket connections. See this help file for more information about the adilas.biz API. Part 2 - ColdFusion Structure & Scopes This diagram shows a large dresser with multiple predefined drawers. Think about both predefined and user-defined containers for storing values and data. We use this analogy to help new developers understand where things are stored and how to get pieces in and out of the application. The drawing has a number of predefined dresser drawers called structures (super variables with names and objects). Here is a list of the predefined structures and what are called scopes. 1. variables scope - Set on the page level. They only live on the page where they are created. This is the default scope. 2. URL scope - These values get passed in to a page via the web address field or URL. These values may be passed from page to page and allow dynamic access points from the web address or link bar. These values are often used to help speed up dynamics, templates, and quick dynamic page results. 3. FORM scope - These are values that get passed to a page from user interactions. FORM scope values often come from searches, reports, data fields, selections, filters, and other web form based options. The FORM scope is much bigger than the URL scope and should be used if size, quantity, and/or security options are needed. Technically, these values are virtually passed behind the scenes in page headers and page bodies. The normal public can't see these variable/value pairs without looking deeper into the underlying pieces. Think of the FORM scope like a giant hidden folder full of data that gets passed from page to page. The hidden folder is marked as private or don't show the values unless asked. 4. session scope - The session scope is set at the cloud or virtual memory level. This is great for storing things that need to last (timeframe) between page requests. These are things like logins, user settings, date ranges, shopping cart data, and other pieces that may be needed by one or more pages. As long as the user is interacting with the server, the session variables will continue until cleared or a preset time period (2 hours) of inactivity occur. Whichever is first. 5. application scope - These values are set when the server starts up and gets used for the first time. The application variables are at the site or server level. These variables and values can live on and on for days, weeks, months, etc. They are values and settings that are needed in multiple places in your site and/or application. 6. arguments scope - These values are used inside of methods, functions, or internal API socket connections. They must be passed in when calling and/or requesting methods or functions. Often arguments have requirements, defaults, and even data types (strings, numeric, dates, etc.). 7. attributes scope - These values are used inside of ColdFusion when making, using, and creating things called custom tags. The custom tags are usually some sort of action or routine that gets performed over and over again. The custom tags help the developers to code once and then use over and over again. 8. CGI Scope - These values are fairly techy and are created behind the scenes. This scope allows the developers to get at things like server paths, page names, IP addresses, and other http or web settings (hyper text transfer protocol). 9. Other Predefined Scopes - This entry is here to help the developers know that there are a number of other scopes that are specific to the task at hand. These include things like error scopes, cffile scopes, cfhttp scopes, and try/catch options. There are a number of other scopes that may be available. See the actual code and/or documentation for more information.

	AU 2927		Client/Server Model & ColdFusion Server Structure	11/24/2014	This is a simple drawing of two different pieces that we use to help developers understand the servers and what they do. Part 1 - Client/Server Model This section helps show the flow of what happens as an outside client makes a web call or page request. The diagram shows clients (laptops, desktops, tablets, phones) connecting or requesting something from a normal web server through HTML (hyper text markup language). If the web server can handle it, the web server returns the request. This is called static HTML or a basic web site. If the normal web server does not know what to do, for example a ColdFusion page request, the web server hands it (the request) off to the ColdFusion server. Basically it is a please help me, I don't know what to do with this... The ColdFusion server than plays with all of its options and assets and returns the results in normal web language (html). The ColdFusion server is kinda like the brains of the process. It is very flexible and can deal with variables, conditional logic (if statements), loops, multiple sets of data coming from different sources, and even database and API connections. Very powerful. If the ColdFusion server needs database information or records, it uses an internal API (application programming interface) to get the data back to the ColdFusion server. This is the wall outlet looking piece of the diagram. ColdFusion (the brain) then talks to the database through a language called SQL or structured query language (database talk). The database responds and sends the information back to the internal API and then back to ColdFusion. The trip between ColdFusion, the internal API, and the database all happen very fast and possibly multiple times per page request. Think of those three pieces (ColdFusion, internal API, and the database) as the three musketeers. They work very well together. Most of the work in the system is done by bouncing between those three players. By the time everything is done, ColdFusion converts the values into normal web or HTML and sends it back to the normal web server that sends it back to the client. All of these connections are done in super fast, lighting quick phases so that it appears that only a single page was requested, processed, and returned. In reality, there are multiple different servers working in combination, each doing their own job, to make the whole. If you take any part of it out, the process would fail. Another fun part of the model deals with how an external API socket connection might take place. We, at adilas, allow access to backend database pieces based on settings and permissions set inside of the main secured environment. The external API is represented by the surge protector type piece that has sockets, data ports, and plug-ins. This section takes a standard piece or request and sends it to the internal API (wall socket in our diagram). The connection is made in a non native format like JSON (java script object notation) or XML (extensible markup language). This allows various 3rd party players or 3rd party solution providers to play with functions, data, and pieces of the adilas.biz business platform. Basically, they (the 3rd party players) are able to code in their native environments (other programming languages) and then request, pass, or pull data from our servers (logic and databases) using external API socket connections. See this help file for more information about the adilas.biz API. Part 2 - ColdFusion Structure & Scopes This diagram shows a large dresser with multiple predefined drawers. Think about both predefined and user-defined containers for storing values and data. We use this analogy to help new developers understand where things are stored and how to get pieces in and out of the application. The drawing has a number of predefined dresser drawers called structures (super variables with names and objects). Here is a list of the predefined structures and what are called scopes. 1. variables scope - Set on the page level. They only live on the page where they are created. This is the default scope. 2. URL scope - These values get passed in to a page via the web address field or URL. These values may be passed from page to page and allow dynamic access points from the web address or link bar. These values are often used to help speed up dynamics, templates, and quick dynamic page results. 3. FORM scope - These are values that get passed to a page from user interactions. FORM scope values often come from searches, reports, data fields, selections, filters, and other web form based options. The FORM scope is much bigger than the URL scope and should be used if size, quantity, and/or security options are needed. Technically, these values are virtually passed behind the scenes in page headers and page bodies. The normal public can't see these variable/value pairs without looking deeper into the underlying pieces. Think of the FORM scope like a giant hidden folder full of data that gets passed from page to page. The hidden folder is marked as private or don't show the values unless asked. 4. session scope - The session scope is set at the cloud or virtual memory level. This is great for storing things that need to last (timeframe) between page requests. These are things like logins, user settings, date ranges, shopping cart data, and other pieces that may be needed by one or more pages. As long as the user is interacting with the server, the session variables will continue until cleared or a preset time period (2 hours) of inactivity occur. Whichever is first. 5. application scope - These values are set when the server starts up and gets used for the first time. The application variables are at the site or server level. These variables and values can live on and on for days, weeks, months, etc. They are values and settings that are needed in multiple places in your site and/or application. 6. arguments scope - These values are used inside of methods, functions, or internal API socket connections. They must be passed in when calling and/or requesting methods or functions. Often arguments have requirements, defaults, and even data types (strings, numeric, dates, etc.). 7. attributes scope - These values are used inside of ColdFusion when making, using, and creating things called custom tags. The custom tags are usually some sort of action or routine that gets performed over and over again. The custom tags help the developers to code once and then use over and over again. 8. CGI Scope - These values are fairly techy and are created behind the scenes. This scope allows the developers to get at things like server paths, page names, IP addresses, and other http or web settings (hyper text transfer protocol). 9. Other Predefined Scopes - This entry is here to help the developers know that there are a number of other scopes that are specific to the task at hand. These include things like error scopes, cffile scopes, cfhttp scopes, and try/catch options. There are a number of other scopes that may be available. See the actual code and/or documentation for more information.

	Adi 933		Custom code - Kent	2/19/2015	Some things I'd like to cover: - brief intro / walkthrough of existing Adilas systems - general overview of the top 10 markets Adilas has a footprint in - open discussion about American Green / ZaZZZ tech roadmap, and how we envision it working with Adilas

	AU 3607		Daily Tasks	2/21/2015	• Working on getting up the data 3 servers. Working towards releasing the server today. Signing off on code to push up to new servers. • On the phone with Steve going over things. He has been working on new black box custom code stuff. Funny enough, he has done enough special includes that he is looking for ways of providing a generic or global custom skin or option. Our whole phone call was talking about custom black box skins and ways to apply a skin as a paid or non-paid choice. Very interesting. He would like to run things through the chooser interface. Basically a sub selection of what the user could see, use, show, hide, or how to skin a page. • An intern came over and we spent some time talking about new code changes. We talked about new global skins, black boxes, web/API sockets, security, and page id numbers. We got out a small whiteboard and brainstormed on authentication and user access to the adilas API sockets. We were kind of stumped on internal vs. external usage of the same virtual data highway. We are going to add some database flags to help us know whether or not the methods are internal or not. We will also hardcode access only to master corporations. Steve called and had questions on adding a new black box to the submit cart page. We have only just barely started to say the word black box and it is already starting to blow up – meaning more and more needs. I think that custom is like looking at an iceberg… You only see a portion of the whole until you get into it a little deeper. It gets deep quick! • Recording notes and working with an intern on validation and flow for pages. Sometimes being so dynamic has its challenges. Pros and cons. • Approving and signing off on code. Steve even sent me new black box code for the submit cart page. This is the second page in the secured environment to get a black box for custom code. The first one was the view cart page. Our plan is to keep adding them (black boxes) as needed. • Also spend some time and talked with an intern about creating a start-up development shop to do adilas custom code projects. Basically a small sister company to handle the custom projects. Working on code for the data 3 server. • Tightening up the image and photo monitor report for all servers. Added a new user filter, added totals, and showed output for time, deposits, quotes, users, and vendors. • On the data 3 server updating SQL to add in an adilas corporation. • Working on the data 3 server. Approved it to go live. Light testing and browsing to check settings and flow.

	AU 3666		Phone Call with Steve	2/21/2015	Phone call with Steve: - Chooser o Sections o Black boxes o Generics – skins & logic - Default homepage - Page level settings - Black box skins - Full takeover or custom - People want to skin things - All 7 black boxes - We need to go past custom & into custom skins – run through chooser - Start with view cart - Fix the generic black page - Add new code logic to the page - Think about page level components, plug & play, drag & drop, parameters, arguments, attributes, subpage settings - WordPress – hooks, widgets, plug-ins

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

	AU 3773		Daily Ideas	3/27/2015	-While at Beaver Mountain ski resort, I rode up the lift with a guy. He is the owner of a men’s clothing store here in Logan, UT. His business jingle is – “How you look is the first message you deliver.” As we talked on the way up the hill on the lift, it got me thinking… What message are we delivering with adilas? Sure it is a flexible work hours but it doesn’t look very exciting. I think it is about time to change that. -As a kind or/sort of blessing – okay – a real blessing. We’ve been able to fly low and under the radar and for quite a while. That has been a huge blessing for us. -A while back we were planning some interface changes. As part of that planning, we wanted to do a graphical homepage or sub homepage for each section inside the system. Basically, an organized list of graphics, icons, menus, buttons, and links. Make sure and do some research inside of adilas university on graphical menus, homepages, and icon menus. We may need to back to 12/23/10 interactive map stuff. (Graphical layout) -When showing page options and layouts, show feeder pages or sections, options, and just in time connections to the pages. (Flow charts) -One of the icons was going to be for training and education. It is okay to put the training and education graphics and links as under construction. Maybe that will help us to get some funding on training for adilas university per section or page section. -When showing pages, also include a generic action page, a generic database connections, and even a generic custom page option. Help tell the story through pictures. Just in time connections and flow. -Put a link to the community funded projects on the graphical start menu pages. This might be a great spot to collect data and sharing as well as let people request pieces and options. Basically, a link or page to go to our forums and/or sharing page. -On the quick search, we need to add options for media/content. That would be cool. -We also need to add new keyword options to get to the new and upcoming graphical start menu pages or graphical homepages. Maybe use “gg” for graphics graphic. Or maybe “start” or “ghome” (graphical homepage), or “menu” or something like that. These keywords would then be used to go the correct pages. For example: using the quick search, select invoices and then type “ghome” or select deposits and type in “ghome” to go to the graphical start menu or graphical homepage for the different sections. -I know all the training is not done yet… but it may really help to provide links, help files, short cuts, graphics, videos, etc. to help out our users. The more they learn on their own… the less we need to teach them and hold their hands. Empower the people! -When searching the developer’s notebook on adilas university… Allow for more than one search term or phase at a time. Maybe use a “t” (plus sign) or some other character to allow multi search phrases per URL link. Then on the page separate out the phrases and play accordingly. For example: some page name cfm, search = base camp and base camp and anchors or some page name cfm, search = base camp – base camp – anchors. Basically, “base camp”, “basecamp”, and “anchors” – some way to pass in multi’s. -On the graphical homepages or start menus… We need a section that could control settings both on an individual level as well as on a World or Corporation level. I’d like to show everything, even if the user doesn’t have the correct permissions. Maybe even use a green light, red light indicator to help show permissions.

	Adi 1103		Additional Vendor/Payee Tracked As Part Of An Expense/Receipt - Great For Credit Card Transactions	5/22/2015	This project allows for a second and/or additional vendor to be tracked per expense/receipt. This would work awesome for businesses who use a credit card for their transactions. Say we used the Bank of America credit card but bought things from Home Depot. Currently we can only record one vendor/payee per expense/receipt. It would be really awesome if we could record both, Bank of America (who we still owe or the payable) and also Home Depot (who we actually purchased from). Anyways, that is the concept. If we add this, we would be able to search either vendor to get the transactions. Bryan Dayton completed in 2017

	AU 3873		Daily Tasks	6/16/2015	• Emails, recording bills, and recording notes. • Went in to Logan to work with my guys. After stand-up meeting I gave some of the guys FTP (file transfer protocol) assess to push up new demos and marketing content. • Worked with an intern to line out his new corp-wide setting project. This is part of the auto retrieve RFID tag values when restoring a quote to the cart for final checkout. • Other interns and I did a small session on the packaging project. We built the database table and talked about the sub inventory fields, columns, and associated tables. • I then worked with a developer on what he is going to need in order to get his multi corp sales report done. I showed him some live data to help him get an idea of how this report would be used in real life. • A developer showed me his print multi pdf labels project. • A contact sent us a referral. He does a think called medical tourism. Basically, they offer a trip to Mexico, a nice hotel, an American doctor, and a full remote recovery package. We chatted and talked about options and what adilas could offer and bring to the table. It was a fun visit. • I’ve been using a couple of graphics and printouts to help explain what, how, and why we do things. The graphics really help get the concepts across. • After the sales meeting, I met with the project manager on a couple projects. We figured out assignments and rough timelines. He has been a huge help to keep things going. • I helped a developer and intern with some new high admin permissions. I gave the developer access to setup new adilas accounts and worlds. • My brother came by and I helped him get started on cataloging video clips and YouTube videos. We are going to use the media/content tools to catalog the YouTube videos. • Another brother showed me some of his design work that he has been doing He is doing awesome. I’m excited! 30 miles. • Went over to a family friend’s house to talk with him about projects. We ended up talking about concepts of watchers and feeders. Good stuff.

	AU 3877		Daily Tasks	6/20/2015	• Emails, tech support, phone calls, and prep work. • Lined out a project for interns. • Quick call with Steve. • On the phone with a developer going over ideas and options to help with both funding of projects and payments for interns and developers. Great conversation! Lots of open communication going back and forth. He has been awesome. We also decided to hold off on any major changes until he gets back from New York. • Phone calls, tech support, and checking out a bowling software package called Drill Spec Coordinator. We have a number of bowling Pro shops that use adilas. Many of those pro shops want a feature similar to this package inside of adilas. • I installed the software and did a couple generic screen captures to get a flavor of the program. I then uninstalled the software from my machine. The vendor’s name is Ebonite that makes the current software package. They are a bowling standard and deal with balls and special drilling specs for holes and grips on bills. • A developer came over and we chatted about a number of office models and pay structures. He pitched a performance based commission model. We both took a bunch of notes and worked through some scenarios. Great meeting and we made a lot of progress. He also pitched a number of ideas dealing with teams, rotations, job sharing, cross training, and other performance based concepts. Great meeting!

	AU 3923		Daily Ideas	7/1/2015	Normal Rep Model for Adilas: - Clients --- Reps: Independent Relationships - Clients --- Adilas: Direct Pay $ - Rep --- Adilas: Commission paid to rep % - There exists an independent relationship between the rep & the clients - The clients pay adilas directly. This is for their monthly service. - As needed, adilas pays the rep a % (percentage) commission based on the monthly. Other models & how to grow adilas: Normal Rep Model: - Clients – direct relationship with Rep - Clients – direct pay to adilas $ - Rep – commission from adilas % - Other reps & independents - Direct pay for servers - Super systems with their own servers and subs – repeatable shop or business hub model - Hub or Shop Model: (direct pay) o Support o Sales o Project management o Custom code o Consulting o Setup o Training o Hosting - They could buy their own servers and/or boxes and bill, provide support, training, setup, and other SaaS (Software as a service) features. -There could be as many hubs, shops, stores, or niche products as needed. Virtually unlimited growth options. White labels, independent clusters, niche products and services, etc. -We could serve up niche products and services, generic business options, small clients, medium sized clients, or even big huge clients. Basically, we farm out or sub out the different services and adilas focuses on the core product or data engine. -Adilas wants to be the core product, the data processing, storage, usage, etc. Basically, the backend data engine piece.

	AU 3902		Daily Tasks	7/6/2015	• Working on graphics for the adilas.biz community funded projects. I redid a couple of other graphics. Trying to create a new look to expose the adilas world building concepts and more. I really think that some new graphics will help our users know more about what we are doing and where we are headed. Communications are somewhat tough to keep on top of. • Added some new ads and layout for the main login page. • On the phone with a developer going over pay rates, hours, and how to transition over to custom work. Great phone call and GoToMeeting session. We were talking and running numbers and scenarios in Microsoft Excel the entire time. We came up with a good plan to help with the transition. The plan dealt with our top four players at the Shop right now. • Went in to Logan to work with my guys. I worked with a developer to get some generic PDF labels created. This is for a bulk print labels project. • I then met with another developer and looked over his plans to further define the adilas shop and key roles within that environment. He had a nice Excel spreadsheet with graphs and such all laid out and displayed. • Later on, he & I got on a GoToMeeting session with another developer and went over his ideas and new documents. We further defined roles and responsibilities and even put names with the different roles. Lots of work with spreadsheets and such. • At the end of the day I got to play with some new Flash interfaces that my brother is working on. Super cool stuff. I want to get them wired up – so that I could use them. Awesome! 30 miles.

	Shop 3821		Virtual Post-It Note	8/19/2015	Business trip to help Safe Harbor Pros focused new features marketing promotion pay off debts and bills help the office start running on their own slavage clean-up code custom solution short time Cons Stress travel is expensive leaving family leaving the shop hard work may not get paid very quickly away from home managing other pieces Call back Bank of America Scout stuff Finish stuff for William Bates Scan recites Flash buttons Document Bear 100 Document That Herb Shop

	Shop 3833		Virtual Post-It Note	10/29/2015	7:45-8:45 Emails, tech support, and a graphic for a client. 9:00-10:00 On the phone with Steve going over developers and different issues that are going on here and there...expand. 11:15-8:45 Meeting w/Nick, Bryan, Calvin, and Dave. Dinner w/Dave at Texas Roadhouse Meeting w/Jake, Daniel, and Dave on the GPS project. Project management w/Will Phone call w/Eric Recording notes and project management. Repeater projects. Price list on custom options.

	Shop 194		Black Box- Mini Receipt	11/12/2015	Need help in getting files off data 2 and help out black box creation flow. Notes: Met with Daniel and we looked up how the rewards points were stored for Blum. We actually logged in and looked around and followed older code from Eric's reward points. We even followed logic for the point redemption process. The original file was: custom/custom_blum_rewards_program.cfm Good session and wrote out some basic steps. Here is a light overview for the record: - What server? - What corp id? - Other special id #'s? - What files are being altered, added, or deleted? - What are the differences between test and live? - What is your to do list for the project?

	Shop 4382		Virtual Post-It Note	11/16/2015	-(10 - 11)Logan, meeting with Russell and talking about scheduling some time to work on projects. On the phone with Steve going over projects and funding. 30 miles -(11 - noon)meeting with Nick to go over a project for a generic #rd party solutions error log and back end admin report interface. -(noon - 1:30 pm)working with Russell to get images for a photo gallery -as part of the photo galleries we went through some old PDF's for the developer's notebook stuff. Fun session. -(1:45 - 4:00)met up with Kris Kofed (consultant) and went to a meeting with Beaver Mountain to talk about their ski school. We met with Debbie (ski school director), Travis (mountain manager), and Kristy (office manager). We first talked shop and drew some things out on paper. Mostly concepts of one-to-many-relationships, players, groups, and mixing different pieces. Travis and Kristy were catching on pretty quick but Debbie doesn't know computers that well and you could see some panic in her tone,questions, and appearance. She seemed to relay as we went along and talked about options, features, and benefits of moving into a system and digital model. Great meeting and we set a model. Great meeting and we set a new meeting time for next Monday to present a full proposal and plan for what we will do for them. -(4:15 - 6:45)Went back to he office and told the guys about the meeting with Beaver mountain. I then worked with Daniel on some code sign off of Blum and Green Door out of California. The session went very well until we ran into a bug on one of the loyalty points calculations. We spent over an hour and a half trying to fix that bug. We finally got it fixed and got everything all wrapped and done.

	Shop 2944		General	11/30/2015	11/30/15 5:15-5:30 Emails and small to do list stuff. 8:15-8:45 Emails and light follow up on things. 10:00-7:00 Went into Logan. Got Russell his checks and talked with him a bit about pros and cons of having help. We talked about some of the challenges and Russell just listened. I worked with Nick on sign-off for the 3rd party error logs. We started getting in to integration for the clear cart logic. Next I spent a 2 hour block with Steve working on sub inventory and helping it to be a smoother process. Lots of tracing steps and trying to figure out what is needed and how we can help. Encountering some small errors, problems, and difference in coding techniques. Working through things. After that, Nick and I did another session on the 3rd party error logs. We added all the code for catching clear cart actions as well as actual Hypur API call errors. The clear cart session took a bit of time as we had to break things up into smaller pieces in order to show both main details and individual line items. After that session with Nick, I worked with Alan Williams for about 2 hours on his new settings for switching the normal Flash my cart favorite cart buttons with a non Flash or plain HTML and CSS type button. We got into the details and started at the source of the change dealing with new personal settings. Busy day today. The other thing that was going on today was Bryan was working on an a custom invoice layout or A Touch of Style. It included a special layout, photos for line items, back order stuff, shipping stuff, etc. It is looking pretty good. 9:30-9:45 On the phone with Eric talking about some new rounding logic for the shopping cart for some of his clients. Basically, the code forces the cart to a straight dollar value with no extra cents or change.

	Shop 542		Talking with Calvin about page level settings	1/21/2016	On a phone call with Calvin going over page level settings. This is where you take an entire database table and break it into each and every field or column name. We talked about using JSON or a real look-up table. We decided on a normal database table for the settings. Here are some of the table specs: (just ideas) db_setting_id int(10) auto increment key field corp_id int(10) default 1 unsigned db_table_name varchar(100) default null db_field_name varchar(100) default null db_field_type varchar(25) default null - (values like numeric, string, or date - not too techy) db_field_alias varchar (150) default null db_field_show tinyInt(1) default 1 (1=show 0=hide) db_field_required tinyInt(1) default 0 (1=required 0=not required) db_field_default varchar(100) default null db_field_rules_max int(10) default 0 (0=skip - any other number either means a max length or a max number) db_field_rules_min int(10) default 0 (0=skip - any other number either means a min length or a min number) db_field_sort int(10) default 100 (let them manually sort the fields as need) db_field_instructions varchar(255) default null (use for any special verbage and/or instructions) db_field_drop_down varchar(255) default null (this could be a list of items to help load a drop down - example: cat\|dog\|mouse\|horse We would want to index the corp_id and the db_table_name.

	Shop 4947		Virtual Post-It Note	4/21/2016	-Tighten down the default expense types per employee. Causing problems if not numeric id numbers. -Cross corp problems with default expanse types for payees. -More Standards -Internal changes - Monies between parties -Database changes -script all changes -search all inserts -search all updates -Full Site Changes -main root -top_secret -web/API -pdf -shop -custom -public -ecta.

	Shop 1277		Meeting with Nick - Tax Calculations	4/22/2016	Working with Nick on how sales tax is calculated inside of adilas. We spent quite a bit of time prepping and even showing different tables and backend database stuff. We used a whiteboard and did a number of different scenarios. We got pretty deep into the subject. We talked about generic calcs, per line item calcs, and what we called special or back calcs (with tax included, discounts, backing into a set total, etc.). Good session and it seemed like Nick was really able to catch on and understand what was going on.

	Shop 3460		Virtual Post-It Note	6/8/2016	-As a note, we are having indexing dates and times. -What about numeric dates ?

	Shop 1154		Alan Time	6/13/2016	Emails and light clean-up until Alan got here. Met with Alan and he showed me some progress on the new shipping settings for ecommerce. We went through some of the logic and looked over a couple of pages. We also talked about some other upcoming projects that deal with a new credit card API gateway connection. I gave him a light review of the different pages and how they work together. I also had a call from Eric Tauer (other developer) asking and talking about inventory tracking and API socket settings.

	Shop 1394		Calvin Chipman	6/15/2016	On a phone call with Calvin about sub inventory stuff. Lots of talking about new sub inventory global (higher) settings such as how to get things in/out of a package (first, last, oldest, newest, based on dates, etc.), show/hide the view subs (visibility), custom sort order for showing subs (numeric, rfid, ref, id, dates, etc.), and how to use and search barcodes for sub inventory. We spent tons of time working and talking about the possible mixed barcode logic. I sent both Calvin and Steve emails on some of the pieces for mixed barcode searches and where I would like to head with things. We have already done a ton of work here and I wanted to capitalize on that. These are things like: see attached for an included text file with some parent child barcode logic, see the top_secret/secure/cart_quick_search.cfm for some of the current barcode search logic, and see this help file link to see some of the current verbage or user-friendly info on doing a barcode search. (https://data0.adilas.biz/top_secret/help.cfm?id=413&pwd=cart)

	Shop 1528		Bryan and Calvin	6/20/2016	Working with Bryan on some API settings and defaults. On a zoom session with Calvin going over the new plans for the sub inventory and custom data storage options. Good stuff. He is going to be creating 3 new tables to store custom dates, custom text values, and custom numeric values. We will then tie-in those values to other tables and other id's. Basically, we will be making a custom storage solution of sorts. This is somewhat based off of some brainstorming that was done on in-line extensions. As a side note, custom data storage is one of three huge keys for custom applications. The other two are custom code options and custom look and feel. When you get all three custom pieces playing together, you can have custom applications.

	Shop 1403		Calvin Chipman	6/30/2016	On a zoom session with Calvin. We spent some time looking into his SQL auto processing tool. He is getting further along and we ran some test cases. He is also adding a logging section to help us track down what is running and what is still pending. Calvin will be building an editor of sorts to help with the script writing portion of the SQL auto processing tool. We also talked about Calvin's new custom text fields, custom numeric fields, and custom date fields. We decided that we would add a new database column to the tables to help us know which id number we were referencing. The new field will be something along the lines of parent_column_name. That way we can state what table to connect to, what the id number column is, and what the actual id number is. This will open up a number of really cool options. This is exciting. As a note, this may end up being part of our real in-line extensions and custom storage options.

	Shop 1687		General	7/23/2016	Built out some code and logic for the barcode (mixed sources) search page. Added options to search sub inventory packages directly from the quick search. All the users need to do is enter a package number in the quick search and use the barcode search option. An example might be: ~555 or ~750 where the package or sub inventory id is 555 or 750. Also built and coded a small page for a client that wanted a special character removed from his general or generic barcode searches. Added a new black box and pushed the new code to all servers. Billed the client for an hour and a half. Doing some thinking about how Steve and I could enter the market and market our skills and time along with the other independent reps and consultants that serve the adilas marketplace. Some fun ideas.

	Shop 1427		Calvin Chipman	8/11/2016	On a zoom session working with Calvin on sub inventory. We ended up talking about how to run pre queries and then use lists of id numbers to help filter other later queries. That lead us to talk about how we were going to do dynamic searches on the new custom date, numeric, and text values tables. We looked at some older code and then we talked about adding a column number field to help with keeping track of which field holds which piece of data. We also needed a separate sort field that would allow us to filter things as needed. Kinda deep database talk and what not. Good session.

	Shop 1430		Calvin Chipman	8/17/2016	On a zoom session with Calvin. We fixed a small bug in switching to dynamic code for dates, strings (text values), and numeric. Once we got that fixed, Calvin showed me part of his clean-up process for changing the code between what was and what will be. Good session.

	Shop 1738		Working with Eric Tauer on an API	8/19/2016	On a GoToMeeting session with Eric Tauer from appLab in Salida, CO. Eric had a new API socket that he wanted to push up. We looked over some code, did some standardization, and then did some testing. We were missing some of the custom database tables so we push things live. Once it was live, we had to do some more testing and debugging. Normally we do all of the testing local and then push it live. This one, we had to flip that due to the custom nature of it. Once we got it all up and good to go, I showed Eric how to record the documentation portion of the project. We added the API socket documentation and went from there. The thing that took the longest was the live debugging. That is tough when you don't know where things are breaking because you don't have a good debugging tool on the live servers without making changes, pushing files, testing, and then altering files, and re-pushing files again.

	Shop 1739		In-line discount code with Bryan	8/19/2016	Bryan came over at 10 am. However, I was still working with Eric on a GoToMeeting session. He worked on some of his own projects while I finished up. Once we got working together, we went over some questions that he had. He made a couple of small tweaks and talked about his current projects. We then spent some time looking over a new project that Bryan will be doing and/or bidding out. Lots of prep and planning.

	Shop 1626		Adilas time	9/8/2016	Went into Logan. Nick drove. We did a small video shoot and interview to help promote both Adilas and BATC Custom Fit (department at Bridgerland Applied Technology College that has worked with Adilas to help with training and such). Both Nick and Shawn were there for the video shoot. Shawn took off after the first part and Nick stayed around until later that day. Shawn was super tired from pulling an all-nighter from his other job. One of the video sessions was us simulating talking with clients. We used Gloria from Bridgerland (marketing), by the end of the video shoot, we were really talking options and pitching Adilas. She and a lady by the name of Heather Ericson had interviewed me earlier, back in September of 2011 or 2013. That was kinda fun. The actual interview part was kinda fun but kinda nerve racking. Alan and Nick and I went to lunch and then afterwards Nick and I worked on some more sub inventory updates. We also did a small session on working on the Adilas API sockets and documentation stuff. Totally different day than most other days. Fun but different.

	Shop 1813		Quick Search for Media/Content	9/13/2016	We need to add media/content options to the adilas quick search. That would really help to look things up and bounce around as needed. This would need all of the normal key word searches as well such as: new, last, home, adv, numeric, and a basic alpha (text) search. That would be pretty cool.

	Shop 2676		Virtual Post-It Note	10/6/2016	- Conversions are starting to get bigger and bigger as well. How does that play in with the part weight field. - Part weight is playing in more and more - What do we want to do with that? Currently it is being used for gram control and/or an alternate multiplier. - We would love to be able to name that field and make it more standard. Currently they are using the catalog_page field (aka the bin number). We may need a couple of extra fields here. This field is a varchar (text field) and allows for both alpha and numeric values. In some of our code, we are having to check for numeric values and then doing multiplication. If it is not a numeric, we are treating it like a value of 1 which doesn't change anything. - We may need another unit of measure field to help with the part weight or some other key factor. - Go back to the parent/child relationships - Is this data needed on the parent or on the individual child. Expand on this. Also, this information may be part of the conversion process. Some of the data may need to be stored higher and then cascading downward. It also may need to be recorded on a per child or per mini conversion level. - The parent items may need a couple more fields that could be dynamic. We need both text and numeric data fields. Maybe thing shipping, ecommerce, weight stuff, alternate units of measure. For example: Say a single candy bar (1 each) may also need a spot to store the number of carbs or sugar content (2.7 milligrams or 5.67 fluid ounces or whatever). - What about other possible thresholds? Think broad... this may not go here, but we have sub inventory, sub attributes, flex grid, corp-wide settings, etc. What about real in-line extensions of the database. That might be really cool. If they want more or less fields, it would be really cool to allow that kind of functionality on the parent item level.

	Shop 1052		Adilas time	10/26/2016	On a GoToMeeting session with Steve, Nick, and Danny. We started out the morning looking at a custom label page that Danny was working on. His code was not part of master so we actually overwrote a small part of it. We got it all figured out and talked about the concept of who has the last cookie (version control)? We then worked in our own little blocks. I did some phone calls and worked on a custom file to create CSV (comma separated values) files. Nick was doing black box stuff. And Steve was bouncing in and out of the meetings. Towards the end, Eric Tauer (developer from Salida, CO) got on the call. We went over our plans for a new page that will help convert inventory items that are in a shopping cart from parent inventory to child inventory. Lots of talk and ideas on the subject. This is needed as we have a number of outside feeders that make quotes and then we have to restore those items to the cart for final checkout, fulfillment, and other user related tasks.

	Shop 1647		Adilas time	10/27/2016	On a GoToMeeting session with Nick, Alan, and Eric Tauer from Salida. We did some light introductions between the guys and jumped into a brainstorming session. Eric and I worked on the ideas and concepts to help with a new cart based page that converts a parent line item into a child or sub inventory line item. See attached for some notes and what not. As part of our session, we did a bunch of drawing and went through the needs and even progression of what is happening as things mature and evolve. Lots of ideas and concepts for the smart cart logic, pricing matrix options, and other tiered pricing stuff. I worked with Alan on some database and invoice API questions. I then spent the rest of the time working with Nick on our large merge project for the black boxes. We got in pretty deep into the cart logic. It is interesting that we keep finding these big hubs of activity and logic. The cart or shopping cart is a huge convergence of pieces and is virtually the gateway to the system.

	Shop 1648		Adilas time	10/31/2016	On a GoToMeeting session. Eric Tauer popped in and we chatted for a bit. I was doing some shop time clean-up and recording notes. I also got on a call with Dave Forbis and we went over a number of different items. He has been doing some demos and helping with project management stuff. We spent about half an hour going over the different projects and options. Dave has been a huge helper over the years. I spent the rest of the session cleaning up post-it notes and doing stuff inside the elements of time for the shop. Lots of recording notes and ideas. I've got a huge stack of post-it notes that need to be recorded.

	Shop 1832		Adilas Time	11/1/2016	On a GoToMeeting session with Steve, Alan, and Eric Tauer. We started out by letting Alan show us his progress on the state API connections he is working on. Eric then joined and he and I did another brainstorming session on the new cart functionality of converting a parent line item into one or more child inventory items within the shopping cart. See attached for some more notes (also expanded some of the older notes from last Thursday). Steve participated in the brainstorming session and brought some good ideas to the table. He is one of the key players that is literally on site with some of clients. Great asset.

	Shop 1053		Adilas Time	11/2/2016	On a GoToMeeting session. Eric and I were working on starting to convert a parent line item into a sub or child inventory line item. We spent most of the morning following and cascading a part_status value to the different pages. This will allow us to key off of this status and prompt and/or show what is needed. Most of these changes were done to existing frameworks and pages. The other guys were working on their own projects.

	Shop 1833		Adilas Time	11/3/2016	On a GoToMeeting session with Eric working on the convert parent line item to child line item page for the cart. Working more on the new page logic and actually building it out. Lots of testing and going back and forth between the brainstorming doc and the actual code page and logic. Making some great progress. About 11:15 am, we switched gears and Eric had to take off for a doctor's appointment. I then flipped over and started working on emails, text messages, and recording deposits. We got in a new loan amount from Kabbage to use to help get caught up and prep for some upcoming expenses.

	Shop 1960		ICS csv files	11/8/2016	Debugging some code for Eric and blum and the Green Door... it ended up being the custom tags cf_validate stuff...

	Shop 1054		Adilas Time	11/9/2016	On a GoToMeeting session with Nick and Eric and Josh (a client). We looked into the barcode issue with different quick cart searches. We talked about expanding functionality and/or change some wording as to what is being done. We did some light work and made some notes on what needs to be expanded and tightened up. Nick and I then worked on some top mini gram control bugs and issues. We had to fix 5 different files that didn't allow for transfer invoices based on their code. The last half of the meeting was back on the project that Eric and I were working on. We built out some more options on the convert parent to child inventory line item swap or conversion page. Working through the logic and making notes on what still needs to be done. Good session.

	Shop 1836		Adilas Time	11/10/2016	On a GoToMeeting session with Alan, Steve, Nick, and Eric. The meeting started out with Alan reporting on some of his API projects. We then helped both Steve and Alan with their joint project (state API connection stuff). We also spent a little bit of time talking about a current and future need to help sew different systems together. I drew some models and we talked about the growing need to interlace and virtually sew different systems together to help make things happen. We talked about our strategic placement of the external alternate id numbers in all of the main player tables and how at some point we may need to get into an application flex grid level to help mix and blend and sew things together. More and more needs are still coming. After that, Eric and I worked on the convert parent to child inventory projects. We advanced the ball for a ways and hit a virtual wall of sorts. The wall was noodle coded logic that was spread from page to page in a certain flow vs. a centralized method or function to handle the logic. We had numerous conversations and decided that we would take the time and convert the page logic into functions. This will be a slight side track but will help speed up this and future projects.

	Shop 1838		Adilas Time	11/15/2016	On a GoToMeeting session with Alan, Steve, Eric, and Nick. Eric and I were breaking out in-line code and logic and putting it into new methods for the shopping cart. We did have some small bugs that popped up in the main shopping cart and Alan was able to get those fixed while Eric and I were working. We did have some small tech supports issues that came up and we had to put out the virtual fires.

	Shop 1055		Adilas Time	11/16/2016	On a GoToMeeting session with Eric and Steve. We had a number of small bugs on data 6 that we had to fix during the session. Most of the problems were from missing files on the new server. Easy fix. Most of the rest of the session was spent building cart functions and changing from a page by page mode to a function based approach. We were working on the add new cart line item section. Light clean-up and testing along the way.

	Shop 1839		Adilas Time	11/17/2016	On a GoToMeeting session with Eric, Alan, Nick, and Steve. We spent the first part of the day reporting on what was going on with our different projects. Eric and I then worked on building out the cart functions. We were working on the add new cart line item function. The end all goal is dealing with the parent to child conversions and helping to standardize things. We also spent some time looking into the data 3 server. It seems to be having problems with the customer queue database table. We watched the server, the I/O read/writes, and the slow queries on the actual server.

	Shop 1840		Adilas Time	11/21/2016	On a GoToMeeting session with Nick, Steve, and Eric. We had to fix a couple sub inventory pieces on the data 3 serves. Eric and I then worked on building out the shopping cart functions and methods for the cart logic. This is our current internal project. The final goal is to help with the convert parent inventory line items to child line items section. This is kinda building up the underlying logic before plowing ahead. It is all kinda interrelated anyways.

	Shop 1841		Adilas Time	11/22/2016	On a GoToMeeting session with Eric, Steve, and Alan. We did some more testing on the new logic functions for the cart. Still working on breaking out in-line code for the cart into new methods. Started into some deeper testing. I had to take off early to go to a doctor's appointment. After I left, Steve and Alan worked on some state API socket stuff.

	Shop 2020		Ideas for customer permissions	11/22/2016	These ideas came from Russell Moore on 11/22/16. Basically, Russell was proposing an idea of adding simple numbers between 1-10 to help grant access to clients and what they could get at. Most of the permissions are for payee/users (people who work for a company or work inside the system). Russell had some ideas for people who work outside the company and/or customers or clients. He had the idea of the simple numbering options and then also a simple password type system. Basically, each entry (time, projects, invoices, media/content, etc.) has an id number and could contain a small password. The customer/clients could then be assigned a password access or tie-in to help us know who has access to what. Anyways, without getting too deep, it was a simple 1-10 numeric value and a simple password field that we could key off of. As a small side note, the adilas help files have an id and a password for every entry. Without the correct combo of both the password and the id, the correct help file will not show up. That is super simple, yet it provides enough security to protect what we are trying to protect. Good stuff. Keep thinking super simple. I love it.

	Shop 1056		Adilas Time	11/23/2016	On a GoToMeeting session with Eric and Steve. Eric and I started into the code on the update cart page. This deals with updating cart line items, recalculating taxes, recalculating discounts, and such. We are working on breaking out in-line code for the cart into new functions and methods. Today was mostly just a breaking apart some of the older code day. We are trying to get the code organized and lightly following a small mini plan that we made up. Good work session.

	Shop 1844		Adilas Time	11/29/2016	On a GoToMeeting session with Eric. We were pulling apart update cart line item logic and putting it into functions and methods. Lots of detail work and breaking things apart line by line. Light testing.

	Shop 1057		Adilas Time	11/30/2016	Eric and I were on a GoToMeeting session working on the cart logic. We worked on the update single line item method and then started into the recalculate the cart method. Lots of building and testing. Small side conversations back and forth as time allowed. Making some progress.

	Shop 1979		Adilas Time	12/1/2016	On a GoToMeeting session with Steve and Eric. Alan popped in for a bit as well. We worked with Steve this morning on some javascript stuff for his page. He did his first loops with javascript and we did some custom math stuff for him. He is learning and picking things up very quickly. After that, Eric and I worked on the update and recalculate methods for the internal shopping cart. We got all the way done with the first round of stuff and started to get into some testing. We still have a ways to go, but we are making good and steady progress every day. Good stuff. At the end of the day, Eric and I switched gears and added in a custom black box to the bulk cart labels page for printing PDF labels. We used the new custom option for creating mini access points. This allows us to create access points (data and logic portals) almost anywhere in the system on a per page basis. Super cool. I image we will be seeing more of this kind of stuff going forward. That sounds exciting.

	Shop 2036		Working with Steve - State API	12/6/2016	On a GoToMeeting session with Steve. We talked about some of the other developments of the day and our thoughts on how things are working out. Good stuff. We then worked on a new page that takes a big number (24 characters or more) and increments that number a set number of times on the page. We had to split the numbers into different sections and pieces. We then had to loop over things to see where it broke and turned into a non numeric value (the original value was a mix of alpha/numeric characters). Kinda random and crazy. Anyways, working on incrementing what values we could. We ran into problems with really big numbers and ColdFusion changing the numbers into scientific notation vs. a normal big integer value. We had to do some research online to get some ideas.

	Shop 2037		Working with Steve - State API	12/7/2016	GoToMeeting work session with Steve. I was doing emails and tech support stuff. I also worked more on the test page to help increment the RFID tag numbers. I had to add some code to help with a padding with 0's for the numeric data problem. Sent the file back to Steve.

	Shop 2042		Adilas Time	12/8/2016	Started off the day doing some clean-up and recording notes. I then started working on some new payroll changes from Shawn Curtis. Eric logged on to the GoToMeeting session and I helped him with some custom logic access points on a page that prints bulk PDF shopping cart labels. We got that finished and then pushed up the files to all servers. Shawn jumped on the GoToMeeting session from 11:30 to 1:30 pm. We started out merging files and working through payroll pages. We then switched gears and started talking about the future for time clocks, project time clocks, payroll tools, HR tools, and tracking sub payroll (tied to time). We also talked about recording mileage. I took a bunch of post-it notes worth of notes and scribbles. Here is what I got. - On elements of time, Shawn often records a location (for tax and mileage purposes) and what the task or project is. - Shawn would love to build a time clock feature that tracks mileage and is super easy to use. Kinda like Bryan's little time clock app. - Allow them to use a mini time clock feature - super simple and scaled back. Any special edits and/or other options would need to be done inside of the normal system. - Allow for departmental or department based logins and time clock options. This could be normal payroll clock in/outs and/or elements of time and project based clock in/outs. - Make sure and look at both Russell's time clock mock-up as well as Bryan's little time clock app. Maybe look at Toggle and even older adilas notes and ideas. Keep it simple. As a side note, this need has existed for years. If we think back, time cards and time clock stuff came right after stock/units back in the early 2000's (2002-2003 ish). There is still a need even today for more tools like this. - Add a small mileage tracker that could be connected to elements of time. It might be nice to either be used as a standalone project and/or an app that can be connected to elements of time. Make the connection to elements of time optional. - We need to allow settings per person for what projects to show up and how to sort and show those simple selection options. - Show the amount of time that has lapsed... - Use simple start and stop buttons. - On the mileage subs of time, tie to an employee name (payee id). That will make it searchable later on. - help search by person and show totals based off of a date range and/or a project selection. Basically, allow for some advanced search options for the mileage reports. - One of the main goals is to limit the number of clicks that a user has to make to get something done. Keep it super simple. Maybe even its own interface with limited functionality. - Simple buttons to clock in and clock out... We do all of the mapping and logic behind the scenes. - Setup a mini skin or something like it. Allow for departmental clock in/outs, single payroll clock in/outs, project clock in/outs, and mileage options. Make all of these pieces toggle on/off options that could play into the same interface if needed. Think settings and dynamic point and click setup. - Make a number of small and simple tasks. Use the power of adilas but make it look super simple. We could do this for all kinds of features and functions. This might be worth exploring and assigning small teams to build out certain parts and/or sections. - Make the look and feel super customizable (colors, placements, buttons, features, etc.). - What about sub flags and tags... That section is brand new and could help with things like sub phases, sub locations, or even different departmental levels for project time (x department charges $50 per hour and y department charges $35 per hour, etc.). That could be pretty cool to help track different rates. - Along with the comment on sub tags and flags... What about holding amouts, time sums (math on the start and end times), and even some billing and/or invoice options. That would be really cool. - On the mileage settings as a sub of time, setup a preset matrix so that you could enter common destinations and/or sub locations. For example, say I always want to record mileage from my house to the shop/office or from my house to my parent's house. It would be really cool if we could preset these values as round trip and/or one ways. This could be based from work, from home, from wherever, as long as it is consistent. - The matrix of sub locations and/or preset mileage settings could even have fields like: mileage alias name (generally what do you want to call it), a from location, a to location, one way mileage (value), round trip mileage (value), sort values (manual sorting option), and a status (active/show or inactive/hidden). These settings could be on a per person basis or on a corp-wide basis. Maybe even use JSON storage for the settings. - What about GPS stuff? We have the fields to hold those values. What if we used an app and got where are you? Where are you going? Where are you now? - What if we had full GPS stuff being tracked for super cheap. Think of a small phone app or something like that. Maybe a small app that piggy backs on a phone or mobile device and then used an API to talk to adilas. That would be pretty cool. - We could add up mileage, do point to point mileage, use full GPS stuff, or just allow for user entry into an open mileage field. It could be super techy or crazy simple. Lots of options. - What about billable hours? We already allow for sub dates and times to be pulled into invoicing. This has existed since 2011. What is the next level? What if we had ways of flagging things with some kind of invoice status and/or billing info. What invoice, is it billable, not billable, has it been billed, does it need to be billed, what is the rate, etc. Think of the next level. We could expand sub dates and times or we could build it into sub flags and tags stuff. - As Shawn was talking, I had the idea, what about cross corp billable hours. Say one company is working on a project for another company. Wouldn't it be cool if a small mini channel and/or tunnel could be made to bridge one corp to another corp. Basically, a user logs in to their corp and is able to make a small time clock record in another corps project. This would have to be permissioned, allowed, agreeded upon, and API socket based connection. Still, that would be pretty cool. - Think app enabled functionality. Think mini skins and/or standalone mini mobile apps. - Be able to quickly switch tasks, projects, etc. Minimal number of clicks. There may need to be a different admin page, but the main interface could be quick and fast. - Shawn wanted to make simple setup wizards to help do the settings and management stuff (admin/manger side). Easy to use and virtually hold your hand through the process. - What about the sub payroll functions and features. That was planned out lightly back in 2011 but has not yet been fully built out. The database tables exist, the ideas and concepts exist, but it has not yet been built out. Maybe it is time. We need to allow these new apps and settings to go all the way out to sub payroll. This could be for employee time clocks and/or project time clocks. Tie things up all the way along. - We will need an admin and payroll dashboard of sorts. This is where an admin and/or manager could get their reports and check on things. Quick reports, easy access, permissioned, and able to see and get to reports and stats quickly. - What about accruing payroll. Currently, that is somewhat hard to put your finger on. By accruing, I'm meaning what is building or amounting in the background. Imagine being able to see what hours and bills are mounting before they hit. Instead of a developer or another employee submitting a huge bill that you didn't know about, you could watch things grow as they happen. Think, what will need to be paid and/or what is value of project X or Y. - Along with accruing payroll and such... It might be nice to go into the smaller entries and do some math on them and store those values in the database. You could then pull quicker reports vs. calculating hours, minutes, and seconds on the fly. That can be a pain. Look into this as an option to help speed things up. - Take what we have already got and put it together in a new skin or interface or mini package of sorts. Most of the underlying pieces are already done. It just needs to be combined and wrapped up together in a cute little sellable, presentable package. - What about other HR (human resources) tools? Branch out a bit and think and/or ask what people need. People will tell you if you ask the right questions. - Map it out and then pitch it as a proposal. Think of the bigger picture. It might also help to think of both short term and long term options. - Dream it up, we'll help you wire it up!

	Shop 2048		Adilas Time	12/13/2016	On a GoToMeeting session with Eric and Steve. Eric and I were working on the new shopping cart methods and converting in-line code into standard methods that we could use over and over again. We spent most of the session working and testing the update cart line item functions. We also cascaded some of the code to other pages. Trying to standardize things.

	Shop 1059		Adilas Time	12/14/2016	On a GoToMeeting session with Steve, Eric, and Nick. We spent the first hour looking over the data 3 server and trying to see if we could see any problems and/or slow down areas. We did see some customer queue issues with slow queries and waiting for table locks. After that, Eric and I worked on the convert parent to child pages and logic for the cart. We read over the pages we did a couple weeks ago and then got back into the swing of things. We added some new logic to swap cart line items and also to remove and add new line items. It is getting closer.

	Shop 2049		Adilas Time	12/15/2016	On a GoToMeeting session with Eric and Steve. Most of the session was used up by Eric and I working on the convert parent to child inventory page for the shopping cart. We spent quite a bit of time working on the scanning line item process and logic. We also went back through the brainstorming document and did some light clean-up on what was needed. Good session.

Showing 150 of 988 Page 1 of 7 :: Go to page ::

What's New

Products

Find Us