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.

Working with Steve and Chuck. Going over reports. Working on and building the dream - that's what we are pitching and selling. Talking about showing them the mock-ups. Helping to put a visual with the pitch. Steve has been kissing a lot of frogs (potential investors and venture capital stuff). He's hoping to find the one (just being silly... like a fairytale). Sell the sizzle...

Switched over to the website proposal and series of questions. I took a bunch of notes here:

- Need for website to be tied into the inventory management system.

- They want a CMS (content management system). They want to control all of the pieces and be able to make the changes. Steve was pitching our own mini CMS type system. Chuck was pitching WordPress with some plugins.

- Talking about running all of the services (one-place shop) for the client. We are your dev team.

- We have so many pieces that are close... they just aren't fully done.

- We may have to help them with a mashup right now. Then, later on, we may be able to build out all of the pieces for them (internally). Chuck is worried about the time to really build it out (right now).

- The power of mock-ups. If you have 14 different plugins... to install, configure, and manage, it can get messy. If WordPress goes down, it makes us look bad.

- Maybe pitch two options... one for WordPress and plugins route - the other, just adilas, we build it all and keep it all up for you.

- If we build it, things take time. real time is needed for planning, building, and we need real budgets, etc.

- We really need to control all of the pieces. They want full control and speed to market. If we build it internally, we have assets that we can throw at it. Basically, fully outsource it to us and we will run with it. We are your one stop dev shop.

- Maintenance fees to keep things going.

- Back to selling them the dream.

- We will save you so much time and effort by systemizing things.

- Talking about social media... that (social media posts and such) becomes the changeable web content, the main website is more of the backend stable piece, that's where you order and interact with the actual products and inventory.

- Talking about real native "mini" apps that tie into the adilas system backend. Keep them small, open or create the doorways, we will go from there. Basically, just a mini portal into their world. Mobile first approach.

Chuck had to take off. Steve and I were talking about inventory thresholds. We were also talking about the future of where things are heading. Lots of mobile stuff. Everybody wants efficiency. Josh is really helping to push on things. That is huge.

Small side note - Brandon was riding snowboards with Aaron Hill, on Friday 1/10/25, up at Beaver Mountain. They were talking about ways to make their clients sticky. When they had to go their different directions, for the day. Here is what Aaron said to Brandon - "Really make those clients sticky! Win that battle! Make it good!". Great advice!

Meeting with Chuck to talk about a vertical time view for appointments and elements of time (calendar events). We setup a new page template for his new page. Talked about how we did the horizontal time view page for beaver mountain. We also talked about a number of possible options and how to show the correct vertical appointment blocks. We even looked at some dynamic CSS and doing custom height calculations on the fly. Making progress.

