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

(use a plus "+" sign to separate search terms. ex: jack+jill+hill)
Sort Value:
 
Adilas.biz Developer's Notebook Report - 4/1/2013 to 4/30/2013 - (54)
Photos
Time Id Color Title/Caption Start Date   Notes
Click to view time photos.
AU 1152 Daily Tasks 4/1/2013   • On the phone with Steve talking about getting tapes back (first training session from February). We also talked about non-profits and getting adilas into the college curriculum level. This would help train the upcoming generations. We also talked about Interns and the Adobe Creative Cloud.
• Research on the Adobe Creative Cloud.
• Bank stuff.
• Paying bills and general catch-up stuff.
• Working on changing vendors and customers using pass through links.
• Finished up the PO vendor change and started to work on the expense/receipt change.
• Working on changing expense/receipt vendors.
• Finished up and launched the change vendor pages.
• Light testing.
 
Click to view time photos.
AU 1153 Daily Tasks 4/2/2013   • Reviewing old Flash projects. The good, the bad and the ugly! I came up with 2 ½ pages of old Flash files that I did for commercial use. I’m excited to get back into it – meaning Flash.
• Phone calls and emails.
• On the phone with Steve. We talked about venues for training. We talked about API’s, custom code, custom interfaces, css (cascading style sheets), and even mixing with different vendors for text messaging and email blasts. We talked about open source and sharing.
• Setting up a visit with my cousin to get his ideas and have him help me do some selling of adilas.
• Working on help files.
• Updating help files and research on podcasting and RSS feeds.
• On the phone with my sister going over ideas for the developer’s notebook. We also talked about turning the help files into audio or podcast files.
• Adding a “change” link for changing a customer invoice from one customer to another. Adding system-maintained history notes about customer changes.
 
Click to view time photos.
AU 1179 Daily Ideas 4/2/2013   -Trying to remember old Flash projects that I did. I’m trying to get back into Flash to do the adilas.biz interactive map and the adilas university.biz training area. I’ve done tons of Flash projects over the years. These are just a few.
Morning Star:
- Navigation banner with roll over graphics
- Location map
- MSAI logo zoom
- Old stock/unit photo galleries
- Deal calc with dynamic data
- Parts application with Flash Remoting
- Parts admin with Flash Remoting
- Floorplan application with Flash Remoting
Fibark
- Fun kayaking animation
Radon Ranger
- Sliding menu
- Comic book with page navigation
- Product display
SOSS
- Flash menu using pencils
Salida.com
- Mountain site navigation
- Tons of sub menus
- Tons of mini ads and animations
- History animation with miner and rafters
Moore Digital Ideas
- Main website with menu, animations, and status bar interactions
- Navigation options
- Photo galleries
- Games – hangmen, catch the apples, etc.
- Lots of pre-loaders
Custom Fit
- Class content using Flash Remoting
Bridgerland Applied Technology College
- Interactive CD-ROM with photo galleries, video, and other dynamic menus and pieces
- Flash cards for Medical terms
Learn To Freeride
- Video teaser and custom player
- Interactive CD-ROM with multiple skins, tons of video, and linked to web content. Music controls and custom video playback options.
- LTF skateboard demo mini app
New Mexico Wild
- Fun animated Flash banner
Vector Trap
- Interactive game board
adilas.biz
- Barcode generator
- My cart favorites – custom mini buttons
- Check write application with moveable fields
- Scrolling list of features
Art of the Rockies
- Animated banner
- Full backend content management system using Flash Remoting and database content
___________________
-At some point it may be fun to go back and look at some of the different Flash files and play around with them.
___________________
(More Flash Projects continued)
Geo Tourism
- Dynamic photo galleries with fade in/outs
- Planet zipline – fun animation
- Other random demos and play files
____________________
-Plan out the maintenance and have a plan in place.
 
Click to view time photos.
AU 1180 Daily Ideas 4/3/2013   -Make a business plan. Include different rounds and steps. Budgets, pro-form, interns and required steps. Also include what we’ve already done. Be positive and share some vision.
-Use people that I know who have skills. My sister, contacts at Bridgerland, my sister-in-law, my dad and others.
-Plan for cross corp business. Create a cross corp mapping table that allows any corp to crisscross or map to any other corp. This could be a one-to-many from the main corp to his/her outside vendors and/or customers. Sharing customers, sharing parts, sharing stock/units, etc.
-As a marketing game… Do a competition between universities and private parties to create a niche product that is able to ride on top of the adilas engine. (Different skins or different functions.)
-Sell adilas as the engine!
-How will people know what our product can do? What are the core functions, types, and tools? The “how to” is different than the “what is possible”.
-Look for and harness people’s potential. It is great to share, build and grow. Help other people be successful!
-What functions do we provide and/or offer? Once you know and choose a function, we can then teach you how to use or do those functions.
-Pricing… there is or there are tons of variables… which ones are important? Which ones are key indicators? How can we let price be our friend? Reps really struggle with how open the concepts and pricing structure are… We may need a standard or some way to quantify this.
 
Click to view time photos.
AU 2928 Daily Tasks 4/3/2013  
  • Went down to Eagle Mountain to meet with my cousin about being an adilas sales rep. We talked some history and concepts and answered questions. He has some good talking skills and you could see his mind working and trying to grasp different things. Great meeting. He has some good potential. He also mentioned that his dad, my uncle, had built some software that he called “the business time machine.” I told my cousin that I would be interested in speaking with my uncle about some of the concepts. 200 miles.
 
Click to view time photos.
AU 1154 Daily Tasks 4/4/2013   • Working on numbers and proforma Excel documents. Forecasting and documents dealing with adilas numbers.
• Went to Smithfield to set my mom up on adilas. Talked with my mom and dad for a while about concepts and vision of adilas. Did some consulting with my parents on paper and then started going through the setup process. 10 miles.
• Went in to Logan to talk with a contact and his accounting buddy. Great meeting and I learned a lot. I got roasted a bit but no harm done. It was fun to express myself. I was very honest and they were very point blank honest. My contact ended up watching and listening and his buddy and I battled balls back and forth. I come out of the meeting knowing what they were looking for and being able to talk about our vision for the future. In a nutshell, I took away the following ideas… adilas is an eBusiness model, we are currently in the cost covering mode, be careful of the innovation model (quick in & quick out), we may end up being acquired by some other company, we are looking for a loan, not for investors at this point. In order to get a loan we need to know what is it for, how much, and what are we willing to give up? We also talked about notes and what are my end goals? Is it a certain amount of passive reoccurring money a month or what? We did go in circles a few times but I felt very good about it and what I’m learning. A couple things that were hotter topics were breaking or changing tradition, changing roles, why would a company want to change from their current system, and what is the scope of the business? I brought up about sharing code and assets and that was met with very negative reactions. Anyway, just some notes.
• Research and recording ideas.
• Working on recording changes to customer assignments for invoices.
 
