all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||||||||
|
|||||||||
|
|
|
Notes:
|
|
-We had a request to store payroll settings per employee. Maybe what we need to do is show what relationships exist so that they may be manually updated. Currently each employee may be assigned to one or more departments. Instead of changing that – maybe just show the relationships and settings. Also maybe a multi-update feature for pay rates, or allow them to be updated from the setup employee page. Spread the love. -Brainstorming notes on making adilas a full-on business platform. Open the door to the data and how it plays, gets connected, is shown and is used over and over again. -I love the word “upstream” – what is the source? What feeds what? How does that affect things? Where is it easiest to control? -We keep getting great ideas but I and/or our existing pieces become the bottleneck. What if we re-built with platform in mind? -Small idea (different company arms). Diagram in notebook: Main adilas (in center box) connected to: hardware, library, marketing, personnel, web services, business(sm, md, lg, xl), stand-alone apps, web, mobile or mini, non-profit, custom look-feel (skins), software, education, eCommerce, commercial, shareware/freeware, government, trainings and setup, info/resources... Don’t get stuck here, think unlimited entry and exit points. -The goal is to create, define, provide, build, re-use, and create a culture that embraces change, thoughts, ideas, concepts and flow. -Allow people to create their own uses of the system. This means provide a core pre-built structure. However, if people only need 3 out of 20 options, let them put it together in a custom wrapper to meet their needs. -Think about a global library of functions, logic, data and mappings. -Create a buffet or smorgasbord of options. They (persons – our company – other company – teams – individuals) could pick and choose. -Allow different pieces (already defined or new pieces) to play in any 1-to-1 or 1-many(one-to-many) relationship. For example: we have vendors, elements of time and expense/receipts. However, they are not currently tied together. If I had a shipping and packing company it might be nice to know who (vendor) is coming in today, what do they need (invoice), and what are they bringing (PO’s and expense/receipts). Imagine being able to virtually morph or create dynamic relationships between the different players through a standard “re-skin-able” interface. -All the players already exist (or may be created) and then you put them in to play by defining rules, parameters, scopes and functions. You get to name them, use them, whatever. -Our current system is already built with data components (ColdFusion CFC’s) and logic pages (searches and reports). What if we allowed others (or our own little sister company) to get at any of those pieces. Once access is granted, the sky is the limit on what pieces could play or piggy back on one another. Get as many or as few as are needed. -I see it as the main “adilas” is the pre-built or canned version. We keep adding permissions and settings but keep a basic and consistent flow. If a new wrapper is needed (custom look, feel, function, relationship, process, steps, etc.), allow that to happen without causing problems upstream and/or downstream (cause and effect relationships). -This may not fit here but what if all data was returned as a standard like xml or Java (or whatever else new comes out) and then consumed by whatever type of application that calls it. The end goal is call, crunch, serve, apply, do it again. -On a different note – what if every function or method call had a user id, corp id, app id. Every function could also pass its data to a converter function. The converter function would get, check, interpret and then send the results back. The original method call would return the native format by default. However, if a different format was needed, it could translate the output to that format. -The incoming values would also need to be standardized – so that flow back and forth would be possible. -A full re-write from the ground up may be required. That would be a couple steps backward to make huge and giant leaps forward. It wouldn’t be the first time. (Meaning a full re-write) -Security, mobility and built with growth in mind are huge keys. -Currently built in Adobe ColdFusion and MySQL databases. It could literally be built in ColdFusion, Java, PHP, ASP, net, Ruby, Visual Basic, Access, Flash, ActionScript, Java Script, you name it. I think the more the merrier… Oracle, Microsoft, Apple, Unix, Web-based, App-based, software, firmware, hardware, freeware, shareware, etc. -Expose the code, the logic, the theory, the formats and the experience to the world. -As long as things are being expanded, what about languages? Computers? Operating systems? Countries? Etc…. -There is enough to go around (info, resources, ideas, etc.)! Share with the people. On a similar note, just read a cool scripture today during my study, it was 2 Kings 4:42-44 (pg. 513 in the Bible)... related topic. -Another quick idea – how cool would it be to over lay a calendar view on everything that happens in the system. Elements of time have groups, details, calendar and time slot view – think everything out of those four levels. -Random other note: If we were to expose this stuff to the world – we should video tape the presentation and then send that around to different colleges around the world. I’m thinking that the college level is the entry point for new and creative thinkers and future business leaders. It may branch out from there, but that is where I’d like to focus first. Post the videos on adilas university for the world to see. -Plan it out, break it up into pieces and even provide code samples. |