Adilas Key Contributors:

Steve Berkenkotter - Main owner and business partner - original ideas, concepts, and training - sales, relationships, dreamer, visionary, custom code, coordinator, builder of the first industry specific skin, and the list goes on. Huge player in the adilas story and timeline. One of the original owners in Moring Star Automotive - where the system came from. There are three known Steve's in the system notes. Most of them are this Steve (99 out of 100 times). He won't admit it, but adilas was his brainchild.

David Berkenkotter - Steve's brother and business partner in Morning Star Automotive. David was a system user and helped us create the adilas quick search. He liked using that feature, the quick search, but it only existed on one page originally. He wanted us to put it on every page. That ended up being in the header. He was also one of the original partners in adilas. Power user in the system. Sadly, he passed away due to cancer.

Shari Olin - Commonly known as "Shari O.". She worked in the accounting department back in the Morning Star days. She has been somewhat of a mother hen to help all of us crazy chickens keep going. She helps with customer support, training, payroll, bill collection, and tons of backend office functions. Major power user. Just being silly, but she can have the mouth of a sailor but the heart of an angel. Part of the adilas admin team and a great friend.

Craig Leitner - Also part of the original Morning Star team. Craig was the automotive floorplan and bank guy. He is a power user in the system and does a lot of bank reconciliation and other tasks. He currently works with Steve and asks as the adilas controller (money flow guy).

Cory Warden - Originally an adilas rep and consultant. Cory become part of the team after being a rep for quite some time. She helps with customer care, client support, project management, and keeping the team on track. She also does all of the news and updates and other training material. Cory does tons of oversight type services for our clients. Power user and part of the admin team.

Sean Carlton - Sean was a manager at a Cannabis dispensary in Colorado that used adilas for years and years until they sold. Steve recruited Sean to help with sales, deployment, and training. Sean brings lots of usage experience. Often, he is one of the helpers if we need to send someone onsite to help with a deployment or training session. Power user.

Brandon Moore - I'm one of the guys that writes most of the developer's notebook entries. Originally, I was hired by Morning Star, the automotive dealership, to help with data entry, accounting, and website stuff. I ended up being one of the main adilas developers and architects. I build content, write code, help other developers and team members, and help with training. Helped start the project back in 2001 under the Morning Star name.

Chris Dunsey - One of the first adilas interns (developers). Helped with a number of projects. Ended up being somewhat of a consultant later on.

Shawn Curtis - Kinda a funny story. He was taking a developer's class at Bridgerland. He knew my brother Russell. He asked to join our developer class and became one of the first interns along with Chris Dunsey. Shawn ended up helping with payroll and other projects. Some of the photo galleries in the system came from Shawn's help. He also worked on the media/content (file upload) pieces. Later on, he did more payroll work and acted as a buddy to Brandon and did some consulting work. We worked together for years and years.

Russell Moore - Russell is my younger brother. Originally, he was added to the group because of his graphic skills. He ended up being a great backend developer and project manager. He has also acted as a trainer and mentor for Brandon along the way. Much of the current system came from projects and efforts that Russell was involved with. He has also been Brandon's AI tutor in recent years. Great help to the system. Huge contribution.

Chris Johnnie - He is an entrepreneur who teamed up with Russell to help create a company called "Adilas For Business" or "AFB". Eventually, both Russell and Chris sold their pieces back to adilas. They were honestly the first ones to really try to run as a white label of adilas. This was back in 2015 and 2016. Chris really helped to push the product to the next level along with Russell's help.

Danny Shuford - Longtime friend of Steve's. Danny helped with some website design, sales, and videos for adilas. He even got into creating custom PDF labels for clients. Light development work.

Marisa Shaw - She is Danny's daughter. Danny brought her to an adilas training event in Denver, CO. Marisa was the star student. She ended up helping with some graphics, flyers, marketing material, teaching, instruction, and planning. Power user. Very helpful.

Shannon Scoffield - Shannon is Brandon and Russell's sister. Her maiden name is Shannon Moore. Huge help and virtual assistant to Brandon. She has helped with training, project management, and content creation. Most of the major content sessions were or have been with Brandon and Shannon working together. When they, Brandon and Shannon, were traveling, Shannon was one of the primary adilas instructors. If she was teaching Brandon was taking notes. If Brandon was teaching, Shannon was taking notes. Power user.

Cheryl Moore - Cheryl is my mom. What an asset. She owns a small business and has owed a few different ones. When we were doing training sessions, she came to every one of them. She asked wonderful questions and was a great supporter. Sometime, I would use her as a test subject - can my mom do this? If yes, we are good. If not, we may need to keep tweaking it. Thanks mom!

Wayne Moore - Wayne is my dad. He was my hiking buddy and more than willing to talk about ideas and concepts on our walks and hikes. He helped out with video stuff and was a great coordinator for making other connections. He worked at Bridgerland (technical college) and helped us get setup with classrooms, computer labs, and other great connections. Huge cheerleader! There is another Wayne, Wayne Andersen, he is a backend developer, systems guy, and database guy.

Wayne Andersen - This Wayne lives in Portugal and helps with all of the backend security, server, and code testing. Major skills, writes code, helps push all of us to new technologies, partially retired but loves to play with tech stuff. If you search for Wayne and it deals with concepts and coordination stuff, that's my dad, Wayne Moore. If you search for Wayne and it sounds like a master backend guy, that's Wayne Andersen.

Alan Williams - One of the lead developer's at adilas.biz. Alan joined us in 2015 and quickly came up through the ranks. Trainer, CTO, team lead, master developer, prototyper, and system architect. Alan has helped with many projects and features over the years. He also helped Brandon with some of the prep work for the adilas lite (fracture) plans and project. Sometimes called "Dr. Alan" by the other developers. Example: This might be a project for Dr. Alan.

Bryan Dayton - Bryan has been one of the most versatile guys on our team. Originally, he joined a development class out of curiosity. He and Brandon live in the same town and know each other from church. Bryan has done more custom code or small system projects than almost any other developer. He also joined the team in 2015. He helps with sales, custom projects, pushing on projects that he thinks will yield a return. Lots of work on the adilas lite and fracture project. Very hard working and versatile.

Dustin Siegel - Developer who helped with numerous cannabis and cultivation type projects. He worked directly under Steve to help with that business vertical. Many of the original pages that Steve built were taken over and remade by Dustin.

Eric Tauer - Developer and custom code guy. Originally, Eric knew Steve and lived in Salida, CO. As a note, adilas is Salida spelled backwards. Eric has a background in database work and data warehousing. Eric has done tons of custom systems for clients. Often, Eric would pioneer certain features or logic, as custom code, and then we would bring those features into the main adilas application.

Garrett Kirschbaum - Adilas intern and then full developer back in 2015. Stressful time of building and expansion. He and others helped run the adilas shop with Brandon's help. Garrett was a great developer and helped us standardize a number of tools and features. He was the first developer to work on sub inventory, back in the day. He also did other projects and helped with some developer management stuff.

Charles or "Chuck" Swann - Charles was an instructor at Bridgerland for web development. He builds custom websites, does amazing mock-ups, prototypes, and is a CSS master (styling a website using code). Chuck worked with Russell to help with redesign work, projects, and vision. Chuck worked fulltime for a number of years and now works and coordinates work done by a small hand-picked design and development team. Anything that needs some design loving gets passed over the Chuck and his small team.

Steve McNew - Friend of Steve Berkenkotter's. This Steve helped prep some whitepaper documents to help with getting adilas standardized and some internal audit type stuff. Mostly white papers and putting things down on paper. He ended up getting hired by the local school district and wasn't able to finish the process, but he got it started. He asked some great questions, and we had some good conversations.

Abby Elkins - Abby is Brandon's daughter. Her maiden name was Abby Moore. Abby, when she was little (10-12 years old) helped with some of the original concept artwork for adilas. Later on, she helped with content for the presentation gallery and then the adilas lite plans (fracture). Currently, she is working graphic artwork for different adilas pages. She's now in her mid 20's and has some awesome art and content skills.

Aspen Moore - Aspen is Abby's younger sister and Brandon's daughter. Aspen helped Brandon with some planning and counseling (mental help). Aspen also did some general business consulting with her dad Brandon.

John Maestas - Developer, backend server guys, and designer. John came to us through Dustin. John was uses as a jack of all trades on the backend and frontend. He did numerous projects, documentation, payroll, and page redesign projects. John was also very help to Brandon in working on the notes and comments on the SWOT analysis document. Many other projects as well. Good vision of the future.

Kiva Berkenkotter - Steve's wife. She helped Steve with various projects and planning sessions. At one point, she was in charge of paying commissions and collecting monthly reoccurring payments. Huge supporter to Steve!

Heather Moore - Heather is Brandon's wife. What a trooper. Cheerleader, support, ideas, and consulting. Huge asset to Brandon (me). Thanks Heather!

Jonathan Wells - Designer and mock-up guy. He helped to map out the system and created a number of deep mock-ups for adilas lite (fracture) projects. Great job catching the vision and putting those pieces into a visual representation. We still refer to his work when talking about fracture (future project for adilas).

Jonathan Johnson - Business consultant from Epic Enterprises. Met with Brandon and Steve in end of 2019 into 2020. Really helped us see some needs and opportunities. Later, helped Brandon with some other consulting when trying to define the fracture plan.

Calvin Chipman - Windows software developer. Calvin also did a bunch of web-based work, database stuff, label printing, and API socket stuff. Calvin was the first developer to use the adilas API's to create a native mobile app for a client. He also built a number of special developer tools used by some of our team to speed things up. He's the tool guy!

Cody Apedaile - Bryan Dayton's cousin, Cody helped with a bunch of JavaScript code and changes. He also spent some time working on the UML diagram for the adilas database. We didn't get things finished, but he was working on a new build your own interface (custom to you) for adilas. We ran out of funding. We want to get back to that project at some point.

Dave Forbis - Dave was the official "high tech gofer". He did a bunch of things. Graphics, project management, brainstorming, planning, sales, and helped with managing developers for the adilas shop. He was another great student. He came to a number of training courses and brought so much to the courses. He was also a big support to Brandon during some rough times.

