Search The Adilas.biz Developer's Notebook
Time Period:
Daily (enter the day you want to see)
Monthly
Custom Date Range to
Template Filter:
Color Code:
General Text Filter:

(use a plus "+" sign to separate search terms. ex: jack+jill+hill)
Sort Value:
 
Adilas.biz Developer's Notebook Report - 5/1/2013 to 5/31/2013 - (49)
Photos
Time Id Color Title/Caption Start Date   Notes
Click to view time photos.
AU 1202 Daily Tasks 5/1/2013   • Recording notes in notebook.
• Capturing tape 2 of the adilas training.
• Added some code to help skip the news and updates page for multiple logins per day. Now it will only show once per day.
• Watched the whole tape 2 from the February 2013 adilas training. It was a mixed demo of sorts.
• Working on eCommerce.
• Entering old expense/receipts.
• Finishing up a small video file from the adilas training session.
 
Click to view time photos.
AU 1203 Daily Tasks 5/2/2013   • Redoing videos with better audio clips. Meet the adilas team.
• On the phone with Steve. We talked about eCommerce, different rounds and releases, protection through sharing, education and training, and money stuff.
• Redoing videos with better audio. Uploaded new clips up to YouTube. Pushed up a small adilas demo clip to YouTube as well.
• Learning about different settings inside of YouTube. It tried to help me with some giggling, bouncing, and contrast. The output made the video clip look quite random and weird. I then started playing inside of Microsoft Movie Maker to help me get the right contrast and such. A little bit of a learning curve. Redoing a couple of video clips and even re-capturing one of the tapes.
• Reviewing more adilas class footage.
• On the phone with Steve talking about ideas for marketing adilas. We are headed to a full self-serve model that is consumable by tons of different people. The adilas mal could have spots for CPA’s, teachers, developers, artists (graphic guys), temps, consultants, reps, attorneys, hardware (sales), businesses, add on products and services, etc. If everybody could talk, share and sell to everybody… it would be pretty cool!
• On the phone with Steve talking about using adilas to help produce the adilas mall. We could use “customers” (main application type or player group). We could categorize by type. Allow photos, logs, etc. This will help pave the road for a future linked in community. We could even flex grid different “customers” together if we wanted.
 
Click to view time photos.
AU 1229 Daily Ideas 5/2/2013   Notes and brainstorming with Steve about marketing and direction:
- If we only charged for data processing and storage, they (meaning our clients) could technically manage and control their fee structure. Let them get at the data. Let them see what they have and let them manage it.
- We need to open the adilas mall. This could be for CPA’s, Attorney’s, Developers, graphic artists, reps, consultants, trainers, etc. We need this pretty quick.
- Each database could be a single corp or it could be multi corps. Think of pancakes on a plate. Is it a stack of 1, 5, 10, 100, etc.???
- All Data Is Live And Searchable – we store and process your data… Our little saying has three parts.
o All Data – everything or a complete package
o Is Live – living and all tied in
o And Searchable – what do you want and how do you want it?

o Focus on this little saying (above)

- How could we ride on top of what already exists? Newtek allows for a shared environment already… what if we talked with them and then did similar things or used their backbone….
- What about a small fee to be part of the adilas mall. Maybe $5. Adilas could keep 20% and then pay the other 80% to one of our associates or something like that.
- Lots of businesses and individuals may want to be part of the adilas mall. Allow them to create their own profile.
- “Pave the road!” – once it gets paved, more and more people will use it!
- We could use adilas customers (main application type on system player group) and allow people to add a profile. We could use the customer types to help control what category each person or business fits in to.
- They could then use logs, photos, normal customer fields, contacts, etc. We could also allow flex grid tie-ins to be uses to connect different profiles. This could be friends, buddies, partners, recommendations, etc.
- Allow the adilas community to thrive and help each other out.
- To help with visual stuff… what if we allowed photos to be tied to part categories and customer types.
- Maybe tie the adilas mall to the help files (as a link). Then allow users to shop for what they want and need.
- People who want to create a custom shopping cart could basically put a small HTML form into any page and then pass that data right to the add to cart page. They could even add shipping if needed as a hidden form field.
- Small time eCommerce could be a great little niche area for adilas users.
 
Click to view time photos.
AU 2282 Brainstorming - Adilas Mall & Adilas Self Service 5/2/2013   - By managing their own data (meaning customer), they could technically control their fee structure. Let them get at it; let them see it; let them manage it.
- We need the adilas mall (adilas world – 6/4/13) – CPA’s, Attorney, developers, reps, consultants, we need this pretty quick!
- Each database could be a single corp or it could be multi-corps
- All Data Is Live And Searchable
o We store and process your data
- How could we ride on top of what already exists? - Newtek allows for a shared environment already… what if we talked with them and then did similar things or used their backbone…
- What about a small fee to be part of the adilas mall. (adilas world – 6/4/13)
- Businesses and business profile – “pave the road!!!”
- Use adilas customers (group or players) and allow people to add a profile. We could control the customer types, add photos, and logs (mini tweets).
o We could use the flex grid to link partners together if needed.
- Tie photos to types – customer and parts – open up the visual options.
- Maybe tie the adilas mall to the help files (a link) create a new folder called “mall” (“world” 6/4/13)
 
Click to view time photos.
AU 1204 Daily Tasks 5/3/2013   • Small little tweak to the LTF website. Added a new link to the links page.
• Phone call to a contact of team Utah.
• Recording notes about marketing and creating the adilas mall.
• Working on eCommerce. Added a new setting to help with checking for quantities on hand before showing add to cart options.
• Working on eCommerce. Light tweaks to help with navigation and look and feel.
 
