Meeting with Cory and Shari O. Going over projects and priorities. Small updates on where each of the current projects stand. We talked quite a bit about the need for more special line items and maybe even making them more dynamic. Special line items are things that our clients get by default (things like labor, part number other, fee, shipping, freight, discount, supplies, etc.). They also have some special functionality that nothing else has as far as how they play, how they show up for roll call, and special grouping on certain reports. The other feature that Cory has been using recently is the percentage add-on feature that takes the cart total and then figures out a percentage to make that number stick and pass through the cart as a fee or whatever. We may end up doing a project to help with these features (dynamic special line items).

Toward the end of the meeting, we were talking about yearend payroll updates and changes that are needed (taxes, rules, forms, new rates and formulas). That comes up every year. One of our constant maintenance items for the adilas application.

Checking out some code from Will for a custom client website. Quick phone call with Steve and then merging in Will's branch of code. Texting back and forth with Will to answer questions.

Working with Eric. Going over a rollout plan for his tip stuff. His branch has 24 files, 2 current conflicts, and 15 cfc's (ColdFusion components). Lots of dependencies and internal changes. Tips sound pretty easy on the surface. It is going to get deep. It affects reports, invoices, math, deposits, payouts, balance sheet items, accounts receivable, etc.

We also talked quite a bit about USAePay (merchant gateway that we use). We have a need for some of our guys to have the actual hardware devices in their hands. We have some simulators, but the actual accounts and products are only available in a live environment. That adds a challenge. We talked about the need to better equip our developers with the correct hardware to help them in their coding and debugging processes. There is a cost to some of that. There is also a cost on the not having those pieces (more development time and even some guess work).

Anyways, we spent a little bit of time going over some ideas to help us out with R&D (research and development) type projects. We may look at getting our guys better hardware to test on and actual full or paid accounts vs just test accounts and simulators. It depends on the project. Anyways, at least having conversations about the needs there.

Bryan and I spent some time working on a small fix for some of his Authorize.net code. We pushed up some changes. We then flipped over and did some more work on the data disconnect on data 8 for a client and their sub inventory reports. We went in and ran a number of test queries, made some actual code changes and pushed up the new code. Bryan sent some emails out to let some of the power users know and to go in and try it out.

Emails and helping Chuck with some questions. Getting him going in a good direction.

Meeting with Shannon. We were going over the SWOT analysis document. Shannon had taken all of the pieces and put them together into a single document. See attached. It is very rough still, but a good start. Most of our session we were talking about plans and how we want to organize things. We decided to do two different SWOT analysis. One will be for the current - ship A - or adilas as it is right now. The other will be ship B - fracture or adilas lite - where we are headed. We also decided that we are going to do a small summary (quick and dirty) and then provide more for those who really want to read it. Not everybody likes to pour over all of the details.