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 - 8/1/2013 to 8/31/2013 - (58)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
Adi 741 |
|
Custom Code | 8/1/2013 |
Hi Steve, I hope you are having a nice week. I spoke with Mark Spoone today and we discussed the commission structure for the sales reps and we would like you to go ahead and set this up in Adilas. We pulled reports today by sales rep/location and it's a nice report except we couldn't see the breakdown of cases they each sold. With that said here is what we would like to see in Adilas... Commission Structure: Sales Price - $31.00 = Commission If a Sales Rep shares a sale with another Sales Rep the commission (Sales Price - $31.00) would be split 50/50. If the call center shares a (telephone) sale with a Sales Rep then there is a 1% commission for the Sales Rep. It would be calculated like this: Sales Price - $31.00 = Commission; Commission - Sales Price * 1% = the commission the sales rep receives. Please let me know if that makes sense or if you need further information or breakdown. Thanks for your help with this. Let us know your timeframe ;) Talk soon, Kath |
|
|
|
Adi 742 |
|
Custom Code - Kelly Reuest | 8/1/2013 |
Steve - I am thinking I would like to add a few items to the MMJ Operations Page, these are items that AZ is computing manually (and it is not easy to do) Total Sales Less Tax Weight Sold (We need to figure this out for both We-Weight and Pre-Weigh) Average Weight Sold Per Customer % of Sales by Shelf (Top, Mid, Special, Etc - description) # of New Patients vs # of Returning Patients Sales Male vs Female Total Customers Per Day (Not Invoice = Customers) Are these items that can be added easily? Let me know. Best, Kelly |
|
|
AU 1718 |
|
Daily Tasks | 8/1/2013 |
• Recording notes form conversation with a rep from yesterday. See previous day. • Checking images and writing an email to a contact at BATC about uploading photos and images. • Light tech support. • Research and email updates about a report request to allow all products to be matched up with a vendor even if they (the vendors) are different. This might sound weird but currently all vendor searches try to match the vendor to the PO line items. However, we have a need to search by the main PO vendor and then get any line item that matches the main vendor regardless of the vendor assignment on the line items. This is a complication dealing with generic inventories or mixed vendor inventories. • Working on the advanced PO search and adding a new main vendor search option. |
|
|
AU 1745 |
|
Daily Ideas | 8/1/2013 |
-On elements of time for the developer’s notebook – I would like to create a monthly recap time template. In that or those entries, I would like to upload full notebook pages in sequence for the month. All of the other entries will have date specific tasks and ideas. The image galleries for those pages will also be specific for that date. The month end or monthly recap entries will have a basic recap and then pages and pages of raw notebook files (photos and scans). This may be a good spot for someone to go and then virtually look right at the physical notebook pages vs. going day by day and then browsing entries. -Observation about searches and drill-downs – Almost any report or relationship may be pulled as part of a report (simple). This includes special hardcoded and/or dynamic filters. The power of adilas is allowing for those reports to be searched or drilled-down into the underlying data. The drill-down provides the evidence or support of the sum or grouping. The reason for this comment deals with bottom level is flexible and dynamic, you can then build groups and sums on top of that. If you start with the group or sum, you may need to build each drill-down as its own sub report. So, in a way, if you start with a dynamic result, you can build on it as a base. If you start with a grouping, you will either need to make it a standalone value or create a custom drill-down report to support it. The more groups you want, potentially, the greater number of supporting results or reports you will need. If the bottom level is already flexible and dynamic, you can pass data back and forth to give the illusion of supporting details. It (the flexible and dynamic bottom level) also allows a user to get right to that data without going through an upper grouping. Anyway, just an observation. -Once we get all of the eCommerce stuff done – we may want to change the default web presence address to the main adilas.biz domain name. Sometimes the webservices don’t fully match what is really there. Either that or we need to sync things up better. If we do use the main adilas.biz site, all the data is live vs. relying on a webservice synchronization. -We need to allow small images on the part category section. It will add more color to the page. I also got an idea from a contact at BATC to add a category switcher at the top of the search result page for eCommerce. |
|
|
AU 1719 |
|
Daily Tasks | 8/2/2013 |
• Brainstorming and reviewing different pages. • Sent off a number of adilas logos to a contact in Colorado. He and his partner are looking into doing something to help sell and support adilas. Interesting. • Recording notes. • On the phone with Steve going over our plan and how to get things out to the people. We need to get more people involved. We talked about eCommerce, opening up the API, and allowing others to piggy back and play side by side with us. Eventually we will be training our competition. We feel kind of weak right now but eventually it will turn out okay! Here we go! Recording more notes and ideas. • Working on the advanced PO line item search by different vendor options. • Got a call from a rep in Denver with a request to get more columns output on the advanced invoice line items export to MS Excel. Made some notes on what is going on. • Working on the advanced PO line item search. Finished up and posted files online. |
|
|
AU 1746 |
|
Daily Ideas | 8/2/2013 |
-Adilas has become somewhat of a community effort and/or community project. I would love to keep it that way. Maybe the community and our users could help us take things to the next level. -On the permission to lock down customer to reps – we know that ideally it would work best as a one-to-many relationship but we are thinking of doing a miniature version to start with. This will be a more rigid permission. That will solve some things temporarily until we can circle down and around again. -As a side note to the customers to salesperson (reps) permission – On the one-to-many, it would be cool if we could set up limits, permission, and even do both (limits and access) based on states, customer types, zip codes, cities, etc. That would be really cool. -Also as another note on the customers to salesperson permission – It gets deep pretty quickly. What about customers tied to invoices, stock/units, elements of time, quotes, statements, etc. What about those relationships? Are they limited or open based on settings in this permission? -As soon as we can, we need to do the following: - Open up the API (application programming interface) - Add the content server (separate content from data for load balancing) - Make the system more modular and independent (tons of mini adilas’) - Finish up eCommerce (it is close but it needs a bit more) - Round two (2) of elements of time - Roll call page for all main players - Reflexive side of the flex grid -Maybe put all adilas.biz help files on adilasuniversity.biz site. I’m assuming that eventually there will be tons of different domains that serve up adilas content. It might be nice to have a standard place for all main adilas help files. -The flex grid is super cool and very flexible – However, we are seeing a need for in-line fields that may be used for parts, invoices, customers, vendors, etc. Almost a custom field level for all of the main 12 system players or groups. The thing that would make it cool is if you could name it, set the data type, set rules and defaults, and then be able to search by these fields according to data types (dates, numeric, decimals, text, and binary). The search ability by data type is super important. -In a nutshell here is what is going on. People are getting creative and recording their data wherever they can right now. They, the companies, then export the data into MS Excel and then use the data to represent different things. It would be nice to help them out. The problem comes in to play as each company is unique and may have different needs. We could add some custom fields but then it makes the whole system a little heavier. This would be a case where we would add static fields in order to increase dynamic usage. I see the need, but I’m not sure we are ready to jump yet in that direction. The ideal would be to allow for unlimited dynamics and allow for those changes to happen and flow within the bounds of the system. This is custom, yet in-line, and fully allowed; that could get kind of tricky. -Another piece to the custom and in-line code is getting each corporation or world by itself. That makes the custom fields weigh less because they only apply to certain worlds and/or corporations. The trick there is updates and changes. If everything is custom – how do you update pages and features. It kind of comes back to in-line custom code. Basically, we know it needs to be custom so, plan for custom right off the bat. -All of this talk about in-line custom code makes me think of settings and permissions on an almost page level. This could be clear to the – use this field, call it this, require this, search by this, and have it show up here and here and here. Basically, this is the default outline, layout, and pre-set settings. If you want something different… you need to play at this upper admin “tech” level. Then you could do custom right out of the box. We aren’t there yet… but I can see it down the road in the future. -Two huge keys are: 1. Centralize the data 2. Catch the data -If you can get to that level – the rest is all possible. Those are the two things I see as paramount! -The deeper we go, the more we see things headed to “world building” and “virtual world building”. -Sometimes I get so excited recording notes and ideas that it is hard to pull back and do the work. Maybe I could become a professional daydreamer! -This is kind of silly – we say that our biggest competition is “tradition”. We also say that eventually we will be used to train our competition. What if we end up training people how to overcome tradition? Anyway, I thought that is was kind of funny. -The assembly line really helped out businesses. Things were done overtime and then passed on to the next step of the assembly line. Adilas does the same exact thing with your business data. Things are done over time and then passed on to the next step. Pretty cool! -I’d like to make a graphic and show how businesses use different assembly lines. It would then be fun to show how adilas uses similar processes to link and connect data together. -This is an old analogy we used to use for showing flow (graphics/sketches for each): operations and accounting - both perfectly in line – static. Operations and accounting – different things happen over time but they come back together – dynamic. The new analogy may look something like this – once again relating back to an assembly line – type analogy: operations and accounting – different things happen over time but they come back together in order to pass the checkpoints. Or another analogy that fits this flow is a bottle of data flowing down the river. As it flows (through a virtual assembly line) it passes certain checkpoints. My daughter even drew me a graphic for this. Some of the key elements are: 1. Enter once 2. Use over and over 3. Run it over time 4. Checkpoints help maintain flow 5. Checkpoints may be permissioned if needed 6. Track the entire life cycle. |
|
|
|
Adi 743 |
|
Custom Code - Michael | 8/2/2013 | Redo add to the current operations page and look at ranking on the CRM/Sales/Games page. May move them to crm_3 or crm_4 | |
|
|
Adi 744 |
|
Custom Code - Idea | 8/2/2013 | Kelly and Josh want to have a multi view of the income statement over time ........ year to year to year view. I'll setup a page that has 3 frames and populate with the income statement in each, they can set the dates and pull the data | |
|
|
Adi 745 |
|
Custom Code - ideas for operations | 8/2/2013 |
For our day to day operations or any other company as well I'm going to try a 3 or 4+ frame operations page and drive data reports/forecasting/et cetera into the frames. This way people can interact and the get even more lost :) Frames could be the answer to many challenges I'm having on operational pages. But need to research because HTML5 does not support ..... |
|
|
AU 1720 |
|
Daily Tasks | 8/3/2013 |
• Writing an email to Steve about pros and cons of using HTML frames. We want to make a POS (point of sale) interface for restaurants and deli’s. Basically, the interface will have menu buttons on one side and the actual cart or shopping cart on the other side. It should be a fun project. • Prepping for new projects. Making and recording new notes. • On the phone with Steve talking about new projects. We talked quite a bit about a new POS interface called the “split cart” which will end up being an HTML frameset with menus on the left and the cart on the right hand side. Basically, it will leave the cart favorite buttons up and available on the left and all other actions will be done on the right. It should save some time and be easier to use if the company uses my cart favorite buttons. We also talked tons about working with and educating reps vs. clients. That way, the reps and consultants can teach the clients. We also talked about marketing and funds. Great conversation. • Added an update to the news and updates page about the new link to view all PO line items. • Other emails and tech support. • Combing customer data for a company for a custom list and data upload. |
|
|
AU 1747 |
|
Daily Ideas | 8/3/2013 |
-I’d like to add a new set of reports that are on the adilas upper admin level. In world building terms – this is at the universe level. This would be global specs, how many customers, invoices, quotes, expense/receipts, deposits, PO’s, parts, locations, banks, cart favorite buttons, users, logins, etc. This could be daily, weekly, monthly, or custom. It could also include photos and other universe level stats. I’m not worried about the details – this is just for general stats and usage. -As a note, we need to remember to only get what we need. Each corporation or world takes care of their own business! -Other universe level reports are: How many logins per day? How many unique users per day or date range? How many images and what is their total storage size? Etc. -We may want to standardize the customer and part number data import files and structures. If yes, we could move through those files in a much quicker format. If custom is needed, then we could run that separately or on a per client basis. Basically, I’m spending too much time on some of these files. -Ideas for a new “split cart” POS interface – Steve was playing with ideas and we are thinking about making it a new standard option inside of adilas. The split cart would be my cart favorite buttons on one side and the main cart on the other side. As a button gets pushed on the left, the right side updates and shows the changes. In a way, it will be almost like having two windows open at a time but they (the two windows) will be interacting and playing together. -Here are some needed features of the split cart: - HTML frameset – my cart favorite buttons (left side), normal adilas shopping cart (right side) - New mappings on URL addresses and window targets - Custom code for different button types and button groups - Ability to reset the split cart - Ability to toggle between a normal cart and the split cart - Simple dynamic nav on the left. - dummied down interface - Maybe even a dummied down cart for the right side -Along with the split cart, it would be cool, if we had a couple more personal settings to go along with that. I was thinking: Normal cart or split cart (cart view modes), who’s cart favorites to use, and any other my cart favorite settings that might be needed. -Help our users get in and out as quick as possible. At the same time, they still need to provide enough data to make the trans-action happen. -A possible usage of “invoice classifications” (future project) is as a custom “checkpoint” for invoices. This could be a date and/or a date range, an invoice classification, and maybe some notes. Invoice classifications may also be used for eCommerce or even steps in the eCommerce process. For example: ordered, filled, skipped, backordered, etc. -A couple pages back there is an entry about making a data or business data assembly line with custom checkpoints. The invoice classifications or something like that may end up playing in or filling that need. As a note, we already do a custom mapping for “transition invoices”. The invoice classifications could easily be something like that and/or something similar. For future reference, see top_secret/secure/view_transition_dates.cfm for more info and sub settings for transition invoices. |
|
|
AU 1721 |
|
Daily Tasks | 8/5/2013 |
• Recording notes from my mini notebook. • Working on a customer import file for a client. Lots of data combing. • Went in to Smithfield to meet with my brother and sister. Talked with my sister about the developer’s notebook and taking flyers up to the University. I got a couple new videos from my brother. He didn’t come while I was there so I watched both videos all the way through. I left him a note and called him before heading home. 20 miles. • Working on the customer upload for a client. • Working on another customer upload for another company. • Writing an email to a client explaining why the upload is taking so long. Even sent a small screen shot of the data. • Finished up the customer upload for a client. |
|
|
AU 1748 |
|
Daily Ideas | 8/5/2013 |
-These notes came from my mini notebook that I keep with my scriptures. It is a little hand held mini notebook. There are tons of other notes in it as well. -Here are a couple of notes from church yesterday that relate to what we have going on with adilas: -Perfect linear vs. branching and somewhat random. This deals with how we show flow and processes. Often they are perfect linear marks… however, in the real world, each one may be different and possibly has many subs or branching paths. We need to be able to follow what happens in real life. Plan for random. -Time is important but so is trouble and adversity. Often, time allows us to overcome and deal with the troubles and adversity. They work together. -If we “unite” together – that is where the power comes from. Be united! -Seek and find safety through sharing! -Enjoy the journey! -I’m grateful that the Lord has allowed me to work with Steve Berkenkotter. It sure has been fun and I’ve gathered strength from him. I’m grateful for our mutual friendship and business relationship. -Help lift and promote others. -Allow others to help and then help promote them as well. -Build bridges! -Freedom comes from living and playing according to God’s rules. -Freely give, freely receive – share! -Dealing with elements of time – Allow other people to chime in. This could be as simple as opening up the view and comment permission for elements of time. We could then approve and allow as needed. Virtual mini forum. |
|
|
AU 1722 |
|
Daily Tasks | 8/6/2013 |
• On the phone with my brother talking about graphics and sales. We are planning to meet tomorrow and go over a plan and do some training. We talked about doing some marketing and even some graphic practice on the developer’s notebook. I’m hoping to use my brother’s skills in graphics, animations, and in sales. He has a natural skill set that lends well with sales. • Back working on some data combing for a client. Lots of manual entries. • Went in to Bridgerland to work with my dad and a contact there. I spent some time working on a customer data files and helping to answer questions about adilas. I also had some light conversations with different people who came in to look at the BATC surplus items. Once everybody left, I ended up talking to this contact about business and how to grow. He is quite a dreamer and has worked with IT (Information Technology) people before. We had a good talk. He made a couple suggestions including contract labor and keeping things on contract labor for as long as possible. He also mentioned project management software and helping to track things. My mind turned to elements of time and tweaking a few things out a bit. We also talked about using other people’s money to grow our business, instead of us funding the projects. Let our customer’s fund projects that they want and then sub those projects out. I (Brandon & Steve) need to get out of the hot spots and dream and manage more. We also need to charge more and cover our costs. Good things are happening, we just need to keep going and be willing to change as needed. Change can be very hard. It can also be needed. • More data combing for a customer data upload. Finished up and uploaded 1,100+ new customers and log files. Sent an email update. |
|
|
AU 1749 |
|
Daily Ideas | 8/6/2013 |
-A contact at Bridgerland made some recommendations for photo management. He would like to see the ability to upload multiple images and also a system where the computer automatically goes right back to the photo management page. Kind of like an upload and then do it again without any interactions. -As a note on the multi photo upload. It may be a cool little feature to tie into the content server. Basically, push the files up and tell the user thank you, and then keep going. When done, record the action but do some of the processing behind the scenes. This may be a good way to use a content server and then talk back and forth behind the scenes. Maybe even using a webservice and/or JSON (Java Script Object Notation), anyway, some good ideas. -We may want to run an ad for contract developer or developers for small projects. -An idea for inline custom code – What if we allowed each page in the site to have a custom section where code could be added for buttons, links, graphics, etc. Imagine a spot at the top, a part of the main body, and a part at the bottom. Almost another piece of the header and footer that allows custom code. It would be both HTML and possible dynamic code options. On the dynamics, it could be, pick what variables are available and do the mapping in-line. -If we allow in-line custom code, we will also need to validate it. This may be down the line a ways. |
|
|
AU 1723 |
|
Daily Tasks | 8/7/2013 |
• My brother came for a meeting. He showed me some graphics that he was working on for adilas. He has one that will show an adilas logo and then different skins that could be mounted over the top of his “adilas engine”. That will be pretty fun. He is also working on one that has a horse and a cart. We did some training in Fireworks and worked on some image clean-up. We then did a logo for a company. After that I did a small demo of different graphics and Flash projects that I have worked on. That was fun. We talked about other commercials (animations) and storyboard ideas. My brother is excited. I printed him off a bunch of training flyers and got him a check for work that he has been doing. • Recording notes from my meeting with my brother. • Random to do list stuff. • Emails, tech support, invoices, etc. • On the phone with a website developer talking about a gun club and shooting range. They are looking for eCommerce and reservation stuff. It is exciting to see where things are going. • Went in to Smithfield to work with my mom on adilas. She got her first order of bulk herbs in today. We added 30+ items on a PO, we globally updated some prices, setup a bank, did one deposit, and 4 expense/receipts. Great little training sessions and she is picking it up and doing awesome. It is fun to see her get it and start to make connections in the system. I also got a new video from my brother to upload to YouTube. 20 miles. • Emails and tech support. Wrote a long email about using barcodes and the barcode generator. Also included info on hardware recommendations for label printers and scanners. |
|
|
AU 1750 |
|
Daily Ideas | 8/7/2013 |
-Commercial idea from my brother – The adilas.biz system overview map flyer as a commercial. It talks about sales, inventory tracking, point of sales, CRM (Customer Relationship Management), scheduling, online expense tracking, BI (Business Intelligence). Backend office and accounting functions, payroll and timecards, and how you get all of this with adilas. The complete package. -Elements of time – we will need rentals, reservations, and bookings to be tied to eCommerce very soon. It is coming! |
|
|
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 1725 |
|
Daily Tasks | 8/9/2013 |
• Working on specs for a teacher to student interface. Prepping information to send to my brother to help with the graphics. • Entering business expenses from July. Got kind of behind due to a crazy July. Light balance sheet work, scans, and expense/receipts. Worked on bank stuff. • Paid some credit card bills. • Emails, graphics, and tech support. • Emails back and forth with Steve. • On the phone with my brother going over proofs and graphic ideas. Good stuff going on. |
|
|
AU 2292 |
|
Brainstorming - Ideas for a Teacher Interface and/or Custom Homepage | 8/9/2013 |
Ideas for a teacher interface and/or custom homepage: - Final dimensions 750 x 450 (width x height) – the image needs to be: a gif or jpeg image - Once the graphic exists, we will wire it up to make it be active. - There are 4 main sections: o My Student Log Notes o My Student Follow-ups o My Student Flex Grid Tie-Ins o My Calendar - Each section needs a link to the following: o Today o Yesterday o Tomorrow o This week o Last week o Next week o This month o Last month o Next month o Home o Advanced Search o All - Ideas: o Desk, chalkboard scene, classroom scene, or something teacher(ish) o See sketches on scan in photo gallery |
|
|
AU 1726 |
|
Daily Tasks | 8/10/2013 |
• Emails and reviewing things on the to-do list. • On the phone with Steve going over tons of things. We talked a lot about getting help from contract labor and people we know. We talked about using client money to fund these outside projects. Basically, as a client needs or wants something, we charge them and then sub our small pieces of the job to our sub contract labor people. We are already doing that a little bit but it could continue to grow. We want to stay with contract labor for as long as possible. We also talked about my brother and using him for some graphics. We talked about job costing and circling around and fixing small pieces of the puzzle. We also talked a bit about eCommerce and different client needs. The other subjects were in-line custom code, page settings, and how to do the adilas API (application programming interface). We talked about ways to handle and deal with possible security issues and flow. Good stuff and a great conversation. The other person we talked about was an adilas team member and making sure we take good care of her, she is a great asset to the company. • Recording notes and ideas from my conversation with Steve. • Checking image sizes for photo uploads; we may want to help that process out a bit. We are getting quite a few bigger images and scans. • New limited customer search permission. This will limit customer searches base on assigned salesperson. • Also worked on the printable vendor search results. Changed some permissions. Also added a basic numbering to help people know what permissions to add or check. The numbers will change but at least it is a good starting point. More work on the limited customer search permission. • Working on the limited customer search by salesperson permission. Got files done and posted files online. Started testing and activating the new permission. • Adding an update to the news and updates page for the new permission. |
|
|
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 1727 |
|
Daily Tasks | 8/12/2013 |
• Added the main elements of time notes field to the default output for advanced time searches. Posted files online. • Checking on bin #’s and units of measure on the advanced invoice line items search results. • On the phone doing some tech support. • Quick call to Steve to check on some items. • Finished up the code for showing bin #’s and units of measure on the advanced invoice line items report page. Posted files online. • On the phone with my brother talking about graphics. He sent me a fun prototype of his teacher interface with items kind of blocked in. We also talked a little bit about Flash. My brother is thinking about learning Flash as well as Fireworks. • Went in to Smithfield to work with my other brother on some video stuff. I got a new video from him and we talked about future projects. 20 miles. • Checking out the PO line items advanced search. Trying to make sure that it (the report) was able to export bin #’s and units of measure. • Finished up the new column output values and posted files online. • Reviewing my brother’s latest video from the February 2013 training event. Squeezed the video clip and uploading it to YouTube. • Random phone calls and light tech support. |
|
|
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 1728 |
|
Daily Tasks | 8/13/2013 |
• Emails and light research on the first data gateway. • More emails. Small fix on the flyers page for outside reps. • Went in to town to meet with my brother. We talked graphics and then did some stuff in Flash. My brother wants to learn and I’m game to help him learn. It will be fun. 30 miles. • Meeting with my dad and one of his associates. We met with a CPA/business consultant about setting up an education based non-profit organization. Good meeting. • I then worked with my dad on setting up a demo for use with the Bear 100 mile race and using adilas to track runners. We took some time and entered in some fake data. |
|
|
AU 1753 |
|
Daily Ideas | 8/13/2013 |
-On sub dates and times within the main elements of time section. We need to help populate certain next date fields and allow new entries to be added leaving off right where the last entry left off. We also need to calculate or add up the totals. These are all small things that would help speed up the process. -We need to get Steve’s “steps to success” into the user manual. They are kind of rough, but at least they are there and have been written up. They also contain links to help files and links to YouTube videos. Good start, good stuff. |
|
|
AU 1729 |
|
Daily Tasks | 8/14/2013 |
• Adding a new logo for a company. • Took some extra time and sent my brother some ideas on how to tweak an image. I made some minor changes and then documented them so that he could see what I did to tweak things a bit. He is learning very quickly. • Working on pagination for showing and viewing my car favorite buttons. • On the phone with a past adilas rep who is looking to come back to work in Colorado Springs area. |
|
|
AU 1730 |
|
Daily Tasks | 8/15/2013 |
• Working on pagination for my cart favorites. • Had to figure out a way to add row counts to query results. I then used these row numbers as part of the pagination. This one was kind of funky because the output was grouped instead of normal base records. Anyway, a bit of a challenge. • Answering emails and light tech support. Pushed a couple more graphics over to my brother to work on. • Went it to town to meet with my sister. We met and she showed me the progress that has been made on the developer’s notebook project. She has 1,800+ elements of time in and online. Great stuff. The bulk of our meeting was dealing with the user’s guide or user manual. We also talked about reaching out and getting additional help from others including volunteers. 20 miles. • Lots of emails, light tech support, and helping my brother with some graphics. We’ll call that graphic support. • On the phone with Steve. We talked about new custom projects and how to fund them. We talked about interns and using college kids and university folks. We talked about storage for clients. This storage could be old archives, files, pdf’s, etc. We also talked about changing a focus from “that is on our tick list”… to “that’s a great idea! Are you willing to pitch in and help it get done?” Anyway, a huge paradigm shift for us. We are going to be recruiting help, interns, and even volunteers to help with different projects. There is enough of a custom demand that we are going to elevate things to the next level. Great conversation. We are both super excited about the direction we are headed in. Yee haw! • New logo for a company. |
|
|
AU 1731 |
|
Daily Tasks | 8/16/2013 |
• General to do list stuff. Light brainstorming on marketing and email stuff. • Graphic support with my brother and other email updates. • Renewed a number of domain names for adilas. • Purchased the adilasworld.com and .biz domain names. • General to do list stuff. Wrote an email to the folds at USU about a need for two paid interns from the USU Business School. • Went in to Smithfield to work with my brother on video footage. He is doing well and gave me two new clips. 20 miles. • Uploading video clips to YouTube. |
|
|
AU 1754 |
|
Daily Ideas | 8/16/2013 | -Possible future domain name – adilasstorage.biz | |
|
AU 1732 |
|
Daily Tasks | 8/17/2013 | • Answering emails throughout the day. | |
|
AU 1733 |
|
Daily Tasks | 8/19/2013 |
• Product upload for a company. Ran into a problem with the part numbers being too general or generic. They were note unique and the data file had a number of duplicates. • On the phone with Steve going over different ideas and going over questions and current projects. We talked about interns, projects and transitioning into a different system of charging for custom stuff. • Creating a number of custom pdf’s for some contacts down in Colorado at adilasdata.com. Sent the custom pdf’s to one of them that attended our last Denver training session. • Reviewing an email from my brother about Ted talks at ted.com. Some fun stuff there. • Prepping files to create a cross venture with an email and text messaging company called Full Circle Interactive Media. I sent them some sample data and a sample API method call. The email also included some other security specs and ideas. • Working on a custom project for a teacher and tracking her students using customer’s and flex grid as core curriculum data points. • New logo and wiring up custom homepage and interface options. Using my brother’s custom graphic as an image map for the teachers. Wiring up the graphic and overlaying buttons for the teacher interface. Fun and good stuff. Small tweaks to underlying pages to pass correct variables. • More wiring up the graphic. I’ve been making lots of underlying page changes to allow things to be detailed out. |
|
|
AU 1734 |
|
Daily Tasks | 8/20/2013 |
• Emails, phone calls, and light tech support. • Following up with Utah State University about getting some interns to help with projects. • Working on the teacher/student interface. Made some code tweaks to how the flex grid plays and passes data over the URL string. Finished up wiring up the custom teacher/student interface. It has 59 buttons overlaid on a simple classroom setting graphic. Pretty cool! • Working on some custom flex grid stuff for a teacher and the teacher/student interface. Getting organized and recording ideas. • Went in to town to work with my brother on video clips. He gave me two new clips to put up and online. Also talked with my mom about adilas contacts up at the University. She is a great cheerleader. 20 miles. • Working on the teacher’s custom code and special flex grid page for her students. |
|
|
AU 1755 |
|
Daily Ideas | 8/20/2013 |
-Thinking about the adilas community – Lots of community ideas… Lots of community projects… Lots of community funding… -Recruit other people and harness their talents. Let different people help where they are able… Lots of hands make light work. -On the flex grid – tighten things down a bit to allow users who have a “limited customer search” permission only be able to see customer flex grid for their customers. We also need to limit viewing options and add/edit flex grid features according to the limited customer search permission. -On the standalone flex grid tie-in page – Add some math to the values column, add export and filter options, add checkboxes and Java Script for math, basically make it feel like its own little database per main item. Trick it out a little bit. Maybe also show/hide row options or even show/hide options per column. Basically, be default it will have auto populated info, but if needed, the page could be tweaked out and/or exported to meet the needs. -Eventually, the standalone flex grid tie-in page will need to be able to hold its own settings, preset values, filters, and other custom settings. Think mini database per main item. |
|
|
AU 1735 |
|
Daily Tasks | 8/21/2013 |
• Posted two new YouTube videos up online. Added links to the adilasuniversity.biz site. • Working on a custom parts upload for a company. • On the phone with Steve going over the adilas world site that Steve is building. He had a couple questions. I also showed him the teacher/student interface and we talked about schools as a possible venue and client option. We also talked about gift cards and in-store credit options. If we went in that direction, meaning schools, we would need some custom code but 90+ percent is already there. Fun conversation! • Setting up a school playsite. Also finished up the part number migration for a company. • Emails and light clean-up. • Adding flex grid tie-in titles and custom fields for a client. Working on corp-wide settings. • My brother came over and we had a good session. We talked about Flash, animations, ideas for adilas commercials, recent projects, his classroom interface graphic, and other projects. We did some training on elements of time and customer billing. We then setup new corporations for him for family history and his studies or school work. Great session. • Went over to a client’s house to show her the progress on the school data tracking system. She had another teacher there so I showed both teachers the system and the tweaks we had made. They really want to see the flex grid piece in action and see how easy it is to add the core data points. Basically, they want an easy button that says “add core data.” The page then shows a simple search with the student’s name and an add button for each student to go right to a custom flex grid form that says “core data.” It has limited fields but allows the teacher to quickly slam in the data. The pain is getting the data in quick and easy! • Recording notes and ideas for the school project. We need a couple tweaks. |
|
|
AU 1756 |
|
Daily Ideas | 8/21/2013 |
-I was on a walk with my dad this morning and I got to thinking – my dad is a great recruiter and talent scout. It would be cool to tap into that talent and resource. -A long time ago I worked with a guy who was a master designer and a great artist and computer guy. I was thinking about contacting him and seeing if he had any leads to people we could hire for adilas work and projects. Ben is a master and would be another good resource. -Use the adilas demo sites in training. This will help keep them up to date and make them better play grounds. |
|
|
AU 1736 |
|
Daily Tasks | 8/22/2013 |
• Tons and tons of brainstorming ideas. Lots of them have to do with the teacher interface we are working on. See other notes and bullets on the next couple of pages. I’ve got 12 little post-it notes full of ideas written or scribbled out on my desk. • Made some phone calls about an upcoming teacher’s meeting next week. • Emails and other phone calls. • Called my brother to talk about some graphic changes we need for the teacher interface. • Emails and recording notes. • Made a to-do list because my desk is exploding with post-it notes. • On the phone with Steve going over different projects and future game plan options. Our game plan is to keep our costs low. We spent almost an hour talking game plan, goals, and ideas. We are going to be openly soliciting help, funds, and ideas from the adilas community. This will push the product forward and will create tons of new jobs. We are seeing a growing need to push elements of time to its full potential. We need it to help communicate with our clients, our users, our developers, and with the community. Good stuff. • Recording notes and trying to get organized. • Phone calls and emails. • Went in to town to meet with my dad, my brother and another contact. This contact is a freelance graphic artist and is going to help adilas with some graphics and basic HTML stuff. We chatted and shared some needs and vision of the future. We looked at her work and talked about some training for my brother. She will help train him in Adobe Illustrator, Adobe Flash, and Adobe Fireworks. She should be coming to the adilas training in a couple of days. 30 miles. |
|
|
AU 1757 |
|
Daily Ideas | 8/22/2013 |
-Last night and this morning I had a great brainstorming session. The result was tons of post-it notes all over my desk. Some of these notes are in random order but were part of the brainstorming session. -On elements of time – We need a multi filter for elements assigned to a single person (normal) plus any elements that are unassigned or general items. This could be as simple as a list like “1,77” where 1=unassigned, and 77=some user id number. This is a small tweak but it could really help in a shared environment. -We’ve said this before but we need to open up the adilas API (application programming interface) and make it consumable by any other application and/or programming language. We need to be willing to allow things to be more open and available. -I don’t have to know all of the new technologies. Allow others who know the new technologies the ability to use and build as needed. Let them consume or use pieces as they see fit. -We may need to hire out the web design for the main adilas.biz website. It might be good to get some fresh blood and new ideas. -My brother said his friend wanted to see the customer reviews and ratings for adilas. We are working on it. -On standalone flex grid reports. Allow multiple sort options. This could be on custom fields, dates, values, id numbers, etc. -On the standalone flex grid report (and maybe other flex grid reports), add up the columns if possible. If numeric, great, add it up; if not, assume 0 and leave the total blank. -We have had requests to add bulk flex grid tie-ins. This most likely will be custom but very possible. One of our first shots may be for teachers and students and entering grades and assignments. -On elements of time, in the time slot view – add a check for pre (before block) and post (after block) elements of time. Basically, show a count of elements that are outside the visible start and end time block. -On some of the custom interface pieces – we may need to check for certain settings or custom documents. If a corporation doesn’t have those, show a light error and maybe even show a graphic or screen shot of what would happen. This could help teach them and still say a gentle no. -Maybe use quick graphics and proofs to help show what the plans are and what might be coming. Just like when a building is going up, the drawings or plans help to show the vision. We need more of this. Something quick to show the concept. -We may have other pages where we could create some quick graphics to show the concepts and/or mock-ups of what will go there. Treat it like marketing and planning. -Show a standalone flex grid link right by the in-line flex grid report. Currently, the link to the standalone flex grid is up at the top of the page. We may also want to add new flex grid tie-in links where the flex grid in-line reports and shown. Make it friendlier. -Quote from my friend in Colorado – “Get out of the way and let people come in!” -Add a button for the “paperwork” link to pages. If the custom documents exist, let people get to it easier. -On the custom documents page, maybe show buttons and links. Currently only links are used. It could be something like: Button [view/use] – Title and normal link (some custom document name), [view/use] – (some other title name), etc., etc. This may help it be more user friendly. -You dream it up – we’ll wire it up! -The above statement “you dream it up – we’ll wire it up!” This came about while my dad and I were out on a walk. We actually stopped walking and I wrote it down. I’m a pencil and paper guy. My dad had his cell phone and did a voice text message conversion and then tried to send it to me. I won because he didn’t have any signal… kind of funny! -There is more and more new technology being developed. It is very hard to keep up. We are seeing smaller and smaller devices, more and more touch screen, and even hand help projectors and motion sensing technology. We need to let adilas play in those realms. We do this by making it consumable! -We need to add some validation on dual salesperson assignments. Currently, an invoice, a customer, a quote may all be assigned to the same salesperson without any validation on who is the second or other salesperson. We do need to tighten this up. Once we do fix this – we also need to fix older records and existing data. -My dad is a great talent scout, coordinator, and go to guy. He is kind of like the character “sniff” (nose to the air) in the book “Who Moved My Cheese?”. That is awesome! -Things are changing rapidly – we need to plan for that. -I may only be able to document things, but at least they are written down. That may be my contribution! -My dad and I were talking – we know a guy who has a fancy Mustang (car) but he keeps it in an old cargo box. It is a gem (the car) in a box (old cargo trailer). Adilas is kind of like that right now! -On the standalone flex grid reports – Allow a show/hide option for the different columns. There may also be a value for show/hide “auto” which dynamically checks for which fields to show. Currently, the default is “auto”. If we add the other, it just adds to the flexibility of the tool. As a note, the current “auto” setting checks the lengths of the fields and looks for values greater than zero. If yes, it shows the value. -Marketing idea – Let people know about our ideas and tick list. Then allow then (the people and/or users) to help fund the projects. Kind of like a think tank or over a pre-order system. Maybe set a goal as far as people, interest level, or funding dollars. This could be per project. Coordinate these values to a level of “see a need, fill a need!” Good stuff! |
|
|
|
Adi 759 |
|
Custom Code - Label | 8/23/2013 |
Hey Kelly! I have inserted a screenshot below showing the barcode we need to be compliant with AZDHS (change bottom left to "Purchased" and bottom right to today's date) Hi Kelly, >> >> I wanted to see if it is possible to change the auto-populated data on the Adilas barcode generator. We have been changing Bottom Left to read "Purchased" and the Bottom Right to the current date. The only corp wide setting I saw was to change the default label size. How involved of a process (time and cost) would it be to make this change? >> >> Thanks! >> Caleb |
|
|
AU 1737 |
|
Daily Tasks | 8/23/2013 |
• Reviewing graphics for my brother. Answering emails and light tech support. • More graphic stuff with my brother. • Working on elements of time. Added a new link to the add/edit sub dates and time section. The new link allows you to add a new sub starting right where the last one left off. • Went in to town to work with my dad on tracking runners for the Bear 100 miles race. Making small tweaks to adilas and the sub dates and times feature within elements of time. 30 miles. • Went up to the University and talked with a gentleman in the Business department. We had a good sit down meeting and I tried to tell him what we are looking for as far as interns and help from the college. It takes a little bit of time even for people to understand where we are coming from. I really enjoy talking to people who will listen. One thing that I do too much of is trying to get out everything at once. I get so excited, I just want to tell them everything all at once. • Went back to Bridgerland to work with my dad more on tracking the Bear 100 runners. He is getting the flow down and it is fun to see him using adilas. • Recording notes, checking email, and checking in on different projects. • Went in to Smithfield to help my brother and give an adilas demo. The guy was interested in an inventory tracking system. He wants to do eCommerce, eBay, and merchant processing. Fun little demo. I then got some new video clips from my brother. He’s been working hard! |
|
|
AU 1758 |
|
Daily Ideas | 8/23/2013 |
-When giving a demo – keep it simple and don’t try to show them everything under the sun. Simple, fun, direct! -Pay Pal… eBay… We are going to need ways of connecting with both of these avenues and resources. Feeding data and values back and forth. These features would really help on the eCommerce side of things. |
|
|
AU 1738 |
|
Daily Tasks | 8/24/2013 |
• Previewing new YouTube videos that my brother gave me from the first adilas training event. Great stuff and my brother has done a great job on the training clips. He goes in and adds little call outs and text to help the users focus on small pieces; it really helps. If I go over something too quickly, he does a simple review of what I did and where I’m at. The other laptop is now crunching the clips so that we can pass them up to YouTube. • Recording notes and checking email. Just as a note, my email inbox has been exploding lately. That is good and bad. Good in that we are busy and bad in that usually means more busy times ahead. • Emails and tech support. Emails back and forth with an associate about customer needs for eCommerce. • New logos for two companies. • Working on a part number upload for a client. • Posted files online and modified some crop-wide settings. |
|
|
AU 1759 |
|
Daily Ideas | 8/24/2013 |
-We got a request from one of our associates to add a customer password field. -We may need an option where a customer could add themselves to a customer list without creating a shopping cart through eCommerce. That option could be really positive and/or a real pain just because it opens up a section without a purpose. But it may help to get and collect interested person’s information. |
|
|
AU 1739 |
|
Daily Tasks | 8/26/2013 |
• Small update about where we are heading using students, interns, and such. Posted the update online in the news and update page. • Emails and light tech support. • Recording notes about World Building concepts. Sent a small email to Brandon Mull (author) about using his five main points for a good story. They are: characters, relationships, trouble, decisions, and consequences. • Working on elements of time for recording the Bear 100 race with all of its people and racers. Small code tweaks. • Posted files and updated the update page about students and interns. |
|
|
AU 1760 |
|
Daily Ideas | 8/26/2013 |
-Recording notes about world building concepts. Saturday night into Sunday morning, I woke up due to a dream that I was having. I was fasting for help and trying to figure out how to best keep the balance between work, family, church, and personal. These notes may need to be adjusted slightly, I was scribbling on post-it notes as fast as I could. -3D printers – I was thinking about how a 3D printer takes an AutoCAD or technical drawing converts the document into a physical item by outputting ply plastics in the shape of the object. It is able to go in multiple directions such as sideways, up and down, and back and forth. Pretty cool! (Another idea – what about a number of robot arms all working together to build something.) -What if you put a bunch of 3D printers together all building the same output or project. I was thinking of relating these multiple 3D printers to the main 12 groups or system players inside the system. Imagine a number of 3D printers for customers, invoices, quotes, vendors, PO”s (purchase orders), users, stock/units, parts, elements of time, expanse/receipts, deposits, and user-maintained balance sheet items; Imagine these 3D printers working in tandem or working together as different things related together (called tie-in or relationships). -Use this concept of multiple 3D printers to help show world building concepts. -Blocking or rough layouts. Most projects start out with a general plan. As things develop, more and more details will be added. Say for example you wanted to “rough in” or “block” a car. It might look something like this (notebook sketch) – very loose and only represents a light form or blocking… -As more details are added or carved out, the more the “blocked out” item becomes what it needs to be. This is a process and maybe even a progression. For example: The blocked car could become: (sketch of a car progressing from a blocky outline to a more refined and then detailed and accessorized car). Almost like a Cub Scout pine wood derby car being made. -Think multiple systems playing together over time. -Each with their own functions and/or jobs. -Eventually it tells the story as you run it over time. -2 key components of “blocking” are: Catch and hold the data in a central location. Once you have those two things (the data and it is centralized) you could detail them out. -Include the adilas core concepts. They are: 1. Characters 2. Relationships 3. Trouble, Problems, Needs, and Goals 4. Decisions and Choices 5. Consequences (Cause and Effects) 6. Accountability 7. Objects and Data Over Time 8. Permissions and Settings 9. Systems 10. Vision and Future Developments 11. Tech, Tools, and Maintenance 12. The Story -By applying these concepts, you only limit yourself to what you can dream up or how deep or far off is your vision… keep it positive. Think potential! -Circle back around to goals, planning, output, and needs. These could even by dynamic and/or changing… sometimes that may be scary… but sometime that is what is needed. -The 5 story building concepts from Brandon Mull, author of “Fablehaven”, “Beyonders”, and “The Candy Shop Wars”. www.brandonmull.com/site/video-bestbook.html The main 5 are: characters, relationships, trouble, decisions, and consequences. I’d like to relate those to world building concepts for businesses. -What’s your story or what’s your world? -Spell it out without getting too wordy. Say 2-5 pages. -This concept “world building” is one of the things that makes adilas unique as its own system. -If you don’t want to play at this level, that’s okay. -These concepts are pioneering the future of business and how systems will track things. -Ours is a first generation, stable product. Eventually it will get leaped or leap frogged by a next generation product. We may even leap frog ourselves. This is just the nature of progression. It is part of the game. -Our goal is to share and take a small crack at “Tradition”. -This is a modern-day pioneering! -Solicit help and ideas – from different sources. -Dream it up – we’ll wire it up! -Balance is one of the goals. Pull it back to the goals. -King Benjamin, in the book of Mosiah, has some great advice about balance. See Mosiah 1-5 in the Book of Mormon. -Apply it if you know it! -Define the terms and concepts of world building – lightly. These are the 12 main core adilas concepts. -A different approach – may need to be taught differently! That is okay! -My dad’s ideas on transitioning and progress… “Moving Forward” and “Project Next”. |
|
|
|
Adi 749 |
|
Logan Training Curse | 8/27/2013 | August adilas training. | |
|
AU 1740 |
|
Daily Tasks | 8/27/2013 |
• Browsing around for stock/units and prep for class later today. • Working on the teacher/student project. Started adding the custom pages for tracking the student core data points. • Went into BATC for day one of the Logan training even for August. We had my sister and the lady that is going to do some graphic work for us in class. We also had a number of folks online using GoToMeeting. We started the morning going over stock/units. It was kind of a demo and of a teaching segment. It didn’t go over very smooth, in my mind, but we got the job done. One of the fun things was showing relationships and cause and effects. We spent all morning doing stock/units. After lunch, we did a wedding and catering demo. We added items, rentals, services, etc. We did some elements of time, some recipes (build and sell), and some basic carts. After that we jumped into a book store and setup some new DVD’s, training manuals, and subscriptions. We played with eCommerce and reoccurring invoices. Great class. 30 miles. • Emails and light tech support. |
|
|
|
AU 2143 |
|
Adilas 3 Day Training Notes - Logan | 8/27/2013 |
ADILAS LOGAN TRAINING - AUGUST 27-29 Day 1 - August 27th -Began with stock/serialized units. Class member’s husband is in the car dealership industry, so showing a little bit of that to start off the adilas training. -There are some really neat things you can do with serialized stock units and inventory.... lots of neat functionality... I can only imagine how incredibly helpful this would be for people in this industry to use adilas.... there is so much functionality with adilas, it is crazy! Now we just need to figure out the best ways for other people to see that and start using it - sales! -Adilas does custom documentation - so they can do any documenting that you need, the forms can be populated with all of your data in adilas - SO many powerful tools! -Stock units actually have huge pieces within the puzzle that they can hold and connect to. ****IDEA: What if we started doing something like a weekly demo. Maybe pick a time slot on a Friday or a time slot that changes weekly, 1-2 hours and Brandon or Steve or someone could do the demo. It could be open at a location nearby or even through GoToMeeting as well. We just need way more people at these trainings... we need people here so maybe if we could invite just tons of people to demos... we could get some greater interest. We need to get the word out. People only really come to adilas trainings if they use adilas, so we need a quick enough exposure that they are interested in talking more. Because most people cannot dedicate anything like the kind of time that our trainings are set for but they could probably squeeze out an hour for a demo & questions and answer session to see if they are even interested. We could pass out flyers with some catchy info and the times. Papa could record it and maybe from some of those sessions, we could get some little demo videos that people could distribute or users/sales people/anyone could use to do a special little video presentation demo of adilas. So maybe we need a super snazzy 1/4 sheet flyer and we need to get spreading the word abroad. People have to know about adilas and get some exposure to it or they can never use it. Even if we try to use the huge asset of the customer base already using adilas. If you could set up the demos, users could invite their friends to get on and watch or they could access some of the videos we create. Especially if we could get even a super great 10-15 min demo/overview of adilas and get it out to your users. They can show that and give personal experiences... but basically give them some more tools to help them market adilas for you, as well as incentivizing this process in some way. You might get some power users that realize that they really like sharing adilas and they could get some good stuff going.... Just some thoughts. **** ***Maybe we could even do short demos for each of the main "categories" or ways to use adilas... like a quick demo for CRM, POS, Inventory tracking, Backend accounting, etc., etc., etc. ***Maybe it would be cool to even do some little videos like we watched with Brandon Mull.... just short with him explaining important points and concepts.... like a "What isn't adilas?" video.... or some adilas overview videos ****Maybe papa needs to come with us to Colorado this next go around and film some demos, film some power users, film some commercials, get some goods on all of this great stuff we have going on. He and the mama could join us. -Stock units - you are able to add multiple subs and can track so many other related fields - a lot more info. **Once you set things up on operations - they start cascading themselves throughout the system... behind the scenes, it is already showing up in other places... we are feeding accounting automatically just by doing operations. -As you do your day to day transactions - accounting follows those actions -I think it is really constructive to the learning process, when we go back in and fix problems... or we didn't have what we needed for a specific goal, so that we can go back and work through the process of putting it in -All Data Is Live And Searchable - it is amazing how quickly the system can recover data, even year’s back, that is such a valuable asset! ***Chart out the normal flow of the business, understand their needs, etc. Then you can go in and help cater the best adilas fit. -We setup going through a wedding planning/catering service type business - it was really good, we got to practice with various elements including parts/inventory, PO's, recipes, elements of time -Adilas really comes alive for people when they finally relate it to themselves, or problems they have had in their own industry/business, or when they finally understand how helpful it is for their needs, it somehow seems to open so much more after that as to how helpful this could be for everyone. *Dream it up, plan it out, make it happen! -What you have in your adilas right now is available on eCommerce right now - that really is pretty amazing. Incredibly quick and cost effective and you have that functionality right now! Captions on the pictures especially (and searchable texts) are great to add because they can be found by search engines, etc. They show up on your descriptions on eCommerce. So when you learn how to play, there is so much you can do! And SO amazing that it tracks directly to your adilas and all of your inventory, real time, live data. AMAZING!!! -A good practice would be to check the history homepage every day when you pop into adilas. It would tell you things that you have ready like reoccurring invoices, or possibly elements of time you have scheduled, or target dates for things to sell, etc. -Great tools so you can adapt your web pricing and what you want to show or hide or if there is something that you would like to be priced differently for one or the other. |
|
|
AU 1655 |
|
Daily Tasks | 8/28/2013 | Day 2 Adilas Training in Logan Utah – demonstrating elements of time | |
|
AU 1741 |
|
Daily Tasks | 8/28/2013 |
• Recording notes from day 1 of the training event. Fixed a small bug that we found in training yesterday. Posted new files online. • Working on the add core data portion for the teacher and the teacher/student interface. Working on the add core data points page and how the custom flow for the flex grid will work. Making progress. • Went in to town for day two of adilas training. We covered some world building concepts and spent quite a bit of time on the adilas formula flyer and talking about mixing and blending of options. We have the formula: Results = Mix (Functions, Players, Concepts). We ended up talking about lots of different options and what is needed for each section. Lots of mixing and blending of features. We talked about customers, logs, statements, receivables, eCommerce, general web presence, elements of time, and flex grid tie-ins. Our day ended up having a light flavor of custom code and custom interfaces. We introduced the saying – “Dream it up, we’ll wire it up!”. The other thing that was kind fun was drawing traditional accounting vs. our objects and data over time model. Lots of dreams and concepts. We ended the day just talking about photos and random concepts. That was kind of fun as well. 30 miles. • Working on the school project for our teacher contact. • Finished up a rough version of the add core for students section. It was rough and kind of duct taped but we got it up and online. • Went over to the teacher’s home that we are working with and talked about the different teachers. A few teachers were there; they were excited and want the full program as soon as possible. Interestingly enough, they are wanting options to add things in bulk. I think that it is interesting… once you figure out a simple process; people want to do it faster and faster. Kind of interesting. Good meeting and I was glad that one of the teachers who is currently a client and has been to some of our trainings before was there, she is quite sharp. |
|
|
|
AU 2144 |
|
Adilas 3 Day Training Notes - Logan | 8/28/2013 |
Day 2 - August 28 -Today we are trying to focus on elements of time, customers, and flex grid type applications. -Telling the story adds validation and may be more important than just a list of numbers. If you have the back-up story, that gives validity to your numbers and your flow. The story is SO important. -Cause and effect - perpetuation, cascading effects, etc. -Systems: everything affects/effects everything else. Interconnectedness, how characters interact, play and associate with each other. -You want to categorize and detail things out so that you can know where money is coming and going from your P&L - so much better to have that on the invoicing side - because that shows such greater details. And you don't want to double play/book, you don't want to show the same things from invoices and deposits on your P&L - so defer those to invoices if possible b/c there is much greater detail. And it cuts down your time on the deposit side, so you don't have to try to detail it all out there - it is already on the invoice side, yeah, happy day! Law of Deference - deferring to the player that can hold the most detail &/or be the most effective for your business processes. -With interest that accrues - a good way to go might be to just make another quick invoice with interest expenses - it would be good to have that as an "item" if that happens often in your business. -Good teaching view when Brandon made the invoice really tiny and circled to show what part was the main, the line items and the payments... that was helpful, b/c not everyone knows that. -Tell the whole story... adilas and you are documenting everything going on... tell the story with all the details. -System history - pretty cool stuff! -Good read: "Who Moved My Cheese?" **We should do a little adilas overview - like some of the things Brandon was talking about how things are changing SO much and how we need to change along with that and how adilas has. I think it is really instructive to discuss some of the history and some of the tradition that holds things back or causes some tensions, etc., etc..... **Another really good description/instruction with the discussion of the more rigid traditional accounting idea w/adjustments, etc. vs. objects and data over time, with checkpoints/doors, holding places, advancing things letting it flex, pulling it back in - allows for time to occur as it does with this model. It would be great to get some graphical representations of these. -Tell the story, that is what everyone wants/needs and it is meant to do. ****WHOA! I feel like I have this realization every time I am in a training that adilas has SO much more potential than I even realize, than anyone in these trainings even realize! **Amazing potential with eCommerce and web presence... that you could expose whatever you wanted them to see if you have adilas customize it. That is amazing, so you could have them schedule themselves online, then you could prep inventory if you needed, or you could have them satisfy their own accounts online and pay their payments, etc. Such an incredible asset! Allows you to make smart money decisions, time decisions, and a predictive approach to your inventory and so forth. A good example here is mom's herb business and being able to see what people want and then you can make sure to have it when it comes. Super sweet stuff! ***You dream it up, adilas wires it up! ***"Dream it up, we'll wire it up!" -There is NO business that won't love and eat up that model!!! Huge, huge, huge!!! -On the tick list - to get a generated email or confirmation order, etc. Adilas is trying to shift to a just in time model as well, allowing their clients/customers to pay for the future development. **Adilas World - a mall for professionals - SO cool, what a great asset for customers and for professionals on adilas world. Already in concept - super cool stuff on the way. **"What doesn't adilas do?" ***IDEA: Adilas needs to become a just in time venue as well - just in time development as people are paying for that development and so forth, etc. **You can skin adilas not only just with a fun or custom interface but you can cut out all the unnecessary steps and speed up the process super-fast - linking it straight to your pieces with no problem. **Incredibly powerful engine with adilas - now custom look, feel and flow! Neat! -Cool little teaser interface - with the school data tracking --- API: Application Programming Interface -Flex grid - a front end programmer/user created database - wow, powerful! *We all loved the little school interface - I think it is so powerful, even though a lot of us can imagine how you could have different interfaces, it is SO powerful to see it! And it is so fun to explore, or see where some of the little "buttons" go, and to see how fast and efficient it is for their uses. -If you want to record the data, you can record the data. You can copy and paste full emails into the log notes, you can put what you want in there. -What is your goal? What are you trying/wanting to accomplish? These are critical questions to answer to help direct your flow, setup, etc. ***IDEA: from Tanya, maybe create a flow chart or rubric of sorts to help ascertain what a client needs. Maybe it's too dynamic to have a chart but maybe you could come up with something generic to help reps/consultants ask the right questions to help them get the best use out of adilas. Or really it could even be accessible to users, then they can self-assess what they want and then maybe have a direction to head - education/training. *Future: giving users the ability to be their own front end programmers. In-line customer work - future development. -Adilas is currently a bare bones model - which is great because that means you can dress it up basically any way you want. Powered by the adilas engine you can dress it up as you like it. -Can skin eCommerce with one of just a couple easy pages - skin it on the top side however you want to present it. Big giant buttons, easy, appealing interface, so many cool things. WOW! *Adilas has all of the data and lots of power - do you want it to look pretty & custom? Great - get a designer. Get a developer, get things how you want them. -Just like with other things - people don't know, what they don't know - adilas. There is SO much that is possible! UNLIMITED POSSIBILITIES!!! -Web people will understand how to pass data and variables to different places. -"Never let a crisis go to waste" – was said satirically today in reference to a quote from the past, but that truly is a valuable point. We hopefully don't let crises go to waste in our life - hopefully we change or adapt or flex or jump, shift whatever, so we don't get squished, so that we are better prepared for the future. Sometimes we try to do all we can to avoid a crisis in our life but they are a powerful means of change and can be positive in so many ways if we respond. Like Pres. Uchtdorf says that it is not our adversity but how we respond to it that creates our story or our destiny. |
|
|
AU 1742 |
|
Daily Tasks | 8/29/2013 |
• Went in to town for day three of the August adilas training. What a great session! We covered some things that we had never covered before. Our goal was banks, deposits, expense/receipts, and back-end accounting stuff. Well, it got pretty deep and we followed a ton of paths from start to finish. It was really fun. We did a whole day of training on the backend of “the story”. Tons of relationships and cause and effects. Great stuff. We covered expense/types, old school vs. new school account, flow on the map, what is automated – what is not, options, variables, objects and data over time, potential problems, known issues, disconnects, and vision for the future. I used my marker and drawing tools more during this training session than any other training session. It was almost to the overboard level. The whole thing deals with flow and cause and effect relations. We had good participation both in class and online. Tiring but awesome! 30 miles. • Working with my dad on his new video and digital video toys. We are hoping to record right to digital vs. tapes and analog technologies. Exciting stuff. |
|
|
AU 1761 |
|
Daily Ideas | 8/29/2013 |
-Small clean-up. These are notes from a phone call with Steve on 8/22/13. They got skipped over – running too fast (time wise). - We don’t care how much money other people make. We would love to create new jobs for people. Our goal is to be the processing and storage company. We want to keep expanding the backend and the main company. - On using students – we may want to get some Bios on the students. Any contribution to have a student help with a project is tax deductible. - Some of the future is custom reports, custom interfaces, etc. - Steve and I need to help manage the needs and the possible conflicts. - Contribute and community. |
|
|
|
AU 2145 |
|
Adilas 3 Day Training Notes - Logan | 8/29/2013 |
Day 3 - August 29 -Today we are mainly trying to focus on the back-end accounting functions -Money coming out of your bank - expenses - from various things like A/P, inventory, users, vendors, rei's, splits(A/P), etc. Which then shows up on your P&L and then also affects your balance sheet. -Money coming into your bank - deposits - from invoices, A/R, -Ideally - it is great to categorize your stuff before you get into adilas - set up your cans first thing, then it can really help to track things - like right here with expenses - what are our expense category and then if you have that all set up, you can stuff thing in the correct category -A lot of things are tracking automatically to the P&L and the B.S. but if you want it tracked out at a finer level you could set up more categories or something but again remember the Law of Deference - deferring to someone with more information for example deferring to the PO vs. the expense one line description. System maintained vs. user maintained balance sheet items - system tracks it or you need to add it. (User maintained B.S. item - like the company truck, a loan, things that adilas doesn't know what they are going to do. Other things they already map/track - system maintained) *Line it out in word or on paper - once you set it up and have a flow and goals it is amazing how much easier and focused it makes things -System maintained example - once a PO comes in with inventory your B.S. automatically increases with assets - it flows there, but also the A/P flows in there to your balance sheet so they are automatically flowing through. ----Financial flow calculator and worksheet - just an educational/instructive tool - does not save in the database, just a tool -The Income Statement (P&L) feeds the balance sheet with net profit - that is fed automatically from adilas - the connection between the two -Telling your story accurately and detailed creates your accounting ???'s for class - Requests for class questions - what happens to my sales tax - how and where does that effect things/end up? What happens with shipping? ---- Brandon did a great job covering sales tax. Freight - business preference and flow - out of gross profit or net profit, COGS vs. Expenses -6 accounting categories - Revenue, COGS, Expenses, Assets, Liabilities, Equity -They can automate things that are pretty standard, structured or a more rigid process.... but the minute people have great variability in the way they function, then you have to leave that more open and more maintained on the user level. It is still gathered and in its holding tank - to wherever it has advanced to and then you can go and advance it along the line as you need and are ready. -End of the month, you are going to have to manual/physical entry your sales tax - there are just too many variables to automate it... so you know you're going to spend a little time doing that. But all of the data is there and gathered and it is still probably at least 75% there and you just have to wrap it together and put it where you need it. *Real data on real time - not having to make all these adjustments -Old school accounting - deals with numbers; adilas accounting - deals with the story. -Balance sheet - a point in time (a single date, a snap shot in time) .... -P&L/Income statement - more of an accrual and over time, what is happening through the year and how it is continuing, rolls over your fiscal year as your profit and loss statement (the pulse). P&L feeds the balance sheet with its net profit - to the balance sheet. -Trying to teach cause and effect relationships. I cannot even believe how much easier it is tracking your accounting from the operations side... it helps you understand SO much more of what is actually happening! -Full record/transaction of everything that happens! **Possible new setting - talking with Cheryl... about getting a potential setting to distribute the cost of freight across however many items you have so that it can be added back into the cost of your items so that you can cover that cost and attribute it this way within your inventory. Probably not a high priority - right now mom just has some extra prep work to do on the PO side to figure out how much she needs to add to her items to make sure she is marking things up enough. -What tool do I need for the current job? *Adilas balances day by day by day.... traditionally a lot of accounting settings balance at the end of the month and often times there are huge disconnects that are really difficult to account for or making multiple adjustments. There seems to be a huge disconnect when accountants are looking for pennies in certain scenarios and have everything detailed out and then they can get to the end of the month and not account for some huge amount and then they just make an adjustment. That is a huge disconnect!!!! *Adilas - all in one, operations will lead and we will feed accounting according to what operations are and do. Adilas - incredible operations tracking that can take it to the accounting level. Not required but available. -If you play with adilas on the fairways and the greens (the way things automatically track through) they are making all these little connections for you. -A really great question about Gift Cards really illustrated the point to me again that understanding the story and how things flow really helps to know where you need to track or put something or what the next step is. So we need to add a user-maintained balance sheet item for our gift cards here - we needed to hold it as a liability. ***So cool that adilas will be moving to a model where they can ask - okay, who would like this? Who wants to help fund the creation of this project? -Gift Card tracking (lunch card tracking) - future development for adilas to track it out to the detailed level where it is automated and tracked to the balance sheet -Pre-paid items: you have to hold that as a liability at least until you have expirations or what not.... -Future of adilas - load balancing -Wanting to take adilas out to the serious balance sheet level? A/R, A/P - automated. Inventory & banks also automated and they are the 2 biggest keys you need to get in line to head to the Balance sheet level. Get the stuff that feeds in automatically going and feeding in and then you are ready to take it to that level. *Record the story! Record everything that you do! Record everything that you do physically and then if you need to do a little tiny bit of connecting, no problem. -The heart of adilas - objects and data over time - this tells the story -Great little analogy I like that Brandon made about the horse leading the cart - which we talk about over and over as being the most ideal way to get things done, really it is to move forward with any efficiency.... but the funny analogy he said was that when you have things set up in the right way, with the horse leading the cart, every once in a while the horse is going to poop and you have to do a little clean up. Over 75% of the accounting is already done just by leading with operations but every little bit there is some clean up - so there you can use your balance sheet and some other tools to clean up a little. It's just part of the game, but SO much easier at the point, to just scoop up a little poop, or do just a little bit of clean up and everything else is just rolling along and moving forward with ease and efficiency and we are prepared to scoop up any little items that we need. :) |
|
|
AU 1743 |
|
Daily Tasks | 8/30/2013 |
• On the phone with my brother going over graphics and future projects. • On the phone with Steve talking about training and upcoming projects and needs. Steve was very excited about getting help from interns and such. I took a whole page of notes. They will be recorded later on. It was fun to feel Steve’s excitement. Great phone call. • Recording notes from day three of the adilas training. • Worked on the custom pages for our teacher associate and the teacher/student interface. • Went in to town with my sister to go meet with a contact up at USU. • She and I talked about ideas for adilas all the way to our appointment. When we got there, he wasn’t there. So we chatted and talked with a student who was also waiting for Dave. As we chatted, he mentioned that he has done some sales, had some graphic experience, and may be interested in a job. He seemed like a nice kid. 30 miles. • After that my sister and I met with our contact we had intended to meet with. It kind of started out a little rough but go better. After a while he made a call to another professor who works in information systems. He hung around for a little bit and then left. My sister and I finished our visit with the other professor and his son. It was mostly concept and vision. At the end, he showed us a project that he was working on. It had a nice graphical feel and he was using some new technologies. It was nice to see. I can’t wait for adilas to have a fun skin on top of it. On the way home, my sister and I talked about how nobody gets adilas at first. It seems to take some time to get people into a new mind set. Education is huge! • Went over to Bridgerland to pick up the adilas laptop. Talked with dad a bit and then headed home. • Working with my brother on adilas video clips and such. I gave him a copy of the new August adilas training stuff. Once he gets done with the other footage, he will start on that section. • Previewing and checking out video footage from my brother. Started squeezing video clips. • More work on our teacher’s custom teacher/student project. The custom part deals with core data tracking. We have a page that grabs custom flex grid fields and builds a dynamic menu of sorts. Walking through each section line by line. Not very hard, it just takes time. |
|
|
AU 1762 |
|
Daily Ideas | 8/30/2013 |
-These are some notes from a phone call with Steve on 8/30/13. We were talking about future vision and how to help fund future projects inside of adilas. -This is “your adilas”! -Just in time custom code. -Login and check out the projects. Then circle back around. -Focus on community. -Maybe a custom label management tool. Be able to add custom labels to pages. Maybe use an icon instead of a link. Labels may need to be added on main pages and/or on line items. -How many pancakes on a plate? Basically, how many corporations or worlds on your server? -For eCommerce – We need to set the customer type behind the scenes instead of letting a customer choose that setting. This would be great corp-wide setting for eCommerce. -In training we heard two new words that will end up being used as adilas terminology. They are: Customer facing and frontend programmer. Both phrases came from the graphic associate at the training. Customer facing means which parts and pieces are open to your customers or the general public. A frontend programmer deals with settings, permissions, and interface vs. a backend programmer who deals with code and database stuff. -We would like to use elements of time to show and track funding on future projects. -We like to use the analogy of water turning into ice. This is how we track data and operations and accounting. (Water – slush – ice). What if we do the same things with ideas… say something like this… ideas – projects (potential) – development & project funding – tools & functions for adilas. Basically, we have tons of ideas, it would be cool to turn some of the ideas into projects, get project funding, do the development, and then roll out new tools and features. -Scientists do the same thing in a way… Scientific Method: ideas – hypotheses – theories – eventually leading to laws (not exactly sure of the order). -What if we helped our users (virtually community) to help in the idea, project, funding and development process. -Phase 1 of our development (meaning adilas as a company) – We thought it out, we planned it, we funded it, and finally rolled it out for use. -Phase 2 of our development (meaning adilas as a company) – We show the ideas and open it up to the world and then ask for help. Have people re-think it (multiple different topics and levels) and be involved. -Steve also mentioned “fracturing” or “breaking”. Sometimes we look at those as bad or unwanted. Maybe we need to build in order to break of fracture things. That is kind of scary but maybe breaking is or could be good. This topic is definitely scary, but maybe it is needed. Interesting concept! -Steve put it this way… “Expose the thin ice!” People want to see that. It seems kind of scary but maybe that will help in progression! -The whole thing comes back to just in time custom code or just in time code. Interesting! -Build and break, build and break, build and break! That is progress! |
|
|
AU 1744 |
|
Daily Tasks | 8/31/2013 |
• Working on the custom pages for the teacher/student interface for our teacher. Uploaded pages and setup her company online. Settings and flex grid fields. • Went over to the teacher’s house to help her get setup. We entered teachers, permissions, departments, and added students, and data points. Light training. • New logo for a company; got the graphic from my brother. |
|
|
AU 1763 |
|
Daily Ideas | 8/31/2013 |
-On training – Maybe put all the graphics on one page. These are graphics for concepts and theory. Another option is to make a page on adilasuniversity that I could go to and use for training. Another spot is under “objects & data over time” button on the map. That might be a good place for it. -I’d like to create some “get to know you” graphics for the main system groups, players, characters, and individuals. This is like a baseball trading and or a superhero profile sheet. I’d like to use this in training. As a note, I have sent an email to a graphic associate to see if she is interested in tackling this project. |
|