We had a bunch of guys on the meeting this morning. Sean and Marisa were asking questions about using sub inventory out in ecommerce. There are tons of different settings. Ecommerce was not designed for the customer to be super detailed, like they are inside the main system. Out in ecommerce, they just say something like - I want this and that. Behind the scenes we have to check packages, counts, quantities, and other availability. This makes it kinda interesting... We have to play in simple requests but record things in crazy levels of details.

Steve was helping to guide the discussion. He did a great job and it was fun to watch and participate. We ended up having Alan pop in and go through things. As he was talking, I was scribbling down notes, ideas, and such. There are so many moving parts and pieces. All part of the same game or same puzzle.

We got into some Metrc and state compliance issues and needs. We ended up checking out some data for a client. They had added things, removed things, set things to inactive, voided things, and adjusted quantities using adjustment tools in the system. A complex series of events and timing. Also, different things done by different people. Thank goodness for histories being kept and maintained by the system. We ended up having Sean and Marisa do some fixes and then reach back out to the clients to let them know (passing on the knowledge and info - training).

Putting in another plug for a couple of other things that we still need to build out and/or refine a bit:

- We need to add a history table for sub inventory. The table already exists, but has not yet been wired up. That would really help.

- A quick search tool for RFID tags, media/content (files and links), and sub inventory attributes and packages (batches). The quick search already exists, we just don't have those things listed in the available search options. That would be really cool.

- The story about what is happening is so important. Eventually, it will end at a certain state or status, but what happened to get it there is huge. That's where the history and story comes in.

- We added more to the known issues report and known issues list. This will become part of the master code branch so that we can gather up ideas and such. We are hoping to get this report and tool out soon. Still under construction, but coming. Yeah!

- Steve is doing awesome on JIT (just in time) project management and delegation. Super fun to watch him work today.

- Steve and Kelly were on a meeting earlier today - as part of that meeting, they were using elements of time (calendar objects) to schedule recipe/builds to happen on certain days (production). The elements of time hit the calendar and the individual elements of time had links to fire off or do certain recipes on certain days. Creative use of both tools and mixing them together. As a side note, we are seeing elements of time being used more and more to coordinate and orchestrate different pieces as needed. So powerful!

-  There is a value of group trouble shooting and putting the puzzle pieces together. Not too many, but enough!

- Some of the jobs and tasks require planning and even pre-planning.

- We deal with moving targets all of the time - static (non moving) vs dynamic (constantly moving)

- Out in ecommerce, we have different levels. Inside the system, we help take the users into deep waters, based on permissions. However, out in ecommerce, we need to keep it simple (customer view and customer level), yet eventually we need the deep water info. What do we automate and what do we leave or make as a human type interaction? There is a balance and not situations are the same. Wouldn't it be cool if we could virtually setup the data assembly line with automated tasks and manual entry tasks. We can do that, but we have to be involved every time. Wouldn't it be cool if we could build the tool to help configure things as needed and have it all tied into the big picture software package or system app. Let's keep working towards that!