Click to view time photos.
AU 1155 Daily Tasks 4/5/2013   • On the phone with Steve. We talked a lot about advertising and marketing and getting the word out there. We talked about me holding on to things and not wanting to put things out there until they are done. That is a pro and a con. We are at the point we need to get this product out there. What we really need is tons of reps. We need to just get out there.
• Working on links to custom paperwork and documents for all main application types. As I was doing this update, my vision was opened and the word “data” and managing data is what we do. See the notes on this other page - for some of the thoughts. (Below)
• Reviewing and working on Flash CSG stuff. Trying to get back up to date on Flash stuff.
 
Click to view time photos.
AU 1181 Daily Ideas 4/5/2013   -We are master data trackers – tracking data is our business.
-We specialize in dynamic data tracking – real-time virtual data portal.
-Dynamic searchable data or in other words… “all data is live and searchable”. That’s what adilas is!
-Something that would really help adilas would be to get photo galleries for each main application player. We already have seven of the twelve.
-We track data, we search data, we pull reports from data, we help you create relationships between data, we run data over time, we eat and sleep data! We love data and help you tell the story of what you are doing using data.
-Big Data is a new buzz word… kind of interesting.
-Things that need to be done can all fit under the term “future development”. Keep it very positive. Simple, I like it.
-I’m so grateful for personal revelation and communication with God. I’m glad that I can talk to Him at any time, from any place, about any subject. That’s very important to me!
-We are also very good at building stability and taking the time to get things done right. Along with this, we are able to maintain our costs at an incredibly low rate. We can by happy with what we have and can keep going and going and going.
-We also write and record everything – we document the story!
-We are very good at listening to our customers and writing down and recording their ideas. We then try to work those ideas into the puzzle. Almost half of adilas has come from user feedback. We need to continue to harness and tap that resource.
-We are willing to keep on developing and thinking of the future. We love ideas…
-Riders on the storm… Song by The Doors. –Meaning we are the riders.
-We are a live test bed which actually produces ideas… almost an idea center or idea farm. We then take those ideas to the next step. We do that over and over again.
-We love to share knowledge, ideas, concepts, and even code.
 
Click to view time photos.
AU 1156 Daily Tasks 4/6/2013   • Working on the online Flash course through USU.
 
Click to view time photos.
AU 1182 Daily Ideas 4/6/2013   -We are good at fundamentals and stacking basics on top of basics. We can do that all day long!
-One thing that could help would be a couple weeks to update our main website. Including verbage, layout, pages, meta tags, links, buttons, and model or scope.
 
Click to view time photos.
AU 1157 Daily Tasks 4/8/2013   • Working on eCommerce settings.
• On the phone with Steve using GoToMeeting to help Steve with some code stuff. We went over Cold Fusion components and how we already use an internal API of sorts for all of our pages. He was shocked that we already have so many pieces already in place.
• Back on eCommerce settings.
• On the phone with my cousin. We went over a quick demo of adilas and what it can do. I’m excited to get the product out to market. We did talked about dummying things down, dressing things up, and allowing for a 30-60 day free trial. Good stuff.
• Emails, phone calls, and tech support.
• On the phone again with my cousin about marketing ideas. We talked more about a free trial period and motivating sales staff to continue selling once they are making enough money. Human nature kicks in and people get lazy. How do you keep them going?
• Working on eCommerce.
• Working on the Flash CSG class stuff.
 
Click to view time photos.
AU 1183 Daily Ideas 4/8/2013   Marketing notes from my cousin:
-Give out free 30-60 day trials. Provide an easy to use tutorial and/or setup wizard and make it super simple.
-We may need to dummy things way down. This could be by permission, interface or skins, or by function.
-Two basic tutorials: Sales and inventory tracking and CRM (Customer Relationship Management). Quick and simple.
-If we offer a lifetime commission model… How do we continue to motivate our sales staff? We may need to attach a quota or something like that. Just an idea.
-Make a distinctive pricing guide. Lay it out and provide a standard matrix for people to use. Maybe with price points and up sales.
 
Click to view time photos.
AU 1158 Daily Tasks 4/9/2013   • Prep for a meeting with my sister. We met and talked about “protecting ourselves by sharing!” Basically we had a meeting about what we need to do to get adilas concepts out to the public. We went in circles but ended up deciding that we need to teach and focus on concepts. If we help people learn and understand concepts the rest (processes, interface, etc.) will be much easier for them to get and understand. We also talked about different ways to show and tell about these concepts. We came up with histories and stories about concepts or animated timelines to show how things developed. One focuses on the concepts and how they came to be and the other focuses on general “see a need, fill a need” process that has happened over time. Some awesome stuff. See later on for meeting notes.
• Went to Smithfield and went by the bank. Talked with a bank associate about some business banking stuff. Including ACH (auto clearing house) payments, SBA (small business administration) loans, and general banking stuff. He wants me to contact him next week. 10 miles.
• Brainstorming and talking with my wife about options and where we are headed. We went over a light business plan and my wife agreed to help me write the actual business plan. Great meeting and I think it helped her catch the vision of where we are going.
• Tech support and emails.
• Recording notes.
 
