It's Monday. Josh, Dustin, Steve, and I were on the morning meeting. Josh checked in and we set up some time to work on merging in his discount engine stuff. We added some new permissions and created a new help file for him to populate. We are hoping to get all of his code rounded up and populated within the next couple of days. Good stuff.

Steve's summary from January - Mrs. Shari O. needs some help. We've got that going and Pat will be helping out. We need to make it easy, pretty, and powerful. Steve would like to circle back around and then we need to do some look and feel stuff (make it look pretty). We will keep building out the functionality but we really need it to look nice and appear more simple. If we can get the current model, more spiffy (nice looking), we can really wind some things up. It is a very abundant model. The future of SaaS (software as a service) is customization. People want to start very simple and slick but as they go, they start looking for more functionality and eventually really want it to be their way (custom code and customization).

What do people do the most inside our system? We can pull in stats from all of the servers and then look at them (the stats) side by side. We could then have Russell go in and help us with some cool look and feel on the top 10 pages. Once that is done, we could keep drilling in deeper and deeper.

Alan popped in and gave us a report. Steve and I were working on different projects. I'm working on checking in code that Will did for a thing called transitional PO's. The new PO type is between an order/request (not tied to inventory) and a live PO (fully tied to inventory and payables). The new transitional PO's allow for pre-payments (assets or pre-payments on inventory) and will be tracked on the balance sheet differently. The project has about 22 pages in it. Just going through and checking out code and adding my own flair to it.

Molly and I met for about an hour to talk about options and possibilities for ICC's or internal cost corrections. She started out saying that she has worked with a number of clients and sometimes it takes up to 20-30 hours to do some clean-up (depending on the size of the client and how long its been since the last cleaning). As a side note, we see bigger problems with normal parent inventory due to the last known cost that is held at the parent item level.

Sub inventory is much tighter and works pretty good. The only known problem with sub inventory deals with some rounding error problems over time. Basically, by the time you split up certain known costs over and over again, clear down to 5 levels of decimal accuracy, there becomes a small rounding error for certain items. It is just math but it still ends up looking like a problem.

The catch 22 is on what it takes to look things up and fix them. On parent inventory, Molly goes and looks at the usage per item. She can then fix things fairly quick. On subs, there are much less problems (originally), but sub inventory is even harder to clean-up due to closed packages, parent item settings and status, and some of the math.

The main goal is to get the cost of goods perfect and/or help the user get to a perfect level. Ideally we would like to build out a new core tool called ICC's or internal cost corrections.

Molly would really like it to follow a FIFO (first in first out) type model for costing. This would require us to be able to go all the way back in time and see what came in and at what cost. It would then try to reconcile itself based on how many have been sold and at what value. For example: if we start out with a 100 at $0.45 per, ideally, we would sell the first 100 items for that $0.45 cost. It gets complicated as things change over time, we don't fully sell out of a specific quantity based on cost, or a person buys multiple things from different cost levels. We have also had problems with users just going in and randomly changing item costs.

- At some point, we need to make an adjustment and/or update to the COGS (cost of goods sold).

- Molly was talking quite a bit about the in/out extended cost. We had some discussion based on FIFO vs last known cost.

