all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||||||||
|
|||||||||
|
|
|
Notes:
|
|
-Adilas flex zone timeline drawing (Sketch of flex zones or virtual waiting rooms, with checkpoints and permissions, and time going in either direction.) (See scan in photo gallery) -Life has to have some flex zones or small waiting rooms. -There may be things that are unfinished – that’s okay, they will stay in the flex zones until they are ready. When ready, they may be advanced to the next stage. -There will be time – just keep going. -Instead of just one timeline (like the graphic or drawing above), there are multiple time lines working together. Time, itself, has many one-to-many relationships. They all play into the bigger whole but are made up of tiny little individual pieces and parts, kind of interesting. -We have a client that is looking for EDI (Electronic Data Interchange) pieces and functions. Steve has done a little bit of research and we’ll only start heading in that direction if needed. EDI is basically a way for one or more computers to talk to each other. Notes from a phone call with Steve on 3/1/14. - Let our developers build their own clientele. Our reps already do this on their own. - Our current top three priorities are: o Package stuff, o Split Cart functions (interface), o API (application programming interface) & 3rd party plug-ins. - Custom documents are a good profit center for adilas. This could include: o Documents o EDI – Electronic Data Interchange o Outside Feeds o Internal Feeds o Loyalty Points o Customer Gift Cards o Labels o Barcodes o RFID o Reoccurring push/pull actions - Maybe think about bulking up or beefing up the custom pipes or custom documents area. - Use the barcode generator (if possible) for some of the custom pieces. If needs be, we could always create a new barcode generator or custom label app if we needed something more robust. - Packaging and subs of part numbers or subs of item numbers. - The deeper we get, the more elements of time appear to be connected to everything else in the system. - Packages and conversions are almost one in the same. One is limited or quantified and the other is open ended or unlimited. - Should we make a whole new item type??? A mix between a stock/unit and a general part? What about backward compatibility (people wanting to go backwards)??? - Steve kept using the phrase “occurrence of…” or “instance of…” when talking about tracking packages. Virtual usage. - The naming has to be dynamic… Just like in elements of time. - Batch, packages, reports - Maybe store dynamic parameters (actual JSON objects) inside of the subs for time called sub comments. These fields are big, they accept HTML, and they are already a sub of time. - Maybe use time for packaging and expiration dates as if it was manufacturing. Think both retail and manufacturing of packages, lots, batches, etc. - On part categories… what if we allowed categories to be stacked inside and/or on top of other categories. Allow it to go as deep as it needs to go. - If we let simple objects connect to each other and to themselves, how do you go back up the chain? I am talking about showing the relationships. Instead of simple nested part categories… what if it were people connected to other people (say like genealogy). The person exists as a single object, they could then be connected to other people or other objects to create a relationship. The relationship then helps to define how they interact and any dependencies or other independent states that exist. It basically starts forming the story as the objects and data move or interact over time. - Make the teaching graphics available, to all users, that we use when doing adilas demos and training sessions. Add a muffin tin, add the dream it up, and add a cup and plate model with an underlying platter or bigger tray. Think stacking objects. - Teach base level core concepts like operations and accounting. - We are going to need a sales and setup team inside of adilas. Help them sell what we have! - Our best sales people are involved in the setup process. - Create a small setup team using existing persons. - Do weekly demo meeting to help get awareness up. - On packaging… what about packages of packages or deep one-to-many relationships? - Packaging may need its own barcode. This could be something simple or it could be cryptic for a main time id, something in the middle, and then a sub of time. Just trying to get ideas. - On elements of time… We have the “anything” sub – pools and subs. We need to get that ready for use. - Packages may contain more than one item. Possible mixed items. - The mother is “time” – then anything that gets applied will be the sub. - Moving items from a “shelf” to a “package” or subset. Think about moving pieces into other pieces. Basically, it is all mini manufacturing or internal builds. - Show the usage over time. - Elements of time… this becomes the master. - “Any” scheduler – everything needs to be tied to elements of time. - Push out the developer’s notebook – stake our claim on some of these emerging ideas – do it in a fashion that helps build and share. Remember, “The rising tide raises all boats.” I think the real quote says “ships” but I like boats better. Ships seem so big. Anyway, help raise the tide! - Work smarter, not harder. - Allow all or “any” of the pieces inside of adilas to be plugged into time or into an element of time. - The different report types are: o Calendar o Time slot o Grouped o Details o Advanced (pick & choose) o Subs and stats o Export to Excel o Time Line Horizontal (new) o Time Line Vertical (new) o Other Formats (new & futuristic) - What if we used Cold Fusion to dump and display objects inline using a cf dump tag. This may have a place, especially in the API documentation and testing zone. - We would like to set up a number of adilas training centers. This could be a great business for us and/or other interested parties. - Prep for a demo meeting. - Use Bridgerland as our first adilas training center. It is a great fit and is already in use. - Pass out flyers for the free demo. Maybe pay a team member $10/hour to pass out flyers. - We are shooting for 50 new clients. - Do the weekly demos on Thursday night from 6-8pm. - Use BATC (Bridgerland) or the Business Resource Center for the software demos. - Maybe show a calendar on the main login page. Have drill-downs to different details, photos, links, and other content. - Have the same calendar show-up on the adilas training page. Start using elements of time. - Get adilas university up and live with help files, developer’s notebook, and training and videos. |