Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Blue
Created By: Shannon Scoffield
Created Date/Time: 11/19/2014 10:08 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
 
Time Id: 2894
Template/Type: Daily Ideas
Title/Caption: Daily Ideas
Start Date: 10/14/2014
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 -
click to enlarge - photo by: Shannon Scoffield -
click to enlarge - photo by: Shannon Scoffield -


Notes:
-On all real in-line extensions… on all dates and times.. include a used flag (yes/no value). If used, put a 1 (one). If not used, put a real date and use a 0 (zero) in the used flag field.
-We have a good and stable set of code and functions for main groups and system player groups. The new and developing need seems to be in the sub or subs of subs level. Everything seems to be headed in that direction… Sub permissions, sub settings, sub inventory, sub tracking, sub groups, sub categories, sub functions, sub locations, sub phases, sub payroll, sub accounting, etc. Whole new levels to explore and figure out.

Flat 2D objects vs. multi-dimensional 3D objects… (Please see sketches on scans in photo gallery)
- Flat file with rows and columns
- Three dimensional data objects built with properties of time, money, and space
- X=Time, Y=Money, Z=Space

Flat 2D models to compare operations and accounting along with 3D models to compare operations and accounting. The progression!
- Operations on top and accounting on the bottom. Perfectly in balance. Ideal in a perfect world.
- Operations on top and accounting on the bottom. Real world example, sometimes these things need to flex and then come back together. This happens in real life all the time.
- Same as above with multiple instances where things flex and then come back together. Real life mixed with time.
- Flexing model over time with dates and checkpoints at certain places. Dates and times now playing into the model.

- Flexing model over time with:
1. Operations on the top
2. Accounting on the bottom
3. Process over time – multi bubbles or pods
4. Checkpoints as things come back together (dots) – Dates & Times
5. Permissions (user permissions) to limit access to the process (vertical lines)

- Flexing 3D model that includes space. Depth, layers, stacking, wrapping, etc.
- Add space to get a 3D model of how operations and accounting could work together.
- 3D concepts – x=time, y=money, z=space

-Another huge piece of the puzzle deals with being able to both add and subtract elements. We need to be able to go in both directions. For example: We may need more dates, more checkpoints, and more permissions. Other times we may need to short cut, streamline, or dummy things down. It (the elements of time, money, and space) need to flex as needed.
-Steve and I talked a lot about attributes or pre-set pools (proposed subs of time). These could include rules, assignments, matrix or grids, sub players, options, sub locations, sub phases, etc. We kept switching between the word attributes and pools. The phrase attributes seemed to fit slightly better than pools just because you didn’t have to define it every time. This deals with verbage and terminology vs. the actual holding piece or data group.