all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||
|
|||
|
|
|
Notes:
|
|
Notes from a phone call with Steve on 2/15/14: - On funding, we are looking for a loan. We are trying to steer away from investors and looking for a possible loan. Maybe offer 10% to 12% on interest. - We could also allow our clients (top paying or longest clients) to pre-pay with a discount applied. We may want to limit this to clients that have a year or more time with adilas. Maybe 10% for 6 months pre-payment. 20% for 1 year pre-payment. 25% for 2 years. 30% for 3 or more years. Kind of like a season pass for a ski resort. They (the ski resort) get more capital up front and the lifts (servers) are going to be running anyway. Notes on packaging or packages (sub of the parts section). - Maybe add a 3rd item type. Other two are serialized items (stock/units) and general items (parts). The 3rd item type might be a sub or baby of a momma (either stock/units or general items). - Keep the naming conventions as dynamic as possible. - Maybe change “parts” to “items” at the top most level. This is clear up at the top level or 12 main system player groups. - What if this 3rd item type was able to handle outside services, job costing, packages, subs of the main, etc.? That would be super cool. - Conversions could be part of this sub or 3rd item type. - There may already exist some ideas and notes on “mini units”. This is an older idea but may have some ideas for what we are trying to do. Mix between stock/units and parts. - Package control – helping, watching, and monitoring. - Stock/units mixing with packages or element of time to get RFID tag tracking, job costing, and subs of subs. - Lots of new 1-many relationships. - Round two of elements of time deals with payroll options, rentals, reservations, job costing, clear to the any person, place, or thing level. This could be to a dispatching level on elements of time. As a note, there are tons of notes on what we wanted for round two of elements of time – check out old notebooks and brainstorming pages. Look in early 2011 for details. - Track the “time” related to packaging. - The 3rd item type may be done by taking an existing item and creating a one-to-many relationship from it to a new group or package. -We are heading toward generic corp-wide settings. We could then bulk change these settings based on different industries. What is your industry? Can we help you setup some common features, settings, and interface options that are used by people in your industry? Help our users get the most out of the system by using settings and permissions. -Steve and I were working on building some new corp-wide settings… As we went through the process, we came up with a few key points to help us get started. They are: start with ideas and needs. Then do some planning. Then make new database changes. Go to the source of where things start. Build the settings, then actions and updates, and then cascade the new settings as needed. Finish up with sign-off and deployment of new features. |