Click to view time photos.
AU 1184 Daily Ideas 4/9/2013   Recap of meeting with my sister to talk about training and direction: Developer’s notebook
-Protect ourselves by sharing!
-Concepts inside of adilas are 10x (times) greater than the code.
-Visually display the concepts (photos, animations, video, etc.)
- Provide the history and story
o Nested to details
- Brainstorming notes
- Developer’s notebook
- Actual ideas and working pieces
o (Sketch in notebook of brick wall – foundation piece being things like: time, permissions, settings; the next level: data, empower users, etc., etc.)
-Concept based learning
- Each concept needs a story
-Abundance Model – “enough to go around” – sharing
-Tie or connect through feelings or feeling a part of the story.
-“See a need, fill a need” (movie – Robots) – This is a “base”
- As a need is filled it creates a new something or something new
-What about an interactive timeline
-Concept Buffet
-Animated Timeline or story
-The movie “Up” – see entry from 1/5/13 to 1/8/13
-We’d like to show the development of these concepts in two ways. –By Concept –By Timeline
-Teach the “why”
-When recording data (actual pieces) we will need two or more pieces… what concept or subject (players) and what timeframe.
-Figure out the core concepts – we started out with about 20, then decided to go to 10, and then the list kept growing and growing. Kind of started going in circles. I took the assignment to come up with the master list of concepts and sub concepts.
-For the record, here are a few things we scribbled down:
- Centralizing data
- Going to the source
- Empowering the user
- Permissions and settings
- Objects and data over time
- One-to-many relationships
- “See a need, fill a need” – “base” or foundation
- Next logical step – development
- Systems thinking
- Games (rules, players, goals, challenges) game of business
- Data
- adilas – all data is live and searchable
- Dynamics
- Relationships
-Other core concepts that we were listing out:
- Education and sharing
- Types and functions (“why” or building blocks)
- Roll call – what is your story – return and report
- Record the story – the story may be more important than the numbers
- Scalability
- Custom
- Dreaming
- Players
- Culture, vocabulary, change
- Put things to rest “life cycle”
- Mix & blend (we mix concepts and players to create flow, processes, and interface)
- Catch the pieces
- Data mapping
- Peace of mind
- Point the picture – vision of the future
- Open entry, open exit (no contracts, pick & choose, only use certain pieces, etc.)
 