Click to view time photos.
AU 1205 Daily Tasks 5/4/2013   • Emails and tech support for photos and scans.
• Working on eCommerce and actually building the shopping cart.
• Brainstorming on more settings.
• Working on eCommerce. Reviewing notes and brainstorming ideas.
• Added eight more setting for eCommerce. They were for button text, shipping, etc.
 
Click to view time photos.
AU 1230 Daily Ideas 5/4/2013   -New buzz words… software as a service (saas), Private Cloud, Hosted, or on-premise. These are all different solution types.
 
Click to view time photos.
AU 2283 Brainstorming & To-Do's 5/4/2013   - Possible new settings
o “Save As Quote” – “Submit – Save As Quote”
o “Submit Online Order” – “Submit – Place Order”
o “Final Submit” – “Submit – Finalize Checkout”
o “Create” or “Confirm and Process”
o “Final Checkout” – “Process checkout”
o “Buy now”, “Yes, Let’s do it!”
- Check for blank values
- Shipping (web shipping info)
- Re-read the brainstorming pages (elements of time) for eCommerce.
- Email notification or text message notification.
- Allow simple form scope submission
o This could be a simple way to allow custom shopping carts
- Document the process, the pages, etc. This includes the new add to cart page, view cart, login pages, etc.
- Valid login fields for the remote customer sign in:
 
Click to view time photos.
AU 1206 Daily Tasks 5/6/2013   • Added a new logo for a company.
• Working on the new May training flyer for the 3 day training course. Posted files online.
• Sent out a number of emails dealing with training and upcoming classes.
• Bank stuff.
• Tech support, emails, and phone calls.
• On the phone with Steve talking about eCommerce and other client needs. We need to add a new silver permission that hides all costs. We are having some managers ask for that.
 
Click to view time photos.
AU 1231 Daily Ideas 5/6/2013   -We need a new permission to help hide all costs from salespersons. This is a manager thing. I personally think it helps people to know what things cost but it makes certain managers uneasy.
-We have had a number of requests to see sales by customer type. This is possible but not yet included by default. Basically, a customer is connected to an invoice and a customer type is connected to a customer. It just needs to go out another level deeper.
 
Click to view time photos.
AU 1207 Daily Tasks 5/7/2013   • Emails and tech support.
• New logo for a company.
• Checking out a patient upload file and providing a quote.
• Tech support.
• Patient upload for a company.
• On the phone with a consultant helping her get setup and her user accounts setup correctly. She had a number of different logins and wanted them all under the same username and password. Other light tech support.
• Add a new permission for hiding part costs on invoices.
• Went back and forth between Richmond and Smithfield twice. I went and had a meeting with my brother. We went up the canyon and talked about being an adilas rep. I ended up offering him a job to help do video editing and helping get the adilas training footage up and online. He seems very excited and has plenty of skills. He has already made his own music videos. The adilas stuff should be a snack. I’m excited to see what he comes up with. I gave him a budget of 100 hours at $15/hour. 20 miles.
• Working on the new hide cost and profit permission.
 
Click to view time photos.
AU 1208 Daily Tasks 5/8/2013   • Created a couple of helper graphics to help my brother with some tips on Microsoft Movie Maker. Sent them to him via email.
• Did a GoToMeeting demo with my uncle and his son, my cousin. We talked about adilas and what we’ve done and created. Nice little demo.
• Writing an email with training info to my cousin.
• Online bill payments for company credit card.
• Working on the hide costs and profit permission.
 
Click to view time photos.
AU 1209 Daily Tasks 5/9/2013   • Went out to meet with a contact and do an adilas demo. He tracks restoration jobs and weed control data. These are private and government projects that are doing large restoration projects. He has a home grown system that has four to five main pieces feeding into a large database. He then tries to pull data out of the database and show it to his customer and/or staff. His pain was in the marrying of all the different systems and then trying to pull data back with nominal web background (coding knowledge). I showed him elements of time, dynamic pages and search options, and some code basics. It ended up being more of a consulting meeting vs. an adilas demo but I used adilas as my supporting documentation and real life example of what was possible. Kind of a fun angle for using adilas as a working example of options and theory. 20 miles.
• Recording notes and monitoring remote servers.
• Working on eCommerce. Implementing new settings for cart options and flow. Started on the add to cart.
• Went in to Logan for a couple of meetings. Stopped by the bank and talked with a banker about ACH debit transactions. I then went to Bridgerland to meet with my dad and contact he had been talking to. We had a multi hour training session. It started out with just my dad and a couple. We talked theory, history, and light inventory. Another contact then joined us and we talked questions and answers for quite some time. This contact is a buyer for a sporting good warehouse of sorts. Great meeting and great energy. The couple was really excited. 20 miles.
 
Click to view time photos.
AU 1232 Daily Ideas 5/9/2013   -If we need to, we could offer a private cloud option which would be a dedicated box. It could be the $997 per month fee. We would then have to figure out who pays for and owns the server. I would say they own the server, the domain name, and the SSL. They would be required to run their own PCI Compliance stuff. The $997 fee would be for the adilas code and database (application). Maybe even let them people choose where they want it hosted at. As long as it is able to run ColdFusion and MySQL, it could technically be anywhere in the world. This may or may not work with updates and access to the system. Basically, it is just an idea right now and needs to be though out more.
 
Click to view time photos.
AU 1210 Daily Tasks 5/10/2013   • Emails, tech support, phone calls, recording notes, and bank stuff. Got tons of documents ready for the bank, including tax returns, bank statements and bios on Steve and I.
• Went down to Salt Lake City to meet with a contact about LTF and options that we have with what we have done and what may be possible. We met and chatted and then I showed him the DVD loop and the actual app (product). He was quite impressed and we talked options for quite some time. The meeting was about 2 hours. 180 miles.
 
