Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Stephen Berkenkotter
Created By: Stephen Berkenkotter
Created Date/Time: 5/7/2019 8:00 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 4636
Template/Type: Brandon Time
Title/Caption: Meeting with Mike and team Herbo
Start Date/Time: 5/7/2019 12:00 pm
End Date/Time: 5/7/2019 1:30 pm
Main Status: Active

Sorry, no photos available for this element of time.


Notes:

Meeting with Mike Rountree, Jim Dougal, Tim Lyons, Gannon, Steve Berkenkotter, and Brandon Moore - Team Herbo

- Looking at options to help do a white label and see what market share they could get to and/or grab

- From seed (starting) clear out to general ledger (full backend/frontend accounting and financials)

- Working with Cory as an adilas rep/consultant

- There are three different things that need to be implemented together

- They have clients in the CBD category - raw material providers, internal manufacturing, packing, distributing, retail, lots of supply chain things, marketing and sales

- They have a distribution category

- They have a retail category

- How do we scope a project? You start on paper. You make a plan, you know the tools that exists, you see what matches, what doesn't, where do you start, and what are the priorities? It comes back to a plan. This could be a flow chart, diagrams, whitepapers, other documentation. It really helps if you have someone who knows Adilas and what tools are available and what tools can flex and change by default. That really helps.

- Some of the tools are different corporations (different worlds), multiple locations within your worlds, what key players (12 main players) play into that model, etc. Steve was also talking about parent/child inventory relationships. Lots of mixing and blending between the things.

- Builds, transfers, phases, locations, sub locations, etc.

- White labeling allows for custom pages and custom code - We have white label theme levels (multi or group level) as well as custom black box code (per corporation or per world). We can customize almost anything. This includes show, hide, look and feel, logic, toggle switches, flow process, requirements, validation, reporting, ect. We use the phrase you dream it up, we'll help you wire it up.

- Cory is great consultant that really knows Adilas. At some point, you will need someone on your teams that really plays the other part of the puzzle. You have to know the client and the solution. Then you mix them together to get results.

- Bring up questions... they aren't good or bad, they are just questions. Get them out there and then see what is needed (easy, medium, more complex)

- Herbo will create some diagrams of what they need and how they want things to play (processes) - Here is the world and here is how the players need to interact

- Training and content - Who owns what, who builds what, who does what? Also, what about passing training and content back and forth? Adilas is willing to provide any thing that we have through database exports, Excel, CSV, XML, JSON.

- Tim had some great questions on the backend stack and server climate. We recommended that he get with Wayne Andersen to get all of the details. Tim has a vast knowledge of backend operations and servers.

- Herbo will be working on some flow charts, processes, etc. They will have a virtual meeting of the minds and making any plans that are possible.

- On the Adilas side, Steve will be working with Cory to help with any deeper consulting info. Steve is a master planner and knows the system front to back and what is possible.