Click to view time photos.
AU 2278 Brainstorming - Developer's Notebook 4/9/2013   Meeting with my sister going over what we want to do with the developer’s notebook:
(Other sketches & diagrams can be found on the scan in the photo gallery)
- Protect ourselves by sharing!
- Concepts – 10x greater than the code
- Core concepts
- “Visual” or video concepts
o History & story
o Nested to details
o Brainstorming
- Driving a car... we learn concepts like right turns, left turns, parking, passing, etc. Then we can go anywhere… even to places that we don’t know or haven’t been.
- Concept based learning
o Each concept needs a story
- Feel the story
- Abundance model – “enough to go around”
- “See a need, fill a need.” – Robots movie.
o Creates something new
- “Base”
- Interactive timeline
- Concept buffet
- Animated timeline or story – The movie “Up” – see entry from 1/5/13
- Two different ways – by concept or by timeline
- Teach the why
- When recording data (actual pieces_ we will need two pieces… what concept or subject and what timeframe
- Figure out the core concepts – 20(ish) – (subs or subs of nesting)
- Let’s do 10 – everything is somewhat built on this kind of model – (plate & cups sketch: with the main (plate) and cups (line items, payments, system history, flex grid, other content, custom docs, photos, etc.)
o Centralizing data
o Going to the source
o Empowering the user
o Permissions and settings
o Objects and data over time
o One-to-many relationships
o See a need, fill a need – “base” foundation
o Next logical step – development
o Systems thinking
o Games
o Data
o Adilas – all dad is live and searchable
o Dynamics
o Relationships
o Education and sharing
o Types and function (why)
o Roll call
o Scalability
o Custom
o Dreaming
o What is your story – “record the story”
o Communication
o Players
o Culture, vocabulary & change
o Put things to rest “life cycle”
o Mix & blend
o Catch the pieces
o Data mapping
o Peace of mind
o Paint the picture – vision of the future
o Open entry, open exit (no contracts, pick & choose, only use certain pieces, etc.
- This is how we track and manage data…. We Mix Concepts & Players
- We are almost coming full circle instead of us dictating flow, processes, and interface – we want people to mix and blend concepts and players to make their own flow, processes, and interface
 
Click to view time photos.
AU 1159 Daily Tasks 4/10/2013   • Prep for a meeting with my sister. We met and talked about “protecting ourselves by sharing!” Basically we had a meeting about what we need to do to get adilas concepts out to the public. We went in circles but ended up deciding that we need to teach and focus on concepts. If we help people learn and understand concepts the rest (processes, interface, etc.) will be much easier for them to get and understand. We also talked about different ways to show and tell about these concepts. We came up with histories and stories about concepts or animated timelines to show how things developed. One focuses on the concepts and how they came to be and the other focuses on general “see a need, fill a need” process that has happened over time. Some awesome stuff. See later on for meeting notes.
• Went to Smithfield and went by the bank. Talked with a bank associate about some business banking stuff. Including ACH (auto clearing house) payments, SBA (small business administration) loans, and general banking stuff. He wants me to contact him next week. 10 miles.
• Brainstorming and talking with my wife about options and where we are headed. We went over a light business plan and my wife agreed to help me write the actual business plan. Great meeting and I think it helped her catch the vision of where we are going.
• Emails and tech support.
• On the phone with Steve talking about concepts, loans, and business plan stuff. We just need to get it out there.
• Bank stuff and brainstorming on concepts and ideas.
• Recording hours and notes from a meeting with my sister yesterday. Since that meeting my mind has been going nuts over concepts and players and how they interact.
• Brainstorming on the core concepts inside of adilas. Reading and writing down ideas.
• Steve called and had some questions about code stuff. We also talked about concepts. Steve said that adilas virtually catches everything we do physically. Basically, we either do it and then record it or we record it and then do it. We talked about the engine and who our users are. We also talked about fundamentals and doing them over and over again. Concepts about concepts.

• Tech support and emails.
• Recording notes.
 
Click to view time photos.
AU 1185 Daily Ideas 4/10/2013   -We mix concepts and players
-We are almost coming full circle… Instead of us dictating flow, processes, and interface. We want people to mix and blend concepts and players to make their own flow, processes, and interface.
-Everything is somewhat build on this kind of model: (sketch in notebook of main plate with little cups – “holders/containers”
1. Main
2. Line items
3. Payments
4. System history
5. Flex grid
6. Photos/scans
7. Custom documents
8. Other – content (files)

1. The main – this holds the player name and id number. It also holds basic information that applies to everything else. This is like the main container. In the model, this is the plate and the bowl.
2. Line items – These are the details, items, or categories of the main. Add as many as you want to tell the story.
3. Payments – These are money amounts that get applied to help satisfy what is owed (incoming or outgoing). Unlimited.
4. System history – These are history notes, dates, and flags that get added behind the scenes as a user does an action. Unlimited and un-editable. This is the audit trail.
5. Flex grid tie-ins – These are for user-maintained histories, custom fields, or tying to other system players. (Buddy system.) Optional. Unlimited.
6. Photos/scans – These are for scans, images, photos, and documentation. Optional. Max of 100 per player.
7. Custom documents – These are custom documents that may be needed by the main player. PDF’s, Excel, Word, forms, etc. Optional. Unlimited. Assigned on a company level.
8. Other - content (files) – These are files that need to be attached to the main player. Audio, video, PDF’s, Excel, Word, contracts, etc. Optional. Unlimited. Currently under construction.

-It would be really cool to have some simple learning modules that could teach or go over concepts, flow, and processes. I’m thinking small Flash widgets of sorts.
-What if we had a bird’s eye view of adilas. Big picture. Simple overview. Basic concepts. Basic players.
-Some people (most) are in a hurry and they don’t want to be educated. They want a new care without any driver’s ed course.
-Driving a car… we learn concepts like right turn, left turn, parking, passing, etc. Once we learn the basics we can go anywhere… even to places that we don’t know or haven’t been.
 
Click to view time photos.
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
 
Click to view time photos.
AU 1160 Daily Tasks 4/11/2013   • Writing new concept idea and brainstorming on a concept buffet or tons of different concepts.
• On the phone with Steve. We used GoToMeeting and I helped him with some custom code and dashboards he is making for clients. His skills are improving and he is doing awesome.
• Phone calls, tech support, and sending some pages to Steve to help with permissions.
• On the phone with a client doing some training for getting inventory into the system. Editing invoices and applying payments.
• Tech support.
• Working on a list of core concepts inside of adilas. Lots of brainstorming and writing. Light brainstorming on using elements of time to help with my notebook and recording history and/or even family history.
 
Click to view time photos.
AU 1186 Daily Ideas 4/11/2013   -All system players (main application types) need a general reference number field. This would allow for any outside alias names or numbers from other outside systems.
-On the main… There is usually a lock-down option and/or a lock-down permission of sorts.
-Every major player needs:
- The main
- Line items
- Payments
- System histories
- Flex grid tie-ins
- Photos/scans
- Custom documents
- Other – content or files (assigned per corp)
-Vendors, users and payees need a general notes field.
-Work on standardizing things
-It is okay to still need future development.
-My dad and I went on a hike up Smithfield Canyon. We saw hundreds of new improvements. On the way home we were talking about how those improvements will open tons of doors and will more people enjoy that area. We also talked about improvements that we make to adilas and how they will help tons of people.
-Maybe make a business plan for MDI and then use that and invest in adilas.
-On a hike with my dad we were talking about all of the inter-connected systems in the human body. It works like a machine and all of the systems need to work together to make things happen. I asked my dad to start thinking about doing a human body systems comparison with the adilas concepts and players and how they work in a system. It will be fun!
Human Systems vs. Adilas Systems
Skeletal (bones) -?
Muscular (muscles) -?
Nervous (brain & nerves) -?
Digestive (stomach & intestines) -? Concepts & Players
Respiratory (breathing, lungs & heart) -?
Circulatory (lungs, blood, heart, veins) -?
Reproductive (make new ones) -?
Endocrine (waste) -?
-Speaking about interconnected systems – we have often asked, what pieces can we do without? The answer usually comes back as none of them – we need them all or certain people need them all.
-I had the thought – what would happen if you tried to take your religion out of your personality? Depending on how inter-connected they were… it could be impossible to separate. Kind of like having a body but not having bones or muscles. They just go together (or should go together).
-On some of our help files and pages (normal webpages) it might be nice to make some of them into Adobe PDF documents for easier printing. We have 400+ help files and pages of information. We almost have a mini library…
-The deeper we get, the more some of our jobs become organizing and grouping large amounts of data. On this same note… the first step is catching all the data. Once we are catching the data, then the task becomes being able to search, group, and categorize that data. Without being able to quickly and accurately get at the data, it almost becomes like a broken model.
-My notebook is exploding… My paper model is starting to break. I’m writing as fast as I can but I have no way to go back and search it. I’m starting to duplicate things, forget things, and it is taking tons of time and then tons more time going backwards. It might be time for elements of time and using adilas (all data is live and searchable) to record and track adilas.
-Speaking of breaking models… My notebooks are all on paper and in tons of different spots. I need to centralize the data, categorize it, record it, and document it. I have a lot of important stuff but it is all spread all over the place.
-I think I will make a master element of time for each main topic. I will then print out a list of main topics and their id #’s. I will then go through my notebook and hand sew elements of time together using the flex grid. My master thread will hold id’s for all subs. Each sub will hold its own data, images, notes, and details. The mini subs will be standalone by date (historical) and the master thread will be by category according to the thread name. Here is a simple diagram. This will be duplicated over and over again…
-(Sketch in notebook of this idea) Flex grid to subs, flex grid tie-ins, sub elements, master thread or by category.) (These (referring to subs) would be subs or the details. They would be standalone entries with their own dates, captions, notes, colors, and photos/scans.) (They would be sewn together using flex grid.)
 
Click to view time photos.
AU 2280 Brainstorming - Adilas Concepts 4/11/2013   - All elements work together, interacting and influencing one another.
- 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.
- 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.
- Grocery Store Analogy: 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 interfaces
- Objects are defined by relationships
- Construction – you could build anything with a saw, drill, hammer and a screw driver (goal, tools, how to apply the tools)
- My son was reading and the word “turnkey” he turned into “turkey” (gobble, gobble). He then said adilas was a wild turkey chase. You go all over the place like chasing a wild turkey. Kind of funny!
 
Click to view time photos.
AU 1161 Daily Tasks 4/12/2013   • On the phone with Steve talking about the venue for the Colorado training event. We will be right in Denver just above a rep’s office. We also talked about using GoToMeeting for weekly training sessions.
• Working on flyers. Also tweaked the main adilas.biz homepage to highlight what we do and added some new graphics and flyers to the page. Worked on a new flyer to introduce adilas.
• Working on a new intro to adilas.biz flyer. Lots of bullets, a few graphics, and small headings. I also updated the training flyer for the Denver location.
• Posted files online.
 
Click to view time photos.
AU 1187 Daily Ideas 4/12/2013   -We could use GoToMeeting and open up adilas university with almost nothing other than what we already have. We could schedule classes, teachers, subjects, dates, times, etc.
-We could even use elements of time to fill out class rosters and track attendance.
-Then deeper we get, the more I’m seeing elements of time being used more and more for tons of different pieces of the puzzle.
-On the tech spec flyer. I would really like to show the requirement and then show options and rough price ranges to help our users out. The only requirement is a device that can connect with the Internet. Everything else is optional.
-On the tech specs – break it down to what it does, how it works, and even how to test it. Talk about human interface devices. Also load the deal for custom paperwork, custom reports, forms, labels, and interfaces.
 
Click to view time photos.
AU 1162 Daily Tasks 4/13/2013   • Working on eCommerce pages
 
Click to view time photos.
AU 1188 Daily Ideas 4/13/2013   -To help with search engines… we need to update keywords, descriptions, and other meta tags. We may even need to store that info in the database per corp for full eCommerce. That way each corp could have their own meta tags.
 
Click to view time photos.
AU 1189 Daily Ideas 4/14/2013   -My wife’s dad is talking about family history… “People are defined by their relationships.” I can see the same thing with objects. “Objects are defined by their relationships.” Data makes up objects and interconnected pieces of data make up relationships. In my model, it all comes back to data and data relationships.
-We created adilas with certain main players and predetermined relationships. Each company and/or user then goes into adilas and creates and sets up their own players and relationships. Basically, we built a world where other people may come and build their own world. Kind of fun.
-What if, beyond the API (application programming interface), we allowed each and every page to be skinned by corp and by user. This would be more in-line custom code. What fields to use, what order are the fields in, where do they go once submitted? Imagine all of the settings being able to be recorded and controlled on the fly from the database. This could also be what buttons do you want? What links would you like? And even what do you want your page to look like? Click, point, drag and drop, buttons, links, graphics, forms, reports, layout, etc.? What do you want your world to look like and be?
-The main players inside of adilas are kind of like our “tool bag”. Match tools to jobs!
-Mix and blend – players and functions.
 
Click to view time photos.
AU 1163 Daily Tasks 4/15/2013   • Brainstorming and working on narrowing down main core concepts and theories for adilas. Come up with 12 core concepts, 12 main players, and 12 business functions.
• Organizing functions, players, and concepts. The server had some troubles and we had a reset.
• On the phone with a bank associate talking about Business products.
• On the phone with my dad and a contact from USU printing. I will be doing a demo with him the first part of May.
• Writing down ideas and concepts.
• Adding a news and update page.
 
Click to view time photos.
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.
 
Click to view time photos.
AU 2281 Brainstorming - Adilas Functions, Players & Concepts 4/15/2013   - Pushing towards a self-service model
- GoToMeeting – weekly training session
- Pay for training sessions
- New page when you login – training & updates
- Adilasuniversity.biz – 2 classes a day, 5 days a week
- New front end for the main website
Adilas…..
- Core concepts
- Application players
- Business functions
- Results
“Get results by applying business functions, application players, and core concepts.”
Business Functions (Results & Outcomes) what do you want?
1. Sales, Inventory Tracking, and 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 and Accounting Functions
9. Histories and Reports
10. BI (Business Intelligence)
11. Web Presence and eCommerce
12. Virtual Data Portal (Big Data)
Application Players (tools to use) – What 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 and scheduling)
Core Concepts – (why & how) – (why & how does it work?)
1. Players
2. Relationships
3. Problems, Needs, and Goals
4. Decisions and Choices
5. Cause and Effects
6. Accountability
7. Objects and Data Over Time
8. Systems
9. Permissions and Settings
10. Vision and Future Developments
11. Tech, Tools, and Maintenance
12. The Story
 
Click to view time photos.
AU 1164 Daily Tasks 4/16/2013   • Went in to town to see a bank associate. We talked for a while and then a rep from Salt Lake City came in. We talked about adilas and where we’ve been and where we are headed. We talked quite a bit about ACH (auto clearing house or automatic debit). We want to be able to use ACH as a payment method for adilas. We also talked about merchant processing and direct deposits. It was a good meeting and I think that he got a good taste of what we are doing and what we are looking for. 20 miles.
• Went back in to town to meet with my dad. He wanted me to talk with a lady in the Business Resource Center at BATC. On the way, my dad and I chatted with a number of people. I talked with some contacts about elements of time and time clocks. We, my dad and I then talked with a lady about a car repair facility. We then went over to meet with the lady in the Business Resource Center. We talked about tons of stuff and she had run an art gallery for a while. As we talked, she was virtually reliving memories about what was required to run her business. She really seemed to connect with what we are doing and seemed to enjoy the direction. She gave me some contacts up at the University who deal with entrepreneurs and business mentors. She is part of “SCORE” which is a national organization that helps small businesses. Entrepreneurs may be a perfect match for what we do and what we are offering. We talked with Cindy about presenting and giving classes on what we do. She was very open to the idea. Good stuff. 20 miles.
• Lunch meeting with my dad. While at lunch my dad grabbed the manager and had me talk to him. We chatted for half an hour about how to run things over time and help with flow and editing data. We talked a lot about hot interface plays into the puzzle. We also talked about how new and modern processes sometimes need to be new from the start. Tradition can be a huge wall. One of his problems was dealing with three different systems and marrying all the data together. That is so common in businesses today.
• Writing and recording hours. Lots of fun stuff today.
• New logo for a company.
 
Click to view time photos.
AU 1191 Daily Ideas 4/16/2013   -On the API (application programming interface)… I want to control access on a corp level and on a user level. This will end up being almost a sub permission level. Inside of adilas, each section has a permission. On the API level, each function could have a permission level just by allowing access or not. This is not required but could be allowed. Major options for customization and special tweaks. Think permissions on a function by function basis.
-Some people who see the need or have felt the pain – know and understand what we are doing!
-Interface is huge! We want a standard classic interface and then tons of industry specific interfaces. If those don’t work, build your own through the API.
-Yesterday, I was thinking results = functions x players x concepts.
-Interface is a huge part of that puzzle. Instead of saying times (like a math function) what if you say mix and blend until you get interface. So, in a way interface is part of the results.
-Promotion codes, tracking sales, loyalty points, customer gift cards, etc. All of these are future developments. Some of this starts getting into marketing.
-Two possible spots for more love are in marketing and HR (human relationships). Both could use a little dose of lovin’!
-On pricing and billing – maybe point out the monthly stats as part of the monthly billing structure. That might help us get an idea of usage and prices. Being able to save as a PDF would also be cool.
-The secret is to centralize the data and then record and catch the pieces. If you can do these two things, the rest will be possible. It may not be in the right format (yet) but if you have it, you will be able to use it.
-On the content server… We need to make sure and store the bigger files in the database. We want to prevent any direct browsing of the files. If the users want it, they will need to go through the correct channels.
-My dad said this today… “These guys haven’t broken any rules per say, but they have broken tradition.” That’s a fun way to put it!
 
Click to view time photos.
AU 1165 Daily Tasks 4/17/2013   • Added a quick news and update page for adilas. It is a basic page that we will be updating constantly. Everybody who logs in gets directed to it. They can then either read it or just go to the homepage. This will help us communicate better with our users.
• Small payroll tweaks. Phone calls and emails. Checking on two payroll issues. One was calculating memo hours and the other one was dealing with custom state unemployment calculations and settings.
• More work on the state unemployment calculations.
• Posted files online.
 
Click to view time photos.
AU 1192 Daily Ideas 4/17/2013   -Sometimes I get hung up about doing things perfectly right the first time. That is great but maybe too rigid. For example: One time I was looking for my window scraper and couldn’t find it. I started getting mad and thinking which one of my kids moved it or didn’t put it away. In the meantime, a nice lady came up and used her coat sleeve and cleaned off my windows. I just stood there in shock. It was a great lesson – one that I need to be reminded of often.
 
Click to view time photos.
AU 1166 Daily Tasks 4/18/2013   • Light tech support.
• Then on the phone and using GoToMeeting with Steve about his custom code pages he is working on. He is learning tons and doing great. A fun side note is he is using our internal API to create his custom files. The more he uses our own API, the more he sees how that can be used by other outside developers.
• Brainstorming, tech support, and working on the introduction to adilas.biz flyer. Added a new formula that talks about what we do. It is: Results = Mix (Functions, Players, Concepts) I then listed 12 results, 12 functions, 12 players and 12 core concepts.
• Working on two different flyers. One is a simple introduction to adilas. The other deals with the concepts and formula for adilas key pieces. Lots of small tweaks and having my wife read over parts.
 
Click to view time photos.
AU 1193 Daily Ideas 4/18/2013   -Define the goal, objective, or desired outcome. This is the best place to start. Once you know the goal, you can then figure out how to get there. This is a huge piece of the puzzle.
-We have a couple people who are masters of different accounting programs. It would be cool if we could hire them to help us with common processes in other programs. For example: In QuickBooks you do this. In adilas you do this. In Peachtree you do this. In adilas you do this. Etc. I’m thinking of other contacts.
-Adilas may need a custom solutions department or team. This could be skins, graphics, interface, flow, or even franchises.
-On photo galleries. Add small graphic to try to help people get information about uploading photos. Put it on the top of each add/edit photo page. This will help users get the correct settings.
-Perspective… what level are you at? What do you want to see? Where would you like to go? I was hiking with my dad and we were way up on the side of a mountain looking down on the valley. Being way up high allowed us to see things differently as compared with being in the middle or at the bottom. The feature we were looking at were the same but depending on our perspective they seemed or appeared different. As I was hiking I just kept thinking about the word perspective and how that applies to tons of different things.
-Along with perspective, we have a fun little graphic that my daughter made. It is a busy street scene with cars, roads, buildings, parking lots, etc. Here is the text that we have on graphic… Think of a bird’s eye view looking down on a busy street… Lots and lots of activity… coming… going… turning… doing… staying… becoming… what if you could… (then we had a little picture of a helicopter). Watch from above? Be on the street level? Be inside one of the cars? Actually play back the movie? (then in bold) Well, you can!!! This little graphic deals with levels, perspective, permissions, and even roles and permissions. Kind of fun.
-Learning for transfer… Once you learn to drive a car, you can drive a golf cart, a van, a truck, an SUV, etc. The concepts are the same. You may need to make a small changes or tweaks but the concepts are the same. The same thing happens inside of adilas. Once you learn the concepts, you can apply them in any situation. You will also be able to mix and blend concepts. Good stuff!
 
Click to view time photos.
AU 1167 Daily Tasks 4/19/2013   • Added two new PDF flyers to the main adilas.biz homepage. One was a simple two page introduction with light history, features, and pricing. The other one was a single page document called the adilas formula.
• Updated the news and updates page. Posted files online.
• Working on eCommerce. Reviewing notes.
• On the phone ordering a new computer projector for adilas training.
• Working on eCommerce.
 
Click to view time photos.
AU 1194 Daily Ideas 4/19/2013   -Marrying multiple systems together… There is a known problem with businesses that have multiple software packages that they use to run their business. What if we added extra fields or extra tables to help with that process. We already know it is an issue. Why not meet the issue with open arms and say “we have this… what do you have? How can we tie them together? Let’s meet together here in a pre-built connection tool or sorts.” Anyways, we already know that it exists, why not plan accordingly. We could even use the same features to crisscross multiple corporations. This could be brother/sister corps, parent/child, etc. Even vendor/consumer relationships. Relationships help tell the story.
-We made a little graphic with a globe inside of the adilas logo. Start at the universe level and then drilling down and go deeper and deeper. Start way up and then virtually zoom in.
 
Click to view time photos.
AU 1168 Daily Tasks 4/20/2013   • Brainstorming on ice-down dates and system wide roll call per day. Good stuff!
• Added a small graphics to help people click on the help file for photo galleries and add/edit photo/scans. The help file has a number of settings and tips for photos.
• Working on the logic for the add to cart button for eCommerce.
 
Click to view time photos.
AU 1195 Daily Ideas 4/20/2013   -Thinking about “roll call”… I don’t even know if this is possible, but would happen if you had one table just for roll call? This would be what flag, what date, what checkpoint, what status? This is just an idea but if we had everything in one place, it sure would make reporting easier. Currently we have all of the pieces (mostly) but they are all continued in-line or on tons of different tables.
-This idea is somewhat related to some topics back in October and November of 2010. We have tons of brainstorming on watchers, feeders, standalone declarations, etc. A global “roll call” table may end up being part of those options.
-In a nut shell – things happen every day (changing, turning, staying, coming, going, becoming, etc.) Our goal is where is it at (the objects and/or data) when the day closes? Almost like a “snapshot” or daily summary. If more details are needed, we could always go back and check on the objects history.
-The one (or more) problems with this deal with changes and going back in time. This is especially true if one value is related to another value. You end up getting a cause and effect chain of events.
-One way to solve this is to put each corporation on its own mini adilas and then look-up all of details, dates, and flags on the fly. We could speed things up by using numeric dates, smaller tables, and using global watchers that help things stay contained. We have a thing called the “ice down” date. That could help us lock things down and then don’t allow any changes. If a change is needed, we could back up the ice down date and then record changes. That date could be a backward compatible border or boundary of sorts. Basically, a no one goes past here unless the ice down date is backed up.
-Another thought keeps playing through my head… what if you still kept – all data is live and searchable – but added a lock or sorts. You still want all of the data but you also don’t want everything to be flexible all the time. Maybe once you lock it down, no one gets to touch, unless the lock down (ice down) date gets pushed back. Everything is still there and plays a part but it prevents tampering and changing once it gets perfectly locked down.
-Maybe think about formulas in a spreadsheet… But be able to lock them down…
 
Click to view time photos.
AU 1169 Daily Tasks 4/22/2013  
  • Working on the training flyer for showing parts of the main system players. Using the analogy of plates and cups.
  • Tweaking the player flyer to include as analogy between the human world and the adilas world. Printing out tons of flyers and updating the main website with the new flyers.
  • My sister and I went on a business road trip out to Colorado. We had a three day training event in Denver and then a full day brainstorming and meeting with the adilas team. Great week! Here are some highlights of the trip:
  • We drove to Colorado from Logan, UT. Along the way we talked about concepts and learning styles. The total trip was 1,476 miles.
 
Click to view time photos.
AU 1196 Daily Ideas 4/22/2013   -For training… It might be fun to let other people drive and have control of the master computer. They could do tasks that they normally do. They could then comment or teach as they go or we/I could comment and give the play by play action. Kind of like a sports commentator.
-Be able to search parts by quantity – high to low
-Include the meeting Id’s on the flyer. GoToMeeting
-Add industry specific notifiers – semi push technology.
 
No po photos available. Click to view time details.
Adi 670 Denver Training Class 4/23/2013   Three day Denver training class.
 
Click to view time photos.
AU 1172 Daily Tasks 4/23/2013   Went to the first day of class. Crazy weather. Stuck in traffic for two hours. The wrong address was on the flyer. Got lost and had to make some phone calls. Got to the site and setup for the class. We had 10-15 people in the class. We tried using GoToMeeting and ended up getting kicked off multiple times. Lots of good discussions. The topic was very heavy toward MMJ or Medical Marijuana industry. Good session. The class dynamics were pretty crazy with lots of different personalities.
 
Click to view time photos.
AU 1173 Daily Tasks 4/24/2013   Went to the second day of class. We had better class dynamics and had a great day. We covered the new introduction to adilas flyer and read and discussed it in class. We then had a treat and allowed a couple power users to lead and show the class what they do inside of adilas. A gal from a company here in Denver did a great job and did a couple of hours of training. Good stuff. We still had a few problems with overloading GoToMeeting. Better day with less craziness today!
 
Click to view time photos.
AU 1174 Daily Tasks 4/25/2013   Went in the third day of training. Good day with even less crazy class dynamics. We started off the day going over the new flyer dealing with system players and main application types. We then went into a small exercise creating objects using plates and cups. We had some good discussions and did lots of question and answer stuff. One of our top reps in the Denver area also did some flow charts and live consulting during the session. It was fun to watch what was going on. After the meeting our team member volunteered to help coordinate “open communication” and flow for the adilas team and reps. Good stuff! As a side note, I got to meet a number of people today that I had only talked with over the phone. That was fun.
-As an observation, I was quite impressed with one class participant. He was quite technical and understood concepts on a much higher level than most of the rest of the class. He added lots of good insight to the class discussions. I can see great potential in that type of user/consultant once they catch the vision of where we are going with adilas. Good stuff!
 
Click to view time photos.
AU 1197 Daily Ideas 4/25/2013   -What if custom flow included custom tables that could be made inside of adilas by the users. Imagine being able to name it, create fields, assign data types and even create relationships between custom and standard tables.
-Inline custom code at a point and click level. Think of master time templates and how we virtually allow a user to pick and choose types and functions.
-What if we created a new product that could be sold as a “whole system” and then allow that company to customize and build the entire model. We sell the basic “shell” and let them customize it and skin it as needed. This could literally be their own adilas.
-“Open communication.” Quote by one of the adilas team members at the Denver training session.
-“Step out of the door and let them come in!” – My friend in Colorado
 
Click to view time photos.
AU 1199 Daily Ideas 4/25/2013   My sister took a bunch of notes. These are some of her notes:
- Permissions/settings – finite (a few) main things, click on it (small list) and then expand your options. Instead of having things all together, break it up into sections.
- Page settings – personalized - almost like a print preview setting. Be able to check or click something and have it interactively show up or show what it does.
- Knowing/understanding settings and permissions. Not just how to use it but what does it do.
- Email & text message blasts through adilas. Something free and/or connect to an outside service.
- Access to print barcodes… they would like to print groups, sheets, or be able to get at them quicker.
- Loyalty punch card, gift certificates, reward points, and other marketing options.
- People really want quick, user friendly, efficient flow and effective tools.
- A control or view to see who is logged in.
- Interaction is the best part for digesting the info.
- Be able to sort parts or quantity per vendor. This would help with ordering.
- It would be nice to show ways or how things expire. This deals with inventory and expiration dates.
- Some of the companies would like to use QR (quick reference) codes. These are 2D barcodes that can store more info than a standard font based barcode.
- People would like to send invoices by clicking a button.
- Through eCommerce, allow people to agree to text and email blasts.
- Percentage discount calculator on incoming PO’s. Basically, allocate a certain percentage across the board. Currently this is a manual calculation.
- Reflexive side of the flex grid.
- Add a new permission for super admin photo management.
- Specific industry training or specialized info and feedback.
- Notifiers
- Capture and allow digital signatures inside of adilas.
- Be able to control custom data types. How do you want custom data fields to play? Text, numeric, Boolean, date, etc.
- Art on consignment idea for interfaces. Our rep mentioned tattoo artists and how they market their art work. If you want this, go see so and so.
- We had a request for a couple of old reports to be brought back. They are: Best sellers report and Build your own report (mend & repair).
- Export to CSV (comma separated values) files for all data inside of adilas.
- “Open communication” – conversation at the end of the day with adilas team members and a rep.
- We are trying to take our shared database model into smaller individual pieces. We still want to allow multi and sub corporations. We may not want to break our current model. There is still some huge value in what we have going on. It still may be important to have everything play under the same roof.
- We may need an html (plain web) version for my cart favorites. Currently, they only use Flash technology.
- When teaching sales & invoicing… Make sure and include discounts, returns, trades, and refunds. These are all very important.
- On the steps to success (user guide/outline) – Talk about settings and permissions per category. Also, group the help files under the different sub sections.
- Similar to the US Forest Service – Land of Many Uses – adilas is a land of many uses.
 
Click to view time photos.
AU 1175 Daily Tasks 4/26/2013   Met in Salida at Steve’s house. We had a multi hour brainstorming session with the adilas team. We listed a number of topics on a white board and then started discussing ideas and options. Great meeting. There are pages of notes (a couple pages back). I also wrote an email (after the fact) to help fill one of our team members that couldn’t make it, in on new developments and direction. Most of the meeting was dealing with business plan, marketing and adilas university.
 
Click to view time photos.
AU 1198 Daily Ideas 4/26/2013   -I love what my friend said, “step out of the door and let them come in!” He and I talked last night for hours about how he has been waiting for this time. One of the key things we talked about was the phrase “As Is” and grouping all of the to do list into the phrase “future developments”. Good stuff!
-We are playing with ideas about opening up adilas university using weekly GoToMeeting sessions. We are thinking about 2 hour sessions with a topic and then open questions and answer sessions. It really could be quite easy!
-Along with that, we could post the topics and times on the news and update page.
-We need some fun videos that help introduce and give virtual tours of different sections. Also small orientations about the subject and the concepts and theory for the subjects.
-On adilas university, we need a spot where reps, consultants, sales, and other adilas team members can post information and small bios and photos about themselves. This will help put names and faces together. It might also be cool if we allowed up to 10 (random number) photos and captions to help everybody know a little bit about each person.
-We need to use our team member to help coordinate “flow” and “communication” within the adilas team.
-Minimize the number of times people see the news and update page. Maybe just once a day.
-When extending or allowing things to connect to other systems. Maybe call it the “Application Flex Grid” or application flex grid tie-ins.
-Change by stats and volume
Meeting with Steve and other adilas team members… going over the future for adilas and where we are headed. Here are some rough notes:
- Goals – help people, release the bottlenecks, team of 5@5K/month
- Direction – North or forward
- Business Plan
- ACH (Wells Fargo)
- Protection (sharing)
- Servers
- API (Application Programming Interface)
- Stats – space – code for free then charge for storage and usage (charge by volume or power)
- Training
- Adilas University
- Marketing
- Help/Interns/Employees
- Open communication & flow (team member assigned)
- Custom code
- Future Development (all future products)
- As is = Released versions or version #’s
- Our sales & marketing plan is free – adilas engine
- Flow charts
- White label – free
- Projections
- Timeline – within a year
- Application Flex Grid Tie-ins
- You get what you give
- Internal adilas mall – future playground, cross corp, internal sales, franchises
- Target computer people
- Target “Denver” – Colorado based
- Scale the training model
- Sell & market what we have
- Market through the Internet
- Use technology
- Go after the already trained – inactive adilas users
- Rough Budget
o 50K Help
o 20K Marketing people & research
o 50K Marketing budget
o 50K Repay Loan
o 10K Reps/Consultants
o 10K A specific rep
o 10K Adilas University
- Future Development Ideas
o Mid may eCommerce
o Additional photo galleries
o Content server
o Normal servers
o Adilas eCommerce (start at $197 directly from the web)
o Second round of elements of time
o API & custom skins
 
Click to view time photos.
AU 1176 Daily Tasks 4/27/2013   -I took my sister into a Salida store that uses adilas. This is a kitchen needs shop that sells mugs, plates, forks, spoons, gadgets, etc. I had my sister watch as they rang up using adilas and barcodes. It was also fun to talk to an employee there. She was talking up a storm and loving adilas.
-After my sister and I left the shop, we thought that it would be fun to go onsite and film adilas users in their own environment or place of business. Film how they use the system, their experience, approach, etc. Basically, make it a commercial of sorts. This could be very fun.
 
Click to view time photos.
AU 1200 Daily Ideas 4/27/2013   -I took my sister into a Salida store that uses adilas. This is a kitchen needs shop that sells mugs, plates, forks, spoons, gadgets, etc. I had my sister watch as they rang up using adilas and barcodes. It was also fun to talk to an employee there. She was talking up a storm and loving adilas.
-After my sister and I left the shop, we thought that it would be fun to go onsite and film adilas users in their own environment or place of business. Film how they use the system, their experience, approach, etc. Basically, make it a commercial of sorts. This could be very fun.
 
Click to view time photos.
AU 1177 Daily Tasks 4/29/2013   • Reviewing footage from the Denver training class.
• New logo for a company.
• Notes from the adilas team meeting. Sent a big email with notes and explanations.
• Reviewing footage from the adilas training courses.
 
Click to view time photos.
AU 1178 Daily Tasks 4/30/2013   • On the phone with an associate and replying to emails.
• Setting up a digital capture system to start working with the first adilas training course. We have 16 video tapes from February of 2013.
• Recording notes from the Colorado trip. Going over meeting notes with my wife and reviewing footage from the first adilas class back in February of 2013.
• On the phone with someone from the LDS Church. I sent him an email with adilas information. I got his number from my brother.
• New logo for two companies.
• Making a small movie using Windows Movie Maker.
• Uploaded the movie to YouTube. It is a 20 minute introduction to adilas and who the key players are.
• Working on a second core concept video for adilas.
• Added a second concept video to YouTube.
• Updated pages and posted new links on the homepage.
• I also added the new videos to the news and updates page.
 
Click to view time photos.
AU 1201 Daily Ideas 4/30/2013   -On training, maybe spend more time on one or two subjects vs. trying to get everything covered. Remember to focus on people.
-Also, if someone is there at a class, help them actually do something or work on a project or sorts. Think the word “apply”. That is very important.