Click to view time photos.
AU 1233 Daily Ideas 5/10/2013   Ideas for parts:
• Group or Player Level – default “parts”
o Category Level – default “part category” (many - unlimited)
* Item Level – default “part number” (many - unlimited)
In real life:
• Group or Player Level
o Category A
* Item 1
* Item 2
* Item 3
* Item 4
o Category B
* Item 5
* Item 6
(Small worksheet – category, item, fill in the boxes to indicate a category or a part or item)
-It would be really awesome to turn adilas university into a 501©3 non-profit. We could then use the adilas eCommerce section to accept donations to help fund the project. That may be a great way to help pay teachers, servers, custom code, play sites, etc.
-While in Salt Lake I had the thought about schools and lunch cards and keeping track of who owes what and how much money is in on their cards or on their account. This is the same exact thing as a customer loyalty card or a gift card. They are the same concepts, just different audiences or usages.
-LTF… Idea from contact in Salt Lake. Put LTF up on a Google drive or make it downloadable right from the website. All other hard copies would then be collectors’ items or sorts. He also mentioned Google drive as a way to get a copy of LTF out to his guys around the states. What a great idea, thanks!
-On the same note, I am and was so focused on the physical product. I haven’t even been thinking about a full, as is, original download of the existing product. I could make a mac version and a PC version. Make a couple zip files and call it good.
-As a different note, I was sitting in front of the Utah State Capitol building… I love to look at history and what great people have done. It is inspiring to me!
-I just ordered some pizza and I’m sitting outside. My whole way home from Salt Lake I’ve been driving on the old Hwy 89. I did this on purpose to get off of the Interstate. I’ve been going through city after city, town after town, and I’ve seen tons of small businesses. I kept thinking adilas could help them, and them, and them.
-I then got to thinking that every business could actually benefit from the concepts that we are using inside of adilas. Even the biggest businesses are still using the old double entry accounting model. There is some pain there and it is general among every business.
-I keep thinking… How could we help everybody to run better, smoother, and more efficient? The answer that keeps running through my head is “the concepts”. The adilas code is one of thousands of possible options, but the underlying concepts are where the real value lies.
-How do you teach concepts so that people get it and start using that as an option? Well, somebody has to teach it, explain it, show it, and even map it out. It needs to go basic to hardcore tech. Different people will understand and play at different levels.
-I’m thinking that adilas university is and will be part of that answer. Help teach people in an organized yet dynamic way. Make it progression based, yet nonlinear. Basically, an LTF (Learn to Freeride) project for teaching business, concepts, theory, flow, cause and effect, etc. Maybe LTF was a prep step for this monster project…
 
Click to view time photos.
AU 1211 Daily Tasks 5/11/2013   • Emails, tech support, and bank stuff.
• Research on upgrading servers to bigger faster boxes.
• Recording notes in my notebook.
• Emails and recording more notes. Objects and data overtime.
• Working on some tweaks to the adilas university logo and site. Also worked with my brother on some video stuff.
• Changed the adilasuniversity.biz site and listed our first online class dealing with corp-wide settings. Adilas university will officially open on May 16th of 2013. Yee haw!
 
Click to view time photos.
AU 1234 Daily Ideas 5/11/2013   -I woke up at 4:00 am dreaming about how data was organized over time. It felt like something was missing from my dream but I wanted to record what I scribbled on some post-it notes before going back to bed.
When I say “calendar”, I was thinking dates and times in general. Not specifically a calendar application. Anyways, I was trying to organize the different pieces into a calendar type format. This was clear at the players and sub players level. In other words, clear at the database table level. Imaging 200+ (two hundred plus) tables with data, objects, and relations all playing in time to complete the whole. Here are some of my notes…
-It starts with objects and data overtime
- This helps tell the story or the history
o As this happens “relationships” are created and formed.
* This is the who, what, where, when, how long, how much, how many, etc. (aka details)
o The blocks of time then sub divide into smaller pieces. For example: Days, hours, minutes, and seconds.
* These time blocks then divide into the 200+ tables were data is stored. This is how relationships are formed in a digital world.
* They can be grouped by day (default) or by smaller blocks if needed.
(Small diagram: in notebook)
(This is where the objects, data and relationships go or end up. This tiny square is where you could have your 200+ database tables that hold the data.)
Notes from a dream about organizing data over time. (Continued)
-Anyways, I was seeing the database tables holding data clear down at the second level. This is kind of deep but it felt like the best spot for it. Prior to this dream, I’ve always envisioned the database at the day or daily level. However, it feels like it needs to go even deeper. Basically, at the day level, there are too many variables (too big of a time span). If you took it clear down to the seconds you could always go back up and sum things up by the minute, hour, day, month, year, etc.
-If you take things clear down to the second level, without freaking out or overwhelming, your users, you get?
- This produces the story, the history, and the ability to track objects and data over time.
- Time becomes the constant piece to ride on.
- It comes back to – all data is live and searchable.
- This also allows for groups, edits, changes, flex, corrections, etc.
- It allows us to convert data (virtual water) water-slush-snow-ice.
- This also creates the “life cycle”
-It circles back to tracking objects and data over time.
-Enter once; use it over and over again.
-If the data is correct, let it flow!
-If a change is needed, make the change, lock it down, and let it flow!
-All data is live and searchable.
-I keep thinking that it would be cool if we could run reports off of archived values. However, every time I go there, I can see a problem if anything changes in the past. It has a cause and effect relationship going forward. It basically makes it so that you can’t rely on the archived values. Maybe the secret is to start with the just in time calculation and help speed up the database processing and indexing.
-Numeric dates could help out a ton. You could index the main integer part and then store the decimal part as a separate value. The integer part is the day; the decimal part is the hours, minutes, and seconds.
-The default group would be on the day or integer level. If the user needed to go deeper they could get into the decimal part. It would still exist but the default would be on the day or integer level.
-Either way, if using a numeric date value, make sure to separate it into two different fields. Index the integer and just store the decimal part. If no decimal is needed, just use 0 (zero).
-I had some fun ideas about adilas university the other day. It was kind of a cross between adilas and LTF and using a non-linear Flash type interface. I also thought about simple HTML Frames, sub menus, etc.
-Some diagrams in the notebook:
-each link from the simple page would load in a new menu on the frame set.
-a click from the frame-set menu would put a video into the player.
-Another idea was an app of sorts that uses the screen area to show everything. Unlike LTF that had a skin and a player, this little app would be just a player and then skin itself on top of the player section. Basically a way to conserve space. This would be nice for mobile stuff. (Player with a small wrapper) (Player with a menu)
 