Josh - There are three Josh's. Josh Wheeler, Brandon's friend and developer. Josh Sagert, developer and adilas user (worked tons on the discount engine), and Josh White, Steve's friend from California. Josh White has brought us a number of bigger leads and bigger players, like franchises, and other higher-end clients. Anything recent is Josh White, from California. He helps with networking, sales, and dreaming of new things.

Suzi Distelberg - Sales, training, and deployment. She also worked with some custom projects and doing step-by-step user guides. She has helped with all kinds of projects and even gone onsite for setups and training. Great asset!

Kelly Whyman - Kelly is Dustin's wife. Kelly was single handedly the best independent sales rep that adilas had. She did training, consulting, and sponsored a number of custom projects. Kelly helped Steve and Brandon with reports, functionality, and other things. She got so good at things, state contracts snagged her up to work at state and multi-state level stuff.

Molly Hennessy - Molly was another independent sales rep and consultant. She had numerous clients and got into doing SOP's (standard operating procedures) and other high-end documentation and training. Molly was an entrepreneur and even started creating some of her own product and services. If you search adilas on google, some of the other results are from Molly. Super creative and a great consultant.

Hamid Karbasi - Developer - He has worked with Brandon doing small websites, training, and small tasks. He currently is a manager at a retail store and brings some managerial type skills to the table. Willing to talk about concepts and how they apply to retail and other environments. He is also lightly helping with some planning for fracture.

Gene Spaulding - Friend, entrepreneur, and businessman. Gene is an old college friend. We had a number of friends in common. He has been a small mentor to me over the years. Way back, before adilas, he helped me get my first business loan for a project that I was working on.

Sharik Peck - Friend, entrepreneur, public speaker, physical therapist, and businessman. Good influence and mentor in ways. Sharik and I used to exercise together back in the day. Many of fun walk, run, and weightlifting session. Learning some conference and training skills from him and his wife. They have done really well pushing their product lines and doing some marketing. Trying to get some ideas.

Bridgerland Technical College - Use to be Bridgerland Applied Technology College. Not a person, but a huge help. This is a local technical college in the Logan, UT, area. Brandon's dad, Wayne, worked there. Tons of assets. They provided classrooms, training options, computers, and even an small incubation spot (starter office space) for the adilas shop during the startup phase. Huge asset!

McCorvey's Pro Shop - Also known as Bowling World. Client that had multiple locations. The started out with around 30 and grew up to the 90+ location level, all using adilas. Long time client.

Emerald Fields - They were the first client that wanted their own fully dedicated box and server. They had multiple locations and requested some custom code, reports, and features.

Beaver Mountain Ski School - Client that we helped them track their ski school (snow sport) lessons. Students, instructors, classes, and schedules. Custom interface dealing with elements of time and flex grid.

Bear 100 - This was the first event or annual event client that we did. They used the system for about a week each year. They had 350+ runners and their families that would be on the site for multiple days straight. It was a 100 mile running race with 13 aid stations and a small social portal for the family and friends to watch their runners. This one was special as it had custom input options to upload CSV files to populate the database vs normal HTML form field entries. Records were sent in batches from remote places to adilas for storage and race progress.

High Valley Bike Shuttle - Online ecommerce and scheduling client. They also have a cafe and small retail store. Fun online scheduling and bulk flex grid projects.

Herbo - Mike Roundtree, owner of Herbo, was the first company to do a small white label of adilas. Mike has been a great asset to Steve and the two of them have worked on projects, plans, and dreams. Herbo also has a custom payment solution that they are trying to market and get rolling. Mike has been a great supporter for years. He is also a certified CPA and that credential helps us and him. We would like to get other CPA's on board as well. Thanks Mike!

Nxtlinq AI - AI assistant. These guys really pushed us to get an AI agent inside of adilas. Tons of development took place and lots of prep stuff. We wanted to do a 3-part plan for integrating AI. 1. Teach it how to navigate using the AI quick search (check - done), 2. Teach it all things adilas. and 3. Teach it how to be clear up at the consultant type level. We only got the first phase done. Lots of other plans and such, but we ran out of funding.

Grok AI - Steve loves using Grok. He has built a number of image generation options inside of adilas. He is also working with Grok to feed it data to help with analytics and AI insight. This is not finished yet, but we may end up using Grok as an AI assistant inside of adilas. We have simple and emerging connections available right now but need to really polish things up before going live with the AI assistant options.

ChatGPT AI - We have started using ChatGPT to help with code, explanations, explore resources, planning, and help with training and flow for people and other AI bots. Currently, Brandon, Steve, Bryan, Alan, Josh, Russell, Chuck, and Wayne are using AI in either ChatGPT chat sessions or some other form of AI. We have some using Copilot, Gemini, Claude, etc. AI is actually helping in many ways. ChatGPT is a big one for use. Anyways, they are earning their place in the adilas key contributors list.

There are so many more that I can't list. Developers, users, power users, reps, consultants, trainers, clients, accountants, friends, family, and even critics. They have all helped out the idea farming process and progression. Good stuff! We couldn't have done this alone. It takes a community to do what we are doing.

Phone call with Steve after our AI meeting. Going over tons of ideas and options... Exciting times.

- On the 3rd party solutions page, add in the other API's that Nxtlinq may need to access their data. Do this all behind the scenes so that a user doesn't have to go in and turn any of those settings on. That way, all of these API sockets will be monitored and controlled via the 3rd party solutions channel.

- We can handle the user level permissions - meaning allowing a user to turn the AI agent on/off at will. The corporation may turn it on, but not all users may want it. Basically, the corp level will be the top level and the user level will be on an individual basis level.

- Earlier today, we were talking about subsets of aliases - Steve had the idea... What about multiple levels deep? Aliases of aliases of aliases... We can totally keep it all strait but what if a user does something all the time... What if the AI agent was able to make its own aliases for common tasks. Talking about predictiveness and interpreting input and intent - We even talked about slang or certain terms that may be used in different regions.

- "Adi go" - command prompt - We already have "Adi" as our little blue dog avatar (helper or mascot). Maybe using "Adi" as a command prompt. This would be similar to how smart phone users can talk with Siri or Alexa. Ours would be "Adi". Idea from Steve.

- Sell what we have

- The value of hyperlinks - mixing command line, Gui interfaces, web, and API - we are built for this

After Steve and I got finished, I was wrapping up for the day. I was really grateful that everything was going good, meeting wise, direction, etc. I was saying a little prayer and had a number of thoughts pop into my head. Call it inspiration, direction, or whatever. I'll take it and I love it! Here are my notes:

- On the user set aliases (making their own prompts), for the AI quick search prompts, what if we used a "#" (pound or hashtag sign) for all user specific prompts. That would not compete with any of our existing prompts. For example: #xyz or #something or #somethingelse... - we could even reclaim certain existing prompts by just add the hashtag in front of it. Another example may be... The prompt or keyword for clocking in/out has an alias of "my time" - what if a user wanted to use that for his/her own prompt for project time tracking. They could create "#my time" or "#time" and it would totally work. Even though both of those values are normal keywords by themselves. It could be really cool. Imagin a hashtag and at least one letter, more if needed. Super simple for quick speed.

- Be able to build and show the prompts and what they are tied to. Simple user interface to setup and maintain their own AI quick search prompts. Very similar to the icon payee top links in the snow owl theme, but even more, and easier to get to... they would be clickable and usable in the AI quick search text fields. Anywhere in the system... That would be super cool! Even better than the icon payee top links (existing link building or special button feature inside of adilas right now).

- What if we used the "go mode" page (new AI quick search prompt page) to show their own prompts or even a fracture type interface - simple tiles and buttons - (small sample image)

- When creating your own buttons, be able to name them, color them, set an icon, a link (advanced - they have to know the URL or web link) or a simple quick search prompt. Maybe even tie the user created prompts and buttons together or make it a dual-purpose database action. Some of the buttons may need to open up a new window and some (most) will just jump to that new page. Just some ideas.

- What about being able to tie multiple prompts together in a mini list, process, or mini prompt recipe? That would be super cool. Imagine something like this: start cart, choose customer, show x or add y to the cart, simple cash checkout - simple English or natural language instructions and the system would help them walk through that process... kinda hold their hand. It won't just do all of them at once, but it will know what the process should be. We could easily create those one-to-many relationships and virtual steps or phases of the process. Just for fun, it makes me think of a data assembly line or assembly line for data. Cool stuff!

- Along this multi-prompt line... We already allow for duplicating invoices to the cart. What if we used a template type scenario and setup a master invoice and then were able to duplicate the exact thing in one click. If changes are needed, they could modify it, but cut out all of the searching and such. What about a partial duplication process... once again a mini recipe for certain steps or data assembly line controls.

- We have a page inside the current system called "my favorites". It currently has a number of buttons on that page. This was one of my todo list notes from a couple of days ago... It totally fits here (see below).

todo: Get back to the ideas of the my favorites page inside of adilas... it got taken over and a bunch of hardcoded buttons put on it. But it does have some potential. See this help file - help.cfm?id=418&pwd=favorites - or visit this page - top_secret/secure/my_favorites.cfm. Added this note on 10/14/25 - it would be so cool to let the users choose anything that they want in the system and then organize it and name it. Cody Apedaile started a draw your own interface (but got pulled off of it for budget reasons). Anyways, the goal is still there to help create your own interface and organize your own buttons as you see fit.

-  Super simple, using old school tech with a modern or new school flare... it will work

- What about helping with memory... We could help hold small comments, save/hold this or that, or even helping to string things together... Maybe help them with their memory... It won't tax the server very hard (store simple things in session - per login). Imagine small AI quick search prompts like clear memory, save to memory, view memory, etc. Super simple stuff. Use JSON storage if saving memory in a more long-term fashion. Simple interface to get things in/out of memory and even use the AI quick search field to help. That would be cool.

- This may not be ready yet - but what if we record and then help them go from one thing to the next to the next... simple session memory with a display... If we know a series of AI quick search prompts... It wouldn't be that hard to display something with a next button, help them step through the process.

Working on more AI options and prompts. I have a small list that I would like to add and make happen. See EOT # 12286 in the shop (private).

