all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
Yellow
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Uploaded Media/Content & Other Files
(1)
|
||||
| Media Name | File Type | Date | Description | |
| email_about_time_clocks_12_10_16.docx | Doc/Text | 1/8/2019 | This is a text copy of an email that was sent out on 12/10/16. It is currently 1/8/19, and I'm adding it to the main element of time. Just trying to keep things straight. This email was a pitch to see if we could build out a smaller part of the whole and make it a standalone finished product of sorts. Anyways, just some ideas. One of the things that I like about it, is it has a limit and done option. Some of the other projects in adilas just go and go for ever... this one at least feels like it has a bottom and could be fully completed. | |
|
Notes:
|
|
Started off the day doing some clean-up and recording notes. I then started working on some new payroll changes from Shawn Curtis. Eric logged on to the GoToMeeting session and I helped him with some custom logic access points on a page that prints bulk PDF shopping cart labels. We got that finished and then pushed up the files to all servers. Shawn jumped on the GoToMeeting session from 11:30 to 1:30 pm. We started out merging files and working through payroll pages. We then switched gears and started talking about the future for time clocks, project time clocks, payroll tools, HR tools, and tracking sub payroll (tied to time). We also talked about recording mileage. I took a bunch of post-it notes worth of notes and scribbles. Here is what I got. - On elements of time, Shawn often records a location (for tax and mileage purposes) and what the task or project is. - Shawn would love to build a time clock feature that tracks mileage and is super easy to use. Kinda like Bryan's little time clock app. - Allow them to use a mini time clock feature - super simple and scaled back. Any special edits and/or other options would need to be done inside of the normal system. - Allow for departmental or department based logins and time clock options. This could be normal payroll clock in/outs and/or elements of time and project based clock in/outs. - Make sure and look at both Russell's time clock mock-up as well as Bryan's little time clock app. Maybe look at Toggle and even older adilas notes and ideas. Keep it simple. As a side note, this need has existed for years. If we think back, time cards and time clock stuff came right after stock/units back in the early 2000's (2002-2003 ish). There is still a need even today for more tools like this. - Add a small mileage tracker that could be connected to elements of time. It might be nice to either be used as a standalone project and/or an app that can be connected to elements of time. Make the connection to elements of time optional. - We need to allow settings per person for what projects to show up and how to sort and show those simple selection options. - Show the amount of time that has lapsed... - Use simple start and stop buttons. - On the mileage subs of time, tie to an employee name (payee id). That will make it searchable later on. - help search by person and show totals based off of a date range and/or a project selection. Basically, allow for some advanced search options for the mileage reports. - One of the main goals is to limit the number of clicks that a user has to make to get something done. Keep it super simple. Maybe even its own interface with limited functionality. - Simple buttons to clock in and clock out... We do all of the mapping and logic behind the scenes. - Setup a mini skin or something like it. Allow for departmental clock in/outs, single payroll clock in/outs, project clock in/outs, and mileage options. Make all of these pieces toggle on/off options that could play into the same interface if needed. Think settings and dynamic point and click setup. - Make a number of small and simple tasks. Use the power of adilas but make it look super simple. We could do this for all kinds of features and functions. This might be worth exploring and assigning small teams to build out certain parts and/or sections. - Make the look and feel super customizable (colors, placements, buttons, features, etc.). - What about sub flags and tags... That section is brand new and could help with things like sub phases, sub locations, or even different departmental levels for project time (x department charges $50 per hour and y department charges $35 per hour, etc.). That could be pretty cool to help track different rates. - Along with the comment on sub tags and flags... What about holding amouts, time sums (math on the start and end times), and even some billing and/or invoice options. That would be really cool. - On the mileage settings as a sub of time, setup a preset matrix so that you could enter common destinations and/or sub locations. For example, say I always want to record mileage from my house to the shop/office or from my house to my parent's house. It would be really cool if we could preset these values as round trip and/or one ways. This could be based from work, from home, from wherever, as long as it is consistent. - The matrix of sub locations and/or preset mileage settings could even have fields like: mileage alias name (generally what do you want to call it), a from location, a to location, one way mileage (value), round trip mileage (value), sort values (manual sorting option), and a status (active/show or inactive/hidden). These settings could be on a per person basis or on a corp-wide basis. Maybe even use JSON storage for the settings. - What about GPS stuff? We have the fields to hold those values. What if we used an app and got where are you? Where are you going? Where are you now? - What if we had full GPS stuff being tracked for super cheap. Think of a small phone app or something like that. Maybe a small app that piggy backs on a phone or mobile device and then used an API to talk to adilas. That would be pretty cool. - We could add up mileage, do point to point mileage, use full GPS stuff, or just allow for user entry into an open mileage field. It could be super techy or crazy simple. Lots of options. - What about billable hours? We already allow for sub dates and times to be pulled into invoicing. This has existed since 2011. What is the next level? What if we had ways of flagging things with some kind of invoice status and/or billing info. What invoice, is it billable, not billable, has it been billed, does it need to be billed, what is the rate, etc. Think of the next level. We could expand sub dates and times or we could build it into sub flags and tags stuff. - As Shawn was talking, I had the idea, what about cross corp billable hours. Say one company is working on a project for another company. Wouldn't it be cool if a small mini channel and/or tunnel could be made to bridge one corp to another corp. Basically, a user logs in to their corp and is able to make a small time clock record in another corps project. This would have to be permissioned, allowed, agreeded upon, and API socket based connection. Still, that would be pretty cool. - Think app enabled functionality. Think mini skins and/or standalone mini mobile apps. - Be able to quickly switch tasks, projects, etc. Minimal number of clicks. There may need to be a different admin page, but the main interface could be quick and fast. - Shawn wanted to make simple setup wizards to help do the settings and management stuff (admin/manger side). Easy to use and virtually hold your hand through the process. - What about the sub payroll functions and features. That was planned out lightly back in 2011 but has not yet been fully built out. The database tables exist, the ideas and concepts exist, but it has not yet been built out. Maybe it is time. We need to allow these new apps and settings to go all the way out to sub payroll. This could be for employee time clocks and/or project time clocks. Tie things up all the way along. - We will need an admin and payroll dashboard of sorts. This is where an admin and/or manager could get their reports and check on things. Quick reports, easy access, permissioned, and able to see and get to reports and stats quickly. - What about accruing payroll. Currently, that is somewhat hard to put your finger on. By accruing, I'm meaning what is building or amounting in the background. Imagine being able to see what hours and bills are mounting before they hit. Instead of a developer or another employee submitting a huge bill that you didn't know about, you could watch things grow as they happen. Think, what will need to be paid and/or what is value of project X or Y. - Along with accruing payroll and such... It might be nice to go into the smaller entries and do some math on them and store those values in the database. You could then pull quicker reports vs. calculating hours, minutes, and seconds on the fly. That can be a pain. Look into this as an option to help speed things up. - Take what we have already got and put it together in a new skin or interface or mini package of sorts. Most of the underlying pieces are already done. It just needs to be combined and wrapped up together in a cute little sellable, presentable package. - What about other HR (human resources) tools? Branch out a bit and think and/or ask what people need. People will tell you if you ask the right questions. - Map it out and then pitch it as a proposal. Think of the bigger picture. It might also help to think of both short term and long term options. - Dream it up, we'll help you wire it up! |
|
Additional Comments/Notes - Subs (1)
|
||||
| Title/Caption | Date | Time | Done By | Comment/Note |
| Notes from Steve | 12/12/2016 | 9:32 am | Brandon Moore |
- Start at the beginning. - Similar to sub inventory... help them start and then walk through the system. Almost a wizard-type interface or step-by-step process. - Some people don't like videos and help files. They want something that is intuitive. Keep it simple and straightforward. - Small wire jobs can go so far and be so cool - so many things already exist - we just need to wire it together - little mini apps or small pieces. - We need to build a mixture of things. Keep thinking web or any device. We may not want to build super specific apps. We want to reach a wide verity of clients and industries. - We need to slim down and make things simple and/or help people follow the flow that they do. We just wire it together and help them bounce without 50 million clicks. - Think perspective - space shuttle view, plane view, birds eye view, street level, ant or grasshopper level, micro level. - Use technology to help sell what we have. Communication is a huge key. One of the hardest things is that we have some cool things but how do we let everybody know what we have. People are super busy. - We would really like to do some personal training sessions twice a month. We would like to see if we could get people to come to Shannon (where ever she is). Maybe use my dad as a coordinator and venue finder person. - Steve would also like us to build out a small page that shows training and make it full on ecommerce ready so that we could start getting payments directly from the site. Maybe go in and scrape some code off of the community funded projects page (https://data0.adilas.biz/top_secret/community_funded_projects.cfm). |