Click to view time photos.
AU 1212 Daily Tasks 5/13/2013   • Customer migration for a company.
• On the phone with a contact from Newtek talking about server upgrades and options.
• More server stuff.
• On the phone with Steve. We talked about funding and upcoming projects. We talked quite a bit about servers and how best to grow and expand our current model. We also talked quite a bit about byproducts that are created as part of the adilas application. Some of the byproducts may actually have more than the original monthly fee structure. We also talked about eCommerce and some of the future options there. Good stuff.
• Tech support, emails, and research on servers and migrations.
• Working on tech specs for the server upgrade. Recording notes and looking up old configuration settings. Research on upgrading versions of MySQL databases.
 
Click to view time photos.
AU 1235 Daily Ideas 5/13/2013   -On round two (2) of elements of time… we need to include job costing. This could be a section on the actual element of time or it could be on the invoices, deposits, and expense/receipt line items. If we did it that way, we could just roll call them over to the element of time to show the job costing.
-We had a request to limit customer based on assigned salespersons. That sounds good but I can foresee that it would actually create possible duplicate records. There are both pros and cons to that idea.
 
Click to view time photos.
AU 1213 Daily Tasks 5/14/2013   • Customer migration for a company out of Texas. Round two. Pulling data off of spreadsheet and importing into live database tables.
• Invoiced for a company and tried to charge their card. Came back as do not honor. Small email to let them know what is going on.
• Working on eCommerce add to cart. Lots of copying and posting and checking form values.
• Working on eCommerce and the add to cart page.
• Went into town to do an adilas demo. Put some files in the safe deposit box. Stopped by and chatted with a contact at the Logan bank. Then went to Bridgerland for the adilas demo. There were four people plus my Dad and I. There was a computer tech guy, a couple and another contact. One of them has a small repair shop; he wanted to see quotes, customer, and invoices. The couple just wanted a small overview. Great meeting and it was fun to interact with the people. 20 miles.
 
Click to view time photos.
AU 1236 Daily Ideas 5/14/2013   -If we are talking roll call and cross tying main players together… it sure would be nice to cross tie invoices, deposits, expense/receipts (line items), and PO’s to user-maintained balance sheet items. This would help the roll call… on both sides of the fence. Tell the story and create the relationships.
-On web settings per part number… We may need a field that indicates whether or not partial product quantities are allowed. For example: say you have a product that is an each or quantity of 1. What happens if the customer wants to buy 1.5, 1.25, 0.75, etc. That creates a problem. At the same point, we have other products that allow partials. Say you have a product that is sold by the ounce or by the pound. Decimals are needed at that level.
-Maybe we could check for “each” (unit of measure) and then force to an integer or non-decimal value.
 
Click to view time photos.
AU 1214 Daily Tasks 5/15/2013   • On the phone with Steve. We talked quite a bit about his (Steve’s) market plan. We would like to focus on the Denver, CO area. We would also like to focus on computer people and people who already know business and bookkeeping. The people who have computer, business or bookkeeping skills are able to hit the ground running. We can help train others, but it takes more work. Steve would also like to teach some classes that focus on business and steps to success in business. This will help us show what we can do for your business or company. We also talked about different pricing models and doing a standard shared cloud, semi-private cloud, and full private cloud models. This deals with how many other companies are on the same server. We talked a lot about how we, as a company, need to pull back a level and coordinate things at the server level. We talked about custom code and even pushing our existing structure to the next levels. This would be in-line custom code, show/hide fields, defaults, sort orders, naming conventions, flow, and even custom database tables, and an API to help let our users consume things however they want. Great stuff! The other thing we talked about was including some other associates in our next team meeting. We talked about possible dates in July for our next major team meeting.
• On the phone with a client. They are looking for some help or training. They have been running on a minimal set of skills. All they need is some help and training to get going in the right direction.
• Emails and tech support.
• Bank stuff, emails, and recording hours.
• Light brainstorming on ideas for new silver permissions.
• Added the new user permission to the news and updates page. It is the hide costs and profit permission.
• Signing off on the hide costs and profits permission.
• Working on eCommerce. Showing the cart or the web view cart page.
 
Click to view time photos.
AU 1237 Daily Ideas 5/15/2013   -One of adilas’ biggest assets is the ability to track all of your data.
-New silver permissions…
- Limit customers per salesperson (basic or one-to-many)
- Limit users to locations (basic (single, assigned, per user, settings) or one-to-many)
- Add “view only” permissions for all main sections. Invoices, parts, quotes, deposits, expense/receipts, balance sheet items, etc.
- Smaller version of the sales and profit reports. Just the sales part. Take off the costs and profits. It may need a new name as it is or will be missing part of the report.
 