On a meeting with Steve. We went over the adilas mini API and the new AI filters (sub filters within the main filter). We then talked about some proposals. I was pitching for some guys to help us out and work on specific projects. There were three code masters (Calvin, Brian, and Cody), maybe give them each 1% of adilas, plus $20K to cover (3-4 months). Just some thoughts. Steve wanted to know what they would be working on. I showed him the ship A MVP list that I have. Talking about how AI can help with training. That would be so awesome. Going over adilas lite and I showed him that we have the first 4 done. We also set a rough goal of putting adilas, llc percentages up for sale as of October of this year. Trying to generate some capital to keep pushing things forward. Other talks about projects and AI stuff.

Working on gathering information for a letter of recommendation for Cody. He did a great job and worked for us for about 6 months. The only reason that we had to stop working together was because of budgets (tight). We would love to have him back if possible. Just for fun, here are almost 80 entries in the developer's notebook where I was working with Cody. Lots of good stuff. Click here for the link.

Meeting with Bryan. He had an older branch that had multiple merge conflicts. Going through that process. We had to get his local box up to speed with new environment variables and settings. We ran out of time to do the merge conflicts on the old branch. We will do that at a later date. We then flipped over and did some more work on getting Bryan's local machine up and running. After that, we looked at Cody Apedaile's checkwrite and label builder code. Bryan wants to use some drag and drop functionality to build out a restaurant interface type environment. Bryan and Cody are going to be working together on that project.

Meeting with Cody. He and I were working through a small transition. I'm going to be taking over on the adilas label builder project. Cody is going to be activity looking for a new job. I wish it wasn't so, but it all deals with budgets and funding. Anyways, I also need to send Cody the check stubs for the last few entries (for his records).

We spent some time going over pages, instructions, and passing todo lists back and forth. Cody has been working with us for the past six months. We have made some great progress. Good stuff!

Talking budget stuff. Then going deeper into the adilas label builder. Working on getting deeper into line items for the label builder. We already have all of the main 12 players, at the top or main level. Next, we will be getting into the line item levels. Lots of talk about getting the interest level built up for the label builder. Basically, we want to get people excited about using the label builder and then actually using it. The more they use it, the more feedback and changes we can make from their requests and feedback.

We finished up our meeting by making plans to finish up some of the MVP pieces for adilas ship A. We have a few things that are really needed to make it all work.

Working with Cody on his UML diagram stuff. He had some questions. We went through things and answered his questions. We were talking about the complexity of building a home and possible analogies as compared to building out a fully integrated ERP or POS system with CRM, CMS, payroll, ecommerce, etc. It can get pretty complex. Cody and I were talking about the importance of planning. There is a growing need for standardization. Planning for growth. We want to get out of the patch jobs and into growth and development. He sent me a small graphic (screenshot) and the original authoring file of his current progress on the UML diagrams. They are uploaded into the shop media/content files.

After our meeting, I went in and cut some checks and recorded notes.

Working with Cody on mapping out the database for his UML diagrams. Somewhat of a small work session. He would ask about certain fields and I would tell him what they did and how they were used and/or related. We would then move on to the next piece. If he didn't need me, I was working on my own stuff.

Emails. Back on the CSV upload with mapping options for parts and items. Added the upload code and did some light testing. Pushed file up to all servers. Sent out an email to Sean and Cory to let them know how to use it. After that, I paid a few bills and cut a couple of checks for Cody and me from inside of adilas. Quick phone call with Sean to go over the new tool.

Meeting with Cody. Going over UML diagrams that he is working on. Talking about efficiency, reuse, pros and cons of copy and paste, pros and cons of duplicating data, and math on the fly or precalculated math. Lots of good topics. Here are some of my notes:

- The importance of refactoring. Keep refining and paring things down. Make it smoother as we go.

- Talking about mini conversions and other options. Mini conversions is a sub of sub inventory (parent/child inventory). For example: Say you have something that gets sold by the case, by the bottle, and by the fluid ounce. You have to be able to go up and down the conversions to show what is really there. True inventory tracking.

- Talking about lots of suggestions and what makes sense to change out and/or leave.

- On the mini conversions, we might be able to hold the conversion id's and the math all on the same table. Help the users setup the conversion charts and/or relationships. Especially if we don't know the conversion factors or ratios (custom conversions or custom units of measure).

- We have had a lot of wild west style development (anything goes). There is a need for specific roles and company structure (adilas jelly fish model - future plans for where we are heading as a company).

- We mix so many different business verticals. That has been a huge blessing but also a small curse (so diverse).

- Cody was pitching that we need a primary role of a database admin type person (specialists per role). Creating the chain of command, down the different roles. Basically, turning the wild west into a more modern city (modern development environment).

- Talking about someone who knows how to work really hard and how to help them to work smarter and use technology.

- Cody wants us looking into growth, in the long run. Talking about a master plan and then breaking things down into more digestible pieces.

- Talking about internal education and structure. We need our team to know what to do and how it (all of the pieces) fits with the bigger picture or the whole.

- Figuring out what we have, suggestions for what to change, and future plans.

- We then got into time sub inventory and parent/child relationships. It gets deep, pretty quickly.

- Growth is hard to manage sometimes.

- Talking about independent developers, light guidance, and working on our own. Reasons for building out the UML diagram. Not just for Cody but for all other developers who will be working on this project.

- Building out the dream. Getting organized (not really official, but pretending that it was official). It will all help in the long run. Risk vs rewards - push/pull in the organization. Unofficially organize ourselves (at least on the development side).

- Link to the interactive map - small visual for how things are organized.

Meeting with Cody. Spent the whole time going over the adilas database. He is mapping things out and had a number of questions. We were looking in code, looking up tables, checking relationships, primary keys, foreign keys, lists, dynamics, etc. Good work session. As we went through things, he is also starting a list of suggestions and ideas on how we can restructure things to help make it more efficient and flow better. I was encouraging him in those efforts. We also briefly talked about where we are headed and some of the overarching goals of the adilas system. One of the upcoming needs will be graphical homepages with quick stats, summaries, graphs, and charts. I have a bunch of other notes on graphical homepages (over the year) by clicking here.

Working with Cody. Going over his UML diagrams (using drawio - an online drawing tool) to map out the adilas database. We then flipped over to the latest build of the adilas label builder and did some code review. We merged in some files. He then helped me with some CSS debugging on one of my projects.