Meeting with Chuck to go over the horizontal time view stuff for appointments and scheduling. Sent him a link to the video for Beaver Mountain and how they use the horizontal time view and scheduling for ski school stuff. Also, a couple of screenshots and some other notes and references (notebook entries id #'s 8004 and 10914) dealing with time, settings, and where we want to go.

Meeting with Bryan. Working on some demo flow options. Tons of stuff for the golf club demo site. We went over new carts, ways to track tables (say like in a restaurant), custom buttons, and other topics. Here are a couple of topics that need their own line.

- We would like to set it up to be able to setup and/or pass through flex grid items from the shopping cart to either customers, invoices, quotes, or elements of time. That would be so cool. Currently, you have to get out of the shopping cart before you can deal with flex grid tie ins (custom fields or custom one-to-many relationships). We talked about ways to do this and make it happen. Brainstorming.

- Putting multiple people on a single element of time. We already do this for places like Beaver Mountain (ski school lessons) and High Valley Bike (bike shuttle services). We just need ways to make it easier to do for other companies. You can already set it up, but you kinda have to know what to do and how to do it to make it really work. Also, some of those other businesses, we've helped them out by creating a custom set of buttons to jump into their specific flows. That really makes it easy for them. Basically, ways to speed things up and make it not so custom but a generic, yet configurable, toolset. Behind the scenes, we use a thing called limited flex grid to make the forms look super simple and easy to use.

- Bryan and I went over lots of options for splitting tickets or bills. Here's the scenario. Say a guy wants to set up a tee time (golfing) for he and three other friends. We need to schedule the tee time (calendar event or element of time). We also need to bill each person or put it on their tab. We can do that right now but we would have to do one of the following. 1. Create four invoices, one for each person and put it on account (they will pay later or their tab). Or 2. We make one invoice for the full amount and then let them, each person, make a payment towards the full ticket. You can do that right now but it doesn't put it on account for each one. It would just be an invoice with multiple payments. Anyways, we talked about some bulk tools for the shopping cart or ways of saying... duplicate this invoice for these people (bulk tools). Then it, the system, goes out and does it.

Just some ideas and discussion topics. Good stuff! Bryan is doing a great job asking questions and what not. Lots of fun ideas and getting him some training on the system.

Morning sales meeting. Somewhat disconnected and a little bit rough. Nobody was really leading the meeting. Everybody reported in and some small demos of what people were working on were done. I was working on my own little project in the background. I added in a daily notes option for Beaver Mountain while I was listening.

At the end of the meeting, John was explaining some of the new default page view settings that we are working on. It didn't really go over that good. I think that it was because different people were doing their own stuff and projects and only heard part of the report. We got it all figured out in the end, but there was some confusion, contention, and some light friction for a bit.

More work on the Beaver Mountain Ski School and custom tool tips for the horizontal time view page to show lessons, availability, and who has things scheduled. They use that page every day, while they are open for the season. Worked on some custom formatting. Merged in the code and pushed it up for some live testing. Let the client know via text message.

Custom code for Beaver Mountain and adding custom data tool tips with lesson names, instructor counts, and student counts to the horizontal time view page that they use for their ski school lessons. Working through new logic and doing tons of testing. Ran into a CSS (look and feel) issue right at the end. Pushed up a temporary file to show them some progress.

Beaver Mountain custom tool tips for their horizontal time view page. Lots of prep work and reading over older code.

Back on the Beaver Mountain horizontal time view and adding in custom tool tips with captions and lesson counts. Finished up the top part for unassigned lessons.

Working on the Beaver Mountain custom horizontal time view (the original one). They requested a rollover/hover type tool tip to show more info without taking up any space on the horizontal time view page. I started into it and adding title/captions, student counts, and instructor counts. Created a new code branch to track the new changes.

Working on three different projects. First, quick tweak to help with High Valley Bike Shuttle and setting up reports and shuttles for the next season. Second, sending files over to Beaver Mountain. These included some instructions, template files, and blank registration forms. I also sent an email to the client with information. Third, I worked on some new tool tips for the Beaver Mountain on their horizontal time view. The folks at the ski school have requested a few things. Playing around with ideas and options. Light research.

Going back to the idea of setting up custom verbiage and SOP's (standard operating procedures) for clients, we have a ton of great options in the top header and footer for the snow owl theme. Each person has 8 of their own custom navigation links and buttons. There are also over 40+ custom navigation links and buttons that may be setup per corporation. If used correctly, it would make access to simple SOP's and other custom training, education, or tips available to all users, right from the site, using the custom headers and footer links. That is pretty cool. We need to remember this when we are building out fracture and our next theme and framework. These custom links and buttons are huge. What do you need? Where do you want to go? What is important to you and your company? Let us help you out... Good stuff!

Work session with John. We were fixing some CSS and making changes out in the shop. We fixed the ecommerce view for what are called icon boxes (a view out in ecommerce - layout). The display needed more space and we had to move the price and add to cart buttons around. It got a little deep, due to the settings of what was going on. After that, we started into the Beaver Horizontal time view and trying to add tool tips to the layout and view. Because this page is custom and somewhat old, we had to go back to older styles of code. The new pages have that stuff built in, but the older pages couldn't pull it in, there were conflicts - libraries and other crisscrossing dependencies.

Fun show and tell with the guys and gals. I showed off the Beaver Mountain special events, how we are building in paperwork and release forms, subs of time, history and usage, and customer logs. Danny, Sean, Michael, Shari O., John, etc. were on the meeting and I was just explaining things and showing the guys where we are headed, drawing, asking questions, good back and forth, and just having fun. I'm not sure if they knew it or not, but they were my audience today.

Went into to the Beaver Mountain office and worked with Amie and Kristy. Showed them a live demo of the special events and how things work and flow. Good demo and making progress. They gave me a small list of other things that are needed and wanted. Great meeting.

Working on some custom code for Beaver Mountain and their special events. Spent time working on waivers, paperwork, and prep work. Pushed up files and prepared for live demo. Getting vendors, items, PO's, web settings, elements of time, and photos all ready.

Two different sessions, working on custom code for Beaver Mountain. The first one was from 1:30-4:00 pm and the second was from 4:30-6:30 pm. Spent time looking into custom data collection and waivers and paperwork. Tying the pages into a time id and invoice number. Worked on hidden flex grid fields to pass along for the forms to work correctly. Started building the new waiver/paperwork file.

New custom data collection page that submits data to the paperwork or registration form. Custom code for Beaver Mountain special events.

New user accounts for Kristy and Amie for Beaver Mountain. Working on formatting on ecommerce pages and micro tweaks to code.

Working on Beaver Mountain stuff. Merged in some changes. Small tweaks to internal elements of time pages. Working on code.

Working on Beaver Mountain special events. Small bug fix on the classic add/edit parts categories page. Adding in new vendors, part categories, and items for Beaver. Setting up ecommerce images and ecommerce settings. Tons of new product images.

Building out the unique and special events for Beaver Mountain. Going through the checklists from my notebook from an in-person client meeting with Beaver. Small time and flex grid code changes. Pushed up some files.

Scheduling time, doing research, and planning for some custom code that is needed for Beaver Mountain. Went in and made a whole to do list inside of my digital scratch file. I'll be working through the list. I spent some time reading over my notebook notes from meetings with the client. Transferring hand scribbled notes into digital to do lists.

Logged into their new system and spent some time going through corp-wide settings, locations, snow owl look and feel, and ecommerce settings. Feeling better about the project and making good progress.

Sales meeting. Finding pain points and then addressing those pain points. Everybody was touching base and sharing stories. I did a demo on elements to time and how it works with the new pages and new horizontal time view. At one point, only Beaver Mountain Ski School had a horizontal time view page. We revamped some of that custom code and made it more global and available for everyone.

One of the guys had the idea of showing schools and being able to show multiple people at a single time. Dealing with training and education and even demos. Getting more people to see and understand things at once vs the one-on-one game we are playing right now. We spent some time going over MVP's and what is needed. MVP's could be - minimal viable product, plan, person, etc. We all need the continuous win to help us along the way. Little wins and success go a long way.

Steve and I touching base on things. Meeting with Bryan. Merged in 10 new files for elements of time. The new code came from Chuck. John helped us push it up to data 0 for testing. Looking over Bryan's progress on his migration of the custom Beaver Mountain horizontal time view to a more generic and public accessible horizontal time view page. Bryan is also working on pulling across the add additional user/payee assignments page. Once again, custom code that only Beaver Mountain had access to and now we are reverse merging in that new code so that other clients could use that type of functionality.

Went over to Bryan's house to work. My computer was down. We went over new settings and ideas for time buttons and tying them into my cart favorites. We wrote down some ideas in Bryan's notebook.

From 2 pm to 3 pm - Bryan and I jumped on the server meeting (from his house). Cory, John, Bryan, and I were on the meeting. Wayne joined part way through. After the meeting, Bryan and I jumped back in and worked on refining the old custom code that we made for Beaver Mountain. More time button stuff and planning. Bryan has all of the notes. I was kind of just an extra today - no computer or anything.

Bryan has been making videos about his project, just to document things. Small push to change eXpo payment type to Herbo payment type. Lots of talk about layers on time and availability. Bryan got deeper into reviewing the horizontal time view page for Beaver. We also talked about time buttons (this will be a sub of my cart favorite buttons but to help book and sell time - with an additional calendar tie-in as well as shopping cart functionality). See elements of time #'s 6967, 8004, and 9633 for other ideas on time buttons.

We were playing inside of Microsoft Excel with scenarios and options for web availability and layering.

Sean and Danny were talking about demos and techniques. They are prepping an outline with hyperlinks to help them navigate and show things quickly vs having to navigate the whole system to get to the same pages. Good technique.

Steve joined the meeting, even though it was his day off. We got into talking about new time settings and my meeting yesterday with Beaver Mountain (local ski school). They have been using adilas for close to 7 years now. Most recently, they are looking to use it to help them with registration for their special mountain events and races. It was unintentional, but I ended up giving all of the guys on a meeting a full-on demo of what we are doing and where we are heading.

Steve was kind of challenging me on a few things - why did you do that? What about this or that? Maybe we could do this or that, etc. We talked about it and I took some notes. I still don't fully know what direction to go and what would be best, but I took some notes. Some of it was dealing with multiple systems vs a single system, settings, custom code vs building for the masses, and individual customer records vs quick flex grid to get super simple data into the system quickly. We talked about effort levels, timing, speed, data in/out, exports, and future flow. It was a good discussion, even though I felt like I was being challenged on every front.

As a side note, when we started this project, back in 2015, we didn't have what we have now (7 years later). If we had had what we have now, it would have been a different story. All things are possible and are options, it just depends on timing, resources, budgets, skills, and where the system is at (functionality wise).

As a part of fracture and going forward, we will be trying to turn in as much stuff to settings as we possibly can. We have 4 known levels for settings. They are corp-wide (world level), group-wide (12 main players), page-wide (per page per section), and user-wide (preferences and options per person). Things keep breaking down into smaller and smaller pieces another word for it is "subs". We even were talking about things like subs of corp-wide settings and almost location-wide settings. We don't want to go there yet, but it is starting to surface. Basically, the main goal is to turn everything into settings, where possible.

Along those same lines, if you have tons of settings, you will also need different levels of users - end users (lower levels of knowledge and skill), medium or middle users (knowledge of settings, options, and configurations). You will also need the admin users or backend/systems admin persons (who is making and building the settings for the others to use). It can get deep.

It is ok to re-think the processes or re-think these processes. Permission granted! Often, education leads to new ideas. We see it in our clients all the time. We add something or teach them how to do something and almost immediately they come up with something new, different, or that now seems possible based on the last known level. We call that taking the next logical step. It's huge and big part of what we do.

The last note for this session was this - everything is breaking into subs, sub settings, sub permissions, and sub configuration options. Everything!

On a meeting with Bryan. Review of the demo that we did for Beaver Mountain. Showed him some of the ideas and things that they would like based on the demo. We spent some time looking at the date-picker code. Pushed up 17 files with some code changes. Switched over to the new time settings stuff. Horizontal and vertical time views (like Beaver Mountain). Tons of time talking about the availability table (new for online scheduling). Going over plans and new time settings.

We also talked about adding links to the new public horizontal time view page from multiple different places inside the system. Bryan took some of the custom code from the Beaver Mountain pages and is making it more public and general for all of our users. He already did that (just a few days ago) but now we are trying to add links and navigation so that people can actually use it and get to it from multiple other places and pages. All part of the process of building things out. Bryan really liked the horizontal time view functionality. Good stuff!

Went into to Beaver Mountain to do a live demo for Kristy and Amie for unique special events and online sign-up and registration options. Good demo. Came home with a bunch of notes and to do list items. We decided that we would run the special events on a different system as compared to the current one that is being used by the Beaver Mountain ski school. All of the flex grid tie-in settings and verbiage are different. We allow for custom but only one set of custom settings, not a one-to-many on the custom settings and custom verbiage stuff (field names and aliases).

Prep work for Beaver Mountain. Making sure that vendors, items, categories, time templates, and settings were all in place. This was on the old system - meaning the ski school system. Eventually, we created a whole new system for them to run and track their special events.

Beaver Mountain and looking over ecommerce/shop pages. Scheduling code review. Went pretty deep for the review. Small tweaks and changes.

Fixing the bulk add and bulk edit flex grid tools. Trying to make them more standard and available for anyone who uses flex grid, not just certain clients. I changed the page names from the bike shuttle company pages to more generic page names, so that we could use those pages for our other clients. Small tweaks and code adjustments to make the new pages work. I also did some work and added in the new bulk flex grid tools for Beaver Mountain and pushed up new code. Sent an email to let them know that they now have access to those bulk tools. That should really help them out.

Monday morning and off to the races (again). Busy morning! Steve and I were working on some code tweak. I reported on a meeting with Beaver Mountain and showing them online scheduling and bulk flex grid tools. That went really well.

We switched gears and started talking about where we are heading, as a company (as adilas). Here is a quick list, the priorities haven't really been set (numbers) but all of these things are on the top of our list (quick list):

1. Online scheduling (we have determined 3 different levels. Number 1 is done, 2 is on the way, and 3 is still to come)
2. Internal scheduling (make it easier - internal - and new settings for time)
3. Merchant processing and quick and easy carts (chip, swipe, easy & pretty cart) - We already have a bunch of this, just refining it and making it tighter.
4. Labels builder and custom labels
5. Aggregates (quick summed up data) and business intelligence stuff (eye candy - light graphs, charts, and other look and feel stuff)

Steve was talking about his approach for doing sales. He does some things for free and then tries to sell them on the upgrades or next levels. We think that we can really do well by selling services and even reselling services from others (internally and externally as needed). As we go forward, there will be more and more focus on the frontend or look and feel of the application (UI/UX stuff).

Our current goal is just to keep cracking on it and doing daily refinement. That's about all that we can control or manage sometimes.

Went into Beaver Mountain, Logan Office and met with Debbie and Kristy. Good little meeting and show and tell session. My main goal was to show some of the new client facing scheduling options and bulk flex grid tools. We ended up talking about all kinds of stuff. We went over online scheduling, special events, RFID tag tracking, reoccurring or duplicating time, campgrounds, merchant processing, hardware, and systems in general. I really enjoyed the meeting and hopefully the ladies did as well. Lots of potential for where we could go.

See attached for some of my notes. They would like a few tweaks to their existing system.

Steve, Sean, and I were talking about showing stats, system-wide aggregated data and totals across all servers. We used to have these statics that showed how many invoices, PO's, expense/receipts, and deposits we had done. All kinds of stuff. It may be cool to get something like that going again. We were talking sales and what not.

After that, we flowed over into some talks about online scheduling and I gave them (Steve and Sean) a small demo of the new settings that Bryan finished up. We talked about the next level and what round 2 of those scheduling settings would look like. We spent some time and I showed them around in the bike shuttle site as well as what custom code we had done for Beaver Mountain Ski School. Good stuff!

The next topic was digital journaling or journals for whatever. Adilas is setup perfectly to allow any user or business to harness main players, log notes, unlimited flex grid tie-ins, custom fields, media/content, and photo/scans to almost anything. It could be clients or customers, items or products, appointments, events, invoice, etc. Tons of options. That's pretty cool. All of that is done, right now.

Sean was asking some questions about more graphical homepage and getting into some eye candy, graphs, stats, charts, and other aggregate values. I chimed in and mentioned that we have wanted to do graphical homepage since 2013 and earlier. Here is a link to some older entries that talk about or mention the need for digital or graphical homepages. That seems to be what people want.

Lastly, Steve and Sean were talking about demos and getting demos and leads from live events and shows. They are trying to work a number of different angles. It's fun to see them work and try different things.

Small demo about the new global features for limited flex grid for both Steve and Sean. This feature used to be exclusive for the Ski School up at Beaver Mountain. We pushed it out to the whole adilas system earlier this week. It should be a great tool for those who are doing combos with flex grid tie-ins. Steve asked about the plan for the bike shuttle company. I told him that we are planning on doing 3 basic steps - prep, train on existing pieces, work on automation.

Hope (Experanza) reported in and wanted to do more marketing with a specific company. She has good connections in her industry. She and Sean are trying to get some advertising into magazines and in front of different parties. As a small side note, it was fun to listen in from the background. You could tell that she was a power user of adilas and those people tend to be our best salespeople or representatives. They have lived it.

Just for fun, Steve would love to go back through and figure out who else we could grab that were adilas power users. There is an untapped resource there - who has the skills and who has done what over time? Another idea was, if we can get the adilas cafe all setup, these power users could offer their own skills and services. That would be totally awesome! Also, if you take a power user and then teach them something else that they don't know (different section of adilas), they tend to pick things up really fast. They are able to build off of a good knowledge and skill base. They eat it up and see the potential.

We talked about other possible marketing stuff, events, swag, banners, the works. Steve and Sean were talking about options and marketing efforts.

Next, we switched gears and Steve and I started working on pulling in custom labels into auto print from the cart. We kinda got lost and couldn't figure it out until we saw that his browser (just a setting) was blocking what we were trying to do. We got it figured out but it had us stumped for a little while. After that, we talked briefly about the MMLLC (multi member LLC) stuff and where we are heading. We also talked about the upcoming scheduling stuff that is coming down the pipeline. As it gets developed, we will need to make sure and get the training and education stuff out there to help our users and trainers.

Planning and researching some changes that are needed on the use limited flex grid tie-in pages. Currently only Beaver Mountain Ski School uses the special limited flex grid pages. We would like to roll that out to all clients and let them configure things and how things get setup and shown. Even though in the background it is doing flips and twists, make it look super simple on the frontend. It makes a difference. Imagine around 40+ fields to handle a single flex grid tie-in. What if you could get that down to 4 or 5 key fields. Wouldn't that look so much simpler. Anyways, we have it, but it fully custom and only tied to one corporation. We are looking at rolling that out to all clients. It will be pretty cool.

The Tuesday morning sales meeting was going on this morning. Marisa and Chuck were both presenting and sharing. They were talking about the scheduling side of adilas and how that would be cool to keep building that out. See this link for some other ideas on both horizontal views and vertical views for scheduling and elements of time. That link also has access to a small 2.5 minute demo video showing elements of time and some custom work that we did for Beaver Mountain (ski area and their snowsports school lessons).

Chuck and Marisa were also reviewing some recent email campaigns for trailer dealerships. They were looking at stats and how many emails had been opened and viewed. They were also talking about other places to advertise and connect with business to business software people and clients. Just looking for ways to advertise what we have to offer.

After the meeting, Steve and I were briefly talking about ecommerce and how it is going to be super important that our clients can sell all of their products and services. This includes normal inventory items, different services, and time (bookings and appointments). They all need to be able to be sold from the same ecommerce interface. You can tell that some of that is really heating up and there is a demand out there for it.

Alan and Dustin joined the meeting and we were going over units of measure and a possible variable casting error. John chimed in and recommended an Adobe ColdFusion update that might fix the problem. They spent some time looking into that.

Emails, recording notes, and general to do list stuff. Trying to do smaller blasts to keep caught up better. Email out to Beaver Mountain pitching the idea of a customer facing scheduling app. We already have a bike shuttle company that wants that. We are just pitching our services, as well as custom code work out to clients. Also recording some gift cards that got distributed.

Small bug fixes on the printable parts page. A client let us know that there was an undefined variable being requested. Got it fixed and pushed up to all servers. Added two new columns to the Beaver Mountain printable student list report. Quick update. Pushed up files.

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.

Working on a custom time view - horizontal time view report for Cinnamon Creek Campground. Using pieces of the Beaver Mountain horizontal time view report to recreate a similar function for a campground and their sub amenities - such as the archery range, the challenge course, the luau firepit, service projects, and cooking pavilions and kitchens.

See attached for a 2.5 minute demo of the Beaver Mountain Ski School - custom scheduling app that they use for booking their ski school lessons. It uses adilas and elements of time and flex grid.

Here is a link to some other ideas for setting up the templates for both horizontal views and vertical views for elements of time.

As I was giving a demo to some of the internal guys (small sales pitch on vision and options), I was showing what we did for Beaver Mountain and their horizontal time view (time across the top and their ski lesson instructors down the left side with their time periods marked out for when they are booked). I thought that it would be cool to let the users setup those (or similar) horizontal templates using settings. They could name the template, create new, assign filter or search criteria, able to edit or delete, search, view, and even get their own URL or address (similar to how we do saved reports). I thought that would be super cool. Allow for time blocks to be set across the top - start/end times, block size (10 mins, 15 mins, 30 mins, hours, etc.), and what to show down the left side. This could be people, users, customers, vendors, locations, items, etc.

Imagine a template that you could setup what it looked like (settings), what it pulled (settings), and how it displays that data (layout based on settings for persons, places, or things). That would be so cool. Basically, what we created for Beaver Mountain Ski School, but configurable.

Here are some small ideas (just scratching the surface): Instructors and lessons that are booked per instructor, classes being taught per room, shooting ranges and lane assignments and booked slots, employee work schedules, light rentals, appointments, multiple person schedules (each with a different URL to access a person at a time or a different URL to see all together, if needed), daily task lists, etc., etc.

Filters could be time templates, colors, phases, action statuses (started, stopped, pending, completed, etc.), assigned to (person, place or things), or whatever.

The Beaver Mountain horizontal view deals with conflicts, drill-downs to the underlying events (elements of time), and also allows for quick adding based on values within the horizontal view. For example: Say you have an instructor and they have an opening from 2-4 pm. If you click on the "+" sign in that section, it would already know the date, the person, the time block, and other criteria. You then take that info and auto fill out the form so it becomes super easy to add to the horizontal grid based on quick steps. All kinds of stuff could be passed through to the next (create new) page. Anyways, just wanted to record this idea and jot down some notes.

- New note added on 7/19/21

What about vertical time views (visual blocking out the time slots). We already have a time slot report which shows things going down, and it's pretty cool. It could be built out even better and show things in blocks. Currently, it just shows the span but not a visual block yet. If we could just take it to the next level, it would be pretty cool. Just ideas here, what about anything that could fit in the same vertical block, great. If there is a conflict or double booking, we add another vertical column. The horizontal time view adds extra rows. The vertical time view could add extra columns (very similar).

Steve and Sean going over sales stuff. They were talking about the Apple Model and how someone greats you when you come in and then you could be helped by someone else by going through some sort of simple queue type process. Danny checked in. After that, we helped Steve with his local environment. Both Dustin and John Maestas checked in. Some small intros were made and what not. John is Dustin's friend. John is just getting going with us on some development projects.

They then started to talk about different versions and generations, for example: generation 3 or generation 4, etc. Dustin has been responsible for some of the new versions out in cultivation land and what not. It is fun to see the progress and the changes over time.

After these guys left, we went into a sub meeting of sorts and worked through some things. Sometimes, our clients, want industry specific processes that are fully built out and completely industry specific (super narrow focus and/or paths to choose). As we were talking, we ended up talking about drawing out the processes, pretending to do simulations and different use cases. We also talked about being proactive vs reactive  and/or passive. We really want to help our users out and then let them help us refine it vs waiting completely on the client's input. Sometimes they don't know what is possible, they tend to stick with what is set in front of them.

Often, our clients don't realize that we can customize it (tweak or refine the processes). That seems really trivial to us, but thinking in custom code (what is possible) is a skill. The deeper we go, the more we are seeing that all of our layouts need to be fully customized or customizable and based on settings. That sounds awesome, but that adds a whole other level of complexity. Small and skinny yet totally data driven.

We need to get back to the limited flex grid pages. Make it slick and skinny. We are already using it for Beaver Mountain, but want to make it good to go for all of our clients. This would be so cool, but it will take some more work. Having said that, we really really want to get back to this. The limited flex grid is a way of setting up custom fields and dynamically populating a really small add/edit form that only shows what they want or need vs all of the possible fields.

As a side note, the flex grid table has over 40+ different fields that we can and do use for different things. Imagine is you could setup a simple form that only had 5-6 of those custom values. It then becomes really simple vs too big or too overwhelming. The goal is user defined simplicity, yet still being fully connected and powerful. If needed, we could always flip over to a full or more extended mode if some other field or value is needed. It is almost like layering the interface and the data. Super simple on the surface, but deeper or more rich as needed (layering).

We got off into communications and dealing with outbound messages, communication options, and getting people connected to the correct sub or special pages (combo of communication and navigation options).

Next, we got talking about building out custom skins (wrappers of the logic and data) and how that plays into the mix. We did some light pitching and talking about different packaging and marketing options. Some of the subjects that we chatted about were things like ski area, gun shooting lanes, classes, and then working with people in those industries to build and test out products and services. Basically, have or get a dream, build it, and then use people who are in that industry to test and give feedback on interface, navigation, user experience, flow, and functionality requirements.

On the marketing and sales side, if we have someone who is using our product in a specific industry, that testimonial does tons for helping others in that industry to be willing to jump on board. We have also found that if we find someone who is in an industry and they are willing to help, provide feedback, beta test, and give ideas... that is like gold and helps the process get smoother and smoother. It is amazing how a little bit of icing makes the cake look that much better.

Expanding into other horizons, we really want to do this. Our conversation circled back around to the dream it up, push on it, and we'll help you wire that up type model. You dream it up, we'll wire it up. Making things simple, powerful, and easy. Awesome words/phrases, harder to do, but possible. We also talked about opening our eyes and minds to what is possible. Being able to see and/or imagine is sometimes harder than you think. Once we can see it, the next phase is letting our users and clients catch that vision. Once you can transfer the vision, others start helping to beat that drum and making it happen. Share the vision!

As we look at the MVP (minimal viable product or minimal viable plan) type approach, we get pulled out of the dream land and back into - what are the next step or steps that need to happen. You can't lose sight of the goal, but you also have to make it work (along the way) vs just the dream at the end of the tunnel. Having said that... one thing that has been very successful for us is... get them hooked on one aspect and then letting them go and start dreaming. They'll start putting the pieces together. You just have to get that process started. Sometimes with an MVP type approach and then let it grow from there.

Here are a couple of other topics that were discussed: saved reports and connecting to them, other future projects (fracture), reviewing topics listed above, automated and predictive logic, aggregates and quick starts, templates, build your own processes (data assembly line and flex bubbles or flex pods), and other topics. Good meeting. Lots of new ideas and also firming up some of the older ones that keep circling around.

Shawn and I got on a GoToMeeting. He wasn't quite done, so we both just worked on our own projects. I finished up some custom code for Beaver Mountain. They wanted me to modify their add/edit process for adding new ski/snowboard lessons (new elements of time).

Getting things your way - the power of a custom solution. Steve and I were talking about core vs custom development. Where we are at right now is letting clients step up and have us build certain features. There is no possible way that we could shoulder all of the requests. We just can't give away anything for free right now. The companies that want to play and pay, they will succeed. Custom software as a service (SaaS) allows our clients to build out their own dreams and processes.

We were talking about finishing up some of the existing projects. Sometimes we like to dream and keep building and building. Maybe we need to circle back around and finish some of the outstanding projects. Steve was talking about - is this mission critical or can it maybe wait or hang out a bit? We are trying to get a better handle on this.

Yesterday, Steve and I were talking about mixed server technologies. Steve was also saying, as a reminder, that as we keep building, if we have outside services or 3rd party products, they will constantly need updating and keeping up with the new changes that keep coming. Even though some of the new pieces may look cool and be all gui (graphical user interface) and such, you still need them to be updated with the functionality that keeps rolling out the door. 

--------

Dustin was working on some cultivation stuff and had an issue with a pound sign (#) not passing through his page flow. We jumped on and did a little work around code to help him out. I spent some time and reworked the sub inventory searches for parent items as well as sub barcodes and sub RFID tags. I made a couple other simple changes and tested and pushed up some new code. Eric popped in and had a couple of questions as well. Pretty quite morning.

At the end of the session, I pumped out some quick changes to an employee report for Beaver Mountain Ski Area. Pushed up the code and let Debbie know that the new code was up and online.

While up at Beaver, did some training for the office staff. I had both Hatti and the new girl (can't remember the other ones name).

Spent some time working and training Debbie and Hatti up at Beaver Mountain on elements of time, flex grid tie-ins, and customers (students). We went over some flow, duplicating elements of time, and reoccurring (sessions and/or weekly reoccurring classes and lessons).

Made some custom code changes for Beaver Mountain (local ski area) for their ski school. Added some new ease of use buttons, added some status filters to a couple of queries, uploaded and tested new code.

Light research for a different client on bitcoin and other crypto currencies. Reading over an executive summary for a new startup company in the financial and merchant processing side of things. This is my own comment, but I'm seeing more and more financial based company taking an interest in offering a solution and/or harvesting existing pieces the further along we go. They seem to be the bigger players who help drive solutions forward. It makes sense, but it is kinda fun to see the working and movements of the financial and merchant processing guys in action. Everybody is trying to carve out their space and create a valid and relevant solution. Interesting.

Went into town to do some training for a new office girl by the name of Hatti. She works with Beaver Mountain Ski School as an office person. We did some adilas training on elements of time (lessons), customers (students), users (employees and staff), and flex grid (custom fields and multi assignments). Good meeting and Hatti seemed to pick up on things pretty quickly. I did some simple drawings and we went through a number of scenarios and features.

Towards the end of the conversation, I popped in and talked with Travis (owner and manager). We chatted about simple POS (point of sale) options, merchant processing, and digital timecards. I told him that they, Beaver Mountain, are only using about 15% of what is possible under the adilas roof. They are super busy right now leading into the season, but hopefully I planted a few seeds and some potential.

Chatted on the phone with Calvin going over API socket connection for his desktop application. Also did some light planning for the upcoming live adilas training session. Here are a couple of random notes... no special order at this point.

- Sell the sizzle...

- Think GEO tourism for selling the venue and location of Logan, UT. 1.5 hours North of Salt Lake, hiking, fishing, history, USU campus, shopping, mountains, rivers, valley, Bear Lake, etc. 10 minutes from Logan, you could be in the mountains.

- Guest speakers - concepts, vision, processes, procedures, etc.

- Highlight new features, new updates, and upcoming projects. Think of things like Campaign Rise (social media and custom wire job for elements of time), Beaver Mountain Ski Area and Ski School, Steve's campground stuff, Plant phases and cultivation stuff, Russell's new custom email stuff, ecommerce, WordPress integration, white label stuff, sales tax changes, new discount options, etc.

- Show what has happened, what is happening, and what will be coming down the pipeline. Maybe show a timeline with some key points and historical stepping stones.

- World building concepts and how different clients are problem solving with adilas as their worlds change and progress. Try to focus on 3D world building and the concepts of the data assembly line. Show how some of that stuff is already playing out.

- Different topic, but I would really like to get some sites out there like billboards pointing back to adilas and what we are doing. These are all of the main concepts such as 3D world building, data assembly line, creating a system, API sockets and playing at the wall, etc. These might be great projects for Russell to give his developers who are going through the program at Bridgerland. Good stuff.

(1-4 pm) At Beaver working on changes to stuff at Beaver Mountain. Flex grid permissions, horizontal view, custom verbage, passing dates for adding new lessons, testing and pushing live.

-On the beaver horizontal report . . . we had a bug show up if the start/end dates were different. Say 1/8/17 10am to 1/9/17 12am - if took the time diff and tried to find position. 

-Allow for companies to get their data.

-Maybe even full database and SQL code.

-Push up videos to the content server.

-Having people push on thinks that are huge.

-Negative variable (-16) slots backwards. We may need to check for that.