all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||||||||
|
|||||||||
|
|
|
Notes:
|
|
-On sub locations and sub classifications (previously known as invoice classifications)… These classifications may need a tie to an actual location even if it is “all” or one (unassigned). Basically, I’m thinking about combining the two sections. A sub location could be a sub classification tied to a main location. Currently this section doesn’t exist. Anyway, maybe think about combining sub locations and sub classifications vs. an invoice classification deals with opening it up more to be able to play with any of the main system player groups. Such as expense/receipts, deposits, stock/units, PO’s, etc. -Check the multiplier on the build and hold recipes. There may be a multiplier problem. Maybe rework and check math. -On the server and data structure model. It could also be expanded to include: Groups, individuals, data, and time. Without indenting it might look like this: 1. Internet 2. Adilas Admin – Universe Level 3. Media/Content Server – optional 4. Domain or App Server – Data Server 5. Database – Cluster Level ---- Note: as of 12/13/13 The Cluster Level will be on the database level. It started on the media/content level, then the server level, and now the database level. ---- On 12/20/13 it changed again – Universe, Galaxies, Clusters, Solar systems. 6. Corporations – World Level 7. Locations – (prior page numbering) 8. Sub Locations – optional – (prior page numbering) 9. System Player Groups – (prior page numbering) 10. Departments – optional sub of users – (prior page numbering) **New numbering – Basically, below the world level, things really blow up and get into the details, relationships, etc. 6. Corporations – World Level 7. Locations a. Sub Locations – optional 8. System Player Groups a. 12 Main Player Groups i. Customers 1. Customer Types – user defined – dynamic list ii. Invoices 1. Invoice Types iii. Quotes – (Etc., etc., etc. – it just keeps going and going – deeper and deeper) – as another note… this is where sub classifications would come in to play, possibly for each main player group. iv. Parts – General Inventory Items v. Stock/Units – Serialized Inventory vi. Elements of Time – Calendaring & Scheduling vii. Employee/Users viii. Vendors ix. PO’s or Purchase Orders x. Expense/Receipts xi. Deposits xii. Balance Sheet Items – As a note, each one of these 12 main player groups could have tons of subs, types, and special functions ---- this gets pretty deep! 9. Individuals – Unlimited number with a huge variety. These are objects and are tied to the 12 main groups. 10. Data Level – these relate back to tables in the database or what bucket to store the date in. a. Main b. Line Items c. Payments d. System History e. Flex Grid Tie-Ins f. Special Subs & Relationships g. Photos & Scans h. Custom Documents i. Other Content 11. Dates & Time – Run all levels over “Time” a. Years b. Months c. Weeks d. Days e. Hours f. Minutes g. Seconds -We watched an awesome video on Facebook and how they track and store huge amounts of data. Very inspiring. Their goal is to be big and huge. They have huge data centers with tons of servers. Our goal is to be super small and nimble vs. huge and at a single giant datacenter. I want to be in datacenters all over the world. We could take up a small corner or a couple of bays on a server rack and be totally happy. Zero overhead. Spread out. Be all about tools, service, and customization options. We could potentially live anywhere - US, foreign, web, cloud, Intranets – behind company firewalls, and even on personal computers and devices. |