Talking about making some UML diagrams for the adilas database. We spent a bunch of time talking about databases and all of the interconnected relationship (just for parts, PO's, invoices, and sub inventory). For me, send Cody all of my old database docs (take the time to get him the correct info - ended up finding a few back from 2016 and 2017 - they had been uploaded into the adilas shop media/content folder - do a description search by database and set the dates back to 2016 to 2017).

We also spent some time talking about banking hours and how that works (paid time off or future payout options). We then got into working on permissions inside of the label builder. We went through a bunch of stuff and added some light permissions to the label builder home page. Good work session.

Cody is wanting to help me get some of the older projects done that have been on my tick list for years and years. I'm excited about that.

Emails. Quick meeting with Cody to look at his code. Ended up debugging a small database update to total up the sub date/times for all existing records. We pushed up the code and then talked about some of the next steps.

Meeting with Cody. Trying to figure out the next phase or part of the label builder project. We recorded some notes and plan on doing some security stuff on Wednesday morning. We talked about using the buddy system to get through certain projects and help with motivation. I sent him over a whole bunch of my little todo list items. I helped him get some small bugs fixed, that I knew how to fix (based on older files and custom includes). Small work session.

Meeting with Cody. Looking over his new database queries (lots of left joins) on some of stock/unit queries. We then looked at the bug we were working on Monday. He got it fixed. It was a case sensitive thing with JavaScript. Pushed up a bunch of code. Then, Cody, helped me fix a bunch of other small JavaScript errors. One of the ones was dealing with a bounding box issue (imposed margin of sorts on a page). You could see it (a form control piece) but couldn't interact with it. We got that fixed and a couple of other small issues. Small work session.

A couple of days ago, I had a small dream about using the adilas label builder to help people market and sell their products. Nothing too special, but I wanted to record that I was dreaming about it. We are currently on version 3, made by Cody Apedaile. The code is live but we haven't really had people go in and start working on it yet (testing and playing with it). The new label builder is pretty cool and has tons of potential. I'm hoping that we will have people in playing with things and building labels within a few weeks. It is currently at a MVP type level. We have a number of other things we really want to do with it, but it is coming.

Just for the record: The adilas label builder - version 1 was done by Calvin Chipman. It was a standalone Windows app that connected to the backend adilas database through an API. Really good product but it was limited to Windows.

The adilas label builder - version 2 was also done by Calvin Chipman. We wanted a more open web version. He subbed some of the development out in order to make a JavaScript or web version of his original product. It ended up costing quite a bit and we basically ran out of funding. It only got part way done. We were planning a revamp of that code - version 2. After looking into it, we decided to take what we liked, and build a whole new version.

The adilas label builder - version 3 incorporates a new label homepage, a build new interface that is super flexible and powerful. It can handle static text, dynamic text, rectangles, circles, images, barcodes, QR codes, layering, stacking, and other cool dynamics. This is probably way too big, but here was an internal demo that we did back in December of last year (12/2024) to show off the label builder. Anyways, it is looking really good. I can't wait to help people use it and market their stuff, items, and products.

Meeting with Cody. Going over progress. We were going to send out an email asking for feedback on the new label builder (to our internal crew). As we were typing up the email, we ended up looking into a small bug that I had found. That sent us off on a tangent and we are going to be refactoring some code before we ask for feedback. The error was dealing with the main save button on the label builder. It was really saving things, but it was showing an error. We were having issues with the CDN (content delivery network) and browser caching issues. We could change the actual JavaScript file and then have the server pull it in, but it wasn't being fully pulled into the other areas. Some light struggles there. We even tried a few work arounds. We ended up that Cody will look at it deeper and we'll get back together, once we have a plan in place or working.

Zoom meeting with Sean, Bryan, and Steve from the adilas team. We were meeting with Cody from Alliance - a civil engineering division out of northern Utah. Going over project time tracking and invoicing. Permission templates.

Small idea from Cody - be able to flip flop subs of time from the main elements of time to other elements of time. For example, say your guys are clocking in/out on a certain project. They make a mistake and it, the timecard, should have been on a different project. Currently, you have to make that record inactive and copy/paste the info to the correct spot. They would like it if you could just change the main time id (project id) for the sub and then it virtually gets moved to the correct spot. I made some notes on my to do list, on my computer. Great idea!

Emails. Then flipped over to the branch that Cody did to flip the list find and list contains functions. We are trying to use the list find functions, as they are tighter and produce more controllable output. Going page by page and looking at code and files in his branch. Adding modified logs and doing light clean-up. Did three different sessions on this bug fix today. Spent from 9:30 am to 11:30 am, 3:30 pm to 4:45 pm, and 6:15 pm to 7 pm. 4 hours total.

Meeting with Cody. Going over the PDF reader code that he wrote (parsing and stripping out data values for tax withholdings). We then jumped over and started looking for a new project for Cody. He ran a global find and replace for the list contains vs the list find functions. I need to check that out and get it all merged into the system or the master branch.

After that, we switched over and he will be working on the total time for sub dates and times. I showed him some existing payroll stuff and we spent a bit of time looking around and finding the different pieces of the puzzle. His project will be in the sub dates and time, not in payroll, but they are similar (calculating total time). We also did some just in time project management (our specialty) and planning. This project was started by Steve and Eric last March of 2024, and it is already 3/4 of the way done but it needs some light detail work. I'm hoping that Cody will be able to follow things along and help make it just a little bit tighter, which will allow us to fully use it better.

Payroll updates. Got a digital file from Cody Apedaile. Took the values and started working with them. The goal is to take a PDF file (from the pub-15 from the IRS), convert the PDF table data into a CSV (Cody did that), then use that CSV file to build database update scripts. Spent lots of time prepping the excel file and moving data around.

Working with Cody. He asked for and needs a focus. We went over some of my todo list stuff. Custom PDF's, paperwork, payroll stuff, parsing text documents, etc. Talking about percentages and inviting Cody into the adilas MMLLC (multi-member LLC) co-owner family. We over what that means and how it works for taxes. General stuff.

Quick meeting with Cody to touch base and setup another meeting. He is working on the infinite scroll stuff.

Meeting with Cody. Going over the infinite scroll stuff. He was showing me some of his code. Doing some code review on the label builder. Working on new help files for the label builder. Making plans for our next steps.

Various meetings, throughout the day.

On a Zoom meeting with Cory. Looking over some gram control settings.

On a meeting with Cody. He got a few things tweaked for the check write stuff. Looking at pagination on the label builder. He was also showing me some work that he was doing on the infinite scroll (scroll, get more results, scroll, get more results, repeat until finished).

Working with Steve. Debugging things. Found problem with list contains vs list find functions. Pushed up the new file.

Emails and reading over a response from Chuck about a custom website.

Paying bills. Meeting with Cody and Chuck. Light introductions and then some back and forth. Cody was showing Chuck some of the label builder pieces. We also showed Chuck some of Cody's other projects that he has been working on. Towards the end of the meeting, we got into some Yogen Fruz tools and needs. We even talked about bigger dashboard, visualization tools, and prediction type stuff. Chuck likes to build out a list of requirements and then make a plan. He wants me to send some things his way.

Working with Cody. Shooting for MVP (minimal viable product). Talking about what that will take. We spent most of the whole session working on pagination and going over organization stuff (where to put things). Trying to eliminate technical debt and make things as painless as possible. We also setup some more meetings for next week. We have a plan. Our next goal is to follow that plan and keep pushing forward.

Working with Cody. Our main goal today was to get in and look at the pagination stuff on the label builder app. We got in there and started to add small search and filter options to some of the search fields. We then took those values and were starting to cascade them throughout the actual searches (method calls and results). Good little work session. Cody is going to run with it for a bit and we'll check back in again on Wednesday.

Meeting with Steve and Cody. We were talking about current needs for the adilas system. Here are some of my notes:

- Going over forms, accordions, modals (popup windows), client-side validation, ease of use, dashboards, custom homepages, buttons, containers, canvases and pallets (like an artist with paint - a pallet or possible colors and tools), asynchronous loading, preset pages that load certain things, sizing things, moving things around, etc.

- New custom homes... Imagine using the new drag and drop interface (what Cody is working on) and then be able to swap out our homepages (existing homepages) with new custom home pages (built by the users or as an industry specific skin or white label). Eventually you could do lower-level pages as well. Think full custom... for the whole system.

- Getting Chuck involved, right off the bat. Chuck is the frontend designer. Responsive design (phones, tablets, and other devices).

- Where we are heading... not just a new label builder, we are building packaging, designs, full layouts, etc. Steve was saying that if we offer a custom and internal solution, we could potentially help with overcoming minimums on custom design layouts and print projects. Almost like a print shop. Making dynamic graphics. Making packaging with the correct information right on it, just making as many as needed. Basically, you could skip the full packaging and then adding a label on top of that. If people want to print other things... then let's talk about it. This could be making gift cards, employee cards, custom packaging, 3D printing, etc. Not just for labels, it could be for more.

- Light looking at sheets and sheet labels. We want to launch an MVP (minimal viable product) and then sort of tease them (our clients) going forward. help them catch and see the vision. If you can give our clients a vision of one, they can see the possibilities of doing thousands.

- It's all about efficiency, ease of use, helping them get into the correct direction. We talked about galleries and ways to add the data (whatever that is) to the different things or places. Almost a bunch of options and pick and choose what you want and how you want to organize your data.

- I will have the responsibility of hooking up both Chuck and Cody. Letting them get together to go over some gui (ui/ux) stuff (graphical user interface or user experience stuff).

- Steve was talking about how so many people have tons and tons of photos and helping them organize them (in bulk). This was just an idea. It's just data and some management type things. Maybe some bulk galleries with notes, flags, tags, and ways to organize things. It's all just data... print it, organize it, share it, etc. More talk on flagging and tagging items.

I thought that it was a great meeting. Steve and Cody were having fun and doing some great brainstorming stuff. I was chiming in every once in a while, but it was mostly Steve and Cody. Super fun!

Meeting with Cody and Alan over a GoToMeeting session. Alan had to join us by phone. We were talking about teams, budgets, and vision. Here are some of my notes:

- Frankenstein computer project. Mixing and blending different styles and such.

- Specialists and filling in the gaps (in our teams). The ideal would be working in Parrell vs just one person on a single project.

- We would love having a known frontend designer. We do have a guy, Chuck and Piper, but both are only doing less than 10 hours a week. We need someone full time.

- Small teams of two

- We spent some time talking about timing, when to push and when to chill.

- A real need for direction (a goal and vision). All going together towards that goal.

- Eye candy, graphs, charts, buttons, containers, widgets, and such. Helping people to get more info graphs and quick summary information (dashboards).

- Sometimes, cool isn't useful... to certain people. Cool can help sell things.

- Cody was talking about adding graphs and charts to the custom homepage builder. That would be super cool.

- Finding out what would be beneficial to our users. Fill in the gaps. Ease of use to help train people. Seeing information, counts, and summaries quickly.

- Talking about visual homepages for all of the main players.

- From Alan - eventually using web sockets to show real time data and changes.

- Ideas on new homepages... we could take all of the old ones and turn them into an old or basic home, add new graphical homes, and maybe the last 15 entries of the data for some super simple home pages.

- Focusing on manager type tools. Top paying customers, group counts, bestselling products, busiest times, etc.

- There always seems to be some stress over money and budgets.

- Cody was grateful for the time to meet with Alan.

Alan had to drop off, we (Cody and I) then switched over to the adilas label builder and talking about direction and eye candy options. We are going to try to help focus on some tools and visuals for manager's and help them save time or feel like adilas gives them some time savers... One of our main goals is helping people out.

Recording notes from the day. General clean-up stuff. Ordered a Dymo label printer and some labels for Cody to help do some testing. Emails out to Alan about meeting with Cody and I to go over things.

Meeting with Cody. We spent the whole session looking over the label builder and figuring out a tick list of where we are heading next. Lots of planning and talking about getting organized into teams. See attached notes for some tick list items and priorities.

Phone call with Josh about ecommerce. Emails and light tech support. Looking into a new fix from Cody on the check write system. Pushed up new files.

Fun new tools and toys demo. We had Cody, Shari O., Bryan, and I on the meeting. We went through the new check write settings first. After that, we got into the other main projects that Cody is working on. We spent some good time going over the new adilas label builder (v3) and the new custom homepage layout tool (fracture/adilas lite stuff). Check out the attached video, if you want to see things. It's about 52 minutes.

After the meeting, Cody and I pushed up some new changes and did some light testing.

Meeting with Cody. Went over a small bug on the check write settings. We then spent the whole time on the label builder. We pushed up some new code and did some prep work for the demo this afternoon. We are inviting some of our team members to see what we are working on - Cody's projects - check write settings, custom label builder (v3), and custom homepages and customer interfaces. Should be a good meeting.

Meeting with Bryan and looking at his cost plus code for adding items to the cart. Following logic and making some small changes. Did some code review and deeper checking on certain pages. Merged in new code and ran database updates on all servers.

Small preview of some of the other projects that we are working on. Showed him some of Cody's stuff (drag and drop, build new, create custom labels, check printing layouts, and custom homepages). I also showed him a few new settings for the mini scan cart. We also talked about ways of creating quick preset settings to help configure applications without all of the training on how to do it (settings - but done with speed and in bulk).

Meeting with Cody. We spent the whole time going over small tweaks and testing the check write and check printing settings and features. Small tweaks. Most of it was pretty tight. Great little session. We pushed up the new changes to all servers.

Light testing for Cody. Looking into some formatting for prices, cots, and quantities for labels. It gets pretty deep. Playing with new check write features.

Prepping code to help merge stuff in for Cody. Looking at database updates for the label builder (v3 or version 3) and the new check write app. Running database updates on all servers. Recording some notes.

Meeting with Cody. Went over the check write application - new code and changes. Light debugging and testing. We then switched over to the label stuff. We were going back through those pieces and working on small to do list items and doing some code review. Great little session.

Meeting with Cody. He was showing me his custom home page builder. Super cool drag and drop interface stuff. We then talked about copying things - private and public options - for buttons and interfaces. Lastly, we spent some time looking into the default homepages and how we could use these new custom homepages directly inside of the choose interface page.

I texted Cody and we will reschedule. I was sick today.

Meeting with Cody and doing a code review on his branch (CA-check-print-dev) for the check write application. We did some database updates, code review, and fixed a few small bugs. Some of the bugs were from older code but we just now found them as we were in there testing. Good work session.

At the end of the work session, Cody showed me his progress on the build your own custom homepage interface. Drag and drop, buttons, containers, etc. He is just getting started but it will end up being super cool.

Meeting with Cody. Going over new changes to the label builder. He added in circles and rounded corners for rectangles (drawing shapes for labels). He also restyled it to the snow owl theme colors and look and feel. We then spent some time talking about building out custom pages and how that might look and work. He will be working on a small prototype, and we will get back together to see what he has come up with.

Meeting with Cody. Going over the adilas check write app changes. He has the main bank check settings, the print individual checks interface, and the logic done. It is getting close. We ended up adding eight new columns to the check specs table to allow users to move some of the placeholders around on the check. These placeholders are things like logos, bank info, corp info, and check number fields.

We also looked at the adilas label builder, and I showed him my progress on doing the final code review on that project. We are going to tweak a few things with the builder layout but it is also making great progress. I really want to get these tools out to our users so that they can start being used and we can get some feedback. That's important.

Code review on Cody's v3 adilas label builder. Going over changes and flow.

Code review on Cody's version 3 of the adilas label builder. Light research, pulled down the code, and started going through things. Poking around a little bit. Ended up getting pulled off of it for a phone call with Steve.

Emails, phone calls with Bryan - helping him get his local all setup, paying bills, and other general stuff. Meeting with Cody to go over his changes on the adilas check write settings for banks and check printing. It is looking good. We touched base on some other projects, and I told him that I would be doing some code review on the adilas label builder this week.

Recording notes from last week. Meeting with Cody, Wayne, and Alan. Going over progress and new interfaces ideas and options. We then let Alan and Cody talk about API sockets and how to set them up and use them. Tech talk stuff. They got into some deep topics and Cody was asking for some samples. Both Wayne and Alan were chiming in and giving him tips and pointers.

Meeting with Cody. Going over a small bug in the check write settings. We ended up spending quite a bit of time there and making a pretty good plan. As we were talking, Cody was saying "Being clear in communication makes a lot of difference." He helped me format my notes better so that it wasn't assuming things, they were clearer, and it was all spelled out so that anyone could have read it.

After we finished up with our plans on the check write bug, we switched over and started talking about custom responsive web pages and a custom interface and navigation builder. That sent us off to talking about good visuals, eye candy, graphs, charts, and custom components. We then spent some time talking about API's and how to connect to the API sockets internally. Basically, getting the data from the database and mixing both server-side and client-side languages (code). I'm going to set up a small meeting with Wayne and Alan to make sure that we are all on the same page.

From Cody - If you provide good visuals and have good structure, that is good story telling (meaning, we can help tell the client and user stories better by having in those visuals and correct formats). I liked how he tied it into story telling or digital story telling. That's where we are headed.

Paying bills. Jumped on a meeting with Cody. We talked about the adilas label builder. We are going to work on it on Wednesday to see if we can get it ready to push up to let people start playing with it. We then looked into some other projects. We looked at a check printing bug. Cody is going to look into that.

Next, we then looked into what it might take to build a create your own interface type model. Lots of drawings and talking about options and plans. I sent him the link for where we are headed, based on the some of the adilas lite videos. See this page for some videos: https://data0.adilas.biz/lite/adilas_lite_videos.cfm

Meeting with Cody to go over the changes for the adilas label builder. Going over the JavaScript drawing functions. Tons of them for lines, boxes, corners, rotation handles, basic text fields, text boxes (multi line), images, etc. We also went over his dynamic search and view functions (actually showing the labels). We ended up talking about the image search functionality stuff and light debugging there. He is making progress. His JavaScript stuff is really tight and great. We just need to spend some time on the ColdFusion and database side of things to really make it smooth and flow within our application. Looking good.

Meeting with Cody for code review on the version 3 adilas label builder. Introduced Cody to Alan and let them talk for a bit. Going through the pages and finding bugs and going over code. Deep code review of his project. We went through a bunch of pages for both ColdFusion and JavaScript pages. Looking good.

Meeting with Cody. Going over progress on the adilas label builder page. He has got it quite a ways along. We need to do some major code review, but it is looking good (ish) - just needs a little bit of loving. We will meet again on Wednesday for a multi-hour long code review. If we need more, we'll book more time.

Quick meeting with Cody to see progress and answer some questions. Cody is still learning the system but getting much faster. He was showing me some local filters based on JavaScript stuff for showing certain page results. We talked about next steps for the label builder. I told him that I would get him a list of dynamics (text placeholders) per application type to help with substituting or swapping out dynamics (on the labels) with real data.

Meeting with Hamid. He is working on a budget tool. We went through things and tried to get his local files back on track. He had been spinning his wheels a bit and needed some help. Part of that is learning. We spent the whole time going over code and team coding on his little project. I sent him a small sample of some jQuery stuff that I made for Cody. Hopefully it will help. He is going to review it later this week and first part of next week.

Went up to Bryan's house to take him a label scanner and Dymo label printer. We got it all setup and did some practice prints and what not. I also had him jump onto Cody's label builder branch (new code project) and look around a bit. I'm going to have both Bryan and Cody do some co-coding on that project.

Working with Cody on his label builder project. We jumped on the GoToMeeting session and passed code back and forth (pushing and pulling) to do some local testing. We had to install some Dymo label printer software and play around with that for a bit. We made a few changes and talked about next steps. I'm going to connect Cody and Bryan to work together a bit. That should be a good match.

Helping Amber (my daughter) with some of her organization of the printouts of the adilas developer's notebook stuff - physical printouts of the elements of time with planning, brainstorming, and other notes.

Meeting with the Lucky Puppy or Puppy Palace folks (dog nails and grooming service). They are looking for a multi-relational pets to owners, pets to techs, color based key, and tons of other things. I showed a small demo of the backend code and where we are at with things. They wanted to know where we are heading moving forward. They are a potential client and we are looking for ways to help them out and solve some of their problems. Suzi recorded the last half of the meeting when they were showing us some of their needs. These are some of my notes:

- As a disclaimer... I went back through the video and refined my notes. Original meeting was on 8/22. I rewatched the video on 8/26 and added a few more notes on 8/27/24. We already have a ton of these pieces. This meeting was to show us what they are wanting and needing and how we will need to put it all together. Just guessing, but I'd say we have 85% of all of these things right now. We just need to tweak a few things out, make some plans, add some new settings, and alter the flow a little bit here and there. That's awesome!

- Choose a customer, choose a pet, choose a service(s), choose a color, choose other assistants, check in/out, create a cart, manage the tips (split tips - they really want this... this was huge). Be able to copy the booking and rebook it (docking and rebooking). Email and text message back to the client. That's kind of a summary of sorts.

- Be able to edit the cart and add discounts during checkout

- 100 appointments a day - phone calls, changes, super-fast paced

- Show cancelations - what was there - They like to see what has changed, moved, or been canceled

- Adding a new client and making it quick - currently, they are using first name, last name, cell phone, email, and zip code. Be able to add more if needed. We have tons of settings there already.

- Notes on pets ... name, type (breed), age, size, up to date on vaccine, does it bite? etc. - thinking about flex grid tie-ins or a custom table there. On the notes and records for the dogs, maybe group things and then allow a subset to be shown. Go from simple groups (say per pet name) to more complex, everything tied to that pet.

- Each service has a time (block of time) associated with the service - there are some pros and cons to that approach. Anyways, just making a list of things that they were showing us and asking for.

*** Fast... they love drag and drop - They would love to be able to easily drag and drop and edit a time slot (length of the appointment - longer or shorter) all done through drag and drop.

- Making the appointments, changing the appointments, etc. - planning for the next step

- Major color code key - they are using multiple colors - each one means something - allow them to set up their own keys and values and colors.

- Tie-in the monies a little bit tighter - they would love to see it more or better - currently they are using multiple systems and then running the cards on the side. They would love to see it all tied in together better. Ideally, they are wanting a mix of an integrated scheduling software package, CRM (customer and pet relationship management), full POS (point of sale), ability to mix both products and services, and manage the money part of the puzzle. Sounds like our kind of game.

*** Tip splitting is huge... keep track of things... tight - reporting the tips split by person (by tech). Help automate this for them. Currently, they have to do it manually. This feature is big enough that it is a make-or-break level feature.

- They are having a problem with tracking their dogs... and having to read the notes for each one, over and over. They need the multi-relational database between owners and pets. We want to really help make this nice. I was originally thinking flex grid tie-ins... We may want to look into a way of doing sub queries or special grouping to make it smoother. We could also do some sort of custom table or custom joiner table.

- Being able to see the whole picture... they need techs, time slots, rooms, services, and needs (client and pet needs). All tracked in one place. Fully customizable - show simple to more complex.

- Alerts on the appointments - little flags - possibly even color-coded tags and flags

- A 3D view of the techs, the rooms, the appointments, the needs, the conflicts, the crossovers, etc. - that would be super cool - just an idea

*** Email and text messaging - app messaging - they really want normal text messaging including conversations back and forth. Here are a few other things related to text messaging needs: - Send message when booking the appointment, send reminders - multiple, send appointment confirmations - auto and manual, send booking reminders - some of their appointments are booked out 4-6 weeks in advance. There was also some talks about sending out auto emails for different actions or steps. Those would need to be defined.

- Switched to a different software package - They started showing us "Rosy" (used for 8 years - lots of data and history) - this is a human salon based software package. Part way through, the switched and showed us a dog or pet care solution called "GrooMore". They, the client, currently used Rosy in one location and the GrooMore software in another location. They are looking to get the best of both worlds. Ideally, we, adilas can come up with a mix and blend of both and become/be used as a newer or custom software option.

- They would like customizable enterprise - multi-location controls and flow of data, pricing, processes, reporting, etc.

- There are going to be transition strategies that need to be involved as our relationship develops. They want to keep going, with minimal issues, get back data, and make it all smooth. At some point, depending on what we can show them, we may need some transition strategies.

- There are too many appointments - a glitch could really be a problem - high volume

- They would like the option of seeing the last service, if known, per client/pet

- They want the appointment to hold all services and all assistants vs each service being its own appointment and each helper being its own mini appointment. More relational database connections.

- Their customer and service look-ups were really fast - asynchronous calls - like ajax or dynamic select or predictive text searches

- Be able to set settings for future interactions - what they normally get - be able to save that (speed things up by saving choices per customer and per pet)

- They need both owner names and pet names to show up on the view - They also want to see both names, client and pet(s), along with all services (cart line items), as well as other assigned flags per appointment. These would show up on the rollover or mouse hover action (aka the popup or rollover popup).

- They are constantly checking the schedule (visual display) to make sure all is well - help them out - simple look and feel with all of the details under the covers.

- Simple to add the other assistants - some appointments require 2-4 extra techs - make that quick. As a side note, the main appointment may be for a certain time and the assistant may be for a subset of that time. All tied to the correct pet.

- Showing conflicts - on the fly - both from calendar view and through a setup flow

- Showing the scheduling for any other assistants. Along with that, booking multi-staff appointments and then making sure that things stay tied together.

- Simple process (how long - in minutes) - add the drag and drop (super cool). Allow for both manual changes or drag and drop changes.

- Docking - saving or moving things - everything that is attached (all attached) - be able to move or put in the holding queue (session or memory) and then pull that back out when ready. Even having multiple things in the memory queue if needed. That would be cool. If needed, we could reuse quotes as a template of sorts. We could also allow for multiple things to be put in the queue. Kinda like a multi copy and paste board of sorts. You just get to manage it (really simply).

- Confirmed or unconfirmed appointments - checked in/out, paid, etc. - different flags and colors per appointment

- Colors - new dogs, bite risk, etc.

- Be able to book multiple staff members at the same time

- Multi-level sliding modals to add things - pretty slick

- Birthdays - it is nice to be able to just put in years and months and back figure the birthdate (help them out). Allow for either a real birthday or back figure based on the approximant (years and months combo).

- Being able to add tags for clients and tags for dogs - each their own tags and flags. Each tag gets a name/title and a color.

- Medical issues and comments - be able to add/edit

- Vaccination records - tracking that info

- Vet info - doctor info and such

- Dashboards

- Conversational text messages and using a huge texting tool

- Intake forms - QR codes or links - they add their own documents or forms (confirm and accept forms) - let the clients put in their own details. These client intake forms would be handled through the ecommerce or client portal section of the application.

- Quick jump from day to day, week to week, and month to month

- Notes - intake notes, appointment notes, ongoing list of notes. Being able to search and filter notes as needed.

- Be able to add/edit the tags per person or per pet

- Being able to search clients or pets by the tags. Thinking flex attributes for this.

- They are doing some mobile on-site appointments. They want to pull up clients in that area to say we are in the area. They like to tag their client's general location (area) to help with targeted marketing efforts.

- Bulk text messaging based on filters or tags - batch send out things based on applied filters of the larger record set.

- Searching by pet name and then finding the client based on the dog or pet name

- Deceased dogs - dogs that have passed away - they still want to see it - maybe just flagged vs not fully deleting the pet profile.

- They would love integrated financials - in the end

- Reach out to Jen if I have other questions. Debi and her crew seemed to be pretty busy (booked).

- Just an idea, currently we allow for photos and media/content to be added to the main customer or client records. Up to 100 photos per client. Do we want to open that up and allow for sub groupings withing the photos for the specific dogs? We do allow things like this to take place for parts and general inventory items (photos and media/content for subs). Anyways, this could come later as well, if needed. Just an idea.

- Empower them on the setup and layout... Let them drive it - block sizes, what to show on the title per appointment, what to show on the hover (rollover popup), color keys, flags, etc.

*** vertical time view (a design has been built by Chuck - branch CAS-93)

- For me - claim some time - make time for it - review the video and make a plan... make sure that we have access to the correct demo site and make things flow there. Thinking about settings and putting the power in their hands - put them in the driver's seat. Wow - great meeting!

1/13/25 Bryan and Brandon meeting 

To outline what it would take in time/money to complete this project.  Then take the information to Steve and Suzi to decide if we are moving forward or putting it on hold. 

A ball park estimate without outlining each project would be at least 200-250 hours ($20,000-$25,000).  At 20 hours per week (which Bryan has available) it would take 3 months.  This project would be utilized in similar pet grooming and salon type businesses.  Currently Puppy Palace would utilize this.  At $300/month the ROI would be 5 years.

1. Vertical time view. (20-40hr project)

    a. Populate Charles' layout

    b. Already have a time slot view.

2. Add drag and drop. (done fairly quickly because time slots already exist - Javascript edit).

    a. outsource this to Cody (20-30hr)

3. Tip splitting. (20hrs)

    a. tips field exists (Eric) on the main invoices if using CC.

    b. open up so that any cart can utilize it.

    c. create a tips page.

4. Texting/email API. (30-40 hrs)

    a. Garrett/Calvin created apis with Twillio.

    b. General filtering (no "cannabis", other reserved words).

    c. They pay 3rd party directly, or pay through Adilas? Monitor and record that.

5. Flagging and Tagging tweaks (15-20 hrs).

6. Pet specific needs. Owner to pet, pet to vet, etc.

*** could be used for multiple Adilas projects.

Meeting with Cody to help him out with images on the label builer. We did some light training on using the adilas system and adding images to different places. We had to disable his full group by options inside of MySQL (database engine or database server stuff). That took a little bit. We then worked on some new code to help with the label homepage. I added in a search method and some simple output values. We passed the file back and forth and he got the new code working on his local system. Making progress.

Working with Cody on the label builder app. He was working on images and being able to make those more dynamic. We talked about ColdFusion stuff and how to use the debugger as your fiend (secret little hacks and tips). We also went over how to invoke functions and methods using ColdFusion. Along with that, we spent some time looking at how we use dynamics to search multiple fields based off of app types and generic filters (both numeric or alpha characters). Lastly, we talked about flagging code with small "todo" list items to help us move forward. Basically, hardcode things and then circle back around to make it more dynamic.

Emails and recording notes.

Various things going on. Emails, phone call with Calvin about his FTP uploader and some new changes. Phone call with Cody about using asynchronous calls between JavaScript and ColdFusion. Started putting together a small sample file of using JQuery with ColdFusion. Sent some time building a special clean-up page to help with updating barcodes and adding leading zeros (padding with zeros - dynamically - as needed to reach a certain size). Busy evening!

Jumped on with Cody to look at his progress on the adilas label builder (version 3 or v3). We built a new view/print page (just the shell) and then talked about image uploads. We also looked at some existing image reports and look-ups that are in the system. We setup a time to work on Wednesday to help push the project forward.

Working with Cody on the label builder integration. We had to work on his local install of the adilas files (development environment) for a bit. We had to replace files, setup permission, pull tables across, etc. Somewhat of an ordeal (hour and a half of messing with it). We then got him logged in and able to see the code from our adilas label builder branch (v3 or version 3). He then started working on the page to get it to work.

I was going to switch over and start working on the label homepage and what it looks like. I ended up just watching him work and providing some light feedback on layout and style stuff. He is going to keep working on it and we'll get back together first part of next week. Once he gets going, he moves. It was fun to watch.

Working with Cody. Trying to get the version 3 adilas label builder to a point to be used (going from new scratch pages to real live pages). Small work session for a couple of hours. We did some database update stuff to help control the version numbers. Then retrofitted the old code to be v2 (version 2). All of the new code will be v3. We then started to build a new label builder homepage. We got a couple of wrapper pages setup and started the process to pull in the new code. Good progress for today.

Meeting with Cody. He was showing me new mouse wheel zoom features, keyboard input (+ key, - key, and arrow keys), app types (like customer or parts), scroll (space bar drag or translating), find and replace dynamics, etc. took a bunch of screenshots. See attached. We then started talking about small to do list items and small tweaks that we can add. Talking about other needs for the adilas label builder (version 3 or v3).

Steve joined us. Intro between Steve and Cody. We were generally talking about interfaces and custom drawing needs (restaurants, campgrounds, warehouses, custom interfaces) - being able to draw the interfaces and then wire them up (links, buttons, searches, filters, actions, etc.). Tons of other needs out in ecommerce and throughout the whole system for more JavaScript type needs.

We, Cody and I, did a demo of the new v3 adilas label builder. I did a small demo and pitched a few things based on my screenshots. Then Cody did a version of the demo (live playing with the objects). Light back and forth and talking about features, advantages, and benefits of the new design.

Switched over to a request email from a client and how to help with those pieces (changes and new development). This is for the frozen yogurt place. We talked about locking down the POS (point of sale system), showing saved carts (mini queue for saved quotes/orders), simple customer interactions (search by phone number or enter as a new customer), show loyalty points, and showing what is in the cart (second customer facing screen). Lots of ideas.

After that, I showed a demo of the new discount homepage and where things are at there. We talked about plans and what not. We are going to build out the simple pages for the cart and then keep working on the discount stuff. Making progress.

Steve had to bailout to get on a demo with a client. Cody and I setup some times to work together next week on integrating the new label builder into adilas. Great meeting.

Meeting with Cody to see his progress on the adilas label builder. He can now dynamically replace things (text with database values), change images on the fly, and show one or more canvases for printing. Making some great progress. He was stuck there a couple of days ago.

He ended up making a super small scratch file to work on some fetch stuff for JavaScript URLs (web or directory paths). That little scratch file was huge and opened up a door for him to include the things that he was learning and doing into the bigger application. That is awesome. We chatted about the value of those little self-contained scratch files and how much they help in the learning process. If you build everything, all together, you can get lost by all of surrounding pieces. Sometimes that small focus is so important.

Towards the end of the meeting we talked about next steps. I got him app type id's for the 12 main player groups and we talked about making labels specific for each of the main 12 player groups. We will start with customers and parts for the first two player groups that get the new labels.

Meeting with Cody on label printing. He was running into some cross site scripting stuff. Having issues with graphics, barcodes, and QR codes being able to be re-rendered by sending things to another page for printing. We looked around and then I ended up sending him some older existing files that are currently being used to help with the label builder process. One of them was 33,000 lines of code long. That's a super long file. The other ones were only around 1,000 lines long (pretty normal).

Meeting with Cody to look at his progress on the adilas label builder. He can show the image (label) on a different page now. We ended up working on the different submit buttons (view label, save, save and exit, and just plain exit). We made a few changes and then started to look into what it will take to make the labels dynamic (data driven) vs static (as they are built). We made some small plans and played with doing some string replacements (dynamics). Cody is going to work on it and see what happens. Basically, using an existing saved label or saved content, we will change the content, re-render the label (image) and then show the new label with changes. In theory... it will work.

As a note, the adilas label builder already exists. This is just a whole new take on it to add a bunch of functionality and change the interface. It should be pretty cool once we finish things up a bit more.

Meeting up with Cody to go over his progress on the label builder. He is doing awesome. Today he was showing me how he integrated it with Adobe ColdFusion and all through custom tags. Super cool. We talked about next steps and what else is needed. He will start working on basic CRUD stuff for the database actions (create, read, update, and delete). We will also be building out navigation between a label homepage and the add/edit label builder page. We spent some time and went over how adilas normally handles the add/edit processes in existing pages (passing modes and id numbers). Good stuff and making progress.

Emails, recording notes, printing checks, and checking on bill pay options through our bank (spoke with Kasi or Casey at PB&T). Checking out Cody's label stuff on GitHub. Pulled down a local copy to play with.

Meeting with Cody over GoToMeeting. He got the rotation done and the transform stuff for the label maker. Just for fun, he was showing me some of the computer graphic level math and game design stuff that is playing into the label maker project. Pretty cool!

Maybe working on saving things next. Sent him the existing database table schemas and we talked about different columns. He would like me to setup a GitHub account so that I could get access to his project and source files. He would also love to get more hours if possible.

Phone calls with Steve and Bryan. Talked with Steve about some manufacturing stuff and new default vendors and default customer settings. We talked about options and ways to help take out steps and automate things. More and more settings. We also talked about other deployments and clients and upcoming projects. Light talks about staff and even a new guy (Cody - developer) and Piper (designer working with Chuck). Trying to make things happen.

Bryan had some questions about more QuickBooks API stuff and other projects that he is working on. He's got a lot of stuff going on as well.

Meeting with Cody. Looking into label builder changes that he has been making. He is working on rotation (for boxes, images, and text fields) and QR codes. He also added in some alpha transparency options. Making progress.

Meeting with Cody to go over progress on the label builder. He has got a text box with wrapping text, an option for images, normal rectangle boxes, normal text, and the ability to stack (layers) and organize the content. Making progress. Next, he will be working on rotation and barcodes and QR codes. I also gave him some links to different documents where we have some brainstorming notes on what we want for requirements for an MVP on the label builder.

Quick meeting with Cody to go over progress on the label builder. Printing a quick check for Cody. Quick phone call with Hamid, touching base. He is doing some ColdFusion training. We are going to re-meet up after the 4th of July.

Meeting with Cody. He is playing around with some concepts for the adilas label builder. He has made some major changes since yesterday. He can do both boxes and simple text fields. He can move them around (drag and drop) and nudge them (little arrow keys to change the x and y coordinates). Each new element creates its own inputs (form fields). Those inputs stack up and create an accordion type interface (visual display). He can remove elements, change their stacking (front to back), etc. It's looking good. Still just in scratch (play) mode.

I also showed him the existing database (for labels), how we are storing things, a small intro into the 12 main player groups, and how eventually, we will need this label builder to be able to create dynamic or data driven labels. I hope that I didn't overdo it (overwhelming him), but I wanted to show him where it was heading and going.

As of right now, he is going to play with straight JavaScript until we run into a need for other technologies. Sounds like a good plan to me.

Meeting with Cody to check out his progress on the adilas label builder. He is playing with a JavaScript Canvas and getting interactions to show back and forth on a small webpage. He is mostly going to be playing with the JavaScript side and I will help with the backend connections. I sent him some video references on the adilas label builder. I spent a little bit of time looking over the videos that we have on file for the label builder. I thought that this one was a fun one, showing where we are heading (video link - 5 minutes - promo video for the adilas label builder - next steps).

Bryan had some questions on the QuickBooks API connections. Just looking around a bit. Lots of OAuth stuff. Back and forth, back and forth. Small graphic fix for Shari O. and the adilas internal email stuff. Emails and follow-up. Non-compete for Cody Apedaile. Prep work on the adilas label builder app.

Meeting with Cody. I set him up as a user inside adilas and inside of the adilas shop. We briefly started into looking at JavaScript canvas stuff with the intent to build a label builder. We have been through multiple versions already. We are hoping to make it simpler and more interactive and easy to use. Those are big requests... :)

