all data is live and searchable
[reset this page] .
[historical web outline - entries by month] .
[adilas community funded projects] .
[contact adilas.biz support - email form] .
[help]
|
Adilas.biz Developer's Notebook Report - All to All - (353)
|
||||||
|
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 2248 |
|
Notes - Use Technology, Business to Business Interactions, Worlds & eCommerce | 6/4/2012 |
Use technology - Mall, social media, community, system, B2B, “adilas world” - adilasworld.biz - adilasworld.com World building or business world building Business to business transactions - Training business to business – buy and sell from corp to corp - “Game”, “Game mode” interface Worlds eCommerce flow: invoice checkout procedure Assuming that we already have a customer signed in and/or added to the database. - This page could query the database and check for any other additional contacts that have the word “shipping” or “ship” in the contact type. Show the main address, any other options or allow them to add a new address. (Select from a list provided) (add a new address) - This page will act as the final review and the payment page. Once submitted, the invoice will be final and the info submitted to the database. So, on shipping… what about same as billing address option - On shipping, we need to validate that a valid address exists. The only requirements are a name and a zip code. We need to check for a city, state, and address as well. (Layout: See scans in photo gallery for 6/4/12) |
|
|
AU 1139 |
|
Daily Ideas | 3/14/2013 |
Artist & Writers Fest – USU -Brandon Mull – Author of Fablehaven – - Dream it up in your head and then do it - Use the real world as a model - Spend lots of time daydreaming - Details and memories provide additional insight - World building – create a new environment or world - Think through how the world would work and what would happen. Example: Say a good fiction writer might talk about a concept of an automobile. A great fiction writer goes clear to the traffic jam level of this concept. o Take things to a new level and what happens in their society or culture. How do you deal with cause and effects? - What new abilities does this bring to the picture? - Brandon interacted with the audience quite well… lots of questions and responses. Story based. He was talking about concepts of world building. Think through the realities of the world you are building. - Characters, details, physical description, use of words, how they think, what do they do, personality, learn about past, base off of real people, what they choose, stay true to that, relationships, interactions between players. - Five key pieces to a story and/or world building: characters & relationships & trouble & decisions & consequences. - Imagination can take you places. - Sometimes no’s help create who you are – a great teacher! Reading session – Writer’s & Artist Fest - I want to accomplish my dreams – so that is what I’ll do – young author. - Limitless! o Creativity, motivation, capacity of the heart, challenges. |
|
|
AU 1129 |
|
Daily Tasks | 3/27/2013 |
• On the phone with Steve. We went over a few things about training and client needs. We talked briefly about job costing and different ways to use some of the adilas tools. Eventually we will need to make both makes and models into a dynamic corp-wide setting (what to call them). • Went into town for day two of training. We had more participants with GoToMeeting and had a great session. On a fun note, we started the day talking about “world building” – a concept that fantasy and sci-fi writers use to help their readers learn and understand the rules and options in these other worlds. We then started talking about the adilas world and what goes on there. We lightly talked about five features that Brandon Mull – author of “Fablehaven” used in a seminar. They are: characters, relationships, problem and/or trouble, choices and decisions, and finally consequences. Great session. Lots of interaction through GoToMeeting. There were three clients that chimed in a good deal. There were others but those three were active and asked tons of questions. 20 miles. • During training we found and got a couple of new requests. Spent some time making some quick fixes. Linked up the default check writing bank to the add new expense/receipt page and the add new expense/receipt payment page. Also changed the flow on the Special Live PO’s and how the main vendor/payee gets changed. The old way used a dynamic drop-down list to change the PO vendor (basically setting the payables vendor). The downside was that in order for vendor to show up, they needed to have at least one PO and one item or part in the system. These requirements helped to limit the list but added some complexity to the process. The other change we made was to switch the drop-down list to a straight id number field. This makes it easy to switch but requires a vendor/payee id look-up. Posted files online. |
|
|
AU 2279 |
|
Brainstorming - Adilas Concepts | 4/10/2013 |
What are the main concepts of adilas? This was just a small exercise… there are tons more… o Players: - Empowering the user - Data - Basic building blocks - Permissions and settings - Physical extension of actions into a virtual world - Friends and buddies - Functions and tools - Characters - Story - Same thing over and over again o Problems, Needs, and Goals: - Next logical steps - Development - Data - Change - Functions - Goals - Pain - Needs, trouble or problems o Consequences and actions: - Game of business - Cause and effects - Data o Time: - Objects and data over time - Data - Roll call - Searching - Change - Underlying and kind of subtle o Relationships: - One-to-many - Data - Culture - Fundamentals, do things over and over, stack and stack - Mix and blend - Friends and buddies - Repetition o Decisions and choices - Game of business - Cause and effect - Data o Accountability: - Data - Searching or searchable - History - Track everything - Virtual recorder or video - Capture real life actions in virtual reality o Systems: - Centralizing data - The “whole” - Systems thinking - Data - Scalability - Engine - Web-based - How you use it & what you do – create what you look like - Human body - Server based - Concept buffet - Developer’s notebook and sharing o Vision and future developments: - Next logical step - Data - Dreaming - Change - Platform - Concept and buffet - Developer’s notebook and sharing o Tools and Maintenance: - Data - Paper, spreadsheets, databases, software, IT and notebooks, servers, web applications, platforms and API’s - Breaking models and tools • This causes problems - Searching - Maintenance o The Story: - Going to the source - History - Data - Data mapping - Features, advantages, benefits - Players, relationships, trouble, choices, consequences - Time - Data portal - World building - Virtual copy of real life - Hand stitch or sew it together o Functions: - Data Other Notes: - Inputs & outputs – you get what you give - Weakest link affects the whole - Confidence - It takes work - Think logically – what happened in real life and how would I do that in a virtual world - Flag & date - If correct, let it flow - Checkpoints - Computers are dumb, powerful, but dumb, you have to tell it what to do - Everybody uses the system differently - World building and telling the story - It may be over kill at times but it helps track the story, even if it gets complicated. - You tell the story, we then help you map backwards to show where things were at. - Push vs. pull – give automatically or ask for - Concept buffet –tons of topics - You find what you are looking for - Different notes from talking with Steve about adilas, direction, and core concepts: o What you do physically everyday…. We capture that is a virtual environment o Whatever you do physically… you have to record it o Physical extension of physical actions – physical to virtual o Willing to try and love of learning o Engine o Features, advantages, and benefits o Fundamentals, do over and over, stack and stack - Pyramid Diagram #1 (starting at the top and moving to the base in this order) o Permissions o Settings o Functions o Types o Friends - Pyramid Diagram #2 (starting at the top and moving to the base in this order) o Functions o Types o Settings o Permissions o Concepts |
|
|
AU 1190 |
|
Daily Ideas | 4/15/2013 |
-Similar to the mix and blend comment above… I think that I will start using this phrase… - “Get results by applying business functions, application players, and core concepts.” -In short – Results, Functions, Players, and Concepts. From 4/9/13 to 4/15/13 I had an explosion of ideas and concepts. I was trying to boil hundreds of concepts down into smaller categories. I ended up with these 12 core concepts. Many of these top level concepts have tons of subs. 1. Players 2. Relationships 3. Problems, Needs and Goals 4. Decisions & Choices 5. Cause & Effects 6. Accountability Core Concepts 7. Objects & Data Over Time 8. Systems 9. Permissions & Settings 10. Vision & Future Developments 11. Tech, Tools, & Maintenance 12. The Story These are some other thoughts that haven’t made it in to my notebook. Most of them come from 4/9 to 4/15. - Inputs & outputs – “you get what you give!” Normally you hear “you get out of it what you put in to it.” What if you shortened that saying to… “you get what you give!” That changes its meaning incredibly. - Weakest link affects the whole. - Confidence - It takes work - Think logically – what happened in real life and how would I do that in a virtual world? - Flag & date - If correct, let it flow~ - Checkpoints - Computers are dumb, powerful, but dumb. You have to tell it what to do. - Everybody uses the system differently. - World building and telling the story. - It may be overkill at times but it helps track the story, even if it gets complicated. - You tell the story, we then help you map backwards to show where things were at. - Push vs. Pull – give automatically or wait until asked. - Concept buffet – tons of topics. - You find what you are looking for. - eBusiness Model - All elements work together, interacting and influencing one another. - Objects are defined by relationships. - Be willing to change. If we replace bad habits with good ones, it can dramatically improve or reinforce the change. That is good! - Focus on and teach people! The actual subject is secondary. That is hard to remember sometimes. - It is okay to testify of truth wherever it is found! - What is adilas? A complete package. It is way more than just a “sales & inventory tracking system.” You get everything! - Confidence – feeling good about yourself and what you have done. And knowing and/or believing you can do it. - Everything starts with your goal. What do you want to do? What do you need? Once we know that, we then look or think about the tools to get the job done. - Say you go to the grocery store. You have tons of options. If you know what you want, you just go there. If you don’t know what you want, you start walking aisles. Inside of adilas, it is the same way, if you know what you want (you have a goal) you just go there. If not, you may feel stuck or may get frustrated. - Portability – ability to move or change. - Industry specific – skins and interface. - Construction… you could build anything with a saw, a drill, a hammer, and a screw driver. If you know how to use them and what they do. Think – goal, tools, and then how to apply the tools or concepts. - I love the word “apply” or “applied”. That means putting things to action. - My son was reading the word “turnkey” and he turned it into “turkey” (gobble, gobble). He then said adilas was a wild turkey chase. You go all over the place like chasing a wild turkey. I thought it was kind of funny! - What you do physically every day… we capture that in a virtual environment. The system is like a physical extension of physical actions. - Our people need to be willing to try and love to learn. - We have an engine. - Stick to the fundamentals… do it over and over, stack and stack and stack. - We are pushing towards a self-service model. - Use GoToMeeting and do weekly training sessions. This could start adilas university with very little money. Maybe getting up to 2 classes a day, 5 days a week. - Along with that, it may be good to pay a rep or someone to teach a class. Say $40 per session or $50 per session. 2 hours. - We want to use a new landing page for notes, updates, news, and upcoming training events. This page would pop up when a user logs in each day. Maybe set a session variable and if 0, show the page. If 1, let them bounce around as needed. - The main adilas.biz and adilasuniversity.biz site both need some loving. |
|
|
AU 1242 |
|
Daily Ideas | 5/27/2013 |
-Ideas for a flyer… “World Building”. I had the idea to do a flyer about the concept of world building and telling the story. This could include a number of concepts and how they help to “tell the story”. Include: characters, relationships, trouble, decisions, consequences (From the author: Brandon Mull) -Along with the world Building flyer… Add an analogy between the human world and the adilas world. This might need a little help! Human World vs. Adilas World Universe - Adilas admin Worlds/locations - Corporations/locations Populations/Groups - System Players Individuals/Objects - Main Objects Data Level - Data Level -World building and telling the story: universe, world, locations, populations/groups, individuals, data. Do a flyer that talks about world building and telling the story. Include adilas core concepts. (This whole flyer is the why) |
|
|
AU 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! |
|
|
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! |
|
|
AU 1246 |
|
Daily Tasks | 6/4/2013 |
• Working on adding and editing customer information using the backend eCommerce section and customer sign in portal. Brainstorming on flow. • Checking in with the server team at Newtek to plan the server migration process. • Updating pages about upcoming server migration. • Tech support and phone calls. • Rereading over the Adilas, LLC. Operation agreement document. • On the phone with Steve. We talked about current client needs, using technology, adilas university, education, reps, training centers, and marketing ideas. We talked about the adilas mall and what we may want to call it. We had a great discussion and ended up talking about “World Building” and fun related concepts. We decided to change the “adilas mall” concept to the “adilas world” concept. This will be a special site that will highlight and showcase users, reps, consultants, CPA’s, Attorneys, trainers, graphic people, code writers, etc. We had a great time talking about how world building and adilas go hand in hand. The deeper we get, the more we see a need for a community of users and eventually B2B business to business transactions. • Revamping the original adilas operational agreement from back in 2009. Kind of fun. Sent copies to Steve and David. |
|
|
AU 1670 |
|
Daily Tasks | 6/24/2013 |
• Writing an email to someone who does marketing for companies. Wrote him an email explaining concepts of “world building” and catching the story. Explained a small analogy about the human world and the adilas world. Included topics like: Universe Level, World Level, Location Level, Group level, Individual Level, Data Level, Run all Levels over “Time”. See a copy of the email for full details. • On the phone with Steve going over possible marketing plans. We talked a lot about world building and getting our product out to the masses. We also talked a lot about reps and spending some money to get some good reps and training centers. Lots of options. We then did about an hour and a half GoToMeeting session to help Steve with his custom code work and creating a custom calculator for a debt consolidation company. • Recording notes and light research on world building. • Went to Smithfield to work with my brother and sister. Got a bunch of videos from my brother and chatted with my sister about the upcoming training class. Lots of good stuff going on. 15 miles. • Reviewing video footage from the adilas training class back in February of 2013. My brother gave me some new files today to crunch and squeeze for uploading. • Working on custom uploads for a company. • Emails and tech support. • Customer upload for a company. • Migrated patients and customers for three different corporations. Small email to let them know what we did. |
|
|
AU 1671 |
|
Daily Tasks | 6/25/2013 |
• Online searching for graphics to help in a world building flyer. I think that I want to tie world building with capturing the story and storytelling. That seems like a natural fit. • Went in to Logan to teach day one of the June training class. We had 5-6 people and spent tons of time practicing and playing with the features. We also switched out as far as who was running the main computer. Lots of good interactions and lots of learning. 20 miles. • Worked on graphics for the story and world building flyer. |
|
|
AU 2142 |
|
Adilas 3 Day Training Notes - Logan | 6/27/2013 |
Day 3 - Logan, June adilas training - June 27, 2013 Morning • Concepts - world building - theory, history • Went through corp wide settings, dynamic, flexible nature • Permissions and settings so that we could move into financials • Looking at P&L, accountability, After Lunch, • A class participant wanted to know how to track all sorts of things with her students. -Went with a customer option (called students), then went into flex grid to track and tie thing. • - A class participant said something to the effect.... so what you are giving me is my own database. That is essentially what you could call it, your own, personal, customizable database. • People LOVE adilas! They are SO impressed with the flexibility, the adaptability, the search ability, the usability and the accountability! • The data is in - it is retrievable, it is searchable, it is there for the long hull! • Going through questions class participants had about things that had not been covered yet, or clarifying • Discussing flow of deposits and how things flow to and from the bank • A class participant entering a deposit • Printing checks • What is your real goal? Is that attainable in reality? |
|
|
AU 1686 |
|
Daily Tasks | 7/3/2013 |
• Squeeze stuff and crunching tons of videos. I’ve got two computers going. One for code and graphics and one for video stuff. Worked on the “World Building” graphics. My wife helped me with some verbage. We changed the “object level” to the “individual level” and also changed the time part to read “run all levels over time”. Sent out an email to Steve and others requesting feedback and ideas on the world building concepts. • Brainstorming and recording notes. • New logos for two companies. |
|
|
AU 1707 |
|
Daily Ideas | 7/3/2013 |
-We have had a number of requests to help with emails and notifications. If we wanted to, we could set up each company with their own email address and then use that address to send invoices, updates, notifications, etc. For example: Say for a company called XYZ Construction. The email address could be xyz_construction@adilas.biz. The addresses could be a forward only address. We could then call a special web service and use a single send method to use the email functionality that is wanted. -As a pro – if we did the email stuff for our clients, each person that they reach out to would see the name adilas.biz. That is good advertising as long as it doesn’t get abused. -I am so thankful for help from above. I know that my Heavenly Father and His Son live! I get help all the time in more ways than I can count. Just trying to some credit where credit is due! Yee Haw! -Do a flyer showing tools: - Head & Mind - Paper & Pencil - Word Processors - Spreadsheets - Databases - Software & IT (Information Technology) - Web & Cloud - Custom & API (Application Programming Interface) - World Building |
|
|
AU 1689 |
|
Daily Tasks | 7/6/2013 |
• Brainstorming on concepts and ideas for business world building. Lots of mental scenarios. • Working on a contract calculator page. Finished calculator and posted online. Light testing. • Working on a custom project for a teacher using adilas for students and teachers. • Online reviewing some custom code that Steve did. It looks good. It has a custom interface and a custom debt calculator. His skills are definitely improving. Good stuff. • Emails back and forth and some planning on our current to do list. • On the phone with Steve. Lots of talk about custom code and fun upcoming projects. Lots of things are clicking and popping. • Working on a new flyer for the July training event. Also working on showing new YouTube videos. Added all 24 new YouTube training videos to adilasuniversity. |
|
|
AU 1696 |
|
Daily Tasks | 7/16/2013 |
• Went in to day one of the Denver Training event for adilas. We met at the Moose Lodge; the building was a multipurpose room (where we did the training) and a bar/diner/pool hall. It looked a little random but ended up working out just fine. We set up the class room and added a bunch of tables and chairs. David ended up bringing a large movie screen, which really helped. There were a couple of new people that came to the training. We had 3-4 online over GoToMeeting and we had about 10 in the live class room. The day started with Steve giving a basic sales demo. It was fun to watch him do that. We then spent most of the day talking about corp-wide settings, sales, quotes, invoice, etc. We covered services, generic products, vendor specific items, and PO’s. Great class. We used the world building graphics quite a bit and tried to relate back and forth between the graphics and what concepts and/or levels we were playing at. |
|
|
AU 2137 |
|
Adilas 3 Day Training Notes - Denver | 7/18/2013 |
DAY 3 - JULY 18th - Focus on deposits, banks, expenses, etc. -Started off with a question from online which led us back into flex grid -Back into flex grid... (Transparent & non-transparent flex grid options) -The only caution for flex grid is plan it out so you don't have to re-do all of your work and so that you can have the pieces you need where you want ^I need to learn more about flex grid and elements of time -I love the problem solving aspect of setup and consulting.... understanding their issues, concerns, needs, goals and helping choose the best tools to fit that goal or an acceptable solution for their concerns -It is so neat that the flex grid is its own customizable database on top of the application. -You can even barcode flex grid if you would like - a company uses this because they have different pricing for many of their customers on the same parts *We need testimonials and experiences from customers - people see the value in that, it had been mentioned by multiple class members -Stock units seem really neat - we saw a little bit with a company that had done a lot of internal invoicing with stock units - really amazing how much they tracked everything.... construction management and job costing to the n-th level -Once you have all of this data, you can do SO many things. Plan ahead, know what you need for future projects, have everything tracked to the finest detail... huge potential, everywhere! -Brandon did a little show & tell of how some different company's use adilas - people LOVE this! This seems to give people an understanding to the point where they finally grasp some of the possibilities of adilas. It is interesting to hear their reactions, because we have been working in adilas now for 2 days and they have been really excited but people love seeing how this is really used in business and they start seeing an even bigger picture. A good little wow show, they really capture just how much this tracks and how easy it makes people's lives in business and how great of a business tool adilas is. ....... Now we just need to get some "commercial", "testimonials" from so many of these customers that are using adilas. -Adilas really increased the re-sale value when you have such a detailed customer base and detailed books and you really increase the value by showing what the company is that is being sold. *IDEA: A rep training - which was already mentioned above but what if it was largely rep led and instructed - specifically for reps and how to setup clients, but also all that adilas does -Protection by sharing - and the users and those in the class were expressing their appreciation of that and also feedback on how smart or a good route that is -Security question - password & profile help page. Talking about all the upfront adilas does to keep things safe *Users get super frustrated when they are set up and feel like they have been left alone. If you can make a good setup and initial training, that is critical, but there is a definite need for consultants and training - no question obviously, why we're here again and why adilas university is forth coming. You will definitely have some people that will get in and figure it out and make things work and you definitely have other people who will need more hand holding. Also known - just figuring out how to address that again and help users to be successful! That should be the focus of the rep/consultant - help your users/clients to be successful. -Is accounting even needed if nothing is happening? Great way to ask that - let operations lead. Put the horse before the cart. -Zipper analogy - a great starting point - because merging operations with accounting will change the ways businesses can function and can change the face of what will occur in business accounting and tracking.... Brandon wanted me to record that Joe was talking about this but more of a comment than an idea. Maybe an idea as an approach??? -Reps/consulting/instruction note: we really need to be able to help people understand principles, flow, some basics and where to go for help (help file, tech support, adilas university, etc.) about how adilas functions.... because when people understand flow and more principles, then hopefully they can be more prepared to go in and figure out how to make things work for them. -Interactive map: operations on the bottom and as things flow through the bottom section, then thing begin to rise to the top (a little cream scenario), when you have good operations, things will be cascading to the top - your accounting aspects -I'm really impressed with Brandon's teaching: sometimes it gets really challenging to cover basics, flow, and possibilities when you have such varying levels of users and also users or clients who really want their "problem" questions answered... anyhow, it definitely takes a balance and I am grateful for Brandon's patience and teaching and all such things. -Accounting comes with the natural flow of accounting -It is important to understand that there are many ways around the track. Different ways work for different people, industries and preferences - and help other to work in the way that they need... Roxanne: demoing expense/receipt - Good to remind people when setting up and the interface looks intimidating. That assets are any monies coming in, liabilities are any monies going out. With that PO's are tied to inventory, what you are paying and bringing in for inventory. Expense/receipts are any other money out for whatever....... -She also copies and pastes a lot of her little notes into all the different sections, b/c different ones show up in different reports -P&L - Profit and Loss, I.S. - Income Statement, B.S. - Balance Sheet -Roxanne was saying: Get in there and get working - if you make mistakes, not a problem, it can be cleaned up but be unafraid to get in there and just use it. There are ways to clean up, to move on, just get going and try to do the best we can. -Reimbursements - when creating that expense receipts for a reimbursement, you are putting in what they paid - so "no bank assigned", then when you go to pay him that will essentially create a new expense/receipt to satisfy that one or many if there are many to reimburse *Always work out of your payables, you're always cleaning up your payables. For what you owe, look at your payables, work from there. Look at what to pay from there, and then you have it broken down to your PO's, your REI's, and your Splits. -The "not yet" verified link on PO expenses you are paying on - if you click on that link it will take you right to the verify page and then right back to your payables homepage - instead of going back and doing the process over and over and over, you can do it all there nice and fast. Wahoo! Thanks Roxanne, that was a great demo! Back with Brandon leading - but a lot of group comments and input, wrapping up the training scenarios, etc. -Great comment by Joe as we were talking about future clients - Every situation you walk into you need to assess the client, not only what they need, but what is their interest and desire - are they ready to soak up adilas like a sponge.... or are they no, no we have QuickBooks/PeachTree/whatever... then you just throw them a bone and then another bone, etc., etc. Then Brandon was discussing that you really can walk someone step by step. You can start with some aspect of the application and once they get that then you can introduce another aspect. What do you want??? *The byproducts that adilas creates is worth way more than the monthly payment for the application *People believe in adilas and the way adilas functions. They love how adilas cares about their customers and reps, they appreciate how adilas is not stingy with all of their code or training, they love it for the incredible business tool it is - that it tracks everything and does almost anything they want and that you can tie everything together and tell the whole story, they love that adilas is offering training for free right now, that adilas actually takes their ideas for improvement and incorporates that. Those things make people believe in adilas and people are selling and promoting adilas because they love the product and they believe in adilas' philosophy. -Things are automatically mapping just as you are operating. -"People do things different ways, and so does adilas." -comment from Roxanne as we were discussing how important it is to set people up right from the beginning or in a way that works for them and their preference -Also a note, a consultant was discussing that they doesn't know everything but you don't want a client to know that or feel like you don't know what you're doing. So they focus on another problem or area of training for that time, express that you can focus on the question next time or after getting these things settled, work with something that you know, - then they’ll figure out the answer for the next time. That was their trade style. *But of course another style - which others mentioned, is: I don't know the answer to that question but I know where I can get the answer and I will get it for you. That is how I like to play as well. Be completely up front and honest and transparent but I am willing to work for the answers and get them to you. You can still be confident about the system and your abilities without knowing the answer to everything. Just be up front and professional and get the answers you need or find creative solutions for their problems. The answers are there. -Here is the system, there are some rules involved but you can play like crazy with whatever you want! -History has such great power, records the rest of your story. -Traditional accounting - I need to close up my month, what happened this month. Adilas - what happened today, at any time, and at any time throughout the day. All sorts of data - run all levels over time! -You can use any aspect of adilas.... or all aspects of adilas. What do they want? Or if you hit the brick wall of tradition, offer something they don't have... then they can slowly work into things later if they want, or if not, no problem. You can sell adilas just for their pain! -Because you are not forced to play in one specific way it opens things up exponentially. That is why adilas can service all sorts of clients, industries, etc., etc. -People love that adilas supports the small business owners and truly works to support clients and does not kowtow to huge corporate companies. -And still growing.... :) -A great selling point for customers is also the idea sharing - if a client has a need, adilas often has a tool that can help, and if adilas doesn't have it you can submit your suggestions or they can build you the custom function or maybe there can be a piggyback development -Put notes in everywhere in adilas - use the notes to the max, tell the story Notes for graphic ideas: -Adilas Engine with different bodies/skins - multiple ways to show how customizable, various ways to interface -World building graphics - -Items travelling through the pipes: PO's - transformation - invoice -Steve's symbolism about an ant colony all participating to build adilas |
|
|
AU 1746 |
|
Daily Ideas | 8/2/2013 |
-Adilas has become somewhat of a community effort and/or community project. I would love to keep it that way. Maybe the community and our users could help us take things to the next level. -On the permission to lock down customer to reps – we know that ideally it would work best as a one-to-many relationship but we are thinking of doing a miniature version to start with. This will be a more rigid permission. That will solve some things temporarily until we can circle down and around again. -As a side note to the customers to salesperson (reps) permission – On the one-to-many, it would be cool if we could set up limits, permission, and even do both (limits and access) based on states, customer types, zip codes, cities, etc. That would be really cool. -Also as another note on the customers to salesperson permission – It gets deep pretty quickly. What about customers tied to invoices, stock/units, elements of time, quotes, statements, etc. What about those relationships? Are they limited or open based on settings in this permission? -As soon as we can, we need to do the following: - Open up the API (application programming interface) - Add the content server (separate content from data for load balancing) - Make the system more modular and independent (tons of mini adilas’) - Finish up eCommerce (it is close but it needs a bit more) - Round two (2) of elements of time - Roll call page for all main players - Reflexive side of the flex grid -Maybe put all adilas.biz help files on adilasuniversity.biz site. I’m assuming that eventually there will be tons of different domains that serve up adilas content. It might be nice to have a standard place for all main adilas help files. -The flex grid is super cool and very flexible – However, we are seeing a need for in-line fields that may be used for parts, invoices, customers, vendors, etc. Almost a custom field level for all of the main 12 system players or groups. The thing that would make it cool is if you could name it, set the data type, set rules and defaults, and then be able to search by these fields according to data types (dates, numeric, decimals, text, and binary). The search ability by data type is super important. -In a nutshell here is what is going on. People are getting creative and recording their data wherever they can right now. They, the companies, then export the data into MS Excel and then use the data to represent different things. It would be nice to help them out. The problem comes in to play as each company is unique and may have different needs. We could add some custom fields but then it makes the whole system a little heavier. This would be a case where we would add static fields in order to increase dynamic usage. I see the need, but I’m not sure we are ready to jump yet in that direction. The ideal would be to allow for unlimited dynamics and allow for those changes to happen and flow within the bounds of the system. This is custom, yet in-line, and fully allowed; that could get kind of tricky. -Another piece to the custom and in-line code is getting each corporation or world by itself. That makes the custom fields weigh less because they only apply to certain worlds and/or corporations. The trick there is updates and changes. If everything is custom – how do you update pages and features. It kind of comes back to in-line custom code. Basically, we know it needs to be custom so, plan for custom right off the bat. -All of this talk about in-line custom code makes me think of settings and permissions on an almost page level. This could be clear to the – use this field, call it this, require this, search by this, and have it show up here and here and here. Basically, this is the default outline, layout, and pre-set settings. If you want something different… you need to play at this upper admin “tech” level. Then you could do custom right out of the box. We aren’t there yet… but I can see it down the road in the future. -Two huge keys are: 1. Centralize the data 2. Catch the data -If you can get to that level – the rest is all possible. Those are the two things I see as paramount! -The deeper we go, the more we see things headed to “world building” and “virtual world building”. -Sometimes I get so excited recording notes and ideas that it is hard to pull back and do the work. Maybe I could become a professional daydreamer! -This is kind of silly – we say that our biggest competition is “tradition”. We also say that eventually we will be used to train our competition. What if we end up training people how to overcome tradition? Anyway, I thought that is was kind of funny. -The assembly line really helped out businesses. Things were done overtime and then passed on to the next step of the assembly line. Adilas does the same exact thing with your business data. Things are done over time and then passed on to the next step. Pretty cool! -I’d like to make a graphic and show how businesses use different assembly lines. It would then be fun to show how adilas uses similar processes to link and connect data together. -This is an old analogy we used to use for showing flow (graphics/sketches for each): operations and accounting - both perfectly in line – static. Operations and accounting – different things happen over time but they come back together – dynamic. The new analogy may look something like this – once again relating back to an assembly line – type analogy: operations and accounting – different things happen over time but they come back together in order to pass the checkpoints. Or another analogy that fits this flow is a bottle of data flowing down the river. As it flows (through a virtual assembly line) it passes certain checkpoints. My daughter even drew me a graphic for this. Some of the key elements are: 1. Enter once 2. Use over and over 3. Run it over time 4. Checkpoints help maintain flow 5. Checkpoints may be permissioned if needed 6. Track the entire life cycle. |
|
|
AU 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 1739 |
|
Daily Tasks | 8/26/2013 |
• Small update about where we are heading using students, interns, and such. Posted the update online in the news and update page. • Emails and light tech support. • Recording notes about World Building concepts. Sent a small email to Brandon Mull (author) about using his five main points for a good story. They are: characters, relationships, trouble, decisions, and consequences. • Working on elements of time for recording the Bear 100 race with all of its people and racers. Small code tweaks. • Posted files and updated the update page about students and interns. |
|
|
AU 1760 |
|
Daily Ideas | 8/26/2013 |
-Recording notes about world building concepts. Saturday night into Sunday morning, I woke up due to a dream that I was having. I was fasting for help and trying to figure out how to best keep the balance between work, family, church, and personal. These notes may need to be adjusted slightly, I was scribbling on post-it notes as fast as I could. -3D printers – I was thinking about how a 3D printer takes an AutoCAD or technical drawing converts the document into a physical item by outputting ply plastics in the shape of the object. It is able to go in multiple directions such as sideways, up and down, and back and forth. Pretty cool! (Another idea – what about a number of robot arms all working together to build something.) -What if you put a bunch of 3D printers together all building the same output or project. I was thinking of relating these multiple 3D printers to the main 12 groups or system players inside the system. Imagine a number of 3D printers for customers, invoices, quotes, vendors, PO”s (purchase orders), users, stock/units, parts, elements of time, expanse/receipts, deposits, and user-maintained balance sheet items; Imagine these 3D printers working in tandem or working together as different things related together (called tie-in or relationships). -Use this concept of multiple 3D printers to help show world building concepts. -Blocking or rough layouts. Most projects start out with a general plan. As things develop, more and more details will be added. Say for example you wanted to “rough in” or “block” a car. It might look something like this (notebook sketch) – very loose and only represents a light form or blocking… -As more details are added or carved out, the more the “blocked out” item becomes what it needs to be. This is a process and maybe even a progression. For example: The blocked car could become: (sketch of a car progressing from a blocky outline to a more refined and then detailed and accessorized car). Almost like a Cub Scout pine wood derby car being made. -Think multiple systems playing together over time. -Each with their own functions and/or jobs. -Eventually it tells the story as you run it over time. -2 key components of “blocking” are: Catch and hold the data in a central location. Once you have those two things (the data and it is centralized) you could detail them out. -Include the adilas core concepts. They are: 1. Characters 2. Relationships 3. Trouble, Problems, Needs, and Goals 4. Decisions and Choices 5. Consequences (Cause and Effects) 6. Accountability 7. Objects and Data Over Time 8. Permissions and Settings 9. Systems 10. Vision and Future Developments 11. Tech, Tools, and Maintenance 12. The Story -By applying these concepts, you only limit yourself to what you can dream up or how deep or far off is your vision… keep it positive. Think potential! -Circle back around to goals, planning, output, and needs. These could even by dynamic and/or changing… sometimes that may be scary… but sometime that is what is needed. -The 5 story building concepts from Brandon Mull, author of “Fablehaven”, “Beyonders”, and “The Candy Shop Wars”. www.brandonmull.com/site/video-bestbook.html The main 5 are: characters, relationships, trouble, decisions, and consequences. I’d like to relate those to world building concepts for businesses. -What’s your story or what’s your world? -Spell it out without getting too wordy. Say 2-5 pages. -This concept “world building” is one of the things that makes adilas unique as its own system. -If you don’t want to play at this level, that’s okay. -These concepts are pioneering the future of business and how systems will track things. -Ours is a first generation, stable product. Eventually it will get leaped or leap frogged by a next generation product. We may even leap frog ourselves. This is just the nature of progression. It is part of the game. -Our goal is to share and take a small crack at “Tradition”. -This is a modern-day pioneering! -Solicit help and ideas – from different sources. -Dream it up – we’ll wire it up! -Balance is one of the goals. Pull it back to the goals. -King Benjamin, in the book of Mosiah, has some great advice about balance. See Mosiah 1-5 in the Book of Mormon. -Apply it if you know it! -Define the terms and concepts of world building – lightly. These are the 12 main core adilas concepts. -A different approach – may need to be taught differently! That is okay! -My dad’s ideas on transitioning and progress… “Moving Forward” and “Project Next”. |
|
|
AU 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 1776 |
|
Daily Tasks | 9/12/2013 |
• Recording hours and transferring notes from loose pages to notebook pages. • Finished up transferring notes and recording ideas. I love taking notes… it helps me remember things. If not, everything tends to blend together into a mush of random pieces. • On telephone with a college student. He wants to help with some adilas graphics and such. He will be coming over later today for an interview. • Did some prep on the World Building flyer for adilas. I’m going to put him on that if he thinks it is a cool idea. The fun part about the prep was photo copying pages out of my notebook for him. I’m excited to get these files up and online. • This student came over to my house and we had a little meeting. My sister and I met his up at the University on 8/30/13 while waiting to talk to a professor. Anyway, he got to my house and I got to see some of his art work. It looked great and had a fun geometric balance to it. Once we were finished with his stuff, we started to talk about World Building and what we are hoping to do with that. Lots of concepts. I gave him a small stack of papers with ideas from past notebook entries. It had sample graphics, notes, and ideas I gave him the assignment to start watching YouTube videos and getting familiar with what we are doing. We will be meeting next Tuesday. • My sister came over and we did a training session on expense/receipts and balance sheet items. We did flex grid stuff, we did payments on account, we did ACH stuff, etc. We scanned receipts, invoice, credit card stuff, etc. It was a great exercise. We even got in to problem solving, did bank reconciliation, and found a duplicate check. All real and all live training. She did awesome and was flying around the site. Great meeting. |
|
|
AU 2293 |
|
Brainstorming - How to Introduce the Main Players | 9/19/2013 |
Small Brainstorming session on how to introduce Main Players: Example: Introducing main players like introducing groups – [like LOTR (Lord of the Rings) hobbits, elves, etc.] Personality…. Start with tools – move to – World building – move to – flavors (your flavor drives, guides the world you build) – Main Piece Possibilities vs. Limitations of the Players: - What are you?/ Brief Intro: - Abilities/What does it do?: - Friends /How does it interact?: - Weaknesses/Limitations/Shortcomings: - How much are you used?/When are you used? Interactive commercial: - General info intro: - What’s your flavor? - Multi-media - If you let people select at the different levels – show them where to change that or how to make it happen. (corp-wide settings – screen shots, etc.) - Commercial on Application Players: o Customer o Vendors o Etc., etc., etc. Approach it from the world view – Basic General World - Do we need to make it applicable for different flavors? Such as: standard retail, big tickets, services…..clinic, etc. Other notes and an example with customers: - Customer Homepage o Search o Advanced search o Log o Add/edit - Contacts o Add/edit o Search - Notes & logs & follow-up o Add/edit o Search - Photo - Flex grid |
|
|
AU 2294 |
|
Brainstorming Tools - Their Features, Advantages & Limitations | 9/24/2013 |
This Document came from the September adilas training course, 9/24-9/26/2013: Tools that we use: Features, advantages, and benefits: Limitations and how do these tools break: 1. Head and mind a. Always on, not limited, imagination, switch at will, creative, huge capacity. b. Think through things, process clear to the end without actually committing, different scenarios, multi-tasking even while doing other things. c. Unlimited capacity to learn and process. d. Start here and translate to other processes. e. Limitations – Recall, searching, memory, what you do know, knowledge, affected by outside sources. f. Break the mind – sleep, eat, and intake. Volume and number of transactions. g. Complexity 2. Paper and pencil (pen) a. Write things down to remind you, categorize things, you can do all sorts of stuff. b. Draw, make it up quickly, written hard copy, plan, play with options, you can flip pages, you can have huge, tiny massive, erase, mobile, searchable. c. Limitations – Search-ability but not centralized. d. You have to have it. Potentially dangerous with loss or damage – outside sources or personal neglect. e. Not centralized – no one else has it. Hard to share unless you send or copy it. f. Only one original. g. Break pencil and paper – searching, stacking, organizing, auto calculate, create relationships, nothing is automatic, everything is manual. h. Physical problems with paper, run out of ink, pencil breaks, if you lose the original, you have to start all over again. i. As it spreads, it becomes harder to get back to what you are looking for. No record of who touched anything. What date/times some things happened. 3. Computer Based – word processing or a text document a. All the creativity of paper and pen but you can now search it, print it, save it, send it, centralized, easy access, looks nice, readable, formatted, spell check, copy & paste, speed. b. Graphics, links, insert things, create columns and rows, email it, go back and change (small amounts to full pages of new content), take things away (delete). c. Limitations – structured, certain rules, learning curve (learn the tools), the program itself (does it even offer what you are looking for). d. Your skill level. Electricity and a computer or device. Dishing off to outside sources (printers, faxes, email, Internet). e. If it is not centralized, it doesn’t do anybody any good. Run out of space to save it. 4. Spreadsheets (rows and columns) a. It does the math for you. It can do calculations. Searchable, organize it, show/hide columns and rows, color, graphs, add graphics, block in cells, lock cells, connect certain things. b. Ability to reference to specific cells. Ability to sub divide and expand. c. Good structured look and feel. d. Export and Import data because it is already formatted in rows and columns. e. Changing sizes and merging data cells. f. Limitations – volume. It maxes out at a certain level. g. No history – once you replace it with something, it is gone. h. Higher skill level in order to play. i. Limited to rows and columns. j. It is not centralized. It is on your machine. k. Static layout – If your data is different or variable, it breaks. l. Break a spreadsheet – volume, you have to see the whole thing at once. m. Formulas and moving and inserting columns and rows. It may break all of the formulas and references to other cells. n. Electricity, computer, you have to buy it. o. Spreadsheets are not the most compatible for touch screens. p. Manual filters and always looking at a full screen of data. You can get lost very easy if the columns and/or row headings are not shown. q. You can overwrite things very easy. 5. Databases a. Unlimited structure, storage in the billions, relationships, histories, you can link things, search things, you never look at the whole database all at once. b. Return and report, call back, dynamic level for storage (one-to-many). Scalable. c. Different types of databases. There are file share databases (limited number of connections) or server databases (unlimited number of connections). What are the open connection options. d. Calculations, filter things, pull back certain rows, you can query things (asking it for things), loop or play in bulk – multiple tasks at once. e. Storing and cataloging things. Modular or ability to compartmentalize. f. Limitations – Where is the database located at? Location is very important. g. Computer problems such as electricity, hardware issues, connection issues, multiple variables. h. Security issues. i. Skill level – who sets it up? Who is going to work on it? How easy is it to get the data in and out? j. Break a database – volume (usually traffic vs. size). k. Deleting or dropping information. Losing integrity between pieces of the one-to-many. l. Too big or cumbersome. 6. Software Packages and IT (Information Technology) a. Package or packaged. Pre-built, on your own computer. Industry specific scope or niche. b. Keep coming out with new upgrades or versions. Improvements are being made. c. Thousands and thousands of choices. d. User friendly (general statement), support, manuals, well used and communities, training, etc. Lots of resources. e. You feel like you own something – even if it is older – you still own it. f. You can customize it for yourself. Create you work flow. g. Networking and everything can be hard wired. Established different connections. h. It is a tool that is meant for a specific job. It is a catered tool box. i. It has a version number that related to a historic level of the software. j. There are freeware, shareware, and different pricing structures. Bundles, packages, suites, downloadable or on a hard copy (disk). k. Limitations – price or cost. Same with IT (information technology). $0 to millions and millions. l. Implementation and delivery. How do you get it? Install? Download it? Served up to you? How do you consume it? m. Versions and computers – they don’t always match. Upgrades. Static and constant need for upgrades. Once you make it, it is that version until the next upgrade. n. Licenses – how many do you have and how many do you need? Bottlenecks of limit output by not having the right tools. o. Niche specific – but then you have to try to marry non-compatible products together. The average is between 4-6 software packages. Maybe more. p. Skill set and use of the tools. q. Break software – viruses, outdated, cost, volume, traffic, and hardware issues, not support of non-user friendly, natural disasters, computer crashes. r. Newer products with more features. Constant leap from of features. 7. Web & Cloud a. Great when it is fast, personal, anyone can access it with a device, centralized, unlimited as far as storage capacity, versatile. b. Use outside pieces, tons of features, graphics, links, form, buttons, animations, video, sound, print, you can search like crazy. c. If hardware crashes, no problem, switch device. d. Cut you IT (information technology) costs to almost nothing. e. Mobile. From your car, on the go, multiple things connected to the same pieces of data, collaborate from anywhere, anytime, multiple people can share tasks and work on projects. f. Conditional logic (if, then). NO updates, no waiting for the next upgrade (it gets pushed to the server). g. ADILAS – All Data Is Live And Searchable, Secure, Serviceable, Scalable, Sustainable. h. Go paperless. Scans, images, files, and other content tied into the system. i. Skin things (look and feel and flow and processes). j. Cut steps, speed up processes, customize things to a huge level. k. Younger generations are getting more and more tech savvy. l. Future??? Where is it going? Currently pioneering some of these fields and places. How deep is the rabbit hole? Potential! m. Limitations – Have to have Internet access (somewhat of a diminishing problem). More and more places are getting it and access is becoming free more and more. Free is good! n. Travel if Internet is down – have to get to a signal. o. Security or un-secure (hacks and stolen data). Semi unknown??? Brings up question because you don’t physically have it or can’t touch it. Where is it? Movies almost create this hype or scare on vulnerability. p. How adilas.biz uses security – HTTPS – the “S” is very important. This deals with a thing called SSL (secure socket layer) – encryption. Check logins – 3 strikes you’re out policy on failed logins. Each corporation (aka virtual world) has users assigned. Each page in the system checks for a three-way tie or code. Corp to User – User to Permission on each page. System history or virtual surveillance system. 75% of the entire adilas.biz application deals with validation and security. q. Skill set – certain requirements. r. Interoperability – meaning playing with outside players and service. Everything has to work together. Adilas – uses a “System Thinking” type model. Cause and effects, consequences, tell the story, connections and relationships. s. Custom needs. Load balancing and potential traffic. Adilas tried to be an e-Business buffet – you dream it up, we’ll wire it up! t. Play with both old and new technologies. Browsers, computers, operating systems, unknowns. 8. API or Custom (application programming interface) 9. World Building (stories and movies – ultra custom level) |
|
|
AU 1787 |
|
Daily Tasks | 9/26/2013 |
• Went in to town for day three of the Logan training class. Once again my sister and I worked on the “tools that we use” brainstorming document. It covers these tools: 1. Head & mind 2. Paper & pencil 3. Computer based – word processing or a text document 4. Spreadsheets (rows & columns) 5. Databases 6. Software packages and IT (information technology) 7. Web & cloud 8. API or custom (API = application programming interface) 9. Virtual world building (like stories & movies – with characters, relationships, trouble, decisions, and consequences) • After that, we got in to deposits, bank stuff, and lots of theory about how adilas tracks the data. We talked about auto vs. manual. We also talked about flow and natural cause and effect relationships that exist as you advance the ball from holding area to holding area. Just like water slowly transforming to slush, snow, and then ice. I used my marker pen quite a bit to explain and demo different scenarios. In the afternoon session, we had another guy come participate with us. He is looking into the assistant web develop position for adilas. He was quite sharp and seemed to follow along well. After the class, we conducted a formal interview. He seems to have some great skills. He also seemed to be very stable and a natural leader. Good stuff. As another comment for day three – I spent a good half an hour showing history and how adilas runs things on a more modern model and method. I had fun with it. |
|
|
|
AU 2148 |
|
Adilas 3 Day Training Notes - Logan | 9/26/2013 |
Day 3 – ****-Potential fix-it: when we turned off the start cart permission, and even other permissions, it was still able to get at the start cart page and go through the cart. **** *** You dream it up, we'll wire it up! What information/data do you want to track? Such incredible capacity for tracking data like crazy!!!! What happens... normal day to day transactions or "accounting" of what you have done... what you want to track -This is a live, experimental, real time project... not a software package wrapped on the shelf at Wal-Mart... But there is huge potential & flexibility with that. -Eventually people will end up building similar systems to adilas and tracking data and things this way. -Consultant: When people get data, they want more and they want it faster &... &... & -Mapping back because the object is moving over time - so you don't have to enter debits/credits, etc., etc. -Net profit from P&L goes right to Balance Sheet. Balance sheet where you eventually want everything to flow... balance sheet - a picture in time - point in time, am I in balance? P&L flows over time... length of time... net profit flows into (an equity on) Balance Sheet. ***We NEED or should create - that graphic/flyer, however you'd like to show it of the difference between T-accounts and how technology has improved to track things over time and map back and track everything -Web services and eCommerce - 3 letters of company and corp key id (i.e. mor-03 or use-53) to get into the shop eCommerce - go to the home page of adilas and add shop after the backslash, then put in the corp id - the use for testing playground: guest, 1234 -Once you know what containers you have put things in... then you can jump to them super fast... you know which drawer or container to go to, to find what you're looking for... -World building: characters relationships, trouble, decisions, consequences .... cause and effect |
|
|
AU 1803 |
|
Daily Ideas | 9/28/2013 |
Random notes – Woke up 3:30am and couldn’t sleep: - Use graphic mock-ups and layouts. No code is required and a picture tells a thousand words. Super-fast and it creates a model or goal to build towards. - Make graphic flow of different pieces. This could even be simple flow charts. - Use existing pages as default icons. - Get notebooks to my sister and get caught up on what is in the notebooks. - Help Steve push the adilas world to a real usable level. - Maybe think of small trial periods for approved persons. - I need to do more teaching and training. This could be in ColdFusion, adilas, or adilas sales and service. - Check out the operations seminar at USU. What a great resource. - I need to play as a team instead of just doing things all by myself. - Contact my brother and work with him on some of his commercial ideas and what not. - Get creative on funding and money flow. - Figure out new projects, scopes, and budgets. - Go back and review notes from 12/24/12 (December of 2012). Lots of good notes and ideas. - Figure out what is promised as far as tools and features. - Schedule the next training event. - Post the first round of the user guide. - Recruit internally. - Put Shari on task with the user guide. - Adilas university may end up being a non-profit. Until then, go ahead and just run it as it. We can transition later. - Get the database ready to be duplicated. - Finish up tools and features for eCommerce. - Get the content server up and online by end of 4th quarter 2013. - Organized and prepare the next whole level. Take adilas to the platform level. This is us dreaming to a super high level. Reach and stretch a bit. As a note, plan that this next level or model, at some future point, will also break and become a stepping stone. Include: custom css, layout, design, destinations, flow, tables, code, choices, in-line custom code, API options, pre-built templates, pattern after elements of time with build your own types and apply functions as needed. Be able to create your own flow and check points. Think of holding areas, checkpoints, permissions, and flow. We also need to add correct data mapping back to states and status and holding areas. Track the full life cycle of the items and transactions. - You dream it up – we’ll wire it up! - Show flow charts. This could be recommended flow, options, and special circumstances. - Use other people’s money to fund the projects. - We bring experience and vision to the table. - We will build on what we have. - The new platform level may need steps, phases, and different levels. - We at adilas need to follow our own advice and dream it up! - Document it, sketch it out, draw it up, and go to it. - Make visual homepages with icons and sections. - Get the notebook caught up… It takes extra effort to do things twice. Writing and sketching and then rewriting. - We have been planning this upgrade or next level for years. This doesn’t just come out of nowhere. - Think “platform”! Think “world building”! Think “in-line custom code”! - Make things consumable! - Plan the education and training from the get go or right from the start. This can’t be an afterthought. You almost plan it from the beginning and let it lead development. Then it truly becomes marketing. - The project for the developer’s notebook is very important. We have to share and communicate what is going on. This notebook is a huge part of our communication and direction. - Plan it out, seek help, use other people’s money to fund the projects. - Our plan is to share and seek protection out in the open by sharing. We also want to focus on the abundance model. Not only is there enough to go around, this model deals with more than money and business. My sister said the other day, this model also deals with people, skills, ideas, talents, drive, etc. Her saying that really helped my open my mind and think differently. -Start with education and an open API (application programming interface) or open source code. Those are two huge keys that we currently have shadows of but are lacking the full implantation of those features. - In order to get where we are going… You have to have some time in the game. - Education needs to be brought up to the marketing level. -We may end up leap frogging ourselves. That would be kind of fun. - Build to eliminate bottle necks in flow, processes, code, education, marketing, people, and other pivotal points. - We want to get marketing involved from the ground floor level. - On a personal note, I’ve done a number of projects and tried to market after the fact. That process is pretty tough. We need to see the vision and fund the projects with the vision. Self-funding is very difficult. - Plan for mobile and new technology! - Plan for data production and duplication! - Plan for snap-on and bolt-on additional features. It would be super cool if some of the code and features already anticipated external connections. Think application flex grid level. - Depending on our goals… we might need to start a whole new company or at least another arm of the current company. - Talking about new or extending business can be scary. It feels big! But, we’ve done this before and , most likely, we’ll do it again. - What about timing for this? That is still kind of a big unknown. - I am sad now. Sitting here thinking about the size of the project that we are currently in and thinking how big this current proposal is. In order to build, the weight, load, and wealth must be spread out. And then I start thinking... Build on what you have! And, the mode softens. I need to remember that saying. - Use adilas' existing base and experience to market the next level of growth. Again, build on what you have! - As an idea... I know of a company with a dream and they are daily building towards it. Would you like to hear more or become a part of that vision and dream? The company is called "adilas.biz". Come and check it out! - The taboo word is not "break" or "break it". The real taboo word is "eventually". This came from a small conversation during one of the lunch breaks during the Logan September adilas training course. - Choose your flavors (like an ice cream shop). - Pick your tools (like a tool shed or toolbox). - Skin your engine (like a vehicle). - Build your world (like worlds of a solar system). - This might be a fun part of the adilas formula flyer. Maybe replace the results section of the flyer. - Sample sketch of this idea (see photo gallery, sketch includes: Choose your flavor (ice cream treats), Pick your tools (tools for building), Skin your engine (different vehicles), Build your world (different worlds and planets), adilas logo in the middle. |
|
|
AU 1840 |
|
Daily Ideas | 10/16/2013 |
-Target, web – mix together to get --- (Sketches in notebook, see scans in photo gallery for 10/16/13) Each section is one of the main system groups or sections. In world building we use the following analogies….. - Human World ----- Adilas World - Universe Level – Different worlds or different companies inside the system - World Level – Imagine a single company or core shot of a virtual world - Location Level – Imagine the above model stacked or with multiple layers - Group Level – The groups are each full section from the center hub out in a triangle shape - Individual Level – The individual level deals with the outer ring or where the data is stored - Data Level – The data layer is an analogy of a play with cups or buckets on it. As data is added, it gets tied to the main and entered into a cup and/or bucket. - Run all levels over “time” – Create the business data assembly line with checkpoints and permissions. |
|
|
AU 1821 |
|
Daily Tasks | 10/17/2013 |
• Working on the Texas 130-U PDF document. • On the phone with Shari talking about Denver training session, a big projector screen, and ACH bank stuff. • Sketching out more ideas for the adilas GPS graphic. I want to add world building concepts and create a comparison between the human world and the adilas world. • Working on the Texas 130-U document. Ran into a ColdFusion and Adobe font issue. Light research online. • Went into BATC for day four of the adilas intern ColdFusion class. We did a light review, played with Flash interfaces, and started into ColdFusion. We made a bunch of hyperlinks and copied our basic template page. We did a little bit of cfif and conditional logic. Pretty good work session day. At the end of class I helped one guy with a mini project passing URL variables. He did well. • Working on the Texas 130-U document. Emails and a light touch-up on the adilas pricing matrix. Sent a copy of the pricing matrix to Steve. • More work on the Texas 130-U document. |
|
|
AU 1842 |
|
Daily Ideas | 10/18/2013 |
-On the adilas GPS graphic… Put the world building concepts first, then the adilas counterparts, then the GPS interface. Idea by my dad. • Human world building analogy on the left • Next verbage for the different levels • Next the adilas world counter parts to the human world building concepts • Next the adilas GPS interface model -On the content management system…. Harness the power of referencing a path to local files, remote access files (reference the URL), internal network files, or physical files that get uploaded to the servers. -Just an idea for the content management system… what if we could help a user upload their files to an outside storage system. Say: Google drive, Microsoft Sky drive, drop box, Adobe Creative Cloud, YouTube, Photo Bucket, Facebook, etc.? Basically, from adilas to something else. Then hold and store a reference or hyper link to that file or folder or directory structure. In a way use adilas to create a link in table of contents and reference library. We don’t have to store all the files… we may just need to allow for flexibility and then help people organize their stuff wherever it is located – whether it is local, remote, network, or physically on an adilas server. -Use the power of a hyper link to reference data wherever it is stored. They, hyperlinks, help the user jump right to the source. |
|
|
|
AU 2141 |
|
Adilas 3 Day Training Notes - Denver | 10/24/2013 |
Day 3: Oct. 24 -Think of adilas like a game... cause & effect, cause & effect... -P&L - runs over time; B.S. - snapshot in time; main players on the P&L - Revenue, COGS, Expenses -Revenue: more so what you are going to be taxed on... from Mick - the transfer of goods or services at a price.... so invoices (an investment would go on the balance sheet but it would not be inputted on the P&L -Henry Ford and the assembly line --- adilas ---- Adilas - a new tradition. -Adilas - so user friendly, so accessible --- and the connectivity is INVALUABLE! -Peachtree, QuickBooks. (Traditional accounting systems) are numeric or alpha-numeric systems.... whereas adilas is more an alpha system... much easier for the user. Also a traditional accounting system is a T-account or flat... whereas adilas is a multi-dimensional, mobile system... also units of measurement already built in to the system... incredibly enjoyable -Paul said this a cool way... with all of these worlds are stories so often they invite us into their world or for the story we experience things in "their" world, come into my world. But with adilas, it is... "What is YOUR world?"... Because we are here to help you create your world. How do you want to play? How can we help to build your world and help it to function? -System Assets: think monies you are bringing in, monies in; System Liabilities: monies, monies going out -Reiterate some of the small things when setting up... because often people get overwhelmed just b/c it's all new and you forget how and where or for instance things coming in... all need to come in on a PO for example... -Funny, but true, Roxanne says anyone that has done shopping online can do sales in adilas.... they might need some training and guidance for other functionality like adding in inventory, or doing accounting... but for sales, it is very logical and user friendly *The edit ability of adilas is a huge asset or benefit of using the system! ***Whatever you do outside of the system... do inside the system! -With verifying deposits and expenses... if they have been verified but they are wrong, you can back it up and actually un-verify it, then you can add/remove items... then you can go back and get things correct and you can verify it... a good way to back up if you made that mistake.... -Check your homepages so that you can see what you've been doing... sometimes people add so fast or use the back button and end up adding a whole bunch... so it is good to monitor and care for things.... Best practice: add things only once... then edit, edit, edit, whatever you need.... if you tried to add it, you might just need to search for it or figure out where to find it. -Verifying things... is such a great way to basically check done... to say yes, this is correct; I authorize that to move forward...... (On a PO, the specific verify date is not as important as the Expenses and Deposit verify dates... that is very important on those last ones) ***Idea/want to have: the ability to divide payments on expenses... or on paying off PO's with partial payments (divide payments like applying payments for our customers) -Creating actual objects allows for multi-dimensional relationships... it simulates and/or tracks what really happens in the world... with time, relationships, story, etc. *Don't be afraid to start playing... even just start with what you can start with... you can circle back around and edit if needs be, or teach the next step at the next time, etc. ***IDEA: from Uri, asking if we had thought about QR codes/swift codes for sending direct transfers, especially for those that are sending huge amounts of money to people ***IDEA: Quick exports to Excel... any page, any data... again from Uri -You are able to pull all sorts of data and reports from adilas... but you do have to know where to find it.... -adilas and others will sometimes trick out the system just a bit & put in a $0 expense to track their monthly bank statements.... so that they can have a holding place, attached to their vendor and then upload all the photos for their bank statement... so that they can document that along the way as well ****IDEA: a box on expenses that you can say how much you would like to pay, as noted earlier... that way it can help you calculate and do the math... -Splits allow for partial payments... but reimbursements do not allow for partials... so if you have a unique situation, you may need to play accordingly -I personally need to have a better understanding of items like equity, capital, user-maintained balance sheet items (the running, assigned, etc. what are the differences in those options, what does it mean?), (Learn what feeds automatically and what needs to be manually entered... and what situations), P&L statements, payroll, payroll taxes --- really just how a lot of the accounting works.... liabilities - loans, company distributions, assets... (So many places to get to this information... many great resources for understanding these processes... Shari had specifically been talking about payroll) -Other content bucket: local - is it on my C drive, F, my docs, etc., etc., etc. Remote - your YouTube account, google drive, sky drive, etc., etc. for both of these no costs just referencing to these files. Physical: pushed up to adilas servers and retrievable from adilas servers... that one they will have to charge for because of the space and potential file size.... but this is going to be SO neat! Really, the possibilities are SO immense. What kind of content do you use, what do you want?! |
|
|
AU 1853 |
|
Daily Tasks | 11/7/2013 |
• Emails and phone calls. • Research on the content server and uploading multiple files to the server. • Went in to town for a 3D simulation demo of a program for assembly lines and robots. I was trying to get ideas on how to show data assembly and real-time cause and effect relationships. Tons of ideas. See more notes later on for details. 30 miles. • Went to BATC to help the interns. We had 4 interns in class today. We talked about the 3D simulation demo and how we could do some of that kind of stuff inside of adilas. Things like building invoice, tying invoice payments to deposits, and recording accounts receivable’s back to customers. Good discussion. One of the interns shared a small lesson on regular expressions and how to use them. We then spent most of the rest of the day planning out page flow and how to optimize the traffic to and from the content server. Great brainstorming session. See the loose page dated 11/7/13 for notes, sketch, and flow chart. As a random side note, 3D simulations and modern day modeling are very similar to old school flow charts and diagrams. The main difference is feel, depth, richness, and animation of the process. Both show processes. One verbally and visually explains and the other is primarily a visual tool. • Spent some time talking with interns on individual levels. Listened to one of their ideas about a smart grid or custom component of sorts. Talked with the other intern about his role and where we are going. Spent some time copying ideas from the whiteboard brainstorming session on to loose paper and organizing some of the thoughts. |
|
|
AU 1857 |
|
Daily Tasks | 11/12/2013 |
• Paying bills. Called and reserved the Moose Lodge in Denver for the January 2014 training event. Started working on the new January 2014 training flyer. • On the phone with Steve. Talking about a custom label project. We talked about maybe piggy-backing on the custom documents section. We also talked about custom projects, interns, funding, and picking up the profitable byproducts that adilas creates. • Went in to Bridgerland for the intern class. One of the interns taught us a small lesson on chance and calculating odds. Lots of strategic planning. We made some more database choices by adding a new sub table and created some new reference id numbers for the media/content project. We worked on the physical, upload a file page inside of our project. 30 miles. • Cleaning up and chatting with the interns. • Went out to Smithfield to work with my sister and brother. Chatted with my sister about internal adilas teams and how we will be developing those teams to a fuller extent. She would like to be a part of those teams. I got nine new video files from my brother. I also gave him all of the files from the October Denver training session. We chatted lightly about direction and goals. • File management and uploading videos to YouTube. • Working on the adilas GPS (global positioning system) graphic. Working on the visuals for adilas world building concepts. |
|
|
AU 1883 |
|
Daily Ideas | 11/21/2013 |
-Thought about videos on adilas university… I thought that it might be fun to get some fun screen shots and show them as part of the video review. I was hoping that it would entice the users to want to watch and view the video clips. For example: video such & such (sketch on notebook page, see scans for 11/21/13) -On the corp-wide settings. Maybe put some basic info to help the people (our users) know that there are some other admin settings like: custom homepages, custom interface options, and tons of eCommerce settings that are available. This list may also include email invoice settings, special “hooks” to 3rd party products, etc. -On eCommerce… I want to make sure that a user (customer) can login even if no cart options are set. Basically, make the eCommerce backend be independent of the shopping cart and ability to show web inventory and items. -On eCommerce… we need a setting to control the default customer type for adding a new customer to the database. Currently the new customer gets to select what type they are. That could be a possible problem for some industries. -Time and space are two huge keys. Lately we have been focusing a lot on time and tracking objects and data over time. The other piece is “space” or organizing flow. In some ways, the word “interface” could be used as a substitute for “space”. The word space doesn’t have to be as big as what we think of space with planets, starts, systems, etc. It could be as small as your desk, your car, your home, your business, your interface. Space is a way to organize what you store or work with. This could be memories, letters, pictures, files, business data, transactions, etc. Things happen over time – we need to track that. As they happen we need to account for that or store that. How and where we store things, comes back to interface or “my virtual space”. I think it is super fun to think about how both time and space or space and time work and play together. This is virtual world building on a whole new level. |
|
|
AU 1893 |
|
Daily Tasks | 12/5/2013 |
• Brainstorming on server structures and world building concepts. See other notes a couple pages back. • Went in to BATC. The interns and my sister were there. We used the big white board to draw and sketch out ideas and naming conventions. We also found that the content servers may be a looser tie or relationship than originally thought. We took some pictures of the brainstorming session on the whiteboard. We watched a fun video about the data center of Facebook. That was pretty cool and made our project look much smaller. My sister did some training on recipe/builds and we had some fun playing around in those sections. • Light code work on the media/content project. 30 miles. • Brainstorming and sketching more ideas about world building levels and data structure pieces. • Went out to my brother’s house to get some more video clips. He had 20 new clips for me. 20 miles. • Emails. |
|
|
AU 1919 |
|
Daily Ideas | 12/20/2013 |
-When creating diagrams and flow… Maybe list the pages and organize them but don’t put any flow lines unless there is a built-in or automatic flow. This will allow us to do scenarios vs. a more rigid or mandatory process. Use actual mini page graphics. -Processes may start out pretty flexible but then may become more specific as things progress. See the driving to school analogy in the notes on 12/19/13. Idea came from my sister. -Graphical Interface Ideas…. (See scan in photo gallery) o Sub Homepage: map layout, sub homepage, world building concepts – group – use GPS and map layout graphics to help show world building concepts o Reports and options – search reports and special options o Individual Data Level – Individuals, Data, Run all levels over time – (use page icons to help with graphics and icons and buttons) |
|
|
AU 1906 |
|
Daily Tasks | 12/21/2013 |
• Playing with some ideas for a graphical layout. The idea involves page icons, names, and world building concepts. Also did some research on the structure of the universe and how clusters play in to that model. • Working with an intern on migrating code on the media/content project. We are taking his old files and bringing them into adilas as live files. Also working with another intern on new database tables, layout structure, and use cases. Good stuff. He made a small Microsoft Excel file with all of the new table names. • Tech support and emails. Sent an update email to a client about changes to new servers. Added a Christmas card to the news and updates page on adilas. It was a picture of Mary, Joseph, and baby Jesus. I also put up a general update about new changes and moving to a cluster based server model. |
|
|
AU 3634 |
|
Brainstorming: On the Adilas Team & Adilas Application | 12/31/2013 |
Scan: Notes from a meeting – Thoughts on an adilas team - Don’t lose the entrepreneurial spirit. That’s a gem! Dream it up and go get it! - Sometimes we may be missing a huge key piece of the puzzle. o Maybe a huge piece we are missing is the custom code work and consulting sections. We are allowing tons of outside reps & consultants make tons of money on our product. We may need our own little team that could capitalize on those pieces. o What are our inputs & outputs? o Where are our needs? o How can we solve those needs? o We need to help pick up what people want. - Keep building toward the dream. Spend time on where it needs to go. - Keep doing good and keep serving. Sometimes service pays more than hard money. Story about a guy buying a pack of cigarettes from a lady who was trying to quit. That little act of service was still in force 40+ years later. Great story. - Going back to the pieces we are missing. There are tons of jobs and projects. Let’s internalize them and allow other people’s money to help fund those projects. Why couldn’t adilas have a team that does sales, consulting, and custom implementation. That may be the next phase of growth. - On a different note, we really need to help map out the system. A virtual adilas “you are here” or a flow chart of what goes on. An adilas GPS system or sorts. Scan: Edits & Notes to the Results = Mix(Functions, Players, Concepts) Flyer (Please see scan in photo gallery) Get results by applying business functions, application players, and core concepts. Here is a quick look at what we bring to the table to help you run your business. Results = Mix(Functions, Players, Concepts) It would be so cool to make a flyer for each one of these things. Not just a flyer per section but a flyer per line 1-12 on all 4 sections. Results: (Turn this into questions & statements. Who, what, when, how, where, why?) What are you looking for? What is the goal or outcome? 1. Get Something for Your Pain 2. Make More Money 3. Custom Interface & Graphical Look/Feel 4. Flow & Processes (Logical, Smooth) 5. Tracking Numbers & Data Values 6. Tie-in Paperwork & Documentation 7. Archive & Storage of data 8. Search-ability – All Data Is Live And Searchable 9. Ease of Use 10. Custom Business Solutions 11. Other Goals & Output 12. You Name It… Dream it up, we’ll wire it up! Dynamic & Adaptable – Your e-Business buffet! Application Players: What tools are you going to use? 1. Customers 2. Invoices 3. Quotes 4. Vendors 5. PO’s (Purchase Orders) 6. Parts (General Inventory Items) 7. Stock/Units (Serialized Inventory) 8. Deposits 9. Expense/Receipts 10. Employee/Users 11. User-Maintained Balance Sheet Items 12. Elements of Time (Calendar & Scheduling) Business Functions: What do you want? How will you reach your goals? 1. Sales, Inventory Tracking, & POS (Point of Sale) 2. CRM (Customer Relationship Management) 3. CMS (Content Management System) 4. Online Expense Tracking 5. Payroll & Timecards 6. Calendar & Scheduling 7. Create Data Relationships Between System Players 8. Backend Office & Accounting Functions 9. Histories & Reports 10. BI (Business Intelligence) 11. Web Presence & eCommerce 12. Virtual Data Portal (Big Data) Core Concepts: Why & how does it work? Virtual world building… 1. Capture & Record the Story 2. Groups, Characters, Players, & Individuals 3. Relationships 4. Trouble, Problems, Needs, & Goals 5. Decisions & Choices 6. Consequences (Cause & Effects) 7. Accountability 8. Permissions & Settings 9. Systems Thinking 10. Vision & Future Developments 11. Tech, Tools, & Maintenance 12. Objects & Data Over Time Each corporation inside of adilas is its own little fenced in area or world… where only assigned users for that corporation may play and/or participate. Corp-wide settings allow for variations and custom usage of the adilas platform. Scan: Adilas Results Flyer Updated Adilas Results Flyer (Please see scan in photo gallery) Free Weekly Demos Scan: Sketch – One to Many Relationships, Mixing & Blending Sketch – One to Many Relationships, Mixing & Blending (Please see scan in photo gallery) Scan: Adilas.biz eBusiness Seminar Brainstorming Adilas.biz eBusiness Seminar Brainstorming Adilas.biz eBusiness Seminar flyer: - Business functions - More white space - Less wordy - More marketing • Sales, Inventory Tracking, & Point of Sale • CRM (Customer Relationship Management) • Payroll, Timecards, & Online Expense Tracking • Calendar & Scheduling • Backend Office & Accounting Functions |
|
|
AU 1948 |
|
Daily Tasks | 1/27/2014 |
• Emails and updating system time clocks. Made it so that all the servers had the same time zone. • Working on a web service to update the master corporation list. Signed off on code for the master list and posted files online. Activated the new master corp admin permission. • On the phone with Steve going over the new corp master list stuff • On the phone with a client going over parts, categories, recipes, builds, etc. He wanted to get things setup to help him in the bidding process. Other phone calls and tech support stuff. • Working on a new login page. Added the web address to the page. Added some world building graphics to the login screen. • Went to Denver with my sister for the January adilas training course. The trip went from 1/27/14 to 2/2/14. Total of 1,603 miles. |
|
|
Adi 838 |
|
Packages and Conversions | 2/1/2014 | Steve and Brandon had a brainstorming session on Saturday night. We talked about taxes per part category. World building levels and tons and tons on parts, conversions, and packages. | |
|
AU 1965 |
|
Daily Tasks | 2/1/2014 |
• Emails. • Pulling down a copy of the adilas database. This copy was as of 1/21/14, when we split the servers. Also working on search options for package and RFID tags. Added new search options to both advanced PO and invoice line item searches. Posted files online. • Recording notes and making a back-up copy of all code files. • Went in to Salida to work with Steve. I got him new code, new files, and updated his laptop computer. We then did three different brainstorming sessions. We did one full whiteboard on calculating taxes based on part categories. We did a full whiteboard session on world building concepts and how companies could possibly configure their worlds and universe related pieces. We then spent the rest of the evening going over RFID tags, packages, and conversions. This was a pretty long session and we got some really good ideas. As a note, we (Steve) took some pictures of the whiteboard. See element of time id #838 inside of adilas for the photos. |
|
|
AU 1969 |
|
Daily Ideas | 2/1/2014 |
-We need to create a graphic to help see the vision and features and potential. This deals with world building concepts. 1. Universe Level 2. Galaxies 3. Clusters 4. Solar Systems 5. Worlds 6. Locations 7. Groups 8. Individuals 9. Data 10. Run all levels over time -On locations and tax settings, add a new file that will allow taxes to be applied only to specific part categories. We are thinking a small text field and a comma separated list of categories. We would also like to link to a list of part categories to make it easy to get the id numbers. -Login idea – Currently, we require a login every time. Steve thought that it would be cool to help save some of those settings if a user registers a specific device or IP address. That might help speed things up, but it may also open up a possible security hole. Maybe store cookies or an actual database lookup. -On the hardcoded part number “verbage”, we need to change the price to $0 instead of $1. Idea came from a client. -Steve would like us to put a list of adilas clients online. This would be advertising for companies and might help with Google search results. This would be corporation name, address, city, state, zip, and maybe logo. As a note, we may need to allow corporation to show/hide this information. |
|
|
AU 2924 |
|
March 2014 Monthly Recap | 3/1/2014 |
This month adilas started holding weekly demos called “Cloud Software Demo – Challenging and Breaking Traditions”. A robotics teacher participated at one of these demos and helped contribute to a great discussion on how adilas is an assembly line for business data and business processes. From this session, and realizing the customization potential and flexibility behind this full business system application, he helped express some ideas that have been adapted to become a new adilas catch phrase, “Your data, your world, your way!”. The adilas developers and interns spent a great deal of time working on larger scaled projects such as the media/content server and mapping the adilas API. Extensive amounts of time have been spent planning, writing code, testing, signing off on code, and so forth, as these projects have gone to deeper phases of development. Adilas developers also received a request for their first custom PDF label this month. The option to assign default expense types per vendor was added this month, as well as the PayPal merchant processing gateway. Other working projects included payroll state tax withholding, photo galleries, increasing the auto increment maximums for invoices and quotes, and more. Adilas also held it's reoccurring, free monthly training event at Bridgerland in Logan, UT. *We hope you are enjoying the adilas developer's notebook! Please utilize and explore the vast search capabilities of adilas to find more information throughout the developer's notebook. For further questions, or help, please feel free to contact us at: support@adilas.biz. |
|
|
AU 2054 |
|
Daily Ideas | 3/6/2014 |
Notes from the first adilas demo and from a guy who teaches robotics at Bridgerland. -For the next demo… I would like to bring a banner, flyers, markers for the board, signs about where we are at, drinks, and all of the adilas toys (scanners, printers, card readers, barcode printers, barcode scanners, digital cameras, etc.) -World building – what does that mean and to what level are we talking about? How far do we want to take it? How far do you want to take it? -We offer the tools to make and create your own virtual assemble line. Processes or data points. -The robotics teacher, during the demo, really caught on to the data and process assembly line concept. He loved the fact that one, it existed, and two, that is was customizable. He thought that we should focus more on that vs. permissions and settings which allow us to do that. In selling terms – you sell the “sizzle” not the “stake”. I loved it! More notes from the first weekly demo that we did and ideas and notes from the robotics teacher. -Questions for people… Do you have any custom processes? What are your data points? How many places of entry do you have? Where is your pain? -We then come back and show how we can fill those needs. We have both custom and flexibility that are ready out of the box. -“This may be the only system that you need.” – Robotics teacher. -“Your data, your system, your world, your way.” Great little tag line for adilas – the “any” thing software. Dream it up! We’ll help you wire it up! -You control the process and your own virtual data assembly line. -There was a lot of focus on the words “you” and “your” and “yours”. Kind of interesting. -At the end of the demo the teacher went back to check on his class. After a couple of minutes, he came back while we were taking things down. He basically said, “You need to start selling this thing! It is ready! Put a stamp on it! You’re done!” This was dealing with me not letting it go because it isn’t done yet. I know that I need to get out of the way and let people come in and use our product. I’m trying to get out of the way! I really am! -Adilas – the “anything” software! -On training and demos… Help to solve problems, relieve pain and pressure points, help people! The pain could be disconnected systems, multiple points of entry, complicated processes, data tracking needs, bulk management, relationships between pieces and players, etc. -Explore and expand the social side of the web and customer interactions. This could be log files, follow-ups, elements of time, sub dates and time, sub comments, sub sign-offs, etc. Maybe allow some of these pieces to be used and interacted with from the customer login portal side. -On the customer web interactions – think about how companies want to interact with their customers. Currently most pieces of the communication train are verbal, email, written, etc. What if you could put everything all together in one place and allow interactions from both internal sources and external sources (customers and end users). That could be really cool! -What if we allowed some of the adilas CRM (customer relationship management) stuff to have a customer side to it. Meaning, the customer was able to log on and both see and interact with what is going on with their projects and pieces. -We may need some new settings to allow or deny access. We will also need show/hide options so that we could specify between internal, external, and admin only options. |
|
|
Adi 847 |
|
New tag line - Your Data, Your System, Your World, Your Way! | 3/8/2014 |
On 3/6/14 we had our first ever weekly sales demo. We called it "Cloud Software Demo - Challenging & Breaking Tradition". As part of the demo a guy by the name of Matt Fuller really caught on to the concept of a virtual data or process assembly line. He loved that it was super customizable. By the time the demo was done, he was highly recommending that we sell that part of adilas... After hashing some things around, we came up with something like this: Your Data, Your System, Your World, Your Way! This could be a great little tag line for the adilas "any" thing software package. You dream it up, we'll help you wire it up! Sell the "Sizzle" not the "Stake"! |
|
|
AU 2047 |
|
Daily Tasks | 3/8/2014 |
• Browsing the adilas site and checking usage for different companies. • Recording notes in notebook, reviewing to do lists, and trying to get organized. Added a couple new graphics to the adilas class and teaching photo gallery. Light research on robotic assembly lines. I want to draw a parallel between a robotic assembly line for actual products and an assembly line for business processes and business data. As a note, see elements of time inside adilas university. Do a search for “robot” and then do another search for “assembly line”. There are some good entries there. • Research on 3D printers and making objects. Emails, tech support, and recording notes. • On the phone with Steve and another developer who is setting up a page crawling engine to pull certain eCommerce and web data out of the adilas web services database for mutual clients. The data being extracted is only web settings for customer eCommerce inventory. Basically, this 3rd party engine will browse a company’s inventory and pull out names, descriptions, and prices. It then shows this data on its own server and just points to adilas servers if the viewer is interested in shopping or purchasing. It is kind of like a shopping app for specific industries. • Small tweaks on the adilas web presence and eCommerce pages. Added some links and changed some default values. Posted files online and let the 3rd party developer know about changes. • Changed the time zones for day light savings on all servers. Small tweaks to the developer’s helper page on the data 1 and data 2 boxes. • Made a few changes to a client’s website. Posted files online. |
|
|
AU 3681 |
|
Brainstorming - Adilas Business Functions/Features | 3/20/2014 |
This is a brainstorming document that was done from 3/20/14 to 3/27/14. It covers all 12 of the major business functions that adilas provides. The goal here is to focus more on the “sizzle” vs. the steak. The brainstorming was done by Brandon, Shannon, Dave, Cheryl, & others. Goal/Objective: Show & tell all 12 Business Functions/Features – here is what this can do. Brief definition – this is what this is. - What functionality – per business features – what, what, what – show me WHAT it can do. WHAT features does it have…. - From start to finish – follow this path all the way through – start to finish & review it 1. Sales, Inventory Tracking, & POS (Point of Sale): - Serialized inventory - Consignment inventory - Hide/show line items (hidden line items) - Advanced add to cart items - Barcoding - Package tracking - RFID Tracking - Custom labels - Paperwork – custom - Content Management - Photos/Images - Shopping carts - Duplicating - Vendor specific items - Generic items - Service items - Tiered pricing structure - Interface options - Dynamic cart interface - Quote – save as - Discounts - Contract pricing – using flex grid - Adjustable invoice styles - My Cart Favorites – Buttons - Recipe/Builds - Adjustable tax settings - Multiple customers per invoice/quote - Mixed tickets - eCommerce – Point of Sale options - Merchant Processing – credit cards - Customer queue - Item usages - Flex Grid - Transfers between locations - Update inventory count options – shrinkage/loss - Returns/refunds/exchanges - Tie directly to customer PO’s – dynamic fields - Custom search options - Sell anything! - Editable after the fact - Record notes – printable & non-printing - Searchable notes – searchable data 2. CRM (Customer Relationship Management) - Unlimited logs - Unlimited follow-ups - Calendar - Appointments - Bill for time - Track special data – customize your database - Additional contacts - Custom data fields - Paperwork - Photos/scans/images - Content Management - Export to Excel - Email/text message - Tie to specific sales associates - Current receivables – past history - Backend eCommerce login - Pay portals - Statements - Apply payments - Purchase history / statistics - Link to any other application piece - Custom search options - Trending & marketing 3. CMS (Content Management System) - Photos, scans, images - Reference any file – local, remote, physical upload - Unlimited & searchable reference library - Documentation - Custom documents - Paperwork - Contracts - Custom mappings - Direct to eCommerce - Your data, your system, your world, your way! - ??? – Something more… - Custom search options - Virtual World Building - Look & feel - What do you want? We’ll serve it up! - Mix & blend - Point & click interface 4. Online Expense Tracking - Reimbursements - Expense accounts - Payments on account - Payables - Access from anywhere - Enter data from anywhere - Print checks from anywhere - Bank reconciliation - Automatically cascades to P&L - Check requests - Check printing - Multiple payments - Documentation - Split between location - Aging, due dates - Dynamic reporting - Exporting to Excel - Bulk verify - Unlimited banks - Payroll - Custom search options - Photos, scans - Digital filing - Paperless office - Automated…. ??? - ACH & EFT’s – wiring money 5. Payroll & Timecards - Digital time clock – clock in/out - Admin time cards - Admin time clocks - Commissions - Salary - Overtime - Split deals - Hourly - Year to date summaries - Unlimited departments - Auto calculate federal & state withholdings - Summary reports - View/print my pay stubs - Bulk timecard options - Check writing - 1099’s - W-2’s - Automatic annual updates - Custom search options - HR management - Needed piece for every business – employees are used in other pieces of the puzzle – common denominator – wrap that up and present that well – potentially, on our side, take a day and create a few custom interfaces (that you could even flip to a mobile app) and just have this as an entrance (or get your foot in the door piece) - Compensation - Holiday pay/hours - Vacation pay/hours - Sick pay 6. Calendar & Scheduling - ANYTHING - How do you use time? - Appointments - Calendaring - Scheduling - Reservations - To-do lists - Projects – track subs and totals for projects - Servicing - Project management - Pools - Rentals - Dispatching - Bill for time - Reminders - Follow-ups - Notices - Dynamic naming - Create & name your own time templates - Scans, photos, images - Content uploads - 4 different report types/view: calendar, time slot, groups, & details - Advance searching - Add subs - Tie to customer, vendors, locations - Queue things to be invoiced - Project status – what needs to be done or what status is it at - Color code - Unlimited notes, entries, sub dates & times - Block out time spans - Packaging - GPS tracking - RFID tag tracking - Customer checkpoints - Document processes over time, with time - Customer facing calendar - Registration - Adding time to invoices & quotes - The underlying concept – ALL things run over time 7. Create Data Relationships Between System Players - Natural relationships - System maintained relationships - User maintained relationships - Special relationships – connections - Flex Grid Tie Ins - Custom fields - Customizable databases - Unlimited notes - Unlimited connections - Customizable reports - Relationship builder - Virtual buddy system - Process & flow relationships - Roll call – anytime o Who o What o When o Where o How many o How much o Who else – other connections o Why - Systems thinking - Cause & effects - Telling the story - Records all processes - Histories – system recorded histories – when/who did this? - User recorded histories - Linking within system groups - Core concepts - Accountability - World Building – creating realistic & logical relationships - Objects – objects & data over time - Multiple access points – multiple entry points - Visual organization & structure in data relationships 8. Backend Office & Accounting Functions - Automated Balance Sheet - Automated Profit & Loss Statement - User maintained Balance Sheet flexibility - Automates 75%+ of your financials - Live feedback - Live financial report for any data – even historical - Searchable - Editable - Build in audit trail - Tells the story - Tax reports - Automated cause & effects - Banks - Inventories - Receivables - Payables - Floorplan - Checkbooks - Check-writing - Payroll - Commissions - Withholdings – taxes - Shrinkage, loss - Documentation - Photos, scans - Content - Forms – standard forms - 1099’s, W-2’s - Operation led & accounting automated – horse before the cart - Simulate traditional accounting using modern technology - Business mapping data over time & data relationships - Entries are objects & portions of information progress/flow forward - HR management 9. Histories & Reports - ALL Data Is Live And Searchable (& retrievable) - Data in – data out - Usages - Histories o Financial o Effectual o Historical - System history for every action - Quick search - Advanced searches - Exports to Excel - Save as pdf - Print reports - Dynamic filtering & searching - Wild card searches - Drill-down to multiple layers of data - Any data in – is retrievable! - Build your own reports - Date sensitive reports - Pre-set criteria - Custom reports - Search & retrieve ALL data! - Know the data source – where is that information stored - Just in time reporting – live, flexible reports - Retrieve information for marketing, HR, sales, inventories, financials, trending, usages 10. BI (Business Intelligence) - Def: The pulse – what is happening in your business, who/what is involved, how does this play, they want to know the story – all of this is done with data, using data to tell the story, analytics, what does this mean, interpreting, marketing, trending, etc. - Provide the History & Reports *** - Usage - Interfaces – dashboard level - Return & report - Track usage, data, interactions, history, etc.: o Customers o Invoices o Stock/Units o Items/Parts, Inventory o Deposits o Expense/Receipts o PO’s o Vendors o Employees/Users o Quotes o Elements of Time o Balance Sheet Items - Relational data interactions - Dynamic data levels – unlimited – one to many to many relationships - Thank you adilas for making our lives easier! - Spend time analyzing & tracking data instead of building - Cutting edge – fastest browsers, new technology - Graphs, charts, visual representation for data - Data projections - Anytime roll call – return & report - Cascading, flexible, dynamic - Just in time – reports, history, recall, financials – what do I want to look at right now - Cloud based – centralized data – access anytime, anywhere - World Building: o Universe level o Galaxies o Clusters o Solar System o World o Location o Groups o Individuals o Data o Run All Levels Over Time - B2B or business to business interactions - Technology advances – memory, storage, processing power - Playing to where things are going - Future vision – anticipating, trending - The tools to reach future vision - Adaptability - Make appropriate changes according to your data - The data & reports to make your business decisions – research, marketing, trends, etc. - Affordable - Enterprise toolset for small to medium businesses - Cutting edge system for the right price - Grows with your company – reflects your - Time efficiency *** - Quick access & accountability for business functions - Business stimulating ideas - Project management – managing business - Entrepreneurial idea type system vs. more rigid/fixed systems - Multi-accessible, editable, adaptable flow vs. linear, rigid flow - A living tool 11. Web Presence & eCommerce - Online elements of time & calendaring options – scheduling, appointments, rentals, reservations, class seats, projects, timelines, check-off processes, etc., etc. (not exposed yet) - Online quotes/orders - eCommerce – cart to payment to shipping functionality - Continual updates & releases - Adjustable settings & eCommerce options - PayPal - Multiple Merchant Gateways – Authorize.net, Maxx Merchants, Merchant One, USAePay, First Data - Shipping API’s - Merchant Gateway API’s - Marketing/messaging API’s - Promotion codes - Special web pricing - Marketing – sales - Futuristically… smart menu – that helps track & calculate time according to the tasks you choose - Downloadable products – E-products - Customer login options - View user history, view your quotes, your invoices, your accounts - Online bill pay - Assign monthly rates for varying levels of customer use - Specify features for different customer types - What do you want your site to do? Dream it up! We’ll wire it up! - Full integration with your adilas system - Real time inventory counts & tracking - Free canned version with adilas subscription – custom upgrade to whatever level you want to play - Photo management - Descriptions - Categorization - Settings - Customizable look & feel - Connect the adilas engine to your already functioning website - Educate your users – CMS - Custom contract, disclaimers, agreements, paperwork - Link to external sources, upload additional content - Videos - Connect with social media – Facebook, twitter, LinkedIn, Pinterest, etc. - The entire adilas engine - Interconnected - Free - Ready to go - eCommerce ready to go POS system - affordable eCommerce packages - Show/hide things on the web instantly from within your adilas: locations, items, stock/units, contact information, etc. - Permissioned & protected inside adilas – then eCommerce – separate but fully integrated customer facing side - SEO automatically functioning: photo management, descriptions, your content (maximize for your company’s name) – to incredible levels - Contact us links - Future: mix & blend eBay & adilas & other big markets - Phone, call-in, mail order, - for web presence - Emailing invoices - Direct logins - Customer pay portals - Touch screen eCommerce – drag & drop - Multi functionality - Recipe/building 12. Virtual Data Portal (Big Data) - Archive data - The entire adilas package - Data sphere – data world - ANY data, ALL data - All file types - POS, eCommerce, scheduling, expense tracking, all of the 12 business functions here in one nifty little package - All Data Is Live And Searchable - Manageable data - Affordable data system - User friendly system - E-Business buffet – what do you want??? - Your business, your way! - World Building Concepts: - Cache, secure & retrieve data - Cross-company data sharing: vendor to supplier, or vice versa, to retailer, to … - Fun - Understand relationships – cause & effect - Systems thinking – systems working - Collect data as it’s happening – filter as needed, retrieve as desired - Searches data, crunches data - Data in bulk - Customer reports, returns - Unlimited data – mess volumes - Dream it up! - Work with the whole or filter down to smaller sections - Start to finish on processes - Plan it out – accomplish it in the system - Centralize the data - Follow the entire process through the data - View the entire history - Tell the story - Visualize it your way – graphs, tables, charts, rows & columns - Educate on big data – make it less intimidating - Making big data consumable - Normal operations create the big data – the sum of your normal operations create the whole – your big data - Creates all the connections & links from normal flow - Making informed decisions – make the best decision by having the best data - Making choices based on actual data - The whole, complete, inter-connected package - Build your world, create your interactions, populate your world, create your own processes, view any piece at any time - ADILAS – ALL Data Is Live And Searchable - It comes line upon line, piece by piece – normal operations –big data - The adilas formula is: Results = Mix(Functions, Players, & Concepts) - Tech, tools, & maintenance - Needs – trouble motivates action |
|
|
AU 2760 |
|
Daily Ideas | 7/25/2014 |
-Fix and modify the interactive map. Take off some of the prep pieces and add some other common features. Make it into a more full and ready to use interface. Add media/content, barcode generator, help files, YouTube videos, interface changer, etc. -On the world building flyer and concepts… Play with the world analogy… Where do you live? What is your environment? What will you encounter today? Tomorrow? Next year? What tools and features will you need? -On the flyer… use as few words as possible… make it a visual show and tell… Allow for them to drill-down or get more if they want it. -Add additional buttons to the new media/content icons and call-out navigation pieces. -On the GPS core and the interactive map… make the drill-downs go a little bit deeper and show an interface that shows options. Bring the users to a place that will educate and make choices easier by knowing what the options are. -We’ve had a number of requests to be able to upload multiple documents at a time. This is for both media/content and photos. -When showing each group or main system player group… show all of the pages and what those pages do. Help demystify how things work. Maybe even show a normal flow and cause and effects on how the items and data play together. |
|
|
AU 3699 |
|
Adilas Versions & Progression | 7/31/2014 |
Adilas Versions: - 12 years of progress - 8th version - Info graphics per year – 2001-2014 (See scan in photo gallery for sketches) Versions: 1. Inventory tracking system – Locations, employee/users, and stock/units (serialized inventory) – big ticket items 2. 3. 4. 5. 6. 7. 8. World Building -Base Camp -Anchors Versions: - Description/Features - Time 1. Version 1: 2001-2002 (?) - Inventory Tracking - Stock/Units or Serialized Inventory - Multiple Locations - Employee/Users - Role Based Permissions - Digital time clock 2. Version 2: 2002-2003 (?) - Full & General Inventory - Parts Department – General Items - Basic Inventory Point of Sale - Vendors, Purchase Orders (PO’s), parts, items, services, quotes, tax settings, invoices, and customers 3. Version 3: 2004-2006 - Payroll Reports, Commission Reports, & Withholdings - Stock Units - Floorplan app - Photo Management for Stock/Units - Web Presence for Stock/Units 4. Version 4: 2006-2007 – Full Rewrite - Full Rewrite with a New Base of Permissions & Settings - Changed from MS Access databases to MySQL server database - Banks, Expenses, Check Write System, Deposits - Invoice Rewrite to Open to Both Stock/Units, Parts, & Services 5. Version 5: 2007-2009 - Accounts Payable - Accounts Receivable - P&L – Income Statement - Balance Sheet - Officially Started Up Adilas (6/2008) 6. Version 6: 2009 - Merchant processing for credit cards - Recipe/Builds - Introduced corp-wide settings (custom naming conventions) - Web presence for parts & general inventories - CRM functionality & customer logs - Flex grid tie ins - Customer paperwork & PDF’s - Reoccurring invoices 7. Version 7: 2010 - Major work on corp-wide settings - Security settings tightened - Lots of new POS (Point of Sale) features such as o Barcode printing o Receipt printer invoices o Inventory ordering process o Dewy decimal – up to 5 levels of decimal accuracy o My cart favorite buttons – custom o Units of measure o Sales & profit reports o Advanced add to cart 8. Version 8: 2011-2012 - Elements of time – Calendaring & Scheduling - System designing & layout pieces and how they all worked together - Interactive map layout - More work on my cart favorites and other POS functions - System refinement - Customer queue - Smart groups and tiered pricing structure - Enhanced barcode search capacity - Duplicate PO - Choose interface options - New custom homepages 9. Version 9: 2013-2014 - Custom code & custom interfaces - Industry specific tweaks & charges - Built-in eCommerce and full web presence - Tons of new settings & permissions - Tons of training both online and live classes - Introduced World Building concepts - Lots of new flyers and graphics - Hired college interns to help with custom code projects - Over 100+ hours of training captured and edited - Lots of new YouTube videos - More icons & buttons - Added additional photo galleries for all 12 main system player groups - Migrated to multiple servers and further defined world building levels and definitions - Added full media/content (file management stuff for PDF, spreadsheets, word processing, graphics, images, video, and audio files - API sockets - 3rd party vendors - Custom code Update note: this was lightly recorded into the database on 9/20/14. See elements of time #873 in adilas or #2777 in the adilas university site. Recorded on 9/20/14. |
|
|
AU 3700 |
|
Brainstorming & Tech - Elements of Time | 8/1/2014 |
Adilas Versions: - 12 years of progress - 8th version - Info graphics per year – 2001-2014 (See scan in photo gallery for sketches) Versions: 1. Inventory tracking system – Locations, employee/users, and stock/units (serialized inventory) – big ticket items 2. 3. 4. 5. 6. 7. 8. World Building -Base Camp -Anchors Versions: - Description/Features - Time 1. Version 1: 2001-2002 (?) - Inventory Tracking - Stock/Units or Serialized Inventory - Multiple Locations - Employee/Users - Role Based Permissions - Digital time clock 2. Version 2: 2002-2003 (?) - Full & General Inventory - Parts Department – General Items - Basic Inventory Point of Sale - Vendors, Purchase Orders (PO’s), parts, items, services, quotes, tax settings, invoices, and customers 3. Version 3: 2004-2006 - Payroll Reports, Commission Reports, & Withholdings - Stock Units - Floorplan app - Photo Management for Stock/Units - Web Presence for Stock/Units 4. Version 4: 2006-2007 – Full Rewrite - Full Rewrite with a New Base of Permissions & Settings - Changed from MS Access databases to MySQL server database - Banks, Expenses, Check Write System, Deposits - Invoice Rewrite to Open to Both Stock/Units, Parts, & Services 5. Version 5: 2007-2009 - Accounts Payable - Accounts Receivable - P&L – Income Statement - Balance Sheet - Officially Started Up Adilas (6/2008) 6. Version 6: 2009 - Merchant processing for credit cards - Recipe/Builds - Introduced corp-wide settings (custom naming conventions) - Web presence for parts & general inventories - CRM functionality & customer logs - Flex grid tie ins - Customer paperwork & PDF’s - Reoccurring invoices 7. Version 7: 2010 - Major work on corp-wide settings - Security settings tightened - Lots of new POS (Point of Sale) features such as o Barcode printing o Receipt printer invoices o Inventory ordering process o Dewy decimal – up to 5 levels of decimal accuracy o My cart favorite buttons – custom o Units of measure o Sales & profit reports o Advanced add to cart 8. Version 8: 2011-2012 - Elements of time – Calendaring & Scheduling - System designing & layout pieces and how they all worked together - Interactive map layout - More work on my cart favorites and other POS functions - System refinement - Customer queue - Smart groups and tiered pricing structure - Enhanced barcode search capacity - Duplicate PO - Choose interface options - New custom homepages 9. Version 9: 2013-2014 - Custom code & custom interfaces - Industry specific tweaks & charges - Built-in eCommerce and full web presence - Tons of new settings & permissions - Tons of training both online and live classes - Introduced World Building concepts - Lots of new flyers and graphics - Hired college interns to help with custom code projects - Over 100+ hours of training captured and edited - Lots of new YouTube videos - More icons & buttons - Added additional photo galleries for all 12 main system player groups - Migrated to multiple servers and further defined world building levels and definitions - Added full media/content (file management stuff for PDF, spreadsheets, word processing, graphics, images, video, and audio files - API sockets - 3rd party vendors - Custom code Update note: this was lightly recorded into the database on 9/20/14. See elements of time #873 in adilas or #2777 in the adilas university site. Recorded on 9/20/14. Elements of Time Homepage Params FORM – URL – Defaults - Action status id o Action status • 1 - Assigned to id o Assigned to • Normal id = x + 0 = all, 1 = unassigned, 1,id = unassigned plus me - Block size o Block size o C-W • “ “ - Color value o Color value • “all” - Created by id o Created by id • 1 - Customer filter o Customer • “All” - Daily date, FORM time period = 1 o Lots of if statements to refigure FORM o Me period = 1 • “ “ - From date o From date • “ “ - General title o Title • “All” - Monthly date – 1-12, FORM time period = 3 o If blank set to current • “ “ - Monthly year – FORM time period = 3 o If blank set to current • “ “ - Quick jump date • “ “ - Quick jump frequency • “ “ - Quick jump value • “ “ - Report type o Group o Calendar o Details o Time slot o Type – required if going URL o C-W • “ “ - Show group subs o 1 = show o 0 = hide o Show subs o C-W • “ “ - Show logs o Yes = show o No = hide o Show logs o Run extra cfc • “yes” - Time block end o Sample – “5:00 pm” o To time o C-W • “ “ - Time block frequency id o 2 = sec o 3 = min o 4 = hours o Block frequency o C-W • “ “ - Time block size o Block frequency size o C-W • “ “ - Time block start o Sample “8:00 am” o From time o C-W • “ “ - Time period o 1 = daily o 2 = weekly o 3 = monthly o 4 = custom o Defaults are 1 & 4 o C-W • “ “ - Time template id o 1 = all numeric o Template • 1 - To date o Used with from date o To date o FROM time period = 4 • “ “ - Weekly dates o Filled if blank o “start date, end date” • “ “ Time #2773 |
|
|
AU 2792 |
|
Daily Tasks | 8/13/2014 |
|
|
|
AU 2794 |
|
Daily Tasks | 8/15/2014 |
|
|
|
AU 2810 |
|
Daily Ideas | 8/15/2014 |
-On the adilas GPS core layout, when the very center hub is clicked, show all of the different homepages with links to each homepage. Maybe set it up like the expanded chooser page with icons for the different homepages. (Or maybe it shows the map when the center hub is clicked.) -When we circle back around on help files, it might be nice to put a graphic of each page as part of the help file. A good example is the help file for the teacher/student interface (help id = 435). Notes on making full database copies: -We need to make a choice – add to an existing database or create a new standalone database. Our world building concept for databases is “solar systems” inside a “cluster” (box or domain name). -We need to be able to go both ways – new solar system or add to an existing solar system? -When copying, we need a master. A copy only works from a shared environment to a new environment. A copy may fail, due to id conflicts, from a shared environment to another shared environment. For this first round, shared to shared copies won't be allowed. Only shared to new will work for round one. -When checking between a master and a new solar system, do a query, check id's, and either insert or update depending on what we need. -Make it reusable for other corps. -I can see a future need for copying and moving from an existing shared environment to another shared environment. I wanted to avoid this crazy mapping and relationship stuff, but we may have to do it. Bummer! -We had a request to use the default invoice setting (print options) on quotes. Basically, the people want to go right to the mini quote once a shopping cart is saved. -On all new solar systems (new databases and database copies), add date indexing to all dates. This should really help with query speed. |
|
|
Adi 866 |
|
Intellectual Property Workshop | 8/21/2014 |
Brandon Moore, Wayne Moore, Cheryl Moore, Shannon Moore, and Dave Forbis attended a workshop on intellectual property in Logan, UT. The workshop was put on by the Small Business Development Center, Cooperative Extension of USU. The presenters were a law firm that dealt with patents, trademarks, copyrights, etc. See attached for my notes. What I got out of the workshop was basic information, timelines, ball park figures, and what is required. My favorite part of the workshop was dealing with how patents, trademarks, and copyrights can be denied and/or rejected. This might sound random, but I think that our goal is not to secure a patent on every little feature. Our goal is to defend patents being put on to core concepts. We need the model to be open and free. If not, it will swing power potentially in the wrong direction. So, in a nutshell, by us talking about things, publishing things, teaching, instructing, and building with openness in mind, we are helping to keep the patents out of the core of the ideas and concepts. Let people patent smaller pieces of the puzzle, that is no problem. However, we need to protect and educate people on the core of what we are doing. I have said this in private before, but I would bet that the core concepts that adilas.biz is built on are 100 times more valuable than the code that we have written over the years. There could be thousands of possible code angles on these same concepts. That is well and fine and a known fact. The important piece is protecting the core concepts and principles of what we are doing. We kinda fell into this... this wasn't our original goal. However, I do feel that we have some super important things that we are developing such as:
Anyways, those are some of the pieces that I see that we are doing and developing that could potentially be patented and/or copyrighted. They are listed here to start the process. |
|
|
AU 2774 |
|
Intellectual Property Workshop | 8/21/2014 |
Brandon Moore, Wayne Moore, Cheryl Moore, Shannon Moore, and Dave Forbis attended a workshop on intellectual property in Logan, UT. The workshop was put on by the Small Business Development Center, Cooperative Extension of USU. The presenters were a law firm that dealt with patents, trademarks, copyrights, etc. See attached for my notes. What I got out of the workshop was basic information, timelines, ball park figures, and what is required. My favorite part of the workshop was dealing with how patents, trademarks, and copyrights can be denied and/or rejected. This might sound random, but I think that our goal is not to secure a patent on every little feature. Our goal is to defend patents being put on to core concepts. We need the model to be open and free. If not, it will swing power potentially in the wrong direction. So, in a nutshell, by us talking about things, publishing things, teaching, instructing, and building with openness in mind, we are helping to keep the patents out of the core ideas and concepts. Let people patent smaller pieces of the puzzle, that is no problem. However, we need to protect and educate people on the core of what we are doing. I have said this in private before, but I would bet that the core concepts that adilas.biz is built on are 100 times more valuable than the code that we have written over the years. There could be thousands of possible code angles on these same concepts. That is well and fine and a known fact. The important piece is protecting the core concepts and principles of what we are doing. We kinda fell into this... this wasn't our original goal. However, I do feel that we have some super important things that we are developing such as:
Anyway, those are some of the pieces that I see that we are doing and developing that could potentially be patented and/or copyrighted. They are listed here to start the process. |
|
|
AU 2813 |
|
Daily Ideas | 8/21/2014 |
-Flood the market with ideas and concepts. Instead of trying to secure a patent on business world building concepts and practices, the goal may actually be to prevent patents on core pieces that are needed by businesses so they can go and do. -You have to give to get! Give people a taste... of what you've got. -You have to make things repeatable. Think, can anybody else do this? Can I put another actor in my place and have it succeed? If not, you need to get it to that level. Think of a play... Is it planned out enough that someone else could play that role? -You have to standardize things to a specific level. It doesn't have to be dry and boring, it can be super fun, but it does need at least a level of standardization. -Our clients are _________ (fill in the blank). Can I do this? If yes, what is the answer? Do I know who I am serving? Do they know what I'm offering? How does this interaction take place? Great questions. |
|
|
AU 2800 |
|
Daily Tasks | 8/22/2014 |
|
|
|
AU 2843 |
|
Daily Ideas | 9/6/2014 | -Thinking about the data and business assembly line concept. We've got to get that out there to the world. It deals with world building, automated pieces working together, and kind of like a robotic manufacturing facility – but for data and business logic vs. normal manufactured goods. The data assembly line for businesses. See notes back from 8/2/13. Also search adilas university for notes regarding “assembly line”. Lots of notes on the subject. This is the future of many businesses. It need to be protected as a general universal concept. We all need it! | |
|
AU 2844 |
|
Daily Ideas | 9/10/2014 |
-If we watch people use the system without any other information it may help us find the holes and pitfalls. That takes quite a bit of time, but if you don't have to explain everything, it actually saves you time in the long run. ////////////////////////// As a side note, we added a Word Document on 10/30/2019. Original date of the entry above is 9/10/2014. The new Word Document came from Chuck Swann, an adilas designer/developer. It was listing out some additional needs for schools. See this link for more info on that doc. |
|
|
AU 2846 |
|
Daily Ideas | 9/12/2014 |
Up early with seasonal allergies so I decided to do some brainstorming on what we need to require for adilas developers. New adilas developers will need: 1. These products installed on their laptop: Adobe ColdFusion 10 (or higher), MySQL 5.6 (or higher), and some kind of editor for code. Examples might be Adobe Dreamweaver, Adobe ColdFusion Builder, Eclipse, etc. The code editor needs to be able to handle HTML, CFML, and Java Script. 2. Other product recommendations are: Adobe Creative Cloud, Adobe Acrobat Pro (able to create PDF forms), MySQL – Front (database programming) and Microsoft Office products such as MS Excel & MS Word. 3. A basic understanding and knowledge of the following: • HTML Basics - Document structures - Links - Tables - Anchor tags - Frames and targets - Lists (bullets & numbers) - Formatting – bold, italics, underline, headings, fonts, colors, sizes, etc. - Nested tables - Div tags, alignment - Other tags – line breaks, paragraphs, horizontal rules, etc. • CSS basics • Java Script basics • ColdFusion basics - Comments - Variables - Cf output - Dumps - Scopes – variables, URL, FORM, application, session, etc. - Tables & HTML Forms & Form controls - Naming conventions o Database o Variables o ColdFusion o Etc. - Conditional logic – if, else if, else - Nested if statements - Loops – lots of different kinds o Basic index loop o Lists, arrays, structures, query o Nested loops - Lists - Arrays - Structures - Database Logic - Queries - Includes - Redirects - Parameters - Validation - Custom Tags - Functions & Methods - Complex Data Structures - External Options – Convert to PDF, Excel, Web Services, API, Email, Etc. • Database & SQL Basics - Relational Database Models - Select Queries - Insert queries - Update queries - Table joins - Scripting changes - Queries of queries (ColdFusion) 4. A basic understanding and knowledge of adilas, its form, function, structure, and vision. • World Building Concepts • One-to-many relationships • Permissions & Settings • 12 Main Application Player Groups: - Customers - Invoices - Quotes - Parts & General Inventory Items - Stock/Units – Serialized Inventory - Elements of Time – Calendar & Scheduling - Employee/Users - Vendors - PO's or Purchase Orders - Expense/Receipts - Deposits - Balance Sheet Items • Flex Grid Tie-Ins • Intro to Accounting • Photos, Scans, & Content • Payroll & Timecards • Web Presence & eCommerce • Locations & Tax Settings • Documentation and other developer specific topics such as help files, custom settings, navigation, and code sign-off's 5. Progress Reports, Testing Understanding & Knowledge, & Completion • Classes attended – list, sign, and date • Tests passed – list, sign, & date • Manuals, resources, code samples, etc. • Different Levels - Adilas Intern - Adilas Developer - Adilas Project Lead - Adilas Trainer • Completion Records - Sign-off's - Diplomas & certification • Adilas world Other notes: -Teach live classes for these subjects. Charge for the classes. Allow testing out of any subject. Charge for testing. Cap testing time frames as needed. Code samples on FTP servers. Use adilas university. Create actual manuals for both online and printable PDF's. Use GoToMeeting for online classes. Post class schedules and agendas and itineraries. Use elements of time to hold all of this stuff – as much as possible. |
|
|
|
Adi 873 |
|
Start of the adilas version control system | 9/20/2014 |
As part of the world building project and database copy we are adding some light version controls. This is a list of the prior versions of adilas before the database copy and split. Version 0 - Prior to 2001 Paper tickets, handwritten invoices, numerous spreadsheets, paper timecards per employee, Peachtree Accounting Software, mailing a zip disk from location to location to update inventory. This is where we started from. Version 1 - 2001 to 2002 Web based inventory tracking, stock/units or serialized inventory, multiple locations, employee/users, role based permissions, digital time clocks and timecards. Custom write up system for Morning Star Automotive out of Salida, Colorado. Version 2 - 2002 to 2003 Full parts and general inventory department, basic inventory point of sale, vendors, purchase orders (PO's), parts, items, services, quotes, tax settings, invoices, and customers. Version 3 - 2004 to 2006 Payroll reports & withholdings, commission reports, stock/unit floorplan app, photo management for stock/units, web presence to show stock/units to the public. Version 4 - 2006 to 2007 Full system rewrite, base of permissions & settings. Changed from MS Access database to MySQL Server database. Added banks, expenses, check write system, deposits, & opened up invoices to handle both stock/units and general inventory items and services. Version 5 - 2007 to 2009 Lots of new accounting features. Accounts payable, accounts receivable, P&L (profit & loss) or income statement, first rounds of the balance sheet. Adilas, LLC officially started in June of 2008. Adilas - all data is live and searchable. Version 6 - 2009 Merchant processing - credit cards, recipe/builds, introduced corp-wide settings (custom naming conventions), web presence for parts & general inventories, CRM functionality for customers, flex grid tie-ins, custom paperwork, and reoccurring invoices. Version 7 - 2010 - Part 1 Major work on corp-wide settings, security settings tightened, & lots of new POS (point of sale) features. New features: barcode printing, mini receipt printing, my cart favorite buttons, units of measure, sales & profit reports, & advanced add to cart. Version 7 - 2010 - Part 2 Major rework on inventory ordering processes and system. Allowed for generic mix vendor PO's vs. strict vendor specific PO's. Added a feature codenamed the "adilas dewy decimal" - up to 5 levels of decimal accuracy for costs, quantities, and prices. Version 8 - 2011 to 2012 - Part 1 Added elements of time, calendar, and scheduling. More work on my cart favorite buttons. Added smart groups & tiered pricing structure. Enhanced barcode search capacity. Added duplicate PO, choose interface options, and new custom homepages. Version 8 - 2011 to 2012 - Part Major effort to define how the system interacts and plays together. Lots of work on concepts (underlying core of the system). Added the interactive map layout and touch screen button interfaces. Also added the customer queue (virtual waiting room). Version 9 - 2013 to 2014 - Part 1 New custom code & custom interfaces, industry specific tweaks & changes. Built-in ecommerce & full web presence. Tons of new settings and permissions. Tons of training, both online and live classes. Introduced world building concepts. Version 9 - 2013 to 2014 - Part 2 Hired college interns to help with custom code projects. Over 100+ hours of training captured and edited. New videos put on YouTube. Started adding buttons and icons to pages. Added additional photo galleries for all 12 main system player groups. Version 9 - 2013 to 2014 - Part 3 Defined world building levels & definitions. Migrated to multiple dedicated servers. Added full media/content uploads for all 12 main player groups (file management stuff). API socket connections, custom code, and integration with 3rd party vendors. |
|
|
|
AU 2777 |
|
Start of the adilas version control system | 9/20/2014 |
As part of the world building project and database copy we are adding some light version controls. This is a list of the prior versions of adilas before the database copy and split. Version 0 - Prior to 2001 Paper tickets, handwritten invoices, numerous spreadsheets, paper timecards per employee, Peachtree Accounting Software, mailing a zip disk from location to location to update inventory. This is where we started from. Version 1 - 2001 to 2002 Web based inventory tracking, stock/units or serialized inventory, multiple locations, employee/users, role based permissions, digital time clocks and timecards. Custom write up system for Morning Star Automotive out of Salida, Colorado. Version 2 - 2002 to 2003 Full parts and general inventory department, basic inventory point of sale, vendors, purchase orders (PO's), parts, items, services, quotes, tax settings, invoices, and customers. Version 3 - 2004 to 2006 Payroll reports & withholdings, commission reports, stock/unit floorplan app, photo management for stock/units, web presence to show stock/units to the public. Version 4 - 2006 to 2007 Full system rewrite, base of permissions & settings. Changed from MS Access database to MySQL Server database. Added banks, expenses, check write system, deposits, & opened up invoices to handle both stock/units and general inventory items and services. Version 5 - 2007 to 2009 Lots of new accounting features. Accounts payable, accounts receivable, P&L (profit & loss) or income statement, first rounds of the balance sheet. Adilas, LLC officially started in June of 2008. Adilas - all data is live and searchable. Version 6 - 2009 Merchant processing - credit cards, recipe/builds, introduced corp-wide settings (custom naming conventions), web presence for parts & general inventories, CRM functionality for customers, flex grid tie-ins, custom paperwork, and reoccurring invoices. Version 7 - 2010 - Part 1 Major work on corp-wide settings, security settings tightened, & lots of new POS (point of sale) features. New features: barcode printing, mini receipt printing, my cart favorite buttons, units of measure, sales & profit reports, & advanced add to cart. Version 7 - 2010 - Part 2 Major rework on inventory ordering processes and system. Allowed for generic mix vendor PO's vs. strict vendor specific PO's. Added a feature codenamed the "adilas dewy decimal" - up to 5 levels of decimal accuracy for costs, quantities, and prices. Version 8 - 2011 to 2012 - Part 1 Added elements of time, calendar, and scheduling. More work on my cart favorite buttons. Added smart groups & tiered pricing structure. Enhanced barcode search capacity. Added duplicate PO, choose interface options, and new custom homepages. Version 8 - 2011 to 2012 - Part Major effort to define how the system interacts and plays together. Lots of work on concepts (underlying core of the system). Added the interactive map layout and touch screen button interfaces. Also added the customer queue (virtual waiting room). Version 9 - 2013 to 2014 - Part 1 New custom code & custom interfaces, industry specific tweaks & changes. Built-in ecommerce & full web presence. Tons of new settings and permissions. Tons of training, both online and live classes. Introduced world building concepts. Version 9 - 2013 to 2014 - Part 2 Hired college interns to help with custom code projects. Over 100+ hours of training captured and edited. New videos put on YouTube. Started adding buttons and icons to pages. Added additional photo galleries for all 12 main system player groups. Version 9 - 2013 to 2014 - Part 3 Defined world building levels & definitions. Migrated to multiple dedicated servers. Added full media/content uploads for all 12 main player groups (file management stuff). API socket connections, custom code, and integration with 3rd party vendors. |
|
|
AU 2834 |
|
Daily Tasks | 9/22/2014 |
|
|
|
AU 2851 |
|
Daily Ideas | 9/22/2014 |
-We need to tweak the adilas content server a bit. I would like to use it as a temporary storage server. That could be a spot where we could put older data that is not being used in a production or live environment. Eventually we will need an actual storage server, but the content server may work just fine for now. -Along with the changes listed above, I would also like to move the media/content files out of the top secret folder and into a content folder. That way, down the road, we could even configure a single server to be both a data server and a content server. The main top secret folder is used with session stuff and requires a valid login. If we created a content folder, it could be used for file uploads and file views. -The content server will need a database installed on the box. The plan is to use that as an alternate or low volume storage facility. This will be our storage facility for now. Set it up with all the new world building pieces. Plan for where we are headed. Think future. Ideas for a build your own label app: -Had a phone call from a client. It was dealing with a custom label request. By the time we were done talking her problem was actually at the time or sub inventory level. Interestingly enough, what she actually needs is a packaging application that includes a customized label. What I got out of it was we need a custom label maker that can be dynamically made, saved, designed, printed, sized, mapped to, and even help in controlling sub inventory and cost controls (packaging). -Use flash because you can control printing, sized, dynamic text, barcodes, etc. We could combine the precision of the bank check-write application (moving fields around using drag and drop or using arrow keys for exact positioning). We could click pieces or icons to add place holders. We could capture -x, -y, and -z (how long or left to right, top to bottom, front to back) coordinates. We could capture widths (length), heights (how short/tall), etc. We could allow naming of templates, naming of fields or placeholders, hardcoded values, text, and offer dynamic mapping options. We could allow graphics, lines, colors, etc. Each piece could be named, turned on/off, configured, and set up. -Notes from a sketch – please see scan in photo gallery: new template, save template, print test; setup the layout, the sizes, the fonts, etc.; click to add an option or feature: text, barcode, graphic or image, lines, draw (free form), where does the data come from – mapping and naming, positioning and sizes left to right, top to bottom, stacking and layers -x, -y, -z widths, heights; different tools such as a selection tool, a move tool, a trash can, a scale tool, a zoom tool, etc. -Be able to copy existing label templates. Be able to share them, use a direct API to add and edit them as needed. -Be able to tie a label to any of the 12 main system player groups. Once applied, allow for mapping options specific to those groups. -On the custom label making app... we need to allow users the option of doing a mini custom label to the existing barcode generator page or a full-on custom label using the builder. We could still use the mini label maker and barcode generator app with custom mappings and assignments. -On the custom labels... Allow flow through data to be set. Say a location, sub location, license number, or even a previous batch to flow through the process. This is part of the line of custody stuff... Bought it from here, sold it to here, sent it to here, back again, and then repackaged it and sold it here... This is just an example but it might be nice to be able to back track and find things. -RFID tags and other tracking numbers might be very important for tags and labels. Open up the external_alternate_id field on all 12 main system player groups. -On sub inventory and cost controls (packaging), be able to control how tight to monitor the packages. For example, able to sell to zero or unlimited. -The unlimited option may be useful for conversions. That is a small subject all by itself. -As a push for the custom label – I've got 6-10 custom label jobs sitting in my inbox right now. Instead of doing each one individually, I think we need to push this project forward and empower the users. -The big question... Flash or PDF – ActionScript 1.0 or ActionScript 3.0 – work as if for years! We need to go to Flash ActionScript 3.0. |
|
|
AU 2837 |
|
Daily Tasks | 9/25/2014 |
|
|
|
AU 2868 |
|
Daily Ideas | 10/9/2014 |
Just for fun.... Think about sub locations per system player groups.... Just showing 4 of the 12 main system player groups: Invoices: 1. Pending 2. Work in progress 3. Layaway 4. Shipping 5. Archived 6. Etc. Items: 1. Bin # 2. Pallet # 3. Bay # 4. Floor # 5. Area 6. Section 7. Room 8. Etc. Stock/Units: 1. Lot 2. Show room 3. Front line 4. Repair 5. Rental fleet 6. Etc. Employee/Users: 1. Department 2. Office # 3. Area 4. Team 5. Committee 6. Task Force 7. Probation 8. Etc. -Thoughts on sub locations.... What if we made a section under elements of time for sub locations. (Think of sub locations per main player group) We could allow each main system player group to have virtual sub locations. This is kind of new... Instead of a single set of sub locations, what if we could specify subs per group... For example, say subs for a stock/unit could be Montrose Colorado (main location), North Lot (sub location). The item still exists in Montrose but we also know a sub of the main. Where the new piece comes in is by main player group. Let's say we are doing some parts (general inventory) movement, we may not want North Lot as a sub location. What if we only wanted Basement or Storage? Basically allow sub locations per main system player group. A PO might want sub locations of pending, filed, to be paid, shredded, etc. (Different subs for invoice, PO's, products, employees, etc.) -I'm seeing an increased need to cross tie a single data object (invoice #777, PO #251, E/R #555, stock/unit #101) to subs of the elements of time features. This could allow for sub phases, movement, sub tracking, sub locations, sub assignments, etc. We could add time elements to each of the main system player groups. The other part of this new need is where the action takes place. Traditionally, all subs of elements of time happen from the main element of time. What if we stored the data under the main element of time but showed or allowed access to the subs from the host or parent data object. For example: Let's say that invoice #37 (host or parent data object) wanted to track how long it took to build something... We could use sub dates and times (sub of time) but have it show up and be editable from invoice #37. The person could be interacting with time without ever leaving the invoice environment. That could be really cool and has a lot of potential. Here is what it might look like: (Sketch – please see scan in photo gallery – Main system player groups who need to access subs of time... There are actually 12 main player groups – just added a few of them for this drawing: Customers, invoices, quotes, parts, stock/units, vendor, PO's, expenses... Elements of time as a wrapper or pass through to the subs or functions of time – some of the subs or functions of time: sub dates & times, sub locations, sub comments, sub sign-offs, sub payroll, sub reminders, sub GPS & RFID tracking, sub assignments... Basically, use the main elements of time as a wrapper or pass through to access any of the subs or functions of time. Gain access to anything using time as a wrapper. -Wow, I didn't know time and time functionality (subs of time) were so important. Basically, if we used time as the wrapper or pass through media, medium, vehicle, or channel... We could add additional functionality to all existing player groups and individual players. That could be so powerful! I'm excited! -Instead of making time a key player, in this instance or event, it will be almost transparent but will allow main data objects and groups to access additional functionality. -What if... we could create templates for each main player group (all 12). We could then allow access to subs of time based on settings per template. It gets back to “Types” and “Functions”. Both types and functions of time were major topics while we were developing the system section called elements of time. I'm seeing a potential to take those same concepts to all main player groups and even let main player groups connect to sub functions of functionality of time or other player groups. This could get deep, but basically defining different types and functions for the different players and player groups. -Once we define the subs or functions, we could allow cross tying or cross usage as needed. Basically, make everything part of a bigger interactive system or data sphere. Bring it all together into one bigger system. -Things would still have a home or default usage, but we could open up cross overs and functionality to meet the demands of a flexible and complete world. True world building. Taking custom to a new level. -A couple days back I was writing about real in-line extensions. Well today I was explaining the concepts to the adilas interns. I used a couple of small drawings to show them what we were trying to do and come up with. Here are some rough sketches of how I was trying to explain things... (Please see sketches on scans in photo galleries): new in-line extensions, pretend an existing database table, core system with possible extensions, flow chart or relationship model with some extensions, throw things in the bucket, predefined levels, bucket or main data object with subs... -Imagine a one-to-many relationship (main boxes and lines) -Then imagine the flexibility if you could virtually extend and control other needs and wants on almost any table or relationship. Look at the dotted lines. Think options and custom business or data solution. -Imagine a bucket with certain predefined sections or sub containers (how the bucket is organized). Then imagine extending or adding custom containers as needed. -Small fix is needed on creating an internal-repair ticket from a URL web link. If no prior location is selected, it drops the URL.stock value and the user has to re-enter it. Help them out by keeping the known stock/unit value going forward. |
|
|
AU 2863 |
|
Daily Tasks | 10/11/2014 |
|
|
|
AU 2870 |
|
Daily Ideas | 10/11/2014 |
-Using in-line extensions will give us the flexibility of Microsoft Excel with the power of a relational database and cloud based infrastructure. That will be awesome. -The key pieces are: 1. Centralize the data 2. Be able to collect and store the data 3. How to interact with the data 3.1. Interface 3.2. Flow & Processes 3.3. Analytics & Reporting 3.4. BI (Business Intelligence) & Big Data Space & Time Brainstorming: -Brainstorming on project phases and sub locations... Theses are subs of elements of time (and space). These pieces position or arrange how and where and what is happening or has happened or will happen. I think that we need to keep them subs or functions of time and space. However, I also think that we need to record the current state or status on the main. This allows it to be searched and referenced quicker. -We already store the action status value on the main elements of time table. These sub locations or projects phases would be the same way. We would hold an unlimited list of sub locations or project phases on or in the sub tables... but we would also make the current sub location or current project phase be part of the main element of time. -I'm really excited to see “space” or organization of time start playing into the mix. This is exciting! -If we are talking about subs showing up on the main individual data items or data objects, there are other pieces that want to be counted or accounted for. For example: Say a person was adding sub dates and times (virtual timecards) to a project. It sure would be nice if the total amount of time (sum of the subs) could show up on the main. All of the details are still held in the subs, but the current value becomes part of main. This is also true for things like action status logs, sub dates and times, project phases, sub locations, etc. -Elements of time and space need to be a foundational wrapper for all functionality for adilas. We already do this in a very light way. Invoices are assigned to locations and dated; PO's are assigned to locations and dates; deposits and expense/receipts are assigned to a date and one or more locations at a time. Inventory is tracked per location and by date (sometimes multiple dates). Almost everything we do has a component of space (locations and layering) and time (dates and date/time stamps). We already play this game... What if we just take it to the next level and allow the users to virtually wrap the system, the groups, and the individuals in both time and space? That would be awesome! -Time and space is ok (still works) but space and time sounds better. What about elements of space and time? -What if we add the word “space” into all of our pieces of documentation, literature, notes, quick search, etc. It may be made fun of at first but I think it could gain some ground especially if we start teaching and using those concepts together. -On the quick search – I would like options to search time or elements of time. I would also like a quick search option for space and time or elements of space and time. The space and time options could search much more and find all instances of things in both main and sub tables and database fields. If you searched space and time it could be the global adilas or all adilas searchable. -Locations and dates are a general way of saying space and time. We already knew that dates and times were important but we didn't know how deep locations or layering pieces would be (organizing your data). We've got to include space... It adds to and increases what dates and time can do by itself... It is a compound concept that needs both space and time! Think of our little assembly line graphic for our world building concepts... (Please see sketch on scan in photo gallery): -Space is how we organize over time -Pretend that the dots are checkpoints or key phases (dates/times) -Pretend that the top line is operations and the bottom line is accounting -Time goes both directions -Pretend that the vertical lines show permissions or access levels. Who gets to play at what level? -Pretend that the pods are areas or sub locations or departments (space) -In between checkpoints we have to allow some flex in the model -Lately I've been toying with the idea of a wrapper or a way to combine core concepts. I want them (core concepts) to interact and play together. I've been headed towards a wrapper of time (see entries from 5/22/14 and 6/3/14 in adilas university – developer's notebook). Anyway, my new direction is a wrapper or foundation of both space and time. You've got to have them both. -The bottom level (number 10) of the world building concepts currently says... Run all levels over “Time”. I think it needs to read – Run all levels through “Space” and “Time”. The word “through” may be a good general term for a wrapper, media, medium, or channel. We'll try that and see how it goes. |
|
|
Adi 893 |
|
Adilas.biz 3D Word Building - Graphic | 10/15/2014 |
This is a first round graphic dealing with adilas.biz 3d world building concepts. The graphic shows all three dimensions: x = time, y = money, and z = space. The graphic also shows some of the features that adilas.biz offers to their uses. These include: - Sales & Inventory - POS (Point of Sale) - CRM (Customer Relationship Management) - ecommerce - Calendar & Scheduling - Payroll & Timecards - Document Management - BI (Business Intelligence) - Backend Office & Accounting The graphic ends with the question... What does your World look like? |
|
|
AU 2787 |
|
Adilas.biz 3D World Building - Graphic | 10/15/2014 |
This is a first round graphic dealing with adilas.biz 3d world building concepts. The graphic shows all three dimensions: x = time, y = money, and z = space. The graphic also shows some of the features that adilas.biz offers to their users. These include: - Sales & Inventory - POS (Point of Sale) - CRM (Customer Relationship Management) - eCommerce - Calendar & Scheduling - Payroll & Timecards - Document Management - BI (Business Intelligence) - Backend Office & Accounting The graphic ends with the question... What does your World look like? |
|
|
AU 2879 |
|
Daily Tasks | 10/15/2014 |
• Recording notes and pushing up brainstorming docs to elements of time. • Research on barcodes in Adobe PDF documents. Reinstalling Adobe Acrobat Pro. • Drawing pictures comparing 2D and 3D objects in my notebook. This is basically the history of how our vision of the assembly line for data came about. Steve originally came up with the concept of the assembly line for data in 2008. As some of our meetings progressed, a number of questions came up about how to handle different scenarios. See elements of time in adilas university from January 2008 to December 2008. Search for the words “balance sheet” between those dates. Around November of 2008 we were getting pretty deep. It was then that Steve had to help explain that our job was to just show the data back to the user vs. forcing a perfect balance. He drew the original analogy of... Operations & accounting: Ideal in a perfect world or controlled environment vs. Real world requires flex and possible variables (please see sketches on scans in photo galleries). Original model or analogy done by Steve in 2008. • As of now, 10/15/14, that model has grown and developed into a full 3D (three dimensional) model using time, money, and space (depth) to track user’s actions and reactions. Basically a 3D cause and effect model. We call it an assembly line for data. See a couple pages back for a visual evolution of our model. • I couldn't help it... I was so excited about taking our data assembly line concept to 3D that I spent a couple of hours creating some adilas.biz 3D world building graphics. • Adding new 3D world building graphics to a new 3D world building help file. See the following web address – https://data0.adilas.biz/top_secret/help.cfm?id=483&pwd=building • On the phone with Steve talking about projects. • Worked on the show all help files page. Small tweak on the add/edit media/content page to allow a direct data drill-down link to occur or point to the underlying data or main tie-in. • Added the vendor as an output option on the grouped PO line items. Posted files online and did some testing. |
|
|
AU 2881 |
|
Daily Tasks | 10/17/2014 |
• Paying bills. • Working on the Denver training flyer for the end of October. The course was called new system updates and advanced backend office and accounting. Reformatted the flyer and added the 3D world building graphic on it. Sent it to Steve for approval. • Purchased a number of new domains. They are: 3DWorldBuilding.com, BusinessZipper.com, NewSchoolAccounting.com, RollCallAccounting.com, BusinessWorldBuilding.com, AdilasUniverse.com, and AdilasUniverse.biz. I’m really excited about some of those domain names! • Went with my dad down to Salt Lake City to meet with a potential client. They are an emergency preparedness company that wanted to see what we could do for them. On the drive down, I browsed their website using my dad’s hotspot while my dad drove. Once we got there, we met them at Village Inn for brunch. I used the interactive map graphic and the adilas GPS core graphic to explain core concepts. A gentleman and his web developer were at the meeting. They both had great questions and kept me hopping. I barely got to eat my meal. After the brunch they wanted a live demo. We then went to the web developer’s house to play with adilas. They kept throwing out questions and I would respond. They (combined) basically drove the demo by throwing question after question. Great session. As we were driving away, we got a call from him with some other questions. He had some excellent questions and you could tell that he was a very sharp cookie. 200 miles. |
|
|
|
Adi 895 |
|
Brainstorming session between Steve and Brandon | 10/22/2014 | See attached for brainstorming documents dealing with sub inventory and cost controls (packaging), recipe/builds (extending functionality), 3D world building (creating the whole system), etc. | |
|
AU 2885 |
|
Daily Tasks | 10/22/2014 |
• On the phone with a friend talking about projects and upcoming possible work options. He is a friend and full time web developer down in Salt Lake City. We’ve been good friends for years and years. • Working with an intern on getting his custom label layouts to show up correctly. • On the phone with Steve and a new developer going over sub inventory and cost controls. We talked a lot about recipe/builds, processes, pools, etc. Lots of new brainstorming notes on a Microsoft Word document from our phone call. See that word doc for details. • Emails and tech support. • On the phone with Steve going deeper into needs of the system and 3D world building – Everything is somewhat interconnected in a 3D system or 3D model of sorts. It is a system! • Recording notes and light phone support. • Back on in-line discounts. Working on new settings to help with discounts on the world or corporation level. New eCommerce settings, discount settings, and discount campaign options. • New logo for a company. • Working with my brother on his first ColdFusion training lesson. Working with variables. • Emails and phone calls about custom code, product uploads, product syncs, and custom exports from adilas to different software packages. • Working on new discount corp-wide settings. |
|
|
AU 2888 |
|
Daily Tasks | 10/25/2014 |
• Working on help files and prep for a meeting with a developer. Made some small needed changes to help files with documentation about login resets. Trying to make things more dynamic. • The developer came over and we worked on getting him started with the API socket or API parts (connections). We are going to call his project “wiring up the wall” so that we can let any outside party or parties “play at the wall.” The phrase “play at the wall” was mentioned by my dad as we were on a morning walk. We’ve used that phrase a number of times since then when trying to explain API socket connections (virtual data ports) to different people. See notes on other page for graphics that the developer and I drew to describe the process or concepts of play at the wall. • Working on help files for API socket connections or data ports. Lots of reading and writing. Trying to explain the process using analogies. • Writing up a help file to help explain 3D world building and business world building concepts. Included: x=time, y=money, and z=space levels and dimensions. Also included all 12 main adilas core concepts. I can’t wait to put graphics with the new help files. Help to both tell and show the story. That is the goal! |
|
|
AU 2889 |
|
Daily Tasks | 10/27/2014 |
• Adding 3D world building graphics and adilas GPS core layout graphics to help files. Posted new files online. • Working on new corp-wide settings for discounts and in-line discounts. • Working on custom discount setting for customers. Adding the discount campaign fields for customer. • Adding the customer discount campaign to different pages. • Adding fields to the advanced customer search page. |
|
|
AU 2891 |
|
Daily Tasks | 10/29/2014 |
• Emails. • Working with an intern and my brother. The intern was working on a custom PDF invoice and my brother was working on an intro to ColdFusion page. He was working with basic math and variables. • Working with my brother on variables. Working on adding two new system permissions. They are for my invoices – limited view per user and a new permission for a discount approver. This is a manager level permission to help with discounts. • Went in to Bridgerland to meet with a graphic designer about billboard and banner sites. Great meeting. We talked concepts and plans for just over an hour. Lots of little sketches about 3D world building, the data assembly line, API sockets and data ports. 30 miles. • Went to Preston, ID, with my dad to go to a meeting for the radio guys that helped with the Bear 100. Took a bunch of notes in my little green notebook. We then went to an ice cream Shoppe and talked about GPS event and race tracking using adilas as a backend engine with a cool and simple GPS app on the front end. Really good stuff and both my dad and I were really excited. |
|
|
Adi 901 |
|
New adilas banners | 10/31/2014 |
Here are two new adilas banners that will be printed and used at the upcoming trade show. Banner 1 - PDF - 11MB - https://data0.adilas.biz/public/adilas_banner.pdf Banner 2 - PDF - 12MB - https://data0.adilas.biz/public/adilas_banner_2.pdf The banner design was originally created by Steve using CSS (cascading style sheets) and graphics. We then had to convert the ideas to Adobe Photoshop in order to get the resolution high enough. Brandon did the Photoshop work and pushed the files up online. A lady by the name of Katrina Skinner helped with some of the data points and verbage. Banner 2 includes information and data about 3D World Building as well as other key concepts such as: assembly line for data, custom data engine, custom dashboards, and real-time data portal. |
|
|
AU 2788 |
|
New Banners for the Las Vegas trade show | 10/31/2014 |
Here are two new adilas banners that will be printed and used at the upcoming trade show in Las Vegas. Banner 1 - PDF - 11MB - https://data0.adilas.biz/public/adilas_banner.pdf Banner 2 - PDF - 12MB - https://data0.adilas.biz/public/adilas_banner_2.pdf The banner design was originally created by Steve using CSS (cascading style sheets) and graphics. We then had to convert the ideas to Adobe Photoshop in order to get the resolution high enough. Brandon did the Photoshop work and pushed the files up online. A lady by the name of Katrina Skinner helped with some of the data points and verbage. Banner 2 includes information and data about 3D World Building as well as other key concepts such as: assembly line for data, custom data engine, custom dashboards, and real-time data portal. |
|
|
AU 2893 |
|
Daily Tasks | 10/31/2014 |
• Swapped out the training flyer on the login page with a new banner ad. • On the phone with Steve. We went over some code questions and talked about upcoming projects. Trying to catch and communicate about the vision of where we are headed. • Working with an intern on graphics. Got him started on building his own icon menus for pages. While he was doing that, I was reworking some banner graphics. • Added 3D world building concepts to the banners. Purchased a couple new domain names for assembly line for data. • Finalized the new banners and put the high resolution PDF's online. I also added new elements of time with graphics and links to the new banners. The second banner has verbage and graphics dealing with 3D world building, assembly line for data, custom data engine, and real-time data portal. See elements of time #2788 in adilas university site or #901 in the main adilas site. Trying to start recording as we go vs. waiting until the end. |
|
|
AU 2964 |
|
Daily Tasks | 12/8/2014 |
• Reviewing notes from this last week. Crazy busy times. Lots of good stuff is happening. Also just to record this, I talked yesterday at church with a Sunday school teacher and computer guy and he would like to start working with us as an adilas intern. He will do great. I’ve been watching him for a while now. Good stuff! • New logos for some clients. Tweaked the code to allow .png (ping or programmable network graphics) as company logos. This allows for layers and transparent backgrounds. Also worked on moving the media/content code to the content folder. This will help us once we have to configure code to allow both a data server and a media content server on the same box. Anyway, just some prep work. • Helping an intern with some data import logic. Phone calls, tech support, emails, and finishing up little projects that were started. • Spent quite a bit of time writing up a new help file to explain the adilas formula or adilas.biz 101 flyer. See help file #487 for details. Lots of work on the 3D world building concept and capturing and recording the digital story. In my mind, those pieces are the goal. We’ll keep on building in order to reach and obtain the goal of full 3D World Building. |
|
|
AU 3002 |
|
Daily Tasks | 1/5/2015 |
• Uploading files tot eh adilas code bank. Sending an email to an adilas developer out of Nebraska dealing with FTP access to the adilas code bank. Other emails and recording notes on expanding the 3D World Building model to include other resources in the y axis or money scope. See notes on other page for more details. • Sent an email out the adilas interns with a light schedule of training times for January. • Emails and small code changes. • Fixing some links on the Learn to Freeride site. • Small code changes and updating files with verbage changes and minor code tweaks. • Went in to Bridgerland for the first of a multi-day, multi-week developer training session. No formal training but helped setup computers and laptops. We had a number of people there. My brother and I talked graphic and my sister and I talked training schedules. 30 miles. |
|
|
AU 3010 |
|
Daily Ideas | 1/5/2015 |
-Yesterday I worked with my daughter on photos for family history. I started her on some photo editing stuff. I have made it my goal to do at least two hours a week of family history. I’m planning to use adilas as the backend engine. I will create a skin for it and build whatever custom pages are needed. Here are some of my other plans: -For family history… We will use customer as people and individuals, we will use customer types as family groups or families. We will use a lot of flex grid pieces for custom fields and relationship builders. Elements of time will be big portion of the project. We may end up using media content to store video, audio, and other pictures, and/or documents. Lots of photo galleries for customers and elements of time. I also want to setup the pre-defined groups or pools for assignments to elements of time. We will use some custom interfaces and will make it as easy as possible. Ideas are just starting to formulate… This will be fun! -On 3D World Building… I had a thought yesterday about the y axis. Currently, it is labeled money. What if we left it as money but also included other resources. Using resources or expanding it to include resources is huge. X = time, Y = money, Z = space. 3D World Building Model: X = time, Y = money, Z = space (please see sketch on photo gallery scan). Trying to expand the definition of money. - A resource could be any number of things that you use or have available. A resource could be money (the x axis), but it could also be other things such as… materials, potential, skills, talents, and even time or space could be resources. The goal is to think outside of the box and think beyond normal money. - What about resources like: knowledge, experience, family, land, health, senses, (sight, hearing, touch, taste, smell), etc. - What about love, friendship, humanity, storage or built up levels of something. How about fuel, food, nature, air, water, soil, rocks, trees, beauty, etc. - What about talents and skills like: speaking, writing, acting, entertaining, leading, singing, playing, working, designing, developing, etc. Tons of possible resources may exist and/or be used. Think outside of the box and let the y axis be more than just money. Think about resources… on hand, available, acquirable, promised, used, and/or supply (not demand) levels. Good stuff! - What about people, personnel, science, technology, processes, intellectual property, customer base, data, databases, code, programs, etc. Resources don’t have to be money. - Resources usually need to be harvested and cared for. |
|
|
AU 3013 |
|
Daily Ideas | 1/9/2015 |
-We need to harness all resources. This may include the adilas content server and charging for companies that are over their limits. -Contact Dave (working with project management) to see if any projects are cooking and/or getting hot. We could use a good shot in the arm to help with funding some of these new interns. -We could gain a bunch by building out the database copy and duplicate process – World Building. -GPS tracking and round two of elements of time could help with future revenue and options. That project needs to get done at some point in the near future. -Sub inventory and cost controls (packaging) as well as a custom label maker app are also very needed. -What about other community funded projects. Open up the options. What about eCommerce templates or other templates. -The whole adilas API backend application. That has huge potential for future growth. -Steve is another huge asset. Many of the adilas custom projects go through him. All we need to do is ask. - We have had a number of requests to do a pricing tier based on a quantity of a group and/or category. We already do a single item tier based on quantities… but we don’t base the sum of each category on pricing matrix. Basically, people are wanting to group things together and then play as if that is the quantity based on the group not the item by item details. Maybe look into a switch or feature on the smart button that allows for things to be grouped by association to a smart button. This may require some math flipping but could be done. Ask a consultant out of Colorado if more info is needed. -As a note about the grouped quantity tiered prices… This may be something that could be run as custom code as the shopping cart gets built… Say the store is using barcodes… as it adds items to the cart… one at a time... it may not know what to do until it gets done or hits certain thresholds along the way. Say for example: Buy 10 of any kind of party pizza for $10 or $1.57 per if under 10. We may not know what we have until just as it happens. I would recommend that we add some kind of price and quantity and category watchers – in the cart – to handle this type of scenarios. It might need to check the cart contents every time a new item is added. -This may already be listed somewhere… but we have had request for discounts per category or per item category. For example: All backpacks 25% off, all climbing gear 20% off, selected camping items 25% off (limited or a sub set of the main inventory). We need to be able to cover both options. Also, I seem to remember a date range and/or a time range for these discounts. Say, a new sale from 1/15 to 1/21 or a reoccurring sale (happy hour) from 4pm to 6pm daily. Anyway, just some ideas. -Sometimes deposits take forever… we need to circle back around and check the tables, joins, and logic. The report that takes the longest seems to be the “payments not yet deposited” report under the running bank balance(s) page. |
|
|
AU 3014 |
|
Daily Ideas | 1/10/2015 |
-Another huge piece of the puzzle is the dynamic graphical user interface (GUI interface) with the adilas GPS core and adilas interactive map. I would like this to be done in Adobe Flash. -Another huge project is being able to save and create your own reports. This will be done with a page that collects the report settings and then saves the settings as a JSON object. Settings may be applied per page, per corporation (world), per user(s), etc. Basically, a custom option to save favorites, save reports, build reports, assign reports, etc. The data that gets saved needs to be able to be modified (edited) as well as copied to make other reports and/or assignments. Create your own favorite buttons. -I went to a planning meeting today for the youth of the church. I was impressed as I saw different groups of young men and young women meeting with their leaders to help plan the next six months. As I was talking with some of the other leaders at my table, we were talking about how members of the church are trained and able to work and do different callings and jobs. They each user their own resources and even pray for guidance and direction. We were having fun talking about how things work and how so many talented people come together to create great outcomes. I know that God is involved but we were really enjoying talking about the individual efforts of the members and people who are involved. Good stuff! -We are going to allow different parties to help and participate in different projects inside of adilas. We, adilas, will put a person over a specific project and then start building towards that as the goal. We gully know that some of these projects are way bigger than the people we will be putting on them. That is okay and we will use that as a learning and growing options or opportunity. Kind of like what God does for us. He trusts us with all kinds of things and allows us to grow along the way. I am grateful for the chance and opportunity to learn and grow. -A developer came over today. As part of our discussion we talked about opening up additional bays like a repair shop or garage. We also talked about a pool and how there is both a deep end and shallow end. These two analogies were part of our discussion talking about project management and trying to tap into resources. Repair Shop (see sketch in photo gallery – multiple bays and an office) - Garage with multiple bays or work areas. - Different developers may only be able to work on certain projects. Pool or swimming pool (see sketch in photo gallery) - Deep end - Shallow end - Cross cut of a pool - Different levels for different projects – match the level to the developer and the needs -Think of a team scenario… break projects down into the main components. Number the pieces, determine the levels, make assignments and plan accordingly. Almost like an assembly line for projects. Plan, prep, build, sign-off. |
|
|
AU 2933 |
|
Brainstorming on Round 2 of Elements of Time | 1/20/2015 |
Meeting with the adilas interns and going over objectives and scope for round 2 of elements of time. This will be the adilas project for the internship. We used two white boards and had an hour long session on what was included. See photos for more info. Image one has a list of database tables and which pieces are currently done and in place. There are a number of subs that still need some work. The first sub we will be tackeling is the sub GPS and RFID tag tracking piece. Our plans are to make a small sub project for training and then make it go live once everybody knows what is going on in a smaller scale. The other parts of photo one are a small flow chart of pages, the words functions (subs) and types of time applied to the templates, and a rough budget and timeframe for the project. The other image has a number of ways that people use time in their business. We listed and talked about a number of the different options such as: to do lists, basic calendar, reminders, tracking things, date/time spans, rentals, reservations, project management, events, schedules, appointments, meetings, seasonal things, marketing/sales/analytics, family history, inventory tracking, and dispatch. The other pieces of this photo are some small graphics talking about static vs. dynamic and some object lessons on one-to-many relationships. There is also a 3D world building model and how time, space, and money (resources) play into things. The last part is a small breakdown of time into smaller building blocks such as years, months, days, hours, minutes, etc. Great session and we should be starting on the process come next Monday as part of our class. |
|
|
AU 3583 |
|
Daily Ideas | 1/20/2015 |
I was reviewing my notebook (church one) from back on 10/10/14 and found some cool stuff on making the foundation a wrapper of sorts vs. a plain bottom level foundation. There are some good notes in that notebook. Here is an illustration that I liked… (Please see scan in photo gallery) - House on top of a foundation: foundation of a house. We place it at the bottom and then build up. - What if… the foundation is or was a giant wrapper. House built inside or wrapped inside of a bigger foundation. If God is our foundation… wouldn’t it be cool to have Him and His love surrounding or all around us – wrapped in His love. I think that would be cool. -Allow the media/content entries and/or pieces to be shown outside the secured environment. This means add a switch to make a piece public or customer facing (normal web). These pieces don’t have to be tied to anything and may be independent items. On the other hand… these media/content entries and/or pieces may be tied internally to an object or item inside. They can play either way –with or without a buddy. -The deeper we go… the more I see that harnessing resources and harvesting resources (both verbs) are so important. In our 3D World Building Model… they y axis is called “money” for something short and quick. However… it truly should be labeled resources. Lots of compound concepts… |
|
|
AU 3598 |
|
Daily Tasks | 2/14/2015 |
• Brainstorming on a way to teach developers how to work with data. See previous pages for notes. As an interesting side effect, the brainstorming session came back to a foundation of settings and permissions. That foundation leads into 3D World Building concepts of time, resources, and space. Kind of interesting. I think that I need to teach my guys about the foundation of permissions and settings. Help them get a solid base and then build from there. • Research and adding notes to my other notes. Having fun with flow and processes of working with data. • More brainstorming on moving and changing things over time. • Working on the flow for bulk and line by line in-line discounts. • Working on more on in-line discounts. • Emails • Working on outputting in-line discounts on printable invoices and save as pdf versions of invoices. • My brother came over and we got him paid for some training. He gave me a fun 3D idea for blocking elements of time. See next page. • Working on the printer friendly invoice page and showing in-line discounts. Sent an email update on custom code progress. |
|
|
AU 3603 |
|
Daily Ideas | 2/14/2015 |
-New graphic idea for helping developer understand the process of working with data – almost like a construction worker. (Please see scans in photo gallery) Inputs: Make a list of known inputs. What do you get or start with? Tools: Make a list of tools that you use to get the job or project done. Outputs: What did you make or get as an output? Imagine a funnel to slowly take a bigger raw input and get it ready for an output. -Elaborating on the new graphic idea to help developers with the concepts of working with data… (Please see scans in the photo gallery) Mini Version: Inputs: Start with? Tools: Outputs: Goal or end with? Funnel and reverse funnel effect – mix and blend as needed -Bigger Version: (Please see scans in photo gallery – lots of ideas) Input Types: - JSON – var1: value - XML – - Text – “something as text” - Mixed Data - Objects or structures - URL Data - FORM Data - Query - Array - Variable - List - Other/Custom - As a note… data could be any of the inputs – all kinds of stuff. Outputs: - Graphics - Tables - Reports - FORMs - Links - Navigation - Pages - Data - Other/Custom - As a note… data could be any of the inputs – all kinds of stuff. Tools: - Database - Spreadsheet - Text/Word Processing - Libraries - Traffic Control - Functions - Paper & pencil - Mind & head - Functions - API sockets - Parameters (windows & doors) - Conditional logic (if, else if, else) - Loops & steps - Graphics - Page Redirects & Reroutes - Dumps - Includes - Web - Apps - Software - Hardware - Data – see inputs & outputs - Includes - Validation - Server side code - Client side code - Multi-media - Custom tags - Other/Custom Tools - Settings - Permissions - 3D – Time, Resources, Space Start simple and work up from there -I’m running out of room… I’ll have to put this on its own page – these are just ideas. -The goal is to mix and blend as needed! -I’d love to add graphics or icons to all of these inputs, outputs, and tools. -See adilas university and search for “foundation” to get some good results. -As a small note… You start with known values that are simple… As you mix and blend and as things get more complicated… Things always seem to trend to “other” or “custom”. The word custom usually requires things like settings and permissions. Settings and permissions lead into our 3D World Building Model of Time, Resources, and Space. (3D World Building Concepts: X = Time, Y = Resources, & Z = Space) -Everything is inter-connected. -Permissions and settings may need to change over time. Think of how God works with His children… He places them in certain circumstances and gives them talents and trials. As time goes on and as cause and effect actions take place, God is willing to virtually change permissions and settings as needed. Change doesn’t have to be up or down. It could also mean front to back, left to right, diagonal, add or subtract, multiply, divide, etc. Granular or micro controls. God loves His children and helps us learn and grow along the way. I know He loves us! -This is a design idea that was submitted by my brother. My brother sketched this design while listening to part of an adilas intern training class. 3D Calendar Idea by my brother: - Imagine days of the month as 3D cubes or blocks: - (Please see sketches on scans in photo galleries) - Month: o Week 1: o Week 2: o Pretend it went from 1-7: S, M, T, W, Th, F, S, 8-14: S, M, T, W, Th, F, S and so on… Days and months Each day could be broken down into 24 hours. Each hour is a mini block. - Break each day into 24 hour blocks – single day - Take each day and block and expand it into 24 smaller blocks… Hours o This could go 0-11 am, 12-11 pm or 12-23 if on a 24 hour block - Days and hours Each hour could be broken down into 60 minutes. Each minute could be a small block of time. - Example: Monday, May 9th at 10:00am – single hour block of time - Break each hour into 60 minute blocks. Each minute could be broken down into 60 seconds. - Break each minute into 60 second blocks - Single minute - Minutes & seconds - Example: Monday, May 9th at 10:45 am It could go deeper but I think the point is made. Basically, a 3D calendar that could show any level of detail. I showed my model going from months, days, hours, minutes, and seconds. The model could also go up if needed to things like: months, quarters, years, decades, centuries, millenniums. Whatever you want. Think levels both big and small. |
|
|
AU 3600 |
|
Daily Tasks | 2/17/2015 |
• Writing and email and light proposal on breaking things into subs and doing some custom work. • Went in to Bridgerland to work with interns. Started out by helping an intern get an adilas system setup. We took about 2 hours and went over three main concepts. We covered permissions, settings, and time. I really enjoyed that session. It helps me see how each of those sections are part of the foundation. An interesting piece of that foundation is that all three parts move and change or may be changed. • I then worked with an intern on two different projects. We did a lot of white boarding and talked about the web/API socket project and new adilas black boxes for all eCommerce pages. We planned out the admin page for virtually opening and closing API socket doors and windows. This is part of the API socket project and starting to expose those pieces to the outside public. I • I then worked with two interns on World Building and splitting out the databases. We drew out the 10 levels of World Building and how the solar system level (databases) needed some help to become a one-to-many relationship so that each company could have its own database. After the brainstorming session, we put an intern on a small database copy project. • I worked with another intern on his mini project and we spent a lot of time working on validation and page flow. He has been doing good and well. Another intern was also there today and he was working with another intern. Very good day. 30 miles. |
|
|
AU 3604 |
|
Daily Tasks | 2/18/2015 |
• Went in to Bridgerland to work with the interns. Spent some time working with an intern helping him to copy and duplicate database tables. I also got another intern lined out on a part number migration for a company out of Orem, UT. 30 miles. • Went back to Bridgerland after a doctor’s appointment. Worked with two interns on world building and getting the database split up. I helped another intern with his API socket assignment page. This is a section where a user is able to virtually able to open and close API socket connections to the outside world, using a simple point and click interface. I also helped out another intern with his mini project and inserting data. |
|
|
AU 3609 |
|
Daily Tasks | 2/24/2015 |
• Went in to Bridgerland to work with interns on their projects. An intern and I spent the first two hours on World Building without any interruptions. Good session. • An intern came and we worked on his project for a client. He showed me his progress on the custom report and measurement form. We also talked about next steps and where things are headed. He is catching the vision and doing great. • I worked with another intern on his API stuff and looking over code. He is very fast and is flying and making progress on his projects. I spent some more time with an intern on splitting up databases and he was using my computer to do the code work. At the end of the day I worked with an intern again and then some with another intern. Currently, this intern is working on a dynamic search and output report for his fisherman’s app. The other person that I worked with today was another developer/intern. We spent a good 45 minutes together today working on creating and populating database tables based on functions and steps. Very busy day today. These guys keep me hopping! 30 miles. • Emails, paying bills, and recording notes. |
|
|
AU 3610 |
|
Daily Tasks | 2/25/2015 |
• Emails and updates on projects. Sent a number of large emails dealing with eCommerce, custom code, splitting databases, dedicated servers, and world building. Lots of good stuff. • Went in to Bridgerland to work on projects. I ended up talking to the Custom Fit manager from Bridgerland about a custom class and course tracking database project. He showed me their current Access database program and explained some of the ins and outs of what they do. I was quite impressed and enjoyed seeing the flow and options. We ended up spending just over an hour and a half with talking and a quick lunch. They need a system that tracks classes, teachers, students, costs, invoices, state funding, etc. Good little meeting. • I also worked with an intern on his mini project, his table joins and options for his little app. • An intern and I spent a couple hours signing off on his projects. He is doing super and has really taken off. Lots of work on the API socket pieces. I also helped an intern with some SQL and database questions. He is working and making progress on splitting up the database. Busy day today. 3o miles. |
|
|
AU 3617 |
|
Daily Tasks | 3/3/2015 |
• Answering emails and phone messages. • On the phone with Steve. We talked about different projects, needs, and who is on what project. We also talked about prices for 3rd party solutions and prices for general API socket usage. I really want to keep the general API sockets open and free. • Went in to Bridgerland to work. Worked with an intern on World Building and database work. I spent some time with an intern on Black Boxes and direction there. We even called Steve. See notes. • I worked with an intern on doing edits and coding the edit process. Two interns and I did a brainstorming session on black boxes, API sockets, and structure. Worked with an intern on his web/API documentation project. 30 miles. • Phone calls and follow-ups. Talked with project manager about some projects. He is going to start helping with project management stuff. |
|
|
AU 3618 |
|
Daily Tasks | 3/4/2015 |
• Paying bills. Emails and recording notes from yesterday. • On the phone with a software developer and independent computer consultant. He has worked for WordPerfect, Avery Labels, and other companies. WE had a good chat and talk. He may want to do some projects for us. • Went into Bridgerland to work with the interns. An intern and I spent almost the entire day working on the solar system – level 4 databases. Great session and lots of progress today. Two interns were working on adilas API sockets. • We took a break for an hour today to teach the guys some accounting basics. We used up an entire whiteboard and I had a blast showing how different things interact through cause and effect relationships. We talked about old school debits and credits (1494 A.D.), T-accounts, chart of accounts, P&L, balance sheet, adjustments, journal entries, ledgers, etc. We also talked about new school accounting, and 3D World Building. We talked about time, space, resources, money, flow, data assembly line, the story behind the numbers, checkpoints, flex, and roll call principles. Super fun… : ) Here is a small rendition of what the white board looked like… • See notes from 10/14/14 for more info on the progression and how we got to 3D Accounting and 3D World Building. Went through the whole progression: (Please see sketch on scan in photo gallery): (Includes: horse, cart & horse, Operations & Accounting flex bubble, Old school accounting and operations batching missing time (gap of time),T-accounts, 3D assembly line for data, 3D World Building (x = time, y = resources, z = space). |
|
|
AU 3623 |
|
Daily Ideas | 3/4/2015 |
-I had a lot of fun today talking about the progression of accounting… We went from debits and credits to cause and effect relationships as they flow and pass through space and time. Sort of an overview of old school accounting vs. new school accounting. See small drawing on other page. Fun little session. At the end of the teaching session… an intern wanted to see that – the progression and data assembly line for data – in real life – inside of adilas. We did some sales, deposits, and ran P&L and balance sheets to show what was going on. Good stuff! -I enjoy learning how things work. It has been super fun to learn things along the way. |
|
|
AU 3625 |
|
Daily Ideas | 3/6/2015 |
-The current goal seems to be breaking things down into small, more modular pieces and components. That is fin and well, but that could be a very large project. Good thing that we like huge projects. -I’ve been thinking about doing some Adobe Flash development. I would also like to learn more java script. Use black box concepts and make small Flash widgets, graphs, animations, etc. Think functional eye candy… That sounds fun. -Back on 2/14/15 I have some tools for working with data. We sketched out a bunch… That might be a cool Flash project… Here are some more ideas: (Please see sketches on scan in photo gallery) Data and tools concepts: - Containers or buckets - Video or multimedia - Smoke & mirrors - 3D World Building Model - x = time, y = resources, z = space - One-to-many relationships - Cookies - Cloud or session - Blender or mixer - Audio - Black box custom - Any device – client side or devices - Files - 3D Assembly Line - Adilas.biz - Graphs & charts - Calendar & dates - Time - Layers or stacking - Server side |
|
|
AU 3744 |
|
Daily Tasks | 3/10/2015 |
• Uploading files and doing emails. • Finished up the code for the advanced add to cart page. Uploaded files, tested, and even merged current branch into the master code repository inside of bit bucket. A developer has us working with some version control stuff to help coordinate efforts. • Went into Bridgerland to work. Did some email stuff and worked with a developer on some sales and consulting items. 30 miles. • Met with Dave on a client database project and proposal. We both then met with the manager for about 1.5 hours in his office. We took notes and he showed us around. After that, Dave and I met and went over things. We put some prices on paper and worked through the different parts of the proposal. • Working with a developer on the web/API documentation project. We also work on some printable layout options. • Conference call with a developer and a client out of California. We are planning a special roll call report that is a one pager. The report is a roll call page and is a cross between a P&L (Profit & Loss) report and a mini balance sheet. Eventually she wants the report to be exportable to feed an outside accounting program with mappings to specific chart of accounts and sub types. • Working with my brother on graphics and ideas for showing developers tools and functions. We looked at his pages and graphics and sketched out ideas. We also went through the progression of the data assembly line. Lots of sketches and drawings. We also talked about how our vision has grown over the years. • Working with my brother and a developer on different projects. My brother is doing graphics and the developer is working on the adilas API and getting things ready to release to the public. • Got a call from a developer. Apparently, another developers and I made some API socket changes that effected this developer’s 3rd party socket settings. So, I went in and made some tweaks to make things work. Made some changes to the web/API documentation process. This allows different access levels to the API sockets. We have normal, 3rd parts, universe, internal, and demo options. |
|
|
AU 3746 |
|
Daily Tasks | 3/12/2015 |
• Went in to Bridgerland to work with my guys. Started out the day working with an intern to see how his training is going. • I then worked with another developer to help restore his local database. Once we got that going we worked on World Building and splitting apart the main database. • Most of the day was spent with a developer working on looking over code and working together on his new code to copy and transfer full tables between servers using crazy dynamics and API sockets. Pretty intense. The developer came up with the plan. I mostly just helped with debugging and consulting type stuff. 30 miles. • Reading a letter that my dad wrote to a guy who is very good and GIS and GPS about 3D event tracking and plans to head in that direction. My dad is really excited about the 3D event planning and 3D event tracking stuff. |
|
|
AU 3749 |
|
Daily Tasks | 3/16/2015 |
• Emails about quantity monitoring per cart and advanced options for flex grid and custom PO settings. Wrote another email dealing with copying invoices between systems. • Reviewing and reading over a proposal that Dave sent to me in regards to a database project. This deals with students and clients, etc. • Meeting with a new developer. We went over some needs, dynamics, commissions, options, current status on some different projects. I showed him our current label and barcode generator app. We talked about future label needs for shipping, packaging, invoicing, etc. Tons of different things. We also talked about training and the need to help with video and media based training for different organizations. We talked about the potential of mixing the LTF (Learn to Freeride) project with the adilas media/content project. That will be fun to get that all put together here soon. Good stuff. • Emails and recording bills and invoices from the developers. • Working with a developer on a custom project for a system-wide roll call page. Basically, it is a cross between a P&L and a balance sheet. The end goal is to feed in all known compartments and daily sums into hidden system-wide elements of time to hold the daily roll calls and daily sums. Anyway, he is working on this new report for a client. • I also helped an intern on some World Building pieces to migrate huge tables with data. Other random phone calls and emails. Reading up on ColdFusion code frameworks. An intern wanted me to read up on these as an option. |
|
|
AU 3750 |
|
Daily Tasks | 3/17/2015 |
• Reading over and editing a request for proposal for a client database project. Original proposal was done and written by Dave. • Went in to Bridgerland to work with my guys. Totaled up hours of instruction for January, February, and March so far… We are over 1,000 man hours working with the interns and new developers. That is awesome! • I worked with an intern signing off on some code. We lined out the next little part of the World Building project. We booked another month there at Bridgerland to use their facility. • Another intern came in and we had a great class discussion on application and page setup and frameworks. We filled up the whiteboard and talked lots of concepts. We also determined a couple of other needed black boxes. We decided to get rid of the side bar left and side bar right black boxes. Those are part of the body. The two new ones are head or top part of the HTML and end or bottom part of the HTML. These places allow for css, java script, JQuery, etc. • Bridgerland was a happening place today. We had guys working on World Building API documentations, graphics, project management, proposals, graphics, and finishing up mini projects. • I was working with my brother on his projects for his internship. His graphics and web pages are looking good. His project is showing financial flow for simple sales and inventory tracking. He and I also went through a midterm evaluation. He scored very well. He is doing great. • Dave and I then went over a proposal for the client database project. We read through the document together and made some notes on changes. • I then worked with an intern on his mini project. He is getting closer on finishing it up. It is a small fisherman’s app to record fishing trips. Anyway, we worked on database updates and page flow. • While I was working with different people, a developer was helping to coordinate other projects and working on API socket stuff. He is doing a great job. 30 miles. |
|
|
AU 3767 |
|
Daily Ideas | 3/18/2015 |
Possible community funded projects: - Sub inventory & cost controls (packaging) - GPS & GIS – subs of time - World Building - eCommerce face lift - Black box project for custom code - Ice-down date - Sales & promotions - Emailing invoices & quotes - On-line customer bill pay portal - Customer loyalty points & gift cards - Automating more of the balance sheet and financials - Sub locations - Sub phases - Open up the full adilas API socket back end - Etc. - Tons of options: - Reflexive side of the flex grid - Real in-line extensions - Custom dynamic labels - Dynamic roll call page - Custom page settings -I need a mini receipt to help out with split invoice payments. I’m thinking about community funded projects and invoices. Basically getting payments from multiple sources for a single invoice. -On the community invoices… I’d like to use the water, slush, to ice analogy for these projects. Liquid and loose at first and then getting more and more firm as the projects get funded. As things get funded, we’ll firm up deadlines, details, and full project details. It is ok just to start and go from there. |
|
|
AU 3752 |
|
Daily Tasks | 3/19/2015 |
• Big email report about the progress on the adilas API sockets and customer facing API. • Went in to Bridgerland to work with my guys. I worked with an intern on the API documentation project. We made some small code tweaks and then rolled into the copy and paste process of harvesting code and comments for documentation. I had a fun meeting with a guy out of the Logan area. He is a sales rep and business job coach (consultant). Anyway, we met and chatted about options for using and selling adilas. He is all about simple and being willing to break tradition. We had a great chat. He showed me some cool online apps for smart phones and other devices. We talked about possible 3rd party integration or development of our own apps. We then went up to the whiteboard and had a fun little session. I really enjoyed the meeting. • Worked with an intern on more world building and data migration. I also met with another intern to go over a request for proposal. This is for the client database job. • Partway through the day today, a developer and I had to fix some errors and error messages on both data 0 and data 2. Things are definitely getting more complex with multiple servers, test environments, live environments, and multiple developers playing the game. It got a little stressful due to some unknowns and users not being able to access certain pages. • I worked with a developer on getting up some new code to track and monitor errors and error handling. He wrote the code and I helped debug and guide the shop. Awesome day! I’m so grateful that I have some help to push some of these new projects ahead. 30 miles. • A developer came over and up from Salt Lake City. We went over some of his code that he wrote for the adilas API sockets. His code is done in ASP.net (Microsoft active server pages or dot net code). We are planning on having a number of code libraries and demo apps to help other developers get started on some custom code. We talked about lots of future options and had a good time. We got him all paid up and I got his new code files. He is a great guy. I’d love to see him be a part of our team as we go down the line. • Made a couple of late night code changes to help with some reported error messages. It’s been a busy day today. Small tweaks to discount campaign tracking and custom PDF labels. |
|
|
AU 3757 |
|
Daily Tasks | 3/25/2015 |
• On the phone with Steve going over the API socket pieces and what is needed and what is done. • Went in to Bridgerland to work. Spent some time with an intern on database World Building stuff. Helped another intern on some data migration stuff. Got another intern started on some code to help save report settings. If we could save some reports per user and per corporation… that would be awesome! 30 miles. • Conference call with my dad and a guy who specialized in GIS. We talked about apps, services, modems, SMS messages, cell and cellular data packets, and even options for GPS as a service. Great call. My dad and I figured out that GPRS modems were a huge key to the GPS data world. GPRS stand for something like… Global Packet Receiving Model… or something like that. Basically, it is a hub or modem that sends and receives text messages between GPS units, cell phones, and other devices that play in that world. He helped us with some great break-throughs. I was very impressed. See additional notes later on. • Helping interns on their projects. • Conference call with a client. My sister, two developers, and I were on the call. Great call and we had some good discussions on different topics. We talked about PayPal, skinning the shopping cart, distributing costs of goods sold, affiliate programs, email and text message blasts, and referral marketing. We briefly talked about site analytics and point systems. We committed to some deadlines and promised a written proposal of work that would be done. Exciting times. • Worked with an intern on some API socket documentation. I then spent some time with another intern doing customer migration stuff. |
|
|
AU 3758 |
|
Daily Tasks | 3/26/2015 |
• Went in to Bridgerland to meet and work with my guys. I did some prep work and drew a full page diagram that showed the existing eCommerce and shopping cart interface. It was kind of fast and kind of rough but I got it done. As a note, way back, we decided that a just in time map and navigation process would be really cool. Instead of drawing tons and tons of lines all over the place… it would be cool to show progression and options based on scenarios. That would be cool. Sadly, this quick graphic was not like that, but at least it helped. • Anyway, we had a group meeting and brainstorming session. We had 8 of us there. We drew on the whiteboard and all of the guys participated. Fun meeting. Lots of vision and potential. • We talked about new changes, deadlines, eCommerce, how eCommerce is so powerful when connected to the whole operations and accounting side of the equation. We talked about black boxes, concepts, shells, skins, web hosting, domains, sub domains, and API socket integration. The guys were pretty in to it and were catching the vision. • After the meeting, I worked with an intern on data imports and migration. I also worked with one of the interns on saving report settings and another on his copy and paste project to help with documentation. Worked with another intern on World Building and splitting out databases. • Went over to the Cache Business Resource Center to meet with a gentleman. We chatted and he asked some questions about our product and what we offer. I drew some sketches and we chatted. He then offered us to use the CBRC (Cache Business Resource Center) for things we needed for adilas. He will be a good connection down the road. • Went back to Bridgerland. Worked with two developers on their new eCommerce pieces. Talking with a developer about future plans and potential. The guys are excited. • Another developer came over and we worked on Oregon state tax withholdings and tax stuff. • On the phone with an intern. We did a GoToMeeting session and looked at his database migration code. It looked good. We decided that we needed to add a new field for customer SSN (social security numbers). We also need to encrypt that value for storage. |
|
|
|
Adi 985 |
|
Sub Phases Or Checkpoints - Sub of Time | 3/30/2015 |
Currently can use sub phases with sub flags and tags. Developers are currently using this. Still need to implement checkpoints ex assembly line. |
|
|
AU 3762 |
|
Daily Tasks | 3/31/2015 |
• Went in to Bridgerland to work with my guys. They are all doing well. I worked with an intern and made some code changes to help the web/API documentation stuff work better. We added a number of links, verbage changes, and navigation options. I then spent some time with him doing line by line documentation checks and tweaks. • I had a great meeting with a local consultant and his partner. We chatted for a bit and then moved over to the whiteboard. We talked about systemizing things, data assembly line, and 3D World Building. Great meeting. They scheduled another meeting for next Tuesday to see a demo. • Spent time working with other interns on their different projects. 30 miles. |
|
|
AU 3778 |
|
Daily Tasks | 4/2/2015 |
• Went in to Bridgerland to work. Spent the first little while working with an intern on splitting up main invoice tables and invoice payment tables. This is a mini surgery in the mist of the bigger database split up and World Building project. 30 miles. • On the phone with interns going over code to add the social security number to customer records. I was at Bridgerland with one of interns and the other was joining us from home because he was sick. We worked on the code to add the new filed and then to encrypt the data for storage. • Working with an intern on splitting out databases and invoice payments. I worked with another intern on saving report settings into JSON for later use. • Back on a phone call and GoToMeeting session with the two interns. • Working on new code to help cascade new fields and changes around the system. As a funny note, part way through the afternoon, the fire alarm went off. We evacuated the building. The college was on Spring Break so hardly anyone was on the campus. So, once outside, me and my interns, my guys, we got a Frisbee and played catch in the parking lot until the fire alarm went off. It was really fun and made everybody in a slap stick and funny mode. Good stuff. |
|
|
AU 3793 |
|
Daily Tasks | 4/16/2015 |
• Reviewing the day from yesterday. • Follow-up emails and checking in on a couple of proposals that I’ve got out for some potential client projects. • Other emails and tech support. • Went into Bridgerland to work with my guys. • A developer showed me a new import tool that he is working on. He is very good at tools and processes. • I spent most of the morning working with a developer on cleaning up a code branch on bit bucket. It was an earlier branch and we kind of messed it up by putting in random files that were unrelated. Because everything wasn’t fully done, it never got merged into the master branch or the main trunk. We compared a lot of files and did some salvage work. • I then got a developer going on my favorite buttons and my saved report settings. • Next, I worked with a developer to install and implement a new black box inside of the printable invoice page. These new black boxes are built inside the secured environment. • Brainstorming with another developer on world building concepts and using elements of time as the root or highest level wrapper. Basically, we need everything o be part of the elements of time family. This could be natural and/or adopted into the same family. See other ideas and sketches for ideas. • Met with my brother and watched his presentation on adilas training. He showed all of the guys what he was working on. They all enjoyed seeing his games and other designs as well. We had six guys watching his presentation. • Worked with another developer on domains and sub domains. They want to use that for eCommerce. We (the developer and I) went and looked at some office space that he had found. He knows a guy who has some open office space that we could move into. Lots of fun things happening. 30 miles. • Emails, invoices, and catching up on things. |
|
|
AU 3812 |
|
Daily Ideas | 4/16/2015 |
-I’ve got a number of projects and proposals right in front of me. How can I help those projects go forward and be able to scoop up the low hanging fruit in front of me? I think that I need to slow down and pick things up. Sometimes going slow takes more time but can really help! -Sketches of how elements of time play into all pieces and parts. Concepting with a developer. See sketches on scans in photo gallery: - 12 main player groups like customers, invoices, parts, users, vendors, etc. - Subs or sub functions of time. All main players could use and/or talk to any of the sub functions of time. - 12 main players with their own natural subs or features. - Subs or sub functions of time. - The above model started getting into other natural connections and subs of the main player groups. - I still kind of like the oval and spiral or radial model. Just trying to figure out the best option to help people understand. - 3 main points for joining items to the family of elements of time are: 1. Life span 2. Checkpoints 3. Data assembly line - What if part of the core contained the following elements… 1. Permissions 2. Settings 3. Functions of time & space 4. Media/content & files 5. Relationships 6. Concepts & principles 7. Other key factors & players 8. What is needed to tell, record, & play the story out? - At the core of world building – you have a number of core concepts and principles. They are the core. Without the core concepts and principles, the whole thing fails. Help it grow by supporting the core! - The very heart of the matter deals with a number of interrelated and compound concepts. That is where the model gains strength. - Help other people know about this core concepts, principles, and interrelated pieces. The “why” many take a while to teach, show, and develop. It is worth it! |
|
|
AU 3782 |
|
Brainstorming about the need to mix elements of time, sub functions, and 3D world building concepts | 4/21/2015 |
These are some whiteboard brainstorming pictures of a brainstorming session between Brandon Moore and Calvin Chipman. We were talking about how relationships, inside of adilas, are created and/or manufactured. The subject covered was dealing with how we want to help to virtually adopt different players and player groups inside of adilas to the sub functions of elements of time and space. The subject was somewhat on the topic of data glue. We covered main application types (system player groups), main id numbers (how they connect), and what natural options and relationships already exist. We figured that at the most basic level, we could use the following fields to connect any piece to any other piece.
This brainstorming session also mixed a little bit of 3D world building with sub functions of time, permissions, settings, photos and scans, locations (stacked model), and with media/content (files). By the time we were done, we were talking about a thing called the application flex grid (connecting different worlds or software applications together) and real in-line extensions (possible ways of extending any table or column in the entire database). Good session. |
|
|
AU 3815 |
|
Daily Ideas | 4/21/2015 |
Sketch of a brainstorming session with a developer on relationships and how elements of time play a part of the whole: App Types (List of all 12 app types): - Customers - Invoices - Quotes - Parts/Items - Stock/Units - Elements of Time - Employee/Users - Vendor/Payee - PO’s - Expense/Receipts - Deposits - Balance Sheet Items Main Id’s (list of main id number fields) Elements of Time (main players, sub functions of time, and other options – all of the boxes in the middle were sub functions of time) 3D World Building Concepts (x= time, y = $, z = space) Time (break down time – days, hours, minutes, seconds) Developer’s ideas to help with a base time elements, time glue, or a data glue option: (as a note if we allow for different corps… you could actually even connect worlds) - Corp id 1 - App type id 1 - Main id 1 - Sub id 1 - Table name 1 - (Above – item 1) - Corp id 2 - App type id 2 - Main id 2 - Sub id 2 - Table name 2 - (Above – item 2) - Time type id - Reoccurring type id - Start date - Start time - End date - End time - Use end date - Be able to connect any two object main to main, sub to sub, main to sub, etc. - Things like single, span/range, reoccurring, etc. - Things like name, daily, weekly, monthly, annually, quarterly, hourly, etc. - As a note, we could add items 1, 2, 3, 4, 5, 6 if needed. Each one could be connected to any other player. Or even other players in other worlds. - This could really help with the application flex grid and connecting different systems together. |
|
|
AU 3826 |
|
Daily Tasks | 5/7/2015 |
• Went in to Logan to work at the office. Worked with a developer on adding the Green Bridge as a merchant processing gateway option. • We spent a couple of hours going over flow and direction of how the cart checkout process works. • I worked with a developer on project management stuff and billing. He, Steve, a consultant from Colorado, and myself were on a conference call going over database flow on sub inventory and cost control (packaging) stuff. We spent over an hour and a half working on a spreadsheet to nail down the anticipated flow and relationships. Great session. • We introduced a new self-referencing id number to help show subs of subs. • I then spent about an hour working with some developers on concepts of 3D world building, burning platforms, re-building models, and running things (data & values) through time and space. Kind of out there a bit but a fun conversation. As a side note, sometimes it takes a problem or breaking something in order to stimulate change. It also sometimes takes weeks, months, and years to understand and apply certain concepts. Line upon line, precept upon precept. Slow and steady wins the race. 30 miles. |
|
|
AU 3852 |
|
Daily Ideas | 5/8/2015 |
-For example, say the adilas GPS core model, but use the model for showing data, usage, flow, training, permissions, settings, and even tech or concept stuff. - Add different modes to the GPS core layout model. Be able to switch as needed… Call the different modes “app modes” - Date & work mode - Usage & stats mode - Education & training mode - Permission mode - Settings mode - Relationship & tech mode While we were talking about the core layout, add a 3D cube on the top of the world building pieces. 3D World Building: x=time, y=money, z=space -We need to make things a little bit easier and put things or display things in a visual way. We’ve got tons of great data but it is hard to get it all back out without knowing where it is and how it is stored. Make it simple and obvious. Use grids, graphics, charts, direct changes, simple layouts, etc. |
|
|
AU 3829 |
|
Daily Tasks | 5/11/2015 |
• Working on the app modes and adding 3D World Building concepts to the adilas GPS core graphic. Trying to get things ready for the new interface. • Went in to Logan to work with the interns. I helped migrate some files and cleaned up an older branch from bit bucket dealing with icon menus. 30 miles. • Working with a developer on an API socket connection to help handle event driven email communications. We spent the afternoon building the socket connecting and testing along the way. • I also had a talk and discussion with a developer about transitioning all of the interns off of internal projects into client funded projects. • Today stress levels were higher and you could feel it. All in all a god day today. • Recording bills and expenses. |
|
|
AU 3841 |
|
Daily Tasks | 5/26/2015 |
• Checking the data 1 server. Upgraded from ColdFusion 10 to ColdFusion 11. Small tweaks and checks to make sure all was well. • Working on payroll options to show sales commissions based off of gross sales vs. commissions based off of profits. • Working with sub reports, totals, and output displays. • On the phone with Steve talking about internal projects like splitting up database tables for invoice and invoice line items. • Other projects are packaging and full database split or world building concepts. We talked about funding options and how to work and play the game. • Went into Logan to work at the office. • A developer called in from New York via video chat. • Another developer called and let us know that his Reno, NV, thing was going to be more intense than originally planned. • We had a full house and staff there today. We had 10 of us guys here today. • All of these guys know generally where they are headed and it is exciting to watch them. I bounced between people and helped where possible. • I also did some email stuff and did a number of tech support related things. • We got a developer some new data and got him lined out to work with stock/units and making sure that we could refine searches, save report settings, and exports to Microsoft Excel. • Some developers were doing sign-offs on icon menus. • My brother and the project manager were working on sales ideas and such. • I worked with a developer a bit on the eCommerce API socket connections. That section is somewhat of a mess right now. It is going to take some time. I also met with the owner of the building and talked about rent, needs, options, and ideas. Busy day! 30 miles. |
|
|
AU 3868 |
|
Daily Tasks | 6/10/2015 |
• Emails and viewing a Ted talk by Simon Sinek. See notes above and on other page. • Updating the main login page. Took off a couple of ads. • Fixed an invoice bug and prepped some developer update files for helping developers migrate and update their local systems. • Went into the Logan office. I spent the first couple of hours working with a developer on sales, goals, and vision of how the adilas model works. We spent quite a bit of time drawing things out and going over numbers. • We also had a discussion about a hybrid independent model vs. a full traditional employee model. Good stuff. • I helped to rough out a project for an intern. We even got to start working on it. It deals with grabbing the last known RFID tag numbers for shopping carts that are restored to a cart. • I got another intern helping me do some prep work on the data 3 custom files. He was prepping them for the invoices and invoice payments switch and migration project for data 3. • A developer and I had a great meeting with a client. My dad brought them over to our office and we chatted for a bit. We spent quite a bit of time talking about concepts of the data assembly line and how that works. We also talked about concepts of systems and how to interconnect things together. They want a product demo tomorrow. 30 miles. • Went over to Bridgerland to meet with my dad and the Ham radio guys for the Bear 100 race. My dad and I pitched the adilas concept and tying in everything for GPS, automated data entry and retrieval, and custom searches and special interfaces. Good stuff, great meeting. • Recording notes, paying bills, and emails. • Working on custom files for the data 3 server. • Migrating and splitting all invoices and invoice payments on the data 3 server. Testing new code. This marks the completion of the project to split up invoices and invoice payments on all 4 data servers. Yea! |
|
|
AU 3888 |
|
Daily Ideas | 6/10/2015 |
Ted talk by Simon Sinek about inspiring leadership: -I got a fun email from my brother. It had a video link in it to a Ted talk given by Simon Sinek about how great leaders inspire action and vision. The talk was from back in September 2009. http://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action. Anyway, a great talk. I took a whole post-it note full of ideas. The nuts and bolts… teach the why! -Golden Circle – why is the core – what is your purpose – reverse the order and teach the why – Driven by a cause – (Target sketch – from the center and working outward – why, how, what) -People don’t buy what you do they buy why you do it. -Innovation and adoption cycle: inventors and early adapters (Teach people the why!) Why, how, what. -Tell people what you believe. Random sketches of board – meeting with a developer on flow and options….: - Clients, direct pay, adilas. Rep, own relationships, commission for development or sales. - Hub model – this could be duplicated over and over again. Adilas – world building & a hub that provides other features such as: o 3rd party products o Developers o Customer service o Project management o Sales o Training o Consulting o Other services |
|
|
AU 3871 |
|
Daily Tasks | 6/13/2015 |
• Recording notes, emails, and research. Watched a couple of videos on Arduino microprocessors and how to set them up. Just trying to get familiar with what is out there as options. • Updating and signing off on code for icon menus. Reposted a number of files online. • Prepping files for a developer/client. He wants to work on the internal cost corrections and update cost PO process. This is also tied into a possible project dealing with a setting for using average costing models. Some of the pieces of the project I believe in and want, and some of the pieces I really don’t want – like average costing. • More prep work for getting files and database pieces ready for this developer/client. • Trying to prep world building code to migrate corp specific records for a client. Ended up reviewing a developer’s code from back in March of this year. Crazy how time flies. |
|
|
AU 3872 |
|
Daily Tasks | 6/15/2015 |
• Working on code prep for a client. More work on code that a developer did for the full database split and migration back in March of this year (helping people get off the bus). Full world building pieces. • Went in to Logan to work with my guys. I got a room setup to help do some training on the sub inventory and cost controls (packaging). • We did a multi hour session on the project and recorded the session. We used a couple of laptops, a digital microphone, a projector, and lots of talking and interactions. Good stuff! • A contact came by and chatted with a developer and I about setting up radio packet data and working with CSV (comma separated values) files. He was giving us ideas on how to get and chew up text and packet data. This project deals with runners and even tracking of data for the Bear 100 mile race event. • I spent some time with an intern signing off on code to be able to email invoices to clients from inside of adilas. This is a new general tool for all users. 30 miles. • On the phone with a developer doing a salvage job on a data upload that went weird. We used GoToMeeting and were able to retrieve almost 100 lost customers and customer records based off of invoices and dates. Good stuff. |
|
|
AU 3874 |
|
Daily Tasks | 6/17/2015 |
• Emails and recording notes. • Going through files and methods to split up database tables for world building pieces. • Went in to Logan to work with the guys. • Worked with an intern to give him some admin permissions on all servers for uploading and helping with client look and feel and client logs. • A developer grabbed me and we had a good meeting about moving forward with the hub or adilas shop model. We talked about getting things back to an organic growth model. Things have been kind of crazy lately. We talked about adilas feeding the shop between $1,500 to $2,000 worth of internal work a week. This is $6,000 to $8,000 a month (roughly). We talked about a feeder period of 6 months and how much we could gain by an arrangement of that kind. We talked all kinds of numbers, break even projections, direction, vision, etc. This was probably a two hour meeting with whiteboard drawings with lots of talking and discussing options. • After that, some interns and I did another session on the sub inventory and cost controls (packaging) project. We scripted the database creation process and then got into a small business lesson. We ended up talking for about an hour on where adilas is at as a company. • Sadly, only the lead up portion got recorded using GoToMeeting. Someone else had a demo and needed the GoToMeeting account. Fun conversation. • I think that interns got into it very well. That was fun. • Another fun part of the conversation was the why we do what we do. I really enjoyed that. • After that session, I talked with a developer about options for GPS and internal 3rd party solutions. He would possibly like to get into providing the GPS units, setups, installations, etc. I told him that the market was open and we didn’t have a problem with that. • I also spent an hour or so with the project manager roughing out projects at the wall (whiteboard wall). We did about 6 projects with different options and costs. It really helps to bat the projects around with someone else to talk out details, flow, complexity, options, and costs. Busy but great day! 30 miles. |
|
|
AU 3875 |
|
Daily Tasks | 6/18/2015 |
• Recording notes from yesterday. Lots of numbers and business talks yesterday. • Reviewing video footage from yesterday. I watched the last 20 minutes of the packaging GoToMeeting section (start at 1:38-1:58). It has a great dialog on how our model has changed, grown, and how we are positioned to really move into the different markets. Kind of fun. The last five minutes talked about some pieces that make adilas unique (1:54-1:58). • Tech support calls and fixing a small bug with the teacher/student interface. • On the phone with a developer going over business plans and decisions. He wants to get things under control very soon and quickly. I hope that everything goes well with some of the transitions that are needed. • Went in to Logan to work with my guys. • A developer and I went on a walk around the block. We chatted about sales, numbers, and shop dynamics. There are some concerns with decisions and management stuff. Normal HR (human resources) stuff between people and personalities. • Met with a guy today who is a technology consultant that works with another friend who I’ve been chatting with. We met and talked about options and what adilas could bring the table. I used the interactive map flyer and the GPS core layout flyer to explain what we can do. Those graphics really help to explain the concepts of 3D world building and the data assembly line concepts. Those pieces are part of the story or why we do what we do. • After he left, we had our normal morning stand-up meeting. As part of the meeting a developer presented some of his plan. It was received with mixed reviews. We all talked about some options and what we want to do. Lots of emotions and different people somewhat jockeying for positions. Basically, debts are high, funds are low, and spirits are somewhere in between. Things aren’t super bad but finances and money are definitely tight. I’m hoping and praying for a miracle. • There is a lot of potential but it is hard to convert raw potential into raw money, capital, and cash flow. If we got paid for all of our outstanding invoices we would be okay. However, our receivables are kind of slow and our payables are mounting daily. Anyway, I didn’t see how the meeting ended. I had to leave and go get a Boy Scout physical for Scout camp next week. When I came back to work, everybody was busy working. • Around 1:30pm a client came by to our shop for an appointment. We met and talked for a good 45 minutes to an hour before his partner came to participate in a group brainstorming session. We all had fun and used up the whole whiteboard (wall) going over a two-deep affiliate program. We talked needs, listed out ideas, options, goals, rules, and various dreams. • There was good dialogue between the group of us there. Lots of drawing, sketching, and consulting going on. My sister took some notes of the session. There was also lots of good learning going on. Both of the partners have been involved with numerous businesses over the years. They are both quite seasoned and are a wealth of knowledge. • See entries back from 12/4/10 for some notes that I took while watching one of the partners do a foam clothing class (cold weather survival stuff). Some of the concepts and principles that I learned from him have played a huge part of what adilas has become. Concepts such as systems, acquisition of knowledge, function over fashion, they why and how that is developed over time, etc. Great stuff and very pivotal both now and especially back then. • Just for fun, I looked up my notes that I did back in December of 2010 and showed them to him from inside the adilas developer’s notebook application (elements of time). That was kind of fun. • After those guys left, I worked with numerous different developers on their different projects. Crazy day! Fun, long, emotionally charged, and a lot of learning and applying concepts. Good stuff! 30 miles. • Spent the evening defining multiple different developer pay models. I created an hourly system, titles, qualifications, add-ons, prices and costs, and other options. There are developer models for training, interns, developers, trainers, leads, independents, 3rd part solutions, and custom or open models. Lots of options • Anyway, I created a spreadsheet for the different models and what each one gets, requires, and may or may not need/use. Lots of different options. Trying to create a hybrid solution of sorts. I sent out an email to Steve, the project manager, and developers and asked for their feedback. |
|
|
|
Shop 3814 |
|
Virtual Post-It Note | 6/24/2015 |
|
|
|
AU 3899 |
|
Daily Tasks | 7/2/2015 |
• Went in to Logan to work with my guys. I had a 2.5 hour meeting with a developer going over ideas on models and how we could stack and grow this thing. See other page for some model ideas. • I worked with some other developers on mapping out a project to automate expense/receipts and balance sheet items. Lots of training and showing them they why behind the need. • I got on a conference call a developer, a client, and my dad. We went over the progress that we are making in the GPS world and land. Good meeting and the developer was able to get some new information. The GPS landscape is kind of random with hidden little pieces scattered all over. People are holding pieces and not sharing information very easily. Interesting! • The owner of the building where our office is, called me in to chat with me. He wanted to know what we do and what we offer. We had a great discussion and ended up filling up an entire whiteboard with drawings and sketches. We covered: dynamics, systems, player groups, functions, settings & permissions, rep models, server structures, 3D world building concepts, data assembly line concepts, stats, and even possible 3rd party predictive models for stats and other analytics. Great little meeting. • As a fun side note, Dave helped me out twice today by pulling me out of very long meetings. He pulled me out of the meeting with a developer this morning and with the building owner this afternoon. I kind of needed that extra help to pull out of those meetings that just keep going and going. Good meetings, just long… : ) 30 miles. |
|
|
AU 3902 |
|
Daily Tasks | 7/6/2015 |
• Working on graphics for the adilas.biz community funded projects. I redid a couple of other graphics. Trying to create a new look to expose the adilas world building concepts and more. I really think that some new graphics will help our users know more about what we are doing and where we are headed. Communications are somewhat tough to keep on top of. • Added some new ads and layout for the main login page. • On the phone with a developer going over pay rates, hours, and how to transition over to custom work. Great phone call and GoToMeeting session. We were talking and running numbers and scenarios in Microsoft Excel the entire time. We came up with a good plan to help with the transition. The plan dealt with our top four players at the Shop right now. • Went in to Logan to work with my guys. I worked with a developer to get some generic PDF labels created. This is for a bulk print labels project. • I then met with another developer and looked over his plans to further define the adilas shop and key roles within that environment. He had a nice Excel spreadsheet with graphs and such all laid out and displayed. • Later on, he & I got on a GoToMeeting session with another developer and went over his ideas and new documents. We further defined roles and responsibilities and even put names with the different roles. Lots of work with spreadsheets and such. • At the end of the day I got to play with some new Flash interfaces that my brother is working on. Super cool stuff. I want to get them wired up – so that I could use them. Awesome! 30 miles. |
|
|
AU 3927 |
|
Daily Ideas | 7/7/2015 |
-Put up a new PDF flyer and new help file dealing with the concepts of the data assembly line. See entries in September and October 2014 for more details. See sketches on scans in photo gallery 7/7/2015 of: - Static - Dynamic - Dynamic with time, checkpoints, & permissions - X = Time, Y = $, Z = Space - 3D Assembly Line for data – include objects & data over time, resource tracking, & spatial elements (space) -Put up a new PDF flyer and new help file talking about expanding the concepts of world building, systems, and different levels and how they interact and play… Universe, galaxies, clusters, solar systems, worlds, locations, groups, individuals, data level, and run all levels over time and through space. -“We teach people how to treat us.” – My sister. This could be good and bad, abusive and helpful, pushy and firm, etc. Very interesting concept. She and I were talking on the way down to Salt Lake City about clients, relationships, and expectations. -I hate to say it, but we have trained a number of our clients to push and demand the moon for pennies or almost nothing. We have jumped almost every time. It turns into an abusive type relationship. Nobody likes that. This is just me confessing about adilas and some of our clients. Adilas has just taken it on the chops, time and time again. We’ve got to put our foot down. This is for me personally as well. I barely make it from check to check with no wiggle room. -My sister and the Project Manager are going to help make some safety nets (processes & procedures) for our development team. Virtual safety nets for our development team. -See notes on 7/29/15 for an expanded view of this graphic. |
|
|
AU 3933 |
|
Daily Ideas | 7/22/2015 |
Notes from a meeting with a developer and his friend/associate: - Analogy of a railroad (or pre-built platform). So, the story goes that this gentleman wanted to ship a load of used cars from back East to the Mountains (Rockies). Anyway, he called up the train company and tried to get them to ship his vehicles. The company actually said no, they only shipped new cars (insurance stuff). So, he asked about other options – here is where the analogy comes in – the person said back to him…. You can do it, but you need to: o Buy the land o Put down the tracks o But the train or buy a rail car - Basically, the guy was saying – you can do that but you need to build your own railroad system to do that. - This answer shocked him and at first he was kind of taken back… then after he thought about it, the answer made more sense and he learned some lessons from it. This little analogy ended up being an underlying topic on platforms that we used over and over again in our discussion. Basic railroad tracks: - Buy the land - Put down the tracks - Buy the train Basic railroad tracks: - Think of different industries and/or niche products or pieces - Railroad tracks with different spurs or branches - Once the main track system is built, you can create offshoots or spurs Going along with the railroad analogy (continued): - What about spurs of spurs, niche products, custom lines, etc. - Once the main system is laid down, all kind of options could be added on, bolted on, offered by 3rd parties, etc. - Sketches of basic tracks & tracks with spurs & branches -What about the virtual real estate around the tracks? That is an open market and available to outside parties. -If a railroad is too old fashion – maybe call it part of the data highway or virtual data assembly line – whatever. -Anyway, if 75% of the system is fully in place, the other 20-25% is basically custom stuff. -As the main priorities get taken care of, the customers will want the next and next priorities taken care of. This process virtually creates a reoccurring customer because they keep rolling from priority to priority. That is awesome! -In the railroad analogy, if you buy a box car and put a sticker on it (the other 20-25%) that becomes your part of the system. The tracks are still owned by the railroad company but you, as a customer, are allowed to use the system as your own (in a certain way). Basic Rep Model: - Client --- two-way relationship (key) --- Rep/Consultant - Clients – Adilas – Direct pay for service - Rep/Consultant – Adilas – sales commission 20-40% - The key piece is the two-way relationship between the clients and the rep/consultant Basic Shop or Hub Model: - Clients --- two-way relationship (key) --- Shop or Hub - Clients – Adilas – Direct pay for service - Rep/Consultant – Adilas – sales commission 20-40% - See entry from back on 7/20/15 to get more info on the shop model - The Shop or Hub model offers a number of different services but could be the same as a Rep/Consultant only bigger. Basic 3rd Party Solution Model: - Clients --- Normal two-way relationship --- 3rd Party (product solution) --- secondary two-way relationship – commissions --- Adilas - Clients – Adilas – Direct pay for service plus possible payment for 3rd party solutions - A 3rd party has an additional relationship with Adilas More notes from the meeting with a developer and his friend/associate: - 3rd Party Solutions could be spread around the platform or railroad model. Think of different products, solutions, niches, add-on’s, etc. - Main track system: spurs or branches off of the main tracks - These could be other 3rd part options and solutions - Each one could be industry specific - They could be products, services, solutions, etc. Think Historically… - Imaging how town across the west were setup to support and use the railroad - Once the train came to town, that allowed for people to come, products to come and go, businesses to support the new needs, etc. People ended up building whole towns just because the trains would stop there. - The train company didn’t own the other businesses and the other businesses didn’t own the train company. They worked together in some kind of relationship – both parties needing the other. This creates a dependent relationship. - Adilas is starting to see a number of new dependent relationships starting to show themselves. Our clients need a rep and/or consultant. The reps and consultants need a developer to help them build custom pieces. Developers need project managers and designers to help them produce the new code and features. All of these people need a way to track things and help with billing. The process keeps going and provides numerous new jobs, careers, businesses, services, etc. - Because one thing feeds and grows another… The growth of adilas will be somewhat like the spread of the railroad to the Western United States. Our product, the adilas system, brings with it tons of jobs and opportunities. That is fun! - So, if our product and system creates jobs and opportunities, how can we help that part of the system grow? - We could start recruiting people who want to help and service those positions. Maybe colleges, tech schools, business schools, consulting services, insurance people, sales, accountants, data entry people, designers, developers, trainers, etc. Basically start building small communities. - Most of the growth comes back to training and education. - Training and education cost money. As a side note… The cost could be flipped depending on where the need is. If a business pays for a person to be trained they gain an employee. If a person pays to be trained you gain a student who can then do something. Interesting twist. - How do you keep your guys and gals (sheep) in the fold? Often it is through training, education, set standards, and then some form of return and report type system. - Sometimes growth and pain are parallels. - Part of the model may be pushed towards marketing and training as well as recruiting and retention. You’ve got to keep things somewhat together. - Don’t promote them out of their abilities. As a fun story, this guy was saying that they had two guys on the night crew that were doing awesome. They promoted them to a different position and things fell apart. The company was about to fire them it got so bad. Right before they fired the guys, they decided to switch them back to the night crew. Both guys flourished. Basically the point was… don’t promote them out of their abilities. - The adilas model may end up looking like this… with independents, shops, hubs, 3rd parties, etc. o 3rd party with added features & products o Sketch of how things connect – model (Adilas, 3rd party, clients, independents, & the shop). |
|
|
AU 3917 |
|
Daily Tasks | 7/25/2015 |
• Working with my brother to wire up two different sites. They are a basic sales page for vehicles, trailers, RV’s, and motorsports. Awesome graphics and very loose flow. The other site was the one my brother did for his practicum and internship back in February and March of this year. It is a training website for adilas university. I got really excited about the graphics and options that it has. We spent quite a bit of time going over the photo gallery which has graphics of 3D world building, the adilas interactive map, core business functions, main system players, etc. Lots of fun. Here is the current URL or link to photo gallery page: http://www.adilasuniversity.biz/training/photo_gallery.html • Recording notes about my session with my brother and other light brainstorming on how to get the word out. • Signing off on GPS and RFID tag tracking code done by an intern. • Working on the advanced sub time search and search results page. |
|
|
|
Shop 4375 |
|
Virtual Post-It Note | 11/12/2015 |
-( Planning for code projects) -What server? -what corp id? -other special id numbers? -need to keep track of what files are being altered, added, or deleted? -what are the differences between test and live. -whats your to do list. (END planning for code projects) -with Bryan what branch are you? -How can you renew this? -what's your plan? -technical aspects? -what would make it move dynamic? -what is your budget and how will you spemd that? -What goals? -possible problems/ -expand options? -wish list? (TIME) -(9:45 - 11:15)Logan - worked with Daniel on some project planning. See Element of time number 194 in the adilas shop. Good notes. 30 miles -(11:15 - 12-:00_ working with Bryan on some project planning. More good notes. See element of time number 195 in the adilas shop. -on the adilas GPS core...add some basic stats on the graphical home pages and sub home pages. -(12:00 - 6:15)phone calls, tech support, and helping guys with their projects. worked with Dave, Russell, Bryan,Daniel and Alan. Dave and Russell were talking about elements of time and I got to chime in and share some vision about watchers, feeders, automated financials, and history of elements of time. I had fun rolling things back and talking about the why behind the interactive map, 3D financials, world building, and how elements of time is somewhat of a precursor for other sections. -(9:15 - 10:00 PM) paying bills and recording expenses. |
|
|
|
Shop 262 |
|
working on sales page | 12/3/2015 |
working on sales page Notes: Meeting with Russell to talk about sales, commissions, and marketing ideas. We spent the whole time going over numbers, ideas, concepts, and options. We both were drawing on the whiteboard & covered tons of topics. We talked about packages, presets, costs, models, on boarding new clients, transitions, and how to ease into the different phases. super fun meeting talking about cause and effects, relationships, world building, the railroad model, & branching out to other verticals or industries. Good session. Lots of fun ideas. 30 miles. |
|
|
|
Shop 278 |
|
working with sales page | 12/7/2015 | We talked about graphics and ended up brainstorming on how to teach and show world building concepts using the GPS core layout graphic. We did a number of pages & went through diagrams for the universe level, the galaxy level, the cluster level, and the world level. Logs of drawings, sketching, and talking about flow and options. I find this kind of stuff exciting. | |
|
|
Shop 2814 |
|
General | 12/7/2015 |
12/7/15 8:30-9:00 On the phone with Steve going over plans and what is happening. Crazy times. 10:45-6:15 Went into Logan to work. Help Bryan out with his projects. Had a meeting with both Calvin and Bryan to talk about permissions and who used what features. Basically, how do we advertise features and still control who gets them based on admin (universal level) permission and corporation and user (world level) permissions. Calvin is working on an export for Quick Books and Bryan is finishing up a consolidated report for receivables and payables. Next I worked with Daniel and went over plans for Beaver Mountain Ski School. We wrote an email and updated a quote from them. We are still trying to negotiate prices, features, and such. After that, I worked with Bryan and we added some new permissions to his consolidated receivables and consolidated payable reports. We made changes and pushed files live. Garrett came by and we chatted about some features for sub inventory and getting up some new servers and possibly doing some bidding on servers and setup services for servers. I gave Garrett a check and got him all paid up on his current projects. Next, I worked with Russell on a sales page. We talked about graphics and ended up brainstorming on how to teach and show world building concepts using the GPS core layout graphic. We did a number of pages and went through diagrams for the universe level, the galaxy level, the cluster level, and the world level. Lots of drawing and sketching, and talking about flow and options. I find this stuff exciting. The last part of the day was helping Bryan sign off on code for his custom invoice (Excel format). Lots of code clean-up and testing. Good, but busy day. 30 miles. |
|
|
|
Shop 290 |
|
Working with my Dad | 12/11/2015 |
Meeting with a new developer. Notes: Met with a guy by the name of Matt. He is going to be working with my dad on his industrial recycling. We met and talked and then I showed Matt some of the vision and where we are going. We had a good conversation about the data assembly line concepts and how to systemize things. He seemed to be pretty sharp and caught on really good. |
|
|
|
Shop 506 |
|
Getting data for Calvin | 1/16/2016 |
Did some data exports and prep work for Calvin. He needed a number of fields and tables from the data 2 server. I spent a good hour or so just getting tables exported. I then FTPed the files and tables down to my computer. While they were downloading, Calvin and I talked about some world building options and how we could potentially use a Windows based tool to get the database splitting and database cloning done much quicker. Lots of fun options. We talked about servers, tools, needs, and lots of other topics. There may be tons of potential to use Calvin's knowledge of Windows tools to help automate the processes for servers and database stuff. Once the data got all pulled down and transferred over to Calvin's box, we got the new tables imported and updated on his local testing machine. Good session. |
|
|
|
Shop 403 |
|
Calvin Chipman | 1/18/2016 | On a phone call with Calvin. We worked on settings and values for my cart favorites and smart group buttons. Calvin is working on a project that is using smart group logic out in the ecommerce and/or shop folder pages. We also talked about the world building and database tools. I proposed a 50/50 split on the tools and what they could do for duplicating worlds, creating new worlds, and migrating worlds out of the shared environment (the bus) and into their own worlds (cars or motorcycles). Good session. | |
|
|
Shop 414 |
|
Calvin Chipman | 2/2/2016 | Calvin called and we got on a GoToMeeting session. I got to see some of his new code for the SQL editor. It can now import, export, and run other queries. Good stuff. I was tagged with getting Calvin a list of what is planned for the World Building pieces. | |
|
|
Shop 581 |
|
Sub Inventory | 2/11/2016 |
On a GoToMeeting session with Steve. Our main topic was finishing up the sub inventory brainstorming page. We ended up on a number of different topics. Fun session. We also had Russell, Dave Forbis, and Bryan chime in here and there as they found the topics interesting. Kinda fun. We did a small quote for Kelly Whyman. She wants a few things. We decided to see if we could roll together adding datepickers to all dates, implementing the ice-down date for financials, and cascading database field settings (starting with the customers table) all around the entire site. We decided that would be touching almost 1,000 pages. We also decided that we would have a good 15-20 hours of code writing and logic and then pushing that code to all 1,000 pages. We came up with a number between $30,000 and $50,000. We are going to try to use community funded projects to get some of that stuff done. We can get started as soon as we get the first $5,000. A huge piece of what we did today was talk about some concepts of the adilas community and how to tap into that as a resource. See the attached notes: - Next logical step - This is what our goal is... What is the next logical step? - We are selling a partially done product That has been a huge pain but super worth it... We have a producing idea farm - right now! Our clients are helping us drive the ship! – If we have a producing idea farm - we need to harvest some of these things. - We try to listen to what our customers are really asking - within limits of budgets and time - what can we do to help the ones who love what we do? - we may need to pick and choose what clients we service. - what will benefit everybody the most? - In the railroad analogy, we are the train tracks - we'll let others build out the other pieces as they see fit and needs. - Quote from Danny Shuford - Adilas is a business solution for solution minded people. - Ideas from Ryan Fox (adilas client) - Adilas Community - Post things - Training - Teach from the inside out - This is a huge resource that we could tap into - Tap into the power users - Help them setup their own companies - We are sitting on the answer to tech support and customer service - basically make a call to the power users and see if they want to help make some side money - allow our people to make some extra money by helping to fill needs - allow them to set their own schedules or times when they are not working for someone else - What if we had a merchant account that could be used for the adilas community. Help push things around. This could be for selling both products and services - Be able to send requests to users for help and tech support - training - setup - audience that is watching what is going on (potential for advertising and marketing) - maybe use Calvin's gmext (group mass texting) texting to the power users. Then let them respond to service the needs. - See elements of time - in the adilas shop - # 667 - concepts of sharing resources and tapping into a community type platform. - Referrals and testimonials - who knows it, who loves it, who can help us spread it around and about. - Idea on a flat tech support/training fee - thinking $20/hour for our community to help with training, setup, and such. We (adilas) then would pass the monies around. We would eat the credit card fees as our part of the process. We could spread the monies around and help track things. - The way we make our money is by more and more clients using our system. There will be tons of ways to make other monies once things get pushed and get going. - We really need to get the job costing and finish up the elements of time thing done to get to a higher level... That would be awesome. - What if we change from "as is" to "community driven" - What do you want? And what tools do you need? Here is what we have, if you like it great. If you want something else, let us know. Let's drive this thing together. Help us know where we are headed. - Another internal asset that we have is the data that we are storing and connecting together. That is huge! - Whoever wants to play... then let's play! That is who we want. - Get the system to help the people know what to do next and how to fix potential problems that come up. Easy wizard steps, new interfaces, training (inside out), new setting and features. - Corp setting, page settings, location settings, user settings, manager settings, etc. To what level? Business world building! - Business to Business (B2B) transactions. Application flex grid options. EDI electronic data interchanges. - Keep plugging, keep plugging! We are going in the right direction! The windows keep opening. This project is way bigger than we are... - Our business model is: small to medium sized business, self-server, software as a service, open API model, etc. |
|
|
|
Shop 4955 |
|
Virtual Post-It Note | 2/15/2016 |
-Labels -Sub inventory -Sub categories -Bar codes -World building |
|
|
|
Shop 644 |
|
Adilas World | 3/8/2016 | Alan and I worked on the "any" scheduler app and sub functions of time. We ended up going into the adilas university site and looking up some of the early brainstorming pieces for elements of time. We talked types of time, functions of time, 3D world building, data assembly line stuff, and much more. I was really enjoying the dialog and conversation. I hope that Alan was enjoying it as much. This has been part of the dream all along. Fun session. | |
|
|
Shop 532 |
|
Brandon Coding Time | 3/9/2016 |
Working on a new page to help show what database tables and record counts exist for each corporation. This report will be used to help with the data migration process. This is a prep step for the upcoming world building project. The goal is to get everybody off the buss (shared database environment) and get each company or group of companies using their own database. I also helped out Shawn and Bryan with different little questions on their projects. Shawn is doing payroll functions and Bryan was working on servers and doing a custom data import project for a client. |
|
|
|
Shop 757 |
|
World Building | 3/9/2016 | On a GoToMeeting session with Steve and Will trying to debug a couple of errors on pages. One of them was really fast. The other one got deep and we couldn't really tell where the problem was located. We flipped back and forth between the presenters and shared our screens. The problem was dealing with sub inventory and the new bulk edit PO page and logic. We can't tell if that page is wrong or the add/edit sub inventory logic is wrong. It only happens at certain times, but there seems to be a small disconnect between the normal logic and sub inventory logic. That project is super deep and hasn't really been all the way looked over and/or verified (code sign-off). | |
|
|
Shop 758 |
|
World Building | 3/10/2016 | On the phone with Steve. We talked about a couple of projects and some light funding stuff. We then went in and blocked the new edit PO lines items page due to a small bug with sub inventory. | |
|
|
Shop 759 |
|
World Building | 3/14/2016 | On a GoToMeeting session with Steve working on the bulk edit PO line items. We were debugging the sub inventory edits and how to track things through. Will Hudson came over and watched and we got everything figured out. We made the fixes and then repushed the files up to all live servers. | |
|
|
Shop 840 |
|
Bryan Dayton | 3/24/2016 |
Met and talked with Bryan about financing and options going forward. We did a small whiteboard session and discussed progress, progression of team building, and options going forward. I offered Bryan options on servers, world building stuff, and customer gift card programs. Good Meeting. Got a call from my wife and her water had broken earlier in the morning (I already knew that). She had called the doctor and he wanted her to come in. I had to cut my meeting with Bryan short to get home and help get her to the hospital. We ended up having our little girl "Brooklynn" at 7:37 pm on 3/24/16. Busy day. |
|
|
|
Shop 1094 |
|
Brainstorming Meeting with Steve | 3/26/2016 |
On a GoToMeeting session with Steve to go over a proposed budget and a plan for the upcoming couple of months. We spent a lot of time talking about individuals and how best to get them going and connected with the rest of the team. See time id # 1274 in the main adilas site for more info. Both the budget and the brainstorming doc were uploaded to that element of time. We covered: - Team building - forming, storming, norming, and performing - adilas university - adilas world, adilas market, adilas community - developer's notebook - world building - own skill levels & abilities - persons and their skill levels - work ethic, commitment level, investment level, time, availability, communication skills, coding and general skill levels, social, special attributes, and timelines. - Maintenance - Pace - Code clean-up, sign-off - Elements of time - Servers, roll-overs, and availability - World building - splitting up databases - Training and support team |
|
|
|
Shop 654 |
|
World Building | 3/29/2016 |
Working with Bryan up at the board. We did two full whiteboards (walls) full of graphics and illustrations. We talked about a ton of flow, concepts, and directions. We covered our current models, where we are headed, and what to possibly look out for. Good session. See time id # 1101 for photos of the brainstorming session. Some of the database splitting stuff is clear back to 2013 and 2014. This project has been a long time coming. |
|
|
|
Shop 703 |
|
Bryan Dayton | 3/29/2016 | Working with Bryan to find old pieces of the world building project. This one has some roots and branches. We started going over some database stuff and spent some time looking for older files that deal with defining the adilas database and what database tables are on the cluster level (level 3) or on the solar system level (level 4) tables. Trying to get back on track on this project. | |
|
|
Shop 847 |
|
Bryan Dayton | 4/4/2016 |
Working on a flex grid wire job. We opened up a number of sample pages to get code and see how other project had been run. Trying to get him the code he needs for his project. The last half of the session was spent brainstorming on the world building project (splitting up the databases) up at the board. We ended up going until 2 pm with small phone calls and such in between. On the phone with Calvin for 15 minutes and then on the phone with Steve for an hour going over the state of the project and what is required. We decided to stick with the older model for now until we can get some funding to advanced to the newer level. |
|
|
|
Shop 706 |
|
Calvin Chipman | 4/4/2016 | Small phone call for about 15 minutes. Just touched base and talked about API stuff and the future of the world building database tools. | |
|
|
||||||