- Molly and I were trying to figure out basic rules - only grab items that have an in/out extended cost that is not zero and a quantity that is not zero (don't worry about items that match perfectly or have zeros). If an item has a quantity (+ or -) - we need to look at it. We may need to work backwards to get our numbers.

- We also had some discussion about are we trying to get super detailed (matching PO's with invoices with costs) or be more general and just get the grand totals correct per item? Good discussion. We left off with Molly going to reach out to Eric to see if he has more time to meet and work on a tool/report to help fix things. I am supposed to think about options and come up with some ideas. Lots of moving pieces.

Met with Bryan a couple different times. We were working on some dynamic JavaScript that allowed for a loop to take place over query results, build a dynamic link or URL (web address) and pick up a user selection that may change based on the users input. Long story made short, we were mixing HTML, JavaScript, ColdFusion, and SQL query output into a series of conditional links. It got pretty deep. This is part of his cross corp mapping project.

In between our sessions and after the last session, I spent some time recording notes and filling in things from today's meetings. Busy times.

Steve had some questions. We worked through a looping problem. Bryan Dayton popped in and we went over some cross corp mapping and options. Some of the clients want a bulldozer type approach (force things from one corp into the next corp) and we would like more of a mapping (strategic or more precise movements) type flow. We made a few decisions and Bryan is going to release a dual option (force it like a bull in a china shop and gentle like a dove).

Josh and I jumped on to look at some code for his discount engine and sales tool. We modified a few things and then started testing. My browser and version of ColdFusion were kinda old and he was using some of the latest and greatest new features. We got to a certain point and I basically said, you may need to talk with Alan as he has all of the latest and greatest features and versions of software. So, long story made short, I helped on the logic side and then was unable to help on the full testing side due to software versions and what not. Great session and we made some progress.

We got a report that there was a problem with selling out stock/units from the data 0 box. I went in and looked around. I re-uploaded the page that was throwing the error. I tried it and it still didn't work. I did a remote login on the server and found that a single table was fully locked and set to read only. I pulled a known value and then tried to change it. The error came back as the table was set to read only. I called Alan and sent a text to Wayne. Alan called me back and said that I would have to reset the MySQL database services (quick turn on/off of just the database). I did that and it seemed to fix the problem. Just wanted to record that for future use, if needed. 

Keep following up on graphical sales flyer, custom emails, and adilas market.

Shannon and I started re-watching the video of Kelly Whyman doing a presentation from the Denver training event. See this element of time and look for the afternoon video on day 3 - the actual start time of the Kelly portion of the video is at 2:33:19 (ish) - https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=3957

- One of the first things that she does is get the physical process that really happen and then she breaks those values into a work flow and defines who is going to do what?

- Setting and maintaining the expectations. Owners and operators are different. If things are too complicated, they, the users, stop putting things in.

- There are those who are good at frontend, backend, and maintenance. Different skills, talents, and interest levels.

- Shannon and I talked about "getting an investment approach" where the clients see what other successful people do. This was talking about other skills such as training, setup, maintenance, consulting, overseeing, etc. Ongoing help and other services.

- The setup and initial portion of the client's implementation is very important. They may need some ongoing oversight and/or help. How am I going to support you to get to your goals. Ongoing relationships.

- Try to operate out of the box first and then customize from there. Sometimes they jump too early on the custom bandwagon. Everybody loves the idea of custom but it can be a two edge sword. There might be a difference between small customization vs full or huge customization.

- Are you really ready to take on adilas? Is this the right system for you? You have to really want this (data feeding game). We talked about can's and should's... cost/time analysis.

- Maybe a way we can differentiate ourselves is based on concepts. We love talking about 3D world building, systems, interconnected data relationships, digital story telling, permissions & settings, and objects and data over time. There is an older PDF flyer that has a fun math equation of :: "Results = Mix(Functions, Players, Concepts)". See this older flyer for more info: https://data0.adilas.biz/adilas_formula.pdf - Good stuff.

- Sell the sizzle

Anyways, Shannon and I only made it part way through the video from Kelly. We had some good talks and we have some homework to keep watching and taking notes. We will touch base again next week on Tuesday.

On the phone talking with Shari O. She called and had a request/question. We got it resolved and then did some talking about the adilas team and how people are coming together. Shari O. is doing a great job and is helping new comers have fun, get connected, and share in tasks and information sharing. I'm super excited and she is doing awesome and creating a fun team dynamic. She gets my vote. Yee haw!

Back reviewing video content from a training video and a presentation done by Kelly Whyman.

- What kind of a setup is it? Coming off of another system, brand new, a recovery type scenario? Fresh setup, new implementation, or a clean-up.

- Corp-wide settings and what you call things? Speak their language and setup an internal glossary.

- Sharing information back and forth. Build the team.

- What are your goals and how are we doing on those goals? Sometime the first quarter is pivotal on if they like the system or not. You have to be there (physically at times).

- Templates and standardizing things. Using bite size flow charts, lots of drawings, etc. Show visual diagrams and then relate it to the system. Start out of the system and then go back in the system.

- No more than 60 to 90 minutes per session. Do a session and then allow for some Q & A.

- Help them learn that mistakes are ok and then how to correct those mistakes.

- When getting a client started, do a once a week follow-up and/or training session. After a few of these, they may not need them as often.

- Recording training sessions and share them - avoid being a broken record.

- On a demo, who am I speaking to (owner or operator)? She usually does a 30 minute consulting meeting and then she gears her demo based on that.

- Talk about the life cycle of different things... there is always a start, one or more steps, and a finish. Sometimes people love seeing that full life cycle.

- 4-square diagram - PO's, Invoices, Expense/Receipts, Deposits - use positive and negatives and explain it really simply. How do these values affect inventory or banks. This is a great simple process of what really works. These are the big 4. So many things play into the mix.

- On tech support - a quick response can help eliminate the escalation of the emotion - sometimes that is where the problems are and/or where their roots are.

- Defining the rules and expectations early on help to set the ground rules

- How much do you want to work? There are tons of options, but it is important that you define those rules and guidelines. If you don't define those goals, it could run you over... literally.

- The language that we speak between developers, consultants, and clients. We all have to play in the same area and define who wants what, who is going to do what, and who is going to fund what? Once we answer those questions, we can move forward.

- When you are onsite with a client, you will get spun in multiple directions... lots of moving pieces. We need both women and men working together to make the team stronger.

- Adilas has and does create a community of independent parties. Working together and sharing values and ethics. Good stuff.

Dustin and I were on the morning meeting. Pretty quiet overall. I started working on a custom invoice for shipping and work orders for a client.

Josh and Eric popped in. I helped Eric with a small bug in his sub special account tracking project (loyalty points and gift cards). After that, Josh and I spent almost 2 hours doing some code review on his discount engine. We spent most of the time working on the action page (add/edit and committing to the database). It is looking good and really coming along. This is the first major tool that Josh has created for adilas. Sometimes those first code reviews take longer just learn each other's style and way of coding. Good meeting.

As a random side note, some of the developer like using Zoom more than GoToMeeting. Some of them say that they have less of a delay when using Zoom. Interesting.

I got an email from a client and they needed a number of invoices voided out. They were running into an error and a page redirect. I went in and look at it and we needed to alter some internal code. I made the changes, tested, and uploaded a new void item file. I then voided out all of their requested tickets and added notes.

Bryan and I jumped on a GoToMeeting session. He got his cross corp mapping code ready for code review. We spent the first part of the session going over changes and doing light clean-up. Once we got things merged in, we then invited Molly on to help us look things over. Almost immediately, we ran into a new request to provide a corporation to vendor cross corp mapping. This new project already does a number of cross corp mappings from items in one corporation to items inside another corporation. It was kinda funny that almost immediately we needed another cross corp mapping.

One of our goals deals with the application flex grid (interconnecting or mapping anything between corporations or even between systems or software platforms). This is kinda still a dream, but we are making progress and seeing more and more needs for this kind of thing, function, and/or tool set.

Calvin and I jumped on a Zoom meeting. He is working on pulling in label values for invoices and invoice line items for his adilas label builder app. Tons of data and it gets kinda tough to cycle through and figure out what is needed and what is not needed. It gets pretty deep with multiple queries and multiple one-to-many relationships. Most of what we were talking about was strategy on how to gather, filter, and only advanced data that is needed. This is stuff that makes your head hurt... :)

Everybody is feeling the pressure. Lots of requests and requirements. Steve and I were talking about priorities and how to manage the amount of inflowing requests and requirements. Sometimes it is literally disabling in some ways. Pretty crazy. I'm so thankful for the people who are helping but even that is a challenge at times.

Dustin and Eric popped in and reported. Eric is feeling swamped as well. We had some more talks about priorities and what not. Lots of moving pieces between internal projects, customer projects, 3rd parties, bug fixes, maintenance, and client demands. Everything tends to work out.

Josh and I worked on getting his "set manager discounts (discount engine)" tool up and ready as a beta release. We went through the code, made a number of changes, and did some testing. Great meeting. This is Josh's first core adilas piece that is being launched.

By the time we were done, we were able to merge in his code to the master branch. We had to run a database update and activate a permission. All servers got new code and the database updates but we only pushed the permission on data 0 and on data 3. Josh has a client who has volunteered to help beta test his discount engine. Our plan is to help all servers go live on Monday with the new discount engine.

The new discount engine allows for a discount/campaign to be named, set a percentage off or dollars off, tie it to a customer type, a part category, or an individual item or part. The engine also allows for date/time discounts including daily, specific days of the week, and even time based (every Tuesday from 4 pm to 6 pm).

The other cool thing is the system is actually setup to add discounts on discounts up to a set max. For a beta release, I'm happy and I know that Josh is super excited. We'll do some fine tuning and then do a full release. We also talked about some possible video clips and maybe some tutorials. Exciting.

Recording notes, emails, and tech support. Finished up a custom shipping invoice for a client and posted it online.

I got into the meeting a little bit late. Steve and Dustin were working on some things. Once they were done, Wayne began reporting on some of the new AWS (amazon web services) things. We were talking about moving some of our existing pieces (server stuff) over and across to AWS and then tweaking things from there. Lots of options to help optimize things. There are so many things on the virtual to do list... we'll just get started and then go from there.

We are also excited to start seeing real costs and real usage patterns. This is both internal and external.

Wayne and I spent a couple of hours going over tons of things... data servers, content servers, images, corp-specific folders and storage, session stuff, security hashes, Windows specific code, and tons of other things. Super good meeting.

Steve, Josh, and I ended up having a discussion about the new discount engine (new code that is being released) and wanting our clients to move from Classic to the Snow Owl theme. We have so much more functionality on the newer Snow Owl theme. Some people are too busy to switch, some are just unsure, some think there are issues, etc. We would really like to use the discount engine to help us transition those users over to the newer look and better settings.

It takes a village to do some of these tasks and things. Delegate, empower and get out the way. We keep building and tearing things down. That is part of the process. We have some great people all around us. Let's keep feeding those fires. Yee haw!

Paying bills and other to do list things.

Steve, Bryan, and I went over some of the cross corp mapping stuff. We got in pretty deep. We kept coming back to the top-level vendor to corp mapping. Sometimes we have to kick things around quite a bit before we really either understand things or nail them down. Before the meeting, Steve and I were talking about needs for the application flex grid (any system to any other system).

Calvin was giving Steve and I a demo on the adilas label builder. He was showing us new label options for invoices, PO's, and items. Prior to this, he only had customer info ready. Good progress.

Steve and I started out together on the morning meeting. Just the two of us and we were talking about who could handle what projects and how do we feel about each person and their load/contribution. Good talks. Steve and I also worked some code and some new logic that he needed for some clients in Oregon. After that, I started to rework a sales flyer the Naters did with the adilas doggie images.

Josh joined us and had some questions about how the current discount logic worked inside of adilas. The most confusing part was dealing with a tax category of with tax included and a discount. We went through a number of scenarios trying to get certain numbers. We kept running into math errors and unexpected outputs. We called in Alan and he looked around with us. As a side note, discounts get super crazy deep, especially when mixed with back calcs like with tax included or back figuring to a known target value. We made a number of tweaks and did some testing together. I fixed one file and then we planned on letting Alan go in and make some other tweaks, including some display changes to the advanced add to cart pages.

See attached for the graphic of the new sales flyer with the doggie images.

Eric and I hooked up and did a small session. He was having a login problem switching to a new code base from the repository. We fixed a couple small issues and the other one we at least got to a starting point (where to look for the problem). We also lightly spent some time talking about primary navigation for the sub special tracking accounts (where to put links and such) for things like loyalty points, gift cards, etc. The other thing that we did was setup some time blocks to work on the sub special account tracking project. Eric also has some new 3rd party solutions that he will be working on and coding. We talked about some options there.

Shannon and I got together over GoToMeeting to work on some concepts and verbage for a new sales flyer. We reviewed some notes from last week (Elements of time id's 4348 and 4371) and talked about a lot of concepts. See attached for a couple of the ideas. 

Working with Bryan to go over some of the cross corp mapping stuff (start of the application flex grid).

Got on a Zoom session with Calvin to see some progress on his adilas label builder app. He had added in some quantity options for parts, PO's, and invoices. He also showed me some other features such as about (light marketing stuff) and options to reroute back to the start to do a different label. He is making progress and we scheduled some more time for tomorrow.

Nobody was on this morning, right at first, so I took some time and finished up some notes from yesterday. Alan popped in and showed me some progress on the in-line discounts with tax included. He reworked the JavaScript on the advanced add to cart and advanced edit cart line pages. It looked good and we virtually kicked the tires quite a bit to test different things. Good stuff.

Eric and I had a good long meeting. We started out and just touched base. We then jumped off the GoToMeeting for a special client Zoom meeting. We met with a company and talked about 3rd party solutions, API sockets, and ways to integrate between the two solutions. Part way through the meeting and presentation, they, the other company, pulled in one of their main tech people. We then reviewed and somewhat started over. Minor detail.

After the client meeting, we jumped on the 3rd party project and went through all of the pieces. After we were done, Eric was saying that he would like to do more of this type of work. He was getting it and enjoyed it. I also saw him do some clean-up from other developers as he was working. I was grateful for that.

The last couple of hours was spent on the sub special account tracking project (loyalty points, gift cards, etc.). We went in and added some navigation from about 4 spots inside the system (ways to get to the master special accounts and ways to get to the corporation level special accounts), we tested it and then started working on other logic pieces. Good work session.

Calvin and I worked on his adilas label builder app project. His first round project is getting close. We moved out of his Windows based app (the actual label builder app) and into the web and tying the two programs and platforms together. The label builder is very powerful and dynamic. Anything you can think about may be added to the labels. That includes any number of graphics, lines, QR codes, barcodes, static text (fixed values), input text (open for typing), and dynamic text (pulling in data from a database). Any of these things may be used in any context and any number of times. If you wanted a label with 4 different barcodes on it, no problem. Pretty crazy.

Anyways, our new goal is providing a way for us to connect to user data (normal adilas stuff like PO's, invoices, items, parts, customers, etc.) to the power of the adilas label builder. We went into adilas and determined about 7 access points for the custom labels. Calvin is going to start working on those pages and passing information from page to page to start sewing up the functionality. Great progress.

After working with Calvin earlier, he gave me an assignment to help prep a new page for him. I built him a new page that was black box ready and had a number of basic adilas features built into the page. I sent them over to him to help him get a place to start coding and integrating the two products together.

I got an email from Josh about a few new changes that needed posted online for the new discount engine (still in beta release). He has a demo and some training with a client tomorrow and needed a couple small tweaks. I went in and made the changes and modified a few things. Merged things in and pushed up new code to the servers. Let Josh know that he should be good to go with his training and demos.

The morning meeting was with Steve, Eric, and I. Most of the time we were just working on individual projects. I was recording notes from yesterday and Eric was working on his sub special account tracking project. Eric would ask small questions here and there as we were working. Steve reported on a few things and then had to take off. Fairly quiet meeting.

Eric and I were working on his project. I ended up on a call with Calvin and going over some of his adilas label builder stuff. As it progressed, I ended up flip flopping between both Eric and Calvin answering questions and helping them here and there.

Bryan and I spent the first hour working through a small flow related bug on a 3rd party API socket to auto add a customer based on a phone number and then add then to the customer queue. We fixed and tested the API socket calls and pushed up new files. We also altered a few of the error messages to help give some more information about what was missing and/or needed.

The second hour was spent on the cross corp mapping project (starting of the application flex grid stuff). We were deep in sub inventory land going over parent items, child packages, sub inventory attributes, and then custom dates, custom text entries, and custom numeric values. It gets super deep (quickly). Anyways, the best thing we did was write out some scenarios in plain English to help understand where the different parts and pieces comes from and/or go as a destination. Lots of good progress keeping it simple vs trying to write code without understanding the flow of data first. Anyways, good meeting and making some headway.

Wayne jumped on and showed Steve and I his first instance of adilas running on an AWS (amazon web services) setup. We had a few small glitches, but great progress. Wayne showed us around and how he could virtually set timers, watchers, and virtually dial in needs based on usage and/or preset timers or requirements. Huge paradigm shift in our thinking.

Both Steve and I spent some time bouncing through pages and doing light testing. I made a small document with a few of the light tweaks that may be needed.

Eric joined the meeting and had some questions for all of us. He got a new database from Wayne, had some 3rd party solution questions for Steve, and Eric and I talked about our plans for the next couple of days.

After the main meeting, Steve and I chatted briefly about new options and where things seem to be headed. Lots of new options are starting to pop up. Exciting, but it will take some management to really make them fly. Good stuff.

I got an email this morning requesting a way to show/hide the general units of measure. We have about 30+ standard units of measure such as inches, centimeters, grams, ounces, pounds, gallons, etc. Tons of standard type options. Anyways, we had a request where people could show/hide (virtually turn things on/off) based on a per corporation basis. They can currently make and/or create their own custom units of measure, but they have no way of manipulating the general list that we provide.

For example: Say you have a company that only deals in each, grams, and ounces... they may not want liters, dozens, feet, ton, etc. We already do a similar thing with money types (forms of payment such as cash, check, visa, mastercard, gift certificate, etc.). The new request would be to do a similar thing with the units of measure. The existing page top_secret/secure/money_types_select.cfm has a list of all existing money types and then allows for show/hide checkboxes to shorten the lists. We would want something similar to that type of an interface.

Also by way of a note, we then went to all of the pages where those list show up and added some look-up code to help limit the view of those selections to what has been virtually turned on/off. Everything still exists, we just strategically hide/show the correct values.

Emails and tech support. Steve and I got on a meeting and worked through some code to help store default unit of measure settings per item/part category. Towards the end of the meeting, we started to add the new code to the submit cart page that passes the new data out to a state compliance party called Metrc.

Busy morning. Dustin, Steve, and I started out the meeting. We then had Alan join, Eric join, and Josh as well. Steve and I worked on some new code together. I then passed it over to him to test it. Alan reported on where he was at on certain projects. Josh had some questions for Steve and Eric and I worked on his sub special account tracking project (loyalty points, gift cards, etc.). A big majority of the time was working with Eric and making sure we could get his new database install up and working. Because we brought things up from the ground up, it uncovered a few things with our current project. Good progress all around.

Eric and I were working through some database settings and changes. Eric has a brand new database from Wayne and we are lightly refining it and helping it to be more stable and ready for use.

Steve had me do a code merge and we got some new files pushed to all servers. As a side note, he has already done over 30 code branches on his own. Most of those branches had 20+ files per branch. Good stuff.

We are trying to boil things down for a sales flyer. We are wanting to work more on the core concepts and build a why and what are we trying to do flyer.

Working with Bryan to go over cross corp invoices to PO's and mapping things all the way down to sub inventory. Super deep wire job.

Hopped on the morning meeting with Dustin. Just the two of us were on there for the first part. Dustin had some questions about some of the reports coming off of the cultivation homepage that he and Steve were working on. We ended up talking about having a plan and really knowing where the different pieces either are and/or should be. Knowing is half the battle (old G.I. Joe quote). If you know what should happen, then you could go back and actually check that. If you don't fully know, how are you supposed to check and/or verify what is happening. You've got to know and/or have a map of sorts.

Wayne came on and gave a small report. He is making good progress on the AWS stuff and reported on some custom tags and ideas on doing unit testing using a special framework and program. Most of our testing will be in ColdFusion but some of it may end up being in Java or some bigger or more robust language.

Eric and I got together and worked on his loyalty points code. He is at the level where he is testing automated add processes (attributing loyalty points based on an invoice) as well as using reward/loyalty points as a payment type and adding in records to take away and/or remove available points earned. Good stuff.

Met with Calvin over a Zoom session. He was showing me progress on the adilas label builder. He is now working inside of adilas and doing connections, links, forms, and API socket calls from adilas to his label builder program. He has it working locally on his machine. I gave him a few requests/suggestions but it is looking good. The next major step is building a Windows service and being able to do the same thing live on the adilas content server (where we will serve up all of the custom PDF labels using his label builder). I authorized him to keep going and sent a small update over to Steve.

Bryan and I were in deep looking over cross corp (invoices to PO's) with sub inventory and sub inventory attributes. Deep crisscross mappings. We did some drawing and even created some sample code with id's and what data is tied to what fields (scenarios and samples). Mostly an educational and exploratory session.

Calvin and I met up and he gave me another demo on his progress for the adilas label builder. He now has a web-based system that collects user inputs and quantities and passes that data over to the label builder app.

Steve and I were talking about where we are going and some of our vision about getting there.

- Sometimes we get new users started by setting up vendors, adding people, and bringing in inventory - it then branches all over from there.

- We were talking about how complicated the system is and/or perceptions of how complicated things are. Very interesting.

- How do we focus... sometimes it seems like we are all scattered all over the place.

- The difference between working in your business or working on your business.

- The need for a new paint job and adding in virtual guard rails.

- Maybe even hold hands and come up with a joint venture type project. Redesigning some of our old standards and making it look newer and be easier to do and use.

- Triage - in medical terms... what is the best use of our time and what would be the best outcome? Imagine limited resources and tons of needs and/or demands... what, who, when, why, and how much? Ok, now that you have a plan, work that plan.

- We were talking form and function and the correlation between operations and accounting... Operations want it quick and dirty (super simple - form). Accounting wants it tighter and more detailed (function and depth). It gets interesting trying to mix things. So, if we want to do a redesign, lets start with the operations side things.

- Steve passed me over a link for some new learning - https://gridbyexample.com/learn/

- Start scheduling time to do the rework projects that we want to do (triage style). We are in charge of what we really want to do (in some ways). Schedule some time to work on some of the look and feel.

- Summary on the sales side... lets bring it up and make it look pretty (first impression). That would really help it sell better. Choose to work on the look and feel and flow process.

- We miss Russell. He really helped push us to some new levels.

- We have some coding standards... we would like to get some good look and feel standards.

- Use technology to help you cascade the standards, the style, and the functionality.

- Sometimes it takes hours of poking around and research to figure out what we want and even what is possible.

- We may need to get back to a tick list and then setting the priorities. This is something that Steve and I used to do back in the day. Simple spreadsheet and make it available to admin, developers, reps, consultants, etc.

- Bottlenecks and burning platforms and working through those things.

Eric and I were working on his sub special account tracking project. I got on his branch and started to go through the first database update page. Meanwhile, Eric was still working on more tweaks and deeper in the cart logic.

Russell got us started with some CSS templates from bootstrap and Inspinia. Go buy the templates and then use them in projects. There is also a guy by the name of Spencer that has some CSS skills and works with AJAX and jQuery. It may also be beneficial to do some studying on normal JavaScript. That seems to be a good base level for some of these other languages.

Bryan and I met and talked about his cross corp mapping project. We decided that he was going to put it up online for a few users to test and then get back and push it up to all servers. We are making progress.

Monday morning... here we go again.

Steve, Dustin, and I were on the morning meeting to start with. Each of us has our own to do list stuff. We touched base and then started working on our different projects. One of my projects for today is to take all of my post-it notes on my desk and put them all on one giant to do list and/or tick list. I only made it through a couple of post-it notes before I got pulled off that project to help with another one.

Eric joined the meeting and had a number of questions about the sub special account tracking project and some decisions on how and where to do the safety checks. We got in to it and decided that he would need both local validation and server-side validation. We talked about mixing JavaScript (local) with ColdFusion (server) and how best to do that. I showed him some examples and pointed him in the right direction.

Calvin joined and had some questions about direction and working with multiple servers. He is working on the adilas label builder app and wizard-type project for custom labels. Steve and I setup a demo for tomorrow. Calvin also needed some help accessing some live data to do some tests and what not.

After that, I went back to adding in to do list items on the big spreadsheet. I paid some bills and light tech support stuff. One of the tech support questions was dealing with custom field settings for customers. This has been somewhat of an issue since 2016. Long story made short, we added a page where a user can change names, show/hide, sort, set defaults, require, etc. for basic customer fields. That options exists on one page... it also only applies itself to just one page. The problem and/or request has been, why don't you cascade those settings all the way through the system? To answer that, I would say, we would love to... it just takes time, planning, a goal, and funding to get it done. We would love to finish some of those things up.

Towards the end of the call/meeting, Steve and I talked briefly about priorities and needs within the system. Lots of demands and we have to manage the resources based on both internal demands and external demands on the same resources.

4/3/2020: Breaking this into parts to get some done. Client is billed 2,000 to get this to work for terms field only at this time.

See eot 989 inside of adilas (on this list)

Terms is not dynamic- you edit the customer settings and it shows in the customer but not in the cart, for example. It is hard-wired currently.

Allow people to turn things on/off. Too many fields 

Eot 4427 in developers notebook

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=4427

At some point, we want to circle back around and rebuild a bunch of the pieces and how they act and interact. We would like to call this new rebuild "fracture" or something to that effect. Anyways, here are some brainstorming ideas on the fracture pieces that we would like to sew together. No specific order:

- object oriented approach (objects and data over time)

- use teams and different talent pools

- ice berg vs mountain type analogy (what is being exposed and what are the perceptions - visual exposure)

- settings and different setting levels (corp, group, page, user)

- subs... of sub (everything is fracturing into smaller and smaller pieces) - plan for it and embrace it

- API socket connections and external work flow options

- database scaling (corp-specific databases or corp-specific database tables)

- real in-line database extensions (add/edit/remove database fields and help them flow through the whole system)

- 3D world building - keep going and building out these ideas and concepts - one step at a time

- data assembly line(s) - concepts of tracking phases, grouping, sub locations, allowing flex and checkpoints, permissions, mapping to financials, etc.

- using time or elements of time as a base level and then mix, blend, and share sub functionality and tracking options (more objects and data over time stuff)

- funding and making sure we can fund the planning, design, and development of our game plan

- help files, videos, and SOP (standard operating procedures) - standard and custom

- black box and ways to customize the pages, verbage, logic, and process flow

- summarized data (aggregated data) vs transactional data (all the steps and transactions) - we need both - watchers, feeders, and triggers

- following and dreaming the dream - it may sound way out there... but following that dream is huge

- make a visual plan

- include general testing, unit testing, validation (local and serer-side), and standardizing requirements

- version control and deployment

- going back and doing research and review of older notes - tons of mini gold nuggets to harvest from doing this over the years (make sure and harvest some of our own ideas)

- use of sub homepages and graphical hubs of sort - also use graphics, charts, graphs, and other elements

- summed up data with drill-downs or searches available (basic or advanced) - approach all most everything from a summed up version into a more expansive (expanded) view and/or format

- be able to export any data to CSV, Excel, PDF, and general web format

- smaller mini functions - getters and setters - for miniature database access and updates

- use sub flags, tags, and other similar features - lots of ideas about sub phases, sub groups, sub locations, sub flags, sub tags, sub progress, etc. Lots of prior documentation on elements of time and subs of time, including how to virtually adopt functionality between main player groups (invoices, deposits, expense/receipts, PO's, customers, parts/items, stock/units, vendors, employee/users, quotes, elements of time, balance sheet items, etc.)

- custom look and feel - able to match moving trends

- responsive (able to change size and layout based on device or screen size) - mobile development

- sales - how are we going to market and/or sell our products and services - how are we going to set things up for correct billing and tracking (usage, storage, bandwidth, queries, connections, data, files, images, etc.)

- communications, push/pull notifications, automated things, queues and scheduling tasks, bulk and individual communications

- good project management

- sub permissions - almost down to the function type level (as needed)

- dynamic verbage, custom layout(s), dynamic link builder (favorites), and simple look and feel

If you are looking for other ideas for the fracture account stuff. See this URL or web address: https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=fracture

Meeting with Bryan to go over some changes that he was working on for the cross corp invoice to PO's functionality. That code is super deep and deals with all of the normal crisscross relationships plus do the same thing for cross corp (or between worlds). Super deep.

Steve and I looked at some complex code together. He is working on a new custom gram control widget for a client. The new widget goes clear down to a sub inventory attribute level to get an effective weight value per package. Deep way to figure out a calculated weight.

Wayne and Steve were having some good discussions on the new AWS (amazon web services) stuff. Lots of talk about bringing new corporations on and getting them all setup out in the AWS landscape. They were even talking about rewriting our API to match the AWS environment in a better manner.

Calvin was giving us a demo of his Adilas Label Builder app. He showed us a full build from the ground up. We built a PO label and then did a number of live tests. We had Wayne, Steve, and myself on the demo. Calvin is doing a great job. I will be meeting with him later on today to finish up some pieces.

Briefly working with Eric on some local JavaScript validation and questions. He is getting further along on his sub special account tracking project (loyalty points, gift cards, etc.).

Working with Wayne on media/content stuff. He is going through and testing all kinds of stuff on the new AWS environment. Currently, we have provided him a list of some known bugs and he is working through them. That is awesome.

Spent some more time working on the adilas tick list (giant to do list). Still just trying to get all of the smaller projects listed out and on one spreadsheet. That's a pretty big project in and of itself.

Wayne has been heading this project, along with Eric.

https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?q=AWS

In progress. Hundreds of methods to be exposed. 

This is round 2 piece. Bid out for $15,000 to make it into a web app.

Steve would like the login and API setup page to be more user friendly. Currently it requires some very techy info and we need to tie it to better security. We may also need to allow corp keys that are aliases vs the old way (use-53). I had a small problem with doing a label and then not being able to get back to it to edit it. I couldn't use the new labels using Internet Explorer. We still need help files for the new label builder. It may also be nice to record some training videos and publish them. I also told Calvin that I would help build him an adilas 3rd party solutions page. Also, as a reminder, I was going to send Calvin an email and request some formatting options. I would also love the option to be able to nudge a selection around using the arrow keys (moving the actual fields in the label editor).

Lots of new videos, updates, and help files needed. Things keep changing - on a daily basis. Shannon and I talked about turning help files and/or training material into elements of time, our own CMS (content management system) for user guide topics and files. That could really help and speed things up.

This project has been months and months in the coming… it is getting closer and really needs some tight combing, code review, and kicking the tires.

Calvin was slightly delayed, so I kept working on the adilas tick list project (getting notes off of post-it notes and into a bigger spreadsheet document). Got the spreadsheet ready and sent it over to Steve. There were 50+ projects just on that new spreadsheet. Calvin called and we touched base. I am going to make a page for him to help promote his Adilas Label Builder app and wizard type editor. He will send people an email with a download link and serial numbers. Calvin will also finish up the last little tweaks and push up those files. We are getting close on this round. The next phase will come after we allow a few users to get in there and beat it up a bit.

Got on a GoToMeeting with Eric and worked through some JavaScript validation and work flow.

Shannon and I met up and went over some things. We started out and I gave her a demo on a couple of the new things that are being released. I had some struggles with Calvin's Adilas Label Builder, but it got better. I took down some notes and will be reaching out to him. I also showed her a demo of Josh's discount engine and where that is at. We talked about some other converging projects, including Eric's loyalty points and gift card stuff (sub special accounts). We briefly talked about some sales flyer stuff and encouraged each other to keep chasing the dream. sometimes it feels kind of allusive and hard to catch. Good meeting.

Met up with Bryan to go over some code. He had a question about auto populating a number of PDF forms for a vacation rental facility. This client has a simple form that gets filled out and then the system generates all of the documents based on what pieces of the form were filled out. Bryan was trying to debug one of the forms not working. We looked deeper and it came down to a slight spelling difference between two variables. Once we got it fixed, everything worked great.

We spent the rest of the time merging in his cross corp stuff and pushing it to all other servers. This is the cross corp invoice to PO stuff that he has been working on (cross corp mapping).

Pretty quite meeting today. Steve was sick. I was working on small to do list items. Nobody else jumped on the meeting. I was making some small code tweaks. Phone calls, fixed a small graphic, and worked on some new pages to help promote MyEasySoftware and projects that Calvin has done.

The attached graphic is a small one that I made for our GoToMeeting account. We needed to put a logo up for when people join our meeting. It says "Think of where we can go!". It has a mountain trail, an adilas interface, and the adilas logo. As a side note, maybe we should sell potential. We've got a lot of that. Interesting angle.

Going through adilas pages, changing page icons and verbage to help with Calvin's new adilas label builder stuff. Also trying to help do a little bit of advertising for Calvin and MyEasySoftware.

On the GoToMeeting with Shawn. We also had Pat and Drea pop in and ask a couple of questions about the state of Oklahoma.

Going over some sub inventory queries. Lots of moving pieces and deep stuff.

Steve and I were on the morning meeting. He is still feeling kinda sick. We worked on a small query for his code and then tried to work on Calvin's adilas label builder. Steve's copy of the program is stuck in a login credential error. We tried installing and uninstalling the program a few time. We will most likely have to reach out to Calvin to see what to do. Along those lines, I also made some notes on my to do list about some other tweaks that may be needed.

I spoke with Shawn, Eric, Bryan, and Dustin at different times during the morning session. Some were simple questions and others were trying to setup times to work on certain projects. Lots of email stuff. I used the last part of the meeting to look over new state and federal tax withholdings that Shawn submitted.

Tech support for Shari O. and a stock/unit issue. We ended up fixing some code and pushing it up to data 0. It was dealing with URL encoding a passed value. The value they, the client, was trying to pass was causing the button code to break.

I also helped Eric on a JavaScript loop question. I showed him a couple of ways of doing it, using existing code and hopefully pointed him in a good direction.

Paying bills, working with Shawn, pushing up code for Dustin, and checking new state withholdings.

Bryan and I merged in some code and then spent some time working on the adilas user group code. This is feature that Bryan built to help us prioritize the project requests. Anybody is able to sign up for an account. The users will then be able to add a project, vote on things, and add comments. Currently, Bryan will be the supervisor for this feature and its use. Anyways, we spent some time and got it ready to go live. It still needs some look and feel stuff and a deep code review, but Bryan pitched it saying that if it is used a bunch, we could spend more time on it and really fix it up. I think he just wanted to get it out there. He will circle back around next week and pitch it to both Steve and I to get some direction.