Meeting with Cody to see his progress on his website project. He is building a small story book website for a practice project. His code and ColdFusion is looking good. He is getting it. We then talked a little bit about jQuery, AJAX, and how to cross JavaScript with ColdFusion. I showed him a few examples and hopefully got him on his way. I would really like to use him on our adilas label builder project, if Steve will allow it.

Went into Logan to meet with Cody. He showed me what he has been working on this week. I gave him some training on Adobe ColdFusion and MySQL to look into. He is much more advanced than some of our other recruits (new developers). I got him paid and lightly lined out on the next steps for a mini project using his skills. 30 miles.

Helping Cody Apedaile get his local ColdFusion and MySQL environment setup and going.

Reviewing a resume for Cody Apedaile. He just graduated from USU with a degree in computer science. Spent half an hour chatting with Cody over the phone. Sent him an email with a small training proposal. Ship B stuff.

Reviewing notes for the Bear 100 changes that have been requested. Reading some notes from the Bear 100 race director. Quick phone call to touch base and go over the email. Cody did a great job summarizing things and listing out priorities. That is awesome!

Went into Smithfield to meet with Cody Draper from the Bear 100. We met at his house and went over pros and cons from the 2022 race that happened about a week ago. He seems pretty happy with how things went. This is his first year taking over as the new race director. We took some notes and chatted for a bit. He is looking to push the system forward. We did some consulting and will be modifying things before next year's race. Good stuff!

