Zoom meeting with Cory, Steve, and Kelly. We were talking about sub inventory. Subs are great but do require more work and effort. Getting info in, out, reporting, and bulk updates and bulk tools. When we started, we didn't even know what was needed. As things unroll and unfold, we are beginning to see a bigger picture. That is awesome!

We have mountains and mountains of data. Now what?

As the meeting progresses, we spent some time talking about the challenges to sub inventory. Here are some of my notes:

- Sub inventory attributes and being category specific

- Settings all over the place - configuration

- What about changes, updates, and flipping categories (after the fact)?

- Possible mapping of categories, sub attributes, etc. Talking about mapping by id numbers and not names or column numbers.

- We need a sub inventory history section. Tables are already built, but they have not been tied in.

- Some of our clients want so much control

- Sub attributes, parent attributes, flex attributes, flex grid tie-ins, and other different levels or layers

- Master list of sub attributes and then repurpose those per category. This could be tied in with the mapping options listed up higher. Either start from the top (master list) and go down (what sub attributes are needed per category) or list out each attribute per category (current model) and then tie and/or map them back to a master type list. We may have to go in both directions. Just some thoughts.

- Kelly likes how parent attributes can be bridged over categories. Having said that, we need to be able to search by sub attributes, parent attributes, and flex attributes.

- Certain clients want to pull data without the category specific reliance. Basically, once we catch the data, we have to be able to let it be searched, pulled, filtered, shown, and exported. It's all part of the puzzle. Being able to get at and use the data. That's a huge key. Just being silly - ADILAS - all data is live and searchable

- Maybe upping the permission level to add/edit sub inventory or sub inventory templates or sub attributes. Once again, we need some histories of who is doing what in the system.

- Steve was talking about - 1. Capturing the data. 2. Then being able to get it back out (in any form - CSV, Excel, PDF, printable, web). and 3. Being able to play in bulk and deal with automation options. Those are some of the goals (small summary).

- We have people who are wanting to add certain sub attributes on the fly, as part of a sub process or sub phase. This gets into sub locations, sub phases, and sub processes and/or steps. Currently, we only show the subs at certain steps and make them go back to certain places to add/edit or update that data. There is a lot of manual work involved. How cool would it be if we could help them and let them setup their own processes, phases, and sub processes. Mini concepts of the data assembly line.

- There is a need for bulk update tools, easy flow processes, and being able to setup their own data flow based off of the subs or steps within a process.

- The use of templates to help control other actions, defaults, rules, and assignments. Having that example and/or template really helps answer a number of questions.

- We went back to the main need of being able to pull data out of the system (quickly and easily) - all data is live and searchable - We really need this and keep going with what we already have.

- Kelly and Steve working on advanced reporting and moving beyond a band-aid. What about going back and correcting the plumbing from the get go. Planning for the future.

- Need for more controls, handrails, and ability to scale.

- Build and break, build and break. Well, it's time to fix it again! it's breaking!

- What if we re-imagined it??? What would it look like? What things do we need to consider if we were to rebuild this out?

- Kelly was recommending that we get into a real life system to see the challenges. We made some plans to meet with Kelly again see the tools that she uses, how she uses them, and what is still lacking and/or needed.

///////////////////

This is more for me, but what are the next steps in the planning process for new phases, data assembly line stuff, and where do we want this to go? Help lead and guide it! Keep pushing for more bulk tools, bulk options, and bulk tools to add, edit, update, change, pull data in, pull data out, etc. We can do a bunch of things on a one-by-one basis, let's keep pushing that to the next level. Yee haw!