all data is live and searchable
[reset this page] .
[historical web outline - entries by month] .
[adilas community funded projects] .
[contact adilas.biz support - email form] .
[help]
|
Adilas.biz Developer's Notebook Report - All to All - (201)
|
||||||
|
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 1475 |
|
Daily Ideas | 8/21/2009 |
-When searching for vendors, show link to payables for that vendor similar to customer and receivables. -Maybe allow for horizontal logos. 166 _w x 83 _h vertical logos would create a problem with spacing. -Cleanup all of the extra cf output tags on older files, this could take a while. -From Post-it notes: - Send the email from contact - What about customer support packages or setup packages - Include disclosures about setup and free tech support - Paid vs. free support Brainstorming on adilas: • extra notes added at random later times -On the adilas home page I would like the following pieces: no specific order - Log in - Sub links and nav - Small Flash animation with key points - System history reports with the following rows and columns: (Vision…) o Date switch (just for fun – in case people want to play around with different dates) o Look up date: _________, Submit – 7 Days, Prior, 30 Days, Prior o Application type: Look up date (Value – Count), 1 Day Prior (Value – Count) Drill downs: - Deposits - Invoices - PO’s - Expense/Receipts - Checks printed - Reimbursements - BSI (spelled out) - New stock/units - Sold stock/units - Quotes - Flex grid tie-ins - Time cards - General stats - Customers - Vendors - Parts/Services/Products/Accessories - Permissions -Maybe include photos -What’s new at adilas! -SIMPLE… make it easy… -Let people know what we’ve got… sell it… - Roll call accounting - Status accounting - Adilas university - Accopps - Adilas referrals Non date specific stats for adilas users: - About us and adilas history page - Simplified features list - Icons for desktop - Privacy policy -General System Info * (Up towards the top) similar to main application types and their drill-downs. -Submit a request/ticket -Contact us general price/quote -Flyers -Site may – add all text versions (not pdf links) and add link to adilaswebservices developer help -About us – FAQ’s with basic info -Other services and merchant processing -Once we drill-down from a main application type to a subpage… we need the following: - Screen shots - Tutorials - Overview - Sub topics - Theory/concepts - Audio (even if it only reads the page for you) - Cause and effect relations - Advanced tips and tricks - (Internal) side note (from inside adilas) – maybe have a link to the main subpage (explaining it) from the different home pages. - Navigation that allows them to jump to a new topic or section. Maybe a drop-down box with main application types or concepts. FEATURES - Too many to list - Inventory - Accounting - Operations - Reports - Financials - Digital filing - Joined system ADVANTAGES - Tons - Real time - Under one roof - Low cost - No contracts - Open 24/7 - Any computer - Any time - Easy access - Customizable BENEFITS - Peace of mind - Save money - Make more sales - Time management - Real time - Know down to the penny where you are at - Provide your accountant with good numbers -Add free calculators for payments and financing and profit and discount. -Finish up galleries – Deposit, Customer, Vendor/Payee, Employee -Focus on positive action words -Payroll: - Look how easy - Hourly - Commission - Mixed, etc. - Reports -Sales tax: - Reports, multi locations, special taxes -Web presence: - Automatic, instantaneous, dynamic, on the fly, photos -Photo galleries: - Point and click - Scans, photos, documents, paperwork, etc. - Paperless – going green - Easy filing – enter, scan, upload, number, done! -Searchable: - Alost anything right at your fingertips on every screen - Quick search -Simple to complex: - Whole system tries to follow this strategy - Reports – General, drill-down, details -Operations, operations, operations: - Easy, intuitive, real-time, resources, permission-able -Logical next step: - Start here, get comfortable, when you’re ready, we’ll take you to the next step. - Trying to make it dummy proof -Flexible and dynamic: - Tie anything together - Spider web – tons of ways around the horn - 3-D relations - Flex grid - Natural tie-in • Catch the vision…. - Add some hype - Add some vision - Get people to buy into the vision not necessarily the application. -Start to finish number: - Enter or create, monitor the status or states of being, ice it down when done, move on • One of my main goals is to have our site and files super search engine friendly. What do people search for, for accounting and operations software, packages, hosted solutions, tool sets, etc. -Inventory tracking: - Bring it in, move it around, sell it, archive it, next - Instantly update your online web site by doing normal daily work flow. Real time, change a price, it changes, add a photo, it’s there, sell it, it shows it. • How do you describe what we do… - See list of domain names - We catch the data at the point of action and then allow look-ups and searches on the records in a time based environment. - We see a need and amp the course to the goal. -Help and tech support: - Help files - Video tutorials - Power users - Email and phone support • Old vs. new methodology – “Bridge the gap” - T-accounts, general ledger, debits, credits, posting, chart of accounts - Roll call technology, linear, life cycle, status - “Bridge the gap” -eCommerce and shopping cart: - Get it, show it, sell it, do it again - Merchant accounts - Integrated into inventory counts and quantities - Electronic payment processing • adilas tool set: - Pick and choose - Customize -Web services: - Custom look and feel - Adilas functions and data streamed over the internet to provide custom features for employees and customers - We do the work, you reap the benefits • We trap and catch all the details – once you have all the data, it is just a matter of showing it back in a report that is readable. -Financials: - P&L - Sales reports - Expense tracking - Aged Receivables - Aged Payables - Inventory Tracking - Balance Sheet - Banks • Cut-out the bottle necks and need for multiple (double or more) entry. - Share the work load - Permission based - Role based • Started out as a custom write-up system. Moved to the commercial level. Many companies have similar needs. Code once, use many. -Bank friendly: - Verify - Reconcile - Outstanding checks and deposits - Daily bank balances - Online check printing - Positive pay (coming soon) - Deposit and check register • Future development and optimization – explain the piggy back system and modular architecture. -Easy as surfing the web: - All the web basics apply - Back button - Super back button - Forms - Reports - Links - Multi windows - Copy and paste • Save, store, print – converts to pdf options, every page is printable. • New words specific to adilas: - Roll call accounting - accopps - Operation based accounting - Flex grid - Expense/receipt - Transition invoice -Manufacturing: - Internal invoicing - Outside repairs - Recipe/builds - Security & privacy -Reoccurring Invoices: - Create a master - Set up the reoccurring frequency - Point and click - Bulk invoicing - Customizable - Custom verbage - Corp-wide setting - List of options and possibilities – see the corp-wide settings page for options. Maybe even include a dummy link and form to show options -Receivables: - Aging - Statements - Apply payments - Settings and terms - Light-weight Client - Low overhead - Minimal system and IT requirements - Browser-based, web-based - Hook to your own printer - Cut you IT costs - No hardware to buy - No upfront software fee or contract -Payables: - Aging - Reimbursements - Splits – payments on account - PO’s - Stock/units - Payroll - Taxes and other collected items • Web hosted solution – web based • Modular application – each page is tied to a permission and completely independent – small and modular. -Customers: - History - Log files - Multi contacts - Receivables - Quotes - Statements - Invoices - CRM functions - JIT – Just in time – approach • Event driven updates • Simplified Approach: difference between acronym for special functionality CRM, CMS, ERP, Cloud Computing - Roll call accopps. Debit, credit, general ledger, chart of accounts, adjustments - linear accounting. PO’s all in one. -Check Request: - Submit, review, approve, print - Review every expense before it leaves out the door - Ability to approve checks while away from the office - Keep up to date tabs on bank balances • Centralized database solution, cloud computing, cloud accounting. |
|
|
AU 1585 |
|
Daily Tasks | 12/29/2009 |
• Went up to Buena Vista to work with an associate. Created a general outline of what we wanted to do. We talked about marketing ideas and potential from adilas. We spend a lot of time talking about video tutorials. 50 miles. • Ordered a new hosting plan for adilas university. • Updated some settings for Steve’s company website, paid for outstanding service owed. • Purchased new domain names for New School Accounting (.com & .biz) • Working on new 2010 tax tables and settings. |
|
|
AU 2398 |
|
Brainstorming - Adilas University & Adilas Marketing Ideas | 12/29/2009 |
Adilas University & adilas Marketing Ideas Video Tutorials - Web basics (1.1, 1.2, 1.3) - Stuff - Theory (2.1, 2.2) - Old vs. New - Start at entry level (FAQ’s) - Server based (FAQ’s)] Marketing - YouTube - Business magazines - Pay per click - Remote Training Classes - Trade shows - Search engines - Door to door - Referral - Webinars - Newspaper - TV (Review sites) - Radio (Review sites) - Our website - Links and banners - Tele marketing - Email campaign - Updates - Newsletters Adilas University - Should it be 80 – 90- 100% video training? - Email opt in for videos Leather on the seats - Fluff |
|
|
AU 3563 |
|
2010 | 1/1/2010 |
YEARLY ACCOMPLISHMENTS 2010 Steve, This is a list of things that happened and accomplishments made during the 2010 year on adilas. It was a great year with tons of great stuff. If you need more detail, just let me know. I have everything documented down to the date. January 2010: • Brandon and Andy created their first video tutorial. It never got published but it was a 4 minute video on using the adilas shopping cart. • Small face lift to the main adilas.biz site. Added the cloud background. • Created a number of new flyers. Added options for dynamic name and contact info. • Lots of brainstorming on marketing, what do we do, and how can we get it out to the people? • Came up with a new slogan: Your date, you cache & retrieve it, we secure it. • Prep and research for the dewy decimal system. • Encoded sensitive database fields for storage. Examples: bank accounts, routing numbers, customer and employee SSN’s, driver license numbers, EIN’s, and usernames. Passwords were already encoded prior to this. • Added a forgot password helper page. February 2010: • Added a multiplier for the recipe/build prep page. • Added the add as advanced PO line item page. This page allowed for mini conversion calculations during the add line item process. • Added new PDF forms. 1 for Texas and 2 for Colorado (paperwork). • Posted the first round of the dewy decimal stuff online. Hundreds of files were updated. • Small fix on internal transfer invoices. Added current costs to items. March 2010: • Added units of measure to parts, PO’s, invoices, and quotes. • Activated corp-wide settings: show bin numbers, show unit of measure, and show line item numbers. • Steve loaned some money to adilas. Thanks! • Added a sort order option to PO and invoice line items. Included a bulk sort page for changing multiple sort values at a single time. • Added code to help automate bad debt payments. • Added the profit and discount calculator. Linked up the profit and discount calculator with the loan payment calculator. • Brandon and Andy worked on some marketing ideas. • Added a tools and features list to the main adilas.biz homepage. Also a small scrolling flash movie with the features. Most of the ideas came from Brandon and Andy’s marketing sessions. April 2010: • Added special line item settings to the corp-wide settings. Over 100+ fields. Things like: Labor, Supplies, Other, Collected, Fee, Dealer Handling, Discount, Freight, etc. • Added a merchant processing prep step to help speed up the transactions. We were experiencing long wait times (every once in a while). • Added a grouped customer log report. • Added the profit percentage to the global parts mark-up tool. • Added a price helper field to the add/edit number page. Local java script to help with profit margins, mark-ups, and pricing. • Added a price switch to trailer and toppers. They were always a mark-up value and we added options to choose between a list price and the mark-up value that was calculated on the fly from the basis. • Applied the stock/unit price switch to all stock/units and made it part of the global stock/unit mark-up tool. May 2010: • Created the mini invoice or 3” customer receipt. • Added the last 4 of the credit card numbers to the payment notes for reference. • Tons of time working onsite at an adilas client’s. Great ideas and training ground. • Added the barcode generator. Added page tie-ins and posted a free barcode generator on the main adilas.biz homepage. • Added a recalc taxes switch for invoices with multiple locations. This is an after the fact deal and allowed for items to be pulled from one location and then flipped to another location. The taxes would be recalculated and invoice values changed. • Added the financial flow calculator and worksheet. June 2010: • Spent more onsite time at a client’s (on and off throughout the entire month of June). • Added a new tax category called “With Tax Included”. This helps back into a bottom dollar value. • Added a discount calculation option right from the profit and discount calculator page. • Added a printer friendly link to the printable PO page. Took off all of the extra navigation and quick search info. • Lots of new corp-wide settings. Added the barcode quick cart, quick cash checkout, number of payments on checkout, customer web settings, show/hide prices, web return address, and barcode label sizes. • Changed all of the disabled/helper fields to a light blue color with black text. The old way was a white field with a light grey text value. The new fields stand out and are easier to read. • Added the PO quantity to the add/edit parts page. This is really handy when adding new parts from within the PO line items mode. • Added the apply quick discount to the edit cart line items page. • Added the auto calculate change due setting. Recorded the info and helped show the actual change due. July 2010: • Brandon and family moved from Salida, CO to the Logan, UT area. Salida was the birth place of adilas.biz application. Spell Salida backwards… you get adilas. (2001-2010 9 years) • Added tons of new details to the grouped daily/weekly reports. Showed tons of new break-downs and details with drill-down links to underlying data. • Added a corp-wide setting to help limit and/or open up location specific inventory tracking. • Major push to activate all existing corp-wide settings. Didn’t actually complete until August 2010. • Added the key word “All” to all of the quick searches. August 2010: • Combined a push on all of the corp-wide settings. • Added external customer PO #’s to invoices and quotes. • Finished up the basic corp-wide settings. In all, updated and changed over 700+ files in all. Files were from the main adilas.biz site, secure backend, data components, web/customer files, etc. • Did some page clean-up and added some CSS (style sheet) changes to every page in the site (while checking for corp-wide settings). Tightened up the overall look and feel of the application (minor changes to the eye but helped to standardize code and flow). • Added new drill-down links to the history homepage report. • Created the mini version of the daily/weekly report (3” format). September 2010: • Added a corp-wide setting for specific unit names. • Added a new global find and replace part number feature or tool. • Added the first round of the advanced add to cart section or page. • Added a gateway connection to the Merchant One online credit card gateway. This was the second merchant processing option for adilas customers. • Added a test page for all merchant processing accounts. • Did a full rework on the USAePay gateway code and merchant processing code. This rework eliminated the random slow connections and made the entire system seem like it was working as fast as lightning. USAePay was the original merchant gateway added to the adilas.biz system (11/2009). October 2010: • Tons of brainstorming and documenting ideas and concepts. Worked on mapping out system players and processes on paper. • Created an interactive map of the adilas business platform. Map is just in concept stage and was drawings and graphics. Used a “building” layout to show players, concepts, and virtual departments. The building metaphor has rooms, sections, hallways, doors, and shows relative connections of the pieces (strategically placed items to show flow and relationships). • Presented the map concept during a whiteboard session in Salida. • Added all special line items, as their own group, to the history homepage as drill-down links. • Lots of brainstorming on the scheduler application and the element of “time”. • Ordered a new dedicated server for adilas.biz. • Switched to ColdFusion 9 as our scripting environment. • Tweaked the code that deals with changing part numbers. New code will help to cascade changes to the appropriate other tables. Much cleaner and hug time saver. • Went to live on the new dedicated server. Saw major increase in uptime and speeds. • Put up the first round of the adilasuniversity.biz site. Small graphic with some links and some verbage. November 2010 • Added some new filters on the update inventory counts pages. They were a barcode filter and a vendor quick switch field. • We have over 100+ domain names pointed to the adilasuniversity.biz site. This is mostly for future marketing and domain real-estate protection. • Added a link right from the default photo (thumbnail) to the add/edit photo page. Idea came from a guy named Logan out of Denver, CO. • Added a total or bottom dollar value to the advanced add to cart page. • Full rework on the advanced add to cart section. Included tax calcs, back calcs to quantity and prices, discounts, mark=ups, etc. • Added the part category as a filter on the main part number search. • Added the my cart favorites section. This is a user-maintained dynamic button section that allows for searching of parts, recipe/builds, adding items to cart, displaying advanced add to cart options, and custom setting (quantity, price, and description). • Brainstorming on adilas university and a multi-media training tool. December 2010: • Added a special my cart favorites search part number interface. • Posted an out of business note on the Morning Star Automotive website. The turning of an era! Thank you Morning Star! You got us where we are today! (site will be left up as a demo site) • Added buttons to create new items (deposits, carts, invoices, quotes, PO’s, expense/receipts, BSI, etc.) • Added show/hide toggle buttons to show/hide the main search criteria for reports. • Added the “Any” name option for customers and vendors. • Reworked the customer payment history report. Allowed custom settings to be applied and the ability to hide the deposit info. Basically, a printable customer payment history report. • Added a checkbox to help keep the search criteria open if needed (got a little too aggressive on the show/hide options). • Condensed the PO location/contact info for printable PO’s. • Working on a graphic version for the interactive business platform map. Really excited about the future! |
|
|
AU 2149 |
|
Brainstorming adilas.biz Website Layout | 1/12/2010 |
Main adilas.biz website layout: Home: - Page Elements: o Introduction o System History (design & meat – with date) o Flash Key points (design element) - Privacy - FAQ’s - Login (form & link) - Contact Us - Pricing - Flyers - About Us - Site Map - Features - Video Tutorials - Search Web Inventory - Testimonials - Other Products - Demo Header Bar or main links: - Home - Login - Features - FAQ’s - Flyers - Video Tutorials - Pricing - About Us - Contact Us - Search Web Inventory Footer Bar: - All of the header values… plus privacy and site map Side Notes: - Business - System - Application - Tools set - Web online Old Drop-Downs: Home: Adilas System: - Tools & Features - Our approach - FAQ’s - Permissions - Pricing - Schedule Demo - Vision of the future Customer Service: - About us - Contact us - Testimonials - Get a quote Training: - Video tutorials - Adilas university - Old school vs. new school - How to…. Marketing: - Flyers - Other products and services - Pricing Search Web Inventory: Newer version of drop-downs below: (the older version of these drop downs is directly above) Home: - On the main homepage this will flip to login Adilas System: - Tools & features - Our approach - FAQ’s - Pricing - Permissions - Vision Training & Education: - Video tutorials - How to’s…. - Old school vs. new school - Adilas university Sales & Marketing: - Flyers - Testimonials - Other products & services - Pricing - Employment Customer Service: - About us - Contact us - Get a quote - Schedule a demo Search Web Inventory: |
|
|
AU 271 |
|
Daily Tasks | 10/30/2010 |
• Testing the new server and seeing how things are going. Found a couple of issues that will need attention at some point. • Started working on the first round splash page for adilas university. Finished up and launched the adilas university website. It had some links, a graphic that says “reach new heights” and has some graduates throwing their graduation hats in the air. It also had four paragraphs worth of info about adilas and what we are trying to do. Small but good start. • Originally added a couple of sentences that talked about a 3D object and time based model. I went on a run with my data and he thought that I should take that out until we own it and can prove it… basically, how can we protect ourselves until we get it done. • I called and talked with Steve about it. We need to finish up the last couple puzzle pieces and make sure everything can play together. |
|
|
AU 307 |
|
Daily Tasks | 11/30/2010 |
• On the phone with Steve going over the needs for people to view and use multi-media training. We also talked about using the interested company to help fund the project and development costs. • Spent some time brainstorming on adilas university and the multi-media training application. • Wrote an email proposal (light and loose) to my dad and his associate about having adilas.biz be involved in the project for the training application. • Spent some phone time with customers going over the flex grid tie-ins and how to use them to track serial numbers. Sent them a small recap on the phone conversations. • Started working on the new my cart settings for the custom add to cart options. This includes fixed quantities, fixed prices and fixed descriptions. • Added a new logo for a company. Posted colors and logo online. • Full database back-up. |
|
|
AU 311 |
|
Daily Ideas | 11/30/2010 |
Ideas for the adilas university multi-media training application: -Secure multi-media player. By 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 presentations, still images, automated output, etc. -Be able to mix and match what the player can do… -The end goal is to automate as much as possible. We may have to take some steps to get to that stage. -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). -Usage histories – every time a user views a clip – we record a history note behind the scenes. Random idea – may show the user which ones they have seen and when. Maybe even a started and completed flag. -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. -On usage histories – it may also be cook 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. -This usage history would also need some special reports to help managers and trainers know that is being viewed and what might need a touch-up or re-visit. -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. -What about a valid login plus and IP address – additional security? Just an idea. Maybe a white list of IP addresses. Then again this makes it more technical. Maybe leave it out until we really need it. |
|
|
AU 3564 |
|
2010 | 12/31/2010 |
YEARLY ACCOMPLISHMENTS 2010 Steve, This is a list of things that happened and accomplishments made during the 2010 year on adilas. It was a great year with tons of great stuff. If you need more detail, just let me know. I have everything documented down to the date. January 2010: • Brandon and Andy created their first video tutorial. It never got published but it was a 4 minute video on using the adilas shopping cart. • Small face lift to the main adilas.biz site. Added the cloud background. • Created a number of new flyers. Added options for dynamic name and contact info. • Lots of brainstorming on marketing, what do we do, and how can we get it out to the people? • Came up with a new slogan: Your date, you cache & retrieve it, we secure it. • Prep and research for the dewy decimal system. • Encoded sensitive database fields for storage. Examples: bank accounts, routing numbers, customer and employee SSN’s, driver license numbers, EIN’s, and usernames. Passwords were already encoded prior to this. • Added a forgot password helper page. February 2010: • Added a multiplier for the recipe/build prep page. • Added the add as advanced PO line item page. This page allowed for mini conversion calculations during the add line item process. • Added new PDF forms. 1 for Texas and 2 for Colorado (paperwork). • Posted the first round of the dewy decimal stuff online. Hundreds of files were updated. • Small fix on internal transfer invoices. Added current costs to items. March 2010: • Added units of measure to parts, PO’s, invoices, and quotes. • Activated corp-wide settings: show bin numbers, show unit of measure, and show line item numbers. • Steve loaned some money to adilas. Thanks! • Added a sort order option to PO and invoice line items. Included a bulk sort page for changing multiple sort values at a single time. • Added code to help automate bad debt payments. • Added the profit and discount calculator. Linked up the profit and discount calculator with the loan payment calculator. • Brandon and Andy worked on some marketing ideas. • Added a tools and features list to the main adilas.biz homepage. Also a small scrolling flash movie with the features. Most of the ideas came from Brandon and Andy’s marketing sessions. April 2010: • Added special line item settings to the corp-wide settings. Over 100+ fields. Things like: Labor, Supplies, Other, Collected, Fee, Dealer Handling, Discount, Freight, etc. • Added a merchant processing prep step to help speed up the transactions. We were experiencing long wait times (every once in a while). • Added a grouped customer log report. • Added the profit percentage to the global parts mark-up tool. • Added a price helper field to the add/edit number page. Local java script to help with profit margins, mark-ups, and pricing. • Added a price switch to trailer and toppers. They were always a mark-up value and we added options to choose between a list price and the mark-up value that was calculated on the fly from the basis. • Applied the stock/unit price switch to all stock/units and made it part of the global stock/unit mark-up tool. May 2010: • Created the mini invoice or 3” customer receipt. • Added the last 4 of the credit card numbers to the payment notes for reference. • Tons of time working onsite at an adilas client’s. Great ideas and training ground. • Added the barcode generator. Added page tie-ins and posted a free barcode generator on the main adilas.biz homepage. • Added a recalc taxes switch for invoices with multiple locations. This is an after the fact deal and allowed for items to be pulled from one location and then flipped to another location. The taxes would be recalculated and invoice values changed. • Added the financial flow calculator and worksheet. June 2010: • Spent more onsite time at a client’s (on and off throughout the entire month of June). • Added a new tax category called “With Tax Included”. This helps back into a bottom dollar value. • Added a discount calculation option right from the profit and discount calculator page. • Added a printer friendly link to the printable PO page. Took off all of the extra navigation and quick search info. • Lots of new corp-wide settings. Added the barcode quick cart, quick cash checkout, number of payments on checkout, customer web settings, show/hide prices, web return address, and barcode label sizes. • Changed all of the disabled/helper fields to a light blue color with black text. The old way was a white field with a light grey text value. The new fields stand out and are easier to read. • Added the PO quantity to the add/edit parts page. This is really handy when adding new parts from within the PO line items mode. • Added the apply quick discount to the edit cart line items page. • Added the auto calculate change due setting. Recorded the info and helped show the actual change due. July 2010: • Brandon and family moved from Salida, CO to the Logan, UT area. Salida was the birth place of adilas.biz application. Spell Salida backwards… you get adilas. (2001-2010 9 years) • Added tons of new details to the grouped daily/weekly reports. Showed tons of new break-downs and details with drill-down links to underlying data. • Added a corp-wide setting to help limit and/or open up location specific inventory tracking. • Major push to activate all existing corp-wide settings. Didn’t actually complete until August 2010. • Added the key word “All” to all of the quick searches. August 2010: • Combined a push on all of the corp-wide settings. • Added external customer PO #’s to invoices and quotes. • Finished up the basic corp-wide settings. In all, updated and changed over 700+ files in all. Files were from the main adilas.biz site, secure backend, data components, web/customer files, etc. • Did some page clean-up and added some CSS (style sheet) changes to every page in the site (while checking for corp-wide settings). Tightened up the overall look and feel of the application (minor changes to the eye but helped to standardize code and flow). • Added new drill-down links to the history homepage report. • Created the mini version of the daily/weekly report (3” format). September 2010: • Added a corp-wide setting for specific unit names. • Added a new global find and replace part number feature or tool. • Added the first round of the advanced add to cart section or page. • Added a gateway connection to the Merchant One online credit card gateway. This was the second merchant processing option for adilas customers. • Added a test page for all merchant processing accounts. • Did a full rework on the USAePay gateway code and merchant processing code. This rework eliminated the random slow connections and made the entire system seem like it was working as fast as lightning. USAePay was the original merchant gateway added to the adilas.biz system (11/2009). October 2010: • Tons of brainstorming and documenting ideas and concepts. Worked on mapping out system players and processes on paper. • Created an interactive map of the adilas business platform. Map is just in concept stage and was drawings and graphics. Used a “building” layout to show players, concepts, and virtual departments. The building metaphor has rooms, sections, hallways, doors, and shows relative connections of the pieces (strategically placed items to show flow and relationships). • Presented the map concept during a whiteboard session in Salida. • Added all special line items, as their own group, to the history homepage as drill-down links. • Lots of brainstorming on the scheduler application and the element of “time”. • Ordered a new dedicated server for adilas.biz. • Switched to ColdFusion 9 as our scripting environment. • Tweaked the code that deals with changing part numbers. New code will help to cascade changes to the appropriate other tables. Much cleaner and hug time saver. • Went to live on the new dedicated server. Saw major increase in uptime and speeds. • Put up the first round of the adilasuniversity.biz site. Small graphic with some links and some verbage. November 2010 • Added some new filters on the update inventory counts pages. They were a barcode filter and a vendor quick switch field. • We have over 100+ domain names pointed to the adilasuniversity.biz site. This is mostly for future marketing and domain real-estate protection. • Added a link right from the default photo (thumbnail) to the add/edit photo page. Idea came from a guy named Logan out of Denver, CO. • Added a total or bottom dollar value to the advanced add to cart page. • Full rework on the advanced add to cart section. Included tax calcs, back calcs to quantity and prices, discounts, mark=ups, etc. • Added the part category as a filter on the main part number search. • Added the my cart favorites section. This is a user-maintained dynamic button section that allows for searching of parts, recipe/builds, adding items to cart, displaying advanced add to cart options, and custom setting (quantity, price, and description). • Brainstorming on adilas university and a multi-media training tool. December 2010: • Added a special my cart favorites search part number interface. • Posted an out of business note on the Morning Star Automotive website. The turning of an era! Thank you Morning Star! You got us where we are today! (site will be left up as a demo site) • Added buttons to create new items (deposits, carts, invoices, quotes, PO’s, expense/receipts, BSI, etc.) • Added show/hide toggle buttons to show/hide the main search criteria for reports. • Added the “Any” name option for customers and vendors. • Reworked the customer payment history report. Allowed custom settings to be applied and the ability to hide the deposit info. Basically, a printable customer payment history report. • Added a checkbox to help keep the search criteria open if needed (got a little too aggressive on the show/hide options). • Condensed the PO location/contact info for printable PO’s. • Working on a graphic version for the interactive business platform map. Really excited about the future! |
|
|
AU 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 3626 |
|
No Dates: Adilas Application & Sales Brainstorming | 1/1/2011 |
Scan 1 – Planning what needs to happen in different parts of adilas – categories, items, priorities… Category – Item: - PO’s – Items on order/in transit - Time – Round 1 Elements of Time - General – Email support - Web - eCommerce - Customer – Customer pay portal - Reports – All grouped reports – Be able to go back and forth - Reports – Direct links to sub actions - Web – Adilas University - Photos – Secure Images and use content server - Look & feel – My Quick Buttons - Look & feel – Graphics & icons - Taxes – Sales tax & collected fees - B.S.I – balance sheet round 4 - Training – Roll Call Page - Reports – user history - Reports – financial Roll Call history - Training – Interactive business platform - Training – General user manual - Training – Adilas theory - Time – Online reservations - Web – main adilas face lift - Web – automation for crop sign-up and setup - A/P – Payables rework - Flex Grid – Reflexive side of the flex grid - Photos – Upload pdf - Invoices – Interactive shopping cart and interactive quotes - Payroll – Payroll rework - Training – Map out entire system - Photos – Be able to replace the mini thumbnail for photos - Reports – Graphs & charts - Reports – Visual eye candy – dashboards - Photos – Other photo galleries for vendors, employee/users, deposits, part categories, stock/unit, and subs or category flow - Vendors – Additional vendor/customer ties A/P & A/R & other look up options - Web – Merchant Processing batches, deposits, Authorizations tips - Locations – Cash Drawer Management - Locations – Build a 1-many for locations and sub locations - Web – Be able to web service pieces around - Reports – run on grouped totals for speed - Look & Feel – Touch screen interface - Customers – Customer type – sales reports - Invoice – Print multi invoices interface - E/R’s – Recurring Expenses and balance sheet items - B.S.I. – Known issues report - Reports – Build your own reports - Maintenance – Import & export tools - Customers – Promotion codes and marketing Time/Priority: - Web - Clean up - Look & feel - Flex grid - Bank - P&L - B.S.I - Training - History - Reports - E/R’s - Dep’s - Photos - Admin - Corp-wide setting - Payroll - A/P - Theory - Users - A/R - Vendor - Floor plan - Tools - Maintenance - PO’s - Stock Scan 78 – Sales Planning 1 – Small biz – medium biz – big fish Visions: 1-100 1. I hit all accountants – trust of biz – something to gain 2. Used dealers 3. Subs or Reps or Employee 4. Big fish Scan 85 – Sales & Setup Process “Start at the very beginning – that’s a very good place to start.” –Sound of Music Prep – any order: 1. Interest and desire to use the system 2. Somebody to help you get started – sales rep 3. Initial consulting and rough idea of business flow and needs Setup: 4. Contact a system administration to set up corporation and corp admin user. Set up assigned inventory types. 5. System will set up basic categories and default values. Sales rep and corp admin setup remaining options like users, departments, permission, banks, makes, models, vendors, account types, stores, taxes, special line items, etc. Enter data: 6. Start entering data. Either start with current needs or back clear up and enter balance sheet items. 7. At this point, it could start going in any direction as far as data: Data: - Expense/receipts - PO’s/invoices - Deposits - Units - Etc. - Balance sheet items Needs or Requirements: - Banks, check #’s, expense types - Vendors, parts, part categories - Banks, deposit types, items to deposit (pmt on sales/balance sheet stuff) - Makes, models - Balance sheet types, banks, check #’s Scan 114 – ADILAS Acronym Brainstorming ADILAS – All Data Is Live And Searchable ADILAS A – Access D – Dynamic I – Individual L – Live A – Account S – Services ADILAS: A: - Access - Accounting - Application - Accops - Automated - Alive - Abstract - Account - Addictive - Admin D: - Daily - Data - Direct - Drill-down - Dream - Dynamic - Diverse I: - Individual - Independent - Infinity - Inexpensive L: - Live - Local A: - Account S: - System - Service(s) - Systematic - Self-contained - Savvy - Simple - Search Scan 142 – Adilas Application Word Brainstorming Adilas Notes – Word Brainstorming: - Upload - Retrieve - Submit - Turn - Navigate - Explore - Sell - Follow - Show - Extract - Jump - Lead - Roll - Communicate - Collaborate - Cooperate - Enjoy - Fix - Load - Monitor - Point - Hold - Discover - Alter - Read - Switch - Become - Schedule - Stay - Grow or grown - Extend - Blend - Optimize - Combine - Go - Stop - Simplify - Track - Fill - Rely upon - See - View - Click - Browse - Enter - Educate - Teach - Solve - Workout - Send - Get find - Save - Search - Store - Consolidate - Switch - Clarify - Refine - Cut - Lower - Raise - Run - Squeeze - Give - Build - Work with - Sort - Classify - Create - Update - Access - Tighter - Track - Choose - Keep - Loosen - Make - Modify - Push - Pull - Lift - Elevate - Present - Prepare - Start - Finish - Prevent - Be - Wear - Customize - Clip - Structure - Advance - Expand - Use - Reuse - Drive - Connect - Collect - Continue - Add - Subtract - Divide - Multiply - Believe - Post - Write - Stack - Cover - Classify - Satisfy - Draw - Recycle - Replenish - Gain - Select - Recall - Refresh - Renew - Redo - Undo - Assemble - Record - Bump - Solve - Tie - Bind - Organize - Enhance - Replace - Eliminate - Empower Adilas Phrases Brainstorming: - Live & Searchable - Centrally Located Data - Always Up To Date - Empower the People - Enter Once – Use Many - No Limits - Super User Friendly - Digital Filing System - Ongoing Development - Safe & Secure - In a hurry? Go mobile! - Know at a Glance - Build Data Relationships Scan 144 – Flyers Flyers: - Trailer - Vehicle & Automotive - Boat & Marine - Motorcycle/ATV/Snowmobile (Motor Sports) - Pawn Shops - Modular Homes - Self-Storage - Retail - Profound Services - Restaurant - Manufacturing - Custom - Individual - Farmer/Rancher - Non-Profit - Churches - Airports – FBO’s - Contractors - Tractor & Farm Implement - eCommerce - Make the contact info dynamic… on the bottom Scan 145 – Adilas Colors/Logo Adilas Colors/Logo • Background colors • Gradients & soft • Rounded edges • 3D on adilas image Scan 146 – Adilas Phrases & Tag Line Brainstorming Adilas.biz - Data storage & retrieval - Cloud data storage & retrieval - Cloud.biz - Cloudaccounting.biz - Cache - We help you cache your data - Your data, you cache & retrieve, we secure - Flexible patterns & power users - Old vs. new - Your data, you cache it, we secure it, you retrieve it - We have a data portal - Up, secure, down - Up, secure, organize, down - Pull, secure, push - Send, secure, retrieve - Post, secure, get - Facilitate change Old vs. New Old: - In house servers - T-1 lines - Dedicated lines - Hardwired connections - Software & yearly updates - Large IT Staff New: - Let operations lead accounting – secure, retrieve - Bits of data archive - Commit, secure, retrieve - Data – you commit, we secure, you retrieve Scan 147 – Adilas Catch Phrase Brainstorming Adilas Catch Phrase Brainstorming: - Our business solution for you is to store your data in real-time and give it back to you in a linked and organized manner/fashion. - Giving back your data in a linked and organized fashion. - Giving you live and searchable data - Skate to where the puck is going to be! Customers: - Do a ton - Give - Send - Upload - Work - Submit We: - Organize - Store - Link - Collect - Facilitate - Always there - Reformat or reformulate - Carry data for you - (More progressive clients) Here is our marketing & sales catch phrase: You throw data, we catch and organize it, you call it back as needed. - Where are you headed? - Questions? - Data trash truck - Do you know where your data is? - How can we help you? - Do you really know what’s going on with your business? - What do you want from your business? - Where’s your business going? Scan 148, 150 – Adilas Tools & Functions Adilas Tools & Functions: Categories: System Tools: - Real-time data portal - No limits - Safe & secure - Web based - Hosted solution - No hardware requirements - No software requirements - No upgrades needed – ever - Unlimited growth potential - Search, save, store, print - Manufacturing - Recipes/build - Scan - Photos - Documents - Receipts - Invoices - Search - Vin numbers - Serial numbers - Histories & audit trails - Help files - Printable documents/lists - Save as PDF Inventory Management: - Add/edit inventory - Update inventory - Mini conversions - Accuracy up to five decimals - Units of measurement - Photo & image galleries - Online tracking - Parts & accessories - Custom service products - Stock units - Serialized inventory - Internal inventory transfers - Purchase orders – PO’s - Update inventory counts - Linked to your website Accounting: - All your numbers in one place - Operation driven accounting functions - Cloud accounting - Real-time environment - Good numbers for accountant - Bank transfers - Deposits - Expense receipts - Accounts receivable - Accounts payable - Balance sheets - Income statements (P&L) - Photo galleries & documentation - Scan receipts/invoices – visual proof - Statements - Reimbursements - Payments on account - Check requests - Check writing application - Unlimited banks - Remote check writing - Expense types - Floorplan - Bank - Running balance(s) - Reconcile Banks - Check register - Bulk verification - Life cycle accounting - Roll call accounting - Linear accounting - Paperless office Payroll: - Digital timecards - Calculate payroll & withholdings - Commissions - Salary - Hourly - Combinations pay schemes - Diary (daily) Operations: - Digital filing system - Event driven updates - Remote check printing - Huge tool set - Make more sales - Quotes – save & email - Internal tickets - Loan calculator - Date to first payment - Profit & discount calculator - Manager’s checkbook – slush fund – unit pac - Global markup settings - Mixed tickets - Unlimited line items - Merchant processing - Credit card payments On the Web: - Any computer with internet - Access 24/7 - Access anywhere - Server based - Light-weight client - Easy access - Instant web presence - Customer web inventory Customers: - Customers - Up logs - CRM - History - YTD – invoice payments, etc. Reports: - Sales tax reporting - Build your own reports - Profit per reports - Advanced search options - Data drill downs - Wild card searches People: - Empower the users - 100+ permissions Maintenance: - Locations – multi - Departments - Vendors - Management - Makes/models - Look & feel - Corp-wide settings Admin: - Any sized business - Corporations – multi - Full customizable - Peace of mind - Drive profits - Work with great people - Audit trails - Corporation wide settings Easy to Use!: - Live & searchable - Centrally located data - Super user friendly - Open to ideas & suggestions - No contracts - Reoccurring invoices - Online tutorial videos - Navigation - Jump menus Time Efficient: - All under one roof - Server based - Go anywhere - Got a blackberry? Run your business! - Mobile - Enter once – use over and over - In a hurry? Go mobile! - View at a glance Cost Effective: - Cloud computing - Cut your IT costs - Low cost full business solution - Reduce travel – work from home Dynamic Interface: - Ongoing development - Build data relationships - Relational database - Modular - Flexible, dynamic, and powerful - Flex grid tie-ins - Custom naming conventions Real-time: - Always up to date Scan 149 – Flyers Flyer: Main – Bullets - Features - Inventory - Accounting - Operations - Reports - Time Scan 155 – Holiday Special Banner Holiday Special Banner Holiday & Christmas Special… - One free roll of clean sacks with every order through January 2011! - No codes or coupons to worry about - Normal - With tax included - State tax - County tax - City tax - Other tax 1 - Out of area tax |
|
|
AU 2211 |
|
Brainstorming What is still needed to roll everything out like we want to? | 6/9/2011 |
What is still needed to roll everything out like we want to? - Ecommerce and customer pay portals. Maybe online reservations. (2 weeks) - Help files (3 days) - Grouped reports (2 weeks) - My favorite buttons (2 weeks) - Graphical navigation and page flow (all sub homepages) (2 weeks) - My user history - Flash media player (2 weeks) - Roll call page with associative reports flex grid and other system ties (3 days) - New credit card gateways (Lucy and First Data) show groups then details (2 weeks) - Balance sheet rework – round 4 (1 month) o Feeders o Watchers o Known issues o Standalone declarations o Payables rework o Taxes and collected fees - Training manual and adilas university… Ongoing project (1 month) - User history reports (3days) - Financial history reports (1 week) - Small tweaks to current history reports (1 day) - New photo galleries and moving over to content server (2 weeks) - Payroll rework (1 week) o Gross sales o Elements of time (subs) o Reports - Ideas and sharing… global updates, global idea center, global forum, all elements of time (1 week) - Objects and data over time – adilasuniversity – theory and concepts (2 weeks) - On order and in transit tracking (1 week) - Sub locations and how they tie-in to things (1 week) - Elements of time (1 month) |
|
|
AU 603 |
|
Daily Ideas | 9/9/2011 |
-What if we combined the my favorite links and buttons with the build your own custom reports section. This would be this page, these settings, this name, this sort category, etc. Basically, take the old mend and repair concept and add it to the my favorite links and buttons options. -It seems that everything is going in to a personal setting-type structure. Some great learning models: -Gospel principles are very simple – set up the adilas university just like that. Basic concept, what does this mean, basic examples, expand the vision. -Boy scout E.D.G.E method does the same thing: explain, demonstrate, guide, enable. -The Duty to God method does the same thing: Learn, Act, Share. -I love to say: Learn it, Live it, Love it, Share it. -LTF – get the skills, learn the moves, go ride! |
|
|
AU 629 |
|
Daily Ideas | 10/7/2011 | -When doing adilas university and training – use the principle of repetition in the learning process. Kind of like the visit of Moroni to Joseph Smith. Don’t assume that people have watched the other videos; spell it out, review it where needed and sum it up where possible. | |
|
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! |
|
|
AU 751 |
|
Daily Tasks | 3/22/2012 |
• On the phone with Steve going over our game plan and some tax questions. We talked a lot about adilas university and what we need there. • Did some tax preparation for our taxes. • Worked on web settings for stock/units. • Also spend some time checking existing web service calls. • Added links from stock/units and parts to the online web versions. |
|
|
AU 765 |
|
Daily Tasks | 4/7/2012 |
• Working on the advanced expense/receipt search and results page. Added options to export to Excel and refine your search. • On the phone with Steve going over ideas for adilas university. We also talked about reps and what we need to do to keep our company progressing. • Posted files online that were done. |
|
|
AU 786 |
|
Daily Ideas | 4/12/2012 |
-We had a request to store payroll settings per employee. Maybe what we need to do is show what relationships exist so that they may be manually updated. Currently each employee may be assigned to one or more departments. Instead of changing that – maybe just show the relationships and settings. Also maybe a multi-update feature for pay rates, or allow them to be updated from the setup employee page. Spread the love. -Brainstorming notes on making adilas a full-on business platform. Open the door to the data and how it plays, gets connected, is shown and is used over and over again. -I love the word “upstream” – what is the source? What feeds what? How does that affect things? Where is it easiest to control? -We keep getting great ideas but I and/or our existing pieces become the bottleneck. What if we re-built with platform in mind? -Small idea (different company arms). Diagram in notebook: Main adilas (in center box) connected to: hardware, library, marketing, personnel, web services, business(sm, md, lg, xl), stand-alone apps, web, mobile or mini, non-profit, custom look-feel (skins), software, education, eCommerce, commercial, shareware/freeware, government, trainings and setup, info/resources... Don’t get stuck here, think unlimited entry and exit points. -The goal is to create, define, provide, build, re-use, and create a culture that embraces change, thoughts, ideas, concepts and flow. -Allow people to create their own uses of the system. This means provide a core pre-built structure. However, if people only need 3 out of 20 options, let them put it together in a custom wrapper to meet their needs. -Think about a global library of functions, logic, data and mappings. -Create a buffet or smorgasbord of options. They (persons – our company – other company – teams – individuals) could pick and choose. -Allow different pieces (already defined or new pieces) to play in any 1-to-1 or 1-many(one-to-many) relationship. For example: we have vendors, elements of time and expense/receipts. However, they are not currently tied together. If I had a shipping and packing company it might be nice to know who (vendor) is coming in today, what do they need (invoice), and what are they bringing (PO’s and expense/receipts). Imagine being able to virtually morph or create dynamic relationships between the different players through a standard “re-skin-able” interface. -All the players already exist (or may be created) and then you put them in to play by defining rules, parameters, scopes and functions. You get to name them, use them, whatever. -Our current system is already built with data components (ColdFusion CFC’s) and logic pages (searches and reports). What if we allowed others (or our own little sister company) to get at any of those pieces. Once access is granted, the sky is the limit on what pieces could play or piggy back on one another. Get as many or as few as are needed. -I see it as the main “adilas” is the pre-built or canned version. We keep adding permissions and settings but keep a basic and consistent flow. If a new wrapper is needed (custom look, feel, function, relationship, process, steps, etc.), allow that to happen without causing problems upstream and/or downstream (cause and effect relationships). -This may not fit here but what if all data was returned as a standard like xml or Java (or whatever else new comes out) and then consumed by whatever type of application that calls it. The end goal is call, crunch, serve, apply, do it again. -On a different note – what if every function or method call had a user id, corp id, app id. Every function could also pass its data to a converter function. The converter function would get, check, interpret and then send the results back. The original method call would return the native format by default. However, if a different format was needed, it could translate the output to that format. -The incoming values would also need to be standardized – so that flow back and forth would be possible. -A full re-write from the ground up may be required. That would be a couple steps backward to make huge and giant leaps forward. It wouldn’t be the first time. (Meaning a full re-write) -Security, mobility and built with growth in mind are huge keys. -Currently built in Adobe ColdFusion and MySQL databases. It could literally be built in ColdFusion, Java, PHP, ASP, net, Ruby, Visual Basic, Access, Flash, ActionScript, Java Script, you name it. I think the more the merrier… Oracle, Microsoft, Apple, Unix, Web-based, App-based, software, firmware, hardware, freeware, shareware, etc. -Expose the code, the logic, the theory, the formats and the experience to the world. -As long as things are being expanded, what about languages? Computers? Operating systems? Countries? Etc…. -There is enough to go around (info, resources, ideas, etc.)! Share with the people. On a similar note, just read a cool scripture today during my study, it was 2 Kings 4:42-44 (pg. 513 in the Bible)... related topic. -Another quick idea – how cool would it be to over lay a calendar view on everything that happens in the system. Elements of time have groups, details, calendar and time slot view – think everything out of those four levels. -Random other note: If we were to expose this stuff to the world – we should video tape the presentation and then send that around to different colleges around the world. I’m thinking that the college level is the entry point for new and creative thinkers and future business leaders. It may branch out from there, but that is where I’d like to focus first. Post the videos on adilas university for the world to see. -Plan it out, break it up into pieces and even provide code samples. |
|
|
AU 776 |
|
Daily Tasks | 4/20/2012 |
• Reading emails and a proposal for a California company to do full circle tracking of products and services. • Other emails and tech support. • Did some emails back and forth to Steve about help files and options. • Re-read and updated the adilas history biography. • Posted a PDF version online at adilas university.biz. • More work on Alabama state tax calcs. |
|
|
AU 2252 |
|
Brainstorming - Planning for Meet the Players | 7/13/2012 |
Planning for meet the players (ideas): - I’ve got about 40 players - It might be fun to give stats of some sorts – pretend like they are real people or players (one time I thought of making an actual movie about the players and what each department did and how they interacted. Maybe this could be a prep step for that…) - Maybe color code things like: o Actual item – yellow o Buddies & subs – green o Flow (normal) – blue o Flow (special) – purple o Financial – turquoise o Operations – black - Maybe a what do I do? What’s my job? How am I used? - Maybe a diagram of the pieces or sub pieces and 1-many relationships - Plan out what the sub menus for the map might look like - We could actually do a flash movie on flow, friends, and pieces - How could we standardize the process? - I’d like to use the map as much as possible - I may have to redo this whole section once the actual map gets done. - I could actually do the map and then do these pieces… the only problem here is the extra two to four weeks of development… the actual map would be really cool. - Maybe just prep everything that I can… at this point, then once the full plan is done, bust it out. Treat this like the visual prep or plan for the actual thing. - Script for actual - At one point, I wanted to use the same interactive player to help and handle the learning and multi-media portion of adilas university, - On the demos we wanted to get to the o General theory o Basic/beginner o Intermediate o Advanced o Tech level - What about a comic book approach… keep all of the graphics static – think storyboard - We could use motion trails to show interaction… think about Family Circus comics… they have one person playing through a number of things… (sketch on scan) |
|
|
AU 1063 |
|
Daily Ideas | 1/3/2013 |
-On pages with thumbnails, show a border around the thumbnail and match it to the link color. Sometimes the photos blend in. This little outline will help them show up better. -We started a concept website in January 2010 for adilas. It could really be cool if we went in that direction. Basically, the site has a number of links and menus at the top. It would then show a number of features and counters for things like invoices, customers, parts, checks, elements of time, customer logs, flex grid tie-ins, vendors, expense/receipts, deposits, time cards, logins, etc. -Some of the menus for the concept are: The adilas system Training and education o Tools & features -Video tutorials o Our approach -How to’s o Faq’s -Scenarios o What’s new -Old school vs. new school o Pricing -Adilas university o Permissions o FREE web tools o Get the vision Sales and marketing Customer service o Flyers -About us o Testimonials -Get a quote o Other services -Schedule a live demo o Pricing -Contact us o Opportunity Login Search web inventory With a little loving, some of these subjects would really help us sell our services. This may need some tweaking (the menus) but it as a great start. -Add the mini calendar to the free online tools. -Tell the inside story of what, why and how things happen; what goes on internally to help with flow and efficiency. -My daughter was having fun with the word believe and said – If you are to be live, believe. |
|
|
AU 2275 |
|
Brainstorming - Meeting to Talk About Adilas | 2/22/2013 |
- The servers are the top monsters. Cluster: content, data 1, data 2, data 3, adilas university, web services, outside website (sketch of flow and layouts – see sketches in photo gallery) - Put the help files on adilas university - Put YouTube videos on adilas university - Put the developer’s notebook on adilas university - Monitor each cluster and who is on each server - Growth and “farming” of data and servers - Keep cluster 1 and data 1 very small and make adilas the controlling entity - Play musical chairs – mix and match – learn other pieces of the puzzle |
|
|
AU 1104 |
|
Daily Ideas | 2/23/2013 |
-“It’s time for musical chairs… everybody get up and go to the next station.” -S.O. -“Are you prepared to let go of what you need to?” –my dad. -With reps – do’s and don’ts. With paying – do’s and don’ts. -What do we need to setup a corp – process or required pieces. -Adapt and overcome! -Outline and structure the training material – we were a little too open. -Bank account to get ACH services. -Take off the flyer about bringing the lunch. -The servers are the top monster. -(Sketch in notebook with clusters. Content - Data 1, 2, 3, etc. - each corp has its own little area - each corp feeds the outside web services (adilas web services). If content is needed it gets pulled from a content server. (Adilas university)) -Sketches of the cluster model. -1 content server hooked to multiple data servers. -Each data server would have a number of corporations under a specific data server. Kind of like their own little “adilas”. -The model above is for a single cluster. Multiple clusters could be used either together or by themselves, very flexible… -Put the help files on adilas university. -Put the YouTube videos on adilas university. -Put the developer’s notebook on adilas university. -Monitor each cluster and who is on each server. -Growth and “farming” of data servers. -Keep cluster 1 and data 1 very small and make adilas the controlling entity. -Play musical chairs – mix and match – learn other pieces of the puzzle. -Accounts are reviewed on a semi-annual basis. Based on that review, we analyze and will do something with the monthly fees. -Create a web-based company assessment. Fill out as much as you feel comfortable: looking for numbers and values. - # of EIN’s - # of Location(s) - # of Employees - Business type or industry - # of transactions - You get it all…. Help us know which features you are interested in? o Do you have inventory? - How many unique types? o Do you have any serialized inventory or big tick items? o Do you sell labor? o Do you sell time? o Do you sell services? o Do you plan on uploading photos, scans and images? o Do you plan on using the scheduler and elements of time? o Do you plan on using merchant processing? o Do you plan on using eCommerce? (May require additional fees) Still dealing with a web based company assessment… - Other notes on request - Reps or how did you hear about us - Main contact info - Company name - Contact name - Phone - Call to action! -Have the reps use this request from to submit info to us. This would be how they request a new corporation. -Buttons that say “quote me” or “sign me up”. This is a call to action or an action link. -We will be contacting you. -Have and show some testimonials. -Having the adilas team here in Utah at my house was a great blessing and we got a ton done. I’m super thankful for a couple of extra days due to bad flying weather. It was a blessing in disguise! |
|
|
AU 1140 |
|
Daily Ideas | 3/15/2013 |
-We’ve had a few requests for a smaller or limited version of the sales and profit report. The report would be at a salesperson (employee) level and would only show sold info. Any cost and profits would not show up on that report. -For XML – use adilasDataRequest and adilasDataResponse as main root elements. -Inventory with attributes. One part number with multi attributes – sizes, colors, etc. -Last costs – may be a problem. Last known costs vs. average costs. We may need ICC’s pretty soon! Maybe a corp-wide setting for costing. -On new databases per corps – maybe use an auto id for invoices, deposits, expense/receipts, PO’s, time, etc. instead of assigning new numbers by direct assignment. This could help (using auto id’s) to eliminate or minimize duplicates. -When allowing persons to submit external data, suing the open API, allow for FORM scope, URL scope, and XML options. Make it flexible yet manageable. -Use adilas university, for documenting the API. -Thinking of breaking the API into main players, functions and details or options for each function. Think outlines and drill-downs. The API will be on the tech level of the application. -We are walking an interesting line… Education vs. Development… Development is fun but without education – what does it do? Education without development – feels limited or dead? We may need to mix and blend. (Kind of like faith and works – you need both.) |
|
|
AU 1123 |
|
Daily Tasks | 3/21/2013 |
• New logo for a company. • Working on eCommerce. • Recording hours to the other notebook. Did some training and tech support on expense/receipts. Added a view button to the chooser page. People were clicking on the set as default button instead of the graphic. The view button helps them make a decision. • Went into Bridgerland to test the laptop on GoToMeeting. Worked with my sister for a couple of hours and tweaked some settings. Shared with my sister about what I want to do for adilas university. I also brought up the next project and how we went to take the adilas user guide to a digital level. We talked about concept, beginner, intermediate, advanced, and tech levels. At the tech level, we would be into database and code stuff. Basically, I need my sister’s help to help me carve out time to work on it. While at Bridgerland, I also talked with a guy about “PLC’s”, I think that stands for Programmable Logic Controllers. I was interested in setting up a business type model that could be arranged like an electrical or circuit board PLC. This would allow for mapping, flow, checkpoints, etc. This goes along with what we want to do for our open API (application programming interface). Anyways, I watched his run through a couple of training problems to get some ideas. What I saw was multiple tools being used at once or as needed. I saw maps, structures, desired output goals, inline monitoring, ability to see cause and effect, and ways to code and simulate code. Our model doesn’t follow perfectly with a PLC but there are quite a few similarities. Good stuff! 20 miles. |
|
|
AU 1179 |
|
Daily Ideas | 4/2/2013 |
-Trying to remember old Flash projects that I did. I’m trying to get back into Flash to do the adilas.biz interactive map and the adilas university.biz training area. I’ve done tons of Flash projects over the years. These are just a few. Morning Star: - Navigation banner with roll over graphics - Location map - MSAI logo zoom - Old stock/unit photo galleries - Deal calc with dynamic data - Parts application with Flash Remoting - Parts admin with Flash Remoting - Floorplan application with Flash Remoting Fibark - Fun kayaking animation Radon Ranger - Sliding menu - Comic book with page navigation - Product display SOSS - Flash menu using pencils Salida.com - Mountain site navigation - Tons of sub menus - Tons of mini ads and animations - History animation with miner and rafters Moore Digital Ideas - Main website with menu, animations, and status bar interactions - Navigation options - Photo galleries - Games – hangmen, catch the apples, etc. - Lots of pre-loaders Custom Fit - Class content using Flash Remoting Bridgerland Applied Technology College - Interactive CD-ROM with photo galleries, video, and other dynamic menus and pieces - Flash cards for Medical terms Learn To Freeride - Video teaser and custom player - Interactive CD-ROM with multiple skins, tons of video, and linked to web content. Music controls and custom video playback options. - LTF skateboard demo mini app New Mexico Wild - Fun animated Flash banner Vector Trap - Interactive game board adilas.biz - Barcode generator - My cart favorites – custom mini buttons - Check write application with moveable fields - Scrolling list of features Art of the Rockies - Animated banner - Full backend content management system using Flash Remoting and database content ___________________ -At some point it may be fun to go back and look at some of the different Flash files and play around with them. ___________________ (More Flash Projects continued) Geo Tourism - Dynamic photo galleries with fade in/outs - Planet zipline – fun animation - Other random demos and play files ____________________ -Plan out the maintenance and have a plan in place. |
|
|
AU 1187 |
|
Daily Ideas | 4/12/2013 |
-We could use GoToMeeting and open up adilas university with almost nothing other than what we already have. We could schedule classes, teachers, subjects, dates, times, etc. -We could even use elements of time to fill out class rosters and track attendance. -Then deeper we get, the more I’m seeing elements of time being used more and more for tons of different pieces of the puzzle. -On the tech spec flyer. I would really like to show the requirement and then show options and rough price ranges to help our users out. The only requirement is a device that can connect with the Internet. Everything else is optional. -On the tech specs – break it down to what it does, how it works, and even how to test it. Talk about human interface devices. Also load the deal for custom paperwork, custom reports, forms, labels, and interfaces. |
|
|
AU 1190 |
|
Daily Ideas | 4/15/2013 |
-Similar to the mix and blend comment above… I think that I will start using this phrase… - “Get results by applying business functions, application players, and core concepts.” -In short – Results, Functions, Players, and Concepts. From 4/9/13 to 4/15/13 I had an explosion of ideas and concepts. I was trying to boil hundreds of concepts down into smaller categories. I ended up with these 12 core concepts. Many of these top level concepts have tons of subs. 1. Players 2. Relationships 3. Problems, Needs and Goals 4. Decisions & Choices 5. Cause & Effects 6. Accountability Core Concepts 7. Objects & Data Over Time 8. Systems 9. Permissions & Settings 10. Vision & Future Developments 11. Tech, Tools, & Maintenance 12. The Story These are some other thoughts that haven’t made it in to my notebook. Most of them come from 4/9 to 4/15. - Inputs & outputs – “you get what you give!” Normally you hear “you get out of it what you put in to it.” What if you shortened that saying to… “you get what you give!” That changes its meaning incredibly. - Weakest link affects the whole. - Confidence - It takes work - Think logically – what happened in real life and how would I do that in a virtual world? - Flag & date - If correct, let it flow~ - Checkpoints - Computers are dumb, powerful, but dumb. You have to tell it what to do. - Everybody uses the system differently. - World building and telling the story. - It may be overkill at times but it helps track the story, even if it gets complicated. - You tell the story, we then help you map backwards to show where things were at. - Push vs. Pull – give automatically or wait until asked. - Concept buffet – tons of topics. - You find what you are looking for. - eBusiness Model - All elements work together, interacting and influencing one another. - Objects are defined by relationships. - Be willing to change. If we replace bad habits with good ones, it can dramatically improve or reinforce the change. That is good! - Focus on and teach people! The actual subject is secondary. That is hard to remember sometimes. - It is okay to testify of truth wherever it is found! - What is adilas? A complete package. It is way more than just a “sales & inventory tracking system.” You get everything! - Confidence – feeling good about yourself and what you have done. And knowing and/or believing you can do it. - Everything starts with your goal. What do you want to do? What do you need? Once we know that, we then look or think about the tools to get the job done. - Say you go to the grocery store. You have tons of options. If you know what you want, you just go there. If you don’t know what you want, you start walking aisles. Inside of adilas, it is the same way, if you know what you want (you have a goal) you just go there. If not, you may feel stuck or may get frustrated. - Portability – ability to move or change. - Industry specific – skins and interface. - Construction… you could build anything with a saw, a drill, a hammer, and a screw driver. If you know how to use them and what they do. Think – goal, tools, and then how to apply the tools or concepts. - I love the word “apply” or “applied”. That means putting things to action. - My son was reading the word “turnkey” and he turned it into “turkey” (gobble, gobble). He then said adilas was a wild turkey chase. You go all over the place like chasing a wild turkey. I thought it was kind of funny! - What you do physically every day… we capture that in a virtual environment. The system is like a physical extension of physical actions. - Our people need to be willing to try and love to learn. - We have an engine. - Stick to the fundamentals… do it over and over, stack and stack and stack. - We are pushing towards a self-service model. - Use GoToMeeting and do weekly training sessions. This could start adilas university with very little money. Maybe getting up to 2 classes a day, 5 days a week. - Along with that, it may be good to pay a rep or someone to teach a class. Say $40 per session or $50 per session. 2 hours. - We want to use a new landing page for notes, updates, news, and upcoming training events. This page would pop up when a user logs in each day. Maybe set a session variable and if 0, show the page. If 1, let them bounce around as needed. - The main adilas.biz and adilasuniversity.biz site both need some loving. |
|
|
AU 1175 |
|
Daily Tasks | 4/26/2013 | Met in Salida at Steve’s house. We had a multi hour brainstorming session with the adilas team. We listed a number of topics on a white board and then started discussing ideas and options. Great meeting. There are pages of notes (a couple pages back). I also wrote an email (after the fact) to help fill one of our team members that couldn’t make it, in on new developments and direction. Most of the meeting was dealing with business plan, marketing and adilas university. | |
|
AU 1198 |
|
Daily Ideas | 4/26/2013 |
-I love what my friend said, “step out of the door and let them come in!” He and I talked last night for hours about how he has been waiting for this time. One of the key things we talked about was the phrase “As Is” and grouping all of the to do list into the phrase “future developments”. Good stuff! -We are playing with ideas about opening up adilas university using weekly GoToMeeting sessions. We are thinking about 2 hour sessions with a topic and then open questions and answer sessions. It really could be quite easy! -Along with that, we could post the topics and times on the news and update page. -We need some fun videos that help introduce and give virtual tours of different sections. Also small orientations about the subject and the concepts and theory for the subjects. -On adilas university, we need a spot where reps, consultants, sales, and other adilas team members can post information and small bios and photos about themselves. This will help put names and faces together. It might also be cool if we allowed up to 10 (random number) photos and captions to help everybody know a little bit about each person. -We need to use our team member to help coordinate “flow” and “communication” within the adilas team. -Minimize the number of times people see the news and update page. Maybe just once a day. -When extending or allowing things to connect to other systems. Maybe call it the “Application Flex Grid” or application flex grid tie-ins. -Change by stats and volume Meeting with Steve and other adilas team members… going over the future for adilas and where we are headed. Here are some rough notes: - Goals – help people, release the bottlenecks, team of 5@5K/month - Direction – North or forward - Business Plan - ACH (Wells Fargo) - Protection (sharing) - Servers - API (Application Programming Interface) - Stats – space – code for free then charge for storage and usage (charge by volume or power) - Training - Adilas University - Marketing - Help/Interns/Employees - Open communication & flow (team member assigned) - Custom code - Future Development (all future products) - As is = Released versions or version #’s - Our sales & marketing plan is free – adilas engine - Flow charts - White label – free - Projections - Timeline – within a year - Application Flex Grid Tie-ins - You get what you give - Internal adilas mall – future playground, cross corp, internal sales, franchises - Target computer people - Target “Denver” – Colorado based - Scale the training model - Sell & market what we have - Market through the Internet - Use technology - Go after the already trained – inactive adilas users - Rough Budget o 50K Help o 20K Marketing people & research o 50K Marketing budget o 50K Repay Loan o 10K Reps/Consultants o 10K A specific rep o 10K Adilas University - Future Development Ideas o Mid may eCommerce o Additional photo galleries o Content server o Normal servers o Adilas eCommerce (start at $197 directly from the web) o Second round of elements of time o API & custom skins |
|
|
AU 1233 |
|
Daily Ideas | 5/10/2013 |
Ideas for parts: • Group or Player Level – default “parts” o Category Level – default “part category” (many - unlimited) * Item Level – default “part number” (many - unlimited) In real life: • Group or Player Level o Category A * Item 1 * Item 2 * Item 3 * Item 4 o Category B * Item 5 * Item 6 (Small worksheet – category, item, fill in the boxes to indicate a category or a part or item) -It would be really awesome to turn adilas university into a 501©3 non-profit. We could then use the adilas eCommerce section to accept donations to help fund the project. That may be a great way to help pay teachers, servers, custom code, play sites, etc. -While in Salt Lake I had the thought about schools and lunch cards and keeping track of who owes what and how much money is in on their cards or on their account. This is the same exact thing as a customer loyalty card or a gift card. They are the same concepts, just different audiences or usages. -LTF… Idea from contact in Salt Lake. Put LTF up on a Google drive or make it downloadable right from the website. All other hard copies would then be collectors’ items or sorts. He also mentioned Google drive as a way to get a copy of LTF out to his guys around the states. What a great idea, thanks! -On the same note, I am and was so focused on the physical product. I haven’t even been thinking about a full, as is, original download of the existing product. I could make a mac version and a PC version. Make a couple zip files and call it good. -As a different note, I was sitting in front of the Utah State Capitol building… I love to look at history and what great people have done. It is inspiring to me! -I just ordered some pizza and I’m sitting outside. My whole way home from Salt Lake I’ve been driving on the old Hwy 89. I did this on purpose to get off of the Interstate. I’ve been going through city after city, town after town, and I’ve seen tons of small businesses. I kept thinking adilas could help them, and them, and them. -I then got to thinking that every business could actually benefit from the concepts that we are using inside of adilas. Even the biggest businesses are still using the old double entry accounting model. There is some pain there and it is general among every business. -I keep thinking… How could we help everybody to run better, smoother, and more efficient? The answer that keeps running through my head is “the concepts”. The adilas code is one of thousands of possible options, but the underlying concepts are where the real value lies. -How do you teach concepts so that people get it and start using that as an option? Well, somebody has to teach it, explain it, show it, and even map it out. It needs to go basic to hardcore tech. Different people will understand and play at different levels. -I’m thinking that adilas university is and will be part of that answer. Help teach people in an organized yet dynamic way. Make it progression based, yet nonlinear. Basically, an LTF (Learn to Freeride) project for teaching business, concepts, theory, flow, cause and effect, etc. Maybe LTF was a prep step for this monster project… |
|
|
AU 1211 |
|
Daily Tasks | 5/11/2013 |
• Emails, tech support, and bank stuff. • Research on upgrading servers to bigger faster boxes. • Recording notes in my notebook. • Emails and recording more notes. Objects and data overtime. • Working on some tweaks to the adilas university logo and site. Also worked with my brother on some video stuff. • Changed the adilasuniversity.biz site and listed our first online class dealing with corp-wide settings. Adilas university will officially open on May 16th of 2013. Yee haw! |
|
|
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 1246 |
|
Daily Tasks | 6/4/2013 |
• Working on adding and editing customer information using the backend eCommerce section and customer sign in portal. Brainstorming on flow. • Checking in with the server team at Newtek to plan the server migration process. • Updating pages about upcoming server migration. • Tech support and phone calls. • Rereading over the Adilas, LLC. Operation agreement document. • On the phone with Steve. We talked about current client needs, using technology, adilas university, education, reps, training centers, and marketing ideas. We talked about the adilas mall and what we may want to call it. We had a great discussion and ended up talking about “World Building” and fun related concepts. We decided to change the “adilas mall” concept to the “adilas world” concept. This will be a special site that will highlight and showcase users, reps, consultants, CPA’s, Attorneys, trainers, graphic people, code writers, etc. We had a great time talking about how world building and adilas go hand in hand. The deeper we get, the more we see a need for a community of users and eventually B2B business to business transactions. • Revamping the original adilas operational agreement from back in 2009. Kind of fun. Sent copies to Steve and David. |
|
|
AU 2137 |
|
Adilas 3 Day Training Notes - Denver | 7/18/2013 |
DAY 3 - JULY 18th - Focus on deposits, banks, expenses, etc. -Started off with a question from online which led us back into flex grid -Back into flex grid... (Transparent & non-transparent flex grid options) -The only caution for flex grid is plan it out so you don't have to re-do all of your work and so that you can have the pieces you need where you want ^I need to learn more about flex grid and elements of time -I love the problem solving aspect of setup and consulting.... understanding their issues, concerns, needs, goals and helping choose the best tools to fit that goal or an acceptable solution for their concerns -It is so neat that the flex grid is its own customizable database on top of the application. -You can even barcode flex grid if you would like - a company uses this because they have different pricing for many of their customers on the same parts *We need testimonials and experiences from customers - people see the value in that, it had been mentioned by multiple class members -Stock units seem really neat - we saw a little bit with a company that had done a lot of internal invoicing with stock units - really amazing how much they tracked everything.... construction management and job costing to the n-th level -Once you have all of this data, you can do SO many things. Plan ahead, know what you need for future projects, have everything tracked to the finest detail... huge potential, everywhere! -Brandon did a little show & tell of how some different company's use adilas - people LOVE this! This seems to give people an understanding to the point where they finally grasp some of the possibilities of adilas. It is interesting to hear their reactions, because we have been working in adilas now for 2 days and they have been really excited but people love seeing how this is really used in business and they start seeing an even bigger picture. A good little wow show, they really capture just how much this tracks and how easy it makes people's lives in business and how great of a business tool adilas is. ....... Now we just need to get some "commercial", "testimonials" from so many of these customers that are using adilas. -Adilas really increased the re-sale value when you have such a detailed customer base and detailed books and you really increase the value by showing what the company is that is being sold. *IDEA: A rep training - which was already mentioned above but what if it was largely rep led and instructed - specifically for reps and how to setup clients, but also all that adilas does -Protection by sharing - and the users and those in the class were expressing their appreciation of that and also feedback on how smart or a good route that is -Security question - password & profile help page. Talking about all the upfront adilas does to keep things safe *Users get super frustrated when they are set up and feel like they have been left alone. If you can make a good setup and initial training, that is critical, but there is a definite need for consultants and training - no question obviously, why we're here again and why adilas university is forth coming. You will definitely have some people that will get in and figure it out and make things work and you definitely have other people who will need more hand holding. Also known - just figuring out how to address that again and help users to be successful! That should be the focus of the rep/consultant - help your users/clients to be successful. -Is accounting even needed if nothing is happening? Great way to ask that - let operations lead. Put the horse before the cart. -Zipper analogy - a great starting point - because merging operations with accounting will change the ways businesses can function and can change the face of what will occur in business accounting and tracking.... Brandon wanted me to record that Joe was talking about this but more of a comment than an idea. Maybe an idea as an approach??? -Reps/consulting/instruction note: we really need to be able to help people understand principles, flow, some basics and where to go for help (help file, tech support, adilas university, etc.) about how adilas functions.... because when people understand flow and more principles, then hopefully they can be more prepared to go in and figure out how to make things work for them. -Interactive map: operations on the bottom and as things flow through the bottom section, then thing begin to rise to the top (a little cream scenario), when you have good operations, things will be cascading to the top - your accounting aspects -I'm really impressed with Brandon's teaching: sometimes it gets really challenging to cover basics, flow, and possibilities when you have such varying levels of users and also users or clients who really want their "problem" questions answered... anyhow, it definitely takes a balance and I am grateful for Brandon's patience and teaching and all such things. -Accounting comes with the natural flow of accounting -It is important to understand that there are many ways around the track. Different ways work for different people, industries and preferences - and help other to work in the way that they need... Roxanne: demoing expense/receipt - Good to remind people when setting up and the interface looks intimidating. That assets are any monies coming in, liabilities are any monies going out. With that PO's are tied to inventory, what you are paying and bringing in for inventory. Expense/receipts are any other money out for whatever....... -She also copies and pastes a lot of her little notes into all the different sections, b/c different ones show up in different reports -P&L - Profit and Loss, I.S. - Income Statement, B.S. - Balance Sheet -Roxanne was saying: Get in there and get working - if you make mistakes, not a problem, it can be cleaned up but be unafraid to get in there and just use it. There are ways to clean up, to move on, just get going and try to do the best we can. -Reimbursements - when creating that expense receipts for a reimbursement, you are putting in what they paid - so "no bank assigned", then when you go to pay him that will essentially create a new expense/receipt to satisfy that one or many if there are many to reimburse *Always work out of your payables, you're always cleaning up your payables. For what you owe, look at your payables, work from there. Look at what to pay from there, and then you have it broken down to your PO's, your REI's, and your Splits. -The "not yet" verified link on PO expenses you are paying on - if you click on that link it will take you right to the verify page and then right back to your payables homepage - instead of going back and doing the process over and over and over, you can do it all there nice and fast. Wahoo! Thanks Roxanne, that was a great demo! Back with Brandon leading - but a lot of group comments and input, wrapping up the training scenarios, etc. -Great comment by Joe as we were talking about future clients - Every situation you walk into you need to assess the client, not only what they need, but what is their interest and desire - are they ready to soak up adilas like a sponge.... or are they no, no we have QuickBooks/PeachTree/whatever... then you just throw them a bone and then another bone, etc., etc. Then Brandon was discussing that you really can walk someone step by step. You can start with some aspect of the application and once they get that then you can introduce another aspect. What do you want??? *The byproducts that adilas creates is worth way more than the monthly payment for the application *People believe in adilas and the way adilas functions. They love how adilas cares about their customers and reps, they appreciate how adilas is not stingy with all of their code or training, they love it for the incredible business tool it is - that it tracks everything and does almost anything they want and that you can tie everything together and tell the whole story, they love that adilas is offering training for free right now, that adilas actually takes their ideas for improvement and incorporates that. Those things make people believe in adilas and people are selling and promoting adilas because they love the product and they believe in adilas' philosophy. -Things are automatically mapping just as you are operating. -"People do things different ways, and so does adilas." -comment from Roxanne as we were discussing how important it is to set people up right from the beginning or in a way that works for them and their preference -Also a note, a consultant was discussing that they doesn't know everything but you don't want a client to know that or feel like you don't know what you're doing. So they focus on another problem or area of training for that time, express that you can focus on the question next time or after getting these things settled, work with something that you know, - then they’ll figure out the answer for the next time. That was their trade style. *But of course another style - which others mentioned, is: I don't know the answer to that question but I know where I can get the answer and I will get it for you. That is how I like to play as well. Be completely up front and honest and transparent but I am willing to work for the answers and get them to you. You can still be confident about the system and your abilities without knowing the answer to everything. Just be up front and professional and get the answers you need or find creative solutions for their problems. The answers are there. -Here is the system, there are some rules involved but you can play like crazy with whatever you want! -History has such great power, records the rest of your story. -Traditional accounting - I need to close up my month, what happened this month. Adilas - what happened today, at any time, and at any time throughout the day. All sorts of data - run all levels over time! -You can use any aspect of adilas.... or all aspects of adilas. What do they want? Or if you hit the brick wall of tradition, offer something they don't have... then they can slowly work into things later if they want, or if not, no problem. You can sell adilas just for their pain! -Because you are not forced to play in one specific way it opens things up exponentially. That is why adilas can service all sorts of clients, industries, etc., etc. -People love that adilas supports the small business owners and truly works to support clients and does not kowtow to huge corporate companies. -And still growing.... :) -A great selling point for customers is also the idea sharing - if a client has a need, adilas often has a tool that can help, and if adilas doesn't have it you can submit your suggestions or they can build you the custom function or maybe there can be a piggyback development -Put notes in everywhere in adilas - use the notes to the max, tell the story Notes for graphic ideas: -Adilas Engine with different bodies/skins - multiple ways to show how customizable, various ways to interface -World building graphics - -Items travelling through the pipes: PO's - transformation - invoice -Steve's symbolism about an ant colony all participating to build adilas |
|
|
AU 1699 |
|
Daily Tasks | 7/19/2013 |
• Made a new training flyer for August. Added links to adilas university to different pages. Updated training pages. Posted files online. • Went in to Salida for a team meeting. We had quite a few people come and participate. We had Shari, David, Steve, Craig, Brandon, my brother, my sister, Shari’s son, another associate, a previous employee and her husband. Anyway, a good group of us. We talked about sales, marketing and support. The deeper we got, the more all three topics kind of morphed together into the “needs” of adilas. If you don’t have sales, you can’t fund education and support. If you don’t have education and support, you can’t do mass marketing and sales. It was interesting to see our whole group go in circles over and over again. Steve also expressed a lot of concern about monies and having enough to make things happen as they need to. Shari and I expressed to Steve multiple times that he was not alone. You could really feel his weight and stress level. Steve seemed to be at almost a breaking point. I was in the same breaking point about 6-8 months ago. Overwhelmed, spread thin and more than we can handle alone. We tried to emphasize “team” and that he is not alone. Anyway, the meeting ended and no new ideas or direction was presented other than stick to the current plan, work as a team, and time will tell the story. Great meeting. |
|
|
|
AU 2138 |
|
Adilas Team Meeting Notes | 7/19/2013 |
ADILAS TEAM MEETING NOTES - JULY 19th FOCUS TOPICS: Marketing, Sales, Support MARKETING: -Commercials on youtube.com - how they use adilas, talking about how they love it, what they do with adilas, what they love about us. Show what it can do, for lots of other people. This is what it does.... how someone uses it and what they think about the product. -Target people with previous knowledge of business & technology - or at least try to have them as reps, so they have an understanding of business concepts and can understand adilas. Get actual reps that can go out and be representatives for adilas with the knowledge and skills to be successful as a rep. -Adilas has all of the CRM, Inventory management, Employees & payrolls, finances & accounting, ----- would like to also include and improve on marketing for adilas and also to help users with marketing -Little business seminars - live events - they let me show you what this is, instead of just come to training. Seeing the possibilities and what adilas can do.... show the product and then training, reps, etc. can be setup later when we the clients are in place. LIVE infomercials. -Business Resource Center: a source for a lot of entrepreneurs - allow demos & presentations of business related aspects... getting the product out there -Increasing our education and support - get education higher than the function, so that people and marketing can move that forward and advance the growth of function -Go after the people that want to be on the system - you can tell who those people are because of how they interact. If they get someone specifically on the ball that can get completely trained and then is responsible for training everyone else in the company and takes care of everything, they are the ones that really succeed and really take off. Steve's analogy of the really tough sales with bad credit, so you can work with, work with, work with but at the end of the day, they are still the toughest sales. Go for those who have the budget and the structure that they are already ready to move forward. -If you can get someone who already knows what's going on, they can take off with that. Then you are not teaching them every little thing instead you have them understanding at least of business and so forth. -Laser focused training on adilas university so that you could link people to those videos and have small focus. -At the end of the day - it really takes someone who catches the vision and who wants to learn. -Adilas is a piece of clay but most people want a cup. So somehow we have to get them to see the excellent flexibility..... or maybe you just need people that recognize that an adaptable piece of clay is better than a cup. -Companies need to see the possibilities but you may also need to build the piece that they want or their dream business model and train them in how to use it. Maybe you'll have to play both worlds or both sides of the coin.... or maybe you will want to focus on one for now. -Steve knows the system well enough that he can go to a company and can really assess if the company can use adilas. And IF they are willing participant, you can really go places. -We have to figure out how to market our product to those who are willing participants. You have to fire customers in a market as well, just like employees or those who aren't willing to go anywhere. -A link on boxes with reps or something and those need help with various aspects - they could click a box and then a rep that has expertise in that area could help them or something like that -Small & medium sized businesses - that is the current focus -For some of the people - if you can't get to the trough and eat by yourself then maybe this is not the pasture for you. -The ones who want something for nothing are not the people that are the kind of accounts you want. Maybe if we don't babysit them so much we can have them help themselves... so then we need to have the training in there, videos so that they can go there, figure it out themselves and get going -Social media - if you could find a way to harness that, you could do hugely powerful things there -Sub homepages: with a graphical interface that talks about the functions for that page and pushes essentially the technology and the training right in front of them - that could be rocking! Or in a side bar with help videos, side bars, graphical interfaces.... just one thing to keep in mind is that some people really like it right now how it is, so do you want to change up how they like to get in and work? Or do you just combine it somehow with what you have now? -More and more the need is coming to be able to customize their application. To make it how they want it, what they want to see, or being able to create their own, they can pick and choose it how they want... -More user-friendly - perception wise - we have to keep the elephant, we just have to make it bite size -Use our advantages where we have them. So some of those are how nimble and flexible adilas still is. It is not so constrained, so instead of a little to go box, adilas is an eBuffet. -Find a rep that has a vision to put in a little adilas training center in a major metropolitan area. Potentially customers would fly others in for little training or what not... -We need more people on sales - how? Because the majority of the reps do consulting and setup.... but we need a sales force to really get adilas out there. -Call centers - if they would want to take the product -Sales forces - could you get sales teams in major metropolitan areas - could you use college students - could you spend a day at career and job fairs, get people on sales on commission, and then you could also get a setup team which is paid hourly or whatever -You have such a prime target area with college students because they are so hungry to get working and get out into a market -But we do need to close the gap between education and functionality -Maybe they need Brandon focusing more on development and we may need to get someone else that is there teaching -Maybe I need to meet some movers and shaker friends and get them going into the sales aspect.... -College job/career fairs -Let's get the support up there - let's make it accessible, easy, clean, organized, focused --- so that we can continue to snowball and get more and more people involved and as all of that happens, it will continue to build and snowball, snowball -eCommerce will be a huge opportunity - because to have a web presence to sell, it is about 8-20,000 to get that web presence and this is a much less expensive and excellent option -Plant analogy - the process of time is important in this process, as the plant grows -Joe's comment: You mean that I only have to sell them on one page/piece of adilas for them to sneak around the brick wall of tradition? -What is your pain? We have something that can help you with that? Think of how great a product you have for such a service - that is powerful for a potential sales person... they could sell any aspect for any businesses need. That kind of product gives a sales individual incredible confidence if they can understand that and catch the vision. -Have someone creating visual interfaces (custom wrappers) and putting them over the adilas engine *They need people out selling adilas -So maybe you don't want to spend time training customers but maybe you want to spend your time training reps -Just keep going - things are growing and progressing but we need some amount of structure and support to really take it to the next level. -So maybe this is way, way future - but I know Brandon had talked about getting this into business schools and getting students to train and do assignments on that - but then what if you were to be a presence in that school at a job/career fair and they already recognize the name, they are already familiar with the product and they know it's potential - then all of the sudden you have this potentially massive sales, setup and user force -What does adilas do? - - - Basically anything you want! -Should we raise the bar a little bit and go after bigger companies???? People that will either figure it out themselves or are willing to pay for the -Brandon kept saying - we have a plan in place, let's keep advancing the ball and accelerating and just keep going. -We have a hosted solution - that is the time for that - so let's see what we can do with that -Do info blasts at colleges - 2 hour demo or in the business department - get out to people that can potentially go out and do your sales for you -Do info blasts with reps -We need to change the packaging of adilas - if you can dress it up it will potentially sell itself -We almost need a power statement for adilas - an adilas in 30 seconds -It is ripe! It is ready to get out. -Maybe it would be cool to create a cool college type poster - so it does inventory, tracking, accounting, grad school tracking, CRM, - but also research tracking, project tracking, family history, etc., etc., etc. -We NEED to get sales people! -Have Santiago go to the business college, go the University -Who are my sales buddies???? -Get a sales team leader - have them recruit and create a sales team -Also do I now other coders, developers, graphics, marketing people....???? -Steve mentioned that he has never gotten to the point where he has had more sales than we have been able to handle at this point -WE NEED SALES PEOPLE! -It's different from other sales as well, because you need those people with sales mentality but they also need to know the product -Brandon - it's coming, it's coming, it's coming.... -There are a lot of people ready to help but we need some people that are ready to go out and sale -Internet marketers - possibly a great sales force? -We need people that can network and get things going, advancing the ball more and more and more and more.... -As it continues to progress and expand, you will eventually touch those people who will want to create those sales forces, who want to take it farther. -If we do end up shifting the burning platform - no problem. We would all rather find bookkeeping people, they are great to find and you can get them almost anywhere, especially at the rates we could pay if we could get more product sold! -We have got to find a way to sell more product!!!! -We need to be able to support the support crew... it will get there... it's coming, it's coming.... -I enjoy problem solving things like this - so what part can I play to help -Shari -expressing that she realized she is part of adilas and she wants to help it grow... she wants to help lighten loads and figure out what can be done -We are here to support Steve - he needs help there. -We're seeing to the future - the compensation will come, it will come. -We might eventually need a tech support person that could handle all the tech support at some point - almost like a lot of these other services offer 24/7 support. Maybe though when you get enough clients, you can *The key question for today: How do we find and create a good sales force? -Or maybe we won't want a tech support but have it fielded for someone that has an expertise in that field - like the adilas world/mall idea - get someone who is professional in that area - they can handle the support for that question - that will be the most effective and a shared method. But also if you have the support, education, and training in place -Sales will come, let's keep pushing on sales - but let's keep bringing up the support so that when we go to sale, we can have a huge infrastructure to support the sales that will come -Maybe we need to change focus and work on support - maybe I need to focus with Brandon on the user guide, wait on the developer's notebook and move forward on training accessible to helping reps, users and everyone get up and going. -If we could get those training videos up and going and have that support there - then maybe we can be ready to blast ahead and move forward and put in a huge structural piece for the sales to move forward -We could possibly get some of these trainings and adilas university up in a month or so - profiles back up on the world - something like a $50 profile -Adilas world - this deals with this above - Brandon saying that we could build that before next month's training - even if on a $500 budget -The railroad project - an example from Brandon about the LDS temple being built and the prophet discussing that they had to take a break and take time to help build the railroad and there was some resistance but once the railroad is done they could transport so much faster and were able to -We've got to figure out a way to sale what we have - and it is ready to sell right now! -It's ready, it's ready, we can keep supporting - so maybe the focus does need to change toward sales - because you HAVE to have some amount of revenue to move forward -Shari - if we build it, they will come. But we do need to help it grow & someday we'll have the big bag of candy & though it's not there right now, it will come -Shari is really helping coordinate, reach out, organize and helping to grow -It's here, it's built, it will come, we need the flow, we need to support each other and we need to move forward as well! -Keep moving forward! -Steve is there to look out for everyone, he wants to make sure every person is taken care of and he is concerned about that. Then we have to figure out what to do to support Steve. -Are you prepared to let go of what you need to? ----- That is a powerful question! *We need to get schools on board with this - especially the universities -we need to get this involved at the University level - we need students on adilas as the wave of the future for operations tracking and accounting - if you got some school accounts you could potentially have some of your biggest paying customers and then you are creating an instructed user base, a sales base, a consultant base and you are basically priming the next generation to use adilas and be successful -We need to get adilas into the education system at every level - and interesting thought - if we are so concerned about getting our education up to the level we want - why don't we utilize any aspect we can that every educational system has to offer -We need WAY more people at trainings each month if we are going to continue to do them. Maybe we need smaller fliers to pass out individually, maybe we need free ads posted, maybe we need fliers up in prime locations - like the University - like the school of business - we need to do our part to bring people to come because. We should have at least 20 people at each class and hopefully the majority of them are new and potential clients ****Why can't adilas right now, raise every customers base price, by some percentage, and every new client that comes in, put them in the new pricing tier **** It's already so much cheaper - maybe too cheap - people understand that rates go up typically by percentages every year. You guys have to know that you are worth it!!!! Automatically updates - you are not re-selling every few year. This product is not what people have originally had and just express that we have to increase the rates to match the product being given. -Make sure you ask people for what your worth and as you are worth more - you should be asking for more -You guys have to grow with how you are growing, you have got to cover your costs as well - we have to cover what we are offering you right now ****Raise the pricing structure a blanket amount and then if you have other customers that have been longtime customers give them a preferred customer discount (like a blanket 10% and maybe long-time preferred customers at 5%???) **** ***Adilas has been growing and expanding as have the costs associated with that. The prices may need to reflect that. -They want to get to the place where they can charge for usage rates but we are not quite there yet. -Adilas needs its own eCommerce - set prices for rates - create pricing tiers that you can follow and -Want to turn in adilas to a hosting company - the product is free but you will pay for what you do with adilas as the hosting company. -The what about(s)....? And the how come(s).....? Are what bury Steve and Brandon so if there is a way to relieve the pressure -If you can get people who will consume it themselves - STUDENTS - prime target, they already know how to use these, they like to explore, they just fly on this and they can consume it and pass it on and just go to town on all of this stuff *The future of adilas is as bright as potentially anything could be - but maybe we just need the fuel to get there -Look at what the competition is giving and at what price to help create your pricing structure *Does it need to move right now to the modular focus and so that they could get pricing in place - so that they are paying for usage - modular mode - a natural price increase time.... so some could snip off some pricing and others could add to it for holding their pdf docs and what not - so people are willing to pay to access that in the modular unit -Potential for investors???? -There are a lot of challenges with this particular business - so much there - but it's a little different beast so how do you handle those challenges -We need to get some canned demos and some canned commercials -We need companies that have someone who can be the ones writing SOP (Standard Operating Procedures) and move forward on that -You can charge in many different ways. By usage seems like it would be the best - but you could charge by "room", like the kitchen, or the garage, or.... ****You could get a change in the price right now when you set people up with eCommerce you change adjust their prices right there. And all those clients who are not going to use eCommerce, let them know you are going to have a blanket increase of 10% or whatever**** This is something that could be done right now! **** -Let's get the younger generation involved as much as we can - they are primed to work in a system like this *Great meeting - lots of input |
|
|
AU 1 |
|
Daily Tasks | 7/30/2013 | Setup the adilas university system with Russell and Shannon Moore. Yee Haw! | |
|
AU 1704 |
|
Daily Tasks | 7/30/2013 |
• Went in to BATC to work with my dad on some government surplus items that were donated to Bridgerland. They, BATC, are going to be categorizing and selling the surplus items. I was there to help and show them how to use adilas to track and show the items. Very little work was done inside of adilas. Most of the day was getting organized and sorting out the items. Only about an hour of the day as spent inside of adilas. Just enough to show them parts, PO’s, and photo gallery stuff. 30 miles. • Went to Smithfield to work with my sister and brother. Set up a printer for my mom and did some light training. She will be using it for her herbal business and tracking things through adilas. The meeting with my sister and brother was dealing with elements of time and putting the developer’s notebook up on adilas university. We also talked about some marketing stuff and using the Utah State University campus as a venue for training and sponsoring different events. 20 miles. • Went back in to town to work with my dad and others on the BATC surplus items. Minor work was done in adilas but I feel this could be a good project to help show how adilas can help companies with their eCommerce and web presence needs. Good stuff. 30 miles. |
|
|
AU 1724 |
|
Daily Tasks | 8/8/2013 | • Posted some new videos up on YouTube. Created links to the new videos that were already up on YouTube. Posted some new files on adilas university. | |
|
AU 1751 |
|
Daily Ideas | 8/10/2013 |
-Adilas university was originally going to be for adilas clients. I can actually see it being used more by reps than clients. Or maybe used by reps for clients. They (the reps) go and do some research and then they, person to person, teach the concepts. That way, they make the money from the training. -I used to say “as is”. Steve likes to say “as is now” meaning it will continue to progress or go forward. I like it with the word “now” attached to it. Kind of fun. -We have had the request to add wholesale pricing settings to adilas eCommerce options. Basically, the wholesale people want to show everything except for prices unless, or until, the customer logs in. Once they know that they have a valid customer, they want to show the shopping cart and wholesale prices. The system needs to be sharp enough to determine a login and a customer type. It will then either show or hide the pricing. -This hasn’t been asked for yet, but Steve mentioned that it would be cool if we could show retail pricing for the general public and wholesale pricing for wholesale customers. We will tackle this as it comes up. -Round two of elements of time is gaining momentum. This would include job costing, special payroll, rentals, reservations, bookings and virtual dispatch type functions. -Eventually, these subs of time (functions of time) that are listed above will also need to be eCommerce ready and available. What it the availability? Can I reserve this? Can I book this? Can I pay for this online? Time is very important. -When we get time, it would be cool to circle back around and check the permissions. There are a number of “black” or “under constructions” permissions that need a little bit of loving. They are: - Read Email - Inventory Special Search - Build A New Report - Rentals - Reoccurring Internal Invoices - Migration – Old Data - Add/Edit Payment Type - Cross Corp Billing - Any Corp Billing - System Monitors -When dealing with the API (application programming interface) use the system to create a special transaction key or API code for security. We may want more than one and make it somewhat random so that each corp will be unique or special. |
|
|
AU 1752 |
|
Daily Ideas | 8/12/2013 |
-I had the idea, while at church, to recruit helpers from with-in adilas for certain projects. Get the people who want to help. -We will need to upgrade the adilas university website. It will need to be a ColdFusion 10 server, have its own SSL, and have a working copy of the adilas code all on board and live. -Eventually, I would like all of the adilas university content to come right off the adilasuniversity.biz site. This includes making adilasuniversity the master spot for all help files and user manual docs. -I imagine that eventually there will be many different domains that serve up adilas content. Ideally, they should all link to a central training place. Why not use adilasuniversity as that centralized spot? -Recruit help for the adilas API, user manual, and content server from within the ranks of adilas. They already know the system and have a vested interest in making things work better or smoother. -As people begin to help us with different projects – it would be cool to use elements of time to communicate and coordinate efforts. This would also include photos and scans that get attached to elements of time as well as sub notes and comments. -We need round two of elements of time very soon. -Once place where additional history notes may be needed are dealing with photos and uploads. Who, when, what, etc. Track photos/scans history. Currently this is not being done. Another place may be the customer name in case somebody changes it. Another may be a vendor name. |
|
|
|
AU 1768 |
|
Daily Ideas | 9/3/2013 |
-“Data in detail” – Quote by my father on 9/3/13 while on a morning walk. He said that one of the things that make adilas unique is – “Data in detail.” Another one from him is, “Not all data is created equal.” – February 2013 training session. -The receive invoice page needs some pagination. It also needs a paid date to be shown. This is an older page that has not had much action for quite some time. -We talked about doing a “get to know you” flyer for the groups and system player groups. I also think we need to do similar type flyers for the functions and core concepts. We need to let people know what we are doing! -A future project might be to document what each page inside of adilas does and what page params it allows and/or requires. -On the adilas API (application programming interface), we need to check for an SSL connection. If not, we need to prompt. If any decoding is needed, we need to decode or encode values as needed. This needs to be done on the application level. Not at the user level. -When showing the tech level of the API or adilas university – Go by function not by page. Show the concepts or how the different methods work and function, not necessarily how our pages work and flow. Show the users what is available to them through the API. If needed, show main page flow. This should help the end user understand what is going on. |
|
|
AU 1798 |
|
Daily Ideas | 9/13/2013 |
-Referral marketing idea… $10.00 a head per day for active participation in the free adilas training course. This goes to the person who got somebody to go to training. Cap it at $100 per day or 10 people per person who did the inviting. The person who attends the training doesn’t get paid; they just get the free training and get inspired. The benefit to adilas is in the referral marketing and realizing how for that training can go. People love our product once they know how to use it. If they don’t take the time to learn it is like expecting a saw and a drill to build your porch. If you know how to use the tools, you (meaning the person not the tools) can then build a porch. Tools require skilled operators! Why not incentives or encourage people to get trained. I wrote a whole email with this idea in a proposal type format. See the email from 9/13/13 with the subject of “A referral marketing idea.” -Along with this same referral marketing idea… We could do different amounts for smaller blocks. Say $5 a head for smaller 2 or 3 hour demo sessions. This $5 a head helps pay the rep for opening his/her mouth. Then hopefully they, the reps, could pick up new accounts and/or get one-on-one demos setup. It is a small little amount up front with the possibilities of landing actual real deals. -Maybe we could try small info sessions and do ice cream or pizza or pay the per head amount. Basically, most people don’t want to give up their time and effort for nothing. -We may also get certain people and pay them to man booths, tables, or do flyers. Ideally, these would be reps that know the product and could get some business out of the events. -As a note, if we did do the referral marketing ideas… We may need some way to verify things to make sure people don’t say they have a certain number of people and they really don’t. Just as ideas… a video of the session, a photo, a recording, paper reviews, contact info, or a digital sign-in sheet. The digital sign-in sheet could help the rep get back in touch with the people who come to the events, training, demos, or work sessions. Heck, they could eve use adilas, create an element of time and assign customers (prospects) to the element of time. Once we add a photo gallery for time, they could document the event. Tons of options. -Another idea is to co-sponsor an event with an adilas rep or consultant. Then the visiting adilas team member could vouch for what goes on and numbers for the event. -Tons and tons of mini events, training sessions, and demos. Small blasts may work better than multi=day training events. -An idea from my brother – show the potential of each group within adilas. There are 12 main player groups. Set up a teaser video that shows what is possible and what flavors each group had and/or is capable of. Almost to the commercial level per group. For example: Invoices are one of the 12 groups. -Invoices could have customer, multi-customer, no customer; tied internally to a stock/unit, be a transfer invoice, be a transition invoice, be an eCommerce invoice, have one line item, multi lines, hidden lines, mixed tickets, elements of time, on account, single payments, multi payments, change due, disclaimers, custom verbage, special paperwork, photos and scans, signature lines, different views and sizes, etc., etc. Show the group overview in a commercial type video setting. -We are going to need a centralized place for our visual teaching tools, graphics, analogies, video clips, and other animations and assets. This could be on adilas university or under the button on the interactive map that reads “objects & data over time”. That button is right smack dab in the middle of the map. -On eCommerce, we need a setting that will allow shipping to be skipped. For example: a downloadable product or a service or a booking or reservation or a rental. Adilas does reoccurring payments and monthly subscriptions, that doesn’t need any shipping info. We might need the option to be smart… meaning can the system tell if the items be purchased are physical or unlimited. -We need the option of sending an email with custom verbage and/or custom information. This could be general day-to-day use or notices or it could be part of eCommerce. As a note, this email and/or text message capability may need to be a setting or a one-to-many between corporations and items or corporations and transaction types. It may also need to be dynamic or user driven. -We need to ask a few different corporations for permission to show other potential clients or people how they use adilas. This would be strictly for demo purposes. Another idea is to literally make a small commercial of how they use adilas. We could film them using it, them showing it, and then let them see the final video. Then we wouldn’t even access to their site. -Dealing with tools that we expect to do the job without any manual intervention…. I was thinking about the Disney/Pixar movie “Wall-E”. At one point the captain is presented a user manual (a book). The captain gives a verbal command of “Manual Open!” Instead of saying manual like a user manual he says it like a Hispanic name of Manuel. Eventually the robot Auto (huge play on words) physically opens the book for the captain. This whole scene is a light play on words between manual and auto. Long story short – we almost expect tools to be at an auto level. However, many tools are made for manual usage and do nothing of themselves. Think of a power saw and a power drill – they will just sit there until picked up and used. In the right hands, those two tools can help to make beautiful work and do a great job. |
|
|
AU 1800 |
|
Daily Ideas | 9/17/2013 |
-Spread out tons of tiny video clips inside of adilas. Have some sort of little icon or link or image where people can get help on anything inside of adilas. Basically, take adilas university and have it all over the place in mini segments around the site. It will all be together on the adilasuniversity site, but spread around inside the main site. -Adilas is like an iPhone or iPad. It has tons of potential depending on what apps you install and use. Inside of adilas it depends on permissions, settings, tools, and features. |
|
|
AU 1803 |
|
Daily Ideas | 9/28/2013 |
Random notes – Woke up 3:30am and couldn’t sleep: - Use graphic mock-ups and layouts. No code is required and a picture tells a thousand words. Super-fast and it creates a model or goal to build towards. - Make graphic flow of different pieces. This could even be simple flow charts. - Use existing pages as default icons. - Get notebooks to my sister and get caught up on what is in the notebooks. - Help Steve push the adilas world to a real usable level. - Maybe think of small trial periods for approved persons. - I need to do more teaching and training. This could be in ColdFusion, adilas, or adilas sales and service. - Check out the operations seminar at USU. What a great resource. - I need to play as a team instead of just doing things all by myself. - Contact my brother and work with him on some of his commercial ideas and what not. - Get creative on funding and money flow. - Figure out new projects, scopes, and budgets. - Go back and review notes from 12/24/12 (December of 2012). Lots of good notes and ideas. - Figure out what is promised as far as tools and features. - Schedule the next training event. - Post the first round of the user guide. - Recruit internally. - Put Shari on task with the user guide. - Adilas university may end up being a non-profit. Until then, go ahead and just run it as it. We can transition later. - Get the database ready to be duplicated. - Finish up tools and features for eCommerce. - Get the content server up and online by end of 4th quarter 2013. - Organized and prepare the next whole level. Take adilas to the platform level. This is us dreaming to a super high level. Reach and stretch a bit. As a note, plan that this next level or model, at some future point, will also break and become a stepping stone. Include: custom css, layout, design, destinations, flow, tables, code, choices, in-line custom code, API options, pre-built templates, pattern after elements of time with build your own types and apply functions as needed. Be able to create your own flow and check points. Think of holding areas, checkpoints, permissions, and flow. We also need to add correct data mapping back to states and status and holding areas. Track the full life cycle of the items and transactions. - You dream it up – we’ll wire it up! - Show flow charts. This could be recommended flow, options, and special circumstances. - Use other people’s money to fund the projects. - We bring experience and vision to the table. - We will build on what we have. - The new platform level may need steps, phases, and different levels. - We at adilas need to follow our own advice and dream it up! - Document it, sketch it out, draw it up, and go to it. - Make visual homepages with icons and sections. - Get the notebook caught up… It takes extra effort to do things twice. Writing and sketching and then rewriting. - We have been planning this upgrade or next level for years. This doesn’t just come out of nowhere. - Think “platform”! Think “world building”! Think “in-line custom code”! - Make things consumable! - Plan the education and training from the get go or right from the start. This can’t be an afterthought. You almost plan it from the beginning and let it lead development. Then it truly becomes marketing. - The project for the developer’s notebook is very important. We have to share and communicate what is going on. This notebook is a huge part of our communication and direction. - Plan it out, seek help, use other people’s money to fund the projects. - Our plan is to share and seek protection out in the open by sharing. We also want to focus on the abundance model. Not only is there enough to go around, this model deals with more than money and business. My sister said the other day, this model also deals with people, skills, ideas, talents, drive, etc. Her saying that really helped my open my mind and think differently. -Start with education and an open API (application programming interface) or open source code. Those are two huge keys that we currently have shadows of but are lacking the full implantation of those features. - In order to get where we are going… You have to have some time in the game. - Education needs to be brought up to the marketing level. -We may end up leap frogging ourselves. That would be kind of fun. - Build to eliminate bottle necks in flow, processes, code, education, marketing, people, and other pivotal points. - We want to get marketing involved from the ground floor level. - On a personal note, I’ve done a number of projects and tried to market after the fact. That process is pretty tough. We need to see the vision and fund the projects with the vision. Self-funding is very difficult. - Plan for mobile and new technology! - Plan for data production and duplication! - Plan for snap-on and bolt-on additional features. It would be super cool if some of the code and features already anticipated external connections. Think application flex grid level. - Depending on our goals… we might need to start a whole new company or at least another arm of the current company. - Talking about new or extending business can be scary. It feels big! But, we’ve done this before and , most likely, we’ll do it again. - What about timing for this? That is still kind of a big unknown. - I am sad now. Sitting here thinking about the size of the project that we are currently in and thinking how big this current proposal is. In order to build, the weight, load, and wealth must be spread out. And then I start thinking... Build on what you have! And, the mode softens. I need to remember that saying. - Use adilas' existing base and experience to market the next level of growth. Again, build on what you have! - As an idea... I know of a company with a dream and they are daily building towards it. Would you like to hear more or become a part of that vision and dream? The company is called "adilas.biz". Come and check it out! - The taboo word is not "break" or "break it". The real taboo word is "eventually". This came from a small conversation during one of the lunch breaks during the Logan September adilas training course. - Choose your flavors (like an ice cream shop). - Pick your tools (like a tool shed or toolbox). - Skin your engine (like a vehicle). - Build your world (like worlds of a solar system). - This might be a fun part of the adilas formula flyer. Maybe replace the results section of the flyer. - Sample sketch of this idea (see photo gallery, sketch includes: Choose your flavor (ice cream treats), Pick your tools (tools for building), Skin your engine (different vehicles), Build your world (different worlds and planets), adilas logo in the middle. |
|
|
AU 3642 |
|
To-Do & Brainstorming for the Teacher Site | 9/30/2013 |
To-Do’s - Customer upload for a client - Recruit trainers for the October training session - Send out email for interns that didn’t make it - News & updates – October adilas training pdf flyer - Send out email for ColdFusion class - Print out more business cards - Do the Teacher stuff - Update YouTube & adilas university site with new files - Put all help files or at least give access to them from adilas university. Maybe even allow people to see the developer’s notebook. - How can I help and get the biggest bang for my buck? Help videos, user manuals, graphics, code, selling, coordinating? Interfaces, mapping, flow, flyers, commercials, documents, training? Brainstorming layout for forms on the teacher site: (Please see scan in photo gallery) |
|
|
AU 3643 |
|
Brainstorming: Projects Needed for Adilas | 10/7/2013 |
Projects that are needed for adilas: - More options for getting to other custom interfaces - Custom add bulk flex grid for the teacher/student site & for grades - Finish up eCommerce and online bill pay section - Email invoices (by Nov 15th) – promised - Invoice classifications – custom checkpoints or financial mapping points - First Data Gateway - Trans First Gateway - PayPal Gateway - YouTube video project - Adilas API project - Payroll taxes for different states: o Utah, Idaho, Michigan, Arizona, Washington, California, DC, and a bunch of other states ($50 per or each) - Round 2 of elements of time - Photo galleries o Deposits, vendors, users, & quotes - Content server – All 12 main players for PDF, Word, Excel, audio & video files - $1,000 - Internal Cost Corrections (ICC’s) - Multi Statement Function - $250 - Wholesale pricing for eCommerce - Texas 130-U PDF document - Preform & investor package - Adilas eCommerce - PCI Compliance - Adilas world - Adilas university - Show the upcoming projects – funded projects - The developer’s notebook - Expose help files - User guide - Mapping out player groups system - Ice-down date – disable all editable fields, not just the submit button - Copy of the system ($1,000) & splitting out the database ($1,000) - Merge customers (by Oct. 31 – promised) & non-edit on customer name - Custom labels – barcodes & em-bedded barcodes – custom print jobs |
|
|
AU 3645 |
|
To-do's | 10/25/2013 |
Scratch Paper Notes – To-Do’s - Read a contact’s stuff - Server research – hot fixes, ping, and resets - Check on money movement options - Flash interface – start with what you have & know you can always circle back around. Just get it out there. - Roll call page & virtual GPS on adilas - Map it out - Skip training for November & December - Print out notes from training session - Review the developer’s notebook - Follow-up on tech support & emails - expenses - “adilas diversity” – my dad 10/28/13 - Adilas world, adilas university, plan it out and go get it |
|
|
AU 1883 |
|
Daily Ideas | 11/21/2013 |
-Thought about videos on adilas university… I thought that it might be fun to get some fun screen shots and show them as part of the video review. I was hoping that it would entice the users to want to watch and view the video clips. For example: video such & such (sketch on notebook page, see scans for 11/21/13) -On the corp-wide settings. Maybe put some basic info to help the people (our users) know that there are some other admin settings like: custom homepages, custom interface options, and tons of eCommerce settings that are available. This list may also include email invoice settings, special “hooks” to 3rd party products, etc. -On eCommerce… I want to make sure that a user (customer) can login even if no cart options are set. Basically, make the eCommerce backend be independent of the shopping cart and ability to show web inventory and items. -On eCommerce… we need a setting to control the default customer type for adding a new customer to the database. Currently the new customer gets to select what type they are. That could be a possible problem for some industries. -Time and space are two huge keys. Lately we have been focusing a lot on time and tracking objects and data over time. The other piece is “space” or organizing flow. In some ways, the word “interface” could be used as a substitute for “space”. The word space doesn’t have to be as big as what we think of space with planets, starts, systems, etc. It could be as small as your desk, your car, your home, your business, your interface. Space is a way to organize what you store or work with. This could be memories, letters, pictures, files, business data, transactions, etc. Things happen over time – we need to track that. As they happen we need to account for that or store that. How and where we store things, comes back to interface or “my virtual space”. I think it is super fun to think about how both time and space or space and time work and play together. This is virtual world building on a whole new level. |
|
|
AU 1889 |
|
Daily Tasks | 12/3/2013 |
• Prep work on the adilas platform concepts and theory. Found a couple good entries in the adilas university site for the developer’s notebook. They were 4/12/12 and 9/28/13. Good stuff. • Making some phone calls on SSL’s and how best to set up server structures. • Went in to Bridgerland to work with the interns. My sister and two interns were there. We started out with my sister doing some training on PO’s, inventory, and parts. We played in a play site and added tons of candy bars and different items. We flipped PO vendors and even did a global find and replace on a duplicate items. After the training we briefly talked about how quick things transfer directly to eCommerce. • We then did a two hour brainstorming session on the current adilas server and database structure. We talked current state and tons about future plans. Lots of talk about platform and making adilas into a full on business platform. Steve joined our GoToMeeting session and really helped out a ton. Of the 2 hour session, Steve talked for about 45 minutes on different subjects. Great session. We recorded the whole session through GoToMeeting. I spent quite a bit of time drawing out small models and diagrams in a graphics program. It worked out pretty slick and helped to illustrate the points that were being made. Awesome session! 30 miles. • My sister and I sat down and went over 10-15 categories in the adilas user guide. She took notes and I talked and showed concepts using some of the training graphics. Fun mix of history, concepts, and basics. -On payroll taxes, we have had the request to check into tax settings for persons who work in multiple departments. Currently, the system treats each employee and each department separately. Some of the employers would like it to track independently, like we do in the back end, and then bring it together in the front end as a group. That way they make sure that the employee is getting enough taxes withheld. |
|
|
AU 3650 |
|
Tech - Current adilas.biz Model as of 2013 & Proposed 2014 Model | 12/3/2013 |
Current Model for adilas.biz as of 2013: (Please see sketches in photo gallery) - Adilaswebservices.biz – web presence parts & stock/unit inventories - Adilas university – small shell with email functionality - Main adilas.biz server – dedicated box, SSL, database, photos, main application box Proposed Model for adilas.biz for 2014: (See sketch on scan in photo gallery) |
|
|
AU 1894 |
|
Daily Tasks | 12/6/2013 |
• Small tweaks on the ACH stuff for Shari. Looking into a web service problem between the main adilas.biz server and the adilas university server. • Emails and tech support. • Recording notes in notebook. Helping an intern with the media/content project. |
|
|
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 2052 |
|
Daily Ideas | 3/1/2014 |
-Adilas flex zone timeline drawing (Sketch of flex zones or virtual waiting rooms, with checkpoints and permissions, and time going in either direction.) (See scan in photo gallery) -Life has to have some flex zones or small waiting rooms. -There may be things that are unfinished – that’s okay, they will stay in the flex zones until they are ready. When ready, they may be advanced to the next stage. -There will be time – just keep going. -Instead of just one timeline (like the graphic or drawing above), there are multiple time lines working together. Time, itself, has many one-to-many relationships. They all play into the bigger whole but are made up of tiny little individual pieces and parts, kind of interesting. -We have a client that is looking for EDI (Electronic Data Interchange) pieces and functions. Steve has done a little bit of research and we’ll only start heading in that direction if needed. EDI is basically a way for one or more computers to talk to each other. Notes from a phone call with Steve on 3/1/14. - Let our developers build their own clientele. Our reps already do this on their own. - Our current top three priorities are: o Package stuff, o Split Cart functions (interface), o API (application programming interface) & 3rd party plug-ins. - Custom documents are a good profit center for adilas. This could include: o Documents o EDI – Electronic Data Interchange o Outside Feeds o Internal Feeds o Loyalty Points o Customer Gift Cards o Labels o Barcodes o RFID o Reoccurring push/pull actions - Maybe think about bulking up or beefing up the custom pipes or custom documents area. - Use the barcode generator (if possible) for some of the custom pieces. If needs be, we could always create a new barcode generator or custom label app if we needed something more robust. - Packaging and subs of part numbers or subs of item numbers. - The deeper we get, the more elements of time appear to be connected to everything else in the system. - Packages and conversions are almost one in the same. One is limited or quantified and the other is open ended or unlimited. - Should we make a whole new item type??? A mix between a stock/unit and a general part? What about backward compatibility (people wanting to go backwards)??? - Steve kept using the phrase “occurrence of…” or “instance of…” when talking about tracking packages. Virtual usage. - The naming has to be dynamic… Just like in elements of time. - Batch, packages, reports - Maybe store dynamic parameters (actual JSON objects) inside of the subs for time called sub comments. These fields are big, they accept HTML, and they are already a sub of time. - Maybe use time for packaging and expiration dates as if it was manufacturing. Think both retail and manufacturing of packages, lots, batches, etc. - On part categories… what if we allowed categories to be stacked inside and/or on top of other categories. Allow it to go as deep as it needs to go. - If we let simple objects connect to each other and to themselves, how do you go back up the chain? I am talking about showing the relationships. Instead of simple nested part categories… what if it were people connected to other people (say like genealogy). The person exists as a single object, they could then be connected to other people or other objects to create a relationship. The relationship then helps to define how they interact and any dependencies or other independent states that exist. It basically starts forming the story as the objects and data move or interact over time. - Make the teaching graphics available, to all users, that we use when doing adilas demos and training sessions. Add a muffin tin, add the dream it up, and add a cup and plate model with an underlying platter or bigger tray. Think stacking objects. - Teach base level core concepts like operations and accounting. - We are going to need a sales and setup team inside of adilas. Help them sell what we have! - Our best sales people are involved in the setup process. - Create a small setup team using existing persons. - Do weekly demo meeting to help get awareness up. - On packaging… what about packages of packages or deep one-to-many relationships? - Packaging may need its own barcode. This could be something simple or it could be cryptic for a main time id, something in the middle, and then a sub of time. Just trying to get ideas. - On elements of time… We have the “anything” sub – pools and subs. We need to get that ready for use. - Packages may contain more than one item. Possible mixed items. - The mother is “time” – then anything that gets applied will be the sub. - Moving items from a “shelf” to a “package” or subset. Think about moving pieces into other pieces. Basically, it is all mini manufacturing or internal builds. - Show the usage over time. - Elements of time… this becomes the master. - “Any” scheduler – everything needs to be tied to elements of time. - Push out the developer’s notebook – stake our claim on some of these emerging ideas – do it in a fashion that helps build and share. Remember, “The rising tide raises all boats.” I think the real quote says “ships” but I like boats better. Ships seem so big. Anyway, help raise the tide! - Work smarter, not harder. - Allow all or “any” of the pieces inside of adilas to be plugged into time or into an element of time. - The different report types are: o Calendar o Time slot o Grouped o Details o Advanced (pick & choose) o Subs and stats o Export to Excel o Time Line Horizontal (new) o Time Line Vertical (new) o Other Formats (new & futuristic) - What if we used Cold Fusion to dump and display objects inline using a cf dump tag. This may have a place, especially in the API documentation and testing zone. - We would like to set up a number of adilas training centers. This could be a great business for us and/or other interested parties. - Prep for a demo meeting. - Use Bridgerland as our first adilas training center. It is a great fit and is already in use. - Pass out flyers for the free demo. Maybe pay a team member $10/hour to pass out flyers. - We are shooting for 50 new clients. - Do the weekly demos on Thursday night from 6-8pm. - Use BATC (Bridgerland) or the Business Resource Center for the software demos. - Maybe show a calendar on the main login page. Have drill-downs to different details, photos, links, and other content. - Have the same calendar show-up on the adilas training page. Start using elements of time. - Get adilas university up and live with help files, developer’s notebook, and training and videos. |
|
|
AU 3675 |
|
Planning - Packaging & To-Do's | 3/1/2014 |
Packaging & To-Do’s: - Check the credit cards and make sure things could clear - Let our developers build their own clientele - Split cart - Package stuff - API & 3rd party - EDI – Electronic Data Interchange o Push or pull or catch o Application flex grid stuff o Two computers talking to each other - Custom documents are a profit center for us o “Custom” – Beef up pipes or bulk up that area o Documents o EDI – Electronic Data Interchange o Feeds o Loyalty Points o Custom Gift Cards o Labels o Barcodes o RFID o Reoccurring Push/Pull Actions - Barcode generator – maybe allow custom to go through it or have a whole other flash app that can take custom Packaging…: - Elements of time – sub of everything - Package thing & conversion thing are one in the same - New item type??? o Backward compatible Process: - New item - Track quantity - “Occurrence of”… o Sub of the items that exist - Naming has to be dynamic… elements of time - Usage or occurrence of… both quantitative and unlimited - Batch, packages, reports - Dynamic parameters (JSON objects) stored inside of the sub comments of time - Use time for packaging as if it was manufacturing - Retail and manufacturing of packages - On subs and sub part categories… what if we allowed categories to be stacked inside and on top of other categories. Allow it to go as deep as it needs to go. - If we let simple objects connect to each other and to themselves, how do we go back up the chain? Show the relationships. Instead of part categories… what if it were people connected to other people (genealogy). The person exists as a single object, they could then connect to other people or other objects to create a relationship. The relationship then helps to define how they interact and the dependencies or independencies that exist. It basically starts forming the story or the objects and data move or interact over time. - Get graphics available to all users – training sessions o Add muffin tin o Add Dream it up! - Teach base level core concepts like operations and accounting - Sales & setup team o Sell what we have! o Sales people need to be involved in the setup process o $35 o Create a small team o Weekly demo meetings (2 hours) Packaging… Continued: - Packages of packages - One-to-many relationships - Own unique barcode for the package o Main time id, something in the middle, sub of time - Time – “anything” – parts & such - Conversions = unlimited & packages = limited or quantified - Packages may contain more than one item - The mother is “time” then anything that gets applied will be the sub - Moving items from a “shelf” to a “package” on subset. Think moving pieces into other pieces. Basically, it is all mini manufacturing or internal builds. - Show the usage over time - Elements of time… this becomes the master - “Any” scheduler - Everything needs to be tied to elements of time - Push out the developer’s notebook – stake our claim on some of these emerging ideas – do it in a fashion that helps build and share. The rising tide raises all boats (ships). (I like boats better, ships seem so big.) - Work smarter, not harder - Allow all or “any” of the pieces inside of adilas to be plugged into time or into an element of time. - The different report types are: o Calendar o Time slot o Grouped o Details o Advanced (pick and choose) o Subs and stats o Time line horizontal (new) o Time line vertical (new) o Export to Excel o Other formats (future & now) - What if we used ColdFusion to dump and display objects inline using cfdump tags. To-Do: - Adilas training centers - Prep for a demo meeting - Bridgerland as our first adilas training center - Pass out flyers for free demo - My brother - $10 per hour to pass out flyers - 50 new clients - 6-8pm on Thurs. - Business resource center for demo - Call intern Classes: (adilas training) - 6th: 12 – elements of time & 2 – flex grid - 13th: 12 – Inventory & 2- Sales - 20th: 12 – recipe/builds & 2 = expense/receipt - Basic Sales & Inventory - Recipe/Build Class - Flex Grid - New Features - Elements of Time - Expense/Receipts - Payroll - Show a calendar on the main login page. Have drill downs to details, photos, links, and other content. - Have the same calendar show-up on the adilas training page. - Get adilas university, live with help files, developer’s notebook, etc. Packaging & Tracking – Goals: - Track – Lots, S/N, Package, etc. - Custom naming - Chain of custody - Ease of use - Deal w/bulk track individual - Conversions (1st) - Packaging - 1-many-many-1-many-many Goals & Conversions: - Trade by lowest - Common factor - Beware of rounding - Standard vs. non-standard - 2 tables: o Units of Measure o Linker – UofM x:y, UofM |
|
|
AU 2047 |
|
Daily Tasks | 3/8/2014 |
• Browsing the adilas site and checking usage for different companies. • Recording notes in notebook, reviewing to do lists, and trying to get organized. Added a couple new graphics to the adilas class and teaching photo gallery. Light research on robotic assembly lines. I want to draw a parallel between a robotic assembly line for actual products and an assembly line for business processes and business data. As a note, see elements of time inside adilas university. Do a search for “robot” and then do another search for “assembly line”. There are some good entries there. • Research on 3D printers and making objects. Emails, tech support, and recording notes. • On the phone with Steve and another developer who is setting up a page crawling engine to pull certain eCommerce and web data out of the adilas web services database for mutual clients. The data being extracted is only web settings for customer eCommerce inventory. Basically, this 3rd party engine will browse a company’s inventory and pull out names, descriptions, and prices. It then shows this data on its own server and just points to adilas servers if the viewer is interested in shopping or purchasing. It is kind of like a shopping app for specific industries. • Small tweaks on the adilas web presence and eCommerce pages. Added some links and changed some default values. Posted files online and let the 3rd party developer know about changes. • Changed the time zones for day light savings on all servers. Small tweaks to the developer’s helper page on the data 1 and data 2 boxes. • Made a few changes to a client’s website. Posted files online. |
|
|
AU 2069 |
|
Daily Tasks | 3/27/2014 |
• Doing logos for different companies. Ended up working on the adilas API calls. Checking off on code changes made by a developer. • Went in to Bridgerland for day three of the March adilas training seminar. We had a great session and all of us learned tons and tons. I got rebuked for apologizing for things that are not done. I’ll try to focus on what is done instead. We covered topics of histories, reports, searching, exporting, business intelligence (BI), web presence, eCommerce, big data, and virtual data portal stuff. One of my favorites was the business intelligence sections. We did quite a bit of class based brainstorming and got some great notes and ideas. Once again, both a friend (class participant) and my mom were the star students. Great session. We also had a wonderful lunch whiteboard session. See elements of time #2007 inside of adilas university site for pictures of the lunch brainstorming session. 30 miles. |
|
|
AU 2115 |
|
Daily Ideas | 4/8/2014 |
-For me… Just keep going – you have a good plan and it is written down. That is huge! Just keep going. If we can’t get to it yet, at least write it down and we’ll circle back around. This is basically a way to pave the road for future projects. -At some point, it would be nice to add an adilas forum (using elements of time) and let users comment on different things. -For our own internal projects… we need to figure out a system that helps us go from water, to slush, to ice on our own projects. See elements of time #1762 inside of adilas university site for more details. (8/30/13) -Notes from April 2014 General Conference. Lots of good answers to prayers. -Circle back and do what has already been revealed. Go back through my notebook and make sure things are done and cleaned up. This will provide some peace of mind. Notes from a phone call with Steve and with an adilas rep out of Denver: - We need to help build a set of standardized spreadsheets to help with data imports and import tools. We are thinking about vendors, users, items, customers, and maybe financial accounts. - Angle for sales… If people want something, they’ll pay for it. This helps us get what we need. - On imports… we need a price structure which will help us to regain funds for using it. - User and consultant levels… building it vs. operating it – big difference and some people get it and some people don’t get it. There are different levels. Our goal is to help where possible. - The rep has a need to migrate adilas data from one system to another. Basically, cut off an old system and start completely new or fresh. Think about selling a business. They want to keep some of the old and then be able to start new. - Application flex grid – getting data from other systems – including data from adilas to adilas. - It is all about “interconnectivity”. - Having a fresh start or fresh re-start of a business is worth some money. Pull only certain pieces as needed to the new system. It would also be cool if certain users still had access to the old system. - A new start could be compared to a snake shedding its skin. This would be virtual pieces that need to be broken off. As businesses change, their needs change, and the way that they do business changes. We need to be able to flow with them to that new level. - There will be more and more demands for the API (application programming interface) as we go along. The goal will be to mix and blend as needed. - Packaging is still a very hot topic with some of these customers. Packaging meaning subs of parts and items. Package controls and package monitoring. - For 3rd part plug-ins and standalone snap-on extensions. We need to have some sort of “pay to play” type agreements. This could be development costs or a commission or kickback structure. - We need to present our future projects to the public so that we can create awareness and get community funding for those projects. Think of water, slush, and ice to get the jobs done. On adilas university, reference elements of time #1762 on 8/30/13 for more details. - Elements of time was added to the system because we found that our future growth depended on it. Well, it’s time to move forward with some of those needs. - I’m seeing a need to get all of our research and plans posted for others to see. Some people may not care a bit for what we offer. Others may really enjoy and gain great knowledge from what we offer in concept, principles, and in practice. The cool thing is that we have applied tons of these different pieces over the years. That is awesome. - For Steve, we may want to open up all three servers for adding new accounts. |
|
|
AU 3685 |
|
Small To-Do List & Database Changes to Make | 4/12/2014 |
Database Changes to Make: - Add to elements of time table - Show on web - Add to customer log - Show on web - Show on calendar Small to do list: - Logos - State tax stuff with an intern - Elements of time o Show on the web o Customer facing calendar o News & updates - Download files from an intern - Show/hide help files – adilas university - Finish up Full Circle connections o Opt in/out email o Opt in/out text o New customer fields o 3rd party page o API assignments & history - Fix MSAI inventory website for a demo site - Folders for images - Passing data to the webservices site dealing with server names and assignments o We need to flip this to the shop folder - Flyer for Colorado o Plan it out - Developer’s Queue o Customer funded projects - Customer logs – show/hide on the web - Customer logs – show/hide on the calendar |
|
|
AU 2127 |
|
Daily Ideas | 4/25/2014 |
-Idea from my sister – Do custom classes and charge $25 per seat. This would be custom topics and custom catered classes. -Have people pre-pay for custom code. -Get businesses to beat the street for us – referral program. -Lots of options for custom interfaces. -Notes from team meeting on 4/25/14. Triangle Sketch: Each on one side: Sales, Training, Consulting o Consulting – Hourly plus commission o Sales – Bird dog fee plus commission o Training – Free -Help fund the training at adilas training centers. Maybe hold back a portion of the monthly fees and use that to help with training. -Setup adilas world – place where people could virtually shop for adilas supported products and services. -Setup adilas university – place where people can learn about adilas, tools, features, functions, scenarios, concepts, and history. -Add to the developer’s queue for projects. Think water, slush, snow, to ice (stages of the different projects). |
|
|
|
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 2128 |
|
Daily Ideas | 4/26/2014 |
Ideas & projects for one of the developers: - Expand and sign-off on custom interfaces for the chooser section. - Graphic menus – Like the printable invoice page. - Ice down date with a fun graphic. This only deals with things that affect the financials. - Scripting the database creation setup step. - Migrating data into mini databases. - Documenting all adilas pages – web/API documentation tables and API stuff. - Build in-line custom code and button settings pages. Ideas & projects for my sister: - Catalog adilas university videos - User guide - Developer’s notebook - Custom classes - Help map out system and flow |
|
|
AU 2109 |
|
Daily Tasks | 4/30/2014 |
• Recording notes from loose pages from the Colorado trip. • On the phone with the Colorado developer going over options for custom shipping and eCommerce. • Recording notes in my notebook. • Reviewing notes and making a to do list. • Posting all adilas files online. Setting up a new computer (laptop) for me to use. • Working on the Highland Vineyards Client spotlight page. Added a new YouTube video player that gets tied in to the media/content server. We will end up using this player for the YouTube videos for adilas university. • Finished up working on the Highlands Vineyards Client spotlight page. Added the new video spotlight to the news and updates page. Made the May training schedule and posted the files online. Good stuff. |
|
|
AU 2320 |
|
Daily Tasks | 5/28/2014 |
• Installing the new SSL for the media/content server. • Went in to Bridgerland for day two of the May adilas training course. We uploaded a number of marketing images and graphics that a class attendee had made (he is also helping with some adilas marketing ideas). See element of time #2268 in the adilas university site. We talked back and forth about the concepts and how to get things (people and objects) to work together. We did some basic accounting work and talked about relationships. After lunch, we took the interactive map and split it up into different sections. Each person then reported and/or presented on what their part of the map did. It was crazy to see how every section either pulled from or was connected to the other sections. After the map graphic, we then went to the GPS (Global Positioning System) core graphic. We talked about flow and virtual feeders. We also talked about content or files. We decided that media/content and files were kind of like one of the main 12 player groups but may even be bigger than the player groups. We decided that we need a link to the media/content homepage right from the center or hub of the system. After the GPS core graphic, we used the plates and cups graphic (virtual buckets and how we store data and create objects). We went through a number of scenarios and mapped things out in the bucket model. At the end of the day I worked with a developer on getting him into the API socket model for his first custom project. He got half down as a retaining and startup fee. 30 miles. |
|
|
AU 3699 |
|
Adilas Versions & Progression | 7/31/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. |
|
|
AU 2872 |
|
August 2014 Monthly Recap | 8/1/2014 |
The majority of time this month was spent on a huge database copy project. This is a really exciting project for adilas as it will allow greater flexibility and options for clients. This project included hours and hours spent prepping tables for copy, creating new database structures, planning, scripting database table levels, and more. With the ability to copy, move, and start new databases, it will be like the difference of allowing clients to have their seat on the bus (current shared model) or have their own motorcycle or agile vehicle (future individual model). Allowing clients to work in their own adilas environment, instead of a shared environment, will greatly increase the speed and agility of their adilas. Other exciting new projects were started this month such as, working with a cash kiosk system to provide integration for users between adilas and cash kiosks. Adilas now has an expanded chooser section with over 20 new options available to all users. Initial tables and code for the in-line discount project were started as well as a custom behavior tracking project for a school. After attending a copyright and patent workshop we continue to feel an ever-increasing need to get more information out about the core concepts which adilas has been built on and functions by. We want these core concepts and ideas to be freely known, available, and used by people all throughout the business world. For more information on this entry specifically, please see element of time #2774 here in adilas university. *We hope you are enjoying the adilas developer's notebook! Please utilize and explore the vast search capabilities of adilas to find more information throughout the developer's notebook. For further questions, or help, please feel free to contact us at: support@adilas.biz. |
|
|
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 2764 |
|
Daily Tasks | 8/2/2014 |
• Working on the icon menu for invoice line items and the add/edit main invoice page. Posted files online and light testing. • Working on showing all help files “as is”. Trying to get the pieces we have done out and about. • Working on showing all adilas university elements of time. This deals with the developer’s notebook. My sister has been working on this project for months. Good stuff! • On the phone with Steve going over our current game plan. We talked projects, funding, direction, and vision. Lots of good stuff coming down the pipeline. • Working on a time related interface project. • Writing a long email about free adilas API code and documentation. Included the existing stuff and also included the futuristic stuff that we are developing for our new JSON API socket connections. • Reworking a custom interface page that shows the time slot functionality on the time homepage. Cleaning up code and figuring out what params are needed for the mini time project. |
|
|
AU 2793 |
|
Daily Tasks | 8/14/2014 |
|
|
|
AU 2794 |
|
Daily Tasks | 8/15/2014 |
|
|
|
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 2800 |
|
Daily Tasks | 8/22/2014 |
|
|
|
AU 2843 |
|
Daily Ideas | 9/6/2014 | -Thinking about the data and business assembly line concept. We've got to get that out there to the world. It deals with world building, automated pieces working together, and kind of like a robotic manufacturing facility – but for data and business logic vs. normal manufactured goods. The data assembly line for businesses. See notes back from 8/2/13. Also search adilas university for notes regarding “assembly line”. Lots of notes on the subject. This is the future of many businesses. It need to be protected as a general universal concept. We all need it! | |
|
AU 2846 |
|
Daily Ideas | 9/12/2014 |
Up early with seasonal allergies so I decided to do some brainstorming on what we need to require for adilas developers. New adilas developers will need: 1. These products installed on their laptop: Adobe ColdFusion 10 (or higher), MySQL 5.6 (or higher), and some kind of editor for code. Examples might be Adobe Dreamweaver, Adobe ColdFusion Builder, Eclipse, etc. The code editor needs to be able to handle HTML, CFML, and Java Script. 2. Other product recommendations are: Adobe Creative Cloud, Adobe Acrobat Pro (able to create PDF forms), MySQL – Front (database programming) and Microsoft Office products such as MS Excel & MS Word. 3. A basic understanding and knowledge of the following: • HTML Basics - Document structures - Links - Tables - Anchor tags - Frames and targets - Lists (bullets & numbers) - Formatting – bold, italics, underline, headings, fonts, colors, sizes, etc. - Nested tables - Div tags, alignment - Other tags – line breaks, paragraphs, horizontal rules, etc. • CSS basics • Java Script basics • ColdFusion basics - Comments - Variables - Cf output - Dumps - Scopes – variables, URL, FORM, application, session, etc. - Tables & HTML Forms & Form controls - Naming conventions o Database o Variables o ColdFusion o Etc. - Conditional logic – if, else if, else - Nested if statements - Loops – lots of different kinds o Basic index loop o Lists, arrays, structures, query o Nested loops - Lists - Arrays - Structures - Database Logic - Queries - Includes - Redirects - Parameters - Validation - Custom Tags - Functions & Methods - Complex Data Structures - External Options – Convert to PDF, Excel, Web Services, API, Email, Etc. • Database & SQL Basics - Relational Database Models - Select Queries - Insert queries - Update queries - Table joins - Scripting changes - Queries of queries (ColdFusion) 4. A basic understanding and knowledge of adilas, its form, function, structure, and vision. • World Building Concepts • One-to-many relationships • Permissions & Settings • 12 Main Application Player Groups: - Customers - Invoices - Quotes - Parts & General Inventory Items - Stock/Units – Serialized Inventory - Elements of Time – Calendar & Scheduling - Employee/Users - Vendors - PO's or Purchase Orders - Expense/Receipts - Deposits - Balance Sheet Items • Flex Grid Tie-Ins • Intro to Accounting • Photos, Scans, & Content • Payroll & Timecards • Web Presence & eCommerce • Locations & Tax Settings • Documentation and other developer specific topics such as help files, custom settings, navigation, and code sign-off's 5. Progress Reports, Testing Understanding & Knowledge, & Completion • Classes attended – list, sign, and date • Tests passed – list, sign, & date • Manuals, resources, code samples, etc. • Different Levels - Adilas Intern - Adilas Developer - Adilas Project Lead - Adilas Trainer • Completion Records - Sign-off's - Diplomas & certification • Adilas world Other notes: -Teach live classes for these subjects. Charge for the classes. Allow testing out of any subject. Charge for testing. Cap testing time frames as needed. Code samples on FTP servers. Use adilas university. Create actual manuals for both online and printable PDF's. Use GoToMeeting for online classes. Post class schedules and agendas and itineraries. Use elements of time to hold all of this stuff – as much as possible. |
|
|
AU 2833 |
|
Daily Tasks | 9/20/2014 |
|
|
|
AU 2834 |
|
Daily Tasks | 9/22/2014 |
|
|
|
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 2870 |
|
Daily Ideas | 10/11/2014 |
-Using in-line extensions will give us the flexibility of Microsoft Excel with the power of a relational database and cloud based infrastructure. That will be awesome. -The key pieces are: 1. Centralize the data 2. Be able to collect and store the data 3. How to interact with the data 3.1. Interface 3.2. Flow & Processes 3.3. Analytics & Reporting 3.4. BI (Business Intelligence) & Big Data Space & Time Brainstorming: -Brainstorming on project phases and sub locations... Theses are subs of elements of time (and space). These pieces position or arrange how and where and what is happening or has happened or will happen. I think that we need to keep them subs or functions of time and space. However, I also think that we need to record the current state or status on the main. This allows it to be searched and referenced quicker. -We already store the action status value on the main elements of time table. These sub locations or projects phases would be the same way. We would hold an unlimited list of sub locations or project phases on or in the sub tables... but we would also make the current sub location or current project phase be part of the main element of time. -I'm really excited to see “space” or organization of time start playing into the mix. This is exciting! -If we are talking about subs showing up on the main individual data items or data objects, there are other pieces that want to be counted or accounted for. For example: Say a person was adding sub dates and times (virtual timecards) to a project. It sure would be nice if the total amount of time (sum of the subs) could show up on the main. All of the details are still held in the subs, but the current value becomes part of main. This is also true for things like action status logs, sub dates and times, project phases, sub locations, etc. -Elements of time and space need to be a foundational wrapper for all functionality for adilas. We already do this in a very light way. Invoices are assigned to locations and dated; PO's are assigned to locations and dates; deposits and expense/receipts are assigned to a date and one or more locations at a time. Inventory is tracked per location and by date (sometimes multiple dates). Almost everything we do has a component of space (locations and layering) and time (dates and date/time stamps). We already play this game... What if we just take it to the next level and allow the users to virtually wrap the system, the groups, and the individuals in both time and space? That would be awesome! -Time and space is ok (still works) but space and time sounds better. What about elements of space and time? -What if we add the word “space” into all of our pieces of documentation, literature, notes, quick search, etc. It may be made fun of at first but I think it could gain some ground especially if we start teaching and using those concepts together. -On the quick search – I would like options to search time or elements of time. I would also like a quick search option for space and time or elements of space and time. The space and time options could search much more and find all instances of things in both main and sub tables and database fields. If you searched space and time it could be the global adilas or all adilas searchable. -Locations and dates are a general way of saying space and time. We already knew that dates and times were important but we didn't know how deep locations or layering pieces would be (organizing your data). We've got to include space... It adds to and increases what dates and time can do by itself... It is a compound concept that needs both space and time! Think of our little assembly line graphic for our world building concepts... (Please see sketch on scan in photo gallery): -Space is how we organize over time -Pretend that the dots are checkpoints or key phases (dates/times) -Pretend that the top line is operations and the bottom line is accounting -Time goes both directions -Pretend that the vertical lines show permissions or access levels. Who gets to play at what level? -Pretend that the pods are areas or sub locations or departments (space) -In between checkpoints we have to allow some flex in the model -Lately I've been toying with the idea of a wrapper or a way to combine core concepts. I want them (core concepts) to interact and play together. I've been headed towards a wrapper of time (see entries from 5/22/14 and 6/3/14 in adilas university – developer's notebook). Anyway, my new direction is a wrapper or foundation of both space and time. You've got to have them both. -The bottom level (number 10) of the world building concepts currently says... Run all levels over “Time”. I think it needs to read – Run all levels through “Space” and “Time”. The word “through” may be a good general term for a wrapper, media, medium, or channel. We'll try that and see how it goes. |
|
|
AU 2877 |
|
Daily Tasks | 10/13/2014 |
• Recording notes and concepts on space and time and 3D objects and 3D data models. Kind of dreaming. • Reviewing notes and logic for in-line discounts. Checking math to make sure that the calculations were correct. Started going through code pages one at a time to add the new pieces. Working on the add to cart page. • Email to a client about a custom invoice. Created a quote and logged some notes. Apparently, there had been some verbal promises made but nothing was in writing. I officially started the ball in motion. • Emails and tech support stuff. • Helping an intern with his new barcode and label project for a client out of Texas. Called and talked with the client to see how things needed to be done. • Working on logic for in-line discounts. Light tech support for a client out of Arizona. • On the phone with the Colorado developer talking about extensions and flex fields. We also lightly talked about space and time as a wrapper of sorts. Just basic concept level stuff, nothing too deep. • More discount and flow logic. An intern came over and we worked on his web/API documentation project. • Getting notebook scans ready to send to my sister to enter into the online Developer’s Notebook on adilas university. |
|
|
AU 2878 |
|
Daily Tasks | 10/14/2014 |
• Emails on new permissions for invoices and limiting invoices to a specific salesperson. Also helping an intern with some css placement for a custom label job. • On the phone with Steve going over direction for the sub inventory and cost controls (packaging) section. The first hour was basically a pitch to head towards round two of elements of time as a virtual wrapper for all main system player groups. We did a GoToMeeting session and were drawing and talking concepts for over an hour. Really fun session. We used the graphics from 10/9/14 as a basis of our discussion. We also used the interactive map and the GPS core layout graphic to show flow and concepts. I had a lot of fun. 3D or three dimensional pieces were brought into the discussion. As a note, the 3D elements are: x=Time, y=Money, and z=Space. (Please see sketch on scan in photo gallery) o X – Time is on the bottom – it keeps running and may be broken down into years, months, weeks, days, hours, minutes, seconds, etc. o Y – Money flows upward or downwards – In business a point or trend that is flowing upwards is often a good thing (not always). Also, we want all monies to be tracked clear to the bank and financial level. Think of cream rising to the top. As a historical note… My dad is the one who came up with money as the y axis. That came from a walk earlier this morning. o Z – Space provided the depth structure of the items as they relate to time and money. Space allows for organizing, stacking, layering, packaging, combining, and separating. There are tons of things or attributes that may be applied to space. o Anyway, back to the telephone meeting, we used the last hour and a half talking about requirements for sub inventory and cost controls. See elements of time #892 in adilas or time #2786 in adilas university (developer’s notebook) for the actual brainstorming document. We spent a lot of time dreaming and talking about subs of subs, extensions, matrix, rules, and assignments, sub attributes, packaging, barcodes, space, etc. Great session. • An intern came over to work on the web/API documentation project. I helped him out a bit and tried to get organized. I started entering subs and elements of time to help us monitor custom code projects. We really need to do this. • Recording custom code projects into adilas – using elements of time. |
|
|
AU 2879 |
|
Daily Tasks | 10/15/2014 |
• Recording notes and pushing up brainstorming docs to elements of time. • Research on barcodes in Adobe PDF documents. Reinstalling Adobe Acrobat Pro. • Drawing pictures comparing 2D and 3D objects in my notebook. This is basically the history of how our vision of the assembly line for data came about. Steve originally came up with the concept of the assembly line for data in 2008. As some of our meetings progressed, a number of questions came up about how to handle different scenarios. See elements of time in adilas university from January 2008 to December 2008. Search for the words “balance sheet” between those dates. Around November of 2008 we were getting pretty deep. It was then that Steve had to help explain that our job was to just show the data back to the user vs. forcing a perfect balance. He drew the original analogy of... Operations & accounting: Ideal in a perfect world or controlled environment vs. Real world requires flex and possible variables (please see sketches on scans in photo galleries). Original model or analogy done by Steve in 2008. • As of now, 10/15/14, that model has grown and developed into a full 3D (three dimensional) model using time, money, and space (depth) to track user’s actions and reactions. Basically a 3D cause and effect model. We call it an assembly line for data. See a couple pages back for a visual evolution of our model. • I couldn't help it... I was so excited about taking our data assembly line concept to 3D that I spent a couple of hours creating some adilas.biz 3D world building graphics. • Adding new 3D world building graphics to a new 3D world building help file. See the following web address – https://data0.adilas.biz/top_secret/help.cfm?id=483&pwd=building • On the phone with Steve talking about projects. • Worked on the show all help files page. Small tweak on the add/edit media/content page to allow a direct data drill-down link to occur or point to the underlying data or main tie-in. • Added the vendor as an output option on the grouped PO line items. Posted files online and did some testing. |
|
|
AU 2903 |
|
Daily Ideas | 10/24/2014 |
-I really want to help with the developer’s notebook project and adilas university for videos and training. I’d love to budget an hour or so each day per project. I think that would be fun. -Just wanted to record this. I had a client call me today and ask why we are soliciting their employees to come to work for us. I heard her out, but basically said we are looking for people with skills. All work is independent and may be done on the side, as moon lighting, or as an independent. The lady said that we are stealing her employees. I tried to say that our goal is not to steal an employee but we do openly solicit people who have skills and want to help. That is part of our model. As a side note, I personally don’t even know the person who is in question or who has been solicited. The client was basically calling to complain about what was happening. As a follow-up, I did send out an email to the core adilas players reminding them to be kind and tactful if they are soliciting skills and talents. |
|
|
AU 2893 |
|
Daily Tasks | 10/31/2014 |
• Swapped out the training flyer on the login page with a new banner ad. • On the phone with Steve. We went over some code questions and talked about upcoming projects. Trying to catch and communicate about the vision of where we are headed. • Working with an intern on graphics. Got him started on building his own icon menus for pages. While he was doing that, I was reworking some banner graphics. • Added 3D world building concepts to the banners. Purchased a couple new domain names for assembly line for data. • Finalized the new banners and put the high resolution PDF's online. I also added new elements of time with graphics and links to the new banners. The second banner has verbage and graphics dealing with 3D world building, assembly line for data, custom data engine, and real-time data portal. See elements of time #2788 in adilas university site or #901 in the main adilas site. Trying to start recording as we go vs. waiting until the end. |
|
|
Adi 905 |
|
Logos for adilas university | 11/4/2014 | See attached... These are three ideas that were created by Dave Forbis for logos for adilas university. We can add any verbage that we want, these are just the logos or shapes. | |
|
AU 2789 |
|
Logo ideas and proofs for adilas university | 11/4/2014 | See attached... These are three ideas that were created by Dave Forbis for logos for adilas university. We can add any verbage that we want, these are just the logos or shapes. | |
|
AU 2909 |
|
Daily Tasks | 11/4/2014 |
• Brainstorming on presets and allowing a number of predefined functions to be a sub of time. See prior notes. • Brainstorming on simple tools like pencils, paper, grids, spreadsheets, etc. Also some thoughts on "tweeners" or "inbetweeners". We need to set the key frames and then allow others to help fill in the gaps between the key frames. See notes on Disney and Flash (back a page). • Got some new logos from a marketing consultant for adilas university. I put them online and sent an email out to different people trying to get their opinion. Other email stuff. • Working on the standalone discount options for the new discount calculator page. I need code to do both in-line discounts (new) and standalone discounts (older). • On the phone with Steve. We talked options and did a GoToMeeting session. We worked on the adilas world (live help) pieces and showing images and gallery stuff. We also worked on some of Steve’s sales reports and graphs. • On the phone with a consultant going over things for a conference call later today. Also reformatted the new adilas banners back to a Photoshop file type for a print shop. • Tech support. • On the phone with a client. We talked adilas for a while and then we talked about the client's own virtual warboard product. I took a page of notes but it sounds like a fun future project. It will include transforming day-to-day business data into a virtual game or virtual reality model. Kind of like my idea of making a virtual movie of how the data and players interact and play together. See my notes from later 2010 into early 2011. Anyway, I have a page of notes. This client’s stuff has some purpose based projections and cascading data forward pieces that could and will be fun to play with. • Working with my brother on formatting data and variables. • Working on clearing all discounts that are set from the bulk discount calculator. • Working on displaying the data on the bulk discount calculator page. The project is slowly coming together. |
|
|
AU 2936 |
|
Daily Tasks | 11/14/2014 |
• Working on custom code for a shopping cart include. Going line by line. • More work on a developer’s custom shopping cart code. On the phone with the developer and then emails. Sent him my final copy and revisions. • Working with an intern on new training criteria for new developers. Uploaded some new files with icon menus. Found that some of the new files had overwritten some previous changes. Small version control issue. Reverted back to older files and put files in question into a temporary staging folder. Fixed problem online and talked with the intern about sign-off processes. See other notes for details. • Recording notes and ideas on version control and code sign-off processes. • Meeting with an adilas associate about project management and bringing on new qualified adilas developers. We are going to be adding new adilas university classes for HTML, ColdFusion, Database stuff, and adilas basics. See other notes for details. • Recording notes from loose pages into my notebook. See notes: • Signing off on icon menu pages from an intern. Pages are for media/content and elements of time. Small tweaks and checking code. Added some java script to help with subs of time. I added a counter for the caption for sub dates and times. |
|
|
AU 2951 |
|
Daily Ideas | 11/14/2014 |
Code Sign-Off Process: 10. Sign-off on code and add small version control per page. Talking with an adilas intern. 11. I would like to work with developers on their machines and sign-off on things locally. 12. Once a page has been signed off locally, the developer will upload pages into the top secret/need sign offs folder. This will keep it out of production until it gets a final gate keeper review. 13. The gate keeper (Brandon for now) will pull down the files that need a sign-off. The gate keeper will then test and make sure that things are good to go to production. 14. Once put in production, new code will be put up online in the released or normal top secret folders. All developers will go to the FTP server to get the latest files that have been released. We had a request to help manage max & minimum inventory levels across companies. That sounds like application flex grid or real in-line extensions. These projects are gaining momentum and heat. New Developers: 15. Meeting with an adilas associate and talking about a company that can help or who would manage the process of bringing people on board and bringing them up to speed. Both reps and consultants as well as developers. We are focusing on the developers right now. 16. Film and record all of the training pieces and put them up on adilas university. 17. Have a test and/or certification level to help with skill sign offs. Maybe use flex grid tie-ins or elements of time to accomplish this. 18. Do things once and then use over and over again. 19. Make the first video as a 5 minute overview. Keep it brief. 20. Anybody new needs to go through the process. 21. Use the code segment – can act as an evaluation process of sorts. Basically, do we want to spend the money on their education? In other words, a trial period of sorts. 22. Plan some 2 hour session in December & November – monthly & weekly training sessions. 23. -Generally schedule out time frames for each subject. o Topic: • Bullet points • Requirements • Options • Visual aids • Time frame 24. Double the bang for the buck… show code sample and concepts and how they relate to adilas. Put the concepts into action at the source. 25. Use all of the different teaching methods and learning styles. Audio, visual, actual, hands on, etc. 26. There will be quite a lot of time in both pre & post production stuff. 27. API – Play at the wall! This is where we could support the largest number of code developers. 28. Do a small 1-2 hour seminar for interested developers – Look for people who are interested. Pull from a bigger pool! 29. Start the first seminar with hand-picked folks who want to play. 30. Use the seminars and meetings as a screening process for qualified people. Help them get the skills to pay the bills. Share, share, share! 31. Try storming – Be willing to circle back around. 32. It is ok to break models. We do it all the time. BE sensitive about his but don’t fear. Take more counsel from your faith, hopes, and dreams than from your fears. Let faith win! 33. When teaching a code class, it might be cool to have a way for class participants to submit and run code. Maybe use elements of time and sub comments. Maybe each person has their own main element and then uses the sub comments for assignments. |
|
|
AU 3730 |
|
Brainstorming - On-Boarding Interns & Code Sign-Off Process | 11/14/2014 |
- 30 hrs - $300 o 15 CF Code - $20/hr = $300 o 10 adilas - $20 hr = $200 o 5 actual project – hands on o $800 - New 10-20 new clients - $2,000 per month - New custom jobs - $5,000-$10,000 per month - Company who manages (Facilitator) – on boards process & bring them up to speed - Film and record all of the pieces adilas university - Have a test and cert base to accomplish the sign-offs - Do it once – use many - First video is the overview – 5 mins (brief) - Anybody new needs to go through the process - Code evaluation process o Do we want to speed the money on their education - Plan 2 hour sessions in December - Generally schedule out timeframes for each subject – (Liks – 10 min) o Bullet points that need to be addressed and/or covered o Options o Visual aids - Double the process by showing these concepts in action inside of adilas - Auto, visual, hands on or actual - There will be some pre & post production stuff - API – Play at the Wall! - Small 1 hour seminar for developers – look for people who are interested (pool of people) - Start the end of November - Use the meeting as a screening process for qualified people - Try storming - Okay with breaking models - David.forbis@adilas.biz – Project Management - What if we had a way for class participants to submit code for running and/or checking? Maybe use elements of time & sub comments Talking with an intern about flow & code sign-off process: (Please see sketches on scan in photo gallery) 1. Sign-off locally 2. Upload all to need sign offs 3. Pull down from need sign offs 4. Brandon is the gatekeeper (right now) 5. Once actually released they will go into production & updated on the MDI server 6. Max & min on inventories |
|
|
AU 2953 |
|
Daily Ideas | 11/21/2014 |
-A shopping bag or grocery bag is a great one-to-many analogy. I was trying to bring things into my house and had a huge full arm load. I was using both hands, arms, and chin. Then I thought, man, if I just had a grocery bag or two this would be easy. The more I thought about it… the more I think it could be a good one-to-many relationship example. All you need is a small container to hold the pieces… -See sketches in photo gallery: Person trying to hold all of the pieces – too many to manage. VS Good use of a one-to-many relationship: Person using a container (shopping bag) to hold smaller details or items. -We had another request to show grouped data per day. They wanted the daily, weekly, and monthly totals. Basically, they wanted the financial history homepage report that will show data specific totals based on categories. See notes from 9/12/13 in adilas university for info on the financial history report. Commission Structure for 3rd Party Solutions: • To adilas: a. 20% • To 3rd Party: a. 80% • What: a. External solution. They bill the client. Then they pay us back 20%. • To adilas: a. 30% • To 3rd Party: a. 70% • What: a. External solution. We handle all the billing. We pay the 70% back to them. • To adilas: a. 40% • To 3rd Party: a. 60% • What: a. Internal solution. We host the files, pages, and apps. We handle all the billing. We then pay the 60% back to the vendors. Usually, this is an adilas developer that creates an internal 3rd party solution. • To adilas: a. 50% • To 3rd Party: a. 50% • What: a. Internal solution. We host the files, pages, and apps. We handle all the billing. The developers create, makes and does the maintenance on the project. We handle all the billing and pay back the 50% commission back to the developers. This is an option for adilas developers who basically make the app or feature happen and then maintain it. The original work and effort are on the developer. The maintenance also falls on the developer. They also get a perfect 50/50 split of the revenue. |
|
|
AU 2944 |
|
Daily Tasks | 11/24/2014 |
• Working on in-line discounts and calculating the total saving per shopping cart. • In-line discounts. • Recording notes from loose pages and post-it notes. • Emails and drawing a graphic to show the web client/server relationship between clients, web servers, Cold Fusion servers, internal API sockets, external API parts, and database servers. • On a conference call with a financial services going over a kiosk, payment, bill recycler type interface. An adilas associate is the project manager and I was being the technical contact. There were two other gentlemen on the call and we talked ship and shared ideas. I told them that I would send them some brainstorming documents from 9/3/14 to 9/6/14. • Working with an intern on a new developer Power Point presentation to help train adilas developers in adilas. Also talked on the phone with our new adilas project manager about the meeting and call earlier today. He is doing a great job. • Drawing a graphic to help with Cold Fusion training. Adding the new graphic to adilas university. I then started writing some information and explanations on what the graphic contains. Lots of back and forth editing. • More writing about the client/server model and the Cold Fusion structures and scopes graphic. See time entries in both the main adilas.biz site (#908) or on the adilas university site (#2927) for details. • On the phone with the new developer from Salida, CO going over code structure, flow, and how things work. We used the new graphics that we created today to help illustrate the processes and structure. That was kind of fun. • Recording bills for adilas. Uploading scans and checking account balances. |
|
|
AU 2956 |
|
Daily Ideas | 11/27/2014 |
-Today is Thanksgiving. Lost to be grateful for… Count your blessings not your problems. Build on what you have. Work as if for years. There will still be time. Keep moving forward. -We may end up needing to get our own GPS server to catch and hold GPS data. We could then use API’s and web services to connect and pull real time reports and data. Another option is to use a GPS server as a service (pay for somebody else to host the data). Either way, we just need access to the data or virtual air time. See Wikipedia – GPS & GPS Server. -Steve thinks that we need a help forum or some sort of way to answer multiple questions at once. Answer once, use many. Share our library of questions and answers. Steve has kept tons of emails for years. He would like to circle back around and use some of that content. Great idea! We’ve spent hours and hours and more hours writing emails and answers on how things work or step-by-step instructions on different subjects. We need to capitalize on all that effort. That would be awesome! Maybe have my sister help make that archive as part of adilas university. That would be really cool! |
|
|
AU 2958 |
|
Daily Tasks | 12/1/2014 |
• Emails and recording notes. • Reviewing GoToMeeting Training sessions from last year. Lots of adilas university clips as well as Cold Fusion Training stuff. I had forgotten about that as an asset. Lots of good stuff there, it is just not organized at this point. • Reviewing video clips and trying to plan how to use them. • Copying videos and files from different computers. • Working with an intern on what to do with all of our video footage. Lots of data, not very organized yet. • Working with an intern on customer data upload process. • On the phone with my sister talking about client needs for a client and their upcoming eCommerce site. They are looking to play ball pretty quick. • Working with an intern showing him some of the new video clips and training sessions. • Working on a letter and memo for the adilas developers training meeting this coming Thursday. • Went in to town to get a number of 32 GB USB flash drives to put video clips on. These will be for new adilas developers to help them get started with older videos. Got 10 $40 flash drives for $10/per. Christmas sale! 30 miles. • Writing individual emails to the adilas developers inviting them to a special meeting this Thursday. Trying to get everybody together to set up some expectations and processes. Good stuff! |
|
|
AU 2961 |
|
Daily Tasks | 12/4/2014 |
• Working with an intern on logic for his first customer upload. Over its course, we spent about 10 hours on what needs to happen and why. Also had some light tech support calls. • On the phone with both Steve and an intern going over the entire process of doing a customer data upload. We did a GoToMeeting session. We drew out the process. That included a funnel process from MS Excel, temp database, new table, ColdFusion page, queries, loops, variables, conditional logic and other tweaks to the variables. Then we check the live database and then point the new and clean variables back into tables, rows, and relationships in the live database. We even FTPed (file transfer protocol) the tables up, logged into the remote server, and ran the live update. Great session. After that Steve and I talked about new shopping cart access points and black boxes for custom code. We also talked about integrating with different pieces of software on a user’s machine and then allowing full API connections from the software applications installed on user machines. • Uploaded the new graphic for the shopping cart black box diagram. I also tweaked an adilas associates’ adilas university logo and put it up online. That was fun to get that graphic up and online. • Working with my brother on arrays and structures. • Working on a meeting agenda and printouts for the developer’s meeting. • Went in to Bridgerland to meet with adilas developers and adilas interns. This was our first meeting of this level and scope. We ended up with 15 people at the meeting. There were only two that I haven’t met before. They were friends of one of the current interns. We had a great group of people at the meeting. We did a two hour session and covered lots of ground. Super awesome meeting and I was humbled by the participation and comments from the group. It was awesome and humbling at the same time. See elements of time #2930 in adilas university for the video web link. We gave out flyers, paperwork, and handed out all of the new jump drives that I had. Great session and good energy. See this URL for the GoToMeeting screen capture: http://www.adilascontent.biz/videos/adilas_developers_meeting_12_4_14.wmv. 30 miles. |
|
|
AU 2972 |
|
Daily Tasks | 12/17/2014 |
• Working on logic for the in-line discounts on the edit cart line item page. Lots of testing. • Emails and working with an intern on teaching concepts. • Working with an intern on some data migration clean-up. He pushed up 56,000+ records yesterday and we ran some light clean-up on the records. • I also got an email from a developer out of Utah. He is working on an app that uses ASP.net and Java Script to connect to the adilas API sockets. He sent me his first round baby demo app to play with. Good stuff. • Reviewing notes and content on adilas university. • Working on the advanced edit cart line item page for in-line discounts. • Working on the Java Script for the advanced edit cart line items page. Paying bills and working with an intern on icon menus. • A developer came over for a meeting. We chatted and did a little bit of catch-up. We talked business, projects, and even some personal direction. We did a sign-off session on new 1099 and W-2 forms for 2014. We then updated some code files and started into the kiosk payment project. I took him on a small demo and tour of what we did for the C4Ever Systems guys back in September of this year. We drew some notes and flow charts and talked some concepts. We even talked about project management and the need for documentation. That is very important and takes time, but it also translates into dollars and cents later on. Great meeting! • A new contact came over for an interview. He will be one of five new interns that will be starting in January of 2015. We had a great interview. We started out just chatting and getting to know each other. We then moved on and did a light HTML and web knowledge quiz. He did so well on the HTML quiz that we moved on to a small SQL and database quiz. The whole thing was done on paper and lots of drawings back and forth. Good stuff and he is excited to get up and get going. I’m excited to see what some of these new guys bring to the table. Yee haw! |
|
|
AU 3573 |
|
Daily Tasks | 1/20/2015 |
• On the phone with Steve working on the adilas world files. We did a GoToMeeting session and I was doing some code. We followed a couple of paths and decided that we would just hard code the headers and footers instead of including the prebuild ones. • Went in to Bridgerland to meet with my brother. He had some graphic sketches that he wanted to show me. We also talked about a branching interactive graphic to show cause and effects for sales, purchase orders, and inventory tracking. 30 miles. • Working with the interns on loops and more logic. Great little session. We covered index loops, list loops, array loops, and structure or collection loops. After that we did a whiteboard session on round 2 of elements of time. We used two whole white boards and spent over an hour going over scope and depth of the project. I think it went over well. See elements of time #2933 in adilas university for photos of the whiteboards. • Emails and tech support stuff. |
|
|
AU 3578 |
|
Daily Tasks | 1/26/2015 |
• Working on bulk voids for a client and doing some clean-up for another client. Sent emails with info and updates. • Working on ICC’s (internal cost corrections). Gathering ideas and doing research inside of adilas and adilas university. Looking over past notebooks and scans. • Emails. Helping an intern out with some custom logic on a data import. Reviewing some of Steve’s code and helping my sister with some tech support stuff. • Went into Bridgerland to work with the interns. We did a couple hours of review. Each of the guys took turns being in front of the class reviewing code and going over things. After the review, we started planning out our joint min project for elements of time and sub GPS and RFID tag tracking. We made a flow chart and started to define database tables and such. See elements of time #2934 inside of adilas university for photos of the white board planning sessions. 30 miles. |
|
|
AU 3586 |
|
Daily Ideas | 1/26/2015 | -Move and transfer some of the coding ideas and things to do over from the main adilas site over to adilas university site. Help create a single source library to help with research. These additions may go good in the adilas university site under the section called categories inside of elements of time. Basically, grouped research in a single location or library. | |
|
AU 3588 |
|
Daily Tasks | 2/3/2015 |
• Working on logic for tax calculations for with tax included and in-line discounts. Flipped the process around and put the tax calculation first and then the in-line discounts. Emails and small verbal quotes. • Went in to Bridgerland to start a session with the interns. Setup some requirements to help guide them on their mini project. See elements of time id #3345 inside of adilas university for a pdf version of the requirements. Working with different interns on their projects. Lots of white board time and helping to lead them down the learning path. 30 miles. • Working with interns on projects. One intern was working on a tree project, another was working on the eCommerce API stuff, another was working on subs of time and GPS and RFID tag subs, another was working on a weather and fishing app, another was working on data imports, another was starting on a gift card and loyalty points system, and another showed me some of his graphics that he has been working on. Crazy but exciting times. Lots of learning going on and happening today. • Emails and recording notes from loose pages. • Recording notes in my notebook. It is a lot of work to keep caught up. However, I feel so much better when I am caught up and recording things as they happen. In the last two days, I’ve going through a stack of about 20 post-it notes and recorded notes back into my notebook. Normally I try to record directly into my notebook but if I get behind, I record things on loose pages or on post-it notes. I then have to go back through the notes and write things a second time to get them into the real notebook. I know that it takes more time but sometimes the process of writing things over and over again makes it stick better in my head. It is probably a blessing in disguise. Anyway, I’m currently caught up and ready to go! Yee haw! |
|
|
AU 3601 |
|
Daily Ideas | 2/5/2015 |
Back on 1/20/15 we were brainstorming on a project called round 2 of elements of time. See entries from that date for details. Anyway, when I was driving home, I started thinking about how we needed elements of time to advance the ball for our balance sheet and financial records. When I got home, I scribbled some small ideas on a post-it note and stuck it on my scanner. I’ve been meaning to record those pieces but have been slammed. Here they are: - Use elements of time behind the scenes to record daily records per categories. No other math other than the daily sums is needed. We will then pull reports based on those daily sums. Watchers and feeders. - The different categories will be updated and maintained as they happen in real time. This includes normal actions such as adds, edits, deletes, voids, etc. This is possible as most pieces are manipulated on a one by one basis. - There are tons of entries in the adilas university site on watchers. Search for the key word watchers. Some of the entries go back to 2008, 2009, and 2010. Things started getting hot in 2010. Lots of planning and mapping sessions were being done. That whole process was the prep and foundation for elements of time – round 1. We just ran out of time to get it all done. See specifically the entries for the month of October 2010. Interactive map, watchers, feeders, roll call, mappings, etc. - On the daily records per categories (watchers and feeders), these would be accounting level subs of time. They could be done daily per location as needed. The subs would only be added as something happens. Keep it small and tight. Simple sums would be sufficient. Relate the subs back to pieces of the financials. Use the P&L (profit and loss or income statement) and the balance sheet as the categories to keep track of. For example: part categories, revenue, cost of goods sold, expense types, deposit types, balance sheet pieces, taxes, receivables, payables, etc. - The goal is daily sums per location per category. The word category is kind of broad but record key pieces per day. These feeders could then be used to support and/or feed other reports including the P&L (profit and loss) and balance sheet. - I really need to get these records (my notebook) out to the public. There is a lot of good stuff here that could benefit the whole human race. The ideas, knowledge, and planning are free. Making it happen… that takes resources. See notes back on 1/24/15 about new custom black boxes for custom code. Today while doing a whiteboard session, we may end up adding other options for custom headers and custom footers. These would be more global type pieces but available if needed. The word global means more system wide vs. per page like most of the other custom code. Standard page inside of adilas – black box custom code options: - Top – full takeover or custom logic - CSS – Global or system wide - Top custom header – Global or system wide - Top mini – under the header - Main body black box - Bottom mini – above the footer - Bottom custom footer – global or system wide Be able to switch out any piece of a page as if it was a Lego building system. The page name would remain the same but the display and logic could be customized with no problems. -To take the black box concept even further… What if each page had options to use a point and click interface to show/hide criteria, custom naming conventions, change display order, and even add or subtract links, navigation, buttons, graphics, and even database fields. The extra database fields might need to be tied to the future project called real in-line extensions. See notes from 10/2/14 through 10/9/14. -I wanted to record a miracle… We’ve been working with new interns for over a month now. They are growing and developing some great skills. We are really excited about that. The scary side to that is how much it costs to get them to a level where they can play the game. Anyway, I was telling my dad and he asked me if I could get a loan or something to help bump these guys over the hump into a producing level. I told him that I didn’t think so… He immediately said – “Let me talk to mom and see if we could get you something.” You have to realize that my parents aren’t rich or well to do. They scrape and pinch like most of us. Anyway, I end up heading home, ran some errands, and finally get home. Later I get a call from my dad and he says – “Come by tomorrow and mom will give you some money.” They are planning on loaning me $5,000 to help bump the interns into a producing level. That will really help and is literally a miracle. I feel very blessed. I told my mom and dad… “I want to be just like you when I grew up.” I love how quick they give, serve, help, and jump in. They are and have been a huge blessing in my life. I’m very grateful! |
|
|
AU 3603 |
|
Daily Ideas | 2/14/2015 |
-New graphic idea for helping developer understand the process of working with data – almost like a construction worker. (Please see scans in photo gallery) Inputs: Make a list of known inputs. What do you get or start with? Tools: Make a list of tools that you use to get the job or project done. Outputs: What did you make or get as an output? Imagine a funnel to slowly take a bigger raw input and get it ready for an output. -Elaborating on the new graphic idea to help developers with the concepts of working with data… (Please see scans in the photo gallery) Mini Version: Inputs: Start with? Tools: Outputs: Goal or end with? Funnel and reverse funnel effect – mix and blend as needed -Bigger Version: (Please see scans in photo gallery – lots of ideas) Input Types: - JSON – var1: value - XML – - Text – “something as text” - Mixed Data - Objects or structures - URL Data - FORM Data - Query - Array - Variable - List - Other/Custom - As a note… data could be any of the inputs – all kinds of stuff. Outputs: - Graphics - Tables - Reports - FORMs - Links - Navigation - Pages - Data - Other/Custom - As a note… data could be any of the inputs – all kinds of stuff. Tools: - Database - Spreadsheet - Text/Word Processing - Libraries - Traffic Control - Functions - Paper & pencil - Mind & head - Functions - API sockets - Parameters (windows & doors) - Conditional logic (if, else if, else) - Loops & steps - Graphics - Page Redirects & Reroutes - Dumps - Includes - Web - Apps - Software - Hardware - Data – see inputs & outputs - Includes - Validation - Server side code - Client side code - Multi-media - Custom tags - Other/Custom Tools - Settings - Permissions - 3D – Time, Resources, Space Start simple and work up from there -I’m running out of room… I’ll have to put this on its own page – these are just ideas. -The goal is to mix and blend as needed! -I’d love to add graphics or icons to all of these inputs, outputs, and tools. -See adilas university and search for “foundation” to get some good results. -As a small note… You start with known values that are simple… As you mix and blend and as things get more complicated… Things always seem to trend to “other” or “custom”. The word custom usually requires things like settings and permissions. Settings and permissions lead into our 3D World Building Model of Time, Resources, and Space. (3D World Building Concepts: X = Time, Y = Resources, & Z = Space) -Everything is inter-connected. -Permissions and settings may need to change over time. Think of how God works with His children… He places them in certain circumstances and gives them talents and trials. As time goes on and as cause and effect actions take place, God is willing to virtually change permissions and settings as needed. Change doesn’t have to be up or down. It could also mean front to back, left to right, diagonal, add or subtract, multiply, divide, etc. Granular or micro controls. God loves His children and helps us learn and grow along the way. I know He loves us! -This is a design idea that was submitted by my brother. My brother sketched this design while listening to part of an adilas intern training class. 3D Calendar Idea by my brother: - Imagine days of the month as 3D cubes or blocks: - (Please see sketches on scans in photo galleries) - Month: o Week 1: o Week 2: o Pretend it went from 1-7: S, M, T, W, Th, F, S, 8-14: S, M, T, W, Th, F, S and so on… Days and months Each day could be broken down into 24 hours. Each hour is a mini block. - Break each day into 24 hour blocks – single day - Take each day and block and expand it into 24 smaller blocks… Hours o This could go 0-11 am, 12-11 pm or 12-23 if on a 24 hour block - Days and hours Each hour could be broken down into 60 minutes. Each minute could be a small block of time. - Example: Monday, May 9th at 10:00am – single hour block of time - Break each hour into 60 minute blocks. Each minute could be broken down into 60 seconds. - Break each minute into 60 second blocks - Single minute - Minutes & seconds - Example: Monday, May 9th at 10:45 am It could go deeper but I think the point is made. Basically, a 3D calendar that could show any level of detail. I showed my model going from months, days, hours, minutes, and seconds. The model could also go up if needed to things like: months, quarters, years, decades, centuries, millenniums. Whatever you want. Think levels both big and small. |
|
|
AU 3599 |
|
Daily Tasks | 2/16/2015 |
• Emails. • Working on invoices and outputting in-line discounts and total savings. Also added a new corp-wide setting to allow invoice line item photos to show up by default. Basically making the photo invoice a valid default invoice type. Posted some files online. • Recording notes from an idea that my brother gave me on a 3D calendar model. He came over on Saturday 2/14 and showed me a 3D design for showing the calendar. He broke it into days, weeks, months. He also took it down from days into hours, minutes, etc. See notes from 2/14/15. See elements of time #3557 in adilas university for scans on the 3D calendar. • New logo for a client out of Texas. • Going through emails and responding to requests. I’m seeing a number of new requests that are based on the sub permission level. This deals with a permission but the permission also needs one or more settings. It is interesting to see how both permissions and settings need to play together (compound concepts) to create the foundation of what we do inside of adilas. • On the phone with Steve for half an hour talking about custom settings. He was also asking about flow for his swipe driver’s license project. Basically, swipe the license and then have the system parse through the magnetic data and store the values. We talked about using temporary tables, the session scope (cloud or memory), and step-by-step pass through values. • Wrote a large email to an adilas rep/consultant about ideas for mixing sub permissions and sub settings. It is crazy to see how everything is headed to sub control levels. The email also talked about real in-line extensions. The email was a light proposal of sorts. It is fun to see things starting to come together. |
|
|
AU 3622 |
|
Daily Ideas | 3/3/2015 |
-Steve would like to add more default choices to the chooser page. He would like new choices for different sections. Currently we only allow choices for main homepages. Steve would like to see future choices for shopping carts, interfaces, and sub homepages, etc. This also includes choices for skins, templates, themes, and other options. Tons of choices. -As part of a brainstorming session we talked about ways to use adilas black boxes for eCommerce. The guys also wanted to change the file structure and use sub domains and alternate URL paths. More talk about skins and full page redesigns. One of the main topics was paths and structure. Lots of talk about web hosting options. -We are seeing that the future may be in web hosting. People need a place to park their data, their files, their images, etc. People want access to their data and also want to be able to customize things easily. The key is easily… : ) -Plan and work as if web hosting and data storage will be in the future plans. CMS – Content Management Systems. -Subs and subpage settings are going to be coming soon. It is crazy to see how almost everything is splitting and breaking down into subs and smaller pieces. -We are also seeing more needs to be able to sync up databases between live and local platforms. We have developers who need live data. We have multiple servers that need a master copy of different tables such as help files, permissions, web/API socket documentation, tax and withholding tables, etc. Data interchange – based on permissions and settings – will be needed soon. Interesting. -With the data interchange … we may want to provide tools to allow a two party agreements to transfer and migrate data. Provide the tools and let the different practices create their own relationships. See adilas university back in 2008 dealing with two party agreements. Both requests, and approvals of data interchange. -On black boxes… what about using pages that include another page include. Basically stacking includes as needed. Includes are ways of breaking up bigger pages into smaller re-useable parts and pieces. |
|
|
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 1005 |
|
Adilas University - Videos, Training, Tutorials, Shortcuts, & User Guide | 3/30/2015 |
Brandon and Shannon are currently working on this. We have a number of videos out there, hundreds of hours of training that raw. Every week this is being touched on for a couple of hours. |
|
|
AU 3849 |
|
Daily Ideas | 5/5/2015 |
-On the affiliate programs and promotion codes, allow them to be tracked to the person level if needed. That is customers, vendors, and employee/users. Also allow for campaign tracking options. The important thing is tying a campaign or promotion code to a specific person or entity. It could also be internal or unassigned. -Setup all adilas guys with some access to elements of time in both adilas as well as adilas university. Get everybody assigned and help them use the tools. -Add categories and types to sub dates and times. If applicable, even show items sorted and separated by type and category. This could be all kinds of stuff. Expand and think of different options. -Go through the elements of time section and update a bunch of tables to get things prepped for round 2. This includes things like app-types, main id’s, sub id’s, table names, bigger category options, more settings, and more date and time options. -Add new subs of time – sub checklists, sub budgets, sub locations, sub phases, sub packaging, etc. -Beef up the sub assignments table – Be able to handle any connection to any other application player and/or sub player… Expand! |
|
|
AU 3832 |
|
Daily Tasks | 5/14/2015 |
• Adding new logos and colors for 5 different corporations. Most of the new ones are on the data 3 server. • Went into Logan to work at the office. Did some code sign-off on icon menus. • Worked with a developer on using cookies to help with his software bridge. • Meeting with a consultant to go over sales and features. • Meeting with my brother and seeing his Flash interface (adilas university stuff). Good day. 30 miles. • Phone calls, tech support, and messages. Called clients in Colorado. • Called a consultant about gross sales commissions for payroll. Emails and more tech support. • A contact came over to my house for an interview. We met and chatted about tech stuff as well as about training options. He is a very talented teacher and instructor. |
|
|
AU 3844 |
|
Daily Tasks | 5/28/2015 |
• On the phone with Steve pitching the idea of setting up an adilas training center and/or a hub or service shop for different adilas services. These could be things such as: customer service, training, setup, consulting, sales, web design, eCommerce, graphics, custom code, project management, data entry, migration and data imports, etc. • Tons of possible services and different options. We also talked about creating industry specific niches for training, sales, consulting, design, setup, compliance, etc. The other subject of our conversation was franchises and franchising out any part of our model. Awesome phone call and lots of ideas. • Went into Logan to work with my guys. • A developer set me up with a headset and a Google voice account. • I was on a GoToMeeting session with a developer going over shipping and eCommerce stuff. • I worked with my brother on some of his graphics, flyers, and mock-ups. • The project manager and I had a good conference call with some guys from a cash management and compliance company about GPS, RFID tag tracking, cash management, kiosks, and loyalty cards. Good stuff! • I worked with a developer some more on other eCommerce stuff and questions that he had. • Another developer and I worked on splitting invoices. • Four of us got on a GoToMeeting session with Steve to show him icons, graphics, flyers, app mock-ups, and adilas university training stuff done by my brother. Fun demo. • My brother and I were kind a tag teaming and pitching a number of ideas and concepts. Fun phone call and GoToMeeting session. 30 miles. • Recording notes for the day. Lots of good stuff going on. • Signing off on code for splitting up invoices and invoice payments. Testing and even migrating some local database records. |
|
|
AU 3858 |
|
Daily Ideas | 5/29/2015 |
-Add my saved favorites (as a link) to the interactive map (part of the side bar). Also add links to the media/content home, all advanced searches and exports, retail quick cart, YouTube videos, adilas world, adilas university, adilas hub, adilas GPS core layout, etc. -On the GPS core layout, put the multi interface chooser as an option from the core or center. (Link to the multi interface chooser from the core of the GPS core) |
|
|
AU 3901 |
|
Daily Tasks | 7/4/2015 |
• Recording bills and scanning invoices. • Adding a new wholesale tax category to the list of options. • Started working on some new personal settings for my cart favorites. • Reviewing some past entries – lots of neat memories as I searched for “personal settings” in the adilas university (developer’s notebook) section. I ended up going on a walk and recording some thoughts in my little mini notebook. Good evening and a great 4th of July. |
|
|
|
Adi 1174 |
|
Financial History Report - All Activity As It Plays Out Over Time - 3rd Part of the History Homepage | 7/9/2015 |
This would be the 3rd history report type on the history homepage. The other two reports are the effectual (what shows up for roll call) and the historical (who touched what). This other financial history report would be what shows up on the financials over time. This would virtually allow us to watch a company progress, almost like a movie playing over time. See the adilas university site (developer's notebook) for financial history for more info and notes. |
|
|
AU 3917 |
|
Daily Tasks | 7/25/2015 |
• Working with my brother to wire up two different sites. They are a basic sales page for vehicles, trailers, RV’s, and motorsports. Awesome graphics and very loose flow. The other site was the one my brother did for his practicum and internship back in February and March of this year. It is a training website for adilas university. I got really excited about the graphics and options that it has. We spent quite a bit of time going over the photo gallery which has graphics of 3D world building, the adilas interactive map, core business functions, main system players, etc. Lots of fun. Here is the current URL or link to photo gallery page: http://www.adilasuniversity.biz/training/photo_gallery.html • Recording notes about my session with my brother and other light brainstorming on how to get the word out. • Signing off on GPS and RFID tag tracking code done by an intern. • Working on the advanced sub time search and search results page. |
|
|
|
Shop 3837 |
|
Virtual Post-It Note | 11/5/2015 |
5:00-5:30
8:15-9:15
10:00-10:30
10:30-11:00
11:00-2:00
3:00-8:00
New Community Funded Projects
|
|
|
|
Shop 2731 |
|
General | 12/18/2015 |
12/18/15 -6:15-9:15 See E of T #324 in the shop-Alan-Html me cart favorites button. -10:00-12:30 See E of T #304 in the shop-Daniel-horizontal time slot report. -1:00-1:30 Russel and I had a small meeting while eating lunch. We basically talked about direction and vision. We both like to dream big...It's the getting it done that is the hard part. -1:30-3:00 Cleaning up the shop. Sweeping floors and meeting with Russell on some up coming projects such as the Adilas university site, the Adilas market site, and the Adilas world site. All of these projects and up and coming in the near future. -3:00-4:15-Catching up on notes and notebook stuff. Cleaned out a number of time entries for the last couple of days. Basically, I go to the favorites page, click on Brandon Time (a time template name) and clean up the older entries. I record notes about happenings and progress that is made. Recording things is a big part of my job. -5:00-5:45-Light clean-up on corp-wide settings for the shop. I also updated an invoice from the Beaver Mountain to note the trade details for Beaver Mountain. -5:45-6:30-Recording notes from loose pages and post-it notes into my main notebook. |
|
|
|
Shop 478 |
|
sales page | 1/21/2016 | Russell and I worked on the pick a color CSS settings. Calvin was using my machine to update some SQL software, so I used Russell's computer to do the work this morning. Russell also showed me a demo of what he is thinking about for the adilas university site. Good stuff. | |
|
|
Shop 681 |
|
Possible cross corp mappings | 2/10/2016 |
Possible cross corp mappings between the adilas shop and the adilas university developer's notebook app. That would be cool to record in one place and then automatically map over to another site. Just yesterday, Todd Williams came over and we were talking about some new business options. All of the new market transactions would also need some of the cross corp mappings. Cool stuff. I see a huge need for different applications and different software packages to be able to crisscross information and data. That is part of where we are headed. Plan for it and make it as easy as possible. |
|
|
|
Shop 644 |
|
Adilas World | 3/8/2016 | Alan and I worked on the "any" scheduler app and sub functions of time. We ended up going into the adilas university site and looking up some of the early brainstorming pieces for elements of time. We talked types of time, functions of time, 3D world building, data assembly line stuff, and much more. I was really enjoying the dialog and conversation. I hope that Alan was enjoying it as much. This has been part of the dream all along. Fun session. | |
|
|
Shop 1094 |
|
Brainstorming Meeting with Steve | 3/26/2016 |
On a GoToMeeting session with Steve to go over a proposed budget and a plan for the upcoming couple of months. We spent a lot of time talking about individuals and how best to get them going and connected with the rest of the team. See time id # 1274 in the main adilas site for more info. Both the budget and the brainstorming doc were uploaded to that element of time. We covered: - Team building - forming, storming, norming, and performing - adilas university - adilas world, adilas market, adilas community - developer's notebook - world building - own skill levels & abilities - persons and their skill levels - work ethic, commitment level, investment level, time, availability, communication skills, coding and general skill levels, social, special attributes, and timelines. - Maintenance - Pace - Code clean-up, sign-off - Elements of time - Servers, roll-overs, and availability - World building - splitting up databases - Training and support team |
|
|
|
Shop 848 |
|
Shop meeting about project management | 4/5/2016 |
Team meeting with Dave, Bryan, Russell, Shawn, Chris Johnnie, and my self. We started out with problems: - incoming sources of project requests - my email, Steve's email, Dave's email, Shannon's email, Bryan's email, phone calls, from reps, etc. - time to get back with clients - communication breakdowns - not done/broken - who - $ monies/commissions/ownership - changing ground - we are too nice - knowledge gap - tech/skills The gap model, cart and horse, sales and custom jobs, data assembly line, time (x axis), monies/resources (y axis), space/organization (z axis), shop/hub model, project costing Team Building: - Forming - Storming - Norming - Performing Possible Solutions: - Adilas World - Adilas Market - Adilas University - Developer's Notebook - Companion Software Packages - People - Process or processes - procedures - tools - Quoting Process - Cover ourselves - Education |
|
|
|
Shop 1480 |
|
Recording notes | 6/11/2016 |
Recording notes from yesterday about a GoToMeeting session with Steve and talking about parts/items and conversions. We have been around the pond a number of times and I think we are finally starting to understand it a little bit better. See notes from 6/10/16 in the adilas shop. Also as a small side note, I went to the main adilas site and searched for conversions and got a couple entries. I then went to the adilas university site and did a similar search. I found tons of entries (40+) on the subject. Good resource. |
|
|
|
Shop 3466 |
|
Virtual Post-It Note | 6/14/2016 |
-Error or bug with query -With Jane, maybe try a sub query to speed things up -Add the time id number to the add_edit_time_sub.cfm page -Steves tax return -"managing expectations" for adilas, consultants, and other 3rd parties -Upload the files we have -Create a new welcome letter and setup the expectations -Intro letter to all clients( already exists ) -Setup a culture of training and communication -Rules and how to play the - genral rules -Set aside time for the user guide and adilas university |
|
|
|
Shop 1515 |
|
Quote session with Shannon | 6/16/2016 |
On a GoToMeeting session with Shannon. We did a couple of quotes and went over some tech support questions. We also talked about some of the next rounds for the balance sheet and the accounting features inside of adilas. Good stuff. As a note, the balance sheet and other financial sections inside of adilas have had numerous sessions and rounds. There are a number of other rounds that have been in the planning stages clear back from 2010. Search the adilas university site for balance sheet, mapping, watchers, feeders, standalone declarations, or interactive map. Lots of notes on the subject. Things really started to heat up in October of 2010 for the balance sheet and full system mapping. See elements of time # 2166 and 2167 in the adilas university site to get a flavor. Expand the search and research as needed. |
|
|
|
Shop 1520 |
|
Push for more custom data storage | 6/18/2016 |
As Steve and I were talking, we decided that we need a way to hold and store more custom data. It made me think of some other brainstorming that we did back in October of 2014 on real in-line extensions. We could also build out the flex grid a little bit more. Basically, we need custom data storage options that give us toggle on/off options with granular data control. This could be JSON (huge or flexible objects) or real live database tables and fields that could be linked up and stored on a per corporation, per database table, basis. See element of time # 2865, 2861, 2868, & 2870 in the adilas university site. There are more as well. Search for "in-line extensions" in the adilas university site to find more results. |
|
|
|
Shop 1533 |
|
Meeting with Calvin | 6/20/2016 | On a zoom meeting with Calvin going over the new changes and database changes that are needed for sub inventory. Calvin had a small proposal written up. We went through things and made a couple of changes but mostly talked about direction and vision. I had him read time id # 2865 in the adilas university site to get an idea about what we wanted to do with real in-line extensions and custom data storage. I was so grateful that I could send Calvin to that time id and let him go over the info at his own speed and pace. Good stuff. | |
|
|
Shop 1566 |
|
Russell time | 7/11/2016 |
Got to the shop about 12:30 pm. We didn't have internet for awhile. I worked on some code for sub inventory. I met with Russell from about 1:30 pm to about 5:15 pm. Most of what we were talking about was budgets, vision, and people. Who can do what and where would we like to put people? Lots of discussion about the shop, direction, and use of time, personnel, and other resources. Russell and I went over some pros and cons for keeping the Adilas Shop (renting some office space) and/or working from home and saving time and money. Tons of good dialog here. We also had a full sheet of paper with things written on it and somewhat organized into sections (pros for home, cons for home, pros for the shop, cons for the shop). Good conversations. We may need to look deeper into this and explore some of the other options. Here are some other small notes from the day: - Slow and steady - let things drop off - Maybe stop doing custom stuff right now (this is from me) - We are somewhat in a catch 22 type scenario - I mentioned to Russell that I feel kinda trapped - We talked about a bunch of different things - Russell also feels kinda trapped in some ways. - Russell needs to earn some money - It get heavy carrying a dream by yourself - We are way under full market value - costs for the system - this may be why we have a problem - the supply and demand are not equalized. - We may still need a hybrid shop that does both hourly, bid, quote, and per job payment structures. - Russell has some dreams of his own and really wants to play with what we have - make it better and better - Things like adilas ecommerce packages, adilas world, adilas market, adilas university, adilas project manager, and even making an adilas app. |
|
|
|
Shop 1040 |
|
Adilas time | 8/3/2016 |
Day 3 of the sub inventory stuff. Tons of work on brainstorming and setting goals. See the media/content on time id # 1694. Look for entries made on 8/3/16. Use this link to go to the media/content search results. Some of the ideas: - Take sub inventory clear out to the task management and project management level. - Three biggies - 1. Powerful, 2. Easy, 3. Looks Nice -- if yes, we could sell this to almost anyone. - Education and tons of options there. - Take the adilas university model and extend that type of functionality to our clients as an additional service. - Permissions and certifications - Huge session on S.M.A.R.T. Goals lead by Russell. Nick took notes (see media/content on time id # 1694). Lots of good information there. |
|
|
|
Shop 3478 |
|
Virtual Post-It Note | 8/4/2016 |
-8:45-9:00 Emails and general stuff -9:00-12:15 Day 4 on sub inventory. 1/2 hour brainstorming and the rest of the time following things around. Tracking down changes, recording things,and checking for bugs. Scripted an update script for changes to prevent unit of measure. Working with Nick ,Alan, and Russell on the changes. Working with Alan on known code on bit bucket branches, expand. -1:00-1:45 Emails and general stuff. -1:45-3:45 Zoom session with Russell. Media/Content, Adilas University, Elements of time, research, and direction - expand. -3:45-5:45 Nick - already recorded -5:45-6:00 Recording notes and hours. |
|
|
|
Shop 1802 |
|
Meet w/Shannon | 9/7/2016 |
On a GoToMeeting session with Shannon. We went over the technical side of the new sub inventory changes. I showed Shannon the database changes, and some of the new custom storage options that Calvin created. We talked about some tech support questions, how to nicely say "no", and some other general subjects and topics. We also looked at a quote for new email settings and a request for invoices and quotes and recording invoice histories. They also wanted certain people to be auto CCed (carbon copied) and other email and invoice settings. We talked briefly about doing some more instructor lead training courses. Shannon recommended that we focus on the laser specific videos (smaller focused clips) for adilas university before we try to do more instructor lead training courses. I thought that was a good idea. |
|
|
|
Shop 1922 |
|
Meeting with Chris and Russell, Marketing Ideas | 10/17/2016 |
On a Zoom session with Russell and Chris Johnnie. They were proposing some marketing ideas and opening up some conversations. Here are some of my notes: - They would like to sell the adilas marketplace back to us. This was going to be the adilas world project (back in the day) and they modified it to the adilas market. This is our community networking and marketing site. They were talking between $9,000 to $15,000. They would also consider possible monthly payments. - They pitched a model of they build it and get it ready and then resell it back to us. They stay on the front end of the development cycle. We get to pick and choose where we send them and what we want to buy back. - They would like to do a similar things with the adilas university project. They would like to build it out and get it started and then roll it back over to us. - They would like to keep pushing forward on the other projects that are on their tick list. - If we owned the adilas marketplace, we could negotiate prices and agreements for the market. Steve is the best source for filling up the market. We could give things away, charge, and push people there. This could also allow us to encourage a free market enterprise vs. an endorsed or pre-set market. - Russell had an adilas rep that asked about duplicating the adilas market for her own networking needs. Russell took the idea and would like to see it be a toggle on/off service for adilas clients. Basically a marketing and networking hub of sort for other companies. Mini networking teams. - AFB (adilas for business) would like to work on a long-term relationship with the main adilas company. - The adilas university site and concept needs to be able to duplicate as well. Basically, there are tons of people and companies who need to help educate and teach what they do or sell. A community learning center of sorts. Once again a toggle on/off service that comes with the adilas platform. - A note from Chris Johnnie - Maybe set the prices to help out loyal customers. This could be something that we add in for free and/or some kind of promotion or customer loyalty program or perk. - We may need to raise the commissions rates and system prices to a higher level. This could help make the ball go further. Higher prices and higher commission rates could help to sell the products or services. - Russell and Chris would love to see a 60-80% commission on the first year of service. It would then roll into the normal 20-40% commission as a reoccurring model. Basically, the first year is kinda front loaded. Once the client is stable and on the system, the reoccurring commission is at a smaller rate. Kinda like an investment. - We need and AFB would like to make a ecommerce version of adilas and help to gather the correct setup and sign-up information for a new adilas system. This would be a series of small forms that get and collect the corporation, location, and user information. This is a great lead in to packages and possible upsells. - What if we took the setup fee (say $150 - $250) and pushed a good portion of that to the rep or consultant to help with the setup and training of the client. Or, if the setup fee was increased, we could push a portion to training and education. Helping to get the clients off to the races on the right foot. - There are two huge keys: They are education and maintenance. Those two things may be more important than new features. - Russell gave the corn field analogy. He said, say you have some land but don't have the time to plant it. What if you allowed someone else to plant it and they get 60-80% of the corn the first year. Then the next year, they only get 20% of the corn that gets produced by that field (client payments for a system). Anyways, the goal and idea was to use other people to help plow the field and get things ready. They make enough and we get another field plowed. - We, as adilas, may need to help these guys keep pushing the ball forward and helping them with sales and what not. Keep moving forward and kicking the ball down the road. |
|
|
|
Shop 2047 |
|
Adilas Time | 12/12/2016 |
On a GoToMeeting session with Steve. We talked about direction and where we want to head in the coming months. We also looked over the adilas YouTube media/content player, we setup a cannabis specific site (just the folders and rough structure), and we also talked about training events. Steve would like us to strip off the code from the https://data0.adilas.biz/top_secret/community_funded_projects.cfm page and start being able to collect monies to help with daily training events. We also talked about how my dad volunteered to find us venues for our training classes. Shannon got on the call. We talked about some progress on the videos that she, Dave Forbis, Russell, and Chris Johnnie. Shannon showed us the link to the current google drive videos. https://drive.google.com/drive/folders/0B7QkXlJmb-PSeGRMZF9jbG10ZEE We talked about the difference between in-person vs. webinar (web based training). We are seeing the need for the live sessions (they enjoy the connection with the people). Who, where, when? We need to offer the live events, even if they aren't fully attended. Build out the adilas university video library and the user guide. Make it easy to use and help train the trainers there. One of the unknown values is how do you help someone to stay on and keep going. Shannon mentioned Dave Forbis and Shari O. as up and coming helpers for tech support stuff. Also, Nick and Alan (both developers do have some great teaching skills). I could also be more a consultant and trainer type person. One of the major challenged is how fast things change. We shoot a video or write a help file and then things change. How do you keep up? What a good question... We have some great users... that is good and bad. We also don't have any standard certifications and/or train the trainer type stuff. Some of these people have some major skills but might be liabilities on the other hand. What about the adilas marketplace and the adilas university? We may be going too fast for our own good. What would happen if we totally slowed down and sell what we have? We build and build but are somewhat unable to slow down and tell people what we have to offer. What is the master plan? Do we already have it written down but just need to follow it or do we need to redefine it? We are seeing a change in the way that the system flows... We are getting more API socket calls, we are getting shortcuts, we are seeing more black box stuff, more developer specific code. We need to tell Shannon and Shari O. Who is going to do this new training? We may need to recruit who made it to help do the training. Make that part of the process. Slow things down a bit. The developer's notebook is kinda splitting now as well. We have elements of time in adilas university, adilas, and in the adilas shop section. How are we going to bring all of that together. We have things fracturing and splitting all around us. That is part of the game, we need to allow and accept that. How are we going to deal with that? Sustainable pace - slow and steady wins the race. Maybe keep looking at the process and judge the pace and needs accordingly. People have the potential to let you down. The only person we can truly trust is God. We can then give trust to other people. Make him your main stable anchor and then extend to others. If all else fails, then the sure anchor will still hold fast. I would rather be a trusting person and then be betrayed vs. not being a trusting person from the get go. Quote from Shannon who got it from an apostle (lightly tweaked). We are looking for a loyalty and commitment level of sorts. We do have to be picky. It comes down to a balance and a relationship. Take your time and start to build from there. Relationships take time. That is ok, build it everyday. We make the choices and strengthen and exercise those choices everyday. |
|
|
Shop 2157 |
|
Adilas Time | 1/24/2017 |
On a GoToMeeting session with Steve. More notes on the QR codes. - They want to be able to put their own SKU or item number on the label. - Steve is allowing them to go to an open package and then populate what they are wanting... (mini preset conversions). They have preset multipliers (0.7grams, 1gram, 3.5grams, etc.). They can then enter amounts and watch to see what the total is. - Steve is recording the number of the presets as a sub attribute held on the sub entry itself. He can then check against those numbers to see how much has been sold and what is still available. - Instead of going subs and sub attributes... what if we break more into a traditional model (one-to-many) and start going vertical vs. horizontal. Create a physical grandchild id, record the weight, the cost, the price, how many made, how many sold, special description, etc. Example: Say PO #27, Line # 4, Sub ~15, Conversion `77 (`=back tick or #=pound). We could then use a QR code that was something like: ~15`77 or ~15#77. - Keep going vertical in a one to many relationship. - On pricing tiers and conversion templates... make these their own free roaming tables. We could then attach them to any sub templates. They exist outside (so we don't have to remake them over and over). We could then attach them as needed. - Conversions will need rules, setup options, verbage, and conversions that allow back and forth traffic. Steve was calling conversions - never land - off in the clouds. - We need to track cart status, quote status, and reserved status. See attached for a simple drawing. Here are some notes. The ~15 is the sub. It is in grams. The `77 and `78 are conversions. The m is for made, the s is for sold, the p is for price, the q is quantity (in grams - same as the parent), a visual unit of measure, and possible pricing rules. Along with that, we also talked about tracking the cart status, quote status, and a new one called reserved (who else if asking for it) status. - We really need to get into sub categories before we get into smart cart logic. This will then make it easier for sales, promotions, campaigns, etc. - How will loyalty points and coupons play into this model? Build the whole system out and let the computer help solve the problems. The loyalty points need to be as automatic as the pricing tiers. Think all roads lead to the same virtual outcome. Mix and blend as needed. - The end goal is the employees scan the item and it knows how much, what, where, and when... Lots of one to many relationships. - Along with this... we will eventually need to look into custom labels. Track _x and _y coordinates, custom verbage, auto feeds, dynamic mapping, etc. Logos, backgrounds, symbols, hard coded stuff, conversion stuff, and pricing tiers. - Conversion land... You may be required to label with a QR code so we could track things back down. We may need to nail down conversions before we get into custom labels. - This may bring things into the 3D world building level. _x = time, _y = resources, and _z = stacking and layering. Conversions and labels might be part of the _z level or Z axis. - We are also seeing more need to track things via RFID tag and other digital models. - Doing conversions... we still need to figure out how to show this on an invoice, quote, and/or cart. We still may need to get into more smoke and mirrors (hidden fields, hidden lines, visual quantities vs actual quantities, etc.). We have lots of other brainstorming ideas and notes on this. Check here in the shop, in adilas, and in the adilas university. - On a different note... What about a cash drawer reconciler? We could add a new placeholder inside the cart struct and populate it with some kind of setting or something. Tie it to the login. It will change on a daily basis. We would then need to look at a way of recording this on the deposit or invoice payment level. We may also have some options based off of users, banks, and other things. This gets into sub locations or more Z axis layering and stacking. - tie the deposits to the drawers. This could also include over and short options if off. - small idea on the cart... if you need drawer management, maybe have a watcher on the view cart page that prompts for a who are you and what drawer. We could keep some of this stuff in the session scope so we don't have to prompt each day. Another option might be to have an assignment where a drawer could be assigned to one or more users per day. Kind of a management tool. If yes, it could look it up and record the values based off of the management tool. |
|
|
|
Shop 2253 |
|
Adilas Time | 2/15/2017 |
On a GoToMeeting session with Alan. We went over some of the existing code that interfaces between a kiosk and a bank note recycler (BNR). We drew out some diagrams and talked about the old flow vs. where we want things to go. I then did some light research on in-store credit and loyalty points. Lots of good stuff out in the adilas university area. It may take some time to do the research and gather things up. I can see the need for someone, most likely me, to do that research and bring things together. There were also a number of entries here in the adilas shop that dealt with loyalty points. Lots of options to search. Steve popped in and we started talking about new corp stats and getting some of that information tied in. We talked about adding in some new fields to the master corp table. We talked about multiple salespersons, commission percentages, tying to customers, reoccurring invoices, etc. We then started to talk about dynamic interfaces, quadrants, navigation, accordion stuff, frames, drag and drop stuff, etc. We talked about flash interfaces, skins, themes, etc. We would love to build out some of the graphical carts, interfaces, navigation options, etc. Steve was even talking about how his ColdFusion Builder (development environment) allows for docking, moving, sizing, panels, expanding frames, minimizing, maximizing, show/hide options, etc. Basically, a fully functional and controllable interface, data sub sets, and custom page layouts. We started to revisit loyalty points and special accounts with Eric. We got into the smart cart logic and a virtual pricing engine. We also started talking about how to build it out and how to record where things are coming from (QR codes, barcodes, buttons, certain pages, etc.). We talked about using the custom cart black box stuff... "session.myCart_st.myCustomCodeInfo_st" and then making and assigning custom arrays, lists, and other stored values. Light brainstorming with Steve and Eric on the pricing engine and possible other values and variables for the smart cart logic: new fields we could set on the whole cart level (new internal fields and flags)... part_id special_flag allow_price_recalc item_to_cart_source visual_uofm_id visual_uofm_initials visual_description item_size item_color item_weight locked_original_price locked_original_tax_category_id on the item level... what about special flags and options... allow_discounts exclude_from_discounts allow_price_recalc counts_for_loyalty use_pricing_matrix on the child level... what about special flags and options... allow_discounts exclude_from_discounts allow_price_recalc counts_for_loyalty use_pricing_matrix - Using simple lists with line references. setting up lists, dummy lists, real lists, list appends, list finds, etc. simple mini database stuff. - These lists will be added into a virtual cart black box piece of sorts - Speaking of lists... maybe we build a list of rules and exceptions - what about checkboxes and building dynamic lists. Using checkboxes allows us to show multiple things and still get a list of entered values. We love the simple rules and options. - As a side note, they used a pencil up in space until they could figure out how to get a pen to work (temperature, gravity, etc.). It was that simple. |
|
|
|
Shop 2322 |
|
Alan Time | 2/16/2017 |
On a GoToMeeting session with Alan. We talked about his research on the BNR (cash handling stuff) and what that project will take. We then flipped and started talking about world building stuff and splitting apart the database into corp-specific or world-specific pieces. That is huge and big part of where we are headed. We setup a saved favorite report inside of the adilas university site for world building. That will make it easier to get to. We also setup a saved favorite here in the adilas shop for world building research. |
|
|
|
Shop 2421 |
|
Shawn Time | 3/6/2017 |
On a phone call and then a GoToMeeting session with Shawn. He has been sick the last little while. We talked about 5 main things... 1. Working with Russell (new team stuff) 2. More state withholdings - we need to break up the CFC into at least two pieces. It is getting too big (over the max number of characters for a method). 3. Printing and doing PDF docs - What about looking into Flash for printing? This would be nice but we may have some time here. 4. New trailers docs - Fairly new stuff. 5. Email stuff - We looked us notes, I sent him a photo of our whiteboard session, and we got Shawn setup with FTP access to the adilas university site for email stuff. This is one of our biggest needs right now. |
|
|
|
Shop 2370 |
|
Adilas Time | 3/7/2017 |
On a GoToMeeting with Steve and Eric. We helped Steve with some questions and then talked with Eric. While talking with Eric, they were talking about coding things for a drive-through pharmacy type model with digital signatures, photo captures, video captures, remote file upload stuff, etc. All kinds of digital paperwork stuff. Calvin joined the call just after 10 am. We chatted and talked about mini conversions up until about 12 pm. Calvin and I divided and started doing some light research. I was looking in the adilas university site and inside of adilas for info on conversions. Calvin was doing some looking inside of the adilas shop site. Here are some of our findings: 7/16/09 - adilas university - Time Id: 2377 - Photos – Lots of loose pages and playing with ideas. - Idea - catch the lowest possible increment (or value of 1) - Everything needs a base of 1 - Cost per 1 - Weight/measurement per 1 - Weight/measurement per type - Idea - there may be a difference between quantity and weight. We need to account for both. - Idea - part of this element of time was around the time when we added multi decimal point accuracy (code name – adilas dewy decimal). - Question - How are items sold? Quantity, Weight, Length, Package, Volume, or some other measurement? 7/22/09 - adilas university - Time Id: 1435 - Idea - New corp-wide setting for allowing part number (item) conversions. This was created but has sat dormant for years. 7/28/09 - adilas university - Time Id: 2380 - Photos - Multiple pages that show questions and answers for a single company and their flow. This was from Trinity Fasteners and how they work (buying and selling nuts and bolts). Good flow and ideas. Real life scenarios, needs, and requirements. 12/11/09 - adilas university - Time Id: 1590 - Photos - Notebook entries with some ideas and bullet points. Basically, there will be some dust (+ and -) - play in a ball park level and allow for rounding errors. 2/1/14 - adilas.biz - Time Id: 838 - Photo - whiteboard session with some ideas on it - Idea - Qty in, u of m in, qty out, u of m out, multiplier qty - Idea - add a conversion qty and a conversion u of m - Idea - add a flag that says use or don’t use the conversion - Idea - reverse recipes (preset things, hold all of the details, distribute pieces and products as needed) /// notes from Calvin. Time Id's from the shop... 1221 995 1480 1449 1633 1645 1054 1839 2062 * good stuff 2130 2193 2157 * (good stuff - grid drawing) 2167 * (good stuff - screen shot of conversion/pring: steves_mini_convesion_page_for_qr_codes.jpg) 2258 * (good stuff - more notes) 2260 * (good stuff - spreadsheet) 2403 2405 /// notes from Steve - We have pricing needs, conversion needs, etc. Kitting, recipe/builds, batches, lots, packages, sub inventory, packaging and repackaging (unlimited number of times - make a box, put x number of boxes in a bigger box, take y number of bigger boxes and put into a case or palette). - Every time you break down a child, we need to be loose-y-goosy. The parent and child needs to be the same unit of measure. Then below that, we can have all kinds of different price to quantity relationships. (quantity discounts, pricing matrix, cost of goods sold, etc.) - We need a dynamic tool that could hold user-defined data. - Steve sees the interface as part of the solution - (see his prebuild template for a starting point) - The interface will have parent info, vendor info, child quantity and/or weight, child id, package tag, etc. - Be able to name it (what to call the unit of measurement - example: cones, shake, trim, eighth, quarters, etc.), setup the underlying relationship to the parent and child unit of measure, set a price per, etc. - We also need to track all items being tracked in carts, sold, made, created, available, reserved, etc. - Be able to create a mini conversion template and/or conversion matrix. These would be standalone pieces that could be setup like a template and then used over and over again. Think one-to-many. - Maybe have the parent item be tied to a certain conversion matrix and/or template. We may also see that the templates might need to be tied at the part category level (this may help cascade things out better and more efficiently). - We need a tool that allows for individual business to decide what is what... and how they want to convert things, break things down, sell things, and display things. Very dynamic. - We allow them to build as many main conversion templates as needed. They could copy, duplicate, remove, reuse, etc. /// other notes... - We talked about of the history behind a few of the bigger pieces such as the dewy decimal system, flex grid tie-ins, sub inventory, sub attributes, and current mini conversions. They are all somewhat inter-related and we have built from one thing to the next. - We talked about building in a one-to-many traditional database model and go vertical vs. horizontal. This will help things be smaller and more agile vs. heavier and lots of unused fields and extra columns. Think just in time as a sub or mini conversion of the sub inventory packages, batches, or lots. - We also talked about what is needed to show the mini conversions on a quote and/or invoice line item. We need at least three fields (maybe more). They would be the visual unit of measure (conversion uofm), visual quantity and/or weight (conversion number of some kind), and a flag to use or not use the visual (mini conversion) fields. - Dealing with the show/hide options on the quote and invoice line items, what about setting the normal fields like we already do (main line quantity and main unit of measure), then we could either duplicate that data on the show or special visual fields or we could set it to some kind of blank or default value. The goal here is to decide if we want to use one set of fields to do the backend accounting and then have another set of fields that show what was really going on. If we made it consistent, we could run certain reports off of certain fields and other reports off of other fields. That way we would have to add any special logic, it would be real values vs. show values. That might be nice. Just an idea. - When Steve and Calvin talked, they made it sound very simple and straight forward. When Brandon talked, it got technical and went into other requirements. As a side note, we may need a little bit of both simple and technical. |
|
|
|
Shop 2371 |
|
Adilas Time | 3/8/2017 |
Eric and I were on a GoToMeeting session. We were doing some research. I did some looking in the adilas university site. I found a couple of gems that talked about loyalty points and gift cards. AU - time id 2265 - 12/14/12 - concept of corp-wide settings for loyalty points. This was just an idea. AU - time id 1199 - 4/25/13 - punch card concept. This is a giant wish list and things that still need to be added. AU - time id 1233 - 5/10/13 - lunch cards and other needs for the same type of account. Some kind of special tracking account. Load, unload, check balances, etc. AU - time id 1240 - 5/20/13 - concept of a reloadable account of sorts. AU - time id 2898 - 10/18/14 - dynamic and broad, be able to name, use for multiple options, auto id's, user assigned id's, quick searches, homepages, etc. AU - time id 3818 - 4/27/15 - sub locations and unique ideas about promotion codes, referrals, drop shipping, gifting circles, and gift to get (points and credits), other gift card stuff. - Idea from Eric - On loyalty points and such, what about number of visits. This is something that may have been left out. This could be extra points for every 5th visit or a special discount on the 10th visit, etc. In the adilas shop (this site): AS - time id 2253 - 2/15/17 - cart logic plus loyalty points AS - time id 2257 - 2/22/17 - brain dump on ideas, tables, and flow for loyalty points. Some graphics and such with ideas on special accounts, transactions, and how to relate the account to different parties (customers, vendors, users, or generic). - What about doing some processes during a checkout. That would help with transactional data. Also, what about voids, what about changes to an invoice after the fact. We need to include some logic on those actions. - We really need some kind of a transactional accounting. What about time based options such as double loyalty points for the next couple of hours. - We need to record both the ins and outs on the points and redemption stuff. We looked at the current balance sheet items (say a loan or something). It allows for a name, a type, and recording of manual transactions (bump up or down). Eric wanted to have both a manual transaction feature (like the balance sheet) as well as automated stuff (cart and invoice logic). We also talked about having a main account table (what to call it - say lunch card), a table for account rules (what adds points, what takes things away - logic for the account), a table to hold the individual special accounts (say lunch card 1, 2, 3, etc.), and then an account transaction table. See screen shot for ideas and light flow. - One other note, we wanted to make sure and add one special column on the main account for a JSON object if needed. This would be for a developer to add something special. Not for the general public. The goal here is a special access point in case we need to go a little bit deeper and more custom. - The account rules would be setup like the iTunes builder, where we could catch all known rules. Such as: include items, exclude items, part categories, quantity rules, customer types, visit counts, special promotions, limited usage, and other special flags. - On the account transactions, we need to set it up similar to the balance sheet item transactions. That allows for bump values (+ or -), amounts, notes, and dynamic tie-in's to invoices and expense/receipts. Most of the transactions will be on the invoice side but we wanted to allow for other outbound monies if needed. Say an affiliate program where you actually earn cash or get a commission check or something. |
|
|
|
Shop 2480 |
|
Adilas Time | 4/12/2017 |
Steve and I were talking about people management and human resources. We know that there are people who want us to be very structured and very organized. Steve and I really don't want to go super deep into that model. Maybe we let them try to run with it. Go back to the railroad model. We own the tracks and the land and we allow others to build all around us and maybe ride along with us. We need to sell what we have. We may also need to help train them on what they have. We are seeing our clients as targets from other companies. They have a relationship with us and a level of trust, but these other companies want to jump on and sell to them as well. This is somewhat of a problem. We have somewhat given up two major pieces... They are the adilas market (adilas world) and the adilas university. Currently, we have allowed Adilas For Business to start running with these pieces. On pricing for a system, we need to have a standard structure. It is pretty loose right now. Also, we are seeing that companies that don't get trained, tend to fall off the system. We may need to go more towards a small package type scenario where we have setup, monthly, some consulting, and some training built in. We have tons of people who want to play but some of them don't really want to do the work. Kinda like the little red hen and making bread, planting, harvesting, grinding the wheat, and cooking the bread. Once it came out, everybody wanted to play but by then it was too late. We are seeing tons of outside parties that want to create their own little products. What people really want is an integrated product that does it all. They want a platform and/or a system. What if we don't try to grow and grow with more clients... What if we focused on the clients that we have. We have enough. We just need to take care of them. We just let things keep growing as we can (organic growth). We may end up pulling back a bit and stabilizing things vs. pushing forward with a wreckless vengeance. Adilas training centers. We've got some great ideas out there. That would be really cool. We are seeing more and more of a need to get our people trained. That helps make our clients happier and more loyal to what we are doing and where we are going. We keep getting ideas and suggestions (virtual idea farm) from our clients. We need to keep harvesting those ideas and such. From Steve - "It's not how fast you go, it is how well you go fast." - Good stuff. |
|
|
|
Shop 2557 |
|
Russell Moore | 4/24/2017 |
On a Zoom meeting with Russell. We started off the meeting with Russell doing a demo on putting the adilas university on a program called thinkific.com. It looked pretty cool and it was just what we are wanting to do on training and lesson stuff. Super cool. As we were talking, I was somewhat torn on using an existing product and/or building our own product. The problem is time and money. Currently we don't have the time to do and finish out our dreams. That hurts a little. We then talked about goals and direction and where we want to go. Russell is really trying to push us towards being bigger and bigger. That is both good and bad. I have some mixed feelings about getting too big too quickly. Interesting. After that, we switched gears and worked on a custom project that Russell is doing on the adilas 3rd party solutions page. It is dealing with a custom wire job and turning on multiple windows with just one click. |
|
|
|
Shop 2679 |
|
Adilas Time | 6/1/2017 |
On the morning GoToMeeting session. The first two hours were working on mini conversions. This was Steve, Eric, and myself all working and talking together. We were planning out database pieces and running through ideas and scenarios. We ended this section by giving Steve a small assignment to work on the mini conversion template level - first two database tables. he was going to be working on some ideas and concepts over the weekend. The second couple of hours were with working with Steve and Russell and I talking about things and where they are at. This got into a fairly deep conversation. We started out by setting up a light agenda... The first four main points were: our efforts (AFB and adilas), mini conversions and related items, other projects coming down the pipeline, and level of clearance. As we got into it, we only touched on the first topic and spent the whole there. See attached for some of the notes. There is also a small graphic that started the conversation out and where we could go. The graphic pitched the ideas of how AFB and adilas could either start the merge process and/or create a more distinct separation between the two entities. Basically, Russell and Chris Johnnie have been making enough waves that they are getting noticed. That was their goal. They have virtually tapped into some key elements including controlling the look and feel, ecommerce, new settings, the adilas market, and small taps into the adilas university area or space. We talked about the current state and how that could be altered. As we pitched the ideas, Russell played back and I took notes. To start off with, Steve mostly listened as Russell and I laid out some different plans and options. We were both laying out pros, cons, and virtual wish lists on how we could merge and blend things together. Topics ranged from goals, to buyout options, to who will take care of what. See attached for more details. Russell was very open and virtually laid out some of his ideas and strategy on where he was headed and why. After all of that, Steve started talking more and we have tons of notes from what he was saying. The gist of it was that adilas would like to restructure things into more of an overarching trust type option and then roll forward from there. Steve was pitching ideas on how we could come together as a single stronger entity. We talked numbers, financials, and options. Super fun talk. We ended the meeting by Russell and Steve saying let's meet and talk again tomorrow. Russell would like a certain level of power or influence over certain subjects. It was fun to see how certain things were playing out and seeing options where we could go. All parties left the meeting excited about more similar talks tomorrow. |
|
|
|
Shop 3111 |
|
Adilas Time | 10/31/2017 |
On the morning GoToMeeting session. We did some talking about current projects and progress. Russell popped in and asked some questions about sending emails and doing his own http requests. We got him all setup to FTP and interface with the adilas university site (where our email options are). Alan popped in and we went over more on the sales tax expansion project. He is just reading through things and trying to get up to speed. We also jumped in and did some checking on some code for the state Metrc (Metric) API. Towards the end of the meeting, we actually had a guy on with us from Metrc who gave us a new API key. Both Steve and Alan did some live code changes and gave him a small demo. Pretty slick and it looked nice. |
|
|
|
Shop 3195 |
|
Project management and planning | 10/31/2017 |
Doing research on subs of time. I found a number of good elements of time. Two good ones here in the shop were # 2042 and # 2130. I then went and read some stuff out in the adilas university site and the developer's notebook. I was searching for sub payroll and found a number of good entries in both sites. After reading those entries, I went and worked a little bit on the help file for subs of time (sub functions or add-on's of time). I was writing some info about the sub tags and flags and how they can handle sub categories, sub flags, sub groups, sub phases, sub progress, sub locations, sub tags, and sub types. Very flexible and pretty cool. |
|
|
|
Shop 3285 |
|
Adilas Time | 12/28/2017 |
Talking with Steve on the morning GoToMeeting. - Concepts of a trust and who owns what... -- What about founders, co-founders, dependables, etc. -- How do we bring people into the family or inter circle? -- How do we let people go? -- How do we pay people? -- Defining the model - Being a business solution like playing in social media - come learn about what adilas does - The use of the word dependables - Outside parties need to build on the main core platform - We are all standing on the shoulders of giants - We are working on a dynamic working model - we want to keep pushing that thing forward - What about multiple people trying to do similar projects at the same time? How does that play out. - Like landing an airplane... if you can hit the correct pattern, great, hit it. If not, just circle back around and try to line it up again. Basically, if you miss a pass, just do it again until it lines up. It is ok to make multiple passes. - Eric and his pricing engine - Russell and Chris Johnnie on their AFB stuff - Calvin and his email and text messaging stuff - There are a number of huge pieces that need to be nailed down and pulled in... they are things like adilas world, adilas market, and adilas university. - We want to keep pushing the adilas monthly up so that we could push more monies around to our dependables and other outside 3rd parties. - We may need to talk with some of our outside parties and figure out how to structure things. How can we join up and roll things together. - On the billing, we need to setup some standards for who bills, what percentages get kept and/or paid back - Put the monies into the payables and then allow some of our guys to go in and print their own checks. - If their payables go over a certain amount or certain age, we move it to the balance sheet - Define the core of adilas a little bit deeper - What are the ground rules and how to play the game. - We are seeing that our people want a level of trust and/or consistency - expectations and such - Like a volcano, inside the circle, outside the circle, how do people move between things, how do we manage complacency and/or lack of motivation - How can we help them (our players) see the bigger vision - Danny Shuford - We are a business solution for solution minded people - The Adilas API sockets will be coming more into the main picture. If we really push this out, we could harness so many more developers. We could really define what is available and what is possible. This is part of the Adilas platform and how it could work. - We can help steer the ship - The code is one of a thousand possible options. The concepts we are built upon are really worth way more than the actual code. - Steps to success - telling and catching the story - allocate some time to this project - what have we learned and applied along the way |
|
|
|
Shop 3416 |
|
Adilas Time | 1/25/2018 | Backing up images files, photos, scans, and media/content for all of the adilas.biz accounts. They are the main adilas.biz account, the playground - use for testing account, adilas university, adilas world, and the adilas shop account. | |
|
|
Shop 3536 |
|
Adilas Time | 2/27/2018 |
Barcode printer trouble shooting with a client. - Problems with the label printers. We have had more problems with the Zebra printers. They Dymo printers seem to work much better. More people are switching over to the Zebra printers due to ratings and quality. The Dymo is considered a lesser of a printer. - We do have a problem with receipt printers but not as much as label printers. - We are hoping that Svend (spelling), a tech, could help us out. - We have issues with operating systems, browsers, hardware, etc. They all need to match up. - We have had a number of complaints about systems being setup wrong. This usually isn't a software issue, but deals with settings and hardware. Maybe the system does have problems due to the number of options. - Shannon and Shari O. have been great on the support side. They are the best. - We briefly talked about possibly moving away from the Flash barcode generator. We could do HTML, CSS, and/or Adobe PDF. - We have seen problems with printing (receipts and labels) due to different browsers. Some times Chrome works better, other times Microsoft Edge or Internet Explorer. - Russell - we are not responsible for the hardware. Maybe we should specify the hardware to use. - When we say a self-serve model, people don't really understand that. What does that mean? - We need to use the Adilas Market (adilas world) to point people to professional 3rd party persons who specialize in hardware. - On the setup or start-up email, we may want to put some info there about integrating with hardware. - There are many people who like the freedom of picking their own hardware. We need to keep that open. We also need to figure out how to service that openness. - Just for an example - We had 6 key players on a multi-hour tech support call today. We really need a master hardware specialist. We just don't have a master and/or 3rd party solution for that yet. We need it pretty soon. - We are seeing quotes going out for 20-60 systems at a time. How are we going to support that? We may really want to get some certification and/or recommendations to outside 3rd party solutions. - There are so many hardware options. A GoToMeeting session is really hard if we are just directing mouse clicks. Sometimes if we are live and onsite, we can fiddle on things at our own leisure vs having someone right there trying to listen and puppet the motions. - Sometimes our reps (our independent consultants) really take a beating. If anything goes wrong, it immediately casts a negative reflection on the main adilas company. - Some of our clients don't have a clue on what they are training... Who's fault is that? We need to make sure that our consultants have the training that they need. - Often it is in the initial setup and/or training where things go off the tracks. That is huge. - We may need to push the adilas market more... this could be for training, setup, consulting, hardware, etc. - Certified or verified consultants. We may even need some different levels. - If a consultant does something wrong, if has a huge effect on us and our progression. - The Adilas University is another big spot where we can help educate and help train our people, users, consultants, setup people, etc. - We have some very complicated needs... We have multiple industries... tons of settings... tons of options... and multiple paths. - We also have some new accounts that are trying to be at the white label level. If they get that big, we want them to be able to help out with the tech support, training, and setup. - Steve - We don't have a contract and people complain a lot, but they often end up staying with us. - We are all independent... We need to have some options and/or contacts or connections. - Maybe a hardware doc that has options and/or even suggestions for 3rd parties that could help. - Steve - Question for our clients... Is it software support or hardware support? It almost goes in different directions. Maybe we should help direct the traffic where it needs to go. Maybe a number for normal support and a number for hardware support. - We all have spent hours and hours at people's places of business helping them get things setup. It would be so helpful if we had a hardware expert who could help. A hardware guy or gal may end up spending hours and hours figuring things out to get it working. - We have tons of past users who are master users and players... it would be so cool to harness some of that knowledge. - Russell's word - dependables - We need more people like that. They just get the job done and help our clients fly and be very happy. - As we get support calls, maybe ask who their consultant is? That may help us know who is doing what and where things may be needed. - We turned over the presentation over to Russell to show us around some ideas for the news and updates page (aka adilas features). Basically, an online list (very visual and easy to navigate) of help files, videos, tips, tricks, and other verbage info. We can load up all kinds of stuff, step-by-steps, tutorials, links, screen shots, images, animated gifs, animations, videos, etc. Basically, make the adilas user manual be a super powerful piece of the puzzle. Make the information more accessible and very visually stimulating. Help our users and reps/consultants get the info and training as quick as possible. - Steve and others have tons of emails with info, tech support, etc. That is a huge untapped resource. This is just a note. |
|
|
|
Shop 3569 |
|
Adilas Time | 3/5/2018 |
Morning GoToMeeting session with Steve, Alan, and Russell. - Still on building new deposits, we also talked about adding in new settings to show payments to be deposited by user and by money types. Make this a personal setting. Another personal setting could be how they want payments grouped. Once again, this could be by user, money type, dates, etc. More setting options. |
|
|
|
Shop 3589 |
|
Adilas Time | 3/12/2018 |
Morning GoToMeeting I was working on sales tax expansion project for Kelly - tying in the tax by customer type stuff. Alan and Steve were working on some Leaf Data and Metrc API stuff Russell and Steve went over the new WordPress news and updates section (adilas university, help files, media/content) for adilas features and such. Lots of good ideas and what not. Good meeting between Steve and Russell. Lots of questions and answers. Michael with McCorvey's Pro Shop jumped on and chatted with me on some needs that they have. Below are some bullet points from the conversation: Indiana - need this asap - county specific North Carolina - I didn't know about that FUTA - check Florida calcs Employees clocking in at one store but they really want that value to be split between locations. We talked about departments and how the internal setup goes. We also talked about a combined P&L between multiple locations (across states) and across multiple departments. Maybe relate the employee taxes to where the person lives vs where they work. Somehow we need to combine some hours and maybe even allow for cross bridging of hours between different departments. They would really like to be able to clock in/out at different locations and have the system calculate things properly. Problem with the cost of goods sold - they get items at all kinds of costs (sales, promotions, bulk, etc.) but they sale things and the system uses the last known cost. That creates all kinds of problems with the P&L. ICC - internal cost corrections - this is important to do for items and usage under the bridge - bring things back to 0 quantity and 0 costs, where appropriate. This needs to be managed going forward. This needs to be done location by location - per item. Michael would really like to get some data and the code for the part usage page and inventory adjustment pages - this would be database tables, data, code and page logic and also methods that are used. Possible black box code for average costs - tied to the add to cart logic - this is a new twist and/or option since we last talked Michael would really like it built in with a corp-wide setting that says something like - use last known cost or use average cost - this could be huge... it creates a nice alternative for similar businesses. There size and the number of locations complicates the issue. Some of their managers are paid based off of the percentage (back to the P&L) Item life cycles - at some point, the product will reach the end and/or die out. |
|
|
|
Shop 3693 |
|
Adilas Time | 4/25/2018 |
Talking about PHP projects with Russell. We talked about using Bridgerland and their developers to help build and maintain certain new and existing projects. Russell really would like to work on some developer training courses, API socket training courses, etc. Basically, ways of making it easier to get interested people into the development side of the system easier. We also spent some time talking about other possible projects... these would be built out using PHP and then connected to and/or talking to adilas.biz through external API sockets. Projects like outside scheduling of time (both adilas and google), outside ecommerce sites, visible elements of time (public viewable), project management, and scheduling time for employees. All great options. They would also be great projects for the Bridgerland developers. We also talked about pushing more and more on the Adilas University site, the Adilas Market (adilas world), play at the wall (web/API sockets), and creating a fun and pretty front facing site. We will fund those projects. We will keep core adilas and custom code behind the wall and keep it internal as far as who builds on it. The rest is open territory. Russell mentioned versioning our code so that we don't hurt other developers who have already done development. This is dealing with the API and then also making things backwards compatible. Basically, we really want outside developer to play the game and "Play at the wall". Good discussion. After that, I reviewed some notes about time clocks (see attached for an email that was sent out in December of 2016). I also wanted to make a note that elements of time # 2042, here in the shop, has a ton of information about some of the payroll, time clocks, and project direction. Just trying to keep all of the pieces sorta linked together. I scheduled a live adilas training session at Bridgerland for May 29th, 30th, and 31st. I let a few people know and will be trying to grab some ideas and such from key users, reps, developers, and admin persons. Good stuff. |
|
|
|
Shop 4011 |
|
Meeting with Shannon | 10/9/2018 |
Meeting with Shannon - 2 tasks to follow up on - hardware with Svend and picking up existing pieces for the adilas user guide. New notes - She has met with Svend twice and they have another meeting setup for later this week. Their goal is to get Svend's adilas market profile up and have some live content by next week. Once that profile is live, we will let Shari O. and Drea know to help point people who have hardware questions to Svend's market profile. As a second step, we would like to do some more news and updates (tips and tricks) dealing with hardware and then give some credit to Svend and such. Create links back and forth between the adilas market profile and the news and updates. Shannon will reach out to Russell and see if she can get some more advanced training on both news and updates and advanced options for the adilas market stuff. Russell is still the master there. On the user guide stuff, we also went in and found some of the old content that was created for the adilas user guide. I did some light checking on my end with no new results. Shannon did find a number of her files. Shannon will be pushing those pieces up in to the adilas university so that we can get to that info. She has about 20 Word docs that have some beginner user content. We scheduled a meeting for next week, and will stay on task with those two tasks. Just advancing the ball. Also, as a fun note, I gave Shannon some other updates on who is working on what and some other inside adilas news. We are really excited to have Shannon back working with us. It will be awesome. |
|
|
|
||||||