Click to view time photos.
AU 1215 Daily Tasks 5/16/2013   • Doing some research between XML and JSON. XML stands for Extensible Markup Language and JSON stands for Java Script Object Notation. Anyway, I was doing some research to determine what type of results would be best for the adilas API (Application Programming Interface). It appears that the JSON (pronounced Jason) notation may end up being the easiest for us to implement and use. There is less of a conversion and it is a lighter weight data-interchange. My friend gave me a call last night and mentioned it. He is very tech savvy and often has his nose to the wind and what is cutting edge. Good stuff.
• Tech support and emails. Had a request to create a data file and FTP the file to a remote server on a daily basis.
• Working on eCommerce files. Added view cart links to all pages.
• eCommerce - Added a thank you graphic.
• Went over to my brother’s house and worked with him on videos and switching from Windows Movie Maker to Vegas video. I think it will be much better. 10 miles.
• Working on eCommerce and the update cart page.
• Playing with ColdFusion Structures and going between JSON (Java Script Object Notation) and ColdFusion. That is superfast. I can see a ton of great options using this type of data-interchange. Good stuff.
 
Click to view time photos.
AU 1216 Daily Tasks 5/17/2013   • Brainstorming on eCommerce and expected flow and functions. Rereading old brainstorming notes and ideas about eCommerce and the adilas API (application programming interface). Good stuff.
• On the phone with Steve. We reset the server and then watched it come up. It kind of struggled coming back up. We then talked about possible using JSON as our API data-interchange language. We did a quick GoToMeeting and I showed Steve a demo of where we are at with eCommerce. More good stuff to come.
• Research on platform and application dynamics.
• Working on eCommerce. Working on the update cart logic. Ended up doing a light brainstorm on tracking data over time. See the next couple of pages.
• Back on eCommerce. Update cart logic.
 
