Working with Shannon. We stated out the session talking about building on what we have and filling in the gaps. We talked about building bridges vs building walls (one lets people in and the other keeps people out).

We talked about API's, sockets, endpoints, and how all these things play and flow together. I was drawing up a storm. We spent a bunch of time looking at some graphics in the teaching gallery and then drawing on top of those graphics. We then flipped over to work on content in the adilas lite and fracture plans. We were working in the API socket section of that page. So many potential benefits and ways to use it. One of my big takeaways was how this could tie-in to the value add-on core model. We, adilas, create the master road map for our product that is called the value add-on core. Adilas is going to build out the main transactional core (level 1 of 5). Any other level could be built out and/or added to with the API. We can't even fathom all of the possibilities. If you want more information about the value add-on core and all of the levels of the master plan, please see that section. Here is a quick overview of the adilas value add-on core model...

Level 1 - Adilas Transactional Data Core

Level 2 - Industry Specific Skins

Level 3 - Custom Code

Level 4 - Business Intelligence (BI)

Level 5 - Enterprise (multi world)