Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Charles Swann
Created By: Charles Swann
Created Date/Time: 10/22/2019 2:28 pm
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 5082
Template/Type: Brandon Time
Title/Caption: Meeting with Chuck
Start Date/Time: 10/29/2019 1:00 pm
End Date/Time: 10/29/2019 2:15 pm
Main Status: Active

click to enlarge - photo by: Brandon Moore - Some new screenshots of the camp adilas project. One of these is a map concept for a campground and the other is for a customer quick link page.
click to enlarge - photo by: Brandon Moore - A new screenshot of a reservation overview page and the map concept page. I have a zoomed in view later on for both screenshots.
click to enlarge - photo by: Brandon Moore - Small layout of multiple screens - still in design mode, but making progress.
click to enlarge - photo by: Brandon Moore - Quick checkout screenshot. Calendar on the left with basic info, some search options on the top right, day at a glance widget, and quick checkout option on the bottom right. As a note, some new flag and notes sections were added via icons at the bottom..
click to enlarge - photo by: Brandon Moore - Screenshot of the advanced reservation screen. Options for check-in, check-out, site types, amenities, vehicle info, customer info, and payment info.
click to enlarge - photo by: Brandon Moore - Screenshot concept for a reservation overview page. The page includes site numbers, site types, options, camper name, date range, optional services, payment status, notes, flags, and quick buttons.
click to enlarge - photo by: Brandon Moore - Zoomed in view of the map concept screenshot. The map may have a mix of real photos, overlay maps, icons, rollovers, pop-ups, and map filters (see bottom right for filters). The filters would select and deselect sites based on the filters. Fun idea.
click to enlarge - photo by: Brandon Moore - Concept of a customer/camper overview screenshot. All of the data would allow for drill-downs and quick changes where needed. This includes the name, email form, phone, status change, payment into, and checking flags or showing more options and values.
 


Notes:

Meeting with Chuck to get an update on Camp Adilas. We started out reviewing some other new graphics that are being presented and worked on. We then jumped into schools and how adilas could help out schools. Kind of a fun start to the meeting.

- Schools and options of supporting schools and education needs. Say like Bridgerland Tech College - They have 25 different departments, they sell all kinds of things, they have a book store, class fees, special events, tracking profit per department, café - lunchroom, catering, etc.

- Being able to configure the tools and features to fill the needs of the different companies and/or departments within a bigger organization.

- Here is a link that deals with options for schools, some older brainstorming - https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=2844

- As we were talking, Chuck said that he sees himself as being able to be the bridge between the tech side and the people side. He likes that kind of stuff.

After the first part of the meeting, we got back into some campground and camp adilas stuff. See attached for a number of screenshots and an overview of where we are headed. Here are some notes from that part of the meeting:

- We talked about tons of options on different flags and tags. These could be things like notes, red flags, warnings, etc.

- Options for simple reservations and options for advanced reservations.

- Being able to collect vehicle information, customer information (counts and types), payment information, etc. There is some basic information and potentially, some more advanced or one-to-many detail information that may need to be gathered. Lots of moving parts and pieces.

- We talked about primary reservations, secondary reservations, and being able to stack and unstack those reservations and payments or deposits on the reservations.

- On the payments, be able to apply discounts to all reservations or just certain tickets.

- Be able to send out emails to help collect other information to help fill in the gaps and speed up the process.

- We got into some details on the different screenshots. Detailed site overviews, handicap accessible (wheelchair icon), color coding, using flags and tags, etc. On the color coding, we even talked about allowing the color codes to be setup using settings. We would set some defaults, but allow each company to change or alter those settings. Say something like yellow for partial paid, red for need to pay, and green for good to go (already fully paid).

- Chuck showed us some map options. He had actually used a drone to capture an aerial view of a campsite. We talked about all kinds of map and map overlay options. We talked about mixing maps, photos, icons, services, options, site photos, descriptions, filters, add to cart, set or choose date ranges, etc. All of these options, right from the map. Kinda fun. One of the cool ideas was using the icons on the map to help filter and show sites that matched your filtered search.

- We got into some of the other sub screens and talked about a customer info screen with flags and payment options.

- Lots of options for settings on a per section or per page level. That is awesome and we would encourage the development to be build off of settings.

- Be able to build your own reports and then be able to save those reports with the settings and configuration values needed. We already do this in places inside of adilas. Keep going along those lines.

- Showing reports on earning and services sold. Be able to see sales based on tents, RV's, cabins, firewood, power, and swimming. Whatever the services and/or options might be.

- As we build this business vertical out, it will open up new options for other companies that need scheduling and reservations. Good stuff.

- One of the last things that we talked about was using all of the different kinds of resources such as other developers, trainers, code, google, other team members, reps/consultants, etc. No specific rules there, just use what you need and play well with others. We want to keep it pretty open, but still make the resources available that are needed and wanted.