Click to view time photos.
AU 1238 Daily Ideas 5/17/2013   -What if you could run the balance sheet by days? How about by hours? How about by minute? How about by seconds? That should be plenty deep. The goal is to balance by date (day) but we may need smaller increments to help us find out what is going on. Things might by flexing in and out at different times. Eventually things come back together. We have used a diagram like this: (diagram in notebook – operations are on the top, accounting is on the bottom – shows to lines that are static and rigid, then shows two lines that bubble out and come back to parallel – dynamic and flexible.
The goal is to eventually have them match up or be equal. In a real world environment things are dynamic and flexible. Why not match or mimic that type of world. If things are tracked down to the second, that would allow for things to be both dynamic and flexible. Our little model (diagram above) might be too simple. What if it actually looked like this: (sketch in notebook)
Life cycle with check points… operations is still on the top, accounting is still on the bottom. What if it comes back together for certain check points or at certain times. Then depending on what happens over time, it may break apart again only to come back together at the next check point.
Then you could date and flag the checkpoints as needed.
-On a different note, it you pull back far enough, a wavy line can look smooth. For example: (sketches in notebook) …. Pretend these are the same lines just looking at them from different levels or perspectives. For example: by second, by minute, by hour, by day, by week, by month, by year.
-Dealing with tracking data over time to the second, minute, hour, and day levels…
-By the time you get to the day, week, month, and year levels, you are seeing the big picture.
-Imagine grass on your lawn. What does it look like? That depends on your level or perspective.
(Sketches – pretend this is the same grass at different levels: ant – seconds, grasshopper – minutes, cat – hours, person – days, birds in the sky – weeks, plane flying over a city – months.)
 
Click to view time photos.
AU 2284 Brainstorming - eCommerce & Customer Login Portal 5/17/2013   eCommerce & Customer Login Portal:
Buttons:
- Clear cart
- Update cart
- Sign in (my account)
- Checkout (continue – proceed to secure checkout)
- Quote/Order/Checkout
- Quote/Order/Checkout
Quotes:
- Customer
- Then submit
Order:
- Customer
- Pickup notes
- Then submit
Invoices:
- Customer
- Shipping (need a flag, shipping applied – yes, no, how much
- Billing
- Payment
- Special notes
- Review
- Then submit
Other sketches – see scan in photo gallery

eCommerce & Customer Login Portal:
- Create a login portal section. If the company allows items to be seen online, show links to new inventory search. If not, make the portal a standalone section.
- Once logged in store the customer data. Use as filter, cart stuff, etc.
- Allow them to update addresses, phone #’s, etc. Put it back on the source or the actual customer.
- Allow for:
o Bill pay
o Look at payables
o Print invoices
o See histories
o Create statements
o Auto login from outside sources through a mix of corp, cust, and invoice. Check against a hash value. Allow on invoice and/or quotes.
- On the history homepage. Show new web quotes, orders, and invoices. Provide a drill-down to get to these orders. It would be cool if we had invoice classifications in place. If not, we will need to search internal notes.
- Provide quick links to get to new web changes. Provide all of these from one page:
o New quotes
o New customers
o New orders
o New invoices
o New statements
o New payments
- Add a new permission to view web activity (web activity reports)
- Link from the web presence page to the new web activity page. Maybe just beef up that existing permission or add to it. We may need two different permissions.
- Add a crumb trail on the checkout process. Maybe like a vehicle checkout process.
- Allow restore to cart for customers view of older invoices. Allow for duplicate invoices as well. All from within the login portal.
 
Click to view time photos.
AU 1217 Daily Tasks 5/18/2013   • Bank stuff.
• More bank stuff. Scans and new balance sheet item to help with cash advances and project payments.
• Working in eCommerce. Reading over new pages.
 
Click to view time photos.
AU 1239 Daily Ideas 5/18/2013   -We’ve had some requests to be able to limit user logins and user timecards from certain IP addresses. We are already catching the IP addresses, we just aren’t limiting by IP addresses.
-We are going to need all 50 states ready for payroll very soon. We are also going to need better options for paperwork, forms, and reports.
 
Click to view time photos.
AU 1218 Daily Tasks 5/20/2013   • Emails, tech support, and following up on the new dedicated server that we ordered. Also spent some time brainstorming on hybrid parts that could only be used one time each. See note on other page for details.
• Working on eCommerce. Reading over page and current code light brainstorming on backend flow for eCommerce.
• Working on eCommerce and the customer sign in and web portal.
• On the phone with Steve. We talked about eCommerce settings, options, and flow. We talked quite a bit about unique items and one time only usage. We also talked about personal settings, in-line custom code, and marrying the two options together. We also talked about mapping financials to the second (time) level. Good stuff and more to come.
• Reviewing notes and ordering some POS supplies for the Logan training sessions.
 
Click to view time photos.
AU 1240 Daily Ideas 5/20/2013   -I would love to add the key word “auto” to the parts department. This would auto create a part number by using the id number.
-The keyword “auto” could also be used on the barcode fields for flex grid, my cart favorite buttons, and recipes. Maybe add a small tag to help us know what it is. Example: f19976 (flex grid #9976) of FAV 320 (cart favorite button #320) or RB14 (recipe/build 14).
-It may also be cool if a part number could be set as a one-time usage. Basically, once used it removes itself from the active pile. There may be pros and cons to this.
-If we did use a one-time usage option on parts. It might be nice to show “sold” instead of out of stock on the web or eCommerce site.
-It may be worth our time to look into a cross between a big ticket stock/unit and a part number. We may need something in between. Tracked one on one but entered and sold in bulk. Some sort of hybrid item.
-If we did a hybrid item, it could be entered into the part department with an auto part numbers and then the reference number acting like a generic part number. That way we could search by either. This could also be part of the onetime usage flag.
-So to recap, assuming that all of this was done. Say you sold tons of items and they are very similar yet unique. They are not quite a stock/unit and not quite a part that goes into a bin or bucket. What it we used the parts department, had the system create a unique part number, used the reference field as a generic part number (same for tons of items) and then used “auto” for the barcode value. This would create unique items with the same or similar reference numbers. So, it I wanted all of my “bronze bear sculptures” I could search the reference number for “bear” or the barcode to get a specific item. I could then use a flag to flag the item so that it could only be used one. Thus, using the key word “auto” and a one-time usage flag, we could technically show tons of items that are similar yet unique. They each could be used once, have their own photos, prices, descriptions, and unique part numbers. We could even automate clean-up functions that once they get sold, they show the sold status.
-I could see a usage for this in consignment shops, hand crafted items, or custom build shops. Each item is unique and needs to be treated by itself, yet sold in bulk. Each item also needs to be tracked coming in, while in inventory, only sold once, and then paid for or whatever the final process is. If the user doesn’t want to make them all individuals, they could just run it as a normal part that gets put on the shelf or into a bin or bucket.
-From Post-it note: auto part numbers and auto one time usage options – basically, when used, they inactivate themselves.
-At some point, we may need some bulk management tools for parts. Hide/show, web status, price changes (already done) and other bulk options.
-Idea for in-line custom code… what if you could go in and detail out functionality according to types, functions, locations, and pre-filtered searches. Basically, I only want you to see this and this. You will never see this and this, and I only want you to be able to interact with this and this. This could be functions: add, edit, search, verify, lock, etc. This could be by types: only these time templates, only these PO types, only these invoice types, only these customer types, only these expense types. This could also be pre-set or filtered reports. For example: I only get to see sales from this location. I only get to see expenses from this bank or this vendor or this expense type. These are all options and criteria of sorts. Wouldn’t it be cool if we could allow companies the option to control these pieces using in-line custom code. I think this would be awesome.
-Some of the ideas for in-line custom code are also part of the personal settings that may be applied per page. What if we married the two together. Personal settings could be updated and changed by a user. In-line custom code could be set by an administrator and could over rule or update personal settings. Basically, the user has control unless a setting is set by an admin and then set to a locked status. If an admin person makes a setting and doesn’t lock it down, that just becomes a default and the user could go in and change things as needed. Once something gets set and locked down by admin, it becomes un-editable by the user. It would only be editable by an admin level user. This could be two birds with one stone. AS a side note… some of the settings may be used as a one-to-many depending on the page and what it does. Interesting twist on personal settings.
-It sure would be nice to have the main system player’s home pages in a graphical format. Show the options, flow, permissions, settings, in-line custom code, special reports, and training specific to the task at hand. Be it: invoice homepage, parts homepage, deposit homepage, vendors homepage, etc.
-I’m starting to see a big need for the customer gift cards, in-store credit and loyalty points. Also being able to re-load, add, subtract, use, etc.
 
Click to view time photos.
AU 2285 Brainstorming - eCommerce & eCommerce Flow 5/20/2013   eCommerce & flow: eCommerce
Sketches – see scan in photo gallery
Customer Portal:
- Standalone or as part of the checkout process
- Mode for the sign in:
o Invoice
o Quote
o Order
o Blank
o Basic
o If the mode is note blank, re-route to either a show page or some type of review.
Customer:
- Main is billing
- Secondary is shipping “Ship To”
- When prompted… show details but make them go deeper to edit something
- What about customer types? Let the user choose and check for just one. If yes, default to that.
Check the whole process with and without navigation turned on.
 
Click to view time photos.
AU 1219 Daily Tasks 5/21/2013   • Downloading the newest version of ColdFusion. Light online research.
• Installing ColdFusion 10. Light browsing and testing on files and updating code to work with the new server.
• Reading entries in my notebook.
• Working on the customer sign in portal for eCommerce.
• Went in to Logan drop off a couple of adilas.biz flyers. Tried going to see a contact but ended up visiting with some other contacts. 20 miles.
• Went to Smithfield to work with my brother on some video editing. He is doing good and it is turning out well. 10 miles.
 
Click to view time photos.
AU 1220 Daily Tasks 5/22/2013   • Reviewing notes in my notebook.
• Working on the customer sign in portal for eCommerce.
• On the phone with Steve. We did a GoToMeeting session and looked over his code for different groups. He is getting better and better at doing custom reports.
• Working on the customer sign in for eCommerce.
• Reviewing notes in my notebook.
• Adding links to the my account section for eCommerce.
 
Click to view time photos.
AU 1221 Daily Tasks 5/23/2013   • Reviewing internal costing for stock units.
• Bank stuff and monitoring remote servers.
• Brainstorming, phone calls, and browsing the site.
• Working on the remote customer login or sign in process for eCommerce.
• Working on the customer sign in (login) for eCommerce. Added some validation on what fields could be used. On the phone with Newtek talking about the server migration. We came up with the plan to switch domain names and use adilascontent.biz domain and SSL to lower the possible down time with changing the DNS (domain name server) records. Called and talked with Steve to get his ideas about what we should do. We also talked about costing models for stock/units.
• Writing an email with technical information about the site transfer.
• Finished writing the email bout the upcoming site transfer.
 
Click to view time photos.
AU 1241 Daily Ideas 5/23/2013   -On using stock/units for internal job costing. It would be cool if the internal invoices that are applied to the stock/units could show grouped invoice line items (grouped). It would also be cool if you could see grouped expense/receipt types that have been applied to the stock/units. All of the data already exists, it just needs to be grouped better.
-On the above idea bout grouping data… All we need to do is make the underlying advance reports be able to show and group the data. Then just provide a dynamic link and the process could be done. Pretty easy fix.
-Today, I opened up a big project that we helped track back in 2008/2009 out of the country of Belize. It was a multimillion dollar construction project that used adilas to track costs on the project. They used stock/units, locations, parts, PO’s, internal invoices, and expense/receipts to track their data. They did a great job. Anyway, I opened up the corporation and made it active again. They have tons and tons of data. I may use parts of that as a demo for showing job costing. They were very creative and did a great job. Sometime it is fun to go back and remember what we did and where we’ve been. Good stuff!
 
Click to view time photos.
AU 1222 Daily Tasks 5/24/2013   • Went in to Bridgerland to have a meeting with my dad and a guy. He is maintenance guy and teaches for Bridgerland. I did a demo on stock/units and internal costing, outside repairs, and internal invoicing. We talked a lot of theory and I used Steve’s old business and another company to show different options. The highlight for me was talking about tracking data objects over time. I showed both this gentleman and my dad some of the little sketches that I’ve been working on. (5/11 and 5/17 ideas on time and tracking to micro levels). The other highlight was dealing with ideas for tons of different interfaces. We talked about interfaces for maintenance, home food storage, process monitoring, batch codes, etc. I can’t wait to get the program to that level. 20 miles.
• Meeting with by brother. He was showing me his music making software and cool things he could do with it. It was quite a visual piece of software. All kinds of buttons, options, sliders, dials, switches, etc. He kept showing me screen after screen and all of them were different. It was a little overwhelming but good to see. It cast a thought about complexity and how relative complexity really is. Another really fun thing with the sound editing software was how it could deal with live input and just by changing settings and filters it could change the sounds in real time. It also mapped things out in layers that could by moved and mapped over time. Most media type software packages have both layers and time lines. Movie editors, Flash, sound editors, etc. Anyway, fun to get some layering and timeline ideas. Great meeting.
• Phone calls, emails, tech support, and playing with new POS (Point of Sale) hardware for the upcoming training session for adilas.
• On the phone with Steve going over some code questions. Good stuff.
• New logo for a company.
• On the phone with some new contacts talking about an adilas setup. One of them wants to be an adilas rep and the other is a business consultant that works at the college. Great people.
• Domain settings for adilascontent.biz.
 
Click to view time photos.
AU 1223 Daily Tasks 5/25/2013   • Random stuff. Checking new receipt paper, emails, phone calls, and setting up a new flatbed scanner and printer.
• On the phone with Steve going over his custom code and good map app for a company. We did a GoToMeeting session and talked about his code. He is having fun.
• Trouble shooting a new printer and scanner. It had problems at first.
• Validating some code that Steve made and did for the limited retail dash board pages. Cascaded the hide costs and profit permission to the pages.
• Posted files online and sent Steve a copy of the new files.
 
Click to view time photos.
AU 2286 Brainstorming - Migrating Data from Dedicated Box to Dedicated Box 5/25/2013   Migrating data from dedicated box to dedicated box:
- Leave adilas.biz up
- Add notes that we are migrating data and will temporarily be using adilascontent.biz – news & updates
- Set any form submissions (logins) to the adilascontent.biz server
- Set up adilascontent.biz and point the domain to the new server
- Make sure that it is resolving to the new server
- Make sure that the new server has a valid SSL
- On the adilaswebservices.biz (customer web) site update the path for images so that it gets its data from the content server.
- Get everything running on the new server and once things are stable, make the DNS changes to the adilas.biz site. In theory it will be old passing to new and then new passing to new (once the switch is made).
- Once we are sure that everything is good to go, we will revert and flip things back to the main adilas.biz site.
- See email sent on 5/23/13 to Newtek.
 
Click to view time photos.
AU 1224 Daily Tasks 5/27/2013   • Went in to town to setup the first paying client in Utah. They do consulting. I showed them the whole backend setup process and got their credit card information. Fun setup. They would really like to become adilas reps and consultants. Good stuff! 15 miles.
• Went in to Smithfield to work with my sister on users, permissions, departments, and flow for upcoming training session.
• Setting up the training corp and light testing.
• Customer migration for a company.
 
Click to view time photos.
AU 1242 Daily Ideas 5/27/2013   -Ideas for a flyer… “World Building”. I had the idea to do a flyer about the concept of world building and telling the story. This could include a number of concepts and how they help to “tell the story”. Include: characters, relationships, trouble, decisions, consequences (From the author: Brandon Mull)
-Along with the world Building flyer… Add an analogy between the human world and the adilas world. This might need a little help!
Human World vs. Adilas World
Universe - Adilas admin
Worlds/locations - Corporations/locations
Populations/Groups - System Players
Individuals/Objects - Main Objects
Data Level - Data Level
-World building and telling the story: universe, world, locations, populations/groups, individuals, data. Do a flyer that talks about world building and telling the story. Include adilas core concepts. (This whole flyer is the why)
 
No po photos available. Click to view time details.
Adi 673 Logan Training Class 5/28/2013   Three day training course in Logan. Looking to do the following:

Day 1 - Sales, Inventory Tracking, and POS (Point Of Sale)

Day 2 - Customers, Elements of Time, and Flex Grid

Day 3 - Deposits, Expense/Receipts, and Backend Office Functions.
 
Click to view time photos.
AU 1225 Daily Tasks 5/28/2013   • Finished up the customer migration for a company.
• Emails and tech support.
• Creating an agenda for day 1 of the training class.
• Went into town to teach day 1 of the Logan training class. It took quite a bit of time to set up the class. I had printers, barcode scanners, credit card readers, scanners, etc. Tons of stuff. I only had a few students but it was fun to do and show some different pieces. We talked about world building and how user to corps are setup. I used a graphics program to draw and show relations. I started with Microsoft Paint and then went to Fireworks to be more accurate. It got a little bit deep but it was pretty fun. One of the interesting things that happened was I introduced the “chooser” (choose your interface) and it kind of confused the students. Almost too many options before they really know where they were going. I’ve got to think of way to ease people into the mix of adilas. It is quite big and very dynamic. 20 miles.
• Small side note about how the day ended (5/28/13). About 2:30-3:00pm my wife brought my son and daughter to Bridgerland. She had taken my son in today to be checked for diabetes. His blood sugar level was over 700+. A normal level is between 60-100(ish). Anyway, the doctors wanted us (my wife and I) to take my son down to Primary Children’s Hospital in Salt Lake City. So, we cancelled the last couple of hours of the day 1 (one) training course and I went with my wife and son down to Salt Lake. My dad and mom and sister helped shut things down and took my daughter home. My dad helped my give my son a blessing before we left Logan. Pretty crazy day!
 
Click to view time photos.
AU 1226 Daily Tasks 5/29/2013   • Emails, light tech support, and did three new logos for a company. Lots of watching and observing what they do at the Hospital for systems and/or ideas for training people how to use adilas.
 
Click to view time photos.
AU 1227 Daily Tasks 5/30/2013   • Created a new June training flyer. Cascaded it throughout the site. Updated the news and update page. Emails and tech support stuff from the Hospital.
 
Click to view time photos.
AU 1228 Daily Tasks 5/31/2013   • Random emails, catch-up, and getting organized. Made a couple phone calls and made some to do lists.
• Prepping files to help switch servers.
• Brainstorming about ideas for more mobile code, pages, settings, and flow. See notes on this page and next page.
• Working on files to transfer them over to the adilas content server for testing.
 
Click to view time photos.
AU 1243 Daily Ideas 5/31/2013   -What if we marketed adilas at the “World Building” level. Take it clear out to the sci-fi realm. Space, time, levels, orbs, permissions, settings, rules, in-line custom code, etc.
-What if it was a “3D World Building” software application. Build characters, relationships, cause and effects, locations, rules, flow, processes, etc.
-What if we make it too dynamic and over complicate things? I’m not sure at what level that happens.
-What if we made it more complicated to make it more simple? I know that sounds weird, but what if we had to do that?
-Wrap up one project at a time. A base hit will do! Remember, sometimes small and manageable changes are better than huge on hard to control changes. A base hit will do!
 
Click to view time photos.
AU 2287 Brainstorming - Ideas & Goals for Making the Adilas Site More Mobile & Modular 5/31/2013   Ideas and goals for making the adilas site more mobile and modular:
- Be as dynamic and mobile as possible.
- Store variables and settings in a database. Use the Application.cfm pages to help cascade these variables to the subpages.
- Play at the different levels:
o Universe
o World
o Locations
o Groups
o Individuals
o Data
o Time
- As much as possible, create defaults, settings, permissions, and in-line custom code and flow.
- We need to look and watch for hard coded settings and values.
o Database Id’s
o Look-up fields
o Conditional logic with hardcoded output
o Void store/location
o Void bank
o No bank assigned
o N/A System Vendors
• Parts
• Stock/Unit
o Admin payee id’s
o Admin corp id to watch for changes
o Hardcoded dates
o Hardcoded links or URL’s
o Permission id’s
- Wrap up one project at a time. A base hit will do! Small and manageable changes…
- Some of this may be futuristic and needs to be pushed to future developments.
- For now, I need something pretty quick