Phone call with the new race director for the Bear 100 Mile Race. His name is Cody Draper. We went over aid station changes, when I need runner data and bib numbers, and how the invoicing will work. The plan is to invoice him after the race at $4/runner that starts the race. He's excited.

I've got a project coming up that needs some new settings for elements of time (calendar, scheduling, and events). I woke up this morning and couldn't stop thinking about some ideas for some new settings. I scribbled them down on a 3x5 card (front and back). I was saying a prayer and the ideas kept coming. Kinda fun. Also, the other fun thing was almost being able to see how to do some of these things and the potential that they could unlock. Really fun.

Anyways, here are the ideas. After I got them all scribbled down, I texted Steve to see if he would want to meet for a bit to go over the new settings and ideas. We jumped on a GoToMeeting session and he and I had a good 45 minute chat, with drawings, proposals, pitches, and lots of ideas going back and forth. Good session. Here is an expanded version of some of my little notes and scribbles.

- Dealing with time templates - what if we allowed for a basic mode and an advanced mode? Some people may not want to see all of the pieces. The basic mode would be what currently exits and/or something pared down from that. The new advanced mode would allow for all kinds of other settings, verbage changes, field name aliases, special instructions, sort order (where the fields show up), settings, required options, etc. The time templates page would have a toggle switch to go between the basic mode and the advanced mode. There would also be links directly to the advanced and basic modes from the list of time templates page. Same permission, just a toggle switch between the page modes. As a side note, Chuck recommended that we maybe have a "custom" mode.

