all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
Yellow
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Uploaded Media/Content & Other Files
(6)
|
||||
| Media Name | File Type | Date | Description | |
| talking_about_mini_conversions.txt | Doc/Text | 2/23/2017 | These are some notes that I took while on a GoToMeeting session with Calvin and Steve. Just trying to catch some of the questions, ideas, and scenarios. This deals with QR codes, mini conversions, and transactional details for subs of subs. | |
| steves_mini_conversion_page_for_qr_codes.jpg | Image/JPEG | 2/23/2017 | Steve's mini conversion page to help with building custom QR codes and doing mini conversions. This was an early prototype that is helping us know where to go. Here just as a reference. | |
| small_drawing_of_the_new_conversion_transactions.jpg | Image/JPEG | 2/23/2017 | This is a small drawing of the mini conversion transaction details. It shows a small stacking order from PO, to PO line items, to parent inventory, to sub inventory. The drawing then shows a small grid (table) like structure. We were just brainstorming on ideas. The table captions (column or field names) are listed at the bottom. They are things like: auto id number, sub inventory id, how many were made (actual production or creating process), how many were sold (physically on an invoice), how many were quoted (on a quote), how many were added to the cart (queued up and claimed), real unit of measure, real quantity, visual unit of measure, visual unit of measure name, price, etc. Just playing with ideas... Nothing set in stone at this point. | |
| stacking_parents_childs_and_conversions.jpg | Image/JPEG | 2/23/2017 |
This was a drawing to show the relationship between PO's, PO line items, parent items (parts), child items (sub inventory), and then into conversions. We talked about taking the conversions into a vertical level and actually adding a table to hold the conversions and mini transactional details of what is happening. In the graphic, there is a horizontal arrow and sub inventory attributes. That is what is currently happening and how we are attempting to solve the problem of conversions right now. The problem there is, we have too much data that is needed to be stored and we are relying on a user/client to set up the correct fields. Very limited in option and nature. We we want to go with things is in a vertical or normal database one-to-many type model. If we build a special table for mini conversions, we can capture changes in a just in time fashion. We also gain a set of columns, rows, and tables that are designed to specifically hold mini conversion stuff. This drawing also talks about treating conversions in _z or Z axis of the 3D world building model. This is layering, stacking, and organizing of sub data. We also talked about the virtual data assembly line, checkpoints, permissions, flow, etc. The goal is to catch the data, make it easy to look it up, record the story of what happened to a child item, and then be able to look things up by the mini conversion id numbers. For example `77 and `78 in the example shown. Those would be new records that hold mini conversion info. |
|
| converging_projects_for_selling_items.jpg | Image/JPEG | 2/23/2017 | This is a small drawing of multiple projects all coming into play at one time. They are: smart cart logic, sales and promotions, custom labels, sub inventory, mini conversions, discounts, tiered pricing, loyalty points, and other special account tracking options. They all seem to be interconnected and needed for the full point of sale (POS) side to work correctly. Interesting. | |
| QR codes and mini conversions - Part 2 | Video | 2/23/2017 | This is a GoToMeeting recording of a meeting between Calvin, Steve, and Brandon. We were going over QR codes, mini conversions, and how multiple different pieces were all coming together into one section and/or hitting at the same time. Good discussion and notes on questions and ideas on where to go with things. | |
|
Notes:
|
|
On a GoToMeeting session with Steve. Calvin joined us just after 11 am. Steve and I started out the morning and got his new report pages up and running. We had to add some variables to calculate some totals. After that, we reviewed an older video and took notes from a prior session between Steve, Calvin, and I using QR codes to do mini conversions. We took some notes and tried to prep for a meeting with Calvin. See elements of time # 2157 and 2167 for notes and other ideas. This current element of time has a number of media/content pieces attached. There is a video recording of the session between Steve, Calvin, and I - It has some graphics, drawing, and some notes. We attached all of those pieces, graphics and notes from our session. The whole thing was dealing with QR codes, mini conversions, sub inventory attributes, breaking things into smaller pieces, and other incoming pieces. Good conversations. Here is a link to the media/content for this element of time. It has tons of special notes about the graphics, the actual notes, and the video link. Please read the next page to get a deeper look at what was being discussed. - A couple of things of interest were... horizontal recording of the data (fixed columns) vs. vertical recording of the data (dynamic one-to-many database records). We want to go vertical as much as possible. It keeps the relationships smaller and tighter. - Dynamic flow and/or processes - We what to allow our users/clients to define what their virtual checkpoints are. This relates back to the data assembly line concept. If we can define the checkpoints, it should help with flow and quality control. If we could set those checkpoints up dynamically (customer flow) that would be awesome. - The power of a relational model. Instead of duplicating tons and tons of data, you just create one-to-many relationships and allow the data to flow both up and down the chain. You only store what you need vs. a huge pre-set grid and/or matrix. It stays small but you still capture all that you need. - We are seeing a converging of many projects for the POS (point of sale) system hitting or being worked on at the same time... They are: smart cart logic, sales and promotions, custom labels, sub inventory, mini conversions, discounts, tiered pricing, loyalty points, and other special account tracking options. See media/content for a quick drawing of the converging of projects. |