all data is live and searchable
[reset this page] .
[historical web outline - entries by month] .
[adilas community funded projects] .
[contact adilas.biz support - email form] .
[help]
|
Adilas.biz Developer's Notebook Report - 2/1/2011 to 2/28/2011 - (41)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 370 |
|
Daily Tasks | 2/1/2011 |
• Added new logos and colors for two companies. • Worked adilas sales commissions. Wrote out six checks to reps and people in the field. • Tons of brainstorming and reviewing notes on the “any” scheduler. Thinking of calling it the “any” scheduler or just “element of time” and then letting the users control what they want to call it. I spent a lot of time reading over old entries and pulling out info from my notebooks. • Replied to an email about tech specs for merchant processing and barcode readers. |
|
|
AU 394 |
|
Daily Ideas | 2/1/2011 |
-On the interactive platform map – have an html version of every flash option. If users are using a non-flash device, they can still get to the functionality of the flash interface. -On the “any” scheduler – I need some sort of work, time or job sheets to help tie activities to invoices and payees (employee/users) to jobs. This would be a separate field and sub report on the calculate payroll page. Think about Monarch paying their ski school staff for work, teaching, head counts, etc. I want it to tie to payroll. -The calculate payroll page needs options to save as PDF for all sub reports. Some of these reports are only available from this page. -Maybe have a recipe/build interface for elements of time and scheduling. -Grouped reports for all main application types. Group by customer, vendor/payee, parts, makes, etc. -Grouped reports over time – how many per day, week, month, year, etc. Stack items and application types. Almost a history report over time. |
|
|
AU 2181 |
|
Brainstorming - Ideas & Concepts for the adilas.biz "Any" Scheduler (Elements of Time) | 2/1/2011 |
1 February 2011 Ideas & Concepts for the adilas.biz “any” scheduler - This section began 2/1/11 & concluded 3/4/11 1. Tie to payroll. Add options for commission gross sales profit. 2. Remember that one of the original ideas in adilas was a series of containers or “Pringle's cans”. Stuff things where they need to go and move things around as needed. 3. The heart is – “Objects and data over time.” 4. We are trying to record and document the “story”. Tell the story: who, what, when, where, how much, how long, why, etc. 5. Map to check points and status as they happen (past, present, and future). 6. Be your own style! And let the users be their own style. 7. Scheduler for personal. 8. Scheduler for customer time cards – tie to invoices and show payment status. 9. Go onsite and ask about schedulers. • Dental, doctor/medical, rentals, car maintenance, manufacturing, classes and courses, golf tee times, hotel/motel, guide services, trips, cleaning companies, services like heating and plumbing, buy here – pay here, CPA/lawyer’s appointments, customer/client billing of time, reservations, salons/beauty, therapy, lessons, events, competitions, mobile persons, vacation time shares, membership, licenses, pre-paid services, etc. 10. What do you call it? 11. How many different pieces does it have? 12. How can you keep it flexible yet simple? 13. I want it to be a time-based scheduler on a flex grid tie-in level. This means all main players can play with built-in functionality. 14. Time… why not call it “Time” or “Element of time” and then let users define if they want customer time cards, rentals, to do lists, mini blogs, appointments, etc. 15. Include anything that could have a timeline on it. 16. Other thing to think about – rentals and buying down units, share and coordinating schedules, unassigned task or job pools, allow others to assign or move to their pile or task-list. 17. Add visible and basic/admin status. See the flex grid tie-ins for more info. This could also be a privacy or mark as private settings. Who else gets to see it? 18. When creating time based element – what about having a point and click interface with show/hide options during the creation process? Options, actions, types, etc. 19. What happens if I pre-define certain types of time elements and allow users to copy/paste and tweak the pre-sets? 20. Maybe I could add options for corp-wide settings and individual settings. 21. This may not be related but what about project management, goals, ideas, tick lists, wish lists, cataloging (events, agendas, video clips, etc.), or documenting ideas and plans. 22. Maybe review the MDI idea center. 23. Blogs, forums, threads, sign offs, comments, sharing and collaboration. 24. Show on web – build a pre-built page to show. This could be a blog, mini blog, update page, or a sales or specials page. 25. Along with show/hide on the web – maybe a show until date. 26. What about a newsletter? Think about an art company’s website I worked with. They also have meetings, shows, and special events. 27. What about an HTML editor of sorts – maybe photos, links, line breaks, tables, div tags (css), lists, horizontal rules, etc. This may have to come later on. 28. Keep it super simple – select time and objects and then click go. 29. Allow the time line to be printed in different formats and outputs. 30. Think about using spreadsheets as a layout form for the scheduling. 31. Some of the users will be doing scheduling either on a phone of mobile device or viewing a schedule from a phone or mobile device. 32. Think about water in a ditch – it always flows in the path of least resistance. Help to channel people and their use of the system so that if flows and is very simple. 33. Allow time elements to be tied together. This could be a single event, a series, a brother/sister or parent/child relationship. Help tell the story! Cause and effect, planned and un-planned, hay and sad, etc. 34. I am not limited to a Flash only interface. I can mix whatever technologies I need to and piggy back on existing technologies. I could use ColdFusion, database stuff, HTML, tables, div tags, css, Java Script, graphics, charts, MS Excel spreadsheets, PDF, etc. 35. Drag and drop is wanted but not required. This may come later as an upgrade or add on. 36. Design it first on paper, create static screen shots, then build the dynamic interface and add the needed interactivity. 37. Hide/show additional details when printing and viewing. This could be page settings, Java Script pop-ups, spreadsheet comments, or Flash status bar rollovers. 38. Random note about Flash – I may need to upgrade to the latest version. I could also stay with my current version for this first round. 39. We need a light package that allows for invoicing, quoting, using a recipe/build for presets, my cart favorites, groups, advanced grids, etc. We need to be able to attach deposits and invoice payments. These items need to flow right in to the normal back end adilas functions. We may need some new flags to help track states and status. I want it to go clear to the balance sheet (only if needed). 40. On the customer time clocks – allow items to be shown as invoiced/not invoiced or no charge. Allow for time sheets to show/hide on invoice. They could be individual and/or summed up. This might tie in to the visibility settings. 41. I want to allow it (time and elements) to be fully connected but they don’t interfere with normal traffic. Maybe another full application on top of the main application. Time goes in both “known” directions. Think 3rd dimension. Multiple pieces may share the same time space but each may have a different life or life cycle. 42. Time needs to be the one (1) and whatever plays in to that space is the many. 43. Allow multiple bookings in a single slot of time. Also don’t force ends to match-up perfectly. Let it flow like water… fully user-maintained… If needed show some extra flags for potential problems, double, triple, quadruple, booking, overlaps, gaps, disconnects, and waiting lists. 44. Allow the users to put and place what they want into the time-based model. 45. Allow users to go back in time (if needed). Basically, time as it is forecasted (future-somewhat unknown), time as it happens (user may be too busy to change something), and time in the past (what did happen or what was perceived). 46. The key to time is let it flow and date/time stamp and the actual history behind the scenes. This will become the audit trail if needed. 47. Like a virtual to do list – If an item gets done, let it stay. If not, allow it to be pushed forward. 48. If I’m using a quote to hold items or reservations – I may end up with multiple quotes (or invoices). It may be cool if you could stack, chain, or combine quotes and invoices. 49. It might be nice if the scheduler had its own photo gallery. It might also be nice if it had access to the reflexive photo galleries (what is it tied to). The main photo galleries are tied to the main objects. The photo gallery for the scheduler will be more of a one-time deal. 50. What if you could search, filter, and print out different Excel spreadsheets dynamically. 51. Think of the Flash timeline – This is a 2-D, layered timeline with actions, labels, spans, fills, blanks, and color-coded items. 52. What if we took that one step further and added a 3-D or cubic level to the time line. Think about the bricks in a building – Each brick represents a block of time; however, as you look closer at the individual bricks you can start seeing the details that make it up. A brick wall can be the entire wall, just a row, just a column, just a small block of bricks (cluster), or clear down to the details of each and every brick. 53. Most timelines are flat and straight. This is random, but what about a cycle, round, cubic, or infinity timeline model. Just a thought. 54. The scheduler might be a series of 1-many relationships. Each time element could have any number of subs. This could be good for details, follow-up, GPS stuff, tie-ins to other pieces, etc. It may need to go to a 3-deep level. Or more… (See #103 for ideas on subs and snap-ons.) 55. Have each corp start over with an id of one (1) and then increment from there. 56. My dad had the idea of the “any” scheduler – (12/4/10) • All dynamic: - Anything – different application types, general, generic, and build your own - Any place – locations and sub locations (maybe even open or custom) - Any # of events - Any length (time) - Any # of participants - Any price or cost 57. The whole thing is a “system”. That becomes a key word. A full system allows you to do things that others can’t do. 58. I want multiple entry points. Use the quick search, use the time element homepage, and be able to add from any unit (just like the flex grid). 59. I think we need to add a new main application type to the flex grid tie-ins. It will be “Element of Time”. Maybe a future one might also be “Standalone Declaration”. This may come later. Maybe even use quote as a future option. 60. Why do you do it? Because it needs to be done! Ask the question – what would I do? This helps developer the why – the why takes time to figure out and develop. 61. Function vs. Fashion – this is an attitude. There is always a choice. Once it works – you can make it look pretty. 62. Add a one to many from locations to sub locations. This could be rooms, offices, conference rooms, cabins, king beds, queen beds, party room, mini mall, warehouse, etc. (Storage units) 63. Allow a single customer to sign-up for multiple items, packages, classes, and time frames. This could eve cross locations. 64. Allow customer to split and share tickets. This could be as simple as multi payments on the same ticket or actually splitting a ticket. Maybe a restore to cart and then some edits. The trick here is being able to keep things tied together, fast and easy, and making sure that the original gets used, cleaned-up, or voided out. 65. Potential problem – Currently invoice and quotes are location specific. We may need to look at this and allow corps to mix and match locations and sub locations on invoices and quotes. 66. Be able to register for classes, courses, trips, events, etc. 67. Employee time scheduling and shift planning. 68. Be able to handle dispatching and service calls. I also have a need to be able to tie-in GPS as part of this. This may be a sub of the time elements. 69. “Apply” what you learn! Do this along the way. Don’t wait to the end. The more you apply it – the more it becomes a part of you. 70. There may be some cross-over to the multi-media player and training application. 71. Recruit help! It is okay not to have all of the answers. The more people that are willing to help, the better it is in the end! 72. I want and need some sort of work, time, or job sheets to help tie activities to invoices and payees (employee/users) to jobs. This needs to tie back to payroll and be available as a dynamically fed option. It would also need its own report from the calculate payroll page. Think about the ski mountain I worked for and how they pay their ski school staff. It could be hourly, teaching time, head counts, referral rates, etc. 73. Contact companies already using adilas to see what they would like in a scheduler application. 74. In order to allow invoices with multiple locations, maybe we will need to switch the (P&L) revenue and COGS sections to invoice line items instead of the main invoice. 75. On quotes – we may need an option that allows for a single quote to be restored to cart or split into different invoices more than once. Currently, once an invoice is created, it locks the quote from being used. This may need to be opened up a bit. Maybe make it a setting on the main quote. 76. We already have the flex grid in place – why don’t we allow options to automatically chain and link things together. Think of this as putting water fountains and sinks around your house or building. You shouldn’t have to go all the way outside to get the water source. 77. What about events and classes. This might be a mix of dates and participants. Depending on how tight the scheduling is, I could see an alternating schedule and/or multiple classes/labs being scheduled back to back. Think of a class at Bridgerland or room at the University. Either way you might need multiple start and end times. How do you keep all of the participants tied to each date and time? Roll call. 78. Some events and classes will be in rented or non-permanent locations. We might want a choice to select from a list of locations and sub locations or enter a temporary or custom location. 79. Spent some time in Staples Office Supply Store in the planner and appointment book section. Think very simple like a day planner, to do list, desk calendar, etc. 80. Allow preset blocks – seconds, minute, ¼ hours (15 minutes), ½ hour, and hours. The user could then see and choose the level without typing anything. It would also be cool to let them see start and stop values. For example: My dad always begins at 6:00 am and ends at 8:00 pm (whatever). If something custom is needed it would also show up. Maybe even have a button for 24 hours (if needed). 81. Time – slots, as many or as much as needed. Items, rooms, persons – as many or as much as needed. 82. We many want the users to choose between simple vs. complex time elements. They also need to be able to show results on different levels. (See #103 for info on subs and snap-ons.) 83. Online reservations and registration will lead right in to online eCommerce. We need to plan for that. Along with that – we also need a way for customers to pay their bills and see history (activity) and outstanding values. Self-service. 84. If people are in a hurry – they may want to schedule an appointment without getting all of the customer info. Allow for a generic party or customer name. This can be replaced later on or just left as is. 85. Adilas already has 2 or 3 storage units. Maybe call and talk with them about wishes. 86. I use sticky-notes or post-it notes all the time. I wonder if adilas could have a small mini blog or quick notes section. 87. Remember this is just a tool. The variable is still people and having them follow through. As an idea – if you tie it to payroll – that helps motivate people and users to play. 88. Be able to choose colors. This is not required. Maybe have a number of pre-sets and then be able to add custom colors if needed. 89. Let the users define preset increments of time – a couple days, 1 week, 2 weeks, a month, etc. Or maybe have a jump field – jump ahead, jump back. Be able to easily come back to the current day. Use a calendar interface to help show layouts and dates. 90. Be able to show other appointments per customer or customer family member by clicking a link or a button to show related or other appointments both in the past and in the future. 91. If a company wants to do rentals or dispatching – allow for pools of items, locations, and users. The system could help you pull from the pools by drag-and-drop or by clicking a check box. Another idea is to have the system remember the main time element as it searches for other pieces to tie to it. (Session scope) Be able to clear the memory if needed. 92. Make this as small and easy as possible – yet as flexible, bit, and complicated as needed. This will be a balancing act. 93. Be able to mark things in/out of play. This could be workers on a crew, service trucks, equipment that is in the shop or being fixed – help coordinate what is going on. 94. Templates of time, start and end time ranges, days of the week that are in play, etc. Be able to set known times and standard occurrences – weekly, meetings, training, lunch breaks, etc. 95. It may be line managers or crew chiefs that are setting up schedules for their employees. Each crew or line may need the flexibility to switch crews, locations, shifts, etc. 96. Be able to schedule a webinar. 97. Allow a buddy system on tasks, ideas, comments, and assignments. 98. Time also deals with the future like goals and forecasting. It could also be used to determine reality vs. planned. I could see a manager setting a goal for each day – then a crew manager entering an actual for each day. That would allow the person(s) to monitor progress and actual output. 99. If you were in manufacturing – you could even schedule production runs, needs, and demands. What about maintenance schedules. 100. It would be pretty cool if the system could help send you reminders . This could be email, screen pop-ups, text messages, etc. As a side note – some scheduling applications use MS Outlook as the platform and then use a MS exchange server as part of the application. Maybe a notification@adilas.biz or reminder@adilas.biz email form or address. 101. Estimates, quotes and job costing. The goal here is to gather up the details and show how they relate to income and costs. This could include supplies, parts, labor, time, overhead, rentals, sub-contractors, project management, fees, etc. It might be nice to have a report that shows what is revenue and what is a cost or expense. The goal is the bottom line or profit margin. Many times, the element of time plays in to these types of jobs. 102. A couple of things to think about – sign off requirements, sign off by who, changing status and how long in each section (aging of changes), assignment changes, aging in the queue and/or running time between phases or status. 103. What I’m seeing develop is a simple time object that can have all sorts of subs or pieces stacked on. Kind of like Legos. The main would hold and carry all of the subs. Each sub section has the functionality built in to it, not the main time element. This allows for known actions to be “snapped on” and they already know how, where, when, and how much to play. Maybe a “time snap-on” or “element snap-on”. Build the functionality in to the subs and options. Maybe just call it and “add-on” or an “add-on component”. 104. Once we go clear to eCommerce – we will need to know what to do (instructions), what to show, and how to show availability and bookings. 105. Each element of time may be tied to a master recipe or template. This will show options, show/hide “snap-ons”, and set requirements. 106. Be able to schedule payments and due dates. This is money coming and going. Think of a bank collecting on a loan or a buy here pay here checking to see if their buyer is on time. This could also be for monies going out. 107. Almost every element or piece inside of adilas is related to time. Is there a way to bring things together without making the user duplicate their efforts? Basically, we have tons of stuff that is already getting assigned to an element of time. I would love for that stuff to show-up and be counted as well. Adilas – All Data Is Live And Searchable. 108. Reoccurring invoices (and expense/receipts and balance sheet items – not done yet) need to show up as an element of time. 109. I’m sitting here thinking about how every piece of the puzzle is tied to an element of time. I’m also thinking about how I could have missed this “Big” of a component of the entire picture. We have been running things for years and only now is it clicking and making more sense. I’m grateful that I’ve had time to soak some of this in. 110. There are six pages of notes in my mini notebook dated back in 8/27/08 under the topic of reoccurring invoices. Here are some highlights and/or ideas: - Inter-corp options, master/sub relationship, be able to turn on/off the master, back tie to units to help buy them down (physically and/or depreciation adjustments), normal operating hours for each unit, only show those hours unless the full 24 hour link is clicked, be able to search for available dates and times, be able to cancel and back things out. - Need in/out stamps for check in/out, booked vs. actual usage, special notes and/or instructions per booking. Think general to specific, average time slot per unit. - What about capacity, # of guests (customers), optimal #, min #, max #. - Productivity reports (booked, used, optional), assignments (requests), mass entry (recipes), different reports that deal with dates, time ranges, capacity ranges, available, booked, etc. - Rate tables for seasonal use, waiting list feature, cleaning status on each unit, package deals, late fees, cleaning fees, other fees. 111. We want to add a sales and promotion section to adilas. Maybe customer reword programs, promotion codes, sales, and seasonal pricing can play in to time. This deals with loyalty programs, points, rations, and marketing campaigns. 112. Marketing and promotion is a huge part of business. Help them start to manage that as well. 113. For drag and drop or selection pools – what if we actually create a second or sub time element for items that are not available. Basically, one pool for active and one pool for inactive or out of play. This may be able to be done by reverse association but I wanted to add it as an option. 114. When going to drag and drop. Use the adilas multi-media player to show and display elements. Include interactions between the left sub and right main panel. 115. At some point we wanted to add specific medical records. The elements of time might be a perfect spot. This would be as a sub or add-on component. 116. What about someone that goes to a resort. Everything goes on a tab and then could be pulled together. It might work cool if you could stack or combine invoices. Another cool thing might be to limit line items by date range and then print or show to your client. 117. Not everything that gets recorded needs to be shown or made printable. What about practice, draft, or concept notes. 118. We need an option to add up to five levels deep for an outline. This outline needs to be able to form in html and automatically in the Flash player (sub nav panel). Be able to edit on a single and/or bulk level. 119. On the outline – maybe use a table with 10 columns. Use two columns for each level. Column 1 (one) would be the Number and/or bullet point. Column 2 (two) would have the title, data, etc. 120. We need to be able to tie assets to outlines and/or subs. This is full content management. Be able to upload and store assets and content for users. We many want this on a different content server. That way it doesn’t impact the main adilas site or traffic. 121. Another function of time is a progress report. This could be added on to a task, to do list, document, idea, project, job costing, students, customer, etc. 122. What I’m seeing is eventually all of this data and content will need to be able to fly around via web services. We want it to get to the level of… “Your data, you cache and retrieve it, we secure it.” Make a super open interface… This could even allow outside developers to tie in to adilas functionality to create a hybrid super solution. 123. “Sphere” – once you are in the data sphere you can virtually go anywhere at any time. Other words or names are ball, global, bubble, orb, orbit, and realm. This concept could make a cool visual for how to get around inside of adilas. The outside layers could continue to expand as needed. 124. Training may fit best as an element of time similar to a document, outline, or idea. The media assets and contents could then be tied to sub elements. 125. Maybe have a show/hide status for items still in edit mode. It might also be cool if you could lock things down at some point and only allow growth or actions to take place on certain pieces. 126. What if we created system-maintained time elements and they became the watchers. Return and report! I’m not saying everything, but what if we wrapped all existing objects and data inside of adilas and allowed them to play or be counted in their own time element. Maybe one element per day with unlimited financial subs. 127. We need to stitch, sew, chain, group and link things together. This could be physical, virtual, or based on a relationship model. The entire system is a series of 1 to many relationships. 128. Originally I was thinking that time had two parts type and function. What I’m seeing is that the type just tells or dictates the functions needed. You can create type by adding function(s). 129. Matter – cannot be created or destroyed – but it may be combined, altered, formed, molded, compressed, etc. Fine matter, course matter, liquid, solid, gas, vapor, plasma, pure, contaminated, etc. Cut it, stack it, bend it, break it, etc. 130. Time – cannot be created or destroyed – this is a give (as far as we know) – what we do with it depends of each person. It could be simple, complex, self, others, persons, places, things, reoccurring, standard, variable, by choice, by dictation, by consequence, by others, etc. 131. Question about the system –maintained time elements – will that blow-up the elements of time table. Maybe we could have a special system-maintained section that mimics the elements of time without adding tons of system-maintained items (non-editable and non-searchable (ish)). In some ways, it might be nice to leave time as user-defined and put the daily watchers in a different table. 132. What if the type of time is the template with all of the defaults and settings assigned. 133. Most email programs have a calendar and appointment application. They may also have a to do list or sticky note section. Some people have apps on their phone. Where adilas comes in is connecting other pieces, built-in functionality, and already in the business platform environment. We win on the scalability and tie-ins to business functions. 134. We may need a special page that helps people know about their options – training eventually, but before that – some sample and guidance… show options. 135. Allow for defaults, presets, and custom values on all entries. This includes date and time selection – auto or custom date/time stamps. 136. Create a master list of functions of time. Duplicate this list and allow users and corporations to modify or create an alias name of the functions. What they do will still be the same but allow for custom naming. 137. Categories are the same way – create defaults and allow them to change the names and values as needed. 138. Categories are tied to functions of time and functions of time are tied to templates or types of time. 139. Certain settings, like back tie to units (or anything else – persons, places, or things) may need settings and options on the individual items that could then play forward. Even though we may want a back tie – It may need to come from the items themself and only play when needed. Another option is to think more globally and create a pool that knows what to do – then when the pool is update, the items already know how to play instead of being on a one-by-one basis. This could even work for sales and promotions. 140. Along the lines above – we may need to add a reverse look-up from the items to the pools so that they know what to do. 141. On the templates (types of time) – allow for the users to either preset hardcoded values or defaults or set the settings to dynamically look-up values like current user, current location, current date, current time, etc. Help wherever possible. 142. On reminders and notifications – push the valves in front of the user on the time homepage and the main homepage. There will also be options to help notify via email or text message. 143. When booking things for a date range – maybe add a transparent sub date/time option to hold each date to help with booking and availability. 144. On categories – instead of just one, what if they could pick and choose – like check boxes or something, maybe tie colors to categories. 145. When showing people how the elements of time work – show them a very basic drawing of the key pieces. (Templates have functions and functions have categories). 146. “A fox that chases two rabbits catches neither.” Focus and get the job done! Then move on. 147. When looking at a single item – show the bookings for three months. This may help to get an idea of usage and availability. 148. Sometimes the prep is more important than the jump. 149. On the templates – It might be nice to add an option to preset sub default titles. Either separate with commas or add a one-to-many relationship. Look at the flex grid titles for ideas. Options may include leave blank, a set value, or a list of values to use. 150. I may need to “dummy” things way down. This is like going hunting with an army, planes, tanks, and ships – when all that is needed is a small gun and some bullets. I know that it is a balancing act, but less might be more. 151. Currently we have a template that controls the elements of time. What if we had some settings that controlled the templates? 152. I can see a market for a scaled down version of adilas – say an adilas express or something like that. - Maybe a home version, a business starter version, an entrepreneur version, a small business, and a medium or large business, maybe an enterprise level. Okay, just took it too far again. 153. In conference on (4/3/11) I heard a talk that was talking about basic needs. The question was posed- will this buy me any bread? Cover the basic needs before we go tweaking to the “nth“ level. Keep it simple! 154. We may need to rate a table per user or per tech. This would automatically tie in to the rate or general amount according to who was assigned and the total time. From Post-it notes: - Group Meetings o Use technology to get the biggest impact - Group Training Sessions - Group Invites/Seminars - Newspaper ads - Flyers - Adilas theory demos - Webinars - Video capture, Dimdim, simple drawings, and power-point slide shows - Use Steve’s house until we grow out of it On customer site: - Easy contact info: o Email form o Phone #’s - Video demo o Overview o Specific tasks or concepts - Maybe a tutorial link or help files - What about showing general pricing and allow credit card payments and sign up - Adilas express - Adilas non-profit - Maybe allow the users to select # or users, # of locations, # of invoices or annual gross sales, send email requesting a quote. |
|
|
AU 371 |
|
Daily Tasks | 2/2/2011 |
• Brainstorming and recording notes for the “any” scheduler application. • Spent some time on the phone talking to a customer going over bank stuff. • Added a new logo and colors for a company. Posted files online. • Worked on the interactive platform map. Still a graphic but getting much closer and tighter. • Posted the image online in the history item for adilas. • Sent Steve an email. • On the phone with Steve going over the interactive platform map. |
|
|
AU 372 |
|
Daily Tasks | 2/3/2011 |
• On the phone with Steve going over the ideas and potential problems with the scheduler. Lots of options and tons of challenges ahead. • Added logo and colors for a company. • Made some business cards for myself. • Reviewing notes and making questions to ask users. • Went around going onsite to talk to businesses about how they deal with and track time. Went to 10 different places and asked questions and go some great ideas. 30 miles. |
|
|
AU 395 |
|
Daily Ideas | 2/3/2011 |
Notes from local businesses: • Physical therapy company – no current solution, would love something that was simple and cost effective. • Dental company – using Dentricts – quite happy but willing to talk. • Manufacturing company – talked with receptionist and got number – need to call. Left card and questions. • Manufacturing company – briefly spoke with receptionist. Contact was out of office, go back on Monday. • Service and dispatch company – contact gave me a quick tour of their software – likes and dislikes. • Cleaning and restoration company – received info for the need to call and ask for a certain contact. Went back and visited with him, talked lots of job costing. • Hair salon – they just use an appointment book. • Chain retail store – looked at day planners, calendars, desk planners, erasable planners and daily schedulers. -Have reoccurring invoices, expense/receipts and balance sheet items show up as part of the roll call and history assigned to time. Have them show up for the history homepage report. -There is some good balance sheet item information in my small mini notebook. It may be good to go back and review it. -Push vs. pull technology. |
|
|
AU 373 |
|
Daily Tasks | 2/4/2011 |
• Recording notes and information from my field trip yesterday. • On the phone with a customer going over payroll step-by-step for 4 employees. • Spent some time playing with the zoom digital recorder. Playing with settings channels and recording small practice clips. This will be used to help do the voice over and to train folks on adilas. • On the phone with Steve going over customer sales and promotions and customer loyalty programs. We talked quite a bit about the scheduler application, good stuff. • Writing an email to a contact about sales, promotions and customer loyalty programs. |
|
|
AU 374 |
|
Daily Tasks | 2/5/2011 |
• Brainstorming on the “any” scheduler application. • Scanning and documenting notes thus far. • Sent an email update to Steve and others and posted notes online in the history photo gallery. • Working on the database layout for the element of time. • Spent some time reviewing the MDI Idea Center application. |
|
|
AU 2182 |
|
Brainstorming Types of Time - Elements of Time | 2/5/2011 |
Types of Time - (any of these things could have the word “my” appended to it) - (my) to do list, tasks, assignments - (my) mini blog, sticky notes, or my quick notes - (my) appointments, calendar, schedule (simple), day planner, specials, sales, planning - Simple – above. Complex – below. - (my) time sheet, work sheet, payroll log (ties to payroll and maybe invoices, po’s, and expenses, may be tied to customers - (my) customer time clock, work order, customer time sheet (tied to customers and/or invoices) - (My) ideas, wants and needs, discussions, forums, sharing, collaboration, threads, blogs (one or more people, sign-offs, comments, building…) - Seasonal, peak, non-peak, holiday, specials, promotion (tied to look-up with fee schedules or price to date ratios) - (my) updates, newsletters, projects, documents, meetings, agendas, shows, special events (main with sub sections) - Rentals, reservations, dispatching, advanced scheduling, service calls - Rewards programs, sales and promotion, loyalty programs, points, marketing - Events, classes, roll call, webinars, events, registration, trips, courses - Estimates, quotes, job costing - Manufacturing, production, forecast models, goals - Employee, technicians, doctors, teachers, guides, crews, managers, one or many (scheduling people – simple to detailed) - Reoccurring events, templates, or set schedules - Payments coming in or going out - Waiting lists - Tick lists, project management, cataloging - Queues, pools, job pools, unassigned, pick list - Maybe subsets of persons, places, things, combinations, or custom Categories - Rentals & reservations - Lists & tasks - Notes & documentation - Schedules & appointments - Time Logs - Collaboration & sharing - Documents & projects - Events & meetings - Dispatching - Persons o Employee/user o Customer o Vendor/payee o Salesperson - Classes & courses - Estimates & quotes - Registration - Manufacturing & production - Goals & forecasts Rough overview of the MDI Idea Center: - Add an item (document), choose a client from list, select a project (dynamic according to client), choose a document type (see below), title, notes, budgeted hours, priority, sign-off required, sign-off by who, hide/show document (still in edit mode). - Able to search any projects, any clients, etc. Quick and advanced search options. - Only the correct person could do the sign-off. It would then show up for roll call. Very simple: a check box and a notes field. - Anybody could add a comment to any document. All of the person (user) date and time stamps happen behind the scenes. Very simple: a notes field. - Application had an auto response (send an email to Brandon) built-in. It would let me know if an item was added, a comment, and/or a sign-off happened, pretty cool. - It also had an email form built in. - The notes and comments allowed for html to help in the presentation. Any outside files had to be uploaded separately through FTP. - It also had options to finish the document. This included finish notes, actual hours, priority, and lock-down options. - There was a built-in 5-level deep outline option using div tags. - Document types (drop-down list): ideas, add-ons, progress reports, change requests, bags, phone calls, meetings and verbal, email documentation, other, proposals, contracts, project scope and overview, project schedules, “workflow, roles, and responsibilities”, phases and milestones, creative document, technical document, requirements and specifications, other main documents. |
|
|
AU 375 |
|
Daily Tasks | 2/7/2011 |
• On the phone with Steve going over things. • Helped to some quick tech support for clients. • Added an id# search option for parts, customer and vendor/payees. • Worked on the elements of time. Breaking things down into types and requirements. Came up with idea to have a basic time element and then use lego-type “snap-on” pieces for additional functionality. • Created a standalone quick search page and a standalone system basics page. • Added a new logo for a company – replaced their other one. • Posted files online for the id# quick search. |
|
|
AU 2183 |
|
Brainstorming Elements of Time | 2/7/2011 |
Possible requirements for different time elements: Needs: - Name or title - Start date - Start time - End date - End time - Total time (in seconds) duration - General notes - Status/state (general) - Status subs (colors) - Relationship type - Location o Sub locations o Custom/temporary locations - General amount - Visible status (shoe/transparent) - Basic/admin status - Privacy status - Category - Sub category - GPS (subs) - Payroll (subs) - Sign off - Notification and reminders - Html - History, photos, comments (subs) - Multi-steps (commit to memory) - Show/hide on web and show until date - Rounded time - Rates - Assignment changes (subs) buddies or buddy system - Invoice status (subs) (invoiced, not invoiced, no charge) - Income and costs (subs) or part of other subs determine profit margins - Planned vs. reality, output or goal watching - Sub pools (subs) all different types - Reoccurring, template master, known set schedules (blocks of time) subs applied settings or template - Pool items in/out of play for specific time elements - Flex fields, names, and types - Tie-ins or flex grid tie-ins (it doesn’t have to be flex grid) subs - Customer(s) and participants, roll call over time (who showed up, who didn’t) - Vendor/payee - Preset settings – this may be part of templates - Sub time frames – these hold a place but get tied back to the master for all lists of who, what and where - Pick options: dates, fees, times, workshops, classes, etc. (usually tied to invoices and quotes) - Destination – (quote, transition invoice, regular invoice) - Details – follow up - Finished settings (projects, to do lists, jobs, etc.) - Overlaps, gaps, possible conflicts - Rewards programs and promotions - Availability – not available - Medical records - Caps, minimums and requirements optional - Deadlines, timeline, phases - Rentals - Financial players and factors - Invoice payments and e/r payments with again and schedules - Rate tables (sales and seasons) - Standards – start and end time ranges, slot values, days of week, reoccurring items - Job costing - Statues changes and aging - Queue times - eCommerce - Inter corp - Masters - Back tie to units - Cancel or void (back out) - Check in/out, start/stop time - Mass entry - Report functionality - Waiting list |
|
|
AU 376 |
|
Daily Tasks | 2/8/2011 |
• Tech support, phone calls and emails. • Worked on the multi-media player mock-up. • Sent an email to my dad and another associate of his. • On the phone with a customer going over depreciation and how to record it. • Working on the "any” scheduler application. • Reading old notebook. • On the phone with Steve going over progress and new discoveries. Talked about the element of time and how it is going to play, expand and tie things together. Fun brainstorming session. |
|
|
AU 396 |
|
Daily Ideas | 2/8/2011 |
On post-it notes in notebook: • Go through each section (main app type) and figure out the groups (biggest to smallest) help provide a map to quickly get at the data. • On sales tax – redo the report to show a daily breakdown with a drill-down to details. • I want everything to go from main, groups, categories to details. |
|
|
AU 377 |
|
Daily Tasks | 2/9/2011 |
• On the phone with Steve going over new progress. Talked about the advanced add to cart features and flow. • Spent some time playing with the advanced add to cart page. • Tested some funky stuff with the “with Tax Included” tax settings plus backing in to a total dollar value. Basically, the user wants two reverse calcs both done at the same time. • Made some tweaks on the advanced add to cart page. Got kind of stuck…. Lots of moving pieces. • Added an auto calculate switch to help control the page and the auto calculations done on the page. • On the phone with Steve telling him where we are headed with the advanced add to cart page. • Started prepping the page to receive URL params as pass through values. |
|
|
AU 397 |
|
Daily Ideas | 2/9/2011 |
On post-it note in notebook: • Financial history look-up • User history look-up by payee id and location • Full site map of the adilas.biz system. My Quick links • Email sales and support page. • Beef up flex grid searches and dynamic drop-down titles and options. • Payroll feeders on balance sheet items. • Time conditional logic – only date, no time, just a single day (choices). • Might sound weird – no dates – but able to show up for roll call – on specific numeric days (not dates). Like accrued payroll… • Standalone declarations From mini-notebook: • Add a flag to help people know if a transaction is system maintained or user maintained. • Make the system return and report. • “Teach them correct principles and let them govern themselves.” –Joseph Smith • Help the people catch the vision – this will drive them. • Everybody is playing on the same team - bring things together. • A solid base supports the whole. -Need pagination on sales tax report. -Ease the load on the server. Reports are either too big or take too long to run. I want it to run as smooth as possible. -Maybe add a flag per line item for possible tax problems. This would help the accounting staff find the possible problems quicker. -Once we start in to Flash – I can see navigation, sub modules, shopping carts, schedulers, training, etc. starting to play in the same base player. It might be cool if there were options for classic html and interactive or flash. |
|
|
AU 378 |
|
Daily Tasks | 2/10/2011 |
• On the phone with Steve’s sister talking about medial scheduling and billing. • Did some invoices and deposits. • Working on the advanced add to cart and my cart favorites. • Wrote and email to a contact about drag and drop options. • Finished up the changes on the advanced add to cart page. • Posted new files online for the advanced add to cart and my cart favorites. The new code allows for the auto calc functions to be disabled and to pass dynamic values to the advanced add to cart page through a my cart favorite button. • On the phone with Steve. We went over the new features and talked price quotes for the store that is being worked on. • Worked on some help files. |
|
|
AU 398 |
|
Daily Ideas | 2/10/2011 |
On post-it note in notebook: • Had a dream about data and reorganizing it in to days, months and years (today, yesterday, last 7 days, last 15 days, last 30 days). With a drill-down to details. I have to do something to help ease the load of the server. -Need a customer payment page. Maybe use the customer id number and email address as a login. Once in, allow them to view their history (invoices and quotes) and make a payment on their bill. When done provide them with a receipt of sorts. -On the training and media player – I want options for QuickTime, mp3 audio, html step-by-steps and Flash. I want to service all of our clients and their learning styles. -Label making – this could be products, barcodes, prescriptions, customer mailing, etc. |
|
|
AU 379 |
|
Daily Tasks | 2/11/2011 |
• Cleaning up some bad debt. • Reoccurring invoices and some reoccurring payments. • Did logos for two customers. • Worked on a business bio for adilas. |
|
|
AU 380 |
|
Daily Tasks | 2/12/2011 | • Working on a written version of the history of adilas. Created a four page document and then a smaller one page condensed history and education bio. | |
|
AU 381 |
|
Daily Tasks | 2/14/2011 |
• Spent some time monitoring the server. • Purchased 3 new domains – they were businesszipper.com & .biz and businessdatamapping.com. • Worked more on the adilas.biz history document. • On the phone with a rep going over touch screen options and my cart favorites. They were onsite helping at a dispensary and they were really frustrated with how long the invoice and checkout process takes. The problem was that they weren’t using my cart favorites or the advanced add to cart page. Those two tools really help in their industry. • Worked on the history document. Read it out loud and worked on editing with my wife. • Pointed the new domains to the correct server. |
|
|
AU 382 |
|
Daily Tasks | 2/15/2011 |
• Working on the element of time. • Reviewing notes. • Had two different phone calls to help do some tech support for dispensaries. One was dealing with credit cards and cash drawers and the other one was dealing with my cart favorites. • Started working on a giant matrix for the element of time (6 pages typed together). The purpose is to determine types of time and functions of time. |
|
|
AU 2184 |
|
Brainstorming Types & Functions of Time - Elements of Time | 2/15/2011 |
Simplify – Types and Functions of Time 1. There are 50 to 100 known types of time. Many are very similar, only what you call it needs to change. Almost like groups or families. Like values. 2. There are 50 to 100 known functions (needs) for time elements to play with. 3. Most people want things that are pre-set and ready to function out of the box. Other people want to be able to customize things. 4. If things are too hard to do, set-up, or maintain… you lost functionality because people are inherently lazy. K.I.S.S. 5. What is a standard? How do I play to that? 6. It needs to be as simple as possible. 7. What if we created basic templates (types and functions) and then allowed the user to apply a template to each time element. 8. What if every element of time was as simple as an id number, a corp, and a template id number. All other pieces would be subs according to the template (directions and requirements). At least one sub would be required but the element could have more than one. 9. What if the types were something like: personal (my), person(s), place(s), thing(s), combination, custom. 10. What if the functions were something like: date only, date/time, …. Infinity 11. Why am I scared to commit… I see that it is big; I see that people want to be able to call it this and that. I want to tie it all together, and part of me wants to keep it all under the same roof “elements of time”. 12. Is my pride getting in the way? Even this page… am I getting too worried about what people will think (later on)? What is the hang-up? 13. I’m feeling a lot of stress… I have needs to finish up balance sheet, do a training application, build the scheduler, map out the entire system, build new reports, etc. 14. What happened? I’ve always had tons to do… why the huge swarm of things in the last couple of months? Why am I so limited? Everything feels big… Everything feels complicated… It seems like everything is so interconnected… I know that is good and bad… 15. I’m thinking that the process needs to go like this… scheduling, balance sheet, and training. I would love to put training first but I also know that some major changes are coming down the pipeline. 16. Things are changing so fast… It is hard for me to keep up with things. I can’t imagine being a user and trying to deal with all of the changes. 17. Maybe keep making the changes and then go back and start training people how to do it properly. (Once changes have been made) 18. Apply what you learn along the way. The more you do the more it sticks and becomes a part of you. 19. Who is counting time anyway… I’m not trying to break some record or something. I am trying to make progress and I’m okay with a step at a time. Only run as fast as you are able. From a gridded outline for brainstorming “elements of time”; Needs – rows – 1,2,3… & Types of Time – columns – A, B, C… NEEDS - rows 1. Basics, quick name or title, corp, id, template, creator id, sub type 2. Date (day only, single, multi, range, reoccurring) 3. Category & sub category sort 4. Time (time only, n/a, single, multi, range, special rounded, reoccurring) 5. Total time 6. Notes & credits (real, practice, draft, concept – 255 or big) 7. Payroll 8. Privacy, show/hide, web, visible, permissions 9. Assignment(s) & changes (one or many), change log 10. Reminder(s) & notification(s) - sending messages and pushing reminders to main homepage 11. Photos & media – subs, choices, ftp, decisions, stitching, content… video, stills, graphs, maps, audio, html, pdf, word, etc. 12. Comments 13. Invoice tie-ins – details or summed up (invoice types), (invoiced, not invoiced, no charge), recipe tie-in (one to many) 14. Quick tie-ins (build or pull from multi chain as needed) 15. Financial & general amount – standalone declarations, able to add back up to the main (revenue, costs, value) 16. Sign-offs & by who? – maybe a 1-many (review, outside players – sharing) 17. Rate tables & look-ups – seasonal, promotion, sales 18. Expiration dates &/or show until dates – due or target dates 19. Booked vs. actual usage, planned vs. reality 20. GPS subs 21. Sub pool(s) – what kind in/out of play 22. Reoccurring (master/share, template, blocks, average unit, standards, slot, values) 23. Flex fields (names & types) 24. Tie-ins (flex grid, what else) what about tying together subs and media, sewing, stitching, links, groups 25. Customer (1 or many) look back, relationships to other tie-ins, roll call, participants, general or generic 26. Vendor/payee (1 or many) 27. Histories & usage logs – start, stop, # of times 28. Sub times or sub time frames – due dates, aging & queues (relationships) 29. Follow-up & details –progress reports 30. Finished/starting settings or completion – starting, prerequisites, requirements, test & evaluation 31. Rewards & promotions 32. Medical records 33. Capacity, min, max, optional 34. Deadlines, timelines, phases, grace periods, due dates, outlines, content, details 35. Status changes – edit mode, dynamic status lock down 36. eCommerce 37. Inter corp – security, settings (general, per corp, per user, IP address) 38. Back tie to units – this may be on the unit or a pool that the unit is assigned to 39. Cancel/back-out/void (see status), (make sure and cascade to subs) 40. Check in/out (start/stop, actual/rough) 41. Mass entry – recipes, packages, deals 42. Priority & rating 43. Reports & searching needs – capacity, conflicts, testing, history, usage, availability, booked, open/closed 44. Waiting list 45. Cleaning status 46. Fees (late, cleaning, other) 47. Person(s) – customer, vendor, payee, user, salesperson, N/A, party, unassigned, crews, lines, shifts 48. Place(s) – subs, temp, variable, multi, unassigned 49. Thing(s) – storage, units, parts, general or generic, assets, money, supplies, labor, overhead, shipping, sub-contractors, game 50. Dynamics – (fun & extras, names, titles, needs, html, multi-step, memory, colors, increments, webservices) Types of time – columns A. Lists, tasks, assignments B. Notes & reminders, progress reports C. Basic, scheduling & appointments D. Time sheets, time logs E. Sharing & collaboration F. Sales & promotion marketing G. Meetings & events, classes H. Projects, updates & newsletters I. Resorts & tabs J. Reservations K. Dispatching L. Registration M. Job costing, estimates, quotes & invoices N. Maintenance, manufacturing & production O. People, employees, techs, doctors, teachers, crews P. Invoices, e/r’s, bs: reoccurring or system-maintained Q. Goals & forecasting, (production, sales, general) R. Rentals, storage S. Places, rooms, locations, subs, main, #’s T. Things, stock/units, parts, general, pools U. Payments in/out, date due, deadlines & grace periods |
|
|
AU 383 |
|
Daily Tasks | 2/16/2011 |
• Squeezed new video for a customer. Posted file online. • Email updates and sending invoices out. • On the phone with a customer going over my cart favorites and using the flex grid to search drivers licenses. • Did some research on the iPad and Sorenson Squeeze 7. Little bit of research on Flash as well. • Recording ideas for the multi-media player. |
|
|
AU 399 |
|
Daily Ideas | 2/16/2011 |
-On all advanced searches – show a link or button to help filter the results. This uses the advanced searches without making the users wade through three different search forms and not having any existing data. See the invoice payment page for options. -On the advanced searches – what if they submitted back to the main search page and passed values and modes “main, lines, parts”. That page could then decide whether to show all forms, just one form and what options to prepopulate. -We had a cookie cook off at church – we didn’t know that the judges were looking for … some of the cookies looked good and some not so good but had a good taste. Who is judging our product? What do they want? |
|
|
AU 2185 |
|
Brainstorming - Ideas & Concepts for the Multi-media Training Tool | 2/16/2011 |
Ideas & concepts for the multi-media training tool 1. Make a template for learning and distributing knowledge. 2. Knowledge = Information (correct & right information) x Experience or K= I x E 3. Add a crumb trail to help the users know where they are at… 4. Secure multi-media player. Be multi-media I mean graphics, buttons, links, text, searchable, printable, audio(mp3), video, mapping, motion, PDF, web, controllable, code once – use many, dynamic templates, database fed, permissions, history, usage, forums, feedback, charts, pod casts, dynamic outlines, decision trees within presentation, still images, automated output, etc. 5. Be able to mix and match what the player can do… 6. The end goal is to automate as much as possible. We may have to take some steps to get to that stage. 7. Usage permissions – General public (no login required), all users per corp (requires a valid login), only specific users may view (1-many from training to users). 8. Usage histories – Every time a user views a clip – we record a history note behind the scenes. Random idea – maybe show the users which ones they have seen and when. Maybe even a started and completed flag. 9. If a valid login is required, how can we help the users know if their time limit is up and/or getting close. Maybe run a check against the login table and then prompt them to keep the session alive by searching or refreshing their login history page. 10. On usage histories – it may be cool if you could require certain training modules before allowing a user to use a specific part of the application. This could get out of control but may help educate people before you just turn them loose. 11. The usage history would also need some special reports to help managers and trainers know what is being viewed and what might need a touch-up or revisit. 12. As long as we are doing training… what about testing and evaluations? Why not include a testing module. Not required at all unless you want it. We provide the database, question templates, etc. We also provide the correcting reports to managers. 13. What about a valid login plus an IP address – additional security? Just an idea. Maybe a white list of IP addresses. This may come later if needed. Another idea is require the IP addresses on the login not the media. 14. Training could be as simple as a narrated slideshow or as complicated as a branching interactive video with different sub sections. Because it is a multi-media player – you could even mix and match presentation types in a single player. 15. Ask the question – what would I do? 16. Maybe allow for web services or domain name aliases… 17. Allow outside users to login under a public username and password to submit content for review and formatting. This may require an approval process or an approval/sign off field(s). Only show items that have been approved. 18. Be able to categorize training. This also includes sort options. 19. Keep things fast and efficient – this may require a hybrid solution… 20. We might need to use frames – standard adilas header, player window, extra content to print or add/edit something, standard footer a. This could help with branding, searchable and printable text, etc. b. This might need to be three or four windows within a single master window – you might need to scroll the whole page as a unit. You may also need to scroll the extra content window. It is possible to also use an I-frame instead of a normal frame. 21. One of the goals is to lessen the number of clicks… leave menus open, show indicators, simulate a back-type button, etc. Make it a good experience. This also includes a play all of next clip. 22. Allow the user to determine what buttons to show… this would be done during the set-up phase of the media clip. Different buttons might be play, pause, stop, rewind, fast forward, full speed, ¾ speed, ½ speed, ¼ speed, loop, back to start, step forward, step back, volume, mute, scroll up, scroll down, scroll right, scroll left, zoom in/out. 23. “Apply” what you learn! Do this along the way… don’t wait to the end. The more you apply it, the more it becomes a part of you. 24. Be able to choose options like video, slide show, horizontal scroll (h-scroll), vertical scroll (v-scroll), audio, web link(s), animation, step-by-step, etc. Each section or sub section could have their own button options. You could also show/hide and call any button from a function call on the fly. 25. Make the player as generic as possible. It also needs to be as flexible as possible. It should be able to respond to any event or need. In order to do this, all functions will need to be available and published (written & documented). We may even need to provide flash code samples. Make it easy, I don’t want to be the bottle neck… open it up for other developers. 26. If a change is made in the process, maybe have a piece at the end that shows additions or modifications. That way you don’t have to totally redo the entire clip. 27. Another idea is to break the pieces into smaller pieces so that it would be easy to cut and paste or fill in changes or gaps. Think “bite size” pieces. 28. Allow backgrounds and text colors to be modified. Maybe even think about variable (dynamic) symbols and buttons (icons). Make everything transparent to help show custom background colors. 29. Another option is to allow dynamic player buttons, use .swf files, and allow the player to be fully customized. Even allow a custom loader to be used. 30. The smaller more modular pieces, the better. This will help with branching logic, videos within videos, smaller downloads, and snap-on components and functionality. 31. Remember the non-flash users. This could be html or .mov files. 32. Push vs. Pull technology. Allow the user options to show related clips or possible next steps. 33. Once we start in to flash… I can see navigation, sub modules, shopping carts, schedulers, training, etc. Starting to play in the same base player. It might be cool if there were optional choices or options for classic html or interactive Flash. 34. I want options for QuickTime, mp3 audio, html step-by-steps, & Flash. I want to service all of our clients and their learning styles. 35. Training may fit best as an element of time similar to a document, outline, or idea. The media assets and contents could then be tied to subs. Think of an interactive outline that has subs and dynamic content. That outline becomes the training as it is organized and then sent to a player to allow the user to interact with it. 36. What about tests, quizzes, and evaluations being tied to education and training pieces? This is not required but might be a cool option. 37. Allow the doors to be opened to recruit or enlist help… This could be flow, concepts, media, content, suggestions, needs, etc. The goal would be to provide a clear and logical path with built-in checkpoints and checks. This is a way to duplicate yourself and share the load. 38. Dealing with content, media, and/or other assets… What about having a place for credits… This is the who behind the pieces… This could help to motivate people to play and even drive business to them as individuals. 39. Random idea – Inside of LTF we have a music selection (jukebox or iPod). It might be fun to allow others to be able to change music or have some fun and control of different tunes and/or moods. This doesn’t have to be tied just to music. It could be for music, background sounds, different levels and takes, tracks, different teachers and/or instructors, additional commentary, etc. Sound and music are a big part of learning and defining who people are and what they enjoy and/or feel comfortable with. 40. Instruction could also be a form of meditation or visualizing certain steps and/or events. Think of some calm backgrounds with someone talking or taking you on a mental journey. 41. What about custom help files or standard operating procedures? Because each page has a help file id, we could technically allow a user to tie in their own procedures dynamically so that their users would see or have access to the correct help files or custom help files. This could be HTML, pdf, audio, video, graphics, or other…. (added 12/14/12) |
|
|
AU 384 |
|
Daily Tasks | 2/17/2011 |
• Recording ideas for the training application. • Went in to town to meet with my dad and one of his associates. We had breakfast at BATC and then started talking about the multi-media training tool and where we are at. I explained my personal needs, wants and vision. Both chimed in with ideas and comments. Great session! I took some good notes and we are planning another meeting in a couple of weeks. 30 miles. • Brainstorming on the player and flow for the application. • Watched a couple of videos (online training) at Lynda.com on Audacity and Flash 8. |
|
|
AU 400 |
|
Daily Ideas | 2/17/2011 |
-Not everything that gets recorded needs to be printable – what about practice, draft or concept notes. -We need an option to add up to five levels deep for an outline. This outline needs to be able to form in html and automatically in the flash player (sub nav panel). Be able to edit on single and bulk levels. -On post-it note: Five level outline (html and Flash nav) progress reports: training (goes under documents, outlines or content), tests, quizzes, evaluations, locked (recruit help), sharing and submitting content, credits (sphere – inside the sphere), chaining things together, songs and shuffles like LTF, FTP upload of assets. -As a note on the outline – maybe use a table with 10 columns. Use two columns for each level. Column 1 would be the number or bullet point. Column 2 would have the title, date, etc. -We need to be able to tie assets to outlines and/or subs. This is full on content management. Be able to upload and story assets so that it doesn’t impact the main adilas site or traffic. -What about progress reports. This could be for tasks, to do lists, documents, students, customers, etc. -What I’m seeing is eventually all of this data needs to be able to fly around via web services. We want it to get to the level of … “your data, you cache and retrieve it, we secure it.” Super open interface. This could even allow outside developers to tie in to adilas functionality to create a hybrid super solution. -Sphere – once you are in the “data” sphere you can virtually go anywhere at any time. Other words or names: data sphere, data bull, data globe, data bubble, data orb, data orbit, realm. (This could create a fun visual. The sphere or space could continue to grow to whatever level.) (Business data sphere.) -Training may fit best as an element of time similar to a document, outline or idea. Media assets and contents could them be tied to subs. Think of an interactive outline that has subs and dynamic content. That becomes the training as it is organized and then sent to a player to help interact with the user. -What about tests, quizzes, and evaluations being tied to education and training pieces. This is not required and would be a possible option. -Allow the doors to be open to recruit or enlist help, content and suggestions from others. Provide the path so that others may help. This is a way to duplicate yourself. Share the load. -Maybe have a show/hide status for items still in edit mode. It might also be cool if you could lock things down at some point or only allow growth or actions on certain pieces. -What if we created system-maintained time elements and then became the watchers. I’m not saying everything, but what it we wrapped all existing objects and data inside of adilas and allowed them to play or be counted in their own time element. -Dealing with content, media and/or assets. What about having or allowing a place for credits – this is the who behind the pieces. This may help to motivate people and even drive business to certain players. -We need to stitch, sew, chain and link things together. This could be physical, virtual or based on a relationship model. 1-many - The whole system is a series of 1-many (one to many) relationships. -Random idea – inside of LTF we have a music jukebox or iPod; it might be fun to allow others to be able to change music or have some fun with different tones or modes. This could be music, sounds, different tracks, different people, additional commentary, etc. Sound and music are a big part of learning. -Instruction could also be a form of meditation or visualizing certain things. Maybe calm backgrounds with someone talking or taking you through steps… |
|
|
AU 385 |
|
Daily Tasks | 2/18/2011 |
• On the phone with a customer trying to show them their new commercial. • Reviewing the ColdFusion 9 cfspreadsheet tags. Did some research on using spreadsheets in ColdFusion. • Helping a customer and his staff create and print out custom barcodes. • Working on Excel files for a company. • On the phone with a customer that got locked out of the system. • Worked on a PCI compliance issue for my computer and modem. |
|
|
AU 386 |
|
Daily Tasks | 2/19/2011 |
• Wrote an update email to all merchants who are using USAePay and Newtek as their merchant processor. The update was about PCI compliance stuff. • Worked on some other Excel files for some customers. Sent them files and as adilas history report. |
|
|
AU 401 |
|
Daily Ideas | 2/19/2011 |
-Need an advanced flex grid search and results page. -Sum up flex grid amounts. Be able to filter the standalone flex grid per main. -It might be cool to pull statements to groups of people. Say 30, 60, 90 – who has values in that range. -Need to add a roll call to each item in the system. This includes associate links in the flex grid and line items of other pieces. Map it out. -Be able to sum up and group flex grid tie-ins without showing all of the details. -Here is what I need to do – catch the details on the operations side, once the details and flow are good to go, start pulling back in to groups and then sums. The grouped sums are the goal but don’t do much without the underlying details and pieces. |
|
|
AU 387 |
|
Daily Tasks | 2/21/2011 |
• On the phone with Steve going over things and catching up on the past week. We talked quite a bit about cash drawers and tracking exact ins and outs and drawer amounts. We also talked about Merchant Processing and maybe needing a new gateway for CHARGE Anywhere. We also talked about a training application. • Spent some time on the phone with a contact helping out with some adilas stuff. They quit a company who is getting off of the adilas system. Created some business cards for this contact and sent them an email with a little bit of info. Sent another email about how adilas commissions work. • Spent some time recording ideas for the “any” scheduler and the multi-media player and training tool. |
|
|
AU 388 |
|
Daily Tasks | 2/22/2011 |
• Light brainstorming on system-maintained elements of time and how they play in to the whole picture. • On the phone with Steve doing a quick review of where we are at and what is needed to make our current projects flow and jive together. They are the elements of time, balance sheet changes and training. • Worked on the elements of time. • Sitting at my table and working on the 6 page time matrix (pieces of paper taped together). Started sketching out ideas for database tables. |
|
|
AU 402 |
|
Daily Ideas | 2/22/2011 |
-On the interactive map – under objects and data over time – include web basics, using the browser, multi windows, find on every page, etc. Also include client-server models, 1-many and other basic adilas theory. -Expose the payroll reports to outside the calculate payroll page. Also allow pages to be saved as pdf. |
|
|
AU 389 |
|
Daily Tasks | 2/23/2011 |
• Signed up for a test account with Charge Anywhere. • On the phone with a customer going over how to pay for a PO with normal funds and a vendor issued credit. • Working on the element of time and database fields. • Working on filtering down the functions of time. Looking at close to 20 functions down from about 50. • Planning small pieces of the database and pouring over needs of the elements of time. |
|
|
AU 2186 |
|
Brainstorming - Elements of Time - Email Calendaring & Time | 2/23/2011 |
Hotmail – To Do: - Due date: = none or date java script and choose date - Due date time: = non or presets - Priority: high, normal, low - States: Not Started, In Progress, Done (extras) - Send Reminder: no reminder, increments of time before the to-do event (extras) - Description: optional (extras) The display had a section for past due with a number, today with a number, done closed unless opened, once you clicked on done, it would show the item with a strike-through text value. It also allowed me to delete done to-do’s. A warning came up and prompted for confirmation. Smarter Mail: My Tasks: - Subject - Start: today’s date with nearest ½ hour block chosen, java script calendars and time pickers - Due: today’s date with an hour added on to nearest ½ hour block, choosers - Reminder: none, time increments - Priority: 1-10 - Status: Not Started, In Progress, Completed, Canceled - % Complete: 0-100 (by 10’s) - Description - Categories: not required My Notes: - Color: - Notes: (both searchable) - Categories: (both searchable) My Calendar: - Subject - Attendees - Location - Start - End - All day appointment - Availability: busy or free - Reminder - Email notification - Recurrence info o Sub section: • Once • Daily: subs - every “n” days css, every weekday, forever, end after “n” occurrences, end by date • Weekly: subs – every “n” weeks, Sun, Mon, Tues, Wed, Thurs, Fri, Sat (checkboxes) • Monthly: subs – every, “n” month(s), day “n”, the first, second, third, fourth, last; day of week • Yearly: subs – every month, day – the first, second, third, fourth, last day of week of month - Notes: - Categories |
|
|
AU 390 |
|
Daily Tasks | 2/24/2011 |
• Brainstorming on time and how to reduce the number of functions of time. • Writing an email to an associate about where we are at. • Reviewing notes. • New logo and colors for a company. Posted files online. |
|
|
AU 391 |
|
Daily Tasks | 2/25/2011 | • Working on the Charge Anywhere gateway. Got stuck due to an SSL issue. Did some research and ended up purchasing a cfx tag to help with http requests. | |
|
AU 392 |
|
Daily Tasks | 2/26/2011 |
• On the phone with Steve going over things and touching base. • Reading documentation for cfx-http5. Custom cfx tag. |
|
|
AU 403 |
|
Daily Ideas | 2/26/2011 |
-On the scheduler – allow for an auto or custom date/time stamp. -Create a master functions of time list and then allow corporations to alias or change the names. What they do will still be the same but allow for custom naming. -Categories are the same way – create defaults and allow them to change them as needed. -Categories are tied to functions of time and functions of time are tied to templates or types of time. -When setting up templates – allow for dynamics to be set “current user”, “default loc”, etc. -On invoices – maybe have a daily number to keep things smaller. Each day it would start over at 1 and go up. -On my cart favorites – some of the users would like a group button that allows for custom settings to be applies to more than one item. Basically, they want to simplify the first round of choices and have a 1-many on buttons and settings. Code once – use many. |
|
|
AU 393 |
|
Daily Tasks | 2/28/2011 |
• Reading documentation on the cfx-http5 extension tag. • Sent an email to Charge Anywhere asking about doing an inquiry. • On the phone with Steve going over options and needs. • Worked on integrating the Charge Anywhere gateway. |
|
|
AU 404 |
|
Daily Ideas | 2/28/2011 | -On all photo and file uploads – it might be nice to use the cfx-http5 tag with sync options to help while uploading files (take the load off of cold fusion). It might be cool to see an upload status or graphic that says uploading. It might also be cool to help the users tune up their scanners and cameras to make fast downloads. | |