Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Blue
Created By: Shannon Scoffield
Created Date/Time: 8/13/2013 6:30 pm
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
 
Time Id: 1186
Template/Type: Daily Ideas
Title/Caption: Daily Ideas
Start Date: 4/11/2013
Main Status: Active

click to enlarge - photo by: Shannon Scoffield -
click to enlarge - photo by: Shannon Scoffield -
click to enlarge - photo by: Shannon Scoffield -
click to enlarge - photo by: Shannon Scoffield -
 
 


Notes:
-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.)