- We already do this with customer database field names (allow for field names to be controlled). We want to do the same thing for elements of time. We will use the db_field_settings table to store specific info (field name options) for each time template, if the users wish to. If not, we will use a default set of data stored in the db_field_settings table for basic time_templates. We will use the field called db_table_name to store the value "time_templates" to store the default values assigned to corp 1. Just like the customers stuff. For each time template, we will change the name from "time_templates" to "time_templates_[555]" where the number will be the corp specific time template id number. Tons of sweet options there already. Aliases, defaults, placeholders, build your own drop-downs, required yes/no, max, min, show/hide, sort order, etc. As a side note, we currently let the main time templates handle the show/hide options. Somehow we may need to sync those up and/or figure out which one is the master. For right now, I'm still leaning on the time template being the master and the db_field_settings table holding the naming, aliases, special directions, defaults, etc. I hope that makes sense.

- On the advanced time search page. I would really like to add a master template switch at the top of the page. This would be a drop-down form field that shows all of the time templates. If a time template is selected (or preselected through a URL.template value), at the top, and submitted, then the page would be able to virtually slim down based on the settings, naming, and custom pieces per time template. The current advanced time search has everything plus the kitchen sink. If a template is selected, then the page could only show those pieces that are turned on, the correct naming, the correct filters and search criteria, and hide all unused sub searches as well. The time template settings would also affect the sub time searches and use the correct verbage, info, naming, show/hide, filters, etc. Basically, be able to dynamically convert the advanced time search page into a time template specific search form or page. That would be super cool. Also, if a template is selected, the search results could also translate and show the correct fields, verbage, settings, and make it feel round trip (search, results, and details). Higher in this entry, it is alluded to the fact that we could control the page with a URL value (URL.template) and then we could link to it, store quick buttons, etc. That would be really handy. As a side note, Chuck recommended that we look into a tab or tabs based page for all of the different searches - make it more digestible vs all in-line down the page. We could still have the template switch, but show the different searches in a vertical or horizontal tab display. Great idea.

- On the sub flags and tags, we need some more template settings. You can turn 5 different sections on with this sub (one of the bigger subs). A section within the sub tags and flags, was one that that was added later on (for phase tracking and location moving) it deals with possible sub tie-ins (PO's, invoices, quotes, etc.). Currently, we can't control that piece through settings. It just kinda got added out of necessity vs through the normal development process (planning). All we need to do is go in and add those settings, flip some of the old values (existing data) and make it more straight forward as people set those things up in the future. Along those same lines, the sub flags and tags may need some help on the output and display and the add/edit process. All of those pieces were altered and got the sub tie-in hardcoded to them. We may need to remove or make that more settings based.

- On sub flags and tags, I would like to be able to show the last flag or fag on the main. It holds the data right now, but doesn't show the entry. Light tweak to make it show up on the working with time page and the printable time page. Also, check the searchability of the last known flag or tag on the main, through the advanced search.

- There are two pieces of the main elements of time that we can't control via settings yet... they are the make private and admin only checkboxes. We need to be able to turn those two settings on and off. Currently, every element of time automatically gets those. They are not used that often and need to become settings so that we can show/hide those options. As a side note, those two settings do have some hardcoded text values like "private" or "admin only" that show up on other reports and report types if someone searches for something that is marked as private or admin only. Just a heads up. We may want to limit the verbage on these settings.

- The general amount field on the main elements of time is currently locked to showing dollars. I would love to add some settings to allow that field to be named and formatted. I was thinking of dollars and cents, decimals, plain (no formatting), and integers (remove the decimals). That would make it more useful. For example: I have a time template called mileage and I use the general amount field to hold the number of miles. It holds the correct value but when I pull the report, it always shows the miles in dollars and cents vs just a plain or decimal number. Anyways, I think that could help. Also, along those lines, there are some budget and estimate settings (different settings but still tied to the main element of time)  that could use similar number formatting options. See notes at the bottom for some other mileage ideas.

- What about allowing for the sort order of the fields? This is more complex, but it would be cool. You could put whatever makes sense to you first and move other fields around (up and down or sorted). We may have to circle back around to make sure this is possible.

- Recently we added a thing called flex attributes to the customer section or player group within the system. The flex attributes are virtually real in-line database extensions. We allow for new fields to be configured, added in, able to search, able to show-up, etc. These flex attributes are datatype specific (dates, times, strings, numbers, decimals) vs just plain text fields like the flex grid tie-ins. We eventually want to add these flex attributes to all 12 main system wide player groups (customers - already, invoices, quotes, parts and items, stock/units, elements of time - coming soon, I hope, employee/users, vendors, PO's, expense/receipts, deposits, and balance sheet items). One more thought on this topic of flex attributes. We may need some flex attributes on a global scale (able to cross time templates) and we may need time template specific flex attributes. We may want to do the global ones first, then limit or tighten things down for the time template specific flex attributes after the global flex attributes are added and stable.

- Horizontal grids - show time blocks with main categories or values going down the left and time across the top. We would love to allow for saving settings, allowing for special homepages, and custom buttons, just like my cart favorite buttons. See element of time 6967 for more info on horizontal grids. This is a form of blocking out times and who or what is scheduled, called for, or booked. Ideally, we want to be able to configure these horizontal and vertical time views, so that we could have and use more of them. That would be really cool. Once again, see element of time 6967 to get more details and information on horizontal grids. We used a custom horizontal time view for the Beaver Mountain Ski School. They have been using it for 5-6 years now. We would love to keep building off of that type of a model and make it even more configurable and savable without tons of custom code. Make it a tool for all of our users.

- Visual blocking of time... both horizontal and vertical blocking or showing bars or blocks of time. This is a visual way of showing what is booked and what is not booked or called for. Both directions, horizontal (side to side) and vertical (up and down). We need them both. We currently have the time slot view which is close to vertical blocking, but it still needs to be more bold and handle the blocking in a better way. The logic seems to be there, but it still needs a little visual help to really bock and virtually claim those slots or segments of time. It might be nice to ask for certain visual blocking right from the advanced time search - kinda like a report type. We already have a calendar view, time slot view, grouped view, and detailed view. Maybe add horizontal block view, and vertical block view. That would be cool.

- We would like to add in some dynamic dates. These special dates would allow reports to be saved with the dynamic dates vs a physical date range or custom fixed date rage. The dynamic dates would and could be things like: current day, current week, current month, current quarter, current year,  yesterday (prior day), last week, (prior week), last month (prior month), last quarter (prior quarter), last year (prior year), tomorrow (next day), next week (future week), next month (future month), next quarter (future quarter), next year (future year), etc. These would be really handy, so that saved reports could just pull relative info (based off of the current or today's date value), without having to worry about updating or flipping date ranges. Anyways, I think this will be awesome and we could use it all over the system on other reports and pages. Especially, wherever we are saving reports and pulling up saved data. These dynamic dates may make it super awesome and powerful.

- Be able to use the calendar view and calendar overlay for tons of new reports. Be able to save almost anything in an calendar type view. That would be awesome. Once again, the dynamic dates, mentioned above, would be really cool with this. Maybe even have an advanced search page that could save and filter the data and then show it on a calendar type report view. Great visual for what is happening on what day over time. We could call it the advanced calendar page or report. It would also be super cool if we could point subs of time to some sort of calendar type report or other visual time blocking type report. Currently, most of the subs only show up in detail view (normal tables with rows and columns). Being able to see the subs in other report formats (calendar, time slots, time blocking, horizontal, vertical, groups, etc.) would be sweet.

- On the template settings (techy stuff behind the scenes), currently, when adding and editing a main element of time, you have to pass in the template settings when adding or editing the main element of time. I would like to automate this process. It would make it easier for the developers. This is more of a behind the scenes switch on the methods and method calls. Most of those template settings don't change very often. We should have the methods themselves do the look-ups and make the changes (adds and updates to the fields on the elements of time table). This would really simplify the add and edit main elements of time processes.

- Being able to control the names and settings on the subs is going to be huge. This means what they are called (like sub dates and times, sub comments, sub sign-off's, sub flags and tags, sub payroll, etc.) and what fields they hold. Be able to change that on a per template basis. It also includes the sub fields and what they are called. For example: Say the default sub section is called "Sub Dates & Times". We may want to rename that "Amenities" or "Sub Bookings" or "Project Timecards". We could also control the field names with the sub section. Say the origianl or default field name is "Sub Title or Caption". Say you wanted to change it to "Extra Booking" or "Follow-up Reason" or "Sub Event" or whatever. Being able to change what the main things are called and also what the sub fields, within each sub of time are called and how they act. That will be a game changer. Here is a list of the current subs of time.

- On the working with time page, make the add/edit subs easier. Add in buttons to help with the add new process. The current way is just a simple link. It kind of gets hidden. Make it a little bit more bold and obvious.

- Some of these settings and concepts would be super cool for the fracture project. We really want to hide whatever we can, show what we need to, and allow for the whole thing to be dynamically (through data vs code) controlled and configured. That would be a super cool piece for fracture. See the above entries for some ideas.

- Futuristically, we would love to be able to switch elements of time between time templates. Currently, you get one time template and that is it. We don't allow an element of time to switch templates due to all of the background settings that are being held, monitored, and used.

- We may also need to add in some settings to deal with the general name for elements of time. That is very broad. Each time template can be named individually, but we have had clients that want it called the calendar, scheduling, etc. We may need some bigger corp-wide settings that control the main name and smaller abbreviations. For example: The defaults may be "Elements of Time" and "Time" for short. However, they could be set to Calendar, Lessons, Schedules, Reservations, Rentals, Bookings, Assignments, Tasks, To Do's, etc. The more that people can call it what they want, the less they end up fussing later on. That key piece of speaking their language is huge.

- It's not all code, some of this is just planning and dreaming

- It may be nice to use a spreadsheet to help with some of the planning. We have lots of rows, columns, and complex data that is needed for the planning portion.

- As a side note, it was so tempting to see a need, and then jump and try to fill that need. I on purpose spent some additional time (hours and hours), trying to get ideas and thoughts out of my head and on to paper (virtually) so that all of the pieces became public knowledge. My normal urge was to figure out a portion of it and then just do it vs writing all of these things down for the benefit of others (and myself).

///////

On 8/10/21 added some ideas for advanced job costing.

- Mini P&L per element of time. If we can tell that an invoice or expense or PO was tied to the element of time, have it automatically show up in a mini P&L (profit and loss) statement. This may be done with flex grid tie-ins right now (currently - but somewhat manual). We would love to automate it and build it into the mix. That would be really cool. Maybe do some searching for "job costing" to get other ideas.

///////

On 9/2/21 added some ideas from Chuck Swann

- Chuck read through these ideas and gave Brandon some feedback. Some of the ideas have been listed above with Chuck's name (search above). Here are some of the highlights - What about adding in some custom CSS (cascading style sheets) or custom display options? Maybe think about using a tabs based display for the advanced time search. The word or mode of "custom" may be better than "advanced" - technically, the advanced mode could be the custom mode, it just sounds better and more fitting to what we are really doing - dealing with time templates. Lots of the existing pages need an update to work better with the snow owl theme (style and face lift for pages). Make elements of time easier to use, in general.

///////

On 9/2/21 added ideas and projects from Cory

- Build out the online and customer facing scheduling options - this is a big project, all by itself. There are more details on other pages. We have a bike shuttle company that needs online scheduling (from ecommerce) and there are many others who are looking for this. Any business could use customer facing, online scheduling.

///////

On 8/21/23 added some ideas from a buddy - Josh Hanks

- On mileage. Maybe add a sub of a sub to do mileage. We may also need a standalone option (list way up higher using the general amount field) or adding it to a sub date and time entry. Not all entries would need mileage, thus a one to many off of the subs (sub off of sub dates and times). Imagine template settings under sub dates and times to say something like: Need mileage? If yes, do you want to enter a simple number (x number of miles) or use start/stop odometer readings (then we automate and do the math when submitted). Anyways, I had a great meeting with Josh Hanks on 8/21/23. He's a water master, ditches and irrigation stuff, he has a need for these things mixed together - projects, hours, notes, and mileage. The other benefits would be reports, exports, and math that is done for you. We may also add in photo galleries, document management stuff (media/content), etc. We have all of the pieces, we would just need to mix it together better and make it a small industry specific skin. Eventually, when we build out fracture or adilas lite, we want to include some industry specific skins as part of that project or platform (part of the value add-on core model). This may be a fun little venture into that world.

///////

On 1/23/25 added some notes about being able to flip subs from one element of time to another - incase it got added incorrectly

- On subs of time... it would be super cool if you could jump into a super admin edit mode and be able to flip the main EOT tie-in and/or adjust the person who did the record. If we did this... we would need to make sure that we record a good history message add/or tie it to a special permission. For example: Say we have a sub date and time that was added to project # 25 but it really needed to be added to project # 28. It would be cool to be able flip the record from EOT to EOT. It would also be cool to create a new sub... tied to you, as the user. Then jump into the super admin mode and flip it for your buddy. We would need to record the histories, but that would be cool, in a way. My idea is to add a small button to allow the flip flop, then use the same page, just in a super admin mode. We would have to make the action page smart enough to tell if the page was being super admin mode or just normal edit mode. That way we get the correct histories (maybe both sides, if flipping things around). Idea came from Cody (engineer from logan area) on 1/23/25.